Terminal device and communication method

Abstract

To allow a terminal device and a base station device to efficiently communicate with each other.SOLUTION: In a terminal device, a first field with a fixed bit size included in a RAR UL grant is used to indicate allocation of PUSCH frequency resources. A processing unit interprets the first field truncated or extended by truncating bits of the first field or inserting bits into the first field as a field indicating the allocation of PUSCH frequency resources. When an initial UL BWP is an active UL BWP, whether to truncate bits of the first field or insert bits into the first field is based on bandwidth of the initial UL BWP. When an additional UL BWP is an active UL BWP, whether to truncate bits of the first field or insert bits into the first field is based on the bandwidth of the initial UL BWP.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

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

[0003] For the fifth generation cellular system, three expected service scenarios are required: eMBB (enhanced Mobile BroadBand) which realizes high-speed, large-capacity transmission; URLLC (Ultra-Reliable and Low Latency Communication) which realizes low-latency, highly reliable communications; and mMTC (massive Machine Type Communication) which connects a large number of machine-type devices such as IoT (Internet of Things). [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 Summary of the Invention [Problem to be solved by the invention]

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

[0006] (1) In order to achieve the above object, the present invention provides the following features: That is, a terminal device performing a contention based random access procedure in one embodiment of the present invention includes a receiving unit that receives a PDSCH including an RAR message, and a control unit that controls resource allocation based on a first field indicating an Msg3 PUSCH frequency resource assignment indicated in a first UL grant included in the RAR message, wherein the control unit truncates X bits from the least significant bit to the bits of the first field when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, and inserts Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the value of the predetermined number of resource blocks, wherein the number of first resource blocks is the number of resource blocks indicating the bandwidth of a UL BWP having the same BWP identifier as a DL BWP in which configuration information of a CORESET indicated in a Type 1 PDCCH common search space set is set, the Type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information.

[0007] (2) According to an aspect of the present invention, a base station device communicating with a terminal device performing a contention based random access procedure includes a control unit that generates a first UL grant including a first field indicating an Msg3 PUSCH frequency resource assignment indicating resource assignment, and a transmission unit that transmits a PDSCH including an RAR message, the first UL grant being included in the RAR message, the control unit truncating X bits from a least significant bit to bits of the first field when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, and inserting Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the value of the predetermined number of resource blocks, the number of first resource blocks being a UL BWP having the same BWP identifier as a DL BWP in which configuration information of CORESET indicated in a Type 1 PDCCH common search space set is set. The type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information.

[0008] (3) Also, a communication method according to one embodiment of the present invention is a communication method of a terminal device, which receives a PDSCH including an RAR message, controls resource allocation based on a first field indicating an Msg3 PUSCH frequency resource assignment indicated in a first UL grant included in the RAR message, truncates X bits from the least significant bit to the bits of the first field when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, and inserts Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the value of the predetermined number of resource blocks, wherein the number of first resource blocks is the number of resource blocks indicating a bandwidth of a UL BWP having the same BWP identifier as a DL BWP in which configuration information of a CORESET indicated in a Type 1 PDCCH common search space set is set, the Type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information.

[0009] (4) Also, a communication method according to one embodiment of the present invention is a communication method of a base station device, which generates a first UL grant including a first field indicating an Msg3 PUSCH frequency resource assignment indicating resource allocation, and transmits a PDSCH including an RAR message, the first UL grant being included in the RAR message, and the control unit truncates X bits from the least significant bit to the bits of the first field when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, and inserts Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the value of the predetermined number of resource blocks, the number of first resource blocks is the number of resource blocks indicating a bandwidth of a UL BWP having the same BWP identifier as a DL BWP in which configuration information of a CORESET indicated in a Type 1 PDCCH common search space set is set, the Type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information.

[0010] (5) Furthermore, an integrated circuit according to one embodiment of the present invention is an integrated circuit implemented in a terminal device, and causes the terminal device 1 to perform a function of receiving a PDSCH including an RAR message and a function of controlling resource allocation based on a first field indicating an Msg3 PUSCH frequency resource assignment indicated in a first UL grant included in the RAR message, and when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, truncates X bits from the least significant bit in the bits of the first field, and when the number of first resource blocks is greater than the value of the predetermined number of resource blocks, inserts Y most significant bits set to a value of '0' after the hopping bit into the bits of the first field, and the number of first resource blocks is the number of resource blocks indicating the bandwidth of a UL BWP having the same BWP identifier as a DL BWP in which configuration information of a CORESET indicated in a Type 1 PDCCH common search space set is set, and the Type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information.

[0011] (6) According to an embodiment of the present invention, an integrated circuit is provided in a base station apparatus, and causes the base station apparatus to perform a function of generating a first UL grant including a first field indicating an Msg3 PUSCH frequency resource assignment indicating resource allocation, and a function of transmitting a PDSCH including an RAR message, the first UL grant being included in the RAR message, truncating X bits from the least significant bit to the bits of the first field when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, and inserting Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the value of the predetermined number of resource blocks, and the number of first resource blocks being a UL grant having the same BWP identifier as a DL BWP in which configuration information of CORESET indicated in a Type 1 PDCCH common search space set is set. The type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information. Effect of the Invention

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

[0013] [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 an SS / PBCH block and SS burst set for an embodiment of the present invention. [Diagram 3] A figure showing an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. [Figure 4] 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. [Diagram 5] A diagram showing an example of a slot or subframe according to an embodiment of the present invention. [Figure 6] FIG. 2 is a diagram illustrating an example of beamforming according to an embodiment of the present invention. [Figure 7] FIG. 1 is a diagram showing an example of a BWP setting according to an embodiment of the present invention. [Figure 8] 1 is a diagram showing an example of a random access procedure of a terminal device 1 according to an embodiment of the present invention. [Figure 9] FIG. 13 is a diagram illustrating an example of fields included in a RAR UL grant according to an embodiment of the present invention. [Figure 10] FIG. 11 is a diagram illustrating an example of interpretation of the 'Msg3 PUSCH frequency resource allocation' field according to the present embodiment. [Figure 11] FIG. 1 is a diagram illustrating an example for explaining uplink resource allocation type 1 for a BWP according to the present embodiment. [Figure 12] FIG. 1 is a diagram showing an example of calculating an RIV according to an embodiment of the present invention. [Figure 13] FIG. 13 is a diagram showing an example of allocation of SSB indices to PRACH opportunities according to the present embodiment. [Figure 14] FIG. 2 is a flow diagram illustrating an example of a random access procedure of a MAC entity according to an embodiment of the present invention. [Figure 15] 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an embodiment of the present invention. [Figure 16] 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

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

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

[0016] The terminal device 1 is also referred to as a user terminal, a mobile station device, a communication terminal, a mobile device, a terminal, a UE (User Equipment), or an MS (Mobile Station). 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 reception points 4. At least some of the functions / processing of the base station device 3 described below may be functions / processing of each transmission 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 coverage areas (communication areas) controlled by one or more transmission / reception points 4. Furthermore, one cell may be divided into multiple partial areas (beamed areas), and the base station device 3 may serve the terminal device 1 in each partial area. Here, the partial area may be identified based on the index of the beam used in beamforming or the index of precoding.

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

[0018] In FIG. 1, in wireless communication between the terminal device 1 and the base station device 3, orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single-carrier frequency division multiplexing (SC-FDM), discrete Fourier transform spread OFDM (DFT-S-OFDM), or multi-carrier code division multiplexing (MC-CDM) may be used.

[0019] In addition, in FIG. 1, the wireless communication between the terminal device 1 and the base station device 3 may use Universal Filtered Multi-Carrier (UFMC), Filtered OFDM (F-OFDM), Windowed OFDM (Windowed OFDM), or Filter-Bank Multi-Carrier (FBMC).

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

[0021] 1, the above-mentioned transmission method may be used in which a CP is not used or zero padding is used instead of a CP in wireless communication between the terminal device 1 and the base station device 3. Also, a CP or zero padding may be added to both the front and rear.

[0022] One aspect of the present embodiment may be operated in carrier aggregation or dual connectivity with radio access technologies (RATs) such as LTE and LTE-A / LTE-A Pro. In this case, it may be used in some or all of the cells or cell groups, carriers or carrier groups (e.g., a primary cell (PCell), a secondary cell (SCell), a primary secondary cell (PSCell), a master cell group (MCG), a secondary cell group (SCG), etc.). It may also be used as a standalone cell that operates alone. In dual connectivity operation, the SpCell (Special Cell) is referred to as the PCell of the MCG or the PSCell of the SCG depending on whether the MAC (Medium Access Control) entity is associated with the MCG or the SCG, respectively. If not in dual connectivity operation, the SpCell (Special Cell) is referred to as the PCell. The SpCell (Special Cell) supports PUCCH transmission and contention-based random access.

[0023] 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, two types of subsets of serving cells, a master cell group and a secondary cell group, may be configured for the terminal device 1. The master cell group may be configured with one primary cell and zero or more secondary cells. The secondary cell group may be configured with one primary secondary cell and zero or more secondary cells.

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

[0025] In the downlink, a carrier corresponding to a serving cell is called a downlink component carrier (or downlink carrier). In the uplink, a carrier corresponding to a serving cell is called an uplink component carrier (or uplink carrier). In the sidelink, a carrier corresponding to a serving cell is called a sidelink component carrier (or sidelink carrier). Downlink component carriers, uplink component carriers, and / or sidelink component carriers are collectively called component carriers (or carriers).

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

[0027] In FIG. 1, the following physical channels are used in wireless communication between the terminal device 1 and the base station device 3.

[0028] ·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)

[0029] The PBCH is used to broadcast important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1.

[0030] Also, the PBCH may be used to broadcast a time index within a period of a block of a synchronization signal (also referred to as an SS / PBCH block). Here, the time index is information indicating an index of a synchronization signal and a PBCH within a cell. For example, when an SS / PBCH block is transmitted using the assumption of three transmission beams (transmission filter setting, quasi co-location (QCL: Quasi Co-Location) for reception spatial parameters), a time order within a predetermined period or a set period may be indicated. Also, the terminal device may recognize a difference in the time index as a difference in the transmission beam.

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

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

[0033] DCI format 0_0 may include information indicating scheduling information (frequency domain resource allocation and time domain resource allocation) of the PUSCH.

[0034] DCI format 0_1 ​​may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band width part (BWP), a Channel State Information (CSI) request, a Sounding Reference Signal (SRS) request, and information regarding antenna ports.

[0035] DCI format 1_0 may include information indicating scheduling information (frequency domain resource allocation and time domain resource allocation) of the PDSCH.

[0036] DCI format 1_1 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band portion (BWP), a transmission configuration indication (TCI), and information regarding antenna ports.

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

[0038] DCI format 2_1 is used to notify the terminal device 1 of physical resource blocks and OFDM symbols for which no transmission may be assumed. Note that this information may be called a preemption instruction (discontinuous transmission instruction).

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

[0040] DCI format 2_3 is used to transmit a group of TPC commands for sounding reference signal (SRS) transmission by one or more terminal devices 1. An SRS request may be transmitted together with the TPC command. An SRS request and a TPC command may be defined in DCI format 2_3 for an uplink without PUSCH and PUCCH, or for an uplink in which the transmission power control of SRS is not linked to the transmission power control of PUSCH.

[0041] DCI for the downlink is also referred to as a downlink grant or a downlink assignment. Here, DCI for the uplink is also referred to as an uplink grant or an uplink assignment.

[0042] A CRC (Cyclic Redundancy Check) parity bit added to a DCI format transmitted in one PDCCH is scrambled with a C-RNTI (Cell-Radio Network Temporary Identifier), a CS-RNTI (Configured Scheduling-Radio Network Temporary Identifier), a RA-RNTI (Random Access-Radio Network Temporary Identity), or a Temporary C-RNTI. The C-RNTI and CS-RNTI are identifiers for identifying a terminal device in a cell. The Temporary C-RNTI is an identifier for identifying a terminal device 1 that has transmitted a random access preamble during a contention based random access procedure.

[0043] The C-RNTI (identifier (identification information) of the terminal device) 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 Temporary C-RNTI (TC-RNTI) is used to control the PDSCH transmission or PUSCH transmission in one or more slots. The Temporary C-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 (random access response identification information) is determined according to the frequency and time location information of the physical random access channel that transmitted the random access preamble.

[0044] The PUCCH is used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3). 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). The HARQ-ACK may indicate a HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH).

[0045] 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) and Random Access Response (RAR) in the downlink.

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

[0047] 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 RRC signaling (also referred to as RRC message: Radio Resource Control message, RRC information: Radio Resource Control information) in a Radio Resource Control (RRC) layer. The base station device 3 and the terminal device 1 may also transmit and receive MAC control elements in a Medium Access Control (MAC) layer. Here, the RRC signaling and / or the MAC control element are also referred to as a higher layer signal (higher layer signaling). The higher layer here means a higher layer as viewed from the physical layer, and may include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may include one or more of a RRC layer, an RLC layer, a PDCP layer, a NAS layer, etc.

[0048] The PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. Here, in the PDSCH, the RRC signaling transmitted from the base station device 3 may be common signaling for a plurality of terminal devices 1 in a cell. Furthermore, the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device 1. That is, terminal device-specific (UE-specific) information may be transmitted using dedicated signaling for a certain terminal device 1. Furthermore, the PUSCH may be used to transmit UE capabilities in the uplink.

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

[0050] The synchronization signal may include a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). The PSS and SSS may be used to detect the cell ID.

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

[0052] The reference signal is used by the terminal device 1 to perform propagation path compensation of the physical channel. Here, the reference signal may also be used by the terminal device 1 to calculate the downlink CSI. In addition, the reference signal may be used for fine synchronization to the extent that numerology such as radio parameters and subcarrier intervals and FFT window synchronization can be performed.

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

[0054] The 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. The CSI-RS is used for measuring channel state information (CSI) and beam management, and applies a periodic, semi-persistent, or aperiodic CSI reference signal transmission method. For CSI-RS, non-zero power (NZP) CSI-RS and zero power (ZP) CSI-RS with zero transmission power (or zero reception power) may be defined. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmission power or no transmission. PTRS is used to track the phase on the time axis for the purpose of compensating for frequency offset caused by phase noise. TRS is used to compensate for Doppler shift during high-speed movement. Note that TRS may be used as one setting of CSI-RS. For example, radio resources may be configured as a TRS for one-port CSI-RS.

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

[0056] The DMRS is used to demodulate a modulated signal. Two types of DMRS may be defined: a reference signal for demodulating the PUCCH and a reference signal for demodulating the PUSCH, and both may be called DMRS. The SRS is used for measuring uplink channel state information (CSI), channel sounding, and beam management. The PTRS is used to track the phase on the time axis in order to compensate for the frequency offset caused by phase noise.

[0057] The downlink physical channels and / or downlink physical signals are collectively referred to as downlink signals. The uplink physical channels and / or uplink physical signals are collectively referred to as uplink signals. The downlink physical channels and / or uplink physical channels are collectively referred to as physical channels. The downlink physical signals and / or uplink physical signals are collectively referred to as physical signals.

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

[0059] Fig. 2 is a diagram showing an example of an SS / PBCH block (also referred to as a synchronization signal block, SS block, or SSB) and an SS burst set (also referred to as a synchronization signal burst set) according to this embodiment. Fig. 2 shows an example in which two SS / PBCH blocks are included in a periodically transmitted SS burst set, and the SS / PBCH block is composed of four consecutive OFDM symbols.

[0060] An SS / PBCH block is a unit block including at least a synchronization signal (PSS, SSS) and / or a PBCH. Transmitting a signal / channel included in an SS / PBCH block is expressed as transmitting an SS / PBCH block. When transmitting a synchronization signal and / or a PBCH using one or more SS / PBCH blocks in an SS burst set, the base station device 3 may use an independent downlink transmission beam for each SS / PBCH block.

[0061] In Fig. 2, the PSS, SSS and PBCH are time / frequency multiplexed in one SS / PBCH block, but the order in which the PSS, SSS and / or PBCH are multiplexed in the time domain may be different from the example shown in Fig. 2.

[0062] The SS burst set may be transmitted periodically. For example, a period for use in initial access and a period set for a connected (Connected or RRC_Connected) terminal device may be defined. The period set for a connected (Connected or RRC_Connected) terminal device may be set in the RRC layer. The period set for a connected (Connected or RRC_Connected) terminal 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. The period for use in initial access may be defined in advance in a specification or the like.

[0063] The SS burst set may be determined based on a system frame number (SFN), and the starting position (boundary) of the SS burst set may be determined based on the SFN and a period.

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

[0065] SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets are 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.

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

[0067] The number of SS / PBCH blocks (which may also be referred to as the number of SS blocks or SSBs) may be defined as, for example, the number of SS / PBCH blocks in an SS burst, or 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, or 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, or an SS burst set, or a period of SS / PBCH blocks.

[0068] Hereinafter, the reference signal described in this embodiment includes a downlink reference signal, a synchronization signal, an SS / PBCH block, a downlink DM-RS, a CSI-RS, an uplink reference signal, an SRS, and / or an uplink DM-RS. For example, the downlink reference signal, the synchronization signal, and / or the SS / PBCH block may be referred to as a reference signal. The reference signal used in the downlink includes a downlink reference signal, a synchronization signal, an SS / PBCH block, a downlink DM-RS, a CSI-RS, and the like. The reference signal used in the uplink includes an uplink reference signal, an SRS, and / or an uplink DM-RS, and the like.

[0069] The reference signal may be used for radio resource measurement (RRM) and for beam management.

[0070] Beam management may be a procedure performed by base station device 3 and / or terminal device 1 to align the directivity of an analog and / or digital beam in a transmitting device (base station device 3 in the case of downlink and terminal device 1 in the case of uplink) with the directivity of an analog and / or digital beam in a receiving device (terminal device 1 in the case of downlink and base station device 3 in the case of uplink) to obtain beam gain.

[0071] In addition, procedures for configuring, setting up or establishing a beam pair link may include the following procedures. Beam selection Beam refinement Beam recovery

[0072] For example, beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1. Beam improvement may be a procedure for selecting a beam with a higher gain, or changing the beam between the base station device 3 and the terminal device 1 to an optimal one due to movement of the terminal device 1. Beam recovery may be a procedure for reselecting a beam when the quality of the communication link is degraded due to blockage caused by the passage of an obstruction or a person in communication between the base station device 3 and the terminal device 1.

[0073] Beam management may include beam selection, beam improvement. Beam recovery may include the following procedures: Beam failure detection New beam discovery · Sending a beam recovery request -Monitoring responses to beam recovery requests

[0074] For example, when selecting a transmission beam of the base station device 3 in the terminal device 1, the RSRP (Reference Signal Received Power) of the SSS included in the CSI-RS or SS / PBCH block may be used, or the CSI may be used. In addition, a CSI-RS resource index (CRI) may be used as a report to the base station device 3, or an index indicated by a sequence of the PBCH included in the SS / PBCH block and / or a demodulation reference signal (DMRS) used for demodulating the PBCH may be used.

[0075] Furthermore, the base station device 3 instructs the terminal device 1 of a time index of CRI or SS / PBCH when instructing the beam, and the terminal device 1 receives based on the instructed time index of CRI or SS / PBCH. At this time, the terminal device 1 may set a spatial filter based on the instructed time index of CRI or SS / PBCH and receive. Furthermore, the terminal device 1 may receive using the assumption of quasi-co-location (QCL). When a signal (antenna port, synchronization signal, reference signal, etc.) is "QCL" with another signal (antenna port, synchronization signal, reference signal, etc.) or when "the assumption of QCL is used," it can be interpreted that a signal is associated with another signal.

[0076] Two antenna ports are said to be QCLs if the long-term properties of the channel over which a symbol at one antenna port is carried can be inferred from the channel over which a symbol at the other antenna port is carried. The long-term properties of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if antenna port 1 and antenna port 2 are QCLs with respect to average delay, it means that the receive timing of antenna port 2 can be inferred from the receive timing of antenna port 1.

[0077] This QCL can also be extended to beam management. For this purpose, a spatially extended QCL may be newly defined. For example, the long term properties of a channel in the spatial domain may be the angle of arrival (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and / or the angle spread (e.g. ASA (Angle Spread of Arrival) and ZSA (Zenith angle Spread of Arrival)) in a radio link or channel, the angle of departure (AoD, ZoD, etc.) and its angle spread (e.g. ASD (Angle Spread of Departure) and ZSD (Zenith angle Spread of Departure)), spatial correlation, and reception spatial parameters.

[0078] For example, if antenna port 1 and antenna port 2 can be considered as a QCL in terms of receive spatial parameters, it means that the receive beam for receiving a signal from antenna port 2 can be inferred from the receive beam (receive spatial filter) for receiving a signal from antenna port 1.

[0079] A combination of long-range properties that may be considered to be a QCL may be defined as a QCL type. For example, the following types may be defined: Type A: Doppler shift, Doppler spread, average delay, delay spread Type B: Doppler shift, Doppler spread Type C: Average delay, Doppler shift Type D: Reception spatial parameters

[0080] The above-mentioned QCL type may be set and / or indicated as a transmission configuration indication (TCI) in the RRC and / or MAC layer and / or DCI, which indicates the assumption of QCL between one or two reference signals and PDCCH or PDSCH DMRS. For example, when the index #2 of the SS / PBCH block and the QCL type A+QCL type B are set and / or indicated as one state of the TCI when the terminal device 1 receives the PDCCH, the terminal device 1 may receive the DMRS of the PDCCH and perform synchronization and propagation path estimation by regarding the Doppler shift, Doppler spread, average delay, delay spread, reception spatial parameters, and long-range characteristics of the channel when receiving the SS / PBCH block index #2 as the long-range characteristics of the channel. At this time, the reference signal indicated by the TCI (SS / PBCH block in the above example) may be referred to as a source reference signal, and the reference signal (PDCCH DMRS in the above example) influenced by the long-range characteristics inferred from the long-range characteristics of the channel when receiving the source reference signal may be referred to as a target reference signal. Furthermore, the TCI may be configured by RRC with one or more TCI states and a combination of a source reference signal and a QCL type for each state, and may be indicated to the terminal device 1 by the MAC layer or DCI.

[0081] With this method, operations of the base station device 3 and the terminal device 1 equivalent to beam management may be defined as beam management and beam instruction / reporting, based on the assumption of QCL in the spatial domain and radio resources (time and / or frequency).

[0082] A subframe will be described below. In this embodiment, a subframe is referred to as a subframe, but it may also be referred to as a resource unit, a radio frame, a time period, a time interval, or the like.

[0083] FIG. 3 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 is 10 ms long. Each radio frame is composed of 10 subframes and W slots. One slot is composed of X OFDM symbols. That is, one subframe has a length of 1 ms. Each slot has a time length defined by a subcarrier interval. For example, when the subcarrier interval of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix), X=7 or X=14, which are 0.5 ms and 1 ms, respectively. When the subcarrier interval is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. For example, when X=14, when the subcarrier interval is 15 kHz, W=10, and when the subcarrier interval is 60 kHz, W=40. FIG. 3 shows the case of X=7 as an example. It can be similarly extended to the case of X=14. Also, the uplink slot is defined similarly, and the downlink slot and the uplink slot may be defined separately. Also, the bandwidth of the cell in FIG. 3 may be defined as a part of the band (BWP: BandWidth Part). Also, the slot may be defined as a transmission time interval (TTI: Transmission Time Interval). The slot may not be defined as a TTI. The TTI may be a transmission period of a transport block.

[0084] 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 subcarriers constituting one slot depends on the downlink and uplink bandwidths of the cell, respectively. Each element in the resource grid is called a resource element. A resource element may be identified by a subcarrier number and an OFDM symbol number.

[0085] A resource grid is used to represent the mapping of resource elements of a certain physical downlink channel (such as PDSCH) or uplink channel (such as PUSCH). For example, when the subcarrier spacing is 15 kHz, the number of OFDM symbols included in a subframe is X=14, and in the case of NCP, one physical resource block is defined by 14 consecutive OFDM symbols in the time domain and 12*Nmax consecutive subcarriers in the frequency domain. Nmax is the maximum number of resource blocks determined by the subcarrier spacing setting μ described later. That is, the resource grid is composed of (14*12*Nmax,μ) resource elements. In the case of ECP (Extended CP), since only a subcarrier spacing of 60 kHz is supported, one physical resource block 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 consists of (48*12*Nmax,μ) resource elements.

[0086] As resource blocks, a reference resource block, a common resource block, a physical resource block, and a virtual resource block are defined. One resource block is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may be a resource block with 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 may simply be referred to as a "reference point"). The common resource block is a resource block numbered in ascending order from 0 at each subcarrier interval setting μ from reference point A. The above-mentioned resource grid is defined by this common resource block. The physical resource block is a resource block numbered in ascending order from 0 included in a band part (BWP) described later, and the physical resource block is a resource block numbered in ascending order from 0 included in the band part (BWP). A certain physical uplink channel is first mapped to a virtual resource block. Then, the virtual resource block is mapped to a physical resource block. Hereinafter, a resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

[0087] Next, we will explain the subcarrier spacing setting μ. As mentioned above, NR supports one or more OFDM numerologies. For a given BWP, the subcarrier spacing setting μ (μ=0,1,...,5) and the cyclic prefix length are given by the higher layer for the downlink BWP and by the higher layer for the uplink BWP. Here, when μ is given, the subcarrier spacing Δf is given by Δf=2^μ·15(kHz).

[0088] For 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 setting and cyclic prefix, N^{slot}_{symb} consecutive OFDM symbols are in a slot, where N^{slot}_{symb} is 14. The start of a slot n^{μ}_{s} in a subframe is aligned in time with the start of the N^{slot}_{symb}th OFDM symbol of n^{μ}_{s} in the same subframe.

[0089] Next, subframes, slots, and minislots will be described. FIG. 4 is a diagram showing the relationship between subframes, slots, and minislots in the time domain. As shown in the figure, three types of time units are defined. A subframe is 1 ms regardless of the subcarrier spacing, the number of OFDM symbols included in a slot is 7 or 14, and the slot length differs depending on the subcarrier spacing. Here, when the subcarrier spacing is 15 kHz, one subframe includes 14 OFDM symbols. A downlink slot may be referred to as PDSCH mapping type A. An uplink slot may be referred to as PUSCH mapping type A.

[0090] A minislot (which may be called a subslot) is a time unit consisting of OFDM symbols fewer than the number of OFDM symbols contained in a slot. The figure shows an example in which a minislot is composed of two OFDM symbols. The OFDM symbols in a minislot 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 called 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 a reference signal and data are fixed. A downlink minislot may be called PDSCH mapping type B. An uplink minislot may be called PUSCH mapping type B.

[0091] FIG. 5 is a diagram showing an example of a slot format. Here, an example is shown in which the subcarrier spacing is 15 kHz and the slot length is 1 ms. In the figure, D indicates the downlink and U indicates the uplink. As shown in the figure, within a certain time interval (for example, the minimum time interval that must be allocated to one UE in the system), Downlink symbol Flexible Symbols Uplink symbol The ratio may include one or more of the following. Note that these ratios may be predetermined as a slot format. Also, they may be defined by the number of downlink OFDM symbols included in the slot, or the start and end positions within the slot. Also, they may be defined by the number of uplink OFDM symbols or DFT-S-OFDM symbols included in the slot, or the start and end positions within the slot. Note that the scheduling of a slot may be expressed as the scheduling of a resource in which the relative time positions of the reference signal and the slot boundary are fixed.

[0092] The terminal device 1 may receive a downlink signal or a downlink channel using a downlink symbol or a flexible symbol. The terminal device 1 may transmit an uplink signal or a downlink channel using an uplink symbol or a flexible symbol.

[0093] FIG. 5(a) shows an example in which a certain time interval (for example, the minimum unit of time resource that can be assigned to one UE, or may be referred to as a time unit, etc., or a plurality of minimum units of time resource may be bundled and referred to as a time unit) is entirely used for downlink transmission, and FIG. 5(b) shows an example in which the first time resource is used for uplink scheduling, for example, via PDCCH, and an uplink signal is transmitted via a flexible symbol including a processing delay for PDCCH, a switching time from downlink to uplink, and generation of a transmission signal. FIG. 5(c) shows an example in which the first time resource is used for transmitting PDCCH and / or downlink PDSCH, and is used for transmitting PUSCH or PUCCH via a gap for processing delay, a switching time from downlink to uplink, and generation of a transmission signal. Here, as an example, the uplink signal may be used for transmitting HARQ-ACK and / or CSI, i.e., UCI. In Fig. 5(d), the first time resource is used for transmitting PDCCH and / or PDSCH, and then, via a gap for processing delay, downlink to uplink switching time, and generation of a transmission signal, is used for transmitting uplink PUSCH and / or PUCCH. Here, as an example, the uplink signal may be used for transmitting uplink data, i.e., UL-SCH. In Fig. 5(e), all the time resources are used for uplink transmission (PUSCH or PUCCH).

[0094] The above-mentioned downlink part and uplink part may be composed of multiple OFDM symbols, similar to LTE.

[0095] FIG. 6 is a diagram showing an example of beamforming. A plurality of antenna elements are connected to one transmission unit (TXRU: Transceiver unit) 50, and the phase is controlled by a phase shifter 51 for each antenna element, and a beam can be directed in an arbitrary direction with respect to the transmission signal by transmitting from the antenna element 52. Typically, the TXRU may be defined as an antenna port, and in the terminal device 1, only the antenna port may be defined. Since the directivity can be directed in an arbitrary direction by controlling the phase shifter 51, the base station device 3 can communicate with the terminal device 1 using a beam with high gain.

[0096] Hereinafter, the bandwidth part (BWP, Bandwidth part) will be described. The BWP is also referred to as a carrier BWP. The BWP may be set for each of the downlink and the uplink. The BWP is defined as a set of consecutive physical resources selected from a consecutive subset of common resource blocks. The terminal device 1 can be set with up to 4 BWPs in which one downlink carrier BWP (DL BWP) is activated at a certain time. The terminal device 1 can be set with up to 4 BWPs in which one uplink carrier BWP (UL BWP) is activated at a certain time. In the case of carrier aggregation, the BWP may be set in each serving cell. At this time, the fact that one BWP is set in a certain serving cell may be expressed as the BWP not being set. Also, the fact that two or more BWPs are set may be expressed as the BWP being set.

[0097] <MAC entity operation> In an activated serving cell, there is always one active BWP. BWP switching for a serving cell is used to activate an inactive BWP and deactivate an active BWP. BWP switching for a serving cell is controlled by a PDCCH indicating a downlink assignment or an uplink grant. BWP switching for a serving cell may also be controlled by a BWP inactivity timer, by RRC signaling, or by the MAC entity itself at the start of a random access procedure. Upon addition of an SpCell (PCell or PSCell) or activation of an SCell, one BWP is first active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The first active DL BWP and the first active UL BWP may be specified in an RRC message sent from the base station device 3 to the terminal device 1. The active BWP for a serving cell is specified by the RRC or PDCCH sent from the base station device 3 to the terminal device 1. Also, the first active DL BWP and the UL BWP may be included in the message 4. In an unpaired spectrum (such as a TDD band), the DL BWP and the UL BWP are paired, and BWP switching is common for the UL and DL. In the active BWP for each activated serving cell for which a BWP is configured, the MAC entity of the terminal device 1 applies normal processing. The normal processing includes transmitting a UL-SCH, transmitting a RACH, monitoring a PDCCH, transmitting a PUCCH, transmitting an SRS, and receiving a DL-SCH.For each activated serving cell with BWP configured, in the inactive BWP, the MAC entity of the terminal device 1 does not transmit UL-SCH, does not transmit RACH, does not monitor PDCCH, does not transmit PUCCH, does not transmit SRS, and does not receive DL-SCH. When a certain serving cell is deactivated, the active BWP may be made non-existent (for example, the active BWP is deactivated).

[0098] <RRC operation> The BWP information element (IE) included in the RRC message (system information to be notified, information sent in the dedicated RRC message) is used to configure the BWP. The RRC message transmitted from the base station device 3 is received by the terminal device 1. For each serving cell, the network (such as the base station device 3) configures at least an initial BWP for the terminal device 1, including at least a downlink BWP and one (such as when the serving cell is configured for uplink) or two (such as when the supplementary uplink in the appendix is used) uplink BWPs. Further, the network may configure additional uplink BWPs or downlink BWPs for a certain serving cell. The BWP configuration is divided into uplink parameters and downlink parameters. Also, the BWP configuration is divided into common parameters and dedicated parameters. The common parameters (such as BWP uplink common IE and BWP downlink common IE) are cell-specific. The common parameters of the initial BWP of the primary cell are also provided in the system information. For all other serving cells, the network provides the common parameters by dedicated signals. The BWP is identified by the BWP ID. The initial BWP has a BWP ID of 0. The BWP IDs of other BWPs take values from 1 to 4.

[0099] The initial DL BWP may be defined by the PRB location and the number of consecutive PRBs, subcarrier spacing, and cyclic prefix for the control resource set (CORESET) for the type 0 PDCCH common search space. That is, the initial DL BWP may be configured by pdcch-ConfigSIB1 included in the MIB or PDCCH-ConfigCommon included in ServingCellCongfigCommon. The information element ServingCellCongfigCommon is used to configure cell-specific parameters of the serving cell for the terminal device 1. In this case, the size of the initial DL BWP is N size BWP、0 N size BWP、0 is the number of resource blocks that indicates the bandwidth of the initial DL BWP, where the initial DL BWP is of size N size BWP、0 This is the early DL BWP.

[0100] Also, the initial DL BWP may be provided to the terminal device 1 by SIB1 (systemInformationBlockType1) or ServingCellCongfigCommon (e.g., ServingCellConfigCommonSIB). The information element ServingCellCongfigCommonSIB is used to configure cell-specific parameters of the serving cell for the terminal device 1 in SIB1. In this case, the size of the initial DL BWP is N size BWP、1 N size BWP、1 is N size BWP、0 may be equal to 。 N size BWP、1 is N size BWP、0 where the initial DL BWP is of size N size BWP、1 This is the early DL BWP.

[0101] The initial UL BWP may be provided by SIB1 (systemInformationBlockType1) or initialUplinkBWP to the terminal device 1. The information element initialUplinkBWP is used to set the initial UL BWP.

[0102] In this embodiment, unless otherwise specified, the initial DL BWP is N size BWP、0 It may be the initial DL BWP of N size BWP、1 It may be an initial DL BWP.

[0103] The terminal device 1 may be configured with one primary cell and up to 15 secondary cells.

[0104] FIG. 14 is a flow diagram showing an example of a random access procedure of a MAC entity according to this embodiment.

[0105] <Start of random access procedure (S1001)> In Fig. 14, S1001 is a procedure related to random access procedure initialization. In S1001, the random access procedure is initiated by a PDCCH order, the MAC entity itself, a beam failure notification from a lower layer, or RRC, etc. The random access procedure in the SCell is initiated only by a PDCCH order including a ra-PreambleIndex that is not set to 0b000000.

[0106] In S1001, the terminal device 1 receives random access setting information via a higher layer before initiating a random access procedure. The random access setting information may include one or more elements of the following information or information for determining / setting the following information: prach-ConfigIndex: A set of one or more time / frequency resources (also called random access channel occasions, PRACH occasions, RACH occasions) available for transmitting a random access preamble preambleReceivedTargetPower: initial power of the preamble (can be the target received power) rsrp-ThresholdSSB: Reference Signal Received Power (RSRP) threshold for selection of SS / PBCH blocks (which may be associated random access preambles and / or PRACH opportunities) rsrp-ThresholdCSI-RS: Reference Signal Received Power (RSRP) threshold for selection of CSI-RS (which may be associated random access preamble and / or PRACH opportunity) · rsrp-ThresholdSSB-SUL: Reference Signal Received Power (RSRP) threshold for selection between NUL (Normal Uplink) and SUL (Supplementary Uplink) carriers. powerControlOffset: Power offset between rsrp-ThresholdSSB and rsrp-ThresholdCSI-RS when a random access procedure is initiated for beam failure recovery. ·powerRampingStep: Power ramping step (power ramping factor). Indicates the step of the transmit power ramped up based on the preamble transmission counter PREAMBLE_TRANSMISSION_COUNTER. ra-PreambleIndex: one or more available random access preambles or one or more available random access preambles in the plurality of random access preamble groups ra-ssb-OccasionMaskIndex: Information to determine the PRACH opportunities allocated to the SS / PBCH blocks on which the MAC entity transmits the random access preamble. ·ra-OccasionList: Information for determining the PRACH opportunities assigned to the CSI-RS on which the MAC entity may transmit a random access preamble ·preamTransMax: Maximum number of preamble transmissions ssb-perRACH-OccasionAndCB-PreamblesPerSSB (SpCell only): Parameter indicating the number of SS / PBCH blocks mapped to each PRACH opportunity and the number of random access preambles mapped to each SS / PBCH block ra-ResponseWindow: Time window for monitoring random access responses (SpCell only) -ra-ContentionResolutionTimer: Contention Resolution Timer · numberOfRA-PreamblesGroupA: number of random access preambles in random access preamble group A for each SS / PBCH block · PREAMBLE_TRANSMISSION_COUNTER: preamble transmission counter DELTA_PREAMBLE: Power offset value based on the random access preamble format · PREAMBLE_POWER_RAMPING_COUNTER: Preamble power ramping counter · PREAMBLE_RECEIVED_TARGET_POWER: Initial random access preamble power. Indicates the initial transmission power for the random access preamble transmission. · PREAMBLE_BACKOFF: Used to adjust the timing of random access preamble transmission.

[0107] When a random access procedure is initiated for a serving cell, the MAC entity refreshes the Msg3 buffer, sets the state variable PREAMBLE_TRANSMISSION_COUNTER to 1, sets the state variable PREAMBLE_POWER_RAMPING_COUNTER to 1, and sets the state variable PREAMBLE_BACKOFF to 0 ms. If the carrier used for the random access procedure is explicitly signaled, the MAC entity selects the signaled carrier to perform the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the signaled carrier. If the carrier used for the random access procedure is not explicitly signaled, and a SUL carrier is configured for the serving cell, and the RSRP of the downlink path loss reference is smaller than rsrp-ThresholdSSB-SUL, the MAC entity selects the SUL carrier to perform the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the SUL carrier. Otherwise, the MAC entity selects the NUL carrier to perform the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the NUL carrier.

[0108] <Start of random access procedure (S1002)> S1002 is a procedure for selecting a random access resource (including a time / frequency resource and / or a preamble index) in the MAC layer of the terminal device 1. The procedure for selecting a random access resource (including a time / frequency resource and / or a preamble index) in the MAC layer of the terminal device 1 will be described below.

[0109] The terminal device 1 sets a value for the preamble index (which may be referred to as PREAMBLE_INDEX) of the random access preamble to be transmitted in the following procedure.

[0110] The terminal device 1 (MAC entity) selects an SS / PBCH block or CSI-RS whose RSRP exceeds a predetermined threshold when (1) a random access procedure is initiated by a notification of beam failure from a lower layer, (2) a random access resource (which may be a PRACH opportunity) for non-contention based random access for a beam failure recovery request associated with an SS / PBCH block (also referred to as an SSB) or a CSI-RS is provided in the RRC parameters, and (3) the RSRP of one or more SS / PBCH blocks or CSI-RS exceeds a predetermined threshold. If a CSI-RS is selected and there is no ra-PreambleIndex associated with the selected CSI-RS, the MAC entity may set the ra-PreambleIndex associated with the selected SS / PBCH block to the preamble index (PREAMBLE_INDEX). Otherwise, the MAC entity sets the ra-PreambleIndex associated with the selected SS / PBCH block or CSI-RS to the preamble index.

[0111] The terminal device 1 sets the signaled ra-PreambleIndex to the preamble index when (1) ra-PreambleIndex is provided by PDCCH or RRC, (2) the value of the ra-PreambleIndex is not a value indicating a contention-based random access procedure (e.g., 0b000000), and (3) the SS / PBCH block or CSI-RS is not associated with a random access resource for non-contention-based random access by RRC. 0bxxxxxx means a bit string placed in a 6-bit information field.

[0112] When (1) random access resources for non-contention based random access associated with the SS / PBCH block are provided by RRC and (2) one or more SS / PBCH blocks whose RSRP exceeds a predetermined threshold are available among the associated SS / PBCH blocks, the terminal device 1 selects one of the SS / PBCH blocks whose RSRP exceeds the predetermined threshold and sets the ra-PreambleIndex associated with the selected SS / PBCH block to the preamble index.

[0113] When (1) a CSI-RS and a random access resource for non-contention based random access are associated in RRC, and (2) one or more CSI-RSs whose RSRP exceeds a predetermined threshold are available among the associated CSI-RS, the terminal device 1 selects one of the CSI-RSs whose RSRP exceeds the predetermined threshold, and sets the ra-PreambleIndex associated with the selected CSI-RS to the preamble index.

[0114] If none of the above conditions are satisfied, the terminal device 1 performs a contention-based random access procedure. In the contention-based random access procedure, the terminal device 1 selects an SS / PBCH block having an RSRP of the SS / PBCH block that exceeds a set threshold, and selects a preamble group. If a relationship between the SS / PBCH block and the random access preamble is set, the terminal device 1 randomly selects ra-PreambleIndex from one or more random access preambles associated with the selected SS / PBCH block and the selected preamble group, and sets the selected ra-PreambleIndex to the preamble index.

[0115] When the MAC entity selects one SS / PBCH block and an association between the PRACH opportunity and the SS / PBCH block is set, the MAC entity may determine the next available PRACH opportunity from among the PRACH opportunities associated with the selected SS / PBCH block. However, when the terminal device 1 selects one CSI-RS and an association between the PRACH opportunity and the CSI-RS is set, the terminal device 1 may determine the next available PRACH opportunity from among the PRACH opportunities associated with the selected CSI-RS.

[0116] The available PRACH opportunities may be determined based on mask index information, SSB index information, resource configuration configured in the RRC parameters, and / or selected reference signal (SS / PBCH block or CSI-RS). The resource configuration configured in the RRC parameters includes resource configuration per SS / PBCH block and / or resource configuration per CSI-RS.

[0117] The base station device 3 may transmit the resource configuration for each SS / PBCH block and / or the resource configuration for each CSI-RS to the terminal device 1 by an RRC message. The terminal device 1 receives the resource configuration for each SS / PBCH block and / or the resource configuration for each CSI-RS from the base station device 3 by an RRC message. The base station device 3 may transmit mask index information and / or SSB index information to the terminal device 1. The terminal device 1 acquires the mask index information and / or SSB index information from the base station device 3. The terminal device 1 may select a reference signal (SS / PBCH block or CSI-RS) based on a certain condition. The terminal device 1 may identify the next available PRACH opportunity based on the mask index information, the SSB index information, the resource configuration set in the RRC parameters, and the selected reference signal (SS / PBCH block or CSI-RS). The MAC entity of the terminal device 1 may instruct the physical layer to transmit a random access preamble using the selected PRACH opportunity.

[0118] The mask index information is information indicating an index of a PRACH opportunity available for transmitting a random access preamble. The mask index information may be information indicating a part of a PRACH opportunity of a group of one or more PRACH opportunities defined by the prach-ConfigurationIndex. The mask index information may also be information indicating a part of a PRACH opportunity of a group of PRACH opportunities to which a specific SSB index specified by the SSB index information is mapped.

[0119] The SSB index information is information indicating an SSB index corresponding to one of one or more SS / PBCH blocks transmitted by the base station device 3. The terminal device 1 that has received the message 0 identifies a group of PRACH opportunities to which the SSB index indicated by the SSB index information is mapped. The SSB index mapped to each PRACH opportunity is determined by the PRACH configuration index, the upper layer parameter SB-perRACH-Occasion, and the upper layer parameter cb-preamblePerSSB.

[0120] <Transmission of random access preamble (S1003)> S1003 is a procedure for random access preamble transmission. For each random access preamble, the MAC entity increments the state variable PREAMBLE_POWER_RAMPING_COUNTER by one if (1) the state variable PREAMBLE_TRANSMISSION_COUNTER is greater than 1, and (2) no notification of the power ramp counter being stopped has been received from higher layers, and (3) the selected SS / PBCH block has not changed.

[0121] The MAC entity then selects a value for DELTA_PREAMBLE and sets the state variable PREAMBLE_RECEIVED_TARGET_POWER to a predetermined value, which is calculated as preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER-1)*powerRampingStep.

[0122] The MAC entity then calculates the RA-RNTI associated with the PRACH opportunity on which the random access preamble is transmitted, other than the non-contention based random access preamble for beam failure recovery request. The RA-RNTI is calculated by RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id, where s_id is the index of the first OFDM symbol of the PRACH to be transmitted and takes values ​​from 0 to 13. t_id is the index of the first slot of the PRACH in the system frame and takes values ​​from 0 to 79. f_id is the index of the PRACH in the frequency domain and takes values ​​from 0 to 7. ul_carrier_id is the uplink carrier used for Msg1 transmission. The ul_carrier_id for the NUL carrier is 0, and the ul_carrier_id for the SUL carrier is 1.

[0123] The MAC entity instructs the physical layer to transmit a random access preamble using the selected PRACH.

[0124] <Receiving random access response (S1004)> S1004 is a procedure for receiving a random access response. Once the random access preamble is transmitted, the MAC entity performs the following operations regardless of the possible occurrence of a measurement gap. Here, the random access response may be a MAC PDU for the random access response.

[0125] A MAC PDU (Random Access Response MAC PDU) consists of one or more MAC subPDUs and possible padding. Each MAC subPDU consists of one of the following: -MAC subheader containing only the Backoff Indicator -MAC subheader showing only RAPID -MAC subheader and MAC RAR (MAC payload for Random Access Response) indicating RAPID

[0126] A MAC subPDU containing only a Backoff Indicator is placed at the beginning of a MAC PDU. Padding is placed at the end of a MAC PDU. A MAC subPDU containing only RAPID and a MAC subPDU containing RAPID and a MAC RAR can be placed anywhere between a MAC subPDU containing only a Backoff Indicator and the padding.

[0127] The MAC RAR has a fixed size and is composed of reserved bits to be set to 0, transmission timing adjustment information (TA command, Timing Advance Command), UL grant (UL grant, RAR UL grant), and TEMPORARY_C-RNTI. Hereinafter, the RAR message may be a MAC RAR. The RAR message may be a random access response.

[0128] In S1004, if the MAC entity has transmitted a non-contention based random access preamble for a beam failure recovery request, the MAC entity starts a random access response window (ra-ResponseWindow) at the first PDCCH opportunity from the end of the random access preamble transmission. Then, while the random access response window is running, the MAC entity monitors the PDCCH of the SpCell identified by the C-RNTI for a response to the beam failure recovery request. Here, the duration (window size) of the random access response window is given by the ra-ResponseWindow included in the upper layer parameter BeamFailureRecoveryConfig. Otherwise, the MAC entity starts a random access response window (ra-ResponseWindow) at the first PDCCH opportunity from the end of the random access preamble transmission. Here, the duration (window size) of the random access response window is given by the ra-ResponseWindow included in the upper layer parameter RACH-ConfigCommon. Then, while the random access response window is running, the MAC entity monitors the PDCCH of the SpCell identified by the RA-RNTI for a random access response. Here, the information element BeamFailureRecoveryConfig is used to configure RACH resources and candidate beams for beam failure recovery for the terminal device 1 in case of beam failure detection. The information element RACH-ConfigCommon is used to specify cell-specific random access parameters.

[0129] The MAC entity may consider the random access procedure to be successfully completed if (1) an acknowledgement of the PDCCH transmission is received from lower layers, and (2) the PDCCH transmission is scrambled by the C-RNTI, and (3) the MAC entity has sent a non-contention based random access preamble for a beam failure recovery request.

[0130] Next, the MAC entity performs the following actions if (1) a downlink assignment is received in the PDCCH for the RA-RNTI and (2) the received transport block is successfully decoded.

[0131] The MAC entity shall set PREAMBLE_BACKOFF to the value of the BI field contained in the MAC subPDU if the random access response includes a MAC subPDU containing a BackoffIndicator, otherwise the MAC entity shall set PREAMBLE_BACKOFF to 0 ms.

[0132] The MAC entity may consider the random access response as successfully received if it contains a MAC subPDU containing a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX.

[0133] If (1) the random access response is deemed to have been received successfully, and (2) the random access response contains a MAC subPDU containing only RAPID, the MAC entity shall consider the random access procedure to have been completed successfully, and shall indicate to upper layers the receipt of an acknowledgement to the symstem information request. Here, if condition (2) is not met, the MAC entity shall apply the following action A to the serving cell from which the random access preamble is transmitted.

[0134] <Start of Action A> The MAC entity processes the received transmission timing adjustment information (Timing Advance Command) and indicates to the lower layer the preambleReceivedTargetPower and the amount of power ramping applied to the latest random access preamble transmission, where the transmission timing adjustment information is used to adjust the transmission timing deviation between the terminal device 1 and the base station device 3 from the received random access preamble.

[0135] If the serving cell for the random access procedure is an SCell for SRS only, the MAC entity may ignore the received UL grant, otherwise the MAC entity processes and indicates the value of the received UL grant to lower layers.

[0136] If no random access preamble is selected by the MAC entity from within the range of contention based random access preambles, the MAC entity may consider the random access procedure to be successfully completed.

[0137] <End of Action A> When the random access preamble is selected by the MAC entity from the range of contention-based random access preambles, the MAC entity sets TEMPORARY_C-RNTI to the value of the Temporary C-RNTI field included in the received random access response. Then, when the random access response is successfully received for the first time in this random access procedure, the MAC entity notifies a predetermined entity (Multiplexing and assembly entity) that the next uplink transmission will include C-RNTI MAC CE if no transmission is being performed on the CCCH logical channel (common control channel logical channel), and obtains a MAC PDU for transmission from the predetermined entity (Multiplexing and assembly entity) and stores the obtained MAC PDU in the Msg3 buffer. When a transmission is being performed on the CCCH logical channel, the MAC entity obtains a MAC PDU for transmission from the predetermined entity (Multiplexing and assembly entity) and stores the obtained MAC PDU in the Msg3 buffer.

[0138] If at least one of the following conditions (3) to (4) is satisfied, the MAC entity considers that the random access response has not been successfully received and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by one. The MAC entity indicates a random access problem to higher layers when the value of the preamble transmission counter reaches a predefined value (maximum number of preamble transmissions + 1) and a random access preamble is transmitted in the SpCell. And, if the random access procedure was initiated due to an SI request, the MAC entity considers that the random access procedure has not been completed successfully.

[0139] The MAC entity considers that the random access procedure is not completed successfully if the value of the preamble transmission counter reaches a predefined value (maximum number of preamble transmissions + 1) and the random access preamble is transmitted on the SCell.

[0140] Condition (3) is that the random access response window set in RACH-ConfigCommon has expired and a random access response including a random access preamble identifier that matches the transmitted preamble index has not been received. Condition (4) is that the random access response window set in BeamFailureRecoveryConfig has expired and a PDCCH scrambled by the C-RNTI has not been received.

[0141] If the random access procedure is not completed, the MAC entity selects a random backoff time between 0 and PREAMBLE_BACKOFF if the random access preamble was selected by the MAC itself from among the range of contention-based random access preambles in the random access procedure, delays the next random access preamble transmission by the selected backoff time, and executes S1002. If the random access procedure is not completed, the MAC entity executes S1002 if the random access preamble was not selected by the MAC itself from among the range of contention-based random access preambles in the random access procedure.

[0142] The MAC entity may stop the random access response window upon successfully receiving a random access response containing a random access preamble identifier that matches the transmitted preamble index.

[0143] The terminal device 1 transmits a message 3 on the PUSCH based on the UL grant.

[0144] <Collision Resolution (S1005)> S1005 is a procedure related to contention resolution.

[0145] Once Msg3 is transmitted, the MAC entity starts the collision resolution timer and restarts the collision resolution timer at each HARQ retransmission. The MAC entity monitors the PDCCH while the collision resolution timer is running, regardless of the possible occurrence of measurement gaps.

[0146] When receiving a PDCCH transmission acknowledgement from the lower layer and C-RNTI MAC CE is included in Msg3, the MAC entity shall consider the contention resolution successful, stop the contention resolution timer, discard the TEMPORARY_C-RNTI and consider the random access procedure to be completed successfully if at least one of the following conditions (5) to (7) is satisfied:

[0147] Condition (5) is that the random access procedure is initiated by the MAC sublayer itself or the RRC sublayer, the PDCCH transmission is scrambled by the C-RNTI, and the PDCCH transmission includes an uplink grant for the initial transmission. Condition (6) is that the random access procedure is initiated by a PDCCH order, and the PDCCH transmission is scrambled by the C-RNTI. Condition (7) is that the random access procedure is initiated for beam failure recovery, and the PDCCH transmission is scrambled by the C-RNTI.

[0148] If a CCCH SDU (UE contention resolution identity) is included in Msg3 and the PDCCH transmission is scrambled by TEMPORARY_C-RNTI, the MAC entity stops the collision resolution timer if the MAC PDU is successfully decoded. If the successfully decoded MAC PDU then includes a UE contention resolution identity MAC CE and the UE collision resolution identity in the MAC CE matches the CCCH SDU transmitted in Msg3, the MAC entity considers the collision resolution successful and finishes disassembly and demultiplexing of the MAC PDU. Then, if a random access procedure is initiated for the SI request, the MAC entity indicates to the upper layer the receipt of a positive response to the SI request. If a random access procedure is not initiated for the SI request, the MAC entity sets the C-RNTI to the value of TEMPORARY_C-RNTI. The MAC entity then discards the TEMPORARY_C-RNTI and considers the random access procedure to be successfully completed.

[0149] If the MAC entity finds that the UE collision resolution identity in the MAC CE does not match the CCCH SDU sent in Msg3, it shall discard the TEMPORARY_C-RNTI, consider the collision resolution unsuccessful, and discard the successfully decoded MAC PDU.

[0150] If the collision resolution timer expires, the MAC entity discards the TEMPORARY_C-RNTI and considers contention resolution unsuccessful. If the MAC entity considers contention resolution unsuccessful, it flushes the HARQ buffers used for the transmission of the MAC PDU in the Msg3 buffer and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by one. If the preamble transmission counter value reaches a predefined value (maximum number of preamble transmissions + 1), the MAC entity indicates a random access problem to upper layers. And, if the random access procedure was initiated due to an SI request, the MAC entity considers the random access procedure to have not been completed successfully.

[0151] If the random access procedure is not completed, the MAC entity selects a random backoff time between 0 and PREAMBLE_BACKOFF, delays the next random access preamble transmission by the selected backoff time, and executes S1002.

[0152] Once the random access procedure is completed, the MAC entity shall discard any non-contention based random access resources explicitly signalled for non-contention based random access procedures other than the non-contention based random access procedure for a beam failure recovery request, and shall flush the HARQ buffers used for the transmission of MAC PDUs in the Msg3 buffer.

[0153] The control resource set (CORESET) in this embodiment will be described below.

[0154] A control resource set (CORESET) is a time and frequency resource for searching downlink control information. The configuration information of a CORESET includes a CORESET identifier (ControlResourceSetId, CORESET-ID) and information for identifying the frequency resource of the CORESET. The information element ControlResourceSetId (CORESET identifier) ​​is used to identify a control resource set in a serving cell. The CORESET identifier is used between BWPs in a serving cell. The CORESET identifier is unique between BWPs in a serving cell. The number of CORESETs in each BWP is limited to 3, including the initial CORESET. In a serving cell, the value of the CORESET identifier ranges from 0 to 11.

[0155] The control resource set identified by the identifier 0 (ControlResourceSetId 0) of CORESET is called CORESET#0. CORESET#0 may be configured by pdcch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellCongfigCommon. That is, the configuration information of CORESET#0 may be pdcch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellCongfigCommon. The configuration information of CORESET#0 may be configured by controlResourceSetZero included in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon. That is, the information element controlResourceSetZero is used to indicate CORESET#0 (common CORESET) of the initial DL BWP. The CORESET indicated by pdcch-ConfigSIB1 is CORESET#0. The information element pdcch-ConfigSIB1 in the MIB or the dedicated configuration is used to configure the initial DL BWP. The configuration information pdcch-ConfigSIB1 of CORESET for CORESET#0 does not include information that explicitly identifies the identifier of CORESET and the frequency resources (e.g., the number of consecutive resource blocks) and time resources (the number of consecutive symbols) of CORESET, but the frequency resources (e.g., the number of consecutive resource blocks) and time resources (the number of consecutive symbols) of CORESET for CORESET#0 can be implicitly specified by the information included in pdcch-ConfigSIB1. The information element PDCCH-ConfigCommon is used to configure cell-specific PDCCH parameters provided in the SIB. PDCCH-ConfigCommon may also be provided at the time of handover and addition of PSCell and / or SCell. The configuration information of CORESET#0 is included in the configuration of the initial BWP.That is, the configuration information of CORESET#0 does not need to be included in the configuration of BWPs other than the initial BWP. controlResourceSetZero corresponds to 4 bits (e.g., the 4 most significant bits) of pdcch-ConfigSIB1. CORESET#0 is a control resource set for the type 0 PDCCH common search space.

[0156] The configuration information of an additional common CORESET (additional common control resource set) may be configured by the commonControlResourceSet included in PDCCH-ConfigCommon. The configuration information of the additional common CORESET may be used to specify an additional common CORESET used for the random access procedure. The configuration information of the additional common CORESET may be included in the configuration of each BWP. The identifier of the CORESET indicated in the commonControlResourceSet takes a value other than 0.

[0157] The common CORESET may be a CORESET (for example, an additional common CORESET) used in a random access procedure. In addition, in this embodiment, the common CORESET may include a CORESET set by the setting information of CORESET#0 and / or an additional common CORESET. In other words, the common CORESET may include CORESET#0 and / or an additional common CORESET. CORESET#0 may be referred to as common CORESET#0. The terminal device 1 may also refer to (obtain) the setting information of the common CORESET in a BWP other than the BWP in which the common CORESET is set.

[0158] Configuration information of one or more CORESETs may be configured by PDCCH-Config. The information element PDCCH-Config is used to configure UE-specific PDCCH parameters (e.g., CORSET, search space, etc.) for a BWP. PDCCH-Config may be included in the configuration of each BWP.

[0159] That is, in this embodiment, the configuration information of the common CORESET indicated by MIB is pdcch-ConfigSIB1, the configuration information of the common CORESET indicated by PDCCH-ConfigCommon is controlResourceSetZero, and the configuration information of the common CORESET (additional common CORESET) indicated by PDCCH-ConfigCommon is commonControlResourceSet. Also, the configuration information of one or more CORESETs (UE specifically configured Control Resource Sets, UE-specific CORESETs) indicated by PDCCH-Config is controlResourceSetToAddModList.

[0160] A search space is defined to search for PDCCH candidates. A searchSpaceType included in the configuration information of a search space indicates whether the search space is a common search space (CSS) or a UE-specific search space (USS). A UE-specific search space is derived from at least the value of a C-RNTI set by a terminal device 1. That is, a UE-specific search space is derived individually for each terminal device 1. A common search space is a search space common to multiple terminal devices 1, and is composed of CCEs (Control Channel Elements) of a predetermined index. A CCE is composed of multiple resource elements. The configuration information of a search space includes information on a DCI format to be monitored in the search space.

[0161] The configuration information of the search space includes an identifier of the CORESET identified by the configuration information of the CORESET. The CORESET identified by the identifier of the CORESET included in the configuration information of the search space is associated with the search space. In other words, the CORESET associated with the search space is a CORESET identified by the identifier of the CORESET included in the search space. The DCI format indicated by the configuration information of the search space is monitored in the associated CORESET. Each search space is associated with one CORESET. For example, the configuration information of the search space for the random access procedure may be configured by ra-SearchSpace. That is, the DCI format to which a CRC scrambled by RA-RNTI or TC-RNTI is added is monitored in the CORESET associated with the ra-SearchSpace.

[0162] As described above, the configuration information of CORESET#0 is included in the configuration of the initial DL BWP. The configuration information of CORESET#0 does not have to be included in the configuration of a BWP (additional BWP) other than the initial DL BWP. When a BWP (additional BWP) other than the initial DL BWP refers to the configuration information of CORESET#0 (refer, acquire, etc.), it may be necessary to at least satisfy that CORESET#0 and SS blocks are included in the additional BWP in the frequency domain and that the same subcarrier interval is used. In other words, when a BWP (additional BWP) other than the initial BWP refers to the configuration information of CORESET#0 (refer, acquire, etc.), it may be necessary to at least satisfy that the bandwidth and SS blocks of the initial DL BWP are included in the additional BWP in the frequency domain and that the same subcarrier interval is used. At this time, the search space (e.g., ra-SearchSpace) configured for the additional BWP can refer to the configuration information of CORESET#0 (refer, acquire, etc.) by indicating the identifier 0 of CORESET#0. Furthermore, if the bandwidth of the initial DL BWP is included in the additional DL BWP in the frequency domain, and the SS block is included in the additional DL BWP, and any of the conditions of using the same subcarrier spacing is not satisfied, the terminal device 1 does not need to expect the additional DL BWP to refer to the configuration information of CORESET#0. That is, in this case, the base station device 3 does not need to configure the terminal device 1 that the additional DL BWP refers to the configuration information of CORESET#0. Here, the initial DL BWP is of size N size BWP、0 It may be an initial DL BWP.

[0163] When a (additional) DL BWP refers to (refer, acquire, etc.) the configuration information of the CORESET of another BWP, it may be necessary to at least satisfy that in the frequency domain, the CORESET (or the bandwidth of the BWP) and / or the SS block (associated) contained in the BWP is included in the additional BWP and uses the same subcarrier spacing. In other words, if any of the conditions in the frequency domain that the CORESET (or the bandwidth of the BWP) is included in the additional DL BWP and the SS block (associated) contained in the BWP is included in the additional DL BWP and uses the same subcarrier spacing is not satisfied, the terminal device 1 may not expect the additional DL BWP to refer to the configuration information of the CORESET set for that BWP.

[0164] The terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs arranged in each active serving cell configured to monitor the PDCCH. The set of PDCCH candidates corresponds to one or more search space sets. Monitoring means decoding each PDCCH candidate according to one or more DCI formats to be monitored. The set of PDCCH candidates monitored by the terminal device 1 is defined by a PDCCH search space set (PDCCH search space sets). One search space set is a common search space set or a UE-specific search space set. In the above, a search space set is referred to as a search space, a common search space set is referred to as a common search space, and a UE-specific search space set is referred to as a UE-specific search space. The terminal device 1 monitors PDCCH candidates in one or more of the following search space sets. - a Type0-PDCCH common search space set: This search space set is configured by higher layer parameters searchSpaceZero indicated in MIB or searchSpaceSIB1 indicated in PDCCH-ConfigCommon. This search space is for monitoring of DCI format of SI-RNRI scrambled CRC in the primary cell. - a Type0A-PDCCH common search space set: This search space set is configured by the higher layer parameter searchSpace-OSI indicated in PDCCH-ConfigCommon. This search space is for monitoring the DCI format of SI-RNRI scrambled CRC in the primary cell. - a Type1-PDCCH common search space set: This search space set is configured by the higher layer parameter PDCCH-ConfigCommon, search space for random access procedure (ra-SearchSpace). This search space is for monitoring DCI format of RA-RNRI or CRC scrambled in TC-RNTI in the primary cell. Type1-PDCCH common search space set is the search space set for random access procedure. - a Type2-PDCCH common search space set: This search space set is a higher layer parameter, -Configured by the search space for paging procedure (pagingSearchSpace) indicated in ConfigCommon. This search space is for monitoring the DCI format of the CRC scrambled with the P-RNTI in the primary cell. - a Type3-PDCCH common search space set: This search space set is a higher layer parameter, -The search space type indicated by Config is configured by a common search space (SearchSpace). This search space is for monitoring the DCI format of the CRC scrambled with INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI. For the primary line cell, it is for monitoring the DCI format of the CRC scrambled with C-RNTI or CS-RNTI(s). - a UE-specific search space set: This search space set is configured by a UE-specific search space (SearchSpace) with a search space type indicated by PDCCH-Config, which is a higher layer parameter. This search space is for monitoring the DCI format of the CRC scrambled with C-RNTI or CS-RNTI(s).

[0165] If the terminal device 1 is provided with one or more search space sets by corresponding upper layer parameters (searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, etc.) and the terminal device 1 is provided with a C-RNTI or a CS-RNTI, the terminal device 1 may monitor PDCCH candidates for DCI format 0_0 and DCI format 1_0 having the C-RNTI or CS-RNTI in the one or more search space sets.

[0166] The BWP configuration information is divided into DL BWP configuration information and UL BWP configuration information. The BWP configuration information includes information element bwp-Id (BWP identifier). The BWP identifier included in the DL BWP configuration information is used to identify (reference) the DL BWP in a serving cell. The BWP identifier included in the UL BWP configuration information is used to identify (reference) the UL BWP in a serving cell. BWP identifiers are assigned to each of DL BWP and UL BWP. For example, the BWP identifier corresponding to a DL BWP may be referred to as a DL BWP index. The BWP identifier corresponding to a UL BWP may be referred to as a UL BWP index. The initial DL BWP is referenced by DL BWP identifier 0. The initial UL BWP is referenced by UL BWP identifier 0. Other DL BWPs or other UL BWPs may each be referenced by BWP identifiers 1 to maxNrofBWPs. That is, a BWP identifier set to 0 (bwp-Id=0) is associated with the initial BWP and cannot be used for other BWPs. maxNrofBWPs is the maximum number of BWPs per serving cell, which is 4. That is, the other BWP identifiers can have values ​​from 1 to 4. Other higher layer configuration information is associated with a specific BWP using the BWP identifier. A DL BWP and a UL BWP having the same BWP identifier may mean that the DL BWP and the UL BWP are paired.

[0167] FIG. 7 is a diagram showing an example of BWP settings according to an embodiment of the present invention.

[0168] For each serving cell, one initial BWP is configured, which includes at least one DL BWP and one UL BWP. And for a serving cell, additional BWPs (additional UL BWP and / or additional DL BWP) may be configured. Up to four additional BWPs may be configured. However, in one serving cell, only one DL BWP and one UL BWP are active.

[0169] In FIG. 7, one initial BWP (BWP#0) and two additional BWPs (BWP#1 and BWP#2) are configured for a terminal device 1 in a certain serving cell. 801 is an initial DL BWP (DL BWP#0). 802 is an initial UL BWP (UL BWP#0). 805 is an additional DL BWP (DL BWP#1). 806 is an additional UL BWP (UL BWP#1). 808 is an additional DL BWP (DL BWP#2). 809 is an additional UL BWP (UL BWP#2). In the following, it is assumed that DL BWP#1 is activated and UL BWP#0 is activated. In other words, DL BWP#0 and UL BWP#1 are inactive BWPs. DL BWP#2 and UL BWP#2 are inactive BWPs. In this case, the activated DL BWP#1 may be referred to as an active DL BWP (active DL BWP, currently active DL BWP). The activated initial UL BWP#0 may be referred to as an initial active UL BWP (initial active UL BWP). The terminal device 1 performs downlink reception in the active DL BWP#1 and performs uplink transmission in the initial active UL BWP.

[0170] 803 is CORESET#0 configured for the initial DL BWP. 804 is an additional common CORESET configured for the initial DL BWP. 807 is a CORESET configured for the additional BWP#1. 810 is a CORESET configured for the additional BWP#2. 807 and 810 may be referred to as UE specific CORESETs (UE specifically configured Control Resource Sets). As described above, the configuration information of CORESET#0 (803) may be configured by pdcch-ConfigSIB1 or PDCCH-ConfigCommon. The configuration information of the additional common CORESET (804) may be configured by commonControlResourceSet included in PDCCH-ConfigCommon. The configuration information of CORESETs (807 and 810) may be configured by controlResourceSetToAddModList included in PDCCH-Config. The value of the identifier of CORESET 803 is given as 0. The value of the identifier of CORESET 804 may be given as 1. The value of the CORESET identifier in 807 may be given as 3. The value of the CORESET identifier in 810 may be given as 6. The value of the CORESET identifier included in the ra-searchspace for DL ​​BWP#0 is set to 1, and the value of the CORESET identifier included in the ra-searchspace for DL ​​BWP#2 is set to 6.

[0171] In FIG. 7, ra-searchspace is set for each of DL BWP#0, DL BWP#1, and DL BWP#2. As described above, the configuration information of the search space for the random access procedure may be set by ra-SearchSpace. As a first example, the identifier of the CORESET included in the ra-searchspace set for a certain DL BWP may be set to the value of the identifier of the CORESET that identifies the configuration information of the CORESET that is set for the DL BWP, or may be set to the value of the identifier of the CORESET that is included in the ra-SearchSpace set for the initial BWP. That is, the ra-searchspace set for a certain DL BWP may indicate the identifier of the CORESET that identifies the configuration information of the CORESET that is set for the DL BWP, or may indicate the identifier of the CORESET that is included in the ra-SearchSpace set for the initial BWP. That is, the ra-searchspace set for a certain DL BWP may not indicate the identifiers of the common and UE-specific CORESET that are set for DL ​​BWPs other than the DL BWP and the initial DL BWP. In other words, the base station device 3 may transmit an RRC message so that the ra-searchspace set for a certain DL BWP does not indicate the identifiers of the common and UE-specific CORESETs set for other DL BWPs other than the DL BWP and the initial DL BWP. For example, the value of the CORESET identifier included in the ra-searchspace for DL ​​BWP #1 may be set to 1 or 3. The value of the CORESET identifier included in the ra-searchspace for DL ​​BWP #1 is not set to 6. When the value of the CORESET identifier included in the ra-searchspace for DL ​​BWP #1 is set to 1, the terminal device 1 monitors the DCI format included in the ra-searchspace in the active DL BWP #1 based on the configuration information of CORESET #1 (804) identified by the CORESET identifier 1.When the value of the CORESET identifier included in the ra-searchspace for DL ​​BWP#1 is set to 3, the terminal device 1 monitors the DCI format included in the ra-searchspace in the active DL BWP#1 based on the configuration information of CORESET#3 (807) identified by the CORESET identifier 3. That is, the ra-searchspace set for a DL BWP may indicate the identifier of the CORESET that identifies the configuration information of the common CORESET. For example, the value of the CORESET identifier included in the ra-searchspace for DL ​​BWP#1 may be set to 1. That is, when CORESET#1 is set in the initial DL BWP, CORESET#0 cannot be called as the ra-searchspace. When CORESET#1 is not set in the initial DL BWP, CORESET#0 can be called as the ra-searchspace. However, as an extension of the first example, even when CORESET#1 is set in the initial DL BWP, CORESET#0 may be allowed to be called as the ra-searchspace by the DL BWP.

[0172] As a second example, the identifier of the CORESET included in the ra-searchspace set for a certain DL BWP may be set to the value of the identifier of the CORESET that identifies the configuration information of the common CORESET that is set for the DL BWP, or may be set to the value of the identifier of the common CORESET for the random access procedure that is set for another BWP. That is, the ra-searchspace set for a certain DL BWP may indicate the identifier of the CORESET that identifies the configuration information of the common CORESET that is set for the DL BWP, or may indicate the identifier of the common CORESET for the random access procedure that is set for another BWP. For example, the value of the identifier of the CORESET included in the ra-searchspace for the DL BWP#1 may be set to 1, 3, or 6. That is, if CORESET#1 is set for the initial DL BWP, CORESET#0 cannot be called as the ra-searchspace of the DL BWP. If CORESET#1 is not set for the initial DL BWP, CORESET#0 can be called as the ra-searchspace of the DL BWP.

[0173] As a third example, the identifier of a CORESET included in the ra-searchspace configured for a certain DL BWP may be set to the identifier value of all common CORESETs configured in the terminal device 1. That is, the ra-searchspace configured for a certain DL BWP may indicate the identifier of a CORESET that identifies the configuration information of all common CORESETs configured in the serving cell. For example, the identifier value of a CORESET included in the ra-searchspace for DL ​​BWP#1 may be set to 0, 1, 3, or 6.

[0174] It may be set to the value of the CORESET identifier that identifies the configuration information of the CORESET that is set for the DL BWP, or it may be set to the value of the CORESET identifier that is set for another BWP. That is, the ra-searchspace that is set for a DL BWP may indicate the identifier of the CORESET that identifies the configuration information of the CORESET that is set for the DL BWP, or it may indicate the identifier of the common CORESET that is set for another BWP. For example, the value of the CORESET identifier included in the ra-searchspace for DL ​​BWP#1 may be set to 0, 1, 3, or 6.

[0175] The random access procedure of this embodiment will be described. The random access procedure is classified into two procedures: contention based (CB) and non-contention based (non-CB) (also called CF: Contention Free). The contention based random access is also called CBRA, and the non-contention based random access is also called CFRA.

[0176] The random access procedure may include (i) transmitting a random access preamble (Message 1, Msg1) on the PRACH, (ii) receiving a Random Access Response (RAR) message (Message 2, Msg2) along with the PDCCH / PDSCH, and, if applicable, (iii) transmitting a Message 3 PUSCH (Msg3 PUSCH), and (iv) receiving a PDSCH for collision resolution.

[0177] The contention-based random access procedure is initiated by a PDCCH order, a MAC entity, a notification of beam failure from a lower layer, or an RRC or the like. When a beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1, if a certain condition is satisfied, the MAC entity of the terminal device 1 initiates a random access procedure. When a beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1, a procedure of determining whether a certain condition is satisfied 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 MAC entity includes a random access procedure initiated by a scheduling request procedure. The random access procedure for a beam failure recovery request may or may not be considered as a random access procedure initiated by the MAC entity. Since different procedures may be performed in the random access procedure for a beam failure recovery request and the random access procedure initiated by the scheduling request procedure, the random access procedure for a beam failure recovery request and the scheduling request procedure may be distinguished. The random access procedure for a beam failure recovery request and the scheduling request procedure may be a random access procedure initiated by a MAC entity. In an embodiment, the random access procedure initiated by the scheduling request procedure may be referred to as a random access procedure initiated by a MAC entity, and 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 initiation of a random access procedure upon receiving a beam failure notification from a lower layer may mean the initiation of a random access procedure for a beam failure recovery request.

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

[0179] The occurrence of uplink data transmittable to the terminal device 1 may include triggering of a buffer status report corresponding to the transmittable uplink data. The occurrence of uplink data transmittable to the terminal device 1 may include pending a scheduling request triggered based on the occurrence of the transmittable uplink data.

[0180] The occurrence of sidelink data available for transmission to the terminal device 1 may include triggering of a buffer status report corresponding to the transmittable sidelink data. The occurrence of sidelink data available for transmission to the terminal device 1 may include pending scheduling requests triggered based on the occurrence of the transmittable sidelink data.

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

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

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

[0184] However, when the random access preamble index indicated in message 0 is a predetermined value (for example, when all bits indicating the index are 0), the terminal device 1 may perform a contention-based random access procedure in which the terminal device 1 randomly selects one from a set of available preambles and transmits it.

[0185] However, the random access setting information may include information common within a cell, or may include dedicated information that differs for each terminal device 1.

[0186] However, some of the random access configuration information may be associated with all SS / PBCH blocks in the SS burst set, or some of the random access configuration information may be associated with all of the configured CSI-RS or CSI-RSs, or some of the random access configuration information may be associated with one downlink transmission beam (or beam index).

[0187] However, a portion of the random access configuration information may be associated with one SS / PBCH block in the SS burst set. However, a portion of the random access configuration information may be associated with one of the one or more configured CSI-RS. However, a portion of the random access configuration information may be associated with one downlink transmission beam (or beam index). However, the information associated with one SS / PBCH block, one CSI-RS, and / or one downlink transmission beam may include index information (which may be, for example, an SSB index, a beam index, or a QCL configuration index) for identifying the corresponding one SS / PBCH block, one CSI-RS, and / or one downlink transmission beam.

[0188] The PRACH opportunities are described below.

[0189] A set of one or more PRACH opportunities available for transmitting the random access preamble may be specified by an upper layer parameter prach-ConfigIndex provided by an upper layer (an upper layer signal). A set of one or more PRACH opportunities available for transmitting the random access preamble is specified according to a PRACH configuration (physical random access channel configuration) index given by prach-ConfigIndex and a predetermined table (also referred to as a random access channel configuration (PRACH config) table). However, the specified one or more PRACH opportunities may be a set of PRACH opportunities associated with one or more SS / PBCH blocks transmitted by the base station device 3.

[0190] However, the PRACH configuration index may be used to set the period (PRACH configuration period (Physical Random Access Channel configuration period: PRACH configuration period)) at which the set of PRACH opportunities shown in the random access configuration table is repeated over time, the subcarrier index, resource block index, subframe number, slot number, system frame number, symbol number, and / or the format of the preamble in which the random access preamble can be transmitted.

[0191] However, the number of SS / PBCH blocks mapped to each PRACH opportunity may be indicated by the higher layer parameter SSB-perRACH-Occasion provided by the higher layer. If SSB-perRACH-Occasion is a value smaller than 1, one SS / PBCH block is mapped to multiple consecutive PRACH opportunities.

[0192] However, the number of random access preambles mapped to each SS / PBCH block may be indicated by the higher layer parameter cb-preamblePerSSB provided by the higher layer. The number of random access preambles mapped to each SS / PBCH block on each PRACH opportunity may be calculated from SSB-perRACH-Occasion and cb-preamblePerSSB. The index of the random access preamble mapped to each SS / PBCH block on each PRACH opportunity may be determined from SB-perRACH-Occasion, cb-preamblePerSSB, and the SSB index.

[0193] For PRACH opportunities, the SSB index may be mapped according to the following rules: (1) First, the preamble index is mapped in ascending order in one PRACH opportunity. For example, if the number of preambles in a PRACH opportunity is 64 and the number of random access preambles mapped to each SS / PBCH block in each PRACH opportunity is 32, the SSB indexes mapped to a certain PRACH opportunity are n and n+1. (2) Second, the SSBs are mapped to multiple frequency-multiplexed PRACH opportunities in ascending order of frequency resource index. For example, if two PRACH opportunities are frequency-multiplexed and the SSB indices mapped to the PRACH opportunities with smaller frequency resource indexes are n and n+1, the SSB indices mapped to the PRACH opportunities with larger frequency resource indexes are n+2 and n+3. (3) Third, the SSB index is mapped to multiple PRACH opportunities time-multiplexed within a PRACH slot in ascending order of time resource index. For example, in addition to the example in (2) above, if two more PRACH opportunities are multiplexed in the PRACH slot in the time direction, the SSB indexes mapped to these PRACH opportunities are n+4, n+5, and n+6, n+7. (4) Fourth, the index is mapped to multiple PRACH slots in ascending order. For example, in addition to the example in (3) above, if a RACH opportunity exists in the next PRACH slot, the mapped SSB index will be n+8, n+9, .... However, in the above example, if n+x becomes larger than the maximum value of the SSB index, the value of the SSB index will return to 0.

[0194] Fig. 13 is a diagram showing an example of allocation of SSB indexes to PRACH opportunities according to an embodiment of the present invention. Fig. 13 shows an example in which there are two PRACH slots in a certain time interval, and one PRACH slot has two PRACH opportunities (RO) in the time direction and two PRACH opportunities (RO) in the frequency direction, and SSB indices range from 0 to 11. Two SSB indices are mapped to one PRACH opportunity, and the SSB indices are mapped according to the above rules (1) to (4), and are mapped again from SSB index 0 from the seventh PRACH opportunity.

[0195] Although an SSB index is mapped to each PRACH opportunity, if the SSB index is not mapped to all SSB indexes (all SS / PBCH blocks transmitted by the base station device 3) even when all PRACH opportunities in the PRACH configuration period specified by prach-ConfigIndex are used, the SSB index may be mapped over multiple PRACH configuration periods. However, the number of all SS / PBCH blocks transmitted by the base station device 3 may be indicated by a higher layer parameter. A period in which the PRACH configuration period is repeated a predetermined number of times so that all SSB indexes are mapped at least once is called an association period. The number of PRACH configuration periods constituting the association period may be a minimum value that satisfies the above condition from a set of multiple predetermined values. The set of multiple predetermined values ​​may be determined for each PRACH configuration period. However, if the number of remaining PRACH opportunities is greater than the number of SS / PBCH blocks after all SSB indexes are mapped to the PRACH opportunities in the association period, the SSB index may be mapped again. However, when all SSB indices are mapped to the PRACH opportunities in an association period and the number of remaining PRACH opportunities is less than the number of SS / PBCH blocks, the SSB index may not be mapped to the remaining PRACH opportunities. A cycle in which a PRACH opportunity is assigned once for each SSB index is referred to as an SSB index allocation cycle. When SSB-perRACH-Occasion is 1 or more, each SSB index is mapped to one PRACH opportunity in one SSB index allocation cycle. When SSB-perRACH-Occasion is a value smaller than 1, each SSB index is mapped to 1 / SSB-perRACH-Occasion PRACH opportunities in one SSB index allocation cycle. The terminal device 1 may specify the association period based on the PRACH configuration period indicated by the PRACH configuration index and the number of SS / PBCH blocks specified by upper layer parameters provided by the upper layer (upper layer signal).

[0196] Each of one or more random access preamble groups included in the random access setting information may be associated with each reference signal (e.g., SS / PBCH block, CSI-RS, or downlink transmission beam). The terminal device 1 may select a random access preamble group based on a received reference signal (e.g., SS / PBCH block, CSI-RS, or downlink transmission beam).

[0197] However, the random access preamble group associated with each SS / PBCH block may be specified by one or more parameters signaled at higher layers. One of the one or more parameters may be an index (e.g., a start index) of one of the available preambles. One of the one or more parameters may be the number of preambles available for contention-based random access per SS / PBCH block. One of the one or more parameters may be the sum of the number of preambles available for contention-based random access and the number of preambles available for non-contention-based random access per SS / PBCH block. One of the one or more parameters may be the number of SS / PBCH blocks associated with one PRACH opportunity.

[0198] However, the terminal device 1 may receive one or more downlink signals each transmitted using one downlink transmission beam, receive random access setting information associated with one of the downlink signals, and perform a random access procedure based on the received random access setting information. The terminal device 1 may receive one or more SS / PBCH blocks in an SS burst set, receive random access setting information associated with one of the SS / PBCH blocks, and perform a random access procedure based on the received random access setting information. The terminal device 1 may receive one or more CSI-RSs, receive random access setting information associated with one of the CSI-RSs, and perform a random access procedure based on the received random access setting information.

[0199] The one or more pieces of random access configuration information may consist of one random access channel configuration (RACH-Config) and / or one physical random access channel configuration (PRACH-Config).

[0200] The random access channel configuration may include parameters related to random access for each reference signal.

[0201] The physical random access channel configuration may include parameters related to the physical random access channel for each reference signal (such as a PRACH configuration index and a PRACH opportunity).

[0202] One piece of random access setting information may indicate a parameter related to random access corresponding to one reference signal, and multiple pieces of random access setting information may indicate a plurality of parameters related to random access corresponding to a plurality of reference signals.

[0203] One piece of random access setting information indicates parameters related to physical random access corresponding to one reference signal, and may indicate parameters related to multiple random accesses corresponding to multiple reference signals.

[0204] When a corresponding reference signal is selected, random access setting information corresponding to the reference signal (random access channel setting corresponding to the reference signal, physical random access channel setting corresponding to the reference signal) may be selected.

[0205] However, the terminal device 1 may receive one or more pieces of random access setting information from a base station device 3 and / or a transmission / reception point 4 different from the base station device 3 and / or a transmission / reception point 4 that transmits the random access preamble. For example, the terminal device 1 may transmit a random access preamble to the second base station device 3 based on at least one piece of random access setting information received from the first base station device 3.

[0206] However, the base station device 3 may receive a random access preamble transmitted by the terminal device 1 and determine a downlink transmission beam to be applied when transmitting a downlink signal to the terminal device 1. The terminal device 1 may transmit the random access preamble using a PRACH opportunity indicated in random access setting information associated with a certain downlink transmission beam. The base station device 3 may determine a downlink transmission beam to be applied when transmitting a downlink signal to the terminal device 1 based on the random access preamble received from the terminal device 1 and / or the PRACH opportunity at which the random access preamble was received.

[0207] The base station device 3 transmits RRC parameters including one or more pieces of random access setting information (which may include random access resources) to the terminal device 1 as an RRC message.

[0208] The terminal device 1 may select one or more available random access preambles and / or one or more available PRACH 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 available 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.

[0209] In this embodiment, uplink resource allocation type 0 and uplink resource allocation type 1 are supported for uplink resource allocation. In uplink resource allocation type 0, the resource block assignment information includes a bitmap indicating resource block groups (RBGs, Resource Block Groups) allocated to the terminal device 1. A resource block group is a set of contiguous virtual resource blocks and may be defined by higher layer parameters.

[0210] The following describes uplink resource allocation type 1.

[0211] The resource block assignment information is a size N size BWP Denotes a set of non-interleaved virtual resource blocks contiguously allocated in the active BWPs of size N size BWPis the number of resource blocks indicating the bandwidth of the active UL BWP. If DCI format 0_0 is detected in the type 0-PDCCH common search space set in CORESET#0, size N size BWP indicates the bandwidth of the initial UL BWP.

[0212] The uplink type 1 resource assignment field is the starting resource block (RB start、 Starting virtual resource block) and the number of contiguously allocated resource blocks (L RBs ) and a resource indication value (RIV) corresponding to the resource assignment field. That is, the resource indication value RIV is indicated in the resource assignment field. RB start L indicates the start position of the allocated resource block. RBs indicates the number (length, size) of resource blocks of the allocated resources. The resource indication value RIV indicates resources to be allocated for the corresponding UL BWP. The target UL BWP may be a UL BWP to which a resource assignment (resource assignment field) is applied. The terminal device 1 first determines the UL BWP to which the resource assignment is applied, and then determines the resource allocation within the determined UL BWP. In other words, the value of RIV is determined based on the size (N size BWP ), starting resource block (RB start ), and the number of contiguously allocated resource blocks (L RBs In other words, the terminal device 1 calculates the RIV value and N size BWPBased on the bit string in the resource assignment field, the base station apparatus 3 calculates the starting position of the resource blocks allocated in the UL BWP and the number of resource blocks to be consecutively allocated. That is, the terminal apparatus 1 interprets the bits in the resource assignment field for the UL BWP to which the resource assignment is applied. The base station apparatus 3 determines the resource allocation in the UL BWP to be applied to the terminal apparatus 1, generates an RIV based on the size of the UL BWP to be applied, and transmits a resource assignment including a bit string indicating the RIV to the terminal apparatus 1. The terminal apparatus 1 specifies the resource block allocation in the frequency direction (of the PUSCH) of the UL BWP to be applied based on the bit string in the resource assignment field.

[0213] FIG. 12 is a diagram showing an example of calculating the RIV.

[0214] In FIG. 12(A), N size BWP is the number of resource blocks that indicate the bandwidth of the active UL BWP. The value of RIV is the number of resource blocks that indicate the bandwidth of the initial BWP, N size BWP , the start position of the resource block RB start , and the number of consecutively allocated resource blocks L RBs Calculated based on RB start L is the starting position of the resource block for an active UL BWP. RBs is the number of contiguous resource blocks allocated to an active BWP. Thus, the allocated resources for an active BWP are determined by the resource block start position RB start , and the number of consecutively allocated resource blocks L RBs If the DCI format is detected in a common search space set (e.g., a type 1 PDCCH common search space set), N in FIG. size BWP The number of resource blocks indicating the bandwidth of the initial UL BWP is used for the

[0215] In FIG. 12(B), N nitial BWP is the number of resource blocks that indicates the bandwidth of the initial BWP (UL BWP). N active BWP is the number of resource blocks that indicate the bandwidth of the active BWP (UL BWP). The value of RIV is the number of resource blocks that indicate the bandwidth of the initial BWP, N nitial BWP , the start position of the resource block RB' start , and the number of consecutively allocated resource blocks L' RBs RB' is calculated based on the start L' is the start position of the resource block for the initial BWP. RBs RB' is the number of contiguous resource blocks allocated for the initial BWP. start and the coefficient K multiplied by RB start The multiplication of L'RBs and the coefficient K is L RBs The value of the coefficient K is calculated based on the bandwidth of the initial BWP and the bandwidth of the active BWP. N active BWP N nitial BWP If the value of K is greater than or equal to Floor(N active BWP / N nitial BWP ) where the function Floor(A) outputs the largest integer that is not greater than A. active BWP N nitial BWP The value of K is 1 if the allocated resources for an active BWP are equal to or smaller than the starting position of the resource block RB start , and the number of consecutively allocated resource blocks L RBs It is identified by:

[0216] The resource identification method of Fig. 12(B) may be used in cases where the size of the DCI format (or the size of the frequency domain resource assignment field included in the DCI format) in the USS is derived by an initial BWP and applied to an active BWP. The DCI format may be DCI format 0_0 and / or DCI format 0_1.

[0217] FIG. 11 is a diagram illustrating an example of uplink resource allocation type 1 for BWP.

[0218] In FIG. 11, one initial UL BWP (1101) and two additional UL BWPs (1102 and 1103) are configured for the terminal device 1. As described above, the common resource block n PRB are resource blocks numbered in ascending order from 0 in each subcarrier spacing setting μ from point A. That is, 1114 is a common resource block numbered 0. In the subcarrier spacing setting μ, common resource block 0 (common resource block index 0, n CRB The center of subcarrier index 0 of point #0) coincides with point A. 1104 is the start position of the carrier in subcarrier spacing setting μ, and is given by the higher layer parameter OffsetToCarrier. That is, the higher layer parameter OffsetToCarrier is the offset in the frequency domain between point A and the lowest available subcarrier of the carrier. The offset (1115) indicates the number of resource blocks in subcarrier spacing setting μ. That is, when the subcarrier spacing setting μ is different, the frequency domain band of the offset is different. In the subcarrier spacing setting μ, 1104 may be the position of the resource block where the carrier starts. The physical resource blocks are resource blocks numbered in ascending order from 0 for each BWP. In the subcarrier spacing setting μ of each BWP index i, the physical resource block n in that BWP index i is PRB and common resource block nCRB The relationship is (Equation 3)n CRB =n PRB +N start BWP、i For each BWP subcarrier spacing setting μ, N start BWP、i is the number of common resource blocks where BWP index i starts relative to common resource block index 0. N size BWP、i is the number of resource blocks that indicates the bandwidth of the BWP of index i in the subcarrier spacing setting μ of BWP index i.

[0219] The frequency domain location and bandwidth of the BWP are given by the higher layer parameter locationAndBandwidth. Specifically, the first physical resource block (physical resource block index 0) of BWP index i and the number of consecutive physical resource blocks are given by the higher layer parameter locationAndBandwidth. The value indicated in the higher layer parameter locationAndBandwidth is interpreted as the value of RIV for the carrier. As shown in Figure 12(A), size BWP is set to 275. Then, the RB identified by the value of RIV start and L RBs indicates the first physical resource block of the BWP (physical resource block index 0) and the number of consecutive physical resource blocks that indicate the bandwidth of the BWP. The first physical resource block of BWP index i is the physical resource block offset relative to the physical resource block (1104) indicated by the higher layer parameter OffsetToCarrier. The number of resource blocks that indicate the bandwidth of BWP index i is N size BWP、i The N start BWP、i is given from the first physical resource block of BWP index i and the offset indicated by the higher layer parameter OffsetToCarrier.

[0220] That is, in FIG. 11, in the subcarrier spacing setting μ of UL BWP#0, 1105 is the physical resource block index 0 (n PRB The relationship between the physical resource blocks and the common resource blocks in UL BWP#0 is n CRB =n PRB +N start BWP、0 In the subcarrier spacing setting μ of UL BWP#0, N start BWP、0 (1107) is the common resource block where UL BWP#0 for common resource block index 0 starts. size BWP、0 (1106) is the number of resource blocks indicating the bandwidth of UL BWP#0 in the subcarrier spacing setting μ of UL BWP#0.

[0221] In FIG. 11, in the subcarrier spacing setting μ of UL BWP#1, 1108 is the physical resource block index 0 (n PRB The relationship between the physical resource blocks and the common resource blocks in UL BWP#1 is n CRB =n PRB +N start BWP、1 In the subcarrier spacing setting μ of UL BWP#1, N start BWP、1 (1110) is the common resource block where UL BWP#1 for common resource block index 0 starts. size BWP、1 (1109) is the number of resource blocks indicating the bandwidth of UL BWP#0 in the subcarrier spacing setting μ of UL BWP#1.

[0222] In FIG. 11, in the subcarrier spacing setting μ of UL BWP#2, 1111 is the physical resource block index 0 (n PRBThe relationship between the physical resource blocks and the common resource blocks in UL BWP#2 is n CRB =n PRB +N start BWP、2 In the subcarrier spacing setting μ of UL BWP#2, N start BWP、2 (1113) is the common resource block where UL BWP#2 starts for common resource block index 0. size BWP、2 (1112) is the number of resource blocks indicating the bandwidth of UL BWP#2 in the subcarrier spacing setting μ of UL BWP#2.

[0223] As can be seen from FIG. 11, for each BWP set in the terminal device 1, the starting position (starting common resource block, N start BWP ) and the number of resource blocks (N size BWP ) are different. When interpreting the RIV indicated by the bits of the resource assignment field, the terminal device 1 needs to determine the UL BWP to which the resource assignment is applied. That is, the terminal device 1 determines the UL BWP to which the resource assignment is applied, and size BWP、i Based on this, the RIV is interpreted and the starting resource block (RB start ), and the number of contiguously allocated resource blocks (L RBs ) can be calculated. start indicates the position where the allocated resources start based on the physical resource block index 0 of the UL BWP to which the resource assignment applies. For example, the RB start Even if the value of is the same, the starting position of the common resource block is different when the resource assignment is applied to different UL BWPs.

[0224] In addition, the size of the UL BWP to which the resource allocation applies is N size BWPIf N is different, the number of bits in the resource assignment field that can indicate the RIV value is different. The number of bits in the resource block assignment field that can indicate the RIV value is Ceiling(log2(N size BWP (N size BWP +1) / 2)).

[0225] FIG. 8 is a diagram showing an example of a random access procedure of the terminal device 1 in this embodiment.

[0226] <Message 1 (S801)> In S801, the terminal device 1 transmits a random access preamble to the base station device 3 via PRACH. This transmitted random access preamble may be referred to as message 1 (Msg1). The transmission of the random access preamble is also referred to as PRACH transmission. The random access preamble is configured to notify information to the base station device 3 by using one sequence among a plurality of sequences. For example, 64 types of sequences (random access preamble index numbers are from 1 to 64) are prepared. When 64 types of sequences are prepared, 6-bit information (which may be ra-PreambleIndex or preamble index) can be indicated to the base station device 3. This information may be indicated as a random access preamble identifier (RAPID, Random Access preamble Identifier).

[0227] In the case of a contention-based random access procedure, the terminal device 1 itself randomly selects an index of a random access preamble. In the contention-based random access procedure, the terminal device 1 selects an SS / PBCH block having an RSRP of the SS / PBCH block exceeding a set threshold, and selects a preamble group. When a relationship between the SS / PBCH block and the random access preamble is set, the terminal device 1 randomly selects ra-PreambleIndex from one or more random access preambles associated with the selected SS / PBCH block and the selected preamble group, and sets the selected ra-PreambleIndex to the preamble index (PREAMBLE_INDEX). In addition, for example, the selected SS / PBCH block and the selected preamble group may be divided into two subgroups based on the transmission size of the message 3. The terminal device 1 may randomly select a preamble index from a subgroup corresponding to a small transmission size of the message 3 when the transmission size of the message 3 is small, and may randomly select a preamble index from a subgroup corresponding to a large transmission size of the message 3 when the transmission size of the message 3 is large. An index for a small message size is typically selected when the propagation path characteristics are poor (or the distance between the terminal device 1 and the base station device 3 is long), and an index for a large message size is selected when the propagation path characteristics are good (or the distance between the terminal device 1 and the base station device 3 is short).

[0228] In the case of a non-contention based random access procedure, the index of the random access preamble is selected based on information received by the terminal device 1 from the base station device 3. Here, the information received by the terminal device 1 from the base station device 3 may be included in the PDCCH. When the bit values ​​of the information received from the base station device 3 are all 0, the contention based random access procedure is executed by the terminal device 1, and the index of the random access preamble is selected by the terminal device 1 itself.

[0229] <Message 2 (S802)> Next, in S802, the base station device 3 that has received the message 1 generates an RAR message including an uplink grant (RAR UL grant, Random Access Response Grant, RAR UL grant) for instructing the terminal device 1 to transmit, and transmits a random access response including the generated RAR message to the terminal device 1 on DL-SCH. That is, the base station device 3 transmits a random access response including an RAR message corresponding to the random access preamble transmitted in S801 on a PDSCH in the primary cell. The PDSCH corresponds to a PDCCH including an RA-RNTI. The RA-RNTI is calculated by RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id. Here, s_id is the index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13. t_id is the index of the first slot of the PRACH in the system frame, and takes a value from 0 to 79. f_id is the index of the PRACH in the frequency domain and takes a value from 0 to 7. ul_carrier_id is the uplink carrier used for Msg1 transmission. The ul_carrier_id for the NUL carrier is 0 and the ul_carrier_id for the SUL carrier is 1.

[0230] The random access response may be referred to as a message 2 or Msg2. The base station device 3 includes in the message 2 a random access preamble identifier corresponding to the received random access preamble and an RAR message (MAC RAR) corresponding to the identifier. The base station device 3 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 RAR message transmission timing adjustment information (TA command, Timing Advance Command) for adjusting the shift. The RAR message includes at least a random access response grant field mapped to an uplink grant, a Temporary C-RNTI field to which a Temporary C-RNTI (Cell Radio Network Temporary Identifier) ​​is mapped, and a TA command (Timing Advance Command). The terminal device 1 adjusts the timing of PUSCH transmission based on the TA command. The timing of PUSCH transmission may be adjusted for each group of cells. The base station device 3 includes in the message 2 a random access preamble identifier corresponding to the received random access preamble.

[0231] To respond to the PRACH transmission, the terminal device 1 detects (monitors) DCI format 1_0 with CRC parity bits added and scrambled by the corresponding RA-RNTI during the random access response window. The period (window size) of the random access response window is given by the upper layer parameter ra-ResponseWindow. The window size is the number of slots based on the subcarrier spacing of the Type1-PDCCH common search space.

[0232] If the terminal device 1 detects a PDSCH including DCI format 1_0 and one DL-SCH transport block with a CRC scrambled by the RA-RNTI added within the window period, the terminal device 1 passes the transport block to the upper layer. The upper layer analyzes the transport block for a random access preamble identifier (RAPID) associated with the PRACH transmission. If the upper layer identifies the RAPID included in the RAR message of the DL-SCH transport block, the upper layer indicates an uplink grant to the physical layer. Identification means that the RAPID included in the received random access response is the same as the RAPID corresponding to the transmitted random access preamble. The uplink grant is called a random access response uplink grant (RAR UL grant) in the physical layer. That is, the terminal device 1 can identify the RAR message (MAC RAR) addressed to the terminal device 1 from the base station device 3 by monitoring the random access response (message 2) corresponding to the random access preamble identifier.

[0233] (i) if the terminal device 1 does not detect DCI format 1_0 with a CRC scrambled by the RA-RNTI within the window period, or (ii) if the terminal device 1 does not correctly receive a DL-SCH transport block in the PDSCH within the window period, or (iii) if the upper layer does not identify a RAPID associated with the PRACH transmission, the upper layer instructs the physical layer to transmit a PRACH.

[0234] If the received random access response includes a random access preamble identifier corresponding to the transmitted random access preamble and the terminal device 1 selects the random access preamble based on the information received from the base station device 3, the terminal device 1 considers that the non-contention based random access procedure has been successfully completed and transmits a PUSCH based on the uplink grant included in the random access response. If the received random access response includes a random access preamble identifier corresponding to the transmitted random access preamble and the terminal device 1 itself selects the random access preamble, the terminal device 1 sets the TC-RNTI to the value of the TC-RNTI field included in the received random access response and transmits a random access message 3 on the PUSCH based on the uplink grant included in the random access response. The PUSCH corresponding to the uplink grant included in the random access response is transmitted in the serving cell in which the corresponding preamble was transmitted on the PRACH.

[0235] The RAR UL grant (RAR uplink grant) is used for scheduling PUSCH transmission (Msg3 PUSCH). The terminal device 1 transmits a message 3 based on the RAR UL grant. Fig. 9 is a diagram showing an example of a field included in the RAR UL grant.

[0236] 9, when the value of the frequency hopping flag is 0, the terminal device 1 transmits the Msg3 PUSCH without frequency hopping. When the value of the frequency hopping flag is 1, the terminal device 1 transmits the Msg3 PUSCH with frequency hopping.

[0237] The 'Msg3 PUSCH time resource allocation' field is used to indicate the time domain resource allocation for the Msg3 PUSCH. The 'MCS' field is used to determine the MCS index for the Msg3 PUSCH. The 'TPC command for Msg3 PUSCH' field is used for setting the transmission power of Msg3 PUSCH. In a contention-based random access procedure, the 'CSI request' field is reserved. In a non-contention-based random access procedure, the 'CSI request' field is used to determine whether an aperiodic CSI report is included in the PUSCH transmission.

[0238] The interpretation of the 'Msg3 PUSCH frequency resource allocation' field will be described below. This field is used for resource allocation for PUSCH transmission of message 3. The 'Msg3 PUSCH frequency resource allocation' field may be referred to as a fixed size resource block assignment. That is, the Msg3 PUSCH frequency resource assignment has a fixed number of bits, regardless of the bandwidth of the UL BWP configured for the terminal device 1. The terminal device 1 receives the number of resource blocks (N size BWP ) based on the Msg3 PUSCH frequency resource assignment. The terminal device 1 then truncates or inserts bits into the Msg3 PUSCH frequency resource assignment, thereby adapting the resource assignment to the bandwidth of the UL BWP to which it is applied. size BWPis the number of resource blocks indicating the bandwidth of the UL BWP to which the resource assignment is applied. In S802 below, the UL BWP to which the resource assignment is applied is the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied.

[0239] FIG. 10 is a diagram showing an example of interpretation of the 'Msg3 PUSCH frequency resource allocation' field according to this embodiment.

[0240] In FIG. 10A, 1001 is a 'Msg3 PUSCH frequency resource allocation' field having a fixed 14 bits. 1002 is N UL,hop Hopping bits. 1003 is hopping bits from 1001 to N UL,hop The bits remaining after removing the hopping bits are (14-N UL,hop ) bits. That is, the 14-bit 1001 is composed of 1002 and 1003. UL,hop The number of hopping bits is determined by the value indicated in the 'Frequency hopping flag' field and / or N size BWP For example, N UL,hop The number of bits in the example is N size BWP may be 1 bit if the size of N is smaller than a predetermined number of resource blocks. UL,hop The number of bits in the example is N size BWP may be 2 bits, where the size of N is equal to or greater than the value of the predetermined number of resource blocks. The value of the predetermined number of resource blocks may be 50. size BWP The explanation will be given later.

[0241] As mentioned above, if the value of the Frequency hopping flag is 0, N UL,hopThe hopping bit is 0 bit. In this case, 1003 is 1001, which has 14 bits. If the value of the Frequency hopping flag is 1, N UL,hop The number of hopping bits is N size BWP may be given one or two bits depending on whether the value of N exceeds a predetermined resource block number value Y. For example, size BWP If is less than a given number of resource blocks Y, then N UL,hop The hopping bit may be given as 1 bit. N size BWP If is equal to or greater than a given value Y of the number of resource blocks, then N UL,hop The hopping bit may be given as 2 bits, i.e. 1003 has 12 bits or 13 bits.

[0242] Figure 10(B) shows N size BWP 13 shows an example of truncating bits of the 'Msg3 PUSCH frequency resource allocation' field when Msg3 PUSCH frequency is less than or equal to a predetermined value X of the number of resource blocks.

[0243] In FIG. 10B, the terminal device 1 is size BWP When N is smaller than or equal to the value X of a predetermined number of resource blocks, the bits of the Msg3 PUSCH frequency resource assignment are truncated by b bits from the least significant bit (LSB). That is, b bits is the number of bits to be truncated. The value of b is expressed as (Equation 1): b = Ceiling(log2(N size BWP (N size BWP+1) / 2)), where the function Ceiling(A) outputs the smallest integer not less than A. The truncated Msg3 PUSCH frequency resource assignment may be referred to as a truncated resource block assignment. The terminal device 1 may interpret the truncated resource block assignment according to the rules for normal DCI format 0_0.

[0244] In FIG. 10B, 1004 is an Msg3 PUSCH frequency resource assignment having 14 bits. 1005 is an N UL,hop 1006 is the hopping bit. N UL,hop Bits other than the hopping bits. 1008 is the resource block assignment to be truncated. The number of bits of 1008 is b bits. The number of bits of 1007 is 14-b.

[0245] Figure 10(C) shows N size BWP 13 illustrates an example of inserting bits in the 'Msg3 PUSCH frequency resource allocation' field when the bandwidth of the PUSCH frequency resource allocation field is greater than a predetermined value X of resource blocks.

[0246] In FIG. 10C, 1009 is an Msg3 PUSCH frequency resource assignment having 14 bits. 1010 is N UL,hop 1012 is the hopping bit from Msg3 PUSCH frequency resource assignment UL,hop These are the bits remaining after removing the hopping bits. The number of bits in 1012 is (14-N UL,hop ) bits. The terminal device 1 has N size BWP is greater than the value X of the predetermined number of resource blocks, N UL,hopAfter the hopping bit, b most significant bits (MSB) are inserted, which are set to a value of '0'. That is, b bits is the number of bits to be inserted. The value of b is calculated using the formula (2) b = (Ceiling(log2(N size BWP (N size BWP +1) / 2))−Z). The value of Z may be 14. The Msg3 PUSCH frequency resource assignment into which b bits are inserted may be referred to as an extended resource block assignment. The terminal device 1 may interpret the extended resource block assignment according to the rules for normal DCI format 0_0. In FIG. 10(C), the number of bits of 1011 is b bits. 1009 is the extended resource block assignment. The number of bits of 1009 is the sum of 14 bits of the Msg3 PUSCH frequency resource assignment and b bits.

[0247] As described above, one initial BWP including at least one DL BWP and one UL BWP is configured for the terminal device 1. Furthermore, up to four additional BWPs are configured for the terminal device 1. Then, the size (N size BWP ) may vary. UL BWP size N size BWP is the number of resource blocks indicating the bandwidth of the corresponding UL BWP. When identifying a resource allocation, the terminal device 1 first determines the UL BWP to which the resource assignment is applied, and then determines the resource allocation within the determined UL BWP.

[0248] When truncating or inserting bits for the Msg3 PUSCH frequency resource assignment, the terminal device 1 determines the UL BWP to which the resource assignment is applied. That is, the terminal device 1 determines Nsize BWP Based on the UL BWP to which the resource allocation applies.

[0249] In the following, in this embodiment, N indicates the bandwidth of the UL BWP to which the resource assignment is applied (the UL BWP to be interpreted). size BWP The method of determining N in the random access procedure will be described. size BWP Determine the determined N size BWP The RIV is generated using the above, a bit string to be included in the frequency resource assignment field is determined, and the PUSCH frequency resource assignment is transmitted to the terminal device 1.

[0250] As described above, the terminal device 1 monitors the DCI format to which the CRC scrambled by the RA-RNTI or TC-RNTI is added in the search space for the random access procedure (type 1 PDCCH common search space set). The terminal device 1 receives a random access response by monitoring the DCI format to which the CRC scrambled by the RA-RNTI is added in this search space set. The terminal device 1 is indicated with the configuration information of the CORESET for the type 1 PDCCH common search space set.

[0251] In one aspect of the present embodiment, in the contention-based random access procedure, the terminal device 1 may determine, as the UL BWP to which the resource assignment is applied, a UL BWP having the same BWP identifier as a DL BWP in which the configuration information of CORESET associated with the search space for the random access procedure (type 1 PDCCH common search space set) is set. That is, in the contention-based random access procedure, size BWPis the number of resource blocks indicating the bandwidth of a UL BWP having the same BWP identifier as a DL BWP in which the configuration information of CORESET associated with the type 1 PDCCH common search space set is set. size BWP The terminal device 1 uses the determined N to truncate or insert bits in the Msg3 PUSCH frequency resource assignment. The bits of the truncated or extended resource block assignment indicate the value of RIV. size BWP N in Figure 12(A) size BWP Using RB start and L RBs The RB calculated from the RIV value can be calculated. start indicates the starting position of the allocated resources relative to physical resource block index 0 of the UL BWP to which the resource assignment applies. In other words, the numbering of the resource assignments indicated in the RAR UL grant starts in ascending order from physical resource block index 0 corresponding to the UL BWP to which the resource assignment applies (the lowest physical resource block number of the UL BWP to which the resource assignment applies).

[0252] In one aspect of this embodiment, in a contention-based random access procedure, the terminal device 1 determines either the initial UL BWP or the active UL BWP as the UL BWP to which resource assignment is applied, based on whether the DL BWP in which the configuration information of CORESET associated with the type 1 PDCCH common search space set is set is the initial DL BWP. For example, when the DL BWP in which the configuration information of CORESET associated with the type 1 PDCCH common search space set is set is the initial DL BWP, the terminal device 1 may determine the initial ULBWP as the UL BWP to which resource assignment is applied. Also, when the DL BWP in which the configuration information of CORESET associated with the type 1 PDCCH common search space set is set is not the initial DL BWP, the terminal device 1 may determine the active UL BWP as the UL BWP to which resource assignment is applied. Then, N size BWP is the number of resource blocks indicating the bandwidth of the UL BWP. Then, the terminal device 1 determines N size BWP is used to truncate or insert bits into the Msg3 PUSCH frequency resource assignment.

[0253] Also, in one aspect of this embodiment, in the contention based random access procedure, the terminal device 1 determines either the initial UL BWP or the active UL BWP as the UL BWP to which the resource assignment is applied, based on whether the CORESET associated with the type 1 PDCCH common search space set is a common CORESET. For example, when the CORESET associated with the type 1 PDCCH common search space set is a common CORESET, the terminal device 1 may determine the initial UL BWP as the UL BWP to which the resource assignment is applied. Also, when the CORESET associated with the type 1 PDCCH common search space set is not a common CORESET, the terminal device 1 may determine the active UL BWP as the UL BWP to which the resource assignment is applied. Then, N size BWP is the number of resource blocks indicating the bandwidth of the UL BWP to which the resource assignment is applied. size BWP is used to truncate or insert bits into the Msg3 PUSCH frequency resource assignment.

[0254] Also, as an extension of the above aspect, in the contention-based random access procedure, the terminal device 1 determines either the initial UL BWP or the active UL BWP as the UL BWP to which the resource assignment is applied, based on whether the CORESET associated with the type 1 PDCCH common search space set is CORESET#0. For example, when the CORESET associated with the type 1 PDCCH common search space set is CORESET#0, the terminal device 1 may determine the initial UL BWP as the UL BWP to which the resource assignment is applied. Also, when the CORESET associated with the type 1 PDCCH common search space set is not CORESET#0, the terminal device 1 may determine the active UL BWP as the UL BWP to which the resource assignment is applied. Also, when the CORESET associated with the type 1 PDCCH common search space set is an additional common CORESET, the terminal device 1 may determine the UL BWP having the same BWP identifier as the DL BWP to which the additional common CORESET is set as the UL BWP to which the resource assignment is applied. That is, when an additional common CORESET is set for an initial DL BWP, the terminal device 1 may determine the initial UL BWP as the UL BWP to which the resource assignment is applied. When an additional common CORESET is set for an additional DL BWP, the terminal device 1 may determine a UL BWP having the same BWP identifier as the additional DL BWP as the UL BWP to which the resource assignment is applied.

[0255] Also, as one aspect of the present embodiment, in the contention based random access procedure, the terminal device 1 may always determine the initial UL BWP as the UL BWP to which resource assignment is applied. size BWP is the number of resource blocks indicating the bandwidth of the initial UL BWP. size BWPThe terminal device 1 uses the determined N to truncate or insert bits in the Msg3 PUSCH frequency resource assignment. The bits of the truncated or extended resource block assignment indicate the value of RIV. size BWP N in Figure 12(A) size BWP The RIV is generated by using the RB start and L RBs The terminal device 1 receives the RB from the RIV. start and L RBs Get RB start indicates the starting position of the assigned resources relative to the physical resource block index 0 corresponding to the initial UL BWP. In other words, the numbering of the resource allocations indicated from the RAR UL grant starts from the physical resource block index 0 corresponding to the initial UL BWP (the lowest physical resource block number of the UL BWP to which the resource assignment applies).

[0256] In addition, as one aspect of the present embodiment, in a non-contention based random access procedure, the terminal device 1 may determine a UL BWP that is always active as a UL BWP to which resource assignment is applied. size BWP is the number of resource blocks indicating the bandwidth of the active UL BWP. size BWP The terminal device 1 uses the determined N to truncate or insert bits in the Msg3 PUSCH frequency resource assignment. The bits of the truncated or extended resource block assignment indicate the value of RIV. size BWP N in Figure 12(A) size BWP The RIV is generated by using the RB start and L RBsThe terminal device 1 receives the RB from the RIV. start and L RBs Get RB start indicates the starting position of the assigned resources relative to the physical resource block index 0 corresponding to the active UL BWP. In other words, the numbering of the resource allocations indicated from the RAR UL grant starts from the physical resource block index 0 corresponding to the active UL BWP (the lowest physical resource block number of the UL BWP to which the resource assignment applies).

[0257] From the above example, in the contention-based random access procedure, when DCI format 1_0 for scheduling a PDSCH (DL-SCH transport block) including a RAR UL grant indicating resource block assignment information is detected in a common search space (e.g., type 1 PDCCH common search space) in CORESET#0 (or an additional common CORESET configured for the initial DL BWP), the N size BWP Here, DCI format 1_0 is DCI format 1_0 with CRC parity bits scrambled by the corresponding RA-RNTI added.

[0258] In the above aspect, in the non-contention based random access procedure, the terminal device 1 determines the active UL BWP as the UL BWP to which the resource assignment is applied, regardless of whether the CORESET associated with the type 1 PDCCH common search space set is a common CORESET. Also, in the non-contention based random access procedure, the terminal device 1 determines the active UL BWP as the UL BWP to which the resource assignment is applied, regardless of whether the DL BWP in which the configuration information of the CORESET associated with the type 1 PDCCH common search space set is set is an initial DL BWP.

[0259] That is, the terminal device 1 determines whether the random access procedure is a contention-based random access procedure or a non-contention-based random access procedure, and determines whether the initial UL BWP or the active UL BWP is the UL BWP to which the resource assignment is applied (N size BWP For example, when the random access procedure is a contention-based random access procedure, the terminal device 1 may determine the initial UL BWP as the UL BWP to which the resource assignment is applied. Then, N size BWP is the number of resource blocks indicating the bandwidth of the initial UL BWP. In addition, when the random access procedure is a non-contention based random access procedure, the terminal device 1 may determine the active UL BWP as the UL BWP to which the resource assignment is applied. And, N size BWP is the number of resource blocks indicating the bandwidth of the active UL BWP.

[0260] N UL,hop The number of hopping bits is determined by the size of the UL BWP to which the resource assignment applies (N size BWP ) exceeds a predetermined value Y of the number of resource blocks. size BWP N indicates the bandwidth of the UL BWP to which the resource allocation determined in the above manner is applied. size BWP That is, N size BWP If is less than a given number of resource blocks Y, then N UL,hop The hopping bit may be set to 1 bit. The frequency offset of the second hop for the PUSCH transmission of message 3 is Floor(N size BWP / 2) or Floor(N size BWP / 4). N size BWPIf is equal to or greater than a given value Y of the number of resource blocks, then N UL,hop The hopping bits may be given as 2 bits. The frequency offset of the second hop for the PUSCH transmission of message 3 is Floor(N size BWP / 2), Floor(N size BWP / 4), or -Floor(N size BWP / 4).

[0261] As described above, the resource block numbering (RB Indexing) of the resource allocation (uplink type 0 and / or type 1 resource allocation) is determined in the UL BWP to which the resource assignment indicating the resource allocation is applied. Specifically, when the BWP indication field (bandwidth part indicator field) is not set in the DCI format, the RB numbering of the resource allocation is determined in the active BWP of the terminal device 1. However, even when the BWP indication field (bandwidth part indicator field) is not set in the DCI format, the RB numbering of the resource allocation is determined in the initial UL BWP for the DCI format 0_0 detected in any common search space set in the CORESET #0 (or an additional common CORESET set for the initial DL BWP). That is, even when the BWP indication field (bandwidth part indicator field) is not set in the DCI format, the RB numbering of the resource allocation is determined in the initial UL BWP for the DCI format 0_0 detected in any common search space set in the CORESET set for the initial DL BWP. Also, even if the BWP indication field (bandwidth part indicator field) is not set in the DCI format, for DCI format 0_0 detected in any common search space set in the CORESET configured for the active BWP, the RB numbering of the resource allocation is determined within the active BWP.

[0262] When a BWP indication field (bandwidth part indicator field) is set in the DCI format, the RB numbering of the resource allocation is determined within the BWP indicated in the BWP indication field. However, even if the BWP indication field (bandwidth part indicator field) is set in the DCI format, the RB numbering of the resource allocation is determined within the initial UL BWP for DCI format 0_0 detected in any common search space set in CORESET#0 (or an additional common CORESET set for the initial DL BWP). When detecting a PDCCH for the terminal device 1, the terminal device 1 first determines a UL BWP to which the resource assignment is applied, and then determines a resource allocation within the determined UL BWP.

[0263] Also, for the RAR UL grant, the RB numbering of the uplink type 1 resource allocation may be determined within the active BWP of the terminal device 1. Also, in the contention based random access procedure, the RB numbering of the resource allocation indicated in the RAR UL grant is determined within the initial UL BWP of the terminal device 1. That is, in the contention based random access procedure, the RB numbering of the frequency direction resource allocation of the PUSCH scheduled by the RAR UL grant (MAC RAR) is determined within the initial UL BWP of the terminal device 1. Also, in the non-contention based random access procedure, the RB numbering of the resource allocation indicated in the RAR UL grant is determined within the active UL BWP of the terminal device 1. That is, in the non-contention based random access procedure, the RB numbering of the frequency direction resource allocation of the PUSCH scheduled by the RAR UL grant (MAC RAR) is determined within the active UL BWP of the terminal device 1.

[0264] Also, in a contention-based random access procedure, when DCI format 1_0 for scheduling a PDSCH (DL-SCH transport block) including an RAR UL grant is detected in a common search space (for example, a type 1 PDCCH common search space) in CORESET#0, the RB numbering of the resource allocation indicated in the RAR UL grant may be determined in the initial UL BWP of the terminal device 1. Here, the DCI format 1_0 is DCI format 1_0 to which a CRC parity bit scrambled by the corresponding RA-RNTI is added. Also, in a contention-based random access procedure, when DCI format 1_0 for scheduling a PDSCH (DL-SCH transport block) including an RAR UL grant is detected in a common search space (for example, a type 1 PDCCH common search space) in an additional common CORESET (or a CORESET other than CORESET#0), the RB numbering of the resource allocation indicated in the RAR UL grant may be determined in the active UL BWP of the terminal device 1. However, if DCI format 1_0 scheduling a PDSCH (DL-SCH transport block) including an RAR UL grant is detected in a common search space (e.g., a type 1 PDCCH common search space) in an additional common CORESET configured for an initial DL BWP, the RB numbering of the resource allocation indicated in the RAR UL grant may be determined within the initial UL BWP of the terminal device 1.

[0265] Also, for DCI format 0_0 that schedules retransmission of Msg3 PUSCH, the RB numbering of the resource allocation is determined by the UL BWP to which the RAR UL grant (resource block assignment included in the RAR UL grant) is applied. DCI format 0_0 that schedules retransmission of Msg3 PUSCH is scrambled by the TC-RNTI. DCI format 0_0 does not include a BWP indication field.

[0266] <Message 3 (S803)> The terminal device 1 performs PUSCH transmission of message 3 based on the RAR UL grant included in the RAR message received in S802. The PUSCH corresponding to the transmission of message 3 is transmitted in the serving cell in which the corresponding preamble was transmitted in the PRACH. Specifically, the PUSCH corresponding to the transmission of message 3 is transmitted in an active UL BWP.

[0267] <Resending message 3 (S803a)> The retransmission of the message 3 is scheduled by DCI format 0_0 to which a CRC parity bit scrambled by the TC-RNTI included in the RAR message is added. That is, the PUSCH retransmission of the transport block transmitted on the PUSCH corresponding to the RAR UL grant included in the RAR message is scheduled by DCI format 0_0 to which a CRC parity bit scrambled by the TC-RNTI is added. The DCI format 0_0 is transmitted on the PDCCH of the type 1 PDCCH common search space set. That is, after transmitting the message 3 in S803, the terminal device 1 may monitor the DCI format 0_0 that schedules the retransmission of the message 3. In S803a, if the terminal device 1 detects the DCI format 0_0 that schedules the retransmission of the message 3, it executes S803b.

[0268] The DCI format 0_0 for scheduling the retransmission of message 3 includes a frequency domain resource assignment field. The bits of the field are assigned based on the initial UL BWP. Specifically, the number of bits of the field is expressed as Ceiling(log2(N UL、BWP RB (N UL、BWP RB +1) / 2)), where N UL、BWP RBis the number of resource blocks indicating the bandwidth of the initial UL BWP. That is, even if resources for retransmission of message 3 are scheduled in any UL BWP among one or more UL BWPs configured for the terminal device 1, the number of bits in the frequency domain resource assignment field is a fixed value (the same value) based on the bandwidth of the initial UL BWP.

[0269] As an example, UL、BWP RB may be given based on the type of random access procedure. For example, in a contention-based random access procedure, N UL、BWP RB is the number of resource blocks indicating the bandwidth of the initial UL BWP. For example, in a non-contention based random access procedure, N UL、BWP RB is the number of resource blocks indicating the bandwidth of the active UL BWP.

[0270] The terminal device 1 needs to interpret the bits of the frequency domain resource assignment field based on the initial UL BWP to adapt to the bandwidth of the UL BWP to which the frequency domain resource assignment (frequency domain resource assignment field) is applied. As described above, the terminal device 1 determines the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied when truncating or inserting bits for the Msg3 PUSCH frequency resource assignment. Here, the UL BWP to which the frequency domain resource assignment field included in the DCI format 0_0 is applied may be determined by the same determination method as the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied, as described above. That is, the UL BWP to which the frequency domain resource assignment included in the DCI format 0_0 is applied may be the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied. That is, the terminal device 1 may specify the frequency direction resource block allocation of the PUSCH in the UL BWP to which the Msg3 PUSCH frequency resource allocation is applied, based on the value of the RIV indicated in the frequency domain resource assignment field.

[0271] For example, when the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied is the initial UL BWP (or the initial active UL BWP), the UL BWP to which the frequency domain resource assignment field included in DCI format 0_0 is applied is the initial UL BWP. The base station device 3 generates an RIV using the size of the initial UL BWP to which the resource assignment is applied, determines a bit string to be included in the frequency resource assignment field, and transmits it to the terminal device 1. Then, the terminal device 1 specifies the frequency direction resource allocation of PUSCH to the physical resource blocks of the UL BWP (initial UL BWP) to which the resource assignment is applied, regardless of which UL BWP is actually activated. The terminal device 1 uses FIG. 12(A) to determine the RB corresponding to the physical resource block of the initial BWP.start and L RBs Here, N in FIG. size BWP is the resource block indicating the bandwidth of the initial UL BWP. In other words, the value of RIV indicated in the frequency domain resource assignment field is the size of the initial UL BWP to which the resource assignment is applied, the RB corresponding to the resource block of the initial UL BWP, start and L RBs Based on RB start is the number of resource blocks indicating the start position of resource allocation based on the physical resource block index 0 of the initial BWP UL. RBs cannot exceed the number of resource blocks indicating the bandwidth of the initial UL BWP, i.e. the numbering of resources indicated in the frequency domain resource assignment field starts from the lowest number of physical resource blocks of the initial UL BWP.

[0272] From the above example, when DCI format 0_0 is detected in the type 1 PDCCH common search space set in CORESET#0 or an additional common CORESET configured for the initial DL BWP, N in FIG. 12(A) size BWPThe size of the initial UL BWP is used for the size of the initial UL BWP. Here, DCI format 0_0 may be monitored by the CSS. That is, even if the activated UL BWP (UL BWP through which uplink data is transmitted) is not the initial UL BWP, the terminal device 1 identifies the resource block allocation in the frequency direction of the initial UL BWP. The value of the resource block offset between the physical resource block index 0 of the initial UL BWP and the physical resource block index 0 of the active UL BWP is given by the higher layer parameter locationAndBandwidth set for each BWP. In addition, for a case in which DCI format 0_0 is detected in any common search space set in CORESET#0 or an additional common CORESET set for the initial DL BWP, N in FIG. 12(A) is used for the resource block offset. size BWP The size of the initial UL BWP is used.

[0273] For example, when the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied is an active UL BWP, the UL BWP to which the frequency domain resource assignment field included in DCI format 0_0 is applied is the active UL BWP. The base station device 3 generates an RIV using the size of the active UL BWP to which the resource assignment is applied, determines a bit string to be included in the frequency resource assignment field, and transmits it to the terminal device 1. Then, the terminal device 1 specifies the frequency direction resource allocation of the PUSCH of the active UL BWP to which the frequency domain resource assignment is applied. If the active UL BWP is not the initial active UL BWP, the terminal device 1 uses the method of FIG. 12(B) to determine the RB corresponding to the physical resource block of the active UL BWP. start and L RBs In this case, N in FIG. nitial BWP is the number of resource blocks that indicates the bandwidth of the initial UL BWP. active BWPis the number of resource blocks that indicate the bandwidth of the active UL BWP. The value of RIV is the number of resource blocks that indicate the bandwidth of the initial BWP, N nitial BWP , the start position of the resource block RB' start , and the number of consecutively allocated resource blocks L' RBs Based on the above, the RB start is the number of resource blocks indicating the start position of resource allocation based on physical resource block index 0 of the active UL BWP, i.e., the numbering of resources indicated in the frequency domain resource assignment field starts from the lowest physical resource block number of the active UL BWP.

[0274] In view of the above example, the size of DCI format 0_0 in a CSS (any common search space set or type 1 PDCCH common search space set) (or the size of the frequency domain resource assignment field included in the DCI format) is derived from the size of the initial UL BWP, but the UL BWP to which the resource assignment of the Msg3 PUSCH frequency resource assignment field is applied is an active UL BWP, in which case the method of FIG. 12(B) may be applied. In other words, the size of DCI format 0_0 in a CSS (or the size of the frequency domain resource assignment field included in the DCI format) is derived from the size of the initial UL BWP, but the size of the DCI format 0_0 (or the size of the frequency domain resource assignment field included in the DCI format) is applied to another active UL BWP (an activated UL BWP other than the initial UL BWP), in which case the method of FIG. 12(B) may be applied. Here, the CSS is a CSS associated with a CORESET other than CORESET#0 and an additional common CORESET configured for the initial DL BWP. That is, the CSS is a CSS associated with a CORESET configured for a DL BWP other than the initial DL BWP. Here, the DCI format 0_0 may be scrambled by the TC-RNTI. That is, the DCI format is derived by the size of the initial UL BWP, but the UL BWP to which the DCI format is applied is another active UL BWP, and the search space set in the DCI format is a common search space set associated with a CORESET configured for a BWP other than the initial DL BWP, or a UE-specific search space set, the method of FIG. 12(B) may be applied.

[0275] As described above, the number of bits in the frequency domain resource assignment field included in DCI format 0_0 is N, which indicates the bandwidth of the initial UL BWP. UL,BWP RBThe N UL,hop The number of hopping bits is N UL,BWP RB may be given as one or two bits depending on whether N exceeds a predetermined value Y of the number of resource blocks. UL,hop The number of hopping bits is N size BWP may be given 1 or 2 bits depending on whether N exceeds a predetermined value Y of the number of resource blocks. size BWP is the number of resource blocks indicating the bandwidth of the UL BWP to which the frequency domain resource assignment field applies. That is, N size BWP If is less than a given number of resource blocks Y, then N UL,hop The hopping bit may be set to 1 bit. The frequency offset of the second hop for the PUSCH transmission of message 3 is Floor(N size BWP / 2) or Floor(N size BWP / 4). N size BWP If is equal to or greater than a given value Y of the number of resource blocks, then N UL,hop The hopping bits may be given as 2 bits. The frequency offset of the second hop for the PUSCH transmission of message 3 is Floor(N size BWP / 2), Floor(N size BWP / 4), or -Floor(N size BWP / 4).

[0276] <Resending message 3 (S803b)> In S803a, if DCI format 0_0 to which CRC parity bits scrambled by the TC-RNTI are added is detected, the terminal device 1 performs PUSCH retransmission of the transport block transmitted in S803.

[0277] <Message 4 (S804)> To respond to the PUSCH transmission of message 3, the terminal device 1, for which no C-RNTI is indicated, monitors DCI format 1_0, which schedules a PDSCH including a UE contention resolution identity, where this DCI format 1_0 is appended with CRC parity bits scrambled by the corresponding TC-RNTI. To respond to the PDSCH reception with the UE contention resolution identity, the terminal device 1 transmits HARQ-ACK information on a PUCCH, which may be transmitted on the active UL BWP in which message 3 is transmitted.

[0278] This allows the terminal device 1 performing the random access procedure to transmit uplink data to the base station device 3.

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

[0280] 15 is a schematic block diagram showing the configuration of a terminal device 1 of this embodiment. As shown in the figure, the terminal device 1 includes a radio transmission / reception unit 10 and an upper layer processing unit 14. The radio transmission / reception 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 transmission / reception unit 10 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. The upper layer processing unit 14 is also referred to as a measuring unit, a selecting unit, or a control unit 14.

[0281] 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 selecting one reference signal from one or more reference signals based on the measurement value of each reference signal. The upper layer processing unit 14 may have a function of selecting a PRACH opportunity associated with the selected one reference signal from one or more PRACH opportunities. The upper layer processing unit 14 may have a function of identifying one index from one or more indexes set in a higher layer (e.g., an RRC layer) and setting the index as a preamble index when bit information included in information indicating the start of a random access procedure received by the radio transmission / reception unit 10 is a predetermined value. The upper layer processing unit 14 may have a function of identifying an index associated with a selected reference signal from one or more indexes configured by RRC and setting the index as a preamble index. The upper layer processing unit 14 may have a function of determining a next available PRACH opportunity based on received information (e.g., SSB index information and / or mask index information). The upper layer processing unit 14 may have a function of selecting an SS / PBCH block based on received information (e.g., SSB index information).

[0282] The medium access control layer processing unit 15 included in the upper layer processing unit 14 performs processing of the MAC layer (medium access control layer). The medium access control layer processing unit 15 controls the transmission of a scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 16.

[0283] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer (radio resource control layer). The radio resource control layer processing unit 16 manages various setting information / parameters of its own device. The radio resource control layer processing unit 16 sets various setting information / parameters based on an upper 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.

[0284] The wireless transceiver 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transceiver 10 separates, demodulates, and decodes a signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver 10 generates a transmission signal by modulating and encoding data, and transmits the signal to the base station device 3. The wireless transceiver 10 may have a function of receiving one or more reference signals in a certain cell. The wireless transceiver 10 may have a function of receiving information identifying one or more PRACH opportunities (e.g., SSB index information and / or mask index information). The wireless transceiver 10 may have a function of receiving a signal including instruction information instructing the start of a random access procedure. The wireless transceiver 10 may have a function of receiving information identifying a predetermined index. The wireless transceiver 10 may have a function of receiving information identifying an index of a random access preamble. The wireless transceiver 10 may have a function of transmitting a random access preamble at a PRACH opportunity determined by the upper layer processing unit 14.

[0285] 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 RF unit 12 outputs the processed analog signal to the baseband unit.

[0286] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract a signal in the frequency domain.

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

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

[0289] FIG. 16 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. As shown in the figure, the base station device 3 includes a radio transmission / reception unit 30 and an upper layer processing unit 34. The radio transmission / reception 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 radio transmission / reception unit 30 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. 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 control unit 34.

[0290] The upper layer processing unit 34 performs some or all of the processes 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 identifying one reference signal from one or more reference signals based on a random access preamble received by the radio transceiver unit 30. The upper layer processing unit 34 may identify a PRACH opportunity for monitoring the random access preamble from at least the SSB index information and the mask index information.

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

[0292] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 ​​generates downlink control information (uplink grant, downlink grant) including resource allocation information for the terminal device 1. The radio resource control layer processing unit 36 ​​generates or acquires from an upper node downlink control information, downlink data (transport block, random access response) arranged on a physical downlink shared channel, system information, an RRC message, a MAC CE (Control Element), and the like, 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 the 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.

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

[0294] The radio transmission / reception unit 30 has a function of transmitting one or more reference signals. The radio transmission / reception unit 30 may also have a function of receiving a signal including a beam failure recovery request transmitted from the terminal device 1. The radio transmission / reception unit 30 may have a function of transmitting information identifying one or more PRACH opportunities (for example, SSB index information and / or mask index information) to the terminal device 1. The radio transmission / reception unit 30 may have a function of transmitting information identifying a predetermined index. The radio transmission / reception unit 30 may have a function of transmitting information identifying an index of a random access preamble. The radio transmission / reception unit 30 may have a function of monitoring a random access preamble at a PRACH opportunity identified by the upper layer processing unit 34. Other than that, some of the functions of the radio transmission / reception unit 30 are similar to those of the radio transmission / reception unit 10, and therefore description thereof will be omitted. Note that, when the base station device 3 is connected to one or more transmission / reception points 4, some or all of the functions of the radio transmission / reception unit 30 may be included in each transmission / reception point 4.

[0295] Furthermore, the upper layer processing unit 34 transmits (transfers) or receives 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. 16, other components of the base station device 3 and transmission paths of data (control information) between the components are omitted, but it is clear that the base station device 3 has a plurality of blocks having other functions necessary for operating as the base station device 3 as components. For example, the upper layer processing unit 34 includes a radio resource management layer processing unit and an application layer processing unit. The upper layer processing unit 34 may also have a function of setting a plurality of scheduling request resources corresponding to each of a plurality of reference signals transmitted from the radio transmission / reception unit 30.

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

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

[0298] (1) More specifically, a terminal device 1 in a first aspect of the present invention includes a receiving unit 10 that receives a PDSCH including an RAR message, and a control unit 16 that controls resource allocation based on a first field indicating an Msg3 PUSCH frequency resource assignment indicated in a first UL grant included in the RAR message, wherein the control unit truncates X bits from the least significant bit into the bits of the first field when the number of first resource blocks is smaller than or equal to a predetermined number of resource blocks, and inserts Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is greater than the predetermined number of resource blocks, and the number of first resource blocks is given based on a type of random access procedure.

[0299] (2) In the first aspect of the present invention, when the type of the random access procedure is a non-contention based random access procedure, the first number of resource blocks is a number of resource blocks indicating a bandwidth of an active UL BWP.

[0300] (3) In the first aspect of the present invention, when the type of the random access procedure is a contention based random access procedure, the first number of resource blocks is a number of resource blocks indicating a bandwidth of an initial UL BWP.

[0301] (4) A base station device 3 in a second aspect of the present invention includes a control unit 36 ​​that generates a first UL grant including a first field indicating an Msg3 PUSCH frequency resource assignment indicating resource allocation, and a transmission unit 30 that transmits a PDSCH including an RAR message including the first UL grant, wherein the control unit truncates X bits from the least significant bit into the bits of the first field when the number of first resource blocks is smaller than or equal to a predetermined number of resource blocks, and inserts Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the predetermined number of resource blocks, and the number of first resource blocks is given based on a type of random access procedure.

[0302] (5) In the second aspect of the present invention, when the type of the random access procedure is a non-contention based random access procedure, the first number of resource blocks is a number of resource blocks indicating a bandwidth of an active UL BWP.

[0303] (6) In the second aspect of the present invention, when the type of the random access procedure is a contention based random access procedure, the first number of resource blocks is a number of resource blocks indicating a bandwidth of an initial UL BWP.

[0304] (7) A terminal device 1 performing a contention-based random access procedure in a third aspect of the present invention includes a receiving unit 10 that receives a PDSCH including an RAR message, and a control unit 16 that controls resource allocation based on a first field indicating an Msg3 PUSCH frequency resource assignment indicated in a first UL grant included in the RAR message, and the control unit truncates X bits from the least significant bit to the bits of the first field when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, and inserts Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the value of the predetermined number of resource blocks, and the number of first resource blocks is the number of resource blocks indicating the bandwidth of a UL BWP having the same BWP identifier as a DL BWP in which configuration information of a CORESET indicated in a Type 1 PDCCH common search space set is set, the Type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information.

[0305] (8) A base station device 3 communicating with a terminal device 1 performing a contention based random access procedure according to a fourth aspect of the present invention includes a control unit 36 ​​that generates a first UL grant including a first field indicating an Msg3 PUSCH frequency resource assignment indicating resource allocation, and a transmission unit 30 that transmits a PDSCH including an RAR message, and the first UL grant is included in the RAR message, and the control unit truncates X bits from the least significant bit to the bits of the first field when the number of first resource blocks is smaller than or equal to a value of a predetermined number of resource blocks, and inserts Y most significant bits set to a value of '0' after a hopping bit into the bits of the first field when the number of first resource blocks is larger than the value of the predetermined number of resource blocks, and the number of first resource blocks is determined based on a UL BWP identifier having the same BWP identifier as a DL BWP in which configuration information of CORESET indicated in a type 1 PDCCH common search space set is set. The type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource for searching for downlink control information.

[0306] (9) A terminal device 1 in a fifth aspect of the present invention includes a receiving unit 10 that receives a first DCI format scrambled by a TC-RNTI in a search space set, and a control unit 16 that determines a resource allocation for a PUSCH based on a second field indicating a frequency domain resource assignment included in the first DCI format, wherein, based on the number of first resource blocks indicating the bandwidth of a first UL BWP, the bits of the first field indicating the Msg3 PUSCH frequency resource assignment indicated in a first UL grant included in an RAR message are truncated from the least significant bit and / or the most significant bit is inserted, the size of the second field is derived by the bandwidth of an initial UL BWP, and the control unit determines a frequency direction resource block allocation to be applied to the first UL BWP based on the value of RIV indicated in the second field.

[0307] (10) In a fifth aspect of the present invention, when the first UL BWP is an active UL BWP other than an initial UL BWP and the search space set is a common search space associated with a CORESET set for a BWP other than an initial DL BWP or a UE-specific search space, the control unit identifies a first start position of resource allocation based on an initial UL BWP and a number of first resource blocks consecutively allocated from a value of RIV indicated in the second field, and applies a second start position and the number of second resource blocks obtained by scaling the first start position and the number of the first resource blocks by a coefficient K to physical resource blocks of an active UL BWP to identify resource allocation of a PUSCH, where the CORESET is a time and frequency resource for searching for downlink control information.

[0308] (11) In a fifth aspect of the present invention, when the first UL BWP is an active UL BWP other than an initial UL BWP and the search space set is a common search space associated with a CORESET set for an initial DL BWP, the control unit identifies a first start position of resource allocation based on the initial UL BWP and the number of first resource blocks consecutively allocated from the value of RIV indicated in the second field, and applies the identified first start position and the identified number of first resource blocks to physical resource blocks of the initial UL BWP to specify resource allocation for a PUSCH.

[0309] (12) In a fifth aspect of the present invention, when the first UL BWP is an initial UL BWP, a first start position of resource allocation and the number of first resource blocks consecutively allocated based on the initial UL BWP are identified from the value of RIV indicated in the second field, and the identified first start position and the number of first resource blocks are applied to physical resource blocks of the initial UL BWP to determine resource allocation for a PUSCH.

[0310] (13) In the fifth aspect of the present invention, the coefficient K is given by the ratio of the bandwidth of the active UL BWP to the bandwidth of the initial UL BWP rounded down to the nearest power of two when the bandwidth of the active UL BWP is greater than the bandwidth of the initial UL BWP, and is given by 1 otherwise.

[0311] (14) A base station device 3 in a sixth aspect of the present invention includes a control unit 36 ​​that generates a first DCI format including a second field indicating a frequency domain resource assignment indicating resource allocation information, and a transmission unit 30 that transmits the first DCI format in a Type 1 PDCCCH common search space set, wherein the first DCI format is scrambled by a TC-RNTI, bits of a first field indicating an Msg3 PUSCH frequency resource assignment indicated in a first UL grant included in an RAR message are truncated from the least significant bit and / or the most significant bit is inserted based on the number of first resource blocks indicating a bandwidth of a first UL BWP, a size of the second field is derived based on a bandwidth of an initial UL BWP, and the control unit specifies a frequency direction resource block allocation of a PUSCH of the first UL BWP to be applied to a terminal device, and generates a value of an RIV indicated in the second field.

[0312] (15) In a sixth aspect of the present invention, when the first UL BWP is an active UL BWP other than an initial UL BWP and a CORESET associated with the common search space set is a CORESET set for a BWP other than an initial DL BWP, the control unit identifies a first start position of resource allocation based on an initial UL BWP and a number of first resource blocks consecutively allocated from a value of RIV indicated in the second field to be generated, applies a second start position and the number of second resource blocks obtained by scaling the first start position and the number of the first resource blocks by a coefficient K to physical resource blocks of an active UL BWP, and specifies a resource allocation of a PUSCH to be applied to a terminal device, and the CORESET is a time and frequency resource for searching for downlink control information.

[0313] (16) In a sixth aspect of the present invention, when the first UL BWP is an active UL BWP other than an initial UL BWP and a CORESET associated with the common search space set is a CORESET set for an initial DL BWP, the control unit identifies a first start position of resource allocation based on the initial UL BWP and a number of first resource blocks consecutively allocated from a value of RIV indicated in the second field to be generated, applies the identified first start position and the identified number of first resource blocks to a physical resource block of the initial UL BWP, and specifies a resource allocation of a PUSCH to be applied to a terminal device, and the CORESET is a time and frequency resource for searching for downlink control information.

[0314] (17) In a sixth aspect of the present invention, when the first UL BWP is an initial UL BWP, the control unit identifies a first start position of resource allocation based on the initial UL BWP and the number of first resource blocks consecutively allocated from a value of RIV indicated in the second field to be generated, applies the identified first start position and the identified number of first resource blocks to physical resource blocks of the initial UL BWP, and specifies a resource allocation of a PUSCH to be applied to a terminal device.

[0315] (18) In a sixth aspect of the present invention, the coefficient K is given by the ratio of the bandwidth of the active UL BWP to the bandwidth of the initial UL BWP rounded down to the nearest power of two when the bandwidth of the active UL BWP is greater than the bandwidth of the initial UL BWP, and is given by 1 otherwise.

[0316] This allows the terminal device 1 to communicate with the base station device 3 efficiently.

[0317] 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), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

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

[0319] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), 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 circuit described above may be composed of a digital circuit or an analog circuit. In addition, when a technology for integrated circuitization that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit according to that technology.

[0320] In the embodiment of the present invention, an example is described in which the present invention is applied to a communication system composed of a base station device and a terminal device, but the present invention can also be applied to a system in which terminals communicate with each other, such as D2D (Device to Device).

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

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

[0323] 1(1A, 1B) Terminal equipment 3 Base station equipment 4 Transmitting / receiving points (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 that communicates with a base station, A receiver that receives an initial uplink (UL) bandwidth portion (BWP) configuration and an additional UL BWP configuration via a radio resource control (RRC) message and receives a random access response (RAR) message including a UL grant in a contention-based random access procedure; a processor for switching the active UL BWP between the initial UL BWP and the additional UL BWP such that one of the initial UL BWP and the additional UL BWP is activated as an active UL BWP and the other is deactivated; A transmitter that transmits a Physical Uplink Shared Channel (PUSCH) in the active UL BWP; Preparation, The PUSCH is scheduled using the RAR UL grant comprising a PUSCH frequency resource allocation field of a fixed bit size; The processing unit interprets the truncated or extended field as a field indicating a frequency resource allocation of the PUSCH; (1) In the case of a contention-based random access procedure and the initial UL BWP is an active UL BWP, the truncated field is a field in which bits are truncated from the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP, or the extended field is a field in which bits are inserted into the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP to extend the field; (2) In the case of a contention-based random access procedure and the additional UL BWP is an active UL BWP, the truncated field is a field in which bits are truncated from the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP, or the extended field is a field in which bits are inserted into the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP to extend the field; The size of the initial UL BWP is a number of resource blocks indicating a bandwidth of the initial UL BWP. Terminal device.

2. A communication method in a terminal device that communicates with a base station device, comprising: receiving an initial uplink (UL) bandwidth portion (BWP) configuration and an additional UL BWP configuration via a Radio Resource Control (RRC) message; receiving a random access response (RAR) message including a UL grant with a PUSCH frequency resource allocation field of a fixed bit size in a contention-based random access procedure; switching the active UL BWP between the initial UL BWP and the additional UL BWP such that one of the initial UL BWP and the additional UL BWP is activated as an active UL BWP and the other is deactivated; interpreting the truncated or extended field as a field indicating a frequency resource allocation for a Physical Uplink Shared Channel (PUSCH), (1) In the case of a contention-based random access procedure and the initial UL BWP is an active UL BWP, the truncated field is a field in which bits are truncated from the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP, or the extended field is a field in which bits are inserted into the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP to extend the field; (2) In the case of a contention-based random access procedure and the additional UL BWP is an active UL BWP, the truncated field is a field in which bits are truncated from the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP, or the extended field is a field in which bits are inserted into the PUSCH frequency resource allocation field of the fixed bit size by always using the size of the initial UL BWP to extend the field. Steps and transmitting the PUSCH in the active UL BWP; having The PUSCH is scheduled using the RAR UL grant; The size of the initial UL BWP is a number of resource blocks indicating a bandwidth of the initial UL BWP. Communication methods.

Images