PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63/390,526, filed July 19, 2022, Provisional Patent Application Serial No. 63/396,362, filed August 9, 2022, and Provisional Patent Application Serial No. 63/410,111, filed September 26, 2022, each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to communications in 3 GPP networks. In particular, some embodiments relate to simultaneous multi-panel and transmitreceive point (TRP) transmissions and configurations thereof in fifth generation (5G) and later networks.

BACKGROUND

[0003] The use and complexity of wireless systems has increased due to both an increase in the types of electronic devices using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on the electronic devices. As expected, a number of issues abound with the advent of any new technology, including complexities related to the use of multiple TRPs and multiple panels.

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. 1 A illustrates an architecture of a network, in accordance with some aspects. [0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates simultaneous multi-TRP multi-panel transmission in accordance with some embodiments.

[0010] FIGS. 4A and 4B illustrate simultaneous transmission with multipanel (STxMP) with time domain (TD) repetition respectively without and with panel switching in accordance with some embodiments.

[0011] FIGS. 5 A and 5B respectively illustrate consecutive and interleaved resource allocation for a Physical Uplink Shared Channel (PUSCH) in panel 1 and 2 in accordance with some embodiments.

[0012] FIG. 6A illustrates single downlink control information (DCI) based frequency domain multiplexing (FDM) STxMP with TD repetition with frequency/panel switching in accordance with some embodiments.

[0013] FIG. 6B illustrates single DCI based FDM STxMP with TD repetition without frequency/panel switching in accordance with some embodiments.

[0014] FIGS. 7A and 7B respectively illustrate multi-DCI based FDM STxMP with TD repetition with and without frequency/panel switching in accordance with some embodiments.

[0015] FIGS. 8A and 8B respectively illustrate multi-DCI based FDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments.

[0016] FIGS. 9A and 9B respectively illustrate single-DCI based SDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments.

[0017] FIGS. 10A and 10B respectively illustrate multi-DCI based SDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments. [0018] FIGS. 11 A and 1 IB respectively illustrate multi-DCI based SDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments.

[0019] FIGS. 12A and 12B respectively illustrate an aperiodic-channel state information (A-CSI) or semi-persistent CSI (SP-CSI) multiplexing on a STxMP PUSCH transmission or STxMP PUSCH repetitions in accordance with some embodiments.

[0020] FIGS. 13A and 13B respectively illustrate an A-CSI or SP-CSI multiplexing on a first TD repetition or on first and second repetitions of a STxMP PUSCH transmission in accordance with some embodiments.

[0021] FIG. 14 illustrates physical resource block (PRB) distance for a Physical Uplink Control Channel (PUCCH) transmission from a first and second panel transmission in accordance with some embodiments.

[0022] FIG. 15 illustrates a panel ID in accordance with some embodiments.

[0023] FIG. 16 illustrates another panel ID in accordance with some embodiments.

[0024] FIG. 17 illustrates another panel ID in accordance with some embodiments.

[0025] FIG. 18 illustrates a frequency resource for PUCCH for a first and second panel for STxMP operation in accordance with some embodiments.

[0026] FIG. 19 illustrates separate discrete Fourier transform (DFT) operations for modulated symbols for a STxMP PUCCH FDM-A scheme in accordance with some embodiments.

[0027] FIG. 20 illustrates a single DFT operation for modulated symbols for a STxMP PUCCH FDM-A scheme in accordance with some embodiments.

[0028] FIG. 21 illustrates a flowchart of codebook (CB) and noncodebook (nCB) based multi-TRP transmissions in accordance with some embodiments.

[0029] FIG. 22 illustrates a flowchart of PUCCH transmission in accordance with some embodiments.

[0030] FIG. 23 illustrates another flowchart of PUCCH transmission in accordance with some embodiments. [0031] FIG. 24 illustrates a flowchart of PUSCH transmission in accordance with some embodiments.

DETAILED DESCRIPTION

[0032] The following description and the drawings sufficiently illustrate 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, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0033] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140 A includes 3 GPP LTE/4G and NG network functions that may be extended to 6G and later generation functions.

Accordingly, although 5G is referred to herein, it is to be understood that this is to extend as able to 6G (and later) structures, systems, and functions. A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0034] The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0035] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 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 3 GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0036] In some aspects, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0037] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with 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 contain 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 6 ^th generation NodeBs - and thus may be alternately referred to as next generation NodeB (xNB). [0038] Each of the gNBs may implement protocol entities in the 3GPP protocol stack, in which the layers are considered to be ordered, from lowest to highest, in the order 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 in each gNB may be distributed in different units - a Central Unit (CU), at least one Distributed Unit (DU), and a Remote Radio Head (RRH). The CU may provide functionalities such as the control the transfer of user data, and effect mobility control, radio access network sharing, positioning, and session management, except those functions allocated exclusively to the DU.

[0039] The higher 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 higher PHY layer also implemented in the DU, while the lower PHY layer is implemented in the RRH. The CU, DU and RRH may be implemented by different manufacturers, but may nevertheless be connected by the appropriate interfaces therebetween. The CU may be connected with multiple DUs.

[0040] The interfaces within the gNB include the El and front-haul (F) Fl interface. The El interface may be between a 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 El AP service. The El interface may separate Radio Network Layer and Transport Network Layer and enable exchange of UE associated information and non-UE associated information. The El AP services may be non UE- associated services that are related to the entire El interface instance between the gNB-CU-CP and gNB-CU-UP using a non UE-associated signaling connection and UE-associated services that are related to a single UE and are associated with a UE-associated signaling connection that is maintained for the UE.

[0041] The Fl interface may be disposed between the CU and the DU. The CU may control the operation of the DU over the Fl interface. As the signaling in the gNB is split into control plane and user plane signaling, the Fl interface may be split into the Fl-C interface for control plane signaling between the gNB-DU and the gNB-CU-CP, and the Fl -U interface for user plane signaling between the gNB-DU and the gNB-CU-UP, which support control plane and user plane separation. The Fl interface may separate the Radio Network and Transport Network Layers and enable exchange of UE associated information and non-UE associated information. In addition, an F2 interface may be between the lower and upper parts of the NR PHY layer. The F2 interface may also be separated into F2-C and F2-U interfaces based on control plane and user plane functionalities.

[0042] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0043] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising 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).

[0044] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0045] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 can be transmission-reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0046] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can 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 an example, any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.

[0047] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121. [0048] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0049] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0050] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120. [0051] The P-GW 123 may further be a node for policy enforcement and charging data collection. 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 a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0052] In some aspects, the communication network 140 A can be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[0053] An NG system architecture (or 6G system architecture) can include the RAN 110 and a core network (CN) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network (5GC)) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces. [0054] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

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

[0056] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0057] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to 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).

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

[0059] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170B, e.g. an IMS operated by a different network operator.

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

[0061] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates 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), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (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 case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

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

[0063] In some aspects, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following servicebased interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a servicebased interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used. [0064] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size.

Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0065] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, 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 any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1 A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0066] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0067] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0068] The communication 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., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., 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, compass, accelerometer, or other sensor. 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 or control one or more peripheral devices (e.g., a printer, card reader, etc.).

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

[0070] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, 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; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.

[0071] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5 ^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.

[0072] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0073] The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out 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, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

[0074] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example 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 (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3 G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (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), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP 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 (such as 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 (Third generation) (CDMA2000 (3 G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication SystemZExtended Total Access Communication System (TACSZETACS), 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, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. Had, IEEE 802. Hay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 Ip or IEEE 802.1 Ibd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to- Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802.1 Ip based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc. [0075] Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3 -2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 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: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 - 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi-Gigabit Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0076] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.

[0077] Aspects described herein can 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 3 GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0078] As above, Rel-17 NR supports multi-TRP physical uplink shared channel (PUSCH) repetitions and physical uplink control channel (PUCCH) repetitions. 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 sub-slots. However, in each time slot or sub-slot, only one UL transmission occasion occurs towards a certain TRP. To utilize the multiple TRPs more efficiently, it is desirable for the Rel-18 5GNR system to support simultaneous multi-TRP multi-panel transmission schemes in UL, where the UE is equipped with multiple antenna panels. FIG. 3 illustrates simultaneous multi- TRP multi-panel transmission in accordance with some embodiments. In particular, to increase the overall capacity and to increase robustness of the transmission to potential blockage of the channel, the UE may transmit data and control information targeting two or more TRPs simultaneously as shown in FIG. 3. In FIG. 3, the transmit beam from panel 1 is targets TRP1, and the transmit beam from panel 2 targets TRP 2.

[0079] To support simultaneous multi-TRP (mTRP) multi-panel transmission operations in UL, different transmission schemes can be considered. For example, the mTRP transmissions 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 transmissions by a single DCI that is either transmitted through one TRP or multiple TRPs. A multi-DCI-based scheme schedules the PUSCH transmissions by multiple DCIs through multiple TRPs.

[0080] In Rel-17, multi-TRP based repetition schemes were supported, where the same transport block (TB) and uplink control information (UCI) may be transmitted with different PUSCH/PUCCH repetitions to different TRPs in a time domain multiplexing (TDM) manner to increase the reliability of the communication. In Rel-18, simultaneous transmission with multi-panel (STxMP) is supported, where two PUSCH/PUCCH transmission occasions may be transmitted from two different UE panels to two different TRPs simultaneously.

[0081] Different multiplexing types in STxMP schemes may be used, such as spatial domain multiplexing (SDM), frequency domain multiplexing (FDM), 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 TB) may be simultaneously transmitted separately from different UE panels. In FDM-A STxMP, different parts of the frequency domain resource 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 (RV) of the same TB may be transmitted from different UE panels on non-overlapped frequency domain resources and the same time domain resources. To enhance the reliability and coverage of the UL transmission, STxMP with repetitions may be allowed in the time domain.

[0082] Note that channel state information (CSI) may include a Channel Quality Indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a synchronization signal/Physical Broadcast Channel (SS/PBCH) Block Resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), layer 1 Reference Signal Received Power (Ll-RSRP) or layer 1 Signal to Interference and Noise Ratio (Ll-SINR), which are reported from the UE to the base station. Aperiodic CSI (A-CSI) reporting and semi-persistent CSI (SP-CSI) reporting may be triggered by the CSI request field in the DCI . In this case, the A/SP-CSI reporting and UL transmission may be scheduled by one or more DCIs at the same time. However, how to handle the A/SP-CSI multiplexing on a STxMP transmission is not yet specified.

[0083] As mentioned above, multi-TRP time domain (TD) repetition may be also supported in STxMP transmission with and without panel switching to enhance the coverage and reliability. FIGS. 4A and 4B illustrate simultaneous transmission with multi-panel (STxMP) with time domain (TD) repetition respectively without and with panel switching in accordance with some embodiments. Note that the TD repetition can be either repetition type- A, which is slot-based, or repetition type-B, which is based on back-to-back repetition.

For UL transmissions from UE panel 1 and panel 2, the same frequency resource or a different frequency resource may be used, which corresponds to SDM or FDM-based STxMP schemes, respectively.

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

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

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

[0087] Moreover, the redundancy version for repetitions may be specified for a PUSCH STxMP with and without TD repetition. In one embodiment, for a single-DCI-based PUSCH STxMP without TD repetition, if the two panels are transmitting two repetitions of the same TB, the DCI may indicate the first RV for the first repetition 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 transmitted through the second panel uses RV2/RV3/RV1/RV0, respectively. [0088] In another embodiment, for a single-DCI based PUSCH STxMP with TD repetition, if the two panels are transmitting the repetitions of two different TBs, i.e., panel-1 transmits the repetitions of TB1 in different time domain resources and panel-2 transmits the repetitions of TB2 in different time domain resources, the DCI may indicate the first RV for the first repetition transmitted through panel-1, and the RV pattern (0 2 3 1) is applied separately to the PUSCH through the two panels with a possibility of configuring RV offset for 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 RV offset 1, the first repetition through the second panel uses RV2/RV3/RV1/RV0, respectively. And the following repetitions through the panel use the following RV in RV pattern (0 2 3 1) sequentially.

[0089] In another embodiment, for a single-DCI based PUSCH STxMP with TD repetition, if the two panels are transmitting the repetitions of the same TBs, i.e., panel-1 and panel-2 transmit the information of the TB, the DCI may indicate the first RV for the first repetition transmitted through panel- 1, and the RV pattern (0 2 3 1) is applied separately to the PUSCH through the two panels with a possibility of configuring RV offset for 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 RV offset 1, the first repetition through the second panel uses RV2/RV3/RV1/RV0, respectively. And the following repetitions through the panel use the following RV in RV pattern (0 2 3 1) sequentially.

[0090] In another option of the last two embodiments, the RV offset indication may be absent in the DCI, and the RV offset is 1 by default. Note that the repetition mentioned above for RV mapping is the actual repetition for repetition Type B.

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

[0092] FPM STxMP Transmission with TD repetition

[0093] In FDM STxMP transmission, two orthogonal frequency resources in an uplink BWP, are allocated for the UL transmission through panel 1 and panel 2, respectively.

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

[0095] In another option, the frequency offset between the starting PRB of the PUSCH transmission in the first and second panel may be determined in accordance with the frequency offset that is configured for intra-slot, interrepetition or inter-slot frequency hopping of the PUSCH transmission.

[0096] As a further extension, the frequency offset between the starting PRB of the PUSCH transmission in the first and second panel may be determined in accordance with the bandwidth of the UL bandwidth part (BWP). For instance, the frequency offset may be equal to Ag _X y _P /2] , ^ B T/4], or -[^BW/4]- Note that this embodiment may be applicable for uplink resource allocation type 0 and 1.

[0097] FIG. 5A and 5B illustrates consecutive resource allocation for a PUSCH in panel 1 and 2 in accordance with some embodiments. In the example shown in FIG. 5 A, the frequency offset between the starting PRB for the PUSCH in the panel 1 and 2 may be configured by higher layers.

[0098] In another embodiment, the two disjoint frequency resources for the PUSCH transmission for the first and second panel may be interleaved in the frequency domain. In one option, the frequency resource for the PUSCH transmission for the first panel may be allocated with every even N PRBs, while the frequency resource for the PUSCH transmission for the second panel may be allocated with every odd N PRBs, or vice versa. Note that N may be pre-defined in the specification or configured by higher layers via RMSI, OSI, or RRC signaling or dynamically indicated in the DCI or a combination thereof. In another option, N may be determined in accordance with Resource Block Group (RBG) size when uplink resource allocation type 0 is used for frequency resource allocation.

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

[00100] In another option, when uplink resource allocation type 0 or type 1 is used for frequency resource allocation for the STxMP, the FDRA field in the DCI for scheduling the PUSCH may be used to indicate the frequency resource of the PUSCH transmission for the first and second panel jointly. Further, the frequency resource of the PUSCH transmission in the first panel may be determined accordingly based on the rule as mentioned above. This may also apply for the determination of frequency resource for the PUSCH transmission in the second panel.

[00101] FIG. 5B illustrates interleaved resource allocation for a PUSCH in panel 1 and 2 in accordance with some embodiments. In the example, the PUSCH for panel 1 is transmitted in every even N PRBs, while the PUSCH for panel 2 is transmitted in every odd N PRBs. Note that N may be configured by higher layers as mentioned above.

[00102] In FDM STxMP TD repetitions, the association of the two frequency resources with the panels may be switched or not switched in each next STxMP transmission occasion, and the scheduling may be single-DCI or multi-DCI, which are illustrated by the following embodiments.

[00103] FIGS. 6A and 6B respectively illustrate single DCI based FDM STxMP with TD repetition with and without frequency/panel switching in accordance with some embodiments. The single DCI at least indicates the number of TD repetitions. In particular, a time domain resource allocation field may be used to indicate the one row from a table for the time domain resource allocation of the PUSCH transmission, which includes number of repetitions, mapping type and starting and length indicator value (SLIV). In these and later figures the solid arrows indicate the mTRP repetition process, the dotted arrows indicate the sTRP repetition process, and the box around the PUSCHs indicates one STxMP PUSCH transmission or TD repetition.

[00104] In other embodiments, multiple DCIs may be used to schedule the FDM STxMP with TD repetition. FIGS. 7 A and 7B respectively illustrate multi- DCI based FDM STxMP with TD repetition with and without frequency/panel switching in accordance with some embodiments.

[00105] In another embodiment, multi-DCI based FDM STxMP with TD repetition with or without frequency/panel switching may be achieved by other methods. FIGS. 8 A and 8B respectively illustrate multi-DCI based FDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments.

[00106] In particular, repetition with frequency/panel switching may also be achieved by two simultaneous single-TRP repetition processes with frequency hopping guided by dashed arrows as shown in FIG. 8A. In this case, two simultaneous single-DCI based multi-TRP repetition processes without frequency hopping are shown in FIG. 8A guided by solid arrows.

[00107] Similarly, repetition without frequency/panel switching may also be achieved by two simultaneous single-TRP repetition processes without frequency hopping as shown in FIG. 8B guided by dashed arrows. In addition, two simultaneous single-DCI based multi-TRP repetition processes with frequency hopping are shown in FIG. 8B guided by solid arrows.

[00108] SDM STxMP Transmission with TD repetition

[00109] In SDM STxMP transmission, the same frequency resources may be allocated for the UL transmission through panel 1 and panel 2. In SDM STxMP TD repetitions, the association of the two panels with the PUSCH may be switched or may not be switched in each next STxMP transmission occasion, and the scheduling may be single-DCI or multi-DCI, as illustrated by the following embodiments.

[00110] FIGS. 9A and 9B respectively illustrate single-DCI based SDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments. That is, the SDM STxMP with TD repetition may be scheduled by a single DCI with or without frequency/panel switching. The single DCI at least indicates the number of TD repetitions. In particular, time domain resource allocation field may be used to indicate the one row from a table for the time domain resource allocation of the PUSCH transmission, which includes number of repetitions, mapping type, and SLIV.

[00111] FIGS. 10A and 10B respectively illustrate multi-DCI based SDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments. That is, multiple DCIs are used in FIGS. 10A and 10B, rather than the single DCI shown in FIGS. 9 A and 9B. [00112] In another embodiment, multi -DCI based SDM STxMP with TD repetition with or without frequency/panel switching may be achieved by other methods. FIGS. 11 A and 1 IB respectively illustrate multi-DCI based SDM STxMP with TD repetition with or without frequency/panel switching in accordance with some embodiments.

[00113] In particular, repetition with frequency/panel switching may also be achieved by two simultaneous single-TRP repetition processes with panel switching guided by dashed arrows as shown in FIG. 11 A. In this case, two simultaneous single-DCI based multi-TRP repetition processes without panel switching are shown in FIG. 11 A guided by solid arrows.

[00114] Similarly, repetition without panel switching may also be achieved by two simultaneous single-TRP repetition processes without panel switching as shown in FIG. 1 IB guided by dashed arrows. In addition, two simultaneous single-DCI based multi-TRP repetition processes with panel switching are shown in FIG. 1 IB guided by solid arrows.

[00115] In another embodiment, when time domain repetition is applied for the STxMP transmission, beam cycling may be applied for the PUSCH from different panels. The existing beam cycling pattern with cyclic and sequential beam mapping may be used for the PUSCH transmission in each panel, which may further improve the reliability.

[00116] 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 the PUSCH transmission for a first panel and the second two SRS resource sets may be associated with the PUSCH transmission for a second panel. Further, the SRS resource set indication may be extended to indicate whether beam cycling is enabled or disabled for STxMP transmission.

[00117] In another option, two SRS resource sets may be configured for the STxMP PUSCH transmission with beam cycling, where each panel is associated with both SRS resource sets. In this case, panel 1 and panel 2 may be associated with different SRS resource sets for each STxMP transmission.

[00118] A/SP-CSI Multiplexing on STxMP [00119] When aperiodic-CSI (A-CSI) or semi-persistent CSI (SP-CSI) is scheduled together with STxMP PUSCH transmission, the A/SP-CSI may be multiplexed on the STxMP PUSCH transmission. FIGS. 12A and 12B respectively illustrate an aperiodic-channel state information (A-CSI) or semi- persistent CSI (SP-CSI) multiplexing on a STxMP PUSCH transmission or STxMP PUSCH repetitions in accordance with some embodiments. As shown in FIG. 12A, the A/SP-CSI may be multiplexed on the STxMP PUSCH transmission through both panels.

[00120] Note that when other uplink control information (UCI) types including Hybrid Automatic Repeat Request acknowledgement (HARQ-ACK) feedback is multiplexed with the A/SP-CSI on the PUSCH only for one of the panels, an A/SP-CSI report is only multiplexed on the PUSCH for one of the panels. For instance, if HARQ-ACK feedback is multiplexed with the A/SP-CSI on the PUSCH for panel 1, the A/SP-CSI report is only multiplexed on the PUSCH for panel 1.

[00121] Further, for a SDM scheme, a FDM scheme A, an SFN-based transmission scheme, when the A/SP-CSI is multiplexed on the STxMP PUSCH transmission for both panels, the number of resources allocated for the A/SP-CSI transmission is determined in accordance with the total resource allocated for PUSCH transmission for both panels.

[00122] For an FDM scheme B and a SDM repetition scheme, when the A/SP-CSI is multiplexed on the STxMP PUSCH transmission for both panels, the number of resources allocated for the A/SP-CSI transmission is determined in accordance with the resource allocated for the PUSCH transmission for each panel, respectively.

[00123] Note that the above embodiments may also apply when time domain repetition is applied for the STxMP PUSCH.

[00124] In another embodiment, the A/SP-CSI may be multiplexed on the STxMP PUSCH transmission through both panels if the PUSCH transmission from both panels are repetitions, which may have the same RV or different RVs, of the same TB, as shown in FIG. 12B.

[00125] A/SP-CSI Multiplexing on STxMP with TD Repetition [00126] FIGS. 13A and 13B respectively illustrate an A-CSI or SP-CSI multiplexing on a first TD repetition or on first and second repetitions of a STxMP PUSCH transmission in accordance with some embodiments. Thus, as shown in FIG. 13 A, the A/SP-CSI is only multiplexed on the first TD repetition of the STxMP PUSCH transmission. Similarly, the A/SP-CSI may be multiplexed on the first TD repetition and the second TD repetition of the STxMP PUSCH transmission as shown in FIG. 13B.

[00127] Note that when the A/SP-CSI on the STxMP PUSCH transmission with TD repetition without a transport block, the number of repetitions for the A/SP-CSI is only 1 for the PUSCH transmission in each panel. This may apply for the case for the activation of the SP-CSI transmission on the PUSCH or the SP-CSI on the PUSCH without a corresponding PDCCH.

[00128] Further, for PUSCH repetition type B, the UE may expect the same number of symbols for nominal and actual repetition. If the number of symbols for nominal and actual repetitions for each panel is different, the UE may drop the A-CSI and/or SP-CSI report.

[00129] Mechanisms on PUCCH resource configuration for STxMP operation

[00130] Multiple STxMP transmission schemes may be considered for PUCCH transmission, i.e., FDM, single frequency network (SFN). For instance, as above the following schemes may be used: FDM-A scheme: different frequency domain parts of one PUCCH resource are transmitted by two different UE panels. FDM-B scheme: two FDMed PUCCH transmission occasions of the same UCI with the same PUCCH format are transmitted from two different UE panels SFN scheme: the same PUCCH/PUCCH-DMRS is transmitted from two different UE panels simultaneously.

[00131] Further, STxMP PUCCH transmission may be scheduled by either a single DCI (sDCI) or multiple DCIs (mDCI). When the STxMP PUCCH transmission is scheduled by a sDCI, PUCCH resources on more than one panel are determined. Further, for an FDM-A scheme, when PUCCH format 3 is used for carrying the UCI payload, certain mechanisms may be defined on the transmission scheme so as to reduce the Peak-to-Average Power Ratio (PAPR).

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

[00133] PUCCH resource configuration for STxMP operation

[00134] As above, multiple STxMP transmission schemes may be considered for PUCCH transmission, i.e., FDM, SFN. STxMP PUCCH transmission may be scheduled by either a sDCI or multiple DCIs. When the STxMP PUCCH transmission is scheduled by sDCI, PUCCH resources on more than one panel are determined.

[00135] Embodiments of PUCCH resource configuration for STxMP operation are provided as follows:

[00136] In some aspects, the following embodiments may apply for all PUCCH formats including PUCCH format 0, 1, 2, 3 and 4.

[00137] In one embodiment, for a sDCI STxMP PUCCH transmission scheme, a PUCCH resource indicator (PRI) may be included in the DCI format 1 1 and/or 1 2 for scheduling a PDSCH, where the PRI and/or starting positioning of a control channel element (CCE) for the corresponding physical downlink control channel (PDCCH) transmission may be used to determine a PUCCH resource. Further, more than one transmission occasion or frequency resources from a first and second panel may be included in the PUCCH resource. [00138] In one option, the following PUCCH-Resource information element (IE) may be updated to include a second starting PRB index in the first and second hop as indicated below. In some aspects, the starting PRB index in the first and second hop in the existing PUCCH resource IE may be used for the STxMP PUCCH transmission from the first panel; where the second starting PRB index in the first and second hop may be used for the STxMP PUCCH transmission from the second panel. In some aspects, when frequency hopping is disabled, the second starting PRB index for the second hop is not applicable.

PUCCH-Resource ::= SEQUENCE { pucch-Resourceld PUCCH-Resourceld. startingPRB PRB-Id, startingPRB2 PRB-Id, intraSlotFrequencyHopping ENUMERATED { enabled }

OPTIONAL, - Need R secondHopPRB PRB-Id

OPTIONAL, - Need R secondHopPRB2 PRB-Id

OPTIONAL, - Need R format CHOICE { formatO PUCCH-formatO format 1 PUCCH-formatl. format2 PUCCH-format2 formats PUCCH-format3 format4 PUCCH-format4

[00139] In some aspects, a second starting PRB index in the first and second hop may not be present in the PUCCH resource IE. This may indicate the SFN operation for a STxMP PUCCH transmission. Alternatively, a 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 resource IE. This may also indicate the SFN operation for a STxMP PUCCH transmission.

[00140] In another option, the following PUCCH-Resource IE may be updated to include a PRB distance between the PUCCH transmission from a first and second panel as indicated below. In some aspects, when frequency hopping is enabled for a PUCCH transmission, the same PRB distance is applied for the PUCCH transmission for the second hop between the PUCCH transmission from a first and second panel.

PUCCH-Resource ::= SEQUENCE { pucch-Resourceld PUCCH-Resourceld, startingPRB PRB-Id, distancePRB PRB-Id, intraSlotFrequencyHopping ENUMERATED { enabled } OPTIONAL, - Need R secondHopPRB PRB-Id

OPTIONAL, - Need R format CHOICE { formatO PUCCH-formatO, formatl PUCCH-formatl, format2 PUCCH-format2, formats PUCCH-format3, format4 PUCCH-format4

} }

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

[00142] FIG. 14 illustrates PRB distance for a PUCCH transmission from a first and second panel transmission in accordance with some embodiments. In the example shown in FIG. 14, a PRB distance is configured between the PUCCH transmission from a first and second panel.

[00143] In another embodiment, a Medium Access Control - Control Element (MAC-CE) for PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition may be extended to support STxMP PUCCH transmission. In particular, a panel ID may be included in a PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE. In some aspects, bit “0” may indicate a first panel while bit “1” may indicate a second panel.

[00144] FIG. 15 illustrates a panel ID in accordance with some embodiments. The Panel ID of FIG. 15 is in a PUCCH spatial relation Activation/Deactivation MAC-CE. In FIG. 15, the first reserved bit in the Oct for each spatial relation info ID is updated for panel ID. In some aspects, bit “0” may indicate a first panel while bit “1” may indicate a second panel.

[00145] FIG. 16 illustrates another panel ID in accordance with some embodiments. Like FIG. 15, the Panel ID of FIG. 16 is in a PUCCH spatial relation Activation/Deactivation MAC-CE. In the FIG. 16, the second reserved bit in the Oct for each spatial relation info ID is updated for panel ID. In some aspects, bit “0” may indicate a first panel while bit “1” may indicate a second panel. [00146] In another option, a new MAC-CE may be defined to the PUCCH spatial relation Activation and Deactivation for STxMP PUCCH transmission.

In the MAC CE, one or more following parameters may be included: serving cell ID, BWP ID, panel ID, PUCCH resource ID, a first associated spatial relation info ID for a first panel and a second associated spatial relation info ID for a second panel.

[00147] In another embodiment, a PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC-CE may be extend to support STxMP PUCCH transmission. In particular, the panel ID may be included in the PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC- CE. In some aspects, bit “0” may indicate a first panel while bit “1” may indicate a second panel.

[00148] FIG. 17 illustrates another panel ID in accordance with some embodiments. The Panel ID of FIG. 17 is in a PUCCH Power Control Set Update MAC-CE for STxMP PUCCH operation. In FIG. 17, the first and second reserved bits in the Oct for PUCCH power control set IDs are updated for panel ID. In some aspects, bit “0” may indicate a first panel while bit “1” may indicate a second panel.

[00149] In another option, a new MAC-CE may be defined to a PUCCH Power Control Set Update for STxMP PUCCH transmission. In the MAC CE, one or more following parameters may be included: serving cell ID, BWP ID, panel ID, PUCCH resource ID, a first associated PUCCH power control set ID for a first panel and a second associated PUCCH power control set ID for a second panel.

[00150] In another embodiment, for a sDCI STxMP PUCCH transmission scheme, a first and second PRI may be included in the DCI format 1 1 and/or 1 2 for scheduling a PDSCH, where the first and second PRI and/or starting positioning of a CCE for the corresponding PDCCH transmission may be used to determine a first and second PUCCH resource from a first and second panel, respectively.

[00151] In another option, a first PRI is included in the DCI format 1 1 and/or 1 2 for scheduling a PDSCH. Further, a differentiated PRI may be also included in the same DCI, where the second PRI may be determined based the first PRI and the differentiated PRI.

[00152] In some aspects, panel information including panel identity be configured as part of PUCCH resource configuration. In one example, tl following PUCCH-Resource IE may be updated to include the panel ID as indicated.

PUCCH-Resource : := SEQUENCE { pucch-Resourceld PUCCH-Resourceld, pucch-PanellD pucch-PanellD startingPRB PRB-Id, intraSlotFrequencyHopping ENUMERATED { enabled } OPTIONAL, - Need R secondHopPRB PRB-Id OPTIONAL, - Need R format CHOICE { formatO PUCCH-formatO, format 1 PUCCH-formatl, format2 PUCCH-format2, formats PUCCH-format3, format4 PUCCH-format4

}

}

[00153] In another example, the following PUCCH-SpatialRelationlnfo IE may be updated to include the panel ID as indicated.

PUCCH-SpatialRelationlnfo : := SEQUENCE { pucch- Spati alRel ati onlnfold PUCCH-SpatialRelationlnfoId, servingCellld ServCelllndex

OPTIONAL, - Need S pucch-PanellD pucch-PanellD referencesignal CHOICE { ssb-Index S SB -Index, csi-RS-Index NZP-CSI-RS-Resourceld, srs PUCCH-SRS

}, pucch-PathlossReferenceRS-Id PU C CH-Pathl os sReferenceRS -Id. pO-PUCCH-Id PO-PUCCH-Id, closedLoopIndex ENUMERATED { iO, il }

} [00154] For this option, the UE may expect that same PUCCH format, starting symbols and number of symbols, and number of PRB are used for STxMP PUCCH transmissions.

[00155] In another embodiment, for a sDCI STxMP PUCCH transmission scheme, a PRI may be included in the DCI format 1 1 and/or 1 2 for scheduling PDSCH, where a PRI and/or starting positioning of CCE for the corresponding PDCCH transmission may be used to determine a set of PUCCH resources. In particular, the group of PUCCH resources include a first and second PUCCH resource from a first and second panel, respectively.

[00156] For this option, a panel ID may be included as part of PUCCH resource configuration or PUCCH spatial relation info configuration.

[00157] Frequency resource partitioning for STxMP FDM-A scheme

[00158] Embodiments of frequency resource partitioning for STxMP

FDM-A scheme are provided as follows:

[00159] In some aspects, a STxMP FDM-A PUCCH transmission scheme may apply for PUCCH format 2 and/or 3.

[00160] In one embodiment, for an FDM-A STxMP PUCCH scheme, a frequency resource for the PUCCH transmission for a first and second panel may be contiguous. Further, assuming the number of PRBs configured for a PUCCH format 2 is N _PRB , the PUCCH transmission for the first panel and second panel occupies [/V _RRB /2] and pV _RRB /2], respectively.

[00161] In some aspects, when frequency hopping is enabled, this may also apply for the frequency resource in the second hop for the PUCCH transmission for the first and second panel.

[00162] FIG. 18 illustrates a frequency resource for PUCCH for a first and second panel for STxMP operation in accordance with some embodiments. In FIG. 18, it is assumed 10 PRBs are allocated for the PUCCH format 2. In this case, the first 5 PRBs are allocated for PUCCH transmission for the first panel, while the second 5 PRBs are allocated for PUCCH transmission for the second panel.

[00163] In another embodiment, for an FDM-A STxMP PUCCH scheme, a frequency resource for the PUCCH transmission for a first and second panel may be interleaved. In particular, the frequency resource for the PUCCH transmission for the first panel may be allocated with every even K PRBs, while the frequency resource for the PUCCH transmission for the second panel may be allocated with every odd K PRBs, or vice versa.

[00164] In some aspects, K may be pre-defined in the specification or configured by higher layers (higher layer signaling) via NR RMSI, NR OSI or dedicated RRC signaling, dynamically indicated in the DCI, or a combination thereof. In another option, K may be determined in accordance with the number of PRBs configured for a PUCCH resource. In one example, K = 1 or 2.

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

[00166] Embodiments of a STxMP FDM-A scheme for PUCCH format 3 and a PUSCH with DFT-s-OFDM waveform are provided as follows:

[00167] In one embodiment, for a STxMP FDM-A scheme for PUCCH format 3 and a PUSCH with DFT-s-OFDM waveform, modulated symbols for the PUCCH and PUSCH transmission with a DFT-s-OFDM waveform may be equally split into two parts, where the first and second part are input to a first and second DFT, respectively. Further, the modulated symbols after the DFT operation are mapped to the allocated resources for the PUCCH and PUSCH transmission for the first and second panel, respectively.

[00168] FIG. 19 illustrates separate DFT operations for modulated symbols for a STxMP PUCCH FDM-A scheme in accordance with some embodiments. In FIG. 19, a first and second DFT is applied for the split modulated symbols for the PUCCH transmission for a first and second panel, respectively.

[00169] In another embodiment, for a STxMP FDM-A scheme for PUCCH format 3 and a PUSCH with DFT-s-OFDM waveform, a single DFT is applied for the modulated symbol for PUCCH and PUSCH transmission.

Further, the modulated symbols after DFT operation are equally split into two parts, where the first and second part are mapped to the allocated resources for the PUCCH and PUSCH transmission for the first and second panel, respectively. [00170] FIG. 20 illustrates a single DFT operation for modulated symbols for a STxMP PUCCH FDM-A scheme in accordance with some embodiments. In FIG. 20, a single DFT is applied for the modulated symbol for PUCCH and PUSCH transmission.

[00171] STxMP CDM scheme for PUCCH format 0/1/4

[00172] Embodiments of STxMP CDM scheme for PUCCH format 0/1/4 are provided as follows:

[00173] In one embodiment, for PUCCH format 0 and 1, different cyclic shifts may be configured for the STxMP PUCCH transmission from a first and second panel, respectively. In some aspects, the initial cyclic shift in the existing PUCCH format 0 and format 1 IE may be used for the STxMP PUCCH transmission from the first panel; where the second initial cyclic shift may be used for the STxMP PUCCH transmission from the second panel.

[00174] In one option, the following PUCCH-formatO and PUCCH- formatl IE may be updated to include a second initial cyclic shift as indicated below, respectively.

PUCCH-formatO ::= SEQUENCE { initialCyclicShift INTEGER(O. l l), initialCyclicShift2 INTEGER(O. l l), nrofSymbols INTEGER (1 .2), startingSymbolIndex INTEGER(0..13)

}

PUCCH-formatl ::= SEQUENCE { initialCyclicShift INTEGER(O. l l), initialCyclicShift2 INTEGER(O. l l), nrofSymbols INTEGER (4 .14), startingSymbolIndex INTEGER(O. IO), timeDomainOCC INTEGER(0..6)

}

[00175] In another embodiment, for PUCCH format 4, a different orthogonal cover code (OCC) index may be configured for the STxMP PUCCH transmission from a first and second panel, respectively. In some aspects, the OCC index in the existing PUCCH format 4 IE may be used for the STxMP PUCCH transmission from the first panel; where the second OCC index may be used for the STxMP PUCCH transmission from the second panel. [00176] In one option, the following PUCCH-format4 may be updated to include a second OCC index as indicated below.

PUCCH-format4 ::= SEQUENCE { nrofSymbols INTEGER (4 .14), occ-Length ENUMERATED {n2,n4}, occ-Index ENUMERATED {n0,nl,n2,n3}, occ-Index2 ENUMERATED {n0,nl,n2,n3}, startingSymbolIndex INTEGER(O. IO) }

[00177] Precoding Indication and maximum rank configuration for

STxMP

[00178] As above, multiple antennas may be equipped in each panel of the UE and TRP. Therefore, the UE may perform precoding of the data and control information to be transmitted to achieve higher data rate and reliability. The precoding matrix for UL transmission may either be pre-defined as a codebook or computed by the UE. In other words, two transmission modes, namely, codebook (CB) based transmission and non-codebook (nCB) based transmission are supported. For CB based transmission, the gNB provides the UE with a transmit precoding matrix indication in the DCI. The UE uses the indicator, which is called transmitted precoding matrix indicator (TPMI), to select the PUSCH transmit precoder from a set of codebooks. For nCB based transmission, the UE determines its PUSCH precoder based on a CSI-RS measurement from the downlink, and determines the number of layers of the transmission based on an SRS resource indication (SRI) field from the DCI. [00179] In summary, for CB based transmission, the UE determines its PUSCH transmission precoder(s) based on based on the SRI(s), TPMI(s), and the transmission rank. For nCB based transmission, the UE may determine its PUSCH precoder(s) and transmission rank based on the SRI(s) when multiple SRS resources are configured. Note that the SRI is a DCI field, and TPMI(s) and the transmission rank are given by DCI fields called Precoding information and number of layers (PINL).

[00180] However, the above precoding indication methodology is applicable to single-TRP based PUSCH transmission and multi-TRP based PUSCH repetition (two PUSCH repetitions are transmitted in different time domain resources). In simultaneous multi-TRP multi-panel PUSCH transmission, there may be more PUSCH transmission schemes and more conditions/constraints under different transmission schemes.

[00181] Furthermore, in Rel-17 multi-TRP PUSCH transmission, the maxRank configured by RRC signaling is applied to both PUSCH repetitions. However, in SDMed STxMP PUSCH transmission, the two PUSCH transmitted from two panels may have different ranks. Thus, how to configure the maximum ranks for the two panels is to be considered.

[00182] Several methods are indicated herein to enhance the precoding indication, i.e., the SRI field and PINL field, for simultaneous multi-TRP multipanel PUSCH (SxPUSCH) transmission, and methods of configuring the maximum ranks. Note that SxPUSCH is the same as STxMP PUSCH.

[00183] Maximum Rank Indication for Single-DCI based STxMP Transmission

[00184] In one embodiment, two maximum ranks, e.g., maxRank and maxRank2, may be configured for panel- 1 and panel-2 respectively.

[00185] In another embodiment, the legacy configuration, e.g., maxRank, may be reused for the total maximum rank across two panels. For example, if maxRank = 3, layer combinations 1+1, 1+2, 2+1 may be transmitted.

[00186] In another embodiment, if two maximum ranks are configured, the maximum ranks may be mapped to different UE capability value sets.

[00187] PCI field(s) determination for single-DCI based STxMP PUSCH

[00188] In one embodiment, for nCB-based STxMP PUSCH transmissions and CB-based STxMP PUSCH transmissions with different numbers of ports in the configured SRS resources, two SRI fields may be used to indicate the two SRS resources from the two SRS resource sets corresponding to the two TRPs separately. But for CB-based STxMP PUSCH transmissions with the same number of ports in the configured SRS resources, only one SRI field may be used in the DCI. [00189] In another embodiment, for nCB-based STxMP PUSCH transmissions and CB-based STxMP PUSCH transmissions with different numbers of ports in the configured SRS resources, two SRI fields may be used to indicate the two SRS resources from the two SRS resource sets corresponding to the two TRPs separately. But for CB-based STxMP PUSCH transmissions with the same number of ports in the configured SRS resources, no SRI field is indicated in the DCI.

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

[00191] In some embodiments, the electronic devices, networks, systems, chips or components, or portions or implementations thereof, of the above figures may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in FIG. 21, which illustrates a flowchart of CB and nCB based multi-TRP transmissions in accordance with some embodiments. Specifically, the process 2100 of FIG. 21 may include or relate to a method to be performed by a UE, one or more elements of a UE, and/or an electronic device that includes or implements a UE. The process 2100 may include identifying, at operation 2102, 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 are to occur; identifying, at operation 2104, whether the first and second transmissions are CB or nCB; and transmitting, at operation 2106, the first and second transmissions based on whether the first and second transmissions are CB or nCB.

[00192] FIG. 22 illustrates a flowchart of PUCCH transmission in accordance with some embodiments. The process 2200 of FIG. 22 may include or relate to a method to be performed by a UE, one or more elements of a UE, and/or one or more electronic devices that include or implement an element of a UE. The process 2200 may include identifying, at operation 2202 in a configuration message received from a base station, a first starting PRB and a second starting PRB; and transmitting, at operation 2204, a first PUCCH based on the first starting PRB from a first panel and a second PUCCH based on the second starting PRB from a second panel. [00193] FIG. 23 illustrates another flowchart of PUCCH transmission in accordance with some embodiments. The process 2300 of FIG. 23 may include or relate to a method to be performed by a base station, one or more elements of a base station, and/or one or more electronic devices that include or implement an element of a base station. The process 2300 of FIG. 23 may include transmitting, at operation 2302 to a UE, a configuration message that includes an indication of a first starting PRB and an indication of a second starting PRB; and identifying, at operation 2304 from the UE, a first PUCCH transmission based on the first starting PRB from a first panel and a second PUCCH transmission based on the second starting PRB from a second panel.

[00194] FIG. 24 illustrates a flowchart of PUSCH transmission in accordance with some embodiments. The process 2400 of FIG. 24 may include or relate to a method to be performed by a base station, one or more elements of a base station, and/or one or more electronic devices that include or implement an element of a base station. The process 2400 of FIG. 24 include, at operation 2402, receiving configuration information for STxMP for a PUSCH transmission. The process further includes, at operation 2404, encoding a PUSCH for STxMP based on the configuration information.

[00195] Examples

[00196] Example 1 is an apparatus for a user equipment (UE), the apparatus comprising: memory; and processing circuitry, to configure the UE to: receive at least one downlink control information (DCI) to schedule simultaneous transmission with multi-panel (STxMP) uplink (UL) transmission; determine, from the at least one DCI, whether time domain (TD) repetition is to be applied to the UL; and transmit the UL transmission to multiple transmitreceive points (TRPs) based on a determination whether TD repetition is to be applied; and wherein the memory is configured to store the DCI.

[00197] In Example 2, the subject matter of Example 1 includes, wherein the processing circuitry is further configured to use type-A slot-based repetition for the UL transmission. [00198] 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 the UL transmission.

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

[00200] In Example 5, the subject matter of Examples 1-4 includes, wherein: the UL transmission is a Physical Uplink Shared Channel (PUSCH) transmission, and the processing circuitry is further configured to, in a first mode, associate a PUSCH transmission in a first panel with a first sounding reference signal (SRS) resource set and a PUSCH transmission in a second panel with a second SRS resource set, and, in a second mode, associate the PUSCH transmission in the first panel with the second SRS resource set and the PUSCH transmission in the second panel with the first SRS resource set.

[00201] 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).

[00202] 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.

[00203] In Example 8, the subject matter of Examples 1-7 includes, wherein the processing circuitry is further configured to determine for each panel a redundancy version (RV) for a STxMP Physical Uplink Shared Channel (PUSCH) with and without TD repetition based on a single DCI, the RV for each panel dependent on whether each panel is configured to transmit an identical transmission block (TB) or different TBs, the single DCI including a number of TD repetitions.

[00204] In Example 9, the subject matter of Example 8 includes, wherein the processing circuitry is further configured to determine, based on an RV offset value in the single DCI, an RV offset for each panel dependent on whether each panel is configured to transmit the identical TB or different TBs.

[00205] In Example 10, the subject matter of Examples 1-9 includes, wherein the processing circuitry is further configured to use frequency domain multiplexing (FDM) for the STxMP UL transmission, consecutive physical resource blocks (PRBs) in an UL bandwidth part (BWP) being allocated for the UL transmission by different panels.

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

[00207] In Example 12, the subject matter of Example 11 includes, wherein the processing circuitry is further configured to determine a frequency offset between a starting PRB of the UL transmission in the panels from at least one of: higher layer signaling via at least one of remaining 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.

[00208] In Example 13, the subject matter of Examples 11-12 includes, wherein the processing circuitry is further configured to determine a frequency offset between a starting PRB of the UL transmission in the panels based on a frequency offset configured for intra-slot, inter-repetition, or inter-slot frequency hopping of the UL transmission.

[00209] In Example 14, the subject matter of Examples 1-13 includes, wherein the processing circuitry is further configured to use frequency domain multiplexing (FDM) for the STxMP UL transmission, interleaved physical resource blocks (PRBs) in an UL bandwidth part (BWP) being allocated for the UL transmission by different panels.

[00210] In Example 15, the subject matter of Example 14 includes, wherein the processing circuitry is further configured to determine a number of PRBs of each panel from at least one of: higher layer signaling via at least one of remaining minimum system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling, 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.

[00211] In Example 16, the subject matter of Examples 14-15 includes, wherein the processing circuitry is further configured to determine a frequency resource for each 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.

[00212] 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 a single DCI, a number of TD repetitions, mapping type, and starting and length indicator value (SLIV) for TDRA.

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

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

[00215] In Example 20, the subject matter of Examples 18-19 includes, wherein the processing circuitry is further configured to determine, for TD repetition without the at least one of frequency 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.

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

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

[00218] In Example 23, the subject matter of Examples 21-22 includes, wherein the processing circuitry is further configured to determine from multiple 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.

[00219] In Example 24, the subject matter of Examples 1-23 includes, wherein the processing circuitry is further configured to: use spatial domain multiplexing (SDM) STxMP UL transmission with TD repetition with beam cycling, and one of: use two different sounding reference signal (SRS) resource sets for the STxMP UL transmission with beam cycling for each panel, an SRS resource set indication configured to indicate whether beam cycling is enabled for the STxMP UL transmission, or use identical two SRS resource sets for the STxMP UL transmission with beam cycling for each panel, each STxMP UL transmission for each panel is associated with different SRS resource sets.

[00220] In Example 25, the subject matter of Examples 1-24 includes, wherein: the processing circuitry is further configured to multiplex an aperiodic- channel state information (A-CSI) or semi-persistent CSI (SP-CSI) transmission with the STxMP UL transmission through multiple panels, for a spatial domain multiplexing (SDM) scheme, frequency domain multiplexing (FDM) scheme A, or a single frequency network (SFN)-based transmission scheme, a number of resources allocated for the A-CSI or SP-CSI transmission is determined in accordance with a total resource allocated for the STxMP UL transmission for both panels, and for an FDM scheme B and a SDM repetition scheme, a number of resources allocated for the A-CSI or SP-CSI transmission is determined in accordance with resource allocation for the STxMP UL transmission for each panel, respectively.

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

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

[00223] In Example 28, the subject matter of Example 27 includes, wherein the maximum ranks are mapped to different UE capability value sets.

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

[00225] In Example 30, the subject matter of Examples 1-29 includes, wherein 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, SRS resources from SRS resource sets corresponding to the TRPs for codebook (nCB)-based STxMP UL transmissions with identical numbers of ports in the SRS resources.

[00226] In Example 31, the subject matter of Examples 1-30 includes, wherein the processing circuitry is further configured to determine SRS resources from SRS resource sets corresponding to the TRPs for codebook (nCB)-based STxMP UL transmissions with identical numbers of ports in the SRS resources without use of a sounding reference signal (SRS) resource indication (SRI) field in the at least one DCI.

[00227] In Example 32, the subject matter of Examples 1-31 includes, wherein the processing circuitry is further configured to determine, from separate sounding reference signal (SRS) resource indication (SRI) fields in the at least one DCI, SRS resources from SRS resource sets corresponding to the TRPs for non-codebook (nCB)-based STxMP UL transmissions and CB-based STxMP UL transmissions independent of a number of ports in the SRS resources.

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

[00229] 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 and second panel in the PUCCH resource.

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

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

[00232] 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: a PUCCH spatial relation Activation/Deactivation or PUCCH Power Control Set Update for multiple TRP PUCCH repetition Medium Access Control - Control Element (MAC-CE), a PUCCH resource configuration, or PUCCH spatial relation information. [00233] In Example 38, the subject matter of Examples 33-37 includes, wherein: a first and second PUCCH resource indicator (PRI) in a DCI format 1 1 or 1 2 for scheduling a physical downlink shared channel (PDSCH) in a single DCI STxMP PUCCH transmission scheme, and the processing circuitry is further configured to use at least one of the first and second PRI or a starting positioning of a control channel element (CCE) for a corresponding PDCCH transmission to respectively determine a first and second PUCCH resource from the first and second panel.

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

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

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

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

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

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

[00240] Example 45 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-44.

[00241] Example 46 is an apparatus comprising means to implement of any of Examples 1-44.

[00242] Example 47 is a system to implement of any of Examples 1-44.

[00243] Example 48 is a method to implement of any of Examples 1-44.

[00244] Although an embodiment has been described with reference to specific example embodiments, it will be evident 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 rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00245] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [00246] In this document, the terms "a" or "an" are used, as is common in patent documents, to indicate one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. As indicated herein, although the term “a” is used herein, one or more of the associated elements may be used in different embodiments. For example, the term “a processor” configured to carry out specific operations includes both a single processor configured to carry out all of the operations as well as multiple processors individually configured to carry out some or all of the operations (which may overlap) such that the combination of processors carry out all of the operations. Further, the term “includes” may be considered to be interpreted as “includes at least” the elements that follow.

[00247] The 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, in the foregoing Detailed Description, it may be seen 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. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.