Enhanced upring power control

Abstract

An apparatus and system for uplink power control in multi-transmit / receive point (TRP) operation is described. Power control of sounding reference signals (SRS) to different TRPs is indicated in downlink control information (DCI). SRS power control adjustment state may be related to or separate from physical uplink shared channel (PUSCH) power control adjustment state to the TRP and may be indicated intrinsically based on order or extrinsically using additional bits in the DCI. Multiple SRS resource sets are transmitted for codebook-based transmission, which is used for mapping between SRS resource index (SRI) and path loss reference signals, spatial relations, P0 and alpha values.

Description

Technical Field

[0001] Claim of priority This application claims the benefit of priority of International Application No. PCT / CN2021 / 081025 filed on March 16, 2021, International Application No. PCT / CN2021 / 087373 filed on April 15, 2021, International Application No. PCT / CN2021 / 118257 filed on September 14, 2021, and International Application No. PCT / CN2021 / 124550 filed on October 19, 2021, which are hereby incorporated by reference in their entirety.

[0002] Technical field Embodiments relate to next generation (NG) wireless communications. In particular, some embodiments relate to uplink power control.

Background Art

[0003] The use and complexity of new radio (NR) wireless systems, including fifth generation (5G) networks and especially beginning to include sixth generation (6G) networks, are increasing due to both an increasing number of types of devices UE using network resources and the amount and bandwidth of data used by various applications such as video streaming operating on these UEs. The corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, is becoming increasingly complex due to a significant increase in the number and diversity of communication devices. As expected, there are many problems with the emergence of new technologies.

Brief Description of the Drawings

[0004] In the drawings, which are not necessarily drawn to scale, like numerals may describe like components in different figures. Like numerals with different suffixes may represent different examples of like components. The drawings generally illustrate, by way of example and not limitation, the various embodiments discussed in this document.

[0005] [Figure 1A] A diagram showing the architecture of a network according to some embodiments.

[0006] [Figure 1B] A diagram showing the architecture of a non - roaming 5G system according to some embodiments.

[0007] [Figure 1C] A diagram showing the architecture of a non - roaming 5G system according to some embodiments.

[0008] [Figure 2] A block diagram of a communication device according to some embodiments.

[0009] [Figure 3] A diagram showing the power control state of a sounding reference signal (SRS) according to some embodiments.

[0010] [Figure 4] A diagram showing another SRS power control state according to some embodiments.

[0011] [Figure 5] A diagram showing transmission of a transmission / reception point (TRP) according to some embodiments.

[0012] [Figure 6] A diagram showing another TRP transmission according to some embodiments.

[0013] [Figure 7] A diagram showing transmission of a TRP command according to some embodiments.

[0014] [Figure 8]This figure shows power control for SRS antenna switching in several configurations. [Modes for carrying out the invention]

[0015] The following description and drawings adequately illustrate specific embodiments so that those skilled in the art can implement them. Other embodiments may incorporate structural, logical, electrical, process, and other variations. Parts and features of some embodiments may be included in or replaced by parts and features of other embodiments. Embodiments described in the claims encompass all available equivalents of those claims.

[0016] Figure 1A shows network architectures in several embodiments. Network 140A includes 3GPP® LTE / 4G and NG network functions, which can be extended to 6G functionality. Therefore, although 5G is mentioned, it will be understood that it can be extended to 6G structures, systems, and functions as much as possible. Network functions can be implemented as individual network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtualized functions instantiated on an appropriate platform, such as dedicated hardware or cloud infrastructure.

[0017] Network 140A is shown to include user equipment (UE) 101 and UE102. UE101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing devices including wired and / or wireless communication interfaces. UE101 and 102 may be collectively referred to as UE101 in this specification, and UE101 can be used to perform one or more of the technologies disclosed herein.

[0018] Any of the radio links described herein (such as those used in, for example, network 140A or any other illustrated network) may operate in accordance with any exemplary radio communication techniques and / or standards. Any spectrum management scheme may include, for example, dedicated licensed spectra, unlicensed spectra, and (licensed) shared spectra (such as Licensed Shared Access (LSA) at 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz and other frequencies, and Spectrum Access System (SAS) at 3.55–3.7 GHz and other frequencies). Different single-carrier orthogonal frequency domain multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), particularly 3GPP NR, may be used by assigning OFDM carrier data bit vectors to corresponding symbolic resources.

[0019] In some embodiments, either UE101 or 102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. In some embodiments, either UE101 or 102 may include a Narrowband (NB) IoT UE (e.g., an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE, etc.). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with MTC servers or devices over a public land mobile network (PLMN), proximity-based service (ProSe), or device-to-device (D2D) communications, a sensor network, or an IoT network. The M2M or MTC exchange of data may be a machine-initiated data exchange. An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with ephemeral connections. IoT UEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity within the IoT network. In some embodiments, either UE 101 or 102 may include an extended MTC (eMTC) UE or a further extended MTC (FeMTC) UE.

[0020] UE101 and 102 may be configured to connect to a radio access network (RAN) 110, for example, to be communicatively coupled. RAN 110 may be, for example, an E-UTRAN (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network), an NG RAN (NextGen RAN), or any other type of RAN.

[0021] UE101 and 102 utilize connections 103 and 104, respectively, each including a physical communication interface or layer (described in more detail below), in which connections 103 and 104 are illustrated as air interfaces enabling communication coupling and can be matched with cellular communication protocols such as the Global System for Mobile Communications (GSM®) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5G protocol, 6G protocol, etc.

[0022] In one embodiment, UE101 and 102 may further exchange communication data directly via the ProSe interface 105. The ProSe interface 105 may also be referred to as a sidelink (SL) interface that includes one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink sharing channel (PSSCH), a physical sidelink discovery channel (PSDCH), a physical sidelink broadcast channel (PSBCH), and a physical sidelink feedback channel (PSFCH).

[0023] UE102 is shown to be configured to access access point (AP) 106 via connection 107. Connection 107 can include a local radio connection, such as a connection that matches any IEEE 802.11 protocol, and accordingly, AP106 can include a Wireless Fidelity (WiFi®) router, for example. In this example, AP106 is shown to connect to the internet without connecting to the core network of the radio system (described in more detail below).

[0024] RAN110 may include one or more access nodes that enable connections 103 and 104. These access nodes (ANs) may be called base stations (BS), node B, evolved node B (eNB), next-generation (5th or 6th generation) node B (gNB), RAN nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some embodiments, communication nodes 111 and 112 may be transmit / receive points (TRPs). In the example, when communication nodes 111 and 112 are node B (e.g., eNB or gNB), one or more TRPs may function within the communication cell of node B. RAN110 may include one or more RAN nodes to provide macrocells, e.g., macroRAN node 111, and one or more RAN nodes to provide femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low-power (LP) RAN node 112.

[0025] Either RAN node 111 or 112 can terminate the air interface protocol and serve as the initial point of contact for UEs 101 and 102. In some embodiments, either RAN node 111 or 112 can perform various logical functions for RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and radio network controller (RNC) functions such as mobility management. In one example, either node 111 and / or 112 can be a gNB, eNB, or another type of RAN node.

[0026] RAN110 is shown to be communicably coupled to the core network (CN) 120 via the S1 interface 113. In various embodiments, CN120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN (for example, as illustrated in relation to Figures 1B-1C). In this embodiment, the S1 interface 113 is divided into two parts: the S1-U interface 114, which carries traffic data between RAN nodes 111 and 112 and the service gateway (S-GW) 122, and the S1-Mobility Management Entity (MME) interface 115, which is a signaling interface between RAN nodes 111 and 112 and the MME 121.

[0027] In this embodiment, CN120 includes MME121, S-GW122, Packet Data Network (PDN) Gateway (P-GW)123, and Home Subscriber Server (HSS)124. MME121 may have functions similar to the control plane of a Legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME121 may manage mobility aspects of access, such as gateway selection and tracking area list management. HSS124 may include a database for network users, including subscriber-related information to support the processing of communication sessions of network entities. CN120 may include one or more HSS124s depending on the number of mobile subscribers, equipment capacity, network configuration, etc. For example, an HSS124 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0028] S-GW122 may terminate the S1 interface 113 toward RAN110 and may route data packets between RAN110 and CN120. In addition, S-GW122 may be a local mobility anchor point for inter-RAN node handover and may also provide an anchor for 3GPP inter-mobility. Other responsibilities of S-GW122 may include lawful intercept, charging, and any policy enforcement.

[0029] P-GW123 may terminate its SGI interface toward the PDN. P-GW123 may route data packets between CN120 and an external network, such as a network containing the application server 184 (also called an application function (AF)), via the Internet Protocol (IP) interface 125. P-GW123 may also communicate data to an external network 131A, which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element that provides applications that use IP bearer resources together with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, P-GW123 is shown to be communicably coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services for UE101 and 102 via CN120 (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0030] P-GW123 may also be a node for policy enforcement and billing data collection. Policy and billing rule function (PCRF)126 is the policy and billing control element of CN120. In non-roaming scenarios, in some embodiments, a single PCRF may exist within the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local breakout of traffic, two PCRFs may exist associated with the UE's IP-CAN: namely, a Home PCRF (H-PCRF) within the HPLMN and a V-PCRF (Visited PCRF) within the VPLMN (Visited Public Land Mobile Network). PCRF126 may be communicably coupled to the application server 184 via P-GW123.

[0031] In some embodiments, the communication network 140A may be a 5G or 6G network, including an IoT network or a new 5G radio network that uses communications in licensed (5G NR) and unlicensed (5G NR-U) spectrums. One of the things that enables the current IoT is narrowband IoT (NB-IoT). Operations in the unlicensed spectrum may include dual-connection (DC) operations and standalone LTE systems in the unlicensed spectrum, and accordingly, LTE-based technology operates only in the unlicensed spectrum without using an "anchor" in the unlicensed spectrum called MulteFire. Further enhanced operations in LTE systems in both licensed and unlicensed spectrums are expected in future releases and 5G systems. Such enhanced operations may include technologies for sidelink resource allocation and UE processing behavior for NR sidelink V2X communications.

[0032] The NG system architecture (or 6G system architecture) may include a RAN110 and a 5G core network (5GC)120. The NG-RAN110 may include multiple nodes such as gNBs and NG-eNBs. The CN120 (e.g., 5G core network / 5GC) may include access and mobility functions (AMF) and / or user plane functions (UPF). The AMF and UPF can be communicatively coupled to the gNB and NG-eNB via NG interfaces. More specifically, in some embodiments, the gNB and NG-eNB can be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNB and NG-eNB can be coupled to each other via an Xn interface.

[0033] In some embodiments, the NG system architecture can use reference points between various nodes. In some embodiments, the gNB and NG-eNB can be implemented as base stations, mobile edge servers, small cells, home eNBs, etc. In some embodiments, the gNB can be the master node (MN) in a 5G architecture, and the NG-eNB can be the secondary node (SN).

[0034] Figure 1B shows a non-roaming 5G system architecture in several embodiments. In particular, Figure 1B shows a 5G system architecture 140B in reference point representation, which can be extended to a 6G system architecture. More specifically, UE 102 can communicate with RAN 110 and one or more other 5GC network entities. The 5G system architecture 140B includes several network functions (NFs) such as AMF 132, Session Management Function (SMF) 136, Policy Control Function (PCF) 148, Application Function (AF) 150, UPF 134, Network Slice Selection Function (NSSF) 142, Authentication Server Function (AUSF) 144, and Unified Data Management (UDM) / Home Subscriber Server (HSS) 146.

[0035] UPF134 can provide connectivity to the data network (DN) 152, which may include, for example, operator services, internet access, or third-party services. AMF132 can be used to manage access control and mobility, and may also include network slice selection functionality. AMF132 can provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. SMF136 can be configured to set up and manage various sessions according to network policies. Therefore, SMF136 may be involved in session management and the assignment of IP addresses to UEs. SMF136 may also select and control UPF134 for data transfer. SMF136 may be associated with a single session of UE101 or multiple sessions of UE101. That is, UE101 may have multiple 5G sessions. Different SMFs can be assigned to each session. The use of different SMFs may allow each session to be managed individually. As a result, the functionality of each session may be independent of each other.

[0036] UPF134 can be deployed in one or more configurations depending on the desired service type and can be connected to a data network. PCF148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in 4G communication systems). UDM can be configured to store subscriber profiles and data (similar to HSS in 4G communication systems).

[0037] AF150 may provide information about packet flow to PCF148, which is involved in policy control to support the desired QoS. PCF148 may set mobility and session management policies for UE101. For this purpose, PCF148 may use the packet flow information to determine appropriate policies for the proper operation of AMF132 and SMF136. AUSF144 may store data for UE authentication.

[0038] In some embodiments, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B, as well as several IP multimedia core network subsystem entities such as a call session control function (CSCF). More specifically, the IMS 168B includes a CSCF, which can operate as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not shown in Figure 1B), or a query CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session states in the network, and the E-CSCF can be configured to handle specific aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. The I-CSCF166B can be configured to function as a contact point for all IMS connections directed to the network operator's subscribers or roaming subscribers currently located within the network operator's service area, within the operator's network. In some embodiments, the I-CSCF166B can be connected to another IP multimedia network 170E, for example, an IMS operated by a different network operator.

[0039] In some embodiments, the UDM / HSS146 can be coupled to an application server 160E, which may include a telephone application server (TAS) or another application server (AS). The AS160B can be coupled to the IMS168B via the S-CSCF164B or I-CSCF166B.

[0040] Reference point representations indicate that there may be interactions between corresponding NF services. For example, Figure 1B shows the following reference points: namely, N1 (between UE102 and AMF132), N2 (between RAN110 and AMF132), N3 (between RAN110 and UPF134), N4 (between SMF136 and UPF134), N5 (between PCF148 and AF150, not shown), N6 (between UPF134 and DN152), N7 (between SMF136 and PCF148, not shown), N8 (between UDM146 and AMF132, not shown), N9 (between two UPF134s, not shown), N10 (between UDM146 and SMF136) N11 (between AMF132 and SMF136, not shown), N12 (between AUSF144 and AMF132, not shown), N13 (between AUSF144 and UDM146, not shown), N14 (between two AMF132s, not shown), N15 (between PCF148 and AMF132 in non-roaming scenarios, or between PCF148, the destination network and AMF132 in roaming scenarios, not shown), N16 (between two SMFs, not shown), and N22 (between AMF132 and NSSF142, not shown). Other reference point representations not shown in Figure 1B can also be used.

[0041] Figure 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in Figure 1B, the system architecture 140C may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, the 5G system architecture can be service-based, and interactions between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0042] In some embodiments, as shown in Figure 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access those services. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (service-based interface presented by AMF132), Nsmf 158I (service-based interface presented by SMF136), Nnef 158B (service-based interface presented by NEF154), Npcf 158D (service-based interface presented by PCF148), Nudm 158E (service-based interface presented by UDM146), Naf 158F (service-based interface presented by AF150), Nnrf 158C (service-based interface presented by NRF156), Nnssf 158A (service-based interface presented by NSSF142), and Nausf 158G (service-based interface presented by AUSF144). Other service-based interfaces not shown in Figure 1C (e.g., Nudr, N5g-eir, and Nudsf) can also be used.

[0043] The NR-V2X architecture supports highly reliable, low-latency sidelink communications with various traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The technologies disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0044] Figure 2 shows block diagrams of communication devices according to several embodiments. The communication device 200 may be a dedicated computer, a personal computer or laptop computer (PC), a UE such as a tablet PC or smartphone, a dedicated network device such as an eNB, a server running software that configures the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in Figures 1A to 1C. Note that the communications described herein may be encoded before transmission by a transmitting entity (e.g., UE, gNB) for reception by a receiving entity (e.g., gNB, gNB) and decoded after reception by the receiving entity.

[0045] The embodiments described herein may include or operate on logic or a set of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing a specified operation and may be configured or arranged in a particular manner. In one example, a circuit may be arranged in a manner designated as a module (e.g., internally or relative to an external entity such as another circuit). In one example, one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors, in whole or in part, may be configured by firmware or software (e.g., instructions, application parts, or applications) as modules that operate to perform a specified operation. In one example, the software may reside on a machine-readable medium. In one example, the software, when executed by the underlying hardware of the module, causes the hardware to perform a specified operation.

[0046] Accordingly, the terms “module” (and “component”) are understood to encompass tangible entities, that is, entities that are physically constructed, specifically configured (e.g., hardwired) or temporarily configured (e.g., transiently) (e.g., programmed) to operate in a specified manner or to perform some or all of the operations described herein. Considering an example where a module is temporarily configured, each module does not need to be instantiated at once. For example, if a module includes a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as different modules at different times. Thus, software may configure a hardware processor to, for example, configure a particular module at one point in time and different modules at different points in time.

[0047] The communication device 200 may include a hardware processor (or equivalent processing circuit) 202 (e.g., a central processing unit (CPU), GPU, hardware processor core, or any combination thereof), main memory 204, and static memory 206, some or all of which may communicate with each other via an interlink (e.g., a bus) 208. The main memory 204 may include any or all of removable and non-removable storage, volatile memory, or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In one example, the display unit 210, the input device 212, and the UI navigation device 214 may be touchscreen displays. The communication device 200 may further include a storage device (e.g., a drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a Global Positioning System (GPS) sensor, a compass, an accelerometer, or other sensors. The communication device 200 may further include an output controller, such as a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near-field communication (NFC), etc.) connection) for communicating with or controlling one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0048] The storage device 216 may include a non-temporary machine-readable medium 222 (hereinafter simply referred to as the machine-readable medium) on which one or more sets of data structures or instructions 224 (e.g., software) that embody or utilize one or more of the technologies or functions described herein are stored. The instructions 224 may also reside, all or at least partially, in the main memory 204, in the static memory 206, and / or in the hardware processor 202 while being executed by the communication device 200. Although the machine-readable medium 222 is illustrated as a single medium, the term “machine-readable medium” may include a single or multiple mediums (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224.

[0049] The term “machine-readable medium” may include any medium capable of storing, encoding, or carrying instructions for execution by the communication device 200, and causing the communication device 200 to execute one or more of the technologies of this disclosure, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable mediums may include solid memory, optical and magnetic media. Specific examples of machine-readable mediums may include non-volatile memory such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks.

[0050] Instruction 224 may further be transmitted and received over a communication network using the transmission medium 226 via the network interface device 220, utilizing one of several wireless local area network (WLAN) transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmit Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Exemplary communication networks may include, among others, local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), plain old telephone (POTS) networks, and wireless data networks. Communication over a network may include one or more different protocols such as the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard family known as Wi-Fi, the IEEE 802.16 standard family known as WiMAX, the IEEE 802.15.4 standard family, the LTE (Long Term Evolution) standard family, the UMTS (Universal Mobile Telecommunications System) standard family, P2P (peer-to-peer) networks, and next-generation (NG) / fifth-generation (5G). For example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet®, coaxial, or telephone jacks) or one or more antennas for connecting to the transmission medium 226.

[0051] It should be noted that, as used herein, the term “circuit” refers to, is part of, or includes, hardware components configured to provide the functionality described, such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), and digital signal processors (DSPs). In some embodiments, a circuit may run one or more software or firmware programs to provide at least some of the functionality described. The term “circuit” may also refer to a combination of program code used to perform the functionality of that program code and one or more hardware elements (or a combination of circuits used in an electrical or electronic system). In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

[0052] Therefore, as used herein, the terms “processor circuit” or “processor” refer to, part of, or include a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The terms “processor circuit” or “processor” may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs) single-core or multi-core processors, and / or any other devices capable of executing or otherwise operating computer executable instructions such as program code, software modules, and / or functional processes.

[0053] Any of the radio links described herein may operate in accordance with one or more of the following wireless communication technologies and / or standards, including, but not limited to, the following: namely, GSM® (Global System for Mobile Communications) wireless communication technology, GPRS (General Packet Radio Service) wireless communication technology, EDGE (Enhanced Data Rates for GSM Evolution) wireless communication technology and / or 3GPP® (Third Generation Partnership Project) wireless communication technology, e.g., UMTS (Universal Mobile Telecommunications System), FOMA (Freedom of Multimedia Access), 3GPP LTE (Long Term Evolution), 3GPP LTE Advanced (Long Term Evolution Advanced), CDMA2000 (Code division multiple access 2000), CDPD (Cellular Digital Packet Data), Mobitex, 3G (Third Generation), CSD (Circuit Switched Data), HSCSD (High-Speed ​​Circuit-Switched Data), UMTS(3G)) (Universal Mobile Telecommunications System (Third Generation) Generation)), W-CDMA(UMTS)(Wideband Code Division Multiple Access (Universal Mobile Telecommunications System)), HSPA(High Speed ​​Packet Access), HSDPA(High-Speed ​​Downlink Packet Access), HSUPA(High-Speed ​​Uplink Packet Access), HSPA+(High Speed ​​Packet Access Plus), UMTS-TDD(Universal Mobile TelecommunicationsSystem-Time-Division Duplex, TD-CDMA (Time Division-Code Division Multiple Access), TD-CDMA (Time Division-Synchronous Code Division Multiple Access), 3GPP Rel.8 (Pre-4G) (3rd Generation Partnership Project Release 8 (Pre-4th Generation)), 3GPP Rel.9 (3rd Generation Partnership Project Release 9), 3GPP Rel.10 (3rd Generation Partnership Project Release 10), 3GPP Rel.11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel.13 (3rd Generation Partnership Project Release 13), 3GPP Rel.14 (3rd Generation Partnership Project Release 14), 3GPP Rel.15 (3rd Generation Partnership Project Release 15), 3GPP Rel.16 (3rd Generation Partnership Project Release 16), 3GPP Rel.17 (3rd Generation Partnership Project Release 17) and subsequent releases (Rel.18, Rel.19, etc.), 3GPP 5G, 5G, 5G NR (5G New Radio), 3GPP 5G new radio, 3GPP LTE Extra, LTE-Advanced Pro, LAA (LTE Licensed-Assisted Access), MuLTEfire, UTRA (UMTS Terrestrial Radio Access), E-UTRA (Evolved UMTS Terrestrial Radio Access), LTEAdvanced(4G)(Long Term Evolution Advanced (4th Generation))、cdmaOne(2G)、CDMA2000(3G)(Code division multiple access 2000 (Third generation))、EV-DO(Evolution-Data Optimized or Evolution-Data Only)、AMPS(1G)(Advanced Mobile Phone System (1st Generation))、TACS / ETACS(Total Access Communication System / Extended Total Access Communication System)、D-AMPS(2G)(Digital AMPS (2nd Generation))、PTT(Push-to-talk)、MTS(Mobile Telephone System)、IMTS(Improved Mobile Telephone System)、AMTS(Advanced Mobile Telephone System)、OLT(Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony)、MTD(Swedish abbreviation for Mobiltelefonisystem D or Mobile telephony system D)、Autotel / PALM(Public Automated Land Mobile)、ARP(Finnish for Autoradiopuhelin, "car radio phone")、NMT(Nordic Mobile Telephony)、Hicap(High capacity version of NTT (Nippon Telegraph and Telephone))、CDPD(Cellular Digital Packet Data)、Mobitex、DataTAC、iDEN(Integrated Digital Enhanced Network)、PDC(Personal Digital Cellular)、CSD(CircuitSwitched Data), PHS (Personal Handy-phone System), WiDEN (Wideband Integrated Digital Enhanced Network), iBurst, UMA (Unlicensed Mobile Access), also known as 3GPP Generic Access Network (GAN standard), Zigbee (registered trademark), Bluetooth (registered trademark), WiGig (Wireless Gigabit Alliance) standard, mmWave standard (wireless systems operating in the 10-300GHz range, such as WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating in the 300GHz and above THz range, (3GPP / LTE-based or IEEE 802.11p or IEEE 802.11bd and others) vehicle-to-vehicle (V2V), vehicle-to-X, vehicle-to-infrastructure (V2I), and infrastructure-to-vehicle (I2V) communication technologies, 3GPP Cellular V2X, DSRC (Dedicated Short Range European ITS-G5 systems (i.e., ITS-G5A (i.e., ITS-G5 operation in the European ITS frequency band dedicated to ITS for safety-related applications in the frequency range of 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., ITS operation in the European ITS frequency band dedicated to non-safety applications in the frequency range of 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., ITS operation in the frequency range of 5,470 GHz to 5,725 GHz), including European flavors of IEEE 802.11p-based DSRC (European ITS-G5A (i.e., ITS-G5 operation in the European ITS frequency band dedicated to ITS for safety-related applications in the frequency range of 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., ITS operation in the European ITS frequency band dedicated to non-safety applications in the frequency range of 5,855 GHz to 5,875 GHz), and ITS-G5C (i.e., ITS operation in the frequency range of 5,470 GHz to 5,725 GHz)).Japanese DSRC and IEEE 802.11bd-based systems in the 700MHz band (including 715MHz-725MHz).

[0054] The embodiments described herein may be used in the context of any spectrum management scheme, including dedicated licensed spectra, unlicensed spectra, license-exempt spectra, and (licensed) shared spectra (LSA = licensed shared access in 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz and further frequencies, and SAS = spectrum access system / CBRS = Citizen Broadband Radio System in 3.55–3.7 GHz and further frequencies).Applicable spectral bands include: IMT (International Mobile Telecommunications) spectrum, as well as other types of spectrum / bands, such as nationally allocated bands (450-470 MHz, 902-928 MHz (Note: allocated in the US (FCC Part 15), for example), 863-868.6 MHz (Note: allocated in the European Union (ETSI EN 300 220), for example), 915.9-929.7 MHz (Note: allocated in Japan, for example), 917-923.5 MHz (Note: allocated in South Korea, for example), 755-779 MHz and 779-787 MHz (Note: allocated in China, for example), 790-960 MHz, 1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz) MHz, 2.4~2.4835GHz (Note: These are globally available ISM bands, also used by the Wi-Fi technology family (11b / g / n / ax) and Bluetooth®), 2500~2690MHz, 698~790MHz, 610~790MHz, 3400~3600MHz, 3400~3800MHz, 3800~4200MHz, 3.55~3.7GHz (Note: For example, allocated in the United States for citizen broadband wireless services), 5.15~5.25GHz and 5.25~5.35GHz and 5.47~5.725GHz and 5.725~5.85GHz bands (Note: For example, allocated in the United States (FCC part 15)), consisting of four U-NII bands totaling 500MHz of spectrum), 5.725~5.875GHz (Note: For example, allocated in the European Union (ETSI EN) The 5.47-5.65GHz band (as allocated in 301 893), 5925-7125MHz and 5925-6425MHz bands (as allocated in the US and European Union respectively; next-generation Wi-Fi systems are expected to include the 6GHz spectrum as an operating band, but as of December 2017, Wi-Fi systems are not yet permitted in this band. Regulations are expected to be completed between 2019 and 2020).), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600~3800MHz, 3800~4200MHz, 3.5GHz band, 700MHz band, bands in the 24.25~86GHz range, etc.), spectrum made available under the FCC's "Spectrum Frontier" 5G concept (including 27.5~28.35GHz, 29.1~29.25GHz, 31~31.3GHz, 37~38.6GHz, 38.6~40GHz, 42~42.5GHz, 57~64GHz, 71~76GHz, 81~86GHz and 92~94GHz, etc.), 5.9GHz ITS (Intelligent Transport Systems) band (typically 5.85~5.925GHz) and 63~64GHz, band currently allocated to WiGig (e.g., WiGig Band 1 (57.24~59.40GHz), WiGig Band 2 (59.40~61.56GHz), WiGig Band 3 (61.56~63.72GHz), WiGig Band 4 (63.72~65.88GHz), 57~64 / 66GHz (Note: This band has a near-global designation for MGWS (Multi-Gigabit Wireless Systems) / WiGig). The United States (FCC part 15) has allocated a total of 14GHz spectrum, while the European Union (ETSI EN 302 567 and ETSI EN 301 for fixed P2P) 217-2) allocates a total of 9 GHz spectrum, including the 70.2 GHz–71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76–81 GHz, and future bands including 94–300 GHz and above. The scheme can be secondarily used for bands such as the TV white space band (typically below 790 MHz), where the 400 MHz and 700 MHz bands are particularly promising candidates. In addition to cellular applications, it can address specific applications in vertical markets such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low latency, and drone applications.

[0055] The embodiments described herein can also be implemented to enable hierarchical application of the scheme by introducing hierarchical prioritization of use for different types of users (e.g., low / medium / high priority, etc.) based on prioritized access to the spectrum, such as highest priority for Tier 1 users, then priority for Tier 2 users, then priority for Tier 3 users, and so on.

[0056] The embodiments described herein can also be applied to different single-carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multi-carrier (FBMC), OFDMA, etc.), particularly 3GPP NR (New Radio), by assigning OFDM carrier data bit vectors to corresponding symbolic resources.

[0057] While some functions such as AP, eNB, NR, or gNB are defined on the network side, it should be noted that these terms are typically used in the context of 3GPP 5G and 6G communication systems. Furthermore, UEs can also fulfill this role and function as APs, eNBs, or gNBs; that is, some or all of the functions defined for network equipment can be implemented by the UE.

[0058] As described above, the NR Rel-15 specification supports various types of SRS resource sets. An SRS resource set is configured with a parameter called "usage," which can be set to "beamManagement," "codebook," "nonCodebook," or "antennaSwitching." SRS resource sets configured for "beamManagement" are used for beam acquisition and uplink beam indication using SRS. SRS resource sets configured for "codebook" and "nonCodebook" are used to determine UL precoding by explicit indication via the transmission precoding matrix index (TPMI) or implicit indication via the SRS resource index (SRI). Finally, SRS resource sets configured for "antennaSwitching" are used to acquire DL channel status information (CSI) using SRS measurements at the UE by leveraging the interrelationships of channels in a time-domain duplex (TDD) system. In SRS transmission, time-domain behavior can be periodic, semi-persistent, or aperiodic. The RRC configurations for SRS resource sets are as follows: [Table 1]

[0059] When an SRS resource set is configured as "aperiodic," the SRS resource set also includes a trigger state configuration (aperiodicSRS-ResourceTrigger, aperiodicSRS-ResourceTriggerList). The trigger state defines which downlink control information (DCI) code points trigger the corresponding SRS resource set transmission.

[0060] Aperiodic SRS can be triggered via an SRS request field within the DCI. The SRS request field can be carried by DCI formats 0_1 / 0_2 / 1_1 / 1_2 / 2_3. Note that DCI formats 0_1 / 0_2 are used for scheduling physical uplink shared channels (PUSCH), DCI formats 1_1 / 1_2 are used for scheduling physical downlink shared channels (PDSCH), and DCI format 2_3 is used to trigger aperiodic SRS for groups of UEs.

[0061] In the RRC configuration, the parameter srs-PowerControlAdjustmentStates defines whether the SRS power control state should follow PUSCH or be separate from PUSCH. If the parameter srs-PowerControlAdjustmentStates is not present, the SRS power control should follow the first PUSCH power control adjustment state, i.e., h b,f,c =f b,f,c (i,0). If the parameter srs-PowerControlAdjustmentStates exists and its value is sameAsFci2, then the SRS power control should follow the second PUSCH power control adjustment state, i.e., h b,f,c =f b,f,c (i,1). If the parameter srs-PowerControlAdjustmentStates exists and its value is separateClosedLoop, then the SRS power control consists of separate power control states.

[0062] The output power of the pusher is given by the following formula:

number

[0063] The parameters are as follows: b: UL BWP index; f: Carrier index; c: Serving cell; j: Parameter set configuration index; l: PUSCH power control adjustment state index; i: PUSCH transmission occasion; q d : Reference signal index used for path loss calculation corresponding to different beams. Generally, each component in the formula is as follows: P CMAX : UE maximum output power; P 0_PUSCH : Target that received the PUSCH power; M: Bandwidth in terms of resource blocks; α: Path loss compensation coefficient; PL: Path loss (beam specific); Δ: Adjustment according to MCS; f[[ID=?]] b,f,c (i, l): Adjustment according to the transmission power control (TPC) command from the gNB, where l ∈ {0, 1}.

[0064] Similarly, the output power of the SRS is derived as follows:

Equation

[0065] The parameters are as follows:

[0066] The parameters are as follows: b: UL BWP index; f: Carrier index; c: Serving cell; q s : SRS resource set ID; l: SRS power control adjustment state index; i: SRS transmission occasion; q d : Reference signal index used for path loss calculation corresponding to different beams. For SRS power control, each component in the formula is as follows: P CMAX : UE maximum output power; P 0_SRS : Target that received the SRS power; M: Bandwidth in terms of resource blocks; α: Path loss compensation coefficient; PL: Path loss (beam specific); h b,f,c (i, l): Adjustment according to the TPC command from the gNB. The power control adjustment state for SRS may be the same as or different from that of PUSCH.

[0067] However, several issues arise with this. In Release 17, it is agreed that SRS can be triggered by DCI format 0_1 / 0_2 without a scheduling PUSCH. In this case, since no PUSCH is sent, a separate power control state can be applied to the SRS. However, in multi-TRP operations, the UE may be configured with two sets of SRS resources for codebook / non-codebook based transmissions. If multiple sets of SRS resources destined for different TRPs are triggered via the same DCI, the same separate power control state will be applied, which is undesirable because the SRS transmissions are destined for different TRPs.

[0068] Figure 3 shows SRS power control states in several embodiments. In particular, Figure 3 shows SRS power control states related to DCI 0_1 / 0_2 without scheduling pushes, illustrating the problems associated with multiple TRP configurations. In addition, for SRS triggered by DCI format 0_1 / 0_2 without scheduling pushes, there should be two TPC commands, and dynamic switching between a single TRP and multiple TRPs should also be supported.

[0069] In multi-TRP operation scenarios, the same issue may be observed with SRS triggered by DCI format 2_3.

[0070] Another issue with multi-TRP operation involves supporting dynamic switching between single-TRP and multi-TRP. For SRS triggered by DCI format 0_1 / 0_2 scheduling a PUSCH, if the DCI schedules a PUSCH transmission for only one TRP, but the SRS request triggers SRS transmissions for two TRPs, the power control state for the SRS can become problematic. Figure 4 shows different SRS power control states in several embodiments.

[0071] For example, consider the case of a UE composed of SRS resource sets A and B. SRS resource set A is the same as the first PUSCH power control state, i.e., f b,f,c (i,0) is configured with the same power control state, and SRS resource set B is the same as the second PUSCH power control state, i.e., f b,f,c If a DCI configured in the same power control state as (i,1) and scheduling a PUSCH transmission to the first TRP (TRP#1, corresponding to the first PUSCH power control state) also triggers both SRS resource sets A and B, then the question is whether SRS resource set B follows the second PUSCH power control state, because PUSCH is not transmitted to the second TRP. Figure 4 shows the SRS power control states for DCI 0_1 / 0_2 scheduling PUSCH.

[0072] In addition, the UE may consist of two power control states (l ∈ {0, 1}) for push transmission in multi-TRP operation. Which power control state is applied can be determined by a mapping between the SRI and power control state l. In this case, the mapping is provided by the RRC parameter sri-PUSCH-ClosedLoopIndex in SRI-PUSCH-PowerControl: [Table 2]

[0073] However, Rel-17 agrees that the maximum number of SRS resource sets for codebook / non-codebook-based transmissions in multi-TRP operations is two. This means that transmissions to different TRPs are distinguished by different SRS resource sets. For example, the first SRS resource set corresponds to the first TRP, and the second SRS resource set corresponds to the second TRP. In this case, the PUSCH power control state should be derived from a different SRS resource set than the SRI. Therefore, methods for enhancing SRS and PUSCH power control to support multi-TRP operations are presented herein.

[0074] Scenario A: SRS triggered by DCI format 0_1 / 0_2 without PUSCH scheduling

[0075] In some embodiments, for a single TRP operation, when the SRS is triggered by DCI format 0_1 / 0_2 without a scheduling push, the TPC commands carried within the DCI are applied to SRS power control. An example of a specification change is shown below. For SRS power control in section 7.3.1 of TS 38.213 v16.4.0, it is as follows:

[0076] Regarding the SRS power control adjustment state for the active UL BWP b and SRS transmission opportunity i of the carrier f of serving cell c: If srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS and PUSCH transmissions, and SRS is triggered by DCI format 0_1 / 0_2 which schedules PUSCH, h b,f,c (i,l=f b,f,c (i,l) and here, f b,f,c (i,l) is in the current PUSCH power control adjustment state as described in Section 7.1.1; or If srs-PowerControlAdjustmentState indicates the same power control adjustment state for SRS transmission and PUSCH transmission, and SRS is triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, and tpc-Accumulation is not provided, then the following applies:

number

[0077] Here, δ SRS,b,f,c The values ​​are given in Table 7.1.1-1.

[0078] δ SRS,b,f,c (m) is a TPC command included in DCI format 0_1 / 0_2 without PUSCH scheduling.

[0079] If srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS transmission and PUSCH transmission, and SRS is triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, and tpc accumulation is provided, h b,f,c (i) = δ SRS,b,f,c (i) is the case.

[0080] If the UE is not configured for push transmission of the active UL BWP b of carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and push transmission, and tpc accumulation is not provided, then:

number

[0081] Here, δ SRS,b,f,cThe values ​​are given in Table 7.1.1-1.

[0082] δ SRS,b,f,c (m) is coded together with other TPC commands in the PDCCH of DCI format 2_3, as described in Section 11.4.

[0083] ...

[0084] In some embodiments, in multi-TRP operation, the SRS power control state is extended to include two power control adjustment states separate from the PUSCH. The two separate power control states may apply to the SRS power control when the SRS is triggered by DCI format 0_1 / 0_2 without scheduling of the PUSCH. The SRS power control state may be one of the following: the same power control state as the first PUSCH power control adjustment state, the same power control state as the second PUSCH power control adjustment state, a first power control state separate from the PUSCH, or a second power control state separate from the PUSCH.

[0085] For example, the value of srs-PowerControlAdjustmentStates could be {sameAsFci2, separateClosedLoop-1, separateClosedLoop-2}. If the parameter srs-PowerControlAdjustmentStates does not exist, the SRS power control should follow the first PUSCH power control adjustment state, i.e., h b,f,c =f b,f,c (i,0). If the parameter srs-PowerControlAdjustmentStates exists and its value is sameAsFci2, then the SRS power control should follow the second PUSCH power control adjustment state, i.e., h b,f,c =f b,f,c(i,1). If the parameter srs-PowerControlAdjustmentStates exists and its value is separateClosedLoop-1, the SRS is configured with a separate first power control state. If the parameter srs-PowerControlAdjustmentStates exists and its value is separateClosedLoop-2, the SRS is configured with a separate second power control state.

[0086] Example of specification changes for SRS power control in Section 7.3.1 of TS38.213 v16.4.0:

[0087] Regarding the SRS power control adjustment state for the active UL BWP b and SRS transmission opportunity i of the carrier f of serving cell c:

[0088] If srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS transmission and PUSCH transmission, h b,f,c (i,l=f b,f,c (i,l) and here, f b,f,c (i,l) indicates the current PUSCH power control adjustment state, as described in Section 7.1.1.

[0089] Alternatively, if the UE is not configured for push transmission of the active UL BWP b of carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and push transmission, and tpc accumulation is not provided, then:

number

[0090] Here, δ SRS,b,f,c The values ​​are given in Table 7.1.1-1.

[0091] δ SRS,b,f,c(m,l) is a TPC command value that is coded together with other TPC commands in a PDCCH of DCI format 2_3, as described in Section 11.4, or is included in DCI format 0_1 / 0_2 without PUSCH scheduling.

[0092] If the UE is not configured for push transmission of the active UL BWP b of the carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and push transmission, and tpc accumulation is provided, h b,f,c (i,l)=δ SRS,b,f,c (i,l) and UE is DCI format 2_3 or DCI format 0_1 / 0_2 without scheduling of PUSCH, K before the first symbol of SRS transmission opportunity i SRS,min The symbol is detected, and here, δ SRS,b,f,c The absolute value of is provided in Table 7.1.1-1.

[0093] In another embodiment, the SRS still uses the three existing power control adjustment states: the same power control state as the first PUSCH power control state, the same power control state as the second PUSCH power control state, and a power control state separate from PUSCH. When the SRS is triggered by DCI 0_1 / 0_2 without PUSCH scheduling, the DCI performs the SRS power control adjustment h b,f,c (i,l) should be considered. If the SRS is configured to be the same as the first push power control state, then l=0. If the SRS is configured to be the same as the second push power control state, then l=0.

[0094] An example of a specification change is shown below. Regarding SRS power control in Section 7.3.1 of TS38.213 v16.4.0, it is as follows:

[0095] Regarding the SRS power control adjustment state for the active UL BWP b and SRS transmission opportunity i of the carrier f of serving cell c:

[0096] If srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS and PUSCH transmissions, and SRS is triggered by DCI format 0_1 / 0_2 which schedules PUSCH, h b,f,c (i,l=f b,f,c (i,l) and here, f b,f,c (i,l) indicates the current PUSCH power control adjustment state, as described in Section 7.1.1.

[0097] Alternatively, if srs-PowerControlAdjustmentState indicates the same power control adjustment state for SRS transmission and PUSCH transmission, and SRS is triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, and tpc accumulation is not provided,

number

[0098] If srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS transmission and PUSCH transmission, and SRS is triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, and tpc accumulation is provided, h b,f,c (i,l)=δ SRS,b,f,c (i,l) is such that l=0 if srs-PowerControlAdjustmentStates is the same power control state as the first PUSCH power control state, and l=1 if srs-PowerControlAdjustmentStates is the same power control state as the second PUSCH power control state.

[0099] If the UE is not configured for push transmission on the active UL BWP b of the carrier f of serving cell c and the SRS transmission opportunity i, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and push transmission, and tpc accumulation is not provided,

number

[0100] In another embodiment, in an SRS triggered by DCI 0_1 / 0_2 without PUSCH scheduling, two TPC commands are included in DCI 0_1 / 0_2 during a multi-TRP operation. Each TPC command is applied to the SRS transmission destined for its respective TRP. Two TPC command fields may be included in the DCI, each containing one TPC command. Alternatively, only one TPC command field may be included in the DCI, with the code points of the DCI field indicating two TPC commands.

[0101] The application of TPC commands to SRS power control states can be implicit or explicit. In implicit indication, for example, a first TPC command is applied to an SRS transmission to a first TRP, i.e., to an SRS having a first power control state. A second TPC command is applied to an SRS transmission to a second TRP, i.e., to an SRS having a second power control state. The triggered SRS selects the corresponding TPC command according to its power control state configuration.

[0102] Figure 5 shows several embodiments of TRP transmission. In particular, Figure 5 shows an exemplary application of TPC with DCI 0_1 / 0_2 without PUSCH for indicating SRS. In explicit indication, an additional bit is added to indicate whether the TPC command is applied to the first SRS power control state or the second SRS power control state.

[0103] Dynamic switching between multi-TRP operation and single-TRP operation is also supported. In one example, two TPC commands are always included in the DCI. Whether a single TPC command or both TPC commands are applied is further determined by the power control state configuration of the triggered SRS. In another example, in DCI 0_1 / 0_2 without PUSCH scheduling, it is configurable whether a single TPC command or two TPC commands are included.

[0104] This embodiment may be applicable to both single DCI multi-TRP operations and multi-DCI multi-TRP operations. In another example, this embodiment may be applicable only to single DCI multi-TRP operations. In multi-DCI multi-TRP operations, only one TPC command is included in the DCI.

[0105] In another embodiment, for an SRS triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, unused fields may be reused to reconfigure the SRS parameters. One, some, or all of the following SRS power control parameters can be reconfigured via unused bits of DCI format 0_1 / 0_2 without PUSCH scheduling.

[0106] SRS Power Control Adjustment State - One of the applicable SRS power control adjustment states can be dynamically indicated via DCI. For example, the power control state for an RRC configuration for an SRS is the same as the first push power control state. In DCI, the state can be reconfigured as a different state, for example, a power control state separate from push or (if there are two separate power control states) a first separate power control state.

[0107] Path Loss Reference Signals - A list of path loss reference signals may be constructed by RRC. In DCI, applicable path loss reference signals may be indicated for SRS.

[0108] Spatial relationships - A list of spatial relationships may be constructed by RRC. In DCI, applicable spatial relationships may be indicated for SRS.

[0109] P0 and Alpha values ​​- A list of P0s and a list of Alphas, or a list of P0s and Alphas, may be constructed by the RRC. In the DCI, the applicable P0s and Alphas may be indicated for the SRS.

[0110] Note: This embodiment can be applied to both single TRP operation and multi-TRP operation.

[0111] In another embodiment, for an SRS triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, whether it is a multi-TRP operation or a single-TRP operation, only open-loop power control is applied to the triggered SRS, i.e., h b,f,c (i,l)=0.

[0112] In another example, for an SRS triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, the triggered SRS may consist of an alpha value and / or a P0 value, which implicitly means that open-loop power control is performed for the triggered SRS.

[0113] In another embodiment, for SRSs triggered by DCI format 0_1 / 0_2 without PUSCH scheduling, only SRSs having the same power control state as PUSCH can be triggered. In another alternative embodiment, SRSs having the same or different power control states as PUSCH can be triggered by DCI format 0_1 / 0_2 without PUSCH scheduling.

[0114] Scenario B: SRS triggered by DCI Format 2_3

[0115] In one embodiment, in a multi-TRP operation, for an SRS triggered by DCI format 2_3, the SRS power control may be extended to include two separate power control adjustment states from those of the PUSCH. The two separate power control adjustment states may be applied to the SRS power control when the SRS is triggered by DCI format 2_3. The SRS power control state may be one of the following: namely, the same power control state as the first PUSCH power control adjustment state, the same power control state as the second PUSCH power control adjustment state, a first power control state separate from the PUSCH power control state, or a second power control state separate from the PUSCH power control state.

[0116] For example, the value of srs-PowerControlAdjustmentStates could be {sameAsFci2, separateClosedLoop-1, separateClosedLoop-2}. In this case, if the parameter srs-PowerControlAdjustmentStates does not exist, the SRS power control should follow the first PUSCH power control adjustment state, i.e., h b,f,c =f b,f,c (i,0); if the parameter srs-PowerControlAdjustmentStates exists and its value is sameAsFci2, then the SRS power control should follow the second PUSCH power control adjustment state, i.e., h b,f,c =f b,f,c (i,1) If the parameter srs-PowerControlAdjustmentStates exists and its value is separateClosedLoop-1, the SRS is configured with a first separate power control state; if the parameter srs-PowerControlAdjustmentStates exists and its value is separateClosedLoop-2, the SRS is configured with a second separate power control state.

[0117] An example of a specification change is shown below. Regarding SRS power control in Section 7.3.1 of TS38.213 v16.4.0, it is as follows:

[0118] Regarding the SRS power control adjustment state for the active UL BWP b and SRS transmission opportunity i of the carrier f of serving cell c:

[0119] If srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS transmission and PUSCH transmission, h b,f,c (i,l=f b,f,c (i,l) and here, f b,f,c (i,l) indicates the current PUSCH power control adjustment state, as described in Section 7.1.1.

[0120] Alternatively, if the UE is not configured for push transmission of the active UL BWP b of carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and push transmission, and tpc accumulation is not provided, then:

number

[0121] Here, δ SRS,b,f,c The values ​​are given in Table 7.1.1-1.

[0122] δ SRS,b,f,c (m,l) is coded together with other TPC commands in the PDCCH of DCI format 2_3, as described in Section 11.4.

[0123] When srs-PowerControlAdjustmentStates indicates the first PUSCH power control state, l=0, and when srs-PowerControlAdjustmentStates indicates the second PUSCH power control state, l=1.

[0124] If the UE is not configured for push transmission of the active UL BWP b of the carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and push transmission, and tpc accumulation is provided, h b,f,c (i,l)=δ SRS,b,f,c (i,l) and UE is DCI format 2_3, or DCI format 0_1 / 0_2 without PUSCH scheduling, K before the first symbol of SRS transmission opportunity i SRS,min The symbol is detected, and here, δ SRS,b,f,c The absolute value of is provided in Table 7.1.1-1.

[0125] l=0 when srs-PowerControlAdjustmentStates indicates a first separate PUSCH power control state, and l=1 when srs-PowerControlAdjustmentStates indicates a second separate PUSCH power control state.

[0126] In another embodiment, for an SRS triggered by DCI 2_3, in a multi-TRP operation, there may be two TPC commands included in DCI 2_3. Each TPC command is applied to the SRS transmission destined for each TRP. Two TPC command fields may be included in the DCI, each containing one TPC command. Alternatively, only one TPC command field may be included in the DCI, and the code points of the DCI field may indicate two TPC commands.

[0127] The application of TPC commands to SRS power control states can be implicitly or explicitly indicated. In implicit indication, for example, a first TPC command is applied to an SRS transmission to a first TRP, i.e., to an SRS having a first power control state. A second TPC command is applied to an SRS transmission to a second TRP, i.e., to an SRS having a second power control state. The triggered SRS selects the corresponding TPC command according to the power control state configuration. Figure 6 shows different TRP transmissions in several embodiments. In particular, Figure 6 shows an exemplary application of TPC by DCI 2_3 to an SRS.

[0128] In explicit instructions, additional bits may be added to indicate whether the TPC command applies to the first SRS power control state or the second SRS power control state.

[0129] Dynamic switching between multi-TRP operation and single-TRP operation is also supported. In one example, two TPC commands are always included in DCI 2_3. Whether a single TPC command or both TPC commands are applied is further determined by the power control state configuration of the triggered SRS. In another example, in DCI 2_3 without PUSCH scheduling, it is configurable whether a single TPC command or two TPC commands are included.

[0130] This embodiment may be applicable to both single DCI multi-TRP operations and multi-DCI multi-TRP operations. Alternatively, this embodiment may be applicable only to single DCI multi-TRP operations, in which only one TPC command is included in the DCI.

[0131] In another embodiment, for an SRS triggered by DCI format 2_3, one, some, or all of the following SRS power control parameters can be reconfigured via unused bits of DCI format 2_3 to reconfigure the SRS.

[0132] SRS Power Control Adjustment State - One of the applicable SRS power control adjustment states can be dynamically indicated via DCI. For example, the power control state for an RRC configuration for an SRS is the same as the first push power control state. In DCI, the state can be reconfigured as a different state, for example, a power control state separate from push or (if there are two separate power control states) a first separate power control state.

[0133] Path Loss Reference Signals - A list of path loss reference signals may be constructed by RRC. In DCI, applicable path loss reference signals may be indicated for SRS.

[0134] Spatial relationships - A list of spatial relationships may be constructed by RRC. In DCI, applicable spatial relationships may be indicated for SRS.

[0135] P0 and Alpha values ​​- A list of P0s and a list of Alphas, or a list of P0s and Alphas, may be constructed by the RRC. In the DCI, the applicable P0s and Alphas may be indicated for the SRS.

[0136] This embodiment can be applied to both single-TRP and multi-TRP operations. In addition, having two power control states separate from PUSCH can be applied to some or all SRS uses, i.e., antenna switching, beam management, codebook / non-codebook. Having two power control states separate from PUSCH can be applied to some or all DCI formats that can trigger SRS, such as DCI 0_1 / 0_2 / 1_1 / 1_2 / 2_3.

[0137] Scenario C: SRS triggered by DCI format 0_1 / 0_2 with scheduling of PUSCH

[0138] In one embodiment, in a multi-TRP operation, for an SRS triggered by DCI format 0_1 / 0_2 with PUSCH scheduling, the DCI schedules a single TRP PUSCH transmission, but the same DCI triggers SRS transmissions toward multiple TRPs, which may result in inconsistencies in the application of TPC commands. In another case, the DCI schedules a single TRP transmission toward TRP#A, and the same DCI triggers an SRS transmission toward TRP#B.

[0139] For example, if there are always two TPC commands (TPC command #0 and #1) included in DCI for multi-TRP operation, TPC command #0 may be used for PUSCH / SRS transmissions directed to TRP #A (f b,f,c (i,0),h b,f,c (i,0)), TPC command #1 may be used for PUSCH / SRS transmission toward TRP#B (f b,f,c (i,1),h b,f,c (i,1)). If DCI only schedules a single TRP PUSCH transmission toward TRP#A, and the same DCI triggers an SRS toward a different TRP, namely TRP#B, then TPC command #0 applies to the PUSCH power control state toward TRP#A (and also to the SRS toward TRP#A if triggered). TPC command #1 is omitted by PUSCH but applies to the SRS power control state toward TRP#B, i.e., h b,f,c (i,1). Figure 7 shows several embodiments of TRP command transmission. In particular, Figure 7 shows exemplary applications of TPC commands to PUSCH and SRS. Alternatively, for SRS transmission toward TRP#B, only open-loop power control is applied, i.e., h b,f,c (i,1)=0.

[0140] In another example, if a DCI schedules only a single TRP push transmit, and only one TPC command is included in the DCI, then if the same DCI triggers an SRS directed to a different TRP, only open-loop power control will apply to the SRS transmit directed to a different TRP as a push. Alternatively, the TPC command may apply to the SRS transmit regardless of whether the transmit is directed to the same TRP or a different TRP.

[0141] In another embodiment, for DCI formats 0_1 / 0_2 with PUSCH scheduling, TPC commands carried in DCI may be interpreted as TPC commands for all uplink channels / signals (or at least for PUSCH and SRS), including PUSCH, PUCCH, and SRS. If two TPC commands are included in DCI, the first TPC command applies to all uplink channels / signals to the first TRP (PUSCH / PUCCH / SRS or at least PUSCH / SRS), and the second TPC command applies to all uplink channels / signals to the second TRP (PUSCH / PUCCH / SRS, or at least PUSCH / SRS). This embodiment may also apply to other DCI formats that schedule PUSCH and carry TPC commands, such as DCI formats 0_0 and DCI formats 2_2. For example, for an SRS transmission directed to a single TRP, the latest TPC command to be applied to the corresponding TRP should be used for SRS power control, which may be carried in DCI format 0_0 / 0_1 / 0_2 / 2_2 and received prior to the SRS transmission.

[0142] Scenario D: Push power control in multi-TRP environments

[0143] In one embodiment, the number of SRS resource sets is increased to two for codebook / non-codebook-based transmissions in multi-TRP operations. The DCI 0_1 / 0_2 scheduling the PUSCH includes two SRI fields, each SRI field indicating an SRS resource from a different SRS resource set. In this case, the PUSCH power control state may be explicitly or implicitly associated with a different SRS resource set, or may be explicitly / implicitly indicated by the first or second SRI field.

[0144] In one example, the order of SRIs can implicitly indicate the PUSCH power control state, with the first SRI applied to the first PUSCH power control state and the second SRI applied to the second PUSCH power control state. The first SRI indicates one SRS resource from an SRS resource set that has an SRS power control state set to match the first PUSCH power control state. The second SRI indicates one SRS resource from an SRS resource set that has an SRS power control state set to match the second PUSCH power control state.

[0145] Alternatively, the first SRI may indicate one SRS resource from an SRS resource set with a lower ID, and the second SRI may indicate one SRS resource from an SRS resource set with a higher ID. The PUSCH power control state may also be indicated by the SRS power control state of the corresponding SRS resource set. For example, for the first SRI, if the associated SRS resource set consists of the same resources as the second PUSCH power control state, then the first SRI applies to the second PUSCH power control state.

[0146] In another example, an SRS resource set may be explicitly configured with a new parameter indicating whether a first SRI or a second SRI in the DCI is used for the SRS resource set. The SRS power control state configured for the SRS resource set may further indicate a PUSCH power control state for an SRI. For example, SRS resource set #B is explicitly configured to use a first SRI, and SRS resource set #B is configured to be the same as the second PUSCH power control state. The first SRI is then applied to the second PUSCH power control state.

[0147] In one embodiment, the mapping between SRI and path loss RS / alpha / P0 for push power control should support configurations with multiple SRS resource sets in multi-TRP operation, i.e., TRP-specific push power control parameters should be defined.

[0148] For example, the parameters sri-PUSCH-PathlossReferenceRS-Id and sri-P0-PUSCH-AlphaSetId in RRC can have two values. The first value applies to the first PUSCH power control state, and the second value applies to the second PUSCH power control state. Alternatively, one additional sri-PUSCH-PathlossReferenceRS-Id and one additional sri-P0-PUSCH-AlphaSetId are included in SRI-PUSCH-PowerControl, which applies to the second PUSCH power control state. An example of modification to the RRC Information Element (IE) SRI-PUSCH-PowerControl is shown below. [Table 3]

[0149] In another example, two groups of SRI-PUSCH-PowerControl may be introduced for multi-TRP operation, one for each TRP. The first group of SRI-PUSCH-PowerControl applies to the first TRP (first PUSCH power control state), and the second group of SRI-PUSCH-PowerControl applies to the second TRP (second PUSCH power control state). An example of the modification is shown below. [Table 4]

[0150] When performing push power control, the UE first determines the push power control state according to the SRI field (the corresponding push power control state depending on whether it is the first or second SRI field). Next, for a given push power control state, the corresponding path loss RS, P0, and alpha are determined according to the SRI code point and the push power control state.

[0151] Scenario E: SRS power control parameter update

[0152] In one embodiment, for an SRS in multi-TRP operation, a media access control-control element (MAC-CE) may be introduced to update one, some, or all of the following parameters: namely, the SRS power control adjustment state or SRS closed-loop power control index, path loss reference signal, spatial relationship, P0 value, and alpha value.

[0153] MAC-CE can be used to update the above SRS parameters for one, some, or all of the following types of SRS: aperiodic, semi-persistent, and periodic SRS.

[0154] MAC-CE can be used to update the above SRS parameters for one, some, or all of the following uses of SRS: namely, codebook, non-codebook, antenna switching, and beam management.

[0155] MAC-CE can be used to update the above SRS parameters for one or more SRS resource sets. Alternatively, MAC-CE can be used to update the above SRS parameters for one or more SRS resources within a single SRS resource set. For example, one, some, or all of the following parameters: namely the SRS power control adjustment state, or the SRS closed-loop power control index, the path loss reference signal, the spatial relationship, the P0 value, and the alpha value, may be defined as a parameter set by RRC (or the SRS power control adjustment state, P0, and alpha may be added to the path loss reference signal IE or the spatial relationship IE).

[0156] RRC can constitute a list of parameter sets, i.e., multiple parameter sets, for the UE. MAC-CE can indicate (by parameter set ID) one parameter set to be applied for SRS. Alternatively, the parameter set may be implicitly indicated by the path loss reference signal ID or spatial relation ID.

[0157] In another example, the RRC may define a parameter set consisting of the following parameters: namely, the SRS power control adjustment state or SRS closed-loop power control index, the P0 value, and the alpha value.

[0158] RRC can constitute a list of parameter sets, i.e., multiple parameter sets, for the UE. MAC-CE may indicate one parameter set to be applied for SRS (by parameter set ID), or it may indicate a path loss reference signal ID / spatial relation ID to be applied for SRS.

[0159] In another embodiment, if the UE supports a Rel-17 joint DL / UL Transmission Configuration Indicator (TCI) state or a Rel-17 separate DL / UL TCI state, the TCI state may be associated with one, some, or all of the following parameters for the SRS: namely, the SRS power control adjustment state or SRS closed-loop power control index, the path loss reference signal, the P0 value, and the alpha value.

[0160] When the gNB indicates a TCI status to the UE, the relevant parameters may be applied to the SRS transmission.

[0161] In another example, for SRS with antenna switching, the SRS parameters listed above should conform to the indicated joint DL / UL TCI state or separate DL / UL TCI state. Alternatively, for SRS with antenna switching, the beam for SRS transmission should conform to the separate DL TCI state, and the SRS parameters listed above may conform to the separate UL TCI state. Alternatively, the SRS parameters listed above should conform to MAC-CE.

[0162] In another example, for an SRS with beam management, if the SRS refines a gNB Rx beam, the SRS parameters listed above should follow the indicated joint DL / UL TCI state or separate UL TCI state. If the SRS refines a UE Tx beam, the TCI state does not apply to the SRS, and the SRS parameters listed above may follow MAC-CE. Alternatively, for an SRS with beam management, the SRS parameters listed above should follow MAC-CE.

[0163] In another example, for SRS with a non-codebook, if the relevant CSI-RS is configured, the SRS parameters listed above should conform to MAC-CE. If the relevant CSI-RS is not configured, the SRS parameters listed above should conform to the indicated joint DL / UL TCI state or separate UL TCI state.

[0164] Scenario F: Power control with PDCCH iterations

[0165] In one embodiment, when a PDCCH iteration including intra-slot iterations and inter-slot iterations is enabled, if a TPC command (for PUSCH, PUCCH, or SRS) is included in the DCI, the TPC command carried by multiple PDCCH iterations is considered only once for the corresponding closed-loop power control state when performing uplink power control for PUSCH / PUCCH / SRS, and includes both enabling and disabling TPC accumulation.

[0166] Scenario G: Power control for antenna switching

[0167] In one embodiment, for an SRS with antenna switching, the Tx power is maintained the same across SRS resources in one or more aperiodic SRS resource sets triggered by the same DCI. This can be used when closed-loop power control is applied and / or when open-loop power control is applied.

[0168] Figure 8 illustrates power control for SRS antenna switching in several ways. For example, in closed-loop power control, if a TPC command is received between aperiodic SRS resource sets for antenna switching triggered by the same DCI, the TPC command is ignored, as shown in the example in Figure 8. Alternatively, the gNB does not send a TPC command between aperiodic SRS resource sets for antenna switching triggered by the same DCI.

[0169] An example of a specification change in Section 7.3.1 of TS 38.213 is as follows: If srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS transmission and PUSCH transmission, the update of the power control adjustment state for SRS transmission opportunity i is performed on SRS resource set q s The update of the power control adjustment state SRS transmission opportunity i occurs at the beginning of each SRS resource within, and if not, the SRS resource set q s This occurs at the beginning of the first SRS resource transmitted within the set. In SRS with antenna switching, if multiple SRS resource sets are triggered by the same DCI, the power control adjustment update occurs only at the beginning of the first SRS resource transmitted within the first SRS resource set.

[0170] In another example, with SRS involving antenna switching, if multiple SRS resource sets are triggered by the same DCI, the SRS resource sets are treated as a single SRS transmission opportunity.

[0171] In another embodiment, in an SRS with antenna switching, the same Tx power is maintained across all SRS resources in a periodic / semi-persistent SRS resource set during a cycle, causing all receiving antennas to ring by transmitting all SRS resources. Which SRS resource transmission is used as the starting point of a cycle can be predefined or configured / instructed by the gNB. For example, if a periodic / semi-persistent SRS resource set contains four SRS resources, the same Tx power is applied to the SRS during a cycle in which all four SRS resources are transmitted.

[0172] While embodiments have been described with reference to specific exemplary embodiments, it will be apparent that various modifications and changes may be made to these embodiments without departing from the broader scope of this disclosure. Therefore, this specification and the drawings should be interpreted as illustrative, not restrictive. The accompanying drawings, forming part of this specification, illustrate, not restrictive, specific embodiments in which the subject matter may be carried out. The illustrated embodiments are described in sufficient detail so that those skilled in the art can carry out the teachings disclosed herein. Other embodiments may be utilized and derived therefrom so that structural and logical substitutions and modifications can be made without departing from the scope of this disclosure. Therefore, this detailed description should not be interpreted as restrictive, and the scope of various embodiments is defined solely by the accompanying claims, along with the entire scope of equivalents to which such claims are entitled.

[0173] The subject matter may be referred to herein, individually and / or collectively, by the term “embodiments” if one or more are actually disclosed, solely for convenience and without the intention of voluntarily limiting the scope of this application to any single inventive concept. Therefore, it should be understood that while certain embodiments are illustrated and described herein, any arrangement calculated to achieve the same objective may be substituted for the specific embodiments shown. This disclosure should cover any and all adaptations or variations of the various embodiments. Combinations of the above embodiments with other embodiments not specifically described herein will become apparent to those skilled in the art upon consideration of the foregoing description.

[0174] In this specification, the terms "a" or "an" are used to include one or more, independently of any other example or use of "at least one" or "one or more," as is common in the patent literature. In this text, the term "or" is used to refer to non-exclusive or, for example, "A or B" includes "including A but not B," "including B but not A," and "A and B," unless otherwise indicated. In this text, the terms "including" and "in which" are used as plain English equivalents of the terms "comprising" and "wherein," respectively. Furthermore, in the following claims, the terms "including" and "in which" are open-ended; that is, a system, UE, article, configuration, formula or process that includes elements in addition to those enumerated after such terms in the claim is still considered to be within the scope of that claim. Furthermore, in the following claims, the terms "first," "second," and "third," etc., are used merely as labels and are not intended to impose numerical requirements on their subjects.

[0175] This abstract of the disclosure is provided in accordance with 37C.FR §1.72(b), which requires an abstract to enable readers to quickly confirm the nature of the technical disclosure. It is presented with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, as can be seen in the prior detailed description, various features have been grouped into a single embodiment in order to simplify the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than those expressly described in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in fewer features than all the features of a single disclosed embodiment combined. Accordingly, the following claims are incorporated into the detailed description, and each claim stands independently as a separate embodiment.

Claims

1. An apparatus for fifth-generation node B (gNB), the apparatus is: Transmitting a physical downlink control channel (PDCCH) including downlink control information (DCI) to a user equipment (UE) compatible with multi-transmit / receive point (TRP) operation, wherein the DCI includes a transmit power control (TPC) command, the TPC command is for a sounding reference signal (SRS), and the TPC command is configured to indicate the power control adjustment status of each TRP in the UE's multi-TRP operation. The UE receives the SRS having power dependent on the TPC command, A processing circuit that configures the gNB to perform the following: A memory configured to store the aforementioned TPC command, A device comprising, wherein a set of SRS power control parameters, including SRS power control adjustment state, path loss reference signal, spatial relationship, P0 value, and alpha value, is defined by radio resource control (RRC) signaling.

2. The processing circuit configures the gNB to use DCI format 0_1 ​​or 0_2, which does not involve scheduling of physical uplink shared channels (PUSCH), as the DCI for the single TRP operation of the UE. The apparatus according to claim 1.

3. For the multi-TRP operation of the UE, the DCI includes a plurality of TPC commands applied to SRS power control, and the SRS consists of a plurality of SRS power control adjustment states separate from the physical uplink shared channel (PUSCH) power control adjustment states. The apparatus according to claim 1 or 2.

4. The DCI is either DCI format 0_1 ​​or 0_2, or DCI format 2_3, which does not involve scheduling of physical uplink shared channels (PUSCH). Each SRS power control state is: A first selection from one of the following: the same power control state as the first PUSCH power control adjustment state, the same power control state as the second PUSCH power control adjustment state, a first SRS power control state separate from the first and second PUSCH power control adjustment states, and a second SRS power control state separate from the first and second PUSCH power control adjustment states, or The same power control state as the first PUSCH power control adjustment state indicated by the SRS power control adjustment, h b,f,c (i,l), l=0, and the same power control state as the second PUSCH power control adjustment state indicated by the SRS power control adjustment, h b,f,c (i,l), l=1, and a second selection from one of the SRS power control states which are separate from the first and second PUSCH power control adjustment states, The apparatus according to claim 3, which is designated as one of the following.

5. The DCI is either DCI format 0_1 ​​or 0_2, or DCI format 2_3, which does not involve scheduling of physical uplink shared channels (PUSCH). The aforementioned DCI is Different TPC command fields, or A single TPC command field, wherein the code point of the single TPC command field indicates the TPC command, It includes two TPC commands provided by one of them, Each TPC command is applied to SRS transmissions destined for different TRPs. The apparatus according to any one of claims 1 to 4.

6. The relationship between the TPC command and the SRS power control state is implicitly indicated such that the first TPC command is applied to the first SRS transmission to the first TRP, and the second TPC command is applied to the second SRS transmission to the second TRP, or The relationship between the TPC command and the SRS power control state is explicitly indicated by an additional bit that shows whether each TPC command is applied to a first SRS power control state or a second SRS power control state. The apparatus according to claim 5, which is one of the two.

7. The dynamic switching between multi-TRP operation and single-TRP operation is instructed by the power control state configuration of the SRS, or At least one of the SRS power control parameters is reconfigured via an unused bit of the release 17 in the DCI. At least one of the following: The apparatus according to claim 5.

8. The DCI is DCI format 0_1 ​​or 0_2, which does not involve scheduling of physical uplink shared channels (PUSCH). Regardless of whether the UE is in multi-TRP operation or single-TRP operation, only open-loop power control is applied to the SRS. The apparatus according to any one of claims 1 to 7.

9. The DCI is DCI format 0_1 ​​or 0_2, which involves scheduling of physical uplink shared channels (PUSCH). If the DCI includes a first TPC command and a second TPC command for multi-TRP operation, the first TPC command is associated with a PUSCH transmission or SRS transmission toward the first TRP, and the second TPC command is associated with a PUSCH transmission or SRS transmission toward the second TRP. When the DCI schedules only a single TRP push transmission toward the first TRP and triggers an SRS transmission toward the second TRP, the first TPC command is associated with the push power control state toward the first TRP, and the second TPC command is associated with the SRS power control state toward the second TRP. The apparatus according to any one of claims 1 to 8.

10. The DCI schedules only single TRP physical uplink shared channel (PUSCH) transmissions. Only one TPC command is included in the DCI. The DCI triggers an SRS transmission directed to a TRP different from the PUSCH transmission. Only open-leap power control is applied to the SRS transmission. The apparatus according to any one of claims 1 to 9.

11. The DCI is one of the following: DCI format 0_1 ​​or 0_2, DCI format 0_0, or DCI format 2_2, with scheduling of physical uplink shared channels (PUSCH). The DCI includes a first TPC command and a second TPC command, The first TPC command is applied to the physical uplink shared channel (PUSCH) and SRS to the first TRP, The aforementioned second TPC command is applied to PUSCH and SRS to the second TRP, The most recent first and second TPC commands are used for the current SRS directed to at least the first TRP and the second TRP, respectively, and the most recent first and second TPC commands are encoded for transmission to the UE prior to the transmission of the current SRS. The apparatus according to any one of claims 1 to 10.

12. In multi-TRP operations, multiple SRS resource sets are used for codebook and non-codebook-based transmissions. The DCI is DCI format 0_1 ​​or 0_2, which involves scheduling of physical uplink shared channels (PUSCH). The DCI includes first and second SRS resource index (SRI) fields, each indicating an SRS resource from a different SRS resource set. The PUSCH power control state is either explicit or implicit. Associated with different SRS resource sets, or To be indicated by the first and second SRI fields, At least one of the following, The implicit indication of the PUSCH power control state is based on an SRI sequence in which the first SRI is applied to the first PUSCH power control state and the second SRI is applied to the second PUSCH power control state. The apparatus according to any one of claims 1 to 11.

13. The first SRI indicates one SRS resource from an SRS resource set having an SRS power control state that is a first PUSCH power control state, and the second SRI indicates one SRS resource from an SRS resource set having an SRS power control state that is a second PUSCH power control state. The first SRI may point to one SRS resource from the SRS resource set having a lower identifier (ID), and the second SRI may point to one SRS resource from the SRS resource set having a higher ID, or The PUSCH power control state is indicated by the SRS power control state of the corresponding SRS resource set. The apparatus according to claim 12, which is one of the present inventions.

14. The explicit configuration of a particular SRS resource set is based on whether the first SRI and the second SRI are used in the particular SRS resource set, and the SRS power control state configured for the particular SRS resource set indicates a PUSCH power control state for the corresponding SRI, or The mapping between characteristics including the path loss reference signal, spatial relationships, P0 value, and alpha value for push power control and each SRI supports multiple SRS resource sets in multi-TRP operation. At least one of the above, and the mapping is The parameters sri-PUSCH-PathlossReferenceRS-Id and sri-P0-PUSCH-AlphaSetId in the SRI-PUSCH-PowerControl parameter of the RRC signaling indicate one of two values: a first value applied to the first PUSCH power control state and a second value applied to the second PUSCH power control state. The additional sri-PUSCH-PathlossReferenceRS-Id and the additional sri-P0-PUSCH-AlphaSetId in the SRI-PUSCH-PowerControl parameter are applied to the second PUSCH power control state, or Regarding multi-TRP operation, the first SRI-PUSCH-PowerControl is applied to the first TRP, and the second SRI-PUSCH-PowerControl is applied to the second TRP. The apparatus according to claim 12, as indicated by one of the following.

15. If the UE supports a Rel-17 joint downlink / uplink (DL / UL) transmit configuration indicator (TCI) state or a Rel-17 separate DL / UL TCI state, the TCI state is associated with at least one of the SRS power control parameters. The apparatus according to any one of claims 1 to 14.

16. A device for user equipment (UE) compatible with multi-transmit / receive point (TRP) operation, the device is: Receiving a physical downlink control channel (PDCCH) from a fifth-generation node B (gNB) including downlink control information (DCI), wherein the DCI includes transmit power control (TPC) commands, the TPC commands are for sounding reference signals (SRS), and the TPC commands are configured to indicate the power control adjustment status of each TRP in the UE's multi-TRP operation. The gNB transmits the SRS using the power indicated by the TPC command, A processing circuit that configures the UE to perform the following: A memory configured to store the DCI, A device comprising, wherein a set of SRS power control parameters, including SRS power control adjustment state, path loss reference signal, spatial relationship, P0 value, and alpha value, is defined by radio resource control (RRC) signaling.

17. The DCI is DCI format 0_1 ​​or 0_2, which involves scheduling of physical uplink shared channels (PUSCH). The DCI includes first and second SRS resource index (SRI) fields, each indicating an SRS resource from a different SRS resource set. The PUSCH power control state is either explicit or implicit. Associated with different SRS resource sets, or To be indicated by the first and second SRI fields, At least one of the following: The apparatus according to claim 16.

18. A non-temporary computer-readable storage medium for storing instructions for execution by one or more processors of a fifth-generation node B (gNB), wherein when the instructions are executed, the one or more processors: The method involves transmitting a physical downlink control channel (PDCCH) containing downlink control information (DCI) to a user equipment (UE) that supports multi-transmit / receive point (TRP) operation, wherein the DCI includes a transmit power control (TPC) command, the TPC command is for a sounding reference signal (SRS), and the TPC command is configured to indicate the power control adjustment status of each TRP in the UE's multi-TRP operation. The UE receives the SRS having power dependent on the TPC command, A non-temporary computer-readable storage medium configured such that the gNB performs the following: a set of SRS power control parameters, including SRS power control adjustment state, path loss reference signal, spatial relations, P0 value and alpha value, is defined by radio resource control (RRC) signaling.

19. The DCI is DCI format 0_1 ​​or 0_2, which involves scheduling of physical uplink shared channels (PUSCH). The DCI includes first and second SRS resource index (SRI) fields, each indicating an SRS resource from a different SRS resource set. The PUSCH power control state is either explicit or implicit. Associated with different SRS resource sets, or To be indicated by the first and second SRI fields, At least one of the following: The non-temporary computer-readable storage medium according to claim 18.

Images