WO2018032001A1

WO2018032001A1 - Techniques for multiplexing different new radio communication service types

Info

Publication number: WO2018032001A1
Application number: PCT/US2017/046781
Authority: WO
Inventors: Ajit Nimbalker; Ralf Bendlin; Sergey PANTELEEV; Alexey Khoryaev; Alexei Davydov; Joonyoung Cho; Honglei Miao; Ingolf Karls; Markus Dominik Mueck
Original assignee: Intel Corporation
Priority date: 2016-08-12
Filing date: 2017-08-14
Publication date: 2018-02-15

Abstract

Techniques for multiplexing different New Radio (NR) service types can include providing assistance information to devices for handling the impact on communications of one traffic type by another traffic type. Control and or data multiplexing techniques can also be provided to minimize the impact of one traffic type on another. Reference signals can also be provided that enhance interference and or puncture handling. A frame structure design can also be provided to enhance multiplexing of different data types.

Description

TECHNIQUES FOR MULTIPLEXING DIFFERENT NEW RADIO

COMMUNICATION SERVICE TYPES

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 (3GPP) network. The next generation of wireless communications includes a diverse set of usage scenarios and applications. For example, 3GPP New Radio Access Technologies will likely support multiple service types, such as Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communications (mMTC), and Ultra-Reliable Low-Latency Communications (URLLC), among others. However, different service types can cause interference therebetween. Accordingly, there is a continuing need for addition multiplexing techniques to reduce the effects of interference between different service types.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] 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:

FIG. 1 illustrates a wireless system, in accordance with an example;

FIG. 2 illustrates a narrowband partition in the frequency domain allocated to various service types, in accordance with an example;

FIG. 3 illustrates a URLLC frame structure with TTI shortening and the same subcarrier spacing for a paired spectrum, in accordance with an example;

FIG. 4 illustrates eMBB and URLLC multiplexing causality in eMBB UL subframes, in accordance with an example;

FIG. 5 illustrates eMBB and URLLC multiplexing causality in eMBB DL subsystems, in accordance with an example;

FIG. 6 illustrates a URLLC frame structure with TTI shortening and the same subcarrier spacing for unpaired spectrum, in accordance with an example; FIG. 7 illustrates TTI shortening by decreasing the OFDM symbol duration, in accordance with an example;

FIG. 8 illustrates TTI shortening by decreasing the OFDM symbol duration, in accordance with an example;

FIG. 9 illustrates a system operable to mitigate an impact of multiplexing of signals, in accordance with an example;

FIGS. 10A-10F illustrate multiplexing of URLLC subframe in an eMBB DL subframe, in accordance with an example;

FIGS. 1 lA-1 IE illustrate multiplexing of URLLC subframe in an eMBB UL subframe, in accordance with an example;

FIG. 12 illustrates multiple URLLC users scheduled within a first control channel of one eMBB TTI that includes at least a portion of the control information, in accordance with an example;

FIG. 13 illustrates a reference signal structure for URLLC interference handling, in accordance with an example;

FIG. 14 illustrates a technique to mitigate an impact of multiplexing of signals, in accordance with an example;

FIG. 15 illustrates 15 kHz and 14 symbols frame structures for eMBB, and 60 kHz and 7 symbol frame structures for URLLC, in accordance with an example;

FIG. 16 illustrates 15 kHz and 14 symbol frame structures for eMBB, and 60 kHz and 8 symbol frame structures for URLLC, in accordance with an example;

FIG. 17 illustrates a technique to mitigate an impact of multiplexing of signals, in accordance with an example;

FIG. 18 illustrates another technique to mitigate an impact of multiplexing of signals, in accordance with an example;

FIG. 19 illustrates another technique to mitigate an impact of multiplexing of signals, in accordance with an example;

FIG. 20 illustrates another technique to mitigate an impact of multiplexing of signals, in accordance with an example;

FIG. 21 illustrates another technique to mitigate an impact of multiplexing of signals, in accordance with an example;

FIG. 22 illustrates another technique to mitigate an impact of multiplexing of signals, in accordance with an example; FIG. 23 illustrates preemption of some eMBB symbols by URLLC traffic, in accordance with an example;

FIG. 24 illustrates preemption of some eMBB symbols by URLLC traffic, in accordance with an example;

FIG. 25 illustrates preemption of some eMBB symbols by URLLC traffic, in accordance with an example;

FIG. 26 illustrates an architecture of a wireless network with various components of the network in accordance with some embodiments;

FIG. 27 illustrates example components of a device in accordance with some

embodiments; and

FIG. 28 illustrates example interfaces of baseband circuitry in accordance with some embodiments.

[0003] 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

[0004] 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

[0005] 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."

[0006] As used herein, the term "wireless access point" or "Wireless Local Area Network Access Point (WLAN-AP)" refers to a device or configured node on a network that allows wireless capable devices and wired networks to connect through a wireless standard, including WiFi, Bluetooth, or other wireless communication protocol.

[0007] 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.

[0008] 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 (3 GPP), and will be referred to herein simply as "New Radio (NR)."

EXAMPLE EMBODIMENTS

[0009] 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.

[0010] FIG. 1 illustrates a wireless system, in accordance with an example. In one aspect, the wireless system 100 includes one or more Base Stations (BS) 110 and one or more User Equipment (UE) devices 120 that can be communicatively coupled by a wireless communication protocol. In one instance, the one or more BSs may be Long

Term Evolved (LTE) evolved NodeBs (eNB) that can be communicatively coupled to one or more UEs by a Third-Generation Partnership Project (3GPP) Long Term Evolved (LTE) network. In one instance, the UE can be one or more of a smart phone, a tablet computing device, a laptop computer, an internet of things (IOT) device, and/or another type of computing devices that is configured to provide digital communications. As used herein, digital communications can include data and/or voice communications, as well as control information.

[0011] Further described herein are methods and systems to achieve efficient coexistence of multiple use cases for New Radio (NR) interface. The use cases can include by way of example, but without limitation, Ultra-Reliable Low-Latency

Communications (URLLC) traffic, and Enhanced Mobile Broadband (eMBB) traffic, Massive Machine Type Communication (mMTC) and the like. In one aspect, assistance information can be provided so that the devices can handle the impact on communications of one traffic type by another traffic type. Control and or data multiplexing techniques can also be provided to minimize the impact of one traffic type on another. Reference signals can also be provided that enhance interference and or puncture handling. A frame structure design can also be provided to enhance multiplexing of different data types.

[0012] In one aspect, URLLC and eMBB communication have different requirements, such as latency and reliability, that can translate into different physical layer attributes, such as Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) and Negative Acknowledgement (NACK) timing, HARQ Roundtrip Times (RTT), and Transmission Time Intervals (TTI).

[0013] In one aspect, URRLC traffic can be prioritized over eMBB traffic in some situations. In such situations, methods to mitigate the impact of URLLC multiplexing with eMBB traffic can improve system performance.

[0014] In one aspect, eMBB traffic can be characterized by low-latency data transmission, which could imply a Time Division Multiplexing (TDM) control channel and first frequency mapping of downlink data Resource Elements (RE). The TDM control channel and first frequency mapping can facilitate efficient pipelining and faster decoding times.

[0015] In one aspect, Key Performance Indicators (KPI) for URLLC include user plane latency and reliability. For URLLC the target for user plane latency can be 0.5 milliseconds (ms) for Uplink (UL) and 0.5 ms for Downlink (DL). The above user plane latency values may be considered an average value and does not have an associated high reliability requirement. eMBB traffic may also benefit from low-latency transmission. A Time Division Multiplex (TDM) control channel and frequency first mapping of downlink data resource elements can facilitate efficient pipelining and fast decode times. For eMBB the target for user plane latency can be 4 ms for both UL and DL.

[0016] In one aspect, reliability can be evaluated by probability of successfully transmitting X bytes within 1 ms, which is the time it takes to deliver a small data packet from a radio protocol layer 2/3 Service Data Unit (SDU) ingress point to a radio protocol layer 2/3 SDU egress point of a radio interface, at a predetermined channel quality (e.g., coverage edge). The target for reliability can be lxl 0^"5 within 1 ms. In one example, the URLLC reliability requirement for one transmission of a packet can be lxl 0^"5 for 20 bytes with a user plane latency of 1 ms.

[0017] In one aspect, when URLLC traffic arrives at the radio protocol layer

2/3 SDU ingress point at a BS or UE, the UE Physical (PHY) layer may be DL and UL synchronized (i.e., the UE has a valid timing advance), DL synchronized but not the UL (i.e., the UE does not have a valid timing advance), or neither the DL nor the UL are synchronized (i.e., the UE may be in a Radio Resource Control (RRC) idle (RRC IDLE) mode between paging occasions). In the case of the UE being in a RRC IDLE mode, the BS can first page the UE when URLLC traffic arrives at its radio protocol layer 2/3 SDU ingress point, whereas the UE can autonomously initiate a random-access procedure when URLLC traffic arrives at its radio protocol layer 2/3 SDU ingress point.

[0018] In one aspect, different usage scenarios can be multiplexed into the same carrier by various means. For example, a narrowband partition in the frequency domain can be allocated to URLLC, mMTC and MBB as illustrated in FIG. 2. For example, slices of time are divided into Transmission Time Intervals (TTI) to transmit data packets for different service types 210. Regular TTI partitions 220 can be used to transmit services types such as eMBB. Long TTI partitions 230 can be used to transmit service types that have small data requirements but may have poor transmission channel that requires a large number of repetitions, such as Massive Machine Type

Communication (mMTC). Short TTI 240 partitions can be used to transmit service types that have data that may arrive at any time and needs low transmission latency, such as URLLC. Time domain multiplexing is equally possible. Different service types 210 can use different numerologies. Notwithstanding, the same usage scenario can also use different numerologies. For instance, the 3.75 kilo Hertz (kHz) and 15 kHz subcarrier spacing can be TDM and Frequency -Division Multiplexed (FDM), so far as they do not occupy overlapping resources. For example, for the serving cell on which (EPDCCH) is monitored, a UE need not monitor the EPDCCH in a subframe which is configured by higher layers to be part of a positioning reference signal occasion if the positioning reference signal occasion is configured within Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) subframes and the Cyclic Prefix (CP) length used in subframe #0 is the normal cyclic prefix.

[0019] In one aspect, a semi-static separation of resources for URLLC traffic may not be feasible or efficient due to stringent latency and reliability specifications. For example, a separate partition in the frequency domain could be reserved for URLLC that coexist with other frequency partitions, such as for eMBB or mMTC, within the same NR carrier. However, if URLLC traffic is sporadic, the semi-statically reserved frequency resources can remain unused most of the time. More importantly, in order to fulfil possible URLLC reliability requirements, wideband transmission of URLLC data may be desired to reap the benefits of frequency diversity.

[0020] In one aspect, mMTC transmission are inherently narrow band in nature due to the coverage and low-cost requirements for mMTC devices. The mMTC transmissions, at least in medium to extreme coverage conditions, also utilize hundreds if not thousands of repetitions. Thus, by design, mMTC transmissions occupy considerable time resources. URLLC transmission, on the other hand, can typically be wideband in nature but last a few microseconds to fulfill reliability and latency constraints for mission critical services.

[0021] In one aspect, URLLC resources can alternatively be semi-statically reserved in the time domain, for example to facilitate the aforementioned wideband transmissions. There can be two ways to achieve low latency communications in coexistence with eMBB. URLLC and eMBB may have different TTI lengths but the same subcarrier spacing. For example, 15 kHz subcarrier spacing with 14 Orthogonal Frequency Division Multiplex (OFDM) symbols per TTI for eMBB and 15 kHz subcarrier spacing with 2 OFDM symbols per TTI for URLLC. Alternatively, URLLC and eMBB may use different subcarrier spacing. For example, 15 kHz subcarrier spacing in 1 ms TTI for eMBB and 60 kHz subcarrier spacing with 0.25 ms TT for URLLC.

[0022] In one aspect, in the case of paired spectrum wherein duplex constraints do not apply, TTI shortening with the same subcarrier spacing can be used to meet URLLC performance. TTI shortening can be used even if 15 kHz subcarrier spacing is assumed. An example is illustrated in FIG. 3, wherein minimum scheduling and HARQ ACK and NACK can be assumed, but without additional switching gaps.

[0023] FIG. 3 illustrates a URLLC frame structure with TTI shortening and the same subcarrier spacing for a paired spectrum. In the DL, a control frame 305 can schedule data for the DL 310 and optionally on the UL 315. In one instance, transmission, feedback and retransmission can be take less than 1 ms, with lxlO^"5 transmission errors.

[0024] In one aspect, URLLC traffic arrives randomly at the Media Access Control (MAC) buffer and hence does not follow a schedule. Hence, when URLLC traffic arrives at the MAC buffer during a long eMBB TTI (e.g., 1ms), time-division multiplexing of the two cannot fulfil the URLLC requirements as depicted in FIGS. 4 and 5.

[0025] FIG. 4 illustrates the eMBB and URLLC multiplexing causality issue in eMBB UL subframes. In one aspect, an eMBB DL subframe in an exemplary TDD system can have 1ms subframes lengths. Once the BS has prepared the Downlink Control Information (DCI) to designate a subframe as DL it cannot change the duplex direction 410 for 1 ms. The BS cannot change the duplex direction until the first symbol of the subsequent subframe 420. If URLLC traffic arrives at the MAC buffer of the BS during a eMBB UL subframe, he BS can cease receiving eMBB transmissions and start transmitting URLLC data. However, the URLLC UE may experience excessive interference from eMBB UL UEs when decoding the URLLC DL data.

[0026] FIG. 5 illustrates the eMBB/URLLC multiplexing causality issue in MBB DL subsystems. If URLLC traffic 510 arrives at the UE Media Access Control (MAC) buffer during the eMBB DL subframe 520, the BS cannot receive URLLC UL transmission due to the full duplex constraints, as illustrated in FIG. 5. Consequently, in order to fulfill the URLLC requirement in TDD systems, frequent UL and DL resources for URLLC need to be allocated in the time domain, which may severely impact eMBB performance. The situation can be no different from Time Division Long Term Evolved (TD-LTE) where the HARQ Round Trip Time (RTT) in UL and DL also depends on the TDD UL/DL configuration such that switching of the duplex direction is defined on a symbol level rather than a subframe level as a consequence of the latency requirements, as illustrated in FIG. 6. The frame structure can include a switching guard 610 before each uplink control 620 and downlink control 630. In FIG.6, a URLLC frame structure with TTI shortening and the same subcarrier spacing for unpaired spectrum is depicted. In case of an unpaired spectrum, TTI shortening with the same subcarrier spacing can be used to meet ULLC requirements even with 15 kHz subcarrier spacing. However, additional switching guards need to be configured to allow the duplexer in the transceiver circuitry to switch from transmitting to receiving and vice versa. This leaves less and less resources for semi-static multiplexing of URLLC and eMBB in a time-division manner.

[0027] In one aspect, it has been assumed 15 kHz subcarrier spacing for URLLC and eMBB and resulting subframe length of 1 ms in the above description of a number of examples. As illustrated in FIG. 7, the subcarrier spacing puts a fundamental limit on the achievable latency and further shortening of the TTI may only be achieved by increasing the subcarrier spacing. As depicted in FIG.7 TTI shortening can be achieved by decreasing the OFDM symbol duration 710, 720. So far it has been assumed, the eMBB and URLLC transmissions are characterized by identical subcarrier spacing, and the focus has been on the potentially different switching times between UL and DL for eMBB and URLLC in TDD systems, where for example, switching the duplexing direction once every subframe, for example 1 ms for 15 kHz subcarrier spacing, may not be sufficient for URLLC.

[0028] In one aspect, for multiplexing URLLC and eMBB traffic using the same carrier spacing in FDD systems, the URLC and eMBB channels can be multiplexed on a resource element (RE) level within one OFDM symbol, as they share the same numerology. A search space can be defined that incorporates opportunities to schedule URLLC transmission throughout a subframe, as illustrated in FIG. 3.

[0029] Using MBMS as an example, the BS MAC scheduler can dynamically allocate resources for MBMS to different service types, namely MBB, in MBFSN subframes without PMCH transmissions. The presence of PMCH transmissions is, however, a priori known to the BS MAC scheduler via the schedule broadcasted on the MCCH. Hence, if subframe n is a MBSFN subframe not used for PMCH transmission, the BS MAC scheduler can instruct the BS Physical (PSY) layer in subframe n-k to prepare a PDSCH transmission in subframe n using TM9 or TM10, where k is the processing delay to encode the MAC PDU for transmission on a PDSCH. In addition, each resource reserved for MBMS contains a non MBSFN region which can be used to schedule the MBB transmission in TM9 or TM10 in the MBSFN region of the resources reserved for MBMS. In such case, different service types (e.g., MBMS and MBB) use the same TTI duration, namely, on subframe.

[0030] In one aspect, where the TTI duration for URLLC is considered shorter than for eMBB, the BS can schedule a URLLC transmission during an on-going eMBB transmission as illustrated in FIG. 3. If eMBB and URLLC use different subcarrier spacings, the numerology can be dynamically switched within one subframe. While changing the numerology allows for further shortening of the TTI duration, it is not clear if this is needed to fulfill the URLLC requirements. Moreover, increasing the subcarrier spacing for just one usage scenario does not alleviate the problems arising from the full duplex constraints in TDD systems. However, increasing the subcarrier spacing may minimize the switching guards as illustrated in FIG. 8. As depicted in FIG. 8, the subcarrier spacing can be increased to decrease switching guards 810.

[0031] In one aspect, eMBB traffic can operate with larger, identical subcarrier spacing for use with larger subcarrier spacing for URLLC traffic. This can alleviate latency and duplexing constraints, as URLLC and eMBB operation can be the same from a structural perspective, albeit with potentially different channel design to achieve the URLLC reliability requirements.

[0032] In one aspect, when URLLC and eMBB transmissions do not occupy orthogonal resource, the URLLC and eMBB transmissions can create interference with each other. In one scenario, if URLLC traffic is prioritized over eMBB traffic and the BS receives a URLLC packet for transmission in the middle of an ongoing eMBB transmission, the BS can choose to puncture the eMBB transmission to transmit the URLLC packet. In another scenario, a serving cells' eMBB traffic may experience interference from a neighboring BS that may be performing a URLLC transmission, which can be termed as "bursty interference." Such situations can also occur in cases where eMBB traffic can be served with different TTI durations.

[0033] FIG. 9 depicts a system operable to mitigate an impact of multiplexing of signals. In one aspect, the UE can decode assistance information associated with an interference signal 910. The interference signal can be one or a plurality of signals multiplexed in a same time-frequency resource region. The assistance information can include at least one of a time-frequency resource region information and/or a physical transmission format information. For example, the assistance information can indicate time-frequency regions with different numerologies or the same numerologies. The assistance information can be dynamic, semi-static, or a combination thereof. For example, an eMBB user can be configured with resources that could be used to identify if its allocated resources are punctured by other traffic. For instance, a first control channel at the beginning of a Transmission Time Interval (TTI) can indicate the resource allocation (e.g., MCS, etc.) for the eMBB traffic, and a second control channel within or at the end of the allocated resources can indicate the punctured resources. The assistance information can be signaled in the physical layer transmission format of the interference signal (e.g., modulation, Demodulation Reference Signal (DMRS) structure, numerology) on overlapped resources.

[0034] In one instance, the overlapping signals may include intra cell signals. For example, when Ultra Reliable Low Latency Communication (URLLC) signals and Mobile Broadband (MBB) do not occupy orthogonal resources, URLLC and MBB transmissions can create interference with each other. In one scenario, if URLLC traffic is prioritized over eMBB traffic and if the Base Station (BS) receives a URLLC packet to transmit in the middle of an ongoing eMBB transmission, the BS may choose to puncture the eMBB transmission to transmit the URLLC packet. In another scenario, the eMBB traffic for a serving cell of a given BS may experience interference from a neighboring BS that may be performing an URLLC transmission, which can be termed a burst interference from URLLC to eMBB traffic. Such scenarios can also occur for cases where eMBB traffic can be served with different TTI durations. Accordingly, the assistance information can be applicable to both intra-cell interference and inter-cell interference.

[0035] In one aspect, the UE can decode at least one of the plurality of signals multiplexed in the same time-frequency resource region 920. The plurality of signals can include a selected signal and the interference signal. The plurality of selected signals can be decoded based on the decoded assistance information to extract a selected signal.

[0036] If the interference signal uses another numerology, then an Interference

Rejection Combining (IRC) receiver may be the used. However, if the level 1 (LI) structure is the same, a Network Assisted Interference Cancelation and Suppression (NAICS) type of received may be utilized.

[0037] Indication of the URRL numerology can be provided by the scheduling DCI transmitted with the eMBB numerology. This can be as illustrated for the DL and the UL in FIGS. 10A-10F and 11A-11E respectively. FIGS. 10A-10F depict

multiplexing of URLLC subframe in an eMBB DL subframe. FIGS. 1 lA-1 IE depict multiplexing of an URLLC subframe in an eMBB UL subframe.

[0038] FIGS. 10A and 11A illustrate a 15 kHz frame structure 1010 and a 60 kHz frame structure 1020. Generally, the receiver at the BS in the UL or at the UE for downlink should not be required to blindly detect the numerology of a transmission, especially, if several transmissions (e.g., eMBB and URLLC) may occur simultaneously with different numerologies. Hence, at any given time, the BS and UE receiver circuitry can know about the numerology with which to receive a potential transmission. In FIG 10B, the URLLC UE is not interested in eMBB traffic and the UE PHY can be configured to receive a particular numerology, e.g., 60kHz subcarrier spacing. For the other cases depicted in FIGS. 10C-10F and 1 lB-1 IE, the URLLC UE is also interested in receiving eMBB traffic. In FIGS. 10 C and 1 IB, the URLLC can have a 60 kHz Physical Downlink Control Channel (PDCCH) with 60 kHz symbol alignment. In FIGS. 10D and l lC, the URLLC can have 60 kHz PDCCH with 15 kHz symbol alignment. In FIGS. 10E and 1 ID, the URLLC has no 60 kHz PDCCH, but 60 kHz symbol alignment. In

FIGS. 10F and HE, the URLLC has not 60 kHz PDCCH, but 15 kHz symbol alignment.

[0039] Since the UE receiver can receive (or monitor for) a transmission in one numerology, both eMBB transmission and at least URLLC control channel transmissions are received with the same numerology, e.g., 15kHz subcarrier spacing. The URLLC control channel can then indicate that the corresponding URLLC data transmission will be transmitted in a different numerology, e.g., 60kHz subcarrier spacing. In FIGS. IOC and 1 IB, a gap is defined 1030 between the URLLC control channel (using a first numerology) and the URLLC data channel (using a second numerology) in order to align the data channel transmission according to some predefined rule. For example, the gap can be such that the URLLC data transmission in FIG. IOC is aligned with that of the case in FIG. 10A (i.e., the symbol boundaries of the URLLC numerology coincide).

Alternatively, no such gap is defined 1040 and the URLLC data transmission starts at the end of the URLLC control channel transmission as depicted in the case depicted in FIGS. 10D and 11C. In cases depicted in FIGS. IOC and 10D, the URLLC transmission using a second numerology may have a separate control channel whereas in the cases illustrated in FIGS. 10E and 10F no second control channel in a second numerology exists. The same principle can be applied to the UL when the UE already has a valid UL grant for the MBB traffic. For example, the UE has been scheduled for an UL transmission in subframe n using a first numerology, e.g., 15kHz subcarrier spacing. The resulting subframe/TTI duration can be 1ms. During the transmission, URLLC traffic arrives at said UE's MAC buffer. The UE thus transmits an indication using the first numerology to inform the BS that it will switch numerologies to a second numerology for

transmission of the URLLC UL traffic. The indication informs the UE about the pending URLLC transmission and that the BS receiver has to switch the numerology after the indication has been received. Similar to the DL, a search space can be defined in which the BS monitors for indications from URLLC UEs with MBB UL grant.

[0040] Mixed numerologies can be challenging from an interference perspective. The receiver may not be able to apply Reduced Complexity Maximum Likelihood (RML) like receivers if the waveform is not known. The IRC receiver may also be challenging to apply due to channel estimation. In such case, the UE may be limited to estimate the covariance matrix. Therefore, from an interference perspective, it can be better to mix eMBB and URLLC under the same numerology. In other words, spectrum allocations with different numerologies should probably be aligned across network or same assistance signaling to indicate whether they are aligned.

[0041] In one aspect, a BS can encode a desired signal for transmission to a UE. For example, the BS can encode an eMBB packet for transmission to the UE. In one aspect, Code Blocks (CB) of the eMBB transmission can be reordered by the BS prior to mapping on the physical channel resources. Reordering CBs can advantageously randomize the impact of bursty interference. In comparison, a single Transport Block (TB) can contain one or more blocks processed and transmitted in the same order in conventional LTE communication systems. Reordering the CB in one TTI generally will not introduce extra processing delay, as compared to more general interleaving approached within a TTI, whether the receiver waits until all symbols of the CB are received or does not wait. [0042] In one aspect, acquire assistance information can include an enhanced multi-part control. A first control channel of an enhanced multi-part control can be similar to a conventional control channel scheduling downlink data for an eMBB user (e.g., containing a resource allocation, Modulation and Coding Scheme (MCS)). A second control channel that modifies or enhances the first control channel can be sent if the BS multiplexes one traffic type, such as URLLC, within the allocated resources of a second type, such as eMBB. The second control channel can be as simple as a single cell-wide indicator of the presence of URLLC traffic, similar to a Physical Control Format Indicator Channel (PCFICH), or it can be the control channel used to schedule the URLLC user. In one instance, for example, the eMBB user can be configured with additional blind decodes to be used to detect and handle URLLC traffic. A cell-wide indicator of URLLC traffic presence can further be used to also indicate the TDD UL/DL configuration of the current subframe. The enhanced multi-part control could allow faster URLLC access in the UL, as otherwise unscheduled UEs cannot make use of the flexible data region. The functionality may also be utilized for unlicensed operation, such as on WiFi communication bands. An example of codewords, before encoding, for transmission on an indicator channel is illustrated in Table 1.

Table 1

Additional TDD UL/DL configuration could be indicated using more bits, such as when multiple guards and UL resources are reserved in a subframe. In addition, extension to multiple URLLC users within one eMBB TTI is illustrated in FIG. 12. As depicted in FIG. 12, multiple URLLC users can be scheduled within a first control channel 1210 of one eMBB TTI that includes at least a portion of the control information. More additional control information can be included at the end of respective URLLC transmissions 1220, 1230. For example, some of the additional control information can be transmitted after the data transmission of each respective URLLC. For instance, a special control channel following the data transmission can include information on the URLLC puncture. In another instance, conventional control information can carry HARQ retransmission information and also indicate the URLLC puncture information of the previous transmission.

[0043] FIG. 13 illustrates a reference signal structure for URLLC interference handling. In one aspect, a horizontal Demodulation Reference Signal (DM-RS) 1310 can be used for eMBB transmissions to allow interference covariance matrix estimation of Orthogonal Frequency Division Multiplexing (OFDM), for inter-cell interference handling of URLLC on eMBB transmission. Given that a URLLC transmission most likely will be wideband, such DM-RSs can be made relative sparse in the frequency domain, and transmitted in a Transport Protocol (TP) specific manner regardless of the UE allocations. One antenna port transmission, or even zero power, may be sufficient. Moreover, the horizontal DM-RS structure can be beneficial for URLLC reception processing because it may avoid time domain interpolation of channel estimations, thus providing early pre-symbol decoding capability that is crucial to satisfy the stringent latency requirements.

[0044] FIG. 14 depicts a technique to mitigate an impact of multiplexing of signals. In one aspect, a first time-frequency resource region can be determined for transmission 1410. In one aspect, a data packet of a first traffic type can be encoded into a first coded stream 1420. In one aspect, the coded steam can be mapped into a first set of RE. The first set of REs can be a subset of the first time-frequency resource region.

[0045] In one aspect, a DM-RS associated with associated with the first traffic can be modulated into a second set of REs 1430. The second set of REs can be a subset of the first time-frequency resource region. The second set of REs can be associated with one or more antenna ports. In one aspect, an interference reference signal associated with a second traffic can be multiplexed into a third set of REs 1440. In one aspect, the third set of REs can be a subset of the first time-frequency resource region. The time-san of the third set of REs can be greater than a span of the second set of REs. The third set of REs can be associated with a single antenna port or with zero transmission power. The third set of REs can be used for interference handling via interference covariance estimation per OFDM symbol.

[0046] In one aspect, the first, second and third set of REs can be encoded for transmission on the first time-frequency resource 1450. In one aspect, information regarding the first time-frequency resource region, the first reference signa, and the second reference signal can be encoded for transmission on a control channel 1460.

[0047] In one example, the first traffic type can be eMBB transmissions and the second traffic can be URLLC transmissions. In one instance, the eMBB traffic and URLLC traffic can have different TTI and the same subcarrier spacing. In another instance, the eMBB traffic and URLLC traffic can have different subcarrier spacing. In yet another instance, the eMBB traffic and URLLC traffic do not occupy orthogonal resources.

[0048] In one aspect, erased information of punctured data can be recovered.

In one example, a HARQ, an erasure correcting code, or the like can be used to recover erased eMBB information from punctured data. For URLLC, a Single Carrier (SC) waveform, without CP, that may not be aligned to OFDM symbol boundaries can be supported to provide an early start to the transmission.

[0049] In one aspect, for the case of scheduled or grant-less uplink URLLC transmission, in order to meet a target user plane latency of 0.5 ms, the resources for UL transmission can be allocated in 0.125 ms increments. The resources for UL transmission can be either scheduling request (SR) and then data for scheduled UL, or data for grant- less UL. Reservation of these URLLC resources to serve sporadic URLLC transmissions may be inefficient in terms of system capacity. For example, in FIGS. 15 andl6, the case of eMBB and URLLC multiplexing is shown. FIG. 15 illustrates 15 kHz and 14 symbols frame structures for eMBB, and 60 kHz and 7 symbol frame structures for URLLC. FIG. 16 illustrates 15 kHz and 14 symbol frame structures for eMBB, and 60 kHz and 8 symbol frame structures for URLLC. As depicted in FIG. 15, if UL URLLC resources are reserved semi-statically, then two full symbols may be used in eMBB DL shared channels (e.g., 5^th and 7^th). As depicted in FIG. 16, for 8 symbols frame structures for URLLC, half of the symbols may be used for eMBB. However, the duration between URLLC TTI is increased to approximately 0.1429 ms.

[0050] In one aspect, it can be desirable to be able to dynamically use the reserved URLLC resources for eMBB transmission. FIG. 17 depicts a technique to mitigate an impact of multiplexing of signals. The technique can be used when dynamically using the URLLC resources for eMBB transmission. In one aspect, a BS can detect an UL URLLC transmission at a start of an URLLC TTI 1710. The UL URLLC resources can be allocated within one or more DL eMBB resources. In one aspect, the DL eMBB symbol start can be aligned with a URLLC TTI.

[0051] In one aspect, the BS can encode for transmission a DL eMBB transmission 1720. In one aspect, the BS can decode the detected UL URLLC transmission 1730. In one aspect, a part of the DL eMBB transmission can be dropped or punctured to receive the UR URLLC transmission when detected. The DL eMBB transmission can be dropped or punctured to avoid full duplex operation or mitigate half- duplex collision. In one example, the UL URLLC and DL eMBB transmission can both be TDD.

[0052] In one example, when the BS detects the UL URLLC transmission it can either drop or puncture a part of the DL eMBB transmission. If a UL URLLC transmission is not detected, the BS may decide to transmit the DL eMBB transmission.

[0053] A mapping of the DL eMBB resources can be adapted to utilize a part of an eMBB symbol duration to receive the UL URLLC transmission. For example, an interlace or interleave mapping of resource element into affected symbols may provide shorter symbol duration allowing utilization of a half of the symbol for sensing and another half for DL eMBB data transmission. Effectively, this may be seen as a dynamic change of eMBB numerology at affected symbols. The UL URLLC signal may start from a preamble sequence that is used to detect the UL URLLC presence.

[0054] In one aspect, the UL URLLC resources are allocated within the eMBB resources if the UL URLLC traffic is sporadic. The technique advantageously provides a mechanism to vacate DL eMBB resources for UL URLLC transmission.

[0055] FIG. 18 depicts another technique to mitigate an impact of multiplexing of signals. In one aspect, a Base Station (BS) can determine a scheduled UL eMBB transmission 1810. In one aspect, the BS can encode an eMBB DCI for transmission 1820. The DCI can include an indication cancelling an UL eMBB transmission, if an URLLC latency budget exceeds a DCI processing time, in order for a UE to be able to drop the scheduled UL eMBB transmission before a DL URLLC transmission. In one aspect, the BS can encode for transmission the DL URLLC transmission 1830.

[0056] In one example, the DL URLLC traffic may arrive when there is already scheduled UL eMBB and URLLC transmissions. The URLLC and eMBB transmission can be TDD. The BS may therefore not be able to discard planned UL transmission that have already been granted because the maximum latency budget to transmit DL URLLC may be lower than the typical eMBB processing latency.

[0057] FIG. 19 depicts another technique to mitigate an impact of multiplexing of signals. In one aspect, a User Equipment can perform a clear channel assessment (CCA) or Listen-Before-Talk (LBT) at a start of an URLLC TTI to detect a DL URLLC transmission 1910.

[0058] In one aspect, the UE can encode an UL eMBB transmission when an ongoing DL URLLC transmission is not detected by the CCA or LBT 1920. The timing of transmitting the UL eMBB transmission can be modified to start after the DL URLLC transmission plus a propagation delay of the DL URLLC transmission. The URLLC transmission and eMBB transmission can be TDD.

[0059] In one aspect, when the UE, having an UL eMBB transmission, detects an ongoing DL URLLC transmission, then the UE can refuse the UL transmission on that resource 1930. The turn-around gaps for Receive-Transmit (RX-TX) and Transmit- Receive (TX-RX) switching should be allocated in this case. An energy detection based CCA or LBT may not be appropriate in this case because a UE may yield to another UL transmission in a neighboring call, which may not be efficient.

[0060] In one aspect, the problem of transmission timing in this case should be taken into account. For example, DL transmission timing and UL transmission timing may not be aligned because of timing advance mechanisms. In one embodiment, the UL eMBB timing can be modified to start no earlier than the DL URLLC plus a

predetermined propagation delay. In one instance, the predetermined propagation delay can be a function of the DL reception timing.

[0061] FIG. 20 depicts another technique to mitigate an impact of multiplexing of signals. In one aspect, a BS can receive at least two signals multiplexed into a same time-frequency resource 2010. The at least two signals can include an UL eMBB transmission and an UL URLLC transmission multiplexed using a spreading scheme. In this case, it may appear as if the UL URLLC traffic arrives when there are already scheduled UL eMBB transmissions. [0062] In one aspect, the BS can decode the at least two signals to extract the eMBB and the URLLC transmission based on transmission parameters of the spreading scheme and UL grant resource allocation of the eMBB transmission and the URLLC transmission 2020. Decoding the eMBB and URLLC transmissions using the transmission parameters of the spreading scheme provides a mechanism that may be used for dynamic resource sharing between URLL and eMBB.

[0063] The BS may cancel the UL eMBB signal from UL URLLC transmission having knowledge of transmission parameters of both signals when both transmissions happen intra-cell. Accordingly, in one aspect, the BS can encode the UL grant resource allocations of the eMBB transmission and the URLLC transmission, and the spreading scheme configuration for transmission to a UE prior to receiving the at least two signals. In one aspect, the BS can acquire the UL grant resource allocation of the eMBB transmission and the URLLC transmission of a neighboring cell from by the UL eMBB transmission originated.

[0064] In the inter-cell case, the BS may need to know, by signaling or blind detection, the eMBB UL transmission parameters of the neighboring cells. According, in one aspect, the URLLC transmission and the eMBB transmission are TDD. In one aspect, the URLLC transmission and the eMBB transmission are FDD.

[0065] FIG. 21 depicts another technique to mitigate an impact of multiplexing of signals. In one aspect, a User Equipment can perform a CCA at a start of an URLLC TTI to detect an UL URLLC transmission on a shared resource before starting an UL eMBB transmission 2110. In this case, it may appear as if the UL URLLC traffic arrives when there are already scheduled UL eMBB transmissions.

[0066] In one aspect, the UE can encode the UL eMBB transmission on a current scheduled resource for transmission when an UL URLLC transmission preamble sequence is not detected by the CCA or LBT 2120. The UE can encode the UL eMBB for transmission on a next scheduled resource when the UL URLLC transmission preamble sequence is detected by the CCA or LBT. The turn-around gaps for Receive-Transmit (RX-TX), and Transmit-Receive (TX-RX) switching can be allocated in this case.

[0067] In one aspect, the URLLC transmission and the eMBB transmission are

TDD. In one aspect, the URLLC transmission and the eMBB transmission are FDD. [0068] FIG. 22 depicts another technique to mitigate an impact of multiplexing of signals. In one aspect, the BS can encode, for transmission to a first UE, an eMBB TB at a given (n) TTI 2210. The encoded TB can include an indication to send a Code Block (CB) or Code Block Group (CBG) level HARQ at a specified (n+k) TTI when one or more Resource Blocks (RB) are shared by an eMBB service and an URLLC. When the one or more RBs are not shared, the UE can be dynamically configured send a TB level HARQ at the specified (n+k) TTI.

[0069] In one aspect, the BS can encode, for transmission to a second UE, an URLLC CB or CBG using one or more punctured OFDM symbols during the given (n) TTI 2220.

[0070] In one aspect, the BS can predict when one or more CB or CBGs of the eMBB TB cannot be decoded due to the one or more punctured OFDM symbols because of the transmission of the CB or CBG of the URLLC during the given (n) TTI 2230. In one example, predicting when one or more CBs or CBGs can be decoded can include determining one or more indices of the one or more CBs or CBGs of the eMBB TB punctured by CB or CBGs of the URLLC. The BS then estimates whether the first UE can or cannot correctly decode the affected CBs or CBGs of the eMBB TB.

[0071] In one aspect, the BS can encode, for autonomous retransmission to the first UE, the one or more CBs or CBGs of the eMBB TB predicted to be not decodable due to the one or more punctured OFDM symbols because of the transmission of the CB or CBGs of the URLLC during the given (n) TTI 2240. According, the BS does not need to transmit dedicated new physical channel or new additional downlink control information for the preemption position in the previous scheduled (e.g., n+k TTI) TB. This reduces the UE complexity by not implementing, monitoring and/or receiving new physical channels to recover the potentially punctured one or more CBs or CBGs.

Moreover, the responds once to the punctured and retransmitted one or more CBs or CBGs. The also saves on power consumption by the UE, reduces latency and improves overall UL radio resource efficiency. Upon reception of autonomous retransmitted CBs or CBGs, the UE can discard the first transmission of the CBs or CBGs at the given (n) TTI, so that the preemption URLLC traffic will not cause disturbance of demodulation of the CBs or CBGs retransmitted by the UE.

[0072] In one aspect, the BS can determine at the specified (n+k) TTI whether to retransmit selected CBs or CBGs of the eMBB TB based on reception of a feedback from the first UE 2250.

[0073] FIGS. 23-25 illustrates several examples of preemption of some eMBB symbols by URLLC traffic. As depicted in FIG. 23, for example, the amount of Resource Elements (RE) scheduled for the eMBB UE that are punctured 2310 by URLLC traffic can be significant. However, in other situations, as depicted in FIGS. 24 and 25, the amount of punctured resource 2410, 2510 can be a relatively small portion of the scheduled eMBB REs.

[0074] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio

communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time- Division Duplex (UMTS -TDD), Time Division-Code Division Multiple Access (TD-

CDMA), Time Division-Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3 GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3 GPP Rel. 10 (3rd

Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3 GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3 GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3 GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17), 3GPP Rel. 18 (3rd Generation

Partnership Project Release 18), 3 GPP 5G, 3 GPP LTE Extra, LTE- Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution- Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for

Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy -phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. Had, IEEE 802.11 ay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.11 p and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems, and other similar radio communication technologies.

[0075] Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4- 3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT

(International Mobile Telecommunications) spectrum (including 450 - 470 MHz, 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, etc). Note that some bands are limited to specific region(s) and/or countries), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76- 81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0076] Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3 GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0077] FIG. 26 illustrates an architecture of a wireless network with various components of the network in accordance with some embodiments. A system 2600 is shown to include a UE 2601 and a UE 2602. The UEs 2601 and 2602 are illustrated as smartphones (i.e., 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. In some embodiments, any of the UEs 2601 and 2602 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 (machine initiated) exchanging data with an MTC server and/or device via a public land mobile network (PLMN), Proximity -Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. An IoT network describes interconnecting uniquely identifiable embedded computing devices (within the internet infrastructure) having short-lived connections, in addition to background applications (e.g., keep-alive messages, status updates, etc.) executed by the IoT UE.

[0078] The UEs 2601 and 2602 are configured to access a radio access network (RAN)— in this embodiment, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) 2610. The UEs 2601 and 2602 utilize connections 2603 and 2604, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 2603 and 2604 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, and the like.

[0079] In this embodiment, the UEs 2601 and 2602 may further directly exchange communication data via a ProSe interface 2605. The ProSe interface 2605 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 (PBSCH).

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

[0081] The E-UTRAN 2610 can include one or more access points that enable the connections 2603 and 2604. These access points can be referred to as access nodes, base stations (BSs), NodeBs, eNodeBs, gNodeBs, RAN nodes, RAN nodes, and so forth, and can comprise ground stations (i.e., terrestrial access points) or satellite access points providing coverage within a geographic area (i.e., a cell). The E-UTRAN 2610 may include one or more RAN nodes 2611 for providing macrocells and one or more RAN nodes 2612 for providing femtocells or picocells (i.e., cells having smaller coverage areas, smaller user capacity, and/or higher bandwidth compared to macrocells).

[0082] Any of the RAN nodes 2611 and 2612 can terminate the air interface protocol and can be the first point of contact for the UEs 2601 and 2602. In some embodiments, any of the RAN nodes 2611 and 2612 can fulfill various logical functions for the E-UTRAN 2610 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.

[0083] In accordance with some embodiments, the UEs 2601 and 2602 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 2611 and 2612 over a multicarrier communication channel in accordance various communication techniques, such as 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.

[0084] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 2611 and 2612 to the UEs 2601 and 2602, 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 represents the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0085] The physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to the UEs 2601 and 2602. The physical downlink control channel (PDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It also informs the UEs 2601 and 2602 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 2601 within a cell) is performed at any of the RAN nodes 2611 and 2612 based on channel quality information fed back from any of the UEs 2601 and 2602, and then the downlink resource assignment information is sent on the PDCCH used for (i.e., assigned to) each of the UEs 2601 and 2602.

[0086] The PDCCH uses control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex- valued symbols are first organized into quadruplets, which are then permuted using a sub- block inter-leaver for rate matching. Each PDCCH is transmitted using one or more of these CCEs, where each CCE corresponds to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols are 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).

[0087] The E-UTRAN 2610 is shown to be communicatively coupled to a core network— in this embodiment, an Evolved Packet Core (EPC) network 2620 via an SI interface 2613. In this embodiment, the SI interface 2613 is split into two parts: the Sl-U interface 2614, which carries traffic data between the RAN nodes 2611 and 2612 and the serving gateway (S-GW) 2622, and the Sl-MME interface 2615, which is a signaling interface between the RAN nodes 2611 and 2612 and the mobility management entities (MMEs) 2621.

[0088] In this embodiment, the EPC network 2620 comprises the MMEs 2621 , the S-GW 2622, the Packet Data Network (PDN) Gateway (P-GW) 2623, and a home subscriber server (HSS) 2624. The MMEs 2621 are similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 2621 manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 2624 comprises a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The EPC network 2620 may comprise one or several HSSs 2624, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 2624 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0089] The S-GW 2622 terminates the S 1 interface 2613 towards the E- UTRAN 2610, and routes data packets between the E-UTRAN 2610 and the EPC network 2620. In addition, the S-GW 2622 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.

[0090] The P-GW 2623 terminates an SGi interface toward a PDN. The P-GW 2623 routes data packets between the EPC network 2623 and extemal networks such as a network including the application server 2630 (alternatively referred to as application function (AF)) an Internet Protocol (IP) interface 2625. Generally, the application server 2630 is 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 2623 is shown to be communicatively coupled to an application server 2630 via an IP communications interface 2625. The application server 2630 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 2601 and 2602 via the EPC network 2620.

[0091] The P-GW 2623 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 2626 is the policy and charging control element of the EPC network 2620. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network

(HPLMN) associated with a User Equipment's (UE) 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 2626 may be communicatively coupled to the application server 2630 via the P-GW 2623. The application server 2630 may signal the PCRF 2626 to indicate a new service flow and selecting the appropriate Quality of Service (QoS) and charging parameters. The PCRF 2626 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.

[0092] FIG. 27 illustrates example components of a device in accordance with some embodiments. In some embodiments, the device 2700 may include application circuitry 2702, baseband circuitry 2704, Radio Frequency (RF) circuitry 2706, front-end module (FEM) circuitry 2708, and one or more antennas 2710, coupled together at least as shown. The components of the illustrated device 2700 may be included a UE or a RAN node. In some embodiments, the device 2700 may include less elements (e.g., a RAN node may not utilize application circuitry 2702, and instead include a

processor/controller to process IP data received from an EPC). In some embodiments, the device 2700 may include additional elements such as, for example, memory /storage, display, camera, sensor, and/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).

[0093] The application circuitry 2702 may include one or more application processors. For example, the application circuitry 2702 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 and/or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system. In some embodiments, processors of application circuitry 2702 may process IP data packets received from an EPC.

[0094] The baseband circuitry 2704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 2704 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 2706 and to generate baseband signals for a transmit signal path of the RF circuitry 2706. Baseband processing circuity 2704 may interface with the application circuitry 2702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 2706. For example, in some embodiments, the baseband circuitry 2704 may include a second generation (2G) baseband processor 2704a, third generation (3G) baseband processor 2704b, fourth generation (4G) baseband processor 2704c, and/or other baseband processor(s) 2704d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 2704 (e.g., one or more of baseband processors 2704a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 2706. In other embodiments, some or all of the functionality of baseband processors 2704a-d may be included in modules stored in the memory 2704g and executed via a Central Processing Unit (CPU) 2704e. 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 2704 may include Fast- Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 2704 may include convolution, tail-biting convolution, turbo, Viterbi, and/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.

[0095] In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 2704f. The audio DSP(s) 2704f 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 2704 and the application circuitry 2702 may be implemented together such as, for example, on a system on a chip (SOC).

[0096] In some embodiments, the baseband circuitry 2704 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 2704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/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 2704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

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

[0098] In some embodiments, the RF circuitry 2706 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 2706 may include mixer circuitry 2706a, amplifier circuitry 2706b and filter circuitry 2706c. The transmit signal path of the RF circuitry 2706 may include filter circuitry 2706c and mixer circuitry 2706a. RF circuitry 2706 may also include synthesizer circuitry 2706d for synthesizing a frequency for use by the mixer circuitry 2706a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 2706a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 2708 based on the synthesized frequency provided by synthesizer circuitry 2706d. The amplifier circuitry 2706b may be configured to amplify the down-converted signals and the filter circuitry 2706c 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 2704 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a necessity. In some embodiments, mixer circuitry 2706a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0099] In some embodiments, the mixer circuitry 2706a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 2706d to generate RF output signals for the FEM circuitry 2708. The baseband signals may be provided by the baseband circuitry 2704 and may be filtered by filter circuitry 2706c. The filter circuitry 2706c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[00100] In some embodiments, the mixer circuitry 2706a of the receive signal path and the mixer circuitry 2706a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 2706a of the receive signal path and the mixer circuitry 2706a 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 2706a of the receive signal path and the mixer circuitry 2706a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 2706a of the receive signal path and the mixer circuitry 2706a of the transmit signal path may be configured for superheterodyne operation. [00101] 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 2706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 2704 may include a digital baseband interface to communicate with the RF circuitry 2706.

[00102] 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.

[00103] In some embodiments, the synthesizer circuitry 2706d 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 2706d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

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

[00105] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity. Divider control input may be provided by either the baseband circuitry 2704 or the applications processor 2702 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 2702.

[00106] Synthesizer circuitry 2706d of the RF circuitry 2706 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.

[00107] In some embodiments, synthesizer circuitry 2706d 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 2706 may include an IQ/polar converter. [00108] FEM circuitry 2708 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 2710, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 2706 for further processing. FEM circuitry 2708 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 2706 for transmission by one or more of the one or more antennas 2710.

[00109] In some embodiments, the FEM circuitry 2708 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 a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 2706). The transmit signal path of the FEM circuitry 2708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 2706), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 2710.

[00110] In some embodiments, the device 2700 comprises a plurality of power saving mechanisms. If the device 2700 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 may power down for brief intervals of time and thus save power.

[00111] If there is no data traffic activity for an extended period of time, then the device 2700 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 2700 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 cannot receive data in this state, in order to receive data, it can transition back to

RRC Connected state.

[00112] 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.

[00113] Processors of the application circuitry 2702 and processors of the baseband circuitry 2704 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 2704, alone or in combination, may be used execute Layer 3, Layer 2, and/or Layer 1 functionality, while processors of the application circuitry 2704 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.

[00114] FIG. 28 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 2704 of FIG. 27 may comprise processors 2704A-2704E and a memory 2704G utilized by said processors. Each of the processors 2704A-2704E may include a memory interface, 2804A-2804E, respectively, to send/receive data to/from the memory 2704G. [00115] The baseband circuitry 2704 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 2812 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 2704), an application circuitry interface 2814 (e.g., an interface to send/receive data to/from the application circuitry 2702 of FIG. 27), an RF circuitry interface 2816 (e.g., an interface to send/receive data to/from RF circuitry 2706 of FIG. 27), and a wireless hardware connectivity interface 2818 (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).

EXAMPLES

[00116] The following examples pertain to specific technology embodiments and point out specific features, elements, or steps that may be used or otherwise combined in achieving such embodiments.

[00117] Embodiment 1 includes an apparatus of a user equipment (UE) operable to mitigate an impact of multiplexing of signals of which at least two are of different traffic types, the UE comprising: one or more processors configured to, decode, at the UE, assistance information associated with an interfering signal of a plurality of signals multiplexed in a same time-frequency resource region, the assistance information includes at least one of a time-frequency resource region information and a physical layer transmission format information; and decode, at the UE, at least one of the plurality of signals multiplexed in the same time-frequency resource region based on the decoded assistance information to extract a selected signal, wherein the plurality of signals include the selected signal and the interfering signal; anda memory interface configured to send to a memory one or more of the assistance information, and the decoded selected signal.

[00118] Embodiment 2 includes the apparatus of embodiment 1 , wherein the physical layer transmission format includes one or more of modulation information, a reference signal structure, a subcarrier spacing, and a transmission duration.

[00119] Embodiment 3 includes the apparatus of embodiments 1 or 2, wherein the one or more processors are further configured to, decode, by the UE, an indication to switch numerologies for a subsequent transmission. [00120] Embodiment 4 includes the apparatus of embodiments 1 or 2, wherein the assistance information indicates one or more time/frequency regions with different or same numerologies.

[00121] Embodiment 5 includes the apparatus of embodiments 1 or 2, wherein the assistance information is included in a first control channel at the beginning of a Transmission Time Interval (TTI) that indicates a resource allocation for the desired signal and a second control channel within or at an end of one or more allocated resources that indicates one or more punctured resources.

[00122] Embodiment 6 includes an apparatus of a wireless system operable to mitigate an impact of multiplexing of signals of which at least two are of different traffic types, the wireless system comprising: one or more processors configured to, determine a first time-frequency resource region for transmission; encode a data packet of a first traffic into a first coded stream and map the coded stream into a first set of Resource Elements (RE), the first set of REs being a subset of the first time-frequency resource region; multiplex a demodulation reference signal associated with the first traffic into a second set of REs, the second set of REs being a subset of the first time-frequency resource region; multiplex an interference reference signal associated with a second traffic into a third set of REs, the third set of REs being a subset of the first time- frequency resource region; encode the first, second, and third set of REs for transmission on the first time-frequency resource; and encode information regarding the first time- frequency resource region, the first reference signal, and the second reference signal for transmission on a control channel; and a memory interface configured to send to a memory one or more of the data packet, and the first, second, and third set of REs.

[00123] Embodiment 7 includes the apparatus of embodiment 6, wherein a time- span of the third set of REs is greater than a span of the second set of REs.

[00124] Embodiment 8 includes the apparatus of embodiment 6, wherein the third set of REs is associated with a single antenna port or with zero transmission power.

[00125] Embodiment 9 includes the apparatus of embodiment 6, wherein the second set of REs is associated with one or more antenna ports. [00126] Embodiment 10 includes the apparatus of embodiment 6, wherein the third set of REs is used for interference handling via interference covariance estimation per Orthogonal Frequency Division Multiplexing (OFDM) symbol.

[00127] Embodiment 11 includes the apparatus of embodiments 6-9 or 10, wherein the first traffic comprises an Enhanced Mobile Broadband (eMBB) transmission; and the second traffic comprises an Ultra Reliable Low Latency Communication

(URLLC) transmission.

[00128] Embodiment 12 includes the apparatus of embodiment 11, wherein the eMBB traffic and URLLC traffic have different Transmission Time Intervals (TTI) and the same subcarrier spacing.

[00129] Embodiment 13 includes the apparatus of embodiment 11, wherein the eMBB traffic and URLLC traffic have different subcarrier spacing.

[00130] Embodiment 14 includes the apparatus of embodiment 11, wherein the eMBB traffic and URLLC traffic do not occupy orthogonal resources.

[00131] Embodiment 15 includes an apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising: one or more processors configured to, detect, at the BS, an Uplink (UL) Ultra Reliable Low Latency Communication (URLLC) transmission at a start of an URLLC Transmission Time Interval (TTI), wherein UL URLLC resources are allocated within Downlink (DL) Enhanced Mobile Broadband (eMBB) resources; and encode, for transmission at the BS, a DL eMBB transmission, wherein a part of the DL eMBB transmission is dropped or punctured to receive the UL URLLC transmission when detected, and wherein a mapping of the DL eMBB resources is adapted to utilize a part of an eMBB symbol duration to receive the UL URLLC transmission; and a memory interface configured to send to a memory one or more of UL URLLC, the DL eMBB, and the mapping of the DL eMBB.

[00132] Embodiment 16 includes the apparatus of embodiment 15, wherein the one or more processors are further configured to, decode, at the BS, the detected UL URLLC transmission.

[00133] Embodiment 17 includes the apparatus of embodiments 15 or 16, wherein adapting the mapping of the DL eMBB resources includes interlace mapping or interleave mapping of resource elements into affected symbols. [00134] Embodiment 18 includes the apparatus of embodiments 15 or 16, wherein adapting the mapping of the DL eMBB resources includes dynamically changing eMBB numerology of affected symbols.

[00135] Embodiment 19 includes the apparatus of embodiments 15 or 16, wherein the URLLC transmission and eMBB transmission are Time Division Duplexed (TDD).

[00136] Embodiment 20 include an apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising: one or more processors configured to, determine, by the BS, a scheduled Uplink (UL) Enhance Mobile

Broadband (eMBB) transmission; encode, for transmission by the BS, an eMBB

Downlink Control Information (DCI) including an indication cancelling an UL eMBB transmission, when an Ultra Reliable Low Latency Communication (URLLC) latency budget exceeds a DCI processing time, for a UE to be able to drop the scheduled UL eMBB transmission before a downlink (DL) URLLC transmission; and encode, for transmission by the BS, the DL URLLC transmission; and a memory interface configured to send to a memory one or more of the UL eMBB schedule, and the eMBB DCI.

[00137] Embodiment 21 includes the apparatus of embodiment 20, wherein the URLLC transmission and eMBB transmission are Time Division Duplexed (TDD).

[00138] Embodiment 22 includes an apparatus of a User Equipment (UE) operable to mitigate an impact of multiplexing of signals, the UE comprising: one or more processors configured to, perform, by the UE, a clear channel assessment (CCA) at a start of an Ultra Reliable Low Latency Communication (URLLC) Transmission Time Interval (TTI) to detect a Downlink (DL) URLLC transmission; and encode, for transmission by the UE, an Uplink (UL) Enhanced Mobile Broadband (eMBB) transmission when an ongoing DL URLLC transmission is not detected by the CCA; and a memory interface configured to send to a memory the UL eMBB transmission.

[00139] Embodiment 23 includes the apparatus of embodiment 22, wherein timing of transmitting the UL eMBB transmission is modified to start after the DL URLLC transmission plus a propagation delay of the DL URLLC transmission.

[00140] Embodiment 24 includes the apparatus of embodiment 22, wherein the

URLLC transmission and eMBB transmission are time division duplexed (TDD). [00141] Embodiment 25 includes an apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising: one or more processors configured to, receive, by the BS, at least two signals multiplexed into a same time-frequency resource, the at least two signals including an Uplink (UL) Enhanced Mobile Broadband (eMBB) transmission and an UL Ultra Reliable Low Latency

Communication (URLLC) transmission multiplexed using a spreading scheme; decode, by the BS, the at least two signals to extract the eMBB transmission and the URLLC transmission based on transmission parameters of the spreading scheme and UL grant resource allocations of the eMBB transmission and the URLLC transmission; and memory interface configured to send to a memory one or more of the spreading scheme and the decoded eMBB transmission.

[00142] Embodiment 26 includes the apparatus of embodiment 25, wherein the one or more processors are further configured to, encode, for transmission by the BS, the UL grant resource allocations of the Enhanced Mobile Broadband (eMBB) transmission and the Ultra Reliable Low Latency Communication (URLLC) transmission, and the spreading scheme configuration to a UE prior to receiving the at least two signals.

[00143] Embodiment 27 includes the apparatus of embodiment 25, wherein the one or more processors are further configured to, acquire, by the BS, the UL grant resource allocations of the eMBB transmission and the URLLC transmission of a neighboring cell from which the UL eMBB transmission originated.

[00144] Embodiment 28 includes the apparatus of embodiment 25, wherein the URLLC transmission and eMBB transmission are Time Division Duplexed (TDD).

[00145] Embodiment 29 includes the apparatus of embodiment 25, wherein the URLLC transmission and eMBB transmission are Frequency Division Duplexed (FDD).

[00146] Embodiment 30 includes an apparatus of a User Equipment (UE) operable to mitigate an impact of multiplexing of signals, the UE comprising: one or more processors configured to, perform, by the UE, a clear channel assessment (CCA) at a start of an Ultra Reliable Low Latency Communication (URLLC) Transmission Time Interval (TTI) to detect an Uplink (UL) URLLC transmission on a shared resource before starting an UL Enhanced Mobile Broadband (eMBB) transmission; and encode, for transmission by the UE, the UL eMBB transmission on a current scheduled resource when an UL URLLC transmission preamble sequence is not detected by the CCA; and memory interface configured to send to a memory the UL eMBB transmission.

[00147] Embodiment 31 includes the apparatus of embodiment 30, wherein the one or more processors are further configured to, encode, for transmission by the UE, the UL eMBB transmission on a next scheduled resource when the UL URLLC transmission preamble sequence is detected by the CCA.

[00148] Embodiment 32 includes the apparatus of embodiment 30, wherein the URLLC transmission and eMBB transmission are Time Division Duplexed (TDD).

[00149] Embodiment 33 includes the apparatus of embodiment 30, wherein the URLLC transmission and eMBB transmission are Frequency Division Duplexed (FDD).

[00150] Embodiment 34 includes an apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising: one or more processors configured to, encode, for transmission by the BS to a first User Equipment (UE), an Enhanced Mobile Broadband (eMBB) Transport Block (TB) at a given (n) Transmission Time Interval (TTI), including an indication to send a code block (CB) or code block group (CBG) level Hybrid Automatic Repeat Request (HARQ) at a specified (n+k) TTI when one or more Resource Blocks (RB) are shared by an eMBB service and an URLLC service; encode, for transmission by the BS to a second UE, an URLLC Code Block (CB) or Code Block Group (CBG) using one or more punctured Orthogonal Frequency Division Multiplex (OFDM) symbols during the given (n) TTI; predict, by the BS, when one or more CBs or CBGs of the eMBB TB cannot be decoded due to the one or more punctured OFDM symbols because of the transmission of the CB or CBG of the URLLC during the given (n) TTI; encode, for autonomous retransmission by the BS to the first UE, the one or more CBs or CBGs of the eMBB TB predicted to be affected at a next (n+1) TTI using same redundancy bits as the TB at the given (n) TTI; and a memory interface configured to send to a memory one or more of the CB or CBGs of the eMBB TB.

[00151] Embodiment 35 includes the apparatus of embodiment 34, wherein the one or more processors are further configured to determine, at the BS, whether to retransmit select CBs or CBGs of the eMBB TB, at the specified (n+k) TTI, based on reception of a feedback from the UE. [00152] Embodiment 36 includes the apparatus of embodiment 34, wherein determining whether to retransmit one or more affected CBs or CBGs of the eMBB TB includes, determining, by the BS, one or more indices of the one or more CBs or CBGs of the eMBB TB punctured by CB or CBG of the URLLC; estimate, by the BS, whether the first UE can or cannot correctly decode the affected CBs or CBGs of the eMBB TB; and autonomously retransmit, by the BS, the one or more CBs or CBGs of the eMBB TB when estimated that the first UE cannot correctly decode the affected CBs or CBGs of the eMBB TB.

[00153] Embodiment 37 includes the apparatus of embodiment 34, wherein the eMBB traffic and URLLC traffic do not occupy orthogonal resources.

[00154] Embodiment 38 includes at least one machine readable storage medium having instructions embodied thereon that when executed perform a process to mitigate an impact of multiplexing of signals comprising: decoding assistance information associated with an interfering signal of a plurality of signals multiplexed in a same time- frequency resource region, the assistance information includes at least one of a time- frequency resource region information and a physical layer transmission format information; and decoding at least one of the plurality of signals multiplexed in the same time-frequency resource region based on the decoded assistance information to extract a selected signal, wherein the plurality of signals include the selected signal and the interfering signal.

[00155] Embodiment 39 includes the at least one machine readable storage medium of embodiment 38, wherein the physical layer transmission format includes one or more of modulation information, a reference signal structure, a subcarrier spacing, and a transmission duration.

[00156] Embodiment 40 includes the at least one machine readable storage medium of embodiments 38 or 39, further comprising: decoding an indication to switch numerologies for a subsequent transmission.

[00157] Embodiment 41 includes the at least one machine readable storage medium of embodiments 38 or 39, wherein the assistance information indicates one or more time/frequency regions with different or same numerologies. [00158] Embodiment 42 includes the at least one machine readable storage medium of embodiments 38 or 39, wherein the assistance information is included in a first control channel at the beginning of a Transmission Time Interval (TTI) that indicates a resource allocation for the desired signal and a second control channel within or at an end of one or more allocated resources that indicates one or more punctured resources.

[00159] Embodiment 43 includes at least one machine readable storage medium having instructions embodied thereon that when executed perform a process to mitigate an impact of multiplexing of signals comprising: encoding an Enhanced Mobile

Broadband (eMBB) Transport Block (TB) at a given (n) Transmission Time Interval (TTI), including an indication to send a code block (CB) or code block group (CBG) level Hybrid Automatic Repeat Request (HARQ) at a specified (n+k) TTI when one or more Resource Blocks (RB) are shared by an eMBB service and an URLLC service; encoding an URLLC Code Block (CB) or Code Block Group (CBG) using one or more punctured Orthogonal Frequency Division Multiplex (OFDM) symbols during the given (n) TTI; predicting when one or more CBs or CBGs of the eMBB TB cannot be decoded due to the one or more punctured OFDM symbols because of the transmission of the CB or CBG of the URLLC during the given (n) TTI; encoding the one or more CBs or CBGs of the eMBB TB predicted to be affected at a next (n+1) TTI using same redundancy bits as the TB at the given (n) TTI.

[00160] Embodiment 44 includes the at least one machine readable storage medium of embodiment 43, wherein the one or more processors are further configured to determine, at the BS, whether to retransmit select CBs or CBGs of the eMBB TB, at the specified (n+k) TTI, based on reception of a feedback from the UE.

[00161] Embodiment 45 includes the at least one machine readable storage medium of embodiment 43, wherein determining whether to retransmit one or more affected CBs or CBGs of the eMBB TB includes, determining, by the BS, one or more indices of the one or more CBs or CBGs of the eMBB TB punctured by CB or CBG of the URLLC; estimate, by the BS, whether the first UE can or cannot correctly decode the affected CBs or CBGs of the eMBB TB; and autonomously retransmit, by the BS, the one or more CBs or CBGs of the eMBB TB when estimated that the first UE cannot correctly decode the affected CBs or CBGs of the eMBB TB. [00162] Embodiment 46 includes the at least one machine readable storage medium of embodiment 43, wherein the eMBB traffic and URLLC traffic do not occupy orthogonal resources.

[00163] 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 aspects, 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 aspects, circuitry may include logic, at least partially operable in hardware.

[00164] 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, transitory or 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. Circuitry may include hardware, firmware, program code, executable code, computer instructions, and/or software. A non-transitory computer readable storage medium may be a computer readable storage medium that does not include signal. 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). 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.

[00165] As used herein, the term processor may include general purpose processors, specialized processors such as VLSI, FPGAs, or other types of specialized processors, as well as base band processors used in transceivers to send, receive, and process wireless communications.

[00166] 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.

[00167] 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 cannot 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.

[00168] 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. [00169] 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.

[00170] 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.

[00171] 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 may 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.

[00172] 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 may be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment (UE) operable to mitigate an impact of multiplexing of signals of which at least two are of different traffic types, the UE comprising:

one or more processors configured to,

decode, at the UE, assistance information associated with an interfering signal of a plurality of signals multiplexed in a same time-frequency resource region, the assistance information includes at least one of a time-frequency resource region information and a physical layer transmission format information; and

decode, at the UE, at least one of the plurality of signals multiplexed in the same time-frequency resource region based on the decoded assistance information to extract a selected signal, wherein the plurality of signals include the selected signal and the interfering signal; and

a memory interface configured to send to a memory one or more of the assistance information, and the decoded selected signal.

2. The apparatus of claim 1, wherein the physical layer transmission format includes one or more of modulation information, a reference signal structure, a subcarrier spacing, and a transmission duration.

3. The apparatus of claims 1 or 2, wherein the one or more processors are further configured to,

decode, by the UE, an indication to switch numerologies for a subsequent transmission.

4. The apparatus of claims 1 or 2, wherein the assistance information indicates one or more time/frequency regions with different or same numerologies.

5. The apparatus of claims 1 or 2, wherein the assistance information is included in a first control channel at the beginning of a Transmission Time Interval (TTI) that indicates a resource allocation for the desired signal and a second control channel within or at an end of one or more allocated resources that indicates one or more punctured resources.

6. An apparatus of a wireless system operable to mitigate an impact of multiplexing of signals of which at least two are of different traffic types, the wireless system comprising:

one or more processors configured to,

determine a first time-frequency resource region for transmission;

encode a data packet of a first traffic into a first coded stream and map the coded stream into a first set of Resource Elements (RE), the first set of REs being a subset of the first time-frequency resource region;

multiplex a demodulation reference signal associated with the first traffic into a second set of REs, the second set of REs being a subset of the first time- frequency resource region;

multiplex an interference reference signal associated with a second traffic into a third set of REs, the third set of REs being a subset of the first time- frequency resource region;

encode the first, second, and third set of REs for transmission on the first time-frequency resource; and

encode information regarding the first time-frequency resource region, the first reference signal, and the second reference signal for transmission on a control channel; and a memory interface configured to send to a memory one or more of the data packet, and the first, second, and third set of REs.

7. The apparatus of claim 6, wherein a time-span of the third set of REs is greater than a span of the second set of REs.

8. The apparatus of claim 6, wherein the third set of REs is used for interference handling via interference covariance estimation per Orthogonal Frequency Division Multiplexing (OFDM) symbol.

9. The apparatus of claims 6-7 or 8, wherein

the first traffic comprises an Enhanced Mobile Broadband (eMBB) transmission; and

the second traffic comprises an Ultra Reliable Low Latency Communication (URLLC) transmission.

10. The apparatus of claim 9, wherein the eMBB traffic and URLLC traffic have different Transmission Time Intervals (TTI) and the same subcarrier spacing.

11. The apparatus of claim 9, wherein the eMBB traffic and URLLC traffic have different subcarrier spacing.

12. The apparatus of claim 9, wherein the eMBB traffic and URLLC traffic do not occupy orthogonal resources.

13. An apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising:

one or more processors configured to, detect, at the BS, an Uplink (UL) Ultra Reliable Low Latency

Communication (URLLC) transmission at a start of an URLLC Transmission Time Interval (TTI), wherein UL URLLC resources are allocated within Downlink (DL) Enhanced Mobile Broadband (eMBB) resources; and encode, for transmission at the BS, a DL eMBB transmission, wherein a part of the DL eMBB transmission is dropped or punctured to receive the UL URLLC transmission when detected, and wherein a mapping of the DL eMBB resources is adapted to utilize a part of an eMBB symbol duration to receive the UL URLLC transmission; and

a memory interface configured to send to a memory one or more of UL URLLC, the DL eMBB, and the mapping of the DL eMBB.

14. The apparatus of claim 13, wherein the one or more processors are further configured to,

decode, at the BS, the detected UL URLLC transmission.

15. The apparatus of claims 13 or 14, wherein adapting the mapping of the DL eMBB resources includes interlace mapping or interleave mapping of resource elements into affected symbols.

16. The apparatus of claims 13 or 14, wherein adapting the mapping of the DL eMBB resources includes dynamically changing eMBB numerology of affected symbols.

17. An apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising:

one or more processors configured to,

determine, by the BS, a scheduled Uplink (UL) Enhance Mobile

Broadband (eMBB) transmission; encode, for transmission by the BS, an eMBB Downlink Control Information (DCI) including an indication cancelling an UL eMBB transmission, when an Ultra Reliable Low Latency Communication (URLLC) latency budget exceeds a DCI processing time, for a UE to be able to drop the scheduled UL eMBB transmission before a downlink (DL) URLLC transmission; and

encode, for transmission by the BS, the DL URLLC transmission; and a memory interface configured to send to a memory one or more of the UL eMBB schedule, and the eMBB DCI.

18. An apparatus of a User Equipment (UE) operable to mitigate an impact of multiplexing of signals, the UE comprising:

one or more processors configured to,

perform, by the UE, a clear channel assessment (CCA) at a start of an Ultra Reliable Low Latency Communication (URLLC) Transmission Time Interval (TTI) to detect a Downlink (DL) URLLC transmission; and encode, for transmission by the UE, an Uplink (UL) Enhanced Mobile Broadband (eMBB) transmission when an ongoing DL URLLC transmission is not detected by the CCA; and

a memory interface configured to send to a memory the UL eMBB transmission.

19. The apparatus of claim 18, wherein timing of transmitting the UL eMBB transmission is modified to start after the DL URLLC transmission plus a propagation delay of the DL URLLC transmission.

20. An apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising:

one or more processors configured to, receive, by the BS, at least two signals multiplexed into a same time- frequency resource, the at least two signals including an Uplink (UL) Enhanced Mobile Broadband (eMBB) transmission and an UL Ultra Reliable Low Latency Communication (URLLC) transmission multiplexed using a spreading scheme;

decode, by the BS, the at least two signals to extract the eMBB transmission and the URLLC transmission based on transmission parameters of the spreading scheme and UL grant resource allocations of the eMBB transmission and the URLLC transmission; and

memory interface configured to send to a memory one or more of the spreading scheme and the decoded eMBB transmission.

21. The apparatus of claim 20, wherein the one or more processors are further configured to,

encode, for transmission by the BS, the UL grant resource allocations of the Enhanced Mobile Broadband (eMBB) transmission and the Ultra Reliable Low Latency Communication (URLLC) transmission, and the spreading scheme configuration to a UE prior to receiving the at least two signals.

22. The apparatus of claim 20, wherein the one or more processors are further configured to,

acquire, by the BS, the UL grant resource allocations of the eMBB transmission and the URLLC transmission of a neighboring cell from which the UL eMBB transmission originated.

23. An apparatus of a User Equipment (UE) operable to mitigate an impact of multiplexing of signals, the UE comprising:

one or more processors configured to, perform, by the UE, a clear channel assessment (CCA) at a start of an Ultra Reliable Low Latency Communication (URLLC) Transmission Time Interval (TTI) to detect an Uplink (UL) URLLC transmission on a shared resource before starting an UL Enhanced Mobile Broadband (eMBB) transmission; and

encode, for transmission by the UE, the UL eMBB transmission on a current scheduled resource when an UL URLLC transmission preamble sequence is not detected by the CCA; and

memory interface configured to send to a memory the UL eMBB transmission.

24. The apparatus of claim 23, wherein the one or more processors are further configured to,

encode, for transmission by the UE, the UL eMBB transmission on a next scheduled resource when the UL URLLC transmission preamble sequence is detected by the CCA.

25. An apparatus of a Base Station (BS) operable to mitigate an impact of multiplexing of signals, the BS comprising:

one or more processors configured to,

encode, for transmission by the BS to a first User Equipment (UE), an

Enhanced Mobile Broadband (eMBB) Transport Block (TB) at a given (n) Transmission Time Interval (TTI), including an indication to send a code block (CB) or code block group (CBG) level Hybrid Automatic Repeat Request (HARQ) at a specified (n+k) TTI when one or more Resource Blocks (RB) are shared by an eMBB service and an URLLC service;

encode, for transmission by the BS to a second UE, an URLLC Code Block (CB) or Code Block Group (CBG) using one or more punctured Orthogonal Frequency Division Multiplex (OFDM) symbols during the given (n) TTI; predict, by the BS, when one or more CBs or CBGs of the eMBB TB cannot be decoded due to the one or more punctured OFDM symbols because of the transmission of the CB or CBG of the URLLC during the given (n) TTI; encode, for autonomous retransmission by the BS to the first UE, the one or more CBs or CBGs of the eMBB TB predicted to be affected at a next

(n+1) TTI using same redundancy bits as the TB at the given (n) TTI; and a memory interface configured to send to a memory one or more of the CB or CBGs of the eMBB TB.

26. The apparatus of claim 25, wherein the one or more processors are further configured to determine, at the BS, whether to retransmit select CBs or CBGs of the eMBB TB, at the specified (n+k) TTI, based on reception of a feedback from the UE.

27. The apparatus of claim 25, wherein determining whether to retransmit one or more affected CBs or CBGs of the eMBB TB includes,

determining, by the BS, one or more indices of the one or more CBs or CBGs of the eMBB TB punctured by CB or CBG of the URLLC;

estimate, by the BS, whether the first UE can or cannot correctly decode the affected CBs or CBGs of the eMBB TB; and

autonomously retransmit, by the BS, the one or more CBs or CBGs of the eMBB

TB when estimated that the first UE cannot correctly decode the affected CBs or CBGs of the eMBB TB.

28. The apparatus of claim 25, wherein the eMBB traffic and URLLC traffic do not occupy orthogonal resources.