Method and device for transmitting or receiving sounding reference signal in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting data transmission rates higher than those of a 4G communication system such as LTE. The present disclosure relates to operations of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates an uplink reference signal transmission / reception method in a wireless communication system, and a device capable of performing same. The present disclosure provides the device and the method which are capable of effectively providing services in a mobile communication system. The method performed by a user equipment (UE) in the wireless communication system, according to embodiments of the present disclosure, may comprise the steps of: receiving, from a base station, first downlink control information (DCI) including first information associated with scheduling of a sounding reference signal (SRS); and transmitting the SRS to the base station on the basis of the first DCI.

Description

Method and apparatus for transmitting or receiving a sounding reference signal in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for receiving / transmitting a sounding reference signal by setting / receiving upper-layer parameters for an uplink reference signal and transmitting / receiving scheduling information, and to an apparatus capable of performing the same.

[0002] Looking back at the evolution of wireless communication through successive generations, technologies have been developed primarily for human-oriented services, such as voice, multimedia, and data. Following the commercialization of 5G (5th Generation) communication systems, connected devices, which have been increasing explosively, are expected to be connected to communication networks. Examples of networked objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve into various form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. In the 6G (6th Generation) era, efforts are underway to develop improved 6G communication systems to connect hundreds of billions of devices and objects to provide diverse services. For this reason, 6G communication systems are being referred to as "beyond 5G" systems.

[0003] In the 6G communication system predicted to be realized around 2030, the maximum transmission speed is tera (i.e., 1,000 gigabit) bps (bit per second), and the wireless latency is 100 microseconds (μsec). In other words, compared to the 5G communication system, the transmission speed in the 6G communication system is 50 times faster, and the wireless latency is reduced to one-tenth.

[0004] To achieve such high data transmission speeds and ultra-low latency, 6G communication systems are being considered for implementation in the terahertz (THz) band (e.g., the 95 gigahertz (GHz) to 3 terahertz (3THz) band). Due to more severe path loss and atmospheric absorption phenomena compared to the millimeter wave (mmWave) band introduced in 5G, the importance of technologies capable of guaranteeing signal reach, or coverage, is expected to increase in the terahertz band. As key technologies to ensure coverage, new waveforms, beamforming, and multi-antenna transmission technologies such as massive Multiple-Input and Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, which are superior in terms of coverage compared to RF (Radio Frequency) devices, antennas, and OFDM (Orthogonal Frequency Division Multiplexing), must be developed. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) are being discussed to improve the coverage of terahertz band signals.

[0005] In addition, to improve frequency efficiency and system network, development is underway in 6G communication systems for full duplex technology, in which uplink and downlink simultaneously utilize the same frequency resources at the same time; network technology that integrates satellites and HAPS (High-Altitude Platform Stations); network structure innovation technology that supports mobile base stations and enables network operation optimization and automation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; AI-based communication technology that utilizes AI (Artificial Intelligence) from the design stage and internalizes end-to-end AI support functions to realize system optimization; and next-generation distributed computing technology that realizes services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high performance communication and computing resources (Mobile Edge Computing (MEC), cloud, etc.). In addition, attempts are continuing to further strengthen connectivity between devices, further optimize networks, promote the softwareization of network entities, and increase the openness of wireless communication through the design of new protocols to be used in 6G communication systems, the implementation of hardware-based security environments, the development of mechanisms for the safe utilization of data, and the development of technologies regarding privacy maintenance methods.

[0006] Due to the research and development of such 6G communication systems, it is expected that a new dimension of hyper-connected experience will become possible through the hyper-connectivity of 6G communication systems, which encompasses not only connections between objects but also connections between people and objects. Specifically, it is projected that 6G communication systems will enable the provision of services such as truly immersive eXtended Reality (XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response, which are provided through 6G communication systems with enhanced security and reliability, will be applied in various fields including industry, healthcare, automotive, and home appliances.

[0007] Embodiments of the present disclosure may have one objective of providing an apparatus and method capable of effectively providing services in a wireless communication system.

[0008] According to embodiments of the present disclosure, a method performed by a user equipment (UE) of a wireless communication system may include the steps of receiving first downlink control information (DCI) from a base station, the DCI including first information associated with the scheduling of a sounding reference signal (SRS), and transmitting the SRS to the base station based on the first DCI.

[0009] Embodiments of the present disclosure provide an apparatus and method capable of effectively providing services in a wireless communication system.

[0010] FIG. 1 is a diagram illustrating a comb offset and cyclic shift allocation method during SRS transmission according to an embodiment of the present disclosure.

[0011] FIG. 2 illustrates an example in which the SRS is not transmitted and is transmitted to another slot depending on the UL resources available to the terminal according to an embodiment of the present disclosure and the settings of the triggered SRS resource set.

[0012] FIG. 3 shows an example of a DCI format for scheduling a flexible SRS using a two-stage DCI according to an embodiment of the present disclosure.

[0013] FIG. 4 shows an example of a DCI format for scheduling a flexible SRS using a flag bit according to embodiments of the present disclosure.

[0014] FIG. 5 is a drawing illustrating the structure of a terminal in a wireless communication system according to embodiments of the present disclosure.

[0015] FIG. 6 is a drawing illustrating the structure of a base station in a wireless communication system according to embodiments of the present disclosure.

[0016] FIG. 7 is a drawing illustrating the structure of a terminal in a wireless communication system according to embodiments of the present disclosure.

[0017] FIG. 8 is a drawing illustrating the structure of a base station in a wireless communication system according to embodiments of the present disclosure.

[0018] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0019] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0020] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0021] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0022] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0023] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0024] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0025] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0026] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 3GPP’s HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.

[0027] As a representative example of a broadband wireless communication system, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, or base station (BS)), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

[0028] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0029] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

[0030] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0031] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and at the same time, design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.

[0032] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

[0033] Hereinafter, a / b may be understood as at least one of a or b.

[0034] [Uplink: RS]

[0035] [Regarding SRS]

[0036] A method for estimating an uplink channel using the transmission of a terminal's Sounding Reference Signal (SRS) is described. To transmit configuration information for SRS transmission to the terminal, the base station may set at least one SRS configuration for each uplink BWP, and may also set at least one SRS resource set for each SRS configuration. For example, the base station and the terminal may exchange upper-level signaling information as follows to transmit information regarding the SRS resource set.

[0037] - srs-ResourceSetId: SRS resource set index

[0038] - srs-ResourceIdList: A set of SRS resource indices referenced by the SRS resource set

[0039] - resourceType: This is the time-axis transmission setting for the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information may be provided depending on the usage of the SRS resource set. If set to 'aperiodic', a non-periodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided depending on the usage of the SRS resource set.

[0040] - usage: A setting regarding the usage of the SRS resource referenced in the SRS resource set, which can be set to one of 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'.

[0041] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for controlling the transmit power of the SRS resource referenced in the SRS resource set.

[0042] The terminal can understand that the SRS resources included in the set of SRS resource indices referenced in the SRS resource set follow the information set in the SRS resource set.

[0043] Additionally, the base station and the terminal may transmit and receive upper-layer signaling information to convey individual configuration information for the SRS resource. For example, the individual configuration information for the SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, which may include information regarding frequency hopping within or between slots of the SRS resource. Furthermore, the individual configuration information for the SRS resource may include the time-axis transmission setting of the SRS resource, which may be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. This may be restricted to having the same time-axis transmission setting as the SRS resource set containing the SRS resource. If the time-axis transmission setting of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) may additionally be included in the time-axis transmission setting.

[0044] A base station may enable, deactivate, or trigger SRS transmission to a terminal via upper-layer signaling, including RRC signaling or MAC CE signaling, or L1 signaling (e.g., DCI). For example, a base station may enable or deactivate periodic SRS transmission to a terminal via upper-layer signaling. A base station may instruct a terminal to activate an SRS resource set with resourceType set to periodic via upper-layer signaling, and the terminal may transmit an SRS resource referenced in the activated SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. The terminal can transmit an SRS resource within an active uplink BWP for a periodic SRS resource activated through upper layer signaling.

[0045] For example, a base station can enable or disable semi-persistent SRS transmission to a terminal via upper-layer signaling. The base station can instruct the terminal to enable an SRS resource set via MAC CE signaling, and the terminal can transmit an SRS resource referenced in the enabled SRS resource set. The SRS resource set enabled via MAC CE signaling may be limited to an SRS resource set where resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is configured in the SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information regarding the spatial relation info transmitted via MAC CE signaling that enables semi-persistent SRS transmission without following it. The terminal can transmit the SRS resource within the uplink BWP enabled for the semi-persistent SRS resource activated via upper layer signaling.

[0046] For example, a base station can trigger an aperiodic SRS transmission to a terminal via the DCI. The base station can specify one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI. The terminal can understand that among the configuration information of the SRS resource set, an SRS resource set containing the aperiodic SRS resource trigger specified via the DCI from the list of aperiodic SRS resource triggers has been triggered. The terminal can transmit the SRS resource referenced in the triggered SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource. Additionally, the slot mapping of the transmitted SRS resource can be determined through the slot offset between the PDCCH containing the DCI and the SRS resource, which can refer to the value(s) included in the set of slot offsets set in the SRS resource set. Specifically, the slot offset between the PDCCH containing the DCI and the SRS resource may be the value specified in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set configured in the SRS resource set. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to the spatial relation info configured in the SRS resource, or may refer to the associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is enabled for a non-periodic SRS resource triggered via the DCI.

[0047] When a base station triggers aperiodic SRS transmission to a terminal via DCI, a minimum time interval may be required between the PDCCH containing the DCI triggering the aperiodic SRS transmission and the transmitted SRS so that the terminal can apply configuration information for the SRS resource and transmit the SRS. The time interval for the terminal's SRS transmission can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI triggering the aperiodic SRS transmission and the first symbol mapped to the first transmitted SRS resource(s). The minimum time interval can be determined by referencing the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. Additionally, the minimum time interval may have different values ​​depending on the usage of the SRS resource set containing the transmitted SRS resource. For example, the minimum time interval can be determined by N2 symbols defined by considering the terminal's processing capability based on the terminal's capability, referencing the terminal's PUSCH preparation procedure time. Additionally, considering the usage of the SRS resource set including the transmitted SRS resource, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval can be set to N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be set to N2+14 symbols.The terminal transmits an aperiodic SRS when the time interval for the aperiodic SRS transmission is greater than or equal to the minimum time interval, and can ignore the DCI that triggers the aperiodic SRS when the time interval for the aperiodic SRS transmission is less than the minimum time interval.

[0048]

[0049] The spatialRelationInfo setting information in [Table 1] above refers to a single reference signal and applies the beam information of that reference signal to the beam used for the corresponding SRS transmission. For example, the spatialRelationInfo setting may include information such as that shown in [Table 2] below.

[0050]

[0051] Referring to the spatialRelationInfo setting above, the index of the reference signal to be referenced in order to use the beam information of a specific reference signal—namely, the SS / PBCH block index, CSI-RS index, or SRS index—can be set. The upper signaling referenceSignal is configuration information indicating which reference signal's beam information to reference for the corresponding SRS transmission, and ssb-Index represents the SS / PBCH block index, csi-RS-Index represents the CSI-RS index, and srs represents the SRS index, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the receiving beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the receiving beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmission beam used during the transmission of the SRS corresponding to srs as the transmission beam for the transmission of the SRS.

[0052] [SRS: Antenna switching]

[0053] The following describes the SRS for antenna switching.

[0054] The SRS transmitted from the terminal can be used by the base station to acquire Channel State Information (DL CSI) information (e.g., DL CSI acquisition). As a specific example, in a single-cell or multi-cell (e.g., carrier aggregation (CA)) situation based on Time Division Duplex (TDD), the Base Station (BS) can measure the SRS transmitted from the UE after scheduling the transmission of the SRS to the User Equipment (UE). In this case, the base station can assume reciprocity between the DL (downlink) and UL (uplink) channels and consider the uplink channel information estimated based on the SRS transmitted from the terminal as downlink channel information, and use this to perform scheduling of downlink signals / channels for the terminal. At this time, the terminal can receive a setting from the base station for the use of the SRS for acquiring downlink channel information as antenna switching.

[0055] For example, according to the standard (e.g., 3gpp TS38.214), the use of the SRS can be configured for the base station and / or terminal using a higher layer parameter (e.g., the usage of the RRC parameter SRS-ResourceSet). Here, the use of the SRS can be configured for beam management, codebook transmission, non-codebook transmission, antenna switching, etc.

[0056] If the terminal receives the parameter 'usage' within the SRS-ResourceSet, which is an upper layer signaling, from the base station as 'antennaSwitching', the terminal may receive at least one upper layer signaling setting from the base station according to the reported terminal capability. In this case, the terminal may report 'supportedSRS-TxPortSwitch' as ​​the terminal capability, and the value may be as follows. In the following, 'mTnR' may mean the terminal capability to support transmission through m antennas and reception through n antennas.

[0057] -'t1r2': A terminal capability report value indicating that the terminal is capable of 1T2R operation

[0058] -'t1r1-t1r2': A terminal capability report value indicating that the terminal is capable of 1T1R or 1T2R operation

[0059] -'t2r4': A terminal capability report value indicating that the terminal is capable of 2T4R operation.

[0060] - 't1r4': A terminal capability report value indicating that the terminal is capable of 1T4R operation

[0061] - 't1r6': A terminal capability report value indicating that the terminal is capable of 1T6R operation

[0062] - 't1r8': A terminal capability report value indicating that the terminal is capable of 1T8R operation

[0063] - 't2r6': A terminal capability report value indicating that the terminal is capable of 2T6R operation

[0064] - 't2r8': A terminal capability report value indicating that the terminal is capable of 2T8R operation

[0065] - 't4r8': A terminal capability report value indicating that the terminal is capable of 4T8R operation.

[0066] - 't1r1-t1r2-t1r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 1T2R, or 1T4R operation.

[0067] - 't1r4-t2r4': A terminal capability report value indicating that the terminal is capable of 1T4R or 2T4R operation.

[0068] -'t1r1-t1r2-t2r2-t2r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 1T2R, 2T2R, or 2T4R operations.

[0069] -'t1r1-t1r2-t2r2-t1r4-t2r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 1T2R, 2T2R, 1T4R, or 2T4R operations.

[0070] -'t1r1': A terminal capability report value indicating that the terminal is capable of 1T1R operation

[0071] -'t2r2': A terminal capability report value indicating that the terminal is capable of 2T2R operation.

[0072] -'t1r1-t2r2': A terminal capability report value indicating that the terminal is capable of 1T1R or 2T2R operation.

[0073] -'t4r4': A terminal capability report value indicating that the terminal is capable of 4T4R operation.

[0074] -'t1r1-t2r2-t4r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 2T2R, or 4T4R operation.

[0075] [SRS: How to Set Comb Offset / Cycle Shift]

[0076] This describes the method for setting comb offset and cyclic shift when transmitting the Sounding Reference Signal (SRS) of a terminal.

[0077] The terminal can receive configuration for an SRS resource from the base station via an upper layer signaling, such as SRS-Resource or SRS-PosResource, and may be composed of the following items.

[0078] - For the case of SRS-Resource, the terminal can be configured to set the number of antenna ports for each SRS resource, and the value is It can be defined as and can be configured through the upper-layer signaling nrofSRS-Ports or nrofSRS-Ports-n8. If the upper-layer signaling 'usage' within SRS-ResourceSet is set to a value other than 'nonCodebook' can mean the number of the i-th antenna port, and i is 0 to It can be an integer. If the usage, which is the upper-layer signaling within the SRS-ResourceSet, is set to nonCodebook, each SRS resource is Can be configured with antenna ports, and the antenna port of the i+1th SRS resource within the SRS-ResourceSet It can be defined as. In the case of SRS-PosResource It can be defined as.

[0079] - The terminal can receive a setting for the number of consecutive symbols transmitted via SRS from the base station through nrofSymbols within the resourceMapping, which is an upper layer signaling, and the value is It can be defined as.

[0080] - The terminal can receive a setting for the position of the start symbol for which the SRS is transmitted within a slot from the base station through the startPosition within the resourceMapping, which is a higher-layer signaling, and the value is It can be defined as. In this case, can represent the number of symbols in the slot, and the value can be 14 for a normal cyclic prefix and 12 for an extended cyclic prefix. can refer to an offset value that counts the number of symbols in reverse, starting from the symbol located at the very end of the slot. At this time It can satisfy.

[0081] - can mean the starting position of the frequency resource where the SRS is transmitted.

[0082] The SRS sequence that can be generated through the SRS resource defined based on the above information can be defined as [Equation 1].

[0083] [Mathematical Formula 1]

[0084]

[0085]

[0086]

[0087] At this time, represents the length of the SRS sequence. is determined through [Table 4] below and can be determined through the upper-layer signaling, b-SRS and c-SRS. In this case, when b-SRS is configured, within [Table 4] below You can determine the value, You can determine the value of the subscript b, and if b-SRS is not set It may be. c-SRS is within [Table 4] below. You can determine the value. This can be determined through the upper-layer signaling FreqScalingFactor, and if the parameter is not set It may be possible. When FreqScalingFactor, an upper layer signaling, is set, the terminal can expect the length of the SRS sequence to be a multiple of 6.

[0088] It can be defined as, It can determine the size of the comb. In this case, the size of the comb may refer to the interval between REs where the SRS is transmitted on the frequency resource, and for example, the size of the comb In this case, it may mean that the interval between REs transmitted by SRS is 2 REs. The terminal can receive the size of the Comb through transmissionComb, which is a higher layer signaling. can mean the symbol index within the symbols being transmitted by the SRS resource. The terminal The maximum cyclic shift value depending on the value It can be determined as shown in [Table 3] below.

[0089]

[0090] represents the cyclic shift of the i-th antenna port and the basic sequence It can be defined as follows through.

[0091]

[0092] At this time, can refer to the length of the SRS sequence. Different for a single base sequence and Multiple SRS sequences can be generated depending on the value.

[0093] Multiple basic sequences can be divided into groups, and the group index is It can be defined as, can refer to the index of the base sequence within the group. If In this case, each group may include one basic sequence, and at this time It could be. If In this case, each group may include two basic sequences, and at this time It could be. The definition of is the length of the sequence It may vary depending on the value of.

[0094] If the length of the basic sequence is 36 or more, i.e. When, the basic sequence can be defined as follows. In this case, Is It can be the largest prime number smaller than

[0095]

[0096]

[0097]

[0098]

[0099] When the length of the basic sequence is 6, 12, 18, or 24, that is When, the basic sequence It can be defined as follows.

[0100]

[0101] At this time, The value of can be defined through the following [Table 5] to [Table 8].

[0102] When the length of the basic sequence is 30, that is When, the basic sequence It can be defined as follows.

[0103]

[0104] If the terminal is configured with the upper layer signaling nrofSRS-Ports-n8 as ports8tdm, can be defined as follows, and in the case otherwise It can be defined as.

[0105] -if Igo In the case of, It can be defined as.

[0106] -if Igo In the case of, It can be defined as.

[0107] -When neither of the above two cases is true, It can be defined as.

[0108] antenna port Meaning the cyclic shift corresponding to It can be defined as follows.

[0109]

[0110] At this time, It can be defined as follows.

[0111] - Igo When, It can be defined as.

[0112] - Igo This or, Igo When,

[0113] It can be defined as.

[0114] -When neither of the above two cases is true, It can be defined as.

[0115] At this time, is a parameter that determines the cyclic shift value and can be set through cyclicShift-n2, cyclicShift-n4, or cyclicShift-n8 within the transmissionComb, which is the upper layer signaling, and This can be determined through the above [Table 3].

[0116] and It can be determined as follows.

[0117] - If the upper layer signaling nrofSRS-Ports-n8 is set to ports8tdm, It can be defined as, In the case of In the case of Defined as, In the case of It can be defined as. That is, when a terminal transmits via TDM for an SRS resource composed of 8 antenna ports, the antenna port to be transmitted in the first symbol is For each of 1000, 1001, 1004, and 1005 Defined as 1000, 1001, 1002, and 1003, and the antenna port to be transmitted in the second symbol For each of 1002, 1003, 1006, and 1007 By defining them as 1000, 1001, 1002, and 1003, when allocating resources for the four different antenna ports transmitted in each symbol, the resource allocation method for the SRS resource composed of four antenna ports can be applied as is.

[0118] - Except for the above cases, that is, cases where the upper layer signaling nrofSRS-Ports-n8 is not set to ports8tdm, and It can be defined as.

[0119] It refers to the starting position in the frequency dimension of the SRS corresponding to the i-th antenna port. It can be defined as follows.

[0120]

[0121] At this time, It can be defined as follows.

[0122]

[0123] At this time, It can be defined as follows.

[0124] - In the case of, It can be defined as.

[0125] - In the case of, It can be defined as.

[0126] - In the case of, It can be defined as.

[0127] - In the case of, It can be defined as.

[0128] - In the case of, It can be defined as.

[0129] - In the case of, It can be defined as.

[0130] - In the case of, It can be defined as.

[0131] - For the remaining cases excluding the above cases, It can be defined as.

[0132] At this time, It can be defined as follows.

[0133]

[0134] At this time, It can be defined as follows.

[0135]

[0136] can be set to StartRBIndex, which is the upper layer signaling, and if not set It can be defined as.

[0137] For cases where the upper layer signaling EnableStartRBHopping is configured, the following and It can be determined based on the values ​​through [Table 9], and if not, It can be defined as.

[0138]

[0139] If SRS transmission is performed based on SRS-PosResource, the above It can be defined based on the following [Table 10], and if not (if SRS transmission is performed based on SRS-Resource), the above It can be defined as.

[0140] The offset value in the frequency dimension is a value that determines the position at which the SRS is transmitted in the frequency dimension from the reference position, and can be set via freqDomainShift, a higher-layer signaling. Represents the Comb offset value. It can be set via combOffset-n2, combOffset-n4, or combOffset-n8 within transmissionComb, which is the upper layer signaling.

[0141] As an upper-layer signaling related to frequency hopping of the SRS, a b-hop within freqHoping can be set, and the above It can be defined as.

[0142] is a value representing the index of the frequency position, and can be defined as follows.

[0143] -if In this case, frequency hopping of the SRS is not supported, and indicates the index of the frequency position is all It can have a constant value during the symbol and can be defined as follows.

[0144]

[0145] At this time, is a value set through the upper layer signaling freqDomainPosition, and if not set, the value may be 0.

[0146] -if In this case, frequency hopping of the SRS is supported, and It can be defined as follows.

[0147] if In the case of, It can be defined as follows.

[0148] If not, It can be defined as follows.

[0149] At this time, is if If is an even number, It can be defined as, and if If g is odd, It can be defined as. silver It can be defined as 1 regardless of the value.

[0150] can be defined as a parameter that counts the number of SRS transmissions. If the terminal transmits a non-periodic SRS resource, within a specific slot Within the symbol It can be defined as follows. In this case, This applies when the upper layer signaling nrofSRS-Ports-n8 is configured as ports8tdm It can be defined as, and in cases where it is not It can be defined as. In this case, can be a value set as repetitionFactor, which is the upper layer signaling, and if not set It can be defined as.

[0151] If the terminal transmits periodic or semi-continuous SRS resources, In slots satisfying, It can be defined as follows.

[0152]

[0153] At this time, and can mean the period and slot offset of a periodic or semi-continuous SRS, respectively.

[0154] FIG. 1 illustrates a comb offset and cyclic shift allocation method during SRS transmission according to embodiments of the present disclosure.

[0155] In the first example (100), for the terminal to an SRS resource consisting of 4 antenna ports (comb offset value), (cyclic shift value), (comb size value) and It is assumed that a situation has been set (maximum cyclic shift value). In this case, the terminal As cyclic shift values ​​assigned to 1000 and 1002, respectively and It can be defined as, comb offset values ​​for both 1000 and 1002 It can be defined as (105). Also, the terminal As cyclic shift values ​​assigned to 1001 and 1003, respectively and It can be defined as, comb offset values ​​for both 1001 and 1003 It can be defined as (110). That is, the terminal assigns two antenna ports out of four to the same comb offset, and to separate the two antenna ports within the same comb offset, the interval between the cyclic shift values ​​corresponding to the two antenna ports is maximized, so that the interval is It can be decided as.

[0156] In the second example (130), for an SRS resource consisting of 4 antenna ports, the terminal (comb offset value), (cyclic shift value), (comb size value) and It can be assumed that a situation has been set (maximum cyclic shift value). In this case, the terminal As cyclic shift values ​​assigned to 1000, 1001, 1002, and 1003, respectively It can be defined as, comb offset values ​​for 1000, 1001, 1002, and 1003 It can be defined as (135). That is, the terminal assigns all four antenna ports to the same comb offset, and in order to separate the four antenna ports within the same comb offset, the interval between the cyclic shift values ​​corresponding to the four antenna ports is maximized, so that the interval is It can be decided as.

[0157] In the third example (160), for an SRS resource consisting of four antenna ports, the terminal (comb offset value), (cyclic shift value), (comb size value) and It can be assumed that a situation has been set (maximum cyclic shift value). In this case, the terminal As cyclic shift values ​​assigned to 1000 and 1002, respectively and It can be defined as, comb offset values ​​for both 1000 and 1002 It can be defined as (165). Also, the terminal As cyclic shift values ​​assigned to 1001 and 1003, respectively and It can be defined as, comb offset values ​​for both 1001 and 1003 It can be defined as (170). That is, the terminal assigns two antenna ports out of four to the same comb offset, and to separate the two antenna ports within the same comb offset, the interval between the cyclic shift values ​​corresponding to the two antenna ports is maximized, so that the interval is It can be decided as.

[0158]

[0159]

[0160]

[0161]

[0162]

[0163]

[0164]

[0165]

[0166] [UE capability]

[0167] [Regarding Terminal Capability Reporting]

[0168] In LTE and NR, a terminal can perform a procedure to report the capabilities supported by the terminal to the base station while connected to the serving base station. In the description below, this is referred to as a UE capability report.

[0169] A base station may transmit a UE capability enquiry message requesting capability reporting to a connected terminal. The message may include a request for terminal capability specific to the base station's RAT (radio access technology) type. The request for each RAT type may include information such as supported frequency band combinations. Furthermore, in the case of the UE capability enquiry message, multiple UE capabilities for each RAT type may be requested through a single RRC message container transmitted by the base station, or the base station may transmit the UE capability enquiry message, which includes the request for each RAT type, to the terminal multiple times. That is, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Additionally, while the UE capability enquiry message is generally transmitted initially after the terminal connects with the base station, the base station may request it under any conditions whenever necessary.

[0170] In the above step, the terminal that receives a request for a UE capability report from the base station configures the terminal capability according to the RAT type and band information requested from the base station. A method for the terminal to configure the UE capability in an NR system is described below.

[0171] 1. If the terminal receives a list of LTE and / or NR bands from the base station via a UE capability request, the terminal configures a band combination (BC) for EN-DC and NR stand alone (SA). That is, a candidate list of BCs for EN-DC and NR SA can be configured based on the bands requested from the base station via FreqBandList. Additionally, the bands may have priority in the order listed in FreqBandList.

[0172] 2. If the base station requests a UE capability report by setting the "eutra-nr-only" flag or the "eutra" flag, the terminal may remove NR SA BCs from the list of candidate BCs configured above. This operation may occur only when the LTE base station (eNB) requests the "eutra" capability.

[0173] 3. Subsequently, the terminal may remove fallback BCs from the candidate list of BCs configured in Step 1. Here, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from any BC, and this step may be omitted because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. This step applies to MR-DC as well, that is, LTE bands. The BCs remaining after this step may include the final "candidate BC list."

[0174] 4. The terminal selects the BCs to be reported by selecting BCs that match the requested RAT type from the final "Candidate BC List." In this step, the terminal constructs the supportedBandCombinationList in a defined order. That is, the terminal can construct the BCs and UE capabilities to be reported according to the pre-configured rat-Type order (nr -> eutra-nr -> eutra). Additionally, it constructs a featureSetCombination for the constructed supportedBandCombinationList and can construct a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0175] 5. Additionally, if the requested rat Type is eutra-nr and has an influence, featureSetCombinations is included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set is included only in UE-NR-Capabilities.

[0176] After terminal capability is configured, the terminal can transmit a terminal capability information message containing the terminal capability to the base station. Based on the terminal capability received from the terminal, the base station can subsequently perform appropriate scheduling and transmission / reception management for the terminal.

[0177] The method and apparatus according to the embodiments of the present disclosure are applicable to FDD and TDD systems. Hereinafter, upper signaling (or upper layer signaling) in the present disclosure is a signal transmission method transmitted from a base station to a terminal using a downlink data channel of the physical layer, or from a terminal to a base station using an uplink data channel of the physical layer, and may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC CE).

[0178] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that assign the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that assign the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that assign the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. Hereinafter, for convenience of explanation, the operation of the terminal receiving a PDSCH to which cooperative communication is applied based on conditions similar to those above may be referred to as the NC-JT case.

[0179] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0180] Although described in this disclosure through a number of embodiments, one or more embodiments may be applied simultaneously or in combination.

[0181] In this disclosure, for convenience of description, cells, transmission points, panels, beams, and / or transmission directions that can be distinguished through upper-layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be uniformly described as TRP (transmission reception point), beam, or TCI state. Accordingly, in actual application, TRP, beam, or TCI state may be appropriately replaced with one of the aforementioned terms.

[0182] In this disclosure, a detailed description of related functions or configurations may be omitted if it is determined that such description would unnecessarily obscure the essence of the disclosure. Furthermore, the terms described below are defined in consideration of their functions within this disclosure and may vary depending on the intentions or practices of the user or operator.

[0183] In the present disclosure, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of the following signalings.

[0184] -MIB (Master Information Block)

[0185] -SIB (System Information Block) or SIB

[0186] -RRC (Radio Resource Control)

[0187] -MAC (Medium Access Control) CE (Control Element)

[0188] - In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling.

[0189] -PDCCH (Physical Downlink Control Channel)

[0190] -DCI (Downlink Control Information)

[0191] -Terminal-specific (UE-specific) DCI

[0192] - Group common DCI

[0193] - Common DCI

[0194] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)

[0195] - Non-scheduling DCI (e.g., DCI not intended for scheduling downlink or uplink data)

[0196] -PUCCH (Physical Uplink Control Channel)

[0197] -UCI (Uplink Control Information)

[0198] In the present disclosure, the term "slot" is a general term that may refer to a specific time unit corresponding to a Transmit Time Interval (TTI), and specifically, it may refer to a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

[0199] Hereinafter, a flexible SRS scheduling method and a transmission method according to embodiments of the present disclosure will be described. Specifically, the first embodiment specifically describes an SRS scheduling method and an SRS transmission method for flexibly transmitting SRS by considering currently available UL (uplink) resources and ports requiring transmission.

[0200] In NR, radio resource control (RRC) parameters for supporting SRS can be set for each UL BWP (bandwidth part) specifically for UE. When a base station schedules SRS to a terminal (a trigger may be used instead of the schedule), the base station may schedule specific SRS resource set(s) to the terminal, and the terminal may transmit SRS using the time and frequency resources of all SRS resources included in the SRS resource set scheduled by the base station.

[0201] For RRC parameters used to define an SRS resource set, parameters for the following information can be set:

[0202] - A parameter may be set to indicate the ID of the SRS resource set to identify the SRS resource set triggered by the base station (SRS-ResourceSetId).

[0203] - If an SRS resource set is triggered, a parameter for indicating one or more SRS resources that the terminal must transmit can be set as a sequence of parameter(s) (sequence of SRS-ResourceId).

[0204] - A parameter is set to indicate whether the corresponding SRS resource set is a parameter for supporting aperiodic SRS triggered via DCI, a parameter for supporting semi-persistent SRS that periodically transmits the corresponding SRS resource set from the time the terminal receives an activation instruction until it receives an deactivation instruction, or a parameter for supporting periodic SRS that periodically transmits the corresponding SRS resource set after the terminal receives an RRC setting (resourceType). At this time, for the SRS resource set for supporting aperiodic SRS triggered by DCI, a parameter called aperiodicSRS-ResourceTrigger, which can be set to one of values ​​from 1 to 3, may be set. The parameter in question may be identical to any value indicated by an SRS request field within a DCI capable of triggering aperiodic SRS. If a terminal receives a DCI from a base station containing an SRS request field set to a value identical to the parameter set in the aperiodicSRSResourceTrigger within the SRS resource set for aperiodic SRS, the terminal understands that the SRS resource set has been triggered and may transmit all SRS resources configured in the SRS resource set. Additionally, a slotOffset may be configured within the SRS resource set to determine the slot in which the terminal will transmit SRS based on the slot in which the DCI triggering the SRS was received.

[0205] - You can set RRC parameters to instruct the terminal on what use the corresponding SRS resource set is transmitted to support (usage).

[0206] - If the corresponding SRS resource set is configured to support a specific use case (for example, an SRS resource set configured such that the aforementioned usage is set to nonCodebook to support an SRS for non-codebook-based PUSCH), the terminal may set an identifier for a reference signal (e.g., CSI-RS) to be referenced to calculate a precoder for transmitting an SRS resource of the corresponding SRS resource set (NZP-CSI-RS-ResourceId).

[0207] - The terminal can set parameters to reference to calculate the transmission power for transmitting the corresponding SRS resource set or to determine the spatial domain filter (or UL beam) (alpha, p0, pathlosResourceRS, srs-PowerControlAdjustmentStates, followUnifiedTCI-StateSRS, applyIndicatedTCI-State, etc.)

[0208] That is, in order to schedule a specific SRS resource set considering the aforementioned uses, resources, transmission power, UL beam, etc., the base station may select an SRS resource set configured with specific RRC parameters and trigger it to the terminal. The terminal may determine the slots where all SRS resources within the SRS resource set can be transmitted using the following rules through the following method for the SRS resource set triggered by the base station:

[0209] - If aperiodic SRS is triggered: The terminal may transmit all SRS resources within the triggered SRS resource set from slot n, which received the DCI triggering the SRS resource set, to slot n+k, which is k slots after slot n, indicated by the slotOffset set in the triggered SRS resource set (limited to cases where the SCS of the frequency resource receiving the scheduling DCI and the SCS of the frequency resource transmitting the SRS are identical. If the SCS of the frequency resource receiving the DCI and the SCS of the frequency resource transmitting the SRS are not identical Corrected by, from this, k slots later Transmit all SRS resources within the SRS resource set triggered by a slot). If the terminal and base station support a function to transmit the triggered SRS resource set by additionally counting available resources based on available slots, then n+k slots (or Based on the slot, all SRS resources within the triggered SRS resource set can be transmitted to the (t+1)th available slot according to the time indicated by the SRS offset indicator field, which is included in the same DCI as the DCI that triggered the SRS resource set among the available slot candidate values ​​set as RRC parameters for the SRS resource set. In this case, the available slot refers to a slot containing a UL symbol or a flexible symbol that can transmit all SRS resources within the triggered SRS resource set while satisfying the minimum timing requirements between all SRS resources within the SRS resource set and the PDCCH that triggered it.

[0210] - If semi-persistent SRS is activated: the SCS setting of the frequency resource that transmitted the PUCCH from slot n, which is the time when the terminal transmitted the PUCCH containing a HARQ-ACK for the activation command to activate semi-persistent SRS Based on It can be identified that transmission for the corresponding SRS resource set begins starting from the first slot after the slot. At this time, the terminal can identify the slot-level repetition period and the slot-level offset at which the SRS is transmitted within the repetition period, based on the periodicityAndOffset-sp set on the SRS resource within the SRS resource set, and transmits the SRS resource based on this. The terminal does not expect a different slot-level repetition period to be set on the SRS resource configured in the same SRS resource set.

[0211] - If periodic SRS is configured: The terminal identifies the slot-level repetition period and the slot-level offset at which the SRS is transmitted within the repetition period, based on the periodicityAndOffset-p configured in the SRS resource set within the RRC parameter, and transmits the SRS resource. The terminal does not expect a different slot-level repetition period to be configured for the SRS resource configured in the same SRS resource set.

[0212] In the case of an aperiodic SRS resource set triggered by a base station, the terminal must transmit all SRS resources within the aperiodic SRS resource set into a single slot; in the case of a semi-persistent SRS resource set or a periodic SRS resource set, it may transmit SRS resources according to the period set in periodicityAndOffset-sp or periodicityAndOffset-s and a defined slot offset. When aperiodic SRS is triggered, if the terminal can count the slots where SRS can be transmitted based on available slots, the terminal may delay transmitting SRS until it finds a resource in a time domain where all SRS resources can be transmitted. Additionally, in such an NR framework, even if UL resources remain after transmitting another UL channel (such as PUCH, PUSCH, or another SRS), if all SRS resources within the SRS resource set cannot be transmitted through those resources, the terminal cannot transmit SRS using the remaining UL resources and must use other UL resources. Therefore, inefficiency in resource utilization may occur depending on the configuration of the SRS resource set and the status of currently available UL resources.

[0213] FIG. 2 illustrates an example in which the SRS is not transmitted and is transmitted to another slot depending on the UL resources available to the terminal according to an embodiment of the present disclosure and the settings of the triggered SRS resource set.

[0214] In a TDD system, it can be assumed that the slot settings in the time domain are set such that the ratio between the downlink slot, the Flexible slot, and the uplink slot is 3:1:1 (200). The terminal receives a DCI (201) that triggers an SRS from the base station and identifies the slot to transmit the corresponding SRS resource set (202). If the slot determined by the slotOffset set in the SRS resource set (202) scheduled by the DCI (201) overlaps in the time domain with another uplink channel (e.g., PUCCH) (203) that takes precedence over SRS transmission, different operations may be supported depending on the terminal's capabilities. If the terminal does not support an operation to count available slot-based SRS transmission slots, the terminal may not transmit the symbols of the SRS (202) that overlap with the other uplink channel (203). That is, if the terminal does not support an available slot-based SRS transmission technique that allows the terminal to transmit an SRS by counting time resources indicated by the SRS triggering DCI based on the slot offset set by RRC in the triggered SRS resource set, the terminal may not transmit symbols of the SRS (202) that overlap with another uplink channel (203).

[0215] The terminal can transmit symbols of the SRS (202) that do not overlap with other uplink channels (203). If the terminal supports an operation of counting SRS transmission slots based on available slots, the base station triggers the transmission of the SRS of the corresponding SRS resource set to the t+1th available slot, i.e., the 1st available slot, by using the SRS offset indicator field of the DCI to indicate t as 0. Then, the terminal does not determine that the uplink slot where other uplink channels (203) are transmitted is an available slot, but rather determines that the first uplink slot where all SRS resources (204) within the SRS resource set can be transmitted is an available slot, and can transmit the SRS using that slot. That is, even if the terminal can transmit part of the SRS using some symbols of the uplink slot where other uplink channels (203) are transmitted, it does not transmit the SRS, and can transmit the entire scheduled SRS using the subsequent uplink slot (204). Alternatively, the terminal may transmit only a portion of the entire SRS resource that is scheduled or performed. Or, even if the conditions for determining the existing SRS transmission slot are relaxed so that the terminal can transmit a portion of the SRS resources of the SRS (202), the transmitted SRS resource may not be the SRS resource transmitted to the terminal's SRS port that the base station intends to measure. And if another uplink channel (203) is scheduled before the SRS, the base station may not be able to trigger the terminal to transmit the SRS resource to the SRS port desired by the base station within the SRS resource set using the symbols in the uplink slot remaining after the terminal has transmitted the other uplink channel (203).This is because, since the SRS resource set and SRS resource are grouped according to the RRC parameters that the base station has pre-configured in the terminal, there may not be any RRC parameter settings that correspond to the UL resources available in real time.

[0216] In this way, if the UL resources are insufficient and the terminal cannot transmit all SRS resources within the SRS resource set, it may not be able to transmit any SRS using the resources, and the transmission of SRS may be delayed or the SRS for the SRS port that the base station intends to measure may not be measured.

[0217] If the SRS can be scheduled so that the terminal can transmit the SRS according to the UL resources in the currently available time frequency range, it can be utilized efficiently even if the UL resources in the available time frequency range are small, and the SRS can be flexibly scheduled without resetting separate RRC parameters.

[0218] Embodiment 1-1 describes rules and configuration methods for supporting a new framework for flexible SRS. Embodiment 1-2 describes a method for configuring DCI for scheduling aperiodic SRS based on the new framework described in Embodiment 1-1. Embodiment 1-3 describes a method for configuring RRC for scheduling semi-persistent SRS and periodic SRS based on the new framework described in Embodiment 1-1, and a method for configuring DCI or MAC CE for enabling / disabling semi-persistent SRS.

[0219] The first embodiment designs a framework for transmitting flexible SRS by considering the settings and conditions required to transmit SRS, and proposes an RRC setting method, base station operation, and terminal operation to support it.

[0220] Through RRC parameters, information such as the number of SRS resources and ports in the time / frequency domains configured at the SRS resource level, and the uses of the SRSs, can be separately configured and decoupled so that they can be scheduled in different combinations. Specifically, to support an SRS triggering method that can be combined depending on the situation, rather than an SRS triggering method based on SRS resource sets and SRS resources, the following information may be considered.

[0221] -Slot offset: Indicates the slot-level offset to be scheduled by DCI or to transmit SRS within the periodicity.

[0222] - Starting symbol and symbol length for transmitting the SRS: Indicates the resources in the time domain of the scheduled SRS. It may support a symbol length greater than 14 symbols, etc., if it allows the transmission of all symbols within a slot from one symbol to one or a single triggered SRS between slots.

[0223] -(If necessary) SRS repetition count in the time domain: Indicates the number of times an SRS transmission is repeated using the same SRS port. This can also be implicitly indicated through combinations with other indicators.

[0224] -Transmission Comb: Indicates the comb pattern in the frequency domain of the scheduled SRS, and indicates the frequency offset value and cyclic shift value according to the comb pattern.

[0225] - Frequency start point for transmitting SRS, frequency domain shift, and frequency hopping parameters: Indicates the frequency domain resources of the scheduled SRS, the frequency hopping pattern, and the number of RBs in the frequency domain.

[0226] - Frequency domain or code domain additional function: may indicate whether hopping occurs in the code domain, such as sequence hopping of SRS or hopping of sequence group, or whether hopping occurs in the frequency domain, such as hopping offset values ​​for Comb patterns or cyclic shift hopping, and may indicate values ​​for hopping subsets.

[0227] - Usage of SRS: Indicates the usage of the scheduled SRS. For the usage of the SRS, 'codebook' to support codebook-based PUSCH (the base station can determine the precoder to support codebook-based PUSCH based on the UL channel estimated through the SRS for codebook use and instruct this via TPMI), 'nonCodebook' to support noncodebook-based PUSCH (the base station can determine the SRS port to use for the terminal to transmit PUSCH based on the UL channel estimated through the SRS for nonCodebook use and instruct this via SRI), 'antennaSwitching' to measure the DL channel based on reciprocity in the TDD system (the DL channel can be estimated based on reciprocity from the UL channel estimated by receiving the SRS for antennaSwitching use), and 'beamManagement' to manage the terminal's UL beam.

[0228] - Another RS ​​associated with the SRS (e.g., NZP CSI-RS) considering a specific usage (e.g., 'nonCodebook' use): Indicates another RS ​​associated with the SRS (e.g., NZP CSI-RS) to transmit the SRS of the specific usage (e.g., 'nonCodebook' use). The terminal may calculate a precoder or configure a UL beam or spatial filter to transmit the SRS by referring to the indicated RS.

[0229] -SRS Transmission Power Parameters: These indicate the transmission power parameters to be applied by the terminal when transmitting SRS. Specifically, pathlossReferenceRS for referencing p0, alpha, and pathloss, and srs-PowerControlAdjustmentStates for indicating whether to share closed-loop power control information with PUSCH or manage it separately, may represent the transmission power parameters to be applied by the terminal when transmitting SRS. Alternatively, if it operates based on a unified TCI state, parameters such as followUnifiedTCI-StateSRS, which determines whether to determine the transmission power of the SRS according to the TCI state indicated by DCI or the TCI state set by the RRC parameter; srs-TCI-State, which determines the transmission power of the SRS according to the TCI state set by the RRC parameter; and applyIndicatedTCI-State, which determines the transmission power of the SRS according to the TCI state indicated by DCI and multiple TCI states are indicated, may represent the parameters to indicate the transmission power values ​​to be applied by the terminal when transmitting SRS. Alternatively, it may refer to parameters such as Uplink-powerControlId to indicate Uplink-powerControl, which is configured with transmission power parameters to be applied to the transmission of the corresponding SRS, and PathlossReferenceRS-Id to indicate PathlossReferenceRS.

[0230] -Trigger state: This setting is configured to indicate the set triggered by the corresponding DCI among the aperiodic SRS resource sets scheduled based on the DCI, but it can be omitted. This is because, rather than supporting based on SRS resource sets, SRS resources and SRS ports in the time / frequency domains are scheduled directly by the DCI, so a separate trigger state may not be indicated by the DCI.

[0231] To support a flexible SRS scheduling framework by considering the information that must be instructed and the information that can be omitted for transmitting SRS, the base station may set the following information to the terminal as RRC parameters or define rules between the base station and the terminal. If aperiodic SRS is supported, one of the candidate RRC parameters or actions according to predefined rules may be instructed to the DCI to schedule the SRS.

[0232] - TDRA (Time Domain Resource Allocation): Information is configured by combining elements to indicate a time-domain resource for a scheduled SRS. If aperiodic SRS is supported, one of the pieces of information configured via DCI is indicated. For example, in the RRC configuration for TDRA, a combination of the SRS starting symbol position, symbol length, slot offset, and number of SRS iterations can be configured as a single candidate to indicate the SRS time-domain resource. For candidates for different TDRA indications, at least one piece of information among the SRS starting symbol position, symbol length, slot offset, and number of SRS iterations is set to a different value.

[0233] - FDRA (frequency domain resource allocation): This is configured by combining information to indicate the frequency domain resources of the scheduled SRS. If aperiodic SRS is supported, it indicates one of the information configured via DCI. For example, the RRC configuration for FDRA includes the frequency start point of the SRS to indicate the frequency domain resources of the SRS (which can be defined as {frequency start RB of the SRS = minimum number of RBs for SR transmission x frequency start point of the SRS}), frequency domain shift, and frequency hopping parameters ( A combination of (indicating frequency hopping patterns and the number of RBs of the SRS, etc.) etc., may be included as a single candidate. Alternatively, a combination of the frequency start point of the SRS, the number of RBs of the SRS, and an indicator indicating whether frequency hopping is performed, etc., may be included as a single candidate. That is, when a base station sets RRC parameters for the SRS, the base station, shift in the frequency domain and Instead of frequency hopping parameters including the above, combinations of values ​​to directly indicate resources in the frequency domain used to transmit the SRS may be set as candidates. Additionally, parameters that can be combined as FDRA candidate values ​​may be considered, such as parameters indicating the Transmission Comb, and parameters indicating additional functions in the frequency domain or code domain. For candidates for different FDRA indications, at least one of the information among the parameters for indicating SRS resources in the frequency domain of the described SRS may be set to a different value.

[0234] -Parameters indicating Transmission Comb, parameters indicating additional functions in the frequency domain or code domain: Parameters indicating Transmission Comb, parameters indicating additional functions in the frequency domain or code domain may be set as separate RRC parameters rather than RRC settings for FDRA. If aperiodic SRS is supported, a separate DCI field may be added for the corresponding parameter.

[0235] - Usage of scheduled SRS: If aperiodic SRS is supported, the usage of the scheduled SRS is not set as a separate RRC parameter but can be indicated through a specific field of the DCI according to an embodiment to be described later. If semi-persistent SRS or periodic SRS is supported, the base station can set the usage for the corresponding SRS to the terminal as a separate RRC parameter.

[0236] - Another RS ​​associated with the SRS (e.g., NZP CSI-RS) considering specific usage (e.g., 'non-Codebook' use): Another RS ​​associated with the SRS of specific usage can be set as an RRC parameter. However, such RRC settings may not be separately specified via DCI.

[0237] -SRS Port: The maximum number of SRS ports that the terminal can support can be set as an RRC parameter. If aperiodic SRS is supported, the base station can instruct the terminal via DCI the number of SRS ports (or combinations of SRS ports, etc.) to schedule.

[0238] The first and second embodiments specifically propose an operation in which a base station schedules aperiodic SRS and a terminal transmits the scheduled SRS based on a new framework to support a flexible SRS transmission method.

[0239] A method is described for scheduling an aperiodic SRS based on RRC parameter settings or rules between a base station and a terminal that are necessary to support the flexible SRS scheduling framework described in the 1-1 embodiment, and for the terminal to transmit the scheduled aperiodic SRS.

[0240] In NR, the number of bits in the DCI field for triggering aperiodic SRS is defined as 2 bits, of which 3 code points can be used to trigger some of the SRS resource sets configured in RRC. If a framework for flexible SRS scheduling is introduced, available UL resources can be utilized efficiently because SRS resources can be scheduled more flexibly; however, the DCI overhead required for scheduling may increase. Considering these points, three main DCI operation methods can be considered.

[0241] [Method 1] uses a DCI composed of two stages, and [Method 2] introduces a flag bit or a new RNTI and interprets subsequent DCI fields as DCI fields to support a flexible SRS scheduling framework based on whether the value indicated by the flag bit or the new RNTI is descrambling. [Method 3] interprets other DCI fields as DCI fields to support a flexible SRS scheduling framework if the values ​​of specific fields within the DCI are set to a certain combination.

[0242] [Method 1] A base station may use a first-stage DCI based on a two-stage DCI to instruct a terminal whether to schedule an SRS or the usage of the scheduled SRS, and may use a second DCI to instruct specific scheduling information for the scheduled SRS. The base station may configure an SRS request field in the first-stage DCI. The SRS request field included in the first-stage DCI may be 1 bit in size. In this case, if the base station does not schedule an aperiodic SRS to a terminal receiving a DCI containing a 1-bit SRS request field, the base station may instruct the SRS request field to be '0'. If the base station schedules an aperiodic SRS to a terminal receiving a DCI containing a 1-bit SRS request field, the base station may instruct the SRS request field to be '1'. In one embodiment, the bit size of the SRS request field included in the first stage DCI may be defined as 2, and the base station may indicate whether the aperiodic SRS is scheduled and the usage of the scheduled SRS together with the 2-bit SRS request field. If the base station does not schedule the aperiodic SRS to a terminal receiving the DCI containing the 2-bit SRS request field, the base station may indicate the SRS request field as '00'.If a base station schedules an aperiodic SRS with usage of codebook or nonCodebook to a terminal receiving a DCI containing a 2-bit SRS request field (whether the scheduled SRS is for codebook or nonCodebook use can be determined by other RRC parameters set in the terminal (e.g., whether txConfig in PUSCH-Config is set to codebook or nonCodebook)), the base station may set the SRS request field to '01'. If a base station schedules an aperiodic SRS with usage of beamManagement to a terminal receiving a DCI containing a 2-bit SRS request field, the base station may set the SRS request field to '10'. If a base station schedules an aperiodic SRS with usage of antennaSwitching to a terminal receiving a DCI containing a 2-bit SRS request field, the base station may set the SRS request field to '11'. The table below shows examples where the code point of the 2-bit SRS request field is used to indicate whether SRS is scheduled and the purpose of the scheduled SRS.

[0243]

[0244] Unlike Table 11, the uses of each code point and scheduled SRS may be mapped to different combinations.

[0245] The base station instructs the second stage DCI with specific scheduling information for the SRS to be scheduled. The second stage DCI may include DCI fields to indicate one of the actions based on the aforementioned RRC parameters or predefined rules. The second stage DCI may include specific DCI fields for scheduling the SRS as follows:

[0246] - [DCI Configuration 1: TDRA Field - FDRA Field - SRS Port Field - TCI State Field for SRS] The base station may specify one of the TDRA candidates configured by RRC to indicate the time domain resource of the SRS to be scheduled in the TDRA field within the second stage DCI. The base station may specify one of the FDRA candidates configured by RRC to indicate the frequency domain resource of the SRS to be scheduled in the FDRA field within the second stage DCI. In this case, the FDRA candidate configured by RRC may be configured with parameters indicating a Transmission Comb that can be additionally combined, and parameters indicating additional functions in the frequency domain or code domain. The base station may specify the SRS port for transmitting the scheduled SRS in the SRS port field based on the maximum number of SRS ports configured by RRC. In this case, the SRS port field may indicate only the number of SRS ports to be used for transmitting the scheduled SRS. For example, if the base station sets the maximum number of SRS ports in the terminal to 8 and schedules 4-port SRS transmission, the base station may configure the SRS port field to 3 bits and indicate the field as '100'. Alternatively, the SRS port field may indicate an SRS port for transmitting scheduled SRS based on a bitmap or code point. For example, if the base station sets the maximum number of SRS ports in the terminal to 8 and indicates an SRS port based on a bitmap, the base station may configure the SRS port field to 8 bits and indicate the SRS port field as '00001111' to schedule SRS to be transmitted to the 5th, 6th, 7th, and 8th SRS ports.Similarly, to schedule SRS transmissions to a different number of different SRS ports, the base station may instruct the terminal by setting the bit corresponding to the SRS port the terminal will use to transmit the SRS to 1, and the bit corresponding to the SRS port the terminal will not use to transmit the SRS to 0. If the base station has instructed the terminal to multiple TCI states to support multi-TRP (transmission and reception point) using the unified TCI framework, and if multiple TCI states can be applied to uplink transmission and reception after the beam application time, the base station may instruct the terminal to specify the TCI state to apply to the scheduled SRS by providing a TCI state field for the SRS. The TCI state field for the SRS may consist of 1 bit (it may be composed of 1 bit if the number of supported mTRPs is 2, and 2 bits if it is 4. If a larger number of TRPs is supported, the TCI state field for the SRS may be configured using a larger number of bits to account for this). If the TCI state field for a 1-bit SRS is indicated as '0', the terminal can transmit a scheduled SRS using the first TCI state among multiple TCI states. If the TCI state field for a 1-bit SRS is indicated as '1', the terminal can transmit a scheduled SRS using the second TCI state among multiple TCI states. DCI configuration 1 assumes that the usage of the scheduled SRS is indicated via the first stage DCI or by another method.And it may be assumed that transmission comb-related parameters and frequency domain additional functions (e.g., hopping offset values ​​for the comb pattern or cyclic shift hopping) or code domain additional functions (e.g., sequence hopping of SRS or hopping of sequence groups, etc.) are included in the combination candidates of the FDRA set as RRC.

[0247] - [DCI Configuration 2: TDRA field - FDRA field - SRS port field - TCI state field for SRS - Usage field - Transmission Comb field - Comb hopping field - cyclic shift hopping field - sequence hopping field - sequence group hopping field] The TDRA field, FDRA field, SRS port field, and TCI state field for SRS in DCI Configuration 2 can be configured as DCI fields in the same way as described in DCI Configuration 1. In this case, it is assumed that the FDRA combination candidates set as RRC do not include information such as Transmission Comb, Comb hopping, cyclic shift hopping, sequence hopping, sequence group hopping, etc., and that the usage of the SRS scheduled through first stage DCI or other methods is not specified. The base station may configure the Usage field with 2 bits (it may be configured with more than 2 bits if SRS usage is added) and specify one of four usages (codebook or nonCodebook or beamManagement or antennaSwitching) or three usages (one of codebook or nonCodebook or beamManagement or antennaSwitching). The Transmission Comb field may specify the configuration of the transmission comb of the scheduled SRS and the comb offset by specifying one of the candidates for the transmission comb set by the RRC parameter to support the transmission comb (2 and / or 4 and / or 8) that the terminal can support.Based on a UE capability report regarding whether the terminal can support the corresponding feature, the base station may set candidates for Comb hopping as RRC parameters and candidates for cyclic shift hopping as RRC parameters. For terminals capable of supporting each feature, the base station directs one of the Comb hopping candidates set as RRC parameters to the Comb hopping field and one of the cyclic shift hopping candidates set as RRC parameters to the cyclic shift hopping field. If the terminal cannot support the corresponding feature (Comb hopping or cyclic shift hopping), the DCI field (Comb hopping field or cyclic shift hopping field) for directing the candidate for each feature may not be configured in the second stage DCI. The base station may set candidates for sequence hopping and sequence group hopping as respective RRC parameters and may direct one of the candidates for sequence hopping and sequence group hopping set as RRC to the terminal using the sequence hopping field and the sequence group hopping field. Alternatively, the base station may combine candidates for sequence hopping and sequence group hopping to set them as RRC parameters, and may use a single integrated sequence hopping and sequence group hopping field (consisting of a single field rather than individual fields) to instruct the terminal to one of the combination candidates for sequence hopping and sequence group hopping set as RRC.

[0248] - [DCI Configuration 3] A DCI configuration in which some of the DCI fields defined in DCI Configuration 1 and DCI Configuration 2 are omitted can be supported.

[0249] - [DCI Configuration 4] TDRA (or and FDRA) candidates that can be indicated by the TDRA (or and FDRA) field can be set as a list-type RRC parameter, and different TDRA (or and FDRA) candidates for each SRS usage can be set by different list-type RRC parameters. For example, TDRA (or and FDRA) List 1 can be set as an RRC parameter to indicate TDRA (or and FDRA) for an SRS whose usage is codebook or nonCodebook, TDRA (or and FDRA) List 2 can be set as an RRC parameter to indicate TDRA (or and FDRA) for an SRS whose usage is beamManagement, and TDRA (or and FDRA) List 3 can be set as an RRC parameter to indicate TDRA (or and FDRA) for an SRS whose usage is antennaSwitching. The number of candidates for TDRA (or and FDRA) included in each list may differ, and the number of bits in the TDRA (or and FDRA) field within the DCI may be determined based on the TDRA (or and FDRA) list containing the largest number of candidates among all TDRA (or and FDRA) lists. Depending on the usage of the SRS indicated by the first stage DCI or the usage of the SRS indicated by other methods, the terminal may determine the time (or and frequency) domain resources of the scheduled SRS by referring to the TDRA (or and FDRA) field within the second stage DCI and the TDRA (or and FDRA) list for the corresponding usage.

[0250] -[DCI Configuration 5] Candidates can be set as a single RRC parameter by combining the time domain resources and frequency domain resources of the scheduled SRS, and the time domain resources and frequency domain resources of the scheduled SRS can be indicated using a single DCI field.

[0251] The bit size of each field described in [DCI Configuration 1], [DCI Configuration 2], and [DCI Configuration 3] is determined by the number of candidates for each field set as RRC and whether the terminal supports the corresponding feature. For example, if the terminal cannot support the Comb Hopping feature, the bit size of the Comb Hopping field may be defined as 0.

[0252] The first stage DCI can be transmitted via PDCCH. The second stage DCI can be transmitted via PDCCH in the same way as the first stage DCI. Alternatively, the second stage DCI can be transmitted via PDSCH instead of PDCCH, unlike the first stage DCI. Specifically, the second stage DCI is transmitted via PDSCH but is considered as DCI separate from the data and can be transmitted by mapping it to the RE of PDSCH according to separate multiplexing rules. Alternatively, the second stage DCI is transmitted via PDSCH and can be transmitted as a MAC CE. In this case, a new LCID can be defined to transmit the second stage DCI, and the terminal can identify the second stage DCI using the MAC CE received with the new LCID and understand the specific time domain resources, frequency domain resources, and transmission technique of the scheduled SRS.

[0253] FIG. 3 shows an example of a DCI format for scheduling a flexible SRS using a two-stage DCI according to embodiments of the present disclosure.

[0254] The base station may configure an SRS request field (301) or a field (302) indicating the usage of the SRS scheduled with the SRS request within the first stage DCI (300). At this time, fields for indicating other information in addition to the field may also be configured within the first stage DCI (300). If the base station configures a field (302) indicating the usage of the SRS scheduled with the SRS request within the first stage DCI (300), each code point indicated by the corresponding 2-bit field may indicate whether the SRS is triggered and the usage of the triggered SRS (303). The base station may configure fields (311 or 312) indicating scheduling information regarding the resources and transmission method of the SRS scheduled with the SRS request field (301) or the field (302) indicating the usage of the SRS scheduled with the SRS request within the second stage DCI (310) within the second stage DCI (310). Depending on the DCI configuration method, the fields included in the second-stage DCI may be configured differently.

[0255] [Method 2] A base station may configure a 1-bit flag field as the first bit of a DCI format that can be used to trigger an SRS. Alternatively, a base station may configure a 1-bit flag field as the last bit of a DCI format that can be used to trigger an SRS. The flag field may be used to indicate whether to schedule an SRS using a flexible SRS scheduling method. For example, if the 1-bit flag field is indicated as '1', the terminal identifies that the received DCI format was transmitted by the base station for the purpose of scheduling a flexible SRS and may use the remaining DCI bits to determine the resources and transmission method of the scheduled flexible SRS. For example, as a method of configuring the DCI bits to determine the resources and transmission method of the scheduled flexible SRS, the method of configuring the DCI field indicated as a second stage DCI as described above in [Method 1] may be used.

[0256] FIG. 4 shows an example of a DCI format for scheduling a flexible SRS using a flag bit according to embodiments of the present disclosure.

[0257] The first example (401) represents an example in which a 1-bit flag field is configured as the first field of the DCI format, and a Comb or hopping method is indicated in combination with the FDRA field, and the usage of the scheduled SRS is indicated in a different DCI (e.g., first stage DCI) or in a different way.

[0258] The second example (402) represents an example in which a 1-bit flag field is configured as the first field of the DCI format, a Comb or hopping method is indicated by a separate DCI field, and the usage of the scheduled SRS is indicated by the same DCI Usage field.

[0259] The third example (403) represents an example where a 1-bit flag field is configured as the last field of the DCI format, and the Comb or hopping method is indicated in combination with the FDRA field, and the usage of the scheduled SRS is indicated by a different DCI (e.g., first stage DCI) or a different method. In this case, zeros (0) may be added (pad zero bits) so that the DCI has the same number of DCI bits as the other DCI format or the same format used for a different purpose.

[0260] The fourth example (404) represents an example in which a 1-bit flag field is configured as the last field of the DCI format, a Comb or hopping method is indicated by a separate DCI field, and the usage of the scheduled SRS is indicated by the Usage field of the same DCI. In this case, zeros (pad zero bits) may be added to the DCI so that it has the same number of DCI bits as other DCI formats or the same format used for other purposes.

[0261] In one embodiment, when a DCI format is descrambled into a specific RNTI (e.g., a newly introduced RNTI for a flexible SRS scheduling framework) without using a 1-bit flag field, the terminal can identify the DCI successfully detected by the corresponding RNTI as the DCI for scheduling the flexible SRS. At this time, as a method of configuring the DCI bit to determine the resources and transmission technique of the scheduled flexible SRS, a method of configuring the DCI field indicated as the second stage DCI as described above in [Method 1] may be used.

[0262] [Method 3] If a combination of specific fields within a DCI format capable of scheduling a flexible SRS is set to certain values, the terminal can reinterpret other DCI fields as DCI fields for flexible SRS scheduling to identify SRS resources and transmission techniques for transmitting the SRS. Specifically, if the HARQ process number field and / or Redundancy version field and / or Modulation and coding scheme field and / or New date indicator field are set to specific values, the terminal can reinterpret and utilize other fields as fields for scheduling the flexible SRS. If the HARQ process number field and / or Redundancy version field and / or Modulation and coding scheme field and / or New date indicator field are set to specific values, the TDRA field and FDRA field can be used to indicate the time and frequency resources of the scheduled SRS. Other existing fields can also be reinterpreted and utilized as fields to indicate SRS usage or SRS transmission methods. The number of bits required for scheduling not only the TDRA and FDRA fields but also other SRSs may be smaller than or equal to the number of bits in the previously set fields.

[0263] The first-third embodiment specifically proposes a base station scheduling a periodic SRS or a semi-persistent SRS and a terminal transmitting the scheduled SRS based on a new framework to support a flexible SRS transmission method.

[0264] In the case of Periodic SRS, the terminal can periodically transmit SRS after being set as an RRC parameter. Along with the SRS scheduling information and SRS transmission method indicated by the DCI to schedule the aperiodic SRS, the periodicity of the repeated transmission of SRS and the slot level offset within the period can be set using the RRC parameter. That is, for each periodic SRS, setting of RRC parameters for SRS transmission is required, and for each periodic SRS, the RRC parameter may include one TDRA RRC parameter to indicate a time resource (or an indicator capable of indicating one TDRA candidate from the aforementioned TDRA list) and one FDRA RRC parameter to indicate a frequency resource (or an indicator capable of indicating one FDRA candidate from the aforementioned FDRA list). In addition, the RRC parameters for the periodic SRS may include RRC settings for the usage of the corresponding periodic SRS, RRC settings for the repetition period, RRC settings for the slot-level offset within the repetition period, RRC settings for the SRS port, or indicators for the TCI state to be applied. Furthermore, depending on whether the terminal supports additional SRS transmission techniques, the RRC parameters for the periodic SRS may include RRC settings for applying additional hopping techniques in the frequency domain and RRC settings for applying additional hopping techniques in the code domain.

[0265] In the case of semi-persistent SRS, some information regarding the SRS to be activated and transmitted periodically is set as RRC parameters, while the activation and remaining scheduling information is indicated by the DCI for activation. Some of the information that must be indicated in a flexible SRS scheduling-based framework can be indicated through the DCI field of the DCI for activating the semi-persistent SRS. For example, the TDRA, FDRA, SRS port, and / or TCI state to be applied for transmitting the SRS of the semi-persistent SRS can be indicated through the DCI for activation. Additionally, within the RRC parameters for each semi-persistent SRS, RRC settings for SRS usage, RRC settings for the repetition period, and / or RRC settings for the slot-level offset within the repetition period may be included. Furthermore, depending on whether the terminal supports additional SRS transmission techniques, RRC settings for applying additional hopping techniques in the frequency domain and RRC settings for applying additional hopping techniques in the code domain may be included.

[0266] The second embodiment specifically describes an RRC setting method and a scheduling method for triggering a plurality of SRS transmissions.

[0267] When supporting Aperiodic SRS, the same trigger state can be set as an RRC parameter for multiple SRS resource sets, and multiple SRS resource sets with the same trigger state can be triggered simultaneously with a single DCI.

[0268] The aperiodic SRS trigger method based on the flexible SRS scheduling framework described in the first embodiment is explained based on a single SRS transmission. Even in the flexible SRS scheduling framework, additional RRC settings and DCI instructions may be required to trigger multiple SRSs with a single DCI.

[0269] Two options may be considered to trigger multiple SRSs into a single DCI (if a two-stage DCI is used, the combination of the first-stage DCI and the second-stage DCI can be understood as a single DCI). In the case of [Option 1], multiple fields may be defined to trigger each SRS within the DCI that triggers the SRS. In the case of [Option 2], considering the transmission of multiple SRSs, RRC parameters for the TDRA, RRC parameters for the FDRA, and RRC parameters to indicate other SRS scheduling information may be set.

[0270] [Option 1]

[0271] Multiple SRS request fields or SRS request fields with a large bit size may be supported in the DCI for triggering Aperiodic SRS. For example, the base station may determine the maximum number of SRS that can be triggered simultaneously based on terminal capabilities or according to rules predefined by the base station and the terminal. The number of SRS request fields in the DCI may correspond to the maximum number of SRS that can be triggered simultaneously. As a specific example, if a maximum of four SRS can be triggered simultaneously, four SRS request fields may be included in the DCI for triggering Aperiodic SRS. Alternatively, the number of bits in the SRS request field may be increased to allow additional code points to be indicated using the SRS request field, taking into account the maximum number of SRS that can be triggered simultaneously. For example, among the examples described in [Method 1] of the first embodiment, a 1-bit SRS request field indicating only whether an SRS is triggered may be expanded to 2 bits. In this case, the following Table 12 shows examples of SRS request fields for triggering multiple SRS.

[0272]

[0273] If the SRS request field of the first stage DCI indicates whether the SRS is triggered and the usage of the triggered SRS together, the SRS request field can be configured with more than 2 bits as shown in Table 13 below, and multiple SRS combinations with different usages can be indicated.

[0274]

[0275] Table 13 is an example, and the SRS request field may be configured with more than 3 bits to trigger more SRSs simultaneously. If SRSs are triggered using a two-stage DCI and specific scheduling information for the triggered SRSs is directed to the second-stage DCI, the same number of DCI fields as the number of SRSs triggered by the first-stage DCI may be included in the second-stage DCI. For example, the terminal may identify that two aperiodic SRSs have been triggered by receiving the SRS request field of the first-stage DCI according to [Table 11]. Subsequently, the terminal may receive specific scheduling information for the two aperiodic SRSs through the second-stage DCI. Two TDRA fields and two FDRA fields may be included within the second-stage DCI received by the terminal. Furthermore, DCI fields that may be included in another second-stage DCI may be configured twice, in the same manner as described in the first-2 embodiments. In this case, the first of the two fields may represent scheduling information for the first SRS, and the second field may represent scheduling information for the second SRS.

[0276] [Option 2]

[0277] RRC parameters may be configured so that candidate values ​​indicated by DCI fields can schedule multiple SRSs. As a specific example, multiple time-domain resource information may be included to trigger multiple SRSs for some TDRA candidates within a TDRA list configured by the RRC indicated by the TDRA field. That is, within the RRC parameters for a single TDRA candidate, RRC parameters for multiple starting symbol positions, multiple symbol lengths, multiple slot offsets, or multiple SRS iterations may be configured. Other DCI fields (e.g., FDRA fields and other SRS-related fields) may also have information configured as RRC parameters to trigger multiple SRSs within a configuration indicated by a single code point. Alternatively, the configuration information indicated by some DCI fields may indicate a single piece of information rather than multiple different pieces of information. If the TDRA field and / or FDRA field trigger different time / frequency resources to trigger multiple SRSs, but different DCI fields indicate the same information, the terminal can apply the information indicated by the same information to the multiple triggered SRSs and transmit it. For example, if the TDRA field and the FDRA field trigger different time / frequency resources and the field indicating the TCI state to be applied to the SRS indicates the same information, the terminal can apply the same TCI state to multiple SRSs transmitted to different time / frequency resources and transmit them.

[0278] When SRS is scheduled by applying [Option 2], the terminal may transmit a single SRS or multiple SRSs as follows. If all fields within the DCI indicate RRC configuration information that triggers a single SRS, the terminal transmits the single SRS based on the indicated scheduling information. If all fields within the DCI indicate RRC configuration information that triggers multiple SRSs, the terminal transmits multiple SRSs based on the respective scheduling information indicated by the DCI. If the base station indicates RRC configuration information that triggers multiple SRSs in some fields within the DCI, and RRC configuration information containing a single SRS scheduling information in the remaining fields, the terminal may apply the corresponding scheduling information to each of the multiple SRSs if the DCI fields indicate RRC configuration information that triggers multiple SRSs, and may apply the corresponding scheduling information identically to the multiple SRSs.

[0279] FIG. 5 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0280] Referring to FIG. 5, the terminal may include a transceiver (referring to a terminal receiver (500) and a terminal transmitter (510)), a memory (not shown), and a terminal processing unit (505, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (500, 510), memory, and terminal processing unit (505) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0281] The transceiver can transmit and receive signals with a base station. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts its frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0282] In addition, the transceiver can receive a signal through a wireless channel and output it to a processor, and transmit the signal output from the processor through a wireless channel.

[0283] Memory can store programs and data necessary for the operation of the terminal. Additionally, memory can store control information or data included in signals transmitted and received by the terminal. Memory may be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0284] In addition, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiment. For example, the processor can receive a DCI composed of two layers and control the components of the terminal to receive multiple PDSCHs simultaneously. There may be multiple processors, and the processors can perform the operation of controlling the components of the terminal by executing a program stored in memory.

[0285] FIG. 6 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0286] Referring to FIG. 6, the base station may include a transceiver unit, which refers to a base station receiver (600) and a base station transmitter (610), a memory (not shown), and a base station processing unit (605, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver unit (600, 610), memory, and base station processing unit (605) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. In addition, the transceiver unit, memory, and processor may be implemented in the form of a single chip.

[0287] The transceiver can transmit and receive signals with a terminal. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts its frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0288] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

[0289] Memory can store programs and data necessary for the operation of the base station. Additionally, memory can store control information or data included in signals transmitted and received by the base station. Memory can be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0290] A processor can control a series of processes to enable a base station to operate according to the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to configure two layers of DCIs containing allocation information for a plurality of PDSCHs and to transmit them. There may be multiple processors, and the processors can perform control operations on the components of the base station by executing a program stored in memory.

[0291] Referring to FIG. 7, a terminal according to one embodiment may include a transceiver (710), a memory (720), and a processor (730). The transceiver (710), memory (720), and processor (730) of the UE may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited thereto. For example, the terminal may include more or fewer components than those described above. Additionally, the processor (730), the transceiver (710), and the memory (720) may be implemented as a single chip. Additionally, the processor (730) may include at least one processor. Furthermore, the terminal of FIG. 7 may correspond to the terminal of FIG. 5.

[0292] The transceiver (710) collectively refers to a UE receiver and a UE transmitter and can transmit and receive signals with a base station or network entity. The signals transmitted and received with the base station or network entity may include control information and data. The transceiver (710) may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise amplification and down-converting the frequency of a received signal. However, this is merely an example of the transceiver (710), and the components of the transceiver (710) are not limited to an RF transmitter and an RF receiver.

[0293] Additionally, the transceiver (710) can receive a signal through a wireless channel and output it to a processor (730), and transmit the signal output from the processor (730) through a wireless channel. The memory (720) can store programs and data required for the operation of the UE. Additionally, the memory (720) can store control information or data included in a signal acquired by the UE. The memory (720) may be a storage medium or a combination of storage media such as read-only memory (ROM), random access memory (RAM), a hard disk, CD-ROM, and DVD.

[0294] The processor (730) can control a series of processes to operate the terminal. For example, the transceiver (710) can receive a data signal including a control signal transmitted by a base station or network entity, and the processor (730) can determine the result of receiving the control signal and data signal transmitted by the base station or network entity. The processor (730) of FIG. 7 can correspond to the terminal processing unit (505) of FIG. 5.

[0295] Referring to FIG. 8, a base station according to one embodiment may include a transceiver (810), a memory (820), and a processor (830). The transceiver (810), memory (820), and processor (830) of the base station may operate according to the communication method of the base station described above. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. Additionally, the processor (830), the transceiver (810), and the memory (820) may be implemented as a single chip. Additionally, the processor (830) may include at least one processor. Furthermore, the base station of FIG. 8 may correspond to the base station of FIG. 6.

[0296] The transceiver (810) collectively refers to a base station receiver and a base station transmitter, and can transmit and receive signals with a terminal (UE) or a network entity. The signals transmitted and received with the terminal or network entity may include control information and data. The transceiver (810) may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise amplification and down-converting the frequency of a received signal. However, this is merely an example of the transceiver (810), and the components of the transceiver (810) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (810) can receive a signal through a wireless channel and output it to a processor (830), and transmit the signal output from the processor (830) through a wireless channel.

[0297] The memory (820) can store programs and data necessary for the operation of the base station. Additionally, the memory (820) can store control information or data included in signals acquired by the base station. The memory (820) may be a storage medium such as a read-only memory (ROM), random access memory (RAM), hard disk, CD-ROM, DVD, or a combination of storage media. The processor (830) can control a series of processes to enable the base station to operate as described above. For example, the transceiver (810) can receive a data signal including a control signal transmitted by a terminal, and the processor (830) can determine the result of receiving the control signal and the data signal transmitted by the terminal. The processor (830) of FIG. 8 may correspond to the base station processing unit (605) of FIG. 6.

[0298] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0299] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.

[0300] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0301] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to the device performing the embodiment of the present disclosure through an external port. Additionally, a separate storage device on the communication network may be connected to the device performing the embodiment of the present disclosure.

[0302] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0303] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G, or NR system.

[0304] Meanwhile, the order of description in the drawings illustrating the method of the present invention does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel.

[0305] Alternatively, drawings describing the method of the present invention may omit some components and include only some components to the extent that the essence of the present invention is not impaired.

[0306] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not impair the essence of the invention.

[0307] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will understand that modifications can be easily made to other specific forms without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and their equivalents should be interpreted as being included within the scope of the present disclosure.

Claims

1. A method performed by a UE (user equipment) of a wireless communication system, A step of receiving a first DCI (downlink control information) from a base station, the DCI including first information associated with the scheduling of a sounding reference signal (SRS); and A method comprising the step of transmitting the SRS to the base station based on the first DCI.

2. In Paragraph 1, A method comprising at least one of the above first information including a TDRA (time domain resource allocation) field, an FDRA (frequency domain resource allocation) field, a field for indicating a Transmission Comb, a field for indicating a Usage for the SRS, a field for indicating the number of ports for the SRS, or a field for indicating a TCI (transmission configuration indicator) status for the SRS.

3. In Paragraph 1, The method further includes the step of receiving a second DCI from the base station, the second DCI including a request to trigger the transmission of the SRS. The above second DCI is received prior to the above first DCI, in a method.

4. In Paragraph 1, The first DCI above includes information for indicating an identification method for a first field included in the first DCI, or A method in which the first DCI indicates an identification method for the first field by a combination of at least one field included in the first DCI.

5. A method performed by a base station of a wireless communication system, A step of transmitting a first DCI (downlink control information) containing first information associated with the scheduling of an SRS (sounding reference signal) to a UE (user equipment); and A method comprising the step of receiving the SRS transmitted from the above UE based on the first DCI.

6. In Paragraph 5, A method comprising at least one of the above first information including a TDRA (time domain resource allocation) field, an FDRA (frequency domain resource allocation) field, a field for indicating a Transmission Comb, a field for indicating a Usage for the SRS, a field for indicating the number of ports for the SRS, or a field for indicating a TCI (transmission configuration indicator) status for the SRS.

7. In Paragraph 5, The method further includes the step of transmitting a second DCI to the above UE, the second DCI including a request to trigger the transmission of the above SRS, and The above second DCI is transmitted prior to the above first DCI, a method.

8. In Paragraph 5, The first DCI above includes information for indicating an identification method for a first field included in the first DCI, or A method in which the first DCI indicates an identification method for the first field by a combination of at least one field included in the first DCI.

9. Regarding UE (user equipment): At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the UE: Receive a first DCI (downlink control information) from a base station that includes first information associated with the scheduling of an SRS (sounding reference signal), and A UE that causes the base station to transmit the SRS based on the first DCI.

10. In Paragraph 9, The above first information comprises at least one of a TDRA (time domain resource allocation) field, an FDRA (frequency domain resource allocation) field, a field for indicating a Transmission Comb, a field for indicating a Usage for the SRS, a field for indicating the number of ports for the SRS, or a field for indicating the TCI (transmission configuration indicator) status for the SRS, a UE.

11. In Paragraph 9, The above commands are the above UE: To receive a second DCI from the above base station that includes a request to trigger the transmission of the SRS, and The above second DCI is a UE received prior to the above first DCI.

12. In Paragraph 9, The first DCI above includes information for indicating an identification method for a first field included in the first DCI, or The above first DCI indicates an identification method for the first field by a combination of at least one field included in the above first DCI, UE.

13. Regarding base stations: At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the base station: Transmitting a first DCI (downlink control information) containing first information related to the scheduling of an SRS (sounding reference signal) to a UE (user equipment), and A base station that receives the SRS transmitted from the above UE based on the above first DCI.

14. In Paragraph 13, A base station comprising at least one of the above first information, a TDRA (time domain resource allocation) field, an FDRA (frequency domain resource allocation) field, a field for indicating a Transmission Comb, a field for indicating a Usage for the SRS, a field for indicating the number of ports for the SRS, or a field for indicating a TCI (transmission configuration indicator) status for the SRS.

15. In Paragraph 13, The above commands are the above base station: To transmit a second DCI to the above UE, which includes a request to trigger the transmission of the above SRS, and The above second DCI is transmitted prior to the above first DCI, and The first DCI above includes information for indicating an identification method for a first field included in the first DCI, or A base station in which the first DCI indicates an identification method for the first field by a combination of at least one field included in the first DCI.

Images