Signal transmission and reception method and apparatus in wireless communication systems

By configuring frequency hopping for SRS transmission within single slots, the method improves signal accuracy and efficiency in wireless communication systems, addressing the limitations of RedCap devices.

JP2026513213APending Publication Date: 2026-04-23LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
LG ELECTRONICS INC
Filing Date
2024-04-08
Publication Date
2026-04-23

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in accurately and efficiently transmitting and receiving signals, particularly for terminals with reduced performance capabilities, such as RedCap devices, which require improved methods for SRS transmission and reception.

Method used

Implementing frequency hopping configurations for SRS transmission and reception that ensure each hop is contained within a single slot interval, with specific settings for starting positions, lengths, and bandwidths, and allowing for RF retuning, to support terminals with smaller maximum bandwidths.

Benefits of technology

This approach enhances signal transmission and reception accuracy and efficiency in wireless communication systems, particularly benefiting RedCap devices by optimizing SRS transmission and reception.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026513213000001_ABST
    Figure 2026513213000001_ABST
Patent Text Reader

Abstract

According to at least one embodiment disclosed herein, a method by which a terminal transmits a sounding reference signal (SRS) in a wireless communication system includes receiving configuration information for the SRS for positioning via higher-level signaling; and transmitting the SRS for positioning in each frequency band of a plurality of hops, based on the configuration information including a frequency hopping configuration for the SRS for positioning, wherein the frequency hopping configuration includes i) information about the starting position of each hop and ii) information about the length of each hop in the time domain, and the terminal does not need to expect that one hop among the plurality of hops configured based on the frequency hopping configuration will be configured beyond a single slot.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This specification relates to a wireless communication system, and more particularly, to a method for transmitting or receiving uplink / downlink signals in a wireless communication system and an apparatus therefor.

Background Art

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. Generally, a wireless communication system is a multiple access system that shares available system resources (bandwidth, transmission power, etc.) to support communication with multiple users. Examples of multiple access systems include CDMA (code division multiple access) systems, FDMA (frequency division multiple access) systems, TDMA (time division multiple access) systems, OFDMA (orthogonal frequency division multiple access) systems, SC-FDMA (single carrier frequency division multiple access) systems, and the like.

Summary of the Invention

Problems to be Solved by the Invention

[0003] The technical problem to be achieved by the present invention is to provide a method for transmitting or receiving signals more accurately and efficiently in a wireless communication system and an apparatus therefor.

[0004] The technical problem to be achieved by the present invention is not limited to the above technical problem, and other technical problems will be inferred from the following embodiments.

Means for Solving the Problems

[0005] In a one-sided wireless communication system, a method by which a terminal transmits an SRS (sounding reference signal) may include receiving, through higher layer signaling, configuration information regarding an SRS for positioning; and transmitting the SRS for positioning in each frequency band of each of a plurality of hops, based on the configuration information including a frequency hopping configuration for the SRS for positioning. The frequency hopping configuration may include i) information regarding a start position of each hop and ii) information regarding a length of each hop in the time domain.The terminal can be configured not to expect that a single hop among the plurality of hops configured based on the frequency hopping setting is configured beyond a single slot.

[0006] The terminal can be configured such that none of the multiple hops are expected to be set beyond the single slot interval (duration) associated with each hop.

[0007] The entire sequence from the start symbol to the end symbol of the single hop can be contained within a single slot interval (duration).

[0008] i) The information regarding the starting position of each hop may include information regarding the starting symbol of each hop and information regarding the slot offset.

[0009] The final symbol position of each hop can be the starting symbol position of each hop plus the length of each hop as described in ii).

[0010] The frequency hopping setting may further include at least one of the following: iii) information regarding the number of hops, iv) information regarding the starting PRB (physical resource block) of the first hop in the time domain among the hops, v) information regarding hop bandwidth, or vi) information regarding the number of overlapping RBs between hops.

[0011] None of the aforementioned hops can be set across multiple slots.

[0012] The terminal may be a second type of terminal with reduced performance to support a smaller maximum terminal bandwidth than the first type of terminal.

[0013] The aforementioned frequency hopping can be performed based on RF (radio frequency) retuning.

[0014] In another aspect, a processor-readable recording medium can be provided on which a program for performing the aforementioned SRS transmission method is recorded.

[0015] Another aspect of a device for wireless communication includes a memory for storing instruction words and a processor that operates by executing the instruction words, the operation of which the processor may include receiving configuration information for SRS for positioning via higher-level signaling and transmitting the SRS for positioning in each frequency band of a plurality of hops, based on the configuration information including frequency hopping settings for the SRS for positioning. The frequency hopping settings may include i) information about the starting position of each hop in the time domain and ii) information about the length of each hop. The device may be configured not to expect that one hop of the plurality of hops configured based on the frequency hopping settings will be configured beyond a single slot.

[0016] The aforementioned device may further include a transceiver.

[0017] The aforementioned device may be a terminal operating in a wireless communication system.

[0018] The aforementioned device may be a processing device configured to control a terminal operating in a wireless communication system.

[0019] In another aspect of a wireless communication system, a method by which at least one base station receives a sounding reference signal (SRS) may include: determining a frequency hopping setting for the SRS for positioning; transmitting setting information, including the frequency hopping setting, to a terminal via higher-level signaling; and receiving the SRS for positioning from the terminal in each frequency band of a plurality of hops based on the setting information, including the frequency hopping setting. The frequency hopping setting may include i) information about the starting position of each hop in the time domain, and ii) information about the length of each hop. The base station may determine the frequency hopping setting such that no single hop among the plurality of hops is set beyond a single slot, based on the fact that the terminal is a second type terminal with reduced performance to support a smaller terminal maximum bandwidth than a first type terminal.

[0020] Another aspect of this is that a processor-readable recording medium can be provided, which contains a program for executing the aforementioned SRS transmission method.

[0021] Another aspect of a base station for wireless communication includes at least one memory for storing instruction words; and at least one processor that operates by executing the instruction words, the operation of which the at least one processor may include determining frequency hopping settings for a sounding reference signal (SRS) for positioning; transmitting setting information, including the frequency hopping settings, to a terminal via higher-level signaling; and receiving the SRS for positioning from the terminal in each frequency band of a plurality of hops based on the setting information, including the frequency hopping settings. The frequency hopping settings may include i) information about the starting position of each hop in the time domain, and ii) information about the length of each hop. The at least one processor may be configured to determine the frequency hopping settings such that no single hop among the plurality of hops is set beyond a single slot, based on the fact that the terminal is a second type terminal with reduced performance to support a smaller terminal maximum bandwidth than a first type terminal. [Effects of the Invention]

[0022] According to one embodiment of the present invention, signals can be transmitted or received more accurately and efficiently in a wireless communication system.

[0023] The effects obtained by the present invention are not limited to those mentioned above, and other effects can be inferred from the following examples. [Brief explanation of the drawing]

[0024] [Figure 1] This document illustrates physical channels used in 3GPP systems, an example of wireless communication systems, and general signal transmission methods using them. [Figure 2] The structure of a radio frame is illustrated below. [Figure 3]An example of a slot resource grid is shown. [Figure 4] This shows an example of how a physical channel is mapped within a slot. [Figure 5] The PDSCH reception and ACK / NACK transmission processes are illustrated as examples. [Figure 6] The PUSCH transmission process is given as an example. [Figure 7] This figure shows an example of a positioning protocol setting. [Figure 8] This figure shows an example of OTDOA. [Figure 9] This figure shows an example of a Multi RTT. [Figure 10] This document describes the procedure for operating a network node (e.g., a higher-level node of a terminal, such as an LMF) according to one embodiment. [Figure 11] This document outlines the procedures for terminal operations that perform positioning measurement. [Figure 12] This illustrates various ISAC environments. [Figure 13-14] This is an example of a 3GPP wireless communication system that supports ISAC. [Figure 15] An example of multiple SRSp hops contained within a single slot is shown. [Figure 16] This shows an example of an SRSp hop that is truncated based on slot boundaries. [Figure 17] This shows an example of frequency hopping behavior of an SRSp resource across a slot boundary. [Figure 18-19] Each example shows an SRSp hop for multiple slots that do not straddle a slot boundary. [Figure 20] This shows an example of SRSp resource mapping reconfigured based on slot boundaries. [Figure 21-22] This shows an example of frequency hopping behavior for SRSp resources truncated based on slot boundaries. [Figure 23-24]Each example shows the frequency hopping behavior of an SRSp resource across slot boundaries. [Figure 25] This diagram illustrates the operation of a network and terminals according to one embodiment. [Figure 26] This shows the flow of a terminal SRS transmission method according to one embodiment. [Figure 27] This shows the flow of a base station SRS reception method according to one embodiment. [Figure 28-31] Examples of communication systems 1 and wireless devices applicable to the present invention are provided. [Modes for carrying out the invention]

[0025] The following technologies can be used in various wireless connectivity systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented using radio technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA can be implemented using radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project: registered trademark: hereinafter the same) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA, and LTE-A (Advanced) is an advanced version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A.

[0026] As more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing RAT (Radio Access Technology) is emerging. Furthermore, massive MTC (Machine Type Communications), which connects multiple devices and things to provide various services anytime, anywhere, is one of the important issues to consider in next-generation communications. Moreover, communication system designs that take into account reliability and latency-sensitive services / terminals are being discussed. Thus, the introduction of next-generation RATs that take into account eMBB (enhanced Mobile Broadband Communication), massive MTC, URLLC (Ultra-Reliable and Low Latency Communication), etc., is being discussed, and in one embodiment of the present invention, for convenience, the relevant technology is referred to as NR (New radio or New RAT).

[0027] The term "base station" as used herein may be replaced by terms such as fixed station, Node B, gNode B (gNB), Access Point (AP), cell, or TRP (transmission and reception point). Repeaters may be replaced by terms such as Relay Node (RN) or Relay Station. The term "terminal" may be replaced by terms such as User Equipment (UE), Mobile Station (MS), MSS (Mobile Subscriber Station), or SS (Subscriber Station).

[0028] To clarify the explanation, 3GPP NR will be used as the primary reference, but the technical concept of this invention is not limited to this.

[0029] The following documents can be referenced for background art, terminology, definitions, and abbreviations related to this invention.

[0030] - 38.211: Physical channels and modulation

[0031] - 38.212: Multiplexing and channel coding

[0032] - 38.213: Physical layer procedures for control

[0033] - 38.214: Physical layer procedures for data

[0034] - 38.215: Physical layer measurements

[0035] - 38.300: NR and NG-RAN Overall Description

[0036] - 38.304: User Equipment (UE) procedures in idle mode and in RRC Inactive state

[0037] - 38.321Medium Access Control (MAC) protocol specification

[0038] - 38.331: Radio Resource Control (RRC) protocol specification

[0039] - 37.213: Introduction of channel access procedures to unlicensed spectrum for NR-based access

[0040] - 36.355: LTE Positioning Protocol

[0041] - 37.355: LTE Positioning Protocol

[0042] Terms and Abbreviations

[0043] - 5GC: 5G Core Network

[0044] - 5GS: 5G System

[0045] - AoA: Angle of Arrival

[0046] - AP: Access Point

[0047] - CID: Cell ID

[0048] - E-CID: Enhanced Cell ID

[0049] - GNSS: Global Navigation Satellite System

[0050] - GPS: Global Positioning System

[0051] - LCS: LoCation Service

[0052] - LMF: Location Management Function

[0053] - LPP: LTE Positioning Protocol

[0054] - MO-LR: Mobile Originated Location Request

[0055] - MT-LR: Mobile Terminated Location Request

[0056] - NRPPa: NR Positioning Protocol A

[0057] - OTDOA: Observed Time Difference Of Arrival

[0058] - PDU: Protocol Data Unit

[0059] - PRS: Positioning Reference Signal

[0060] - RRM: Radio Resource Management

[0061] - RSSI: Received Signal Strength Indicator

[0062] - RSTD: Reference Signal Time Difference

[0063] - ToA: Time of Arrival

[0064] - TP: Transmission Point

[0065] - TRP: Transmission and Reception Point

[0066] - UE: User Equipment

[0067] - SS: Search Space

[0068] - CSS: Common Search Space

[0069] - USS: UE-specific Search Space

[0070] - PDCCH: Physical Downlink Control Channel

[0071] - PDSCH: Physical Downlink Shared Channel;

[0072] - PUCCH: Physical Uplink Control Channel;

[0073] - PUSCH: Physical Uplink Shared Channel;

[0074] - DCI: Downlink Control Information

[0075] - UCI: Uplink Control Information

[0076] - SI: System Information

[0077] - SIB: System Information Block

[0078] - MIB: Master Information Block

[0079] - RRC: Radio Resource Control

[0080] - DRX: Discontinuous Reception

[0081] - RNTI: Radio Network Temporary Identifier

[0082] - CSI: Channel state information

[0083] - PCell: Primary Cell

[0084] - SCell: Secondary Cell

[0085] - PSCell: Primary SCG(Secondary Cell Group) Cell

[0086] - CA: Carrier Aggregation

[0087] - WUS: Wake up Signal

[0088] - TX: Transmitter

[0089] - RX: Receiver

[0090] - RSTD: Reference Signal Time Difference

[0091] - RS: Reference Signal

[0092] - PRS: Positioning Reference Signal

[0093] - SRS: Sounding Reference Signal

[0094] In wireless communication systems, terminals receive information from base stations via the downlink (DL) and transmit information from base stations via the uplink (UL). The information transmitted and received between base stations and terminals includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0095] Figure 1 illustrates the physical channels used in 3GPP NR systems and typical signal transmission methods using them.

[0096] When a terminal is powered on from an off state or enters a new cell, in step S101, it performs initial cell search operations, such as establishing synchronization with the base station. For this purpose, the terminal receives an SSB (Synchronization Signal Block) from the base station. The SSB includes a PSS (Primary Synchronization Signal), an SSS (Secondary Synchronization Signal), and a PBCH (Physical Broadcast Channel). Based on the PSS / SSS, the terminal establishes synchronization with the base station and obtains information such as the cell identity. The terminal also obtains broadcast information within the cell based on the PBCH. In addition, during the initial cell search stage, the terminal can receive a Downlink Reference Signal (DL RS) to check the status of the downlink channel.

[0097] In step S102, terminals that have completed the initial cell search receive a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) based on the information from the Physical Downlink Control Channel, thereby obtaining more specific system information.

[0098] Subsequently, the terminal performs a random access procedure, such as in steps S103 to S106, to complete the connection to the base station. For this purpose, the terminal transmits a preamble via a Physical Random Access Channel (PRACH) (S103) and receives a response message to the preamble via a Physical Downlink Control Channel and its corresponding Physical Downlink Sharing Channel (S104). In the case of contention-based random access on a competitive infrastructure, a contention resolution procedure is performed, such as transmitting further Physical Random Access Channels (S105) and receiving Physical Downlink Control Channels and their corresponding Physical Downlink Sharing Channels (S106).

[0099] A terminal that has performed these procedures then receives the physical downlink control channel / physical downlink shared channel (S107) and transmits the physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) as part of the general uplink / downlink signal transmission procedure (S108). The control information transmitted by the terminal to the base station is collectively referred to as Uplink Control Information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted via PUCCH, but if control information and traffic data need to be transmitted simultaneously, it is transmitted via PUSCH. Furthermore, UCI can be transmitted aperiodically via PUSCH at the request / instruction of the network.

[0100] Figure 2 illustrates the structure of a wireless frame. In NR, uplink and downlink transmissions are composed of frames. A wireless frame has a length of 10ms and is divided into two 5ms half-frames (HF). Each half-frame is divided into five 1ms subframes (SF). Each subframe is divided into one or more slots, and the number of slots within a subframe depends on the SCS (Subcarrier Spacing). Each slot contains 12 or 14 OFDM (Orthogonal Frequency Division Multiplexing) symbols by a CP (cyclic prefix). When a normal CP is used, each slot contains 14 symbols. When an extended CP is used, each slot contains 12 symbols.

[0101] Table 1 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when a general CP is used.

[0102] [Table 1]

[0103] *N slot symb : Number of symbols in the slot

[0104] *N frame,u slot : Number of slots in the frame

[0105] *N subframe,u slot : Number of slots within the subframe

[0106] Table 2 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when the extended CP is used.

[0107] [Table 2]

[0108] The frame structure shown is merely an example; the number of subframes, slots, and symbols within a frame can be varied in many ways.

[0109] In an NR system, OFDM pneumatics (numerology, e.g., SCS) can be configured to differ between multiple cells merged into a single terminal. This allows the (absolute time) intervals of time resources (e.g., SF, slots, or TTI) (collectively referred to as TU (Time Unit) for convenience), which consist of the same number of symbols, to differ between the merged cells. Here, symbols include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbols).

[0110] Figure 3 illustrates a resource grid for slots. A slot contains multiple symbols in the time domain. For example, in the case of a general CP, one slot contains 14 symbols, while in the case of an extended CP, one slot contains 12 symbols. A carrier wave contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Body Wave Point) is defined as multiple consecutive PRBs (Physical RBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier wave contains a maximum of N (e.g., 5) BWPs. Data communication takes place on activated BWPs, and only one BWP is activated per terminal. In the resource grid, each element is called a Resource Element (RE), and one complex symbol can be mapped to it.

[0111] Figure 4 shows an example of how physical channels are mapped within a slot. In an NR system, a frame is characterized by a self-contained structure in which the DL control channel, DL or UL data, and UL control channel are all contained within a single slot. For example, the first N symbols in a slot are used for transmitting the DL control channel (e.g., PDCCH) (hereinafter referred to as the DL control area), and the last M symbols in the slot are used for transmitting the UL control channel (e.g., PUCCH) (hereinafter referred to as the UL control area). N and M are integers greater than or equal to 0. The resource area (hereinafter referred to as the data area) between the DL control area and the UL control area is used for transmitting DL data (e.g., PDSCH) or UL data (e.g., PUSCH). The GP provides a time gap during the process of the base station and terminal switching from transmission mode to reception mode or from reception mode to transmission mode. Some symbols at the point in time when switching from DL to UL within a subframe can be set as the GP.

[0112] The PDCCH carries DCI (Downlink Control Information). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation for the DL-SCH (downlink shared channel), resource allocation information for the UL-SCH (uplink shared channel), paging information for the PCH (Paging Channel), system information on the DL-SCH, resource allocation information for higher-level control messages such as random connection responses transmitted on the PDSCH, transmission power control commands, and activation / deactivation of CS (Configured scheduling). The DCI includes a CRC (cyclic redundancy check), which is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with a terminal identifier (e.g., Cell-RNTI, C-RNTI). If the PDCCH is related to paging, the CRC is masked with P-RNTI (Paging-RNTI). If the PDCCH relates to system information (e.g., System Information Block, SIB), the CRC is masked with SI-RNTI (System Information RNTI). If the PDCCH relates to random connection responses, the CRC is masked with RA-RNTI (Random Access-RNTI).

[0113] Figure 5 illustrates the PDSCH reception and ACK / NACK transmission process. Referring to Figure 5, the terminal detects a PDCCH in slot #n, where the PDCCH contains downlink scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH indicates the DL assignment-to-PDSCH offset (K0) and the PDSCH-HARQ-ACK reporting offset (K1). After the terminal receives the PDSCH from slot #(n+K0) according to the scheduling information for slot #n, and then finishes receiving the PDSCH in slot #n1 (where n+K0≦n1), it transmits a UCI via PUCCH in slot #(n1+K1). Here, the UCI contains the HARQ-ACK response to the PDSCH. If the PDSCH is configured to transmit at most one TB, the HARQ-ACK response consists of 1 bit. When a PDSCH is configured to transmit up to two TBs, the HARQ-ACK response consists of 2 bits if spatial bundling is not configured, and 1 bit if spatial handling is configured. If the HARQ-ACK transmission time for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes the HARQ-ACK responses for multiple PDSCHs.

[0114] Figure 6 illustrates the PUSCH transmission process. Referring to Figure 6, the terminal detects a PDCCH in slot #n, where the PDCCH contains uplink scheduling information (e.g., DCI format 0_0, 0_1). The terminal transmits a PUSCH in slot #(n+K2) according to the scheduling information in slot #n, where the PUSCH contains a UL-SCH TB.

[0115] RedCap (Reduced Capability) terminal

[0116] In recent years, in addition to the main use cases of 5G (mMTC, eMBB, and URLLC), there has been growing importance and interest in use case areas that span mMTC and eMBB, or mMTC and URLLC. Consequently, there is a growing need for terminals that can efficiently support these use cases from the perspectives of device cost, power consumption, and form factor. Terminals for such purposes can be defined as (NR)RedCap (reduced capability) UE / devices. Furthermore, to distinguish them from RedCap devices, general NR terminals that support all or one or more of the main use cases of 5G can be defined as NR(normal)UE / devices or non-RedCap UE / devices. A RedCap UE may be a terminal that intentionally reduces some of the key 5G capabilities (maximum data transmission rate, user experience data transmission rate, latency, mobility, connectivity density, energy efficiency, spectral efficiency, and regional traffic efficiency) as defined in IMT-2020, in order to achieve all or part of low device cost / complexity, low power consumption, and a small form factor.

[0117] For convenience, the domain of 5G use cases spanning mMTC and eMBB, or mMTC and URLLC, which are target use cases for Redcap devices, will be referred to as "redcap use cases." Examples of redcap use cases include the following:

[0118] (1) Connecting industries

[0119] 1) Sensors and actuators can connect to the 5G network and core.

[0120] - Includes use cases and requirements for large-scale IWSNs (Industrial Wireless Sensor Networks).

[0121] - A relatively low-cost service requiring not only a URLLC service with very high requirements, but also a small device form factor with a battery life of several years.

[0122] - The requirements for this service are higher than those for LPWA (Low Power Wide Area, i.e., LTE-M / NB-IOT), but lower than those for URLLC and eMBB.

[0123] - Devices in such environments include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, and the like.

[0124] 2) Smart City

[0125] - The vertical areas of smart cities include data collection and processing to more efficiently monitor and control urban resources and to provide services to urban residents. In particular, the placement of surveillance cameras is an essential element not only in smart cities but also in factories and industrial sites.

[0126] 3) Wearable

[0127] Wearable use cases include smartwatches, rings, eHealth-related devices, and medical monitoring devices. One characteristic of these use cases is the small size of the devices.

[0128] Redcap use cases may be unsupportable for LPWA (Low Power Wireless Area) terminals (e.g., LTE-M, NB-IoT, etc.) in terms of bit rate, latency, etc., and while NR terminals can functionally support them, they may be inefficient in terms of terminal manufacturing cost, form factor, and battery life. Supporting these use case areas in 5G networks with redcap terminals that have characteristics such as low cost, low power consumption, and small form factor can result in reduced terminal manufacturing and maintenance costs. Redcap use cases have quite diverse requirements in terms of terminal complexity, target bit rate, latency, and power consumption. These redcap requirements can be divided into generic requirements that apply to all redcap use cases and requirements that apply only to specific use cases. Some representative generic and use case specific requirements can be defined as shown in [Table 3] below.

[0129] [Table 3]

[0130] The above redcap requirements are met by various features (combinations) provided by the terminal and base station, but the following are examples of features and sub-features that the terminal / base station assists in meeting the redcap requirements.

[0131] i.Complexity reduction features:

[0132] - Reduced number of UE RX / TX antennas

[0133] - UE bandwidth reduction

[0134] - Half-Duplex-FDD

[0135] - Relaxed UE processing time

[0136] -Relaxed UE processing capability

[0137] ii. Power saving:

[0138] - Reduced PDCCH monitoring by smaller numbers of BDs and CCE limits

[0139] - Extended DRX for RRC Inactive and / or Idle

[0140] - RRM relaxation for stationary devices

[0141] iii.Coverage recovery / enhancement

[0142] SRS (sounding reference signal)

[0143] SRS is a UL reference signal transmitted by the terminal and received by the base station. Based on the SRS, the base station can perform link adaptation, DL channel estimation using channel reciprocity properties, UL beam management, UL precoding, and / or acquire UL measurements.

[0144] The terminal receives SRS configuration information provided by the base station (e.g., TS38.331 SRS-Config IE) and can determine the parameters for SRS transmission based on this information. The SRS configuration consists of a list of SRS-Resources, SRS-PosResources, SRS-ResourceSets, and SRS-PosResourceSets, where each of the SRS-ResourceSets and SRS-PosResourceSets contains a set of SRS-Resources and SRS-PosResources.

[0145] SRS can be divided into three resource types depending on the time resource settings and transmission method.

[0146] For SRS with the resource type set to periodic, the terminal determines where the SRS resource will be transmitted based on the configured period and offset set in the RRC, and transmits the SRS periodically without further signaling if configured.

[0147] For SRS with the resource type set to semi-persistent, the terminal determines the location where the SRS resource will be transmitted based on the configured period and offset set in the RRC. Then, if the SRS transmission is activated by MAC CE, the terminal begins the instructed periodic transmission of the SRS. If deactivated by MAC CE, the terminal stops transmitting the SRS.

[0148] For SRS resources set to aperiodic, the terminal transmits the instructed SRS, reflecting the offset position set in the RRC, relative to the time of receipt of the DCI instructing triggering for that SRS resource set.

[0149] Positioning

[0150] Positioning refers to measuring radio signals to determine the geographical location and / or speed of user equipment (UE). Location information is requested and reported to clients associated with the UE (e.g., applications). Location information may also be contained within a core network or requested by clients connected to the core network. The location information is reported in a standard format, such as cell-based or geographic coordinates, and may include estimated error values ​​for the UE's location and speed, and / or the positioning method used for positioning.

[0151] Figure 7 shows an example of a positioning protocol configuration for measuring the location of a device.

[0152] Referring to Figure 7, LPP is used as a point-to-point interface between a location server (E-SMLC and / or SLP and / or LMF) and a target device (UE and / or SET) to position the target device using position-related measurements obtained from one or more reference sources. Through LPP, the target device and the location server exchange measurement and / or position information based on signals A and / or B.

[0153] NRPPa is used for information exchange between the reference source (ACCESS NODE and / or BS and / or TP and / or NG-RAN node) and the location server.

[0154] The functions provided by the NRPPa protocol include the following:

[0155] - E-CID Location Information Transfer. This function allows for the exchange of location information between the reference source and the LMF for the purpose of E-CID positioning.

[0156] - OTDOA Information Transfer. This function allows information to be exchanged between the reference source and the LMF for the purpose of OTDOA positioning.

[0157] - Reporting of General Error Situations. This feature reports general error situations for which error messages are not defined for each function.

[0158] Positioning methods supported by NG-RAN include GNSS (Global Navigation Satellite System), OTDOA, E-CID (enhanced cell ID), barometric pressure sensor positioning, WLAN positioning, Bluetooth® positioning, TBS (terrestrial beacon system), and UTDOA (Uplink Time Difference of Arrival). The position of the UE can be measured using any one of the above positioning methods, or it may be measured using two or more positioning methods.

[0159] OTDOA(Observed Time Difference Of Arrival)

[0160] Figure 8 shows an example of an OTDOA (observed time difference of arrival) positioning method.

[0161] The OTDOA positioning method uses the measurement timing of downlink signals received by the UE from multiple TPs, including eNBs, ng-eNBs, and PRS-dedicated TPs. The UE measures the timing of the received downlink signals using positional aid data received from a position server. The UE's position is then determined based on these measurement results and the geographical coordinates of adjacent TPs.

[0162] A UE connected to a gNB can request a measurement gap from a TP for OTDOA measurement. If the UE is unable to recognize the SFN for at least one TP in the OTDOA auxiliary data, it will use an autonomous gap to obtain the SFN of the OTDOA reference cell before requesting a measurement gap for the RSTD (Reference Signal Time Difference) measurement.

[0163] Here, RSTD is defined based on the smallest relative time difference between the boundaries of two subframes received from the reference cell and the measurement cell, respectively. That is, it is calculated based on the relative time difference between the start time of the subframe in the reference cell closest to the start time of the subframe received from the measurement cell. The reference cell, on the other hand, is selected by the UE.

[0164] For accurate OTDOA measurement, it is necessary to measure the TOA (time of arrival) of signals received from three or more geographically dispersed TPs or base stations. For example, by measuring the TOA for each of TP 1, TP 2, and TP 3, and calculating the RSTD for TP 1-TP 2, TP 2-TP 3, and TP 3-TP 1 based on the three TOA values, a geometric hyperbola can be determined, and the point where this hyperbola intersects can be estimated as the location of the UE. In this case, there may be accuracy and / or uncertainty for each TOA measurement, and the estimated UE location may be known by a predetermined range due to the uncertainty of the measurement.

[0165] For example, the RSTD for two TPs is calculated based on Equation 1.

[0166] [Number]

[0167] c is the speed of light, {x t , y t} are the (unknown) coordinates of the target UE, {x i , y i} are the (known) coordinates of the TP, and {x1, y1} are the coordinates of the reference TP (or another TP). Here, (T i - T1) is the transmission time offset between two TPs, which is referred to as "Real Time Differences" (RTDs), and n i , n1 indicate values related to the UE TOA measurement error.

[0168] E-CID (Enhanced Cell ID)

[0169] In the cell ID (CID) positioning method, the location of the UE can be measured by the geographical information of the serving ng-eNB, serving gNB, and / or serving cell of the UE. For example, the geographical information of the serving ng-eNB, serving gNB, and / or serving cell is obtained by paging, registration, etc.

[0170] On the other hand, the E-CID positioning method can utilize additional UE measurements and / or NG-RAN radio resources to improve UE position estimates, in addition to the CID positioning method. While the E-CID positioning method can utilize some measurement methods similar to those of the RRC protocol's measurement control system, generally, additional measurements are not performed solely for the purpose of measuring the UE's position. In other words, a separate measurement configuration or measurement control message may not be provided to measure the UE's position, and the UE may not expect to be required to perform additional measurement operations solely for position measurement, and can report measurements obtained by measurement methods that are generally measurable by the UE.

[0171] For example, the serving gNB implements the E-CID positioning method using E-UTRA measurements provided by the UE.

[0172] The following describes examples of measurement elements that can be used for E-CID positioning.

[0173] - UE Measurements: E-UTRA RSRP (Reference Signal Received Power), E-UTRA RSRQ (Reference Signal Received Quality), UE E-UTRA Receive-Transmit Time Difference (Rx-Tx Time difference), GERAN / WLAN RSSI (Reference Signal Strength Indication), UTRAN CPICH (Common Pilot Channel) RSCP (Received Signal Code Power), UTRAN CPICH Ec / Io

[0174] - E-UTRAN measurement: ng-eNB receive-transmit time difference (Rx-Tx Time difference), Timing Advance (T ADV ), Angle of Arrival (AoA)

[0175] Here, T ADV These are divided into Type 1 and Type 2, as follows:

[0176] T ADV Type 1 = (Time difference between receiving and transmitting ng-eNB) + (Time difference between receiving and transmitting UE E-UTRA)

[0177] T ADV Type 2 = ng-eNB receive-transmit time difference

[0178] On the other hand, AoA is used to measure the direction of the UE. AoA is defined as the estimated angle relative to the UE's position, measured counterclockwise from the base station / TP. In this case, the geographical reference direction is north. The base station / TP can use uplink signals such as SRS (Sounding Reference Signal) and / or DMRS (Demodulation Reference Signal) for AoA measurement. Also, the larger the antenna array arrangement, the higher the accuracy of the AoA measurement, and if the antenna array is arranged at the same interval, the signals received by adjacent antenna elements will have a certain phase rotation.

[0179] UTDOA(Uplink Time Difference of Arrival)

[0180] UTDOA is a method for determining the location of an UE by estimating the arrival time of an SRS signal. When calculating the estimated SRS arrival time, the serving cell can be used as a reference cell, and the location of the UE can be estimated by the difference in arrival times with other cells (or base stations / TPs). To implement UTDOA, the E-SMLC instructs the target UE's serving cell to direct SRS transmission to the target UE. The E-SMLC also provides configurations such as periodic / aperiodic, bandwidth, and frequency / group / sequence hopping for the SRS.

[0181] Multi-RTT (Round Trip Time)

[0182] Figure 9 shows an example of a Multi RTT (round trip time) positioning method.

[0183] Referring to Figure 9(a), an example of an RTT process is illustrated in which TOA measurement is performed by an initiating device and a responding device, and the responding device provides the TOA measurement to the initiating device for RTT measurement (calculation). For example, the initiating device is a TRP and / or terminal, and the responding device is a terminal and / or TRP.

[0184] The starting device transmits an RTT measurement request, and the responding device receives it (1301).

[0185] The starting device transmits an RTT measurement signal at t0, and the response device acquires a TOA measurement at t1 (1303).

[0186] The response device transmits the RTT measurement signal at t2, and the activation device acquires the TOA measurement at t3 (1305).

[0187] The response device transmits information regarding [t2-t1], and the activation device receives this information and calculates the RTT based on equation 2 (1307). This information may be transmitted or received based on another signal, or it may be transmitted or received included in the RTT measurement signal (1305).

[0188]

number

[0189] Referring to Figure 9(b), the RTT corresponds to a double-range measurement between the two devices. Positioning estimation is performed from this information. Based on the measured RTT, d1, d2, and d3 are determined, and the target device location is determined by the intersection of circles with each BS1, BS2, BS3 (or TRP) as the center and each d1, d2, and d3 as the radius.

[0190] NG-RAN positioning structure and procedures

[0191] Figure 10 shows the positioning structure of the NG (next generation) RAN (radio access network). NR RAN is also referred to as NR RAN or 5G RAN.

[0192] The AMF receives a request for certain location services related to a specific target UE from another entity (e.g., a GMLC or UE), or decides to initiate certain location services on behalf of a specific target UE (e.g., an IMS emergency call). The AMF then sends a location service request to the LMF. The LMF can process the location service request, which includes transmitting assistance data to the target UE and / or positioning the target UE for UE-based and / or UE-assisted positioning. The LMF sends the location service results (e.g., a location estimate for the UE) to the AMF. In the case of location services requested by an entity other than the AMF (e.g., a GMLC or UE), the AMF sends the location service results to that entity.

[0193] NG-RAN nodes can control TRP / TPs such as RRM or DL-PRS only TPs to support TBS on a PRS-based system.

[0194] LMF can connect to E-SMLC to access UTRAN information.

[0195] The LMF connects to the SLP, which is responsible for specifying the position relative to the user plane.

[0196] Figure 11 shows an example of a location service supported by NG-RAN.

[0197] When the UE is in the CM-IDLE state, and the AMF receives a Location Service Request, the AMF initiates a Network Trigger Service Request to configure signaling for connection with the UE and assignment of a specific serving gNB / ng-eNB. In Figure 11, it is assumed that the UE is in connected mode.

[0198] A location service request to the UE is triggered, and the location service request to the UE is one of 1101, 1102, or 1103. For example, a 5GC entity (e.g., GMLC) requests some location services (e.g., positioning) for the target UE from the Serving AMF (1101), the Serving AMF triggers some location services for the target UE itself (e.g., to locate the UE for an emergency call) (1102), or the UE requests some location services (e.g., positioning or assistance data transmission) from the Serving AMF at the NAS level (1103).

[0199] The AMF transmits the location service request to the LMF (1104).

[0200] The LMF provides service on the NG-RAN to acquire location measurement or support data and initiates positioning procedures with nearby ng-eNB / gNB (1105).

[0201] (Instead of or in addition to step 1105) The LMF initiates a positioning procedure with the UE to obtain a location estimate or positioning measurement, or to transmit location-assistant data to the UE (1106).

[0202] The LMF provides the AMF with location service responses (1107) (e.g., indication of success or failure, request and location estimation for the UE if obtained).

[0203] (In the case of 1101) AMF provides a location service response to the 5GC entity (1108) (e.g., location estimation for UE).

[0204] (In the case of 1102), the AMF uses the location service response received in step 1107 to support the service that triggered it in step 1102 (1109) (for example, providing the GMLC with location estimation related to the emergency call).

[0205] (In the case of 1103) The AMF provides a location service response to the UE (1110) (e.g., location estimation for the UE).

[0206] SRS (Sounding Reference Signal) for positioning.

[0207] In Rel.15 NR systems, periodic, non-periodic, and semi-persistent Rel.15 SRS can be transmitted by base stations for the measurement of UL RTOA (UL-Relative Time of Arrival), UL SRS-RSRP, and UL-AOA (UL-Angle of Arrival), thereby supporting UL TDOA and UL AOA.

[0208] In the Rel.16 / 17 NR system, periodic, non-periodic, and semi-persistent SRS for positioning can be transmitted by base stations to measure the Rx-Tx time difference of UL RTOA, UL SRS-RSRP, UL-AOA, and gNB, thereby supporting UL TDOA, UL AOA, and multi-RTT.

[0209] The RRC parameters set for an SRS differ depending on its intended use. For example, in the case of an SRS for positioning, the settings are indicated by SRS-PosResources and SRS-PosResourceSet, while in the case of an SRS used for other purposes (e.g., Rel.15 SRS), the settings are indicated by SRS-Resources and SRS-ResourceSet.

[0210] To avoid confusion between SRS for positioning and SRS used for other purposes, SRS for positioning will be referred to as SRS-p below, and SRS used for other purposes (e.g., beam management) will be referred to as SRS-m. Unless otherwise specified in the following new proposals, SRS can be interpreted as meaning SRS-p.

[0211] The SRS resource mapping method in the time / frequency domain on a resource grid (e.g., Figure 3) is defined in the standard documentation. In the case of SRS-m, repetition can be set within a slot, and intra-slot frequency hopping using this is supported. However, in the case of SRS-p, based on the current NR standard (Rel-17), intra-slot repetition cannot be set, and intra-slot frequency hopping is not supported. In the case of periodic / semi-persistent SRS-m, inter-slot frequency hopping is supported in a periodic form.

[0212] SRS-p settings are provided based on the terminal's serving cell (or camp on cell), and SRS-p transmitted by the terminal based on the SRS-p settings can be received by one or more cells (or TRPs) including that serving cell.

[0213] For example, SRS-p can be set by the RRC parameters SRS-PosResourceSet and SRS-PosResource, which are defined in the TS38.331 standard. Specifically, when the higher-level parameter SRS-PosResource is set for an SRS (i.e., SRS-p) and the higher-level parameter SpatialRelationInfoPos is set, the ID of the configuration field of the reference signal is provided. The reference RS can be an SRS, CSI-RS, SS / PBCH block, DL PRS of a serving cell, or DL ​​PRS configured in an SS / PBCH block, all set by the higher-level parameter SRS-Resource or SRS-PosResource.

[0214] The UE is not expected to transmit multiple SRS resources with different spatial relationships within the same OFDM symbol.

[0215] If the higher-level parameter SpatialRelationInfoPos is not set, the terminal can use a fixed spatial domain transmission filter or another spatial domain transmission filter for transmitting SRS-p set by the higher-level parameter SRS-PosResource across multiple SRS resources.

[0216] In RRC_CONNECTED mode, the terminal transmits SRS-p, which is set by the higher-level parameter SRS-PosResource, within the active UL BWP.

[0217] For each SRS-p resource, only one RS source is provided for the higher-level parameter SpatialRelationInfoPos.

[0218] When operating on the same carrier, if SRS-p conflicts with a scheduled PUSCH, SRS-p is dropped at the conflicting symbol.

[0219] The terminal does not expect the SRS-PosResource to be set on the carrier of a serving cell that has a slot format consisting of DL / UL symbols that are not set for PUSCH / PUCCH transmission.

[0220] Depending on the UE's capabilities, an SRS-p resource associated with the initial UL BWP can be configured, and the SRS-p resource is transmitted within the initial UL BWP during RRC_INACTIVE mode with the same CP and subcarrier interval as configured for the initial UL BWP. Depending on the UE's capabilities, an SRS-p resource for positioning can be configured outside the initial BWP in RRC_INACTIVE mode, and the frequency position and bandwidth, subcarrier interval and CP length for SRS-p transmission can be configured. An SRS-p resource configured outside the initial BWP in RRC_INACTIVE mode is configured with the same bandwidth and CC as the initial UL BWP.

[0221] ISAC(Integrated Sensing And Communication)

[0222] In recent years, various methods for utilizing wireless sensing in wireless communication systems have been discussed. Generally, conventional radar technology is considered as a method for wireless sensing, but radar technology is specialized for sensing and does not take into account the characteristics of communication, and it has limitations in that the transmitting and receiving nodes require separate equipment to send and receive signals for wireless sensing. To solve these problems, methods for utilizing wireless sensing in wireless communication systems that support communication using cellular networks, such as 5G and / or next-generation 6G (e.g., ISAC or JCAS (Joint Communication And Sensing)) have been actively researched in recent years.

[0223] In 3GPP standardization, research has been initiated to support ISACs for 5G / 6G. In the TR 22.837 document issued by the 3GPP SA1 WG, radio sensing is defined as a technique for acquiring information about the characteristics of the environment and / or surrounding objects, using radio waves to measure distance, angle or instantaneous velocity. In this context, scenarios in which sensing and communication share the same frequency band and hardware are considered, and methods may be considered in which radio waves for sensing share / reuse radio waves for communication (e.g., use of reference signals for communication (e.g., SSB, DMRS, CSI-RS and / or SRS)), or in which radio waves for radio sensing are designed separately.

[0224] Generally, wireless sensing supported by ISACs can be considered to be performed through the process in which a signal transmitted at the transmitting end is reflected by a target object and received at the receiving end, and sensing modes for scenarios can be defined depending on the relationship between the transmitting and receiving ends. Based on whether the transmitting and receiving ends are the same, the case where the transmitting and receiving ends are the same can be defined as mono-static sensing mode, and the case where the transmitting and receiving ends are different can be defined as bi-static sensing mode.

[0225] Figure 12 shows an example of a wireless sensing mode supported by ISAC.

[0226] Referring to Figure 12, when considering the transmission and reception operations in the 3GPP standard and the nodes participating in them, the sensing modes can be broadly classified as follows.

[0227] (a) BS mono-static sensing mode: A BS that has transmitted radio waves receives the reflected signal.

[0228] (b) BS-to-BS bi-static sensing mode: A system where one BS receives the reflected signal of radio waves transmitted by another BS.

[0229] (c) BS-to-UE bi-static sensing mode: The UE receives the signal that has been reflected from the radio waves transmitted by the BS.

[0230] (d) BS mono-static sensing mode: The UE that transmitted the radio wave receives the reflected signal.

[0231] (e) UE-to-UE bi-static sensing mode: One UE receives the reflected signal of radio waves transmitted by another UE.

[0232] (f) UE-to-BS bi-static sensing mode: The BS receives the reflected signal of the radio waves transmitted by the transmitting UE.

[0233] However, in addition to the six use cases mentioned above, sensing modes that include multiple transmit / receive nodes may be referred to as multi-static sensing modes.

[0234] Wireless sensing using ISAC / JCAS is being explored for application in various scenarios. Generally, wireless sensing aims to acquire information about objects that do not have (or are unrelated to) communication modules, and possible scenarios can be broadly categorized into three types, as follows:

[0235] (1) Object detection and tracking: This is a scenario for sensing target objects or people and tracking their location information. Typical examples include sensing intruders in indoor / outdoor environments, tracking the location of UAVs or AGVs, and autonomous driving assistance scenarios.

[0236] (2) Environment monitoring: This is a scenario aimed at collecting information about the surrounding environment of the transmitting / receiving nodes. Typical examples include rainfall observation and flood sensing scenarios.

[0237] (3) Motion monitoring: This is a scenario for sensing the movement of an object, and typical examples include scenarios for identifying human movements and gestures.

[0238] The performance metrics and their levels required in each of the aforementioned scenarios are diverse and can differ from one another. In order to design an ISAC / JCAS that is suitable for the service quality required in each scenario, it is necessary to consider various key performance requirements. The 3GPP standard TS 22.137 document defines the key performance requirements for each service scenario as positioning accuracy, speed estimation accuracy, confidence level, sensing resolution, missed detection probability, false alarm probability, maximum delay of sensing service, and refresh rate, and the required level for each key performance requirement can differ depending on the service scenario.

[0239] The radio frequency sensing function can provide a service for object position detection without the need to connect to an object through a device in the network. The function of obtaining range, velocity, and angle information from radio frequency signals can provide a wide range of new functions such as various object sensing, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision position detection, tracking, and activity recognition. The radio sensing service can provide information to various industries (e.g., unmanned aircraft, smart home, V2X, factories, railways, public safety, etc.) that enable applications such as intruder sensing, vehicle assisted driving and navigation, trajectory tracking, collision avoidance, traffic management, health, and traffic management. In some cases, radio sensing can further use non-3GPP type sensors (e.g., radar, camera) to assist 3GPP base sensing. For example, the operation of the radio sensing service, i.e., the sensing operation, depends on the transmission, reflection, and scattering processing of radio sensing signals. Therefore, radio sensing can provide an opportunity to enhance a conventional communication system from a communication network to a wireless communication and sensing network.

[0240] Figures 13 and 14 show an example in which ISAC is applied to a 3GPP wireless communication system. The embodiments of Figures 13 and 14 can be combined with various embodiments of the present disclosure. Specifically, Figure 13 shows an example of sensing (e.g., monostatic sensing) using a sensing receiver and a sensing transmitter at the same position, and Figure 14 shows an example of sensing (e.g., bistatic sensing) using a separated sensing receiver and a sensing transmitter.

[0241] The proposals discussed below are also applicable to the aforementioned ISAC environment.

[0242] Frequency hopping (FH) of SRS for positioning

[0243] Briefly summarizing the problems of the prior art related to the matters discussed below and the motivation related to the embodiments proposed in the present disclosure, it is as follows.

[0244] - In order to improve the positioning performance during the transmission of SRSp by the RedCap terminal, the application of frequency hopping is required. However, the RedCap terminal requires a relatively long switching delay (e.g., RF retuning) for hopping and will transmit across multiple slots.

[0245] - While the frequency hopping operation of SRSp is being performed, the transmission operations of other UL signals / channels are hindered, resulting in waste of resources. Therefore, in order to prevent this waste of resources, it is necessary to complete the frequency hopping operation in the shortest possible time.

[0246] - In the conventional Rel-17 standard, the transmission operation of the SRSp resource is performed in slot units. As an example to solve such problems, a transmission method across slot boundaries can be proposed.

[0247] 3GPP has been promoting standardization and technological development to support a variety of devices, including not only conventional mobile terminals but also MTC / NB-IoT. As one of these technologies, Reduced Capability (RedCap) NR was introduced in Rel-17, which reduces the capability of conventional NR, requires cost gains, is not very sensitive to data rates, and is less important from a latency perspective. Devices that support RedCap include wearables, industrial wireless sensors, and video surveillance equipment, and gains in capability are achieved by reducing the supported bandwidth, reducing the maximum number of supported MIMO layers, modulation order, and Rx branches, and supporting half-duplex (HD) across the entire bandwidth.

[0248] Currently, the 3GPP NR Rel-18 standard has the following target requirements for positioning accuracy for RedCap terminals, and most experiments have shown that these target requirements in Table 4 are not met. In the case of RedCap terminals, the maximum frequency bandwidth they support is smaller than that of conventional NR-supporting terminals (normal UEs), which may result in a decrease in performance in terms of decoding / detection accuracy of transmitted and received reference signals. Accordingly, frequency hopping is being discussed to improve the positioning accuracy of RedCap terminals.

[0249] [Table 4]

[0250] As mentioned above, for a RedCap terminal to perform frequency hopping transmission, RF retuning for shifting frequency bands is required, and switching delays between hops are necessary, which can increase the total transmission time of SRSp resources. Since increased resource transmission time will limit the transmission of other signals or channels, minimizing resource transmission time using frequency hopping is required for efficient resource allocation. The current NR Rel-17 standard supports time-domain resource allocation for SRSp resources on a slot basis.

[0251] Based on these characteristics and problems, we propose a time-domain resource allocation method for frequency hopping operations to support improved accuracy and efficient resource allocation of positioning technology on the RedCap UE UL SRS platform.

[0252] This specification describes a proposed method based on the 3GPP NR system, focusing on UL SRS-based positioning techniques. However, the proposed method is not limited to this and is generally applicable to other positioning techniques and various RS systems capable of measuring terminal positioning. The proposed method is applicable to all types of transmission and reception schemes and positioning techniques expected by base stations and terminals.

[0253] The methods proposed herein may be implemented independently without being combined with other methods, or they may be implemented in a combined and coordinated form. Some terms, symbols, and sequences used may be replaced with other terms, symbols, and sequences.

[0254] [Proposal 1] Improved resource mapping for conventional SRSp resource mapping and frequency hopping in the time domain.

[0255] Proposal 1 proposes an efficient time-domain resource allocation method that reduces the time gap between hops in the frequency hopping operation of SRSp resources by mapping one or more hops within a single slot.

[0256] The current NR Rel-17 standard supports time-domain resource allocation for SRSp resources on a slot-by-slot basis, allowing for improved resource mapping schemes in frequency-hopping operations that do not consider slot units. In the current standard, in-slot time-domain resource mapping for semi-persistent or periodic SRSp resources is performed by specifying the start position and symbol length parameters.

[0257] As an example of improvement, a method can be considered in which additional resource mapping parameters related to frequency hopping are defined and a combination of said parameters is used. Specifically, if frequency hopping operation of a terminal is expected, additional time-domain resource mapping configuration information related to frequency hopping operation can be specified, and said configuration information can specify the hop-to-hop switching delay (e.g., in units of symbols) and the number of hops. In this case, among the parameters related to time-domain resource mapping of SRSp resources supported by the conventional NR Rel-17 standard, the value of the parameter specifying the symbol length can be interpreted and operated as the symbol length of one hop.

[0258] Figure 15 schematically shows an example of a frequency hopping operation as proposed above, where each SRSp resource consists of a total of five hops, each consisting of two symbols, and there is a hop-to-hop time gap (FC203) of three symbols across the slot (FC204), with each block representing a symbol constituting the SRSp resource. As mentioned above, the time domain start position (FC201) of the frequency hopping operation can be set by the start position parameter value in the resource mapping settings of the conventional SRSp resource, and the number of symbols in each hop can be set by the nrof symbol parameter value in the resource mapping settings. When frequency hopping operation of a terminal is expected, the hop-to-hop time gap (FC203) can be set by the switching delay parameter per hop symbol in the time domain resource mapping setting information related to the additional frequency hopping operation, and the number of hops for the overall frequency hopping operation can be set by the parameter indicating the number of hops in the setting information.

[0259] The terminal can obtain configuration information related to the time-domain resource mapping of SRSp resources provided by the base station. For example, if the terminal is a RedCap terminal, it can additionally obtain time-domain resource mapping configuration information related to frequency hopping provided by the base station, in which case the terminal can expect SRSp resource transmission operation using frequency hopping. The terminal can use the received time-domain resource mapping configuration information related to frequency hopping to perform frequency hopping transmission operation for the SRSp resource. Specifically, the time-domain frequency hopping operation can be defined using the start position and symbol count parameters in the time domain supported by the NR Rel-17 standard, and the aforementioned switching delay and hop count parameters, and it is expected that this frequency hopping operation can operate even across slot boundaries. At the time of SRSp resource transmission configured / instructed by the received SRSp resource mapping configuration information, the terminal performs frequency hopping operation for the SRSp resource and transmits it.

[0260] The base station can provide the terminal with the configuration information of the SRSp resource instructed by the LMF. As an example, when the target terminal is a RedCap terminal, the time-domain resource mapping configuration information related to frequency hopping can be additionally transmitted. Then, at the time of transmitting the configured / instructed SRSp resource, the base station receives the SRSp resource transmitted from the terminal at the configured / instructed frequency resource position, combines the received hops, performs measurements for positioning, and then reports the measurement results to the LMF.

[0261] In the case of Proposal 1, the LMF can selectively additionally transmit the configuration information related to the frequency hopping operation via the base station. The LMF receives the positioning-related measurements measured using the SRSp resource transmitted from the terminal reported by the base station, and through these measurements, the LMF can estimate the position of the terminal by calculation.

[0262] Proposal 1 can reduce the total required time in the time domain during frequency operation and the possibility of collision with other uplink signals or channels by minimizing the time gap between repetitions ( / hops) of the resource in the frequency hopping operation of the SRSp resource. Also, there is an advantage that the quality of uplink data transmission can be improved while maintaining the performance of positioning accuracy.

[0263] [Proposal 2] Resource mapping at slot boundaries

[0264] A processing operation method at the slot boundary in the resource mapping of the SRSp resource performing the frequency hopping operation is proposed.

[0265] As mentioned above, the current NR Rel-17 standard supports time-domain resource allocation for SRSp resources on a slot basis, and consequently, most terminal transceivers are also implemented on a slot basis. Therefore, it is necessary to prevent the transmission of SRSp resources from crossing slot boundaries. To this end, we can consider two methods: one that considers slot boundaries when mapping SRSp resources to ensure that they do not cross slot boundaries, and another that, if an SRSp resource allocated by resource mapping crosses a slot boundary, splits the hop and repeats it. These will be explained separately in Proposal 2-1 and Proposal 2-2.

[0266] Proposal 2-1. Repeated allocation based on (sub)slot boundaries (= resource mapping in repeating units (single hop))

[0267] Proposal 2-1 proposes a method for time-domain resource mapping of SRSp resource hops so that a single hop does not cross a slot boundary during SRSp frequency hopping operation.

[0268] To prevent a single hop from crossing a slot boundary during SRSp frequency hopping, several methods can be considered for time-domain resource mapping of SRSp resource hops: restricting the starting position according to the symbol length of each hop; shifting hops that cross boundaries at the symbol level in the time domain; and duplicating the hopping pattern in slot units based on the boundary. Each of these will be explained separately as Option 1, Option 2, and Option 3.

[0269] (Option 1) Starting position restriction based on hop symbol length

[0270] (i) Option 1-1

[0271] When setting the starting position, the number of symbols per hop, and the inter-hop switching delay (e.g., in units of symbols) according to Proposal 1, it is possible to prevent hops from touching slot boundaries during frequency hopping operation of SRSp resources by setting the resource mapping by restricting the setting of the starting position based on the sum of the number of symbols per hop and the inter-hop switching delay (e.g., in units of symbols).

[0272] As a specific example, the number of symbols in one slot is N. symbol slot The sum of the number of hops that can be configured for an SRSp resource and the inter-hop switching delay (in symbols) is N. symbol hop,total Therefore, N symbol hop,total is 1 / 2*N symbol slot (For example, N symbol slot If = 14, then if it is greater than 7), the following formula calculates the transmission start time domain position l_0 of the SRSp resource in the slot. offset The corresponding starting position parameter value is N symbol hop,total It can be restricted by N. symbol hop,total is 1 / 2*N symbol slot (For example, N symbol slot If =14, then it is less than or equal to 7), Ceiling[1 / 4*N symbol slot ](For example, N symbol slot If = 14, the starting position parameter value is 2N (if greater than 4). symbol hop,total It can be restricted to that.

[0273]

number

[0274] (ii) Options 1-2

[0275] When applying the proposed Option 1-1 method described above, a method can be proposed that performs time-domain resource mapping considering sub-slot boundaries rather than slot boundaries. For example, N symbol slot If = 14, a virtual sub-slot boundary can be defined between the 7th and 8th symbols in the slot, and the proposed Option 1-1 method can be applied so that resources do not straddle that boundary.

[0276] Option 1-2 may offer advantages in terms of efficient resource allocation because it may have a larger number of symbols in the slot during SRSp resource transmission compared to Option 1-1.

[0277] (iii) Options 1-3

[0278] When setting the initial hop start position according to Proposal 1, resource mapping can be configured to ensure that hops do not touch slot boundaries during frequency hopping of SRSp resources by restricting the initial hop start position setting based on the switching gap (e.g., in units of symbols) determined considering the number of symbols for each hop and RF readjustment between adjacent hops in the time domain.

[0279] Table 5 shows the starting position of the first hop in the time domain. The starting position of the first hop is indicated by the symbol index within the slot. For example, Table 5 corresponds to the first hop out of five hops.

[0280] [Table 5]

[0281] In Table 5, T gap This indicates the switching time, N gap symb This indicates the switching gap (unit: symbols), N hop symb This indicates the number of symbols per hop.

[0282] Table 5 shows an example of an in-slot symbol index value for the time domain start position of the first hop to set up so that hops do not straddle slot boundaries, depending on the number of symbols for each hop set for the frequency hopping operation of SRSp and the switching gap between adjacent hops in the time domain (e.g., in units of symbols). The symbol index value is the number of OFDM symbols in the slot (N) when the number of symbols for each hop and the switching gap between adjacent hops in the time domain are all the same. symb slot This is an example of calculating all possible starting positions for the first hop when the number of hops does not straddle a slot boundary, using 14 symbols. Table 5 is an example assuming a hop count of 5, and the above setting can be followed for all configurable hop counts to gain advantages in terms of multiplexing between terminals. The value of the inter-hop switching gap (e.g., in units of symbols) is determined by the UE capability reported from the terminal to the base station and the pneumatics (i.e., SCS) of the SRSp.

[0283] If the number of symbols between the start and end of two adjacent hops in the time domain is greater than the number of OFDM symbols in one slot, intra-slot hopping cannot be performed. However, even in this case, to conserve time resources, a method can be used to restrict the start position of the first hop, or to increase the flexibility of resource mapping, the start positions of each hop can be set to be the same, following the conventional slot-based SRS resource mapping method. When following the conventional slot-based resource mapping method, the time gap between hops must be set on a slot-by-slot basis, and the setting of the time gap can be done according to the following formula 4.

[0284]

number

[0285] In the above formula, N slot gap This indicates the time gap between hops in the slot-level resource mapping scheme, N symb hop The symbol length per hop is N symb gap The switching gap, N, is determined by considering RF readjustment between two adjacent hops in the time domain. symb slot This refers to the number of symbols in a slot. For example, if the sum of the symbol length per hop and the switching gap between two adjacent hops in the time domain is less than the number of symbols in one slot, the slot-level time gap between hops is set to 0 slots, and hopping can be performed from the same starting position for each slot.

[0286] The above explanation focuses on illustrating the proposed method using examples for all cases of symbol lengths for each hop, as shown in Table 5. However, it is not limited to these examples and can also be applied to the symbol lengths of SRS resources supported by the current Rel-17 standard, as shown in Table 6.

[0287] Table 6 shows the starting position of the first hop in the time domain. The starting position of the first hop is indicated by the symbol index within the slot. For example, Table 6 is for the first hop out of five hops.

[0288] [Table 6]

[0289] In Table 6, T gap This indicates the switching time, N gap symb This indicates the switching gap (unit: symbol), N hop symb This indicates the number of symbols per hop.

[0290] Options 1-3 are configurable for all cases where hops are performed in such a way that they do not cross slot boundaries during frequency hopping, which can be advantageous in terms of scheduling flexibility by the base station.

[0291] In options 1-1, 1-2, and 1-3, the hopping patterns and time / frequency resources scheduled by the base station can be used as is, regardless of slot boundaries, which offers advantages in terms of efficient resource allocation, and also has the advantage of maintaining the UE multiplexing gain through base station scheduling.

[0292] (Option 2) Symbol-level shifting scheme in the time domain

[0293] When setting the starting position, the number of symbols per hop, and the inter-hop switching delay (e.g., in units of symbols) according to Proposal 1, if a hop that straddles a slot boundary occurs, the resource mapping can be configured to symbol-level shift the time domain position of subsequent hops including that hop so that the starting position of that hop is located on the boundary, thereby preventing hops from touching slot boundaries during the frequency hopping operation of the SRSp resource.

[0294] Figure 16 shows an example of frequency hopping behavior of an SRSp resource across a slot boundary. In Figure 16, each SRSp resource consists of a total of five hops, each consisting of four symbols, and shows an example of frequency hopping behavior with a hop-to-hop time gap of one symbol (FC302) across a slot (FC303), where each block represents the symbols that make up the SRSp resource. FC301 represents a hop that straddles a slot boundary (FC304). The different shading patterns of each block represent the actual repetition of the terminal.

[0295] As a concrete example of Option 2, if the third hop (FC301) of an SRSp resource straddles a slot boundary, the resource mapping can be reconfigured by delaying the third, fourth, and fifth hops by three symbols each so that the starting position of that hop lies on the boundary.

[0296] (Option 3) Slot-based hopping pattern duplication method

[0297] (i) Option 3-1

[0298] If a hop occurs that spans a slot boundary, the time-domain resource mapping can be configured by repeating the hopping pattern of the previous slot for the next slot, thereby preventing the hop from touching the slot boundary during the frequency-hopping operation of the SRSp resource.

[0299] Figure 17 shows an example of frequency hopping behavior of an SRSp resource across a slot boundary. In Figure 17, each SRSp resource consists of a total of five hops, each consisting of four symbols, and shows an example of frequency hopping behavior with a hop-to-hop time gap (FC312) of one symbol across a slot (FC313), where each block represents the symbols that make up the SRSp resource. FC311 represents the hop that straddles the slot boundary (FC314). The different shading patterns of each block represent the actual repetition of the terminal.

[0300] As a concrete example of Option 3-1, if the third hop (FC311) of an SRSp resource straddles a slot boundary, the hopping pattern can be configured by resetting the time domain start position and the number of symbols per hop settings for previous hops to the FC311 hop and subsequent hops, including the FC311 hop. In this case, the frequency domain start PRB, bandwidth, and comb pattern settings for the FC311 hop and subsequent hops can be maintained as they are.

[0301] (ii) Option 3-2

[0302] Even if no hops crossing the aforementioned slot boundaries occur, the hopping pattern of the previous slot can be repeated in the next slot in a similar manner to configure time-domain resource mapping, thereby preventing hops from touching slot boundaries during the frequency hopping operation of the SRSp resource.

[0303] Figure 18 shows an example of frequency hopping behavior for an SRSp resource that does not straddle but crosses a slot boundary (FC324). In Figure 18, each SRSp resource consists of a total of five hops of three symbols, and the figure shows an example of frequency hopping behavior that crosses a slot (FC323) with a hop-to-hop time gap (FC322) of two symbols, where each block represents the symbols that make up the SRSp resource. The different shading patterns of each block represent the actual repetition of the terminal.

[0304] As a concrete example of Option 3-2, a hopping pattern can be constructed by resetting the time domain start position and the number of symbols per hop settings for the previous hop for hops that cross slot boundaries. In this case, the frequency domain start PRB, bandwidth, and comb pattern settings for that hop can be maintained as they are.

[0305] Option 3-2 offers advantages in terms of UE multiplexing because the time / frequency domain relationships between SRSp resources within the slot are maintained.

[0306] The terminal can obtain SRSp resource configuration information from the base station, which is time-domain resource-mapped so that no portion of the resources straddles slot boundaries, and based on this configuration information, can perform frequency-hopping transmission operations of the SRSp resources according to the method of Proposal 1. The SRSp resource configuration information may include information about i) the start position of each hop in the time domain (e.g., start slot offset, start symbol (within the slot)), ii) the length of each hop (e.g., the number of symbols contained in the hop), and iii) the number of hops. The SRSp resource configuration information may further include information about iv) the start PRB of the first hop in the time domain, and v) the bandwidth of the hops. In addition (optionally), vi) the SRSp resource configuration information may also include information about the number of overlapping RBs between hops.

[0307] The configuration operation of mapping SRSp resource hops to time domain resources so that a single hop exists across slot boundaries during SRSp frequency hopping may not be expected by the terminal. That is, the terminal may not expect any single hop to be configured across slot boundaries. In other words, the time resources of a single hop should all be completely contained within a single slot. Since the time resources of each hop within a slot are determined by i) the starting symbol of each hop (within the slot) (included in the starting position information of each hop), and ii) the length of each hop (number of symbols), a combination of i) the starting position of each hop and ii) the length of each hop must be configured so that each hop is not configured across slot boundaries. That is, the last symbol of the hop must be configured so that it does not exceed the duration (or the last symbol of the slot). Here, the last symbol of the hop is the sum of i) the starting symbol of the hop and ii) the length of the hop, so the relationship "i) the starting symbol of the hop + ii) the length of the hop ≤ the length of the slot" must be satisfied. In other words, the terminal does not expect any single hop to be set to "i) hop start symbol + ii) hop length > length of the slot".

[0308] When resource mapping and frequency hopping are performed as proposed above, the situation where at least one hop of an SRSp resource crosses a slot boundary does not occur, resulting in advantages in terms of both terminal realization complexity and positioning accuracy.

[0309] On the other hand, in the case of some signals, such as repeated PUSCH transmissions, if one of multiple PUSCH repeats crosses a slot boundary, the single PUSCH repeat is split into two actual Tx repeats based on the boundary between slots, and each of the two split actual Tx repeats may be transmitted in a different slot. However, the actual Tx repeat whose size after splitting is 1 symbol is dropped.

[0310] However, unlike PUSCH, SRSp resources consist of a single sequence. Therefore, if SRSp is split across slots like PUSCH, the characteristics of the single sequence of SRSp cannot be maintained, resulting in a decrease in positioning performance. To solve this problem, the above proposal explores a method to prevent situations in which one hop of SRSp spans multiple slots from occurring in the first place.

[0311] Proposal 2-1-1. Method for guaranteeing inter-hop switching time during repeated allocation based on (sub)slot boundaries.

[0312] When mapping SRSp resource hops to time-domain resources so that a single hop does not cross a slot boundary during frequency hopping operation of SRSp resources, we propose a method to ensure inter-hop switching time.

[0313] When mapping SRSp resource hops to time-domain resources so that a single hop does not cross a slot boundary during frequency hopping of SRSp resources, several methods can be proposed to guarantee inter-hop switching time: one that considers the time gap between the first hop within a slot and the adjacent slot boundary (hereinafter referred to as the "beginning gap"), one that considers the sum of time gaps within a slot, and one that drops hops or symbols adjacent to slot boundaries. Each of these will be explained separately as Option 1, Option 2, and Option 3.

[0314] (Option 1) Resource mapping method that considers the beginning gap within a slot in the time domain

[0315] When performing time-domain resource mapping while considering slot boundaries in this way, the predefined hopping pattern may be reset, potentially resulting in situations where inter-hop switching time is not guaranteed. To ensure this, inter-hop switching time can be guaranteed by considering the time gap between the first hop and the adjacent slot boundary within the slot (i.e., the beginning gap) and restricting the time domain start position of the first hop. In other words, the time domain start position of the first hop can be restricted so that the time gap between the starting slot boundary of the slot and the first hop (i.e., the beginning gap) does not become smaller than the inter-hop switching time value required according to the UE capability.

[0316] Figure 19 shows an example of frequency hopping behavior for an SRSp resource that does not straddle but crosses a slot boundary (FC724). In Figure 19, each SRSp resource consists of a total of five hops of three symbols, and the figure shows an example of frequency hopping behavior that crosses a slot (FC723) with a hop-to-hop switching time (FC722) of two symbols, where each block represents the symbols that make up the SRSp resource. The different shading patterns of each block represent the actual repetition of the terminal.

[0317] Figure 20 shows an example of frequency hopping behavior for an SRSp resource with time domain resource mapping reset according to Option 1. Each SRSp resource is configured with a total of five hops consisting of three symbols, and the example shows frequency hopping behavior where the start position of the first hop (FC725) is set to be less than the switching time, and the start position of the first hop is reset to the second symbol, with each block representing the symbols that make up the SRSp resource. The different shading patterns of each block represent the actual repetition of the terminal.

[0318] [Example A-1] - Adaptive transmission from terminal

[0319] As a specific example, in Figure 19, if the switching time (FC722) is set to 2 symbols, the time interval between the slot start boundary and the first hop is 1 symbol and is smaller than the switching time. Therefore, to ensure inter-hop switching time, the start position of the first hop can be restricted to the second symbol or later. When performing time domain resource mapping according to option 3-2 of proposal 2-1 above, as shown in Figure 20, the switching time between the last hop of a previous slot and the first hop of a subsequent slot can be ensured by having the terminal adaptively reset the start position of the first hop (FC925) to the second symbol, and then duplicating and transmitting the hopping pattern on a slot-by-slot basis.

[0320] [Example A-2] - Base station configuration

[0321] As another specific example, in Figure 19, if the switching time (FC722) is set to 2 symbols, the time interval between the slot start boundary and the first hop is 1 symbol and is smaller than the switching time. Therefore, to ensure inter-hop switching time, the base station can restrict the starting position of the first hop to be assigned after the second symbol. If the base station assigns the starting position of the first hop to the second symbol and provides the configuration information to the terminal, the terminal can, based on the configuration information, ensure the switching time between the last hop of the previous slot and the first hop of the subsequent slot by replicating the hopping pattern slot by slot, as shown in Figure 20, in accordance with option 3-2 of proposal 2-1 above.

[0322] In Option 1, the terminal can guarantee the required inter-hop switching time with low computational complexity when reconfiguring time-domain resources.

[0323] (Option 2) Resource mapping method that considers the sum of the beginning gap and ending gap within a slot in the time domain.

[0324] As proposed above, when mapping time-domain resources while considering slot boundaries, the predefined hopping pattern may be reset, potentially resulting in situations where inter-hop switching time is not guaranteed. To ensure this, inter-hop switching time can be guaranteed by restricting resource mapping by considering the sum of the beginning and ending gaps within a slot.

[0325] [Example A] Within a slot, the starting position of the first hop can be restricted so that the sum of the beginning gap and the time gap between the last hop in the slot and the adjacent slot boundary (hereinafter referred to as the "ending gap") is not smaller than the hop-to-hop switching time value required according to the UE capability.

[0326] Figure 21 shows an example of frequency hopping behavior for an SRSp resource that does not straddle but crosses a slot boundary (FE124). In Figure 21, each SRSp resource consists of a total of five hops of two symbols, and an example is shown where frequency hopping behavior is performed across a slot (FE123) with a hop-to-hop switching time (FE122) of three symbols. Each block represents a symbol that makes up the SRSp resource. The different shading patterns of each block represent the actual repetition of the terminal.

[0327] In Figure 21, when the switching time (FE122) is set to 3 symbols, the beginning gap (FE125) and ending gap (FE126) are each 1 symbol, and the sum of the two gaps is less than the switching time. Therefore, the starting position (FE125) of the first hop can be restricted to guarantee the inter-hop switching time.

[0328] [Example A-1] - Adaptive transmission from terminal

[0329] As a specific example, when performing time-domain resource mapping according to option 3 of proposal 2-1 above, after the terminal adaptively resets the starting position of the first hop to the third symbol, the switching time between the last hop of the previous slot and the first hop of the subsequent slot can be guaranteed by duplicating and transmitting the hopping pattern on a slot-by-slot basis for hops after the hop (FE121) that straddles the slot boundary according to option 3-1.

[0330] [Example A-2] - Base station configuration

[0331] As another example, when a base station maps the SRSp resource, to ensure a switching gap, it can restrict the first hop start position to be mapped after the third symbol, and the switching gap can be ensured by setting the time domain start position to the fourth symbol and providing it to the terminal.

[0332] [Example B] Within the slot, the hop-to-hop time gap and the sum of the SRS transmitted symbols are N symb slot The number of symbols in an SRSp resource can be limited to prevent it from becoming too long. That is, the number of symbols in an SRSp resource can be limited to satisfy equation 5.

[0333]

number

[0334] In equation 5, T gap begin T is the time gap between the first hop in the slot and the adjacent slot boundary (i.e., the beginning gap), T gap end T is the time gap between the last hop in the slot and the slot boundary adjacent to that hop (i.e., the ending gap). gap hopN is the time interval between SRSp resource hops within the slot. symb Slot N is the number of symbols in one slot. symb SRS N is the number of symbols allocated to SRSp resource transmission. hop N is the number of hops configured for the SRSp resource. hop Slot,i This is the number of hops assigned within the i-th slot, T switch This refers to the switching time between adjacent hops required depending on the UE capability.

[0335] Option 2 ensures the required inter-hop switching time while minimizing wasted time resources in the time-domain resource mapping for frequency hopping of SRSp resources.

[0336] As an example, a terminal can obtain configuration information for SRSp resources provided by a base station. Based on the resource mapping information in this information, it is expected to transmit SRSp resources. However, if the specified resource mapping spans a slot boundary, it is expected that the resource mapping will be reconfigured using the method described in Proposal 2-1 or another method. In this case, if the switching gap cannot be guaranteed, it is expected that the resource mapping will be reconfigured using the proposed method. Subsequently, the terminal can transmit SRSp resources at the location of the configured / specified frequency resource at the time of the reconfigured SRSp resource transmission.

[0337] As an example, a base station can refer to configuration information related to an SRSp resource in a positioning information request message requested by the LMF and provide the terminal with the configuration information for that SRSp resource. If the resource mapping in the provided information spans a slot boundary, the base station can expect the terminal to reconfigure the resource mapping using the method of proposal 2-1 or other methods. In this case, if the switching gap cannot be guaranteed, the base station can expect the terminal to reconfigure the resource mapping using the proposed method, or the base station can configure it under the limitations of the proposed method. Subsequently, the base station can receive the SRSp resource transmitted from the terminal at the location of the configured / instructed frequency resource at the time of transmission of the SRSp resource that is expected to have been reconfigured, combine / combine the received hops, perform a measurement for positioning, and then report the measurement to the LMF.

[0338] For example, the LMF can request SRSp resource configuration information from the base station and receive the SRSp resource configuration information actually configured by the base station. The LMF receives positioning-related measurements from the base station, which are measured using the SRSp resources transmitted from the terminal, and through these measurements, the LMF can estimate the terminal's position by calculation.

[0339] When the proposed method described above is used, the time-domain resource mapping method that prevents hops from crossing slot boundaries during frequency hopping can guarantee the required switching time between adjacent hops.

[0340] The above explanation focused on resolving issues that arise when reconfiguring time-domain resource mapping across slot boundaries. However, the proposed method is not limited to these issues and is generally applicable to other problems that occur during resource mapping of reference signals.

[0341] (Option 3) Drop a hop or symbol adjacent to the slot boundary.

[0342] When performing time-domain resource mapping while considering slot boundaries, the predefined hopping pattern may be reset, potentially resulting in situations where inter-hop switching times are not guaranteed. To ensure this, inter-hop switching times can be guaranteed by dropping hops or symbols adjacent to slot boundaries.

[0343] Figure 22 shows an example of frequency hopping behavior for an SRSp resource that does not straddle but crosses a slot boundary (FE101). In Figure 22, each SRSp resource consists of a total of five hops of three symbols, and an example is shown where frequency hopping behavior is performed across a slot with a hop-to-hop time gap of two symbols (FE105), where each block represents the symbols that make up the SRSp resource. The different shading patterns of each block represent the actual repetition of the terminal.

[0344] As a specific example, when performing time-domain resource mapping according to option 3-2 of proposal 2-1, the switching time can be guaranteed by dropping the hop before (FE103) or the hop after (FE104) of the slot boundary corresponding to FE101 in Figure 22 on a hop-by-hop basis. In this case, there is the advantage of minimizing the increase in terminal complexity and power consumption due to frequent RF retuning for dropping. As another example, when performing time-domain resource mapping according to option 3-2 of proposal 2-1, the switching time can be guaranteed by dropping the last symbol of the hop before (FE103) or the first symbol of the hop after (FE104) of the slot boundary corresponding to FE101 in order to guarantee the required switching time. In this case, there is the advantage of minimizing the degradation of positioning accuracy performance due to dropping.

[0345] For example, because it does not require additional time-domain resources to be allocated for the frequency-hopping operation of SRSp resources, it has the advantage of reducing time resource overhead and ensuring data transmission and reception.

[0346] Proposal 2-2. Iteration after splitting at slot boundaries (= resource mapping for each resource unit (all hops))

[0347] Proposal 2-2 proposes a method for handling situations where, during SRSp frequency hopping, at least one hop of a time-domain resource-mapped SRSp resource crosses a slot boundary without considering slot boundaries. For this situation, we can consider a method that does not perform any separate handling at the slot boundary, a method that splits the resource into actual iterations at the slot boundary, or a method that drops some of the split iterations. Each of these is described separately as Option 1, Option 2, and Option 3.

[0348] (Option 1) A method that does not perform separate processing (handling) for symbols that span slot boundaries.

[0349] Figure 16 shows an example of frequency hopping behavior for an SRSp resource across a slot boundary. In Figure 16, each SRSp resource consists of a total of five hops, each consisting of four symbols, and an example is shown where frequency hopping behavior is performed across a slot (FC303) with a hop-to-hop time gap of one symbol (FC302). Each block represents the symbols that make up the SRSp resource. FC301 represents the hop that straddles the slot boundary (FC304). The different shading patterns of each block represent the actual repetition of the terminal.

[0350] Even in the case of hops that cross slot boundaries, a method that does not require separate processing can be considered. As a specific example, in Figure S3 above, the terminal can transmit only r_3(0), r_3(1), and r_3(2) from the four sequences r_3(0), r_3(1), r_3(2), and r_3(3) generated by the four symbols to the third hop (FC301) that straddles the slot boundary (FC304), and then transmit the fourth symbol, which is the sequence r_3(3) that was generated in advance in the next slot.

[0351] In Option 1, when the sequence is the same for each SRSp burst (hop), no separate action is required from the terminal, which has advantages from the standpoint of terminal implementation.

[0352] (Option 2) A method that divides into actual repetitions at slot boundaries.

[0353] Figure 23 shows an example of frequency hopping behavior for an SRSp resource across a slot boundary. In Figure 23, each SRSp resource consists of a total of five hops, each consisting of four symbols, and an example is shown where frequency hopping behavior is performed across a slot (FC403) with a hop-to-hop time gap of one symbol (FC402). Each block represents the symbols that make up the SRSp resource. FC401 represents the hop that spans the slot boundary (FC404). The different shading patterns of each block represent the actual repetition of the terminal.

[0354] For hops that cross slot boundaries, a method can be considered in which the sequence is divided into two actual repeats based on the slot boundary. Symbols belonging to the slot before the slot boundary transmit the sequence generated for each symbol as is, while symbols belonging to the slot after the slot boundary can generate a new sequence from the symbols closest to the slot boundary and transmit it. As a specific example, in Figure S4 above, for the third hop (FC401) that straddles the slot boundary (FC404), the terminal can transmit only r_3(0), r_3(1), and r_3(2) of the four sequences r_3(0), r_3(1), r_3(2), and r_3(3) generated by the four symbols, and then transmit the sequence r_3(0)' newly generated in the next slot for the fourth symbol.

[0355] In the case of Option 2, when a different sequence is generated for each SRSp burst (hop), there is no need to save the sequence generated in the previous slot until the next slot, which has an advantage in terms of terminal implementation.

[0356] (Option 3) A method that divides at slot boundaries and then drops a portion of it.

[0357] Figure 24 shows an example of frequency hopping behavior for an SRSp resource across a slot boundary. In Figure 24, each SRSp resource consists of a total of five hops, each consisting of four symbols, and an example is shown where frequency hopping behavior is performed across a slot (FC503) with a hop-to-hop time gap of one symbol (FC502). Each block represents the symbols that make up the SRSp resource. FC401 represents the hop that spans the slot boundary (FC504). The different shading patterns of each block represent the actual repetition of the terminal.

[0358] For hops that cross slot boundaries, a method can be considered in which the hops are divided based on the slot boundary and then dropped according to the following rule options.

[0359] (i) Rule Option 1: Taking into consideration positioning accuracy performance, a rule can be set to drop symbols with fewer symbols in the slots before / after the slot boundary.

[0360] (ii) Rule Option 2: Taking into consideration the complexity of terminal manifestation, a rule can be set to drop symbols corresponding to subsequent slots of the boundary.

[0361] For example, a terminal can obtain SRSp resource configuration information provided by a base station. When transmitting multiple SRSp resource symbols according to the resource mapping for the frequency hopping operation of the SRSp resource, if the SRSp transmission symbol spans across slot boundaries, the transmission of that symbol may be dropped in accordance with the above rule option.

[0362] When the proposed method is used and frequency hopping of SRSp resources is performed across multiple slots, flexibility can be guaranteed in the time-domain resource mapping of SRSp resources.

[0363] [Proposal 3] Collision handling with DL slots in a TDD environment

[0364] Proposal 3 proposes a handling method for remaining symbols when, in a TDD environment, transmission is not completed within a UL slot where SRS frequency hopping is set / instructed, and a DL slot follows. The proposed method follows the resource mapping methods proposed in Proposals 2-1 and 2-2, and will be explained in separate Case 1 and Case 2 sections.

[0365] (Case 1) Resource mapping that does not allow SRSp resources to span slot boundaries

[0366] In a TDD environment, if transmission is not completed within a UL slot where SRS frequency hopping is set / instructed, and a DL slot follows, two methods can be considered for handling the remaining repetitions: continuing transmission of the remaining symbols in subsequent UL slots, or dropping the remaining symbols. These two methods will be explained separately as Option 1 and Option 2.

[0367] (Option 1) Drop the repetition

[0368] If a terminal is unable to complete the frequency hopping operation within consecutive UL slots in which SRSp resource frequency hopping is configured / instructed, transmission may not be expected for the remaining hops (repetitions).

[0369] (Option 2) Continue transmitting the remaining repetitions in the next UL slot.

[0370] If a terminal is unable to complete the frequency hopping operation within the UL slot in which SRSp resource frequency hopping is configured / instructed, the remaining hops (repetitions) can be expected to be retransmitted in UL slots subsequently assigned to that DL slot.

[0371] (Case 2) Resource mapping that allows SRSp resources to span slot boundaries

[0372] In a TDD environment, if transmission is not completed within a UL slot where SRS frequency hopping is set / instructed, and a DL slot follows, two methods can be considered for handling the remaining symbols and repetitions: continuing transmission of the remaining symbols and repetitions in subsequent UL slots, or dropping them. These will be explained separately as Option 1 and Option 2.

[0373] (Option 1) Drop the remaining symbols & repetitions

[0374] If a terminal is unable to complete the frequency hopping operation within consecutive UL slots in which SRSp resource frequency hopping is configured / instructed, transmission may not be expected for symbols after the slot boundary and for the remaining hops (repetitions) that span the slot boundary between the UL slot and the DL slot.

[0375] (Option 2) Continue transmitting the remaining symbols and repetitions in the next UL slot.

[0376] If a terminal is unable to complete the frequency hopping operation within consecutive UL slots in which SRSp resource frequency hopping is set / instructed, the symbols after the boundary and the remaining hops (repetitions) of the repetitions that span the slot boundary between the UL slot and the DL slot can be expected to be retransmitted in a UL slot assigned after the DL slot. When retransmitting in a subsequently assigned UL slot, the method for transmitting the symbols corresponding to the symbols after the boundary of the repetitions that span the slot boundary can be considered separately, according to the methods of Option 1 and Option 2 of Proposal 2-2, either by following the sequence generation of the previous slot or by generating a new sequence for that slot and transmitting it.

[0377] Next, for the frequency hopping operation of SRSp resources, we propose a method for assigning RRC configuration information related to frequency hopping as an ID and configuring / instructing it.

[0378] [Proposal 4] Direct instruction of frequency hopping setting switching by RRC

[0379] To configure the frequency hopping operation of SRSp resources, we propose a method that assigns an ID to the RRC configuration information related to frequency hopping, and then directly specifies the frequency hopping configuration ID to switch to when switching of the frequency hopping configuration is required.

[0380] • Provides settings related to frequency hopping.

[0381] A frequency hopping setting ID parameter can be added to the RRC settings of an SRSp resource to specify the ID of a setting set related to frequency hopping that has been pre-configured in the RRC. When transmitting the SRSp resource, the setting information corresponding to the setting set ID related to frequency hopping can be used to execute the frequency hopping operation. For example, an FHconfig-ID parameter can be added as an optional characteristic in the freqHopping-r16 field within the SRS-PosResource-16 IE, which contains the RRC setting information of the SRSp resource. When frequency hopping is requested for the SRSp resource, the setting information ID related to frequency hopping can be specified via the FHconfig-ID parameter. The terminal can then execute the frequency hopping operation of the SRSp resource by using the setting information corresponding to the defined ID from the frequency hopping-related setting information pre-configured by the newly defined FHconfig IE.

[0382] • Settings content related to frequency hopping

[0383] The setting information related to frequency hopping may include frequency hopping pattern information including the number of hops, hop bandwidth, time gap between hops, number of symbols per hop, and overlapping RB, as well as an ID for that setting information. To reduce parameter overhead, the number of symbols per hop and hop bandwidth can be set using conventional SRSp resource setting information without using separate RRC parameters. For example, fields for the number of hops, hop bandwidth, time gap between hops, number of symbols per hop, and overlapping RB can be added to the FHconfig IE, and their respective values ​​can be set. Hop bandwidth, number of symbols per hop, and overlapping RB can be set selectively. If the selectively set parameters are not set, the number of symbols per hop can be set according to the number of symbols in the SRSp resource, the hop bandwidth can be set to a value obtained by equally dividing the bandwidth of the SRSp resource by the number of hops, and overlapping RB can be left unset.

[0384] • SRSP resource frequency hopping transmission

[0385] When a terminal is configured / instructed by the base station to use the proposed frequency hopping configuration method, the terminal can perform frequency hopping by combining this configuration information with the SRSp resource configuration information obtained from the base station. In the frequency hopping operation of the SRSp resource, the starting position of the frequency domain follows the information in the SRSp resource configuration linked to the active BWP, and the BW of each hop can be configured / instructed in a separate frequency hopping configuration as described above, or it can follow the BW information in the SRSp resource configuration as is. In the frequency hopping operation of the SRSp resource for RedCap terminals, the hopping pattern in the frequency domain can be restricted to a sequential staircase pattern. During the frequency hopping operation of the SRSp resource, the starting position of the frequency domain follows the information in the SRSp resource configuration linked to the active BWP, and after each hop, the inter-hop time gap value configured / instructed in a separate frequency hopping configuration can be applied to perform time domain resource mapping for each hop.

[0386] As an example, a terminal can obtain configuration information for SRSp resources provided by a base station. If the terminal is a RedCap terminal, the frequency hopping pattern used for SRSp transmission can be configured via parameters related to the frequency hopping configuration ID within the received SRSp resource. Specifically, the configuration information and configuration ID related to the frequency hopping can be pre-configured in the IE related to the frequency hopping configuration via an RRC message. Subsequently, the terminal transmits the SRSp resource at the location of the configured / instructed frequency resource at the time of transmission of the configured / instructed SRSp resource.

[0387] As an example, a base station can provide a terminal with configuration information for an SRSp resource instructed by the LMF. If the target terminal is a RedCap terminal, the base station can configure and transmit the frequency hopping pattern used for SRSp transmission via parameters related to the frequency hopping configuration ID of the SRSp resource to be transmitted. Specifically, this can be done by linking the configuration information and configuration ID related to the frequency hopping in the IE related to the frequency hopping configuration via an RRC message. Subsequently, the base station receives the SRSp resource transmitted from the terminal at the location of the configured / instructed frequency resource at the time of transmission of the configured / instructed SRSp resource, combines the received hops, performs a measurement for positioning, and reports the measurement results to the LMF.

[0388] For example, the LMF can transmit configuration information for SRSp resources via a base station. The LMF receives positioning-related measurements from the base station, which are measured using the SRSp resources transmitted from the terminal, and based on these measurements, the LMF can calculate and estimate the location of the terminal.

[0389] As mentioned above, specifying the assignment ID for the configuration information related to frequency hopping has the advantage of saving resources.

[0390] While the above proposal describes methods for SRSp resources, the proposed methods are not limited to the terms used in the description, and methods for per SRSp resource set, per BWP, per UE, and / or per carrier can also be considered.

[0391] [Proposal 5] A method for performing frequency hopping setting switching in conjunction with the activated BWP.

[0392] Proposal 5 proposes a method for configuring frequency hopping operation of SRSp resources by linking RRC setting information related to frequency hopping to the BWP, and executing the switching of frequency hopping settings in response to the switching of the BWP.

[0393] • Provides settings related to frequency hopping.

[0394] After configuring the setting information related to frequency hopping as a set and assigning an ID to it, each ID can be linked to the configured BWP, and frequency hopping operations can be performed on SRSp resources assigned within the active BWP using the frequency hopping setting information corresponding to the active BWP. For example, an optional FHconfig-ID field can be added to the BWP IE containing the setting information of a pre-configured BWP. When the BWP is activated, frequency hopping operations can be performed using the pre-configured frequency hopping-related setting information corresponding to the frequency hopping setting ID indicated in the field when transmitting SRSp resources within the active BWP.

[0395] • Settings content related to frequency hopping

[0396] The configuration information related to frequency hopping can include frequency hopping pattern information including the number of hops, hop bandwidth, time gap between hops, number of symbols per hop, and overlapping RB, as well as an ID for the configuration information. To reduce parameter overhead, the number of symbols per hop and hop bandwidth can be set using conventional SRSp resource configuration information without using separate RRC parameters. For example, the fields for number of hops, hop bandwidth, time gap between hops, number of symbols per hop, and overlapping RB can be added to the FHconfig IE and their respective values ​​can be set. Hop bandwidth, number of symbols per hop, and overlapping RB can be set selectively. If the selectively set parameters are not set, the number of symbols per hop can be set according to the number of symbols in the SRSp resource, the hop bandwidth can be set as a value obtained by equally dividing the bandwidth of the SRSp resource by the number of hops, and overlapping RB can be left blank.

[0397] • SRSp resource frequency hopping transmission operation

[0398] When a terminal is configured / instructed by the base station to use the proposed frequency hopping configuration method, it can perform frequency hopping by combining this configuration information with the SRSp resource configuration information obtained from the base station. In the frequency hopping operation of the SRSp resource, the starting position of the frequency domain follows the information in the SRSp resource configuration linked to the active BWP, and the BW of each hop can be configured / instructed separately in the frequency hopping configuration as described above, or it can follow the BW information in the SRSp resource configuration as is. In the frequency hopping operation of the SRSp resource for RedCap terminals, the hopping pattern in the frequency domain can be restricted to a sequential staircase pattern. In the frequency hopping operation of the SRSp resource, the starting position of the frequency domain follows the information in the SRSp resource configuration linked to the active BWP, and after each hop, the time-domain resource mapping for each hop can be performed by applying the inter-hop time gap value configured / instructed in a separate frequency hopping configuration.

[0399] The setting information related to frequency hopping may include frequency hopping pattern information including the number of hops, hop bandwidth, time gap between hops, number of symbols per hop, and overlapping RB, as well as an ID for the setting information. To reduce parameter overhead, the number of symbols per hop and hop bandwidth can be set using conventional SRSp resource setting information without using separate RRC parameters. For example, the fields for number of hops, hop bandwidth, time gap between hops, number of symbols per hop, and overlapping RB can be added to the FHconfig IE and their respective values ​​can be set. Hop bandwidth, number of symbols per hop, and overlapping RB can be set selectively. If the selectively set parameters are not set, the number of symbols per hop can be set according to the number of symbols in the SRSp resource, the hop bandwidth can be set as a value obtained by equally dividing the bandwidth of the SRSp resource by the number of hops, and overlapping RB can be left blank.

[0400] As an example, a terminal can obtain configuration information for an SRSp resource provided by a base station. If the terminal is a RedCap terminal, it can be expected to transmit the SRSp resource while performing frequency hopping. In this case, the frequency hopping pattern used for SRSp transmission can be configured via parameters related to the frequency hopping configuration ID in the active BWP linked to the SRSp resource. The terminal transmits the SRSp resource at the location of the configured / instructed frequency resource at each configured / instructed transmission point for the SRSp resource.

[0401] As an example, a terminal can obtain configuration information for an SRSp resource provided by a base station. If the terminal is a RedCap terminal, it can be expected to transmit the SRSp resource while performing frequency hopping. In this case, the frequency hopping pattern used for SRSp transmission can be configured via parameters related to the frequency hopping configuration ID in the active BWP linked to the SRSp resource. The terminal transmits the SRSp resource at the location of the configured / instructed frequency resource at each configured / instructed transmission point for the SRSp resource.

[0402] As an example, a base station can provide a terminal with configuration information for an SRSp resource instructed by the LMF. If the target terminal is a RedCap terminal, the base station can transmit the frequency hopping operation configuration information for the SRSp resource received from the terminal to the BWP in the format of a pre-configured frequency hopping setting ID. When the BWP is activated, the base station can expect the terminal to transmit according to the frequency hopping setting linked to the BWP. The base station receives the SRSp resource transmitted from the terminal at the location of the configured / instructed frequency resource at the time of SRSp resource transmission, combines the received hops, performs a measurement for positioning, and then reports the measurement results to the LMF.

[0403] When settings related to frequency hopping are linked to the active BWP, resources can be saved because no separate instructions for frequency hopping are required. Furthermore, since frequency hopping is initiated within the active BWP, it is possible to save time in terms of RF retuning time for the frequency hopping operation.

[0404] For example, the LMF can transmit configuration information for SRSp resources via a base station. The LMF receives positioning-related measurements from the base station, which are measured using the SRSp resources transmitted from the terminal, and through these measurements, the LMF can calculate and estimate the location of the terminal.

[0405] Figure 25 is a diagram illustrating the operation of a network and terminals according to one embodiment.

[0406] In Figure 25, the network may include nodes that function as location servers such as LMFs and / or at least one of one or more BS / TRPs. For example, the transmission and reception / measurement of radio signals related to the radio interface between the network and the terminal in Figure 25 can be interpreted as BS / TRP operations, and the terminal's location determination can be interpreted as being performed by a location server such as a BS and / or LMF, depending on the positioning method.

[0407] Referring to Figure 25, a terminal can report its UE capability to the network via higher-layer signaling (A05). Through its UE capability, a terminal can report that it is a second-type terminal (RedCap UE) with reduced performance to support a smaller terminal maximum bandwidth than a first-type terminal (e.g., a normal UE).

[0408] The network may determine a frequency hopping configuration for the SRS for positioning (A10). The network may determine the frequency hopping configuration such that no single hop among the multiple hops is configured beyond a single slot, based on the fact that the terminal is a second-type terminal with reduced performance to support a smaller terminal maximum bandwidth than a first-type terminal. The frequency hopping configuration may include i) information regarding a start position of each hop and ii) information regarding a length of each hop in the time domain.

[0409] The network can transmit configuration information regarding an SRS for positioning, including the frequency hopping settings, to the terminal via higher layer signaling (A15). In other words, the terminal can receive configuration information regarding an SRS for positioning via higher layer signaling (UE may receive, through higher layer signaling) (A15).

[0410] Based on the fact that the terminal is a second-type terminal with reduced performance to support a smaller terminal maximum bandwidth than that of a first-type terminal, the terminal can be configured not to expect that any of the plurality of hops, which are configured based on the frequency hopping information, is configured beyond a single slot interval (duration).

[0411] The terminal can generate an SRS sequence based on the configuration information related to SRS (A20).

[0412] The terminal can transmit the SRS for positioning in each frequency band of each of a plurality of hops, based on the configuration information including a frequency hopping configuration for the SRS for positioning (A25, A26, A27, A28). The frequency hopping can be performed based on the terminal's RF (radio frequency) retuning.

[0413] The network can measure the SRS transmitted by the terminal and determine the terminal's location based on this (A30).

[0414] Figure 26 shows the flow of an SRS transmission method for a terminal according to one embodiment.

[0415] Referring to Figure 26, the terminal can receive configuration information regarding an SRS for positioning via higher-layer signaling (B05).

[0416] The terminal can transmit the SRS for positioning in each frequency band of each of a plurality of hops, based on the configuration information including a frequency hopping configuration for the SRS for positioning (B10).

[0417] The frequency hopping configuration may include i) information regarding the start position of each hop and ii) information regarding the length of each hop in the time domain.

[0418] The terminal can be configured not to expect that a single hop among the plurality of hops configured based on the frequency hopping setting is configured beyond a single slot.

[0419] The terminal can be configured such that none of the multiple hops are expected to be set beyond the single slot interval (duration) associated with each hop.

[0420] The entire sequence from the start symbol to the end symbol of the single hop can be contained within a single slot interval (duration).

[0421] i) The information regarding the starting position of each hop may include information regarding the starting symbol of each hop and information regarding the slot offset.

[0422] The final symbol position of each hop can be the starting symbol position of each hop plus the length of each hop as described in ii).

[0423] The frequency hopping setting may further include at least one of the following: iii) information regarding the number of hops, iv) information regarding the starting PRB (physical resource block) of the first hop in the time domain among the multiple hops, v) information regarding the hop bandwidth, or vi) information regarding the number of overlapping RBs between hops.

[0424] None of the aforementioned hops can be set across multiple slots.

[0425] The terminal can be a second-type terminal with reduced performance to support a smaller maximum terminal bandwidth than the first-type terminal.

[0426] The aforementioned frequency hopping can be performed based on RF (radio frequency) retuning.

[0427] Figure 27 shows the flow of an SRS reception method for a network (base station, TRP and / or LMF) according to one embodiment.

[0428] Referring to Figure 27, the network (base stations and / or LMFs) can determine the frequency hopping settings for the SRS for positioning (C05).

[0429] The base station can transmit configuration information, including the frequency hopping settings, to the terminal via higher-level signaling (C10).

[0430] The network (base station and / or TRP) can receive the SRS for positioning from the terminal in each frequency band of a plurality of hops based on the configuration information, including the frequency hopping settings (C10).

[0431] The frequency hopping setting may include i) information regarding the starting position of each hop in the time domain, and ii) information regarding the length of each hop.

[0432] The network (base station and / or LMF) may determine the frequency hopping configuration such that no single hop among the multiple hops is configured beyond a single slot, based on the fact that the terminal is a second-type terminal with reduced performance to support a smaller terminal maximum bandwidth than a first-type terminal.

[0433] The frequency hopping configuration may include i) information regarding the start position of each hop and ii) information regarding the length of each hop in the time domain. The frequency hopping configuration may further include at least one of the following: iii) information regarding the number of hops, iv) information regarding the start PRB (physical resource block) of the first hop in the time domain, v) information regarding the hop bandwidth, or vi) information regarding the number of overlapping RBs between hops. The i) information regarding the start position of each hop may include information regarding the start symbol and slot offset of each hop.

[0434] None of the aforementioned hops can be set beyond the single slot interval (duration) associated with each hop.

[0435] The entire sequence from the start symbol to the end symbol of the single hop can be contained within a single slot interval (duration).

[0436] The final symbol position of each hop can be the starting symbol position of each hop plus the length of each hop as described in ii).

[0437] None of the aforementioned hops can be set across multiple slots.

[0438] The aforementioned frequency hopping can be performed based on the RF (radio frequency) retuning of the terminal.

[0439] Figure 28 illustrates a communication system 1 applicable to the present invention.

[0440] Referring to Figure 28, the communication system 1 to which the present invention applies includes wireless equipment, a base station, and a network. Here, wireless equipment means equipment that communicates using wireless connectivity technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)), and is also referred to as communication / wireless / 5G equipment. However, wireless equipment includes, but is not limited to, robots 100a, vehicles 100b-1, 100b-2, XR (eXtended Reality) equipment 100c, handheld devices 100d, home appliances 100e, IoT (Internet of Things) equipment 100f, and AI equipment / servers 400. For example, vehicles include vehicles equipped with wireless communication functions, autonomous vehicles, and vehicles capable of inter-vehicle communication. Here, vehicles include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include AR (Augmented Reality), VR (Virtual Reality), and MR (Mixed Reality) devices, and are embodied in forms such as HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) installed in vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, and robots. Mobile devices include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), and computers (e.g., notebook computers). Home appliances include TVs, refrigerators, and washing machines. IoT devices include sensors and smart meters. For example, base stations and networks are also embodied in wireless devices, and certain wireless devices 200a can also operate as base stations / network nodes for other wireless devices.

[0441] Wireless devices 100a to 100f are connected to network 300 via base station 200. Artificial Intelligence (AI) technology is applied to wireless devices 100a to 100f, and wireless devices 100a to 100f are connected to AI server 400 via network 300. Network 300 is configured using a 3G network, 4G (e.g., LTE) network, or 5G (e.g., NR) network. Wireless devices 100a to 100f can communicate with each other via base station 200 / network 300, but can also communicate directly without going through the base station / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0442] Wireless communication / connections 150a, 150b, and 150c are performed between wireless devices 100a-100f / base station 200 and between base stations 200 / base station 200. Here, wireless communication / connections are performed by various wireless connection technologies such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication), and communication between base stations 150c (e.g., relay, IAB (Integrated Access Backhaul) (e.g., 5G NR)). Wireless communication / connections 150a, 150b, and 150c enable wireless devices and base stations / wireless devices, and base stations to transmit / receive radio signals from each other. For example, wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, based on various proposals of the present invention, one of the following is performed: a process of setting various configuration information for transmitting / receiving radio signals, a process of various signal processing (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), or a resource allocation process.

[0443] Figure 29 illustrates a wireless device to which the present invention can be applied.

[0444] Referring to Figure 29, the first radio device 100 and the second radio device 200 transmit and receive radio signals using various radio connectivity technologies (e.g., LTE, NR). Here, {first radio device 100, second radio device 200} correspond to {radio device 100x, base station 200} and / or {radio device 100x, radio device 100x} in Figure 29.

[0445] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 controls the memory 104 and / or the transceivers 106 and is configured to embody the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this specification. For example, the processor 102 processes information in the memory 104 to generate first information / signals, and then transmits a wireless signal containing the first information / signals with the transceiver 106. The processor 102 also receives a wireless signal containing second information / signals with the transceiver 106, and then stores the information obtained from signal processing of the second information / signals in the memory 104. The memory 104 is connected to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code containing instructions for performing some or all of the processes controlled by the processor 102, or for performing the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this specification. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). The transceiver 106 is connected to the processor 102 and transmits and / or receives radio signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or receiver. The transceiver 106 can also be mixed with an RF (radio frequency) unit. In one embodiment of the present invention, the wireless device may also mean a communication modem / circuit / chip.

[0446] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 controls the memory 204 and / or the transceivers 206 and is configured to embody the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this specification. For example, the processor 202 processes information in the memory 204 to generate third information / signals, and then transmits a wireless signal containing the third information / signals with the transceiver 206. The processor 202 also receives a wireless signal containing fourth information / signals with the transceiver 206, and then stores the information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 is connected to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code containing instructions for performing some or all of the processes controlled by the processor 202, or for performing the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this specification. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). The transceiver 206 is connected to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or receiver. The transceiver 206 can also be mixed with an RF unit. In one embodiment of the present invention, wireless equipment can also mean a communication modem / circuit / chip.

[0447] The hardware elements of the wireless devices 100 and 200 will be described in more detail below. However, one or more protocol layers are embodied by one or more processors 102 and 202. For example, one or more processors 102 and 202 embody one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed in this specification. One or more processors 102 and 202 generate messages, control information, data, or information by the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed in this specification. One or more processors 102, 202 generate signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data, or information by the functions, procedures, suggestions, and / or methods disclosed in this specification and provide them to one or more transceivers 106, 206. One or more processors 102, 202 receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information by the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed in this specification.

[0448] One or more processors 102, 202 are also referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 are embodied by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) are included in one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed in this specification are embodied using firmware or software, and the firmware or software is embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed in this specification is included in one or more processors 102, 202, or is stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this specification are embodied using firmware or software in the form of code, instructions and / or sets of instructions.

[0449] One or more memory units 104, 204 are connected to one or more processors 102, 202 and can store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memory units 104, 204 consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memory units 104, 204 are located inside and / or outside one or more processors 102, 202. In addition, one or more memory units 104, 204 are connected to one or more processors 102, 202 by various technologies such as wired or wireless connections.

[0450] One or more transceivers 106, 206 can transmit user data, control information, radio signals / channels, etc., as referred to in the methods and / or flowcharts described herein, to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed herein, from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 and transmit and receive radio signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information or radio signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information or radio signals from one or more other devices. Furthermore, one or more transceivers 106, 206 are connected to one or more antennas 108, 208, and one or more transceivers 106, 206 are configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this specification, by one or more antennas 108, 208. In this specification, one or more antennas are multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102, 202. One or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0451] Figure 30 shows another example of wireless equipment applicable to the present invention. Wireless equipment can be embodied in various forms depending on the use case / service (see Figure 28).

[0452] Referring to Figure 30, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 in Figure 29 and are composed of various elements, components, units, and / or modules. For example, the wireless devices 100 and 200 include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102, 202 and / or one or more memories 104, 204 in Figure 29. For example, the transceiver 114 includes one or more transceivers 106, 206 and / or one or more antennas 108, 208 in Figure 29. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls the various operations of the wireless devices. For example, the control unit 120 controls the electrical and mechanical operation of the wireless device based on the program / code / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via a wireless / wired interface using the communication unit 110, or stores information received from an external device (e.g., another communication device) via a wireless / wired interface using the communication unit 110 in the memory unit 130.

[0453] The additional element 140 is configured in various ways depending on the type of wireless device. For example, the additional element 140 includes at least one of the following: a power unit / battery, an input / output unit (I / O unit), a drive unit, and a computer unit. However, wireless devices can be embodied in forms such as robots (Figure 29, 100a), vehicles (Figure 29, 100b-1, 100b-2), XR devices (Figure 29, 100c), portable devices (Figure 29, 100d), home appliances (Figure 29, 100e), IoT devices (Figure 29, 100f), digital broadcasting terminals, hologram devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, AI servers / devices (Figure 29, 400), base stations (Figure 29, 200), and network nodes. Depending on the use case / service, the wireless device may be mobile or used in a fixed location.

[0454] In Figure 30, the various elements, components, units / parts, and / or modules within the wireless devices 100 and 200 are either entirely connected to each other by a wired interface, or at least some are wirelessly connected by the communication unit 110. For example, within the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are wiredly connected, and the control unit 120 and the first units (e.g., 130 and 140) are wirelessly connected by the communication unit 110. Furthermore, each element, component, unit / part, and / or module within the wireless devices 100 and 200 further comprises one or more elements. For example, the control unit 120 is composed of one or more processor sets. For example, the control unit 120 is composed of a set of communication control processors, application processors, ECUs (Electronic Control Units), graphics processing processors, memory control processors, and so on. As another example, the memory section 130 may consist of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0455] Figure 31 illustrates a vehicle or autonomous vehicle to which the present invention can be applied. The vehicle or autonomous vehicle can be embodied in a mobile robot, a vehicle, a train, aerial vehicle (AV), ship, etc.

[0456] Referring to Figure 31, the vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 is composed of part of the communication unit 110. Each of blocks 110 / 130 / 140a to 140d corresponds to blocks 110 / 130 / 140 in Figure 30.

[0457] The communication unit 110 transmits and receives signals (e.g., data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 controls elements of the vehicle or autonomous vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The drive unit 140a enables the vehicle or autonomous vehicle 100 to travel on the ground. The drive unit 140a includes an engine, motor, powertrain, wheels, brakes, steering system, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes a wired / wireless charging circuit, battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (inertial measurement unit) sensor, collision sensor, wheel sensor, speed sensor, tilt sensor, weight sensing sensor, heading sensor, position module, vehicle forward / reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illuminance sensor, pedal position sensor, etc. The autonomous driving unit 140d embodies technologies such as lane keeping during driving, automatic speed adjustment like adaptive cruise control, automatic driving according to a predetermined route, and automatic route setting and driving when a destination is set.

[0458] For example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and drive plan based on the obtained data. The control unit 120 controls the drive unit 140a so that the vehicle or autonomous vehicle 100 moves according to the autonomous driving route (e.g., speed / direction adjustment) according to the drive plan. The communication unit 110 acquires the latest traffic information data from the external server non-periodically during autonomous driving, and also acquires surrounding traffic information data from surrounding vehicles. The sensor unit 140c also obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and drive plan based on the newly acquired data / information. The communication unit 110 transmits information such as vehicle position, autonomous driving route, and drive plan to the external server. Based on the information collected from the vehicle or autonomous vehicle, the external server can predict traffic information data in advance using AI technology, etc., and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0459] The embodiments described above are combinations of the components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly mentioned. Each component or feature can be implemented in a form that is not combined with other components or features. It is also possible to combine some components and / or features to constitute embodiments of the present invention. The order of the operations described in the embodiments of the present invention is changeable. Some components or features of any embodiment can be included in other embodiments, or replaced by corresponding components or features of other embodiments. Claims that are not explicitly referenced in the claims can be combined to constitute embodiments, or can be included as new claims by amendments after filing.

[0460] It will be obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the features of the invention. Therefore, the above detailed description should not be interpreted restrictively in any way, but should be considered illustrative. The scope of the invention shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the invention are included within the scope of the invention.

[0461] [Industrial applicability] This disclosure can be used in various devices including networks such as terminals, base stations, and / or location servers of wireless mobile communication systems.

[0462] [Claims when filing an international application] [Claim 1] A method for a terminal (user equipment: UE) to transmit an SRS (sounding reference signal) in a wireless communication system, The step of receiving configuration information regarding SRS for positioning via higher-level signaling; and The step of transmitting the SRS for positioning in each frequency band of a plurality of hops, based on the setting information including frequency hopping settings for the SRS for positioning; The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, A method wherein the terminal does not expect that one of the multiple hops set based on the frequency hopping setting will be set beyond a single slot. [Claim 2] The method according to claim 1, wherein the terminal does not expect any of the plurality of hops to be set beyond the single slot interval (duration) associated with each hop. [Claim 3] The method according to claim 1, wherein the single hop from the start symbol to the end symbol is contained within a single slot interval (duration). [Claim 4] i) The information regarding the start position of each hop in the time domain includes information regarding the start symbol of each hop and information regarding the slot offset, The method according to claim 3, wherein the position of the last symbol of each hop is obtained by adding the length of each hop to the position of the starting symbol of each hop. [Claim 5] The aforementioned frequency hopping setting is, iii) Information regarding the number of the multiple hops, iv) Of the multiple hops mentioned above, information regarding the start PRB (physical resource block) of the first hop in the time domain, v) Information regarding hop bandwidth, or vi) The method according to claim 1, further comprising at least one of the pieces of information relating to the number of overlapping RBs between hops. [Claim 6] The method according to claim 1, wherein none of the aforementioned hops are set across multiple slots. [Claim 7] The method according to claim 1, wherein the terminal is a second type terminal whose performance is reduced to support a smaller terminal maximum bandwidth than that of a first type terminal. [Claim 8] The method according to claim 1, wherein the frequency hopping is performed based on RF (radio frequency) retuning. [Claim 9] A processor-readable recording medium on which a program for performing the method described in claim 1 is recorded. [Claim 10] A device for wireless communication, Memory for storing command words; and A processor that operates by executing the aforementioned instruction; The operation of the aforementioned processor is as follows: The step of receiving configuration information regarding the SRS (sounding reference signal) for positioning via higher-level signaling; and The step of transmitting the SRS for positioning in each frequency band of a plurality of hops, based on the setting information including frequency hopping settings for the SRS for positioning; The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, The device does not expect that one of the multiple hops set based on the frequency hopping setting will be set beyond a single slot. [Claim 11] It is further equipped with a transmitter and receiver, The device according to claim 10, wherein the device is a terminal that operates in a wireless communication system. [Claim 12] The apparatus according to claim 10, wherein the apparatus is a processing device configured to control a terminal operating in a wireless communication system. [Claim 13] A method for a wireless communication system in which at least one base station (BS) receives an SRS (sounding reference signal), The stage of determining the frequency hopping settings for SRS (Sensor-Based Positioning); The step of transmitting configuration information, including the frequency hopping settings, to the terminal (user equipment: UE) via higher-level signaling; and The step of receiving the SRS for positioning in each frequency band of a plurality of hops from the terminal based on the setting information including the frequency hopping setting; The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, A method for determining the frequency hopping settings such that no single hop among the plurality of hops is set beyond a single slot, based on the fact that the base station is a second type terminal whose performance is reduced to support a smaller terminal maximum bandwidth than a first type terminal. [Claim 14] A processor-readable recording medium on which a program for performing the method described in claim 13 is recorded. [Claim 15] A base station (BS) for wireless communication, At least one memory for storing command words; and The system comprises at least one processor that operates by executing the aforementioned instruction; The operation of the aforementioned at least one processor is as follows: The stage of determining the frequency hopping settings for the SRS (sounding reference signal) used for positioning; The step of transmitting configuration information, including the frequency hopping settings, to the terminal (user equipment: UE) via higher-level signaling; and A step of receiving the SRS for positioning in each frequency band of a plurality of hops from the terminal based on the setting information including the frequency hopping setting; It includes, The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, A base station in which at least one processor determines the frequency hopping configuration such that no single hop among the plurality of hops is configured beyond a single slot, based on the fact that the terminal is a second type terminal with reduced performance to support a smaller terminal maximum bandwidth than a first type terminal.

Claims

1. A method for a terminal (user equipment: UE) to transmit an SRS (sounding reference signal) in a wireless communication system, The step of receiving configuration information regarding the SRS for positioning via higher-level signaling; and The step of transmitting the SRS for positioning in each frequency band of a plurality of hops, based on the setting information including frequency hopping settings for the SRS for positioning; The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, A method wherein the terminal does not expect that one of the multiple hops set based on the frequency hopping setting will be set beyond a single slot.

2. The method according to claim 1, wherein the terminal does not expect any of the plurality of hops to be set beyond the single slot interval (duration) associated with each hop.

3. The method according to claim 1, wherein the single hop from the start symbol to the end symbol is contained within a single slot interval (duration).

4. i) The information relating to the start position of each hop in the time domain includes information relating to the start symbol of each hop and information relating to the slot offset, The method according to claim 3, wherein the position of the last symbol of each hop is obtained by adding the length of each hop to the position of the starting symbol of each hop.

5. The aforementioned frequency hopping setting is, iii) Information regarding the number of the plurality of hops, iv) Information regarding the start PRB (physical resource block) of the first hop in the time domain among the multiple hops, v) Information regarding hop bandwidth, or vi) The method according to claim 1, further comprising at least one of the pieces of information relating to the number of overlapping RBs between hops.

6. The method according to claim 1, wherein none of the aforementioned multiple hops are set across multiple slots.

7. The method according to claim 1, wherein the terminal is a second type terminal whose performance is reduced to support a smaller maximum terminal bandwidth than that of a first type terminal.

8. The method according to claim 1, wherein the frequency hopping is performed based on RF (radio frequency) retuning.

9. A processor-readable recording medium on which a program for performing the method described in claim 1 is recorded.

10. A device for wireless communication, Memory for storing command words; and A processor that operates by executing the aforementioned instruction; The operation of the aforementioned processor is as follows: The step of receiving configuration information regarding the SRS (sounding reference signal) for positioning via higher-level signaling; and The step of transmitting the SRS for positioning in each frequency band of a plurality of hops, based on the setting information including frequency hopping settings for the SRS for positioning; The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, The device does not expect that one of the multiple hops set based on the frequency hopping setting will be set beyond a single slot.

11. It is further equipped with a transmitter and receiver, The device according to claim 10, wherein the device is a terminal that operates in a wireless communication system.

12. The apparatus according to claim 10, wherein the apparatus is a processing device configured to control a terminal operating in a wireless communication system.

13. A method for receiving a sounding reference signal (SRS) in a wireless communication system, wherein at least one base station (BS) receives an SRS. The stage of determining the frequency hopping settings for the SRS for positioning; The step of transmitting configuration information, including the frequency hopping setting, to a terminal (user equipment: UE) via higher-level signaling; and The step of receiving the SRS for positioning in each frequency band of a plurality of hops from the terminal based on the setting information including the frequency hopping setting; The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, A method for determining the frequency hopping settings such that no single hop among the plurality of hops is set beyond a single slot, based on the fact that the base station is a second type terminal whose performance is reduced to support a smaller terminal maximum bandwidth than a first type terminal.

14. A processor-readable recording medium on which a program for performing the method described in claim 13 is recorded.

15. A base station (BS) for wireless communication, At least one memory for storing command words; and The system comprises at least one processor that operates by executing the aforementioned instruction; The operation of the aforementioned at least one processor is as follows: The stage of determining the frequency hopping settings for the SRS (sounding reference signal) for positioning; The step of transmitting configuration information, including the frequency hopping setting, to a terminal (user equipment: UE) via higher-level signaling; and A step of receiving the SRS for positioning in each frequency band of a plurality of hops from the terminal, based on the setting information including the frequency hopping setting; It includes, The aforementioned frequency hopping setting is, i) Information regarding the starting position of each hop in the time domain, and ii) Includes information on the length of each hop, A base station in which at least one processor determines the frequency hopping configuration such that no single hop among the plurality of hops is configured beyond a single slot, based on the fact that the terminal is a second type terminal with reduced performance to support a smaller terminal maximum bandwidth than a first type terminal.