Base station device, terminal device, and communication method

Abstract

A terminal device comprises: a receiving unit, which receives a MIB for setting a first CORESET, receives a SIB1 for setting a second CORESET, receives first information for setting an initial UL BWP and second information for setting an additional UL BWP, and receives a first DCI format for scheduling a PUSCH in a common search space; and a sending unit, which determines a set of allocated resource blocks based on a first field included in the first DCI format, and sends the PUSCH through an activated UL BWP, wherein the activated UL BWP is any one of the initial ULBWP and the additional UL BWP, wherein a first value represented by the first field is given based on the size of the initial UL BWP, a first starting position as the starting position of the set of allocated resource blocks, and the number of first resource blocks allocated continuously, and wherein the common search space is used for a random access process.

Description

Technical Field

[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-134079 filed in Japan on July 17, 2018, and the contents thereof are incorporated herein by reference. Background Art

[0002] Currently, as wireless access methods and wireless network technologies for the fifth-generation cellular system, the Third Generation Partnership Project (3GPP) is conducting technical research and standardization on LTE (Long Term Evolution)-Advanced Pro (LTE's extended standard, namely LTE-A Pro) and NR (New Radiotechnology) (Non-Patent Document 1).

[0003] In the fifth-generation cellular system, the following three scenarios are requested as hypothetical service scenarios: eMBB (enhanced Mobile BroadBand) for high-speed / large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) for low-latency / high-reliability communication, and mMTC (massive Machine Type Communication) for a large number of machine-type devices such as IoT (Internet of Things).

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-patent document 1: RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology,” June 2016 Summary of the invention

[0007] Problem that the invention aims to solve

[0008] 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 can efficiently perform communication in the above-mentioned wireless communication system.

[0009] Technical Solution

[0010] (1) In order to achieve the above-mentioned purpose, the scheme of the present invention adopts the following scheme. That is, a terminal device of one scheme of the present invention comprises: a receiving unit, receiving the MIB for setting the first control resource set (CORESET), receiving the SIB1 for setting the second CORESET, receiving the first information for setting the initial uplink portion bandwidth (UL BWP) and the second information for setting the additional ULBWP, and receiving the first DCI format P for scheduling PUSCH in the common search space; and a sending unit, determining the set of allocated resource blocks based on the first field included in the first DCI format, and sending the PUSCH through the activated UL BWP, wherein the activated UL BWP is any one of the initial UL BWP and the additional UL BWP that is activated, and when the common search space is the first common search space, the first value represented by the first field is based on the initial UL The first common search space is a common search space used for a random access process. The CORESET associated with the first common search space may be a first CORESET or a second CORESET. The first starting position is the starting position of the set of allocated resource blocks. The number of the first resource blocks is the number of continuously allocated resource blocks in the set of allocated resource blocks.

[0011] (2) In addition, a base station device that communicates with a terminal device according to one embodiment of the present invention comprises: a sending unit, which sends a MIB for setting a first control resource set (CORESET), sends a SIB1 for setting a second CORESET, sends first information for setting an initial uplink partial bandwidth (UL BWP) and second information for setting an additional UL BWP, generates a first field based on a set of resource blocks to be allocated to the terminal device, and sends a first DCI format including the generated first field in a common search space; and a receiving unit, which receives a PUSCH through an activated UL BWP, wherein the activated ULBWP for the terminal device is any one of the initial UL BWP and the additional UL BWP that is activated, and when the common search space is the first common search space, the first value represented by the first field is based on the initial UL The first common search space is a common search space used for a random access process. The CORESET associated with the first common search space may be a first CORESET or a second CORESET. The first starting position is the starting position of the set of allocated resource blocks. The number of the first resource blocks is the number of continuously allocated resource blocks in the set of allocated resource blocks.

[0012] (3) In addition, a communication method of one embodiment of the present invention is a communication method of a terminal device, receiving a MIB for setting a first control resource set (CORESET), receiving a SIB1 for setting a second CORESET, receiving first information for setting an initial uplink portion bandwidth (UL BWP) and second information for setting an additional UL BWP, receiving a first DCI format for scheduling a PUSCH in a common search space, determining a set of allocated resource blocks based on a first field included in the first DCI format, sending the PUSCH through an activated UL BWP, the activated UL BWP being any one of the initial UL BWP and the additional UL BWP being activated, and when the common search space is the first common search space, a first value represented by the first field is based on the initial UL BWP. The first common search space is a common search space used for a random access process. The CORESET associated with the first common search space may be a first CORESET or a second CORESET. The first starting position is the starting position of the set of allocated resource blocks. The number of the first resource blocks is the number of continuously allocated resource blocks in the set of allocated resource blocks.

[0013] (4) In addition, a communication method of one embodiment of the present invention is a communication method of a base station device communicating with a terminal device, sending a MIB for setting a first control resource set (CORESET), sending a SIB1 for setting a second CORESET, sending first information for setting an initial uplink partial bandwidth (UL BWP) and second information for setting an additional UL BWP, generating a first field based on a set of resource blocks to be allocated to the terminal device, sending a first DCI format including the generated first field in a common search space, receiving a PUSCH through an activated UL BWP, wherein the activated ULBWP for the terminal device is any one of the initial UL BWP and the additional UL BWP that is activated, and when the common search space is the first common search space, a first value represented by the first field is based on the initial UL BWP. The first common search space is a common search space used for a random access process. The CORESET associated with the first common search space may be a first CORESET or a second CORESET. The first starting position is the starting position of the set of allocated resource blocks. The number of the first resource blocks is the number of continuously allocated resource blocks in the set of allocated resource blocks.

[0014] (5) In addition, an integrated circuit of one embodiment of the present invention is an integrated circuit installed in a terminal device, which enables the terminal device to perform the following functions: receive a MIB for setting a first control resource set (CORESET), receive a SIB1 for setting a second CORESET, receive first information for setting an initial uplink portion bandwidth (UL BWP) and second information for setting an additional ULBWP, receive a first DCI format for scheduling a PUSCH in a common search space; and determine a set of allocated resource blocks based on a first field included in the first DCI format, send the PUSCH through an activated UL BWP, the activated UL BWP being any one of the initial UL BWP and the additional UL BWP being activated, and when the common search space is the first common search space, the first value represented by the first field is based on the initial UL The first common search space is a common search space used for a random access process. The CORESET associated with the first common search space may be a first CORESET or a second CORESET. The first starting position is the starting position of the set of allocated resource blocks. The number of the first resource blocks is the number of continuously allocated resource blocks in the set of allocated resource blocks.

[0015] (6) In addition, an integrated circuit of one embodiment of the present invention is an integrated circuit installed in a base station device that communicates with a terminal device, which enables the base station device to perform the following functions: sending an MIB for setting a first control resource set (CORESET), sending an SIB1 for setting a second CORESET, sending first information for setting an initial uplink partial bandwidth (UL BWP) and second information for setting an additional UL BWP, generating a first field based on a set of resource blocks to be allocated to the terminal device, and sending a first DCI format including the generated first field in a common search space; and receiving a PUSCH through an activated ULBWP, wherein the activated UL BWP for the terminal device is any one of the initial UL BWP and the additional ULBWP that is activated, and when the common search space is the first common search space, the first value represented by the first field is based on the initial UL The first common search space is a common search space used for a random access process. The CORESET associated with the first common search space may be a first CORESET or a second CORESET. The first starting position is the starting position of the set of allocated resource blocks. The number of the first resource blocks is the number of continuously allocated resource blocks in the set of allocated resource blocks.

[0016] Beneficial Effects

[0017] According to one aspect of the present invention, a base station apparatus and a terminal apparatus can communicate efficiently. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a diagram showing the concept of a wireless communication system according to an embodiment of the present invention.

[0019] Figure 2 2 is a diagram showing an example of an SS / PBCH block and an SS burst set according to an embodiment of the present invention.

[0020] Figure 3 This is a diagram showing an example of a schematic configuration of uplink and downlink time slots according to an embodiment of the present invention.

[0021] Figure 4 It is a diagram showing the relationship between subframes, slots, and mini slots in the time domain according to the embodiment of the present invention.

[0022] Figure 5 This is a diagram showing an example of a time slot or a subframe according to an embodiment of the present invention.

[0023] Figure 6 This is a diagram showing an example of beamforming according to an embodiment of the present invention.

[0024] Figure 7 This is a diagram showing an example of BWP setting according to the embodiment of the present invention.

[0025] Figure 8 It is a diagram showing an example of a random access procedure of the terminal device 1 according to the embodiment of the present invention.

[0026] Fig. 9 It is a diagram showing an example of fields included in the RAR UL Grant according to an embodiment of the present invention.

[0027] Fig.10 This is a diagram showing an example of interpretation of the field “Msg3 PUSCH frequency resource allocation” according to the present embodiment.

[0028] Fig.11 This is a diagram showing an example of uplink resource allocation type 1 for BWP according to the present embodiment.

[0029] Fig.12 FIG. 1 is a diagram showing an example of calculating the RIV according to the embodiment of the present invention.

[0030] Fig.13 This is a diagram showing an example of allocation of SSB indices for PRACH opportunities according to the present embodiment.

[0031] Fig.14 It is a flowchart showing an example of a random access procedure of a MAC entity according to an embodiment of the present invention.

[0032] Fig.15 It is a schematic block diagram showing the configuration of the terminal device 1 according to the embodiment of the present invention.

[0033] Fig.16 It is a schematic block diagram showing the configuration of the base station device 3 according to the embodiment of the present invention. DETAILED DESCRIPTION

[0034] Hereinafter, embodiments of the present invention will be described.

[0035] Figure 1 is a conceptual diagram of a wireless communication system according to this embodiment. Figure 1 In the wireless communication system, a terminal device 1A, a terminal device 1B, and a base station device 3 are provided. Hereinafter, the terminal device 1A and the terminal device 1B are also referred to as the terminal device 1.

[0036] The terminal device 1 is also called a user terminal, a mobile station device, a communication terminal, a mobile device, a terminal, a UE (User Equipment), and an MS (Mobile Station). The base station device 3 is also called a wireless base station device, a base station, a wireless base station, a fixed station, an NB (NodeB), an eNB (evolved NodeB), a BTS (Base Transceiver Station), a BS (Base Station), an NR NB (NR Node B), an NNB, a TRP (Transmission and Reception Point), and a gNB. The base station device 3 may also include a core network device. In addition, the base station device 3 may have one or more transmission reception points 4. At least a part of the functions / processing of the base station device 3 described below may be the functions / processing of each transmission reception point 4 possessed by the base station device 3. The base station device 3 may serve the terminal device 1 as one or more cells in the communicable range (communication area) controlled by the base station device 3. In addition, the base station device 3 may also use the communicable range (communication area) controlled by one or more transceiver points 4 as one or more cells to serve the terminal device 1. In addition, one cell may be divided into a plurality of local areas (Beamed area: beam range), and the terminal device 1 may be served in each local area. Here, the local area can be identified based on the index of the beam used in beamforming or the index of precoding.

[0037] A wireless communication link from the base station device 3 to the terminal device 1 is referred to as a downlink. A wireless communication link from the terminal device 1 to the base station device 3 is referred to as an uplink.

[0038] exist Figure 1 In the wireless communication between the terminal device 1 and the base station device 3, orthogonal frequency division multiplexing (OFDM: Orthogonal Frequency Division Multiplexing) including cyclic prefix (CP: Cyclic Prefix), single carrier frequency division multiplexing (SC-FDM: Single-Carrier Frequency Division Multiplexing), discrete Fourier transform spread OFDM (DFT-S-OFDM: Discrete Fourier Transform Spread OFDM) and multi-carrier code division multiplexing (MC-CDM: Multi-Carrier Code Division Multiplexing) can be used.

[0039] In addition, Figure 1 In the wireless communication between the terminal device 1 and the base station device 3, universal-filtered multi-carrier (UFMC), filtered OFDM (F-OFDM: FilteredOFDM), windowed OFDM (Windowed OFDM) and filter bank multi-carrier (FBMC: Filter-Bank Multi-Carrier) can also be used.

[0040] It should be noted that, in the present embodiment, OFDM is used as the transmission method and OFDM symbols are used for description, but the present invention also includes the case where the above-mentioned other transmission methods are used.

[0041] In addition, Figure 1 In the wireless communication between the terminal device 1 and the base station device 3, the CP may not be used, or the above transmission method with zero padding may be used instead of the CP. In addition, the CP and the zero padding may be added to both the front and rear sides.

[0042] One scheme of the present embodiment can operate in carrier aggregation or dual connection of a radio access technology (RAT: Radio Access Technology) called LTE, LTE-A / LTE-A Pro. In this case, it can be used for a part or all of the cells or cell groups, carriers or carrier groups (for example, primary cell (PCell: Primary Cell), secondary cell (SCell: Secondary Cell), primary and secondary cells (PSCell), MCG (Master Cell Group), SCG (Secondary Cell Group), etc.). In addition, it can also be used for independent deployment of single operation. In dual connection operation, SpCell (SpecialCell) is called PCell of MCG or PSCell of SCG, depending on whether the MAC (MAC: Medium Access Control: Media Access Control) entity is associated with MCG or SCG. If it is not a dual link operation, SpCell (SpecialCell) is called PCell. SpCell (Special Cell) supports PUCCH transmission and competitive random access.

[0043] In this embodiment, one or more service cells may be set for the terminal device 1. The multiple service cells that are set may include a primary cell and one or more secondary cells. The primary cell may be a service cell that has performed an initial connection establishment process, a service cell that has started a connection re-establishment process, or a cell that is indicated as a primary cell during a switching process. One or more secondary cells may be set at or after an RRC (Radio Resource Control) connection is established. However, the multiple service cells that are set may include a primary and secondary cell. The primary and secondary cells may be secondary cells that can send control information in the uplink among the one or more secondary cells for which the terminal device 1 is set. In addition, subsets of two types of service cells, namely a primary cell group and a secondary cell group, may also be set for the terminal device 1. The primary cell group may be composed of one primary cell and zero or more secondary cells. The secondary cell group may be composed of one primary and secondary cell and zero or more secondary cells.

[0044] The wireless communication system of this embodiment can apply TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). The TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method can be applied to all multiple cells. In addition, the cell applying the TDD method can also be aggregated with the cell applying the FDD method. The TDD method can also be called unpaired spectrum operation. The FDD method can also be called paired spectrum operation.

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

[0046] The physical channels and physical signals of this embodiment are described.

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

[0048] PBCH (Physical Broadcast CHannel)

[0049] PDCCH (Physical Downlink Control CHannel: Physical Downlink Control Channel)

[0050] PDSCH (Physical Downlink Shared CHannel: Physical Downlink Shared Channel)

[0051] PUCCH (Physical Uplink Control CHannel: Physical Uplink Control Channel)

[0052] PUSCH (Physical Uplink Shared CHannel: Physical Uplink Shared Channel)

[0053] PRACH (Physical Random Access CHannel)

[0054] The PBCH is a channel for broadcasting important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1 .

[0055] In addition, PBCH can be used for the time index within the period of the block (also called SS / PBCH block) of the broadcast synchronization signal. Here, the time index is information indicating the index of the synchronization signal and PBCH within the cell. For example, in the case of transmitting the SS / PBCH block using the assumption of three transmit beams (transmit filter settings, quasi co-location (QCL: Quasi Co-Location) related to the receiving spatial parameters), the time sequence within a pre-set period or a set period can be represented. In addition, the terminal device can identify the difference in time index as the difference in transmit beams.

[0056] PDCCH is used to send (or transport) downlink control information (Downlink Control Information: DCI) in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). Here, one or more DCIs (also referred to as DCI formats) are defined for the transmission of downlink control information. That is, the field for the downlink control information is defined as DCI and mapped to information bits. PDCCH is sent in PDCCH candidates. The terminal device 1 monitors a set of PDCCH candidates in the serving cell. Monitoring means attempting to decode the PDCCH according to a certain DCI format.

[0057] For example, the following DCI format may be defined.

[0058] DCI format 0_0

[0059] DCI format 0_1

[0060] DCI format 1_0

[0061] DCI format 1_1

[0062] DCI format 2_0

[0063] DCI format 2_1

[0064] DCI format 2_2

[0065] DCI format 2_3

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

[0067] DCI format 0_1 ​​may include: information indicating scheduling information of PUSCH (frequency domain resource allocation and time domain resource allocation), information indicating partial bandwidth (BWP: BandWidth Part), channel state information (CSI: Channel StateInformation) request, sounding reference signal (SRS: Sounding Reference Signal) request, and information related to antenna ports.

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

[0069] DCI format 1_1 may include: information indicating scheduling information (frequency domain resource allocation and time domain resource allocation) of PDSCH, information indicating a partial bandwidth (BWP), a transmission configuration indication (TCI: Transmission Configuration Indication), and information related to antenna ports.

[0070] DCI format 2_0 is used to notify the time slot format of one or more time slots. The time slot format is defined as each OFDM symbol in the time slot is classified as any one of downlink, variable, and uplink. For example, when the time slot format is 28, DDDDDDDDDDDDFU is applied to the OFDM symbols of 14 symbols in the time slot indicating the time slot format 28. Here, D is a downlink symbol, F is a variable symbol, and U is an uplink symbol. It should be noted that the time slot will be described later.

[0071] DCI format 2_1 is used to notify the terminal device 1 of physical resource blocks and OFDM symbols that can be assumed not to be transmitted. It should be noted that this information can also be called a preemption indication (intermittent transmission indication).

[0072] DCI format 2_2 is used to transmit PUSCH and a transmit power control (TPC: Transmit Power Control) command for PUSCH.

[0073] DCI format 2_3 is used to send a group of TPC commands for sending a sounding reference signal (SRS) implemented by one or more terminal devices 1. In addition, an SRS request can be sent together with the TPC command. In addition, in DCI format 2_3, an SRS request and a TPC command can be defined for an uplink without PUSCH and PUCCH or an uplink in which the transmission power control of the SRS is not associated with the transmission power control of the PUSCH.

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

[0075] The CRC (Cyclic Redundancy Check) parity bits attached to the DCI format sent via a PDCCH can be scrambled by 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 (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 has sent a random access preamble in a contention based random access procedure.

[0076] C-RNTI (identifier (identification information) of the terminal device) is used to control PDSCH or PUSCH in one or more time 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 time 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 based on the frequency and time location information of the physical random access channel where the random access preamble is transmitted.

[0077] PUCCH is used to send uplink control information (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: Channel State Information) for indicating the state of the downlink channel. In addition, the uplink control information may include a scheduling request (SR: Scheduling Request) for requesting UL-SCH resources. In addition, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement). HARQ-ACK can represent HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol DataUnit: MAC PDU (Media Access Control Protocol Data Unit), Downlink-Shared Channel: DL-SCH (Downlink Shared Channel)).

[0078] The PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the media access (MAC: Medium Access Control) layer. In addition, in the case of downlink, it is also used to transmit system information (SI: System Information), random access response (Random Access Response: RAR), etc.

[0079] PUSCH can be used to transmit HARQ-ACK and / or CSI together with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. In addition, it can also be used to transmit only CSI or only HARQ-ACK and CSI. In other words, it can also be used to transmit only UCI.

[0080] Here, the base station device 3 and the terminal device 1 exchange (transmit and receive) signals at the upper layer (upper layer: higher layer). For example, the base station device 3 and the terminal device 1 can transmit and receive RRC signaling (also called RRC message: Radio Resource Control message, RRC information: Radio Resource Control information) at the radio resource control (RRC: Radio Resource Control) layer. In addition, the base station device 3 and the terminal device 1 can also transmit and receive MAC control elements at the MAC (Medium Access Control: Media Access Control) layer. Here, RRC signaling and / or MAC control elements are also referred to as upper layer signals (upper layer signals: higher layersignaling). The upper layer here means the upper layer observed from the physical layer, and therefore, it can include one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum: Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the upper layer can include one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.

[0081] PDSCH or PUSCH can be used to send RRC signaling and MAC control elements. Here, in PDSCH, the RRC signaling sent from the base station device 3 can be signaling shared by multiple terminal devices 1 in the cell. In addition, the RRC signaling sent from the base station device 3 can also be signaling dedicated to a certain terminal device 1 (also called dedicated signaling). That is, dedicated signaling can be used to send terminal device-specific (UE-specific) information to a certain terminal device 1. In addition, PUSCH can be used to send UE capabilities (UE Capability) in the uplink.

[0082] exist Figure 1 In the wireless communication of the downlink, the following downlink physical signal is used. Here, the downlink physical signal is not used to transmit information output from the upper layer, but is used by the physical layer.

[0083] Synchronization signal (SS)

[0084] Reference Signal (RS)

[0085] The synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). The PSS and SSS may be used to detect a cell ID.

[0086] The synchronization signal is used for the terminal device 1 to obtain synchronization in the frequency domain and time domain of the downlink. Here, the synchronization signal can be used for the terminal device 1 to select the precoding or beam in the precoding or beamforming performed by the base station device 3. It should be noted that the beam can also be referred to as a transmit or receive filter setting, or a spatial domain transmit filter or a spatial domain receive filter.

[0087] The reference signal is used for the terminal device 1 to perform transmission path compensation of the physical channel. Here, the reference signal can also be used for the terminal device 1 to calculate the CSI of the downlink. In addition, the reference signal can be used for fine synchronization, which is fine synchronization that can achieve a degree of fine synchronization such as wireless parameters, subcarrier spacing and other parameter sets and FFT window synchronization.

[0088] In this embodiment, any one or more of the following downlink reference signals are used.

[0089] DMRS (Demodulation Reference Signal)

[0090] CSI-RS (Channel State Information Reference Signal)

[0091] PTRS (Phase Tracking Reference Signal)

[0092] TRS (Tracking Reference Signal)

[0093] DMRS is used to demodulate the modulated signal. It should be noted that two types of reference signals, a reference signal for demodulating PBCH and a reference signal for demodulating PDSCH, can be defined in DMRS, and both can be referred to as DMRS. CSI-RS is used for measuring channel state information (CSI: Channel State Information) and beam management, and a periodic, semi-static or non-periodic CSI reference signal transmission method is applied. For CSI-RS, non-zero power (NZP: Non-Zero Power) CSI-RS and zero transmission power (or receiving power) (zero power (ZP: Zero Power)) CSI-RS can be defined. Here, ZP CSI-RS can be defined as a CSI-RS resource with zero transmission power or not transmitted. PTRS is used to track the phase on the time axis to ensure the frequency offset caused by phase noise. TRS is used to ensure Doppler shift during high-speed movement. It should be noted that TRS can be used as a setting for CSI-RS. For example, the CSI-RS of a port can also be used as TRS to set wireless resources.

[0094] In this embodiment, any one or more of the following uplink reference signals are used.

[0095] DMRS (Demodulation Reference Signal)

[0096] PTRS (Phase Tracking Reference Signal)

[0097] SRS (Sounding Reference Signal)

[0098] DMRS is used to demodulate modulated signals. It should be noted that two types of reference signals, one for demodulating PUCCH and one for demodulating PUSCH, can be defined in DMRS, and both can be referred to as DMRS. SRS is used for uplink channel state information (CSI) measurement, channel detection, and beam management. PTRS is used to track the phase on the time axis to ensure the frequency offset caused by phase noise.

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

[0100] BCH, UL-SCH and DL-SCH are transport channels. The channels used in the medium access control (MAC) layer are called transport channels. The units of transport channels used in the MAC layer are also called transport blocks (TB) and / or MAC PDU (Protocol Data Unit). HARQ (Hybrid Automatic Repeat reQuest) is controlled for each transport block in the MAC layer. The transport block is the unit of data that the MAC layer delivers to the physical layer. In the physical layer, the transport block is mapped to the codeword, and the encoding process is performed for each codeword.

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

[0102] The SS / PBCH block is a unit block including at least synchronization signals (PSS, SSS) and / or PBCH. The signal / channel included in the transmission SS / PBCH block is expressed as the transmission SS / PBCH block. When one or more SS / PBCH blocks in the SS burst set are used to transmit the synchronization signal and / or PBCH, the base station device 3 can use a downlink transmission beam independent of each SS / PBCH block.

[0103] exist Figure 2 In the SS / PBCH block, the PSS, SSS, and PBCH are time-division multiplexed / frequency-division multiplexed. The order in which the PSS, SSS, and / or PBCH are multiplexed in the time domain can be the same as Figure 2 The examples shown in are different.

[0104] The SS burst set can be sent periodically. For example, a period for initial access and a period set for a connected (Connected or RRC_Connected) terminal device can be defined. In addition, the period set for a connected (Connected or RRC_Connected) terminal device can be set at the RRC layer. In addition, the period set for a connected (Connected or RRC_Connected) terminal is a period of wireless resources in the time domain that may potentially be sent, and it can actually be determined whether it is sent by the base station device 3. In addition, the period for initial access can be pre-defined in a specification book, etc.

[0105] The SS burst set may be determined based on a system frame number (SFN: System Frame Number). In addition, the start position (boundary) of the SS burst set may be determined based on the SFN and the cycle.

[0106] For the SS / PBCH block, an SSB index (also referred to as an SSB / PBCH block index) is allocated according to the temporal position in the SS burst set. The terminal device 1 calculates the SSB index based on the information of the PBCH and / or the reference signal included in the detected SS / PBCH block.

[0107] The same SSB index is assigned to the SS / PBCH blocks with the same relative time in each SS burst set in multiple SS burst sets. It can be assumed that the SS / PBCH blocks with the same relative time in each SS burst set in multiple SS burst sets are QCL (or the same downlink transmission beam is applied). In addition, it can also be assumed that the antenna ports of the SS / PBCH blocks with the same relative time in each SS burst set in multiple SS burst sets are QCL related to average delay, Doppler frequency shift, and spatial correlation.

[0108] It can also be assumed that within a period of a certain SS burst set, the SS / PBCH blocks assigned the same SSB index are QCLs related to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation. The setting corresponding to one or more SS / PBCH blocks (or reference signals) as QCL can be called QCL setting.

[0109] The number of SS / PBCH blocks (which may be referred to as the number of SS blocks or the number of SSBs) may be defined as, for example, the number of SS / PBCH blocks (number) in an SS burst or SS burst set or in a period of an SS / PBCH block. In addition, the number of SS / PBCH blocks may represent the number of beam groups used for cell selection in an SS burst or in an SS burst set or in the periodicity of an SS / PBCH block. Here, a beam group may be defined as: the number of different SS / PBCH blocks or the number of different beams included in an SS burst or in an SS burst set or in the periodicity of an SS / PBCH block.

[0110] In the following, the reference signals described 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.

[0111] In addition, the reference signal can be used for radio resource measurement (RRM: Radio Resource Measurement) and beam management.

[0112] Beam management can be a process for the base station device 3 and / or terminal device 1 to obtain beam gain by matching the directionality of the analog and / or digital beam in the transmitting device (the base station device 3 in the case of downlink and the terminal device 1 in the case of uplink) with the analog and / or digital beam in the receiving device (the terminal device 1 in the case of downlink and the base station device 3 in the case of uplink).

[0113] It should be noted that the process of constructing, setting or establishing beam pairing may include the following process.

[0114] Beam selection

[0115] Beam refinement

[0116] Beam recovery

[0117] For example, beam selection may be a process of selecting a beam in communication between the base station device 3 and the terminal device 1. In addition, beam refinement may be a process of further selecting a beam with a high gain or changing the optimal beam between the base station device 3 and the terminal device 1 by moving the terminal device 1. Beam recovery may be a process of reselecting a beam when the quality of the communication link is reduced due to obstruction caused by an obstruction, the passage of a person, etc. in communication between the base station device 3 and the terminal device 1.

[0118] Beam management may include beam selection and beam refinement. Beam recovery may include the following processes.

[0119] Detect beam failure

[0120] Discover new beams

[0121] Send beam recovery request

[0122] Monitor responses to beam restoration requests

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

[0124] In addition, the base station device 3 indicates the time index of CRI or SS / PBCH when indicating the beam to the terminal device 1, and the terminal device 1 receives based on the indicated time index of CRI or SS / PBCH. At this time, the terminal device 1 can set and receive spatial filtering based on the indicated time index of CRI or SS / PBCH. In addition, the terminal device 1 can use the assumed quasi co-location (QCL) for reception. A certain signal (antenna port, synchronization signal, reference signal, etc.) and other signals (antenna port, synchronization signal, reference signal, etc.) "are QCL", or "the assumption of using QCL" can be interpreted as a certain signal being associated with other signals.

[0125] If the long term property of the channel that transmits a symbol in a certain antenna port can be inferred from the channel that transmits a symbol in the other antenna port, then the two antenna ports are considered to be QCL. The long term property of the channel includes one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, when antenna port 1 and antenna port 2 are QCL related to the average delay, it means that the reception timing of antenna port 2 can be inferred from the reception timing of antenna port 1.

[0126] The QCL can also be extended to beam management. Therefore, the QCL extended to space can also be redefined. For example, the long term property of the channel in the assumption of QCL in the spatial domain can be the arrival angle (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and / or angle spread (Angle Spread, such as ASA (Angle Spread of Arrival), ZSA (Zenith angle Spread of Arrival)), transmission angle (AoD (deviation angle), ZoD, etc.) or its angle spread (Angle Spread, such as ASD (Angle Spread of Departure), ZSD (Zenith angle Spread of Departure)), spatial correlation (Spatial Correlation) and receiving space parameters in the wireless link or channel.

[0127] For example, when the reception spatial parameters between antenna port 1 and antenna port 2 are considered to be QCL, it means that the reception beam for receiving the signal from antenna port 2 can be inferred based on the reception beam for receiving the signal from antenna port 1 (reception spatial filtering).

[0128] As a QCL type, a combination of long-range characteristics that can be regarded as a QCL can be defined. For example, the following types can be defined.

[0129] Type A: Doppler shift, Doppler spread, average delay, delay spread

[0130] Type B: Doppler shift, Doppler spread

[0131] Type C: Average delay, Doppler shift

[0132] Type D: receiving space parameters

[0133] The above-mentioned QCL type can assume and / or indicate the QCL of one or two reference signals and PDCCH or PDSCH DMRS as a transmission configuration indication (TCI: Transmission Configuration Indication) through the RRC and / or MAC layer and / or DCI. For example, when the index #2 of the SS / PBCH block and the QCL type A+QCL type B are set and / or indicated as a state of TCI when the terminal device 1 receives the PDCCH, when the terminal device 1 receives the PDCCH DMRS, the DMRS of the PDCCH can be regarded as the Doppler frequency shift, Doppler spread, average delay, delay spread, receiving space parameters and long-interval characteristics of the channel in the reception of the SS / PBCH block index #2, and synchronization and transmission path estimation are performed. At this time, the reference signal indicated by the TCI (the SS / PBCH block in the above example) can be called the source reference signal, and the reference signal affected by the long-interval characteristics (the PDCCH DMRS in the above example) inferred from the long-interval characteristics of the channel when receiving the source reference signal can be called the target reference signal. In addition, TCI can set a combination of a source reference signal and a QCL type for one or more TCI states and each state through RRC, and indicate it to the terminal device 1 through the MAC layer or DCI.

[0134] According to this method, as beam management and beam indication / reporting, the actions of the base station device 3 and the terminal device 1 equivalent to beam management can be defined based on the assumption of QCL in the spatial domain and wireless resources (time and / or frequency).

[0135] The subframe is described below. In the present embodiment, it is called a subframe, but it may also be called a resource unit, a radio frame, a time interval, a time interval, etc.

[0136] Figure 3 This is a diagram showing an example of the schematic structure of the uplink and downlink time slots of the first embodiment of the present invention. The length of each wireless frame is 10 ms. In addition, each wireless frame is composed of 10 subframes and W time slots. In addition, one time slot is composed of X OFDM symbols. That is, the length of one subframe is 1 ms. The time length of each time slot is defined by the subcarrier spacing. For example, when the subcarrier spacing of the OFDM symbol is 15 kHz and is NCP (Normal Cyclic Prefix), X=7 or X=14, which are 0.5 ms and 1 ms, respectively. In addition, when the subcarrier spacing is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. In addition, for example, when X=14, when the subcarrier spacing is 15 kHz, W=10, and when the subcarrier spacing is 60 kHz, W=40. Figure 3 The case of X=7 is shown as an example. It should be noted that the extension can also be performed when X=14. In addition, the uplink time slot can be defined in the same way, or the downlink time slot and the uplink time slot can be defined separately. In addition, Figure 3 The bandwidth of a cell can be defined as a part of the frequency band (BWP: BandWidth Part). In addition, a time slot can be defined as a transmission time interval (TTI: Transmission Time Interval). A time slot may not be defined as a TTI. A TTI may be a transmission period of a transport block.

[0137] The signal or physical channel sent in each time slot can be represented by a resource grid. The resource grid defines each parameter set (subcarrier spacing and cyclic prefix length) and each carrier through multiple subcarriers and multiple OFDM symbols. The number of subcarriers that constitute a time slot depends on the bandwidth of the downlink and uplink of the cell respectively. Each element in the resource grid is called a resource element. Resource elements can be identified using the number of subcarriers and the number of OFDM symbols.

[0138] The resource grid is used to represent the mapping of resource elements of a physical downlink channel (PDSCH, etc.) or uplink channel (PUSCH, etc.). For example, when the subcarrier spacing is 15kHz, the number of OFDM symbols included in the subframe is X=14 and it is NCP, a physical resource block is defined by 14 consecutive OFDM symbols in the time domain and 12*Nmax consecutive subcarriers in the frequency domain. Nmax is the maximum number of resource blocks determined by the subcarrier spacing setting μ described later. That is, the resource grid is composed of (14*12*Nmax, μ) resource elements. In the case of ECP (Extended CP), only a subcarrier spacing of 60kHz is supported, so a physical resource block is defined by, for example, 12 (the number of OFDM symbols included in a time slot)*4 (the number of time slots included in a subframe)=48 consecutive OFDM symbols in the time domain and 12*Nmax, μ consecutive subcarriers in the frequency domain. That is, the resource grid is composed of (48*12*Nmax, μ) resource elements.

[0139] As resource blocks, reference resource blocks, shared resource blocks, physical resource blocks, and virtual resource blocks are defined. One resource block is defined as 12 subcarriers that are continuous in the frequency domain. The reference resource block is shared by all subcarriers. For example, a resource block can be formed with a subcarrier spacing of 15kHz, and the serial numbers are marked in ascending order. The subcarrier index 0 of the reference resource block index 0 can also be called reference point A (point A) (or just "reference point"). The shared resource block is a resource block that is numbered in ascending order starting from 0 in each subcarrier spacing setting μ starting from reference point A. The above-mentioned resource grid is defined by the shared resource block. The physical resource block is a resource block that is numbered in ascending order starting from 0 and included in the partial bandwidth (BWP) described later. The physical resource block is a resource block that is numbered in ascending order starting from 0 and included in the partial bandwidth (BWP). First, a physical uplink channel is mapped to a virtual resource block. Thereafter, the virtual resource block is mapped to the physical resource block. Hereinafter, a resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

[0140] Next, the subcarrier spacing setting μ is explained. As described above, one or more OFDM parameter sets are supported in NR. In a certain BWP, the subcarrier spacing setting μ (μ = 0, 1, ..., 5) and the cyclic prefix length are given by the upper layer for the BWP of the downlink and by the upper layer in the BWP of the uplink. Here, when μ is given, the subcarrier spacing Δf is given by Δf = 2^μ·15 (kHz).

[0141] In the 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 the cyclic prefix, N^{slot}_{symb} consecutive OFDM symbols are located in 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^{μ}_{s}N^{slot}_{symb}th OFDM symbol in the same subframe.

[0142] Next, subframes, slots, and mini-slots are described. Figure 4 It is a diagram showing the relationship between subframes, time slots, and mini-time slots in the time domain. Figure 4As shown, three time units are defined. Regardless of the subcarrier spacing, the subframe is 1ms, the number of OFDM symbols included in the time slot is 7 or 14, and the time slot length varies depending on the subcarrier spacing. Here, in the case of a subcarrier spacing of 15kHz, 14 OFDM symbols are included in one subframe. The downlink time slot may also be referred to as PDSCH mapping type A. The uplink time slot may also be referred to as PUSCH mapping type A.

[0143] A mini slot (may also be referred to as a sub slot) is a time unit composed of OFDM symbols which are smaller than the number of OFDM symbols included in a slot. Figure 4 The case where a mini-slot includes two OFDM symbols is shown as an example. The OFDM symbols in the mini-slot may also be timed to be consistent with the OFDM symbols that constitute the slot. It should be noted that the minimum unit of scheduling may be a slot or a mini-slot. In addition, the allocation of mini-slots may also be referred to as non-slot based scheduling. In addition, the scheduling of mini-slots may be represented as a resource in which the relative time position of the scheduling reference signal and the start position of the data is fixed. The downlink mini-slot may also be referred to as PDSCH mapping type B. The uplink mini-slot may also be referred to as PUSCH mapping type B.

[0144] Figure 5 1 is a diagram showing an example of a time slot format. Here, a case where the time slot length is 1 ms with a subcarrier spacing of 15 kHz is shown as an example. Figure 5 In the figure, D represents downlink and U represents uplink. Figure 5 As shown, a certain time interval (for example, a minimum time interval that must be allocated to a UE in the system) may include:

[0145] Downlink symbol

[0146] Variable symbols

[0147] Uplink symbols

[0148] One or more of. It should be noted that these proportions can be preset as a time slot format. In addition, it can also be defined by the number of OFDM symbols of the downlink included in the time slot or the starting position and the ending position in the time slot. In addition, it can also be defined by the number of OFDM symbols or DFT-S-OFDM symbols of the uplink included in the time slot or the starting position and the ending position in the time slot. It should be noted that the scheduling time slot can be expressed as a resource in which the relative time position of the scheduling reference signal and the time slot boundary is fixed.

[0149] The terminal device 1 may receive a downlink signal or a downlink channel through a downlink symbol or a variable symbol. The terminal device 1 may also transmit an uplink signal or a downlink channel through an uplink symbol or a variable symbol.

[0150] Figure 5 (a) is an example of using all downlink transmissions in a certain time interval (for example, it can be called the minimum unit of time resources that can be allocated to a UE or a time unit, etc. In addition, the minimum units of multiple time resources can also be collectively referred to as time units). Figure 5 In (b), the uplink is scheduled in the first time resource, for example, via the PDCCH, and the uplink signal is transmitted via a variable symbol including the processing delay of the PDCCH and the switching time from downlink to uplink, and the generation of the transmission signal. Figure 5 In (c), the first time resource is used to send PDCCH and / or PDSCH of the downlink, and is used to send PUSCH or PUCCH via an interval for processing delay and switching time from downlink to uplink, and generation of the transmission signal. Here, as an example, the uplink signal can be used to send HARQ-ACK and / or CSI, i.e., UCI. Figure 5 In (d), the first time resource is used to send PDCCH and / or PDSCH, and is used to send uplink PUSCH and / or PUCCH via an interval for processing delay and switching time from downlink to uplink, and generating a transmission signal. Here, as an example, the uplink signal can be used to send uplink data, i.e., UL-SCH. Figure 5 (e) is an example of all being used for uplink transmission (PUSCH or PUCCH).

[0151] The downlink part and uplink part mentioned above may include multiple OFDM symbols similar to LTE.

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

[0153] Hereinafter, the partial bandwidth (BWP, Bandwidth part) will be described. The BWP is also referred to as the carrier BWP. The BWP can also be set separately for the downlink and the uplink. The BWP is defined as a set of consecutive physical resources selected from a consecutive subset of shared resource blocks. The terminal device 1 can set up to four BWPs that activate one downlink carrier BWP (DL BWP) at a certain time. The terminal device 1 can set up to four BWPs that activate one uplink carrier BWP (UL BWP) at a certain time. In the case of carrier aggregation, the BWP can be set in each serving cell. At this time, setting one BWP in a certain serving cell can be expressed as not setting a BWP. In addition, setting two or more BWPs can also be expressed as setting a BWP.

[0154] <MAC entity actions>

[0155] In an activated serving cell, there is always an activated (already activated) BWP. BWP switching for a serving cell is used to activate a deactivated (disabled) BWP and deactivate an activated (already activated) BWP. BWP switching for a serving cell is controlled by a PDCCH indicating a downlink allocation or an uplink grant. BWP switching for a serving cell can 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, a BWP is activated first without receiving a PDCCH indicating a downlink allocation or an uplink grant. The first active DL BWP (first activation DL BWP) and UL BWP (first activation UL BWP) may be specified by an RRC message sent from the base station device 3 to the terminal device 1. The activated BWP for a serving cell is specified by an RRC or PDCCH sent from the base station device 3 to the terminal device 1. In addition, the first active DL BWP (first activation DL BWP) and UL BWP (first activation UL BWP) may be included in Message 4. In an unpaired spectrum (TDD band, etc.), the DL BWP and UL BWP are paired, and BWP switching is common for UL and DL. In the activated BWP of each activated serving cell with a BWP configured, the MAC entity of the terminal device 1 applies normal processing. Normal processing includes transmitting UL-SCH, transmitting RACH, monitoring PDCCH, transmitting PUCCH, transmitting SRS, and receiving DL-SCH. In the deactivated BWP of each activated serving cell with a BWP configured, the MAC entity of the terminal device 1 does not transmit UL-SCH, does not transmit RACH, does not monitor PDCCH, does not transmit PUCCH, does not transmit SRS, and does not receive DL-SCH. It is also possible that when a serving cell is disabled, there is no activated BWP (e.g., the activated BWP is deactivated).

[0156] <RRC action>

[0157] The BWP information element (IE) included in the RRC message (broadcast system information, information sent through a dedicated RRC message) is used to set the BWP. The RRC message sent from the base station device 3 is received by the terminal device 1. For each service cell, the network (base station device 3, etc.) sets at least an initial BWP (initial BWP) for the terminal device 1, including at least a downlink BWP and one (if an uplink is set in the service cell, etc.) or two (when a supplementary uplink is used, etc.) uplink BWP. In addition, the network may set an additional uplink BWP or downlink BWP for a certain service cell. The BWP setting is divided into uplink parameters and downlink parameters. In addition, the BWP setting is divided into common parameters and dedicated parameters. Common parameters (BWP uplink common IE or BWP downlink common IE, etc.) are cell-specific. The common parameters of the initial BWP of the main cell are also provided in the system information. For all other service cells, the network provides common parameters through dedicated signals. BWP is identified by BWPID. The BWP ID of the initial BWP is 0. The BWP IDs of other BWPs take values ​​from 1 to 4.

[0158] The initial DL BWP can be defined by the PRB location (location) of the control resource set (CORESET) for the type 0 PDCCH common search space, the number of consecutive PRBs, the subcarrier spacing, and the cyclic prefix. That is, the initial DL BWP can be set according to the PDCCH-ConfigCommon included in the pdcch-ConfigSIB1 or ServingCellCongfigCommon included in the MIB. The information element ServingCellCongfigCommon is used to set the cell-specific parameters of the serving cell for terminal device 1. In this case, the size of the initial DL BWP is N size BWP，0 . N size BWP，0 is the number of resource blocks representing the bandwidth of the initial DL BWP. Here, the initial DL BWP is of size N size BWP，0 Initial DL BWP.

[0159] Alternatively, the initial DL BWP may be provided to the terminal device 1 according to SIB1 (systemInformationBlockType1) or ServingCellCongfigCommon (e.g., ServingCellConfigCommonSIB). The information element ServingCellCongfigCommonSIB is used to set the cell-specific parameters of the serving cell for the terminal device 1 in SIB1. In this case, the size of the initial DL BWP is N size BWP，1 . N size BWP，1 Can be used with N size BWP，0 Equal. size BWP，1 Can also be used with N size BWP，0 Here, the initial DL BWP is of size N size BWP，1 Initial DL BWP.

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

[0161] In this embodiment, unless otherwise specified, the initial DL BWP may be N size BWP，0 The initial DL BWP can also be N size BWP，1 Initial DL BWP.

[0162] The terminal device 1 can set one primary cell and up to 15 secondary cells.

[0163] Fig.14 This is a flowchart showing an example of a random access procedure of a MAC entity according to the present embodiment.

[0164] <Start of Random Access Procedure (S1001)>

[0165] exist Fig.14In S1001, S1001 is a process related to the initiation of the random access procedure. In S1001, the random access procedure is initiated by the PDCCH order, the MAC entity itself, a notification of beam failure from the lower layer, or RRC. The random access procedure in the SCell is initiated only by the PDCCH order including the ra-PreambleIndex not set to 0b000000.

[0166] In S1001, the terminal device 1 receives random access setting information via an upper layer before initiating a random access procedure. The random access setting information may include the following information or one or more elements of information used to determine / set the following information.

[0167] prach-ConfigIndex: A set of one or more time / frequency resources (also called random access channel occasions, PRACH occasions, RACH opportunities) that can be used for the transmission of random access preambles

[0168] preambleReceivedTargetPower: initial power of the preamble (can also be the target received power)

[0169] rsrp-ThresholdSSB: The reference signal received power (RSRP) threshold used to select the SS / PBCH block (and possibly the associated random access preamble and / or PRACH opportunity)

[0170] rsrp-ThresholdCSI-RS: The threshold of the reference signal received power (RSRP) used to select the CSI-RS (and also the associated random access preamble and / or PRACH opportunity)

[0171] rsrp-ThresholdSSB-SUL: The reference signal received power (RSRP) threshold used to select between the NUL (Normal Uplink) carrier and the SUL (Supplementary Uplink) carrier

[0172] powerControlOffset: The power offset between rsrp-ThresholdSSB and rsrp-ThresholdCSI-RS when starting a random access procedure for beam failure recovery

[0173] powerRampingStep: power ramping step size (power ramping factor). Indicates the step size of the transmission power that is increased based on the preamble transmission counter PREAMBLE_TRANSMISSION_COUNTER.

[0174] ra-PreambleIndex: one or more available random access preambles or one or more random access preambles that can be used in the plurality of random access preamble groups

[0175] ra-ssb-OccasionMaskIndex: Information used to determine the PRACH opportunity allocated to the SS / PBCH block for the MAC entity to send the random access preamble

[0176] ra-OccasionList: Information used to determine the PRACH opportunities allocated to the CSI-RS for the MAC entity to send the random access preamble

[0177] preamTransMax: Maximum number of preamble transmissions

[0178] ssb-perRACH-OccasionAndCB-PreamblesPerSSB (SpCell only): A parameter indicating the number of SS / PBCH blocks mapped to each PRACH opportunity and the number of random access preambles mapped to each SS / PBCH block

[0179] ra-ResponseWindow: The time window for monitoring random access responses (SpCell only)

[0180] ra-ContentionResolutionTimer: Conflict resolution (contention resolution: ContentionResolution) timer

[0181] numberOfRA-PreamblesGroupA: The number of random access preambles in random access preamble group A used for each SS / PBCH block

[0182] PREAMBLE_TRANSMISSION_COUNTER: Preamble transmission counter

[0183] DELTA_PREAMBLE: Power offset value based on random access preamble format

[0184] PREAMBLE_POWER_RAMPING_COUNTER: Preamble power ramping counter

[0185] PREAMBLE_RECEIVED_TARGET_POWER: Initial random access preamble power. Indicates the initial transmit power for random access preamble transmission.

[0186] PREAMBLE_BACKOFF: used to adjust the timing of sending the random access preamble.

[0187] When a random access procedure starts in a certain service 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 used in the random access procedure is explicitly notified, the MAC entity selects the carrier notified for the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the notified carrier. In the case where the carrier used in the random access procedure is not explicitly notified and a SUL carrier is set for the service cell, and the RSRP referenced by the downlink path loss is less than rsrp-ThresholdSSB-SUL, the MAC entity selects the SUL carrier for the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the SUL carrier. In other cases, the MAC entity selects the NUL carrier for the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the NUL carrier. <Start of random access procedure (S1002)>

[0188] S1002 is a random access resource selection process. The following describes a random access resource selection process (including time / frequency resources and / or preamble index) in the MAC layer of the terminal device 1.

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

[0190] Terminal device 1 (MAC entity) selects an SS / PBCH block or CSI-RS whose RSRP exceeds a specified threshold when (1) a random access procedure is started by notification of beam failure from a lower layer, (2) a random access resource (which may also be a PRACH opportunity) for non-contention-based random access for beam failure recovery request associated with an SS / PBCH block (also called an SSB) or a CSI-RS is provided through RRC parameters, and (3) the RSRP of one or more SS / PBCH blocks or CSI-RS exceeds the specified threshold. If there is no ra-PreambleIndex that has selected a CSI-RS and is 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). In other cases, the MAC entity sets the ra-PreambleIndex associated with the selected SS / PBCH block or CSI-RS as the preamble index.

[0191] When (1) ra-PreambleIndex is provided through PDCCH or RRC, (2) the value of ra-PreambleIndex is not a value indicating a contention-based random access process (e.g., 0b000000), and (3) the SS / PBCH block or CSI-RS is not associated with a random access resource for non-contention-based random access through RRC, the terminal device 1 sets the ra-PreambleIndex notified through signaling as the preamble index. 0bxxxxxx means a bit string configured as a 6-bit information field.

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

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

[0194] When any of the above conditions are not met, the terminal device 1 performs a contention-based random access process. In the contention-based random access process, the terminal device 1 selects an SS / PBCH block with RSRP of an SS / PBCH block that exceeds a set threshold, and selects a preamble group. When the relationship between the SS / PBCH block and the 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.

[0195] When the MAC entity selects an SS / PBCH block and sets the association between the PRACH opportunity and the SS / PBCH block, it can determine the next available PRACH opportunity among the PRACH opportunities associated with the selected SS / PBCH block. Among them, when the terminal device 1 selects a CSI-RS and sets the association between the PRACH opportunity and the CSI-RS, it can determine the next available PRACH opportunity among the PRACH opportunities associated with the selected CSI-RS.

[0196] The available PRACH opportunities may be determined based on the mask index information, the SSB index information, the resource settings set by the RRC parameters, and / or the selected reference signal (SS / PBCH block or CSI-RS). The resource settings set by the RRC parameters include resource settings for each SS / PBCH block and / or resource settings for each CSI-RS.

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

[0198] The mask index information is information indicating the index of a PRACH opportunity that can be used for sending a random access preamble. The mask index information may be information indicating a portion of PRACH opportunities in one or more PRACH opportunity groups determined by prach-ConfigurationIndex. In addition, the mask index information may be information indicating a portion of PRACH opportunities in a group of PRACH opportunities mapped with a specific SSB index determined by SSB index information.

[0199] The SSB index information is information indicating an SSB index corresponding to any one of one or more SS / PBCH blocks transmitted by the base station device 3. The terminal device 1 receiving the message 0 determines a group of PRACH opportunities mapped with an SSB index indicated by the SSB index information. 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.

[0200] <Transmission of Random Access Preamble (S1003)>

[0201] S1003 is a process related to the transmission of a random access preamble. For each random access preamble, the MAC entity increments a state variable PREAMBLE_POWER_RAMPING_COUNTER when (1) the state variable PREAMBLE_TRANSMISSION_COUNTER is greater than 1, (2) no notification of a stopped power lamp counter is received from the upper layer, and (3) the selected SS / PBCH block is not changed.

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

[0203] Next, the MAC entity calculates the RA-RNTI associated with the PRACH opportunity that sent the random access preamble, other than based on the non-contention random access preamble for beam failure recovery request. The RA-RNTI is calculated by RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id. Here, s_id is the index of the first OFDM symbol of the PRACH sent, and takes a value from 0 to 13. t_id is the index of the first time 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 in Msg1 transmission. The ul_carrier_id for the NUL carrier is 0, and the ul_carrier_id for the SUL carrier is 1.

[0204] The MAC entity instructs the physical layer to use the selected PRACH to send a random access preamble. <Reception of random access response (S1004)>

[0205] S1004 is a process related to random access response reception. Once the random access preamble is sent, the MAC entity performs the following actions regardless of whether a measurement interval may occur. Here, the random access response may be a MAC PDU for random access response.

[0206] A MAC PDU (MAC PDU of random access response) consists of one or more MAC subPDUs and possible padding. Each MAC subPDU consists of any of the following.

[0207] A MAC subheader that includes only the Backoff Indicator

[0208] ·Only the RAPID MAC subheader

[0209] MAC subheader and MAC RAR (MAC payload for Random Access Response) indicating RAPID

[0210] The MAC subPDU including only the Backoff Indicator is allocated to the start of the MAC PDU. The padding is allocated to the end of the MAC PDU. The MAC subPDU including only the RAPID and the MAC subPDU including the RAPID and the MAC RAR can be allocated to any one between the MAC subPDU including only the Backoff Indicator and the padding.

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

[0212] In S1004, if the MAC entity sends a non-contention-based random access preamble for a beam failure recovery request, the MAC entity starts a random access response window (ra-ResponseWindow) through the first PDCCH opportunity from the end of the random access preamble transmission. Moreover, during the operation of the random access response window, the MAC entity monitors the PDCCH of the SpCell identified by the C-RNT in order to respond to the beam failure recovery request. Here, the time period (window size) of the random access response window is given by the ra-ResponseWindow included in the upper-layer parameter BeamFailureRecoveryConfig. In other cases, the MAC entity starts a random access response window (ra-ResponseWindow) through the first PDCCH opportunity from the end of the random access preamble transmission. Here, the time period (window size) of the random access response window is given by the ra-ResponseWindow included in the upper-layer parameter RACH-ConfigCommon. Moreover, during the operation of the random access response window, the MAC entity monitors the PDCCH of the SpCell identified by the RA-RNTI for random access response. Here, in the case of beam failure detection, the information element BeamFailureRecoveryConfig is used in the configuration of RACH resources and candidate beams in order to perform beam failure recovery for the terminal device 1. The information element RACH-ConfigCommon is used to specify cell-specific random access parameters.

[0213] The random access procedure may be considered to have been successfully completed when (1) the MAC entity receives a reception notification sent by the PDCCH from the lower layer, (2) the PDCCH is sent encrypted by the C-RNTI, and (3) the MAC entity sends a non-contention-based random access preamble for a beam failure recovery request.

[0214] Next, the MAC entity performs the following actions when (1) a downlink assignment is received in the PDCCH of the RA-RNTI and (2) the received transport block has been successfully decoded.

[0215] When the random access response includes a MAC subPDU including a BackoffIndicator, the MAC entity sets PREAMBLE_BACKOFF to the value of the BI field included in the MAC subPDU. In other cases, the MAC entity sets PREAMBLE_BACKOFF to 0 ms.

[0216] The MAC entity may regard that reception of the random access response is successful when the random access response includes a MAC subPDU including a random access preamble identifier corresponding to the sent PREAMBLE_INDEX.

[0217] In the case where (1) the reception of the random access response is deemed to be successful, and (2) the random access response includes a MAC subPDU including only RAPID, the MAC entity deems that the random access procedure has been successfully completed, and then indicates the reception of the positive response (acknowledgement) to the SI request (system information request) to the upper layer. Here, in the case where condition (2) is not met, the MAC entity applies the following action A in the serving cell that sends the random access preamble.

[0218] <Beginning of Action A>

[0219] The MAC entity processes the received transmission timing adjustment information (Timing Advance Command) and indicates the preambleReceivedTargetPower and the amount of power increase applied to the latest random access preamble transmission to the lower layer. Here, the transmission timing adjustment information is used to adjust the transmission timing offset between the terminal device 1 and the base station device 3 according to the received random access preamble.

[0220] In the case where the serving cell for the random access procedure is an SCell used only for SRS, the MAC entity may ignore the received UL grant. In other cases, the MAC entity processes the value of the received UL grant and indicates it to the lower layer.

[0221] In the event that a random access preamble is not selected by the MAC entity from the range of contention-based random access preambles, the MAC entity may deem the random access procedure to have been successfully completed.

[0222] <End of Action A>

[0223] In the case where a random access preamble is selected by the MAC entity from within the range of contention-based random access preambles, the MAC entity sets the TEMPORARY_C-RNTI to the value of the temporary C-RNTI field included in the received random access response. Then, in the case where the random access response is successfully received for the first time during the random access process, if the MAC entity does not send a CCCH logical channel (common control channel logical channel), it notifies the specified entity (Multiplexing and assembly entity) of the C-RNTI MAC CE included in the next uplink transmission, and then obtains the MAC PDU for transmission from the specified entity (Multiplexing and assembly entity), and stores the obtained MAC PDU in the Msg3 buffer. In the case where the MAC entity sends a CCCH logical channel, it obtains the MAC PDU for transmission from the specified entity (Multiplexing and assembly entity), and stores the obtained MAC PDU in the Msg3 buffer.

[0224] If at least one of the following conditions (3) to (4) is met, the MAC entity considers that the random access response is successfully received and increments a preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER). When the value of the preamble transmission counter reaches the specified value (maximum number of preamble transmissions + 1) and the random access preamble is sent through the SpCell, the MAC entity indicates the random access problem to the upper layer. In addition, when the random access procedure is started for an SI request, the MAC entity considers that the random access procedure is not successfully completed.

[0225] When the value of the preamble sending counter reaches the specified value (the maximum number of preamble sending + 1) and the random access preamble is sent through the SCell, the MAC entity considers that the random access process has not been successfully completed.

[0226] Condition (3) is that the period of the random access response window set by RACH-ConfigCommon expires, and no random access response including a random access preamble identifier consistent with the transmitted preamble index is received. Condition (4) is that the period of the random access response window set by BeamFailureRecoveryConfig expires, and no PDCCH scrambled by C-RNTI is received.

[0227] In the case where the random access process is not completed, if the random access preamble is selected from the range of contention-based random access preambles by MAC itself during the random access process, the MAC entity selects a random backoff time between 0 and PREAMBLE_BACKOFF, delays the transmission of the next random access preamble according to the selected backoff time, and then executes S1002. In the case where the random access process is not completed, if the random access preamble is selected from the range of contention-based random access preambles by MAC itself during the random access process, the MAC entity executes S1002.

[0228] If a random access response including a random access preamble identifier consistent with the sent preamble index is successfully received, the MAC entity may stop the random access response window.

[0229] The terminal device 1 sends a message 3 via the PUSCH based on the UL grant.

[0230] <Conflict Resolution (S1005)>

[0231] S1005 is a process related to contention resolution.

[0232] Once Msg3 is sent, the MAC entity starts the conflict resolution timer and restarts the conflict resolution timer at each HARQ retransmission. The MAC entity monitors the PDCCH during the conflict resolution timer regardless of whether a measurement gap may occur.

[0233] When receiving a reception notification sent by PDCCH from the lower layer and the C-RNTI MAC CE is included in Msg3, if at least one of the following conditions (5) to (7) is met, the MAC entity regards the contention elimination as successful, stops the conflict elimination timer, discards the TEMPORARY_C-RNTI, and regards the random access process as having been successfully completed.

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

[0235] In the case where the CCCH SDU (UE contention resolution Identity) is included in Msg3 and the PDCCH transmission is encrypted via TEMPORARY_C-RNTI, if the MAC PDU has been successfully decoded, the MAC entity stops the conflict resolution timer. Next, if the successfully decoded MAC PDU includes a UE conflict resolution identity (UE contentionresolution identity) MAC CE, and the UE conflict resolution identity in the MAC CE matches the CCCH SDU sent via Msg3, the MAC entity deems the conflict resolution successful and ends the disassembly and demultiplexing of the MAC PDU. Moreover, in the case where the random access procedure is started for an SI request, the MAC entity indicates the receipt of a positive response to the SI request to the upper layer. In the case where the random access procedure is not started for an SI request, the MAC entity sets the C-RNTI to the value of the TEMPORARY_C-RNTI. Next, the MAC entity discards the TEMPORARY_C-RNTI and deems that the random access procedure has been successfully completed.

[0236] When the UE conflict resolution identifier in the MAC CE does not match the CCCH SDU sent through Msg3, the MAC entity discards the TEMPORARY_C-RNTI, regards the conflict resolution as unsuccessful, and discards the successfully decoded MAC PDU.

[0237] When the conflict elimination timer expires, the MAC entity discards the TEMPORARY_C-RNTI and deems the contention elimination unsuccessful. When the contention elimination is deemed unsuccessful, the MAC entity refreshes the HARQ buffer used for sending the MAC PDU in the Msg3 buffer and increments a preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER). If the value of the preamble transmission counter reaches the specified value (the maximum number of preamble transmissions + 1), the MAC entity indicates the random access problem to the upper layer. Moreover, when the random access process is started for an SI request, the MAC entity deems that the random access process has not been successfully completed.

[0238] When the random access process is not completed, the MAC entity selects a random backoff time between 0 and PREAMBLE_BACKOFF, delays the transmission of the next random access preamble according to the selected backoff time, and executes S1002.

[0239] When the random access process is completed, for the non-contention based random access process other than the non-contention based random access process for beam failure recovery request, the MAC entity discards the non-contention based random access resources explicitly notified by signaling, and refreshes the HARQ buffer used for sending the MAC PDU in the Msg3 buffer.

[0240] The control resource set (CORESET) according to this embodiment is described below.

[0241] The control resource set (CORESET, Control resource set) is a time and frequency resource used to search for downlink control information. The setting information of CORESET includes information that determines the identifier of CORESET (ControlResourceSetId, CORESET-ID) and the frequency resources of CORESET. The information element ControlResourceSetId (identifier of CORESET) is used to determine the control resource set in a certain service cell. The identifier of CORESET is used between BWPs in a certain service cell. The identifier of CORESET is unique between BWPs in a service cell. The number of CORESETs for each BWP is limited to 3, including the initial CORESET. The value of the identifier of CORESET in a certain service cell takes a value from 0 to 11.

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

[0243] The setting information of the additional common CORESET (additional common control resource set) can be set according to the commonControlResourceSet included in PDCCH-ConfigCommon. The setting information of the additional common CORESET can be used to specify the additional common CORESET used in the random access process. The setting information of the additional common CORESET can be included in the setting of each BWP. The identifier of the CORESET indicated by commonControlResourceSet takes a value other than 0.

[0244] The public CORESET may be a CORESET used in the random access process (e.g., an additional public CORESET). In addition, in the present embodiment, the public CORESET may include a CORESET set in the setting information of CORESET#0 and / or an additional public CORESET. That is, the public CORESET may include CORESET#0 and / or an additional public CORESET. CORESET#0 may also be referred to as public CORESET#0. Even in a BWP other than a BWP in which a public CORESET is set, the terminal device 1 may refer to (acquire) the setting information of the public CORESET.

[0245] The configuration information of one or more CORESETs may be configured according to PDCCH-Config. The information element PDCCH-Config is used to configure UE-specific PDCCH parameters (eg CORESET, search space, etc.) for a BWP. PDCCH-Config may be included in the configuration of each BWP.

[0246] That is, in this embodiment, the setting information of the common CORESET indicated by MIB is pdcch-ConfigSIB1, the setting information of the common CORESET indicated by PDCCH-ConfigCommon is controlResourceSetZero, and the setting information of the common CORESET (supplemented common CORESET) indicated by PDCCH-ConfigCommon is commonControlResourceSet. In addition, the setting information of one or more CORESETs (UEspecifically configured Control Resource Sets: UE specifically configured control resource set, UE-specific CORESET) indicated by PDCCH-Config is controlResourceSetToAddModList.

[0247] The search space is defined as a search space for searching for PDCCH candidates. The searchSpaceType included in the search space setting information indicates that the search space is a common search space (CSS) or a UE-specific search space (USS). The UE-specific search space is derived from at least the value of the C-RNTI set by the terminal device 1. That is, the UE-specific search space is derived separately for each terminal device 1. The common search space is a search space common to multiple terminal devices 1 and is composed of a pre-set index CCE (Control Channel Element). CCE is composed of multiple resource elements. The search space setting information includes information on the DCI format monitored in the search space.

[0248] The setting information of the search space includes an identifier of the CORESET determined by the setting information of the CORESET. The CORESET determined by the identifier of the CORESET included in the setting information of the search space is associated with the search space. In other words, the CORESET associated with the search space is a CORESET determined by the identifier of the CORESET included in the search space. The DCI format indicated by the setting information of the search space is monitored in the associated CORESET. Each search space is associated with a CORESET. For example, the setting information of the search space used for the random access process can be set according to the ra-SearchSpace. That is, the DCI format with a CRC scrambled by the RA-RNTI or TC-RNTI is monitored in the CORESET associated with the ra-SearchSpace.

[0249] As described above, the setting information of CORESET#0 is included in the setting of the initial DL BWP. The setting information of CORESET#0 may not be included in the setting of a BWP (an additional BWP) other than the initial DL BWP. In the case where a BWP (an additional BWP) other than the initial DL BWP refers to (refer, acquire, etc.) the setting information of CORESET#0, it may be necessary to at least satisfy that CORESET#0 and the SS block are included in the additional BWP in the frequency domain and use the same subcarrier spacing. In other words, in the case where a BWP (an additional BWP) other than the initial DL BWP refers to (refer, acquire, etc.) the setting information of CORESET#0, it may be necessary to at least satisfy that the bandwidth of the initial DL BWP and the SS block are included in the additional BWP in the frequency domain and use the same subcarrier spacing. At this time, the search space (e.g., ra-SearchSpace) set for the additional BWP can refer to (refer, acquire, etc.) the setting information of CORESET#0 by indicating the identifier 0 of CORESET#0. In addition, if any of the conditions that the bandwidth of the initial DL BWP in the frequency domain is included in the additional DL BWP, the SS block is included in the additional DL BWP, and the same subcarrier spacing is used is not satisfied, the terminal device 1 may not expect the additional DL BWP to refer to the setting information of CORESET#0. That is, in this case, the base station device 3 may not set the additional DLBWP to refer to the setting information of CORESET#0 for the terminal device 1. Here, the initial DL BWP may be N in size. size BWP，0 Initial DL BWP.

[0250] In the case where a certain (additional) DL BWP refers to (refer, acquire, etc.) the setting information of the CORESET of another BWP, it may be necessary to at least satisfy the conditions that the CORESET (or the bandwidth of the BWP) and / or the (associated) SS blocks included in the additional BWP in the frequency domain are included in the additional BWP and use the same subcarrier spacing. That is, if any of the conditions that the CORESET (or the bandwidth of the BWP) is included in the additional DL BWP in the frequency domain, and the (associated) SS blocks included in the BWP are included in the additional DL BWP and use the same subcarrier spacing is not satisfied, the terminal device 1 may not expect the additional DL BWP to refer to the setting information of the CORESET set for the BWP.

[0251] The terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs configured in each activated service cell set to monitor the PDCCH. The set of PDCCH candidates corresponds to one or more search space sets. Monitoring means decoding each PDCCH candidate according to one or more monitored DCI formats. The set of PDCCH candidates monitored by the terminal device 1 is defined as a PDCCH search space set (PDCCH search space sets). A search space set is a common search space set or a UE-specific search space set. In the above description, the search space set is referred to as a search space, the common search space set is referred to as a common search space, and the UE-specific search space set is referred to as a UE-specific search space. The terminal device 1 monitors PDCCH candidates in one or more of the following search space sets.

[0252] - Type 0 PDCCH common search space set: This search space set is set according to the search space zero (searchSpaceZero) indicated by the MIB as a parameter of the upper layer or the search space SIB1 (searchSpaceSIB1) indicated by the PDCCH-ConfigCommon. This search space is used to monitor the DCI format of the CRC scrambled by the SI-RNRI in the primary cell.

[0253] - Type 0 A PDCCH common search space set (a Type 0 A-PDCCH common search space set): This search space set is set according to the search space OSI (searchSpace-OSI) indicated by PDCCH-ConfigCommon as a parameter of the upper layer. This search space is used to monitor the DCI format of the CRC scrambled by the SI-RNRI in the primary cell.

[0254] - Type 1 PDCCH common search space set: This search space set is set according to the search space (ra-SearchSpace) for the random access procedure indicated by PDCCH-ConfigCommon as a parameter of the upper layer. This search space is used to monitor the DCI format of the CRC scrambled by the RA-RNRI or TC-RNTI in the primary cell. The Type 1 PDCCH common search space set is the search space set for the random access procedure.

[0255] - Type 2-PDCCH common search space set: This search space set is set according to the search space for the paging process (pagingSearchSpace) indicated by PDCCH-ConfigCommon as a parameter of the upper layer. This search space is used to monitor the DCI format of the CRC scrambled by the P-RNTI in the primary cell.

[0256] - Type 3 DCCH common search space set (a Type3-PDCCH common search space set): This search space set is set according to the search space type indicated by PDCCH-Config as a parameter of the upper layer as a common search space (SearchSpace). This search space is used to monitor the DCI format of the CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI or TPC-SRS-RNTI. It is used to monitor the DCI format of the CRC scrambled by C-RNTI or CS-RNTI(s) for the primary cell.

[0257] -UE-specific search space set: This search space set is set according to the search space type indicated by PDCCH-Config as a parameter of the upper layer as a UE-specific search space (SearchSpace). This search space is used to monitor the DCI format of the CRC scrambled by C-RNTI or CS-RNTI(s).

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

[0259] The setting information of BWP is divided into the setting information of DL BWP and the setting information of UL BWP. The setting information of BWP includes the information element bwp-Id (identifier of BWP). The identifier of BWP included in the setting information of DL BWP is used to determine (reference) the DL BWP in a certain serving cell. The identifier of BWP included in the setting information of UL BWP is used to determine (reference) the UL BWP in a certain serving cell. The identifier of BWP is assigned to DL BWP and UL BWP respectively. For example, the identifier of BWP corresponding to DL BWP can also be called DL BWP index (DL BWP index). The identifier of BWP corresponding to UL BWP can also be called UL BWP index (UL BWP index). The initial DL BWP is referenced by the identifier 0 of DL BWP. The initial UL BWP is referenced by the identifier 0 of UL BWP. Other DL BWPs or other UL BWPs can be referenced by the identifiers 1 to maxNrofBWPs of BWP respectively. That is, the identifier of the BWP 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 for each serving cell, which is 4. That is, the value of the identifier of other BWPs takes a value from 1 to 4. Other upper layer setting information uses the BWP identifier to establish an association with the determined BWP. The fact that the DL BWP and the UL BWP have the same BWP identifier may mean that the DL BWP and the UL BWP are paired.

[0260] Figure 7 This is a diagram showing an example of BWP setting according to the embodiment of the present invention.

[0261] An initial BWP including at least one DL BWP and one UL BWP is set for each serving cell. In addition, an additional BWP (an additional UL BWP and / or an additional DL BWP) can be set for a certain serving cell. The additional BWP can be set to a maximum of four. However, in a serving cell, there is one activated DL BWP and one activated UL BWP.

[0262] exist Figure 7In a certain service cell, an initial BWP (BWP#0) and two additional BWPs (BWP#1 and BWP#2) are set for the 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 (DLBWP#2). 809 is the additional UL BWP (UL BWP#2). In the following, it is assumed that DL BWP#1 is activated and UL BWP#0 is activated. That is, DL BWP#0 and UL BWP#1 are inactivated BWPs. DL BWP#2 and UL BWP#2 are inactivated BWPs. In this case, the activated DL BWP#1 can also be referred to as an activated DL BWP (activated DL BWP, currently active DLBWP). The activated initial UL BWP#0 may also be referred to as an initial active UL BWP. The terminal device 1 performs downlink reception in the activated DL BWP#1 and activates uplink transmission in the initial active UL BWP.

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

[0264] exist Figure 7, ra-searchspace is set for DL ​​BWP#0, DL BWP#1, and DL BWP#2, respectively. As described above, the setting information of the search space used for the random access process can be set according to the ra-SearchSpace. As a first example, the identifier of the CORESET included in the ra-searchspace set for a certain DL BWP can be set to the value of the identifier of the CORESET that determines the setting information of the CORESET set for the DL BWP, or can be set to the value of the identifier of the CORESET included in the ra-SearchSpace set for the initial BWP. That is, the ra-searchspace set for a certain DL BWP can represent the identifier of the CORESET that determines the setting information of the CORESET set for the DL BWP, or can represent the identifier of the CORESET included in the ra-SearchSpace set for the initial BWP. That is, the ra-searchspace set for a certain DL BWP may not represent the identifiers of the common and UE-specific CORESETs set for other DL BWPs other than the DL BWP and the initial DL BWP. In other words, the base station device 3 may also send an RRC message in such a manner that the ra-searchspace set for a certain DL BWP does not indicate the identifiers of the common and UE-specific CORESETs set for the DL BWP and other DL BWPs other than the initial DL BWP. For example, for DL ​​BWP#1, the value of the identifier of the CORESET included in the ra-searchspace may be set to 1 or 3. For DL ​​BWP#1, the value of the identifier of the CORESET included in the ra-searchspace is not set to 6. In the case where the value of the identifier of the CORESET included in the ra-searchspace is set to 1 for DL ​​BWP#1, the terminal device 1 monitors the DCI format included in the ra-searchspace through the activated DL BWP#1 based on the setting information of CORESET#1 (804) determined by the identifier 1 of the CORESET. When the value of the identifier of the CORESET included in the ra-searchspace is set to 3 for DL ​​BWP#1, the terminal device 1 monitors the DCI format included in the ra-searchspace through the activated DL BWP#1 based on the setting information of CORESET#3 (807) determined by the identifier of the CORESET 3. That is, the ra-searchspace set for a certain DL BWP can indicate the identifier of the CORESET that determines the setting information of the common CORESET.For example, for DL ​​BWP#1, the value of the identifier of the CORESET included in the ra-searchspace may be set to 1. That is, when CORESET#1 is set for the initial DL BWP, CORESET#0 cannot be paged as the ra-searchspace. When CORESET#1 is not set for the initial DL BWP, CORESET#0 can be paged as the ra-searchspace. However, as an extension of the first example, when CORESET#1 is set for the initial DL BWP, the DL BWP may also page CORESET#0 as the ra-searchspace.

[0265] In addition, as a second example, the identifier of the CORESET included in the ra-searchspace set for a certain DL BWP may be set to the value of the identifier of the CORESET that determines the setting information of the common CORESET set for the DL BWP, or may be set to the value of the identifier of the common CORESET used for the random access procedure set for other BWPs. That is, the ra-searchspace set for a certain DL BWP may indicate the identifier of the CORESET that determines the setting information of the common CORESET set for the DL BWP, or may indicate the identifier of the common CORESET used for the random access procedure set for other BWPs. For example, for DL ​​BWP#1, the value of the identifier of the CORESET included in the ra-searchspace may be set to 1, 3, or 6. That is, when CORESET#1 is set for the initial DL BWP, CORESET#0 cannot be paged as the ra-searchspace of the DL BWP. When CORESET#1 is not set for the initial DL BWP, CORESET#0 can be paged as the ra-searchspace of the DL BWP.

[0266] In addition, as a third example, the identifier of the CORESET included in the ra-searchspace set for a certain DL BWP can be set to the value of the identifier of all common CORESETs set for the terminal device 1. That is, the ra-searchspace set for a certain DL BWP can represent the identifier of the CORESET that determines the setting information of all common CORESETs set for the serving cell. For example, for DL ​​BWP#1, the value of the identifier of the CORESET included in the ra-searchspace can be set to 0, 1, 3, 6.

[0267] It can be set to the value of the identifier of the CORESET that determines the setting information of the CORESET set for the DL BWP, or it can be set to the value of the identifier of the CORESET set for other BWPs. That is, the ra-searchspace set for a certain DL BWP can represent the identifier of the CORESET that determines the setting information of the CORESET set for the DL BWP, or it can represent the identifier of the common CORESET set for other BWPs. For example, for DL ​​BWP#1, the value of the identifier of the CORESET included in the ra-searchspace can be set to 0, 1, 3, or 6.

[0268] The random access procedure of this embodiment is described. The random access procedure is divided into two types: contention-based (CB) and non-contention-based (non-CB) (also called CF: Contention Free). Contention-based random access is also called CBRA, and non-contention-based random access is also called CFRA.

[0269] The random access procedure may include: (i) transmission of a random access preamble (message 1, Msg1) in PRACH; (ii) reception of a random access response (RAR) message (message 2, Msg2) accompanying PDCCH / PDSCH; where applicable, (iii) transmission of message 3PUSCH (Msg3PUSCH); and (iv) reception of PDSCH for conflict elimination.

[0270] The contention-based random access procedure is initiated by the PDCCH order, the MAC entity, a notification of beam failure from the lower layer, or the RRC, etc. In the case where the beam failure notification is provided from the physical layer of the terminal device 1 to the MAC entity of the terminal device 1, when a certain condition is met, the MAC entity of the terminal device 1 starts the random access procedure. The process of starting the random access procedure by judging whether a certain condition is met when the beam failure notification is provided from the physical layer of the terminal device 1 to the MAC entity of the terminal device 1 may also be referred to as a beam failure recovery procedure. This random access procedure is a random access procedure for a beam failure recovery request. The random access procedure initiated by the MAC entity includes a random access procedure initiated by a scheduling request procedure. The random access procedure for a beam failure recovery request may or may not be considered to be a random access procedure initiated by a MAC entity. In the random access procedure for a beam failure recovery request and the random access procedure initiated by the scheduling request procedure, different procedures are sometimes performed, so the random access procedure for a beam failure recovery request and the scheduling request procedure can be distinguished. The random access procedure for beam failure recovery request and the scheduling request procedure may be referred to as a random access procedure initiated by a MAC entity. In a certain embodiment, the random access procedure initiated by the scheduling request procedure may be referred to as a random access procedure initiated by a MAC entity, and the random access procedure for beam failure recovery request may be referred to as a random access procedure based on a notification of beam failure from a lower layer. Hereinafter, the start of a random access procedure in the case of receiving a notification of beam failure from a lower layer may mean the start of a random access procedure for beam failure recovery request.

[0271] The terminal device 1 performs a contention-based random access process during initial access from a state where the terminal device 1 is not connected (communicating) with the base station device 3 and / or when a scheduling request is made when the terminal device 1 is connected to the base station device 3 but uplink data that can be sent to the terminal device 1 or sidelink data that can be sent to the terminal device 1 is generated. However, the use of contention-based random access is not limited to this.

[0272] Generating uplink data transmittable to the terminal device 1 may include triggering a buffer status report corresponding to the transmittable uplink data. Generating uplink data transmittable to the terminal device 1 may also include waiting for a scheduling request triggered by the generation of the transmittable uplink data.

[0273] Generating sidelink data transmittable to terminal device 1 may include triggering a buffer status report corresponding to the transmittable sidelink data. Generating sidelink data transmittable to terminal device 1 may also include waiting for a scheduling request triggered by the generation of the transmittable sidelink data.

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

[0275] Non-contention-based random access can be used to quickly acquire uplink synchronization between the terminal device 1 and the base station device 3 when handover is invalid and the transmission timing of the mobile station device is invalid while the base station device 3 is connected to the terminal device 1. Non-contention-based random access can be used to transmit a beam failure recovery request when a beam failure occurs in the terminal device 1. However, the use of non-contention-based random access is not limited to this.

[0276] Among them, the information indicating the start of the random access process can be called message 0, Msg.0, NR-PDCCH command, PDCCH command, etc.

[0277] In which, when the random access preamble index indicated by message 0 is a specified value (for example, all bits representing the index are 0), terminal device 1 can perform a contention-based random access process by randomly selecting one from a set of available preambles to send.

[0278] However, the random access setting information may include information that is common in a cell, or may include dedicated information that is different for each terminal apparatus 1 .

[0279] Part of the random access setting information may be associated with all SS / PBCH blocks in the SS burst set. Part of the random access setting information may be associated with all one or more CSI-RSs that are set. Part of the random access setting information may be associated with a downlink transmit beam (or beam index).

[0280] Part of the random access setting information may be associated with an SS / PBCH block in the SS burst set. Part of the random access setting information may be associated with one of the one or more CSI-RSs that are set. Part of the random access setting information may be associated with a downlink transmit beam (or beam index). However, information associated with an SS / PBCH block, a CSI-RS and / or a downlink transmit beam may include index information for determining a corresponding SS / PBCH block, a CSI-RS and / or a downlink transmit beam (for example, an SSB index, a beam index or a QCL setting index).

[0281] The following describes the PRACH opportunity.

[0282] The set of one or more PRACH opportunities that can be used for sending a random access preamble can be determined by an upper layer parameter prach-ConfigIndex provided by an upper layer (upper layer signal). According to the PRACH setting (physical random access channel setting) index given by prach-ConfigIndex and a pre-set table (also called a random access channel setting (PRACH config) table), a set of one or more PRACH opportunities that can be used for sending a random access preamble is determined. However, the one or more PRACH opportunities determined may be a set of PRACH opportunities that are associated with one or more SS / PBCH blocks sent by the base station device 3, respectively.

[0283] However, the PRACH configuration index can be used to repeat the period of the set of PRACH opportunities shown in the random access configuration table in time (PRACH configuration period (physical random access channel configuration period: PRACH configuration period)), the subcarrier index that can send a random access preamble, the resource block index, the subframe number, the time slot number, the system frame number, the symbol number and / or the format of the preamble.

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

[0285] However, the number of random access preambles mapped to each SS / PBCH block can be represented by the upper layer parameter cb-preamblePerSSB provided by the upper layer. The number of random access preambles mapped to each SS / PBCH block through each PRACH opportunity can be calculated based on SSB-perRACH-Occasion and cb-preamblePerSSB. The index of the random access preamble mapped to each SS / PBCH block through each PRACH opportunity can be determined based on SB-perRACH-Occasion, cb-preamblePerSSB and SSB index.

[0286] For PRACH opportunities, the SSB index can be mapped by the following rules.

[0287] (1) First, mapping is performed in ascending order of preamble indexes through a PRACH opportunity. For example, when the number of preambles of a PRACH opportunity is 64 and the number of random access preambles mapped to each SS / PBCH block through each PRACH opportunity is 32, the SSB indexes mapped to a certain PRACH opportunity are n and n+1.

[0288] (2) Second, multiple frequency-division multiplexed PRACH opportunities are mapped in ascending order of frequency resource index. For example, when two PRACH opportunities are frequency-division multiplexed, and the SSB indexes mapped to the PRACH opportunity with a smaller frequency resource index are n and n+1, the SSB indexes mapped to the PRACH opportunity with a larger frequency resource index are n+2 and n+3.

[0289] (3) Third, multiple PRACH opportunities that are time-division multiplexed in the PRACH time slot are mapped in ascending order of time resource index. For example, based on the example in (2) above, when two PRACH opportunities are further multiplexed in the time direction in the PRACH time slot, the SSB indexes mapped to these PRACH opportunities are n+4, n+5 and n+6, n+7.

[0290] (4) Fourth, multiple PRACH time slots are mapped in ascending order of index. For example, based on the example in (3) above, when there is a RACH opportunity in the next PRACH time slot, the mapped SSB index is n+8, n+9, ... However, in the above example, when n+x is greater than the maximum value of the SSB index, the value of the SSB index returns to 0.

[0291] Fig.13 3. It is a diagram showing an example of allocation of SSB indices for PRACH opportunities according to an embodiment of the present invention. Fig.13 An example is shown in which there are two PRACH time slots in a certain time interval, there are two PRACH opportunities (RO) in the time direction, there are two PRACH opportunities (RO) in the frequency direction, and there are 0 to 11 SSB indexes. One PRACH opportunity is mapped with two SSB indexes, and the SSB indexes are mapped according to the above rules (1) to (4), and the mapping starts again from SSB index 0 from the seventh PRACH opportunity.

[0292] The SSB index is mapped to each PRACH opportunity, but when all PRACH opportunities within the PRACH setting period determined by prach-ConfigIndex are not mapped to all SSB indexes (all SS / PBCH blocks sent by the base station device 3), the SSB index can be mapped to multiple PRACH setting periods. However, the number of all SS / PBCH blocks sent by the base station device 3 can be represented by upper layer parameters. The period in which the PRACH setting period is repeated a specified number of times in a manner that maps all SSB indexes at least once is called an association period. The number of PRACH setting periods constituting the association period can use the minimum value that satisfies the above conditions in a set of multiple pre-set values. The set of multiple pre-set values ​​can be determined for each PRACH setting period. However, on the basis of mapping all SSB indexes to the PRACH opportunities within the association period, if the number of remaining PRACH opportunities is greater than the number of SS / PBCH blocks, the SSB index can be remapped. However, on the basis of mapping all SSB indexes to the PRACH opportunities within the association period, if the number of remaining PRACH opportunities is less than the number of SS / PBCH blocks, SSB indexes may not be mapped to the remaining PRACH opportunities. The period in which PRACH opportunities are successively allocated to all SSB indexes is called the SSB index allocation period. When SSB-perRACH-Occasion is greater than 1, each SSB index is mapped to one PRACH opportunity in one SSB index allocation period. When SSB-perRACH-Occasion is a value less than 1, each SSB index is mapped to 1 / SSB-perRACH-Occasion PRACH opportunities in one SSB index allocation period. The terminal device 1 can determine the association period based on the PRACH setting period represented by the PRACH setting index and the number of SS / PBCH blocks determined by the upper layer parameters provided by the upper layer (upper layer signal).

[0293] One or more random access preamble groups included in the random access setting information may be associated with each reference signal (e.g., SS / PBCH block, CSI-RS, or downlink transmit beam), respectively. Terminal device 1 may select a random access preamble group based on a received reference signal (e.g., SS / PBCH block, CSI-RS, or downlink transmit beam).

[0294] Among them, the random access preamble group associated with each SS / PBCH block can be determined by one or more parameters notified by the upper layer. One of the one or more parameters can be an index (e.g., a start index) of one or more available preambles. One of the one or more parameters can be the number of preambles that can be used for contention-based random access in each SS / PBCH block. One of the one or more parameters can also be the total number of preambles that can be used for contention-based random access and the number of preambles that can be used for non-contention-based random access in each SS / PBCH block. One of the one or more parameters can also be the number of SS / PBCH blocks associated with a PRACH opportunity.

[0295] Among them, the terminal device 1 can receive one or more downlink signals respectively transmitted using a downlink transmission beam, receive random access setting information associated with one of the downlink signals, and perform a random access process based on the received random access setting information. The terminal device 1 can receive one or more SS / PBCH blocks in an SS burst set, receive random access setting information associated with one of the SS / PBCH blocks, and perform a random access process based on the received random access setting information. The terminal device 1 can receive one or more CSI-RS, receive random access setting information associated with one of the CSI-RS, and perform a random access process based on the received random access setting information.

[0296] The one or more random access configuration information may include a random access channel configuration (RACH-Config) and / or a physical random access channel configuration (PRACH-Config).

[0297] The random access channel setting may include parameters related to random access of each reference signal.

[0298] The physical random access channel configuration may include parameters related to the physical random access channel of each reference signal (index of the PRACH configuration, PRACH opportunity, etc.).

[0299] One random access setting information may indicate parameters regarding random access corresponding to one reference signal, and a plurality of random access setting information may indicate parameters regarding a plurality of random accesses corresponding to a plurality of reference signals.

[0300] One random access configuration information may indicate parameters regarding physical random access corresponding to one reference signal, or may indicate parameters regarding multiple random accesses corresponding to multiple reference signals.

[0301] If the corresponding reference signal is selected, 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) can be selected.

[0302] The terminal device 1 may receive one or more random access setting information from a base station device 3 and / or a transceiver point 4 different from the base station device 3 and / or the transceiver point 4 that sends the random access preamble. For example, the terminal device 1 may send a random access preamble to the second base station device 3 based on at least one of the random access setting information received from the first base station device 3.

[0303] Among them, the base station device 3 can determine the downlink transmission beam that should be applied when sending a downlink signal to the terminal device 1 by receiving the random access preamble sent by the terminal device 1. The terminal device 1 can use the PRACH opportunity indicated by the random access setting information associated with a downlink transmission beam to send the random access preamble. The base station device 3 can determine the downlink transmission beam that should be applied when sending 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 of the random access preamble received.

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

[0305] The terminal device 1 can select one or more available random access preambles and / or one or more available PRACH opportunities for use in the random access process based on the propagation path characteristics between the terminal device 1 and the base station device 3. The terminal device 1 can select one or more available random access preambles and / or one or more available PRACH opportunities for use in the random access process based on the propagation path characteristics (for example, which can also be the reference signal received power (RSRP)) measured by the reference signal received from the base station device 3 (for example, SS / PBCH block and / or CSI-RS).

[0306] In this embodiment, in uplink resource allocation, uplink resource allocation type 0 and uplink resource allocation type 1 are supported. In uplink resource allocation type 0 (uplink resource allocation type 0, uplink type 0 resource allocation), resource block assignment information includes a bitmap representing resource block groups (RBGs, Resource Block Groups) allocated to the terminal device 1. A resource block group is a collection of continuous virtual resource blocks and can be defined by upper layer parameters.

[0307] Hereinafter, uplink resource allocation type 1 (uplink resource allocation type 1, uplink type 1 resource allocation) will be described.

[0308] Resource block assignment information is represented in N size BWP A set of non-interleaved virtual resource blocks consecutively allocated to the scheduled terminal device 1 in the activated BWP of size BWP is the number of resource blocks representing the bandwidth of the activated UL BWP. In the case where DCI format 0_0 is detected in the type 0-PDCCH common search space set in CORESET#0, size N size BWP Indicates the bandwidth of the initial UL BWP.

[0309] The uplink type 1 resource assignment field consists of the starting resource block (RB start , starting virtual resource block) and the number of consecutively allocated resource blocks (L RBs ) is composed of a resource indication value (RIV, Resource Indication Value) corresponding to the RB. That is, the resource indication value RIV is shown in the resource assignment field. start Indicates the starting position of the allocated resource block. RBs The resource indication value RIV indicates the number (length, size) of resource blocks of the allocated resources. The resource indication value RIV indicates the resources allocated with the corresponding UL BWP as the object. The UL BWP as the object may be the UL BWP to which the resource assignment (resource assignment field) is applied. The terminal device 1 first determines the UL BWP to which the resource assignment is applied, and then determines the resource allocation within the determined UL BWP. That is, the value of RIV is determined according to the size (N) of the UL BWP to which the resource assignment is applied. size BWP ), start resource block (RB start ) and the number of consecutively allocated resource blocks (L RBs In other words, the terminal device 1 calculates the resource allocation field based on the value of RIV and N size BWP The starting position of the resource blocks allocated in the UL BWP and the number of resource blocks allocated continuously are calculated. That is, the terminal device 1 interprets the bits of the resource assignment field for the UL BWP to which the resource assignment is applied. The base station device 3 determines the resource allocation within the UL BWP applied to the terminal device 1, generates the RIV based on the size of the applied UL BWP, and sends the resource assignment including the bit string representing the RIV to the terminal device 1.

[0310] The terminal device 1 determines the resource block allocation in the frequency direction (of the PUSCH) of the applicable UL BWP based on the bit string of the resource assignment field.

[0311] Fig.12 is a diagram showing an example of calculating RIV.

[0312] exist Fig.12 In (A), N size BWP is the number of resource blocks representing the bandwidth of the activated UL BWP. The value of RIV is based on the number of resource blocks N representing the bandwidth of the initial BWP. size BWP , the starting position of the resource block RB start and the number of consecutively allocated resource blocks L RBs To calculate. RB start is the starting position of the resource block for the activated UL BWP. RBs is the number of resource blocks that are continuously allocated to the activated BWP. start and the number of consecutively allocated resource blocks L RBs To determine the allocated resources for the activated BWP. In the event that a DCI format is detected in a common search space set (e.g., a type 1 PDCCH common search space set), Fig.12 N in (A) size BWP The number of resource blocks used to represent the bandwidth of the initial UL BWP.

[0313] exist Fig.12 In (B), N nitial BWP N is the number of resource blocks representing the bandwidth of the initial BWP (UL BWP). active BWP is the number of resource blocks representing the bandwidth of the activated BWP (UL BWP). The value of RIV is based on the number of resource blocks N representing the bandwidth of the initial BWP. nitial BWP , the starting position of the resource block RB' start And the number of consecutively allocated resource blocks L' RBs To calculate. RB' start is the starting position of the resource block for the initial BWP. RBs RB' is the number of resource blocks that are continuously allocated for the initial BWP. start Multiply by the coefficient K to get RB start . L' RBs Multiply by the coefficient K to get L RBsThe value of coefficient K is calculated based on the bandwidth of the initial BWP and the bandwidth of the activated BWP. active BWP Greater than N nitial BWP In the case of active BWP / N nitial BWP ) value. Here, the function Floor(A) outputs the largest integer not higher than A. active BWP Equal to or less than N nitial BWP In the case of , the value of K is 1. Therefore, according to the starting position RB of the resource block start and the number of consecutively allocated resource blocks L RBs To determine the allocated resources for the activated BWP.

[0314] exist Fig.12 In the resource determination method of (B), the size of the DCI format in the USS (or the size of the frequency domain resource assignment field included in the DCI format) is derived according to the initial BWP, but it can also be used in the case of applying to the activated BWP. The DCI format can be DCI format 0_0 and / or DCI format 0_1.

[0315] Fig.11 FIG. 1 is a diagram showing an example of uplink resource allocation type 1 for BWP.

[0316] exist Fig.11 In the example, one initial UL BWP (1101) and two additional UL BWPs (1102 and 1103) are set for the terminal device 1. As described above, the shared resource block n PRB The resource blocks are numbered in ascending order starting from 0 in each subcarrier spacing setting μ starting from point A. That is, 1114 is a common resource block numbered 0 (common resource block 0). In the subcarrier spacing setting μ, common resource block 0 (common resource block index 0, n CRB#0) coincides with point A. 1104 is the starting position of the carrier in the subcarrier spacing setting μ, which is given by the upper-layer parameter OffsetToCarrier. That is, the upper-layer parameter OffsetToCarrier is the offset in the frequency domain between point A and the lowest subcarrier that can be used by the carrier. The offset (1115) represents the number of resource blocks in the subcarrier spacing setting μ. That is, when the subcarrier spacing setting μ is different, the frequency band of the frequency domain of the offset is different. In the subcarrier spacing setting μ, 1104 can be the position of the resource block where the carrier starts. The physical resource block is a resource block that is numbered in ascending order starting from 0 for each BWP. In the subcarrier spacing setting μ of each BWP index i, the physical resource block n in the BWP index i PRB Shared resource block n CRB The relationship is given by (Formula 3)n CRB =n PRB +N start BWP，i In the subcarrier spacing setting μ of each BWP, N start BWP，i is the number of common resource blocks starting with BWP index i for common resource block index 0. N size BWP，i It is the number of resource blocks representing the bandwidth of the BWP with index i in the subcarrier spacing configuration μ of the BWP index i.

[0317] The frequency domain location and bandwidth of the BWP are given by the upper layer parameter locationAndBandwidth. Specifically, the first physical resource block (physical resource block index 0) and the number of consecutive physical resource blocks of BWP index i are 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. Fig.12 As shown in (A), N size BWP Set to 275. In addition, the RB identified by the RIV value start and L RBs The first physical resource block (physical resource block index 0) representing the BWP and the number of consecutive physical resource blocks representing the bandwidth of the BWP. The first physical resource block of BWP index i is the physical resource block offset relative to the physical resource block (1104) indicated by the upper layer parameter OffsetToCarrier. The number of resource blocks representing the bandwidth of BWP index i is N size BWP，i . N of BWP index i star tBWP，iIt is given according to the first physical resource block with BWP index i and the offset indicated by the upper layer parameter OffsetToCarrier.

[0318] That is, in Fig.11 In the subcarrier spacing setting μ of UL BWP#0, 1105 is the physical resource block index 0 (n PRB The relationship between the physical resource blocks and the shared resource blocks in UL BWP#0 is given by n CRB =n PRB +N start BWP，0 In the subcarrier spacing setting μ of UL BWP#0, N start BWP，0 (1107) is the common resource block starting from UL BWP#0 with common resource block index 0. size BWP，0 (1106) represents the number of resource blocks of the bandwidth of ULBWP#0 in the subcarrier spacing configuration μ of UL BWP#0.

[0319] exist Fig.11 In the subcarrier spacing setting μ of UL BWP#1, 1108 is the physical resource block index 0 (n PRB #0). The relationship between the physical resource blocks and the shared resource blocks in UL BWP#1 is given by n CRB =n PRB +N start BWP，1 In the subcarrier spacing setting μ of UL BWP#1, N start BWP，1 (1110) is the common resource block starting from ULBWP#1 with common resource block index 0. size BWP，1 (1109) represents the number of resource blocks of the bandwidth of UL BWP#0 in the subcarrier spacing setting μ of UL BWP#1.

[0320] exist Fig.11 In the subcarrier spacing setting μ of UL BWP#2, 1111 is the physical resource block index 0 (n PRB #0). The relationship between the physical resource blocks and the shared resource blocks in UL BWP#2 is given by n CRB =n PRB +N start BWP，2 In the subcarrier spacing setting μ of UL BWP#2, N start BWP，2 (1113) is the common resource block starting from ULBWP#2 with common resource block index 0. size BWP，2 (1112) represents the number of resource blocks of the bandwidth of UL BWP#2 in the subcarrier spacing setting μ of UL BWP#2.

[0321] from Fig.11 From the perspective of each BWP set in the terminal device 1, the starting position (starting shared resource block, N start BWP ) and the number of resource blocks (N size BWP ) is different. When the terminal device 1 interprets the RIV indicated by the bits of the resource assignment field, it is necessary to determine the UL BWP to which the resource assignment is applied. That is, the terminal device 1 can determine the UL BWP to which the resource assignment is applied, and based on the N of the determined UL BWP size BWP，i To explain RIV, calculate the starting resource block (RB start ) and the number of consecutively allocated resource blocks (L RBs ). The calculated RB start Indicates the position where the resources to be allocated start with reference to the physical resource block index 0 of the UL BWP to which the resource assignment is applied. For example, even if the calculated RB start The value of is the same, when the UL BWP for applying resource assignment is different, the position of the starting common resource block is also different.

[0322] In addition, the size N of the UL BWP for resource assignment is applied size BWP When the number of resource block assignment bits indicating the value of RIV is different, the number of bits indicating the value of RIV is also different. The number of bits of the resource block assignment field indicating the value of RIV is determined by Ceiling(log2(N size BWP (N size BWP +1) / 2)) is given.

[0323] Figure 8 It is a diagram showing an example of a random access procedure of the terminal device 1 according to the present embodiment.

[0324] <Message 1 (S801)>

[0325] In S801, the terminal device 1 sends a random access preamble to the base station device 3 via the PRACH. The sent random access preamble may also be referred to as message 1 (Msg1). The sending of the random access preamble is also referred to as PRACH sending. The random access preamble is configured to notify the base station device 3 of information by using one of a plurality of sequences. For example, 64 sequences (the random access preamble index is numbered from one to sixty-four) are prepared. When 64 sequences are prepared, 6 bits of information (which may also be ra-PreambleIndex or preamble index) can be indicated to the base station device 3. The information can be represented as a random access preamble identifier (RAPID: Random Access preamble Identifier).

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

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

[0328] <Message 2 (S802)>

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

[0330] The random access response may also be referred to as message 2 or Msg2. In addition, the base station device 3 includes the random access preamble identifier corresponding to the received random access preamble and the RAR message (MAC RAR) corresponding to the identifier in message 2. The base station device 3 calculates the offset of the transmission timing between the terminal device 1 and the base station device 3 based on the received random access preamble, and includes the transmission timing adjustment information (TA command, Timing Advance Command) used to adjust the offset in the RAR message. The RAR message includes at least: a random access response authorization field mapped to an uplink authorization, a temporary C-RNTI (Cell Radio Network Temporary Identifier) ​​field mapped to a temporary C-RNTI, and a TA command (Timing Advance Command). The terminal device 1 adjusts the timing of PUSCH transmission based on the TA command. The timing of PUSCH transmission can be adjusted according to the group of cells. In addition, the base station device 3 includes the random access preamble identifier corresponding to the received random access preamble in message 2.

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

[0332] When the terminal device 1 detects a DCI format 1_0 with a CRC encrypted by RA-RNTI and a PDSCH including a DL-SCH transport block within the window period, the terminal device 1 transmits the transport block to the upper layer. The upper layer parses the transport block for a random access preamble identifier (RAPID) associated with the PRACH transmission. When the upper layer identifies the RAPID included in the RAR message of the DL-SCH transport block, the upper layer indicates an uplink grant to the physical layer. Identification means that the RAPID included in the received random access response is the same as the RAPID corresponding to the random access preamble sent. The uplink grant is called a random access response uplink grant (RAR UL grant) at the physical layer. That is, the terminal device 1 can determine the RAR message (MAC RAR) with the device itself as the destination from the base station device 3 by monitoring the random access response (message 2) corresponding to the random access preamble identifier.

[0333] In the case where (i) the terminal device 1 does not detect the DCI format 1_0 to which the CRC encrypted by the RA-RNTI is attached within the window period, or (ii) the terminal device 1 does not correctly receive the DL-SCH transport block in the PDSCH within the window period, or (iii) the upper layer does not identify the RAPID associated with the PRACH transmission, the upper layer instructs the physical layer to send the PRACH.

[0334] When the received random access response includes a random access preamble identifier corresponding to the sent 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 regards that the non-competitive random access process has been successfully completed, and sends PUSCH based on the uplink authorization included in the random access response.

[0335] When the random access preamble identifier corresponding to the transmitted random access preamble is included in the received random access response and the terminal device 1 selects the random access preamble by itself, the TC-RNTI is set to the value of the TC-RNTI field included in the received random access response, and the random access message 3 is transmitted through the PUSCH based on the uplink grant included in the random access response. The PUSCH corresponding to the uplink grant included in the random access response transmits the corresponding preamble in the serving cell transmitted through the PRACH.

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

[0337] exist Fig. 9 When the value of the frequency hopping flag in is 0, the terminal device 1 transmits the Msg3 PUSCH without frequency hopping. When the value of the frequency hopping flag is 1, the terminal device 1 transmits the Msg3 PUSCH with frequency hopping.

[0338] The "Msg3 PUSCH time resource allocation" field is used to indicate resource allocation in the time domain for Msg3 PUSCH.

[0339] The "MCS" field is used to determine the MCS index used for Msg3 PUSCH.

[0340] The "TPC command for Msg3 PUSCH" field is used to set the transmission power of Msg3 PUSCH.

[0341] In a contention-based random access procedure, the "CSI request (CST request)" field is reserved. In a non-contention-based random access procedure, the "CSI request" field is used to determine whether an aperiodic CSI report is included in the PUSCH transmission.

[0342] The following is an explanation of the "Msg3 PUSCH frequency resource allocation" field. This field is used to allocate resources 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 is independent of the bandwidth of the UL BWP set for the terminal device 1 and has a fixed number of bits. The terminal device 1 determines the number of resource blocks (N) based on the bandwidth of the UL BWP to which the resource assignment is applied. size BWP ), the Msg3PUSCH frequency resource assignment is cut or inserted with bits. Moreover, the terminal device 1 can make it suitable for the bandwidth of the UL BWP to which the resource assignment is applied by cutting or inserting bits in the Msg3 PUSCH frequency resource assignment. size BWP is the number of resource blocks representing the bandwidth of the UL BWP to which the resource assignment is applied. In the following S802, the UL BWP to which the resource assignment is applied is the UL BWP to which the Msg3PUSCH frequency resource assignment is applied.

[0343] Fig.10 This is a diagram showing an example of interpretation of the "Msg3 PUSCH frequency resource allocation" field according to the present embodiment.

[0344] Fig.10 In (A), 1001 is a "Msg3 PUSCH frequency resourceallocation" field having a fixed 14 bits. 1002 is N UL，hop Frequency hopping bit. 1003 is 1001 minus N UL，hop The remaining bits are (14-N UL，hop ) bits. That is, the 14-bit 1001 is composed of 1002 and 1003. UL，hop The number of frequency hopping bits is based on the value indicated in the "Frequency hopping flag" field and / or N size BWP For example, N UL，hop The number of bits in the example is N size BWPWhen the size of N is smaller than the value of the specified number of resource blocks, it may be 1 bit. UL，hop The number of bits in the example is N size BWP If the size of is greater than or equal to the value of the specified number of resource blocks, it can be 2 bits. The value of the specified number of resource blocks can be 50. N size BWP The description will be given later.

[0345] As mentioned above, when the value of the frequency hopping flag is 0, N UL，hop The frequency hopping bit is 0 bit. In this case, 1003 is 1001, which has 14 bits. When the value of the frequency hopping flag (Frequency hopping flag) is 1, N UL，hop The number of frequency hopping bits can be based on N size BWP The value of exceeds the value Y of the specified number of resource blocks, which is given as 1 bit or 2 bits. size BWP If the value Y is less than the specified number of resource blocks, N UL，hop The frequency hopping bit can be given as 1 bit. size BWP If the value Y is greater than or equal to the specified number of resource blocks, N UL，hop The frequency hopping bit can be given as 2 bits, that is, 1003 has 12 bits or 13 bits.

[0346] Fig.10 (B) means that in N size BWP A diagram of an example of clipping the bits of the "Msg3PUSCH frequency resource allocation" field when the value X is less than or equal to the specified number of resource blocks.

[0347] exist Fig.10 In (B), terminal device 1 is in N size BWP When the value X is less than or equal to the specified number of resource blocks, the bits of the Msg3 PUSCH frequency resource assignment are cut from the least significant bit (LSB) by b bits. That is, b bits are the number of bits to be cut. The value of b is calculated by (Equation 1) b = Ceiling (log2 (N size BWP (N size BWP+1) / 2)). Here, the function Ceiling(A) outputs the smallest integer not less than A. The clipped Msg3 PUSCH frequency resource assignment may also be referred to as a clipped resource block assignment. The terminal device 1 may interpret the clipped resource block assignment according to the rules for the ordinary DCI format 0_0.

[0348] exist Fig.10 In (B), 1004 is a 14-bit Msg3 PUSCH frequency resource assignment. 1005 is N UL，hop 1006 is the frequency hopping bit in Msg3 PUSCH frequency resource assignment except N UL，hop The bits other than the frequency hopping bits. 1008 is the cut resource block assignment. The number of bits of 1008 is b bits. The number of bits of 1007 is 14-b.

[0349] Fig.10 (C) means that in N size BWP A diagram of an example of the bits into which the "Msg3 PUSCH frequency resource allocation" field is inserted when the bandwidth is greater than the value X of the prescribed number of resource blocks.

[0350] exist Fig.10 In (C), 1009 is a 14-bit Msg3 PUSCH frequency resource assignment. 1010 is N UL，hop 1012 is the frequency hopping bit removed from the Msg3 PUSCH frequency resource assignment. UL，hop The number of bits in 1012 is (14-N UL，hop ) bits. Terminal device 1 is in N size BWP If the value X is greater than the specified number of resource blocks, N in the Msg3PUSCH frequency resource assignment UL，hop After the frequency hopping bit, the b most significant bits (MSB) set to "0" are inserted. That is, b bits are the number of inserted bits. The value of b is given by (Formula 2) b = (Ceiling (log2 (N size BWP (N size BWP +1) / 2))-Z). The value of Z may be 14. The Msg3 PUSCH frequency resource assignment with b bits inserted may also be referred to as an extended resource block assignment. The terminal device 1 may interpret the extended resource block assignment according to the rules for the ordinary DCI format 0_0. Fig.10In (C), the number of bits 1011 is b bits. 1009 is the extended resource block assignment. The number of bits 1009 is the sum of 14 bits of Msg3 PUSCH frequency resource assignment and b bits.

[0351] As described above, one initial BWP including at least one DL BWP and one UL BWP is set for the terminal device 1. Furthermore, a maximum of four additional BWPs are set for the terminal device 1. Furthermore, the size (N) of each UL BWP set for the terminal device 1 size BWP ) can be different. The size N of UL BWP size BWP is the number of resource blocks representing the bandwidth of the corresponding UL BWP. When determining resource allocation, the terminal device 1 first determines the UL BWP to which resource assignment is applied, and then determines resource allocation within the determined UL BWP.

[0352] When the terminal device 1 cuts or inserts bits in the Msg3 PUSCH frequency resource assignment, the terminal device 1 determines the UL BWP to which the resource assignment is applied. That is, the terminal device 1 determines N indicating the bandwidth of the UL BWP used when the Msg3 PUSCH frequency resource assignment is cut or inserted bits based on the UL BWP to which the resource assignment is applied. size BWP .

[0353] In the present embodiment, N represents the bandwidth of the UL BWP to which resource assignment is applied (the UL BWP to be explained). size BWP The base station device 3 determines N in the random access process. size BWP , using the determined N size BWP To generate RIV, determine the bit string included in the field of frequency resource assignment, and send the PUSCH frequency resource assignment to terminal device 1.

[0354] As described above, the terminal device 1 monitors the DCI format with the CRC encrypted by the RA-RNTI or TC-RNTI in the search space (type 1 PDCCH common search space set) used for the random access process. The terminal device 1 receives the random access response by monitoring the DCI format with the CRC encrypted by the RA-RNTI in the search space set. The setting information of the CORESET used for the type 1 PDCCH common search space set is indicated to the terminal device 1.

[0355] In one solution of the present embodiment, in the contention-based random access process, the terminal device 1 may determine a UL BWP having a BWP identifier as the UL BWP for application resource assignment, the BWP identifier being the same as the DL BWP having the setting information of the CORESET associated with the search space (type 1 PDCCH common search space set) used for the random access process. That is, in the contention-based random access process, N size BWP is the number of resource blocks indicating the bandwidth of the UL BWP having the same BWP identifier as the DL BWP configured with the configuration information of the CORESET associated with the type 1 PDCCH common search space set. size BWP The bit of the cut resource block assignment or the extended resource block assignment indicates the value of RIV. The terminal device 1 can use the determined N size BWP Used for Fig.12 N size BWP , to calculate RB start and L RBs RB calculated based on the RIV value start Indicates the starting position of resources allocated based on the physical resource block index 0 of the UL BWP to which resource assignment is applied. In other words, the numbering of resource allocation indicated by the RAR UL grant starts in ascending order from the physical resource block index 0 corresponding to the UL BWP to which resource assignment is applied (the lowest number of the physical resource blocks of the UL BWP to which resource assignment is applied).

[0356] In one scheme of the present embodiment, during the contention-based random access process, the terminal device 1 determines either the initial UL BWP or the activated UL BWP as the UL BWP for application resource assignment based on whether the DL BWP with the setting information of the CORESET associated with the type 1 PDCCH common search space set is the initial DL BWP. For example, the terminal device 1 may determine the initial ULBWP as the UL BWP for application resource assignment when the DL BWP with the setting information of the CORESET associated with the type 1 PDCCH common search space set is the initial DL BWP. In addition, the terminal device 1 may determine the activated UL BWP as the UL BWP for application resource assignment when the DL BWP with the setting information of the CORESET associated with the type 1 PDCCH common search space set is not the initial DL BWP. Furthermore, N size BWPis the number of resource blocks indicating the bandwidth of the UL BWP. Furthermore, the terminal device 1 uses N as the bandwidth of the UL BWP determined as the UL BWP to which the resource assignment is applied. size BWP , cut or insert bits for Msg3 PUSCH frequency resource assignment.

[0357] In addition, in one scheme of the present embodiment, during the contention-based random access process, the terminal device 1 determines either the initial UL BWP or the activated UL BWP as the UL BWP for application resource assignment based on whether the CORESET associated with the type 1 PDCCH common search space set is a public CORESET. For example, the terminal device 1 may determine the initial UL BWP as the UL BWP for application resource assignment when the CORESET associated with the type 1 PDCCH common search space set is a public CORESET. In addition, the terminal device 1 may determine the activated UL BWP as the UL BWP for application resource assignment when the CORESET associated with the type 1 PDCCH common search space set is not a public CORESET. Moreover, N size BWP is the number of resource blocks representing the bandwidth of the UL BWP to which the resource assignment is applied. size BWP To cut or insert bits for Msg3 PUSCH frequency resource assignment.

[0358] In addition, as an extension of the above-mentioned scheme, in the contention-based random access process, the terminal device 1 determines either the initial UL BWP or the activated ULBWP as the UL BWP for application resource assignment based on whether the CORESET associated with the type 1 PDCCH common search space set is CORESET#0. For example, the terminal device 1 may determine the initial UL BWP as the UL BWP for application resource assignment when the CORESET associated with the type 1 PDCCH common search space set is CORESET#0. In addition, the terminal device 1 may determine the activated UL BWP as the UL BWP for application resource assignment when the CORESET associated with the type 1 PDCCH common search space set is not CORESET#0. In addition, the terminal device 1 may determine the UL BWP with the same BWP identifier as the DL BWP with the additional public CORESET as the UL BWP for application resource assignment when the CORESET associated with the type 1 PDCCH common search space set is an additional public CORESET. That is, the terminal device 1 can determine the initial UL BWP as the UL BWP for application resource assignment when an additional common CORESET is set for the initial DL BWP. The terminal device 1 can determine the UL BWP having the same BWP identifier as the additional DL BWP as the UL BWP for application resource assignment when an additional common CORESET is set for the additional DL BWP.

[0359] In addition, in one solution of this embodiment, in the contention-based random access process, the terminal device 1 can always determine the initial UL BWP as the UL BWP for application resource assignment. That is, in the contention-based random access process, N size BWP is the number of resource blocks representing the bandwidth of the initial UL BWP. size BWP The bit of the cut resource block assignment or the extended resource block assignment indicates the value of RIV. The terminal device 1 can use the determined N size BWP Used for Fig.12 N size BWP , determine the generation of RIV. RIV is based on RB start and L RBs Generate, terminal device 1 obtains RB according to RIV start and L RBs RB startIndicates the starting position of resources allocated with reference to physical resource block index 0 corresponding to the initial UL BWP. In other words, the numbering of resource allocation indicated by the RAR UL grant starts from physical resource block index 0 corresponding to the initial UL BWP (the lowest number of physical resource blocks of the UL BWP to which resource assignment is applied).

[0360] In addition, in one solution of this embodiment, in the non-contention-based random access process, the terminal device 1 can always determine the activated UL BWP as the UL BWP for application resource assignment. That is, in the non-contention-based random access process, N size BWP is the number of resource blocks representing the bandwidth of the activated UL BWP. size BWP The bit of the cut resource block assignment or the extended resource block assignment indicates the value of RIV. The terminal device 1 can use the determined N size BWP Used for Fig.12 N size BWP , determine the generation of RIV. RIV is based on RB start and L RBs Generate, terminal device 1 obtains RB according to RIV start and L RBs RB start Indicates the starting position of resources allocated with reference to physical resource block index 0 corresponding to the activated UL BWP. In other words, the numbering of resource allocation indicated by the RAR UL grant starts from physical resource block index 0 corresponding to the activated UL BWP (the lowest number of physical resource blocks of the UL BWP to which resource assignment is applied).

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

[0362] In the above scheme, in the process of non-contention-based random access, the terminal device 1 determines the activated UL BWP as the UL BWP for application resource assignment regardless of whether the CORESET associated with the type 1 PDCCH common search space set is a public CORESET. In addition, in the process of non-contention-based random access, the terminal device 1 determines the activated UL BWP as the UL BWP for application resource assignment regardless of whether the DL BWP with the setting information of the CORESET associated with the type 1 PDCCH common search space set is the initial DL BWP.

[0363] That is, the terminal device 1 determines either the initial UL BWP or the activated UL BWP as the UL BWP (N) to which resource assignment is applied based on whether the random access procedure is based on a contention random access procedure or a non-contention random access procedure. size BWP ). For example, the 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 based on a contention random access procedure. size BWP is the number of resource blocks representing the bandwidth of the initial UL BWP. In addition, the terminal device 1 may determine the activated UL BWP as the UL BWP to which resource assignment is applied when the random access procedure is based on a non-contention random access procedure. Furthermore, N size BWP is the number of resource blocks representing the bandwidth of the activated UL BWP.

[0364] N UL，hop The number of frequency hopping bits may be based on the size of the UL BWP (N size BWP ) exceeds the specified number of resource blocks, and is given as 1 bit or 2 bits. size BWP It can be N which represents the bandwidth of the UL BWP for application resource assignment determined in the above scheme. size BWP That is, in N size BWP If the value Y is less than the specified number of resource blocks, N UL，hop The frequency hopping bit may be given as 1 bit. The frequency offset of the second hop for PUSCH transmission of message 3 is Floor(N size BWP / 2) or Floor(N size BWP / 4). size BWPIf the value Y is greater than or equal to the specified number of resource blocks, N UL，hop The frequency hopping bit can be given as 2 bits. The frequency offset of the second hop for PUSCH transmission of message 3 is Floor(N size BWP / 2)、Floor(N size BWP / 4) or -Floor(N size BWP / 4).

[0365] As described above, the resource block numbering (RBIndexing) of the resource allocation (uplink type 0 and / or type 1 resource allocation) is determined within the UL BWP of the application resource assignment representing the resource allocation. Specifically, when the BWP indication field (bandwidth part indicator field) is not set for the DCI format, the RB numbering of the resource allocation is determined within the activated BWP of the terminal device 1. However, even when the BWP indication field (bandwidth part indicator field) is not set for the DCI format, for the DCI format 0_0 detected in any common search space set in CORESET#0 (or an additional common CORESET in which the initial DL BWP is set), the RB numbering of the resource allocation is determined within the initial UL BWP. That is, even when the BWP indication field (bandwidth part indicator field) is not set for the DCI format, for the DCI format 0_0 detected in any common search space set in the CORESET in which the initial DL BWP is set, the RB numbering of the resource allocation is determined within the initial UL BWP. In addition, even when the BWP indicator field (bandwidth part indicator field) is not set for the DCI format, for DCI format 0_0 detected in any common search space set in the CORESET in which the activated BWP is set, the RB number of the resource allocation is marked as determined within the activated BWP.

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

[0367] In addition, for the RAR UL grant, the RB numbering notation of the uplink type 1 resource allocation can be determined within the activated BWP of the terminal device 1. In addition, in the contention-based random access process, the RB numbering notation of the resource allocation shown in the RAR UL grant is determined within the initial UL BWP of the terminal device 1. That is, in the contention-based random access process, the RB numbering notation of the resource allocation in the frequency direction of the PUSCH scheduled by the RAR UL grant (MAC RAR) is determined within the initial UL BWP of the terminal device 1. In addition, in the non-contention-based random access process, the RB numbering notation of the resource allocation shown in the RAR UL grant is determined within the activated UL BWP of the terminal device 1. That is, in the non-contention-based random access process, the RB numbering notation of the resource allocation in the frequency direction of the PUSCH scheduled by the RAR UL grant (MACRAR) is determined within the activated UL BWP of the terminal device 1.

[0368] In addition, in the contention-based random access process, when a DCI format 1_0 for scheduling a PDSCH (DL-SCH transport block) including a RAR UL grant is detected in a common search space (e.g., a type 1 PDCCH common search space) in CORESET#0, the RB number label of the resource allocation indicated by the RAR UL grant can be determined within the initial UL BWP of the terminal device 1. Here, the DCI format 1_0 is a DCI format 1_0 to which CRC parity bits scrambled by the corresponding corresponding RA-RNTI are attached. In addition, in the contention-based random access process, when a DCI format 1_0 for scheduling a PDSCH (DL-SCH transport block) including a RAR UL grant is detected in a common search space (e.g., a type 1 PDCCH common search space) in an additional common CORESET (or, a CORESET other than CORESET#0), the RB number label of the resource allocation indicated by the RAR UL grant can be determined within the activated UL BWP of the terminal device 1. However, when DCI format 1_0 for scheduling PDSCH (DL-SCH transport block) including RAR UL grant is detected in the common search space (for example, type 1 PDCCH common search space) in the additional common CORESET in which the initial DL BWP is set, the RB number label of the resource allocation indicated by the RAR UL grant can be determined within the initial UL BWP of terminal device 1.

[0369] In addition, for DCI format 0_0 scheduling retransmission of Msg3 PUSCH, the RB number of the resource allocation is marked as determined in the UL BWP to which the RAR UL grant (the resource block assignment included in the RAR UL grant) is applied. DCI format 0_0 scheduling retransmission of Msg3 PUSCH is scrambled by TC-RNTI. DCI format 0_0 does not include a BWP indication field.

[0370] <Message 3 (S803)>

[0371] Terminal device 1 performs PUSCH transmission of message 3 based on the RAR UL grant included in the RAR message received in S802. The PUSCH corresponding to the transmission of message 3 is transmitted in the serving cell of the preamble corresponding to the PRACH transmission. Specifically, the PUSCH corresponding to the transmission of message 3 is transmitted in the activated UL BWP.

[0372] <Retransmission of Message 3 (S803a)>

[0373] The 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 attached. That is, the PUSCH retransmission of the transport block sent by the 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 attached. This DCI format 0_0 is sent via the PDCCH of the type 1 PDCCH common search space set. That is, after the terminal device 1 sends message 3 in S803, the DCI format 0_0 for scheduling the retransmission of message 3 can be monitored. In S803a, if the terminal device 1 detects the DCI format 0_0 for scheduling the retransmission of message 3, S803b is executed.

[0374] The DCI format 0_0 for scheduling the retransmission of message 3 includes a frequency domain resource assignment field. The bits of this field are given based on the initial UL BWP. Specifically, the number of bits of this field is calculated by (Formula 4) Ceiling(log2(N UL，BWP RB (N UL，BWP RB +1) / 2)). Here, N UL，BWP RB It is the number of resource blocks representing the bandwidth of the initial UL BWP. That is, regardless of which UL BWP among the one or more UL BWPs set for the terminal device 1 is used to schedule resources for the retransmission of message 3, the number of bits of the frequency domain resource assignment field is a fixed value (the same value) based on the bandwidth of the initial UL BWP.

[0375] Furthermore, as an example, N UL，BWP RB It can be given based on the type of random access procedure. For example, in a contention-based random access procedure, N UL，BWP RB is the number of resource blocks representing the bandwidth of the initial UL BWP. In addition, for example, in a non-contention based random access procedure, N UL，BWP RB is the number of resource blocks representing the bandwidth of the activated UL BWP.

[0376] In order to make the bits of the frequency domain resource assignment field based on the initial UL BWP applicable to the bandwidth of the UL BWP to which the frequency domain resource assignment (frequency domain resource assignment field) is applied, the terminal device 1 needs to interpret. As described above, when the terminal device 1 cuts or inserts bits in the Msg3 PUSCH frequency resource assignment, it determines the ULBWP to which the Msg3 PUSCH frequency resource assignment is applied. Here, the UL BWP to which the frequency domain resource assignment field included in the DCI format 0_0 is applied can be determined by the same determination method as described above as the UL BWP to which the Msg3PUSCH frequency resource assignment is applied. That is, the UL BWP to which the frequency domain resource assignment included in the DCI format 0_0 can be the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied. That is, the terminal device 1 can determine the resource block allocation in the frequency direction of the PUSCH to which the ULBWP to which the Msg3 PUSCH frequency resource assignment is applied based on the value of the RIV shown by the frequency domain resource assignment field.

[0377] For example, in the case where the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied is the initial UL BWP (or the initially activated ULBWP), the UL BWP to which the frequency domain resource assignment field included in the DCI format 0_0 is applied is the initial UL BWP. The base station device 3 generates the RIV using the size of the initial UL BWP to which the resource assignment is applied, determines the bit string included in the frequency resource assignment field, and sends it to the terminal device 1. Moreover, the terminal device 1 determines the frequency-direction resource allocation of the PUSCH 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 can use Fig.12 (A) to determine the RB corresponding to the physical resource block of the initial BWP start and L RBs Here, Fig.12 N in (A) size BWP The value of the RIV indicated by the frequency domain resource assignment field is based on the size of the initial UL BWP to which the resource assignment is applied, the RB corresponding to the resource block of the initial UL BWP, and the start and L RBs To give. RB start The number of resource blocks indicating the starting position of resource allocation based on the physical resource block index 0 of the initial BWP UL. RBs The number of resource blocks in the bandwidth of the initial UL BWP cannot be exceeded. That is, the numbering of the resources indicated by the frequency domain resource assignment field starts from the smallest number of the physical resource blocks in the initial UL BWP.

[0378] From the above example, for the case where DCI format 0_0 is detected in the type 1 PDCCH common search space set in the additional common CORESET configured for CORESET#0 or the initial DL BWP, Fig.12 N in (A) size BWP Use the size of the initial UL BWP. Here, DCI format 0_0 can be monitored in the CSS. That is, when the activated UL BWP (UL BWP that sends uplink data) is not the initial UL BWP, the terminal device 1 also determines the resource block allocation in the frequency direction of the initial UL BWP. The value of the resource block offset between the physical resource block index 0 of the initial UL BWP and the physical resource block index 0 of the activated UL BWP is given by the upper layer parameter locationAndBandwidth set for each BWP. In addition, for the case where DCI format 0_0 is detected in any common search space set in the additional common CORESET set for CORESET#0 or the initial DL BWP, in Fig.12 N in (A) size BWP Use the size of the initial UL BWP.

[0379] For example, in the case where the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied is an activated UL BWP, the UL BWP to which the frequency domain resource assignment field included in the DCI format 0_0 is applied is an activated UL BWP. The base station device 3 generates the RIV using the size of the activated UL BWP to which the resource assignment is applied, determines the bit string included in the frequency resource assignment field, and sends it to the terminal device 1. Furthermore, the terminal device 1 determines the resource allocation in the frequency direction of the PUSCH to which the frequency domain resource assignment is applied. In the case where the activated UL BWP is not the initially activated UL BWP, the terminal device 1 can use Fig.12 Method (B) of determining the RB corresponding to the physical resource block of the activated UL BWP start and L RBs In this case, Fig.12 N in (B) nitial BWP N is the number of resource blocks representing the bandwidth of the initial UL BWP. active BWP is the number of resource blocks representing the bandwidth of the activated UL BWP. The value of RIV is based on the number of resource blocks N representing the bandwidth of the initial BWP. nitial BWP , the starting position of the resource block RB' startAnd the number of consecutively allocated resource blocks L' RBs To give. RB start The number of resource blocks indicating the starting position of resource allocation based on the physical resource block index 0 of the activated UL BWP. That is, the numbering of resources indicated by the frequency domain resource assignment field starts from the lowest number of the physical resource blocks of the activated UL BWP.

[0380] From the above example, the size of DCI format 0_0 in CSS (any common search space set or type 1 PDCCH common search space set) (or the size of the frequency domain resource assignment field included in the DCI format) is derived according to the size of the initial UL BWP, but in the case where the UL BWP to which the resource assignment of the Msg3 PUSCH frequency resource assignment field is applied is the activated UL BWP, it can be applied Fig.12 In other words, the size of DCI format 0_0 in the CSS (or the size of the frequency domain resource assignment field included in the DCI format) is derived according to the size of the initial UL BWP, but the size of the DCI format 0_0 (or the size of the frequency domain resource assignment field included in the DCI format) is applied to other activated UL BWPs (in the case of activated UL BWPs other than the initial UL BWP, the size of the DCI format 0_0 can be applied). Fig.12 Method (B). Here, the CSS is a CSS associated with a CORESET other than the additional common CORESET set for CORESET#0 and the initial DL BWP. That is, the CSS is a CSS associated with a CORESET set for a DL BWP other than the initial DL BWP. Here, DCI format 0_0 can be scrambled by TC-RNTI. That is, the DCI format is derived according to the size of the initial UL BWP, but when the UL BWP to which the DCI format is applied is another activated 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, it can be applied Fig.12 (B) method.

[0381] As described above, the number of bits of the frequency domain resource assignment field included in DCI format 0_0 is represented by N representing the bandwidth of the initial UL BWP. UL，BWP RB The frequency domain resource assignment field includes N UL，hop The number of frequency hopping bits can be based on N UL ，BWP RB Whether the number of resource blocks exceeds the specified number is given as 1 bit or 2 bits. In addition, the frequency domain resource assignment field includes NUL，hop The number of frequency hopping bits can be based on N size BWP Whether the number of resource blocks exceeds the specified number is given as 1 bit or 2 bits. size BWP is the number of resource blocks representing the bandwidth of the UL BWP to which the frequency domain resource assignment field is applied. size BWP If the value Y is less than the specified number of resource blocks, N UL，hop The frequency hopping bit may be given as 1 bit. The frequency offset of the second hop for PUSCH transmission of message 3 is Floor(N size BWP / 2) or Floor(N size BWP / 4). size BWP If the value Y is greater than or equal to the specified number of resource blocks, N UL，hop The frequency hopping bit can be given as 2 bits. The frequency offset of the second hop for PUSCH transmission of message 3 is Floor(N size BWP / 2)、Floor(N size BWP / 4) or -Floor(N size BWP / 4).

[0382] <Retransmission of Message 3 (S803b)>

[0383] In S803a, when DCI format 0_0 to which CRC parity bits scrambled by TC-RNTI are added is detected, the terminal device 1 performs PUSCH retransmission of the transport block transmitted in S803.

[0384] <Message 4 (S804)>

[0385] In response to the PUSCH transmission of message 3, the terminal device 1 to which the C-RNTI is not indicated monitors the DCI format 1_0 that schedules the PDSCH including the UE contention resolution identity. Here, the DCI format 1_0 is attached with CRC parity bits encrypted by the corresponding TC-RNTI. In response to the reception of the PDSCH with the UE contention resolution identity, the terminal device 1 sends HARQ-ACK information via the PUCCH. The transmission of the PUCCH can be performed in the activated UL BWP that sends message 3.

[0386] Thereby, the terminal device 1 performing the random access procedure can transmit uplink data to the base station device 3 .

[0387] Hereinafter, the configuration of the device according to this embodiment will be described.

[0388] Fig.15 This 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 is configured to include a wireless transceiver unit 10 and an upper layer processing unit 14. The wireless transceiver unit 10 is configured to include an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 is configured to include a media access control layer processing unit 15 and a wireless resource control layer processing unit 16. The wireless transceiver unit 10 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. The upper layer processing unit 14 is also referred to as a measuring unit, a selecting unit, or a controlling unit 14.

[0389] The upper layer processing unit 14 outputs the uplink data (also referred to as a transport block) generated by the user's operation, etc. to the wireless transceiver unit 10. The upper layer processing unit 14 performs part or all of the processing in the medium access control (MAC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the radio resource control (RRC) layer. The upper layer processing unit 14 may have a function of selecting a reference signal from one or more reference signals based on the measurement value of each reference signal. The upper layer processing unit 14 may also have a function of selecting a PRACH opportunity associated with the selected reference signal from one or more PRACH opportunities. The upper layer processing unit 14 may have a function of determining an index from one or more indexes set by the upper layer (e.g., the RRC layer) and setting it as the preamble index when the bit information included in the information indicating the start of the random access process received by the wireless transceiver unit 10 is a specified value. The upper layer processing unit 14 may have a function of determining an index associated with the selected reference signal among one or more indexes set by the RRC, and setting it as a preamble index. The upper layer processing unit 14 may have a function of determining the next available PRACH opportunity based on the received information (e.g., SSB index information and / or mask index information). The upper layer processing unit 14 may have a function of selecting an SS / PBCH block based on the received information (e.g., SSB index information).

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

[0391] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer (radio resource control layer) processing. The radio resource control layer processing unit 16 manages various setting information / parameters of the device itself. The radio resource control layer processing unit 16 sets various setting information / parameters based on the upper layer signal received from the base station device 3. That is, the radio resource control layer processing unit 16 sets various setting information / parameters based on the information indicating various setting information / parameters received from the base station device 3. The radio resource control layer processing unit 16 controls (determines) resource allocation based on the downlink control information received from the base station device 3.

[0392] The wireless transceiver 10 performs physical layer processing such as modulation, demodulation, encoding, 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 encoding the data, and sends it to the base station device 3. The wireless transceiver 10 may have a function of receiving one or more reference signals in a certain cell. The wireless transceiver 10 may have a function of receiving information (for example, SSB index information and / or mask index information) that determines one or more PRACH opportunities. The wireless transceiver 10 may have a function of receiving a signal including indication information indicating the start of a random access process. The wireless transceiver 10 may also have a function of receiving information that determines a specified index. The wireless transceiver 10 may have a function of receiving information that determines the index of a random access preamble. The wireless transceiver 10 may also have a function of sending a random access preamble through a PRACH opportunity determined by the upper layer processing unit 14.

[0393] The RF unit 12 converts (down-converts) the signal received via the antenna unit 11 into a baseband signal by orthogonal demodulation, and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit.

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

[0395] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the data to generate OFDM symbols, adds a CP to the generated OFDM symbols 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 .

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

[0397] Fig.16 1 is a schematic block diagram showing the structure of the base station device 3 of the present embodiment. As shown in the figure, the base station device 3 is configured to include a wireless transceiver unit 30 and an upper layer processing unit 34. The wireless transceiver unit 30 is configured to include an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 is configured to include 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 a sending unit, a receiving unit, a monitoring unit, or a physical layer processing unit. In addition, a control unit is also provided to control the operation of each unit based on various conditions. The upper layer processing unit 34 is also referred to as a control unit 34.

[0398] The upper layer processing unit 34 performs part or all of the processing in the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 34 may have a function of determining a 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 determine the PRACH opportunity for monitoring the random access preamble based on at least the SSB index information and the mask index information.

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

[0400] The wireless resource control layer processing unit 36 ​​included 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 in the terminal device 1. The wireless resource control layer processing unit 36 ​​generates or obtains downlink control information, downlink data (transmission block, random access response), system information, RRC message, MAC CE (Control Element) and the like configured in the physical downlink shared channel from the upper node, and outputs them to the wireless transceiver unit 30. In addition, the wireless resource control layer processing unit 36 ​​manages various setting information / parameters of each terminal device 1. The wireless resource control layer processing unit 36 ​​can set various setting information / parameters for each terminal device 1 via the upper layer signal. That is, the wireless resource control layer processing unit 36 ​​sends / broadcasts information indicating various setting information / parameters. The wireless resource control layer processing unit 36 ​​can send / broadcast information for determining the setting of one or more reference signals in a certain cell.

[0401] When an RRC message, MAC CE and / or PDCCH is sent from the base station device 3 to the terminal device 1, and the terminal device 1 performs processing based on the reception, the base station device 3 assumes that the terminal device performs the processing and performs processing (control of the terminal device 1 and the system). That is, the base station device 3 sends the RRC message, MAC CE and / or PDCCH to the terminal device 1 so that the terminal device performs processing based on the reception.

[0402] The wireless transceiver unit 30 has a function of sending one or more reference signals. In addition, the wireless transceiver unit 30 may have a function of receiving a signal including a beam failure recovery request sent from the terminal device 1. The wireless transceiver unit 30 may have a function of sending information (for example, SSB index information and / or mask index information) to determine one or more PRACH opportunities to the terminal device 1. The wireless transceiver unit 30 may also have a function of sending information to determine a specified index. The wireless transceiver unit 30 may also have a function of sending information to determine the index of the random access preamble. The wireless transceiver unit 30 may have a function of monitoring the random access preamble through the PRACH opportunity determined by the upper layer processing unit 34. In addition, the functions of a part of the wireless transceiver unit 30 are the same as those of the wireless transceiver unit 10, so the description is omitted. It should be noted that when the base station device 3 is connected to one or more transceiver points 4, part or all of the functions of the wireless transceiver unit 30 may also be included in each transceiver point 4.

[0403] In addition, the upper layer processing unit 34 performs transmission (forwarding) or reception of control messages or user data between the base station devices 3 or between the upper layer network device (MME, SGW (Serving-GW)) and the base station device 3. Fig.16In the figure, the components of other base station devices 3 and the propagation paths of data (control information) between the components are omitted, but it is obvious that as components, there are multiple blocks having other functions required to work as the base station device 3. For example, there are a radio resource management (Radio Resource Management) layer processing unit and an application layer processing unit in the upper layer processing unit 34. In addition, the upper layer processing unit 34 may also have a function of configuring multiple scheduling request resources corresponding to each of the multiple reference signals sent from the wireless transceiver unit 30.

[0404] It should be noted that the “unit” in the figure refers to an element that realizes the functions of the terminal device 1 and the base station device 3 and each process, expressed by terms such as components, circuits, constituent devices, equipment, and units.

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

[0406] (1) More specifically, the terminal device 1 of the first scheme of the present invention comprises: a receiving unit 10, which receives a PDSCH including a RAR message; and a control unit 16, which controls resource allocation based on a first field indicating a Msg3 PUSCH frequency resource assignment indicated by a first UL grant included in the RAR message, wherein the control unit cuts X bits from the least significant bits in the bits of the first field when the number of first resource blocks is less than or equal to a value of a prescribed number of resource blocks, and inserts the most significant bit of Y bits set to a value of "0" after a frequency hopping bit in the bits of the first field when the number of first resource blocks is greater than a value of a prescribed number of resource blocks, wherein the number of first resource blocks is given based on the type of random access procedure.

[0407] (2) In the first solution of the present invention, when the type of the random access procedure is a non-contention-based random access procedure, the number of the first resource blocks is the number of resource blocks representing the bandwidth of the activated UL BWP.

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

[0409] (4) The base station device 3 of the second scheme of the present invention comprises: a control unit 36, which generates a first UL grant including a first field indicating a Msg3 PUSCH frequency resource assignment indicating resource allocation; and a sending unit 30, which sends a PDSCH including a RAR message including the first UL grant, wherein the control unit cuts X bits from the least significant bits in the bits of the first field when the number of first resource blocks is less than or equal to the value of a prescribed number of resource blocks, and inserts the most significant bit of Y bits set to a value of "0" after the frequency hopping bit in the bits of the first field when the number of first resource blocks is greater than the value of the prescribed number of resource blocks, wherein the number of first resource blocks is given based on the type of random access procedure.

[0410] (5) In the second solution of the present invention, when the type of the random access procedure is a non-contention-based random access procedure, the number of the first resource blocks is the number of resource blocks representing the bandwidth of the activated UL BWP.

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

[0412] (7) A terminal device 1 for performing a contention-based random access procedure according to a third solution of the present invention comprises: a receiving unit 10 for receiving a PDSCH including a RAR message; and a control unit 16 for controlling resource allocation based on a first field indicating a Msg3 PUSCH frequency resource assignment indicated by a first UL grant included in the RAR message, wherein the control unit cuts X bits from the least significant bits in the bits of the first field when the number of first resource blocks is less than or equal to a value of a prescribed number of resource blocks, and inserts the most significant bit of Y bits set to a value of '0' after a frequency hopping bit in the bits of the first field when the number of first resource blocks is greater than a value of a prescribed number of resource blocks, wherein the number of first resource blocks is the number of resource blocks indicating a bandwidth of a UL BWP having a BWP identifier identical to a DL BWP having setting information of a CORESET indicated by a type 1 PDCCH common search space set, wherein the type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource used to search for downlink control information.

[0413] (8) A base station device 3 that communicates with a terminal device 1 that performs a contention-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 PUSCH frequency resource assignment indicating resource allocation in Msg3; and a transmission unit 30 that transmits a PDSCH including a RAR message, wherein the first UL grant is included in the RAR message, wherein the control unit cuts X bits from the least significant bits in the bits of the first field when the number of first resource blocks is less than or equal to a value of a predetermined number of resource blocks, and inserts the most significant bit of Y bits set to a value of "0" after the frequency hopping bit in the bits of the first field when the number of first resource blocks is greater than a value of a predetermined number of resource blocks, wherein the number of first resource blocks is the number of resource blocks representing a bandwidth of a UL BWP having a BWP identifier identical to a DL BWP having setting information of a CORESET indicated by a type 1 PDCCH common search space set, wherein the type 1 PDCCH common search space set is a search space set used for a random access procedure, and the CORESET is a time and frequency resource used to search for downlink control information.

[0414] (9) The terminal device 1 of the fifth scheme of the present invention comprises: a receiving unit 10, which receives a first DCI format encrypted by TC-RNTI in a search space set; and a control unit 16, which determines the resource allocation of PUSCH based on a second field representing the frequency domain resource assignment included in the first DCI format, and for the bits of the first field representing the Msg3PUSCH frequency resource assignment indicated in the first UL authorization included in the RAR message, based on the number of first resource blocks representing the bandwidth of the first UL BWP, cuts and / or inserts the most significant bits from the least significant bits, and the size of the second field is derived according to the bandwidth of the initial UL BWP, and the control unit determines the resource block allocation in the frequency direction applied to the first UL BWP based on the value of RIV indicated in the second field.

[0415] (10) In the fifth scheme of the present invention, when the first UL BWP is an activated 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, the control unit determines the resource allocation of the PUSCH by applying the second starting position and the second number of resource blocks obtained by scaling the first starting position and the number of first resource blocks by a factor K to the physical resource blocks of the activated UL BWP based on the value of the RIV indicated by the second field, and the CORESET is a time and frequency resource for searching for downlink control information.

[0416] (11) In the fifth scheme of the present invention, when the first UL BWP is an activated UL BWP other than the initial UL BWP, and the search space set is a common search space associated with the CORESET set for the initial DL BWP, the control unit identifies the first starting position of resource allocation and the number of first resource blocks allocated continuously based on the initial UL BWP according to the value of the RIV indicated by the second field, applies the identified first starting position and the number of first resource blocks to the physical resource blocks of the initial UL BWP, and determines the resource allocation of the PUSCH.

[0417] (12) In the fifth scheme of the present invention, when the first UL BWP is the initial UL BWP, according to the value of the RIV indicated by the second field, the first starting position of resource allocation and the number of first resource blocks that are continuously allocated are identified based on the initial UL BWP, 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 determine the resource allocation of the PUSCH.

[0418] (13) In the fifth scheme of the present invention, when the bandwidth of the activated UL BWP is greater than the bandwidth of the initial UL BWP, the coefficient K is given as the ratio of the bandwidth of the activated UL BWP to the initial UL BWP rounded to the nearest power of 2, and in other cases, it is given as 1.

[0419] (14) The base station device 3 of the sixth scheme of the present invention comprises: a control unit 36, which generates a first DCI format including a second field indicating a frequency domain resource assignment indicating resource allocation information; and a sending unit 30, which sends the first DCI format in a type 1 PDCCCH common search space set, wherein the first DCI format is encrypted by the TC-RNTI, and for the bits of the first field indicating the Msg3 PUSCH frequency resource assignment indicated by the first UL authorization included in the RAR message, based on the number of first resource blocks indicating the bandwidth of the first UL BWP, the most significant bits are cut and / or inserted from the least significant bits, and the size of the second field is derived according to the bandwidth of the initial UL BWP. The control unit determines the resource block allocation in the frequency direction of the PUSCH of the first UL BWP applied to the terminal device, and generates the value of the RIV indicated in the second field.

[0420] (15) In the sixth scheme of the present invention, when the first UL BWP is an activated 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, the control unit identifies the first starting position of resource allocation and the number of first resource blocks allocated continuously based on the initial ULBWP according to the value of the RIV indicated by the second field generated, and applies the second starting position and the number of second resource blocks obtained by scaling the first starting position and the number of first resource blocks by a factor K to the physical resource blocks of the activated UL BWP, thereby determining the resource allocation for the PUSCH applied to the terminal device, wherein the CORESET is a time and frequency resource for searching for downlink control information.

[0421] (16) In the sixth scheme of the present invention, when the first UL BWP is an activated 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 the first starting position of resource allocation and the number of first resource blocks continuously allocated based on the initial UL BWP according to the value of the RIV indicated by the second field generated, applies the identified first starting position and the number of first resource blocks to the physical resource blocks of the initial UL BWP, and determines the resource allocation for the PUSCH applied to the terminal device, wherein the CORESET is the time and frequency resources used to search for downlink control information.

[0422] (17) In the sixth scheme of the present invention, when the first UL BWP is the initial UL BWP, the control unit identifies the first starting position of resource allocation and the number of first resource blocks allocated continuously based on the initial UL BWP according to the value of the RIV indicated by the second field generated, applies the identified first starting position and the number of first resource blocks to the physical resource blocks of the initial UL BWP, and determines the resource allocation of the PUSCH applied to the terminal device.

[0423] (18) In the sixth scheme of the present invention, when the bandwidth of the activated UL BWP is greater than the bandwidth of the initial UL BWP, the coefficient K is given as the ratio of the bandwidth of the activated UL BWP to the initial UL BWP rounded to the nearest power of 2, and in other cases, it is given as 1.

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

[0425] The program running in the device involved in the present invention can be a program that controls a central processing unit (CPU) or the like to enable a computer to function in order to realize the functions of the embodiments involved in the present invention. The program or the information processed by the program is temporarily stored in a volatile memory such as a random access memory (RAM) or a non-volatile memory such as a flash memory, a hard disk drive (HDD) or other storage device system.

[0426] It should be noted that the program for realizing the functions of the embodiments of the present invention may also be recorded in a computer-readable recording medium. This can be realized by reading the program recorded in the recording medium into a computer system and executing it. The "computer system" referred to here refers to a computer system built into a device, and includes a computer system of hardware such as an operating system and peripherals. In addition, a "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or other computer-readable recording media.

[0427] In addition, each functional block or each feature of the device used in the above-mentioned embodiments can be installed or executed by an electronic circuit such as an integrated circuit or multiple integrated circuits. Circuits designed in a manner to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor may be a microprocessor, or it may be a processor, controller, microcontroller, or state machine of an existing type. The above-mentioned electronic circuit may be composed of a digital circuit or an analog circuit. In addition, in the case of the emergence of integrated circuit technology to replace existing integrated circuits through the advancement of semiconductor technology, one or more schemes of the present invention may also use new integrated circuits based on the technology.

[0428] It should be noted that, in the embodiments of the present invention, an example applicable to a communication system composed of a base station apparatus and a terminal apparatus is described, but it is also applicable to a system in which terminals communicate with each other such as D2D (Device to Device).

[0429] It should be noted that the invention of the present application is not limited to the above-mentioned embodiments. In the embodiments, an example of a device is described, but the invention of the present application is not limited thereto and can be applied to fixed or non-movable electronic devices set up indoors and outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as other living equipment.

[0430] Above, the embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiments, and also includes design changes within the scope of the gist of the present invention. In addition, the present invention can be variously modified within the scope shown in the technical solution, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other.

Claims

1. A terminal device that communicates with a base station device, the terminal device comprising: a receiving unit that receives the setting of the initial uplink partial bandwidth UL BWP and the setting of the additional UL BWP via a radio resource control RRC message, and receives downlink control information DCI format 0_0 for scheduling a physical uplink shared channel PUSCH in a type 1 PDCCH common search space; and a transmitting unit, configured to transmit the PUSCH in the activated UL BWP, One of the initial UL BWP and the additional UL BWP is activated as the activated UL BWP, The bit width of the first field in the DCI format 0_0 is determined based on the size of the initial UL BWP, The transmitting unit determines the resource blocks to be consecutively allocated for the PUSCH based on the resource indication value RIV indicated by the first field and the following formula: In for In this case, RIV is calculated by the following formula: to give; Otherwise, RIV is calculated by the following formula: to give; among them, In the formula is the size of the initial UL BWP, RB start is the starting position of the continuously allocated resource blocks in the activated UL BWP, L RBs is the number of the continuously allocated resource blocks, The numbering of the consecutively allocated resource blocks is determined within the activated UL BWP and starts from the lowest resource block of the activated UL BWP.

2. A base station device that communicates with a terminal device, the base station device being characterized in that it includes: a transmitting unit that transmits the setting of the initial uplink partial bandwidth UL BWP and the setting of the additional UL BWP via a radio resource control RRC message, and transmits downlink control information DCI format 0_0 for scheduling a physical uplink shared channel PUSCH in a type 1 PDCCH common search space; and a receiving unit, configured to receive the PUSCH in the activated UL BWP, One of the initial UL BWP and the additional UL BWP is activated as the activated UL BWP, The bit width of the first field in the DCI format 0_0 is determined based on the size of the initial UL BWP, The receiving unit determines the resource blocks that are consecutively allocated for the PUSCH based on the resource indication value RIV indicated by the first field and the following formula: In for In this case, RIV is calculated by the following formula: to give; Otherwise, RIV is calculated by the following formula: to give; among them, In the formula is the size of the initial UL BWP, RB start is the starting position of the continuously allocated resource blocks in the activated UL BWP, L RBs is the number of the continuously allocated resource blocks, The numbering of the consecutively allocated resource blocks is determined within the activated UL BWP and starts from the lowest resource block of the activated UL BWP.

3. A communication method for a terminal device communicating with a base station device, characterized in that: have: The step of receiving the setting of the initial uplink bandwidth portion UL BWP and the setting of the additional UL BWP via a radio resource control RRC message; A step of receiving downlink control information DCI format 0_0 for scheduling a physical uplink shared channel PUSCH in a type 1 PDCCH common search space; and The step of sending the PUSCH in the activated UL BWP, One of the initial UL BWP and the additional UL BWP is activated as the activated UL BWP, The bit width of the first field in the DCI format 0_0 is determined based on the size of the initial UL BWP, The communication method has a step of determining resource blocks that are consecutively allocated for the PUSCH based on a resource indication value RIV indicated by the first field and the following formula, In for In this case, RIV is calculated by the following formula: Otherwise, RIV is given by the following formula: to give; among them, In the formula is the size of the initial UL BWP, RB start is the starting position of the continuously allocated resource blocks in the activated UL BWP, L RBs is the number of the continuously allocated resource blocks, The numbering of the consecutively allocated resource blocks is determined within the activated UL BWP and starts from the lowest resource block of the activated UL BWP.

4. A communication method of a base station device for communicating with a terminal device, characterized in that: have: The step of sending the initial uplink bandwidth UL BWP setting and the additional UL BWP setting via a radio resource control RRC message; The step of sending downlink control information DCI format 0_0 for scheduling a physical uplink shared channel PUSCH in a type 1 PDCCH common search space; and The step of receiving the PUSCH in the activated UL BWP, One of the initial UL BWP and the additional UL BWP is activated as the activated UL BWP, The bit width of the first field in the DCI format 0_0 is determined based on the size of the initial UL BWP, The communication method has a step of determining resource blocks that are consecutively allocated for the PUSCH based on a resource indication value RIV indicated by the first field and the following formula, In for In this case, RIV is calculated by the following formula: Otherwise, RIV is given by the following formula: to give; among them, In the formula is the size of the initial UL BWP, RB start is the starting position of the continuously allocated resource blocks in the activated UL BWP, L RBs is the number of the continuously allocated resource blocks, The numbering of the consecutively allocated resource blocks is determined within the activated UL BWP and starts from the lowest resource block of the activated UL BWP.

Images