SYSTEMS

BACKGROUND

[0001] Wireless systems typically include multiple User Equipment (UE) devices communicatively coupled to one or more Base Stations (BS). The one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNB) or New Radio (NR) next generation NodeBs (gNB) that can be communicatively coupled to one or more UEs by a Third- Generation Partnership Project (3 GPP) network.

[0002] Next generation wireless communication systems are expected to be a unified network/system that is targeted to meet vastly different and sometimes conflicting performance dimensions and services. New Radio Access Technology (RAT) is expected to support a broad range of use cases including Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Mission Critical Machine Type Communication (uMTC), and similar service types operating in frequency ranges up to 100 GHz.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

[0004] FIG. 1 illustrates signaling that indicates a presence of an ultra-reliable and low latency communications (URLLC) transmission within scheduled enhanced Mobile Broadband (eMBB) resources in accordance with an example;

[0005] FIG. 2 illustrates a service-specific resource allocation unit (SSRAU) structure in accordance with an example;

[0006] FIG. 3 illustrates mission-critical resource element group (MC-REG) structure candidates in accordance with an example;

[0007] FIG. 4 illustrates a distributed resource mapping in accordance with an example; [0008] FIG. 5 illustrates a physical channel mapping and downlink control information (DCI) format design for a preempted ultra-reliable and low latency communications (URLLC) resource indication in accordance with an example;

[0009] FIG. 6 illustrates an in-band ultra-reliable and low latency communications (URLLC) puncturing indictor (UPI) transmission to indicate puncturing in accordance with an example;

[0010] FIG. 7 illustrates an in-band one-bit on-off signaling transmission in accordance with an example;

[0011] FIG. 8 depicts functionality of a user equipment (UE) operable to perform data communication with a base station in accordance with an example;

[0012] FIG. 9 depicts functionality of a base station operable to perform data

communication with a user equipment (UE) in accordance with an example;

[0013] FIG. 10 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for performing data communication between a user equipment (UE) and a base station in accordance with an example;

[0014] FIG. 11 illustrates an architecture of a wireless network in accordance with an example;

[0015] FIG. 12 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example;

[0016] FIG. 13 illustrates interfaces of baseband circuitry in accordance with an example; and

[0017] FIG. 14 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.

[0018] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

[0019] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

DEFINITIONS

[0020] As used herein, the term "User Equipment (UE)" refers to a computing device capable of wireless digital communication such as a smart phone, a tablet computing device, a laptop computer, a multimedia device such as an iPod Touch®, or other type computing device that provides text or voice communication. The term "User Equipment (UE)" may also be refer to as a "mobile device," "wireless device," of "wireless mobile device."

[0021] As used herein, the term "Base Station (BS)" includes "Base Transceiver Stations (BTS)," "NodeBs," "evolved NodeBs (eNodeB or eNB)," and/or "next generation NodeBs (gNodeB or gNB)," and refers to a device or configured node of a mobile phone network that communicates wirelessly with UEs.

[0022] As used herein, the term "cellular telephone network," "4G cellular," "Long Term Evolved (LTE)," "5G cellular" and/or "New Radio (NR)" refers to wireless broadband technology developed by the Third Generation Partnership Project (3GPP).

EXAMPLE EMBODIMENTS

[0023] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter. [0024] Fifth Generation (5G) New Radio (NR) wireless communication systems are expected to satisfy several use cases, such as enhanced Mobile Broadband (eMBB) and ultra-reliable and low latency communications (URLLC). However, eMBB and URLLC have different specifications in terms of user plane latency and coverage levels. The key specification for URLLC relate to user plane latency and reliability. For example, for

URLLC, the target for user plane latency is 0.5 milliseconds (ms) for uplink (UL) and 0.5 ms for downlink (DL), and the target for reliability is 1-10 ^"5 within 1 ms. As a result, URLLC services are expected to exploit a shorter transmission time interval (TTI) as compared to the TTI used by eMBB services to satisfy the more stringent latency specification for URLLC.

[0025] In 5G NR wireless communication systems, it is important to support efficient multiplexing of eMBB and URLLC services in the same carrier. One multiplexing solution is to have dedicated bandwidth reservation solely for the URLLC service.

However, the disadvantage of this multiplexing solution is that resource utilization becomes inefficient due to the stringent delay and reliability specification for URLLC, as well as random (or bursty) arrival of URLLC packets. Alternatively, a puncturing option to an eMBB data region by URLLC data can provide good efficiency in terms of resource utilization since both URLLC and eMBB can be scheduled on demand. However, the puncturing of the eMBB data with the shortened TTI of URLLC can cause a performance loss for eMBB data.

[0026] In the present technology, mechanisms are described to mitigate coexistence issues of eMBB and URLLC data, especially for the puncturing option. For example, a novel mission-critical data element (MCDE)-based resource element (RE) mapping scheme can be utilized for URLLC resource mapping, which can serve to distribute REs preempted by URLLC evenly across a shortened TTI (or mini-slot). In addition, novel cell-specific and UE-specific signaling mechanisms and a novel physical channel design can allow an eNodeB to inform an eMBB receiver about resources used by an URLLC transmission in a slot, which can take into account a tradeoff between DL control overhead and URLLC resource indication granularity. Thus, the present technology describes a novel mechanism for achieving coexistence of multi-services (e.g., URLLC services and eMBB services) on a same component carrier (CC) to minimize performance loss of eMBB due to the preemption (or priority) of URLLC transmissions. In other words, eMBB and URLLC can be dynamically multiplexed on a same CC for 5G NR wireless communication systems.

[0027] In one example, coexistence issues can persist for the eMBB service because URLLC is to be timely scheduled without waiting in order to meet the stringent latency specification of URLLC. To solve this issue, the eMBB can be punctured in order to allow for the sporadic nature of URLLC transmissions. For example, a base station can signal to a UE regarding a presence of an URLLC transmission within scheduled resources (e.g., eMBB resources for that UE), which can improve a decoding

performance (e.g., enhanced log-likelihood ratio (LLR) computation or correction) at a receiver decoder side.

[0028] FIG. 1 illustrates exemplary signaling that indicates a presence of an ultra-reliable and low latency communications (URLLC) transmission within scheduled enhanced Mobile Broadband (eMBB) resources. Resource elements (REs) can be mapped for a physical downlink shared channel (PDSCH) reception of a first service type. In one example, a UE can receive a first downlink control information (DCI) format or a downlink message identifying a first resource for a first data channel (e.g., for eMBB) transmitted by a network entity (e.g., a base station, a cell or a transmission point). The UE can receive the first DCI format that identifies the first resource used for the first data channel transmitted over a first transmission time interval (TTI) (e.g., a slot). Then, the UE can receive a second physical signaling (e.g., a second DCI format) which identifies a presence of a second resource for a second data channel (e.g., for URLLC) over a second TTI (e.g., a mini-slot). In other words, the second data channel can be related to a service (e.g., for URLLC) that is different than a service (e.g., for eMBB) that is related to the first data channel. Generally speaking, the first data channel can be a first physical downlink shared channel (PDSCH) and the second data channel can be a second PDSCH. The UE can determine a puncturing or rate-matching bandwidth and mini-slot(s) indices for performing rate-matching or puncturing for the detected first data channel around resources of the second data channel, as indicated by the second physical signaling (e.g., the second DCI format) or a second physical channel. The UE can perform rate-matching assuming that the first data channel is not mapped to REs used by resources of the second data channel, or the UE can perform the puncturing option for the first data channel around the detected resources of the second data channel. Thus, the detected resources of the second data channel can preempt or be prioritized over resources of the first data channel that are in a same time-frequency resource. In other words, detected resources of the second PDSCH can preempt or be prioritized over resources of the first PDSCH. In addition, the first DCI format can point to or be associated (linked) with the second physical signaling (e.g., the second DCI format) or the second physical channel to simplify control signal processing of an eMBB receiver.

[0029] In one configuration, a UE can monitor the second DCI format in accordance with a defined periodicity for a DL preemption indication on the first PDSCH that is indicated by the first DCI format. The second TTI used as a reference downlink resource for the DL preemption indication can be equal to a monitoring periodicity of the second DCI format carrying the DL preemption indication. A frequency region of the reference downlink resource for the second PDSCH indicated by the second DCI format can be configured explicitly by higher layers or is implicitly derived based on a system bandwidth.

[0030] In one configuration, the UE can decode data received from the base station. At the UE side, bits carried in first PDSCH resources allocated by the first DCI format that are preempted by second PDSCH resources allocated by the second DCI format can be set to zero to improve a decoding performance of the first PDSCH at the UE.

[0031] FIG. 2 illustrates an exemplary service-specific resource allocation unit (SSRAU) structure. More specifically, FIG. 2 illustrates a preemption of resources with a SSRAU concept for the case of URLCC. A SSRAU can be defined for resource allocation (RA) of different service types in order to minimize a control signaling overhead of a second data channel, such as a second PDSCH. A scalable SSARU structure can be used to describe resources occupied by a second data channel (e.g., for URLLC operations). A wide-band SSRAU for the RA of the second data channel (e.g., for URLLC) can be defined as ^{m a} time domain and K resource blocks (e.g., physical or virtual resource blocks) in a frequency domain, where Njym _f c ^sioi denotes a number of OFDM symbols in a mini-slot and K can be a function of N^^ ^{l slot} .

[0032] As an example, N^^ ^slot = 2 and K = 6, such that both the first SSRAU (e.g., for eMBB) and a second SSRAU (e.g., for URLLC) can include a same number of REs to maintain constant overhead and code block sizes that are not too small. In one example, resources used for a second DCI format transmission can be included in a first DCI format or implicitly derived based on the resources allocated by the first DCI in accordance with predefined rules.

[0033] In one example, the first SSRAU and the second SSRAU can include different resource blocks in a frequency domain and different symbols in a time domain, and the first SSRAU and the second SSRAU can include a same number of resource elements (REs).

[0034] In one example, the second data channel can be transmitted on an aggregation of one or several mission-critical data elements (MCDEs), where a MCDE consists of multiple mission-critical resource element groups (MC-REGs). The MCDEs available in a system bandwidth or service-specific resource sets across a second TTI can be numbered from 0 to N _MCDE — 1, where NMCDE denotes a number of MCDEs. One second physical data channel can utilize either a localized transmission or distributed

transmission, which can be configured by higher layers per UE or dynamically indicated by the second physical channel. In addition, the MC-REGs can be used for defining the mapping of the second data channel (e.g., for URLLC) to REs.

[0035] FIG. 3 illustrates exemplary mission-critical resource element group (MC-REG) structure candidates. For example, REs forming one MC-REG can be distributed evenly across a whole bandwidth (or a configured bandwidth region) to provide various benefits, such as to minimize performance impacts on a given first data channel and/or to provide frequency diversity. In some cases, all REs except some REs or resource blocks (RBs) can be assumed by the UE to be used for reference signaling (RS), which can include a demodulation reference signal (DMRS), channel state information Reference Signals (CSI-RS), beam-specific reference signals (BRS), or for synchronization signals or for carrying a NR master information block (MIB) or system information blocks (SIBs), and one RB in one symbol can constitute a first MC-REG in an increasing order of frequency. In other words, one MC-REG can span over one RB.

[0036] In one example, a second MC-REG can consist of of REs k within one symbol with k = k ₀ + 0, k ₀ + 1, ... , k ₀ + 5 and the other MC-REG, or a third MC-REG, can consist of REs k within one OFDM symbol with k = k ₀ + 6, k ₀ + 7, ... , k ₀ + 11, respectively, wherein ko is a first RE in a frequency index in a PRB (assuming a PRB spans 12 subcarriers in the frequency domain). Alternatively, a fourth MC-REG can consist of even REs k (i.e., frequency index) within one OFDM symbol with k = k ₀ + 0, k ₀ + 2, ... , k ₀ + 10 and the other MC-REG, or a fifth MC-REG, can consist of odd REs k within one OFDM symbol with k = k ₀ + 1, k ₀ + 7, ... , k ₀ + 11, respectively. In another example, MC-REG ί can generally consist of K evenly distributed REs within one PRB with index k, k = k ₀ + i + I ^■ for different MC-REG sizes, as shown in FIG. 3. In addition, a same principle can be applied for a case where the PRB spans a different number of subcarriers in the frequency domain, e.g., 8 subcarriers, 16 subcarriers, 28 subcarriers, etc.

[0037] In one example, with respect to the MC-REG structures, resource allocation (RA) information for a second data channel can indicate to a scheduled UE a set of distributed MCDEs and a MCDE number n corresponding to: for localized mapping, MC-REGs numbered (n mod N _ _REG + JKC- _RE G in PRB index (k + n x C-I _E G/KC- _RE G + N _RB )' ^or f° ^r distributed mapping, MC-REGs numbered n mod N^- _RE G ^M

0, 1, ... , Z-I _E G/N _M C- _RE G - U = 0, 1, - , C- _E G ^~ 1, N g is a total number of RBs on this CC, and N _MC - _REG is ^a number of MC-REGs within a single RB. For example, N _MC - _REG ⁼ 2 f° ^r the second/fourth MC-REG structure, as shown in FIG. 3.

[0038] FIG. 4 illustrates an example of a distributed resource mapping for a second data channel. Second channel transmissions (e.g., for URLLC) can involve aggregation of two

MCDEs in a distributed manner with a MC-REG structure, assuming N^g = 0, N _RB = 48, = 3. As shown, the distributed resource mapping can be for MCDE X and for MCDE X with an offset shifting in a frequency domain. In one example, a frequency- domain offset value can be introduced for resource mapping in order to guarantee that RBs carrying MC-REGs in different symbols are not the same. The offset value can be fixed in a specification, or can be varied for different mini-slot length configurations as a function of the symbol index. Alternatively, the offset value can be derived using a pseudo-random function of the symbol index, a UE ID, a physical or virtual cell-ID, a mini-slot index and/or a slot index. Thus, the distribution of MCDE transmissions can be maximized across symbols within one mini-slot to avoid interference among adjacent cells.

[0039] In one configuration, various schemes are described to indicate a presence and a position of REs preempted by a second channel (e.g., for mission-critical URLLC traffic). After the presence of the second channel is detected, a UE can discard corresponding LLRs received from corresponding REs during decoding. For example, a discarding bits operation can be implemented by setting calculated LLR values to 0 or other predefined values for all symbols received from the preempted REs.

[0040] On one example, a new DCI format X can be used to indicate a resource occupied by a second channel in a first TTI, and can be detectable for a group of UEs. For example, the new DCI format X can be used to transmit the following information: RA number 1, RA number 1 , ... , RA number N.

[0041] FIG. 5 illustrates an example of a physical channel mapping and downlink control information (DCI) format design for a preempted ultra-reliable and low latency communications (URLLC) resource indication. For example, one field of RA number ί can be used to indicate preempted resource blocks or MCDEs by a second channel (e.g., for URLLC) in a second TTI ί— 1. In a first alternative, as shown in FIG. 5, each RA number field in a new DCI format can include a bitmap indicating SSRAUs or MCDEs that are occupied by second channels in a second TTI, where the SSRAUs or the MCDEs are a set of physical RBs or MC-REGs. The field number N can be equal to a number of second TTIs within a first TTI, and the bitmap of each RA number field can depend on the number of SSRAU or MCDEs in a second TTI. An order of SSRAU or MCDEs for bit mapping can be such that SSRAU or MCDE 0 to N are mapped to a most significant bit (MSB) to a least significant bit (LSB) of the bitmap. The SSRAU or MCDE can preempted by the second channel when a corresponding bit value in the bitmap is equal to 1, and the SSRAU or MCDE are not occupied otherwise. Alternatively, the RA number field can be used to indicate an actual number of consecutive SSRAUs or MCDEs used for second channel(s) transmissions. In a second alternative, as shown in FIG. 5, the RA number field can be used to indicate a predefined partem index or a resource index from a few pre-defined configurations. As an example, a 3 -bit index field can be defined to indicate eight resource allocation options, including full PRBs, one of the

first/second/third/fourth 1/4 PRBs, top half PRBs or bottom half PRBs. [0042] In one example, this DCI format can be cell specific or group specific. Further, a new radio network temporary identifier (RNTI), e.g., a mission-critical RNTI (MC- RNTI), can be defined for a transmission of a NR physical downlink control channel (PDCCH), wherein a cyclic redundancy code (CRC) can scrambled by the MC-RNTI. This MC-RNTI can be predefined or configured by higher layers via an NR master information block (xMIB), an NR system information block (xSIB) or radio resource control (RRC) signaling.

[0043] In one configuration, a frequency domain location of the physical channel carrying the new DCI format X can be configured via higher layers or can be predefined. For example, the physical channel can be configured by higher layers to transmit over part of a whole bandwidth in order to minimize a performance loss of a first channel, as well as to sustain a puncturing of a new channel (e.g., the physical channel) but still satisfy performance criteria. In another example, one on-off signal can be configured by higher layers to semi-statically control a presence of the new channel used for carrying the DCI format in order to avoid unnecessary power consumption at the UE for blind detection of the physical channel, e.g., in the case when the second channel is not present for a relatively long time window. In addition, the UE can assume no second channel presence when no new DCI format was detected in a first TTI.

[0044] FIG. 6 illustrates an example of an in-band ultra-reliable and low latency communications (URLLC) puncturing indictor (UPI) transmission to indicate puncturing. One URLLC Puncturing Indicator (UPI) format X can be used to indicate resources occupied by a second channel (e.g., for URLLC) within an allocated bandwidth of a first channel (e.g., for eMBB) in a first TTI. In a first alternative, as shown in FIG. 6, a whole bandwidth can be divided into multiple URLLC bands (U-band) according to an SSRAU value, and each bit in the UPI can be used to indicate a presence of the URLLC for a particular U-band. In a second alternative, as shown in FIG. 6, bands allocated for the first channel can be divided into multiple U-bands, and each bit in the UPI can indicate the URLLC presence for a particular U-band. As an example, six (mini-slot number) multiplied by two (U-bands number) is equal to 12 bits, which can be opportunistically transmitted within the eMBB bands. Further, the UPI bits can be punctured into a bit stream of the first channel using a same modulation as the data (or a configured modulation order, or QPSK modulation or using outermost constellation points of the modulation used for data), and can be transmitted within the allocated PRBs of the first channel in a last symbol, e.g., mapped in sequence between edges of the bandwidth of the first channel. In addition, the payload size of the UPI can be varied depending on an actual number of eMBB RBs allocated for a given UE and ab exact position in the frequency domain.

[0045] In one example, RE numbers used for the UPI can be a function of data modulation and coding scheme (MCS), a coding rate of the first channel and a target performance difference between the UPI and data of the first channel. As one example, the REs number can be determined as follows:

' M _sc N _sym offset

Q = min(

da ), where O _UPI is a number of UPI bits and O _data is a number of information bits transmitted in the first channel, M^ ^SCH is a scheduled bandwidth for the first channel in the first TTI expressed as a number of subcarriers, N y^ ^CH is a number of single carrier frequency division multiple access (SC-FDMA) symbols in a current first channel transmission, and βο fset is configured by higher layers.

[0046] FIG. 7 illustrates an example of an in-band one-bit on-off signaling transmission. For example, one-bit on-off indicator signaling can be used to dynamically indicate a presence of a second type channel in a band reserved for second channel(s)

transmission(s) in a second TTI. The UE can perform a discontinuous transmission (DTX) detection for a presence of second channel(s) when scheduled with a first channel transmission. Additional bits (e.g., 2-bits) can be used to additionally indicate RB information of the second channel in the frequency domain. In another example, a UE scheduled with the first channel transmission can monitor the DCI formats used to schedule the second channel or the presence of a predefined channel (e.g., a demodulation reference signal (DMRS) sequence of the second channel can be detectable for the UE scheduled with the first channel) in each predetermined position per each second TTI in order to identify the resources punctured by the second channel transmission.

[0047] In one configuration, a method of wireless communication can include receiving a first DCI format indicating a first type of service-specific resource allocation unit (SSRAU) in a first TTI for first channel data reception or transmission. The method of wireless communication can include receiving a second DCI format indicating a second type of service-specific resource allocation unit (SSRAU) for second data channel(s) transmission in one or multiple second TTIs within the first TTI. The method of wireless communication can include identifying resources preempted by the resources indicated by the second DCI format within the allocated first type of SSRAU indicated by the first DCI format. The method of wireless communication can include decoding or transmitting data on the resources scheduled by the first DCI format with handling of preempted resources identified by the second DCI format.

[0048] In one example, the first SSRAU and the second SSRAU includes different resource blocks in a frequency domain and different symbols in a time domain. In another example, the first SSRAU and the second SSRAU can include a same number of REs. In yet another example, one second data channel can be transmitted on an aggregation of one or several mission-critical data elements (MCDEs), where a MCDE consists of multiple mission-critical resource element groups (MC-REGs), and the MC-REGs can be used for defining the mapping of the second data channel to resource elements (REs).

[0049] In one example, the method of wireless communication can include grouping a set of REs in a second TTI to constitute MC-REGs, grouping a set of MC-REGs to constitute one more MCDEs, and aggregating one or more MCDEs for a second data channel transmission. In another example, MC-REG ί generally consists of K evenly distributed REs within one PRB with index k, k = k ₀ + i + I ^■ In yet another example, the second physical data channel can use either localized transmissions or distributed transmissions, which can be configured by higher layers.

[0050] In one example, the second DCI format can be transmitted to a group of UEs and can include multiple resource allocation (RA) number fields, where each RA number field can be used to indicate preempted resource blocks or MCDEs by the second channel in the second TTI. In another example, each RA number field in the second DCI format can include a bitmap indicating the SSRAUs or MCDEs that are occupied by second channels in the second TTI. In yet another example, an RA number field within the second DCI format can be equal to the number of second TTIs within a first TTI, and the bitmap of each RA number field can depend on the number of SSRAUs or MCDEs in the second TTI. In addition, the RA number field can be used to indicate an actual number of consecutive SSRAU or MCDE used for second channel (s)

transmissions.

[0051] In one example, a frequency domain location of a physical channel carrying the second DCI format can be higher layer configured to transmit over part of a whole bandwidth. In another example, One on-off signal can be configured by higher layers to semi-statically control a presence of the physical channel used for carrying the second DCI format. In yet another example, one URLLC Puncturing Indicator (UPI) can be transmitted in the second DCI format within the RBs allocated by the first DCI format to indicate resources occupied by the second channels.

[0052] In one example, a whole bandwidth can be divided into multiple URLLC bands (U-band) according to an SSRAU value, and each bit in the UPI can be used to indicate the presence of the URLLC for a particular U-band. In another example, bands allocated for a first channel can be divided into multiple U-bands, and each bit in the UPI can indicate the URLLC presence for a particular U-band. In yet another example, RE numbers used for the UPI can be a function of data MCS, a coding rate of the first channel and a target performance difference between the UPI and data of the channel. In addition, a UE scheduled with a first channel transmission can monitor the DCI formats used to schedule the second channel or the presence of a predefined channel (e.g., a

DMRS sequence of a second channel in each predetermined position per each second TTI to determine the presence of second channel transmissions).

[0053] Another example provides functionality 800 of a user equipment (UE) operable to perform data communication with a base station, as shown in FIG. 8. The UE can comprise one or more processors configured to decode, at the UE, a first downlink control information (DCI) format received from the base station, wherein the first DCI format identifies a first type of service-specific resource allocation unit (SSRAU) used for resource allocation in a first data channel transmitted over a first transmission time interval (TTI), as in block 810. The UE can comprise one or more processors configured to decode, at the UE, a second DCI format received from the base station, wherein the second DCI format identifies a second type of SSRAU used for resource allocation in a second data channel transmitted over a second TTI, as in block 820. The UE can comprise one or more processors configured to identify, at the UE, resources allocated by the second DCI format that preempt resources allocated by the first DCI format that are in a same time-frequency resource, as in block 830. The UE can comprise one or more processors configured to perform, at the UE, a data communication with the base station using the resources allocated by the first DCI format that are not preempted by the resources allocated by the second DCI format, as in block 840. In addition, the UE can comprise a memory interface configured to send to a memory the first DCI format and the second DCI format.

[0054] Another example provides functionality 900 of a base station operable to perform data communication with a user equipment (UE), as shown in FIG. 9. The base station can comprise one or more processors configured to encode, at the baes station, a first downlink control information (DCI) format for transmission to the UE, wherein the first DCI format identifies a first type of service-specific resource allocation unit (SSRAU) used for resource allocation in a first data channel transmitted over a first transmission time interval (TTI), as in block 910. The base station can comprise one or more processors configured to encode, at the base station, a second DCI format for

transmission to the UE, wherein the second DCI format identifies a second type of SSRAU used for resource allocation in a second data channel transmitted over a second TTI having a period that is within a period of the first TTI, as in block 920. The base station can comprise one or more processors configured to perform, at the base station, a data communication with the UE using resources allocated by the first DCI format that are not preempted by resources allocated by the second DCI format, as in block 930. In addition, the base station can comprise a memory interface configured to send to a memory the first DCI format and the second DCI format.

[0055] Another example provides at least one machine readable storage medium having instructions 1000 embodied thereon for performing data communication between a user equipment (UE) and a base station, as shown in FIG. 10. The instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The instructions when executed by one or more processors of the UE perform: decoding, at the UE, a first downlink control information (DCI) format received from the base station, wherein the first DCI format identifies a first type of service-specific resource allocation unit (SSRAU) used for resource allocation in a first data channel transmitted over a first transmission time interval (TTI) as in block 1010. The instructions when executed by one or more processors of the UE perform: decoding, at the UE, a second DCI format received from the base station, wherein the second DCI format identifies a second type of SSRAU used for resource allocation in a second data channel transmitted over a second TTI having a period that is within a period of the first TTI as in block 1020. The instructions when executed by one or more processors of the UE perform: identifying, at the UE, resources allocated by the second DCI format that preempt resources allocated by the first DCI format that are in a same time-frequency resource as in block 1030. The instructions when executed by one or more processors of the UE perform: performing, at the UE, a data communication with the base station using the resources allocated by the first DCI format that are not preempted by the resources allocated by the second DCI format as in block 1040.

[0056] FIG. 11 illustrates an architecture of a system 1100 of a network in accordance with some embodiments. The system 1100 is shown to include a user equipment (UE) 1101 and a UE 1102. The UEs 1101 and 1102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

[0057] In some embodiments, any of the UEs 1101 and 1102 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

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

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

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

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

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

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

[0064] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1111 and 1112 to the UEs 1101 and 1102, while uplink transmissions can utilize similar techniques. The grid can be a time- frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane

representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time- frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

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

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

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

[0068] The RAN 1110 is shown to be communicatively coupled to a core network (CN) 1120— via an S I interface 1113. In embodiments, the CN 1120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S I interface 1113 is split into two parts: the Sl-U interface 1114, which carries traffic data between the RAN nodes 1111 and 1112 and the serving gateway (S-GW) 1122, and the SI -mobility management entity (MME) interface 1115, which is a signaling interface between the RAN nodes 1111 and 1112 and MMEs 1121.

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

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

[0070] The S-GW 1122 may terminate the SI interface 1113 towards the RAN 1110, and routes data packets between the RAN 1110 and the CN 1120. In addition, the S-GW 1122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

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

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

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

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

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

modulation/demodulation circuitry of the baseband circuitry 1204 may include Fast- Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1204 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

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

[0077] In some embodiments, the baseband circuitry 1204 may provide for

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

[0078] RF circuitry 1206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1208 and provide baseband signals to the baseband circuitry 1204. RF circuitry 1206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1204 and provide RF output signals to the FEM circuitry 1208 for transmission. [0079] In some embodiments, the receive signal path of the RF circuitry 1206 may include mixer circuitry 1206a, amplifier circuitry 1206b and filter circuitry 1206c. In some embodiments, the transmit signal path of the RF circuitry 1206 may include filter circuitry 1206c and mixer circuitry 1206a. RF circuitry 1206 may also include synthesizer circuitry 1206d for synthesizing a frequency for use by the mixer circuitry 1206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1206a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1208 based on the synthesized frequency provided by synthesizer circuitry 1206d. The amplifier circuitry 1206b may be configured to amplify the down-converted signals and the filter circuitry 1206c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1204 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1206a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

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

[0081] In some embodiments, the mixer circuitry 1206a of the receive signal path and the mixer circuitry 1206a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 1206a of the receive signal path and the mixer circuitry 1206a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1206a of the receive signal path and the mixer circuitry 1206a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1206a of the receive signal path and the mixer circuitry 1206a of the transmit signal path may be configured for super-heterodyne operation. [0082] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1204 may include a digital baseband interface to communicate with the RF circuitry 1206.

[0083] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

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

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

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

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

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

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

[0090] In some embodiments, the FEM circuitry 1208 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1206). The transmit signal path of the FEM circuitry 1208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1210). [0091] In some embodiments, the PMC 1212 may manage power provided to the baseband circuitry 1204. In particular, the PMC 1212 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 1212 may often be included when the device 1200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 1212 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation

characteristics.

[0092] While FIG. 12 shows the PMC 1212 coupled only with the baseband circuitry 1204. However, in other embodiments, the PMC 1212 may be additionally or

alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1202, RF circuitry 1206, or FEM 1208.

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

[0094] If there is no data traffic activity for an extended period of time, then the device 1200 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 1200 may not receive data in this state, in order to receive data, it must transition back to

RRC Connected state.

[0095] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

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

[0097] FIG. 13 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 1204 of FIG. 12 may comprise processors 1204a-1204e and a memory 1204g utilized by said processors. Each of the processors 1204a-1204e may include a memory interface, 1304a-1304e, respectively, to send/receive data to/from the memory 1204g.

[0098] The baseband circuitry 1204 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1312 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1204), an application circuitry interface 1314 (e.g., an interface to send/receive data to/from the application circuitry 1202 of FIG. 12), an RF circuitry interface 1316 (e.g., an interface to send/receive data to/from RF circuitry 1206 of FIG. 12), a wireless hardware connectivity interface 1318 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 1320 (e.g., an interface to send/receive power or control signals to/from the PMC 1212.

[0099] FIG. 14 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile

communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (R E), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network

(WLAN), a wireless personal area network (WPAN), and/or a WWAN. The wireless device can also comprise a wireless modem. The wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). The wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.

[00100] FIG. 14 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.

Examples

[00101] The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments. [00102] Example 1 includes an apparatus of a user equipment (UE) operable to perform data communication with a base station, the UE comprising: one or more processors configured to: decode, at the UE, a first downlink control information (DCI) format received from the base station, wherein the first DCI format identifies a first type of service-specific resource allocation unit (SSRAU) used for resource allocation in a first data channel transmitted over a first transmission time interval (TTI); decode, at the UE, a second DCI format received from the base station, wherein the second DCI format identifies a second type of SSRAU used for resource allocation in a second data channel transmitted over a second TTI; identify, at the UE, resources allocated by the second DCI format that preempt resources allocated by the first DCI format that are in a same time- frequency resource; and perform, at the UE, a data communication with the base station using the resources allocated by the first DCI format that are not preempted by the resources allocated by the second DCI format; and a memory interface configured to send to a memory the first DCI format and the second DCI format.

[00103] Example 2 includes the apparatus of Example 1, further comprising a transceiver configured to: receive the first DCI format from the base station; receive the second DCI format from the base station; and perform the data communication with the base station using resources that are determined based on the first DCI format and the second DCI format.

[00104] Example 3 includes the apparatus of any of Examples 1 to 2, wherein the first data channel is a first physical downlink shared channel (PDSCH) and the second data channel is a second PDSCH.

[00105] Example 4 includes the apparatus of any of Examples 1 to 4, wherein the second TTI has a period that is within a period of the first TTI.

[00106] Example 5 includes the apparatus of any of Examples 1 to 4, wherein the one or more processors are further configured to monitor the second DCI format in accordance with a defined periodicity for a downlink (DL) preemption indication on the first data channel that is indicated by the first DCI format using the first type of SSRAU, wherein the first data channel is a first physical downlink shared channel (PDSCH), wherein the second TTI used as a reference downlink resource for the DL preemption indication is equal to a monitoring periodicity of the second DCI format carrying the DL preemption indication.

[00107] Example 6 includes the apparatus of any of Examples 1 to 5, wherein a frequency region of the reference downlink resource for the second data channel indicated by the second DCI format is configured explicitly by higher layers or is implicitly derived based on a system bandwidth, wherein the second data channel is a second physical downlink shared channel (PDSCH).

[00108] Example 7 includes the apparatus of any of Examples 1 to 6, wherein: the first type of SSRAU and the second type of SSRAU include different resource blocks in a frequency domain and different symbols in a time domain; and the first type of SSRAU and the second type of SSRAU include a same number of resource elements (REs).

[00109] Example 8 includes the apparatus of any of Examples 1 to 7, wherein the one or more processors configured to perform the data communication are further configured to: encode data for transmission to the base station; or decode data received from the base station, wherein bits carried in first data channel resources allocated by the first DCI format that are preempted by second data channel resources allocated by the second DCI format are set to zero to improve a decoding performance of the first data channel at the UE, wherein the first data channel is a first physical downlink shared channel (PDSCH) and the second data channel is a second PDSCH.

[00110] Example 9 includes the apparatus of any of Examples 1 to 8, wherein: the second data channel is received at the UE using one or more aggregated mission-critical data elements (MCDEs), wherein a MCDE includes multiple mission-critical resource element groups (MC-REGs), wherein the MC-REGs define a mapping of the second data channel to resource elements (REs); a set of REs are grouped in the second TTI to form the MC- REGs, wherein a set of MC-REGs are grouped to form one or more MCDEs, wherein the one or more MCDEs are aggregated for transmissions over the second data channel; or a MC-REG includes K evenly distributed REs within one physical resource block (PRB), wherein K is an integer.

[00111] Example 10 includes the apparatus of any of Examples 1 to 9, wherein the second data channel utilizes localized transmissions or distributed transmissions that are configured via higher layer signaling. [00112] Example 11 includes the apparatus of any of Examples 1 to 10, wherein: the second DCI format includes one or more resource allocation (RA) fields, wherein a RA field indicates preempted resource blocks or mission-critical data elements (MCDEs) by the second data channel in the second TTI; the RA field includes a bitmap indicating SSRAUs or MCDEs that occupy the second data channel in the second TTI; the RA field is equal to the second TTI within the first TTI and the bitmap of each RA field corresponds to the SSRAUs or MCDEs in the second TTI; or the RA field indicates an actual number of consecutive SSRAUs or MCDEs used for transmissions over the second data channel.

[00113] Example 12 includes the apparatus of any of Examples 1 to 11, wherein: a frequency domain location of the second data channel carrying the second DCI format is configured via a higher layer to transmit over a portion of a bandwidth; or an on-off signal is configured via the higher layer to semi-statically control a presence of the second data channel used for carrying the second DCI format.

[00114] Example 13 includes the apparatus of any of Examples 1 to 12, wherein: an ultra- reliable and low latency communications (URLLC) puncturing indictor (UPI) is transmitted in the second DCI format with resources allocated by the first DCI format, wherein the UPI is used to indicate resources occupied by the second data channel; a bandwidth is divided into multiple URLLC bands (U-bands) in accordance with the second type of SSRAU, and each bit in the UPI indicates a presence of a URLLC for a defined U-band; or bands allocated for the first data channel are divided into multiple U- bands, wherein each bit in the UPI indicates a presence of a URLCC for a defined U- band, wherein a number of resource elements (REs) used for the UPI is a function of a modulation and coding scheme (MCS) for data, a coding rate of the first data channel and a target performance difference between the UPI and data carried over the first data channel.

[00115] Example 14 includes an apparatus of a base station operable to perform data communication with a user equipment (UE), the base station comprising: one or more processors configured to: encode, at the baes station, a first downlink control information (DCI) format for transmission to the UE, wherein the first DCI format identifies a first type of service-specific resource allocation unit (SSRAU) used for resource allocation in a first data channel transmitted over a first transmission time interval (TTI); encode, at the base station, a second DCI format for transmission to the UE, wherein the second DCI format identifies a second type of SSRAU used for resource allocation in a second data channel transmitted over a second TTI having a period that is within a period of the first TTI; and perform, at the base station, a data communication with the UE using resources allocated by the first DCI format that are not preempted by resources allocated by the second DCI format; and a memory interface configured to retrieve from a memory the first DCI format and the second DCI format.

[00116] Example 15 includes the apparatus of Example 14, wherein the first data channel is a first physical downlink shared channel (PDSCH) and the second data channel is a second PDSCH.

[00117] Example 16 includes the apparatus of any of Examples 14 to 15, wherein the one or more processors are further configured to configure, by the base station, a defined periodicity for the UE to monitor the second DCI for a downlink (DL) preemption indication on the first data channel that is indicated by the first DCI format using the first type of SSRAU, wherein the first data channel is a first physical downlink shared channel (PDSCH), wherein the second TTI used as a reference downlink resource for the DL preemption indication is equal to a monitoring periodicity of the second DCI format carrying the DL preemption indication.

[00118] Example 17 includes the apparatus of any of Examples 14 to 16, wherein a frequency region of the reference downlink resource for the second data channel indicated by the second DCI format is configured explicitly by higher layers or is implicitly derived based on a system bandwidth, wherein the second data channel is a second physical downlink shared channel (PDSCH).

[00119] Example 18 includes the apparatus of any of Examples 14 to 17, wherein: the first type of SSRAU and the second type of SSRAU include different resource blocks in a frequency domain and different symbols in a time domain; and the first type of SSRAU and the second type of SSRAU include a same number of resource elements (REs).

[00120] Example 19 includes the apparatus of any of Examples 14 to 18, wherein the one or more processors are further configured to: encode the second data channel for transmission from the base station using one or more aggregated mission-critical data elements (MCDEs), wherein a MCDE includes multiple mission-critical resource element groups (MC-REGs), wherein the MC-REGs define a mapping of the second data channel to resource elements (REs); group a set of REs in the second TTI to form the MC-REGs; or group a set of MC-REGs to form one or more MCDEs, wherein the one or more MCDEs are aggregated for transmissions over the second data channel, wherein a MC- REG includes K evenly distributed REs within one physical resource block (PRB), wherein K is an integer.

[00121] Example 20 includes the apparatus of any of Examples 14 to 19, wherein the second data channel utilizes localized transmissions or distributed transmissions that are configured via higher layer signaling.

[00122] Example 21 includes the apparatus of any of Examples 14 to 20, wherein: the second DCI format includes one or more resource allocation (RA) fields, wherein a RA field indicates preempted resource blocks or mission-critical data elements (MCDEs) by the second data channel in the second TTI; the RA field includes a bitmap indicating SSRAUs or MCDEs that occupy the second data channel in the second TTI; the RA field is equal to the second TTI within the first TTI and the bitmap of each RA field corresponds to the SSRAUs or MCDEs in the second TTI; or the RA field indicates an actual number of consecutive SSRAUs or MCDEs used for transmissions over the second data channel.

[00123] Example 22 includes the apparatus of any of Examples 14 to 21, wherein: a frequency domain location of the second data channel carrying the second DCI format is configured via a higher layer to transmit over a portion of a bandwidth; or an on-off signal is configured via the higher layer to semi-statically control a presence of the second data channel used for carrying the second DCI format.

[00124] Example 23 includes the apparatus of any of Examples 14 to 22, wherein: an ultra-reliable and low latency communications (URLLC) puncturing indictor (UPI) is transmitted in the second DCI format with resources allocated by the first DCI format, wherein the UPI is used to indicate resources occupied by the second data channel; a bandwidth is divided into multiple URLLC bands (U-bands) in accordance with the second type of SSRAU, and each bit in the UPI indicates a presence of a URLLC for a defined U-band; or bands allocated for the first data channel are divided into multiple U- bands, wherein each bit in the UPI indicates a presence of a URLCC for a defined U- band.

[00125] Example 24 includes at least one machine readable storage medium having instructions embodied thereon for performing data communication between a user equipment (UE) and a base station, the instructions when executed by one or more processors of the UE perform the following: decoding, at the UE, a first downlink control information (DCI) format received from the base station, wherein the first DCI format identifies a first type of service-specific resource allocation unit (SSRAU) used for resource allocation in a first data channel transmitted over a first transmission time interval (TTI); decoding, at the UE, a second DCI format received from the base station, wherein the second DCI format identifies a second type of SSRAU used for resource allocation in a second data channel transmitted over a second TTI having a period that is within a period of the first TTI; identifying, at the UE, resources allocated by the second DCI format that preempt resources allocated by the first DCI format that are in a same time-frequency resource; and performing, at the UE, a data communication with the base station using the resources allocated by the first DCI format that are not preempted by the resources allocated by the second DCI format.

[00126] Example 25 includes the at least one machine readable storage medium of Example 24, wherein: the first data channel corresponds to an enhanced Mobile

Broadband (eMBB) service; and the second data channel corresponds to an ultra-reliable and low latency communications (URLLC) service, wherein the eMBB service and the URLLC service are multiplexed on a same component carrier.

[00127] Example 26 includes the at least one machine readable storage medium of any of Examples 24 to 25, wherein the first data channel is a first physical downlink shared channel (PDSCH) and the second data channel is a second PDSCH.

[00128] Example 27 includes the at least one machine readable storage medium of any of Examples 24 to 26, wherein: the first type of SSRAU and the second type of SSRAU include different resource blocks in a frequency domain and different symbols in a time domain; and the first type of SSRAU and the second type of SSRAU include a same number of resource elements (REs).

[00129] Example 28 includes a user equipment (UE) operable to perform data communication with a base station, the UE comprising: means for decoding, at the UE, a first downlink control information (DCI) format received from the base station, wherein the first DCI format identifies a first type of service-specific resource allocation unit (SSRAU) used for resource allocation in a first data channel transmitted over a first transmission time interval (TTI); means for decoding, at the UE, a second DCI format received from the base station, wherein the second DCI format identifies a second type of SSRAU used for resource allocation in a second data channel transmitted over a second TTI having a period that is within a period of the first TTI; means for identifying, at the UE, resources allocated by the second DCI format that preempt resources allocated by the first DCI format that are in a same time-frequency resource; and means for performing, at the UE, a data communication with the base station using the resources allocated by the first DCI format that are not preempted by the resources allocated by the second DCI format.

[00130] Example 29 includes the UE of Example 28, wherein: the first data channel corresponds to an enhanced Mobile Broadband (eMBB) service; and the second data channel corresponds to an ultra-reliable and low latency communications (URLLC) service, wherein the eMBB service and the URLLC service are multiplexed on a same component carrier.

[00131] Example 30 includes the UE of any of Examples 28 to 29, wherein the first data channel is a first physical downlink shared channel (PDSCH) and the second data channel is a second PDSCH.

[00132] Example 31 includes the UE of any of Examples 28 to 30, wherein: the first type of SSRAU and the second type of SSRAU include different resource blocks in a frequency domain and different symbols in a time domain; and the first type of SSRAU and the second type of SSRAU include a same number of resource elements (REs).

[00133] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). In one example, selected components of the transceiver module can be located in a cloud radio access network (C-RAN). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

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

[00135] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00136] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00137] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

[00138] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[00139] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00140] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

[00141] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology.