WO2018144899A1 - Downlink (dl) control channel configuration and monitoring for new radio (nr) ultra-reliable low latency communication (urllc) - Google Patents

Abstract

A network device such as an evolved NodeB (eNB) or next generation NodeB (gNB) can configure a set of user equipment (UE)-specific Search Spaces (USSs) to a UE, such as an Ultra-Reliable Low Latency Communication (URLLC) UE. The network device can dynamically / semi-statically re-configure USSs to decrease or eliminate resource blocking and a number of blind decoding attempts. The network device can utilize processing circuitry to generate a USS Resource Indicator (USSRI) that indicates the USS from among multiple USSs based on various predetermined criteria. The USSRI can be communicated to enable URLLCs based on resources derived from the indicated USS.

Description

DOWNLINK (DL) CONTROL CHANNEL CONFIGURATION AND MONITORING FOR NEW RADIO (NR) ULTRA-RELIABLE LOW LATENCY COMMUNICATION (URLLC)

REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No.

62/455,423 filed February 6, 2017, entitled "DL CONTROL CHANNEL

CONFIGURATION AND MONITORING FOR NR URLLC", the contents of which are herein incorporated by reference in their entirety.

FIELD

[0002] The present disclosure relates to wireless technology, and more specifically to techniques for employing downlink (DL) control channel configuration and monitoring for new radio (NR) ultra-reliable low latency communication (URLLC).

BACKGROUND

[0003] Various 5G requirements for Ultra-Reliable Low Latency Communication (URLLC) imply that 5G data communication should be able to achieve 1 0^"5 packet error probability and have up to 1 millisecond (ms) latency. The downlink (DL) and/or uplink (UL) URLLC transmissions may be scheduled by a serving Base Station (BS, evolved NodeB (eNB), new generation / new radio eN B (gNB), or other network stations / component). The BS is expected to provide user equipment (UE) with control information on the scheduled DL and/or UL URLLC transmission parameters (e.g. resources, modulation and coding scheme (MCS), etc). UEs receive

corresponding information carried in the downlink control information (DCI) transmitted by the BSs.

[0004] In long term evolution (LTE) systems the DCIs are transmitted using either physical downlink control channel (PDCCH) or enhanced PDCCH (EPDCCH). In general case, to allow BS scheduling flexibility, the UE does not necessarily have exact information on the time/frequency resources assigned for the particular DCI transmission from the BS to the UE. Instead, the UE has information on the set of possible transmission hypothesis (e.g., the control channel search space). For each hypothesis, the UE has information on the associated time/frequency resources (REs), ( E)PDCCH, aggregation level. The UE performs monitoring of its control channel search space in each or subset of DL subframes and performs blind detection of the possible candidate (E)PDCCH transmissions. Typically, the control channel search space includes a subset of resources (e.g. Control Channel Elements (CCEs)) from the full set of resources available for the control channel transmission. T he number of hypothesis can be kept rather limited in order to reduce DE implementation complexity and minimize the amount of blind control channel decoding, which can be performed at the UE.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIG. 1 is a block diagram illustrating an example user equipments (UEs) in a network with network components useable in connection with various aspects described herein.

[0006] FIG. 2 is a diagram illustrating example components of a device that can be employed in accordance with various aspects discussed herein.

[0007] FIG. 3 is a diagram illustrating example interfaces of baseband circuitry that can be employed in accordance with various aspects discussed herein.

[0008] FIG. 4 is a block diagram illustrating a system employable at a UE that facilitates USS reconfiguration in connection with URLLC transmission, according to various aspects described herein.

[0009] FIG. 5 is a block diagram illustrating a system employable at a BS (Base Station) that facilitates USS reconfiguration in connection with URLLC transmission from one or more UEs, according to various aspects described herein.

[0010] FIG. 6 is a diagram illustrating an example of control channel transmission with data slots per aggregation level, according to various aspects discussed herein.

[0011] FIG. 7 is an example simulation of blockage probability, according to various aspects discussed herein.

[0012] FIG. 8 is a diagram illustrating an example of control channel transmission with data slots per aggregation level, according to various aspects discussed herein.

[0013] FIG. 9 is a diagram illustrating an example of control channel transmission, according to various aspects discussed herein.

[0014] FIG. 10 is a diagram illustrating control channel transmissions per aggregation level, according to various aspects discussed herein.

[0015] FIG. 11 is a flow diagram of an example method employable at a UE that facilitates USS reconfiguration in connection with URLLC transmission, according to various aspects described herein, according to various aspects discussed herein. [0016] FIG. 12 is a flow diagram of an example method employable at a BS that facilitates USS reconfiguration in connection with URLLC transmission from one or more UEs.

DETAILED DESCRIPTION

[0017] 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. 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 (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user equipment (e.g., mobile phone, etc.) 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."

[0018] 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).

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

[0020] 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." Additionally, in situations wherein one or more numbered items are discussed (e.g., a "first X", a "second X", etc.), in general the one or more numbered items may be distinct or they may be the same, although in some situations the context may indicate that they are distinct or that they are the same.

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

[0022] In consideration of various deficiencies or solutions described herein, such as for minimizing blockage conditions and reducing resource blockage probabilities to ensure available control channel resources, the various search spaces (e.g., UE- specific search space, common search space, or the like) can be configured and utilized for URLLC devices by various mechanisms in order to minimize or eliminate blockage conditions as well as blind decoding attempts of candidates (e.g., physical resource blocks, resource elements, control channel elements (CCEs), or their corresponding resources for transmissions). [0023] In LTE, in particular, two general types of search space can be defined: common search space (CSS) and UE-specific search space (USS). The CSS is expected to be monitored by all UEs and the set of resources is also predef i ned / known to all UEs. The USS resources can be UE-specific so that they are designated and utilized by a particular identified UE, and depend on the UE- specific parameters uniquely assigned or designated to the particular identified UE, for example. USS could be defined in different ways, for example, according to section 9.1 .1 from 3GPP TS 36.213. In general cases, the USS assigned to different UEs associate with a network can at least partially overlap. In particular, if the eNB / gNB transmits control information to multiple UEs in one scheduling unit / transmission opportunity (TxOP) (e.g., a subframe in LTE, a slot / mini-slot in 5G New Radio (NR), or the like), a control channel blockage problem could arise. In particular, it can happen that the USS of two UEs overlap at least partially, and the eNB / gNB can only schedule a single UE transmission while transmission to another UE may not be possible due to a lack of available control channel resources (e.g., transmission is blocked). For LTE, one of the key design targets was minimization of the blockage probability under constraint of fixed number of blind decoding hypothesis decodings, detections, or attempts at decoding. In general, the blocking probability is kept at relatively low levels, but can be made lower in probability to enable the availability of resources based on one or more aspects / embodiments herein.

[0024] Mini slot can be used to indicate a transmission shorter than a slot, which can start anywhere within a slot and end anywhere within a slot, but finally there is no term in the specification called mini slot. There is another type of slot that is a flexible slot, but in this context it can be assumed that a mini slot is a transmission shorter than a slot, for example, ½ or ¼ of a slot.

[0025] For example, various aspects can include generating control channel search space configurations, which can enable minimizing the control channel blocking probability in applications to the URLLC or URLLC devices. In order to provide for protection of the control channel from blocking, for example, a dynamic / semi-static UE-specific search space re-configuration can be performed. A dynamic search space adjustment can be performed to minimize or prevent resource blocking and minimize number of blind decoding attempts.

[0026] Additionally or alternatively, the common search space for URLLC

transmissions can be utilized by generating an increase in the number of candidates for DCI transmission that could potentially decrease the number of blocking(s) or the probability of blockage, where the USS of at least two UEs overlap and the eNB / gNB is only able to schedule a single you a transmission while transmissions to other UEs are not possible due to a lack of available control resources (i.e., transmission become blocked or reduced in ability such as by a low signal to noise, interference, collision or the like communication measure of a predetermined threshold).

[0027] Additionally or alternatively, an implicit control search space size can be adjusted or an adjustment can be performed such as by a use rule, which may be predefined or not predefined, to extend the search space based on a DCI transmission blocking being detected by the network device or the eNB / gNB, for example.

Embodiments herein then enable a reduction of this probability of blockage or increase in blind decodings for transmissions on the network, and, thus, cause a more effective utilization of resources dedicated to DL control information transmission.

[0028] Additional aspects and details of the disclosure further described below with reference to figures.

[0029] Embodiments described herein can be implemented into a system using any suitably configured hardware and/or software. FIG. 1 illustrates an architecture of a system 1 00 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 102 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.

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

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

[0032] 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).

[0033] 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).

[0034] 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). 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.

[0035] 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 and downlink dynamic radio resource management and data packet scheduling, and mobility management.

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

[0037] 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 1 01 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. [0038] 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.

[0039] 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).

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

[0041] The RAN 1 10 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 .

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

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

[0044] The P-GW 123 can terminate an SGi interface toward a PDN. The P-GW 123 can route data packets between the EPC network 123 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 101 and 102 via the CN 120.

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

[0046] FIG. 2 illustrates example components of a 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 or a RAN node. 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 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).

[0047] 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. [0048] 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), sixth 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.

[0049] In addition, the memory 204G (as well as other memory components discussed herein, such as memory 430, memory 530 or the like) 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.

[0050] 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).

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

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

[0053] 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 bandpass 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.

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

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

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

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

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

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

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

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

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

[0063] 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 210. 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.

[0064] 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 210). [0065] 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.

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

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

[0068] 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 can not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.

[0069] 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 is totally unreachable to the network and can power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[0070] 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, described in further detail below.

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

[0072] 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 external 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 212).

[0073] Referring to FIG. 4, illustrated is a block diagram of a system 400 employable at a UE or other network device (e.g., loT device) that facilitates dynamic or semi-static configuration of the UE-specific search space, associated resources, related candidate / CCE numbers, corresponding aggregation layers or the like according to various aspects described herein. System 400 can include one or more processors 410 (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with FIG. 2 and/or FIG. 3) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection with FIG. 3), transceiver circuitry 420 (e.g., comprising part or all of RF circuitry 206, which can comprise transmitter circuitry (e.g., associated with one or more transmit chains) and/or receiver circuitry (e.g., associated with one or more receive chains) that can employ common circuit elements, distinct circuit elements, or a combination thereof), and a memory 430 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s) 410 or transceiver circuitry 420). In various aspects, system 400 can be included within a user equipment (UE). As described in greater detail below, system 400 can facilitate configuration for transmission URLLC UE transmission(s) involving adaptable configuration(s) of one or more of search space, control channel resources, CCEs, aggregation levels, time instances, indices or the like.

[0074] In various aspects discussed herein, signals and/or messages can be generated and output for transmission, and/or transmitted messages can be received and processed. Depending on the type of signal or message generated, outputting for transmission (e.g., by processor(s) 410, processor(s) 510, etc.) can comprise one or more of the following: generating a set of associated bits that indicate the content of the signal or message, coding (e.g., which can include adding a cyclic redundancy check (CRC) and/or coding via one or more of turbo code, low density parity-check (LDPC) code, tailbiting convolution code (TBCC), etc.), scrambling (e.g., based on a scrambling seed), modulating (e.g., via one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.), and/or resource mapping (e.g., to a scheduled set of resources, to a set of time and frequency resources granted for uplink transmission, etc.). Depending on the type of received signal or message, processing (e.g., by processor(s) 410, processor(s) 51 0, etc.) can comprise one or more of: identifying physical resources associated with the signal/message, detecting the signal/message, resource element group deinterleaving, demodulation, descrambling, and/or decoding.

[0075] Referring to FIG. 5, illustrated is a block diagram of a system 500 employable at a Base Station (BS), eNB, gNB or other network device that can enable generation and processing of configurable search spaces and related resources (e.g., times, time instances, CCEs, aggregation levels, or the like) for one or more UEs (e.g., URLLC UEs, or non-URLLC UEs) according to various aspects described herein. System 500 can include one or more processors 510 (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with FIG. 2 and/or FIG. 3) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection with FIG. 3), communication circuitry 520 (e.g., which can comprise circuitry for one or more wired (e.g., X2, etc.) connections and/or part or all of RF circuitry 206, which can comprise one or more of transmitter circuitry (e.g., associated with one or more transmit chains) or receiver circuitry (e.g., associated with one or more receive chains), wherein the transmitter circuitry and receiver circuitry can employ common circuit elements, distinct circuit elements, or a combination thereof), and memory 530 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s) 510 or communication circuitry 520). In various aspects, system 500 can be included within an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (Evolved Node B, eNodeB, or eNB), next generation Node B (gNodeB or gNB) or other base station or TRP (Transmit/Receive Point) in a wireless communications network. In some aspects, the processor(s) 510, communication circuitry 520, and the memory 530 can be included in a single device, while in other aspects, they can be included in different devices, such as part of a distributed architecture. As described in greater detail below, system 500 can facilitate configuration of UE(s) for transmission of URLLC UE transmission(s) involving adaptable configuration(s) of one or more of search space, control channel resources, CCEs, aggregation levels, time instances, indices or the like.

[0076] FIG. 6 illustrates an example control channel transmission 600 generated by the eNB / gNB 500 and processed by a UE (e.g., a URLLC UE 400) for transmission over a network managed or controlled by the eNB / gNB 500 with respect to different aggregation levels.

[0077] Control signaling can be utilized to support the transmission of the downlink and uplink transport channels (DL-SCH and UL-SCH). Control information for one or multiple UEs can be contained in a Downlink scheduling Control Information (DCI) message and is transmitted through the Physical Downlink Control Channel (PDCCH). DCI messages contain the following information: a. DL-SCH resource allocation (the set of resource blocks containing the DL-SCH) and modulation and coding scheme, which allows the UE to decode the DL-SCH; b. Transmit Power Control (TPC) commands for the Physical Uplink Control Channel (PUCCH) and UL-SCH, which adapt the transmit power of the UE to save power; c. Hybrid-Automatic Repeat Request (HARQ) information including the process number and redundancy version for error correction; d. MIMO precoding information. Depending on the purpose of DCI message, different DCI formats are defined.

[0078] Control channel elements can be found on each of the search spaces at every aggregation level with subframes zero to thirty-one, for example. A PDCCH can be transmitted on one or an aggregation of several consecutive control channel elements (CCEs), which can be according to the aggregation level assigned or corresponding to processing of the transmission. A CCE can be a group of nine consecutive resource-element groups (REGs). The number of CCEs used to carry a PDCCH can be controlled by the PDCCH format. A PDCCH format of 0, 1 , 2, or 3 corresponds to 1 , 2, 4, or 8 consecutive CCEs being allocated to one PDCCH, which can also be according to the aggregation level, for example.

[0079] In LTE two general types of search space are defined: common search space (CSS) and UE-specific search space (USS). The common search space (CSS) can be monitored by UEs (e.g., a URLLC UE 400 or other UE) associated with the network of the eNB / gNB 500, in which the set of resources can be known to all UEs of the network. The USS resources can be UE-specific and depend on the UE- specific parameters, such as by a UE identifier. T h e USS could be defined in different ways, for example, according to section 9.1 .1 from 3GPP TS 36.21 3. The resources can include bandwidth, frequency, timing, resource elements (REs), resource element groups (REGs), control channel resources (e.g., physical downlink channel (PDCCH) resources), CCE candidates, physical resource blocks (PRBs), physical resource block pairs, mapping resources, or other resources.

[0080] Additionally, the USS assigned for different UEs can at least partially overlap or be shared, where the eNB / gNB 500 transmits control information to multiple UEs (e.g., with a same UE id, or other identifier) in one scheduling unit (e.g., transmission opportunity, same subframe in LTE, or same slot / mini-slot in 5G New Radio (NR)) a control channel blockage. In these instances, a blockage problem can arise or increase in probability. In particular, the eNB / gNB 500 generate the USS of two or more U Es (e.g. , URLLC UEs 400 or non-URLLCs without the constraint parameters discussed above with 1 0^"5 packet error probability, up to 1 millisecond (ms) latency, etc.) that overlap at least partially in resources and can schedule a single UE transmission only, while transmission to another UE can become impossible (blocked) or reduced in ability due to a lack of available control resources.

[0081] For LTE communications implemented for the URLLCs by the eNB / gNB 500 one of the key design targets, in particular, can be a minimization of the blockage probability under the constrains of a fixed number of blind decoding hypothesis, decodings or attempts being made. As such, the eNB / gNB 500, in various aspects, can detect blockage and reduce the blockage probability or eliminate it by modifying the search space and generating a reconfiguration of the search spaces and related resources (e.g., aggregation level, time instances, resource indexes, CCEs or other control channel resources) on a per UE basis.

[0082] For the 3GPP NR systems it can be implemented with similar concepts utilizing (e.g., data control information (DCI), search space, blind decodings / blind decoding attempts, CSS, USS, or the like) to be reused with potentially a number of / various modifications. Assuming NR URLLC transmissions are sporadic over the network, the eNB / gNB 500 can schedule the NR URLCC UEs in a single time interval (e.g., a mini-slot, slot, or other scheduling unit). Due to low latency objectives

postponing packet transmission to other scheduling interval / TxOP (mini-slot or slot) could be unacceptable and lead to further packet loss. However, control channel blockage could negatively affect the URLLC and not allow the threshold target of key performance indicators (KPIs) (e.g., a 1 0^"5 packet error probability) to be satisfied. As such, the eNB / gNB 500 can minimize / eliminate control channel blocking probability for the URLLC.

[0083] For example, one or more various aggregation levels and associated resources to a UE-specific search space can be configured or modified dynamically or semi-statically based on configuration by the eNB / gNB 500. In particular, a dynamic / semi-static UE-search space can be modified / re-configured to be adjusted based on one or more quality measurements and a number of blind decoding attempts by the UEs (e.g., the URLLC UE 400) be reduced based on the modification / re-configuration of the search space (SS) to the UE 400. In one example, various USSs can be signaled and an indicator (e.g., USS Resource Indicator ( USSRI)) modified to initiate a change or change in use of one USS to a different USS with one or more different resources, CCEs, time instances, aggregation levels, start / stop indices, or the like). For example, aggregation levels 1 , 2, 4, or 8, as illustrated in the control channel transmission 600 of FIG. 6, or even aggregation level 16 (not shown) for NR. In one example, the UE less or more candidates based on the USSRI indicating a different aggregation level, for example, with more or less candidates associated.

[0084] In other aspects / embodiments, the CSS can be utilized for URLCC and an increase in the number of candidates can be configured for DCI transmission that could potentially decrease the number of decoding attempts by the UE / the number blockages / probability of blocking as discussed. [0085] In other aspects, implicit control search space size adjustment can be utilized by the eNB / gNB 500 based on a use rule, which can be predefined, or additionally or alternatively, not predefined, to extend the search space in a case of, or in response to, a detection by the eNB / gNB 500 or indication by the UE 400 to the eNB / gNB 500 of a DCI transmission blocking occurring.

[0086] Embodiments / aspects allow reducing the probability of DCI blocking and, as a result, can cause a more effective utilization of resources dedicated to DL control information transmissions by decreasing blockage (e.g., DCI blocking probability, or the like) and the number of blind decoding attempts or blind decodings at the URLLC UE.

[0087] Referring to FIG. 7, illustrated is a set of test results 700 of a DCI blocking probability that can be potentially detected or measured by either the eNB / gNB 500 or a URLLC UE 400 or other UE / network device. The results 700 demonstrate the DCI blocking probability observed in cases of DCI transmission in legacy and extended ( E) UE-specific search spaces defined, for example, according to the procedure described in Section 9.1 .1 of 3GPP TS 36.213, for example, or Section 10.1 of 3GPP TS 38.213 Release 15. It can be seen, that search space size extension in two times leads to significant reduction of DCI blocking probability.

[0088] In various aspects of the first example embodiment, whether to modify or reconfigure the USS can be dynamically / semi-statically configured by higher layers or can be dynamically indicated in the DCI (e.g., wherein the radio resource control (RRC) / medium access control (MAC) / DCI configuration can be generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410). For dynamic configuration, the transmission can refer to / add to the layer 1 signaling by the DCI, for example.

[0089] In an aspect, a USSRI indicator can be generated (e.g., by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410) to initiate a modification or re-configuration of the search space (e.g., URLLC USS). A USS Resource Indicator ( USSRI) can be utilized by the processor(s) 410 of the UE to derive the USS and associated resources, as well as operate as a trigger to initiate any change in a USS to another USS. Various USS configurations can be signaled to the UE, and the UE can change among these dynamically based on the USSRI. The USSRI can be altered or modified in response to a quality measurement or a channel quality detected by a network device (the eNB / gNB 500, or URLLC UE 400). Accordingly, the aggregation level can also be modified in response to the channel quality measurements. The aggregation level can thus also be indicated by an indicator such as the USSRI, and dynamically / semi-statically modified or re-configured based on a quality measurement or channel quality satisfying a predetermined threshold or not (e.g., a signal to noise ratio, or other channel measurement of quality or performance), which could indicate blockage.

[0090] The USSRI provides information to derive the USS resources used for further URLLC DCI monitoring. The UE monitors signaled USSRI information to derive the USS. This USS can then be changed dynamically upon the reception of the USSRI, which itself could be carried in a DCI carried by a CSS.

[0091] Alternatively or additionally, a dedicated physical channel can be used for USSRI transmission, which can be a separate signaling from the DCI itself. It could be received in between reception of control channel information for data something to reconfigure USSI, but without data. For example, a main purpose of the indication is to indicate or reconfigure such that it is monitored to acquire a DCI for rescheduling data. Two different DCI can be generated, for search space configuration and another for data scheduling itself, which may be received in different time instances. In order for the UE to understand which time instances USSRI applies, it should be associated with time instances, and the time instance itself could be also (re-)configured dynamically in USSRI or it could be derived in a next slot or mini slot after USSRI reception based on the USSRI, and so on, for example.

[0092] In an aspect, the USSRI can be transmitted independently from the actual DCI. In other words, DCI transmission does not imply USSRI transmission in the same mini-slot (or slot) and vice-versa, where it could be in the same mini-slot (or slot) based on one or more indicators of time instances or the DCI therein.

[0093] Further, the USSRI can be generated to indicate USS resources being used for a particular min-slot associated with a time instance of the USSRI reception. Alternatively or additionally, the USSRI can also indicate resources for other mini- slots not associated with the time instance of the USSRI reception. A mini-slot, in particular, can refer any portion within a slot of a transmission for a control channel transmission (e.g., a PDCCH, DCI, physical resources blocks, CCEs, bandwidth, frequency, duration of the transmission, time instances, aggregation level, candidates blocks or the like).

[0094] Further, the USSRI can be generated to indicate USS resources used for a particular mini-slot associated with time instance of USSRI reception. T h e USSRI may also indicate resource for other mini-slots not associated with the time instance of USSRI reception.

[0095] In an embodiment, by default the UE (e .g . , URLLC UE 400) can be configured to perform DCI monitoring in a certain USS. In response to the UE receiving the USSRI, the USS indicated in USSRI can either override the default USS or supplement the USS set (be appended to the previous assumption of the UE search space). For example, the UE 400 can operate on a pre-defined assumption on UE specific search space and once a USSRI is decoded, the UE 400 can then compose this set of control channel resources as a union of a previous resource set and the resource set that is indicated in the USSRI . As such, there can be two alternatives in operation, which can be trigger by or indicated further with the USSRI. The UE 400 can then perform DCI monitoring in the USS indicated in the USSRI in a particular mini-slot / set of forthcoming slot(s).

[0096] In another embodiment, a semi-static USS re-configuration or

modification can be implement via the RRC or MAC signaling (e.g., wherein the radio resource control (RRC) / medium access control (MAC) / DCI configuration can be generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410).

[0097] The UE-specific search space carries control information specific to a particular UE and is monitored by at least one UE in a cell (network). Unlike the common space search, the starting location of the UE-specific search space may be varied for each subframe or UE. The starting location of the UE-specific search space is determined in every subframe normally using a hash function, as specified in TS36.213, Clause 9, for example.

[0098] In the UE-specific search space the UE finds its PDCCH by monitoring a set of PDCCH candidates (a set of consecutive CCEs on which PDCCH could be mapped) in every subframe. If no cyclic redundancy check (CRC) error is detected when the UE uses its radio network temporary identifier (RNTI) to demask the CRC (16-bit value also refers as C-RNTI) on a PDCCH, the UE determines that PDCCH carries its own control information. The PDCCH candidate sets correspond to different PDCCH formats. There can be 4 PDCCH formats: 0, 1 , 2 or 3, for example. If the UE fails to decode any PDCCH candidates for a given PDCCH format it tries to decode candidates for other PDCCH formats. This process can be normally repeated for all possible PDCCH formats until all directed PDCCHs are successfully decoded in UE-specific search space.

[0099] In an aspect of semi-static USS modification, the USS configuration could be fixed for a UE (and without using any hashing function) and this could be assigned, for example, during an association procedure / operation with the network by the UE 400, for example, as well as re-configured / modified based on a decision by the base station (e.g., the eNB / gNB 500). This could be utilized, for example, in response to the eNB / gNB 500 having enough control channel capacity to assigned fixed orthogonal USS to each associated UE among UEs communicatively coupled / associated with the network of the network device 500, which can be scheduled simultaneously, for example. The eNB / gNB 500 detects which UEs are associating with it or communicatively coupled to it, and can assign the USS accordingly in a fixed or predefined manner within a UE- specific search space.

[00100] In another aspect, a set (one or more) of USSs can be extended or be processed as an extension of the first / previous USS. The set of USSs could be signalized to a UE during association to a BS and reconfigured based on BS decision. Each subset may be signaled as a vector of indexes of CCEs or as a bitmap of CCE in each aggregation level or as a start CCE index plus end CCE index. Alternatively, a predefined mapping of CCEs to search space sets could be defined and indexed for each aggregation level. In particular, the configuration of USS sets can either be U E-specific or UE-common. In the case of the UE specific configuration different UEs can be configured with different sets which may partially overlap or not overlap. Th e actual USS to be used in a particular control channel monitoring occasion / instance(s) can be derived from USSRI , which can be re-configured / modified based on predetermined criteria comprising one or more of: a blockage possibility being detected, such as when the sets of USS overlap at least partially, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs (e.g., where ULRLLC numbers are greater than non-URLLC UE numbers or vice versa), associated with a network managed by and communicatively coupled to the

processing circuitry 510 or the eNB / gNB 500.

[00101 ] Various approaches could be used for the eNB / gNB 500 to generate the search space set (SS set) generation. Referring to FIG. 8, illustrated is an example SS set 800 where each resource set is divided on non-orthogonal search spaces. The search space configuration is non-orthogonal within / in a set of orthogonal DCI transmission resource sets. The resources themselves are not orthogonal for a UE and between UEs. The resources available for control channel transmission can be divided into several orthogonal resource sets. When configured, the multiple sets can contain overlapping CCEs (e.g., as between non-orthogonal search space 1 and search space 2). For different UEs, the sets can be fully or partially overlapping, for example. In response to the UEs being scheduled within one instance of a control channel transmission (e.g., within one mini-slot), the eNB / gNB 500 can assign the USSRI to each UE that indicates the orthogonal subsets of the search spaces. In this case, the USSRI can simply encoded the search space index, Iss, via the processor 51 0 of the eNB / gNB 500 and be transmitted to the UE 400 for processing. The eNB / gNB 500 can then select Iss for each scheduled UE to be orthogonal to all other scheduled UEs.

[00102] In another approach for the eNB / gNB 500 to generate the search space set (SS set) generation. Referring to FIG. 9, illustrated is an example of orthogonal search space allocation 900 in a total resource set. Here, the eNB / gNB 500 can generate the search space orthogonalization inside a total pool of resources. The search space is orthogonal and the multiple sets can be configured to correspond to a UE or multiple UEs. With the sets being joined, the eNB / gNB 500 can switch different UEs between these sets. In this case, all resources available for control channel transmission can be divided into several orthogonal search spaces. In response to one or more UEs not needing to be scheduled within one or more instances of the control channel (e.g., within a mini-slot), the eNB / gNB 500 can assign the USSRI to each UE that indicates a different search space index, Iss.

[00103] Referring to FIG. 10, illustrated is an example search space configuration generated by the eNB / gNB 500 with an assumption or based on the channel / link condition or quality.

[00104] In an embodiment, the LTE the aggregation levels were and can be fixed for common search space and for USS. However, the eNB / gNB 500 can operate to configure the aggregation level per UE based on its general quality conditions or a channel quality measurement. An aggregation level can be mainly used to control redundancy of the control channel information, and thus, be used to control coverage of the control channel. Some UEs with bad coverage, or channel / link quality not satisfying a predetermined threshold (SNR, or other quality) could be configured with high aggregation levels (e.g., 8 or even 16, LTE up to 8, but NR could have up to 16). However, some UEs associated with the network or cell could be operating with good quality conditions could be scheduled by DCI in a small aggregation level, like 2 or 4.

[00105] When the eNB / gNB 500 applies this configurable aggregation level for search space there is more room to improve / decrease blockage probability so that the eNB / gNB 500 removes some aggregation level candidates from the UE, these candidate(s) can be used for additional decoding(s) in the search space. Thus, the blockage probability can be improved by, in NR, the aggregation level being

configurable, either per search space or per candidate.

[00106] If a UE has good connection (e.g., high signal-to- interference-plus-noise ratio (SINR), SNR, or the like quality indication / measurement) with serving base station (BS) (e.g., the eNB / gNB 500), then it can receive DCI in search spaces with low aggregation levels e.g., within search space with low number of resources per candidate. Otherwise, if the UE has or is detected as having a bad connection, one not satisfying a predetermined threshold, for example, to the BS or associated cell, then I can use the search space with a high(er) aggregation level or higher number of resources per candidate in a search space than a lower one. Thus, having information about link conditions or channel quality measurements, the eNB / gNB 500 can optimize the number of candidates in the USS in order to reduce blockage probability. That is, the BS can configure to each UE a subset of aggregation levels to be monitored based on the channel quality measurements, predetermined criteria or a combination.

[00107] In one example, as illustrated in FIG. 10 in the control channel transmission 1000, UE #2 has better channel conditions than UE #1 and it is assigned to monitor only aggregation level (AL) 1 and 2, while UE #1 is assigned to monitor AL 4 and 8. Given that a reduction of monitored aggregation levels reduces the total number of blind decoding candidates, the BS (e.g., eNB / gNB 500) can configure more CCE candidates within each aggregation level, thus effectively extending the search space and reducing the blockage while keeping the same number of blind decoding attempts.

[00108] In another embodiment of the semi-static configuring, a predefined mapping function can be used to determine the USS. For example, in LTE USS is dependent on a time index or indices (e.g., a frame index, a slot index, or dependent on some cell IDs or UE identifiers (IDs)). During association, the BS or the eNB / gNB 500 can signal to the UE to initiate association with the rule for search space reconfiguration, which could be dependent of several system specific parameters (e.g., a system frame number, a slot index, a cell ID, or the like), or UE-specific parameters 9e.g., a UE network temporary identity.

[00109] In other aspects, the eNB / gNB 500 can operate to utilize the CSS with USS extension. Instead of assigning some USS to UEs, randomizing them, and reducing blockage by a mechanism, all resources could alternatively be assigned to common search spaced. The UE could then attempt multiple candidates in the common search space. Here, the eNB / gNB 500 thus has full flexibility to distribute control channel resources between UEs, but this would be at the expense of UE monitoring flexibility because in this case the UE could be required to check many decoding candidates as blind decoding attempts. For example, as multiple UEs (e.g., 10) are actively associated / communicatively coupled to the network / cell of the eNB / gNB 500, then all of them would be scheduled in a common search space. Each one would perform one decoding by each UE to determine what common search space is assigned to the UE. Increasing the number of DCI blind decoding candidates (e.g., increase of the size of search space) may result in decrease of the blocking probability. Hence, an approach is to utilize common search space for URLLC DCI transmissions to all UEs (e.g., no USS). This approach is capable to minimize or prevent DCI blocking for maximum number of active users but, could impact number of blind decoding that each user should do.

[00110] In another embodiment, the search space could be increased based on a UE specific rule. IN this case if it is difficult / impossible to transmit DCI to a particular UE via the eNB / gNB 500 and associated circuitry, the BS can extend the USS by using the specific rule for extensions, which could be predefined at the UE 400. As an example of the rule for USS extension could be the LTE UE-specific search space changing of Y_K value specified in Section 9.1 .1 of 3GPP TS 36.213, for example, or Section 1 0.1 of 3GPP TS 38.213 Release 15 that leads to USS changing. This method increases USS and provides certain level of protection from DCI blocking.

[00111 ] In various such aspects, the resources herein can be configured for one or more UEs via higher layer signaling, for example, NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI) or radio resource control (RRC) signaling (e.g., generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410), wherein frequency hopping can be performed (e.g., by processor(s) 510 and communication circuitry 520 or by processor(s) 410 and transceiver circuitry 420, respectively) across these two configured BW parts for transmission (e.g., via communication circuitry 520 or transceiver circuitry 420) of DL (e.g., generated by processor(s) 51 0) or UL (e.g., generated by processor(s) 410). In various such aspects, a frequency hopping pattern across multiple BW parts can be configured by higher layers via MSI, RMSI, OSI, or RRC signaling or dynamically indicated in the DCI or a combination thereof (e.g., wherein the higher layer signaling and/or DCI generated by processor(s) 510, transmitted via communication circuitry 520, received via transceiver circuitry 420, and processed by processor(s) 410).

[00112] For each serving cell that a UE is configured to monitor PDCCH in a search space other than TypeO-PDCCH common search space, the UE is configured the following: - a number of search space sets by higher layer parameter search-space- config; - for each search space set in a control resource set p : an indication that the search space set is a common search space set or a UE-specific search space set by higher layer parameter Common-search-space-flag; a number of PDCCH candidates M_P'^L> per CCE aggregation level L by higher layer parameters Aggregation-level-1 ,

Aggregation-level-2, Aggregation-level-4, Aggregation-level-8, and Aggregation-level- 16, for CCE aggregation level 1 , CCE aggregation level 2, CCE aggregation level 4, CCE aggregation level 8, and CCE aggregation level 16, respectively; a PDCCH monitoring periodicity of k_p slots by higher layer parameter Monitoring-periodicity-

PDCCH-slot; a PDCCH monitoring offset of o_p slots, where o < o_p < k_p , by higher layer parameter Monitoring-offset-PDCCH-slot; a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the control resource set within a slot for PDCCH monitoring, by higher layer parameter Monitoring-symbols-PDCCH-within-slot.

[00113] A UE determines a PDCCH monitoring occasion from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. A PDCCH UE-specific search space s ^L at CCE aggregation level

L {i, 2, 4, 8, 16} is defined by a set of PDCCH candidates for CCE aggregation level L . If a UE is configured with higher layer parameter CrossCarrierSchedulingConfig for a serving cell the carrier indicator field value corresponds to the value indicated by CrossCarrierSchedulingConfig. [001 14] For a serving cell on which a UE monitors PDCCH candidates in a UE- specific search space, if the UE is not configured with a carrier indicator field, the UE shall monitor the PDCCH candidates without carrier indicator field. For a serving cell on which a UE monitors PDCCH candidates in a UE-specific search space, if a UE is configured with a carrier indicator field, the UE shall monitor the PDCCH candidates with carrier indicator field.

[001 15] In a first set of examples to the various aspects / embodiments herein, the below examples are envisioned further.

[001 16] Example 1 may include the method of downlink physical control channel monitoring configuration comprising of: configuring, by a BS, a set of UE-specific Search Spaces to a UE; transmitting, by a BS, a UE-specific Search Space Resource Indicator (US SRI); configuring, by a BS, of extended UE-specific search spaces (USS) for mapping of a UE-specific DCI; configuring, by a BS, of modifiable UE-specific search spaces (USS) for mapping of a UE-specific DCI.

[001 17] Example 2 may include the method of example 1 and/or some other example herein, wherein a set of USS is configured and signaled by a BS to a UE using an RRC message.

[001 18] Example 3 may include the method of example 2 and/or some other example herein, wherein a USS from the set of USSs is configured to a UE by the BS using USSRI.

[001 19] Example 4 may include the method of example 2 and/or some other example herein, wherein the US SRI carries an index of the USS in the configured set.

[00120] Example 5 may include the method of example I and/or some other example herein, wherein the USSRI indicates USS resources in the particular mini-slot or a slot associated with time instance of US SRI reception.

[00121 ] Example 6 may include the method of example 1 and/or some other example herein, wherein the USSRI indicates resource for other mini-slots or slots not associated with the time instance of US SRI reception.

[00122] Example 7 may include the method of example 1 and/or some other example herein, wherein USSRI is signaled by BS in a common search space DCI.

[00123] Example 8 may include the method of example 1 and/or some other example herein, wherein USSRI is signaled by BS in a USS DCI.

[00124] Example 9 may include the method of example 1 and/or some other example herein, wherein US SRI is signaled by a BS in Radio Resource Control message. [00125] Example 10 may include the method of example 1 and/or some other example herein, wherein US SRI is signaled by a BS in Radio Resource Control message.

[00126] Example 1 1 may include the method of examples 7 and 8 and/or some other example herein, wherein the DCI with US SRI is a first stage DCI.

[00127] Example 12 may include the method of example 10 and/or some other example herein, wherein the US SRI in the first stage DCI points to the control resource set of the second stage DCI.

[00128] Example 13 may include the method of example 1 and/or some other example herein, wherein the USS is extended by common search space.

[00129] Example 14 may include the method of example 1 and/or some other example herein, wherein USS is extended by specific rules is applied.

[00130] Example 15 may include the method of example 1 and/or some other example herein, wherein USS extension comprise of; detection of impossibility to transmit DCI to a UE due to DCI blockage on BS side; application of a rule for extending USS by adding new DCI transmission resources on BS side.

[00131 ] Example 16 may include the method of example 1 and/or some other example herein, wherein a set of monitored aggregation levels is configured to a UE based on its link quality.

[00132] Example 17 may include the method of example 1 and/or some other example herein, wherein USSRI is signaled by a BS in a MAC control element format.

[00133] Example 18 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1 -17, or any other method or process described herein.

[00134] Example 19 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1 -17, or any other method or process described herein.

[00135] Example 20 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1 -1 7, or any other method or process described herein.

[00136] Example 21 may include a method, technique, or process as described in or related to any of examples 1 -17, or portions or parts thereof. [00137] Example 22 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1 -17, or portions thereof.

[00138] Example 23 may include a method of communicating in a wireless network as shown and described herein.

[00139] Example 24 may include a system for providing wireless communication as shown and described herein.

[00140] Example 25 may include a device for providing wireless communication as shown and described herein.

[00141] 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 can occur in different orders and/or concurrently with other acts or events apart from those illustrated and/or described herein. In addition, not all illustrated acts can be required to implement one or more aspects or embodiments of the description herein. Further, one or more of the acts depicted herein can be carried out in one or more separate acts and/or phases.

[00142] Referring to FIG. 11 , illustrated is a flow diagram of an example method 1 100 employable at a UE that facilitates USS adaptation and associated resources by reconfiguration or modification thereof and an associated indictor. bandwidth adaptation and/or frequency hopping in connection with URLLC transmission, according to various aspects described herein, according to various aspects discussed herein. In other aspects, a machine readable medium can store instructions associated with method 1 100 that, when executed, can cause a UE to perform the acts of method 1 100.

[00143] At 1 1 10, the process flow 1 100 includes processing a plurality of user equipment (UE)-specific search spaces (USSs) corresponding to different resources for a control channel transmission.

[00144] At 1 120, the process flow 1 100 processes a UE-specific Search Space Resource Indicator (USSRI) that is based on one or more predetermined criteria.

[00145] At 1 130, the process flow 1 100 determines a USS of the plurality of USSs based on the USSRI. [00146] At 1 140, the process flow 1 100 generates a transmission based on the USS.

[00147] In other aspects, the process flow 1 100 can include an operation to modify, or supplement, the USS associated with an Ultra-Reliable Low Latency

Communication (URLLC) to a different USS of the plurality of different USSs in response to processing a different USSRI that is based on a change in the one or more predetermined criteria.

[00148] In other aspects, the process flow 1 100 can include an operation to process the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel independent of the DCI.

[00149] In other aspects, the process flow 1 100 can include an operation to determine an index of control channel common elements (CCEs) in the USS, or a bitmap of the CCEs, associated with an aggregation level.

[00150] In other aspects, the process flow 1 100 can include an operation to modify one or more aggregation levels based on the USSRI and one or more channel quality measurements to one or more higher aggregation levels or one or more lower aggregation levels with less CCE candidates than the one or more higher aggregation levels.

[00151 ] Additionally or alternatively, method 1 1 00 can include one or more other acts described herein in connection with transmitting entity aspects of system 400

[00152] Referring to FIG. 12, illustrated is a flow diagram of an example method 1200 employable at a BS that facilitates USS adaptation and associated resources by reconfiguration or modification thereof and an associated indictor, according to various aspects discussed herein. In other aspects, a machine readable medium can store instructions associated with method 1 200 that, when executed, can cause a BS (e.g., eNB, gNB, etc.) to perform the acts of method 1200.

[00153] At 1210, the process flow 1200 includes generating a user equipment (UE)- specific search space (USS) associated with resources for control channel

transmission.

[00154] At 1220, the process flow 1200 includes generating a UE-specific Search Space Resource Indicator (USSRI) that indicates the USS from among a plurality of USSs associated with different resources based on one or more predetermined criteria. [00155] At 1230, the process flow 1200 includes communicating the USSRI for an Ultra-Reliable Low Latency Communication (URLLC).

[00156] In other aspects, the process flow 1 100 can include modifying the USS to a different USS of the plurality of different USSs based on a change in the one or more predetermined criteria, wherein the one or more predetermined criteria comprises at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network; re-configuring the USSRI based on the different USS; and communicating the re-configured USSRI to initiate a change from the USS to the different USS.

[00157] In other aspects, the process flow 1 100 can include generating the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel with or separate from the DCI.

[00158] In other aspects, the process flow 1 100 can include generating the USSRI to indicate one or more indices of control channel common elements (CCEs) in the USS associated with one or more aggregation levels; and indicating, via the USSRI, the one or more aggregation levels to be monitored by a URLLC UE.

[00159] In other aspects, the process flow 1 100 can include re-configuring the one or more aggregation levels based on a channel quality measurement associated with the URLLC UE by reducing the one or more aggregation levels to one or more lower aggregation levels or increasing the one or more aggregation levels to one or more higher aggregation levels comprising more CCE candidates than the one or more lower aggregation levels.

[00160] Additionally or alternatively, method 1200 can include one or more other acts described herein in connection with transmitting entity aspects of system 500.

[00161 ] 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 can also be implemented as a combination of computing processing units.

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

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

[00164] 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 (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) 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.

[00165] In a second set of examples to the various aspects / embodiments herein, the below examples are envisioned further.

[00166] Example 1 is an apparatus configured to be employed in a next generation Node B (gNB), comprising: processing circuitry configured to: generate a plurality of user equipment (UE)-specific search spaces (USSs) corresponding to different resources for a control channel transmission; determine a USS of the plurality of USSs based on one or more predetermined criteria; generate a UE-specific Search Space Resource Indicator (USSRI) of the USS based on the one or more predetermined criteria; and a radio frequency (RF) interface, configured to provide, to RF circuitry, data for transmission of the USSRI.

[00167] Example 2 includes the subject matter of Example 1 , wherein the one or more predetermined criteria comprises at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra- Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a network managed by and communicatively coupled to the processing circuitry.

[00168] Example 3 includes the subject matter of any one of Examples 1 -2, including or omitting any elements as optional, wherein the processing circuitry is further configured to modify the USS associated with an Ultra-Reliable Low Latency

Communication (URLLC) of a user equipment (UE) to a different USS of the plurality of different USSs based on a change in the one or more predetermined criteria.

[00169] Example 4 includes the subject matter of any one of Examples 1 -3, including or omitting any elements as optional, wherein the processing circuitry is further configured to determine an increase in a blockage probability in response to one or more USS resources of the control channel transmission at least partially overlapping in assignment to different UEs within a subframe, a slot, a mini-slot, or a plurality of orthogonal frequency-division multiplexing (OFDM) symbols, and modify the USS and the USSRI based on the one or more USS resources.

[00170] Example 5 includes the subject matter of any one of Examples 1 -4, including or omitting any elements as optional, wherein the processing circuitry is further configured to enable about a 1 0^"5 error probability and up to about a 1 millisecond latency for a URLLC based on the control channel transmission in response to modifying the USS or re-configuring the USSRI to enable a derivation of different USS resources.

[00171 ] Example 6 includes the subject matter of any one of Examples 1 -5, including or omitting any elements as optional, wherein the processing circuitry is further configured to generate the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel independent of the DCI.

[00172] Example 7 includes the subject matter of any one of Examples 1 -6, including or omitting any elements as optional, wherein the processing circuitry is further configured to extend or modify the USS, and enable a mapping of a UE-specific DCI based on the extended or modified USS.

[00173] Example 8 includes the subject matter of any one of Examples 1 -7, including or omitting any elements as optional, wherein the processing circuitry is further configured to generate a communication with the plurality of USSs, indicate the USS of the plurality of USSs via the USSRI, and modify the USS to a different USS of the plurality of USSs by modifying the USSRI.

[00174] Example 9 includes the subject matter of any one of Examples 1 -8, including or omitting any elements as optional, wherein the processing circuitry is further configured to generate the USSRI to indicate an index of control channel common elements (CCEs) in the USS, or a bitmap of the CCEs, associated with an aggregation level.

[00175] Example 10 includes the subject matter of any one of Examples 1 -9, including or omitting any elements as optional, wherein the processing circuitry is further configured to modify one or more aggregation levels to be monitored by a URLLC UE differently than a non-URLLC UE, and initiate a monitoring of the one or more modified aggregation levels by the URLLC UE via the control channel transmission.

[00176] Example 1 1 includes the subject matter of any one of Examples 1 -10, including or omitting any elements as optional, wherein the processing circuitry is further configured to modify the one or more aggregation levels based on a predetermined threshold of one or more channel quality measurements associated with the URLLC UE by reducing the one or more aggregation levels to one or more lower aggregation levels or increasing the one or more aggregation levels to one or more higher aggregation levels comprising more CCE candidates than the one or more lower aggregation levels. [00177] Example 12 includes the subject matter of any one of Examples 1 -1 1 , including or omitting any elements as optional, wherein the processing circuitry is further configured to communicate the USSRI in a radio resource control (RRC) message, via a physical (PHY) layer, or a media access control (MAC) layer.

[00178] Example 13 is an apparatus configured to be employed in a user equipment (UE), comprising: processing circuitry configured to: process a plurality of user equipment (UE)-specific search spaces (USSs) corresponding to different resources for a control channel transmission; process a UE-specific Search Space Resource

Indicator (USSRI); determine a USS of the plurality of USSs based on the USSRI; and a radio frequency (RF) interface, configured to provide, to RF circuitry, data for transmission based on the USSRI.

[00179] Example 14 includes the subject matter of Example 13, including or omitting any elements as optional, wherein the processor circuitry is further configured to modify, or supplement, the USS associated with an Ultra-Reliable Low Latency Communication (URLLC) to a different USS of the plurality of different USSs in response to processing a different USSRI that is based on a change in one or more predetermined criteria comprising at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network or serving cell.

[00180] Example 15 includes the subject matter of any one of Examples 1 3-14, including or omitting any elements as optional, wherein the processor circuitry is further configured to derive different USS resources from a change in a different USSRI being received than the USS.

[00181 ] Example 16 includes the subject matter of any one of Examples 1 3-15, including or omitting any elements as optional, wherein the processing circuitry is further configured to process the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel independent of the DCI.

[00182] Example 17 includes the subject matter of any one of Examples 1 3-16, including or omitting any elements as optional, wherein the processing circuitry is further configured to process the USSRI to acquire a DCI and time instances for rescheduling data, wherein the time instances are independent of a time instance of USSRI reception. [00183] Example 18 includes the subject matter of any one of Examples 1 3-17, including or omitting any elements as optional, wherein the processing circuitry is further configured to determine an index of control channel common elements (CCEs) in the USS, or a bitmap of the CCEs, associated with an aggregation level.

[00184] Example 19 includes the subject matter of any one of Examples 1 3-18, including or omitting any elements as optional, wherein the processing circuitry is further configured to modify one or more aggregation levels based on the USSRI and one or more channel quality measurements to one or more higher aggregation levels or one or more lower aggregation levels with less CCE candidates than the one or more higher aggregation levels.

[00185] Example 20 is a computer readable storage medium storing executable instructions that, in response to execution, cause one or more processors of a user equipment (UE) to perform operations comprising: monitoring a physical downlink control channel (PDCCH) in a search space in a control resource set; processing a number of user equipment (UE)-specific search space (USS) sets based on one or more higher layer parameters with an indication; and configuring or monitoring a USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

[00186] Example 21 includes the subject matter of Example 20, including or omitting any elements as optional, wherein the operations further comprise: configuring the USS set to another USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

[00187] Example 22 includes the subject matter of any one of Examples 20-21 , including or omitting any elements as optional, wherein the operations further comprise: configuring for the USS set with a number of PDCCH candidates corresponding to a control channel element aggregation level by the one or more higher layer parameters.

[00188] Example 23 includes the subject matter of any one of Examples 20-22, including or omitting any elements as optional, wherein the one or more higher layer parameters comprises at least one of: an Aggregation-level-1 , Aggregation-level-2, Aggregation-level-4, Aggregation-level-8, and Aggregation-level-16, for CCE

aggregation level 1 , CCE aggregation level 2, CCE aggregation level 4, CCE

aggregation level 8, and CCE aggregation level 1 6, respectively.

[00189] Example 24 includes the subject matter of any one of Examples 20-23, including or omitting any elements as optional, wherein the operations further comprise: processing a UE-specific Search Space Resource Indicator (USSRI) that is configured to indicate which USS set of the number of USS sets to monitor in response to a change of one or more predetermined criteria comprising at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network or serving cell.

[00190] Example 25 is a computer readable storage medium storing executable instructions that, in response to execution, cause one or more processors of an evolved NodeB (eNB) or a next generation NodeB (gNB) to perform operations comprising: generating a user equipment (UE)-specific search space (USS) associated with resources for control channel transmission; generating an indication that indicates the USS from among a plurality of USSs associated with different control channel resources; and communicating the indication.

[00191 ] Example 26 includes the subject matter of any one of Examples 25-26, including or omitting any elements as optional, wherein the operations further comprise: generating the indication to indicate one or more control channel common elements (CCEs) in the USS associated with one or more aggregation levels; and

communicating, via the indication, the one or more aggregation levels to be monitored by a UE; and configuring the UE to monitor the USS with a number of control channel candidates based on the one or more aggregation levels of the indication.

[00192] Example 27 includes the subject matter of any one of Examples 25-27, including or omitting any elements as optional, wherein the operations further comprise: re-configuring the one or more aggregation levels associated with the UE by reducing the one or more aggregation levels to one or more lower aggregation levels or increasing the one or more aggregation levels to one or more higher aggregation levels comprising more control channel candidates than the one or more lower aggregation levels.

[00193] Example 28 includes the subject matter of any one of Examples 25-27, including or omitting any elements as optional, wherein the operations further comprise: modifying the USS to a different USS of the plurality of different USSs based on a change in one or more predetermined criteria, wherein the one or more predetermined criteria comprises at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency

Communication (URLLC) UEs to non-URLLC UEs, associated with a same network; re-configuring the indication based on the different USS; and communicating the reconfigured indication to initiate a change from the USS to the different USS, wherein the indication comprises a UE-specific Search Space Resource Indicator (USSRI).

[00194] Example 29 includes the subject matter of any one of Examples 25-28, including or omitting any elements as optional, wherein the operations further comprise: generating the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel with or separate from the DCI.

[00195] Example 30 is an apparatus of a user equipment (UE) comprising: means for monitoring a physical downlink control channel (PDCCH) in a search space in a control resource set; means for processing a number of user equipment (UE)-specific search space (USS) sets based on one or more higher layer parameters with an indication; and means for configuring a USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

[00196] Example 31 includes the subject matter of Example 30, including or omitting any elements as optional, further comprising: means for configuring the USS set to another USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

[00197] Example 32 includes the subject matter of any one of Examples 30-31 , including or omitting any elements as optional, further comprising: means for configuring for the USS set with a number of PDCCH candidates corresponding to a control channel element aggregation level by the one or more higher layer parameters.

[00198] Example 33 includes the subject matter of any one of Examples 30-32, including or omitting any elements as optional, wherein the one or more higher layer parameters comprises at least one of: an Aggregation-level-1 , Aggregation-level-2, Aggregation-level-4, Aggregation-level-8, and Aggregation-level-16, for CCE

aggregation level 1 , CCE aggregation level 2, CCE aggregation level 4, CCE

aggregation level 8, and CCE aggregation level 1 6, respectively.

[00199] Example 34 includes the subject matter of any one of Examples 30-33, including or omitting any elements as optional, further comprising: means for processing a UE-specific Search Space Resource Indicator (USSRI) that is configured to indicate which USS set of the number of USS sets to monitor in response to a change of one or more predetermined criteria comprising at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra- Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network or serving cell.

[00200] Example 35 is an apparatus of an evolved NodeB (eNB) or a next generation NodeB (gNB) comprising: means for generating a user equipment (UE)-specific search space (USS) associated with resources for control channel transmission; means for generating an indication that indicates the USS from among a plurality of USSs associated with different control channel resources; and means for communicating the indication.

[00201 ] Example 36 includes the subject matter of Example 35, including or omitting any elements as optional, further comprising: means for generating the indication to indicate one or more control channel common elements (CCEs) in the USS associated with one or more aggregation levels; and means for communicating, via the indication, the one or more aggregation levels to be monitored by a UE; and means for configuring the UE to monitor the USS with a number of control channel candidates based on the one or more aggregation levels of the indication.

[00202] Example 37 includes the subject matter of any one of Examples 35-36, including or omitting any elements as optional, further comprising: means for reconfiguring the one or more aggregation levels associated with the UE by reducing the one or more aggregation levels to one or more lower aggregation levels or increasing the one or more aggregation levels to one or more higher aggregation levels comprising more control channel candidates than the one or more lower aggregation levels.

[00203] Example 38 includes the subject matter of any one of Examples 35-37, including or omitting any elements as optional, further comprising: means for modifying the USS to a different USS of the plurality of different USSs based on a change in one or more predetermined criteria, wherein the one or more predetermined criteria comprises at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network; means for reconfiguring the indication based on the different USS; and means for communicating the re-configured indication to initiate a change from the USS to the different USS, wherein the indication comprises a UE-specific Search Space Resource Indicator (USSRI).

[00204] Example 39 includes the subject matter of any one of Examples 35-38, including or omitting any elements as optional, further comprising: means for generating the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel with or separate from the DCI.

[00205] Example 40 is an apparatus configured to be employed in a next generation Node B (gNB), comprising: a memory interface comprising an indication; one or more processors configured to: monitor a physical downlink control channel (PDCCH) in a search space in a control resource set; process a number of user equipment (UE)- specific search space (USS) sets based on one or more higher layer parameters with an indication; and configure or monitor a USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

[00206] Example 41 includes the subject matter of Example 40, including or omitting any elements as optional, wherein the one or more processors are further configured to: configure the USS set to another USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

[00207] Example 42 includes the subject matter of any one of Examples 40-41 , including or omitting any elements as optional, wherein the one or more processors are further configured to: configure for the USS set with a number of PDCCH candidates corresponding to a control channel element aggregation level by the one or more higher layer parameters.

[00208] Example 43 includes the subject matter of any one of Examples 40-42, including or omitting any elements as optional, wherein the one or more higher layer parameters comprises at least one of: an Aggregation-level- 1 , Aggregation-level-2, Aggregation-level-4, Aggregation-level-8, and Aggregation-level- 16, for CCE

aggregation level 1 , CCE aggregation level 2, CCE aggregation level 4, CCE

aggregation level 8, and CCE aggregation level 1 6, respectively.

[00209] Example 44 includes the subject matter of any one of Examples 40-43, including or omitting any elements as optional, wherein the one or more processors are further configured to: process a UE-specific Search Space Resource Indicator (USSRI) that is configured to indicate which USS set of the number of USS sets to monitor in response to a change of one or more predetermined criteria comprising at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non- URLLC UEs, associated with a same network or serving cell. [00210] Example 45 is an apparatus configured to be employed in a next generation Node B (gNB), comprising: a memory interface comprising an indication; one or more processors configured to: generate a user equipment (UE)-specific search space (USS) associated with resources for control channel transmission; generate an indication that indicates the USS from among a plurality of USSs associated with different control channel resources; and encode a communication with the indication.

[00211] Example 46 includes the subject matter of Example 45, wherein the one or more processors are further configured to: generate the indication to indicate one or more control channel common elements (CCEs) in the USS associated with one or more aggregation levels; and communicate, via the indication, the one or more aggregation levels to be monitored by a UE; and configure the UE to monitor the USS with a number of control channel candidates based on the one or more aggregation levels of the indication.

[00212] Example 47 includes the subject matter of any one of Examples 45-46, including or omitting any elements as optional, wherein the one or more processors are further configured to: re-configure the one or more aggregation levels associated with the UE by reducing the one or more aggregation levels to one or more lower aggregation levels or increasing the one or more aggregation levels to one or more higher aggregation levels comprising more control channel candidates than the one or more lower aggregation levels.

[00213] Example 48 includes the subject matter of any one of Examples 45-46, including or omitting any elements as optional, wherein the one or more processors are further configured to: modify the USS to a different USS of the plurality of different USSs based on a change in one or more predetermined criteria, wherein the one or more predetermined criteria comprises at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra- Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network; re-configure the indication based on the different USS; and communicate the re-configured indication to initiate a change from the USS to the different USS, wherein the indication comprises a UE-specific Search Space Resource Indicator (USSRI).

[00214] Example 49 includes the subject matter of any one of Examples 45-47, including or omitting any elements as optional, wherein the one or more processors are further configured to: generate the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel with or separate from the DCI.

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

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

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

[00218] 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, 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, CDMA1800 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.

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

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

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

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

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

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

[00225] 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 can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given or particular application.

Claims

CLAIMS What is claimed is:

1 . An apparatus configured to be employed in a next generation Node B (gNB), comprising:

processing circuitry configured to:

generate a plurality of user equipment (UE)-specific search spaces (USSs) corresponding to different resources for a control channel transmission;

determine a USS of the plurality of USSs based on one or more predetermined criteria; and

generate a UE-specific Search Space Resource Indicator (USSRI) of the USS based on the one or more predetermined criteria; and

a radio frequency (RF) interface, configured to provide, to RF circuitry, data for transmission of the USSRI.

2. The apparatus of claim 1 , wherein the one or more predetermined criteria comprises at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a network managed by and communicatively coupled to the processing circuitry.

3. The apparatus of any one of claims 1 -2, wherein the processing circuitry is further configured to modify the USS associated with an Ultra-Reliable Low Latency Communication (URLLC) of a user equipment (UE) to a different USS of the plurality of different USSs based on a change in the one or more predetermined criteria.

4. The apparatus of any one of claims 1 -3, wherein the processing circuitry is further configured to determine an increase in a blockage probability in response to one or more USS resources of the control channel transmission at least partially overlapping in assignment to different UEs within a subframe, a slot, a mini-slot, or a plurality of orthogonal frequency-division multiplexing (OFDM) symbols, and modify the USS and the USSRI based on the one or more USS resources.

5. The apparatus of claim 4, wherein the processing circuitry is further configured to enable about a 1 0^"5 error probability and up to about a 1 millisecond latency for a URLLC based on the control channel transmission in response to modifying the USS or re-configuring the USSRI to enable a derivation of different USS resources.

6. The apparatus of any one of claims 1 -5, wherein the processing circuitry is further configured to generate the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel independent of the DCI.

7. The apparatus of any one of claims 1 -6, wherein the processing circuitry is further configured to extend or modify the USS, and enable a mapping of a UE- specific DCI based on the extended or modified USS.

8. The apparatus of any one of claims 1 -7, wherein the processing circuitry is further configured to generate a communication with the plurality of USSs, indicate the USS of the plurality of USSs via the USSRI, and modify the USS to a different USS of the plurality of USSs by modifying the USSRI.

9. The apparatus of any one of claims 1 -8, wherein the processing circuitry is further configured to generate the USSRI to indicate an index of control channel common elements (CCEs) in the USS, or a bitmap of the CCEs, associated with an aggregation level.

10. The apparatus of any one of claims 1 -9, wherein the processing circuitry is further configured to modify one or more aggregation levels to be monitored by a URLLC UE differently than a non-URLLC UE, and initiate a monitoring of the one or more modified aggregation levels by the URLLC UE via the control channel

transmission.

1 1 . The apparatus of claim 10, wherein the processing circuitry is further configured to modify the one or more aggregation levels based on a predetermined threshold of one or more channel quality measurements associated with the URLLC UE by reducing the one or more aggregation levels to one or more lower aggregation levels or increasing the one or more aggregation levels to one or more higher aggregation levels comprising more CCE candidates than the one or more lower aggregation levels.

12. The apparatus of claim 10, wherein the processing circuitry is further configured to communicate the USSRI in a radio resource control (RRC) message, via a physical (PHY) layer, or a media access control (MAC) layer.

13. An apparatus configured to be employed in a user equipment (UE), comprising: processing circuitry configured to:

process a plurality of user equipment (UE)-specific search spaces (USSs) corresponding to different resources for a control channel transmission;

process a UE-specific Search Space Resource Indicator (USSRI); and determine a USS of the plurality of USSs based on the USSRI ; and a radio frequency (RF) interface, configured to provide, to RF circuitry, data for transmission based on the USSRI.

14. The apparatus of claim 13, wherein the processor circuitry is further configured to modify, or supplement, the USS associated with an Ultra-Reliable Low Latency Communication (URLLC) to a different USS of the plurality of different USSs in response to processing a different USSRI that is based on a change in one or more predetermined criteria comprising at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network or serving cell.

15. The apparatus of any one of claims 13-14, wherein the processor circuitry is further configured to derive different USS resources from a change in a different USSRI being received than the USS.

16. The apparatus of any one of claims 13-15, wherein the processing circuitry is further configured to process the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel independent of the DCI.

17. The apparatus of any one of claims 13-16, wherein the processing circuitry is further configured to process the USSRI to acquire a DCI and time instances for rescheduling data, wherein the time instances are independent of a time instance of USSRI reception.

18. The apparatus of any one of claims 13-17, wherein the processing circuitry is further configured to determine an index of control channel common elements (CCEs) in the USS, or a bitmap of the CCEs, associated with an aggregation level.

19. The apparatus of any one of claims 13-18, wherein the processing circuitry is further configured to modify one or more aggregation levels based on the USSRI and one or more channel quality measurements to one or more higher aggregation levels or one or more lower aggregation levels with less CCE candidates than the one or more higher aggregation levels.

20. A computer readable storage medium storing executable instructions that, in response to execution, cause one or more processors of a user equipment (UE) to perform operations comprising:

monitoring a physical downlink control channel (PDCCH) in a search space in a control resource set;

processing a number of user equipment (UE)-specific search space (USS) sets based on one or more higher layer parameters with an indication; and

configuring a USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

21 . The computer readable storage medium of claim 20, wherein the operations further comprise:

configuring the USS set to another USS set of the number of USS sets based on the one or more higher layer parameters with the indication.

22. The computer readable storage medium of claim 21 , wherein the operations further comprise: configuring for the USS set with a number of PDCCH candidates corresponding to a control channel element aggregation level by the one or more higher layer parameters.

23. The computer readable storage medium of claim 22, wherein the one or more higher layer parameters comprises at least one of: an Aggregation-level-1 , Aggregation- level-2, Aggregation-level-4, Aggregation-level-8, and Aggregation-level-16, for CCE aggregation level 1 , CCE aggregation level 2, CCE aggregation level 4, CCE

aggregation level 8, and CCE aggregation level 1 6, respectively.

24. The computer readable storage medium of any one of claims 20-23, wherein the operations further comprise:

processing a UE-specific Search Space Resource Indicator (USSRI) that is configured to indicate which USS set of the number of USS sets to monitor in response to a change of one or more predetermined criteria comprising at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non- URLLC UEs, associated with a same network or serving cell.

25. A computer readable storage medium storing executable instructions that, in response to execution, cause one or more processors of an evolved NodeB (eNB) or a next generation NodeB (gNB) to perform operations comprising:

generating a user equipment (UE)-specific search space (USS) associated with resources for control channel transmission;

generating an indication that indicates the USS from among a plurality of USSs associated with different control channel resources; and

communicating the indication.

26. The computer readable storage medium of claim 25, wherein the operations further comprise:

generating the indication to indicate one or more control channel common elements (CCEs) in the USS associated with one or more aggregation levels; and

communicating, via the indication, the one or more aggregation levels to be monitored by a UE; and configuring the UE to monitor the USS with a number of control channel candidates based on the one or more aggregation levels of the indication.

27. The computer readable storage medium of claim 26, wherein the operations further comprise:

re-configuring the one or more aggregation levels associated with the UE by reducing the one or more aggregation levels to one or more lower aggregation levels or increasing the one or more aggregation levels to one or more higher aggregation levels comprising more control channel candidates than the one or more lower aggregation levels.

28. The computer readable storage medium of any one of claims 25-27, wherein the operations further comprise:

modifying the USS to a different USS of the plurality of different USSs based on a change in one or more predetermined criteria, wherein the one or more

predetermined criteria comprises at least one of: a blockage probability, a number of UEs, a number of blind decoding attempts by a UE, or a ratio of Ultra-Reliable Low Latency Communication (URLLC) UEs to non-URLLC UEs, associated with a same network;

re-configuring the indication based on the different USS; and

communicating the re-configured indication to initiate a change from the USS to the different USS, wherein the indication comprises a UE-specific Search Space

Resource Indicator (USSRI).

29. The computer readable storage medium of any one of claims 25-28, wherein the operations further comprise:

generating the USSRI in a downlink control information (DCI) carried by a common search space (CSS) of the control channel transmission, in a USS DCI, or in a dedicated physical channel with or separate from the DCI.