JP7790844B2 - Terminal, base station and communication method - Google Patents

Description

The present invention relates to a terminal, a base station, and a communication method in a wireless communication system.

For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that meet the requirements of a large-capacity system, high data transmission speeds, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption (for example, non-patent document 1).

NR Release 17 considers the use of higher frequency bands than previous releases (e.g., Non-Patent Document 2). For example, in the frequency band from 52.6 GHz to 71 GHz, applicable numerology including subcarrier spacing and channel bandwidth, physical layer design, and anticipated interference in actual wireless communications are being considered.

3GPP TS 38.300 V16.6.0 (2021-06) 3GPP TS 38.306 V16.5.0 (2021-06)

In newly operating frequency bands that use higher frequencies than conventional bands, it is expected that larger sub-carrier spacing (SCS) and a larger number of beams will be used. The system information required when performing initial access must be appropriate for operation in those frequency bands.

The present invention has been made in consideration of the above points, and enables initial access to be performed according to the frequency band in a wireless communication system.

According to the disclosed technology, there is provided a terminal including: a receiving unit that receives a block including a synchronization signal and a broadcast channel from a base station; and a control unit that assumes Quasi-Co-Location (QCL) between the blocks including the synchronization signal and the broadcast channel, wherein the broadcast channel includes a parameter that notifies subcarrier spacing, the number of parameters related to the QCL that are applied to the block including the synchronization signal and the broadcast channel is based on the parameter that notifies subcarrier spacing, and the number of parameters related to the QCL is 64 or less .

The disclosed technology enables initial access to be performed according to the frequency band in a wireless communication system.

1 is a diagram illustrating an example of the configuration of a wireless communication system according to an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of a frequency range according to an embodiment of the present invention. FIG. 1 is a diagram illustrating an example of an SSB structure. A figure showing an example (1) of SSB and RMSI arrangement. A figure showing an example (2) of SSB and RMSI arrangement. A figure showing an example (3) of SSB and RMSI arrangement. 1 is a flowchart illustrating an initial access according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of an MIB according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. FIG.

The following describes an embodiment of the present invention with reference to the drawings. Note that the embodiment described below is an example, and the embodiments to which the present invention can be applied are not limited to the following embodiment.

Existing technologies are used as appropriate when operating the wireless communication system of an embodiment of the present invention. However, the existing technologies in question may be, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning that includes LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR), unless otherwise specified.

In addition, in the embodiments of the present invention described below, terms used in existing LTE, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily referred to as "NR-".

Furthermore, in an embodiment of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or another method (e.g., Flexible Duplex, etc.).

Furthermore, in an embodiment of the present invention, "configuring" radio parameters, etc. may mean that predetermined values are pre-configured, or that radio parameters notified from the base station 10 or terminal 20 are set.

Figure 1 is a diagram showing an example configuration of a wireless communication system in an embodiment of the present invention. As shown in Figure 1, the wireless communication system in an embodiment of the present invention includes a base station 10 and a terminal 20. Although Figure 1 shows one base station 10 and one terminal 20, this is an example and there may be multiple base stations 10 and multiple terminals 20 of each.

The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. The base station 10 transmits synchronization signals and system information to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via NR-PBCH and is also referred to as broadcast information. The synchronization signals and system information may also be referred to as SSB (SS/PBCH block). As shown in FIG. 1, the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

The terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and performs measurement of propagation path quality based on the reception results of the reference signals.

Figure 2 shows an example of a frequency range in an embodiment of the present invention. The NR specifications of 3GPP Release 15 and Release 16 are considering operating in frequency bands above 52.6 GHz, for example. As shown in Figure 2, FR (Frequency range) 1, which is currently specified for operation, is the frequency band from 410 MHz to 7.125 GHz, with an SCS (Subcarrier spacing) of 15, 30, or 60 kHz and a bandwidth of 5 MHz to 100 MHz. FR2 is the frequency band from 24.25 GHz to 52.6 GHz, with an SCS of 60, 120, or 240 kHz and a bandwidth of 50 MHz to 400 MHz. For example, the newly operated frequency band may be from 52.6 GHz to 71 GHz.

In the newly operated frequency bands, up to 64 SSB beams may be supported in both licensed and unlicensed bands. Furthermore, the initial BWP (Bandwidth Part) may support a 120 kHz SCS for SSB and a 120 kHz SCS for initial access signals and channels.

In addition to 120 kHz SCS, SSB with 480 kHz SCS may be supported. This SSB may be used to perform initial access supporting CORESET (Control Resource Set) #0/Type 0-PDCCH included in the MIB. However, the following restrictions may apply. For example, the entry number of the synchronization raster may be restricted. Furthermore, in the case of SSB with 480 kHz SCS, only CORESET #0/Type 0-PDCCH with 480 kHz SCS may be supported. Furthermore, SSB-CORESET multiplexing pattern 1 (SS/PBCH block and CORESET multiplexing pattern 1) may be prioritized.

Support may be provided for uniquely identifying ANR (Automatic Neighbor Relation) and PCI (Physical Cell Identity) for detecting SSBs with 120 kHz SCS, 480 kHz SCS, and 960 kHz SCS. Also, support may be provided for CORESET#0/Type0-PDCCH included in the MIB for SSBs with 120 kHz SCS, 480 kHz SCS, and 960 kHz SCS. Also, one CORESET#0/Type0-PDCCH SCS may be supported per SSB SCS. For example, {SSB SCS, CORESET#0/Type0-PDCCH SCS} may be supported as {120, 120}, {480, 480}, or {960, 960}. Furthermore, SSB-CORESET multiplexing pattern 1 may be prioritized.

In Release 16NR-U, enhancements related to SSB were made. For example, within a discovery burst transmission window (DBTW) of up to 5 ms, up to 20 SSB candidate positions may be configured for a 30 kHz SCS, and up to 10 SSB candidate positions may be configured for a 15 kHz SCS. Furthermore, within each DBTW, one of up to eight beams applied to SSB may be transmitted at one of the SSB candidate positions corresponding to PBCH-DMRS. The PBCH payload may also indicate the SSB candidate position index and the MSB of the Quasi co-location (QCL) parameter. The number of QCL parameters applied to SSB may be {1, 2, 4, 8}.

Figure 3 is a diagram illustrating an example of an SSB structure. As shown in Figure 3, the SSB is arranged within a resource of 20 PRBs (Physical Resource Blocks) and 4 symbols. The PSS is arranged from PRB #4 to PRB #15 of the first symbol. The SSS is arranged from PRB #4 to PRB #15 of the third symbol. The PBCH is arranged from PRB #0 to PRB #20 of the second and fourth symbols, and from PRB #0 to PRB #3 and PRB #16 to PRB #20 of the third symbol. Also, as shown in Figure 3, the PBCH is accompanied by a DMRS (Demodulation Reference Signal) arranged every four symbols.

The SSB symbol position within a slot in one half frame and the SSB burst pattern are set for each SCS. For example, in a 15 kHz SCS, the first SSB symbol is placed in symbol #2 and symbol #8 within one slot. In licensed bands below 3 GHz, SSB is placed in slots #0 and #1. In licensed bands above 3 GHz, SSB is placed in slots #0, #1, #2, and #3. In unlicensed bands above 3 GHz, SSB is placed in slots #0, #1, #2, #3, and #4.

Also, for example, in one case of 30 kHz SCS, the first symbol of the SSB is placed in symbol #4, symbol #8, symbol #16, and symbol #20 within two slots. In bands below 3 GHz, the SSB is placed in slot #0. In bands above 3 GHz, the SSB is placed in slot #0, slot #1, slot #2, and slot #3.

Also, for example, in other cases of 30 kHz SCS, the first symbol of SSB is placed in symbol #2 and symbol #8 within one slot. In licensed bands, SSB is placed in slot #0 and slot #1, or slot #0, slot #1, slot #2 and slot #3. In unlicensed bands, SSB is placed in all slots from slot #0 to slot #9.

Also, for example, in 120 kHz SCS, the first symbol of SSB is placed in symbol #4, symbol #8, symbol #16, and symbol #20 within two slots. SSB is placed in slot #0, slot #1, slot #2, slot #3, slot #5, slot #6, slot #7, slot #8, slot #10, slot #11, slot #12, slot #13, slot #15, slot #16, slot #17, and slot #18.

Also, for example, in 240 kHz SCS, the first symbol of the SSB is placed in symbol #8, symbol #12, symbol #16, symbol #20, symbol #32, symbol #36, symbol #40, and symbol #44 within the four slots. SSB is placed in slot #0, slot #1, slot #2, slot #3, slot #5, slot #6, slot #7, and slot #8.

Figure 4 shows an example (1) of SSB and RMSI allocation. As shown in Figure 4, the SSB and the PDSCH carrying CORESET (Control Resource Set) #0 and RMSI (Remaining Minimum System Information), e.g., SIB1 (System Information Block 1), may be allocated to radio resources by TDM (Time Division Multiplexing). This TDM allocation may be supported in FR1 (Frequency Range 1) and FR2 (Frequency Range 2). Terminal 20 may receive CORESET #0 via the PDCCH.

Figure 5 shows an example (2) of SSB and RMSI allocation. As shown in Figure 5, the SSB and the PDSCH carrying CORESET #0 and RMSI, e.g., SIB1, may be allocated to radio resources using TDM and FDM (Frequency Division Multiplexing). This TDM and FDM allocation may be supported in FR2 when the SCS of the SSB is twice that of the PDCCH.

Figure 6 shows an example (3) of SSB and RMSI allocation. As shown in Figure 5, the SSB and the PDSCH carrying CORESET #0 and RMSI, e.g., SIB1, may be allocated to radio resources by FDM. This FDM allocation may be supported in FR2 when the SCS of the SSB is the same as the SCS of the PDCCH.

The arrangement example shown in Figure 4 above uses more symbols than other arrangement examples, thereby enhancing coverage for CORESET #0 and SIB1. The arrangement example shown in Figure 5 above does not require beam switching between receiving SSB and receiving CORESET #0 and SIB1, and is compatible with multiple numerologies. The arrangement example shown in Figure 6 above does not require beam switching between receiving SSB and receiving CORESET #0 and SIB1, and is compatible with a single numerology.

Figure 7 is a flowchart for explaining initial access in an embodiment of the present invention. In step S1, the terminal 20 receives an SSB and performs synchronization with the cell. Furthermore, the terminal 20 receives an MIB (Master Information Block) via the PBCH included in the SSB. In the following step S2, the terminal 20 monitors the Type 0-PDCCH search space and receives CORESET #0 via the PDCCH. In the following step S3, the terminal 20 receives SIB1 via the PDSCH based on the control information included in CORESET #0. In the following step S4, the terminal 20 performs initial access to the base station 10 based on the received system information. The initial access may be performed, for example, by a random access procedure.

Figure 8 is a diagram showing an example of an MIB in an embodiment of the present invention. As shown in Figure 8, the MIB includes the information element subCarrierSpacingCommon, which notifies the SCS. However, if only one set of SCS is expected, notification of the SCS is not necessary. Furthermore, for the 16 values of the information element ssb-SubcarrierOffset, which notifies the subcarrier offset, the number of bits can be reduced by reducing the number of channel rasters and/or synchronization rasters.

In addition, the DCI field ChannelAccess-Cpext notifies the LBT (Listen before talk) type and CP extension index, but CP extension may not be necessary in the 52.6 GHz-71 GHz band because the symbol length becomes shorter for larger SCSs.

For example, if the SCS is 120 kHz, the first symbol of the SSB candidate may be index {4, 8, 16, 20} + 28 x n. Index 0 corresponds to the first symbol of the first slot of the half frame. Slot positions n = 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, and 18 may be supported.

For example, if the SCS is 480 kHz or 960 kHz, the slot position n of the SSB may be determined based on LBT operation. For example, different SSB arrangements may be applied with and without LBT.

For example, the combinations {SCS of SSB, SCS of CORESET #0/Type 0-PDCCH} may be supported as {120, 120}, {480, 480}, and {960, 960}.

In the 52.6 GHz-71 GHz band, for example, DB (discovery burst) may be supported. Regarding DBTW, the following 1)-4) are being considered.

1) Support for operation when SCS is unknown; 2) Whether to notify information related to LBT (e.g., enabled or disabled) via MIB; 3) Signaling design related to DBTW and how to control the possibility that the size of DCI1_0 may be ambiguous; 4) Details of signaling to enable or disable DBTW.

In addition, the following 1)-3) must be determined.
1) Reuse of the information element subCarrierSpacingCommon; 2) Whether to reuse the DCI field ChannelAccess-Cpext and introduce similar notifications in other DCI1_0 formats; 3) Whether or not to notify whether LBT is enabled or disabled, licensed or unlicensed, whether DBTW is enabled or disabled, and QCL parameters related to SSB, or how to notify them.

Therefore, we propose P1) to P4) below.
P1) Using the information element subCarrierSpacingCommon in the MIB for other purposes. P2) Using the information element ssb-SubcarrierOffset in the MIB for other purposes. P3) Using the DCI field ChannelAccess-Cpext for other purposes. P4) Introducing a new DCI field in DCI format 1_0 that is scrambled with RA-RNTI, MsgB-RNTI, and/or TC-RNTI.

The following explains P1) above. The RRC parameter subCarrierSpacingCommon may notify the information shown in 1)-4) below.

1) A QCL parameter may be signaled. For example, the QCL parameter may be N ^QCL _SSB , i.e., the number of QCL parameters applied to the SSB. The QCL parameter may be greater than 64, e.g., 128, 192, etc. Alternatively, the QCL parameter may be less than 64, e.g., 32, 16, 48, etc.

By notifying the QCL parameters as described above, DBTW in Release 16NR-U can be applied with minimal specification changes.

In addition, whether LBT is enabled or disabled, DBTW is enabled or disabled, and/or licensed or unlicensed operation may be determined in association with the QCL parameter value. For example, if the QCL parameter is 64, LBT and DBTW may be disabled, and if the QCL parameter is other than 64, LBT and DBTW may be enabled.

2) Whether LBT is enabled or disabled may be notified after at least one of the following transmissions. For example, this may be after transmission of DL Msg2 (PDCCH with DCI format 1_0 scrambled with RA-RNTI/MsgB-RNTI, RAR (Random Access Response)). It may also be after transmission of DL Msg4 (PDCCH with DCI format 1_0 scrambled with C-RNTI/TC-RNTI). It may also be after transmission of UL Msg1 (PRACH). It may also be after transmission of UL MsgA (PRACH and PUSCH). It may also be after transmission of UL Msg3 (PUSCH scheduled by an UL grant in the RAR).

In addition, the above DL or the above UL may be associated with an SSB including an MIB that signals subCarrierSpacingCommon, which notifies whether LBT is enabled or disabled.

A specific type of LBT may be used when the above LBT enabled is signaled. For example, LBT with random backoff may be used, or LBT without random backoff may be used.

Whether DBTW is enabled or disabled may be associated with signaling that LBT is enabled or disabled. For example, if LBT is signaled as enabled, DBTW may be enabled.

As described above, by being notified whether LBT is enabled or disabled after a specified transmission, it becomes possible to set whether or not to apply LBT to signals or channels related to initial access, thereby improving communication efficiency.

3) The validity or invalidity of DBTW applied to the transmission of at least the associated SSB may be notified. Note that the associated SSB may be an SSB that includes an MIB that signals subCarrierSpacingCommon that notifies the validity or invalidity of DBTW. This notification may reduce the overhead associated with blind detection of SSB in terminal 20.

4) It may be notified whether the frequency band is licensed or unlicensed. The notification may be associated with whether LBT is enabled or disabled, DBTW is enabled or disabled, and/or a predetermined QCL parameter value. For example, if it is notified that the frequency band is unlicensed, the terminal 20 may assume that LBT is enabled and/or DBTW is enabled.

The following explains P2) above. One or more bits of ssb-SubcarrierOffset may be used for purposes other than notifying k_SSB. Note that k_SSB indicates the frequency domain offset in units of the number of subcarriers between the SSB and all other resource block grids. The terminal 20 may perform the operations shown in 1)-4) below with respect to one or more bits of ssb-SubcarrierOffset.

1) The number of bits for uses other than notifying k_SSB may be a fixed value defined in the specifications. For example, 1, 2, or 3 bits of the MSB or LSB of ssb-SubcarrierOffset may be the number of bits for other uses. The number of bits for other uses may also differ for each band. The number of bits for other uses may be determined depending on the channel raster and/or synchronization raster in that band. The number of bits for other uses may also be determined based on settings.

2) The uses other than k_SSB notification may be at least one of the following. For example, it may be a use to notify whether LBT is enabled or disabled. For example, when LBT is notified as enabled, UL transmission may start after LBT is performed in the band, or when LBT is not notified as enabled, LBT may not be necessary. It may also be a use to notify whether DBTW is enabled or disabled. For example, when DBTW is notified as enabled, the terminal 20 may assume the same QCL for multiple SSBs in a half frame (i.e., 5 ms).

3) Notification of 2) above may be performed by combining subCarrierSpacingCommon and a portion of ssb-SubcarrierOffset. For example, notification of 2) above may be performed by using 1 bit of subCarrierSpacingCommon and 1 bit of the MSB or LSB of ssb-SubcarrierOffset. 3) may be applied to bands that meet specified conditions or restrictions. For example, 3) may be applied to bands in which the number of synchronization rasters and/or the number of channel rasters is smaller than a specified number.

4) Bits #12 and #13 or bits #12 to #14 of the ssb-SubcarrierOffset may be used to indicate whether or not the bits already used for mapping to the most recent SSB will be used for another purpose, or for what purpose. Bits #12 and #13 may also be notified with different values. Furthermore, in the 52.6 GHz-71 GHz band, mapping to the most recent SSB may not be notified. Furthermore, the three bits #12 to #14 of the ssb-SubcarrierOffset may be used as in the conventional mapping in FR2.

By using ssb-SubcarrierOffset as in 1)-4) above, more bits can be used to communicate more information than when using only subCarrierSpacingCommon.

Conventional examples of ssb-SubcarrierOffset are shown in Table 1.

As shown in Table 1, bits #0 to #11 of the ssb-SubcarrierOffset are traditionally used to notify k_SSB, bits #12 to #14 are used to notify the most recent GSCN (Global synchronization channel number), and bit #15 is reserved.

On the other hand, an example of using ssb-SubcarrierOffset in an embodiment of the present invention is shown in Table 2.

As shown in Table 2, bits 0 to 5 of the ssb-SubcarrierOffset are used to signal k_SSB. That is, k_SSB is signaled at a granularity that is twice the granularity supported in FR2. Also as shown in Table 2, bits 6 and 7 of the ssb-SubcarrierOffset indicate the mapping of the second SSB corresponding to the CORESET associated with the Type 0-PDCCH search space set to the nearest GSCN. Also as shown in Table 2, bits 8 to 15 of the ssb-SubcarrierOffset are used for other purposes as described above.

The following explains P3) above. The DCI field ChannelAccess-Cpext may convey information other than the channel access type and/or the CP extension time index.

For example, the other information may be at least one of the following 1)-3).

1) The LBT type may be an LBT type. For example, the LBT type may be an LBT with random backoff. The LBT type may also be no LBT, i.e., no LBT needs to be performed before transmission starts. The LBT type may also be, for example, an LBT with a fixed sensing period without random backoff. The LBT type may also be an LBT that applies an omnidirectional sensing beam. The LBT type may also be an LBT that applies a directional sensing beam. The directional sensing beam may be a sensing beam that has the same spatial filter, QCL assumption, or TCI (Transmission Configuration Indicator) notification as the beam applied to the scheduled transmission.

2) It may also be information indicating whether the band is licensed or unlicensed.

3) It may also be information indicating whether DBTW is enabled or disabled.

The above information 1)-3) may be associated with other information. For example, if information indicating no LBT is explicitly notified by the DCI field ChannelAccess-Cpext, the terminal 20 may assume that DBTW is disabled.

P3) above may be applied in combination with P1), P2) and P4). Note that P3) above may be applied to an UL grant DCI, a DL allocation DCI, or an UL grant DCI and a DL allocation DCI. An UL grant DCI may mean one or more DCI formats 0_x, and a DL allocation DCI may mean one or more DCI formats 1_x.

The following explains P4) above. A new DCI field may be added to a DCI format to notify at least one of 1) and 2) below. This DCI field may be scrambled by the RA-RNTI, MsgB-RNTI, and/or TC-RNTI.

1) LBT mode. For example, this may be information indicating whether LBT is enabled or disabled, information indicating whether LBT involves random backoff, or information indicating whether LBT is directional or omnidirectional.

2) Information indicating whether the band is licensed or unlicensed.

P4) allows the LBT mode to be set for UL transmissions during initial access (e.g., the PUSCH of Msg3). Note that the LBT type in P3 may be signaled by a new DCI field.

For example, an X-bit DCI field "LBT mode" may be added to DCI format 1_0, which is scrambled with RA-RNTI or MsgB-RNTI, to indicate the LBT mode for transmitting Msg3-PUSCH.

Furthermore, for example, a DCI field may be added to DCI format 1_0, which is scrambled with RA-RNTI or MsgB-RNTI, indicating whether the cell is one to which shared spectrum access applies, one to which spectrum shared access applies in FR2-2, or one to which spectrum shared access applies in FR1.

The above-described embodiment allows the base station 10 and terminal 20 to notify information required in high frequency bands by using information elements or DCI fields in conventional system information to notify for other purposes, thereby enabling efficient signaling.

In other words, in a wireless communication system, initial access can be performed according to the frequency band.

(Device configuration)
Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

<Base station 10>
Fig. 9 is a diagram showing an example of the functional configuration of a base station 10 according to an embodiment of the present invention. As shown in Fig. 9, the base station 10 includes a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 9 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations according to the embodiment of the present invention.

The transmitter 110 has the function of generating signals to be transmitted to the terminal 20 and transmitting the signals wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 has the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, information of higher layers from the received signals. The transmitter 110 also has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

The setting unit 130 stores pre-set setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to initial access settings.

As described in the embodiments, the control unit 140 controls the setting of initial access. The control unit 140 also performs scheduling. The functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

<Terminal 20>
Fig. 10 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Fig. 10, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 10 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL/SL control signals, etc. transmitted from the base station 10. For example, the transmitter 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc. to another terminal 20 as D2D communication, and the receiver 220 receives PSCCH, PSSCH, PSDCH, PSBCH, etc. from the other terminal 20.

The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The content of the setting information includes, for example, information related to the initial access settings.

The control unit 240 controls the initial access settings as described in the embodiments. The functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

(Hardware configuration)
The block diagrams (FIGS. 9 and 10) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for 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 directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

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

For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 11 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 in one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a memory device 1002, an auxiliary memory device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

In the following description, the term "apparatus" can be interpreted as a circuit, device, unit, etc. The hardware configuration of the base station 10 and terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001 and the memory device 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

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

The processor 1001 also reads programs (program code), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with these. The program used is a program that causes a computer to execute at least some of the operations described in the above-mentioned embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the various processes described above have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

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

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

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, network controller, network card, or communication module. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting/receiving antenna, amplifier, transmitting/receiving unit, transmission path interface, etc. may be realized by the communication device 1004. The transmitting/receiving unit may be implemented as a physically or logically separated transmitting unit and receiving unit.

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

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

Furthermore, the base station 10 and the terminal 20 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 such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

(Summary of the embodiment)
As described above, according to an embodiment of the present invention, there is provided a terminal having: a receiving unit that receives from a base station a block including a synchronization signal and a broadcast channel, a control channel that carries control information, and a shared channel that carries system information based on the control information; and a control unit that executes initial access with the base station based on the system information, wherein the information included in the broadcast channel includes at least one of information related to QCL (Quasi co-location), information related to LBT (Listen before talk), information related to DBTW (Discovery burst transmission window), and information indicating whether a band is in licensed operation or unlicensed operation.

With the above configuration, the base station 10 and terminal 20 can notify information required in high frequency bands by using information elements or DCI fields in conventional system information to notify other uses, enabling efficient signaling. In other words, in a wireless communication system, initial access can be performed according to the frequency band.

The information contained in the broadcast channel may be notified by the value of a bit that notifies the subcarrier offset from the block. With this configuration, the base station 10 and terminal 20 can notify information required in high frequency bands by using information elements or DCI fields in conventional system information to notify for other purposes, enabling efficient signaling.

The receiving unit receives information indicating the LBT type via a DCI (Downlink Control Information) field, and the control unit may execute an LBT that applies the LBT type before starting transmission. With this configuration, the base station 10 and terminal 20 can notify information required in high frequency bands by using information elements or DCI fields in conventional system information to notify for other purposes, enabling efficient signaling.

The receiving unit receives information indicating the LBT type via a DCI field scrambled by the RA-RNTI, MsgB-RNTI, or TC-RNTI, and the control unit may execute an LBT that applies the LBT type before starting transmission. With this configuration, the base station 10 and terminal 20 can notify information required in high frequency bands by using information elements or DCI fields in conventional system information to notify other uses, enabling efficient signaling.

Furthermore, according to an embodiment of the present invention, a base station is provided which has a transmitting unit that transmits a block including a synchronization signal and a broadcast channel, a control channel carrying control information, and a shared channel carrying system information to a terminal based on the control information, and a control unit that performs initial access with the terminal based on the system information, wherein the information contained in the broadcast channel includes at least one of information related to QCL (Quasi co-location), information related to LBT (Listen before talk), information related to DBTW (Discovery burst transmission window), and information indicating whether the band is in licensed or unlicensed operation.

With the above configuration, the base station 10 and terminal 20 can notify information required in high frequency bands by using information elements or DCI fields in conventional system information to notify other uses, enabling efficient signaling. In other words, in a wireless communication system, initial access can be performed according to the frequency band.

Furthermore, according to an embodiment of the present invention, a communication method is provided in which a terminal executes a reception procedure for receiving from a base station a block including a synchronization signal and a broadcast channel, a control channel carrying control information, and a shared channel carrying system information based on the control information, and a control procedure for performing initial access with the base station based on the system information, and the information contained in the broadcast channel includes at least one of information related to QCL (Quasi co-location), information related to LBT (Listen before talk), information related to DBTW (Discovery burst transmission window), and information indicating whether the band is in licensed or unlicensed operation.

With the above configuration, the base station 10 and terminal 20 can notify information required in high frequency bands by using information elements or DCI fields in conventional system information to notify other uses, enabling efficient signaling. In other words, in a wireless communication system, initial access can be performed according to the frequency band.

(Supplementary explanation of the embodiment)
Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (unless inconsistent). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

Each aspect/embodiment described in this disclosure may be applied to at least one of systems utilizing LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), or other suitable systems, and next generation systems enhanced based on these. In addition, multiple systems may be combined (for example, a combination of at least one of LTE and LTE-A with 5G, etc.).

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

Specific operations described herein as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes including a base station 10, it is clear that various operations performed for communication with a terminal 20 may be performed by at least one of the base station 10 and other network nodes other than the base station 10 (such as, but not limited to, an MME or S-GW). While the above example illustrates a case where there is one other network node other than the base station 10, the other network node may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

The information or signals described in this disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). They may also be input and output via multiple network nodes.

Input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

In this disclosure, 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).

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

Software, instructions, information, etc. may also be transmitted and received via 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), these wired and/or wireless technologies are included within the definition of transmission media.

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.

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.

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

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

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

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

A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). 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 this coverage area.

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

A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

At least one of the base station and the mobile station may be referred to as 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, or the mobile body itself. 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 also be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions possessed by the base station 10 described above. 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.

Similarly, the user terminal in this disclosure may be interpreted as a base station. In this case, the base station may be configured to have the functions possessed by the user terminal described above.

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 a table, database, or other data structure), and ascertaining something that is considered a "determination." Also, "determining" and "determining" may include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and other actions that are considered a "determination." 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.

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.

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

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

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 or that the first element must in some way precede the second element.

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

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

A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

Numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology may indicate, 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 structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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.

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Other names may also be used for radio frame, subframe, slot, minislot, and symbol.

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

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

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

Note that when one slot or one minislot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the smallest time unit for scheduling. Furthermore, the number of slots (minislots) constituting the smallest time unit for scheduling may be controlled.

A TTI with a time length of 1 ms may be referred to as 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 referred to as a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length 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 that of a long TTI and greater than or equal to 1 ms.

A resource block (RB) is a resource allocation unit in the time and frequency domains, 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.

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

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

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

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

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

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

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

In this disclosure, where articles are added by translation, such as a, an, and the in English, this disclosure may include the noun following these articles being plural.

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 "combined" may also be interpreted in the same way as "different."

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

In this disclosure, SSB is an example of a block that includes a synchronization signal and a broadcast channel.

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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims (7)

a receiving unit that receives a block including a synchronization signal and a broadcast channel from a base station;
a control unit that assumes Quasi-Co-Location (QCL) between blocks including a synchronization signal and a broadcast channel ;
the broadcast channel includes a parameter for reporting a subcarrier interval ;
the number of parameters related to the QCL applied to the block including the synchronization signal and the broadcast channel is based on a parameter notifying the subcarrier spacing;
A terminal , wherein the number of parameters related to the QCL is 64 or less . The terminal according to claim 1 , wherein the number of parameters related to the QCL is 32 or 64. When the terminal operates in FR (Frequency Range) 2-2, the parameter notifying the subcarrier spacing is used to indicate the number of parameters related to the QCL applied to a block including the synchronization signal and the broadcast channel. The terminal according to claim 1. The broadcast channel includes a Master Information Block (MIB),
The terminal according to claim 1 , wherein the MIB includes a parameter that notifies the subcarrier spacing. The terminal according to claim 4 , wherein the parameter indicating the subcarrier spacing is subCarrierSpacingCommon. A communication method performed by a terminal, comprising:
receiving a block including a synchronization signal and a broadcast channel from a base station;
and assuming Quasi-Co-Location (QCL) between blocks including a synchronization signal and a broadcast channel;
the broadcast channel includes a parameter for reporting a subcarrier interval;
the number of parameters related to the QCL applied to the block including the synchronization signal and the broadcast channel is based on a parameter indicating the subcarrier spacing;
A communication method, wherein the number of parameters related to the QCL is 64 or less. A communication system including a base station and a terminal,
The base station transmits a block including a synchronization signal and a broadcast channel to the terminal;
The terminal
receiving a block including a synchronization signal and a broadcast channel from the base station;
Assuming QCL (Quasi-Co-Location) between blocks including synchronization signals and broadcast channels,
the broadcast channel includes a parameter for reporting a subcarrier interval;
the number of parameters related to the QCL applied to the block including the synchronization signal and the broadcast channel is based on a parameter indicating the subcarrier spacing;
A communication system, wherein the number of parameters related to the QCL is 64 or less.