Simultaneous multi-panel and TRP transmission

Abstract

Apparatus and systems are described that support uplink UL transmission via simultaneous transmission over multiple panels (STxMP). At least one downlink control information (DCI) is used to schedule STxMP UL transmissions to multiple transmission / reception points (TRPs). The DCI indicates whether time-domain (TD) repetition should be applied, as well as time-domain and / or frequency-domain resource locations for different multiplexing schemes. Aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) multiplexing is multiplexed into one or more of the repetitions. One or more sounding reference signal (SRS) resource indication (SRI) fields in the DCI indicate the SRS resources to use for transmission. A physical uplink control channel (PUCCH) resource configuration mechanism is described for STxMP operation.

Description

[Technical Field]

[0001] Embodiments relate to communications within 3GPP networks. In particular, some embodiments relate to simultaneous multi-panel and transmit-receive point (TRP) transmissions and their configuration in fifth generation (5G) and beyond networks. [Background technology]

[0002] The use and complexity of wireless systems is increasing due to the increasing types of electronic devices using network resources and the amount of data and bandwidth used by various applications, such as video streaming, running on electronic devices. As expected, the emergence of new technologies brings with it various challenges, such as the complexities associated with using multiple TRPs and multiple panels. [Brief explanation of the drawings]

[0003] [Figure 1A] 1 depicts the architecture of a network according to several aspects. [Figure 1B] 1 depicts a non-roaming 5G system architecture according to several aspects. [Figure 1C] 1 depicts a non-roaming 5G system architecture according to several aspects. [Figure 2] 1 illustrates a block diagram of a communication device according to some embodiments. [Figure 3] 1 illustrates simultaneous multi-TRP multi-panel transmission according to some embodiments. [Figure 4A] 1 illustrates simultaneous transmission over multiple panels (STxMP) with time domain (TD) repetition without panel switching, according to some embodiments. [Figure 4B] 1 illustrates simultaneous transmission over multiple panels (STxMP) via time domain (TD) repetition with panel switching, according to some embodiments. [Figure 5A]1 illustrates contiguous resource allocations for a physical uplink shared channel (PUSCH) in panels 1 and 2, according to some embodiments. [Figure 5B] 1 illustrates interleaved resource allocation for a physical uplink shared channel (PUSCH) in panels 1 and 2, according to some embodiments. [Figure 6A] 1 illustrates a frequency domain multiplexing (FDM) STxMP based on a single downlink control information (DCI) with TD repetition and frequency / panel switching, according to some embodiments. [Figure 6B] 1 illustrates FDM STxMP based on single DCI with TD repetition without frequency / panel switching, according to some embodiments. [Figure 7A] 1 illustrates FDM STxMP based on multi-DCI with TD repetition with frequency / panel switching, according to some embodiments. [Figure 7B] 1 illustrates FDM STxMP based on multi-DCI with TD repetition without frequency / panel switching, according to some embodiments. [Figure 8A] 1 illustrates FDM STxMP based on multi-DCI with TD repetition with frequency / panel switching, according to some embodiments. [Figure 8B] 1 illustrates FDM STxMP based on multi-DCI with TD repetition without frequency / panel switching, according to some embodiments. [Figure 9A] 1 illustrates SDM STxMP based on single DCI with TD repetition with frequency / panel switching, according to some embodiments. [Figure 9B] 1 illustrates SDM STxMP based on single DCI with TD repetition without frequency / panel switching, according to some embodiments. [Figure 10A] 1 illustrates SDM STxMP based on multi-DCI with TD repetition with frequency / panel switching, according to some embodiments. [Figure 10B]1 illustrates SDM STxMP based on multi-DCI with TD repetition without frequency / panel switching, according to some embodiments. [Figure 11A] 1 illustrates SDM STxMP based on multi-DCI with TD repetition with frequency / panel switching, according to some embodiments. [Figure 11B] 1 illustrates SDM STxMP based on multi-DCI with TD repetition without frequency / panel switching, according to some embodiments. [Figure 12A] 1 illustrates aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) multiplexing in STxMP PUSCH transmission, in accordance with some embodiments. [Figure 12B] 1 illustrates aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) multiplexing with STxMP PUSCH repetitions, in accordance with some embodiments. [Figure 13A] 10 illustrates A-CSI or SP-CSI multiplexing in the first TD iteration of an STxMP PUSCH transmission, in accordance with some embodiments. [Figure 13B] 10 illustrates A-CSI or SP-CSI multiplexing in the first TD repetition and second TD repetition of an STxMP PUSCH transmission, in accordance with some embodiments. [Figure 14] 10 illustrates a physical resource block (PRB) distance of a physical uplink control channel (PUCCH) transmission from a first and second panel transmission, according to some embodiments. [Figure 15] 10 depicts a panel ID according to some embodiments. [Figure 16] 10 depicts another panel ID according to some embodiments. [Figure 17] 10 depicts another panel ID according to some embodiments. [Figure 18] 10 illustrates frequency resources of PUCCH in first and second panels for STxMP operation, according to some embodiments. [Figure 19]1 illustrates a discrete Fourier transform (DFT) operation of modulated symbols for a STxMP PUCCH FDM-A scheme, according to some embodiments. [Figure 20] 10 illustrates a single DFT operation of modulated symbols for a STxMP PUCCH FDM-A scheme, in accordance with some embodiments. [Figure 21] 1 illustrates a flowchart of codebook (CB) and non-codebook (nCB) based multi-TRP transmission according to some embodiments. [Figure 22] 1 illustrates a flowchart of PUCCH transmission according to some embodiments. [Figure 23] 10 illustrates another flowchart of PUCCH transmission according to some embodiments. [Figure 24] 1 illustrates a flowchart of a PUSCH transmission according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0004] The drawings are not necessarily drawn to scale, but in the drawings, the same numbers may refer to similar components even in different views. The same numbers with different suffixes may represent different instances of similar components. The drawings generally illustrate, by way of example, and not by way of limitation, various embodiments discussed in the present specification.

[0005] The following description and drawings sufficiently represent specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for portions and features of other embodiments. Embodiments set forth in the claims encompass all available equivalents of the claims.

[0006] 1A illustrates a network architecture in accordance with some aspects. Network 140A includes 3GPP LTE / 4G and NG network functions that may be extended to 6G and beyond. Thus, while 5G is referenced herein, it should be understood that this is extendable to 6G (and beyond) structures, systems, and functions. Network functions may be implemented as individual network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtualized functions instantiated on a suitable platform, e.g., dedicated hardware or a cloud infrastructure.

[0007] Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are depicted as smartphones (e.g., handheld, touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may include any mobile or non-mobile computing device, such as a portable (laptop) or desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and 102 are sometimes referred to collectively herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0008] Any of the wireless links described herein (e.g., used within network 140A or other described networks) may operate according to any example wireless communication technology and / or standard, including any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., 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 or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR may be used by allocating OFDM carrier data bit vectors to corresponding symbol resources.

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

[0010] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, to a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The RAN 110 may include one or more gNBs, one or more of which may be implemented by multiple units. Note that although gNBs may be referred to herein, the same aspects may apply to other generation NodeBs, such as sixth generation NodeBs, and thus may alternatively be referred to as Next Generation NodeBs (xNBs).

[0011] Each gNB may implement protocol entities in the 3GPP protocol stack, where the layers are considered to be ordered from bottom to top as follows: Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Control (PDCP), and Radio Resource Control (RRC) / Service Data Adaptation protocol (SDAP) (for the control plane / user plane). The protocol layers within each gNB may be distributed among different units: a Central Unit (CU), at least one Distributed Unit (DU), and Remote Radio Heads (RRHs). The CU provides functions such as control of user data forwarding, except for functions exclusively assigned to the DU, and may accomplish mobility control, radio access network sharing, positioning, and session management.

[0012] The upper protocol layers (PDCP and RRC for the control plane / PDCP and SDAP for the user plane) may be implemented in the CU, and the RLC and MAC layers may be implemented in the DU. The PHY layer may be split, with the upper PHY layer also implemented in the DU, but the lower PHY layer implemented in the RRH. The CU, DU, and RRH may be implemented by different manufacturers but may still be connected by appropriate interfaces between them. A CU may be connected to multiple DUs.

[0013] Interfaces within the gNB include E1 and fronthaul (F)F1 interfaces. The E1 interface may be between the CU control plane (gNB-CU-CP) and the CU user plane (gNB-CU-UP) and thus may support the exchange of signaling information between the control plane and the user plane through E1AP services. The E1 interface may separate the radio network layer and the transport network layer and enable the exchange of UE-related and non-UE-related information. E1AP services may be non-UE-related services that pertain to the entire E1 interface instance between the gNB-CU-CP and the gNB-CU-UP using a non-UE-related signaling connection, and UE-related services that pertain to a single UE and are associated with a UE-related signaling connection maintained for the UE.

[0014] The F1 interface may be located between the CU and the DU. The CU may control the operation of the DU via the F1 interface. Because signaling within the gNB is divided into control plane and user plane signaling, the F1 interface may be divided into an F1-C interface for control plane signaling between the gNB-DU and the gNB-CU-CP and an F1-U interface for user plane signaling between the gNB-DU and the gNB-CU-UP, which support the separation of the control plane and the user plane. The F1 interface may separate the radio network layer and the transport network layer and enable the exchange of UE-related and non-UE-related information. The F2 interface may also be located between the lower and upper parts of the NR PHY layer. The F2 interface may also be divided into an F2-C interface and an F2-U interface based on the control plane and user plane functions.

[0015] UEs 101 and 102 utilize connections 103 and 104, respectively, each having a physical communication interface or layer (discussed further below), which in this example are represented as air interfaces enabling communication coupling and may follow cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, the Code-Division Multiple Access (CDMA) network protocol, the Push-to-Talk (PTT) protocol, the PTT over Cellular (POC) protocol, the Universal Mobile Telecommunications System (UMTS) protocol, the 3GPP Long Term Evolution (LTE) protocol, the 5G protocol, the 6G protocol, and the like.

[0016] In certain aspects, the UEs 101 and 102 may also directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface, which includes one or more logical channels, including, but not limited to, a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0017] UE 102 is shown configured to access Access Point (AP) 106 via connection 107. Connection 107 may comprise a local wireless connection, such as a connection according to any IEEE 802.11 protocol, whereby AP 106 may comprise a Wireless Fidelity (Wi-Fi®) router. In this example, AP 106 is shown connected to the Internet without a connection to a wireless system's core network (discussed further below).

[0018] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may comprise terrestrial stations (terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmission-reception points (TRPs). When the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes that provide macrocells, e.g., macro RAN node 111, and one or more RAN nodes that provide femtocells or picocells (e.g., cells having a smaller coverage range, lower user capacity, or higher bandwidth compared to a macrocell), e.g., low power (LP) RAN node 112.

[0019] Both RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for UEs 101 and 102. In some aspects, both RAN nodes 111 and 112 may fulfill various logical functions for the RAN 110, including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In one example, both nodes 111 and 112 may be gNBs, eNBs, or other types of RAN nodes.

[0020] The RAN 110 is shown communicatively coupled to a core network (CN) 120 via an S1 interface 113. In some aspects, the CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or other type of CN (e.g., as described with reference to FIGS. 1B-1C ). In this aspect, the S1 interface 113 is divided into two parts: an S1-U interface 114 that carries traffic data between the RAN nodes 111 and 112 and a serving gateway (S-GW) 122, and an S1-MME interface 115 that is a signaling interface between the RAN nodes 111 and 112 and a mobility management entity (MME) 121.

[0021] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 is similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSNs). The MME 121 may manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS 124 may have a database for network users containing subscription-related information to support the handling of communication sessions by network entities. The CN 120 may have one or more HSSs 124, depending on the number of mobile subscribers, device capabilities, network organization, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0022] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. The S-GW 122 may also be a local mobility anchor point for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 include lawful interception, charging, and some policy enforcement.

[0023] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the CN 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 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 in the core network (e.g., a UMTS packet service (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown communicatively 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 (e.g., a voice over Internet Protocol (VoIP) session, a PTT session, a group communication session, a social networking service, etc.) for the UEs 101 and 102 via the CN 120.

[0024] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectively Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0025] In some aspects, the communications network 140A can be an IoT network or a 5G or 6G network, including a 5G New Radio network using communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One current implementation of IoT is Narrowband IoT (NB-IoT). Operation in unlicensed spectrum includes dual connectivity (DC) operation and standalone LTE systems in unlicensed spectrum, whereby LTE-based technologies operate solely in unlicensed spectrum without the use of an "anchor" in licensed spectrum, known as MultiFire. Further enhanced operation of LTE systems in licensed and unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operation can include techniques for sidelink resource allocation and UE processing operations for NR sidelink V2X communications.

[0026] The NG system architecture (or 6G system architecture) may include a RAN 110 and a core network (CN) 120. The NG-RAN 110 may include multiple nodes, such as a gNB and an NG-eNB. The CN 120 (e.g., a 5G core network (5GC)) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some aspects, the gNB and the NG-eNB may be connected to the ALF by an NG-C interface and to the UPF by an NG-U interface. The gNB and the NG-eNB may be coupled to each other via an Xn interface.

[0027] In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some aspects, the gNB may be a master node (MN) and the NG-eNB may be a secondary node (SN) in the 5G architecture.

[0028] 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. 1B illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, a UE 102 can communicate with a RAN 110 and one or more other CN network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an AMF 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a UPF 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146.

[0029] The UPF 134 can provide connectivity to the data network 152, which may include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and may also include a network slice selection function. The AMF 132 can provide UE-based authentication, authorization, mobility management, etc., and can be access technology independent. The SMF 136 can be configured to set up and manage various sessions according to network policies. The SMF 136 can thus be involved in session management and UE IP address allocation. The SMF 136 can also select and control the UPF 134 for data transfer. The SMF 136 can be associated with a single session of the UE 101 or with multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. A different SMF can be assigned to each session. The use of a different SMF can allow each session to be managed individually, resulting in the functionality of each session being independent of each other.

[0030] The UPF 134 can be arranged in one or more configurations according to the desired service type and can be connected to a data network. The PCF 148 can be configured to provide a policy framework with network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0031] The AF 150 may provide information about the packet flow to the PCF 148, which is responsible for policy control to support the desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To accomplish this, the PCF 148 may use the packet flow information to determine appropriate policies for appropriate operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0032] In some aspects, the 5G system architecture 140B includes an IP Multimedia Subsystem (IMS) 168B and multiple IP Multimedia Core Network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF that can operate as a Proxy CSCF (P-CSCF) 162B, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B may be configured to be the first point of contact for the UE 102 within the IM Subsystem (IMS) 168B. The S-CSCF 164B may be configured to handle session state within the network, and the E-CSCF may be configured to handle certain aspects of the emergency session, such as routing emergency requests to the correct emergency center or PSAP. The I-CSCF 166B may be configured to serve as a liaison point within the network of the network operator for all IMS connections destined for subscribers of that network operator or roaming subscribers currently within the network operator's service area. In some aspects, the I-CSCF 166B may be connected to other IP multimedia networks 170B, e.g., IMSs operated by different network operators.

[0033] In some aspects, the UDM / HSS 146 may be coupled to an application server (AS) 160B, which may include a telephony application server (TAS) or other application server. The AS 160B may be coupled to an IMS 168B via an S-CSCF 164B or an I-CSCF 166B.

[0034] 1B shows the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), and N10 (between the UDM 146 and the SMF 136, not shown). , N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in a non-roaming scenario, or between the PCF 148, the visited network, and the AMF 132 in a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between the AMF 132 and the NSSF 142, not shown). Other reference point representations not shown in Figure 1B may also be used.

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

[0036] 1C , a service-based representation can be used to represent network functions in the control plane, allowing other authorized network functions to access those services. In this regard, the 5G system architecture 140C can include the following service-based interfaces: Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (e.g., Nudr, N5g-eir, and Nudsf) may also be used.

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

[0038] 2 illustrates a block diagram of a communications device according to some embodiments. Communications device 200 may be a dedicated computer, a UE such as a personal or laptop computer (PC), a tablet PC, or a smartphone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or a machine capable of executing instructions (sequential or otherwise) specifying operations to be performed by the machine. For example, the communications device block diagram may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded prior to transmission by a transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after receipt by the receiving entity.

[0039] The examples described herein may include or operate on logic or multiple components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) that can perform specified operations and may be configured or arranged in a particular way. In one example, a circuit may be arranged as a module (e.g., internally or relative to external entities such as other circuits) in a specified manner. In one example, all or part of one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In one example, the software may reside on a machine-readable medium. In one example, the software, when executed by the underlying hardware of a module, causes the hardware to perform the specified operations.

[0040] Thus, the terms "module" (and "component") are understood to include entities that are physically constructed, specially configured (e.g., hardwired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a specified manner or to perform some or all of the operations described herein. Considering examples in which the modules are temporarily configured, each of the modules need not be instantiated at any one time. For example, if the modules include a general-purpose hardware processor that is configured using software, the general-purpose hardware processor may be configured as each different module at different times. The software may configure the hardware processor accordingly, e.g., to configure a particular module at one time and to configure a different module at a different time.

[0041] The communications device 200 may include a hardware processor (or equivalently, processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204, and a 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 and / or non-volatile memory. The communications device 200 may further include a display unit 210, such as a video display, an alphanumeric input device 202 (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 202, 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, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0042] Storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter simply referred to as machine-readable medium) having stored thereon one or more sets of data structures or instructions 224 (e.g., software) embodied or utilized by any one or more of the techniques or functions described herein. Instructions 224 may reside, completely or at least partially, within main memory 204, static memory 206, and / or within hardware processor 202 during execution thereof by communications device 200. Although machine-readable medium 222 is depicted as a single medium, the term "machine-readable medium 222" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224.

[0043] The term "machine-readable medium" may include any medium that can store, encode, or carry instructions for execution by communications device 200, cause communications device 200 to perform any one or more of the techniques of this disclosure, or store, encode, or carry data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memory, and optical and magnetic media. Specific examples of machine-readable media 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, optical and magnetic disks, random access memory (RAM), and CD-ROM and DVD-ROM disks.

[0044] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via an interface device 220 utilizing any one of a number of wireless local area network (WLAN) transport protocols (e.g., frame relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone service (POTS) network, and a wireless data network. Communication over the network may include one or more of a variety of protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, the IEEE 802.16 family of standards known as WiMax, the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, next-generation (NG) / fifth-generation (5G) standards, among others. In one example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas for connecting to the transmission medium 226.

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

[0046] As used herein, the term "processor circuitry" or "processor" thus refers to, is part of, or includes circuitry capable of sequentially and automatically performing a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The term "processor circuitry" or "processor" may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single or multi-core processors, and / or any other device capable of executing or otherwise manipulating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0047] Any of the wireless links described herein may operate in accordance with any one or more of the following wireless communication technologies and / or standards: Global System for Mobile Communications (GSM) wireless communication technology, General Packet Radio Service (GPRS) wireless communication technology, Enhanced Data Rates for GSM Evolution (EDGE) wireless communication technology, and / or Third Generation Partnership Project (3GPP) wireless communication technologies, such as Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code Division Multiple Access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CDS), and / or LTE-Advanced. High-Speed Circuit-Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (3rd Generation) (UMTS (3G)), Wideband Code Division Multiple Access (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSPA),HSDPA), High-Speed Uplink Packet Access (HSUPA), High-Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (3GPP Rel. 8 (Pre-4G)), 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 (e.g., Rel. 18, Rel. 19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE-Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code Division Multiple Access 2000 (3rd Generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (Evolution-Data Optimized or Evolution-Data Only,EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System / Extended Total Access Communication System (TACS / ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D or Mobile telephony system D), Public Automated Land Mobile (Autotel / PALM), ARP (Finnish for Autoradiopuhelin ("Automobile Radio Telephone"), NMT (Nordic Mobile Telephony), NTT (Nippon Telegraph and Telephone)'s high-capacity version (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC),PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Broadband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also known as the 3GPP Universal Access Network or GAN standard, Zigbee, Bluetooth, Wireless Gigabit Alliance Alliance, WiGig) standards, mmWava standards in general (wireless systems operating in the 10-300 GHz and above range, such as WiGig, IEEE802.11ad, IEEE802.1ay, etc.), technologies operating above the 300 GHz and THz bands, Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies (based on 3GPP / LTE or IEEE802.11p or IEEE802.1bd and others), Dedicated Short Range Radio (DSRC) technologies such as 3GPP Cellular V2X, intelligent transportation systems, and others. Communications systems (typically operating in the 5850 MHz to 5925 MHz band or higher (typically up to 5935 MHz, following the proposed changes in CEPT Report 71)), European ITS-G5 systems (i.e., the European version of IEEE 802.11p-based DSRC, including ITS-G5A (i.e., operation of the European ITS frequency bands dedicated to ITS for safety-related applications in the frequency range of 5875 GHz to 5905 GHz), ITS-G5B (i.e., operation of the European ITS frequency bands dedicated to ITS non-safety applications in the frequency range of 5855 GHz to 5875 GHz), ITS-G5C (i.e., operation of ITS applications in the frequency range of 5470 GHz to 5725 GHz), DSRC in Japan in the 700 MHz band (including 715 MHz to 725 MHz), IEEE 802.11bd-based systems, etc.

[0048] Aspects described herein may be used in connection with any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, license-exempt spectrum, and (licensed) shared spectrum (e.g., 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 = Citizens Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum and other types of spectrum / bands, such as bands with national allocations (450-470 MHz, 902-928 MHz (note: e.g., allocated in the United States (FCC Part 15)), 863-868.6 MHz (note: e.g., allocated in the European Union (ETSI EN300)). 200), 915.9-929.7 MHz (Note: allocated for example in Japan), 917-923.5 MHz (Note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (Note: allocated for example in China), 790-960 MHz, 1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2.4-2.4835 GHz (Note: ISM band available worldwide, also used by the Wi-Fi family of technologies (11b / g / n / ax) and Bluetooth).), 2500-2690MHz, 696-790MHz, 610-790MHz, 3400-3600MHz, 3400-3800MHz, 3800-4200MHz, 3.55-3.7GHz (Note: Allocated, for example, in the US for Citizens Broadband Wireless Service), 5.15-5.25GHz, 5.25-5.35GHz, 5.47-5.725GHz, and 5.725-5.85GHz (Note: Allocated, for example, in the US (FCC Part 15), consisting of four U-NII bands within a total of 500MHz spectrum), 5.725-5.875GHz (Note: Allocated, for example, in the EU (ETSI EN301 893), 5.47-5.65 GHz (Note: allocated in South Korea, for example), 5925-7125 MHz and 5925-6425 MHz bands (Note: under consideration in the US and EU, respectively. Next-generation Wi-Fi systems are expected to include the 6 GHz spectrum as an operating band, but as of December 2017, Wi-Fi systems have not yet been permitted in this band. Regulation is expected to be completed between 2019 and 2020.), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800-4200 MHz, the 3.5 GHz band, the 700 MHz band, and bands in the 24.25-86 GHz range, etc.), and the FCC's "Spectrum Spectrum made available under the “Frontier” 5G initiative (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).), 5.9 GHz (typically 5.85-5.925 GHz) and the 63-64 GHz ITS (Intelligent Transport Systems) bands, bands currently allocated to WiGig, such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz), WiGig Band 3 (61.56-63.72 GHz), and WiGig Band 4 (63.72-65.88 GHz), and 57-64 / 66 GHz (Note: This band has a near-universal designation for Multi-Gigabit Wireless Systems (MGWS) / WigGig. A total of 14 GHz of spectrum has been allocated in the US (FCC Part 15), but the EU (ETSI EN 302 567 and ETSI EN 301 for fixed P2P) A total of 9 GHz of spectrum has been allocated in RFC 217-2. This includes the 70.2 GHz to 71 GHz bands, and any band between 65.88 GHz and 71 GHz, bands currently allocated for automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme allows for secondary use in bands such as TV white space bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being promising candidates. In addition to cellular applications, it can also accommodate specific applications for vertical markets, such as Program Making and Special Events (PMSE), medical, health, surgery, automotive, low latency, drones, and other applications.

[0049] Aspects described herein may also be implemented in a hierarchical manner by introducing a virtual prioritization of usage for different types of users (e.g., low / medium / high priority, etc.) based on prioritized access to spectrum, e.g., tier-1 users are assigned the highest priority, followed by tier-2, then tier-3, etc. users.

[0050] Aspects described herein may also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP New Radio (NR) by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0051] As mentioned above, Rel-17 NR supports multi-TRP physical uplink shared channel (PUSCH) repetition and physical uplink control channel (PUCCH) repetition. This allows the same uplink (UL) data or control information to be transmitted to multiple TRPs as multiple repetitions / transmissions in multiple time slots or subslots. However, only one UL transmission occasion occurs for a particular TRP in each time slot or subslot. To more efficiently utilize multiple TRPs, it is desirable for Rel-18 5G NR systems to support a simultaneous multi-TRP multi-panel transmission scheme in the UL, where a UE is equipped with multiple antenna panels. Figure 3 illustrates simultaneous multi-TRP multi-panel transmission according to some embodiments. In particular, to increase overall capacity and transmission robustness against potential channel blocking, a UE may transmit data and control information simultaneously targeting two or more TRPs, as shown in Figure 3. In Figure 3, the transmit beam from panel 1 targets TRP1, and the transmit beam from panel 2 targets TRP2.

[0052] To support simultaneous multi-TRP (mTRP) multi-panel transmission operation in the UL, various transmission schemes can be considered. For example, mTRP transmission can be scheduled by either a single DCI (sDCI) or multiple DCIs (mDCI). In particular, a single downlink control information (DCI)-based scheme schedules PUSCH transmission by a single DCI transmitted through either one TRP or multiple TRPs. A multi-DCI-based scheme schedules PUSCH transmission by multiple DCIs through multiple TRPs.

[0053] Rel-17 supports a repetition scheme based on multiple TRPs, where the same transport block (TB) and uplink control information (UCI) can be transmitted on different PUSCH / PUCCH repetitions to different TRPs in a time-domain multiplexing (TDM) manner to improve communication reliability. Rel-18 supports simultaneous transmission with multiple panels (STxMP), where two PUSCH / PUCCH transmission occasions can be transmitted simultaneously from two different UEs to two different TRPs.

[0054] In the STxMP scheme, various multiplexing types may be used, such as spatial domain multiplexing (SDM), frequency domain multiplexing (FDM), and single frequency network (SFN). For example, in SDM STxMP, the same or different layers of one PUSCH or two PUSCHs (with the same or different TBs) may be transmitted separately and simultaneously from different UE panels. In FDM-A STxMP, different portions of the frequency domain resources of one PUSCH transmission occasion may be transmitted from different UE panels. In FDM-B STxMP, two PUSCH transmission occasions with the same or different repetition values (RVs) of the same TB may be transmitted from different UE panels on non-overlapping frequency domain resources and the same time domain resources. To enhance the reliability and coverage of UE transmissions, STxMP with repetition may be permitted in the time domain.

[0055] Note that the channel state information (CSI) may include a channel quality indicator (CQI), a synchronization signal / physical broadcast channel (SS / PBCH) block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), a layer 1 reference signal received power (L1-RSRP), or a layer 1 signal-to-interference and noise ratio (L1-SINR) reported from a UE to a base station. Aperiodic CSI (A-CSI) reporting and semi-persistent CSI (SP-CSI) reporting can be triggered by a CSI request field in DCI. In this case, A / SP-CSI reporting and UL transmission can be scheduled by one or more DCIs simultaneously. However, how to handle A / SP-CSI multiplexing with SP-CSI transmission has not yet been specified.

[0056] As mentioned above, multi-TRP time domain (TD) repetition can also be supported in STxMP transmission with or without panel switching to enhance coverage and reliability. Figure 4A illustrates simultaneous transmission using multiple panels (STxMP) with time domain (TD) repetition without panel switching, and Figure 4B illustrates STxMP with TD repetition with panel switching, according to some embodiments. Note that TD repetition can be slot-based repetition type A or back-to-back repetition type B. For UL transmission from panel 1 to panel 2 of a UE, the same or different frequency resources may be used, corresponding to STxMP schemes based on SDM or FDM, respectively.

[0057] In one option, similar to PUSCH repetition for multiple TRP operation, the association between PUSCH and sounding reference signal (SRS) resource sets in different panels may be switched. In particular, in one mode, PUSCH transmission in a first panel may be associated with a first SRS resource set, while PUSCH transmission in a second panel may be associated with a second SRS resource set.

[0058] In another mode, PUSCH transmission in the first panel may be associated with a second SRS resource set, while PUSCH transmission in the second panel may be associated with the first SRS resource set, and switching between the two modes may be indicated by an existing field, e.g., an SRS resource set indication in the DCI.

[0059] In one option, a field in the DCI scheduling PUSCH for STxMP may be used to indicate whether panel switching is enabled or disabled when time domain repetition is applied. Alternatively, a reserved state in an existing field may be used to indicate whether panel switching is enabled or disabled when time domain repetition is applied.

[0060] Furthermore, redundancy versions for repetition may be specified for PUSCH STxMP with or without TD repetition. In one embodiment, for PUSCH STxMP based on a single DCI without TD repetition, if two panels are transmitting two repetitions of the same TB, the DCI may indicate a first RV for the first repetition being transmitted through the first panel, and the RV pattern (0 2 3 1) is applied cyclically. For example, if the DCI indicates RV0 / RV2 / RV3 / RV1 for the first repetition, the second repetition being transmitted through the second panel uses RV2 / RV3 / RV1 / RV0, respectively.

[0061] In another embodiment, for PUSCH STxMP based on a single DCI with TD repetition, if two panels transmit repetitions of two different TBs, i.e., panel 1 transmits repetitions of TB1 on different time domain resources and panel 2 transmits repetitions of TB2 on different time domain resources, the DCI may indicate the first RV for the first repetition transmitted through panel 1, and an RV pattern (0 2 3 1) may be applied separately to the PUSCH through the two panels to set an RV offset relative to the starting RV for the first repetition through the second panel. For example, if the DCI indicates RV0 / RV2 / RV3 / RV1 for the first repetition through the first panel and an RV offset of 1, the first repetition through the second panel uses RV2 / RV3 / RV1 / RV0, respectively. Subsequent repetitions through the panels sequentially use subsequent RVs in the RV pattern (0 2 3 1).

[0062] In another embodiment, for PUSCH STxMP based on a single DCI with TD repetition, if two panels transmit the same TB repetition, i.e., if Panel 1 and Panel 2 transmit TB information, the DCI may indicate the first RV for the first repetition transmitted through Panel 1, and the RV pattern (0 2 3 1) may be applied separately to the PUSCH through the two panels to set an RV offset relative to the starting RV for the first repetition through the second panel. For example, if the DCI indicates RV0 / RV2 / RV3 / RV1 for the first repetition through the first panel and an RV offset of 1, the first repetition through the second panel uses RV2 / RV3 / RV1 / RV0, respectively. Subsequent repetitions through the panels sequentially use subsequent RVs in the RV pattern (0 2 3 1).

[0063] In another option for the last two embodiments, the offset indication may be absent in the DCI and the RV offset defaults to 1. Note that the repetitions mentioned above for the RV mapping are the actual repetitions for repetition type B.

[0064] STxMP with TD repetition can be scheduled by a single DCI or by multiple DCIs. In the following, different STxMP schemes with TD repetition are described.

[0065] FDM STxMP transmission with TD repetition

[0066] In FDM STxMP transmission, two orthogonal frequency resources in the uplink BWP are allocated for UL transmission via Panel 1 and Panel 2, respectively.

[0067] In one embodiment, two disjoint frequency resources for PUSCH transmission in the first and second panels may be contiguous in the frequency domain. In one option, the frequency resources for uplink transmission in the first and second panels may be allocated in a set of contiguous physical resource blocks (PRBs). In this case, a frequency domain resource allocation (FDRA) field in the DCI scheduling the PUSCH transmission may be used to indicate the frequency resource allocation for the PUSCH transmission in the first panel. Furthermore, the frequency offset between the starting PRBs of the PUSCH transmission in the first and second panels may be configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling, or may be dynamically indicated in the DCI, or a combination thereof.

[0068] In another option, the frequency offset between the starting PRBs of the PUSCH transmission in the first and second panels may be determined according to a frequency offset that is set for intra-slot, inter-repetition, or inter-slot frequency hopping of the PUSCH transmission.

[0069] As a further enhancement, the frequency offset between the starting PRBs of the PUSCH transmission in the first and second panels may be determined according to the bandwidth of the UL bandwidth portion (BWP). For example, the frequency offset may be

number

[0070] 5A and 5B illustrate consecutive resource allocations for a physical uplink shared channel (PUSCH) in panels 1 and 2, according to some embodiments. In the example shown in FIG. 5A, the frequency offset between the starting PRBs of the PUSCH transmissions in panels 1 and 2 may be configured by higher layers.

[0071] In other embodiments, two disjoint frequency resources for PUSCH transmission in the first and second panels may be interleaved in the frequency domain. In one option, frequency resources for PUSCH transmission in the first panel may be allocated every N even PRBs, while frequency resources for PUSCH transmission in the second panel may be allocated every N odd PRBs, or vice versa. Note that N may be predefined in the standard, configured by higher layers via RMSI, OSI, or RRC signaling, or dynamically indicated in DCI, or a combination thereof. In another option, N may be determined according to a resource block group (RBG) when uplink resource allocation type 0 is used for frequency resource allocation.

[0072] In another option, if uplink resource allocation type 0 is used for frequency resource allocation for STxMP, the FDRA field in the DCI scheduling the PUSCH may be used to indicate the frequency resources of the PUSCH transmission in the first panel. Furthermore, the frequency resources of the PUSCH transmission in the second panel may be derived accordingly. For example, the frequency resources of the PUSCH transmission in the second panel may be shifted by N PRBs from the frequency resources of the PUSCH transmission in the first panel.

[0073] In another option, when uplink resource allocation type 0 or type 1 is used for frequency resource allocation for STxMP, the FDRA field in the DCI scheduling the PUSCH is used to jointly indicate the frequency resources of PUSCH transmission in the first and second panels. Furthermore, the frequency resources of PUSCH transmission in the first panel can be determined accordingly based on the rules as described above. This can also be applied to determining the frequency resources for PUSCH transmission in the second panel.

[0074] 5B illustrates interleaved resource allocation for PUSCHs in panels 1 and 2 according to some embodiments. In this example, the PUSCH in panel 1 is transmitted every N even PRBs, while the PUSCH in panel 2 is transmitted every N odd PRBs, where N may be configured by higher layers as described above.

[0075] In FDM STxMP repetition, the association of the two frequency resources with the panel may or may not be switched at each subsequent STxMP transmission occasion, and the scheduling may be single DCI or multi-DCI, which will be described by the following embodiments.

[0076] Figure 6A illustrates an FDM STxMP based on a single downlink control information (DCI) with TD repetition with frequency / panel switching, according to some embodiments, and Figure 6B illustrates an FDM STxMP based on a single DCI with TD repetition without frequency / panel switching, according to some embodiments. The single DCI indicates at least the number of TD repetitions. In particular, the time-domain resource allocation field may be used to indicate one row from a table of time-domain resource allocations for PUSCH transmission, where the row includes the number of repetitions, the mapping type, and the starting and length indicator values (SLIVs). In these and subsequent figures, solid arrows indicate mTRP repetition processes, dashed arrows indicate sTRP repetition processes, and a box surrounding a PUSCH indicates one STxMP PUSCH transmission or TD repetition.

[0077] In other embodiments, multiple DCIs may be used to schedule an FDM STxMP with TD repetition. Figure 7A illustrates an FDM STxMP based on multiple DCIs with TD repetition with frequency / panel switching, and Figure 7B illustrates an FDM STxMP based on multiple DCIs with TD repetition without frequency / panel switching, according to some embodiments.

[0078] In other embodiments, FDM STxMP based on multi-DCI with TD repetition with and without frequency / panel switching can be achieved by other methods. Figure 8A illustrates FDM STxMP based on multi-DCI with TD repetition with frequency / panel switching according to some embodiments, and Figure 8B illustrates FDM STxMP based on multi-DCI with TD repetition without frequency / panel switching according to some embodiments.

[0079] In particular, repetition with frequency / panel switching can also be achieved by two simultaneous single TRP transmission processes with frequency hopping, as indicated by dashed arrows, as shown in Figure 8 A. In this case, a multi-TRP repetition process based on two simultaneous single DCIs without frequency hopping is shown in Figure 8 A, as indicated by solid arrows.

[0080] Similarly, repetition without frequency / panel switching can also be achieved by two simultaneous single TRP repetition processes without frequency hopping as indicated by dashed arrows in Figure 8B, and two simultaneous single DCI-based multi-TRP repetition processes with frequency hopping as indicated by solid arrows in Figure 8B.

[0081] SDM STxMP transmission with TD repetition

[0082] In SDM STxMP transmission, the same frequency resources may be allocated for UL transmission over panel 1 and panel 2. In SDM STxMP TD repetition, the association of the two panels with the PUSCH may not be switched at each subsequent STxMP transmission occasion, and scheduling may be single DCI or multi-DCI, as described by the following embodiments.

[0083] 9A illustrates an SDM STxMP based on a single DCI with TD repetition with frequency / panel switching, and FIG. 9B illustrates an SDM STxMP based on a single DCI with TD repetition without frequency / panel switching, according to some embodiments. That is, an SDM STxMP with TD repetition can be scheduled by a single DCI with or without frequency / panel switching. The single DCI indicates at least the number of TD repetitions. In particular, the time domain resource allocation field may be used to indicate one row from a table of time domain resource allocation for PUSCH transmission, where the row includes the number of repetitions, the mapping type, and the SLIV.

[0084] Figure 10A illustrates an SDM STxMP based on multi-DCI with TD repetition with frequency / panel switching, and Figure 10B illustrates an SDM STxMP based on multi-DCI with TD repetition without frequency / panel switching, according to some embodiments, i.e., multiple DCIs are used in Figures 10A and 10B, rather than the single DCI shown in Figures 9A and 9B.

[0085] In other embodiments, SDM STxMP based on multi-DCI with TD repetition with and without frequency / panel switching can be achieved by other methods. Figure 11A illustrates SDM STxMP based on multi-DCI with TD repetition with frequency / panel switching, and Figure 11B illustrates FDM STxMP based on multi-DCI with TD repetition without frequency / panel switching, according to some embodiments.

[0086] In particular, repetition with frequency / panel switching can also be achieved by two simultaneous single TRP transmission processes with panel switching indicated by dashed arrows as shown in Figure 11 A. In this case, a multi-TRP repetition process based on two simultaneous single DCIs without panel switching is shown in Figure 11 A indicated by solid arrows.

[0087] Similarly, repetition without panel switching can be achieved by two simultaneous single-TRP repetition processes without panel switching, as indicated by dashed arrows in Figure 11B, and two simultaneous single-DCI-based multi-TRP repetition processes with panel switching, as indicated by solid arrows in Figure 11B.

[0088] In another embodiment, when time domain repetition is applied to STxMP transmission, beam cycling can be applied to PUSCH from different panels. The existing beam cycling pattern with cyclic and sequential beam mapping can be used for PUSCH transmission on each panel, which can further increase reliability.

[0089] In one option, four SRS resource sets may be configured for STxMP PUSCH transmission with beam cycling in each panel, where the first two SRS resource sets may be associated with PUSCH transmission in the first panel and the second two SRS resource sets may be associated with PUSCH transmission in the second panel. Furthermore, the SRS resource set indication may be extended to indicate whether beam cycling is enabled or disabled for STxMP transmission.

[0090] In another option, two SRS resource sets may be configured for STxMP PUSCH transmission with beam cycling, with each panel associated with both SRS resource sets, in which case Panel 1 and Panel 2 may be associated with different SRS resource sets for each STxMP transmission.

[0091] A / SP-CSI multiplexing in STxMP

[0092] When aperiodic CSI (A-CSI) or semi-persistent CSI (SP-CSI) is scheduled together with an STxMP PUSCH transmission, the A / SP-CSI may be multiplexed with the STxMP PUSCH transmission. Figure 12A illustrates aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) multiplexing with an STxMP PUSCH transmission according to some embodiments, and Figure 12B illustrates aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) multiplexing with STxMP PUSCH repetitions according to some embodiments. As shown in Figure 12A, the A / SP-CSI may be multiplexed with the STxMP PUSCH transmission through both panels.

[0093] Note that if other uplink control information (UCI) types, including hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback, are multiplexed with A / SP-CSI on the PUSCH for only one panel, then the A / SP-CSI report is multiplexed on the PUSCH for only one panel. For example, if HARQ-ACK feedback is multiplexed with A / SP-CSI on the PUSCH for panel 1, then the A / SP-CSI report is multiplexed on the PUSCH for only panel 1.

[0094] Furthermore, for the SDM scheme, FDM scheme A, and SFN-based transmission scheme, when A / SP-CSI is multiplexed with STxMP PUSCH transmission for both panels, the number of resources allocated to A / SP-CSI transmission is determined according to the total resources allocated to PUSCH transmission for both panels.

[0095] For the FDM scheme and the SDM repetition scheme, when A / SP-CSI is multiplexed into STxMP PUSCH transmission for both panels, the number of resources allocated for A / SP-CSI transmission is determined according to the resources allocated for PUSCH transmission for each panel, respectively.

[0096] It should be noted that the above embodiment may also be applied when time domain repetition is applied to STxMP PUSCH.

[0097] In other embodiments, A / SP-CSI may be multiplexed with STxMP PUSCH transmissions through both panels, where the PUSCH transmissions from both panels are repetitions of the same TB, which may have the same RV or different RVs, as shown in FIG. 12B.

[0098] A / SP-CSI multiplexing in STxMP with TD repetition

[0099] Figure 13A illustrates A-CSI or SP-CSI multiplexing in the first TD repetition of an STxMP PUSCH transmission in accordance with some embodiments, and Figure 13B illustrates A-CSI or SP-CSI multiplexing in the first and second TD repetitions of an STxMP PUSCH transmission in accordance with some embodiments. Thus, as shown in Figure 13A, A / SP-CSI is multiplexed only in the first TD repetition of an STxMP PUSCH transmission. Similarly, A / SP-CSI may be multiplexed in the first and second TD repetitions of an STxMP PUSCH transmission as shown in Figure 13B.

[0100] Note that for A / SP-CSI in STxMP PUSCH transmission with TD repetition that does not include transport blocks, the number of repetitions of A / SP-CSI is only one for PUSCH transmission in each panel, which may apply to the case of SP-CSI transmission on PUSCH or activation of SP-CSI on PUSCH without a corresponding PDCCH.

[0101] Furthermore, for PUSCH repetition type B, the UE may expect the same number of symbols for normal repetition and actual repetition. If the number of symbols for normal repetition and actual repetition per panel is different, the UE may drop A-CSI and / or SP-CSI reports.

[0102] Mechanism for PUCCH resource configuration for STxMP operation

[0103] Several STxMP transmission schemes may be considered for PUCCH transmission: FDM, Single Frequency Network (SFN). For example, as mentioned above, the following schemes may be used: FDM-A scheme: Different frequency domain portions of one PUCCH resource are transmitted by two different UE panels. FDM-B scheme: Two FDM-enhanced PUCCH transmission occasions with the same UCI in the same PUCCH format are transmitted from two different UE panels. SFN scheme: The same PUCCH / PUCCH-DMRS is transmitted simultaneously from two different UE panels.

[0104] Furthermore, STxMP PUCCH transmission can be scheduled by either single DCI (sDCI) or multiple DCI (mDCI). If STxMP PUCCH transmission is scheduled by sDCI, PUCCH resources on more than one panel are determined. Furthermore, for the FDM-A scheme, when PUCCH format 3 is used to carry the UCI payload, a specific mechanism can be defined for the transmission scheme to reduce the Peak-to-Average Power Ratio (PAPR).

[0105] Described herein are mechanisms for PUCCH resource configuration for STxMP operation. In particular, PUCCH resource configuration for STxMP operation, frequency resource partitioning for STxMP FDM-A scheme, STxMP FDM-A scheme for PUSCH with PUCCH format 3 and Discrete Fourier transform-spread orthogonal frequency-division multiplexing (DFT-s-OFDM) waveform, and STxMP CDM scheme for PUCCH formats 0 / 1 / 4. In some aspects, a panel ID may be explicitly indicated or configured for a panel for STxMP transmission, or may be implicitly linked to other IDs, such as a control resource set (CORESET) ID, TRP ID, etc.

[0106] PUCCH resource configuration for STxMP operation

[0107] As mentioned above, multiple STxMP transmission schemes, i.e., FDM and SFN, can be considered for PUCCH transmission. STxMP PUCCH transmission can be scheduled by either sDCI or mDCI. If STxMP PUCCH transmission is scheduled by sDCI, PUCCH resources on more than one panel are determined.

[0108] An embodiment of PUCCH resource configuration for STxMP operation is described as follows.

[0109] In some aspects, the following embodiments may be applied to all PUCCH formats, including PUCCH formats 0, 1, 2, 3, and 4.

[0110] In one embodiment, for the sDCI STxMP PUCCH transmission scheme, a PUCCH resource indicator (PRI) may be included in DCI format 1_1 and / or 1_2 for scheduling the PDSCH, and the starting position of the PRI and / or the control channel element (CCE) for the corresponding physical downlink control channel (PDCCH) transmission may be used to determine the PUCCH. Furthermore, more than one transmission occasion or frequency resource from the first and second panels may be included in the PUCCH resource.

[0111] In one option, the next PUCCH resource information element (IE) may be updated to include a second starting PRB index for the first and second hops as shown below: In some aspects, the starting PRB index in the first and second hops in the existing PUCCH resource IE may be used for STxMP PUCCH transmissions from the first panel, and the second starting PRB index in the first and second hops may be used for STxMP PUCCH transmissions from the second panel. In some aspects, if frequency hopping is disabled, the second starting PRB index for the second hop is not applicable.

number

[0112] In some aspects, the second starting PRB index in the first and second hop may not be present in the PUCCH Resources IE, which may indicate SFN operation for STxMP PUCCH transmission. Alternatively, the second starting PRB index in the first and second hop may be equal to the starting PRB index in the first and second hop in the PUCCH Resources IE, which may also indicate SFN operation for STxMP PUCCH transmission.

[0113] In another option, the Next PUCCH Resources IE may be updated to include the PRB distance between the PUCCH transmissions from the first and second panels as shown below: In some aspects, if frequency hopping is enabled for the PUCCH transmissions, the same PRB distance between the PUCCH transmissions from the first and second panels applies for the PUCCH transmissions of the second hop.

number

[0114] In some aspects, if the PRB distance is not present in the PUCCH resource IE, this may indicate SFN operation for STxMP PUCCH transmission.

[0115] 14 illustrates the PRB distance of the PUCCH transmission from the first and second panel transmissions according to some embodiments. In the example shown in FIG. 14, the PRB distance is set between the PUCCH transmissions from the first and second panels.

[0116] In other embodiments, the Medium Access Control-Control Element (MAC-CE) for PUCCH spatial relationship activation / deactivation for multiple TRP PUCCH repetitions may be extended to support STxMP PUCCH transmission. In particular, a panel ID may be included in the PUCCH spatial relationship activation / deactivation MAC CE for multiple TRP PUCCH repetitions. In some aspects, a "0" bit may indicate the first panel, while a "1" bit may indicate the second panel.

[0117] Figure 15 illustrates a panel ID according to some embodiments. The panel ID in Figure 15 is in the PUCCH spatial relationship activation / deactivation MAC-CE. In Figure 15, the first reserved bit in the Oct per spatial relationship information ID is updated for the panel ID. In some aspects, bit "0" may indicate the first panel, while bit "1" may indicate the second panel.

[0118] Figure 16 illustrates another panel ID according to some embodiments. Similar to Figure 15, the panel ID in Figure 16 is in the PUCCH spatial relationship activation / deactivation MAC-CE. In Figure 16, the second reserved bit in the Oct per spatial relationship information ID is updated for the panel ID. In some aspects, bit "0" may indicate the first panel, while bit "1" may indicate the second panel.

[0119] In another option, a new MAC-CE may be defined for PUCCH spatial relationship activation and deactivation for STxMP PUCCH transmission. The MAC CE may include one or more of the following parameters: serving cell ID, BWP ID, panel ID, PUCCH resource ID, first associated spatial relationship information ID for the first panel, and second associated spatial relationship information ID for the second panel.

[0120] In other embodiments, the MAC-CE for PUCCH power control set updating for multiple TRP PUCCH repetitions may be extended to STxMP PUCCH transmissions. In particular, a panel ID may be included in the MAC-CE for PUCCH power control set updating for multiple TRP PUCCH repetitions. In some aspects, a "0" bit may indicate the first panel, while a "1" bit may indicate the second panel.

[0121] Figure 17 illustrates another panel ID according to some embodiments. The panel ID in Figure 17 is in the PUCCH power control set update MAC-CE for STxMP PUCCH operation. In Figure 17, the first and second reserved bits in the Oct of the PUCCH power control ID are updated for the panel ID. In some aspects, bit "0" may indicate the first panel, while bit "1" may indicate the second panel.

[0122] In another option, a new MAC-CE may be defined for PUCCH power control set updating for STxMP PUCCH transmission. The MAC CE may include one or more of the following parameters: serving cell ID, BWP ID, panel ID, PUCCH resource ID, first associated PUCCH power control set ID for the first panel, and second associated PUCCH power control set ID for the second panel.

[0123] In other embodiments, for an sDCI STxMP PUCCH transmission scheme, the first and second PRIs may be included in DCI format 1_1 and / or 1_2 for scheduling the PDSCH, and the starting positions of the first and second PRIs and / or CCEs for the corresponding PDCCH transmission may be used to determine the first and second PUCCH resources from the first and second panels, respectively.

[0124] In another option, the first PRI is included in DCI format 1_1 and / or 1_2 for scheduling the PDSCH. Furthermore, a differentiated PRI may also be included in the same DCI, and the second PRI may be determined based on the first PRI and the differentiated PRI.

[0125] In some aspects, panel information, including the panel ID, may be configured as part of the PUCCH resource configuration. In one example, the next PUCCH resource IE may be updated to include the panel ID as shown.

number

[0126] In another example, the next PUCCH-SpatialRelationInfo IE may be updated to include the panel ID as shown.

number

[0127] For this option, the UE may expect the same PUCCH format, start symbol and number of symbols, and number of PRBs to be used for STxMP PUCCH transmission.

[0128] In other embodiments, for the sDCI STxMP PUCCH transmission scheme, a PRI may be included in DCI format 1_1 and / or 1_2 for scheduling a PDCCH, and the starting position of the PRI and / or the CCE for the corresponding PDCCH transmission may be used to determine a set of PUCCH resources. In particular, the group of PUCCH resources includes the first and second PUCCH resources from the first and second panels, respectively.

[0129] For this option, the panel ID may be included as part of the PUCCH resource configuration or the PUCCH spatial relationship information configuration.

[0130] Frequency resource partitioning for STxMP FDM-A schemes

[0131] An embodiment of frequency resource division for the STxMP FDM-A scheme is given as follows.

[0132] In some aspects, the STxMP FDM-A PUCCH transmission scheme may be applied to PUCCH formats 2 and / or 3.

[0133] In one embodiment, for an FDM-A STxMP PUCCH scheme, the frequency resources for PUCCH transmission in the first and second panels may be consecutive. Furthermore, the number of PRBs configured for PUCCH format 2 is N PRB Assuming that, the PUCCH transmissions in the first and second panels are respectively

number

[0134] In some aspects, if frequency hopping is enabled, this may also apply to frequency resources within the second hop for PUCCH transmissions of the first and second panels.

[0135] Figure 18 illustrates frequency resources for PUCCHs in the first and second panels for STxMP operation, according to some embodiments. In Figure 18, it is assumed that 10 PRBs are allocated to PUCCH format 2. In this case, the first five PRBs are allocated to PUCCH transmission in the first panel, while the second two PRBs are allocated to PUCCH transmission in the second panel.

[0136] In other embodiments, for an FDM-A STxMP PUCCH scheme, the frequency resources for PUCCH transmission in the first and second panels may be interleaved, in particular, the frequency resources for PUCCH transmission in the first panel are allocated every K even PRBs, while the frequency resources for PUCCH transmission in the second panel are allocated every K odd PRBs, or vice versa.

[0137] In some aspects, K may be predefined in the standard, configured by higher layers (higher layer signaling) via NR RMSI, NR OSI, or dedicated RRC signaling, dynamically indicated in DCI, or a combination thereof. In another option, K may be determined according to the number of PRBs configured for PUCCH resources. In one example, K=1 or 2.

[0138] STxMP FDM-A scheme for PUSCH with PUCCH format 3 and DFT-s-OFDM waveform

[0139] An embodiment of the STxMP FDM-A scheme for PUSCH with PUCCH format 3 and DFT-s-OFDM waveform is given as follows.

[0140] In one embodiment, for a STxMP FDM-A scheme for PUSCH with PUCCH format 3 and a DFT-s-OFDM waveform, the modulated symbols for PUSCH with PUCCH format 3 and a DFT-s-OFDM waveform are equally divided into two parts, and the first and second parts are input to a first and second DFT, respectively. The modulated symbols after the DFT operation are then mapped to the allocated resources for PUCCH and PUSCH transmission in the first and second panels, respectively.

[0141] Figure 19 illustrates separate Discrete Fourier Transform (DFT) operations on modulated symbols for the STxMP PUCCH FDM-A scheme, according to some embodiments. In Figure 19, first and second DFTs are applied to the split modulated symbols for PUCCH transmission in the first and second panels, respectively.

[0142] In another embodiment, for PUCCH format 3 and an STxMP FDM-A scheme for PUSCH with a DFT-s-OFDM waveform, a single DFT is applied to the modulated symbols for PUCCH and PUSCH transmission. Further, the modulated symbols after the DFT operation are equally divided into two parts, and the first and second parts are mapped to the allocated resources for PUCCH and PUSCH transmission in the first and second panels, respectively.

[0143] Figure 20 illustrates a single DFT operation on modulated symbols for a STxMP PUCCH FDM-A scheme, in accordance with some embodiments, in which a single DFT is applied to modulated symbols for PUCCH and PUSCH transmissions.

[0144] STxMP CDM scheme for PUCCH formats 0 / 1 / 4

[0145] An embodiment of the STxMP CDM scheme for PUCCH formats 0 / 1 / 4 is given as follows:

[0146] In one embodiment, for PUCCH formats 0 and 1, different cyclic shifts may be configured for STxMP PUCCH transmissions from the first and second panels, respectively. In some aspects, an initial cyclic shift in the IE of existing PUCCH formats 0 and 1 may be used for STxMP PUCCH transmissions from the first panel, and a second initial cyclic shift may be used for STxMP PUCCH transmissions from the second panel.

[0147] In one option, the following PUCCH format 0 and PUCCH format 1 IEs may be updated to include the second initial cyclic shift as shown below:

number

[0148] In other embodiments, for PUCCH format 4, different orthogonal cover code (OCC) indices may be configured for STxMP PUCCH transmissions from the first and second panels, respectively. In some aspects, an OCC index in an IE of existing PUCCH format 4 may be used for STxMP PUCCH transmissions from the first panel, and a second OCC index may be used for STxMP PUCCH transmissions from the second panel.

[0149] In one option, the next PUCCH format 4 may be updated to include a second OCC as shown below.

number

[0150] Precoding instructions and maximum rank settings for STxMP

[0151] As mentioned above, multiple antennas may be equipped on the UE and each panel of the TRP. Therefore, the UE may perform precoding of transmitted data and control information to achieve higher data rates and reliability. The precoding matrix for UE transmission may be either predefined as a codebook or calculated by the UE. In other words, two transmission modes are supported: codebook (CB)-based transmission and non-codebook (nCB)-based transmission. For CB-based transmission, the gNB provides a transmit precoding matrix indication to the UE in the DCI. The UE selects a PUSCH transmit precoder from a set of codebooks using an indicator called the transmitting precoding matrix indicator (TPMI). For nCB-based transmission, the UE determines its PUSCH precoder based on CSI-RS measurements from the downlink and the number of transmission instances based on the SRS resource indication (SRI) field from the DCI.

[0152] In summary, for CB-based transmission, the UE determines its PUSCH transmission precoder based on SRI, TPMI, and transmission rank. For nCB-based transmission, the UE may determine its PUSCH precoder and transmission rank based on SRI when multiple SRS resources are configured. Note that SRI is a DCI field, and TPMI and transmission rank are given by a DCI field called Precoding information and number of layers (PINL).

[0153] However, the above precoding instruction methodology is applicable to PUSCH transmission based on a single TRP and PUSCH repetition based on multiple TRPs (two PUSCH repetitions are transmitted on different time domain resources). In simultaneous multiple TRP multiple panel PUSCH transmission, there may be more PUSCH transmission schemes and more conditions / constraints under different transmission schemes.

[0154] Furthermore, in Rel-17 multi-TRP PUSCH transmission, the maxRank set by RRC signaling applies to both PUSCH repetitions. However, in SDM STxMP PUSCH transmission, the two PUSCHs transmitted from the two panels may have different ranks. Therefore, it is necessary to consider how to set the maximum rank for the two panels.

[0155] Several methods are presented herein to enhance the precoding indication, i.e., SRI and PINL fields, and methods for setting the maximum rank for simultaneous multi-TRP multi-panel PUSCH (SxPUSCH) transmission, where SxPUSCH is the same as STxMP PUSCH.

[0156] Maximum rank indication for STxMP transmission based on single DCI

[0157] In one embodiment, two maximum ranks, eg, maxRank and maxRank2, can be set for panel 1 and panel 2, respectively.

[0158] In other embodiments, a legacy setting, e.g., makRank, may be reused for the overall maximum rank between two panels. For example, if maxRank=3, then the example combinations 1+1, 1+2, 2+1 may be transmitted.

[0159] In other embodiments, if two maximum ranks are configured, the maximum ranks may be mapped to different UE capability value sets.

[0160] DCI field determination for STxMP PUSCH based on single DCI

[0161] In one embodiment, in the case of nCB-based STxMP PUSCH transmission and CB-based STxMP PUSCH transmission with different numbers of ports within the configured SRS resources, two SRI fields may be used to indicate two SRS resources from two SRS resource sets corresponding to two TRPs, respectively, but in the case of CB-based STxMP PUSCH transmission with the same number of ports within the configured SRS resources, only one SRI field may be used in the DCI.

[0162] In another embodiment, in the case of nCB-based STxMP PUSCH transmission and CB-based STxMP PUSCH transmission with different numbers of ports within the configured SRS resources, two SRI fields may be used to indicate two SRS resources from two SRS resource sets corresponding to two TRPs, respectively, but in the case of CB-based STxMP PUSCH transmission with the same number of ports within the configured SRS resources, the SRI field is not indicated in the DCI.

[0163] In another embodiment, two DCI fields of the SRI are indicated for both CB-based and nCB-based PUSCH transmissions.

[0164] In some embodiments, the electronic device, network, system, chip, or component of the above figures, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. One such process is depicted in FIG. 21. FIG. 21 depicts a flowchart of multi-TRP transmission based on codebook (CB) and non-codebook (nCB) according to some embodiments. Specifically, process 2100 of FIG. 21 may include or relate to a method performed by a UE, one or more elements of a UE, and / or an electronic device that includes or implements a UE. Process 2100 may include, at operation 2102, determining that a first transmission from a first antenna panel to a first TRP and a second transmission from a second antenna panel to a second TRP should occur; at operation 2104, determining whether the first transmission and the second transmission are CB or nCB; and at operation 2106, transmitting the first transmission and the second transmission based on whether the first transmission and the second transmission are CB or nCB.

[0165] 22 illustrates a flowchart of PUCCH transmission according to some embodiments. Process 2200 of FIG. 22 may include or relate to a method performed by a UE, one or more elements of a UE, and / or an electronic device that includes or implements a UE. Process 2200 may include, at operation 2202, identifying a first starting PRB and a second starting PRB in a configuration message received from a base station, and, at operation 2204, transmitting a first PUCCH from the first panel based on the first starting PRB and transmitting a second PUCCH from the second panel based on the second starting PRB.

[0166] 23 illustrates another flowchart of a PUCCH transmission according to some embodiments. Process 2300 of FIG. 23 may include or relate to a method performed by a base station, one or more elements of a base station, and / or an electronic device that includes or implements a base station. Process 2300 of FIG. 23 may include, at operation 2302, sending a configuration message to a UE that includes an indication of a first starting PRB and an indication of a second starting PRB, and, at operation 2304, specifying, from the UE, a first PUCCH transmission based on the first starting PRB from the first panel and a second PUCCH transmission based on the second starting PRB from the second panel.

[0167] 24 depicts a flowchart of PUSCH transmission according to some embodiments. Process 2400 of FIG. 24 may include or relate to a method performed by a base station, one or more elements of a base station, and / or an electronic device that includes or implements a base station. Process 2400 of FIG. 24 includes, at operation 2402, receiving STxMP configuration information for PUSCH transmission. The process further includes, at operation 2404, encoding the PUSCH for STxMP based on the configuration information.

[0168] example

[0169] Example 1 is an apparatus for a user equipment (UE), the apparatus comprising a memory and a processing circuit, the processing circuit comprising: receiving at least one downlink control information (DCI) for scheduling simultaneous transmission with multiple panels (STxMP) uplink (UL) transmissions; determining, from at least one DCI, whether time domain (TD) repetition should be applied to the UL; Sending UL transmissions to multiple Transmit / Receive Points (TRPs) based on determining whether TD repetition should be applied Configure the UE as follows: The memory is a device configured to store the DCI.

[0170] In Example 2, the subject matter of Example 1 includes wherein the processing circuitry is further configured to use a type A slot-based repetition for UL transmission.

[0171] In Example 3, the subject matter of Examples 1-2 includes wherein the processing circuitry is further configured to use Type B back-to-back repetition for UL transmission.

[0172] In Example 4, the subject matter of Examples 1-3 includes the processing circuitry further configured to use multi-panel transmission for the UL transmission, wherein the UL transmission uses the same frequency resources for spatial domain multiplexing (SDM) and different frequency resources for frequency domain multiplexing (FDM).

[0173] In Example 5, the subject matter of Examples 1-4 includes: the UL transmission is a physical uplink shared channel (PUSCH) transmission; and the processing circuitry is further configured to: in the first mode, associate the PUSCH transmission in the first panel with a first sounding reference signal (SRS) resource set and associate the PUSCH transmission in the second panel with a second SRS resource set; and in the second mode, associate the PUSCH transmission in the first panel with the second SRS resource set and associate the PUSCH transmission in the second panel with the first SRS resource set.

[0174] In Example 6, the subject matter of Example 5 includes wherein the processing circuitry is further configured to switch between the first mode and the second mode based on an SRS resource set indication in downlink control information (DCI).

[0175] In Example 7, the subject matter of Examples 1-6 includes wherein the processing circuitry is further configured to determine whether panel switching is enabled during the TD repetition based on a downlink control information (DCI) field.

[0176] In Example 8, the subject matter of Examples 1-7 includes the processing circuitry being further configured to determine, per panel, a redundancy version (RV) for the STxMP physical uplink shared channel (PUSCH) with and without TD repetition based on the single DCI, the RV per panel depending on whether each panel is configured to transmit the same transport block (TB) or different TB, and the single DCI including the number of TD repetitions.

[0177] In Example 9, the subject matter of Example 8 includes the processing circuitry being further configured to determine an RV for each panel based on the RV offset value within the single DCI, the RV depending on whether each panel is configured to transmit the same TB or different TB.

[0178] In Example 10, the subject matter of Examples 1-9 includes the processing circuitry further configured to use frequency domain multiplexing (FDM) for the STxMP UL transmission, and contiguous physical resource blocks (PRBs) within the UL bandwidth portion (BWP) are allocated for UL transmission by different panels.

[0179] In Example 11, the subject matter of Example 10 includes the processing circuitry being further configured to determine a frequency resource allocation for a UL transmission of one of the panels from a frequency domain resource allocation (FDRA) field in at least one DCI that schedules the UL transmission.

[0180] In Example 12, the subject matter of Example 11 includes the processing circuitry being further configured to determine a frequency offset between starting PRBs of UL transmissions on the panel from at least one of higher layer signaling via at least one of Minimum Remaining System Information (RMSI), Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling, or dynamic indication in at least one DCI.

[0181] In Example 13, the subject matter of Examples 11-12 includes wherein the processing circuitry is further configured to determine a frequency offset between starting PRBs of UL transmissions at the panel based on a frequency offset configured for frequency hopping within a slot, between repetitions, or between slots of the UL transmissions.

[0182] In Example 14, the subject matter of Examples 1-13 includes the processing circuitry further configured to use frequency domain multiplexing (FDM) for the STxMP UL transmission, and interleaved physical resource blocks (PRBs) within the UL bandwidth portion (BWP) are allocated for UL transmission by different panels.

[0183] In Example 15, the subject matter of Example 14 includes the processing circuitry further configured to determine the number of PRBs for each panel from at least one of higher layer signaling via at least one of Minimum Remaining System Information (RMSI), Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling, dynamic indications in at least one DCI, or a resource block group (RBG) size when uplink resource allocation type 0 is used for frequency resource allocation.

[0184] In Example 16, the subject matter of Examples 14-15 includes, wherein the processing circuitry is further configured to determine frequency resources for each panel from a frequency domain resource allocation (FDRA) field in the single DCI when uplink resource allocation type 0 or 1 is used for frequency resource allocation.

[0185] In Example 17, the subject matter of Examples 1-16 includes wherein the processing circuitry is further configured to determine, from a time domain resource allocation (TDRA) field in the single DCI, a number of TD repetitions, a mapping type, and a start and length indicator value (SLIV) for the TDRA.

[0186] In Example 18, the subject matter of Examples 1-17 includes, wherein the processing circuitry is further configured to determine, from the plurality of DCIs, a frequency domain multiplexing (FDM) STxMP UL transmission with TD repetition with and without at least one of frequency switching or panel switching.

[0187] In Example 19, the subject matter of Example 18 includes the processing circuitry being further configured to determine, for a TD repetition in which there is at least one of a frequency switch or a panel switch, two simultaneous single TRP repetition processes with frequency hopping or two simultaneous single DCI-based multi-TRP repetition processes without frequency hopping.

[0188] In Example 20, the subject matter of Examples 18-19 includes, wherein the processing circuitry is further configured to determine, for a TD repetition without at least one of frequency switching or panel switching, two simultaneous single TRP repetition processes without frequency hopping or two simultaneous single DCI-based multi-TRP repetition processes with frequency hopping.

[0189] In Example 21, the subject matter of Examples 1-20 includes, wherein the processing circuitry is further configured to determine whether to use spatial domain multiplexing (SDM) STxMP UL transmission with TD repetition using the same frequency resources allocated per panel and to switch panel association at each STxMP transmission occasion.

[0190] In Example 22, the subject matter of Example 21 includes the processing circuitry being further configured to determine, from a time domain resource allocation (TDRA) field in the single DCI, a number of TD repetitions, a mapping type, and a start and length indicator value (SLIV) for the TDRA of the SDM STxMP UL transmission with TD repetition.

[0191] In Example 23, the subject matter of Examples 21-22 is further characterized in that the processing circuitry receives from the plurality of DCIs: TD repetition with panel switching using two simultaneous single-TRP repetition processes with panel switching or two simultaneous single-DCI-based multi-TRP repetition processes without panel switching; or TD repetition without panel switching using two simultaneous single-TRP repetition processes without panel switching or two simultaneous single-DCI-based multi-TRP repetition processes with panel switching further configured to determine:

[0192] In Example 24, the subject matter of Examples 1-23 is further characterized in that the processing circuitry uses spatial domain multiplexing (SDM) STxMP UL transmission with TD repetition with beam cycling; using two different sounding reference signal (SRS) resource sets for STxMP UL transmission with beam cycling per panel, the SRS resource set indication being configured to indicate whether beam cycling is enabled for the STxMP UL transmission, or using the same two SRS resource sets for STxMP UL transmission with beam cycling per panel, the UL transmission per panel being associated with a different SRS resource set. The method further comprises:

[0193] In Example 25, the subject matter of Examples 1-24 is further configured to: multiplex aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) transmissions with the STxMP UL transmissions across the multiple panels; In the case of a transmission scheme based on a spatial domain multiplexing (SDM) scheme, a frequency domain multiplexing (FDM) scheme A, or a single frequency network (SFN), the number of resources allocated for A-CSI or SP-CSI transmission is determined according to the total resources allocated for STxMP UL transmission for both panels; In the case of the FDM scheme B and the SDM repetition scheme, the number of resources allocated for A-CSI or SP-CSI transmission is determined according to a resource allocation for STxMP UL transmission per panel, respectively.

[0194] In Example 26, the subject matter of Examples 1-25 includes wherein the processing circuitry is further configured to multiplex aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) transmissions on only the first TD repetition of the STxMP UL transmission or on the first TD repetition of the STxMP UL transmission and the second TD repetition of the STxMP UL transmission.

[0195] In Example 27, the subject matter of Examples 1-26 includes wherein the processing circuitry is further configured to determine an independent maximum rank per panel from the single DCI.

[0196] In Example 28, the subject matter of Example 27 includes mapping the maximum rank to a different set of UE feature values.

[0197] In Example 29, the subject matter of Examples 1-28 includes wherein the processing circuitry is further configured to determine, from a sounding reference signal (SRS) resource indication (SRI) field in the at least one DCI, an SRS resource in the SRS resource set corresponding to the TRP separately for non-codebook (nCB)-based STxMP UL transmission and CB-based STxMP UL transmission with different numbers of ports in the SRS resource.

[0198] In Example 30, the subject matter of Examples 1-29 includes: the processing circuitry is further configured to determine, from a single sounding reference signal (SRS) resource indication (SRI) field in the at least one DCI, an SRS resource in the SRS resource set corresponding to the TRP for CB-based STxMP UL transmission with an equal number of ports in the SRS resource.

[0199] In Example 31, the subject matter of Examples 1-30 includes: the processing circuitry is further configured to determine, without using a sounding reference signal (SRS) resource indication (SRI) field in the at least one DCI, an SRS resource in the SRS resource set corresponding to the TRP for CB-based STxMP UL transmission with the same number of ports in the SRS resource.

[0200] In Example 32, the subject matter of Examples 1-31 includes wherein the processing circuitry is further configured to determine, from a distinct sounding reference signal (SRS) resource indication (SRI) field in the at least one DCI, an SRS resource in the SRS resource set corresponding to the TRP for non-codebook (nCB)-based STxMP UL transmission and for CB-based STxMP UL transmission independent of the number of ports in the SRS resource.

[0201] In Example 33, the subject matter of Examples 1-32 includes the processing circuitry being further configured to receive, from a fifth-generation NodeB, a first starting physical resource block (PRB) and a second starting PRB of physical uplink control channel (PUCCH) resources, and transmit a multi-panel (STxMP) PUCCH transmission from the first panel using the first starting PRB simultaneously with a PUCCH from the second panel using the second starting PRB.

[0202] In Example 34, the subject matter of Example 33 includes wherein the processing circuitry is further configured to use more than one transmission occasion or frequency resource from the first panel and the second panel within the PUCCH resource.

[0203] In Example 35, the subject matter of Examples 33-34 includes the processing circuitry being further configured to use a first starting PRB index for the first and second hops in a PUCCH resource information element (IE) for STxMP PUCCH transmission from the first panel and a second starting PRB index for the first and second hops for STxMP PUCCH transmission from the second panel.

[0204] In Example 36, the subject matter of Examples 33-35 includes wherein the processing circuitry is further configured to determine, from the PUCCH resources, a PRB distance between the STxMP PUCCH transmissions from the first panel and the second panel.

[0205] In Example 37, the subject matter of Examples 33-36 includes wherein the processing circuitry is further configured to determine a panel identifier (ID) from at least one of medium access control-control element (MAC-CE), PUCCH resource configuration, or PUCCH spatial relationship information for PUCCH spatial relationship activation / deactivation or PUCCH power control set update for the multiple TRP PUCCH recurrences.

[0206] In Example 38, the subject matter of Examples 33-37 includes, in a single DCI STxMP PUCCH transmission scheme, first and second PUCCH resource indicators (PRIs) are included in DCI formats 1_1 and / or 1_2 for scheduling a physical downlink shared channel (PDSCH), and the processing circuitry is further configured to use at least one of the first and second PRIs or starting positions of control channel elements (CCEs) for the corresponding PDCCH transmission to determine the first and second PUCCH resources from the first and second panels, respectively.

[0207] In Example 39, the subject matter of Examples 33-38 includes wherein the processing circuitry is further configured to use contiguous frequency resources for STxMP PUCCH transmission of the first and second panels for a frequency domain multiplexing (FDM)-A STxMP PUCCH scheme.

[0208] In Example 40, the subject matter of Examples 33-39 includes wherein the processing circuitry is further configured to use interleaved frequency resources for STxMP PUCCH transmission of the first and second panels for a frequency domain multiplexing (FDM)-A STxMP PUCCH scheme.

[0209] In Example 41, the subject matter of Examples 33-40 includes the processing circuitry being further configured, for a STxMP frequency-domain multiplexing (FDM)-A scheme for PUCCH Format 3 and a physical uplink shared channel (PUSCH) with a discrete Fourier transform-spread orthogonal frequency-division multiplexing (DFT-s-OFDM) waveform, to equally divide modulated symbols for PUCCH and PUSCH transmission, each portion of the modulated symbols being provided to a different DFT.

[0210] In Example 42, the subject matter of Examples 33-41 includes wherein the processing circuitry is further configured to use a single DFT on modulated symbols for PUCCH and PUSCH transmission for a STxMP FDM-A scheme for PUCCH format 3 and a physical uplink shared channel (PUSCH) with a discrete Fourier transform-spread orthogonal frequency-division multiplexing (DFT-s-OFDM) waveform.

[0211] In Example 43, the subject matter of Examples 33-42 includes wherein the processing circuitry is further configured to use different cyclic shifts for STxMP PUCCH transmissions from the first and second panels for PUCCH formats 0 and 1.

[0212] In Example 44, the subject matter of Examples 33-43 includes wherein the processing circuitry is further configured to use different orthogonal cover code (OCC) indices for STxMP PUCCH transmissions from the first and second panels for PUCCH format 4.

[0213] Example 45 is at least one machine-readable medium containing instructions that, when executed by a processing circuit, cause the processing circuit to perform the operations to be performed of any of Examples 1-44.

[0214] Example 46 is an apparatus including the means to be implemented in any one of Examples 1 to 44.

[0215] Example 47 is a system to be implemented according to any one of Examples 1 to 44.

[0216] Example 48 is a method to be carried out according to any of Examples 1 to 44.

[0217] Although the 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 the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative and not a limiting sense. The accompanying drawings, which form a part of the specification, show, by way of example, and not by way of limitation, specific embodiments in which the subject matter may be practiced. The represented embodiments are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Structural and logical substitutions may be made without departing from the scope of the present disclosure, such that other embodiments may be utilized and derived therefrom. Therefore, this detailed description is not to be construed in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.

[0218] Subject matter may be referred to herein, individually and / or collectively, by the term "embodiment" for convenience only; this is not intended to voluntarily limit the scope of the present application to any single inventive concept when multiple inventive concepts are in fact disclosed. Accordingly, although specific embodiments have been illustrated and described herein, it should be understood that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiment shown. The present disclosure is intended to cover any adaptations or modifications of the various embodiments. Combinations of the above embodiments, as well as other embodiments not specifically described herein, will be apparent to those skilled in the art upon reviewing the above description.

[0219] The terms "a" and "an" are used herein, as is common in patent documents, to indicate one or more, regardless of other instances or uses of "at least one" or "one or more." The term "or" is used herein to refer to a non-exclusive logical or, such as "A or B" including "A but not B," "B but not A," or "A and B," unless otherwise specified. The terms "including" and "in which" are used herein as the plain-English equivalents of the terms "comprising" and "wherein," respectively. Also, in the following claims, the terms "including" and "comprising" are open-ended, meaning that a system, UE, article, composition, formulation, or process containing elements in addition to those recited after such term in a claim is still considered within the scope of that claim. Furthermore, in the following claims, the terms "first," "second," "third," etc., are used merely as labels and do not impose numerical requirements on their objects. As indicated herein, although the term "a" is used herein, different embodiments may use one or more of the associated elements. For example, the term "a processor" configured to perform certain operations includes both a single processor configured to perform all of the operations and multiple processors individually configured to perform some or all of the operations (which may overlap) such that all of the operations are performed by a combination of processors. Furthermore, the term "comprises" may be considered to be interpreted as "comprising at least" the preceding listed elements.

[0220] This Abstract of the Disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, the foregoing Detailed Description may reveal that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as an independent embodiment.

[0221] [Priority claim] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 390,526, filed July 19, 2022, U.S. Provisional Patent Application No. 63 / 396,362, filed August 9, 2022, and U.S. Provisional Patent Application No. 63 / 410,111, filed September 26, 2022, which are incorporated herein by reference in their entireties.

Claims

1. 1. An apparatus for a user equipment (UE), comprising: Decoding at least one downlink control information (DCI) for scheduling uplink (UL) transmissions via simultaneous transmission over multiple panels (STxMP) from a fifth generation NodeB (gNB); determining, from the at least one DCI, whether time domain (TD) repetition should be applied to the STxMP UL transmission; a processing circuit configured to encode the STxMP UL transmission for transmission to multiple transmission / reception points (TRPs) based on a determination of whether the TD repetition should be applied; a memory configured to store the DCI; A device having:

2. the processing circuitry is further configured to use multi-panel transmission for the STxMP UL transmission, the STxMP UL transmission using the same frequency resource for spatial domain multiplexing (SDM) and different frequency resource for frequency domain multiplexing (FDM).

10. The apparatus of claim 1.

3. The STxMP UL transmission is a Physical Uplink Shared Channel (PUSCH) transmission; The processing circuitry In a first mode, PUSCH transmission in a first panel is associated with a first sounding reference signal (SRS) resource set, and PUSCH transmission in a second panel is associated with a second SRS resource set; In a second mode, a PUSCH transmission in the first panel is associated with a second SRS resource set, and a PUSCH transmission in the second panel is associated with the first SRS resource set; Switching between the first mode and the second mode based on an SRS resource set indication in downlink control information (DCI) further configured as follows:

3. The device according to claim 1 or 2.

4. The processing circuitry is further configured to determine whether panel switching is enabled during the TD repetition based on a downlink control information (DCI) field.

3. The device according to claim 1 or 2.

5. The processing circuitry For each panel, determine a redundancy version (RV) of an STxMP physical uplink shared channel (PUSCH) with and without TD repetition based on a single DCI, the RV for each panel depending on whether each panel is configured to transmit the same transport block (TB) or different TVs, and the single DCI indicates the number of TD repetitions; Determine an RV offset for each panel based on the RV offset value in the single DCI, depending on whether each panel is configured to transmit the same TB or different TB. It is configured as follows:

3. The device according to claim 1 or 2.

6. The processing circuitry using frequency domain multiplexing (FDM) for the STxMP UL transmission, and contiguous physical resource blocks (PRBs) within a UL bandwidth portion (BWP) are allocated for the STxMP UL transmission by different panels; determining a frequency resource allocation for the STxMP UL transmission of one of the panels from a Frequency Domain Resource Allocation (FDRA) field in the at least one DCI for scheduling the STxMP UL transmission; determining a frequency offset between starting PRBs of the STxMP UL transmissions at the panel from at least one of higher layer signaling via at least one of Residual Minimum System Information (RMSI), Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling, or a dynamic indication in the at least one DCI; Determine a frequency offset between starting PRBs of the STxMP UL transmission in the panel based on a frequency offset set for intra-slot, inter-repetition, or inter-slot frequency hopping of the STxMP UL transmission. further configured as follows:

3. The device according to claim 1 or 2.

7. The processing circuitry using frequency domain multiplexing (FDM) for the STxMP UL transmission, and interleaved physical resource blocks (PRBs) within a UL bandwidth portion (BWP) are allocated for the STxMP UL transmission by different panels; determining the number of PRBs for each panel from at least one of higher layer signaling via at least one of Residual Minimum System Information (RMSI), Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling, or a dynamic indication in a single DCI, or a Resource Block Group (RBG) size when uplink resource allocation type 0 is used for frequency resource allocation; or Determining frequency resources per panel from a frequency domain resource allocation (FDRA) field in a single DCI when uplink resource allocation type 0 or 1 is used for frequency resource allocation Execute at least one of the following: further configured as follows:

3. The device according to claim 1 or 2.

8. The processing circuitry determining, from the plurality of DCIs, a frequency domain multiplexing (FDM) STxMP UL transmission with TD repetition with and without at least one of frequency switching or panel switching; In the case of a TD repetition in which at least one of the frequency switching or panel switching occurs, determining two simultaneous single-TRP repetition processes with frequency hopping or two simultaneous multi-TRP repetition processes based on a single DCI without frequency hopping; or In the case of TD repetition without at least one of the frequency switching or panel switching, determining two simultaneous single TRP repetition processes without frequency hopping or two simultaneous multi-TRP repetition processes based on a single DCI with frequency hopping. Execute at least one of the following: further configured as follows:

3. The device according to claim 1 or 2.

9. The processing circuitry Using spatial domain multiplexing (SDM) STxMP UL transmission with TD repetition using the same frequency resources allocated to each panel among the multiple panels; determining whether to switch panel associations at each STxMP transmission occasion; determining a number of TD repetitions, a mapping type, and a length indicator value (SLIV) for the TDRA of said SDM STxMP UL transmission with TD repetitions from a time domain resource allocation (TDRA) within a single DCI; or From multiple DCIs: TD repetition with panel switching using two simultaneous single-TRP repetition processes with panel switching or two simultaneous multi-TRP repetition processes based on a single DCI without panel switching; or TD repetition without panel switching using two simultaneous single TRP repetition processes without panel switching or two simultaneous multi-TRP repetition processes based on a single DCI with panel switching To determine Execute at least one of the following: further configured as follows:

3. The device according to claim 1 or 2.

10. The processing circuit is Using spatial domain multiplexing (SDM) STxMP UL transmission with TD repetition with beam cycling, using two different sounding reference signal (SRS) resource sets for the STxMP UL transmission with beam cycling per panel, wherein an SRS resource set indication is configured to indicate whether beam cycling is enabled for the STxMP UL transmission; or The same two SRS resource sets are used for the STxMP UL transmission with beam cycling per panel, and the UL transmission per panel is associated with a different SRS resource set. Execute one of the further configured as follows:

3. The device according to claim 1 or 2.

11. the processing circuitry is further configured to multiplex aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) transmissions with the STxMP UL transmissions across multiple panels; In the case of a transmission scheme based on a spatial domain multiplexing (SDM) scheme, a frequency domain multiplexing (FDM) scheme A, or a single frequency network (SFN), the number of resources allocated for the A-CSI or SP-CSI transmission is determined according to the total resources allocated for the STxMP UL transmission for both panels; In the case of FDM scheme B and SDM repetition scheme, the number of resources allocated for the A-CSI or SP-CSI transmission is determined according to a resource allocation for the STxMP UL transmission per panel, respectively.

3. The device according to claim 1 or 2.

12. the processing circuitry is further configured to multiplex an aperiodic channel state information (A-CSI) or semi-persistent CSI (SP-CSI) transmission onto only a first TD repetition of the STxMP UL transmission, or onto the first TD repetition of the STxMP UL transmission and a second TD repetition of the STxMP UL transmission.

3. The device according to claim 1 or 2.

13. the processing circuitry is further configured to determine an independent maximum rank for each panel from a single DCI; The maximum rank is mapped to a different set of UE capability values.

3. The device according to claim 1 or 2.

14. The processing circuitry determining, from a Sounding Reference Signal (SRS) Resource Indication (SRI) field in the at least one DCI, SRS resources in an SRS resource set corresponding to the TRP separately for non-codebook (nCB)-based STxMP UL transmission and CB-based STxMP UL transmission with different numbers of ports in the SRS resources; or Determine an SRS resource in an SRS resource set corresponding to the TRP from a single SRI field in the at least one DCI for STxMP UL transmission based on CB by the same number of ports in the SRS resource; or determining an SRS resource in an SRS resource set corresponding to the TRP for STxMP UL transmission based on CB by the same number of ports in the SRS resource without using any SRI field in the at least one DCI; further configured to perform at least one of 3. The device according to claim 1 or 2.

15. The processing circuitry Decode a first starting physical resource block (PRB) and a second starting PRB of physical uplink control channel (PUCCH) resources from the gNB; Encoding PUCCH transmission by simultaneous transmission via multiple panels (STxMP) to simultaneously transmit transmission from a first panel using the first starting PRB and a PUCCH from a second panel using the second starting PRB. further configured as follows:

3. The device according to claim 1 or 2.

16. The processing circuitry more than one transmission occasion or frequency resource from the first panel and the second panel within the PUCCH resource; or a first starting PRB index of the first and second hops in a PUCCH resource information element (IE) for the STxMP PUCCH transmission from the first panel and a second starting PRB index of the first and second hops for the STxMP PUCCH transmission from the second panel; further configured to use at least one of 16. The apparatus of claim 15.

17. An apparatus for a fifth generation NodeB (gNB), encoding at least one downlink control information (DCI) for scheduling uplink (UL) transmissions via simultaneous transmission over multiple panels (STxMP) for transmission to a user equipment (UE), the at least one DCI configured to indicate whether time domain (TD) repetition should be applied to the STxMP UL transmissions; a processing circuit configured to decode the STxMP UL transmission from the UE, directed to multiple transmission / reception points (TRPs), based on a determination of whether the TD repetition should be applied; a memory configured to store the DCI; A device having:

18. The processing circuitry encoding a first starting physical resource block (PRB) and a second starting PRB for physical uplink control channel (PUCCH) resources for transmission to the UE; Decode a multi-panel (STxMP) PUCCH transmission from at least one of a first panel of the UE using the first starting PRB simultaneously with a PUCCH from a second panel of the UE using the second starting PRB. further configured as follows:

18. The apparatus of claim 17.

19. instructions for execution by one or more processors of a user equipment (UE), The instructions, when executed by the one or more processors, cause the UE to: Decoding at least one downlink control information (DCI) for scheduling uplink (UL) transmissions via simultaneous transmission over multiple panels (STxMP) from a fifth generation NodeB (gNB); determining, from the at least one DCI, whether time domain (TD) repetition should be applied to the STxMP UL transmission; encoding the STxMP UL transmission for transmission to multiple transmission / reception points (TRPs) based on the determination of whether TD repetition should be applied; program.

20. The instructions, when executed by the one or more processors, further cause the UE to: The STxMP UL transmission uses multi-panel transmission; The STxMP UL transmission uses the same frequency resource for spatial domain multiplexing (SDM) and different frequency resource for frequency domain multiplexing (FDM); 20. The program of claim 19.

21. A non-transitory computer-readable storage medium storing the program according to claim 19 or 20.

Images