WO2018039160A1 - Dynamic loading control and interference management for mobile communication systems - Google Patents

Abstract

An apparatus is configured to be employed within a base station. The apparatus comprises baseband circuitry which includes a radio frequency (RF) interface and one or more processors. The one or more processors are configured to generate control information for loading and interference conditions, generate a control message using the control information for non-orthogonal multiple access (NOMA) or orthogonal multiple access (OMA) uplink transmissions by one or more user equipment (UE) devices, generate a payload data unit (PDU) having the control message, and send the PDU to the RF interface for transmission to the one or more UE devices.

Description

DYNAMIC LOADING CONTROL AND INTERFERENCE MANAGEMENT FOR MOBILE COMMUNICATION SYSTEMS

FIELD

[0001] Various embodiments generally relate to the field of wireless communications.

RELATED APPLICATIONS

[0002] This application claims the benefit of Provisional Application No. 62/378,047, filed August 22, 2016.

BACKGROUND

[0003] Wireless or mobile communication involves wireless communication between two or more devices. The communication requires resources to transmit data from one device to another and/or to receive data at one device from another.

[0004] Wireless communication typically has limited resources in terms of time and frequency. The utilization of these limited resources can impact communication data rate, reliability, latency and the like. Underutilization of these resources can occur, thereby degrading communication, reliability, data rate and the like. Additionally, higher data rates are increasingly used or required for wireless communication.

[0005] What is needed are techniques to facilitate allocation of resources used for wireless communications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] FIG. 1 illustrates a block diagram of an example wireless communications network environment for a network device (e.g., a UE or an eNB) according to various aspects or embodiments.

[0007] FIG. 2 illustrates another block diagram of an example of wireless

communications network environment for a network device (e.g., a UE or an eNB) according to various aspects or embodiments.

[0008] FIG. 3 another block diagram of an example of wireless communications network environment for network device (e.g., a UE or an eNB) with various interfaces according to various aspects or embodiments.

[0009] FIG. 4 is a diagram illustrating a framework for dynamic loading control and interference management for mobile communication systems in accordance with some embodiments. [0010] FIG. 5 is a diagram illustrating an example of a medium access control layer (MAC) protocol data unit (PDU) in accordance with some embodiments.

[0011] FIG. 6 is a diagram illustrating a MAC DL control message 600 for an ACK response in accordance with some embodiments.

[0012] FIG. 7 is a diagram illustrating a messaging scenario including a DL control message for a schedule based OMA or NOMA in accordance with some embodiments.

[0013] FIG. 8 is a diagram illustrating MAC DL control message in accordance with some embodiments.

[0014] FIG. 9 is a diagram illustrating a messaging scenario including a DL control message for a grant-less UE transmission in accordance with some embodiments.

[0015] FIG. 10 is a diagram illustrating resource allocations based on dynamic loading and/or interference in accordance with some embodiments.

[0016] FIG. 1 1 is a diagram illustrating puncturing of a last symbol of a slot to mitigate interference for asynchronous UL transmissions in accordance with some embodiments.

[0017] FIG. 12 is a flow diagram illustrating a method for dynamic loading control and/or interference management for mobile communication systems in accordance with some embodiments

DETAILED DESCRIPTION

[0018] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. Embodiments herein may be related to RAN1 and 5G.

[0019] As utilized herein, terms "component," "system," "interface," and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor, a process running on a processor, a controller, an object, an executable, a program, a storage device, and/or a computer with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more."

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

[0021] As another example, a component can be an apparatus with specific

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

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

"comprising".

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

[0024] Wireless/mobile communication typically has limited resources in terms of time and frequency. The utilization of these limited resources can impact

communication data rate, reliability, latency and the like. Underutilization of these resources can occur, thereby degrading communication, reliability, data rate and the like. Additionally, higher data rates are increasingly used or required for wireless communication.

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

[0026] A new radio access technology (RAT) supports a broad range of use cases including enhanced mobile broadband, machine-type communication (MTC), massive MTC (mMTC), critical MTC and operates in frequency ranges up to 100 GHz. For massive MTC (mMTC) type of applications, grant-free non-orthogonal multiple access may be beneficial for supporting massive number of UEs requesting intermittent transmissions of small data packets.

[0027] Autonomous/grant-free/contention based UL non-orthogonal multiple access for the new RAT has the following characteristics: [0028] A transmission from a UE does not need the dynamic and explicit scheduling grant from an eNB. Multiple UEs can share the same time and frequency resources.

[0029] For autonomous/grant-free/contention based UL non-orthogonal multiple access (NOMA) transmission(s), collision of time/frequency resources from different UEs can be identified and mitigated. Some possible techniques to facilitate grant-free communication includes using a code sequence, UL and/or DL synchronization, managing power control, determining receiver impact, and the like.

[0030] The code sequence or interleaver pattern can be determined by the node and/or used by the UE.

[0031] Further, UL synchronization between a UE and an eNB. DL synchronization is assumed. The synchronization includes where timing offsets between UEs are within a cyclic prefix and where timing offsets between UEs are greater than a cyclic prefix. The FFS is a model of timing offsets.

[0032] Examples of power control include open-loop power control, realistic open- loop power control and close-loop power control. The open-loop power control assumes near ideal conditions and determines an average signal to noise ratio (SNR) between UEs for link level calibration. The realistic open-loop power control generates coefficients, such as alpha and P0 values, based on realistic conditions. The generated coefficients are used to determine power values, such as an average signal to noise ratio (SNR) between UEs for link level calibration. The close-loop power control determines power in closed -loop situations.

[0033] For an UL non-orthogonal multiple access (NOMA) transmission, a UE device may attempt to transmit the data packets multiple times until it receives the

Acknowledge (ACK) response from eNB. However, in the case of relatively high loading conditions where a large number of UEs may attempt to transmit the data using NOMA techniques simultaneously, consistent strong interference may be observed at the eNB receiver, which may result in decoding failure and degraded performance.

[0034] To address this interference and the like, and thereby improve the system performance, dynamic loading control and interference management is utilized. In particular, an eNB may schedule orthogonal multiple access (OMA) for one or more UEs and/or transmit a message to a group of UEs to inform the loading condition or access information.

[0035] Thus, various embodiments are shown that facilitate dynamic loading and/or interference. [0036] FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments. The system 100 is shown to include a user equipment (UE) 101 and a UE 102. The UEs 101 and 1 02 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but can 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.

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

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

[0039] In this embodiment, the UEs 101 and 1 02 can further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 can

alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

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

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

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

management and data packet scheduling, and mobility management.

[0043] In accordance with some embodiments, the UEs 101 and 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1 1 1 and 1 1 2 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers. [0044] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1 1 1 and 1 12 to the UEs 101 and 1 02, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

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

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

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

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

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

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

[0050] The S-GW 122 can terminate the S1 interface 1 13 towards the RAN 1 1 0, and routes data packets between the RAN 1 10 and the CN 120. In addition, the S-GW 122 can be a local mobility anchor point for inter-RAN node handovers and also can provide an anchor for inter-3GPP mobility. Other responsibilities can include lawful intercept, charging, and some policy enforcement. [0051] The P-GW 123 can terminate an SGi interface toward a PDN. The P-GW 123 can route data packets between the CN network 120 and external networks such as a network including the application server 130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 can be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 123 is shown to be communicatively coupled to an application server 130 via an IP communications interface 125. The application server 130 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1 01 and 102 via the CN 120.

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

[0053] In one or more embodiments, IMS services can be identified more accurately in a paging indication, which can enable the UEs 101 , 102 to differentiate between PS paging and IMS service related paging. As a result, the UEs 101 , 102 can apply preferential prioritization for IMS services as desired based on any number of requests by any application, background searching (e.g., PLMN searching or the like), process, or communication. In particular, the UEs 1 01 , 102 can differentiate the PS domain paging to more distinguishable categories, so that IMS services can be identified clearly in the UEs 101 , 102 in comparison to PS services. In addition to a domain indicator (e.g., PS or CS), a network (e.g., CN 120, RAN 1 10, AP 106, or combination thereof as an eNB or the other network device) can provide further, more specific information with the TS 36.331 -Paging message, such as a "paging cause" parameter. The UE can use this information to decide whether to respond to the paging, possibly interrupting some other procedure like an ongoing PLMN search.

[0054] In one example, when UEs 101 , 102 can be registered to a visited PLMN (VPLMN) and performing PLMN search (i.e., background scan for a home PLMN (HPLMN) or a higher priority PLMN), or when a registered UE is performing a manual PLMN search, the PLMN search can be interrupted in order to move to a connected mode and respond to a paging operation as part of a MT procedure / operation.

Frequently, this paging could be for PS data (non-IMS data), where, for example, an application server 130 in the NW wants to push to the UE 101 or 102 for one of the many different applications running in / on the UE 101 or 1 02, for example. Even though the PS data could be delay tolerant and less important, in legacy networks the paging is often not able to be ignored completely, as critical services like an IMS call can be the reason for the PS paging. The multiple interruptions of the PLMN search caused by the paging can result in an unpredictable delay of the PLMN search or in the worst case even in a failure of the procedure, resulting in a loss of efficiency in network

communication operations. A delay in moving to or handover to a preferred PLMN (via manual PLMN search or HPLMN search) in a roaming condition can incur more roaming charges on a user as well.

[0055] FIG. 2 illustrates example components of a network device 200 in accordance with some embodiments. In some embodiments, the device 200 can include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 21 2 coupled together at least as shown. The components of the illustrated device 200 can be included in a UE 101 , 102 or a RAN node 1 1 1 , 1 12, AP, AN, eNB or other network component. In some embodiments, the device 200 can include less elements (e.g., a RAN node can not utilize application circuitry 202, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the network device 200 can include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations). [0056] The application circuitry 202 can include one or more application processors. For example, the application circuitry 202 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 200. In some embodiments, processors of application circuitry 202 can process IP data packets received from an EPC.

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

encoding/decoding circuitry of the baseband circuitry 204 can include convolution, tail- biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other embodiments. [0058] In some embodiments, the baseband circuitry 204 can include one or more audio digital signal processor(s) (DSP) 204F. The audio DSP(s) 204F can be include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other embodiments. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 204 and the application circuitry 202 can be implemented together such as, for example, on a system on a chip (SOC).

[0059] In some embodiments, the baseband circuitry 204 can provide for

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

[0060] RF circuitry 206 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various

embodiments, the RF circuitry 206 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 206 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204. RF circuitry 206 can also include a transmit signal path which can include circuitry to up- convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.

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

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

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

[0064] In some embodiments, the output baseband signals and the input baseband signals can 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 can be digital baseband signals. In these alternate embodiments, the RF circuitry 206 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 204 can include a digital baseband interface to communicate with the RF circuitry 206.

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

embodiments is not limited in this respect.

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

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

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

[0069] Synthesizer circuitry 206d of the RF circuitry 206 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can 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 can 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.

[0070] In some embodiments, synthesizer circuitry 206d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can 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 can be a LO frequency (fLO). In some embodiments, the RF circuitry 206 can include an IQ/polar converter.

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

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

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

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

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

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

[0077] An additional power saving mode can 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 can be unreachable to the network and can power down completely. Any data sent during this time can incur a large delay with the delay presumed to be acceptable.

[0078] Processors of the application circuitry 202 and processors of the baseband circuitry 204 can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 204, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 204 can 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 can comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 can 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 can comprise a physical (PHY) layer of a UE/RAN node. Each of these layers can be implemented to operate one or more processes or network operations of embodiments / aspects herein.

[0079] In addition, the memory 204G can comprise one or more machine-readable medium / media including instructions that, when performed by a machine or component herein cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein. It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium (e.g., the memory described herein or other storage device). Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions. Also, any connection can also be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.

[0080] In general, there is a move to provide network services for the packet domain. The earlier network services like UMTS or 3G and predecessors (2G) configured a CS domain and a packet domain providing different services, especially CS services in the CS domain as well as voice services were considered to have a higher priority because consumers demanded an immediate response. Based on the domain that the paging was received, the device 200 could assign certain priority for the incoming transaction. Now with LTE / 5G most services are moving to the packet domain. Currently, the UE (e.g., 1 01 , 102, or device 200) can get paging for a packet service without knowing any further information about the paging of the MT procedure, such as whether someone is calling on a line, a VoIP call, or just some packet utilized from Facebook, other application service, or other similar MT service. As such, a greater opportunity exists for further delays without the possibility for the UE to discriminate between the different application packets that could initiate a paging and also give a different priority to it based on one or more user preferences. This can could be important for the UE because the UE might be doing other tasks more vital for resource allocation.

[0081] In one example, a UE (e.g., 101 , 102, or device 200) could be performing a background search for other PLMNs. This is a task the UE device 200 could do in regular intervals if it is not connected on its own home PLMN or a higher priority PLMN, but roaming somewhere else. A higher priority could be a home PLMN or some other PLMNs according to a list provided by the provider or subscriber (e.g., HSS 124).

Consequently, if a paging operation arrives as an MT service and an interruption results, such that a start and begin operation are executed, a sufficient frequency of these interruptions could cause the UE to never complete a background search in a reasonable way. This is one way where it would be advantageous for the UE or network device to know that the interruption is only a packet service, with no need to react to it immediately, versus an incoming voice call that takes preference immediately and the background scan should be postponed.

[0082] Additionally, the device 200 can be configured to connect or include multiple subscriber identity / identification module (SIM) cards / components, referred to as dual SIM or multi SIM devices. The device 200 can operate with a single transmit and receive component that can coordinate between the different identities from which the SIM components are operating. As such, an incoming voice call should be responded to as fast as possible, while only an incoming packet for an application could be relatively ignored in order to utilize resources for the other identity (e.g., the voice call or SIM component) that is more important or has a higher priority from a priority list / data set / or set of user device preferences, for example. This same scenario can also be utilized for other operations or incoming data, such as with a PLMN background search such as a manual PLMN search, which can last for a long period of time since, especially with a large number of different bands from 2G, etc. With an ever increasing number of bands being utilized in wireless communications, if paging interruptions come in between the operations already running without distinguishing between the various packet and real critical services such as voice, the network devices can interpret this manual PLMN search to serve and ensure against a drop or loss of any increment voice call, with more frequent interruptions in particular.

[0083] As stated above, even though in most of these cases the PS data is delay tolerant and less important, in legacy networks the paging cannot be ignored

completely, as critical services like an IMS call can be the reason for the PS paging. The multiple interruptions of a PLMN search caused by the paging can result in an unpredictable delay of the PLMN search or in the worst case even in a failure of the procedure. Additionally, a delay in moving to preferred PLMN (via manual PLMN search or HPLMN search) in roaming condition can incur more roaming charges on user.

Similarly, in multi-SIM scenario when UE is listening to paging channel of two networks simultaneously and has priority for voice service, a MT IMS voice call can be interpreted as "data" call as indicated in MT paging message and can be preceded by MT Circuit Switched (CS) paging of an other network or MO CS call initiated by user at same time. As such, embodiments / aspects herein can increase the call drop risk significantly for the SIM using IMS voice service.

[0084] In embodiments, 3GPP NW can provide further granular information about the kind of service the network is paging for. For example, the Paging cause parameter could indicate one of the following values / classes / categories: 1 ) IMS voice/video service; 2) IMS SMS service; 3) IMS other services (not voice/video/SMS-related; 4) any IMS service; 5) Other PS service (not IMS-related). In particular, a network device (e.g., an eNB or access point) could only be discriminating between IMS and non-IMS services could use 4) and 5), whereas a network that is able to discriminate between different types of IMS services (like voice/video call, SMS, messaging, etc.) could use 3) instead of 4) to explicitly indicate to the UE that the paging is for an IMS service different from voice/video and SMS. By obtaining this information UE may decide to suspend PLMN search only for critical services like incoming voice/video services.

[0085] In other aspects, dependent on the service category (e.g., values or classes 1 -5 above), the UE 101 , 102, or device 200 can memorize that there was a paging to which it did not respond, and access the network later, when the PLMN search has been completed and the UE decides to stay on the current PLMN. For example, if the reason for the paging was a mobile terminating IMS SMS, the MME can then inform the HSS (e.g., 124) that the UE is reachable again, and the HSS 124 can initiate a signaling procedure which will result in a delivery of the SMS to the UE once resources are more available or less urgent for another operation / application / or category, for example. To this purpose the UE 101 , 102, or 200 could initiate a periodic tau area update (TAU) procedure if the service category in the Paging message indicated "IMS SMS service", for example.

[0086] FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 204 of FIG. 2 can comprise processors 204A-204E and a memory 204G utilized by said processors. Each of the processors 204A-204E can include a memory interface, 304A-304E, respectively, to send/receive data to/from the memory 204G.

[0087] The baseband circuitry 204 can further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 312 (e.g., an interface to send/receive data to/from memory exernal to the baseband circuitry 204), an application circuitry interface 314 (e.g., an interface to send/receive data to/from the application circuitry 202 of FIG. 2), an RF circuitry interface 316 (e.g., an interface to send/receive data to/from RF circuitry 206 of FIG. 2), a wireless hardware connectivity interface 31 8 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 320 (e.g., an interface to send/receive power or control signals to / from the PMC 21 2. [0088] FIG. 4 is a diagram illustrating a framework 400 for dynamic loading control and interference management for mobile communication systems in accordance with some embodiments. The framework 400 can be utilized with the above embodiments and variations thereof, including the system 100 described above. The framework 400 is provided as an example and it is appreciated that suitable variations are

contemplated.

[0089] The framework 400 facilitates grant-less and grant based transmissions by providing a downlink (DL) control message that provides loading control and/or interference management information. The grant free transmission can include autonomous and non-orthogonal multiple access (NOMA) access, orthogonal multiple access (OMA) and the like based transmissions.

[0090] The loading control and/or interference management information permits the device 401 perform uplink (UL) transmissions based on and/or while considering the loading and interference information. As a result, the device 401 can therefore identify and utilize available resources for grant-less UL communications.

[0091] The framework 400 includes a network device 401 and a node 402. The device 401 is shown as a UE device and the node 402 is shown as an eNB for illustrative purposes. It is appreciated that the UE device 401 can be other network devices, such as Aps, ANs and the like. It is also appreciated that the eNB 402 can be other nodes or access nodes (ANs), such as BSs, gNB, RAN nodes and the like. Other network or network devices can be present and interact with the device 401 and/or the node 402.

[0092] Downlink (DL) transmissions occur from the eNB 402 to the UE 401 whereas uplink (UL) transmissions occur from the UE 401 to the eNB 402. The downlink transmissions utilize a DL control channel and a DL data channel. The uplink transmissions utilize an UL control channel and a UL data channel. The various channels can be different in terms of direction, link to another eNB and the like.

[0093] The eNB 402 generates a DL control message and transmits the control message as shown at 404. The UE 401 generates an UL transmission based on the control message also at 404. The interference and/or loading is mitigated by the eNB 402 and/or the UE 401 for the UL transmission. The UL transmission can be scheduled (granted) by the eNB 402 or can be grantless.

[0094] The control message includes control information that facilitates loading and/or interference management. The loading and/or interference management can be performed the by UE 401 , the eNB 402, and/or both the UE 401 and the eNB 402. The control message can be only for the UE 401 or for a group of UEs that includes the UE 401 .

[0095] Generally, the UE device 401 receives and decodes the DL control message and uses the control information to generate a grant-less/free or grant-based UL transmission in response.

[0096] In one example, the UE device 401 uses dynamic loading control and interference management based on the control information to determine dynamic loading and interference at the eNB 402 and to identify suitable resources, including time, frequency, power, and the like to use for the UL transmission. Thus, the control information can include interference and/or loading conditions at the eNB 402 to allow the UE device 401 to make the determination on UL resources to use.

[0097] In one example, the DL control message is provided within a control channel, such as a physical downlink control channel (PDCCH). In another example, the DL control message is provided within a data channel, such as a physical downlink shared channel (PDSCH) scheduled by a PDCCH.

[0098] The UL transmission can use NOMA, which uses the power domain for multiple access. Using NOMA can allow multiple UEs to access most or all subcarrier channels and bandwidth resources.

[0099] The DL control message and control information can be for a variety of purposes or types of information and examples of these types are shown at 406, 408 and 410.

[00100] In one example, the message includes an acknowledgement/non

acknowledgement (ACK/NACK) response for a corresponding UL transmission as shown at 406. In this example, the UE device 410 generate a grant-less UL

transmission using NOMA.

[00101 ] In another example, the message can include schedule information for the UE 401 related to an orthogonal multiple access (OMA) UL transmission or a NOMA UL transmission as shown at 408. The schedule information can be configured for a group of UEs, including the UE 401 .

[00102] In yet another example, the message includes informing one or more UE devices of loading conditions, access conditions, and the like of the eNB 402 as shown at 410. The UE 401 uses the control information to determine and utilize resources for UL transmissions that mitigate interference and loading impact.

[00103] In one example, the UE 401 uses the control information to identify a subcarrier not being used and uses the identified subcarrier for the UL transmission. [00104] In another example, the message includes a reallocation of resources based on loading and/or interference conditions at the eNB 402. The eNB 402 determines or obtains loading and/or interference conditions and generates a reallocation of the resources to mitigate interference and loading problems for UL transmissions. The reallocation can include assigning resources to subgroups of a group of UE devices that include the UE 401 .

[00105] The control message can be for a single UE device, such as the UE device 401 . Additionally, the control message can be for a group of UE devices, where the UE devices within the group use one or more shared physical resources to transmit UL data. A group identity can be used to mask a cyclic redundancy check (CRC) for PDCCH transmission within a common search space. Additionally, the control message can include UE identities, full or partial. Further, the identity can include a preamble and/or demodulation reference signal (DM-RS) sequence. The preamble and/or DM- RS sequence index can be carried in the control or shared channel to facilitate contention resolution.

[00106] It is appreciated that the framework 400 can be used with additional nodes and/or UE devices.

[00107] FIG. 5 is a diagram illustrating an example of a medium access control layer (MAC) protocol data unit (PDU) 500 in accordance with some embodiments. The PDU 500 can be used as the control message shown in FIG. 4 and/or variations thereof.

[00108] The PDU 500 includes, in this example, a MAC header, A? control messages (MSG), and padding. The MAC header includes a plurality of subheaders 501 . Each of the subheaders 501 is associated with one of the MAC control messages. Thus, for example, subheader 1 is associated with control message 1 , subheader 2 is associated with control message 2 and subheader n is associated with control message n.

[00109] The subheaders 501 can include a full UE identity (ID) and/or partial ID. The UE ID is an identity of a specific UE device, such as the device 401 . The UE ID identifies the UE that the associated control message is intended for.

[00110] The subheaders 501 can also include an E field/flag and or a T field/flag. The E flag, if present, indicates that more fields are present in the MAC header. The E field is set to "1 " to indicate at least another set of E/T/UE-ID fields follow. The E field is set to "0" to indicate that a MAC DL control message or padding starts at a next byte.

[00111 ] The T field indicates whether the MAC subheader includes a group ID, preamble ID, DM-RS ID, backoff indicator and the like. The T field is set to "0" to indicate the presence of a backoff indicator (Bl) field in the subheader. The T field is set to "1 " to indicate a presence of a group ID, preamble ID, DM-RS ID, backoff indicator and the like fields in the subheader.

[001 12] Additionally, the subheaders 501 can also include a preamble and/or DM-RS sequence index to identify or further identify which control message is intended for a given UE.

[001 13] In operation, a node, such as the eNB 402 generates the MAC PDU 500 and transmits the PDU 500 within a control or shared channel for a group of UE devices (from 1 to n). The group of UE devices receive and decode the PDU 500. Each UE decodes UE identity from the MAC header to identify the DL control message for the UE. The UE then uses the control message to generate a UL grant-less or grant free transmission based on control information from the control message.

[001 14] It is appreciated that the PDU 500 is provided for illustrative purposes and that suitable variations are contemplated.

[001 15] FIG. 6 is a diagram illustrating a MAC DL control message 600 for an ACK response in accordance with some embodiments. The control message 600 is included in MAC payload or PDU, such as the PDU 500 described above. The control message 600 is provided as an example for illustrative purposes and it is appreciated that suitable variations are contemplated. The control message 600 can be used in the framework 400 and variations thereof.

[001 16] A timing advance command can be included or omitted, depending on whether synchronous or asynchronous U L transmission is to be used. The timing advance command is generated by a node to synchronize or align UL transmissions for a particular UE device. The timing advance command can be used for PUSCH and/or PUCCH transmissions by the particular UE device.

[001 17] The control message 600 is shown with a plurality of messages or parts designated 1 -5. The message 600, in this example, is shown using octal base notation (OCT) and as octal numbers.

[001 18] A first part (OCT 1 ) includes an indicator R and a timing advance command for asynchronous communication.

[001 19] A second part (OCT 2) includes and/or continues the timing advance command for asynchronous communication and a full UE identity.

[00120] A third part (OCT 3) includes and/or continues the full UE identity.

[00121 ] A fourth part (OCT 4) includes and/or continues the full UE identity.

[00122] A fifth part (OCT 5) includes and/or continues the full UE identity. [00123] Thus, the control message 600 provides an ACK/NACK response to a particular UE device. Additionally, the control message includes the timing advance command and the full UE identity. The timing advance command provides the delay or offset for its subsequent UL transmission and the full UE identity allows the UE device to determine that the control message is for itself. It is appreciated that the control message 600 can be used in other lengths and the like and that other suitable variations are contemplated.

[00124] FIG. 7 is a diagram illustrating a messaging scenario 700 including a DL control message for a scheduled based OMA or NOMA in accordance with some embodiments. The scenario 700 is provided for illustrative purposes and it is

appreciated that suitable variations are contemplated.

[00125] An eNB may detect preambles and/or DM-RS sequences from multiple UE devices successfully, but fail to decode a packet associated with the detected preamble ID or DM-RS sequence ID. If the decoding failure occurs more than a threshold number of times, a high loading condition may exist at the eNB. The high loading condition is where consistent and relatively strong interference is observed at the eNB receiver.

[00126] The scenario 700 includes a UE device and an eNB. The UE device generates a transmission and subsequent retransmissions for data. The transmissions are received by the eNB, however they result in decoding failures 702. The eNB may be able to detect preambles and/or DM-RS sequences for the transmission, but is unable to decode the associated packet due to loading conditions at the eNB.

[00127] In this example, the eNB has a threshold of three (3). After the third transmission of the data, eNB generates a DL control message 703 that includes control information to facilitate transmission by the UE. It is appreciated that the repetition threshold can be other suitable values besides 3. The eNB also uses a DL monitoring window that is typically between two UL transmissions.

[00128] The control message and information includes UE specific time and frequency resources allocated for the UE using OMA transmission. Similar to random access response (RAR), a UL grant can be included in the control message. The grant identifies the specific time and frequency resources to use so that the eNB can decode the associated packet.

[00129] Thus, the UE generates a scheduled UL transmission 704 based on the allocated time and frequency resources.

[00130] FIG. 8 is a diagram illustrating MAC DL control message 800 in accordance with some embodiments. The control message 800 is included as a MAC payload or PDU, such as the PDU 500 described above. The control message 800 is provided as an example for illustrative purposes and it is appreciated that suitable variations are contemplated.

[00131 ] The control message 800 can be used with the framework 400 and variations thereof. The control message 800 is shown with a plurality of messages or parts designated 1 -6. The message 800, in this example, is shown using octal base notation (OCT) and as octal numbers.

[00132] The message 800 includes a UL grant in response to a retransmission failure of a grant-less UL transmission, such as described with regard to FIG. 7.

[00133] A timing advance command can be included or omitted, depending on whether synchronous or asynchronous UL transmission is to be used.

[00134] The message 800 is shown with a plurality of messages or parts designated

1 -6. Each row depicts a control message.

[00135] A first part (OCT 1 ) includes an indicator R and a timing advance command for asynchronous communication.

[00136] A second part (OCT 2) includes/continues the timing advance command for asynchronous communication and a full UE identity.

[00137] Third and fourth parts (OCT 3 and OCT 4) includes a UL grant for a UE device. The grant identifies time and frequency resources so that the UE device can generate a scheduled UL transmission for a previously failed grant-less UL

transmissions, such as shown in FIG. 7.

[00138] A fifth part (OCT 5) includes a UE specific signature for the UE device.

[00139] A sixth part (OCT 6) includes/continues the UE specific signature for the UE device.

[00140] Thus, this example control message 800 is for a scheduled UL transmission using NOMA after the UE device has failed beyond a threshold of repetitions to perform a grant-less uplink transmission. The control message 800 includes the timing advance command, the UL grant, the full UE identity, and the UE specific signature.

[00141 ] FIG. 9 is a diagram illustrating a messaging scenario 900 including a DL control message for a grant-less UE transmission in accordance with some

embodiments. The scenario 900 is provided for illustrative purposes and it is

appreciated that suitable variations are contemplated.

[00142] An eNB may detect preambles and/or DM-RS sequences from multiple UE devices successfully, but fail to decode a packet associated with the detected preamble ID or DM-RS sequence ID. If the decoding failure occurs more than a threshold number of times, a high loading condition may exist at the eNB. The high loading condition is where consistent and relatively strong interference is observed at the eNB receiver.

[00143] The scenario 900 includes a UE device and an eNB. The UE device generates a transmission and subsequent retransmissions for data. The transmissions are received by the eNB, however they result in decoding failures 702, as occurred in FIG. 7. The eNB may be able to detect preambles and/or DM-RS sequences for the transmission, but is unable to decode the associated packet due to loading conditions at the eNB.

[00144] In this example, the eNB again has a threshold of three (3). After the third transmission of the data, eNB generates a DL control message 903 that includes control information to facilitate transmission by the UE. It is appreciated that the repetition threshold can include other suitable values besides 3.

[00145] The control message and information includes loading and/or interference information. The UE uses the control information to identify suitable resources so that the eNB can receive/decode an UL data transmission.

[00146] In one example, the control message identifies a monitoring window in which the UE monitors for a DL transmission containing the control message and/or the eNB monitors for an UL transmission by the UE with the UL data. The window typically occurs between UL transmissions.

[00147] Thus, the UE generates a grant-less UL transmission 904 based on the allocated time and frequency resources.

[00148] FIG. 10 is a diagram illustrating resource allocations based on dynamic loading and/or interference in accordance with some embodiments. The allocations 1000 are provided for illustrative purposes and it is appreciated that suitable variations are contemplated.

[00149] Typically, a group of UE devices share a set of time and frequency resources as shown in a first allocation 1 001 . Here, the group of UEs includes UE #1 to UE #8. The group shares the same set of resources for grant-less UE transmissions. However, loading conditions and/or interference can be such that some or all of the grant-less UE transmissions fail.

[00150] As a result, an eNB initiates an action to mitigate the loading and/or interference. In one approach, the eNB includes an overloading indicator or back off indicator in a MAC subheader. The indicator can be similar to a random access response (RAR) and indicates that the eNB is experiencing relatively high loading and/or high interference. The UEs in the group are made aware of the overloading and can take a corrective action.

[00151 ] In another approach, the eNB can divide and/or reallocate resources to subgroups of the group of UEs to mitigate high loading and/or high interference and facilitate grant-less UL transmissions.

[00152] The eNB can determine high loading and/or high interference conditions based on measured loads, feedback from UE devices, and the like.

[00153] The eNB performs the reallocation in response to the determined high loading and/or high interference conditions. Further, the eNB specifies the reallocation of resources for the group of UEs in a control message. The reallocation segments the resources and/or modifies resources available and provides reallocated resources to two or more subsets of groups. Some UEs may be assigned a greater number of resources, which can lead to reduced interference.

[00154] An example of a suitable reallocation 1002 shows resources allocated to a first subset of the group and a second subset of group. The first subset includes UE#1 to UE#4 and the second subset includes UE#5 to UE#8. The reallocation is provided with the control message.

[00155] Upon receiving the reallocation 1002, the UEs utilize the reallocated resources for grant-less UL transmissions.

[00156] In another example, the eNB generates a control message that indicates one or more UEs of the group that are prohibited from transmitting using a grant-less UL transmission. The prohibited UEs can utilize another approach for UL transmissions, such as using a random access channel (RACH) procedure.

[00157] When multiple UEs transmit the data packet in the same physical resources, UL synchronization may or may not be present. For the UL asynchronous case, multiple UEs transmit the uplink packet following a DL reference timing without application of timing advance. As a result, timing offsets between UEs can be greater than a cyclic prefix. While for the UL synchronous case, timing offsets between UEs are within a cyclic prefix.

[00158] For the UL NOMA communication, a unified channel or frame structure design for both asynchronous and synchronous uplink transmission can be used. Note that additional functionality, including estimation of timing of arrival may be needed at eNB receiver for asynchronous NOMA transmission. [00159] In one example, a gap can be inserted between preamble and data transmissions to allow the eNB to estimate the timing of arrival from multiple UEs.

However, for synchronous UL transmission, this gap is not typically be needed.

[00160] In another example, independent resource pools are configured for synchronous and asynchronous UL NOMA transmissions. Thus, in the case when a UE applies timing advance (TA) for uplink NOMA transmission, it transmits the data in/using the synchronous resource pool.

[00161 ] Additionally, the asynchronous resource pool and the synchronous resource pool can be multiplexed in a time division multiplexing (TDM) or frequency division multiplexing (FDM) manner or a combination thereof. The resource pool partitioning can be configured by high layers in a cell specific or UE group specific manner via NR master information block (MIB), NR system information block (SIB) or radio resource control (RRC) signaling.

[00162] Additionally, for asynchronous UL NOMA, given that UE follows DL synchronization timing for uplink transmission and a large timing offset may be observed at eNB receiver, last OFDM symbol may be punctured to avoid the inter- symbol interference (ISI) or inter-subframe interference.

[00163] FIG. 1 1 is a diagram illustrating puncturing of a last symbol of a slot to mitigate interference for asynchronous UL transmissions 1 100 in accordance with some embodiments. The transmissions 1 100 are provided for illustrative purposes and it is appreciated that suitable variations are contemplated.

[00164] Puncturing can be used to remove parity bits to increase/modify the coding rate. Also, puncturing patterns can be used and shared between the UE device and node. Here, puncturing can mitigate interference for UL transmssions.

[00165] The transmissions 1 1 00 include a first slot 1 101 and a second slot 1 102. The transmissions are depicted with frequency resources along a y-axis from bottom to top and time resources along an x-axis from left to right.

[00166] Each slot is seven (7) OFDM symbols in length and includes a DM-RS in the middle. For the first slot 1 101 , the transmission is performed without puncturing. For the second slot, the last OFDM symbol is punctured to allow asynchronous UL NOMA transmission by the UE.

[00167] Although the design is shown with a slot length of 7 symbols, the design can be extended to other examples or implementations. In one example, the DM-RS is provided at a beginning of a slot to allow an eNB to estimate timing of transmission arrivals from different UE devices. [00168] While the methods described within this disclosure are illustrated in and described herein as a series of acts or events, it will be appreciated that the illustrated ordering of such acts or events are not to be interpreted in a limiting sense. For example, some acts may occur in different orders and/or concurrently with other acts or pre apart from those illustrated and/or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments of the description herein. Further, one or more of the acts depicted herein may be carried out in one or more separate acts and/or phases.

[00169] FIG. 12 is a flow diagram illustrating a method 1200 for dynamic loading control and/or interference management for mobile communication systems in accordance with some embodiments.

[00170] The method or process 1200 is described with reference to a UE device and a node, however it is appreciated that other device and/or nodes can be used. For example, the node can be other types of nodes, such as an eNB, gNB and the like. The method 1 200 can be implemented using the above systems, arrangements and variations thereof.

[00171 ] The node determines loading and interference conditions at block 1 204. The determination can at least partially be based on one or more prior grant-less UL transmissions. The determination can also include identified failed UE transmissions and the like. The determination can be specific to a UE device or be for a group of UE devices. The determination can also include determining a timing advance command for synchronous or asynchronous communication.

[00172] The node generates a control message for the UE device based on the determined loading and interference conditions at block 1206.

[00173] The control message includes control information to facilitate UL

transmissions for the UE device. The control information can include the determined loading and interference conditions/information, reallocation of resources based on the determined loading and interference conditions, a specific grant of UL transmission resources, asynchronous or synchronous timing information and the like.

[00174] The node generates and transmits a payload data unit (PDU) at block 1208 that includes the control message for the UE device. The PDU typically also includes a MAC header that includes a plurality of subheaders for one or more UE devices. The PDU also typically includes a plurality of downlink (DL) control messages. The plurality of subheaders include UE identity that associates the UE with one of the plurality of control messages. The PDU can also include padding. [00175] The plurality of subheaders include a subheader for the UE device that associates the device with the control message, which is one of the plurality of control messages.

[00176] The UE device receives and decodes the PDU at block 1 21 0 to obtain the control message for the UE device. In one example, the UE device decodes the PDU by identifying the subheader of the MAC header for the UE device based on the UE identity. Once identified, the subheader is used to obtain the control message from the plurality of control messages.

[00177] The UE device performs an UL transmission based on the control message at block 121 2. The UL transmission is grant-less, but can be a grant based UL

transmission based on the control message. The grant-less means that the UL transmission is not scheduled by the node. The UL transmission can also be non- orthogonal multiple access (NOMA) UL or OMA UL transmissions.

[00178] In one example, the UE device determines UL time and frequency resources that mitigate loading and interference based on the loading and interference information provided in the control message.

[00179] In another example, the UE device uses reallocated resources for its group of UEs or subgroup provided within the control message.

[00180] In another example, the UE device uses reallocated resources that have been segmented or separated from resources allocated for its group of UE devices.

[00181 ] In another example, the UE device uses timing information, such as timing advances, provided within the control message to facilitate timing of the UL

transmission.

[00182] In another example, one or more symbols or OFDM symbols are punctured to facilitate timing and mitigate interference and/or loading at the node.

[00183] The method 1200 can be repeated or re-utilized for additional channel estimation. It is appreciated that suitable variations of the method 1000 are

contemplated.

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

[00185] As it employed in the subject specification, the term "processor" can refer to substantially any computing processing unit or device including, but not limited to including, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology;

parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile devices. A processor may also be implemented as a combination of computing processing units.

[00186] In the subject specification, terms such as "store," "data store," data storage," "database," and substantially any other information storage component relevant to operation and functionality of a component and/or process, refer to "memory

components," or entities embodied in a "memory," or components including the memory. It is noted that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.

[00187] By way of illustration, and not limitation, nonvolatile memory, for example, can be included in a memory, non-volatile memory (see below), disk storage (see below), and memory storage (see below). Further, nonvolatile memory can be included in read only memory, programmable read only memory, electrically programmable read only memory, electrically erasable programmable read only memory, or flash memory.

Volatile memory can include random access memory, which acts as external cache memory. By way of illustration and not limitation, random access memory is available in many forms such as synchronous random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, Synchlink dynamic random access memory, and direct Rambus random access memory. Additionally, the disclosed memory components of systems or methods herein are intended to include, without being limited to including, these and any other suitable types of memory.

[00188] Examples can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.

[00189] Example 1 is an apparatus configured to be employed within a base station. The apparatus comprises baseband circuitry which includes a radio frequency (RF) interface and one or more processors. The one or more processors are configured to generate control information for loading and interference conditions, generate a control message using the control information for non-orthogonal multiple access (NOMA) uplink transmissions by one or more user equipment (UE) devices, generate a payload data unit (PDU) having the control message, and send the PDU to the RF interface for transmission to the one or more UE devices.

[00190] Example 2 includes the subject matter of Example 1 , including or omitting optional elements, where the base station is a next Generation NodeB.

[00191 ] Example 3 includes the subject matter of any of Examples 1 -2, including or omitting optional elements, where the one or more processors are configured to generate a UE identity for a first UE device of the one or more UE devices and include the UE identity within the PDU.

[00192] Example 4 includes the subject matter of any of Examples 1 -3, including or omitting optional elements, where the one or more processors are configured to include a scheduled uplink grant for a first UE device of the one or more UE devices.

[00193] Example 5 includes the subject matter of any of Examples 1 -4, including or omitting optional elements, where the one or more processors are configured to reallocate uplink transmission resources for the one or more UE devices.

[00194] Example 6 includes the subject matter of any of Examples 1 -5, including or omitting optional elements, where the reallocated uplink transmission resources are segmented for a plurality of subgroups of the one or more UE devices.

[00195] Example 7 includes the subject matter of any of Examples 1 -6, including or omitting optional elements, where the PDU includes a message header and a plurality of control messages. [00196] Example 8 includes the subject matter of any of Examples 1 -7, including or omitting optional elements, where the message header includes a plurality of subheaders, where each subheader is associated with one of the plurality of control messages and includes a unique UE identity.

[00197] Example 9 includes the subject matter of any of Examples 1 -8, including or omitting optional elements, whereone or more processors are configured to generate a timing advance command for a first UE device of the one or more UE devices based on the loading and interference conditions, and include the timing advance command with the control message.

[00198] Example 10 includes the subject matter of any of Examples 1 -9, including or omitting optional elements, where the timing advance is configured for synchronous communication or asynchronous communication with the first UE device.

Example 1 1 is an apparatus configured to be employed within a user equipment (UE) device comprising baseband circuitry. The baseband circuitry includes a radio frequency (RF) interface and one or more processors. The one or more processors are configured to obtain a payload data unit (PDU) from the RF interface as received from a base stations; decode the PDU to identify a subheader for the UE device; use the identified subheader to decode a control message from the PDU; generate uplink data based on the control message; and send the uplink data to the RF interface for a grant- less uplink non-orthogonal multiple access (NOMA) or orthogonal multiple access (OMA) transmission based on the control message to a base station.

[00199] Example 12 includes the subject matter of Example 1 1 , including or omitting optional elements, wherein the control message includes an acknowledgement (ACK) for a prior grant-less uplink NOMA transmission by the UE device.

[00200] Example 13 includes the subject matter of any of Examples 1 1 -12, including or omitting optional elements, wherein the control message includes loading and/or interference information of the base station.

[00201 ] Example 14 includes the subject matter of any of Examples 1 1 -13, including or omitting optional elements, where the control message includes reallocated uplink resources for the UE device.

[00202] Example 15 includes the subject matter of any of Examples 1 1 -14, including or omitting optional elements, where the control message includes granted uplink time and frequency resources.

[00203] Example 16 is one or more computer-readable media having instructions that, when executed, cause a base station to determine loading and interference conditions; generate a control message based on the determined loading and interference conditions, wherein the control message mitigates loading and interference at the base station for grant-less uplink transmissions by one or more UE devices; transmit the control message within a protocol data unit (PDU); and receive the uplink transmission in compliance with the transmitted control message.

[00204] Example 17 includes the subject matter of Example 16, including or omitting optional elements, where the PDU is transmitted within a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH).

[00205] Example 18 includes the subject matter of any of Examples 16-17, including or omitting optional elements, where the one or more computer-readable media further have instructions that, when executed, cause a base station to reallocate resource for uplink transmissions based on the determined loading conditions and identify the reallocated resources within the control message.

[00206] Example 19 includes the subject matter of any of Examples 16-18, including or omitting optional elements, where the uplink transmission is grant-less.

[00207] Example 20 includes the subject matter of any of Examples 16-19, including or omitting optional elements, where the uplink transmission is grant based and uses time and frequency resources as scheduled by the base station.

[00208] Example 21 is an apparatus configured to be employed within a user equipment (UE) device. The apparatus includes a means to receive a downlink transmission from a base station; a means to obtain a control message from the downlink transmission, where the control message includes loading and interference conditions for the base station; and a means to determine uplink time and frequency resources for an uplink transmission that mitigates loading and/or interference degradation for the uplink transmission based on the loading and interference conditions.

[00209] Example 22 includes the subject matter of Example 21 , including or omitting optional elements, further comprising a means to transmit the uplink transmission using the determined uplink time and frequency resources.

[00210] Example 23 includes the subject matter of any of Examples 21 -22, including or omitting optional elements, where the uplink transmission is a non-orthogonal multiple access (NOMA) transmission.

[00211 ] It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Combinations of the above should also be included within the scope of computer- readable media.

[00212] Various illustrative logics, logical blocks, modules, and circuits described in connection with aspects disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other

programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform functions described herein. A general-purpose processor can be a microprocessor, but, in the alternative, processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor can comprise one or more modules operable to perform one or more of the s and/or actions described herein.

[00213] For a software implementation, techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform functions described herein. Software codes can be stored in memory units and executed by processors. Memory unit can be implemented within processor or external to processor, in which case memory unit can be communicatively coupled to processor through various means as is known in the art. Further, at least one processor can include one or more modules operable to perform functions described herein.

[00214] Techniques described herein can be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA1800, etc. UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA. Further, CDMA1800 covers IS-1800, IS-95 and IS-856 standards. A TDMA system can implement a radio technology such as Global System for Mobile

Communications (GSM). An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.1 1 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.18, Flash-OFDML , etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on downlink and SC-FDMA on uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). Additionally, CDMA1 800 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). Further, such wireless communication systems can additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802. xx wireless LAN, BLUETOOTH and any other short- or long- range, wireless communication techniques.

[00215] Single carrier frequency division multiple access (SC-FDMA), which utilizes single carrier modulation and frequency domain equalization is a technique that can be utilized with the disclosed aspects. SC-FDMA has similar performance and essentially a similar overall complexity as those of OFDMA system. SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure. SC-FDMA can be utilized in uplink communications where lower PAPR can benefit a mobile terminal in terms of transmit power efficiency.

[00216] Moreover, various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data. Additionally, a computer program product can include a computer readable medium having one or more instructions or codes operable to cause a computer to perform functions described herein.

[00217] Communications media embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term "modulated data signal" or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[00218] Further, the actions of a method or algorithm described in connection with aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination thereof. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium can be coupled to processor, such that processor can read information from, and write information to, storage medium. In the alternative, storage medium can be integral to processor. Further, in some aspects, processor and storage medium can reside in an ASIC. Additionally, ASIC can reside in a user terminal. In the alternative, processor and storage medium can reside as discrete components in a user terminal. Additionally, in some aspects, the s and/or actions of a method or algorithm can reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product. [00219] The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

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

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

Claims

CLAIMS What is claimed is:

1 . An apparatus for a base station, comprising baseband circuitry having:

a radio frequency (RF) interface; and

one or more processors configured to:

generate control information for loading and interference conditions; generate a control message using the control information for non- orthogonal multiple access (NOMA) or orthogonal multiple access (OMA) uplink transmissions by one or more user equipment (UE) devices;

generate a payload data unit (PDU) having the control message; and send the PDU to the RF interface for transmission to the one or more UE devices.

2. The apparatus of claim 1 , wherein the base station is a next Generation NodeB.

3. The apparatus of claim 1 , wherein the one or more processors are configured to generate a UE identity for a first UE device of the one or more UE devices and include the UE identity within the PDU.

4. The apparatus of claim 1 , wherein the one or more processors are configured to include a scheduled uplink grant for a first UE device of the one or more UE devices.

5. The apparatus of claim 1 , wherein the one or more processors are configured to reallocate uplink transmission resources for the one or more UE devices.

6. The apparatus of claim 5, wherein the reallocated uplink transmission resources are segmented for a plurality of subgroups of the one or more UE devices.

7. The apparatus of any one of claims 1 -6, wherein the PDU includes a message header and a plurality of control messages.

8. The apparatus of claim 7, wherein the message header includes a plurality of subheaders, wherein each subheader is associated with one of the plurality of control messages and includes a unique UE identity.

9. The apparatus of any one of claims 1 -6, wherein one or more processors are configured to generate a timing advance command for a first UE device of the one or more UE devices based on the loading and interference conditions, and include the timing advance command with the control message.

10. The apparatus of claim 9, wherein the timing advance is configured for synchronous communication or asynchronous communication with the first UE device.

1 1 . An apparatus for user equipment (UE) device, comprising baseband circuitry having:

a radio frequency (RF) interface; and

one or more processors configured to:

obtain a payload data unit (PDU) from the RF interface as received from a base station;

decode the PDU to identify a subheader for the UE device; use the identified subheader to decode a control message from the PDU; generate uplink data based on the control message; and

send the uplink data to the RF interface for a grant-less uplink non- orthogonal multiple access (NOMA) or orthogonal multiple access (OMA) transmission based on the control message to the base station.

12. The apparatus of claim 1 1 , wherein the control message includes an

acknowledgement (ACK) for a prior grant-less uplink NOMA transmission by the UE device.

13. The apparatus of claim 1 1 , wherein the control message includes loading and/or interference information of the base station.

14. The apparatus of any one of claims 1 1 -13, wherein the control message includes reallocated uplink resources for the UE device.

15. The apparatus of claim 1 1 , wherein the control message includes granted uplink time and frequency resources.

16. One or more computer-readable media having instructions that, when executed, cause a base station to:

determine loading and interference conditions;

generate a control message based on the determined loading and interference conditions, wherein the control message mitigates loading and interference at the base station for grant-less uplink transmissions by one or more UE devices;

transmit the control message within a protocol data unit (PDU); and

receive the uplink transmission in compliance with the transmitted control message.

17. The computer-readable media of claim 16 wherein the PDU is transmitted within a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH).

18. The computer-readable media of any one of claims 16-17 comprising one or more computer-readable media having instructions that, when executed, further cause the base station to:

reallocate resource for uplink transmissions based on the determined loading conditions and identify the reallocated resources within the control message.

19. The computer-readable media of any one of claims 16-17, wherein the uplink transmission is grant-less.

20. The computer-readable media any one of claims 16-17, wherein the uplink transmission is grant based and uses time and frequency resources as scheduled by the base station.

21 . An apparatus for a user equipment (UE) device comprising:

a means to receive a downlink transmission from a base station;

a means to obtain a control message from the downlink transmission, where the control message includes loading and interference conditions for the base station; and a means to determine uplink time and frequency resources for an uplink transmission that mitigates loading and/or interference degradation for the uplink transmission based on the loading and interference conditions.

22. The apparatus of claim 21 , further comprising a means to transmit the uplink transmission using the determined uplink time and frequency resources.

23. The apparatus of any one of claims 21 -22, wherein the uplink transmission is a non-orthogonal multiple access (NOMA) transmission.