Method and apparatus for enabling panel-specific configuration and transmission

Abstract

Methods, base station units, and remote units are disclosed. According to one embodiment, a method at a base station unit includes: sending a first message to a remote unit, the first message including a configuration related to two or more sounding reference signal (SRS) resource groups, each SRS resource group containing one or more SRS resources for codebook-based or non-codebook-based UL transmission, wherein one or more SRS resources in one SRS resource group are sent only by one panel; sending a second message to the remote unit, the second message including a set of power control parameters configured for each SRS resource group, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to wireless communication and, more particularly, to methods and apparatuses for enabling panel-specific configurations and panel-specific uplink (UL) transmissions. Background Art

[0002] The following abbreviations are hereby defined, some of which are referenced in the following description: 3rd Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), Frequency Division Duplexing (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), New Radio (NR), 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), Multiple Input Multiple Output (MIMO), Frequency Range 2 (FR2), Physical Uplink Shared Channel (PUSCH), Physical Downlink Control Channel (PDCCH), Sounding Reference Signal (SRS), SRS Resource Indicator (SRI), Downlink Control Information (DCI), Resource Block (RB), Non-Zero Power (NZP), Channel State Information Reference Signal (CSI-RS), Control Resource Set (CORESET), Bandwidth Part (BWP), Quasi-Co-Location (QCL), Transmission Configuration Indicator (TCI), Transmitter Receiver Point (TRP).

[0003] In NR, Release 16 will include support for multi-panel based UL MIMO operation. Enhancements for multiple TRPs and / or multiple panel transmissions include improved reliability and robustness through ideal and non-ideal backhaul among multiple TRPs. Designating UL transmit beams for multi-panel operation will help in selecting panel-specific beams for UL transmissions. Summary of the Invention

[0004] Methods and apparatuses for enabling panel-specific configurations and panel-specific UL transmissions are disclosed.

[0005] In one embodiment, a method at a base station unit includes: sending a first message to a remote unit, the first message including a configuration related to two or more sounding reference signal (SRS) resource groups, each SRS resource group including one or more SRS resources for uplink transmission based on codebook and non-codebook, wherein one or more SRS resources in one SRS resource group are sent by only one panel. Sending a second message to the remote unit, the second message including a set of power control parameters configured for each SRS resource group, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal.

[0006] In another embodiment, a method at a remote unit includes: receiving a first message from a base station unit, the first message including a configuration related to two or more sounding reference signal (SRS) resource groups, each SRS resource group including one or more SRS resources for uplink transmission based on codebook and non-codebook, wherein one or more SRS resources in one SRS resource group are sent by only one panel; receiving a second message from the base station unit, the second message including a set of power control parameters configured for each SRS resource group, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal; and based on the second message, determining a set of power control parameters for each SRS resource according to respective panels.

[0007] In another embodiment, a base station unit includes: a transceiver; a memory; a processor coupled to the transceiver and the memory and configured to: send a first message to a remote unit, the first message including a configuration related to two or more sounding reference signal (SRS) resource groups, each SRS resource group including one or more SRS resources for uplink transmission based on codebook and non-codebook, wherein one or more SRS resources in one SRS resource group are sent by only one panel, and send a second message to the remote unit, the second message including a set of power control parameters configured for each SRS resource group, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal.

[0008] In another embodiment, the remote unit includes: a transceiver; a memory; a processor coupled to the transceiver and the memory and configured to: receive a first message from a base station unit, the first message including a configuration related to two or more sounding reference signal (SRS) resource sets, each SRS resource set including one or more SRS resources for uplink transmission based on a codebook and non-codebook, wherein one or more SRS resources in one SRS resource set are transmitted only by one panel, receive a second message from the base station unit, the second message including a set of power control parameters configured for each SRS resource set, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal, and based on the second message, determine a set of power control parameters for each SRS resource according to respective panels.

[0009] Those skilled in the art will understand that the effects that can be achieved using the present disclosure are not limited to what has been specifically described above, and the above and other effects that can be achieved by the present disclosure will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more specific description of the embodiments briefly described above will be presented by reference to specific embodiments shown in the drawings. It is understood that these drawings depict only some embodiments and are not to be considered as limiting the scope. The embodiments will be described and explained with additional specificity and detail by using the drawings, wherein:

[0011] Figure 1 FIG. [FIG NUMBER] is a schematic diagram showing a radio link between one UE having multiple panels and multiple TRPs;

[0012] Figure 2 FIG. [FIG NUMBER] is a schematic diagram showing UL transmission based on multiple PDCCHs according to one embodiment;

[0013] Figure 3 FIG. [FIG NUMBER] shows Figure 2 a schematic signal flow diagram of the signal flow between a gNB and a UE of the embodiment shown;

[0014] Figure 4 FIG. [FIG NUMBER] is a schematic diagram showing UL transmission based on a single PDCCH according to another embodiment;

[0015] Figure 5 FIG. [FIG NUMBER] is a schematic flowchart showing processing steps at a gNB according to another embodiment;

[0016] Figure 6 FIG. [FIG NUMBER] is a schematic block diagram showing a device according to one embodiment. DETAILED DESCRIPTION

[0017] As will be understood by those skilled in the art, aspects of the described 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, microcode, etc.), or an embodiment combining software and hardware aspects, which may generally be referred to herein as a "circuit", "module", or "system". Additionally, 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, hereinafter referred to as "code". The storage device may be tangible, non-transitory, and / or non-transmissive. The storage device may not contain a signal. In certain embodiments, the storage device only uses signals for accessing the code.

[0018] Certain functional units described in this specification may be marked as "modules" to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit, including custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in a programmable hardware device, such as a field programmable gate array, programmable array logic, programmable logic device, etc.

[0019] A module may also be implemented in code and / or software for execution by various types of processors. The identified code module may, for example, include one or more physically or logically executable code blocks, which may be organized, for example, as objects, procedures, or functions. However, the executable files of the identified module need not be physically placed together, but may include different instructions stored in different locations, which, when logically connected together, include the module and implement the stated purpose of the module.

[0020] In fact, a code module may be a single instruction, or multiple instructions, and may even be distributed over several different code segments, different programs, and multiple memory devices. Similarly, the operational data may be identified and described herein within the module and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations, including different computer-readable storage devices. In cases where a module or a portion of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0021] Any combination of one or more computer-readable media can be utilized. The computer-readable media can be a computer-readable storage medium. The computer-readable storage medium can be a storage device that stores code. The storage device can be, by way of example, but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0022] A non-exhaustive list of more specific examples of storage devices will include the following: an electrical connection having one or more wires, a portable computer floppy disk, 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.

[0023] The code for implementing the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages such as Python, Ruby, Java, Smalltalk, C++, etc., as well as conventional procedural programming languages such as the "C" programming language, etc., and / or machine language such as assembly language. The code can execute entirely on the user's computer, partly on the user's computer, execute as a stand-alone software package, partly on the user's computer and partly on a remote computer, or execute entirely on a remote computer or server. In the last scenario, the remote computer can be connected to the user's computer through any type of network connection, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider via the Internet).

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

[0025] In addition, the described features, structures, or characteristics of the embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as programming examples, 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 instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring any aspect of the embodiments.

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

[0027] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other device to operate in a particular manner so that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions and / or actions specified in the schematic flowcharts and / or schematic block diagram blocks.

[0028] The code can also be loaded onto a computer, other programmable data processing device, or other device to cause a series of operational steps to be performed on the computer, other programmable device, or other device to produce a computer-implemented process such that the code executed on the computer or other programmable device provides a process for implementing the functions and / or actions specified in the flowchart and / or block diagram blocks.

[0029] The schematic flowcharts and / or schematic block diagrams depicted in the drawings illustrate the possible architectures, functions, and operations of apparatuses, systems, methods, and program products according to various embodiments described below. In this regard, each block in the schematic flowcharts and / or schematic block diagrams can represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function.

[0030] It should also be noted that in some alternative implementations, the functions labeled in the blocks may not occur in the order labeled in the figures. For example, depending on the functions involved, two consecutively shown blocks may be executed substantially simultaneously, or these blocks may sometimes be executed in the reverse order. Other steps and methods that are equivalent in function, logic, or effect to one or more of the boxes or portions thereof may be the same as those shown in the figures.

[0031] Although various arrow types and line types may be employed in the flowcharts and / or block diagrams, they are understood not to limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used to merely indicate the logical flow of the depicted embodiments. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the recited steps of the depicted embodiment. It will also be noted that each block of the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware that performs the specified functions or actions, or a combination of dedicated hardware and code.

[0032] The description of an element in each figure may refer to the elements of the previous figures. In all the figures, the same numbers represent the same elements, including alternative embodiments of the same element.

[0033] The description of an element in each figure may refer to the elements of the previous figures. In all the figures, the same numbers represent the same elements, including alternative embodiments of the same element.

[0034] In NR, Release 15 only supports UL transmission based on a single panel, and only one UL link should be maintained for one UE at a given time. For example, only one SRS resource set may be configured for one UE for UL transmission based on codebook or non-codebook, and all SRS resources in this single set share the same power control parameters.

[0035] In Release 15, the SRS resources in the same SRS resource set share the same set of power control parameters, including P0 (target received power), alpha (path loss compensation factor), path loss reference signal (providing DL-RS for the UE to determine the DL path loss estimate), and closed-loop power control ID (CL-PCID). The total calculated power will be evenly distributed among all the simultaneous ports within the SRS resource set. This means that the SRS transmission can only support one power control loop including open-loop power control and closed-loop power control. Therefore, SRS resources or SRS ports with the same power are sent to different TRPs using different panels simultaneously.

[0036] For SRS and PUCCH transmissions in the higher frequency band FR2, the higher layer parameter spatialRelationInfo is used to indicate the transmission beam or filter for each SRS or PUCCH resource. Each PUCCH-spatialRelationInfo configures power control parameters. This means that PUCCH can support beam-specific power control. However, due to the SRS configuration architecture in Release 15, the detailed solution is not applicable to SRS transmissions.

[0037] If both the UE and the gNB know the association between the transmission beam of the SRS and the UE panel, more accurate panel-specific configurations can be supported, enabling more efficient UL transmissions.

[0038] Figure 1 Schematic diagram of the radio link between one UE with multiple panels and multiple TRPs.

[0039] For a UE equipped with multiple panels, transmission based on panel switching can provide additional diversity gain with limited power. In addition, simultaneous transmission of PUSCH by multiple panels can provide both diversity gain and high UL throughput. To enable these two scenarios, panel-specific configurations and transmissions should be enabled.

[0040] Take SRS power control as an example. As Figure 1 shown, UL beam #1-2 of panel #1 and UL beam #2-2 of panel #2 are expected to cover different TRPs (TRP #1 and TRP #2 respectively). Generally, Figure 1 the path losses 1 (PL1) and PL2 shown may vary greatly and should be estimated based on different DL-RSs (such as CSI-RS #1-2 and CSI-RS #2-2). Therefore, it is preferable to support independent power control loops for different panel-TRP links so that transmissions on different panels can be sent at different target powers. In addition, independent power control for each panel can also facilitate the network to perform interference coordination among multiple TRPs to obtain better system performance.

[0041] To support multiple panel-TRP link transmissions and panel-specific transmissions, the panel ID needs to be defined in an explicit or implicit manner and panel-specific configurations need to be supported.

[0042] Figure 2 Schematic diagram showing UL transmission based on multiple PDCCHs according to one embodiment.

[0043] To enable panel-specific configurations and transmissions, the panel ID needs to be defined and panel-specific parameters need to be configured, such as power control-related parameters for UL transmission.

[0044] According to one embodiment, the UE needs to report its capabilities, such as the number of panels it is equipped with and / or the number of panels activated at a given time. Based on the reported UE capabilities, the gNB can explicitly assign a unique ID to each panel or each activated panel.

[0045] For example, if the UE reports its capabilities as {# of panels = 4 and # of activated panels = 2}, then the gNB can assign panel #1, 2, 3, 4 to each panel or panel #1, 2 to each activated panel based on the reported capabilities. The gNB can associate the panel ID with UE-specific higher-layer parameters, which include PUSCH-Config, PUSCH-ConfigCommon, PUSCH-PowerControl, PUCCH-Config, PUCCH-ConfigCommon, PUCCH-PowerContorl, and SRS-Config, etc. The UE can obtain the panel-specific configurations for PUSCH, PUCCH, and SRS transmissions from the higher-layer signaling received from the gNB to enable Figure 2 the multi-PDCCH-based PUSCH transmission shown in

[0046] As Figure 2 shown, the UE is equipped with 4 panels, and panel #1 and panel #2 are activated for UL transmission. There are two links between TRP#1 and panel #1 and between TRP#2 and panel #2. The UE can receive UL grants from TRP#1 via panel #1 and from TRP#2 via panel #2. The UE can send SRS, PUSCH, and PUCCH to TRP#1 via panel #1 and send SRS, PUSCH, and PUCCH to TRP#2 via panel #2. In this structure, each TRP can send DCI to the UE to schedule the UE to send PUSCH and / or SRS. The gNB can configure 2 different sets of PUSCH-Config, PUCCH-Config, SRS-Config, namely PUSCH-Config#1, PUCCH-Config#1, SRS-Config#1 and PUSCH-Config#2, PUCCH-Config#2, SRS-Config#2, for the UE and associate them with panel ID panel #1 and panel #2 respectively. TRP#1 and TRP#2 can use independent DCI to schedule independent PUSCH or SRS transmissions with different panel-specific configurations. With this arrangement, panel-specific power control can also be achieved.

[0047] In addition to explicitly allocating panel IDs as described above, another way to allocate panel IDs is to configure more than one SRS resource set for a UE used for UL transmission based on codebook and non-codebook, where each SRS resource set corresponds to a UE panel. In other words, the identification of the SRS resource set can serve as the panel ID. The gNB can configure independent power control parameters {p0, alpha, pathlossRS} for different SRS resource sets, that is, configure power control parameters according to the panel.

[0048] Figure 3 shows Figure 2 a schematic signal flow diagram of the signal flow between the gNB and the UE of the illustrated embodiment.

[0049] As Figure 3 shown, in step 301, the UE reports its capabilities to the gNB. The capabilities here can include the number of panels equipped by the UE and / or the number of activated panels. According to this report, the gNB allocates panel IDs for all panels or the active panels of the UE. In addition, the gNB can associate the panel ID with UE-specific higher-layer parameters. Next, in step S302, the gNB can send higher-layer signaling including configurations related to the panel ID and UE-specific higher-layer parameters to the UE. Next, in step S303, the gNB can send a UL grant to the UE to trigger SRS transmission or schedule PUSCH transmission. Next, in step S304, the UE can send the corresponding SRS or PUSCH (S304) to the gNB using the panel-specific parameters obtained from the higher-layer signaling.

[0050] Figure 4 is a schematic diagram showing UL transmission based on a single PDCCH according to another embodiment.

[0051] Figure 4 The structure shown is Figure 2 similar, except that only TRP#1 can send DCI to the UE to schedule the UE to send PUSCH and / or SRS.

[0052] According to the prior art, for codebook or non-codebook-based transmission, a UE can only be configured with one SRS resource set, and all SRS resources in a single set share the same power control parameters.

[0053] In NR, different SRS resource sets can be used for different purposes. For example, the gNB can configure two SRS resource sets with periodic and aperiodic time behaviors respectively to achieve more flexible channel sounding. The SRS resources within an SRS resource set transmitted by the same panel can be defined as an SRS resource group. According to another embodiment, the identifier of the SRS resource group can serve as the panel ID. Different SRS resource groups can be configured with different panel-specific parameters, such as the power control parameter set {p0, alpha, pathlossRS, closeLoopIndex}.

[0054] For example, the UE can obtain the mapping between the SRS-Group-ID set and the power control parameter set {p0, alpha, pathlossRS, closeLoopIndex} based on the radio resource control (RRC) signaling shown in Table 1.

[0055] Table 1

[0056]

[0057] With this arrangement, SRS resource-specific configuration is enabled, that is, p0, alpha, pathlossRS, and other related parameters can be configured for each SRS resource.

[0058] Based on this embodiment, Figure 4 the single PDCCH-based multi-panel UL transmission shown can be achieved.

[0059] Return Figure 1 and Figure 3 discuss another embodiment.

[0060] In NR, the higher layer parameter spatialRelationInfo can be configured to indicate the transmission beam or filter of each SRS resource or PUCCH resource in FR2. The candidate values of spatialRelationInfo can be set to 'SSB-Index' or 'CSI-RS-Index', that is, the index of the synchronization signal block or the index of the channel state information resource signal. If the higher layer parameter spatialRelationInfo of the SRS resource is configured to a specific CSI-RS, the UE will transmit the SRS resource through the UL beam also used to receive the specific CSI-RS. As Figure 1As shown, the DL-RS (CSI-RS#1-1, CSI-RS#1-2, CSI-RS#1-3) sent from TRP#1 is received through Panel#1, while the DL-RS (CSI-RS#2-1, CSI-RS#2-2, CSI-RS#2-3) sent from TRP#2 is received through Panel#2. The network can group the DL-RS into different groups corresponding to different TRPs. Assuming that at a given time, a TRP can only communicate with one panel of the UE, different DL-RS groups correspond to different UE panels. Panel-specific parameters, such as a set of power control parameters, can be configured or associated with different DL-RS groups. In other words, the identification of the DL-RS group can act as the panel ID.

[0061] The UE can obtain the panel-specific parameters of each panel according to the spatialRelationInfo of each SRS resource or PUCCH resource.

[0062] Take Figure 1 the scenario shown as an example. All the DL-RS sent by one TRP can be simply grouped into one group, and a set of power control parameters is associated with each DL-RS group as follows:

[0063] DL-RS-Group#1::={CSI-RS#1-1, CSI-RS#1-2, CSI-RS#1-3, p0-1, alpha-1, pathlossRS-1}

[0064] DL-RS-Group#2::={CSI-RS#2-1, CSI-RS#2-2, CSI-RS#2-3, p0-2, alpha-2, pathlossRS-2}.

[0065] The spatialRelationInfo of each SRS resource is configured as follows:

[0066] SRS-Resource-Set::={

[0067] SRS resource#1-1::={spatialRelationInfo='CSI-RS#1-1'}

[0068] SRS resource#1-2::={spatialRelationInfo='CSI-RS#1-2'}

[0069] SRS resource#1-3::={spatialRelationInfo='CSI-RS#1-3'}

[0070] SRS Resource #2-1:: = {spatialRelationInfo = 'CSI-RS#2-1'}

[0071] SRS Resource #2-2:: = {spatialRelationInfo = 'CSI-RS#2-2'}

[0072] SRS Resource #2-3:: = {spatialRelationInfo = 'CSI-RS#2-3'}

[0073] }

[0074] SRS resources whose spatialRelationInfo values fall into the same DL-RS group can share the same set of power control parameters. For example, since the spatialRelationInfo of SRS Resource #1-1, SRS Resource #1-2, and SRS Resource #1-3 are CSI-RS#1-1, CSI-RS#1-2, and CSI-RS#1-3 respectively, and they are in the same DL-RS group DL-RS-Group#1, SRS Resource #1-1, SRS Resource #1-2, and SRS Resource #1-3 will share the same set of power control parameters {p0-1, alpha-1, pathlossRS-1}. Similarly, SRS Resource #2-1, SRS Resource #2-2, and SRS Resource #2-3 will share the same set of power control parameters {p0-2, alpha-2, pathlossRS-2}.

[0075] With this arrangement, the panel ID is implicitly assigned, and panel-specific configurations and UL transmissions are enabled.

[0076] Figure 5 is a schematic flowchart showing the processing steps at the gNB according to another embodiment.

[0077] In step 1, the gNB receives a report related to the UE's capabilities from the UE. The capabilities reported by the UE may include the number of panels and / or the number of active panels.

[0078] In step 2, the gNB assigns a unique ID to each panel.

[0079] In step 3, the gNB configures the panel IDs associated with UE-specific higher-layer parameters, such as PUSCH-Config, PUSCH-ConfigCommon, PUSCH-PowerControl, PUCCH-Config, PUCCH-ConfigCommon, PUCCH-PowerContorl, and SRS-Config.

[0080] In step 4, the gNB sends high-layer signaling including configured panel-specific parameters to the UE.

[0081] In step 5, the gNB sends a UL grant to schedule a PUSCH or trigger an aperiodic SRS.

[0082] In step 6, the gNB receives an SRS or PUSCH sent from the UE using the panel-specific parameters.

[0083] Corresponding processing steps may be performed at the UE, and the figure is omitted in the specification.

[0084] Reference Figure 6 , the UE includes a processor, a memory, and a transceiver. The processor implements the functions, processes, and / or methods proposed above Figures 1 to 5 . The gNB includes a processor, a memory, and a transceiver. The processor implements the functions, processes, and / or methods proposed above Figures 1 to 5 . The layers of the radio interface protocol may be implemented by the processor. The memory is connected to the processor to store various information for driving the processor. The transceiver is connected to the processor to transmit and / or receive radio signals.

[0085] The memory may be located inside or outside the processor and is connected to the processor in various well-known ways. In addition, the relay node may have a single antenna or multiple antennas.

[0086] In the above embodiments, the components and features of the embodiments are combined in a predetermined form. Unless otherwise clearly stated, each component or function should be regarded as an option. Each component or feature may be implemented without being associated with other components or features. In addition, the embodiments may be configured by associating some components and / or features. The order of operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with components and features corresponding to another embodiment. Obviously, the claims not explicitly recited in the claims are combined to form embodiments or included in new claims.

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

[0088] The present disclosure aims to define methods and devices for panel IDs to enable panel-specific configurations and panel-specific UL transmissions. The present disclosure also provides methods and devices for panel-specific SRS power control parameter configurations to enable power control loop maintenance for each panel.

[0089] The embodiments can be practiced in other specific forms. The described embodiments are considered to be illustrative rather than restrictive in all respects. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes that fall within the equivalent meaning and scope of the claims should be included within their scope.

Claims

1. A method at a base station unit, comprising: Sending a first message to a remote unit, the first message including configurations related to two or more sounding reference signal (SRS) resource sets, each SRS resource set containing one or more SRS resources for codebook - based or non - codebook - based uplink transmission, wherein one or more SRS resources in one SRS resource set are sent only by one panel; And Sending a second message to the remote unit, the second message including a set of power control parameters configured for each SRS resource set, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal.

2. The method according to claim 1, further comprising: Sending a third message to the remote unit, the third message including a plurality of panel IDs respectively configured for a plurality of panels based on a report of the capabilities of the remote unit, wherein the panel ID is associated with a set of high - layer parameters configured for PUCCH and / or PUSCH and / or SRS.

3. The method according to claim 2, wherein, The capabilities of the remote unit include the number of equipped panels and / or the number of activated panels.

4. The method according to claim 1, further comprising: Sending a fourth message to the remote unit, the fourth message including configurations related to one or more downlink reference signal (DL - RS) resource sets, wherein the set of power control parameters is configured for each DL - RS resource set, and wherein the DL - RS is a channel state information reference signal (CSI - RS) and / or a synchronization signal block (SSB).

5. A method at a remote unit, comprising: Receiving a first message from a base station unit, the first message including configurations related to two or more sounding reference signal (SRS) resource sets, each SRS resource set containing one or more SRS resources for codebook - based or non - codebook - based uplink transmission, wherein one or more SRS resources in one SRS resource set are sent only by one panel; Receiving a second message from the base station unit, the second message including a set of power control parameters configured for each SRS resource set, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal; And Based on the second message, determining a set of power control parameters for each SRS resource according to respective panels.

6. The method according to claim 5, further comprising: Reporting the capabilities of the remote unit to the base station unit; Receiving a third message from the base station unit, the third message including a plurality of panel IDs respectively configured for a plurality of panels based on a report of the capabilities of the remote unit, wherein the panel ID is associated with a set of high - layer parameters configured for PUCCH and / or PUSCH and / or SRS; Determining the association between the panel ID and the set of high - layer parameters of PUCCH and / or PUSCH and / or SRS based on the third message; And Determining a set of high - layer parameters for each panel based on the corresponding panel ID.

7. The method according to claim 6, wherein The capabilities of the remote unit include the number of equipped panels and / or the number of activated panels.

8. The method according to claim 5 further comprises: receiving a fourth message from the base station unit, the fourth message including configurations related to one or more downlink reference signal (DL-RS) resource groups, wherein the set of power control parameters is configured for each DL-RS resource group, and wherein the DL-RS is a channel state information reference signal (CSI-RS) and / or a synchronization signal block (SSB); and determining, based on the fourth message and according to the transmit beam indication of each SRS resource, a set of power control parameters for each SRS resource.

9. A base station unit comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory and configured to: send a first message to a remote unit, the first message including configurations related to two or more sounding reference signal (SRS) resource groups, each SRS resource group including one or more SRS resources for codebook-based or non-codebook-based uplink transmission, wherein one or more SRS resources in one SRS resource group are transmitted by only one panel, and send a second message to the remote unit, the second message including a set of power control parameters configured for each SRS resource group, wherein the set of power control parameters at least includes a target received power, a path loss compensation factor, and a path loss reference signal.

10. The base station unit according to claim 9, wherein the processor is further configured to: send a third message to the remote unit, the third message including a plurality of panel IDs respectively configured for a plurality of panels based on a report of the capabilities of the remote unit, wherein the panel ID is associated with a set of high-layer parameters configured for PUCCH and / or PUSCH and / or SRS.

11. The base station unit according to claim 10, wherein, The capabilities of the remote unit include the number of equipped panels and / or the number of activated panels.

12. The base station unit according to claim 9, wherein the processor is further configured to: send a fourth message to the remote unit, the fourth message including configurations related to one or more downlink reference signal (DL-RS) resource groups, wherein the set of power control parameters is configured for each DL-RS resource group, and wherein the DL-RS is a channel state information reference signal (CSI-RS) and / or a synchronization signal block (SSB).

13. A remote unit comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory and configured to: receive a first message from a base station unit, the first message including configurations related to two or more sounding reference signal (SRS) resource groups, each SRS resource group including one or more SRS resources for codebook-based or non-codebook-based uplink transmission, wherein one or more SRS resources in one SRS resource group are transmitted by only one panel, Receive a second message from the base station unit, the second message including a set of power control parameters configured for each SRS resource group, where the set of power control parameters includes at least a target reception power, a path loss compensation factor, and a path loss reference signal, and Based on the second message, determine, according to respective panels, a set of power control parameters for each SRS resource.

14. The remote unit according to claim 13, wherein the processor is further configured to:[[]] Report the capabilities of the remote unit to the base station unit, Receive a third message from the base station unit, the third message including a plurality of panel IDs respectively configured for a plurality of panels based on a report of the capabilities of the remote unit, where the panel ID is associated with a set of high-layer parameters configured for PUCCH and / or PUSCH and / or SRS, Based on the third message, determine the association between the panel ID and the set of high-layer parameters for PUCCH and / or PUSCH and / or SRS, and Based on the corresponding panel ID, determine the set of high-layer parameters for each panel.

15. The remote unit according to claim 14, wherein, The capabilities of the remote unit include the number of equipped panels and / or the number of activated panels.

16. The remote unit according to claim 13, wherein the processor is further configured to:[[]] Receive a fourth message from the base station unit, the fourth message including a configuration related to one or more downlink reference signal (DL-RS) resource groups, where the set of power control parameters is configured for each DL-RS resource group, and where the DL-RS is a channel state information reference signal (CSI-RS) and / or a synchronization signal block (SSB), and Based on the fourth message, determine, according to the transmit beam indication of each SRS resource, a set of power control parameters for each SRS resource.

Images