Terminal, wireless communication method, base station, and system

By increasing the SRS resource set and the number of resources, and dynamically adjusting the spatial relationships, the problem of low efficiency in updating SRS spatial relationships in NR is solved, enabling fast and flexible beam management and improving mobility and efficiency.

CN115918198BActive Publication Date: 2026-05-08NTT DOCOMO INC
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
NTT DOCOMO INC
Filing Date
2020-01-24
Publication Date
2026-05-08

AI Technical Summary

Technical Problem

In NR systems after Rel.16, existing technologies struggle to quickly and dynamically update the SRS spatial relationships of user terminals, resulting in inefficient beam management.

Method used

By increasing the number of SRS resource sets and resources, and flexibly setting spatial relationship information through RRC and MAC CE signaling, the spatial relationship of SRS resources can be dynamically adjusted to support more SRS resource sets and resources, and reduce the size of the SRI field to improve efficiency.

Benefits of technology

It enables rapid and flexible control of the spatial relationships of SRS, improves the efficiency and adaptability of beam management, supports more SRS resource sets and resources, and meets the needs of mobility inside and outside the cell.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115918198B_ABST
    Figure CN115918198B_ABST
Patent Text Reader

Abstract

A terminal according to one embodiment of the present disclosure includes a control unit that determines the size of an SRS Resource Indicator (SRI) field of downlink control information that indicates transmission in a case where more than two SRS resources are set for codebook-based transmission or in a case where more than four SRS resources are set for non-codebook transmission, and a transmission unit that performs the transmission based on the SRS resources indicated by the SRI field. According to one embodiment of the present disclosure, the spatial relation of the SRS can be appropriately designated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, base stations, and systems in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] The study also explored subsequent systems to LTE (e.g., also known as the 5th generation mobile communication system (5G), 5G+ (plus), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] 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

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., NR), user terminals (user equipment (UE)) control the transmission processing of uplink channels, signals, etc. (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) based on spatial relations.

[0009] In Rel.15 NR, the configuration information for the measurement reference signal (SRS) resources assigned to the UE includes spatial relation information (also known as Spatial Relation Information (SRI)). That is, SRS resources are linked and configured one-to-one with spatial relations. However, in NR versions after Rel.16, it is required that spatial relations be dynamically changed with respect to SRS.

[0010] Therefore, one of the purposes of this disclosure is to provide a terminal, wireless communication method, and base station capable of appropriately specifying the spatial relationships of SRS.

[0011] Methods for solving problems

[0012] One aspect of this disclosure relates to a terminal comprising: a control unit that determines the size of an SRS Resource Indicator (SRI) field for indicating downlink control information for transmission when more than two measurement reference signal (SRS) resources are set for codebook-based transmission, or when more than four SRS resources are set for non-codebook transmission; and a transmission unit that performs the transmission based on the SRS resources indicated by the SRI field.

[0013] Invention Effects

[0014] According to one method of this disclosure, the spatial relationships of SRS can be appropriately specified. Attached Figure Description

[0015] Figure 1 This is a diagram illustrating an example of spatial relationship information in SRS.

[0016] Figure 2 This is a diagram illustrating an example of an SRI indication for codebook-based transmission in Implementation 1.1.

[0017] Figure 3 This indicates that in implementation 1.1, transmission is based on a non-codebook and L max A diagram showing an example of an SRI indicator with a value of 1.

[0018] Figure 4 This indicates that in implementation 1.1, transmission is based on a non-codebook and L max A diagram illustrating an example of an SRI indicator with a value of 2.

[0019] Figure 5A as well as Figure 5B This is a diagram illustrating an example of the reduction in the size of the SRI field in implementation method 1.1.

[0020] Figure 6A as well as Figure 6B This is a diagram illustrating an example of an SRS resource ID assigned to multiple SRS resource sets in implementation 1.2.

[0021] Figure 7 This is a diagram illustrating an example of an SRI indication used for codebook-based transmission when multiple SRS resource sets are spanned and the SRS resource ID is unique.

[0022] Figure 8A as well as Figure 8B This is a diagram illustrating an example of an SRI indication used for codebook-based transmission in the case of multiple SRS resource sets where the SRS resource ID is shared.

[0023] Figures 9A to 9C This is a diagram illustrating an example of the correspondence between the SRI field and the SRSI field.

[0024] Figure 10A as well as Figure 10B This is a diagram illustrating an example of the reduction in the size of the SRSI field in implementation method 1.2.

[0025] Figure 11 This is a diagram illustrating an example of setting information for the spatial relationships of the SRS involved in the second embodiment.

[0026] Figure 12A as well as Figure 12B This is a diagram illustrating an example of MACCE for spatial relationship updating of P-SRS according to the third embodiment.

[0027] Figure 13 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0028] Figure 14 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0029] Figure 15 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0030] Figure 16 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment. Detailed Implementation

[0031] (SRS)

[0032] In NR, the use of measurement reference signals (SRS) is widespread. NR's SRS is used not only for CSI measurements in the uplink (UL) used in existing LTE (LTE Rel.8-14), but also for CSI measurements in the downlink (DL), beam management, and more.

[0033] A UE can also be configured with one or more SRS resources. SRS resources can also be identified through the SRS Resource Index (SRI).

[0034] Each SRS resource can also have one or more SRS ports (or correspond to one or more SRS ports). For example, the number of ports for each SRS can be 1, 2, 4, etc.

[0035] The UE can also be configured with one or more SRS resource sets. An SRS resource set can also be associated with a specific number of SRS resources. The UE can also use higher-level parameters publicly with respect to the SRS resources contained in an SRS resource set. In addition, the resource set in this disclosure can also be replaced with a collection, resource group, group, etc.

[0036] Information related to SRS resources or resource sets can also be set to the UE using higher-layer signaling, physical-layer signaling, or a combination thereof.

[0037] Additionally, in this disclosure, higher-layer signaling may be any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc.

[0038] MAC signaling can also use MAC Control Element (MAC CE) or MAC Protocol Data Unit (PDU). Broadcast information can also be Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), or Other System Information (OSI).

[0039] Physical layer signaling can also be, for example, downlink control information (DCI).

[0040] SRS configuration information (e.g., "SRS-Config" in the RRC information element) can also include SRS resource set configuration information, SRS resource configuration information, etc.

[0041] SRS resource set configuration information (e.g., the "SRS-ResourceSet" parameter of the RRC) may also include the SRS resource set ID (identifier) ​​(SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, the SRS resource type, and the usage of the SRS.

[0042] Here, the SRS resource type can also represent any of the following: Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), or Aperiodic SRS (A-SRS). Additionally, the UE can periodically (or periodically after activation) send P-SRS and SP-SRS. The UE can also send A-SRS based on SRS requests from the DCI.

[0043] Furthermore, the uses of SRS (the "usage" in the RRC parameter, the "SRS-SetUse" in the L1 (Layer-1) parameter) can also include beam management, codebook, non-codebook, antenna switching, etc. For example, SRS used for codebook or non-codebook purposes can also be used to determine the precoder for transmission on the SRI-based, codebook-based, or non-codebook-based uplink shared channel (PUSCH) transmission.

[0044] SRS for beam management purposes can also be conceived as follows: for each SRS resource set, only one SRS resource can be transmitted at a specific time instant. Alternatively, if multiple SRS resources belong to different SRS resource sets, these SRS resources can be transmitted simultaneously.

[0045] SRS resource configuration information (e.g., "SRS-Resource" in RRC parameters) may also include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, transmission combo, SRS resource mapping (e.g., time and / or frequency resource location, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hop association information, SRS resource type, sequence ID, spatial relationship information ("SRS-SpatialRelationInfo"), etc.

[0046] The UE can switch the BWP (Bandwidth Part) used for SRS transmission on a per-slot basis, and it can also switch antennas. In addition, the UE can apply at least one of intra-slot hopping and inter-slot hopping to SRS transmission.

[0047] (Spatial Relationships)

[0048] In NR, the UE controls the transmission processing (e.g., transmission, mapping, precoding, modulation, encoding, or at least one of the uplink channels and signals (which can also be expressed as "channel / signal"; hereinafter, "A / B" can also be replaced with "at least one of A and B") based on a specific spatial relation.

[0049] In addition, spatial relationships can also be replaced by quasi-co-location (QCL), QCL concept, transmission configuration indicator state (TCI state), beam, etc.

[0050] Spatial relationships applicable to a specific channel / signal can also be determined by spatial relationship information (SRI) that is notified (set) through higher-layer signaling. Spatial relationship information of the SRS (e.g., "spatialRelationInfo" of the RRC parameter) can also represent the spatial relationship information between a specific reference signal (RS) and the SRS.

[0051] The specific reference signal can also be at least one of a Synchronization Signal Block (SSB), a Channel State Information-Reference Signal (CSI-RS), and a Measurement Reference Signal (Sounding Reference Signal (SRS)). Here, the SSB can also be referred to as a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block.

[0052] Figure 1 This is a diagram representing an example of spatial relationship information in SRS. It is described using ASN.1 (Abstract Syntax Notation One) notation (note that this is only an example and not a complete description).

[0053] In this example, the spatial relationship information of the SRS (e.g., “SRS-SpatialRelationInfo” of RRC IE) may also include at least one of the SSB index, CSI-RS resource ID, and SRS resource ID as an index of the aforementioned specific reference signal (reference RS (parameter “referenceSignal”)).

[0054] Additionally, in this disclosure, the SSB index, SSB resource ID, and SSBRI (SSB Resource Indicator) can be interchanged. Furthermore, the CSI-RS index, CSI-RS resource ID, and CRI (CSI-RS Resource Indicator) can also be interchanged. Furthermore, the SRS index, SRS resource ID, and SRI can also be interchanged.

[0055] The configured SRI may also include at least one of the SSB index, CSI-RS resource ID, and SRS resource ID as an index to the specific RS mentioned above. In addition, the SRI may also include the serving cell index, Bandwidth Part (BWP) ID, etc., corresponding to the specific RS mentioned above.

[0056] In addition, in this disclosure, indexes, IDs, indicators, resource IDs, etc., can be interchanged.

[0057] When spatial relationship information related to the SSB or CSI-RS and the SRS is configured for a certain SRS resource, the UE can also use the same spatial domain filter as the spatial domain filter used to receive the SSB or CSI-RS to transmit the SRS resource. That is, in this case, the UE can also assume that the UE receive beam for the SSB or CSI-RS is the same as the UE transmit beam for the SRS.

[0058] When spatial relationship information is set for a certain SRS (target SRS) resource, which is related to other SRSs (reference SRSs) and the target SRS, the UE can also use the same spatial domain filter as the spatial domain filter used to transmit the reference SRS to transmit the target SRS resource. That is, in this case, the UE can also assume that the UE transmit beam for the reference SRS is the same as the UE transmit beam for the target SRS.

[0059] Furthermore, the spatial domain filter used for base station transmission, the downlink spatial domain transmission filter, and the base station's transmit beam can be interchanged. Similarly, the spatial domain filter used for base station reception, the uplink spatial domain receive filter, and the base station's receive beam can also be interchanged.

[0060] Furthermore, the spatial domain filter used for UE transmission, the uplink spatial domain transmission filter, and the UE's transmit beam can be interchanged. Similarly, the spatial domain filter used for UE reception, the downlink spatial domain receive filter, and the UE's receive beam can also be interchanged.

[0061] Additionally, spatial relationship information (SRI) can also correspond to beams. For example, the UE can be envisioned as transmitting ULs using different beams for different SRIs.

[0062] The beam indication used for the uplink control channel (Physical Uplink Control Channel (PUCCH)) can also be set via higher-layer signaling. For example, if the PUCCH spatial relation information includes a single spatial relation information (SpatialRelationInfo) parameter, the UE can apply this parameter to the PUCCH. If the PUCCH spatial relation information includes more than one spatial relation information parameter, the (activated) parameter applied in the PUCCH can be determined based on the MAC CE.

[0063] In addition, the spatial relationship information of PUCCH can also be obtained by replacing SRS with PUCCH in the spatial relationship information of SRS mentioned above, so it will not be explained again.

[0064] The beam indication used for PUSCH can also be determined based on the SRI (SRS Resource Indicator) field included in the DCI. The UE can also transmit PUSCH using the same transmit beam as the corresponding SRS within the SRS configured by higher layers, based on the specified SRI. Furthermore, the beam indication used for SRS can also be determined in the same way.

[0065] For example, a UE configured to transmit PUSCH based on a codebook can also determine (select) the SRS resources contained in the codebook's SRS resource set based on the SRI field of the DCI.

[0066] UEs configured to transmit PUSCH based on non-codebook can also determine (select) the purpose of SRS based on the SRI field of DCI, using SRS resources contained in the non-codebook SRS resource set.

[0067] Furthermore, the number of SRS resources in an SRS resource set used for codebook purposes can differ from the number of SRS resources in an SRS resource set used for non-codebook purposes; for example, the former could contain 2 resources while the latter contains 4. In this case, the size of the SRI field could also be 1 bit in the former and 2 bits in the latter.

[0068] Additionally, in Rel.15 NR, P-SRS spatial relationships are semi-statically set at SRS resource levels. For codebook-based transmissions, the maximum number of SRS resources is 2, meaning a maximum of 2 spatial relationships can be used. For non-codebook-based transmissions, the maximum number of SRS resources is 4, meaning a maximum of 4 spatial relationships can be used.

[0069] Therefore, regarding P-SRS, if spatial relationships need to be updated based on UE movement, the RRC needs to be reset. Since RRC reset takes a relatively long time, the efficiency of updating spatial relationships in Rel.15 P-SRS is very poor.

[0070] However, in NR versions after Rel.16, in order to improve mobility within and between cells, it is required to update the spatial relationships of P-SRS at a higher speed.

[0071] Therefore, the inventors of this invention have conceived of a method for appropriately setting (or specifying) the spatial relationship of SRS (e.g., P-SRS). According to one aspect of this disclosure, the UL beam of the SRS, the UL beam of the PUSCH, etc., can be flexibly controlled.

[0072] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be applied individually or in combination.

[0073] Additionally, in the following embodiments, SRI can also be replaced with spatial relation information for SRS (also referred to as SRI for SRS, SRS spatial relation info, etc.). Furthermore, "applying SRI ID (or SRI corresponding to SRI ID) in a specific channel / signal" and "applying spatial relation corresponding to SRI ID in a specific channel / signal" can also be interchanged.

[0074] In this disclosure, when the UE has multiple panels, the SRS resource set (or SRS resource set ID) may be the same as or different from the panel (or panel ID).

[0075] In addition, in this disclosure, panels, uplink (UL) transmitting entities, TRPs, spatial relationship information (SRI), spatial relationships, control resource sets (CORESET), PDSCHs, codewords, base stations, specific antenna ports (e.g., DeModulation Reference Signal (DMRS)) ports, specific antenna port groups (e.g., DMRS port groups), and specific groups (e.g., Code Division Multiplexing (CDM) groups, specific reference signal groups, CORESET groups) can also be substituted for each other.

[0076] Furthermore, panel identifiers (IDs) and panels can be interchanged. That is, TRP IDs and TRPs, CORESET group IDs and CORESET groups, etc., can also be interchanged. IDs and indexes can also be interchanged.

[0077] Furthermore, in this disclosure, sequences, lists, sets, groups, etc., can be interchanged.

[0078] (Wireless communication method)

[0079] <First Implementation Method>

[0080] The first embodiment involves increasing the number of spatial relationships set via RRC by at least one of increasing the number of SRS resources set within an SRS resource set and increasing the number of SRS resource sets set. Here, these increases may also refer to increases starting from the maximum number utilized in Rel.15 NR.

[0081] The first implementation method is generally divided into the following implementation methods 1.1 to 1.3:

[0082] (Implementation 1.1) Increase the maximum number of set SRS resources in an SRS resource set without increasing the maximum number of set SRS resources (same as Rel.15).

[0083] (Implementation 1.2) Increase the maximum number of set SRS resource sets, but do not increase the maximum number of set SRS resources within an SRS resource set (same as Rel.15).

[0084] (Implementation method 1.3) Increase both the maximum number of SRS resources set in an SRS resource set and the maximum number of SRS resource sets set.

[0085] Implementation methods 1.1 to 1.3 all relate to codebook-based transmission in which more than two SRS resources are allocated to the UE, or to non-codebook-based transmission in which more than four SRS resources are allocated to the UE.

[0086] [Implementation Method 1.1]

[0087] In implementation 1.1, for UL beam management, the maximum number of SRS resources set within an SRS resource set can also be increased to a value greater than the maximum number (=16) of Rel.15 NR (e.g., 32, 64 or more) based on the UE capability (maxNumberSRS-ResourcePerSet-BM).

[0088] Furthermore, regarding codebook-based transmission (higher-layer parameter txConfig=codebook), the maximum number of SRS resources set within the codebook's SRS resource set can be increased to a value greater than the maximum number (=2) in Rel.15 NR (e.g., 4, 8, 16, 32, 64 or higher). This value can be pre-specified by the specification or determined based on UE capabilities (e.g., maxNumberSRS-ResourcePerSet in mimo-CB-PUSCH).

[0089] Alternatively, it can be based on the number N of SRS resources specified within an SRS resource set whose purpose is codebook. SRS The size (number of bits) of the SRS Resource Indicator (SRI) field in DCI is assumed to be ceil(log2(N)). SRS Here, ceil(X) is the top function of X (the same applies below).

[0090] Figure 2 This is a diagram illustrating an example of an SRI indication used for codebook-based transmission in implementation 1.1. Figure 2 The left column of the table (the bit field mapped to the index) corresponds to the value obtained by mapping the SRI field to the index of the decimal number. The same applies in the following figures.

[0091] The right column of this table corresponds to the SRI (or SRS resource ID) associated with the index. For example... Figure 2 As shown, the index value i (i=0, ..., N) SRS -1) can also correspond to SRI=i respectively. N SRS For example, it could also be 4, 8, 16, 32, 64, etc. Furthermore, the correspondence is not limited to... Figure 2 Examples. It can also be done for each N. SRS Different values ​​correspond to different relationships.

[0092] In addition, for non-codebook-based transmission (higher-layer parameter txConfig = nonCodebook), the maximum number of configured SRS resources within the SRS resource set used for the codebook can also be increased to a value greater than that maximum number in Rel.15 NR (= 4) (e.g., 8, 16, 32, 64, or a value greater than that). Additionally, this value can be either predefined by the specification or determined based on UE capabilities (e.g., maxNumberSRS-ResourcePerSet of mimo-NonCB-PUSCH).

[0093] It can also be based on the number N of configured SRS resources within the SRS resource set used for non-codebook SRS , and the size (number of bits) of the SRS resource indicator field envisioned as DCI is obtained by ceil(log2( )).

[0094] In addition, when the maximum multiple-input multiple-output (Multi Input Multi Output (MIMO)) layer (higher-layer parameter "maxMIMO-Layers") is configured for the UE, L max can also be determined based on this parameter; otherwise, L max can also be provided by the maximum number of layers of PUSCH supported by the UE for non-codebook-based transmission.

[0095] Figure 3 is a diagram showing an example of the SRI indication for non-codebook-based transmission in Embodiment 1.1 and L max = 1. In this example, up to 1 SRI (or SRS resource ID) corresponding to the index in the case of N SRS = x (x = 2,..., 8) is shown. As Figure 3 shown, the value of the index i (i = 0,..., N SRS - 1) can also correspond to SRI = i respectively. Additionally, the correspondence is not limited to the Figure 3 example.

[0096] Figure 4 is a diagram showing an example of the SRI indication for non-codebook-based transmission in Embodiment 1.1 and L max = 2. In this example, up to 2 SRIs (or SRS resource IDs) corresponding to the index in the case of N SRS = x (x = 2,..., 8) are shown. Additionally, the correspondence is not limited to the Figure 3 example.

[0097] <<Reduction of SRI field size>>

[0098] Additionally, in order to use the SRI field of DCI to specify the set N SRS All of an SRS resource, such as Figures 2 to 4 As shown, the number of bits depends on N. SRS Therefore, it is preferable to reduce (or limit) the size of the SRI field.

[0099] For example, the size of the SRI field can also be determined based on the number of active SRS resources (e.g., the number of active SRS resources used for codebook or non-codebook purposes). Here, the UE can also activate or deactivate SRS resources set by RRC based on MAC CE.

[0100] Figure 5A as well as Figure 5B This is a diagram illustrating an example of the reduction in the size of the SRI field in implementation method 1.1. Figure 5A Corresponding to Figure 2 In the example of the SRI indication shown for codebook-based transmission, N SRS When the value is 8, the SRI field size is 6 bits.

[0101] Figure 5B This example illustrates how the UE determines the SRI field size based on the number of active SRS resources. Here, we assume the SRS resources corresponding to SRI=2 and 3 are active. In this case, the number of active SRS resources is 2, therefore, the UE can also determine that the SRI field size is log22=1 bit. The UE can also assume that the SRI corresponding to deactivated SRS resources is not specified through the SRI field (in...). Figure 5B In this context, the SRI field value is represented by '-'.

[0102] In addition, the UE can also be assumed to have the same SRI field size (or the number of possible values ​​of SRI that can be specified through the SRI field) as Rel.15.

[0103] The UE can also be envisioned as follows: when the SRS resource set used for codebook is configured with more than 2 SRS resources, the SRI field for codebook-based transmission is 1 bit (e.g., the SRI values ​​that can be represented are 0 and 1).

[0104] The UE can also be envisioned as follows: when there are more than 4 SRS resources set for non-codebook SRS resource sets, the SRI field for non-codebook-based transmission is 2 bits (e.g., the SRI value that can be expressed is 0 to 3).

[0105] The UE can also have the SRI field size set via higher-layer signaling (or the possible values ​​of the SRI that can be specified via the SRI field).

[0106] The UE can also determine the SRI field size (or the possible values ​​of the SRI that can be specified through the SRI field) based on specific UE capabilities. For example, the UE can also decide that, if it reports support for that specific UE capability, the SRI field size is larger than that based on N. SRS The value that is determined is small.

[0107] These reductions in SRI field sizes can be applied either to one party in codebook-based transmissions or non-codebook-based transmissions, or to both parties. When applied to both parties, the SRI field size can be the same for both parties or different values ​​can be applied. For example, the UE can also use higher-layer signaling to set different values ​​for parameters related to the SRI field size for codebook-based transmissions and for parameters related to the SRI field size for non-codebook-based transmissions.

[0108] [Implementation Method 1.2]

[0109] In implementation 1.2, more than one SRS resource set may be set for the same purpose. For example, the maximum number of SRS resource sets that can be set for codebook or non-codebook purposes can be predetermined by the specification or determined based on the UE capabilities.

[0110] Figure 6A as well as Figure 6B This diagram illustrates an example of an SRS resource ID assigned to multiple SRS resource sets in implementation 1.2. In this example, it is assumed that the SRS resource sets #0 to #3 illustrated have the same purpose (e.g., codebook, non-codebook), but are not limited thereto.

[0111] Figure 6A This indicates an example where the SRS resource ID is unique across multiple SRS resource sets. In this case, the UE can also assume that the same SRS resource ID is not assigned for different SRS resource sets. Figure 6A In this context, for SRS resource set #k (k=0 to 3), SRS resources #2k and #2k+1 are set.

[0112] Figure 6B This represents an example where the SRS resource ID is shared across multiple SRS resource sets. In this case, the UE can also be designed so that the same SRS resource ID is set for different SRS resource sets. Alternatively, the UE can be designed so that the same SRS resource ID is set for all SRS resource sets.

[0113] exist Figure 6B In this configuration, SRS resources #0 and #1 are set for the entire SRS resource set #k (k=0 to 3). Based on this structure, for example, even when using the same SRS resources, the UE can apply different beams (QCL concept) to transmit PUSCH based on the SRS resource set.

[0114] <<Codebook-based transmission>>

[0115] A UE configured for codebook-based transmission can also be envisioned where the SRS resource set and both sides of the SRS resources are determined solely through the SRI field. In this case, the UE can also be envisioned with an SRI field size of [missing information]. .

[0116] Here, N SRS,m M is the set number of SRS resources contained in an SRS resource set m used as a codebook. SRS set It is the number of SRS resource sets set for the purpose of codebook.

[0117] The correspondence (mapping relationship) between SRI fields and SRS resources can be predefined by a specification or determined by at least one of the following rules.

[0118] Figure 7 This is a diagram illustrating an example of an SRI indication used for codebook-based transmission, where the SRS resource ID is unique across multiple SRS resource sets. Figure 7 In the example, each index value is specified to represent a distinct SRS resource ID. In this case, if an SRS resource ID is specified, the SRS resource set is also specified.

[0119] Figure 8A as well as Figure 8B This is a diagram illustrating an example of an SRI indication used for codebook-based transmission when multiple SRS resource sets are spanned and SRS resource IDs are shared. In these examples, each N... SRS,m =2、M SRS set The case of =4, but not limited to this.

[0120] Figure 8A It is a diagram showing the correspondence between SRI indicators and SRS resources, which are rearranged in order of SRS resource ID as primary (first) order and SRS resource set ID as secondary (second) order, and are associated with them in ascending order as indexes.

[0121] Figure 8BIt is a diagram showing the correspondence between SRI indicators and SRS resources, which are rearranged in order of SRS resource set ID as primary (first) order and SRS resource ID as secondary (second) order, and are associated in ascending order with these as indexes.

[0122] In addition, UEs configured to transmit based on codebooks can also determine the SRS resource set based on the SRS Resource Set Indication (SRSI) field newly included in the DCI, and determine the SRS resources within the SRS resource set based on the SRI field.

[0123] Figures 9A to 9C This is a diagram illustrating an example of the correspondence between the SRI field and the SRSI field. Figure 9A This is a diagram illustrating an example of the mapping relationship of SRI fields for codebook-based transmission when the SRS resource ID is unique across multiple SRS resource sets.

[0124] In this example, the first SRS resource can also refer to the SRS resource corresponding to the smallest SRS resource ID in the SRS resource set specified by SRSI. The second SRS resource can also refer to the SRS resource corresponding to an ID that is larger than the first SRS resource. In addition, the terms "larger" and "smaller" in this disclosure can be used interchangeably.

[0125] Figure 9B This is a diagram illustrating an example of the mapping between SRI fields used for codebook-based transmission when SRS resource IDs are shared across multiple SRS resource sets. In this example, index 0 corresponds to SRI=0, and index 1 corresponds to SRI=1, but it is not limited to this.

[0126] Figure 9C This is a diagram illustrating an example of the mapping between SRSI fields used for codebook-based transmission. In this example, index = i corresponds to the (i+1)th SRS resource set, but it is not limited to this.

[0127] <<Non-codebook-based transmission>>

[0128] A UE configured for non-codebook-based transmission can also be conceived as having any SRS resource from any SRS resource set simultaneously specified solely through the SRI field. In this case, based on the SRI field, for example, SRS resource #0 of the first SRS resource set and SRS resource #3 of the second SRS resource set can be specified to the UE.

[0129] In addition, a UE configured for non-codebook-based transmission may also be considered such that any SRS resource of only the same SRS resource set can be simultaneously specified only through the SRI field. In this case, based on the SRI field, for example, a group of SRS resource #0 of the first SRS resource set and SRS resource #3 of the same first SRS resource set can be specified for the UE, while a group of an SRS resource of the first SRS resource set and an SRS resource of the second SRS resource set cannot be specified for the UE.

[0130] The UE may also determine that the size of the SRI field capable of simultaneously specifying any SRS resource of any SRS resource set is bits. In addition, the UE may also determine that the size of the SRI field capable of simultaneously specifying any SRS resource of only the same SRS resource set is bits.

[0131] Here, N SRS,m is the number of configured SRS resources included in the SRS resource set m for non-codebook use, and M SRS set is the number of configured SRS resource sets for non-codebook use.

[0132] In addition, a UE configured for non-codebook-based transmission may also determine the SRS resource set based on the above-mentioned SRSI field and determine the SRS resources within the SRS resource set based on the SRI field. In this regard, since it duplicates the content described in Figures 9A to 9C , it will not be repeated here.

[0133] <<Reduction of SRI and SRSI Field Sizes>>

[0134] Regarding Embodiment 1.2, the size of the SRI field may also be reduced by the same method as in Embodiment 1.1. In addition, in Embodiment 1.2, the size of the SRSI field may also be reduced.

[0135] For example, the size of the SRSI field may also be determined based on the number of active SRS resource sets (e.g., the number of active SRS resource sets for codebook or non-codebook use). Here, the UE may also activate or deactivate the SRS resource sets configured through RRC based on the MAC CE.

[0136] Figure 10A And Figure 10B is a diagram showing an example of the reduction of the SRSI field size in Embodiment 1.2. Figure 10A shows the case where only the second SRS resource set is the active SRS resource set, Figure 10B shows the case where the active SRS resource sets are the second SRS resource set and the third SRS resource set.

[0137] exist Figure 10A In this case, the number of active SRS resource sets is 1. The UE can also determine that the SRSI field is log21 = 0 bits. The UE can assume that the SRS resource specified through the SRI field is an SRS resource contained in the second SRS resource set.

[0138] exist Figure 10B In this case, the number of activated SRS resource sets is 2. The UE can also determine that the SRSI field is log22 = 1 bit. The UE can also assume that the SRI corresponding to the deactivated SRS resource was not specified through the SRI field (in...). Figure 5B In this context, the value of the SRI field is represented by '-'.

[0139] In addition, in such Figure 7 , Figure 8A , Figure 8B If the SRS resource set and both SRS resources are determined solely by the SRI field, the size of the SRI field can also be determined using the same method based on the active SRS resource and one or both of the active SRS resource set.

[0140] In addition, the UE can also be designed so that the sum of the SRI field size and the SRSI field size is the same as Rel.15.

[0141] The UE can also envision that, when multiple SRS resource sets for the purpose of codebooks are set, the sum of the SRI field size and the SRSI field size for codebook-based transmission is 1 bit (e.g., the SRI values ​​that can be represented are 0 and 1).

[0142] The UE can also envision that, in the case where multiple SRS resource sets for non-codebook purposes are set, the sum of the SRI field size and the SRSI field size for non-codebook-based transmission is 2 bits (e.g., the SRI value that can be expressed is 0 to 3).

[0143] The SRSI field size can also be set by higher-layer signaling. Alternatively, the SRSI field size can be determined based on specific UE capabilities.

[0144] The reduction of these SRI and SRSI field sizes can be applied either to one party in codebook-based transmission and the other in non-codebook-based transmission, or to both parties. When applied to both parties, the SRSI field size can be the same for both parties or different values ​​can be applied. For example, the UE can also use higher-layer signaling to set different values ​​for parameters related to the SRSI field size for codebook-based transmission and for parameters related to the SRSI field size for non-codebook-based transmission.

[0145] [Implementation Method 1.3]

[0146] In implementation 1.3, regarding codebook-based transmission (higher-layer parameter txConfig=codebook), more than one SRS resource set used for codebooks can also be set for the UE. Furthermore, regarding codebook-based transmission, the maximum number of SRS resources that can be set within the SRS resource set used for codebooks can be increased to a value greater than the maximum number (=2) of Rel.15 NR (e.g., 4, 8, 16, 32, 64 or higher).

[0147] The maximum number of configurable SRS resource sets for codebook-based transmission can be predetermined by the specification or determined based on UE capabilities. The maximum number of configurable SRS resources for codebook-based transmission (the maximum number of SRS resources within one SRS resource set) can be predetermined by the specification or determined based on UE capabilities.

[0148] In implementation 1.3, furthermore, regarding non-codebook-based transmission (higher-layer parameter txConfig=nonCodebook), more than one SRS resource set for non-codebook purposes can also be set for the UE. Furthermore, regarding non-codebook-based transmission, the maximum number of SRS resources that can be set within the non-codebook-based SRS resource set can be increased to a value greater than the maximum number (=4) of Rel.15 NR (e.g., 8, 16, 32, 64 or higher).

[0149] The maximum number of configurable SRS resource sets for non-codebook-based transmission can be predetermined by the specification or determined based on UE capabilities. The maximum number of configurable SRS resources for non-codebook-based transmission (the maximum number of SRS resources within one SRS resource set) can be predetermined by the specification or determined based on UE capabilities.

[0150] Regarding the setting of SRS resources and the method for determining the SRI and SRSI fields in Implementation 1.3, it can be the same as at least one of Implementations 1.1 and 1.2. Additionally, the N shown in Implementation 1.2... SRS,m In implementation method 1.3, the method may also vary for each m.

[0151] According to the first embodiment described above, a large number of SRIs can be dynamically switched and utilized.

[0152] <Second Implementation Method>

[0153] The second implementation involves spatial relationship information of the SRS. In the second implementation, for more flexible control of spatial relationships, the reference RS (baseline RS) corresponding to the target SRS can support not only SSB, CSI-RS, P-SRS, and SP-SRS that can be set in Rel.15 NR, but also at least one of A-SRS and CORESET.

[0154] Figure 11 This diagram illustrates an example of the setting information for the spatial relationships of the SRS involved in the second embodiment. It is described using ASN.1 (Abstract Syntax Notation One) notation (this is merely an example and therefore not a complete description). Furthermore, the RRC parameter names are not limited to those shown.

[0155] In this example, the setting information for spatial relationships associated with SRS resources (e.g., “SRS-SpatialRelationInfo” in RRC IE (which can also be expressed as “SRS-SpatialRelationInfo-r16”, “SRS-SpatialRelationInfo-r17”, etc.)) differs from “SRS-SpatialRelationInfo” in Rel.15 in that “CORESET” can be set in the reference RS (parameter “referenceSignal”).

[0156] The parameter “CORESET” may also include at least one parameter representing the ID of the CORESET (“ControlResourceSetId”) and a parameter representing the downlink BWP to which the CORESET belongs (“BWP-Id”).

[0157] In addition, the UE can also be envisioned as being able to set all the resource IDs in P-SRS, SP-SPS, and A-SRS as the parameter "srs".

[0158] The SRS resource configuration information (the “SRS-Resource” parameter of the RRC) can also include one or more of the configuration information for the aforementioned spatial relationships.

[0159] When the spatial relationship setting information associated with a certain SRS resource (target SRS resource) is related to the reference SRS (including the parameter "srs"), the UE may also use the same spatial domain filter as the spatial domain filter used to transmit at least one of the reference P-SRS, reference SP-SRS, and reference A-SRS to transmit the target SRS resource.

[0160] When the spatial relationship setting information associated with the target SRS resource is related to the reference CORESET (including the parameter "CORESET"), the UE may also use the same spatial domain filter as the spatial domain filter used to receive the reference CORESET (or the PDCCH, PDCCH-DMRS, etc. associated with the reference CORESET) to transmit the target SRS resource.

[0161] Alternatively, the target SRS resource can be at least one of the following: P-SRS resource, SP-SRS resource, or A-SRS resource.

[0162] According to the second embodiment described above, a more appropriate reference signal can be set as the spatial relationship of the SRS.

[0163] <Third Implementation Method>

[0164] The third implementation relates to a MAC CE for updating the spatial relationships of P-SRS. In the existing Rel.15 NR, the spatial relationships of P-SRS can be set only through RRC signaling, but by using MAC CE, dynamic updates can be supported.

[0165] The UE can also be activated via MAC CE for reference signal resources used in the derivation of spatial relationships of SRS resources contained in a certain SRS resource set. Such activation can also be referred to as an update (or overlay) of the spatial relationship (SRI) corresponding to the SRS resource. In addition, in this disclosure, activation, deactivation, indication, selection, update, decision, etc. can be used interchangeably.

[0166] The UE can also be envisioned as applying the spatial relationship (SRI) activated by the aforementioned MAC CE for the SRS resources specified by the DCI during the transmission of a specific signal / channel (e.g., PUSCH, SRS).

[0167] Figure 12A as well as Figure 12BThis is a diagram illustrating an example of MACCE used for spatial relationship updates of P-SRS in the third embodiment.

[0168] Figure 12A This represents an example of a MAC CE that can be used in updating the spatial relationships of SRS resource levels. This MAC CE may also include information indicating whether it is active or deactivated ("A / D" field), a cell ID identifying the cell containing the SRS resource set containing the active object, a BWP ID corresponding to the UL bandwidth part (BWP) of the SRS resource set containing the active object, the P-SRS resource set ID of the active object, the active object carrier ("SUL" field), and the reference signal resource ID corresponding to the spatial relationship of the SRS resources, etc. Additionally, "R" indicates a reserved field.

[0169] The reference signal resource ID used for the i-th SRS resource within the SRS resource set corresponds to "resource ID". i (ResourceID) i Additionally, the reference signal resource ID can be at least one of the following: a non-zero power CSI-RS resource index, an SSB index, an SRS resource ID, a CORESET ID, etc. The MAC CE can also contain the serving cell ID, BWP ID, etc., corresponding to the reference signal resource ID (whether these are included can also be indicated by the "C" field).

[0170] F i It can also be used to identify "resource ID" i (Resource ID) i Which reference signal (e.g., CSI-RS, SSB, SRS (P-SRS, SP-SRS, A-SRS), CORESET) corresponds to? "Resource ID" i (Resource ID) i The correspondence between ") and which reference signal can also be based on F i With "Resource ID" i (Resource ID) i The judgment is based on a specific combination of bits of the "" itself.

[0171] exist Figure 12A In the middle, F i It can be represented using 1 bit, but is not limited to this. For example, a UE that is configured with the spatial relationship settings shown in the second embodiment can also be conceived as F. i It is 2 bits, 3 bits, or more. In this case, "Resource ID" i (Resource ID) i The size of ")" is not limited to 7 bits. For example, in Fi In the case of 2 bits, F i =0 can also indicate that the resource ID is an SSB index or an SRS resource index, F i =1 can also indicate that the resource ID is an NZP CSI-RS index or an SRS resource index, F i =2 can also represent the resource ID as CORESET ID.

[0172] Figure 12A The MAC CE can be applied to at least one (e.g., all) of the SRS resource sets used for codebook, non-codebook, beam management, and antenna switching.

[0173] Figure 12B This represents an example of a MAC CE that can be used in updating spatial relationships at the SRS resource set level. This MAC CE is similar to... Figure 12A However, the difference lies in that it includes F and Resource ID instead of F. i and resource ID i (Resource ID) i The Resource ID corresponds to the reference signal Resource ID used for all SRS resources within the SRS resource set. F can also be used to identify which reference signal the Resource ID corresponds to. i Similarly, F can also be more than 2 bits.

[0174] Figure 12B The MAC CE can be applied to at least one of the SRS resource sets used for codebook, non-codebook, beam management, and antenna switching (e.g., beam management).

[0175] In addition, if the MAC CE for spatial relationship updating of P-SRS in the third embodiment is supported, the UE can also use the MAC CE to update multiple spatial relationships covering multiple CCs, multiple BWPs, etc. at the same time.

[0176] For example, a UE can also have a list of CCs (or BWPs) set via RRC. This list can also be set with one or more. If the beam (QCL, TCI state, spatial relationship) of any CC in the CC list is updated, the UE can also update the beams of other CCs included in the CC list to the same beam.

[0177] If the spatial relationship of the P-SRS of a specific CC (cell) is updated through the aforementioned MAC CE, the UE can also update the spatial relationship of the P-SRS of other CCs included in the aforementioned list that the specific CC contains to be the same as the updated spatial relationship of the specific cell.

[0178] According to the third embodiment described above, the spatial relationship corresponding to the SRS resource can be dynamically switched and utilized.

[0179] <Other Implementation Methods>

[0180] In addition, the P-SRS in the above embodiments can also be replaced by at least one of P-SRS, SP-SRS and A-SRS.

[0181] (Wireless communication system)

[0182] The structure of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0183] Figure 13 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one implementation. The wireless communication system 1 may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized by the Third Generation Partnership Project (3GPP).

[0184] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also 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)), etc.

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

[0186] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0187] The wireless communication system 1 may also include: a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. User terminals 20 may also be located within at least one cell. The configuration and number of each cell and user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

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

[0189] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these; for example, FR1 can also be equivalent to a frequency band higher than FR2.

[0190] In addition, user terminal 20 can also communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0191] Multiple base stations 10 can also be connected via wired (e.g., fiber optic cable based on the Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

[0192] Base station 10 may also be connected to core network 30 via other base stations 10 or directly. Core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0193] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

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

[0195] Wireless access methods can also be referred to as waveforms. In addition, in wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be applied in the wireless access methods of UL and DL.

[0196] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0197] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0198] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and high-level control information can also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) can be transmitted via PBCH.

[0199] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0200] Additionally, the DCI for scheduling PDSCH can also be called DL allocation, DL DCI, etc., and the DCI for scheduling PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can also be replaced with DL data, and PUSCH can also be replaced with UL data.

[0201] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0202] A search space can also correspond to a PDCCH candidate that matches one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" used in this disclosure can be used interchangeably.

[0203] Uplink control information (UCI) can also be transmitted via PUCCH, including at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). Random access preambles used for establishing a connection with the cell can also be transmitted via PRACH.

[0204] In addition, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, various channels may be described without the word "physical".

[0205] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. As DL-RS, wireless communication system 1 can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), phase tracking reference signals (PTRS), etc.

[0206] Synchronization signals can be, for example, at least one of the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0207] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0208] (Base station)

[0209] Figure 14 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0210] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0211] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0212] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0213] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of a transmitter / receiver, RF circuitry, baseband circuitry, filters, phase shifters, measurement circuitry, transmitting / receiving circuitry, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0214] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0215] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0216] The transmitting / receiving unit 120 can also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 can also receive the aforementioned uplink channel, uplink reference signal, etc.

[0217] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

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

[0219] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing, Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0220] For baseband signals, the transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc., to the wireless frequency band, and transmit the wireless frequency band signals through the transmitting and receiving antenna 130.

[0221] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, demodulate baseband signals, etc., for signals in the wireless frequency band that are received by the transmitting and receiving antenna 130.

[0222] For the acquired baseband signal, the transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to acquire user data.

[0223] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also 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 can also be output to the control unit 110.

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

[0225] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of the transmitting and receiving unit 120, the transmitting and receiving antenna 130 and the transmission path interface 140.

[0226] Additionally, the control unit 110 can also control the size of the SRS Resource Indicator (SRI) field used to indicate the downlink control information (DCI) transmitted when more than two measurement reference signals (Sounding Reference Signal (SRS)) resources are set to the user terminal 20 for codebook-based transmission, or when more than four SRS resources are set to the user terminal 20 for non-codebook transmission.

[0227] The transmitting and receiving unit 120 can also receive transmissions (e.g., PUSCH, SRS) from the user terminal 20 based on the SRS resources represented by the SRI field.

[0228] (User terminal)

[0229] Figure 15 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0230] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0231] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0232] The control unit 210 can also control signal generation, mapping, etc. The control unit 210 can also control transmission, reception, measurement, etc., using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmission / reception unit 220.

[0233] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0234] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0235] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0236] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0237] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0238] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0239] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0240] Furthermore, whether or not to apply DFT processing can be based on the transform precoding settings. For a certain channel (e.g., PUSCH), if transform precoding is activated, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0241] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0242] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0243] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to obtain user data.

[0244] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can also 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 can also be output to the control unit 210.

[0245] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure can also be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0246] Additionally, the control unit 210 may determine the size of the SRS Resource Indicator (SRI) field used to indicate the downlink control information (DCI, e.g., DCI format 0_1 ​​for scheduling PUSCH) for transmission when more than two measurement reference signals (Sounding Reference Signals) resources are set for codebook-based transmission, or when more than four SRS resources are set for non-codebook transmission.

[0247] In addition, the SRI disclosed herein can also be replaced with spatial relation.

[0248] The transmitting and receiving unit 220 may also perform the transmission (transmission of PUSCH, SRS, etc.) based on the SRS resources represented by the SRI field.

[0249] The control unit 210 may also determine the size of the SRI field based on the number of active SRS resources or the number of set SRS resource sets.

[0250] The control unit 210 may also perform the transmission using the same spatial domain filter used for the control resource set (CORESET) based on spatial relationship information associated with the SRS resources represented by the SRI field.

[0251] The control unit 210 can also determine the spatial relationship associated with the periodic SRS resource based on the Medium Access Control (MAC) control element (MAC CE).

[0252] (Hardware structure)

[0253] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0254] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. As described above, the implementation method is not particularly limited.

[0255] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 16 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0256] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0257] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0258] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading out and writing data in the memory 1002 and the storage device 1003.

[0259] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be configured as a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least some of the control unit 110 (210), the transmit / receive unit 120 (220), etc. described above may also be implemented by the processor 1001.

[0260] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0261] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to one embodiment of this disclosure.

[0262] Storage device 1003 may also be a computer-readable recording medium, such as at least one of a flexible disc, floppy disk, optical disk (e.g., compact disc ROM, CD-ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), stripe, database, server, or other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0263] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmitting and receiving unit 120 (220) and transmitting and receiving antenna 130 (230) can also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) can also be implemented by physically or logically separating the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0264] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0265] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

[0266] Furthermore, the base station 10 and the user terminal 20 can also 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), and a field-programmable gate array (FPGA), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0267] (Variation example)

[0268] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0269] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitutes a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0270] Here, the parameter set can also refer to communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0271] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

[0272] A time slot can also contain multiple mini-time slots. Each mini-time slot can also consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (PUSCH) mapping type B.

[0273] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols used in this disclosure can be used interchangeably.

[0274] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is to say, at least one of the subframe and TTI can be a subframe in the existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0275] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0276] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0277] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0278] A TTI with a duration of 1 ms can also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0279] In addition, long TTIs (e.g., normal TTIs, subframes, etc.) can be replaced with TTIs with a duration of more than 1ms, and short TTIs (e.g., shortened TTIs, etc.) can be replaced with TTIs with a duration of less than long TTIs but more than 1ms.

[0280] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0281] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0282] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0283] Furthermore, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0284] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0285] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0286] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Furthermore, terms such as "cell" and "carrier" in this disclosure can be replaced with "BWP".

[0287] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0288] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0289] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0290] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0291] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

[0292] Input and output information, signals, etc., can be stored in a specific location (e.g., memory) or managed using management tables. Input and output information, signals, etc., can be overwritten, updated, or appended. Output information, signals, etc., can also be deleted. Input information, signals, etc., can also be sent to other devices.

[0293] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0294] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0295] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0296] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0297] Whether it is called software, firmware, middleware, microcode, hardware description language, or any other name, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, program, subprogram, software module, application, software application, software package, routine, subroutine, object, executable file, execution thread, process, function, etc.

[0298] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0299] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0300] In this disclosure, the terms "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", "beamwidth", "beam angle", "antenna", "antenna element", and "panel" are used interchangeably.

[0301] In this disclosure, the terms "Base Station (BS)", "Wireless 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", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0302] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​the base station providing communication services within that coverage area, as well as at least one of the base station subsystems.

[0303] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0304] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0305] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. This mobile body can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and the mobile station also includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0306] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be replaced with side channel.

[0307] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0308] In this disclosure, actions are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. Clearly, in a network containing one or more network nodes having a base station, various operations performed for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0309] The various methods / implementations described in this disclosure can be used individually, in combination, or switched as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, with respect to the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0310] The various methods / implementations described in this disclosure can also be applied to 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), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), systems utilizing other appropriate wireless communication methods, and next-generation systems derived from them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0311] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise specified. In other words, the word "based on" means both "based on only" and "based on at least".

[0312] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0313] The term "determining" as used in this disclosure can encompass a wide variety of actions. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database, or other data structure), and ascertaining.

[0314] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0315] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". In other words, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made.

[0316] In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0317] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connected” can also be replaced with “access.”

[0318] In this disclosure, when two elements are connected, it is possible to use more than one wire, cable, printed electrical connection, etc., and to use electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region as several non-limiting and non-inclusive examples, so that they are "connected" or "combined" with each other.

[0319] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other". Additionally, this term can also mean "A and B are different from C respectively". Terms such as "separate" and "combined" can also be interpreted in the same way as "different".

[0320] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0321] In this disclosure, for example, in cases where articles are added through translation such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0322] The invention disclosed herein has been described in detail above. However, it will be apparent to those skilled in the art that the invention is not limited to the embodiments described herein. The invention can be implemented with modifications and variations without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description in this disclosure is for illustrative purposes only and is not intended to limit the invention in any way.

Claims

1. A terminal, comprising: The receiving unit receives the Medium Access Control (MAC) element, which represents the Transmission Configuration Indication (TCI) state of the SRS (Sounding Reference Signal) resource used for measurement. The control unit determines the size of the SRS Resource Indicator (SRI) field in the downlink control information indicating codebook-based or non-codebook-based transmission when more than two SRS resources are set for codebook-based transmission or more than four SRS resources are set for non-codebook-based transmission. as well as The transmitting unit performs the indicated codebook-based transmission or non-codebook-based transmission based on the SRS resource represented by the SRI field and whose TCI state is represented by the MAC control element.

2. The terminal as described in claim 1, wherein, When the TCI status for SRS resources of a specific cell is updated via the MAC control element and the specific cell is included in a set list, the control unit updates the TCI status for SRS resources of other cells included in the list to the TCI status for SRS resources of the specific cell.

3. The terminal as described in claim 1 or 2, wherein, The control unit specifies the SRS resource set based on the SRS resource set indicator field included in the downlink control information, and specifies the SRS resources within the SRS resource set based on the SRI field.

4. The terminal as described in claim 1 or 2, wherein, In the case where more than four SRS resources are set within an SRS resource set for non-codebook transmission, the control unit determines the size of the SRI field in the downlink control information.

5. A wireless communication method, which is a wireless communication method for a terminal, comprising: The step of receiving a Medium Access Control (MAC) element, which represents the Transmission Configuration Indication (TCI) state of the Sounding Reference Signal (SRS) resource used for measurement. The steps for determining the size of the SRS Resource Indicator (SRI) field in the downlink control information indicating codebook-based or non-codebook-based transmissions when more than two SRS resources are configured, or when more than four SRS resources are configured; and Based on the SRS resource represented by the SRI field and whose TCI state is represented by the MAC control element, the instructed codebook-based transmission or non-codebook-based transmission step is performed.

6. A base station, comprising: The transmitting unit sends a Medium Access Control (MAC) element to the terminal. This MAC element indicates the Transmission Configuration Indication state (TCI) of the SRS (Sounding Reference Signal) resource used for measurement. The control unit determines the size of the SRS Resource Indicator (SRI) field in the downlink control information indicating whether the transmission is based on a codebook or not. This determination is made when more than two SRS resources are set to the terminal for codebook-based transmissions or more than four SRS resources are set to the terminal for non-codebook-based transmissions. as well as The transmitting unit performs the indicated codebook-based transmission or non-codebook-based transmission based on the SRS resource represented by the SRI field and whose TCI state is represented by the MAC control element.

7. A system comprising a terminal according to any one of claims 1 to 4 and a base station according to claim 6.

Citation Information

Patent Citations

  • Transmission method and device and computer readable storage medium

    CN110535508A