WO2024206315A1

WO2024206315A1 - Systems and methods of dynamic waveform switching for transmission of physical downlink channels

Info

Publication number: WO2024206315A1
Application number: PCT/US2024/021484
Authority: WO
Inventors: Gang Xiong; Yingyang Li; Yi Wang
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2023-03-31
Filing date: 2024-03-26
Publication date: 2024-10-03
Anticipated expiration: 2025-09-30

Abstract

Various embodiments herein provide techniques for dynamic downlink waveform switching. For example, aspects of various embodiments may include dynamic waveform switching for downlink (DL) transmission, such as physical downlink shared channel (PDSCH) transmission; and/or dynamic waveform switching for physical uplink shared channel (PUSCH) in case of bandwidth part (BWP) switching. Other embodiments may be described and claimed.

Description

SYSTEMS AND METHODS OF DYNAMIC WAVEFORM SWITCHING FOR TRANSMISSION OF PHYSICAL DOWNLINK CHANNELS

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/493,668, which was filed March 31, 2023.

BACKGROUND

In Third Generation Partnership Project (3GPP) New Radio (NR) Release (Rel)-15, a 4- step random access procedure (referred to as a physical random access channel (PRACH) procedure) was defined. The PRACH procedure may be used for a user equipment (UE) to obtain initial access to a wireless cellular network. In NR, the system design is based on a waveform of cyclic prefix (CP) - orthogonal frequency-division multiplexing (OFDM) for downlink (DE) and uplink (UL), as well as Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) for UL.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates a 4 step random access channel (RACH) procedure.

Figure 2 illustrates a 4 step RACH procedure with waveform indication, in accordance with various embodiments.

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

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

Figure 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

Figure 6 illustrates a network in accordance with various embodiments.

Figures 7, 8, and 9 illustrate example procedures to practice various embodiments herein.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

Various embodiments herein provide systems and methods of dynamic downlink waveform switching. For example, aspects of various embodiments may include:

• Dynamic waveform switching for DL transmission

• Dynamic waveform switching for PUSCH in case of bandwidth part (BWP) switching

As mentioned above, a 4-step random access procedure (referred to as a random access channel (RACH) procedure was defined in 3GPP NR Rel- 15. Figure 1 illustrates the 4-step RACH procedure for initial access. In the first step, the user equipment (UE) transmits physical random access channel (PRACH) in the uplink, which allows the next generation Node B (gNB) to estimate the delay between gNB and UE for subsequent uplink (UL) timing adjustment. The PRACH in the first step may be referred to as a PRACH preamble, and may include a randomly selected preamble signature. Subsequently, in the second step, gNB sends the random access response (RAR) which carries timing advanced (TA) command information and uplink grant for the uplink transmission that is to be transmitted in the third step. The UE expects to receive the RAR within a time window, of which the start and end may be configured by the gNB, e.g., via system information block (SIB). The UE then sends Msg3 based on the uplink grant in the RAR. The Msg3 may include a physical uplink shared channel (PUSCH). The gNB then sends a Msg4 for contention resolution.

In NR, system design is based on waveform choice of cyclic prefix - orthogonal frequencydivision multiplexing (CP-OFDM) for DL and UL, and additionally, Discrete Fourier Transform- spread-OFDM (DFT-s-OFDM) for UL. The DFT-s-OFDM waveform may be realized by enabling transform preceding at the transmitter side. When transform precoding is disabled, CP- OFDM waveform is employed for PUSCH transmission. Typically, DFT-s-OFDM waveform can achieve better uplink coverage performance due to its low peak-to-average power ratio (PAPR) compared to CP-OFDM waveform.

For 6G, it is envisioned that different waveforms, e.g., CP-OFDM waveform and single carrier based waveform such as DFT-s-OFDM and/or single carrier - frequency domain equalization (SC-FDE) waveform may be supported for DL transmission. In some cases, the waveform type may depend on the deployment scenario, UE location, traffic type, and/or other conditions. When more than one waveform type is employed for the transmission of DL signal/channel, additional mechanisms may need to be defined to allow dynamic adaptation of waveform type for DL signal/channel transmission.

• Dynamic waveform switching for DL transmission

Dynamic waveform switching for DL transmission

Embodiments of dynamic waveform switching for DL transmission are described further below.

In one embodiment, one field can be included in the downlink control information (DCI) for scheduling physical downlink shared channel (PDSCH), which is used to indicate the waveform used for the PDSCH transmission. In some aspects, dynamic waveform switching may be applied for the DCI format with Cyclic Redundancy Check (CRC) scrambled with Cell - Radio Network Temporary Identifier (C-RNTI), CS-RNTI, and/or MCS-RNTI, or for unicast PDSCH transmission.

In some aspects, the DCI format used for dynamic waveform switching for PDSCH transmissions may be DCI format 1_1 and/or 1_2 or DCI format for multi-cell scheduling. The DCI format 1_1 and/or 1_2 is for single PDSCH scheduling or multi-PDSCH scheduling in a serving cell. In some aspects, the DCI format used for dynamic waveform switching for PDSCH transmissions may be DCI format l_0.

When two waveforms are supported and/or configured for PDSCH transmissions, 1-bit field may be included in the DCI for scheduling PDSCH, wherein bit “0” may be used to indicate a first waveform type is applied for the scheduled PDSCH transmission, while bit “1” may be used to indicate a second waveform type is applied for scheduled PDSCH transmission. In one example, a first waveform type may be CP-OFDM, while a second waveform type may be DFT-s-OFDM waveform or SC-FDE waveform.

When more than two waveforms are supported and/or configured for PDSCH transmission, the field size for dynamic waveform indication can be determined as [log₂(I\vi )l, where I_WF is the number of waveforms that are supported and/or configured for PDSCH transmission. In particular, one code point of the field is used to indicate which waveform is applied for PDSCH transmission. In one option, the presence of dynamic waveform switching field may be configured, e.g., by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling, dynamically indicated in the DCI, or a combination thereof.

In another embodiment, for 4-step RACH procedure, physical random access channel (PRACH) resource partitioning may be used for UE to request the waveform type for Msg2 and/or Msg4 transmission. In particular, separate PRACH preamble on shared PRACH occasion or separate PRACH occasions may be used to differentiate a first waveform type and a second waveform type used for Msg2 and/or Msg4 transmission. Further, the first waveform type may be predefined in the specification or indicated in the master information block (MIB) or configured by RMSI.

For this option, when UE transmits the PRACH in a first set of PRACH resources, which corresponds to a first waveform type for Msg2 and/or Msg4 transmission, the UE may receive Msg2 and/or Msg4 by assuming the first waveform type. Similarly, when UE transmits the PRACH in a second set of PRACH resources, which corresponds to a second waveform type for Msg2 and/or Msg4 transmission, the UE may receive Msg2 and/or Msg4 by assuming the second waveform type.

In another option, Msg3 may include request of waveform type for DL transmission. In this case, after UE transmits Msg3 which includes the request of waveform type, the UE may receive Msg4 by assuming the requested waveform type.

In another embodiment, for 4-step RACH procedure, one field in the DCI for scheduling Msg2 transmission may be used to indicate the waveform that is used for Msg2 PDSCH transmission. In this case, the field is included in the DCI format with CRC scrambled with RA- RNTI.

In another option, one field in the DCI for scheduling Msg4 may be used to indicate the waveform that is used for Msg4 transmission. In this case, the field is included in the DCI format with CRC scrambled with TC-RNTI.

In some aspects, if same set of waveforms are supported for the transmission of both DL and UL channels and/or signals, when gNB indicates the waveform type for the Msg2 PDSCH transmission, the UE may assume the same waveform type for the Msg3 PUSCH transmission.

Figure 2 illustrates one example of 4-step RACH procedure with waveform indication. In the example, UE transmits PRACH with separate PRACH preambles in shared PRACH occasions or separate PRACH occasions to request the waveform for subsequent PDSCH transmissions. Subsequently, gNB indicates the waveform type in the DCI for scheduling Msg2 and/or Msg4 PDSCH. In another embodiment, for 2-step RACH, PRACH resource partitioning and/or MsgA PUSCH may be used to request the waveform type for MsgB PDSCH transmission. In particular, separate PRACH preamble on shared PRACH occasion or separate PRACH occasions may be used to differentiate a first waveform type and a second waveform type used for MsgB transmission. In addition, MsgA PUSCH may include request of waveform type for MsgB transmission.

In this case, after UE transmits MsgA PRACH with PRACH resource partitioning or MsgA PUSCH which includes the request of waveform type, the UE may receive MsgB by assuming the requested waveform type.

In another option, one field in the DCI for scheduling MsgB transmission may be used to indicate the waveform that is used for MsgB PDSCH transmission. In this case, the field is included in the DCI format with CRC scrambled with MsgB-RNTI.

In another embodiment, when different waveforms are supported and/or configured for PDSCH transmission, per field size match is applied to align the DCI field size among different configured waveforms.

In particular, for DCI format that includes dynamic waveform indication for scheduling PDSCH transmission, bit width of each field is set to the maximum between the bit width of the field assuming different configured waveforms, if different. Further, for the waveform indicated in the DCI, if the bit width N of a field would be smaller than the maximum bit width of the field, UE decodes the field using N least significant bits. If N=0, the UE ignores the field for the indicated waveform.

In another embodiment, when different waveforms are supported and/or configured for PDSCH transmission, per DCI format size match is applied to align the DCI field size among different configured waveforms.

For example, overall DCI size may be determined in accordance with the maximum DCI size among all configured waveforms. In some embodiments, a dynamic waveform indication field may be included in the DCI format, e.g., at the beginning of the DCI format. In this case, DCI field size for each DCI field is determined in accordance with the indicated waveform type. In addition, zero padding may be appended after all the DCI fields to match the maximum size determined from all configured waveforms.

In another embodiment, in case of multi-PDSCH scheduling, where a DCI is used to schedule multiple PDSCHs carrying independent transport blocks (TBs) in a cell, a single dynamic waveform indication field may be included in the DCI, which can be used to commonly indicate the waveform type used for the multiple PDSCHs. In another option, separate dynamic waveform indication field may be included in the DCI for multi-PDSCH scheduling, where each field is used to indicate the waveform for each coscheduled PDSCH, respectively.

In one embodiment, one or more waveforms can be configured for the PDCCH transmission for a UE. The configuration can be commonly applied to all serving cells. Alternatively, the configuration can be configured per scheduling cell. Alternatively, the configuration can be configured per scheduled cell. In another option, the configuration of waveform type for PDCCH transmission can be configured per BWP.

In one option, one waveform for PDCCH transmission can be configured and commonly applied to all UE specific search space (USS) set of the UE. Note: it is possible that the PDCCH candidates in a common search space may use a different waveform.

In one option, the waveform for PDCCH transmission can be configured per USS set for the UE. In this option, the PDCCH transmissions for the UE may be configured with different waveforms in different SS sets.

In one option, the waveform for PDCCH transmission can be configured per Control Resource Set (CORESET) for the UE. In this option, the PDCCH transmissions for the UE may be configured with different waveforms in different CORESET.

In one option, the waveform for PDCCH transmission can be configured per PDCCH aggregation level (AL) for the UE. for example, for low AL, OFDM waveform may be used for better efficiency, on the other hand, for high AL, DFT-s-OFDM waveform or SC-FDE waveform may be used for better coverage. The AL dependent waveform configuration can commonly apply to all SS sets for a UE. Alternatively, the AL dependent waveform configuration can be configured per SS set.

In another embodiment, in case of multi-cell scheduling, where a DCI is used to schedule PDSCH transmissions in more than one cells, a single dynamic waveform indication field may be included in the DCI for multi-cell scheduling, which can be used to commonly indicate the waveform type used for the multiple PDSCHs in more than one carrier.

In another option, separate dynamic waveform indication field may be included in the DCI for multi-cell scheduling, where each field is used to indicate the waveform for the PDSCH in each co-scheduled cell, respectively. When dynamic waveform indication is not configured or presence of dynamic waveform indication field in the DCI format is not configured by RRC signaling for a carrier, waveform indication for the carrier is not included in the waveform indication field. Dynamic waveform switching for PUSCH and/or PDSCH in case of BWP switching

Embodiments of dynamic waveform switching for PUSCH in case of BWP switching are described further below. While aspects of various embodiments are described with reference to PUSCH, embodiments may also apply for the case for dynamic waveform switching for PDSCH in case of BWP switching.

In one embodiment, in case of dynamic BWP switching by a DCI, UE does not expect the dynamic waveform indication is included in the DCI for scheduling PUSCH transmission. In this case, UE determines the waveform for PUSCH transmission in accordance with existing mechanism.

In another embodiment, in case of dynamic BWP switching by a DCI, if dynamic waveform indication is configured for both current active BWP and target BWP which is different from current active BWP, UE first determines each field size for current active BWP in accordance with indicated waveform from dynamic waveform indication field. In particular, either per field based size match or per DCI format based size match may be used to determine the field size for current active BWP.

Further, UE derives the indicated values for each bit field for target BWP based on the existing rule for BWP switching as defined in Clause 12 in 3GPP Technical Standard (TS) 38.213, V17.4.0 (hereinafter “TS38.213”), e.g., using zero padding or least significant bits depending on the field required for the DCI format interpretation for the target BWP.

In another embodiment, in case of dynamic BWP switching by a DCI, when current active BWP is configured with dynamic waveform switching or the dynamic waveform switching field is included in the DCI, and when target BWP is not configured with dynamic waveform switching or the dynamic waveform switching field is not included in the DCI, the field size in the DCI format with BWP switching may be determined in accordance with a reference waveform in the current active BWP for the scheduled PUSCH transmission.

The reference waveform may be determined based on one or more of the following options:

• A default waveform, which may be predefined in the specification, or configured by higher layers via RRC signalling.

• The waveform that is determined based on the dynamic waveform indication in the DCI.

• The waveform that is determined based on the dynamic waveform indication in last DCI for PUSCH in the current active BWP.

• The waveform that is determined based on the existing mechanism for the target BWP. In one example, when the waveform for the PUSCH transmission is determined based on the configuration. The waveform for the PUSCH transmission in target BWP is determined based on existing mechanism, e.g., determined based on the configuration. Further, UE derives the indicated values for each bit field for target BWP based on the existing rule for BWP switching as defined in Clause 12 in TS38.213, e.g., using zero padding or least significant bits depending on the field required for the DCI format interpretation for the target BWP.

In another embodiment, in case of dynamic BWP switching by a DCI, when current active and target BWP are configured with dynamic waveform switching or the dynamic waveform switching field is included in the DCI, the field size in the DCI format with BWP switching may be determined in accordance with a reference waveform in the current active BWP for the scheduled PUSCH transmission.

• The waveform that is determined based on the dynamic waveform indication in the DCI for the target BWP.

• The waveform that is determined based on the existing mechanism for the target BWP. In one example, the waveform for the PUSCH transmission for the target BWP is determined based on the configuration transformPrecoder in PUSCH- Config or msg3-transformPrecoder.

The waveform for the PUSCH transmission in target BWP is determined by the dynamic waveform switching field in the DCI. Further, UE derives the indicated values for each bit field for target BWP based on the existing rule for BWP switching as defined in Clause 12 in TS38.213, e.g., using zero padding or least significant bits depending on the field required for the DCI format interpretation for the target BWP.

In another embodiment, in case of dynamic BWP switching by a DCI, when current active BWP is not configured with dynamic waveform switching or the dynamic waveform switching field is not included in the DCI, and when target BWP is configured with dynamic waveform switching or the dynamic waveform switching field is included in the DCI, the DCI field size is determined based on the configuration in current active BWP. Further, dynamic waveform indication with “0” or configured waveform is applied for waveform for target BWP. SYSTEMS AND IMPLEMENTATIONS

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

Figure 3 illustrates a network 300 in accordance with various embodiments. The network 300 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 300 may include a UE 302, which may include any mobile or non-mobile computing device designed to communicate with a RAN 304 via an over-the-air connection. The UE 302 may be communicatively coupled with the RAN 304 by a Uu interface. The UE 302 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, loT device, etc.

In some embodiments, the network 300 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 302 may additionally communicate with an AP 306 via an over-the-air connection. The AP 306 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 304. The connection between the UE 302 and the AP 306 may be consistent with any IEEE 802.11 protocol, wherein the AP 306 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 302, RAN 304, and AP 306 may utilize cellular- WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 302 being configured by the RAN 304 to utilize both cellular radio resources and WLAN resources.

The RAN 304 may include one or more access nodes, for example, AN 308. AN 308 may terminate air-interface protocols for the UE 302 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 308 may enable data/voice connectivity between CN 320 and the UE 302. In some embodiments, the AN 308 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 308 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 308 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 304 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 304 is an LTE RAN) or an Xn interface (if the RAN 304 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 304 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 302 with an air interface for network access. The UE 302 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 304. For example, the UE 302 and RAN 304 may use carrier aggregation to allow the UE 302 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 304 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 302 or AN 308 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 304 may be an LTE RAN 310 with eNBs, for example, eNB 312. The LTE RAN 310 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 304 may be an NG-RAN 314 with gNBs, for example, gNB 316, or ng-eNBs, for example, ng-eNB 318. The gNB 316 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 316 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 318 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 316 and the ng-eNB 318 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 314 and a UPF 348 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN314 and an AMF 344 (e.g., N2 interface).

The NG-RAN 314 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 302 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 302, 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 302 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 302 and in some cases at the gNB 316. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

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

In some embodiments, the CN 320 may be an LTE CN 322, which may also be referred to as an EPC. The LTE CN 322 may include MME 324, SGW 326, SGSN 328, HSS 330, PGW 332, and PCRF 334 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 322 may be briefly introduced as follows.

The MME 324 may implement mobility management functions to track a current location of the UE 302 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 326 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 322. The SGW 326 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 328 may track a location of the UE 302 and perform security functions and access control. In addition, the SGSN 328 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 324; MME selection for handovers; etc. The S3 reference point between the MME 324 and the SGSN 328 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

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

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

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

In some embodiments, the CN 320 may be a 5GC 340. The 5GC 340 may include an AUSF 342, AMF 344, SMF 346, UPF 348, NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, and AF 360 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 340 may be briefly introduced as follows.

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

The AMF 344 may allow other functions of the 5GC 340 to communicate with the UE 302 and the RAN 304 and to subscribe to notifications about mobility events with respect to the UE 302. The AMF 344 may be responsible for registration management (for example, for registering UE 302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 344 may provide transport for SM messages between the UE 302 and the SMF 346, and act as a transparent proxy for routing SM messages. AMF 344 may also provide transport for SMS messages between UE 302 and an SMSF. AMF 344 may interact with the AUSF 342 and the UE 302 to perform various security anchor and context management functions. Furthermore, AMF 344 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 304 and the AMF 344; and the AMF 344 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 344 may also support NAS signaling with the UE 302 over an N3 IWF interface. The SMF 346 may be responsible for SM (for example, session establishment, tunnel management between UPF 348 and AN 308); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 348 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 El system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 344 over N2 to AN 308; 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 302 and the data network 336.

The UPF 348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 336, and a branching point to support multi-homed PDU session. The UPF 348 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 348 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 350 may select a set of network slice instances serving the UE 302. The NSSF 350 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 350 may also determine the AMF set to be used to serve the UE 302, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 354. The selection of a set of network slice instances for the UE 302 may be triggered by the AMF 344 with which the UE 302 is registered by interacting with the NSSF 350, which may lead to a change of AMF. The NSSF 350 may interact with the AMF 344 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 350 may exhibit an Nnssf service-based interface.

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

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

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

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

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

The data network 336 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 338.

Figure 4 schematically illustrates a wireless network 400 in accordance with various embodiments. The wireless network 400 may include a UE 402 in wireless communication with an AN 404. The UE 402 and AN 404 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 402 may be communicatively coupled with the AN 404 via connection 406. The connection 406 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 402 may include a host platform 408 coupled with a modem platform 410. The host platform 408 may include application processing circuitry 412, which may be coupled with protocol processing circuitry 414 of the modem platform 410. The application processing circuitry 412 may run various applications for the UE 402 that source/sink application data. The application processing circuitry 412 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 414 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 406. The layer operations implemented by the protocol processing circuitry 414 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 410 may further include digital baseband circuitry 416 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 414 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 410 may further include transmit circuitry 418, receive circuitry 420, RF circuitry 422, and RF front end (RFFE) 424, which may include or connect to one or more antenna panels 426. Briefly, the transmit circuitry 418 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 420 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 422 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 424 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 418, receive circuitry 420, RF circuitry 422, RFFE 424, and antenna panels 426 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 414 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 426, RFFE 424, RF circuitry 422, receive circuitry 420, digital baseband circuitry 416, and protocol processing circuitry 414. In some embodiments, the antenna panels 426 may receive a transmission from the AN 404 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 426.

A UE transmission may be established by and via the protocol processing circuitry 414, digital baseband circuitry 416, transmit circuitry 418, RF circuitry 422, RFFE 424, and antenna panels 426. In some embodiments, the transmit components of the UE 404 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 426.

Similar to the UE 402, the AN 404 may include a host platform 428 coupled with a modem platform 430. The host platform 428 may include application processing circuitry 432 coupled with protocol processing circuitry 434 of the modem platform 430. The modem platform may further include digital baseband circuitry 436, transmit circuitry 438, receive circuitry 440, RF circuitry 442, RFFE circuitry 444, and antenna panels 446. The components of the AN 404 may be similar to and substantially interchangeable with like-named components of the UE 402. In addition to performing data transmission/reception as described above, the components of the AN 408 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 5 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 5 shows a diagrammatic representation of hardware resources 500 including one or more processors (or processor cores) 510, one or more memory/storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 502 may be executed to provide an execution environment for one or more network slices/sub- slices to utilize the hardware resources 500.

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

Figure 6 illustrates a network 600 in accordance with various embodiments. The network 600 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 600 may operate concurrently with network 300. For example, in some embodiments, the network 600 may share one or more frequency or bandwidth resources with network 300. As one specific example, a UE (e.g., UE 602) may be configured to operate in both network 600 and network 300. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 300 and 600. In general, several elements of network 600 may share one or more characteristics with elements of network 300. For the sake of brevity and clarity, such elements may not be repeated in the description of network 600.

The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 608 via an over-the-air connection. The UE 602 may be similar to, for example, UE 302. The UE 602 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, loT device, etc.

Although not specifically shown in Figure 6, in some embodiments the network 600 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 6, the UE 602 may be communicatively coupled with an AP such as AP 306 as described with respect to Figure 3. Additionally, although not specifically shown in Figure 6, in some embodiments the RAN 608 may include one or more ANss such as AN 308 as described with respect to Figure 3. The RAN 608 and/or the AN of the RAN 608 may be referred to as a base station (BS), a RAN node, or using some other term or name.

The UE 602 and the RAN 608 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.

The RAN 608 may allow for communication between the UE 602 and a 6G core network (CN) 610. Specifically, the RAN 608 may facilitate the transmission and reception of data between the UE 602 and the 6G CN 610. The 6G CN 610 may include various functions such as NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, AF 360, SMF 346, and AUSF 342. The 6G CN 610 may additional include UPF 348 and DN 336 as shown in Figure 6.

Additionally, the RAN 608 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 624 and a Compute Service Function (Comp SF) 636. The Comp CF 624 and the Comp SF 636 may be parts or functions of the Computing Service Plane. Comp CF 624 may be a control plane function that provides functionalities such as management of the Comp SF 636, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlying computing infrastructure for computing resource management, etc.. Comp SF 636 may be a user plane function that serves as the gateway to interface computing service users (such as UE 602) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 636 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 636 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 624 instance may control one or more Comp SF 636 instances.

Two other such functions may include a Communication Control Function (Comm CF) 628 and a Communication Service Function (Comm SF) 638, which may be parts of the Communication Service Plane. The Comm CF 628 may be the control plane function for managing the Comm SF 638, communication sessions creation/configuration/releasing, and managing communication session context. The Comm SF 638 may be a user plane function for data transport. Comm CF 628 and Comm SF 638 may be considered as upgrades of SMF 346 and UPF 348, which were described with respect to a 5G system in Figure 3. The upgrades provided by the Comm CF 628 and the Comm SF 638 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 346 and UPF 348 may still be used.

Two other such functions may include a Data Control Function (Data CF) 622 and Data Service Function (Data SF) 632 may be parts of the Data Service Plane. Data CF 622 may be a control plane function and provides functionalities such as Data SF 632 management, Data service creation/configuration/releasing, Data service context management, etc. Data SF 632 may be a user plane function and serve as the gateway between data service users (such as UE 602 and the various functions of the 6G CN 610) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.

Another such function may be the Service Orchestration and Chaining Function (SOCF) 620, which may discover, orchestrate and chain up communication/computing/data services provided by functions in the network. Upon receiving service requests from users, SOCF 620 may interact with one or more of Comp CF 624, Comm CF 628, and Data CF 622 to identify Comp SF 636, Comm SF 638, and Data SF 632 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 636, Comm SF 638, and Data SF 632 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 620 may also responsible for maintaining, updating, and releasing a created service chain.

Another such function may be the service registration function (SRF) 614, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 636 and Data SF 632 gateways and services provided by the UE 602. The SRF 614 may be considered a counterpart of NRF 354, which may act as the registry for network functions.

Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 626, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 612 and eSCP-U 634, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 626 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

Another such function is the AMF 644. The AMF 644 may be similar to 344, but with additional functionality. Specifically, the AMF 644 may include potential functional repartition, such as move the message forwarding functionality from the AMF 644 to the RAN 608.

Another such function is the service orchestration exposure function (SOEF) 618. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications.

The UE 602 may include an additional function that is referred to as a computing client service function (comp CSF) 604. The comp CSF 604 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 620, Comp CF 624, Comp SF 636, Data CF 622, and/or Data SF 632 for service discovery, request/response, compute task workload exchange, etc. The Comp CSF 604 may also work with network side functions to decide on whether a computing task should be run on the UE 602, the RAN 608, and/or an element of the 6G CN 610.

The UE 602 and/or the Comp CSF 604 may include a service mesh proxy 606. The service mesh proxy 606 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 606 may include one or more of addressing, security, load balancing, etc.

Example Procedures

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 3-6, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. For example, Figure 7 illustrates an example process 700 in accordance with various embodiments. In some embodiments, the process 700 may be performed by a UE or a portion thereof. At 702, the process may include receiving a downlink control information (DCI) to schedule a physical downlink shared channel (PDSCH), wherein the DCI includes an indication of a waveform type for the PDSCH. At 704, the process may further include decoding the PDSCH based on the indicated waveform type.

In some embodiments, the PDSCH may correspond to a downlink message of a random access procedure, such as a Msg2 and/or Msg 4 of a 4-step random access procedure, and/or a MsgB of a 2-step random access procedure. In some embodiments, the UE may send a message to a gNB to request the indication of the waveform type. For example, the request may be included in an uplink message of a random access procedure, such as a Msgl and/or Msg3 of the 4-step random access procedure, and/or a MsgA PRACH and/or PUSCH of the 2-step random access procedure. Figure 8 illustrates another example process 800 in accordance with various embodiments. In some embodiments, the process 800 may be performed by a UE or a portion thereof. At 802, the process 800 may include identifying a first set of physical random access channel (PRACH) resources that are associated with a first waveform type and a second set of PRACH resources that are associated with a second waveform type. At 804, the process 800 may further include encoding a first random access message for transmission on a selected one of the first or second set of PRACH resources. At 806, the process 800 may further include decoding a second random access message based on the respective first or second waveform type that is associated with the selected first or second set of PRACH resources.

For example, the first random access message may be a Msgl (e.g., PRACH preamble) of a 4-step random access procedure, or a MsgA PRACH of a 2-step random access procedure. The second random access message may be a Msg2 or a Msg4 of the 4-step random access procedure, or a MsgB of the 2-step random access procedure.

Figure 9 illustrates another example process 900 in accordance with various embodiments. In some embodiments, the process 900 may be performed by a gNB or a portion thereof. At 902, the process 900 may include encoding, for transmission to a user equipment (UE), downlink control information (DCI) to schedule a physical downlink shared channel (PDSCH), wherein the DCI includes an indication of a waveform type for the PDSCH. At 904, the process 900 may further include encoding the PDSCH for transmission based on the indicated waveform type.

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

Some non-limiting examples of various embodiments are provided below.

Example 1 may include an apparatus of a user equipment (UE), the apparatus comprising processor circuitry to: receive a downlink control information (DCI) to schedule a physical downlink shared channel (PDSCH), wherein the DCI includes an indication of a waveform type for the PDSCH; and decode the PDSCH based on the indicated waveform type. The apparatus may further include a memory to store the waveform type.

Example 2 may include the apparatus of example 1 , wherein the DCI has a DCI format with cyclic redundancy check (CRC) scrambled with a cell (C)-radio Network Temporary Identifier (RNTI), configured scheduling (CS)-RNTI, and/or modulation and coding scheme (MCS)-RNTI.

Example 3 may include the apparatus of example 1 , wherein the DCI is a DCI format 1_1, a DCI format 1_2, a DCI format l_0, or a DCI format for multi-cell scheduling.

Example 4 may include the apparatus of example 1 , wherein the PDSCH corresponds to a Msg2, a Msg4, or a MsgB of a random access procedure.

Example 5 may include the apparatus of example 4, wherein the waveform type is a first waveform type, and wherein the processor circuitry is further to encode, for transmission, a Msgl, a Msg3, a MsgA physical random access channel (PRACH), or a MsgA physical uplink shared channel (PUSCH) of the random access procedure, wherein the Msgl, the Msg3, the MsgA PRACH, or the MsgA PUSCH includes a request for the waveform type.

Example 6 may include the apparatus of example 5, wherein the waveform type is a first waveform type, wherein the Msgl, the Msg3, or the MsgA is transmitted in PRACH resources associated with a second waveform type that is different than the first waveform type, and wherein the Msg2, the Msg4, or the MsgB is received based on the second waveform type.

Example 7 may include the apparatus of any one of examples 1-6, wherein the waveform type is indicated from among a plurality of supported waveform types that include two or more of: cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM), discrete Fourier Transform (DFT)-spread (s)-OFDM, or single carrier (SC)-frequency domain equalization (FDE)-OFDM.

Example 8 may include the apparatus of any one of examples 1-6, wherein the waveform type is indicated from among a plurality of supported waveform types, and wherein the DCI includes fields or a DCI format that are size matched based on the supported waveform types.

Example 9 may include the apparatus of any one of examples 1-6, wherein the DCI is to schedule multiple PDSCHs to carry different transport blocks in a cell, and wherein the DCI includes a single field with the indication of the waveform type that is to apply to the multiple PDSCHs.

Example 10 may include one or more computer-readable media having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE) configure the UE to: identify a first set of physical random access channel (PRACH) resources that are associated with a first waveform type and a second set of PRACH resources that are associated with a second waveform type; encode a first random access message for transmission on a selected one of the first or second set of PRACH resources; and decode a second random access message based on the respective first or second waveform type that is associated with the selected first or second set of PRACH resources.

Example 11 may include the one or more computer-readable media of example 10, wherein the first random access message includes a request for a waveform type to be used for a physical downlink shared channel (PDSCH).

Example 12 may include the one or more computer-readable media of example 11, wherein the second random access message includes an indication of the waveform type to be used for the PDSCH.

Example 13 may include the one or more computer-readable media of example 10, wherein the first and second sets of PRACH resources are included in separate PRACH occasions or same PRACH occasions with different PRACH preambles.

Example 14 may include the one or more computer-readable media of any one of examples 10-13, wherein the first random access message is a PRACH preamble, a Msg3, a MsgA PRACH, or a MsgA physical uplink shared channel (PUSCH) of a random access procedure, and the second random access message is a Msg2, a Msg4, or a MsgB of the random access procedure.

Example 15 may include one or more computer-readable media having instructions, stored thereon, that when executed by one or more processors of a next generation Node B (gNB) configure the gNB to: encode, for transmission to a user equipment (UE), downlink control information (DCI) to schedule a physical downlink shared channel (PDSCH), wherein the DCI includes an indication of a waveform type for the PDSCH; and encode the PDSCH for transmission based on the indicated waveform type.

Example 16 may include the one or more computer-readable media of example 15, wherein the DCI has a cyclic redundancy check (CRC) scrambled with a cell (C)-radio Network Temporary Identifier (RNTI), configured scheduling (CS)-RNTI, and/or modulation and coding scheme (MCS)-RNTI, and wherein the DCI is a DCI format 1_1, a DCI format 1_2, a DCI format l_0, or a DCI format for multi-cell scheduling.

Example 17 may include the one or more computer-readable media of example 15, wherein the PDSCH is included in a message of a random access procedure.

Example 18 may include the one or more computer-readable media of example 17, wherein the message is a first message, and wherein the instructions, when executed, further configure the gNB to: receive, from the UE, a second message of the random access procedure, wherein the second message includes a request for the waveform type. Example 19 may include the one or more computer-readable media of example 18, wherein the waveform type is a first waveform type, wherein the second message is received in PRACH resources associated with a second waveform type that is different than the first waveform type, and wherein the DCI is encoded based on the second waveform type.

Example 20 may include the one or more computer-readable media of any one of examples 15-19, wherein the waveform type is indicated from among a plurality of supported waveform types that include two or more of: cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM), discrete Fourier Transform (DFT)-spread (s)-OFDM, or single carrier (SC)-frequency domain equalization (FDE)-OFDM.

Example 21 may include a method of wireless communication in a wireless cellular system (e.g., a fifth generation (5G) or new radio (NR) system), the method comprising: indicating, by a gNodeB (gNB), a dynamic waveform indication in a downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); and transmitting, by the gNB, the PDSCH in accordance with the waveform type indicated by the dynamic waveform indication.

Example 22 may include the method of example 21 or some other example herein, wherein dynamic waveform switching may be applied for the DCI format with Cyclic Redundancy Check (CRC) scrambled with Cell - Radio Network Temporary Identifier (C- RNTI), CS-RNTI, and/or MCS-RNTI, or for unicast PDSCH transmission.

Example 23 may include the method of example 21 or some other example herein, wherein DCI format used for dynamic waveform switching for PDSCH transmissions may be DCI format 1_1 and/or 1_2 or DCI format for multi-cell scheduling

Example 24 may include the method of example 21 or some other example herein, wherein for 4-step RACH procedure, physical random access channel (PRACH) resource partitioning may be used for UE to request the waveform type for Msg2 and/or Msg4 transmission.

Example 25 may include the method of example 21 or some other example herein, wherein for 4-step RACH procedure, one field in the DCI for scheduling Msg2 transmission may be used to indicate the waveform that is used for Msg2 PDSCH transmission

Example 26 may include the method of example 21 or some other example herein, wherein for 2-step RACH, PRACH resource partitioning and/or MsgA PUSCH may be used to request the waveform type for MsgB PDSCH transmission

Example 27 may include the method of example 21 or some other example herein, wherein one field in the DCI for scheduling MsgB transmission may be used to indicate the waveform that is used for MsgB PDSCH transmission Example 28 may include the method of example 21 or some other example herein, wherein when different waveforms are supported and/or configured for PDSCH transmission, per field size match is applied to align the DCI field size among different configured waveforms.

Example 29 may include the method of example 21 or some other example herein, wherein when different waveforms are supported and/or configured for PDSCH transmission, per DCI format size match is applied to align the DCI field size among different configured waveforms

Example 30 may include the method of example 21 or some other example herein, wherein in case of multi-PDSCH scheduling, where a DCI is used to schedule multiple PDSCHs carrying independent transport blocks (TB) in a cell, a single dynamic waveform indication field may be included in the DCI, which can be used to commonly indicate the waveform type used for the multiple PDSCHs

Example 31 may include the method of example 21 or some other example herein, wherein one or more waveforms can be configured for the PDCCH transmission for a UE.

Example 32 may include the method of example 21 or some other example herein, wherein in case of dynamic BWP switching by a DCI, UE does not expect the dynamic waveform indication is included in the DCI for scheduling PUSCH transmission.

Example 33 may include the method of example 21 or some other example herein, wherein in case of dynamic BWP switching by a DCI, if dynamic waveform indication is configured for both current active BWP and target BWP which is different from current active BWP, UE first determines each field size for current active BWP in accordance with indicated waveform from dynamic waveform indication field.

Example 34 may include the method of example 21 or some other example herein, wherein in case of dynamic BWP switching by a DCI, when current active BWP is configured with dynamic waveform switching or the dynamic waveform switching field is included in the DCI, and when target BWP is not configured with dynamic waveform switching or the dynamic waveform switching field is not included in the DCI, the field size in the DCI format with BWP switching may be determined in accordance with a reference waveform in the current active BWP for the scheduled PUSCH transmission.

Example 35 may include the method of example 21 or some other example herein, wherein in case of dynamic BWP switching by a DCI, when current active and target BWP are configured with dynamic waveform switching or the dynamic waveform switching field is included in the DCI, the field size in the DCI format with BWP switching may be determined in accordance with a reference waveform in the current active BWP for the scheduled PUSCH transmission. Example 36 may include the method of example 21 or some other example herein, wherein in case of dynamic BWP switching by a DCI, when current active BWP is not configured with dynamic waveform switching or the dynamic waveform switching field is not included in the DCI, and when target BWP is configured with dynamic waveform switching or the dynamic waveform switching field is included in the DCI, the DCI field size is determined based on the configuration in current active BWP.

Example 37 may include a method of a UE, the method comprising: receiving a downlink control information (DCI) to schedule a physical downlink shared channel (PDSCH), wherein the DCI includes an indication of a waveform type for the PDSCH; and decoding the PDSCH based on the indicated waveform type.

Example 38 may include the method of example 37 or some other example herein, wherein the DCI has a DCI format with Cyclic Redundancy Check (CRC) scrambled with Cell - Radio Network Temporary Identifier (C-RNTI), CS-RNTI, and/or MCS-RNTI.

Example 39 may include the method of example 37 or some other example herein, wherein the PDSCH is a unicast PDSCH.

Example 40 may include the method of example 37-39 or some other example herein, wherein the DCI is a DCI format 1_1, a DCI format 1_2, or a DCI format for multi-cell scheduling.

Example 41 may include the method of example 37-40 or some other example herein, wherein the PDSCH is included in a Msg2, a Msg4, or a MsgB of a random access procedure.

Example 42 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-41, or any other method or process described herein.

Example 43 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-41, or any other method or process described herein.

Example 44 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-41, or any other method or process described herein.

Example 45 may include a method, technique, or process as described in or related to any of examples 1-41, or portions or parts thereof.

Example 46 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-41, or portions thereof.

Example 47 may include a signal as described in or related to any of examples 1-41, or portions or parts thereof.

Example 48 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-41, or portions or parts thereof, or otherwise described in the present disclosure.

Example 49 may include a signal encoded with data as described in or related to any of examples 1-41, or portions or parts thereof, or otherwise described in the present disclosure.

Example 50 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-41, or portions or parts thereof, or otherwise described in the present disclosure.

Example 51 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-41, or portions thereof.

Example 52 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-41, or portions thereof.

Example 53 may include a signal in a wireless network as shown and described herein.

Example 54 may include a method of communicating in a wireless network as shown and described herein.

Example 55 may include a system for providing wireless communication as shown and described herein.

Example 56 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.

3GPP Third 35 AN Access 70 BER Bit Error Ratio

Generation Network BFD Beam

Partnership AnLF Analytics Failure Detection

Project Logical Function BLER Block Error

4G Fourth ANR Automatic Rate

Generation 40 Neighbour Relation 75 BPSK Binary Phase

5G Fifth AOA Angle of Shift Keying

Generation Arrival BRAS Broadband

5GC 5G Core AP Application Remote Access network Protocol, Antenna Server

AC 45 Port, Access Point 80 BSS Business

Application API Application Support System

Client Programming Interface BS Base Station

ACR Application APN Access Point BSR Buffer Status

Context Relocation Name Report

ACK 50 ARP Allocation and 85 BW Bandwidth

Acknowledgem Retention Priority BWP Bandwidth Part ent ARQ Automatic C-RNTI Cell

ACID Repeat Request Radio Network

Application AS Access Stratum Temporary

Client Identification 55 ASP 90 Identity

ADRF Analytics Data Application Service CA Carrier

Repository Provider Aggregation,

Function Certification

AF Application ASN.1 Abstract Syntax Authority

Function 60 Notation One 95 CAPEX CAPital

AM Acknowledged AUSF Authentication Expenditure

Mode Server Function CBD Candidate

AMBR Aggregate AWGN Additive Beam Detection

Maximum Bit Rate White Gaussian CBRA Contention

AMF Access and 65 Noise 100 Based Random

Mobility BAP Backhaul Access

Management Adaptation Protocol CC Component

Function BCH Broadcast Carrier, Country Channel Code, Cryptographic 35 CM Connection C/R Checksum Management, Command/Resp

CCA Clear Channel Conditional 70 onse field bit Assessment Mandatory CRAN Cloud Radio CCE Control CMAS Commercial Access Channel Element 40 Mobile Alert Service Network, Cloud CCCH Common CMD Command RAN Control Channel CMS Cloud 75 CRB Common CE Coverage Management System Resource Block Enhancement CO Conditional CRC Cyclic CDM Content 45 Optional Redundancy Check Delivery Network CoMP Coordinated CRI Channel-State CDMA Code- Multi-Point 80 Information Division Multiple CORESET Control Resource Access Resource Set Indicator, CSI-RS

CDR Charging Data 50 COTS Commercial Resource Request Off-The-Shelf Indicator

CDR Charging Data CP Control Plane, 85 C-RNTI Cell Response Cyclic Prefix, RNTI

CFRA Contention Free Connection CS Circuit Random Access 55 Point Switched CG Cell Group CPD Connection CSCF call CGF Charging Point Descriptor 90 session control function

Gateway Function CPE Customer CSAR Cloud Service CHF Charging Premise Archive

Function 60 Equipment CSI Channel-State

CI Cell Identity CPICHCommon Pilot Information CID Cell-ID (e.g., Channel 95 CSI-IM CSI positioning method) CQI Channel Interference CIM Common Quality Indicator Measurement Information Model 65 CPU CSI processing CSI-RS CSI CIR Carrier to unit, Central Reference Signal Interference Ratio Processing Unit 100 CSI-RSRP CSI CK Cipher Key reference signal received power CSI-RSRQ CSI DMTF Distributed ECCA extended clear reference signal 35 Management Task channel received quality Force 70 assessment,

CSI-SINR CSI DPDK Data Plane extended CCA signal-to-noise and Development Kit ECCE Enhanced interference DM-RS, DMRS Control Channel ratio 40 Demodulation Element,

CSMA Carrier Sense Reference Signal 75 Enhanced CCE

Multiple Access DN Data network ED Energy

CSMA/CA CSMA DNN Data Network Detection with collision Name EDGE Enhanced avoidance 45 DNAI Data Network Datarates for GSM

CSS Common Access Identifier 80 Evolution

Search Space, Cell(GSM Evolution) specific Search DRB Data Radio EAS Edge

Space Bearer Application Server

CTF Charging 50 DRS Discovery EASID Edge

Trigger Function Reference Signal 85 Application Server

CTS Clear-to-Send DRX Discontinuous Identification

CW Codeword Reception ECS Edge

CWS Contention DSL Domain Configuration Server

Window Size 55 Specific Language. ECSP Edge

D2D Device-to- Digital 90 Computing Service

Device Subscriber Line Provider

DC Dual DSLAM DSL EDN Edge

Connectivity, Direct Access Multiplexer Data Network Current 60 DwPTS EEC Edge

DCI Downlink Downlink Pilot 95 Enabler Client

Control Time Slot EECID Edge

Information E-LAN Ethernet Enabler Client

DF Deployment Local Area Network Identification Flavour 65 E2E End-to-End EES Edge

DL Downlink EAS Edge 100 Enabler Server Application Server EESID Edge Physical FACCH Fast Enabler Server Downlink Control 70 Associated Control Identification Cannel CHannel

EHE Edge EPRE Energy per FACCH/F Fast

Hosting Environment 40 resource element Associated Control EGMF Exposure EPS Evolved Packet Channel/Full Governance System 75 rate

Management EREG enhanced REG, FACCH/H Fast Function enhanced resource Associated Control EGPRS 45 element groups Channel/Half

Enhanced ETSI European rate

GPRS Telecommunica 80 FACH Forward Access

EIR Equipment tions Standards Channel Identity Register Institute FAUSCH Fast eLAA enhanced 50 ETWS Earthquake and Uplink Signalling Licensed Assisted Tsunami Warning Channel

Access, System 85 FB Functional enhanced LAA eUICC embedded Block EM Element UICC, embedded FBI Feedback Manager 55 Universal Information eMBB Enhanced Integrated Circuit FCC Federal Mobile Card 90 Communications

Broadband E-UTRA Evolved Commission

EMS Element UTRA FCCH Frequency Management System 60 E-UTRAN Evolved Correction CHannel eNB evolved NodeB, UTRAN FDD Frequency E-UTRAN Node B EV2X Enhanced V2X 95 Division Duplex EN-DC E- F1AP Fl Application FDM Frequency UTRA-NR Dual Protocol Division Connectivity 65 Fl-C Fl Control Multiplex

EPC Evolved Packet plane interface FDM A Frequency Core Fl-U Fl User plane 100 Division Multiple EPDCCH interface Access enhanced FE Front End

PDCCH, enhanced FEC Forward Error Sistema (Engl.: 70 GTS Go To Sleep

Correction Global Navigation Signal (related

FFS For Further Satellite to WUS)

Study System) GUMMEI Globally

FFT Fast Fourier 40 gNB Next Unique MME

Transformation Generation NodeB 75 Identifier feLAA further gNB-CU gNB- GUTI Globally enhanced Licensed centralized unit, Next Unique Temporary

Assisted Generation UE Identity

Access, further 45 NodeB HARQ Hybrid ARQ, enhanced LAA centralized unit 80 Hybrid

FN Frame Number gNB-DU gNB- Automatic

FPGA Field- distributed unit, Next Repeat Request

Programmable Gate Generation HANDO Handover

Array 50 NodeB HFN HyperFrame

FR Frequency distributed unit 85 Number

Range GNSS Global HHO Hard Handover

FQDN Fully Navigation Satellite HLR Home Location

Qualified Domain System Register

Name 55 GPRS General Packet HN Home Network

G-RNTI GERAN Radio Service 90 HO Handover

Radio Network GPS I Generic HPLMN Home

Temporary Public Subscription Public Land Mobile

Identity Identifier Network

GERAN 60 GSM Global System HSDPA High

GSM EDGE for Mobile 95 Speed Downlink

RAN, GSM EDGE Communication Packet Access

Radio Access s, Groupe Special HSN Hopping

Network Mobile Sequence Number

GGSN Gateway GPRS 65 GTP GPRS HSPA High Speed

Support Node Tunneling Protocol 100 Packet Access

GLONASS GTP-UGPRS HSS Home

GLObal'naya Tunnelling Protocol Subscriber Server

NAvigatsionnay for User Plane a Sputnikovaya HSUPA High IEI Information loT Internet of Speed Uplink Packet Element Things Access Identifier IP Internet

HTTP Hyper Text IEIDL Information Protocol Transfer Protocol 40 Element 75 Ipsec IP Security,

HTTPS Hyper Identifier Data Internet Protocol

Text Transfer Protocol Length Security

Secure (https is IETF Internet IP-CAN IP- http/ 1.1 over Engineering Task Connectivity Access SSL, i.e. port 443) 45 Force 80 Network I-Block IF Infrastructure IP-M IP Multicast

Information IIOT Industrial IPv4 Internet

Block Internet of Things Protocol Version 4

ICCID Integrated IM Interference IPv6 Internet Circuit Card 50 Measurement, 85 Protocol Version 6

Identification Intermodulation IR Infrared

IAB Integrated , IP Multimedia IS In Sync Access and IMC IMS IRP Integration

Backhaul Credentials Reference Point

ICIC Inter-Cell 55 IMEI International 90 ISDN Integrated Interference Mobile Services Digital

Coordination Equipment Network

ID Identity, Identity ISIM IM Services identifier IMGI International Identity Module

IDFT Inverse Discrete 60 mobile group identity 95 ISO International Fourier IMPI IP Multimedia Organisation for

Transform Private Identity Standardisation

IE Information IMPU IP Multimedia ISP Internet Service element PUblic identity Provider

IBE In-Band 65 IMS IP Multimedia 100 IWF Interworking-

Emission Subsystem Function

IEEE Institute of IMSI International I-WLAN

Electrical and Mobile Interworking

Electronics Subscriber WLAN Engineers 70 Identity Constraint LAN Local Area LTE Long Term length of the Network Evolution convolutional LADN Local M2M Machine-to- code, USIM Area Data Network Machine

Individual key 40 LBT Listen Before 75 MAC Medium Access kB Kilobyte (1000 Talk Control bytes) LCM LifeCycle (protocol kbps kilo-bits per Management layering context) second LCR Low Chip Rate MAC Message

Kc Ciphering key 45 LCS Location 80 authentication code

Ki Individual Services (security/encryption subscriber LCID Logical context) authentication Channel ID MAC-A MAC key LI Layer Indicator used for

KPI Key 50 LLC Logical Link 85 authentication Performance Indicator Control, Low Layer and key KQI Key Quality Compatibility agreement Indicator LMF Location (TSG T WG3 context)

KSI Key Set Management Function MAC-IMAC used for Identifier 55 LOS Line of 90 data integrity of ksps kilo-symbols Sight signalling messages per second LPLMN Local (TSG T WG3 context)

KVM Kernel Virtual PLMN MANO Machine LPP LTE Management

LI Layer 1 60 Positioning Protocol 95 and Orchestration (physical layer) LSB Least MBMS Ll-RSRP Layer 1 Significant Bit Multimedia reference signal LTE Long Term Broadcast and received power Evolution Multicast

L2 Layer 2 (data 65 LWA LTE-WLAN 100 Service link layer) aggregation MBSFN

L3 Layer 3 LWIP LTE/WLAN Multimedia

(network layer) Radio Level Broadcast LAA Licensed Integration with multicast Assisted Access 70 IPsec Tunnel 105 service Single Frequency 35 MIMO Multiple Input 70 MSB Most

Network Multiple Output Significant Bit

MCC Mobile Country MLC Mobile MSC Mobile

Code Location Centre Switching Centre

MCG Master Cell MM Mobility MSI Minimum

Group 40 Management 75 System

MCOT Maximum MME Mobility Information,

Channel Management Entity MCH Scheduling

Occupancy MN Master Node Information

Time MNO Mobile MSID Mobile Station

MCS Modulation and 45 Network Operator 80 Identifier coding scheme MO Measurement MSIN Mobile Station MDAF Management Object, Mobile Identification Data Analytics Originated Number Function MPBCH MTC MSISDN Mobile

MDAS Management 50 Physical Broadcast 85 Subscriber ISDN

Data Analytics CHannel Number

Service MPDCCH MTC MT Mobile

MDT Minimization of Physical Downlink Terminated, Mobile

Drive Tests Control Termination

ME Mobile 55 CHannel 90 MTC Machine-Type

Equipment MPDSCH MTC Communication

MeNB master eNB Physical Downlink s

MER Message Error Shared MTLF Model Training

Ratio CHannel Logical

MGL Measurement 60 MPRACH MTC 95 Functions

Gap Length Physical Random mMTCmassive MTC,

MGRP Measurement Access massive

Gap Repetition CHannel Machine-Type

Period MPUSCH MTC Communication

MIB Master 65 Physical Uplink Shared 100 s

Information Block, Channel MU-MIMO Multi

Management MPLS MultiProtocol User MIMO

Information Base Label Switching

MS Mobile Station MWUS MTC 35 NFVI NFV Physical Random wake-up signal, MTC Infrastructure 70 Access CHannel

WUS NFVO NFV NPUSCH

NACK Negative Orchestrator Narrowband

Acknowledgement NG Next Physical Uplink

NAI Network 40 Generation, Next Gen Shared CHannel

Access Identifier NGEN-DC NG- 75 NPSS Narrowband

NAS Non-Access RAN E-UTRA-NR Primary

Stratum, Non- Access Dual Connectivity Synchronization

Stratum layer NM Network Signal

NCT Network 45 Manager NSSS Narrowband

Connectivity NMS Network 80 Secondary

Topology Management System Synchronization

NC-JT NonN-PoP Network Point Signal coherent Joint of Presence NR New Radio,

Transmission 50 NMIB, N-MIB Neighbour Relation

NEC Network Narrowband MIB 85 NRF NF Repository

Capability NPBCH Function

Exposure Narrowband NRS Narrowband

NE-DC NR-E- Physical Reference Signal

UTRA Dual 55 Broadcast NS Network

Connectivity CHannel 90 Service

NEF Network NPDCCH NSA Non-Standalone

Exposure Function Narrowband operation mode

NF Network Physical NSD Network

Function 60 Downlink Service Descriptor

NFP Network Control CHannel 95 NSR Network

Forwarding Path NPDSCH Service Record

NFPD Network Narrowband NSS Al Network Slice

Forwarding Path Physical Selection

Descriptor 65 Downlink Assistance

NFV Network Shared CHannel 100 Information

Functions NPRACH S-NNSAI Single-

Virtualization Narrowband NSSAI NSSF Network Slice PAR Peak to PDN Packet Data Selection Function Average Ratio Network, Public

NW Network PBCH Physical Data Network NWDAF Network Broadcast Channel PDSCH Physical

Data Analytics 40 PC Power Control, 75 Downlink Shared Function Personal Channel

NWUSNarrowband Computer PDU Protocol Data wake-up signal, PCC Primary Unit Narrowband WUS Component Carrier, PEI Permanent NZP Non-Zero 45 Primary CC 80 Equipment Power P-CSCF Proxy Identifiers

O&M Operation and CSCF PFD Packet Flow Maintenance PCell Primary Cell Description

ODU2 Optical channel PCI Physical Cell P-GW PDN Gateway Data Unit - type 2 50 ID, Physical Cell 85 PHICH Physical OFDM Orthogonal Identity hybrid-ARQ indicator Frequency Division PCEF Policy and channel Multiplexing Charging PHY Physical layer OFDMA Enforcement PLMN Public Land

Orthogonal 55 Function 90 Mobile Network

Frequency Division PCF Policy Control PIN Personal Multiple Access Function Identification Number OOB Out-of-band PCRF Policy Control PM Performance OOS Out of and Charging Rules Measurement Sync 60 Function 95 PMI Precoding

OPEX OPerating PDCP Packet Data Matrix Indicator EXpense Convergence PNF Physical

OSI Other System Protocol, Packet Network Function Information Data Convergence PNFD Physical

OSS Operations 65 Protocol layer 100 Network Function Support System PDCCH Physical Descriptor OTA over-the-air Downlink Control PNFR Physical PAPR Peak-to- Channel Network Function A verage Power PDCP Packet Data Record

Ratio 70 Convergence Protocol POC PTT over 35 PSFCH physical 70 RA-RNTI Random

Cellular sidelink feedback Access RNTI

PP, PTP Point-to- channel RAB Radio Access

Point PSCell Primary SCell Bearer, Random

PPP Point-to-Point PSS Primary Access Burst

Protocol 40 Synchronization 75 RACH Random Access

PRACH Physical Signal Channel

RACH PSTN Public Switched RADIUS Remote

PRB Physical Telephone Network Authentication Dial resource block PT-RS Phase-tracking In User Service

PRG Physical 45 reference signal 80 RAN Radio Access resource block PTT Push-to-Talk Network group PUCCH Physical RAND RANDom

ProSe Proximity Uplink Control number (used for

Services, Channel authentication)

Proximity- 50 PUSCH Physical 85 RAR Random Access

Based Service Uplink Shared Response

PRS Positioning Channel RAT Radio Access

Reference Signal QAM Quadrature Technology

PRR Packet Amplitude RAU Routing Area

Reception Radio 55 Modulation 90 Update

PS Packet Services QCI QoS class of RB Resource block,

PSBCH Physical identifier Radio Bearer

Sidelink Broadcast QCL Quasi coRBG Resource block

Channel location group

PSDCH Physical 60 QFI QoS Flow ID, 95 REG Resource

Sidelink Downlink QoS Flow Element Group

Channel Identifier Rel Release

PSCCH Physical QoS Quality of REQ REQuest

Sidelink Control Service RF Radio

Channel 65 QPSK Quadrature 100 Frequency

PSSCH Physical (Quaternary) Phase RI Rank Indicator

Sidelink Shared Shift Keying RIV Resource

Channel QZSS Quasi-Zenith indicator value

Satellite System RL Radio Link RLC Radio Link RRC Radio Resource 70 S-CSCF serving

Control, Radio Control, Radio CSCF

Link Control Resource Control S-GW Serving layer layer Gateway

RLC AM RLC 40 RRM Radio Resource S-RNTI SRNC Acknowledged Mode Management 75 Radio Network

RLC UM RLC RS Reference Temporary

Unacknowledged Signal Identity

Mode RSRP Reference S-TMSI SAE

RLF Radio Link 45 Signal Received Temporary Mobile

Failure Power 80 Station

RLM Radio Link RSRQ Reference Identifier

Monitoring Signal Received SA Standalone

RLM-RS Quality operation mode

Reference 50 RSSI Received Signal SAE System

Signal for RLM Strength 85 Architecture

RM Registration Indicator Evolution

Management RSU Road Side Unit SAP Service Access

RMC Reference RSTD Reference Point

Measurement Channel 55 Signal Time SAPD Service Access

RMSI Remaining difference 90 Point Descriptor

MSI, Remaining RTP Real Time SAPI Service Access

Minimum Protocol Point Identifier

System RTS Ready-To-Send SCC Secondary

Information 60 RTT Round Trip Component Carrier,

RN Relay Node Time 95 Secondary CC RNC Radio Network Rx Reception, SCell Secondary Cell

Controller Receiving, Receiver SCEF Service

RNL Radio Network S1AP SI Application Capability Exposure

Layer 65 Protocol Function

RNTI Radio Network SI -MME SI for 100 SC-FDMA Single

Temporary the control plane Carrier Frequency

Identifier Sl-U SI for the user Division

ROHC RObust Header plane Multiple Access

Compression SCG Secondary Cell 35 SFI Slot format 70 SMSF SMS Function

Group indication SMTC SSB-based

SCM Security SFTD Space- Measurement Timing

Context Frequency Time Configuration

Management Diversity, SFN SN Secondary

SCS Subcarrier 40 and frame timing 75 Node, Sequence

Spacing difference Number

SCTP Stream Control SFN System Frame SoC System on Chip

Transmission Number SON Self- Organizing

Protocol SgNB Secondary gNB Network

SDAP Service Data 45 SGSN Serving GPRS 80 SpCell Special Cell

Adaptation Support Node SP-CSI-RNTISemi-

Protocol, S-GW Serving Persistent CSI RNTI

Service Data Gateway SPS Semi-Persistent

Adaptation SI System Scheduling

Protocol layer 50 Information 85 SQN Sequence

SDL Supplementary SI-RNTI System number

Downlink Information RNTI SR Scheduling

SDNF Structured Data SIB System Request

Storage Network Information Block SRB Signalling

Function 55 SIM Subscriber 90 Radio Bearer

SDP Session Identity Module SRS Sounding

Description Protocol SIP Session Reference Signal

SDSF Structured Data Initiated Protocol SS Synchronization

Storage Function SiP System in Signal

SDT Small Data 60 Package 95 SSB Synchronization

Transmission SL Sidelink Signal Block

SDU Service Data SLA Service Level SSID Service Set

Unit Agreement Identifier

SEAF Security SM Session SS/PBCH Block

Anchor Function 65 Management 100 SSBRI SS/PBCH

SeNB secondary eNB SMF Session Block Resource

SEPP Security Edge Management Function Indicator,

Protection Proxy SMS Short Message Synchronization Service Signal Block Resource TA Timing 70 TMSI Temporary

Indicator Advance, Tracking Mobile

SSC Session and Area Subscriber

Service TAC Tracking Area Identity

Continuity 40 Code TNL Transport

SS-RSRP TAG Timing 75 Network Layer

Synchronization Advance Group TPC Transmit Power

Signal based TAI Control

Reference Tracking Area TPMI Transmitted

Signal Received 45 Identity Precoding Matrix

Power TAU Tracking Area 80 Indicator

SS-RSRQ Update TR Technical

Synchronization TB Transport Block Report

Signal based TBS Transport Block TRP, TRxP

Reference 50 Size Transmission

Signal Received TBD To Be Defined 85 Reception Point

Quality TCI Transmission TRS Tracking

SS-SINR Configuration Reference Signal

Synchronization Indicator TRx Transceiver

Signal based Signal 55 TCP Transmission TS Technical to Noise and Communication 90 Specifications,

Interference Ratio Protocol Technical

SSS Secondary TDD Time Division Standard

Synchronization Duplex TTI Transmission

Signal 60 TDM Time Division Time Interval

SSSG Search Space Multiplexing 95 Tx Transmission,

Set Group TDMATime Division Transmitting,

SSSIF Search Space Multiple Access Transmitter

Set Indicator TE Terminal U-RNTI UTRAN

SST Slice/Service 65 Equipment Radio Network

Types TEID Tunnel End 100 Temporary

SU-MIMO Single Point Identifier Identity

User MIMO TFT Traffic Flow UART Universal

SUL Supplementary Template Asynchronous

Uplink Receiver and USB Universal Serial VNFFG VNF Transmitter Bus Forwarding Graph UCI Uplink Control USIM Universal VNFFGD VNF Information Subscriber Identity Forwarding Graph UE User Equipment 40 Module 75 Descriptor UDM Unified Data USS UE-specific VNFMVNF Manager Management search space VoIP Voice-over- IP, UDP User Datagram UTRA UMTS Voice-over- Internet Protocol Terrestrial Radio Protocol UDSF Unstructured 45 Access 80 VPLMN Visited Data Storage Network UTRAN Public Land Mobile Function Universal Network UICC Universal Terrestrial Radio VPN Virtual Private Integrated Circuit Access Network Card 50 Network 85 VRB Virtual UL Uplink UwPTS Uplink Resource Block UM Pilot Time Slot WiMAX

Unacknowledge V2I Vehicle-to- Worldwide d Mode Infrastruction Interoperability UML Unified 55 V2P Vehicle-to- 90 for Microwave Modelling Language Pedestrian Access UMTS Universal V2V Vehicle-to- WLANWireless Local Mobile Vehicle Area Network

Telecommunica V2X Vehicle-to- WMAN Wireless tions System 60 everything 95 Metropolitan Area UP User Plane VIM Virtualized Network UPF User Plane Infrastructure Manager WPANWireless Function VL Virtual Link, Personal Area Network URI Uniform VLAN Virtual LAN, X2-C X2-Control Resource Identifier 65 Virtual Local Area 100 plane URL Uniform Network X2-U X2-User plane Resource Locator VM Virtual XML extensible URLLC UltraMachine Markup Reliable and Low VNF Virtualized Language

Latency 70 Network Function XRES EXpected user

RESponse

XOR exclusive OR

ZC Zadoff-Chu ZP Zero Power

Terminology

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

The term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment. The term “AI/ L application” or the like may be an application that contains some AI/ML models and application-level descriptions.

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 computerexecutable 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.

The term “machine learning” or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets. Although the term “ML algorithm” refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.

The term “machine learning model,” “ML model,” or the like may also refer to ML methods and concepts used by an ML-assisted solution. An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), descision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation a specific ML model could have many sub-models as components and the ML model may train all sub-models together. Separately trained ML models can also be chained together in an ML pipeline during inference. An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference). The term “ML training host” refers to an entity, such as a network function, that hosts the training of the model. The term “ML inference host” refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable). The ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution). The term “model inference information” refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.

Claims

1. An apparatus of a user equipment (UE), the apparatus comprising: processor circuitry to: receive a downlink control information (DCI) to schedule a physical downlink shared channel (PDSCH), wherein the DCI includes an indication of a waveform type for the PDSCH; and decode the PDSCH based on the indicated waveform type; and a memory to store the waveform type.

2. The apparatus of claim 1, wherein the DCI has a DCI format with cyclic redundancy check (CRC) scrambled with a cell (C)-radio Network Temporary Identifier (RNTI), configured scheduling (CS)-RNTI, and/or modulation and coding scheme (MCS)-RNTI.

3. The apparatus of claim 1, wherein the DCI is a DCI format 1_1, a DCI format 1_2, a DCI format l_0, or a DCI format for multi-cell scheduling.

4. The apparatus of claim 1, wherein the PDSCH corresponds to a Msg2, a Msg4, or a MsgB of a random access procedure.

5. The apparatus of claim 4, wherein the waveform type is a first waveform type, and wherein the processor circuitry is further to encode, for transmission, a Msgl, a Msg3, a MsgA physical random access channel (PRACH), or a MsgA PUSCH of the random access procedure, wherein the Msgl, the Msg3, the MsgA PRACH, or the MsgA PUSCH includes a request for the waveform type.

6. The apparatus of claim 5, wherein the waveform type is a first waveform type, wherein the Msgl, the Msg3, or the MsgA is transmitted in PRACH resources associated with a second waveform type that is different than the first waveform type, and wherein the Msg2, the Msg4, or the MsgB is received based on the second waveform type.

7. The apparatus of any one of claims 1-6, wherein the waveform type is indicated from among a plurality of supported waveform types that include two or more of: cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM), discrete Fourier Transform (DFT)- spread (s)-OFDM, or single carrier (SC)-frequency domain equalization (FDE)-OFDM.

8. The apparatus of any one of claims 1-6, wherein the waveform type is indicated from among a plurality of supported waveform types, and wherein the DCI includes fields or a DCI format that are size matched based on the supported waveform types.

9. The apparatus of any one of claims 1-6, wherein the DCI is to schedule multiple PDSCHs to carry different transport blocks in a cell, and wherein the DCI includes a single field with the indication of the waveform type that is to apply to the multiple PDSCHs.

10. One or more computer-readable media having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE) configure the UE to: identify a first set of physical random access channel (PRACH) resources that are associated with a first waveform type and a second set of PRACH resources that are associated with a second waveform type; encode a first random access message for transmission on a selected one of the first or second set of PRACH resources; and decode a second random access message based on the respective first or second waveform type that is associated with the selected first or second set of PRACH resources.

11. The one or more computer-readable media of claim 10, wherein the first random access message includes a request for a waveform type to be used for a physical downlink shared channel (PDSCH).

12. The one or more computer-readable media of claim 11, wherein the second random access message includes an indication of the waveform type to be used for the PDSCH.

13. The one or more computer-readable media of claim 10, wherein the first and second sets of PRACH resources are included in separate PRACH occasions or same PRACH occasions with different PRACH preambles.

14. The one or more computer-readable media of any one of claims 10-13, wherein the first random access message is a PRACH preamble, a Msg3, a MsgA PRACH, or a MsgA physical uplink shared channel (PUSCH) of a random access procedure, and the second random access message is a Msg2, a Msg4, or a MsgB of the random access procedure.

15. One or more computer-readable media having instructions, stored thereon, that when executed by one or more processors of a next generation Node B (gNB) configure the gNB to: encode, for transmission to a user equipment (UE), downlink control information (DCI) to schedule a physical downlink shared channel (PDSCH), wherein the DCI includes an indication of a waveform type for the PDSCH; and encode the PDSCH for transmission based on the indicated waveform type.

16. The one or more computer-readable media of claim 15, wherein the DCI has a cyclic redundancy check (CRC) scrambled with a cell (C)-radio Network Temporary Identifier (RNTI), configured scheduling (CS)-RNTI, and/or modulation and coding scheme (MCS)- RNTI, and wherein the DCI is a DCI format 1_1, a DCI format 1_2, a DCI format l_0, or a DCI format for multi-cell scheduling.

17. The one or more computer-readable media of claim 15, wherein the PDSCH is included in a message of a random access procedure.

18. The one or more computer-readable media of claim 17, wherein the message is a first message, and wherein the instructions, when executed, further configure the gNB to: receive, from the UE, a second message of the random access procedure, wherein the second message includes a request for the waveform type.

19. The one or more computer-readable media of claim 18, wherein the waveform type is a first waveform type, wherein the second message is received in PRACH resources associated with a second waveform type that is different than the first waveform type, and wherein the DCI is encoded based on the second waveform type.

20. The one or more computer-readable media of any one of claims 15-19, wherein the waveform type is indicated from among a plurality of supported waveform types that include two or more of: cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM), discrete Fourier Transform (DFT)-spread (s)-OFDM, or single carrier (SC)-frequency domain equalization (FDE)-OFDM.