WO2023050302A1 - Traitement de collision pour déclenchement de srs apériodique - Google Patents

Traitement de collision pour déclenchement de srs apériodique Download PDF

Info

Publication number
WO2023050302A1
WO2023050302A1 PCT/CN2021/122150 CN2021122150W WO2023050302A1 WO 2023050302 A1 WO2023050302 A1 WO 2023050302A1 CN 2021122150 W CN2021122150 W CN 2021122150W WO 2023050302 A1 WO2023050302 A1 WO 2023050302A1
Authority
WO
WIPO (PCT)
Prior art keywords
priority rule
priority
srs resource
srs
triggered
Prior art date
Application number
PCT/CN2021/122150
Other languages
English (en)
Inventor
Bingchao LIU
Lingling Xiao
Hongmei Liu
Haiming Wang
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2021/122150 priority Critical patent/WO2023050302A1/fr
Publication of WO2023050302A1 publication Critical patent/WO2023050302A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal

Definitions

  • 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.
  • New Radio NR
  • VLSI Very Large Scale Integration
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • EPROM or Flash Memory Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • LAN Local Area Network
  • WAN Wide Area Network
  • UE User Equipment
  • eNB Evolved Node B
  • gNB Next Generation Node B
  • Uplink UL
  • Downlink DL
  • CPU Central Processing Unit
  • GPU Graphics Processing Unit
  • FPGA Field Programmable Gate Array
  • OFDM Orthogonal Frequency Division Multiplexing
  • RRC Radio Resource Control
  • RX User Entity/Equipment
  • SRS Sounding Reference Signal
  • 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.
  • 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.
  • 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.
  • 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’ .
  • 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
  • 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) .
  • 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’
  • 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’ .
  • slot n-4, slot n, slot n+1 and slot n+6 are non-available slots
  • 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.
  • time location e.g. symbol (s)
  • time location e.g. symbol (s)
  • time location e.g. symbol (s)
  • time location e.g. symbol (s)
  • 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.
  • 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.
  • priority rules including priority
  • 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.
  • 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.
  • 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.
  • priority rules including
  • a remote unit 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
  • 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
  • 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.
  • Figure 6 is a schematic block diagram illustrating apparatuses according to one embodiment.
  • 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” .
  • code 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.
  • modules 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.
  • VLSI very-large-scale integration
  • 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.
  • 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.
  • 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.
  • the software portions are stored on one or more computer readable storage devices.
  • 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 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.
  • 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.
  • 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) .
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider
  • 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.
  • 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) .
  • 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) .
  • 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.
  • one or more SRS resource sets with usage beamManagement are configured.
  • the gNB acquires detailed CSI for the DL channel based on estimates of the UL channel
  • the usage of a SRS resource set can be set to ‘beamManagement’ , ‘codebook’ , ‘nonCodebook’ or ‘antennaSwitching’ .
  • all SRS resources in an SRS resource set have the same usage configured to the SRS resource set.
  • 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.
  • 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’ ;
  • Priority rule candidate #6 ‘codebook’ or ‘nonCodebook’ > ‘antennaSwitching’ > ‘beamManagement’ .
  • the usage appeared in front of “>” has a higher priority than the usage appeared behind “>” .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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) .
  • 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.
  • the SRS resources triggered by NR Release 15 or 16 version DCI i.e. a DCI that does not contain t value field
  • the SRS resources triggered by NR Release 17 version DCI i.e. a DCI containing t value field
  • NR Release 17 version DCI i.e. a DCI containing t value field
  • 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) .
  • 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.
  • the slot offset i.e. the value of k
  • 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.
  • 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.
  • 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) .
  • 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.
  • 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) .
  • 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.
  • 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) .
  • 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.
  • 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) .
  • 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) .
  • the priority rule #2 may not be used in determining which SRS resource among the triggered SRS resources that collide has the highest priority.
  • 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.
  • 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) .
  • 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) .
  • 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) .
  • 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) .
  • 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) .
  • 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) .
  • 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.
  • 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.
  • 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’ .
  • 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 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) .
  • priority rule order of priority rule #1, 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 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.
  • priority rule candidate #1 i.e. ‘beamManagement’ > ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’
  • 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.
  • 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
  • the SRS resources from SRS resource set#1 for ‘beamManagement’ usage
  • the SRS resources from SRS resource set#2 for ‘beamManagement’ usage
  • the SRS resources from SRS resource set#2 have the same priority 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#1 and SRS resource set#2”
  • 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
  • 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” ) .
  • priority rule #5 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.
  • the SRS resources from SRS resource set#2 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
  • 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”
  • 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” ) .
  • 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” ) .
  • priority rule #3 and priority rule #4 are 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.
  • 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
  • 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.
  • priority rule #1 e.g. priority rule candidate #1: ‘beamManagement’ > ‘antennaSwitching’ > ‘codebook’ or ‘nonCodebook’ ) .
  • SRS resource set#3 that overlap with (i.e.
  • the SRS resources from SRS resource set#5 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” ) .
  • 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) .
  • 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
  • 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) .
  • priority rule #3 e.g. priority rule #3, candidate #1: the SRS resource (s) triggered by the latest DCI have the highest priority
  • the SRS resources from SRS resource set#5 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.
  • the method 400 is performed by an apparatus, such as a remote unit (UE) .
  • 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.
  • 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.
  • 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.
  • Figure 5 is a schematic flow chart diagram illustrating a further embodiment of a method 500 according to the present application.
  • the method 500 is performed by an apparatus, such as a base unit.
  • 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.
  • 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.
  • 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.
  • Figure 6 is a schematic block diagram illustrating apparatuses according to one embodiment.
  • the UE i.e. the remote unit
  • the UE 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
  • 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.
  • 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.
  • the gNB i.e. base unit
  • the gNB 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention divulgue des procédés et des appareils destinés à traiter une collision pour un déclenchement de SRS apériodique. Un procédé au niveau d'un UE comprend la réception d'une ou de plusieurs ressources SRS à déclenchement DCI devant être transmises dans au moins un même symbole ; la détermination de quelle ressource SRS parmi les multiples ressources de SRS déclenchées qui entrent en collision dans ledit même symbole a la priorité la plus élevée selon au moins l'une des règles de priorité comprenant la règle de priorité #1 : sur la base de l'utilisation de chacune des ressources SRS déclenchées qui entrent en collision, règle de priorité #2 : sur la base d'une version des DCI déclenchant chacune des ressources SRS déclenchées qui entrent en collision, règle de priorité #3 : sur la base du temps de déclenchement des DCI déclenchant chacune des ressources SRS déclenchées qui entrent en collision, règle de priorité #4: sur la base du décalage d'intervalle configuré pour chacune des ressources SRS déclenchées qui entrent en collision, règle de priorité #5 : sur la base de l'ID de ressource SRS de chacune des ressources SRS déclenchées qui entrent en collision, et une règle de priorité #6 : sur la base d'un ID d'ensemble de ressources SRS associé à chacune des ressources SRS déclenchées qui entrent en collision ; et la transmission, dans ledit au moins un même symbole, de la ressource SRS déterminée comme ayant la priorité la plus élevée.
PCT/CN2021/122150 2021-09-30 2021-09-30 Traitement de collision pour déclenchement de srs apériodique WO2023050302A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/122150 WO2023050302A1 (fr) 2021-09-30 2021-09-30 Traitement de collision pour déclenchement de srs apériodique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/122150 WO2023050302A1 (fr) 2021-09-30 2021-09-30 Traitement de collision pour déclenchement de srs apériodique

Publications (1)

Publication Number Publication Date
WO2023050302A1 true WO2023050302A1 (fr) 2023-04-06

Family

ID=85780392

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/122150 WO2023050302A1 (fr) 2021-09-30 2021-09-30 Traitement de collision pour déclenchement de srs apériodique

Country Status (1)

Country Link
WO (1) WO2023050302A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391447A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 探测参考信号的传输方法、装置及系统
CN110474734A (zh) * 2018-05-11 2019-11-19 华为技术有限公司 通信方法及装置
CN110943813A (zh) * 2018-09-21 2020-03-31 中国移动通信有限公司研究院 一种SRS resource传输的方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391447A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 探测参考信号的传输方法、装置及系统
CN110474734A (zh) * 2018-05-11 2019-11-19 华为技术有限公司 通信方法及装置
CN110943813A (zh) * 2018-09-21 2020-03-31 中国移动通信有限公司研究院 一种SRS resource传输的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CMCC: "Discussion on remaining issues on SRS", 3GPP TSG RAN WG1 MEETING #94, R1-1808831, 11 August 2018 (2018-08-11), XP051516204 *

Similar Documents

Publication Publication Date Title
US20200170027A1 (en) Reporting information transmission method, user side device and network side device
WO2022073189A1 (fr) Activation simultanée d'états tci pour une liaison montante (ul) et une liaison descendante (dl)
CN114424610B (zh) 确定用于ul信号的默认空间关系
US20230370219A1 (en) Pusch transmission in multi-dci based multi-trp
US20230261719A1 (en) Default beam determination for uplink signal transmission
CN115336363A (zh) 默认波束确定
CN116326025A (zh) 用于dl和ul波束指示的联合tci状态
CN114365426B (zh) 用于相位跟踪参考信号的方法和装置
WO2023050302A1 (fr) Traitement de collision pour déclenchement de srs apériodique
US20240195573A1 (en) Mac ce for separate indication of dl tci and ul tci
US20230049134A1 (en) Aperiodic srs triggering and transmission
US20240314804A1 (en) Dynamic common beam switching for dl reception
CN115443706A (zh) 跨载波调度中的默认波束确定
WO2022032657A1 (fr) Déclenchement flexible d'un srs apériodique
WO2023137654A1 (fr) Transmission ul basée sur trp multiples à dci uniques dans une structure de tci unifiée
WO2024082571A1 (fr) Opération multi-trp avec structure tci unifiée avant l'indication des états tci par des dci
WO2022205258A1 (fr) Amélioration de la commande de puissance d'une transmission pusch avec répétition
WO2023206338A1 (fr) Commutation dynamique entre des schémas pusch reposant sur un mono-trp ou un trp multiple
WO2023283907A1 (fr) Détermination de faisceau par défaut et de signal de référence de perte de trajet par défaut
US20230403115A1 (en) Phase tracking reference signal for sfn based pdsch transmission
WO2023142115A1 (fr) Prise en charge d'une transmission ul à panneaux multiples
WO2023130247A1 (fr) Transmission ul basée sur plusieurs trp multi-dci dans une structure tci unifiée
WO2023206429A1 (fr) Signal de référence de suivi de phase pour transmission ul multi-panneau simultanée
WO2024026724A1 (fr) Prise en charge d'une transmission de srs avec 8 ports d'antenne
US20230254873A1 (en) Feedback Information Transmission Method, Terminal and Network Device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21958876

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05/07/2024)