TRANSMISSION AND/OR RETRANSMISSION SCHEMES FOR DATA IN SYSTEMS

WITH HIGH CARRIER FREQUENCIES

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/160,571, which was filed March 12, 2021; U.S. Provisional Patent Application No. 63/160,577, which was filed March 12, 2021.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to initial transmission and/or retransmission of data in systems that are operating with carrier frequencies above approximately 52.6 gigahertz (GHz).

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 depicts an example signal generation procedure for a two-port uplink control information (UCI) scenario, in accordance with various embodiments.

Figure 2 depicts an example comb-based two port transmission scheme, in accordance with various embodiments.

Figure 3 depicts an example of a mixed initial transmission and retransmission on a physical downlink shared channel (PDSCH) and/or a physical uplink shared channel (PUSCH), in accordance with various embodiments.

Figure 4 depicts an example of use of a dedicated demodulation reference signal (DMRS) related to initial transmission and retransmission on a PDSCH and/or a PUSCH, in accordance with various embodiments.

Figure 5 depicts an example of use of a DMRS related to UCI, initial transmission, and retranmission on a PDSCH and/or a PUSCH, in accordance with various embodiments.

Figure 6 depicts an example of use of a shared DMRS for UCI and initial transmission with a same modulation order, in accordance with various embodiments. Figure 7 depicts an example of use of a shared DMRS for UCI and retransmission with a same modulation order, in accordance with various embodiments.

Figure 8 depicts use of a shared DMRS for use with a UCI, initial transmission, and retransmission on a PUSCH, in accordance with various embodiments.

Figure 9 depicts an example technique related to mixed initial transmission and retransmission of data channels, in accordance with various embodiments.

Figure 10 depicts an alternative example technique related to mixed initial transmission and retransmission of data channels, in accordance with various embodiments.

Figure 11 depicts an example technique related to transmission of uplink control information (UCI), in accordance with various embodiments.

Figure 12 depicts an alternative example technique related to transmission of uplink control information (UCI), in accordance with various embodiments.

Figure 13 schematically illustrates a wireless network in accordance with various embodiments.

Figure 14 schematically illustrates components of a wireless network in accordance with various embodiments.

Figure 15 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.

BACKGROUND

Various embodiments generally may relate to the field of wireless communications.

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 phrases “A or B” and “A/B” mean (A), (B), or (A and B). Mobile communication has evolved significantly from early voice systems to current highly sophisticated integrated communication platform. The next generation wireless communication system, which may be referred to herein as fifth generation (5G) or new radio (NR), will provide access to information and sharing of data anywhere, anytime by various users and applications. NR may be a unified network/system that target to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multi-dimensional requirements may be driven by different services and applications. In general, NR may evolve based on third generation partnership project (3 GPP) long term evolution (LTE)- Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions. NR may enable connections by wireless and deliver fast, rich contents and services. Some embodiments herein may refer to an enhanced transmission scheme for UCI. Some embodiments may additionally or alternatively relate to mixed initial transmission and retransmission of data channels for higher carrier frequencies.

Enhanced transmission scheme for UCI

In NR Release- 15 (Rel-15), short physical uplink control channel (PUCCH) (PUCCH format 0 and 2) transmissions may span 1 or 2 symbols, and long PUCCH (PUCCH format 1, 3 and 4) transmissions may span from 4 to 14 symbols within a slot. Further, long PUCCH transmissions may span multiple slots to further enhance the coverage. In addition, for a given UE, two short PUCCHs transmissions as well as a short PUCCH transmissions and a long PUCCH transmission may be multiplexed in a time division multiplexing (TDM) manner in a same slot. Further, single port transmission may be applied for all different PUCCH formats.

Note that uplink control information (UCI) may be carried by the PUCCH or the PUSCH. In particular, the UCI may include information or indications related to one or more of the following: scheduling request (SR), hybrid automatic repeat request - acknowledgement (HARQ-ACK) feedback, channel state information (CSI) report, e.g., channel quality indicator (CQI), pre-coding matrix indicator (PMI), CSI resource indicator (CRI) and rank indicator (RI) and/or beam related information (e.g., layer 1 - reference signal received power (Ll-RSRP)).

For cellular systems, coverage may be an important factor for successful operation. Compared to LTE, NR may be deployed at higher carrier frequency, e.g., in frequency range 2 (FR2) at the millimeter-wave (mmWave) frequency band. In some embodiments, FR2 may refer to a frequency range between approximately 24.6 GHz and approximately 71 GHz. In this case, coverage loss may occur due to larger path-loss, which may make it more challenging to maintain an adequate quality of service. Typically, uplink coverage is the bottleneck for system operation considering the low transmit power at the user equipment (UE)-side. For systems operating above the approximately 52.6GHz carrier frequency, and/or sixth generation (6G) communication systems, it may be more desirable to improve the coverage for UCI transmission on the PUCCH or the PUSCH, especially in cases where the UE is equipped with multiple transmit antennas. In this case, multiple port transmission may be employed for UCI transmission on PUCCH or PUSCH to exploit the benefit of transmit diversity or spatial diversity. To support multiple port transmission for UCI transmission on PUCCH or PUSCH, certain design changes to legacy 3GPP specifications may be desired. Various embodiments herein include systems and methods of enhanced transmission scheme for UCI on PUSCH.

In one embodiment, when multiple port-based transmission is applied for UCI, separate coding may be applied for UCI on each port. Further, the same coding with same or different scrambling may be used for the UCI transmission on different port. Note that this coding scheme may be applied for UCI transmission on PUCCH or PUSCH.

When different scrambling sequences are applied for the UCI transmission on each port, a fixed offset may be used for the scrambling sequence initialization between two ports for UCI transmission.

In one example, the scrambling sequence generator for UCI transmission on a first port may be initialized with cinit ^{= n} RNTI 2 ¹⁵ + 7l _ID

Where n _RNTI is the Radio Network Temporary Identifier (RNTI) for UCI transmission, which can be a cell-RNTI (C-RNTI) and/or a temporary C-RNTI (TC-RNTI). n _ID may be configured by higher layers via minimum system information (MSI), remaining minimum system information (RMSI) (e.g., system information block 1 (SIB1)), other system information (OSI), and/or radio resource control (RRC) signalling and, if not configured, n _ID may be the physical cell ID. Further, the scrambling sequence generator for UCI transmission on a second port may be initialized with ci _nit = ⁿ RNTI ' 2 ¹⁵ + P _IE) + D

Where D may be predefined in the specification. For example, in some embodiments D may be equal to 1.

In another embodiment, block-wised orthogonal cover code (OCC) may be applied for the modulated symbols prior to discrete fourier transform (DFT) operation for multiple port UCI transmission on PUSCH.

Figure 1 illustrates an example procedure for signal generation for two port UCI transmission scheme. In particular, UCI is coded and modulated in each antenna port (AP), as indicated by the branching pathways from the UCI input. Specifically, one pathway corresponds to AP #0, and another pathway corresponds to AP #1. As mentioned above, the same coding with same or different scrambling can be used for the UCI transmission on each AP. Subsequently, block-wised spreading with OCC is performed on the modulated symbols. After that, spread modulated symbols are input to the DFT block, mapped to the allocated resource in the frequency domain as the input to the inverse fast fourier transform (IFFT) block, and then converted into time domain signal for each AP, AP #0 and AP #1.

In one example, the block-wised spreading operation for the modulated symbols prior to DFT is given by

) i = 0,1. (iV _SF M _symb /M _s c) - l

Where JV _SF is the spreading factor, M _sc is the number of subcarriers for UCI transmission, M _symb is the number of symbols for UCI transmission, and w _nAp is the OCC code for n _AP port, which is given in Table 1, below. For two port transmission, iV _SF = 2.

Table 1. w _n ^ _p for two port UCI transmission

In another embodiment, modulated symbols after DFT operation may be directly mapped to different combs for different ports for UCI transmission. As used herein, a “comb” refers to the use of different subcarriers in the frequency domain for different ports. In one example, even subcarrier may be allocated for a UCI port #1, as indicated by the cross-hatched subcarriers of Figure 2, while odd subcarrier may be allocated for a UCI port #2, as indicated by the diagonally-hatched subcarriers of Figure 2.

In another embodiment, when pre-DFT blocked-wised OCC is applied for UCI transmission on PUSCH, OCC index may be configured by higher layers via MSI, RMSI (SIB1), OSI, and/or RRC signalling, _or dynamically indicated in the DCI, or a combination thereof.

Similarly, when UCI is mapped to different combs for multiple port transmission, comb index may be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling or dynamically indicated in the DCI or a combination thereof.

In another embodiment, when shared DMRS is applied for the transmission of UCI and uplink shared channel (UL-SCH) on PUSCH, comb index or OCC index on each port for UCI transmission on PUSCH can be determined in accordance with the DMRS antenna port (AP) index for PUSCH transmission.

In this case, DMRS AP for PUSCH transmission may be first determined in accordance with the indication in the DCI, and further the comb index or OCC index of UCI on PUSCH for each AP can be determined in accordance with the DMRS AP index.

In one option, when two-port transmission is applied for UCI on PUSCH, comb index of 0 or OCC index of 0 is associated with the smaller indicated DMRS AP, while comb index of 1 or OCC index of 1 is associated with the larger indicated DMRS AP for PUSCH transmission.

Table 2 illustrates one example of comb or OCC index for two port UCI transmission from DMRS AP index for PUSCH. In the example, p ₀ is the first or smaller DMRS AP within two indicated DMRS APs; while _x is the second or larger DMRS AP within the two indicated DMRS APs for PUSCH transmission.

Table 2. Comb or OCC index from DMRS AP index

Initial transmission and retransmission of data channels for higher carrier frequencies

In NR Release 15, system design is targeted for carrier frequencies up to 52.6GHz with a waveform choice of cyclic prefix - orthogonal frequency-division multiplexing (CP-OFDM) for downlink (DL) and uplink (UL), and additionally, Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) for UL. However, for carrier frequencies at or above approximately 52.6GHz, a single carrier based waveform may be used in order to handle issues including low power amplifier (PA) efficiency and large phase noise.

For a single carrier based waveform, DFT-s-OFDM may be considered for both DL and UL. For an OFDM-based transmission scheme including DFT-s-OFDM, a cyclic prefix (CP) may be inserted at the beginning of each block, where the last data symbols in a block are repeated as the CP. Typically, the length of CP may exceed the maximum expected delay spread in order to overcome the inter-symbol interference (ISI).

Further, for systems operating at or above the 52.6GHz carrier frequency, or 6G communication systems, a relatively large number of TBs may be scheduled by a single DCI for PDSCH and PUSCH transmissions. If some of the TBs are not received successfully at the receiver, the transmitter may need to retransmit the failed TBs. Meanwhile, if the transmitter has some new packets that need to be transmitted, the transmitter may combine the initial transmission of some TBs and retransmission of failed TBs in a single PDSCH or PUSCH.

Figure 3 illustrates one example of mixed initial transmission (e.g., the blocks with linear shading) and retransmission (e.g., the blocks with gridded cross-shading) for PDSCH and PUSCH. Note that although in the example, retransmission of TBs is located before initial transmission of TBs, embodiments herein may include the case when initial transmission is located before retransmission of the TBs.

It will be noted that Figure 3, and other Figures herein, are intended as example Figures for the purpose of discussion. Specific shading patterns may be used differently in different Figures, unless explicitly indicated otherwise. In other words, a shading pattern used in one of Figures 3-8 may represent a different concept than the same shading pattern used in another of Figures 3-8.

For the mixed initial transmission and retransmission in a PDSCH or PUSCH, a 5G base station (gNB) may schedule different modulation orders for initial transmission and retransmission of TBs. In this case, it may be difficult for the transmitter to maintain phase continuity between initial transmission and retransmission, especially from the UE perspective. This may also result in different transmit powers between initial transmission and retransmission of TBs. To address this issue, certain mechanisms be desired for the mixed initial transmission and retransmission for PDSCH and PUSCH.

Various embodiments herein provide mechanisms for mixed initial transmission and retransmission of data channel for higher carrier frequency. Specifically, embodiments for mixed initial transmission and retransmission of data channel may include one or more of the following:

In one embodiment, when different modulation orders are used for the initial transmission and retransmission of the TBs on PUSCH and PDSCH, dedicated DMRS(s) may be allocated for the initial transmission and retransmission of the TBs, respectively. In this case, decoding of retransmission of TBs and initial transmission of TBs may be based on DMRS for retransmission and initial transmission of the TBs, respectively. In some embodiments, the modulation orders for initial and retransmission of the TBs may be explicitly indicated in the DCI.

Further, if different transmit powers are used for the transmission of retransmission and initial transmission of TBs, depending on UE capability, a time gap may be inserted between transmission of retransmission and initial transmission of TBs on PUSCH. Note that the time gap may be defined on the basis of symbol or symbol group. In particular, a number of symbols for a time gap within the PDSCH or PUSCH transmission may be configured by higher layers via MSI, MSI, OSI, and/or dedicated RRC signalling, or dynamically indicated in the DCI or a combination thereof. The number of symbols for the time gap may be reported by UE as UE capability. Figure 4 illustrates one example of dedicated DMRS for initial transmission (e.g., the diagonally shaded block) and retransmission (e.g., the vertically shaded block) on PUSCH and PDSCH. In the example, DMRS for retransmission is transmitted before retransmission of TB(s) on PUSCH (e.g., the horizontally shaded blocks) and DMRS for initial transmission is transmitted before initial transmission (e.g., the grid-shaded blocks) of TB(s) on PDSCH or PUSCH. Note that, depending on the duration of initial and retransmission of the TBs, additional DMRS symbol(s) may be inserted within the retransmission and initial transmission of the TBs on PDSCH or PUSCH. Further, a 1-symbol gap may be inserted between initial and retransmission of the TBs, which is reserved for power transition.

In another embodiment, when UCI is multiplexed on PUSCH, and if different modulation orders are used for the transmission of UCI, retransmission and initial transmission of TBs, dedicated DMRS(s) are allocated for the UCI, initial transmission and retransmission of the TBs, respectively. Further, depending on UE capability, if different transmit powers are used for the transmission of UCI, retransmission and initial transmission of TBs, a time gap may be inserted between transmission of UCI, retransmission and initial transmission of TBs on PUSCH. Note that the modulation order for UCI may be predefined in the specification or equal to the modulation order for the initial or retransmission of the TBs on PUSCH, which may be explicitly indicated in the DCI as mentioned above.

Note that UCI may include one or more of the following: scheduling request (SR), hybrid automatic repeat request - acknowledgement (HARQ-ACK) feedback, channel state information (CSI) report, e.g., channel quality indicator (CQI), pre-coding matrix indicator (PMI), CSI resource indicator (CRT) and rank indicator (RI) and/or beam related information (e.g., Ll-RSRP (layer 1- reference signal received power)).

Figure 5 illustrates one example of dedicated DMRS for UCI (e.g., as indicated by the diagonally-shaded block that rises from left-to-right), DMRS for initial transmission (as indicated by the vertically-shaded block), and DMRS for retransmission (as indicated by the diagonally- shaded block that falls from left-to-right) on PUSCH. In the example, DMRS for UCI is transmitted before the UCI (indicated by the cross-hatched blocks) on PUSCH, DMRS for retransmission is transmitted before retransmission (as indicated by the horizontally-shaded blocks) of TB(s) on PUSCH, and DMRS for initial transmission is transmitted before initial transmission (indicated by the grid-shaded blocks) of TB(s) on PUSCH. Further, a 1 symbol gap is inserted between UCI, initial and retransmission of the TBs, which is reserved for power transition.

In another embodiment, a same modulation order may be used for the transmission of UCI and initial transmission or retransmission of TBs on PUSCH. When the same modulation order is employed for the transmission of UCI and initial transmission of TBs on PUSCH or the transmission of the UCI and retransmission, a shared DMRS may be used for the transmission of UCI and initial transmission or the transmission of UCI and retransmission, respectively.

Further, when same modulation order is used for the transmission of UCI and initial transmission on PUSCH, UCI may be mapped before the initial transmission and shared DMRS may be allocated before the UCI. A time gap may be inserted between retransmission and UCI on PUSCH for power transition as mentioned above.

Figure 6 illustrates one example of a shared DMRS for UCI and initial transmission (as indicated by the diagonally-shaded block that falls from left-to right) with same modulation order. In the example, different modulation orders are used for retransmission and UCI/initial transmission on PUSCH. In this case, DMRS for retransmission (as indicated by the block with vertical shading) is transmitted before retransmission (as indicated by the blocks with horizontal shading) of TB(s) on PUSCH and shared DMRS for UCI and initial transmission is transmitted before the UCI (as indicated by the blocks with cross-hatch shading) on PUSCH. Further, a 1 symbol gap is inserted between retransmission and UCI, which is reserved for power transition.

Similarly, if same modulation order is used for the transmission of UCI and retransmission on PUSCH, UCI may be mapped before the retransmission and shared DMRS is allocated before the UCI. A time gap may be inserted between retransmission and initial on PUSCH for power transition as mentioned above.

Figure 7 illustrates one example of use of a shared DMRS for UCI and retransmission (as indicated by the block with the diagonal shading that rises from left to right) with same modulation order. In the example, different modulation orders are used for initial transmission (indicated by the blocks with gridded shading) and UCI/retransmission (as indicated by the blocks with cross- hatch shading and the blocks with horizontal shading, respectively) on PUSCH. In this case, DMRS for initial transmission (as indicated by the block with diagonal shading that falls from left-to-right) is transmitted before initial transmission of TB(s) on PUSCH and shared DMRS for UCI and retransmission is transmitted before the UCI on PUSCH. Further, a 1 symbol gap is inserted between retransmission and initial transmission, which is reserved for power transition.

In another embodiment, the same modulation order may always applied for the initial transmission, retransmission and/or UCI. In this case, indication of modulation order or modulation and coding scheme (MCS) for the retransmission of the TBs on PDSCH or PUSCH is not included in the DCI. In addition, modulation order offset or MCS offset between first transmission and retransmission may not be included in the DCI.

When same modulation orders are used for the transmission of UCI, initial and retransmission of TB(s) on PUSCH, shared DMRS may be used for UCI, initial and retransmission of the TBs on PUSCH, which can be transmitted before the UCI. In this case, time gap may not be needed during PUSCH transmission.

Figure 8 illustrates one example of shared DMRS (as indicated by the blocks with diagonal shading) for UCI, initial transmission and retransmission on PUSCH. In the example, UCI (indicated by the blocks with cross-hatch shading) is transmitted before retransmission (indicated by the blocks with horizontal shading) of the TBs and followed by initial transmission (as indicated by the blocks with gridded shading) of the TBs on PUSCH. As mentioned above, depending on the length of PUSCH transmission, additional DMRS symbol(s) may be inserted.

Note that other permutations of the mapping order of UCI, retransmission and initial transmission may be additionally or alternatively derived in other embodiments herein.

In another embodiment, when different transmit power is applied for the transmission of initial transmission, retransmission and/or UCI, a shared DMRS may be used. In this case, transmit power difference or transmit power ratio between initial transmission, retransmission and/or UCI may be configured by higher layers via MSI, RMSI (e.g., SIBl), OSI or RRC signalling or dynamically indicated in the DCI or a combination thereof. In this case, the receiver can derive the power difference between the DMRS symbols and initial transmission, retransmission and/or UCI.

In another embodiment, different frequency domain resource allocation (FDRA) can be allocated for the initial and retransmission of TB(s) on PDSCH or PUSCH. In this case, two FDRA fields can be inserted in the DCI to indicate the frequency domain resource for the initial and retransmission of TB(s) on PDSCH or PUSCH, respectively. Alternatively, same starting PRBs but different length of PRBs or PRB size difference can be used for the transmission of the initial and retransmission of TB(s) on PDSCH or PUSCH.

Further, when UCI is multiplexed on PUSCH, same frequency domain resource can be allocated for the UCI and initial transmission of the TB(s), or the UCI and retransmission of the TB(s) on PUSCH.

In another embodiment, separate transmit power command (TPC) fields can be included in the DCI, which is used for the transmission of the initial and retransmission of TB(s) on PUSCH, respectively. Further, when UCI is multiplexed on PUSCH, same TPC command can be used for the UCI and initial transmission of the TB(s), or the UCI and retransmission of the TB(s) on PUSCH.

As a further extension, independent transmit power processes can be applied for the transmission of initial and retransmission of TB(s) on PUSCH.

EXAMPLE TECHNIQUES Figures 9-12 depicts various example techniques related to embodiments herein. It will be understood that such techniques are intended as examples of certain embodiments of the present disclosure, and other embodiments may include more or fewer elements, elements performed in a different order, different elements, etc.

Figure 9 depicts an example technique related to mixed initial transmission and retransmission of data channels, in accordance with various embodiments. Such a technique may be performed by an electronic device that is, is part of, or includes a user equipment (UE) in a cellular network such as a fifth generation (5G) or higher cellular network. The technique may include identifying, at 905, a received indication of a first modulation order for an initial transmission of a transport block (TB), and a received indication of a second modulation order for a retransmission of a transport block (TB) on a physical uplink shared channel (PUSCH), wherein the first and second modulation orders are different; and encoding, at 910 for transmission based on the indications of the first and second modulation orders, a first demodulation reference signal (DMRS) for the initial transmission of the TB and a second DMRS for the retransmission of the TB on the PUSCH, wherein the first and second DMRS are different.

Figure 10 depicts an alternative example technique related to mixed initial transmission and retransmission of data channels, in accordance with various embodiments. Such a technique may be performed by an electronic device that is, is part of, or includes a base station in a cellular network such as a fifth generation (5G) or higher cellular network. The technique may include encoding, at 1005 for transmission to a user equipment (UE), an indication of a first modulation order for an initial transmission of a transport block (TB) and an indication of a second modulation order for a retransmission of a TB on a physical uplink shared channel (PUSCH), wherein the first and second modulation orders are different; and encoding, at 1010 for transmission based on the first modulation order and the second modulation order, a first demodulation reference signal (DMRS) for the initial transmission of the TB and a second DMRS for the retransmission of the TB on the PUSCH, wherein the first and second DMRS are different.

Figure 11 depicts an example technique related to transmission of uplink control information (UCI), in accordance with various embodiments. Such a technique may be performed by an electronic device that is, is part of, or includes a user equipment (UE) in a cellular network such as a fifth generation (5G) or higher cellular network. The technique may include identifying, at 1105, uplink control information (UCI); encoding, at 1110, the UCI for transmission on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) using a multiple-port transmission scheme; and transmitting, at 1115, the UCI on the PUCCH or the PUSCH on a plurality of ports using the multiple-port transmission scheme.

Figure 12 depicts an alternative example technique related to transmission of uplink control information (UCI), in accordance with various embodiments. Such a technique may be performed by an electronic device that is, is part of, or includes a base station in a cellular network such as a fifth generation (5G) or higher cellular network. The technique may include identifying, at 1205, uplink control information (UCI) received from a user equipment (UE) on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); and processing, at 1210, the UCI. In embodiments, the UCI may have been transmitted by the UE on a the PUCCH or the PUSCH on a plurality of ports using the multiple-port transmission scheme.

SYSTEMS AND IMPLEMENTATIONS

Figures 13-15 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 13 illustrates a network 1300 in accordance with various embodiments. The network 1300 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 1300 may include a UE 1302, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1304 via an over-the-air connection. The UE 1302 may be communicatively coupled with the RAN 1304 by a Uu interface. The UE 1302 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 1300 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 1302 may additionally communicate with an AP 1306 via an over-the-air connection. The AP 1306 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1304. The connection between the UE 1302 and the AP 1306 may be consistent with any IEEE 802.11 protocol, wherein the AP 1306 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 1302, RAN 1304, and AP 1306 may utilize cellular- WLAN aggregation (for example, LWAEWIP). Cellular- WLAN aggregation may involve the UE 1302 being configured by the RAN 1304 to utilize both cellular radio resources and WLAN resources.

The RAN 1304 may include one or more access nodes, for example, AN 1308. AN 1308 may terminate air-interface protocols for the UE 1302 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1308 may enable data/voice connectivity between CN 1320 and the UE 1302. In some embodiments, the AN 1308 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 1308 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1308 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 1304 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 1304 is an LTE RAN) or an Xn interface (if the RAN 1304 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 1304 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1302 with an air interface for network access. The UE 1302 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1304. For example, the UE 1302 and RAN 1304 may use carrier aggregation to allow the UE 1302 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 1304 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 1302 or AN 1308 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 1304 may be an LTE RAN 1310 with eNBs, for example, eNB 1312. The LTE RAN 1310 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 1304 may be an NG-RAN 1314 with gNBs, for example, gNB 1316, or ng-eNBs, for example, ng-eNB 1318. The gNB 1316 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1316 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1318 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 1316 and the ng-eNB 1318 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 1314 and a UPF 1348 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1314 and an AMF 1344 (e.g., N2 interface). The NG-RAN 1314 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 1302 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1302, 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 1302 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 1302 and in some cases at the gNB 1316. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 1304 is communicatively coupled to CN 1320 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1302). The components of the CN 1320 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 1320 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 1320 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1320 may be referred to as a network sub-slice.

In some embodiments, the CN 1320 may be an LTE CN 1322, which may also be referred to as an EPC. The LTE CN 1322 may include MME 1324, SGW 1326, SGSN 1328, HSS 1330, PGW 1332, and PCRF 1334 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1322 may be briefly introduced as follows.

The MME 1324 may implement mobility management functions to track a current location of the UE 1302 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc. The SGW 1326 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1322. The SGW 1326 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 1328 may track a location of the UE 1302 and perform security functions and access control. In addition, the SGSN 1328 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1324; MME selection for handovers; etc. The S3 reference point between the MME 1324 and the SGSN 1328 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 1330 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 1330 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1330 and the MME 1324 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 1320.

The PGW 1332 may terminate an SGi interface toward a data network (DN) 1336 that may include an application/content server 1338. The PGW 1332 may route data packets between the LTE CN 1322 and the data network 1336. The PGW 1332 may be coupled with the SGW 1326 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1332 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 1332 and the data network 13 36 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 1332 may be coupled with a PCRF 1334 via a Gx reference point.

The PCRF 1334 is the policy and charging control element of the LTE CN 1322. The PCRF 1334 may be communicatively coupled to the app/content server 1338 to determine appropriate QoS and charging parameters for service flows. The PCRF 1332 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 1320 may be a 5GC 1340. The 5GC 1340 may include an AUSF 1342, AMF 1344, SMF 1346, UPF 1348, NSSF 1350, NEF 1352, NRF 1354, PCF 1356, UDM 1358, and AF 1360 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 1340 may be briefly introduced as follows.

The AUSF 1342 may store data for authentication of UE 1302 and handle authentication- related functionality. The AUSF 1342 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 1340 over reference points as shown, the AUSF 1342 may exhibit an Nausf service-based interface.

The AMF 1344 may allow other functions of the 5GC 1340 to communicate with the UE 1302 and the RAN 1304 and to subscribe to notifications about mobility events with respect to the UE 1302. The AMF 1344 may be responsible for registration management (for example, for registering UE 1302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 1344 may provide transport for SM messages between the UE 1302 and the SMF 1346, and act as a transparent proxy for routing SM messages. AMF 1344 may also provide transport for SMS messages between UE 1302 and an SMSF. AMF 1344 may interact with the AUSF 1342 and the UE 1302 to perform various security anchor and context management functions. Furthermore, AMF 1344 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1304 and the AMF 1344; and the AMF 1344 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 1344 may also support NAS signaling with the UE 1302 over an N3 IWF interface.

The SMF 1346 may be responsible for SM (for example, session establishment, tunnel management between UPF 1348 and AN 1308); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1348 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 1344 over N2 to AN 1308; 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 1302 and the data network 1336.

The UPF 1348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1336, and a branching point to support multi -homed PDU session. The UPF 1348 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 1348 may include an uplink classifier to support routing traffic flows to a data network. The NSSF 1350 may select a set of network slice instances serving the UE 1302. The NSSF 1350 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 1350 may also determine the AMF set to be used to serve the UE 1302, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1354. The selection of a set of network slice instances for the UE 1302 may be triggered by the AMF 1344 with which the UE 1302 is registered by interacting with the NSSF 1350, which may lead to a change of AMF. The NSSF 1350 may interact with the AMF 1344 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 1350 may exhibit an Nnssf service-based interface.

The NEF 1352 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 1360), edge computing or fog computing systems, etc. In such embodiments, the NEF 1352 may authenticate, authorize, or throttle the AFs. NEF 1352 may also translate information exchanged with the AF 1360 and information exchanged with internal network functions. For example, the NEF 1352 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 1352 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1352 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1352 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 1352 may exhibit an Nnef service-based interface.

The NRF 1354 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 1354 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 1354 may exhibit the Nnrf service-based interface.

The PCF 1356 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 1356 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1358. In addition to communicating with functions over reference points as shown, the PCF 1356 exhibit an Npcf service-based interface.

The UDM 1358 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1302. For example, subscription data may be communicated via an N8 reference point between the UDM 1358 and the AMF 1344. The UDM 1358 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1358 and the PCF 1356, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1302) for the NEF 1352. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1358, PCF 1356, and NEF 1352 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 1358 may exhibit the Nudm service- based interface.

The AF 1360 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 1340 may enable edge computing by selecting operator/3 ^rd party services to be geographically close to a point that the UE 1302 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 1340 may select a UPF 1348 close to the UE 1302 and execute traffic steering from the UPF 1348 to data network 1336 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1360. In this way, the AF 1360 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1360 is considered to be a trusted entity, the network operator may permit AF 1360 to interact directly with relevant NFs. Additionally, the AF 1360 may exhibit an Naf service-based interface.

The data network 1336 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 1338.

Figure 14 schematically illustrates a wireless network 1400 in accordance with various embodiments. The wireless network 1400 may include a UE 1402 in wireless communication with an AN 1404. The UE 1402 and AN 1404 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein. The UE 1402 may be communicatively coupled with the AN 1404 via connection 1406. The connection 1406 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 1402 may include a host platform 1408 coupled with a modem platform 1410. The host platform 1408 may include application processing circuitry 1412, which may be coupled with protocol processing circuitry 1414 of the modem platform 1410. The application processing circuitry 1412 may run various applications for the UE 1402 that source/sink application data. The application processing circuitry 1412 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 1414 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1406. The layer operations implemented by the protocol processing circuitry 1414 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 1410 may further include digital baseband circuitry 1416 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1414 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 1410 may further include transmit circuitry 1418, receive circuitry 1420, RF circuitry 1422, and RF front end (RFFE) 1424, which may include or connect to one or more antenna panels 1426. Briefly, the transmit circuitry 1418 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1420 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1422 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1424 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 1418, receive circuitry 1420, RF circuitry 1422, RFFE 1424, and antenna panels 1426 (referred genetically 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 1414 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 1426, RFFE 1424, RF circuitry 1422, receive circuitry 1420, digital baseband circuitry 1416, and protocol processing circuitry 1414. In some embodiments, the antenna panels 1426 may receive a transmission from the AN 1404 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1426.

A UE transmission may be established by and via the protocol processing circuitry 1414, digital baseband circuitry 1416, transmit circuitry 1418, RF circuitry 1422, RFFE 1424, and antenna panels 1426. In some embodiments, the transmit components of the UE 1404 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 1426.

Similar to the UE 1402, the AN 1404 may include a host platform 1428 coupled with a modem platform 1430. The host platform 1428 may include application processing circuitry 1432 coupled with protocol processing circuitry 1434 of the modem platform 1430. The modem platform may further include digital baseband circuitry 1436, transmit circuitry 1438, receive circuitry 1440, RF circuitry 1442, RFFE circuitry 1444, and antenna panels 1446. The components of the AN 1404 may be similar to and substantially interchangeable with like- named components of the UE 1402. In addition to performing data transmission/reception as described above, the components of the AN 1408 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 15 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 15 shows a diagrammatic representation of hardware resources 1500 including one or more processors (or processor cores) 1510, one or more memory/storage devices 1520, and one or more communication resources 1530, each of which may be communicatively coupled via a bus 1540 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1500.

The processors 1510 may include, for example, a processor 1512 and a processor 1514. The processors 1510 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 1520 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1520 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 1530 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1504 or one or more databases 1506 or other network elements via a network 1508. For example, the communication resources 1530 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 1550 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1510 to perform any one or more of the methodologies discussed herein. The instructions 1550 may reside, completely or partially, within at least one of the processors 1510 (e.g., within the processor’s cache memory), the memory/storage devices 1520, or any suitable combination thereof. Furthermore, any portion of the instructions 1550 may be transferred to the hardware resources 1500 from any combination of the peripheral devices 1504 or the databases 1506. Accordingly, the memory of processors 1510, the memory/storage devices 1520, the peripheral devices 1504, and the databases 1506 are examples of computer-readable and machine-readable media.

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 A.l may include a method comprising: transmitting, by a UE, uplink control information (UCI) on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) using a multiple port based transmission scheme.

Example A.2 may include the method of Example A.l, wherein when multiple port based transmission is applied for UCI, separate coding is applied for UCI on each port, wherein same coding with same or different scrambling can be used for the UCI transmission on different port.

Example A.3 may include the method of Example A.l and/or some other example herein, wherein when different scrambling sequences are applied for the UCI transmission on each port, a fixed offset can be used for the scrambling sequence initialization between two ports for UCI transmission.

Example A.4 may include the method of Example A.l and/or some other example herein, wherein block-wised orthogonal cover code (OCC) can be applied for the modulated symbols prior to DFT operation for multiple port UCI transmission on PUSCH.

Example A.5 may include the method of Example A.l and/or some other example herein, wherein modulated symbols after DFT operation are directly mapped to different combs for different ports for UCI transmission.

Example A.6 may include the method of Example A.l and/or some other example herein, wherein when pre-DFT blocked-wised OCC is applied for UCI transmission on PUSCH, OCC index may be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling or dynamically indicated in the DCI or a combination thereof.

Example A.7 may include the method of Example A.l and/or some other example herein, wherein when UCI is mapped to different combs for multiple port transmission, comb index may be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling or dynamically indicated in the DCI or a combination thereof.

Example A.8 may include the method of Example A.l and/or some other example herein, wherein when shared DMRS is applied for the transmission of UCI and uplink shared channel (UL-SCH) on PUSCH, comb index or OCC index on each port for UCI transmission on PUSCH can be determined in accordance with the DMRS antenna port (AP) index for PUSCH transmission.

Example A.9 may include the method of Example A.l and/or some other example herein, wherein DMRS AP for PUSCH transmission can be first determined in accordance with the indication in the DCI; wherein the comb index or OCC index of UCI on PUSCH for each AP can be determined in accordance with the DMRS AP index.

Example A.10 may include the method of Example A.l and/or some other example herein, wherein when two port transmission is applied for UCI on PUSCH, comb index of 0 or OCC index of 0 is associated with the smaller indicated DMRS AP, while comb index of 1 or OCC index of 1 is associated with the larger indicated DMRS AP for PUSCH transmission.

Example A.l 1 may include a method of a user equipment (UE), the method comprising: determining uplink control information (UCI); and encoding the UCI for transmission on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) using a multiple port transmission scheme.

Example A.12 may include the method of Example A.l 1, wherein the multiple port transmission scheme includes applying separate coding for the UCI on each port of a plurality of ports.

Example A.13 may include the method of Example A.11 and/or some other example herein, wherein the same coding with the same or different scrambling sequence is used for the transmission of the UCI on the different ports.

Example A.14 may include the method of Example A.l 1-13 and/or some other example herein, wherein different scrambling sequences are applied for the transmission of the UCI on respective ports.

Example A.15 may include the method of Example A.14 and/or some other example herein, wherein a fixed offset is used for the scrambling sequence initialization between two ports for the transmission of the UCI.

Example B.l may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method comprising: receiving, by a UE from a gNodeB, an indication of a different modulation order for an initial transmission of a transport block (TB) and retransmission of a TB on a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH); and transmitting, by the UE, a dedicated demodulation reference signal (DMRS) for the initial transmission of the TB and the retransmission of the TB, respectively, on the PUSCH; or receiving, by the UE, a dedicated DMRS for the initial transmission of the TB and the retransmission of the TB, respectively, on the PDSCH. Example B.2 may include the method of Example B.l and/or some other example herein, wherein if different transmit powers are used for the transmission of retransmission and initial transmission of TBs, depending on UE capability, time gap may need to be inserted between transmission of retransmission and initial transmission of TBs on PUSCH.

Example B.3 may include the method of Example B.l and/or some other example herein, wherein a number of symbols for time gap within the PDSCH or PUSCH transmission may be configured by higher layers via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (RRC) signalling or dynamically indicated in the DCI or a combination thereof.

Example B.4 may include the method of Example B.l and/or some other example herein, wherein when uplink control information (UCI) is multiplexed on PUSCH, and if different modulation orders are used for the transmission of UCI, retransmission and initial transmission of TBs, dedicated DMRS(s) are allocated for the UCI, initial transmission and retransmission of the TBs, respectively.

Example B.5 may include the method of Example B.l and/or some other example herein, wherein if different transmit powers are used for the transmission of UCI, retransmission and initial transmission of TBs, time gap may need to be inserted between transmission of UCI, retransmission and initial transmission of TBs on PUSCH.

Example B.6 may include the method of Example B.l and/or some other example herein, wherein same modulation order can be used for the transmission of UCI and initial transmission or retransmission of TBs on PUSCH.

Example B.7 may include the method of Example B.l and/or some other example herein, wherein When same modulation order is employed for the transmission of UCI and initial transmission of TBs on PUSCH or the transmission of the UCI and retransmission, shared DMRS may be used for the transmission of UCI and initial transmission or the transmission of UCI and retransmission, respectively.

Example B.8 may include the method of Example B.l and/or some other example herein, wherein when same modulation order is used for the transmission of UCI and initial transmission on PUSCH, UCI can be mapped before the initial transmission and shared DMRS is allocated before the UCI.

Example B.9 may include the method of Example B.l and/or some other example herein, wherein if same modulation order is used for the transmission of UCI and retransmission on PUSCH, UCI can be mapped before the retransmission and shared DMRS is allocated before the UCI. Example B.10 may include the method of Example B.l and/or some other example herein, wherein when same modulation orders are used for the transmission of UCI, initial and retransmission of TB(s) on PUSCH, shared DMRS may be used for UCI, initial and retransmission of the TBs on PUSCH, which can be transmitted before the UCI.

Example B.l 1 may include the method of Example B.l and/or some other example herein, wherein transmit power difference or transmit power ratio between initial transmission, retransmission and/or UCI may be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling or dynamically indicated in the DCI or a combination thereof.

Example B.12 may include the method of Example B.l and/or some other example herein, wherein different frequency domain resource allocation (FDRA) can be allocated for the initial and retransmission of TB(s) on PDSCH or PUSCH.

Example B.13 may include the method of Example B.l and/or some other example herein, wherein separate transmit power command (TPC) fields can be included in the DCI, which is used for the transmission of the initial and retransmission of TB(s) on PUSCH, respectively.

Example B.14 may include a method of a user equipment (UE), the method comprising: receiving an indication of a first modulation order for an initial transmission of a transport block (TB) and a second modulation order for a retransmission of a transport block (TB) on a physical uplink shared channel (PUSCH), wherein the first and second modulation orders are different; and encoding, for transmission, a first demodulation reference signal (DMRS) for the initial transmission of the TB and a second DMRS for the retransmission of the TB on the PUSCH, wherein the first and second DMRS are different.

Example B.15 may include the method of Example B.14 and/or some other example herein, wherein different transmit powers are used for the initial transmission and the retransmission, and wherein the method further includes inserting a time gap between the initial transmission and the retransmission.

Example B.16 may include the method of Example B.15 and/or some other example herein, further comprising receiving a configuration of the time gap from a gNB.

Example B.17 may include the method of Example B.16 and/or some other example herein, wherein the configuration is received via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (RRC) signalling or dynamically indicated in the DCI or a combination thereof. Example B.18 may include the method of Example B.14-17 and/or some other example herein, wherein the indication of the first and/or second modulation orders is included in a DCI that schedules the initial transmission and/or the retransmission.

Example B.19 may include a method of a gNB, the method comprising: encoding, for transmission to a UE, an indication of a first modulation order for an initial transmission of a transport block (TB) and a second modulation order for a retransmission of a transport block (TB) on a physical downlink shared channel (PDSCH), wherein the first and second modulation orders are different; and encoding, for transmission, a first demodulation reference signal (DMRS) for the initial transmission of the TB and a second DMRS for the retransmission of the TB on the PUSCH, wherein the first and second DMRS are different.

Example B.20 may include the method of Example B.19 and/or some other example herein, wherein different transmit powers are used for the initial transmission and the retransmission, and wherein the method further includes inserting a time gap between the initial transmission and the retransmission.

Example B.21 may include the method of Example B.20 and/or some other example herein, further comprising encoding, for transmission to the UE, a configuration of the time gap from a gNB.

Example B.22 may include the method of Example B.21 and/or some other example herein, wherein the configuration is transmitted via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (RRC) signalling or dynamically indicated in the DCI or a combination thereof.

Example B.23 may include the method of Example B.19-22 and/or some other example herein, wherein the indication of the first and/or second modulation orders is included in a DCI that schedules the initial transmission and/or the retransmission.

Example C.l includes a method to be performed by an electronic device, wherein the electronic device is a part of a user equipment (UE) in a cellular network, the method comprising: identifying a received indication of a first modulation order for an initial transmission of a transport block (TB), and a received indication of a second modulation order for a retransmission of a transport block (TB) on a physical uplink shared channel (PUSCH), wherein the first and second modulation orders are different; and encoding, for transmission based on the indications of the first and second modulation orders, a first demodulation reference signal (DMRS) for the initial transmission of the TB and a second DMRS for the retransmission of the TB on the PUSCH, wherein the first and second DMRS are different. Example C.2 includes the method of example C.l, and/or some other example herein, wherein different transmit powers are used for the initial transmission and the retransmission, and wherein the method further includes inserting a time gap between the initial transmission and the retransmission.

Example C.3 includes the method of example C.2, and/or some other example herein, further comprising identifying an indication of a configuration of the time gap received from a fifth generation (5G) or higher base station.

Example C.4 includes the method of example C.3, and/or some other example herein, wherein the indication of the configuration is received via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI), dedicated radio resource control (RRC) signalling, or dynamically indicated in the DCI.

Example C.5 includes the method of any of example C.1-C.4, and/or some other example herein, wherein the indication of the first modulation order or the indication of the second modulation order is included in a DCI that schedules the initial transmission and/or the retransmission.

Example C.6. A method to be performed by an electronic device, wherein the electronic device is part of a fifth generation (5G) or higher base station in a cellular network, the method comprising: encoding, for transmission to a user equipment (UE), an indication of a first modulation order for an initial transmission of a transport block (TB) and an indication of a second modulation order for a retransmission of a TB on a physical uplink shared channel (PUSCH), wherein the first and second modulation orders are different; and encoding, for transmission based on the first modulation order and the second modulation order, a first demodulation reference signal (DMRS) for the initial transmission of the TB and a second DMRS for the retransmission of the TB on the PUSCH, wherein the first and second DMRS are different.

Example C.l includes the method of example C.6, and/or some other example herein, wherein different transmit powers are used for the initial transmission and the retransmission, and wherein the method further includes inserting a time gap between the initial transmission and the retransmission.

Example C.8 includes the method of example C.7, and/or some other example herein, further comprising encoding, for transmission to the UE, an indication of a configuration of the time gap.

Example C.9 includes the method of example C.8, and/or some other example herein, wherein the indication of the configuration is transmitted via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI), dedicated radio resource control (RRC) signalling, or dynamically indicated in the DCI.

Example C.10 includes the method of any of example C.6-C.9, and/or some other example herein, wherein the indication of the first modulation order or the indication of the second modulation order is included in a DCI that schedules the initial transmission and/or the retransmission.

Example C.l 1. A method to be performed by an electronic device, wherein the electronic device is part of a user equipment (UE) in a cellular network, the method comprising: identifying uplink control information (UCI); encoding the UCI for transmission on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) using a multiple- port transmission scheme; and transmitting the UCI on the PUCCH or the PUSCH on a plurality of ports using the multiple-port transmission scheme.

Example C.12 includes the method of example C.11, and/or some other example herein, wherein the multiple port transmission scheme is based on application of separate coding for the UCI on respective ports of the plurality of ports.

Example C.13 includes the method of example C.ll, and/or some other example herein, wherein a same coding is used for the transmission of the UCI on the plurality of ports.

Example C.14 includes the method of any of example C.11-C.13, and/or some other example herein, wherein different scrambling sequences are applied for the transmission of the UCI on respective ports of the plurality of ports.

Example C.l 5 includes the method of example C.14, and/or some other example herein, wherein a fixed offset is used for the scrambling sequence initialization between two ports of the plurality of ports for the transmission of the UCI.

Example C.16. A method to be performed by an electronic device, wherein the electronic device is part of a base station in a fifth generation (5G) or higher cellular network, the method comprising: identifying uplink control information (UCI) received from a user equipment (UE) on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); and processing the UCI; wherein the UCI was transmitted by the UE on a the PUCCH or the PUSCH on a plurality of ports using the multiple-port transmission scheme.

Example C.17 includes the method of example C.16, and/or some other example herein, wherein the multiple port transmission scheme is based on application, by the UE, of separate coding for the UCI on respective ports of the plurality of ports.

Example C.18 includes the method of example C.16, and/or some other example herein, wherein a same coding is used for the transmission of the UCI on the plurality of ports. Example C.19 includes the method of any of example C.16-C.18, and/or some other example herein, wherein different scrambling sequences are applied for the transmission of the UCI on respective ports of the plurality of ports.

Example C.20 includes the method of example C.19, and/or some other example herein, wherein a fixed offset is used for the scrambling sequence initialization between two ports of the plurality of ports for the transmission of the UCI.

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 A.1 -C.20, 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 A.1-C.20, 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 A.1-C.20, 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 A.1-C.20, 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 A.1-C.20, or portions thereof.

Example Z06 may include a signal as described in or related to any of examples A.l- C.20, 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 A.1-C.20, 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 A.1-C.20, 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 A.1 -C.20, 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 A.1-C.20, 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 A.1-C.20, 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.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.

3 GPP Third AP Application BRAS Broadband Generation 35 Protocol, Antenna Remote Access

Partnership Port, Access Point 70 Server

Project API Application BSS Business 4G Fourth Programming Interface Support System Generation APN Access Point BS Base Station 5G Fifth 40 Name BSR Buffer Status Generation ARP Allocation and 75 Report 5GC 5G Core Retention Priority BW Bandwidth network ARQ Automatic BWP Bandwidth Part AC Repeat Request C-RNTI Cell

Application 45 AS Access Stratum Radio Network

Client ASP 80 Temporary

ACK Application Service Identity

Acknowledgem Provider CA Carrier ent Aggregation,

ACID 50 ASN.l Abstract Syntax Certification

Application Notation One 85 Authority Client Identification AUSF Authentication CAPEX CAPital AF Application Server Function Expenditure Function AWGN Additive CBRA Contention

AM Acknowledged 55 White Gaussian Based Random Mode Noise 90 Access

AMBRAggregate BAP Backhaul CC Component Maximum Bit Rate Adaptation Protocol Carrier, Country AMF Access and BCH Broadcast Code, Cryptographic Mobility 60 Channel Checksum

Management BER Bit Error Ratio 95 CCA Clear Channel Function BFD Beam Assessment AN Access Failure Detection CCE Control Network BLER Block Error Channel Element

ANR Automatic 65 Rate CCCH Common Neighbour Relation BPSK Binary Phase 100 Control Channel Shift Keying CE Coverage Enhancement CDM Content COTS Commercial C-RNTI Cell Delivery Network Off-The-Shelf RNTI CDMA Code- CP Control Plane, CS Circuit Division Multiple Cyclic Prefix, Switched Access 40 Connection 75 CSCF call

CFRA Contention Free Point session control function Random Access CPD Connection CSAR Cloud Service CG Cell Group Point Descriptor Archive CGF Charging CPE Customer CSI Channel-State

Gateway Function 45 Premise 80 Information CHF Charging Equipment CSI-IM CSI

Function CPICHCommon Pilot Interference

Cl Cell Identity Channel Measurement CID Cell-ID (e g., CQI Channel CSI-RS CSI positioning method) 50 Quality Indicator 85 Reference Signal CIM Common CPU CSI processing CSI-RSRP CSI Information Model unit, Central reference signal CIR Carrier to Processing Unit received power Interference Ratio C/R CSI-RSRQ CSI CK Cipher Key 55 Command/Resp 90 reference signal CM Connection onse field bit received quality Management, CRAN Cloud Radio CSI-SINR CSI

Conditional Access signal-to-noise and Mandatory Network, Cloud interference CMAS Commercial 60 RAN 95 ratio Mobile Alert Service CRB Common CSMA Carrier Sense CMD Command Resource Block Multiple Access CMS Cloud CRC Cyclic CSMA/CA CSMA Management System Redundancy Check with collision CO Conditional 65 CRI Channel -State 100 avoidance Optional Information CSS Common

CoMP Coordinated Resource Search Space, Cell- Multi-Point Indicator, CSI-RS specific Search CORESET Control Resource Space Resource Set 70 Indicator CTF Charging DRX Discontinuous ECSP Edge

Trigger Function Reception Computing Service CTS Clear-to-Send DSL Domain Provider CW Codeword Specific Language. EDN Edge CWS Contention 40 Digital 75 Data Network Window Size Subscriber Line EEC Edge D2D Device-to- DSLAM DSL Enabler Client Device Access Multiplexer EECID Edge DC Dual DwPTS Enabler Client Connectivity, Direct 45 Downlink Pilot 80 Identification Current Time Slot EES Edge

DCI Downlink E-LAN Ethernet Enabler Server Control Local Area Network EESID Edge

Information E2E End-to-End Enabler Server DF Deployment 50 ECCA extended clear 85 Identification Flavour channel EHE Edge

DL Downlink assessment, Hosting Environment DMTF Distributed extended CCA EGMF Exposure Management Task ECCE Enhanced Governance Force 55 Control Channel 90 Management

DPDK Data Plane Element, Function Development Kit Enhanced CCE EGPRS DM-RS, DMRS ED Energy Enhanced

Demodulation Detection GPRS Reference Signal 60 EDGE Enhanced 95 EIR Equipment DN Data network Datarates for GSM Identity Register DNN Data Network Evolution eLAA enhanced Name (GSM Evolution) Licensed Assisted

DNAI Data Network EAS Edge Access,

Access Identifier 65 Application Server 100 enhanced LAA EASID Edge EM Element

DRB Data Radio Application Server Manager Bearer Identification eMBB Enhanced

DRS Discovery ECS Edge Mobile Reference Signal 70 Configuration Server 105 Broadband EMS Element 35 E-UTRA Evolved FCCH Frequency Management System UTRA 70 Correction CHannel eNB evolved NodeB, E-UTRAN Evolved FDD Frequency E-UTRAN Node B UTRAN Division Duplex EN-DC E- EV2X Enhanced V2X FDM Frequency UTRA-NR Dual 40 F1AP FI Application Division

Connectivity Protocol 75 Multiplex EPC Evolved Packet Fl-C FI Control FDM A Frequency Core plane interface Division Multiple

EPDCCH FI -El FI Elser plane Access enhanced 45 interface FE Front End

PDCCH, enhanced FACCH Fast 80 FEC Forward Error Physical Associated Control Correction

Downlink Control CHannel FFS For Further Cannel FACCH/F Fast Study

EPRE Energy per 50 Associated Control FFT Fast Fourier resource element Channel/Full 85 Transformation

EPS Evolved Packet rate feLAA further System FACCH/H Fast enhanced Licensed

EREG enhanced REG, Associated Control Assisted enhanced resource 55 Channel/Half Access, further element groups rate 90 enhanced LAA ETSI European FACH Forward Access FN Frame Number

Telecommunica Channel FPGA Field- tions Standards FAUSCH Fast Programmable Gate Institute 60 Elplink Signalling Array

ETWS Earthquake and Channel 95 FR Frequency Tsunami Warning FB Functional Range

System Block FQDN Fully eUICC embedded FBI Feedback Qualified Domain UICC, embedded 65 Information Name Universal FCC Federal 100 G-RNTI GERAN Integrated Circuit Communications Radio Network Card Commission Temporary

Identity GERAN GSM Global System 70 HSDPA High

GSM EDGE for Mobile Speed Downlink RAN, GSM EDGE Communication Packet Access Radio Access s, Groupe Special HSN Hopping Network 40 Mobile Sequence Number

GGSN Gateway GPRS GTP GPRS 75 HSPA High Speed Support Node Tunneling Protocol Packet Access

GLONASS GTP -U GPRS HSS Home

GLObal'naya Tunnelling Protocol Subscriber Server NAvigatsionnay 45 for User Plane HSUPA High a Sputnikovaya GTS Go To Sleep 80 Speed Uplink Packet Si sterna (Engl.: Signal (related Access

Global Navigation to WUS) HTTP Hyper Text Satellite GUMMEI Globally Transfer Protocol System) 50 Unique MME HTTPS Hyper gNB Next Identifier 85 Text Transfer Protocol Generation NodeB GUTI Globally Secure (https is gNB-CU gNB- Unique Temporary http/ 1.1 over centralized unit, Next UE Identity SSL, i.e. port 443) Generation 55 HARQ Hybrid ARQ, I-Block

NodeB Hybrid 90 Information centralized unit Automatic Block gNB-DU gNB- Repeat Request ICCID Integrated distributed unit, Next HANDO Handover Circuit Card Generation 60 HFN HyperFrame Identification

NodeB Number 95 IAB Integrated distributed unit HHO Hard Handover Access and GNSS Global HLR Home Location Backhaul Navigation Satellite Register ICIC Inter-Cell System 65 HN Home Network Interference

GPRS General Packet HO Handover 100 Coordination Radio Service HPLMN Home ID Identity, GPSI Generic Public Land Mobile identifier

Public Subscription Network Identifier IDFT Inverse Discrete 35 IMPI IP Multimedia ISO International Fourier Private Identity 70 Organisation for

Transform IMPU IP Multimedia Standardisation IE Information PUblic identity ISP Internet Service element IMS IP Multimedia Provider IBE In-Band 40 Subsystem IWF Interworking- Emission IMSI International 75 Function IEEE Institute of Mobile I-WLAN Electrical and Subscriber Interworking

Electronics Identity WLAN Engineers 45 IoT Internet of Constraint IEI Information Things 80 length of the

Element IP Internet convolutional

Identifier Protocol code, USIM

IEIDL Information Ipsec IP Security, Individual key Element 50 Internet Protocol kB Kilobyte (1000

Identifier Data Security 85 bytes)

Length IP-CAN IP- kbps kilo-bits per

IETF Internet Connectivity Access second Engineering Task Network Kc Ciphering key Force 55 IP-M IP Multicast Ki Individual

IF Infrastructure IPv4 Internet 90 subscriber

IM Interference Protocol Version 4 authentication Measurement, IPv6 Internet key

Intermodulation Protocol Version 6 KPI Key , IP Multimedia 60 IR Infrared Performance Indicator

IMC IMS IS In Sync 95 KQI Key Quality Credentials IRP Integration Indicator IMEI International Reference Point KSI Key Set Mobile ISDN Integrated Identifier

Equipment 65 Services Digital ksps kilo-symbols

Identity Network 100 per second

IMGI International ISIM IM Services KVM Kernel Virtual mobile group identity Identity Module Machine LI Layer 1 35 LTE Long Term 70 Broadcast and

(physical layer) Evolution Multicast

Ll-RSRP Layer 1 LWA LTE-WLAN Service reference signal aggregation MBSFN received power LWIP LTE/WLAN Multimedia

L2 Layer 2 (data 40 Radio Level 75 Broadcast link layer) Integration with multicast

L3 Layer 3 IPsec Tunnel service Single (network layer) LTE Long Term Frequency

LAA Licensed Evolution Network

Assisted Access 45 M2M Machine-to- 80 MCC Mobile Country

LAN Local Area Machine Code

Network MAC Medium Access MCG Master Cell

LADN Local Control Group

Area Data Network (protocol MCOT Maximum

LBT Listen Before 50 layering context) 85 Channel

Talk MAC Message Occupancy

LCM LifeCycle authentication code Time

Management (security/ encry pti on MCS Modulation and

LCR Low Chip Rate context) coding scheme

LCS Location 55 MAC-A MAC 90 MD AF Management

Services used for Data Analytics

LCID Logical authentication Function

Channel ID and key MD AS Management

LI Layer Indicator agreement Data Analytics

LLC Logical Link 60 (TSG T WG3 context) 95 Service

Control, Low Layer MAC-IMAC used for MDT Minimization of

Compatibility data integrity of Drive Tests

LPLMN Local signalling messages ME Mobile

PLMN (TSG T WG3 context) Equipment

LPP LTE 65 MANO 100 MeNB master eNB

Positioning Protocol Management MER Message Error LSB Least and Orchestration Ratio

Significant Bit MBMS MGL Measurement

Multimedia Gap Length MGRP Measurement 35 Access Communication Gap Repetition CHannel 70 s Period MPUSCH MTC MU-MIMO Multi

MIR Master Physical Uplink Shared User MIMO Information Block, Channel MWUS MTC Management 40 MPLS Multiprotocol wake-up signal, MTC Information Base Label Switching 75 WUS MIMO Multiple Input MS Mobile Station NACK Negative Multiple Output MSB Most Acknowledgement MLC Mobile Significant Bit NAI Network Location Centre 45 MSC Mobile Access Identifier MM Mobility Switching Centre 80 NAS Non-Access Management MSI Minimum Stratum, Non- Access MME Mobility System Stratum layer Management Entity Information, NCT Network MN Master Node 50 MCH Scheduling Connectivity MNO Mobile Information 85 Topology

Network Operator MSID Mobile Station NC-JT Non MO Measurement Identifier coherent Joint Object, Mobile MSIN Mobile Station Transmission

Originated 55 Identification NEC Network MPBCH MTC Number 90 Capability

Physical Broadcast MSISDN Mobile Exposure CHannel Subscriber ISDN NE-DC NR-E-

MPDCCH MTC Number UTRA Dual

Physical Downlink 60 MT Mobile Connectivity Control Terminated, Mobile 95 NEF Network CHannel Termination Exposure Function

MPDSCH MTC MTC Machine-Type NF Network

Physical Downlink Communication Function Shared 65 s NFP Network CHannel mMTCmassive MTC, 100 Forwarding Path

MPRACH MTC massive NFPD Network

Physical Random Machine-Type Forwarding Path Descriptor NFV Network NPRACH 70 S-NNSAI Single- Functions Narrowband NSSAI

Virtualization Physical Random NSSF Network Slice NFVI NFV Access CHannel Selection Function Infrastructure 40 NPUSCH NW Network NFVO NFV Narrowband 75 NWU S N arrowb and Orchestrator Physical Uplink wake-up signal, NG Next Shared CHannel N arrowb and WU S Generation, Next Gen NPSS Narrowband NZP Non-Zero NGEN-DC NG- 45 Primary Power RAN E-UTRA-NR Synchronization 80 O&M Operation and Dual Connectivity Signal Maintenance NM Network NSSS Narrowband ODU2 Optical channel Manager Secondary Data Unit - type 2 NMS Network 50 Synchronization OFDM Orthogonal Management System Signal 85 Frequency Division N-PoP Network Point NR New Radio, Multiplexing of Presence Neighbour Relation OFDMA NMIB, N-MIB NRF NF Repository Orthogonal Narrowband MP3 55 Function Frequency Division NPBCH NRS Narrowband 90 Multiple Access

Narrowband Reference Signal OOB Out-of-band

Physical NS Network OO S Out of

Broadcast Service Sync

CHannel 60 NS A Non- Standalone OPEX OPerating

NPDCCH operation mode 95 EXpense

Narrowband NSD Network OSI Other System

Physical Service Descriptor Information

Downlink NSR Network OSS Operations Control CHannel 65 Service Record Support System NPDSCH NSSAINetwork Slice 100 OTA over-the-air

Narrowband Selection PAPR Peak-to-

Physical Assistance Average Power

Downlink Information Ratio Shared CHannel PAR Peak to PDN Packet Data 70 POC PTT over Average Ratio Network, Public Cellular PBCH Physical Data Network PP, PTP Point-to- Broadcast Channel PDSCH Physical Point PC Power Control, 40 Downlink Shared PPP Point-to-Point Personal Channel 75 Protocol

Computer PDU Protocol Data PRACH Physical PCC Primary Unit RACH Component Carrier, PEI Permanent PRB Physical Primary CC 45 Equipment resource block

P-CSCF Proxy Identifiers 80 PRG Physical CSCF PFD Packet Flow resource block

PCell Primary Cell Description group PCI Physical Cell P-GW PDN Gateway ProSe Proximity ID, Physical Cell 50 PHICH Physical Services, Identity hybrid-ARQ indicator 85 Proximity-

PCEF Policy and channel Based Service Charging PHY Physical layer PRS Positioning

Enforcement PLMN Public Land Reference Signal Function 55 Mobile Network PRR Packet

PCF Policy Control PIN Personal 90 Reception Radio Function Identification Number PS Packet Services

PCRF Policy Control PM Performance PSBCH Physical and Charging Rules Measurement Sidelink Broadcast Function 60 PMI Precoding Channel

PDCP Packet Data Matrix Indicator 95 PSDCH Physical Convergence PNF Physical Sidelink Downlink

Protocol, Packet Network Function Channel Data Convergence PNFD Physical PSCCH Physical Protocol layer 65 Network Function Sidelink Control

PDCCH Physical Descriptor 100 Channel Downlink Control PNFR Physical PSSCH Physical Channel Network Function Sidelink Shared

PDCP Packet Data Record Channel Convergence Protocol PSCell Primary SCell PSS Primary RAB Radio Access Link Control Synchronization 35 Bearer, Random 70 layer Signal Access Burst RLC AM RLC

PSTN Public Switched RACH Random Access Acknowledged Mode Telephone Network Channel RLC UM RLC

PT-RS Phase-tracking RADIUS Remote Unacknowledged reference signal 40 Authentication Dial 75 Mode

PTT Push-to-Talk In User Service RLF Radio Link PUCCH Physical RAN Radio Access Failure

Uplink Control Network RLM Radio Link Channel RAND RANDom Monitoring

PUSCH Physical 45 number (used for 80 RLM-RS

Uplink Shared authentication) Reference Channel RAR Random Access Signal for RLM

QAM Quadrature Response RM Registration Amplitude RAT Radio Access Management

Modulation 50 Technology 85 RMC Reference QCI QoS class of RAU Routing Area Measurement Channel identifier Update RMSI Remaining QCL Quasi co- RB Resource block, MSI, Remaining location Radio Bearer Minimum

QFI QoS Flow ID, 55 RBG Resource block 90 System QoS Flow group Information

Identifier REG Resource RN Relay Node QoS Quality of Element Group RNC Radio Network Service Rel Release Controller

QPSK Quadrature 60 REQ REQuest 95 RNL Radio Network (Quaternary) Phase RF Radio Layer Shift Keying Frequency RNTI Radio Network QZSS Quasi-Zenith RI Rank Indicator Temporary Satellite System RIV Resource Identifier

RA-RNTI Random 65 indicator value 100 ROHC RObust Header

Access RNTI RL Radio Link Compression RLC Radio Link RRC Radio Resource Control, Radio Control, Radio Resource Control 35 S-GW Serving SCM Security layer Gateway 70 Context

RRM Radio Resource S-RNTI SRNC Management Management Radio Network SCS Sub carrier RS Reference Temporary Spacing Signal 40 Identity SCTP Stream Control

RSRP Reference S-TMSI SAE 75 Transmission Signal Received Temporary Mobile Protocol Power Station SDAP Service Data RSRQ Reference Identifier Adaptation Signal Received 45 SA Standalone Protocol, Quality operation mode 80 Service Data

RSSI Received Signal SAE System Adaptation Strength Architecture Protocol layer Indicator Evolution SDL Supplementary

RSU Road Side Unit 50 SAP Service Access Downlink RSTD Reference Point 85 SDNF Structured Data Signal Time SAPD Service Access Storage Network difference Point Descriptor Function RTP Real Time SAPI Service Access SDP Session Protocol 55 Point Identifier Description Protocol

RTS Ready-To-Send SCC Secondary 90 SDSF Structured Data RTT Round Trip Component Carrier, Storage Function Time Secondary CC SDU Service Data Rx Reception, SCell Secondary Cell Unit

Receiving, Receiver 60 SCEF Service SEAF Security

S1AP SI Application Capability Exposure 95 Anchor Function Protocol Function SeNB secondary eNB

Sl-MME SI for SC-FDMA Single SEPP Security Edge the control plane Carrier Frequency Protection Proxy

Sl-U SI for the user 65 Division SFI Slot format plane Multiple Access 100 indication

S-CSCF serving SCG Secondary Cell SFTD Space-

CSCF Group Frequency Time

Diversity, SFN and frame timing 35 SN Secondary SSC Session and difference Node, Sequence Service

SFN System Frame Number 70 Continuity Number SoC System on Chip SS-RSRP

SgNB Secondary gNB SON Self-Organizing Synchronization SGSN Serving GPRS 40 Network Signal based Support Node SpCell Special Cell Reference S-GW Serving SP-CSI-RNTISemi- 75 Signal Received Gateway Persistent CSI RNTI Power SI System SPS Semi-Persistent SS-RSRQ Information 45 Scheduling Synchronization SI-RNTI System SQN Sequence Signal based Information RNTI number 80 Reference SIB System SR Scheduling Signal Received Information Block Request Quality SIM Subscriber 50 SRB Signalling SS-SINR Identity Module Radio Bearer Synchronization SIP Session SRS Sounding 85 Signal based Signal Initiated Protocol Reference Signal to Noise and SiP System in SS Synchronization Interference Ratio Package 55 Signal SSS Secondary SL Sidelink SSB Synchronization Synchronization SLA Service Level Signal Block 90 Signal Agreement SSID Service Set SSSG Search Space SM Session Identifier Set Group Management 60 SS/PBCH Block SSSIF Search Space SMF Session SSBRI SS/PBCH Set Indicator Management Function Block Resource 95 SST Slice/Service SMS Short Message Indicator, Types Service Synchronization SU-MIMO Single

SMSF SMS Function 65 Signal Block User MIMO SMTC SSB-based Resource SUL Supplementary Measurement Timing Indicator 100 Uplink Configuration TA Timing 35 TMSI Temporary Receiver and Advance, Tracking Mobile 70 Transmitter Area Subscriber UCI Uplink Control

TAC Tracking Area Identity Information Code TNL Transport UE User Equipment

TAG Timing 40 Network Layer UDM Unified Data Advance Group TPC Transmit Power 75 Management TAI Control UDP User Datagram

Tracking Area TPMI Transmitted Protocol Identity Precoding Matrix UDSF Unstructured

TAU Tracking Area 45 Indicator Data Storage Network Update TR Technical 80 Function

TB Transport Block Report UICC Universal TBS Transport Block TRP, TRxP Integrated Circuit Size Transmission Card

TBD To Be Defined 50 Reception Point UL Uplink TCI Transmission TRS Tracking 85 UM Configuration Reference Signal Unacknowledge

Indicator TRx Transceiver d Mode

TCP Transmission TS Technical UML Unified

Communication 55 Specifications, Modelling Language

Protocol Technical 90 UMTS Universal

TDD Time Division Standard Mobile Duplex TTI Transmission Telecommunica

TDM Time Division Time Interval tions System Multiplexing 60 Tx Transmission, UP User Plane TDMATime Division Transmitting, 95 UPF User Plane Multiple Access Transmitter Function TE Terminal U-RNTI UTRAN URI Uniform Equipment Radio Network Resource Identifier TEID Tunnel End 65 Temporary URL Uniform Point Identifier Identity 100 Resource Locator TFT Traffic Flow UART Universal URLLC Ultra- Template Asynchronous Reliable and Low Latency USB Universal Serial VNFFG VNF 70 XRES EXpected user Bus Forwarding Graph RESponse

USIM Universal VNFFGD VNF XOR exclusive OR Subscriber Identity Forwarding Graph ZC Zadoff-Chu Module 40 Descriptor ZP Zero Power

USS UE-specific VNFMVNF Manager 75 search space VoIP Voice-over-IP, UTRA UMTS Voice-over- Internet Terrestrial Radio Protocol Access 45 VPLMN Visited UTRAN Public Land Mobile

Universal Network Terrestrial Radio VPN Virtual Private Access Network Network 50 VRB Virtual

UwPTS Uplink Resource Block

Pilot Time Slot WiMAX V2I Vehicle-to- Worldwide Infrastruction Interoperability V2P Vehicle-to- 55 for Microwave Pedestrian Access V2V Vehicle-to- WLANWireless Local Vehicle Area Network

V2X Vehicle-to- WMAN Wireless everything 60 Metropolitan Area VIM Virtualized Network Infrastructure Manager WPANWireless VL Virtual Link, Personal Area Network VLAN Virtual LAN, X2-C X2-Control Virtual Local Area 65 plane Network X2-U X2-User plane VM Virtual XML extensible Machine Markup

VNF Virtualized Language Network Function Terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

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.

The term “processor circuitry” as used herein 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. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-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. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .

The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA /.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.