IN NR (NEW RADIO)

REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No.

62/444,195 filed January 9, 2017, entitled "UL BANDWIDTH ADAPTATION AND MULTI-SUBBAND OPERATION IN NR", the contents of which are herein incorporated by reference in their entirety.

FIELD

[0002] The present disclosure relates to wireless technology, and more specifically to techniques for employing bandwidth adaptation and multi-BW (bandwidth) part operation in connection with NR (New Radio) UL (Uplink).

BACKGROUND

[0003] Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR), will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network/system that target to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multidimensional goals are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich contents and services.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 is a block diagram illustrating an example user equipment (UE) useable in connection with various aspects described herein.

[0005] FIG. 2 is a diagram illustrating example components of a device that can be employed in accordance with various aspects discussed herein.

[0006] FIG. 3 is a diagram illustrating example interfaces of baseband circuitry that can be employed in accordance with various aspects discussed herein. [0007] FIG. 4 is a block diagram illustrating a system employable at a UE (User Equipment) that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission, according to various aspects described herein.

[0008] FIG. 5 is a block diagram illustrating a system employable at a BS (Base Station) that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission(s) from one or more UEs (User

Equipments), according to various aspects described herein.

[0009] FIG. 6 is a diagram illustrating an example of NR PUCCH (Physical Uplink Control Channel) with short and long duration within UL (Uplink) data slot, according to various aspects discussed herein.

[0010] FIG. 7 is a pair of diagrams illustrating an example of the UL data and control channels configured with different RF bandwidths, according to various aspects discussed herein.

[0011] FIG. 8 is a pair of diagrams illustrating an example wherein RF bandwidth can be the same or different for the UL control channel with short and long duration, respectively, according to various aspects discussed herein.

[0012] FIG. 9 is a diagram illustrating one example of a time gap between the UL control and data channels, according to various aspects discussed herein.

[0013] FIG. 10 is a diagram illustrating one example scenario wherein the UE can drop the UL control channel in the last symbol within one slot, according to various aspects discussed herein.

[0014] FIG. 11 is a diagram illustrating one example of a UL data multiplexed with a

UL control channel with long duration, according to various aspects described herein.

[0015] FIG. 12 is a diagram illustrating one example of four bandwidth parts within a system bandwidth, in connection with various aspects discussed herein.

[0016] FIG. 13 is a diagram illustrating one example of frequency hopping in two configured BW parts in four consecutive slots, according to various aspects discussed herein.

[0017] FIG. 14 is a diagram illustrating one example of a frequency hopping pattern across multiple BW parts for URLLC uplink data transmission, according to various aspects discussed herein.

[0018] FIG. 15 is a flow diagram of an example method employable at a UE that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission, according to various aspects described herein, according to various aspects discussed herein.

[0019] FIG. 16 is a flow diagram of an example method employable at a BS that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission(s) from one or more UEs (User Equipments).

DETAILED DESCRIPTION

[0020] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms "component," "system," "interface," and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user equipment (e.g., mobile phone, etc.) with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more."

[0021] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).

[0022] As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.

[0023] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "including", "includes", "having", "has", "with", or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term

"comprising." Additionally, in situations wherein one or more numbered items are discussed (e.g., a "first X", a "second X", etc.), in general the one or more numbered items may be distinct or they may be the same, although in some situations the context may indicate that they are distinct or that they are the same.

[0024] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0025] Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. FIG. 1 illustrates an architecture of a system 1 00 of a network in accordance with some embodiments. The system 100 is shown to include a user equipment (UE) 101 and a UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface. [0026] In some embodiments, any of the UEs 101 and 102 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network describes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0027] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1 10— the RAN 1 10 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0028] In this embodiment, the UEs 101 and 1 02 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

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

[0030] The RAN 1 1 0 can include one or more access nodes that enable the connections 1 03 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 1 1 0 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1 1 1 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1 12.

[0031] Any of the RAN nodes 1 1 1 and 1 12 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some embodiments, any of the RAN nodes 1 1 1 and 1 12 can fulfill various logical functions for the RAN 1 1 0 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0032] In accordance with some embodiments, the UEs 101 and 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1 1 1 and 1 1 2 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0033] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1 1 1 and 1 12 to the UEs 101 and 1 02, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0034] The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs 101 and 102. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 1 1 1 and 1 12 based on channel quality information fed back from any of the UEs 101 and 102. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 1 02.

[0035] The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1 , 2, 4, or 8).

[0036] Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

[0037] The RAN 1 1 0 is shown to be communicatively coupled to a core network (CN) 1 20— via an S1 interface 1 1 3. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface 1 13 is split into two parts: the S1 -U interface 1 14, which carries traffic data between the RAN nodes 1 1 1 and 1 12 and the serving gateway (S-GW) 122, and the S1 -mobility management entity (MME) interface 1 15, which is a signaling interface between the RAN nodes 1 1 1 and 1 12 and MMEs 121 .

[0038] In this embodiment, the CN 1 20 comprises the MMEs 121 , the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of

communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

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

[0040] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 123 and external networks such as a network including the application server 130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 123 is shown to be communicatively coupled to an application server 130 via an IP communications interface 125. The application server 130 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1 01 and 102 via the CN 120.

[0041] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 130 via the P-GW 123. The application server 130 may signal the PCRF 126 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 126 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 130.

[0042] FIG. 2 illustrates example components of a device 200 in accordance with some embodiments. In some embodiments, the device 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 21 0, and power management circuitry (PMC) 21 2 coupled together at least as shown. The components of the illustrated device 200 may be included in a UE or a RAN node. In some embodiments, the device 200 may include less elements (e.g., a RAN node may not utilize application circuitry 202, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[0043] The application circuitry 202 may include one or more application processors. For example, the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 200. In some embodiments, processors of application circuitry 202 may process IP data packets received from an EPC.

[0044] The baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206. Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206. For example, in some embodiments, the baseband circuitry 204 may include a third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processor(s) 204D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g., one or more of baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. In other embodiments, some or all of the functionality of baseband processors 204A-D may be included in modules stored in the memory 204G and executed via a Central Processing Unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 204 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments,

encoding/decoding circuitry of the baseband circuitry 204 may include convolution, tail- biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0045] In some embodiments, the baseband circuitry 204 may include one or more audio digital signal processor(s) (DSP) 204F. The audio DSP(s) 204F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 204 and the application circuitry 202 may be implemented together such as, for example, on a system on a chip (SOC).

[0046] In some embodiments, the baseband circuitry 204 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 204 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0047] RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204. RF circuitry 206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.

[0048] In some embodiments, the receive signal path of the RF circuitry 206 may include mixer circuitry 206a, amplifier circuitry 206b and filter circuitry 206c. In some embodiments, the transmit signal path of the RF circuitry 206 may include filter circuitry 206c and mixer circuitry 206a. RF circuitry 206 may also include synthesizer circuitry 206d for synthesizing a frequency for use by the mixer circuitry 206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 206a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d. The amplifier circuitry 206b may be configured to amplify the down- converted signals and the filter circuitry 206c may be a low-pass filter (LPF) or bandpass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 204 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 206a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0049] In some embodiments, the mixer circuitry 206a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206d to generate RF output signals for the FEM circuitry 208. The baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206c.

[0050] In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may be configured for super-heterodyne operation.

[0051] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.

[0052] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the

embodiments is not limited in this respect.

[0053] In some embodiments, the synthesizer circuitry 206d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 206d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0054] The synthesizer circuitry 206d may be configured to synthesize an output frequency for use by the mixer circuitry 206a of the RF circuitry 206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 206d may be a fractional N/N+1 synthesizer.

[0055] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 204 or the applications processor 202 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 202.

[0056] Synthesizer circuitry 206d of the RF circuitry 206 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0057] In some embodiments, synthesizer circuitry 206d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 206 may include an IQ/polar converter.

[0058] FEM circuitry 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing. FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 21 0. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 206, solely in the FEM 208, or in both the RF circuitry 206 and the FEM 208.

[0059] In some embodiments, the FEM circuitry 208 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 21 0).

[0060] In some embodiments, the PMC 212 may manage power provided to the baseband circuitry 204. In particular, the PMC 21 2 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 212 may often be included when the device 200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 21 2 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation

characteristics.

[0061] While FIG. 2 shows the PMC 212 coupled only with the baseband circuitry 204. However, in other embodiments, the PMC 2 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208.

[0062] In some embodiments, the PMC 212 may control, or otherwise be part of, various power saving mechanisms of the device 200. For example, if the device 200 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 200 may power down for brief intervals of time and thus save power.

[0063] If there is no data traffic activity for an extended period of time, then the device 200 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 200 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state. [0064] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[0065] Processors of the application circuitry 202 and processors of the baseband circuitry 204 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 204, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 204 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[0066] FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 204 of FIG. 2 may comprise processors 204A-204E and a memory 204G utilized by said processors. Each of the processors 204A-204E may include a memory interface, 304A-304E,

respectively, to send/receive data to/from the memory 204G.

[0067] The baseband circuitry 204 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 312 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 204), an application circuitry interface 314 (e.g., an interface to send/receive data to/from the application circuitry 202 of FIG. 2), an RF circuitry interface 316 (e.g., an interface to send/receive data to/from RF circuitry 206 of FIG. 2), a wireless hardware connectivity interface 31 8 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 320 (e.g., an interface to send/receive power or control signals to/from the PMC 212).

[0068] Referring to FIG. 4, illustrated is a block diagram of a system 400 employable at a UE (User Equipment) that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission, according to various aspects described herein. System 400 can include one or more processors 410 (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with FIG. 2 and/or FIG. 3) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection with FIG. 3), transceiver circuitry 420 (e.g., comprising part or all of RF circuitry 206, which can comprise transmitter circuitry (e.g., associated with one or more transmit chains) and/or receiver circuitry (e.g., associated with one or more receive chains) that can employ common circuit elements, distinct circuit elements, or a combination thereof), and a memory 430 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s) 410 or transceiver circuitry 420). In various aspects, system 400 can be included within a user equipment (UE). As described in greater detail below, system 400 can facilitate configuration for transmission of NR UL transmission(s) involving one or more of bandwidth adaptation and/or frequency hopping on multiple BW parts.

[0069] In various aspects discussed herein, signals and/or messages can be generated and output for transmission, and/or transmitted messages can be received and processed. Depending on the type of signal or message generated, outputting for transmission (e.g., by processor(s) 410, processor(s) 510, etc.) can comprise one or more of the following: generating a set of associated bits that indicate the content of the signal or message, coding (e.g., which can include adding a cyclic redundancy check (CRC) and/or coding via one or more of turbo code, low density parity-check (LDPC) code, tailbiting convolution code (TBCC), etc.), scrambling (e.g., based on a scrambling seed), modulating (e.g., via one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.), and/or resource mapping (e.g., to a scheduled set of resources, to a set of time and frequency resources granted for uplink transmission, etc.). Depending on the type of received signal or message, processing (e.g., by processor(s) 410, processor(s) 51 0, etc.) can comprise one or more of: identifying physical resources associated with the signal/message, detecting the signal/message, resource element group deinterleaving, demodulation, descrambling, and/or decoding.

[0070] Referring to FIG. 5, illustrated is a block diagram of a system 500 employable at a BS (Base Station) that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission(s) from one or more UEs (User Equipments), according to various aspects described herein. System 500 can include one or more processors 510 (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with FIG. 2 and/or FIG. 3) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection with FIG. 3), communication circuitry 520 (e.g., which can comprise circuitry for one or more wired (e.g., X2, etc.) connections and/or part or all of RF circuitry 206, which can comprise one or more of transmitter circuitry (e.g., associated with one or more transmit chains) or receiver circuitry (e.g., associated with one or more receive chains), wherein the transmitter circuitry and receiver circuitry can employ common circuit elements, distinct circuit elements, or a combination thereof), and memory 530 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s) 510 or communication circuitry 520). In various aspects, system 500 can be included within an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (Evolved Node B, eNodeB, or eNB), next generation Node B (gNodeB or gNB) or other base station or TRP (Transmit/Receive Point) in a wireless communications network. In some aspects, the processor(s) 510, communication circuitry 520, and the memory 530 can be included in a single device, while in other aspects, they can be included in different devices, such as part of a distributed architecture. As described in greater detail below, system 500 can facilitate configuration of UE(s) for transmission of NR UL

transmission(s) involving one or more of bandwidth adaptation and/or frequency hopping on multiple BW parts.

[0071] As agreed in the RAN 1 (RAN (Radio Access Network) WG1 (Working Group 1 )) #86bis meeting, NR (New Radio) supports physical uplink control channel (NR PUCCH) with short and long duration. Referring to FIG. 6, illustrated is one example of NR PUCCH with short and long duration within UL (Uplink) data slot, according to various aspects discussed herein. For NR PUCCH with short duration, NR PUCCH and PUSCH (Physical Uplink Shared Channel) can be multiplexed in a time division multiplexing (TDM) manner, which can be targeted for low latency application. For NR PUCCH with long duration, multiple OFDM (Orthogonal Frequency Division

Multiplexing) symbols can be allocated for NR PUCCH to improve link budget and uplink coverage for control channel. More specifically, for UL data slot, NR PUCCH and PUSCH can be multiplexed in a frequency division multiplexing (FDM) fashion. In FIG. 6, in order to accommodate the DL (Downlink) to UL and UL to DL switching time and round-trip propagation delay, a guard period (GP) is inserted between NR physical downlink shared channel (NR PDSCH) and NR physical uplink control channel (NR PUCCH) as well as NR physical downlink control channel (NR PDCCH) and NR physical uplink shared channel (NR PUSCH).

[0072] At the RAN1 #86bis meeting, the following agreement was made with regard to RF bandwidth adaptation for DL transmission (including portions FFS (For Further Study)):

• At least for single carrier operation, NR should allow a UE to operate in a way where it receives at least downlink control information in a first RF bandwidth and where the UE is not expected to receive in a second RF bandwidth that is larger than the first RF bandwidth within less than X με (FFS: value of X)

o FFS the first RF bandwidth is within the second RF bandwidth

^■ FFS the first RF bandwidth is at the center of the second RF

bandwidth

o FFS the maximal ratio of the first RF bandwidth over the second RF

bandwidth

o FFS detailed mechanism

• FFS RF bandwidth adaptation for RRM measurement

[0073] In aspects, RF (Radio Frequency) bandwidth adaptation can also be applied for the UL transmission. As one example, an UL control channel (e.g., generated by processor(s) 410) can be transmitted (e.g., via transceiver circuitry 420) using a relatively narrow RF bandwidth, which can help to reduce transmit complexity and UE power consumption. As another example, an UL data channel (e.g., NR (New Radio) PUSCH (Physical Uplink Shared Channel), which can be generated by processor(s) 41 0) can be transmitted (e.g., via transceiver circuitry 420) using a wider RF bandwidth, in order to achieve higher peak data rate. In various aspects discussed herein, certain mechanisms and techniques can be defined to efficiently switch different RF bandwidths for the transmission of UL control channel (e.g., NR PUCCH (Physical Uplink Control Channel) and UL data channel (e.g., both of which can be generated by processor(s) 41 0, transmitted via transceiver circuitry 420, received via communication circuitry 520, and processed by processor(s) 510).

[0074] Additionally, depending on UE (User Equipment) capability, multiple BW (Bandwidth) parts within a wide system bandwidth can be configured for one UE. In such scenarios, the UE can perform frequency hopping across multiple BW parts (e.g., via processor(s) 410 and transceiver circuitry 420) to exploit the benefit of frequency diversity. Thus, in aspects, certain frequency hopping mechanisms for DL or UL transmission defined herein can be employed. [0075] In various embodiments, mechanisms and techniques for UL RF bandwidth adaptation and multi-BW part operation discussed herein can be employed. For example, these mechanisms can comprise: (a) Mechanisms for bandwidth adaptation for UL transmission and (b) Frequency hopping mechanisms for multiple BW part operation.

Mechanisms for Bandwidth Adaptation for UL Transmission

[0076] As discussed above, a BS (Base Station, e.g., gNB (next generation Node B) can configure (e.g., via configuration signaling (e.g., higher layer signaling) generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) different RF bandwidths for the transmission of the UL control and data channels. For example, for the UL control channel, a narrower RF bandwidth can be configured (e.g., via configuration signaling generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) to reduce transmit complexity and UE power consumption, while for the UL data channel, a wider RF bandwidth can be configured (e.g., generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) to achieve a higher peak data rate. Referring to FIG. 7, illustrated is a pair of diagrams showing an example of the UL data and control channels configured with different RF bandwidths, according to various aspects discussed herein.

[0077] As discussed above, NR can support a UL control channel with short and/or long duration. Referring to FIG. 8, illustrated is a pair of diagrams showing that RF bandwidth can be the same or different for the UL control channel with short and long duration, respectively, according to various aspects discussed herein. In various aspects, the RF bandwidth for UL control channel with short and long duration can be partially overlapping, fully overlapping or disjoint. In various aspects, the BS (e.g., gNB, etc.) can configure (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) a wider RF bandwidth for the UL control channel with long duration, which can help to exploit the benefit of frequency diversity when frequency hopping is employed (e.g., by processor(s) 410 and transceiver circuitry 420).

[0078] In various aspects, mechanisms discussed below can be employed for bandwidth adaptations of UL control and data channel transmission. Various

embodiments can also apply to cases wherein a single UL RF bandwidth is configured (e.g., generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410), in which the transmission BWs of data and control can be different and also can be located in different frequency regions.

[0079] In various aspects, when the RF bandwidth for the UL control channel is located within the RF bandwidth for UL data channel, the UE can transmit (e.g., via transceiver circuitry 420) the UL control channel (e.g., generated by processor(s) 410) using the RF bandwidth for the UL data channel. In aspects, a similar technique can be applied for scenarios wherein the UL control channel and UL data channel are multiplexed (e.g., by processor(s) 410 and processor(s) 510) in a FDM manner in the last symbol(s) within one slot.

[0080] In various aspects, when the RF bandwidth for UL control channel is located outside the RF bandwidth allocated for UL data channel, the UE can employ a larger RF bandwidth to transmit (e.g., via transceiver circuitry 420) both the UL control channel and data channel (e.g., generated by processor(s) 410). The larger RF bandwidth can be a combination of the RF bandwidths used for both the UL control channel and data channel.

[0081] In various aspects, when the RF bandwidth for the UL control channel is located outside the RF bandwidth allocated for the UL data channel and when the time gap between the UL control and data channels is larger than the UE switching time, the UE can transmit (e.g., via transceiver circuitry 420) the UL control channel (e.g., generated by processor(s) 410) using the RF bandwidth allocated for the UL control channel. As mentioned above, this can be also applied for the case when a single UL RF bandwidth is configured, and the transmission BWs of the UL data and control channels can be different and can be located in different frequency regions.

[0082] Referring to FIG. 9, illustrated is a diagram showing one example of a time gap between the UL control and data channels, according to various aspects discussed herein. In the scenario shown in FIG. 9, given that the gap is greater than UE RF bandwidth switching time, the UE can transmit (e.g., via transceiver circuitry 420) the UL control channel (e.g., generated by processor(s) 410) using the RF bandwidth allocated for the UL control channel. In various aspects, depending on the UE capability and/or RF bandwidth, the switching time can be different or can be defined in a UE-specific manner.

[0083] In various aspects, when the RF bandwidth for the UL control channel is located outside the RF bandwidth allocated for UL data channel, the UE can drop (e.g., via processor(s) 410) one of the UL control or data channels depending on the priority of the UL data and control channels.

[0084] Referring to FIG. 10, illustrated is a diagram showing one example scenario wherein the UE can drop (e.g., via processor(s) 41 0) the UL control channel in the last symbol within one slot, according to various aspects discussed herein. In the example of FIG. 10, there is no gap between the UL data and control channels, and the UL control RF bandwidth for short duration is outside the RF bandwidth for the UL data channel, in such a scenario, the UE can drop (e.g., via processor(s) 410) the UL control channel in the last symbol.

[0085] The techniques and mechanisms discussed above can be extended in a similar manner to scenarios involving the UL data channel and the UL control channel with long duration. In one example, when the RF bandwidth for the UL control channel with long duration is located outside the RF bandwidth for the UL data channel, the UE can employ (e.g., via processor(s) 41 0 and transceiver circuitry 420) a larger RF bandwidth or drop (e.g., via processor(s) 410) one of the UL control or data channels.

[0086] In another example, when the RF bandwidth for the UL control channel with long duration is located within the RF bandwidth for the UL data channel, and simultaneous transmission of UL control and data channel is supported, the UE can transmit (e.g., via transceiver circuitry 420) the UL control channel with long duration (e.g., generated by processor(s) 41 0) in the configured resource. Additionally, in aspects, the UL data channel (e.g., generated by processor(s) 410) can puncture or rate match around the resource allocated for the UL control channel with long duration. Referring to FIG. 11 , illustrated is a diagram showing an example of a UL data channel (e.g., generated by processor(s) 41 0) multiplexed (e.g., by processor(s) 410 and transceiver circuitry 420) with a UL control channel with long duration (e.g., generated by processor(s) 41 0), according to various aspects described herein.

[0087] Alternatively, in scenarios wherein the UE multiplexes (e.g., via processor(s) 41 0 and transceiver circuitry 420) the UL data channel (e.g., generated by processor(s) 41 0) with the UL control channel with long duration (e.g., generated by processor(s) 41 0), the UL control channel can be embedded in the UL data channel (e.g., by processor(s) 410 and transceiver circuitry 420) using the same mechanism that uplink control information (UCI) is piggybacked on the UL data channel.

Frequency Hopping Mechanisms for Multiple Bandwidth Part Operation [0088] In aspects, a wide system bandwidth can be divided into multiple BW

(bandwidth) parts. Referring to FIG. 12, illustrated is a diagram showing an example of four bandwidth parts within a system bandwidth, in connection with various aspects discussed herein. In various aspects, the sizes of the BW parts can be the same or different, and can vary across different mini-slots, slots, subframes, or frames, depending on configuration or applications.

[0089] Depending on the UE capability for wide bandwidth support, the UE can be configured (e.g., via configuration signaling generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 41 0) with multiple BW parts within the wide bandwidth. In such scenarios, the UE can perform frequency hopping across multiple BW parts (e.g., via processor(s) 410 and transceiver circuitry 420) to exploit the benefit of frequency diversity. The aggregate BW of the BW parts can be wider than the UE's BW capability, and the UL RF center frequency can change over time (e.g., symbols, mini-slots, slots, subframes, frames, etc.), depending on the scheduled BW part for data and/or control transmission. In one example, the system BW is 100 MHz, the UE's UL BW capability is 20 MHz and each BW part is 20 MHz. In one scenario involving the example, the UE can be configured within a specific 20 MHz BW part only, and its UL transmission (e.g., generated by processor(s) 410, transmitted via transceiver circuitry 420, received via communication circuitry 520, and processed by processor(s) 510) can be limited within the BW part. In another operation scenario, the UE can be scheduled on any BW part by changing the Tx (Transmit) RF frequency over time depending on scheduling of UL data and/or control (e.g., via DCI (Downlink Control Information) generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410). Also, the configured candidate UL control channel resources can be scattered over multiple BW parts within the system bandwidth (100 MHz per the example, or other applicable BW in other embodiments) for load balancing and flexible use of the resources. In this scenario, all the BW parts can be contained within the system bandwidth of a single RF carrier in the network.

However, from a UE perspective, each BW part can be considered as a component carrier as in carrier aggregation operations.

[0090] When scheduling the transmission of DL or UL data channel or UL control channel (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410), the BW part index can be available at UE side. In various aspects, the BW part index can be configured by higher layers (e.g., via RRC signaling), dynamically indicated in the downlink control information (DCI), or via a combination of the two. In various aspects, a set of BW part indexes can be configured by RRC signaling, while one field in the DCI can be used to indicate which one BW part from the set of BW parts to use for data or control channel transmission (e.g., generated by processor(s) 410, transmitted via transceiver circuitry 420, received via communication circuitry 520, and processed by processor(s) 510). In various aspects, the field in the DCI containing BW part information can also include the resource allocation within the configured BW part. In some such aspects, a single field in the DCI can be used to determine the BW part index and resource within the BW part for data or control channel transmission.

[0091] In various aspects, frequency hopping can be enabled or disabled by the BS (e.g., gNB). Whether to enable or disable frequency hopping can be semi-statically configured by higher layers or dynamically indicated in the DCI (e.g., via higher layer or DCI signaling generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410).

[0092] In various aspects, frequency hopping with multiple BW part operation can be applied for one or more of the following cases: (a) UL control channel with multiple slot duration; (b) DL/UL data channel transmission within aggregated slot(s); (c) Semi- persistent DL/UL data channel transmission; (d) UL data transmission without dynamic grant for Ultra-Reliable and Low Latency Communication (URLLC).

[0093] In various aspects, one or more of the following frequency hopping techniques and/or mechanisms can be applied for multiple BW part operation.

[0094] In some aspects, two BW parts can be configured for one or more UEs via higher layer signaling, for example, NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI) or radio resource control (RRC) signaling (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 41 0). Additionally, in aspects, frequency hopping can be performed (e.g., via processor(s) 410 and transceiver circuitry 420) across these two configured BW parts for DL or UL transmission. The frequency resource in different BW parts can be the same or different.

[0095] In various aspects, the DL or UL channel (e.g., generated by processor(s) 51 0 or processor(s) 410, respectively) can be transmitted (e.g., via communication circuitry 520 or transceiver circuitry 420, respectively) in the same BW part in K consecutive slots. In such aspects, the DL or UL channel can be switched (e.g., by processor(s) 510 and communication circuitry 520 or by processor(s) 410 and transceiver circuitry 420, respectively) to another BW part for frequency hopping. The value K can be predefined in the specification, can be configured by higher layers via NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI) or radio resource control (RRC) signaling (e.g., generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) or can be defined as a function of the number of mini-slots or slots used for the DL or UL

Nslot

transmission. In the last case, K can be defined as K = or K = where N _slot

is the number of slots used for DL or UL transmission.

[0096] In scenarios wherein frequency hopping is applied on consecutive slots, a gap can be reserved to allow the BS (e.g., gNB) or UE to switch (e.g., by processor(s) 510 and communication circuitry 520 or by processor(s) 410 and transceiver circuitry 420, respectively) from a first BW part to a second BW part. Referring to FIG. 13, illustrated is a diagram showing one example of frequency hopping in two configured BW parts in four consecutive slots, according to various aspects discussed herein. In the example of FIG. 13, the UE can be configured (e.g., via configuration signaling (e.g., MSI, RMSI, OSI, RRC, etc.) generated by processor(s) 510, transmitted via

communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) with BW parts #0 and #3 for frequency hopping (e.g., by processor(s) 410 and transceiver circuitry 420). Additionally, assuming, as an example, 2 OFDM (or OFDM-based) symbols as the switching time for BW part based frequency hopping, the last symbol in slot #(n+1 ) and the first symbol in slot #(n+2) can be reserved for the gap (in other scenarios, the UE can switch in a greater or lesser number of symbols, depending on UE capabilities and/or configuration). In various aspects, in scenarios involving a dynamic TDD system, the DL control region and guard period can be reserved for the gap for switching time.

[0097] As discussed above, depending on UE capability or RF bandwidth, the switching time can be different or can be defined in a UE-specific manner. Similarly, the number of symbols reserved for gap can be configured by higher layers via RRC signaling or dynamically indicated in the DCI or a combination thereof (e.g., generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410). In one example, if the UE can switch (e.g., via processor(s) 410 and transceiver circuitry 420) the BW part within 1 symbol, the UE can omit transmission of the signal in the last symbol in a first BW part before it switches to a second BW part.

[0098] In various aspects, a frequency hopping pattern across multiple BW parts can be defined as a function of one or more of the following parameters: physical or virtual cell ID, UE ID (e.g., Cell Radio Network Temporary Identifier (C-RNTI), etc.), symbol or slot or mini-slot or subframe or frame index, and/or a parameter which can be indicated in the DCI (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410).

[0099] In one example, assuming N _SB BW parts in the system bandwidth, the BW part index for DL or UL transmission can be derived (e.g., by processor(s) 410 and/or processor(s) 510) as in equation (1 ):

ISB = /(¾, n _s )modJV _SB

Where mod is the modulo operation, N^ _a is the physical cell ID, and n _s is the mini-slot or slot index.

[00100] In various aspects, this frequency hopping mechanism can be further applied (e.g., by processor(s) 410 and transceiver circuitry 420) for grant-free uplink data transmission for URLLC. In this case, the BW part index for the retransmission without dynamic grant from the BS (e.g., gNB, etc.) can be derived (e.g., by processor(s) 410 and/or processor(s) 510) from one or more of the following parameters: physical or virtual cell ID, UE ID (e.g., Cell Radio Network Temporary Identifier (C-RNTI), etc.), symbol or slot or mini-slot or subframe or frame index, and/or BW part index for the initial transmission. In one example, the BW part index for a kth retransmission can be derived (e.g., by processor(s) 410 and/or processor(s) 510) as in equation (2):

= f(N _l , n _s , I _SB (0))modN _SB

[00101 ] Referring to FIG. 14, illustrated is a diagram showing one example of a frequency hopping pattern across multiple BW parts for URLLC uplink data

transmission, according to various aspects discussed herein. In the example of FIG. 14, assuming a BW part for a first transmission is configured by higher layers in a UE- specific manner (e.g., via configuration signaling generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410), the frequency hopping pattern for transmission (e.g., via transceiver circuitry 420) of URLLC uplink data (e.g., generated by processor(s) 41 0) can be aligned at the UE and the BS (e.g., gNB, etc.) (e.g., via processor(s) 410 and transceiver circuitry 420, and processor(s) 510 and communication circuitry 520) to allow the BS (e.g., gNB, etc.) to perform soft combining at the receiver (e.g., via processor(s) 510 and communication circuitry 520) to improve the performance.

Although in the example of FIG. 14, a 1 symbol gap time is reserved for UE to switch from one BW part to another, in various aspects (e.g., depending on UE capabilities and/or configuration), this can vary.

[00102] In various aspects, a frequency hopping pattern across multiple BW parts can be configured by higher layers via MSI, RMSI, OSI, RRC signaling or dynamically indicated in the DCI or a combination thereof (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410). In the latter case, a set of frequency hopping patterns across multiple BW parts can be configured by higher layers via RRC signaling, while one field in DCI can be used to indicate which frequency hopping pattern among the set of frequency hopping patterns to apply for the transmission (e.g., via communication circuitry 520 or transceiver circuitry 420, respectively) of DL or UL channels (e.g., generated by processor(s) 510 or processor(s) 41 0, respectively).

[00103] The DCI carried by the NR physical downlink control channel (NR PDCCH) (e.g., generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) can be used to schedule transmission(s) (e.g., via communication circuitry 520 or transceiver circuitry 420, respectively) of the DL or UL data channel (e.g., generated by

processor(s) 510 or processor(s) 410, respectively) spanning multiple slots, or to semi- persistently schedule transmission(s) (e.g., via communication circuitry 520 or transceiver circuitry 420, respectively) of the DL or UL data channel (e.g., generated by processor(s) 510 or processor(s) 410, respectively) or to schedule transmission(s) (e.g., via transceiver circuitry 420) of the UL control channel (e.g., generated by processor(s) 41 0) with multiple slot duration.

Additional Embodiments

[00104] Referring to FIG. 15, illustrated is a flow diagram of an example method 1 500 employable at a UE that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission, according to various aspects described herein, according to various aspects discussed herein. In other aspects, a machine readable medium can store instructions associated with method 1500 that, when executed, can cause a UE to perform the acts of method 1500.

[00105] At 1510, configuration signaling can be received configuring one or more BWs and/or one or more BW parts for at least one of a UL data channel or a UL control channel, wherein the configuration signaling can optionally configure frequency hopping in connection with the UL data channel and/or a UL control channel.

[00106] At 1520, the UL data channel and/or the UL control channel can be transmitted based on the configuration signaling.

[00107] Additionally or alternatively, method 1500 can include one or more other acts described herein in connection with receiving entity aspects of system 400.

[00108] Referring to FIG. 16, illustrated is a flow diagram of an example method 1 600 employable at a BS that facilitates bandwidth adaptation and/or frequency hopping in connection with NR (New Radio) UL (Uplink) transmission(s) from one or more UEs (User Equipments), according to various aspects discussed herein. In other aspects, a machine readable medium can store instructions associated with method 1600 that, when executed, can cause a BS (e.g., eNB, gNB, etc.) to perform the acts of method 1600.

[00109] At 1610, configuration signaling can be transmitted configuring one or more BWs and/or one or more BW parts for at least one of a UL data channel or a UL control channel, wherein the configuration signaling can optionally configure frequency hopping in connection with the UL data channel and/or a UL control channel.

[00110] At 1620, the UL data channel and/or the UL control channel can be received based on the configuration signaling.

[00111 ] Additionally or alternatively, method 1600 can include one or more other acts described herein in connection with transmitting entity aspects of system 500.

[00112] A first example embodiment employable in connection with aspects discussed herein can comprise a system and/or method of wireless communication for a fifth generation (5G) or new radio (NR) system: configuring (e.g., via configuration signaling generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410), by a BS (e.g., gNB, etc.), at least one of radio frequency (RF) bandwidth(s) or BW part(s) for transmission of UL control and/or data channel(s) (e.g., wherein the UL control and/or data channel(s) can be generated by processor(s) 41 0, transmitted via transceiver circuitry 420, received via communication circuitry 520, and processed by processor(s) 510); and transmitting, by the UE, the UL control and/or data channel (e.g., generated by processor(s) 410, transmitted via transceiver circuitry 420, received via communication circuitry 520, and processed by processor(s) 510), in accordance with the configured RF bandwidth or BW part.

[00113] In various aspects of the first example embodiment, the RF bandwidths for the UL data channel and the UL control channel can be different; and the RF bandwidth for the UL control channel with short and long duration can be different.

[00114] In various aspects of the first example embodiment, a single UL RF bandwidth can be configured (e.g., via configuration signaling generated by

processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410), in which the transmission BWs of the UL data and control channels (e.g., generated by processor(s) 410, transmitted via transceiver circuitry 420, received via communication circuitry 520, and processed by processor(s) 510) can be different and can also be located in different frequency regions.

[00115] In various aspects of the first example embodiment, the RF bandwidth for the UL control channel can be located within the RF bandwidth for the UL data channel, wherein the UE can transmit (e.g., via transceiver circuitry 420) the UL control channel (e.g., generated by processor(s) 41 0) using the RF bandwidth for the UL data channel.

[00116] In various aspects of the first example embodiment, when the RF bandwidth for UL control channel is located outside the RF bandwidth allocated for the UL data channel, the UE can employ (e.g., via processor(s) 410 and transceiver circuitry 420) a larger RF bandwidth to transmit (e.g., via transceiver circuitry 420) both the UL control channel and the UL data channel (e.g., generated by processor(s) 410).

[00117] In various aspects of the first example embodiment, when the RF bandwidth for the UL control channel is located outside the RF bandwidth allocated for the UL data channel and the time gap between the UL control and data channel(s) is larger than the UE switching time, the UE can transmit the UL control channel (e.g., generated by processor(s) 410, transmitted via transceiver circuitry 420, received via communication circuitry 520, and processed by processor(s) 510) using the RF bandwidth allocated for the UL control channel.

[00118] In various aspects of the first example embodiment, when the RF bandwidth for UL control channel is located outside the RF bandwidth allocated for the UL data channel, the UE can drop (e.g., via processor(s) 41 0) one of the UL control or data channel(s) depending on the priority of the UL data and control channel(s). [00119] In various aspects of the first example embodiment, the UE can be configured with multiple BW parts within the wide bandwidth (e.g., via configuration signaling by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410).

[00120] In various aspects of the first example embodiment, the BW part index can be configured by higher layers via radio resource control (RRC) signaling or dynamically indicated in the downlink control information (DCI) or a combination thereof (e.g., wherein the RRC and/or DCI can be generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410); wherein a set of BW part indexes can be configured by RRC signaling, while one field in the DCI can be used to indicate a specific BW part from the set of BW parts to employ for transmission (e.g., via transceiver circuitry 420) of the UL data and/or control channel(s) (e.g., generated by processor(s) 410).

[00121 ] In various aspects of the first example embodiment, whether to enable or disable frequency hopping can be semi-statically configured by higher layers or can be dynamically indicated in the DCI (e.g., wherein the RRC and/or DCI can be generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410). In various such aspects, two BW parts can be configured for one or more UEs via higher layer signalling, for example, NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI) or radio resource control (RRC) signaling (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410), wherein frequency hopping can be performed (e.g., by processor(s) 51 0 and

communication circuitry 520 or by processor(s) 410 and transceiver circuitry 420, respectively) across these two configured BW parts for transmission (e.g., via

communication circuitry 520 or transceiver circuitry 420) of DL (e.g., generated by processor(s) 510) or UL (e.g., generated by processor(s) 41 0). In various such aspects, the switching time can be different or can be defined in a UE specific manner (e.g., via configuration signaling generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410); wherein the number of symbols reserved for the gap can be configured by higher layers via RRC signaling or dynamically indicated in the DCI, or a combination thereof (e.g., wherein the RRC and/or DCI can be generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410). In various such aspects, a frequency hopping pattern across multiple BW parts can be defined as a function of one or more of the following parameters:

physical or virtual cell ID, UE ID (e.g., Cell Radio Network Temporary Identifier (C- RNTI), etc.), symbol or slot or mini-slot or subframe or frame index, and/or a parameter which can be indicated in the DCI (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410). In various such aspects, for grant free uplink transmission, the BW part index for the retransmission without indication from gNB can be derived from one or more following parameters: physical or virtual cell ID, UE ID (e.g., Cell Radio Network Temporary Identifier (C-RNTI)), symbol or slot or mini-slot or subframe or frame index, and BW part index for the first transmission. In various such aspects, a frequency hopping pattern across multiple BW parts can be configured by higher layers via MSI, RMSI, OSI, or RRC signaling or dynamically indicated in the DCI or a combination thereof (e.g., wherein the higher layer signaling and/or DCI generated by processor(s) 51 0, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410).

[00122] Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described.

[00123] Example 1 is an apparatus configured to be employed in a UE (User

Equipment), comprising: a memory interface; and processing circuitry configured to: process first signaling that indicates a first set of frequency resources for a NR (New Radio) PUSCH (Physical Uplink Shared Channel) and a second set of frequency resources for a NR PUCCH (Physical Uplink Control Channel), wherein the first set of frequency resources comprise at least one of a first RF (Radio Frequency) BW

(Bandwidth) or one or more first BW parts, wherein the second set of frequency resources comprise at least one of a second RF BW or one or more second BW parts; generate at least one of the NR PUSCH or the NR PUCCH; map the at least one of the NR PUSCH or the NR PUCCH based at least in part on one or more of the first set of frequency resources or the second set of frequency resources; and send the first signaling to a memory via the memory interface. [00124] Example 2 comprises the subject matter of any variation of any of example(s) 1 , wherein the first set of frequency resources is at least partially distinct from the second set of frequency resources.

[00125] Example 3 comprises the subject matter of any variation of any of example(s) 1 , wherein the second set of frequency resources comprises a first subset for the NR PUCCH with a short duration and a second subset for the NR PUCCH with a long duration, wherein the first subset is at least partially distinct from the second subset.

[00126] Example 4 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the first set of frequency resources comprises the first RF BW and the second set of frequency resources comprises the second RF BW, wherein the first RF BW and the second RF BW are a common RF BW.

[00127] Example 5 comprises the subject matter of any variation of any of example(s) 4, wherein the processing circuitry is configured to at least one of map the NR PUSCH to a first portion of the common RF BW or map the NR PUCCH to a second portion of the common RF BW, wherein the first portion is at least partially distinct from the second portion.

[00128] Example 6 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the first set of frequency resources comprises the first RF BW and the second set of frequency resources comprises the second RF BW, wherein the first RF BW comprises the second RF BW, and wherein the processing circuitry is configured to map the NR PUCCH to the first RF BW.

[00129] Example 7 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the first set of frequency resources comprises the first RF BW and the second set of frequency resources comprises the second RF BW, wherein the first RF BW and the second RF BW are non-overlapping, and wherein the processing circuitry is configured to map the NR PUSCH and the NR PUCCH to a third BW comprising the first BW and the second BW.

[00130] Example 8 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the first set of frequency resources comprises the first RF BW and the second set of frequency resources comprises the second RF BW, wherein the first RF BW and the second RF BW are non-overlapping, wherein the processing circuitry is configured to: map the NR PUSCH to the first RF BW; and map the NR PUCCH to the second RF BW when a time gap between the NR PUSCH and time resources associated with the NR PUCCH is greater than a switching time of the UE. [00131 ] Example 9 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the first set of frequency resources comprises the first RF BW and the second set of frequency resources comprises the second RF BW, wherein the first RF BW and the second RF BW are non-overlapping, wherein the processing circuitry is configured to: select a channel from the NR PUSCH and the NR PUCCH based on priorities of the NR PUSCH and the NR PUCCH; map the selected channel to an associated RF BW of the first RF BW and the second RF BW; and drop the non- selected channel from the NR PUSCH and the NR PUCCH.

[00132] Example 10 comprises the subject matter of any variation of any of example(s) 1 -3, wherein at least one of the one or more first BW parts or the one or more second BW parts comprises a plurality of BW parts.

[00133] Example 1 1 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the processing circuitry is further configured to: process second signaling that indicates a BW part index associated with an indicated BW part of the one or more first BW parts or the one or more second BW parts; and map the at least one of the NR PUSCH or the NR PUCCH to the indicated BW part.

[00134] Example 12 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the processing circuitry is further configured to process third signaling that indicates whether to enable or disable a frequency hopping in connection with the NR PUSCH or the NR PUCCH, wherein the third signaling comprises one or more of higher layer signaling or a DCI (Downlink Control Information) message.

[00135] Example 13 comprises the subject matter of any variation of any of example(s) 1 -3, wherein the at least one of the NR PUSCH or the NR PUCCH is associated with an initial grant-free NR UL transmission, wherein the processing circuitry is further configured to determine a BW part index associated with a

retransmission of the grant-free NR UL transmission based on one or more of a physical cell ID (identifier), a virtual cell ID, an ID of the UE, a symbol index, a mini-slot index, a slot index, a subframe index, a frame index, or a BW part index associated with the initial grant-free NR UL transmission.

[00136] Example 14 comprises the subject matter of any variation of any of example(s) 1 -2, wherein the second set of frequency resources comprises a first subset for the NR PUCCH with a short duration and a second subset for the NR PUCCH with a long duration, wherein the first subset is at least partially distinct from the second subset. [00137] Example 15 comprises the subject matter of any variation of any of example(s) 1 -9, wherein at least one of the one or more first BW parts or the one or more second BW parts comprises a plurality of BW parts.

[00138] Example 16 comprises the subject matter of any variation of any of example(s) 1 -10, wherein the processing circuitry is further configured to: process second signaling that indicates a BW part index associated with an indicated BW part of the one or more first BW parts or the one or more second BW parts; and map the at least one of the NR PUSCH or the NR PUCCH to the indicated BW part.

[00139] Example 17 comprises the subject matter of any variation of any of example(s) 1 -1 1 , wherein the processing circuitry is further configured to process third signaling that indicates whether to enable or disable a frequency hopping in connection with the NR PUSCH or the NR PUCCH, wherein the third signaling comprises one or more of higher layer signaling or a DCI (Downlink Control Information) message.

[00140] Example 18 is an apparatus configured to be employed in a gNB (next generation Node B), comprising: a memory interface; and processing circuitry configured to: generate first signaling that indicates a first set of frequency resources for a NR (New Radio) PUSCH (Physical Uplink Shared Channel) and a second set of frequency resources for a NR PUCCH (Physical Uplink Control Channel), wherein the first set of frequency resources comprise at least one of a first RF (Radio Frequency) BW (Bandwidth) or one or more first BW parts, wherein the second set of frequency resources comprise at least one of a second RF BW or one or more second BW parts; processing at least one of the NR PUSCH or the NR PUCCH, wherein the at least one of the NR PUSCH or the NR PUCCH are mapped to at least a portion of the first set of frequency resources or at least a portion of the second set of frequency resources; and send the configuration signaling to a memory via the memory interface.

[00141 ] Example 19 comprises the subject matter of any variation of any of example(s) 18, wherein the processing circuitry is further configured to generate second signaling that indicates whether to enable a frequency hopping in connection with the NR PUSCH or the NR PUCCH.

[00142] Example 20 comprises the subject matter of any variation of any of example(s) 19, wherein the processing circuitry is further configured to generate third signaling that indicates a pair of BW parts for the frequency hopping, wherein the third signaling comprises one or more of NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling. [00143] Example 21 comprises the subject matter of any variation of any of example(s) 19, wherein the processing circuitry is further configured to generate fourth signaling that indicates, for the frequency hopping, a frequency hopping pattern over a plurality of BW parts of the first set of frequency resources or the second set of frequency resources, wherein the third signaling comprises one or more of NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), radio resource control (RRC) signaling, or a DCI (Downlink Control Information) message.

[00144] Example 22 comprises the subject matter of any variation of any of example(s) 18-21 , wherein the first set of frequency resources is at least partially distinct from the second set of frequency resources.

[00145] Example 23 comprises the subject matter of any variation of any of example(s) 18-21 , wherein the second set of frequency resources comprises a first subset for the NR PUCCH with a short duration and a second subset for the NR

PUCCH with a long duration, wherein the first subset is at least partially distinct from the second subset.

[00146] Example 24 comprises the subject matter of any variation of any of example(s) 18-21 , wherein the first set of frequency resources comprises the first RF BW and the second set of frequency resources comprises the second RF BW, wherein the first RF BW and the second RF BW are a common RF BW.

[00147] Example 25 comprises the subject matter of any variation of any of example(s) 18-21 , wherein the processing circuitry is further configured to: generate fifth signaling that indicates a BW part index that indicates an associated BW part of the one or more first BW parts or the one or more second BW parts, wherein the at least one of the NR PUSCH or the NR PUCCH are mapped to the associated BW part.

[00148] Example 26 is a machine readable medium comprising instructions that, when executed, cause a UE (User Equipment) to: receive first signaling that indicates a first set of frequency resources for a NR (New Radio) PUSCH (Physical Uplink Shared Channel) and a second set of frequency resources for a NR PUCCH (Physical Uplink Control Channel), wherein the first set of frequency resources comprise at least one of a first RF (Radio Frequency) BW (Bandwidth) or one or more first BW parts, wherein the second set of frequency resources comprise at least one of a second RF BW or one or more second BW parts; and transmit the at least one of the NR PUSCH or the NR PUCCH based at least in part on one or more of the first set of frequency resources or the second set of frequency resources. [00149] Example 27 comprises the subject matter of any variation of any of example(s) 26, wherein the instructions, when executed, further cause the UE to receive second signaling that indicates whether to enable or disable a frequency hopping in connection with the NR PUSCH or the NR PUCCH, wherein the third signaling comprises one or more of higher layer signaling or a DCI (Downlink Control Information) message.

[00150] Example 28 comprises the subject matter of any variation of any of example(s) 27, wherein the instructions, when executed, further cause the UE to receive third signaling that indicates a pair of BW parts for the frequency hopping, wherein the third signaling comprises one or more of NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling.

[00151 ] Example 29 comprises the subject matter of any variation of any of example(s) 27, wherein the instructions, when executed, further cause the UE to receive fourth signaling that indicates, for the frequency hopping, a frequency hopping pattern over a plurality of BW parts of the first set of frequency resources or the second set of frequency resources, wherein the third signaling comprises one or more of NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), radio resource control (RRC) signaling, or a DCI (Downlink Control Information) message.

[00152] Example 30 comprises the subject matter of any variation of any of example(s) 27, wherein the instructions, when executed, further cause the UE to determine, for the frequency hopping, a frequency hopping pattern over a plurality of BW parts of the first set of frequency resources or the second set of frequency resources, based at least in part on one or more of a physical cell ID (identifier), a virtual cell ID, an ID of the UE, a symbol index, a mini-slot index, a slot index, a subframe index, a frame index, or a parameter received via a DCI (Downlink Control Information) message.

[00153] Example 31 comprises the subject matter of any variation of any of example(s) 26-30, wherein the instructions, when executed, further cause the UE to receive fifth signaling that indicates a number of symbols reserved for a gap between the PUSCH and the PUCCH, wherein the fifth signaling comprises one or more of RRC (Radio Resource Control) signaling or a DCI (Downlink Control Information) message.

[00154] Example 32 is a machine readable medium comprising instructions that, when executed, cause a gNB (next generation Node B) to: transmit first signaling that indicates a first set of frequency resources for a NR (New Radio) PUSCH (Physical Uplink Shared Channel) and a second set of frequency resources for a NR PUCCH (Physical Uplink Control Channel), wherein the first set of frequency resources comprise at least one of a first RF (Radio Frequency) BW (Bandwidth) or one or more first BW parts, wherein the second set of frequency resources comprise at least one of a second RF BW or one or more second BW parts; and receive at least one of the NR PUSCH or the NR PUCCH, wherein the at least one of the NR PUSCH or the NR PUCCH are mapped to at least a portion of the first set of frequency resources or at least a portion of the second set of frequency resources.

[00155] Example 33 comprises the subject matter of any variation of any of example(s) 32, wherein the instructions, when executed, further cause the gNB to transmit second signaling that indicates a BW part index associated with an indicated BW part of the one or more first BW parts or the one or more second BW parts, wherein the at least one of the NR PUSCH or the NR PUCCH are mapped to the indicated BW part.

[00156] Example 34 comprises the subject matter of any variation of any of example(s) 32-33, wherein the first set of frequency resources is at least partially distinct from the second set of frequency resources.

[00157] Example 35 is an apparatus configured to be employed in a UE (User Equipment), comprising: means for receiving first signaling that indicates a first set of frequency resources for a NR (New Radio) PUSCH (Physical Uplink Shared Channel) and a second set of frequency resources for a NR PUCCH (Physical Uplink Control Channel), wherein the first set of frequency resources comprise at least one of a first RF (Radio Frequency) BW (Bandwidth) or one or more first BW parts, wherein the second set of frequency resources comprise at least one of a second RF BW or one or more second BW parts; and means for transmitting the at least one of the NR PUSCH or the NR PUCCH based at least in part on one or more of the first set of frequency resources or the second set of frequency resources.

[00158] Example 36 comprises the subject matter of any variation of any of example(s) 35, further comprising means for receiving second signaling that indicates whether to enable or disable a frequency hopping in connection with the NR PUSCH or the NR PUCCH, wherein the third signaling comprises one or more of higher layer signaling or a DCI (Downlink Control Information) message.

[00159] Example 37 comprises the subject matter of any variation of any of example(s) 36, further comprising means for receiving third signaling that indicates a pair of BW parts for the frequency hopping, wherein the third signaling comprises one or more of NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling.

[00160] Example 38 comprises the subject matter of any variation of any of example(s) 36, further comprising means for receiving fourth signaling that indicates, for the frequency hopping, a frequency hopping pattern over a plurality of BW parts of the first set of frequency resources or the second set of frequency resources, wherein the third signaling comprises one or more of NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), radio resource control (RRC) signaling, or a DCI (Downlink Control Information) message.

[00161 ] Example 39 comprises the subject matter of any variation of any of example(s) 36, further comprising means for determining, for the frequency hopping, a frequency hopping pattern over a plurality of BW parts of the first set of frequency resources or the second set of frequency resources, based at least in part on one or more of a physical cell ID (identifier), a virtual cell ID, an ID of the UE, a symbol index, a mini-slot index, a slot index, a subframe index, a frame index, or a parameter received via a DCI (Downlink Control Information) message.

[00162] Example 40 comprises the subject matter of any variation of any of example(s) 35-39, further comprising means for receiving fifth signaling that indicates a number of symbols reserved for a gap between the PUSCH and the PUCCH, wherein the fifth signaling comprises one or more of RRC (Radio Resource Control) signaling or a DCI (Downlink Control Information) message.

[00163] Example 41 is an apparatus configured to be employed in a gNB (next generation Node B), comprising: means for transmitting first signaling that indicates a first set of frequency resources for a NR (New Radio) PUSCH (Physical Uplink Shared Channel) and a second set of frequency resources for a NR PUCCH (Physical Uplink Control Channel), wherein the first set of frequency resources comprise at least one of a first RF (Radio Frequency) BW (Bandwidth) or one or more first BW parts, wherein the second set of frequency resources comprise at least one of a second RF BW or one or more second BW parts; and means for receiving at least one of the NR PUSCH or the NR PUCCH, wherein the at least one of the NR PUSCH or the NR PUCCH are mapped to at least a portion of the first set of frequency resources or at least a portion of the second set of frequency resources. [00164] Example 42 comprises the subject matter of any variation of any of example(s) 41 , further comprising means for transmitting second signaling that indicates a BW part index associated with an indicated BW part of the one or more first BW parts or the one or more second BW parts, wherein the at least one of the NR PUSCH or the NR PUCCH are mapped to the indicated BW part.

[00165] Example 43 comprises the subject matter of any variation of any of example(s) 41 -42, wherein the first set of frequency resources is at least partially distinct from the second set of frequency resources.

[00166] Example 44 comprises an apparatus comprising means for executing any of the described operations of examples 1 -43.

[00167] Example 45 comprises a machine readable medium that stores instructions for execution by a processor to perform any of the described operations of examples 1 - 43.

[00168] Example 46 comprises an apparatus comprising: a memory interface; and processing circuitry configured to: perform any of the described operations of examples 1 -43.

[00169] The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

[00170] In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[00171 ] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application.