Base Bureau

Abstract

To appropriately perform notification using a code point in a case where information to be notified to a UE is not properly set.SOLUTION: A base station comprises: a transmission unit that transmits a first SS / PBCH block to be used for notification of a first information element related to a sub carrier offset and a second information element related to a downlink control channel for system information; and a control unit that performs control so as to set a predetermined value to the first information element and set a bit included in the second information element to a first bit value when notifying of start and end positions of a range with no second SS / PBCH block, and so as to set the predetermined value to the first information element and set the bit included in the second information element to a second bit value when notifying of a fact that there is no information related to a second SS / PBCH block associated with a control resource set for a type 0-PDCCH common search space.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a base station in a next-generation mobile communication system. [Background technology]

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-A (LTE Advanced, LTE Rel. 10, 11, 12, 13) has been specified for the purpose of achieving higher capacity and greater sophistication of LTE (LTE Rel. 8, 9).

[0003] Successor systems to LTE (e.g., FRA (Future Radio Access), 5G (5th generation mobile communication system), 5G+ (plus), NR (New Radio), NX (New radio access), FX (Future generation radio access), LTE Rel. 14 or 15 or later, etc.) are also being considered.

[0004] In existing LTE systems (e.g., LTE Rel. 8-13), a user equipment (UE: User Equipment) detects synchronization signals (Primary Synchronization Signal (PSS) and / or Secondary Synchronization Signal (SSS)) through an initial access procedure (also called cell search, etc.), synchronizes with a network (e.g., a radio base station (eNB (eNode B))), and identifies a cell to connect to (e.g., by a cell ID (identifier)).

[0005] In addition, after the cell search, the UE receives a master information block (MIB) transmitted on a broadcast channel (PBCH: Physical Broadcast Channel), a system information block (SIB) transmitted on a downlink (DL) shared channel (PDSCH: Physical Downlink Shared Channel), etc., to acquire setting information (which may be referred to as broadcast information, system information, etc.) for communication with the network. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 36.300 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall Description; Stage 2” Summary of the Invention [Problem to be solved by the invention]

[0007] In future wireless communication systems (e.g., NR or 5G), it is considered that a resource unit including a synchronization signal and a broadcast channel is defined as a synchronization signal block, and initial connection is performed based on the SS block. The synchronization signal is also called PSS and / or SSS, or NR-PSS and / or NR-SSS, etc. The broadcast channel is also called PBCH or NR-PBCH, etc. The synchronization signal block is also called SS block (Synchronization Signal block: SSB), or SS / PBCH block, etc.

[0008] In initial access, the UE searches for a sync raster located at a predetermined frequency position. In NR, it is assumed that the frequency position of the SS / PBCH block in the carrier may be located other than at the center, making it difficult to narrow down the search candidate positions.

[0009] In order to reduce the search load for the synchronization raster, it is possible to notify the UE of information regarding the position of the synchronization raster to be searched by using a code point of a predetermined information element included in a synchronization signal block. However, there has been no sufficient consideration as to what information should be notified to the UE by using the code point of the predetermined information element. If the information to be notified to the UE is not set appropriately, it is not possible to appropriately perform notification using the code point, which may result in a decrease in throughput, etc.

[0010] An object of the present disclosure is to provide a base station capable of appropriately controlling notifications regarding synchronous raster positions. [Means for solving the problem]

[0011] A base station according to an embodiment of the present disclosure includes a transmitter that transmits a first SS / PBCH block used to notify a first information element related to a subcarrier offset and a second information element related to a downlink control channel for system information, and a transmitter that sets a predetermined value to the first information element and sets a first bit value to a bit included in the second information element when notifying a start and end position of a range in which a second SS / PBCH block does not exist, and sets the predetermined value to the first information element when notifying that there is no information related to a second SS / PBCH block associated with a control resource set for a Type 0-PDCCH common search space. , and before The bits included in the second information element The offset that determines the start and end of the range is 0. and a control unit that controls the setting of the bit value to 2. Effect of the Invention

[0012] According to the present invention, notification control regarding synchronous raster positions can be appropriately performed. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram showing an example of an SS search in an existing LTE system. [Diagram 2] 11 is a diagram showing an example of a case where the next synchronization raster to be detected is notified by an SS / PBCH block. FIG. [Diagram 3] 3A and 3B show an example of a table in which RMSI-PDCCH-Config corresponding to kssb and offsets are defined. [Figure 4] 13 is a diagram showing an example of a case where the range of a synchronization raster that is not detected is notified by an SS / PBCH block. FIG. [Diagram 5] 5A and 5B show another example of the RMSI-PDCCH-Config corresponding to the kssb and a table in which an offset is defined. [Figure 6] 1 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment of the present invention. [Figure 7] 1 is a diagram illustrating an example of the overall configuration of a radio base station according to an embodiment of the present invention. [Figure 8] FIG. 2 is a diagram illustrating an example of a functional configuration of a radio base station according to an embodiment of the present invention. [Figure 9] FIG. 2 is a diagram illustrating an example of the overall configuration of a user terminal according to an embodiment of the present invention. [Figure 10] FIG. 2 is a diagram illustrating an example of a functional configuration of a user terminal according to an embodiment of the present invention. [Figure 11] A diagram showing an example of the hardware configuration of a radio base station and a user terminal in one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] In future wireless communication systems (e.g., LTE Rel. 14 and later, 5G or NR, etc.), it is considered to define a signal block (also called an SS block, an SS / PBCH block, etc.) including a synchronization signal (also called an SS, a PSS and / or an SSS, or an NR-PSS and / or an NR-SSS, etc.) and a broadcast channel (also called a broadcast signal, a PBCH, or an NR-PBCH, etc.). A collection of one or more signal blocks is also called a signal burst (an SS / PBCH burst or an SS burst). Multiple signal blocks in the signal burst are transmitted on different beams at different times (also called a beam sweep, etc.).

[0015] In NR, when a UE accesses a network (for example, at initial access), it searches (or monitors) a predetermined frequency position to acquire an SS / PBCH block. In addition, in NR, it is assumed that the number of synchronization rasters (also called sync rasters or SS (Synchronization Signal) rasters), which are frequency positions to be searched at initial access, is set for each band. For example, multiple rasters are set for each of 0-2.65 GHz, 2.4-24.25 GHz, and 24.25-100 GHz. As an example, it is considered to set 8832 rasters for 0-2.65 GHz, 15174 rasters for 2.4-24.25 GHz, and 4384 rasters for 24.25-100 GHz.

[0016] Among the MSI (Minimum System Information) read by the UE at the time of initial access, the MIB (Master Information Block) is transmitted by the PBCH. The remaining MSI is the RMSI (Remaining Minimum System Information), which corresponds to SIB (System Information Block) 1 and SIB2 in LTE. The RMSI is scheduled by the PDCCH specified by the MIB.

[0017] For example, the MIB contents (information elements) include SystemFrameNumber (6 MSBs of SystemFrameNumber), subCarrierSpacingCommon, Ssb-subcarrierOffset, Dmrs-TypeA-Position, pdcchConfigSIB1, cellBarred, intraFreqReselection, spare, 4 LSBs of SystemFrameNumber, Ssb-IndexExplicit, Half-frame-index, etc. Of course, the contents of the MIB contents are not limited to these.

[0018] Some MIB content may be interpreted differently depending on whether a first frequency band or a second frequency band higher than the first frequency band is used. For example, the first frequency band may be a frequency band lower than 6 GHz (sub-6), and the second frequency band may be a frequency band higher than 6 GHz (above-6). The first frequency band may be referred to as FR (Frequency Range) 1. The second frequency band may be a frequency band higher than 24 GHz and may be referred to as FR2, above-24, millimeter wave, etc.

[0019] SystemFrameNumber indicates the upper 6 bits of the system frame number (SFN). subCarrierSpacingCommon indicates the subcarrier spacing (SCS, numerology) for RMSI reception. Ssb-subcarrierOffset indicates the PRB (Physical Resource Block) grid offset for RMSI reception. Dmrs-TypeA-Position indicates whether the symbol position of the DMRS for PDSCH is the third symbol or the fourth symbol in a slot. pdcchConfigSIB1 (which may be called RMSI-PDCCH-Config) indicates the parameter set (PDCCH parameter set) of the PDCCH (or CORESET (Control Resource Set) including the PDCCH, RMSI CORESET) for RMSI reception. cellBarred indicates whether or not this cell is not camped on (Barred / notBarred). "intraFreqReselection" indicates whether or not there is a cell that can be camped on within the same frequency (carrier band) (allowed / not allowed). "spare" is a spare bit that may be used for a specific purpose. "4 LSBs of SystemFrameNumber" indicates the lowest 4 bits of SFN.

[0020] In above-6, Ssb-IndexExplicit indicates the upper 3 bits of the SSB index. In sub-6, one bit of Ssb-IndexExplicit is used together with Ssb-subcarrierOffset.

[0021] If the maximum number of SSB indices is 64, 6 bits may be required. In above-6, the number of SSB indices may be more than 8, and in sub-6, the number of SSB indices may never be more than 8. In sub-6, a specific bit of Ssb-IndexExplicit is used together with 4 bits of Ssb-subcarrierOffset to make Ssb-subcarrierOffset 5 bits. The lowest 3 bits may be implicitly signaled using DMRS for PBCH.

[0022] The Half-frame-index indicates whether this SSB is the first 5 ms half-frame or the second 5 ms half-frame of a radio frame (10 ms). The CRC is a cyclic redundancy check code generated based on the above information.

[0023] In this way, the number of bits and the number of code points required are determined for each MIB content. For example, Ssb-subcarrierOffset expresses the offset between the PRB (PRB for data) based on the carrier center frequency and the PRB of the SSB by the number of subcarriers. For example, when the subcarrier intervals of SSB and RMSI are the same, one PRB is 12 subcarriers, so Ssb-subcarrierOffset uses 12 code points (values ​​0-11) out of 4 bits.

[0024] Also, some MIB content may have extra bits and / or code points. A code point is a value that can be represented by bits.

[0025] For example, in sub-6, one bit of the information element (Ssb-IndexExplicit) corresponding to the index of the SS / PBCH block is used together with the information element (Ssb-subcarrierOffset) corresponding to the subcarrier offset of the SS / PBCH, and the remaining two bits are left unused. Also, for example, in above-6, Ssb-subcarrierOffset uses up to 12 code points (values ​​0 to 11) out of 16 four-bit code points, so at least four code points are unused. In sub-6, Ssb-subcarrierOffset, together with one bit of Ssb-IndexExplicit, uses up to 24 code points (values ​​0 to 23) out of 32 five-bit code points, so at least eight code points are unused.

[0026] In the existing LTE system, a cell-specific reference signal (CRS) is transmitted in each subframe, and the synchronization signal is always fixed at the center of the carrier. Therefore, even if no data traffic is generated, the UE can narrow down the frequency position where the SS search should be performed to some extent by referring to the spectrum of the received power (see Figure 1).

[0027] On the other hand, in NR, it is possible to set a longer transmission cycle for the SS / PBCH block used for initial access, etc. Also, since the frequency position of the SS / PBCH block within the carrier may be placed other than at the center, the narrowing down of search candidate positions used in the existing LTE system cannot be applied, and narrowing down of search candidate positions may be more difficult than in the existing LTE system.

[0028] In this case, it is possible to check multiple synchronization rasters one by one in order during initial access. For example, the UE can detect an accessible SS / PBCH block by sequentially searching multiple SS rasters predefined in the specification, and perform random access based on the RMSI associated with the SS / PBCH block.

[0029] However, when multiple synchronization rasters are searched for in order, it may take time to find an appropriate synchronization raster, which may result in delays in accessing the network (e.g., initial access) and / or increased power consumption.

[0030] In order to solve this problem, it may be possible to use the information elements (MIB contents) of the PBCH included in the SS / PBCH block.

[0031] As described above, the UE searches for the SS / PBCH block on the synchronization raster during initial access. In order to perform initial access, the UE needs to read the RMSI (or SIB) that includes information about the random access channel (RACH). Therefore, in a standalone (SA) NR cell, the RMSI associated with the SSB for initial access is transmitted.

[0032] On the other hand, there are cases where the RMSI associated with an SS / PBCH block not used for initial access, for example, an SS / PBCH block of a cell used only for a secondary cell (SCell) (for example, an NR cell for non-standalone (NSA), a cell for NSA), does not exist (is not transmitted). In the SS / PBCH block of an NSA cell, cellBarred is Barred, and if all cells in that carrier are NSA cells, intraFreqReselection is not allowed.

[0033] In an SS / PBCH block for which no corresponding RMSI exists, information elements used for RMSI reception are not used. Information elements used for RMSI reception include, for example, an information element (pdcchConfigSIB1) used for notification of the PDCCH configuration, and an information element (Ssb-subcarrierOffset) used for notification of the PRB grid offset for RMSI reception.

[0034] For this reason, information is defined that notifies the presence or absence of a corresponding RMSI for unused code points of a specific information element (e.g., Ssb-subcarrierOffset) included in the PBCH. When Ssb-subcarrier-offset notifies that there is no corresponding RMSI (no associated RMSI), the bits (e.g., 8 bits) of the information element (pdcchConfigSIB1) used to notify the PDCCH configuration for RMSI reception can be used for other purposes.

[0035] Therefore, it is conceivable to notify the UE of information regarding the synchronization raster to be searched next by using the pdcchConfigSIB1 (RMSI-PDCCH-Config). That is, information regarding the synchronization raster to be searched next (for example, SS / PBCH block for PCell) is notified to the UE by using an SS / PBCH block that does not support initial access arranged on the synchronization raster (for example, SS / PBCH block for SCell) (see FIG. 2). That is, the UE determines the synchronization raster to be searched next by using an unused code point of Ssb-subcarrierOffset and pdcchConfigSIB1.

[0036] For example, in sub-6 (FR1), the 5-bit 32 code points (k ssb =0-31), a value greater than a given value (for example, k ssb >23) to the UE. In this case, the UE determines that there is no control resource set for the given search space and notifies each k ssb A search for the synchronization raster is performed based on the offset set corresponding to (see FIG. 3A).

[0037] FIG. 3A shows each k ssb (For example, k ssbThis is an example of a table in which the RMSI-PDCCH-Config (pdcchConfigSIB1) corresponding to k = 23-30 and the offset corresponding to the RMSI-PDCCH-Config are specified. ssb =30 is an unspecified offset and corresponds to a reserved bit.

[0038] In addition, in above-6 (FR2), the 4-bit 16 code points of Ssb-subcarrierOffset (k ssb =0-15), the value greater than a given value (for example, k ssb >11) to the UE. In this case, the UE determines that there is no control resource set for the given search space and notifies each k ssb The search for the synchronous raster is performed based on the offset set corresponding to (see FIG. 3B). ssb =14 is an unspecified offset and corresponds to a reserved bit.

[0039] On the other hand, when notifying the next synchronization raster to be detected (for example, SSB corresponding to initial access) using bits included in pdcchConfigSIB1, etc., it is possible that the synchronization raster position does not exist within the frequency range that can be specified by the bits. A specific code point of Ssb-subcarrierOffset may be notified, and the synchronization raster range that does not need to be searched may be notified using 8 bits of RMSI-PDCCH-Config(pdcchConfigSIB1) (see Figure 4).

[0040] For example, in sub-6 (FR1), k ssb =31, above-6(FR2) ssb For example, the UE may use k = 15 to indicate a synchronous raster range that does not need to be searched. ssb If =31 is notified, each k ssb Of the 8 bits corresponding to the 1st 8 bits, the first 4 bits may be used to determine the start of a synchronous raster range that does not need to be searched, and the last 4 bits may be used to determine the end of the synchronous raster range that does not need to be searched.

[0041] In this way, the k ssb Based on this, the UE can be notified of the presence or absence of a CORESET for RMSI related to the SSB (for example, a CORESET for a type 0-PDCCH common search space). If the UE is notified that there is no CORESET for RMSI, the UE can notify the presence or absence of the notified k ssb Based on this, it determines either the synchronous raster position (GSCN) to be searched next or the synchronous raster range that does not need to be searched.

[0042] Currently, when notifying that there is no CORESET for RMSI, information about the synchronization raster is also notified at the same time (for example, k in FR1). ssb =23-29, or k in FR2 ssb =12-13).

[0043] On the other hand, when there is no CORESET for RMSI, there may be cases where information about the synchronization raster does not need to be notified to the UE. For example, a UE operating in a non-standalone mode does not necessarily need to obtain information about the synchronization raster because it is connected to a cell other than the cell it is trying to access.

[0044] Therefore, the inventors have proposed a method for not notifying information about the synchronous raster by using k entries in which reserved entries (reservation bits) are set in FIG. 3A and B. ssb (For example, k in FR1 ssb = 30, or k in FR2 ssb For example, k ssb =30 (or k ssb =14) to the UE, and without informing the UE about the synchronization raster, it is possible to inform the UE that there is no CORESET for RMSI.

[0045] However, in Fig. 3, k ssb = 30, or k ssbWhen k = 14 is used, 8 bits of RMSI-PDCCH-Config (pdcchConfigSIB1) are not used. ssb = 30, or k ssb We focused on the reserved bit at 0x14 and came up with the idea of ​​using this reserved bit to notify the UE that there is no CORESET for RMSI, and to notify the UE of certain information.

[0046] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Each embodiment may be applied alone or in combination. The following embodiments may be applied to a standalone system as well as a non-standalone system.

[0047] (First aspect) In the first aspect, when a predetermined code point is specified in the first information element, it is recognized that there is no control resource set for system information corresponding to the synchronization signal block, and the type of information to be notified is determined based on the code point included in the second information element.

[0048] In the following description, an example will be described in which the first information element is an information element on a subcarrier offset (e.g., Ssb-subcarrierOffset), and the second information element is an information element on a downlink control channel for system information (e.g., RMSI-PDCCH-Config or pdcchConfigSIB1). Of course, the first information element and the second information element are not limited to this. Other information elements included in a synchronization signal block (which may also be called an SS block or an SS / PBCH block) may be used.

[0049] In the first information element (hereinafter also referred to as Ssb-subcarrierOffset), a predetermined code point (e.g., k ssb = 30 (FR1), or k ssb Assume that the command is set to 0x14(FR2).

[0050] When a specific code point is specified in the second information element (hereinafter also referred to as RMSI-PDCCH-Config), the UE recognizes that there is no CORESET for RMSI corresponding to the detected SS block. Furthermore, the UE may recognize that the information on the synchronization raster position to be searched next and the synchronization raster range that does not need to be searched is not included. The specific code point in the second information element may be, for example, "00000000" (in the case of 8 bits).

[0051] On the other hand, if a code point other than the specific code point is specified in the second information element (hereinafter, also referred to as RMSI-PDCCH-Config), the UE recognizes that there is no CORESET for RMSI corresponding to the detected SS block. ssb = 30 (FR1), or k ssb = k other than 14 (FR2) ssb When the RMSI-PDCCH-Config is specified, it may be determined that second information different from the first information notified by the RMSI-PDCCH-Config is notified.

[0052] The code point other than the specific code point in the second information element may be, for example, "00000001 to 11111111" (in the case of 8 bits).

[0053] The second information may be different from the first information, or may be information that specifies a range that does not overlap with the range specified by the first information. For example, the second information may be an offset (e.g., N offset GSCN ) ranges that do not overlap with the ranges of

[0054] As an example, the second information may be used to notify at least one of an offset value larger than 769 and smaller than -769 in FR1, and at least one of an offset value larger than 256 and smaller than -256 in FR2. This allows a wider range to be specified to the UE as the search position of the synchronization raster.

[0055] Alternatively, the second information may be used to notify information other than information regarding the next synchronous raster position to be searched.

[0056] In this way, the UE ssb If the UE detects an SS block in which FR1 is a predetermined value (e.g., FR1 is 30 and FR2 is 14) and RMSI-PDCCH-Config is 0, the UE may determine that there is no next SS block in the cell corresponding to the detected SS block that has a control resource set for the Type 0-PDCCH common search space. ssb If an SS block is detected in which FR1 is a predetermined value (e.g., FR1 is 30 and FR2 is 14) and RMSI-PDCCH-Config is 0, it may be determined that there is no information about the next SS block having a control resource set for the Type 0-PDCCH common search space for the detected SS block.

[0057] According to the above configuration, it is possible not to notify the synchronization raster in the SS block (e.g., the SS block for non-standalone), and it is possible to notify other information by using the bits in the SS block (e.g., the PBCH). In particular, since the amount of information that can be notified by the PBCH (e.g., the MIB) is limited, it is possible to notify useful information by effectively using the 8 bits of the RMSI-PDCCH-Config using the MIB.

[0058] In addition, for a given k ssb The value of (for example, k ssb = 30, k in FR2 ssb For a given code point (e.g., 0) of the RMSI-PDCCH-Config corresponding to the offset (e.g., N offset GSCN ) may be specified and reserved bits may be used for other code points (see Figure 5).

[0059] FIG. 5A corresponds to the table for FR1, and kssb In the case of k = 30, the offset corresponding to a predetermined code point (e.g., 0) of the RMSI-PDCCH-Config is set to 0, and the offset corresponding to other code points (e.g., 1 to 255) is set to reserved. Also, FIG. 5B corresponds to a table for FR2, and k ssb = 14, the offset corresponding to a specific code point (e.g., 0) of the RMSI-PDCCH-Config is set to 0, and the offset corresponding to other code points (e.g., 1 to 255) is set to reserved. This makes it possible to flexibly notify other information using the reserved bits as necessary in the future.

[0060] (Second aspect) In a second aspect, when a code point for notifying a synchronized raster range that does not require searching is specified in a first information element, it is determined that information regarding a synchronized raster range that does not require searching is not included according to the code point notified in the second information element.

[0061] In the first information element (hereinafter also referred to as Ssb-subcarrierOffset), a predetermined code point (e.g., k ssb = 31 (FR1), or k ssb = 15 (FR2)) is specified. The specified code point corresponds to the code point used to notify the synchronized raster range that does not need to be searched.

[0062] When a specific code point is specified in the second information element (hereinafter also referred to as RMSI-PDCCH-Config), the UE recognizes that there is no CORESET for RMSI corresponding to the detected SS block. Furthermore, the UE may recognize that the information on the synchronization raster position to be searched next and the synchronization raster range that does not need to be searched is not included. The specific code point in the second information element may be, for example, "00000000" (in the case of 8 bits).

[0063] On the other hand, if a code point other than the specific code point is specified in the second information element (hereinafter, also referred to as RMSI-PDCCH-Config), the UE recognizes that there is no CORESET for RMSI corresponding to the detected SS block. Furthermore, the UE may determine a synchronization raster range that does not need to be searched based on the specified code point.

[0064] If a specific code point is specified in the RMSI-PDCCH-Config, the UE shall determine the start of the offset (N offset start ) and End (N offset end ) is 0. In this case, the UE may recognize that the synchronous raster (N reference GSCN ) does not have an SS block with a CORESET for the corresponding RMSI. In this case, the UE may determine that intra-frequency reselection is not allowed (equivalent to intraFreqReselection=not allowed).

[0065] However, if the notification contents are different from those of intraFreqReselection notified by PBCH (e.g., MIB), the UE may control to prioritize one of the notifications (e.g., MIB notification) and ignore the other notification. This allows communication to be continued appropriately even if the notification contents are different.

[0066] In this way, by using the code point used to notify the range of the synchronized raster that does not need to be searched, the information about the synchronized raster is not notified. ssb = 30 (FR1), or k ssb When RMSI-PDCCH-Config is specified as 14 (FR2), all code points notified in the RMSI-PDCCH-Config can be used for other purposes.

[0067] (Variations) In a given release (e.g., Rel. 15), it is possible to notify that information on the next synchronization raster position to be searched and the synchronization raster range that does not need to be searched is not included using a specific code point of the RMSI-PDCCH-Config, and k ssb = 30 (FR1), or k ssb It is assumed that the interpretation of the remaining code points of RMSI-PDCCH-Config when FR=14 (FR2) is specified will be specified in a future release (for example, Rel. 16 or later).

[0068] In such a case, k ssb = 30 (FR1), or k ssb In a future release, UE capability information (UE capability) regarding whether the remaining code points of RMSI-PDCCH-Config can be interpreted when FR=14(FR2) is specified may be specified together with the contents of the code points.

[0069] (Wireless communication system) A configuration of a wireless communication system according to an embodiment of the present invention will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present invention or a combination of these methods.

[0070] 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment of the present invention. In the wireless communication system 1, carrier aggregation (CA) and / or dual connectivity (DC) can be applied, which integrates a plurality of basic frequency blocks (component carriers) with the system bandwidth (e.g., 20 MHz) of the LTE system as one unit.

[0071] The wireless communication system 1 may be referred to as LTE (Long Term Evolution), LTE-A (LTE-Advanced), LTE-B (LTE-Beyond), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), NR (New Radio), FRA (Future Radio Access), New-RAT (Radio Access Technology), etc., or may be referred to as a system that realizes these.

[0072] The wireless communication system 1 includes a wireless base station 11 that forms a macrocell C1 with a relatively wide coverage, and wireless base stations 12 (12a-12c) that are arranged in the macrocell C1 and form small cells C2 that are narrower than the macrocell C1. User terminals 20 are arranged in the macrocell C1 and each small cell C2. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure.

[0073] The user terminal 20 can be connected to both the radio base station 11 and the radio base station 12. It is assumed that the user terminal 20 uses the macro cell C1 and the small cell C2 simultaneously using CA or DC. The user terminal 20 may also apply CA or DC using multiple cells (CCs) (for example, five or fewer CCs, six or more CCs).

[0074] Communication between the user terminal 20 and the radio base station 11 can be performed using a carrier (also called an existing carrier, legacy carrier, etc.) with a relatively low frequency band (e.g., 2 GHz) and narrow bandwidth. On the other hand, a carrier with a relatively high frequency band (e.g., 3.5 GHz, 5 GHz, etc.) and wide bandwidth may be used between the user terminal 20 and the radio base station 12, or the same carrier as between the user terminal 20 and the radio base station 11 may be used. Note that the configuration of the frequency bands used by each radio base station is not limited to this.

[0075] Furthermore, the user terminal 20 can communicate in each cell using time division duplex (TDD) and / or frequency division duplex (FDD). Furthermore, a single numerology may be applied in each cell (carrier), or multiple different numerologies may be applied.

[0076] The wireless base station 11 and the wireless base station 12 (or the two wireless base stations 12) may be connected by wire (for example, optical fiber conforming to CPRI (Common Public Radio Interface), X2 interface, etc.) or wirelessly.

[0077] The radio base station 11 and each radio base station 12 are each connected to a higher station device 30, and are connected to a core network 40 via the higher station device 30. The higher station device 30 includes, but is not limited to, an access gateway device, a radio network controller (RNC), a mobility management entity (MME), and the like. Each radio base station 12 may be connected to the higher station device 30 via the radio base station 11.

[0078] The radio base station 11 is a radio base station having a relatively wide coverage, and may be called a macro base station, an aggregation node, an eNodeB (eNB), a transmission / reception point, etc. The radio base station 12 is a radio base station having a local coverage, and may be called a small base station, a micro base station, a pico base station, a femto base station, a Home eNodeB (HeNB), a Remote Radio Head (RRH), a transmission / reception point, etc. Hereinafter, when there is no need to distinguish between the radio base stations 11 and 12, they are collectively referred to as the radio base station 10.

[0079] Each user terminal 20 is a terminal compatible with various communication methods such as LTE and LTE-A, and may include not only a mobile communication terminal (mobile station) but also a fixed communication terminal (fixed station).

[0080] In the wireless communication system 1, as a wireless access scheme, Orthogonal Frequency Division Multiple Access (OFDMA) is applied to the downlink, and Single Carrier Frequency Division Multiple Access (SC-FDMA) and / or OFDMA is applied to the uplink.

[0081] OFDMA is a multi-carrier transmission method that divides a frequency band into multiple narrow frequency bands (subcarriers) and maps data to each subcarrier for communication. SC-FDMA is a single-carrier transmission method that divides the system bandwidth into bands consisting of one or consecutive resource blocks for each terminal, and reduces interference between terminals by having multiple terminals use different bands. Note that the uplink and downlink wireless access methods are not limited to the combination of these, and other wireless access methods may be used.

[0082] In the wireless communication system 1, a downlink shared channel (PDSCH: Physical Downlink Shared Channel) shared by each user terminal 20, a broadcast channel (PBCH: Physical Broadcast Channel), a downlink L1 / L2 control channel, etc. are used as downlink channels. User data, upper layer control information, SIB (System Information Block), etc. are transmitted by the PDSCH. Furthermore, MIB (Master Information Block) is transmitted by the PBCH.

[0083] The downlink L1 / L2 control channels include a PDCCH (Physical Downlink Control Channel), an EPDCCH (Enhanced Physical Downlink Control Channel), a PCFICH (Physical Control Format Indicator Channel), a PHICH (Physical Hybrid-ARQ Indicator Channel), etc. Downlink control information (DCI: Downlink Control Information) including scheduling information of a PDSCH and / or a PUSCH, etc., is transmitted by the PDCCH.

[0084] Note that scheduling information may be notified by DCI. For example, DCI for scheduling DL data reception may be called DL assignment, and DCI for scheduling UL data transmission may be called UL grant.

[0085] The number of OFDM symbols used for the PDCCH is transmitted by the PCFICH. The PHICH transmits delivery confirmation information (e.g., retransmission control information, also called HARQ-ACK, ACK / NACK, etc.) of the HARQ (Hybrid Automatic Repeat reQuest) for the PUSCH. The EPDCCH is frequency division multiplexed with the PDSCH (Downlink Shared Data Channel) and is used for transmitting DCI, etc., like the PDCCH.

[0086] In the wireless communication system 1, as uplink channels, an uplink shared channel (PUSCH: Physical Uplink Shared Channel) shared by each user terminal 20, an uplink control channel (PUCCH: Physical Uplink Control Channel), a random access channel (PRACH: Physical Random Access Channel), and the like are used. The PUSCH transmits user data, higher layer control information, and the like. The PUCCH transmits downlink radio quality information (CQI: Channel Quality Indicator), delivery acknowledgement information, scheduling request (SR), and the like. The PRACH transmits a random access preamble for establishing a connection with a cell.

[0087] In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), etc. are transmitted as downlink reference signals. In addition, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. are transmitted as uplink reference signals. Note that the DMRS may be called a user equipment specific reference signal (UE-specific Reference Signal). In addition, the reference signals to be transmitted are not limited to these.

[0088] (Radio base station) 7 is a diagram showing an example of the overall configuration of a wireless base station according to an embodiment of the present invention. The wireless base station 10 includes a plurality of transmitting / receiving antennas 101, an amplifier unit 102, a transmitting / receiving unit 103, a baseband signal processing unit 104, a call processing unit 105, and a transmission path interface 106. Note that the wireless base station 10 may be configured to include one or more of each of the transmitting / receiving antennas 101, the amplifier unit 102, and the transmitting / receiving unit 103.

[0089] User data to be transmitted from the radio base station 10 to the user terminal 20 on the downlink is input from the higher-level station device 30 to the baseband signal processing unit 104 via the transmission path interface 106 .

[0090] In the baseband signal processing unit 104, transmission processes such as Packet Data Convergence Protocol (PDCP) layer processing, user data division and joining, Radio Link Control (RLC) layer transmission processes such as RLC retransmission control, Medium Access Control (MAC) retransmission control (e.g., HARQ transmission process), scheduling, transmission format selection, channel coding, Inverse Fast Fourier Transform (IFFT) processing, and precoding processing are performed on the user data, and the data is transferred to the transceiver unit 103. In addition, transmission processes such as channel coding and inverse fast Fourier transform are also performed on the downlink control signal, and the data is transferred to the transceiver unit 103.

[0091] The transmitting / receiving unit 103 converts the baseband signal output from the baseband signal processing unit 104 after precoding for each antenna into a radio frequency band and transmits the converted signal. The radio frequency signal frequency-converted by the transmitting / receiving unit 103 is amplified by the amplifier unit 102 and transmitted from the transmitting / receiving antenna 101. The transmitting / receiving unit 103 can be configured from a transmitter / receiver, a transmitting / receiving circuit, or a transmitting / receiving device that are explained based on a common understanding in the technical field related to the present invention. Note that the transmitting / receiving unit 103 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit.

[0092] On the other hand, for an uplink signal, a radio frequency signal received by the transmitting / receiving antenna 101 is amplified by the amplifier unit 102. The transmitting / receiving unit 103 receives the uplink signal amplified by the amplifier unit 102. The transmitting / receiving unit 103 frequency-converts the received signal to a baseband signal and outputs the signal to the baseband signal processing unit 104.

[0093] The baseband signal processing unit 104 performs Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing, error correction decoding, MAC retransmission control reception processing, and RLC layer and PDCP layer reception processing on the user data included in the input uplink signal, and transfers the data to the higher level station device 30 via a transmission path interface 106. The call processing unit 105 performs call processing (setting, releasing, etc.) of communication channels, status management of the wireless base station 10, management of wireless resources, etc.

[0094] The transmission line interface 106 transmits and receives signals to and from the higher-level station device 30 via a predetermined interface. The transmission line interface 106 may also transmit and receive signals (backhaul signaling) to and from other wireless base stations 10 via an inter-base station interface (for example, an optical fiber conforming to CPRI (Common Public Radio Interface), an X2 interface).

[0095] The transceiver 103 transmits a synchronization signal block including a first information element related to a subcarrier offset (e.g., Ssb-subcarrierOffset) and a second information element related to a downlink control channel for system information (e.g., RMSI-PDCCH-Config or pdcchConfigSIB1).

[0096] 8 is a diagram showing an example of a functional configuration of a wireless base station according to an embodiment of the present invention. Note that this example mainly shows functional blocks of characteristic parts in this embodiment, and the wireless base station 10 may be assumed to also have other functional blocks necessary for wireless communication.

[0097] The baseband signal processing unit 104 includes at least a control unit (scheduler) 301, a transmission signal generating unit 302, a mapping unit 303, a reception signal processing unit 304, and a measurement unit 305. Note that these components only need to be included in the radio base station 10, and some or all of the components do not necessarily need to be included in the baseband signal processing unit 104.

[0098] The control unit (scheduler) 301 performs overall control of the wireless base station 10. The control unit 301 can be configured with a controller, a control circuit, or a control device that is explained based on common understanding in the technical field related to the present invention.

[0099] The control unit 301 controls, for example, signal generation in the transmission signal generation unit 302, signal allocation in the mapping unit 303, etc. The control unit 301 also controls signal reception processing in the reception signal processing unit 304, signal measurement in the measurement unit 305, etc.

[0100] The control unit 301 controls the scheduling (e.g., resource allocation) of system information, downlink data signals (e.g., signals transmitted on PDSCH), and downlink control signals (e.g., signals transmitted on PDCCH and / or EPDCCH, such as acknowledgement information). The control unit 301 also controls the generation of downlink control signals, downlink data signals, and the like, based on the result of determining whether or not retransmission control is required for uplink data signals. The control unit 301 also controls the scheduling of synchronization signals (e.g., PSS (Primary Synchronization Signal) / SSS (Secondary Synchronization Signal)), downlink reference signals (e.g., CRS, CSI-RS, DMRS), and the like.

[0101] In addition, the control unit 301 controls the scheduling of uplink data signals (e.g., signals transmitted on PUSCH), uplink control signals (e.g., signals transmitted on PUCCH and / or PUSCH, such as delivery acknowledgement information), random access preambles (e.g., signals transmitted on PRACH), uplink reference signals, etc.

[0102] In addition, the control unit 301 controls to notify at least one of whether or not to search for a synchronization raster, the search range, and the range in which searching is not required, using the code points of the first information element (e.g., Ssb-subcarrierOffset) and the second information element (e.g., RMSI-PDCCH-Config or pdcchConfigSIB1).

[0103] The transmission signal generating unit 302 generates downlink signals (downlink control signals, downlink data signals, downlink reference signals, etc.) based on instructions from the control unit 301, and outputs the generated downlink signals to the mapping unit 303. The transmission signal generating unit 302 can be configured from a signal generator, a signal generating circuit, or a signal generating device that is explained based on common understanding in the technical field related to the present invention.

[0104] The transmission signal generating unit 302 generates a DL assignment for notifying allocation information of downlink data and / or a UL grant for notifying allocation information of uplink data, for example, based on an instruction from the control unit 301. Both the DL assignment and the UL grant are DCI and follow the DCI format. In addition, the downlink data signal is coded and modulated according to a coding rate, a modulation method, and the like determined based on channel state information (CSI) from each user terminal 20, and the like.

[0105] Based on an instruction from the control unit 301, the mapping unit 303 maps the downlink signal generated by the transmission signal generation unit 302 to a predetermined radio resource and outputs the result to the transmission / reception unit 103. The mapping unit 303 can be configured from a mapper, a mapping circuit, or a mapping device that is described based on a common understanding in the technical field related to the present invention.

[0106] The received signal processing unit 304 performs reception processing (e.g., demapping, demodulation, decoding, etc.) on the received signal input from the transmitting / receiving unit 103. Here, the received signal is, for example, an uplink signal (uplink control signal, uplink data signal, uplink reference signal, etc.) transmitted from the user terminal 20. The received signal processing unit 304 can be configured with a signal processor, a signal processing circuit, or a signal processing device described based on common understanding in the technical field related to the present invention.

[0107] The received signal processing unit 304 outputs information decoded by the receiving process to the control unit 301. For example, when a PUCCH including an HARQ-ACK is received, the received signal processing unit 304 outputs the HARQ-ACK to the control unit 301. In addition, the received signal processing unit 304 outputs the received signal and / or the signal after the receiving process to the measurement unit 305.

[0108] The measurement unit 305 performs measurements on the received signal. The measurement unit 305 can be configured with a measurement instrument, a measurement circuit, or a measurement device described based on common understanding in the technical field related to the present invention.

[0109] For example, the measurement unit 305 may perform RRM (Radio Resource Management) measurement, CSI (Channel State Information) measurement, etc., based on the received signal. The measurement unit 305 may measure received power (e.g., RSRP (Reference Signal Received Power)), received quality (e.g., RSRQ (Reference Signal Received Quality), SINR (Signal to Interference plus Noise Ratio), SNR (Signal to Noise Ratio)), signal strength (e.g., RSSI (Received Signal Strength Indicator)), propagation path information (e.g., CSI), etc. The measurement result may be output to the control unit 301.

[0110] (User terminal) 9 is a diagram showing an example of the overall configuration of a user terminal according to an embodiment of the present invention. The user terminal 20 includes a plurality of transmitting / receiving antennas 201, an amplifier unit 202, a transmitting / receiving unit 203, a baseband signal processing unit 204, and an application unit 205. Note that it is sufficient that the user terminal 20 is configured to include one or more of each of the transmitting / receiving antennas 201, the amplifier unit 202, and the transmitting / receiving unit 203.

[0111] The radio frequency signal received by the transmitting / receiving antenna 201 is amplified by the amplifier unit 202. The transmitting / receiving unit 203 receives the downlink signal amplified by the amplifier unit 202. The transmitting / receiving unit 203 frequency-converts the received signal to a baseband signal and outputs the signal to the baseband signal processing unit 204. The transmitting / receiving unit 203 can be configured from a transmitter / receiver, a transmitting / receiving circuit, or a transmitting / receiving device that are explained based on a common understanding in the technical field related to the present invention. Note that the transmitting / receiving unit 203 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit.

[0112] The baseband signal processing unit 204 performs FFT processing, error correction decoding, retransmission control reception processing, etc. on the input baseband signal. Downlink user data is transferred to the application unit 205. The application unit 205 performs processing related to layers higher than the physical layer and the MAC layer, etc. Among the downlink data, broadcast information may also be transferred to the application unit 205.

[0113] On the other hand, uplink user data is input from the application unit 205 to the baseband signal processing unit 204. In the baseband signal processing unit 204, transmission processing for retransmission control (for example, transmission processing for HARQ), channel coding, precoding, Discrete Fourier Transform (DFT) processing, IFFT processing, etc. are performed, and the data is transferred to the transceiver unit 203. The transceiver unit 203 converts the baseband signal output from the baseband signal processing unit 204 into a radio frequency band and transmits it. The radio frequency signal frequency-converted by the transceiver unit 203 is amplified by the amplifier unit 202 and transmitted from the transceiver antenna 201.

[0114] In addition, the transceiver 203 receives a synchronization signal block including a first information element related to a subcarrier offset (e.g., Ssb-subcarrierOffset) and a second information element related to a downlink control channel for system information (e.g., RMSI-PDCCH-Config or pdcchConfigSIB1).

[0115] 10 is a diagram showing an example of a functional configuration of a user terminal according to an embodiment of the present invention. Note that this example mainly shows functional blocks of characteristic parts in this embodiment, and the user terminal 20 may be assumed to also have other functional blocks necessary for wireless communication.

[0116] The baseband signal processing unit 204 of the user terminal 20 includes at least a control unit 401, a transmission signal generating unit 402, a mapping unit 403, a reception signal processing unit 404, and a measurement unit 405. Note that these components only need to be included in the user terminal 20, and some or all of the components do not necessarily need to be included in the baseband signal processing unit 204.

[0117] The control unit 401 performs overall control of the user terminal 20. The control unit 401 can be configured from a controller, a control circuit, or a control device that is explained based on common understanding in the technical field related to the present invention.

[0118] The control unit 401 controls, for example, signal generation in the transmission signal generation unit 402, signal allocation in the mapping unit 403, etc. The control unit 401 also controls signal reception processing in the reception signal processing unit 404, signal measurement in the measurement unit 405, etc.

[0119] The control unit 401 acquires the downlink control signal and the downlink data signal transmitted from the radio base station 10 from the received signal processing unit 404. The control unit 401 controls the generation of the uplink control signal and / or the uplink data signal based on the result of judging whether or not retransmission control is required for the downlink control signal and / or the downlink data signal.

[0120] In addition, the control unit 401 sets a predetermined code point (for example, k ssb = 30 (FR1), or k ssb If the second information element (e.g., RMSI-PDCCH-Config) is specified as the control resource set for system information corresponding to the synchronization signal block, the control resource set is recognized as not being present, and the type of information to be notified is determined based on the code point (e.g., using 8 bits) included in the second information element (e.g., RMSI-PDCCH-Config).

[0121] Furthermore, when the first code point (for example, 00000000) is specified in the second information element, the control unit 401 may determine that the second information element does not include information on the synchronization raster position to be searched and the synchronization raster range that does not need to be searched.

[0122] In addition, when a code point other than the first code point is specified in the second information element, the control unit 401 determines whether or not a code point other than the predetermined code point (for example, k ssb =24-29(FR1), or k ssb In the case where the FR2 information element is specified as FR1=12-13 (FR2), it may be determined that information different from the information notified by the second information element is notified.

[0123] A predetermined offset with respect to the synchronization raster position may be defined for a first code point in the second information element, and reserved bits may be set for code points other than the first code point.

[0124] In addition, the control unit 401 may include a code point (e.g., k ssb = 31 (FR1), or k ssb If a second code point (e.g., 00000000) is specified in the second information element, it may be determined that the information on the synchronization raster range that does not need to be searched is not included.

[0125] The transmission signal generating unit 402 generates uplink signals (uplink control signals, uplink data signals, uplink reference signals, etc.) based on instructions from the control unit 401, and outputs the signals to the mapping unit 403. The transmission signal generating unit 402 can be configured from a signal generator, a signal generating circuit, or a signal generating device that is explained based on common understanding in the technical field related to the present invention.

[0126] The transmission signal generating unit 402 generates uplink control signals related to acknowledgement information, channel state information (CSI), etc., based on, for example, an instruction from the control unit 401. The transmission signal generating unit 402 also generates uplink data signals based on an instruction from the control unit 401. For example, when a downlink control signal notified from the radio base station 10 includes an UL grant, the transmission signal generating unit 402 is instructed by the control unit 401 to generate an uplink data signal.

[0127] Based on an instruction from the control unit 401, the mapping unit 403 maps the uplink signal generated by the transmission signal generation unit 402 to a radio resource and outputs the result to the transmission / reception unit 203. The mapping unit 403 can be configured with a mapper, a mapping circuit, or a mapping device that is described based on a common understanding in the technical field related to the present invention.

[0128] The received signal processing unit 404 performs reception processing (e.g., demapping, demodulation, decoding, etc.) on the received signal input from the transmitting / receiving unit 203. Here, the received signal is, for example, a downlink signal (downlink control signal, downlink data signal, downlink reference signal, etc.) transmitted from the wireless base station 10. The received signal processing unit 404 can be configured from a signal processor, a signal processing circuit, or a signal processing device that is explained based on a common understanding in the technical field related to the present invention. Furthermore, the received signal processing unit 404 can configure a receiving unit related to the present invention.

[0129] The received signal processing unit 404 outputs information decoded by the receiving process to the control unit 401. The received signal processing unit 404 outputs, for example, broadcast information, system information, RRC signaling, DCI, and the like to the control unit 401. In addition, the received signal processing unit 404 outputs the received signal and / or the signal after the receiving process to the measurement unit 405.

[0130] The measurement unit 405 performs measurements on the received signal. The measurement unit 405 can be configured with a measurement instrument, a measurement circuit, or a measurement device described based on common understanding in the technical field related to the present invention.

[0131] For example, the measurement unit 405 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 405 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement result may be output to the control unit 401.

[0132] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically and / or logically coupled, or may be realized by using two or more devices that are physically and / or logically separated and directly and / or indirectly (for example, by using wires and / or wirelessly) connected to each other and using these multiple devices.

[0133] For example, a radio base station, a user terminal, etc. in one embodiment of the present invention may function as a computer that performs processing of the wireless communication method of the present invention. Fig. 11 is a diagram showing an example of a hardware configuration of a radio base station and a user terminal according to one embodiment of the present invention. The above-mentioned radio base station 10 and user terminal 20 may be physically 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.

[0134] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the radio base station 10 and the user terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0135] For example, although only one processor 1001 is shown, there may be multiple processors. Additionally, the processes may be performed by one processor, or the processes may be performed by one or more processors simultaneously, sequentially, or in other manners. Additionally, the processor 1001 may be implemented by one or more chips.

[0136] Each function in the radio base station 10 and the user terminal 20 is realized, for example, by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations, controls communications via a communication device 1004, and controls the reading and / or writing of data in the memory 1002 and the storage 1003.

[0137] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned baseband signal processing unit 104 (204), call processing unit 105, etc. may be realized by the processor 1001.

[0138] Furthermore, the processor 1001 reads out programs (program codes), software modules, data, etc. from the storage 1003 and / or the communication device 1004 into the memory 1002, and executes various processes according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 401 of the user terminal 20 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and other functional blocks may be realized in a similar manner.

[0139] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store an executable program (program code), software modules, and the like for implementing a wireless communication method according to one embodiment of the present invention.

[0140] Storage 1003 is a computer-readable recording medium, and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (CD-ROM (Compact Disc ROM)), a digital versatile disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, and other suitable storage media. Storage 1003 may also be referred to as an auxiliary storage device.

[0141] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize, for example, Frequency Division Duplex (FDD) and / or Time Division Duplex (TDD). For example, the above-mentioned transmission / reception antenna 101 (201), amplifier unit 102 (202), transmission / reception unit 103 (203), transmission path interface 106, etc. may be realized by the communication device 1004.

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

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

[0144] Furthermore, the radio base station 10 and the user 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), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0145] (Modification) In addition, the terms described in this specification and / or terms necessary for understanding this specification may be replaced with terms having the same or similar meanings. For example, a channel and / or a symbol may be a signal (signaling). Also, a signal may be a message. A reference signal may be abbreviated as RS (Reference Signal) and may be called a pilot, pilot signal, etc. depending on the applied standard. Also, a component carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, etc.

[0146] Moreover, a radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may 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.

[0147] Furthermore, a slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may also be a time unit based on numerology. A slot may also include multiple minislots. Each minislot may be composed of one or more symbols in the time domain. A minislot may also be called a subslot.

[0148] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. A radio frame, a subframe, a slot, a minislot, and a symbol may each be called by a different name. For example, one subframe may be called a transmission time interval (TTI), a plurality of consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, a subframe and / or a TTI may be a subframe (1 ms) in an existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that a unit representing a TTI may be called a slot, a minislot, or the like, instead of a subframe.

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

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

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

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

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

[0154] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. In addition, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI and one subframe may each be composed of one or more resource blocks. Note that one or more RBs may be called a physical resource block (PRB), a subcarrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0156] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. 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, etc. may be changed in various ways.

[0157] Furthermore, the information, parameters, etc. described in this specification may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0158] The names used for parameters and the like in this specification are not limiting in any respect. For example, the various channels (e.g., PUCCH (Physical Uplink Control Channel), PDCCH (Physical Downlink Control Channel), etc.) and information elements may be identified by any suitable names, and the various names assigned to these various channels and information elements are not limiting in any respect.

[0159] The information, signals, etc. described herein 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.

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

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

[0162] The notification of information is not limited to the aspects / embodiments described in this specification, 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, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination of these.

[0163] The physical layer signaling may be called L1 / L2 (Layer 1 / Layer 2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC connection setup message, an RRC connection reconfiguration message, etc. The MAC signaling may be notified by using a MAC control element (MAC CE (Control Element)), for example.

[0164] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0165] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., with a predetermined value).

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

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

[0168] As used herein, the terms "system" and "network" are used interchangeably.

[0169] In this specification, the terms "base station (BS)", "radio base station", "eNB", "gNB", "cell", "sector", "cell group", "carrier" and "component carrier" may be used interchangeably. A base station may also be called a fixed station, NodeB, eNodeB (eNB), access point, transmission point, reception point, femtocell, small cell, etc.

[0170] A base station can accommodate one or more (e.g., three) cells (also called sectors). 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 term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

[0171] In this specification, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)" and "terminal" may be used interchangeably. A base station may also be called a fixed station, NodeB, eNodeB (eNB), access point, transmission point, reception point, femtocell, small cell, etc.

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

[0173] Furthermore, the radio base station in this specification may be read as a user terminal. For example, each aspect / embodiment of the present invention may be applied to a configuration in which communication between a radio base station and a user terminal is replaced with communication between a plurality of user terminals (D2D: Device-to-Device). In this case, the user terminal 20 may be configured to have the functions of the radio base station 10 described above. Furthermore, the terms "uplink" and "downlink" may be read as "side". For example, an uplink channel may be read as a side channel.

[0174] Similarly, the user terminal in this specification may be interpreted as a wireless base station. In this case, the wireless base station 10 may be configured to have the functions of the user terminal 20 described above.

[0175] In this specification, an operation that is described as being performed by a base station may be performed by its upper node in some cases. In a network including 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 the base station, one or more network nodes other than the base station (such as, but not limited to, an MME (Mobility Management Entity) and an S-GW (Serving-Gateway)), or a combination thereof.

[0176] Each aspect / embodiment described herein may be used alone, in combination, or switched depending on the implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described herein may be rearranged unless inconsistent. For example, the methods described herein present elements of various steps in an example order, and are not limited to the particular order presented.

[0177] Each aspect / embodiment described in this specification may be applied to a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), New-RAT (Radio Access Technology), NR (New Radio), NX (New radio access), FX (Future generation radio access), GSM (Registered trademark) (Global System for Mobile communications), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (Registered trademark)), IEEE 802.16 (WiMAX (Registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (Registered trademark), or other suitable wireless communication method, and / or a next generation system enhanced based on these.

[0178] As used herein, 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."

[0179] As used herein, 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 herein 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 precede the second element in some way.

[0180] As used herein, the term "determining" may encompass a wide variety of actions. For example, "determining" may be considered to be "determining" calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, etc. Also, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc. Also, "determining" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. That is, a "judgment" may be considered as "deciding" to take some action.

[0181] As used herein, 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 the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed."

[0182] As used herein, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables and / or printed electrical connections, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range and / or optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0183] In this specification, the term "A and B are different" may mean "A and B are different from each other." Terms such as "separate," "coupled," etc. may be interpreted similarly.

[0184] When the terms "including," "comprising," and variations thereof are used in this specification or the claims, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in the specification or the claims, the term "or" is not intended to be an exclusive or.

[0185] Although the present invention has been described in detail above, it is clear to those skilled in the art that the present invention is not limited to the embodiments described in the present specification. The present invention can be implemented in modified and altered forms without departing from the spirit and scope of the present invention defined based on the description of the claims. Therefore, the description in this specification is for illustrative purposes only and does not have any limiting meaning on the present invention.

[0186] This application is based on Japanese Patent Application No. 2020-517743, filed on May 11, 2018, the contents of which are incorporated herein in their entirety.

Claims

[Claim 1] a transmitter for transmitting a first SS / PBCH block used for reporting a first information element related to a subcarrier offset and a second information element related to a downlink control channel for system information; a control unit that controls the first information element to have a predetermined value and the bit included in the second information element to have a first bit value when notifying the start and end positions of a range in which a second SS / PBCH block does not exist, and that controls the first information element to have the predetermined value and the bit included in the second information element to have a second bit value corresponding to the case in which an offset determining the start and end of the range is 0 when notifying that there is no information on a second SS / PBCH block associated with a control resource set for a Type 0-PDCCH common search space.

Images