WO2021173061A1

WO2021173061A1 - Enabling new physical downlink control channel aggregation levels for reduced capability user equipment

Info

Publication number: WO2021173061A1
Application number: PCT/SE2021/050149
Authority: WO
Inventors: Mohammad MOZAFFARI; Anders Wallén; Kittipong KITTICHOKECHAI; Yi-Pin Eric Wang; Yutao Sui; Andreas HÖGLUND
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-02-27
Filing date: 2021-02-23
Publication date: 2021-09-02

Abstract

A method (1200) performed by a wireless device (110) for decoding a physical downlink control channel, PDCCH, candidate is provided. The method includes the wireless device being configured (1202) with an aggregation level that is not a power of 2. The aggregation level is a number of control channel elements (CCEs) used per 0PDCCH candidate. The wireless device decodes (1204) at least one PDCCH candidate using the aggregation level that is not a power of 2.

Description

ENABLING NEW PHYSICAL DOWNLINK CONTROL CHANNEL AGGREGATION LEVELS FOR REDUCED CAPABILITY USER EQUIPMENT

TECHNICAL FIELD

The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for enabling new Physical Downlink Control Channel aggregation levels for reduced capability user equipment.

BACKGROUND

The next paradigm shift in processing and manufacturing is the Industry 4.0, in which factories are automated and made much more flexible and dynamic with the help of wireless connectivity. This includes real-time control of robots and machines using time-critical machine-type communication (cMTC) and improved observability, control, and error detection with the help of large numbers of more simple actuators and sensors (e.g., massive machine-type communication (mMTC)).

For cMTC support, Ultra-Reliable Low Latency Communications (URLLC) was introduced in 3^rd Generation Partnership Project (3GPP) Release 15 for both Long Term Evolution (LTE) and New Radio (NR), and NR URLLC is further enhanced in Release 16 within the enhanced URLLC (eURLLC) and Industrial Internet-of-Things (IoT) work items.

For mMTC and low power wide area (LPWA) support, 3GPP introduced both narrowband Internet-of-Things (NB-IoT) and long term evolution for machine-type communication (LTE-MTC or LTE-M) in Release 13. These technologies have been further enhanced through all releases up until and including the ongoing Release 16 work. NR was introduced in 3GPP Release 15 and focused mainly on the enhanced mobile broadband (eMBB) and cMTC. For Release 17, however, an NR user equipment (UE) type with lower capabilities will likely be introduced since it is supported and proposed by many companies. The intention is to have an MTC version of NR (i.e., Reduced capability NR device (NR-RedCap)) that is mid-end, filling the gap between eMBB NR and NB-IoT/LTE-M. One goal of this approach is to provide more efficient inband operation with URLLC in industrial use cases.

Low-cost or low-complexity UE implementation is needed for the 5^th Generation (5G) system (e.g., for massive industrial sensors deployment or wearables). Currently, NR-RedCap (Reduced capability NR device) is used as the running name for the discussion of such low-complexity UEs in 3GPP. See , RP- 193238, New SID on support of reduced capability NR devices.

NR-RedCap is a new feature that is currently under discussion and could be introduced as early as in 3GPP Release 17. NR-RedCap is intended for use cases that do not require a device to support full-fledged NR capability and International Mobile Telecommunications-2020 (IMT-2020) performance requirements. For example, the data rate does not need to reach above 1 Gbps, and the latency does not need to be as low as 1 ms. By relaxing the data rate and latency targets, NR-RedCap allows low-cost or low-complexity UE implementation. In 3GPP Release 15, an NR UE is required to support 100 MHz carrier bandwidth in frequency range 1 (from 410 MHz to 7125 MHz) and 200 MHz carrier bandwidth in frequency range 2 (from 24.25 GHz to 52.6 GHz). For NR-RedCap UEs, supporting 100 MHz or 200 MHz bandwidth is superfluous. For example, a UE bandwidth of 8.64 MHz might be sufficient if the use cases do not require a data rate higher than 20 Mbps. Reduced UE bandwidth results in reduced complexity and possibly reduced energy consumption as well.

NR Physical Downlink Control Channel (PDCCH)

PDCCH carries downlink control information (DCI). PDCCHs are transmitted in control resource sets (CORESETs), which span over one, two, or three contiguous Orthogonal Frequency Division Multiplexing (OFDM) symbols over multiple resource blocks (RBs). A PDCCH is carried by 1, 2, 4, 8, or 16 control channel elements (CCEs). Each CCE is composed of 6 resource element groups (REGs) and each REG is 12 resource elements (REs) in one OFDM symbol (i.e., one REG is made up of one resource block) as shown in Figure 1 below.

FIGURE 1 illustrates an example of a CORESET. In the example of FIGURE 1, 36 RBs are used.

In order to receive DCI, a UE needs to blindly decode PDCCH candidates potentially transmitted from the network using one or more search spaces. A search space consists of a set of PDCCH candidates where each candidate can occupy multiple CCEs. The number of CCEs used for a PDCCH candidate is referred to as aggregation level (AL), which in NR. can be 1, 2, 4, 8, or 16. A higher AL provides higher coverage.

There currently exist certain challenges. For instance, in NR. different ALs can be used for PDCCH transmissions. Currently, possible NR. PDCCH ALs are { 1, 2, 4, 8, 16}. A high AL provides better coverage than a low AL and thus may be more suitable for larger cells, extreme coverage scenarios, and for coverage compensation for reduced capability UEs. A high AL, however, generally requires larger bandwidth as it consists of more CCEs. For example, to support AL 16 in a two-symbol CORESET, and 30 kHz subcarrier spacing (SCS), the bandwidth should be at least 17.28 MHz. Table 1 and Table 2 below present the minimum bandwidth required for different ALs for different CORESET durations.

Table 1 : Minimum required bandwidth for different ALs for 30 kHz SCS.

Table 2: Minimum required bandwidth for different ALs for 15 kHz SCS.

As can be seen from Table 1 and Table 2 above, the bandwidth required for supporting an AL depends on the SCS, CORESET duration, and AL (i.e., number of CCEs). Depending on the bandwidth of NR-RedCap EEs, some of the current AL- CORESET configurations may not be supported. For instance, if the bandwidth of an NR-RedCap EE in frequency range 1 (FR1) is 10MHz, the following configurations will not be feasible in the current NR. CORSET configurations:

• AL 16 for 30 kHz SCS, regardless of CORESET duration; · AL 8 for 30 kHz SCS, one-symbol CORESET duration; and

• AL 16 for 15 kHz SCH, one-symbol CORESET duration.

Using lower ALs results in coverage degradation. For instance, the coverage of AL 8 is approximately 3 dB lower than that of AL 16. Meanwhile, in order to compensate for the PDCCH coverage degradation due to reduced EE complexity (e.g., reduced number of antennas), high ALs are useful (e.g., higher AL levels than 16 may be needed).

In addition, to limit the EE complexity, there is a constraint on the number of non-overlapping CCEs that the EE needs to monitor per time unit. This CCE limit is lower for lower capability EEs. In this regard, there is a tradeoff between coverage and EE complexity in terms of the AL (assuming that lower ALs should still be included for optimal performance in good coverage). Due to the CCE limit, it may not be possible to configure high ALs, which can prevent achieving high coverage. SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. In one aspect, the present disclosure describes solutions for supporting high and/or new PDCCH ALs for reduced capability UEs to ensure sufficient coverage. New PDCCH ALs are enabled to provide sufficient coverage and flexibility for supporting reduced capability UEs that have limitations on bandwidth, number of antennas, and/or number of CCE monitoring. As one example, new ALs are disclosed for coverage maximization of reduced capability UEs. As another example, new ALs are disclosed to increase flexibility for handling tradeoff between coverage and CCE limit.

According to certain embodiments, a method by a wireless device for decoding a PDCCH candidate includes the wireless device being configured with an aggregation level that is not a power of 2, The aggregation level is a number of CCEs used per PDCCH candidate. The wireless device decodes at least one PDCCH candidate using the aggregation level that is not a power of 2.

According to certain embodiments, a wireless device for decoding a PDCCH candidate includes processing circuitry configured to be configured with an aggregation level that is not a power of 2. The aggregation level is a number of control channel elements, CCEs, used per PDCCH candidate. The processing circuitry is configured to decode at least one PDCCH candidate using the aggregation level that is not a power of 2.

According to certain embodiments, a method by a network node for configuring a wireless device with an aggregation level for decoding a PDCCH candidate includes configuring the wireless device with an aggregation level that is not a power of 2. The aggregation level is a number of CCEs used per PDCCH candidate.

According to certain embodiments, a network node for configuring a wireless device with an aggregation level for decoding a PDCCH candidate includes processing circuitry configured to configure the wireless device with an aggregation level that is not a power of 2. The aggregation level is a number of CCEs used per PDCCH candidate. Certain embodiments may provide one or more of the following technical advantages. As one example, certain embodiments may advantageously provide coverage compensation for reduced capability UEs that have stringent limitations on bandwidth and/or the number of antennas compared to regular NR devices. As another example, in certain embodiments the highest ALs can be supported when needed to achieve the highest coverage performance. As still another example, certain embodiments may advantageously provide flexibility for handling tradeoff between coverage and CCE monitoring limit for reduced capability UEs.

Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 illustrates an example of a CORESET;

FIGURE 2 illustrates ALs in a CORESET with 12 CCEs, according to certain embodiments;

FIGURE 3 illustrates the potential issue of overlapping between new ALs with existing ones, according to certain embodiments;

FIGURE 4 illustrates an example of PDCCH candidates with AL 6 and AL 8 using the proposed approach, according to certain embodiments;

FIGURE 5 illustrates an example wireless network, according to certain embodiments;

FIGURE 6 illustrates an example network node, according to certain embodiments;

FIGURE 7 illustrates an example wireless device, according to certain embodiments;

FIGURE 8 illustrate an example user equipment, according to certain embodiments;

FIGURE 9 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments; FIGURE 10 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 11 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 12 illustrates a method implemented in a communication system, according to one embodiment;

FIGURE 13 illustrates another method implemented in a communication system, according to one embodiment; FIGURE 14 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 15 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 16 illustrates an example method by a wireless device, according to certain embodiments;

FIGURE 17 illustrates an exemplary virtual computing device, according to certain embodiments;

FIGURE 18 illustrates another example method by a wireless device, according to certain embodiments; FIGURE 19 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 20 illustrates an example method by a network node, according to certain embodiments;

FIGURE 21 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 22 illustrates another example method by a network node, according to certain embodiments; and

FIGURE 23 illustrates another exemplary virtual computing device, according to certain embodiments. DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

The main issues with the existing approaches, which are described above, are as follows. First, reduced bandwidth UEs may not be able to configure high ALs, leading to PDCCH coverage degradation. Second, with the existing ALs of {1, 2, 4, 8, 16}, sufficient coverage may not be achieved for reduced capability UEs (e.g., due to reduced number of antennas). Third, there is a limit on the number of CCEs which can be monitored by a UE per slot. The existing ALs may not provide full flexibility for handling tradeoff between coverage and CCE limit. Certain embodiments are described below to address these and other issues.

Maximum AL for Coverage Maximization

Given the bandwidth reduction of NR-RedCap UEs, the current CORESET configuration may not be able to support the highest AL as discussed above. The existing possible AL set is {1, 2, 4, 8, 16}, which requires (6, 12, 24, 48, 96} REGs. One REG is made up of one RB (12 REs in frequency domain) and one OFDM symbol in time domain. As the NR-RedCap UEs are supposed to have much lower bandwidth than the existing NR UEs, the current design of the CORESET structure for NR poses several limitations. For example, there is not any value between 48 and 96 REGs. Consequently, it may not be possible to use some RBs as PDCCH resources for some UE bandwidths.

Therefore, it would be beneficial to support new ALs to expand the existing possible AL set (1, 2, 4, 8, 16}. This provides flexibility in terms of resource allocation and offers PDCCH coverage enhancement and/or coverage compensation for NR-RedCap UEs.

The UE can be configured with the maximum AL which can be supported within its largest configurable CORESET. In particular, the following AL is supported:

where N_RB is the number of RBs and N_sym is the number of symbols for the configured CORESET. Also, is the floor function.

To illustrate, consider the following example. AL 12 is supported for a CORESET spanning over 24 RBs and 3 symbols. Note that, within this CORESET, with the existing ALs, a UE cannot support AL16. Thus, AL 8 is the maximum AL that the UE can use. The new AL 12 provides better coverage compared to AL 8.

Table 3 below shows the new ALs for three-symbol CORESETs.

Table 3: Example of new ALs for three-symbol CORESETs

Note that the maximum AL occupies the entire CORESET bandwidth. Thus, there is only one PDCCH candidate with the maximum AL.

FIGURE 2 illustrates an example 20 with ALs in a CORESET with 12 CCEs. More specifically, FIGURE 2 illustrates an example of ALs 12 (one candidate), 8 (one candidate), and 4 (assuming two candidates) in a CORESET with 24 PRBs and 3 symbols which consists of 12 CCEs.

It should be understood that FIGURE 2 is used for purposes of illustration. It is also possible to configure 3 AL=4 candidates, which won’t leave any unused CCEs in this setup.

The new “intermediate” AL can be treated as a punctured version of the next higher AL with a pre-determined mapping of which CCE will not be read by a UE with limited CORESET bandwidth. For example, if a NR-RedCap UE has a CORESET capable of AL 12 but not the legacy format AL 16, it would be implicitly understood by both UE and gNB that when AL 16 is configured the UE will instead monitor AL 12 as a punctured version of AL 16 with the same start position (and clearly defined which 4 CCE will not be read).

The above-described case corresponds to implicit indication of new AL where AL 16 is configured for a UE to monitor in a search space while the UE CORESET bandwidth only supports up to maximum AL 12, according to:

To support AL 12, the size of the output of rate matching for polar code is determined according to PDCCH candidate with AL 12 instead of AL16. Alternatively, the extra PDCCH candidates (i.e., CCEs) of AL 16 may be punctured to match with AL 12.

Another approach for implicit indication is where a PDCCH candidate with maximum AL from the set {1, 2, 4, 8, 16} which can be supported by the UE CORESET is configured. If the UE CORESET can support a new, larger AL according to:

the new AL is also monitored by the UE. Also, it is possible to explicitly configure the new AL in the search space in addition to other ALs.

New ALs for coverage enhancement under the CCE limit In order to limit the UE complexity and power consumption, there is a constraint on the number of non-overlapping CCEs that the UE needs to monitor per slot. In this regard, there is a tradeoff between coverage and UE complexity in terms of the AL. While having a higher AL improves the coverage, it increases the UE complexity, because more CCEs need to be monitored per slot (assuming that lower ALs should still be included for optimal performance in good coverage). Due to the CCE limit, it may not be possible to configure high ALs. For example, due to the CCE limit per slot, the UE may configure AL 8 instead of AL 16, which has around 3 dB lower coverage. To reduce such coverage degradation, it can be beneficial to have new ALs other than the existing ALs { 1, 2, 4, 8, 16} to achieve the maximum coverage while satisfying the CCE limits. In certain embodiments, the AL configured for the UE may be based on a level of coverage provided by the AL. For instance, in case AL 16 cannot be used, it can be replaced with AL 12 instead of AL 8 if the CCE limit is met. AL 12 provides higher coverage than AL 8. Therefore, to increase flexibility for handling tradeoff between coverage and CCE limit, the existing set of ALs can be extended.

In certain embodiments, the set of possible ALs is extended from (1, 2, 4, 8, 16} to ALs (1, 2, 3, 4, 6, 8, 12, 16}, where (3, 6, 12} are new ALs. That is, for this example, aggregationLevel3, aggregationLevel6, and aggregationLevell2 can be included in nrofCandidates in the SearchSpace information element (IE) for indication of the number of PDCCH candidates per AL. The new AL levels should be used to give a minimum overlapping of PDCCH candidates when necessary, which is discussed in more detail below.

In certain embodiments, it is also possible that any (one or more) of the following configurations can be used: AL 16 is replaced with AL 12; AL 8 is replaced with AL 6; and AL 4 is replaced with AL 3.

From a configuration point of view, the IE aggregatioriLevel16 would then be reinterpreted by a NR-RedCap UE as aggregationLevell 2 in the ASN.1 encoding shown below (taken from 3GPP TS 38.331, “NR; Radio Resource Control (RRC); Protocol specification”), still using the same ANS.l code but with an added clarification in the Field Description. In certain embodiments, either all these new ALs would be used in the reinterpretation for NR-RedCap UEs (e.g., based on device type or UE capabilities), or it would be dependent on the maximum legacy AL the UE is capable of such that all larger ALs would be reinterpreted to lower ALs that the UE can handle. SearchSpace information element

- ASN1 START

- TAG-SEARCHSPACE-START

SearchSpace

SEQUENCE { searchSpaceld SearchSpaceld, controlResourceSetld ControlResourceSetld

OPTIONAL, — Cond SetupOnly monitoringSlotPeriodicityAndOffset CHOICE { sll NULL, sl2 INTEGER (0..1), sl4 INTEGER (0 .3), si 5 INTEGER (0..4), si 8 INTEGER (0 .7), sllO INTEGER (0..9), si 16 INTEGER (0 .15), sl20 INTEGER (0 .19), sl40 INTEGER (0 .39), sl80 INTEGER (0..79), si 160 INTEGER (0 .159), sl320 INTEGER (0 .319), sl640 INTEGER (0 .639), si 1280 INTEGER (0 .1279), sl2560 INTEGER (0 .2559)

} OPTIONAL,

Cond Setup duration INTEGER (2 .2559) OPTIONAL, — Need R monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL, - Cond Setup nrofCandidates SEQUENCE { aggregationLevel 1 ENUMERATED { n0, nl, n2, n3, n4, n5, n6, n8}, aggregationLevel2 ENUMERATED { n0, nl, n2, n3, n4, n5, n6, n8}, aggregationLevel4 ENUMERATED { n0, nl, n2, n3, n4, n5, n6, n8}, aggregati onLevel 8 ENUMERATED { n0, nl, n2, n3, n4, n5, n6, n8}, aggregationLevel 16 ENUMERATED { n0, nl, n2, n3, n4, n5, n6, n8} } OPTIONAL, -

Cond Setup

Another aspect of the present disclosure is to ensure efficient multiplexing by minimizing overlap between different PDCCH candidates. For example, a candidate of AL 4 does not overlap with more than one candidate of AL 8. The index of CCEs in PDCCH candidates for different ALs can be determined using a hash function, for example as described in 3GPP TS 38.213, “NR; Physical layer procedures for control” and reproduced below: For a search space set S associated with CORESET p , the CCE indexes for AL L corresponding to PDCCH candidate of the

search space set in slot for an active downlink (DL) bandwidth

part (BWP) of a serving cell corresponding to carrier indicator field value n_CI are given by:

In the above hash function, N_CCE,p is the number of CCEs, numbered from 0 to -! in CORESET P. The variable n_CI is the carrier

indicator field value if the wireless device is configured with a carrier indicator field by CrossCarrierSchedulingConfig for the serving cell on which PDCCH is monitored. Otherwise, including for any common search space (CSS), n_CI = 0. The variable

where is the number of PDCCH candidates the wireless device

is configured to monitor for AL L of a search space set s for a serving cell corresponding to n_{CI .} The variable i = 0, · · · , L - 1 is also used in the above hash function.

In the above hash function, the variable depends on whether it

is for a CSS or a UE-specific search space (USS). For any CSS:

For a USS:

in which and D = 65531 . The Radio Network

Temporary Identifier (RNTI) value used for ⁿRNTI is the Cell-RNTI (C-RNTI). The value of A_p depends on the value of pmod3. in the above equation: 4_p = 39827 for pmod3 = 0 · A_p = 39829 for pmod3 = 1 ; and A_p = 39839 for p mod 3 = 2 .

In the above hash function, the variable depends on whether it

is for a CSS or a USS. For any CSS:

For a USS, the maximum of over all configured

n_CI values for a CCE AL L of search space set S .

The hash function above ensures minimum overlap between PDCCH candidates for ALs which are a power of 2 (i.e., AL = 2^k, where However, if the

AL is not a power of 2, it is possible that one candidate of L_new overlaps with two candidates of AL L > L_new (i.e., blocking two candidates). Similarly, one candidate of AL L < L_new may overlap with two candidates of AL L_new.

FIGURE 3 illustrates an example 30 demonstrating the potential issue of overlapping between new ALs with existing ones. In certain embodiments, the AL configured for the UE may be based on a number of overlapping PDCCH candidates (e.g., overlap between PDCCH candidates from different ALs). In some cases, the AL configured for the UE may be an AL that reduces overlap between a number of PDCCH candidates. For instance, the positions of PDCCH candidates for an AL may be determined such that their overlap with candidates of other ALs is minimized.

The present disclosure contemplates that various solutions can be used in order to ensure efficient multiplexing when introducing a new AL, L_new. A new AL (such as an AL that is not a power of 2) may for example be determined/selected/designed such that a PDCCH candidate from the new AL overlaps with at most one PDCCH candidate from a larger AL that is a power of 2. According to one example embodiment, the index of CCEs uses the following steps: · Let L_new be the new AL, where 2^k_1 < L_new < 2^k

• Find the index of the first CCEs for AL L = 2^k

• Use only the first L_new CCEs of each candidate of AL L = 2^k. Specifically, the index of CCEs for AL L_new can be found using the following hash function:

For a search space set S associated with CORESET P , the CCE indexes for AL 2^k_1 < L_new < 2^k corresponding to PDCCH candidate m_s of the search space set in slot for an active DL

BWP of a serving cell are given by the equation below:

In the above hash function, N_CCE,p is the number of CCEs, numbered from 0 to N_CCE,p ^_ 1 in CORESET P . The variable m_s = the number of PDCCH

candidates the wireless device is configured to monitor for AL L_new. The variable i = 0, ^...,L_new — 1 is also used in the above hash function.

In the above hash function, the variable depends on whether it is

for a CSS or a USS. For any CSS:

For a USS:

in which _and D = 65537 . The RNTI value used

for n_RNTI is the C-RNTI. The value of A_p depends on the value of pmod3 in the above equation: A_p — 39827 for pmod3 — 0 ;

A_p =39829 for pmod3 = 1 · and A_p =39839 for pmod3 = 2

FIGURE 4 illustrates an example 40 of PDCCH candidates 41 with AL 6 and PDCCH candidates 42 with AL 8, using the proposed approach. The CCEs 43 labeled as “unused” shall be understood as unused for the AL 6 candidates 41, but may be used, in this example, for PDCCH candidates with AL 1 or AL 2.

In an alternative approach, the first CCE index is chosen other than the lowest index given by the hash function above. One such example would be to modify the range of the index i in the hash function to start at a non-zero value, such as, without limitation, using the last indices up to 2^k — 1, where:

FIGURE 5 illustrates a wireless network in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 5. For simplicity, the wireless network of FIGURE 5 only depicts network 106, network nodes 160 and 160b, and WDs 110. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (WD) 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 160 and WD 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.

FIGURE 6 illustrates an example network node 160, according to certain embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless 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)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also 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). Yet further examples of network nodes include 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), core network nodes (e.g., Mobile Switching Centres (MSCs), Mobility Management Entities (MMEs)), Operations & Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self Optimized Network (SON) nodes, positioning nodes (e.g., Evolved- Serving Mobile Location Centres (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 6, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 6 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules). Similarly, network node 160 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 network node 160 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 NodeB’ s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 160.

Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 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.

Processing circuitry 170 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 160 components, such as device readable medium 180, network node 160 functionality. For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 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 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160, but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 180 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 processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 6 that may be responsible 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, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

FIGURE 7 illustrates an example wireless device 110, according to certain embodiments. As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer- premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to- infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD 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 WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, Wideband Code Division Multiplexing Access (WCDMA), LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120, and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114. Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 120 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 WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 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 device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110 as a whole, and/or by end users and the wireless network generally. Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, 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.

Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., 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 processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be considered to be integrated.

User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110, and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.

FIGURE 8 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or 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). UE 200 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 8, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIGURE 8 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIGURE 8, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 8, or only a subset of the components. 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.

In FIGURE 8, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware- implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, 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 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be 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. UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may 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, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIGURE 8, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (EO), startup, or reception of keystrokes from a keyboard that are stored in a non volatile memory. Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or 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 in storage medium 221, which may comprise a device readable medium.

In FIGURE 8, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, Universal Terrestrial Radio Access Network (UTRAN), WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 may include 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. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200. The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIGURE 9 is a schematic block diagram illustrating a virtualization environment 300 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 a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized. The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

As shown in FIGURE 9, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

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.

In the context of NFV, virtual machine 340 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 virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in FIGURE 9.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 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 signalling can be effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

FIGURE 10 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIGURE 10, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3GPP- type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420. Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).

The communication system of FIGURE 10 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of UL and DL communications. For example, base station 412 may not or need not be informed about the past routing of an incoming DL communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.

FIGURE 11 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 11. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530. Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 11) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in FIGURE 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510, an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both the request data and the user data. Client application 532 may interact with the user to generate the user data that it provides.

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIGURE 11 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 10, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 11 and independently, the surrounding network topology may be that of FIGURE 10.

In FIGURE 11, OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the coverage of NR-RedCap devices and potentially other types of wireless devices and thereby provide benefits such as better responsiveness, improved data rate, reduced user waiting time, and improved energy efficiency.

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 OTT connection 550 between host computer 510 and UE 530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 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 511, 531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

FIGURE 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 12 will be included in this section. In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission. FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 14 will be included in this section. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub step 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section. In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

FIGURE 16 depicts a method 1000 in a wireless device 110 such as, for example, a UE 200, in accordance with certain embodiments. More particularly, FIGURE 16 depicts a method performed by a wireless device 110 for decoding a PDCCH candidate. The method begins at step 1002, with the wireless device 110 being configured with an AL that is not 1, 2, 4, 8, or 16 (i.e., being configured with an AL that is other than 1, 2, 4, 8, and 16).

In certain embodiments, the AL may be a number of control channel elements used for a PDCCH candidate.

In certain embodiments, the method may comprise decoding the PDCCH candidate using the configured AL that is not 1, 2, 4, 8, or 16.

In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 may not be a power of 2 (i.e., the configured AL that is not 1, 2, 4, 8, or 16 may be other than a power of 2). In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 may be one of 3, 6, or 12.

In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 may be a maximum AL that can be supported within a largest configurable (e.g., configured) CORESET of the wireless device. In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 may be based on a number of RBs and a number of symbols of the largest configurable (e.g., configured) CORESET of the wireless device.

In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 may be determined according to the equation:

L may be the AL. N_RB may be a number of resource blocks for the largest configurable (e.g., configured) CORESET of the wireless device 110. N_sym may be a number of symbols for the largest configurable (e.g., configured) CORESET of the wireless device.

may be a floor function.

L may be the AL, N_RB may be a number of resource blocks for the largest configurable (e.g., configured) CORESET of the wireless device 110. N_sym may be a number of symbols for the largest configurable (e.g., configured) CORESET of the wireless device 110.

In certain embodiments, being configured with the AL that is not 1, 2, 4, 8, or 16 may comprise being explicitly configured with the AL that is not 1, 2, 4, 8, or 16. In certain embodiments, being explicitly configured with the AL that is not 1, 2, 4, 8, or 16 may comprise receiving, from a network node 160, an indication of the AL that is not 1, 2, 4, 8, or 16. The indication may be included in a SearchSpace information element.

In certain embodiments, being configured with the AL that is not 1, 2, 4, 8, or 16 may comprise being implicitly configured with the AL that is not 1, 2, 4, 8, or 16. In certain embodiments, being implicitly configured with the AL that is not 1, 2, 4, 8, or 16 may comprise: receiving, from a network node 160, an indication of an AL that the wireless device 110 should use to decode the PDCCH candidate; determining that the wireless device 110 does not support the indicated AL and/or that the wireless device 110 supports a higher AL than the indicated AL; and using the AL that is not 1, 2, 4, 8, or 16 to decode the PDCCH candidate instead of the indicated AL. In certain embodiments, the method may further comprise determining the AL that is not 1, 2, 4, 8, or 16. In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be determined according to the equation:

may be a floor function. In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be determined according to the equation:

L may be the AL. N_RB may be a number of resource blocks for the largest configurable (e.g., configured) CORESET of the wireless device 110. N_sym may be a number of symbols for the largest configurable (e.g., configured) CORESET of the wireless device 110.

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is lower than the indicated AL. The AL that is not 1, 2, 4, 8, or 16 may comprise a punctured version of the indicated AL. In certain embodiments, the method may comprise determining which of a plurality of control channel elements comprising the indicated AL will not be read for the punctured version of the indicated AL. In certain embodiments, the indicated AL may be an AL 16 and the AL that is not 1, 2, 4, 8, or 16 may be an AL 12. The AL 12 may be a punctured version of the AL 16.

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is higher than the indicated AL. The method may comprise determining the AL that is higher than the indicated AL. In certain embodiments, the AL that is higher than the indicated AL may be determined according to the equation:

L may be the AL. N_RB may be a number of resource blocks for the largest configurable (e.g., configured) CORESET of the wireless device 110. N_sym may be a number of symbols for the largest configurable (e.g., configured) CORESET of the wireless device. [.J may be a floor function. In certain embodiments, the AL that is higher than the indicated AL may be determined according to the equation:

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be based on a level of coverage provided by the AL that is not 1, 2, 4, 8, or 16.

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be based on a limit on a number of non-overlapping control channel elements that applies to the wireless device 110.

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be based on a number of overlapping PDCCH candidates. The method may comprise determining the AL that is not 1, 2, 4, 8, or 16 that reduces overlap between different PDCCH candidates. In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be a new AL and determining the new AL may comprise: letting L_new be the new AL, where 2^k-1 < L_new < 2^k; determining an index of a first control channel element for an AL L = 2^k; and using only the first L_new control channel elements of each PDCCH candidate of AL L = 2^k . In certain embodiments, the method may comprise determining an index of control CCEs for AL L_new using the following hash function: for a search space set s associated with a CORESET p, CCE indexes for AL 2^k-1 < L_new < 2^k corresponding to a PDCCH candidate m_s of the search space set in slot for an active DL BWP of a serving cell are given by:

embodiments, for a UE-specific search space (USS),

A_p =39827 for pmod3 = 0 , A_p = 39829 for pmod3 = 1 ,

A_p =39839 f_or pmod3 = 2 , and D = 65537 . In certain embodiments, i = 0 , ... , L_new — 1. N_{CCE ,p} may be a number of control channel elements, numbered from 0 to N_CCE,p — 1 , in CORESET P . In certain embodiments, m_s = where is a number of PDCCH candidates the wireless

device is configured to monitor for AL L_new. In certain embodiments, the first control channel element index may be chosen other than the lowest index given by the hash function. In certain embodiments, the method may comprise modifying a range of the index i in the hash function to start at a non-zero value. In certain embodiments, the method may comprise using one or more last indices up to 2^k — 1, wherein i = 2^k — L_new ,.., 2^k — 1

In certain embodiments, the wireless device 110 may be a New Radio reduced capability (NR-RedCap) wireless device. In certain embodiments, the wireless device 110 may have a bandwidth of one of: at most 10 MHz; at most 20 MHz; at most 30 MHz; at most 40 MHz; and at most 50 MHz.

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be based on one or more capabilities of the wireless device 110. In certain embodiments, the method may comprise sending capability information to a network node 160.

In certain embodiments, the method may comprise: providing user data; and forwarding the user data to a host computer via the transmission to the base station. FIGURE 17 illustrates a schematic block diagram of an apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device (e.g., wireless device 110 shown in FIGURE 5). Apparatus 1100 is operable to carry out the example method described with reference to FIGURE 16 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 16 is not necessarily carried out solely by apparatus 1100. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 1102, determining unit 1104, communication unit 1106, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.

In certain embodiments, apparatus 1100 may be a UE. In certain embodiments, apparatus 1100 may be an NR-RedCap wireless device. In certain embodiments, apparatus 1100 may have a bandwidth that is one of: at most 10 MHz; at most 20 MHz; at most 30 MHz; at most 40 MHz; and at most 50 MHz. Apparatus 1100 may be configured to perform a method for decoding a PDCCH candidate (e.g., the method described above in relation to FIGURE 16).

As illustrated in FIGURE 17, apparatus 1100 includes receiving unit 1102, determining unit 1104, and communication unit 1106. Receiving unit 1102 may be configured to perform the receiving functions of apparatus 1100. For example, receiving unit 1102 may be configured to receive, from a network node 160, an indication of the AL that is not 1, 2, 4, 8, or 16 (e.g., in a SearchSpace information element). As another example, receiving unit 1102 may be configured to receive, from a network node, an indication of an AL that the wireless device 110 should use to decode the PDCCH candidate.

Receiving unit 1102 may receive any suitable information (e.g., from another wireless device or a network node). Receiving unit 1102 may include a receiver and/or a transceiver, such as RF transceiver circuitry 122 described above in relation to FIGURE 5. Receiving unit 1102 may include circuitry configured to receive messages and/or signals (wireless or wired). In particular embodiments, receiving unit 1102 may communicate received messages and/or signals to determining unit 1104 and/or any other suitable unit of apparatus 1100. The functions of receiving unit 1102 may, in certain embodiments, be performed in one or more distinct units.

Determining unit 1104 may perform the processing functions of apparatus 1100. For example, determining unit 1104 may be configured to use an AL that is not 1, 2, 4, 8, or 16 to decode a PDCCH candidate. As another example, determining unit 1104 may be configured to be configured with an AL that is not 1, 2, 4, 8, or 16. In certain embodiments, determining unit 1104 may be configured to be explicitly configured with the AL that is not 1, 2, 4, 8, or 16. In certain embodiments, determining unit 1104 may be configured to be implicitly configured with the AL that is not 1, 2, 4, 8, or 16. As still another example, determining unit 1104 may be configured to decode the PDCCH candidate using the configured AL that is not 1, 2, 4, 8, or 16 (e.g., an AL that is one of 3, 6, or 12, or an AL that is not a power of 2).

As yet another example, determining unit 1104 may be configured to determine that the wireless device 110 does not support the indicated AL and/or that the wireless device 110 supports a higher AL than the indicated AL. Determining unit 1104 may be configured to use the AL that is not 1, 2, 4, 8, or 16 to decode the PDCCH candidate instead of the indicated AL. In certain embodiments, determining unit 1104 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 (e.g., using the equation described above in relation to FIGURE 16).

As another example, in certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is lower than the indicated AL (e.g., the indicated AL may be AL 16 and the AL that is not 1, 2, 4, 8, or 16 may be an AL 12). The AL that is not 1, 2,4, 8, or 16 may comprise a punctured version of the indicated AL. In certain embodiments, determining unit 1104 may be configured to determine which of a plurality of control channel elements comprising the indicated AL will not be read for the punctured version of the indicated AL.

As another example, in certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is higher than the indicated AL. Determining unit 1104 may be configured to determine the AL that is higher than the indicated AL (e.g., using the equation L = described above in relation to

FIGURE 16).

As another example, determining unit 1104 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on a level of coverage provided by the AL that is not 1, 2, 4, 8, or 16.

As another example, determining unit 1104 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on a limit on a number of non-overlapping control channel elements that applies to the wireless device 110.

As another example, determining unit 1104 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on a number of overlapping PDCCH candidates. Determining unit 1104 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 that reduces overlap between different PDCCH candidates. In certain embodiments, the aggregation level that is not 1, 2, 4, 8, or 16 may be a new aggregation level, and determining unit 1104 may be configured to determine the new aggregation level. In certain embodiments, determining unit 1104 may be configured to: let L_new be the new AL, where 2^k-1 < L_new < 2^k; determine an index of a first control channel element for an AL L = 2^k; and use only the first L_new control channel elements of each PDCCH candidate of AL L = 2^k. Determining unit 1104 may be configured to determining an index of control channel elements for AL L_new (e.g., using the hash function described above in relation to FIGURE 16). Determining unit 1104 may be configured to modify a range of the index in the hash function to start at a non-zero value. Determining unit 1104 may be configured to use one or more last indices up to 2^k — 1, wherein i = 2^k — L_new, ··· , 2^k — 1.

As another example, determining unit 1104 may be configured to provide user data. Determining unit 1104 may include or be included in one or more processors, such as processing circuitry 120 described above in relation to FIGURE 5. Determining unit 1104 may include analog and/or digital circuitry configured to perform any of the functions of determining unit 1104 and/or processing circuitry 120 described above. The functions of determining unit 1104 may, in certain embodiments, be performed in one or more distinct units.

Communication unit 1106 may be configured to perform the transmission functions of apparatus 1100. For example, communication unit 1106 may be configured to send capability information to a network node 160. As another example, communication unit 1106 may be configured to forward user data to a host computer via a transmission to a network node 160 (e.g., a base station).

Communication unit 1106 may transmit messages (e.g., to another wireless device and/or a network node). Communication unit 1106 may include a transmitter and/or a transceiver, such as RF transceiver circuitry 122 described above in relation to FIGURE 5. Communication unit 1106 may include circuitry configured to transmit messages and/or signals (e.g., through wireless or wired means). In particular embodiments, communication unit 1106 may receive messages and/or signals for transmission from determining unit 1104 or any other unit of apparatus 1100. The functions of communication unit 1106 may, in certain embodiments, be performed in one or more distinct units.

FIGURE 18 depicts another method 1200 by a wireless device 110 (e.g., aUE), in accordance with certain embodiments. More particularly, FIGURE 18 depicts a method performed by a wireless device 110 for decoding a PDCCH candidate. The method begins at step 1202, with the wireless device 110 being configured with an aggregation level that is not a power of 2. The aggregation level is a number of CCEs used per PDCCH candidate. At step 1204, the wireless device 110 decodes at least one PDCCH candidate using the aggregation level that is not a power of 2.

In a particular embodiment, the wireless device 110 determines, for each PDCCH candidate 41 with the aggregation level that is not a power of 2, the CCEs used for this PDCCH candidate such that this PDCCH candidate overlaps with at most one PDCCH candidate 42 with a second aggregation level. The second aggregation level is a power of 2 and is larger than the aggregation level that is not a power of 2. In a further particular embodiment, the second aggregation level is 2^k ; the aggregation level that is not a power of 2 is larger than 2^k"1; and k is a positive integer.

In a particular embodiment, there is at least one CCE 43 located between two PDCCH candidates 41 with the aggregation level that is not a power of 2, and the at least one CCE is unused by all PDCCH candidates with the aggregation level that is not a power of 2.

In a particular embodiment, the aggregation level that is not a power of 2 is a new aggregation level, L_new , and the wireless device determines an index of the CCEs used for the at least one PDCCH candidate using the following hash function:

- for a search space set ^s associated with a CORESET ^P, CCE indexes for aggregation level 2^k-1 < L_new < 2^k corresponding to a PDCCH candidate m_s of the search space set in slot for an active

downlink bandwidth part of a serving cell are given by:

i — 0, ··· , L_new 1, N_CCE,p is a number of control channel elements, numbered from 0 to is a number of PDCCH

candidates the wireless device is configured to monitor for the new aggregation level, L_new.

In a particular embodiment, a first CCE index is chosen other than a lowest index given by the hash function of Claim 5. In a further particular embodiment, the wireless device 110 modifies a range of the index i in the hash function above to start at a non-zero value.

In a particular embodiment, the wireless device 110 uses one or more last indices up to 2^k — 1, and i = 2^k — L_new, ··· , 2^k — 1.

In a particular embodiment, the aggregation level that is not a power of 2 is a new aggregation level, L_new , and the wireless device 110 determines the new aggregation level by:

- letting L_new be the new AL, where 2^fe_1 < L_new < 2^k ;

- determining an index of a first control channel element for an aggregation level L = 2^k; and

- using only the first L_new control channel elements of each PDCCH candidate of aggregation level L = 2^k.

In a particular embodiment, the aggregation level that is not a power of 2 is greater than 16.

In a particular embodiment, the aggregation level that is not a power of 2 is one of 3, 6, or 12.

In a particular embodiment, the aggregation level that is not a power of 2 is a maximum aggregation level that is supported within a configurable CORESET of the wireless device.

In a further particular embodiment, the configurable CORESET of the wireless device comprises a largest configurable CORESET of the wireless device.

In a further particular embodiment, the aggregation level that is not a power of 2 is based on a number of resource blocks and a number of symbols of the largest configurable CORESET of the wireless device.

In a particular embodiment, the aggregation level that is not a power of 2 is a maximum aggregation level that is supported by a bandwidth limitation of a CORESET of the wireless device.

In a further particular embodiment, a next aggregation level above the aggregation level that is not a power of 2 is not supported within the bandwidth limitation of the CORESET of the wireless device.

In a particular embodiment, the configured aggregation level that is not a power of 2 is determined according to the equation:

- L is the aggregation level;

- N_RB is a number of resource blocks for the largest configurable CORESET of the wireless device;

- N_sym is a number of symbols for the largest configurable CORESET of the wireless device; and

- is a floor function.

In a particular embodiment, the wireless device is implicitly configured with the aggregation level that is not the power of 2. Being implicitly configured with the aggregation level that is not the power of 2 includes: receiving, from a network node 160, an indication of an indicated aggregation level that the wireless device 110 should use to decode the PDCCH candidate; determining that the wireless device 110 does not support the indicated aggregation level and/or that the wireless device 110 supports a higher aggregation level than the indicated aggregation level; and using the aggregation level that is not a power of 2 to decode the PDCCH candidate instead of the indicated aggregation level.

In a further particular embodiment, the aggregation level that is not a power of 2 is an aggregation level that is lower than the indicated aggregation level.

In a further particular embodiment, the aggregation level that is not a power of 2 comprises a punctured version of the indicated aggregation level, and the wireless device 110 determines which of a plurality of CCEs comprising the indicated aggregation level will not be read for the punctured version of the indicated aggregation level.

In a further particular embodiment, the aggregation level that is not a power of 2 is an aggregation level that is higher than the indicated aggregation level.

In a particular embodiment, the aggregation level that is not a power of 2 is based on a limit on a number of non-overlapping CCEs that applies to the wireless device 110.

In a particular embodiment, the wireless device 110 is a NR-RedCap wireless device.

In a particular embodiment, the aggregation level that is not a power of 2 is based on one or more capabilities of the wireless device, and the wireless device 110 sends, to a network node 160, information indicating the one or more capabilities of the wireless device.

FIGURE 19 illustrates a schematic block diagram of an apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device (e.g., wireless device 110 shown in FIGURE 5). Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 18 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 18 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 1302, determining unit 1304, communication unit 1306, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.

In certain embodiments, apparatus 1300 may be a UE. In certain embodiments, apparatus 1300 may be an NR-RedCap wireless device. In certain embodiments, apparatus 1300 may have a bandwidth that is one of: at most 10 MHz; at most 20 MHz; at most 30 MHz; at most 40 MHz; and at most 50 MHz. Apparatus 1300 may be configured to perform a method for decoding a PDCCH candidate (e.g., the method described above in relation to FIGURE 18).

As illustrated in FIGURE 19, apparatus 1300 includes receiving unit 1302, determining unit 1304, and communication unit 1306. Receiving unit 1302 may be configured to perform the receiving functions of apparatus 1300. For example, receiving unit 1302 may be configured to receive, from a network node, an indication of an AL that is not a power of 2 (e.g., in a SearchSpace information element). The AL may be a number of CCEs used per PDCCH candidate. As another example, receiving unit 1302 may be configured to receive, from a network node, an indication of an AL that the wireless device should use to decode at least one PDCCH candidate.

Receiving unit 1302 may receive any suitable information (e.g., from another wireless device or a network node). Receiving unit 1302 may include a receiver and/or a transceiver, such as RF transceiver circuitry 122 described above in relation to FIGURE 7. Receiving unit 1302 may include circuitry configured to receive messages and/or signals (wireless or wired). In particular embodiments, receiving unit 1302 may communicate received messages and/or signals to determining unit 1304 and/or any other suitable unit of apparatus 1300. The functions of receiving unit 1302 may, in certain embodiments, be performed in one or more distinct units.

Determining unit 1304 may perform the processing functions of apparatus 1300. For example, determining unit 1304 may be configured to use an AL that is not a power of 2 to decode a PDCCH candidate. As another example, determining unit 1304 may be configured to be configured with an AL that is not a power of 2. In certain embodiments, determining unit 1304 may be configured to be explicitly configured with the AL that is not a power of 2. In certain embodiments, determining unit 1304 may be configured to be implicitly configured with the AL that is not a power of 2. As still another example, determining unit 1304 may be configured to decode at least one PDCCH candidate using the configured AL that is not a power of 2 (e.g., an AL that is one of 3, 6, or 12).

As another example, determining unit 1304 may be configured to provide user data.

Determining unit 1304 may include or be included in one or more processors, such as processing circuitry 120 described above in relation to FIGURE 7. Determining unit 1304 may include analog and/or digital circuitry configured to perform any of the functions of determining unit 1304 and/or processing circuitry 120 described above. The functions of determining unit 1304 may, in certain embodiments, be performed in one or more distinct units. Communication unit 1306 may be configured to perform the transmission functions of apparatus 1300. For example, communication unit 1306 may be configured to send capability information to a network node. As another example, communication unit 1306 may be configured to forward user data to a host computer via a transmission to a network node (e.g., a base station).

Communication unit 1306 may transmit messages (e.g., to another wireless device and/or a network node). Communication unit 1306 may include a transmitter and/or a transceiver, such as RF transceiver circuitry 122 described above in relation to FIGURE 7. Communication unit 1306 may include circuitry configured to transmit messages and/or signals (e.g., through wireless or wired means). In particular embodiments, communication unit 1306 may receive messages and/or signals for transmission from determining unit 1304 or any other unit of apparatus 1300. The functions of communication unit 1306 may, in certain embodiments, be performed in one or more distinct units.

FIGURE 20 depicts a method 1400 in a network node 160 (e.g., a gNB or an eNB), in accordance with certain embodiments. More particularly, FIGURE 20 depicts a method performed by a network node 160 for configuring a wireless device 110 with an AL for decoding a PDCCH candidate. The method begins at step 1402, where the network node configures the wireless device with an AL that is not 1, 2, 4, 8, or 16 (i.e., configuring the wireless device with an AL that is other than 1, 2, 4, 8, or 16).

In certain embodiments, the AL may be a number of CCEs used for a PDCCH candidate.

In certain embodiments, the method may comprise determining the AL that is not 1, 2, 4, 8, or 16.

In certain embodiments, the method may comprise obtaining capability information for the wireless device 110. The method may comprise determining the AL that is not 1, 2, 4, 8, or 16 based on the obtained capability information.

In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 is not a power of 2 (i.e., the configured AL that is not 1, 2, 4, 8, or 16 may be other than a power of 2).

In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 may be one of 3, 6, or 12.

In certain embodiments, the configured AL that is not 1, 2, 4, 8, or 16 may be a maximum AL that can be supported within a largest configurable (e.g., configured) CORESET of the wireless device 110. The configured AL that is not 1, 2, 4, 8, or 16 may be based on a number of resource blocks and a number of symbols of the largest configurable (e.g., configured) CORESET of the wireless device 110.

L may be the AL. N_RB may be a number of resource blocks for the largest configurable (e.g., configured) CORESET of the wireless device 110. N_sym may be a number of symbols for the largest configurable (e.g., configured) CORESET of the wireless device. may be a floor function.

In certain embodiments, configuring the AL that is not 1, 2, 4, 8, or 16 may comprise explicitly configuring the AL that is not 1, 2, 4, 8, or 16. Explicitly configuring the AL that is not 1, 2, 4, 8, or 16 may comprises sending, to the wireless device 110, an indication of the AL that is not 1, 2, 4, 8, or 16. The indication may be included in a SearchSpace information element.

In certain embodiments, configuring the AL that is not 1, 2, 4, 8, or 16 may comprise implicitly configuring the AL that is not 1, 2, 4, 8, or 16. Implicitly configuring the AL that is not 1, 2, 4, 8, or 16 may comprise sending, to the wireless device 110, an indication of an AL that the wireless device 110 should use to decode the PDCCH candidate. The method may comprise configuring the wireless device 110 to: determine that the wireless device 110 does not support the indicated AL and/or that the wireless device 110 supports a higher AL than the indicated AL; and use the AL that is not 1, 2, 4, 8, or 16 to decode the PDCCH candidate instead of the indicated AL. In certain embodiments, the method may comprise configuring the wireless device 110 to determine the AL that is not 1, 2, 4, 8, or 16. In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 is determined according to the equation:

L may be the AL. N_RB may be a number of resource blocks for the largest configurable (e.g., configured) CORESET of the wireless device 110. N_sym may be a number of symbols for the largest configurable (e.g., configured) CORESET of the wireless device 110. may be a floor function. In certain embodiments, the AL that

is not 1, 2, 4, 8, or 16 may be determined according to the equation:

L may be the AL. N_RB may be a number of resource blocks for the largest configurable (e.g., configured) CORESET of the wireless device. N_sym may be a number of symbols for the largest configurable (e.g., configured) CORESET of the wireless device 110.

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is lower than the indicated AL. The AL that is not 1, 2, 4, 8, or 16 may comprise a punctured version of the indicated AL. The method may comprise configuring the wireless device with a mapping to be used by the wireless device 110 to determine which of a plurality of control channel elements comprising the indicated AL will not be read for the punctured version of the indicated AL.

In certain embodiments, the indicated AL may be an AL 16 and the AL that is not 1, 2, 4, 8, or 16 may be an AL 12. The AL 12 may be a punctured version of the

AL 16.

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is higher than the indicated AL. The method may comprise configuring the wireless device 110 to determine the AL that is higher than the indicated AL. In certain embodiments, the AL that is higher than the indicated AL may be determined according to the equation:

is higher than the indicated AL may be determined according to the equation:

In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be based on a number of overlapping PDCCH candidates. In certain embodiments, the method may comprise determining the AL that is not 1, 2, 4, 8, or 16 that reduces overlap between different PDCCH candidates. In certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be a new AL and determining the new AL may comprise: letting L_new be the new AL, where 2^k-1 < L_new < 2^k; determining an index of a first control channel element for an AL L = 2^k; and using only the first L_new control channel elements of each PDCCH candidate of AL L = 2^k. In certain embodiments, the method may comprise determining an index of control channel elements for AL L_new using the following hash function: for a search space set s associated with a CORESET ^P , control channel element indexes for AL 2^k-1 < L_new < 2^k corresponding to a

PDCCH candidate m_s of the search space set in slot ¹¹ ( _/ for an active DL BWP of a serving cell are given by:

In certain embodiments, for any CSS, In certain embodiments, for

A_p =39827 f_or pmod3 = 0 ,

A_p =39829 for pmod3 = A_p = 39839 for pmod3 = 2 , and D = 65537 . In certain embodiments, i = 0, ••• ,L_new — 1 . N_CCE,p may be a number of control channel elements, numbered from 0 to N_CCE,p - 1 , in CORESET P . In certain embodiments, m_s = 0, . . . , — 1 , where is a number of PDCCH

candidates the wireless device 110 is configured to monitor for AL L_new. In certain embodiments, the first control channel element index may be chosen other than the lowest index given by the hash function above. In certain embodiments, the method may comprise modifying a range of the index i in the hash function of embodiment 74 to start at a non-zero value. In certain embodiments, the method may comprise using one or more last indices up to 2^k — 1, wherein i = 2^k — L_new, ··· , 2^k — 1.

In certain embodiments, the wireless device 110 may be a New Radio reduced capability (NR-RedCap) wireless device 110. In certain embodiments, the wireless device 110 may have a bandwidth of one of: at most 10 MHz; at most 20 MHz; at most 30 MHz; at most 40 MHz; and at most 50 MHz.

In certain embodiments, the network node 160 may comprise a base station. In certain embodiments, the base station may be at least one of: an eNB; and a gNB.

In certain embodiments, the method may comprise: obtaining user data; and forwarding the user data to a host computer or a wireless device 110.

FIGURE 21 illustrates a schematic block diagram of an apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a network node (e.g., network node 160 shown in FIGURE 6). Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 20 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 20 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 1502, determining unit 1504, communication unit 1506, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.

In certain embodiments, apparatus 1500 may be an eNB or a gNB. Apparatus 1500 may be configured to perform a method for configuring a wireless device with an AL for decoding a PDCCH candidate (e.g., the method described above in relation to FIGURE 20).

As illustrated in FIGURE 21, apparatus 1500 includes receiving unit 1502, determining unit 1504, and communication unit 1506. Receiving unity 1502 may be configured to perform the receiving functions of apparatus 1500. For example, receiving unit 1502 may be configured to obtain capability information for a wireless device (e.g., an NR-Redcap wireless device). As another example, receiving unit 1502 may be configured to obtain user data.

Receiving unit 1502 may receive any suitable information (e.g., from a wireless device or another network node). Receiving unit 1502 may include a receiver and/or a transceiver, such as RF transceiver circuitry 172 described above in relation to FIGURE 6. Receiving unit 1502 may include circuitry configured to receive messages and/or signals (wireless or wired). In particular embodiments, receiving unit 1502 may communicate received messages and/or signals to determining unit 1504 and/or any other suitable unit of apparatus 1500. The functions of receiving unit 1502 may, in certain embodiments, be performed in one or more distinct units.

Determining unit 1504 may perform the processing functions of apparatus 1500. For example, determining unit 1504 may be configured to configure a wireless device with an AL that is not 1, 2, 4, 8, or 16 (e.g., for decoding a PDCCH candidate). As another example, determining unit 1504 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 (e.g., an AL that is one of 3, 6, or 12, and/or an AL that is not a power of 2). In certain embodiments, determining unit 1504 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on a number of RBs and a number of symbols of the largest CORESET of the wireless device (e.g., using the equation described above in relation to FIGURE 20). As still

another example, determining unit 1504 may be configured to obtain capability information for the wireless device (e.g., from receiving unit 1502). In certain embodiments, determining unit 1504 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on the obtained capability information.

As another example, determining unit 1504 may be configured to explicitly configure the AL that is not 1, 2, 4, 8, or 16.

As another example, determining unit 1504 may be configured to implicitly configure the AL that is not 1, 2, 4, 8, or 16. In certain embodiments, determining unit 1504 may be configured to cause communication unit 1506 to send, to the wireless device, an indication of an AL that the wireless device should use to decode the PDCCH candidate. Determining unit 1504 may be configured to configure the wireless device to determine that the wireless device does not support the indicated AL and/or that the wireless device supports a higher AL than the indicated AL. Determining unit 1504 may be configured to configure the wireless device to use the AL that is not 1, 2, 4, 8, or 16 to decode the PDCCH candidate instead of the indicated AL. In certain embodiments, determining unit 1504 may be configured to configure the wireless device to determine the AL that is not 1, 2, 4, 8, or 16 (e.g., (e.g., using the equation described above in relation to

FIGURE 20).

As another example, in certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is lower than the indicated AL (e.g., the indicated AL may be AL 16 and the AL that is not 1, 2, 4, 8, or 16 may be an AL 12). The AL that is not 1, 2, 4, 8, or 16 may comprise a punctured version of the indicated AL. In certain embodiments, determining unit 1504 may be configured to configure the wireless device with a mapping to be used by the wireless device to determine which of a plurality of control channel elements comprising the indicated AL will not be read for the punctured version of the indicated AL. In certain embodiments, determining unit 1504 may be configured to determine which of a plurality of control channel elements comprising the indicated AL will not be read for the punctured version of the indicated AL.

As another example, in certain embodiments, the AL that is not 1, 2, 4, 8, or 16 may be an AL that is higher than the indicated AL. Determining unit 1504 may be configured to configure the wireless device to determine the AL that is higher than the indicated AL (e.g., using the equation

described above in relation to FIGURE 20).

As another example, determining unit 1504 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on a level of coverage provided by the AL that is not 1, 2, 4, 8, or 16.

As another example, determining unit 1504 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on a limit on a number of non-overlapping control channel elements that applies to the wireless device.

As another example, determining unit 1504 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 based on a number of overlapping PDCCH candidates. Determining unit 1504 may be configured to determine the AL that is not 1, 2, 4, 8, or 16 that reduces overlap between different PDCCH candidates. In certain embodiments, the aggregation level that is not 1, 2, 4, 8, or 16 may be a new aggregation level, and determining unit 1504 may be configured to determine the new aggregation level. In certain embodiments, determining unit 1504 may be configured to: let L_new be the new AL, where 2^k-1 < L_new < 2^k; determine an index of a first control channel element for an AL L = 2^k; and use only the first L_new control channel elements of each PDCCH candidate of AL L = 2^k. Determining unit 1504 may be configured to determining an index of control channel elements for AL L_new (e.g., using the hash function described above in relation to FIGURE 20). Determining unit 1504 may be configured to modify a range of the index in the hash function to start at a non-zero value. Determining unit 1504 may be configured to use one or more last indices up to 2^k — 1, wherein i = 2^k — L_new, ··· , 2^k — 1.

As another example, determining unit 1504 may be configured to obtain user data.

Determining unit 1504 may include or be included in one or more processors, such as processing circuitry 170 described above in relation to FIGURE 5. Determining unit 1504 may include analog and/or digital circuitry configured to perform any of the functions of determining unit 1504 and/or processing circuitry 170 described above. The functions of determining unit 1504 may, in certain embodiments, be performed in one or more distinct units.

Communication unit 1506 may be configured to perform the transmission functions of apparatus 1500. For example, communication unit 1506 may be configured to send, to the wireless device, an indication of the AL that is not 1, 2, 4, 8, or 16 (e.g., in a SearchSpace information element). As another example, communication unit 1506 may be configured to send, to the wireless device, an indication of an AL that the wireless device should use to decode the PDCCH candidate. As still another example, communication unit 1506 may be configured to forward user data to a host computer or a wireless device.

Communication unit 1506 may transmit messages (e.g., to a wireless device and/or another network node). Communication unit 1506 may include a transmitter and/or a transceiver, such as RF transceiver circuitry 172 described above in relation to FIGURE 5. Communication unit 1506 may include circuitry configured to transmit messages and/or signals (e.g., through wireless or wired means). In particular embodiments, communication unit 1506 may receive messages and/or signals for transmission from determining unit 1504 or any other unit of apparatus 1500. The functions of communication unit 1504 may, in certain embodiments, be performed in one or more distinct units.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

In some embodiments a computer program, computer program product or computer readable storage medium comprises instructions which when executed on a computer perform any of the embodiments disclosed herein. In further examples, the instructions are carried on a signal or carrier and are executable on a computer and when executed perform any of the embodiments disclosed herein. FIGURE 22 depicts another method 1600 in a network node 160 (e.g., a gNB or an eNB), in accordance with certain embodiments. More particularly, FIGURE 22 depicts a method performed by a network node 160 for configuring a wireless device 110 with an AL for decoding a PDCCH candidate. The method begins at step 1602, where the network node 160 configures the wireless device 110 with an aggregation level that is not a power of 2. The aggregation level is a number of CCEs used for at least one PDCCH candidate.

In a particular embodiment, the network node 160 determines, for each PDCCH candidate 41 with the aggregation level that is not a power of 2, the CCEs used for this PDCCH candidate such that this PDCCH candidate overlaps with at most one PDCCH candidate 42 with a second aggregation level. The second aggregation level is a power of 2 and is larger than the aggregation level that is not a power of 2.

In a particular embodiment, the second aggregation level is 2^k ; the aggregation level that is not a power of 2 is larger than 2^k-1 ; and wherein k is a positive integer. In a particular embodiment, there is at least one CCE 43 located between two

PDCCH candidates 41 with the aggregation level that is not a power of 2, and the at least one CCE is unused by all PDCCH candidates with the aggregation level that is not a power of 2.

In a particular embodiment, the aggregation level that is not a power of 2 is a new aggregation level, L_new, and the network node 160 determines an index of the CCEs used for a PDCCH candidate with the aggregation L_new using the following hash function: for a search space set ^s associated with a CORESET ^P, CCE indexes for aggregation level 2^k-1 < L_new < 2^k corresponding to a PDCCH candidate m_s of the search space set in slot

for an active downlink bandwidth part of a serving cell are given by:

CCE indexes for AL L_new:

where for any

A_p = 39827 _for pmod3 = 0 A_p = 39829 _for pmod3 = 1

L = ³⁹⁸³⁹ _for pmod3 = 2 , _and D = 65537 . i 0, ··· , L_new 1, N_CCE,p is a number of control channel elements, numbered from 0 to N_CCE,p ^{_ 1} in CORESET and where is a number of PDCCH

In a further particular embodiment, a first CCE index is chosen other than a lowest index given by the hash function above.

In a further particular embodiment, the network node 160 modifies a range of the index i in the hash function above to start at a non-zero value.

In a further particular embodiment, the network node 160 uses one or more last indices up to 2^k — 1, and i = 2^k — L_new, ··· , 2^k — 1.

In a particular embodiment, the aggregation level that is not a power of 2 is a new aggregation level, L_new , and the network node 160 determines the new aggregation level by:

- letting L_new be the new AL, where 2^fe_1 < L_new < 2^k ;

In a particular embodiment, the configured aggregation level that is not a power of 2 is one of 3, 6, or 12.

In a particular embodiment, the configured aggregation level that is not a power of 2 is a maximum aggregation level that is supported within a configurable CORESET of the wireless device 110.

In a further particular embodiment, the configurable CORESET of the wireless device 110 comprises a largest configurable CORESET of the wireless device.

In a particular embodiment, the configured aggregation level that is not a power of 2 is based on a number of resource blocks and a number of symbols of the largest configurable CORESET of the wireless device 110.

In a particular embodiment, the aggregation level that is not a power of 2 is a maximum aggregation level that is supported by a bandwidth limitation of a CORESET of the wireless device 110.

In a further particular embodiment, a next aggregation level above the aggregation level that is not a power of 2 is not supported within the bandwidth limitation of the CORESET of the wireless device 110.

- L is the aggregation level;

- is a floor function.

In a particular embodiment, configuring the aggregation level that is not a power of 2 includes sending, to the wireless device 110, an indication of the aggregation level that is not a power of 2.

In a particular embodiment, the network node 160 obtains capability information for the wireless device 110.

In a further particular embodiment, network node 160 determines the aggregation level that is not a power of 2 based on the obtained capability information. In a particular embodiment, the network node 160 transmits at least one PDCCH using the aggregation level that is not a power of 2.

In a particular embodiment, the network node 160 comprises a base station.

In a further particular embodiment, the base station is at least one of an eNB and a gNB.

FIGURE 23 illustrates a schematic block diagram of an apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a network node (e.g., network node 160 shown in FIGURE 6). Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 22 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 22 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 1702, determining unit 1704, communication unit 1706, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

In certain embodiments, apparatus 1700 may be an eNB or a gNB. Apparatus 1700 may be configured to perform a method for configuring a wireless device with an AL for decoding a PDCCH candidate (e.g., the method described above in relation to FIGURE 22). As illustrated in FIGURE 23, apparatus 1700 includes receiving unit 1702, determining unit 1704, and communication unit 1706. Receiving unity 1702 may be configured to perform the receiving functions of apparatus 1700. For example, receiving unit 1702 may be configured to obtain capability information for a wireless device (e.g., an NR-Redcap wireless device). As another example, receiving unit 1702 may be configured to obtain user data.

Receiving unit 1702 may receive any suitable information (e.g., from a wireless device or another network node). Receiving unit 1702 may include a receiver and/or a transceiver, such as RF transceiver circuitry 172 described above in relation to FIGURE 6. Receiving unit 1702 may include circuitry configured to receive messages and/or signals (wireless or wired). In particular embodiments, receiving unit 1702 may communicate received messages and/or signals to determining unit 1704 and/or any other suitable unit of apparatus 1700. The functions of receiving unit 1702 may, in certain embodiments, be performed in one or more distinct units.

Determining unit 1704 may perform the processing functions of apparatus 1700. For example, determining unit 1704 may be configured to configure a wireless device with an AL that is not a power of 2 (e.g., for decoding a PDCCH candidate). The aggregation level is a number of CCEs used for at least one PDCCH candidate

As another example, determining unit 1704 may be configured to determine the AL that is not a power of 2 (e.g., an AL that is one of 3, 6, or 12). In certain embodiments, determining unit 1704 may be configured to determine the AL that is not a power of 2 based on a number of RBs and a number of symbols of the largest

CORESET of the wireless device (e.g., using the equation

described above in relation to FIGURE 22). As still another example,

determining unit 1704 may be configured to obtain capability information for the wireless device (e.g., from receiving unit 1702). In certain embodiments, determining unit 1704 may be configured to determine the AL that is not a power of 2 based on the obtained capability information.

As another example, determining unit 1704 may be configured to explicitly configure the AL that is not a power of 2.

As another example, determining unit 1704 may be configured to implicitly configure the AL that is not a power of 2. In certain embodiments, determining unit 1704 may be configured to cause communication unit 1706 to send, to the wireless device, an indication of an AL that the wireless device should use to decode the PDCCH candidate.

Determining unit 1704 may include or be included in one or more processors, such as processing circuitry 170 described above in relation to FIGURE 6. Determining unit 1704 may include analog and/or digital circuitry configured to perform any of the functions of determining unit 1704 and/or processing circuitry 170 described above. The functions of determining unit 1704 may, in certain embodiments, be performed in one or more distinct units.

Communication unit 1706 may be configured to perform the transmission functions of apparatus 1500. For example, communication unit 1706 may be configured to send, to the wireless device, an indication of the AL that is not 1, 2, 4, 8, or 16 (e.g., in a SearchSpace information element). As another example, communication unit 1706 may be configured to send, to the wireless device, an indication of an AL that the wireless device should use to decode the PDCCH candidate. As still another example, communication unit 1706 may be configured to forward user data to a host computer or a wireless device.

Communication unit 1706 may transmit messages (e.g., to a wireless device and/or another network node). Communication unit 1706 may include a transmitter and/or a transceiver, such as RF transceiver circuitry 172 described above in relation to FIGURE 6. Communication unit 1706 may include circuitry configured to transmit messages and/or signals (e.g., through wireless or wired means). In particular embodiments, communication unit 1706 may receive messages and/or signals for transmission from determining unit 1704 or any other unit of apparatus 1700. The functions of communication unit 1706 may, in certain embodiments, be performed in one or more distinct units.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. In some embodiments a computer program, computer program product or computer readable storage medium comprises instructions which when executed on a computer perform any of the embodiments disclosed herein. In further examples, the instructions are carried on a signal or carrier and are executable on a computer and when executed perform any of the embodiments disclosed herein.

EXAMPLE EMBODIMENTS

Example Embodiment 1. A wireless device, the wireless device comprising: processing circuitry configured to perform any of the steps of any of the embodiments described with respect to FIGURES 16 and 18; and power supply circuitry configured to supply power to the wireless device.

Example Embodiment 2. A network node, the network node comprising: processing circuitry configured to perform any of the steps of any of the embodiments described with respect to FIGURES 20 and 22; power supply circuitry configured to supply power to the wireless device.

Example Embodiment 3. A user equipment (UE), the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the embodiments described with respect to FIGURES 16 and 18; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Example Embodiment 4. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a network node having a radio interface and processing circuitry, the network node’s processing circuitry configured to perform any of the steps of any of the embodiments described with respect to FIGURES 20 and 22.

Example Embodiment 5. The communication system of the previous embodiment further including the network node.

Example Embodiment 6. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the network node. Example Embodiment 7. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

Example Embodiment 8. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the steps of any of the embodiments described with respect to FIGURES 20 and 22.

Example Embodiment 9. The method of the previous embodiment, further comprising, at the network node, transmitting the user data.

Example Embodiment 10. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Example Embodiment 11. A user equipment (UE) configured to communicate with a network node, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

Example Embodiment 12. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the embodiments described with respect to FIGURES 16 and 18.

Example Embodiment 13. The communication system of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE.

Example Embodiment 14. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

Example Embodiment 15. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the steps of any of the embodiments described with respect to FIGURES 16 and 18.

Example Embodiment 16. The method of the previous embodiment, further comprising at the UE, receiving the user data from the network node.

Example Embodiment 17. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a network node, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the embodiments described with respect to FIGURES 16 and 18.

Example Embodiment 18. The communication system of the previous embodiment, further including the UE.

Example Embodiment 19. The communication system of the previous 2 embodiments, further including the network node, wherein the network node comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the network node.

Example Embodiment 20. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

Example Embodiment 21. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

Example Embodiment 22. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the network node from the UE, wherein the UE performs any of the steps of any of the embodiments described with respect to FIGURES 16 and 18.

Example Embodiment 23. The method of the previous embodiment, further comprising, at the UE, providing the user data to the network node.

Example Embodiment 24. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

Example Embodiment 25. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

Example Embodiment 26. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a network node, wherein the network node comprises a radio interface and processing circuitry, the network node's processing circuitry configured to perform any of the steps of any of the embodiments described with respect to FIGURES 20 and 22.

Example Embodiment 27. The communication system of the previous embodiment further including the network node.

Example Embodiment 28. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the network node.

Example Embodiment 29. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Example Embodiment 30. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising: at the host computer, receiving, from the network node, user data originating from a transmission which the network node has received from the UE, wherein the UE performs any of the steps of any of the embodiments described with respect to FIGURES 16 and 18.

Example Embodiment 31. The method of the previous embodiment, further comprising at the network node, receiving the user data from the UE.

Example Embodiment 32. The method of the previous 2 embodiments, further comprising at the network node, initiating a transmission of the received user data to the host computer.

Example Embodiment 33. A computer program, the program comprising instructions which when executed on a computer perform any one of the methods of the described with respect to FIGURES 16 and 18.

Example Embodiment 34. A computer program product comprising a computer program, the program comprising instructions which when executed on a computer perform any one of the methods described with respect to FIGURES 16 and 18.

Example Embodiment 35. A computer storage medium comprising a computer program, the program comprising instructions which when executed on a computer perform any one of the methods described with respect to FIGURES 16 and 18.

Example Embodiment 36. A computer storage carrier comprising a computer program, the program comprising instructions which when executed on a computer perform any one of the methods described with respect to FIGURES 16 and 18.

Example Embodiment 37. A computer program, the program comprising instructions which when executed on a computer perform any one of the methods described with respect to FIGURES 20 and 22.

Example Embodiment 38. A computer program product comprising a computer program, the program comprising instructions which when executed on a computer perform any one of the methods described with respect to FIGURES 20 and 22s. Example Embodiment 39. A computer storage medium comprising a computer program, the program comprising instructions which when executed on a computer perform any one of the methods described with respect to FIGURES 20 and 22.

Example Embodiment 40. A computer storage carrier comprising a computer program, the program comprising instructions which when executed on a computer perform any one of the methods described with respect to FIGETRES 20 and 22.

Claims

1. A method (1200) performed by a wireless device (110) for decoding a physical downlink control channel, PDCCH, candidate, the method comprising: being (1202) configured with an aggregation level that is not a power of 2, the aggregation level being a number of control channel elements, CCEs, used per PDCCH candidate; and decoding (1204) at least one PDCCH candidate using the aggregation level that is not a power of 2.

2. The method of Claim 1, further comprising: determining, for each PDCCH candidate (41) with the aggregation level that is not a power of 2, the CCEs used for this PDCCH candidate such that this PDCCH candidate overlaps with at most one PDCCH candidate (42) with a second aggregation level, wherein the second aggregation level is a power of 2 and is larger than the aggregation level that is not a power of 2.

3. The method of Claim 2, wherein the second aggregation level is 2^k , wherein the aggregation level that is not a power of 2 is larger than 2^k_1, and wherein k is a positive integer.

4. The method of any one of Claims 1 to 3, wherein: there is at least one CCE (43) located between two PDCCH candidates (41) with the aggregation level that is not a power of 2, and the at least one CCE is unused by all PDCCH candidates with the aggregation level that is not a power of 2.

5. The method of any one of Claims 1 to 4, wherein the aggregation level that is not a power of 2 is a new aggregation level, L_new , and wherein the method further comprises determining an index of the CCEs used for the at least one PDCCH candidate using the following hash function:

- for a search space set ^s associated with a CORESET ^P, CCE indexes for aggregation level 2^k-1 < L_new < 2^k corresponding to a PDCCH candidate m_s of the search space set in slot

for an active downlink bandwidth part of a serving cell are given by: CCE indexes for AL L_new: 2^k

- where for any CSS, for a US

S,

A_p = 39827 _for pmod3 = 0 A_p = 39829 _for pmod3 = 1

A_p = 39839 _for pmod3 = 2 and D= 65537 ; i = 0, ···, L_new 1, N_CCE,p is a number of control channel elements, numbered from 0 to N_CCE,p ^{- 1} , in CORESET ^P ; and where is a number of PDCCH

6. The method of Claim 5, wherein a first CCE index is chosen other than a lowest index given by the hash function of Claim 5.

7. The method of any one of Claims 5 to 6, further comprising modifying a range of the index i in the hash function of Claim 5 to start at a non-zero value.

8. The method of Claim 7, further comprising:

- using one or more last indices up to 2^k — 1;

- wherein i = 2^k — L_new, ···, 2^k — 1.

9. The method of any one of Claims 1 to 5, wherein the aggregation level that is not a power of 2 is a new aggregation level, L_new , and the method further comprises determining the new aggregation level by:

- letting L_new be the new AL, where 2^fe_1 < L_new < 2^k ;

- determining an index of a first control channel element for an aggregation level L = 2^k; and using only the first L_new control channel elements of each PDCCH candidate of aggregation level L = 2^k.

10. The method of any one of Claims 1 to 9, wherein the aggregation level that is not a power of 2 is greater than 16.

11. The method of any one of Claims 1 to 9, wherein the aggregation level that is not a power of 2 is one of 3, 6, or 12.

12. The method of any one of Claims 1 to 9, wherein the aggregation level that is not a power of 2 is a maximum aggregation level that is supported within a configurable Control Resource Set, CORESET, of the wireless device.

13. The method of Claim 12, wherein the configurable CORESET of the wireless device comprises a largest configurable CORESET of the wireless device.

14. The method of Claim 13, wherein the aggregation level that is not a power of 2 is based on a number of resource blocks and a number of symbols of the largest configurable CORESET of the wireless device.

15. The method of any one of Claims 1 to 9, wherein the aggregation level that is not a power of 2 is a maximum aggregation level that is supported by a bandwidth limitation of a CORESET of the wireless device.

16. The method of Claim 15, wherein a next aggregation level above the aggregation level that is not a power of 2 is not supported within the bandwidth limitation of the CORESET of the wireless device.

17. The method of any one of Claims 1 to 16, wherein: the configured aggregation level that is not a power of 2 is determined according to the equation:

- L is the aggregation level;

- N_Sym is a number of symbols for the largest configurable CORESET of the wireless device; and - is a floor function.

18. The method of any one of Claims 1 to 17, wherein the wireless device is implicitly configured with the aggregation level that is not the power of 2, and wherein being implicitly configured with the aggregation level that is not the power of 2 comprises: receiving, from a network node (160), an indication of an indicated aggregation level that the wireless device should use to decode the PDCCH candidate; determining that the wireless device does not support the indicated aggregation level and/or that the wireless device supports a higher aggregation level than the indicated aggregation level; and using the aggregation level that is not a power of 2 to decode the PDCCH candidate instead of the indicated aggregation level.

19. The method of Claim 18, wherein the aggregation level that is not a power of 2 is an aggregation level that is lower than the indicated aggregation level.

20. The method of Claim 19, wherein: the aggregation level that is not a power of 2 comprises a punctured version of the indicated aggregation level, and the method further comprises determining which of a plurality of CCEs comprising the indicated aggregation level will not be read for the punctured version of the indicated aggregation level.

21. The method of Claim 18, wherein the aggregation level that is not a power of 2 is an aggregation level that is higher than the indicated aggregation level.

22. The method of any one of Claims 1 to 21, wherein the aggregation level that is not a power of 2 is based on a limit on a number of non-overlapping CCEs that applies to the wireless device.

23. The method of any one of Claims 1 to 22, wherein the wireless device is a New Radio reduced capability (NR-RedCap) wireless device.

24. The method of any one of Claims 1 to 23, wherein: the aggregation level that is not a power of 2 is based on one or more capabilities of the wireless device, and the method further comprises sending, to a network node, information indicating the one or more capabilities of the wireless device.

25. A method (1600) performed by a network node (160) for configuring a wireless device (110) with an aggregation level for decoding a physical downlink control channel, PDCCH, candidate, the method comprising: configuring (1602) the wireless device with an aggregation level that is not a power of 2, the aggregation level being a number of control channel elements, CCEs, used per PDCCH candidate.

26. The method of Claim 25, further comprising: determining, for each PDCCH candidate (41) with the aggregation level that is not a power of 2, the CCEs used for this PDCCH candidate such that this PDCCH candidate overlaps with at most one PDCCH candidate (42) with a second aggregation level, wherein the second aggregation level is a power of 2 and is larger than the aggregation level that is not a power of 2.

27. The method of Claim 26, wherein the second aggregation level is 2^k , wherein the aggregation level that is not a power of 2 is larger than 2^k_1, and wherein k is a positive integer.

28. The method of any one of Claims 25 to 27, wherein: there is at least one CCE (43) located between two PDCCH candidates (41) with the aggregation level that is not a power of 2, and the at least one CCE is unused by all PDCCH candidates with the aggregation level that is not a power of 2.

29. The method of any one of Claims 25 to 28, wherein the aggregation level that is not a power of 2 is a new aggregation level, L_new , and wherein the method further comprises determining an index of the CCEs used for a PDCCH candidate with the aggregation L_new using the following hash function:

for an active downlink bandwidth part of a serving cell are given by:

A_p = 39827 _for pmod3 = 0 A_p = 39829 _for pmod3 = 1

A_p = 39839 _for pmod3 = 2 and D= 65537 ; i = 0, ···, L_new 1, is a number of control channel elements, numbered from 0 to

number of PDCCH candidates the wireless device is configured to monitor for the new aggregation level, L_new.

30. The method of Claim 29, wherein a first CCE index is chosen other than a lowest index given by the hash function of Claim 29.

31. The method of any one of Claims 29 to 30, further comprising modifying a range of the index i in the hash function of Claim 29 to start at a non-zero value.

32. The method of Claim 31, further comprising:

- using one or more last indices up to 2^k — 1;

- wherein i = 2^k — L_new, ···, 2^k — 1.

33. The method of any of Claims 25 to 29, wherein the aggregation level that is not a power of 2 is a new aggregation level, L_new , and the method further comprises determining the new aggregation level by: letting L_new be the new AL, where 2^k-1 < L_new < 2^k ; - determining an index of a first control channel element for an aggregation level L = 2^k; and

34. The method of any one of Claims 25 to 33, wherein the aggregation level that is not a power of 2 is greater than 16.

35. The method of any one of Claims 25 to 33, wherein the configured aggregation level that is not a power of 2 is one of 3, 6, or 12.

36. The method of any one of Claims 25 to 33, wherein the configured aggregation level that is not a power of 2 is a maximum aggregation level that is supported within a configurable Control Resource Set, CORESET, of the wireless device.

37. The method of Claim 36, wherein the configurable CORESET of the wireless device comprises a largest configurable CORESET of the wireless device.

38. The method of Claim 37, wherein the configured aggregation level that is not a power of 2 is based on a number of resource blocks and a number of symbols of the largest configurable CORESET of the wireless device.

39. The method of any one of Claims 25 to 33, wherein the aggregation level that is not a power of 2 is a maximum aggregation level that is supported by a bandwidth limitation of a CORESET of the wireless device.

40. The method of Claims 39, wherein a next aggregation level above the aggregation level that is not a power of 2 is not supported within the bandwidth limitation of the CORESET of the wireless device.

41. The method of any one of Claims 25 to 40, wherein: the configured aggregation level that is not a power of 2 is determined according to the equation:

- L is the aggregation level;

- N_RB is a number of resource blocks for the largest configurable CORESET of the wireless device; - is a number of symbols for the largest configurable CORESET

of the wireless device; and

- is a floor function.

42. The method of any of Claims 25 to 41, wherein configuring the aggregation level that is not a power of 2 comprises: sending, to the wireless device, an indication of the aggregation level that is not a power of 2.

43. The method of any one of Claims 25 to 42, wherein the aggregation level that is not a power of 2 is based on a limit on a number of non-overlapping CCEs that applies to the wireless device.

44. The method of any one of Claims 25 to 43, further comprising: obtaining capability information for the wireless device.

45. The method of Claim 44, further comprising: determining the aggregation level that is not a power of 2 based on the obtained capability information.

46. The method of any one of Claims 25 to 45, further comprising transmitting at least one PDCCH using the aggregation level that is not a power of 2.

47. The method of any one of Claims 25 to 46, wherein the wireless device is a New Radio reduced capability (NR-RedCap) wireless device.

48. The method of any one of Claims 25 to 47, wherein the network node comprises a base station.

49. The method of Claim 48, wherein the base station is at least one of: an eNB; and a gNB.

50. A wireless device (110) for decoding a physical downlink control channel, PDCCH, candidate, the wireless device comprising: processing circuitry (120) configured to: be configured with an aggregation level that is not a power of 2, the aggregation level being a number of control channel elements, CCEs, used per PDCCH candidate; and decode at least one PDCCH candidate using the aggregation level that is not a power of 2.

51. The wireless device of Claim 50, wherein the processing circuitry is configured to perform any of the steps of any of Claims 2 to 24.

52. A network node (160) for configuring a wireless device (110) with an aggregation level for decoding a physical downlink control channel, PDCCH, candidate, the network node comprising: processing circuitry (170) configured to: configure the wireless device with an aggregation level that is not a power of 2, the aggregation level being a number of control channel elements, CCEs, used per PDCCH candidate.

53. The network node of Claim 52, wherein the processing circuitry is configured to perform any of the steps of any of Claims 26 to 49.