Terminal, wireless communication method, base station and system

Abstract

A terminal according to an aspect of the present disclosure comprises: a control unit that determines, on the basis of a control resource set (CORESET) in which downlink control information (DCI) has been detected, spatial relation information for a physical uplink shared channel (PUSCH) to be scheduled according to the DCI; and a transmission unit that transmits the PUSCH by use of a precoder based on the spatial relation information. According to an aspect of the present disclosure, UL transmissions can appropriately be controlled even when multi-TRPs are used.

Description

[Technical field]

[0001] The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system. 、 base station and systems Regarding. [Background technology]

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of achieving higher capacity and greater sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In NR, communications using one or multiple transmission / reception points (TRP) (multi-TRP) are being considered.

[0006] However, if the existing Rel.15 / 16 specifications are used to transmit to multiple TRPs, there is a problem that performance, scheduling flexibility, etc. are limited. Therefore, if the existing Rel.15 / 16 specifications are used, UL transmission across M-TRPs may not be performed properly, which may result in a decrease in throughput or degradation of communication quality.

[0007] Therefore, the present disclosure provides a terminal and a wireless communication method capable of appropriately controlling UL transmission even when multi-TRP is used. 、 base station and systems One of the aims is to provide. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives one downlink control information (DCI) that schedules uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmission for a plurality of transmission / reception points (TRPs) and higher layer parameters that set power control parameters for the PUSCH transmission for the plurality of TRPs for each sounding reference signal (SRS) resource set for the PUSCH transmission; The one DCI and Based on the higher layer parameters, For the above multiple TRPs A control unit for controlling the PUSCH transmission. The higher layer parameters include a first parameter and a second parameter corresponding to different PUSCH transmissions. . Effect of the Invention

[0009] According to one embodiment of the present disclosure, UL transmission can be appropriately controlled even when multi-TRP is used. [Brief description of the drawings]

[0010] [Figure 1] 1A and 1B are diagrams illustrating an example of repeated transmission of a PUSCH. [Diagram 2] 2A and 2B are diagrams showing an example of an invalid symbol pattern. [Diagram 3] 3A and 3B are diagrams showing an example of nominal repetitions and actual repetitions. [Figure 4] FIG. 4 is a diagram illustrating an example of repeated transmission of PUSCH in multi-TRP. [Diagram 5] 5A and 5B are diagrams showing an example of a problem that occurs when attempting to transmit to an M-TRP using the existing Rel. 15 / 16 specifications. [Figure 6] FIG. 6 is a diagram illustrating an example of SRI control of a PUSCH according to the first embodiment. [Figure 7] 7A and 7B are diagrams illustrating an example of a correspondence relationship between the value of the SRI field and the SRI according to the first embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a correspondence relationship between the value of the SRI field and the SRI according to the modification of the first embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of control of the transmission power of the PUSCH according to the second embodiment. [Figure 10] FIG. 10 is a diagram showing an example of power control parameter settings in the existing Rel. 15 / 16 NR. [Figure 11] FIG. 11 is a diagram illustrating an example of power control parameter settings according to the second embodiment. [Figure 12] FIG. 12 is a diagram illustrating another example of the setting of the power control parameters according to the second embodiment. [Figure 13] 13A and 13B are diagrams illustrating an example of control of the transmission power of a PUSCH according to the third embodiment. [Figure 14] 14A and 14B are diagrams illustrating another example of control of the transmission power of the PUSCH according to the third embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] (Repeat sending) In Rel.15, repeated transmission is supported for data transmission. For example, a base station (network (NW), gNB) repeats DL data (e.g., downlink shared channel (PDSCH)) a predetermined number of times. Alternatively, a UE repeats UL data (e.g., uplink shared channel (PUSCH)) a predetermined number of times.

[0012] FIG. 1A is a diagram showing an example of repeated transmission of PUSCH. In FIG. 1A, an example is shown in which a predetermined number of repeated PUSCHs are scheduled by a single DCI. The number of repetitions is also called a repetition factor K or an aggregation factor K.

[0013] In FIG. 1A, the repetition factor K=4, but the value of K is not limited to this. In addition, the n-th repetition may be called the n-th transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K-1). In addition, FIG. 1A shows repeated transmission of a PUSCH dynamically scheduled by DCI (e.g., a dynamic grant-based PUSCH), but may be applied to repeated transmission of a configuration grant-based PUSCH.

[0014] For example, in Fig. 1A, the UE quasi-statically receives information indicating the repetition factor K (e.g., aggregationFactorUL or aggregationFactorDL) through higher layer signaling. Here, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

[0015] The MAC signaling may be, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (MAC PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), etc.

[0016] The UE controls reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) of the PDSCH or transmission processing (e.g., at least one of transmission, mapping, modulation, and coding) of the PUSCH in K consecutive slots based on at least one of the following field values ​​(or information indicated by the field values) in the DCI: Allocation of time domain resources (e.g. starting symbol, number of symbols in each slot, etc.); Allocation of frequency domain resources (e.g., a certain number of resource blocks (RBs) and a certain number of resource block groups (RBGs)), Modulation and Coding Scheme (MCS) index, Configuration of the PUSCH demodulation reference signal (DMRS: Demodulation Reference Signal), PUSCH spatial relation info or Transmission Configuration Indication (TCI) state (TCI-state).

[0017] The same symbol allocation may be applied between K consecutive slots. Figure 1A shows a case where the PUSCH in each slot is assigned to a predetermined number of symbols from the beginning of the slot. The same symbol allocation between slots may be determined as described above in the time domain resource allocation.

[0018] For example, the UE may determine symbol allocation in each slot based on a start symbol S and a number of symbols L (e.g., Start and Length Indicator (SLIV)) determined based on a value m of a predetermined field (e.g., a TDRA field) in the DCI. The UE may determine the first slot based on K2 information determined based on a value m of a predetermined field (e.g., a TDRA field) in the DCI.

[0019] On the other hand, among the K consecutive slots, the redundancy versions (RVs) applied to the TBs based on the same data may be the same or at least partially different. For example, the RV applied to the TB in the n-th slot (transmission opportunity, repetition) may be determined based on the value of a predetermined field (e.g., the RV field) in the DCI.

[0020] If the communication direction of the resources allocated in K consecutive slots differs in at least one symbol from the UL, DL, or Flexible of each slot specified by at least one of the uplink / downlink communication direction indication information for TDD control (e.g., RRC IE “TDD-UL-DL-ConfigCommon” and “TDD-UL-DL-ConfigDedicated”) and the slot format indicator of the DCI (e.g., DCI format 2_0), the resources of the slot including that symbol may not be transmitted (or received).

[0021] In Rel. 15, as shown in FIG. 1A, PUSCH is repeatedly transmitted across multiple slots (slot units), but in Rel. 16 and later, it is expected that PUSCH will be repeatedly transmitted in units shorter than slots (for example, subslot units, minislot units, or units of a specified number of symbols) (see FIG. 1B).

[0022] In FIG. 1B, the repetition factor K=4, but the value of K is not limited to this. In addition, the n-th repetition may be called the n-th transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K-1). In addition, FIG. 1B shows repeated transmission of a PUSCH dynamically scheduled by DCI (e.g., a dynamic grant-based PUSCH), but may be applied to repeated transmission of a configuration grant-based PUSCH.

[0023] The UE may determine symbol allocation for PUSCH transmission (e.g., PUSCH with k=0) in a predetermined slot based on a start symbol S and a number of symbols L (e.g., StartSymbol and length) determined based on a value m of a predetermined field (e.g., TDRA field) in DCI of the PUSCH. Note that the UE may determine the predetermined slot based on Ks information determined based on a value m of a predetermined field (e.g., TDRA field) of the DCI.

[0024] The UE may dynamically receive information indicating the repetition factor K (e.g., numberofrepetitions) through downlink control information. The repetition factor may be determined based on a value m of a predetermined field (e.g., a TDRA field) in the DCI. For example, a table may be supported that defines the correspondence between the bit value notified by the DCI, the repetition factor K, the start symbol S, and the number of symbols L.

[0025] The slot-based repetition transmission shown in FIG. 1A may be referred to as repetition transmission type A (e.g., PUSCH repetition Type A), and the subslot-based repetition transmission shown in FIG. 1B may be referred to as repetition transmission type B (e.g., PUSCH repetition Type B).

[0026] The UE may be configured to apply at least one of repetitive transmission type A and repetitive transmission type B. For example, the base station may notify the UE of the repetitive transmission type applied by the UE by higher layer signaling (e.g., PUSCHRepTypeIndicator).

[0027] Either repetitive transmission type A or repetitive transmission type B may be configured in the UE for each DCI format for which the PUSCH is scheduled.

[0028] For example, for a first DCI format (e.g., DCI format 0_1), if higher layer signaling (e.g., PUSCHRepTypeIndicator-AorDCIFormat0_1) is set to repetitive transmission type B (e.g., PUSCH-RepTypeB), the UE applies repetitive transmission type B for PUSCH repetitive transmission scheduled in the first DCI format. Otherwise (e.g., if PUSCH-RepTypeB is not set or if PUSCH-RepTypA is set), the UE applies repetitive transmission type A for PUSCH repetitive transmission scheduled in the first DCI format.

[0029] (Invalid symbol pattern) When applying repetitive transmission type B to PUSCH transmission, it is also considered to notify a UE of information on symbols (or symbol patterns) that cannot be used for PUSCH transmission. The symbol pattern that cannot be used for PUSCH transmission may be called an invalid symbol pattern, an invalid symbol pattern, or the like.

[0030] It is being considered to notify the invalid symbol pattern by using at least one of higher layer signaling and DCI. The DCI may be in a predetermined DCI format (for example, at least one of DCI formats 0_1 and 0_2).

[0031] For example, information about an invalid symbol pattern that cannot be used for PUSCH transmission is notified to the UE by using a first higher layer parameter. Also, whether or not the information about the invalid symbol pattern is applied may be notified to the UE by using DCI. In this case, a bit field (a field for notifying whether or not an invalid symbol pattern is applied) for indicating whether or not the information about the invalid symbol pattern is applied may be set in the DCI.

[0032] Also, the second higher layer parameter may be used to notify the UE of whether or not a notification field (or additional bit) in the DCI is set. In other words, when the UE is notified of information on an invalid symbol pattern by the first higher layer parameter, the UE may determine whether or not to apply the information on the invalid symbol pattern based on the second higher layer parameter and the DCI.

[0033] When the first higher layer parameter is not notified or configured, the UE may control the transmission of the PUSCH without considering the invalid symbol pattern. When the first higher layer parameter is notified or configured, the UE may determine whether or not to apply the invalid symbol pattern based on the second higher layer parameter and the DCI. For example, when the second higher layer parameter instructs the DCI to add an additional bit (or a predetermined field) indicating whether or not to apply the invalid symbol pattern, the UE may determine whether or not to apply the invalid symbol pattern based on the predetermined field.

[0034] The first higher layer parameter may be information for notifying a symbol pattern that is invalid for PUSCH transmission, and may be in the form of a bitmap, for example (see FIG. 2A). FIG. 2A illustrates an example in which an invalid symbol pattern is defined by a bitmap (1-D bitmap) for the time domain. The UE may determine resources available for PUSCH transmission in one or more frequency bandwidths (e.g., Bandwidth Part (BWP)) based on information about the invalid symbol pattern (see FIG. 2B).

[0035] Here, a case is shown in which one or a common invalid symbol pattern is applied to a plurality of BWPs, but a different invalid symbol pattern may be set or applied to each BWP.

[0036] (Nominal repetitions / Actual repetitions) When repeat transmission type B is applied and repeat transmission is performed in subslot units, there may be cases where a certain repeat transmission crosses a slot boundary depending on the repetition coefficient (K) and the data allocation unit, etc.

[0037] Figure 3A shows an example of a case where repetition transmission type B is applied when the repetition factor (K) is 4 and the PUSCH length (L) is 4. In Figure 3A, a PUSCH with k=3 is arranged across a slot boundary. In this case, the PUSCH may be divided (or segmented) based on the slot boundary for transmission (see Figure 3B).

[0038] Also, a case is assumed in which a slot contains a symbol that cannot be used for PUSCH transmission (for example, DL symbol or invalid symbol). FIG. 3A shows a case in which a symbol that cannot be used for PUSCH transmission (here, DL symbol) is included in some symbols in which the PUSCH with k=1 is arranged. In such a case, PUSCH transmission may be performed using symbols other than the DL symbol (see FIG. 3B).

[0039] In the case where DL symbols (or invalid symbols) are included in symbols other than both ends of the assigned symbols of a certain PUSCH, PUSCH transmission may be performed using symbols other than the DL symbol portion. In this case, the PUSCH may be divided (or segmented).

[0040] FIG. 3B shows a case in which, in subslot-based repeat transmission, a PUSCH with k=1 (Rep#2) is divided into two by a DL symbol (Rep#2-1 and #2-2), and a PUSCH with k=3 (Rep#4) is divided into two by a slot boundary (Rep#4-1 and #4-2).

[0041] Note that the repetitive transmission before considering DL symbols, invalid symbols, or slot boundaries (FIG. 3A) may be called nominal repetitions. The repetitive transmission after considering DL symbols, invalid symbols, or slot boundaries (FIG. 3B) may be called actual repetitions.

[0042] (Spatial Relationships for SRS, PUSCH) In Rel.15 NR, a UE may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used to transmit a measurement reference signal (e.g., a Sounding Reference Signal (SRS)).

[0043] Specifically, the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

[0044] An SRS resource set may be associated with (group together) a number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

[0045] The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type (e.g., Periodic SRS, Semi-Persistent SRS, or Aperiodic SRS), and information on SRS usage.

[0046] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic SRS (A-SRS). Note that the UE may transmit the P-SRS and SP-SRS periodically (or periodically after activation) and transmit the A-SRS based on an SRS request of the DCI.

[0047] Furthermore, the use (RRC parameter "usage" and L1 (Layer-1) parameter "SRS-SetUse") may be, for example, beam management, codebook (CB), noncodebook (NCB), antenna switching, etc. The SRS for codebook or noncodebook use may be used to determine a precoder for codebook-based or noncodebook-based PUSCH transmission based on the SRI.

[0048] For example, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI) in the case of codebook-based transmission. The UE may determine a precoder for PUSCH transmission based on the SRI in the case of non-codebook-based transmission.

[0049] The SRS resource information may include an SRS resource ID (SRS-ResourceId), an SRS port number, an SRS port number, a transmission Comb, an SRS resource mapping (e.g., time and / or frequency resource position, resource offset, resource period, repetition number, SRS symbol number, SRS bandwidth, etc.), hopping related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

[0050] The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a certain reference signal and the SRS. The certain reference signal may be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS / PBCH block may be referred to as a Synchronization Signal Block (SSB).

[0051] The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the predetermined reference signal.

[0052] In the present disclosure, the SSB index, the SSB resource ID, and the SSB Resource Indicator (SSBRI) may be interchangeable. Also, the CSI-RS index, the CSI-RS resource ID, and the CSI-RS Resource Indicator (CRI) may be interchangeable. Also, the SRS index, the SRS resource ID, and the SRI may be interchangeable.

[0053] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc., corresponding to the above-mentioned predetermined reference signal.

[0054] When the UE is configured with spatial relationship information regarding the SSB or CSI-RS and the SRS for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) for receiving the SSB or CSI-RS. In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0055] When the UE is configured with spatial relationship information regarding a certain SRS (target SRS) resource between another SRS (reference SRS) and the SRS (target SRS), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

[0056] The UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on a value of a predetermined field (e.g., an SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information of the SRS resource (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

[0057] When using codebook-based transmission for PUSCH, the UE may be configured by RRC with two SRS resources per SRS resource set and one of the two SRS resources may be indicated by DCI (1-bit SRI field).When using non-codebook-based transmission for PUSCH, the UE may be configured by RRC with four SRS resources per SRS resource set and one of the four SRS resources may be indicated by DCI (2-bit SRI field).

[0058] (Multi-TRP) In NR, it is considered that one or more transmission / reception points (TRPs) (multi-TRPs (M-TRPs)) will perform DL transmission to a UE using one or more panels (multi-panels). It is also considered that a UE will perform UL transmission to one or more TRPs (see Figure 4).

[0059] However, if transmission for M-TRP is attempted using the existing Rel.15 / 16 specifications, there is a problem in that performance, scheduling flexibility, etc. are limited. Transmission for M-TRP corresponds to, for example, multiple PUSCH transmissions using different SRIs.

[0060] 5A and 5B are diagrams showing an example of a problem when attempting to transmit to M-TRP using the existing Rel.15 / 16 specifications. In this example, it is assumed that the value of the SRI field of DCI = 0 corresponds to SRI#0, and the value of the SRI field = 0 corresponds to SRI#1.

[0061] 5A corresponds to a case where transmission for M-TRP is to be performed using the existing specifications of Rel. 15. In this example, PUSCH #1 corresponding to SRI #0 is scheduled using a certain DCI (DCI1), and PUSCH #2 corresponding to SRI #1 is scheduled using another DCI (DCI2).

[0062] Here, DCI1 and DCI2 have the same HARQ process ID (or HARQ process number) and indicate the same New Data Indicator (NDI) field value. In other words, PUSCH#2 means retransmission of the same data (transport block) as PUSCH#1. According to this example, PUSCH of the same data can be transmitted (retransmitted, repeatedly transmitted) at short intervals using different beams (SRI).

[0063] On the other hand, in Rel. 15, DCI2 for scheduling another PUSCH #2 can only be issued (notified) after PUSCH #1 has been transmitted, which is not preferable when it is desired to transmit PUSCH #1 and #2 with a small time difference.

[0064] 5B corresponds to a case where transmission for M-TRP is to be performed using the existing specifications of Rel. 16. In this example, PUSCH #1 corresponding to SRI #0 is scheduled using DCI (DCI1) detected in CORESET with control resource set (CONTROLL RESOURCE SET (CORESET)) pool index = 0, and PUSCH #2 corresponding to SRI #1 is scheduled using DCI (DCI2) detected in CORESET with CORESET pool index = 1.

[0065] In Rel.16, when PUSCHs associated with different CORESET pool index values ​​are scheduled and a first PUSCH is scheduled by a CORESET (first PDCCH) of one CORESET pool index value, the UE may schedule a second PUSCH that starts before the end of the first PUSCH by a CORESET (second PDCCH) of the other CORESET pool index value that ends after the first PDCCH. Figure 5B corresponds to this case.

[0066] In other words, in Rel.16, even before the completion of transmission of PUSCH#1 scheduled by DCI#1, DCI#2 for scheduling another PUSCH#2 can be issued (notified) if the CORESET pool indices of these DCIs are different.

[0067] However, according to the existing Rel.15 / 16 specifications, the correspondence between the SRI field and the SRI is set in common regardless of the CORESET pool index where the DCI is detected (corresponding to the SRI in the same SRS resource set), so flexible transmission to the M-TRP cannot be realized. The same is true for the Transmit Power Control (TPC) related parameters corresponding to the SRI field.

[0068] Therefore, if the existing Rel. 15 / 16 specifications are followed, UL transmission across the M-TRP may not be performed properly, which may result in a decrease in throughput or degradation of communication quality.

[0069] Therefore, the present inventors have conceived a method for controlling UL transmission across M-TRPs. According to one aspect of the present disclosure, for example, a UE can perform UL transmission for multiple TRPs using different beams.

[0070] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0071] In the present disclosure, "A / B" and "at least one of A and B" may be read as interchangeable.

[0072] In the present disclosure, the terms activate, deactivate, indicate, select, configure, update, determine, etc. may be read as interchangeable terms.

[0073] In the present disclosure, RRC, RRC parameters, RRC messages, RRC signaling, higher layer parameters, information elements (IEs), and configurations may be interchangeable. In the present disclosure, MAC CE, update commands, and activation / deactivation commands may be interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be interchangeable.

[0074] In the present disclosure, the terms panel, beam, panel group, beam group, precoder, uplink (UL) transmitting entity, TRP, spatial relationship information (SRI), spatial relationship, SRS Resource Indicator (SRI), SRS resource, control resource set (COntrol REsource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword, base station, predetermined antenna port (e.g., DeModulation Reference Signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., Code Division Multiplexing (CDM) group, predetermined reference signal group, CORESET group), predetermined resource (e.g., predetermined reference signal resource), predetermined resource set (e.g., predetermined reference signal resource set), CORESET pool, PUCCH group (PUCCH resource group), spatial relationship group, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), The terms TCI state, unified TCI state, common TCI state, QCL, QCL assumption, etc. may be read interchangeably.

[0075] In addition, a TCI status identifier (ID) and a TCI status may be interchangeable. A TCI status and a TCI may be interchangeable.

[0076] In this disclosure, the terms index, ID, indicator, and resource ID may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, and subset may be interchangeable.

[0077] In the present disclosure, the TRP index, CORESET pool index (CORESETPoolIndex), pool index, group index, etc. may be read as interchangeable.

[0078] In the present disclosure, a single PDCCH (DCI) may be referred to as a PDCCH (DCI) of a first scheduling type (e.g., scheduling type A (or type 1)), and a multi-PDCCH (DCI) may be referred to as a PDCCH (DCI) of a second scheduling type (e.g., scheduling type B (or type 2)).

[0079] In this disclosure, for a single DCI, the ith TRP (TRP#i) may refer to the ith TCI state, the ith CDM group, etc. (i is an integer). For a multi-DCI, the ith TRP (TRP#i) may refer to the CORESET corresponding to CORESET pool index=i, the ith TCI state, the ith CDM group, etc. (i is an integer).

[0080] In this disclosure, a single PDCCH may be assumed to be supported when multiple TRPs use an ideal backhaul, and multiple PDCCHs may be assumed to be supported when multiple TRPs use a non-ideal backhaul.

[0081] In addition, the ideal backhaul may be called DMRS port group type 1, reference signal associated group type 1, antenna port group type 1, CORESET pool type 1, etc. The non-ideal backhaul may be called DMRS port group type 2, reference signal associated group type 2, antenna port group type 2, CORESET pool type 2, etc. The names are not limited to these.

[0082] In the present disclosure, multi-TRP (MTRP, M-TRP), multi-TRP system, multi-TRP transmission, and multi-PDSCH may be read as interchangeable.

[0083] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, scheduling multiple PUSCHs by one DCI, sDCI-based MTRP transmission, and activating two TCI states on at least one TCI codepoint may be read as interchangeable.

[0084] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, mDCI-based MTRP transmission, scheduling multiple PUSCHs using two DCIs, and setting two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read as interchangeable.

[0085] The repetition in the present disclosure may be interchangeably read as MTRP-based repetition, Rel.17 repetition, repetition applying different spatial relationships, repetitive PUSCH, repetitive PUCCH, repetitive transmission, etc. Furthermore, the repetitive transmission in the following embodiments may correspond to at least one of repetitive transmission type A, repetitive transmission type B, and other repetitive transmission types.

[0086] Note that the PUSCH in the following embodiments may or may not be a repetitive PUSCH (it may be a PUSCH that is transmitted once).

[0087] Furthermore, the SRS resource set in the following embodiments may be interpreted as an SRS resource set whose purpose is a codebook or a non-codebook, or may be interpreted as an SRS resource set whose purpose is another purpose.

[0088] In addition, in the present disclosure, hereinafter, "CORESET pool index is set to 0" may be read as "CORESET pool index is set to 0 or CORESET pool index is not set".

[0089] (Wireless communication method) <First embodiment> The first embodiment describes a case where multiple DCIs are used for M-TRP. In this case, at least one CORESET having a CORESET pool index (RRC parameter "CORESETPoolIndex") of 1 or more is configured for the UE.

[0090] In the first embodiment, the UE may determine the SRI of a PUSCH based on a CORESET pool index of a CORESET for (eg, detecting) a DCI that schedules the PUSCH.

[0091] The UE may determine the SRI only when a CORESET pool index is configured for at least one CORESET in a certain BWP / certain component carrier. Also, the UE may determine the SRI only when a PUSCH is scheduled by a DCI detected in a CORESET with a CORESET pool index configured.

[0092] 6 is a diagram illustrating an example of control of SRI of PUSCH according to the first embodiment. In this example, PUSCH #1 corresponding to SRI #0_0 is scheduled using DCI (DCI1) detected in a CORESET with CORESET pool index = 0, and PUSCH #2 corresponding to SRI #1_1 is scheduled using DCI (DCI2) detected in a CORESET with CORESET pool index = 1.

[0093] The correspondence relationship between the DCI and SRI field values ​​and the SRI differs from the case of FIG. 5B and varies for each CORESET pool index, as will be described later in FIGS. 7A and 7B.

[0094] 7A and 7B are diagrams showing an example of a correspondence relationship between the value of the SRI field and the SRI according to the first embodiment. In the present disclosure, SRI#i_j (where i and j are numbers) may mean the j-th SRI corresponding to the CORESET pool index=i. SRI#i_j may be explicitly or implicitly associated with the CORESET pool index and set / activated by higher layer signaling.

[0095] FIG. 7A shows an example in which a plurality of SRIs (two in this example) corresponding to one SRI code point (field value) are configured by higher layer signaling (for example, RRC signaling). PUSCH#k (k-th PUSCH) (k is an integer) may mean the SRI corresponding to the k-th TRP, or may mean the SRI corresponding to the k-th repetition. PUSCH#i may be read as the i-th SRI. Note that the present disclosure can also be applied to cases in which the third and subsequent PUSCHs are specified.

[0096] The UE may determine an SRI by referring to the first SRI for a PUSCH scheduled in a CORESET with a CORESET pool index = 0. The UE may determine an SRI by referring to the second SRI for a PUSCH scheduled in a CORESET with a CORESET pool index = 1. With this configuration, it is possible to flexibly indicate an SRI for an M-TRP (when a different CORESET pool index is used) without increasing the field size of the DCI.

[0097] In Fig. 7A, SRI#0_0 and SRI#1_0 are set in relation to the SRI field value = 0. For example, SRI#0_0 corresponding to PUSCH#1 is applied to a PUSCH scheduled by a DCI with an SRI field value = 0 detected in a CORESET with a CORESET pool index = 0. In Fig. 6, since DCI1 had an SRI field value = 0 and DCI2 had an SRI field value = 1, SRI#0_0 was applied to PUSCH#1 and SRI#1_1 was applied to PUSCH#2 with reference to Fig. 7A.

[0098] In Fig. 7A, the CORESET pool index may not be explicitly associated with SRI#i_j, for example, the i-th SRI corresponding to a value of a certain SRI field may be determined to be associated with CORESET pool index=i. Meanwhile, as shown in Fig. 7B, the SRI#i_j associated with a certain CORESET pool index may be explicitly configured in the UE.

[0099] In this example, two SRS resources are configured for an SRS resource set with a purpose of codebook (CB) (the size of the SRI field is 1 bit), but this is not limiting. For example, even if one SRS resource is configured for an SRS resource set with a purpose of codebook (the size of the SRI field is 0 bit), the SRI of the PUSCH may be configured for each CORESET pool index and determined based on the CORESET pool index that detects the DCI that schedules the PUSCH.

[0100] According to the first embodiment described above, the SRI for M-TRP can be appropriately determined.

[0101] <Modification of the first embodiment> The CORESET pool index of the first embodiment may be replaced with a TCI state ID or a CORESET index. For example, the UE may determine the SRI of the PUSCH based on the TCI state ID or CORESET ID of the CORESET for the DCI that schedules the PUSCH (e.g., detects the DCI). The TCI state ID may be replaced with a QCL assumption.

[0102] In a variant of the first embodiment, even if a different CORESET pool index (or a CORESET pool index with a value greater than or equal to 1) is not configured, the UE can determine the SRI (or TCI state) of a PUSCH based on the CORESET in which it detects the DCI that schedules the PUSCH.

[0103] Fig. 8 is a diagram showing an example of a correspondence relationship between the value of the SRI field and the SRI according to the modified example of the first embodiment. This example is similar to Fig. 6, but differs in that DCI1 is detected in a CORESET with CORESET ID=2, and DCI2 is detected in a CORESET with CORESET ID=3.

[0104] Here, assuming that the TCI state corresponding to the CORESET of CORESET=2 corresponds to TCI#0 (TCI ID=0) and the TCI state corresponding to the CORESET of CORESET=3 corresponds to TCI#1, the UE may apply TCI#0 as the SRI for PUSCH#1 scheduled by DCI1 and may apply TCI#1 as the SRI for PUSCH#2 scheduled by DCI2.

[0105] In addition, the CORESET pool index in other embodiments of the present disclosure may also be read as a TCI state ID or a CORESET index.

[0106] <Second embodiment> The second embodiment describes a case where multiple DCIs are used for M-TRP.

[0107] In a second embodiment, the UE may determine the transmission power of the PUSCH based on a CORESET pool index of a CORESET for (e.g., detecting) a DCI that schedules the PUSCH. For example, the UE may determine a transmission power control (TPC) related parameter of the PUSCH based on a CORESET pool index of a CORESET that detects a DCI that schedules the PUSCH.

[0108] Here, the transmission power control (TPC) related parameters may be, for example, at least one of α, P0, a closed loop power control state, and a path loss reference signal (PL-RS), or may be an index related to at least one of these. Hereinafter, the TPC related parameters are also referred to as power control parameters. It is naturally understood by those skilled in the art that values ​​calculated based on these are used in the calculation formula for the transmission power of the PUSCH.

[0109] The UE may determine the transmission power only when a CORESET pool index is set for at least one CORESET in a certain BWP / certain component carrier. The UE may also determine the transmission power only when a PUSCH is scheduled by a DCI detected in a CORESET in which a CORESET pool index is set. The determination of the transmission power may be used when a correspondence relationship between SRIs is set for each CORESET pool index as shown in the first embodiment, or may be used otherwise.

[0110] 9 is a diagram illustrating an example of control of transmission power of PUSCH according to the second embodiment. In this example, PUSCH #1 corresponding to SRI #0_x (x is an integer) is scheduled using DCI (DCI1) detected in a CORESET with CORESET pool index=0, and PUSCH #2 corresponding to SRI #1_y (y is an integer) is scheduled using DCI (DCI2) detected in a CORESET with CORESET pool index=1.

[0111] The UE derives the transmission power of PUSCH #1 based on a first power control parameter associated with CORESET pool index = 0. Also, the UE derives the transmission power of PUSCH #2 based on a second power control parameter associated with CORESET pool index = 1.

[0112] FIG. 10 is a diagram showing an example of power control parameter settings in the existing Rel. 15 / 16 NR. This example is described using Abstract Syntax Notation One (ASN.1) notation (note that this is merely an example and may not be a complete description). The following drawings may also use ASN.1 notation.

[0113] In the present disclosure, a suffix indicating that the RRC information element, the RRC parameter, etc. is introduced in a specific resource (e.g., "_r16", "_r17", "-r16", "-r17", etc.) may be added to the name of the RRC information element, the RRC parameter, etc. The suffix may not be added, or another word may be added.

[0114] In the existing Rel.15 / 16 NR, the configuration of the PUSCH power control parameters (RRC information element "PUSCH-PowerControl") may include a list (sri-PUSCH-MappingToAddModList) for setting the correspondence between the SRI and the power control parameters (SRI-PUSCH-PowerControl) and a list (sri-PUSCH-MappingToReleaseList) for releasing the correspondence. The SRI field is associated with the ID of the power control parameter (SRI-PUSCH-PowerControlId) by sri-PUSCH-MappingToAddModList.

[0115] SRI-PUSCH-PowerControl may include an ID of a power control parameter, a parameter indicating the ID of the PL-RS (sri-PUSCH-PathlossReferenceRS-Id), a parameter indicating the ID of the set of P0 and α (sri-P0-PUSCH-AlphaSetId), and a parameter indicating an index of the closed loop power control state (sri-PUSCH-ClosedLoopIndex).

[0116] Fig. 11 is a diagram illustrating an example of the configuration of power control parameters according to the second embodiment. In this example, the existing sri-PUSCH-MappingToAddModList, sri-PUSCH-MappingToReleaseList, and SRI-PUSCH-PowerControl illustrated in Fig. 10 are used for the configuration of the first power control parameter associated with CORESET pool index=0.

[0117] On the other hand, sri-PUSCH-MappingToAddModList_r17, sri-PUSCH-MappingToReleaseList_r17, and SRI-PUSCH-PowerControl_r17 are used for setting the second power control parameters associated with CORESET pool index = 1. The ID of the power control parameter of SRI-PUSCH-PowerControl_r17 may be identified by SRI-PUSCH-PowerControlId_r17 or may be identified by SRI-PUSCH-PowerControlId.

[0118] For example, assuming that the correspondence between the SRI field value and the SRI is set as shown in Fig. 7A, when applying SRI#0_0 or SRI#0_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on the first power control parameter. Also, when applying SRI#1_0 or SRI#1_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on the second power control parameter.

[0119] 12 is a diagram showing another example of the configuration of power control parameters according to the second embodiment. In this example, sri-PUSCH-MappingToAddModListFirst_r17, sri-PUSCH-MappingToReleaseListFirst_r17, and SRI-PUSCH-PowerControlFirst_r17 are used for the configuration of the first power control parameters associated with CORESET pool index=0. The ID of the power control parameter of SRI-PUSCH-PowerControlFirst_r17 may be identified by SRI-PUSCH-PowerControlIdFirst_r17 or may be identified by SRI-PUSCH-PowerControlId.

[0120] On the other hand, sri-PUSCH-MappingToAddModListSecond_r17, sri-PUSCH-MappingToReleaseListSecond_r17, and SRI-PUSCH-PowerControlSecond_r17 are used for setting a second power control parameter associated with CORESET pool index = 1. The ID of the power control parameter of SRI-PUSCH-PowerControlSecond_r17 may be identified by SRI-PUSCH-PowerControlIdSecond_r17 or may be identified by SRI-PUSCH-PowerControlId.

[0121] For example, assuming that the correspondence between the SRI field value and the SRI is set as shown in Fig. 7A, when applying SRI#0_0 or SRI#0_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on the first power control parameter. Also, when applying SRI#1_0 or SRI#1_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on the second power control parameter.

[0122] According to the second embodiment described above, the transmission power for the M-TRP can be appropriately determined.

[0123] <Third embodiment> The third embodiment describes the case where a single DCI is used for the M-TRP.

[0124] In the single DCI-based M-TRP, different SRIs may be applied to multiple PUSCHs (for M-TRPs) scheduled by the single DCI. In this case, the UE may determine the transmission power of the PUSCH based on the SRI applied to the PUSCH.

[0125] The third embodiment may be realized in a manner in which the setting of power control parameters for each CORESET pool index in the above-described second embodiment is replaced with, for example, setting of power control parameters for each TRP (for each SRI set).

[0126] The first SRI (a set of SRIs for the first PUSCH) and the second SRI (a set of SRIs for the second PUSCH) may be configured / activated for the UE by higher layer signaling (e.g., RRC signaling, MAC CE, etc.), respectively.

[0127] 13A and 13B are diagrams illustrating an example of control of the transmission power of PUSCH according to the third embodiment. In this example, as shown in FIG. 13A, PUSCHs #1 and #2 are scheduled using DCI (DCI1). The value of the SRI field of DCI1 is 0.

[0128] FIG. 13B is a diagram showing an example of a correspondence relationship between the value of the SRI field and the SRI. The value of the SRI field may be associated with a different SRI for each of PUSCH #1 and #2. In the example of FIG. 13A, the application of SRI #0_0 to PUSCH #1 and the application of SRI #1_0 to PUSCH #2 may be indicated by the SRI field=0 of DCI1.

[0129] 13B also shows power control parameters corresponding to SRI. When applying SRI#0_0 or SRI#0_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on a first power control parameter (e.g., SRI-PUSCH-PowerControl, SRI-PUSCH-PowerControlFirst_r17). When applying SRI#1_0 or SRI#1_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on a second power control parameter (e.g., SRI-PUSCH-PowerControl_r17, SRI-PUSCH-PowerControlSecond_r17).

[0130] 14A and 14B are diagrams showing another example of control of the transmission power of PUSCH according to the third embodiment. In this example, as shown in FIG. 14A, PUSCHs #1 and #2 are scheduled using DCI (DCI1). FIG. 14A differs from FIG. 13A in that DCI1 has two SRI fields (SRI fields #1 and #2).

[0131] 14B is a diagram showing an example of a correspondence relationship between the value of the SRI field and the SRI. The value of the SRI field #1 may be associated with the SRI for PUSCH #1. The value of the SRI field #2 may be associated with the SRI for PUSCH #2. In the example of FIG. 14A, SRI field #1=0 may indicate application of SRI #0_0 to PUSCH #1, and SRI field #2=1 may indicate application of SRI #1_1 to PUSCH #2.

[0132] 14B also shows power control parameters corresponding to SRI. When applying SRI#0_0 or SRI#0_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on a first power control parameter (e.g., SRI-PUSCH-PowerControl, SRI-PUSCH-PowerControlFirst_r17). When applying SRI#1_0 or SRI#1_1 to a PUSCH, the UE may derive the transmission power of the PUSCH based on a second power control parameter (e.g., SRI-PUSCH-PowerControl_r17, SRI-PUSCH-PowerControlSecond_r17).

[0133] According to the third embodiment described above, the transmission power for the single DCI-based M-TRP can be appropriately determined.

[0134] <Fourth embodiment> The fourth embodiment relates to switching between sDCI-based MTRP and mDCI-based MTRP. Hereinafter, the sDCI-based MTRP, the mDCI-based MTRP, and the like will also be referred to as MTRP schemes.

[0135] [Embodiment 4.1] The UE may assume that only one of the MTRP schemes is configured by RRC signaling, and when a switch between these MTRP schemes is required, the UE may be reconfigured with an RRC parameter indicating one of the MTRP schemes.

[0136] [Embodiment 4.2] The UE may assume that any of the MTRP schemes is activated / specified by the MAC CE / DCI. The MAC CE may be a dedicated MAC CE for specifying (or switching) the MTRP scheme, or may be a MAC CE for other purposes. The MTRP scheme may be specified by the value of a specific field (e.g., the MTRP scheme field) included in the MAC CE. The specific field (e.g., the MTRP scheme field, any existing field) of the DCI may indicate a certain MTRP scheme or may indicate switching of the MTRP scheme.

[0137] [Embodiment 4.3] The UE may assume that multiple MTRP schemes are configured via RRC signaling.

[0138] In embodiment 4.3, the UE may assume that a CORESET with a CORESET pool index configured operates for mDCI-based MTRP (e.g., the UE may use the CORESET to monitor mDCI).

[0139] In embodiment 4.3, the UE may assume that a CORESET for which a CORESET pool index is not set operates for sDCI-based MTRP (for example, the CORESET may be used to monitor sDCI). Note that the UE may assume that a CORESET for which a CORESET pool index is not set operates for sDCI-based MTRP when two or more TCI states are activated (two or more TCI states correspond) for at least one codepoint in the TCI field for the CORESET (DCI).

[0140] In the existing Rel.16, a CORESET in which a CORESET pool index is not set is regarded as a CORESET with a CORESET pool index = 0 (in other words, it is assumed to operate / be treated similarly to a CORESET with a CORESET pool index = 0). On the other hand, in embodiment 4.3, such a consideration / assuming is not performed, and the UE considers (or treats) a CORESET in which a CORESET pool index is not set as a CORESET for sDCI-based MTRP.

[0141] For this reason, in order to switch between the Rel.16 operation and the operation of embodiment 4.3, a higher layer parameter (for example, a parameter "EnableS-DCI" that enables sDCI-based MTRP) may be introduced. When the higher layer parameter is set, the UE may consider that a CORESET in which a CORESET pool index is not set operates for sDCI-based MTRP (and not treat it the same as a CORESET with a CORESET pool index = 0); otherwise, as in Rel.16, a CORESET in which a CORESET pool index is not set may be treated the same as a CORESET with a CORESET pool index = 0.

[0142] In addition, the "sDCI-based MTRP" in embodiment 4.3 may be read as "single TRP" or "PUSCH for single TRP", etc.

[0143] According to the fourth embodiment described above, the first and second power control parameters described in the second and third embodiments can be commonly used in the control of both the sDCI-based MTRP and the mDCI-based MTRP (they do not need to be set individually), thereby simplifying the configuration of the RRC parameters and suppressing an increase in communication overhead associated with RRC notifications.

[0144] <Other> At least one of the above embodiments may be applied only to UEs that support or have reported a particular UE capability.

[0145] The specific UE capabilities may indicate at least one of the following: ·Whether to support the association of CORESET pool index with SRI; Whether to support associating CORESET pool index with power control parameters; Whether to support multiple SRI-PUSCH-PowerControl settings; Whether to support multiple different associations between PUSCH and SRI in sDCI-based MTRP; Whether to support switching between sDCI-based MTRP and mDCI-based MTRP; · Maximum number of power control parameters supported.

[0146] Note that, when the UE supports the settings of SRI-PUSCH-PowerControlFirst_r17 and SRI-PUSCH-PowerControlSecond_r17, the supported maximum number of power control parameters may be counted as 2. Also, when the UE supports the settings of SRI-PUSCH-PowerControl of Rel.15 / 16 and SRI-PUSCH-PowerControl_r17 of Rel.17, the supported maximum number of power control parameters may be counted as 2, or may be counted as 1 excluding the setting of SRI-PUSCH-PowerControl of Rel.15 / 16.

[0147] In addition, at least one of the above-described embodiments may be applied when specific information related to the above-described embodiments is configured in the UE by higher layer signaling (if not configured, for example, the operation of Rel. 15 / 16 is applied). For example, the specific information may be multiple power control parameters, any RRC parameters for a specific release (for example, Rel. 17), etc.

[0148] Each of the above-described embodiments may be applied when (the operation of) multi-TRP or multi-panel is set in the UE, or may be applied when not.

[0149] (Wireless communication systems) A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination of these methods.

[0150] 15 is a diagram showing an example of a schematic configuration of a wireless communication system according to an 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), or the like, which are specified by the Third Generation Partnership Project (3GPP).

[0151] Furthermore, the wireless communication system 1 may support dual connectivity between a plurality of Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include 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)), and the like.

[0152] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN) and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN and the LTE (E-UTRA) base station (eNB) is the SN.

[0153] The wireless communication system 1 may support dual connectivity between multiple base stations in the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0154] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged in the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1. A user terminal 20 may be located in at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as a base station 10.

[0155] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0156] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and 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 frequency band higher than FR2.

[0157] Furthermore, the user terminal 20 may perform communication in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0158] The multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0159] 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 at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0160] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0161] In the wireless communication system 1, a wireless access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and the uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.

[0162] The radio access scheme may be called a waveform. In the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0163] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0164] In addition, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0165] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0166] 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 of at least one of the PDSCH and the PUSCH.

[0167] In addition, DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. In addition, PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

[0168] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or multiple search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0169] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," and "CORESET setting" in the present disclosure may be read as interchangeable terms.

[0170] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and a scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0171] In the present disclosure, a downlink, an uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning of the channels.

[0172] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0173] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and the DMRS for the PBCH) may be called an SS / PBCH block, an SS Block (SSB), or the like. In addition, the SS, SSB, and the like may also be called a reference signal.

[0174] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may be called a user equipment specific reference signal (UE-specific reference signal).

[0175] (base station) 16 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

[0176] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the base station 10 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0177] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0178] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transmission and reception unit 120, the transmission and reception antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission and reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0179] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0180] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0181] The transmitting / receiving antenna 130 can be composed of an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0182] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0183] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0184] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0185] The transceiver 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0186] The transceiver unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna .

[0187] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna .

[0188] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0189] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0190] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data) for the user terminal 20, control plane data, etc.

[0191] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0192] In addition, the transmission / reception unit 120 may transmit downlink control information (Downlink Control Information (DCI)) used to determine spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) to the user terminal 20 in a certain control resource set (COntrol REsource SET (CORESET)).

[0193] The transceiver 120 may receive the PUSCH transmitted by the user terminal 20 using a precoder based on the spatial relationship information.

[0194] (User terminal) 17 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230.

[0195] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0196] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0197] The control unit 210 may control signal generation, mapping, etc. 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.

[0198] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting / receiving circuit, and the like, which are described based on common understanding in the technical field related to the present disclosure.

[0199] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0200] The transmitting / receiving antenna 230 can be composed of an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

[0201] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0202] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0203] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0204] The transceiver 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit sequence to be transmitted, and output a baseband signal.

[0205] Whether or not to apply the DFT process may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver 220 (transmission processor 2211) may perform the DFT process as the transmission process to transmit the channel using a DFT-s-OFDM waveform, and may not perform the DFT process as the transmission process if transform precoding is enabled for the channel.

[0206] The transceiver unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna 230.

[0207] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna 230.

[0208] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0209] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0210] In addition, the transmitting section and the receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0211] In addition, the control unit 210 may determine spatial relationship information for an uplink shared channel (PUSCH) scheduled by a sounding reference signal (SRS) resource indicator (SRI) based on a control resource set (COntrol REsource SET (CORESET)) in which the downlink control information (DCI) is detected. In addition, this spatial relationship information may be interchangeably read as a sounding reference signal (SRS) resource indicator (SRI).

[0212] The transceiver 220 may transmit the PUSCH using a precoder (or a spatial domain transmit filter) based on the spatial relationship information.

[0213] The control unit 210 may determine the spatial relationship information based on a CORESET pool index of the CORESET.

[0214] The control unit 210 may determine the transmission power of the PUSCH based on power control parameters (for example, first and second power control parameters) set for each CORESET pool index.

[0215] When a specific upper layer parameter (e.g., the parameter “EnableS-DCI” that enables sDCI-based MTRP) is set, the control unit 210 may treat a CORESET in which a CORESET pool index is not set as a CORESET for a single DCI-based multi-transmission / reception point.

[0216] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0217] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission may be called a transmitting unit, a transmitter, and the like. In either case, as described above, the method of realization is not particularly limited.

[0218] For example, 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. 18 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. The above-mentioned base station 10 and user terminal 20 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, etc.

[0219] In this disclosure, the terms "apparatus," "circuit," "device," "section," "unit," and the like can be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0220] For example, although only one processor 1001 is shown, there may be multiple processors. Also, the processes may be performed by one processor, or the processes may be performed by two or more processors simultaneously, sequentially, or in other manners. Also, the processor 1001 may be implemented by one or more chips.

[0221] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations, controls communications via a communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0222] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0223] Moreover, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to the programs. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and the other functional blocks may be realized in a similar manner.

[0224] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store a program (program code), a software module, and the like that is executable to implement a wireless communication method according to an embodiment of the present disclosure.

[0225] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0226] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0227] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0228] In addition, 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 each device.

[0229] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as 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., and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0230] (Modification) In addition, the terms explained in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be read as mutually interchangeable. A signal may also be a message. A reference signal may also be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, etc.

[0231] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0232] Here, the numerology may be a communication parameter applied to at least one of the transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0233] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may also be a time unit based on numerology.

[0234] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0235] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. A different name may be used for the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be read as interchangeable with each other.

[0236] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0237] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0238] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0239] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0240] A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI 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, etc.

[0241] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0242] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0243] In addition, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0244] In addition, one or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0245] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0246] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0247] The BWP may include a UL BWP (a BWP for UL) and a DL BWP (a BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0248] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given channel / signal outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0249] The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

[0250] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0251] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0252] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0253] Furthermore, information, signals, etc. may 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 / output via a plurality of network nodes.

[0254] Input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0255] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0256] The physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, by using a MAC Control Element (CE).

[0257] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0258] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., with a predetermined value).

[0259] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0260] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0261] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0262] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," and the like may be used interchangeably.

[0263] In this disclosure, terms such as "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0264] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

[0265] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0266] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0267] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0268] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0269] Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0270] In the present disclosure, an operation performed by a base station may be performed by its upper node in some cases. It is clear that in a network including one or more network nodes having base stations, various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0271] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0272] Each aspect / embodiment described in the present disclosure may be implemented using any of a wide variety of standards, including Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal point)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems using 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other appropriate wireless communication methods, next-generation systems that are based on these, etc. Also, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0273] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0274] Any reference to an element using a designation such as "first," "second," etc., 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, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0275] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, and the like.

[0276] A "determining" may also be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

[0277] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. That is, "determination" may be considered to be "deciding" to perform some action.

[0278] Additionally, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

[0279] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0280] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

[0281] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0282] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0283] In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0284] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiver for receiving one Downlink Control Information (DCI) for scheduling Physical Uplink Shared Channel (PUSCH) transmission for a plurality of TRPs and higher layer parameters for setting power control parameters for the PUSCH transmission for the plurality of TRPs for each Sounding Reference Signal (SRS) resource set for the PUSCH transmission; A control unit that controls the PUSCH transmission for the multiple TRPs based on the one DCI and the higher layer parameters, A terminal, wherein the higher layer parameters include a first parameter and a second parameter corresponding to different PUSCH transmissions.

2. The terminal according to claim 1, wherein the first parameter and the second parameter are included in higher layer signaling including a parameter indicating an index of a path loss reference signal and a parameter indicating an index of a set of P0 and α.

3. receiving one Downlink Control Information (DCI) for scheduling Physical Uplink Shared Channel (PUSCH) transmissions for a plurality of Transmission / Reception Points (TRPs) and higher layer parameters for configuring power control parameters for the PUSCH transmissions for the plurality of TRPs for each Sounding Reference Signal (SRS) resource set for the PUSCH transmissions; and controlling the PUSCH transmission for the plurality of TRPs based on the one DCI and the higher layer parameters. The wireless communication method for a terminal, wherein the higher layer parameters include a first parameter and a second parameter corresponding to different PUSCH transmissions.

4. A transmitter that transmits one Downlink Control Information (DCI) that schedules uplink shared channel (PUSCH) transmission for a plurality of transmission / reception points (TRPs) and higher layer parameters that set power control parameters for the PUSCH transmission for the plurality of TRPs for each Sounding Reference Signal (SRS) resource set for the PUSCH transmission; A control unit that controls the PUSCH transmission for the multiple TRPs based on the one DCI and the higher layer parameters, The base station, wherein the upper layer parameters include a first parameter and a second parameter corresponding to different PUSCH transmissions.

5. A system including a terminal and a base station, The terminal includes: A receiver for receiving one Downlink Control Information (DCI) for scheduling Physical Uplink Shared Channel (PUSCH) transmission for a plurality of TRPs and higher layer parameters for setting power control parameters for the PUSCH transmission for the plurality of TRPs for each Sounding Reference Signal (SRS) resource set for the PUSCH transmission; A control unit that controls the PUSCH transmission for the multiple TRPs based on the one DCI and the higher layer parameters, The higher layer parameters include a first parameter and a second parameter corresponding to different PUSCH transmissions, The base station, A system comprising a transmitter for transmitting the one DCI and the higher layer parameters.

Images