WO2023187450A1

WO2023187450A1 - Adaptive uplink scheduling to minimize maximum power reduction (mpr) impact

Info

Publication number: WO2023187450A1
Application number: PCT/IB2022/053018
Authority: WO
Inventors: Govardhan Madhugiri Dwarakinath; Muhammad Ali Kazmi
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-03-31
Filing date: 2022-03-31
Publication date: 2023-10-05

Abstract

A method performed by a network node (1610A, 1610B, 1800, 2002, 2104) for determining resource block allocation for scheduling a user equipment, UE, (1612A, 1612B, 1612C, 1612D, 1700, 2002, 2106) in an uplink communication, the method includes determining (601) a UE power class of a UE. The method further includes determining (603) a UE location of the UE. The method further includes determining (605) a multiple access scheme, MAS, type for the UE. The method further includes determining (607) a resource block allocation for the UE based on the UE power class, the UE location, and the MAS type for the UE. The method further includes allocating (609) the resource block for the UE. Additionally, or alternatively, resource block availability is known and the MAS type for the UE is determined based on the UE power class, the UE location and the available resource blocks.

Description

ADAPTIVE UPLINK SCHEDULING TO MINIMIZE MAXIMUM POWER REDUCTION (MPR) IMPACT TECHNICAL FIELD [0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications. BACKGROUND [0002] Scheduling is a very important functionality in LTE/NR (long term evolution/new radio) or any communications technology. Scheduling helps in efficient accommodation of user equipments (UEs) over time-frequency resources for data transmission. The UE is scheduled for uplink (UL) or downlink (DL) transmission by the serving base station (e.g., eNB, gNB etc.). Scheduler implementation is network provider specific. The most ideal scheduler is the one which tries to achieve optimal capacity and performance in the network. Multiple UEs can be scheduled in the same time resource (e.g., symbol, slot, transmission time interval (TTI), subframe etc.) for both FDD (frequency division duplex) & TDD (time division duplex) schemes. Scheduling in UL for LTE/NR is mostly contiguous in frequency domain. For example, UEs are given a designated number of physical resource blocks (PRBs) continuously along the bandwidth in a time resource (e.g., symbols, slot, subframe, etc.). In NR, the UL transmission can be done using any of two different multiple access schemes, CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) or DFTS-OFDM (discrete Fourier transform- spread orthogonal frequency division multiplexing). The term multiple access scheme may also be called as waveform, waveform type, OFDM waveform etc. The waveform implies conversion of baseband IQ samples present on each sub-carrier in frequency domain into a multi-tone signal, for example: CP-OFDM, DFTS-OFDM etc. In NR, the base station (e.g., gNB) can configure the UE to use either OFDM or DFTS-OFDM for UL transmission. Each multiple access scheme or waveform has its own characteristics, properties and merits. For example: [0003] For CP-OFDM: ^ Used under higher throughput scenarios ^ Effective and efficient for MIMO (multiple input multiple output) use case ^ Higher spectral efficiency, as there is no PRB size restriction within the bandwidth [0004] For DFTS-OFDM: ^ Efficient under power limited scenarios ^ Only single layer transmission is possible ^ Has RB restriction within given bandwidth ^ Effective for higher cell ranges [0005] The non-linear characteristic of the UE transmission Power Amplifier (PA) may lead to emissions outside the allowed UE band e.g., to meet, out of band emission requirements, the UE is allowed to reduce its maximum power by employing Maximum Power Reduction (MPR), which is pre-defined. The term MPRWT refers to the maximum power reduction due to modulation orders (e.g., BPSK (binary phase shift keying), QPSK (quadrature phase shift keying), 16 QAM (quadrature amplitude modulation), 64 QAM etc.), transmission bandwidth (BWchannel) configurations listed in table 5.3.2-1 of 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 38.101, and OFDM waveform types (e.g., DFT-s-OFDM, CP-OFDM etc.). For example, in 3GPP specifications, the MPR for a specific BW (bandwidth) region (RB region) is defined as function of multiple access schemes, modulation (e.g., BPSK, QPSK, 16 QAM, 64 QAM etc.), and Power Class (PC) of the UE as shown in tables below from TS 38.101-2, v17.2.0: Table 1: MPR_WT For Power Class 1, BW_channel ≤ 200 MHz Modulation MPRWT (dB), BWchannel ≤ 200 MHz Outer RB Inner RB allocations

Table 2: MPRWT For Power Class 1, BWchannel = 400 MHz Modulation MPRWT (dB), BWchannel = 400 MHz Outer RB Inner RB allocations Ta

, Modulation MPRWT, BWchannel ≤ 200 MHz Inner RB allocations, Edge RB Table 4:

MPR_WT For Power Class 3, BW_channel = 400 MHz Modulation MPRWT, BWchannel = 400 MHz Inner RB Ed e RB

[0006] The UE signals its power class to the network via UE capability information. At present in frequency range FR2, there are 5 different UEs/devices Power classes - namely power class # 1, # 2, # 3, # 4 and # 5. The frequencies within FR2 are also called "mmwave." FR2 may further be split into 2 or more subranges. In one example, FR2 frequencies may range from 24 GHz to 52.6 GHz e.g., FR2-1 subrange within FR2. In another example FR2 may range from 24 GHz to 71 GHz. In another example FR2 frequencies from 52.6 GHz to 71 GHz may be called as FR2-2 subrange within FR2. SUMMARY [0007] There currently exist certain challenges. Specifically, current Scheduling algorithms do not consider Maximum Power Reduction (MPR) based scheduling for UEs with different UE power classes. Additionally, in existing systems, more than one multiple access scheme (MAS) schemes are not employed for scheduling the same UE. With different operating frequencies and deployments in LTE/4G, 5G and future communication technologies, it would be challenging to have one scheduling algorithm for UEs with different PCs, especially for UEs at Cell edge. Due to higher operating frequencies, it has become a challenge for the base station to serve scheduling entities (e.g., UEs) on cell edge with agreeable performance. There are many interference mitigating mechanisms but there are no scheduling algorithms which consider MPR, with MAS (e.g., OFDM waveform) to achieve robust scheduling which avoids or maintains OOB emission within acceptable limit, achieving better performance at cell edge. [0008] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. [0009] According to some embodiments, a method performed by a network node for determining resource block allocation for scheduling a user equipment (UE) in an uplink communication includes determining a UE power class of a UE. The method further includes determining a UE location of the UE. The method includes determining a multiple access scheme (MAS) type for the UE. The method includes determining a resource block allocation for the UE based on the UE power class, the UE location, and the MAS type for the UE. The method further includes allocating the resource block for the UE. [0010] According to some other embodiments, a method performed by a network node for determining a multiple access scheme (MAS) type for scheduling a user equipment (UE) in an uplink communication includes determining a UE power class of a UE. The method further includes determining a UE location of the UE. The method includes determining available resource blocks for allocation to the UE. The method further includes determining a MAS type for the UE based on the UE power class, the UE location, and the available resource blocks. The method includes allocating one or more resource blocks of the available resource blocks for the UE along with the MAS type determined to the UE for uplink transmission. [0011] Analogous network nodes, computer programs, and computer program products are provided. [0012] Certain embodiments may provide one or more of the following technical advantages. Various embodiments may reduce interference for neighboring cells, neighboring sites of similar radio access technology (RAT) and communication systems (e.g., could be a different RAT). Various embodiments may efficiently utilize the MPR to schedule cell edge UEs of different power classes simultaneously. Various embodiments may combine simultaneous allocation of different OFDM waveforms when scheduling cell edge UEs of different power classes simultaneously to achieve a robust scheduling algorithm. The mechanisms described in the various embodiments enable resource allocation to UEs associated with different power classes, waveforms, and geographical location within the cell in a systematic manner enhancing resource utilization and efficiency. This can lead to achieving improvement in system and user throughput (e.g., bitrate) in the uplink and enhanced UE coverage. BRIEF DESCRIPTION OF THE DRAWINGS [0013] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings: [0014] Figure 1 is an illustration of an example of two resource block regions within a cell's channel bandwidth; [0015] Figure 2 is an illustration of a generic resource block region for a UE with power class 1; [0016] Figure 3 is an illustration of a generic resource block region for a UE with power class 2 to 5; [0017] Figure 4 is an illustration of a cell center and cell edge; [0018] Figure 5 is a block diagram illustrating a method of determining resource block allocation region based on UE power class, type of multiple access scheme, and UE location; [0019] Figures 6-9 are flow charts illustrating operations of a network node according to some embodiments; [0020] Figure 10 is a block diagram illustrating a method of determining a multiple access scheme type based on available resource blocks, UE power class, and UE location; [0021] Figures 11-15 are flow chart illustrating operations of a network node according to some embodiments; [0022] Figure 16 is a block diagram of a communication system in accordance with some embodiments; [0023] Figure 17 is a block diagram of a user equipment in accordance with some embodiments; [0024] Figure 18 is a block diagram of a network node in accordance with some embodiments; [0025] Figure 19 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments; [0026] Figure 20 is a block diagram of a virtualization environment in accordance with some embodiments; and [0027] Figure 21 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments in accordance with some embodiments. DETAILED DESCRIPTION [0028] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. , in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment. [0029] In this description, while the main focus is on PC1 (power class 1) and PC3 (power class 3), which are Fixed Wireless Access (FWA) and MBB (Mobile broadband) UEs respectively, the embodiments described herein are applicable to any power class (present or those introduced in future). Irrespective of power class, MPR for DFTS-OFDM is lower for inner and outer resource block (RB) regions in comparison to CP-OFDM. CP-OFDM has by and large the same MPR for all RB regions for certain power classes e.g., PC3. Having different MPR helps in avoiding out of band (OOB) emission e.g., Adjacent Channel Leakage Ratio (ACLR), unwanted emission etc. OOB emission can cause interference to communication systems, cells, nearby base stations which uses adjacent frequency channels for operation of signals e.g., reception and/or transmission of signals. Such interference can severely degrade the performance of the network (e.g., decrease user and/or system throughput) or even blocking receiver in adjacent frequency channels ceasing communication. [0030] As previously indicated, current scheduling algorithms do not consider Maximum Power Reduction (MPR) based scheduling for UEs with different UE power classes. Some embodiments of the various embodiments enable a network node of scheduling UEs with resources (e.g., time-frequency resources such as RBs, resource element etc.) in a cell based on or taking into account at least the following parameters/characteristics: UE power class, OFDM waveform (e.g., CP-OFDM, DFTS-OFDM, etc.), and UE location within the cell (e.g., cell edge, cell center, etc.). [0031] Other embodiments of the various embodiments enable a network node of determining an OFDM waveform (e.g., CP-OFDM, DFTS-OFDM etc.) for scheduling UEs in a cell based on (e.g., taking into account) at least the following parameters/characteristics: UE power class, available resource blocks (e.g., RB region within the channel bandwidth, and UE location within the cell (e.g., cell edge, cell center, etc.). [0032] Some objectives of the various embodiments are to provide cell edge UEs with acceptable performance (e.g., acceptable throughput, etc.) and reduce interference to neighboring cells. [0033] The UEs with different PCs in the cell can be determined by the network node (e.g., base station, gNB, etc.) using power class information sent by the UE in a UE capability RRC (radio resource control) IE (information element). [0034] The UE location within the cell can be determined by the network node based on signal level and/or UE location information (e.g., based on the UE signal level (e.g., path loss, RSRP (reference signal received power), etc.) to determine whether the UEs are categorized into cell edge UEs or cell center UEs, etc. [0035] Based on maximum power reduction (MPR), there are different RB regions defined such as region 1, region 2 (where, e.g., both 1 and 2 are inner RB regions) and outer region within the channel bandwidth of the cell. [0036] The embodiments are applicable for any number of time-frequency resource (e.g., resource block (RB)) regions within the channel BW. The term RB and PRB (physical resource block) may be used interchangeably in the description herein but mean the same thing. The various embodiments are applicable to any type of time-frequency resource or time-frequency allocation or time-frequency region. For the sake of consistency and simplicity most examples hereinafter use the term RB or RB allocation or RB region. Other examples of time-frequency resource are resource element, tone, sub-PRB etc. [0037] Figure 1 shows an example of two RB regions (inner and outer RB regions) for certain channel bandwidth of the cell e.g., 200 MHz bandwidth. The various embodiments are also applicable to any number of RB regions e.g., inner, middle, outer etc. Figure 2 and Figure 3 represent Generic RB region examples for UE power class 1 and power class 2 to 5, respectively. In Figures 2 and 3, N_RB is the maximum number of RBs for a given channel Bandwidth, L_CRB is the transmission bandwidth which represents length of a contiguous resource block allocation expressed in unit of Resource. [0038] The RBs regions may also be called as RB groups e.g., inner RB group and outer RB group. The RBs regions can be determined based on one or more parameters. These parameters include: [0039] 1. Channel bandwidth. For example, o number of RBs in outer RB region in larger BW (e.g., BW ≥ 200 MHz) is larger compared to the number of RBs in outer RB region in smaller BW (e.g., BW < 200 MHz). o number of RBs in inner RB region in larger BW (e.g., BW ≥ 200 MHz) is smaller compared to the number of RBs in inner RB region in smaller BW (e.g., BW < 200 MHz). [0040] 2. Fraction of channel bandwidth. For example, RBs within X% of outer most channel BW in frequency domain belong to outer RB region whereas the remaining Y% (Y=100-X) belong to inner RB region. [0041] 3. Numerology of signals transmitted in the cell. Examples include CP length, subcarrier spacing (SCS), slot length, symbol length etc. For example: o number of RBs in outer RB region when SCS is larger (e.g., SCS ≥ 120 KHz) is larger compared to the number of RBs in outer RB region when SCS is smaller (e.g., SCS < 120 KHz). o number of RBs in inner RB region when SCS is larger (e.g., BW ≥ 200 MHz) is smaller compared to the number of RBs in inner RB region when SCS is smaller (e.g., SCS < 120 KHz). o Examples of RB regions within the cell BW are shown in Figures 1, 2 and 3. [0042] In Figures 2 and 3, NRB is the maximum number of RBs for a given channel Bandwidth, L_CRB is the transmission bandwidth which represents length of a contiguous resource block allocation expressed in unit of Resource Blocks. The definition of different RB regions is based on power class and channel bandwidth [0043] For UE power class 1: RB_end = RB_Start + L_CRB - 1 RB_Start,Low = Max(1, Floor(LCRB/2)) RB_Start,High = N_RB – RB_Start,Low – L_CRB [0044] An RB allocation is an Outer RB allocation if RB_Start < RB_Start,Low OR RB_Start > RB_Start,High OR L_CRB > Ceil(N_RB/2) [0045] An RB allocation belonging to Table 1 is a Region 1 inner RB allocation if RB_start ≥ Ceil(1/3 N_RB) AND RB_end < Ceil(2/3 N_RB) [0046] An RB allocation belonging to Table 2 is a Region 1 inner RB allocation if RB_start ≥ Ceil(1/4 N_RB) AND RB_end < Ceil(3/4 N_RB) AND L_CRB ≤ Ceil(1/4 N_RB) [0047] An RB allocation is a Region 2 inner allocation if it is NOT an Outer allocation AND NOT a Region 1 inner allocation. [0048] For the UE power classes 2 to 5: R^B _Start,Low ^{= max(1, L} _CRB ^), RB_Start,High = NRB – RBStart,Low – LCRB, RBend = RBStart + LCRB - 1 [0049] An RB allocation belonging to Table 3 is a Region 1 inner RB allocation if: RB_Start,Low ≤ RB_Start ≤ RB_Start,High, and L_CRB ≤ ceil(N_RB/3) [0050] An RB allocation belonging to Table 4 is a Region 1 inner RB allocation if RB_start ≥ Ceil(1/4 N_RB) AND RB_end < Ceil(3/4 N_RB) AND L_CRB ≤ Ceil(1/4 N_RB) [0051] For all transmission bandwidth configurations, an RB allocation is an Outer RB Region2 or Edge allocation if it is NOT a Region 1 inner allocation. [0052] Figure 4 shows an example of two geographical regions (cell center and cell edge regions) within the cell. The embodiments are also applicable for classifying the UEs in any number of geographical regions within the cell e.g., within the serving cell of the UE. The regions may also be called as cell portion, cell part, etc. e.g., inner cell portion and outer cell portion. As used herein, a cell refers to a geographical region served be a network node (e.g., cellular base station), which can be logically subdivided into more than one geographical region (e.g., area). The regions can be determined based on one or more parameters. These parameters include: [0053] 1. Cell size. Cell size can be determined based on or defined by one or more of: cell radius (Rc), inter-site distance between adjacent cells etc. o For example, number of regions (e.g., 3 regions) in cell with larger cell size (e.g., cell radius larger than threshold (Hs)) can be larger compared to number of regions in smaller cell size (e.g., Rc ≤ Hs). [0054] 2. Cell type or cell coverage area e.g., macro cell, micro cell, pico cell, etc. The coverage area of macro, micro, pico cells decreases in descending order. o For example, number of regions in macro cell can be larger (e.g., 4 regions) compared to the number of regions in micro cell (e.g., 3 regions), which in turn can be larger than in pico cell (e.g., 2 regions). [0055] 3. Measured signal level. o For example, the region of the cell may be determined based on relation between measured signal level (e.g., path loss, RSRP, RSRQ (reference signal received quality), etc.). For example, the region of the cell where measured signal level is less than or equal to certain threshold (Hm) is designated as inner cell or cell center. On the other hand, the region of the cell where measured signal level is larger than Hm is designated as outer cell or cell edge. [0056] 4. Number of UEs in the cell. o For example, number of regions (e.g., 3 regions) in cell with larger number of UEs (e.g., number of UEs (Nu) larger than threshold (Hu)) can be larger compared to number of regions with smaller number of UEs in the cell (e.g., Nu ≤ Hu). [0057] Determining and allocating RB allocation [0058] Figure 5 illustrates a MPR scheduler in a network node (e.g., serving BS) for determining an RB allocation region for uplink scheduling a UE based on the UE location within the serving cell, the UE power class and multiple access scheme (MAS) type (e.g., OFDM waveform). The network node, using the MPR scheduler, which may be a separate module or integrated into the network node, determines the UE power class, the multiple access scheme type, and the UE location, and determines resource block allocation based on the UE power class, UE location, and MAS type. [0059] Operations of the network node 1800 (implemented using the structure of Figure 16) will now be discussed with reference to the flow chart of Figure 6 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1604 of Figure 16, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1602, RAN node 1800 performs respective operations of the flow chart. UE 1700 (implemented using the structure of Figure 15) will be used as the UE in the description. [0060] Turning to Figure 6, in block 601, the network node can determine the UE power class (PC) based on information received from the UE 1700. For example, the network node 1800 can determine the UE PC in the UE capability comprising also UE power class transmitted by the UE 1700 to the network node via higher layer signaling such as radios resource control (RRC). The information may further indicate supported power classes for different frequency bands, for certain frequency range (e.g., FR1, FR2 etc.). The power class denotes or indicates the maximum output power (Pmax) supported by the UE e.g., for certain band, for certain FR etc. Pmax may also be called as nominal power etc. Pmax for certain PC may be characterized by one or more power class parameters e.g., max total radiated power (TRP), max effective isotropic radiated power (EIRP), minimum peak EIRP, minimum EIRP at certain spherical coverage etc. The PC parameters may further depend on e.g., frequency bands. For example, for PC1 the max TRP=35 dBm, max EIRP=55 dBm, minimum peak EIRP=40 dBm and minimum EIRP at 85^th percentile = 32 dBm for band n257 (2.65-2.95 GHz). In another example for PC3 the max TRP=23 dBm, max EIRP=43 dBm, minimum peak EIRP=22.4 dBm and minimum EIRP at 50th percentile = 11.5 dBm for the same band n257. [0061] In block 603, the network node 1800 determines the UE location of the UE 1700. For example, the network node can determine the location of UEs in different geographical regions (e.g., cell center, cell edge, etc.) of the cell based on for example by comparing a signal level (e.g., signal strength such as path loss, RSRP, etc.) between the UE 1700 and the serving BS, and signal level threshold. For example, if the RSRP measured by the UE 1700 is below or equal to certain threshold (G), then the UE 1700 is assumed to be in the cell center; otherwise, the UE 1700 is assumed to be in the cell edge. In another example the network node can further determine the location of UEs 1700 within the cell based on one or more positioning mechanisms e.g., GNSS (global navigation satellite system), etc. [0062] The different geographical regions can be determined by the network node 1800. This is illustrated in Figure 7, where in block 701, the network node 1800 determines a plurality of geographic regions within a cell based on one or more parameters. The one or more parameters may include one or more of: cell size; cell type; cell coverage area; a measured signal level; and a number of UEs in the cell [0063] Returning to Figure 6, in block 605, the network node 1800 determines the multiple access scheme (MAS) type to be used for UL transmission for the UE 1700. For example, the MAS type in some embodiments is an OFDM waveform type (e.g., DFTS-OFDM, CP-OFDM, etc.) [0064] In block 607, the network node 1800 determines resource block allocation for the UE 1700 for e.g., UL transmission based on the UE power class, the UE location, and the MAS type for the UE. When the UE 1700 is in the cell edge (far from the base station) then the UE 1700 is likely to operate at maximum or higher power which has to be reduced due to MPR to meet out of band (OOB) emission requirements. In this case, an appropriate RB region within the cell BW, which further depends on PC and MAS type, should be chosen. But when the UE 1700 is in the cell center (close to the BS) then UE transmit power is not so high. In this case in principle, the network node 1800 has more freedom in terms of selecting the RB region within the cell BW. However, RBs within the cell BWs are shared between all UEs 1700 within the cell i.e., UEs 1700 in cell center and cell edge. Therefore, to achieve optimal performance the key idea is that the network node 1800 jointly considers the allocation of RBs to all UEs 1700 within the cell during the same time resource (e.g., symbol, slot, sub-frame etc.) by considering their PCs, geographical location in the cell and MAS type to be used for UL transmission. [0065] In some embodiments, the RB allocation is based on a table. Table 5 is one example of RB allocation based on a table. The example in Table 5 uses two different UE power classes (PC_A and PC_B), two different MAS types (OFDM-1 and OFDM-2), two different inner RB regions (inner RBs-1 and inner RBs-2) and two different outer RB regions (outer RBs-1 and outer RBs-2) to describe how such a table can be used. Note that the embodiments are applicable to any number of UE PCs, MAS types, RB regions, etc. Table 5 – example of RB allocation based on UE location, power class, and MAS type RB allocation region: inner RB region or outer RB region -2

[0066] As illustrated by the example in Table 5, the network node 1800 determines the RB region based on UE location as well as UE PC and MAS type. The example shows that even for the same PC and the same MAS type, the RB region can be different based on whether the UE 1700 is in the cell center or in the cell edge. For example, for the same UE PC (e.g., PCA) and the same MAS type (e.g., OFDM-1), the RB region for resource allocation is: inner-RBs-1 if the UE 1700 is in the cell edge and outer-RBs-1 if the UE is in the cell center. [0067] A semi-specific example (with some general and some specific parameters) for the network node implementation for determining RB allocation region for scheduling the UE 1700 in the uplink based on the UE location within the serving cell, the UE power classes (PC1 and PC3), and MAS types (CP-OFDM and DFTS-OFDM) is illustrated in Table 6. As illustrated in Table 6 that the network node determines the RB region based on UE location as well as PC and MAS type. The example shows that even for the same PC (PC1 or PC3) and the same MAS type (CP-OFDM or DFTS-OFDM), the RB region can be different based on whether the UE 1700 is in the cell center or in the cell edge. For example, for the same UE PC (e.g., PC1) and the same MAS type (e.g., DFTS-OFDM), the RB region for resource allocation is: inner-RBs-1 if the UE 1700 is in the cell edge and outer-RBs-1 if the UE 1700 is in the cell center. Table 6: A specific example of RB allocation based on UE location, power class and multiple access scheme types (DFTS-OFDM or CP-OFDM) RB allocation region: inner RB region or outer RB region

[0068] The above scheduling mechanism in the network may simultaneous use DFTS- OFDM and CP-OFDM multiple access schemes for different UEs within the same cell BW in the same time resource (e.g., symbol, slot, etc.). The network node 1800, by sending dedicated RRC signaling indicating transform precoding to be used in UL, can be manage or control the UEs in the cell to send UL transmissions using DFTS-OFDM. And other UEs can use CP- OFDM. By mixing both multiple access schemes for UEs within the same cell BW, highly robust scheduling performance (e.g., higher user throughput and/or cell throughput) for all PC UEs can be achieved at different radio and channel conditions (e.g., signal level such as SINR (signal to interference and noise ratio), etc. [0069] Specific Examples of RB allocation for CP-OFDM only case shall now be described. [0070] Tables 7 and 8 are specific examples of RB allocation for 200 MHz and 400 MHz channel BW of a cell, respectively. In these examples, SCS = 120 kHz is assumed. Therefore, the cell with 200 MHz BW has 132 RBs (for 120 kHz SCS) and the cell with 400 MHz BW has 264 RBs (for 120 kHz SCS). [0071] In each of the examples in Tables 7 and 8, it is assumed that the network node 1800 uses only CP-OFDM to schedule all the UEs in the cell in the same time resource. It is further assumed that there are 4 UEs in the cell to cover all hypothesis in terms of UE PC and UE location in the cell: - UE1 supports PC1 and located in cell edge, - UE2 supports any of PC2-PC5 (e.g., PC3) and located in cell edge, - UE3 supports PC1 and located in cell center, - UE4 supports any of PC2-PC5 (e.g., PC3) and located in cell center. [0072] If there are more than 4 UEs in the cell, then the RBs can further be divided by the network node 1800 for allocating to different UEs. The network node 1800 aims to allocate all or almost all RBs within the cell BW to the 4 UEs in the same time resource (e.g., in a symbol, slot etc.). Therefore, the allocated RBs to different UEs are orthogonal among the 4 UEs in the same time resource (e.g., symbol, slot, subframe etc.). The RBs allocated to the UEs based on their location and PC for CP-OFDM are shown in Table 7 for 200 MHz channel BW and in Table 8 for 400 MHz channel BW. The allocated RBs are expressed in terms of combination of parameters (RB_Start, L_CRB), which are described earlier. Also as stated earlier: RB_end = RB_Start + L_CRB – 1. For example (77,27) in Table 7 for UE PC2-PC5 (e.g., PC3) at cell center in 200 MHz cell BW means: RB_Start=77, L_CRB=27 and RBend = 77+27-1 = 103. In this example 27 RBs are allocated from RB number # 77 to RB number # 103. Table 7: A specific example of RB allocation (RB_Start, L_CRB) based on UE location, power class for 200 MHz channel BW with 120 kHz SCS RB allocation region: inner RB region or outer RB region determined by (RB_Start, L_CRB)

Table 8: A specific example of RB allocation (RBstart, LCRB) based on UE location, power class for 400 MHz channel BW with 120 kHz SCS RB allocation region: inner RB region or outer RB region determined by (RB_Start, L_CRB) E l i ll E l i ll

[0074] Tables 9 and 10 below are specific examples of RB allocation for 200 MHz and 400 MHz channel BW of the cell respectively. In these examples we also assume SCS = 120 kHz. [0075] The difference between Tables 7 and 8 is that in the examples in Tables 9 and 10, it is assumed that the network node uses only DFTS-OFDM to schedule all the UEs in the cell in the same time resource. It is also further assumed that there are 4 UEs in the cell to cover all hypothesis in terms of UE PC and UE location in the cell as described in previous examples (Tables 7-8). Almost all RBs are allocated and are orthogonal among the 4 UEs. The allocated RBs are also expressed in terms of combination of parameters (RB_Start, L_CRB). Table 9: A specific example of RB allocation (RB_Start, L_CRB) based on UE location, power class for 200 MHz channel BW with 120 kHz SCS RB allocation region: inner RB region or outer RB region determined by (RB_start, L_CRB) er

class for 400 MHz channel BW with 120 kHz SCS RB allocation region: inner RB region or outer RB region determined by (RB_start, L_CRB)

[0076] RB allocation examples for hybrid case (CP-OFDM or DFTS-OFDM) [0077] Tables 11 and 12 below are specific examples of RB allocation for 200 MHz and 400 MHz channel BW of the cell respectively. In these examples, SCS = 120 kHz is assumed. [0078] The main difference compared to previous examples (Tables 7-10) is that in the examples in Tables 11 and 12, it is assumed that the network node can use any one of the two MAS types (DFTS-OFDM and CP-OFDM) to schedule the same UE in the cell in the same time resource. However, the network node can use different MAS (DFTS-OFDM or CP-OFDM) to schedule different UEs in the cell in the same time resource. To cover all possible hypothesis in terms of UE PC, UE location in the cell and MAS type, we assume that there are 8 UEs in the cell for RB allocation in the same time resource: - UE1 supports PC1, located in cell edge and configured with DFTS-OFDM, - UE2 supports PC1, located in cell edge and configured with CP-OFDM, - UE3 supports any of PC2-PC5 (e.g., PC3), located in cell edge and configured with DFTS-OFDM, - UE4 supports any of PC2-PC5 (e.g., PC3), located in cell edge and configured with CP-OFDM, - UE5 supports PC1, located in in cell center and configured with DFTS-OFDM, - UE6 supports PC1, located in in cell center and configured with CP-OFDM, - UE7 supports any of PC2-PC5 (e.g., PC3), located in in cell center and configured with DFTS-OFDM, - UE8 supports any of PC2-PC5 (e.g., PC3), located in in cell center and configured with CP-OFDM. [0079] If there are more than 8 UEs in the cell, then the RBs can further be divided by the network node for allocating to different UEs. [0080] In these examples the RB allocation is also selected based on combination of parameters (RB_Start, L_CRB) as described earlier. Also as stated earlier: RB_end = RB_Start + L_CRB – 1. For example (74,15) in Table 11 means: RB_Start=74, L_CRB=15 and RB_end = 88. In this example, 15 RBs are allocated from RB number # 74 to RB number # 88. [0081] To ensure optimum performance (i.e., to minimize impact of MPR) the UE1-8 are allocated RBs as follows: ^ RB allocation for UEs in cell edge which may experience higher MPR (e.g., due to higher transmit power) compared to UEs in cell center: o UE1 (PC1) located in cell edge using DFTS is allocated inner RBs. o UE2 (PC1) located in cell edge using CP-OFDM is allocated outer RBs. o UE3 (PC2-5) located in cell edge using DFTS can be allocated inner or outer RBs because in this case any of inner set of RBs and outer set of RBs is fine. The outer RBs allocation may relieve inner RBs which can be allocated to scenario with higher MPR e.g., UE1 or UE4. o UE4 (PC2-5) located in cell edge using CP-OFDM is allocated inner RBs. ^ RB allocation for UEs in cell center which may experience lower or no MPR (e.g., due to lower transmit power) compared to UEs in cell edge: ^ UE5 (PC1) located in cell center using DFTS is allocated outer RBs. ^ UE6 (PC1) located in cell center using CP-OFDM is allocated inner RBs. ^ UE7 (PC2-5) located in cell center using DFTS is allocated outer RBs. ^ UE8 (PC2-5) located in cell center using CP-OFDM is allocated outer RBs. Table 11: A specific example of RB allocation (RBstart, LCRB) based on UE location, power class and multiple access scheme types (DFTS-OFDM or CP-OFDM) for 200 MHz channel BW with 120 kHz SCS RB allocation region: inner RB region or outer RB region determined by (RB_start, L_CRB) UE l ti n ll d UE l ti n ll nt r er

class and multiple access scheme types (DFTS-OFDM or CP-OFDM) for 400 MHz channel BW with 120 kHz SCS RB allocation region: inner RB region or outer RB region determined by (RB_start, L_CRB)

[0082] The examples in Tables 5-12 demonstrate that the RB allocation region within the channel BW of the cell (e.g., UE serving cell such as primary cell (PCell), primary secondary cell (PSCell), secondary cell (SCell), etc.) depends on at least three basic parameters: UE PC, UE geographical/physical location within the cell and the OFDM waveform type. By using the RB allocation methodology described herein, the following objectives are achieved because adverse impact of MPR on uplink transmission is alleviated or minimized: optimal usage of the RB resources, improved UE coverage in the cell and optimal cell/user throughput. [0083] In the above examples, to account for the MPR characteristic of DFTS-OFDM and CP-OFDM the RB resource allocation scheme employed by the BS can be summarized as follows: - For the UEs 1700 located in the cell edge or cell boundary: o If DFTS-OFDM is used for the uplink transmission, then the BS allocates the inner RBs within the cell BW (i.e., in center of cell BW in frequency domain). o If CP-OFDM is used for the uplink transmission, then the BS allocates the outer RBs within the cell BW (i.e., in edges of cell BW in frequency domain). o In the above cases (for both MAS type) the RB allocation is further dependent on the UE PC due to MRP characteristics e.g., ^ BS typically allocates smaller number of RBs for PC1 on cell edge so that effective UE transmit power after applying MPR can efficiently be utilized. PC2-PC5 are given larger number of RBs to efficiently use net power after MPR. - For the UEs 1700 located in the cell center or close to the BS: o If DFTS-OFDM is used for the uplink transmission, then the BS allocates the outer RBs within the cell BW (i.e., in edges of cell BW in frequency domain). o If CP-OFDM is used for the uplink transmission, then the BS allocates the inner RBs within the cell BW (i.e., in center of cell BW in frequency domain). o In the above cases (for both MAS type) the RB allocation is further dependent on the UE PC due to MRP characteristics e.g. ^ BS typically allocates larger number of RBs to PC1 UEs compared to PC2-5 UE to achieve comparable performance. [0084] The above is illustrated in Figure 8, which illustrates allocating RBs in a network having a cell center and a cell edge/cell boundary. Turning to Figure 8, in block 801, the network node 1800 determines whether the UE 1700 is located in a cell edge or a cell boundary. Alternatively, or additionally, the network node 1800 may determine whether the UE 1700 is located in the cell center or a region within a defined distance of the network node 1800. [0085] The network node 1800 proceeds to block 803 when the UE 1700 is located in the cell edge or the cell boundary. In block 803, the network node 1800 determines if discrete Fourier transform-spread orthogonal frequency division multiplexing (DFTS-OFDM) or cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) will be used for uplink transmission. [0086] When DFTS-OFDM is used, the network node 1800 in block 805 allocates inner resource blocks within the cell bandwidth. When CP-OFDM is used, the network node 1800 in block 807 allocates outer resource blocks within the cell bandwidth. [0087] The network node 1800 proceeds to block 809 when the UE 1700 is located in the cell center or the region within a defined distance of the network node 1800. In block 809, the network node 1800 determines if DFTS-OFDM or CP-OFDM will be used for uplink transmission. [0088] When DFTS-OFDM is used, the network node 1800 in block 811 allocates outer resource blocks within the cell bandwidth. When CP-OFDM is used, the network node 1800 in block 813 allocates inner resource blocks within the cell bandwidth. [0089] The network node 1800 (e.g., serving BS) allocates the RBs within the determined RB region along with other information (e.g., OFDM waveform type, etc.) to the UE 1700 for uplink transmission (e.g., via MAC-CE (medium access control- control element) or DCI (downlink control information) messages). The network node may further receive and decode the signals transmitted by the UE using the allocated RBs. [0090] An alternative of the above is illustrated in Figure 9, which illustrates an alternative of allocating RBs in a network having a cell center and a cell edge/cell boundary. Turning to Figure 9, in block 901, the network node 1800 determines whether the UE 1700 is located in a cell edge or a cell boundary. Alternatively, or additionally, the network node 1800 determines whether the UE 1700 is located in the cell center or the region within a defined distance of the network node 1800. [0091] The network node 1800 proceeds to block 903 when the UE 1700 is located in the cell edge or the cell boundary. In block 903, the network node 1800 determines if discrete Fourier transform-spread orthogonal frequency division multiplexing (DFTS-OFDM) or cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) will be used for uplink transmission. [0092] When DFTS-OFDM is used, the network node 1800 in block 905 allocates outer resource blocks within the cell bandwidth. When CP-OFDM is used, the network node 1800 in block 907 allocates inner resource blocks within the cell bandwidth. [0093] The network node 1800 proceeds to block 909 when the UE 1700 is located in the cell center or the region within a defined distance of the network node 1800. In block 909, the network node 1800 determines if DFTS-OFDM or CP-OFDM will be used for uplink transmission. [0094] When DFTS-OFDM is used, the network node 1800 in block 911 allocates inner resource blocks within the cell bandwidth. When CP-OFDM is used, the network node 1800 in block 913 allocates outer resource blocks within the cell bandwidth. [0095] Additionally, the network node 1800 (e.g., serving BS) allocates the RBs within the determined RB region along with other information (e.g., OFDM waveform type, etc.) to the UE 1700 for uplink transmission (e.g., via MAC-CE or DCI messages). The network node may further receive and decode the signals transmitted by the UE using the allocated RBs. [0096] Figure 10 illustrates a MPR scheduler in a network node 1800 (e.g., serving BS) for determining a multiple access scheme type (e.g., OFDM waveform) for uplink scheduling a UE 1700 based on the UE location within the serving cell, the UE power class, and available resource blocks. The network node 1800, using the MPR scheduler, which may be a separate module or integrated into the network node, determines the UE power class, the UE location, and available RBs and determines a MAS type to use. [0097] Thus, the network node (e.g., serving BS) determines suitable OFDM waveform (e.g., CP-OFDM, DFTS-OFDM etc.) for scheduling UEs in a cell based on (e.g., taking into account) at least the UE PC, available RBs (e.g., RB region within the channel BW in frequency) and the UE location within the cell (e.g., cell edge, cell center, etc.). The term available RBs refer to the RBs not currently allocated to any UE in the cell. For example, even after applying the methodology explained above with respect to Figure 5, there may be un-used or remaining RBs. The method of performed by the MPR scheduler of Figure 8 therefore may be used as complementary to the method performed by the MPR scheduler of Figure 5. The network node 1800 then allocates the available RBs along with the determined OFDM waveform to the UE 1700 for uplink transmission e.g., via MAC-CE or DCI messages. The network node may further receive and decode the signals transmitted by the UE 1700 using the allocated RBs and OFDM waveform. The corresponding scheduler implementation is shown in Figure 8. [0098] The network node 1800 can utilize the examples of RB allocation shown in Tables 5- 12. The main difference is that the network node 1800 has to first determine and use the available RBs in the cell BW as main input to the scheduler. [0099] Figure 11 illustrates operations the network node 1800 performs when determining a multiple access scheme type (e.g., OFDM waveform) for uplink scheduling a UE 1700 based on the UE location within the serving cell, the UE power class, and available resource blocks. [0100] Turning to Figure 11, in block 1101, the network node 1800 determines a user equipment, UE, power class of a UE 1700. For example, the network node 1800 can determine the UE PC in the UE capability comprising also UE power class transmitted by the UE 1700 to the network node via higher layer signaling such as radios resource control (RRC). The information may further indicate supported power classes for different frequency bands, for certain frequency range (e.g., FR1, FR2 etc.). The power class denotes or indicates the maximum output power (Pmax) supported by the UE e.g., for certain band, for certain FR etc. Pmax may also be called as nominal power etc. Pmax for certain PC may be characterized by one or more power class parameters e.g., max total radiated power (TRP), max effective isotropic radiated power (EIRP), minimum peak EIRP, minimum EIRP at certain spherical coverage etc. The PC parameters may further depend on e.g., frequency bands. For example, for PC1 the max TRP=35 dBm, max EIRP=55 dBm, minimum peak EIRP=40 dBm and minimum EIRP at 85^th percentile = 32 dBm for band n257 (2.65-2.95 GHz). In another example for PC3 the max TRP=23 dBm, max EIRP=43 dBm, minimum peak EIRP=22.4 dBm and minimum EIRP at 50th percentile = 11.5 dBm for the same band n257. [0101] In block 1103, the network node 1800 determines the UE location of the UE 1700. For example, the network node can determine the location of UEs in different geographical regions of the cell based on for example by comparing a signal level (e.g., signal strength such as path loss, RSRP etc.) between the UE 1700 and the serving BS, and signal level threshold. For example, if the RSRP measured by the UE 1700 is below or equal to certain threshold (G) then the UE 1700 is assumed to be in the cell center; otherwise, the UE 1700 is assumed to be in the cell edge. In another example the network node can further determine the location of UEs within the cell based on one or more positioning mechanisms e.g., GNSS (global navigation satellite system), etc. [0102] The different geographical regions can be determined by the network node 1800. This is illustrated in Figure 12, where in block 1201, the network node 1800 determines a plurality of geographic regions within a cell based on one or more parameters. The one or more parameters include one or more of: cell size; cell type; cell coverage area; a measured signal level; and a number of UEs in the cell. [0103] Returning to Figure 11, in block 1105, the network node 1800 determines available resource blocks for allocation to the UE 1700. The network node 1800 determines available resource blocks for the UE 1700 for e.g., UL transmission based on the UE power class and the UE location. For example, in Table 5 when the UE location is within the cell edge and the UE power class is PCB, only outer resource blocks are available. [0104] In block 1107, the network node 1800 determines a multiple access scheme, MAS, type for the UE 1700 based on the UE power class, the UE location, and available resource blocks. For example, in Table 5 when the UE location is within the cell edge and the UE power class is PC_B, and only outer resource blocks are available, then the MAS type is OFDM-2. Similarly, if only inner resource blocks are available, then the MAS type is OFDM-1. [0105] In block 1209, the network node 1800 allocates one or more resource blocks of the available resource blocks for the UE 1700 along with the MAS type determined to the UE 1700 for uplink transmission. [0106] Figure 13 illustrates an embodiment of determining the MAS type for the UE 1700. Turning to Figure 13, in block 1301, the network node 1800 determines which geographic region the UE 1700 is located within. [0107] In block 1303, the network node 1800 determines available resource blocks based on the geographic location the UE 1700 is located within and the UE power class. [0108] In block 1305, the network node 1800 determines a MAS type to use based on the UE power class, the geographic region the UE 1700 is located within, and the available resource blocks. [0109] In the above examples, to account for the MPR characteristic of DFTS-OFDM and CP-OFDM the RB resource allocation scheme employed by the BS can be summarized as follows: - For the UEs 1700 located in the cell edge or cell boundary: o If the BS has inner RBs available within the cell BW (i.e., in center of cell BW in frequency domain), then DFTS-OFDM is used for the uplink transmission. o If the BS has outer RBs available within the cell BW (i.e., in edges of cell BW in frequency domain), then CP-OFDM is used for the uplink transmission. o In the above cases (for both MAS type) the RB allocation is further dependent on the UE PC due to MRP characteristics e.g., - For the UEs 1700 located in the cell center or close to the BS: o If the BS has outer RBs available within the cell BW (i.e., in edges of cell BW in frequency domain), then DFTS-OFDM is used for the uplink transmission. o If the BS has inner RBs available within the cell BW (i.e., in center of cell BW in frequency domain), then CP-OFDM is used for the uplink transmission. [0110] The above is illustrated in Figure 14, which illustrates allocating RBs in a network having a cell center and a cell edge/cell boundary. Turning to Figure 14, in block 1401, the network node 1800 determines whether the UE 1700 is located in a cell edge or a cell boundary. Alternatively, or additionally, the network node 1800 determines whether the UE 1700 is located in the cell center or the region within a defined distance of the network node 1800. [0111] The network node 1800 proceeds to block 1403 when the UE 1700 is located in the cell edge or the cell boundary. In block 1403, the network node 1800 determines if inner RBs or outer RBs are available within the cell bandwidth. [0112] When inner RBs are available within the cell bandwidth, the network node 1800 in block 1405 uses DFTS-OFDM for uplink transmissions. When outer RBs are available within the cell bandwidth, the network node 1800 in block 1407 uses CP-OFDM for uplink transmissions. [0113] The network node 1800 proceeds to block 1409 when the UE 1700 is located in the cell center or the region within a defined distance of the network node 1800. In block 1409, the network node 1800 determines if inner RBs or outer RBs are available within the cell bandwidth. [0114] When inner RBs are available within the cell bandwidth, the network node 1800 in block 1411 uses DFTS-OFDM for uplink transmissions. When outer RBs are available within the cell bandwidth, the network node 1800 in block 1413 uses CP-OFDM for uplink transmissions. [0115] In an alternate embodiment, to account for the MPR characteristic of DFTS-OFDM and CP-OFDM the RB resource allocation scheme employed by the BS can be summarized as follows: - For the UEs 1700 located in the cell edge or cell boundary: o If the BS has inner RBs available within the cell BW (i.e., in center of cell BW in frequency domain), then CP-OFDM is used for the uplink transmission. o If the BS has outer RBs available within the cell BW (i.e., in edges of cell BW in frequency domain), then DFTS-OFDM is used for the uplink transmission. o In the above cases (for both MAS type) the RB allocation is further dependent on the UE PC due to MRP characteristics e.g., - For the UEs 1700 located in the cell center or the region within a defined distance of the BS: o If the BS has inner RBs available within the cell BW (i.e., in edges of cell BW in frequency domain), then CP-OFDM is used for the uplink transmission. o If the BS has outer RBs available within the cell BW (i.e., in center of cell BW in frequency domain), then DFTS-OFDM is used for the uplink transmission. [0116] The above is illustrated in Figure 15, which illustrates allocating RBs in a network having a cell center and a cell edge/cell boundary. Turning to Figure 15, in block 1501, the network node 1800 determines whether the UE 1700 is located in a cell edge or a cell boundary. Alternatively, or additionally, the network node 1800 determines whether the UE 1700 is located in the cell center or the region within a defined distance of the network node 1800. [0117] The network node 1800 proceeds to block 1503 when the UE 1700 is located in the cell edge or the cell boundary. In block 1503, the network node 1800 determines if inner RBs or outer RBs are available within the cell bandwidth. [0118] When inner RBs are available within the cell bandwidth, the network node 1800 in block 1505 uses CP-OFDM for uplink transmissions. When outer RBs are available within the cell bandwidth, the network node 1800 in block 1507 uses DFTS-OFDM for uplink transmissions. [0119] The network node 1800 proceeds to block 1509 when the UE 1700 is located in the cell center or the region within a defined distance of the network node 1800. In block 1509, the network node 1800 determines if inner RBs or outer RBs are available within the cell bandwidth. [0120] When inner RBs are available within the cell bandwidth, the network node 1800 in block 1511 uses DFTS-OFDM for uplink transmissions. When outer RBs are available within the cell bandwidth, the network node 1800 in block 1513 uses CP-OFDM for uplink transmissions. [0121] As can be seen from the foregoing, the various embodiments described herein provide a systematic UL resource allocation mechanism for UEs associated with different PCs, waveforms, and geographical location. Some of the various embodiments enable allocating UEs with inner RB region within the cell BW if they are at cell edge and the bandwidth edge (outer) RBs within the cell BW if they are at cell center while using DFTS-OFDM waveform. The RB allocation (e.g., number of RBs) is further based on the UE PC. Other embodiments of the various embodiments enable allocating UEs with outer RBs within the cell BW if they are at cell edge and with inner RBs within the cell BW if they are located at cell center while using CP- OFDM waveform. The RB allocation (e.g., number of RBs) is further based on the UE PC. [0122] Some of the various embodiments provide a mechanism for utilizing both CP-OFDM and DFTS-OFDM waveforms simultaneously so that cell edge and cell center UEs of different PCs can be scheduled with better performance. [0123] Figure 16 shows an example of a communication system 1600 in accordance with some embodiments. [0124] In the example, the communication system 1600 includes a telecommunication network 1602 that includes an access network 1604, such as a radio access network (RAN), and a core network 1606, which includes one or more core network nodes 1608. The access network 1604 includes one or more access network nodes, such as network nodes 1610A and 1610B (one or more of which may be generally referred to as network nodes 1610), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1612A, 1612B, 1612C, and 1612D (one or more of which may be generally referred to as UEs 1612) to the core network 1606 over one or more wireless connections. [0125] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1600 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1600 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0126] The UEs 1612 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1610 and other communication devices. Similarly, the network nodes 1610 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1612 and/or with other network nodes or equipment in the telecommunication network 1602 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1602. [0127] In the depicted example, the core network 1606 connects the network nodes 1610 to one or more hosts, such as host 1616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1606 includes one more core network node (e.g., core network node 1608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0128] The host 1616 may be under the ownership or control of a service provider other than an operator or provider of the access network 1604 and/or the telecommunication network 1602 and may be operated by the service provider or on behalf of the service provider. The host 1616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0129] As a whole, the communication system 1600 of Figure 16 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. [0130] In some examples, the telecommunication network 1602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1602. For example, the telecommunications network 1602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. [0131] In some examples, the UEs 1612 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1604. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). [0132] In the example, the hub 1614 communicates with the access network 1604 to facilitate indirect communication between one or more UEs (e.g., UE 1612C and/or 1612D) and network nodes (e.g., network node 1610B). In some examples, the hub 1614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1614 may be a broadband router enabling access to the core network 1606 for the UEs. As another example, the hub 1614 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1610, or by executable code, script, process, or other instructions in the hub 1614. As another example, the hub 1614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1614 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1614 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [0133] The hub 1614 may have a constant/persistent or intermittent connection to the network node 1610B. The hub 1614 may also allow for a different communication scheme and/or schedule between the hub 1614 and UEs (e.g., UE 1612C and/or 1612D), and between the hub 1614 and the core network 1606. In other examples, the hub 1614 is connected to the core network 1606 and/or one or more UEs via a wired connection. Moreover, the hub 1614 may be configured to connect to an M2M service provider over the access network 1604 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1610 while still connected via the hub 1614 via a wired or wireless connection. In some embodiments, the hub 1614 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1610B. In other embodiments, the hub 1614 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1610B, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0134] Figure 17 shows a UE 1700 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0135] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [0136] The UE 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a power source 1708, a memory 1710, a communication interface 1712, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 17. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [0137] The processing circuitry 1702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1710. The processing circuitry 1702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1702 may include multiple central processing units (CPUs). [0138] In the example, the input/output interface 1706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0139] In some embodiments, the power source 1708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1708 may further include power circuitry for delivering power from the power source 1708 itself, and/or an external power source, to the various parts of the UE 1700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1708 to make the power suitable for the respective components of the UE 1700 to which power is supplied. [0140] The memory 1710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read- only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1710 includes one or more application programs 1714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1716. The memory 1710 may store, for use by the UE 1700 , any of a variety of various operating systems or combinations of operating systems. [0141] The memory 1710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1710 may allow the UE 1700 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1710, which may be or comprise a device-readable storage medium. [0142] The processing circuitry 1702 may be configured to communicate with an access network or other network using the communication interface 1712. The communication interface 1712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1722. The communication interface 1712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1718 and/or a receiver 1720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1718 and receiver 1720 may be coupled to one or more antennas (e.g., antenna 1722) and may share circuit components, software or firmware, or alternatively be implemented separately. [0143] In the illustrated embodiment, communication functions of the communication interface 1712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0144] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 17 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0145] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. [0146] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1700 shown in Figure 17. [0147] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0148] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [0149] Figure 18 shows a network node 1800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). [0150] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). [0151] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). [0152] The network node 1800 includes a processing circuitry 1802, a memory 1804, a communication interface 1806, and a power source 1808. The network node 1800 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1804 for different RATs) and some components may be reused (e.g., a same antenna 1810 may be shared by different RATs). The network node 1800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1800. [0153] The processing circuitry 1802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1800 components, such as the memory 1804, to provide network node 1800 functionality. [0154] In some embodiments, the processing circuitry 1802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1802 includes one or more of radio frequency (RF) transceiver circuitry 1812 and baseband processing circuitry 1814. In some embodiments, the radio frequency (RF) transceiver circuitry 1812 and the baseband processing circuitry 1814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1812 and baseband processing circuitry 1814 may be on the same chip or set of chips, boards, or units. [0155] The memory 1804 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1802. The memory 1804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1802 and utilized by the network node 1800. The memory 1804 may be used to store any calculations made by the processing circuitry 1802 and/or any data received via the communication interface 1806. In some embodiments, the processing circuitry 1802 and memory 1804 is integrated. [0156] The communication interface 1806 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1806 comprises port(s)/terminal(s) 1816 to send and receive data, for example to and from a network over a wired connection. The communication interface 1806 also includes radio front-end circuitry 1818 that may be coupled to, or in certain embodiments a part of, the antenna 1810. Radio front-end circuitry 1818 comprises filters 1820 and amplifiers 1822. The radio front-end circuitry 1818 may be connected to an antenna 1810 and processing circuitry 1802. The radio front-end circuitry may be configured to condition signals communicated between antenna 1810 and processing circuitry 1802. The radio front-end circuitry 1818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1820 and/or amplifiers 1822. The radio signal may then be transmitted via the antenna 1810. Similarly, when receiving data, the antenna 1810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1818. The digital data may be passed to the processing circuitry 1802. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0157] In certain alternative embodiments, the network node 1800 does not include separate radio front-end circuitry 1818, instead, the processing circuitry 1802 includes radio front-end circuitry and is connected to the antenna 1810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1812 is part of the communication interface 1806. In still other embodiments, the communication interface 1806 includes one or more ports or terminals 1816, the radio front-end circuitry 1818, and the RF transceiver circuitry 1812, as part of a radio unit (not shown), and the communication interface 1806 communicates with the baseband processing circuitry 1814, which is part of a digital unit (not shown). [0158] The antenna 1810 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1810 may be coupled to the radio front-end circuitry 1818 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1810 is separate from the network node 1800 and connectable to the network node 1800 through an interface or port. [0159] The antenna 1810, communication interface 1806, and/or the processing circuitry 1802 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1810, the communication interface 1806, and/or the processing circuitry 1802 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [0160] The power source 1808 provides power to the various components of network node 1800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1800 with power for performing the functionality described herein. For example, the network node 1800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1808. As a further example, the power source 1808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [0161] Embodiments of the network node 1800 may include additional components beyond those shown in Figure 18 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1800 may include user interface equipment to allow input of information into the network node 1800 and to allow output of information from the network node 1800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1800. [0162] Figure 19 is a block diagram of a host 1900, which may be an embodiment of the host 1616 of Figure 16, in accordance with various aspects described herein. As used herein, the host 1900 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1900 may provide one or more services to one or more UEs. [0163] The host 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input/output interface 1906, a network interface 1908, a power source 1910, and a memory 1912. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 17 and 18, such that the descriptions thereof are generally applicable to the corresponding components of host 1900. [0164] The memory 1912 may include one or more computer programs including one or more host application programs 1914 and data 1916, which may include user data, e.g., data generated by a UE for the host 1900 or data generated by the host 1900 for a UE. Embodiments of the host 1900 may utilize only a subset or all of the components shown. The host application programs 1914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1914 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1900 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1914 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [0165] Figure 20 is a block diagram illustrating a virtualization environment 2000 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. [0166] Applications 2002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [0167] Hardware 2004 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2008A and 2008B (one or more of which may be generally referred to as VMs 2008), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 2006 may present a virtual operating platform that appears like networking hardware to the VMs 2008. [0168] The VMs 2008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2006. Different embodiments of the instance of a virtual appliance 2002 may be implemented on one or more of VMs 2008, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [0169] In the context of NFV, a VM 2008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 2008, and that part of hardware 2004 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 2008 on top of the hardware 2004 and corresponds to the application 2002. [0170] Hardware 2004 may be implemented in a standalone network node with generic or specific components. Hardware 2004 may implement some functions via virtualization. Alternatively, hardware 2004 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 2010, which, among others, oversees lifecycle management of applications 2002. In some embodiments, hardware 2004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 2012 which may alternatively be used for communication between hardware nodes and radio units. [0171] Figure 21 shows a communication diagram of a host 2102 communicating via a network node 2104 with a UE 2106 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1612A of Figure 16 and/or UE 1700 of Figure 17), network node (such as network node 1610A of Figure 16 and/or network node 1800 of Figure 18), and host (such as host 1616 of Figure 16 and/or host 1900 of Figure 19) discussed in the preceding paragraphs will now be described with reference to Figure 21. [0172] Like host 1900, embodiments of host 2102 include hardware, such as a communication interface, processing circuitry, and memory. The host 2102 also includes software, which is stored in or accessible by the host 2102 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 2106 connecting via an over-the-top (OTT) connection 2150 extending between the UE 2106 and host 2102. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2150. [0173] The network node 2104 includes hardware enabling it to communicate with the host 2102 and UE 2106. The connection 2160 may be direct or pass through a core network (like core network 1406 of Figure 14) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0174] The UE 2106 includes hardware and software, which is stored in or accessible by UE 2106 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2106 with the support of the host 2102. In the host 2102, an executing host application may communicate with the executing client application via the OTT connection 2150 terminating at the UE 2106 and host 2102. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 2150 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 2150. [0175] The OTT connection 2150 may extend via a connection 2160 between the host 2102 and the network node 2104 and via a wireless connection 2170 between the network node 2104 and the UE 2106 to provide the connection between the host 2102 and the UE 2106. The connection 2160 and wireless connection 2170, over which the OTT connection 2150 may be provided, have been drawn abstractly to illustrate the communication between the host 2102 and the UE 2106 via the network node 2104, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0176] As an example of transmitting data via the OTT connection 2150, in step 2108, the host 2102 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 2106. In other embodiments, the user data is associated with a UE 2106 that shares data with the host 2102 without explicit human interaction. In step 2110, the host 2102 initiates a transmission carrying the user data towards the UE 2106. The host 2102 may initiate the transmission responsive to a request transmitted by the UE 2106. The request may be caused by human interaction with the UE 2106 or by operation of the client application executing on the UE 2106. The transmission may pass via the network node 2104, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2112, the network node 2104 transmits to the UE 2106 the user data that was carried in the transmission that the host 2102 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2114, the UE 2106 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2106 associated with the host application executed by the host 2102. [0177] In some examples, the UE 2106 executes a client application which provides user data to the host 2102. The user data may be provided in reaction or response to the data received from the host 2102. Accordingly, in step 2116, the UE 2106 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 2106. Regardless of the specific manner in which the user data was provided, the UE 2106 initiates, in step 2118, transmission of the user data towards the host 2102 via the network node 2104. In step 2120, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2104 receives user data from the UE 2106 and initiates transmission of the received user data towards the host 2102. In step 2122, the host 2102 receives the user data carried in the transmission initiated by the UE 2106. [0178] In an example scenario, factory status information may be collected and analyzed by the host 2102. As another example, the host 2102 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2102 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2102 may store surveillance video uploaded by a UE. As another example, the host 2102 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 2102 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. [0179] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2150 between the host 2102 and UE 2106, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2102 and/or UE 2106. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2150 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2150 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2104. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 2102. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2150 while monitoring propagation times, errors, etc. [0180] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [0181] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Claims

CLAIMS 1. A method performed by a network node (1610A, 1610B, 1800, 2002, 2104) for determining resource block allocation for scheduling a user equipment, UE, (1612A, 1612B, 1612C, 1612D, 1700, 2002, 2106) in an uplink communication, the method comprising: determining (601) a user equipment, UE, power class of a UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106); determining (603) a UE location of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106); determining (605) a multiple access scheme, MAS, type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106); determining (607) a resource block allocation for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) based on the UE power class, the UE location, and the MAS type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106); and allocating (609) the resource block for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106).

2. The method of Claim 1, wherein determining the UE power class of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises receiving a UE capability of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) including the UE power class of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106).

3. The method of Claim 2, wherein receiving the UE capability of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises receiving UE power classes the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) supports for different frequency bands.

4. The method of Claim 3 wherein at least one of the UE power classes indicates a maximum output power, Pmax, supported by the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) for certain frequency bands.

5. The method of Claim 4, wherein Pmax for a power class is characterized by one or more power class parameters comprising one or more of: a maximum total radiated power, TRP; a maximum effective isotropic radiated power, EIRP; a minimum peak EIRP; and a minimum EIRP for a specified spherical coverage.

6. The method of Claim 5 wherein a plurality of the one or more power class parameters is different for different frequency bands.

7. The method of any of Claims 1-6, further comprising determining (701) a plurality of geographic regions within a cell based on one or more parameters.

8. The method of Claim 7, wherein determining the plurality of geographic regions within the cell based on one or more parameters comprises determining the plurality of geographic regions within the cell based on one or more of: cell size; cell type; cell coverage area; a measured signal level; and a number of UEs in the cell.

9. The method of any of Claims 7-8, wherein determining the UE location comprises determining in which geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within.

10. The method of Claim 9, wherein determining in which geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within comprises comparing a signal level between the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) and a serving base station and a signal level threshold.

11. The method of Claim 9, wherein determining in which geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within comprises determining the UE location based on one or more positioning mechanisms.

12. The method of any of Claims 1-9, wherein determining the MAS type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises determining which MAS type is to be used for uplink transmissions by the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106).

13. The method of any of Claims 7-12, wherein each geographic region of the plurality of geographic regions includes one of a cell edge or cell boundary or a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104) and wherein determining the resource block allocation for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) based on the UE power class, the UE location, and the MAS type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises: determining (801) whether the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in a cell edge or cell boundary or is located in a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary, determining (803) whether the MAS type is discrete Fourier transform-spread orthogonal frequency division multiplexing (DFTS-OFDM) or cyclic prefix orthogonal frequency division multiplexing (CP-OFDM); allocating (805) inner RBs within a cell bandwidth when the MAS type is DFTS-OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; allocating (807) outer RBs within the cell bandwidth when the MAS type is CP-OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104), determining (809) whether the MAS type is discrete Fourier transform-spread orthogonal frequency division multiplexing (DFTS-OFDM) or cyclic prefix orthogonal frequency division multiplexing (CP-OFDM); allocating (811) outer RBs within the cell bandwidth when the MAS type is DFTS- OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); and allocating (813) inner RBs within the cell bandwidth when the MAS type is CP-OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104).

14. The method of any of Claims 7-12, wherein each geographic region of the plurality of geographic regions includes one of a cell edge or cell boundary or a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104) and wherein determining the resource block allocation for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) based on the UE power class, the UE location, and the MAS type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises: determining (901) whether the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in a cell edge or cell boundary or is located in a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary, determining (903) whether the MAS type is discrete Fourier transform-spread orthogonal frequency division multiplexing (DFTS-OFDM) or cyclic prefix orthogonal frequency division multiplexing (CP-OFDM); allocating (905) outer RBs within a cell bandwidth when the MAS type is DFTS-OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; allocating (907) inner RBs within the cell bandwidth when the MAS type is CP-OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104), determining (909) whether the MAS type is discrete Fourier transform-spread orthogonal frequency division multiplexing (DFTS-OFDM) or cyclic prefix orthogonal frequency division multiplexing (CP-OFDM); allocating (911) inner RBs within the cell bandwidth when the MAS type is DFTS- OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); and allocating (913) outer RBs within the cell bandwidth when the MAS type is CP-OFDM and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104).

15. A method performed by a network node (1610A, 1610B, 1800, 2002, 2104) for determining a multiple access scheme, MAS, type for scheduling a user equipment, UE, (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) in an uplink communication, the method comprising: determining (1101) a user equipment, UE, power class of a UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106); determining (1103) a UE location of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106); determining (1105) available resource blocks for allocation to the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106); determining (1107) a multiple access scheme, MAS, type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) based on the UE power class, the UE location, and the available resource blocks; and allocating (1109) one or more resource blocks of the available resource blocks for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) along with the MAS type determined to the UE for uplink transmission.

16. The method of Claim 17, wherein determining the UE power class of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises receiving a UE capability of the UE including the UE power class of the UE.

17. The method of Claim 16, wherein receiving the UE capability of the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises receiving UE power classes the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) supports for different frequency bands.

18. The method of Claim 17 wherein at least one of the UE power classes indicates a maximum output power, Pmax, supported by the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) for certain frequency bands.

19. The method of Claim 18, wherein Pmax for a power class is characterized by one or more power class parameters comprising one or more of: a maximum total radiated power, TRP; a maximum effective isotropic radiated power, EIRP; a minimum peak EIRP; and a minimum EIRP for a specified spherical coverage.

20. The method of Claim 19 wherein a plurality of the one or more power class parameters is different for different frequency bands.

21. The method of any of Claims 15-20, further comprising determining (1201) a plurality of geographic regions within a cell based on one or more parameters.

22. The method of Claim 21, wherein determining the plurality of geographic regions within the cell based on one or more parameters comprises determining the plurality of geographic regions within the cell based on one or more of: cell size; cell type; cell coverage area; a measured signal level; and a number of UEs in the cell.

23. The method of any of Claims 21-22, wherein determining the UE location comprises determining in which geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within.

24. The method of Claim 23, wherein determining in which geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within comprises comparing a signal level between the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) and a serving base station and a signal level threshold.

25. The method of Claim 23, wherein determining in which geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within comprises determining the UE location based on one or more positioning mechanisms.

26. The method of any of Claims 15-23, wherein determining the MAS type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) based on the UE power class, the UE location, and the available resource blocks for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) comprises: determining (1301) which geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106)is located within; determining (1303) available resource blocks based on the geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within and the UE power class; determining (1305) a MAS type to use based on the UE power class, the geographic region the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located within, and the available resource blocks.

27. The method of any of Claims 23-25, wherein each geographic region of the plurality of geographic regions includes one of a cell edge or cell boundary or a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104) and wherein determining the MAS type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) based on the UE power class, the UE location, and the available resources comprises: determining (1401) whether the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in a cell edge or cell boundary or is located in a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary, determining (1403) whether inner RBs within a cell bandwidth or outer RBs with the cell bandwidth are available; using (1405) discrete Fourier transform-spread orthogonal frequency division multiplexing, DFTS-OFDM, when inner RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; using (1407) cyclic prefix orthogonal frequency division multiplexing, CP-OFDM, when outer RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104), determining (1409) whether inner RBs within the cell bandwidth or outer RBs with the cell bandwidth are available; using (1411) CP-OFDM when inner RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); and using (1413) DFTS-OFMD when outer RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104).

28. The method of any of Claims 23-25, wherein each geographic region of the plurality of geographic regions includes one of a cell edge or cell boundary or a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104) and wherein determining the MAS type for the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) based on the UE power class, the UE location, and the available resources comprises: determining (1501) whether the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in a cell edge or cell boundary or is located in a cell center or a region within a defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary, determining (1503) whether inner RBs within a cell bandwidth or outer RBs with the cell bandwidth are available; using (1505) cyclic prefix orthogonal frequency division multiplexing, CP-OFDM, when inner RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; using (1507) discrete Fourier transform-spread orthogonal frequency division multiplexing, DFTS-OFDM, when outer RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell edge or the cell boundary; responsive to determining the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104), determining (1509) whether inner RBs within the cell bandwidth or outer RBs with the cell bandwidth are available; using (1511) DFTS-OFDM when inner RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104); and using (1513) CP-OFMD when outer RBs are available within the cell bandwidth and the UE (1612A, 1612B,1612C, 1612D, 1700, 2002, 2106) is located in the cell center or the region within the defined distance of the network node (1610A, 1610B, 1800, 2002, 2104).

29. A network node (1610A, 1610B, 1800, 2002, 2104) adapted to perform according to any of claims 1-28.

30. A network node (1610A, 1610B, 1800, 2002, 2104) comprising: processing circuitry (1802); and memory (1804) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node to perform operations according to any of Claims 1-28.

31. A computer program comprising program code to be executed by processing circuitry (1802) of a network node (1610A, 1610B, 1800, 2002, 2104), whereby execution of the program code causes the network node (1610A, 1610B, 1800, 2002, 2104) to perform operations according to any of Claims 1-28.

32. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1802) of a network node (1610A, 1610B, 1800, 2002, 2104), whereby execution of the program code causes the network node (1610A, 1610B, 1800, 2002, 2104) to perform operations according to any of Claims 1-28.