Method for extending triggering flexibility of non-periodic sounding reference signals - Patents.com

Abstract

The wireless communication method of the terminal includes a step of receiving configuration information including a parameter via downlink control information (DCI) or higher layer signaling, a step of configuring an aperiodic sounding reference signal (A-SRS) transmission based on the parameter, and a step of reporting capability information including a minimum timing requirement between an A-SRS triggering physical downlink control channel (PDCCH) and an SRS resource in a resource set based on a usage setting.

Description

[Technical field]

[0001] One or more embodiments disclosed herein relate to a mechanism(s) how aperiodic Sounding Reference Signal (SRS) triggering can be enhanced by introducing additional flexibility. [Background technology]

[0002] In 5G New Radio (NR) technology, new requirements have been identified for further enhancement of SRS transmission. New items in Rel. 17 relate, for example, to NR Multiple-Input-Multiple-Output (MIMO).

[0003] New ongoing research is targeted at SRS extensions in both frequency band (FR) 1 and FR 2. In particular, it is being considered to identify and specify extensions for aperiodic SRS triggering to facilitate more flexible triggering and / or reduced downlink control information (DCI) overhead / usage.

[0004] It is also under consideration to specify SRS switching for up to 8 antennas (e.g., xTyR, x={1,2,4}, y={6,8}).Furthermore, it is under consideration to evaluate and, if necessary, specify mechanisms to extend SRS capacity and / or coverage, including SRS time bundling, increased SRS repetition, and / or partial sounding across frequency. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP RP 193133, “New WID: Further enhancements on MIMO for NR”, December 2019 [Non-Patent Document 2] 3GPP RAN1 #103-e, 'Chairman's Notes', November 2020 [Non-Patent Document 3] 3GPP RAN1 #104-e, 'Chairman's Notes', February 2021 [Non-Patent Document 4] 3GPP TS 38.214, “NR; Physical procedures for data (Release 16)” [Non-Patent Document 5] 3GPP, TS 38.212, “NR; Multiplexing and channel coding (Release 16)” [Non-Patent Document 6] 3GPP TS 38.331, “NR; Radio Resource Control; Protocol specification (Release 15)” Summary of the Invention

[0006] In general, in one aspect, the embodiments disclosed herein include a transmitter that reports capability information regarding a minimum timing requirement between a physical downlink control channel (PDCCH) that triggers an aperiodic sounding reference signal (A-SRS) transmission and an SRS resource in an SRS resource set; a receiver that receives downlink control information (DCI) indicating slots available for the A-SRS transmission after a reference slot indicated by a trigger offset indicating an offset between a slot for receiving the PDCCH and a reference slot for the A-SRS transmission; and a controller that controls the A-SRS transmission based on a DCI field indicating slots available for the A-SRS transmission, the DCI field being included in the DCI. The DCI indicates a (t+1)th slot available for the A-SRS transmission, counting from the reference slot indicated by the trigger offset, and a list of t values ​​is configured by a Radio Resource Control (RRC) for each SRS resource set, and one t value is selected from the list by the DCI field, and the DCI field exists only when configured by the RRC. , relating to the terminal.

[0007] In general, in one aspect, embodiments disclosed herein include reporting capability information regarding a minimum timing requirement between a physical downlink control channel (PDCCH) that triggers an aperiodic sounding reference signal (A-SRS) transmission and an SRS resource in an SRS resource set; receiving downlink control information (DCI) indicating available slots for the A-SRS transmission after a reference slot indicated by a trigger offset indicating an offset between a slot for receiving the PDCCH and a reference slot for the A-SRS transmission; and controlling the A-SRS transmission based on a DCI field indicating available slots for the A-SRS transmission, the DCI field being included in the DCI. The DCI indicates a (t+1)th slot available for the A-SRS transmission, counting from the reference slot indicated by the trigger offset, and a list of t values ​​is configured by a Radio Resource Control (RRC) for each SRS resource set, and one t value is selected from the list by the DCI field, and the DCI field exists only when configured by the RRC. The present invention relates to a wireless communication method for a terminal.

[0008] In general, in one aspect, the embodiments disclosed herein include a receiver for receiving capability information relating to a minimum timing requirement between a physical downlink control channel (PDCCH) for triggering an aperiodic sounding reference signal (A-SRS) transmission and an SRS resource in an SRS resource set, and a transmitter for transmitting downlink control information (DCI) indicating slots available for the A-SRS transmission after a reference slot indicated by a trigger offset indicating an offset between a slot for receiving the PDCCH and a reference slot for the A-SRS transmission, the DCI being transmitted based on a DCI field indicating slots available for the A-SRS transmission, the DCI being included in the DCI. The DCI indicates a (t+1)th slot available for the A-SRS transmission, counting from the reference slot indicated by the trigger offset, and a list of t values ​​is configured by a Radio Resource Control (RRC) for each SRS resource set, and one t value is selected from the list by the DCI field, and the DCI field exists only when configured by the RRC. This relates to a base station.

[0009] Other embodiments and advantages of the present invention will be apparent from the following description and drawings. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing a schematic configuration of a wireless communication system according to an embodiment. [Diagram 2]FIG. 1 illustrates a schematic configuration of a base station (BS), according to one or more embodiments. [Diagram 3] 1 illustrates a schematic configuration of a user equipment (UE) according to one or more embodiments. [Figure 4] An overview of potential extensions for aperiodic SRS triggering is given. [Diagram 5] 1 shows an example table of PUSCH preparation times. [Figure 6] 1 shows an example of a DCI field. [Figure 7] 1 shows an example of a DCI field. [Figure 8] 13 shows an example of higher layer parameters. [Figure 9] 13 shows an example of a table in which the number of DCI codepoints for A-SRS triggering conditions is expanded. [Figure 10] 13 shows an example of higher layer parameters. [Figure 11] 13 shows an example of higher layer parameters. [Figure 12] 13 shows an example of a table in which the number of DCI codepoints for A-SRS triggering conditions is expanded. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings, in which like elements in different drawings are designated with like reference numerals to maintain consistency.

[0012] In the following description of the embodiments of the present invention, numerous specific details are set forth in order to provide a more thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention can be practiced without these specific details. In other instances, well-known features are not described in detail to avoid obscuring the present invention.

[0013] 1 illustrates a wireless communication system 1 according to one or more embodiments of the present invention. The wireless communication system 1 includes a user equipment (UE) 10, a base station (BS) 20, and a core network 30. The wireless communication system 1 may be an NR system. The wireless communication system 1 is not limited to the specific configuration described herein, and may be any type of wireless communication system, such as an LTE / LTE-Advanced (LTE-A) system.

[0014] The BS 20 may communicate uplink (UL) and downlink (DL) signals with the UEs 10 in the cell of the BS 20. The DL and UL signals may include control information and user data. The BS 20 may communicate the DL and UL signals with the core network 30 via a backhaul link 31. The BS 20 may be a gNodeB (gNB). The BS 20 may be referred to as a network (NW).

[0015] The BS 20 includes an antenna, a communication interface (e.g., an X2 interface) for communicating with neighboring BSs 20, a communication interface (e.g., an S1 interface) for communicating with the core network 30, and a central processing unit (CPU) such as a processor or circuit for processing signals transmitted to and received from the UE 10. The operation of the BS 20 may be realized by the processor processing or executing data and programs stored in a memory. However, the BS 20 is not limited to the above hardware configuration, and may be realized by any other suitable hardware configuration as will be understood by those skilled in the art. A large number of BSs 20 may be deployed to cover a wider service area of ​​the wireless communication system 1.

[0016] The UE 10 may communicate DL signals and UL signals including control information and user data with the BS 20 using a multiple input multiple output (MIMO) technology. The UE 10 may be an information processing device having a wireless communication function, such as a mobile station, a smartphone, a mobile phone, a tablet, a mobile router, or a wearable device. The wireless communication system 1 may include one or more UEs 10.

[0017] The UE 10 includes a CPU, e.g., a processor, a RAM (Random Access Memory), a flash memory, and a wireless communication device for transmitting and receiving wireless signals between the BS 20 and the UE 10. For example, the operation of the UE 10 described below may be realized by the CPU processing or executing data and programs stored in the memory. However, the UE 10 is not limited to the above hardware configuration, and may be configured to include, for example, a circuit for realizing the processing described below.

[0018] 1, the BS 20 may transmit a CSI reference signal (CSI-RS) to the UE 10. In response, the UE 10 may transmit a CSI report to the BS 20. Similarly, the UE 10 may transmit an SRS to the BS 20.

[0019] (BS composition)

[0020] Hereinafter, the BS 20 according to the embodiment of the present invention will be described with reference to Fig. 2. Fig. 2 is a diagram for explaining a schematic configuration of the BS 20 according to the embodiment of the present invention, and the BS 20 may include a plurality of antennas (antenna element group) 201, an amplifier unit 202, a transceiver unit (transmitter / receiver) 203, a baseband signal processor 204, a call processor 205, and a transmission path interface 206.

[0021] User data transmitted in DL from the BS 20 to the UE 10 is input to the baseband signal processing unit 204 from the core network via the transmission path interface 206 .

[0022] In the baseband signal processing unit 204, the signals are subjected to Packet Data Convergence Protocol (PDCP) layer processing, division and joining of user data, RLC layer transmission processing such as Radio Link Control (RLC) retransmission control transmission processing, Medium Access Control (MAC) retransmission control including HARQ transmission processing, scheduling, transmission format selection, channel coding, Inverse Fast Fourier Transform (IFFT) processing, precoding processing, etc. Subsequently, the resulting signals are transferred to each transceiver unit 203. As for the DL control channel signal, transmission processing including channel coding and inverse fast Fourier transform is performed, and the resulting signals are transferred to each transceiver unit 203.

[0023] The baseband signal processing unit 204 notifies each UE 10 of control information (system information) for communication within the cell by higher layer signaling (e.g., RRC (Radio Resource Control) signaling and a broadcast channel). The information for communication within the cell includes, for example, a UL system bandwidth or a DL system bandwidth.

[0024] In each transmitting / receiving unit 203, precoding is performed for each antenna, and a frequency conversion process to a radio frequency band is performed on the baseband signal output from the baseband signal processing unit 204. The amplifier unit 202 amplifies the radio frequency signal that has been frequency converted, and the resulting signal is transmitted from the antenna 201.

[0025] With regard to data transmitted on the UL from UE 10 to BS 20, a radio frequency signal is received by each antenna 201, amplified by amplifier section 202, frequency-converted in transceiver section 203 and converted into a baseband signal, and input to baseband signal processing section 204.

[0026] The baseband signal processor 204 performs FFT processing, IDFT processing, error correction decoding processing, MAC retransmission control reception processing, and RLC layer and PDCP layer reception processing on user data contained in the received baseband signal. The resulting signal is then transferred to the core network via the transmission path interface 206. The call processor 205 performs call processing such as setting up and releasing communication channels, manages the state of the BS 20, and manages radio resources.

[0027] (UE configuration) Hereinafter, a UE 10 according to an embodiment of the present invention will be described with reference to Fig. 3. Fig. 3 shows a schematic configuration of the UE 10 according to the embodiment of the present invention. The UE 10 has a plurality of UE antennas 101, an amplifier unit 102, a circuit 103 including a transceiver unit (transmitter / receiver) 1031, a controller 104, and an application unit 105.

[0028] For DL, radio frequency signals received at the UE antenna 101 are amplified in each amplifier unit 102, and frequency converted to baseband signals in the transmission / reception unit 1031. The control unit 104 performs reception processing such as FFT processing, error correction decoding, and retransmission control on these baseband signals. DL user data is transferred to the application unit 105. The application unit 105 performs processing related to layers higher than the physical layer and MAC layer. In the downlink data, broadcast information is also transferred to the application unit 105.

[0029] On the other hand, UL user data is input from the application unit 105 to the control unit 104. In the control unit 104, retransmission control (Hybrid ARQ) transmission processing, channel coding, precoding, DFT processing, IFFT processing, etc. are performed, and the resulting signals are transferred to each transmission / reception unit 1031. In the transmission / reception unit 1031, the baseband signal output from the control unit 104 is converted into a radio frequency band. Thereafter, the frequency-converted radio frequency signal is amplified in the amplifier unit 102 and then transmitted from the antenna 101.

[0030] One or more embodiments of the present invention, referring to Fig. 4, relate to an extension of aperiodic SRS triggering. In particular, as described in [2], the following may be considered: A given aperiodic SRS resource set may be transmitted in the (t+1)th available slot counting from a reference slot, where t is indicated by DCI or RRC (if only one value of t is configured in RRC), and the possible values ​​of t include at least 0. Furthermore, one or more of the following options for the reference slot may be considered: As one option, the reference slot is the slot with the trigger DCI. As another option, the reference slot is the slot indicated by a legacy trigger offset.

[0031] A definition of "available slot" is also considered that takes into account the UE processing complexity and timelines for determining the available slots, as well as potential coexistence with collision processing. Based on RRC configuration only, an "available slot" is a slot where there is a UL or flexible symbol for the time domain positions for all SRS resources in a resource set and meets the minimum timing requirements between the trigger PDCCH and all SRS resources in the resource set.

[0032] It is also considered whether it would be useful to indicate t explicitly or implicitly, and whether it would be useful to update the candidate triggering offset in the MAC CE.

[0033] As mentioned above, SRS extensions are considered. In one or more embodiments described herein, UE capabilities with respect to minimum timing requirements are taken into account. First, an "available slot" may be considered as a slot that satisfies the condition that for all SRS resources in a resource set, there is a UL symbol(s) or flexible symbol(s) at a time domain position(s) , and may also be considered as a slot that satisfies the UE capabilities with respect to the minimum timing requirement between the triggering PDCCH and all SRS resources in a resource set.

[0034] In one or more embodiments, as part of the capability report, the UE reports a minimum timing requirement between the A-SRS triggering PDCCH and all SRS resources in the resource set. The reported timing requirement can then be considered to be the following in order to determine the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource:

[0035] The UE may consider, as part of its capabilities, a minimum timing requirement to be reported as N3 symbols. In this case, this minimum timing requirement may be considered to specify a minimum time interval as follows:

[0036] Consider an example where the usage of the SRS resource set is set to "codebook" or "antenna switching."

[0037] As a first option for SRS in resource sets with usage set to “codebook” or “antennaSwitching”, the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is N3 symbols plus an additional time T switch It is.

[0038] As a second option for SRS in resource sets with usage set to “codebook” or “antennaSwitching”, the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is N2+N3 symbols and an additional time T switch It is.

[0039] As a third option for SRS in resource sets with usage set to “codebook” or “antennaSwitching”, the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is Max{N2,N3} symbols and an additional time T switch It is.

[0040] Next, an example will be described in which the usage is set to "non-codebook" or "Beam Management".

[0041] As a first option for SRS in resource sets with usage set to “non-codebook” or “Beam Management”, the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is N3+14 symbols plus an additional time T switch It is.

[0042] As a second option for SRS in resource sets with usage set to “non-codebook” or “Beam Management”, the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is N2+N3+14 symbols plus an additional time T switch It is.

[0043] As a third option for SRS in resource sets with usage set to “non-codebook” or “Beam Management”, the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is Max{N2,N3}+14 symbols and an additional time T switch It is.

[0044] In one or more embodiments, regardless of the "usage" of the SRS, the minimum timing requirement may be defined as, for example, Max{existing minimum time for usage, N3}. In this scenario, "codebook", "antennaSwitching", and "existing minimum time for usage" may be defined as N2. "non-codebook" and "BeamManagement", and "existing minimum time for usage" may be defined as N2+14.

[0045] Furthermore, one or more values ​​of N2 may be set as follows:

[0046] In the first option, the value of N2 can be predefined in the specification. An example given in [4] for N2 being predefined in the specification is shown in Figure 5.

[0047] As a second option, one or more values ​​of N2 are reported by the UE as part of its UE capabilities.

[0048] It is noted that the minimum timing requirement may be "the last symbol of the PDCCH and the first symbol of the SRS resource that triggers the aperiodic SRS transmission." It is further noted that the SRS resource may be the first transmitted SRS resource in the triggered SRS resource set.

[0049] Furthermore, if the UE does not report a minimum timing requirement between the A-SRS triggering PDCCH and all SRS resources in a resource set, the minimum timing requirement may be predefined in the specification. For example, the minimum timing between the triggering PDCCH and all SRS resources in a resource set may be defined as follows:

[0050] For SRS in a resource set with usage set to “codebook” or “antennaSwitching”, the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is N2 symbols plus an additional time T switch It is.

[0051] For SRS in a resource set whose usage is set to "non-codebook" or "Beam Management", the minimum time interval between the last symbol of the PDCCH that triggers aperiodic SRS transmission and the first symbol of the SRS resource is N2+14 symbols plus an additional time T switch It is.

[0052] In one or more embodiments, the value of N2 may be predefined in the specification, as shown in FIG.

[0053] In one or more embodiments of DCI / PDCCH detection, the UE may attempt a blind detection (BD) of the DCI format. In a first step, the UE may assume one possible DCI size of the possible DCI formats and may assume a possible aggregation level of the PDCCH. Furthermore, the UE demodulates the PDCCH and attempts a CRC check, where the CRC is scrambled by some Radio Network Temporary Identifier (RNTI) (e.g., C-RNTI, etc.).

[0054] If the CRC check passes, the UE knows that the DCI has been properly received, otherwise the UE goes back to the first step and assumes another possible DCI size and aggregation level, and another demodulation attempt is made, followed by another CRC check.

[0055] Therefore, as the number of possible (i.e., different) DCI sizes increases, the number of blind detections (BDs) for the PDCCH increases as well, which may have a significant impact on UE complexity. As a result, in one or more embodiments, it may be important, e.g., from a complexity perspective, to maintain the same number of BDs as in Rel. 15 / 16.

[0056] One or more embodiments relate to indicating the parameter t using DCI format 0_1 / 0_2. For example, a list of t values ​​may be configured in RRC for each SRS resource set. Then, one value from the list is selected using DCI [3].

[0057] As a first option with reference to Fig. 6, a new configurable DCI field may be added to indicate the t value. In particular, Fig. 6 shows an example of a newly added DCI field indicating t. It should be noted that within the same DCI format, the size of the DCI payload does not change for A-SRS triggering, regardless of the presence or absence of data / CSI. This is beneficial to avoid increasing the number of BDs for DCI. It should also be noted that the new DCI field may only be present if RRC configures it.

[0058] As a second option with reference to Fig. 7, the t value is indicated without adding a new DCI field. In that case, DCI with data / CSI scheduling and DCI without data / CSI scheduling can indicate the t value in different manners. In the case of DCI without data / CSI, an unused field may be reused to indicate the t value. In the case of data / CSI and SRS request, the following methods may be considered to indicate t:

[0059] 1) The UE may only expect a single value of t to be configured by higher layers for each SRS resource set.

[0060] 2) The UE may select one value (e.g., a first value, a minimum value, a maximum value, etc.) of multiple values ​​for t set by a higher layer from a list of values ​​based on one or more rules predefined in a specification or based on a setting by a higher layer (e.g., setting a default value for t).

[0061] As mentioned above, in the case of DCI without data / CSI, unused fields may be reused. For example, the unused DCI fields in DCI without data / CSI may be "DCI fields used for PUSCH scheduling and / or CSI request". In particular, one or more of the unused DCI fields in DCI format 0_1 / 0_2 without scheduling data / CSI may be considered to indicate the t value according to the second option. One or more examples of some potentially unused DCI fields that may be considered to indicate t may include: Bandwidth Part Indicator Frequency domain resource allocation Time domain resource allocation TPC commands for scheduled PUSCH Precoding information and number of layers Antenna port CSI Request

[0062] Returning to the first option, it should be noted that the new DCI field may only be present if the RRC has configured it. For example, a new RRC parameter srs-DCI-t-Field-r17, as shown in FIG. 8, which configures the availability of the new DCI field for indicating the t value, is considered. In this example, if srs-DCI-t-Field-r17 is set to 0, the method considered in the second option can be considered for indicating the t value. If srs-DCI-t-Field-r17 is set to 1, the method considered in the first option can be considered for indicating the t value.

[0063] It should further be noted that when the above mentioned higher layer parameters are configured (i.e. according to the first option), the new DCI field can dynamically indicate the value of t for both cases of DCI for A-SRS triggering with data / CSI and DCI for A-SRS triggering without data / CSI. Alternatively (i.e. according to the second option), the existing DCI field not used for data scheduling and / or CSI request can dynamically indicate the value of t for the case of DCI for A-SRS triggering without data / CSI, and the value of t is semi-statically configured for the case of DCI for A-SRS triggering with data / CSI.

[0064] In one or more embodiments, the number of DCI code points for A-SRS trigger states may be expanded. Currently, the number of DCI code points available for A-SRS trigger states is only three. To support more than three trigger states, Table 7.3.1.1.2-24 of the specification in [5] may be appropriately updated to include more code points, as shown in FIG. 9. In particular, to allow for seven trigger states for A-SRS, as shown in FIG. 9, assuming a bit width of three bits for the SRS request field, Table 7.3.1.1.2-24 in [5] may be updated as shown. For example, new entries may be defined for 100, 101, 110, and 111.

[0065] Furthermore, to flexibly control the DCI overhead, it is possible to configure the size of the "SRS request" field using RRC signaling. Then, based on the configured size of the "SRS request" field, a specific row can be selected from Table 7.3.1.1.2-24 in [5], as shown in Figure 9. For example, when seven trigger states of A-SRS are possible (as shown in Figure 9), the size of the SRS request field can be configured by higher layers. In particular, an example of the configuration of the SRS field size by higher layers is shown in Figure 10.

[0066] srs-RequestDCI-0-2 is defined as follows:

[0067] Indicates the number of bits of "SRS request" in DCI format 0_2. If this field is not present, the value of 0 bit of "SRS request" in DCI format 0_2 applies. If the parameter srs-RequestDCI-0-2 is set to value 1, for a triggered aperiodic SRS resource set, 1 bit is used to indicate one of the first two rows of Table 7.3.1.1.2-24 in TS 38.212. If the value is set to value 2, 2 bits are used to indicate one of the first four rows of Table 7.3.1.1.2-24 in TS 38.212. If the value is set to value 3, 3 bits are used to indicate one of the rows of Table 7.3.1.1.2-24 in TS 38.212. If the UE is configured with supplementaryUplink, an additional bit (i.e. the first bit of the SRS request field) is used to indicate non-SUL / SUL.

[0068] It should be noted that in Rel.16, the above upper layer parameters are introduced to control the DCI payload of DCI format 0_2 (i.e., referred to as compact DCI, compared with DCI format 0_1 ​​of Rel.15). The above proposal is also applicable to DCI format 0_1. A simple method is to define different upper layer parameters (i.e., the above upper layer parameters) to separately control the size of the SRS request field of DCI format 0_1 ​​and the size of the SRS request field of DCI format 0_2. Another method is to specify only the upper layer parameters (i.e., the above upper layer parameters) to control the size of the SRS request field for DCI format 0_2, and the DCI size of the SRS request field for DCI format 0_1 ​​is derived according to an implicit rule (e.g., the number of SRS resource sets whose usage is CB / NCB).

[0069] Furthermore, to support the newly added A-SRS trigger states, the RRC parameters maxNrofSRS-TriggerStates-1 and maxNrofSRS-TriggerStates-2 are updated in aperiodicSRS-ResourceTrigger and aperiodicSRS-ResourceTriggerList of [6], respectively, as shown in Figure 11. For example, if there are seven possible trigger states for A-SRS, then maxNrofSRS-TriggerStates-1 and maxNrofSRS-TriggerStates-2 need to be updated as shown by the updated values ​​in Figure 11.

[0070] As another option, the UE may select an appropriate table of A-SRS triggering states depending on whether the DCI schedules data / CSI or not. That is, for DCIs without scheduling data / CSI, the size of the SRS request field is 1, 2 or 3 bits. As shown in Figure 9, for DCIs without data / CSI, higher layers may configure which entries to consider from the A-SRS triggering state table, i.e., Table 7.3.1.1.2-24 in [5]. Following this example, Figure 10 shows new RRC parameters that may be applied only for DCIs without scheduling data / CSI. As mentioned above, a table for capturing the A-SRS triggering states in this scenario is shown in Figure 9.

[0071] For DCI scheduling data / CSI, the size of the SRS request field is 1 or 2 bits. Therefore, the table shown in Figure 12 may be considered in a scenario where DCI scheduling includes data / CSI.

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

[0073] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

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

[0075] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI)), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (master information block (MIB), system information block (SIB), medium access control (MAC) signaling, etc.), other signals, or a combination of these.

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

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

[0078] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0079] In this disclosure, the terms "base station (BS)", "radio base station", "eNB", "gNB", "cell", "sector", "cell group", "carrier", "component", and "component carrier" may be used interchangeably. A base station may be called a "fixed station", "NodeB", "eNodeB (eNB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "femtocell", "small cell", and the like.

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

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

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

[0083] Furthermore, a radio base station in the present disclosure may be interpreted as a user terminal. For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a radio base station and a user terminal is replaced with communication between multiple user terminals (e.g., D2D (Device-to-Device)). In this case, the user terminal 20 may have the functions of the radio base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be interpreted as "side." For example, an uplink channel may be interpreted as a side channel.

[0084] Similarly, a user terminal in the present disclosure may be interpreted as a radio base station. In this case, the radio base station may have the functions of the above-mentioned user terminal.

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

[0086] One or more embodiments described in this disclosure may be used alone, in combination, or switched in execution. In addition, the order of the process steps, sequences, flow charts, etc. used to describe aspects / embodiments in this disclosure may be changed as long as there is no contradiction. For example, the various methods described in this disclosure present elements of various steps using an example order, but are not limited to the particular order presented therein.

[0087] One or more embodiments described in the present disclosure may be applied to systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), New-RAT (Radio Access Technology), NR (New Radio), NX (New radio access), FX (Future generation radio access), GSM (Global System for Mobile communications), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), other suitable wireless communication methods, and / or next generation systems enhanced based on these.

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

[0089] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0090] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be "judging," calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, etc. Also, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc. Additionally, "determination" as used in this disclosure may be interpreted as "determining" resolving, selecting, choosing, assuming, establishing, comparing, etc. In other words, "determination" may be interpreted as "deciding" to perform some action.

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

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

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

[0094] Furthermore, the term "or" as used in the specification or claims is not intended to be an exclusive or.

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

[0096] Another example The above embodiments and modifications may be combined with each other, and the various features of the embodiments may be combined with each other in various combinations, and the invention is not limited to the specific combinations disclosed herein.

[0097] While the present disclosure has been described with respect to only a limited number of embodiments, it will be apparent to those skilled in the art, having the benefit of this disclosure, that various other embodiments may be devised without departing from the scope of the invention, which scope should therefore be limited only by the scope of the appended claims.

Claims

1. a transmitter for reporting capability information regarding a minimum timing requirement between a physical downlink control channel (PDCCH) that triggers an aperiodic sounding reference signal (A-SRS) transmission and an SRS resource in an SRS resource set; A receiving unit that receives downlink control information (DCI) indicating a slot available for the A-SRS transmission after a reference slot indicated by a trigger offset indicating an offset between a slot for receiving the PDCCH and a reference slot for the A-SRS transmission; A control unit that controls the A-SRS transmission based on a DCI field indicating a slot available for the A-SRS transmission, the DCI being included in the DCI; The DCI indicates a (t+1)-th slot available for the A-SRS transmission, counting from the reference slot indicated by the trigger offset, and a list of t values ​​is configured by a Radio Resource Control (RRC) for each SRS resource set, and one t value is selected from the list by the DCI field; A terminal, wherein the DCI field is present only if configured by the RRC.

2. 2. The terminal of claim 1, wherein the slots available for A-SRS transmission are slots in which an uplink (UL) symbol or a flexible symbol exists for time domain positions for all SRS resources in the SRS resource set and the minimum timing requirement is met.

3. reporting capability information regarding a minimum timing requirement between a physical downlink control channel (PDCCH) that triggers an aperiodic sounding reference signal (A-SRS) transmission and an SRS resource in an SRS resource set; receiving downlink control information (DCI) indicating slots available for the A-SRS transmission after a reference slot indicated by a trigger offset indicating an offset between a slot for receiving the PDCCH and a reference slot for the A-SRS transmission; and controlling the A-SRS transmission based on a DCI field indicating an available slot for the A-SRS transmission, the DCI field being included in the DCI; The DCI indicates a (t+1)-th slot available for the A-SRS transmission, counting from the reference slot indicated by the trigger offset, and a list of t values ​​is configured by a Radio Resource Control (RRC) for each SRS resource set, and one t value is selected from the list by the DCI field; A wireless communication method for a terminal, wherein the DCI field exists only when configured by the RRC.

4. a receiving unit for receiving capability information regarding a minimum timing requirement between a physical downlink control channel (PDCCH) that triggers an aperiodic sounding reference signal (A-SRS) transmission and an SRS resource in an SRS resource set; A transmitter that transmits downlink control information (DCI) indicating slots available for the A-SRS transmission after the reference slot indicated by a trigger offset indicating an offset between a slot for receiving the PDCCH and a reference slot for the A-SRS transmission, The receiver receives the A-SRS transmission, the A-SRS transmission being transmitted based on a DCI field indicating an available slot for the A-SRS transmission, the DCI field being included in the DCI; The DCI indicates a (t+1)-th slot available for the A-SRS transmission, counting from the reference slot indicated by the trigger offset, and a list of t values ​​is configured by a Radio Resource Control (RRC) for each SRS resource set, and one t value is selected from the list by the DCI field; A base station, wherein the DCI field is present only if configured by the RRC.

5. A system having a terminal and a base station, The terminal includes a first transmitter configured to report capability information regarding a minimum timing requirement between a physical downlink control channel (PDCCH) that triggers an aperiodic sounding reference signal (A-SRS) transmission and an SRS resource in an SRS resource set; A first receiving unit that receives downlink control information (DCI) indicating a slot available for the A-SRS transmission after a reference slot indicated by a trigger offset indicating an offset between a slot for receiving the PDCCH and a reference slot for the A-SRS transmission; A control unit that controls the A-SRS transmission based on a DCI field indicating a slot available for the A-SRS transmission, the DCI being included in the DCI; The base station includes a second receiving unit that receives the capability information; a second transmitter for transmitting the DCI; The second receiving unit receives the A-SRS transmission, which is transmitted based on the DCI field included in the DCI; The DCI indicates a (t+1)-th slot available for the A-SRS transmission, counting from the reference slot indicated by the trigger offset, and a list of t values ​​is configured by a Radio Resource Control (RRC) for each SRS resource set, and one t value is selected from the list by the DCI field; The DCI field is only present if configured by the RRC.

Images