Terminal device, base station device, and communication method

Abstract

To allow a terminal device and a base station device to communicate efficiently.SOLUTION: A terminal device receives a first DCI accompanied by an SI-RNTI in a first BWP, receives a SIB on a first time resource, receives a second DCI accompanied by an RA-RNTI in a second BWP, receives an RAR on 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 second parameter list to the second setting if a second parameter list is provided in the SIB, and applies the first parameter list or a first default table if not provided.SELECTED DRAWING: Figure 16

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 enhanced Mobile Broadband (eMBB), 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 massive Machine Type Communication (mMTC), which connects a large number of machine-type devices such as the Internet of Things (IoT). Furthermore, in the future release of NR, Release 17, it is expected that advanced features such as eMBB and URLLC will be implemented for sensor networks, surveillance cameras, and / or wearable devices. There is currently research underway into reduced capability (REDCAP) NR devices that do not require the same 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 wireless communication system described above. [Means for solving the problem]

[0006] (1) In order to achieve the above object, the 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 outputs system information The first physical downlink shared channel (SIB) is scheduled in the first time resource. and receiving the RA-RNTI via the PDSCH in the second BWP of the first cell. a receiving unit for receiving a second DCI with a quantized CRC and receiving a random access response via a second PDSCH scheduled in a second time resource; and a control unit that determines the first time resource using a first value indicated by a field of the second 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, wherein 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 second parameter list is provided in the SIB, and if the second parameter list is provided in the SIB, applies the second parameter list to the second PDSCH time domain resource allocation configuration, and if the second parameter list is not provided in the SIB, applies the first parameter list or the first default table to the second PDSCH time domain resource allocation configuration.

[0007] (2) In addition, the base station device according to one aspect of the present invention transmits first downlink control information (DCI) accompanied with a CRC scrambled by the SI-RNTI in a first BWP of a first cell, A System Information Block (SIB) is sent to the first physical downlink scheduled in the first time resource. and transmitting the RA-RNTI in a second BWP of the first cell via a PDSCH. a transmitter for transmitting a second DCI with a CRC scrambled in said first time resource and a random access response via a second PDSCH scheduled in said first time resource; and a first PDSCH time domain resource allocation indicating a correspondence between the first value and a time resource. and a control unit that determines a first value indicated by a first field included in the first DCI using a second time resource and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and the time domain resource, and determines 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 domain resource, wherein the control unit determines a second value indicated by a second field included in the second DCI using a first default table, a second default table, or a third default table for the first PDSCH time domain resource allocation configuration. and if the second parameter list is provided in the SIB, applying the second parameter list to the second PDSCH time domain resource allocation configuration, and if the second parameter list is not provided in the SIB, applying the previous parameter list to the second PDSCH time domain resource allocation configuration. The first parameter list or the first default table is applied.

[0008] (3) 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, transmit a second DCI with a CRC scrambled by the RA-RNTI and transmit a random access response via a second PDSCH scheduled in the second time resource; Determine a first value indicated by a first field included in the first DCI by using the first time resource and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the first value and a time resource, and determine a second value indicated by a second field included in the second DCI by using the second time resource and a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the second value and a time resource. determine a second value indicated by the SIB, apply a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation configuration, and if the second parameter list is provided in the SIB, apply the second parameter list to the second PDSCH time domain resource allocation configuration, and determine a second value indicated by the SIB, If not provided in the second PDSCH time domain resource allocation configuration, the first parameter The first table or the first default table is applied. Effect of the Invention

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

[0010] [Figure 1] 1 is a diagram showing the concept of a wireless communication system according to an embodiment of the present invention. [Diagram 2] A figure showing an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram showing 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. [Diagram 5] A diagram showing resources in which a PSS, an SSS, a PBCH and a DMRS for a PBCH are arranged within an SS / PBCH block according to an embodiment of the present invention. [Figure 6] 11 is a diagram showing an example of a parameter configuration of the information element BWP-DownlinkCommon of the 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. 2 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. 2 is a diagram showing an example of a PDSCH mapping type according to an embodiment of the present invention. [Figure 10] FIG. 2 is a diagram showing 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. 2 is a diagram showing an example of a default table A according to the embodiment of the present invention. [Figure 12] FIG. 13 is a diagram showing an example of a default table B according to the embodiment of the present invention. [Figure 13] FIG. 13 is a diagram showing an example of a default table C according to the embodiment of the present invention. [Figure 14] FIG. 1 is a diagram showing an example of calculating a SLIV according to an embodiment of the present invention. [Figure 15] A flow diagram showing an example of processing related to receiving DCI, SIB, and random access response in terminal device 1 according to an embodiment of the present invention. [Figure 16] 1 is a flow diagram showing an example of a process related to determining / specifying / configuring / setting a resource allocation table to be applied to PDSCH time domain resource allocation in a terminal device 1 according to an embodiment of the present invention. [Figure 17] FIG. 11 is a flow diagram showing another example of processing related to determining / specifying / configuring / setting a resource allocation table to be applied to PDSCH time domain resource allocation in the 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 PREFERRED EMBODIMENTS

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

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

[0013] 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), a 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 include 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 in 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, which are communication ranges (communication areas) 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.

[0014] 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. can be.

[0015] In FIG. 1, in wireless communication between a terminal device 1 and a base station device 3, a cyclic prefix is ​​used. Alternatively, orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single-carrier frequency division multiplexing (SC-FDM), or discrete Fourier transform spread OFDM (DFT-S-OFDM) may be used, or other transmission methods may be used.

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

[0017] 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 added instead of the CP. Also, the CP and / or zero padding may be added both in front and rear.

[0018] One aspect of the present embodiment is a wireless access technology (RAT) such as LTE, LTE-A, or LTE-A Pro. Carrier aggregation (CA) with LTE Access Technology (LTE) is operated in dual connectivity (DC) In this case, the SpCell may be used in some or all of the cells or cell groups, carriers or carrier groups (for example, a primary cell (PCell), a secondary cell (SCell), a primary secondary cell (PSCell), a master cell group (MCG), a secondary cell group (SCG), etc.). Also, one aspect of the present embodiment may be used in a standalone manner that operates alone. 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 the absence of 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).

[0019] 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 been started, or a cell designated as a 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 after that. 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 an uplink, among one or more secondary cells where the terminal device 1 is configured. In addition, a subset of two types 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.

[0020] In the wireless communication system of the present embodiment, TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex) may be applied. 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 to which the TDD method is applied and cells to which the FDD method is applied may be aggregated. The TDD method may be called an unpaired spectrum operation. The FDD method may be called a paired spectrum operation.

[0021] In the following, a subframe will be described. In this embodiment, the following 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.

[0022] 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. For example, if the subcarrier spacing of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix) is used, the time length of each bit is defined by the subcarrier spacing. , 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 X=14. can be expanded in the same way. The uplink slot is also defined in the same way, 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 called the downlink BWP, and the BWP used in the uplink may be called 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 a transmission period of a transport block.

[0023] The signals or physical channels transmitted in each slot may be represented by a resource grid. The resource grid 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 a subcarrier number and an OFDM symbol number.

[0024] 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, when 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 μ described later. That is, the resource grid is composed 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. That is, the resource grid is composed of (48*12*Nmax,μ) REs.

[0025] As the RB, a reference resource block (reference RB), a common resource block (CRB: Common RB), a PRB, and a virtual resource block (VRB: Virtual RB) are defined. One RB is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may constitute a resource block at a subcarrier interval 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 be provided as a common reference point for the grid of resource blocks. The position of point A may be determined / specified by a parameter offsetToPointA included in SIB1. The parameter offsetToPointA is a parameter indicating a 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 the initial cell selection. However, the unit of the frequency offset is a resource block with a subcarrier spacing of 15 kHz in the case of frequency range (FR) 1, and a resource block with a subcarrier spacing of 60 kHz in the case of frequency range 2. However, the position of point A may be indicated by the frequency position ARFCN (Absolute radio-frequency channel number) by the RRC parameter absoluteFrequencyPointA. The CRBs are RBs numbered in ascending order from 0 in each subcarrier spacing setting μ from point A. Therefore, the number of the CRB is defined for each subcarrier spacing setting μ. The CRB corresponding to the subcarrier spacing setting μ may be referred to as 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.A PRB is an RB numbered in ascending order starting from 0 included in a BWP of each subcarrier spacing setting μ, and a PRB is an RB numbered in ascending order starting from 0 included in a BWP that is 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.

[0026] 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 BWP at a certain time (active The terminal device 1 may not expect to receive a PDSCH, a PDCCH, or a 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.

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

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

[0029] Next, we will explain subframes, slots, and minislots. This figure shows an example of the relationship between a subframe, a slot, and a minislot 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 interval, and the number of OFDM symbols included in a slot is 7 or 14 (however, each symbol (If the CP added to the frame is an Extended CP, it may be 6 or 12.) The slot length depends on the subcarrier spacing. Here, if the subcarrier spacing is 15 kHz, one subframe is includes 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.

[0030] A minislot (which may also be called a subslot) is a time unit consisting of a number of OFDM symbols fewer 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 constituting the slot. The minimum unit of scheduling may be a slot or a minislot. Allocating a minislot may be referred to as non-slot based scheduling. Scheduling a minislot may be expressed as scheduling a resource in which the relative time positions of the start positions of the reference signal and data 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.

[0031] 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 by using an RRC message including a predetermined higher layer parameter received from the base station device 3, or is set by a PDCCH of a specific DCI format (e.g., DCI format 2_0) received from the base station device 3. In this embodiment, a slot format that sets each symbol in a slot to either uplink, downlink, or flexible is called a slot format. One slot format may include a downlink symbol, an uplink symbol, and a flexible symbol.

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

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

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

[0035] 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)

[0036] The PBCH is a Master Information Block (MIB) that contains important system information required by the terminal device 1. It is used to broadcast the PBCH (Essential Information Block, Essential Information Block, 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 the SS / PBCH block (also called synchronization signal block, SS block, SSB) The SIB1 may include information indicating the setting of the PDCCH for the SIB1. , which contains information necessary for evaluating whether the terminal device 1 is allowed to connect to the cell, Information that determines the scheduling of other system information blocks (SIBs) However, the information indicating the PDCCH configuration for SIB1 includes the control resource set CORESET#0 (CORESET#0 is also called CORESET0 or common CORESET) information that determines the common search space and / or the required PDCCH parameters. However, CORESET indicates a resource element 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 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 DCI with a CRC scrambled with SI-RNTI in the PDCCH 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.

[0037] The PBCH may 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 Radio 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.

[0038] 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 the 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 determined by using a quasi-co-location (QCL) assumption for multiple transmit beams, transmit filter settings, and / or receive spatial parameters. When transmitting the blocks, the time order within a predefined or set period may be indicated, and the terminal device may recognize the difference in time index as different QCL assumptions regarding transmit beams, transmit filter settings and / or receive spatial parameters.

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

[0040] 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

[0041] DCI format 0_0 is for scheduling PUSCH in a serving cell. DCI format 0_0 may be used for PUSCH scheduling information (frequency domain The DCI information may include information indicating the DCI domain resource allocation (domain 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, 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.

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

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

[0044] DCI format 1_0 is 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 (domain resource allocation and time domain resource allocation). Among the identifiers, the matrix 1_0 includes C-RNTI, CS-RNTI, MCS-C-RNTI, and Paging RNTI (P-RNTI). A CRC scrambled by any one of the System Information (SI)-RNTI, the Random access (RA)-RNTI, and / or the TC-RNTI may be added to the DCI format 1_0. The DCI format 1_0 may be monitored in a common search space or a UE-specific search space.

[0045] DCI format 1_1 is for scheduling PDSCH in a serving cell. DCI format 1_1 may be used for scheduling information of PDSCH (frequency domain information indicating BWP, information indicating transmission The 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 the C-RNTI, CS-RNTI, and / or MCS-C-RNTI among the RNTIs may be added to the DCI format 1_1. The DCI format 1_1 may be monitored in a UE-specific search space.

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

[0047] DCI format 2_0 is used to notify the slot format of one or more slots. The slot format is defined as a classification of each OFDM symbol in a slot as either downlink, flexible, or uplink. For example, when the slot format is 28, DDDDDDDDDDDDFU is applied to 14 OFDM symbols in a slot in which slot format 28 is specified. Here, D is a downlink symbol, F is a flexible symbol, and U is an uplink symbol. Slots will be described later.

[0048] The 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. Note that this information may be called a preemption instruction (discontinuous transmission instruction).

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

[0050] The DCI format 2_3 is a format for transmitting a sounding reference signal (SRS) by one or more terminal devices 1. In addition, an SRS request may be transmitted together with the TPC command. In addition, in DCI format 2_3, an uplink without PUSCH and PUCCH, or an SRS transmission power control is linked to a PUSCH transmission power control, For the uplink where no SRS is present, SRS requests and TPC commands may be defined.

[0051] The 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.

[0052] 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. The SI-RNTI may be an identifier used for broadcasting system information. The P-RNTI may be an identifier used for paging and notifying of system information changes. The C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying a terminal device within a cell. The TC-RNTI is an identifier for identifying the terminal device 1 that transmitted the random access preamble during CBRA.

[0053] 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 the PDSCH or PUSCH transmission in one or more slots. The TC-RNTI is used to schedule the retransmission of the random access message 3 and the transmission of the 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.

[0054] The C-RNTI and / or other RNTIs may have different values ​​corresponding to the type of traffic of 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 according to 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).

[0055] The PUCCH is used in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3). Used to transmit Uplink Control Information (UCI) Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. The uplink control information may also include a scheduling request (SR) used to request a UL-SCH resource. 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).

[0056] The PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the Medium Access Control (MAC) layer, and is also used to transmit system information (SI: System Information), paging information, random access response (RAR), etc. in the downlink.

[0057] PUSCH is used for 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. In addition, the PUSCH is used to transmit only CSI or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only the UCI.

[0058] 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. The base station device 3 and the terminal device 1 may also transmit and receive a MAC control element in a Medium Access Control (MAC) layer. 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. The upper layer here means an upper layer seen from the physical layer, and may include one or more of the MAC layer, the RRC layer, the RLC layer, the PDCP layer, the NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the upper layer may include one or more of the RRC layer, the RLC layer, the PDCP layer, the NAS layer, etc. Hereinafter, the meaning of "A is given (provided) by the upper layer" or "A is given (provided) by the upper layer" may mean that the upper layer (mainly the RRC layer or the MAC layer, etc.) 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 the 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 the upper layer parameters to the terminal device 1 may mean that the upper layer parameters are given (provided) to the terminal device 1.For example, setting an upper layer parameter 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 parameter in an upper layer. However, setting an upper layer parameter in the terminal device 1 may also include setting a default parameter that is given in advance to the upper layer of the terminal device 1.

[0059] The PDSCH or the 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. In addition, the PUSCH may be used to transmit UE capabilities in the uplink.

[0060] 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)

[0061] The synchronization signal is the Primary Synchronization Signal (PSS) and the Sector Synchronization Signal (SES). The PSS and SSS may be used to detect the cell ID.

[0062] 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 be called a transmit or receive filter setting, or a spatial domain transmit filter or a spatial domain receive filter.

[0063] 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 the downlink CSI. The reference signal may also be used to calculate the downlink CSI, such as radio parameters, numerology such as subcarrier spacing, window synchronization of FFT, etc. This may be used for fine synchronization where

[0064] 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)

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

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

[0067] The DMRS is used to demodulate the modulated signal. Note that the DMRS includes Two types of reference signals may be defined: a reference signal for demodulating the PUSCH and a reference signal for demodulating the PUSCH, and both may be referred to as DMRS. The SRS is used for uplink Channel State Information (CSI) measurement, channel sounding, and beam management. The PTRS is used to track the phase in time to compensate for frequency offsets caused by phase noise.

[0068] 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. In this embodiment, 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.

[0069] BCH, UL-SCH and DL-SCH are transport channels. A channel used in the Medium Access Control (MAC) layer is called a transport channel. A unit of a 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.

[0070] FIG. 4 shows the SS / PBCH block (also called the 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 half frame with SS / PBCH block or 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.

[0071] The SS / PBCH block is a block that 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 a signal / channel included in the SS / PBCH block is expressed 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.

[0072] In Fig. 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 arranged within the SS / PBCH block.

[0073] 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. (subcarriers with subcarrier numbers 56 to 182 relative to the starting subcarrier of the SS / PBCH block).

[0074] 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. (subcarriers with subcarrier numbers 56 to 182 relative to the starting subcarrier of the SS / PBCH block).

[0075] PBCH and DMRS are the second, third, and fourth symbols in the SS / PBCH block (SS / PBCH block The PBCH modulation symbol sequence may be mapped to OFDM symbols having OFDM symbol numbers 1, 2, and 3 relative to the starting symbol of M. symb The SS / PBCH block may be composed of symbols, and may be mapped to resources to which the 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 from 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 from 0 to 47 and 192 to 239 relative to the starting subcarrier of the SS / PBCH block). The symbol sequence of the DMRS is composed of 144 symbols, and may be mapped to the 1st to 240th subcarriers of the second and fourth symbols in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the SS / PBCH block), and to the 1st 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 start subcarrier of the SS / PBCH block), one subcarrier for every four subcarriers. For example, of the 240 subcarriers, the modulation symbols of the PBCH may be mapped to 180 subcarriers, and the DMRS for the PBCH may be mapped to 60 subcarriers.

[0076] Different SS / PBCH blocks in an SS burst set may be assigned different SSB indices. 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. Also, the SSB period to be set for a connected (Connected or RRC_Connected) terminal device 1 may be set by an RRC parameter. Also, 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 that may potentially be transmitted, and the base station device 3 may actually decide whether to transmit or not. Also, the SSB period for which the SS / PBCH block is used for initial access may be defined in advance in a specification or the like. For example, the terminal device 1 performing initial access may consider the SSB period to be 20 milliseconds.

[0077] The time position of the SS burst set to which the SS / PBCH block is mapped is the time position contained in the PBCH. The SS / PBCH block may be determined based on information for determining a system frame number (SFN) and / or information for determining a half frame. Device 1 determines the current system frame number and half frame number based on the received SS / PBCH block. A group may be specified.

[0078] The SS / PBCH block is assigned an SSB index (which may be referred to as an SS / PBCH block index) according to its time 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.

[0079] SS / PBCH blocks with the same relative time within each SS burst set in the 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 the multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Additionally, antenna ports with SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL with respect to average delay, Doppler shift, and spatial correlation.

[0080] Within a period of a certain SS burst set, SS / PBCH blocks that are 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 possibly reference signals) that are QCLs may be referred to as a QCL configuration.

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

[0082] SS / PBCH blocks with the same relative time within each SS burst set in the 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 the multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Additionally, antenna ports with SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL with respect to average 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 QCL with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation.

[0084] 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 For example, there 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).

[0085] The initial downlink BWP may be set by a parameter provided in the MIB, a parameter provided in SIB1, a parameter provided in a SIB, and / or an RRC parameter. For example, the initial downlink BWP may be set 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 set by a parameter initialDownlinkBWP included in the parameter downlinkConfigCommonRedCap provided in SIB1 (or another SIB). However, initialDownlinkBWP may be a parameter indicating a UE-specific (UE-specific, dedicated) setting of the initial downlink BWP for a UE.

[0086] 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 downlinkConfigCommon may be included in a parameter ( The parameter may include a parameter indicating a first initial downlink BWP configuration of a serving cell (e.g., referred to as frequencyInfoDL), and a parameter indicating a first initial downlink BWP configuration of a serving cell (e.g., referred to as initialDownlinkBWP).

[0087] SIB1 may be transmitted including downlinkConfigCommonRedCap, which is a common downlink configuration parameter of a certain cell. The first initial downlink BWP 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 a part or all of the parameter configuration of the initialDownlinkBWP included in downlinkConfigCommon, and each parameter may be configuration information for the second initial downlink BWP (which may be a separate initial downlink BWP). The second initial downlink BWP may be referred to as the second downlink BWP.

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

[0089] FIG. 6 shows information on the initialDownlinkBWP and separateInitialDownlinkBWP according to this embodiment. An example of the parameter configuration of the information element (IE: Information Element) BWP-DownlinkCommon is shown below. The initialDownlinkBWP and separateInitialDownlinkBWP according to this embodiment may include generic parameters genericParameters of the initial downlink BWP, cell-specific parameters pdcch-ConfigCommon of the PDCCH, cell-specific parameters pdsch-ConfigCommon of the PDSCH, and / or other parameters. The information element of the separateInitialDownlinkBWP, BWP-DownlinkCommon, 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.

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

[0091] 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 subcarrierSpacing indicating the subcarrier spacing used in the corresponding BWP, a parameter locationAndBandwidth indicating the location and bandwidth (number of resource blocks (total number)) in the frequency domain of the corresponding BWP, and / or a parameter cyclicPrefix indicating whether the standard CP (cyclic prefix) or the extended CP is used in the corresponding BWP. That is, 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 start 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 offsetToCarrier set by 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. When cyclicPrefix is ​​not included (not set) in genericParameters, the terminal device 1 may use a standard CP instead of an extended CP.

[0092] The frequencyInfoDL includes 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 interval.

[0093] SCS-SpecificCarrier is a parameter that indicates the actual carrier position, bandwidth, and carrier bandwidth. More specifically, an information element SCS-SpecificCarrier in frequencyInfoDL indicates a setting for a specific carrier, and includes subcarrierSpacing, carrierbandwidth, and / or offsetToCarrier. Indicates carrier spacing (e.g., 15kHz or 30kHz for FR1, 60kHz or 120kHz for FR2) The carrierbandwidth is a parameter indicating the bandwidth of the carrier in number of PRBs (Physical Resource Blocks). The 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 number of PRBs (where the subcarrier spacing is the subcarrier spacing of the carrier given by subcarrierSpacing). For example, for a downlink carrier, the carrier bandwidth is given by the higher layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier spacing, and the 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 higher 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.

[0094] If neither initialDownlinkBWP nor separateInitialDownlinkBWP is provided (set) in SIB1 received by the terminal device 1 (which may be another SIB or RRC parameter) (initialDownlinkBWP may not be provided (set) in either downlinkConfigCommon or downlinkConfigCommonRedCap in the 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 (CORESET#0, etc.) 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. When 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 with the initialDownlinkBWP. When initialDownlinkBWP (which may be separateInitialDownlinkBWP) is not provided / set in downlinkConfigCommonRedCap in SIB1 received by the terminal device 1, 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 with the initialDownlinkBWP.If an initialDownlinkBWP (which may be a separateInitialDownlinkBWP) is not provided / set in downlinkConfigCommonRedCap in SIB1 received by the terminal device 1, and an initialDownlinkBWP is provided / set in downlinkConfigCommon in 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) in a 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.

[0095] However, the fact that initialDownlinkBWP is provided in downlinkConfigCommon does not mean that the RRC parameters The meter receives the initialDownlinkBWP and the RRC connection is established (for example, RRCSetup , RRCResume and / or RRCReestablishment has been 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. 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 of CORESET#0. Determining / specifying the initial 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 determine / specify the initial downlink BWP by the CORESET#0 until the RRC connection is established, and may determine / specify the initial downlink BWP by the locationAndBandwidth included in the initialDownlinkBWP after the RRC connection is established.

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

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

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

[0099] The 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.

[0100] The initial uplink BWP may be configured by a parameter provided in the MIB, a parameter provided in SIB1, a parameter provided in the 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.

[0101] The initial uplink BWP may be defined / set by the initialUplinkBWP provided in SIB1 (which may be REDCAP SIB1, other SIBs, or RRC parameters). 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 by parameters included in the initialUplinkBWP provided by the received SIB1.

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

[0103] 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 an 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 as to include the band of the downlink channel to receive the applicable band of the RF circuit. 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 the allocated bandwidth), the terminal device 1 may adjust / re-adjust 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 the 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.

[0104] The terminal device 1 according to the present invention receives / specifies the configuration information of the initial downlink BWP by the upper layer parameter initialDownlinkBWP in downlinkConfigCommon or the upper layer parameter initialDownlinkBWP in downlinkConfigCommonRedCap. However, the initialDownlinkBWP may be included in SIB1 or may be included in any RRC message. For example, the configuration information of the initial downlink BWP may include information indicating the frequency position 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.

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

[0106] An 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. An 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.

[0107] 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 to a predetermined table as an index. 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 repetitions of PDCCH.

[0108] The commonSearchSpaceList is a parameter indicating a list of additional common search spaces (CSS), and sets a common search space 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 a serving cell.

[0109] The searchSpaceSIB1 includes an information element SearchSpaceId indicating an 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 including the SIB1 message from the ID of the search space indicated by searchSpaceSIB1 and the list of common search spaces indicated by commonSearchSpaceList, and may further identify a CORESET used to monitor a PDCCH that schedules the SIB1 message and a setting (e.g., a frequency position) of the CORESET.

[0110] 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 from the ID of the search space indicated by the searchSpaceOtherSystemInformation and the list of common search spaces indicated by the commonSearchSpaceList, and may further identify a CORESET used to monitor a PDCCH that schedules a PDSCH that includes OSI and a setting (e.g., a frequency position) of the CORESET.

[0111] The pagingSearchSpace includes an information element SearchSpaceId indicating an 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, from the ID of the search space indicated by the pagingSearchSpace and the list of common search spaces indicated by the commonSearchSpaceList, and may further identify a CORESET used to monitor a PDCCH that schedules a PDSCH that includes paging information and a setting (e.g., a frequency position) of the CORESET.

[0112] The 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 random access from the ID of the search space indicated by the ra-SearchSpace and the list of common search spaces indicated by the commonSearchSpaceList. It is also possible to specify a CSS to be used for monitoring a PDCCH that schedules a PDSCH that includes a radio access response (RAR), and further specify a CORESET to be used for monitoring a PDCCH that schedules a PDSCH that includes an RAR, and the setting (e.g., frequency location) of the CORESET.

[0113] The multiplexing pattern of PBCH and CORESET corresponds to the SS / PBCH block corresponding to the PBCH in which 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 the PBCH and CORESET is 1, the PBCH and CORESET#0 are time-multiplexed into different symbols.

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

[0115] The above offset is the minimum RB index of the resource blocks assigned to CORESET#0. The first resource block of the corresponding REDCAP PBCH overlaps with the common resource block The offset indicates the offset to the lowest RB index in the block, starting from CORESET#0. The corresponding SS / PBCH block is selected from the smallest RB index of the resource blocks allocated to the The smallest RB index of the common resource block that overlaps with the first resource block of the block. It may also indicate an offset into the

[0116] The terminal device 1 receives the initialDownlinkBWP (or separateInitialDownlinkBWP) including the RRC parameter pdcch-ConfigCommon through SIB1, another SIB, or RRC signaling, and monitors the PDCCH based on the parameter.

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

[0118] 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 column i, n0 and the system frame number are determined based on the parameters O and M shown in the table.

[0119] Multiple "frequency locations and bandwidths" for multiple initial downlink BWPs in a cell " is set (locationAndBandwidth in initialDownlinkBWP in downlinkConfigCommon and locationAndBandwidth in separateInitialDownlinkBWP in downlinkConfigCommonRedCap) (may be the case where 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 in initialDownlinkBWP in downlinkConfigCommon, or may be a cell-specific parameter of the PDCCH that is common to the initial downlink BWP set in initialDownlinkBWP in downlinkConfigCommon and the initial downlink BWP set in separateInitialDownlinkBWP in downlinkConfigCommonRedCap.

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

[0121] 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 (multiple initial downlink BWPs may be set in a certain cell), pdsch-ConfigCommon or each parameter of the 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.

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

[0123] 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 in locationAndBandwidth in downlinkConfigCommonRedCap, the base station device 3 can transmit the downlink channel and the downlink signal appropriately. By including locationAndBandwidth in downlinkConfigCommonRedCap in SIB1 (which may be other SIB or RRC signaling), the base station device 3 can transmit the downlink channel and the reference signal corresponding to the second initial downlink BWP to the terminal device 1 that does not support the frequency position and / or bandwidth of the first initial downlink BWP, and transmit the downlink channel and the reference signal corresponding to the first initial downlink BWP to the terminal device 1 that supports the frequency position and the bandwidth of the first initial downlink BWP. When setting the initial downlink BWP of the frequency position and / or bandwidth supported by all the terminal devices 1 in locationAndBandwidth in initialDownlinkBWP, the base station device 3 does not need to include locationAndBandwidth in downlinkConfigCommonRedCap in SIB1 (which may be other SIB or RRC signaling).

[0124] The terminal device 1 may specify / determine the subcarrier spacing used in all channels and reference signals in the initial downlink BWP by using the subcarrierSpacing included in the genericParameters in the initialDownlinkBWP in downlinkConfigCommon, regardless of whether locationAndBandwidth is included in the 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 the cyclicPrefix included in the genericParameters in the initialDownlinkBWP in downlinkConfigCommon, regardless of whether locationAndBandwidth is included in the downlinkConfigCommonRedCap in SIB1 (which may be another SIB or RRC signaling).

[0125] The terminal device 1 may specify / 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 other SIB or RRC signaling), and monitor / receive the PDCCH. The terminal device 1 may specify / 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 other SIB or RRC signaling), and receive the PDSCH.

[0126] When the terminal device 1 receives locationAndBandwidth included in downlinkConfigCommonRedCap in SIB1 (may be other SIB) and specifies / determines the frequency location and bandwidth of the initial downlink BWP (may be referred to as separate initial downlink BWP) based on the locationAndBandwidth, CORESET#0 is set 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 by locationAndBandwidth included in downlinkConfigCommonRedCap in the received SIB1 (may be other SIB). However, when the initial downlink BWP is set as CORESET#0 until the RRC connection is established, re-established or resumed, the terminal device 1 may perform the random access procedure using the initial downlink BWP determined / specified by CORESET#0.

[0127] When the terminal device 1 receives locationAndBandwidth included in downlinkConfigCommonRedCap in SIB1 (may be other SIB) and specifies / determines the frequency location and bandwidth of the initial downlink BWP (may be referred to as separate initial downlink BWP) based on the locationAndBandwidth, CORESET#0 is set as the initial downlink BWP until the SIB1 is received, and after SIB1 (may be other 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 (may be other SIB), the terminal device 1 may perform a random access procedure using the initial downlink BWP determined / specified by the locationAndBandwidth.

[0128] 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 the locationAndBandwidth included in the downlinkConfigCommonRedCap in the SIB1 based on the information included in the SIB1 (which may be another SIB). The parameter initialBwpTiming indicating the timing for applying the locationAndBandwidth included in the downlinkConfigCommonRedCap in the SIB1 (which may be another SIB) may be 1-bit information.

[0129] 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 different frequency position and / or bandwidth from the first initial downlink BWP is set, The bandwidth of the rate initial downlink BWP is determined by the synchronous It may not contain a signal block. Separate initial downlink BWP for paging, la When 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 The base station device 3 may transmit an additional synchronization signal block (hereinafter referred to as an additional SSB) thereafter. The base station device 3 is specified / determined by locationAndBandwidth in 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 in 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 a non-cell defining SSB: NCD-SSB) that is not a synchronization signal block that defines a cell (referred to as a cell defining SSB: CD-SSB). For example, the additional synchronization signal block may not have a synchronization raster as its center frequency.

[0130] FIG. 8 is a diagram showing an overview 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 set in a certain cell. However, the initial downlink BWP may be the band of CORESET#0. 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) in the band. The terminal device 1 that has received the synchronization signal block identifies the frequency position of CORESET#0, and identifies the frequency position and time position of the PDSCH that includes SIB1 by the PDCCH received in CORESET#0. The terminal device 1 that has received the PDSCH that includes SIB1 identifies the separate SIB by the parameter locationAndBandwidth included in downlinkConfigCommonRedCap in SIB1 (or may be another SIB identified by the SIB1). Identify / determine the frequency location (including bandwidth) of the rate initial downlink BWP. 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 in the separate initial downlink BWP and receive the additional synchronization signal block.

[0131] The terminal device 1 uses DCI format 1_0, DCI format 1_1, or DCI format 1_2. By detecting the PDCCH including the PDSCH, 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.

[0132] The PDSCH mapping type includes PDSCH mapping type A and PDSCH mapping type B. For PDSCH mapping type A, S takes values ​​from 0 to 3. L takes values ​​from 3 to 14. However, the sum of S and L can take a value from 3 to 14. In PDSCH mapping type B, S can take a value from 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.

[0133] 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 mapping depends on the type of PDSCH mapping. It depends on the type of the PDSCH mapping. For PDSCH mapping type A, the position of the first DMRS symbol may be indicated in 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 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 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 PDSCH may be the fourth symbol in the slot. Here, S can take the value of 3 only if dmrs-TypeA-Position is set to 'pos3'. That is, if dmrs-TypeA-Position is set to 'pos2', S can take 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.

[0134] FIG. 9 is a diagram showing an example of a PDSCH mapping type according to this embodiment. FIG. 9(B) is a diagram showing an example of PDSCH mapping type A. In FIG. 9(A), S of the assigned PDSCH is 3. L of the assigned 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 assigned PDSCH is 4. L of the assigned 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 assigned.

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

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

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

[0138] The contention-based random access procedure is initiated by a PDCCH order, a MAC entity, a beam failure indication from lower layers, or by 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 to the MAC entity of the terminal device 1, if a certain condition is satisfied, the MAC entity of the terminal device 1 starts a random access procedure. When provided by the physical layer, the procedure of determining whether a certain condition is met and initiating a 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 the random access procedure initiated by the scheduling request procedure. The random access procedure for a beam failure recovery request is considered as a random access procedure initiated by the MAC entity. A distinction may be made between the random access procedure for beam failure recovery requests and the random access procedure initiated by the scheduling request procedure, since different procedures may be used for the random access procedure for beam failure recovery requests and the random access procedure initiated by the scheduling request procedure. The random access procedure for beam failure recovery requests and the scheduling request procedure may be random access procedures initiated by the MAC entity. In one embodiment, the random access procedure initiated by the scheduling request procedure is referred to as the MAC entity initiated random access procedure, and the beam loss is referred to as the beam loss procedure. The random access procedure for a beam failure recovery request may be referred to as a random access procedure by 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 mean the start of the random access procedure for a beam failure recovery request.

[0139] The terminal device 1 performs a contention-based random access procedure at the time of initial access from a state where it is not connected (communicating) with the base station device 3, and / or at the time of 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 the contention-based random access is not limited to these.

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

[0141] In the non-contention based random access, when the base station device 3 and the terminal device 1 are connected but the handover or the transmission timing of the mobile station device is not valid, the terminal device 1 and the base station device 3 can be quickly connected to each other. This may be used to achieve uplink synchronization between the device 3 and the The access transmits 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.

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

[0143] The terminal device 1 of this embodiment performs a random access procedure by using a higher layer The random access setting information is received via the

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

[0145] 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 by a reference signal (for example, SS / PBCH block and / or CSI-RS) received from the base station device 3.

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

[0147] <Message 1> When transmittable uplink data or transmittable sidelink data is generated, the terminal device 1 transmits a preamble (random The random access preamble may be called message 1 or Msg1. The information is notified to the base station device 3 by a sequence of numbers. For example, 64 types If such a sequence 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.

[0148] <Message 2> The base station device 3 that has received the random access preamble transmits a random access response (RAR: Random Access Response) including an uplink grant for instructing the terminal device 1 to transmit. ) and transmits the generated random access response to the terminal device 1 on the PDSCH. The random access response may be referred to as a message 2 or Msg2. The base station device 3 also calculates a transmission timing shift between the terminal device 1 and the base station device 3 from the received random access preamble, and includes in the message 2 transmission timing adjustment information (Timing Advance Command) for adjusting the shift. The base station device 3 also includes in the message 2 a random access preamble identifier corresponding to the received random access preamble. The base station device 3 also transmits, on the PDCCH, DCI to which a CRC scrambled with RA-RNTI (Random Access-Radio Network Temporary Identity) is added, for indicating 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.

[0149] <Message 3> The terminal device 1 that transmitted the random access preamble The RAR monitors the PDCCH for a random access response identified by the RA-RNTI within a period of several subframes (called the RAR window) after the random access transmission. 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 transmits the random access preamble to the random access response. 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. Using the uplink grant included in the response, the data stored in the buffer is transmitted to the base station apparatus 3. The data transmitted at this time using the uplink grant is referred to as a message 3 or Msg3.

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

[0151] <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 in the resource, the base station device 3 detects 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.

[0152] 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, the contention resolution with other UE 1 is performed. The terminal device 1 regards the resolution as 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 the terminal device 1 in message 3 cannot be confirmed within the timer period, the contention resolution is considered to have been unsuccessful, and the terminal device 1 transmits the random access preamble again and continues the random access procedure. However, if the contention resolution is unsuccessful after repeating the transmission of the random access preamble a predetermined number of times, it is determined 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 the reset of the MAC entity, the terminal device 1 stops the random access procedure.

[0153] 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, a two-step random access may be used in which the four messages are shortened and the terminal device 1 and the base station device 3 are synchronized by transmitting and receiving two messages, message A and message B.

[0154] A method for determining PDSCH time domain resource allocation will now be described.

[0155] The base station device 3 may schedule the terminal device 1 to receive the PDSCH by using DCI. The terminal device 1 may receive the PDSCH by detecting DCI addressed to the terminal device 1. When identifying the PDSCH time domain resource allocation, the terminal device 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 device 1 may select one PDSCH time domain resource allocation configuration in the determined resource allocation table based on a value indicated in a 'Time domain resource assignment' (TDRA) field included in the DCI that schedules the PDSCH. In other words, the base station device 3 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 and the time domain resource value included in the received DCI are The PDSCH time domain resource is identified using a PDSCH time domain resource allocation configuration indicating the correspondence between the PDSCH time domain resources and the PDSCH time domain resource allocation configuration.

[0156] FIG. 10 illustrates a resource allocation method for PDSCH time domain resource allocation according to an embodiment of the present invention. FIG. 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 the PDSCH time domain resource allocation may be determined. The base station device 3 may determine a 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 a PDSCH time domain resource allocation setting. The tables are classified into (I) predefined resource allocation tables and (II) resource allocation tables set from an RRC signal of a higher layer. The predefined resource allocation tables are called default tables, and are defined as, for example, default PDSCH time domain resource allocation A, default PDSCH time domain resource allocation B, and default PDSCH time domain resource allocation C. Also, a default PDSCH time domain resource allocation D different from the default PDSCH time domain resource allocation A may be defined. Hereinafter, the default PDSCH time domain resource allocation A is called default table A, the default PDSCH time domain resource allocation B is called default table B, the default PDSCH time domain resource allocation C is called default table C, and the default PDSCH time domain resource allocation D is called default table D, respectively. However, in the default table, different default tables may be defined depending on whether the CP (Cyclic prefix) added to the PDSCH is a normal CP (NCP) or an extended CP (ECP). If not specified, the default table may be a table in which the CP (Cyclic prefix) assigned to the DSCH is a normal CP (NCP).

[0157] 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 is a diagram showing an example of a default table C. In the example of FIG. 11, the number of rows in the default table A is 16, and each row indicates a setting of a PDSCH time domain resource allocation. 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 a slot, and a number of consecutive allocated symbols L. Define.

[0158] The resource allocation table set by the higher layer RRC signal is given by the higher layer signal pdsch-TimeDomainAllocationList. pdsch-TimeDomainAllocationList includes one or more information elements PDSCH-TimeDomainResourceAllocation. PDSCH-TimeDomainResourceAllocation indicates the setting of PDSCH time domain resource allocation. PDSCH-TimeDomainResourceAllocation may be used to set 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 includes a maximum of 16 entries, and any one of the entries 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. In each entry of the pdsch-TimeDomainAllocationList, K0, mappingType, and / or startSymbolAndLength may be indicated. 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 (e.g., 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 be referred to as a start position and length indicator (SLIV). When the SLIV is applied, unlike the case where 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.

[0159] FIG. 14 is a diagram showing an example of calculating the SLIV.

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

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

[0162] As mentioned above, in the subcarrier spacing setting μ, the slots are set from 0 to Within a subframe or frame, slots are numbered from 0 to N^{subframe,μ}_{slot}-1 in ascending order, and within a frame, slots are numbered from 0 to N^{frame,μ}_{slot}-1 in ascending order. K0 is the number of slots based on the subcarrier spacing of the PDSCH. K0 can take values ​​from 0 to 32. Within a subframe or frame, slots 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.

[0163] When the terminal device 1 detects DCI that schedules a PDSCH, the slot allocated to the 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 PDSCHs. It is a slot. PDSCH is the subcarrier spacing setting for PDSCH. PDCCH is the subcarrier spacing setting for the PDCCH.

[0164] 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 terminal device 1 (UE)-specific RRC parameters pdsch-Config. pdsch-ConfigCommon in downlinkConfigCommon or in downlinkConfigCommonRedCap is used to configure cell-specific parameters for the PDSCH for a certain downlink BWP. pdsch-Config is used to configure terminal device 1 (UE)-specific parameters for the PDSCH for a certain downlink BWP.

[0165] The terminal device 1 may apply different resource allocation tables to the PDSCH time domain resource allocation based on the type (value) of the RNTI for scrambling the CRC added to the 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 the SS / PBCH block and CORESET, the setting information included in SIB1, the setting information included in other SIBs, and / or the setting information included in the RRC parameters. The base station device 3 may apply different resource allocation tables to the PDSCH time domain resource allocation based on the type (value) of the RNTI for scrambling the CRC added to the 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 the SS / PBCH block and CORESET, the setting information included in SIB1, the setting information included in other SIBs, and / or the setting information included in the RRC parameters.

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

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

[0168] The terminal device 1 writes pdsch-TimeDomainAllocationList1 (the first parameter) to pdsch-ConfigCommon. Based on whether pdsch-ConfigCommonRedCap includes pdsch-TimeDomainAllocationList2 (second parameter list), pdsch-ConfigCommonRedCap includes pdsch-TimeDomainAllocationList2 (second parameter list), and / or pdsch-Config includes pdsch-TimeDomainAllocationList3 (third parameter list), it may be determined whether pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, pdsch-TimeDomainAllocationList3, and / or a default table (e.g., default table A) is used as the resource allocation table to be applied to the PDSCH time domain resource allocation. 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 a 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 a parameter list to be used for the resource allocation table.

[0169] In this embodiment, the pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) that may be included in pdsch-ConfigCommonRedCap has the same information element configuration as the pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) that may be included in pdsch-ConfigCommon, but may have a different information element configuration. pdsch-TimeDomainAllocationList2 includes a maximum of 16 entries, similar to pdsch-TimeDomainAllocationList1, and any one of the entries may be used depending on the 4-bit field (TDRA field) included in DCI. In each entry included in pdsch-TimeDomainAllocationList2, K0, mappingType, startSymbolAndLength, and / or other parameters may be indicated. The values ​​available for K0, mappingType, and / or startSymbolAndLength in each entry of pdsch-TimeDomainAllocationList2 may be different from the values ​​available for pdsch-TimeDomainAllocationList1. For example, the K0 value available in pdsch-TimeDomainAllocationList1 may be 0 to 32, and the K0 value available in pdsch-TimeDomainAllocationList2 may be 0 to 4. For example, the mappingType 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.

[0170] The terminal device 1 determines whether or not one or more predetermined conditions are met, and A parameter list or default table to apply to the inter-area resource allocation setting. The TimeDomainAllocationList may determine / specify / configure / set the 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 the determination, it may be determined whether to apply pdsch-TimeDomainAllocationList1, pdsch-TimeDomainAllocationList2, or default table A to the PDSCH time domain resource allocation configuration.

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

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

[0173] Whether PDSCH-ConfigCommon includes pdsch-TimeDomainAllocationList1, separate 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, a 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.

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

[0175] 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, the CSS may indicate a search space ID of the CSS 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.

[0176] However, if a CORESET with a CSS is not 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 refers to a CORESET set in the pdcch-ConfigCommonRedCap may be set. For example, in the CSS, for the terminal device 1 that receives DCI accompanied by a CRC scrambled by 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 by a parameter SearchSpace in a parameter commonSearchSpaceList included in the pdcch-ConfigCommonRedCap.

[0177] However, if a CORESET with a CSS is not 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 refers to a CORESET located in the band of the separate initial downlink BWP in the frequency domain may be set. For example, in the CSS, for the terminal device 1 that receives DCI accompanied by CRC scrambled by RA-RNTI, a search space ID of the CSS is indicated in a parameter ra-SearchSpace included in the pdcch-ConfigCommonRedCap, the CSS specified by the search space ID is linked to a CORESET specified by a controlResourceSetId indicated by a parameter SearchSpace in a parameter commonSearchSpaceList included in the pdcch-ConfigCommonRedCap, and the frequency position of the specified CORESET may be within the band of the separate initial downlink BWP.

[0178] However, if a CORESET with a CSS is not 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 refers to a CORESET located outside the band of the separate initial downlink BWP in the frequency domain may be set. For example, in the CSS, for the terminal device 1 that receives DCI accompanied by CRC scrambled by RA-RNTI, a search space ID of the CSS is indicated in a parameter ra-SearchSpace included in the pdcch-ConfigCommonRedCap, the CSS specified by the search space ID is linked to a CORESET specified by a controlResourceSetId indicated by a parameter SearchSpace in a parameter commonSearchSpaceList included in the pdcch-ConfigCommonRedCap, and the frequency position of the specified CORESET may be outside the band of the separate initial downlink BWP.

[0179] However, if a CORESET with a CSS is not 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 the same as that of the corresponding CSS. It may be outside the band of the Pareto initial downlink BWP. For example, the predetermined CORESET may be a CORESET specified by a parameter controlResourceSetId in a parameter SearchSpace that sets a corresponding CSS in pdcch-ConfigCommonRedCap.

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

[0181] (A1) (regardless of whether pdsch-TimeDomainAllocationList1 is provided in the SIB or not, ) If pdsch-TimeDomainAllocationList2 is provided in the SIB (for example, When the parameter (e.g. PDSCH-ConfigCommonRedCap) includes pdsch-TimeDomainAllocationList2)

[0182] (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 pdsch-TimeDomainAllocationList2 includes the initial downlink BWP (separate initial downlink BWP) set by the separateInitialDownlinkBWP including the pdsch-TimeDomainAllocationList2, a CORESET linked to a CSS for monitoring the corresponding PDCCH is set.

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

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

[0185] (B2) When separateInitialDownlinkBWP is not provided in the SIB and pdsch-TimeDomainAllocationList1 is provided in the SIB (for example, when a parameter provided in the SIB (for example, PDSCH-ConfigCommon) includes pdsch-TimeDomainAllocationList)

[0186] (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 position of the initial downlink BWP (separate initial downlink BWP) set in separateInitialDownlinkBWP includes the frequency position of CORESET#0 set in the MIB

[0187] (B4) In the initial downlink BWP (separate initial downlink BWP) configured by separateInitialDownlinkBWP, a CORESET associated with a CSS for monitoring the corresponding PDCCH is not configured, and pdsch-TimeDomainAllocationList1 is provided in the SIB (for example, when a parameter provided in the SIB (for example, PDSCH-ConfigCommon) includes pdsch-TimeDomainAllocationList).

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

[0189] An example of a condition in 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 (C1), any one or more of the following conditions (C1) to (C8) may be used.

[0190] (C1) pdsch-TimeDomainAllocationList2 is not provided in the SIB (parameters provided in the SIB (e.g., PDSCH-ConfigCommonRedCap) do not include pdsch-TimeDomainAllocationList2) 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).

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

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

[0193] (C5) When pdsch-TimeDomainAllocationList1 is provided in the SIB (for example, when a parameter provided in the SIB (for example, PDSCH-ConfigCommon) includes pdsch-TimeDomainAllocationList), and a parameter provided in the SIB (for example, PDSCH-ConfigCommonRedCap) does not include pdsch-TimeDomainAllocationList2, and the frequency position of the initial downlink BWP (separate initial downlink BWP) set in separateInitialDownlinkBWP does not include the frequency position 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

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

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

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

[0197] However, the conditions for applying pdsch-TimeDomainAllocationList1 to the PDSCH time domain resource allocation settings shown above, the conditions for applying pdsch-TimeDomainAllocationList1, and the default The application of the example of conditions for applying the schedule table depends on whether the corresponding PDSCH is scheduled. The search space of the PDCCH transmitting the DCI may differ depending on the type of RNTI (e.g., SI-RNTI, RA-RNTI, MSGB-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI and / or CS-RNTI) used to scramble the CRC assigned to the DCI to be transmitted, 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 or 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.

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

[0199] 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 a 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 PDSCH may determine a resource allocation table to be applied to the scheduled PDSCH. 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

[0200] In element (A), the type of RNTI that scrambles 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 the RA-RNTI. RNTI and P-RNTI are shown, but other types of RNTI may be defined in a similar manner.

[0201] 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 is a type 0 common search space, a type 0A common search space, a type 1 common search space, , and type 2 common search space. Although FIG. 10 shows the cases of type 1 common search space and type 2 common search space, other search spaces may be defined in the same manner. However, element (B) may be associated with element (A). When element (A) is a predetermined RNTI type, element (B) may be a type of search space corresponding to the type of the RNTI.

[0202] 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 scrambled by the RA-RNTI attached, it may determine a resource allocation table to be applied to the PDSCH scheduled by that DCI. If the pdsch-ConfigCommon received in the SIB1 / other SIBs and / or RRC message received by the terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (No) and the pdsch-ConfigCommonRedCap received in the SIB1 / other SIBs and / or RRC message received by the terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (No) (or if the 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 as default table A (Default A). In other words, the terminal device 1 may apply the default table A indicating the setting of the PDSCH time domain resource allocation to the determination of the PDSCH time domain resource allocation. When the pdsch-ConfigCommon received in the SIB1 / other SIBs and / or RRC message received by the terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (Yes / No) and the pdsch-ConfigCommonRedCap received in the SIB1 / other SIBs and / or RRC message received by the terminal device 1 includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (Yes), the terminal device 1 may determine the resource allocation table to be applied to the PDSCH time domain resource allocation as the pdsch-TimeDomainAllocationList2. In other words, the terminal device 1 may apply the pdsch-TimeDomainAllocationList included in the pdsch-ConfigCommonRedCap to the determination of 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 the 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 the PDSCH time domain resource allocation.

[0203] 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 PDSCH may determine a resource allocation table to be applied to the PDSCH scheduled by the PDSCH. 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 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 the SIB1 / other SIB and / or RRC message received by the terminal device 1 does not include pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) (Yes / No), and the pdsch-ConfigCommonRedCap received in the SIB1 / other SIB and / or RRC message received by the terminal device 1 includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) (Yes), the terminal device 1 The resource allocation table to be applied to the time domain resource allocation may be determined to be the pdsch-TimeDomainAllocationList2. That is, the terminal device 1 may apply the pdsch-TimeDomainAllocationList included in the pdsch-ConfigCommonRedCap to the determination of the PDSCH time domain resource allocation. If the pdsch-ConfigCommon received in the SIB1 / other SIBs and / or RRC message received by the terminal device 1 includes the pdsch-TimeDomainAllocationList(pdsch-TimeDomainAllocationList1) (Yes) and the pdsch-ConfigCommonRedCap received in the SIB1 / other SIBs and / or RRC message received by the terminal device 1 does not include the pdsch-TimeDomainAllocationList(pdsch-TimeDomainAllocationList2) (No) (or if the 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 the pdsch-TimeDomainAllocationList1. That is, the terminal device 1 may apply pdsch-TimeDomainAllocationList included in pdsch-ConfigCommon to determine PDSCH time domain resource allocation.

[0204] As an example C in Figure 10, the terminal device 1 may detect DCI in a type 0 common search space, and if the detected DCI has a CRC attached that is scrambled by the SI-RNTI, it may determine a resource allocation table to be applied to the PDSCH scheduled by that DCI. When a CRC scrambled by the SI-RNTI is attached to the detected DCI, 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 and pdsch-TimeDomainAllocationList2 are provided in the SIB. When a CRC scrambled by the SI-RNTI is attached to the detected DCI, 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.

[0205] 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, in the table shown in FIG. 10, the fifth column states that the PDSCH-ConfigCommonRedCap includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList2) as a condition, but 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, the parameter list and / or default table to be applied to the PDSCH time domain resource allocation configuration may be selected based on whether the PDSCH-ConfigCommon includes pdsch-TimeDomainAllocationList (pdsch-TimeDomainAllocationList1) or the default table. 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.

[0206] In this way, the RNTI that scrambles the CRC assigned to the DCI that schedules the PDSCH is Therefore, the parameter list and / or data set that apply to the PDSCH time domain resource allocation configuration are Since the method of determining the fault table is different, the appropriate For example, pdsch-TimeDomainAllocationList2 can be set as A time resource appropriate for the PDSCH transmitted in the separate initial downlink BWP is defined, and if the PDSCH corresponding to a specific RNTI is not transmitted in the separate initial downlink BWP, a determination method that excludes the pdsch-TimeDomainAllocationList2 from the candidates may be used, and if the PDSCH corresponding to a specific RNTI can be transmitted in the separate initial downlink BWP, a determination method that includes the pdsch-TimeDomainAllocationList2 as a candidate may be used. For example, any of the default table A, the default table B, and the default table C may be applied to the PDSCH time domain resource allocation setting of the PDSCH corresponding to the SI-RNTI, and any of the pdsch-TimeDomainAllocationList1, the pdsch-TimeDomainAllocationList2, and the default table A may be applied to the PDSCH time domain resource allocation setting of the PDSCH corresponding to the RA-RNTI based on the above-mentioned conditions.

[0207] FIG. 15 shows the DCI, SIB, and random access response in the terminal device 1 of the present embodiment. FIG. 15 is a flow chart 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 an SI-RNTI in a first BWP of a first cell. The terminal device 1 determines the first time domain resource using a first value indicated by the second field included in the second DCI and a first PDSCH time domain resource allocation configuration indicating a correspondence relationship between the first value and a time domain resource. In step S1003, the terminal device 1 receives the SIB via the first PDSCH scheduled in the first time resource. When the SIB includes configuration information of the second BWP, the terminal device 1 that has received the SIB can identify the second BWP. In step S1004, the terminal device 1 receives a second DCI with a CRC scrambled by 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 in 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 may determine whether the second parameter list is provided in the SIB, and if the second parameter list is provided in the SIB, apply the second parameter list to the second PDSCH time domain resource allocation configuration, and if the second parameter list is not provided in the SIB, 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 also applicable to the processing related to the 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.

[0208] FIG. 16 is a flow diagram showing an example of a process 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 includes configuration information (initialDownlinkBWP) of a first BWP (which may be an initial downlink BWP). The SIB may include the first BWP (may be PDSCH-ConfigCommon), the PDSCH configuration information of the first BWP (may be PDSCH-ConfigCommon), the configuration information of the second BWP (may be separate initial downlink BWP) (may be separateInitialDownlinkBWP), and / or the PDSCH configuration information of the second BWP (may be PDSCH-ConfigCommonRedCap). In step S2002, the terminal device 1 receives DCI with a CRC scrambled with RA-RNTI on the PDCCH. In step S2003, the terminal device 1 determines whether a second parameter list (may be pdsch-TimeDomainAllocationList2) is provided in the SIB received in step S2001. If step S2003 is yes (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. If step S2005 is positive (S2005-Yes), step S2 In step S2006, the terminal device 1 applies the first parameter list to the PDSCH time domain resource allocation setting, and proceeds to step S2008. If step S2005 is negative (S2005-No), in step S2007, the terminal device 1 applies the default table to the PDSCH time domain resource allocation setting, and proceeds to step S2008. In step S2008, 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 S2009, the terminal device 1 receives the PDSCH with the time resource determined in step S2008. The flow of the flow diagram shown in FIG. 16 is also applicable to the process of determining / specifying / setting / setting the resource allocation table to be applied to the PDSCH time domain resource allocation in the base station device 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.

[0209] FIG. 17 is a flow diagram showing another example of a process related to the determination / identification / setting / setting of 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 with CRC scrambled by RA-RNTI in a common search space (CSS) on a PDCCH. In step S3003, the terminal device 1 determines whether or not 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 the 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 the 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 setting 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 setting according to a predetermined condition (for example, whether the first parameter list is provided in the SIB). The flow of the flow diagram shown in FIG. 17 is also applicable to the process of determining / specifying / setting / setting the resource allocation table to be applied to the 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 are respectively the transmission of the SIB, the transmission of the DCI, and the transmission of the PDSCH.

[0210] The terminal device 1 may select one PDSCH time domain resource allocation configuration in the determined resource allocation table based on a value indicated in a 'Time domain resource assignment' field (TDRA field) included in the DCI that schedules the PDSCH. For example, when the resource allocation table applied to the PDSCH time domain resource allocation is the default table A, the value m indicated in the TDRA field may indicate row index m+1 of the default table A. At this time, the PDSCH time domain resource allocation is the time domain resource allocation configuration indicated by row index m+1. The terminal device 1 receives the PDSCH assuming the time domain resource allocation configuration indicated by row index m+1. For example, when 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 the default table A.

[0211] Also, when the resource allocation table applied to the 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.

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

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

[0214] FIG. 18 is a schematic block diagram showing the configuration of a terminal device 1 according to the present 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 includes 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 processing unit 14, a measurement unit 14, a selection unit 14, a decision unit 14, or a control unit 14.

[0215] 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 transmission / reception unit 10. The upper layer processing unit 14 performs part or all of processing of a Medium Access Control (MAC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Radio Resource Control (RRC) layer. The upper layer processing unit 14 may have a function of acquiring bit information of an MIB (which may be a REDCAP MIB), an SIB1 (which may be a REDCAP SIB1), and other SIBs (which may be REDCAP SIBs). The upper layer processing unit 14 may have a function of determining / specifying a setting (e.g., a frequency position or a bandwidth) of an initial downlink BWP based on information of a system information block (SIB1 / SIB) or RRC signaling. The upper layer processing unit 14 may have a function of determining / specifying the setting (e.g., frequency location and bandwidth) of the initial uplink BWP based on the system information block (SIB1 / SIB) or information of RRC signaling. The upper layer processing unit 14 may have a function of determining / specifying the setting (e.g., frequency location and bandwidth) of the separate initial uplink BWP based on the system information block (SIB1 / SIB) or information of RRC signaling. The upper layer processing unit 14 may have a function of determining the time resource for receiving the PDSCH using a value indicated by a field (TDRA field) included in the DCI and the PDSCH time domain resource allocation setting. The upper layer processing unit 14 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 setting.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 set 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.

[0216] The upper layer processing unit 14 includes a media access control layer processing unit 15 that performs processing for a MAC layer (media access control The media access control layer processing unit 15 controls the transmission of the scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 16.

[0217] 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 (downlink control information) for the base station device 3. 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 a higher layer signal 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.

[0218] 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 a signal received from the base station device 3, and transmits the decoded information to a higher level. The radio transmission / reception unit 10 generates a transmission signal by modulating and encoding data, and transmits it to the base station device 3, etc. The radio transmission / reception unit 10 outputs higher layer signals (RRC messages), DCI, etc. received from the base station device 3 to the higher layer processing unit 14. Based on instructions from the higher layer processing unit 14, the radio transmission / reception unit 10 also outputs uplink signals (PUCCH and / or The radio transceiver 10 generates and transmits a synchronization signal block, an additional synchronization Signal block, PSS, SSS, PBCH, DMRS for PBCH, Random Access Response, PDCCH and The radio transceiver unit 10 may have a function of receiving a PDSCH and / or a PRACH (which may be a random access preamble), a PUCCH and / or a PUSCH. The radio transceiver unit 10 may have a function of monitoring a PDCCH. may have a function of receiving DCI on the PDCCH. The radio transceiver unit 10 may have a function of outputting the DCI received on the PDCCH to the higher layer processing unit 14. The radio transceiver unit 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 of receiving a DCI accompanied by a CRC scrambled with a predetermined RNTI (e.g., SI-RNTI, RA-RNTI, P-RNTI, etc.) in a certain BWP of a certain cell. The radio transceiver unit 10 may have a function of receiving a SIB (which may be SIB1) or a random access response in a certain BWP of a certain cell via a PDSCH scheduled in a predetermined time resource.

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

[0220] 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 is removed, and the signal from which the CP has been removed is subjected to a Fast Fourier Transform (FFT) to extract the signal in the frequency domain.

[0221] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

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

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

[0224] The RF unit 12 may have a function of tuning / 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 own device (which may be called the allocated bandwidth). However, the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when down-converting the received signal to a baseband signal.

[0225] The RF unit 12 may have a function of adjusting / re-adjusting 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 called 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.

[0226] FIG. 19 is a schematic block diagram showing the configuration of a base station device 3 of this embodiment. The base station device 3 includes 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 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.

[0227] The upper layer processing unit 34 performs part or all of the processing of a Medium Access Control (MAC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a 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 and the like to the radio transmitting / receiving 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 the 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 the 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 by using a time resource for transmitting the PDSCH and a 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 or not a predetermined parameter list is provided in an 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 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.

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

[0229] A radio resource control layer processing unit 36 ​​included in the higher 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 DCI, downlink data (transport block (TB), random access response (RAR)) arranged in the PDSCH, system information, RRC message, MAC CE (Control Element), etc., or acquires them from an upper node, and outputs them to the radio transmitting / receiving unit 30. The radio resource control layer processing unit 36 ​​also manages various setting information / parameters of 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 of 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 transmit / report information for identifying the setting of one or more reference signals in a certain cell.

[0230] 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 RRC message, MAC CE, and / or PDCCH, 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 causing the terminal device to perform processing based on its reception.

[0231] The radio transmission / reception unit 30 transmits higher layer signals (RRC messages), DCI, etc. to the terminal device 1. In addition, the wireless transmission / reception unit 30 receives the signal from the terminal device 1 based on an instruction from the upper layer processing unit 34. The radio transmission / reception unit 30 may have a function of transmitting a PDCCH and / or a PDSCH. The radio transmission / reception unit 30 may have a function of receiving one or more PUCCHs and / or PUSCHs. The radio transmission / reception unit 30 may have a function of transmitting DCI on a PDCCH. The radio transmission / reception unit 30 may have a function of transmitting DCI output by the upper layer processing unit 34 on a PDCCH. The radio transmission / reception unit 30 may have a function of transmitting SSB, PSS, SSS, PBCH, and / or a DMRS for the PBCH. The radio transmission / reception unit 30 may have a function of transmitting 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 the system information. The radio transceiver unit 30 may have a function of transmitting a signaling information 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 determined by the user. The radio transceiver unit 30 may have a function of transmitting an SIB (which may be SIB1) or a random access response in a certain BWP of a certain cell via a PDSCH scheduled in a predetermined time resource. Some of the functions of the line transmission / reception unit 30 are similar to those of the wireless transmission / reception unit 10, and therefore the description thereof will be omitted. Some or all of them may be included in each transmission / reception point 4.

[0232] 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 configuration elements Although the transmission path of data (control information) between the base stations is omitted, the base station device 3 It is clear that the upper layer processor 34 includes a plurality of blocks having other functions necessary for its operation as components. For example, the upper layer processor 34 includes a radio resource management layer processor and an application layer processor.

[0233] In addition, the "parts" in the figure are elements that realize the functions and procedures of the terminal apparatus 1 and the base station apparatus 3, and can also be expressed by terms such as section, circuit, component equipment, device, and unit.

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

[0235] 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 is temporarily stored in a volatile memory such as a Random Access Memory (RAM) or a flash memory. The information is stored in the non-volatile memory of a hard disk drive (HDD), or in other storage devices.

[0236] 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 implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes 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 holds a program for a short period of time, or any other computer-readable recording medium.

[0237] Also, each functional block or feature of the apparatus used in the above-described embodiments may be implemented or performed in an electrical circuit, for example, an integrated circuit or a plurality of integrated circuits. An 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, a microcomputer ... 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 electric circuitry described above may be composed of digital circuits or analog circuits. In addition, when an integrated circuit technology that replaces current integrated circuits emerges due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit based on that technology.

[0238] In the embodiment of the present invention, an example in which the present invention is applied to a communication system configured with a base station device and a terminal device has been described. 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). The present invention is also applicable to systems in which

[0239] The present invention is not limited to the above-described embodiment. Although examples have been described, the present invention is not limited to these and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0240] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways 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 replaced with elements that have the same effect are also included. [Explanation of symbols]

[0241] 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 Media 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 Media 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, Receive a first downlink control information (DCI) with a CRC scrambled with an SI-RNTI in a first BWP of a first cell, and schedule a system information block (SIB) to a first time resource. and receiving the first physical downlink shared channel (PDSCH) via the first physical downlink shared channel (PDSCH) that is assigned to the first PDSCH. Receive a second DCI with a CRC scrambled with the RA-RNTI in a second BWP of the cell, and receive a random access response via a second PDSCH scheduled in a second time resource. A receiving unit for receiving the signal; A first value indicated by a first field included in the first DCI, and a combination of the first value 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 ... determining a resource, and determining a second value indicated by a second field included in the second DCI and the second and a control unit for determining the second time resource using a second PDSCH time domain resource allocation configuration indicating a correspondence relationship between the value of The control unit assigns a first default table to the first PDSCH time domain resource allocation configuration. , apply the second or third default table, determining whether a second parameter list is provided in the SIB; If the second parameter list is provided in the SIB, applying the second parameter list to the second PDSCH time domain resource allocation configuration; A terminal device that applies the first parameter list or the first default table to the second PDSCH time domain resource allocation setting if the second parameter list is not provided in the SIB.

2. The control unit is If the second parameter list is not provided in the SIB, If the first parameter list is provided in the SIB, 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 SIB, the first default table is applied to the second PDSCH time domain resource allocation setting.

3. When the second parameter list is not provided in the SIB, the control unit: The second setting information of the second BWP is not provided in the SIB, and the first parameter list If the second PDSCH time domain resource allocation configuration is provided in the SIB, Apply the first parameter list, The terminal device according to claim 1, wherein, when the second setting information is provided in the SIB, the first default table is applied to the second PDSCH time domain resource allocation setting.

4. The receiving unit receives information identifying a frequency location of a control resource set (CORESET) having an index of 0 in a master information block (MIB); The control unit detects that the second parameter list is not provided in the SIB and is When receiving information specifying a frequency location of the second BWP, If the frequency location of the second BWP includes the frequency location of the CORESET and the first parameter list is provided in the SIB, applying the first parameter list to the second PDSCH time domain resource allocation configuration; 2. The method according to claim 1, wherein the first default table is applied to the second PDSCH time domain resource allocation configuration when the frequency location of the second BWP does not include the frequency location of the CORESET. Terminal device.

5. A base station device, In a first BWP of a first cell, a first DCI with a CRC scrambled with an SI-RNTI is transmitted, and a system information block (SIB) is scheduled to a first time resource. and transmitting the first physical downlink shared channel (PDSCH) via the first physical downlink shared channel (PDSCH) that is assigned to the first PDSCH. In a second BWP of the cell, transmit a second DCI with a CRC scrambled with the RA-RNTI and transmit a random access response via a second PDSCH scheduled in a second time resource. A transmitting unit for transmitting the signal; The first field included in the first DCI is indicated by 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. determining a first value, determining a second time resource, and a correspondence between the second value and the time resource; and a second PDSCH time domain resource allocation configuration shown in FIG. and a control unit that determines a second value indicated by the field; The control unit assigns a first default table to the first PDSCH time domain resource allocation configuration. , apply the second or third default table, If the second parameter list is provided in the SIB, applying the second parameter list to the second PDSCH time domain resource allocation configuration; A base station device that applies the first parameter list or the first default table to the second PDSCH time domain resource allocation configuration when the second parameter list is not provided in the SIB.

6. The control unit is In the case where the second parameter list is not provided in the SIB, If the first parameter list is provided in the SIB, applying the first parameter list to the second PDSCH time domain resource allocation configuration; 6. The base station apparatus according to claim 5, wherein, when the first parameter list is not provided in the SIB, the first default table is applied to the second PDSCH time domain resource allocation configuration.

7. When the control unit does not provide the second parameter list in the SIB, The SIB does not provide second configuration information for the second BWP, and the first parameter list applying the first parameter list to the second PDSCH time domain resource allocation configuration if the SIB provides a second PDSCH time domain resource allocation configuration; 6. The base station apparatus according to claim 5, wherein, when the second setting information is provided in the SIB, the first default table is applied to the second PDSCH time domain resource allocation setting.

8. The transmitter transmits information identifying a frequency location of a control resource set (CORESET) having an index of 0 in a master information block (MIB); The control unit does not provide the second parameter list in the SIB and In the case where information specifying the frequency location of the second BWP is being transmitted, If the frequency location of the second BWP includes the frequency location of the CORESET and the first parameter list is provided in the SIB, applying the first parameter list to the second PDSCH time domain resource allocation configuration; 6. The method according to claim 5, wherein the first default table is applied to the second PDSCH time domain resource allocation configuration when the frequency location of the second BWP does not include the frequency location of the CORESET. Base station equipment.

9. A communication method for a base station device, comprising: In a first BWP of a first cell, a first DCI with a CRC scrambled with an SI-RNTI is transmitted, and a system information block (SIB) is scheduled to a first time resource. and transmitting the first PDSCH via a first physical downlink shared channel (PDSCH) that is assigned to the first PDSCH. In a second BWP of the cell, transmit a second DCI with a CRC scrambled with the RA-RNTI and transmit a random access response via a second PDSCH scheduled in a second time resource. death, The first field included in the first DCI is indicated by 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. determining a first value, determining the second time resource, and a correspondence between the second value and the time resource; and a second PDSCH time domain resource allocation configuration shown in FIG. determining a second value represented by the field; Applying a first default table, a second default table, or a third default table to the first PDSCH time domain resource allocation configuration; If the second parameter list is provided in the SIB, applying the second parameter list to the second PDSCH time domain resource allocation configuration; A communication method, comprising: applying the first parameter list or the first default table to the second PDSCH time domain resource allocation configuration if the second parameter list is not provided in the SIB.

Images