Transmission precoding matrix indicator (TPMI) indication and antenna switching for 3 transmit antennas

Abstract

Various embodiments herein relate to a user equipment (UE) that is configured to identify a downlink control information (DCI) that schedules transmission of a physical uplink shared channel (PUSCH). The DCI may also include an indication that the PUSCH is to be transmitted using three antenna ports of the UE. Other embodiments may be described and / or claimed.

Description

[0001] TRANSMISSION PRECODING MATRIX INDICATOR (TPMI) INDICATION AND ANTENNA SWITCHING FOR 3 TRANSMIT ANTENNAS CROSS REFERENCE TO RELATED APPLICATION The present application claims priority to U.S. Provisional Patent Application No.63 / 549,902, which was filed February 5th, 2024. BACKGROUND Various embodiments generally may relate to the field of wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings. Figure 1 illustrates an example of three transmit (Tx) antennas at a user equipment (UE), in accordance with various embodiments. Figure 2 depicts an example of one sounding reference signal (SRS) resource set for antenna switching for a 3T6R configuration, in accordance with various embodiments. Figure 3 depicts an example of two SRS resource setes for antenna switching for a 3T6R configuration, in accordance with various embodiments. Figure 4 depicts an example of two SRS resource sets for antenna switching for a 3T4R configuration, in accordance with various embodiments. Figure 5 depicts an example of two SRS resource sets for antenna switching for 3T8R, in accordance with various embodiments. Figure 6 depicts an example of three SRS resource sets for antenna switching for a 3T8R configuration, in accordance with various embodiments. Figure 7 schematically illustrates a wireless network in accordance with various embodiments. Figure 8 schematically illustrates components of a wireless network in accordance with various embodiments. Figure 9 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Figure 10 illustrates a network in accordance with various embodiments. Figure 11 depicts an example procedure for practicing the various embodiments discussed herein. Figure 12 depicts another example procedure for practicing the various embodiments discussed herein. Figure 13 depicts another example procedure for practicing the various embodiments discussed herein. Figure 14 depicts another example procedure for practicing the various embodiments discussed herein. DETAILED DESCRIPTION The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A), (B), or (A and B). Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in the third generation partnership project (3GPP) technical report (TR) 21.905 v16.0.0 (2019-06). In the 3GPP new radio (NR) specifications, 1-port, 2-port, 4-port and 8-port based physical uplink shared channel (PUSCH) transmissions are supported. However, current commercial mobile user equipments (UEs) are generally equipped with only 1 or 2 transmit (Tx) antennas. To enhance the uplink (UL) performance and anticipating advancements in hardware and design technology, the emergence of UEs equipped with 3 Tx antennas is a foreseeable development in the near future. Consequently, it may be advantageous to augment the NR standards to support 3- port PUSCH supporting up to 3 layers. Figure 1 illustrates an example of 3 Tx antennas at UE side. To support 3 antenna ports for codebook based PUSCH transmissions, signalling enhancements including precoding information may be considered for PUSCH transmissions that are scheduled by downlink control information (DCI) format 0_1 and 0_2. Further, as defined in NR, sounding reference signal (SRS) antenna switching can be used to obtain channel state information (CSI) information for downlink (DL) precoder calculation in the time division duplexed (TDD) system with reciprocity-based operation. In the 3GPP release- 15 and release-16 (Rel-15 and Rel-16) specifications, 1T2R (1 Tx port and 2 receive (Rx) ports), 2T4R (2 Tx ports and 4 Rx ports), and 1T4R (1 Tx port and 4 Rx ports) configurations were supported. The 3GPP Release-17 (Rel-17) specifications further included support of 1T8R (1 Tx port and 8 Rx ports), 1T6R (1 Tx port and 6 Rx ports), 2T8R (2 Tx ports and 8 Rx ports), 2T6R (2 Tx ports and 6 Rx ports), and 4T8R (4 Tx ports and 8 Rx ports) configurations. In case of 3 Tx antenna ports, mechanisms on antenna switching for DL CSI acquisition may need to be updated. Various embodiments herein provide systems and methods for transmitted precoding matrix indication (TPMI) indication and antenna switching for 3 Tx antennas. For example, aspects of various embodiments may include one or more of the following: • Non-coherent codebook design for 3 Tx antennas • Precoding information and number of layers for 3Tx antennas • Antenna switching for 3 Tx antennas Non-coherent codebook design for 3 Tx antennas Embodiments of non-coherent codebook design for 3 Tx antennas are provided as follows: In one embodiment, for ng=3 (non-coherent) codebook for 3 Tx antennas, precoding matrix W for single-layer transmission using three antenna ports can be given by the following with P=√3 11 1 0 10^1^1In addition precoding matrix transmission using three antenna ports for ng=2 (partial coherent) transmission can be given by the following with P=√3 and ^ in any given position taking a value from {1, -1, j, -j} 0 In addition using three antenna ports for ng=1 (full coherent) transmission can be given by the following with P=√3 and ^ in any given position taking a value from {1, -1, j, -j} 1^^^^ In addition, precoding matrix W for two-layer ng=3 (non-coherent) transmission using three antenna ports can be given by the following with P=√3 11 0 1 1 0 1 0 0^ ^0 1^ ,^ ^0 0^ ,^ ^1 0^1In addition, precoding coherent) transmission using three antenna ports can be and ^ in any given position taking a value from {1, -1, j, -j} 1^ 0 1 ^ 0 1 0 ^^ ^^ 0^ ,^ ^0 ^^ ,^ ^^ 0^0 ^ ^ ^ 0In addition precoding matrix W for two- using three antenna ports for ng=1 (full coherent) transmission can be given with P=√6 and ^ in any given position taking a value from {1, -1, j, -j} 1^ ^^ ^^ ^^Further, precoding matrix W for ng=3 (non-coherent) transmission using three antenna ports can be given by the following with P=√3 11 0 0^ ^0 1 0^0 0 1In addition, precoding matrix W for three-layer ng=2 (partial coherent) transmission using three antenna ports can be given by the following with P=√5 and ^ in any given position taking a value from {1, -1, j, -j} 1^ ^ 0 1 ^ ^ 0 1 0 0 ^^^ ^ ^^ ^^ ^ 0^0Further, transmission using three antenna ports can be given by the following with P=3 and ^ in any given position taking a value from {1, -1, j, -j} 1^ ^ ^^^ ^ ^^^In one aspect for codebook- port selection is performed with two sets of ports {0} and {1,2}. A 2Tx codebook (e.g., a code book related to transmission on two Tx ports) along with such port selection is used for PUSCH transmission on 3 Tx ports. In one aspect, port selection is performed using SRS resource indicator with a 1-port SRS resource associated with port {0} and a 2-port SRS resource associated with ports {1,2}. when a 1-port SRS resource is selected, no TPMI is applied for a 1-layer transmission. when a 2-port SRS resource is selected TPMI associated with a 2Tx codebook is applied for a 1 or 2 layer transmission. A 1-port SRS resource and a 2-port SRS resource may be simultaneously selected. In one aspect for codebook-based transmission, port selection is performed with three sets of ports {0}, {1} and {2} each associated with a 1-port SRS resource. In one aspect, port selection is performed using a SRS resource indicator. When one SRS resource is selected no TPMI is applied for a 1-layer transmission. When two SRS resources are selected a TPMI from a 2Tx codebook is applied for a 1-layer or a 2-layer transmission. In one aspect, when two SRS resources are selected no TPMI is applied for a 2-layer transmission. When three SRS resources are selected no TPMI is applied for a 3-layer transmission. In one aspect for non-codebook-based transmission, port selection is performed with three sets of ports {0}, {1} and {2} each associated with a 1-port SRS resource. In one aspect, port selection is performed using a SRS resource indicator. One SRS resource is selected for a 1-layer transmission. Two SRS resources are selected for a 2-layer transmission. Three SRS resources are selected for a 3-layer transmission. Precoding information and number of layers for 3Tx antennas Embodiments of precoding information and number of layers for 3Tx antennas are provided as follows: In one embodiment, for 3 antenna ports for PUSCH scheduled by DCI format 0_1, 0_2 and / or 0_3, precoding information and number of layers or second precoding information field may have 3 bits if txConfig = codebook, ul-FullPowerTransmission is not configured, transform precoder is disabled, and according to the values of higher layer parameters maxRank if multipanelScheme is not configured or max{maxRank, maxRankSfn} if multipanelScheme = sfnScheme or max{maxRank, maxRankSdm} if multipanelScheme = sdmScheme, and codebookSubset. Table 1 illustrates an example field for Precoding information and number of layers or Second Precoding information for 3 antenna ports.

[0002] Table 1. Example precoding information and number of layers or Second Precoding information, for 3 antenna ports, if transform precoder is disabled, maxRank = 2 or 3 or max{maxRank, maxRankSfn} = 2 or 3 or max{maxRank, maxRankSdm} = 2 or 3 or maxRankSdm= 2, and ul-FullPowerTransmission is not configured Bit field mapped codebookSubset = nonCoherent to index In another em o e , o a e a po s o sc e u e y DCI format 0_1, 0_2 and / or 0_3, in case of multiple transmit and receive point (mTRP)-based PUSCH repetitions, PUSCH repetition for the second transmit and receive point (TRP) has same number of layers indicated by precoding information and number of layers fields for 3 antenna ports. Further, second Precoding information field has 2 bits, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission is not configured, transform precoder is disabled, and according to the values of higher layer parameters maxRank if multipanelScheme is not configured or maxRankSfn if multipanelScheme = sfnScheme, and codebookSubset; Table 2 illustrates an example field for P second Precoding information field for 3 antenna ports.

[0003] Table 2. Example of second precoding information, for 3 antenna ports, if transform precoder is disabled, maxRank = 2 or 3 or maxRankSfn = 2, and ul- FullPowerTransmission is not configured Bit field mapped to codebookSubset = nonCoherent index Antenna sw c ng or x an enna Embodiments of antenna switching for 3 Tx antennas are provided as follows: In one embodiment, 3T6R (3 Tx port and 6 Rx port), 3T4R (3 Tx port and 4 Rx port) and / or 3T8R (3 Tx port and 8 Rx port) configurations may be supported for antenna switching for DL channel state information (CSI) acquisition. For periodic and / or semi-persistent SRS configuration, zero or one or two SRS resource sets may be configured for antenna switching for 3T6R and / or 3T4R case. For 3T8R case, zero or one or two or three SRS resource sets may be configured for antenna switching. For aperiodic SRS configuration, zero or one or two SRS resource sets may be configured for antenna switching with 3T6R and / or 3T4R. For 3T8R case, zero or one or two or three SRS resource sets may be configured for antenna switching. In another embodiment, when one SRS resource set is configured for antenna switching, for 3T6R case, one SRS resource set has two SRS resources, where each SRS resource has 3 ports and the two SRS resources are transmitted in the different symbols. The SRS ports associated with the first SRS resource is different from the SRS ports associated with the second SRS resource. For 3T4R case, one SRS resource set has two SRS resources, where a first SRS resource has 3 ports and a second SRS resource has 1 ports and the two SRS resources are transmitted in the different symbols. Further, for a SRS resource set, SRS ports of the resource are associated with a different UE antenna ports. Figure 2 illustrates one example of one SRS resource set for antenna switching for 3T6R. In the figure, one SRS resource set has two SRS resources, where each SRS resource has two subsets, where the first subset has 1 port SRS and second subset has 2 port SRS. The first and second subsets are transmitted in different symbols. Further, a guard symbol may be inserted between two SRS resources with 3 antenna ports. In this case, SRS ports of the first and second SRS resources are associated with different UE antenna ports for 3T6R case. In another embodiment, when two SRS resource sets are configured for antenna switching, for 3T6R case, each SRS resource set has one SRS resource. In this case, a total of two SRS resources are transmitted in different symbols of two different slots, where each SRS resource has 3 ports. Further, the SRS ports of each SRS resource in the given two sets are associated with a different UE antenna ports. In some aspects, this may only apply to the case of aperiodic SRS resource. Figure 3 illustrates one example of two SRS resource sets for antenna switching for 3T6R. In the figure, two SRS resource sets are configured, where each SRS resource set includes one SRS resource that are transmitted in different slots. Further, each SRS resource has two subsets, where the first subset has 1 port SRS and second subset has 2 port SRS. The first and second subset are transmitted in different symbols. In this case, SRS ports of the resources in the first and second SRS resource sets are associated with different UE antenna ports for 3T6R case. In another embodiment, when two SRS resource sets are configured for antenna switching, for 3T4R case, a total of two SRS resources are transmitted in different symbols of two different slots. In this case, a first SRS resource set includes a first SRS resource and a second SRS resource set includes a second SRS resource, respectively. In addition, a first SRS resource has 3 ports and a second SRS resource has 1 port, or a first SRS resource has 2 ports and a second SRS resource has 2 ports. Further, the SRS ports of each SRS resource in the given two sets are associated with a different UE antenna ports. Figure 4 illustrates one example of two SRS resource sets for antenna switching for 3T4R. In the figure, two SRS resource sets are configured, where each SRS resource set includes one SRS resource that are transmitted in different slots. Further, the first SRS resource has 3 ports and the second SRS resource has 1 port. In this case, SRS ports of the resources in the first and second SRS resource sets are associated with different UE antenna ports for 3T4R case. In another embodiment, when two SRS resource sets are configured for antenna switching, for 3T8R case, a total of three SRS resources are transmitted in different symbols of two different slots. In this case, a first SRS resource set includes a first and second SRS resources and a second SRS resource set includes a third SRS resource, respectively. In addition, the first and second SRS resources each has 3 ports and a third SRS resource has 2 ports. In another option, the first SRS resource has 3 ports, the second SRS resource has 2 ports and the third SRS resource has 3 ports. In another option, the first SRS resource has 2 ports, the second SRS resource has 3 ports and the third SRS resource has 3 ports. Further, the SRS ports of each SRS resource in the given two sets are associated with a different UE antenna ports. Figure 5 illustrates one example of two SRS resource sets for antenna switching for 3T8R. In the figure, two SRS resource sets are configured, where a first SRS resource set includes two SRS resources and a second SRS resource set includes one SRS resource that are transmitted in different slots. Further, the SRS resources in the first SRS resource set each has 3 ports and the SRS resource in the second SRS resource set has 2 ports. In this case, SRS ports of the resources in the first and second SRS resource sets are associated with different UE antenna ports for 3T8R case. In another embodiment, when three SRS resource sets are configured for antenna switching, for 3T8R case, a total of three SRS resources are transmitted in different symbols of three different slots. In this case, each SRS resource set includes one SRS resource. In addition, the first and second SRS resources each has 3 ports and a third SRS resource has 2 ports. In another option, the first SRS resource has 3 ports, the second SRS resource has 2 ports and the third SRS resource has 3 ports. In another option, the first SRS resource has 2 ports, the second SRS resource has 3 ports and the third SRS resource has 3 ports. Further, the SRS ports of each SRS resource in the given three sets are associated with a different UE antenna ports. Figure 6 illustrates one example of three SRS resource sets for antenna switching for 3T8R. In the figure, three SRS resource sets are configured, where each SRS resource set includes one SRS resource. Further, the SRS resources in the first SRS and second resource set each has 3 ports and the SRS resource in the third SRS resource set has 2 ports. In this case, SRS ports of the resources in the three SRS resource sets are associated with different UE antenna ports for 3T8R case. Simultaneous multi panel transmission (STxMP) with 3Tx ports In one embodiment, dedicated digital ports for each panel is considered. The maxRank corresponding to single TRP transmission is 1 or 2 while the maxRank in STxMP mode corresponding to the first panel is 1 or 2 and the maxRank corresponding to the second panel is 1. The SRS resource set corresponding to the first panel comprises of a SRS resource with 2 ports and the SRS resource set corresponding to the second panel comprises of a SRS resource with 1 port. Panel-1: 2 Tx PUSCH (maxRank=2), SRS ports = 2 Panel-2: 1 Tx PUSCH (maxRank=1), SRS ports = 1 In another embodiment, shared digital ports across two panels is considered. The maxRank corresponding to single TRP transmission is 3 while the maxRank in STxMP mode corresponding to the first panel is 1 or 2 and the maxRank corresponding to the second panel is 1. The SRS resource set corresponding to the first panel comprises of 3 SRS ports and the SRS resource set corresponding to the second panel comprises of 3 SRS ports. Panel-1: 2 Tx PUSCH (maxRank=2), SRS ports = 3 Panel-2: 1 Tx PUSCH (maxRank=1), SRS ports = 3 SYSTEMS AND IMPLEMENTATIONS Figures 7-10 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments. Figure 7 illustrates a network 700 in accordance with various embodiments. The network 700 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like. The network 700 may include a UE 702, which may include any mobile or non-mobile computing device designed to communicate with a RAN 704 via an over-the-air connection. The UE 702 may be communicatively coupled with the RAN 704 by a Uu interface. The UE 702 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. In some embodiments, the network 700 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. In some embodiments, the UE 702 may additionally communicate with an AP 706 via an over-the-air connection. The AP 706 may manage a WLAN connection, which may serve to offload some / all network traffic from the RAN 704. The connection between the UE 702 and the AP 706 may be consistent with any IEEE 802.11 protocol, wherein the AP 706 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 702, RAN 704, and AP 706 may utilize cellular-WLAN aggregation (for example, LWA / LWIP). Cellular-WLAN aggregation may involve the UE 702 being configured by the RAN 704 to utilize both cellular radio resources and WLAN resources. The RAN 704 may include one or more access nodes, for example, AN 708. AN 708 may terminate air-interface protocols for the UE 702 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 708 may enable data / voice connectivity between CN 720 and the UE 702. In some embodiments, the AN 708 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 708 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 708 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. In embodiments in which the RAN 704 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 704 is an LTE RAN) or an Xn interface (if the RAN 704 is a 5G RAN). The X2 / Xn interfaces, which may be separated into control / user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data / context transfers, mobility, load management, interference coordination, etc. The ANs of the RAN 704 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 702 with an air interface for network access. The UE 702 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 704. For example, the UE 702 and RAN 704 may use carrier aggregation to allow the UE 702 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first / second ANs may be any combination of eNB, gNB, ng-eNB, etc. The RAN 704 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium / carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol. In V2X scenarios the UE 702 or AN 708 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications / software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. In some embodiments, the RAN 704 may be an LTE RAN 710 with eNBs, for example, eNB 712. The LTE RAN 710 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operating on sub-6 GHz bands. In some embodiments, the RAN 704 may be an NG-RAN 714 with gNBs, for example, gNB 716, or ng-eNBs, for example, ng-eNB 718. The gNB 716 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 716 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 718 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 716 and the ng-eNB 718 may connect with each other over an Xn interface. In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 714 and a UPF 748 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN714 and an AMF 744 (e.g., N2 interface). The NG-RAN 714 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS / SSS / PBCH. In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 702 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 702, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 702 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 702 and in some cases at the gNB 716. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. The RAN 704 is communicatively coupled to CN 720 that includes network elements to provide various functions to support data and telecommunications services to customers / subscribers (for example, users of UE 702). The components of the CN 720 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 720 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 720 may be referred to as a network slice, and a logical instantiation of a portion of the CN 720 may be referred to as a network sub-slice. In some embodiments, the CN 720 may be an LTE CN 722, which may also be referred to as an EPC. The LTE CN 722 may include MME 724, SGW 726, SGSN 728, HSS 730, PGW 732, and PCRF 734 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 722 may be briefly introduced as follows. The MME 724 may implement mobility management functions to track a current location of the UE 702 to facilitate paging, bearer activation / deactivation, handovers, gateway selection, authentication, etc. The SGW 726 may terminate an S1 interface toward the RAN and route data packets between the RAN and the LTE CN 722. The SGW 726 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The SGSN 728 may track a location of the UE 702 and perform security functions and access control. In addition, the SGSN 728 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 724; MME selection for handovers; etc. The S3 reference point between the MME 724 and the SGSN 728 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states. The HSS 730 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 730 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 730 and the MME 724 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 720. The PGW 732 may terminate an SGi interface toward a data network (DN) 736 that may include an application / content server 738. The PGW 732 may route data packets between the LTE CN 722 and the data network 736. The PGW 732 may be coupled with the SGW 726 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 732 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 732 and the data network 736 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 732 may be coupled with a PCRF 734 via a Gx reference point. The PCRF 734 is the policy and charging control element of the LTE CN 722. The PCRF 734 may be communicatively coupled to the app / content server 738 to determine appropriate QoS and charging parameters for service flows. The PCRF 732 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI. In some embodiments, the CN 720 may be a 5GC 740. The 5GC 740 may include an AUSF 742, AMF 744, SMF 746, UPF 748, NSSF 750, NEF 752, NRF 754, PCF 756, UDM 758, and AF 760 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 740 may be briefly introduced as follows. The AUSF 742 may store data for authentication of UE 702 and handle authentication- related functionality. The AUSF 742 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 740 over reference points as shown, the AUSF 742 may exhibit an Nausf service-based interface. The AMF 744 may allow other functions of the 5GC 740 to communicate with the UE 702 and the RAN 704 and to subscribe to notifications about mobility events with respect to the UE 702. The AMF 744 may be responsible for registration management (for example, for registering UE 702), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 744 may provide transport for SM messages between the UE 702 and the SMF 746, and act as a transparent proxy for routing SM messages. AMF 744 may also provide transport for SMS messages between UE 702 and an SMSF. AMF 744 may interact with the AUSF 742 and the UE 702 to perform various security anchor and context management functions. Furthermore, AMF 744 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 704 and the AMF 744; and the AMF 744 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 744 may also support NAS signaling with the UE 702 over an N3 IWF interface. The SMF 746 may be responsible for SM (for example, session establishment, tunnel management between UPF 748 and AN 708); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 748 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 744 over N2 to AN 708; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 702 and the data network 736. The UPF 748 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 736, and a branching point to support multi-homed PDU session. The UPF 748 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 748 may include an uplink classifier to support routing traffic flows to a data network. The NSSF 750 may select a set of network slice instances serving the UE 702. The NSSF 750 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 750 may also determine the AMF set to be used to serve the UE 702, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 754. The selection of a set of network slice instances for the UE 702 may be triggered by the AMF 744 with which the UE 702 is registered by interacting with the NSSF 750, which may lead to a change of AMF. The NSSF 750 may interact with the AMF 744 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 750 may exhibit an Nnssf service-based interface. The NEF 752 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure, AFs (e.g., AF 760), edge computing or fog computing systems, etc. In such embodiments, the NEF 752 may authenticate, authorize, or throttle the AFs. NEF 752 may also translate information exchanged with the AF 760 and information exchanged with internal network functions. For example, the NEF 752 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 752 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 752 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 752 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 752 may exhibit an Nnef service-based interface. The NRF 754 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 754 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 754 may exhibit the Nnrf service-based interface. The PCF 756 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 756 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 758. In addition to communicating with functions over reference points as shown, the PCF 756 exhibit an Npcf service-based interface. The UDM 758 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 702. For example, subscription data may be communicated via an N8 reference point between the UDM 758 and the AMF 744. The UDM 758 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 758 and the PCF 756, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 702) for the NEF 752. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 758, PCF 756, and NEF 752 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 758 may exhibit the Nudm service-based interface. The AF 760 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control. In some embodiments, the 5GC 740 may enable edge computing by selecting operator / 3rdparty services to be geographically close to a point that the UE 702 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 740 may select a UPF 748 close to the UE 702 and execute traffic steering from the UPF 748 to data network 736 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 760. In this way, the AF 760 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 760 is considered to be a trusted entity, the network operator may permit AF 760 to interact directly with relevant NFs. Additionally, the AF 760 may exhibit an Naf service-based interface. The data network 736 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application / content server 738. Figure 8 schematically illustrates a wireless network 800 in accordance with various embodiments. The wireless network 800 may include a UE 802 in wireless communication with an AN 804. The UE 802 and AN 804 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein. The UE 802 may be communicatively coupled with the AN 804 via connection 806. The connection 806 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies. The UE 802 may include a host platform 808 coupled with a modem platform 810. The host platform 808 may include application processing circuitry 812, which may be coupled with protocol processing circuitry 814 of the modem platform 810. The application processing circuitry 812 may run various applications for the UE 802 that source / sink application data. The application processing circuitry 812 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations The protocol processing circuitry 814 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 806. The layer operations implemented by the protocol processing circuitry 814 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. The modem platform 810 may further include digital baseband circuitry 816 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 814 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / de-mapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions. The modem platform 810 may further include transmit circuitry 818, receive circuitry 820, RF circuitry 822, and RF front end (RFFE) 824, which may include or connect to one or more antenna panels 826. Briefly, the transmit circuitry 818 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 820 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 822 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 824 may include filters (for example, surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 818, receive circuitry 820, RF circuitry 822, RFFE 824, and antenna panels 826 (referred generically as “transmit / receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be disposed in the same or different chips / modules, etc. In some embodiments, the protocol processing circuitry 814 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components. A UE reception may be established by and via the antenna panels 826, RFFE 824, RF circuitry 822, receive circuitry 820, digital baseband circuitry 816, and protocol processing circuitry 814. In some embodiments, the antenna panels 826 may receive a transmission from the AN 804 by receive-beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna panels 826. A UE transmission may be established by and via the protocol processing circuitry 814, digital baseband circuitry 816, transmit circuitry 818, RF circuitry 822, RFFE 824, and antenna panels 826. In some embodiments, the transmit components of the UE 804 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 826. Similar to the UE 802, the AN 804 may include a host platform 828 coupled with a modem platform 830. The host platform 828 may include application processing circuitry 832 coupled with protocol processing circuitry 834 of the modem platform 830. The modem platform may further include digital baseband circuitry 836, transmit circuitry 838, receive circuitry 840, RF circuitry 842, RFFE circuitry 844, and antenna panels 846. The components of the AN 804 may be similar to and substantially interchangeable with like-named components of the UE 802. In addition to performing data transmission / reception as described above, the components of the AN 808 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. Figure 9 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 9 shows a diagrammatic representation of hardware resources 900 including one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 900. The processors 910 may include, for example, a processor 912 and a processor 914. The processors 910 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. The memory / storage devices 920 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 920 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc. The communication resources 930 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 904 or one or more databases 906 or other network elements via a network 908. For example, the communication resources 930 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. Instructions 950 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 910 to perform any one or more of the methodologies discussed herein. The instructions 950 may reside, completely or partially, within at least one of the processors 910 (e.g., within the processor’s cache memory), the memory / storage devices 920, or any suitable combination thereof. Furthermore, any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral devices 904 or the databases 906. Accordingly, the memory of processors 910, the memory / storage devices 920, the peripheral devices 904, and the databases 906 are examples of computer-readable and machine-readable media. Figure 10 illustrates a network 1000 in accordance with various embodiments. The network 1000 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 1000 may operate concurrently with network 700. For example, in some embodiments, the network 1000 may share one or more frequency or bandwidth resources with network 700. As one specific example, a UE (e.g., UE 1002) may be configured to operate in both network 1000 and network 700. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 700 and 1000. In general, several elements of network 1000 may share one or more characteristics with elements of network 700. For the sake of brevity and clarity, such elements may not be repeated in the description of network 1000. The network 1000 may include a UE 1002, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1008 via an over-the-air connection. The UE 1002 may be similar to, for example, UE 702. The UE 1002 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in- vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. Although not specifically shown in Figure 10, in some embodiments the network 1000 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 10, the UE 1002 may be communicatively coupled with an AP such as AP 706 as described with respect to Figure 7. Additionally, although not specifically shown in Figure 10, in some embodiments the RAN 1008 may include one or more ANss such as AN 708 as described with respect to Figure 7. The RAN 1008 and / or the AN of the RAN 1008 may be referred to as a base station (BS), a RAN node, or using some other term or name. The UE 1002 and the RAN 1008 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges. The RAN 1008 may allow for communication between the UE 1002 and a 6G core network (CN) 1010. Specifically, the RAN 1008 may facilitate the transmission and reception of data between the UE 1002 and the 6G CN 1010. The 6G CN 1010 may include various functions such as NSSF 750, NEF 752, NRF 754, PCF 756, UDM 758, AF 760, SMF 746, and AUSF 742. The 6G CN 1010 may additional include UPF 748 and DN 736 as shown in Figure 10. Additionally, the RAN 1008 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 1024 and a Compute Service Function (Comp SF) 1036. The Comp CF 1024 and the Comp SF 1036 may be parts or functions of the Computing Service Plane. Comp CF 1024 may be a control plane function that provides functionalities such as management of the Comp SF 1036, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlying computing infrastructure for computing resource management, etc.. Comp SF 1036 may be a user plane function that serves as the gateway to interface computing service users (such as UE 1002) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 1036 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 1036 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 1024 instance may control one or more Comp SF 1036 instances. Two other such functions may include a Communication Control Function (Comm CF) 1028 and a Communication Service Function (Comm SF) 1038, which may be parts of the Communication Service Plane. The Comm CF 1028 may be the control plane function for managing the Comm SF 1038, communication sessions creation / configuration / releasing, and managing communication session context. The Comm SF 1038 may be a user plane function for data transport. Comm CF 1028 and Comm SF 1038 may be considered as upgrades of SMF 746 and UPF 748, which were described with respect to a 5G system in Figure 7. The upgrades provided by the Comm CF 1028 and the Comm SF 1038 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 746 and UPF 748 may still be used. Two other such functions may include a Data Control Function (Data CF) 1022 and Data Service Function (Data SF) 1032 may be parts of the Data Service Plane. Data CF 1022 may be a control plane function and provides functionalities such as Data SF 1032 management, Data service creation / configuration / releasing, Data service context management, etc. Data SF 1032 may be a user plane function and serve as the gateway between data service users (such as UE 1002 and the various functions of the 6G CN 1010) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status. Another such function may be the Service Orchestration and Chaining Function (SOCF) 1020, which may discover, orchestrate and chain up communication / computing / data services provided by functions in the network. Upon receiving service requests from users, SOCF 1020 may interact with one or more of Comp CF 1024, Comm CF 1028, and Data CF 1022 to identify Comp SF 1036, Comm SF 1038, and Data SF 1032 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 1036, Comm SF 1038, and Data SF 1032 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 1020 may also responsible for maintaining, updating, and releasing a created service chain. Another such function may be the service registration function (SRF) 1014, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 1036 and Data SF 1032 gateways and services provided by the UE 1002. The SRF 1014 may be considered a counterpart of NRF 754, which may act as the registry for network functions. Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 1026, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 1012 and eSCP- U 1034, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 1026 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc. Another such function is the AMF 1044. The AMF 1044 may be similar to 744, but with additional functionality. Specifically, the AMF 1044 may include potential functional repartition, such as move the message forwarding functionality from the AMF 1044 to the RAN 1008. Another such function is the service orchestration exposure function (SOEF) 1018. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications. The UE 1002 may include an additional function that is referred to as a computing client service function (comp CSF) 1004. The comp CSF 1004 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 1020, Comp CF 1024, Comp SF 1036, Data CF 1022, and / or Data SF 1032 for service discovery, request / response, compute task workload exchange, etc. The Comp CSF 1004 may also work with network side functions to decide on whether a computing task should be run on the UE 1002, the RAN 1008, and / or an element of the 6G CN 1010. The UE 1002 and / or the Comp CSF 1004 may include a service mesh proxy 1006. The service mesh proxy 1006 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 1006 may include one or more of addressing, security, load balancing, etc. EXAMPLEPROCEDURESIn some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 7-10, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 11. For example, the process may include, at 1101, receiving a downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) with three antenna ports, wherein the DCI indicates precoding information and a number of layers for the PUSCH. At 1102, the process may further include encoding the PUSCH for transmission with three antenna ports based on the DCI. Figure 12 illustrates another example process in accordance with various embodiments. At 1201, the process may include encoding, for transmission to a user equipment (UE), a downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) with three antenna ports, wherein the DCI indicates precoding information and a number of layers for the PUSCH. At 1202, the process may further include receiving the PUSCH with three antenna ports based on the DCI. Figure 13 illustrates a process that may be performed by a user equipment (UE), one or more elements of a UE, and / or one or more electronic devices that include and / or implement a UE. The process may include identifying, at 1301 from a base station of a cellular network, a downlink control information (DCI) that schedules transmission of a physical uplink shared channel (PUSCH); identifying, at 1302 based on the DCI, that the PUSCH is to be transmitted using three antenna ports of the UE; and transmitting, at 1303, the PUSCH using three antenna ports. Another such process is depicted at Figure 14. The process of Figure 14 may include or relate to a process to be performed by a base station, one or more elements of a base station, and / or one or more electronic devices that include and / or implement a base station. The process may include generating , at 1401, a downlink control information (DCI) that schedules transmission of a physical uplink shared channel (PUSCH), wherein the DCI includes an indication that the PUSCH is to be transmitted using three antenna ports of a user equipment (UE); and transmitting, at 1402, the DCI to the UE. For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section. EXAMPLES Example 1 may include a method comprising: receiving, by a UE from a gNodeB, a precoding information and number of layers field in the downlink control information (DCI) format for scheduling a physical uplink shared channel (PUSCH) with 3 antenna ports; and transmitting, by the UE, the PUSCH with 3 antenna ports in accordance with indicated precoding information and number of layers field. Example 2 may include the method of example 1 and / or some other example herein, wherein precoding matrix W for single-layer transmission using three antenna ports can be given by the following with P=√3 ^1^0^0^ ^0^ ,^1^ ,^0^. 0^0 ^1Example 3 may include the method of example 1 and / or some other example herein, wherein precoding matrix W for two-layer ng=3 (non-coherent) transmission using three antenna ports can be given by the following with P=√3 ^1 0^1 0^0 0^^0 1^ , ^^0 0^ , ^^1 0^.0 0 0 1 0 1Example 4 may include the method of example 1 and / or some other example herein, wherein precoding matrix W for three-layer ng=3 (non-coherent) transmission using three antenna ports can be given by the following with P=√3 11 0 0^ ^0 1 0^0 0 1Example 5 may include the method of example 1 and / or some other example herein, wherein for codebook-based transmission, port selection is performed with two sets of ports {0} and {1,2}. Example 6 may include the method of example 1 and / or some other example herein, wherein for codebook-based transmission, port selection is performed with three sets of ports {0}, {1} and {2} each associated with a 1-port SRS resource. Example 7 may include the method of example 1 and / or some other example herein, wherein for non-codebook-based transmission, port selection is performed with three sets of ports {0}, {1} and {2} each associated with a 1-port SRS resource. Example 8 may include the method of example 1 and / or some other example herein, wherein for 3 antenna ports for PUSCH scheduled by DCI format 0_1, 0_2 and / or 0_3, precoding information and number of layers or second precoding information field may have 3 bits. Example 9 may include the method of example 1 and / or some other example herein, wherein for 3 antenna ports for PUSCH scheduled by DCI format 0_1, 0_2 and / or 0_3, in case of mTRP based PUSCH repetitions, PUSCH repetition for the second TRP has same number of layers indicated by precoding information and number of layers fields for 3 antenna ports. Example 10 may include the method of example 1 and / or some other example herein, wherein 3T6R, 3T4R and / or 3T8R may be supported for antenna switching for DL channel state information (CSI) acquisition. Example 11 may include the method of example 1 and / or some other example herein, wherein when one SRS resource set is configured for antenna switching, for 3T6R case, one SRS resource set has two SRS resources, where each SRS resource has 3 ports and the two SRS resources are transmitted in the different symbols. The SRS ports associated with the first SRS resource is different from the SRS ports associated with the second SRS resource. Example 12 may include the method of example 1 and / or some other example herein, wherein when two SRS resource sets are configured for antenna switching, for 3T6R case, each SRS resource set has one SRS resource. In this case, a total of two SRS resources are transmitted in different symbols of two different slots, where each SRS resource has 3 ports. Example 13 may include the method of example 1 and / or some other example herein, wherein when two SRS resource sets are configured for antenna switching, for 3T4R case, a total of two SRS resources are transmitted in different symbols of two different slots. Example 14 may include the method of example 1 and / or some other example herein, wherein when two SRS resource sets are configured for antenna switching, for 3T8R case, a total of three SRS resources are transmitted in different symbols of two different slots. Example 15 may include the method of example 1 and / or some other example herein, wherein when three SRS resource sets are configured for antenna switching, for 3T8R case, a total of three SRS resources are transmitted in different symbols of three different slots. Example 16 may include the method of example 1 and / or some other example herein, wherein maxRank corresponding to single TRP transmission is 1 or 2 while the maxRank in STxMP mode corresponding to the first panel is 1 or 2 and the maxRank corresponding to the second panel is 1. Example 17 may include the method of example 1 and / or some other example herein, wherein maxRank corresponding to single TRP transmission is 3 while the maxRank in STxMP mode corresponding to the first panel is 1 or 2 and the maxRank corresponding to the second panel is 1. Example 18 may include a method of a user equipment (UE), the method comprising: receiving a downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) with three antenna ports, wherein the DCI indicates precoding information and a number of layers for the PUSCH; and encoding the PUSCH for transmission with three antenna ports based on the DCI. Example 19 may include the method of example 18 and / or some other example herein, wherein the precoding information includes a precoding matrix W for single-layer transmission using three antenna ports, wherein the precoding matrix W corresponds to the following with P=√3: ^1^0^0^ ^0^ , ^^1^ ,^0^. 00 ^1Example 20 may include the method of example 18 and / or some other example herein, wherein the precoding information includes a precoding matrix W for two-layer non-coherent transmission using three antenna ports, wherein the precoding matrix W corresponds to the following with P=√3: ^1 0^1 0 0 0^^0 1^ ,^0 0^ ,^ ^1 0^.0 ^ ^Example 21 may include the some other example herein, wherein the precoding information includes a precoding matrix W for three-layer non-coherent transmission using three antenna ports, wherein the precoding matrix W corresponds to the following with P=√3: ^1 0 00^.1Example 22 may include the 18-21 and / or some other example herein, wherein the PUSCH is transmitted using codebook-based transmission, and wherein the method further comprises performing port selection for the PUSCH with two sets of ports (e.g., {0} and {1,2}). Example 23 may include the method of example 18-21 and / or some other example herein, wherein the PUSCH is transmitted using codebook-based transmission, and wherein the method further comprises performing port selection for the PUSCH with three sets of ports, wherein the individual sets of ports are associated with a 1-port sounding reference signal (SRS) resource. Example 24 may include the method of example 18-21 and / or some other example herein, wherein the PUSCH is transmitted using non-codebook-based transmission, and wherein the method further comprises performing port selection for the PUSCH with three sets of ports, wherein the individual sets of ports are associated with a 1-port sounding reference signal (SRS) resource. Example 25 may include the method of example 18-24 and / or some other example herein, wherein the DCI has a DCI format 0_1, 0_2, or 0_3. Example 26 may include the method of example 18-25 and / or some other example herein, wherein the precoding information and number of layers are indicated by 3 bits. Example 27 may include the method of example 18-26 and / or some other example herein, wherein the PUSCH is transmitted using multi-transmit-receive point (TRP) based repetitions, and wherein a PUSCH repetition for a second TRP has a same number of layers as the PUSCH transmitted to a first TRP. Example 28 may include the method of example 18-27 and / or some other example herein, further comprising receiving configuration information for antenna switching for downlink (DL) channel state information (CSI) based on 3 transmit antenna ports and 6 receive antenna ports (3T6R), 3T4R and / or 3T8R; and receiving the DL CSI with antenna switching based on the configuration information. Example 29 may include the method of example 18-28 and / or some other example herein, further comprising receiving configuration information for a sounding reference signal (SRS) resource set for antenna switching with 3T6R operation, wherein the SRS resource set includes two SRS resources, wherein the respective SRS resources have three ports and are transmitted in different symbols. Example 30 may include the method of example 29 and / or some other example herein, wherein the ports of the respective SRS resources are different from one another. Example 31 may include the method of example 18-28 and / or some other example herein, further comprising receiving configuration information for two sounding reference signal (SRS) resource sets for antenna switching with 3T6R operation, wherein the respective SRS resource sets include a SRS resource with three ports. Example 32 may include the method of example 31 and / or some other example herein, wherein the respective SRS resources are transmitted in different slots from one another. Example 33 may include the method of example 18-32 and / or some other example herein, further comprising receiving configuration information for two SRS resource sets for antenna switching with 3T4R operation, wherein the respective SRS resource sets include a SRS resource transmitted in different symbols of two different slots from one another. Example 34 may include the method of example 18-33 and / or some other example herein, further comprising receiving configuration information for first and second SRS resource sets for antenna switching with 3T8R operation, wherein the first SRS resource set includes two SRS resources and the second SRS resource set includes one SRS resource. Example 35 may include the method of example 34 and / or some other example herein, wherein the second SRS resource set is transmitted in a different slot from the first SRS resource set. Example 36 may include the method of example 18-33 and / or some other example herein, further comprising receiving configuration information for three SRS resource sets for antenna switching with 3T8R operation, wherein the respective SRS resource sets include a SRS resource transmitted in different symbols of different slots from one another. Example 37 may include a method of a next generation Node B (gNB), the method comprising: encoding, for transmission to a user equipment (UE), a downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) with three antenna ports, wherein the DCI indicates precoding information and a number of layers for the PUSCH; and receiving the PUSCH with three antenna ports based on the DCI. Example 38 may include a method to be performed by a user equipment (UE), one or more elements of a UE, and / or one or more electronic devices that include and / or implement a UE, wherein the method comprises: identifying, from a base station of a cellular network, a downlink control information (DCI) that schedules transmission of a physical uplink shared channel (PUSCH); identifying, based on the DCI, that the PUSCH is to be transmitted using three antenna ports of the UE; and transmitting the PUSCH using three antenna ports. Example 39 may include the method of example 38, and / or one or more other examples herein, wherein the DCI includes an indication of precoding information to be used for transmitting the PUSCH using the three antenna ports. Example 40 may include the method of example 39, and / or one or more other examples herein, wherein the method further comprising identifying, based on the indication of the precoding information a transmission precoding matrix indicator (TPMI) to be used for transmitting the PUSCH using the three antenna ports. Example 41 may include the method of any of examples 38-40, and / or one or more other examples herein, wherein the DCI includes an indication of a number of layers that are to be used for transmitting the PUSCH using the three antenna ports. Example 42 may include the method of any of examples 38-41, and / or one or more other examples herein, wherein the DCI includes an indication of a non-coherent codebook that is to be used for transmitting the PUSCH using the three antenna ports. Example 43 may include the method of any of examples 38-42, and / or one or more other examples herein, wherein the DCI is a DCI format 0_1 or a DCI format 0_2. Example 44 may include the method of any of examples 38-43, and / or one or more other examples herein, wherein the DCI includes an indication of a sounding reference signal (SRS) set to be used for antenna switching with three antenna ports for a downlink channel state information (CSI) acquisition. Example 45 may include 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 and / or implement a base station, wherein the method comprises: generating a downlink control information (DCI) that schedules transmission of a physical uplink shared channel (PUSCH), wherein the DCI includes an indication that the PUSCH is to be transmitted using three antenna ports of a user equipment (UE); and transmitting the DCI to the UE. Example 46 may include the method of example 45, and / or one or more other examples herein, wherein the indication that the PUSCH is to be transmitted using three antenna ports includes an indication of precoding information to be used for transmitting the PUSCH using the three antenna ports. Example 47 may include the method of example 46, and / or one or more other examples herein, wherein the indication of the precoding information includes a transmission precoding matrix indicator (TPMI) that is to be used for transmitting the PUSCH using the three antenna ports. Example 48 may include the method of any of examples 45-47, and / or one or more other examples herein, wherein the indication that the PUSCH is to be transmitted using three antenna ports includes an indication of a number of layers that are to be used for transmitting the PUSCH using the three antenna ports. Example 49 may include the method of any of examples 45-48, and / or one or more other examples herein, wherein the indication that the PUSCH is to be transmitted using three antenna ports includes an indication of a non-coherent codebook that is to be used for transmitting the PUSCH using the three antenna ports. Example 50 may include the method of any of examples 45-49, and / or one or more other examples herein, wherein the DCI is a DCI format 0_1 or a DCI format 0_2. Example 51 may include the method of any of examples 45-49, and / or one or more other examples herein, wherein the DCI includes an indication of a sounding reference signal (SRS) set to be used for antenna switching with three antenna ports for a downlink channel state information (CSI) acquisition. Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-51, and / or any other method or process described herein. Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-51, and / or any other method or process described herein. Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-51, and / or any other method or process described herein. Example Z04 may include a method, technique, or process as described in or related to any of examples 1-51, and / or portions or parts thereof. Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-51, and / or portions thereof. Example Z06 may include a signal as described in or related to any of examples 1-51, or portions or parts thereof. Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-51, and / or portions or parts thereof, or otherwise described in the present disclosure. Example Z08 may include a signal encoded with data as described in or related to any of examples 1-51, and / or portions or parts thereof, or otherwise described in the present disclosure. Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-51, and / or portions or parts thereof, or otherwise described in the present disclosure. Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-51, and / or portions thereof. Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-51, and / or portions thereof. Example Z12 may include a signal in a wireless network as shown and described herein. Example Z13 may include a method of communicating in a wireless network as shown and described herein. Example Z14 may include a system for providing wireless communication as shown and described herein. Example Z15 may include a device for providing wireless communication as shown and described herein. Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Claims

CLAIMS 1. An apparatus for use in a user equipment (UE), wherein the apparatus comprises: memory to store, a downlink control information (DCI) received from a base station, wherein the DCI schedules transmission of a physical uplink shared channel (PUSCH); and one or more processors configured to: identify, based on the DCI, that the PUSCH is to be transmitted using three antenna ports of the UE; and encoding the PUSCH for transmission using three antenna ports.

2. The apparatus of claim 1, wherein the DCI includes an indication of precoding information to be used for transmitting the PUSCH using the three antenna ports.

3. The apparatus of claim 2, wherein the one or more processors are further configured to identify, based on the indication of the precoding information a transmission precoding matrix indicator (TPMI) to be used for transmitting the PUSCH using the three antenna ports.

4. The apparatus of claim 1, wherein the DCI includes an indication of a number of layers that are to be used for transmitting the PUSCH using the three antenna ports.

5. The apparatus of claim 1, wherein the DCI includes an indication of a non-coherent codebook that is to be used for transmitting the PUSCH using the three antenna ports.

6. The apparatus of any of claims 1-5, wherein the DCI is a DCI format 0_1 or a DCI format 0_2.

7. The apparatus of any of claims 1-5, wherein the DCI includes an indication of a sounding reference signal (SRS) set to be used for antenna switching with three antenna ports for a downlink channel state information (CSI) acquisition.

8. One or more computer-readable media comprising instructions that, upon execution of the instructions by one or more processors of an electronic device, are to cause a base station to: generate a downlink control information (DCI) that schedules transmission of a physical uplink shared channel (PUSCH), wherein the DCI includes an indication that the PUSCH is to be transmitted using three antenna ports of a user equipment (UE); andtransmit the DCI to the UE.

9. The one or more computer-readable media of claim 8, wherein the indication that the PUSCH is to be transmitted using three antenna ports includes an indication of precoding information to be used for transmitting the PUSCH using the three antenna ports.

10. The one or more computer-readable media of claim 8, wherein the indication of the precoding information includes a transmission precoding matrix indicator (TPMI) that is to be used for transmitting the PUSCH using the three antenna ports.

11. The one or more computer-readable media of claim 8, wherein the indication that the PUSCH is to be transmitted using three antenna ports includes an indication of a number of layers that are to be used for transmitting the PUSCH using the three antenna ports.

12. The one or more computer-readable media of claim 8, wherein the indication that the PUSCH is to be transmitted using three antenna ports includes an indication of a non-coherent codebook that is to be used for transmitting the PUSCH using the three antenna ports.

13. The one or more computer-readable media of any of claims 8-12, wherein the DCI is a DCI format 0_1 or a DCI format 0_2.

14. The one or more computer-readable media of any of claims 8-12, wherein the DCI includes an indication of a sounding reference signal (SRS) set to be used for antenna switching with three antenna ports for a downlink channel state information (CSI) acquisition.

15. One or more computer-readable media comprising instructions that, upon execution of the instructions by one or more processors of an electronic device, are to cause a user equipment (UE) to: identify a downlink control information (DCI) received from a base station, wherein the DCI schedules transmission of a physical uplink shared channel (PUSCH), and wherein the DCI includes an indication that the PUSCH is to be transmitted using three antenna ports of the UE; and transmit the PUSCH using three antenna ports of the UE.

16. The one or more computer-readable media of claim 15, wherein the indication that the PUSCH is to be transmitted using three antenna ports of the UE includes an indication of precoding information to be used for transmitting the PUSCH using the three antenna ports.

17. The one or more computer-readable media of claim 15, wherein the indication that the PUSCH is to be transmitted using three antenna ports of the UE includes an indication of a number of layers that are to be used for transmitting the PUSCH using the three antenna ports.

18. The one or more computer-readable media of claim 15, wherein the indication that the PUSCH is to be transmitted using three antenna ports of the UE includes an indication of a non-coherent codebook that is to be used for transmitting the PUSCH using the three antenna ports.

19. The one or more computer-readable media of any of claims 15-18, wherein the DCI is a DCI format 0_1 or a DCI format 0_2.

20. The one or more computer-readable media of any of claims 15-18, wherein the DCI includes an indication of a sounding reference signal (SRS) set to be used for antenna switching with three antenna ports for a downlink channel state information (CSI) acquisition.

Images