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

By using configuration information and DCI to set consistent slot offsets for SRS resource sets, the method improves SRS transmission efficiency and clarity, meeting the demands of advanced wireless communication systems for high data traffic and low latency.

JP7736922B2Active Publication Date: 2025-09-09LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024519020
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-09-29
Filing Date
2022-09-29
Publication Date
2025-09-09
Estimated Expiration
2042-09-29

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing and transmitting sounding reference signals (SRS) due to resource shortages and the need for faster, more advanced mobile communication systems that support large data traffic, increased transmission rates, and low latency.

Method used

A method and apparatus for transmitting and receiving SRS based on configuration information and downlink control information (DCI), which includes setting the same number of slot offsets for multiple SRS resource sets to eliminate ambiguity in slot offset indications.

Benefits of technology

This approach enhances the clarity and efficiency of SRS transmission and reception, addressing resource management issues and supporting advanced communication requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007736922000016
    Figure 0007736922000016
  • Figure 0007736922000017
    Figure 0007736922000017
  • Figure 0007736922000018
    Figure 0007736922000018
Patent Text Reader

Abstract

A method and apparatus for transmitting and receiving an SRS in a wireless communication system are disclosed. The method for transmitting and receiving an SRS according to an embodiment of the present disclosure includes receiving configuration information related to an SRS from a base station, receiving DCI from the base station, and transmitting the SRS based on the DCI, where the configuration information includes information for configuring at least one available slot offset for each of at least one SRS resource set, and a number of the at least one available slot offset configured for each of the at least one SRS resource set may be the same.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems, and more particularly to methods and apparatus for transmitting and receiving sounding reference signals (SRS) in wireless communication systems. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to include data services, and the explosive growth in traffic is causing resource shortages. Users are also demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The requirements for next-generation mobile communication systems are to accommodate large and explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, support very low end-to-end latency, and high energy efficiency.To achieve this, various technologies are being researched, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking. Summary of the Invention [Problem to be solved by the invention]

[0004] A technical problem of the present disclosure is to provide a method and apparatus for transmitting and receiving a sounding reference signal.

[0005] Another technical object of the present disclosure is to provide a method and apparatus for transmitting and receiving an aperiodic sounding reference signal based on an SRS request field and / or a slot offset indication field included in downlink control information (DCI).

[0006] The technical problems to be solved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0007] As one embodiment of the present disclosure, a method for transmitting a sounding reference signal (SRS) in a wireless communication system includes the steps of receiving configuration information related to an SRS from a base station, receiving downlink control information (DCI) from the base station, and transmitting the SRS based on the DCI, wherein the configuration information includes information for configuring at least one available slot offset for each of at least one SRS resource set, and the number of the at least one available slot offset configured for each of the at least one SRS resource set may be the same.

[0008] As one embodiment of the present disclosure, a method for a base station in a wireless communication system receiving a sounding reference signal (SRS) includes the steps of transmitting configuration information related to the SRS to a terminal, transmitting downlink control information (DCI) to the terminal, and receiving the SRS based on the DCI from the terminal, wherein the configuration information includes information for configuring at least one available slot offset for each of at least one SRS resource set, and the number of the at least one available slot offset configured for each of the at least one SRS resource set may be the same. [Effects of the Invention]

[0009] According to an embodiment of the present disclosure, a method and apparatus for transmitting and receiving a sounding reference signal can be provided.

[0010] Furthermore, according to an embodiment of the present disclosure, a method and apparatus for transmitting and receiving an aperiodic sounding reference signal based on an SRS request field and / or a slot offset indication field included in a DCI may be provided.

[0011] In addition, according to one embodiment of the present disclosure, the same number of slot offset values ​​are set for multiple SRS resource sets linked to code points included in the SRS request field, thereby eliminating ambiguity related to slot offset indication.

[0012] The effects that can be obtained by the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief explanation of the drawings]

[0013] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples of the present disclosure and, together with the detailed description, explain the technical features of the present disclosure.

[0014] [Figure 1] 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0015] [Figure 2] 1 illustrates an example of a frame structure in a wireless communication system to which the present disclosure can be applied.

[0016] [Figure 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied.

[0017] [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied.

[0018] [Figure 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied.

[0019] [Figure 6] 1 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0020] [Figure 7] FIG. 10 is a diagram illustrating an operation of a terminal for transmitting and receiving a sounding reference signal according to an embodiment of the present disclosure.

[0021] [Figure 8] FIG. 10 is a diagram illustrating the operation of a base station for transmitting and receiving a sounding reference signal according to one embodiment of the present disclosure.

[0022] [Figure 9] FIG. 10 is a diagram for explaining a signaling procedure between a network side and a terminal according to an embodiment of the present disclosure.

[0023] [Figure 10] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0024] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it will be understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0025] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or shown in block diagram form, focusing on the core functions of each structure and device.

[0026] In this disclosure, when a component is "coupled," "coupled," or "connected" to another component, this may include a direct connection as well as an indirect connection where there are other components between them. Also, in this disclosure, the terms "comprise" or "have" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0027] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another, not to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0028] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be used, or that any and all possible combinations of two or more of them may be used. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0029] The present disclosure is described with respect to a wireless communication network or a wireless communication system, and operations performed in a wireless communication network may be performed in the process in which a device (e.g., a base station) that manages the wireless communication network controls the network and transmits or receives signals, or in the process in which a terminal coupled to the wireless network transmits or receives signals to or from the network or between terminals.

[0030] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0031] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In the downlink, a transmitter may be part of the base station, and a receiver may be part of the terminal. In the uplink, a transmitter may be part of the terminal, and a receiver may be part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, evolved-Node B (eNB), Next Generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), artificial intelligence (AI) system / module, road side unit (RSU), robot, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc. Furthermore, a terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0032] The following technologies may be used for various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA may be implemented by radio technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project)® LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0033] For clarity, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical concept of the present disclosure is not limited thereto. LTE refers to technology from 3GPP Technical Specification (TS) 36.xxx Release 8 onward. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onward is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onward is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onward. LTE / NR may be referred to as a 3GPP system. "xxx" refers to the standard document detail number. LTE / NR may be referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, please refer to the matters described in standard documents published before the present disclosure. For example, the following documents may be referenced:

[0034] In 3GPP LTE, reference can be made to TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

[0035] For 3GPP NR, reference can be made to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Standard).

[0036] The terminology abbreviations that may be used in this disclosure are defined as follows:

[0037] - BM: Beam management

[0038] - CQI: Channel Quality Indicator

[0039] - CRI: Channel state information-reference signal resource indicator

[0040] - CSI: Channel State Information

[0041] - CSI-IM: Channel state information-interference measurement

[0042] - CSI-RS: Channel state information-reference signal

[0043] - DMRS: Demodulation Reference Signal

[0044] - FDM: Frequency Division Multiplexing

[0045] - FFT: Fast Fourier transform

[0046] - IFDMA: Interleaved frequency division multiple access

[0047] - IFFT: Inverse fast Fourier transform

[0048] - L1-RSRP: Layer 1 reference signal received power

[0049] - L1-RSRQ: Layer 1 reference signal received quality

[0050] - MAC: Medium Access Control

[0051] - NZP: Non-zero power

[0052] - OFDM: Orthogonal frequency division multiplexing

[0053] - PDCCH: Physical downlink control channel

[0054] - PDSCH: Physical downlink shared channel

[0055] - PMI: Precoding matrix indicator

[0056] - RE: resource element

[0057] - RI: Rank indicator

[0058] - RRC: Radio resource control

[0059] - RSSI: received signal strength indicator

[0060] - Rx: Reception

[0061] - QCL: quasi co-location

[0062] - SINR: Signal to interference and noise ratio

[0063] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))

[0064] - TDM: time division multiplexing

[0065] - TRP: transmission and reception point

[0066] - TRS: Tracking reference signal

[0067] - Tx: transmission

[0068] - UE: User equipment

[0069] - ZP: Zero power

[0070] System in general

[0071] As more communication devices require greater communication capacity, there is a growing need for improved mobile broadband communication compared to existing radio access technologies (RATs). Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide a variety of services anytime, anywhere, is also one of the key issues being considered for next-generation communications. In addition, communication system designs that take into account reliability- and latency-sensitive services / terminals are also being discussed. Thus, the introduction of next-generation RATs that take into account technologies such as enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, these technologies will be referred to as NR in this disclosure. NR is an example of a 5G RAT.

[0072] New RAT systems, including NR, use an OFDM transmission scheme or a similar transmission scheme. A new RAT system may follow OFDM parameters different from those of LTE. Alternatively, a new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist within one cell.

[0073] A numerology corresponds to a subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0074] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0075] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide the NG-RA (NG-Radio Access) user plane (i.e., new access stratum (AS) sublayer / Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) / MAC / PHY) and control plane (RRC) protocol termination for the UE. The gNBs are interconnected via an Xn interface. The gNBs are also connected to an NGC (New Generation Core) via an NG interface. More specifically, the gNBs are connected to an AMF (Access and Mobility Management Function) via an N2 interface and to a UPF (User Plane Function) via an N3 interface.

[0076] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0077] An NR system can support multiple numerologies. Here, a numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, multiple subcarrier spacings may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the numerology used may be selected independently of the frequency band. Furthermore, an NR system may support various frame structures based on multiple numerologies.

[0078] The following describes OFDM numerologies and frame structures that can be considered in an NR system. A number of OFDM numerologies supported in an NR system may be defined as shown in Table 1 below.

[0079] [Table 1]

[0080] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands, a 30 kHz / 60 kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidths, and a 60 kHz or higher SCS supports bandwidths greater than 24.25 GHz to overcome phase noise. NR frequency bands are defined as two types of frequency ranges (FR1 and FR2). FR1 and FR2 may be configured as shown in Table 2 below. FR2 can also refer to millimeter wave (mmW).

[0081] [Table 2]

[0082] In relation to the frame structure in an NR system, the size of the various fields in the time domain is T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and N f= 4096. Downlink and uplink transmission is T f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T = 10 ms. sf =(Δf max N f / 1000)·T c In this case, there may be one set of frames for the uplink and one set of frames for the downlink. In addition, transmission from a terminal in uplink frame number i begins T TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols, symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used.

[0083] Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), the number of slots per subframe (N slot subframe,μ ) and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0084] [Table 3]

[0085] [Table 4]

[0086] FIG. 2 shows an example where μ=2 (SCS is 60 kHz). Referring to Table 3, one subframe may include four slots. The number of slots in one subframe (1, 2, 4) shown in FIG. 2 is an example, and the number of slots that may be included in one subframe is defined as shown in Table 3 or Table 4. A mini-slot may include 2, 4, or 7 symbols, or may include more or fewer symbols. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, and the like may be considered. The physical resources that can be considered in an NR system will now be described in detail. First, regarding antenna ports, the antenna ports are defined so that the channel on which symbols on an antenna port are carried can be inferred from the channel on which other symbols on the same antenna port are carried. Two antenna ports are said to be in a QC / QCL (quasi co-located) relationship if the large-scale properties of the channel carrying symbols on one antenna port can be inferred from the channel carrying symbols on the other antenna port, where the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0087] 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied. Referring to FIG. 3, the resource grid is divided into N RB μ N sc RBIt consists of subcarriers, and one subframe is 14.2 μ In the NR system, a transmitted signal is composed of N OFDM symbols. RB μ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RB μ ≦N RB max,μ The above N RB max,μ represents the maximum transmission bandwidth, which may vary between uplink and downlink as well as with numerology.

[0088] In this case, one resource grid may be configured for μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and the index pair It is uniquely identified by TIFF0007736922000005.tif616, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG0007736922000006.jpg762 represents the position of a symbol within a subframe. When referring to a resource element in a slot, the index pair (k, l) is used, where l = 0,...,N symb μ μ and the resource element for antenna port p. JPEG0007736922000007.jpg617 is a complex value JPEG0007736922000008.jpg911. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indices p and μ may be dropped, so that the complex value is JPEG0007736922000009.jpg1129. Also, a resource block (RB) is a set of N sc RB = 12 consecutive subcarriers.

[0089] Point A serves as a common reference point for the resource block grid and is obtained as follows:

[0090] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0091] - absoluteFrequencyPointA denotes the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number). Common resource blocks are numbered from 0 upwards in the frequency domain for subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between the resource elements (k, l) for the subcarrier spacing setting μ is given by the following equation 1.

[0092]

number

[0093] In Equation 1, k is defined relative to point A so that k=0 corresponds to the subcarrier centered at point A. The physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ Physical resource block n in BWP i is numbered from -1 to i. PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0094]

number

[0095] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.

[0096] Fig. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied, and Fig. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0097] 4 and 5, a slot includes multiple symbols in the time domain. For example, in the general CP, one slot includes seven symbols, while in the extended CP, one slot includes six symbols.

[0098] A carrier wave includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain, and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier wave may include up to N (e.g., 5) BWPs. Data communication is performed using activated BWPs, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol may be mapped to it.

[0099] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC keeps the radio frequency (RF) chip for the entire CC on at all times, battery consumption may increase. Considering various application cases (e.g., eMBB, URLLC, MMTc, V2X, etc.) operating within a single wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Alternatively, each terminal may have different capabilities for maximum bandwidth. In consideration of this, a base station may instruct a terminal to operate only with a portion of the bandwidth of a wideband CC, rather than the entire bandwidth. For convenience, this portion of the bandwidth is defined as a bandwidth part (BWP). A BWP may consist of contiguous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot duration).

[0100] Meanwhile, the base station can configure multiple BWPs within one CC configured for the terminal. For example, a BWP occupying a relatively small frequency domain is configured in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH may be scheduled on a larger BWP.

[0101] Alternatively, when UEs are concentrated in a specific BWP, other BWPs may be configured for some UEs for load balancing. Alternatively, taking into consideration frequency domain inter-cell interference cancellation between adjacent cells, a central portion of the spectrum from the entire bandwidth may be excluded and both BWPs may be configured within the same slot. In other words, the base station can configure at least one DL / UL BWP for UEs associated with a wideband CC.

[0102] The base station can activate at least one DL / UL BWP among the DL / UL BWPs configured at a specific time (through L1 signaling, MAC CE (Control Element), RRC signaling, etc.). The base station can also instruct switching to another configured DL / UL BWP (through L1 signaling, MAC CE, RRC signaling, etc.). Alternatively, the base station can switch to a predetermined DL / UL BWP when a timer value expires on a timer basis. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP.

[0103] However, in situations where the UE is performing an initial access process or before the RRC connection is set up, the DL / UL BWP configuration may not be received. Therefore, the DL / UL BWP assumed by the UE in such situations is defined as the initially active DL / UL BWP.

[0104] FIG. 6 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0105] In a wireless communication system, a terminal receives information from a base station through a downlink and transmits information to the base station through an uplink. Information exchanged between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information exchanged.

[0106] When a terminal is powered on or newly enters a cell, it performs an initial cell search, such as synchronizing with a base station (S601). To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and acquire information such as a cell identifier (ID). The terminal then receives a physical broadcast channel (PBCH) from the base station to acquire broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0107] After completing the initial cell search, the terminal receives a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) based on the information carried on the PDCCH, and can acquire more specific system information (S602).

[0108] Meanwhile, when the terminal first connects to the base station or when there are no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) with the base station (steps S603 to S606). To this end, the terminal transmits a specific sequence as a preamble on a physical random access channel (PRACH) (steps S603 and S605) and can receive a response message to the preamble on a PDCCH and a corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure can also be performed.

[0109] After performing the above-described procedures, the UE can then perform PDCCH / PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission procedure. In particular, the UE receives downlink control information (DCI) via the PDCCH. Here, DCI includes control information such as resource allocation information for the UE, and its format varies depending on its purpose.

[0110] Meanwhile, control information that a terminal transmits to a base station on the uplink or that the terminal receives from a base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In a 3GPP LTE system, a terminal can transmit the above-mentioned control information such as CQI / PMI / RI on a PUSCH and / or a PUCCH.

[0111] Table 5 shows an example of a DCI format in an NR system.

[0112] [Table 5]

[0113] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB)-related information (e.g., Modulation Coding and Scheme (MCS), New Data Indicator (NDI), Redundancy Version (RV), etc.), hybrid-automatic repeat and request (HARQ)-related information (e.g., process number, Downlink Assignment Index (DAI), PDSCH-HARQ feedback timing, etc.), multiple antenna-related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for PUSCH scheduling in one cell. The information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled by C-RNTI (Cell Radio Network Temporary Identifier, Cell RNTI), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) before being transmitted. DCI format 0_1 ​​is used to indicate to a terminal the scheduling of one or more PUSCHs in one cell or downlink feedback information of configured grants (CG). The information included in DCI format 0_1 ​​is CRC-scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI before being transmitted.

[0114] DCI format 0_2 is used for scheduling the PUSCH in one cell. Information included in DCI format 0_2 is CRC scrambled using the C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and then transmitted.

[0115] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., antenna port, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be pre-defined.

[0116] DCI format 1_0 is used for scheduling PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0117] DCI format 1_1 is used for scheduling PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0118] DCI format 1_2 is used for scheduling PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0119] Sounding Reference Signal (SRS)

[0120] In Rel-15NR, interval relation information (e.g., 'spatialRelationInfo') may be used to indicate a transmission beam to be used when a base station transmits an UL channel to a terminal. The base station can indicate which UL transmission beam to use when transmitting a PUCCH and SRS by configuring a DL reference signal (e.g., SSB-RI (SB Resource Indicator), CSI-RS Resource Indicator (CRI) (P / SP / AP: periodic / semi-persistent / aperiodic)) or SRS (i.e., SRS resource) as a reference RS for a target UL channel and / or target RS through RRC configuration. In addition, when the base station schedules a PUSCH to a terminal, the transmission beam indicated by the base station and used for SRS transmission is indicated as a transmission beam for the PUSCH by the SRI field and is used as the PUSCH transmission beam of the terminal.

[0121] Below, SRS for codebook (CB) and non-codebook (NCB) will be described.

[0122] First, in the case of CB UL, the base station can first configure and / or instruct the terminal to transmit an SRS resource set for 'CB'. Then, the terminal can transmit any n-port SRS resource in the SRS resource set. The base station can receive an UL channel based on the SRS transmission and use it for PUSCH scheduling of the terminal.

[0123] Thereafter, when performing PUSCH scheduling using UL DCI, the base station can indicate the PUSCH (transmission) beam of the terminal by indicating the SRS resource for 'CB' previously transmitted by the terminal using the SRI field of the DCI. In addition, the base station can indicate the UL rank and UL precoder by indicating the uplink codebook using a transmitted precoder matrix indicator (TPMI) field. This allows the terminal to transmit the PUSCH according to the instructions.

[0124] Next, even in the case of NCB UL, the base station can first configure and / or instruct the terminal to transmit a 'non-CB' target SRS resource set. Then, based on the reception of the NZP CSI-RS linked to the SRS resource set, the terminal can determine precoders for SRS resources (up to four resources, one port per resource) in the SRS resource set and transmit the SRS resources simultaneously.

[0125] Thereafter, when performing PUSCH scheduling using UL DCI, the base station can indicate a PUSCH (transmission) beam for the terminal by using the SRI field of the DCI to indicate a portion of the 'non-CB' target SRS resources previously transmitted by the terminal, and can also indicate the UL rank and UL precoder, thereby allowing the terminal to transmit PUSCH according to the instructions.

[0126] Below we describe the SRS for beam management.

[0127] SRS may be used for beam management. Specifically, UL BM may be performed by transmitting beamformed UL SRS. Whether an SRS resource set is applied to UL BM is configured by the 'usage' (higher layer parameter). If the usage is set to 'BeamManagement (BM)', only one SRS resource may be transmitted from each of multiple SRS resource sets at a given time instant.

[0128] A terminal may be configured (by higher layer signaling, e.g., RRC signaling) with one or more Sounding Reference Symbol (SRS) resource sets configured by (higher layer parameter) 'SRS-ResourceSet'. For each SRS resource set, the UE may be configured with K≧1 SRS resources (higher layer parameter 'SRS-resource'), where K is a natural number and the maximum value of K is indicated by SRS_capability.

[0129] Below we describe SRS for antenna switching.

[0130] The SRS may be used to acquire DL CSI (Channel State Information) information (e.g., DL CSI acquisition). As a specific example, in a TDD-based single-cell or multi-cell (e.g., carrier aggregation (CA)) situation, a base station (BS) may schedule SRS transmission to a user equipment (UE), and then the SRS may be measured from the UE.

[0131] In this case, the base station may schedule DL signals / channels to the UE based on measurements by the SRS, assuming DL / UL reciprocity. In this case, in connection with DL CSI acquisition based on the SRS, the SRS may be configured for antenna switching.

[0132] As an example, when following a standard (e.g., 3GPP TS 38.214), the usage of the SRS may be configured in the base station and / or terminal using a higher layer parameter (e.g., the usage of the RRC parameter SRS-ResourceSet).

[0133] Here, the use of the SRS may be set to a beam management use, a codebook transmission use, a non-codebook transmission use, an antenna switching use, or the like.

[0134] Hereinafter, a specific description will be given of a case where SRS transmission (that is, transmission of an SRS resource or an SRS resource set) is set as an antenna switching use among the uses described above.

[0135] As an example, for a terminal with partial reciprocity, SRS transmission based on antenna switching (i.e., transmit antenna switching) may be supported for DL ​​(downlink) CSI (Channel State Information) acquisition using SRS transmission in a situation such as TDD (Time Division Duplex).

[0136] When antenna switching is applied, typically about 15 μs may be required between SRS resources (and / or between SRS resources and PUSCH / PUCCH resources) for antenna switching of the UE. In consideration of this, a (minimum) guard period may be defined as shown in Table 6 below.

[0137] [Table 6]

[0138] In Table 7, μ represents numerology, Δf represents subcarrier spacing, and Y represents the number of symbols in the guard interval, i.e., the length of the guard interval. Referring to Table 6, the guard interval may be set based on a parameter μ that determines the numerology. In the guard interval, the UE may be configured not to transmit any other signals, and the guard interval may be configured to be completely used for antenna switching. As an example, the guard interval may be set taking into account SRS resources transmitted in the same slot.

[0139] In particular, when a terminal is configured and / or instructed to transmit an aperiodic SRS configured as intra-slot antenna switching, the terminal transmits the SRS using a different transmit antenna for each designated SRS resource, and the above-mentioned guard interval may be set between each resource.

[0140] Also, as described above, when an SRS resource and / or an SRS resource set configured for antenna switching is configured by higher layer signaling, the UE may be configured to transmit SRS based on UE capability related to antenna switching. Here, the UE capability related to antenna switching may be '1T2R', '2T4R', '1T4R', '1T4R / 2T4R', '1T1R', '2T2R', '4T4R', etc. Here, 'mTnR' may mean a UE capability supporting m transmissions and n receptions.

[0141] (Example S1) For example, for a terminal supporting 1T2R, up to two SRS resource sets may be configured with different values ​​for resourceType in the upper layer parameter SRS-ResourceSet. Here, each SRS resource set may have two SRS resources transmitted in different symbols, and each SRS resource in a given SRS resource set may constitute a single SRS port. Furthermore, the SRS port for the second SRS resource in an SRS resource set may be configured to be associated with a different UE antenna port than the SRS port for the first SRS resource in the same SRS resource set.

[0142] (Example S2) As another example, for a terminal supporting 2T4R, up to two SRS resource sets may be configured with different values ​​for resourceType in the upper layer parameter SRS-ResourceSet. Here, each SRS resource set may have two SRS resources transmitted in different symbols, and each SRS resource in a given SRS resource set may constitute two SRS ports. Also, the SRS port pair for the second SRS resource in an SRS resource set may be configured to be associated with a different UE antenna port than the SRS port pair for the first SRS resource in the same SRS resource set.

[0143] (Example S3) As yet another example, for a UE supporting 1T4R, the SRS resource set may be configured in different manners depending on whether SRS transmission is configured to be periodic, semi-persistent, and / or aperiodic. First, when SRS transmission is configured to be periodic or semi-persistent, zero SRS resource set or one SRS resource set consisting of four SRS resources configured based on the resourceType of the upper layer parameter SRS-ResourceSet may be configured to be transmitted in different symbols.

[0144] Here, each SRS resource in a given SRS resource set can constitute a single SRS port. The SRS ports for each SRS resource may be configured to be associated with different UE antenna ports. Alternatively, when SRS transmission is configured aperiodically, zero SRS resource set or two SRS resource sets consisting of a total of four SRS resources configured based on the resourceType of the higher layer parameter SRS-ResourceSet may be configured to be transmitted in different symbols of two different slots. Here, the SRS ports for each SRS resource in two given SRS resource sets may be configured to be associated with different UE antenna ports.

[0145] (Example S4) As yet another example, for a terminal supporting 1T1R, 2T2R, or 4T4R, up to two SRS resource sets, each consisting of one SRS resource, may be configured for SRS transmission. The number of SRS ports for each SRS resource may be set to 1, 2, or 4.

[0146] If the indicated terminal capability is 1T4R / 2T4R, the terminal can expect the same number of SRS ports (e.g., 1 or 2) to be configured for all SRS resources in an SRS resource set. Also, if the indicated terminal capability is 1T2R, 2T4R, 1T4R, or 1T4R / 2T4R, the terminal need not expect one or more SRS resource sets configured for antenna switching in the same slot to be configured or triggered. Also, if the indicated terminal capability is 1T1R, 2T2R, or 4T4R, the terminal need not expect one or more SRS resource sets configured for antenna switching in the same slot to be configured or triggered.

[0147] How to transmit a sounding reference signal

[0148] In the basic wireless communication system, periodic / semi-persistent / aperiodic SRS is supported, and the SRS request field of the DCI may be used to trigger the aperiodic SRS.

[0149] In this case, a slot offset may be configured (at the set level) for each SRS resource set instructed to transmit by the DCI by RRC signaling. Here, the slot offset refers to an offset value from a DCI reception slot to an SRS transmission slot. The UE can transmit aperiodic SRS based on the corresponding slot offset.

[0150] In the improved wireless communication system, the base station can indicate a specific slot offset from among the slot offset values ​​set (by RRC signaling) for each SRS resource set by DCI.

[0151] In a basic wireless communication system, the slot offset may be counted based on all slots. However, in an improved wireless communication system, the slot offset (i.e., the 't' value) indicated by the DCI (or a slot offset indication field configured with a maximum of n bits (e.g., n is 2) included in the DCI) may be counted based on the UL available slot. Furthermore, the 't' value, which is the slot offset that can be indicated by the DCI, may be set up to, but is not limited to, four per SRS resource set.

[0152] Additionally or alternatively, a reference slot serving as a reference for counting the slot offset t value may be based on a slot offset ("slotOffset") value set by RRC signaling. That is, the UE may calculate the SRS transmission slot by applying the t value from a slot after the "slotOffset" set by RRC signaling from the slot in which the DCI is received (i.e., calculate the SRS transmission slot by counting the "t" value based on available slots).

[0153] Specifically, a given aperiodic SRS resource set may be transmitted in the (t+1)th available slot counting from the reference slot.

[0154] Here, the slot offset value "t" is indicated by DCI or RRC signaling (e.g., when one "t" value is set by RRC signaling), and the candidate values ​​of "t" may include at least 0. The reference slot may include a slot in which the triggering DCI is present or / and a slot indicated by a legacy triggering offset. The candidate values ​​of "t" may be updated by the MAC CE.

[0155] Then, based on the RRC signaling, the available slots may include slots in which there are UL or flexible symbols for time domain positions for all SRS resources of the resource set and which meet the terminal capability for minimum timing requirements between all SRS resources of the resource set and triggering of the PDCCH.

[0156] In the first symbol carrying DCI including the SRS request field and the last symbol of the triggered SRS resource set, the terminal may not expect to receive an SFI indication, an UL cancellation indication, or dynamic scheduling of DL channels / signals in flexible symbols that can change the determination of available slots, and collision handling between the triggered SRS and other UL channels / signals may be performed after the available slots are determined.

[0157] The 't' value may be indicated by DCI format 0_1 / 0_2 without data and CSI request and DCI that can schedule PDSCH / PUSCH. In this case, the DCI has a field for indicating the 't' value, and the field may be applied to multiple configured candidate values ​​of 't'.

[0158] As mentioned above, the interpretation of each code point in the slot offset indication field (or "t" indication field) of the DCI may differ based on the specific SRS resource set indicated by the SRS request field of the DCI.

[0159] For example, in a 1T4R aperiodic SRS transmission scenario, multiple SRS resource sets may be associated with one code point in the SRS request field.

[0160] Assume that the number of slot offset values ​​set for each of the plurality of SRS resource sets is different. In this case, a value indicated by the slot offset indication field may be valid for a specific SRS resource set. However, if the number of slot offset values ​​indicated by the slot offset indication field is insufficient, the value indicated by the field may not be valid for other SRS resource sets. Therefore, ambiguity may occur regarding the interpretation method of the slot offset indication field of the DCI.

[0161] The following describes a method for configuring / instructing a base station to transmit aperiodic SRS from a terminal.

[0162] In describing the present disclosure, "transmitting an SRS resource set" may be used synonymously with "transmitting an SRS based on information set in the SRS resource set."

[0163] Furthermore, "transmitting SRS resource(s)" may be used to mean the same thing as "transmitting SRS(s) based on information set in the SRS resource(s)."

[0164] In addition, an enhanced SRS after Rel-17 may be referred to as an additional SRS or an enhanced SRS, and a terminal supporting the additional (enhanced) SRS may be referred to as an additional UE or an enhanced UE.

[0165] In this regard, a legacy SRS refers to an SRS that can be configured with up to four symbols (legacy SRS configuration), and an enhanced SRS refers to an SRS that can be configured with more than four symbols (enhanced SRS (additional SRS) configuration). This is for convenience of explanation only and is not intended to limit the technical scope of the present disclosure.

[0166] Also, in this document " / " means "and", "or", or "and / or", depending on the context.

[0167] FIG. 7 is a diagram illustrating an operation of a terminal for transmitting and receiving a sounding reference signal according to an embodiment of the present disclosure.

[0168] The terminal may receive configuration information related to the SRS from the base station (S710). For example, the configuration information related to the SRS (e.g., "SRS-config") may include information related to an SRS resource set / SRS resource.

[0169] For example, the information related to the SRS resource sets may include a resource type (e.g., aperiodic, etc.) of at least one SRS resource set, an ID, a usage, and / or information setting at least one available slot offset for the at least one SRS resource set.

[0170] For example, the number of at least one available slot offset configured for each of the at least one SRS resource set configured by the configuration information may be the same, and the number of available slot offsets configurable for each of the at least one SRS resource set may be 1 to 4.

[0171] The information related to the SRS resource may include spatial relation information for the SRS resource, the number of SRS ports, a PTRS port index associated with the SRS resource, a type of the SRS resource, and the like.

[0172] The terminal can receive downlink control information (DCI) from the base station (S720).

[0173] The DCI may include an SRS request field that triggers one or more specific SRS resource sets among at least one SRS resource set configured by the configuration information. One or more SRS resource sets may be concatenated to each code point of the SRS request field. The same number of available slot offsets may be configured for the one or more SRS resource sets.

[0174] As an example, based on the number of at least one available slot offset configured for each of the at least one SRS resource set being greater than one, the DCI may include a slot offset indicator field indicating a particular available slot offset from the at least one available slot offset.

[0175] As another example, the DCI may not include a slot offset indicator field based on the number of at least one available slot offset configured for each of the at least one SRS resource set being 1. That is, when the number of available slot offsets configured for the at least one SRS resource set configured by the configuration information is all 1, the DCI may not include another slot offset indicator field.

[0176] The terminal may transmit an SRS based on the DCI (S730). For example, the terminal may transmit a (non-periodic) SRS to the base station based on the SRS request field and / or the slot offset indication field.

[0177] The terminal can transmit (non-periodic) SRS to the base station based on one or more specific SRS resource sets triggered by the SRS request field. In this case, the terminal can transmit (non-periodic) SRS to the base station based on a specific available slot offset indicated by the DCI among at least one available slot offset configured for the one or more specific SRS resource sets.

[0178] FIG. 8 is a diagram illustrating an operation of a base station for transmitting and receiving a sounding reference signal according to an embodiment of the present disclosure.

[0179] The base station may transmit configuration information related to the SRS to the terminal (S810).

[0180] The SRS-related configuration information may include information for configuring at least one available slot offset for each of at least one SRS resource set and information for configuring a resource type of the at least one SRS resource set as aperiodic, where the number of available slot offsets configured for each of the at least one SRS resource set may be the same.

[0181] The base station may transmit downlink control information (DCI) to the terminal (S820).

[0182] In this case, a DCI may be transmitted from the base station to the terminal to trigger transmission of the aperiodic SRS resource set. The DCI may include, but is not limited to, an SRS request field and / or a slot offset indication field.

[0183] The base station may receive an SRS based on the DCI from the terminal (S830). For example, the base station may receive an RS based on i) one or more specific SRS resource sets triggered by the SRS request field and ii) a specific available slot offset indicated by the slot offset indication field among at least one available slot offset set for the one or more specific SRS resource sets.

[0184] The following describes in detail how the base station configures / instructs the terminal to transmit aperiodic SRS.

[0185] Example 1

[0186] The bit-width of the (explicit) t indication field included in the DCI may be determined based on the maximum number of t values ​​among the number of t values ​​configured in each SRS resource set (i.e., based on the SRS resource set with the maximum t value configured).

[0187] Here, the SRS resource set may refer to one or more SRS resource sets associated with the SRS request field of the DCI (i.e., one or more SRS resource sets belonging to an SRS trigger state).

[0188] For example, assume that a total of three SRS resource sets are linked to each code point in the SRS request field as shown in Table 7 below.

[0189] [Table 7]

[0190] When the SRS request field is set as shown in Table 7, the SRS resource set with the largest t value set among the SRS resource sets set to the SRS trigger state is SRS resource set #3. Since the number of t values ​​set to SRS resource set #3 is four, the bit width or field size of the t indication field may be assumed / agreed between the base station and the terminal as 2 bits so as to indicate four t values. For example, when the number of t values ​​set to SRS resource set #3 is one, since the maximum number of t values ​​(e.g., two) is set for SRS resource set #1, the t indication field may be assumed / agreed between the base station and the terminal as 1 bit.

[0191] For example, the base station may update / activate an SRS resource set associated with the SRS trigger state using a MAC CE message, where the bit width of the t indicator field may be determined in a manner described below.

[0192] Specifically, when the SRS trigger state is updated by the MAC CE, the number of t values ​​configured for each SRS resource set linked to the SRS trigger state may change. As a result, the SRS resource set with the largest number of t values ​​configured may change. Furthermore, there may be an ambiguous period in which the bit width of the t indication field changes before and after the MAC CE update.

[0193] To solve this, the base station and the terminal can agree / assume that the reference time is 3 ms after the terminal receives the MAC CE message updating the SRS trigger status and transmits its ACK / NACK.

[0194] Furthermore, the base station and the terminal may promise / assume that the bit width of the t indication field is determined based on the t value set for each SRS resource set before the SRS trigger state update before the reference time point. The base station and the terminal may promise / assume that the bit width of the t indication field is determined based on the t value set for each SRS resource set after the SRS trigger state update after the reference time point.

[0195] Additionally or alternatively, the UE may expect the same number of t values ​​to be configured for all SRS resource sets configured / connected to the SRS trigger state. In this case, the bit width of the t indication field may be determined according to the number of t values ​​configured equally for all SRS resource sets. For example, the bit width of the t indication field may be determined as "ceil(log2(the number of t values))".

[0196] In the above example, it is assumed that the t indication field is embodied as a newly configurable DCI field explicitly, but this is not limiting. For example, even if the t indication field is an implicit field or if the t value is indicated based on an unused field of the DCI, the operations / assumptions / promises / parameters of the first embodiment described above may be applied / utilized.

[0197] Example 2

[0198] The (explicit) t indication field of the DCI may be interpreted differently depending on which SRS resource set is the target SRS resource set indicated by the SRS request field included in the DCI.

[0199] In addition, the t value set for each SRS resource set may be agreed / assumed between the base station and the terminal in a form in which the lowest t value is mapped first from the lowest code point in the t indication field (i.e., ascending order mapping).

[0200] For example, assume that the SRS request field is set as shown in Table 7. The bit width of the t indication field is 2 bits (00, 01, 10, 11), but the interpretation of the t indication field may differ depending on which SRS resource set indicated by the SRS request field is SRS resource set #1, #2, or #3.

[0201] As an example, if SRS resource set #1 is indicated (by the SRS request field), each bit of the t indication field may be parsed as "00:t=2", "01:t=4", "10:N / A", and "11:N / A". If SRS resource set #2 is indicated,

[0202] As another example, if SRS resource set #2 is indicated (by the SRS request field), each bit of the t indication field may be parsed as "00:t=5", "01:N / A", "10:N / A", and "11:N / A".

[0203] As yet another example, if SRS resource set #3 is indicated (by the SRS request field), each bit of the t indication field may be parsed as "00:t=2", "01:t=5", "10:t=7", and "11:t=8".

[0204] As shown in the above example, the number of code points in the available t indication field may vary depending on the SRS resource set indicated in the SRS request field. In this case, the terminal does not need to expect that an unavailable "N / A" code point will be indicated.

[0205] Example 3

[0206] Example 3 relates to the configuration and operation related to the value t when multiple SRS resource sets are configured / linked to a specific code point (i.e., a specific trigger state) in the SRS request field of the DCI.

[0207] In the improved wireless communication system, multiple SRS resource sets may be configured for a specific xTyR configuration for antenna switching aperiodic SRS triggering, similar to the 1T4R configuration, and the multiple SRS resource sets may all be linked to a specific code point in the SRS request field so that they can all be triggered by a single DCI indication.

[0208] In this case, the code point indicated in the t indication field of the DCI is a single value, but the number of SRS resource sets triggered by the SRS request field is greater than or equal to 1. Therefore, the t indication field must be parsed for each SRS resource set based on the t value set for each SRS resource set.

[0209] Example 3-1

[0210] It is assumed that the bit width of the t indicator field is determined in the manner according to Example 1, and the t indicator field is parsed in the manner according to Example 2. As an example, it is assumed that the code points of the SRS request field are set as shown in Table 8 below.

[0211] [Table 8]

[0212] When the SRS request field is set according to Table 8, the maximum number of t values ​​set in each SRS resource set is 4, so the bit width of the t indication field may be 2 bits according to Example 1. When the code point value indicated in the SRS request field is 00 or 01 (i.e., when SRS resource set #1 or #2 is indicated), the analysis of the t indication field has been described in Example 2, so a duplicated description will be omitted.

[0213] If the code point indicated in the SRS request field is 11, multiple SRS resource sets (i.e., SRS resource sets #3 and #4) may be triggered. Thus, for SRS resource set #3, the t indication field may be parsed as "00:t=2," "01:t=5," "10:t=7," and "11:t=8." And, for SRS resource set #4, the t indication field may be parsed as "00:t=1," "01:t=3," "10:t=6," and "11:t=9."

[0214] Additionally or alternatively, assume that two or more SRS resource sets are configured / concatenated / mapped to one SRS trigger state, in which case the t value of the second (or second-lowest indexed) SRS resource set configured to the trigger state is set to "t value + 1" of the first (or lowest indexed) SRS resource set, or the UE can expect this configuration (Option 1).

[0215] Alternatively, the terminal can ignore the t value set in the second (or second-lowest indexed) SRS resource set and assume / promise / recognize the setting of "t value + 1" in the first (or lowest indexed) SRS resource set (option 2).

[0216] Here, the "t value + 1" (or the "+1" part) may be counted as an available slot, or may be counted in all slots to improve performance by antenna switching SRS transmission in consecutive slots.

[0217] Option 1 and Option 2 may also be applied in the same way when more than two SRS resource sets are configured / connected to one SRS trigger state (e.g., the first SRS resource set = t value, the second SRS resource set = t value + 1, the third SRS resource set = t value + 2, etc.). Additionally or alternatively, in Option 1 and Option 2, the terminal may expect that the t value is configured only for the first (or lowest index) SRS resource set.

[0218] Additionally or alternatively, assume that multiple SRS resource sets are configured / concatenated in a single SRS trigger state. Even if the number of t values ​​configured for each SRS resource set is different, when the t value is indicated by the base station via the t indication field of the DCI, the UE can expect that an ambiguous combination based on the t indication field will not be indicated.

[0219] For example, the ambiguous combination includes a case where a specific code point in the t indication field indicates a t value only for a specific SRS resource set, but does not indicate a t value for the remaining SRS resource sets.

[0220] Example 3-2

[0221] When multiple SRS resource sets are associated with a (specific) code point in the SRS request field, the terminal can expect the same number of t values ​​to be set in all SRS resource sets associated with the (specific) code point.

[0222] For example, assume that the field size of the t indicator field is fixed and different t values ​​are set for each SRS resource set linked to a code point in one SRS request field, in which case a specific code point in the t indicator field can indicate a t value for a specific SRS resource set but may not be valid for other SRS resource sets.

[0223] For example, assume that four t values ​​are configured for SRS resource set #3, but two t values ​​(t=1, 3) are configured for SRS resource set #4. In this case, each bit of the t indication field for SRS resource set #4 may be parsed as "00:t=1," "01:t=3," "10:N / A," and "11:N / A." Therefore, if the t indication field indicates "10" or "11," the t indication field may not be valid for SRS resource set #4, and terminal operation may be ambiguous.

[0224] Additionally, when the single codepoint is used to trigger multiple SRS resource sets, the terminal can expect that the t values ​​for each SRS resource set indicated in the t indication field will not overlap.

[0225] Additionally or alternatively, assume that multiple SRS resource sets are configured / concatenated in a single SRS trigger state. Even if the number of t values ​​configured for each SRS resource set is different, when the t value is indicated by the base station via the t indication field of the DCI, the UE can expect that an ambiguous combination based on the t indication field will not be indicated.

[0226] For example, the ambiguous combination includes a case where a specific code point in the t indication field indicates a t value only for a specific SRS resource set, but does not indicate a t value for the remaining SRS resource sets.

[0227] Example 3-3

[0228] Contrary to Example 3-2, when multiple SRS resource sets are associated with a (specific) code point in the SRS request field, different numbers of t values ​​may be set for each SRS resource set associated with the code point.

[0229] In this case, if a specific code point is indicated by the base station in the t indication field, the specific code point in the t indication field may not be valid for an SRS resource set in which a small number of t values ​​are set.

[0230] Therefore, the terminal can specify / assume / promise with the base station that it will not transmit a specific SRS resource set for which the t value does not apply as a valid value (or for which the t value is analyzed as N / A) (option 3).

[0231] As another example, the terminal can specify / assume / promise with the base station that it will transmit a specific SRS resource set based on the indicated t value for other SRS resource sets other than the specific SRS resource set for which the t value does not apply as a valid value (option 4).

[0232] As an example, in a specific antenna switching configuration where multiple SRS resource sets are configured, Option 3 can be utilized when the base station (intentionally) triggers only some of the SRS resource sets to configure / instruct antenna switching for partial antenna switching or a subset of Rx / Tx antennas.

[0233] As another example, assume that four t values ​​are set for SRS resource set #3 as shown in Table 8, and two t values ​​(for example, t=1, 3) are set for SRS resource set #4.

[0234] In this case, the interpretation of the t indication field for SRS resource set #4 may be "00:t=1", "01:t=3", "10:N / A", and "11:N / A". In this case, if the t indication field indicates "10", the t value for SRS resource set #4 is invalid and the t value for SRS resource set #3 may be indicated as 7. The terminal can transmit both SRS resource sets #3 and #4 by utilizing option 4 and applying t=7.

[0235] As another example, assume that the value of t indicated by a specific DCI is not valid for multiple SRS resource sets but is valid for a specific single SRS resource set, in which case the UE can transmit all triggered SRS resource sets by applying the valid value of t using Option 4.

[0236] As another example, assume that the value of t indicated by a specific DCI is invalid for one or more SRS resource sets but valid for one or more other SRS resource sets, in which case the UE can map the SRS resource sets to valid t values ​​according to a predefined rule.

[0237] As an example, the terminal may map the t value configured / indicated for the valid SRS resource set with the lowest set index (according to a predefined rule) to the non-valid SRS resource set with the lowest set index.

[0238] In this case, when multiple SRS resource sets are transmitted together based on a valid t value, the terminal can apply Option 4 only when the symbol-level positions (within a slot) of the SRS resources included in the multiple SRS resource sets do not overlap.

[0239] As an example, if the symbol level positions (within a slot) of SRS resources included in multiple SRS resource sets overlap, the terminal may cancel and drop transmissions for all SRS resources in the inactive SRS resource sets.

[0240] As yet another example, among the t values ​​set for each SRS resource set, invalid values ​​(eg, N / A, IV) may be defined / set in a manner described below.

[0241] For example, assume that the first and second SRS resource sets are configured / concatenated / mapped to a single SRS trigger state, in which case the base station may configure t={IV,IV,2,3} for the first SRS resource set and configure t={2,3,4,IV} for the second SRS resource set.

[0242] In this case, the first and second t values ​​(or / and the lowest code point and second lowest code point values ​​in the t indication field) may be used to trigger only the second SRS resource set, the third t value (or / and the third lowest code point in the t indication field) may be used to trigger all two SRS resource sets, and the fourth t value may be used to trigger only the first SRS resource set. The above example may also be applied when more than two SRS resource sets are set / concatenated to a single SRS trigger state.

[0243] The above-described embodiments and options may be utilized / operated independently, but are not limited to this. The above-described embodiments and options may also be utilized / operated in combination with each other.

[0244] In the above embodiments and options, the base station configuration can refer to higher layer signaling (e.g., RRC signaling), the base station activation can refer to MAC level signaling including MAC CE messages, and the base station instruction can refer to dynamic instruction using MAC CE / DCI, etc.

[0245] FIG. 9 is a diagram illustrating a signaling procedure between a network side and a terminal according to an embodiment of the present disclosure.

[0246] FIG. 9 shows an example of signaling between the network side and the terminal (UE) in a network situation (e.g., an M-TRP situation) to which the above-described examples of the present disclosure (e.g., Example 1, Example 2, Example 3, or a combination of one or more of their detailed examples) can be applied.

[0247] Here, the UE / network side is exemplary and may be alternatively applied to various devices as described with reference to Fig. 10. Fig. 9 is provided for convenience of explanation and does not limit the scope of the present disclosure. Also, some steps shown in Fig. 9 may be omitted depending on the situation and / or settings. Also, the above-described uplink transmission / reception operation, M-TRP-related operation, etc. may be referenced or used in the operation of the network side / UE in Fig. 9.

[0248] In the following description, the network side may be a base station including multiple TRPs or a cell including multiple TRPs. Alternatively, the network side may include multiple remote radio heads (RRHs) / remote radio units (RRUs). As an example, an ideal / non-ideal backhaul may be established between TRP1 and TRP2 constituting the network side. Furthermore, although the following description is based on multiple TRPs, this may be equally extended and applied to transmission using multiple panels / cells, or may be equally extended and applied to transmission using multiple RRHs / RRUs, etc.

[0249] In addition, in the following description, the description will be based on "TRP", but as described above, "TRP" may be substituted with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), TP (transmission point), base station (gNB, etc.), etc. As described above, TRPs may be distinguished by information (e.g., CORESET index, ID) related to a CORESET group (or CORESET pool).

[0250] As an example, if one terminal is configured to transmit and receive with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one terminal. Such configuration of the CORESET groups (or CORESET pools) may be performed by higher layer signaling (e.g., RRC signaling, etc.).

[0251] Furthermore, the base station may be a general term for an object that transmits and receives data to and from a terminal. For example, the base station may be a concept including one or more TPs (Transmission Points), one or more TRPs (Transmission and Reception Points), etc. Furthermore, the TP and / or TRP may include a panel, a transmission and reception unit, etc. of the base station.

[0252] The terminal can receive SRS-related configuration information from the network side (S105).

[0253] Here, as in the above-mentioned Examples 1 to 3, the SRS-related configuration information may include configuration information related to SRS transmission, configuration information regarding one or more SRS resource sets (i.e., N (N is a natural number) SRS resource sets), etc., and each SRS resource set may include one or more SRS resources, thereby the configuration information may include configuration information regarding one or more SRS resources.

[0254] In addition, the SRS-related configuration information may include a usage value for each SRS resource set (or each SRS resource), where the usage may include codebook, non-codebook, beam management, antenna switching, and / or positioning.

[0255] In addition, the information on the usage setting for antenna switching included in the SRS-related setting information may be set in the form of a subset of the 'xTyR' in which the SRS resource set (or SRS resource) was previously reported to the base station as the terminal's capability information.

[0256] In addition, the SRS-related configuration information may include time-domain operation (ie, periodic transmission, aperiodic transmission, semi-persistent transmission) information for each SRS resource set (or for each SRS resource).

[0257] The SRS-related configuration information may include information for configuring one or more slot offsets for each SRS resource set, and up to four slot offsets may be configured for each SRS resource set, but is not limited thereto.

[0258] The SRS-related configuration information may also include information indicating an available slot from slot n+k in which the aperiodic SRS resource set is transmitted, where slot n refers to the slot in which DCI triggering the aperiodic SRS (i.e., DCI including an SRS request field) is transmitted, and K may refer to the triggering offset.

[0259] For example, the operation of the UE (100 or 200 in FIG. 10) receiving the SRS-related configuration information from the network side (200 or 100 in FIG. 10) in step S105 described above may be implemented by the apparatus of FIG. 10 described below. For example, referring to FIG. 10, one or more processors 102 may control one or more transceivers 106 and / or one or more memories 104 to receive the SRS-related configuration information, and one or more transceivers 106 may receive the SRS-related configuration information from the network side.

[0260] The terminal can transmit DCI to the network side (S110).

[0261] In this case, the DCI may include an SRS request field that triggers SRS transmission for one or more SRS resource sets among the one or more SRS resource sets configured by the configuration information. Additionally or alternatively, the DCI may include a slot offset indication field (or a t (i.e., slot offset) value indication field) that indicates a slot offset.

[0262] For example, the number of slot offsets configured for each of one or more SRS resource sets triggered by the SRS request field may be the same, but is not limited thereto.

[0263] One or more SRS resource sets may be configured for each code point in the SRS request field. For example, multiple SRS resource sets may be configured for a specific code point in the SRS request field.

[0264] For example, the operation of the UE (100 or 200 in FIG. 10) receiving the DCI from the network side (200 or 100 in FIG. 10) in step S110 described above may be implemented by the apparatus of FIG. 10 described below. For example, referring to FIG. 10, one or more processors 102 may control one or more transceivers 106 and / or one or more memories 104 to receive the control information, and one or more transceivers 106 may receive the control information from the network side.

[0265] The terminal can transmit the SRS to the network side based on the configuration information and the DCI (S115).

[0266] The UE may transmit the (non-periodic) SRS based on a specific slot offset value indicated by the DCI, where the specific slot offset value may be the slot offset value indicated by the DCI among one or more slot offset values ​​configured for the SRS resource set triggered by the DCI.

[0267] For example, the operation of the terminal (100 or 200 in FIG. 10) transmitting an SRS to the network side (200 or 100 in FIG. 10) or receiving an SRS from the network side (200 or 100 in FIG. 10) in step S115 described above may be implemented by the device of FIG. 10 described below.

[0268] For example, referring to FIG. 13, one or more processors 102 may control one or more transceivers 106 and / or one or more memories 104, etc., to transmit an SRS.

[0269] General devices to which the present disclosure can be applied

[0270] FIG. 10 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.

[0271] Referring to FIG. 10, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR).

[0272] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals and then transmit a wireless signal including the first information / signals from the transceiver 106. The processor 102 may also receive a wireless signal including second information / signals from the transceiver 106 and then store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 102 and the memory 104 may be part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (Radio Frequency) unit. In the present invention, a wireless device may refer to a communications modem / circuit / chip.

[0273] The second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. For example, the processor 202 may process information in the memory 204 to generate third information / signal, and then transmit a wireless signal including the third information / signal from the transceiver 206. The processor 202 may also receive a wireless signal including fourth information / signal from the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 202 and the memory 204 may be part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a wireless device may refer to a communications modem / circuit / chip.

[0274] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The one or more processors 102, 202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed in this disclosure and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure.

[0275] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions, and / or collections of instructions.

[0276] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or instructions. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0277] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flowcharts of the present disclosure, to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure, via the one or more antennas 108, 208. In this disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received user data, control information, wireless signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0278] FIG. 12 illustrates a vehicle device according to one embodiment of the present disclosure.

[0279] Referring to FIG. 12, the vehicle 100 may include a communication unit 110, a control unit 120, a memory unit 130, an input / output unit 140a, and a position measurement unit 140b.

[0280] The communication unit 110 can transmit and receive signals (e.g., data, control signals, etc.) to and from other vehicles or external devices such as base stations. The control unit 120 can control components of the vehicle 100 to perform various operations. The control unit 120 can be configured to control the memory unit 130 and / or the communication unit 110 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts described in this disclosure. The memory unit 130 can store data, parameters, programs, codes, and instructions that support various functions of the vehicle 100. The input / output unit 140a can output AR / VR objects based on information in the memory unit 130. The input / output unit 140a may include a head-up display (HUD). The position measurement unit 140b can acquire position information of the vehicle 100. The position information may include absolute position information of the vehicle 100, position information within a driving line, acceleration information, position information relative to surrounding vehicles, etc. The position measurement unit 140b may include a GPS and various sensors.

[0281] For example, the communication unit 110 of the vehicle 100 can receive map information, traffic information, etc. from an external server and store the information in the memory unit 130. The position measurement unit 140b can acquire vehicle position information using a GPS and various sensors and store the information in the memory unit 130. The control unit 120 can generate a virtual object based on the map information, traffic information, and vehicle position information, and the input / output unit 140a can display the generated virtual object on a glass window inside the vehicle (1410, 1420). The control unit 120 can also determine whether the vehicle 100 is operating normally within the driving lane based on the vehicle position information. If the vehicle 100 deviates abnormally from the driving lane, the control unit 120 can display a warning on the glass window inside the vehicle via the input / output unit 140a. The control unit 120 can also broadcast a warning message regarding the abnormal driving to nearby vehicles via the communication unit 110. Depending on the situation, the control unit 120 can transmit the vehicle position information and information regarding the driving / vehicle abnormality to relevant authorities via the communication unit 110.

[0282] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented without being combined with other components or features. It is also possible to combine some components and / or features to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to form embodiments, or may be included as new claims by amendment after filing.

[0283] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0284] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of various embodiments, as well as non-transitory computer-readable media on which such software or instructions are stored and executable on a device or computer. Instructions usable for programming a processing system to perform features described in this disclosure may be stored on or in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in this disclosure. Storage media may include high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, but may also include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory optionally includes one or more storage devices located remotely from the processor. Memory, or alternatively, non-volatile memory devices within memory, comprise non-transitory computer-readable storage media. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0285] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include LTE, NR, 6G, and also Narrowband Internet of Things (NB-IoT) for low-power communication. Here, for example, the NB-IoT technology may be an example of a Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (XXX, YYY) of the present disclosure may perform communication based on the LTE-M technology. Here, for example, the LTE-M technology may be an example of an LPWAN technology and may be referred to by various names such as enhanced Machine Type Communication (eMTC). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, wireless communication technologies implemented in the wireless device (XXX, YYY) of the present disclosure may include at least one of ZigBee, Bluetooth, and a Low Power Wide Area Network (LPWAN), which consider low-power communication, and are not limited to the above names. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names. [Industrial Applicability]

[0286] The method proposed in this disclosure has been described mainly as being applied to 3GPP LTE / LTE-A and 5G systems, but it can also be applied to various other wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A step in which a UE (user equipment) receives configuration information related to SRS (sounding reference signal) transmission from a base station; receiving downlink control information (DCI) from the base station by the UE; transmitting an SRS to the base station based on the DCI and the configuration information from the UE; the configuration information includes information related to at least one available slot offset for each of at least one SRS resource set; based on the maximum number of the at least one available slot offsets configured for all of the at least one SRS resource set being greater than one; the DCI includes an offset indicator field associated with a first available slot offset of the at least one available slot offset; and a bit length of the offset indicator field based on the maximum number of the at least one available offset for all of the at least one SRS resource set; The method of claim 1, wherein the DCI does not include the offset indicator field based on the maximum number of the at least one available slot offset configured for all of the at least one SRS resource set being 1.

2. The method of claim 1 , wherein the DCI includes an SRS request field associated with at least one triggered SRS resource set among the at least one SRS resource set.

3. The method of claim 2 , wherein the SRS is transmitted to the base station based on the at least one triggered SRS resource set indicated by the SRS request field.

4. 4. The method of claim 3, wherein the SRS is transmitted to the base station based on a particular available slot offset indicated by the DCI among the at least one available slot offset configured for the at least one triggered SRS resource set.

5. The method of claim 1 , wherein the number of the at least one available slot offset configured for the at least one SRS resource set is 1 to 4.

6. The method of claim 1 , wherein the configuration information includes information related to a resource type of at least one aperiodically configured SRS resource.

7. At least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor receiving configuration information related to sounding reference signal (SRS) transmission from a base station via the at least one transceiver; receiving downlink control information (DCI) from the base station via the at least one transceiver; configured to transmit an SRS to the base station via the at least one transceiver based on the DCI and the configuration information; the configuration information includes information related to at least one available slot offset for each of at least one SRS resource set; based on the maximum number of the at least one available slot offsets configured for all of the at least one SRS resource set being greater than one; the DCI includes an offset indicator field associated with a first available slot offset of the at least one available slot offset; and a bit length of the offset indicator field based on the maximum number of the at least one available offset for all of the at least one SRS resource set; A UE (user equipment) in which the DCI does not include the offset indicator field based on the maximum number of the at least one available slot offset configured for all of the at least one SRS resource set being 1.

8. At least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor transmitting configuration information related to sounding reference signal (SRS) transmission to a user equipment (UE) via the at least one transceiver; transmitting downlink control information (DCI) to the UE via the at least one transceiver; configured to receive, from the UE via the at least one transceiver, an SRS based on the DCI and the configuration information; the configuration information includes information related to at least one available slot offset for each of at least one SRS resource set; based on the maximum number of the at least one available slot offsets configured for all of the at least one SRS resource set being greater than one; the DCI includes an offset indicator field associated with a first available slot offset of the at least one available slot offset; and a bit length of the offset indicator field based on the maximum number of the at least one available offset for all of the at least one SRS resource set; A base station, wherein the DCI does not include the offset indicator field based on the maximum number of the at least one available slot offset set for all of the at least one SRS resource set being 1.