Terminal device, base station device, and communication method

Abstract

To allow a terminal device and a base station device to efficiently communicate with each other.SOLUTION: A terminal device receives first DCI with an SI-RNTI on a first BWP, receives a SIB using a first time resource, receives second DCI with an RA-RNTI on a second BWP, receives a RAR using a second time resource, determines the first time resource using a first value and a first setting included in the first DCI, determines the second time resource using a second value and a second setting included in the second DCI, applies a first parameter list or a first default table to the second setting when a CORESET associated with CSS is not set in second setting information of the second BWP provided in the SIB, and applies a second parameter list or the first default table when the CORESET is set.SELECTED DRAWING: Figure 17

Description

[Technical Field]

[0001] The present invention relates to a terminal device, a base station device, and a communication method. [Background technology]

[0002] Currently, wireless access methods and wireless networks for the fifth generation cellular system As for technologies, the Third Generation Partnership Project (3GPP) is conducting technical studies and formulating standards for LTE (Long Term Evolution)-Advanced Pro and NR (New Radio technology) (Non-Patent Document 1).

[0003] The fifth generation cellular system will feature eMBB (enhanced Mobile Broadband) technology, which will enable high-speed, large-capacity transmission. The three expected scenarios for the service are: BroadBand (URLLC), which realizes low-latency and highly reliable communication; and mMTC (massive Machine Type Communication), which connects a large number of machine-type devices such as IoT (Internet of Things). Furthermore, Release 17, a future release of NR, will support advanced technologies such as eMBB and URLLC, with an eye on applications such as sensor networks, surveillance cameras, and / or wearable devices. Reduced capability (REDCAP) NR devices are being investigated, which do not require high requirements while reducing costs and extending battery life (Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016 [Non-patent document 2] RP-193238, Ericsson, “New SID on support of reduced capability NR devices”, December 2019 Summary of the Invention [Problem to be solved by the invention]

[0005] An object of the present invention is to provide a terminal device, a base station device, and a communication method that enable efficient communication in the above-mentioned wireless communication system. [Means for solving the problem]

[0006] (1) In order to achieve the above object, an embodiment of the present invention provides the following means: That is, a terminal device according to one embodiment of the present invention receives first downlink control information (DCI) accompanied by a CRC scrambled with an SI-RNTI in a first BWP of a first cell, and The first physical downlink shared channel (SIB) is scheduled for the first time resource. a receiver configured to receive a random access response via a scheduled PDSCH (Periodic Differential Sequence Number Channel), in a second BWP of the first cell, in a common search space, a second DCI accompanied by a CRC scrambled with an RA-RNTI, and receive a random access response via the second PDSCH scheduled for a second time resource; and a controller configured to determine the first time resource using a first value indicated by a first field included in the first DCI and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the first value and a time resource, and to determine the second time resource using a second value indicated by a second field included in the second DCI and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and a time resource, wherein the SIB is a random access response of the first BWP of the first cell. The control unit provides first setting information and second setting information of the second BWP, and applies a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation setting, determines whether a first control resource set (CORESET) linked to the common search space is set in the second setting information, and if the first CORESET is not set in the second setting information, applies a first parameter list or the first default table to the second PDSCH time domain resource allocation setting, and if the first CORESET is set in the second setting information, applies the second parameter list or the first default table to the second PDSCH time domain resource allocation setting.

[0007] (2) In addition, in one aspect of the present invention, a terminal device receives first downlink control information (DCI) accompanied by a CRC scrambled with an SI-RNTI in a first BWP of a first cell, and A first physical downlink SIB is scheduled for the first time resource. a receiving unit configured to receive via a shared channel (PDSCH), in a second BWP of the first cell, a second DCI with a CRC scrambled with the RA-RNTI in a common search space, and receive a random access response via a second PDSCH scheduled in a second time resource; a first value indicated by a first field included in the first DCI; and a time resource a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the first PDSCH time domain resource allocation configuration and the second PDSCH time domain resource allocation configuration; and determining a PDSCH time domain resource allocation configuration using a second value indicated by a second field included in the second DCI and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and a time resource. and a control unit that determines the second time resource by using the first setting information of the first BWP and the second setting information of the second BWP, wherein the SIB provides first setting information of the first BWP and second setting information of the second BWP, and the control unit applies a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation configuration, determines whether a first control resource set (CORESET) linked to the common search space is configured in the second setting information, and when the first CORESET is not configured in the second setting information, determines whether the second PDSCH time domain resource is configured. and applying a first parameter list or the first default table to the second PDSCH time domain resource allocation configuration, and applying a previous parameter list or the first default table to the second PDSCH time domain resource allocation configuration if the first CORESET is configured in the second configuration information and the second parameter list is provided in the second configuration information. The second parameter list is applied, and if the first CORESET is set in the second configuration information and the second parameter list is not provided in the second configuration information, the first parameter list or the first default table is applied to the second PDSCH time domain resource allocation configuration.

[0008] (3) In addition, the base station device according to one aspect of the present invention transmits first downlink control information (DCI) accompanied by a CRC scrambled with an SI-RNTI in a first BWP of a first cell, The first physical downlink link scheduled for the first time resource is a transmitter configured to transmit a second DCI accompanied by a CRC scrambled by the RA-RNTI in a common search space in a second BWP of the first cell, and to transmit a random access response via a second PDSCH scheduled in a second time resource; and a controller configured to determine a first value indicated by a first field included in the first DCI, using the first time resource and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the first value and the time resource, and to determine a second value indicated by a second field included in the second DCI, using the second time resource and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and the time resource, wherein the SIB is The control unit provides first setting information of the first BWP and second setting information of the second BWP, and applies a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation setting, determines whether a first control resource set (CORESET) linked to the common search space is set in the second setting information, and if the first CORESET is not set in the second setting information, applies a first parameter list or the first default table to the second PDSCH time domain resource allocation setting, and if the first CORESET is set in the second setting information, applies a second parameter list or the first default table to the second PDSCH time domain resource allocation setting.

[0009] (4) In addition, in one aspect of the present invention, the base station device is configured to: Transmitting a first downlink control information (DCI) with a CRC scrambled with the I-RNTI, The first physical downlink link scheduled for the first time resource is a transmitter configured to transmit a random access response via a scheduled shared channel (PDSCH), in a second BWP of the first cell, in a common search space, a second DCI accompanied by a CRC scrambled with the RA-RNTI, and to transmit a random access response via the second PDSCH scheduled on a second time resource; and a controller configured to determine a first value indicated by a first field included in the first DCI, using the first time resource and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the first value and the time resource, and to determine a second value indicated by a second field included in the second DCI, using the second time resource and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and the time resource, wherein the SIB provides first configuration information of the first BWP and second configuration information of the second BWP, and the controller configured to set a first default value for the first PDSCH time domain resource allocation configuration. the second setting information is configured with the first parameter list or the first default table, and determines whether a first control resource set (CORESET) linked to the common search space is configured in the second setting information; if the first CORESET is not configured in the second setting information, applies a first parameter list or the first default table to the second PDSCH time domain resource allocation setting; if the first CORESET is configured in the second setting information and the second parameter list is provided in the second setting information, applies the second parameter list to the second PDSCH time domain resource allocation setting; if the first CORESET is configured in the second setting information and the second parameter list is not provided in the second setting information, applies the first parameter list or the first default table to the second PDSCH time domain resource allocation setting.

[0010] (5) Furthermore, a communication method according to an aspect of the present invention is a communication method of a base station device, which includes transmitting first downlink control information (DCI) including a CRC scrambled by an SI-RNTI in a first BWP of a first cell, and scheduling a system information block (SIB) to a first time resource. and transmitting the first physical downlink shared channel (PDSCH) to the first cell. In the second BWP, in the common search space, transmit a second DCI with a CRC scrambled by the RA-RNTI, and transmit a random access response via a second PDSCH scheduled in a second time resource, and the first time resource and the correspondence between the first value and the time resource. and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and the time domain resource, to determine a first value indicated by a first field included in the first DCI; and and determining a second value indicated by a second field included in the DCI, wherein the SIB provides first configuration information for the first BWP and second configuration information for the second BWP, and determining whether the first PDSCH time domain resource allocation configuration is based on a first default table, a second default table, or a third default table. A table is applied to determine whether a first control resource set (CORESET) associated with the common search space is configured in the second configuration information, and if the first CORESET is not configured in the second configuration information, the first control resource set (CORESET) associated with the common search space is configured in the second PDSCH time domain resource allocation configuration. When the parameter list or the first default table is applied and the first CORESET is set in the second configuration information, the second PDSCH time domain resource allocation configuration is set to the second CORESET. or the first default table is applied.

[0011] (6) In addition, a communication method according to an aspect of the present invention is a communication method of a base station device, which includes transmitting first downlink control information (DCI) including a CRC scrambled by an SI-RNTI in a first BWP of a first cell, and scheduling a system information block (SIB) to a first time resource. and transmitting the first physical downlink shared channel (PDSCH) to the first cell. In the second BWP, in the common search space, transmit a second DCI with a CRC scrambled by the RA-RNTI, and transmit a random access response via a second PDSCH scheduled in a second time resource, and the first time resource and the correspondence between the first value and the time resource. and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and the time domain resource, to determine a first value indicated by a first field included in the first DCI; and and determining a second value indicated by a second field included in the DCI, wherein the SIB provides first configuration information for the first BWP and second configuration information for the second BWP, and determining whether the first PDSCH time domain resource allocation configuration is based on a first default table, a second default table, or a third default table. A table is applied to determine whether a first control resource set (CORESET) associated with the common search space is configured in the second configuration information, and if the first CORESET is not configured in the second configuration information, the first control resource set (CORESET) associated with the common search space is configured in the second PDSCH time domain resource allocation configuration. the second parameter list or the first default table is applied, and if the first CORESET is configured in the second configuration information and the second parameter list is provided in the second configuration information, the second parameter list is applied to the second PDSCH time domain resource allocation configuration. When the second configuration information is configured with the first CORESET and the second parameter list is not provided in the second configuration information, The first parameter list or the first default table is applied to the allocation settings. [Effects of the Invention]

[0012] According to the present invention, the terminal device and the base station device can communicate efficiently. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating the concept of a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram illustrating the relationship between subframes, slots, and minislots in the time domain according to an embodiment of the present invention. [Figure 4] A figure showing an example of an SS / PBCH block and SS burst set for an embodiment of the present invention. [Figure 5] A diagram showing resources in which PSS, SSS, PBCH, and DMRS for PBCH are arranged within an SS / PBCH block according to an embodiment of the present invention. [Figure 6] 10 is a diagram showing an example of a parameter configuration of an information element BWP-DownlinkCommon of initialDownlinkBWP and separateInitialDownlinkBWP according to an embodiment of the present invention. FIG. [Figure 7] FIG. 1 is a diagram illustrating an example of RF retuning according to an embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing an overview of the frequency location of an additional synchronization signal block according to an embodiment of the present invention. [Figure 9] FIG. 10 is a diagram illustrating an example of a PDSCH mapping type according to an embodiment of the present invention. [Figure 10] FIG. 10 is a diagram illustrating an example of a selection criterion for a resource allocation table applied to PDSCH time domain resource allocation according to the embodiment of the present invention. [Figure 11] FIG. 10 is a diagram showing an example of a default table A according to the embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing an example of a default table B according to the embodiment of the present invention. [Figure 13] FIG. 10 is a diagram showing an example of a default table C according to the embodiment of the present invention. [Figure 14] FIG. 10 is a diagram showing an example of calculating an SLIV according to an embodiment of the present invention. [Figure 15] 10 is a flow diagram showing an example of processing related to reception of DCI, SIB, and random access response in a terminal device 1 according to an embodiment of the present invention. [Figure 16] 10 is a flow diagram showing an example of processing related to determination / identification / configuration / setting of a resource allocation table applied to PDSCH time domain resource allocation in a terminal device 1 according to an embodiment of the present invention. FIG. [Figure 17] FIG. 10 is a flow diagram showing another example of processing related to determination / identification / configuration / setting of a resource allocation table applied to PDSCH time domain resource allocation in a terminal device 1 according to an embodiment of the present invention. [Figure 18] 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an embodiment of the present invention. [Figure 19] 1 is a schematic block diagram showing a configuration of a base station device 3 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, an embodiment of the present invention will be described.

[0015] Fig. 1 is a conceptual diagram of a wireless communication system in this embodiment. In Fig. 1, the wireless communication system includes a terminal device 1A, a terminal device 1B, and a base station device 3. Hereinafter, the terminal device 1A and the terminal device 1B are also referred to as terminal devices 1.

[0016] The terminal device 1 is also referred to as a user terminal, a mobile station device, a communication terminal, a mobile device, a terminal, a UE (User Equipment), or an MS (Mobile Station). However, the terminal device 1 may be a REDCAP NR device and may be referred to as a REDCAP UE. The base station device 3 is also referred to as a radio base station device, a base station, a radio base station, a fixed station, a Node B (NB), an evolved Node B (eNB), a BTS (Base Transceiver Station), a BS (Base Station), an NR Node B (NR NB), an NNB, a TRP (Transmission and Reception Point), or a gNB. The base station device 3 may include a core network device. The base station device 3 may also have one or more transmission and reception points 4. At least some of the functions / processing of the base station device 3 described below may be functions / processing of each transmission and reception point 4 included in the base station device 3. The base station device 3 may serve the terminal device 1 with a communication coverage area (communication area) controlled by the base station device 3 as one or more cells. Furthermore, the base station device 3 may serve the terminal device 1 as one or more cells, each of which is a communication range (communication area) controlled by one or more transmission / reception points 4. Furthermore, the base station device 3 may divide one cell into multiple partial areas (beamed areas) and serve the terminal device 1 in each partial area. Here, the partial area may be identified based on the index of the beam used in beamforming or the index of precoding.

[0017] In this embodiment, the wireless communication link from the base station device 3 to the terminal device 1 is called a downlink. In this embodiment, the wireless communication link from the terminal device 1 to the base station device 3 is called an uplink.

[0018] In FIG. 1, in wireless communication between the terminal device 1 and the base station device 3, a cyclic prefix is ​​used. Orthogonal Frequency Division Multiplexing (OFDM) including Cyclic Prefix (CP), Single-Carrier Frequency Division Multiplexing (SC-FDM), Discrete Fourier Transform Spread OFDM (DFT-S-OFDM), or other transmission methods may be used.

[0019] In this embodiment, OFDM is used as the transmission method and OFDM symbols are used, but the present invention also includes cases where the above-mentioned other transmission methods are used.

[0020] In addition, in FIG. 1, the wireless communication between the terminal device 1 and the base station device 3 does not use a CP. Alternatively, the above-mentioned transmission method may be used in which zero padding is used instead of the CP. Also, the CP or zero padding may be added both before and after the data.

[0021] One aspect of this embodiment is a wireless access technology (RAT) such as LTE and LTE-A / LTE-A Pro. Carrier aggregation (CA) with LTE Access Technology (LTE) is operated in Dual Connectivity (DC) In this case, some or all of the cells or cell groups, carriers or carrier groups (for example, a primary cell (PCell), a secondary cell (SCell)) may be used. The SpCell (Special Cell) may be used in a Primary Secondary Cell (PSCell), a Master Cell Group (MCG), a Secondary Cell Group (SCG), etc. In addition, one aspect of the present embodiment may be used in a standalone mode that operates independently. In DC operation, the SpCell (Special Cell) is referred to as a PCell of an MCG or a PSCell of an SCG depending on whether the MAC (Medium Access Control) entity is associated with an MCG or an SCG, respectively. In non-DC operation, the SpCell (Special Cell) is referred to as a PCell. The SpCell (Special Cell) supports PUCCH transmission and Contention Based Random Access (CBRA).

[0022] In this embodiment, one or more serving cells may be configured for the terminal device 1. The configured multiple serving cells may include one primary cell and one or more secondary cells. The primary cell may be a serving cell where an initial connection establishment procedure has been performed, a serving cell where a connection re-establishment procedure has started, or a cell designated as the primary cell in a handover procedure. One or more secondary cells may be configured at the time when an RRC (Radio Resource Control) connection is established or thereafter. However, the configured multiple serving cells may include one primary secondary cell. The primary secondary cell may be a secondary cell capable of transmitting control information in the uplink, among one or more secondary cells configured for the terminal device 1. Furthermore, two types of subsets of serving cells, an MCG and an SCG, may be configured for the terminal device 1. The MCG may be configured with one PCell and zero or more SCells. The SCG may be configured with one PScell ​​and zero or more SCells.

[0023] The wireless communication system of this embodiment may employ TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). The TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of a plurality of cells. Furthermore, cells employing the TDD method and cells employing the FDD method may be aggregated. The TDD method may be referred to as unpaired spectrum operation. The FDD method may be referred to as paired spectrum operation.

[0024] In the following, a subframe will be described. In this embodiment, the subframe will be referred to as a subframe, but the subframe according to this embodiment may also be referred to as a resource unit, a radio frame, a time period, a time interval, etc.

[0025] FIG. 2 is a diagram showing an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention. Each radio frame has a length of 10 ms. Each radio frame is made up of 10 subframes and W slots. One slot is made up of X OFDM symbols. In other words, the length of one subframe is 1 ms. The time length of each bit is defined by the subcarrier spacing. For example, if the subcarrier spacing of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix) is used, X=7 or X=14. , which are 0.5 ms and 1 ms, respectively. Also, when the subcarrier spacing is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. Also, for example, when X=14, When the subcarrier spacing is 15 kHz, W=10, and when the subcarrier spacing is 60 kHz, W=40. Figure 2 shows an example where X=7. Note that the example in Figure 2 is for the case where X=14. can be similarly expanded. Also, the uplink slot is similarly defined, and the downlink slot and the uplink slot may be defined separately. Also, the bandwidth of the cell in FIG. 2 is a partial bandwidth. However, the BWP used in the downlink may be referred to as the downlink BWP, and the BWP used in the uplink may be referred to as the uplink BWP. A slot may also be defined as a Transmission Time Interval (TTI). A slot does not have to be defined as a TTI, which may be the transmission period of a transport block.

[0026] The signals or physical channels transmitted in each slot may be represented by a resource grid, which is defined by a number of subcarriers and a number of OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier. The number of carriers depends on the downlink and uplink bandwidths of the cell, respectively. Each element in the resource grid is called a resource element (RE). An RE may be identified by its subcarrier number and OFDM symbol number.

[0027] The resource grid is a physical downlink channel (e.g., PDSCH) or an uplink Used to represent the mapping of resource elements of a channel (e.g., PUSCH) For example, if the subcarrier spacing is 15 kHz, the number of OFDM symbols included in the subframe is X=14, and in the case of NCP, one physical resource block (PRB) is , 14 consecutive OFDM symbols in the time domain and 12*Nmax consecutive Nmax is the maximum number of resource blocks (RBs) determined by the subcarrier spacing setting μ, which will be described later. In other words, the resource grid consists of (14*12*Nmax, μ) REs. In the case of ECP (Extended CP), only a subcarrier spacing of 60 kHz is supported, so one PRB is defined by, for example, 12 (the number of OFDM symbols included in one slot) * 4 (the number of slots included in one subframe) = 48 consecutive OFDM symbols in the time domain and 12*Nmax, μ consecutive subcarriers in the frequency domain. In other words, the resource grid consists of (48*12*Nmax, μ) REs.

[0028] The RBs are defined as a reference resource block (reference RB), a common resource block (CRB), a PRB, and a virtual resource block (VRB). One RB is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may constitute resource blocks at subcarrier intervals of, for example, 15 kHz, and may be numbered in ascending order. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (or simply referred to as a "reference point"). Point A may serve as a common reference point for the resource block grid. The position of point A may be determined / specified by a parameter offsetToPointA included in SIB1. The parameter offsetToPointA is a parameter indicating the frequency offset between point A and the lowest frequency subcarrier of the lowest frequency resource block that overlaps with the synchronization signal block used by the terminal device 1 in initial cell selection. However, the unit of the frequency offset is a resource block with a subcarrier spacing of 15 kHz in frequency range (FR) 1, and a resource block with a subcarrier spacing of 60 kHz in frequency range 2. However, the location of point A may be indicated by the frequency location ARFCN (Absolute Radio-Frequency Channel Number) using the RRC parameter absoluteFrequencyPointA. CRBs are RBs numbered in ascending order from 0 in each subcarrier spacing setting μ from point A. Therefore, CRB numbers are defined for each subcarrier spacing setting μ. A CRB corresponding to a subcarrier spacing setting μ may be referred to as a CRBμ. The above-mentioned resource grid is defined by the CRB. However, the center of subcarrier index 0 of CRBμ numbered 0 in each subcarrier spacing setting μ is point A.The PRBs are RBs numbered in ascending order starting from 0 and included in a BWP of each subcarrier spacing setting μ, and the PRBs are RBs numbered in ascending order starting from 0 and included in a BWP with a subcarrier spacing setting μ. A PRB corresponding to a subcarrier spacing setting μ may be referred to as a PRB μ. A physical uplink channel is first mapped to a VRB. Then, the VRB is mapped to a PRB. Hereinafter, an RB may be a VRB, a PRB, a CRB, or a reference resource block.

[0029] A BWP is a subset of consecutive RBs (which may be CRBs) with a certain subcarrier spacing setting in a certain carrier. The terminal device 1 may be configured with up to four BWPs (downlink BWPs) in the downlink. The active downlink BWPs at a certain time are The terminal device 1 may not expect to receive PDSCH, PDCCH, or CSI-RS outside the band of the active downlink BWP. The terminal device 1 may be configured with up to four BWPs (uplink BWPs) in the uplink. At any given time, there may be only one active uplink BWP (active uplink BWP). The terminal device 1 does not transmit PUSCH and PUCCH outside the band of the active uplink BWP.

[0030] Next, we will explain the subcarrier spacing setting μ. As mentioned above, in NR, one or more Several OFDM numerologies are supported. The packet spacing setting μ (μ=0,1,...,5) and the CP length are given by higher layers for the downlink BWP. , is given by the higher layer in the uplink BWP. Here, given μ, The rear spacing Δf is given by Δf=2^μ·15(kHz).

[0031] In the subcarrier spacing setting μ, slots are numbered from 0 to N^{subframe, μ}_{slot}-1 in ascending order within a subframe, and from 0 to N^{frame, μ}_{slot}-1 in ascending order within a frame. Based on the slot configuration and CP, N^{slot}_{symb} consecutive OFDM symbols are obtained. In the slot, N^{slot}_{symb} is 14. In the slot n^{μ}_{s} in the subframe The start of is aligned in time with the start of the n^{μ}_{s}*N^{slot}_{symb}th OFDM symbol in the same subframe.

[0032] Next, we will explain subframes, slots, and minislots. This figure shows an example of the relationship between subframes, slots, and minislots in the time domain. As shown in the figure, three types of time units are defined. A subframe is 1 ms regardless of the subcarrier spacing, and the number of OFDM symbols included in a slot is 7 or 14 (however, each symbol (If the CP added to the subframe is an extended CP, it may be 6 or 12.) The slot length varies depending on the subcarrier spacing. Here, if the subcarrier spacing is 15 kHz, one subframe contains 14 OFDM symbols. The downlink slot may be referred to as PDSCH mapping type A. The uplink slot may be referred to as PUSCH mapping type A.

[0033] A minislot (which may also be called a subslot) is a time unit consisting of fewer OFDM symbols than the number of OFDM symbols contained in one slot. The figure shows an example in which a minislot consists of two OFDM symbols. The OFDM symbols in a slot may coincide with the OFDM symbol timing that constitutes the slot. The smallest unit of scheduling may be a slot or a minislot. Allocating a minislot may also be referred to as non-slot-based scheduling. Scheduling a minislot may also be expressed as scheduling a resource in which the relative time positions of the reference signal and data start positions are fixed. A downlink minislot may be referred to as PDSCH mapping type B. An uplink minislot may be referred to as PUSCH mapping type B.

[0034] In the terminal device 1, the transmission direction of the symbol in each slot (uplink, downlink, The DCI format (uplink, downlink, or flexible) is set in a higher layer using an RRC message including predetermined higher layer parameters received from the base station device 3, or is set by a PDCCH of a specific DCI format (for example, DCI format 2_0) received from the base station device 3. In this embodiment, a slot format is a format in which each symbol in a slot is set to either uplink, downlink, or flexible. One slot format may include downlink symbols, uplink symbols, and flexible symbols.

[0035] In this embodiment, a carrier corresponding to a serving cell is called a component carrier (CC) (or carrier). In this embodiment, in the downlink, a carrier corresponding to a serving cell is called a downlink CC (or downlink carrier). In this embodiment, in the uplink, a carrier corresponding to a serving cell is called an uplink CC (or uplink carrier). In this embodiment, in the sidelink, a carrier corresponding to a serving cell is called a sidelink CC (or sidelink carrier).

[0036] The physical channels and physical signals of this embodiment will be described.

[0037] In FIG. 1, the following physical channels are used in wireless communication between the terminal device 1 and the base station device 3: It is okay to do so.

[0038] PBCH (Physical Broadcast CHannel) PDCCH (Physical Downlink Control CHannel) PDSCH (Physical Downlink Shared CHannel) PUCCH (Physical Uplink Control CHannel) PUSCH (Physical Uplink Shared CHannel) PRACH (Physical Random Access CHannel)

[0039] The PBCH is a Master Information Block (MIB) containing important system information required by the terminal device 1. It is used to broadcast the PBCH (Essential Information Block, EIB: Essential Information Block, BCH: Broadcast Channel). The MIB contains the radio frame (system information for identifying the System Frame Number (SFN), information for identifying the subcarrier spacing of the System Information Block 1 (SIB1), information for identifying the resource block grid and SS / PBCH blocks (also called synchronization signal block, SS block, SSB) The SIB1 may include information indicating the PDCCH configuration for the SIB1. , which contains information necessary for evaluating whether the terminal device 1 is allowed to connect to the cell, Other system information blocks (SIBs) that determine scheduling However, the information indicating the PDCCH configuration for SIB1 includes the information regarding the control resource set. Control Resource Set (CORESET) #0 (CORESET #0 is also called CORESET0 or common CORESET) information that determines the common search space and / or required PDCCH parameters. However, CORESET indicates resource elements of the PDCCH and is composed of a set of PRBs in a time period of a certain number of OFDM symbols (for example, 1 to 3 symbols). CORESET#0 is at least Both CORESET#0 and CORESET#1 may be a CORESET for a PDCCH that schedules SIB1. CORESET#0 may be set in an MIB or may be set via RRC signaling. SIB1 may be scheduled by a PDCCH transmitted in CORESET#0. The terminal device 1 receives SIB1 scheduled by a PDCCH received in CORESET#0. However, the PDCCH that schedules SIB1 may be downlink control information (DCI) with a CRC scrambled with SI-RNTI (Scheduling information - Radio Network Temporary Identifier) ​​transmitted in the PDCCH. DCI and SI-RNTI will be described later. The terminal device 1 may receive, in the PDCCH, DCI with a CRC scrambled with SI-RNTI, and receive a PDSCH including SIB1 scheduled with the DCI. However, the PDCCH that schedules SIB1 may be a PDCCH with a CRC scrambled with SI-RNTI transmitted in the PDCCH.

[0040] The PBCH may also be used to broadcast information for identifying the number (SFN: System Frame Number) of the radio frame (also called a system frame) to which the PBCH is mapped and / or information for identifying a half radio frame (HRF: Half Frame) (also called a half frame). Note that a half radio frame is a time frame with a length of 5 ms, and the information for identifying a half radio frame may be information for identifying whether it is the first 5 ms or the last 5 ms of a 10 ms radio frame.

[0041] The PBCH is also used to broadcast the time index within the period of the SS / PBCH block. Here, the time index is information indicating the index of the synchronization signal and PBCH in the cell. The time index may be referred to as an SSB index or an SS / PBCH block index. For example, the SS / PBCH may be synchronized using the assumption of quasi-co-location (QCL) for multiple transmit beams, transmit filter settings, and / or receive spatial parameters. When transmitting blocks, the time order within a predetermined or set period may be indicated, and the terminal device may recognize different time indexes as different QCL assumptions regarding transmit beams, transmit filter settings, and / or receive spatial parameters.

[0042] The PDCCH is used in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). , is used to transmit (or carry) downlink control information. Here, one or more DCIs (which may be referred to as DCI formats) are defined for the transmission of downlink control information. That is, the fields for downlink control information are defined as DCIs. , are mapped to information bits. The PDCCH is transmitted in the PDCCH candidate. The terminal device 1 Monitor a set of PDCCH candidates in the serving cell, where monitoring may mean attempting to decode the PDCCH according to a certain DCI format.

[0043] For example, the following DCI formats may be defined: DCI Format 0_0 DCI Format 0_1 DCI Format 0_2 DCI Format 1_0 DCI Format 1_1 DCI Format 1_2 DCI Format 2_0 DCI Format 2_1 DCI Format 2_2 DCI Format 2_3

[0044] DCI format 0_0 is used for scheduling PUSCH in a serving cell. DCI format 0_0 may be used for scheduling information (frequency domain) of PUSCH. The DCI information may include information indicating the DCI domain resource allocation (regional resource allocation and time domain resource allocation). The DCI format 0_0 may be added with a Cyclic Redundancy Check (CRC) scrambled by any one of the Radio Network Temporary Identifiers (RNTIs), which are identifiers, namely, Cell-RNTI (C-RNTI), Configured Scheduling (CS)-RNTI, MCS-C-RNTI, and / or Temporary C-RNTI (TC-RNTI). The DCI format 0_0 may be monitored in a common search space or a UE-specific search space.

[0045] DCI format 0_1 ​​is for scheduling PUSCH in a serving cell. DCI format 0_1 ​​may be used for scheduling information (frequency domain) of PUSCH. information indicating BWP, information indicating time domain resource allocation, DCI format 0_1 ​​may include a Channel State Information (CSI) request, a Sounding Reference Signal (SRS) request, and / or information about antenna ports. A CRC scrambled by any of the RNTIs, C-RNTI, CS-RNTI, Semi Persistent (SP)-CSI-RNTI, and / or MCS-C-RNTI, may be added to DCI format 0_1. DCI format 0_1 ​​may be monitored in a UE-specific search space.

[0046] DCI format 0_2 is used for scheduling PUSCH in a serving cell. DCI format 0_2 may be used for PUSCH scheduling information (frequency domain may include information indicating a BWP, a CSI request, an SRS request, and / or information regarding antenna ports. DCI format 0_2 uses C-RNTI, CSI-RNTI, SP-CSI-RNTI, and / or A CRC scrambled by one of the MCS-C-RNTIs may be added to the DCI format 0_2. DCI format 0_2 may be monitored in a UE-specific search space. DCI format 0_2 may also be referred to as DCI format 0_1A, etc.

[0047] DCI format 1_0 is used for scheduling PDSCH in a serving cell. DCI format 1_0 may be used for PDSCH scheduling information (frequency domain The DCI information may include information indicating the DCI domain resource allocation (regional resource allocation and time domain resource allocation). Among the identifiers, Mat1_0 includes C-RNTI, CS-RNTI, MCS-C-RNTI, and Paging RNTI (P-RNTI). A CRC scrambled by any of the System Information (SI)-RNTI, Random access (RA)-RNTI, and / or TC-RNTI may be added. DCI format 1_0 may be monitored in a common search space or a UE-specific search space.

[0048] DCI format 1_1 is used for scheduling PDSCH in a serving cell. DCI format 1_1 may be used for scheduling information (frequency domain) of PDSCH. information indicating BWP, information indicating BWP, DCI format 1_1 may include a Transmission Configuration Indication (TCI) and / or information about an antenna port. A CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among RNTIs may be added to DCI format 1_1. DCI format 1_1 may be monitored in a UE-specific search space.

[0049] DCI format 1_2 is used for scheduling PDSCH in a serving cell. DCI format 1_2 may be used for PDSCH scheduling information (frequency domain DCI format 1_2 may include information indicating a carrier-bandwidth (BWP), a time-domain resource allocation (domain resource allocation and time-domain resource allocation), information indicating a carrier-bandwidth (BWP), a time-domain correlation index (TCI), and / or information regarding an antenna port. DCI format 1_2 may be added with a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among the RNTIs. DCI format 1_2 may be monitored in a UE-specific search space. DCI format 1_2 may also be referred to as DCI format 1_1A, etc.

[0050] DCI format 2_0 is used to indicate the slot format of one or more slots. A slot format is defined as each OFDM symbol in a slot being classified as downlink, flexible, or uplink. For example, if the slot format is 28, DDDDDDDDDDDDFU is applied to the 14 OFDM symbols in a slot for which slot format 28 is specified. Here, D is the downlink symbol, F is the flexible symbol, and U is the uplink symbol. Slots will be described later.

[0051] DCI format 2_1 is used to notify the terminal device 1 of the PRBs (or RBs) and OFDM symbols for which no transmission may be assumed. This information may be called a preemption instruction (discontinuous transmission instruction).

[0052] DCI format 2_2 is used for transmitting PUSCH and transmit power control (TPC) commands for the PUSCH.

[0053] The DCI format 2_3 is a sounding reference signal (SRS) transmitted by one or more terminal devices 1. ) transmission. An SRS request may also be transmitted together with the TPC command. DCI format 2_3 also includes an uplink without PUSCH and PUCCH, or an SRS transmission power control linked to PUSCH transmission power control. For the uplink, which does not have a SRS request and a TPC command, may be defined.

[0054] DCI for the downlink is called a downlink grant or Here, DCI for uplink is also referred to as uplink grant or uplink assignment. DCI may also be referred to as DCI format.

[0055] The CRC parity bits added to the DCI format transmitted on one PDCCH are SI-RNTI , P-RNTI, C-RNTI, CS-RNTI, RA-RNTI, or TC-RNTI. SI-RNTI may be an identifier used for broadcasting system information. P-RNTI may be an identifier used for paging and notifying of system information changes. C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying a terminal device within a cell. TC-RNTI is an identifier for identifying a terminal device 1 that transmitted a random access preamble during CBRA.

[0056] The C-RNTI is used to control the PDSCH or PUSCH in one or more slots. The CS-RNTI is used to periodically allocate resources for the PDSCH or PUSCH. The MCS-C-RNTI is used to indicate the use of a given MCS table for grant-based transmission. The TC-RNTI is used to control PDSCH or PUSCH transmission in one or more slots. The TC-RNTI is used to schedule retransmissions of random access message 3 and transmissions of random access message 4. The RA-RNTI is determined according to the frequency and time location information of the physical random access channel that transmitted the random access preamble.

[0057] The C-RNTI and / or other RNTIs may have different values ​​corresponding to the type of traffic on the PDSCH or PUSCH. The C-RNTI and other RNTIs correspond to the service type (eMBB, URLLC, and / or mMTC) of the data transmitted on the PDSCH or PUSCH. The base station device 3 may use a different value depending on the service type of the data to be transmitted. The terminal device 1 may identify the service type of data transmitted on the associated PDSCH or PUSCH based on the value of the RNTI applied to the received DCI (used for scrambling).

[0058] In uplink wireless communication (wireless communication from terminal device 1 to base station device 3), the PUCCH is Used to transmit uplink control information (UCI) Here, the uplink control information may include Channel State Information (CSI) used to indicate the state of the downlink channel. The uplink control information may also include a Scheduling Request (SR) used to request UL-SCH resources. The uplink control information may also include a Hybrid Automatic Repeat request ACKnowledgement (HARQ-ACK). is the downlink data (Transport block, Medium Access Control Protocol Data Unit: It may also indicate a HARQ-ACK for a MAC PDU, a Downlink-Shared Channel (DL-SCH).

[0059] The PDSCH transmits downlink data (D) from the Medium Access Control (MAC) layer. L-SCH: Downlink Shared CHannel) is used for transmission. In some cases, it is also used to transmit system information (SI), paging information, random access response (RAR), etc.

[0060] PUSCH is used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or It may be used to transmit HARQ-ACK and / or CSI along with the link data. Also, PUSCH is used to transmit only CSI or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only UCI.

[0061] Here, the base station device 3 and the terminal device 1 exchange (transmit and receive) signals in a higher layer. For example, the base station device 3 and the terminal device 1 may transmit and receive an RRC message (also referred to as an RRC message, RRC information, or RRC signaling) in a Radio Resource Control (RRC) layer. Furthermore, the base station device 3 and the terminal device 1 may transmit and receive a MAC control element in a Medium Access Control (MAC) layer. Furthermore, the RRC layer of the terminal device 1 acquires system information broadcast from the base station device 3. Here, the RRC message, the system information, and / or the MAC control element are also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter (higher layer parameter). Each of the parameters included in the higher layer signal received by the terminal device 1 may be referred to as a higher layer parameter. Here, the upper layer refers to an upper layer seen from the physical layer, and may include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, the upper layer may include one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, etc. Hereinafter, the meaning of "A is given (provided) by an upper layer" or "A is given (provided) by an upper layer" may mean that an upper layer (mainly an RRC layer or a MAC layer) of the terminal device 1 receives A from the base station device 3, and the received A is given (provided) to the physical layer of the terminal device 1 from the upper layer of the terminal device 1. For example, in the terminal device 1, "upper layer parameters are provided" may mean that an upper layer signal is received from the base station device 3, and the upper layer parameters included in the received upper layer signal are provided to the physical layer of the terminal device 1 from the upper layer of the terminal device 1. Setting upper layer parameters in the terminal device 1 may mean that the upper layer parameters are given (provided) to the terminal device 1.For example, setting upper layer parameters in the terminal device 1 may mean that the terminal device 1 receives an upper layer signal from the base station device 3 and sets the received upper layer parameters in the upper layer. However, setting upper layer parameters in the terminal device 1 may also include setting default parameters that are given in advance in the upper layer of the terminal device 1.

[0062] The PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. may be common signaling for multiple terminal devices 1 in a cell. The RRC signaling transmitted from the base station device 3 is a signaling dedicated to a certain terminal device 1. In other words, terminal device-specific information may be transmitted using dedicated signaling to a certain terminal device 1. Furthermore, the PUSCH may be used to transmit UE capabilities in the uplink.

[0063] In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used to transmit information output from higher layers, but is used by the physical layer. ·Synchronization signal (SS) ·Reference Signal (RS)

[0064] The synchronization signal is a Primary Synchronization Signal (PSS) and a Sec. The PSS and SSS may be used to detect the cell ID.

[0065] The synchronization signal is used by the terminal device 1 to synchronize the frequency domain and the time domain of the downlink. Here, the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3. Note that the beam may also be referred to as a transmit or receive filter setting, or a spatial domain transmit filter or a spatial domain receive filter.

[0066] The reference signal is used by the terminal device 1 to perform propagation path compensation of the physical channel. The reference signal may also be used by the terminal device 1 to calculate downlink CSI. The reference signal may also be used to calculate downlink CSI, such as radio parameters, numerology such as subcarrier spacing, FFT window synchronization, etc. It can be used for fine synchronization where

[0067] In this embodiment, one or more of the following downlink reference signals are used. ·DMRS(Demodulation Reference Signal) ·CSI-RS(Channel State Information Reference Signal) ·PTRS(Phase Tracking Reference Signal) ·TRS(Tracking Reference Signal)

[0068] DMRS is used to demodulate modulated signals. Two types of DMRS may be defined: a reference signal for demodulating PBCH and a reference signal for demodulating PDSCH, or both may be referred to as DMRS. CSI-RS is Channel State Information (CSI). The CSI-RS is used for measurement and beam management, and periodic, semi-persistent, or aperiodic CSI reference signal transmission methods are applied. Non-zero power (NZP) CSI-RS and zero power (ZP) CSI-RS with zero transmit power (or receive power) may be defined for the CSI-RS. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmit power or no transmit power. PTRS is used to track the phase on the time axis in order to compensate for frequency offset caused by phase noise. TRS is used to compensate for Doppler shift during high-speed movement. Note that TRS may be used as one configuration of CSI-RS. For example, radio resources may be configured as TRS for one-port CSI-RS.

[0069] In this embodiment, one or more of the following uplink reference signals are used. ·DMRS(Demodulation Reference Signal) ·PTRS(Phase Tracking Reference Signal) ·SRS(Sounding Reference Signal)

[0070] DMRS is used to demodulate modulated signals. Note that DMRS includes a PUCCH demodulator. Two types of reference signals may be defined: one for demodulating the PUSCH and the other for demodulating the PUSCH, and both may be referred to as DMRS. SRS is used for measuring uplink channel state information (CSI), channel sounding, and beam management. PTRS is used to track the phase in time to compensate for frequency offsets caused by phase noise.

[0071] In this embodiment, the downlink physical channel and / or the downlink physical signal are collectively referred to as a downlink signal. In this embodiment, the uplink physical channel and / or the uplink physical signal are collectively referred to as an uplink signal. The downlink physical channel and / or the uplink physical channel are collectively referred to as a physical channel. In this embodiment, the downlink physical signal and / or the uplink physical signal are collectively referred to as a physical signal.

[0072] The BCH, UL-SCH, and DL-SCH are transport channels. A channel used in the Medium Access Control (MAC) layer is called a transport channel. The unit of the transport channel used in the MAC layer is also called a transport block (TB) and / or a MAC Protocol Data Unit (PDU). In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block. A transport block is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, a transport block is mapped to a codeword, and encoding processing is performed for each codeword.

[0073] FIG. 4 shows the SS / PBCH block (also referred to as a synchronization signal block, SS block, or SSB) according to this embodiment. FIG. 1 illustrates an example of a half frame (also referred to as a SS burst set) in which one or more SS / PBCH blocks are transmitted. 4 shows an example in which two SS / PBCH blocks are included in an SS burst set that exists at a fixed period (which may be referred to as an SSB period), and the SS / PBCH block is made up of four consecutive OFDM symbols.

[0074] The SS / PBCH block contains the synchronization signals (PSS, SSS), the PBCH, and the DMRS for the PBCH. However, the SS / PBCH block may be a block including a synchronization signal (PSS, SSS), a REDCAP PBCH, and a DMRS for the REDCAP PBCH. Transmitting the signals / channels included in the SS / PBCH block is referred to as transmitting the SS / PBCH block. In the case where one or more SS / PBCH blocks in an SS burst set are used to transmit a synchronization signal and / or a PBCH, an independent downlink transmission beam is used for each SS / PBCH block. It's fine.

[0075] In Figure 4, one SS / PBCH block contains PSS, SSS, PBCH, and DMRS for PBCH. 5 is a table showing resources in which the PSS, SSS, PBCH, and DMRS for the PBCH are allocated within the SS / PBCH block.

[0076] The PSS may be mapped to the first symbol in the SS / PBCH block (the OFDM symbol whose OFDM symbol number is 0 relative to the starting symbol of the SS / PBCH block). The sequence consists of 127 symbols, and is transmitted from the 57th subcarrier to the 183rd subcarrier in the SS / PBCH block. The subcarriers may be mapped to the subcarriers (subcarriers with subcarrier numbers 56 to 182 relative to the starting subcarrier of the SS / PBCH block).

[0077] The SSS may be mapped to the third symbol in the SS / PBCH block (the OFDM symbol whose OFDM symbol number is 2 relative to the start symbol of the SS / PBCH block). The sequence consists of 127 symbols, and is transmitted from the 57th subcarrier to the 183rd subcarrier in the SS / PBCH block. The subcarriers may be mapped to the subcarriers (subcarriers with subcarrier numbers 56 to 182 relative to the starting subcarrier of the SS / PBCH block).

[0078] PBCH and DMRS are the second, third, and fourth symbols within the SS / PBCH block (SS / PBCH block The sequence of modulation symbols for the PBCH may be mapped to OFDM symbols with OFDM symbol numbers 1, 2, and 3 relative to the starting symbol of M. symb The SS / PBCH block is composed of symbols, and may be mapped to resources to which a DMRS is not mapped, including the 1st subcarrier to the 240th subcarrier of the second and fourth symbols in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the starting subcarrier of the SS / PBCH block), and the 1st subcarrier to the 48th subcarrier and the 184th to 240th subcarriers of the third symbol in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 47 and 192 to 239 relative to the starting subcarrier of the SS / PBCH block). The DMRS symbol sequence is composed of 144 symbols, and may be mapped to one subcarrier out of every four subcarriers, including the first to 240th subcarriers of the second and fourth symbols in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the starting subcarrier of the SS / PBCH block), and the first to 48th subcarriers and the 184th to 240th subcarriers of the third symbol in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 47 and 192 to 239 relative to the starting subcarrier of the SS / PBCH block). For example, of the 240 subcarriers, PBCH modulation symbols may be mapped to 180 of the subcarriers, and DMRS for the PBCH may be mapped to 60 of the subcarriers.

[0079] Different SS / PBCH blocks in an SS burst set may be assigned different SSB indices. SS / PBCH blocks assigned a certain SSB index are assigned by base station device 3. For example, the SS / PBCH block may be transmitted periodically based on the SSB period for which it is used for initial access and the SSB period for which it is connected (Connected or RRC_Connected). An SSB period to be set for the terminal device 1 may be defined. Furthermore, the SSB period to be set for a connected (Connected or RRC_Connected) terminal device 1 may be set by an RRC parameter. Furthermore, the SSB period to be set for a connected (Connected or RRC_Connected) terminal device 1 is a period of radio resources in the time domain for potential transmission, and the base station device 3 may actually decide whether to transmit. Furthermore, the SSB period for an SS / PBCH block to be used for initial access may be defined in advance in a specification or the like. For example, the terminal device 1 making initial access may consider the SSB period to be 20 milliseconds.

[0080] The time position of the SS burst set to which the SS / PBCH block is mapped is included in the PBCH. The SS / PBCH block may be identified based on information identifying a system frame number (SFN) and / or information identifying a half frame. Device 1 may determine the current system frame number and half frame based on the received SS / PBCH block.

[0081] An SSB index (which may be referred to as an SS / PBCH block index) is assigned to the SS / PBCH block according to its temporal position within the SS burst set. The terminal device 1 identifies the SSB index based on PBCH information and / or reference signal information included in the detected SS / PBCH block.

[0082] SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assigned the same SSB index. SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Furthermore, antenna ports with SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.

[0083] Within a period of a certain SS burst set, SS / PBCH blocks assigned the same SSB index may be assumed to be QCLs with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation. A configuration corresponding to one or more SS / PBCH blocks (or reference signals) that are QCLs may be referred to as a QCL configuration.

[0084] The number of SS / PBCH blocks (which may also be referred to as the number of SS blocks or the number of SSBs) is, for example, The number of SS / PBCH blocks may be defined as the number of SS / PBCH blocks within an SS burst, an SS burst set, or an SS / PBCH block period. The number of SS / PBCH blocks may also indicate the number of beam groups for cell selection within an SS burst, an SS burst set, or an SS / PBCH block period. Here, a beam group may be defined as the number of different SS / PBCH blocks or different beams included within an SS burst, an SS burst set, or an SS / PBCH block period (SSB period).

[0085] SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assigned the same SSB index. SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Furthermore, antenna ports with SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.

[0086] Within a period of a certain SS burst set, SS / PBCH blocks assigned the same SSB index may be assumed to be QCL with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation.

[0087] The initial BWP, the initial downlink BWP, and the The initial uplink BWP (initial UL BWP) may be a BWP, a downlink BWP, and an uplink BWP used at the time of initial access before the RRC connection is established, respectively. However, The initial BWP, initial downlink BWP and initial uplink BWP may be used after the RRC connection is established. However, the initial BWP, initial downlink BWP and initial uplink BWP are The BWP may be a BWP with an index of 0 (#0), a downlink BWP with an index of 0 (#0), and an uplink BWP with an index of 0 (#0).

[0088] The initial downlink BWP may be configured by parameters provided in an MIB, parameters provided in SIB1, parameters provided in an SIB, and / or RRC parameters. For example, the initial downlink BWP may be configured by a parameter "initialDownlinkBWP" included in the parameter "downlinkConfigCommon" provided in SIB1. For example, SIB1 (or another SIB) may be transmitted including "downlinkConfigCommonRedCap." In this case, the initial downlink BWP may be configured by a parameter "initialDownlinkBWP" included in the parameter "downlinkConfigCommonRedCap" provided in SIB1 (or another SIB). However, the initialDownlinkBWP may be a parameter indicating a UE-specific (dedicated) setting of the initial downlink BWP for a UE.

[0089] The SIB1 may be transmitted including downlinkConfigCommon, which is a common downlink configuration parameter for a certain cell. At least one of the parameters for determining the common downlink parameter downlinkConfigCommon may be included in a parameter ( The parameter may include a parameter indicating the configuration of a first initial downlink BWP of a serving cell (for example, referred to as frequencyInfoDL), and a parameter indicating the configuration of a first initial downlink BWP of a serving cell (for example, referred to as initialDownlinkBWP).

[0090] SIB1 may be transmitted including downlinkConfigCommonRedCap, which is a common downlink configuration parameter of a certain cell. The downlinkConfigCommonRedCap may include a parameter (e.g., referred to as separateInitialDownlinkBWP) indicating the configuration of the initial downlink BWP (which may be referred to as a separate initial downlink BWP). However, the separateInitialDownlinkBWP included in downlinkConfigCommonRedCap is referred to as initialDownlinkBWP and may have the same information element configuration as the initialDownlinkBWP included in downlinkConfigCommon. However, the separateInitialDownlinkBWP may be included in downlinkConfigCommon. However, the separateInitialDownlinkBWP may be included in an SIB other than SIB1 and / or an RRC parameter. However, the separateInitialDownlinkBWP may be a parameter including part or all of the parameter configuration of the initialDownlinkBWP included in downlinkConfigCommon, and each parameter may be configuration information for a second initial downlink BWP (which may be a separate initial downlink BWP). The second initial downlink BWP may be referred to as a second downlink BWP.

[0091] The terminal device 1 includes separateInitialDownlinkBWP in downlinkConfigCommonRedCap. When separateInitialDownlinkBWP is received in SIB1, the separate initial downlink BWP may be specified / configured / determined based on the parameters included in the separateInitialDownlinkBWP. However, the separate initial downlink BWP may also be referred to as the initial downlink BWP. For example, when the terminal device 1 receives separateInitialDownlinkBWP (which may be initialDownlinkBWP included in downlinkConfigCommonRedCap) in SIB1, the terminal device 1 may specify / configure / determine the initial downlink BWP based on the parameters of the separateInitialDownlinkBWP. The initial downlink BWP specified / configured / determined by initialDownlinkBWP in downlinkConfigCommon may be referred to as the first initial downlink BWP, and the initial downlink BWP specified / configured / determined by separateInitialDownlinkBWP in downlinkConfigCommonRedCap may be referred to as the second initial downlink BWP.

[0092] FIG. 6 shows information on the initialDownlinkBWP and separateInitialDownlinkBWP according to this embodiment. An example of the parameter configuration of the information element (IE) BWP-DownlinkCommon is shown below. The initialDownlinkBWP and separateInitialDownlinkBWP according to this embodiment may include genericParameters, a generic parameter of the initial downlink BWP, a cell-specific parameter pdcch-ConfigCommon of the PDCCH, a cell-specific parameter pdsch-ConfigCommon of the PDSCH, and / or other parameters. The information element BWP-DownlinkCommon of the separateInitialDownlinkBWP may be referred to as BWP-DownlinkCommonRedCap. The genericParameters, pdcch-ConfigCommon, and pdsch-ConfigCommon included in the separateInitialDownlinkBWP may be referred to as genericParametersRedCap, pdcch-ConfigCommonRedCap, and pdsch-ConfigCommonRedCap, respectively.

[0093] When multiple initial downlink BWPs are configured in a cell by multiple initialDownlinkBWPs / separateInitialDownlinkBWPs (or when configuration information for multiple frequency positions and / or multiple bandwidths for the initial downlink BWPs is broadcast in a cell), some of the information included in genericParameters in initialDownlinkBWP may be parameters common to the multiple initial downlink BWPs (or configuration information for multiple frequency positions and / or multiple bandwidths of the initial downlink BWPs).

[0094] The information element BWP of the parameter genericParameters specifies the frequency location and bandwidth of the corresponding BWP. The information element BWP may include a parameter indicating the subcarrier spacing used in the corresponding BWP, a parameter locationAndBandwidth indicating the location and bandwidth (total number of resource blocks) of the corresponding BWP in the frequency domain, and / or a parameter cyclicPrefix indicating whether a standard CP (cyclic prefix) or an extended CP is used in the corresponding BWP. In other words, the corresponding BWP may be defined by the subcarrier spacing, the CP, and the location and bandwidth in the frequency domain. However, the value indicated by locationAndBandwidth may be interpreted as a resource indicator value (RIV). The resource indicator value indicates the starting PRB index and the number of consecutive PRBs of the corresponding BWP. However, the first PRB defining the region of the resource indicator value may be a PRB determined by the subcarrier spacing given by subcarrierSpacing of the corresponding BWP and the offsetToCarrier set in SCS-SpecificCarrier included in FrequencyInfoDL (or FrequencyInfoDL-SIB) or FrequencyInfoUL (or FrequencyInfoUL-SIB) corresponding to the subcarrier spacing. Also, the size defining the region of the resource indicator value may be 275. The subcarrier spacing of the initial downlink BWP indicated by subcarrierSpacing included in genericParameters in initialDownlinkBWP may be set to be the same value as the subcarrier spacing indicated by the MIB of the same cell. If cyclicPrefix is ​​not included (not set) in genericParameters, the terminal device 1 may use a standard CP instead of an extended CP.

[0095] frequencyInfoDL is a set of frequencyBandList, which indicates a list of one or more frequency bands to which the downlink carrier belongs, and parameters related to the carrier for each subcarrier interval. The frequencyInfoUL may include a frequencyBandList indicating a list of one or more frequency bands to which the uplink carrier belongs and a list of SCS-SpecificCarriers indicating a set of parameters related to the carrier for each subcarrier spacing.

[0096] SCS-SpecificCarrier is a parameter that indicates the actual carrier location, bandwidth, and carrier bandwidth. The parameter may include a subcarrierSpacing parameter. More specifically, an information element SCS-SpecificCarrier in frequencyInfoDL indicates the configuration for a specific carrier and includes subcarrierSpacing, carrierbandwidth, and / or offsetToCarrier. subcarrierSpacing is a parameter indicating the subcarrier spacing of the carrier (for example, 15 kHz or 30 kHz for FR1, and 60 kHz or 120 kHz for FR2). carrierbandwidth is a parameter indicating the bandwidth of the carrier in terms of the number of PRBs (Physical Resource Blocks). offsetToCarrier is a parameter indicating the offset in the frequency domain between reference point A (the lowest subcarrier of common RB0) and the lowest usable subcarrier of the carrier in terms of the number of PRBs (where the subcarrier spacing is the subcarrier spacing of the carrier given by subcarrierSpacing). For example, for a downlink carrier, its carrier bandwidth is given by the upper layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier spacing, and its starting position on the frequency is given by the parameter offsetToCarrier in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier spacing.For example, for an uplink carrier, its carrier bandwidth is given by the upper layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoUL for each subcarrier spacing, and its starting position on the frequency is given by the parameter offsetToCarrier in SCS-SpecificCarrier in frequencyInfoUL for each subcarrier spacing.

[0097] If neither initialDownlinkBWP nor separateInitialDownlinkBWP is provided (set) in SIB1 (or may be another SIB or RRC parameter) received by the terminal device 1 (this may be the case if initialDownlinkBWP is not provided (set) in either downlinkConfigCommon or downlinkConfigCommonRedCap in SIB1 received by the terminal device 1), the terminal device 1 may determine / identify the initial downlink BWP based on the position and number of consecutive PRBs starting from the PRB with the lowest index and ending with the PRB with the highest index among the PRBs (Physical Resource Blocks) in the CORESET (such as CORESET#0) of the Type0-PDCCH CSS Set, and the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received in the CORESET of the Type0-PDCCH CSS Set. If initialDownlinkBWP (which may be separateInitialDownlinkBWP) is provided in downlinkConfigCommonRedCap in SIB1 received by the terminal device 1, the terminal device 1 may determine / specify the initial downlink BWP by the initialDownlinkBWP. If initialDownlinkBWP (which may be separateInitialDownlinkBWP) is not provided / set in downlinkConfigCommonRedCap in SIB1 received by the terminal device 1, and initialDownlinkBWP is provided / set in downlinkConfigCommon in SIB1 received by the terminal device 1, and the terminal device 1 supports the bandwidth of the BWP set in the initialDownlinkBWP, the terminal device 1 may determine / specify the initial downlink BWP by the initialDownlinkBWP.If the initialDownlinkBWP (which may be a separateInitialDownlinkBWP) is not provided / configured in the downlinkConfigCommonRedCap in the SIB1 received by the terminal device 1, and the initialDownlinkBWP is provided / configured in the downlinkConfigCommon in the SIB1 received by the terminal device 1, and the terminal device 1 does not support the bandwidth of the BWP set in the initialDownlinkBWP, the terminal device 1 may determine / identify the initial downlink BWP based on the position and number of consecutive PRBs starting from the PRB with the lowest index and ending with the PRB with the highest index among the PRBs (Physical Resource Blocks) of the CORESET (such as CORESET#0) of the Type0-PDCCH CSS Set, and the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received in the CORESET of the Type0-PDCCH CSS Set.

[0098] However, the provision of initialDownlinkBWP in downlinkConfigCommon does not mean that the RRC parameter The meter receives the initialDownlinkBWP and the RRC connection is established (for example, RRCSetup , RRCResume and / or RRCReestablishment are received). For example, the terminal device 1 receives the initialDownlinkBWP in the downlinkConfigCommon in the SIB1. In this case, CORESET#0 may be the initial downlink BWP until RRCSetup, RRCResume, or RRCReestablishment is received. However, setting CORESET#0 as the initial downlink BWP does not mean that The initial downlink BWP may be determined / specified by the position and number of consecutive PRBs starting from the PRB with the lowest index and ending with the PRB with the highest index among the PRBs in CORESET#0. Determining / specifying the downlink BWP may be determining / specifying the frequency location and / or bandwidth of the initial downlink BWP. When the terminal device 1 receives the initialDownlinkBWP in SIB1, after receiving RRCSetup, RRCResume and / or RRCReestablishment, the terminal device 1 may determine / specify the initial downlink BWP by the locationAndBandwidth included in the received initialDownlinkBWP. When the terminal device 1 receives the initialDownlinkBWP in SIB1, the terminal device 1 may specify the initial downlink BWP by CORESET#0 until the RRC connection is established, and after the RRC connection is established, the terminal device 1 may determine / specify the initial downlink BWP by the locationAndBandwidth included in the initialDownlinkBWP.

[0099] However, the provision of the initialDownlinkBWP (which may be a separateInitialDownlinkBWP) in the downlinkConfigCommonRedCap may mean a state in which the initialDownlinkBWP is received in the RRC parameters. For example, when the terminal device 1 receives the initialDownlinkBWP in the downlinkConfigCommonRedCap in the SIB1, the terminal device 1 may determine / specify the initial downlink BWP by the locationAndBandwidth included in the received initialDownlinkBWP.

[0100] RRCSetup may be a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCSetupRequest message to the base station device 3 (which may be a network). When an RRC connection with the terminal device 1 is established, the base station device 3 (which may be a network) may transmit an RRCSetup message to the terminal device 1.

[0101] RRCResume may be a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCResumeRequest message or an RRCResumeRequest1 message to the base station device 3 (which may be a network). The base station device 3 (which may be a network) may transmit the RRCResume message to the terminal device 1 when the RRC connection with the terminal device 1 is resumed.

[0102] RRCReestablishment may be a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCReestablishmentRequest message to the base station device 3 (which may be a network). When the RRC connection with the terminal device 1 is re-established, the RRCReestablishment message may be transmitted to the terminal device 1.

[0103] The initial uplink BWP may be configured by a parameter provided in an MIB, a parameter provided in SIB1, a parameter provided in an SIB, or an RRC parameter. For example, the initial uplink BWP may be configured by a parameter initialUplinkBWP provided in SIB1. Here, initialUplinkBWP is a parameter indicating a UE-specific (dedicated) setting of the initial uplink BWP for each UE.

[0104] The initial uplink BWP may be defined / configured by the initialUplinkBWP provided in SIB1 (which may be REDCAP SIB1, another SIB, or an RRC parameter). The terminal device 1 may determine the initial uplink BWP based on the initialUplinkBWP provided by the received SIB1. For example, the terminal device 1 may specify settings such as the frequency position and subcarrier spacing of the initial uplink BWP using parameters included in the initialUplinkBWP provided by the received SIB1.

[0105] The terminal device 1 has an antenna and a signal processing unit that processes baseband signals. An RF circuit is provided between the antenna and the filter. The RF circuit mainly comprises a signal processing unit, power amplifier, antenna switch, filter, etc. When receiving a signal, the signal processing unit of the RF circuit demodulates the RF signal received via the filter and outputs the received signal to the signal processing unit. When transmitting a signal, the high-frequency signal processing unit of the RF circuit modulates the carrier signal to generate an RF signal, amplifies the power with the power amplifier, and outputs it to the antenna. The antenna switch connects the antenna and filter when receiving a signal, and connects the antenna and power amplifier when transmitting a signal.

[0106] When the bandwidth of the set initial downlink BWP is wider than the bandwidth supported by the RF circuit of the terminal device 1 (which may be referred to as allocated bandwidth), the terminal device 1 The frequency band to which the circuit is applied may be tuned / retuned. Adjusting / re-adjusting the frequency band to be used may be referred to as RF tuning / RF retuning. FIG. 7 is a diagram showing an example of RF retuning. In FIG. 7, when the applicable band of the RF circuit used in the terminal device 1 is outside the band of the downlink channel received in the initial downlink BWP, the terminal device 1 performs RF retuning so that the applicable band of the RF circuit includes the band of the downlink channel to be received. When the bandwidth of the set initial uplink BWP is wider than the bandwidth supported by the RF circuit included in the terminal device 1 (which may be referred to as allocated bandwidth), the terminal device 1 may adjust / re-adjust (tuning / retuning) the frequency band to be used by the RF circuit in the initial uplink BWP. When the bandwidth of the set downlink BWP is wider than the bandwidth supported by the RF circuit included in the terminal device 1 (which may be referred to as allocated bandwidth), the terminal device 1 may adjust / re-adjust the frequency band to be used by the RF circuit in the downlink BWP. If the bandwidth of the set initial uplink BWP is wider than the bandwidth supported by the RF circuit of the terminal device 1 (which may be referred to as the allocated bandwidth), the terminal device 1 may adjust / readjust the frequency band to which the RF circuit is applied within the uplink BWP.

[0107] The terminal device 1 according to the present invention receives / specifies configuration information of the initial downlink BWP by the higher layer parameter initialDownlinkBWP in downlinkConfigCommon or the higher layer parameter initialDownlinkBWP in downlinkConfigCommonRedCap. However, the initialDownlinkBWP may be included in SIB1 or any RRC message. For example, the configuration information of the initial downlink BWP may include information indicating the frequency location and bandwidth of the initial downlink BWP. The terminal device 1 may receive SIB1 or any RRC signaling including multiple pieces of configuration information of the initial downlink BWP. Multiple pieces of configuration information of the initial downlink BWP may be included in one parameter initialDownlinkBWP.

[0108] The pdcch-ConfigCommon (which may be referred to as pdcch-ConfigCommonRedCap) that may be included in the initialDownlinkBWP in downlinkConfigCommon and the pdcch-ConfigCommon that may be included in the initialDownlinkBWP in downlinkConfigCommonRedCap include the parameter controlResourceSetZero of CORESET#0 used in the common search space or UE specific search space, the parameter commonControlResourceSet of the additional common CORESET used in the common search space or UE specific search space, the parameter commonControlResourceSet of the common search space 0 (common search space #0), a parameter commonSearchSpaceList indicating a list of common search spaces other than common search space 0, a parameter searchSpaceSIB1 indicating the ID of the search space for SIB1 messages, a parameter searchSpaceOtherSystemInformation indicating the ID of the search space for other system information, a parameter pagingSearchSpace indicating the ID of the search space for paging, and / or a parameter ra-SearchSpace indicating the ID of the search space for random access procedures. However, pdcch-ConfigCommon (pdcch-ConfigCommonRedCap) that may be included in initialDownlinkBWP within downlinkConfigCommonRedCap may not always include controlResourceSetZero.

[0109] The information element (IE) ControlResourceSetZero indicated by controlResourceSetZero is set to any value between 0 and 15. However, the number of values ​​that can be set to ControlResourceSetZero may be other than 16, for example, 32. The information element SearchSpaceZero indicated by searchSpaceZero is set to any value between 0 and 15. However, the number of values ​​that can be set to SearchSpaceZero may be other than 16, for example, 32.

[0110] The terminal device 1 determines the number of consecutive resource blocks and the number of consecutive symbols for CORESET#0 from controlResourceSetZero in pdcch-ConfigCommon. However, the value indicated by controlResourceSetZero is applied as an index to a predetermined table. However, the terminal device 1 may determine the table to be applied based on the supported UE category and / or UE capability. However, the terminal device 1 may determine the table to be applied based on the minimum channel bandwidth. However, the terminal device 1 may determine the table to be applied based on the subcarrier spacing of the SS / PBCH block and / or the subcarrier spacing of CORESET#0. Each row of the table to which the value of controlResourceSetZero is applied as an index may indicate the index indicated by controlResourceSetZero, the multiplexing pattern of PBCH and CORESET, the number of RBs (which may be PRBs) of CORESET#0, the number of symbols of CORESET#0, the offset and / or the number of PDCCH repetitions.

[0111] The commonSearchSpaceList is a parameter indicating a list of additional common search spaces (CSSs), and sets common search spaces whose search space ID is other than 0. The parameter SearchSpace included in the commonSearchSpaceList includes at least a parameter searchSpaceId indicating a search space ID used to identify a search space, and may further include a parameter controlResourceSetId indicating a CORESET ID used to identify one CORESET in the serving cell.

[0112] The searchSpaceSIB1 includes an information element SearchSpaceId indicating the ID of a search space for the SIB1 message. The terminal device 1 may identify a CSS used to monitor a PDCCH that schedules a PDSCH that includes the SIB1 message, and may further identify a CORESET used to monitor a PDCCH that schedules the SIB1 message and a setting (for example, a frequency position) of the CORESET.

[0113] The searchSpaceOtherSystemInformation includes an information element SearchSpaceId indicating an ID of a search space for other system information (OSI). The terminal device 1 may identify a CSS used to monitor a PDCCH that schedules a PDSCH that includes OSI, and further identify a CORESET used to monitor a PDCCH that schedules a PDSCH that includes OSI and a setting (for example, a frequency position) of the CORESET, from the ID of the search space indicated by the searchSpaceOtherSystemInformation and the list of common search spaces indicated by the commonSearchSpaceList.

[0114] The pagingSearchSpace includes an information element SearchSpaceId indicating the ID of a search space for paging. The terminal device 1 may identify a CSS used to monitor a PDCCH that schedules a PDSCH that includes paging information, and may further identify a CORESET used to monitor a PDCCH that schedules a PDSCH that includes paging information and a setting (for example, a frequency position) of the CORESET, from the ID of the search space indicated by the pagingSearchSpace and the list of common search spaces indicated by the commonSearchSpaceList.

[0115] ra-SearchSpace includes an information element SearchSpaceId indicating the ID of a search space for a random access procedure. The terminal device 1 determines the ID of the search space indicated by ra-SearchSpace and the list of common search spaces indicated by commonSearchSpaceList. It is also possible to specify a CSS to be used to monitor a PDCCH that schedules a PDSCH that includes a RAR, and further specify a CORESET to be used to monitor a PDCCH that schedules a PDSCH that includes an RAR and the setting (e.g., frequency location) of the CORESET.

[0116] The multiplexing pattern of PBCH and CORESET corresponds to the SS / PBCH block corresponding to the PBCH where the MIB is detected. This shows the relationship pattern of the frequency / time position of the corresponding CORESET#0. For example, when the multiplexing pattern of PBCH and CORESET is 1, PBCH and CORESET#0 are time-multiplexed in different symbols.

[0117] The number of RBs in CORESET#0 indicates the number of resource blocks that are consecutively allocated to CORESET#0. The number of symbols in CORESET#0 indicates the number of symbols that are consecutively allocated to CORESET#0.

[0118] The above offset is the minimum RB index of the resource blocks allocated to CORESET#0. The first resource block of the corresponding REDCAP PBCH overlaps with the common resource block Indicates the offset to the lowest RB index of the block, where the offset is CORESET#0 The corresponding SS / PBCH block is selected from the lowest RB index of the resource block allocated to the The first resource block of the block may indicate an offset to the lowest RB index of the overlapping common resource block.

[0119] The terminal device 1 receives the initialDownlinkBWP (or separateInitialDownlinkBWP) including the RRC parameter pdcch-ConfigCommon via SIB1, other SIBs, or RRC signaling, and monitors the PDCCH based on the parameter.

[0120] The terminal device 1 determines whether a PDCCH monitoring opportunity is available from searchSpaceZero in pdcch-ConfigCommon. However, the value indicated by searchSpaceZero is used as an index to determine the However, the terminal device 1 may determine the table to be applied based on the supported UE category and / or UE capability. However, the terminal device 1 may determine the table to be applied based on the frequency range.

[0121] The terminal device 1 performs a type 0-PDCCH common search over two consecutive slots starting from slot n0. The terminal device 1 monitors the PDCCH with the space set (Type0-PDCCH CSS Set). In the SS / PBCH block with a value of i, n0 and the system frame number are determined based on the parameters O and M shown in the table.

[0122] Multiple "frequency locations and bandwidths" for multiple initial downlink BWPs in a cell " is set (this may be the case when multiple initial downlink BWPs are set in a certain cell), pdcch-ConfigCommon that may be included in initialDownlinkBWP in downlinkConfigCommon or each parameter of the pdcch-ConfigCommon may be a cell-specific parameter of the PDCCH in the initial downlink BWP set by initialDownlinkBWP in downlinkConfigCommon, or may be a cell-specific parameter of the PDCCH that is common to the initial downlink BWP set by initialDownlinkBWP in downlinkConfigCommon and the initial downlink BWP set by separateInitialDownlinkBWP in downlinkConfigCommonRedCap.

[0123] The pdsch-ConfigCommon (which may be referred to as PDSCH-ConfigCommon) that may be included in the initialDownlinkBWP in downlinkConfigCommon and the pdsch-ConfigCommon (which may be referred to as PDSCH-ConfigCommon, pdsch-ConfigCommonRedCap, or PDSCH-ConfigCommonRedCap) that may be included in the separateInitialDownlinkBWP in downlinkConfigCommonRedCap may include a parameter pdsch-TimeDomainAllocationList that indicates a list of time domain configurations for the timing of downlink allocation for downlink data.

[0124] Indicates multiple "frequency locations and bandwidths" for the initial downlink BWP in a cell. When the parameters (locationAndBandwidth in initialDownlinkBWP in downlinkConfigCommon and locationAndBandwidth in separateInitialDownlinkBWP in downlinkConfigCommonRedCap) are set (when multiple initial downlink BWPs are set in a cell), In this case, pdsch-ConfigCommon or each parameter of pdsch-ConfigCommon that may be included in initialDownlinkBWP in downlinkConfigCommon may be a cell-specific parameter of a PDSCH in the initial downlink BWP set by initialDownlinkBWP in downlinkConfigCommon, or may be a cell-specific parameter of a PDSCH that is common to the initial downlink BWP set by initialDownlinkBWP in downlinkConfigCommon and the initial downlink BWP set by separateInitialDownlinkBWP in downlinkConfigCommonRedCap.

[0125] A terminal device 1 that does not support the frequency position and / or bandwidth of the initial downlink BWP (first initial downlink BWP) set by initialDownlinkBWP in downlinkConfigCommon can receive the downlink channel and downlink signal transmitted from the base station device 3 by identifying / determining the initial downlink BWP (second initial downlink BWP) set by separateInitialDownlinkBWP in downlinkConfigCommonRedCap, which may be included in SIB1 (or another SIB, or may be RRC signaling).

[0126] When the base station device 3 sets an initial downlink BWP of a frequency location and / or bandwidth that is not supported by a specific terminal device 1 in locationAndBandwidth in downlinkConfigCommon, By setting the initial downlink BWP of the frequency position and / or bandwidth supported by the terminal device 1 by locationAndBandwidth in downlinkConfigCommonRedCap, it is possible to appropriately transmit downlink channels and downlink signals. By including locationAndBandwidth in downlinkConfigCommonRedCap in SIB1 (which may be another SIB or RRC signaling), the base station device 3 can transmit downlink channels and reference signals corresponding to the second initial downlink BWP to terminal devices 1 that do not support the frequency position and / or bandwidth of the first initial downlink BWP, and can transmit downlink channels and reference signals corresponding to the first initial downlink BWP to terminal devices 1 that support the frequency position and bandwidth of the first initial downlink BWP. When setting the initial downlink BWP of the frequency position and / or bandwidth supported by all terminal devices 1 by locationAndBandwidth in initialDownlinkBWP, the base station device 3 does not need to include locationAndBandwidth in downlinkConfigCommonRedCap in SIB1 (which may be another SIB or RRC signaling).

[0127] The terminal device 1 may specify / determine the subcarrier spacing used for all channels and reference signals in the initial downlink BWP by using subcarrierSpacing included in genericParameters in initialDownlinkBWP in downlinkConfigCommon, regardless of whether locationAndBandwidth is included in downlinkConfigCommonRedCap in SIB1 (which may be another SIB or RRC signaling).The terminal device 1 may specify / determine whether an extended cyclic prefix CP is used in the initial downlink BWP by using cyclicPrefix included in genericParameters in initialDownlinkBWP in downlinkConfigCommon, regardless of whether locationAndBandwidth is included in downlinkConfigCommonRedCap in SIB1 (which may be another SIB or RRC signaling).

[0128] The terminal device 1 may identify / determine cell-specific parameters of the PDCCH in the initial downlink BWP using pdcch-ConfigCommon included in initialDownlinkBWP in downlinkConfigCommon, regardless of whether locationAndBandwidth is included in downlinkConfigCommonRedCap in SIB1 (which may be another SIB or RRC signaling), and monitor / receive the PDCCH. The terminal device 1 may identify / determine cell-specific parameters of the PDSCH in the initial downlink BWP using pdsch-ConfigCommon included in initialDownlinkBWP in downlinkConfigCommon, regardless of whether locationAndBandwidth is included in downlinkConfigCommonRedCap in SIB1 (which may be another SIB or RRC signaling), and receive the PDSCH.

[0129] When the terminal device 1 receives locationAndBandwidth included in downlinkConfigCommonRedCap in SIB1 (or another SIB) and specifies / determines the frequency location and bandwidth of the initial downlink BWP (which may be referred to as a separate initial downlink BWP) based on the locationAndBandwidth, CORESET#0 may be used as the initial downlink BWP until the RRC connection is established, re-established, or resumed (for example, before receiving RRCSetup, RRCResume, or RRCReestablishment), and after the RRC connection is established, the initial downlink BWP may be determined / specified using locationAndBandwidth included in downlinkConfigCommonRedCap in the received SIB1 (or another SIB). However, when the initial downlink BWP is set to CORESET#0 until the RRC connection is established, re-established, or resumed, the terminal device 1 may perform a random access procedure using the initial downlink BWP determined / specified using CORESET#0.

[0130] When the terminal device 1 receives locationAndBandwidth included in downlinkConfigCommonRedCap in SIB1 (which may be another SIB) and specifies / determines the frequency location and bandwidth of an initial downlink BWP (which may be referred to as a separate initial downlink BWP) based on the locationAndBandwidth, CORESET#0 is used as the initial downlink BWP until the SIB1 is received, and after SIB1 (which may be another SIB) is received, the initial downlink BWP may be determined / specified by locationAndBandwidth included in downlinkConfigCommonRedCap in the received SIB1. However, when the initial downlink BWP is determined / specified by locationAndBandwidth in downlinkConfigCommonRedCap at the time of receiving SIB1 (which may be another SIB), the terminal device 1 may perform a random access procedure using the initial downlink BWP determined / specified by the locationAndBandwidth.

[0131] Based on information included in SIB1 (or another SIB), the terminal device 1 may switch the timing for determining / specifying an initial downlink BWP (which may be referred to as a separate initial downlink BWP) based on locationAndBandwidth included in downlinkConfigCommonRedCap in the SIB1. The parameter initialBwpTiming indicating the timing for applying locationAndBandwidth included in downlinkConfigCommonRedCap in SIB1 (or another SIB) may be 1-bit information.

[0132] In a certain cell, SIB1 is received in a certain initial downlink BWP (first initial downlink BWP). When a separate initial downlink BWP (second initial downlink BWP) having a frequency position and / or bandwidth different from that of the first initial downlink BWP is set, The bandwidth of the rate initial downlink BWP is determined by the synchronization rate of the first signal transmitted within the bandwidth of the initial downlink BWP. May not contain signal blocks. Separate initial downlink BWP for paging, la If a signal serving as a synchronization signal block is required for random access and / or other purposes, an additional synchronization signal block (hereinafter referred to as a synchronization signal block) may be provided within the band of the separate initial downlink BWP. The base station device 3 may transmit an additional synchronization signal block (SSB) thereafter. The base station device 3 is specified / determined by the locationAndBandwidth in the downlinkConfigCommonRedCap. Additional synchronization signal block within the band of the second initial downlink BWP (separate initial downlink BWP) The terminal device 1 may transmit an additional synchronization signal block transmitted within the band of the separate initial downlink BWP specified / determined from the locationAndBandwidth in downlinkConfigCommonRedCap. The additional synchronization signal block may be a synchronization signal block (referred to as NCD-SSB: Non-Cell Defining SSB) that is not a synchronization signal block that defines a cell (referred to as CD-SSB: Cell Defining SSB). For example, the additional synchronization signal block may not have a center frequency that is the synchronization raster.

[0133] FIG. 8 is a diagram showing an outline of the frequency position of the additional synchronization signal block according to this embodiment. In FIG. 8, two initial downlink BWPs, an initial DL BWP and a separate initial DL BWP, are configured in a certain cell. However, the initial downlink BWP may be the band of CORESET#0. In FIG. 8, The downlink BWP includes at least the synchronization signal block (SSB), CORESET#0, and SIB1 in the band. In FIG. 8, the separate initial downlink BWP includes at least an additional synchronization signal block (additional SSB) within the band. The terminal device 1 that receives the synchronization signal block identifies the frequency location of CORESET#0, and identifies the frequency location and time location of the PDSCH that includes SIB1 using the PDCCH received in CORESET#0. The terminal device 1 that receives the PDSCH that includes SIB1 identifies / determines the frequency location (including bandwidth) of the separate initial downlink BWP using the parameter locationAndBandwidth included in downlinkConfigCommonRedCap in SIB1 (or may be another SIB identified by SIB1). Separate The terminal device 1 that has specified / determined the frequency position of the initial downlink BWP is included in downlinkConfigCommonRedCap in SIB1 (or may be another SIB specified by the SIB1). The parameter ssbFrequencyOffset-rc may be used to identify / determine the frequency location of the additional synchronization signal block transmitted within the separate initial downlink BWP and receive the additional synchronization signal block.

[0134] The terminal device 1 uses DCI format 1_0, DCI format 1_1, or DCI format 1_2. By detecting the PDCCH including the PDCCH, the terminal device 1 may decode (receive) the corresponding PDSCH. The corresponding PDSCH is scheduled (indicated) by its DCI format (DCI). The start position (start symbol) of the scheduled PDSCH is referred to as S. The start symbol S of the PDSCH may be the first symbol to which the PDSCH is transmitted (mapped) in a slot. The start symbol S corresponds to the beginning of the slot. For example, if the value of S is 0, the terminal device 1 may receive the PDSCH from the first symbol in a slot. Also, for example, if the value of S is 2, the terminal device 1 may receive the PDSCH from the third symbol in a slot. The number of consecutive symbols of the scheduled PDSCH is referred to as L. The number L of consecutive symbols is counted from the start symbol S. The determination of S and L assigned to the PDSCH will be described later.

[0135] PDSCH mapping types include PDSCH mapping type A and PDSCH mapping type B. For PDSCH mapping type A, S takes a value from 0 to 3. L takes a value from 3 to 14. However, the sum of S and L takes a value from 3 to 14. In PDSCH mapping type B, S is 0 to S takes a value from 1 to 12. L takes a value from {2, 4, 7}. However, the sum of S and L takes a value from 2 to 14.

[0136] The location of the DMRS symbols for the PDSCH depends on the type of PDSCH mapping. The position of the first DM-RS symbol for the PDSCH depends on the type of PDSCH mapping. It depends on the type of PDSCH mapping. For PDSCH mapping type A, the position of the first DMRS symbol may be indicated by the higher layer parameter dmrs-TypeA-Position. That is, the higher layer parameter dmrs-TypeA-Position is used to indicate the position of the first DMRS symbol for the PDSCH or PUSCH. dmrs-TypeA-Position may be set to either 'pos2' or 'pos3'. For example, if dmrs-TypeA-Position is set to 'pos2', the position of the first DMRS symbol for the PDSCH may be the third symbol in the slot. For example, if dmrs-TypeA-Position is set to 'pos3', the position of the first DMRS symbol for the PDSCH may be the fourth symbol in the slot. Here, S can take the value 3 only if dmrs-TypeA-Position is set to 'pos3'. That is, if dmrs-TypeA-Position is set to 'pos2', S takes the value from 0 to 2. In PDSCH mapping type B, the location of the first DMRS symbol is the first symbol of the assigned PDSCH.

[0137] 9A and 9B are diagrams showing examples of PDSCH mapping types according to this embodiment. 9(A) is a diagram showing an example of mapping type A. In FIG. 9(A), S of the allocated PDSCH is 3. L of the allocated PDSCH is 7. In FIG. 9(A), the position of the first DMRS symbol for the PDSCH is the fourth symbol in the slot. That is, dmrs-TypeA-Position is set to 'pos3'. FIG. 9(B) is a diagram showing an example of PDSCH mapping type A. In FIG. 9(B), S of the allocated PDSCH is 4. L of the allocated PDSCH is 4. In FIG. 9(B), the position of the first DMRS symbol for the PDSCH is the first symbol to which the PDSCH is allocated.

[0138] The random access procedure of this embodiment will now be described.

[0139] Random access procedures are classified into two procedures: contention-based (CB) and non-CB (also called contention-free). Dumb access is also called CBRA, and non-contention based random access is also called CFRA.

[0140] The random access procedure is initiated by a PDCCH order, a MAC entity, a beam failure notification from a lower layer, or RRC, etc.

[0141] The contention-based random access procedure is initiated by a PDCCH order, a MAC entity, a beam failure notification from a lower layer, or RRC, etc. A beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1. When a beam failure notification is provided, if certain conditions are met, the MAC entity of the terminal device 1 initiates a random access procedure. When provided by the physical layer, the procedure for determining whether certain conditions are met and initiating the random access procedure may be referred to as a beam failure recovery procedure. This random access procedure is a random access procedure for a beam failure recovery request. The random access procedure initiated by the entity includes a random access procedure initiated by a scheduling request procedure. The random access procedure for a beam failure recovery request is considered a random access procedure initiated by a MAC entity. Random access procedures for beam failure recovery requests and random access initiated by scheduling request procedures Since different procedures may be used for access procedures, a distinction may be made between a random access procedure for beam failure recovery requests and a scheduling request procedure, which may be a random access procedure initiated by a MAC entity. In one embodiment, a random access procedure initiated by a scheduling request procedure is referred to as a MAC entity initiated random access procedure, and a beam loss The random access procedure for a beam failure recovery request may be referred to as a random access procedure based on a beam failure notification from a lower layer. Hereinafter, the start of the random access procedure when a beam failure notification is received from a lower layer may refer to the start of the random access procedure for a beam failure recovery request.

[0142] The terminal device 1 performs a contention-based random access procedure when making an initial access from a state where it is not connected (communicating) with the base station device 3, and / or when making a scheduling request when uplink data or sidelink data that can be transmitted to the terminal device 1 occurs while the terminal device 1 is connected to the base station device 3. However, the use of contention-based random access is not limited to these.

[0143] The non-contention based random access procedure may be initiated when the terminal device 1 receives information instructing the start of the random access procedure from the base station device 3. The non-contention based random access procedure may be initiated when the MAC layer of the terminal device 1 receives a beam failure notification from a lower layer.

[0144] Non-contention based random access is a method for quickly connecting the base station device 3 and the terminal device 1 when handover or transmission timing of the mobile station device is not valid, and the base station device 3 and the terminal device 1 are connected. This may be used to achieve uplink synchronization between the device 3. The access sends a beam failure recovery request when a beam failure occurs in the terminal device 1. However, the applications of non-contention based random access are not limited to these.

[0145] However, the information indicating the start of the random access procedure may also be referred to as message 0, Msg.0, NR-PDCCH order, PDCCH order, etc.

[0146] The terminal device 1 of this embodiment receives the random access request from an upper layer before initiating the random access procedure. The random access setting information is received via the

[0147] The base station device 3 transmits to the terminal device 1 RRC parameters including random access setting information. is transmitted to the terminal device 1 as an RRC message.

[0148] The terminal device 1 may select one or more available random access preambles and / or one or more available physical random access channel (PRACH) opportunities (which may also be referred to as random access channel (RACH) opportunities, PRACH transmission opportunities, or RACH transmission opportunities) to be used for the random access procedure based on propagation path characteristics between the terminal device 1 and the base station device 3. The terminal device 1 may select one or more available random access preambles and / or one or more PRACH opportunities to be used for the random access procedure based on propagation path characteristics (which may be, for example, reference signal received power (RSRP)) measured using a reference signal (for example, SS / PBCH block and / or CSI-RS) received from the base station device 3.

[0149] The random access procedure is realized by transmitting and receiving multiple types of messages between the terminal device 1 and the base station device 3. For example, in a four-step random access, the following four messages are transmitted: Reception is performed.

[0150] <Message 1> The terminal device 1 in which transmittable uplink data or transmittable sidelink data has occurred transmits a preamble (random access preamble) for random access to the base station device 3 via PRACH. The random access preamble may be called message 1 or Msg1. The information is transmitted to the base station device 3 by a sequence of numbers. For example, 64 types If a sequence of this kind is available, 6 bits of information can be indicated to the base station device 3. This information is indicated as a Random Access Preamble Identifier. The preamble sequence is selected from a set of preamble sequences using a preamble index. The selected random access preamble is transmitted on the designated PRACH resource.

[0151] <Message 2> Upon receiving the random access preamble, the base station device 3 sends a random access response (RAR) including an uplink grant to instruct the terminal device 1 to perform transmission. ), and transmits the generated random access response to the terminal device 1 on the PDSCH. The random access response may also be referred to as message 2 or Msg2. Furthermore, the base station device 3 calculates a transmission timing difference between the terminal device 1 and the base station device 3 from the received random access preamble, and includes in message 2 transmission timing adjustment information (Timing Advance Command) for adjusting the difference. Furthermore, the base station device 3 includes in message 2 a random access preamble identifier corresponding to the received random access preamble. Furthermore, the base station device 3 transmits, on the PDCCH, DCI to which a CRC scrambled with RA-RNTI (Random Access Response Identification Information: Random Access-Radio Network Temporary Identity) is added, in order to indicate that the random access response is addressed to the terminal device 1 that transmitted the random access preamble. The RA-RNTI is determined according to the frequency and time location information of the PRACH that transmitted the random access preamble.

[0152] <Message 3> The terminal device 1 that transmitted the random access preamble Within a period of several subframes (called the RAR window) after the random access transmission, the PDCCH is monitored for a random access response identified by the RA-RNTI. When the terminal device 1 that transmitted the preamble detects the corresponding RA-RNTI, it transmits the preamble to the PDSCH. The terminal device 1 that has successfully decoded the random access response sends the random access response a random access preamble corresponding to the random access preamble that it transmitted. If the random access preamble identifier is included, the terminal device 1 corrects the synchronization error using the transmission timing adjustment information indicated in the random access response. The uplink grant included in the response is used to transmit the data stored in the buffer to the base station device 3. The data transmitted using the uplink grant at this time is referred to as message 3 or Msg3.

[0153] In addition, the terminal device 1 receives a random access response that has been successfully decoded as a series of random access If this is the first successful reception in the procedure, the terminal device The received signal includes information (C-RNTI) for identifying base station device 1 and is transmitted to base station device 3.

[0154] <Message 4> The base station device 3 sends a random access response to the message 3 of the terminal device 1. When receiving an uplink transmission on the resource, the C-RNTI MAC CE included in the received message 3 Then, when establishing a connection with the terminal device 1, the base station device 3 transmits a PDCCH addressed to the detected C-RNTI. When transmitting a PDCCH addressed to the detected C-RNTI, the base station device 3 The PDCCH includes an uplink grant. These PDCCHs transmitted by the base station device 3 are messages. This is called Message 4, Msg4 or Contention Resolution Message.

[0155] The terminal device 1 that transmitted the message 3 starts a contention resolution timer that determines the period for monitoring the message 4 from the base station device 3, and attempts to receive the PDCCH transmitted from the base station within the timer. The terminal device 1 that transmitted the C-RNTI MAC CE in the message 3 receives the PDCCH addressed to the transmitted C-RNTI from the base station device 3, and sets the PDCCH for new transmission. If the uplink grant for the UE 1 is included, contention resolution with other UE 1 is performed. The terminal device 1 determines that the contention resolution was successful, stops the contention resolution timer, and ends the random access procedure. If the reception of the PDCCH addressed to the C-RNTI transmitted by its own device in message 3 cannot be confirmed within the timer period, it determines that the contention resolution was not successful, and the terminal device 1 transmits a random access preamble again and continues the random access procedure. However, if the transmission of the random access preamble is repeated a predetermined number of times and contention resolution is not successful, it determines that there is a problem with the random access and notifies the upper layer of the random access problem. For example, the upper layer may reset the MAC entity based on the random access problem. If the upper layer requests a reset of the MAC entity, the terminal device 1 stops the random access procedure.

[0156] By transmitting and receiving the above four messages, the terminal device 1 synchronizes with the base station device 3 and It is possible to transmit uplink data to the base station device 3. However, two-step random access may be used, in which the four messages are shortened and the terminal device 1 and base station device 3 are synchronized by transmitting and receiving two messages, message A and message B.

[0157] A method for identifying PDSCH time domain resource allocation will now be described.

[0158] The base station apparatus 3 may schedule the terminal apparatus 1 to receive the PDSCH by using DCI. The terminal apparatus 1 may receive the PDSCH by detecting DCI addressed to the terminal apparatus 1. When identifying the PDSCH time domain resource allocation, the terminal apparatus 1 determines a resource allocation table to be applied to the PDSCH. The resource allocation table includes one or more PDSCH time domain resource allocation configurations. The terminal apparatus 1 may select one PDSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the 'Time domain resource assignment' (TDRA) field included in the DCI that schedules the PDSCH. In other words, the base station apparatus 3 may schedule the terminal apparatus 1 to receive the PDSCH by detecting DCI addressed to the terminal apparatus 1. The terminal device 1 determines a PDSCH resource allocation for the terminal device 1, generates a TDRA field with a value based on the determined resource allocation, and transmits DCI including the TDRA field to the terminal device 1. The TDRA field value included in the received DCI and the TDRA field value and time domain resource The PDSCH time domain resource is identified using a PDSCH time domain resource allocation configuration that indicates the correspondence between the PDSCH time domain resource and the PDSCH time domain resource.

[0159] FIG. 10 shows a resource allocation scheme applied to PDSCH time domain resource allocation according to an embodiment of the present invention. 10 is a diagram showing an example of a selection criterion for a table. The terminal device 1 selects a table based on the table shown in FIG. Based on the above, a resource allocation table to be applied to PDSCH time domain resource allocation may be determined. The base station device 3 may determine the resource allocation table to be applied to the PDSCH time domain resource allocation based on the table shown in FIG. 10. The resource allocation table may be one or more. In this embodiment, the resource allocation table includes the configuration of a number of PDSCH time domain resource allocations. The tables are classified into (I) predefined resource allocation tables, and (II) resource allocation tables configured from higher layer RRC signaling. The predefined resource allocation tables are called default tables, e.g., default PDSCH time domain resource allocation A, default PDSCH time domain resource allocation B, default PDSCH time domain resource allocation C, default PDSCH time domain resource allocation D, default PDSCH time domain resource allocation E, default PDSCH time domain resource allocation F, default PDSCH time domain resource allocation H, default PDSCH time domain resource allocation I, default The default PDSCH time domain resource allocations are defined as a default PDSCH time domain resource allocation B and a default PDSCH time domain resource allocation C. A default PDSCH time domain resource allocation D different from the default PDSCH time domain resource allocation A may also be defined. Hereinafter, the default PDSCH time domain resource allocation A will be referred to as default table A, the default PDSCH time domain resource allocation B as default table B, the default PDSCH time domain resource allocation C as default table C, and the default PDSCH time domain resource allocation D as default table D. However, different default tables may be defined for when the CP (Cyclic prefix) assigned to the PDSCH is a normal CP (NCP) and when it is an extended CP (ECP). Unless otherwise specified, the default table may be a table for when the CP (Cyclic prefix) assigned to the DSCH is a normal CP (NCP).

[0160] FIG. 11 is a diagram showing an example of a default table A according to this embodiment. FIG. 13 is a diagram showing an example of a default table B according to the present embodiment. 11 shows an example of default table C. In the example of FIG. 11, the number of rows in default table A is 16, and each row indicates a PDSCH time domain resource allocation setting. In FIG. 11, each row indicates a PDSCH mapping type, a slot offset K0 between a PDCCH including DCI and a PDSCH scheduled by the PDCCH, a start symbol S of the PDSCH in the slot, and a number L of consecutive allocated symbols. Define

[0161] The resource allocation table configured by the higher layer RRC signal is provided by the higher layer signal pdsch-TimeDomainAllocationList. pdsch-TimeDomainAllocationList includes one or more information elements PDSCH-TimeDomainResourceAllocation. PDSCH-TimeDomainResourceAllocation indicates the configuration of PDSCH time domain resource allocation. PDSCH-TimeDomainResourceAllocation may be used to configure the time domain relationship between a PDCCH including DCI and a PDSCH scheduled by the PDCCH. pdsch-TimeDomainAllocationList is a list including one or more information elements. One PDSCH-TimeDomainResourceAllocation may be referred to as one entry (or one row). For example, pdsch-TimeDomainAllocationList may include up to 16 entries, and any one entry may be used depending on the 4-bit TDRA field included in DCI. However, the number of entries included in the pdsch-TimeDomainAllocationList may be different, and the number of bits of the TDRA field included in the DCI may be different. Each entry of the pdsch-TimeDomainAllocationList may indicate K0, mappingType, and / or startSymbolAndLength. K0 indicates the slot offset between the PDCCH including the DCI and the PDSCH scheduled by the PDCCH. If K0 is not indicated by the PDSCH-TimeDomainResourceAllocation, the terminal device 1 may assume that the value of K0 is a predetermined value (for example, 0). mappingType indicates whether the mapping type of the corresponding PDSCH is PDSCH mapping type A or PDSCH mapping type B.startSymbolAndLength is an index that gives a valid combination of the start symbol S of the corresponding PDSCH and the number L of consecutive allocated symbols. startSymbolAndLength may also be referred to as a start and length indicator (SLIV). When the SLIV is applied, unlike when a default table is used, the start symbol S and the number L of consecutive symbols of the corresponding PDSCH are given based on the SLIV. The base station device 3 may set the value of the SLIV so that the time domain resource allocation of the PDSCH does not cross a slot boundary.

[0162] FIG. 14 is a diagram illustrating an example of calculating the SLIV.

[0163] In Fig. 14, 14 is the number of symbols contained in one slot. Fig. 14 shows an example of calculating SLIV in the case of NCP (Normal Cyclic Prefix). The value of SLIV is calculated based on the number of symbols contained in the slot, the start symbol S, and the number of consecutive symbols L. Here, the value of L is equal to or greater than 1 and does not exceed (14 - S). When calculating SLIV in ECP, the values ​​7 and 14 in Fig. 14 are replaced by 6 and 12.

[0164] The slot offset K0 will be explained below.

[0165] As mentioned above, in the subcarrier spacing setting μ, the slots are set from 0 to The slots are numbered from 0 to N^{subframe,μ}_{slot}-1 in ascending order, and within a frame they are numbered from 0 to N^{frame,μ}_{slot}-1 in ascending order. K0 is the number of slots based on the PDSCH subcarrier spacing. K0 can take values ​​from 0 to 32. In a subframe or frame, slot numbers are numbered from 0 to 2n in ascending order. Slot number n with a subcarrier spacing setting of 15 kHz corresponds to slot numbers 2n and 2n+1 with a subcarrier spacing setting of 30 kHz.

[0166] When the terminal device 1 detects DCI that schedules a PDSCH, the slot allocated to that PDSCH is floor(n*2 μPDSCH / 2 μPDCCH )+K0. The function floor(A) is given by n is the maximum integer that does not exceed the number of PDCCHs that schedule the PDSCH. It is a slot. μ PDSCH is the subcarrier spacing setting for PDSCH. μ PDCCH is the subcarrier spacing setting for the PDCCH.

[0167] The higher layer signal pdsch-TimeDomainAllocationList may be included in cell-specific RRC parameters pdsch-ConfigCommon in downlinkConfigCommon, cell-specific RRC parameters pdsch-ConfigCommon in downlinkConfigCommonRedCap, and / or user equipment 1 (UE)-specific RRC parameters pdsch-Config. pdsch-ConfigCommon in downlinkConfigCommon or downlinkConfigCommonRedCap is used to configure cell-specific parameters for the PDSCH for a certain downlink BWP. pdsch-Config is used to configure user equipment 1 (UE)-specific parameters for the PDSCH for a certain downlink BWP.

[0168] The terminal device 1 may apply different resource allocation tables to PDSCH time domain resource allocation based on the type (value) of RNTI for scrambling the CRC attached to DCI for scheduling the PDSCH, the type of search space of the PDCCH for receiving the DCI for scheduling the PDSCH, the multiplexing pattern of SS / PBCH blocks and CORESET, the configuration information included in SIB1, the configuration information included in other SIBs, and / or the configuration information included in RRC parameters.The base station device 3 may apply different resource allocation tables to PDSCH time domain resource allocation based on the type (value) of RNTI for scrambling the CRC attached to DCI for scheduling the PDSCH, the type of search space of the PDCCH for receiving the DCI for scheduling the PDSCH, the multiplexing pattern of SS / PBCH blocks and CORESET, the configuration information included in SIB1, the configuration information included in other SIBs, and / or the configuration information included in RRC parameters.

[0169] When the resource allocation table to be applied to PDSCH time domain resource allocation is given by pdsch-TimeDomainAllocationList, different resource allocation tables may be set when the pdsch-TimeDomainAllocationList is included in the cell-specific RRC parameter pdsch-ConfigCommon in downlinkConfigCommon, when it is included in the cell-specific RRC parameter pdsch-ConfigCommon in downlinkConfigCommonRedCap, and when it is included in the terminal device 1 (UE)-specific RRC parameter pdsch-Config. The terminal device 1 may determine the pdsch-TimeDomainAllocationList to be applied to the resource allocation table to be applied to PDSCH time domain resource allocation, based on whether pdsch-TimeDomainAllocationList is included in pdsch-ConfigCommon, pdsch-ConfigCommonRedCap, and / or pdsch-Config.

[0170] For the sake of explanation, in the present invention, the pdsch-TimeDomainAllocationList that can be included in pdsch-ConfigCommon is referred to as pdsch-TimeDomainAllocationList1, the pdsch-TimeDomainAllocationList that can be included in pdsch-ConfigCommonRedCap is referred to as pdsch-TimeDomainAllocationList2, and the pdsch-TimeDomainAllocationList that can be included in pdsch-Config is referred to as pdsch-TimeDomainAllocationList3. It is called.

[0171] Terminal device 1 adds pdsch-TimeDomainAllocationList1 (first parameter) to pdsch-ConfigCommon. It may be determined whether to use pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, pdsch-TimeDomainAllocationList3, and / or a default table (e.g., default table A) as the resource allocation table to be applied to PDSCH time domain resource allocation, based on whether pdsch-ConfigCommonRedCap includes pdsch-TimeDomainAllocationList1 (second parameter list), pdsch-ConfigCommonRedCap includes pdsch-TimeDomainAllocationList2 (second parameter list), and / or pdsch-Config includes pdsch-TimeDomainAllocationList3 (third parameter list). For example, the terminal device 1 may determine whether to use pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, and / or a default table (e.g., default table A) as the resource allocation table to be applied to PDSCH time domain resource allocation, based on whether pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList1 and / or whether pdsch-ConfigCommonRedCap includes pdsch-TimeDomainAllocationList2. The base station device 3 may transmit pdsch-TimeDomainAllocationList in pdsch-ConfigCommon, pdsch-ConfigCommonRedCap, and / or pdsch-Config to have the terminal device 1 determine the parameter list to be used for the resource allocation table.

[0172] In this embodiment, the pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) that can be included in pdsch-ConfigCommonRedCap has the same information element configuration as the pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) that can be included in pdsch-ConfigCommon, but may have a different information element configuration. Like pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2 includes a maximum of 16 entries, and one of the entries may be used depending on the 4-bit field (TDRA field) included in the DCI. Each entry included in pdsch-TimeDomainAllocationList2 may indicate K0, mappingType, startSymbolAndLength, and / or other parameters. The values ​​available for K0, mappingType, and / or startSymbolAndLength in each entry of pdsch-TimeDomainAllocationList2 may differ from the values ​​available for pdsch-TimeDomainAllocationList1. For example, the K0 values ​​available in pdsch-TimeDomainAllocationList1 may be 0 to 32, and the K0 values ​​available in pdsch-TimeDomainAllocationList2 may be 0 to 4. For example, the mappingTypes available in pdsch-TimeDomainAllocationList1 may be mapping type A and mapping type B, and the mappingType available in pdsch-TimeDomainAllocationList2 may be only mapping type B. For example, the mappingType may not be indicated in pdsch-TimeDomainAllocationList2.

[0173] The terminal device 1 determines whether or not one or more predetermined conditions are met. A parameter list or default table to apply to the inter-area resource allocation setting. pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2 and / or Default Table A). The terminal device 1 has at least pdsch-TimeDomainAllocationList1 as an SIB (which may be SIB1). pdsch-TimeDomainAllocationList2 is provided in the SIB (which may be SIB1) and / or the corresponding separate initial downlink BWP has a predefined common A search space (CSS) and / or a CORESET associated with the CSS is set, and based on this determination, it may be determined whether to apply pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, or default table A to the PDSCH time domain resource allocation configuration.

[0174] However, "pdsch-TimeDomainAllocationList1 is provided in SIB" means that it is provided in SIB. The parameters provided may include pdsch-TimeDomainAllocationList1. "pdsch-TimeDomainAllocationList1 is not provided in SIB" means that the If the parameter (e.g., PDSCH-ConfigCommon) contains pdsch-TimeDomainAllocationList1, and / or parameters containing pdsch-TimeDomainAllocationList1 (e.g. For example, PDSCH-ConfigCommon may not be provided in the SIB.

[0175] However, "pdsch-TimeDomainAllocationList2 is provided in SIB" means that it is provided in SIB. The parameters provided may include pdsch-TimeDomainAllocationList2. "pdsch-TimeDomainAllocationList2 is not provided in SIB" means that the pdsch-TimeDomainAllocationList2 in a parameter (e.g., PDSCH-ConfigCommonRedCap) does not contain the parameter pdsch-TimeDomainAllocationList2 and / or It may be that the data (e.g., PDSCH-ConfigCommonRedCap) is not provided in the SIB.

[0176] Whether PDSCH-ConfigCommon includes pdsch-TimeDomainAllocationList1, separate The parameter list and / or default table (e.g., pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, and / or default table A) to be applied to the PDSCH time domain resource allocation configuration may be determined / specified / configured / set based on whether PDSCH-ConfigCommonRedCap, which is a configuration corresponding to the initial downlink BWP, includes pdsch-TimeDomainAllocationList2 and whether a specified common search space (CSS) and / or a CORESET linked to the CSS is configured in the corresponding separate initial downlink BWP.

[0177] In order for the terminal device 1 to receive a random access response via a PDSCH in a separate initial downlink BWP, a common search space needs to be configured in the separate initial downlink BWP. Therefore, depending on whether a predetermined common search space (CSS) and / or a CORESET linked to the CSS is configured in the separate initial downlink BWP, it is considered that an appropriate parameter list for PDSCH time domain resource allocation configuration used to receive the corresponding PDSCH may differ. Therefore, it may be possible to determine whether a predetermined common search space (CSS) and / or a CORESET linked to the CSS is configured in the separate initial downlink BWP, and to determine whether to apply pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, or default table A to PDSCH time domain resource allocation configuration based on the determination. For example, when a predetermined common search space (CSS) and / or a CORESET linked to the CSS is set in the separate initial downlink BWP, the terminal device 1 may apply pdsch-TimeDomainAllocationList2 or default table A to the PDSCH time domain resource allocation setting, and when a predetermined common search space (CSS) and / or a CORESET linked to the CSS is not set in the separate initial downlink BWP, the terminal device 1 may apply pdsch-TimeDomainAllocationList1 or default table A to the PDSCH time domain resource allocation setting.

[0178] However, "a predetermined common search space (CSS) is configured in the separate initial downlink BWP" may mean that a CSS for monitoring a corresponding PDCCH is configured in pdcch-ConfigCommonRedCap included in separateInitialDownlinkBWP, which is the configuration of the separate initial downlink BWP. For example, a search space ID of the CSS may be indicated in a parameter ra-SearchSpace included in pdcch-ConfigCommonRedCap for a terminal device 1 that receives DCI accompanied by a CRC scrambled by RA-RNTI in the CSS.

[0179] However, if a CORESET with a CSS is set in the separate initial downlink BWP, "included in separateInitialDownlinkBWP", which is the setting of separate initial downlink BWP In the pdcch-ConfigCommonRedCap included in the pdcch-ConfigCommonRedCap, a CSS that references the CORESET set in the pdcch-ConfigCommonRedCap may be set. For example, for a terminal device 1 that receives DCI accompanied by a CRC scrambled with RA-RNTI, a search space ID of the CSS may be indicated in a parameter ra-SearchSpace included in the pdcch-ConfigCommonRedCap, and the CSS identified by the search space ID may be linked to a CORESET identified by a controlResourceSetId indicated in a parameter SearchSpace in a parameter commonSearchSpaceList included in the pdcch-ConfigCommonRedCap.

[0180] However, if a CORESET with a CSS is set in the separate initial downlink BWP, "included in separateInitialDownlinkBWP", which is the setting of separate initial downlink BWP In the pdcch-ConfigCommonRedCap included in the pdcch-ConfigCommonRedCap, a CSS referencing a CORESET located within the band of the separate initial downlink BWP in the frequency domain may be set. For example, for the terminal device 1 receiving DCI accompanied by a CRC scrambled with RA-RNTI, a search space ID of the CSS may be indicated by a parameter ra-SearchSpace included in the pdcch-ConfigCommonRedCap, the CSS identified by the search space ID may be linked to a CORESET identified by a controlResourceSetId indicated by a parameter SearchSpace in a parameter commonSearchSpaceList included in the pdcch-ConfigCommonRedCap, and the frequency position of the identified CORESET may be within the band of the separate initial downlink BWP.

[0181] However, if a CORESET with a CSS is set in the separate initial downlink BWP, "included in separateInitialDownlinkBWP", which is the setting of separate initial downlink BWP In the pdcch-ConfigCommonRedCap included in the pdcch-ConfigCommonRedCap, a CSS referencing a CORESET located outside the band of the separate initial downlink BWP in the frequency domain may be set. For example, for the CSS, for the terminal device 1 receiving DCI accompanied by a CRC scrambled with RA-RNTI, a search space ID of the CSS may be indicated by a parameter ra-SearchSpace included in the pdcch-ConfigCommonRedCap, the CSS identified by the search space ID may be linked to a CORESET identified by a controlResourceSetId indicated by a parameter SearchSpace in a parameter commonSearchSpaceList included in the pdcch-ConfigCommonRedCap, and the frequency position of the identified CORESET may be outside the band of the separate initial downlink BWP.

[0182] However, if a CORESET with a CSS is set in the separate initial downlink BWP, "included in separateInitialDownlinkBWP", which is the setting of separate initial downlink BWP In the pdcch-ConfigCommonRedCap included in the CSS, a CSS that references the CORESET set in the pdcch-ConfigCommonRedCap is set, and the frequency position of the CORESET is set to the corresponding CSS. It may be outside the band of the Pareto initial downlink BWP. For example, the predetermined CORESET may be a CORESET identified by the parameter controlResourceSetId in the parameter SearchSpace that sets the corresponding CSS in pdcch-ConfigCommonRedCap.

[0183] The terminal device 1 applies pdsch-TimeDomainAllocationList2 to the PDSCH time domain resource allocation configuration. As an example of the conditions to be applied, the following conditions (A1) or (A2) may be used.

[0184] (A1) (Regardless of whether pdsch-TimeDomainAllocationList1 is provided in the SIB, ) If pdsch-TimeDomainAllocationList2 is provided in the SIB (for example, When the parameter (e.g. PDSCH-ConfigCommonRedCap) contains pdsch-TimeDomainAllocationList2)

[0185] (A2) (Regardless of whether pdsch-TimeDomainAllocationList1 is provided in the SIB, ) pdsch-TimeDomainAllocationList2 is provided in the SIB (e.g., If a parameter (e.g., PDSCH-ConfigCommonRedCap) specifies pdsch-TimeDomainAllocationList2, When the initial downlink BWP (separate initial downlink BWP) configured by the separateInitialDownlinkBWP including the pdsch-TimeDomainAllocationList2 is configured with a CORESET linked to a CSS for monitoring the corresponding PDCCH.

[0186] The terminal device 1 applies pdsch-TimeDomainAllocationList1 to the PDSCH time domain resource allocation configuration. As an example of the conditions to be used, one or more of the following conditions (B1) to (B5) may be used: stomach.

[0187] (B1) pdsch-TimeDomainAllocationList2 is not provided in the SIB (the parameter provided in the SIB (e.g., PDSCH-ConfigCommonRedCap) does not include pdsch-TimeDomainAllocationList2) If pdsch-TimeDomainAllocationList1 is provided in the SIB (e.g., if the SIB does not provide parameters (e.g., PDSCH-ConfigCommonRedCap) that include pdsch-TimeDomainAllocationList2), and / or if the SIB does not provide parameters (e.g., PDSCH-ConfigCommonRedCap) that include pdsch-TimeDomainAllocationList2), then pdsch-TimeDomainAllocationList1 is provided in the SIB (e.g., if the parameters provided in the SIB (e.g., PDSCH-ConfigCommon) include pdsch-TimeDomainAllocationList).

[0188] (B2) When separateInitialDownlinkBWP is not provided in the SIB and pdsch-TimeDomainAllocationList1 is provided in the SIB (for example, when the parameters provided in the SIB (for example, PDSCH-ConfigCommon) include pdsch-TimeDomainAllocationList)

[0189] (B3) When pdsch-TimeDomainAllocationList1 is provided in the SIB (for example, when a parameter provided in the SIB (for example, PDSCH-ConfigCommon) includes pdsch-TimeDomainAllocationList), pdsch-TimeDomainAllocationList2 is not provided in the SIB, and the frequency location of the initial downlink BWP (separate initial downlink BWP) set in separateInitialDownlinkBWP includes the frequency location of CORESET#0 set in the MIB

[0190] (B4) When the initial downlink BWP (separate initial downlink BWP) configured by separateInitialDownlinkBWP does not have a CORESET linked to the CSS for monitoring the corresponding PDCCH, and pdsch-TimeDomainAllocationList1 is provided in the SIB (for example, when the parameters provided in the SIB (for example, PDSCH-ConfigCommon) include pdsch-TimeDomainAllocationList)

[0191] (B5) In the initial downlink BWP (separate initial downlink BWP) configured by separateInitialDownlinkBWP, a CORESET linked to the CSS for monitoring the corresponding PDCCH is configured, and pdsch-TimeDomainAllocationList2 is not provided in the SIB (provided in the SIB). The parameters (e.g., PDSCH-ConfigCommonRedCap) are and / or the SIB does not provide a parameter (PDSCH-ConfigCommonRedCap) that includes pdsch-TimeDomainAllocationList2), if pdsch-TimeDomainAllocationList1 is provided in the SIB (e.g., if a parameter provided in the SIB (e.g., PDSCH-ConfigCommon) includes pdsch-TimeDomainAllocationList)

[0192] An example of a condition under which the terminal device 1 applies a default table (for example, default table A, default table B, or default table C) to the PDSCH time domain resource allocation setting As the condition, one or more of the following conditions (C1) to (C8) may be used.

[0193] (C1) pdsch-TimeDomainAllocationList2 is not provided in the SIB (the parameter provided in the SIB (e.g., PDSCH-ConfigCommonRedCap) does not include pdsch-TimeDomainAllocationList2) and / or the SIB does not provide a parameter (PDSCH-ConfigCommonRedCap) that includes pdsch-TimeDomainAllocationList2), or pdsch-TimeDomainAllocationList1 is not provided in the SIB (e.g., if the parameters provided in the SIB (e.g., PDSCH-ConfigCommon) do not include pdsch-TimeDomainAllocationList1 and / or the SIB does not provide a parameter (PDSCH-ConfigCommon) that includes pdsch-TimeDomainAllocationList1).

[0194] (C3) pdsch-TimeDomainAllocationList2 is not provided in the SIB (the parameter provided by the SIB parameter (e.g., PDSCH-ConfigCommonRedCap) includes pdsch-TimeDomainAllocationList2. and / or the SIB does not provide a parameter (PDSCH-ConfigCommonRedCap) containing pdsch-TimeDomainAllocationList2)

[0195] (C4) When the parameters provided by the SIB (e.g., PDSCH-ConfigCommonRedCap) do not include pdsch-TimeDomainAllocationList2, or when the SIB does not provide a parameter (PDSCH-ConfigCommonRedCap) that includes pdsch-TimeDomainAllocationList2 and pdsch-TimeDomainAllocationList1 is not provided in the SIB (e.g., when the parameters provided by the SIB (e.g., PDSCH-ConfigCommon) do not include pdsch-TimeDomainAllocationList1, and / or if the SIB does not provide parameters (PDSCH-ConfigCommon) including pdsch-TimeDomainAllocationList1)

[0196] (C5) When pdsch-TimeDomainAllocationList1 is provided in the SIB (for example, when the parameters provided in the SIB (for example, PDSCH-ConfigCommon) include pdsch-TimeDomainAllocationList), and the parameters provided in the SIB (for example, PDSCH-ConfigCommonRedCap) do not include pdsch-TimeDomainAllocationList2, and the frequency location of the initial downlink BWP (separate initial downlink BWP) set in separateInitialDownlinkBWP does not include the frequency location of CORESET#0 set in the MIB, or when pdsch-TimeDomainAllocationList2 is not provided in the SIB and pdsch-TimeDomainAllocationList1 is not provided in the SIB

[0197] (C6) When the initial downlink BWP (separate initial downlink BWP) configured by separateInitialDownlinkBWP does not have a CORESET linked to the CSS for monitoring the corresponding PDCCH, and pdsch-TimeDomainAllocationList1 is not provided in the SIB

[0198] (C7) When a CORESET linked to a CSS for monitoring the corresponding PDCCH is set in the initial downlink BWP (separate initial downlink BWP) set by separateInitialDownlinkBWP and pdsch-TimeDomainAllocationList1 is not provided in the SIB

[0199] (C8) In the initial downlink BWP (separate initial downlink BWP) configured by separateInitialDownlinkBWP, a CORESET linked to a CSS for monitoring the corresponding PDCCH is configured, and pdsch-TimeDomainAllocationList1 and pdsch-TimeDomainAllocationList2 are not provided in the SIB.

[0200] However, whether to apply the above-described examples of the conditions for applying pdsch-TimeDomainAllocationList1 to the PDSCH time domain resource allocation configuration, the conditions for applying pdsch-TimeDomainAllocationList1, or the conditions for applying the default table depends on the type of RNTI (for example, SI-RNTI, RA-RNTI, MSGB-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI, and / or or CS-RNTI), the type of search space of the PDCCH transmitting the DCI (e.g., Type 0 common search space, Type 0A common search space, Type 1 common search space, Type 2 common search space, and / or UE specific search space), whether the search space of the PDCCH transmitting the DCI is linked to CORESET#0, whether the search space of the PDCCH transmitting the DCI is linked to a common CORESET, and / or the multiplexing pattern of the SS / PBCH block and CORESET. For example, when the RNTI used to scramble the CRC assigned to the DCI that schedules the corresponding PDSCH is RA-RNTI, the terminal device 1 applies any one of the above conditions (A1) to (A2), any one of (B1) to (B5), and any one of (C1) to (C8), and when the RNTI used to scramble the CRC assigned to the DCI that schedules the corresponding PDSCH is SI-RNTI, the terminal device 1 may apply default table A, default table B, or default table C to the PDSCH time domain resource allocation setting without applying pdsch-TimeDomainAllocationList1 and pdsch-TimeDomainAllocationList2.

[0201] However, in each of the above-mentioned conditions, the "CSS for monitoring the corresponding PDCCH" and the "CORESET linked to the CSS for monitoring the corresponding PDCCH" are the CSS and CORESET for monitoring the PDCCH that schedules the PDSCH to which the PDSCH time domain resource allocation setting is applied.

[0202] The terminal device 1 may determine a resource allocation table to be applied to PDSCH time domain resource allocation based on a plurality of factors, as shown in Fig. 10. The terminal device 1 determines the resource allocation table to be applied to PDSCH time domain resource allocation based on at least some or all of the following factors (A) to (F): The resource allocation table to be applied to the scheduled PDSCH may be determined. Element (A): Type (value) of RNTI that scrambles the CRC added to the DCI Element (B): Type of search space in which DCI is found Element (C): Whether the CORESET associated with the search space is CORESET#0 Element (D): Whether pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList Element (E): Whether pdsch-ConfigCommonRedCap includes pdsch-TimeDomainAllocationList mosquito Element (F): Multiplexed patterns of SS / PBCH blocks and CORESET

[0203] In element (A), the type of RNTI used to scramble the CRC added to the DCI is one of SI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI. In FIG. 10, the type of RNTI that scrambles the CRC added to the DCI is RA-RNTI. However, definitions may be similarly applied to other types of RNTIs.

[0204] In element (B), the type of search space in which DCI is detected is a common search space or a UE-specific search space. The common search space can be a type 0 common search space, a type 0A common search space, or a type 1 common search space. , and Type 2 common search spaces. FIG. 10 shows the cases of Type 1 common search space and Type 2 common search space, but other search spaces may be defined in a similar manner. However, element (B) may be associated with element (A). When element (A) is a predetermined RNTI type, element (B) may be the type of search space corresponding to the type of RNTI.

[0205] As an example A in Figure 10, the terminal device 1 detects DCI in a type 1 common search space, and if the detected DCI has a CRC attached that is scrambled by the RA-RNTI, the terminal device 1 may determine a resource allocation table to be applied to the PDSCH scheduled by that DCI. If the pdsch-ConfigCommon received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (No), and the pdsch-ConfigCommonRedCap received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (No) (or if pdsch-ConfigCommonRedCap itself is not set (-)), the terminal device 1 may determine the resource allocation table to be applied to the PDSCH time domain resource allocation to be default table A (Default A). In other words, the terminal device 1 may use default table A indicating the setting of PDSCH time domain resource allocation to apply to the determination of PDSCH time domain resource allocation. If the pdsch-ConfigCommon received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 includes or does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (Yes / No), and the pdsch-ConfigCommonRedCap received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (Yes), the terminal device 1 may determine that the resource allocation table to be applied to PDSCH time domain resource allocation is pdsch-TimeDomainAllocationList2. In other words, the terminal device 1 may apply the pdsch-TimeDomainAllocationList included in pdsch-ConfigCommonRedCap to determining the PDSCH time domain resource allocation.If the pdsch-ConfigCommon received in SIB1 / other SIBs and / or RRC messages received by terminal device 1 includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (Yes), and the pdsch-ConfigCommonRedCap received in SIB1 / other SIBs and / or RRC messages received by terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2). (No) (or if pdsch-ConfigCommonRedCap itself is not set (-)) The terminal device 1 may determine that the resource allocation table to be applied to PDSCH time domain resource allocation is the pdsch-TimeDomainAllocationList 1. That is, the terminal device 1 may apply the pdsch-TimeDomainAllocationList included in pdsch-ConfigCommon to determine PDSCH time domain resource allocation.

[0206] As an example B in FIG. 10, the terminal device 1 detects DCI in the type 2 common search space, and if the detected DCI has a CRC scrambled by the P-RNTI added, the terminal device 1 The resource allocation table to be applied to the PDSCH scheduled by the UE may be determined. If the pdsch-ConfigCommon received by the terminal device 1 in SIB1 / other SIBs and / or RRC messages does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (No), and the pdsch-ConfigCommonRedCap received by the terminal device 1 in SIB1 / other SIBs and / or RRC messages does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (No) (or if pdsch-ConfigCommonRedCap itself is not set (-)), the terminal device 1 may determine the resource allocation table to be applied to PDSCH time domain resource allocation as the default table. However, it may determine whether to use default table A (Default A), default table B (Default B), or default table C (Default C) based on the multiplexing pattern of the SS / PBCH block and CORESET. If the pdsch-ConfigCommon received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 includes or does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (Yes / No), and the pdsch-ConfigCommonRedCap received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (Yes), the terminal device 1 may determine that the resource allocation table to be applied to PDSCH time domain resource allocation is pdsch-TimeDomainAllocationList2. In other words, the terminal device 1 may apply the pdsch-TimeDomainAllocationList included in pdsch-ConfigCommonRedCap to determining the PDSCH time domain resource allocation. If the pdsch-ConfigCommon received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (Yes), and the pdsch-ConfigCommonRedCap received in SIB1 / other SIBs and / or RRC messages received by the terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (No) (or if pdsch-ConfigCommonRedCap itself is not set (-)), the terminal device 1 may determine that the resource allocation table to be applied to PDSCH time domain resource allocation is pdsch-TimeDomainAllocationList1. In other words, the terminal device 1 may apply the pdsch-TimeDomainAllocationList included in pdsch-ConfigCommon to determining the PDSCH time domain resource allocation.

[0207] As an example C in Figure 10, the terminal device 1 detects DCI in a type 0 common search space, and if the detected DCI has a CRC attached that is scrambled by the SI-RNTI, the terminal device 1 may determine a resource allocation table to be applied to the PDSCH scheduled by that DCI. When the detected DCI has a CRC attached that is scrambled by the SI-RNTI, the terminal device 1 may apply a default table (e.g., default table A, default table B, or default table C) to the PDSCH time domain resource allocation setting, regardless of whether pdsch-TimeDomainAllocationList1 or pdsch-TimeDomainAllocationList2 is provided in the SIB. When the detected DCI has a CRC attached that is scrambled by the SI-RNTI, the terminal device 1 may determine whether to apply default table A, default table B, or default table C to the PDSCH time domain resource allocation setting based on the multiplexing pattern of the SS / PBCH block and CORESET.

[0208] One that applies pdsch-TimeDomainAllocationList2 to PDSCH time domain resource allocation configuration An example of the criterion is whether the corresponding PDSCH can be transmitted / received in a separate initial downlink BWP. For example, the fifth column of the table shown in Fig. 10 lists as a condition whether pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) is included in PDSCH-ConfigCommonRedCap. However, if the corresponding PDSCH cannot be transmitted / received in a separate initial downlink BWP, a table without the fifth column in Fig. 10 may be applied. In other words, if the corresponding PDSCH cannot be transmitted / received in a separate initial downlink BWP, either pdsch-TimeDomainAllocationList1 or the default table may be applied as a selection criterion for the parameter list and / or default table to be applied to the PDSCH time domain resource allocation configuration based on whether PDSCH-ConfigCommon includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1). However, the fact that the corresponding PDSCH cannot be transmitted / received in the separate initial downlink BWP may also mean that a CORESET linked to the CSS is not assigned within the separate initial downlink BWP as a CORESET for receiving the DCI that schedules the PDSCH.

[0209] In this way, the CRC assigned to the DCI that schedules the PDSCH is added to the RNTI that scrambles the CRC. Therefore, the parameter list and / or data set that apply to the PDSCH time domain resource allocation configuration The fault table is determined differently depending on the information transmitted by the PDSCH. For example, if pdsch-TimeDomainAllocationList2 is When appropriate time resources are defined for a PDSCH transmitted in a separate initial downlink BWP, and when a PDSCH corresponding to a predetermined RNTI is not transmitted in a separate initial downlink BWP, a determination method that excludes pdsch-TimeDomainAllocationList2 from the candidates may be used, and when a PDSCH corresponding to a predetermined RNTI can be transmitted in a separate initial downlink BWP, a determination method that includes pdsch-TimeDomainAllocationList2 as a candidate may be used. For example, any of Default Table A, Default Table B, and Default Table C may be applied to the PDSCH time domain resource allocation configuration of a PDSCH corresponding to SI-RNTI, and any of pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, and Default Table A may be applied to the PDSCH time domain resource allocation configuration of a PDSCH corresponding to RA-RNTI based on the above-mentioned conditions.

[0210] FIG. 15 shows the DCI, SIB, and random access response in the terminal device 1 of this embodiment. 15 is a flowchart showing an example of a process related to reception. In step S1001 of FIG. In step S1002, the terminal device 1 receives a first DCI accompanied by a CRC scrambled with the SI-RNTI in a first BWP of a first cell. In step S1003, the terminal device 1 receives an SIB via a first PDSCH scheduled for the first time resource. When configuration information of a second BWP is included in the SIB, the terminal device 1 can identify the second BWP. In step S1004, the terminal device 1 receives a second DCI accompanied by a CRC scrambled with the RA-RNTI in the second BWP of the first cell. In step S1005, the terminal device 1 determines the second time domain resource using a second value indicated by the second field included in the second DCI and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and a time domain resource. In step S1006, the terminal device 1 receives a random access response (RAR) via a second PDSCH scheduled for the second time resource. However, in step S1002, the terminal device 1 may apply the first default table, the second default table, or the third default table to the first PDSCH time domain resource allocation configuration. However, in step S1005, the terminal device 1 determines whether the second parameter list is provided in the SIB, and if the second parameter list is provided in the SIB, may apply the second parameter list to the second PDSCH time domain resource allocation configuration. If the second parameter list is not provided in the SIB, may apply the first parameter list or the first default table to the second PDSCH time domain resource allocation configuration. The flow of the flow diagram shown in FIG. 15 is similarly applicable to processing related to transmission of DCI, SIB, and random access response in the base station device 3. However, the reception of the first DCI in step S1001, the reception of the SIB in step S1003, the reception of the second DCI in step S1004, and the reception of the random access response in step S1006 correspond to the transmission of the first DCI, the transmission of the SIB, the transmission of the second DCI, and the transmission of the random access response, respectively.

[0211] FIG. 16 is a flow diagram showing an example of processing related to determination / identification / configuration / setting of a resource allocation table applied to PDSCH time domain resource allocation in the terminal device 1 of this embodiment. In step S2001 of FIG. 16, the terminal device 1 receives an SIB (which may be SIB1). The SIB contains configuration information (initialDownlinkBWP) of a first BWP (which may be an initial downlink BWP). The SIB may include the first parameter list (which may be Pdsch-TimeDomainAllocationList2), the PDSCH configuration information of the first BWP (which may be PDSCH-ConfigCommon), the configuration information of the second BWP (which may be a separate initial downlink BWP) (which may be separateInitialDownlinkBWP), and / or the PDSCH configuration information of the second BWP (which may be PDSCH-ConfigCommonRedCap). In step S2002, the terminal device 1 receives DCI with a CRC scrambled with the RA-RNTI on the PDCCH. In step S2003, the terminal device 1 determines whether a second parameter list (which may be pdsch-TimeDomainAllocationList2) is provided in the SIB received in step S2001. If step S2003 is positive (S2003-Yes), in step S2004, the terminal device 1 applies the second parameter list to the PDSCH time domain resource allocation configuration, and proceeds to step S2008. If step S2003 is negative (S2003-No), in step S2005, the terminal device 1 determines whether the first parameter list (which may be pdsch-TimeDomainAllocationList1) is provided in the SIB received in step 2001. 16 is similarly applicable to the processing related to determining / specifying / configuring / setting a resource allocation table to be applied to PDSCH time domain resource allocation in the base station apparatus 3. However, the reception of the SIB in step S2001, the reception of the DCI in step S2002, and the reception of the PDSCH in step S2009 correspond to the transmission of the SIB, the transmission of the DCI, and the transmission of the PDSCH, respectively.

[0212] 17 is a flow chart showing another example of processing related to determining / identifying / configuring / setting a resource allocation table applied to PDSCH time domain resource allocation in the terminal device 1 of this embodiment. In step S3001 of FIG. 17, the terminal device 1 receives an SIB (which may be SIB1) including configuration information (which may be separateInitialDownlinkBWP) of a second BWP (which may be a separate initial downlink BWP). The SIB may include configuration information (which may be initialDownlinkBWP) of a first BWP (which may be an initial downlink BWP), PDSCH configuration information (which may be PDSCH-ConfigCommon) of the first BWP, and / or PDSCH configuration information (which may be PDSCH-ConfigCommonRedCap) of the second BWP. In step S3002, the terminal device 1 receives DCI accompanied by a CRC scrambled with RA-RNTI on a PDCCH in a common search space (CSS). In step S3003, the terminal device 1 determines whether a CORESET linked to the CSS in step S3002 is set in the configuration information of the second BWP received in step S3001. However, this determination may be made before step S3002. If step S3003 is yes (S3003-Yes), in step S3004, the terminal device 1 applies the second parameter list (which may be pdsch-TimeDomainAllocationList2) or a default table (which may be default table A) to the PDSCH time domain resource allocation configuration, and proceeds to step S3006. If step S3003 is no (S3003-No), in step S3005, the terminal device 1 applies the first parameter list (which may be pdsch-TimeDomainAllocationList1) or a default table (which may be default table A) to the PDSCH time domain resource allocation configuration, and proceeds to step S3006. In step S3006, the terminal device 1 determines the time resource for receiving the PDSCH based on the value indicated by the TDRA field included in the received DCI and the applied PDSCH time domain resource allocation setting.In step S3007, the terminal device 1 receives the PDSCH in the time resource determined in step S3006. However, in step 3004, the terminal device 1 may determine whether to apply the second parameter list or the default table to the PDSCH time domain resource allocation configuration according to a predetermined condition (for example, whether the second parameter list is provided in the SIB). However, in step 3005, the terminal device 1 may determine whether to apply the first parameter list or the default table to the PDSCH time domain resource allocation configuration according to a predetermined condition (for example, whether the first parameter list is provided in the SIB). The flow of the flowchart shown in FIG. 17 is similarly applicable to the processing related to determining / identifying / configuring / setting a resource allocation table to be applied to PDSCH time domain resource allocation in the base station device 3. However, the reception of the SIB in step S3001, the reception of the DCI in step S3002, and the reception of the PDSCH in step S3007 correspond to the transmission of the SIB, the transmission of the DCI, and the transmission of the PDSCH, respectively.

[0213] The terminal device 1 may select one PDSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the 'Time domain resource assignment' field (TDRA field) included in the DCI scheduling the PDSCH. For example, if the resource allocation table applied to the PDSCH time domain resource allocation is default Table A, the value m indicated in the TDRA field may indicate row index m+1 of default Table A. In this case, the PDSCH time domain resource allocation is the time domain resource allocation configuration indicated from row index m+1. The terminal device 1 receives the PDSCH assuming the time domain resource allocation configuration indicated from row index m+1. For example, if the value m indicated in the TDRA field is 0, the terminal device 1 identifies the time domain resource allocation of the PDSCH scheduled by the DCI using the PDSCH time domain resource allocation configuration of row index 1 of default Table A.

[0214] Also, when the resource allocation table applied to PDSCH time domain resource allocation is a resource allocation table given by pdsch-TimeDomainAllocationList included in pdsch-ConfigCommon or pdsch-ConfigCommonRedCap, the value m indicated in the TDRA field corresponds to the (m+1)th element (entry, row) in the list pdsch-TimeDomainAllocationList. For example, when the value m indicated in the TDRA field is 0, the terminal device 1 may refer to the first element (entry) in the list pdsch-TimeDomainAllocationList. For example, when the value m indicated in the TDRA field is 1, the terminal device 1 may refer to the second element (entry) in the list pdsch-TimeDomainAllocationList.

[0215] However, the parameters set in SIB1 are not broadcast in other SIBs (or REDCAP SIBs). Alternatively, the notification may be given by RRC signaling.

[0216] The configuration of the device in this embodiment will be described below.

[0217] FIG. 18 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment. The terminal device 1 includes a radio transmission / reception unit 10 and an upper layer processing unit 14. The receiving unit 10 includes an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 is configured to include a medium access control layer processing unit 15 and a radio resource control layer processing unit 16. The radio transceiver unit 10 is also referred to as a transmitter unit 10, a receiver unit 10, a monitor unit 10, or a physical layer processing unit 10. The upper layer processing unit 14 is also referred to as a processor unit 14, a measurement unit 14, a selector unit 14, a decision unit 14, or a control unit 14.

[0218] The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by a user operation or the like to the radio transceiver unit 10. The upper layer processing unit 14 performs some or all of the processing of the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 14 may have a function to acquire bit information of the MIB (which may be the REDCAP MIB), SIB1 (which may be the REDCAP SIB1), and other SIBs (which may be the REDCAP SIBs). The upper layer processing unit 14 may have a function to determine / specify the configuration of the initial downlink BWP (e.g., frequency location and bandwidth) based on information in the system information block (SIB1 / SIB) or RRC signaling. The upper layer processing unit 14 may have a function to determine / specify the configuration of the initial uplink BWP (e.g., frequency location and bandwidth) based on information in the system information block (SIB1 / SIB) or RRC signaling. The upper layer processing unit 14 may have a function to determine / specify the configuration of the separate initial uplink BWP (e.g., frequency location and bandwidth) based on information in the system information block (SIB1 / SIB) or RRC signaling. The upper layer processing unit 14 may have a function to determine the time resource for receiving the PDSCH by using a value indicated by a field (TDRA field) included in the DCI and the PDSCH time domain resource allocation configuration. The upper layer processing unit 14 may have a function to apply a predetermined parameter list (e.g., pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, and / or pdsch-TimeDomainAllocationList3) and a predetermined default table (e.g., default table A, default table B, and / or default table C) to the PDSCH time domain resource allocation configuration.The upper layer processing unit 14 may have a function of determining the conditions shown in the present invention (e.g., whether or not a predetermined parameter list is provided in the SIB, and / or whether or not a CORESET linked to a CSS is configured in the configuration information of a predetermined BWP (initialDownlinkBWP and / or separateInitialDownlinkBWP)), and determining, based on the determination, a parameter list (e.g., pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, and / or pdsch-TimeDomainAllocationList3) and / or a default table (e.g., default table A, default table B, and / or default table C) to be applied to the PDSCH time domain resource allocation configuration.

[0219] The upper layer processing unit 14 includes a media access control layer processing unit 15 that processes data in a MAC layer (media access control The medium access control layer processing unit 15 controls the transmission of scheduling requests based on various setting information / parameters managed by the radio resource control layer processing unit 16.

[0220] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 controls the RRC layer (radio resource control The radio resource control layer processing unit 16 performs processing of the downlink control layer (control layer). The radio resource control layer processing unit 16 manages various setting information / parameters of its own device. The radio resource control layer processing unit 16 sets various setting information / parameters based on signals of higher layers received from the base station device 3. That is, the radio resource control layer processing unit 16 sets various setting information / parameters based on information indicating the various setting information / parameters received from the base station device 3. The radio resource control layer processing unit 16 controls (specifies) resource allocation based on downlink control information received from the base station device 3.

[0221] The wireless transmission / reception unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transmission / reception unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and transmits the decoded information to a higher-level The radio transmission / reception unit 10 modulates and encodes data to generate a transmission signal, and transmits the signal to the base station device 3, etc. The radio transmission / reception unit 10 outputs an upper layer signal (RRC message), DCI, etc. received from the base station device 3 to the upper layer processing unit 14. Based on an instruction from the upper layer processing unit 14, the radio transmission / reception unit 10 also outputs an uplink signal (PUCCH and / or The radio transceiver 10 generates and transmits a synchronization signal block, an additional synchronization signal block, and a PUSCH. Signal blocks, PSS, SSS, PBCH, DMRS for PBCH, Random Access Response, PDCCH and The radio transceiver 10 may have a function to receive a PDCCH and / or a PDSCH. The radio transceiver 10 may have a function to transmit a PRACH (which may be a random access preamble), a PUCCH and / or a PUSCH. The radio transceiver 10 may have a function to monitor a PDCCH. The radio transceiver 10 may have a function of receiving DCI on the PDCCH. The radio transceiver 10 may have a function of outputting the DCI received on the PDCCH to the upper layer processing unit 14. The radio transceiver 10 may have a function of receiving a system information block (SIB1 and / or SIB) corresponding to a predetermined cell. The radio transceiver unit 10 may have a function to receive, in a certain BWP of a certain cell, a DCI accompanied by a CRC scrambled with a predetermined RNTI (e.g., SI-RNTI, RA-RNTI, P-RNTI, etc.). The radio transceiver unit 10 may have a function to receive, in a certain BWP of a certain cell, a SIB (which may be SIB1) or a random access response via a PDSCH scheduled in a predetermined time resource.

[0222] The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (down-converts) and removes unnecessary frequency components. The processed analog signal is output to the baseband section.

[0223] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 extracts a CP (Cyclic Prefix) from the converted digital signal. The part corresponding to the CP is removed, and the signal from which the CP has been removed is subjected to a Fast Fourier Transform (FFT) to extract the frequency domain signal.

[0224] The baseband unit 13 performs an Inverse Fast Fourier Transform (IFFT) on the data to generate OFDM symbols, adds CPs to the generated OFDM symbols, generates baseband digital signals, and converts the baseband digital signals into analog signals. The baseband unit 13 outputs the converted analog signals to the RF unit 12.

[0225] The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 also amplifies power. The RF unit 12 may also have a function of determining the transmission power of an uplink signal and / or an uplink channel to be transmitted in the serving cell. The RF unit 12 is also referred to as a transmission power control unit.

[0226] The RF unit 12 may use an antenna switch to connect the antenna unit 11 to a filter provided in the RF unit 12 when receiving a signal, and to connect the antenna unit 11 to a power amplifier provided in the RF unit 12 when transmitting a signal.

[0227] The RF unit 12 may have a function of adjusting / retuning the frequency band to which the RF circuit is applied within the downlink BWP when the bandwidth of the set downlink BWP (for example, the initial downlink BWP) is wider than the bandwidth supported by the receiver of the device itself (which may be referred to as the allocated bandwidth). Note that the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when downconverting the received signal to a baseband signal.

[0228] The RF unit 12 may have a function to adjust / readjust the frequency band to which the RF circuit is applied within the uplink BWP when the bandwidth of the set uplink BWP (for example, the initial downlink BWP) is wider than the bandwidth supported by the transmitter of the own device (which may be referred to as the allocated bandwidth). The frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when an analog signal is up-converted to the carrier frequency.

[0229] FIG. 19 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. The base station device 3 is configured to include a radio transmission / reception unit 30 and an upper layer processing unit 34. The wireless transceiver unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a media access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transceiver unit 30 is also referred to as a transmitter unit 30, a receiver unit 30, a monitor unit 30, or a physical layer processing unit 30. A control unit that controls the operation of each unit based on various conditions may also be provided separately. The upper layer processing unit 34 is also referred to as a processing unit 34, a decision unit 34, or a control unit 34.

[0230] The upper layer processing unit 34 performs some or all of the processing of the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 34 may have a function of generating DCI based on the upper layer signal transmitted to the terminal device 1 and the time resource for transmitting the PUSCH. The upper layer processing unit 34 may have a function of outputting the generated DCI, etc. to the radio transceiver unit 30. The upper layer processing unit 34 may have a function of generating a system information block (SIB1 / SIB) and / or RRC signaling including information for the terminal device 1 to specify an initial downlink BWP. The upper layer processing unit 34 may have a function of generating a system information block (SIB1 / SIB) and / or RRC signaling including information for the terminal device 1 to specify an initial uplink BWP. The upper layer processing unit 34 may have a function of determining a value indicated by a field (TDRA field) included in the DCI using the time resource for transmitting the PDSCH and the PDSCH time domain resource allocation configuration. The upper layer processing unit 34 may have a function of applying a predetermined parameter list (e.g., pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, and / or pdsch-TimeDomainAllocationList3) and a predetermined default table (e.g., Default Table A, Default Table B, and / or Default Table C) to the PDSCH time domain resource allocation configuration.The upper layer processing unit 34 may have a function of determining the conditions shown in the present invention (e.g., whether a predetermined parameter list is provided in the SIB and / or whether a CORESET linked to a CSS is configured in the configuration information of a predetermined BWP (initialDownlinkBWP and / or separateInitialDownlinkBWP)), and determining a parameter list (e.g., pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, and / or pdsch-TimeDomainAllocationList3) and / or a default table (e.g., default table A, default table B, and / or default table C) to be applied to the PDSCH time domain resource allocation configuration based on the determination.

[0231] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs processing of the MAC layer. The media access control layer processing unit 35 performs processing related to the scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 36.

[0232] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 ​​generates DCI (uplink grant, downlink grant) including resource allocation information for the terminal device 1. The radio resource control layer processing unit 36 ​​generates or acquires from an upper node DCI, downlink data (transport block (TB), random access response (RAR)) to be allocated to the PDSCH, system information, an RRC message, a MAC CE (Control Element), and the like, and outputs them to the radio transceiver unit 30. The radio resource control layer processing unit 36 ​​also manages various setting information / parameters for each terminal device 1. The radio resource control layer processing unit 36 ​​may set various setting information / parameters for each terminal device 1 via a signal from an upper layer. That is, the radio resource control layer processing unit 36 ​​transmits / reports information indicating various setting information / parameters. The radio resource control layer processing unit 36 ​​may also transmit / report information for specifying the setting of one or more reference signals in a certain cell.

[0233] When the base station device 3 transmits an RRC message, MAC CE, and / or PDCCH to the terminal device 1 and the terminal device 1 performs processing based on the reception of the message, the base station device 3 performs processing (control of the terminal device 1 and the system) assuming that the terminal device is performing the processing. The base station device 3 sends RRC messages, MAC CEs, and / or PDCCHs to the terminal device 1 that cause the terminal device to perform processing based on the reception.

[0234] The radio transmission / reception unit 30 transmits higher layer signals (RRC messages), DCI, etc. to the terminal device 1. In addition, the radio transmission / reception unit 30 receives the data transmitted from the terminal device 1 based on an instruction from the upper layer processing unit 34. The radio transceiver unit 30 may have a function to transmit a PDCCH and / or a PDSCH. The radio transceiver unit 30 may have a function to receive one or more PUCCHs and / or PUSCHs. The radio transceiver unit 30 may have a function to transmit DCI on the PDCCH. The radio transceiver unit 30 may have a function to transmit DCI output by the upper layer processing unit 34 on the PDCCH. The radio transceiver unit 30 may have a function to transmit SSB, PSS, SSS, PBCH and / or DMRS for the PBCH. The radio transmission / reception unit 30 may have a function to transmit an RRC message (which may be an RRC parameter). The radio transmission / reception unit 30 may be configured to transmit the RRC message (which may be an RRC parameter) when the terminal device 1 receives system information. The radio transceiver unit 30 may have a function of transmitting a signaling block (SIB1 / SIB). In a BWP with The radio transceiver unit 30 may have a function of transmitting a DCI with a CRC that has been allocated to the SIB (which may be SIB1) or a random access response in a certain BWP of a certain cell via a PDSCH that is scheduled in a predetermined time resource. Some of the functions of the line transceiver 30 are the same as those of the wireless transceiver 10, and therefore the description thereof will be omitted. Some or all of them may be included in each transmission / reception point 4.

[0235] The upper layer processing unit 34 also controls the transmission of control messages or user data between the base station devices 3 or between the upper network devices (MME, S-GW (Serving-GW)) and the base station device 3 ( In FIG. 19, other components of the base station device 3 and other components are Although the transmission path of data (control information) between the elements is omitted, the base station device 3 It is clear that the upper layer processing unit 34 includes a plurality of blocks having other functions necessary for its operation. For example, the upper layer processing unit 34 includes a radio resource management layer processing unit and an application layer processing unit.

[0236] Note that the "parts" in the figure are elements that realize the functions and procedures of the terminal device 1 and the base station device 3, and may also be expressed by terms such as section, circuit, component, device, and unit.

[0237] Each of the units denoted by reference numerals 10 to 16 in the terminal device 1 is configured as a circuit. Each of the units denoted by reference numerals 30 to 36 in the base station device 3 may be implemented as a circuit. It may be configured as follows.

[0238] The program that runs on the device according to the present invention may be a program that controls a central processing unit (CPU) or the like to make a computer function so as to realize the functions of the embodiments according to the present invention. The program or information handled by the program may be temporarily stored in a volatile memory such as a random access memory (RAM) or a flash memory. stored in non-volatile memory, hard disk drives (HDDs), or other storage systems. will be done.

[0239] A program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium. The program may be loaded into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0240] Furthermore, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, for example, an integrated circuit or a plurality of integrated circuits. The electrical circuit designed to perform the functions described herein may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a microprocessor (MGA), a microcomputer (MCU ... The general-purpose processor may include a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electrical circuits described above may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge, one or more aspects of the present invention may utilize new integrated circuits based on that technology.

[0241] In the embodiment of the present invention, an example has been described in which the present invention is applied to a communication system configured with a base station device and a terminal device. However, the present invention may also be applied to a communication system in which terminals communicate with each other, such as D2D (Device to Device). This method can also be applied to systems where

[0242] The present invention is not limited to the above-described embodiment. Although an example of a device has been described in the embodiment, the present invention is not limited to this and can be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, for example, AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0243] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0244] 1(1A, 1B) Terminal equipment 3 Base station equipment 4 Transmit / Receive Point (TRP) 10 Radio transmitter / receiver 11 Antenna section 12 RF section 13 Baseband section 14 Upper layer processing unit 15 Medium access control layer processing unit 16 Radio resource control layer processing unit 30 Radio transmitter / receiver 31 Antenna section 32 RF section 33 Baseband section 34 Upper layer processing unit 35 Medium access control layer processing unit 36 Radio resource control layer processing unit 50 Transmitting Unit (TXRU) 51 Phase Shifter 52 Antenna Element

Claims

1. A terminal device, a receiving unit configured to receive, in a first BWP of a first cell, first downlink control information (DCI) with a CRC scrambled with an SI-RNTI and receive a system information block (SIB) via a first physical downlink shared channel (PDSCH) scheduled in a first time resource, and to receive, in a second BWP of the first cell, second DCI with a CRC scrambled with an RA-RNTI in a common search space and receive a random access response via a second PDSCH scheduled in a second time resource; a control unit that determines the first time resource using a first value indicated by a first field included in the first DCI and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the first value and a time resource, and determines the second time resource using a second value indicated by a second field included in the second DCI and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and a time resource, The SIB provides first configuration information of the first BWP and second configuration information of the second BWP; The control unit applies a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation configuration; Determine whether a first control resource set (CORESET) associated with the common search space is set in the second setting information; If the first CORESET is not configured in the second configuration information, apply a first parameter list or the first default table to the second PDSCH time domain resource allocation configuration; A terminal device that applies a second parameter list or the first default table to the second PDSCH time domain resource allocation setting when the first CORESET is set in the second setting information.

2. The control unit When the first CORESET is set in the second BWP, If the second parameter list is provided in the second configuration information, applying the second parameter list to the second PDSCH time domain resource allocation configuration; 2. The terminal device according to claim 1, wherein if the second parameter list is not provided in the second configuration information, the terminal device applies the first default table to the second PDSCH time domain resource allocation configuration.

3. The control unit When the first CORESET is not set in the second BWP, If the first parameter list is provided in the first configuration information, applying the first parameter list to the second PDSCH time domain resource allocation configuration; 2. The terminal device according to claim 1, wherein if the first parameter list is not provided in the first configuration information, the terminal device applies the first default table to the second PDSCH time domain resource allocation configuration.

4. A base station device, a transmitter configured to transmit first downlink control information (DCI) with a CRC scrambled with an SI-RNTI and transmit a system information block (SIB) via a first physical downlink shared channel (PDSCH) scheduled on a first time resource in a first BWP of a first cell, and to transmit second DCI with a CRC scrambled with an RA-RNTI in a common search space in a second BWP of the first cell and transmit a random access response via a second PDSCH scheduled on a second time resource; a control unit that determines the first value indicated by a first field included in the first DCI using the first time resource and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between a first value and a time resource, and determines the second value indicated by a second field included in the second DCI using the second time resource and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between a second value and a time resource, The SIB provides first setting information of the first BWP and second setting information of the second BWP, and the control unit applies a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation configuration; Determine whether a first control resource set (CORESET) linked to the common search space is set in the second setting information; When the first CORESET is not set in the second configuration information, applying a first parameter list or the first default table to the second PDSCH time domain resource allocation configuration; A base station device that applies a second parameter list or the first default table to the second PDSCH time domain resource allocation configuration when the first CORESET is configured in the second configuration information.

5. The control unit When the first CORESET is set in the second BWP, If the second parameter list is provided in the second configuration information, applying the second parameter list to the second PDSCH time domain resource allocation configuration; The base station apparatus according to claim 4, wherein, when the second parameter list is not provided in the second configuration information, the first default table is applied to the second PDSCH time domain resource allocation configuration.

6. The control unit When the first CORESET is not set in the second BWP, If the first parameter list is provided in the first configuration information, applying the first parameter list to the second PDSCH time domain resource allocation configuration; The base station apparatus according to claim 4 , wherein, when the first parameter list is not provided in the first configuration information, the first default table is applied to the second PDSCH time domain resource allocation configuration.

7. A communication method for a base station device, comprising: In a first BWP of a first cell, transmitting first downlink control information (DCI) with a CRC scrambled with an SI-RNTI and transmitting a system information block (SIB) via a first physical downlink shared channel (PDSCH) scheduled on a first time resource; in a second BWP of the first cell, transmitting second DCI with a CRC scrambled with an RA-RNTI in a common search space and transmitting a random access response via a second PDSCH scheduled on a second time resource; determining the first value indicated by a first field included in the first DCI using the first time resource and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between a first value and a time resource; and determining the second value indicated by a second field included in the second DCI using the second time resource and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between a second value and a time resource; The SIB provides first configuration information of the first BWP and second configuration information of the second BWP; Applying a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation configuration; Determine whether a first control resource set (CORESET) linked to the common search space is set in the second setting information; When the first CORESET is not set in the second configuration information, applying a first parameter list or the first default table to the second PDSCH time domain resource allocation configuration; A communication method that applies a second parameter list or the first default table to the second PDSCH time domain resource allocation configuration when the first CORESET is configured in the second configuration information.

Images