Base station apparatus, terminal apparatus, and communication method

Abstract

The present invention related to a terminal device and associated method which enables efficient communication in a wireless communication system. This terminal device communicates with a base station device and is provided with: a reception unit configured to receive a configuration of an initial uplink (UL) bandwidth part (BWP) and a configuration of an additional UL BWP via a radio resource control (RRC) message and receive a random access response (RAR) message including an RAR UL grant in a contention-based random access procedure; a processing unit configured to switch an 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 the active UL BWP and the other one is deactivated; and a transmission unit configured to transmit a physical uplink shared channel (PUSCH) in the active UL BWP, wherein, the PUSCH is scheduled by using the RAR UL grant, the RAR UL grant comprising a PUSCH frequency resource allocation field with a fixed bit size, the processing unit is further configured to to interpret a truncated field or an expanded field as a field indicating a frequency resource allocation of the PUSCH, wherein (i) when the contention-based random access procedure is performed and the initial UL BWP is the active UL BWP, the truncated field is a field in which bits are truncated from the PUSCH frequency resource allocation field with the fixed bit size by using a first size, or the expanded field is a field in which bits are inserted into the PUSCH frequency resource allocation field with the fixed bit size for expanding the PUSCH frequency resource allocation field by using the first size; and (ii) when the contention-based random access procedure is performed and the additional UL BWP is the active UL BWP, the truncated field is a field in which bits are truncated from the PUSCH frequency resource allocation field with the fixed bit size by using the first size, or the expanded field is a field in which bits are inserted into the PUSCH frequency resource allocation field with the fixed bit size for expanding the PUSCH frequency resource allocation field by using the first size; and wherein the initial UL BWP has a size, wherein the first size is the size of the initial UL BWP, and wherein the size of the initial UL BWP is a number of resource blocks indicating a bandwidth of the initial UL BWP.

Description

Base station equipment, terminal equipment, and communication method

[0001] The present invention relates to a base station device, a terminal device, and a communication method. This application claims priority based on Japanese Patent Application No. 2018-134080, filed in Japan on July 17, 2018, the contents of which are incorporated herein by reference.

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

[0003] Fifth-generation cellular systems require three service scenarios: eMBB (enhanced Mobile Broadband) for high-speed, high-capacity transmission; URLLC (Ultra-Reliable and Low Latency Communication) for low-latency, highly reliable communication; and mMTC (massive Machine Type Communication) for numerous machine-type devices such as IoT (Internet of Things) connections.

[0004] RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016.

[0005] An object of one aspect of the present invention is to provide a terminal device, a base station device, a communication method, and an integrated circuit that enable efficient communication in the above-described wireless communication system.

[0006] (1) In order to achieve the above objective, the embodiments of the present invention employ the following means. In other words, a terminal device communicating with a base station device in one aspect of the present invention includes a receiving unit that receives the setting of an initial uplink (UL) bandwidth portion (BWP) and the setting of additional UL BWPs via radio resource control (RRC) messages and receives RAR messages including a random access response (RAR) UL grant, and a transmitting unit that transmits a PUSCH (Physical Uplink Shared Channel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate the allocation of frequency resources for the PUSCH, and whether to truncate the first field or insert bits into the first field is based on the bandwidth of the initial UL BWP.

[0007] (2) Furthermore, a base station device communicating with a terminal device in one aspect of the present invention includes a transmitting unit that transmits the setting of an initial uplink (UL) band portion (BWP) and the setting of an additional UL BWP via a radio resource control (RRC) message, and transmits a RAR message including a random access response (RAR) UL grant, and a receiving unit that receives a PUSCH (Physical Uplink Shared Channel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate the allocation of frequency resources for the PUSCH, and the terminal device either truncates the first field or inserts a bit into the first field, the initial UL This is a base station device based on the bandwidth of BWP.

[0008] (3) Furthermore, a communication method in a terminal device communicating with a base station device according to one aspect of the present invention comprises the steps of receiving the setting of an initial uplink (UL) bandwidth portion (BWP) and the setting of an additional UL BWP via a radio resource control (RRC) message, receiving a RAR message including a random access response (RAR) UL grant, and transmitting a PUSCH (Physical Uplink Shared Channel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate the allocation of frequency resources for the PUSCH, and whether to truncate the first field or insert bits into the first field is a communication method based on the bandwidth of the initial UL BWP.

[0009] (4) Furthermore, a communication method in a base station device communicating with a terminal device according to one aspect of the present invention includes the steps of: transmitting the setting of an initial uplink (UL) band portion (BWP) and the setting of an additional UL BWP via a radio resource control (RRC) message; transmitting a RAR message including a random access response (RAR) UL grant; and receiving a PUSCH (Physical Uplink Shared Channel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate the allocation of frequency resources for the PUSCH, and the terminal device either truncates the first field or inserts a bit into the first field. This is a communication method based on the bandwidth of BWP.

[0010] According to one aspect of this invention, a base station device and a terminal device can communicate efficiently.

[0011] This figure shows a concept of a wireless communication system according to an embodiment of the present invention. This figure shows examples of SS / PBCH blocks and SS burst sets according to an embodiment of the present invention. This figure shows an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. This figure shows the time-domain relationship between subframes, slots, and minislots according to an embodiment of the present invention. This figure shows an example of a slot or subframe according to an embodiment of the present invention. This figure shows an example of beamforming according to an embodiment of the present invention. This figure shows an example of BWP configuration according to an embodiment of the present invention. This figure shows an example of a random access procedure for terminal device 1 according to an embodiment of the present invention. This figure shows an example of a field included in a RAR UL grant according to an embodiment of the present invention. This figure shows an example of interpreting the 'Msg3 PUSCH frequency resource allocation' field according to this embodiment. This figure shows an example of explaining uplink resource allocation type 1 for BWP according to this embodiment. This figure shows an example of calculating RIV according to an embodiment of the present invention. This figure shows an example of assigning an SSB index to a PRACH opportunity according to this embodiment. This is a flowchart showing an example of a random access procedure for a MAC entity according to an embodiment of the present invention. This is a schematic block diagram showing the configuration of terminal device 1 according to an embodiment of the present invention. This is a schematic block diagram showing the configuration of base station device 3 according to an embodiment of the present invention.

[0012] Embodiments of the present invention will be described below.

[0013] Figure 1 is a conceptual diagram of the wireless communication system in this embodiment. In Figure 1, the wireless communication system comprises terminal device 1A, terminal device 1B, and base station device 3. Hereinafter, terminal device 1A and terminal device 1B will also be referred to as terminal device 1.

[0014] Terminal device 1 is also called a user terminal, mobile station device, communication terminal, mobile device, terminal, UE (User Equipment), and MS (Mobile Station). Base station device 3 is also called a radio base station device, base station, radio base station, fixed station, NB (Node B), eNB (evolved Node B), BTS (Base Transceiver Station), BS (Base Station), NR NB (NR Node B), NNB, TRP (Transmission and Reception Point), and gNB. Base station device 3 may include a core network device. Base station device 3 may also include one or more transmission and reception points 4. At least some of the functions / processes of base station device 3 described below may also be functions / processes of each transmission and reception point 4 provided by the base station device 3. Base station device 3 may serve terminal device 1 as one or more cells within a communication range (communication area) controlled by base station device 3. Furthermore, the base station device 3 may serve terminal devices 1 as one or more cells, each comprising a communication range (communication area) controlled by one or more transmission / reception points 4. Alternatively, one cell may be divided into multiple sub-areas (Beamed areas), and terminal devices 1 may be served in each sub-area. Here, the sub-areas may be identified based on the beam index used for beamforming or the pre-coding index.

[0015] The wireless communication link from base station device 3 to terminal device 1 is called the downlink. The wireless communication link from terminal device 1 to base station device 3 is called the uplink.

[0016] In Figure 1, the wireless communication between terminal device 1 and base station device 3 may use 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).

[0017] Furthermore, in Figure 1, universal-filtered multi-carrier (UFMC), filtered OFDM (F-OFDM), windowed OFDM, and filtered-bank multi-carrier (FBMC) may be used for wireless communication between terminal device 1 and base station device 3.

[0018] In this embodiment, OFDM is described using OFDM symbols as the transmission method, but the invention also includes cases where other transmission methods described above are used.

[0019] Furthermore, in Figure 1, the above-described transmission method may be used in wireless communication between terminal device 1 and base station device 3 without using CP, or with zero padding instead of CP. Also, CP or zero padding may be added to both the front and rear.

[0020] One aspect of this 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 cells or cell groups, carriers or carrier groups (e.g., primary cell (PCell), secondary cell (SCell), primary-secondary cell (PSCell), MCG (Master Cell Group), SCG (Secondary Cell Group), etc.). It may also be used in a standalone operation. In dual connectivity operation, SpCell (Special Cell) is referred to as MCG's PCell or SCG's PSCell, depending on whether the MAC (MAC: Medium Access Control) entity is associated with MCG or SCG, respectively. If it is not dual connectivity operation, SpCell (Special Cell) is referred to as PCell. SpCell (Special Cell) supports PUCCH transmission and competition-based random access.

[0021] In this embodiment, one or more serving cells may be configured for the terminal device 1. The configured serving cells may include one primary cell and one or more secondary cells. The primary cell may be the serving cell in which the initial connection establishment procedure was performed, the serving cell that initiated the connection re-establishment procedure, or the cell designated as the primary cell in the handover procedure. One or more secondary cells may be configured at or after the time the RRC (Radio Resource Control) connection is established. However, the configured serving cells may include one primary-secondary cell. The primary-secondary cell may be a secondary cell capable of transmitting control information on the uplink among the one or more secondary cells in which the terminal device 1 is configured. Furthermore, two types of subsets of serving cells, a master cell group and a secondary cell group, may be configured for the terminal device 1. A master cell group may consist of one primary cell and zero or more secondary cells. A secondary cell group may consist of one primary-secondary cell and zero or more secondary cells.

[0022] The wireless communication system of this embodiment may apply TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). The TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of the multiple 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 also be referred to as Unpaired spectrum operation. The FDD method may also be referred to as Paired spectrum operation.

[0023] In a downlink, the carrier corresponding to the serving cell is called the downlink component carrier (or downlink carrier). In an uplink, the carrier corresponding to the serving cell is called the uplink component carrier (or uplink carrier). In a sidelink, the carrier corresponding to the serving cell is called the sidelink component carrier (or sidelink carrier). The downlink component carrier, uplink component carrier, and / or sidelink component carrier are collectively referred to as the component carrier (or carrier).

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

[0025] In Figure 1, the following physical channels are used for wireless communication between terminal device 1 and base station device 3.

[0026] ・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)

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

[0028] Furthermore, PBCH may be used to announce the time index within the period of a block of synchronization signals (also referred to as an SS / PBCH block). Here, the time index is information indicating the index of the synchronization signal and PBCH within the cell. For example, when transmitting an SS / PBCH block using the assumption of three transmit beams (transmit filter settings, and quasi-co-location (QCL) with respect to the receive spatial parameters), the time sequence within a predetermined period or a set period may be indicated. Also, terminal equipment may recognize differences in time indices as differences in transmit beams.

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

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

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

[0032] DCI format 0_1 ​​may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating the Bandwidth Part (BWP), Channel State Information (CSI) requests, Sounding Reference Signal (SRS) requests, and information regarding antenna ports.

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

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

[0035] DCI format 2_0 is used to indicate the slot format for one or more slots. The slot format is defined as classifying each OFDM symbol within a slot as either a downlink, flexible, or uplink. For example, if the slot format is 28, then DDDDDDDDDDDDDFU is applied to the 14 OFDM symbols within the slot that specifies slot format 28. Here, D is a downlink symbol, F is a flexible symbol, and U is an uplink symbol. Slots will be discussed later.

[0036] DCI format 2_1 is used to notify terminal device 1 of physical resource blocks and OFDM symbols that can be assumed not to be transmitted. This information may be referred to as a preemption instruction (intermittent transmission instruction).

[0037] DCI format 2_2 is used for transmitting PUSCH and Transmit Power Control (TPC) commands for PUSCH.

[0038] DCI format 2_3 is used to transmit a group of TPC commands for the transmission of a sounding reference signal (SRS) by one or more terminal devices 1. An SRS request may also be transmitted along with the TPC commands. Furthermore, DCI format 2_3 may define SRS requests and TPC commands for uplinks without PUSCH and PUCCH, or for uplinks where the transmit power control of the SRS is not tied to the transmit power control of PUSCH.

[0039] A DCI for a downlink is also called a downlink grant or downlink assignment. Similarly, a DCI for an uplink is also called an uplink grant or uplink assignment.

[0040] The CRC (Cyclic Redundancy Check) parity bits added to the DCI format transmitted by a single PDCCH are scrambled with C-RNTI (Cell-Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling-Radio Network Temporary Identifier), RA-RNTI (Random Access-Radio Network Temporary Identity), or Temporary C-RNTI. C-RNTI and CS-RNTI are identifiers used to identify terminal devices within a cell. Temporary C-RNTI is an identifier used to identify terminal device 1 that transmitted a random access preamble during a contention-based random access procedure.

[0041] C-RNTI (Terminal Device Identifier (Identification Information)) is used to control PDSCH or PUSCH in one or more slots. CS-RNTI is used to periodically allocate resources for PDSCH or PUSCH. Temporary C-RNTI (TC-RNTI) is used to control PDSCH transmission or PUSCH transmission in one or more slots. Temporary C-RNTI is used to schedule the retransmission of random access message 3 and the transmission of random access message 4. RA-RNTI (Random Access Response Identification Information) is determined according to the frequency and time position information of the physical random access channel that transmitted the random access preamble.

[0042] PUCCH is used to transmit Uplink Control Information (UCI) in uplink wireless communication (wireless communication from terminal device 1 to base station device 3). Here, the uplink control information may include Channel State Information (CSI), which is used to indicate the state of the downlink channel. The uplink control information may also include a Scheduling Request (SR), which is used to request UL-SCH resources. Furthermore, the uplink control information may include a HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement). 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).

[0043] PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared Channel) from the Medium Access Control (MAC) layer. In the case of downlinks, it is also used to transmit system information (SI: System Information) and random access responses (RAR: Random Access Response).

[0044] PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer, or HARQ-ACK and / or CSI along with uplink data. It may also be used to transmit CSI only, or HARQ-ACK and CSI only. In other words, it may be used to transmit UCI only.

[0045] Here, the base station device 3 and the terminal device 1 exchange signals (send and receive) in the higher layer. For example, the base station device 3 and the terminal device 1 may send and receive RRC signaling (RRC message: Radio Resource Control message, also called RRC information: Radio Resource Control information) in the Radio Resource Control (RRC) layer. Also, the base station device 3 and the terminal device 1 may send and receive MAC control elements in the MAC (Medium Access Control) layer. Here, RRC signaling and / or MAC control elements are also referred to as higher layer signals. The higher layer here refers to the layer above the physical layer, and may include one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may include one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.

[0046] PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. Here, in PDSCH, the RRC signaling transmitted from base station equipment 3 may be a common signaling for multiple terminal devices 1 within a cell. Alternatively, the RRC signaling transmitted from base station equipment 3 may be dedicated signaling (also called dedicated signaling) for a particular terminal device 1. That is, terminal device-specific information may be transmitted to a particular terminal device 1 using dedicated signaling. Furthermore, PUSCH may be used to transmit UE Capability on the uplink.

[0047] In Figure 1, the following downlink physical signals are used in downlink wireless communication. Note that 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)

[0048] The synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). The cell ID may be detected using the PSS and SSS.

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

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

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

[0052] DMRS is used to demodulate modulated signals. Note that two types of reference signals may be defined for DMRS: one for demodulating PBCH and another for demodulating PDSCH, or both may be referred to simply as DMRS. CSI-RS is used for measuring Channel State Information (CSI) and beam management, and a periodic, semi-persistent, or aperiodic transmission method of the CSI reference signal is applied. CSI-RS may be defined as Non-Zero Power (NZP) CSI-RS and Zero Power (ZP) CSI-RS, where the transmit power (or receive power) is zero. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmit power or no transmit power. PTRS is used to track the phase in the time domain to compensate for frequency offsets 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, a single-port CSI-RS may have its radio resource configured as a TRS.

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

[0054] DMRS is used to demodulate modulated signals. Note that DMRS may be defined as two types of reference signals: one for demodulating PUCCH and another for demodulating PUSCH, or both may be referred to as DMRS. SRS is used for measuring uplink channel status information (CSI), channel sounding, and beam management. PTRS is used to track phase in the time domain to ensure frequency offset caused by phase noise.

[0055] Downlink physical channels and / or downlink physical signals are collectively referred to as downlink signals. Uplink physical channels and / or uplink physical signals are collectively referred to as uplink signals. Downlink physical channels and / or uplink physical channels are collectively referred to as physical channels. Downlink physical signals and / or uplink physical signals are collectively referred to as physical signals.

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

[0057] Figure 2 shows 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. Figure 2 shows an example in which two SS / PBCH blocks are included in a periodically transmitted SS burst set, and the SS / PBCH blocks consist of consecutive 4 OFDM symbols.

[0058] An SS / PBCH block is a unit block that includes at least a synchronization signal (PSS, SSS) and / or a PBCH. Transmitting the signals / channels contained in an SS / PBCH block is expressed as transmitting an SS / PBCH block. When the base station device 3 transmits the synchronization signal and / or PBCH using one or more SS / PBCH blocks in an SS burst set, it may use an independent downlink transmit beam for each SS / PBCH block.

[0059] In Figure 2, a single SS / PBCH block contains PSS, SSS, and PBCH multiplexed in time / frequency. However, the order in which PSS, SSS, and / or PBCH are multiplexed in the time domain may differ from the example shown in Figure 2.

[0060] SS burst sets may be transmitted periodically. For example, a period for initial access and a period to be set for connected (Connected or RRC_Connected) terminal devices may be defined. The period to be set for connected (Connected or RRC_Connected) terminal devices may be set at the RRC layer. The period to be set for connected (Connected or RRC_Connected) terminals may also be the period of a time-domain radio resource that may potentially be transmitted, and whether or not the base station device 3 actually transmits it may be determined. The period for initial access may also be defined in advance in the specifications or elsewhere.

[0061] The SS burst set may be determined based on the System Frame Number (SFN). The starting position (boundary) of the SS burst set may also be determined based on the SFN and the period.

[0062] An SS / PBCH block is assigned an SSB index (which may also be called an SSB / PBCH block index) according to its temporal position within the SS burst set. Terminal device 1 calculates the SSB index based on the PBCH information and / or reference signal information contained in the detected SS / PBCH block.

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

[0064] Within the period of a given SS burst set, SS / PBCH blocks assigned the same SSB index may be assumed to be QCL with respect to mean delay, mean gain, Doppler spread, Doppler shift, and spatial correlation. The setting corresponding to one or more QCL SS / PBCH blocks (or reference signals) may be referred to as the QCL setting.

[0065] The SS / PBCH block number (which may also be called the SS block number or SSB number) may be defined, for example, as the number of SS / PBCH blocks within an SS burst, an SS burst set, or a period of an SS / PBCH block. Alternatively, the SS / PBCH block number may represent the number of beam groups for cell selection within an SS burst, an SS burst set, or a period of an SS / PBCH block. Here, a beam group may be defined as the number of different SS / PBCH blocks or different beams contained within an SS burst, an SS burst set, or a period of an SS / PBCH block.

[0066] The reference signals described below in this embodiment include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DM-RS, CSI-RS, uplink reference signals, SRS, and / or uplink DM-RS. For example, downlink reference signals, synchronization signals, and / or SS / PBCH blocks may be referred to as reference signals. Reference signals used in the downlink include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DM-RS, CSI-RS, etc. Reference signals used in the uplink include uplink reference signals, SRS, and / or uplink DM-RS, etc.

[0067] Furthermore, the reference signal may be used for radio resource measurement (RRM). The reference signal may also be used for beam management.

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

[0069] The following procedures may be included as part of the process for configuring, setting up, or establishing a beam pair link: • Beam selection • Beam refinement • Beam recovery

[0070] For example, beam selection may be a procedure for selecting a beam in communication between base station equipment 3 and terminal equipment 1. Beam improvement may be a procedure for selecting a beam with higher gain, or for changing the optimal beam between base station equipment 3 and terminal equipment 1 by moving terminal equipment 1. Beam recovery may be a procedure for re-selecting a beam when the quality of the communication link deteriorates due to blockage caused by obstacles or the passage of people in communication between base station equipment 3 and terminal equipment 1.

[0071] Beam management may include beam selection and beam improvement. Beam recovery may include the following procedures: • Detection of beam failure • Discovery of a new beam • Sending a beam recovery request • Monitoring of responses to beam recovery requests

[0072] For example, when selecting the transmit beam of the base station device 3 in 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. Alternatively, the CSI-RS Resource Index (CRI) may be used as the report to the base station device 3, or an index indicated by a sequence of demodulation reference signals (DMRS) used for demodulating the PBCH and / or PBCH included in the SS / PBCH block may be used.

[0073] Furthermore, when the base station device 3 instructs the terminal device 1 to direct the beam, it specifies the CRI or SS / PBCH time index, and the terminal device 1 receives based on the specified CRI or SS / PBCH time index. At this time, the terminal device 1 may set a spatial filter based on the specified CRI or SS / PBCH time index and receive. Alternatively, the terminal device 1 may receive using the assumption of quasi-co-location (QCL). When one 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 one signal is associated with another signal.

[0074] Two antenna ports are said to be QCL (Quality Chain Relation) if the Long Term Property (LCL) of a channel carrying a symbol at one antenna port can be inferred from the channel carrying a symbol at the other antenna port. The Long Term Property of a channel includes one or more of the following: delay spread, Doppler spread, Doppler shift, mean gain, and mean delay. For example, if antenna port 1 and antenna port 2 are QCL with respect to mean delay, it means that the reception timing at antenna port 2 can be inferred from the reception timing at antenna port 1.

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

[0076] For example, if the reception spatial parameters between antenna port 1 and antenna port 2 can be considered QCL, it means that the reception beam receiving the signal from antenna port 2 can be inferred from the reception beam (reception spatial filter) receiving the signal from antenna port 1.

[0077] A combination of long-interval characteristics that can be considered as QCL types may be defined. For example, the following types may be defined: • Type A: Doppler shift, Doppler spread, mean delay, delay spread • Type B: Doppler shift, Doppler spread • Type C: mean delay, Doppler shift • Type D: Receive spatial parameters

[0078] The above-mentioned QCL types may be set and / or instructed as a Transmission Configuration Indication (TCI) that assumes a QCL with one or two reference signals in the RRC and / or MAC layer and / or DCI and PDCCH or PDSCH DMRS. For example, if one state of the TCI when terminal device 1 receives PDCCH is set and / or instructed to be SS / PBCH block index #2 and QCL type A + QCL type B, then when terminal device 1 receives PDCCH DMRS, it may receive the PDCCH DMRS by considering the Doppler shift, Doppler spread, mean delay, delay spread, received spatial parameters and channel long-interval characteristics in the reception of SS / PBCH block index #2, and perform synchronization and propagation path estimation. In this case, the reference signal indicated by the TCI (SS / PBCH block in the above example) may be called the source reference signal, and the reference signal affected by the long-interval characteristics inferred from the long-interval characteristics of the channel when receiving the source reference signal (PDCCH DMRS in the above example) may be called the target reference signal. Furthermore, the TCI may have one or more TCI states and a combination of the source reference signal and QCL type set for each state in the RRC, and this may be instructed to the terminal device 1 by the MAC layer or DCI.

[0079] In this method, the operation of the base station equipment 3 and terminal equipment 1, which are equivalent to beam management, may be defined by the assumption of the QCL of the spatial domain and radio resources (time and / or frequency) as beam management and beam direction / reporting.

[0080] The subframe will be described below. In this embodiment, it is referred to as a subframe, but it may also be referred to as a resource unit, wireless frame, time interval, time interval, etc.

[0081] Figure 3 shows an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention. Each wireless frame is 10 ms long. Each wireless frame consists of 10 subframes and W slots. Each slot consists of X OFDM symbols. That is, the length of one subframe is 1 ms. The time length of each slot is defined by the subcarrier interval. For example, if the subcarrier interval of OFDM symbols is 15 kHz and NCP (Normal Cyclic Prefix), then X = 7 or X = 14, which are 0.5 ms and 1 ms, respectively. If the subcarrier interval is 60 kHz, then X = 7 or X = 14, which are 0.125 ms and 0.25 ms, respectively. Also, for example, if X = 14, then W = 10 when the subcarrier interval is 15 kHz, and W = 40 when the subcarrier interval is 60 kHz. Figure 3 shows the case where X = 7 as an example. The same extension can be applied when X = 14. Furthermore, the uplink slots are defined similarly, and the downlink and uplink slots may be defined separately. Also, the bandwidth of the cells in Figure 3 may be defined as a Bandwidth Part (BWP). Additionally, a slot may be defined as a Transmission Time Interval (TTI). A slot does not necessarily have to be defined as a TTI. The TTI may also be the transmission period of a transport block.

[0082] Each signal or physical channel transmitted in each slot may be represented by a resource grid. The resource grid is defined by a numerology (subcarrier spacing and cyclic prefix length) and, for each carrier, by multiple subcarriers and multiple OFDM symbols. The number of subcarriers constituting a single slot depends on the bandwidth of the cell's downlink and uplink, respectively. Each element within the resource grid is referred to as a resource element. Resource elements may be identified by their subcarrier numbers and OFDM symbol numbers.

[0083] A resource grid is used to represent the mapping of resource elements in a physical downlink channel (such as a PDSCH) or uplink channel (such as a PUSCH). For example, if the subcarrier spacing is 15 kHz, the number of OFDM symbols X in a subframe is 14. 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 μ, which will be described later. In other words, a resource grid consists of (14 * 12 * Nmax, μ) resource elements. In the case of ECP (Extended CP), which is only supported at a subcarrier spacing of 60 kHz, one physical resource block is defined, for example, by 12 (number of OFDM symbols in one slot) * 4 (number of slots in one subframe) = 48 consecutive OFDM symbols in the time domain and 12 * Nmax, μ consecutive subcarriers in the frequency domain. In other words, the resource grid consists of (48 * 12 * Nmax, μ) resource elements.

[0084] Resource blocks are defined as reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks. One resource block is defined as 12 consecutive subcarriers in the frequency domain. Reference resource blocks are common to all subcarriers and may be configured with, for example, a subcarrier interval of 15 kHz and numbered in ascending order. Subcarrier index 0 at reference resource block index 0 may be called reference point A (point A) (or simply called "reference point"). Common resource blocks are resource blocks numbered in ascending order from 0 at each subcarrier interval setting μ from reference point A. The resource grid described above is defined by these common resource blocks. Physical resource blocks are resource blocks numbered in ascending order from 0 that are included in the bandwidth portion (BWP) described later. A physical uplink channel is first mapped to a virtual resource block. Then, the virtual resource block is mapped to a physical resource block. In the following, resource blocks may be virtual resource blocks, physical resource blocks, common resource blocks, or reference resource blocks.

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

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

[0087] Next, we will explain subframes, slots, and minislots. Figure 4 shows 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 interval, and a slot contains 7 or 14 OFDM symbols, with the slot length varying depending on the subcarrier interval. Here, when the subcarrier interval is 15 kHz, one subframe contains 14 OFDM symbols. Downlink slots may be referred to as PDSCH mapping type A. Uplink slots may be referred to as PUSCH mapping type A.

[0088] A mini-slot (which may also be called a sub-slot) is a time unit consisting of fewer OFDM symbols than the number of OFDM symbols contained in a slot. The figure shows an example where a mini-slot consists of two OFDM symbols. The OFDM symbols in a mini-slot may coincide with the timing of the OFDM symbols that make up the slot. The smallest unit of scheduling may be a slot or a mini-slot. Assigning a mini-slot may also be called non-slot-based scheduling. Scheduling a mini-slot may also be described as scheduling a resource where the relative time position of the reference signal and the start position of the data is fixed. Downlink mini-slots may be called PDSCH mapping type B. Uplink mini-slots may be called PUSCH mapping type B.

[0089] Figure 5 shows an example of a slot format. Here, the case where the subcarrier spacing is 15 kHz and the slot length is 1 ms is shown as an example. In the figure, D represents the downlink and U represents 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), one or more of the following may be included: downlink symbols, flexible symbols, and uplink symbols. The ratio of these may be predetermined as the slot format. It may also be defined by the number of downlink OFDM symbols included in the slot or by the start and end positions within the slot. It may also be defined by the number of uplink OFDM symbols or DFT-S-OFDM symbols included in the slot or by the start and end positions within the slot. Scheduling a slot may be expressed as scheduling a resource where the relative time position of the reference signal and the slot boundary is fixed.

[0090] Terminal device 1 may receive downlink signals or downlink channels using downlink symbols or flexible symbols. Terminal device 1 may transmit uplink signals or downlink channels using uplink symbols or flexible symbols.

[0091] Figure 5(a) shows an example where a certain time interval (for example, the smallest unit of time resources that can be allocated to 1UE, or may also be called a time unit; multiple smallest units of time resources may also be bundled together and referred to as a time unit) is entirely used for downlink transmission. Figure 5(b) shows that the first time resource is used for scheduling the uplink, for example via PDCCH, and the uplink signal is transmitted via flexible symbols including the processing delay of PDCCH, the downlink-to-uplink switching time, and the generation of the transmit signal. Figure 5(c) shows that the first time resource is used for transmitting PDCCH and / or downlink PDSCH, and is used for transmitting PUSCH or PUCCH via the processing delay, the downlink-to-uplink switching time, and a gap for generating the transmit signal. Here, as an example, the uplink signal may be used for transmitting HARQ-ACK and / or CSI, i.e., UCI. Figure 5(d) shows the initial time resources used for transmitting PDCCH and / or PDSCH, and then, after processing delays, downlink-to-uplink switching time, and a gap for generating the transmit signal, used for transmitting PUSCH and / or PUCCH on the uplink. Here, for example, the uplink signal may be used for transmitting uplink data, i.e., UL-SCH. Figure 5(e) shows an example where everything is used for uplink transmission (PUSCH or PUCCH).

[0092] The aforementioned downlink and uplink parts may be composed of multiple OFDM symbols, similar to LTE.

[0093] Figure 6 shows an example of beamforming. Multiple antenna elements are connected to a single transceiver unit (TXRU) 50, and the phase is controlled by a phase shifter 51 for each antenna element. By transmitting from the antenna element 52, the beam can be directed in any direction relative to the transmitted signal. 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 any direction by controlling the phase shifter 51, the base station device 3 can communicate with the terminal device 1 using a high-gain beam.

[0094] The Bandwidth part (BWP) is described below. The BWP is also called the Carrier BWP. BWPs may be set for both the downlink and uplink. A BWP is defined as a set of consecutive physical resources selected from a consecutive subset of common resource blocks. Terminal device 1 may be configured with up to four BWPs, each with one downlink carrier BWP (DL BWP) activated at a given time. Terminal device 1 may be configured with up to four BWPs, each with one uplink carrier BWP (UL BWP) activated at a given time. In the case of carrier aggregation, BWPs may be set in each serving cell. In this case, having one BWP set in a serving cell may be expressed as "no BWP set." Also, having two or more BWPs set may be expressed as "BWP set."

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

[0096] <RRC Operation> The BWP information element (IE) contained in RRC messages (system information to be broadcast and information sent in dedicated RRC messages) is used to configure the BWP. RRC messages transmitted from base station equipment 3 are received by terminal equipment 1. For each serving cell, the network (base station equipment 3, etc.) configures terminal equipment 1 with at least an initial BWP, which includes at least a downlink BWP and one (if the serving cell is configured for an uplink, for example) or two (if a supplementary uplink is used, for example) uplink BWPs. Furthermore, the network may configure additional uplink BWPs and downlink BWPs for a serving cell. BWP configuration is divided into uplink parameters and downlink parameters. BWP configuration is also divided into common parameters and dedicated parameters. Common parameters (such as BWP uplink common IE and BWP downlink common IE) are cell-specific. The common parameters for the primary cell's initial BWP are also provided in the system information. For all other serving cells, the network provides common parameters via dedicated signals. BWPs are identified by their BWP ID. The initial BWP has a BWP ID of 0. Other BWPs have BWP IDs ranging from 1 to 4.

[0097] The initial DL BWP may be defined by the PRB location and the number of consecutive PRBs for the control resource set (CORESET) for the type 0 PDCCH common search space, the subcarrier spacing, and the cyclic prefix. That is, the initial DL BWP may be set by pdccch-ConfigSIB1 included in the MIB or by PDCCCH-ConfigCommon included in ServingCellConfigCommon. The information element ServingCellConfigCommon is used to set the cell-specific parameters of the serving cell for the terminal device 1. In this case, the size of the initial DL BWP is N ｓｉｚｅ ＢＷＰ、０ is. N ｓｉｚｅ ＢＷＰ、０ is the number of resource blocks indicating the bandwidth of the initial DL BWP. Here, the initial DL BWP is an initial DL BWP of size N ｓｉｚｅ ＢＷＰ、０ is.

[0098] Also, for the terminal device 1, the initial DL BWP may be provided by SIB1 (systemInformationBlockType1) or ServingCellConfigCommon (for example, ServingCellConfigCommonSIB). The information element ServingCellConfigCommonSIB is used to set the cell-specific parameters of the serving cell for the terminal device 1 within SIB1. In this case, the size of the initial DL BWP is N ｓｉｚｅ ＢＷＰ、１ is. N ｓｉｚｅ ＢＷＰ、１ is N ｓｉｚｅ ＢＷＰ、０ may be equal to 。 N ｓｉｚｅ ＢＷＰ、１ is N ｓｉｚｅ ＢＷＰ、０ may be different from. Here, the initial DL BWP is an initial DL BWP of size N ｓｉｚｅ ＢＷＰ、１ is.

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

[0100] In this embodiment, unless otherwise specified, the initial DL BWP is N ｓｉｚｅ ＢＷＰ、０ The initial download may be BWP, or N ｓｉｚｅ ＢＷＰ、１ The initial download can be BWP.

[0101] Terminal device 1 may be configured with one primary cell and up to 15 secondary cells.

[0102] Figure 14 is a flowchart showing an example of a random access procedure for MAC entities according to this embodiment.

[0103] <Starting the Random Access Procedure (S1001)> In Figure 14, S1001 is the procedure for initializing the random access procedure. 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 SCell is initiated only by a PDCCH order that includes a ra-PreambleIndex that is not set to 0b000000.

[0104] In S1001, terminal device 1 receives random access configuration information via a higher layer before initiating the random access procedure. This random access configuration 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 available for transmitting a random access preamble (also called a random access channel opportunity (occasion), PRACH occasion, or RACH opportunity) - preambleReceivedTargetPower: The initial power of the preamble (may be the target received power) - rsrp-ThresholdSSB: A threshold of reference signal received power (RSRP) for selecting an SS / PBCH block (which may be the associated random access preamble and / or PRACH opportunity) - rsrp-ThresholdCSI-RS: A threshold of reference signal received power (RSRP) for selecting a CSI-RS (which may be the associated random access preamble and / or PRACH opportunity) - rsrp-ThresholdSSB-SUL: NUL (Normal Reference signal received power (RSRP) threshold for selecting between Uplink carriers and SUL (Supplementary Uplink) carriers. Power Control Offset: Power offset between rsrp-Threshold SSB and rsrp-Threshold CSI-RS when a random access procedure is initiated for beam failure recovery. Power Ramping Step: Power ramping step (power ramping factor).The following indicates the steps of transmit power ramped up based on the preamble transmit counter PREAMBLE_TRANSMISSION_COUNTER: ra-PreambleIndex: One or more available random access preambles or one or more available random access preambles in the group of random access preambles ra-ssb-OccasionMaskIndex: Information for determining the PRACH opportunities assigned to the SS / PBCH block on which a MAC entity transmits a random access preamble ra-OccasionList: Information for determining the PRACH opportunities assigned to the CSI-RS on which a MAC entity may transmit a random access preamble preamble preamTransMax: The maximum number of preamble transmissions ssb-perRACH-OccasionAndCB-PreamblesPerSSB(SpCell : parameters 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 random access preamble format - PREAMBLE_POWER_RAMPING_COUNTER: Preamble power ramping counter - PREAMBLE_RECEIVED_TARGET_POWER: Initial random access preamble power. Indicates the initial transmit power for random access preamble transmission. - PREAMBLE_BACKOFF: Used to adjust the timing of random access preamble transmission.

[0105] When a random access procedure is initiated to 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 0ms. If the carrier to be used for the random access procedure is explicitly notified, the MAC entity selects the notified carrier for the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the notified carrier. The MAC entity selects the SUL carrier for performing the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the SUL carrier if the carrier to be used for the random access procedure is not explicitly notified, the SUL carrier is configured for the serving cell, and the RSRP of the downlink path loss reference is less than rsrp-ThresholdSSB-SUL. Otherwise, the MAC entity selects the NUL carrier for performing the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the NUL carrier.

[0106] <Start of Random Access Procedure (S1002)> S1002 is the random access resource selection procedure. The procedure for selecting random access resources (including time / frequency resources and / or preamble indexes) in the MAC layer of terminal device 1 will be described below.

[0107] Terminal device 1 sets a value for the preamble index (which may be called PREAMBLE_INDEX) of the random access preamble to be transmitted using the following procedure.

[0108] Terminal device 1 (MAC entity) selects an SS / PBCH block or CSI-RS whose RSRP exceeds a predetermined threshold if (1) a random access procedure is initiated by notification of a beam failure from a lower layer, (2) a random access resource (which may be a PRACH opportunity) for non-contest-based random access for a beam failure recovery request associated with an SS / PBCH block (also referred to as an SSB) or CSI-RS is provided by 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 as the preamble index (PREAMBLE_INDEX). Otherwise, the MAC entity sets the ra-PreambleIndex associated with the selected SS / PBCH block or CSI-RS into the preamble index.

[0109] Terminal device 1 sets the signaled ra-PreambleIndex to the preamble index if (1) a ra-PreambleIndex is provided in the PDCCH or RRC, (2) the value of the ra-PreambleIndex is not a value that indicates a conflict-based random access procedure (e.g., 0b000000), and (3) no random access resource for non-conflict-based random access is associated with the SS / PBCH block or CSI-RS in the RRC. 0bxxxxxxx represents the bit sequence located in the 6-bit information field.

[0110] Terminal device 1, when (1) a random access resource for non-contradiction-based random access associated with an SS / PBCH block is provided from RRC, and (2) one or more SS / PBCH blocks among the associated SS / PBCH blocks are available in which the RSRP exceeds a predetermined threshold, selects one of the SS / PBCH blocks in which the RSRP exceeds the predetermined threshold, and sets the ra-PreambleIndex associated with the selected SS / PBCH block as the preamble index.

[0111] Terminal device 1, when (1) a random access resource for non-competition-based random access is associated with a CSI-RS in RRC, and (2) one or more CSI-RSs are available among the associated CSI-RSs in which the RSRP exceeds a predetermined threshold, selects one of the CSI-RSs in which the RSRP exceeds the predetermined threshold, and sets the ra-PreambleIndex associated with the selected CSI-RS as the preamble index.

[0112] If none of the above conditions are met, terminal device 1 performs a competition-based random access procedure. In the competition-based random access procedure, terminal device 1 selects an SS / PBCH block with an RSRP exceeding a set threshold and selects a preamble group. If a relationship between an SS / PBCH block and a random access preamble is set, terminal device 1 randomly selects a 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 as the preamble index.

[0113] If a MAC entity selects an SS / PBCH block and an association between a PRACH opportunity and an SS / PBCH block is established, it may determine the next available PRACH opportunity from among those associated with the selected SS / PBCH block. However, if terminal device 1 selects a CSI-RS and an association between a PRACH opportunity and a CSI-RS is established, it may determine the next available PRACH opportunity from among those associated with the selected CSI-RS.

[0114] Available PRACH opportunities may be identified based on mask index information, SSB index information, resource settings configured by RRC parameters, and / or selected reference signals (SS / PBCH blocks or CSI-RS). Resource settings configured by RRC parameters include resource settings per SS / PBCH block and / or resource settings per CSI-RS.

[0115] The base station device 3 may transmit resource settings for each SS / PBCH block and / or resource settings for each CSI-RS in an RRC message to the terminal device 1. The terminal device 1 receives resource settings for each SS / PBCH block and / or resource settings for each CSI-RS from the base station device 3 in 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 obtains 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 certain conditions. The terminal device 1 may identify the next available PRACH opportunity based on the mask index information, SSB index information, resource settings set by the RRC parameters, and the selected reference signal (SS / PBCH block or CSI-RS). The MAC entity of terminal device 1 may instruct the physical layer to send a random access preamble using the selected PRACH opportunity.

[0116] Mask index information indicates an index of PRACH opportunities available for sending random access preambles. Mask index information may also indicate some PRACH opportunities within a group of one or more PRACH opportunities defined in the prach-ConfigurationIndex. Alternatively, mask index information may indicate some PRACH opportunities within a group of PRACH opportunities to which a specific SSB index identified in the SSB index information is mapped.

[0117] The SSB index information is information indicating the SSB index corresponding to one or more SS / PBCH blocks transmitted by the base station device 3. Upon receiving message 0, the terminal device 1 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 setting index, the upper layer parameter SB-perRACH-Occasion, and the upper layer parameter cb-preamblePerSSB.

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

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

[0120] Next, the MAC entity calculates the RA-RNTI associated with the PRACH opportunity in which a random access preamble is transmitted, except in cases of a non-contradiction-based random access preamble for beam failure recovery requests. The RA-RNTI is calculated as 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 transmitted PRACH 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 a NUL carrier is 0, and the ul_carrier_id for a SUL carrier is 1.

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

[0122] <Reception of Random Access Response (S1004)> S1004 is the procedure for receiving a random access response. Once a random access preamble is sent, the MAC entity performs the following actions regardless of the possible occurrence of measurement gaps. Here, the random access response may be a MAC PDU for random access response.

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

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

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

[0126] In S1004, if the MAC entity has sent a non-conflict-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. While the random access response window is running, the MAC entity monitors the PDCCH of the SpCell identified by 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 ra-ResponseWindow, which is 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 ra-ResponseWindow, which is included in the higher-layer parameter RACH-ConfigCommon. Then, while the random access response window is running, the MAC entity monitors the PDCCH of the SpCell identified by RA-RNTI for random access response. Here, the information element BeamFailureRecoveryConfig is used to configure RACH resources and candidate beams for beam failure recovery for terminal device 1 in the event of beam failure detection. The information element RACH-ConfigCommon is used to specify cell-specific random access parameters.

[0127] A MAC entity may consider a random access procedure to have been successfully completed if (1) it receives notification of receipt of a PDCCH transmission from a lower layer, (2) the PDCCH transmission is scrambled by C-RNTI, and (3) the MAC entity sends a non-conflict-based random access preamble for a beam failure recovery request.

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

[0129] The MAC entity sets PREAMBLE_BACKOFF to the value of the BI field contained in the MAC subPDU if the random access response contains a MAC subPDU that includes a BackoffIndicator. Otherwise, the MAC entity sets PREAMBLE_BACKOFF to 0ms.

[0130] A MAC entity may consider the receipt of a random access response to have been successful if it contains a MAC subPDU that includes a random access preamble identifier corresponding to the PREAMBLE_INDEX from which the random access response was sent.

[0131] (1) If the reception of the random access response is deemed successful, and (2) the random access response contains a MAC subPDU containing only RAPID, the MAC entity deems the random access procedure to have been successfully completed and indicates to the upper layer that an acknowledgment has been received for the symptom information request (SI request). If condition (2) is not met, the MAC entity applies the following action A to the serving cell to which the random access preamble is sent.

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

[0133] If the serving cell for a random access procedure is an SCell for SRS only, the MAC entity may ignore the received UL grant. Otherwise, the MAC entity processes the value of the received UL grant and presents it to the lower layer.

[0134] If the random access preamble is not selected by the MAC entity from the range of conflict-based random access preambles, the MAC entity may consider the random access procedure to have completed successfully.

[0135] <End of Operation A> If the random access preamble is selected by the MAC entity from the range of conflict-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. Subsequently, if 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 has been made to the CCCH logical channel, and then obtains a MAC PDU for transmission from the predetermined entity (Multiplexing and assembly entity) and stores the obtained MAC PDU in the Msg3 buffer. If a transmission is made to 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.

[0136] The MAC entity considers that the random access response has not been successfully received if at least one of the following conditions (3) or (4) is met, and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by one. The MAC entity indicates a random access problem to the upper layer when the value of the preamble transmission counter reaches a predetermined value (maximum number of preamble transmissions + 1) and a random access preamble is sent by SpCell. If a random access procedure is initiated for an SI request, the MAC entity considers that the random access procedure has not been successfully completed.

[0137] The MAC entity considers a random access procedure to have not completed successfully if the value of the preamble transmission counter reaches a predetermined value (maximum number of preamble transmissions + 1) and the random access preamble is transmitted via SCell.

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

[0139] 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 in the random access procedure has been selected by the MAC itself from a range of conflict-based random access preambles, delays the transmission of the next random access preamble by the selected backoff time, and then executes S1002. If the random access procedure is not completed, the MAC entity executes S1002 if the random access preamble in the random access procedure has not been selected by the MAC itself from a range of conflict-based random access preambles.

[0140] The MAC entity may stop the random access response window once it has successfully received a random access response containing a random access preamble identifier that matches the transmitted preamble index.

[0141] Terminal device 1 sends message 3 via PUSCH based on UL grant.

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

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

[0144] If the MAC entity receives notification of a PDCCH transmission from a lower layer and C-RNTI MAC CE is included in Msg3, the MAC entity considers the conflict resolution to be successful if at least one of the following conditions (5) to (7) is met, stops the conflict resolution timer, discards TEMPORARY_C-RNTI, and considers the random access procedure to have completed successfully.

[0145] 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 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 PDCCH order, and the PDCCH transmission is scrambled by C-RNTI. Condition (7) is that the random access procedure is initiated for beam failure recovery, and the PDCCH transmission is scrambled by C-RNTI.

[0146] If the 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. Subsequently, if the successfully decoded MAC PDU contains a UE contention resolution identity (UE contention resolution identity) MAC CE, and the UE contention resolution identity within the MAC CE matches the CCCH SDU transmitted in Msg3, the MAC entity considers the collision resolution to be successful and terminates the disassembly and demultiplexing of the MAC PDU. Then, if a random access procedure is initiated for an SI request, the MAC entity indicates to the upper layer that it has received an acknowledgment for the SI request. If the random access procedure is not initiated for the SI request, the MAC entity sets C-RNTI to the value of TEMPORARY_C-RNTI. Subsequently, the MAC entity discards TEMPORARY_C-RNTI and considers the random access procedure to have completed successfully.

[0147] If the MAC entity's UE conflict resolution identity within the MAC CE does not match the CCCH SDU sent in Msg3, it discards TEMPORARY_C-RNTI, considers the conflict resolution unsuccessful, and discards the successfully decoded MAC PDU.

[0148] The MAC entity discards TEMPORARY_C-RNTI when the conflict resolution timer expires, and considers the conflict resolution unsuccessful. If the MAC entity considers the conflict resolution unsuccessful, it flushes the HARQ buffer used to send the MAC PDU in the Msg3 buffer and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by one. When the value of the preamble transmission counter reaches a predetermined value (maximum number of preamble transmissions + 1), the MAC entity indicates a random access problem to the higher layer. If a random access procedure is then initiated for an SI request, the MAC entity considers the random access procedure not to have completed successfully.

[0149] If the random access procedure is not complete, 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.

[0150] Once the random access procedure is complete, the MAC entity discards any explicitly signaled non-conflict-based random access resources for non-conflict-based random access procedures other than the non-conflict-based random access procedure for beam failure recovery requests, and flushes the HARQ buffer used to send the MAC PDU in the Msg3 buffer.

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

[0152] A Control Resource Set (CORESET) is a time and frequency resource for searching downlink control information. CORESET configuration information includes a CORESET identifier (ControlResourceSetId, CORESET-ID) and information identifying the CORESET's frequency resource. The information element ControlResourceSetId (CORESET identifier) ​​is used to identify the Control Resource Set in a given serving cell. CORESET identifiers are used across BWPs in a given serving cell. CORESET identifiers are unique across BWPs in a serving cell. The number of CORESETs in each BWP is limited to three, including the initial CORESET. In a given serving cell, the CORESET identifier can take values ​​from 0 to 11.

[0153] The control resource set identified by CORESET identifier 0 (ControlResourceSetId 0) is referred to as CORESET#0. CORESET#0 may be configured by pdcch-ConfigSIB1 included in the MIB, or by PDCCH-ConfigCommon included in ServingCellConfigCommon. That is, the configuration information for CORESET#0 may be pdcch-ConfigSIB1 included in the MIB, or by PDCCH-ConfigCommon included in ServingCellConfigCommon. The configuration information for CORESET#0 may also be set by controlResourceSetZero, which is included in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon. In other words, the information element controlResourceSetZero is used to indicate the initial DL BWP's CORESET#0 (common CORESET). The CORESET indicated in pdcch-ConfigSIB1 is CORESET#0. The information element pdcch-ConfigSIB1 in the MIB or dedicated configuration is used to configure the initial DL BWP. The CORESET configuration information pdcch-ConfigSIB1 for CORESET#0 does not explicitly identify the CORESET identifier and the CORESET's frequency resources (e.g., the number of continuous resource blocks) and time resources (e.g., the number of continuous symbols). However, the CORESET's frequency resources (e.g., the number of continuous resource blocks) and time resources (e.g., the number of continuous symbols) for CORESET#0 can be implicitly identified by the information contained 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 during handover and when adding PSCell and / or SCell. The configuration information for CORESET#0 is included in the initial BWP configuration.In other words, the configuration information for CORESET#0 does not need to be included in the configuration of BWPs other than the initial BWP. controlResourceSetZero corresponds to 4 bits of pdcch-ConfigSIB1 (e.g., 4 MSB bits and 4 most significant bits). CORESET#0 is the control resource set for the type 0 PDCCH common search space.

[0154] The configuration information for additional common CORESETs may be set by commonControlResourceSet included in PDCCH-ConfigCommon. The configuration information for additional common CORESETs may be used to specify additional common CORESETs used in random access procedures. The configuration information for additional common CORESETs may be included in the configuration of each BWP. The CORESET identifier shown in commonControlResourceSet takes a non-zero value.

[0155] The common CORESET may be a CORESET used in a random access procedure (for example, an additional common CORESET). In this embodiment, the common CORESET may also include CORESETs configured with CORESET #0 and / or additional common CORESET configuration information. In other words, the common CORESET may include CORESET #0 and / or additional common CORESETs. CORESET #0 may also be referred to as common CORESET #0. Terminal device 1 and BWPs other than the BWP in which the common CORESET is configured may also refer to (obtain) the common CORESET configuration information.

[0156] The configuration information for 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 given BWP. PDCCH-Config may be included within the configuration of each BWP.

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

[0158] A search space is defined for searching for PDCCH candidates. The searchSpaceType included in the search space configuration information 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 C-RNTI value set by 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 shared among multiple terminal devices 1 and consists of a predetermined index of CCEs (Control Channel Elements). A CCE consists of multiple resource elements. The search space configuration information includes information on the DCI format monitored in the search space.

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

[0160] As mentioned above, the configuration information for CORESET#0 is included in the initial DL BWP configuration. The configuration information for CORESET#0 does not need to be included in the configuration of BWPs other than the initial DL BWP (additional BWPs). If a BWP other than the initial DL BWP (additional BWP) refers to the configuration information for CORESET#0 (refer, acquire, etc.), it may be necessary to at least satisfy the conditions that CORESET#0 and the SS block are included in the additional BWP in the frequency domain and that the same subcarrier spacing is used. In other words, if a BWP other than the initial BWP (additional BWP) refers to the configuration information for CORESET#0 (refer, acquire, etc.), it may be necessary to at least satisfy the conditions that the bandwidth and SS block of the initial DL BWP are included in the additional BWP in the frequency domain and that the same subcarrier spacing is used. At this time, the search space (e.g., ra-SearchSpace) set for the additional BWP can refer to the CORESET#0 configuration information (refer, acquire, etc.) by indicating identifier 0 of CORESET#0. Furthermore, if the bandwidth of the initial DL BWP is included in the additional DL BWP, and the SS block is included in the additional DL BWP, and the same subcarrier spacing is used, none of the above conditions are met, the terminal device 1 does not need to expect the additional DL BWP to refer to the CORESET#0 configuration information. In other words, in this case, the base station device 3 does not need to configure the terminal device 1 to refer to the CORESET#0 configuration information for the additional DL BWP. Here, the initial DL BWP is size N. ｓｉｚｅ ＢＷＰ、０ The initial download can be BWP.

[0161] When an additional DL BWP refers to (refers, acquires, etc.) the CORESET configuration information of another BWP, it may be necessary to satisfy at least the following conditions: in the frequency domain, the CORESET (or the bandwidth of that BWP) and / or the SS blocks that that BWP contains (are associated with) are included in the additional BWP, and the same subcarrier spacing is used. In other words, if any of the following conditions are not met in the frequency domain—that the CORESET (or the bandwidth of that BWP) is included in the additional DL BWP, and the SS blocks that that BWP contains (are associated with) are included in the additional DL BWP, and the same subcarrier spacing is used—the terminal device 1 does not need to expect the additional DL BWP to refer to the CORESET configuration information set for that BWP.

[0162] Terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs located in each active serving cell configured to monitor PDCCH. A 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 being monitored. The set of PDCCH candidates monitored by terminal device 1 is defined by PDCCH search space sets. A search space set is either 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 as a common search space, and a UE-specific search space set as a UE-specific search space. Terminal device 1 monitors PDCCH candidates in one or more of the following search space sets. - Type0-PDCCH common search space set: This search space set is configured by the higher-level parameter, searchSpaceZero, indicated by MIB, or searchSpaceSIB1, indicated by PDCCH-ConfigCommon. This search space is for monitoring the DCI format of CRC scrambled with SI-RNRI in the primary cell. - Type0A-PDCCH common search space set: This search space set is configured by the higher-level parameter, searchSpaceOSI, indicated by PDCCH-ConfigCommon. This search space is for monitoring the DCI format of CRC scrambled with SI-RNRI in the primary cell.- Type 1 PDCCH common search space set: This search space set is configured by the search space for random access procedures (ra-SearchSpace), which is a higher-level parameter indicated by PDCCH-ConfigCommon. This search space is for monitoring the DCI format of CRCs scrambled with RA-RNRI or TC-RNTI in the primary cell. The Type 1 PDCCH common search space set is a search space set for random access procedures. - Type 2 PDCCH common search space set: This search space set is configured by the search space for paging procedures (pagingSearchSpace), which is a higher-level parameter indicated by PDCCH-ConfigCommon. This search space is for monitoring the DCI format of CRCs scrambled with P-RNTI in the primary cell. - Type 3-PDCCH common search space set: This search space set is defined by a common search space (SearchSpace) with a higher-level parameter, PDCCH-Config, which indicates the search space type. This search space is for monitoring the DCI format of CRC scrambled with INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI. For primary liecels, it is for monitoring the DCI format of CRC scrambled with C-RNTI or CS-RNTI(s).- UE-specific search space set: This search space set is configured by a UE-specific search space (SearchSpace) whose search space type is indicated by the higher-level parameter PDCCH-Config. This search space is for monitoring the DCI format of CRC scrambled with C-RNTI or CS-RNTI(s).

[0163] If terminal device 1 is provided with one or more search space sets by corresponding higher-level parameters (such as searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace), and terminal device 1 is provided with C-RNTI or CS-RNTI, terminal device 1 may monitor PDCCH candidates for DCI format 0_0 and DCI format 1_0 that have C-RNTI or CS-RNTI in its one or more search space sets.

[0164] BWP configuration information is divided into DL BWP configuration information and UL BWP configuration information. BWP configuration information includes the 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 given serving cell. The BWP identifier included in the UL BWP configuration information is used to identify (reference) the UL BWP in a given serving cell. BWP identifiers are assigned to both DL BWP and UL BWP. For example, the BWP identifier corresponding to a DL BWP may be called the DL BWP index. The BWP identifier corresponding to a UL BWP may be called the UL BWP index. The initial DL BWP is referenced by DL BWP identifier 0. The initial UL BWP is referenced by the UL BWP identifier 0. Each of the other DL BWPs or other UL BWPs may be referenced by BWP identifiers from 1 to maxNrofBWPs. In other words, the 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 identifier values ​​for other BWPs can take values ​​from 1 to 4. Configuration information for other higher layers is associated with a specific BWP using the BWP identifier. The fact that a DL BWP and an UL BWP have the same BWP identifier may mean that the DL BWP and the UL BWP are paired.

[0165] Figure 7 shows an example of BWP settings according to an embodiment of the present invention.

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

[0167] In Figure 7, in a serving cell, one initial BWP (BWP#0) and two additional BWPs (BWP#1 and BWP#2) are configured for terminal device 1. 801 is the initial DL BWP (DL BWP#0). 802 is the initial UL BWP (UL BWP#0). 805 is the additional DL BWP (DL BWP#1). 806 is the additional UL BWP (UL BWP#1). 808 is the additional DL BWP (DL BWP#2). 809 is the additional UL BWP (UL BWP#2). Hereafter, we will assume 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 called the active DL BWP (currently active DL BWP). The activated initial UL BWP#0 may be called the initial active UL BWP (initial active UL BWP). Terminal device 1 performs downlink reception with the active DL BWP#1 and uplink transmission with the initial active UL BWP.

[0168] 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 an additional BWP #1. 810 is a CORESET configured for an additional BWP #2. 807 and 810 may also be called UE-specific CORESETs (UE specifically configured Control Resource Sets). As mentioned above, the configuration information for CORESET #0 (803) may be configured by pdcch-ConfigSIB1 or PDCCH-ConfigCommon. The configuration information for the additional common CORESET (804) may be configured by commonControlResourceSet included in PDCCH-ConfigCommon. The CORESET (807 and 810) configuration information may be set by controlResourceSetToAddModList included in PDCCH-Config. The CORESET identifier value for 803 is given as 0. The CORESET identifier value for 804 may be given as 1. The CORESET identifier value for 807 may be given as 3. The CORESET identifier value for 810 may be given as 6. For DL ​​BWP#0, the CORESET identifier value included in ra-searchspace is set to 1, and for DL ​​BWP#2, the CORESET identifier value included in ra-searchspace is set to 6.

[0169] In Figure 7, ra-searchspace is configured for DL ​​BWP#0, DL BWP#1, and DL BWP#2, respectively. As mentioned above, the search space configuration information for the random access procedure may be configured by ra-SearchSpace. As a first example, the CORESET identifier included in the ra-searchspace configured for a DL BWP may be set to the value of the CORESET identifier that identifies the CORESET configuration information configured for that DL BWP, or it may be set to the value of the CORESET identifier included in the ra-SearchSpace configured for the initial BWP. That is, the ra-searchspace set for a certain DL BWP may indicate a CORESET identifier that identifies the CORESET setting information set for that DL BWP, or it may indicate a CORESET identifier included in the ra-searchspace set for the initial BWP. In other words, the ra-searchspace set for a certain DL BWP does not need to indicate the identifiers of common and UE-specific CORESETs set for DL ​​BWPs other than that DL BWP and the initial DL BWP. To put it another way, the base station device 3 may send an RRC message such that the ra-searchspace set for a certain DL BWP does not indicate the identifiers of common and UE-specific CORESETs set for DL ​​BWPs other than that DL BWP and the initial DL BWP. For example, the identifier value of the CORESET contained in ra-searchspace for DL ​​BWP#1 may be set to 1 or to 3. The identifier value of the CORESET contained in ra-searchspace for DL ​​BWP#1 is not set to 6. If the identifier value of the CORESET contained in ra-searchspace for DL ​​BWP#1 is set to 1, the terminal device 1 monitors the DCI format contained in the ra-searchspace with the active DL BWP#1 based on the setting information of CORESET#1 (804) identified by the CORESET identifier 1.If the identifier value of the CORESET included in ra-searchspace for DL ​​BWP#1 is set to 3, terminal device 1 monitors the DCI format included in the ra-searchspace on 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 certain DL BWP may indicate a CORESET identifier that identifies the configuration information of the common CORESET. For example, the identifier value of the CORESET included in ra-searchspace for DL ​​BWP#1 may be set to 1. That is, if CORESET#1 is set for the initial DL BWP, CORESET#0 cannot be called as ra-searchspace. If CORESET#1 is not set in the initial DL BWP, CORESET#0 can be called as ra-searchspace. However, as an extension of the first example, even if CORESET#1 is set in the initial DL BWP, CORESET#0 can be called as ra-searchspace by the DL BWP.

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

[0171] As a third example, the CORESET identifier included in the ra-searchspace set for a certain DL BWP may be set to the value of the identifiers of all common CORESETs set in terminal device 1. That is, the ra-searchspace set for a certain DL BWP may indicate the CORESET identifier that identifies the setting information of all common CORESETs set in that serving cell. 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.

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

[0173] The random access procedure of this embodiment will now be described. Random access procedures are classified into two types: contention-based (CB) and non-contention-based (non-CB) (or contention-free (CF)). Contention-based random access is also called CBRA, and non-contention-based random access is also called CFRA.

[0174] The random access procedure may include (i) sending a random access preamble (message 1, Msg1) in PRACH, (ii) receiving a random access response (RAR) message (message 2, Msg2) with PDCCH / PDSCH, and, where applicable, (iii) sending message 3PUSCH (Msg3PUSCH), and (iv) receiving PDSCH for collision resolution.

[0175] A competition-based random access procedure is initiated by a PDCCH order, MAC entity, beam failure notification from a lower layer, or RRC, etc. When a beam failure notification is provided to the MAC entity of terminal device 1 from the physical layer of terminal device 1, and certain conditions are met, the MAC entity of terminal device 1 initiates the random access procedure. The procedure that determines whether certain conditions are met when a beam failure notification is provided to the MAC entity of terminal device 1 from the physical layer of terminal device 1, and initiates the random access procedure, may be called a beam failure recovery procedure. This random access procedure is a random access procedure for a beam failure recovery request. Random access procedures initiated by the MAC entity include random access procedures initiated by scheduling request procedures. A random access procedure for a beam failure recovery request may or may not be considered 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 a scheduling request procedure, it may be necessary to distinguish between the random access procedure for a beam failure recovery request and the scheduling request procedure. Random access procedures for beam failure recovery requests and scheduling request procedures may be random access procedures initiated by the MAC entity. In one embodiment, a random access procedure initiated by a scheduling request procedure may be referred to as a random access procedure initiated by the MAC entity, and a random access procedure for beam failure recovery requests may be referred to as a random access procedure triggered by beam failure notification from a lower layer. Hereinafter, the initiation of a random access procedure upon receiving beam failure notification from a lower layer may mean the initiation of a random access procedure for beam failure recovery requests.

[0176] Terminal device 1 performs a competition-based random access procedure during initial access from a state where it is not connected (communicating) with base station device 3, and / or during scheduling requests when uplink data or sidelink data that can be transmitted to terminal device 1 becomes available while connected to base station device 3. However, the uses of competition-based random access are not limited to these.

[0177] The occurrence of uplink data that can be transmitted to terminal device 1 may include the triggering of a buffer status report corresponding to the transmittable uplink data. The occurrence of uplink data that can be transmitted to terminal device 1 may also include the pending status of scheduling requests triggered based on the occurrence of transmittable uplink data.

[0178] The occurrence of sidelink data that can be transmitted to terminal device 1 may include the triggering of a buffer status report corresponding to the transmittable sidelink data. The occurrence of sidelink data that can be transmitted to terminal device 1 may also include the pending status of scheduling requests triggered based on the occurrence of transmittable sidelink data.

[0179] A non-contradiction-based random access procedure may be initiated when terminal device 1 receives information from base station device 3 instructing it to start a random access procedure. A non-contradiction-based random access procedure may also be initiated when the MAC layer of terminal device 1 receives notification of a beam failure from a lower layer.

[0180] Non-contradiction-based random access may be used to quickly synchronize the uplink between terminal device 1 and base station device 3 when base station device 3 and terminal device 1 are connected but handover or the transmission timing of the mobile station device is not valid. Non-contradiction-based random access may also be used to send a beam failure recovery request when a beam failure occurs in terminal device 1. However, the applications of non-contradiction-based random access are not limited to these.

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

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

[0183] However, the random access settings information may include information common to all cells, or it may include dedicated information that differs for each terminal device.

[0184] However, some random access configuration information may be associated with all SS / PBCH blocks in an SS burst set. However, some random access configuration information may be associated with all of the configured CSI-RSs. However, some random access configuration information may be associated with a single downlink transmit beam (or beam index).

[0185] However, some random access configuration information may be associated with one SS / PBCH block in an SS burst set. However, some random access configuration information may be associated with one of the configured CSI-RSs. However, some random access configuration information may be associated with one downlink transmit beam (or beam index). However, the information associated with one SS / PBCH block, one CSI-RS, and / or one downlink transmit beam may include index information (e.g., an SSB index, a beam index, or a QCL configuration index) to identify the corresponding SS / PBCH block, one CSI-RS, and / or one downlink transmit beam.

[0186] The following describes PRACH opportunities.

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

[0188] However, the PRACH configuration index may be used to configure the time period during which the set of PRACH opportunities shown in the random access configuration table is repeated (PRACH configuration period (physical random access channel configuration period)), the subcarrier index on which random access preambles can be sent, the resource block index, the subframe number, the slot number, the system frame number, the symbol number, and / or the format of the preamble.

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

[0190] However, the number of random access preambles mapped to each SS / PBCH block may be indicated by the upper-layer parameter cb-preamblePerSSB provided in the upper layer. The number of random access preambles mapped to each SS / PBCH block in 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 in each PRACH opportunity may be determined from SB-perRACH-Occasion, cb-preamblePerSSB, and the SSB index.

[0191] For PRACH opportunities, SSB indices may be mapped according to the following rules: (1) Firstly, for a single PRACH opportunity, they are mapped in ascending order of preamble index. For example, if a PRACH opportunity has 64 preambles and each PRACH opportunity has 32 random access preambles mapped to each SS / PBCH block, then the SSB indices mapped to a given PRACH opportunity will be n and n+1. (2) Secondly, for multiple frequency-multiplexed PRACH opportunities, they are mapped in ascending order of frequency resource index. For example, if two PRACH opportunities are frequency-multiplexed and the SSB indices mapped to the PRACH opportunity with the smaller frequency resource index are n and n+1, then the SSB indices mapped to the PRACH opportunity with the larger frequency resource index will be n+2 and n+3. (3) Thirdly, for multiple time-multiplexed PRACH opportunities within a PRACH slot, they are mapped in ascending order of time resource index. For example, if, in addition to the example in (2) above, there are two more PRACH opportunities in the time direction within the PRACH slot, the SSB indices mapped to these PRACH opportunities will be n+4, n+5 and n+6, n+7. (4) Fourthly, multiple PRACH slots are mapped in ascending order of index. For example, if, in addition to the example in (3) above, there are PRACH opportunities in the following PRACH slots, the mapped SSB indices will be n+8, n+9, ... However, in the above example, if n+x becomes greater than the maximum value of the SSB index, the value of the SSB index returns to 0.

[0192] Figure 13 shows an example of SSB index assignment to a PRACH opportunity according to an embodiment of the present invention. Figure 13 shows an example where there are two PRACH slots in a certain time interval, and within one PRACH slot there are two PRACH opportunities (RO) in the time direction and two in the frequency direction, and the SSB index ranges from 0 to 11. Two SSB indices are mapped to one PRACH opportunity, and the SSB indices are mapped according to the rules (1) to (4) above, and from the seventh PRACH opportunity onwards, the mapping starts again from SSB index 0.

[0193] An SSB index is mapped to each PRACH opportunity, but if not all SSB indices (all SS / PBCH blocks transmitted by the base station device 3) are mapped even when all PRACH opportunities within the PRACH configuration period specified by prach-ConfigIndex are used, the SSB index may be mapped across 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 indices are mapped at least once is called an association period. The number of PRACH configuration periods constituting the association period may be the smallest value from a predetermined set of values ​​that satisfies the above conditions. This predetermined set of values ​​may be defined for each PRACH configuration period. However, if all SSB indices have been mapped to PRACH opportunities within an association period, and the number of remaining PRACH opportunities is greater than the number of SS / PBCH blocks, then SSB indices may be mapped again. However, if all SSB indices have been mapped to PRACH opportunities within an association period, and the number of remaining PRACH opportunities is less than the number of SS / PBCH blocks, then SSB indices do not need to be mapped to the remaining PRACH opportunities. A cycle in which all SSB indices are assigned one PRACH opportunity is called an SSB index assignment cycle. When SSB-perRACH-Occasion is 1 or greater, each SSB index is mapped to one PRACH opportunity in one SSB index assignment cycle. If SSB-perRACH-Occasion is less than 1, each SSB index is mapped to a PRACH opportunity of 1 / SSB-perRACH-Occasion in one SSB index assignment cycle. Terminal device 1 may determine the association period based on the PRACH setting period indicated by the PRACH setting index and the number of SS / PBCH blocks specified by the upper layer parameters provided by the upper layer (upper layer signal).

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

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

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

[0197] One or more random access configuration settings may consist of one random access channel configuration (RACH-Config) and / or one physical random access channel configuration (PRACH-Config).

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

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

[0200] One random access configuration entry may indicate parameters for random access corresponding to one reference signal, while multiple random access configuration entries may indicate parameters for multiple random access corresponding to multiple reference signals.

[0201] A single random access configuration entry may indicate parameters for physical random access corresponding to one reference signal, or it may indicate parameters for multiple random accesses corresponding to multiple reference signals.

[0202] If a corresponding reference signal is selected, the random access configuration information corresponding to the reference signal (random access channel configuration corresponding to the reference signal, physical random access channel configuration corresponding to the reference signal) may be selected.

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

[0204] However, the base station device 3 may determine the downlink transmit beam to be applied when transmitting a downlink signal to the terminal device 1 by receiving a random access preamble transmitted by the terminal device 1. The terminal device 1 may transmit a random access preamble using a PRACH opportunity indicated in the random access setting information associated with a certain downlink transmit beam. The base station device 3 may determine the downlink transmit 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 that received the random access preamble.

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

[0206] Terminal device 1 may select one or more available random access preambles and / or one or more available PRACH opportunities to use for the random access procedure based on the propagation path characteristics with respect to base station device 3. Terminal device 1 may also select one or more available random access preambles and / or one or more PRACH opportunities to use for the random access procedure based on the propagation path characteristics (which may be, for example, reference signal received power (RSRP)) measured by a reference signal (e.g., SS / PBCH block and / or CSI-RS) received from base station device 3.

[0207] In this embodiment, uplink resource allocation supports uplink resource allocation type 0 and uplink resource allocation type 1. In uplink resource allocation type 0, the resource block assignment information includes a bitmap indicating resource block groups (RBGs) to be allocated to terminal device 1. A resource block group is a contiguous set of virtual resource blocks and may be defined from higher-layer parameters.

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

[0209] Resource block assignment information is provided to the scheduled terminal device 1, with a size of N. ｓｉｚｅ ＢＷＰ This shows a set of non-interleaved virtual resource blocks that are contiguously allocated in the active BWP, where size N. ｓｉｚｅ ＢＷＰ This is the number of resource blocks indicating the bandwidth of the active UL BWP. When DCI format 0_0 is found in type 0-PDCCH common search space set in CORESET#0, size N ｓｉｚｅＢＷＰ This indicates the bandwidth of the initial UL BWP.

[0210] The Uplink Type 1 resource assignment field is the Start Resource Block (RB ｓｔａｒｔ、 The starting virtual resource block and the number of contiguously allocated resource blocks (L ＲＢｓ It consists of a Resource Indication Value (RIV) corresponding to the resource. That is, the Resource Indication Value RIV is shown in the Resource Assignment field. ｓｔａｒｔ L indicates the starting position of the allocated resource block. ＲＢｓ This indicates the number (length, size) of resource blocks of the allocated resource. The resource instruction value RIV indicates the resource to be allocated to the corresponding UL BWP. The target UL BWP may be the UL BWP to which the resource assignment (resource assignment field) is applied. 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. That is, the value of RIV is the size (N) of the UL BWP to which the resource assignment is applied. ｓｉｚｅ ＢＷＰ ), Start Resource Block (RB ｓｔａｒｔ ), and the number of contiguously allocated resource blocks (L ＲＢｓ It is calculated by the value of RIV shown in the resource assignment field and N. ｓｉｚｅ ＢＷＰBased on this, the terminal device 1 calculates the starting position of the resource blocks allocated in that UL BWP and the number of resource blocks allocated consecutively. In other words, terminal device 1 interprets the bits in the resource assignment field for the UL BWP to which the resource assignment applies. Base station device 3 determines the resource allocation in the UL BWP to which terminal device 1 applies, generates an RIV based on the size of the applied UL BWP, and transmits a resource assignment including a bit sequence indicating the RIV to terminal device 1. Terminal device 1 identifies the frequency-direction resource block allocation (of PUSCH) for the applied UL BWP based on the bit sequence in the resource assignment field.

[0211] Figure 12 shows an example of how to calculate the RIV.

[0212] In Figure 12(A), N ｓｉｚｅ ＢＷＰ This is the number of resource blocks that represent the bandwidth of the active UL BWP. The value of RIV is the number of resource blocks N that represent the bandwidth of the initial BWP. ｓｉｚｅ ＢＷＰ , resource block start position RB ｓｔａｒｔ , and the number of resource blocks L allocated consecutively. ＲＢｓ It is calculated based on RB. ｓｔａｒｔ This is the starting position of the resource block for the active UL BWP. ＲＢｓ This is the number of resource blocks that are continuously allocated to the active BWP. Thus, the resources allocated to the active BWP are determined by the starting position RB of the resource block. ｓｔａｒｔ , and the number L of resource blocks to be allocated sequentially. ＲＢｓ It is identified by the following: If the DCI format is detected in the common search space set (e.g., the type 1 PDCCH common search space set), then N in Figure 12(A) ｓｉｚｅ ＢＷＰ The number of resource blocks that represent the initial UL BWP bandwidth is used for this purpose.

[0213] In Figure 12(B), N ｎｉｔｉａｌＢＷＰ This is the number of resource blocks that represent the bandwidth of the initial BWP (UL BWP). ａｃｔｉｖｅ ＢＷＰ This is the number of resource blocks that represent the bandwidth of the active BWP (UL BWP). The value of RIV is the number of resource blocks N that represent the bandwidth of the initial BWP. ｎｉｔｉａｌ ＢＷＰ , starting position RB' of the resource block ｓｔａｒｔ , and the number of resource blocks L' allocated consecutively. ＲＢｓ It is calculated based on RB'. ｓｔａｒｔ L' is the starting position of the resource block relative to the initial BWP. ＲＢｓ RB' is the number of resource blocks that are continuously allocated to the initial BWP. ｓｔａｒｔ The multiplication of this by the coefficient K is RB ｓｔａｒｔ The product of L'RBs and the coefficient K is L ＲＢｓ The coefficient K is calculated based on the bandwidth of the initial BWP and the bandwidth of the active BWP. ａｃｔｉｖｅ ＢＷＰ is N ｎｉｔｉａｌ ＢＷＰ If it is greater than, the value of K is K <= Floor(N) in the set {1, 2, 4, 8}. ａｃｔｉｖｅ ＢＷＰ / N ｎｉｔｉａｌ ＢＷＰ This is the largest value that satisfies the condition ). Here, the function Floor(A) outputs the largest integer that does not exceed A. ａｃｔｉｖｅ ＢＷＰ is N ｎｉｔｉａｌ ＢＷＰ If equal to or less than the value of K, the value of K is 1. This means that the resources allocated to the active BWP are at the start position RB of the resource block. ｓｔａｒｔ , and the number L of resource blocks to be allocated sequentially. ＲＢｓ It is identified by [the specified method].

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

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

[0216] In Figure 11, one initial UL BWP (1101) and two additional UL BWPs (1102 and 1103) are configured for terminal device 1. As mentioned above, common resource block n ＰＲＢ These are resource blocks numbered in ascending order from 0 at each subcarrier interval setting μ starting from point A. In other words, 1114 is a common resource block (common resource block 0) assigned the number 0. At the subcarrier interval setting μ, common resource block 0 (common resource block index 0, n ＣＲＢ The center of subcarrier index 0 of #0) coincides with point A. 1104 is the starting position of the carrier in the subcarrier spacing setting μ, and is given by the upper layer parameter OffsetToCarrier. That is, the upper layer parameter OffsetToCarrier is the frequency domain offset between point A and the lowest available subcarrier of the carrier. This offset (1115) indicates the number of resource blocks in the subcarrier spacing setting μ. That is, different subcarrier spacing settings μ result in different bandwidths in the frequency domain of this offset. In the subcarrier spacing setting μ, 1104 may also be the position of the resource block where the carrier starts. 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, there are n physical resource blocks in that BWP index i. ＰＲＢ and common resource block n ＣＲＢ The relationship is (Equation 3) nＣＲＢ = n ＰＲＢ + N ｓｔａｒｔ ＢＷＰ、ｉ is given by. In the sub - carrier spacing setting μ of each BWP, N ｓｔａｒｔ ＢＷＰ、ｉ is the number of common resource blocks at which the BWP index i starts with respect to the common resource block index 0. N ｓｉｚｅ ＢＷＰ、ｉ is the number of resource blocks indicating the bandwidth of the BWP of index i in the sub - carrier spacing setting μ of the BWP index i.

[0217] The position and bandwidth of the frequency domain of the BWP are given by the upper - layer parameter locationAndBandwidth. Specifically, the number of physical resource blocks consecutive to the first physical resource block (physical resource block index 0) of the BWP index i is given by the upper - layer parameter locationAndBandwidth. The value indicated by the upper - layer parameter locationAndBandwidth is interpreted as the value of the RIV for the carrier. As shown in FIG. 12(A), N ｓｉｚｅ ＢＷＰ is set to 275. And the RB ｓｔａｒｔ and L ＲＢｓ indicate the number of physical resource blocks consecutive to the first physical resource block (physical resource block index 0) of the BWP and indicating the bandwidth of the BWP. The first physical resource block of the BWP index i is the physical resource block offset with respect to the physical resource block (1104) indicated by the upper - layer parameter OffsetToCarrier. The number of resource blocks indicating the bandwidth of the BWP index i is N ｓｉｚｅ ＢＷＰ、ｉ . The N ｓｔａｒｔ ＢＷＰ、ｉ of the BWP index i is given from the first physical resource block of the BWP index i and the offset indicated by the upper - layer parameter OffsetToCarrier.

[0218] That is, in Figure 11, in the subcarrier spacing setting μ of UL BWP#0, 1105 is the physical resource block index 0 (n) in UL BWP#0 (1101). ＰＲＢ #0) The relationship between physical resource blocks and common resource blocks in UL BWP#0 is n ＣＲＢ = n ＰＲＢ +N ｓｔａｒｔ ＢＷＰ、０ It is given by the subcarrier spacing setting μ of UL BWP#0, N ｓｔａｒｔ ＢＷＰ、０ (1107) is the common resource block that UL BWP#0 starts with for common resource block index 0. ｓｉｚｅ ＢＷＰ、０ (1106) is the number of resource blocks that represent the bandwidth of UL BWP#0 in the subcarrier spacing setting μ of UL BWP#0.

[0219] In Figure 11, in the subcarrier spacing setting μ of UL BWP #1, 1108 is the physical resource block index 0 (n) in UL BWP #1 (1102). ＰＲＢ #0) The relationship between physical resource blocks and common resource blocks in UL BWP#1 is n ＣＲＢ = n ＰＲＢ +N ｓｔａｒｔ ＢＷＰ、１ It is given by the subcarrier spacing setting μ of UL BWP#1, N ｓｔａｒｔ ＢＷＰ、１ (1110) is the common resource block that UL BWP#1 starts with for common resource block index 0. ｓｉｚｅ ＢＷＰ、１ (1109) is the number of resource blocks representing the bandwidth of UL BWP#0 in the subcarrier spacing setting μ of UL BWP#1.

[0220] In Figure 11, in the subcarrier spacing setting μ of UL BWP#2, 1111 is the physical resource block index 0 (n) in UL BWP#2 (1102). ＰＲＢ #0) The relationship between physical resource blocks and common resource blocks in UL BWP#2 is n ＣＲＢ= n ＰＲＢ +N ｓｔａｒｔ ＢＷＰ、２ It is given by the subcarrier spacing setting μ of UL BWP#2, N ｓｔａｒｔ ＢＷＰ、２ (1113) is the common resource block that UL BWP#2 starts with for common resource block index 0. ｓｉｚｅ ＢＷＰ、２ (1112) is the number of resource blocks that represent the bandwidth of UL BWP#2 in the subcarrier spacing setting μ of UL BWP#2.

[0221] As can be seen from Figure 11, for each BWP set in terminal device 1, the starting position (common resource block to start, N ｓｔａｒｔ ＢＷＰ ) and the number of resource blocks (N ｓｉｚｅ ＢＷＰ ) are different. When terminal device 1 interprets the RIV indicated by the bits of the resource assignment field, it needs to determine the UL BWP to which the resource assignment applies. That is, terminal device 1 determines the UL BWP to which the resource assignment applies, and the N of the determined UL BWP ｓｉｚｅ ＢＷＰ、ｉ Based on this, the RIV is interpreted, and the starting resource block (RB ｓｔａｒｔ ), and the number of contiguously allocated resource blocks (L ＲＢｓ ) can be calculated. ｓｔａｒｔ This indicates the starting position of the allocated resource, relative to physical resource block index 0 of the UL BWP to which the resource assignment is applied. For example, the RB to be calculated ｓｔａｒｔ Even if the values ​​are the same, the starting location of the common resource block will differ if the UL BWP to which the resource assignment is applied is different.

[0222] Additionally, the size N of the UL BWP to which the resource assignment applies. ｓｉｚｅ ＢＷＰIf the RIV is different, the number of bits in the resource assignment that indicate the RIV value will also be different. The bits in the resource block assignment field that can indicate the RIV value are Ceiling(log ２ (N ｓｉｚｅ ＢＷＰ (N ｓｉｚｅ ＢＷＰ It is given by (+1) / (2)).

[0223] Figure 8 shows an example of the random access procedure of the terminal device 1 in this embodiment.

[0224] <Message 1 (S801)> In S801, terminal device 1 transmits a random access preamble to 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 base station device 3 of information by using one of several sequences. For example, 64 types of sequences (random access preamble index numbers from 1 to 64) are available. If 64 types of sequences are available, 6 bits of information (which may be ra-PreambleIndex or preamble index) can be shown to base station device 3. This information may be shown as a Random Access preamble Identifier (RAPID).

[0225] In a competition-based random access procedure, the terminal device 1 randomly selects the index of the random access preamble. In a competition-based random access procedure, the terminal device 1 selects an SS / PBCH block with an RSRP exceeding a set threshold and selects a preamble group. If a relationship between an SS / PBCH block and a random access preamble is set, the terminal device 1 randomly selects a 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 as the preamble index (PREAMBLE_INDEX). Alternatively, for example, the selected SS / PBCH block and the selected preamble group may be divided into two subgroups based on the transmission size of message 3. Terminal device 1 may randomly select a preamble index from a subgroup corresponding to a small message 3 transmission size if the transmission size of message 3 is small, and randomly select a preamble index from a subgroup corresponding to a large message 3 transmission size if the transmission size of message 3 is large. The index for small message sizes is usually selected when the propagation path characteristics are poor (or the distance between terminal device 1 and base station device 3 is large), and the index for large message sizes is selected when the propagation path characteristics are good (or the distance between terminal device 1 and base station device 3 is short).

[0226] In the case of a non-conflict-based random access procedure, the index of the random access preamble is selected by the terminal device 1 based on the information received 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. If all the bit values ​​of the information received from the base station device 3 are 0, the terminal device 1 executes a conflict-based random access procedure, and the index of the random access preamble is selected by the terminal device 1 itself.

[0227] <Message 2 (S802)> Next, the base station device 3, having received message 1, generates a RAR message in S802 that includes an uplink grant (RAR UL grant, Random Access Response Grant) to instruct the terminal device 1 to transmit, and transmits a random access response containing the generated RAR message to the terminal device 1 via DL-SCH. That is, the base station device 3 transmits a random access response containing a RAR message corresponding to the random access preamble transmitted in S801 via PDSCH in the primary cell. This PDSCH corresponds to a PDCCH containing RA-RNTI. This 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 being 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. ul_carrier_id is 0 for a NUL carrier and 1 for a SUL carrier.

[0228] The random access response may be referred to as message 2 or Msg2. The base station device 3 also includes a random access preamble identifier corresponding to the received random access preamble, and a RAR message (MAC RAR) corresponding to that identifier, in message 2. The base station device 3 calculates the timing difference between the terminal device 1 and the base station device 3 from the received random access preamble and includes timing adjustment information (TA command, Timing Advance Command) in the RAR message to adjust this difference. The RAR message includes at least a random access response grant field mapped to the uplink grant, a Temporary C-RNTI field mapped to the Temporary C-RNTI (Cell Radio Network Temporary Identifier), and a TA command (Timing Advance Command). The terminal device 1 adjusts the timing of the PUSCH transmission based on the TA command. The timing of the PUSCH transmission may be adjusted for each group of cells. Furthermore, the base station device 3 includes a random access preamble identifier corresponding to the received random access preamble in message 2.

[0229] To respond to a PRACH transmission, terminal device 1 detects (monitors) a DCI format 1_0 with the CRC parity bits scrambled by the corresponding RA-RNTI added during the duration of the random access response window. The duration (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 interval of the Type1-PDCCH common search space.

[0230] If terminal device 1 detects a DCI format 1_0 with a CRC added that is scrambled by RA-RNTI and a PDSCH containing one DL-SCH transport block within the window period, terminal device 1 passes the transport block to the upper layer. The upper layer parses the transport block for the Random Access Preamble Identifier (RAPID) associated with the PRACH transmission. If the upper layer identifies the RAPID contained 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 contained in the received random access response is the same as the RAPID corresponding to the transmitted random access preamble. The uplink grant is referred to as the Random Access Response Uplink Grant (RAR UL grant) at the physical layer. That is, terminal device 1 can identify a RAR message (MAC RAR) from base station device 3 to itself by monitoring the random access response (message 2) corresponding to the random access preamble identifier.

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

[0232] If the received random access response contains 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 the non-conflict-based random access procedure to have been successfully completed and sends a PUSCH based on the uplink grant included in the random access response. If the received random access response contains 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 value of the TC-RNTI field included in the received random access response and sends a random access message 3 with a 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 sent in the serving cell where the corresponding preamble was transmitted with a PRACH.

[0233] The RAR UL grant (RAR uplink grant) is used for scheduling PUSCH transmissions (Msg3 PUSCH). Terminal device 1 transmits message 3 based on the RAR UL grant. Figure 9 shows an example of the fields included in the RAR UL grant.

[0234] If the value of the frequency hopping flag in Figure 9 is 0, terminal device 1 transmits Msg3PUSCH without frequency hopping. If the value of the frequency hopping flag is 1, terminal device 1 transmits Msg3PUSCH with frequency hopping.

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

[0236] The interpretation of the 'Msg3 PUSCH frequency resource allocation' field is described below. This field is used for resource allocation for the PUSCH transmission of message 3. The 'Msg3 PUSCH frequency resource allocation' field may also 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 UL BWP bandwidth set for terminal device 1. Terminal device 1 has a number of resource blocks (N) that indicate the UL BWP bandwidth to which the resource assignment is applied. ｓｉｚｅ ＢＷＰ Based on this, bits are truncated or inserted into the Msg3 PUSCH frequency resource assignment. The terminal device 1 can then adapt the resource assignment to the bandwidth of the UL BWP to which it is applied by truncating or inserting bits into the Msg3 PUSCH frequency resource assignment. ｓｉｚｅ ＢＷＰHowever, this is 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.

[0237] Figure 10 shows an example of how to interpret the 'Msg3 PUSCH frequency resource allocation' field according to this embodiment.

[0238] In Figure 10(A), 1001 is the 'Msg3 PUSCH frequency resource allocation' field, which has a fixed 14 bits. 1002 is N ＵＬ,ｈｏｐ This is a hopping bit. 1003 is from 1001 to N ＵＬ,ｈｏｐ These are the bits remaining after removing the hopping bits, (14-N ＵＬ,ｈｏｐ ) bits. That is, the 14-bit number 1001 is composed of 1002 and 1003. ＵＬ,ｈｏｐ The number of bits for hopping bits is the value shown in the 'Frequency hopping flag' field, and / or N ｓｉｚｅ ＢＷＰ It is given based on the bandwidth. For example, N ＵＬ,ｈｏｐ The number of bits in the example is N. ｓｉｚｅ ＢＷＰ If the size is smaller than a predetermined number of resource blocks, it may be 1 bit. ＵＬ,ｈｏｐ The number of bits in the example is N. ｓｉｚｅ ＢＷＰ The size may be 2 bits if it is equal to or greater than a predetermined number of resource blocks. The predetermined number of resource blocks may be 50. ｓｉｚｅ ＢＷＰ The explanation will be given later.

[0239] As mentioned above, if the value of the frequency hopping flag is 0, N ＵＬ,ｈｏｐThe hopping bit is 0 bits. In this case, 1003 is 1001 and has 14 bits. If the value of the frequency hopping flag is 1, N ＵＬ,ｈｏｐ The number of bits in the hopping bit is N. ｓｉｚｅ ＢＷＰ The value of may be assigned to one or two bits based on whether it exceeds a predetermined resource block number Y. For example, N ｓｉｚｅ ＢＷＰ If it is smaller than the predetermined number of resource blocks Y, then N ＵＬ,ｈｏｐ The hopping bit may be assigned to 1 bit. N ｓｉｚｅ ＢＷＰ If it is equal to or greater than a predetermined resource block number Y, then N ＵＬ,ｈｏｐ The hopping bit may be assigned to two bits. That is, 1003 may have 12 bits or 13 bits.

[0240] Figure 10(B) is N ｓｉｚｅ ＢＷＰ This figure shows an example of truncating bits in the 'Msg3 PUSCH frequency resource allocation' field if X is less than or equal to a predetermined resource block number.

[0241] In Figure 10(B), terminal device 1 is N ｓｉｚｅ ＢＷＰ If the value of the resource block number X is less than or equal to the value of the predetermined resource block number, the bits of the Msg3 PUSCH frequency resource assignment are truncated by b bits from the least significant bit (LSB). In other words, b bits is the number of bits to be truncated. The value of b is (Equation 1) b = Ceiling(log ２ (N ｓｉｚｅ ＢＷＰ (N ｓｉｚｅ ＢＷＰIt is calculated by (+1) / (2)). Here, the function Ceiling(A) outputs the smallest integer not less than A. The truncated Msg3 PUSCH frequency resource assignment may also be called the truncated resource block assignment. Terminal device 1 may interpret the truncated resource block assignment according to the rules for the normal DCI format 0_0.

[0242] In Figure 10(B), 1004 is a 14-bit Msg3 PUSCH frequency resource assignment. 1005 is N ＵＬ,ｈｏｐ This is a hopping bit. 1006 is in Msg3 PUSCH frequency resource assignment N ＵＬ,ｈｏｐ These are bits other than the hopping bits. 1008 is the resource block assignment to be truncated. The number of bits in 1008 is b bits. The number of bits in 1007 is 14-b.

[0243] Figure 10(C) shows N ｓｉｚｅ ＢＷＰ This figure shows an example of inserting bits into the 'Msg3 PUSCH frequency resource allocation' field when the bandwidth is greater than a predetermined value X for the number of resource blocks.

[0244] In Figure 10(C), 1009 is a 14-bit Msg3 PUSCH frequency resource assignment. 1010 is N ＵＬ,ｈｏｐ This is a hopping bit. 1012 is from Msg3 PUSCH frequency resource assignment N ＵＬ,ｈｏｐ These are the bits remaining after removing the hopping bits. The number of bits in 10¹² is (14 - N). ＵＬ,ｈｏｐ ) bits. Terminal device 1 is N ｓｉｚｅ ＢＷＰ If the value X is large enough to be the predetermined number of resource blocks, Msg3 PUSCH frequency resource assignment will contain N ＵＬ,ｈｏｐAfter the hopping bit, the most significant bit (MSB) b is inserted and set to the value '0'. In other words, b is the number of bits to be inserted. The value of b is (Equation 2) b = (Ceiling(log) ２ (N ｓｉｚｅ ＢＷＰ (N ｓｉｚｅ ＢＷＰ It is calculated by (+1) / (2))-Z). The value of Z may be 14. The Msg3 PUSCH frequency resource assignment into which b bits are inserted may be called the extended resource block assignment. Terminal device 1 may interpret the extended resource block assignment according to the rules for the normal DCI format 0_0. In Figure 10(C), the number of bits in 1011 is b bits. 1009 is the extended resource block assignment. The number of bits in 1009 is the sum of the 14 bits of the Msg3 PUSCH frequency resource assignment and b bits.

[0245] As described above, one initial BWP is configured for terminal device 1, which includes at least one DL BWP and one UL BWP. Furthermore, up to four additional BWPs are configured for terminal device 1. The size (N) of each UL BWP configured for terminal device 1 is... ｓｉｚｅ ＢＷＰ ) may be different. UL BWP size N ｓｉｚｅ ＢＷＰ This is the number of resource blocks indicating the bandwidth of the corresponding UL BWP. When terminal device 1 identifies a resource allocation, it first determines the UL BWP to which the resource allocation applies, and then determines the resource allocation within the determined UL BWP.

[0246] Terminal device 1 determines the UL BWP to which the resource assignment is applied when truncating or inserting bits into the Msg3 PUSCH frequency resource assignment. That is, terminal device 1 determines the bandwidth N of the UL BWP used when truncating or inserting bits into the Msg3 PUSCH frequency resource assignment. ｓｉｚｅＢＷＰ This is determined based on the UL BWP to which the resource assignment applies.

[0247] In this embodiment, N represents the bandwidth of the UL BWP (UL BWP to be interpreted) to which the resource assignment is applied. ｓｉｚｅ ＢＷＰ The method for determining N will be explained. Base station device 3 determines N in random access procedure ｓｉｚｅ ＢＷＰ Determine the N ｓｉｚｅ ＢＷＰ Using this method, the RIV is generated, the bit sequence to be included in the frequency resource assignment field is determined, and the PUSCH frequency resource assignment is transmitted to the terminal device 1.

[0248] As described above, terminal device 1 monitors the DCI format with CRCs added, which are scrambled by RA-RNTI or TC-RNTI in the search space for random access procedures (Type 1 PDCCH common search space set). By monitoring the DCI format with CRCs added, which are scrambled by RA-RNTI in this search space set, terminal device 1 receives random access responses. CORESET configuration information for the Type 1 PDCCH common search space set is shown to terminal device 1.

[0249] In one aspect of this embodiment, in a competition-based random access procedure, terminal device 1 may determine that the UL BWP to which resource assignment is applied is the UL BWP having the same BWP identifier as the DL BWP to which the CORESET configuration information associated with the search space for the random access procedure (Type 1 PDCCH common search space set) is configured. That is, in a competition-based random access procedure, N ｓｉｚｅ ＢＷＰ This is the number of resource blocks indicating the bandwidth of a UL BWP that has the same BWP identifier as the DL BWP in which the CORESET configuration information associated with the Type 1 PDCCH common search space set is configured. And, terminal device 1, the determined N ｓｉｚｅＢＷＰ Using this, bits are truncated or inserted into the Msg3 PUSCH frequency resource assignment. The bits of the resource block assignment being truncated or expanded indicate the RIV value. Terminal device 1 determines N ｓｉｚｅ ＢＷＰ N in Figure 12(A) ｓｉｚｅ ＢＷＰ Used in RB ｓｔａｒｔ and L ＲＢｓ It is possible to calculate RB calculated from the RIV value. ｓｔａｒｔ This 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 resource assignments shown from the RAR UL grant starts in ascending order from physical resource block index 0 (the lowest number of physical resource blocks in the UL BWP to which the resource assignment applies) corresponding to the UL BWP to which the resource assignment applies.

[0250] In one aspect of this embodiment, in a competition-based random access procedure, 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 CORESET configuration information associated with the type 1 PDCCH common search space set is set is the initial DL BWP. For example, terminal device 1 may determine the initial UL BWP as the UL BWP to which resource assignment is applied if the DL BWP in which the CORESET configuration information associated with the type 1 PDCCH common search space set is set is the initial DL BWP. Alternatively, terminal device 1 may determine the active UL BWP as the UL BWP to which resource assignment is applied if the DL BWP in which the CORESET configuration information associated with the type 1 PDCCH common search space set is set is not the initial DL BWP. ｓｉｚｅ ＢＷＰThis is the number of resource blocks indicating the bandwidth of the UL BWP. And N is the bandwidth of the UL BWP determined to be the UL BWP to which the resource assignment is applied to terminal device 1. ｓｉｚｅ ＢＷＰ This is used to truncate or insert bits into the Msg3 PUSCH frequency resource assignment.

[0251] Furthermore, in one aspect of this embodiment, in a competition-based random access procedure, 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 CORESET associated with the type 1 PDCCH common search space set is a common CORESET. For example, terminal device 1 may determine the initial UL BWP as the UL BWP to which resource assignment is applied if the CORESET associated with the type 1 PDCCH common search space set is a common CORESET. Alternatively, terminal device 1 may determine the active UL BWP as the UL BWP to which resource assignment is applied if the CORESET associated with the type 1 PDCCH common search space set is not a common CORESET. ｓｉｚｅ ＢＷＰ This is the number of resource blocks indicating the bandwidth of the UL BWP to which the resource assignment is applied. And terminal device 1, the determined N ｓｉｚｅ ＢＷＰ This is used to truncate or insert bits into the Msg3 PUSCH frequency resource assignment.

[0252] Furthermore, as an extension of the above embodiment, in a competition-based random access procedure, 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 CORESET associated with the type 1 PDCCH common search space set is CORESET #0. For example, terminal device 1 may determine the initial UL BWP as the UL BWP to which resource assignment is applied if the CORESET associated with the type 1 PDCCH common search space set is CORESET #0. Alternatively, terminal device 1 may determine the active UL BWP as the UL BWP to which resource assignment is applied if the CORESET associated with the type 1 PDCCH common search space set is not CORESET #0. Furthermore, if the CORESET associated with the Type 1 PDCCH common search space set is an additional common CORESET, 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 resource assignment is applied. In other words, if the additional common CORESET is set for the initial DL BWP, terminal device 1 may determine the initial UL BWP as the UL BWP to which resource assignment is applied. If the additional common CORESET is set for the additional DL BWP, terminal device 1 may determine the UL BWP having the same BWP identifier as the additional DL BWP as the UL BWP to which resource assignment is applied.

[0253] Furthermore, in one aspect of this embodiment, in a competition-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. That is, in a competition-based random access procedure, N ｓｉｚｅ ＢＷＰ This is the number of resource blocks that represent the bandwidth of the initial UL BWP. And terminal device 1, the determined N ｓｉｚｅ ＢＷＰUsing this, bits are truncated or inserted into the Msg3 PUSCH frequency resource assignment. The bits of the resource block assignment being truncated or expanded indicate the RIV value. Terminal device 1 determines N ｓｉｚｅ ＢＷＰ N in Figure 12(A) ｓｉｚｅ ＢＷＰ It is used to determine if an RIV is generated. The RIV is RB ｓｔａｒｔ and L ＲＢｓ It is generated from, and terminal device 1 receives RB from RIV ｓｔａｒｔ and L ＲＢｓ Obtain RB ｓｔａｒｔ This indicates the starting position of the allocated resources relative to physical resource block index 0, which corresponds to the initial UL BWP. In other words, the numbering of resource allocations shown from the RAR UL grant starts from physical resource block index 0, which corresponds to the initial UL BWP (the lowest number of physical resource blocks in the UL BWP to which the resource assignment applies).

[0254] Furthermore, in one aspect of this embodiment, in a non-contradiction-based random access procedure, the terminal device 1 may always determine the active UL BWP as the UL BWP to which resource assignment is applied. That is, in a non-contradiction-based random access procedure, N ｓｉｚｅ ＢＷＰ This is the number of resource blocks that represent the bandwidth of the active UL BWP. And terminal device 1, the determined N ｓｉｚｅ ＢＷＰ Using this, bits are truncated or inserted into the Msg3 PUSCH frequency resource assignment. The bits of the resource block assignment being truncated or expanded indicate the RIV value. Terminal device 1 determines N ｓｉｚｅ ＢＷＰ N in Figure 12(A) ｓｉｚｅ ＢＷＰ It is used to determine if an RIV is generated. The RIV is RB ｓｔａｒｔ and L ＲＢｓIt is generated from, and terminal device 1 receives RB from RIV ｓｔａｒｔ and L ＲＢｓ Obtain RB ｓｔａｒｔ This indicates the starting position of the allocated resources relative to physical resource block index 0, which corresponds to the active UL BWP. In other words, the numbering of resource allocations shown from the RAR UL grant starts from physical resource block index 0, which corresponds to the active UL BWP (the lowest numbered physical resource block of the UL BWP to which the resource assignment applies).

[0255] As seen in the example above, in a competition-based random access procedure, if DCI format 1_0 that schedules a PDSCH (DL-SCH transport block) containing a RAR UL grant indicating resource block assignment information is detected in the common search space (e.g., type 1 PDCCH common search space) in CORESET #0 (or an additional common CORESET set for the initial DL BWP), then in Figure 12(A), N ｓｉｚｅ ＢＷＰ The initial UL BWP size is used. Here, DCI format 1_0 is DCI format 1_0 with the CRC parity bits scrambled by the corresponding RA-RNTI added.

[0256] In the above embodiment, in a non-conflict-based random access procedure, terminal device 1 determines the active UL BWP as the UL BWP to which resource assignment is applied, regardless of whether the CORESET associated with the Type 1 PDCCH common search space set is a common CORESET. Furthermore, in a non-conflict-based random access procedure, terminal device 1 determines the active UL BWP as the UL BWP to which resource assignment is applied, regardless of whether the DL BWP in which the configuration information for the CORESET associated with the Type 1 PDCCH common search space set is configured is the initial DL BWP.

[0257] In other words, terminal device 1 determines whether the random access procedure is a competition-based random access procedure or a non-competition-based random access procedure, and assigns either the initial UL BWP or the active UL BWP to the UL BWP (N) to which resource assignment is applied. ｓｉｚｅ ＢＷＰ ) is determined as. For example, terminal device 1 may determine the initial UL BWP as the UL BWP to which resource assignment is applied when the random access procedure is a competition-based random access procedure. Then N ｓｉｚｅ ＢＷＰ n is the number of resource blocks indicating the bandwidth of the initial UL BWP. Furthermore, terminal device 1 may determine the active UL BWP as the UL BWP to which resource assignment is applied when the random access procedure is a non-conflict-based random access procedure. Then, N ｓｉｚｅ ＢＷＰ This is the number of resource blocks that indicate the bandwidth of the active UL BWP.

[0258] N ＵＬ,ｈｏｐ The number of hopping bits is equal to the size (N) of the UL BWP to which the resource assignment is applied. ｓｉｚｅ ＢＷＰ ) may be assigned to 1 or 2 bits based on whether it exceeds a predetermined resource block number Y. That is, N ｓｉｚｅ ＢＷＰ N represents the bandwidth of the UL BWP to which the resource assignment determined in the above manner is applied. ｓｉｚｅ ＢＷＰ It may also be N ｓｉｚｅ ＢＷＰ If it is smaller than the predetermined number of resource blocks Y, then N ＵＬ,ｈｏｐ The hopping bit may be given as 1 bit. For the PUSCH transmission of message 3, the frequency offset of the second hop is Floor(N ｓｉｚｅ ＢＷＰ / 2) or Floor(N ｓｉｚｅ ＢＷＰ / 4) N ｓｉｚｅ ＢＷＰ If it is equal to or greater than a predetermined resource block number Y, then NＵＬ,ｈｏｐ The hopping bit may be given as 2 bits. For the PUSCH transmission of message 3, the frequency offset of the second hop is Floor(N ｓｉｚｅ ＢＷＰ / 2), Floor(N ｓｉｚｅ ＢＷＰ / 4), or -Floor(N ｓｉｚｅ ＢＷＰ / 4)

[0259] As mentioned above, the resource block indexing (RB indexing) for resource allocation (uplink type 0 and / or type 1 resource allocation) is determined within the UL BWP to which the resource assignment indicating the resource allocation is applied. Specifically, if the DCI format does not have a bandwidth part indicator field, the RB indexing for resource allocation is determined within the active BWP of terminal device 1. However, even if the DCI format does not have a bandwidth part indicator field, the RB indexing for 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 any additional common CORESET set for the initial DL BWP). In other words, even if the DCI format does not have a bandwidth part indicator field set, the RB numbering for resource allocation is determined within the initial UL BWP for DCI format 0_0 detected in any common search space set in the CORESET configured for the initial DL BWP. Similarly, even if the DCI format does not have a bandwidth part indicator field set, the RB numbering for resource allocation is determined within the active BWP for DCI format 0_0 detected in any common search space set in the CORESET configured for the active BWP.

[0260] If a bandwidth part indicator field (BWP) is set in the DCI format, the RB numbering for resource assignment is determined within the BWP indicated in the BWP indicator field. However, even if a bandwidth part indicator field (BWP) is set in the DCI format, 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), the RB numbering for resource assignment is determined within the initial UL BWP. When terminal device 1 detects a PDCCH for terminal device 1, it first determines the UL BWP to which resource assignment is applied, and then determines the resource assignment within the determined UL BWP.

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

[0262] Furthermore, in a competition-based random access procedure, if a DCI format 1_0 scheduling a PDSCH (DL-SCH transport block) containing a RAR UL grant is detected in the common search space in CORESET#0 (e.g., type 1 PDCCH common search space), the RB numbering of the resource allocation indicated in the RAR UL grant may be determined within the initial UL BWP of terminal device 1. Here, DCI format 1_0 is DCI format 1_0 with CRC parity bits added, which are scrambled by the corresponding RA-RNTI. Furthermore, in a competition-based random access procedure, if a DCI format 1_0 scheduling a PDSCH (DL-SCH transport block) containing a RAR UL grant is detected in a common search space (e.g., 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 within the active UL BWP of terminal device 1. However, if a DCI format 1_0 scheduling a PDSCH (DL-SCH transport block) containing a RAR UL grant is detected in a common search space (e.g., type 1 PDCCH common search space) in an additional common coreset configured for the 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 terminal device 1.

[0263] Furthermore, for DCI format 0_0 that schedules the retransmission of Msg3 PUSCH, the RB numbering for 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 the retransmission of Msg3 PUSCH is scrambled by TC-RNTI. DCI format 0_0 does not include a BWP instruction field.

[0264] <Message 3 (S803)> Terminal device 1 sends a PUSCH of message 3 based on the RAR UL grant contained in the RAR message received in S802. The PUSCH corresponding to the transmission of message 3 is sent in the serving cell where the corresponding preamble was sent as PRACH. Specifically, the PUSCH corresponding to the transmission of message 3 is sent in the active UL BWP.

[0265] <Retransmission of Message 3 (S803a)> Retransmission of Message 3 is scheduled by DCI format 0_0, to which CRC parity bits scrambled by TC-RNTI included in the RAR message are added. That is, the PUSCH retransmission of the transport block sent by PUSCH corresponding to the RAR UL grant included in the RAR message is scheduled by DCI format 0_0, to which CRC parity bits scrambled by TC-RNTI are added. The DCI format 0_0 is transmitted by PDCCH of type 1 PDCCH common search space set. That is, after sending Message 3 in S803, terminal device 1 may monitor DCI format 0_0 to schedule the retransmission of Message 3. In S803a, if terminal device 1 detects DCI format 0_0 to schedule the retransmission of Message 3, S803b is executed.

[0266] The DCI format 0_0 for scheduling the retransmission of message 3 includes a frequency domain resource assignment field. The bits in this field are given based on the initial UL BWP. Specifically, the number of bits in this field is (Equation 4) Ceiling(log ２ (N ＵＬ、ＢＷＰ ＲＢ (N ＵＬ、ＢＷＰ ＲＢ It is calculated by (+1) / (2)). Here, N ＵＬ、ＢＷＰ ＲＢThis represents the number of resource blocks indicating the bandwidth of the initial UL BWP. In other words, regardless of which of the one or more UL BWPs set for terminal device 1 is used to schedule the resources for retransmitting message 3, the number of bits in the frequency domain resource assignment field will be a fixed value (the same value) based on the bandwidth of the initial UL BWP.

[0267] Also, as an example, N ＵＬ、ＢＷＰ ＲＢ N may be given based on the type of random access procedure. For example, in a competition-based random access procedure, ＵＬ、ＢＷＰ ＲＢ This is the number of resource blocks that represent the bandwidth of the initial UL BWP. Also, for example, in a non-contradiction-based random access procedure, N ＵＬ、ＢＷＰ ＲＢ This is the number of resource blocks that indicate the bandwidth of the active UL BWP.

[0268] Terminal device 1 needs to interpret the bits of the frequency domain resource assignment field based on the initial UL BWP in order to adapt them to the bandwidth of the UL BWP to which the frequency domain resource assignment (frequency domain resource assignment field) is applied. As described above, terminal device 1 determines the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied when truncating or inserting bits into the Msg3 PUSCH frequency resource assignment. Here, the UL BWP to which the frequency domain resource assignment field included in 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. That is, the UL BWP to which the frequency domain resource assignment included in DCI format 0_0 is applied may be the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied. That is, terminal device 1 may identify the frequency-direction resource block allocation of PUSCH in the UL BWP to which Msg3 PUSCH frequency resource assignment is applied, based on the RIV value shown in the frequency domain resource assignment field.

[0269] For example, if the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied is the initial UL BWP (or the initial active UL BWP), then 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 the bit sequence to be included in the frequency resource assignment field, and transmits it to the terminal device 1. The terminal device 1 then identifies the PUSCH frequency-direction resource allocation of the physical resource block 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 Figure 12(A) to determine the RB corresponding to the physical resource block of the initial BWP. ｓｔａｒｔ and LＲＢｓ This can be identified. Here, N in Figure 12(A) ｓｉｚｅ ＢＷＰ This is a resource block that indicates the bandwidth of the initial UL BWP. In other words, the RIV value shown in the frequency domain resource assignment field is the size of the initial UL BWP to which the resource assignment applies, and the RB corresponding to the resource block of the initial UL BWP. ｓｔａｒｔ and L ＲＢｓ It is given based on RB. ｓｔａｒｔ This is the number of resource blocks that indicates the starting position of resource allocation, relative to the initial BWP UL's physical resource block index 0. ＲＢｓ This cannot exceed the number of resource blocks representing the bandwidth of the initial UL BWP. That is, the numbering of resources shown in the frequency domain resource assignment field starts from the smallest number of physical resource blocks in the initial UL BWP.

[0270] As seen in the example above, in the case where DCI format 0_0 is detected in a type 1PDCCH common search space set in an additional common coreset configured for CORESET #0 or the initial DL BWP, N in Figure 12(A) ｓｉｚｅ ＢＷＰ The size of the initial UL BWP is used. Here, DCI format 0_0 may be monitored in CSS. In other words, terminal device 1 identifies the frequency-direction resource block allocation of the initial UL BWP even if the activated UL BWP (the UL BWP on which uplink data is transmitted) is not 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. Also, in the case where DCI format 0_0 is detected in CORESET#0 or any common search space set in an additional common CORESET set for the initial UL BWP, N in Figure 12(A) ｓｉｚｅＢＷＰ The initial UL BWP size is used.

[0271] For example, if the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied is an active UL BWP, then the UL BWP to which the frequency domain resource assignment field included in DCI format 0_0 is applied is an 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 the bit sequence to be included in the frequency resource assignment field, and transmits it to the terminal device 1. The terminal device 1 then identifies the PUSCH frequency-direction resource assignment 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 shown in Figure 12(B) to determine the RB corresponding to the physical resource block of the active UL BWP. ｓｔａｒｔ and L ＲＢｓ This can be identified. In this case, N in Figure 12(B) ｎｉｔｉａｌ ＢＷＰ This is the number of resource blocks that represent the initial UL BWP bandwidth. ａｃｔｉｖｅ ＢＷＰ This is the number of resource blocks that represent the bandwidth of the active UL BWP. The value of RIV is the number of resource blocks N that represent the bandwidth of the initial BWP. ｎｉｔｉａｌ ＢＷＰ , starting position RB' of the resource block ｓｔａｒｔ , and the number of resource blocks L' to be allocated sequentially. ＲＢｓ Based on this, it is given. RB ｓｔａｒｔ This is the number of resource blocks that indicates the starting position of resource allocation, relative to the physical resource block index 0 of the active UL BWP. In other words, the numbering of resources shown in the frequency domain resource assignment field starts from the lowest numbered physical resource block of the active UL BWP.

[0272] As seen in the example above, if the size of DCI format 0_0 in 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, and the UL BWP to which the resource assignment of the Msg3 PUSCH frequency resource assignment field is applied is an active UL BWP, then the method in Figure 12(B) may be applied. In other words, if the size of DCI format 0_0 in 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, and the size of 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), then the method in Figure 12(B) may be applied. Here, CSS is the CSS associated with a CORESET other than CORESET#0 and any additional common CORESETs set for the initial DL BWP. In other words, CSS is the CSS associated with a CORESET set for a DL BWP other than the initial DL BWP. Here, DCI format 0_0 may be scrambled by TC-RNTI. That is, the method in Figure 12(B) may be applied when the DCI format is derived from the size of the initial UL BWP, but the UL BWP to which the DCI format applies is another active UL BWP, and the search space set in the DCI format is a common search space set or a UE-specific search space set associated with a CORESET set for a BWP other than the initial DL BWP.

[0273] As mentioned above, the number of bits in the frequency domain resource assignment field included in DCI format 0_0 is N, which represents the bandwidth of the initial UL BWP. ＵＬ，ＢＷＰ ＲＢIt is given by the N included in the frequency domain resource assignment field. ＵＬ,ｈｏｐ The number of bits in the hopping bit is N. ＵＬ，ＢＷＰ ＲＢ It may be assigned to 1 or 2 bits based on whether it exceeds a predetermined resource block value Y. Also, N included in the frequency domain resource assignment field ＵＬ,ｈｏｐ The number of bits in the hopping bit is N. ｓｉｚｅ ＢＷＰ This may be assigned to one or two bits based on whether it exceeds a predetermined resource block value Y. Here, N ｓｉｚｅ ＢＷＰ This is the number of resource blocks that represent the bandwidth of the UL BWP to which the frequency domain resource assignment field is applied. That is, N ｓｉｚｅ ＢＷＰ If it is smaller than the predetermined number of resource blocks Y, then N ＵＬ,ｈｏｐ The hopping bit may be given as 1 bit. For the PUSCH transmission of message 3, the frequency offset of the second hop is Floor(N ｓｉｚｅ ＢＷＰ / 2) or Floor(N ｓｉｚｅ ＢＷＰ / 4) N ｓｉｚｅ ＢＷＰ If it is equal to or greater than a predetermined resource block number Y, then N ＵＬ,ｈｏｐ The hopping bit may be given as 2 bits. For the PUSCH transmission of message 3, the frequency offset of the second hop is Floor(N ｓｉｚｅ ＢＷＰ / 2), Floor(N ｓｉｚｅ ＢＷＰ / 4), or -Floor(N ｓｉｚｅ ＢＷＰ / 4)

[0274] <Retransmission of Message 3 (S803b)> If DCI format 0_0 with CRC parity bits scrambled by TC-RNTI is detected in S803a, terminal device 1 performs a PUSCH retransmission of the transport block sent in S803.

[0275] <Message 4 (S804)> In order to respond to the PUSCH transmission of Message 3, the terminal device 1 not indicated by the C-RNTI monitors DCI format 1_0 that schedules a PDSCH including a UE contention resolution identity. Here, this DCI format 1_0 is added with CRC parity bits scrambled by the corresponding TC-RNTI. In order to respond to the reception of the PDSCH with the UE contention resolution identity, the terminal device 1 transmits HARQ-ACK information on the PUCCH. The transmission of the PUCCH may be performed in the active UL BWP in which Message 3 is transmitted.

[0276] As a result, the terminal device 1 performing the random access procedure can perform uplink data transmission to the base station device 3.

[0277] Hereinafter, the configuration of the device in the present embodiment will be described.

[0278] FIG. 15 is a schematic block diagram showing the configuration of the terminal device 1 of the present embodiment. As shown in the figure, the terminal device 1 includes a wireless transmission / reception unit 10 and an upper layer processing unit 14. The wireless 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 media access control layer processing unit 15 and a radio resource control layer processing unit 16. The wireless transmission / reception unit 10 is also referred to as a transmission unit, a reception unit, a monitoring unit, or a physical layer processing unit. The upper layer processing unit 14 is also referred to as a measurement unit, a selection unit, or a control unit 14.

[0279] 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 wireless transceiver unit 10. The upper layer processing unit 14 performs part or all of the processing of the Medium Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and 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 values of the respective reference signals. 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. When the bit information included in the information instructing the start of the random access procedure received by the wireless transceiver unit 10 is a predetermined value, the upper layer processing unit 14 may specify one index from one or more indexes set in the upper layer (for example, the RRC layer) and set it to the preamble index. The upper layer processing unit 14 may have a function of specifying the index associated with the selected reference signal from one or more indexes set in the RRC and setting it to the preamble index. The upper layer processing unit 14 may have a function of determining the next available PRACH opportunity based on the received information (for example, 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 the received information (for example, SSB index information).

[0280] The MAC layer processing unit 15 included in the upper layer processing unit 14 performs the processing of the MAC layer (Medium Access Control layer). The MAC layer processing unit 15 controls the transmission of scheduling requests based on various setting information / parameters managed by the radio resource control layer processing unit 16.

[0281] The wireless resource control layer processing unit 16, located in the upper layer processing unit 14, performs processing at the RRC layer (wireless resource control layer). The wireless resource control layer processing unit 16 manages various setting information / parameters of its own device. The wireless resource control layer processing unit 16 sets various setting information / parameters based on the upper layer signals received from the base station device 3. In other words, the wireless 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 wireless resource control layer processing unit 16 controls (specifies) resource allocation based on the downlink control information received from the base station device 3.

[0282] The wireless transceiver 10 performs physical layer processing such as modulation, demodulation, coding, and decoding. The wireless transceiver 10 separates, demodulates, and decodes the 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 coding the data and transmits it to the base station device 3. The wireless transceiver 10 may have a function to receive one or more reference signals in a certain cell. The wireless transceiver 10 may have a function to receive information that identifies one or more PRACH opportunities (e.g., SSB index information and / or mask index information). The wireless transceiver 10 may have a function to receive a signal containing instruction information that instructs the start of a random access procedure. The wireless transceiver 10 may have a function to receive information that identifies a predetermined index. The wireless transceiver 10 may have a function to receive information that identifies the index of a random access prinble. The wireless transceiver 10 may have a function to transmit a random access preamble at a PRACH opportunity determined by the upper layer processing unit 14.

[0283] The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (downconvert), removing unwanted frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit.

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

[0285] 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 to generate 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.

[0286] The RF unit 12 removes extraneous frequency components from the analog signal input from the baseband unit 13 using a low-pass filter, upconverts the analog signal to the carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 also amplifies the power. The RF unit 12 may also have a function to determine the transmission power of the uplink signal and / or uplink channel to be transmitted in the cell in service. The RF unit 12 is also referred to as the transmission power control unit.

[0287] Figure 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 is composed of a wireless transceiver unit 30 and a higher layer processing unit 34. The wireless transceiver unit 30 is composed of an antenna unit 31, an RF unit 32, and a baseband unit 33. The higher layer processing unit 34 is composed of a media access control layer processing unit 35 and a wireless resource control layer processing unit 36. The wireless transceiver unit 30 is also referred to as the transmitting unit, receiving unit, monitoring unit, or physical layer processing unit. A separate control unit may also be provided to control the operation of each unit based on various conditions. The higher layer processing unit 34 is also referred to as the control unit 34.

[0288] The upper layer processing unit 34 performs some or all of the processing in the Medium Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Radio Resource Control (RRC) layer. The upper layer processing unit 34 may also have a function to identify one reference signal from one or more reference signals based on the random access preamble received by the wireless transceiver unit 30. The upper layer processing unit 34 may also identify a PRACH opportunity to monitor the random access preamble from at least the SSB index information and the mask index information.

[0289] The media access control layer processing unit 35, located in the upper layer processing unit 34, performs MAC layer processing. The media access control layer processing unit 35 processes scheduling requests based on various setting information / parameters managed by the wireless resource control layer processing unit 36.

[0290] The wireless resource control layer processing unit 36, located in the upper layer processing unit 34, performs RRC layer processing. The wireless resource control layer processing unit 36 ​​generates downlink control information (uplink grant, downlink grant) including resource allocation information for the terminal device 1. The wireless resource control layer processing unit 36 ​​generates or obtains downlink control information, downlink data (transport block, random access response) placed on the physical downlink shared channel, system information, RRC messages, MAC CE (Control Element), etc., from the upper layer node and outputs them to the wireless transceiver unit 30. The wireless resource control layer processing unit 36 ​​also manages various setting information / parameters for each terminal device 1. The wireless resource control layer processing unit 36 ​​may set various setting information / parameters for each terminal device 1 via signals from the upper layer. That is, the wireless resource control layer processing unit 36 ​​transmits / notifies information indicating various setting information / parameters. The wireless resource control layer processing unit 36 ​​may transmit / notify information for identifying the setting of one or more reference signals in a certain cell.

[0291] When the base station device 3 sends an RRC message, MAC CE, and / or PDCCH to the terminal device 1, and the terminal device 1 processes based on its reception, the base station device 3 performs its processing (controlling the terminal device 1 and the system) assuming that the terminal device is performing that processing. In other words, the base station device 3 sends an RRC message, MAC CE, and / or PDCCH to the terminal device 1 to cause the terminal device to perform processing based on its reception.

[0292] The wireless transceiver 30 has the function of transmitting one or more reference signals. The wireless transceiver 30 may also have the function of receiving signals including beam failure recovery requests transmitted from the terminal device 1. The wireless transceiver 30 may have the function of transmitting information (e.g., SSB index information and / or mask index information) that identifies one or more PRACH opportunities to the terminal device 1. The wireless transceiver 30 may have the function of transmitting information that identifies a predetermined index. The wireless transceiver 30 may have the function of transmitting information that identifies the index of the random access preamble. The wireless transceiver 30 may have the function of monitoring the random access preamble at PRACH opportunities identified by the upper layer processing unit 34. Some functions of the wireless transceiver 30 are the same as those of the wireless transceiver 10 and are therefore omitted from the description. Note that if the base station device 3 is connected to one or more transmission / reception points 4, some or all of the functions of the wireless transceiver 30 may be included in each transmission / reception point 4.

[0293] Furthermore, the upper-layer processing unit 34 transmits (transmits) or receives control messages or user data between base station devices 3 or between higher-level network devices (MME, S-GW (Serving-GW)) and base station devices 3. In Figure 16, other components of the base station device 3 and the transmission paths of data (control information) between components are omitted, but it is clear that it has multiple blocks as components that have other functions necessary to operate as a base station device 3. For example, the upper-layer processing unit 34 may include a Radio Resource Management layer processing unit and an Application layer processing unit. The upper-layer processing unit 34 may also have the function of setting multiple scheduling request resources corresponding to each of the multiple reference signals transmitted from the wireless transceiver unit 30.

[0294] In the diagram, "parts" can also be expressed by terms such as section, circuit, component, device, or unit, and represent elements that realize the functions and procedures of terminal device 1 and base station device 3.

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

[0296] (1) More specifically, the terminal device 1 in the first aspect of the present invention comprises a receiving unit 10 that receives a PDSCH including a RAR message, and a control unit 16 that controls resource allocation based on a first field indicating a Msg3 PUSCH frequency resource assignment shown 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 less than or equal to a predetermined number of resource blocks, and inserts the most significant bit of the Y bit, which is set to a value of '0' after the 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 the type of random access procedure.

[0297] (2) In the first embodiment of the present invention, when the type of random access procedure is a non-competition-based random access procedure, the number of first resource blocks is the number of resource blocks representing the bandwidth of the active UL BWP.

[0298] (3) In the first embodiment of the present invention, when the type of the random access procedure is a competition-based random access procedure, the number of the first resource blocks is the number of resource blocks representing the bandwidth of the initial UL BWP.

[0299] (4) The base station device 3 in a second aspect of the present invention comprises a control unit 36 ​​that generates a first UL grant including a first field indicating a resource allocation Msg3 PUSCH frequency resource assignment, and a transmission unit 30 that transmits a PDSCH including a RAR message including the first UL grant, 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 less than or equal to a predetermined number of resource blocks, and inserts the most significant bit of the Y bit, which is set to a value of '0' after the 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 the type of random access procedure.

[0300] (5) In a second embodiment of the present invention, when the type of random access procedure is a non-contradiction-based random access procedure, the number of the first resource blocks is the number of resource blocks representing the bandwidth of the active UL BWP.

[0301] (6) In a second embodiment of the present invention, when the type of the random access procedure is a competition-based random access procedure, the number of the first resource blocks is the number of resource blocks representing the bandwidth of the initial UL BWP.

[0302] (7) A terminal device 1 performing a competition-based random access procedure according to a third aspect of the present invention comprises a receiving unit 10 that receives a PDSCH including a RAR message, and a control unit 16 that controls resource allocation based on a first field indicating the Msg3 PUSCH frequency resource assignment shown in the 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 less than or equal to a predetermined number of resource blocks, and inserts the most significant bit of the Y bit, which is set to a value of '0' after the 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 a UL having the same BWP identifier as the DL BWP in which the setting information of the CORESET shown in the Type 1 PDCCH common search space set is set The number of resource blocks represents the bandwidth of the BWP, the Type 1 PDCCH common search space set is a search space set used for random access procedures, and the CORESET is a time and frequency resource for searching downlink control information.

[0303] (8) A base station device 3 that communicates with a terminal device 1 performing a competition-based random access procedure according to a fourth aspect of the present invention comprises a control unit 36 ​​that generates a first UL grant including a first field indicating a resource allocation Msg3 PUSCH frequency resource assignment, and a transmission unit 30 that transmits a PDSCH including a RAR message, wherein 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 less than or equal to a predetermined number of resource blocks, and inserts the most significant bit of the Y bit set to '0' after the 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 a UL having the same BWP identifier as the DL BWP in which the setting information of the CORESET shown in the type 1 PDCCH common search space set is set The number of resource blocks represents the bandwidth of the BWP, the Type 1 PDCCH common search space set is a search space set used for random access procedures, and the CORESET is a time and frequency resource for searching downlink control information.

[0304] (9) A terminal device 1 in a fifth aspect of the present invention comprises a receiving unit 10 that receives a first DCI format scrambled by TC-RNTI in a search space set, and a control unit 16 that identifies a resource allocation for PUSCH based on a second field indicating a frequency domain resource allocation included in the first DCI format, wherein the bits of the first field indicating the Msg3 PUSCH frequency resource allocation shown in the first UL grant included in the 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 the bandwidth of the first UL BWP, the size of the second field is derived from the bandwidth of the initial UL BWP, and the control unit identifies a frequency-direction resource block allocation to apply to the first UL BWP based on the RIV value shown in the second field.

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

[0306] (11) In a fifth aspect of the present invention, the control unit identifies a first starting position for resource allocation and a number of sequentially allocated first resource blocks based on the initial UL BWP from the value of RIV shown in the second field, and applies the identified first starting position and the number of first resource blocks to the physical resource blocks of the initial UL BWP to identify the resource allocation of PUSCH.

[0307] (12) In a fifth aspect of the present invention, when the first UL BWP is an initial UL BWP, the first starting position of resource allocation and the number of sequentially allocated first resource blocks are identified from the value of RIV shown in the second field based on the initial UL BWP, and the identified first starting position and the number of first resource blocks are applied to the physical resource blocks of the initial UL BWP to identify the resource allocation of PUSCH.

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

[0309] (14) A base station device 3 in a sixth aspect of the present invention comprises 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 TC-RNTI, and 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 shown in the first UL grant included in the 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 the initial UL BWP, and the control unit identifies the frequency-direction resource block allocation of the PUSCH of the first UL BWP to be applied to a terminal device and generates a value of RIV shown in the second field.

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

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

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

[0313] (18) In a sixth aspect of the present invention, the coefficient K is given by a value rounded down to the nearest power of 2 in the ratio of the bandwidth of the active UL BWP to the bandwidth of the initial UL BWP when the bandwidth of the active UL BWP is larger than the bandwidth of the initial UL BWP, and is given by 1 in other cases.

[0314] As a result, the terminal device 1 can communicate with the base station device 3 efficiently.

[0315] The program that operates in the device according to the present invention may be a program that controls the Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of the embodiment according to the present invention. The program or the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, a Hard Disk Drive (HDD), or other storage system.

[0316] Furthermore, a program for realizing the functions of the embodiments related to the present invention may be recorded on a computer-readable recording medium. This can also be realized by loading the program recorded on this recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be 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.

[0317] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An electrical 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, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuit may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of the present invention may also utilize new integrated circuits based on such technologies.

[0318] In the embodiments relating to the present invention, an example of application to a communication system consisting of a base station device and a terminal device has been described, but it is also applicable to systems in which terminals communicate with each other, such as D2D (Device to Device).

[0319] It should be noted that the present invention is not limited to the embodiments described above. Although the embodiments describe an example of a device, the present invention is not limited thereto and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0320] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this 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 this invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included.

Claims

1. A terminal device that communicates with a base station device, comprising: a receiver that receives an initial uplink (UL) band 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 an RAR UL grant; and a transmitter that transmits a PUSCH (Physical Uplink Shared Channel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate allocation of frequency resources for the PUSCH, and whether to truncate the first field or insert a bit into the first field is based on the bandwidth of the initial UL BWP.

2. A base station device communicating with a terminal device, comprising: a transmitter that transmits an initial uplink (UL) band portion (BWP) configuration and an additional UL BWP configuration via a radio resource control (RRC) message and transmits a random access response (RAR) message including an RAR UL grant; and a receiver that receives a PUSCH (Physical Uplink Shared CHannel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate allocation of frequency resources for the PUSCH, and whether the first field is truncated by the terminal device or a bit is inserted into the first field by the terminal device is based on the bandwidth of the initial UL BWP. Base station equipment.

3. A communication method in a terminal device that communicates with a base station device, comprising: a step of receiving an initial uplink (UL) band portion (BWP) configuration and an additional UL BWP configuration via a radio resource control (RRC) message; a step of receiving a random access response (RAR) message including an RAR UL grant; and a step of transmitting a PUSCH (Physical Uplink Shared Channel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate allocation of frequency resources for the PUSCH, and whether to truncate the first field or insert a bit into the first field is based on the bandwidth of the initial UL BWP.

4. A communication method in a base station device that communicates with a terminal device, comprising: a step of transmitting an initial uplink (UL) band portion (BWP) configuration and an additional UL BWP configuration via a Radio Resource Control (RRC) message; a step of transmitting a Random Access Response (RAR) message including an RAR UL grant; and a step of receiving a PUSCH (Physical Uplink Shared CHannel) in an active UL BWP, wherein one of the initial UL BWP and the additional UL BWP is activated as the active UL BWP, the PUSCH is scheduled by the RAR UL grant, a first field included in the RAR UL grant is used to indicate allocation of frequency resources for the PUSCH, and whether the first field is truncated by the terminal device or a bit is inserted into the first field by the terminal device is determined by the initial UL message. A communication method based on the bandwidth of the BWP.

Images