WO2023050302A1

WO2023050302A1 - Collision handling for aperiodic srs triggering

Info

Publication number: WO2023050302A1
Application number: PCT/CN2021/122150
Authority: WO
Inventors: Bingchao LIU; Lingling Xiao; Hongmei Liu; Haiming Wang
Original assignee: Lenovo (Beijing) Limited
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2023-04-06

Abstract

Methods and apparatuses for handling collision for aperiodic SRS triggering are disclosed. A method at an UE comprises receiving one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; determining which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and transmitting, in the at least one same symbol, the SRS resource determined to have the highest priority.

Description

COLLISION HANDLING FOR APERIODIC SRS TRIGGERING

FIELD

The subject matter disclosed herein generally relates to wireless communications, and more particularly relates to methods and apparatuses for handling collision for aperiodic SRS triggering.

BACKGROUND

The following abbreviations are herewith defined, at least some of which are referred to within the following description: New Radio (NR) , Very Large Scale Integration (VLSI) , Random Access Memory (RAM) , Read-Only Memory (ROM) , Erasable Programmable Read-Only Memory (EPROM or Flash Memory) , Compact Disc Read-Only Memory (CD-ROM) , Local Area Network (LAN) , Wide Area Network (WAN) , User Equipment (UE) , Evolved Node B (eNB) , Next Generation Node B (gNB) , Uplink (UL) , Downlink (DL) , Central Processing Unit (CPU) , Graphics Processing Unit (GPU) , Field Programmable Gate Array (FPGA) , Orthogonal Frequency Division Multiplexing (OFDM) , Radio Resource Control (RRC) , User Entity/Equipment (Mobile Terminal) , Transmitter (TX) , Receiver (RX) , Sounding Reference Signal (SRS) , Downlink Control Information (DCI) , (RRC) , Physical Downlink Control Channel (PDCCH) , Physical Uplink Shared Channel (PUSCH) , Multiple-Input Multiple-Output (MIMO) , Channel State Information (CSI) , Time-Division Duplex (TDD) .

In NR Release 15, an aperiodic SRS can only be transmitted in slot n+k, where the DCI triggering the aperiodic SRS resource (s) (e.g. triggering the aperiodic SRS resource set containing the aperiodic SRS resource (s) ) on which SRS is transmitted is transmitted in slot n, and k is the slot offset configured for the aperiodic SRS resource set by RRC signaling. If slot n+k is not an available UL slot or the OFDM symbol (s) in slot n+k for SRS transmission are not configured for UL transmission, the triggered SRS resource shall not be transmitted. In the following description, an OFDM symbol is abbreviated as a symbol. Moreover, this application is only related to aperiodic SRS resource or aperiodic SRS resource set, which may be, as appropriate, abbreviated as SRS resource or SRS resource set.

Flexible aperiodic SRS triggering mechanism was introduced in NR Release 17. In the flexible aperiodic SRS triggering mechanism, a new parameter t≥0 is indicated in the DCI (for example by containing a t value field) triggering the aperiodic SRS resource (e.g. triggering the aperiodic SRS resource set containing the aperiodic SRS resource) . The parameter t means that the SRS is transmitted in (t+1) ^th available slot counting from slot n+k. An “available slot” is a slot satisfying there are UL symbol (s) or flexible symbol (s) , which can be used as UL symbol or DL symbol, for the time domain location (s) (e.g. symbol (s) ) for all the SRS resources in the SRS resource set and satisfying UE capability on the minimum timing requirement between PDCCH containing triggering DCI and all the SRS resources in the SRS resource set. Since SRS will be definitely transmitted in the available slot, the triggering flexibility of aperiodic SRS can be improved.

Although the triggered SRS resource by the flexible aperiodic SRS triggering mechanism can be ensured to be transmitted by finding an available slot, different SRS resources may conflict (e.g. overlap) due to finding a same available slot. For example, different SRS resources may be determined to be transmitted on same symbol (s) of the same slot. It may happen for the case that multiple SRS resource sets are triggered by a same DCI, since different SRS resource sets may be configured with different slot offsets. It may also happen for the case that different SRS resource sets are triggered by different DCIs.

Figure 1 illustrates an example of SRS collision for the case that multiple SRS resource sets are triggered by a same DCI. As illustrated in Figure 1, a UE receives a DCI (transmitted in slot n) containing an SRS request field with value ‘10’ and a t value with value of ‘2’ . Three aperiodic SRS resource sets including SRS resource set#1, SRS resource set#2 and SRS resource set#3 are associated with the SRS request codepoint ‘10’ . The slot offset k = 0 is configured for SRS resource set#1; the slot offset k =1 is configured for SRS resource set#2; and the slot offset k =2 is configured for SRS resource set#3. In addition, as shown in Figure 1, slot n, slot n+1 and slot n+6 are non-available slots, while slot n+2, slot n+3, slot n+4 and slot n+5 are available slots. It means that

SRS resource set#1 (with k = 0 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot counting from slot n (slot n + k = slot n + 0 = slot n) , that is slot n+4 (note that, counting from slot n, the first available slot is n+2, and the second available slot is n+3) ;

SRS resource set#2 (with k = 1 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot counting from slot n+1 (slot n + k = slot n + 1 = slot n+1) , that is slot n+4 (note that, counting from slot n+1, the first available slot is n+2, and the second available slot is n+3) ; and

SRS resource set#3 (with k = 2 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot counting from slot n+2 (slot n + k = slot n + 2 = slot n+2) , that is slot n+5 (note that, counting from slot n+2, the first available slot is n+3, and the second available slot is n+4) .

If the time location (e.g. symbol (s) ) for the SRS resources in SRS resource set#1 and the time location (e.g. symbol (s) ) for the SRS resources in SRS resource set#2 overlap (i.e. collide) in at least one same symbol, a dropping rule is required for the UE to select the SRS resources (from SRS resource set#1 or from SRS resource set#2) to transmit in the overlapped at least one same symbol.

Figure 2 illustrates an example of SRS collision for the case that multiple SRS resource sets are triggered by different DCIs (as well as multiple SRS resource sets are triggered by a same DCI) . As illustrated in Figure 2, a UE receives a DCI#1 (transmitted in slot n-2) containing an SRS request field with value ‘11’ and a t value with value of ‘0’ , and a DCI#2 (transmitted in slot n) containing an SRS request field with value ‘10’ and a t value with value of ‘2’ . Three aperiodic SRS resource sets including SRS resource set#1, SRS resource set#2 and SRS resource set#3 are associated with the SRS request codepoint ‘10’ . Two aperiodic SRS resource sets including SRS resource set#4 and SRS resource set#5 are associated with the SRS request codepoint ‘11’ . In addition, the slot offset k = 0 is configured for SRS resource set#1; the slot offset k =1 is configured for SRS resource set#2; the slot offset k =2 is configured for SRS resource set#3; the slot offset k = 1 is configured for SRS resource set#4; and the slot offset k =6 is configured for SRS resource set#5. In addition, as shown in Figure 2, slot n-4, slot n, slot n+1 and slot n+6 are non-available slots, while slot n-3, slot n-2, slot n-1, slot n+2, slot n+3, slot n+4 and slot n+5 are available slots. So,

SRS resource set#1 (with k = 0 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot counting from slot n (slot n + k = slot n + 0 = slot n) ) , that is slot n+4;

SRS resource set#2 (with k = 1 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot (counting from slot n+1 (slot n + k = slot n + 1 = slot n+1) ) , that is slot n+4;

SRS resource set#3 (with k = 2 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot (counting from slot n+2 (slot n + k = slot n + 2 = slot n+2) ) , that is slot n+5;

SRS resource set#4 (with k = 1 and t = 0) should be transmitted in the first ( (t+1) ^th = (0+1) ^th = 1 ^st) available slot (counting from slot n-1 (slot n-2 + k = slot n-2 + 1 = slot n-1) ) , that is slot n+2; and

SRS resource set#5 (with k = 6 and t = 0) should be transmitted in the first ( (t+1) ^th = (0+1) ^th = 1 ^st) available slot (counting from slot n+4 (slot n-2 + k = slot n-2 + 6 = slot n+4) ) , that is slot n+5.

If the time location (e.g. symbol (s) ) for the SRS resources in SRS resource set#1 and the time location (e.g. symbol (s) ) for the SRS resources in SRS resource set#2 overlap (i.e. collide) in at least one same symbol (labelled as “at least one same symbol between SRS resource set#1 and SRS resource set#2” in Figure 2) , a dropping rule is required for the UE to select the SRS resource (s) (from SRS resource set#1 or from SRS resource set#2) to transmit in the at least one same symbol between SRS resource set#1 and SRS resource set#2. In addition, if the time location (e.g. symbol (s) ) for the SRS resources in SRS resource set#3 and the time location (e.g. symbol (s) ) for the SRS resources in SRS resource set#5 overlap (i.e. collide) in at least one same symbol (labelled as “at least one same symbol between SRS resource set#3 and SRS resource set#5” in Figure 2) , a dropping rule is required for the UE to select the SRS resource (s) (from SRS resource set#3 or from SRS resource set#5) to transmit in the at least one same symbol between SRS resource set#3 and SRS resource set#5.

This invention targets handling collision for aperiodic SRS triggering, that is, how to select SRS resource (s) to be transmitted in the overlapped at least one same symbol.

BRIEF SUMMARY

Methods and apparatuses for handling collision for aperiodic SRS triggering are disclosed.

In one embodiment, a method at an UE comprises receiving one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; determining which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and transmitting, in the at least one same symbol, the SRS resource determined to have the highest priority.

In one embodiment, priority rule #1 may be determined as one of the priority rule candidates including priority rule candidate #1: ‘beamManagement’ > ‘antennaSwitching’ >‘codebook’ or ‘nonCodebook’ ; priority rule candidate #2: ‘antennaSwitching’ >‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ ; priority rule candidate #3: ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ > ‘antennaSwitching’ ; priority rule candidate #4: ‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ ; priority rule candidate #5: ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ ; and priority rule candidate #6: ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ >‘beamManagement’ . Priority rule #2 may be determined as one of the candidates including priority rule #2, candidate #1: the SRS resources triggered by a DCI containing t value field have a higher priority than the SRS resources triggered by a DCI that does not contain t value field; and priority rule #2, candidate #2: the SRS resources triggered by the DCI that does not contain t value field have a higher priority than the SRS resources triggered by the DCI containing t value field. Priority rule #3 may be determined as one of the candidates including priority rule #3, candidate #1: the SRS resource (s) triggered by the latest DCI have the highest priority; and priority rule #3, candidate #2: the SRS resource (s) triggered by the earliest DCI have the highest priority. Priority rule #4 is determined as one of the candidates including priority rule #4, candidate #1: the SRS resource configured with the largest slot offset value has the highest priority; and priority rule #4, candidate #2: the SRS resource configured with the smallest slot offset value has the highest priority. Priority rule #5 may be determined as one of the candidates including priority rule #5, candidate #1: the SRS resource that has the largest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority; and priority rule #5, candidate #2: the SRS resource that has the smallest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority. Priority rule #6 may be determined as one of the candidates including priority rule #6, candidate #1: the SRS resource that is associated with the largest SRS resource set ID is determined as having the highest priority; and priority rule #6, candidate #2: the SRS resource that is associated with the smallest SRS resource set ID is determined as having the highest priority.

In some embodiment, the determining which SRS resource has the highest priority is according to a first priority rule order of priority rule #1, priority rule #2, priority rule #3 and priority rule #4, or a second priority rule order of priority rule #1, priority rule #3 and priority rule #4. In some embodiment, the determining which SRS resource has the highest priority is according to priority rule #5 or priority rule #6. In some embodiment, the determining which SRS resource has the highest priority is according to a third priority rule order of priority rule #3 and priority rule #4, or a fourth priority rule order of priority rule #2, priority rule #3 and priority rule #4.

In one embodiment, a method at a base unit comprises transmitting one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; determining which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and receiving, in the at least one same symbol, the SRS resource determined to have the highest priority.

In another embodiment, a remote unit (UE) comprises a receiver that receives one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; a processor that determines which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and a transmitter that transmits, in the at least one same symbol, the SRS resource determined to have the highest priority.

In yet another embodiment, a base unit comprises a transmitter that transmits one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; a processor that determines which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and a receiver that receives, in the at least one same symbol, the SRS resource determined to have the highest priority.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments, and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

Figure 1 illustrates an example of SRS collision for the case that multiple SRS resource sets are triggered by a same DCI;

Figure 2 illustrates an example of SRS collision for the case that multiple SRS resource sets are triggered by different DCIs;

Figure 3 illustrates another example of SRS collision for the case that multiple SRS resource sets are triggered by a same DCI;

Figure 4 is a schematic flow chart diagram illustrating an embodiment of a method;

Figure 5 is a schematic flow chart diagram illustrating another embodiment of a method; and

Figure 6 is a schematic block diagram illustrating apparatuses according to one embodiment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art that certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit” , “module” or “system” . Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” . The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

Certain functional units described in this specification may be labeled as “modules” , in order to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM) , read-only memory (ROM) , erasable programmable read-only memory (EPROM or Flash Memory) , portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .

Reference throughout this specification to “one embodiment” , “an embodiment” , or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment” , “in an embodiment” , and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including” , “comprising” , “having” , and variations thereof mean “including but are not limited to” , unless otherwise expressly specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, otherwise unless expressly specified. The terms “a” , “an” , and “the” also refer to “one or more” unless otherwise expressly specified.

Furthermore, described features, structures, or characteristics of various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid any obscuring of aspects of an embodiment.

Aspects of different embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .

It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may substantially be executed concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures.

Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each Figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

This application proposes that, among two or more triggered aperiodic SRS resources that collide (or overlap) in at least one same symbol, one of the two or more aperiodic SRS resources that has the highest priority is transmitted in the at least one same symbol, while the other (s) of the two or more aperiodic SRS resources (i.e. the aperiodic SRS resource (s) that do not have the highest priority) will be dropped (i.e. not be transmitted in the at least one same symbol) .

In view of the above, embodiments of this application relate to different priority rules to determine which SRS resource among the triggered SRS resources that collide has the highest priority (or the higher priority if only two triggered SRS resources collide) .

The priority rule according to a first embodiment is based on the usage of each of the triggered SRS resources that collide.

Each SRS resource set is configured with a higher layer parameter usage to indicate the applicability of the SRS resources in this SRS resource set. To support uplink beam management, one or more SRS resource sets with usage = beamManagement are configured. To support CSI acquisition for two UL MIMO modes in NR (codebook based precoding and non-codebook based precoding) , the gNB configures the UE with one or two SRS resource sets with usage = codebook or nonCodebook, wherein each SRS resource set contains up to 2 or 4 SRS resources. To support reciprocity-based operation in TDD deployments, i.e. where the gNB acquires detailed CSI for the DL channel based on estimates of the UL channel, the gNB configures one or more SRS resource sets with usage = antennaSwitching. As a whole, the usage of a SRS resource set can be set to ‘beamManagement’ , ‘codebook’ , ‘nonCodebook’ or ‘antennaSwitching’ . In particular, all SRS resources in an SRS resource set have the same usage configured to the SRS resource set.

For a same UE, up to two SRS resource sets can be configured for ‘codebook’ usage or ‘non-codebook’ usage depending on the PUSCH transmission type. For example, if codebook based PUSCH transmission is configured, up to two SRS resource sets can be configured for ‘codebook’ usage. If non-codebook based PUSCH transmission is configured, up to two SRS resource sets can be configured for ‘codebook’ usage. As a result, it is impossible to concurrently configure both SRS resource sets for ‘codebook’ usage and SRS resource sets for ‘nonCodebook’ usage for the same UE. So, the SRS resource set with ‘codebook’ usage and the SRS resource set with ‘nonCodebook’ usage should have the same priority.

According to the first embodiment, the following six alternative priority rule candidates are proposed:

Priority rule candidate #1: ‘beamManagement’ > ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ ;

Priority rule candidate #2: ‘antennaSwitching’ > ‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ ;

Priority rule candidate #3: ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ > ‘antennaSwitching’ ;

Priority rule candidate #4: ‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ ;

Priority rule candidate #5: ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ ; and

Priority rule candidate #6: ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ > ‘beamManagement’ .

The usage appeared in front of “>” has a higher priority than the usage appeared behind “>” . For example, according to priority rule candidate #1: the SRS resources within the SRS resource set configured with ‘beamManagement’ usage (which can be described as the SRS resources with ‘beamManagement’ usage) have a higher priority than the SRS resources with ‘antennaSwitching’ usage, which have a higher priority than the SRS resources with ‘codebook’ or ‘nonCodebook’ usage.

Multiple aperiodic SRS resource sets, each of which is associated with an aperiodic SRS triggering state, i.e., SRS request codepoint, can be configured for a UE. Two or more aperiodic SRS resource sets with the same usage or different usages can be associated with one aperiodic SRS triggering state. So, it is possible that two or more SRS resources with the same usage are triggered to be transmitted in at least one same symbol. In other words, the triggered aperiodic SRS resources that collide may have the same usage (i.e. the same priority) , which would cause impossibility to determine which one of the aperiodic SRS resources that collide has the highest priority only based on the usage of each of the triggered SRS resources that collide.

In this condition, additional priority rule (s) in addition to being based on the usage of each of the triggered SRS resources that collide (defined as priority rule #1) are necessary.

The following priority rules are further proposed.

(1) Priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide. Aperiodic SRS resources can be triggered by an NR Release 15 (or NR Release 16) version DCI (i.e. a DCI without indicating a t value, or a DCI that does not contain t value field) , or by an NR Release 17 version DCI (i.e. a DCI indicating a t value, or a DCI contains t value field) . For example, the SRS resources triggered by NR Release 17 version DCI (i.e. a DCI containing t value field) have a higher priority than the SRS resources triggered by NR Release 15 or 16 version DCI (i.e. a DCI that does not contain t value field) (priority rule #2, candidate #1) . Alternatively, the SRS resources triggered by NR Release 15 or 16 version DCI (i.e. a DCI that does not contain t value field) have a higher priority than the SRS resources triggered by NR Release 17 version DCI (i.e. a DCI containing t value field) (priority rule #2, candidate #2) .

(2) Priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide. For example, the SRS resource (s) triggered by the latest DCI have the highest priority (priority rule #3, candidate #1) . Alternatively, the SRS resource (s) triggered by the earliest DCI have the highest priority (priority rule #3, candidate #2) .

(3) Priority rule #4: based on the slot offset (i.e. the value of k) configured to each of the triggered SRS resources that collide. For example, the SRS resource configured with the largest slot offset value, e.g. among the SRS resources triggered by a same DCI, has the highest priority (priority rule #4, candidate #1) . Alternatively, the SRS resource configured with the smallest slot offset value, e.g. among the SRS resources triggered by a same DCI, has the highest priority (priority rule #4, candidate #2) . Priority rule #4 may work for the scenario that the SRS resources that triggered by the same DCI.

As a whole, according to the first embodiment, the SRS resource that has the highest priority among the triggered SRS resources that collide is determined according to a priority rule order of priority rule #1, priority rule #2, priority rule #3 and priority rule #4.

It means that the SRS resource that has the highest priority among the triggered SRS resources that collide is determined based on priority rule #1 in a first step. In particular, the SRS resource with the highest priority is determined based on the usage of each of the triggered SRS resources that collide (e.g. the SRS resource with the ‘beamManagement’ usage has the highest priority according to priority rule #1, priority rule candidate #1) .

If two or more SRS resources have the same highest priority based on priority rule #1, the SRS resource that has the highest priority among the two or more SRS resources that have the same highest priority based on priority rule #1 is further determined based on priority rule #2 in a second step. In particular, the SRS resource with the highest priority is determined based on a version of the DCI triggering each of the SRS resources (e.g. the SRS resource triggered by a DCI of NR Release 17 version (i.e. a DCI indicating a t value) has the highest priority according to priority rule #2, candidate #1) .

If two or more SRS resources have the same highest priority based on priority rule #2, the SRS resource that has the highest priority among the two or more SRS resources that have the same highest priority based on priority rule #2 is further determined based on priority rule #3 in a third step. In particular, the SRS resource with the highest priority is determined based on the triggering time of the DCI triggering each of the SRS resources (e.g. the SRS resource triggered by the latest triggering DCI has the highest priority according to priority rule #3, candidate #1) .

If two or more SRS resources have the same highest priority based on priority rule #3, the SRS resource that has the highest priority among the two or more SRS resources that have the same highest priority based on priority rule #3 is further determined based on priority rule #4 in a fourth step. In particular, the SRS resource with the highest priority is determined based on the slot offset (i.e. the value of k) configured to each of the SRS resources (e.g. the SRS resource configured with the largest slot offset has the highest priority according to priority rule #4, candidate #1) .

Accordingly, by at least the first step of determining the highest priority based on priority rule #1, i.e.

by the first step of determining the highest priority based on priority rule #1; or

by the first step of determining the highest priority based on priority rule #1 and the second step of determining the highest priority based on priority rule #2, or

by the first step of determining the highest priority based on priority rule #1 and the second step of determining the highest priority based on priority rule #2 and the third step of determining the highest priority based on priority rule #3; or

by the first step of determining the highest priority based on priority rule #1 and the second step of determining the highest priority based on priority rule #2 and the third step of determining the highest priority based on priority rule #3 and the fourth step of determining the highest priority based on priority rule #4,

one of the triggered SRS resources that collide in at least one same symbol that has the highest priority can be determined. Accordingly, the SRS resource that has the highest priority will be transmitted in the at least one same symbol, while the other SRS resource (s) (that do not have the highest priority) will be dropped (i.e. not be transmitted in the at least one same symbol) .

Incidentally, the priority rule #2 may not be used in determining which SRS resource among the triggered SRS resources that collide has the highest priority. In other words, a priority rule order of priority rule #1, priority rule #3 and priority rule #4 can be used to determine which SRS resource among the triggered SRS resources that collide has the highest priority, irrespective of the version of the DCI triggering each of the SRS resources. It means that priority rule #1 is first used to determine the SRS resource that has the highest priority; and if necessary, priority rule #3 is secondly used to determine the SRS resource that has the highest priority among the SRS resources that all have the same highest priority based on priority rule #1; and if necessary, priority rule #4 is thirdly used to determine the SRS resource that has the highest priority among the SRS resources that all have the same highest priority based on priority rule #3.

The priority rule according to a second embodiment is based on SRS resource ID or SRS resource set ID.

Each SRS resource has a unique ID (e.g. SRS resource ID) . So, the priority of the triggered SRS resources that collide can be determined based on SRS resource ID of each of the triggered SRS resources that collide (defined as priority rule #5) . For example, the SRS resource that has the largest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority (priority rule #5, candidate #1) . Alternatively, the SRS resource that has the smallest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority (priority rule #5, candidate #2) .

Since the SRS resources of a same SRS resource set cannot be configured to be transmitted in the same symbol, if two or more SRS resources are triggered to be transmitted in at least one same symbol of a slot, each of the two or more SRS resources would belong to a different SRS resource set. Each SRS resource set is configured with a unique ID (e.g. SRS resource set ID) . So, the priority of the triggered SRS resources that collide can be determined based on the SRS resource set ID of the SRS resource set containing the SRS resource (which can be expressed as the SRS resource set ID associated with the SRS resource) (defined as priority rule #6) . For example, the SRS resource that is associated with the largest SRS resource set ID is determined as having the highest priority (priority rule #6, candidate #1) . Alternatively, the SRS resource that is associated with the smallest SRS resource set ID is determined as having the highest priority (priority rule #6, candidate #2) .

The priority rule according to a third embodiment is first based on the triggering time of the DCI triggering each of the triggered SRS resources that collide (i.e. priority rule #3) . When the highest priority cannot be determined according to priority rule #3 (e.g. two or more SRS resources that collide are triggered by the same DCI) , the highest priority is further determined based on the slot offset (i.e. the value of k) configured to each of the triggered SRS resources that collide (i.e. priority rule #4) . Optionally, the priority rule #2 (based on a version of the DCI triggering each of the triggered SRS resources that collide) can be also considered in the third embodiment.

As a whole, according to the third embodiment, the SRS resource that has the highest priority among the triggered SRS resources that collide is determined according to a priority rule order of priority rule #3 and priority rule #4. According to a variety of the third embodiment, the SRS resource that has the highest priority among the triggered SRS resources that collide is determined according to a priority rule order of priority rule #2, priority rule #3 and priority rule #4.

Figure 3 illustrates another example that multiple SRS resources triggered by a same DCI collide in at least one same symbol. A UE receives a DCI (transmitted in slot n) containing an SRS request field with value ‘10’ and a t value with value of ‘2’ . Three aperiodic SRS resource sets including SRS resource set#1, SRS resource set#2 and SRS resource set#3 are associated with the SRS request codepoint ‘10’ . The slot offset k = 0 is configured for SRS resource set#1; the slot offset k =1 is configured for SRS resource set#2; and the slot offset k =2 is configured for SRS resource set#3. In addition, as shown in Figure 3, slot n, slot n+1, slot n+2 and slot n+6 are non-available slots, while slot n+3, slot n+4 and slot n+5 are available slots. It means that

SRS resource set#1 (with k = 0 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot counting from slot n (slot n + k = slot n + 0 = slot n) , that is slot n+5 (note that, counting from slot n, the first available slot is n+3, and the second available slot is n+4) ) ;

SRS resource set#2 (with k = 1 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot counting from slot n+1 (slot n + k = slot n + 1 = slot n+1) , that is slot n+5 (note that, counting from slot n+1, the first available slot is n+3, and the second available slot is n+4) ) ; and

SRS resource set#3 (with k = 2 and t = 2) should be transmitted in the third (i.e. (t+1) ^th = (2+1) ^th = 3 ^rd) available slot counting from slot n+2 (slot n + k = slot n + 2 = slot n+2) , that is slot n+5 (note that, counting from slot n+2, the first available slot is n+3, and the second available slot is n+4) ) .

SRS resource set#1 and SRS resource set#2 are configured for ‘beamManagement’ usage, while SRS resource set#3 is configured for ‘codebook’ usage. It can be seen from Figure 3 that some SRS resources from SRS resource set#1 and some SRS resources from SRS resource set#2 are triggered to be transmitted in at least one same symbol (labelled as “at least one same symbol between SRS resource set#1 and SRS resource set#2” in Figure 3) , and some SRS resources form SRS resource set#2 and some SRS resources from SRS resource set#3 are triggered to be transmitted in at least one same symbol (labelled as “at least one same symbol between SRS resource set#2 and SRS resource set#3” in Figure 3) .

If the first embodiment is adopted, i.e. a priority rule order of priority rule #1, priority rule #2, priority rule #3 and priority rule #4, or a priority rule order of priority rule #1, priority rule #3 and priority rule #4 is applied. Since the collision occurred in the example of Figure 3 only relates to SRS resources (or SRS resources of SRS resource sets) triggered by a same DCI, priority rule #2 and priority rule #3, which relate to the priority of DCIs, are not applicable. So, according to the priority rule of the first embodiment, the priority of the triggered SRS resources that collide will be first determined according to priority rule #1, and if the highest priority (or higher priority) cannot be determined, the priority of the triggered SRS resources that collide will be further determined according to priority rule #4. For priority rule #1, we assume that priority rule candidate #1 (i.e. ‘beamManagement’ > ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ ) applies. For priority rule #4, we assume that priority rule #4, candidate #1 (i.e. the SRS resource configured with the largest slot offset value has the highest priority) applies.

Accordingly, for the SRS resources from SRS resource set#1 that overlap with (i.e. collide with) the SRS resources from SRS resource set#2 in at least one same symbol between SRS resource set#1 and SRS resource set#2, since the SRS resources from SRS resource set#1 (for ‘beamManagement’ usage) and the SRS resources from SRS resource set#2 (for ‘beamManagement’ usage) have the same priority based on priority rule #1 (priority rule candidate #1) , while the SRS resources from SRS resource set#2 (with slot offset k =1) has a higher priority than the SRS resources from SRS resource set#1 (with slot offset k =0) based on priority rule #4, candidate #1) , the SRS resources from SRS resource set#2 are transmitted in the “at least one same symbol between SRS resource set#1 and SRS resource set#2” , while the SRS resources from SRS resource set#1 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#1 and SRS resource set#2” ) .

For the SRS resources from SRS resource set#2 that overlap with (i.e. collide with) the SRS resources from SRS resource set#3 in at least one same symbol between SRS resource set#2 and SRS resource set#3, since the SRS resources from SRS resource set#2 (for ‘beamManagement’ usage) have a higher priority than the SRS resources from SRS resource set#3 (for ‘codebook’ usage) based on priority rule #1 (priority rule candidate #1) , the SRS resources from SRS resource set#2 are transmitted in the “at least one same symbol between SRS resource set#2 and SRS resource set#3” , while the SRS resources from SRS resource set#3 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#2 and SRS resource set#3” ) .

If the second embodiment is adopted, i.e. priority rule #5 or priority rule #6 is applied. Since the collision occurred in the example of Figure 3 only relates to SRS resources (or SRS resources of SRS resource sets) triggered by a same DCI, priority rule #6 can be applied. So, according to the priority rule of the second embodiment, the priority of the triggered SRS resources that collide is determined based on priority rule #6. For priority rule #6, we assume priority rule #6, candidate #1 (i.e. the SRS resource that is associated with the largest SRS resource set ID is determined as having the highest priority) applies.

Accordingly, for the SRS resources from SRS resource set#1 that overlap with (i.e. collide with) the SRS resources from SRS resource set#2 in at least one same symbol between SRS resource set#1 and SRS resource set#2, since the SRS resources from SRS resource set#2 (associated with SRS resource set ID = 2) have a higher priority than the SRS resources from SRS resource set#1 (associated with SRS resource set ID = 1) based on priority rule #6, candidate #1, the SRS resources from SRS resource set#2 are transmitted in the “at least one same symbol between SRS resource set#1 and SRS resource set#2” , while the SRS resources from SRS resource set#1 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#1 and SRS resource set#2” ) .

For the SRS resources from SRS resource set#2 that overlap with (i.e. collide with) the SRS resources from SRS resource set#3 in at least one same symbol between SRS resource set#2 and SRS resource set#3, since the SRS resources from SRS resource set#3 (associated with SRS resource set ID = 3) have a higher priority than the SRS resources from SRS resource set#2 (associated with SRS resource set ID = 2) based on priority rule #6, candidate #1, the SRS resources from SRS resource set#3 are transmitted in the “at least one same symbol between SRS resource set#2 and SRS resource set#3” , while the SRS resources from SRS resource set#2 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#2 and SRS resource set#3” ) .

If the third embodiment is adopted, i.e. a priority rule order of priority rule #3 and priority rule #4, or a priority rule order of priority rule #2, priority rule #3 and priority rule #4 is applied. Since the collision occurred in the example of Figure 3 only relates to SRS resources (or SRS resources of SRS resource sets) triggered by a same DCI, priority rule #2 and priority rule #3, which relate to the priority of DCIs, are not applicable. So, according to the priority rule of the third embodiment, the priority of the triggered SRS resources that collide is determined based on priority rule #4. For priority rule #4, we assume priority rule #4, candidate #2 (i.e. the SRS resource configured with the smallest slot offset value has the highest priority) applies.

Accordingly, for the SRS resources from SRS resource set#1 that overlap with (i.e. collide with) the SRS resources from SRS resource set#2 in at least one same symbol between SRS resource set#1 and SRS resource set#2, since the SRS resources from SRS resource set#1 (with slot offset k =0) has a higher priority than the SRS resources from SRS resource set#2 (with slot offset k =1) based on priority rule #4, candidate #2, the SRS resources from SRS resource set#1 are transmitted in the “at least one same symbol between SRS resource set#1 and SRS resource set#2” , while the SRS resources from SRS resource set#2 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#1 and SRS resource set#2” ) .

For the SRS resources from SRS resource set#2 that overlap with (i.e. collide with) the SRS resources from SRS resource set#3 in at least one same symbol between SRS resource set#2 and SRS resource set#3, since the SRS resources from SRS resource set#2 (with slot offset k =1) has a higher priority than the SRS resources from SRS resource set#3 (with slot offset k =2) based on priority rule #4, candidate #2, the SRS resources from SRS resource set#2 are transmitted in the “at least one same symbol between SRS resource set#2 and SRS resource set#3” , while the SRS resources from SRS resource set#3 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#2 and SRS resource set#3” ) .

The following describes the first, second and third embodiments applying to the example illustrating that multiple SRS resources triggered by different DCIs (as well as multiple SRS resources triggered by a same DCI) collide on at least one same symbol in Figure 2.

We assume that SRS resource set#1, SRS resource set#2, SRS resource set#4 and SRS resource set#5 are for ‘beamManagement’ usage; and SRS resource set#3 is for ‘codebook’ usage.

It can be seen from Figure 2 that some SRS resources from SRS resource set#1 and some SRS resources from SRS resource set#2 are triggered to be transmitted in at least one same symbol (labelled as “at least one same symbol between SRS resource set#1 and SRS resource set#2” in Figure 2) , and some SRS resources form SRS resource set#3 and some SRS resources from SRS resource set#5 are triggered to be transmitted in at least one same symbol (labelled as “at least one same symbol between SRS resource set#3 and SRS resource set#5” in Figure 2) .

The determination of the highest (or higher) priority for the triggered SRS resources from SRS resource set#1 and the triggered SRS resources from SRS resource set#2, that are triggered by the same DCI (i.e. DCI 2) , has been described with reference to Figure 3. The following describes the determination of the highest (or higher) priority for the triggered SRS resources from SRS resource set#3 that are triggered by DCI 2 and the triggered SRS resources from SRS resource set#5 that are triggered by DCI 1 that collide.

If the first embodiment is adopted, the priority of the triggered SRS resources that collide will be first determined according to priority rule #1 (e.g. priority rule candidate #1: ‘beamManagement’ > ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ ) . For the SRS resources from SRS resource set#3 that overlap with (i.e. collide with) the SRS resources from SRS resource set#5 in at least one same symbol between SRS resource set#3 and SRS resource set#5, since the SRS resources from SRS resource set#5 (for ‘beamManagement’ usage) have a higher priority than the SRS resources from SRS resource set#3 (for ‘codebook’ usage) based on priority rule #1, priority rule candidate #1, the SRS resources from SRS resource set#5 are transmitted in the “at least one same symbol between SRS resource set#3 and SRS resource set#5” , while the SRS resources from SRS resource set#3 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#3 and SRS resource set#5” ) .

If the second embodiment is adopted, the priority of the collided SRS resources can be determined according to priority rule #6 (e.g. priority rule #6, candidate #2: the SRS resource that is associated with the smallest SRS resource set ID is determined as having the highest priority) . For the SRS resources from SRS resource set#3 that overlap with (i.e. collide with) the SRS resources from SRS resource set#5 in at least one same symbol between SRS resource set#3 and SRS resource set#5, since the SRS resources from SRS resource set#3 (associated with SRS resource set ID = 3) have a higher priority than the SRS resources from SRS resource set#5 (associated with SRS resource set ID = 5) based on priority rule #6, candidate #2, the SRS resources from SRS resource set#3 are transmitted in the “at least one same symbol between SRS resource set#3 and SRS resource set#5” , while the SRS resources from SRS resource set#5 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#3 and SRS resource set#5” ) .

If the third embodiment is adopted, the priority of the collided SRS resources is first determined according to priority rule #3 (e.g. priority rule #3, candidate #1: the SRS resource (s) triggered by the latest DCI have the highest priority) . For the SRS resources from SRS resource set#3 that overlap with (i.e. collide with) the SRS resources from SRS resource set#5 in at least one same symbol between SRS resource set#3 and SRS resource set#5) , since the SRS resources from SRS resource set#3 (triggered by DCI#2 in symbol n) have a higher priority than the SRS resources from SRS resource set#5 (triggered by DCI#1 in symbol n-2) based on priority rule #3, candidate #1, the SRS resources from SRS resource set#3 are transmitted in the “at least one same symbol between SRS resource set#3 and SRS resource set#5” , while the SRS resources from SRS resource set#5 are dropped (i.e. not transmitted in the “at least one same symbol between SRS resource set#3 and SRS resource set#5” ) .

Figure 4 is a schematic flow chart diagram illustrating an embodiment of a method 400 according to the present application. In some embodiments, the method 400 is performed by an apparatus, such as a remote unit (UE) . In certain embodiments, the method 400 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 400 may include 402 receiving one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; 404 determining which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and 406 transmitting, in the at least one same symbol, the SRS resource determined to have the highest priority.

In one embodiment, priority rule #1 may be determined as one of the priority rule candidates including priority rule candidate #1: ‘beamManagement’ > ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ ; priority rule candidate #2: ‘antennaSwitching’ > ‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ ; priority rule candidate #3: ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ > ‘antennaSwitching’ ; priority rule candidate #4: ‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ ; priority rule candidate #5: ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ ; and priority rule candidate #6: ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ > ‘beamManagement’ . Priority rule #2 may be determined as one of the candidates including priority rule #2, candidate #1: the SRS resources triggered by a DCI containing t value field have a higher priority than the SRS resources triggered by a DCI that does not contain t value field; and priority rule #2, candidate #2: the SRS resources triggered by the DCI that does not contain t value field have a higher priority than the SRS resources triggered by the DCI containing t value field. Priority rule #3 may be determined as one of the candidates including priority rule #3, candidate #1: the SRS resource (s) triggered by the latest DCI have the highest priority; and priority rule #3, candidate #2: the SRS resource (s) triggered by the earliest DCI have the highest priority. Priority rule #4 is determined as one of the candidates including priority rule #4, candidate #1: the SRS resource configured with the largest slot offset value has the highest priority; and priority rule #4, candidate #2: the SRS resource configured with the smallest slot offset value has the highest priority. Priority rule #5 may be determined as one of the candidates including priority rule #5, candidate #1: the SRS resource that has the largest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority; and priority rule #5, candidate #2: the SRS resource that has the smallest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority. Priority rule #6 may be determined as one of the candidates including priority rule #6, candidate #1: the SRS resource that is associated with the largest SRS resource set ID is determined as having the highest priority; and priority rule #6, candidate #2: the SRS resource that is associated with the smallest SRS resource set ID is determined as having the highest priority.

Figure 5 is a schematic flow chart diagram illustrating a further embodiment of a method 500 according to the present application. In some embodiments, the method 500 is performed by an apparatus, such as a base unit. In certain embodiments, the method 500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 500 may include 502 transmitting one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; 504 determining which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and 506 receiving, in the at least one same symbol, the SRS resource determined to have the highest priority.

Referring to Figure 6, the UE (i.e. the remote unit) includes a processor, a memory, and a transceiver. The processor implements a function, a process, and/or a method which are proposed in Figure 4.

The UE comprises a receiver that receives one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; a processor that determines which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and a transmitter that transmits, in the at least one same symbol, the SRS resource determined to have the highest priority.

Referring to Figure 6, the gNB (i.e. base unit) includes a processor, a memory, and a transceiver. The processors implement a function, a process, and/or a method which are proposed in Figure 5.

The base unit comprises a transmitter that transmits one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol; a processor that determines which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including priority rule #1: based on the usage of each of the triggered SRS resources that collide, priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide, priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide, priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide, priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and a receiver that receives, in the at least one same symbol, the SRS resource determined to have the highest priority.

Layers of a radio interface protocol may be implemented by the processors. The memories are connected with the processors to store various pieces of information for driving the processors. The transceivers are connected with the processors to transmit and/or receive a radio signal. Needless to say, the transceiver may be implemented as a transmitter to transmit the radio signal and a receiver to receive the radio signal.

The memories may be positioned inside or outside the processors and connected with the processors by various well-known means.

In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.

The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , processors, controllers, micro-controllers, microprocessors, and the like.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects to be only illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

A method of an UE, comprising:

receiving one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol;

determining which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including

priority rule #1: based on the usage of each of the triggered SRS resources that collide,

priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide,

priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide,

priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide,

priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and

priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and

transmitting, in the at least one same symbol, the SRS resource determined to have the highest priority.
The method of claim 1, wherein, priority rule #1 is determined as one of the priority rule candidates including

priority rule candidate #1: ‘beamManagement’ > ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ ;

priority rule candidate #2: ‘antennaSwitching’ > ‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ ;

priority rule candidate #3: ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ > ‘antennaSwitching’ ;

priority rule candidate #4: ‘beamManagement’ > ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ ;

priority rule candidate #5: ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ > ‘beamManagement’ ; and

priority rule candidate #6: ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ > ‘beamManagement’ .
The method of claim 1, wherein, priority rule #2 is determined as one of the candidates including

priority rule #2, candidate #1: the SRS resources triggered by a DCI containing t value field have a higher priority than the SRS resources triggered by a DCI that does not contain t value field; and

priority rule #2, candidate #2: the SRS resources triggered by the DCI that does not contain t value field have a higher priority than the SRS resources triggered by the DCI containing t value field.
The method of claim 1, wherein, priority rule #3 is determined as one of the candidates including

priority rule #3, candidate #1: the SRS resource (s) triggered by the latest DCI have the highest priority; and

priority rule #3, candidate #2: the SRS resource (s) triggered by the earliest DCI have the highest priority.
The method of claim 1, wherein, priority rule #4 is determined as one of the candidates including

priority rule #4, candidate #1: the SRS resource configured with the largest slot offset value has the highest priority; and

priority rule #4, candidate #2: the SRS resource configured with the smallest slot offset value has the highest priority.
The method of claim 1, wherein, priority rule #5 is determined as one of the candidates including

priority rule #5, candidate #1: the SRS resource that has the largest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority; and

priority rule #5, candidate #2: the SRS resource that has the smallest SRS resource ID among the triggered SRS resources that collide is determined as having the highest priority.
The method of claim 1, wherein, priority rule #6 is determined as one of the candidates including

priority rule #6, candidate #1: the SRS resource that is associated with the largest SRS resource set ID is determined as having the highest priority; and

priority rule #6, candidate #2: the SRS resource that is associated with the smallest SRS resource set ID is determined as having the highest priority.
The method of claim 1, wherein, the determining which SRS resource has the highest priority is according to a first priority rule order of priority rule #1, priority rule #2, priority rule #3 and priority rule #4, or a second priority rule order of priority rule #1, priority rule #3 and priority rule #4.
The method of claim 1, wherein, the determining which SRS resource has the highest priority is according to priority rule #5 or priority rule #6.
The method of claim 1, wherein, the determining which SRS resource has the highest priority is according to a third priority rule order of priority rule #3 and priority rule #4, or a fourth priority rule order of priority rule #2, priority rule #3 and priority rule #4.
An UE, comprising:

a receiver that receives one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol;

a processor that determines which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including

priority rule #1: based on the usage of each of the triggered SRS resources that collide,

priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide,

priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide,

priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide,

priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and

priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; anda transmitter that transmits, in the at least one same symbol, the SRS resource determined to have the highest priority.
A method at an base unit, comprising:

transmitting one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol;

determining which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including

priority rule #1: based on the usage of each of the triggered SRS resources that collide,

priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide,

priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide,

priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide,

priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and

priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and

receiving, in the at least one same symbol, the SRS resource determined to have the highest priority.
A base unit, comprising:

a transmitter that transmits one or multiple DCIs triggering multiple SRS resources to be transmitted in at least one same symbol;

a processor that determines which SRS resource among the multiple triggered SRS resources that collide in the at least one same symbol has the highest priority according to at least one of the priority rules including

priority rule #1: based on the usage of each of the triggered SRS resources that collide,

priority rule #2: based on a version of the DCI triggering each of the triggered SRS resources that collide,

priority rule #3: based on the triggering time of the DCI triggering each of the triggered SRS resources that collide,

priority rule #4: based on the slot offset configured to each of the triggered SRS resources that collide,

priority rule #5: based on SRS resource ID of each of the triggered SRS resources that collide, and

priority rule #6: based on SRS resource set ID associated with each of the triggered SRS resources that collide; and

a receiver that receives, in the at least one same symbol, the SRS resource determined to have the highest priority.