WO2022185440A1 - 端末、無線通信方法及び基地局 - Google Patents
端末、無線通信方法及び基地局 Download PDFInfo
- Publication number
- WO2022185440A1 WO2022185440A1 PCT/JP2021/008118 JP2021008118W WO2022185440A1 WO 2022185440 A1 WO2022185440 A1 WO 2022185440A1 JP 2021008118 W JP2021008118 W JP 2021008118W WO 2022185440 A1 WO2022185440 A1 WO 2022185440A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pusch
- transmission
- dci
- reference signal
- srs
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims description 58
- 238000000034 method Methods 0.000 title claims description 28
- 230000005540 biological transmission Effects 0.000 claims abstract description 261
- 238000012545 processing Methods 0.000 description 54
- 230000011664 signaling Effects 0.000 description 32
- 238000010586 diagram Methods 0.000 description 26
- 238000013507 mapping Methods 0.000 description 23
- 238000005259 measurement Methods 0.000 description 22
- 230000009977 dual effect Effects 0.000 description 10
- 238000010295 mobile communication Methods 0.000 description 9
- 238000001914 filtration Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000004364 calculation method Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 6
- 230000004913 activation Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000003321 amplification Effects 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000012937 correction Methods 0.000 description 4
- 230000009849 deactivation Effects 0.000 description 4
- 238000003199 nucleic acid amplification method Methods 0.000 description 4
- 230000000737 periodic effect Effects 0.000 description 4
- 238000013468 resource allocation Methods 0.000 description 4
- 125000004122 cyclic group Chemical group 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 239000011159 matrix material Substances 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000001174 ascending effect Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000007274 generation of a signal involved in cell-cell signaling Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 101150071746 Pbsn gene Proteins 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 108010015046 cell aggregation factors Proteins 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 239000006249 magnetic particle Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0014—Three-dimensional division
- H04L5/0023—Time-frequency-space
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
- H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- 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/04—Wireless resource allocation
-
- 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
- H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
Definitions
- the present disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
- LTE Long Term Evolution
- 3GPP Rel. 10-14 LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).
- LTE successor systems for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later
- 5G 5th generation mobile communication system
- 5G+ 5th generation mobile communication system
- 6G 6th generation mobile communication system
- NR New Radio
- 3GPP Rel. 15 supports repeated transmissions on UL data channels (eg, Physical Uplink Shared Channel (PUSCH)).
- PUSCH Physical Uplink Shared Channel
- the UE controls PUSCH transmission over a plurality of slots (eg, K consecutive slots) based on a repetition factor K set by the network (eg, base station). That is, when performing repeated transmission, each PUSCH is transmitted in different slots (for example, in slot units).
- K Physical Uplink Shared Channel
- each PUSCH is transmitted in units shorter than a slot (eg, subslot units, minislot units).
- TRP transmission/reception points
- one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control repeated PUSCH transmission.
- a terminal includes a receiving unit that receives information regarding configuration of transmission of a plurality of physical uplink shared channels (PUSCH) based on one downlink control information (DCI), and from a plurality of reference signal indexes , a controller that determines one or more reference signal indices to be utilized for spatial relationships and/or pathloss reference signals (PL-RS) for the plurality of PUSCHs.
- PUSCH physical uplink shared channels
- DCI downlink control information
- PL-RS pathloss reference signals
- FIGS. 7A and 7B are diagrams illustrating an example of existing repeated PUSCH transmission and repeated PUSCH transmission according to the second embodiment.
- FIG. 8A and 8B are diagrams illustrating examples of DCI formats that configure repeated transmission of PUSCH based on a single DCI.
- FIG. 9 is a diagram illustrating an example of a schematic configuration of a radio communication system according to an embodiment.
- FIG. 10 is a diagram illustrating an example of the configuration of a base station according to one embodiment.
- FIG. 11 is a diagram illustrating an example of the configuration of a user terminal according to one embodiment.
- FIG. 12 is a diagram illustrating an example of hardware configurations of a base station and user terminals according to an embodiment.
- repeat transmission is supported in data transmission.
- a base station network (NW), gNB) repeats transmission of DL data (for example, downlink shared channel (PDSCH)) a predetermined number of times.
- PDSCH downlink shared channel
- the UE repeats transmission of UL data (eg, uplink shared channel (PUSCH)) a predetermined number of times.
- PUSCH uplink shared channel
- FIG. 1A is a diagram showing an example of repeated transmission of PUSCH.
- FIG. 1A an example of scheduling a predetermined number of repeated PUSCHs with a single DCI is shown.
- the number of iterations is also called a repetition factor K or an aggregation factor K.
- the nth iteration may also be referred to as the nth transmission occasion, etc., and may be identified by a iteration index k (0 ⁇ k ⁇ K ⁇ 1).
- FIG. 1A shows repeated transmissions of PUSCH dynamically scheduled in DCI (eg, dynamic grant-based PUSCH), it may also be applied to repeated transmissions of configured grant-based PUSCH.
- the UE semi-statically receives information indicating the repetition factor K (eg, aggregationFactorUL or aggregationFactorDL) via higher layer signaling.
- the higher layer signaling may be, for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information, or a combination thereof.
- MAC CE Control Element
- MAC PDU Protocol Data Unit
- the broadcast information may be, for example, a master information block (MIB), a system information block (SIB), or a minimum system information (RMSI: Remaining Minimum System Information).
- MIB master information block
- SIB system information block
- RMSI Minimum System Information
- PDSCH reception processing for example, reception, demapping, demodulation, decoding at least one
- control the PUSCH transmission process e.g., transmission, mapping, modulation, and/or coding
- allocation of time domain resources e.g.
- RB resource blocks
- RBG resource block groups
- MCS Modulation and Coding Scheme
- DMRS Demodulation Reference Signal
- TCI transmission configuration indication
- FIG. 1A shows a case where PUSCH in each slot is assigned to a predetermined number of symbols from the beginning of the slot. Identical symbol allocations between slots may be determined as described for time domain resource allocation above.
- the UE determines the symbol in each slot based on the start symbol S and the number of symbols L (eg, Start and Length Indicator (SLIV)) determined based on the value m of a predetermined field (eg, TDRA field) in the DCI. Allocation may be determined. Note that the UE may determine the first slot based on K2 information determined based on the value m of a predetermined field (eg, TDRA field) of DCI.
- L Start and Length Indicator
- the redundancy version (Redundancy Version (RV)) applied to the TB based on the same data may be the same, or may be at least partially different.
- the RV applied to that TB at the nth slot may be determined based on the value of a predetermined field (eg, RV field) in the DCI.
- Resources allocated in consecutive K slots are uplink communication direction indication information for TDD control (for example, "TDD-UL-DL-ConfigCommon", “TDD-UL-DL-ConfigDedicated” of RRC IE) and If the communication direction is different in at least one symbol from UL, DL or Flexible of each slot specified by at least one slot format indicator of DCI (for example, DCI format 2_0), the symbol is Resources in the containing slot may not transmit (or receive).
- PUSCH is repeatedly transmitted over a plurality of slots (slot units) as shown in FIG. 1A, but Rel. 16 and later, it is assumed that PUSCH is repeatedly transmitted in units shorter than slots (for example, in units of subslots, units of minislots, or units of a predetermined number of symbols) (see FIG. 1B).
- the nth iteration may also be referred to as the nth transmission occasion, etc., and may be identified by a iteration index k (0 ⁇ k ⁇ K ⁇ 1).
- FIG. 1B shows repeated transmissions of PUSCH dynamically scheduled in DCI (eg, dynamic grant-based PUSCH), it may also be applied to repeated transmissions of configured grant-based PUSCH.
- a predetermined field eg, TDRA field
- the UE may dynamically receive information indicating the repetition factor K (for example, numberofrepetitions) using downlink control information.
- a repetition factor may be determined based on the value m of a predetermined field (eg, the TDRA field) within the DCI. For example, a table that defines the correspondence between bit values notified by DCI, repetition coefficient K, start symbol S, and number of symbols L may be supported.
- the slot-based repetition transmission shown in FIG. 1A is called repetition transmission type A (for example, PUSCH repetition Type A), and the subslot-based repetition transmission shown in FIG. 1B is called repetition transmission type B (for example, PUSCH repetition Type B ) may be called
- the UE may be configured to apply at least one of repeat transmission type A and repeat transmission type B.
- the repeat transmission type applied by the UE may be notified from the base station to the UE through higher layer signaling (eg, PUSCHRepTypeIndicator).
- Either repetition transmission type A or repetition transmission type B may be configured in the UE for each DCI format that schedules PUSCH.
- a first DCI format e.g., DCI format 0_1
- higher layer signaling e.g., PUSCHRepTypeIndicator-AorDCIFormat0_1
- PUSCH-RepTypeB repeat transmission type B
- the UE receives the first DCI Apply repeat transmission type B for PUSCH repeat transmissions scheduled in the format. Otherwise (e.g., if PUSCH-RepTypeB is not configured or if PUSCH-RepTypA is configured), the UE applies repeat transmission type A for PUSCH repeat transmissions scheduled in the first DCI format. do.
- PUSCH included in the higher layer parameters may be set by a parameter related to the number of repetitions of (eg, numberOfRepetitions-r16).
- the UE may determine the number of PUSCH repetitions scheduled by that DCI based on the DCI's time domain resource allocation field. When the number of repetitions is set/designated to 1, the UE may perform a single PUSCH transmission.
- (Invalid symbol pattern) When applying repeat transmission type B to PUSCH transmission, it is also under consideration to inform the UE of information about symbols (or symbol patterns) that cannot be used for PUSCH transmission.
- a symbol pattern that cannot be used for PUSCH transmission may be called an invalid symbol pattern, an invalid symbol pattern, or the like.
- the DCI may be in a predetermined DCI format (eg, at least one of DCI formats 0_1 and 0_2).
- the first higher layer parameter is used to notify the UE of information on invalid symbol patterns that cannot be used for PUSCH transmission.
- DCI may be used to notify the UE of whether or not the information on the invalid symbol pattern is applied.
- a bit field for indicating whether or not to apply information on invalid symbol patterns field for notifying whether or not to apply invalid symbol patterns
- the second higher layer parameter may be used to notify the UE of whether or not the notification field (or additional bit) in DCI is set. That is, when the information about the invalid symbol pattern is notified by the first higher layer parameter, the UE may determine whether or not to apply the information about the invalid symbol pattern based on the second higher layer parameter and DCI. .
- the UE may control PUSCH transmission without considering invalid symbol patterns.
- the UE may determine whether to apply the invalid symbol pattern based on the second higher layer parameter and DCI. For example, if the second higher layer parameter indicates the addition of an additional bit (or a predetermined field) indicating whether to apply the invalid symbol pattern to the DCI, the UE is based on the predetermined field of the invalid symbol pattern. Applicability may be determined.
- the first upper layer parameter may be information that notifies a symbol pattern that is invalid for PUSCH transmission, and may be applied in a bitmap format, for example (see FIG. 2A).
- FIG. 2A is a diagram showing an example in which invalid symbol patterns are defined in a bitmap (1-D bitmap) in the time domain.
- the UE may determine available resources for PUSCH transmission in one or more frequency bandwidths (eg, BWP) based on information about invalid symbol patterns (see FIG. 2B).
- BWP frequency bandwidths
- repetition transmission type B When repetition transmission type B is applied and repetition transmission is performed in units of sub-slots, some repetition transmission crosses the slot-boundary depending on the repetition factor (K) and data allocation unit. A case arises.
- FIG. 3A shows an example of applying repetition transmission type B when the repetition factor (K) is 4 and the PUSCH length (L) is 4.
- K repetition factor
- L PUSCH length
- PUSCH transmission may be performed using symbols other than the DL symbol portion.
- the PUSCH may be divided (or segmented).
- the UE uses information (SRS configuration information, e.g., RRC control element "SRS-Config" used for transmission of measurement reference signals (e.g., Sounding Reference Signal (SRS)) parameters) may be received.
- SRS configuration information e.g., RRC control element "SRS-Config" used for transmission of measurement reference signals (e.g., Sounding Reference Signal (SRS))
- SRS-Config used for transmission of measurement reference signals (e.g., Sounding Reference Signal (SRS)) parameters
- the UE receives information on one or more SRS resource sets (SRS resource set information, e.g., "SRS-ResourceSet” of the RRC control element) and information on one or more SRS resources (SRS resource information, eg, "SRS-Resource” of the RRC control element).
- SRS resource set information e.g., "SRS-ResourceSet” of the RRC control element
- SRS resource information e.g. "SRS-Resource” of the RRC control element
- One SRS resource set may be associated with a predetermined number of SRS resources (a predetermined number of SRS resources may be grouped together).
- Each SRS resource may be identified by an SRS resource indicator (SRI) or an SRS resource ID (Identifier).
- the SRS resource set information includes an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, SRS resource types (for example, periodic SRS (Periodic SRS), semi-persistent Either SRS (Semi-Persistent SRS) or aperiodic CSI (Aperiodic SRS)), and information on SRS usage may be included.
- SRS-ResourceSetId SRS resource set ID
- SRS-ResourceId list of SRS resource IDs used in the resource set
- SRS resource types for example, periodic SRS (Periodic SRS), semi-persistent Either SRS (Semi-Persistent SRS) or aperiodic CSI (Aperiodic SRS)
- SRS resource types for example, periodic SRS (Periodic SRS), semi-persistent Either SRS (Semi-Persistent SRS) or a
- the SRS resource types are periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic CSI (Aperiodic SRS (A-SRS)).
- P-SRS periodic SRS
- SP-SRS semi-persistent SRS
- A-SRS aperiodic CSI
- the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation) and transmit A-SRS based on DCI's SRS request.
- usage of RRC parameter, "SRS-SetUse” of L1 (Layer-1) parameter is, for example, beam management (beamManagement), codebook (CB), noncodebook (noncodebook ( NCB)), antenna switching, and the like.
- the SRS for codebook or non-codebook applications may be used to determine precoders for codebook-based or non-codebook-based PUSCH transmissions based on SRI.
- the UE determines the precoder for PUSCH transmission based on the SRI, the Transmitted Rank Indicator (TRI) and the Transmitted Precoding Matrix Indicator (TPMI). may be determined.
- the UE may determine the precoder for PUSCH transmission based on the SRI for non-codebook-based transmission.
- SRS resource information includes SRS resource ID (SRS-ResourceId), SRS port number, SRS port number, transmission Comb, SRS resource mapping (eg, time and/or frequency resource position, resource offset, resource period, repetition number, SRS number of symbols, SRS bandwidth, etc.), hopping related information, SRS resource type, sequence ID, spatial relationship information of SRS, and so on.
- the spatial relationship information of the SRS may indicate spatial relationship information between a given reference signal and the SRS.
- the predetermined reference signal includes a Synchronization Signal/Physical Broadcast Channel (SS/PBCH) block, a Channel State Information Reference Signal (CSI-RS) and an SRS (for example, another SRS).
- SS/PBCH Synchronization Signal/Physical Broadcast Channel
- CSI-RS Channel State Information Reference Signal
- SRS for example, another SRS.
- An SS/PBCH block may be referred to as a Synchronization Signal Block (SSB).
- SSB Synchronization Signal Block
- the SRS spatial relationship information may include at least one of the SSB index, CSI-RS resource ID, and SRS resource ID as the index of the predetermined reference signal.
- the SSB index, SSB resource ID, and SSB Resource Indicator may be read interchangeably.
- the CSI-RS index, CSI-RS resource ID and CSI-RS resource indicator (CRI) may be read interchangeably.
- the SRS index, the SRS resource ID, and the SRI may be read interchangeably.
- the spatial relationship information of the SRS may include the serving cell index, BWP index (BWP ID), etc. corresponding to the predetermined reference signal.
- the SRS resource may be transmitted using the same spatial domain filter (spatial domain transmit filter).
- the UE may assume that the UE receive beam for SSB or CSI-RS and the UE transmit beam for SRS are the same.
- a spatial domain filter for the transmission of this reference SRS may be transmitted using the same spatial domain filter (spatial domain transmit filter) as (spatial domain transmit filter). That is, in this case, the UE may assume that the UE transmission beam of the reference SRS and the UE transmission beam of the target SRS are the same.
- the UE may determine the spatial relationship of PUSCHs scheduled by that DCI based on the value of a predetermined field (eg, SRS Resource Identifier (SRI) field) within the DCI (eg, DCI format 0_1). Specifically, the UE may use the spatial relationship information (eg, “spatialRelationInfo” of the RRC information element) of the SRS resource determined based on the value of the predetermined field (eg, SRI) for PUSCH transmission.
- a predetermined field eg, SRS Resource Identifier (SRI) field
- the UE when using codebook-based transmission, the UE is configured by RRC with two SRS resources per SRS resource set and one of the two SRS resources is indicated by DCI (1-bit SRI field).
- DCI (1-bit SRI field).
- the UE when using non-codebook based transmission, the UE is configured by RRC with 4 SRS resources per SRS resource set and one of the 4 SRS resources is indicated by DCI (2-bit SRI field).
- the Transmitted Precoding Matrix Indicator (TPMI) and transmission rank for codebook-based PUSCH transmission are specified in a specific field (e.g., DCI format 0_1) included in the downlink control information (e.g., For example, it is considered to be specified by precoding information and number of layers field).
- a specific field e.g., DCI format 0_1
- DCI format 0_1 included in the downlink control information
- the precoder that the UE uses for codebook-based PUSCH transmission is selected from uplink codebooks with the same number of antenna ports as the value set in the higher layer parameters (e.g., nrofSRS-Ports) configured for SRS resources.
- the higher layer parameters e.g., nrofSRS-Ports
- the size (number of bits) of this particular field is variable depending on the number of antenna ports for PUSCH (for example, the number of ports indicated by nrofSRS-Ports above) and some higher layer parameters.
- This particular field may be 0 bits if the higher layer parameters configured for the UE (eg, txConfig) are set to nonCodebook.
- this particular field may be 0 bits if the higher layer parameters configured for the UE (e.g., txConfig) are configured in the codebook. .
- This particular field is also set for the UE if the higher layer parameters (e.g., txConfig) set for the UE are set in the codebook for the four antenna ports. It may have a bit length of 2 to 6 bits, depending on another higher layer parameter and/or whether the transform precoder is present (enabled or disabled).
- the higher layer parameters e.g., txConfig
- this particular field is set for the UE if the higher layer parameters (e.g., txConfig) set for the UE are set in the codebook for the two antenna ports. It may have a bit length of 1 to 4 bits, depending on another higher layer parameter and/or whether the transform precoder is present (enabled or disabled).
- the higher layer parameters e.g., txConfig
- the other higher layer parameters include a parameter for specifying the UL full power transmission mode (e.g., ul-FullPowerTransmission), a parameter indicating the maximum value of the UL transmission rank (e.g., maxRank), a certain precoding matrix indicator ( It may be at least one of a parameter (for example, codebookSubset) indicating a subset of PMI) and a parameter for specifying a transform precoder (for example, transformPrecoder).
- a parameter for specifying the UL full power transmission mode e.g., ul-FullPowerTransmission
- a parameter indicating the maximum value of the UL transmission rank e.g., maxRank
- a certain precoding matrix indicator It may be at least one of a parameter (for example, codebookSubset) indicating a subset of PMI) and a parameter for specifying a transform precoder (for example, transformPrecoder).
- Path loss RS Path loss PL b in each transmission power control of uplink shared channel (PUSCH), physical uplink control channel (PUCCH), reference signal for measurement (Sounding Reference Signal (SRS))
- f,c (q d ) [dB] is the UE with the index q d of the reference signal (RS, PathlossReferenceRS) for downlink BWP associated with the active UL BWP b of carrier f of serving cell c. calculated by
- pathloss reference RS pathloss reference RS
- pathloss(PL)-RS index q d
- RS used for pathloss calculation and RS resource used for pathloss calculation
- calculation, estimation, measurement, and track may be used interchangeably.
- the PL-RS may be at least one of DL RSs such as SSB and CSI-RS.
- the 15 UEs are configured with up to 4 PL-RSs by RRC signaling. Even if the UL transmit beam (spatial relationship) is updated by MAC CE, PL-RS cannot be updated by MAC CE.
- the 16 UEs are configured with up to 64 PL-RSs by RRC signaling, and one PL-RS is indicated (activated) by MAC CE.
- the UE is required to track up to 4 active PL-RSs for all UL channels (SRS and PUCCH and PUSCH). Tracking the PL-RS may be calculating the path loss based on PL-RS measurements and keeping (storing) the path loss.
- the PL-RS may also be updated to the TCI state.
- At least one of MAC CE for activation/deactivation of PUCCH spatial relationship and MAC CE for activation/deactivation of SRS spatial relationship may not be used.
- a default spatial relationship is being considered as the spatial relationship that the UE will utilize when the spatial relationship is not available for UL transmission (eg, cannot be specified, not specified, not activated).
- the default PL-RS is being considered as the PL-RS to utilize when the PL-RS is not available for UL transmission (ibid.) or when the default spatial relationship is utilized.
- UE operations that utilize these default spatial relationships/default PL-RSs may be referred to as default beam operations.
- the spatial relationship used for PUSCH transmission scheduled by DCI format 0_0 may be referred to as the default spatial relationship
- the PL-RS used for (downlink path loss estimation in) transmission power control of this PUSCH may be called the default PL-RS.
- Rel. Determination of the default spatial relationship/default PL-RS on 15/16 will now be described.
- the spatial relationship of PUSCHs scheduled by DCI format 0_0 follows the spatial relationship (active spatial relationship) corresponding to the PUCCH resource with the lowest PUCCH resource ID within the active UL BWP of the same cell.
- the spatial relationship of the PUSCH scheduled by DCI format 0_0 in a cell is such that the default beam enable parameter (enableDefaultBeamPL-ForPUSCH0-0) for the PUSCH is set to enabled, and the UE is active UL If no PUCCH resources have been configured for the BWP (or PUCCH resources have been configured but not all PUCCH resources have spatial relationships configured), the QCL assumption of the CORESET with the lowest ID in the active DL BWP for the cell followss the spatial relationship with reference to the corresponding QCL type D RS. Otherwise, the spatial relationship of PUSCH scheduled by DCI format 0_0 is Rel. Similar to 15.
- the UE uses the SS that the UE uses to obtain the MIB. From the SS/PBCH block having the same index as the /PBCH block index, downlink path loss is calculated using RS resources. This RS corresponds to the default PL-RS.
- PUSCH transmission is scheduled with DCI format 0_0 and spatial setting is provided in higher layer parameter PUCCH-SpatialRelationInf for the PUCCH resource with the lowest active UL BWP index for each carrier and serving cell.
- the UE uses the same RS resource index as qd for PUCCH transmission in the PUCCH resource with the lowest index for downlink path loss estimation in this PUSCH transmission.
- PUSCH transmission is not scheduled with DCI format 0_0 and the UE is provided with the upper layer parameter enableDefaultBeamPL-ForSRS-r16 and the higher layer parameters PUSCH-PathlossReferenceRS and PUSCH-PathlossReferenceRS-r16. Otherwise, in this PUSCH transmission, the UE uses the same RS resource index as q d as the SRS resource set with SRS resources associated with the PUSCH transmission for downlink path loss estimation.
- the PUSCH transmission is scheduled with DCI format 0_0 and the UE has not been provided with spatial relationship settings for the PUCCH transmission, or if the PUSCH transmission is scheduled with DCI format 0_1 or 0_2 that does not include the SRI field.
- the higher layer parameter SRI-PUSCH-PowerControl is not provided to the UE, the value of the corresponding PUSCH-PathlossReferenceRS-Id is equal to 0, and the RS resource index is q d and used for downlink path loss estimation. do.
- this RS resource may be on the serving cell where the PUSCH is transmitted, or if the higher layer parameter pathlossReferenceLinking is provided, it may be on the serving cell indicated by this value.
- the default beam enable parameter (enableDefaultBeamPL-ForPUSCH0-0) for the PUSCH is set to enabled, and the UE is active If no PUCCH resources have been configured for the UL BWP (or PUCCH resources have been configured but not all PUCCH resources have spatial relationships configured), the QCL assumption of the CORESET with the lowest ID in the active DL BWPs of said cell is the RS corresponding to the RS resource index that provides the periodic RS resource of QCL type D corresponding to .
- Multi-TRP In NR, one or more transmission/reception points (TRP) (multi-TRP) uses one or more panels (multi-panel) to perform DL transmission to the UE. It is also, it is being considered that the UE performs UL transmission for one or more TRPs (see FIG. 4).
- a plurality of TRPs may correspond to the same cell identifier (cell identifier (ID)) or may correspond to different cell IDs.
- the cell ID may be a physical cell ID or a virtual cell ID.
- mapping pattern When the UE decides to perform repeated transmissions of PUSCH for multiple TRPs, it may determine that multiple SRIs and multiple repeated transmissions are supported based on certain rules. Such rules may also be referred to as mapping patterns, mapping rules, correspondence patterns, correspondences, and the like. The UE may assume that the number of PUSCH repetitions exceeds the number of beams used for PUSCH transmission.
- the UE when the UE decides to perform repeated transmissions of PUSCH for multiple TRPs, it may determine that multiple SRIs cyclically correspond to multiple repeated transmissions. Such correspondences may be referred to as cyclical mappings, cyclical patterns, cyclical correspondences, and the like.
- FIG. 5A is a diagram showing an example in which multiple SRIs and multiple repeated transmissions cyclically correspond.
- the UE performs repeated transmissions of PUSCH with a repetition number of 6 and using the first SRI and the second SRI.
- the UE cyclically performs PUSCH transmissions using a first SRI and PUSCH transmissions using a second SRI. For example, a first SRI is applied to the odd iterations (iterations #1, #3, #5) and a second SRI is applied to the even iterations (iterations #0, #2, #4). good too.
- the UE when the UE determines to perform repeated transmission of PUSCH in multiple TRPs, it determines that multiple SRIs correspond to multiple repeated transmissions and a specific number (for example, two) sequentially.
- a specific number for example, two
- Such correspondences may be referred to as sequential mappings, sequential patterns, sequential correspondences, and the like.
- FIG. 5B is a diagram showing an example in which multiple SRIs and multiple repeated transmissions sequentially correspond.
- the UE performs repeated transmissions of PUSCH with a repetition number of 6 and using the first SRI and the second SRI.
- the UE sequentially performs two PUSCH transmissions using the first SRI and two PUSCH transmissions using the second SRI.
- the multiple SRIs and the multiple repeated transmissions correspond successively to roughly equal the number of repetitions divided by the number of SRIs.
- the SRI number is 2
- the correspondence may be called a half-half pattern (mapping).
- FIG. 5C is a diagram showing an example of using a half-half pattern to correspond to multiple SRIs and multiple repeated transmissions.
- the UE performs repeated transmission of PUSCH with 6 specified as the repetition number and using the first SRI and the second SRI.
- the UE performs PUSCH transmission using the first SRI in the first half (first three) PUSCH transmission opportunities, and the second SRI in the second half (three subsequent) PUSCH transmission opportunities. performs PUSCH transmission using
- mapping pattern to be used among the plurality of mapping patterns described using FIGS. 5A to 5C may be defined in the specifications.
- the plurality of mapping patterns may be defined in the specification, and the mapping pattern to be applied may be set/instructed to the UE using at least one of higher layer signaling and physical layer signaling.
- the UE may report to the NW the UE capability regarding which of the multiple mapping patterns the application of which mapping pattern is supported.
- mapping pattern described above may be applied to correspondence between multiple TPMI/TPC commands and multiple PUSCHs.
- FIG. 6 is a diagram showing an example of repeated transmission of PUSCH based on a single DCI for multiple TRPs.
- the UE repeatedly transmits PUSCH twice.
- the UE is instructed with information (RS resources) on SRIs to be applied to each of PUSCH#1 and PUSCH#2, which is included in one DCI.
- panel identifier (ID) and panel may be read interchangeably.
- TRP ID and TRP may be read interchangeably.
- indexes, IDs, indicators, and resource IDs may be read interchangeably.
- A/B may mean “at least one of A and B”. Also, in the present disclosure, “A/B/C” may mean “at least one of A, B and C.”
- SRI Spatial Relation Information
- SRS resource indicator SRS Resource Indicator (SRI)
- SRI SRS resource indicator
- SRI field SRS resource indicator
- SRS resource precoder, etc.
- spatial relation information SRI
- SRI spatial relation information
- SRI for codebook-based transmission SRI for codebook-based transmission
- non-codebook-based SRI combination SRI for codebook-based transmission
- spatialRelationInfo UL TCI
- TCI state TCI state
- Unified TCI QCL, etc.
- the first TRP and the second TRP are the first PUSCH and the second PUSCH, the first PUSCH transmission opportunity and the second PUSCH transmission opportunity, the first SRI and the second SRI, etc. and may be read interchangeably.
- repeated transmission of PUSCH for multiple TRPs may be read as PUSCH over multiple TRPs, repeated PUSCH over multiple TRPs, simply repeated PUSCH, repeated transmission, multiple PUSCH transmission, and the like.
- a single PUSCH transmission for a single TRP may also be referred to simply as a single PUSCH transmission, a PUSCH transmission in a single TRP, and so on.
- repeated transmission of PUSCH for a single TRP may mean repeated transmission of multiple PUSCHs transmitted using the same SRI/beam/precoder.
- repeated transmission of PUSCH for multiple TRPs may mean repeated transmission of multiple PUSCHs transmitted using multiple different SRIs/beams/precoders.
- the repeated transmissions and multiple SRIs/beams/precoders may correspond cyclically as described above, or may correspond sequentially by a certain number, half-half A correspondence using a (half-half) pattern (mapping) may be used.
- determining the spatial relationship of the PUSCH/TCI state may be read as determining (the index of) the reference signal to be applied (utilized) to the spatial relationship of the PUSCH/PL-RS.
- each SRI field may indicate one or more SRS resources (SRIs) to the UE.
- SRIs SRS resources
- the 'dynamic switch' in the present disclosure may mean 'a switch that uses at least one of higher layer signaling and physical layer signaling'.
- switch in the present disclosure may be read interchangeably as switching, change, changing, application, and the like.
- the UE is configured with a single DCI based PUSCH repetition transmission (S-DCI based PUSCH repetition) and a DCI format without (or including) an SRI field (eg, DCI format 0_0). may be used to schedule PUSCH.
- the repeated transmission of PUSCH based on a single DCI is configured by setting multiple SRI fields/TPMI fields/TPC command fields in a specific DCI format (eg, DCI format 0_1/0_2). It may be
- the UE may not repeatedly transmit the PUSCH (or not repeatedly transmit the PUSCH (or transmit once). ) (Embodiment 1-1). That is, when PUSCH is scheduled using a specific DCI format (eg, DCI format 0_0), the UE will receive Rel. 15 may be controlled to transmit PUSCH.
- a specific DCI format eg, DCI format 0_0
- the UE may repeat transmission of the PUSCH X times (X is any integer) (Embodiment 1 -2).
- this “X” may mean the number of beams applied to PUSCH repetition transmission, and may be different from the number of PUSCH repetitions.
- the UE uses a specific DCI format (eg, DCI format 0_0) when PUSCH is scheduled.
- DCI format 0_0 DCI format 0
- the PUSCH transmission may be repeated X times (X is an arbitrary integer).
- Condition 1 Multiple spatial relationships are configured for PUCCH resources (associated PUCCH resources) used to determine PL-RS/spatial relationships of PUSCH,
- Condition 2 multiple TCI states are set for the CORESET (associated CORESET) used to determine the PUSCH PL-RS/spatial relationship;
- Condition 3 multiple TCI states are configured for SRS resources (associated SRS resources) used to determine PL-RS/spatial relationships for PUSCH;
- Condition 4 A higher layer parameter is configured to configure/enable/activate repeated transmission of PUSCH scheduled using a specific DCI format (eg, DCI format 0_0).
- condition 5 when the following condition 5 is a specific DCI format (for example, DCI format 0_0) when the PUSCH is scheduled, the PUSCH can be repeatedly transmitted. May be used: Condition 5: PL-RS for PUSCH/PUCCH resource/CORESET/SRS resource for spatial relationship or multiple spatial relationship/TCI states are configured for reference RS (CSI-RS, SSB, SRS, etc.).
- the UE assumes, expects that one spatial relationship/TCI state is configured/associated for the PUCCH resource/CORESET/SRS resource used to determine the PUSCH PL-RS/spatial relationship.
- the UE may It may be assumed that the spatial relationship/TCI state is the default PL-RS/spatial relationship for PUSCH.
- the UE When multiple spatial relationships/TCI states are configured/associated for the PUCCH resource/CORESET/SRS resource used to determine the PUSCH PL-RS/spatial relationship, the UE shall /TCI state, one spatial relationship/TCI state may be determined/selected as the default PL-RS/spatial relationship for PUSCH.
- the UE determines, from multiple spatial relationships/TCI states, one spatial relationship/TCI state that meets at least one of rules 1 to 5 described below as the default PL-RS/spatial relationship for PUSCH/ You may choose: Rule 1: the spatial relationship/TCI state corresponding to the largest (minimum) spatial relationship ID/TCI state ID, Rule 2: Spatial relationship/TCI state corresponding to maximum (minimum) PUCCH resource ID/CORESET ID/SRS resource ID, Rule 3: For each PUCCH resource/CORESET/SRS resource, the first/second spatial relationship ID/TCI state ID/PUCCH resource ID/CORESET ID/ when the first/second beam/resource is configured the spatial relationship/TCI state corresponding to the SRS resource ID; Rule 4: one spatial relationship/TCI state determined/selected according to specific rules set in higher layer signaling; Rule 5: A spatial relationship/TCI state corresponding to a particular (exact) spatial relationship ID/TCI state ID configured/indicated in higher layer signaling.
- the UE assumes, expects that X spatial relationships/TCI states are configured/associated with respect to the PUCCH resource/CORESET/SRS resource used to determine the PUSCH PL-RS/spatial relationship. You may
- the UE may be assumed to be the default PL-RS/spatial relations for the PUSCH in each PUSCH transmission opportunity.
- X spatial relations/TCI states When more than X spatial relations/TCI states are configured/associated with PUCCH resources/CORESET/SRS resources used to determine PL-RS/spatial relations of PUSCH, the UE shall From a larger number of spatial relationships/TCI states, X spatial relationships/TCI states may be determined/selected as default PL-RS/spatial relationships for PUSCH.
- the UE selects X spatial relationships/TCI states that fall under at least one of rules 1 to 5 described below from the number of spatial relationships/TCI states greater than X as the default PL-RS/spatial for PUSCH. May be determined/selected as relations: Rule 1: Spatial relations/TCI states corresponding to X spatial relation IDs/TCI state IDs in descending order (ascending order) from the largest (minimum) spatial relation ID/TCI state ID, Rule 2: Spatial relations/TCI states corresponding to X PUCCH resource IDs/CORESET IDs/SRS resource IDs in descending order (ascending order) from the largest (smallest) PUCCH resource ID/CORESET ID/SRS resource ID, Rule 3: For each PUCCH resource/CORESET/SRS resource, the first/second spatial relationship ID/TCI state ID/PUCCH resource ID/CORESET ID/ when the first/second beam/resource is configured the spatial relationship/TCI state corresponding to the SRS resource ID; Rule
- X spatial relationships/TCI states may be determined/selected by combining two or more of the above rules. For example, the UE uses a rule to determine A (A is a number smaller than X) spatial relationships/TCI states among the X spatial relationships/TCI states to determine, and then uses another rule. may determine XA spatial relationships/TCI states.
- the UE may assume that the Y spatial relations/TCI states are the default PL-RS/spatial relations for PUSCH.
- the UE may then determine the remaining XY spatial relationships/TCI states that fall under at least one of rules 6 and 7 described below: Rule 6: Spatial relationship/TCI state corresponding to the Nth (N is an integer greater than or equal to 2)/maximum/minimum PUCCH resource ID/CORESET ID, Rule 7: Spatial relationship/TCI state corresponding to a specific (exact) spatial relationship ID/TCI state ID set/indicated in higher layer signaling used to determine Y spatial relationships/TCI states .
- rules 6 and 7 Spatial relationship/TCI state corresponding to the Nth (N is an integer greater than or equal to 2)/maximum/minimum PUCCH resource ID/CORESET ID
- Rule 7 Spatial relationship/TCI state corresponding to a specific (exact) spatial relationship ID/TCI state ID set/indicated in higher layer signaling used to determine Y spatial relationships/TCI states .
- the spatial relationship/PL-RS of PUSCH can be determined appropriately.
- the UE uses the default A PL-RS/spatial relationship may be applied.
- FIG. 7A shows the existing Rel.
- FIG. 15 is a diagram showing an example of repeated transmission of PUSCH on 15/16;
- a common beam/PL-RS (beam/PL-RS#1) is set/indicated for repeated transmissions of PUSCHs (PUSCH#1 and PUSCH#2) scheduled with a single DCI. be done.
- FIG. 7B is a diagram illustrating an example of repeated transmission of PUSCH according to the second embodiment.
- a different beam/PL-RS (beam/PL-RS#1 or beam/PL- RS#2) is set/instructed. In this embodiment, operation switching as shown in FIGS. 7A and 7B will be described.
- the UE when the UE is scheduled to PUSCH using a specific DCI format (e.g., DCI format 0_0)" in the first embodiment, "the UE is set to the default beam operation may be read as "when a PUSCH for which a PL-RS/spatial relationship is not set is scheduled” or "when a PUSCH for which no PL-RS/spatial relationship is set" is scheduled.
- a specific DCI format e.g., DCI format 0_0
- the UE may assume that a different beam/PL-RS is configured for each iteration (transmission opportunity).
- UE is Rel. Even if it is assumed that a different beam / PL-RS is set / indicated for each transmission opportunity of repeated transmission of PUSCH when a specific upper layer parameter (eg, enableDefaultBeamPL-ForSRS_r17) specified after 17 is set. good.
- a specific upper layer parameter eg, enableDefaultBeamPL-ForSRS_r17
- the UE is configured with a specific higher layer parameter (e.g. enableDefaultBeamPL-ForSRS) and a specific DCI format (e.g. DCI format 0_1/0_2) containing multiple SRI fields/TPMI fields/TPC command fields.
- a specific higher layer parameter e.g. enableDefaultBeamPL-ForSRS
- a specific DCI format e.g. DCI format 0_1/0_2
- a different beam/PL-RS is set/indicated for each transmission opportunity of the repeated PUSCH transmission when the repeated PUSCH transmission is scheduled in .
- a specific A DCI format (eg, DCI format 0_1/0_2) may not include a particular field (eg, an SRI field).
- the UE may specify certain higher layer parameters (eg, enableDefaultBeamPL-ForSRS) and Rel. 17 and later specified upper layer parameters (eg, enableDefaultBeamPL-ForSRS_r17) are set, a specific DCI format (eg, DCI format 0_1/0_2) that schedules PUSCH, a specific field ( For example, it may be assumed that the SRI field) is not included.
- certain higher layer parameters eg, enableDefaultBeamPL-ForSRS
- Rel. 17 and later specified upper layer parameters eg, enableDefaultBeamPL-ForSRS_r17
- a specific DCI format eg, DCI format 0_1/0_2
- a specific field For example, it may be assumed that the SRI field
- Certain DCI formats may include certain fields (eg, TPMI field/TPC command field).
- a particular DCI format (eg, DCI format 0_1/0_2) may not include a particular field (eg, TPMI field/TPC command field).
- the UE may determine/judge the value of the TPMI field/value of the TPC command field based on certain rules. Such specific rules may be predefined in the specification or may be configured in the UE via higher layer signaling.
- FIGS. 8A and 8B are diagrams showing an example of a DCI format for setting repeated transmission of PUSCH based on a single DCI.
- the DCI format includes two SRI fields (SRI#1 and SRI#2), two TPMI fields (TPMI#1 and TPMI#2), and two TPC command fields (TPC#1 and TPC#2).
- the DCI format includes two TPMI fields (TPMI#1 and TPMI#2) and two TPC command fields (TPC#1 and TPC#2).
- DCI overhead can be reduced by defining the DCI format for default beam operation as shown in FIGS. 8A and 8B.
- a DCI format (e.g., DCI format) in which a specific upper layer parameter (e.g., enableDefaultBeamPL-ForSRS) is set for the UE and a plurality of specific fields (e.g., SRI field/TPMI field/TPC command field) are included 0_1/0_2), the UE will still be able to schedule PUSCH on Rel. 15/16 (using one default spatial relationship/PL-RS as in FIG. 7A) may be performed.
- a specific upper layer parameter e.g., enableDefaultBeamPL-ForSRS
- a specific fields e.g., SRI field/TPMI field/TPC command field
- a UE that performs repeated transmission of PUSCH based on a single DCI may not operate using the default spatial relationship/PL-RS.
- the spatial relationship/PL-RS for that PUSCH is always configured.
- Each embodiment of the present disclosure provides that when the UE reports to the NW UE capabilities corresponding to at least one of the following, and to the UE, the at least one of the following UE capabilities is configured/activated/indicated by higher layer signaling: may be applied under conditions of at least one of Embodiments of the present disclosure may apply when certain higher layer parameters are configured/activated/indicated for the UE.
- the UE capability may be defined by whether repeated transmission of PUSCH based on a single DCI for multiple TRPs is supported.
- the UE capability may also be defined as to whether or not different SRI/TPMI/TPC command fields are supported for each transmission opportunity for repeated PUSCH transmissions.
- the UE capability may be defined by the number of PUSCH repetitions.
- the UE capability may be defined by the number of active beams/number of PL-RSs for repeated transmission of PUSCH.
- the UE capability may be defined by whether or not the default spatial relationship/PL-RS for repeated transmission of PUSCH is supported.
- the UE capability is whether the default spatial relationship/PL-RS for repeated transmission of PUSCH to determine one beam/PL-RS per PUCCH resource/CORESET/SRS resource in embodiment 1-1 is supported may be defined as
- the UE can implement the method described in the above embodiments while maintaining compatibility with existing specifications.
- wireless communication system A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
- communication is performed using any one of the radio communication methods according to the above embodiments of the present disclosure or a combination thereof.
- FIG. 9 is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment.
- the wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by the Third Generation Partnership Project (3GPP). .
- LTE Long Term Evolution
- 5G NR 5th generation mobile communication system New Radio
- 3GPP Third Generation Partnership Project
- the wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
- RATs Radio Access Technologies
- MR-DC is dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)), etc.
- RATs Radio Access Technologies
- MR-DC is dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)), etc.
- LTE Evolved Universal Terrestrial Radio Access
- EN-DC E-UTRA-NR Dual Connectivity
- NE-DC NR-E -UTRA Dual Connectivity
- the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN).
- the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
- the wireless communication system 1 has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB) )) may be supported.
- dual connectivity NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB)
- gNB NR base stations
- a wireless communication system 1 includes a base station 11 forming a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) arranged in the macrocell C1 and forming a small cell C2 narrower than the macrocell C1. You may prepare.
- a user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminals 20 are not limited to the embodiment shown in the figure.
- the base stations 11 and 12 are collectively referred to as the base station 10 when not distinguished.
- the user terminal 20 may connect to at least one of the multiple base stations 10 .
- the user terminal 20 may utilize at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).
- CA carrier aggregation
- CC component carriers
- DC dual connectivity
- Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)).
- Macrocell C1 may be included in FR1, and small cell C2 may be included in FR2.
- FR1 may be a frequency band below 6 GHz (sub-6 GHz)
- FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
- the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
- TDD Time Division Duplex
- FDD Frequency Division Duplex
- a plurality of base stations (eg, RRH) 10 may be connected by wire (eg, Common Public Radio Interface (CPRI) compliant optical fiber, X2 interface, etc.) or wirelessly (eg, NR communication).
- CPRI Common Public Radio Interface
- NR communication e.g, NR communication
- the base station 11 corresponding to the upper station is an Integrated Access Backhaul (IAB) donor
- the base station 12 corresponding to the relay station (relay) is an IAB Also called a node.
- IAB Integrated Access Backhaul
- the base station 10 may be connected to the core network 30 directly or via another base station 10 .
- the core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.
- EPC Evolved Packet Core
- 5GCN 5G Core Network
- NGC Next Generation Core
- the user terminal 20 may be a terminal compatible with at least one of communication schemes such as LTE, LTE-A, and 5G.
- a radio access scheme based on orthogonal frequency division multiplexing may be used.
- OFDM orthogonal frequency division multiplexing
- CP-OFDM Cyclic Prefix OFDM
- DFT-s-OFDM Discrete Fourier Transform Spread OFDM
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single Carrier Frequency Division Multiple Access
- a radio access method may be called a waveform.
- other radio access schemes for example, other single-carrier transmission schemes and other multi-carrier transmission schemes
- the UL and DL radio access schemes may be used as the UL and DL radio access schemes.
- a downlink shared channel Physical Downlink Shared Channel (PDSCH)
- PDSCH Physical Downlink Shared Channel
- PBCH Physical Broadcast Channel
- PDCCH Physical Downlink Control Channel
- an uplink shared channel (PUSCH) shared by each user terminal 20 an uplink control channel (PUCCH), a random access channel (Physical Random Access Channel (PRACH)) or the like may be used.
- PUSCH uplink shared channel
- PUCCH uplink control channel
- PRACH Physical Random Access Channel
- User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH.
- User data, higher layer control information, and the like may be transmitted by PUSCH.
- a Master Information Block (MIB) may be transmitted by the PBCH.
- Lower layer control information may be transmitted by the PDCCH.
- the lower layer control information may include, for example, downlink control information (DCI) including scheduling information for at least one of PDSCH and PUSCH.
- DCI downlink control information
- the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc.
- the DCI that schedules PUSCH may be called UL grant, UL DCI, etc.
- PDSCH may be replaced with DL data
- PUSCH may be replaced with UL data.
- a control resource set (CControl Resource SET (CORESET)) and a search space (search space) may be used for PDCCH detection.
- CORESET corresponds to a resource searching for DCI.
- the search space corresponds to the search area and search method of PDCCH candidates.
- a CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with certain search spaces based on the search space settings.
- One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels.
- One or more search spaces may be referred to as a search space set. Note that “search space”, “search space set”, “search space setting”, “search space set setting”, “CORESET”, “CORESET setting”, etc. in the present disclosure may be read interchangeably.
- PUCCH channel state information
- acknowledgment information for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.
- SR scheduling request
- a random access preamble for connection establishment with a cell may be transmitted by the PRACH.
- downlink, uplink, etc. may be expressed without adding "link”.
- various channels may be expressed without adding "Physical" to the head.
- synchronization signals SS
- downlink reference signals DL-RS
- the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), Positioning Reference Signal (PRS)), Phase Tracking Reference Signal (PTRS)), etc.
- CRS cell-specific reference signal
- CSI-RS channel state information reference signal
- DMRS Demodulation reference signal
- PRS Positioning Reference Signal
- PTRS Phase Tracking Reference Signal
- the synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).
- PSS Primary Synchronization Signal
- SSS Secondary Synchronization Signal
- a signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called SS/PBCH block, SS Block (SSB), and so on.
- SS, SSB, etc. may also be referred to as reference signals.
- DMRS may also be called a user terminal-specific reference signal (UE-specific reference signal).
- FIG. 10 is a diagram illustrating an example of the configuration of a base station according to one embodiment.
- the base station 10 includes a control section 110 , a transmission/reception section 120 , a transmission/reception antenna 130 and a transmission line interface 140 .
- One or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140 may be provided.
- this example mainly shows the functional blocks that characterize the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
- the control unit 110 controls the base station 10 as a whole.
- the control unit 110 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.
- the control unit 110 may control signal generation, scheduling (eg, resource allocation, mapping), and the like.
- the control unit 110 may control transmission/reception, measurement, etc. using the transmission/reception unit 120 , the transmission/reception antenna 130 and the transmission line interface 140 .
- the control unit 110 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer them to the transmission/reception unit 120 .
- the control unit 110 may perform call processing (setup, release, etc.) of communication channels, state management of the base station 10, management of radio resources, and the like.
- the transmitting/receiving section 120 may include a baseband section 121 , a radio frequency (RF) section 122 and a measuring section 123 .
- the baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212 .
- the transmitting/receiving unit 120 is configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure. be able to.
- the transmission/reception unit 120 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit.
- the transmission section may be composed of the transmission processing section 1211 and the RF section 122 .
- the receiving section may be composed of a reception processing section 1212 , an RF section 122 and a measurement section 123 .
- the transmitting/receiving antenna 130 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.
- the transmitting/receiving unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, and the like.
- the transmitting/receiving unit 120 may receive the above-described uplink channel, uplink reference signal, and the like.
- the transmitting/receiving unit 120 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.
- digital beamforming eg, precoding
- analog beamforming eg, phase rotation
- the transmission/reception unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Control
- HARQ retransmission control for example, HARQ retransmission control
- the transmission/reception unit 120 (transmission processing unit 1211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (DFT) on the bit string to be transmitted. Processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-to-analog conversion may be performed, and the baseband signal may be output.
- channel coding which may include error correction coding
- modulation modulation
- mapping mapping
- filtering filtering
- DFT discrete Fourier transform
- DFT discrete Fourier transform
- the transmitting/receiving unit 120 may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 130. .
- the transmitting/receiving unit 120 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 130.
- the transmission/reception unit 120 (reception processing unit 1212) performs analog-to-digital conversion, Fast Fourier transform (FFT) processing, and Inverse Discrete Fourier transform (IDFT) processing on the acquired baseband signal. )) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing. User data and the like may be acquired.
- FFT Fast Fourier transform
- IDFT Inverse Discrete Fourier transform
- the transmitting/receiving unit 120 may measure the received signal.
- the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal.
- the measurement unit 123 measures received power (for example, Reference Signal Received Power (RSRP)), reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)) , signal strength (for example, Received Signal Strength Indicator (RSSI)), channel information (for example, CSI), and the like may be measured.
- RSRP Reference Signal Received Power
- RSSQ Reference Signal Received Quality
- SINR Signal to Noise Ratio
- RSSI Received Signal Strength Indicator
- channel information for example, CSI
- the transmission path interface 140 transmits and receives signals (backhaul signaling) to and from devices included in the core network 30, other base stations 10, etc., and user data (user plane data) for the user terminal 20, control plane data, and the like. Data and the like may be obtained, transmitted, and the like.
- the transmitter and receiver of the base station 10 in the present disclosure may be configured by at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission line interface 140.
- the transmitting/receiving unit 120 may transmit information regarding settings for transmission of a plurality of physical uplink shared channels (PUSCH) based on one downlink control information (DCI).
- the control unit 110 controls reception of the plurality of PUSCHs to which at least one of a spatial relationship in which one or more reference signal indices out of a plurality of reference signal indices are used and a path loss reference signal (PL-RS) is applied.
- PUSCH physical uplink shared channels
- DCI downlink control information
- the control unit 110 controls reception of the plurality of PUSCHs to which at least one of a spatial relationship in which one or more reference signal indices out of a plurality of reference signal indices are used and a path loss reference signal (PL-RS) is applied.
- PL-RS path loss reference signal
- FIG. 11 is a diagram illustrating an example of the configuration of a user terminal according to one embodiment.
- the user terminal 20 includes a control section 210 , a transmission/reception section 220 and a transmission/reception antenna 230 .
- One or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.
- this example mainly shows the functional blocks of the features of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
- the control unit 210 controls the user terminal 20 as a whole.
- the control unit 210 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.
- the control unit 210 may control signal generation, mapping, and the like.
- the control unit 210 may control transmission/reception, measurement, etc. using the transmission/reception unit 220 and the transmission/reception antenna 230 .
- the control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission/reception unit 220 .
- the transmitting/receiving section 220 may include a baseband section 221 , an RF section 222 and a measurement section 223 .
- the baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212 .
- the transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure.
- the transmission/reception unit 220 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit.
- the transmission section may be composed of a transmission processing section 2211 and an RF section 222 .
- the receiving section may include a reception processing section 2212 , an RF section 222 and a measurement section 223 .
- the transmitting/receiving antenna 230 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.
- the transmitting/receiving unit 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, and the like.
- the transmitting/receiving unit 220 may transmit the above-described uplink channel, uplink reference signal, and the like.
- the transmitter/receiver 220 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.
- digital beamforming eg, precoding
- analog beamforming eg, phase rotation
- the transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, for data and control information acquired from the control unit 210, for example , HARQ retransmission control), etc., to generate a bit string to be transmitted.
- RLC layer processing for example, RLC retransmission control
- MAC layer processing for example, for data and control information acquired from the control unit 210, for example , HARQ retransmission control
- the transmitting/receiving unit 220 (transmission processing unit 2211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), and IFFT processing on a bit string to be transmitted. , precoding, digital-analog conversion, and other transmission processing may be performed, and the baseband signal may be output.
- Whether or not to apply DFT processing may be based on transform precoding settings. Transmitting/receiving unit 220 (transmission processing unit 2211), for a certain channel (for example, PUSCH), if transform precoding is enabled, the above to transmit the channel using the DFT-s-OFDM waveform
- the DFT process may be performed as the transmission process, or otherwise the DFT process may not be performed as the transmission process.
- the transmitting/receiving unit 220 may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 230. .
- the transmitting/receiving section 220 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 230.
- the transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (error correction) on the acquired baseband signal. decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.
- the transmitting/receiving section 220 may measure the received signal.
- the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal.
- the measuring unit 223 may measure received power (eg, RSRP), received quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and the like.
- the measurement result may be output to control section 210 .
- the transmitter and receiver of the user terminal 20 in the present disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230 .
- the transmitting/receiving unit 220 may receive information regarding settings for transmission of a plurality of physical uplink shared channels (PUSCH) based on one downlink control information (DCI).
- the control unit 210 may determine one or more reference signal indices to be used for at least one of spatial relationships and pathloss reference signals (PL-RS) for the plurality of PUSCHs from the plurality of reference signal indices.
- PUSCH physical uplink shared channels
- DCI downlink control information
- the control unit 210 may determine one or more reference signal indices to be used for at least one of spatial relationships and pathloss reference signals (PL-RS) for the plurality of PUSCHs from the plurality of reference signal indices.
- PL-RS pathloss reference signals
- the control unit 210 may determine at least one of the number of the spatial relationships and the PL-RSs for the plurality of PUSCHs based on the number of beams applied to the PUSCHs (first embodiment).
- the control unit 210 may assume that different PL-RSs are applied to each of the plurality of PUSCH transmission opportunities when a specific higher layer parameter is set (second embodiment).
- the DCI format may be at least one of DCI format 0_1 and DCI format 0_2.
- the DCI may not include a Sounding Reference Signal Resource Indicator (SRI) field.
- SRI Sounding Reference Signal Resource Indicator
- each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices.
- a functional block may be implemented by combining software in the one device or the plurality of devices.
- function includes judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deem , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc.
- a functional block (component) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.
- a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
- FIG. 12 is a diagram illustrating an example of hardware configurations of a base station and user terminals according to an embodiment.
- the base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. .
- the hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.
- processor 1001 may be implemented by one or more chips.
- predetermined software program
- the processor 1001 performs calculations, communication via the communication device 1004 and at least one of reading and writing data in the memory 1002 and the storage 1003 .
- the processor 1001 operates an operating system and controls the entire computer.
- the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like.
- CPU central processing unit
- control unit 110 210
- transmission/reception unit 120 220
- FIG. 10 FIG. 10
- the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them.
- programs program codes
- software modules software modules
- data etc.
- the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be similarly implemented.
- the memory 1002 is a computer-readable recording medium, such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or at least any other suitable storage medium. may be configured by one.
- the memory 1002 may also be called a register, cache, main memory (main storage device), or the like.
- the memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.
- the storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also be called an auxiliary storage device.
- a computer-readable recording medium for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also
- the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like.
- the communication device 1004 includes a high-frequency switch, duplexer, filter, frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD), for example. may be configured to include
- the transmitting/receiving unit 120 (220), the transmitting/receiving antenna 130 (230), and the like described above may be realized by the communication device 1004.
- the transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).
- the input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside.
- the output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
- Each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
- the bus 1007 may be configured using a single bus, or may be configured using different buses between devices.
- the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured including hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.
- DSP digital signal processor
- ASIC application specific integrated circuit
- PLD programmable logic device
- FPGA field programmable gate array
- a signal may also be a message.
- a reference signal may be abbreviated as RS, and may also be called a pilot, a pilot signal, etc., depending on the applicable standard.
- a component carrier may also be called a cell, a frequency carrier, a carrier frequency, or the like.
- a radio frame may consist of one or more periods (frames) in the time domain.
- Each of the one or more periods (frames) that make up a radio frame may be called a subframe.
- a subframe may consist of one or more slots in the time domain.
- a subframe may be a fixed time length (eg, 1 ms) independent of numerology.
- a numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel.
- Numerology for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration , a particular filtering process performed by the transceiver in the frequency domain, a particular windowing process performed by the transceiver in the time domain, and/or the like.
- a slot may consist of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain.
- OFDM Orthogonal Frequency Division Multiplexing
- SC-FDMA Single Carrier Frequency Division Multiple Access
- a slot may also be a unit of time based on numerology.
- a slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot.
- a PDSCH (or PUSCH) transmitted in time units larger than a minislot may be referred to as PDSCH (PUSCH) Mapping Type A.
- PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.
- Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.
- one subframe may be called a TTI
- a plurality of consecutive subframes may be called a TTI
- one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.
- TTI refers to, for example, the minimum scheduling time unit in wireless communication.
- a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis.
- radio resources frequency bandwidth, transmission power, etc. that can be used by each user terminal
- a TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.
- one or more TTIs may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
- a TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, or the like.
- a TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.
- the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms
- the short TTI e.g., shortened TTI, etc.
- a TTI having the above TTI length may be read instead.
- a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain.
- the number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve.
- the number of subcarriers included in an RB may be determined based on neumerology.
- an RB may contain one or more symbols in the time domain and may be 1 slot, 1 minislot, 1 subframe or 1 TTI long.
- One TTI, one subframe, etc. may each be configured with one or more resource blocks.
- One or more RBs are Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB Also called a pair.
- PRB Physical Resource Block
- SCG Sub-Carrier Group
- REG Resource Element Group
- PRB pair RB Also called a pair.
- a resource block may be composed of one or more resource elements (Resource Element (RE)).
- RE resource elements
- 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
- a Bandwidth Part (which may also be called a bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a numerology on a carrier.
- the common RB may be identified by an RB index based on the common reference point of the carrier.
- PRBs may be defined in a BWP and numbered within that BWP.
- BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL).
- BWP for UL
- BWP for DL DL BWP
- One or multiple BWPs may be configured for a UE within one carrier.
- At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP.
- BWP bitmap
- radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples.
- the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc. can be varied.
- the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indicated by a predetermined index.
- data, instructions, commands, information, signals, bits, symbols, chips, etc. may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of
- information, signals, etc. can be output from a higher layer to a lower layer and/or from a lower layer to a higher layer.
- Information, signals, etc. may be input and output through multiple network nodes.
- Input/output information, signals, etc. may be stored in a specific location (for example, memory), or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated or appended. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to other devices.
- Uplink Control Information (UCI) Uplink Control Information
- RRC Radio Resource Control
- MIB Master Information Block
- SIB System Information Block
- SIB System Information Block
- MAC Medium Access Control
- the physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), and the like.
- RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.
- MAC signaling may be notified using, for example, a MAC Control Element (CE).
- CE MAC Control Element
- notification of predetermined information is not limited to explicit notification, but implicit notification (for example, by not notifying the predetermined information or by providing another information by notice of
- the determination may be made by a value (0 or 1) represented by 1 bit, or by a boolean value represented by true or false. , may be performed by numerical comparison (eg, comparison with a predetermined value).
- Software whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.
- software, instructions, information, etc. may be transmitted and received via a transmission medium.
- the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) , a server, or other remote source, these wired and/or wireless technologies are included within the definition of transmission media.
- a “network” may refer to devices (eg, base stations) included in a network.
- precoding "precoding weight”
- QCL Quality of Co-Location
- TCI state Transmission Configuration Indication state
- spatialal patial relation
- spatialal domain filter "transmission power”
- phase rotation "antenna port
- antenna port group "layer”
- number of layers Terms such as “rank”, “resource”, “resource set”, “resource group”, “beam”, “beam width”, “beam angle”, “antenna”, “antenna element”, “panel” are interchangeable. can be used as intended.
- base station BS
- radio base station fixed station
- NodeB NodeB
- eNB eNodeB
- gNB gNodeB
- Access point "Transmission Point (TP)”, “Reception Point (RP)”, “Transmission/Reception Point (TRP)”, “Panel”
- a base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.
- a base station can accommodate one or more (eg, three) cells.
- the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is assigned to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head (RRH))) may also provide communication services.
- a base station subsystem e.g., a small indoor base station (Remote Radio)). Head (RRH)
- RRH Head
- the terms "cell” or “sector” refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.
- MS Mobile Station
- UE User Equipment
- Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , a handset, a user agent, a mobile client, a client, or some other suitable term.
- At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like.
- At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like.
- the mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ).
- at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations.
- at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.
- IoT Internet of Things
- the base station in the present disclosure may be read as a user terminal.
- communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.)
- the user terminal 20 may have the functions of the base station 10 described above.
- words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
- uplink channels, downlink channels, etc. may be read as side channels.
- user terminals in the present disclosure may be read as base stations.
- the base station 10 may have the functions of the user terminal 20 described above.
- operations that are assumed to be performed by the base station may be performed by its upper node in some cases.
- various operations performed for communication with a terminal may involve the base station, one or more network nodes other than the base station (e.g., Clearly, this can be done by a Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. (but not limited to these) or a combination thereof.
- MME Mobility Management Entity
- S-GW Serving-Gateway
- each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching along with execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- LTE-B LTE-Beyond
- SUPER 3G IMT-Advanced
- 4G 4th generation mobile communication system
- 5G 5th generation mobile communication system
- 6G 6th generation mobile communication system
- xG xG (xG (x is, for example, an integer or a decimal number)
- Future Radio Access FAA
- RAT New - Radio Access Technology
- NR New Radio
- NX New radio access
- FX Future generation radio access
- GSM registered trademark
- CDMA2000 Code Division Multiple Access
- UMB Ultra Mobile Broadband
- IEEE 802.11 Wi-Fi®
- IEEE 802.16 WiMAX®
- IEEE 802.20 Ultra-WideBand (UWB), Bluetooth®, or other suitable wireless It may be applied to systems using communication methods, next-generation systems extended based on these, and the like. Also, multiple systems may be applied to systems using communication methods, next-generation systems extended based on these, and the like
- any reference to elements using the "first,” “second,” etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, references to first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.
- determining includes judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry ( For example, looking up in a table, database, or another data structure), ascertaining, etc. may be considered to be “determining.”
- determining (deciding) includes receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access ( accessing (e.g., accessing data in memory), etc.
- determining is considered to be “determining” resolving, selecting, choosing, establishing, comparing, etc. good too. That is, “determining (determining)” may be regarded as “determining (determining)” some action.
- connection refers to any connection or coupling, direct or indirect, between two or more elements. and can include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other. Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection” may be read as "access”.
- radio frequency domain when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, radio frequency domain, microwave They can be considered to be “connected” or “coupled” together using the domain, electromagnetic energy having wavelengths in the optical (both visible and invisible) domain, and the like.
- a and B are different may mean “A and B are different from each other.”
- the term may also mean that "A and B are different from C”.
- Terms such as “separate,” “coupled,” etc. may also be interpreted in the same manner as “different.”
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Rel.15では、データ送信において繰り返し送信がサポートされている。例えば、基地局(ネットワーク(NW)、gNB)は、DLデータ(例えば、下り共有チャネル(PDSCH))の送信を所定回数だけ繰り返して行う。あるいは、UEは、ULデータ(例えば、上り共有チャネル(PUSCH))の送信を所定回数だけ繰り返して行う。
・時間領域リソース(例えば、開始シンボル、各スロット内のシンボル数等)の割り当て、
・周波数領域リソース(例えば、所定数のリソースブロック(RB:Resource Block)、所定数のリソースブロックグループ(RBG:Resource Block Group))の割り当て、
・変調及び符号化方式(MCS:Modulation and Coding Scheme)インデックス、
・PUSCHの復調用参照信号(DMRS:Demodulation Reference Signal)の構成(configuration)、
・PUSCHの空間関係情報(spatial relation info)、又は送信構成指示(TCI:Transmission Configuration Indication又はTransmission Configuration Indicator)の状態(TCI状態(TCI-state))。
PUSCH送信に対して繰り返し送信タイプBを適用する場合、PUSCH送信に利用できないシンボル(又は、シンボルパターン)に関する情報をUEに通知することも検討されている。PUSCH送信に利用できないシンボルパターンは、無効シンボルパターン、Invalid symbol pattern、インバリッドシンボルパターン等と呼ばれてもよい。
繰り返し送信タイプBを適用してサブスロット単位で繰り返し送信が行われる場合、繰り返し係数(K)及びデータの割当て単位等によっては、ある繰り返し送信がスロット境界(slot-boundary)をクロス(cross)するケースが生じる。
Rel.15 NRにおいて、UEは、測定用参照信号(例えば、サウンディング参照信号(Sounding Reference Signal(SRS)))の送信に用いられる情報(SRS設定情報、例えば、RRC制御要素の「SRS-Config」内のパラメータ)を受信してもよい。
Rel.16において、コードブックベースのPUSCH送信のための、送信プリコーディング行列インジケータ(Transmitted Precoding Matrix Indicator(TPMI))及び送信ランクが、下りリンク制御情報(例えば、DCIフォーマット0_1)に含まれる特定のフィールド(例えば、プリコーディング情報及びレイヤ数フィールド)によって指定されることが検討されている。
上りリンク共有チャネル(Physical Uplink Shared Channel(PUSCH))、上りリンク制御チャネル(Physical Uplink Control Channel(PUCCH))、測定用参照信号(Sounding Reference Signal(SRS))のそれぞれの送信電力制御におけるパスロスPLb,f,c(qd)[dB]は、サービングセルcのキャリアfのアクティブUL BWP bに関連付けられる下りBWP用の参照信号(RS、パスロス参照RS(PathlossReferenceRS))のインデックスqdを用いてUEによって計算される。
Rel.15 NRにおいては、PUCCH空間関係のアクティベーション/ディアクティベーション用のMAC CEと、SRS空間関係のアクティベーション/ディアクティベーション用のMAC CEと、の個々のMAC CEが必要である。PUSCH空間関係は、SRS空間関係に従う。
NRでは、1つ又は複数の送受信ポイント(Transmission/Reception Point(TRP))(マルチTRP)が、1つ又は複数のパネル(マルチパネル)を用いて、UEに対してDL送信を行うことが検討されている。また、UEが、1つ又は複数のTRPに対してUL送信を行うことが検討されている(図4参照)。
UEは、複数TRP向けのPUSCHの繰り返し送信を行うことを決定するとき、複数のSRIと、複数の繰り返し送信とが、特定のルールに基づいて対応することを判断してもよい。当該ルールは、マッピングパターン、マッピングルール、対応パターン、対応関係、などと呼ばれてもよい。UEは、PUSCHの繰り返し数が、PUSCH送信に用いるビーム数を超えると想定してもよい。
<第1の実施形態>
第1の実施形態では、UEは、単一DCIに基づくPUSCHの繰り返し送信(S-DCI based PUSCH repetition)が設定され、SRIフィールドを有しない(又は含まない)DCIフォーマット(例えば、DCIフォーマット0_0)を用いてPUSCHがスケジュールされてもよい。UEに対し、単一DCIに基づくPUSCHの繰り返し送信が設定されることは、特定のDCIフォーマット(例えば、DCIフォーマット0_1/0_2)に、複数のSRIフィールド/TPMIフィールド/TPCコマンドフィールドが設定されることであってもよい。
条件2:PUSCHのPL-RS/空間関係を決定するために用いられるCORESET(関連する(associated)CORESET)に対して複数のTCI状態が設定される、
条件3:PUSCHのPL-RS/空間関係を決定するために用いられるSRSリソース(関連する(associated)SRSリソース)に対して複数のTCI状態が設定される、
条件4:特定のDCIフォーマット(例えば、DCIフォーマット0_0)を用いてスケジュールされるPUSCHの繰り返し送信を設定/有効(enabled)/アクティベートする上位レイヤパラメータが設定される。
条件5:PUSCHについてのPL-RS/空間関係のためのPUCCHリソース/CORESET/SRSリソース又は参照先のRS(CSI-RS、SSB、SRSなど)に複数の空間関係/TCI状態が設定される。
以下では、上記実施形態1-1における、PUSCH送信のための1つのPL-RS/空間関係の決定方法について説明する。
ルール1:最大(最小)の空間関係ID/TCI状態IDに対応する空間関係/TCI状態、
ルール2:最大(最小)のPUCCHリソースID/CORESET ID/SRSリソースIDに対応する空間関係/TCI状態、
ルール3:PUCCHリソース/CORESET/SRSリソースごとに、第1/第2のビーム/リソースが設定されるときの、第1/第2の空間関係ID/TCI状態ID/PUCCHリソースID/CORESET ID/SRSリソースIDに対応する空間関係/TCI状態、
ルール4:上位レイヤシグナリングで設定される特定のルールに従って決定/選択される1つの空間関係/TCI状態、
ルール5:上位レイヤシグナリングで設定/指示される特定の(正確な(exact))空間関係ID/TCI状態IDに対応する空間関係/TCI状態。
以下では、上記実施形態1-2における、PUSCHの繰り返し送信のための複数のPL-RS/空間関係の決定方法について説明する。
ルール1:最大(最小)の空間関係ID/TCI状態IDから降順(昇順)に、X個の空間関係ID/TCI状態IDに対応する空間関係/TCI状態、
ルール2:最大(最小)のPUCCHリソースID/CORESET ID/SRSリソースIDから降順(昇順)に、X個のPUCCHリソースID/CORESET ID/SRSリソースIDに対応する空間関係/TCI状態、
ルール3:PUCCHリソース/CORESET/SRSリソースごとに、第1/第2のビーム/リソースが設定されるときの、第1/第2の空間関係ID/TCI状態ID/PUCCHリソースID/CORESET ID/SRSリソースIDに対応する空間関係/TCI状態、
ルール4:上位レイヤシグナリングで設定される特定のルールに従って決定/選択されるX個の空間関係/TCI状態、
ルール5:上位レイヤシグナリングで設定/指示されるX個の特定の(正確な(exact))空間関係ID/TCI状態IDに対応する空間関係/TCI状態。
ルール6:N番目(Nは2以上の整数)/最大/最小のPUCCHリソースID/CORESET IDに対応する空間関係/TCI状態、
ルール7:Y個の空間関係/TCI状態の決定に用いられる、上位レイヤシグナリングで設定/指示される特定の(正確な(exact))空間関係ID/TCI状態IDに対応する空間関係/TCI状態。
第2の実施形態では、UEは、SRIフィールドを有する特定のDCIフォーマット(例えば、DCIフォーマット0_1/0_2)でスケジュールされるPUSCHの繰り返し送信に対し、第1の実施形態で記載した方法で、デフォルトPL-RS/空間関係を適用してもよい。
UEに対し、特定の上位レイヤパラメータ(例えば、enableDefaultBeamPL-ForSRS)が設定され、かつ、複数の特定のフィールド(例えば、SRIフィールド/TPMIフィールド/TPCコマンドフィールド)が含まれるDCIフォーマット(例えば、DCIフォーマット0_1/0_2)でPUSCHがスケジュールされる場合であっても、UEは、Rel.15/16で規定されるPUSCHの繰り返し送信の動作(図7Aのような1つのデフォルト空間関係/PL-RSを用いる動作)を行ってもよい。
本開示の各実施形態は、UEが、下記少なくとも1つに対応するUE能力をNWに報告した場合、および、UEに対して、下記少なくとも1つのUE能力について上位レイヤシグナリングによって設定/アクティベート/指示された場合、の少なくとも一方の条件下において適用されてもよい。本開示の各実施形態は、UEに対して、特定の上位レイヤパラメータが設定/アクティベート/指示された場合において適用されてもよい。
以下、本開示の一実施形態に係る無線通信システムの構成について説明する。この無線通信システムでは、本開示の上記各実施形態に係る無線通信方法のいずれか又はこれらの組み合わせを用いて通信が行われる。
図10は、一実施形態に係る基地局の構成の一例を示す図である。基地局10は、制御部110、送受信部120、送受信アンテナ130及び伝送路インターフェース(transmission line interface)140を備えている。なお、制御部110、送受信部120及び送受信アンテナ130及び伝送路インターフェース140は、それぞれ1つ以上が備えられてもよい。
図11は、一実施形態に係るユーザ端末の構成の一例を示す図である。ユーザ端末20は、制御部210、送受信部220及び送受信アンテナ230を備えている。なお、制御部210、送受信部220及び送受信アンテナ230は、それぞれ1つ以上が備えられてもよい。
なお、上記実施形態の説明に用いたブロック図は、機能単位のブロックを示している。これらの機能ブロック(構成部)は、ハードウェア及びソフトウェアの少なくとも一方の任意の組み合わせによって実現される。また、各機能ブロックの実現方法は特に限定されない。すなわち、各機能ブロックは、物理的又は論理的に結合した1つの装置を用いて実現されてもよいし、物理的又は論理的に分離した2つ以上の装置を直接的又は間接的に(例えば、有線、無線などを用いて)接続し、これら複数の装置を用いて実現されてもよい。機能ブロックは、上記1つの装置又は上記複数の装置にソフトウェアを組み合わせて実現されてもよい。
なお、本開示において説明した用語及び本開示の理解に必要な用語については、同一の又は類似する意味を有する用語と置き換えてもよい。例えば、チャネル、シンボル及び信号(シグナル又はシグナリング)は、互いに読み替えられてもよい。また、信号はメッセージであってもよい。参照信号(reference signal)は、RSと略称することもでき、適用される標準によってパイロット(Pilot)、パイロット信号などと呼ばれてもよい。また、コンポーネントキャリア(Component Carrier(CC))は、セル、周波数キャリア、キャリア周波数などと呼ばれてもよい。
Claims (6)
- 1つの下りリンク制御情報(DCI)に基づく複数の物理上りリンク共有チャネル(PUSCH)の送信の設定に関する情報を受信する受信部と、
複数の参照信号インデックスから、前記複数のPUSCHについての空間関係及びパスロス参照信号(PL-RS)の少なくとも一方のために利用される1以上の参照信号インデックスを決定する制御部と、を有する端末。 - 前記制御部は、前記PUSCHに適用するビームの数に基づいて、前記複数のPUSCHについての前記空間関係及び前記PL-RSの少なくとも一方の数を判断する請求項1に記載の端末。
- 前記制御部は、特定の上位レイヤパラメータが設定される場合に、前記複数のPUSCHの各送信機会に対して異なるPL-RSが適用されると想定する請求項1に記載の端末。
- 前記DCIのフォーマットは、DCIフォーマット0_1及びDCIフォーマット0_2の少なくとも一方であり、
前記DCIに、サウンディング参照信号リソースインジケータ(Sounding Reference Signal Resource Indicator(SRI))フィールドが含まれない請求項1に記載の端末。 - 1つの下りリンク制御情報(DCI)に基づく複数の物理上りリンク共有チャネル(PUSCH)の送信の設定に関する情報を受信するステップと、
複数の参照信号インデックスから、前記複数のPUSCHについての空間関係及びパスロス参照信号(PL-RS)の少なくとも一方のために利用される1以上の参照信号インデックスを決定するステップと、を有する端末の無線通信方法。 - 1つの下りリンク制御情報(DCI)に基づく複数の物理上りリンク共有チャネル(PUSCH)の送信の設定に関する情報を送信する送信部と、
複数の参照信号インデックスのうちの1以上の参照信号インデックスが利用される空間関係及びパスロス参照信号(PL-RS)の少なくとも一方が適用される前記複数のPUSCHの受信を制御する制御部と、を有する基地局。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023503254A JPWO2022185440A5 (ja) | 2021-03-03 | 端末、無線通信方法、基地局及びシステム | |
CN202180097718.5A CN117242858A (zh) | 2021-03-03 | 2021-03-03 | 终端、无线通信方法以及基站 |
PCT/JP2021/008118 WO2022185440A1 (ja) | 2021-03-03 | 2021-03-03 | 端末、無線通信方法及び基地局 |
US18/278,327 US20240147463A1 (en) | 2021-03-03 | 2021-03-03 | Terminal, radio communication method, and base station |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/008118 WO2022185440A1 (ja) | 2021-03-03 | 2021-03-03 | 端末、無線通信方法及び基地局 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022185440A1 true WO2022185440A1 (ja) | 2022-09-09 |
Family
ID=83155191
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/008118 WO2022185440A1 (ja) | 2021-03-03 | 2021-03-03 | 端末、無線通信方法及び基地局 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20240147463A1 (ja) |
CN (1) | CN117242858A (ja) |
WO (1) | WO2022185440A1 (ja) |
-
2021
- 2021-03-03 CN CN202180097718.5A patent/CN117242858A/zh active Pending
- 2021-03-03 US US18/278,327 patent/US20240147463A1/en active Pending
- 2021-03-03 WO PCT/JP2021/008118 patent/WO2022185440A1/ja active Application Filing
Non-Patent Citations (2)
Title |
---|
MODERATOR (NOKIA): "Summary #2 of Multi-TRP for PUCCH and PUSCH", 3GPP DRAFT; R1-2101900, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 29 January 2021 (2021-01-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051975979 * |
NTT DOCOMO, INC: "Discussion on MTRP for reliability", 3GPP DRAFT; R1-2101598, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 19 January 2021 (2021-01-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051971753 * |
Also Published As
Publication number | Publication date |
---|---|
US20240147463A1 (en) | 2024-05-02 |
JPWO2022185440A1 (ja) | 2022-09-09 |
CN117242858A (zh) | 2023-12-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022149272A1 (ja) | 端末、無線通信方法及び基地局 | |
JP7305763B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
WO2021181666A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022153395A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022220109A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022149274A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022085198A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022024395A1 (ja) | 端末、無線通信方法及び基地局 | |
JP7308942B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
WO2022029979A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2021171565A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2021181667A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2021171566A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022185440A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022168812A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022163556A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022239111A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022244492A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022190237A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022190238A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022244493A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022239255A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022239254A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022249737A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2023002610A1 (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: 21929016 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18278327 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023503254 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180097718.5 Country of ref document: CN |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21929016 Country of ref document: EP Kind code of ref document: A1 |