System and methods for cross slot sounding reference signal repetition

Abstract

An apparatus and system for implementing cross-slot sounding reference signal (SRS) repetition. A base station (gNB) generates and transmits configuration parameters to user equipment (UE) specifying an SRS repetition pattern that spans multiple time slots. The UE transmits SRS resources or SRS resource sets according to the configured pattern, with different repetitions occurring in different slots. The system supports various repetition schemes including per-resource-set application, per-resource application, and continuous time-domain allocation across slot boundaries. Configuration parameters may include slot indications, slot offsets, and frequency hopping patterns. The UE maintains phase continuity and power consistency during repetition transmission within defined time windows, restarting these windows when specific events occur including frequency hopping, intervening uplink transmissions, or changes in spatial relations or power control parameters.

Description

AG5254-PCT 1884.R64WO1SYSTEM AND METHODS FOR CROSS SLOT SOUNDING REFERENCE SIGNAL REPETITIONPRIORITY

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63 / 761,542, filed February 21, 2025, which is incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] The present disclosure pertains to wireless communications. In particular, this disclosure is related to multi-slot sounding reference signal (SRS) repetition.BACKGROUND

[0003] Mobile communication has evolved significantly from early voice systems to highly sophisticated integrated communication platform. Nextgeneration (NG) wireless communication systems, including 5thgeneration (5G) and sixth generation (6G) or new radio (NR) systems, are to provide access to information and sharing of data by various user equipment (UEs) and applications. NR is to be a unified network / system that is to meet vastly different and sometimes conflicting performance dimensions and services driven by different services and applications. As such, the complexity of such communication systems, as well as interactions between elements within a communication system, has increased. In particular, wireless communication systems increasingly rely on advanced antenna configurations and reference signals to support high-speed data services and adaptive network management. As these systems evolve, improving cellular coverage continues to be a focus of interest for a number of reasons.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:AG5254-PCT 1884.R64WO1

[0005] FIG. 1 A illustrates an architecture of a network, according to some examples.

[0006] FIG. IB illustrates a non-roaming 5G system architecture, according to some examples.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture, according to some examples.

[0008] FIG. 2 illustrates a block diagram of a communication device, according to some examples.

[0009] FIG. 3 illustrates SRS repetition in more than one slot, according to some examples.

[0010] FIG. 4 illustrates SRS repetition in multiple slots, according to some examples.

[0011] FIG. 5 illustrates SRS repetition in a plurality of slots, according to some examples.

[0012] FIG. 6 illustrates a method of compressed SRS transmission, according to some examples.DESCRIPTION

[0013] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for, those of other embodiments. Embodiments outlined in the claims encompass all available equivalents of those claims.

[0014] The following detailed description provides illustrative examples of the disclosed subject matter and is intended to enable those skilled in the art to make and use the described technology. The disclosed subject matter pertains to the field of wireless communications, with a particular focus on techniques for beamspace compression of SRS in RUs to optimize uplink fronthaul throughput in next-generation networks, such as 5G and 6G systems. The described methods and systems address challenges associated with managing highdimensional SRS data while maintaining efficient and flexible communication between distributed units (DUs) and RUs.AG5254-PCT 1884.R64WO1

[0015] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140 A includes 3 GPP LTE / 4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions. A network function may be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and / or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0016] The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and / or wireless communications interface. The UEs 101 and 102 may be collectively referred to herein as UE 101, and UE 101 may be used to perform one or more of the techniques disclosed herein.

[0017] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and / or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0018] In some aspects, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UEAG5254-PCT 1884.R64WO1and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0019] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.

[0020] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and may be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0021] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).AG5254-PCT 1884.R64WO1

[0022] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0023] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmission / reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.

[0024] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and / or 112 may be a gNB, an eNB, or another type of RAN node.

[0025] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gatewayAG5254-PCT 1884.R64WO1(S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0026] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0027] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0028] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-InternetAG5254-PCT 1884.R64WO1Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0029] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0030] In some aspects, the communication network 140 A may be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[0031] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network / 5GC) can include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and the UPF may be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs may be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs may be coupled to each other via Xn interfaces.AG5254-PCT 1884.R64WO1

[0032] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG-eNBs may be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB may be a master node (MN) and NG-eNB may be a secondary node (SN) in a 5G architecture.

[0033] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 may be in communication with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM) / home subscriber server (HSS) 146.

[0034] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 may be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 may be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0035] The UPF 134 may be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 may be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4GAG5254-PCT 1884.R64WO1communication system). The UDM may be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0036] The AF 150 may provide information on the packet flow to the PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0037] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B may be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B may be configured to handle the session states in the network, and the E-CSCF may be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B may be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B may be connected to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

[0038] In some aspects, the UDM / HSS 146 may be coupled to an application server 184, which can include a telephony application server (TAS) or another application server (AS) 160B. The AS 160B may be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0039] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152),AG5254-PCT 1884.R64WO1N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Nil (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0040] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G system architectures may be service-based and interaction between network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0041] In some aspects, as illustrated in FIG. 1C, service-based representations may be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0042] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic andAG5254-PCT 1884.R64WO1aperiodic communications with random packet arrival time and size. Techniques disclosed herein may be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0043] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0044] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0045] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in whichAG5254-PCT 1884.R64WO1modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0046] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0047] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The non-transitory machine readable medium 222 is a tangible medium. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and / or within the hardware processor 202 during execution thereof by theAG5254-PCT 1884.R64WO1communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store the one or more instructions 224.

[0048] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.

[0049] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG) / 5thgeneration (5G) standards among others. In an example, the network interface device 220 mayAG5254-PCT 1884.R64WO1include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.

[0050] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0051] The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0052] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and / or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and / or a Third Generation Partnership Project (3 GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), FreedomAG5254-PCT 1884.R64WO1of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel.15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.19, etc ), 3GPP 5G, 5G, 5GNew Radio (5GNR), 3GPP 5GNew Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication SystemZExtended Total Access Communication System (TACSZETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation forAG5254-PCT 1884.R64WO1Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel / PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as 3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802.1 lad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP / LTE based or IEEE 802.1 Ip or IEEE 802.1 Ibd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802.1 Ip based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety related applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non-safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

[0053] Aspects described herein may be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications)AG5254-PCT 1884.R64WO1spectrum as well as other types of spectrum / bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib / g / n / ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 - 4200 MHz, 3.55-3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band, but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 -94 GHz, etc.), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57-64 / 66 GHz (note: this band has near-global designation for Multi-Gigabit Wireless Systems (MGWS) / WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radarAG5254-PCT 1884.R64WO1applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme may be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0054] As above, numerous aspects of cellular systems are considered during design and deployment. Coverage is one factor that is contemplated for successful operation of a system. Compared to LTE, NR and 6G can be deployed at relatively higher carrier frequency in frequency range 1 (FR1), e.g., at 3.5GHz. In this case, coverage loss is expected due to larger path-loss, which makes it more challenging to maintain an adequate quality of service (QoS). Typically, uplink coverage is the bottleneck for system operation considering the low transmit power at UE side.

[0055] In 5G, SRS were developed to help the gNB acquire the channel state information for uplink (UL) or downlink (DL) communications for time domain duplex (TDD) systems with channel reciprocity. Based on the estimated channel, the gNB may make appropriate decisions for link adaptation and scheduling. As defined in 5G, one or more SRS resource sets may be configured by the gNB via radio resource control (RRC) signaling. Each SRS resource set includes one or more SRS resources. The SRS resource set may be targeted for various purposes, which include precoding matrix determination and beam management for both DL and UL transmissions. In addition, SRS may be configured or transmitted in a periodic, semi-persistent, or aperiodic manner.

[0056] To improve the SRS coverage, repetition can be applied to SRS transmissions. However, in the existing 5G specification, SRS repetition is confined within a slot, which may not be sufficient for cell edge UEs (i.e., UEs at the edge of a cell) with poor coverage in the network. To address this issue, it is more desirable to extend the repetition for SRS transmission for more than one slot.

[0057] In one embodiment, for SRS repetition in more than one slot, the same time domain resource allocation and / or frequency resource allocation may be applied to the SRS resource in the more than one slot.AG5254-PCT 1884.R64WO1

[0058] In one option, SRS repetition in more than one slot is applied on a per-SRS resource set basis. In this case, when more than one SRS resource is configured for a SRS resource set, the SRS repetition in more one slot is applied to a first SRS resource and a second SRS resource in a first slot, and then a first SRS resource and a second SRS resource in a second slot, respectively.

[0059] FIG. 3 illustrates SRS repetition in more than one slot, according to some examples. In the example shown in FIG. 3, one SRS resource set has two SRS resources (SRS resource 1 302, SRS resource 2304), where each SRS resource spans two symbols 306 in a slot 308. Two SRS repetitions for SRS resource 1 302 and for SRS resource 2304 are used in two slots 308 (a repetition as used herein is defined as an SRS instance). In this option, the same time domain resource allocation is applied to SRS repetitions in the slots 308. As shown in FIG. 3, the slots 308 are adjacent and each SRS resource occurs at the same relative location (i.e., same symbols) in each slot 308.

[0060] In another option, SRS repetition in more than one slot is applied on a per SRS resource basis. In this case, when more than one SRS resource is configured for a SRS resource set, the SRS repetition in multiple slots is applied to a first SRS resource in the first slot of multiple slots, and a second SRS resource in the second slot of the multiple slots, respectively.

[0061] FIG. 4 illustrates SRS repetition in multiple slots, according to some examples. In the example, one SRS resource set has two SRS resources (SRS resource 1 402, SRS resource 2404), where each SRS resource spans two symbols 406 in a slot (first slot 408a, second slot 408b). As shown in FIG. 4, two SRS repetitions for SRS resource 1 402 are provided in the first slot 408a and two SRS repetitions for SRS resource 2404 are provided in the second slot 408b. As shown in FIG. 4, the slots are adjacent and the same relative location (i.e., same symbols) in each slot 308. Thus, as shown in FIG. 4, although SRS resources generally occupy the same symbols in each slot, the specific SRS resource being repeated is limited to a single slot (i.e., each slot has multiple instances of the same SRS resource and different slots are associated with different SRS resources).

[0062] In another embodiment, continuous time domain resource allocation may be used for SRS transmission in a plurality of slots. In this case,AG5254-PCT 1884.R64WO1the same frequency domain resource allocation is applied to different SRS repetitions.

[0063] FIG. 5 illustrates SRS repetition in a plurality of slots, according to some examples. In the example shown in FIG. 5, each SRS resource set has one SRS resource (SRS resource 1), where each SRS resource spans two symbols 506 in a slot 508. Further, unlike the examples shown in FIGS. 3 and 4, in which two SRS repetitions are used for each SRS resource, in FIG. 5, four SRS repetitions 502a, 502b, 502c, 502d are used for SRS transmission. In this example, first SRS repetition 502a, second SRS repetition 502b, third SRS repetition 502c, and fourth SRS repetition 502d are transmitted continuously in the time domain (i.e., in adjacent symbols 506).

[0064] In one example, a different frequency hopping pattern is used for repetition of SRS within a slot compared to a frequency hopping pattern used for repetition across slots. As used herein, a frequency hopping pattern includes a starting frequency offset. In another example, repetition of an SRS instance within a slot is aligned in time (no frequency offset) compared to a frequency hopping pattern used for repetition across slots.

[0065] In one example, for SRS repetition in more than one slot, if one SRS repetition in an SRS resource or an SRS resource set collides with a slot boundary, the UE may cancel the SRS repetition. In another example, under the same conditions, the UE may defer the SRS repetition in the next slot or next available slot.

[0066] In another example, for SRS repetition in more than one slot, the UE may not expect that one SRS repetition in an SRS resource or an SRS resource set collides with a slot boundary.

[0067] In another embodiment, for SRS repetition in more than one slot, Physical Resource Block (PRB) offset, comb offset and / or cyclic shift hopping may be applied to the SRS transmission in different slots. In particular, different PRB offset, comb offsets or cyclic shift values may be used for the SRS repetition in different slots.

[0068] In one embodiment, a first slot and a second slot of a first SRS repetition and a second SRS repetition, respectively, may be configured by higher layers via RRC signaling, dynamically indicated in a downlink control information (DCI), or a combination thereof. In particular, the first slot mayAG5254-PCT 1884.R64WO1reuse the existing 3GPP specification for the transmission of SRS instances. The RRC signaling or DCI thus specifies which slots are used for transmission. As the slots are numbered / indexed in 5G, the slot number or timing information provides an indication of a slot to be used for transmission.

[0069] In another example, a first starting symbol and a second starting symbol of a first SRS repetition and a second SRS repetition, respectively, may be configured by higher layers via RRC signaling, dynamically indicated in a DCI, or a combination thereof. In particular, the first starting symbol may reuse the existing 3GPP specification for the transmission of SRS instances. Further, the first starting symbol and the second starting symbol may be defined relative to the first or last symbol of a slot.

[0070] In some aspects, the above variations may apply to an SRS resource or an SRS resource set. In some aspects, the above variations may apply to periodic, semi-persistent, and / or aperiodic SRS transmission.

[0071] In another embodiment, a first slot of a first SRS repetition and a slot offset between the first SRS repetition and a second SRS repetition may be configured by higher layers via RRC signaling, dynamically indicated in a DCI, or a combination thereof. In particular, the first slot may reuse the existing 3 GPP specification for the transmission of SRS instances.

[0072] In another option, a first starting symbol of a first SRS repetition and a symbol offset between the first SRS repetition and a second SRS repetition may be configured by higher layers via RRC signaling, dynamically indicated in a DCI, or a combination thereof. In particular, the first starting symbol may reuse the existing 3GPP specification for the transmission of SRS instances, and may be defined relative to the first or last symbol of a slot.

[0073] In some aspects, these variations may apply to an SRS resource or an SRS resource set and / or may apply to periodic, semi-persistent, and / or aperiodic SRS transmission.

[0074] In another embodiment, SRS repetition in more than one slot is transmitted in available slots for uplink transmission. In particular, the UE determines a slot as an available slot when an SRS repetition does not overlap with semi-statically configured DL symbols and flexible symbols used for synchronization signal block (SSB) transmission. More generally, while a slot isAG5254-PCT 1884.R64WO1a time unit, not all slots can be used for uplink transmission; an available slot is one that is actually usable for uplink SRS transmission.

[0075] In another embodiments, a number of slots for SRS repetitions may be configured by higher layers via RRC signaling. In particular, the number of slots may be configured per SRS resource or SRS resource set. A per SRS resource set basis means treating the entire SRS resource set as a unit (all resources in the SRS resource set are transmitted in slot 1, then repeat so that all SRS resource resources in the SRS resource set are transmitted in slot 2).

[0076] In another option, a set of the number of slots for SRS repetitions may be configured by higher layers via RRC signaling, while one field in the DCI may be used to indicate one value from the set of number of slots for SRS repetitions.

[0077] UE behavior for SRS repetition

[0078] Embodiments of UE behavior for SRS repetition are provided as follows:

[0079] In one embodiment, for continuous SRS repetition in the time domain, a time domain window may be defined for the UE to maintain phase continuity and power consistency during the transmission of SRS repetition. In some aspects, the maximum duration of a nominal time domain window may be configured by higher layers via RRC signaling. In some aspects, the time window for the UE to maintain phase continuity and power consistency during the transmission of SRS repetition could be limited to within a slot. In some aspects, the time window for the UE to maintain phase continuity and power consistency during the transmission of SRS repetition could span across a slot boundary.

[0080] In particular, when the UE starts to transmit the SRS repetition, the UE starts an actual time domain window. In addition, in the case in which an event occurs, the UE may restart the actual time domain window, where the event may be defined in Clause 6.1.7 in 3GPP TS 38.214, herein incorporated by reference in its entirety. In this clause, an event is any occurrence that causes power consistency and phase continuity not to be maintained across transmissions. Specifically, these events include a downlink slot or downlink reception / monitoring based on TDD configuration for unpaired spectrum; gap duration exceeding a threshold where for UEs with certain capabilities the gapAG5254-PCT 1884.R64WO1between consecutive transmissions exceeds 13 symbols (normal CP) or 11 symbols (extended CP) and for UEs without those capabilities any non-zero symbol gap occurs; intervening uplink transmissions scheduled between consecutive SRS transmissions; dropping or cancellation of transmissions according to specified clauses or due to cell DRX operation; different SRS resource set association when applicable configurations are used; different spatial relations or power control parameters between consecutive transmissions; uplink timing adjustment in response to a timing advance command; frequency hopping between transmissions; and for reduced capability half-duplex UEs, dropping / cancellation or overlapping of gaps with downlink reception / monitoring.

[0081] A time domain window is the maximum duration configured by the network within which the UE is expected to maintain phase continuity and power consistency. This is a configured parameter that sets boundaries. An actual time domain window is the operational window that the UE actually uses starting from when the UE begins SRS transmission. The actual time domain window starts at the first symbol of the first SRS transmission. Restarting the actual time domain window means ending the current window and beginning a new one. This occurs when certain events happen that make it impossible or inappropriate to maintain the same phase reference and power level. When the window restarts, the UE essentially resets its phase and power reference point, allowing the UE to establish new baseline parameters appropriate for the changed conditions. The gNB is aware these events cause discontinuities and adjusts its receiver processing accordingly.

[0082] In one option, the start of the first actual time domain window is the first symbol of the first SRS transmission in a slot determined for SRS transmission within the nominal time domain window.

[0083] Further, the end of the actual time domain window may be defined as: the last symbol of the last SRS transmission in a slot within the nominal time domain window, if the actual time domain window reaches the end of the last SRS transmission within the nominal time domain window, and / or the last symbol of a SRS transmission before the event, if an event occurs which causes power consistency and phase continuity not be maintained across SRS transmissions of an SRS repetition within the nominal time domain window.AG5254-PCT 1884.R64WO1

[0084] During the actual time window, the UE maintains phase continuity and power consistency during the transmission of SRS repetition.

[0085] In some aspects, the actual time domain window, nominal time domain window, or UE behavior to maintain phase continuity and power consistency is applied to an SRS resource or an SRS resource set.

[0086] In another embodiment, the additional event to cause the UE to restart the time window may be defined as:

[0087] Frequency hopping for the SRS repetition. In some aspects, this may apply to the case when intra-slot and / or inter-slot frequency hopping is used for an SRS repetition or across slot SRS repetition;

[0088] A physical uplink share channel (PUSCH) and / or a physical uplink control channel (PUCCH) transmission between two SRS repetitions;

[0089] When cyclic shift hopping and / or comb offset hopping is applied for an SRS repetition or across SRS repetition;

[0090] Different spatial relations or power control parameters are applied for the transmission of an SRS within a repetition or across SRS repetition;

[0091] When an SRS symbol is dropped or cancelled during an SRS repetition or across SRS repetition due to collision with other uplink channel s / signaling, which may include PUSCH, PUCCH, physical random access channel (PRACH), or another SRS transmission; and / or

[0092] Usage for an SRS resource set is configured as “beam management” or “antenna switching”.

[0093] FIG. 6 illustrates a method of compressed SRS transmission, according to some examples. In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of the figures herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. For example, the method 600 may include UE processing circuitry receiving at step 602 a number of slots for SRS repetitions via RRC signaling. At step 604, the processing circuitry transmits the SRS with repetitions based on the number of slots. At step 606, the processing circuitry applies the same time domain resource allocation to the SRS resource in more than one slot.

[0094] Accordingly, this disclosure addresses coverage limitations in 5G and 6G cellular systems by enhancing SRS repetition capabilities. An SRS is aAG5254-PCT 1884.R64WO1reference signal transmitted by a UE to enable the gNB to acquire channel state information for uplink or downlink communication in TDD systems. The current 5G specification confines SRS repetition within a single slot, which is insufficient for cell-edge UEs with poor coverage. This SRS repetition is extended herein across multiple slots to improve uplink coverage. An SRS resource refers to a specific configured instance of an SRS transmission, which includes parameters such as time-domain allocation (symbols within a slot), frequency-domain allocation, comb offset, and cyclic shift values. An SRS resource set is a higher-level construct that contains one or more SRS resources and is configured by the gNB via RRC signaling for specific purposes such as precoding matrix determination or beam management. SRS repetition refers to the transmissions of the same SRS multiple times to improve coverage through combining gain at the receiver.

[0095] For the enhanced SRS repetition pattern, a number of approaches are considered. In one embodiment, SRS repetition across multiple slots applies the same time-domain and frequency-domain resource allocation to the SRS resource in each slot. This can be implemented on either a per-SRS-resource-set basis (where all resources in a set are repeated in a first slot, then all repeated in a second slot) or a per-SRS-resource basis (where a first resource is repeated across multiple slots before a second resource begins its repetitions). Another embodiment employs continuous time-domain resource allocation where SRS repetitions are transmitted consecutively across slot boundaries while maintaining the same frequency-domain allocation. Also addressed are practical considerations such as handling collisions with slot boundaries (through cancellation or deferral) and applying frequency hopping patterns, PRB offsets, comb offsets, or cyclic shift hopping across different slots.

[0096] Regarding UE behavior for SRS repetition, maintaining phase continuity and power consistency during multi-slot SRS transmission are described. A nominal time-domain window may be configured by higher layers, within which the UE maintains an actual time-domain window starting from the first symbol of the first SRS transmission. The UE maintains phase continuity and power consistency throughout this actual window, which terminates either at the end of the nominal window or when specific events occur. These triggering events include frequency hopping between repetitions, intervening PUSCH orAG5254-PCT 1884.R64WO1PUCCH transmissions between SRS repetitions, application of cyclic shift or comb offset hopping, changes in spatial relations or power control parameters, symbol cancellations due to collisions with other uplink channels, or when the SRS resource set usage is configured for beam management or antenna switching. This framework ensures reliable channel estimation across repeated transmissions while accommodating the dynamic nature of cellular systems.

[0097] Examples

[0098] Example 1 is a user equipment (UE) comprising: a processor that configures the UE to: receive a configuration for sounding reference signal (SRS) transmission, the configuration specifying a cross-slot SRS repetition pattern for at least one of an SRS resource and an SRS resource set, the crossslot SRS repetition pattern including a plurality of SRS repetitions spanning multiple slots; and transmit the at least one of the SRS resource and the SRS resource set in accordance with the cross-slot SRS repetition pattern, at least a first SRS repetition of the plurality of SRS repetitions transmitted in a first slot and a second SRS repetition of the plurality of SRS repetitions transmitted in a second slot different from the first slot; and a memory configured to store the configuration.

[0099] In Example 2, the subject matter of Example 1 includes, wherein the processor further configures the UE to apply a same time domain resource allocation and a same frequency domain resource allocation to each of the plurality of SRS repetitions across the multiple slots.[000100] In Example 3, the subject matter of Examples 1-2 includes, wherein: the cross-slot SRS repetition pattern is applied on a per-SRS-resource-set basis, the SRS resource set comprises a first SRS resource and a second SRS resource, and the processor further configures the UE to transmit the first SRS resource and the second SRS resource in the first slot, and then transmit the first SRS resource and the second SRS resource in the second slot.[000101] In Example 4, the subject matter of Examples 1-3 includes, wherein: the cross-slot SRS repetition pattern is applied on a per-SRS-resource-set basis, the SRS resource set comprises a first SRS resource and a second SRS resource, and the processor further configures the UE to complete all SRSAG5254-PCT 1884.R64WO1repetitions for the first SRS resource across the multiple slots before transmitting the second SRS resource.[000102] In Example 5, the subject matter of Examples 1-4 includes, wherein: the cross-slot SRS repetition pattern comprises continuous time domain resource allocation across slot boundaries, and the processor further configures the UE to transmit the plurality of SRS repetitions consecutively in a time domain while maintaining a same frequency domain resource allocation for each repetition.[000103] In Example 6, the subject matter of Examples 1-5 includes, wherein the processor further configures the UE to, in response to a determination that a particular SRS repetition of the cross-slot SRS repetition pattern collides with a slot boundary, select between cancellation of the particular SRS repetition and deferment of the particular SRS repetition to one of a next slot and next available slot.[000104] In Example 7, the subject matter of Examples 1-6 includes, wherein the processor further configures the UE to apply at least one of physical resource block (PRB) offset hopping, comb offset hopping, and cyclic shift hopping to different SRS repetitions of the cross-slot SRS repetition pattern, such that different values are used in different slots of the multiple slots.[000105] In Example 8, the subject matter of Examples 1-7 includes, wherein: the configuration further comprises at least one of an indication of the first slot for the first SRS repetition and the second slot for the second SRS repetition, and a slot offset between the first SRS repetition and the second SRS repetition, and the at least one of the indication and the slot offset is received via at least one of radio resource control (RRC) signaling and downlink control information (DCI).[000106] In Example 9, the subject matter of Examples 1-8 includes, wherein: the processor further configures the UE to transmit the plurality of SRS repetitions only in available slots for uplink transmission, and an available slot is a slot in which a particular SRS repetition does not overlap with semi-statically configured downlink symbols or flexible symbols used for synchronization signal block (SSB) transmission.[000107] In Example 10, the subject matter of Examples 1-9 includes, wherein the processor further configures the UE to: maintain phase continuityAG5254-PCT 1884.R64WO1and power consistency during transmission of the plurality of SRS repetitions of the cross-slot SRS repetition pattern within an actual time domain window spanning across the multiple slots; and restart the actual time domain window in response to detection of an event selected from among: frequency hopping between SRS repetitions, a physical uplink shared channel (PUSCH) between the SRS repetitions, physical uplink control channel (PUCCH) transmission between the SRS repetitions, cyclic shift hopping applied between the SRS repetitions, comb offset hopping applied between the SRS repetitions, a change in spatial relation between the SRS repetitions, a change in power control parameters between the SRS repetitions, cancellation of an SRS symbol due to collision with another uplink channel, the SRS resource set being configured for beam management, and the SRS resource being configured for antenna switching usage.[000108] Example 11 is a non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), receive a configuration for sounding reference signal (SRS) transmission, the configuration specifying a cross-slot SRS repetition pattern for at least one of an SRS resource and an SRS resource set, the crossslot SRS repetition pattern including a plurality of SRS repetitions spanning multiple slots; and transmit the at least one of the SRS resource and the SRS resource set in accordance with the cross-slot SRS repetition pattern, at least a first SRS repetition of the plurality of SRS repetitions transmitted in a first slot and a second SRS repetition of the plurality of SRS repetitions transmitted in a second slot different from the first slot.[000109] In Example 12, the subject matter of Example 11 includes, wherein the instructions, when executed, further cause the UE to apply a same time domain resource allocation and a same frequency domain resource allocation to each of the plurality of SRS repetitions across the multiple slots.[000110] In Example 13, the subject matter of Examples 11-12 includes, wherein: the cross-slot SRS repetition pattern is applied on a per-SRS-resource-set basis, the SRS resource set comprises a first SRS resource and a second SRS resource, and the instructions, when executed, further cause the UE to at least one of: transmit the first SRS resource and the second SRS resource in the first slot, and then transmit the first SRS resource and the second SRS resource in theAG5254-PCT 1884.R64WO1second slot, and complete all SRS repetitions for the first SRS resource across the multiple slots before transmitting the second SRS resource.[000111] In Example 14, the subject matter of Examples 11-13 includes, wherein: the cross-slot SRS repetition pattern comprises continuous time domain resource allocation across slot boundaries, and the instructions, when executed, further cause the UE to transmit the plurality of SRS repetitions consecutively in a time domain while maintaining a same frequency domain resource allocation for each repetition.[000112] In Example 15, the subject matter of Examples 11-14 includes, wherein the instructions, when executed, further cause the UE to, in response to a determination that a particular SRS repetition of the cross-slot SRS repetition pattern collides with a slot boundary, select between cancellation of the particular SRS repetition and deferment of the particular SRS repetition to one of a next slot and next available slot.[000113] In Example 16, the subject matter of Examples 11-15 includes, wherein the instructions, when executed, further cause the UE to apply at least one of physical resource block (PRB) offset hopping, comb offset hopping, and cyclic shift hopping to different SRS repetitions of the cross-slot SRS repetition pattern, such that different values are used in different slots of the multiple slots.[000114] In Example 17, the subject matter of Examples 11-16 includes, wherein: the configuration further comprises at least one of an indication of the first slot for the first SRS repetition and the second slot for the second SRS repetition, and a slot offset between the first SRS repetition and the second SRS repetition, and the at least one of the indication and the slot offset is received via at least one of radio resource control (RRC) signaling and downlink control information (DCI).[000115] In Example 18, the subject matter of Examples 11-17 includes, wherein: the instructions, when executed, further cause the UE to transmit the plurality of SRS repetitions only in available slots for uplink transmission, and an available slot is a slot in which a particular SRS repetition does not overlap with semi-statically configured downlink symbols or flexible symbols used for synchronization signal block (SSB) transmission.[000116] Example 19 is a 5th generation NodeB (gNB) comprising: a processor that configures the gNB to: generate a configuration for soundingAG5254-PCT 1884.R64WO1reference signal (SRS) transmission by a user equipment (UE), the configuration specifying a cross-slot SRS repetition pattern for at least one of an SRS resource and an SRS resource set, the cross-slot SRS repetition pattern including a plurality of SRS repetitions spanning multiple slots; transmit the configuration to the UE; and receive, from the UE, the at least one of the SRS resource and the SRS resource set in accordance with the cross-slot SRS repetition pattern, at least a first SRS repetition of the plurality of SRS repetitions transmitted in a first slot and a second SRS repetition of the plurality of SRS repetitions transmitted in a second slot different from the first slot; and a memory configured to store the configuration.[000117] In Example 20, the subject matter of Example 19 includes, wherein: the configuration further comprises at least one of: an indication of the first slot for the first SRS repetition and the second slot for the second SRS repetition, and a slot offset between the first SRS repetition and the second SRS repetition, and the processor further configures the gNB to transmit the indication or the slot offset via at least one of radio resource control (RRC) signaling or downlink control information (DCI).[000118] Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-20.[000119] Example 22 is an apparatus comprising means to implement of any of Examples 1-20.[000120] Example 23 is a system to implement of any of Examples 1-20.[000121] Example 24 is a method to implement of any of Examples 1-20.[000122] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural andAG5254-PCT 1884.R64WO1logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.[000123] The subject matter may be referred to herein, individually and / or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.[000124] In this document, the terms "a" or "an" are used, as is common in patent documents, to indicate one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. As indicated herein, although the term “a” is used herein, one or more of the associated elements may be used in different embodiments. For example, the term “a processor” configured to carry out specific operations includes both a single processor configured to carry out all of the operations as well as multiple processors individually configured to carry out some or all of the operations (which may overlap) such that the combination of processors carry out all of the operations.AG5254-PCT 1884.R64WO1Further, the term “includes” may be considered to be interpreted as “includes at least” the elements that follow.[000125] The Abstract of the Disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it may be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

AG5254-PCT 1884.R64WO1CLAIMSWhat is claimed is:

1. A user equipment (UE) comprising:a processor that configures the UE to:receive a configuration for sounding reference signal (SRS) transmission, the configuration specifying a cross-slot SRS repetition pattern for at least one of an SRS resource and an SRS resource set, the cross-slot SRS repetition pattern including a plurality of SRS repetitions spanning multiple slots; andtransmit the at least one of the SRS resource and the SRS resource set in accordance with the cross-slot SRS repetition pattern, at least a first SRS repetition of the plurality of SRS repetitions transmitted in a first slot and a second SRS repetition of the plurality of SRS repetitions transmitted in a second slot different from the first slot; and a memory configured to store the configuration.

2. The UE of claim 1, wherein the processor further configures the UE to apply a same time domain resource allocation and a same frequency domain resource allocation to each of the plurality of SRS repetitions across the multiple slots.

3. The UE of claim 1 or 2, wherein:the cross-slot SRS repetition pattern is applied on a per-SRS-resource-set basis,the SRS resource set comprises a first SRS resource and a second SRS resource, andthe processor further configures the UE to transmit the first SRS resource and the second SRS resource in the first slot, and then transmit the first SRS resource and the second SRS resource in the second slot.

4. The UE of any of claims 1-3, wherein:the cross-slot SRS repetition pattern is applied on a per-SRS-resource-set basis,AG5254-PCT 1884.R64WO1the SRS resource set comprises a first SRS resource and a second SRS resource, andthe processor further configures the UE to complete all SRS repetitions for the first SRS resource across the multiple slots before transmitting the second SRS resource.

5. The UE of any of claims 1-4, wherein:the cross-slot SRS repetition pattern comprises continuous time domain resource allocation across slot boundaries, andthe processor further configures the UE to transmit the plurality of SRS repetitions consecutively in a time domain while maintaining a same frequency domain resource allocation for each repetition.

6. The UE of any of claims 1-5, wherein the processor further configures the UE to, in response to a determination that a particular SRS repetition of the cross-slot SRS repetition pattern collides with a slot boundary, select between cancellation of the particular SRS repetition and deferment of the particular SRS repetition to one of a next slot and next available slot.

7. The UE of any of claims 1-6, wherein the processor further configures the UE to apply at least one of physical resource block (PRB) offset hopping, comb offset hopping, and cyclic shift hopping to different SRS repetitions of the cross-slot SRS repetition pattern, such that different values are used in different slots of the multiple slots.

8. The UE of any of claims 1-7, wherein:the configuration further comprises at least one of an indication of the first slot for the first SRS repetition and the second slot for the second SRS repetition, and a slot offset between the first SRS repetition and the second SRS repetition, andthe at least one of the indication and the slot offset is received via at least one of radio resource control (RRC) signaling and downlink control information (DCI).AG5254-PCT 1884.R64WO19. The UE of any of claims 1-8, wherein:the processor further configures the UE to transmit the plurality of SRS repetitions only in available slots for uplink transmission, andan available slot is a slot in which a particular SRS repetition does not overlap with semi-statically configured downlink symbols or flexible symbols used for synchronization signal block (SSB) transmission.

10. The UE of any of claims 1-9, wherein the processor further configures the UE to:maintain phase continuity and power consistency during transmission of the plurality of SRS repetitions of the cross-slot SRS repetition pattern within an actual time domain window spanning across the multiple slots; andrestart the actual time domain window in response to detection of an event selected from among:frequency hopping between SRS repetitions,a physical uplink shared channel (PUSCH) between the SRS repetitions,physical uplink control channel (PUCCH) transmission between the SRS repetitions,cyclic shift hopping applied between the SRS repetitions, comb offset hopping applied between the SRS repetitions, a change in spatial relation between the SRS repetitions, a change in power control parameters between the SRS repetitions,cancellation of an SRS symbol due to collision with another uplink channel,the SRS resource set being configured for beam management, and the SRS resource being configured for antenna switching usage.

11. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), that when executed, cause the UE to:receive a configuration for sounding reference signal (SRS) transmission, the configuration specifying a cross-slot SRS repetition pattern for at least one ofAG5254-PCT 1884.R64WO1an SRS resource and an SRS resource set, the cross-slot SRS repetition pattern including a plurality of SRS repetitions spanning multiple slots; and transmit the at least one of the SRS resource and the SRS resource set in accordance with the cross-slot SRS repetition pattern, at least a first SRS repetition of the plurality of SRS repetitions transmitted in a first slot and a second SRS repetition of the plurality of SRS repetitions transmitted in a second slot different from the first slot.

12. The non-transitory computer-readable storage medium of claim 11, wherein the instructions, when executed, further cause the UE to apply a same time domain resource allocation and a same frequency domain resource allocation to each of the plurality of SRS repetitions across the multiple slots.

13. The non-transitory computer-readable storage medium of claim 11 or 12, wherein:the cross-slot SRS repetition pattern is applied on a per-SRS-resource-set basis,the SRS resource set comprises a first SRS resource and a second SRS resource, andthe instructions, when executed, further cause the UE to at least one of:transmit the first SRS resource and the second SRS resource in the first slot, and then transmit the first SRS resource and the second SRS resource in the second slot, andcomplete all SRS repetitions for the first SRS resource across the multiple slots before transmitting the second SRS resource.

14. The non-transitory computer-readable storage medium of any of claims 11-13, wherein:the cross-slot SRS repetition pattern comprises continuous time domain resource allocation across slot boundaries, andthe instructions, when executed, further cause the UE to transmit the plurality of SRS repetitions consecutively in a time domain while maintaining a same frequency domain resource allocation for each repetition.AG5254-PCT 1884.R64WO115. The non-transitory computer-readable storage medium of any of claims 11-14, wherein the instructions, when executed, further cause the UE to, in response to a determination that a particular SRS repetition of the cross-slot SRS repetition pattern collides with a slot boundary, select between cancellation of the particular SRS repetition and deferment of the particular SRS repetition to one of a next slot and next available slot.

16. The non-transitory computer-readable storage medium of any of claims 11-15, wherein the instructions, when executed, further cause the UE to apply at least one of physical resource block (PRB) offset hopping, comb offset hopping, and cyclic shift hopping to different SRS repetitions of the cross-slot SRS repetition pattern, such that different values are used in different slots of the multiple slots.

17. The non-transitory computer-readable storage medium of any of claims 11-16, wherein:the configuration further comprises at least one of an indication of the first slot for the first SRS repetition and the second slot for the second SRS repetition, and a slot offset between the first SRS repetition and the second SRS repetition, andthe at least one of the indication and the slot offset is received via at least one of radio resource control (RRC) signaling and downlink control information (DCI).

18. The non-transitory computer-readable storage medium of any of claims 11-17, wherein:the instructions, when executed, further cause the UE to transmit the plurality of SRS repetitions only in available slots for uplink transmission, and an available slot is a slot in which a particular SRS repetition does not overlap with semi-statically configured downlink symbols or flexible symbols used for synchronization signal block (SSB) transmission.

19. A 5thgeneration NodeB (gNB) comprising:a processor that configures the gNB to:AG5254-PCT 1884.R64WO1generate a configuration for sounding reference signal (SRS) transmission by a user equipment (UE), the configuration specifying a cross-slot SRS repetition pattern for at least one of an SRS resource and an SRS resource set, the cross-slot SRS repetition pattern including a plurality of SRS repetitions spanning multiple slots;transmit the configuration to the UE; andreceive, from the UE, the at least one of the SRS resource and the SRS resource set in accordance with the cross-slot SRS repetition pattern, at least a first SRS repetition of the plurality of SRS repetitions transmitted in a first slot and a second SRS repetition of the plurality of SRS repetitions transmitted in a second slot different from the first slot; anda memory configured to store the configuration.

20. The gNB of claim 19, wherein:the configuration further comprises at least one ofan indication of the first slot for the first SRS repetition and the second slot for the second SRS repetition, anda slot offset between the first SRS repetition and the second SRS repetition, andthe processor further configures the gNB to transmit the indication or the slot offset via at least one of radio resource control (RRC) signaling or downlink control information (DCI).

Images