WO2017095470A1 - System and method for downlink control indicator design in beam aggregation system - Google Patents

System and method for downlink control indicator design in beam aggregation system Download PDF

Info

Publication number
WO2017095470A1
WO2017095470A1 PCT/US2016/028977 US2016028977W WO2017095470A1 WO 2017095470 A1 WO2017095470 A1 WO 2017095470A1 US 2016028977 W US2016028977 W US 2016028977W WO 2017095470 A1 WO2017095470 A1 WO 2017095470A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
dci message
embodiments
enb
comprise
Prior art date
Application number
PCT/US2016/028977
Other languages
French (fr)
Inventor
Yushu Zhang
Yuan Zhu
Qinghua Li
Huaning Niu
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201562262304P priority Critical
Priority to US62/262,304 priority
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2017095470A1 publication Critical patent/WO2017095470A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0014Three-dimensional division
    • H04L5/0023Time-frequency-space

Abstract

An evolved NodeB (eNB) may comprise a controller to execute one or more instructions in a memory to configure one or more downlink control information (DCI) messages that individual DCI message(s) in the one or more DCI messages comprises a codeword, wherein the codeword to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and/or a number of layers; and provide to the UE the one or more DCI messages via a physical downlink control channel (PDCCH) or an enhanced PHDCCH (ePDCCH) based on a search space of the UE. The UE may decode the PUCCH or the ePDCCH to obtain the one or more DCI messages and the one or more codeword specific control information.

Description

SYSTEM AND METHOD FOR DOWNLINK CONTROL INDICATOR DESIGN IN

BEAM AGGREGATION SYSTEM

Cross Reference to Related Applications

[0001] The present application claims priority to U.S. Provisional Patent Application No.

62/262,304, filed on December 2, 20 5 (attorney docket no. P90057Z), the entire specification of which is hereby incorporated by reference in its entirety for all purposes, except for those sections, if any, that are inconsistent with this specification.

BACKGROUND

[0002] Wireless mobile communication technology may use various standards and protocols to transmit data between a base station and a wireless mobile device. In the third generation partnership project (3GPP) long term evolution (LTE) systems, the base station may comprise an evolved Node Bs (eNode Bs or eNBs) in a Universal Terrestrial Radio Access Network (UTRAN) or an evolved UTRAN (e-UTRAN) that may communicate with a wireless mobile devices, known as a user equipment (UE). Data may be transmitted from, an eNode B to a UE via a physical downlink shared channel (PDSCH). A physical downlink control channel (PDCCH) may be used to transfer downlink control information or indicator (DCI) that may inform the UE of resource allocations, scheduling relating to downlink resource assignments on the PDSCH, uplink resource grants, and/or uplink power control commands, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The disclosure described herein is illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements.

[0004] Figure 1 schematically illustrates an example of a network in accordance with various embodiments.

[0005] Figure 2 schematically illustrates an example of an electronic device circuitry in accordance with various embodiments.

[0006] Figure 3 schematically illustrates an example of a long term e volution (LTE) frame structure in accordance with various embodiments. [0007] Figure 4 schematically illustrates an example of one or more processes in accordance with various embodiments.

[0008] Figure 5 illustrates an example of one or more processes in accordance with various embodiments:

[0009] Figure 6 schematically illustrates an example of a network in accordance with various embodiments.

[0010] Figure 7 schematically illustrates an example of one or more processes according to various embodiments.

[0011] Figure 8 schematically illustrates an example of one or more processes according to various embodiments.

[0012] Figure 9 schematically illustrates an example of a system in accordance with various embodiments.

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

DETAILED DESCRIPTION

[0014] Before the present disclosure is disclosed and described, it is to be understood that this disclosure is not limited to the particular structures, process steps, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element.

[0015] References in the specification to "one embodiment", "an embodiment", "an example embodiment", etc., indicate that the embodiment described may comprise a particular feature, structure, or characteristic, but every embodiment may not necessarily comprise the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0016] Embodiments of the disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the disclosure may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may comprise any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a non-transitory machine-readable medium may comprise read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices. For another example, a machine-readable medium, may comprise electrical, optical, acoustical or other forms of propagated signals (e ,g., carrier waves, infrared signals, digital signals, etc.), and others.

[0017] The following description may comprise terms, such as first, second, etc. that are used for descriptive purposes only and are not to be construed as limiting. As used herein, the term "module" may refer to, be part of, or comprise an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that may execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components) that provide the described functionality.

[0018] Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

[0019] An initial overview of technology embodiments may be provided below and then technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter. The following definitions are provided for clarity of the overview and

embodiments described below.

[0020] In a 3GPP radio access network (RAN) LTE system, a transmission station may comprise evolved universal terrestrial radio access network (E-UTRAN) Node Bs (or may be denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, and/or eNBs), which may communicate with a wireless mobile device, known as a user equipment (UE). A downlink transmission may comprise a communication from the transmission station (or eNodeB) to the wireless mobile device (or UE), and an uplink transmission may comprise a communication from the wireless mobile device to the transmission station.

[0021] Some embodiments may be used in conjunction with various devices and/or systems, for example, a UE, e.g., a mobile device, a mobile wireless device, a mobile communication device, a wireless station, a mobile station, a personal computer, a desktop computer, a mobile computer, a laptop computer, a netbook computer, a notebook computer, a tablet computer, a smartphone device, a mobile phone, a cellular phone, a server computer, a handheld computer, a handheld mobile device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wireless node, a base station (BS), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A V) device, a wired or wireless network, a wireless area network, a cellular network, a cellular node, a cellular device, a wireless local area network (WLAN) device, an universal integrated circuit card (UICC), an ultra mobile PC (UMPC), a customer premise equipment (CPE), a multiple input multiple output (MIMO) transceiver or device, a device having one or more internal antennas and/or external antennas, a digital video broadcast (DVB) device, a multi-standard radio device, a wired or wireless handheld device, a wireless application protocol (WAP) device, vending machines, sell terminals, a wearable device, a handset, and/or other consumer electronics such as MP3 players, digital cameras and the like, personal computing accessories and existing and future arising wireless mobile devices which may be related in nature and to which the principles of the embodiments could be suitably applied.

[0022] Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, radio frequency (RF), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), single carrier frequency division multiple access (SC-FDMA), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi -carrier modulation (MDM), discrete multi-tone (DMT), bluetooth®, global positioning system (GPS), wireless fidelity (Wi-Fi), Wi-Max, ZigBeeIM, ultra-wideband (UWB), global system for mobile (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, 4.5G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE) cellular system, LTE advance cellular system, high-speed downlink packet access

(HSDPA), high-speed uplink packet access (HSUPA), high-speed packet access (HSPA), HSPA+, single carrier radio transmission technology (1XRTT), evolution-data, optimized (EV-DO), enhanced data rates for GSM evolution (EDGE), and the like. Other embodiments may be used in various other or future devices, systems and/or networks.

[0023] Some demonstrative embodiments may be described herein with respect to a LTE network. However, other embodiments may be implemented in any other suitable cellular network or system, e.g., a GSM network, a 3G cellular network such as a Universal Mobile

Telecommunications Sy stem (UMTS) cellular sy stem, a 4G cellular network, a 4.5G network, a 5G network, a WiMax cellular network, or the like or other future network. [0024] Figure 1 schematically illustrates a wireless communication network 100 in accordance with various embodiments. The wireless communication network 100 (hereinafter "network 100") may comprise one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums, for example, a radio channel, a cellular channel, an RF channel, a wireless-local-area-network (WLAN) channel such as a WiFi channel, and/or the like. In some demonstrative embodiments, one or more elements of network 1 0 may optionally be capable of communicating over any suitable wired communication links. In one embodiment, network 100 may comprise a base station 110, e.g., an evolved Node B (eNB), that may communicate with a mobile device or terminal, e.g., UE 120. In various embodiments, eNB 1 10 may be a fixed station (e.g., a fixed node) or a mobile station/node. In various embodiments, the network 100 may comprise an access network of an access network of a 3GPP LTE network such as E-UTRAN, 3GPP LTE-A network, 4G network, 4.5G network, a 5G network or other future communication network, a WiMax cellular network, HSPA, Bluetooth, WiFi or other type of wireless access networks or any other future standard interface (SI).

[0025] In some demonstrative embodiments, the eNB 110 may be comprised in a radio access network that may comprise one or more cellular nodes, e.g., an eNB, a Node B, a base station (BS), a base transceiver station (BTS), and/or the like. In various embodiments, UE 120 may be a subscriber station that may be configured to communicate in one or more wireless communication networks, including 3GPP LTE network, 3GPP LTE-U network, 3GPP LTE-A network, a 4G network, a 4.5G network, a 5G network a WiMax cellular network, WiMAX, HSPA, Bluetooth, WiFi, or other wireless networks.

[0026] Referring to Figure 1, eNB 110 may comprise one or more of a controller 114, a transmitter 1 12, a receiver 116 and one or more antennas 118. The eNB 110 may optionally comprise other hardware components and/or software components, e.g., a memory, a storage, an input module, an output module, one or more radio modules and/or one or more digital modules, and/or other components. Transmitter 112 may be configured to transmit signals to UE 120 via one or more antennas 1 18. Receiver 1 16 may be configured to receive signals from UE 120 via one or more antennas 1 18. In some embodiments, the transmitter 112 and/or the receiver 116 may be elements or modules of a transceiver or a transceiver circuitry. In some embodiments, controller 114 may comprise a configuring module or unit or circuitry 114a that may configure one or more DCIs.

[0027] The controller 114 may be coupled with transmitter 112 and/or receiver 116 and/or one or more communications modules or units in eNB 110. The transmitter 112 and/or the receiver 116 may be coupled with the one or more antennas 118 to communicate with UE 120. UE 120 may comprise a transmitter 122 and a receiver 126 and/or one or more communications modules or units. The transmitter 122 and/or the receiver 126 may communicate with a base station (BS), e.g., eNB 1 10 or other type of wireless access point such as wide area network (WW AN) via one or more antennas 128 of the UE 120.

[0028] In some embodiments, controller 114 may control one or more functionalities of eNB 110 and/or control one or more communications performed by eNB 110. In some demonstrative embodiments, controller 1 14 may execute instructions of software and/or firmware, e.g., of an operating system (OS) of eNB 110 and/or of one or more applications. Controller 114 may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller 1 14. In some embodiments, one or more functionalities of controller 114 may be implemented by logic, which may be executed by a machine and/or one or more processors.

[0029] In some embodiments, UE 120 may comprise a controller 124, a transmitter 122, a receiver 126 and/or one or more antennas 128. In some embodiments, UE 120 may comprise other hardware components, software components and/or firmware components, e.g., a memory, a storage, an input unit, an output unit and/or any other components. Transmitter 122 may transmit signals to eNB 110 via one or more antennas 128. Receiver 126 may receive signals from eNB 1 10 via one or more antennas 128. In some embodiments, the transmitter 122 and/or the receiver 126 may be elements or modules of a transceiver circuitry.

[0030] In some embodiments, controller 124 may be coupled to receiver 126 and/or transmitter 122. In some embodiments, controller 124 may control one or more functionalities of UE 120 and/or control one or more communications performed by UE 120. In some demonstrative embodiments, controller 124 may execute instructions of software and/or firmware, e.g., of an operating system (OS) of UE 120 and/or of one or more applications. Controller 124 may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller 12. In some embodiments, one or more functionalities of controller 124 may be implemented by logic, which may be executed by a machine and/or one or more processors.

[0031] In some embodiments, controller 124 may comprise a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual -core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (TC), an application-specific IC (ASIC), or any other suitable or specific processor or controller and/or any combination thereof. [0032] Transmitter 12 may comprise, or may be coupled with one or more antennas 118 of eNB 1 10 to communicate wirelessly with other components of the wireless communication network 100, e.g., UE 120. Transmitter 122 may comprise, or may be coupled with one or more antennas 128 of UE 120 to communicate wirelessly with other components of the wireless communication network 100, e.g., eNB 110. in some embodiments, transmitter 112 and/or transmitter 122 may each comprise one or more transmitters, one or more receivers, one or more transmitters, one or more receivers and/or one or more transceivers that may send and/or receive wireless communication signals, radio frequency (RF) signals, frames, blocks, transmission streams, packets, messages, data items, data, information and/or any other signals.

[0033] In some demonstrative embodiments, the antennas 118 and/or the antennas 128 may comprise any type of antennas suitable to transmit and/or recei ve wireless communication signals, RF signals, blocks, frames, transmission streams, packets, messages, data items and/or data. For example, the antennas 118 and/or the antennas 128 may comprise any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antennas 118 and/or the antennas 128 may implement transmit and/or receive functionalities using separate transmit and/or receive antenna elements. In some embodiments, the antennas 118 and/or the antennas 128 may implement transmit and/or receive functionalities using common and/or integrated transmit receive elements. The antenna may comprise, for example, a phased array antenna, a single element antenna, a dipole antenna, a sec of switched beam antennas, and/or the like.

[0034] While Figure 1 illustrates some components of eNB 110, in some embodiments, the eNB 110 may optionally comprise other suitable hardware, software and/or firmware components that may be interconnected or operably associated with one or more components in the eNB 1 10. While Figure 1 illustrates some components of UE 120, in some embodiments, UE 120 may optionally comprise other suitable hardware, software and/or firmware components that may be

interconnected or operably associated with one or more components in UE 120. For example, eNB 110 and/or UE 120 may comprise one or more radio modules (not shown) to modulate and/or demodulate signals transmitted or received on an air interface, and one or more digital modules (not shown) to process signals transmitted and received on the air interface.

[0035] In some demonstrative embodiments, eNB 110 and/or UE 120 may comprise one or more input units (not shown) and/or one or more output units (not shown). For example, one or more input units may comprise a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or any other pointing/input unit or device. For example, one or more output units may comprise a monitor, a screen, a touch-screen, a flat panel display, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or any other output unit or device.

[0036] In some demonstrative embodiments, UE 120 may comprise, for example, a mobile computer, a mobile device, a station, a laptop computing device, a notebook computing device, a netbook, a tablet computing device, an ultrabook computing device, a handheld computing device, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a wearable device, a relatively small computing device, a non-desktop computer, a "carry small live large"' (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an "Origami" device or computing device, a video device, an audio device, an audio/video (A/V) device, a gaming device, a media player, a smartphone, a mobile station (MS), a mobile wireless device, a mobile communication device, a handset, a cellular phone, a mobile phone, a personal computer (PC), a handheld mobile device, an universal integrated circuit card (UICC), a customer premise equipment (CPE), or other consumer electronics such as digital cameras and the like, personal computing accessories and existing and future arising wireless mobile devices winch may be related in nature and to which the principles of the embodiments could be suitably applied.

[0037] While Figure 1 illustrates one or more components in eNB 110 and/or UE 120, eNB 1 10 and/or UE 120 may each comprise one or more radio modules or units (not shown) that may modulate and/or demodulate signals transmitted or received on an air interface, and/or one or more digital modules or units (not shown) that may process signals transmitted and received on the air interface.

[0038] Figure 2 illustrates an example of an electronic device circuitry 200 according to an embodiment. The electronic device circuitry 200 may be eNB circuitry, UE circuitry, or other type of circuitr}' in accordance with various embodiments. For example, the electronic device circuitry 200 may communicate using one or more wireless communication standards such as 3GPP LTE, 3 GPP LTE-A, 3 GPP LTE-U, WiMAX, HSPA, Bluetooth, WiFi, 5G standards or other wireless standards in various embodiments. The electronic device circuitry 200 may communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a wireless wide area network (WWAN) or other network in various embodiments.

[0039] In various embodiments, the electronic device circuitry 200 may be, or may be incorporated into or otherwise a part of, an eNB, a UE, or other type of electronic device. The electronic device circuitry 200 may comprise transmit circuitry 212 and receive circuitry 216 coupled to control circuitry 214. In some embodiments, the transmit circuitry 212 and/or receive circuitry 216 may be elements or modules of a transceiver circuitry, or in some embodiments may be in a radio frequency (RF) circuitry. In some embodiments, the control circuitr - 214 may be in a baseband circuitry. The electronic device circuitry 200 may be coupled with one or more plurality of antenna elements of one or more antennas 23 8. The electronic device circuitry 200 and/or the components of the electronic device circuitry 200 may be configured to perform operations similar to those described herein.

[0040] In some demonstrative embodiments, the electronic device circuitry 200 may be part of or comprise 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 electronic device circuitry 200 may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.

[0041] In some embodiments, control circuitry 214 may be coupled to transmit circuitry 212 and/or receive circuitry 216. In some embodiments, control circuitry 214 may control one or more functionalities and one or more communications of electronic device circuitry 200. In some demonstrati ve embodiments, control circuitry 214 may execute instructions of software and/or firmware, e.g., of an operating system (OS) and/or one or more applications of the electronic device circuitry 200. Control circuitry 214 may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of the control circuitry 214. In some embodiments, one or more functionalities of control circuitry 214 may be implemented by logic, which may be executed by a machine and/or one or more processors.

[0042] In some embodiments, control circuitry 214 may comprise a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), an

application-specific IC (ASIC), or any other suitable or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof.

[0043] Figure 3 illustrates an example of a long term evolution (LTE) frame structure. In some embodiments, an e B may transmit to a UE a signal on a physical (PHY) layer that may be used to convey the PDCCH. In the illustration of FIGURE 3, an example of a PDCCH is illustrated. [0044] In some embodiments, a radio frame 300 may have a duration 7/ of, e.g., 10 milliseconds (ras). A radio frame may be segmented or divided into, e.g., ten subframes 3 lOi that may each be, e.g., 1 ms long. A subframe may be further subdivided into, e.g., two slots 320a and 320b, each with a duration Tsiot of, e.g., 0.5 ms. In some embodiments, the first slot (#0) 320a may include a physical downlink control channel (PDCCH) 360 and a physical downlink shared channel (PDSCH) 366. The second slot (#2) 320b may include data using the PDSCH. A slot for a component carrier (CC) used by the eNode B and the UE may include one or more resource blocks (RBs) 330a, 330b, 330i, 330m, and 330n based on the CC frequency bandwidth.

[0045] A resource block 330i may include, e.g., 12-15kHz subcarriers 336 (on the frequency axis) and, e.g., 6 or 7 orthogonal fre uency-division multiplexing (OFDM) symbols 332 (on the time axis) per subcarrier. In one embodiment, a RB 330i may use, e.g., seven OFDM symbols if short or normal cyclic prefix is employed. In another embodiment, a RB 330i may use six OFDM symbols if an extended cyclic prefix is used. The RB 330i may be mapped to, e.g., 84 resource elements (REs) 340i using short or normal cyclic prefixing, or may be mapped to, e.g., 72 REs (not shown) using extended cyclic prefixing. A RE 33 Oi may be a unit of a OFDM symbol 342 by a subcarrier (e.g., 15kHz) 346. A RE 330i may transmit, e.g., two bits 350a and 350b of information using QPSK. The number of bits communicated per RE may be dependent on a level of modulation.

[0046] In some embodiments, a control region of a serving cell in carrier aggregation may comprise a set of control channel elements (CCEs). In one embodiment, the CCEs may be numbered from 0 to NCCF -. -1, where Ncczk is the total number of CCEs in the control region of subframe k. A UE may monitor a set of PDCCH candidates on one or more acti vated serving cells as configured by higher layer signaling for control information. For example, the UE may decode each of the PDCCH candidates in the set according to all of the monitored DCI formats. For example, the UE may utilize one or more CCEs to monitor a PDCCH in the set.

[0047] In some embodiments, a physical downlink control channel may be transmitted on an aggregation of one or several CCEs. For example, the CCE(s) may be transmitted consecutively. An example CCE may correspond to, e.g., nine resource element groups (REGs). A REG may comprise, e.g., four resource elements. In one embodiment, a number of REGs that may not be assigned to a physical control format indicator channel (PCFICH) or a physical hybrid automatic repeat request (ARQ) indicator channel (PHTCH) may be denoted as NREG. The CCEs available in a 3GPP LTE system may be numbered from 0 to NCCE - 1, where NCCE :=: (NREG / 9). The PDCCH may support one or more formats. In some embodiments, one or more PDCCHs may be transmitted in a subframe.

[0048] While Figure 3 illustrates some examples of a frame structure and/or PDCCH transmission and mapping, e.g., as described by 3GPP LTE specifications, the examples are not intended to be limiting. Some embodiments may use other frame structure, e.g., with a different frame duration and/or other PDCCH transmission and mapping, e.g., with other configuration for RE, RB and/or CCE, etc. In another embodiment, an enhanced PDCCH (ePDCCH) may be used to increase capacity to allow advances in the design of cellular networks. The aspect of an ePDCCH may include but not limited to CRC attachment, channel coding, rate matching, multiplexing, scrambling, modulation, layer mapping, precoding, resource mapping, and search space requirements and is not intended to limit to a certain system. In some embodiments, a relay physical downlink control channel (R-PDCCH) design with non-interleaved UE-RS based mapping may be used for ePDCCH design to achieve scheduling and a beamforming gain when channel state information (CSI) feedback is available.

[0049] Figure 4 schematically illustrates one or more processes that may be performed on downlink control information or indicator (DCI) in accordance with various embodiments. As shown in Figure 4, the DCI may undergo one or more of processes to create PDCCH payload. For example, the processes may comprise attachment (402) of a cyclic redundancy check (CRC) that may be used for error detection in the DCI message; channel coding (404) for use in forward error correction; and rate matching (106) that may be used to output a bit stream with a desired code rate. Detailed instructions for performing the cyclic redundancy check, channel coding, and rate matching are provided in the 3GPP LTE specifications, e.g., Release 8, 9 and 10. The encoded DCI message(s), e.g., codeword 52.0 in Figure 5, for each control channel may further be multiplexed and/or scrambled and may undergo modulation, layer mapping, precoding and resource mapping.

[0050] While Figure 4 illustrates an example for PDCCH in some embodiments, in some other embodiments, the example of Figure 4 may be applied to ePDCCH.

[0051] Figure 5 schematically illustrates one or more processes that may be performed on downlink control information or indicator (DCI) in accordance with various embodiments. A multiplexer may be used to multiplex encoded DCI 520, e.g., blocks of encoded bits, that may be processed according to Fig. 4, for each control channel to create a block of data. A size of the blocks of data may be altered for PDCCHs to start, at a desired CCE position. The size of the blocks of data may also be altered for the blocks of bits to match an amount of REGs that can be used by the PDCCH. A scrambler 502 may scramble the multiplexed block of bits. In some embodiments, the encoding may be outlined in 3GPP LTE specification.

[0052] A modulator 504 may modulate the scrambled bits. For example, Quadrature Phase Shift Keying (QPSK) may be used to create a block of complex-valued modulation symbols. In some embodiments, other types of modulation, such as Bi-Phase Shift. Keying (BPSK), 16 Quadrature Amplitude Modulation (16-QAM), 32-QAM, 64-QAM, and so forth may also be used. [0053] A layer mapper 506 may map complex symbols to, e.g., one or more transmission layers, e.g., based on a number of transmit antennas used at the eNB. For example, one, two, four, eight and/or other layer mapping may be used. The mapping is outlined in the 3GPP LTE specification.

[0054] A precoder 508 may perform preceding on one or more blocks from, the layer mapper 506. For example, the precoder may take a block from the layer mapper to generate an output for each antenna port. Precoding for transmission diversity may be performed for, e.g., two, four, eight and/or other number of antennas in the eNB.

[0055] A resource mapper 510 may divide the complex valued symbols for each antenna into one or more groups to be mapped to one or more resource elements. In some embodiments, the complex valued symbols for each antenna may be divided into quadruplets. The sets of quadruplets may undergo a permutation such as interleaving and/or cy clic shifting and/or may be mapped to resource elements within resource element groups.

[0056] In some embodiments, the PDCCH may be transmitted prior to the PDSCH in each subframe transmitted from an eNB to a UE. Demodulation of the PDCCH at the UE may be based on, e.g., a cell-specific reference signal (CRS). In some embodiments, a cell may be assigned a single reference signal. A UE may receive a PDCCH using blind decoding. In some embodiments, a UE may use a blind decoding to try one or more CCE aggregation levels and CCE indexes to receive a PDCCH and/or find the UE's PDCCH via Q C decoding.

[0057] . The resources used by the UE for PDCCH blind decoding may be referred to as a search space. In some embodiments, a different search space may be used to detect and demodulate an ePDCCH associated with a UE specific reference signal (UE-RS) relative to the use of a CRS.

[0058] While Figure 5 illustrates an example for PDCCH in accordance with some embodiments, in some other embodiments, the example of Figure 5 may be applied to ePDCCH.

[0059] Figure 6 schematically illustrates an example of a wireless communication network 600 with beam aggregation in accordance with various embodiments. The wireless communication network 600 (hereinafter "network 600") may comprise one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums. In some demonstrative embodiments, network 600 may comprise a beam aggregation sy stem. For example, the network 600 may comprise one or more base stations, e.g., a first eNB 612 and a second eNB 614. In some embodiments, the first eNB 612 may communicate with one or more mobile devices or terminals, e.g., a first UE 622. The second eNB 614 may communicate with one or more mobile devices or terminals, e.g., the first UE 622 and a second UE 624. In various embodiments, the first eNB 612 and/or the second eNB 614 may be a fixed station (e.g., a fixed node) or a mobile station/node. [0060] In some embodiments, network 600 may utilize beam aggregation that may allow two or more transmission points (TP), e.g., first eNB 612 and/or second eNB 614, to jointly transmit one or more signals to a UE with aggregated beams. Figure 6 schematically illustrates one or more beam aggregation examples in frequency domain for the first UE 622, according to various embodiments. As shown in example 1 , for UE 622, first beam 632 and second beam 634 may be scheduled in different resource blocks (RBs), wherein one or more resource blocks for the first beam 632 may be overlapped with one or more resource blocks for the second beam 634. As shown in examples 3 and 4, first beam 632 and second beam 634 may be scheduled in different resource blocks (RBs) without resource block overlapping. As shown in example 2, in some embodiments, one or more signals from the two beams 632 and 634 may be located in the same RBs. Referring to Figure 6, as shown in examples 1 to 4, the second UE 624 may communicate with the second eNB 614 with a beam 680 that may be scheduled in one or more resource blocks without overlapping with those for the second beam 634. In some embodiments, as shown in examples 1 to 4, the one or more resource blocks for beam 680 of the second UE 624 may be overlapped or non-overlapped with those for the first beam 632 of the first UE 622. In some embodiments, eNB 110 may comprise the controller 114 to perform one or more scheduling of Figure 6.

[0061] While Figure 6 illustrates four exemplary examples of beam aggregation, other resource allocation types and/or quasi~co-location (QCL) set may be used in each transmission point. In some embodiments, an eNB may configure downlink control signaling to support various examples and/or enhance scheduling flexibility in beam aggregation. In some embodiments, a total rank of a UE may be increased and the spectrum efficiency (SE) of the U E may be raised in the beam aggregation mode.

[0062] In some embodiments, beam aggregation may be deployed in an intra-site (e.g., ideal) backhaul example and/or an inter-site (e.g., non-ideal) backhaul example. For example, for intra-site backhaul, a joint scheduler for aggregated beams may be used. For inter-site backhaul, a joint scheduler for aggregated beams may or may not be used. In some embodiments, an independent scheduler for aggregated beams with a load balancing may be used for inter-site backhaul. Downlink control signaling design may support beam aggregation for intra-site backhaul and/or inter-site backhaul and/or enhance scheduling flexibility for beam aggregation.

[0063] In beam aggregation, one or more aggregated beams may be transmitted from different transmission points. In some embodiments, a codeword indicating an aggregated beam may result in different channel state information (CSI) in different beams. In some embodiments, a single downlink control indicator (DC!) may be used to mdicate a codeword specific resource allocation for one or more aggregated beams. In some embodiments, a codeword to layer mapping with a codeword specific resource allocation may be configured for one or more aggregated beams with different resource allocation schemes, e.g., as shown in Figure 6, to support a flexible resource allocation.

[0064] For example, based on a codeword specific resource allocation, a resource block assignment may be codeword specific, wherein a codeword may be configured to have a corresponding resource block assignment indication. In some embodiments, a codeword indication may be configured to comprise a resource block assignment that may be codeword specific. For example, a DCI format may be configured as follows:

for each transport block:

- Modulation aria coding scheme - e.g., 5 bits in section 7.1.7 of 3GPP TS 36.213 or other number of bits may be used

- New data indicator - e.g., 1 bit or other number of bits may be used

- Redundancy version - e.g., 2 bits or other number of bits may be used

- Resource block assignment

[0065] In some embodiments, one or more bits may be used for the resource block assignment based on a size of the codeword.

[0066] In some embodiments, different transmission points may use different resource allocation types. In some embodiments, a codeword may be configured to comprise a resource allocation header that may correspond to a resource allocation type. For example, a DCI format may be configured as follows:

for each transport block:

- Modulation and coding scheme - e.g., 5 bits in section 7.1.7 of 3GPP TS 36.213 or other number of bits may be used

- New data indicator - e.g., 1 bit or other number of bits may be used

- Redundancy version - e.g., 2 bits or other number of bits may be used

- Resource allocation header

- Resource block assignment

[0067] In some embodiments, one or more bits may be used for the resource allocation header based on a size of the codew ord.

[0068] In some embodiments, different QCL sets may be used in different beams to enable coordinated multiple points transmission/reception (CoMP) and/or beam aggregation. In some embodiments, a codeword may be configured to relate to a QCL set that may be codeword specific. In some embodiments, a codeword may be configured to comprise a QCL indicator for a QCL set. For example, an example of a DCI format may be configured as follows: for each transport block:

- Modulation and coding scheme - e.g., 5 bits in section 7.1 ,7 of 3GPP TS 36.213 or other number of bits may be used

- New data indicator - e.g., 1 bit or other number of bits may be used

- Redundancy version - e.g., 2 bits or other number of bits may be used

- PDSCH RE mapping and Quasi-Co-Location indicator

[0069] In some embodiments, one or more bits may be used for the QCL indicator based on a size of the codeword.

[0070] In some embodiments, based on the codeword to layer mapping with a codeword specific resource allocation, a codeword may be configured to indicate a configuration of one or more antenna ports (APs) and/or a configuration of layer mapping. In some embodiments, a UE specific reference signal (e.g., a demodulation reference signal (DMRS)) may be divided into, e.g., two sets: APs {7, 8, 11, 13} and APs {9, 10, 12, 14} . In some embodiments, an AP set may be used for a codeword. In some embodiments, a codeword specific AP configuration may be configured to use, e.g., a 2-bit indicator. For example, for codeword 1, one or more antenna ports may be selected from the first set {7, 8, 11, 13}, e.g., in an ascending order. In some embodiments, a descending order may be used. Similarly, for codeword 2, one or more antenna ports may be selected from the second set {9, 10, 12, 14}, e.g., in an ascending order. The 2-bit codeword specific AP configuration may have a value that may correspond to a number of antenna ports used in a corresponding AP set. In some embodiments, other AP configurations may be used and may¬ be indicated by corresponding indicators. The DCI format may be configured as follows:

for each transport block:

- Modulation and coding scheme - e.g., 5 bits as defined in section 7.1.7 of 3GPP TS 36.213 or other number of bits may be used

- New data indicator - e.g., 1 bit or other number of bits may be used

- Redundancy versio - e.g., 2 bits or other number of bits may be used

- Antenna port(s) and number of layers - e.g., 2 bits or other number of bits may be used [0071] In some other embodiments, the information of antenna port(s) and/or number of layers for a codeword may be configured by a 3-bit indicator of Antenna port(s), scrambling identity and number of layers. In some embodiments, if only one codeword is enabled, the number of APs may equal to a value of the 3-bit indicator or the same as Table 5.3.3.1.5c- 1 in 3GPP TS 36.212. In some embodiments, if two codewords are enabled, the total number of APs may begin from 2 and may be configured as Table 1 below for example: Table 1 : Examples of APs and number of layers indication Antenna port(s), Codeword 1 APs Codeword 2 APs

scrambling identity and

number of layers (3 bits)

0 7 9

1 7,8 9

2 7 9, 10

7,8 9, 10

4 7,8, 1 1 9, 10

5 7,8, 1 1 9, 10, 12

6 7,8, 1 1, 13 9, 10, 12

7,8, 1 1 , 13 9, 10, 12, 14

[0072] While Table 1 illustrates an example that may enable two codewords, in some other embodiments, a different number of codewords may be utilized.

[0073] in some embodiments, the payload of the DCI format may be increased if codeword specific resource allocation is used. Some embodiments may enlarge or increase a CCE aggregation level to provide the DCI with a better quality, e.g., for an increased payload of the DCI format. For example, one or more UEs in beam aggregation mode may enlarge a maximum CCE aggregation level. In some embodiments, the maximum CCE aggregation level may be 32 or bigger. In some other embodiments, the maximum CCE aggregation level may have a number different than 32, e.g., a bigger number or a smaller number. In some embodiments, eNB, e.g., 110, may configure the maximum CCE aggregation level, e.g., explicitly, via RRC signaling with, e.g., 1-bit trigger. In some other embodiments, the maximum CCE aggregation level may be configured, e.g., implicitly, in a transmission mode configuration, e.g., in communication standards or protocols.

[0074] In some embodiments, eNB, e.g., 1 10, may transmit an ePDCCH in a beam aggregation way. For example, eNB 1 10 may configure the ePDCCH transmission explicitly, e.g., via R C signaling. In some other embodiments, the ePDCCH transmission may be configured implicitly in a transmission mode configuration, e.g., in communication standards or protocols. In some embodiments, the ePDCCH may be mapped into, e.g., two or more layers if beam aggregation is used.

[0075] In some embodiments, eNB 1 10 may transmit one or more DCI messages (e.g., two or more) to a UE, e.g., 120, in beam aggregation to enhance scheduling flexibility. While the following description may use two DCIs as an example, in some other embodiments, eNB 1 10 may transmit a different number of DCIs, e.g., one or more, to UE 120. In some embodiments, each of the two DCl messages may indicate control signaling for one beam. In some embodiments, the two DC! messages may have the same format or configuration with each other. In some embodiments, the two DCl messages may each indicate, e.g., only one codeword. In some embodiments, the two DCl messages may have one or more common configurations, e.g., antenna port(s), scrambling identity and/or number of layers. In some embodiments, the antenna port(s) and/or the number of layers may be codeword specific. For example, the two DCl messages may both comprise one or more identical common configurations, e.g., antenna port(s), scrambling identity and/or number of layers. For example, the common configuration of antenna port(s), scrambling identity and/or number of layers may be the same in the two DCl messages. In some embodiments, one or more common configurations in a first DCl message of the two DCl messages may each be the same as a corresponding common configuration in a second DCl message of the two DCl messages. In some embodiments, if a first DCl in the two DCIs is not decoded correctly, the codeword of the first DCl may be decoded based on a codeword of a second DCl in the two DCIs.

[0076] In some embodiments, a serving transmission point (TP), e.g., a primary eNB, may serve a UE. In some embodiments, a secondar ' eNB that may not serve a UE may be called as an assistant TP. In some embodiments, a trigger (e.g., 1-bit or other number of bits) may be used in each or both of the two DCl messages to indicate whether a corresponding DCl is used for a serving TP or an assistant TP. In some embodiments, as shown in Table 1 , a 3-bit indicator may be used to configure one or more configurations in the two DCIs, e.g., number of antenna port(s), scrambling identity and/or number of layers. In some other embodiments, a 2-bit indicator may be used in each DCl and may have a value equal to the number of corresponding APs.

[0077] While an example of a serving TP and an assistant TP is described in accordance with some embodiments, in some embodiments, one or more serving TPs and/or one or more assistant TPs may be used. While an example of two DCIs is described in accordance with some embodiments, in some embodiments, one or more DCIs that each correspond to a TP or an aggregated beam may be used.

[0078] In some other embodiments, the two DCIs may have different formats. For example, a primar - DCl may be used for the serving TP and a secondary DCl may be used for the assistant TP. In some embodiments, the primary DCl and/or the secondary DC! may each contain control signaling for one codeword only. In some embodiments, the primary DCl and/or the secondary DCl may each contain control signaling for a different number of codewords. For example, the primary DCl may have a format similar to DCl format 2D, but may indicate a codeword. In some embodiments, the primary DCl may comprise one or more common configurations that may be used for the serving TP and/or the assistant TP, e.g., Carrier indicator. Transmit power control (TPC) command, Downlink assignment index. Hybrid Automatic Repeat Request (HARQ) process number. Sounding Reference Signal (SRS) request, etc.

[0079] The secondar - DCI may contain secondary codeword configuration. An example of the secondary DCI may be as follows:

- Modulation and coding scheme - e.g., 5 bits as defined in section 7.1.7 of 3GPP TS

36.213 or other number of bits may be used

- New data indicator - e.g., 1 bit or other number of bits may be used

- Redundancy version - e.g., 2 bits or other number of bits may be used

- Resource allocation header

- Resource block assignment

- PDSCH RE mapping and Quasi-Co-Location indicator

- Antenna port(s) and number of layers - e.g., 2 bits or other number of bits may be used [0080] For example, for a configuration of APs and number of layers in the secondary DCI, the serving TP may use one or more APs in the first set {7, 8, 11, 13 } . The assistant TP may use one or m ore A Ps in the second set {9, 10, 12, 14} . In som e em bodiments, each of th e two DCIs may use, e.g., a 2-bit indicator to indicate a number of APs. For example, the number of APs may equal to the value of the 2-bit indicator.

[0081] In some other embodiments, the primary DCI and the secondary DCI may each comprise one or more of, e.g.. Carrier indicator, Transmit power control (TPC) command, Downlink assignment index, Hybrid Automatic Repeat Request (HARQ) process number, Sounding

Reference Signal (SRS) request, Modulation and coding scheme, Ne data indicator, Redundancy version, Resource allocation header, Resource block assignment, PDSCH RE mapping and Quasi-Co-Location indicator, and/or Antenna port(s) and number of layers, etc. In some embodiments, a serving TP may configure the primary DCI and/or the secondary DCI. In some other embodiments, an assistant TP may configure a corresponding secondary DCI.

[0082] In some embodiments, the primary DCI and/or the secondary DCI may be transmitted in the serving TP only. In some embodiments, the two DCIs may both be located at a search space of a UE. In some oilier embodiments, a first search space may be used for the primary DCI and/or a secondary search space may be configured for the secondary DCI. In some embodiments, a set of one or more CCE resources may be used to define a search space for PDCCH. For example, a UE may be allocated the set of one or more CCEs. In some embodiments, eNB may select one or more CCEs in the set of CCEs for a PDCCH and one or more oilier CCEs in the set of CCEs for another PDCCH. The set of CCE resources may be divided into two parts: one for the primary DCI, the other for the secondary DCI. Tire serving TP and/or the assistant TP may configure the CCE resource division via RRC signaling. In some embodiments, the CCE aggregation level for the two DCIs may not be the same. In some other embodiment, the CCE aggregation levels for the two DCIs may be the same to reduce a number of blind detection.

[0083] In some embodiments, the primary DCl and the secondar - DCI may each be transmitted in a corresponding TP individually. For example, the primary DCI may be transmitted in the serving TP and/or the secondary DCI may be transmitted in the assistant TP. In some embodiments, for a UE in beam aggregation, the assistant TP may use the same radio network temporary identity (RNTI) as that of the serving TP. In some other embodiments, the assistant TP may configure a different RNTI value in the assistant TP via RRC signaling or via radio access response (RAR) if the UE transmits a Physical Random Access Channel (PRACH) signal to the assistant TP, In some embodiments, the CCE aggregation level for the two DCIs may not be the same. In some other embodiments, the CCE aggregation level for the two DCIs may be the same to reduce a number of blind detection.

[0084] Figure 7 schematically illustrates an example of one or more processes that may be performed by an eNB, e.g., 110 or electronic device circuitry 200 according to various embodiments. The one or more processes may be performed by, e.g., controller 114 or control circuitry 214 or a baseband circuitr ' in eNB 110 and/or the transmitter 1 12 and/or receiver 1 16, For example, at 702, controller 1 14 may configure a downlink control information (DCI), e.g., for the beam aggregation, e.g., via the configuring module 114a. For example, controller 114 may configure the DCI format according to one or more embodiments as described in the disclosure. In some embodiments, the controller 1 14 and/or the control circuitry 214 may comprise the configuration module 114a to configure the DCl according to various embodiments.

[0085] In some embodiments, controller 114 may configure the DCI format to comprise one or more of codeword specific control information or fields, e.g., Resource allocation header.

Resource block assignment, PDSCH RE mapping and Quasi-Co-Location indicator, and/or Antenna port(s) and number of layers, etc.

[0086] In some embodiments, controller 114 may configure the DCI format to comprise, e.g., a 2-bit codeword specific configuration of APs for each codeword, e.g., Antenna port(s) and number of layers with a number of APs with a value of the 2-bit indicator. In some other embodiments, controller 114 may configure the DCI format to comprise, e.g., a 3 -bit indicator of "Antenna port(s), scrambling identity and number of layers with a number of APs equal to the value of the 3 -bit indicator, e.g.. Table 5.3.3.1.5c-l in TS 36.212, for a one-codeword enablement or based on, e.g.. Table 1 as described above for a two-codeword enablement.

[0087] In some embodiments, controller 114 may configure to enlarge a CCE AL to reduce a payload of the DCI format with codeword specific resource allocation. In some embodiments, controller 114 may configure a larger maximum AL explicitly via RRC signaling by, e.g., a 1-bit trigger, or implicitly in a transmission mode configuration.

[0088] In some embodiments, controller 114 may configure ePDCCH transmission in a beam aggregation way explicitly via RRC signaling or implicitly in a transmission mode configuration.

[0089] In some embodiments, one or more eNBs may be used to configure for UE 120 one or more DCIs that may each indicate control signaling for an aggregated beam to enhance the scheduling flexibility. In some embodiments, the one or more eNBs may configure the one or more DCIs to have different formats or the same format. In some embodiments, the one or more eNBs may configure in each codeword a trigger with, e.g., 1 bit or other number of bits, to indicate for which transmission point (TP) a corresponding DCI is used for, e.g., a serving TP or an assistant TP. In some embodiments, each e'NB may use a controller, e.g., 110, in the eNB to configure a corresponding DCI. In some other embodiments, the one or more DCIs may be configured by the same eNB, e.g., via a controller 114.

[0090] For example, if eNB 110 is used as a serving TP, controller 114 in the serving TP may configure a primary DCI and/or a secondary DCI for UE 120 based on one or more

primary/secondary DCI embodiments described in the disclosure. If eNB 1 10 serves as an assistant TP, controller 114 in the assistant TP may configure a secondary DCI for UE 120 based on one or more secondary DCI embodiments described in the disclosure. In some embodiments, the primary DCI and the secondary DCI may be configured to each indicate one or more codewords. For example, the primary DCI and the secondary DCI may each indicate one codeword only.

[0091] For example, the primary DCI and the secondary DCI may comprise one or more common configurations that may be used for the serving TP and the assistant TP, e.g., one or more of Antenna port(s), scrambling identity and number of layers, Carrier indicator, Transmit power control (IPC) command. Downlink assignment index. Hybrid Automatic Repeat Request (HARQ) process number and Sounding Reference Signal (SRS) requestor other common configurations. For example, the common configuration of Antenna port(s), scrambling identity and number of layers may have the same value in the primary DCI and the secondary DCI. If one DCI of the primary DCI and the secondary DCI is not decoded correctly , the other one in the primary DCI and the secondary DCI may be used to decode the incorrectly decoded DCI.

[0092] In some embodiments, the primary DCI and the secondary DCI may be configured in different format. For example, the primary DCI and the secondary DCI may contain control signaling for one codeword.

[0093] In some embodiments, the primar ' DCI may be configured to indicate, e.g., one codeword that may comprise one or more fields that may be included in a DCI format 2D as described in 3GPP TS 36.212. For example, the primary DCI may comprise one or more other common configuration, e.g., one or more of Carrier indicator, Transmit power contra! (TPC) command, Do wnlink assignment index, Hybrid Automatic Repeat Request (HARQ) process number, Sounding Reference Signal (SRS) request, in some embodiments, the secondary DCI may contain a secondary codeword configuration. In some embodiments, Antenna ports and number of layers may be configured in each codeword specific DCI.

[0094] In some embodiments, the secondary DCI may be configured to comprise the secondarv' codeword configuration, e.g. one or more of Modulation and coding scheme. New data indicator, Redundancy version. Resource allocation header. Resource block assignment, PDSCH RE mapping and Quasi -Co-Location indicator, and Antenna port(s)' and number of layers or other secondary codeword configuration.

[0095] In some embodiments, for a configuration of APs and number of layers, the serving TP may use one or more APs in the first set {7, 8, 11, 13} . The assistant TP may use one or more APs in the second set {9, 10, 12, 14} . In some embodiments, each of the two DCTs may use, e.g., a 2-bit indicator to indicate a number of APs for each TP. For example, the number of APs may equal to the value of the 2 -bit indicator.

[0096] In some other embodiments, the primary DCI and/or the secondary DCI may each comprise one or more of, e.g., Carrier indicator, Transmit power control (TPC) command, Downlink assignment index, Hybrid Automatic Repeat Request (HARQ) process number, Sounding Reference Signal (SRS) request, Modulation and coding scheme, New data indicator. Redundancy version, Resource allocation header, Resource block assignment, PDSCH RE mapping and Quasi-Co-Location indicator, and/or Antenna port(s) and number of layers, etc.

[0097] In some embodiments, at 704, the serving TP may be configured to transmit to UE 120 the configured one or more DCIs, e.g., the primary DCI and the secondary DCI, via a PDCCH and/or an ePDCCH based on a search space of the UE 120. For example, the serving TP may transmit to UE 120 the primary DCI and the secondary DCI via the PDCCH and/or the ePDCCH to the search space of the UE 120. The PDCCH and/or the ePDCCH may each carry one or more information bits in the one or more configured DCI(s), e.g., the primary DCI and/or the secondary DCI.

[0098] For example, at 704, the serving TP may transmit the primary DCI and the secondary DCI, e.g., via the transmitter 112. In some embodiments, the two DCIs may both be located at a search space of UE 120. In some embodiments, a first search space may be used for the primary DCI and/or a secondary search space may be configured for the secondary DCI. The CCE resources for UE 120 may be divided into two parts: one for the primary DCI and the other for the secondary DCI. The serving TP and/or the assistant TP may configure the CCE resource division via RRC signaling, e.g., via a 1 -bit trigger or implicitly in a transmission mode configuration, e.g., in communication standards or protocols. In some embodiment, the CCE aggregation levels for the two DCIs may be the same to reduce a number of blind detection. In some other embodiments, the CCE aggregation level for the two DCIs may not be the same.

[0099] In some embodiments, at 704, a corresponding TP may transmit the one or more configured DCIs, e.g., primary DC! and secondary DCT, individually. For example, the serving TP may transmit the primary DCI and/or the assistant TP may transmit the secondary DO. In some embodiments, for UE 120 in beam aggregation, the assistant TP may use the same radio network temporary identity (RNTI) as that of the serving TP. In some other embodiments, in response to receiving a physical random access channel (P ACH) signal from UE 120, the assistant TP may configure a different RNTI value via RRC signaling or via radio access response (RAR), e.g., if multiple access procedures for UE 120 are used. In some embodiments, the CCE aggregation level for the two DCIs may not be the same. In some other embodiments, the CCE aggregation level for the two DCIs may be the same to reduce a number of blind detection.

[00100] In some embodiments, eNB 110 may further provide, e.g., via the configuring module 112a, a PDSCH based on downlink control signaling in the DCI and may transmit the PDSCH to UE 120.

[00101] While Figure 7 illustrates an example of the primary DO and the secondary DO in accordance with some embodiments, in some embodiments, one or more DCIs may be used. While Figure 7 illustrates an example of a codeword in a DCI in accordance with some embodiments, in some embodiments, one or more codewords may be used.

[00102] Figure 8 schematically illustrates another example of one or more processes according to various embodiments. In some embodiments, the one or more processes may be performed by UE 120 or electronic device circuitry 200, e.g., controllers 124 and/or control circuitry 214, a transmitter and/or a receiver. In some embodiments, the one or more processes may be used by the UE 120 m beam aggregation mode. In some embodiments, controller 124 or control circuitry 214 may comprise a first decoder or decoding circuitry 126a that may perform a blind decoding (e ,g., at 804) on a PDCCH and/or an ePDCCH from eNB 1 10 to provide one or more DCIs and/or one or more CCE aggregation level each corresponding to a DCI. In some embodiments, the controller 116 or the controller 214 may comprise a second decoder or decoding circuitry 126b that may perform a decoding (e.g., at 806) on the one or more DOs.

[00103] At 802, UE 120 may receive, e.g., via the receiver 126, from eNB 1 10 downlink control information or indicator (DO) on a PDCCH and/or an ePDCCH. For example, the PDCCH and/or the ePDCCH may cany one or more information bits in the downlink control information. [00104] At 804, controller 124 may perform a PDCCH blind decoding and/or an ePDCCH blind decoding in a search space of the UE 120 to obtain one or more DCIs carried by the PDCCH and/or ePDCCH. In some embodiments, controller 124 may calculate a search space of UE 120 based on the Radio Network Temporary Identity (RNTI) of UE 120 and/or a number of subframes associated with a PDCCH and/or ePDCCH. In some embodiments, eNB 1 10 may enable a second search space of UE 120 for the secondary DO by the RRC signaling, e.g., via transmitter 112. In some embodiments, controller 114 of eNB 110 and/or controller 124 of UE 120 may calculate a search space of UE 120. In some embodiments, a search space of UE 120 may be used to detect and/or demodulate the ePDCCH associated with a UE specific reference signal (UE-RS), wherein the search space for the UE-RS may be different from that for a CRS. In some embodiments, UE 120 may perform a blind decoding in a search space of the UE 120 associated with a DO to obtain a CCE aggregation level corresponding to the DO.

[00105] In some embodiments, controller 124 may perform a PDCCH blind decoding in different search spaces of the UE 120 to obtain a primary DO and a secondary DO, respectively. In some embodiments, controller 124 may perform an ePDCCH blind decoding in different search spaces of the UE 120 to obtain a primary DO and a secondary DO, respectively. In some embodiments, controller 124 may perform a PDCCH blind decoding in different search spaces of the UE 120 to obtain a CCE aggregation level corresponding to the primary DO and another aggregation level corresponding to a secondary DO. Similarly, controller 124 may perform an ePDCCH blind decoding in different search spaces of the UE 120 for the primary DO and the secondary DO to obtain a CCE aggregation level corresponding to the primary DO and a CCE aggregation level corresponding to the secondary DO In some embodiments, the controller 124 and/or the control circuitry 224 may comprise the blind decoder 124a to perform one or more blind decodings according to various embodiments.

[00106] In some embodiments, the controller 124 may perform a PDCCH/ePDCCH blind decoding in a search spaces of the UE 120 corresponding to the primary DO to obtain one or more control information or configurations in the primary DO. In some embodiments, the controller 124 may perform a PDCCH/ePDCCH blind decoding in a search space of the UE 120 corresponding to the secondary DO to obtain one or more control information or configurations in the secondary DO.

[00107] At 806, controller 124 may further decode each DO obtained via a blind decoding to obtain various control information and/or configurations in the DO. In some embodiments, the control information and/or the configurations comprise one or more control information and/or configurations as described in the disclosure. In some embodiments, the controller 124 and/or the control circuitry 224 may comprise the decoder 124b to decode a DO to obtain a content in the DCI according to various embodiments. In another embodiment, the UE 120 may receive, e.g., via the receiver 126, a PDSCH based on the content in the DCI. in some embodiments, controller 124 may decode the primary DCI and the second DCI to obtain a 1-bit indicator for each of the primary DCI and the secondary DCI, wherein the 1-bit may each indicate w hether the DCI corresponds to the serving TP or the assistant TP.

[00108] Embodiments described herein may be implemented into a system using any suitably configured hardware, software and/or firmware. Figure 9 illustrates, for one embodiment, an example system comprising radio frequency (RF) circuitry 930, baseband circuitry 920, application circuitry 910, front end module (FEM) circuitry 960, and/or antenna(s) 950, coupled with each other ai least as shown. In some embodiments, die example system may further comprise one or more of memory /storage, display, camera, sensor, and input/output (I/O) interface, coupled with each other at least as shown. For one embodiment, Figure 9 illustrates example components of a UE device 900 in accordance with some embodiments.

[00109] The application circuitry 910 may include one or more application processors. For example, the application circuitry 910 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors,

application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[00110] The baseband circuitry 920 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 920 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 930 and to generate baseband signals for a transmit signal path of the RF circuitry 930. Baseband processing circuity 920 may interface with the application circuitry 910 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 930. For example, in some embodiments, the baseband circuitry 920 may include a second generation (2G) baseband processor 920a, a third generation (3G) baseband processor 920b, a fourth generation (4G) baseband processor 920c, and/or other baseband processors) 920d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 920 (e.g., one or more of baseband processors) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 930. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 920 may include Fast-Fourier Transform (FFT), preceding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 920 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[00111] In some embodiments, the baseband circuitry 920 may include elements of a protocol stack such as, for example, elements of an EUTRAN protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or RRC elements. A central processing unit (CPU) 920e of the baseband circuitry 920 may be configured to ran elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry 920 may include one or more audio digital signal processor(s) (DS P) 92 Of that may include elements for

compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitiy 920 and the application circuitry 910 may be implemented together such as, for example, on a system on a chip (SOC).

[00112] In some embodiments, the baseband circuitry 920 may provide for

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

[00113] RF circuitry 930 may enable communication with wireless networks

using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 930 may include switches, filters, amplifiers, etc. to facilitate the

communication with the wireless network. RF circuitry 930 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 960 and provide baseband signals to the baseband circuitry 920. RF circuiti 930 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 920 and provide RF output signals to the FEM circuitry 960 for transmission. [00114] In some embodiments, the RF circuitry 930 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitr ' 930 may include mixer circuitry 930a, amplifier circuitry 930b and/or filter circuitry 930c. The transmit signal path of the RF circuitry 930 may include filter circuitry 930c and/or mixer circuitry 930a.

[00115] RF circuitry 930 may also include synthesizer circuitry 930d for synthesizing a frequency for use by the mixer circuitry 930a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 930a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 960 based on the synthesized frequency provided by synthesizer circuitry 930d.

[00116] The amplifier circuitry 930b may be configured to amplify the down-converted signals. The filter circuitry 930c may be a lo -pass filter (LPF) or band-pass filter (EPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 920 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 930a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

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

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

[00119] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 930 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 920 may include a digital baseband interface to communicate with the RF circuitry 930.

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

[00121] In some embodiments, the synthesizer circuitry 930d may be a fractional-N synthesizer or a fractional N N+I synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 930d may be a deita-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-Socked loop with a frequency divider.

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

[00123] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the base band circuitiy 920 or the applications processor 910 depending on the desired output frequency. In some embodiments, a divider control input (e.g., X) may be determined from a look-up table based on a channel indicated by the applications processor 910.

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

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

[00126] FEM circuitry 960 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 950, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 930 for further processing. FEM circuitry 960 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 930 for transmission by one or more of the one or more antennas 950.

[00127] In some embodiments, the FEM circuitry 960 may include a TX/RX switch to switch between transmit mode and receive mode operation.

[00128] The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 930). The transmit signal path of the FEM circuitry 960 may include a power amplifier (PA) to amplify- input RF signals (e.g., provided by RF circuitry 930), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 950.

[00129] In some embodiments, the UE 900 comprises a plurality of power saving mechanisms. If the UE 900 is in an RRC Connected s tate, where it is still connected to the eNB as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity . During this state, the device may power down for brief intervals of time and thus save power.

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

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

[00132] In various embodiments, transmit circuitry, control circuitr ', and/or receive circuitry discussed or described herein may be embodied in whole or in part in one or more of the RF circuitry 930, the baseband circuitry 920, FEM circuitry 960 and/or the application circuitry 910, 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 electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules or units,

[00133] In some embodiments, some or all of the constituent components of the

baseband circuitry 920, the application circuitry 910, and/or the memory/storage may be implemented together on a system on a chip (SOC).

[00134] Memory/storage may be used to load and store data and/or instructions, for example, for system. Memory/storage for one embodiment may include any combination of suitable volatile memory (e.g., dynamic random access memory (DRAM)) and/or non-volatiie memory (e.g., Flash memory).

[00135] In various embodiments, the I/O interface may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.

[00136] In various embodiments, the sensor may include one or more sensing

devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensor may include, but are not limited to, a gyro sensor,

an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF

circuitry to communicate with components of a positioning network, e.g., a global

positioning system (GPS) satellite.

[00137] In various embodiments, the display may include a display (e.g., a liquid crystal display, a touch screen display, etc.).

[00138] In various embodiments, the system may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system, may have more or less components, and/or different architectures.

[00139] EXAMPLES [00140] Example 1 may include an apparatus of an evolved NodeB (eNB), comprising: a memory to store one or more instructions; and a controller to execute one or more instructions in the memory to configure one or more downlink control information (DCI) messages that individual DCI message(s) in the one or more DCI messages comprises a codeword corresponding to an aggregated beam in one or more aggregated beams associated with a user equipment (UE), wherein the codeword to comprise one or more codeword specific control information comprising one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and/or a number of layers; and provide to the UE the one or more DCI messages via a physical downlink control channel (PDCCH) or an enhanced PHDCCH (ePDCCH) based on a search space of the UE.

[00141] Example 2 may comprise the subject matter of Example 1 or some other examples described herein, wherein the controller further to configure a primary DCI message and a secondary DCI message of the one or more DCI messages to have the same DCI format.

[00142] Example 3 may comprise the subject matter of any one of Examples 1 and 2 or some other examples described herein, wherein the controller further to configure the primary DCI message or the secondary DCI message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, a and the antenna port information and/or the number of layers.

[00143] Example 4 may comprise the subject matter of any one of Examples 1 to 3 or some other examples described herein, wherein the controller is further to: configure the primary DCI message or the secondary DCI message to comprise one or more same codeword specific control information.

[00144] Example 5 may comprise the subject matter of any one of Examples 1 to 4 or some other examples described herein, wherein the controller is further to: configure a primary DCI message and a secondary DCI message of the one or more DCI messages to have different DCI formats.

[00145] Example 6 may comprise the subject matter of any one of Examples 1 to 5 or some other examples described herein, wherein the controller is further to: configure the primary DCI message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers. [00146] Example 7 may comprise the subject matter of any one of Examples 1 to 6 or some other examples described herein, wherein the controller is further to: configure the secondary DCI message to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.

[00147] Example 8 may comprise the subject matter of any one of Examples 1 to 7 or some other examples described herein, wherein the controller is further to: configure the primary DCI message and the secondary DCI message with the eNB as a serving transmission port (TP), [00148] Example 9 may comprise the subject matter of any one of Examples 1 to 8 or some other examples described herein, wherein the controller is further to: configure the primary DCI message with the eNB as a serving transmission port (TP) or the secondary DCI message with the eNB as an assistant serving TP.

[00149] Example 10 may comprise the subject matter of any one of Examples 1 to 9 or some other examples described herein, wherein the controller is further to: configure the antenna port information in a DCI message of the one or more DCI messages to comprise a 2-bit indicator to indicate a number of antennas in an aggregated beam associated the DCI message.

[00150] Example 1 1 may comprise an apparatus of user equipment, the apparatus comprising: a first decoder to perform a blind decoding on a physical downlink control channel (PDCCH) or an enhanced PDCCH (ePDCCH) from an evolved NodeB (eNB) to obtain a first downlink control information (DCI) message; and a second decoder to decode the first DCI message to obtain a first codeword, wherein the first codeword to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.

[00151] Example 12 may comprise the subject matter of Example 11 or some other examples described herein, wherein the first decoder is further to: perform a blind decoding on the PDCCH or the ePDCCH to obtain a second DCI message, wherein the second DCI message to have the same DCI format as that of the first DCI message.

[00152] Example 13 may comprise the subject matter of any one of Examples 1 1 and 12 or some other examples described herein, wherein the second decoder is further to: decoding the first DCI message or the second DCI message to obtain one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.

[00153] Example 14 may comprise the subject matter of any one of Examples 1 1 to 13 or some other examples described herein, wherein the second decoder is further to: decoding the first DCI message or the second DCI message to obtain one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.

[00154] Example 15 may comprise the subject matter of any one of Examples 11 to 14 or some other examples described herein, wherein the first decoder is further to: perform a blind decoding on die PDCCH or the ePDCCH to obtain a second DCI message, wherein the second DCI message comprises a secondary DCI message, and wherein the first DCI message comprises a primary DCI message that has a DCI format different from that of the secondary DCI message,

[00155] Example 16 may comprise the subject matter of any one of Examples 11 to 15 or some other examples described herein, wherein the second decoder is further to: decoding the primary DCI message to obtain one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.

[00156] Example 17 may comprise the subject matter of any one of Examples 11 to 16 or some other examples described herein, wherein the second decoder is further to: decoding the secondary DCI message to obtain one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.

[00157] Example 18 may comprise the subject matter of any one of Examples 11 to 17 or some other examples described herein, wherem the second decoder is further to: decoding the primary DCI message and the secondary DCI message from the eNB that serves the UE as a serving transmission port (TP).

[00158] Example 19 may comprise the subject matter of any one of Examples 11 to 18 or some other examples described herein, wherein the second decoder is further to: decoding the primary

DCI message from the eNB that serves the UE as a serving transmission port (TP) and the secondary DCI message from another eNB that serves the UE as an assistant serving TP.

[00159] Example 20 may comprise the subject matter of any one of Examples 11 to 19 or some other examples described herein, wherem the second decoder is further to: decoding the first DCI message or the second DCI message to obtain the antenna port information that comprises a 2-bit indicator to indicate a number of antennas in an aggregated beam corresponding to the first DCI message or the second DCI message.

[00160] Example 21 may comprise the subject matter of any one of Examples 11 to 20 or some other examples described herein, wherein the first decoder is further to: perform a blind decoding on the PDCCH or ePDCCH in a first search space of the UE to obtain a first control channel element (CCE) aggregation level corresponding to the first DCI message; and perform a blind decoding on the PDCCH or ePDCCH in a second search space of the UE to obtain a second control channel element (CCE) aggregation level corresponding to the second DCI message.

[00161] Example 22 may comprise the subject matter of any one of Examples 11 to 21 or some other examples described herein, wherein the second decoder is further to: decoding the first DCI to indicate that the first DCI corresponds to a serving transmission port (TP); and decode the second DCI to indicate that the second DCI corresponds to an assistant TP.

[00162] Example 23 may comprise a non-transitory machine-readable medium having instructions, stored thereon, that, when executed cause an evolved NodeB (eNB) to: configure one or more downlink control information (DCI) messages that individual DCI message(s) in the one or more DCI messages comprises a codeword corresponding to an aggregated beam in one or more aggregated beams associated with a user equipment (UE), wherein the codeword to compri se one or more codeword specific control information comprising one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and/or a number of layers; and provide to the UE the one or more DCI messages via a physical downlink control channel (PDCCH) or an enhanced PHDCCH (ePDCCH) based on a search space of the UE.

[00163] Example 24 may comprise the subject matter of Example 23 or some other examples described herein, having instructions, stored thereon, that, when executed cause the eNB further to: configure a primary DCI message and a secondary DCI message of the one or more DCI messages to have the same DCI format.

[00164] Example 25 may comprise the subject matter of any one of Examples 23 and 24 or some other examples described herein, having instructions, stored thereon, that, when executed cause the eNB further to: configure the primary DCI message or the secondary DCI message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.

[00165] Example 26 may comprise the subject matter of Example 23 to 25 or some other examples described herein, having instructions, stored thereon, that, when executed cause the eNB further to: configure a primaiy DCI message and a secondary DCI message of the one or more DCI messages to have different DCI formats.

[00166] Example 27 may comprise the subject matter of any one of Examples 23 to 26 or some other examples described herein, having instructions, stored thereon, that, when executed cause the eNB further to: configure the primary DCI message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.

[00167] Example 28 may comprise the subject matter of any one of Examples 23 to 27 or some other examples described herein, having instructions, stored thereon, that, when executed cause the eNB further to: configure the secondary DCI message to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.

[00168] Example 29 may comprise the subject matter of any one of Examples 23 to 28 or some other examples described herein, having instructions, stored thereon, that, when executed cause the eNB further to: configure the primary DCI message and the secondary DCI message with the eNB as a serving transmission port (TP).

[00169] Example 30 may comprise the subject matter of any one of Examples 23 to 29 or some other examples described herein, having instractions, stored thereon, that, when executed cause the eNB further to: configure the primary DCI message with the eNB as a serving transmission port (TP) or the secondary DCI message with the eNB as an assistant serving TP.

[00170] Example 31 may comprise a method that may be performed by an evolved

NodeB(eNB), comprising: configuring one or more downlink control information (DCI) messages that individual DCI message(s) in the one or more DCI messages comprises a codeword corresponding to an aggregated beam in one or more aggregated beams associated with a user equipment (UE), wherein the codeword to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and/or a number of layers: and providing to the UE the one or more DCI messages via a physical downlink control channel (PDCCH) or an enhanced PHDCCH (ePDCCH) based on a search space of the UE.

[00171 ] Example 31 may comprise the subject matter of Example 30 or some other examples described herein, further comprising: configuring comprise a primary DCI message and a secondary DCI message of the one or more DCI messages to have the same DCI format.

[00172] Example 32 may comprise the subject matter of any one of Examples 30 and 31 or some other examples described herein, further comprising: configuring the primary DCI message or the secondary DCI message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers . [00173] Example 33 may comprise the subject matter of any one of Examples 30 to 32 or some other examples described herein, further comprising: configuring the primar - DCI message or the secondary DCI message to comprise one or more same codeword specific control information.

[00174] Example 34 may comprise the subject matter of any one of Examples 30 to 33 or some other examples described herein, further comprising: configuring comprise a primary DCI message and a secondary DCI message of the one or more DCI messages to have different DCI formats.

[00175] Example 35 may comprise the subject matter of any one of Examples 30 to 34 or some other examples described herein, further comprising: configuring the primary DCI message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.

[00176] Example 36 may comprise the subject matter of any one of Examples 30 to 35 or some other examples described herein, further comprising: configuring the secondary DCI message to comprise one or more codeword specific control information.

[00177] Example 37 may comprise the subject matter of any one of Examples 30 to 36 or some other examples described herein, further comprising: configuring the primary DCI message and the secondary DCI message with the eNB as a serving transmission port (TP).

[00178] Example 38 may comprise the subject matter of any one of Examples 30 to 37 or some other examples described herein, fuither comprising: configuring the primary DCI message with the eNB as a serving transmission port (TP) or the secondary DCI message with the eNB as an assistant serving TP.

[00179] Example 39 may comprise the subject matter of any one of Examples 30 to 38 or some other examples described herein, further comprising: configuring the antenna port information in each DCI message to comprise a 2-bit indicator to indicate a number of antennas in an aggregated beam associated the DCI message .

[00180] Example 40 may comprise the subject matter of any one of Examples 30 to 39 or some other examples described herein, further comprising: configuring the primary DCI to indicate one codeword and one or more fields in a DCI format 2D.

[00181] Example 41 may comprise the subject matter of any one of Examples 30 to 40 or some other examples described herein, further comprising: transmitting the primary DCI and/or the secondary DCI via the PDCCH and/or the ePDCCH.

[00182] Example 42 may comprise the subject matter of any one of Examples 30 to 41 or some other examples described herein, further comprising: transmitting the primary DCI and/or the secondary DCI when the eNB is to server as the serving TP, and/or transmitting the secondary DCI when the eNB is to serve as the assistant TP.

[00183] Example 43 may comprise the subject matter of any one of Examples 30 to 42 or some other examples described herein, wherein for the UE in beam aggregation, the serving TP is to configure a same radio network temporary identity (RNTT) as the assistant TP, or vice versa.

[00184] Example 44 may comprise the subject matter of any one of Examples 30 to 43 or some other examples described herein, further comprising: for the UE in beam aggregation, the serving TP is to configure a different RNTI via radio resource control (RRC) signaling or via radio access response (RAR) in response to receiving a physical random access channel (PRACH) signal from the UE to the serving TP, or vice versa.

[00185] Example 45 may comprise the subject matter of any one of Examples 30 to 44 or some other examples described herein, further comprising transmitting a PDSCH based on downlink control signal in a DCI.

[00186] Example 46 may comprise a method that may be performed by a UE, the method comprising: performing a blind decoding on a physical downlink control channel (PDCCH) or an enhanced PDCCH (ePDCCH) from an evolved NodeB (eNB) in a first search space associated with a first downlink control information (DCI) message to obtain the first DCI message; and decoding the first DCI message to obtain a first codeword, wherein the codeword to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.

[00187] Example 47 may comprise the subject matter of Example 46 or some other examples described herein, further comprising: performing a blind decoding on the PDCCH or the ePDCCH to obtain a second DCI message, wherein the second DCI message to have the same DCI format as that of the first DCI message.

[00188] Example 48 may comprise the subject matter of any one of Examples 46 and 47 or some other examples described herein, further comprising; decoding the first DCI message or the second DCI message to obtain one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.

[00189] Example 48 may comprise the subject matter of any one of Examples 46 and 47 or some other examples described herein, further comprising: decoding the fi rst DCI message or the second DCI message to obtain one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi -co-location (QCL) indicator, antenna port information and a number of layers.

[00190] Example 49 may comprise the subject matter of any one of Examples 46 to 48 or some other examples described herein, further comprising: performing a blind decoding on the PDCCH or the ePDCCH to obtain a second DCI message, wherein the second DCI message comprises a secondary DCI message, and wherein the first DCI message comprises a primary DCI message that has a DCI format different from that of the secondary DCI message.

[00191] Example 50 may comprise the subject matter of any one of Examples 46 to 49 or some other examples described herein, further comprising: decoding the primary DCI message to obtain one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.

[00192] Example 51 may comprise the subject matter of any one of Examples 46 to 50 or some other examples described herein, further comprising: decoding the secondary DCI message to obtain one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.

[00193] Example 52 may comprise the subject matter of any one of Examples 46 to 51 or some other examples described herein, further comprising: decoding the primary DCI message and the secondary DCI message from the eNB that serves the UE as a serving transmission port (TP).

[00194] Example 53 may comprise the subject matter of any one of Examples 46 to 52 or some other examples described herein, further comprising: decoding the primary DCI message from the eNB that serves the UE as a serving transmission port (TP) and the secondary DCI message from another eNB that serves the UE as an assistant serving TP.

[00195] Example 54 may comprise the subject matter of any one of Examples 46 to 53 or some other examples described herein, further comprising: decoding the first DCI message or the second DCI message to obtain the antenna port information that comprises a 2-bit indicator to indicate a number of antennas in an aggregated beam corresponding to the first DCI message or the second DCI message.

[00196] Example 55 may comprise the subject matter of any one of Examples 46 to 54 or some other examples described herein, further comprising: performing a blind decoding on the PDCCH or ePDCCH in a first search space of the UE to obtain a first control channel element (CCE) aggregation level corresponding to the first DCI message; and performing a blind decoding on the PDCCH or ePDCCH in a second search space of the UE to obtain a second control channel element (CCE) aggregation level corresponding to the second DCI message. [00197] Example 56 may comprise the subject matter of any one of Examples 46 to 55 or some other examples described herein, further comprising; decoding the first DCI to indicate that the first DCI corresponds to a serving transmission port (TP); and decoding the second DCI to indicate that the second DCI corresponds to an assistant TP.

[00198] Example 57 may comprise the subject matter of any one of Examples 46 to 56 or some other examples described herein, further comprising: receiving from the eNB information indicative of a second search space for a secondary DCI via RRC.

[00199] Example 58 may comprise the subject matter of any one of Examples 46 to 57 or some other examples described herein, wherein a different search space is used to detect and/or demodulate the ePDCCH associated with a UE specific reference signal (UE-RS) relative to a cell-specific reference signal (CRS).

[00200] Example 59 may comprise the subject matter of any one of Examples 46 to 58 or some other examples described herein, further comprising: performing a blind decoding in a search space of the UE to obtain a CCE aggregation level for UE.

[00201] Example 60 may comprise the subject matter of any one of Examples 46 to 59 or some other examples described herein, further comprising: performing a blind decoding in a first search space corresponding to the primary DCI to obtain a first CCE aggregation level for the primary DCI and performing a blind decoding in a second search space corresponding to the secondary DCI to obtain a first CCE aggregation level for the secondary DCI.

[00202] Example 61 may comprise the subject matter of any one of Examples 46 to 60 or some other examples described herein, further comprising: calculating a search space of UE based on a radio network temporary identity (RNTI) of the UE and a number of subframes.

[00203] Example 62 may comprise the subject matter of any one of Examples 46 to 61 or some other examples described herein, wherein the CCE resources for a search space of UE to comprise a first portion for the primary DCI and a second portion for the secondary DCI, and wherein the CCE resource division is to be configured by the serving TP and/or the assistant TP via RRC.

[00204] Example 63 may comprise an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 30-45 or 46 to 62, or any oilier method or process described herein.

[00205] Example 64 may comprise 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 30-45 or 46 to 62, or any other method or process described herein.

[00206] Example 65 may comprise an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in one or more elements of a method described in or related to any of examples 30-45 or 46 to 62, or any other method or process described herein.

[00207] Example 66 may comprise a method, technique, or process described in or related to any of examples 30-45 or 46 to 62, or any other method or process described herein.

[00208] Example 67 may comprise 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 of the electronic de vice, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 30-45 or 46 to 62, or portions thereof.

[00209] Example 68 may comprise a method of communicating in a wireless network as shown and described herein.

[00210] Example 69 may comprise a system to provide wireless communication as shown and described herein.

[00211] Example 70 may comprise a device to provide wireless communication as shown and described herein.

[00212] 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 electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules or units.

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

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

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

[00216] Reference throughout this specification to "an example " means that a particular feature, structure, or characteristic described in connection with the example is comprised in at least one embodiment of the present disclosure. Thus, appearances of the phrases "in an example" in various places throughout tins specification are not necessarily ail referring to the same embodiment.

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

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

[00219] Wlnle the forgoing examples are illustrative of the principles of the present disclosure in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation may be made without the exercise of inventive faculty, and without departing from the principles and concepts of the disclosure , Accordingly, it is not intended that the disclosure be limited, except as by the claims set forth below.

[00220] Wlnle the processes of Figures 4, 5, 7 and 8 are illustrated to comprise a sequence of processes, in some embodiments, the one or more processes may be performed in a different order.

[00221 ] While certain features of the disclosure have been described with reference to embodiments, the description is not intended to be construed in a limiting sense. Various modifications of the embodiments, as well as other embodiments of the disclosure, which are apparent to persons skilled in the art to which the disclosure pertains are deemed to lie within the spirit and scope of the disclosure.

Claims

What is claimed is:
1. An apparatus of an e volved NodeB (eNB), comprising:
a memory to store one or more instructions; and
a controller to execute one or more instructions in the memory to:
configure one or more downlink control information (DCI) messages that individual DCI message(s) in the one or more DCI messages comprises a codeword corresponding to an aggregated beam in one or more aggregated beams associated with a user equipment (UE), wherein the codeword to comprise one or more codeword specific control information comprising one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and/or a number of layers; and
provide to the UE the one or more DCI messages via a physical downlink control channel (PDCCH) or an enhanced PHDCCH (ePDCCH).
2. The apparatus of claim 1 , wherein the controller is further to:
configure a primary DCI message and a secondary DCI message of the one or more DCI messages to have the same DCI format.
3. Hie apparatus of claim 2, wherein the controller is further to:
configure the primary DCI message or the secondary DCI message to comprise one or more of a earner indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.
4. The apparatus of any one of claims 2 or 3, wherein the controller is further to:
configure the primary DCI message or the secondary DCI message to comprise the same codeword specific control information.
5. The apparatus of claim 1 , wherein the controller is further to:
configure a primary DCI message and a secondary DCI message of the one or more DCI messages to have different DCI formats.
6. The apparatus of claim 5, wherein the controller is further to: configure the primary DC! message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.
7. The apparatus of claims 5 or 6, wherein the controller is further to:
configure the secondary DCI message to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers .
8. The apparatus of any one of claims 2 to 7, wherein the controller is further to:
configure the primary DCI message and the secondary DCI message with the eNB as a serving transmission port (TP).
9. The apparatus of any one of claims 2 to 7, wherein the controller is further to:
configure the primary DCI message with the eNB as a serving transmission port (TP) or the secondary DCI message with the eNB as an assistant serving TP.
10. The apparatus of any one of claims 1 to 9, wherein the controller is further to:
configure the antenna port information in a DCI message of the one or more DCI messages to comprise a 2-bit indicator to indicate a number of antennas in an aggregated beam associated the DCI message.
11. An apparatus of user equipment, the apparatus comprising:
a first decoder to perform, a blind decoding on a physical downlink control channel (PDCCH) or an enhanced PDCCH (ePDCCH) from an evolved NodeB (eNB) to obtain a first downlink control information (DCI) message; and
a second decoder to decode the first DCI message to obtain a first codeword, wherein the first codeword to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of lay ers.
12, The apparatus of claim 1 1 , wherein the first decoder is further to: perform a blind decoding on the PDCCH or the ePDCCH to obtain a second DC1 message, wherein the second DCI message to have the same DCI format as that of the first DC! message.
13, The apparatus of claim 12, wherein the second decoder is further to:
decode the first DCI message or the second DCI message to obtain one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.
14. The apparatus of any one of claims 12 or 13, wherein the second decoder is further to: decode the first DCI message or the second DCI message to obtain one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.
15. The apparatus of claim 11, wherein the first decoder is further to:
perform a blind decoding on the PDCCH or the ePDCCH to obtain a second DCI message, wherein the second DCI message comprises a secondary DCI message, and wherein the first DCI message comprises a primary DCI message that has a DCI format different from that of the secondaiy DCI message.
16. The apparatus of claim 15, wherein the second decoder is further to:
decode the primary DCI message to obtain one or more of a earner indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.
17. The apparatus of claims 15 or 16, wherein the second decoder is further to:
decode the secondary DCI message to obtain one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.
18. The apparatus of any one of claims 12 to 17, wherein the second decoder is further to: decode the primary DCI message and the secondary DCI message from the eNB that serves the UE as a serving transmission port (TP).
19. The apparatus of any one of claims 12 to 18, wherein the second decoder is further to: decode the primary DCI message from the eNB that serves the UE as a serving transmission port (TP) and the secondary DCI message from another eNB that serves the UE as an assistant sendng TP.
20. The apparatus of any one of claims 12 to 19, wherein the second decoder is further to: decode the first DCI message or the second DCI message to obtain the antenna port information that comprises a 2 -bit indicator to indicate a number of antennas in an aggregated beam corresponding to the first DCI message or the second DCI message.
21. The apparatus of any one of claims 12 to 20, wherein the first decoder is further to: perform a blind decoding on the PDCCH or ePDCCH in a first search space of the UE to obtain a first control channel element (CCE) aggregation level corresponding to the first DCI message; and
perform a blind decoding on the PDCCH or ePDCCH in a second search space of the UE to obtain a second control channel element (CCE) aggregation level corresponding to the second DCI message.
22. The apparatus of any one of claims 12 to 21, wherein the second decoder is further to: decode the first DCI to indicate that the first DCI corresponds to a serving transmission port (TP); and
decode the second DCI to indicate that the second DCI corresponds to an assistant TP,
23. A machine-readable medium having instructions, stored thereon, that, when executed cause an evolved NodeB (eNB) to:
configure one or more downlink control information (DCI) messages that individual DCI message(s) in the one or more DCI messages comprises a codeword corresponding to an aggregated beam in one or more aggregated beams associated with a user equipment (UE), wherein the codeword to comprise one or more codeword specific control information comprising one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and/or a number of layers; and
provide to the UE the one or more DCI messages via a physical downlink control channel (PDCCH) or an enhanced PHDCCH (ePDCCH) based on a search space of the UE.
24. The machine-readable medium of 23 having instructions, stored thereon, that, when executed cause the eNB further to:
configure a primary DC! message and a secondary DCI message of the one or more DCI messages to have the same DCI format.
25. The machine-readable medium of 23 or 24 having instructions, stored thereon, that, when executed cause the eNB further to:
configure the primary DCI message or the secondary DCI message to comprise one or more of a earner indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.
26. The machine-readable medium of 23 having instructions, stored thereon, that, when executed cause the eNB further to:
configure a primary DCI message and a secondary DCI message of the one or more DCI messages to have different DCI formats.
27. i lie machine-readable medium of 26 having instructions, stored thereon, that, when executed cause the eNB further to:
configure the primary DCI message to comprise one or more of a carrier indicator, a transmit power control (TPC) command, a downlink assignment index, a hybrid automatic repeat request (HARQ) process number, a sounding reference signal (SRS) request, and the antenna port information and/or the number of layers.
28. The machine-readable medium of 26 or 27 having instructions, stored thereon, that, when executed cause the eNB further to:
configure the secondary DCI message to comprise one or more of a resource allocation header, a resource block assignment, a physical downlink shared channel (PDSCH) resource element (RE) mapping, an quasi-co-location (QCL) indicator, antenna port information and a number of layers.
29. The machine-readable medium of any one of 23 to 28 having instructions, stored thereon, that, when executed cause the eNB further to: configure the primary DCI message and the secondary DCI message with the eNB as a serving transmission port (TP).
30. The machine-readable medium of any one of 23 to 28 having instructions, stored thereon, that, when executed cause the eNB further to:
configure the primary DCI message with the eNB as a serving transmission port (TP) or the secondary DCI message with the eNB as an assistant serving TP.
PCT/US2016/028977 2015-12-02 2016-04-22 System and method for downlink control indicator design in beam aggregation system WO2017095470A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201562262304P true 2015-12-02 2015-12-02
US62/262,304 2015-12-02

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW105133681A TW201722182A (en) 2015-12-02 2016-10-19 System and method for downlink control indicator design in beam aggregation system

Publications (1)

Publication Number Publication Date
WO2017095470A1 true WO2017095470A1 (en) 2017-06-08

Family

ID=55949109

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/028977 WO2017095470A1 (en) 2015-12-02 2016-04-22 System and method for downlink control indicator design in beam aggregation system

Country Status (2)

Country Link
TW (1) TW201722182A (en)
WO (1) WO2017095470A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018141164A1 (en) * 2017-09-30 2018-08-09 北京小米移动软件有限公司 Downlink control information transmission method and apparatus
US10091777B1 (en) 2017-03-31 2018-10-02 At&T Intellectual Property I, L.P. Facilitating physical downlink shared channel resource element mapping indicator
WO2019111619A1 (en) * 2017-12-06 2019-06-13 シャープ株式会社 Terminal device, base station device and communication method
US10505697B2 (en) 2016-11-03 2019-12-10 At&T Intellectual Property I, L.P. Facilitating a mobile device specific physical downlink shared channel resource element mapping indicator

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140092829A1 (en) * 2012-09-28 2014-04-03 Seunghee Han Systems and methods for semi-persistent scheduling of wireless communications
WO2014133650A1 (en) * 2013-03-01 2014-09-04 Intel IP Corporation Quasi co-location and pdsch resource element mapping signaling for network assisted interference mitigation
US20150131750A1 (en) * 2013-09-05 2015-05-14 Feng Xue Adaptive sectorization of a spational region for parallel multi-user transmissions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140092829A1 (en) * 2012-09-28 2014-04-03 Seunghee Han Systems and methods for semi-persistent scheduling of wireless communications
WO2014133650A1 (en) * 2013-03-01 2014-09-04 Intel IP Corporation Quasi co-location and pdsch resource element mapping signaling for network assisted interference mitigation
US20150131750A1 (en) * 2013-09-05 2015-05-14 Feng Xue Adaptive sectorization of a spational region for parallel multi-user transmissions

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "View on 5G Radio Technology and Standardization", no. Phoenix, AZ, USA; 20150917 - 20150918, 3 September 2015 (2015-09-03), XP051043620, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/WORKSHOP/Docs/> [retrieved on 20150903] *
None

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10505697B2 (en) 2016-11-03 2019-12-10 At&T Intellectual Property I, L.P. Facilitating a mobile device specific physical downlink shared channel resource element mapping indicator
US10091777B1 (en) 2017-03-31 2018-10-02 At&T Intellectual Property I, L.P. Facilitating physical downlink shared channel resource element mapping indicator
US10342009B2 (en) 2017-03-31 2019-07-02 At&T Intellectual Property I, L.P. Facilitating physical downlink shared channel resource element mapping indicator
WO2018141164A1 (en) * 2017-09-30 2018-08-09 北京小米移动软件有限公司 Downlink control information transmission method and apparatus
WO2019111619A1 (en) * 2017-12-06 2019-06-13 シャープ株式会社 Terminal device, base station device and communication method

Also Published As

Publication number Publication date
TW201722182A (en) 2017-06-16

Similar Documents

Publication Publication Date Title
US9642180B2 (en) Mapping an enhanced physical downlink control channel
EP2761901B1 (en) Mapping an enhanced physical downlink control channel
TWI571090B (en) Notifying a ul/dl configuration in lte tdd systems
US9226278B2 (en) Enhanced physical downlink control channel (ePDCCH)
BE1019928A5 (en) Resource allocation for pucch 1b format with channel selection in a tdd lte-a system.
KR101573160B1 (en) Notifying a ul/dl configuration in lte tdd systems
US10051611B2 (en) Network scheduled device to device communication
JP2018093502A (en) Device, program, and machine readable storage medium
TWI554137B (en) Control channel allocation method, control channel searching method and communication apparatus using the same
US9608777B2 (en) LTE hierarchical burst mode
US20150146585A1 (en) Apparatuses and method using enhanced control channel information for tdd-fdd carrier aggregation
US20140348077A1 (en) Control channel design for new carrier type (nct)
JP6038316B2 (en) Hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook generation for inter-band time division duplex (TDD) carrier aggregation (CA)
EP3544221A1 (en) Dynamic configuration of uplink (ul) and downlink (dl) frame resources for a time division duplex (tdd) transmission
KR101697782B1 (en) Method and apparatus for monitoring control channel in multiple carrier system
JP2015503264A (en) Narrow bandwidth devices in broadband networks
EP3031152B1 (en) Method and system of advanced interference cancellation on pdsch at the ue
WO2015094914A1 (en) Methods, apparatus and systems for interference management in a full duplex radio system
EP2847903A1 (en) Downlink control indication for a stand-alone new carrier type (nct)
KR20170136511A (en) Method, apparatus and system for improving an evolved physical downlink control channel for machine type communication
EP3111569B1 (en) Scheduling for an unlicensed carrier type
US9036580B2 (en) Systems and methods for dynamically configuring a flexible subframe
US20180063820A1 (en) Transmission designs for radio access technologies
US9107212B2 (en) Terminal device for receiving signal in wireless communication system for supporting a plurality of component carriers and method thereof
US9215705B2 (en) Method and apparatus for monitoring control channel in wireless communication system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16721318

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16721318

Country of ref document: EP

Kind code of ref document: A1