Aperiodic SRS triggering and transmission

Abstract

Methods and apparatuses for associating aperiodic SRS triggering state with a SRS resource set or a SRS CC set are disclosed. One method includes transmitting an activation / deactivation MAC CE for indicating or updating the association between aperiodic SRS triggering state and a set of aperiodic SRS resources for carrying by a SRS request field value of a DCI format 0_1 or 1_1 or a DCI format 2_3 with a higher layer parameter srs-TPC-PDCCH-Group = typeB or a set of SRS CCs for carrying by a SRS request field value of a DCI format 2_3 with a higher layer parameter srs-TPC-PDCCH-Group = typeA.

Description

TECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to wireless communication and more particularly to methods and apparatus for aperiodic SRS triggering and transmission. BACKGROUND

[0002] The following abbreviations are defined herein, at least some of which are mentioned throughout the description: Third Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), Frequency Division Duplex (FDD), Frequency Division Multiple Access (FDMA), Long Term Evolution (LTE), 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), Personal Digital Assistant (PDA), User Equipment (UE), Uplink (UL), Evolved Node B (eNB), Next Generation Node B (gNB), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Dynamic RAM (DRAM), Synchronous Dynamic RAM (SDRAM), Static RAM (SRAM), Liquid Crystal Display (LCD), Light Emitting Diode (LED), Organic LED (OLED), Orthogonal Frequency Division Multiplexing (OFDM), Radio Resource Control (RRC), Time Division Duplex (TDD), Time Division Multiplexing (TDM), User Entity / Equipment (Mobile Terminal) (UE), Uplink (UL), Universal Mobile Telecommunication System (UMTS), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Downlink Control Information (DCI), Single-DCI (S-DCI), Transmission Reception Point (TRP), Multi-TRP (Multi-TRP or M-TRP), Frequency Range 2 (FR2), Quasi Co-Location (QCL), Channel State Information Reference Signal (CSI-RS), CSI-RS Resource Indicator (CRI), Code Division Multiplexing (CDM), Transmission Configuration Indication (TCI), Sounding Reference Signal (SRS), Control Resource Set (CORESET), Synchronization Signal (SS), Reference Signal (RS), Component Carrier (CC), Bandwidth Part (BWP).

[0003] In Release 16, up to 16 SRS resource sets can be configured for a UE in a BWP according to UE capability using “beam management”, “codebook”, “non-codebook”, and “antenna switching”. Aperiodic time-domain behavior can be utilized to transmit SRS for all used SRS resources. Aperiodic SRS for “beam management”, “codebook”, “non-codebook”, and “antenna switching” can be triggered by DCI formats 0_1 and 1_1 with non-zero “SRS request” field. Carrier switching based aperiodic SRS transmission can be triggered by DCI format 2_3 with non-zero “SRS request” field.

[0004] For aperiodic SRS triggered by DCI format 0_1 or 1_1 and DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group set to “Type B”, each value of “SRS request” field in DCI format 0_1 or 1_1 or 2_3 is associated with one or multiple SRS resource sets configured by RRC signaling. For carrier switching based aperiodic SRS transmission triggered by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group set to “Type A”, each value of “SRS request” field in DCI format 2_3 is associated with a set of CCs for SRS transmission by RRC signaling. Therefore, the association between aperiodic SRS triggering state (i.e. SRS request field value) and SRS resource set or the association between aperiodic SRS triggering state (i.e. SRS request field value) and SRS CC set can only be updated by RRC signaling, which has large latency and is inefficient.

[0005] In addition, for aperiodic SRS transmission for carrier switching, if higher layer parameter srs-TPC-PDCCH-Group = typeA, each aperiodic SRS triggering state can trigger multiple SRS transmissions on multiple CCs configured by higher layer parameter SRS-CC-Set. Up to 4 SRS CC sets can be configured for one UE by RRC. In DCI format 2_3, the first SRS CC set is associated with SRS request field value = ‘01’, the second SRS CC set is associated with SRS request field value = ‘10’, and the third SRS CC set is associated with SRS request field value = ‘11’. It can be seen that it is unknown which SRS request field value the fourth SRS CC set is associated with.

[0006] An object of the present disclosure is to update the association between SRS request field value and triggered SRS transmission in a new way with lower latency. SUMMARY

[0007] Methods and apparatuses for associating aperiodic SRS trigger states with SRS resource sets or SRS CC sets are disclosed.

[0008] In one embodiment, a method includes transmitting an activation / deactivation MAC CE for indicating or updating an association between aperiodic SRS trigger states and aperiodic SRS resource sets or SRS CC sets for carrying by SRS request field values carried by DCI format 0_1 or 1_1 or DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB or by SRS request field values carried by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA.

[0009] In one embodiment, the activation / deactivation MAC CE is a aperiodic SRS resource set activation / deactivation MAC CE for indicating or updating an association between aperiodic SRS trigger states and aperiodic SRS resource sets for carrying by SRS request field values carried by DCI format 0_1 or 1_1 or DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB. One or more aperiodic SRS trigger states and associated aperiodic SRS resource sets are indicated in the aperiodic SRS resource set activation / deactivation MAC CE. In one solution, one or more aperiodic SRS trigger state ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS trigger state or states the aperiodic SRS resource set activation / deactivation MAC CE applies to, and the activation status of all configured aperiodic SRS resource sets for each aperiodic SRS trigger state is indicated by a bitmap. In another solution, one or more aperiodic SRS resource set ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS resource set or sets the aperiodic SRS resource set activation / deactivation MAC CE applies to, and the associated aperiodic SRS trigger state for each SRS resource set is indicated by a 3-bit bitmap, and each bit of the 3-bit bitmap indicates the activation status of each associated aperiodic SRS trigger state of the aperiodic SRS resource set indicated by the SRS resource set ID field.

[0010] In another embodiment, the activation / deactivation MAC CE is a SRS CC set activation / deactivation MAC CE for indicating or updating the association between aperiodic SRS trigger states and SRS CC sets for SRS request field values carried by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA. A UE can be configured with more than four SRS CC sets according to UE capability. In one solution, one or more SRS CC set ID fields are included in the SRS CC set activation / deactivation MAC CE to indicate the activated SRS CC set for each aperiodic SRS trigger state. In another solution, the activation status of all configured SRS CC sets for each aperiodic SRS trigger state is listed as a bitmap and one or more SRS CC sets are activated for one aperiodic SRS trigger state.

[0011] In some embodiments, the aperiodic SRS resource set activation / deactivation MAC CE is associated with a higher layer parameter CORESETPoolIndex configured for a CORESET.

[0012] In some embodiments, the SRS CC set activation / deactivation MAC CE is associated with a higher layer parameter CORESETPoolIndex configured for a CORESET.

[0013] In one embodiment, a method comprises receiving an activation / deactivation MAC CE for indicating or updating the association between aperiodic SRS trigger states and aperiodic SRS resource sets for SRS request field values carried by DCI format 0_1 or 1_1 or DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB or SRS CC sets for SRS request field values carried by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA.

[0014] In another embodiment, a remote unit comprises a receiver configured to receive an activation / deactivation MAC CE for indicating or updating the association between aperiodic SRS trigger states and aperiodic SRS resource sets for SRS request field values carried by DCI format 0_1 or 1_1 or DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB or SRS CC sets for SRS request field values carried by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA.

[0015] In yet another embodiment, a base station unit includes a transmitter configured to transmit an activation / deactivation MAC CE for indicating or updating an association between an aperiodic SRS triggering state and an aperiodic SRS resource set for an SRS request field value carried by DCI format 0_1 ​​or 1_1 or DCI format 2_3 with a higher layer parameter srs-TPC-PDCCH-Group=typeB, or an SRS CC set for an SRS request field value carried by DCI format 2_3 with a higher layer parameter srs-TPC-PDCCH-Group=typeA. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1 FIG. 4 illustrates an aperiodic SRS resource set activation / deactivation MAC CE according to the first embodiment;

[0018] Figure 2 FIG. 4 illustrates an aperiodic SRS resource set activation / deactivation MAC CE according to the second embodiment;

[0019] Figure 3-1 and Figure 3-2 FIG. 4 illustrates an aperiodic SRS resource set activation / deactivation MAC CE according to the third embodiment;

[0020] Figure 4 FIG. 4 illustrates an aperiodic SRS resource set activation / deactivation MAC CE according to a fourth embodiment;

[0021] Figure 5-1 and Figure 5-2 FIG. 4 illustrates an SRS CC set activation / deactivation MAC CE according to a fifth embodiment;

[0022] Figure 6 FIG. 4 illustrates an aperiodic SRS resource set activation / deactivation MAC CE according to a sixth embodiment;

[0023] Figure 7 illustrates an example of an SRS CC set activation / deactivation MAC CE according to the seventh embodiment;

[0024] Figure 8 FIG. 1 illustrates an example of an aperiodic SRS resource set activation / deactivation MAC CE according to the seventh embodiment;

[0025] Figure 9 is a schematic flow chart illustrating an embodiment of a method;

[0026] Figure 10 is a schematic flow chart illustrating a further embodiment of a method; and

[0027] Figure 11 is a schematic block diagram illustrating an apparatus according to an embodiment. DETAILED DESCRIPTION

[0028] As will be appreciated by those skilled in the art, certain aspects of embodiments can be embodied as a system, apparatus, method or program product. Accordingly, embodiments can 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 can all generally be referred to herein as a "circuit," "module" or "system." Furthermore, embodiments can 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, hereinafter "code". The storage devices can be tangible and / or non-transitory. The storage devices can not embody signals. In a certain embodiment, the storage devices take the form of signals solely for the purpose of accessing code.

[0029] Certain of the functional units described in this specification can be labeled as "modules," in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays

[0030] Modules can 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 can include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0031] Indeed, a module of code can be a single instruction, or many instructions, and can even be distributed over several different code segments, in several different programs, and across several memory devices. Similarly, operational data can be identified and illustrated herein within modules, and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set, or can 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 in one or more computer readable storage devices.

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

[0033] 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, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a 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 can 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.

[0034] Code for carrying out operations for embodiments can 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, conventional procedural programming languages, such as the "C" programming language, assembly language, machine language of a computer, or any combination of the foregoing. The code can execute 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 latter scenario, the remote computer can 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 can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0035] References throughout the specification to "one embodiment," "an embodiment," or similar language mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Thus, unless expressly specified otherwise, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout the specification may, but do not necessarily, all refer to the same embodiment, but rather to "one or more but not all embodiments." Unless expressly specified otherwise, the terms "comprise," "comprising," "having," and variations thereof mean "including but not limited to." Unless expressly specified otherwise, an enumerated listing of items does not imply that any or all of the items are mutually exclusive. Unless expressly specified otherwise, the terms "a," "an," and "the" also mean "one or more."

[0036] In addition, the features, structures or characteristics described in the various embodiments can be combined in any suitable manner. In the following description, many 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 the embodiments. However, those skilled in the relevant art will recognize that the embodiments can be practiced without one or more of the specific details or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid confusing various aspects of the embodiments.

[0037] Aspects of various embodiments are described below with reference to schematic flow charts 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 flow charts and / or schematic block diagrams, as well as combinations of blocks in the schematic flow charts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to generate a machine, such that instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions specified for the block or blocks in the schematic flow charts and / or schematic block diagrams.

[0038] The code may also be stored in a storage device that is capable of directing a computer, other programmable data processing apparatus, or other device to function in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions for implementing the functions specified in a block or blocks of the schematic flowchart and / or schematic block diagram.

[0039] The code can 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 which execute on the computer or other programmable apparatus provide processes for implementing the functions specified in the flowchart and / or block diagram block or blocks.

[0040] The illustrative flowcharts and / or the illustrative block diagrams in the various 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 illustrative flowcharts and / or the illustrative block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).

[0041] It also should be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in some alternative implementations, be executed substantially concurrently, or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods can be conceived that are equivalent in function, logic, or effect to those illustrated, with the scope of the present disclosure intended to include such equivalent steps, methods, and functions.

[0042] Although various arrow types and line types can be employed in the flowchart and / or block diagrams, these are understood to be the arrows or connectors of the flowchart represent the logical flow of the depicted embodiments. For example, an arrow can 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 illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by special-purpose hardware-based systems that perform the specified functions or acts, or combinations of special-purpose hardware and code.

[0043] The description of elements in the figures can refer to elements of a preceding figure. Like reference numbers in all figures refer to like elements, including alternate embodiments of like elements.

[0044] In NR Rel-17, more than one SRS resource set can be configured for a UE in a BWP for multi-panel based UL transmission using “codebook” and / or “non-codebook”. More than two SRS resource sets can be configured for a UE in a BWP for antenna switching with up to 8 Rx antenna ports. The maximum number of configured SRS resource sets for a UE in a BWP is 16 in NR Rel-16 according to UE capability. Considering multi-DCI based multi-TRP UL transmission and potential use cases for SRS for antenna switching with up to 8 Rx antenna ports, more than 16 SRS resource sets can be configured for a UE in a BWP according to UE capability.

[0045] Each aperiodic SRS resource set can be associated with one aperiodic SRS trigger state by the higher layer parameter aperiodicSRS-ResourceTrigger or multiple aperiodic SRS trigger states by the higher layer parameter aperiodicSRS-ResourceTriggerList.

[0046] According to the present application, the aperiodic SRS resource set activation / deactivation MAC CE is used to indicate or update the association between an aperiodic SRS trigger state and the SRS resource set for aperiodic SRS triggered by a non-zero SRS request field value carried by DCI format 0_1 or 1_1 or DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB, and the SRS CC set activation / deactivation MAC CE is used to indicate or update the association between an aperiodic SRS trigger state and the SRS CC set for aperiodic SRS triggered by a non-zero SRS request field value carried by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA.

[0047] According to the first embodiment, for aperiodic SRS triggered by DCI format 0_1 or 1_1 or by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB, the gNB can send the aperiodic SRS resource set activation / deactivation MAC CE with the format provided in Table 1. Figure 1 One or multiple SRS resource sets can be activated or deactivated (i.e. associated or disassociated with one aperiodic SRS trigger state) for one aperiodic SRS trigger state indicated in the MAC CE on a BWP.

[0048] The aperiodic SRS resource set activation / deactivation MAC CE according to the first embodiment is identified by a MAC subheader with a dedicated LCID. As shown in Table 2, the aperiodic SRS resource set activation / deactivation MAC CE according to the first embodiment has the following fields: Figure 1

[0049] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0050] BWP ID: This field indicates the DL BWP to which the MAC CE applies as a codepoint of the DCI or UL bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0051] ​aperiodicSRS-ResourceTrigger ID: This field indicates aperiodic SRS resource trigger state to which the MAC CE applies. The length of the aperiodicSRS-ResourceTrigger ID field is 2 bits when one of three aperiodic SRS resource trigger states is triggered.

[0052] S i : If one or more aperiodic SRS resource sets are configured for the UE in the indicated BWP, this field indicates the activation or deactivation (i.e., association or disassociation) status of the aperiodic SRS resource set with SRS-ResourceSetId i. S i The field is set to 1 to indicate that the SRS resource set with SRS-ResourceSetId i shall be activated, i.e., associated with the SRS request field value indicated by the aperiodicSRS-ResourceTrigger ID field. S i The field is set to 0 to indicate that the SRS resource set with SRS-ResourceSetId i shall be deactivated, i.e., disassociated from the SRS request field value indicated by the aperiodicSRS-ResourceTrigger ID field. One or more SRS resource sets can be activated or deactivated (i.e., associated or disassociated from one aperiodic SRS resource trigger state) for one aperiodic SRS resource trigger state.

[0053] R: Reserved bit, set to 0.

[0054] According to the first embodiment, the SRS request field value indicated by the aperiodicSRS-ResourceTrigger ID is associated with each of the SRS resource sets represented by the S i field set to 1, and disassociated from each of the SRS resource sets represented by the S i field set to 0.

[0055] For example, assume that 16 SRS resource sets are configured for the UE in the BWP (indicated by the BWP ID), S0 to S 15 represent the 16 SRS resource sets, respectively. If S n is set to 1 (n is any one of 0 to 15), the (n+1)th SRS resource set represented by S n is associated with the SRS request field value indicated by the aperiodicSRS-ResourceTrigger ID. On the other hand, if S n is set to 0 (n is any one of 0 to 15), the (n+1)th SRS resource set represented by Sn The (n+1)th SRS resource set indicated by is disassociated with the SRS request field value indicated by aperiodicSRS-ResourceTrigger ID.

[0056] The length of the aperiodic SRS resource set activation / deactivation MAC CE according to the first embodiment depends on the number of SRS resource sets configured for the UE in the BWP. When the number of SRS resource sets configured for the UE in the BWP is 16, the length of the aperiodic SRS resource set activation / deactivation MAC CE is 32 bits (i.e. 4 octets). When the number of SRS resource sets configured for the UE in the BWP is 8X (X is a positive integer), the length of the aperiodic SRS resource set activation / deactivation MAC CE is X+2 octets (N equals X+1 as indicated in Table 1). Figure 1

[0057] According to the second embodiment, for aperiodic SRS triggered by DCI format 0_1 or 1_1 or DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB, the gNB can send the aperiodic SRS resource set activation / deactivation MAC CE with the format provided in Table 2. One SRS resource set can be associated with one or more (up to 3) aperiodic SRS resource trigger states. Figure 2

[0058] The aperiodic SRS resource set activation / deactivation MAC CE according to the second embodiment is identified by a MAC subheader with a dedicated LCID. As shown in Table 3, the aperiodic SRS resource set activation / deactivation MAC CE according to the second embodiment has the following fields: Figure 2

[0059] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0060] BWP ID: This field indicates the DL BWP to which the MAC CE applies as the codepoint of the DCI or UL bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0061] SRS Resource Set ID: If one or more aperiodic SRS resource sets are configured for the UE in the BWP, this field indicates one aperiodic SRS resource set to which the MAC CE applies. The length of this field can be 5 bits in case up to 32 SRS resource sets can be configured for the UE in the BWP or 4 bits in case up to 16 SRS resource sets can be configured for the UE in the BWP.​​​

[0062] Ti: This field indicates the activation or deactivation status of the (i+1)th aperiodic SRS trigger state associated with the SRS resource set indicated by the SRS resource set ID field.

[0063] R: Reserved bit, set to 0.

[0064] According to the second embodiment, the SRS resource set indicated by the SRS resource set ID field is associated or disassociated with the (i+1)th aperiodic SRS resource trigger state represented by Ti (i = 0, 1, 2). Ti (i = 0, 1, 2) is set to 1, which means associated, or set to 0, which means disassociated.

[0065] For example, if TO, T1 and T2 are set to 1, 0 and 1, the SRS resource set indicated by the SRS resource set ID field is associated with the first and third aperiodic SRS resource trigger states and disassociated with the second aperiodic SRS resource trigger state.

[0066] The length of the aperiodic SRS resource set activation / deactivation MAC CE according to the second embodiment is fixed to 16 bits (i.e., 2 octets).

[0067] The first embodiment involves associating or disassociating a single aperiodic SRS trigger state with all configured aperiodic SRS resource sets by using one aperiodic SRS resource set activation / deactivation MAC CE according to the first embodiment.

[0068] According to the third embodiment, two or all three aperiodic SRS trigger states are associated or disassociated with all configured aperiodic SRS resource sets by using one aperiodic SRS resource set activation / deactivation MAC CE according to the third embodiment.

[0069] According to the third embodiment, for aperiodic SRS triggered by DCI format 0_1 or 1_1 or by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB, the gNB can send the aperiodic SRS resource set activation / deactivation MAC CE with the format provided in Figure 3-1 or Figure 3-2 .

[0070] One or more aperiodic SRS resource sets can be associated or disassociated with two aperiodic SRS trigger states on a BWP based on the aperiodic SRS resource set activation / deactivation MAC CE shown in Figure 3-1 .

[0071] Figure 3-1 The aperiodic SRS resource set activation / deactivation MAC CE shown in FIGURE 20 is identified by a MAC subheader with a dedicated LCID. As shown in FIGURE 20, the aperiodic SRS resource set activation / deactivation MAC CE has the following fields: Figure 3-1

[0072] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0073] BWP ID: This field indicates the DL BWP to which the MAC CE applies as a codepoint of the DCI or UL bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0074] aperiodicSRS-ResourceTrigger ID1 and aperiodicSRS-ResourceTrigger ID2: This field indicates two aperiodic SRS resource trigger states to which the MAC CE applies. The length of each of aperiodicSRS-ResourceTrigger ID1 and aperiodicSRS-ResourceTrigger ID2 is 2 bits when one of the three aperiodic SRS resource trigger states is triggered.

[0075] S1 i and S2 i : If one or more aperiodic SRS resource sets are configured for the UE in the indicated BWP, S1 i indicates the activation or deactivation status of the SRS resource set with SRS-ResourceSetId i associated with the SRS request field value indicated by aperiodicSRS-ResourceTrigger ID1; and S2 i indicates the activation or deactivation status of the SRS resource set with SRS-ResourceSetId i associated with the SRS request field value indicated by aperiodicSRS-ResourceTrigger ID2. S1 i (or S2 i ) is set to 1 to indicate that the aperiodic SRS resource set with SRS-ResourceSetId i shall be associated with the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID1 (or aperiodicSRS-ResourceTrigger ID2). S1 i (or S2 i is set to 0 to indicate that the aperiodic SRS resource set with SRS-ResourceSetId i shall not be associated with the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID1 (or aperiodicSRS-ResourceTrigger ID2).) is set to 0 to indicate that the aperiodic SRS resource set with SRS-ResourceSetId i shall be disassociated from the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID1 (or aperiodicSRS-ResourceTrigger ID2).

[0076] R: Reserved bit, set to 0.

[0077] According to Figure 3-1 the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID1 is associated with the (i+1)th SRS resource set indicated by S1 i field, and disassociated from the (i+1)th SRS resource set indicated by S1 i field. Similarly, the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID2 is associated with the (i+1)th SRS resource set indicated by S2 i field, and disassociated from the (i+1)th SRS resource set indicated by S2 i field.

[0078] For example, assume that 16 SRS resource sets, S10 to S1 15 , respectively, are configured for a UE in a BWP (indicated by BWP ID). If S1 i is set to 1 (i is any one of 0 to 15), the (i+1)th SRS resource set indicated by S1 i is associated with the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID1. If S1 i is set to 0 (i is any one of 0 to 15), the (i+1)th SRS resource set indicated by S1 i is disassociated from the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID1. Similarly, S20 to S2 15 , respectively, are configured for a UE in a BWP (indicated by BWP ID). If S2 i is set to 1 (i is any one of 0 to 15), the (i+1)th SRS resource set indicated by S2 iThe (i+1)th SRS resource set indicated by is associated with the aperiodic SRS resource trigger state indicated by aperiodicSRS-ResourceTrigger ID2. i is set to 0 (i is any one from 0 to 15), then S2 i The (i+1)th SRS resource set represented by is disassociated from the aperiodic SRS resource triggering state indicated by aperiodicSRS-ResourceTrigger ID2.

[0079] Figure 3-1 The length of the aperiodic SRS resource set activation / deactivation MAC CE shown in depends on the number of SRS resource sets configured for the UE in the BWP. When the number of SRS resource sets configured for the UE in the BWP is 16, Figure 3-1 The length of the aperiodic SRS resource set activation / deactivation MAC CE shown in is 48 bits (i.e., 6 octets). When the number of SRS resource sets configured for the UE in the BWP is 8X (X is a positive integer), Figure 3-1 The length of the aperiodic SRS resource set activation / deactivation MAC CE shown in is 2X+2 octets ( Figure 3-1 The N indicated in is equal to X+1).

[0080] One or more aperiodic SRS resource sets can be based on Figure 3-2 The aperiodic SRS resource set activation / deactivation MAC CE shown in FIG is associated or deassociated with all three aperiodic SRS triggering states on the BWP.

[0081] Figure 3-2 The aperiodic SRS resource set activation / deactivation MAC CE shown in is identified by a MAC subheader with a dedicated LCID. Figure 3-2 As shown, the aperiodic SRS resource set activation / deactivation MAC CE has the following fields:

[0082] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0083] BWP ID: This field indicates the DL BWP to which the MAC CE applies as the codepoint of the DCI or UL Bandwidth Part Indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0084] SN i: If the UE is configured with one or more aperiodic SRS resource sets in the indicated BWP, this field indicates the activation or deactivation status of the aperiodic SRS resource set with SRS-ResourceSetld i associated with the SRS request field value N. i This field is set to 1 to indicate that the aperiodic SRS resource set with SRS-ResourceSetld i shall be associated with the Nth aperiodic SRS resource trigger state. i This field is set to 0 to indicate that the aperiodic SRS resource set with SRS-ResourceSetld i shall be disassociated from the Nth aperiodic SRS resource trigger state.

[0085] R: Reserved bit, set to 0.

[0086] According to the aperiodic SRS resource set activation / deactivation MAC CE shown in Figure 3-2 , the Nth aperiodic SRS resource trigger state is associated with each of the aperiodic SRS resource sets represented by the SN i field set to 1 and disassociated from each of the aperiodic SRS resource sets represented by the SN i field set to 0.

[0087] Since each SRS resource set is indicated three times (S1 i , S2 i and S3 i ) for all three aperiodic SRS resource trigger states, it is not necessary to include any aperiodicSRS-ResourceTrigger ID fields in the aperiodic SRS resource set activation / deactivation MAC CE shown in Figure 3-2 .

[0088] For example, assume that the UE is configured with 16 SRS resource sets in a BWP (indicated by a BWP ID), then SN0 to SN 15 represent the 16 SRS resource sets (N = 1, 2 and 3), respectively. If SN i is set to 1 (N = 1, 2 or 3; i is any one of 0 to 15), then the (i+1)th SRS resource set represented by SN i is associated with the Nth aperiodic SRS resource trigger state. On the other hand, if SN i is set to 0 (N = 1, 2 or 3; i is any one of 0 to 15), then the (i+1)th SRS resource set represented by SN i is disassociated from the Nth aperiodic SRS resource trigger state.

[0089] The length of the aperiodic SRS resource set activation / deactivation MAC CE according to the third embodiment depends on the number of SRS resource sets configured for the UE in the BWP. When the number of SRS resource sets configured for the UE in the BWP is 16, the length of the aperiodic SRS resource set activation / deactivation MAC CE according to the third embodiment is 56 bits (i.e., 7 octets). When the number of SRS resource sets configured for the UE in the BWP is 8X (X is a positive integer), the length of the aperiodic SRS resource set activation / deactivation MAC CE according to the third embodiment is 3X+1 octets ( Figure 3-2 The N indicated in is equal to X+1).

[0090] The second embodiment relates to associating or disassociating one SRS resource set with three aperiodic SRS resource triggering states by using one aperiodic SRS resource set activation / deactivation MAC CE according to the second embodiment.

[0091] According to the fourth embodiment, all configured SRS resource sets are associated or disassociated with three aperiodic SRS resource triggering states by using one aperiodic SRS resource set activation / deactivation MAC CE according to the fourth embodiment.

[0092] According to the fourth embodiment, for aperiodic SRS triggered by DCI format 0_1 ​​or 1_1 or by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group=typeB, the gNB can utilize Figure 4 The aperiodic SRS resource set activation / deactivation MAC CE is sent in the format provided in . All configured aperiodic SRS resource sets can be associated with one or more (up to 3) aperiodic SRS resource triggering states.

[0093] The aperiodic SRS resource set activation / deactivation MAC CE according to the fourth embodiment is identified by a MAC subheader with a dedicated LCID. Figure 4 As shown, the aperiodic SRS resource set activation / deactivation MAC CE according to the fourth embodiment has the following fields:

[0094] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0095] BWP ID: This field indicates the DL BWP to which the MAC CE applies as the codepoint of the DCI or UL Bandwidth Part Indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0096] SRS resource set IDN If one or more (up to N, N is a positive integer) aperiodic SRS resource sets are configured for the UE in the BWP, this field indicates the Nth SRS resource set to which the MAC CE applies.

[0097] TN i This field indicates the activation or deactivation status of the (i+1)th aperiodic SRS trigger state associated with the SRS resource set indicated by the SRS resource set ID N field. The (i+1)th aperiodic SRS trigger state is associated with the SRS resource set indicated by the SRS resource set ID

[0098] R: Reserved bit, set to 0.

[0099] According to the fourth embodiment, the SRS resource set indicated by the SRS resource set ID N field is associated with or disassociated from the (i+1)th aperiodic SRS trigger state indicated by the TN i (i=0, 1, 2) bit. The TN i (i=0, 1, 2) bit is set to 1, which means association, or set to 0, which means disassociation.

[0100] For example, if T10, T11 and T12 are set to 1, 0, 1, the aperiodic SRS resource set indicated by the SRS resource set ID 1 field is associated with the first and third aperiodic SRS trigger states and disassociated from the second aperiodic SRS trigger state.

[0101] The length of the aperiodic SRS resource set activation / deactivation MAC CE according to the fourth embodiment depends on the number of SRS resource sets configured for the UE in the BWP. When the number of SRS resource sets configured for the UE in the BWP is 16, the length of the aperiodic SRS resource set activation / deactivation MAC CE according to the fourth embodiment is 136 bits (i.e. 17 octets). When the number of SRS resource sets configured for the UE in the BWP is X (X is a positive integer), the length of the aperiodic SRS resource set activation / deactivation MAC CE according to the fourth embodiment is X+1 octets (N indicated in the table above is equal to X). Figure 4

[0102] ​For aperiodic SRS transmission for carrier switching scheduled by DCI format 2_3, if the higher layer parameter srs-TPC-PDCCH-Group = typeA, the association between the configured SRS CC set and each aperiodic SRS trigger state for aperiodic SRS transmission can be indicated or updated by SRS CC set activation / deactivation MAC CE according to the present application. In addition, more than four SRS CC sets (e.g., up to eight SRS CC sets) can be configured by RRC according to the present application.

[0103] According to a fifth embodiment, for aperiodic SRS triggered by DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group = typeA, the gNB can send the SRS CC set activation / deactivation MAC CE with the format provided in Figure 5-1 or Figure 5-2 .

[0104] In the SRS CC set activation / deactivation MAC CE shown in Figure 5-1 , four SRS CC sets are configured for the UE in a BWP. Therefore, the 2-bit field can indicate different SRS CC sets. One SRS CC set can be associated with one aperiodic SRS trigger state by the SRS CC set activation / deactivation MAC CE shown in Figure 5-1 .

[0105] Figure 5-1 The SRS CC set activation / deactivation MAC CE shown in Figure 5-1 is identified by a MAC subheader with a dedicated LCID. As shown in , the SRS CC set activation / deactivation MAC CE has the following fields:

[0106] Service Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0107] BWP ID: This field indicates the DL BWP to which the MAC CE applies as the codepoint of the DCI or UL bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0108] CC set ID associated with SRS request field = 01 or 10 or 11: Each of these fields occupies 2 bits and indicates the SRS CC set ID associated with SRS request field value of 01 or 10 or 11, respectively.

[0109] R: Reserved bit, set to 0.

[0110] According to Figure 5-1 The SRS CC set activation / deactivation MAC CE shown in FIGURE 10. Only one SRS CC set can be associated with each of the three aperiodic SRS trigger states. For example, if the field “CC set ID associated with SRS request field = 10” is set to 11, which indicates SRS CC set #3, then SRS CC set #3 is associated with the second aperiodic SRS trigger state indicated by SRS request field = 10.

[0111] Figure 5-1 The SRS CC set activation / deactivation MAC CE shown in FIGURE 10 has a fixed length of 16 bits (i.e., 2 octets).

[0112] In Figure 5-2 In the SRS CC set activation / deactivation MAC CE shown in FIGURE 10, up to eight SRS CC sets can be configured for a UE in a BWP. Therefore, the 3-bit field can indicate a different SRS CC set among the up to eight configured SRS CC sets. The SRS CC set ID associated with SRS request field = 00 can be configured by RRC signaling. Figure 5-2 In the SRS CC set activation / deactivation MAC CE shown in FIGURE 10, one SRS CC set is associated with one aperiodic SRS trigger state.

[0113] Figure 5-2 The SRS CC set activation / deactivation MAC CE shown in FIGURE 10 is identified by a MAC subheader with a dedicated LCID. As shown in FIGURE 11, the SRS CC set activation / deactivation MAC CE has the following fields: Figure 5-2

[0114] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0115] BWP ID: This field indicates the DL BWP to which the MAC CE applies as a codepoint of the DCI or UL bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0116] CC set ID associated with SRS request field = 01 or 10 or 11: Each of these fields occupies 3 bits and indicates the SRS CC set ID associated with SRS request field value of 01 or 10 or 11, respectively. Incidentally, in Figure 5-2 In FIGURE 10, the first (rightmost) bit of octet 3 (shown as “(CONT)”) is part of the “CC set ID associated with SRS request field = 11”.

[0117] R: Reserved bit, set to 0.

[0118] According to​ Figure 5-2 The SRS CC set activation / deactivation MAC CE shown in FIG. 6B, only one SRS CC set can be associated with each of the three aperiodic SRS triggering states. For example, if the field “CC set ID associated with SRS request field = 10” is set to 101 indicating SRS CC set #5, SRS CC set #5 is associated with the second aperiodic SRS triggering state indicated by SRS request field = 10.

[0119] Figure 5-2 The length of the SRS CC set activation / deactivation MAC CE shown in FIG. 6B is fixed to 24 bits (i.e., 3 octets).

[0120] According to a fifth embodiment, each of the configured SRS CC sets can be associated with one of the aperiodic SRS triggering states. The number of the configured SRS CC sets can be more than 4. Although Figure 5-1 and Figure 5-2 The SRS CC set activation / deactivation MAC CE shown in FIG. 6B can support up to 4 configured SRS CC sets and up to 8 configured SRS CC sets, but it is obvious that more configured SRS CC sets can be supported if each of the CC set IDs associated with SRS request field = 01 or 10 or 11 occupies more bits.

[0121] According to a sixth embodiment, for aperiodic SRS triggered by DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA, the gNB can send the SRS CC set activation / deactivation MAC CE with the format provided in FIG. 6C. Figure 6 The SRS CC set activation / deactivation MAC CE is sent by the gNB with the format provided in FIG. 6C. Up to eight SRS CC sets can be configured for a UE in a BWP.

[0122] The SRS CC set activation / deactivation MAC CE according to the sixth embodiment is identified by a MAC subheader with a dedicated LCID. As shown in FIG. 6C, the SRS CC set activation / deactivation MAC CE according to the sixth embodiment has the following fields: Figure 6

[0123] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0124] BWP ID: This field indicates the DL BWP to which the MAC CE applies as a codepoint of the DCI or UL bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0125] SN i ​This field indicates the activation or deactivation status of the SRS CC set with cc-SetIndex i associated with the Nth aperiodic SRS resource triggering state (N = 1 or 2 or 3). SN i This field is set to 1 to indicate that the SRS CC set with cc-SetIndex i shall be associated with the Nth aperiodic SRS resource triggering state. SN i This field is set to 0 to indicate that the SRS CC set with cc-SetIndex i shall be disassociated from the Nth aperiodic SRS resource triggering state.

[0126] R: Reserved bit, set to 0.

[0127] According to the sixth embodiment, the Nth aperiodic SRS resource triggering state (N = 1 or 2 or 3) is associated with each of the SRS CC sets indicated by the SN i fields set to 1 (N = 1 or 2 or 3; i is any one of 0 to 7) and disassociated from each of the SRS CC sets indicated by the SN i fields set to 0 (N = 1 or 2 or 3; i is any one of 0 to 7).

[0128] For example, SN0 to SN7 represent 8 SRS CC sets (N = 1 or 2 or 3), respectively. If SN i is set to 1 (N = 1 or 2 or 3; i is any one of 0 to 7), the (i+1)th SRS CC set indicated by SN i is associated with the Nth aperiodic SRS resource triggering state. On the other hand, if SN i is set to 0 (N = 1 or 2 or 3; i is any one of 0 to 7), the (i+1)th SRS CC set indicated by SN i is disassociated from the Nth aperiodic SRS resource triggering state.

[0129] The length of the aperiodic SRS resource set activation / deactivation MAC CE according to the sixth embodiment depends on the number of SRS CC sets configured for the UE in the BWP and is fixed to 32 bits (i.e., 4 octets) when the number of SRS CC sets configured for the UE in the BWP is 8.

[0130] Although Figure 6 the SRS CC set activation / deactivation MAC CE shown in FIG. 8 can support up to 8 configured SRS CC sets, it is apparent that more configured SRS CC sets can be supported if more SN i (i exceeds 8) fields are included.

[0131] For multi-DCI based multi-TRP operation, up to 5 CORESETs can be configured in a BWP for a UE for PDCCH transmission and each CORESET can be configured with a higher layer parameter CORESETPoolIndex. In FR2, the same SRS request value transmitted by different DCI transmitted from different TRPs should be associated with different SRS resources or different SRS resource sets. So, if a UE is configured with the higher layer parameter CORESETPoolIndex for at least one CORESET in one BWP, the above MAC CE for DCI format 0_1 or 1_1 or 2_3 should be associated with the higher layer parameter CORESETPoolIndex. The SRS request field in DCI can only trigger aperiodic SRS resources activated by the MAC CE associated with the higher layer parameter CORESETPoolIndex configured for the CORESET of the transmitted DCI.

[0132] The association between the higher layer parameter CORESETPoolIndex and the MAC CE according to the first embodiment to the sixth embodiment can be implemented by including an associatedCORESETPoolIndex field with 1 bit in the MAC CE according to the first embodiment to the sixth embodiment.

[0133] Figure 7 An example of the SRS CC set activation / deactivation MAC CE according to the seventh embodiment is illustrated. The example of the aperiodic SRS resource set activation / deactivation MAC CE according to the seventh embodiment is different from the SRS CC set activation / deactivation MAC CE according to the sixth embodiment only in that an additional associatedCORESETPoolIndex field (i.e. the C field in Figure 7 ) is added (to replace one of the reserved bits in Figure 6 ).

[0134] Figure 8 An example of the aperiodic SRS resource set activation / deactivation MAC CE according to the seventh embodiment is illustrated. The example of the aperiodic SRS resource set activation / deactivation MAC CE according to the seventh embodiment is different from the aperiodic SRS resource set activation / deactivation MAC CE according to the first embodiment only in that an additional associatedCORESETPoolIndex field (i.e. the C field in Figure 8 ) is added (to replace one of the reserved bits in Figure 1 ).

[0135] Figure 9is a schematic flow chart illustrating an embodiment of a method 900 according to the present application. In some embodiments, the method 900 is performed by an apparatus, such as a base unit. In certain embodiments, the method 900 can be performed by a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0136] The method 900 can comprise 902 transmitting an activation / deactivation MAC CE for indicating or updating the association between aperiodic SRS triggering state and a set of aperiodic SRS resources for carrying by a SRS request field value of a DCI format 0_1 or 1_1 or a DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB or a set of SRS CCs for carrying by a SRS request field value of a DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA.

[0137] Figure 10 is a schematic flow chart illustrating another embodiment of a method 1000 according to the present application. In some embodiments, the method 1000 is performed by an apparatus, such as a remote unit. In certain embodiments, the method 1000 can be performed by a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0138] The method 1000 can comprise 1002 receiving an activation / deactivation MAC CE for indicating or updating the association between aperiodic SRS triggering state and a set of aperiodic SRS resources for carrying by a SRS request field value of a DCI format 0_1 or 1_1 or a DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeB or a set of SRS CCs for carrying by a SRS request field value of a DCI format 2_3 with higher layer parameter srs-TPC-PDCCH-Group = typeA.

[0139] Figure 11 is a schematic block diagram illustrating an apparatus according to an embodiment.

[0140] With reference to Figure 11 , the UE (i.e., remote unit) comprises a processor, a memory, and a transceiver. The processor implements the functions, procedures, and / or methods as outlined in the above specification. The gNB (i.e., base unit) comprises a processor, a memory, and a transceiver. The processor implements the functions, procedures, and / or methods as outlined in the above specification. Figure 10 Figure 9 ​The layers of the radio interface protocol can be implemented by the processor. The memory is connected with the processor to store various information for driving the processor. The transceiver is connected with the processor to transmit and / or receive a radio signal. Needless to say, the transceiver can be implemented as the transmitter for transmitting a radio signal and the receiver for receiving a radio signal.

[0141] The memory can be positioned within or external to the processor and connected with the processor through various well-known means.

[0142] In the above-described embodiments, components and features of the embodiments are combined in a predetermined form. Each component or function can be considered as an option unless explicitly stated otherwise. Each component or feature can be implemented to be not associated with other components or features. Also, a certain embodiment can be configured by associating some components and / or features. The order of operations described in the embodiments can be changed. Some components or features of any embodiment can be included in another embodiment or replaced with those of another embodiment. It is obvious that claims not explicitly cited in the claims are combined to form the embodiments or included in new claims.

[0143] The embodiments can be implemented by hardware, firmware, software, or a combination thereof. In case of implementation by hardware, according to hardware implementation, the exemplary embodiments described herein can be implemented by 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, etc.

[0144] The embodiments can be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the application is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A method performed by a base station unit, comprising: An activation / deactivation MAC CE is transmitted to indicate or update the association between the aperiodic SRS triggering state and the aperiodic SRS resource set for the SRS request field value carried by DCI format 0_1 ​​or 1_1 or DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeB, or the SRS CC set for the SRS request field value carried by DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

2. The method according to claim 1, wherein The activation / deactivation MAC CE is an aperiodic SRS resource set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the aperiodic SRS resource set for carrying the SRS request field value through DCI format 0_1 ​​or 1_1 or DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeB.

3. The method according to claim 2, wherein: One or more aperiodic SRS triggering states and associated aperiodic SRS resource sets are indicated in the aperiodic SRS resource set activation / deactivation MAC CE.

4. The method according to claim 2 or 3, wherein: One or more aperiodic SRS triggering state ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS triggering state or states the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

5. The method according to claim 4, wherein The activation status of all configured aperiodic SRS resource sets for each aperiodic SRS triggering state is indicated by a bitmap.

6. The method according to claim 2 or 3, wherein: One or more aperiodic SRS resource set ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS resource set(s) the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

7. The method according to claim 6, wherein: The associated aperiodic SRS triggering state for each SRS resource set is indicated by a 3-bit bitmap, and each bit of the 3-bit bitmap indicates an activation state of each associated aperiodic SRS triggering state for the aperiodic SRS resource set indicated by the SRS resource set ID field.

8. The method according to claim 1, wherein The activation / deactivation MAC CE is an SRS CC set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the SRS CC set for carrying the SRS request field value through DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

9. The method according to claim 8, wherein More than four SRS CC sets may be configured for a UE depending on the UE capability.

10. The method according to claim 8 or 9, wherein: One or more SRS CC set ID fields are included in the SRS CC set activation / deactivation MAC CE to indicate the activated SRS CC set for each aperiodic SRS triggering state.

11. The method according to claim 8 or 9, wherein: The activation states of all configured SRS CC sets for each aperiodic SRS triggering state are listed as a bitmap, and one or more SRS CC sets are activated for one aperiodic SRS triggering state.

12. The method according to claim 1, wherein The activation / deactivation MAC CE is associated with a higher layer parameter CORESETPoolIndex configured for the CORESET.

13. A method performed by a remote unit, comprising: An activation / deactivation MAC CE is received to indicate or update the association between the aperiodic SRS triggering state and the aperiodic SRS resource set for the SRS request field value carried by DCI format 0_1 ​​or 1_1 or DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeB, or the SRS CC set for the SRS request field value carried by DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

14. The method according to claim 13, wherein: The activation / deactivation MAC CE is an aperiodic SRS resource set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the aperiodic SRS resource set for carrying the SRS request field value through DCI format 0_1 ​​or 1_1 or DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeB.

15. The method according to claim 14, wherein One or more aperiodic SRS triggering states and associated aperiodic SRS resource sets are indicated in the aperiodic SRS resource set activation / deactivation MAC CE.

16. The method according to claim 14 or 15, wherein: One or more aperiodic SRS triggering state ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS triggering state or states the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

17. The method according to claim 16, wherein The activation status of all configured aperiodic SRS resource sets for each aperiodic SRS triggering state is indicated by a bitmap.

18. The method according to claim 14 or 15, wherein One or more aperiodic SRS resource set ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS resource set(s) the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

19. The method according to claim 18, wherein The associated aperiodic SRS triggering state for each SRS resource set is indicated by a 3-bit bitmap, and each bit of the 3-bit bitmap indicates an activation state of each associated aperiodic SRS triggering state for the aperiodic SRS resource set indicated by the SRS resource set ID field.

20. The method according to claim 13, wherein The activation / deactivation MAC CE is an SRS CC set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the SRS CC set for carrying the SRS request field value through DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

21. The method according to claim 20, wherein More than four SRS CC sets may be configured for a UE depending on the UE capability.

22. The method according to claim 20 or 21, wherein One or more SRS CC set ID fields are included in the SRS CC set activation / deactivation MAC CE to indicate the activated SRS CC set for each aperiodic SRS triggering state.

23. The method according to claim 20 or 21, wherein The activation states of all configured SRS CC sets for each aperiodic SRS triggering state are listed as a bitmap, and one or more SRS CC sets are activated for one aperiodic SRS triggering state.

24. The method according to claim 13, wherein The activation / deactivation MAC CE is associated with a higher layer parameter CORESETPoolIndex configured for the CORESET.

25. A base station unit, comprising: A transmitter configured to transmit an activation / deactivation MAC CE for indicating or updating an association between an aperiodic SRS triggering state and an aperiodic SRS resource set for an SRS request field value carried by DCI format 0_1 ​​or 1_1 or DCI format 2_3 with a higher layer parameter srs-TPC-PDCCH-Group=typeB, or an SRS CC set for an SRS request field value carried by DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

26. The base station unit of claim 25, wherein: The activation / deactivation MAC CE is an aperiodic SRS resource set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the aperiodic SRS resource set for carrying the SRS request field value through DCI format 0_1 ​​or 1_1 or DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeB.

27. The base station unit of claim 26, wherein: One or more aperiodic SRS triggering states and associated aperiodic SRS resource sets are indicated in the aperiodic SRS resource set activation / deactivation MAC CE.

28. The base station unit according to claim 26 or 27, wherein: One or more aperiodic SRS triggering state ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS triggering state or states the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

29. The base station unit of claim 28, wherein: The activation status of all configured aperiodic SRS resource sets for each aperiodic SRS triggering state is indicated by a bitmap.

30. The base station unit according to claim 26 or 27, wherein: One or more aperiodic SRS resource set ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS resource set(s) the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

31. The base station unit of claim 30, wherein: The associated aperiodic SRS triggering state for each SRS resource set is indicated by a 3-bit bitmap, and each bit of the 3-bit bitmap indicates an activation state of each associated aperiodic SRS triggering state for the aperiodic SRS resource set indicated by the SRS resource set ID field.

32. The base station unit of claim 25, wherein: The activation / deactivation MAC CE is an SRS CC set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the SRS CC set for carrying the SRS request field value through DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

33. The base station unit of claim 32, wherein: More than four SRS CC sets may be configured for a UE depending on the UE capability.

34. A base station unit according to claim 32 or 33, wherein: One or more SRS CC set ID fields are included in the SRS CC set activation / deactivation MAC CE to indicate the activated SRS CC set for each aperiodic SRS triggering state.

35. The base station unit according to claim 32 or 33, wherein: The activation states of all configured SRS CC sets for each aperiodic SRS triggering state are listed as a bitmap, and one or more SRS CC sets are activated for one aperiodic SRS triggering state.

36. The base station unit of claim 25, wherein: The activation / deactivation MAC CE is associated with a higher layer parameter CORESETPoolIndex configured for the CORESET.

37. A remote unit comprising: A receiver configured to receive an activation / deactivation MAC CE for indicating or updating an association between an aperiodic SRS triggering state and an aperiodic SRS resource set for an SRS request field value carried by DCI format 0_1 ​​or 1_1 or DCI format 2_3 with a higher layer parameter srs-TPC-PDCCH-Group=typeB, or an SRS CC set for an SRS request field value carried by DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

38. The remote unit of claim 37, wherein: The activation / deactivation MAC CE is an aperiodic SRS resource set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the aperiodic SRS resource set for carrying the SRS request field value through DCI format 0_1 ​​or 1_1 or DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeB.

39. The remote unit of claim 38, wherein: One or more aperiodic SRS triggering states and associated aperiodic SRS resource sets are indicated in the aperiodic SRS resource set activation / deactivation MAC CE.

40. The remote unit of claim 38 or 39, wherein: One or more aperiodic SRS triggering state ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS triggering state or states the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

41. The remote unit of claim 40, wherein: The activation status of all configured aperiodic SRS resource sets for each aperiodic SRS triggering state is indicated by a bitmap.

42. The remote unit of claim 38 or 39, wherein: One or more aperiodic SRS resource set ID fields are included in the aperiodic SRS resource set activation / deactivation MAC CE to indicate which aperiodic SRS resource set(s) the aperiodic SRS resource set activation / deactivation MAC CE is applicable to.

43. The remote unit of claim 42, wherein: The associated aperiodic SRS triggering state for each SRS resource set is indicated by a 3-bit bitmap, and each bit of the 3-bit bitmap indicates an activation state of each associated aperiodic SRS triggering state for the aperiodic SRS resource set indicated by the SRS resource set ID field.

44. The remote unit of claim 37, wherein: The activation / deactivation MAC CE is an SRS CC set activation / deactivation MAC CE for indicating or updating the association between the aperiodic SRS triggering state and the SRS CC set for carrying the SRS request field value through DCI format 2_3 with the higher layer parameter srs-TPC-PDCCH-Group=typeA.

45. The remote unit of claim 44, wherein: More than four SRS CC sets are configured for the remote unit depending on UE capabilities.

46. ​​The remote unit of claim 44 or 45, wherein: One or more SRS CC set ID fields are included in the SRS CC set activation / deactivation MAC CE to indicate the activated SRS CC set for each aperiodic SRS triggering state.

47. The remote unit of claim 44 or 45, wherein: The activation states of all configured SRS CC sets for each aperiodic SRS triggering state are listed as a bitmap, and one or more SRS CC sets are activated for one aperiodic SRS triggering state.

48. The remote unit of claim 37, wherein: The activation / deactivation MAC CE is associated with a higher layer parameter CORESETPoolIndex configured for the CORESET.

Images