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

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

Info

Publication number
WO2020170972A1
WO2020170972A1 PCT/JP2020/005824 JP2020005824W WO2020170972A1 WO 2020170972 A1 WO2020170972 A1 WO 2020170972A1 JP 2020005824 W JP2020005824 W JP 2020005824W WO 2020170972 A1 WO2020170972 A1 WO 2020170972A1
Authority
WO
WIPO (PCT)
Prior art keywords
parameter
pusch
terminal device
resource allocation
random access
Prior art date
Application number
PCT/JP2020/005824
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 WO2020170972A1 publication Critical patent/WO2020170972A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • 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
    • 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. 2019-30647 filed in Japan on February 22, 2019, the content of which is 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
  • 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.
  • a terminal device performing a random access procedure receives a first parameter and a second parameter of an upper layer, receives a PDCCH including DCI, and is scheduled by the DCI.
  • a transmission unit for transmitting PUSCH is predefined by a default table, and the first parameter, the second parameter and the third parameter are in the PUSCH time domain.
  • the first parameter and the third parameter can be recognized regardless of whether the second parameter is received. One of them is selected, and the PUSCH time domain resource allocation is given based on the selected parameters.
  • the base station apparatus that communicates with the terminal apparatus that performs the random access procedure according to an aspect of the present invention transmits the upper layer first parameter and the second parameter, and transmits the PDCCH including the DCI.
  • a receiver for receiving a PUSCH scheduled by the DCI the third parameter being predefined by a default table, the first parameter, the second parameter, and the The third parameter indicates information of PUSCH time domain resource allocation, and when the CRC scrambled by TC-RNTI is added to the DCI, the first parameter is irrespective of whether the second parameter is received or not. , And the third parameter is selected, and the PUSCH time domain resource allocation is given based on the selected parameter.
  • a communication method is a communication method for a terminal device that performs a random access procedure, and receives a first parameter and a second parameter of an upper layer and obtains a PDCCH including DCI.
  • One of the one parameter and the third parameter is selected, and the PUSCH time domain resource allocation is given based on the selected parameter.
  • a communication method is a communication method of a base station device that communicates with a terminal device that performs a random access procedure, and transmits a first parameter and a second parameter of an upper layer. , Transmitting a PDCCH containing the DCI and receiving a PUSCH scheduled by the DCI, the third parameter being predefined by a default table, the first parameter, the first parameter The second parameter and the third parameter indicate information of PUSCH time domain resource allocation, and whether or not the second parameter is received when a CRC scrambled by TC-RNTI is added to the DCI. Regardless, one is selected from the first parameter and the third parameter, and the PUSCH time domain resource allocation is given based on the selected parameter.
  • 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 PDSCH mapping type which concerns on embodiment of this invention.
  • 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 ( Also referred to as 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 more 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 transmission/reception 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.
  • 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 Division Multiplexing
  • a universal filter multi-carrier (UFMC), 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.
  • the OFDM symbol is used as the transmission method for explanation, but the case of using the above-mentioned other transmission method 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 when or after the RRC (Radio Resource Control) connection is established.
  • 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.
  • the TDD (Time Division Duplex) and/or the FDD (Frequency Division Duplex) may be applied to the wireless communication system of the present embodiment.
  • the TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of the plurality of cells. Further, 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
  • PRACH Physical Random Access CHannel
  • 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 parameter), it is set within a predetermined cycle or 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 wireless communication (wireless 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 PDCCH candidates.
  • 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 For example, the following DCI format may be defined.
  • the DCI format 0_0 may be used for PUSCH scheduling in a serving cell.
  • the DCI format 0_0 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation).
  • a CRC scrambled by any of C-RNTI, CS-RNTI, MCS-C-RNTI, and/or TC-RNTI may be added.
  • 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 serving cell.
  • the 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.
  • a CRC scrambled by any of C-RNTI, CS-RNTI, SP (Semi Persistent)-CSI-RNTI, and/or MCS-C-RNTI of RNTI may be added. ..
  • 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, among the identifiers, C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI)-RNTI, Random Access (RA)-RNTI, and/or , TC-RNTI, a scrambled CRC may be added.
  • DCI format 1_0 may be monitored in the common search space or the UE-specific search space.
  • DCI format 1_1 may be used for PDSCH scheduling in a serving cell.
  • DCI format 1_1 is information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), band portion (BWP) information, transmission configuration indication (TCI: Transmission Configuration Indication), and/or antenna port. Information may be included.
  • a CRC scrambled by any of C-RNTI, CS-RNTI, and/or MCS-C-RNTI of RNTI may be added.
  • 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 slot format is 28
  • the DDDDDDDDDDDDFU 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. This information may be referred to as a preemption instruction (intermittent transmission instruction).
  • 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. Further, 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 PUSCH and PUCCH, or for the uplink in which the transmission power control of SRS is not tied to the transmission power control of PUSCH.
  • SRS sounding reference signal
  • DCI for the downlink is also referred to as downlink grant or downlink assignment.
  • the DCI for the uplink is also referred to as an uplink grant or an uplink assignment.
  • DCI may also be referred to as DCI format.
  • 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.
  • 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 determines the resource allocation of the PDSCH to the terminal device 1, generates the'Time domain resource assignment' field of the value based on the determined resource allocation, and the DCI including the'Time domain resource assignment' field. Is transmitted to the terminal device 1.
  • the terminal device 1 identifies the resource allocation in the time direction of PDSCH based on the value of the'Time domain resource assignment' field.
  • the resource allocation table set by the RRC signal of the upper layer is given by the signal pdsch-TimeDomainAllocationList of the upper layer.
  • the pdsch-TimeDomainAllocationList includes one or more information elements PDSCH-TimeDomainResourceAllocation.
  • PDSCH-TimeDomainResourceAllocation indicates the setting of PDSCH time domain resource allocation.
  • PDSCH-TimeDomainResourceAllocation may be used to set a time domain relationship between the PDCCH including the DCI and the PDSCH. That is, pdsch-TimeDomainAllocationList is a list containing one or more information elements.
  • One PDSCH-TimeDomainResourceAllocation may be referred to as one entry (or one row).
  • the upper layer signal pdsch-TimeDomainAllocationList may be included in pdsch-ConfigCommon and/or pdsch-Config.
  • the information element pdsch-ConfigCommon is used to set the cell-specific parameters for PDSCH for a certain BWP.
  • Information element pdsch-Config is used to set UE specific parameters for PDSCH for a certain BWP.
  • FIG. 14 is a diagram showing an example of calculating SLIV.
  • FIG. 14 is the number of symbols included in one slot.
  • FIG. 14 shows an example of calculating SLIV in the case of NCP (Normal Cyclic Prefix).
  • the value of SLIV is calculated based on the number of symbols included in the slot, the start symbol S, and the number L of consecutive symbols.
  • the value of L is equal to or greater than 1 and does not exceed (14-S).
  • 6 and 12 are used instead of the values 7 and 14 in FIG.
  • the terminal device 1 detects the PDCCH (701) including DCI in the slot n. If K 0 is 0, the slot assigned to the PDSCH scheduled by that DCI (701) is given as slot 2n based on (Equation 1). In this case, the PDSCH scheduled by the DCI (701) is the PDSCH (705) in the slot 2n corresponding to the subcarrier interval of 30 kHz.
  • the slot assigned to the PDSCH scheduled by that DCI (701) is given as slot 2n+1 based on (Equation 1).
  • the PDSCH scheduled by the DCI (701) is the PDSCH (706) in slot 2n+1 corresponding to the subcarrier interval of 30 kHz.
  • the slot assigned to the PDSCH scheduled by that DCI (704) is given as slot n+1 based on (Equation 1).
  • the PDSCH scheduled by that DCI (704) is the PDSCH (703) in slot n+1 corresponding to the subcarrier interval of 15 kHz.
  • the terminal device 1 may determine which one of the resource allocation tables is applied to PDSCH time domain resource allocation with reference to FIG. 10. That is, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH scheduled by DCI based on at least some or all of the following elements (A) to (F).
  • the type of search space in which DCI is detected is a common search space or a UE-specific search space.
  • the common search space includes a type 0 common search space, a type 1 common search space, and a type 2 common search space.
  • the terminal device 1 may determine the default table A. That is, the terminal device 1 may apply the determination of PDSCH time domain resource allocation using the default table A indicating the configuration of PDSCH time domain resource allocation.
  • the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by pdsch-Config regardless of whether or not pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList. It may be applied to the determination of area resource allocation.
  • pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList
  • the terminal device 1 uses the pdsch-ConfigCommon resource allocation table to apply PDSCH time domain resource allocation.
  • the terminal device 1 may detect the DCI in the UE-specific search space. A CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI is added to the detected DCI. Then, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH scheduled by the DCI. When pdsch-Config includes pdsch-TimeDomainAllocationList for the terminal device 1, the terminal device 1 assigns the resource allocation table applied to the PDSCH time domain resource allocation to the resource allocation given from the pdsch-TimeDomainAllocationList provided in pdsch-Config. You may decide on the table.
  • the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by pdsch-Config regardless of whether or not pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList. It may be applied to the determination of area resource allocation.
  • pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList
  • the terminal device 1 uses the pdsch-ConfigCommon resource allocation table to apply PDSCH time domain resource allocation.
  • the terminal device 1 is scheduled by its DCI using the PDSCH time domain resource allocation configuration of the row index 1 of the default table A.
  • the resource allocation of the PDSCH in the time direction is specified.
  • the value m indicated in the'Time domain resource allocation' field is (m+1)th in the list pdsch-TimeDomainAllocationList.
  • the terminal device 1 may refer to the first element (entry) in the list pdsch-TimeDomainAllocationList.
  • the terminal device 1 may refer to the second element (entry) in the list pdsch-TimeDomainAllocationList.
  • the meaning of “pdsch-Config includes pdsch-TimeDomainAllocationList” may mean that “pdsch-Config provides pdsch-TimeDomainAllocationList”.
  • the meaning of'pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList' may mean'provided by pdsch-TimeCommonAllocationList in pdsch-ConfigCommon'.
  • the number of bits in the'Time domain resource assignment' field may be given as ceiling(log 2 (I)).
  • the function Ceiling(A) outputs the smallest integer not less than A.
  • the number of bits of the Time domain resource assignment' field may be given based on the number of entries included in pdsch-TimeDomainAllocationList.
  • the number of bits of the Time domain resource assignment' field may be given based on the number of rows of the default table (default table A).
  • the value of I may be the number of entries included in pdsch-TimeDomainAllocationList provided in pdsch-Config.
  • the value of I is the number of entries included in pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. May be. If pdsch-Config does not contain pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not contain pdsch-TimeDomainAllocationList, the value of I is the number of rows contained in the default table (eg default table A). May be.
  • the number of bits of the'Time domain resource assignment' field is given as ceiling(log 2 (I)). May be.
  • the number of bits of the'Time domain resource assignment' field may be a fixed number of bits.
  • the fixed number of bits may be 4 bits.
  • I may be the number of entries included in the pdsch-TimeDomainAllocationList.
  • the value of I may be the number of entries included in pdsch-TimeDomainAllocationList provided in pdsch-Config.
  • the value of I is the number of entries included in pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. May be.
  • the terminal device 1 can specify the number of bits of the'Time domain resource assignment' field generated by the base station device 3. That is, the terminal device 1 can correctly receive the PDSCH destined for the terminal device 1 scheduled by the base station device 3.
  • the terminal device 1 may transmit the corresponding PUSCH by detecting the DCI format 0_0 or the PDCCH including the DCI format 0_1. That is, the corresponding PUSCH may be scheduled (shown) by its DCI format (DCI). Further, the PUSCH may be scheduled by the RAR UL grant included in the RAR message.
  • the start position (start symbol) of the scheduled PUSCH is called S.
  • the starting symbol S of the PUSCH may be the first symbol in which the PUSCH is transmitted (mapped) in a certain slot.
  • the start symbol S corresponds to the start of the slot. For example, when the value of S is 0, the terminal device 1 may transmit the PUSCH from the first symbol in a certain slot.
  • the terminal device 1 may transmit the PUSCH from the third symbol of a certain slot.
  • the number of consecutive symbols of the scheduled PUSCH is called L.
  • the number L of consecutive symbols is counted from the start symbol S. The determination of S and L assigned to PUSCH will be described later.
  • PUSCH mapping types have PUSCH mapping type A and PUSCH mapping type B.
  • PUSCH mapping type A the value of S is 0.
  • L takes a value from 4 to 14.
  • the sum of S and L takes values from 4 to 14.
  • PUSCH mapping type B S takes values from 0 to 13.
  • L takes a value from 1 to 14.
  • the sum of S and L takes values from 1 to 14.
  • the location of the DMRS symbol for PUSCH depends on the type of PUSCH mapping.
  • the position of the first DMRS symbol for PUSCH depends on the type of PUSCH mapping.
  • the position of the first DMRS symbol may be indicated in the upper layer parameter dmrs-TypeA-Position.
  • dmrs-TypeA-Position is set to either'pos2' or'pos3'. For example, if dmrs-TypeA-Position is set to'pos2', the position of the first DMRS symbol for PUSCH may be the third symbol in the slot.
  • the base station device 3 may schedule the terminal device 1 to transmit the PUSCH by DCI. Then, the terminal device 1 may transmit the PUSCH by detecting the DCI addressed to itself.
  • the terminal device 1 first determines the resource allocation table to be applied to the PUSCH.
  • the resource allocation table includes one or more PUSCH time domain resource allocation configurations. Next, the terminal device 1 may select one PUSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the'Time domain resource assignment' field included in the DCI that schedules the PUSCH. Good.
  • the base station device 3 determines the PUSCH resource allocation to the terminal device 1, generates the value of the'Time domain resource assignment' field, and transmits the DCI including the'Time domain resource assignment' field to the terminal device 1. To do.
  • the terminal device 1 identifies the resource allocation in the PUSCH time direction based on the value set in the'Time domain resource assignment' field.
  • FIG. 16 is a diagram defining a resource allocation table applied to PUSCH time domain resource allocation.
  • the terminal device 1 may determine the resource allocation table applied to PUSCH time domain resource allocation based on the table shown in FIG.
  • the resource allocation table includes configurations of one or more PUSCH time domain resource allocations.
  • the resource allocation table is classified into (I) a resource allocation table defined in advance and (II) a resource allocation table configured from an RRC signal of an upper layer.
  • the predefined resource allocation table is defined as the default PUSCH time domain resource allocation A.
  • the default PUSCH time domain resource allocation A will be referred to as the PUSCH default table A.
  • FIG. 17 is a diagram showing an example of the PUSCH default table A for NCP (Normal Cyclic Prefix).
  • PUSCH default table A includes 16 rows. Each row in the PUSCH default table A shows a PUSCH time domain resource allocation configuration.
  • the indexed row is a PUSCH mapping type, a slot offset K 2 between the PDCCH including DCI and the PUSCH, a start symbol S of the PUSCH in the slot, and The number of consecutively allocated symbols L is defined.
  • the resource allocation table set by the RRC signal of the upper layer is given by the signal push-TimeDomainAllocationList of the upper layer.
  • the information element PUSCH-TimeDomainResourceAllocation indicates the configuration of PUSCH time domain resource allocation.
  • PUSCH-TimeDomainResourceAllocation may be used to set the time domain relationship between the PDCCH including the DCI and the PUSCH.
  • the pusch-TimeDomainAllocationList contains one or more information elements PUSCH-TimeDomainResourceAllocation. That is, push-TimeDomainAllocationList is a list including one or more elements (information elements).
  • One information element PDSCH-TimeDomainResourceAllocation may also be referred to as one entry (or one row).
  • the pusch-TimeDomainAllocationList may contain up to 16 entries. Each entry may be defined by K 2 , mappingType, and startSymbolAndLength. K 2 indicates the slot offset between the PDCCH containing the DCI and its scheduled PUSCH. If PUSCH-TimeDomainResourceAllocation does not indicate K 2 , the terminal device 1 assumes that the value of K 2 is 1 when the PUSCH subcarrier interval is 15 kHz or 30 kHz, and the PUSCH subcarrier interval is If it is 60 kHz, it assumes that the value of K 2 is 2, when the sub-carrier interval of the PUSCH is 120 kHz, may be assumed that the value of K 2 is 3.
  • mappingType indicates either PUSCH mapping type A or PUSCH mapping type A.
  • startSymbolAndLength is an index that gives a valid combination of the start symbol S of PUSCH and the number of consecutively allocated symbols L.
  • the startSymbolAndLength may be referred to as a start and length indicator (SLIV). That is, unlike the default table that directly defines the start symbol S and the continuous symbol L, the start symbol S and the continuous symbol L are given based on SLIV.
  • the base station device 3 can set the value of SLIV so that the PUSCH time domain resource allocation does not exceed the slot boundary.
  • the value of SLIV is calculated based on the number of symbols included in the slot, the start symbol S, and the number L of consecutive symbols, as in the formula in FIG.
  • the upper layer signal push-TimeDomainAllocationList may be included in push-ConfigCommon and/or push-Config.
  • the information element push-ConfigCommon is used to set the cell-specific parameters for PUSCH for a certain BWP.
  • the information element push-Config is used to set UE specific parameters for PUSCH for a certain BWP.
  • the terminal device 1 detects DCI which schedules PUSCH.
  • the slot in which the PUSCH is transmitted is given by (Equation 4) Floor(n*2 ⁇ PUSCH /2 ⁇ PDCCH )+K 2 .
  • n is a slot in which the PDCCH that schedules the PUSCH is detected.
  • ⁇ PUSCH is a subcarrier interval setting for PUSCH .
  • ⁇ PDCCH is a subcarrier interval setting for PDCCH .
  • the value of K 2 is one of j, j+1, j+2, or j+3.
  • the value of j is a value specified for the PUSCH subcarrier spacing. For example, if the subcarrier spacing to which PUSCH is applied is 15 kHz or 30 kHz, the value of j may be 1 slot. For example, if the subcarrier spacing to which PUSCH is applied is 60 kHz, the value of j may be 2 slots. For example, if the subcarrier spacing to which PUSCH is applied is 120 kHz, the value of j may be 3 slots.
  • the terminal device 1 may determine which resource allocation table to apply to PUSCH time domain resource allocation based on the table shown in FIG.
  • the terminal device 1 may determine the resource allocation table to be applied to the PUSCH scheduled by the RAR UL grant (MAC RAR).
  • the terminal device 1 may determine the resource allocation table set by the RRC signal of the upper layer. The resource allocation table is given by push-TimeDomainAllocationList included in push-ConfigCommon.
  • the terminal device 1 may determine the PUSCH default table A. That is, the terminal device 1 may use the default table A indicating the configuration of PUSCH time domain resource allocation and apply it to the determination of PUSCH time domain resource allocation.
  • the terminal device 1 may detect a DCI (for example, DCI format 0_0) to which a CRC scrambled by TC-RNTI is added in the common search space (for example, type 1 common search space).
  • the terminal device 1 may determine the resource allocation table applied to the PUSCH scheduled by the DCI. That is, the terminal device 1 determines the resource allocation table applied to the PUSCH scheduled by the DCI, and based on the (m+1)th element (entry, row) in the determined resource allocation table, the time of the PUSCH Region resource allocation may be determined.
  • the terminal device 1 determines the resource allocation table to be applied to the PUSCH time domain resource allocation scheduled by DCI, if the CRC scrambled by TC-RNTI is added to the DCI, push- Regardless of whether or not the push-TimeDomainAllocationList included in Config is received (set), one may be selected from (I) push-TimeDomainAllocationList included in push-ConfigCommon and (II) PUSCH default table A.
  • the terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table. As described above, the value of m may be indicated in the'Time domain resource assignment' field included in the DCI.
  • Whether or not the push-TimeDomainAllocationList included in the push-Config is received may mean whether or not the push-Config includes the push-TimeDomainAllocationList.
  • the fact that push-TimeDomainAllocationList included in push-Config is not received may mean that push-Config is not received.
  • the fact that the push-TimeDomainAllocationList included in the push-Config is not received may mean that the push-Config is received, but the push-Config does not include the push-TimeDomainAllocationList.
  • the reception of the push-TimeDomainAllocationList included in the push-Config may mean that the push-Config is received and the received push-Config includes the push-TimeDomainAllocationList.
  • push-ConfigCommon when push-ConfigCommon includes push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 uses a push-ConfigCommon provided resource-assignment table that is applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from TimeDomainAllocationList. When push-ConfigCommon does not include push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 may determine the resource allocation table applied to the PUSCH time domain resource allocation as the PUSCH default table A.
  • the terminal device 1 determines the resource allocation table applied to the PUSCH time domain resource allocation scheduled by DCI, when the DCI is detected in the type 1 common search space b, Regardless of whether or not the push-TimeDomainAllocationList included in push-Config is received (set), even if one is selected from (I) push-TimeDomainAllocationList included in push-ConfigCommon and (II) PUSCH default table A Good.
  • the terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table.
  • the terminal device 1 may detect the DCI in an arbitrary common search space associated with CORESET#0.
  • a CRC scrambled by the first RNTI is added to the detected DCI.
  • the first RNTI may be any one of C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, and CS-RNTI.
  • the terminal device 1 determines the resource allocation table applied to the PUSCH time domain resource allocation scheduled by DCI, the CRC scrambled by the first RNTI is added to the DCI, and When the DCI is detected in an arbitrary common search space associated with CORESET#0, it is included in (I) push-ConfigCommon regardless of whether the push-TimeDomainAllocationList included in push-Config is received (set). One may be selected from pusch-TimeDomainAllocationList and (II) PUSCH default table A. The terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table.
  • push-ConfigCommon when push-ConfigCommon includes push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 uses a push-ConfigCommon provided resource-assignment table that is applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from TimeDomainAllocationList. If push-ConfigCommon does not include push-TimeDomainAllocationList, the terminal device 1 may determine the PUSCH default table A as the resource allocation table to be applied to PUSCH time domain resource allocation.
  • the terminal device 1 may detect the DCI in (i) an arbitrary common search space not associated with CORESET#0 or (ii) a UE-specific search space.
  • a CRC scrambled by the first RNTI is added to the detected DCI.
  • the first RNTI may be any one of C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, and CS-RNTI. Then, the terminal device 1 may determine the resource allocation table to be applied to the PUSCH scheduled by the DCI.
  • the terminal device 1 determines the resource allocation table applied to the PUSCH time domain resource allocation scheduled by DCI, the CRC scrambled by the first RNTI is added to the DCI, and If the DCI is detected in either (i) any common search space not associated with CORESET#0 or (ii) UE-specific search space, (I) push-TimeDomainAllocationList included in push-ConfigCommon, One may be selected from (II) PUSCH default table A and (III) push-TimeDomainAllocationList included in push-Config. The terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table.
  • push-Config when push-Config includes push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 uses the push-Config provided in push-Config as a resource allocation table applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from TimeDomainAllocationList. That is, when push-Config includes push-TimeDomainAllocationList, the terminal device 1 uses the push-TimeDomainAllocationList provided in push-Config regardless of whether push-ConfigCommon includes push-TimeDomainAllocationList. It may be applied to the determination of area resource allocation.
  • push-Config When push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon includes push-TimeDomainAllocationList, the terminal device 1 uses the push-ConfigCommon to assign the resource allocation table applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from the provided push-TimeDomainAllocationList. That is, the terminal device 1 uses the push-TimeDomainAllocationList provided by push-ConfigCommon to apply the PUSCH time domain resource allocation determination. If push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon does not include push-TimeDomainAllocationList, the terminal device 1 uses the PUSCH default table A as the resource allocation table applied to PUSCH time domain resource allocation. May be determined.
  • the terminal device 1 may select one PUSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the'Time domain resource assignment' field included in the DCI that schedules the PUSCH. Good.
  • the resource allocation table applied to PUSCH time domain resource allocation is the PUSCH default table A
  • the value m shown in the'Time domain resource allocation' field indicates the row index m+1 of the default table A.
  • the PUSCH time domain resource allocation is a configuration of the time domain resource allocation indicated by the row index m+1.
  • the terminal device 1 transmits the PUSCH assuming a configuration of time domain resource allocation indicated by the row index m+1.
  • the number of bits of the'Time domain resource assignment' field included in DCI format 0_1 is (I) whether pushch-ConfigCommon includes pushch-TimeDomainAllocationList and/or (II) whether pushch-Config includes pushch-TimeDomainAllocationList And/or (III) may be provided based at least on the number of rows included in the predefined default table.
  • the DCI format 0_1 is added with a CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI. DCI format 0_1 may be detected in the UE-specific search space.
  • push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon includes push-TimeDomainAllocationList
  • the value of I is the number of entries included in push-TimeDomainAllocationList provided by push-ConfigCommon. May be.
  • the terminal device 1 can specify the number of bits of the'Time domain resource assignment' field generated by the base station device 3. That is, the terminal device 1 can correctly transmit the PUSCH destined for the terminal device 1 scheduled by the base station device 3.
  • Random access procedures are classified into two procedures: contention-based (CB) and contention-free (non-CB) (may be referred to as contention free).
  • Contention-based random access is also called CBRA
  • non-contention-based random access is also called CFRA.
  • 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 a random access procedure.
  • the beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1, it is determined whether a certain condition is satisfied, and the procedure of 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.
  • the random access procedure for the beam failure recovery request and the scheduling request procedure are different from each other in the random access procedure started by the scheduling request procedure. Therefore, the random access procedure for the 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 is in the state of not being connected (communicating) with the base station device 3 at the time of initial access, and/or is being connected to the base station device 3, but is capable of transmitting 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 is generated.
  • the use of contention-based random access is not limited to these.
  • 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.
  • Generation of sidelink data that can be transmitted to the terminal device 1 may include that a scheduling request triggered based on generation 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 is performed quickly between the terminal device 1 and the base station device 3 when the base station device 3 and the terminal device 1 are connected but 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, and may also 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 identifying one downlink transmission beam (which may be, for example, an SSB index, a beam index, or a QCL setting index) may be included.
  • 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 index of the random access preamble is selected by the terminal device 1 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 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 a 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 does not detect the DCI format 1_0 to which the CRC scrambled by RA-RNTI is added 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.
  • the TC-RNTI is included in the received random access response.
  • the value of the TC-RNTI field is set, 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 PUSCH transmission (or RAR PUSCH) scheduling.
  • 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, the 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 called 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. Further, the Msg3 PUSCH may include the PUSCH scheduled by the RAR UL grant in the non-contention based 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).
  • 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.
  • the (Msg3) PUSCH frequency resource allocation' field is used to indicate frequency domain resource allocation for PUSCH transmission scheduled by RAR UL grant.
  • The'(Msg3)PUSCH time resource allocation' field is used to indicate the time domain resource allocation for the PUSCH scheduled by the RAR UL grant.
  • The'MCS' field is used to determine the MCS index for PUSCH scheduled by 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 the aperiodic CSI report is included in the PUSCH transmission.
  • the terminal device 1 performs PUSCH transmission scheduled by the RAR UL grant included in the RAR message received in S802.
  • the terminal device 1 performs PRACH transmission and PUSCH transmission scheduled by the RAR UL grant on the same uplink carrier of the same serving cell.
  • the PUSCH scheduled by the RAR UL grant is sent in the active UL BWP.
  • the subcarrier spacing for the PUSCH scheduled by the RAR UL grant may be indicated from the upper layer parameter SubcarrierSpacing or the upper layer parameter SubcarrierSpacing2 set for the UL BWP. In FDD, the upper layer parameter SubcarrierSpacing may be used to indicate the DL BWP subcarrier spacing.
  • the upper layer parameter SubcarrierSpacing2 may be used to indicate the UL BWP subcarrier spacing.
  • the upper layer parameter SubcarrierSpacing may be used to indicate the subcarrier spacing of NUL (Normal Uplink, Non-SUL) carriers.
  • the upper layer parameter SubcarrierSpacing2 may be used to indicate the subcarrier spacing of the serving cell of the SUL carrier.
  • 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 an index of PRACH opportunities 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 an SSB index corresponding to one of one or more SS/PBCH blocks transmitted by the base station device 3.
  • the terminal device 1 that has received the message 0 identifies 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) have state variable PREAMBLE_TRANSMISSION_COUNTER greater than 1 and (2) have not received a power ramp counter notification from the upper layer and (3) select 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 where 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 related to the reception of a random access response (random access response reception). Once the random access preamble is transmitted, 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 subheader (subheader) indicating RAPID and MAC RAR (MAC payload for Random Access Response)
  • the MAC sub PDU including only the 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 may be arranged anywhere between the padding and the MAC subPDU including only the Backoff Indicator.
  • the MAC RAR has a fixed size and consists of reserved bits (Reserved bits) that are set to 0, transmission timing adjustment information (TA command, Timing Advance Command), UL grant (UL grant, RAR UL grant), and TEMPORARY_C-RNTI. Has been done.
  • the RAR message may be a MAC RAR.
  • the RAR message may be a random access response.
  • 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 the random access procedure to have completed successfully.
  • End of operation A> When the random access preamble is selected by the MAC entity from the range of contention based random access preamble, the MAC entity sets TEMPORARY_C-RNTI to the value of the Temporary C-RNTI field included in the received random access response.
  • 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 terminal device 1 transmits the message 3 by PUSCH based on the UL grant.
  • 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 the UE contention resolution identity MAC CE and the UE collision resolution identity in the 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.
  • CCCH SDU 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 completed successfully.
  • the MAC entity discards TEMPORARY_C-RNTI when the UE collision resolution identity in the MAC CE does not match the CCCH SDU sent in Msg3, considers that the collision resolution is not successful, and decodes the successfully decoded MAC PDU. Discard.
  • 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.
  • FIG. 20 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 some or all of the layers.
  • 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 (for example, SSB index information).
  • 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 RF unit 12 uses a low-pass filter to remove excess frequency components from the analog signal input from the baseband unit 13, upconverts 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.
  • 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.
  • 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 a 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 the 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 the operation is being performed. That is, the base station device 3 sends to 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) identifying 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.
  • the wireless transmission/reception unit 30 is the same as that of the wireless transmission/reception unit 10, and the description thereof will be omitted. If the base station device 3 is connected to one or more transmission/reception points 4, some or all of the functions of the wireless 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 upper network device (MME, S-GW (Serving-GW)) and the base station device 3. ) Or receive.
  • MME mobile phone
  • S-GW Serving-GW
  • receive receives
  • other components of the base station device 3 and transmission paths of data (control information) between the components are omitted, but other functions necessary for operating as the base station device 3 are omitted.
  • the upper layer processing unit 34 has a plurality of blocks that it has as a component.
  • the upper layer processing unit 34 has a radio resource management layer processing unit and an application layer processing unit.
  • the upper layer processing unit 34 may also have a function of setting a plurality of scheduling request resources corresponding to each of a plurality of reference signals transmitted from the 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 base station device 3 that communicates with the terminal device that performs the random access procedure according to the second aspect of the present invention transmits the upper layer first parameter and the second parameter, and transmits the PDCCH including DCI.
  • the first parameter is included in a cell-common PUSCH configuration
  • the second parameter is included in a UE-specific PUSCH configuration. ..
  • the information of the PUSCH time domain resource allocation includes a slot offset between the DCI and the PUSCH, a start symbol of the PUSCH in a slot, and a continuous slot. The number of symbols to be allocated and the PUSCH mapping type are shown.
  • the terminal device 1 can efficiently communicate with the base station device 3.
  • 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, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or others.
  • a general-purpose processor may be a microprocessor, conventional processor, controller, microcontroller, or state machine.
  • the electric circuit described above may be composed of a digital circuit or an analog circuit. Further, in the event that an integrated circuit technology that replaces the current integrated circuit has emerged due to the progress of semiconductor technology, one or more aspects of the present invention can use a new integrated circuit according to the technology.
  • the present invention is not limited to the above embodiment. Although an example of the apparatus is described in the embodiment, the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device, a kitchen device, It can be applied to terminal devices or communication devices such as cleaning/laundry equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

La présente invention concerne un dispositif de terminal et un dispositif de station de base qui communiquent efficacement. L'invention concerne un dispositif de terminal pour effectuer une procédure d'accès aléatoire, le dispositif terminal étant tel que : un premier paramètre et un deuxième paramètre d'une couche supérieure sont reçus ; un PDCCH comprenant des DCI est reçu ; un PUSCH programmé par les DCI est transmis ; un troisième paramètre est défini à l'avance par une table par défaut ; le premier paramètre, le deuxième paramètre, et le troisième paramètre indiquent des informations concernant l'attribution de ressources de domaine temporel de PUSCH ; et lorsqu'un CRC brouillé par un TC-RNTI est ajouté aux DCI, l'un parmi le premier paramètre et le troisième paramètre est sélectionné indépendamment du fait que le second paramètre ait été reçu ou non, et l'attribution de ressource de domaine temporel de PUSCH est effectuée sur la base du paramètre sélectionné.
PCT/JP2020/005824 2019-02-22 2020-02-14 Dispositif de station de base, dispositif de terminal, procédé de communication, et circuit intégré WO2020170972A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2019-030647 2019-02-22
JP2019030647A JP2020137007A (ja) 2019-02-22 2019-02-22 基地局装置、端末装置、通信方法、および、集積回路

Publications (1)

Publication Number Publication Date
WO2020170972A1 true WO2020170972A1 (fr) 2020-08-27

Family

ID=72144882

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/005824 WO2020170972A1 (fr) 2019-02-22 2020-02-14 Dispositif de station de base, dispositif de terminal, procédé de communication, et circuit intégré

Country Status (2)

Country Link
JP (1) JP2020137007A (fr)
WO (1) WO2020170972A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210377979A1 (en) * 2019-02-14 2021-12-02 Panasonic Intellectual Property Corporation Of America User equipment and system performing transmission and reception operations
CN114390641A (zh) * 2022-02-15 2022-04-22 赛特斯信息科技股份有限公司 一种终端初始接入基站的方法
CN114389770A (zh) * 2020-10-19 2022-04-22 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置
WO2022138980A1 (fr) * 2020-12-25 2022-06-30 Sharp Kabushiki Kaisha Équipements utilisateur, stations de base et procédés
US20220217677A1 (en) * 2019-05-02 2022-07-07 Ntt Docomo, Inc. User equipment
WO2023134471A1 (fr) * 2022-01-11 2023-07-20 大唐移动通信设备有限公司 Procédé de détermination de ressource de domaine temporel, dispositif terminal et support de stockage
US12052706B2 (en) 2019-02-14 2024-07-30 Panasonic Intellectual Property Corporation Of America User equipment and system performing transmission and reception operations

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102500494B1 (ko) * 2021-09-07 2023-02-16 주식회사 블랙핀 무선 이동 통신 시스템에서 축소된 성능의 단말이 복수의 탐색구간과 제어자원셋을 이용해서 랜덤 액세스를 수행하고 시스템정보블록2를 수신하는 방법 및 장치
KR102487886B1 (ko) * 2021-09-07 2023-01-12 주식회사 블랙핀 무선 이동 통신 시스템에서 축소된 성능의 단말이 복수의 pusch 공통 설정 정보를 이용해서 랜덤 액세스를 수행하는 방법 및 장치

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 15", 3GPP TS 38.214 V15.4.0 (2018-12, 11 January 2019 (2019-01-11), pages 77 - 80, XP002962301 *
"Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15", 3GPP TS 38.331 V15.4.0 (2018-12, 14 January 2019 (2019-01-14), pages 275 - 277,282-283, XP055724784 *
LG ELECTRONICS ET AL., 3GPP TSG RAN WG1 ADHOC_NR_AH_1709 R1-1715846, 21 September 2017 (2017-09-21), pages 1 - 7, XP051329538 *
SHARP: "Remaining issues on DL/UL data scheduling[ online", 3GPP TSG RAN WG1 #95 R1-1813201, 16 November 2018 (2018-11-16), XP051555202 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210377979A1 (en) * 2019-02-14 2021-12-02 Panasonic Intellectual Property Corporation Of America User equipment and system performing transmission and reception operations
US20220014333A1 (en) * 2019-02-14 2022-01-13 Panasonic Intellectual Property Corporation Of America User equipment and system performing transmission and reception operations
US11943764B2 (en) * 2019-02-14 2024-03-26 Panasonic Intellectual Property Corporation Of America User equipment and system performing transmission and reception operations
US12052706B2 (en) 2019-02-14 2024-07-30 Panasonic Intellectual Property Corporation Of America User equipment and system performing transmission and reception operations
US20220217677A1 (en) * 2019-05-02 2022-07-07 Ntt Docomo, Inc. User equipment
CN114389770A (zh) * 2020-10-19 2022-04-22 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置
WO2022138980A1 (fr) * 2020-12-25 2022-06-30 Sharp Kabushiki Kaisha Équipements utilisateur, stations de base et procédés
WO2023134471A1 (fr) * 2022-01-11 2023-07-20 大唐移动通信设备有限公司 Procédé de détermination de ressource de domaine temporel, dispositif terminal et support de stockage
CN114390641A (zh) * 2022-02-15 2022-04-22 赛特斯信息科技股份有限公司 一种终端初始接入基站的方法

Also Published As

Publication number Publication date
JP2020137007A (ja) 2020-08-31

Similar Documents

Publication Publication Date Title
US11729795B2 (en) Base station apparatus, terminal apparatus, communication method, and integrated circuit
JP7197297B2 (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é
WO2020166696A1 (fr) Dispositif station de base, dispositif terminal et procédé de communication
WO2020170972A1 (fr) Dispositif de station de base, dispositif de 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é
JP7240843B2 (ja) 基地局装置、端末装置、通信方法、および、集積回路
WO2020129783A1 (fr) Appareil de station de base, appareil terminal, procédé de communication et circuit intégré
WO2020166695A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication et circuit intégré
WO2020145368A1 (fr) Dispositif de station de base, dispositif terminal et procédé de communication
WO2020031588A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication et circuit intégré
WO2020129784A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré
WO2020218254A1 (fr) Dispositif de station de base, 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é
WO2020075775A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré
WO2019244861A1 (fr) Dispositif terminal, procédé de communication, et circuit intégré
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: 20758939

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: 20758939

Country of ref document: EP

Kind code of ref document: A1