WO2020075775A1 - Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré - Google Patents

Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré Download PDF

Info

Publication number
WO2020075775A1
WO2020075775A1 PCT/JP2019/039893 JP2019039893W WO2020075775A1 WO 2020075775 A1 WO2020075775 A1 WO 2020075775A1 JP 2019039893 W JP2019039893 W JP 2019039893W WO 2020075775 A1 WO2020075775 A1 WO 2020075775A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
bwp
pusch
terminal device
access procedure
Prior art date
Application number
PCT/JP2019/039893
Other languages
English (en)
Japanese (ja)
Inventor
麗清 劉
山田　昇平
高橋　宏樹
星野　正幸
秀和 坪井
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2020075775A1 publication Critical patent/WO2020075775A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA

Definitions

  • the present invention relates to a base station device, a terminal device, a communication method, and an integrated circuit.
  • the present application claims priority based on Japanese Patent Application No. 2018-191530 filed on October 10, 2018 in Japan, the contents of which are incorporated herein by reference.
  • Non-Patent Document 1 LTE (Long Term Evolution) -Advanced Pro and NR (New Radio) are being used in the 3rd Generation Partnership Project (3GPP) as a wireless access method and wireless network technology for the 5th generation cellular system. technology) and standard development are being conducted (Non-Patent Document 1).
  • 3GPP 3rd Generation Partnership Project
  • machines such as eMBB (enhanced Mobile BroadBand) that realizes high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) that realizes low-delay and high-reliability communication, and IoT (Internet of Things) 3 types of mass machine type communication (mMTC), which is connected to many type devices, are required as the scenario for the service.
  • eMBB enhanced Mobile BroadBand
  • URLLC Ultra-Reliable and Low Latency Communication
  • IoT Internet of Things
  • An object of one aspect of the present invention is to provide a terminal device, a base station device, a communication method, and an integrated circuit that enable efficient communication in the above wireless communication system.
  • the embodiments of the present invention take the following means. That is, the terminal device according to one aspect of the present invention is scheduled by the receiving unit that receives the first parameter of the upper layer and receives the PDSCH including the RAR message, and the first UL grant included in the RAR message. And a transmitter for transmitting PUSCH, wherein the first parameter is used to enable transform precoding and the random access procedure is either a contention-based random access procedure or a non-contention-based random access procedure. Regardless, the transform precoding for PUSCH transmission is set to either'valid 'or'invalid' based on the first parameter.
  • the base station device transmits a first parameter of an upper layer and a PDSCH including a RAR message, and a first UL grant included in the RAR message.
  • Parameter is used to indicate the UE-specific selection of transform precoding for PUSCH, and in the non-contention based random access procedure, transform precoding for PUSCH transmission is set by the second parameter.
  • the second parameter if Based, it is set to one of 'valid' or 'invalid', if the second parameter is not set, on the basis of the first parameter is set to any of 'valid' or 'invalid'.
  • a communication method is a communication method for a terminal device, including receiving a first parameter of an upper layer, receiving a PDSCH including a RAR message, and including the PDSCH in the RAR message. Transmitting a PUSCH scheduled by a first UL grant, the first parameter is used to enable transform precoding, and the random access procedure is contention based random access procedure or non-contention based random access procedure. Regardless of any of the procedures, the transform precoding for the PUSCH transmission is set to either'valid 'or'invalid' based on the first parameter.
  • a communication method is a communication method for a base station device, including transmitting a first parameter of an upper layer, transmitting PDSCH including a RAR message, and including the RAR message.
  • PUSCH scheduled by a first UL grant is received, the first parameter is used to enable transform precoding, and the random access procedure is contention based random access procedure or contention based random Regardless of any access procedure, the transform precoding for the PUSCH transmission is set to either'valid 'or'invalid' based on the first parameter.
  • an integrated circuit is an integrated circuit installed in a terminal device, which has a function of receiving a first parameter of an upper layer and receiving a PDSCH including a RAR message, A function of transmitting the PUSCH scheduled by the first UL grant included in the RAR message, and the first parameter is used to enable transform precoding, and Regardless of whether the random access procedure is a contention-based random access procedure or a non-contention based random access procedure, transform precoding for the PUSCH transmission may be'valid 'or'invalid' based on the first parameter. It is set to either.
  • an integrated circuit is an integrated circuit installed in a base station device, and has a function of transmitting a first parameter of an upper layer and transmitting a PDSCH including a RAR message, The function of receiving the PUSCH scheduled by the first UL grant included in the RAR message, and the first parameter are used to enable transform precoding. Transform precoding for the PUSCH transmission is performed according to the first parameter regardless of whether the random access procedure is a contention based random access procedure or a non-contention based random access procedure. 'Is set to either.
  • the base station device and the terminal device can efficiently communicate with each other.
  • FIG. 6 is a diagram showing a relationship in the time domain of subframes, slots, and minislots according to the embodiment of the present invention. It is a figure which shows an example of the slot or sub-frame which concerns on embodiment of this invention. It is a figure showing an example of beamforming concerning an embodiment of the present invention. It is a figure which shows an example of the frequency hopping which concerns on embodiment of this invention.
  • FIG. 6 is a diagram illustrating an example of a second hop frequency offset for a PUSCH scheduled by a RAR UL grant with frequency hopping according to an embodiment of the present invention.
  • FIG. 1 is a conceptual diagram of a wireless communication system according to this embodiment.
  • the wireless communication system includes a terminal device 1A, a terminal device 1B, and a base station device 3.
  • the terminal device 1A and the terminal device 1B are also referred to as the terminal device 1.
  • the terminal device 1 is also called a user terminal, mobile station device, communication terminal, mobile device, terminal, UE (User Equipment), MS (Mobile Station).
  • the base station device 3 includes a radio base station device, a base station, a radio base station, a fixed station, an NB (Node B), an eNB (evolved Node B), a BTS (Base Transceiver Station), a BS (Base Station), and an NR NB ( It is also called NR Node B), NNB, TRP (Transmission and Reception Point), and gNB.
  • the base station device 3 may include a core network device.
  • the base station device 3 may include one or a plurality of transmission / reception points 4 (transmission reception point).
  • the base station device 3 may serve the terminal device 1 with the communicable range (communication area) controlled by the base station device 3 as one or a plurality of cells.
  • the base station device 3 may serve the terminal device 1 with the communicable range (communication area) controlled by the one or more transmitting / receiving points 4 as one or more cells.
  • one cell may be divided into a plurality of partial areas (Beamed area), and the terminal device 1 may be served in each partial area.
  • the partial region may be identified based on a beam index used in beam forming or a precoding index.
  • a wireless communication link from the base station device 3 to the terminal device 1 is called a downlink.
  • a wireless communication link from the terminal device 1 to the base station device 3 is called an uplink.
  • orthogonal frequency division multiplexing OFDM: Orthogonal Frequency Division Multiplexing
  • CP Cyclic Prefix
  • SC- FDM Single-Carrier Frequency Division Multiplexing
  • DFT-S-OFDM Discrete Fourier Transform Spread OFDM
  • MC-CDM Multi-Carrier Code Division Multiplexing
  • a universal filter multi-carrier (UFMC: Universal-Filtered Multi-Carrier), a filter OFDM (F-OFDM: Filtered OFDM), and a window function are used.
  • Multiplied OFDM (Windowed OFDM) and filter bank multi-carrier (FBMC: Filter-Bank Multi-Carrier) may be used.
  • OFDM is described as an OFDM transmission scheme, but the case of using the other transmission schemes described above is also included in the present invention.
  • the CP in the wireless communication between the terminal device 1 and the base station device 3, the CP may not be used, or the above-mentioned transmission method with zero padding may be used instead of the CP. Also, CP and zero padding may be added to both the front and the rear.
  • One aspect of this embodiment may be operated in carrier aggregation or dual connectivity with a radio access technology (RAT: Radio Access Technology) such as LTE or LTE-A / LTE-A Pro.
  • RAT Radio Access Technology
  • some or all cells or cell groups, carriers or carrier groups for example, primary cell (PCell: Primary Cell), secondary cell (SCell: Secondary Cell), primary secondary cell (PSCell), MCG (Master Cell Group) ), SCG (Secondary Cell Group), etc.
  • PCell Primary Cell
  • SCell Secondary Cell
  • PSCell primary secondary cell
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the SpCell is the PCell of the MCG or the PSCell of the SCG depending on whether the MAC (MAC: Medium Access Control) entity is associated with the MCG or the SCG, respectively. Called.
  • MAC Medium Access Control
  • one or more serving cells may be set for the terminal device 1.
  • the plurality of configured serving cells may include one primary cell and one or more secondary cells.
  • the primary cell may be a serving cell that has undergone the initial connection establishment procedure, a serving cell that has initiated the connection re-establishment procedure, or a cell designated as the primary cell in the handover procedure. Good.
  • One or a plurality of secondary cells may be set at the time when the RRC (Radio Resource Control) connection is established or later.
  • the plurality of configured serving cells may include one primary secondary cell.
  • the primary secondary cell may be a secondary cell capable of transmitting control information in the uplink among one or a plurality of secondary cells in which the terminal device 1 is set.
  • the master cell group may include one primary cell and zero or more secondary cells.
  • the secondary cell group may include one primary secondary cell and zero or more secondary cells.
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • the TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of the plurality of cells. Also, cells to which the TDD scheme is applied and cells to which the FDD scheme is applied may be aggregated.
  • the TDD method may be referred to as an unpaired spectrum operation.
  • the FDD method may be referred to as a paired spectrum operation.
  • the carrier corresponding to the serving cell is called the downlink component carrier (or downlink carrier).
  • a carrier corresponding to a serving cell is called an uplink component carrier (or an uplink carrier).
  • the carrier corresponding to the serving cell is called a side link component carrier (or side link carrier).
  • the downlink component carrier, the uplink component carrier, and / or the side link component carrier are collectively referred to as a component carrier (or carrier).
  • the following physical channels are used in the wireless communication between the terminal device 1 and the base station device 3.
  • PBCH Physical Broadcast CHannel
  • PDCCH Physical Downlink Control CHannel
  • PDSCH Physical Downlink Shared CHannel
  • PUCCH Physical Uplink Control CHannel
  • PUSCH Physical Uplink Shared CHannel
  • PRACH Physical Random Access CHannel
  • the PBCH is used to notify an important information block (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1.
  • MIB Master Information Block
  • EIB Essential Information Block
  • BCH Broadcast Channel
  • the PBCH may be used to broadcast a time index within a cycle of a block of a synchronization signal (also referred to as an SS / PBCH block).
  • the time index is information indicating the index of the synchronization signal and PBCH in the cell.
  • the SS / PBCH block is transmitted using the assumption of three transmission beams (transmission filter setting, pseudo co-location (QCL: Quasi Co-Location) regarding reception spatial parameters)
  • the SS / PBCH block is transmitted within a predetermined cycle or is set. It may indicate the time order within the cycle.
  • the terminal device may recognize the difference in time index as the difference in transmission beam.
  • the PDCCH is used to transmit (or carry) downlink control information (Downlink Control Information: DCI) in downlink radio communication (radio communication from the base station device 3 to the terminal device 1).
  • DCI Downlink Control Information
  • one or more DCIs (which may be referred to as DCI formats) are defined for transmission of downlink control information. That is, a field for downlink control information is defined as DCI and is mapped to information bits.
  • the PDCCH is transmitted in the PDCCH candidate.
  • the terminal device 1 monitors a set of PDCCH candidates (candidate) in the serving cell. Monitoring means trying to decode the PDCCH according to a certain DCI format.
  • DCI format 0_0 may be used for PUSCH scheduling in a certain serving cell.
  • the DCI format 0_0 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation).
  • the DCI format 0_0 may include a CRC scrambled by any one of C-RNTI, CS-RNTI, MCS-C-RNTI, and / or TC-RNTI.
  • DCI format 0_0 may be monitored in the common search space or the UE-specific search space.
  • DCI format 0_1 may be used for PUSCH scheduling in a certain serving cell.
  • DCI format 0_1 refers to information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band portion (BWP: BandWidth Part), channel state information (CSI: Channel State Information) request, and sounding reference.
  • BWP BandWidth Part
  • CSI Channel State Information
  • a signal (SRS: Sounding Reference Signal) request and information about the antenna port may be included.
  • the DCI format 0_1 may include a CRC scrambled by any one of C-RNTI, CS-RNTI, SP-CSI-RNTI, and / or MCS-C-RNTI.
  • DCI format 0_1 may be monitored in the UE-specific search space.
  • DCI format 1_0 may be used for PDSCH scheduling in a serving cell.
  • the DCI format 1_0 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation).
  • the DCI format 1_0 is added with a CRC scrambled by any one of C-RNTI, CS-RNTI, MCS-C-RNTI, P-RNTI, SI-RNTI, RA-RNTI, and / or TC-RNTI. May be.
  • DCI format 1_0 may be monitored in the common search space or the UE-specific search space.
  • the DCI format 1_1 may be used for PDSCH scheduling in a serving cell.
  • the DCI format 1_1 includes information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band portion (BWP), transmission setting instruction (TCI: Transmission Configuration Indication), and information related to antenna ports. Good.
  • the DCI format 1_1 may include a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI. DCI format 1_1 may be monitored in the UE-specific search space.
  • DCI format 2_0 is used to notify the slot format of one or more slots.
  • the slot format is defined as one in which each OFDM symbol in the slot is classified as downlink, flexible, or uplink.
  • the DDDDDDDDDDDDDDFFU is applied to 14 OFDM symbols in the slot in which the slot format 28 is designated.
  • D is a downlink symbol
  • F is a flexible symbol
  • U is an uplink symbol.
  • the DCI format 2_1 is used to notify the terminal device 1 of a physical resource block and an OFDM symbol that may be assumed not to be transmitted. Note that this information may be referred to as a preemption instruction (intermittent transmission instruction).
  • DCI format 2_2 is used for transmitting the transmission power control (TPC: Transmit Power Control) command for PUSCH and PUSCH.
  • TPC Transmit Power Control
  • the DCI format 2_3 is used to transmit a group of TPC commands for transmitting a sounding reference signal (SRS) by one or more terminal devices 1. Also, the SRS request may be transmitted together with the TPC command. Further, in the DCI format 2_3, the SRS request and the TPC command may be defined for the uplink without the PUSCH and the PUCCH, or for the uplink in which the transmission power control of the SRS is not associated with the transmission power control of the PUSCH.
  • SRS sounding reference signal
  • DCI for the downlink is also called downlink grant or downlink assignment.
  • the DCI for the uplink is also referred to as an uplink grant or an uplink assignment.
  • the CRC (Cyclic Redundancy Check) parity bit added to the DCI format transmitted by one PDCCH is C-RNTI (Cell-Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling-Radio Network Temporary Identifier), RA- It is scrambled by RNTI (Random Access-Radio Network Temporary Identity) or Temporary C-RNTI.
  • C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying a terminal device in a cell.
  • the Temporary C-RNTI is an identifier for identifying the terminal device 1 that has transmitted the random access preamble during the contention based random access procedure.
  • C-RNTI terminal device identifier (identification information)
  • the CS-RNTI is used to periodically allocate PDSCH or PUSCH resources.
  • MCS-C-RNTI is used to indicate the use of a given MCS table for grant-based transmission.
  • Temporary C-RNTI (TC-RNTI) is used to control PDSCH transmission or PUSCH transmission in one or more slots.
  • the Temporary C-RNTI is used to schedule the retransmission of the random access message 3 and the transmission of the random access message 4.
  • RA-RNTI random access response identification information
  • the PUCCH is used to transmit uplink control information (Uplink Control Information: UCI) in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3).
  • the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel.
  • the uplink control information may include a scheduling request (SR: Scheduling Request) used for requesting the UL-SCH resource.
  • the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement).
  • HARQ-ACK may indicate HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH).
  • PDSCH Downlink Shared CHannel
  • MAC Medium Access Control
  • SI System Information
  • RAR Random Access Response
  • PUSCH may be used to transmit HARQ-ACK and / or CSI together with uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer or uplink data. It may also be used to send CSI only or HARQ-ACK and CSI only. That is, it may be used to transmit only UCI.
  • UL-SCH Uplink Shared Channel
  • the base station device 3 and the terminal device 1 exchange (transmit / receive) signals in an upper layer (upper layer: higher layer).
  • the base station device 3 and the terminal device 1 send and receive RRC signaling (RRC message: Radio Resource Control message, also called RRC information: Radio Resource Control information) in the radio resource control (RRC: Radio Resource Control) layer.
  • RRC Radio Resource Control
  • the base station device 3 and the terminal device 1 may transmit / receive a MAC control element in a MAC (Medium Access Control) layer.
  • the RRC layer of the terminal device 1 acquires the system information reported from the base station device 3.
  • the RRC signaling, the system information, and / or the MAC control element are also referred to as an upper layer signal (upper layer signalling) or an upper layer parameter.
  • the upper layer here means an upper layer viewed from the physical layer, and thus may include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, and the like.
  • the upper layer may include one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS layer and the like.
  • the meaning of “A is given by the upper layer” or “A is given by the upper layer” means that the upper layer of the terminal device 1 (mainly the RRC layer, the MAC layer, etc.) It may mean that A is received and the received A is given from the upper layer of the terminal device 1 to the physical layer of the terminal device 1.
  • PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements.
  • the RRC signaling transmitted from the base station device 3 may be common signaling to the plurality of terminal devices 1 in the cell.
  • the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device 1. That is, the terminal device specific (UE-specific) information may be transmitted to a certain terminal device 1 by using dedicated signaling.
  • PUSCH may be used for transmission of UE capability (UE Capability) in the uplink.
  • the following downlink physical signals are used in downlink wireless communication.
  • the downlink physical signal is not used for transmitting information output from the upper layer, but is used by the physical layer.
  • SS Synchronization signal
  • RS Reference Signal
  • the synchronization signal may include a primary synchronization signal (PSS: Primary Synchronization Signal) and a secondary synchronization signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS secondary synchronization signal
  • the cell ID may be detected using the PSS and the SSS.
  • the synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and time domain.
  • the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3.
  • the beam may also be called a transmission or reception filter setting, or a spatial domain transmission filter or a spatial domain reception filter.
  • the reference signal is used by the terminal device 1 to perform propagation path compensation on the physical channel.
  • the reference signal may also be used by the terminal device 1 to calculate downlink CSI.
  • the reference signal may be used for fine synchronization (fine synchronization) to the extent that numerology such as radio parameters and subcarrier intervals and window synchronization of FFT can be performed.
  • DMRS Demodulation Reference Signal
  • CSI-RS Channel State Information Reference Signal
  • PTRS Phase Tracking Reference Signal
  • TRS Tracking Reference Signal
  • DMRS is used to demodulate the modulated signal.
  • Two types of reference signals for demodulating PBCH and PDSCH may be defined in DMRS, or both may be referred to as DMRS.
  • the CSI-RS is used for measuring channel state information (CSI: Channel State Information) and beam management, and a transmission method of a periodic or semi-persistent or aperiodic CSI reference signal is applied.
  • Non-zero power (NZP: Non-Zero Power) CSI-RS and transmission power (or reception power) of zero (zero power (ZP: Zero Power) CSI-RS may be defined as CSI-RS.
  • ZP CSI-RS may be defined as CSI-RS resource with zero transmission power or not transmitted.
  • PTRS is for tracking the phase on the time axis in order to guarantee the frequency offset due to phase noise.
  • the TRS is used to guarantee the Doppler shift when moving at a high speed, and the TRS may be used as one setting of the CSI-RS, for example, one-port CSI-RS is used as the TRS. Radio resources may be configured.
  • uplink reference signals are used.
  • DMRS Demodulation Reference Signal
  • PTRS Phase Tracking Reference Signal
  • SRS Sounding Reference Signal
  • DMRS is used to demodulate the modulated signal.
  • Two types of reference signals for demodulating PUCCH and reference signals for demodulating PUSCH may be defined in DMRS, or both may be referred to as DMRS.
  • SRS is used for uplink channel state information (CSI) measurement, channel sounding, and beam management.
  • the PTRS is used to track the phase on the time axis in order to guarantee the frequency offset due to the phase noise.
  • the downlink physical channel and / or the downlink physical signal are collectively referred to as the downlink signal.
  • An uplink physical channel and / or an uplink physical signal are collectively referred to as an uplink signal.
  • the downlink physical channel and / or the uplink physical channel are collectively referred to as a physical channel.
  • the downlink physical signal and / or the uplink physical signal are collectively referred to as a physical signal.
  • BCH, UL-SCH and DL-SCH are transport channels.
  • a channel used in a medium access control (MAC) layer is called a transport channel.
  • the unit of the transport channel used in the MAC layer is also called a transport block (TB: transport block) and / or a MAC PDU (Protocol Data Unit).
  • HARQ Hybrid Automatic Repeat reQuest
  • the transport block is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, transport blocks are mapped to codewords, and an encoding process is performed for each codeword.
  • FIG. 2 is a diagram showing an example of an SS / PBCH block (also referred to as a synchronization signal block, an SS block, an SSB) and an SS burst set (also referred to as a synchronization signal burst set) according to the present embodiment.
  • FIG. 2 shows an example in which two SS / PBCH blocks are included in an SS burst set that is periodically transmitted, and the SS / PBCH block is composed of 4 consecutive OFDM symbols.
  • the SS / PBCH block is a unit block including at least a synchronization signal (PSS, SSS) and / or PBCH. Transmitting the signal / channel included in the SS / PBCH block is expressed as transmitting the SS / PBCH block.
  • the base station device 3 may use an independent downlink transmission beam for each SS / PBCH block. Good.
  • PSS, SSS, and PBCH are time / frequency multiplexed in one SS / PBCH block.
  • the order in which PSS, SSS, and / or PBCH are multiplexed in the time domain may be different from the example shown in FIG.
  • SS burst set may be sent periodically.
  • a cycle to be used for initial access and a cycle set for the connected (Connected or RRC_Connected) terminal device may be defined.
  • the cycle set for the connected (Connected or RRC_Connected) terminal device may be set in the RRC layer.
  • the cycle set for the connected (Connected or RRC_Connected) terminal is the cycle of the radio resources in the time domain that may potentially be transmitted, and whether the base station apparatus 3 actually transmits You may decide.
  • the cycle used for the initial access may be defined in advance in a specification or the like.
  • the SS burst set may be determined based on the system frame number (SFN: System Frame Number). Further, the start position (boundary) of the SS burst set may be determined based on the SFN and the cycle.
  • SFN System Frame Number
  • An SS / PBCH block is assigned an SSB index (may be referred to as SSB / PBCH block index) 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 information of the reference signal included in the detected SS / PBCH block.
  • the same SSB index is assigned to SS / PBCH blocks having the same relative time within each SS burst set in a plurality of SS burst sets.
  • SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL (or have the same downlink transmit beam applied).
  • antenna ports in SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL with respect to average delay, Doppler shift, and spatial correlation.
  • SS / PBCH blocks assigned the same SSB index may be assumed to be QCL with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation.
  • the settings corresponding to one or more SS / PBCH blocks that are QCLs (or may be reference signals) may be referred to as QCL settings.
  • the number of SS / PBCH blocks (which may be referred to as the number of SS blocks or the number of SSBs) is, for example, the number of SS / PBCH blocks in the SS burst or SS burst set, or in the cycle of the SS / PBCH blocks. May be defined. Further, the number of SS / PBCH blocks may indicate the number of beam groups for cell selection in the SS burst, the SS burst set, or the period of the SS / PBCH block. Here, the beam group may be defined as the number of different SS / PBCH blocks or the number of different beams included in the SS burst or the set of SS bursts or in the period of the SS / PBCH block.
  • the reference signals described in this embodiment are downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DM-RSs, CSI-RSs, uplink reference signals, SRSs, and / or uplink DM-. Including RS.
  • the downlink reference signal, the synchronization signal and / or the SS / PBCH block may be referred to as a reference signal.
  • Reference signals used in the downlink include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DM-RSs, CSI-RSs, and the like.
  • the reference signal used in the uplink includes an uplink reference signal, SRS, and / or uplink DM-RS.
  • the reference signal may be used for radio resource measurement (RRM). Further, the reference signal may be used for beam management.
  • RRM radio resource measurement
  • the reference signal may be used for beam management.
  • Beam management includes analog and / or digital beams in a transmitting device (the base station device 3 in the case of downlink and the terminal device 1 in the case of uplink) and a receiving device (the terminal device 1 in the case of downlink).
  • a transmitting device the base station device 3 in the case of downlink and the terminal device 1 in the case of uplink
  • a receiving device the terminal device 1 in the case of downlink
  • the uplink it is the procedure of the base station apparatus 3 and / or the terminal apparatus 1 for matching the directivity of the analog and / or digital beams in the base station apparatus 3 and acquiring the beam gain.
  • the following procedure may be included as a procedure for configuring, setting, or establishing a beam pair link.
  • Beam selection ⁇ Beam refinement ⁇ Beam recovery
  • the beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1.
  • the beam improvement may be a procedure of selecting a beam having a higher gain or changing the beam between the base station device 3 and the terminal device 1 optimally by moving the terminal device 1.
  • the beam recovery may be a procedure of reselecting a beam when the quality of the communication link is deteriorated due to a blockage generated by a blocking object or a person passing in the communication between the base station device 3 and the terminal device 1.
  • Beam management may include beam selection and beam refinement. Beam recovery may include the following procedures. ⁇ Detection of beam failure ⁇ Finding a new beam ⁇ Sending beam recovery request ⁇ Monitoring response to beam recovery request
  • CSI-RS or RSRP Reference Signal Received Power
  • CSI-RS resource index CRI: CSI-RS Resource Index
  • DMRS reference signal
  • the base station device 3 instructs the CRI or SS / PBCH time index when instructing the beam to the terminal device 1, and the terminal device 1 receives based on the instructed CRI or SS / PBCH time index.
  • the terminal device 1 may set and receive the spatial filter based on the instructed CRI or the time index of the SS / PBCH.
  • the terminal device 1 may receive using the assumption of a pseudo co-location (QCL).
  • a signal (antenna port, synchronization signal, reference signal, etc.) and another signal (antenna port, synchronization signal, reference signal, etc.) are “QCL” or “the assumption of QCL is used” means that a signal is Can be interpreted as being associated with another signal.
  • Two antenna ports are said to be QCL if the Long Term Property of the channel carrying a symbol at one antenna port can be inferred from the channel carrying a symbol at the other antenna port.
  • the long-range characteristics of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if the antenna port 1 and the antenna port 2 are QCL with respect to the average delay, it means that the reception timing of the antenna port 2 can be inferred from the reception timing of the antenna port 1.
  • the QCL extended to the space may be newly defined.
  • the arrival angle AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.
  • Angle Spread such as ASA (Angle Spread Arrival) or ZSA (Zenith angle Spread of Arrival)
  • sending angle AoD, ZoD, etc.
  • Angle Spread such as ASD (Angle Spread of Departure) and ZSD ( Zenithangle Spread of Departure)
  • spatial correlation SpatialCorrelation
  • the reception spatial parameter is QCL between the antenna port 1 and the antenna port 2
  • the reception beam reception spatial filter that receives the signal from the antenna port 1 receives the signal from the antenna port 2. It means that the beam can be inferred.
  • QCL type a combination of long-term characteristics that may be considered to be QCL may be defined.
  • the following types may be defined.
  • -Type A Doppler shift, Doppler spread, average delay
  • delay spread-Type B Doppler shift
  • Doppler spread-Type C Average delay
  • Doppler shift-Type D Reception spatial parameter
  • the above-mentioned QCL type sets and / or sets the assumption of QCL of one or two reference signals and PDCCH or PDSCH DMRS at the RRC and / or MAC layer and / or DCI as a transmission configuration indication (TCI). You may instruct.
  • TCI transmission configuration indication
  • the terminal device 1 determines that the PDCCH DMRS
  • the Doppler shift, the Doppler spread, the average delay, the delay spread, the reception spatial parameter and the long-term characteristics of the channel are regarded as the PDCCH DMRS, and the synchronization and the propagation path are received. You may make an estimate.
  • the reference signal (SS / PBCH block in the above example) designated by the TCI is the source reference signal, and the reference is influenced by the long-term characteristic inferred from the long-term characteristic of the channel when the source reference signal is received.
  • the signal (PDCCH DMRS in the above example) may be referred to as the target reference signal.
  • the TCI may have one or more TCI states in RRC and a combination of a source reference signal and a QCL type for each state, and may be instructed to the terminal device 1 by the MAC layer or DCI.
  • subframe Although referred to as a subframe in this embodiment, it may be referred to as a resource unit, a radio frame, a time section, a time interval, or the like.
  • FIG. 3 is a diagram showing an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention.
  • Each of the radio frames is 10 ms long.
  • Each radio frame is composed of 10 subframes and W slots.
  • one slot is composed of X OFDM symbols. That is, the length of one subframe is 1 ms.
  • NCP Normal Cyclic Prefix
  • an uplink slot is defined similarly, and a downlink slot and an uplink slot may be defined separately.
  • the bandwidth of the cell in FIG. 3 may be defined as a part of the bandwidth (BWP: BandWidth Part).
  • the slot may be defined as a transmission time interval (TTI: Transmission Time Interval). Slots may not be defined as TTIs.
  • the TTI may be a transport block transmission period.
  • the signal or physical channel transmitted in each of the slots may be represented by a resource grid.
  • the resource grid is defined by a plurality of subcarriers and a plurality of OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier.
  • the number of subcarriers forming one slot depends on the downlink and uplink bandwidths of the cell.
  • Each of the elements in the resource grid is called a resource element. Resource elements may be identified using subcarrier numbers and OFDM symbol numbers.
  • Reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks are defined as resource blocks.
  • One resource block is defined as 12 consecutive subcarriers in the frequency domain.
  • the reference resource block is common to all subcarriers, and may constitute a resource block at a subcarrier interval of 15 kHz, for example, and may be numbered in ascending order.
  • the subcarrier index 0 in the reference resource block index 0 may be referred to as a reference point A (point A) (may be simply referred to as “reference point”).
  • the common resource block is a resource block numbered in ascending order from 0 in each subcarrier interval setting ⁇ from the reference point A.
  • the resource grid described above is defined by this common resource block.
  • the physical resource blocks are resource blocks numbered in ascending order from 0 included in the band part (BWP) described later, and the physical resource blocks are in ascending order from 0 included in the band part (BWP). It is a numbered resource block.
  • a physical uplink channel is first mapped to a virtual resource block.
  • the virtual resource block is then mapped to the physical resource block.
  • the resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.
  • the subcarrier interval setting ⁇ As mentioned above, NR supports one or more OFDM numerologies.
  • the subcarrier spacing ⁇ f 2 ⁇ ⁇ ⁇ 15 (kHz).
  • slots are counted in ascending order from 0 to N ⁇ ⁇ subframe, ⁇ _ ⁇ slot ⁇ -1 in a subframe, and 0 to N ⁇ ⁇ frame, ⁇ _ ⁇ slot in a frame.
  • ⁇ -1 are counted in ascending order.
  • N ⁇ ⁇ slot ⁇ _ ⁇ symb ⁇ consecutive OFDM symbols in the slot based on the slot settings and the cyclic prefix.
  • N ⁇ ⁇ slot ⁇ _ ⁇ symb ⁇ is 14.
  • the start of slot n ⁇ ⁇ _ ⁇ s ⁇ in a subframe is the start and time of the n ⁇ ⁇ _ ⁇ s ⁇ N ⁇ ⁇ slot ⁇ _ ⁇ symb ⁇ th OFDM symbol in the same subframe. It is aligned.
  • FIG. 4 is a diagram showing the relationship between subframes, slots, and minislots in the time domain. As shown in the figure, three types of time units are defined.
  • the subframe is 1 ms regardless of the subcarrier interval, the number of OFDM symbols included in the slot is 7 or 14, and the slot length varies depending on the subcarrier interval.
  • the subcarrier interval is 15 kHz, 14 OFDM symbols are included in one subframe.
  • the downlink slot may be referred to as PDSCH mapping type A.
  • the uplink slot may be referred to as PUSCH mapping type A.
  • a minislot (may be referred to as a subslot) is a time unit composed of fewer OFDM symbols than the number of OFDM symbols included in the slot.
  • the figure shows an example where the minislot is composed of 2 OFDM symbols.
  • An OFDM symbol in a mini-slot may coincide with the OFDM symbol timing making up the slot.
  • the minimum unit of scheduling may be a slot or a minislot.
  • assigning minislots may be referred to as non-slot based scheduling.
  • scheduling a minislot may be expressed as scheduling a resource in which a relative time position between a reference signal and a start position of data is fixed.
  • the downlink minislot may be referred to as PDSCH mapping type B.
  • the uplink minislot may be referred to as PUSCH mapping type B.
  • FIG. 5 is a diagram showing an example of the slot format.
  • the slot length is 1 ms at a subcarrier interval of 15 kHz is shown as an example.
  • D indicates downlink and U indicates uplink.
  • U indicates uplink.
  • a certain time interval for example, the minimum time interval that must be assigned to one UE in the system
  • It may include one or more of a downlink symbol, a flexible symbol, and an uplink symbol. Note that these ratios may be predetermined as a slot format. Further, it may be defined by the number of downlink OFDM symbols included in the slot or the start position and end position in the slot.
  • scheduling a slot may be expressed as scheduling a resource in which the relative time position between the reference signal and the slot boundary is fixed.
  • the terminal device 1 may receive a downlink signal or a downlink channel with a downlink symbol or a flexible symbol.
  • the terminal device 1 may transmit an uplink signal or a downlink channel with an uplink symbol or a flexible symbol.
  • 5A may also be referred to as a certain time period (for example, a minimum unit of time resources that can be assigned to one UE, a time unit, or the like. Further, a plurality of minimum units of time resources are bundled and referred to as a time unit. 5B), all of them are used for downlink transmission.
  • uplink scheduling is performed via the PDCCH in the first time resource, and the processing delay of the PDCCH and the downlink are performed.
  • the uplink signal is transmitted via the flexible symbol including the switching time from the uplink to the generation of the transmission signal.
  • the uplink signal may be used for transmitting HARQ-ACK and / or CSI, that is, UCI.
  • FIG. 5 (d) is used for transmission of PDCCH and / or PDSCH in the first time resource, and has processing delay, downlink to uplink switching time, and uplink PUSCH and / or via a gap for generation of a transmission signal. Alternatively, it is used for PUCCH transmission.
  • the uplink signal may be used for transmission of uplink data, that is, UL-SCH.
  • FIG. 5 (e) is an example in which all are used for uplink transmission (PUSCH or PUCCH).
  • the downlink part and the uplink part described above may be composed of a plurality of OFDM symbols as in LTE.
  • FIG. 6 is a diagram showing an example of beamforming.
  • a plurality of antenna elements are connected to one transmission unit (TXRU: Transceiver unit) 50, the phase is controlled by the phase shifter 51 for each antenna element, and by transmitting from the antenna element 52, the transmission signal can be transmitted in any direction.
  • the beam can be aimed.
  • TXRU may be defined as an antenna port, and in terminal device 1, only an antenna port may be defined.
  • directivity can be directed in an arbitrary direction, so that the base station device 3 can communicate with the terminal device 1 using a beam having a high gain.
  • BWP Bandwidth part
  • BWP is also referred to as carrier BWP.
  • BWP may be set for each of the downlink and the uplink.
  • BWP is defined as a set of contiguous physical resources selected from a contiguous subset of common resource blocks.
  • the terminal device 1 can set up to four BWPs in which one downlink carrier BWP (DL BWP) is activated at a certain time.
  • DL BWP downlink carrier BWP
  • UL BWP uplink carrier BWP
  • BWP may be set in each serving cell. At this time, the fact that one BWP is set in a certain serving cell may be expressed as the case where no BWP is set. Further, the setting of two or more BWPs may be expressed as the BWP being set.
  • BWP switching for a serving cell is used to activate an inactive (deactivated) BWP and deactivate an active (activated) BWP. To be done.
  • BWP switching for a serving cell is controlled by PDCCH indicating downlink allocation or uplink grant.
  • BWP switching for a serving cell may also be controlled by the BWP inactivity timer, RRC signaling, or by the MAC entity itself at the start of the random access procedure.
  • SpCell PCell or PSCell
  • SCell SpCell
  • one BWP is first active without receiving PDCCH indicating downlink allocation or uplink grant.
  • First active DL BWP (first active DL BWP) and UL BWP (first active UL BWP) may be specified in the RRC message sent from the base station device 3 to the terminal device 1.
  • the active BWP for a certain serving cell is designated by the RRC or PDCCH sent from the base station device 3 to the terminal device 1.
  • the first active DL BWP (first active DL BWP) and the UL BWP (first active UL BWP) may be included in the message 4.
  • the unpaired spectrum TDD band, etc.
  • DL BWP and UL BWP are paired, and BWP switching is common to UL and DL.
  • 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.
  • the MAC entity of the terminal device 1 does not transmit the UL-SCH, does not transmit the RACH, does not monitor the PDCCH, does not transmit the PUCCH, Does not transmit SRS and does not receive DL-SCH. If a serving cell is deactivated, no active BWP may be present (eg, active BWP is deactivated).
  • a BWP information element (IE) included in the RRC message (system information to be broadcast or information sent in the dedicated RRC message) is used to set the BWP.
  • the RRC message transmitted from the base station device 3 is received by the terminal device 1.
  • the network (such as the base station device 3) should have at least one downlink BWP and one (if the serving cell is configured for uplink) or two (supplementary uplink in the Appendix). Is set), at least an initial BWP (initial BWP) including the uplink BWP (for example, is used) is set for the terminal device 1. Further, the network may configure additional uplink BWP or downlink BWP for a serving cell.
  • the BWP setting is divided into an uplink parameter and a downlink parameter.
  • the BWP setting is divided into a common parameter and a dedicated parameter.
  • Common parameters (such as BWP uplink common IE and BWP downlink common IE) are cell-specific.
  • the common parameters of the initial BWP of the primary cell are also provided in the system information.
  • the network provides common parameters on dedicated signals.
  • the BWP is identified by the BWP ID.
  • the initial BWP has a BWP ID of 0.
  • BWP IDs of other BWPs take values from 1 to 4.
  • the initial DL BWP (initial active DL BWP, initial active DL BWP) is the control resource set (CORESET) for the type 0 PDCCH common search space. It may be defined by the position and number of consecutive PRBs, subcarrier spacing, and cyclic prefix for PDCCH reception in. The position of the consecutive PRBs starts from the PRB with the smallest index and ends with the PRB with the largest index among the PRBs of the control resource set for the type 0 PDCCH common search space.
  • the initial DL BWP may be indicated by the upper layer parameter initialDownlinkBWP.
  • the upper layer parameter initialDownlinkBWP may be included in SIB1 (systemInformationBlockType1, ServingCellConfigCommonSIB) or ServingCellCongfigCommon.
  • SIB1 systemInformationBlockType1, ServingCellConfigCommonSIB
  • ServingCellCongfigCommon The information element ServingCellCongfigureCommon SIB is used in SIB1 to set the cell-specific parameter of the serving cell for the terminal device 1.
  • the size of the initial DL BWP is the number of resource blocks of the control resource set (CORESET # 0) for the type 0 PDCCH common search space. It may be.
  • the size of the initial DL BWP may be given by the locationAndBandwidth included in the upper layer parameter initialDownlinkBWP.
  • the upper layer parameter locationAndBandwidth may indicate the position and bandwidth in the frequency domain of the initial DL BWP.
  • multiple DL BWPs may be set for the terminal device 1. Then, of the DL BWPs set for the terminal device 1, the default DL BWP can be set by the parameter defaultDownlinkBWP-Id of the upper layer. If the upper layer parameter defaultDownlinkBWP-Id is not provided to the terminal device 1, the default DL BWP is the initial DL BWP.
  • An initial UL BWP may be provided to the terminal device 1 by SIB1 (systemInformationBlockType1) or initialUplinkBWP.
  • the information element initialUplinkBWP is used to set the initial UL BWP.
  • the terminal device 1 may be set (provided) with an initial UL BWP (initial active UL BWP) by the parameter initialUplinkBWP of the upper layer.
  • a supplementary uplink carrier (supplementary UL carrier) is set for the terminal device 1
  • the terminal device 1 uses the initialUplinkBWP included in the parameter supplementaryUplink of the upper layer to set the initial UL on the supplementary uplink carrier.
  • BWP may be set.
  • Control resource set (CORESET) in this embodiment will be described below.
  • Control resource set is a time and frequency resource for searching downlink control information.
  • the setting information of CORESET includes the identifier of CORESET (ControlResourceSetId, CORESET-ID) and information for specifying the frequency resource of CORESET.
  • the information element ControlResourceSetId (identifier of CORESET) is used to specify the control resource set in a certain serving cell.
  • the CORESET identifier is used between BWPs in a serving cell.
  • the CORESET identifier is unique between BWPs in the serving cell.
  • the number of CORESETs for each BWP is limited to 3, including the initial CORESET. In a certain serving cell, the value of the identifier of CORESET takes a value from 0 to 11.
  • CORESET # 0 The control resource set specified by the CORESET identifier 0 (ControlResourceSetId 0) is called CORESET # 0.
  • CORESET # 0 may be set by pdchch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellCongfigCommon. That is, the setting information of CORESET # 0 may be pdcch-ConfigSIB1 included in the MIB or PDCCH-ConfigCommon included in the ServingCellCongfigCommon.
  • the setting information of CORESET # 0 may be set by controlResourceSetZero included in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon.
  • the information element controlResourceSetZero is used to indicate CORESET # 0 (common CORESET) of the initial DL BWP.
  • 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 CORESET setting information pdcch-ConfigSIB1 for CORESET # 0 the CORESET identifier, the CORESET frequency resource (for example, the number of consecutive resource blocks), and the time resource (the number of consecutive symbols) are explicitly specified.
  • the frequency resource (for example, the number of consecutive resource blocks) and the time resource (the number of consecutive symbols) of CORESET with respect to CORESET # 0 are implicitly indicated by the information included in pdcch-ConfigSIB1. Can be specified.
  • the information element PDCCH-ConfigCommon is used to set cell-specific PDCCH parameters provided in the SIB.
  • PDCCH-ConfigCommon may be provided at the time of handover and addition of PSCell and / or SCell.
  • the setting information of CORESET # 0 is included in the setting of the initial BWP. That is, the setting information of CORESET # 0 does not need to be included in the setting of BWP other than the initial BWP.
  • the controlResourceSetZero corresponds to 4 bits (eg, 4 bits of MSB and 4 bits of most significant bit) of pdchch-ConfigSIB1.
  • CORESET # 0 is a control resource set for the type 0 PDCCH common search space.
  • the setting information of the additional common CORESET may be set by the commonControlResourceSet included in the PDCCH-ConfigCommon.
  • the additional common CORESET configuration information may be used to specify additional common CORESET for system information and / or paging procedures.
  • the setting information of the additional common CORESET may be used to specify the additional common CORESET used in the random access procedure.
  • the setting information of the additional common CORESET may be included in the setting of each BWP.
  • the identifier of CORESET shown in commonControlResourceSet takes a value other than 0.
  • the common CORESET may be CORESET used in the random access procedure (for example, additional common CORESET). Further, in the present embodiment, the common CORESET may include CORESET # 0 and / or CORESET set by the additional common CORESET setting information. That is, common CORESET may include CORESET # 0 and / or additional common CORESET. CORESET # 0 may be referred to as common CORESET # 0.
  • the terminal device 1 and the BWP other than the BWP in which the common CORESET is set may also refer to (acquire) the setting information of the common CORESET.
  • the setting information of one or more CORESETs may be set by PDCCH-Config.
  • the information element PDCCH-Config is used to set UE-specific PDCCH parameters (eg, CORSET, search space, etc.) for a certain BWP.
  • PDCCH-Config may be included in the settings of each BWP.
  • the common RESET setting information indicated by MIB is pdcch-ConfigSIB1
  • the common RESET setting information indicated by PDCCH-ConfigCommon is controlResourceSetZero
  • the additional common COREset indicated by PDCCH-ConfigCommon is additional common RESET.
  • the setting information of the common CORESET) is commonControlResourceSet.
  • the setting information of one or more CORESETs (UE-specifically configured Control Resource Sets, UE-specific CORESET) indicated by PDCCH-Config is controlResourceSetToAddModList.
  • a search space is defined to search for PDCCH candidates (PDCCH candidates).
  • the searchSpaceType included in the search space setting information indicates whether the search space is a common search space (Common Search Space, CSS) or a UE-specific search space (UE-specific Search Space, USS).
  • the UE-specific search space is derived at least from the value of C-RNTI set by the terminal device 1. That is, the UE-specific search space is individually derived for each terminal device 1.
  • the common search space is a common search space among a plurality of terminal devices 1, and is composed of CCEs (Control Channel Elements) with a predetermined index.
  • the CCE is composed of a plurality of resource elements.
  • the search space setting information includes information on the DCI format monitored in the search space.
  • the search space setting information includes the CORESET identifier specified by the CORESET setting information.
  • the CORESET specified by the CORESET identifier included in the search space setting information is associated with the search space.
  • CORESET associated with the search space is CORESET specified by the identifier of CORESET included in the search space.
  • the DCI format indicated by the setting information of the search space is monitored by the associated CORESET.
  • Each search space is associated with one CORESET.
  • the search space setting information for the random access procedure may be set by ra-SearchSpace. That is, the DCI format to which the CRC scrambled by RA-RNTI or TC-RNTI is added in CORESET associated with the ra-Search Space is monitored.
  • 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 BWP (additional BWP) other than the initial DLBWP.
  • BWP other than the initial DL BWP refers to the setting information of CORESET # 0 (refer, acquire, etc.)
  • CORESET # 0 and the SS block are included in the additional BWP in the frequency domain, and It may be necessary to at least satisfy using the same subcarrier spacing.
  • the bandwidth of the initial DL BWP and the SS block are set in the frequency domain. It may be necessary to at least meet the requirements of being included in the additional BWP and using the same subcarrier spacing.
  • the search space for example, ra-SearchSpace
  • the additional BWP refers to the setting information of CORESET # 0 by indicating the identifier 0 of CORESET # 0 (refer, acquire, etc.). be able to.
  • CORESET # 0 is set only for the initial DL BWP, but the terminal device 1 operating with another BWP (additional BWP) refers to the setting information of CORESET # 0.
  • additional BWP refers to the setting information of CORESET # 0.
  • the terminal device 1 does not have to expect that the additional DL BWP refers to the setting information of CORESET # 0. That is, in this case, the base station apparatus 3 does not need to set the terminal apparatus 1 so that the additional DL BWP refers to the setting information of CORESET # 0.
  • the initial DL BWP may be a size N size BWP, 0 initial DL BWP.
  • a (additional) DL BWP refers to (refers, acquires, etc.) the setting information of the CORESET of another BWP, the CORESET (or the bandwidth of the BWP) and / or the BWP is included in the frequency domain ( It may be necessary to at least satisfy that the (associated) SS block is included in the additional BWP and uses the same subcarrier spacing.
  • the terminal device 1 does not have to expect that the additional DL BWP refers to the setting information of CORESET set for the BWP.
  • the terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs arranged in each active serving cell configured to monitor the PDCCH.
  • the set of PDCCH candidates corresponds to one or more search space sets. Monitoring refers to decoding each PDCCH candidate depending on the DCI format or formats being monitored.
  • a set of PDCCH candidates monitored by the terminal device 1 is defined by a PDCCH search space set).
  • One search space set is a common search space set or a UE-specific search space set. In the above, the search space set is called a search space, the common search space set is called a common search space, and the UE-specific search space set is called a UE-specific search space.
  • the terminal device 1 monitors PDCCH candidates with one or more of the following search space sets.
  • This search space set is a search space SIB1 (searchSpaceSIB1) indicated by pdcch-ConfigSIB1 indicated by MIB or PDCCH-ConfigCommon which is an upper layer parameter. ) Or search space zero (searchSpaceZero) included in PDCCH-ConfigCommon. This search space is for monitoring the SI-RNRI scrambled CRC DCI format in the primary cell.
  • searchSpaceOtherSystemInformation This search space set is set by the search space (searchSpaceOtherSystemInformation) indicated by PDCCH-ConfigCommon, which is a parameter of the upper layer.
  • This search space is for monitoring the SI-RNRI scrambled CRC DCI format in the primary cell.
  • -A Type1-PDCCH common search space set This search space set is a search space (ra-SearchSpace) for a random access procedure indicated by PDCCH-ConfigCommon, which is an upper layer parameter. Set by. This search space is for monitoring the DCI format of the CRC scrambled with RA-RNRI or TC-RNTI in the primary cell.
  • the Type 1 PDCCH common search space set is a search space set for a random access procedure.
  • -A Type2-PDCCH common search space set This search space set is set by a search space (pagingSearchSpace) for a paging procedure indicated by PDCCH-ConfigCommon, which is an upper layer parameter. It This search space is for monitoring the DCI format of the P-RNTI scrambled CRC in the primary cell.
  • -A Type3-PDCCH common search space set This search space set is set by the search space (SearchSpace) whose common search space type is PDCCH-Config, which is an upper layer parameter.
  • This search space is for monitoring the DCI format of the CRC scrambled with INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI.
  • INT-RNTI DCI format of C-RNTI
  • CS-RNTI s
  • MSC-C-RNTI MSC-C-RNTI
  • -UE-specific search space set In this search space set, the search space type indicated by PDCCH-Config, which is an upper layer parameter, is set by the UE-specific search space (SearchSpace). .
  • This search space is for monitoring the DCI format of the C-RNTI, CS-RNTI (s), or MSC-C-RNTI scrambled CRC.
  • the terminal device 1 If the terminal device 1 is provided with one or more search space sets by the corresponding upper layer parameters (searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, etc.), the terminal device 1 will receive C-RNTI or When CS-RNTI is provided, the terminal device 1 monitors PDCCH candidates for DCI format0_0 and DCI format1_0 having C-RNTI or CS-RNTI in the one or more search space sets. May be.
  • searchSpaceZero searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, etc.
  • the BWP setting information is divided into DL BWP setting information and UL BWP setting information.
  • the BWP setting information includes an information element bwp-Id (BWP identifier).
  • the BWP identifier included in the DL BWP setting information is used to identify (reference) the DL BWP in a certain serving cell.
  • the BWP identifier included in the UL BWP setting information is used to identify (reference) the UL BWP in a certain serving cell.
  • the BWP identifier is assigned to each of DL BWP and UL BWP. For example, the identifier of the BWP corresponding to the DL BWP may be referred to as the DL BWP index.
  • the identifier of the BWP corresponding to the UL BWP may be referred to as the UL BWP index (ULBWP index).
  • the initial DL BWP is referenced by the DL BWP identifier 0.
  • the initial UL BWP is referenced by the UL BWP identifier 0.
  • maxNofBWPs is the maximum number of BWPs per serving cell and is 4.
  • the value of the other BWP identifier takes a value from 1 to 4.
  • the setting information of the other upper layer is associated with a specific BWP by using the BWP identifier. Having DL BWP and UL BWP have the same BWP identifier may mean that DL BWP and UL BWP are paired.
  • the terminal device 1 may be configured with one primary cell and up to 15 secondary cells.
  • FIG. 14 is a flowchart showing an example of a random access procedure of the MAC entity according to this embodiment.
  • S1001 is a procedure related to the start of a random access procedure (random access procedure initialization).
  • the random access procedure is initiated by a PDCCH order, a MAC entity itself, a beam failure notification from a lower layer, RRC, or the like.
  • the random access procedure in SCell is started only by the PDCCH order including the ra-PreambleIndex that is not set to 0b000000.
  • the terminal device 1 receives the random access setting information via the upper layer before starting the random access procedure (initiate).
  • the random access setting information may include one or more elements of the following information or information for determining / setting the following information.
  • Prach-ConfigIndex a set of one or more time / frequency resources (also called random access channel occasions, PRACH occasions, RACH occasions) available for transmission of random access preambles, preambleReceivedTargetPower : Initial power of preamble (may be target received power)
  • Rsrp-Threshold SSB Reference signal received power (RSRP) threshold for selection of SS / PBCH blocks (which may be associated random access preambles and / or PRACH opportunities)
  • rsrp-Threshold CSI-RS CSI-RS Reference signal received power (RSRP) threshold for selection of (which may be associated random access preamble and / or PRACH opportunity)
  • rsrp-Threshold SSB-SUL NUL (Norm
  • Power ControlOffset rsrp-Threshold SSB and rsrp-Threshold CSI-RS when a random access procedure is started for beam failure recovery.
  • Power RampingStep power ramping step (power ramping factor). Indicates the step of the transmission power ramped up based on the preamble transmission counter PREAMBLE_TRANSMISSION_COUNTER.
  • Ra-PreambleIndex Available one or more random access preambles or one or more available in the plurality of random access preamble groups.
  • Random access preamble ra-ssb-OcclusionMaskIndex information for the MAC entity to determine the PRACH opportunity assigned to the SS / PBCH block sending the random access preamble ra-OccasionList: the MAC entity sends the random access preamble Information for determining PRACH opportunities assigned to good CSI-RSs • premTrans ax: maximum number of preamble transmissions • ssb-perRACH-OcclusionAndCB-PreamblesPerSSB (SpCell only): indicates the number of SS / PBCH blocks mapped to each PRACH opportunity and the number of random access preambles mapped to each SS / PBCH block.
  • ra-ResponseWindow Time window for monitoring random access response (SpCell only)
  • ra-ContentionResolutionTimer Contention Resolution timer timer numberOfRA-PreamblesGroupA: Random for each SS / PBCH block Number of random access preambles in ax preamble group A / PR EAMBLE_TRANSMISSION_COUNTER: preamble transmission counter
  • DELTA_PREAMBLE power offset value based on random access preamble format
  • PREAMBLE_POWER_RAMPING_COUNTER preamble power ramping counter
  • PREAMBLE_RECEIVED_TARGET_POWER initial random access. The initial transmit power for random access preamble transmission is shown. • PREAMBLE_BACKOFF: Used to adjust the timing of random access preamble transmission.
  • the MAC entity When a random access procedure is started in a serving cell, the MAC entity refreshes the Msg3 buffer, sets the state variable PREAMBLE_TRANSMISSION_COUNTER to 1, sets the state variable PREAMBLE_POWER_RAMPING_COUNTER to 1 and sets the state variable PREAMBLE_BACKOFF to 0 ms. If the carrier used for the random access procedure is explicitly notified, the MAC entity selects the notified carrier to perform the random access procedure and sets the state variable PCMAX to the maximum transmission power value of the notified carrier. set.
  • the SUL carrier is set for the serving cell, and the RSRP of the downlink path loss reference is smaller than rsrp-Threshold SSB-SUL. Then, the SUL carrier is selected to perform the random access procedure, and the state variable PCMAX is set to the maximum transmission power value of the SUL carrier. Otherwise, the MAC entity selects the NUL carrier to perform the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the NUL carrier.
  • S1002 is a random access resource selection procedure.
  • a procedure for selecting a random access resource (including a time / frequency resource and / or a preamble index) in the MAC layer of the terminal device 1 will be described.
  • the terminal device 1 sets a value for the preamble index (may be referred to as PREAMBLE_INDEX) of the random access preamble to be transmitted by the following procedure.
  • the terminal device 1 starts the random access procedure by (1) notification of beam failure from the lower layer, and (2) SS / PBCH block (also referred to as SSB) or CSI-RS with RRC parameters. Random access resources (which may be PRACH opportunities) for non-contention based random access for associated beam failure recovery requests are provided, and (3) one or more SS / PBCH blocks or CSIs. -When RSRP of RS exceeds a predetermined threshold, select the SS / PBCH block or CSI-RS for which RSRP exceeds the predetermined threshold.
  • the MAC entity shall identify the ra-PreambleIndex associated with the selected SS / PBCH block with the preamble index (PREAMBLE_INDEX). ) May be set. Otherwise, the MAC entity sets the preamble index to the ra-PreambleIndex associated with the selected SS / PBCH block or CSI-RS.
  • the terminal device 1 is provided with (1) ra-PreambleIndex by PDCCH or RRC, (2) the value of the ra-PreambleIndex is not a value (for example, 0b000000) indicating the contention-based random access procedure, and (3) RRC.
  • 0bxxxxxxx means a bit string arranged in a 6-bit information field.
  • (1) random access resources for non-contention-based random access associated with the SS / PBCH block are provided from the RRC, and (2) RSRP is predetermined among the associated SS / PBCH blocks. If one or more SS / PBCH blocks that exceed the threshold of are available, RSRP selects one of the SS / PBCH blocks that exceeds the predetermined threshold and selects the selected SS / PBCH block. Set the associated ra-PreambleIndex to the preamble index.
  • (1) CSI-RS is associated with the random access resource for non-contention based random access by RRC, and (2) RSRP of the associated CSI-RS exceeds a predetermined threshold value.
  • RSRP selects one of the CSI-RSs exceeding the predetermined threshold and preambles the ra-PreambleIndex associated with the selected CSI-RS. Set to index.
  • the terminal device 1 performs the contention-based random access procedure when none of the above conditions is satisfied.
  • the terminal device 1 selects the SS / PBCH block having the RSRP of the SS / PBCH block exceeding the set threshold value, and selects the preamble group.
  • the terminal device 1 randomly selects one or more random access preambles associated with the selected SS / PBCH block and the selected preamble group.
  • the ra-PreambleIndex is selected for, and the selected ra-PreambleIndex is set as the preamble index.
  • the MAC entity selects one SS / PBCH block and the association between the PRACH opportunity and the SS / PBCH block is set, the MAC entity selects the next PRACH opportunity associated with the selected SS / PBCH block. May determine available PRACH opportunities. However, when the terminal device 1 selects one CSI-RS and the association (association) between the PRACH opportunity and the CSI-RS is set, the terminal device 1 selects the next PRACH opportunity associated with the selected CSI-RS. May determine available PRACH opportunities.
  • Available PRACH opportunities may also be identified based on mask index information, SSB index information, resource settings configured in RRC parameters, and / or selected reference signals (SS / PBCH blocks or CSI-RS). Good.
  • the resource setting set by the RRC parameter includes a resource setting for each SS / PBCH block and / or a resource setting for each CSI-RS.
  • the base station device 3 may transmit the resource setting for each SS / PBCH block and / or the resource setting for each CSI-RS to the terminal device 1 by an RRC message.
  • the terminal device 1 receives the resource setting for each SS / PBCH block and / or the resource setting for each CSI-RS by the RRC message from the base station device 3.
  • the base station device 3 may transmit the mask index information and / or the SSB index information to the terminal device 1.
  • the terminal device 1 acquires the mask index information and / or the SSB index information from the base station device 3.
  • the terminal device 1 may select the reference signal (SS / PBCH block or CSI-RS) based on a certain condition.
  • the terminal device 1 determines the next available PRACH opportunity based on the mask index information, the SSB index information, the resource setting set by the RRC parameter, and the selected reference signal (SS / PBCH block or CSI-RS). May be specified.
  • the MAC entity of the terminal device 1 may instruct the physical layer to transmit the random access preamble using the selected PRACH opportunity.
  • the mask index information is information indicating the PRACH opportunity index that can be used for transmitting the random access preamble.
  • the mask index information may be information indicating a part of PRACH opportunities of a group of one or a plurality of PRACH opportunities defined by prac-ConfigurationIndex. Further, the mask index information may be information indicating some PRACH opportunities in the group of PRACH opportunities to which the specific SSB index specified by the SSB index information is mapped.
  • the SSB index information is information indicating the SSB index corresponding to one of one or more SS / PBCH blocks transmitted by the base station device 3.
  • the terminal device 1 that has received the message 0 identifies the group of PRACH opportunities to which the SSB index indicated by the SSB index information is mapped.
  • the SSB index mapped to each PRACH opportunity is determined by the PRACH configuration index, the upper layer parameter SB-perRACH-Occlusion, and the upper layer parameter cb-preamblePerSSB.
  • S1003 is a procedure relating to transmission of a random access preamble (random access preamble transmission).
  • the MAC entity shall: (1) state variable PREAMBLE_TRANSMISSION_COUNTER is greater than 1; Increment the state variable PREAMBLE_POWER_RAMPING_COUNTER by one if the assigned SS / PBCH block has not changed.
  • the MAC entity selects the value of DELTA_PREAMBLE and sets the state variable PREAMBLE_RECEIVED_TARGET_POWER to a predetermined value.
  • the predetermined value is calculated by preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER-1) * powerRampingStep.
  • the MAC entity calculates the RA-RNTI associated with the PRACH opportunity to which the random access preamble is sent, except for non-contention based random access preamble due to beam failure recovery request.
  • s_id is an index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13.
  • t_id is an index of the first slot of PRACH in the system frame, and takes a value from 0 to 79.
  • f_id is a PRACH index in the frequency domain and takes values from 0 to 7.
  • ul_carrier_id is an uplink carrier used for Msg1 transmission.
  • the ul_carrier_id for the NUL carrier is 0 and the ul_carrier_id for the SUL carrier is 1.
  • the MAC entity instructs the physical layer to transmit the random access preamble using the selected PRACH.
  • S1004 is a procedure regarding reception of a random access response (random access response reception). Once the random access preamble is sent, the MAC entity will perform the following actions regardless of possible occurrence of measurement gaps.
  • the random access response may be a MAC PDU for the random access response.
  • a MAC PDU (random access response MAC PDU) consists of one or more MAC subPDUs and possible padding. Each MAC subPDU is composed of any of the following.
  • MAC sub-header (subheader) containing only Backoff Indicator -MAC subheader (subheader) indicating only RAPID MAC sub-header (subheader) indicating RAPID and MAC RAR (MAC payload for Random Access Response)
  • a MAC subPDU including only Backoff Indicator is placed at the head of the MAC PDU.
  • the padding is placed at 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 placed anywhere between the MAC subPDU including only the Backoff Indicator and the padding.
  • the RAR message may be a MAC RAR.
  • the RAR message may be a random access response.
  • the MAC entity sends a non-contention based random access preamble for beam failure recovery request
  • the MAC entity sends a random access response window (ra-ResponseWindow) at the first PDCCH opportunity from the end of the random access preamble transmission.
  • ra-ResponseWindow a random access response window
  • the MAC entity monitors the SpCell's PDCCH identified by the C-RNTI for response to the beam failure recovery request.
  • the period (window size) of the random access response window is given by ra-ResponseWindow included in the upper layer parameter BeamFailureRecoveryConfig.
  • the MAC entity starts a random access response window (ra-ResponseWindow) at the first PDCCH opportunity from the end of random access preamble transmission.
  • the period (window size) of the random access response window is given by ra-ResponseWindow included in the upper layer parameter RACH-ConfigCommon.
  • the MAC entity monitors the PDCCH of the SpCell identified by RA-RNTI for random access response while the random access response window is running.
  • the information element BeamFailureRecoveryConfig is used for setting the RACH resource and the candidate beam for the beam failure recovery for the terminal device 1 when the beam failure is detected.
  • the information element RACH-ConfigCommon is used to specify cell-specific random access parameters.
  • the MAC entity receives (1) an acknowledgment of the PDCCH transmission from the lower layer, (2) the PDCCH transmission is scrambled by the C-RNTI, and (3) the MAC entity is on a non-contention basis for beam failure recovery request.
  • the random access procedure may be considered to have been successfully completed if the random access preamble is sent.
  • the MAC entity performs the following operations when (1) the downlink assignment is received on the PDCCH of RA-RNTI and (2) the received transport block is successfully decoded.
  • the MAC entity sets PREAMBLE_BACKOFF to the value of the BI field included in the MAC subPDU when the random access response includes the MAC subPDU including the BackoffIndicator. Otherwise, the MAC entity sets PREAMBLE_BACKOFF to 0ms.
  • the MAC entity may consider that the random access response has been successfully received when it includes the MAC subPDU including the random access preamble identifier corresponding to the PREAMBLE_INDEX to which the random access response is transmitted.
  • the MAC entity If (1) the random access response is considered to be successfully received, and (2) the random access response includes a MAC subPDU containing only RAPID, the MAC entity considers the random access procedure to be completed successfully, and , Reception of an acknowledgment (acknowledgement) to an SI request (symstem information request) is shown in the upper layer.
  • the MAC entity applies the following operation A to the serving cell in which the random access preamble is transmitted.
  • the MAC entity processes the received transmission timing adjustment information (Timing Advance Command) and indicates to the lower layer the amount of preambleReceivedTargetPower and power ramping applied to the latest random access preamble transmission.
  • the transmission timing adjustment information is used to adjust the deviation of the transmission timing between the terminal device 1 and the base station device 3 from the received random access preamble.
  • the MAC entity may ignore the received UL grant. Otherwise, the MAC entity processes the received UL grant value and indicates it to lower layers.
  • the MAC entity may consider the random access procedure to have completed successfully.
  • the MAC entity sets TEMPORARY_C-RNTI to the value of the Temporary C-RNTI field included in the received random access response. Then, if the random access response is successfully received for the first time in this random access procedure, the MAC entity, if not transmitting to the CCCH logical channel (common control channel logical channel), Notify a predetermined entity (Multiplexing and assembly entity) that the next uplink transmission includes the C-RNTI MAC CE, and acquire and obtain a MAC PDU for transmission from the predetermined entity (Multiplexing and assembly entity) The MAC PDU is stored in the Msg3 buffer. When transmission is performed on the CCCH logical channel, the MAC entity acquires a MAC PDU for transmission from a predetermined entity (Multiplexing and assembly entity) and stores the acquired MAC PDU in the Msg3 buffer.
  • CCCH logical channel common control channel logical channel
  • the MAC entity considers that the random access response has not been successfully received, and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by one.
  • the MAC entity indicates a random access problem to the upper layer when the value of the preamble transmission counter reaches a predetermined value (maximum number of preamble transmissions + 1) and the random access preamble is transmitted in SpCell. Then, if the random access procedure is initiated for the SI request, the MAC entity considers that the random access procedure has not been completed successfully.
  • the MAC entity determines that the random access procedure has not been completed successfully. I reckon.
  • the condition (3) is that the period of the random access response window set in RACH-ConfigCommon has been expired and the random access response including the random access preamble identifier matching the transmitted preamble index has not been received. That's what it means.
  • the condition (4) is that the period of the random access response window set by BeamFailureRecoveryConfig has expired and the PDCCH scrambled by the C-RNTI has not been received.
  • the MAC entity shall randomly select between 0 and PREAMBLE_BACKOFF if the random access preamble was selected by the MAC itself from the range of contention based random access preambles in the random access procedure. A backoff time is selected, the next random access preamble transmission is delayed at the selected backoff time, and S1002 is executed. If the random access procedure is not completed, the MAC entity performs S1002 if the random access preamble has not been selected by the MAC itself from the contention based random access preamble range in the random access procedure.
  • the MAC entity may stop the random access response window upon successful receipt of a random access response containing a random access preamble identifier that matches the transmitted preamble index.
  • the terminal device 1 transmits the message 3 by PUSCH based on the UL grant.
  • S1005 is a procedure related to collision resolution (Contention Resolution).
  • the MAC entity starts a collision resolution timer and restarts the collision resolution timer at each HARQ retransmission.
  • the MAC entity monitors the PDCCH while the collision resolution timer is running, regardless of the possible occurrence of measurement gaps.
  • the MAC entity is provided if at least one of the following conditions (5) to (7) is satisfied. , The contention resolution is considered successful, the contention resolution timer is stopped, the TEMPORARY_C-RNTI is discarded, and the random access procedure is considered successfully completed.
  • Condition (5) is that the random access procedure is initiated by the MAC sublayer itself or the RRC sublayer, the PDCCH transmission is scrambled by the C-RNTI, and the PDCCH transmission includes an uplink grant for initial transmission.
  • Condition (6) is that the random access procedure is initiated by the PDCCH order and the PDCCH transmission is scrambled by the C-RNTI.
  • Condition (7) is that the random access procedure is initiated for beam failure recovery and the PDCCH transmission is scrambled by the C-RNTI.
  • CCCH SDU (UE contention resolution identity) is included in Msg3 and the PDCCH transmission is scrambled by TEMPORARY_C-RNTI
  • the MAC entity will stop the collision resolution timer if the MAC PDU is successfully decoded. .. Then, if the successfully decoded MAC PDU contains a UE contention resolution identity MAC CE, and the UE collision resolution identity in MAC CE matches the CCCH SDU sent in Msg3, The MAC entity regards the collision resolution as successful and terminates the disassembly and demultiplexing of the MAC PDU. Then, if the random access procedure is initiated for the SI request, the MAC entity indicates to the higher layers the receipt of an acknowledgment for the SI request.
  • UE contention resolution identity UE contention resolution identity
  • the MAC entity sets C-RNTI to the value of TEMPORARY_C-RNTI. Subsequently, the MAC entity discards TEMPORARY_C-RNTI and considers the random access procedure to be successfully completed.
  • the MAC entity discards TEMPORARY_C-RNTI when the UE collision resolution identity in the MAC CE does not match the CCCH SDU transmitted in Msg3, considers that the collision resolution is not successful, and decodes the successfully decoded MAC PDU. Discard.
  • the MAC entity discards TEMPORARY_C-RNTI when the conflict resolution timer expires and considers that conflict resolution is not successful.
  • the MAC entity flushes the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by 1 when it is considered that the conflict resolution is not successful.
  • PREAMBLE_TRANSMISSION_COUNTER the preamble transmission counter
  • the MAC entity indicates a random access problem to the upper layer. Then, if the random access procedure is initiated for the SI request, the MAC entity considers that the random access procedure has not been completed successfully.
  • the MAC entity selects a random backoff time between 0 and PREAMBLE_BACKOFF, delays the next random access preamble transmission at the selected backoff time, and executes S1002.
  • the MAC entity Upon completion of the random access procedure, the MAC entity discards the explicitly signaled non-contention based random access resource for non-contention based random access procedures other than the contention based random access procedure for beam failure recovery request. Then, the HARQ buffer used for transmitting the MAC PDU in the Msg3 buffer is flushed.
  • Random access procedures are classified into two procedures: contention-based (CB: Contention Based) and non-contention-based (non-CB) (may be referred to as CF: Contention Free).
  • CB Contention Based
  • non-CB non-contention-based
  • CF Contention Free
  • the random access procedure is applicable to (i) transmission of random access preamble (message 1, Msg1) on PRACH, (ii) reception of random access response (RAR) message (message 2, Msg2) with PDCCH / PDSCH, and applicable
  • RAR random access response
  • message 3 PUSCH Msg3 PUSCH
  • PDSCH reception for collision resolution may be included.
  • the contention based random access procedure is initiated by PDCCH order, MAC entity, notification of beam failure from lower layers, RRC, etc.
  • the beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1
  • the MAC entity of the terminal device 1 starts the random access procedure.
  • the procedure of determining whether a certain condition is satisfied and starting the random access procedure is called a beam failure recovery procedure. May be.
  • This random access procedure is a random access procedure for beam failure recovery request.
  • the random access procedure initiated by the MAC entity includes the random access procedure initiated by the scheduling request procedure.
  • the random access procedure for beam failure recovery request may or may not be considered a random access procedure initiated by a MAC entity. Since the random access procedure for beam failure recovery request and the random access procedure started by the scheduling request procedure may perform different procedures, the random access procedure for beam failure recovery request and the scheduling request procedure are distinguished. You may do it.
  • the random access procedure for the beam failure recovery request and the scheduling request procedure may be a random access procedure initiated by a MAC entity.
  • a random access procedure initiated by a scheduling request procedure is referred to as a MAC entity initiated random access procedure
  • a random access procedure for a beam failure recovery request is a random access by beam failure notification from a lower layer. You may call it a procedure.
  • the start of the random access procedure when receiving the beam failure notification from the lower layer may mean the start of the random access procedure for the beam failure recovery request.
  • the terminal device 1 When the terminal device 1 is in an initial access from a state where it is not connected (communicated) with the base station device 3, and / or is connected to the base station device 3, it is possible to transmit uplink data or transmission to the terminal device 1.
  • a contention-based random access procedure is performed at the time of scheduling request when possible sidelink data occurs.
  • the use of contention-based random access is not limited to these.
  • the occurrence of uplink data that can be transmitted to the terminal device 1 may include that a buffer status report corresponding to the uplink data that can be transmitted is triggered.
  • the occurrence of the transmittable uplink data in the terminal device 1 may include the pending scheduling request triggered based on the occurrence of the transmittable uplink data.
  • the occurrence of sidelink data that can be transmitted to the terminal device 1 may include that a buffer status report corresponding to the sidelink data that can be transmitted is triggered.
  • the occurrence of sidelink data that can be transmitted to the terminal device 1 may include that a scheduling request triggered based on the occurrence of sidelink data that can be transmitted is pending.
  • the non-contention based random access procedure may be started when the terminal device 1 receives the information instructing the start of the random access procedure from the base station device 3.
  • the non-contention based random access procedure may be started when the MAC layer of the terminal device 1 receives a beam failure notification from the lower layer.
  • the non-contention-based random access allows the base station device 3 and the terminal device 1 to be quickly connected between the terminal device 1 and the base station device 3 when the handover or the transmission timing of the mobile station device is not effective. May be used to establish the uplink synchronization of the.
  • Non-contention based random access may be used to transmit a beam failure recovery request when a beam failure occurs in the terminal device 1.
  • the use of non-contention based random access is not limited to these.
  • the information for instructing the start of the random access procedure is message 0, Msg. 0, NR-PDCCH order, PDCCH order, etc.
  • the terminal device 1 determines the preamble available to the terminal device 1.
  • a contention-based random access procedure of randomly selecting and transmitting one from the set may be performed.
  • the random access setting information may include information that is common within the cell, or may include dedicated information that is different for each terminal device 1.
  • part of the random access setting information may be associated with all SS / PBCH blocks in the SS burst set. However, a part of the random access setting information may be associated with all of the set one or more CSI-RSs. However, a part of the random access setting information may be associated with one downlink transmission beam (or beam index).
  • part of the random access setting information may be associated with one SS / PBCH block in the SS burst set. However, a part of the random access setting information may be associated with one of the set one or more CSI-RSs. However, a part of the random access setting information may be associated with one downlink transmission beam (or beam index). However, the information associated with one SS / PBCH block, one CSI-RS, and / or one downlink transmit beam may correspond to one SS / PBCH block, one CSI-RS, and / or Index information (for example, which may be an SSB index, a beam index, or a QCL setting index) for identifying one downlink transmission beam may be included.
  • Index information for example, which may be an SSB index, a beam index, or a QCL setting index
  • the set of one or more PRACH opportunities available for transmission of the random access preamble may be specified by the upper layer parameter prac-ConfigIndex provided in the upper layer (upper layer signal).
  • prac-ConfigIndex provided in the upper layer (upper layer signal).
  • PRACH setting physical random access channel setting
  • PRACH config a predetermined table
  • PRACH config random access channel setting
  • the specified one or more PRACH opportunities may be a set of PRACH opportunities associated with each of one or more SS / PBCH blocks transmitted by the base station apparatus 3.
  • the PRACH setting index can transmit a random access preamble, which is a cycle in which a set of PRACH opportunities shown in the random access setting table is temporally repeated (PRACH setting cycle (physical random access channel setting cycle: PRACH configuration period)). It may be used to set the subcarrier index, resource block index, subframe number, slot number, system frame number, symbol number, and / or preamble format.
  • PRACH setting cycle physical random access channel setting cycle: PRACH configuration period
  • the number of SS / PBCH blocks mapped to each PRACH opportunity may be indicated by the upper layer parameter SSB-perRACH-Occlusion provided by the upper layer. If SSB-perRACH-Occlusion is less than 1, then one SS / PBCH block is mapped to multiple consecutive PRACH opportunities.
  • the number of random access preambles mapped to each SS / PBCH block may be indicated by an upper layer parameter cb-preamblePerSSB provided by an upper layer.
  • the number of random access preambles mapped to each SS / PBCH block at each PRACH opportunity may be calculated from SSB-perRACH-Occasion and cb-preamblePerSSB.
  • the index of the random access preamble mapped to each SS / PBCH block on each PRACH occasion may be identified from the SB-perRACH-Occasion, cb-preamblePerSSB, and SSB index.
  • the SSB index may be mapped with the following rules.
  • the SSB indexes mapped to the PRACH opportunities with a small frequency resource index are n and n + 1
  • the SSB indexes mapped to the PRACH opportunities with a large frequency resource index are n + 2. It becomes n + 3.
  • multiple PRACH opportunities time-multiplexed in the PRACH slot are mapped in ascending order of time resource index. For example, in addition to the example of (2) above, when two more PRACH opportunities are multiplexed in the time direction within the PRACH slot, the SSB indices mapped to these PRACH opportunities are n + 4, n + 5 and n + 6, n + 7. .
  • a plurality of PRACH slots are mapped in ascending order of index.
  • the SSB indexes to be mapped are n + 8, n + 9, ....
  • the value of the SSB index returns to 0.
  • FIG. 13 is a diagram showing an example of SSB index allocation to PRACH opportunities according to the embodiment of the present invention.
  • two PRACH slots exist in a certain time interval
  • two PRACH slots exist in the time direction
  • two PRACH opportunities (RO) exist in the frequency direction in one PRACH slot
  • SSB indexes 0 to 11 exist.
  • An example of the case is shown.
  • Two SSB indexes are mapped to one PRACH opportunity, SSB indexes are mapped according to the rules of (1) to (4) above, and SSB index 0 is mapped again from the seventh PRACH opportunity.
  • An SSB index is mapped to each PRACH opportunity, but even if all PRACH opportunities within the PRACH setting cycle specified by prac-ConfigIndex are used, all SSB indexes (all SSs transmitted by the base station device 3 are used. / PBCH block), the SSB index may be mapped over multiple PRACH setup periods. However, the number of all SS / PBCH blocks transmitted by the base station device 3 may be indicated by an upper layer parameter. A period in which the PRACH setting period is repeated a predetermined number of times so that all SSB indexes are mapped at least once is referred to as an association period.
  • a minimum value satisfying the above condition may be used from a set of a plurality of predetermined values.
  • the predetermined set of values may be set for each PRACH setting cycle.
  • the SSB indexes are mapped again.
  • the remaining PRACH opportunities have SSB. The index does not have to be mapped.
  • a cycle in which a PRACH opportunity is allocated once for all SSB indexes is called an SSB index allocation cycle.
  • SSB-perRACH-Occlusion is 1 or more, each SSB index is mapped to one PRACH opportunity in one SSB index allocation cycle.
  • SSB-perRACH-Occlusion is less than 1, each SSB index is mapped to PRACH opportunity of 1 / SSB-perRACH-Occlusion in one SSB index allocation cycle.
  • the terminal device 1 may specify the association cycle based on the PRACH setting cycle indicated by the PRACH setting index and the number of SS / PBCH blocks specified by the upper layer parameter provided by the upper layer (upper layer signal). .
  • Each of one or more random access preamble groups included in the random access setting information may be associated with each reference signal (for example, SS / PBCH block, CSI-RS, or downlink transmission beam).
  • the terminal device 1 may select the random access preamble group based on the received reference signal (for example, SS / PBCH block, CSI-RS, or downlink transmission beam).
  • the random access preamble group associated with each SS / PBCH block may be specified by one or more parameters notified by the upper layer.
  • One of the one or more parameters may be an index (eg, a start index) of one or more preambles available.
  • One of the one or more parameters may be the number of preambles available for contention based random access per SS / PBCH block.
  • One of the one or more parameters may be the sum of the number of preambles available for contention-based random access and the number of preambles available for non-contention-based random access per SS / PBCH block.
  • One of the one or more parameters may be the number of SS / PBCH blocks associated with one PRACH opportunity.
  • the terminal device 1 receives one or a plurality of downlink signals transmitted using one downlink transmission beam, respectively, and receives random access setting information associated with one downlink signal among them.
  • the random access procedure may be performed based on the received random access setting information.
  • the terminal device 1 receives one or more SS / PBCH blocks in the SS burst set, receives random access setting information associated with one SS / PBCH block in the SS burst set, and receives the received random access setting.
  • a random access procedure may be performed based on the information.
  • the terminal device 1 receives one or more CSI-RSs, receives random access setting information associated with one of the CSI-RSs, and performs a random access procedure based on the received random access setting information. May be performed.
  • One or more random access setting information may be configured by one random access channel setting (RACH-Config) and / or one physical random access channel setting (PRACH-Config).
  • RACH-Config random access channel setting
  • PRACH-Config physical random access channel setting
  • -Parameters related to random access for each reference signal may be included in the random access channel settings.
  • Parameters related to the physical random access channel for each reference signal may be included in the physical random access channel setting.
  • One piece of random access setting information may indicate a parameter related to random access corresponding to one reference signal, and a plurality of pieces of random access setting information may indicate a parameter related to a plurality of random access corresponding to a plurality of reference signals.
  • One piece of random access setting information may indicate a parameter related to physical random access corresponding to one reference signal, and may indicate a parameter related to a plurality of random access corresponding to a plurality of reference signals.
  • the random access setting information (random access channel setting corresponding to the reference signal, physical random access channel setting corresponding to the reference signal) corresponding to the reference signal may be selected. .
  • the terminal device 1 receives one or a plurality of pieces of random access setting information from the base station device 3 and / or the transmission / reception point 4 different from the base station device 3 and / or the transmission / reception point 4 transmitting the random access preamble.
  • the terminal device 1 may transmit the 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.
  • the base station device 3 may determine the downlink transmission beam to be applied when transmitting the downlink signal to the terminal device 1, by receiving the random access preamble transmitted by the terminal device 1.
  • the terminal device 1 may transmit the random access preamble using the PRACH opportunity indicated by the random access setting information associated with a certain downlink transmission beam.
  • the base station device 3 should apply when transmitting a downlink signal to the terminal device 1 based on the random access preamble received from the terminal device 1 and / or the PRACH opportunity receiving the random access preamble.
  • the link transmit beam may be determined.
  • the base station device 3 transmits to the terminal device 1 an RRC parameter including one or a plurality of pieces of random access setting information (which may include random access resources) as an RRC message.
  • the terminal device 1 determines one or more available random access preambles and / or one or more available PRACH opportunities to be used in the random access procedure based on the channel characteristics with the base station device 3. You may choose.
  • the terminal device 1 is based on the channel characteristic (for example, reference signal reception power (RSRP)) measured by the reference signal (for example, SS / PBCH block and / or CSI-RS) received from the base station device 3. May select one or more available random access preambles and / or one or more PRACH opportunities to use for the random access procedure.
  • RSRP reference signal reception power
  • the uplink resource allocation in the frequency direction in this embodiment will be described below.
  • the terminal device 1 determines a resource block assignment (resource assignment) in the frequency direction using the resource allocation field included in the detected PDCCH DCI. May be.
  • uplink resource allocation types 0 and 1 are supported. The terminal device 1 may assume that the uplink resource allocation type 1 is used when receiving the PDCCH with the DCI format 0_0 that schedules the PUSCH.
  • the terminal device 1 When the PDCCH for the terminal device 1 is detected, the terminal device 1 first decides the UL BWP to which the resource assignment is applied, and then decides the resource allocation within the decided UL BWP.
  • the resource block numbering (RB numbering, RB numbering) of resource allocation starts from the lowest RB of the determined UL BWP. That is, the UL BWP to which the resource assignment is applied is the UL BWP determined by the terminal device 1.
  • the UL BWP determined by the terminal device 1 is a BWP for which uplink transmission (PUSCH transmission) is performed.
  • RB numbering (RB indexing) of (uplink resource allocation type 0 and type 1) is determined in the active BWP of the terminal device 1. That is, in this case, the UL BWP determined by the terminal device 1 may be an active BWP. That is, the UL BWP to which the resource assignment is applied may be an active BWP (active UL BWP).
  • RB numbering of resource allocation may be determined within the BWP indicated in the BWP instruction field. That is, in this case, the UL BWP determined by the terminal device 1 may be the BWP indicated in the BWP instruction field. That is, the UL BWP to which the resource assignment is applied may be the BWP indicated in the BWP instruction field.
  • DCI format 0_0 does not include a BWP indication field.
  • the resource block assignment information is a bit indicating a resource block group (RBGs, Resource Block Groups) allocated to the terminal device 1. Contains a map.
  • a resource block group is a set of continuous virtual resource blocks and may be defined from upper layer parameters.
  • the resource block assignment information is continuous with respect to the scheduled terminal device 1 within the active BWP of size N size BWP.
  • 3 illustrates a set of non-interleaved virtual resource blocks that are dynamically allocated.
  • the size N size BWP is the number of resource blocks indicating the bandwidth of the active UL BWP.
  • the size bandwidth N size BWP, 0 of the initial UL BWP is used. That is, in this case, the resource block assignment information indicates a set of non-interleaved virtual resource blocks continuously allocated to the scheduled terminal device 1 within the initial UL BWP of size N size BWP, 0 .
  • the uplink type 1 resource assignment field is a resource indication value (RIV, Resource Indication Value) corresponding to a start resource block (RB start, start virtual resource block) and the number of resource blocks (L RBs ) continuously allocated. Consists of. That is, the resource instruction value RIV is indicated in the resource assignment field.
  • RB start indicates the start position of the allocated resource block.
  • L RBs indicates the number (length, size) of resource blocks of continuously allocated resources.
  • the base station device 3 determines the resource allocation in the UL BWP determined by the terminal device 1, generates the RIV, and transmits the resource assignment including the bit string indicating the RIV to the terminal device 1.
  • the terminal device 1 specifies the resource block allocation in the frequency direction of the determined UL BWP (of the PUSCH) based on the bit string of the resource assignment field.
  • FIG. 12 is a diagram showing an example of calculating RIV.
  • N size BWP is the number of resource blocks indicating the bandwidth of the active UL BWP.
  • the value of RIV is calculated based on the size N size BWP of the active UL BWP, the start position RB start of the virtual resource block, and the number L RBs of resource blocks continuously allocated.
  • the value of L RBs is equal to or greater than 1 and does not exceed (N size BWP- RB start ).
  • N size BWP The number of resource blocks indicating the bandwidth, N size BWP, 0 is used. However, as described above, if the DCI format 0_0 is detected in any of the common search space set, initial UL size BWP bandwidth N size BWP, 0 is used to N size BWP in FIG 12 (A).
  • the value of L RBs is equal to or greater than 1 and does not exceed (N size BWP, 0- RB start ).
  • N initial BWP is the number of resource blocks indicating the bandwidth of the initial BWP (UL BWP).
  • N active BWP is the number of resource blocks indicating the bandwidth of an active BWP (UL BWP). That is, the N initial BWP is the size of the initial BWP (UL BWP).
  • N active BWP is the size of the active BWP (UL BWP).
  • the value of RIV is calculated based on the size N initial BWP of the initial UL BWP, the start position RB ′ start of the resource block, and the number L ′ RBs of resource blocks continuously allocated.
  • the multiplication of RB 'start and the coefficient K is RB start.
  • the multiplication of L'RBs and the coefficient K is L RBs .
  • the value of K is 1 if the N active BWP is equal to or less than the N initial BWP .
  • the resource to be allocated is specified by the start position RB start of the resource block and the number of resource blocks L RBs that are continuously allocated.
  • the size of the DCI format in USS (or the size of the frequency domain resource assignment field included in the DCI format) is derived by the initial BWP, but is applied to the active BWP. May be used in the case.
  • the DCI format may be DCI format 0_0 and / or DCI format 0_1.
  • FIG. 11 is a diagram showing an example for explaining the uplink resource allocation type 1 for BWP.
  • the common resource block n PRB is a resource block numbered in ascending order from 0 in each subcarrier interval setting ⁇ from the point A. That is, 1114 is a common resource block (common resource block 0) to which the number 0 is attached.
  • the center of the subcarrier index 0 of the common resource block 0 coincides with the point A.
  • 1104 is the start position of the carrier in the subcarrier interval setting ⁇ and is given from the upper layer parameter OffsetToCarrier.
  • the upper layer parameter OffsetToCarrier is an offset in the frequency domain between the point A and the lowest usable subcarrier of the carrier.
  • the offset (1115) indicates the number of resource blocks in the subcarrier interval setting ⁇ . That is, when the subcarrier interval setting ⁇ is different, the band of the frequency region of the offset is different.
  • 1104 may be the position of the resource block where the carrier starts.
  • the physical resource blocks are resource blocks numbered in ascending order from 0 for each BWP.
  • n CRB n PRB + N start BWP, i .
  • N start BWP, i the number of common resource blocks starting with the BWP index i for the common resource block index 0.
  • N size BWP, i the number of resource blocks indicating the BWP bandwidth of index i in the subcarrier interval setting ⁇ of BWP index i.
  • the position and bandwidth of the BWP in the frequency domain are given by the upper layer parameter locationAndBandwidth.
  • the number of physical resource blocks continuous with the first physical resource block (physical resource block index 0) of the BWP index i is given by the upper layer parameter locationAndBandwidth.
  • the value indicated by the parameter locationAndBandwidth of the upper layer is interpreted as the RIV value for the carrier.
  • N size BWP is set to 275.
  • RB start and L RBs identified by the value of RIV indicate the number of consecutive physical resource blocks indicating the first physical resource block (physical resource block index 0) of BWP and the bandwidth of BWP.
  • the first physical resource block of the BWP index i is the physical resource block offset with respect to the physical resource block (1104) indicated by the upper layer parameter OffsetToCarrier.
  • the number of resource blocks indicating the bandwidth of the BWP index i is N size BWP, i .
  • N start BWP, i of BWP index i is given from the offset indicated by the parameter OffsetToCarrier of the first physical resource block and the upper layer of the BWP index i.
  • 1105 is the physical resource block index 0 (n PRB # 0) in the UL BWP # 0 (1101) in the sub carrier interval setting ⁇ of the UL BWP # 0.
  • n CRB n PRB + N start BWP, 0 .
  • N start BWP, 0 (1107) is a common resource block started by UL BWP # 0 for common resource block index 0.
  • N size BWP, 0 (1106) is the number of resource blocks indicating the bandwidth of UL BWP # 0 in the subcarrier interval setting ⁇ of UL BWP # 0.
  • 1108 is the physical resource block index 0 (n PRB # 0) in UL BWP # 1 (1102) in the sub carrier interval setting ⁇ of UL BWP # 1.
  • N start BWP, 1 (1110) is a common resource block started by UL BWP # 1 for common resource block index 0.
  • N size BWP, 1 (1109) is the number of resource blocks indicating the bandwidth of UL BWP # 0 in the subcarrier interval setting ⁇ of UL BWP # 1.
  • 1111 is the physical resource block index 0 (n PRB # 0) in UL BWP # 2 (1102).
  • N start BWP, 2 (1113) is a common resource block started by UL BWP # 2 for common resource block index 0.
  • N size BWP, 2 (1112) is the number of resource blocks indicating the bandwidth of UL BWP # 2 in the subcarrier interval setting ⁇ of UL BWP # 2.
  • the start position (starting common resource block, N start BWP ) and the number of resource blocks (N size BWP ) are different for each BWP set in the terminal device 1.
  • RB numbering of resource allocations starts with the lowest RB of the established UL BWP. For example, even if the calculated RB start value is the same, if the lowest RB of the determined UL BWP is different, the position of the common resource block to start is also different.
  • FIG. 8 is a diagram showing an example of a random access procedure of the terminal device 1 in this embodiment.
  • the terminal device 1 transmits the random access preamble to the base station device 3 via the PRACH.
  • This transmitted random access preamble may be referred to as message 1 (Msg1).
  • Transmission of the random access preamble is also called PRACH transmission.
  • the random access preamble is configured to notify the base station device 3 of information by using one of the plurality of sequences. For example, 64 types of sequences (random access preamble index numbers 1 to 64) are prepared. When 64 types of sequences are prepared, 6-bit information (which may be ra-PreambleIndex or preamble index) can be shown to the base station apparatus 3. This information may be indicated as a Random Access Preamble Identifier (RAPID).
  • RAPID Random Access Preamble Identifier
  • the terminal device 1 In the case of the contention-based random access procedure, the terminal device 1 itself randomly selects the index of the random access preamble. In the contention-based random access procedure, the terminal device 1 selects the SS / PBCH block having the RSRP of the SS / PBCH block exceeding the set threshold value, and selects the preamble group. When the relationship between the SS / PBCH block and the random access preamble is set, the terminal device 1 randomly selects one or more random access preambles associated with the selected SS / PBCH block and the selected preamble group. The ra-PreambleIndex is selected for, and the selected ra-PreambleIndex is set to the preamble index (PREAMBLE_INDEX).
  • the selected SS / PBCH block and the selected preamble group may be divided into two subgroups based on the transmission size of the message 3.
  • the terminal device 1 randomly selects a preamble index from the subgroup corresponding to the transmission size of the small message 3, and when the transmission size of the message 3 is large, the preamble index is selected as the transmission size of the large message 3.
  • the preamble index may be randomly selected from the corresponding subgroup.
  • the index when the message size is small is usually selected when the characteristics of the propagation path are poor (or the distance between the terminal device 1 and the base station device 3 is long), and the index when the message size is large is the propagation path. Is good (or the distance between the terminal device 1 and the base station device 3 is short).
  • the terminal device 1 selects the index of the random access preamble based on the information received from the base station device 3.
  • the information received from the base station device 3 by the terminal device 1 may be included in the PDCCH.
  • the terminal device 1 executes the contention-based random access procedure, and the terminal device 1 itself selects the index of the random access preamble.
  • the base station device 3 that has received 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 transmit in S802. , And transmits a random access response including the generated RAR message to the terminal device 1 by DL-SCH. That is, the base station device 3 transmits a random access response including the RAR message corresponding to the random access preamble transmitted in S801 on the PDSCH in the primary cell (or primary secondary cell).
  • the PDSCH corresponds to the PDCCH including RA-RNTI.
  • s_id is an index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13.
  • t_id is an index of the first slot of PRACH in the system frame, and takes a value from 0 to 79.
  • f_id is a PRACH index in the frequency domain and takes values from 0 to 7.
  • ul_carrier_id is an uplink carrier used for Msg1 transmission.
  • the ul_carrier_id for the NUL carrier is 0 and the ul_carrier_id for the SUL carrier is 1.
  • the random access response may be referred to as Message 2 or Msg2.
  • the base station device 3 includes a random access preamble identifier corresponding to the received random access preamble and a RAR message (MAC RAR) corresponding to the identifier in the message 2.
  • the base station device 3 calculates a transmission timing shift between the terminal device 1 and the base station device 3 from the received random access preamble, and transmits transmission timing adjustment information (TA command, Timing Advance Command) for adjusting the shift. ) Is included in the RAR message.
  • the RAR message includes at least a random access response grant field mapped to an uplink grant, a Temporary C-RNTI field to which a Temporary C-RNTI (Cell Radio Network Temporary Identifier) is mapped, and a TA command (Timing Advance Command). Including.
  • the terminal device 1 adjusts the timing of PUSCH transmission based on the TA command. The timing of PUSCH transmission may be adjusted for each group of cells.
  • the base station device 3 includes the random access preamble identifier corresponding to the received random access preamble in the message 2.
  • the terminal device 1 In order to respond to the PRACH transmission, the terminal device 1 detects the DCI format 1_0 to which the CRC parity bit scrambled by the corresponding RA-RNTI is added in the SpCell (PCell or PSCell) during the random access response window. (Monitor) The period (window size) of the random access response window is given by the upper layer parameter ra-ResponseWindow. The window size is the number of slots based on the subcarrier spacing of the Type1-PDCCH common search space.
  • the terminal device 1 When the terminal device 1 detects the PDSCH including the DCI format 1_0 with the CRC scrambled by RA-RNTI and one DL-SCH transport block within the window period, the terminal device 1 detects the transport block. Pass to upper layer.
  • the upper layer parses that transport block for the random access preamble identifier (RAPID) associated with the PRACH transmission.
  • RAPID random access preamble identifier
  • the upper layer indicates the uplink grant to the physical layer. To identify, the RAPID included in the received random access response and the RAPID corresponding to the transmitted random access preamble are the same.
  • the uplink grant is called a random access response uplink grant (RAR UL grant) in the physical layer. That is, the terminal device 1 can identify the RAR message (MAC RAR) addressed to itself from the base station device 3 by monitoring the random access response (message 2) corresponding to the random access preamble identifier.
  • MAC RAR random access response uplink grant
  • the terminal device 1 When the terminal device 1 does not detect the DCI format 1_0 with the CRC scrambled by RA-RNTI within the window period, or (ii) the terminal device 1 DL-on the PDSCH within the window period If the SCH transport block is not received correctly, or (iii) the upper layer does not identify the RAPID associated with the PRACH transmission, the upper layer instructs the physical layer to transmit the PRACH.
  • the terminal device 1 selects the random access preamble based on the information received from the base station device 3.
  • the device 1 considers that the non-contention based random access procedure has been successfully completed, and transmits the PUSCH based on the uplink grant included in the random access response. If the received random access response includes the random access preamble identifier corresponding to the transmitted random access preamble, and the random access preamble is selected by the terminal device 1 itself, the TC-RNTI is included in the received random access response.
  • the random access message 3 is set to the value of the TC-RNTI field to be transmitted, and the random access message 3 is transmitted by PUSCH based on the uplink grant included in the random access response.
  • the PUSCH corresponding to the uplink grant included in the random access response is transmitted in the serving cell in which the corresponding preamble is transmitted on the PRACH.
  • RAR UL grant is used for scheduling PUSCH transmission (or RAR PUSCH).
  • the PUSCH (or PUSCH transmission) scheduled by the RAR UL grant may be referred to as RAR PUSCH (or RAR PUSCH transmission).
  • RAR PUSCH transmission is PUSCH transmission corresponding to RAR UL grant. That is, the PUSCH (PUSCH transmission) scheduled by the RAR UL grant may be the PUSCH (PUSCH transmission) corresponding to the RAR UL grant.
  • the terminal device 1 transmits Msg3 (message 3) based on the RAR UL grant. That is, in the contention-based random access procedure, Msg3 PUSCH (Msg3 PUSCH transmission) is scheduled by the RAR UL grant. Msg3 may be the first scheduled transmission (PUSCH transmission, first scheduled transmission) of the contention based random access procedure. Msg3 is a message that includes C-RNTI MAC CE or CCCH SDU as part of the contention based random access procedure, and may be transmitted on UL-SCH. In the contention based random access procedure, RAR PUSCH transmission may be Msg3 PUSCH transmission.
  • the terminal device 1 may transmit the PUSCH (RAR PUSCH) based on the RAR UL grant. That is, in the non-contention based random access procedure, the PUSCH scheduled by the RAR UL grant does not have to be referred to as Msg3PUSCH. Also, in the non-contention based random access procedure, the PUSCH scheduled by the RAR UL grant may be referred to as Non-Msg3 PUSCH. That is, in the non-contention based random access procedure, the Non-Msg3 PUSCH may be the PUSCH scheduled by the RAR UL grant.
  • the Msg3 PUSCH may include the PUSCH scheduled by the RAR UL grant in the contention-based random access procedure.
  • the Msg3 PUSCH may also include the PUSCH scheduled by the RAR UL grant in the non-contention based random access procedure.
  • Msg3 PUSCH may be the first scheduled uplink transmission (PUSCH transmission, first scheduled transmission) in the random access procedure. That is, the Msg3 PUSCH may be the PUSCH scheduled by the RAR UL grant regardless of the type of random access procedure (contention-based random access procedure or non-contention-based random access procedure).
  • retransmission of Msg3 PUSCH may be scheduled by DCI format 0_0 with CRC parity bits scrambled by TC-RNTI.
  • the retransmission of Msg3 PUSCH may be scheduled by DCI format 0_0 with CRC parity bits scrambled by C-RNTI.
  • the '(Msg3) PUSCH time resource allocation' field is used to indicate time domain resource allocation for PUSCH scheduled by the RAR UL grant.
  • The'MCS 'field is used to determine the MCS index for the PUSCH scheduled by the RAR UL grant.
  • The'TPC command for scheduled PUSCH 'field is used for setting the transmission power of the PUSCH scheduled by the RAR UL grant.
  • the'CSI request 'field is reserved.
  • the'CSI request 'field is used to determine whether an aperiodic CSI report is included in the PUSCH transmission.
  • FIG. 9 is a diagram showing an example of fields included in the RAR UL grant.
  • the terminal device 1 transmits the PUSCH scheduled by the RAR UL grant without frequency hopping.
  • the terminal device 1 transmits the PUSCH scheduled by the RAR UL grant with frequency hopping.
  • the frequency resource allocation of PUSCH scheduled by RAR UL grant may be uplink resource allocation type 1.
  • FIG. 7 is a diagram showing an example of frequency hopping in the present embodiment.
  • FIG. 7A is an example of PUSCH transmission without frequency hopping.
  • FIG. 7B is an example of PUSCH transmission accompanied by intra-slot frequency hopping.
  • FIG.7 (c) is an example of PUSCH transmission accompanied with inter-slot frequency hopping.
  • PUSCH transmission with intra-slot frequency hopping is performed in a slot with a first frequency hop (first frequency hop, first hop, first frequency unit) and a second frequency hop (second frequency hop). hop, first hop, second frequency unit).
  • the number of symbols for the first frequency hop may be given by Floor (N PUSCH, s symb / 2).
  • the number of symbols for the second frequency hop may be given by N PUSCH, s symb -Floor (N PUSCH, s symb / 2).
  • N PUSCH, s symb is the length of PUSCH transmission in OFDM symbols in one slot.
  • N PUSCH, s symb may be the number of OFDM symbols used for the scheduled PUSCH in one slot.
  • the value of N PUSCH, s symb may be indicated in a field included in the DCI format or RAR UL grant.
  • the resource block difference RB offset between the starting RB (starting RB) of the first frequency hop and the starting RB of the first frequency hop may be referred to as the frequency offset of the resource block. That is, RB offset is the frequency offset of RB between two frequency hops. Also, the RB offset may be referred to as a frequency offset for the second frequency hop. For example, the start RB of the first frequency hop is called RB start .
  • the starting RB of the second frequency hop may be given by (Equation 5) (RB start + RB offset ) modN size BWP .
  • the RB start may be given by the frequency resource allocation field.
  • the function (A) mod (B) divides A and B, and outputs the undivisible remainder.
  • intra-slot frequency hopping may be applied to single-slot PUSCH transmission and / or multi-slot PUSCH transmission.
  • frequency hopping between slots may be applied to multi-slot PUSCH transmission.
  • RB offset is the frequency offset of RB between two frequency hops.
  • '(Msg3) PUSCH frequency resource allocation' field is used for resource allocation for PUSCH transmissions scheduled by RAR UL grant.
  • '(Msg3) PUSCH frequency resource allocation' (PUSCH frequency resource assignment, Msg3 PUSCH frequency resource assignment, PUSCH frequency resource assignment) field is a fixed size resource block assignment (fixed size resource block assignment) or RAR PUSCH frequency resource It may be referred to as allocation (RAR PUSCH frequency resource allocation).
  • the PUSCH frequency resource allocation field (or frequency resource assignment field) has a fixed number of bits regardless of the UL BWP bandwidth set for the terminal device 1.
  • the terminal device 1 processes the frequency resource allocation field based on the size N size BWP of the active UL BWP. That is, the terminal device 1 truncates or inserts bits in PUSCH frequency resource allocation based on the size of the active UL BWP (N size BWP ). Then, the terminal device 1 can adapt to the bandwidth of the UL BWP to which the resource allocation is applied by truncating or inserting bits in the PUSCH frequency resource allocation.
  • FIG. 10 is a diagram showing an example of the interpretation of the'PUSCH frequency resource allocation 'field according to the present embodiment.
  • Reference numeral 1001 in FIG. 10A is a fixed'PUSCH frequency resource allocation 'field having 14 bits.
  • 1002 is a N UL, hop hopping bit.
  • Reference numeral 1003 denotes the bits remaining after removing the N UL, hop hopping bits from 1001 and is (14-N UL, hop ) bits. That is, the 14-bit 1001 is composed of 1002 and 1003.
  • the number of N UL, hop hopping bits is given based on the value indicated in the'Frequency hopping flag 'field and / or the bandwidth of N size BWP .
  • the number of bits in the N UL, hop example may be 1 bit when the size of the N size BWP is smaller than the value of the predetermined number of resource blocks.
  • the number of bits in the N UL, hop example may be 2 bits if the size of the N size BWP is equal to or larger than the value of the predetermined number of resource blocks.
  • the value of the predetermined number of resource blocks may be 50. A description of N size BWP will be given later.
  • the N UL, hop hopping bit is 0 bit.
  • 1003 is 1001 and has 14 bits.
  • the value of the frequency hopping flag (Frequency hopping flag) is 1, does the number of bits of N UL, hop hopping bits exceed the value Y (for example, 50) of the predetermined number of resource blocks for the value of N size BWP ? It may be given to 1 bit or 2 bits depending on whether or not. For example, when N size BWP is smaller than the value Y of a predetermined number of resource blocks, N UL, hop hopping bits may be given to 1 bit. If N size BWP is equal to or greater than the value Y of a given number of resource blocks, then N UL, hop hopping bits may be given to 2 bits. That is, 1003 has 12 bits or 13 bits.
  • FIG. 10B is a diagram illustrating an example of truncating the bits of the'PUSCH frequency resource allocation 'field when N size BWP is smaller than or equal to a predetermined resource block number value of 180.
  • the terminal device 1 truncates the bits of PUSCH frequency resource allocation from the least significant bit (LSB) to b bits when N size BWP is smaller than or equal to the value X of the predetermined number of resource blocks. That is, b bits is the number of truncated bits.
  • the function Ceiling (A) outputs the smallest integer not less than A.
  • the truncated PUSCH frequency resource allocation may be referred to as the truncated frequency resource allocation field.
  • the terminal device 1 may interpret the truncated frequency resource allocation field according to a rule for the frequency resource allocation field (frequency domain resource assignment) included in the DCI format 0_0.
  • 1004 is a PUSCH frequency resource allocation having 14 bits.
  • 1005 is a NUL, hop hopping bit.
  • Reference numeral 1006 denotes bits other than N UL, hop hopping bits in PUSCH frequency resource allocation.
  • 1008 is a resource block allocation to be truncated. The number of bits of 1008 is b bits. The number of bits of 1007 is 14-b.
  • FIG. 10C is a diagram illustrating an example of inserting a bit of the'PUSCH frequency resource allocation 'field when the bandwidth of the N size BWP is larger than the predetermined value 180 of the number of resource blocks.
  • 1009 is PUSCH frequency resource allocation having 14 bits.
  • Reference numeral 1010 is a NUL, hop hopping bit.
  • Reference numeral 1012 denotes bits remaining after PUSCH frequency resource allocation except NUL, hop hopping bits.
  • the number of bits of 1012 is (14-N UL, hop ) bits.
  • N size BWP is larger than the value X of the predetermined number of resource blocks
  • the terminal device 1 sets the b most significant bit (0 most significant bit) to be set to a value of “0” after the N UL, hop hopping bits in the PUSCH frequency resource allocation.
  • Insert MSB most significant bits). That is, b bits is the number of bits to be inserted.
  • the value of Z may be 14.
  • the PUSCH frequency resource allocation in which b bits are inserted may be referred to as an extended resource block allocation field.
  • the terminal device 1 may interpret the extended frequency resource allocation field according to the rule for the frequency resource allocation field (frequency domain resource assignment) included in the DCI format 0_0.
  • the number of bits of 1011 is b bits.
  • Reference numeral 1009 denotes expanded frequency resource allocation.
  • the number of bits of 1009 is the sum of 14 bits and b bits of PUSCH frequency resource allocation.
  • N size BWP may be the size of the active UL BWP.
  • One initial BWP including at least one DL BWP and one UL BWP is set for the terminal device 1. Furthermore, up to four additional BWPs are set for the terminal device 1. The size of each UL BWP set for the terminal device 1 may be different. As mentioned above, there is always one active (activated) BWP in an activated serving cell. For example, if the active UL BWP is the initial UL BWP, then N size BWP is the size of the initial UL BWP.
  • N size BWP is the size of the activated additional UL BWP.
  • the size of UL BWP is the number of resource blocks indicating the bandwidth of the corresponding UL BWP.
  • the terminal device 1 determines to truncate or insert a bit into the PUSCH frequency resource allocation field based on the size N size BWP of the active UL BWP. However, in the contention-based random access procedure, the terminal device 1 decides to truncate or insert a bit into the PUSCH frequency resource allocation field based on the size N size BWP, 0 of the initial UL BWP. May be. That is, in the contention-based random access procedure, the terminal device 1 performs frequency domain resource allocation for Msg3 PUSCH transmission and / or Msg3 PUSCH retransmission in the active UL BWP based on the following conditions 1 and 2. You may decide.
  • the frequency domain resource allocation may be determined within the active UL BWP.
  • Retransmission of Msg3 PUSCH means retransmission of transport block in Msg3 PUSCH.
  • the retransmission of the transport block in the Msg3 PUSCH may be scheduled by the DCI format 0_0 with the CRC scrambled by the TC-RNTI shown in the RAR message. That is, in the contention-based random access procedure, the PUSCH retransmission of the transport block transmitted on the PUSCH corresponding to the RAR UL grant included in the RAR message is performed in the DCI format with the CRC parity bit scrambled by TC-RNTI added. Scheduled by 0_0.
  • the DCI format 0_0 is transmitted on the PDCCH of the type 1 PDCCH common search space set.
  • the initial UL BWP and the active UL BWP in the following Condition 1 and Condition 2 correspond to the same uplink carrier of the same serving cell.
  • the uplink carrier may be an uplink carrier on which PRACH transmission and Msg3 PUSCH transmission are performed.
  • the terminal device 1 (condition 1) has the same subcarrier interval and the same CP (Cyclic Prefix) length as the active UL BWP and the initial UL BWP, and the active UL BWP has all the resources of the initial UL BWP.
  • the value of RIV shown in the Msg3 PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB start of the virtual resource block, and the number of resource blocks to be continuously allocated L RBs.
  • the RIV value shown in the frequency domain resource allocation field included in the DCI format 0_0 that schedules the retransmission of the Msg3 PUSCH is the size of the initial UL BWP, the start position RB start of the virtual resource block, and the continuous allocation. It is given based on the number of resource blocks L RBs that are allocated.
  • the N size BWP used to calculate the frequency offset set for the second hop is , May be the size of the initial UL BWP. That is, in this case, in FIG. 17, the N size BWP may be the size of the initial UL BWP.
  • the terminal device 1 is (condition 1) active UL BWP and initial UL BWP are the same subcarriers. It has the same CP (Cyclic Prefix) length as the interval and the active UL BWP includes all resource blocks of the initial UL BWP, or (condition 2) the active UL BWP is the initial UL BWP.
  • the initial UL BWP is determined, and the resource allocation in the frequency direction within the determined initial UL BWP is determined. The resource block numbering of resource allocation starts from the lowest RB of the finalized UL BWP. That is, when calculating the RIV using FIG.
  • the terminal device 1 uses the size bandwidth N size BWP, 0 of the initial UL BWP as the N size BWP in FIG. 12A.
  • the RB numbering of frequency resource allocation for Msg3 PUSCH transmission or Msg3 PUSCH retransmission may start from the lowest RB (first RB, lowest RB) of the initial UL BWP.
  • Msg3 PUSCH transmission or Msg3 PUSCH retransmission is performed in the active UL BWP. If the active UL BWP is the initial UL BWP, the Msg3 PUSCH transmission is done on the initial UL BWP (the activated initial UL BWP). If the active UL BWP is not the initial UL BWP, the Msg3 PUSCH transmission is done on the active UL BWP.
  • the terminal device 1 determines that the maximum number of resource blocks for frequency domain resource allocation for Msg3 PUSCH transmission and / or Msg3 PUSCH retransmission is the resource block of the initial UL BWP. It may be determined that the RB numbering equals the number and starts with the lowest RB (first RB, lowest RB) of the active UL BWP. At this time, the RIV value shown in the Msg3 PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB start of the virtual resource block, and the number L of resource blocks continuously allocated. Given based on RBs .
  • the RIV value shown in the frequency domain resource allocation field included in the DCI format 0_0 that schedules the retransmission of the Msg3 PUSCH is the size of the initial UL BWP, the start position RB start of the virtual resource block, and the continuous allocation. It is given based on the number of resource blocks L RBs that are allocated. However, the RB numbering may start from the lowest RB (first RB, lowest RB) of the active UL BWP. In Msg3 PUSCH transmission or Msg3 PUSCH retransmission, if both (Condition 1) and (Condition 2) are not satisfied, the N size BWP used for calculating the frequency offset set for the second hop is the active UL BWP.
  • the N size BWP may be the size of the active UL BWP.
  • the N size BWP used for calculation of the frequency offset set for the second hop is the initial UL BWP.
  • the terminal device 1 determines and determines the active UL BWP if both Condition 1 and Condition 2 are not met. Determine resource allocation in the frequency direction within the active UL BWP.
  • the resource block numbering of frequency resource allocation for Msg3 PUSCH transmission or Msg3 PUSCH retransmission starts from the lowest RB of the established active UL BWP.
  • the terminal device 1 uses the size bandwidth N size BWP, 0 of the initial UL BWP for the N size BWP in FIG. 12A when calculating the RIV using FIG. 12A.
  • Msg3 PUSCH transmission or Msg3 PUSCH retransmission is performed in the active UL BWP. If the active UL BWP is the initial UL BWP, the Msg3 PUSCH transmission is done on the initial UL BWP (the activated initial UL BWP). If the active UL BWP is not the initial UL BWP, the Msg3 PUSCH transmission is done on the active UL BWP.
  • the number of N UL, hop hopping bits exceeds the value Y of the predetermined number of resource blocks when the value of N size BWP exceeds Y. It may be given to 1 bit or 2 bits depending on whether it is present or not.
  • the number of N UL, hop hopping bits is 1 bit or 2 bits based on whether the size of the initial UL BWP exceeds the value Y of the predetermined resource block number. May be given to.
  • the bits of N UL, hop hopping bits may be included in the PUSCH frequency resource allocation field included in the RAR UL grant.
  • FIG. 17 is a diagram illustrating a second hop frequency offset for PUSCH scheduled by a RAR UL grant with frequency hopping in the present embodiment. That is, in Msg3 PUSCH transmission or Msg3 PUSCH retransmission, N size BWP in FIG. 17 may be the size of the initial UL BWP (N size BWP, 0 ).
  • the value of the frequency offset for the second hop is determined based on the size of the initial UL BWP (N size BWP, 0 ). May be. Referring to FIG. 17, when the N size BWP is smaller than the value Y of the predetermined number of resource blocks, the N UL, hop hopping bit may be given to 1 bit.
  • the second hop frequency offset (RB offset ) for Msg3 PUSCH transmission is Floor (N size BWP / 2) or Floor (N size BWP / 4). If N size BWP is equal to or greater than the value Y of a given number of resource blocks, then N UL, hop hopping bits may be given to 2 bits.
  • the second hop frequency offset for Msg3 PUSCH transmission is Floor (N size BWP / 2), Floor (N size BWP / 4), or -Floor (N size BWP / 4).
  • the N size BWP used for the frequency offset of the second hop for Msg3 PUSCH transmission may be the size of the initial UL BWP.
  • the N size BWP used for the second hop frequency offset for Msg3 PUSCH transmission may be the size of the active UL BWP.
  • the DCI format 0_0 that schedules the retransmission of the Msg3 PUSCH is added with the CRC scrambled by the TC-RNTI. That is, the frequency offset value may be determined based on FIG. 17 for the PUSCH scheduled by the DCI format 0_0 to which the CRC scrambled by the TC-RNTI is added.
  • the N size BWP in FIG. 17 may be the size of the initial UL BWP.
  • the value of the frequency offset is set by an upper layer parameter frequencyHoppingOffsetLists included in PUSCH-Config.
  • the upper layer parameter frequencyHoppingOffsetLists is used to indicate the set of frequency offset (frequency hopping offset) values when frequency hopping is applied. For example, if the size of the active UL BWP is smaller than the predetermined resource block number value 50 PRB, the DCI format may indicate one of two frequency offsets for which upper layer parameters are set.
  • the DCI format may indicate one of the four frequency offsets for which upper layer parameters are set. Good.
  • Uplink resource allocation type 1 may be used for the scheduled PUSCH. In this embodiment, frequency hopping may be associated with uplink resource allocation type 1.
  • the terminal device 1 determines whether to truncate or insert a bit in the PUSCH frequency resource allocation field based on the size N size BWP of the active UL BWP. Good. That is, in the contention-based random access procedure, the terminal device 1 is based on the size N size BWP of the active UL BWP, and within the active UL BWP, PUSCH transmission scheduled by the RAR UL grant and / or its scheduled PUSCH transmission. Frequency domain resource allocation for PUSCH retransmission may be determined.
  • the PUSCH retransmission scheduled by the RAR UL grant means the retransmission of the transport block in the PUSCH scheduled by the RAR UL grant. Retransmission of the transport block may be scheduled by DCI format 0_0 (or DCI format 0_1) with a CRC that is scrambled by C-RNTI (or MCS-C-RNTI).
  • the terminal device 1 responds to the PUSCH transmission scheduled by the RAR UL grant and / or the frequency domain resource allocation for the scheduled retransmission of the PUSCH.
  • Active UL BWP is determined, and resource allocation in the frequency direction within the determined active UL BWP is determined.
  • the resource block numbering of frequency domain resource allocations for PUSCH transmissions scheduled by RAR UL grants and / or their scheduled PUSCH retransmissions starts from the lowest RB of the established active UL BWP.
  • the value of RIV shown in the PUSCH frequency resource allocation field included in the RAR UL grant is the size of the active UL BWP, the start position RB start of the virtual resource block, and the number L of resource blocks continuously allocated.
  • the frequency domain resource allocation field included in the DCI format 0_0 that schedules the retransmission of the PUSCH scheduled by the RAR UL grant includes the size of the active UL BWP, the start position RB start of the virtual resource block, and continuously. It is given based on the number of allocated resource blocks L RBs .
  • the terminal device 1 uses the size N size BWP of the active UL BWP in FIG. 12 (A) when calculating the RIV using FIG. 12 (A).
  • the number of N UL, hop hopping bits is equal to the number of active UL BWP. It may be given to 1 bit or 2 bits, depending on whether the size exceeds the value Y of the predetermined number of resource blocks.
  • the bits of N UL, hop hopping bits may be included in the PUSCH frequency resource allocation field included in the RAR UL grant.
  • N UL, hop hopping bits may be included in the frequency domain resource allocation field included in the DCI format that schedules retransmission.
  • the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for the scheduled PUSCH may be given by FIG.
  • the N size BWP in FIG. 17 may be the size of the active UL BWP. That is, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH is given by the size of the active UL BWP. Good.
  • the frequency offset value may not be determined based on FIG. 17 for the PUSCH scheduled by the RAR UL grant and / or the retransmission of the scheduled PUSCH. . That is, in the non-contention based random access procedure, the frequency offset value for the PUSCH scheduled by the RAR UL grant and / or the retransmission of the scheduled PUSCH is the upper layer parameter frequencyHoppingOffsetLists included in PUSCH-Config. Set by. The upper layer parameter frequencyHoppingOffsetLists is used to indicate the set of frequency offset (frequency hopping offset) values when frequency hopping is applied.
  • the DCI format may indicate one of two frequency offsets in which upper layer parameters are set. Further, when the size of the active UL BWP is equal to or larger than the value 50PRB of the predetermined number of resource blocks, the DCI format may indicate one of the four frequency offsets in which the upper layer parameters are set. Good.
  • N size BWP may be the size of the initial UL BWP. That is, in FIG. 10, the terminal device 1 determines to truncate or insert a bit in the PUSCH frequency resource allocation field based on the size N size BWP, 0 of the initial UL BWP. That is, the terminal device 1 truncates or inserts bits into or from the PUSCH frequency resource allocation field based on the size N size BWP, 0 of the initial UL BWP regardless of the type of the random access procedure. You may decide.
  • the terminal device 1 is PUSCH scheduled by the RAR UL grant in the active UL BWP based on the size N size BWP, 0 of the initial UL BWP.
  • Frequency domain resource allocations for transmission and / or its scheduled PUSCH retransmissions may be determined. That is, in the non-contention based random access procedure, the value of RIV indicated in the PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB start of the virtual resource block, and the continuous allocation. It is given based on the number of resource blocks L RBs that are allocated.
  • the size bandwidth of the initial UL BWP with respect to the active UL BWP size N size BWP in FIG. Use N size BWP, 0 .
  • the resource block numbering of frequency domain resource allocations for PUSCH transmissions scheduled by RAR UL grants and / or their scheduled PUSCH retransmissions may start from the lowest RB of a confirmed active UL BWP. Good.
  • the number of N UL, hop hopping bits is the size of the initial UL BWP. May be given to 1 bit or 2 bits depending on whether or not exceeds a predetermined resource block number value Y. Then, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for the scheduled PUSCH may be given by FIG.
  • the N size BWP in FIG. 17 may be the size of the initial UL BWP. That is, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH may be given by the size of the initial UL BWP.
  • the number of N UL, hop hopping bits is equal to the number of active UL BWP. It may be given to 1 bit or 2 bits, depending on whether the size exceeds the value Y of the predetermined number of resource blocks. Then, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for the scheduled PUSCH may be given by FIG.
  • the N size BWP in FIG. 17 may be the size of the active UL BWP. That is, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH may be given by the size of the active UL BWP. .
  • N size BWP may be the size of the active UL BWP. That is, in FIG. 10, the terminal device 1 may decide to truncate or insert a bit into the PUSCH frequency resource allocation field based on the size N size BW of the active UL BWP.
  • the terminal device 1 irrespective of the type of the random access procedure, based on the condition 1 and the condition 2 described above, the PUSCH scheduled by the RAR UL grant in the active UL BWP and / or Frequency domain resource allocation for the PUSCH retransmission may be determined.
  • the retransmission of the PUSCH means the retransmission of the transport block in the PUSCH scheduled by the RAR UL grant.
  • the retransmission of transport blocks in the PUSCH is scheduled even in the contention based random access procedure by DCI format 0_0 with CRC added scrambled by TC-RNTI indicated in the RAR message.
  • Retransmissions of transport blocks in the PUSCH may be scheduled by DCI format 0_0 with CRC appended by C-RNTI in a non-contention based random access procedure.
  • the terminal device 1 (condition 1) has the same subcarrier interval and the same CP (Cyclic Prefix) length as the active UL BWP and the initial UL BWP, and the active UL BWP has all the initial UL BWP.
  • the resource block numbering of resource allocation starts from the lowest RB of the finalized UL BWP. That is, when calculating the RIV using FIG.
  • the terminal device 1 uses the size bandwidth N size BWP, 0 of the initial UL BWP as the N size BWP in FIG. 12A.
  • the RB numbering of frequency resource allocations for retransmission of PUSCH and / or its PUSCH scheduled by RAR UL grant may start from the lowest RB (first RB, lowest RB) of the initial UL BWP.
  • the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH may be given by the size of the initial UL BWP.
  • the N size BWP in FIG. 17 may be the size of the initial UL BWP.
  • the retransmission of the PUSCH and / or its PUSCH scheduled by the RAR UL grant is done in the active UL BWP.
  • the terminal device 1 determines that the maximum number of resource blocks of frequency domain resource allocation for retransmission of PUSCH and / or its PUSCH scheduled by the RAR UL grant is the initial UL. It may be determined that the RB numbering is equal to the number of resource blocks of the BWP and that the RB numbering starts from the lowest RB (first RB, lowest RB) of the active UL BWP. At this time, the RIV value indicated in the PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB start of the virtual resource block, and the number of continuously allocated resource blocks L RBs. Given based on.
  • the terminal device 1 uses the size bandwidth N size BWP, 0 of the initial UL BWP as the N size BWP in FIG. 12A.
  • the RB numbering may start from the lowest RB (first RB, lowest RB) of the active UL BWP. That is, for the frequency domain resource allocation for PUSCH and / or retransmission of the PUSCH scheduled by the RAR UL grant, the terminal device 1 activates the active UL if both Condition 1 and Condition 2 are not satisfied.
  • the BWP is determined, and resource allocation in the frequency direction within the determined active UL BWP is determined.
  • the resource block numbering of the frequency resource allocations for retransmissions of the PUSCH and / or its PUSCH scheduled by the RAR UL grant starts from the lowest RB of the established active UL BWP.
  • the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH is also given by the size of the active UL BWP.
  • the N size BWP in FIG. 17 may be the size of the active UL BWP.
  • the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for the scheduled PUSCH may be given by the size of the initial UL BWP.
  • the terminal device 1 may transmit the PUSCH scheduled by the RAR UL grant in the slot n + k 2 + a.
  • the value of k 2 may be indicated by the '(Msg3) PUSCH time resource allocation' field included in the RAR UL grant.
  • a is an additional subcarrier spacing specific slot delay value for the first transmission of the PUSCH scheduled by the RAR UL grant. That is, the value of a corresponds to the subcarrier interval to which the PUSCH scheduled by the RAR UL grant is applied.
  • the value of a may be 2 slots. If the subcarrier spacing is 30 kHz, the value of a may be 3 slots. If the subcarrier spacing is 60 kHz, the value of a may be 4 slots. If the subcarrier spacing is 120 kHz, the value of a may be 6 slots. That is, when the terminal device 1 transmits the PUSCH scheduled by the RAR UL grant, the value of a corresponding to the subcarrier interval of the PUSCH to be transmitted is applied in addition to the k 2 value.
  • the terminal device 1 performs PUSCH transmission of the message 3 based on the RAR UL grant included in the RAR message received in S802.
  • the PUSCH corresponding to the transmission of the message 3 is transmitted in the serving cell in which the corresponding preamble is transmitted on the PRACH. Specifically, the PUSCH corresponding to the transmission of message 3 is transmitted in the active UL BWP.
  • “validating” the transform precoding means that in the uplink communication (for example, PUSCH transmission) between the terminal device 1 and the base station device 3, the discrete Fourier transform spread OFDM (DFT-S- OFDM: Discrete Fourier Transform Spread OFDM) may be used.
  • “disabling” the transform precoding means that in uplink communication (for example, PUSCH transmission) between the terminal device 1 and the base station device 3, an orthogonal frequency including a cyclic prefix (CP: Cyclic Prefix) is included. It may mean that division multiplexing (OFDM: Orthogonal Frequency Division Multiplexing) is used.
  • 'Enabling' transform precoding may mean that transform precoding is applied.
  • Disabling transform precoding may mean that transform precoding is not applied.
  • the terminal device 1 makes the transform precoding'valid 'or'invalid' based on the upper layer parameter msg3-transformPrecoding. May be regarded as either of The base station device 3 uses the upper layer parameter msg3-transformPrecoding to indicate to the terminal device 1 whether transform precoding is applied to Msg3 PUSCH transmission (and / or Msg3 PUSCH retransmission). Good.
  • the terminal device 1 may regard the transform precoding as “valid”.
  • the terminal device 1 may use discrete Fourier transform spread OFDM for Msg3 PUSCH transmission.
  • the terminal device 1 may regard the transform precoding as "invalid”.
  • the terminal device 1 may consider the transform precoding to be “invalid”. That is, the terminal device 1 may use orthogonal frequency division multiplexing for Msg3 PUSCH transmission.
  • the upper layer parameter msg3-transformPrecoding may be indicated from SIB1 or information element RACH-ConfigCommon.
  • the following describes the first example of determining transform precoding for PUSCH scheduled by RAR UL grant in the non-contention based random access procedure.
  • the terminal device 1 transmits the trans Form precoding may be considered either'enabled 'or'disabled'.
  • the terminal device 1 may use the PUSCH (and / or its schedule) scheduled by the RAR UL grant when the upper layer parameter msg3-transformPrecoding is set to'valid '.
  • PUSCH re-transmission may be considered as'valid 'for transform precoding.
  • the terminal device 1 disables the transform precoding for the PUSCH (and / or the retransmission of the scheduled PUSCH) scheduled by the RAR UL grant if the upper layer parameter msg3-transformPrecoding does not exist. May be regarded as'.
  • retransmission of PUSCH scheduled by RAR UL grant may mean retransmission of transport block in PUSCH scheduled by RAR UL grant.
  • the retransmission may be scheduled by DCI format 0_0 (or DCI format 0_1) with a CRC that is scrambled by C-RNTI (or MCS-C-RNTI).
  • the DCI that schedules the retransmission may be DCI format 0_0 transmitted in CSS.
  • the DCI that schedules the retransmission may be DCI format 0_0 transmitted in USS.
  • the DCI that schedules the retransmission may be DCI format 0_1 transmitted in USS.
  • the DCI format 0_0 that schedules the retransmission may be transmitted in CSS and may not be transmitted in USS.
  • the DCI that schedules the retransmission is DCI format 0_0, and need not be DCI format 0_1.
  • the terminal device 1 may regard the transform precoding for the retransmission of the first PUSCH as either “valid” or “invalid” based on the parameter msg3-transformPrecoding of the upper layer. Moreover, if DCI format 0_1 (and / or DCI format 0_0 transmitted in USS) schedules the second PUSCH transmission, the terminal device 1 sets the upper layer parameter transformPrecoder included in PUSCH-Config.
  • the transform precoding for the second PUSCH transmission may be considered to be either “valid” or “invalid” according to the upper layer parameter transformPrecoder, or if the upper layer parameter transformPrecoder is not set. Further, the transform precoding for the second PUSCH transmission may be considered to be either “valid” or “invalid” according to the higher layer parameter msg3-transformPrecoder.
  • the second PUSCH transmission need not be a retransmission of the first PUSCH.
  • the terminal device 1 is configured so that, regardless of whether the random access procedure is the contention-based random access procedure or the non-contention-based random access procedure, the PUSCH (and / or its scheduled) scheduled by the RAR UL grant is used.
  • the transform precoding may be considered to be either'valid 'or'invalid' based on the higher layer parameter msg3-transformPrecoding.
  • the terminal device 1 transforms the PUSCH (and / or the retransmission of the scheduled PUSCH) scheduled by the RAR UL grant when the upper layer parameter msg3-transformPrecoding is set to'valid '.
  • Precoding may be considered'valid '.
  • the terminal device 1 disables the transform precoding for the PUSCH (and / or the retransmission of the scheduled PUSCH) scheduled by the RAR UL grant if the upper layer parameter msg3-transformPrecoding does not exist. May be regarded as'.
  • the terminal device 1 uses the transform precoding as'valid 'or based on the upper layer parameter msg3-transformPrecoding. It may be considered as "invalid". Also, the terminal device 1 is based on the DCI format and / or the search space for scheduling the first PUSCH for the PUSCH retransmission (first PUSCH retransmission) scheduled by the RAR UL grant. May determine whether transform precoding is applied.
  • the terminal device 1 is configured with the upper layer parameter transformPrecoder included in PUSCH-Config.
  • the transform precoding for the first PUSCH retransmission may be considered as either “valid” or “invalid”, and the upper layer parameter transformPrecoder may be If not set, the transform precoding for the first PUSCH retransmission may be considered to be either'valid 'or'invalid' according to the higher layer parameter msg3-transformPrecoder.
  • the terminal device 1 uses the first layer parameter msg3-transformPrecoding based on the first layer. Transform precoding may be considered to be either'valid 'or'invalid' for the PUSCH retransmissions.
  • the terminal device 1 follows the RAR UL according to the upper layer parameter transformPrecoder.
  • Transform precoding for a PUSCH (or retransmission of that PUSCH) scheduled by a grant may be considered either'valid 'or'invalid'.
  • the terminal device 1 may regard the transform precoding as “enabled”. That is, the terminal device 1 may use the discrete Fourier transform spread OFDM for the PUSCH transmission.
  • the terminal device 1 may regard the transform precoding as “invalid”. If the upper layer parameter transformPrecoding is not set (does not exist), the terminal device 1 may regard the transform precoding for PUSCH transmission as'invalid '. That is, the terminal device 1 may use orthogonal frequency division multiplexing for the PUSCH transmission.
  • the terminal device 1 follows the RAR according to the upper layer parameter msg3-transformPrecoder.
  • Transform precoding for PUSCH (or retransmission of that PUSCH) scheduled by UL grant may be considered as either'valid 'or'invalid'. That is, when the upper layer parameter msg3-transformPrecoding is set to "valid" (set), the terminal device 1 may regard the transform precoding for PUSCH transmission as "valid". That is, the terminal device 1 may perform the PUSCH transmission using the discrete Fourier transform spread OFDM.
  • the terminal device 1 may regard the transform precoding for PUSCH transmission as “invalid”.
  • the terminal device 1 may regard the transform precoding for PUSCH transmission as'invalid '. That is, the terminal device 1 may perform the PUSCH transmission using orthogonal frequency division multiplexing.
  • Retransmission of message 3 is scheduled by DCI format 0_0 with a CRC parity bit scrambled by TC-RNTI included in the RAR message. That is, the PUSCH retransmission of the transport block transmitted on the PUSCH corresponding to the RAR UL grant included in the RAR message is scheduled by the DCI format 0_0 to which the CRC parity bit scrambled by TC-RNTI is added.
  • the DCI format 0_0 is transmitted on the PDCCH of the type 1 PDCCH common search space set. That is, the terminal device 1 may monitor the DCI format 0_0 that schedules the retransmission of the message 3 after transmitting the message 3 in S803. When the terminal device 1 detects the DCI format 0_0 which schedules the retransmission of the message 3 in S803a, S803b is executed.
  • the DCI format 0_0 which schedules the retransmission of message 3, contains a frequency domain resource assignment field.
  • the bits of the field are given based on the initial UL BWP. Specifically, the number of bits in the field is calculated by (Equation 4) Ceiling (log 2 (N UL, BWP RB (N UL, BWP RB +1) / 2)).
  • N UL, BWP RB is the number of resource blocks indicating the bandwidth of the initial UL BWP. That is, no matter which UL BWP is set for the terminal device 1, which UL BWP is used to schedule the resource for the retransmission of the message 3, the number of bits of the frequency domain resource assignment field is set. Becomes a fixed value (same value) based on the bandwidth of the initial UL BWP.
  • N UL, BWP RB may be provided based on the type of random access procedure.
  • N UL, BWP RB is the number of resource blocks indicating the bandwidth of the initial UL BWP.
  • N UL, BWP RB is the number of resource blocks indicating the bandwidth of the active UL BWP.
  • the terminal device 1 needs to interpret the bits of the frequency domain resource assignment field based on the initial UL BWP in order to adapt to the bandwidth of the UL BWP to which the frequency domain resource assignment (frequency domain resource assignment field) is applied. There is. As described above, the terminal device 1 determines the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied when truncating or inserting a bit in the Msg3 PUSCH frequency resource assignment.
  • the UL BWP to which the frequency domain resource assignment field included in DCI format 0_0 is applied may be determined by the same determination method as the UL BWP to which the PUSCH frequency resource assignment is applied, as described above.
  • the UL BWP to which the frequency domain resource assignment included in the DCI format 0_0 is applied may be the UL BWP to which the PUSCH frequency resource assignment is applied. That is, the terminal device 1 may specify the resource block allocation in the frequency direction of PUSCH to the UL BWP to which the PUSCH frequency resource assignment is applied, based on the value of RIV indicated in the frequency domain resource assignment field.
  • the UL BWP to which the PUSCH frequency resource assignment is applied is the initial UL BWP (or the initial active UL BWP)
  • the UL BWP to which the frequency domain resource assignment field included in the DCI format 0_0 is applied is the initial UL BWP. It is UL BWP.
  • the base station device 3 uses the size of the initial UL BWP to which the resource assignment is applied to generate the RIV, determines the bit string to be included in the field of the frequency resource assignment, and transmits the bit string to the terminal device 1.
  • the terminal device 1 irrespective of which UL BWP the UL BWP actually activated is, the terminal device 1 assigns the frequency of the PUSCH to the physical resource block of the UL BWP (initial UL BWP) to which the resource assignment is applied. Identify resource allocations for directions.
  • the terminal device 1 can specify the RB start and the L RBs corresponding to the physical resource block of the initial BWP by using FIG.
  • N size BWP in FIG. 12A is a resource block indicating the bandwidth of the initial UL BWP.
  • the value of RIV indicated in the frequency domain resource assignment field is given based on the size of the initial UL BWP to which the resource assignment is applied, and the RB start and L RBs corresponding to the resource block of the initial UL BWP.
  • the RB start is the number of resource blocks indicating the start position of resource allocation with reference to the physical resource block index 0 of the initial BWP UL.
  • L RBs cannot exceed the number of resource blocks indicating the bandwidth of the initial UL BWP. That is, the numbering of the resources indicated in the frequency domain resource assignment field starts from the smallest number of physical resource blocks of the initial UL BWP.
  • ⁇ Message 4 (S804)> In order to respond to the PUSCH transmission of message 3 (Msg3), the terminal device 1 not indicated by the C-RNTI monitors the DCI format 1_0 that schedules the PDSCH including the UE contention resolution identity. Here, a CRC parity bit scrambled by the corresponding TC-RNTI is added to this DCI format 1_0. In order to respond to the PDSCH reception with the UE collision resolution identity, the terminal device 1 sends HARQ-ACK information on the PUCCH. The transmission of the PUCCH may be performed by the active UL BWP to which the message 3 (Msg 3) is transmitted.
  • the terminal device 1 performing the random access procedure can perform uplink data transmission to the base station device 3.
  • FIG. 15 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment.
  • the terminal device 1 is configured to include a wireless transmission / reception unit 10 and an upper layer processing unit 14.
  • the wireless transmission / reception unit 10 includes an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13.
  • the upper layer processing unit 14 includes a medium access control layer processing unit 15 and a radio resource control layer processing unit 16.
  • the wireless transceiver 10 is also referred to as a transmitter, a receiver, a monitor, or a physical layer processor.
  • the upper layer processing unit 14 is also referred to as a measurement unit, a selection unit or a control unit 14.
  • the upper layer processing unit 14 outputs the uplink data (which may be referred to as a transport block) generated by a user's operation or the like to the wireless transmission / reception unit 10.
  • the upper layer processing unit 14 is a medium access control (MAC: Medium Access Control) layer, a packet data integration protocol (Packet Data Convergence Protocol: PDCP) layer, a radio link control (Radio Link Control: RLC) layer, a radio resource control (Radio). Resource Control: RRC) Performs part or all of the layer.
  • the upper layer processing unit 14 may have a function of selecting one reference signal from one or a plurality of reference signals based on the measurement value of each reference signal.
  • the upper layer processing unit 14 may have a function of selecting a PRACH opportunity associated with one selected reference signal from one or a plurality of PRACH opportunities.
  • the upper layer processing unit 14 sets 1 set in the upper layer (for example, the RRC layer) when the bit information included in the information instructing the start of the random access procedure received by the wireless transmission / reception unit 10 has a predetermined value. It may have a function of specifying one index from one or a plurality of indexes and setting it as a preamble index.
  • the upper layer processing unit 14 may have a function of identifying an index associated with the selected reference signal from among one or more indexes set by 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 (eg, 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 (eg, SSB index information).
  • the medium access control layer processing unit 15 included in the upper layer processing unit 14 performs processing of the MAC layer (medium access control layer).
  • the medium access control layer processing unit 15 controls transmission of a scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 16.
  • the radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer (radio resource control layer).
  • the radio resource control layer processing unit 16 manages various setting information / parameters of its own device.
  • the radio resource control layer processing unit 16 sets various setting information / parameters based on 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 (specifies) resource allocation based on the downlink control information received from the base station device 3.
  • the wireless transmission / reception unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding.
  • the wireless transmission / reception unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14.
  • the wireless transmission / reception unit 10 generates a transmission signal by modulating and encoding data and transmits it to the base station device 3.
  • the wireless transmission / reception unit 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 identifies one or more PRACH opportunities.
  • the wireless transmission / reception unit 10 may have a function of receiving a signal including instruction information for instructing the start of the random access procedure.
  • the wireless transmission / reception unit 10 may have a function of receiving information that receives information that specifies a predetermined index.
  • the wireless transmission / reception unit 10 may have a function of receiving information that specifies an index of random access printing.
  • the wireless transmission / reception unit 10 may have a function of transmitting the random access preamble at the PRACH opportunity determined by the upper layer processing unit 14.
  • the RF unit 12 converts a signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (down conversion: downcovert) and removes unnecessary frequency components.
  • the RF unit 12 outputs the processed analog signal to the baseband unit.
  • 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 CP (Cyclic Prefix) from the converted digital signal, performs a fast Fourier transform (FFT) on the signal from which the CP is removed, and outputs a signal in the frequency domain. Extract.
  • CP Cyclic Prefix
  • FFT fast Fourier transform
  • the baseband unit 13 performs an Inverse Fast Fourier Transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, and generates a baseband digital signal to generate a baseband signal. Converts band digital signals to analog signals. The baseband unit 13 outputs the converted analog signal to the RF unit 12.
  • IFFT Inverse Fast Fourier Transform
  • the RF unit 12 uses a low-pass filter to remove excess 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. To do. Further, the RF unit 12 amplifies the power. Further, the RF unit 12 may have a function of determining the transmission power of the uplink signal and / or the uplink channel transmitted in the serving cell.
  • the RF unit 12 is also referred to as a transmission power control unit.
  • FIG. 16 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment.
  • the base station device 3 is configured to include a wireless transmission / reception unit 30 and an upper layer processing unit 34.
  • the wireless transmission / reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33.
  • the upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36.
  • the wireless transceiver 30 is also referred to as a transmitter, a receiver, a monitor, or a physical layer processor.
  • a control unit that controls the operation of each unit based on various conditions may be separately provided.
  • the upper layer processing unit 34 is also referred to as the control unit 34.
  • the upper layer processing unit 34 includes a medium access control (MAC: Medium Access Control) layer, a packet data integration protocol (Packet Data Convergence Protocol: PDCP) layer, a radio link control (Radio Link Control: RLC) layer, and a radio resource control (Radio). Resource Control: RRC) Performs part or all of the layer.
  • the upper layer processing unit 34 may have a function of identifying one reference signal from one or a plurality of reference signals based on the random access preamble received by the wireless transmission / reception unit 30.
  • the upper layer processing unit 34 may specify the PRACH opportunity to monitor the random access preamble from at least the SSB index information and the mask index information.
  • the medium access control layer processing unit 35 included in the upper layer processing unit 34 performs processing of the MAC layer.
  • the medium access control layer processing unit 35 performs processing relating to the scheduling request based on various setting information / parameters managed by the wireless resource control layer processing unit 36.
  • a radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs processing of the RRC layer.
  • the radio resource control layer processing unit 36 generates downlink control information (uplink grant, downlink grant) including resource allocation information for the terminal device 1.
  • the radio resource control layer processing unit 36 receives downlink control information, downlink data (transport block, random access response) arranged on the physical downlink shared channel, system information, RRC message, MAC CE (Control Element), etc. It is generated or acquired from an upper node and output to the wireless transmission / reception unit 30. Further, the radio resource control layer processing unit 36 manages various setting information / parameters of each terminal device 1.
  • the radio resource control layer processing unit 36 may set various setting information / parameters for each terminal device 1 via a signal of an upper layer. That is, the radio resource control layer processing unit 36 transmits / notifies information indicating various setting information / parameters.
  • the radio resource control layer processing unit 36 may transmit / notify information for specifying the setting of one or more reference signals in a certain cell.
  • the base station device 3 When an RRC message, a MAC CE, and / or a PDCCH are transmitted 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 performs the processing.
  • the processing (control of the terminal device 1 and the system) is performed assuming that it is being performed. That is, the base station device 3 sends the terminal device 1 an RRC message, a MAC CE, and / or a PDCCH that causes the terminal device to perform processing based on the reception.
  • the wireless transmission / reception unit 30 has a function of transmitting one or more reference signals. Further, the wireless transmission / reception unit 30 may have a function of receiving a signal including the beam failure recovery request transmitted from the terminal device 1.
  • the wireless transmission / reception unit 30 may have a function of transmitting information (for example, SSB index information and / or mask index information) specifying one or more PRACH opportunities to the terminal device 1.
  • the wireless transmission / reception unit 30 may have a function of transmitting information specifying a predetermined index.
  • the wireless transmission / reception unit 30 may have a function of transmitting information specifying the index of the random access preamble.
  • the wireless transmission / reception unit 30 may have a function of monitoring the random access preamble at the PRACH opportunity specified by the upper layer processing unit 34.
  • a part of the function of the wireless transmission / reception unit 30 is the same as that of the wireless transmission / reception unit 10, and thus the description thereof is omitted.
  • the base station device 3 is connected to one or more transmission / reception points 4, some or all of the functions of the wireless transmission / reception unit 30 may be included in each transmission / reception point 4.
  • the upper layer processing unit 34 transmits (transfers) a control message or user data between the base station devices 3 or between the base network devices 3 (MME, S-GW (Serving-GW)) and the base station device 3. ) Or receive.
  • MME base network devices 3
  • S-GW Serving-GW
  • the upper layer processing unit 34 includes a radio resource management (Radio Resource Management) layer processing unit and an application layer processing unit.
  • the upper layer processing unit 34 may have a function of setting a plurality of scheduling request resources corresponding to each of a plurality of reference signals transmitted from the wireless transmission / reception unit 30.
  • Parts in the figure are elements that realize the functions and procedures of the terminal device 1 and the base station device 3, which are also expressed by terms such as sections, circuits, constituent devices, devices, and units.
  • Each of the units 10 to 16 provided in the terminal device 1 may be configured as a circuit.
  • Each of the units denoted by reference numerals 30 to 36 included in the base station device 3 may be configured as a circuit.
  • the terminal device 1 includes a receiving unit 10 that receives a first parameter of an upper layer and receives a PDSCH including a RAR message, and the RAR message.
  • FIG. 3 shows a set including one or more frequency offset values, wherein the PUSCH with frequency hopping consists of a first frequency hop and a second frequency hop in one slot, and in a contention-based random access procedure, The frequency offset between the first frequency hop and the second frequency hop is the first frequency hop. Given on the basis of the parameter, the contention based random access procedure, the frequency offset between the first frequency hop and the second frequency hops is given based on the size of the initial UL BWP.
  • the base station device 3 transmits the first parameter of the upper layer and transmits the PDSCH including the RAR message, and the first portion included in the RAR message.
  • the PUSCH with frequency hopping comprises a first frequency hop and a second frequency hop within a slot, the set including the frequency offset values, and the first frequency hop in a non-contention based random access procedure.
  • the frequency offset between the hop and the second frequency hop is in the first parameter. Given Hazuki, the contention based random access procedure, the frequency offset between the first frequency hop and the second frequency hops is given based on the size of the initial UL BWP.
  • the terminal device 1 receives the first parameter of the upper layer and receives the PDCCH including the DCI format, and the frequency hopping scheduled by the DCI format.
  • the frequency offset between the two frequency hops is the size of the initial UL BWP
  • the DCI format if it is scrambled by RNTI except TC-RNTI, the frequency offset between the first frequency hop and the second frequency hops is given based on the first parameter.
  • the DCI format may be DCI format 0_0.
  • the base station device 3 transmits the first parameter of the upper layer and transmits the PDCCH including the DCI format, and the frequency hopping scheduled by the DCI format.
  • the PUSCH with frequency hopping consists of a first frequency hop and a second frequency hop in one slot, and if the DCI format is scrambled by TC-RNTI, then the first frequency hop and the The frequency offset between the second frequency hops is the size of the initial UL BWP Given based on, when the DCI format is scrambled by RNTI except TC-RNTI, the frequency offset between the first frequency hop said second frequency hops is given based on the first parameter.
  • the DCI format may be DCI format 0_0.
  • the RNTI other than TC-RNTI may be either C-RNTI, CS-RNTI, or MCS-C-RNTI.
  • the terminal device 1 includes the receiving unit 10 that receives the first parameter and the second parameter of the upper layer and receives the PDSCH including the RAR message, and the receiving unit 10 that is included in the RAR message. And a transmitter 10 for transmitting a PUSCH scheduled by a first UL grant, the first parameter for enabling transform precoding for the PUSCH in a contention based random access procedure.
  • the second parameter is used to indicate UE-specific selection of transform precoding for PUSCH, and in a non-contention based random access procedure, transform precoding for PUSCH transmission is
  • the second parameter is set , "Valid” or "invalid” based on the second parameter, and if the second parameter is not set, either "valid” or “invalid” based on the first parameter. It is set to crab.
  • the base station device 3 in the sixth aspect of the present invention transmits the first parameter and the second parameter of the upper layer, and transmits the PDSCH including the RAR message, and the RAR message.
  • the second parameter is used to indicate a UE-specific selection of transform precoding for PUSCH, and in a non-contention based random access procedure, transform precoding for PUSCH transmission is ,
  • the second parameter is set If the second parameter is set to either'valid 'or'invalid' according to the second parameter and the second parameter is not set, 'valid' or'invalid 'is determined according to the first parameter. It is set to either.
  • the transform precoding for PUSCH transmission is'invalid '.
  • the terminal device 1 can efficiently communicate with the base station device 3.
  • the program running on the device related to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to cause a computer to function so as to realize the functions of the embodiments related to the present invention.
  • the program or information handled by the program is temporarily stored in a volatile memory such as Random Access Memory (RAM) or a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage device system.
  • RAM Random Access Memory
  • HDD Hard Disk Drive
  • the program for implementing the functions of the embodiments according to the present invention may be recorded in a computer-readable recording medium. It may be realized by causing a computer system to read and execute the program recorded in this recording medium.
  • the “computer system” is a computer system built in the device, and includes an operating system and hardware such as peripheral devices.
  • the "computer-readable recording medium” is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another computer-readable recording medium. Is also good.
  • Each functional block or various features of the device used in the above-described embodiment may be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits.
  • An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other Logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof.
  • a general purpose processor may be a microprocessor, or may be a conventional processor, controller, microcontroller, or state machine.
  • the above-described electric circuit may be constituted by a digital circuit or may be constituted by an analog circuit.
  • one or more aspects of the present invention can use a new integrated circuit based on the technology.
  • the present invention is not limited to the above embodiment.
  • an example of the device is described.
  • the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, for example, AV devices, kitchen devices, It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention permet une communication efficace entre le dispositif terminal et le dispositif de station de base. Ce dispositif terminal est destiné à effectuer une procédure d'accès aléatoire et comprend : une unité de réception qui reçoit un premier paramètre d'une couche supérieure et reçoit un PDSCH comprenant un message RAR; et une unité de transmission qui transmet un PUSCH programmé sur la base d'un premier octroi UL inclus dans le message RAR, dans lequel le premier paramètre est utilisé pour valider le précodage de transformation, et le précodage de transformation pour la transmission PUSCH est réglé sur "valide" ou "invalide" sur la base du premier paramètre, que la procédure d'accès aléatoire soit une procédure d'accès aléatoire de base concurrentielle ou une procédure d'accès aléatoire de base non concurrentielle.
PCT/JP2019/039893 2018-10-10 2019-10-09 Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré WO2020075775A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2018191530A JP2020061649A (ja) 2018-10-10 2018-10-10 基地局装置、端末装置、通信方法、および、集積回路
JP2018-191530 2018-10-10

Publications (1)

Publication Number Publication Date
WO2020075775A1 true WO2020075775A1 (fr) 2020-04-16

Family

ID=70164552

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/039893 WO2020075775A1 (fr) 2018-10-10 2019-10-09 Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré

Country Status (2)

Country Link
JP (1) JP2020061649A (fr)
WO (1) WO2020075775A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210400654A1 (en) * 2020-06-18 2021-12-23 Qualcomm Incorporated Coreset and search space association with resource bandwidth
WO2023054172A1 (fr) * 2021-09-29 2023-04-06 シャープ株式会社 Dispositif terminal, dispositif de station de base et procédé de communication

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7481455B2 (ja) * 2020-08-03 2024-05-10 株式会社Ｎｔｔドコモ 端末、無線通信方法、基地局及びシステム

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Maintenance issues of DL/UL data scheduling and HARQ procedure", 3GPP TSG RAN WG1 #94 R1-1809407, 20 August 2018 (2018-08-20), XP051516770, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_94/Docs/R1-1809407.zip> *
NTT DOCOMO, INC.: "Offline summary for UL data transmission procedure", 3GPP TSG RAN WG1 #94 R1-1809767, 22 August 2018 (2018-08-22), XP051517128, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WGlRL1/TSGR1_94/Docs/R1-1809767.zip> *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210400654A1 (en) * 2020-06-18 2021-12-23 Qualcomm Incorporated Coreset and search space association with resource bandwidth
US11723028B2 (en) * 2020-06-18 2023-08-08 Qualcomm Incorporated Coreset and search space association with resource bandwidth
WO2023054172A1 (fr) * 2021-09-29 2023-04-06 シャープ株式会社 Dispositif terminal, dispositif de station de base et procédé de communication

Also Published As

Publication number Publication date
JP2020061649A (ja) 2020-04-16

Similar Documents

Publication Publication Date Title
JP7197297B2 (ja) 基地局装置、端末装置、および、通信方法
JP7271097B2 (ja) 基地局装置、端末装置、および、通信方法
JP7286288B2 (ja) 基地局装置、端末装置、通信方法、および、集積回路
WO2020017391A1 (fr) Dispositif station de base, dispositif terminal, procédé de communication, et circuit intégré
WO2020166624A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré
WO2020166625A1 (fr) Procédé de communication, dispositif terminal, dispositif de station de base, et circuit intégré
WO2020170972A1 (fr) Dispositif de station de base, dispositif de terminal, procédé de communication, et circuit intégré
JP7240843B2 (ja) 基地局装置、端末装置、通信方法、および、集積回路
WO2020031588A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication et circuit intégré
JP2020136759A (ja) 基地局装置、端末装置、通信方法、および、集積回路
WO2020218254A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication et circuit intégré
WO2020075775A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré
WO2020091046A1 (fr) Dispositif de station de base, dispositif terminal, et procédé de communication
WO2019244861A1 (fr) Dispositif terminal, procédé de communication, et circuit intégré
WO2020066854A1 (fr) Appareil de station de base, dispositif terminal, procédé de communication, et circuit intégré
WO2020195531A1 (fr) Dispositif de station de base, dispositif terminal et procédé de communication
JP2020162018A (ja) 基地局装置、端末装置、通信方法、および、集積回路

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19871895

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19871895

Country of ref document: EP

Kind code of ref document: A1