Terminal, wireless communication method, base station and system

By configuring terminals with measurement reference signal resource sets and spatial relationship information, the solution addresses the challenge of controlling PUSCH repetitive transmission in multi-TRP scenarios, improving communication quality and throughput.

JP7591552B2Active Publication Date: 2024-11-28NTT DOCOMO INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2022502784
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-02-28
Publication Date
2024-11-28
Estimated Expiration
2040-02-28

AI Technical Summary

Technical Problem

Existing NR specifications do not adequately address how to control Physical Uplink Shared Channel (PUSCH) repetitive transmission in multi-Transmission/Reception Point (TRP) scenarios, leading to potential throughput degradation and communication quality issues.

Method used

The proposed solution involves configuring a terminal to receive measurement reference signal resource sets and spatial relationship information through Radio Resource Control (RRC) signaling, downlink control information, and Transmission Configuration Indicator (TCI) states to appropriately control PUSCH repetitive transmission across multiple TRPs.

Benefits of technology

This approach enables effective control of PUSCH repetitive transmission even in multi-TRP environments, enhancing communication quality and throughput.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007591552000001
    Figure 0007591552000001
  • Figure 0007591552000002
    Figure 0007591552000002
  • Figure 0007591552000003
    Figure 0007591552000003
Patent Text Reader

Abstract

A terminal according to one embodiment of the present disclosure comprises: a control unit that determines spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH) for a plurality of transmission and reception points using at least one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, and Downlink Control Information (DCI); and a transmission unit that repeatedly transmits the PUSCH using a spatial domain transmission filter based on the spatial relationship information. According to this embodiment of the present disclosure, repeated PUSCH transmission can be appropriately controlled.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system. [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 3GPP Rel.15, repeated transmission is supported for a UL data channel (e.g., an uplink shared channel (Physical Uplink Shared Channel (PUSCH))). The UE controls the transmission of PUSCH over multiple slots (e.g., K consecutive slots) based on a repetition factor K set by the network (e.g., a base station). In other words, when repeated transmission is performed, each PUSCH is transmitted in a different slot (e.g., slot unit).

[0006] On the other hand, in Rel.16 and later, when PUSCH is repeatedly transmitted, it is considered to transmit multiple PUSCHs within one slot. In other words, each PUSCH is transmitted in units shorter than a slot (for example, in units of subslots or minislots).

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

[0008] However, in the conventional NR specifications, there has been no sufficient consideration on how to control the repeated transmission of the PUSCH in the multi-panel / TRP. If the repeated transmission of the PUSCH in the multi-TRP is not performed appropriately, there is a risk that the throughput will decrease or the communication quality will deteriorate.

[0009] Therefore, an object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control PUSCH repetitive transmission. [Means for solving the problem]

[0010] A terminal according to an embodiment of the present disclosure includes: a control unit that, when receiving configuration information related to a sounding reference signal (SRS) resource set for a specific purpose by Radio Resource Control (RRC) signaling, determines spatial relationship information for an uplink shared channel (PUSCH) for a plurality of transmission and reception points based on the SRS resource set for the specific purpose specified by a field of downlink control information (DCI); and a transmission unit that repeatedly transmits the PUSCH based on the spatial relationship information. When a Transmission Configuration Indicator (TCI) state is used as the spatial relationship information, the control unit determines spatial relationship information for a physical uplink shared channel (PUSCH) for a plurality of transmission and reception points based on the SRS resource set for the specific purpose specified by a field of downlink control information (DCI). , which is commonly used in both the downlink and the uplink The TCI state set is used to repeatedly transmit the PUSCH. Effect of the Invention

[0011] According to one embodiment of the present disclosure, PUSCH repetitive transmission can be appropriately controlled even when multi-TRP is applied. [Brief description of the drawings]

[0012] [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 to 5D are diagrams illustrating an example of notification of spatial relationship information according to the first embodiment. [Figure 6] 6A to 6C are diagrams illustrating an example of notification of spatial relationship information according to the second embodiment. [Figure 7] 7A to 7C are diagrams illustrating an example of notification of spatial relationship information according to the third embodiment. [Figure 8] 8A to 8C are diagrams illustrating an example of notification of spatial relationship information according to the fourth embodiment. [Figure 9] 9A to 9C are diagrams illustrating an example of notification of spatial relationship information according to the fifth embodiment. [Figure 10] 10A to 10C are diagrams illustrating an example of notification of spatial relationship information according to the sixth embodiment. [Figure 11] 11A to 11C are diagrams illustrating an example of notification of spatial relationship information according to the seventh embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 15] FIG. 15 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

[0013] (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.

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

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

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

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

[0018] 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).

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

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

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

[0022] 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).

[0023] 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).

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

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

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

[0027] 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).

[0028] 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).

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

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

[0031] (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.

[0032] 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).

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

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

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

[0036] 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., BWP) based on information about the invalid symbol pattern (see FIG. 2B).

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

[0038] (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.

[0039] 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).

[0040] 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).

[0041] 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).

[0042] 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).

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

[0044] (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)).

[0045] 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").

[0046] 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).

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

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

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

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

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

[0052] 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).

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

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

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

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

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

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

[0059] 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).

[0060] (Multi-TRP) In NR, one or more transmission / reception points (TRPs) (multi-TRPs) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs (see Figure 4).

[0061] The TRPs may correspond to the same or different cell identifiers (Cell Identifiers (IDs)), which may be physical or virtual cell IDs.

[0062] However, in the conventional NR specifications, there has been no sufficient consideration on how to control the repeated transmission of the PUSCH in the multi-panel / TRP. If the repeated transmission of the PUSCH in the multi-TRP is not performed appropriately, there is a risk that the throughput will decrease or the communication quality will deteriorate.

[0063] Therefore, the present inventors have conceived a method for controlling PUSCH repetitive transmission. According to one aspect of the present disclosure, for example, a UE can perform PUSCH repetitive transmission for multiple TRPs using a different beam for each repetition unit (e.g., segment, subslot).

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

[0065] In addition, in the present disclosure, panel, Uplink (UL) transmitting entity, TRP, spatial relationship, control resource set (COntrol REsource SET (CORESET)), PDSCH, codeword, base station, specific antenna port (e.g., DeModulation Reference Signal (DMRS) port), specific antenna port group (e.g., DMRS port group), specific group (e.g., Code Division Multiplexing (CDM) group, specific reference signal group, CORESET group), CORESET pool, may be read as interchangeable. Also, panel identifier (ID) and panel may be read as interchangeable. TRP ID and TRP may be read as interchangeable.

[0066] In this disclosure, the terms index, ID, indicator, and resource ID may be interpreted as interchangeable.

[0067] In the present disclosure, "A / B" may mean "at least one of A and B."

[0068] In the present disclosure, the terms list, group, cluster, subset, etc. may be interchangeable. In the present disclosure, the terms spatial relationship information, SRI, SRS resource, precoder, etc. may be interchangeable.

[0069] In the following embodiments, a PUSCH across multiple TRPs may be interchangeably referred to as a repeated PUSCH across multiple TRPs, simply a repeated PUSCH, repeated transmission, etc.

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

[0071] (Wireless communication method) <First embodiment> In a first embodiment, the UE is informed of spatial relationship information for PUSCH across multiple TRPs by a combination of RRC signaling, MAC CE and DCI.

[0072] 5A to 5D are diagrams showing an example of notification of spatial relationship information according to the first embodiment. Hereinafter, a description will be given with reference to FIGS.

[0073] In the first embodiment, the UE may be configured with a predetermined number (e.g., M) of SRS resource lists associated with one SRS resource set through RRC signaling, where the predetermined number M may be, for example, 8, 64, etc., or may be greater than 64. One or more SRS resource lists may be configured in an SRS resource set for a specific application (e.g., codebook or non-codebook).

[0074] A maximum of R SRS resources may be associated with one SRS resource list, where R may correspond to the maximum number of TRPs for the PUSCH.

[0075] 5A shows an example in which a plurality of SRS resource lists (SRS resource lists #0, #1, ...) are set in association with an SRS resource set. SRS resource list #0 is associated with SRS resource #0. SRS resource list #1 is associated with {SRS resources #0, #1}.

[0076] In the first embodiment, when multiple SRS resource lists are configured in a UE, one or more SRS resource lists (subsets of the SRS resource lists) are further activated using the MAC CE, and the maximum number of active SRS resource lists may be limited to a predetermined number (e.g., 2, 4, 8, etc.).

[0077] FIG. 5B is a diagram showing an example of an SRS resource activation / deactivation MAC CE according to the first embodiment. FIG. 5B shows a bit string constituting the MAC CE. The MAC CE may include information such as the cell ID (of the SRS resource set) to which it is applied ("Serving Cell ID" field) and the BWP ID (of the SRS resource set) ("BWP ID" field). The "R" field may represent a reserved bit for future extension. The same is true for the other MAC CE drawings that follow unless otherwise specified.

[0078] In addition, the MAC CE is i " (i=0, 1, 2, ...). The UE i If the field of #i indicates 1, the UE activates the SRS resource list #i. i If the field indicates 0, deactivate the SRS resource list #i.

[0079] In the first embodiment, one or more SRS resource lists among the activated SRS resource lists may be indicated to the UE using a DCI field. Note that the field may be an existing DCI field (e.g., an SRI field), a new DCI field (e.g., an SRS resource list field for repeated transmission), or a combination of multiple fields.

[0080] A UE configured with codebook-based PUSCH transmission or configured with single-layer non-codebook-based PUSCH transmission may assume that one SRS resource list is indicated for PUSCH transmission across multiple TRPs.

[0081] 5C is a diagram showing an example of a correspondence relationship of DCI fields for specifying one SRS resource list according to the first embodiment. In this example, a value of a certain field included in the DCI ("Bit field mapped to index") and a corresponding activated SRS resource list are shown. The number of bits of the field may be determined based on the maximum number of active SRS resource lists.

[0082] In Fig. 5C, different SRS resource lists are specified according to the field values. The UE may assume that the SRS resource list #i activated by the MAC CE corresponds to the values ​​of each field in ascending or descending order. In other words, it may assume that there is a one-to-one correspondence between the activated SRS resource list ID and the field value when they are arranged in ascending or descending order, respectively, from the smallest to the largest.

[0083] For example, assuming a case in which S1=S0=1 is notified in the MAC CE of Figure 5B, the active SRS resource list corresponding to the value of each field may be identified, such that the first SRS resource list in Figure 5C is SRS resource list #0, the second SRS resource list is SRS resource list #1, ...

[0084] A UE configured with non-codebook based PUSCH transmission for multiple layers may assume that multiple SRS resource lists, each corresponding to spatial relationship information for each layer, are indicated for PUSCH transmission across multiple TRPs.

[0085] 5D is a diagram showing an example of a DCI field for specifying a plurality of SRS resource lists according to the first embodiment. In this example, the DCI fields include a bit field for layer #0 ("Bit field for layer #0"), a bit field for layer #1 ("Bit field for layer #1"), etc. The UE may determine the SRS resource list corresponding to the value of each bit field in the same manner as described in FIG. 5C.

[0086] According to the first embodiment described above, the SRS resource list specified by the DCI can be dynamically changed using the MAC CE to perform PUSCH repetitive transmission. For example, control can be performed to use different SRS resources for each PUSCH resource and for each PUSCH repetition.

[0087] <Second embodiment> In a second embodiment, the UE is informed of spatial relationship information for PUSCH across multiple TRPs by a combination of RRC signaling and DCI.

[0088] 6A-6C are diagrams showing an example of notification of spatial relationship information according to the second embodiment. Hereinafter, a description will be given with reference to Figs. 6A-6C. Points not particularly mentioned may be the same as those in the first embodiment.

[0089] In a second embodiment, the UE may be configured with a predetermined number (eg, M) of SRS resource lists associated with one SRS resource set through RRC signaling. Figure 6A is the same as Figure 5A.

[0090] In the second embodiment, one or more SRS resource lists may be specified to the UE from among the SRS resource lists configured by the RRC using a field of the DCI.

[0091] 6B is a diagram showing an example of a correspondence relationship of DCI fields for specifying one SRS resource list according to the second embodiment. In this example, a value of a certain field included in DCI ("Bit field mapped to index") and a corresponding SRS resource list configured by RRC are shown. The number of bits of the field may be determined based on the maximum number of configured SRS resource lists.

[0092] Fig. 6C is a diagram showing an example of a DCI field for specifying a plurality of SRS resource lists according to the second embodiment. This example is similar to Fig. 5D, except that each bit field corresponds to Fig. 6B.

[0093] According to the second embodiment described above, it is possible to appropriately perform PUSCH repeated transmission based on an SRS resource list specified by DCI among SRS resource lists configured by RRC.

[0094] <Third embodiment> In a third embodiment, the UE is informed of spatial relationship information for PUSCH across multiple TRPs by a combination of RRC signaling and MAC CE.

[0095] 7A to 7C are diagrams showing an example of notification of spatial relationship information according to the third embodiment. Hereinafter, a description will be given with reference to Figs. 7A to 7C. Points not particularly mentioned may be the same as those in the first embodiment.

[0096] In the third embodiment, the UE may be configured with a predetermined number (eg, M) of SRS resource lists by RRC signaling. Figure 7A is the same as Figure 5A.

[0097] In the third embodiment, when multiple SRS resource lists are configured in a UE, the MAC CE is further used to activate (or indicate) one or more SRS resource lists.

[0098] FIG. 7B is a diagram showing an example of an SRS resource activation / deactivation MAC CE according to the second embodiment. FIG. 7B is the same as FIG. 5B. Note that the MAC CE in FIG. 7B may be notified to a UE configured for codebook-based PUSCH transmission or configured for single-layer non-codebook-based PUSCH transmission. The UE may notify the UE of the "S i " field may assume that only one will show a value of 1.

[0099] FIG. 7C is a diagram showing another example of SRS resource activation / deactivation MAC CE according to the second embodiment. FIG. 7C is similar to FIG. 7B, but is different in that an SRS resource list ID for each layer can be specified. For example, the first layer ID ("1 st The “Layer ID” field may indicate a layer ID (e.g., 0-3) and the first SRS resource list ID ("1 st The “SRS resource list ID” field may be used to identify an SRS resource list corresponding to the layer of the first layer ID.

[0100] In this example, each layer ID field is 2 bits, and each SRS resource list ID field is 6 bits, but the number of bits is not limited to these. Also, the MAC CE in FIG. 7C may be notified to a UE configured for non-codebook-based PUSCH transmission of multiple layers.

[0101] In the third embodiment, the spatial relationship information for the PUSCH is determined based on the SRS resource list activated by the MAC CE. The UE may determine the spatial relationship information based on multiple SRS resource lists, each corresponding to spatial relationship information for each layer, specified by the MAC CE, for example, in FIG. 7C. Therefore, the spatial relationship information may not be identified by the DCI, and the SRI field of the DCI may be reduced or used for other purposes.

[0102] According to the third embodiment described above, it is possible to appropriately perform PUSCH repeated transmission based on the SRS resource list specified by the MAC CE, among the SRS resource lists configured by the RRC.

[0103] <Fourth embodiment> In a fourth embodiment, the UE is informed of spatial relationship information for PUSCH across multiple TRPs by a combination of MAC CE and DCI.

[0104] 8A-8C are diagrams showing an example of notification of spatial relationship information according to the fourth embodiment. Hereinafter, a description will be given with reference to Figs. 8A-8C. Points not particularly mentioned may be the same as those in the first embodiment.

[0105] In the fourth embodiment, it is assumed that the UE is configured with a predetermined number (e.g., M) of SRS resources associated with one SRS resource set by RRC signaling, where M=2 corresponds to the SRS resource set for codebook-based transmission in Rel.15 NR, and M=4 corresponds to the SRS resource set for non-codebook-based transmission in Rel.15 NR.

[0106] FIG. 8A shows an example in which a plurality of SRS resources (SRS resources #0, #1, . . . ) are configured in association with an SRS resource set.

[0107] In the fourth embodiment, the UE may be activated (or indicated) by the MAC CE with a predetermined number (e.g., N) of SRI sequences, where the SRI sequence may be a combination (set) of 1 to a maximum of R SRS resources, and may be referred to as an SRI set, an SRI group, etc., where R may correspond to the maximum number of TRPs for the PUSCH.

[0108] As the MAC CE, a MAC CE in which an SRI sequence ID is associated with a MAC CE described in the following fifth embodiment may be used.

[0109] In the fourth embodiment, one or more SRI sequences among the activated SRI sequences may be indicated to the UE using a field of the DCI.

[0110] 8B is a diagram showing an example of a correspondence relationship of DCI fields for specifying one SRI sequence according to the fourth embodiment. In this example, a value of a certain field included in DCI ("Bit field mapped to index") and a corresponding activated SRI sequence are shown. The number of bits of the field may be determined based on the maximum number of SRI sequences that can be activated.

[0111] For example, the first SRI sequence may include SRS resource #0. The second SRI sequence may include {SRS resources #0, #1}.

[0112] Fig. 8C is a diagram showing an example of a DCI field for specifying a plurality of SRI sequences according to the second embodiment. This example is similar to Fig. 5D, except that each bit field corresponds to Fig. 8B.

[0113] Note that, when M=1 or the number of SRI sequences activated is 1, the UE may assume that the DCI field for specifying the SRI sequence is 0 bit.

[0114] According to the fourth embodiment described above, PUSCH repeated transmission can be appropriately performed based on the SRI sequence designated by DCI among the SRI sequences activated by the MAC CE.

[0115] <Fifth embodiment> In a fifth embodiment, the UE is informed by the MAC CE of spatial relationship information for PUSCH across multiple TRPs.

[0116] 9A-9C are diagrams showing an example of notification of spatial relationship information according to the fifth embodiment. Hereinafter, a description will be given with reference to FIG. 9A-9C. Points not particularly mentioned may be the same as those in the fourth embodiment.

[0117] In the fifth embodiment, it is assumed that the UE is configured with a predetermined number (eg, M) of SRS resources associated with one SRS resource set through RRC signaling. Figure 9A is the same as Figure 8A.

[0118] In the fifth embodiment, the UE may be activated (or indicated) by the MAC CE with one or up to a predetermined number (eg, N) of SRI sequences.

[0119] FIG. 9B is a diagram showing an example of an SRI sequence (or SRS resource) activation / deactivation MAC CE according to the fifth embodiment. FIG. 9B is the same as FIG. 5B, but includes the following: i The difference is that the " field indicates an SRS resource, not an SRS resource list. i " fields may be assumed to indicate a 1.

[0120] For example, if the MAC CE of FIG. 9B is signaled indicating S1=S0=1, the UE may determine that the SRI sequence includes {SRS resources #0, #1}.

[0121] FIG. 9C is a diagram showing another example of an SRI sequence (or SRS resource) activation / deactivation MAC CE according to the fifth embodiment. FIG. 9C is similar to FIG. 7C, but instead of the SRS resource list ID field, a field “S k,i " is included.

[0122] For example, S 1、1 =S 1、0 =S 2、2 =S 2、19C indicating {SRS resource #0, #1}, the UE may determine that the SRI sequence corresponding to the first layer ID includes {SRS resource #1, #2}.

[0123] According to the fifth embodiment described above, PUSCH repeated transmission can be appropriately performed based on the SRI sequence specified by the MAC CE.

[0124] Sixth embodiment In a sixth embodiment, the UE is informed of spatial relationship information for PUSCH across multiple TRPs by DCI.

[0125] 10A to 10C are diagrams showing an example of notification of spatial relationship information according to the sixth embodiment. Hereinafter, a description will be given with reference to Figs. 10A to 10C. Points not particularly mentioned may be the same as those in the fourth embodiment.

[0126] In the sixth embodiment, it is assumed that the UE is configured with a predetermined number (eg, M) of SRS resources associated with one SRS resource set through RRC signaling. Figure 10A is the same as Figure 8A.

[0127] In a sixth embodiment, the UE may be indicated one or up to a predetermined number (eg, N) of SRI sequences by a field in the DCI.

[0128] 10B is a diagram showing an example of a correspondence relationship of DCI fields for specifying one SRI sequence according to the sixth embodiment. In this example, a value of a certain field included in DCI ("Bit field mapped to index") and a corresponding SRI sequence are shown.

[0129] For example, the first SRI sequence may include SRS resource #0. The second SRI sequence may include {SRS resources #0, #1}. Each SRI sequence may be predefined by a specification.

[0130] Fig. 10C is a diagram showing an example of a DCI field for specifying a plurality of SRI sequences according to the sixth embodiment. This example is similar to Fig. 5D, but differs in that each bit field corresponds to Fig. 10B.

[0131] According to the sixth embodiment described above, PUSCH repeated transmission can be appropriately performed based on the SRI sequence specified by DCI.

[0132] Seventh embodiment In the seventh embodiment, a TCI state may be used as (or instead of) spatial relationship information for PUSCH across multiple TRPs. The TCI state may correspond to at least one of a downlink TCI state (DL TCI state), an uplink TCI state (UL TCI state), and a unified TCI state. The UL TCI state may be replaced with spatial relationship information (spatialrelationinfo).

[0133] Here, the unified TCI state may mean a TCI state that is commonly used in both DL and UL.

[0134] In the seventh embodiment, the UE may determine spatial relationship information for PUSCH across multiple TRPs in accordance with the spatial relationship information, SRS resources, SRI, etc. in at least one of the above-mentioned first to sixth embodiments, which are respectively replaced with TCI state information, TCI state, TCI state ID, etc.

[0135] The TCI state may be configured separately from the configuration of the SRS resource set, the configuration of the SRS resource, etc. (for example, it may be configured by PUSCH configuration information (PUSCH-Config)).

[0136] For example, the UE may be configured with a list of TCI states (eg, UL TCI states) for the PUSCH via RRC signaling.

[0137] The UE may be activated (or indicated) by the MAC CE with a predetermined number (e.g., N) of TCI state sets, where a TCI state set may be a combination (set) of 1 to a maximum of R TCI states, and may be referred to as a set of TCI states, a TCI state group, etc., where R may correspond to a maximum number of TRPs for the PUSCH.

[0138] The UE may determine a TCI state set to be used for a precoder for the PUSCH based on the DCI. The TCI state set may correspond to at least one of a TCI state set configured by the RRC, a TCI state set activated by the MAC CE, a TCI state set predefined by a specification, etc.

[0139] 11A to 11C are diagrams illustrating an example of notification of spatial relationship information according to the seventh embodiment. 11A and 11B correspond to RRC information elements described using ASN.1 (Abstract Syntax Notation One) notation.

[0140] As shown in FIG. 11A, the PUSCH configuration information (PUSCH-Config) may include a list of spatial relationship information for PUSCH (SpatialrelationinfoToAddModList). Each Spatialrelationinfo-r17 included in the list may represent new spatial relationship information after Rel. 17, or may represent existing spatial relationship information. The spatial relationship information may be associated with a spatial relationship information ID (SpatialrelationinfoId).

[0141] As shown in FIG. 11B, the PUSCH configuration information (PUSCH-Config) may include a list of unified TCI states for the PUSCH (utci-StatesToAddModList). Each uTCI-State included in the list may represent a separate unified TCI state. The unified TCI state may be associated with a unified TCI state ID (uTCI-StateId).

[0142] Fig. 11C is a diagram showing an example of a correspondence relationship of DCI fields for specifying one TCI state set (spatial relationship information set) according to the seventh embodiment. A UE to which the list of spatial relationship information in Fig. 11A is set may be instructed to specify a TCI state set based on the correspondence relationship between the DCI fields and Fig. 11C.

[0143] 11C shows DCI code points (values ​​of a certain field) and corresponding spatial relation state sets. For example, code point=000 may correspond to spatial relation information #0 (Spatialrelationinfo #0), code point=001 may correspond to spatial relation information #1 (Spatialrelationinfo #1), and code point=010 may correspond to spatial relation information #0 and #1 (Spatialrelationinfo #0 and #1).

[0144] According to the seventh embodiment described above, PUSCH repeated transmission can be appropriately performed based on the TCI state available for UL.

[0145] <Other> In each of the above-mentioned embodiments, a UE to which one SRS resource (or an SRS resource list including one SRS resource) is designated for PUSCH repeated transmission may transmit the repeated transmission based on the SRS resource. Note that the repeated transmission based on the SRS resource may mean repeated transmission based on a spatial relationship determined based on the SRS resource (e.g., using a spatial domain transmission filter based on the spatial relationship).

[0146] In each of the above-described embodiments, a UE to which multiple SRS resources (or an SRS resource list including multiple SRS resources) are specified for PUSCH repeat transmission may transmit a part of the repeat transmission based on some of these SRS resources, and transmit the rest of the repeat transmission based on the rest.

[0147] In addition, the DCI (or a field of the DCI) in each of the above-mentioned embodiments may be read as an implicit notification using the DCI. This implicit notification using the DCI may include at least one of the following: (detected) DCI (or corresponding to the DCI or used for receiving the DCI), a time resource, a frequency resource, a control channel element (CCE) index, a physical resource block (PRB) index, a resource element (RE) index, a search space index, a control resource set (CORESET) index, and an aggregation level.

[0148] The UE may apply the same embodiment among the above-mentioned first to seventh embodiments to the codebook-based transmission and the non-codebook-based transmission. The UE may apply different embodiments among the above-mentioned first to seventh embodiments to the codebook-based transmission and the non-codebook-based transmission.

[0149] The UE may switch between a plurality of embodiments among the above-mentioned first to seventh embodiments. For example, the first, third, fourth or fifth embodiment using MAC CE may be applied when the UE is configured by RRC (e.g., configured to use MAC CE-based control for PUSCH repeat transmission) or receives a new MAC CE (e.g., MAC CE as shown in the first embodiment), otherwise, non-MAC CE-based control (the second or sixth embodiment) may be applied.

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

[0151] (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.

[0152] 12 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).

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

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

[0155] 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))).

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

[0157] 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).

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

[0159] 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).

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

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

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

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

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

[0165] 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 a downlink channel.

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

[0167] 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).

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

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

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

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

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

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

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

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

[0176] 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).

[0177] (base station) 13 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0194] In addition, the transceiver 120 may transmit to the user terminal 20 at least one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, and Downlink Control Information (DCI), which are used to determine spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for multiple transmission and reception points.

[0195] The transceiver 120 may receive the PUSCH repeatedly transmitted by the user terminal 20 using a spatial domain transmit filter based on the spatial relationship information.

[0196] (User terminal) 14 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 transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0213] In addition, the control unit 210 may determine spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for multiple transmission and reception points by using at least one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, and Downlink Control Information (DCI).

[0214] The transceiver 220 may repeatedly transmit the PUSCH using a spatial domain transmit filter based on the spatial relationship information. Note that in the present disclosure, the spatial relationship information and the spatial relationship may be interpreted as interchangeable.

[0215] The control unit 210 may determine the spatial relationship information based on a Sounding Reference Signal (SRS) resource list associated with a measurement reference signal (SRS) resource set configured by the RRC signaling.

[0216] The control unit 210 may determine the spatial relationship information based on a plurality of SRS resource lists each corresponding to spatial relationship information for each layer. The control unit 210 may determine the plurality of SRS resource lists each corresponding to spatial relationship information for each layer based on at least one of MAC CE and DCI.

[0217] (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.

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

[0219] 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. 15 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.

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

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

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

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

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

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

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

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

[0228] 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).

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

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

[0231] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0249] 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".

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

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

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

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

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

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

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

[0257] 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).

[0258] 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).

[0259] 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).

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

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

[0262] 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).

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

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

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

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

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

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

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

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

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

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

[0273] 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)), 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).

[0274] 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."

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

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

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

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

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

[0280] 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."

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

[0282] 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."

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

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

[0285] 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 control unit that determines spatial relationship information for an uplink shared channel (PUSCH) for a plurality of transmission and reception points based on the SRS resource set for a specific purpose specified by a field of downlink control information (DCI) when receiving configuration information on a sounding reference signal (SRS) resource set for a specific purpose by Radio Resource Control (RRC) signaling; A transmitting unit that repeatedly transmits the PUSCH based on the spatial relationship information, When the control unit uses a Transmission Configuration Indicator (TCI) state as the spatial relationship information, the control unit repeatedly transmits the PUSH using a TCI state set that corresponds to a DCI code point and is commonly used in both downlink and uplink.

2. 2. The terminal of claim 1, wherein the specific application is a codebook (CB) or a noncodebook (NCB).

3. When receiving configuration information on a sounding reference signal (SRS) resource set for a specific purpose through Radio Resource Control (RRC) signaling, determining spatial relationship information for an uplink shared channel (PUSCH) for a plurality of transmission and reception points based on the SRS resource set for the specific purpose specified by a field of downlink control information (DCI); repeatedly transmitting the PUSCH based on the spatial relationship information; When a Transmission Configuration Indicator (TCI) state is used as the spatial relationship information, the terminal repeatedly transmits the PUSH using a TCI state set that corresponds to a DCI code point and is commonly used in both downlink and uplink.

4. A transmitter that transmits, to a terminal, downlink control information (DCI) including a field specifying a sounding reference signal (SRS) resource set for a specific purpose, which is used to determine spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for a plurality of transmission and reception points, when transmitting configuration information regarding a sounding reference signal (SRS) resource set for a specific purpose by Radio Resource Control (RRC) signaling; a receiving unit for receiving the PUSCH repeatedly transmitted by the terminal based on the spatial relationship information, A base station, wherein when a Transmission Configuration Indicator (TCI) state is used as the spatial relationship information, the receiving unit receives the PUSH repeatedly transmitted by the terminal using a TCI state set that corresponds to a DCI code point and is commonly used in both downlink and uplink.

5. A system having a terminal and a base station, When the terminal receives configuration information regarding a sounding reference signal (SRS) resource set for a specific purpose by Radio Resource Control (RRC) signaling, a control unit that determines spatial relationship information for an uplink shared channel (PUSCH) for a plurality of transmission and reception points based on the SRS resource set for the specific purpose specified by a field of downlink control information (DCI); A transmitting unit that repeatedly transmits the PUSCH based on the spatial relationship information, When a Transmission Configuration Indicator (TCI) state is used as the spatial relationship information, the control unit repeatedly transmits the PUSCH using a TCI state set that corresponds to a DCI code point and is commonly used in both downlink and uplink; A transmitter that transmits the DCI to the terminal when the base station transmits the configuration information by the RRC signaling, the DCI being used to determine the spatial relationship information for the PUSCH; a receiving unit for receiving the PUSCH repeatedly transmitted by the terminal based on the spatial relationship information, A system in which, when the receiving unit uses the TCI state as the spatial relationship information, it receives the PUSCH repeatedly transmitted by the terminal using the TCI state set.

Citation Information

Patent Citations

  • User terminal and wireless communication method

    WO2019244207A1

  • User terminal and wireless communication method

    WO2020031353A1