DE112017002348T5 - DOUBLE JET TRANSMISSION AND ACK / NACK FEEDBACK MECHANISM FOR PUCCH - Google Patents

Abstract

Techniques to facilitate improvements to PUCCH (Physical Uplink Control Channel) will be discussed. In a first set of techniques, a double or multi-beam transmission may be used to transmit PUCCH. In a second set of techniques, an independent HARQ (Hybrid ARQ (Automatic Repeat Request)) ACK (Acknowledgment) / NACK (Negative Acknowledgment) feedback for more than one TB (Transport Block) can be transmitted in a single symbol.

Description

REFER TO RELATED APPLICATIONS

This application claims the benefit of the provisional U.S. Applications No. 62 / 332,985 , filed on 6 May 2016, entitled "DUAL BEAM TRANSMISSION AND NOVEL ACK / NACK FEEDBACK MECHANISM FOR 5G PUCCH", the contents of which are fully incorporated herein by reference.

TERRITORY

The present disclosure relates to wireless technology and, more particularly, to techniques associated with a PUCCH (Physical Uplink Control Channel) (e.g., 5G (5th generation) PUCCH, etc.), such as double (or more ) and ACK (Acknowledgment) / NACK (Negative Acknowledgment) feedback techniques.

BACKGROUND

Mobile communication has evolved significantly from the early language systems to today's sophisticated integrated communications platform. The next generation 5G (5 th generation) wireless communication system will provide access to information and data sharing across multiple users and applications, anywhere, anytime. 5G is expected to be a unified network / system that aims to serve very diverse and sometimes contradictory performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, 5G will evolve on the basis of Third Generation Partnership Project (3GPP) LTE (Long Term Evolution) Advanced, which will be expanded with additional potential new Radio Access Technologies (RATs) to improve people's lives through better, enrich simple and seamless solutions for wireless connectivity. 5G will enable everything wirelessly connected, delivering fast, rich content and services.

list of figures

• 1 Figure 3 is a block diagram illustrating an example user equipment (UE) that may be used in conjunction with various aspects described herein.
• 2 FIG. 12 is a diagram illustrating example components of a device that may be employed in accordance with various aspects discussed herein.
• 3 FIG. 10 is a diagram illustrating exemplary interfaces of a baseband circuit that may be employed in accordance with various aspects discussed herein.
• 4 Figure 3 is a diagram illustrating an exemplary type of stand-alone TDD subframe structure in DL (downlink) that may be employed in conjunction with various aspects discussed herein.
• 5 FIG. 10 is a block diagram of a system operable on a UE (user equipment) that enables techniques discussed herein for enhancing the PUCCH according to various aspects described herein.
• 6 FIG. 10 is a block diagram of a system that may be employed at a BS (base station) that facilitates techniques discussed herein for improved PUCCH of a UE according to various aspects described herein.
• 7 FIG. 10 is a diagram of an exemplary dual transmission scheme for PUCCH according to various aspects discussed herein.
• 8th FIG. 10 is an exemplary diagram of a subframe showing resources configured for double beam transmission PUCCH according to various aspects discussed herein.
• 9 Figure 10 is a diagram showing an exemplary time of DL HARQ that may be employed in various aspects discussed herein.
• 10 FIG. 12 is a diagram showing examples of localized and distributed transmission modes for HARQ ACK / NACK feedback on PUCCH according to various aspects discussed herein. FIG.
• 11 FIG. 10 is a diagram of examples of PUCCH resources for a relatively large number of HARQ ACK / NACK feedbacks according to various aspects discussed herein. FIG.
• 12 FIG. 10 is a flowchart of an example method that facilitates PUCCH double or multi-beam transmission to a UE according to various aspects discussed herein.
• 13 FIG. 10 is a flow chart of an example method that may be employed at a BS that enables PUCCH double or multi-beam transmission of one or more UEs according to various aspects discussed herein.
• 14 FIG. 10 is a flowchart of an example method that facilitates fast HARQ ACK / NACK feedback techniques to a UE according to various aspects discussed herein.
• 15 FIG. 10 is a flow diagram of an example method useable by a BS that enables HARQ ACK / NACK feedback from a UE according to various aspects discussed herein.

DETAILED DESCRIPTION

The present disclosure will now be described with reference to the accompanying drawing figures, wherein like reference numerals will be used to refer to like elements throughout, and the illustrated structures and apparatus are not necessarily drawn to scale. As used herein, the terms "component", "system", "interface" and the like are intended to refer to a computer-related entity, hardware, software (eg, in execution), and / or firmware. For example, a component may be a processor (eg, a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer , a tablet PC and / or a user device (eg mobile phone, etc.) with a processing device. By way of illustration, an application running on a server and the server itself may be a component. One or more components may be in a process, and a component may be located on a computer and / or distributed between two or more computers. A set of elements or a set of other components may be described herein, with the term "set" being construed as "one or more".

Further, these components may be executed by various computer-readable storage media storing various data structures, such as a module. The components may communicate via local and / or remote processes, such as a signal having one or more data packets (eg, data from one component communicating with another component in a local system, distributed system, and / or over a network such as the Internet, a local area network, a wide area network, or a similar network with other systems via the signal).

As another example, a component may be a device having specific functionality provided by mechanical parts operated by electrical or electronic circuits, wherein the electrical or electronic circuit is controlled by a software application or firmware application that is one or more Processors running, can be operated. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware application. As still another example, a component may be a device that provides specific functionality through electronic components without mechanical parts; the electronic components may include one or more processors therein for executing software and / or firmware that at least partially imparts the functionality of the electronic components.

The use of the word "exemplary" is intended to represent concepts in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive or rather than an exclusive or. That is, unless stated otherwise or clear from the context, "X is A or B" is intended to mean any of the natural inclusive permutations. That is, if XA is on; XB uses; or X uses both A and B, then "X sets A or B" is satisfied in each of the above cases. In addition, the indefinite articles "one, one, one" as used in this application and the appended claims should be broadly construed as "one or more" unless otherwise stated or understood from the context to be directed to a singular form be. To the extent that the terms "having,""having,""having,""having,""having," or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive a way similar to the term "comprising". In addition, in situations where one or more numbered items are being discussed (eg, a "first X", a "second X", etc.), generally the one or more numbered items may be different or the same, although in FIG In some situations the context may indicate that they are different or that they are the same.

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

Embodiments described herein may be implemented in a system using any suitably configured hardware and / or software. 1 shows an architecture of a system 100 a network according to some embodiments. The system 100 is a user device (UE) 101 and a UE 102 shown illustrated. The UEs 101 and 102 are represented as smartphones (eg, portable touch-screen computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, Desktop computer, wireless handsets or any computing device having a wireless communication interface.

In some embodiments, each of the UEs 101 and 102 an Internet of Things (IoT) UE that may comprise a network access layer designed for low-power loT applications using short-lived UE connections. An IoT UE may use technologies such as Machine-to-Machine (M2M) or Machine Type Communication (MTC) to communicate with an MTC server or device via a Public Land Mobile Network (PLMN), Proximity-Based Service (PLMN). ProSe) or device-to-device (D2D) communication, sensor networks or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. A loT network describes interconnected IoT UEs that may have unique identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UEs can run background applications (eg keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

The UEs 101 and 102 can be configured to B. to communicate with a radio access network (RAN-Radio Access Network) 110 communicatively - the RAN 110 can z. B. Evolved UMTS (Evolved Universal Mobile Telecommunications System) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN) or another type of RAN. The UEs 101 and 102 use each connections 103 and 104 each of which includes a physical communication interface or layer (discussed in more detail below); in this example are the links 103 and 104 shown as an air interface to allow communicative coupling, and may be consistent with cellular communication protocols, such as a Global System for Mobile Communications (GSM), a Code Division Multiple Access (CDMA) network protocol, a push to-talk (PTT) protocol, a PTT-over-cellular (POC) protocol, a UMTS protocol (Universal Mobile Telecommunications System), a 3GPP LTE protocol (Long Term Evolution), a 5G protocol (Protocol 5th generation), a new radio protocol (NR-New Radio) and the like.

In this embodiment, the UEs 101 and 102 Continue to exchange communication data directly via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a Sidelink interface comprising one or more logical channels, including a physical sidelink control channel (PSCCH), a physical shared link channel (PSSCH), a physical sidelink discovery channel (PSDCH ) and a physical Sidelink Broadcast Channel (PSBCH), but not limited thereto.

The UE 102 is shown configured over the connection 107 to an access point (AP) 106 accesses. The connection 107 may include a local wireless connection such as A connection that is consistent with any IEEE 802.11 protocol, where the AP 106 would include a WiFi® router (wireless fidelity router). In this example, the AP is 106 shown so that he is connected to the Internet is connected without being connected to the core network of the wireless system (described in more detail below).

The RAN 110 may include one or more access nodes containing the connections 103 and 104 enable. These Access Nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, etc., and may be ground stations (eg, terrestrial access points) or satellite stations covering a coverage within a geographic area (e.g., a cell). The RAN 110 may include one or more RAN nodes for providing macrocells, e.g. For example, macro RAN nodes 111 , and one or more RAN nodes for providing femto cells or picocells (e.g., cells with smaller coverage areas, lower user capacity or higher bandwidth than macro cells), e.g. B. low power (LP) RAN nodes 112 include.

Each of the RAN nodes 111 and 112 may terminate the air interface protocol and may be the first contact point for the UEs 101 and 102 be. In some embodiments, each of the RAN nodes may 111 and 112 different logical functions for the RAN 110 These include, but are not limited to, Radio Network Control (RNC) functions such as Radio Bearer Management, Dynamic Uplink and Downlink Radio Resource Management, and Data Packet Planning and Mobility Management.

According to some embodiments, the UEs 101 and 102 be configured using orthogonal frequency division multiplex (OFDM) communication signals with each other or with any of the RAN nodes 111 and 112 communicate over a multicarrier communication channel according to various communication techniques, such as Orthogonal Frequency Division Multiplexing (OFDMA) communication technology (e.g., for downlink communications) or a single-carrier Frequency Division Multiplexing (SC-FDMA) communication technique (eg, uplink). and ProSe or Sidelink communications), although the scope of the embodiments is not limited in this regard. The OFDM signals may comprise a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource lattice may be for downlink transmissions from any of the RAN nodes 111 and 112 to the UEs 101 and 102 while uplink transmissions can use similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency-level representation is a common practice for OFDM systems, making them intuitive for radio resource allocation. Each column and row of the resource grid corresponds to an OFDM symbol or an OFDM subcarrier. The duration of the resource grid in the time domain corresponds to a slot in a radio frame. The smallest time-frequency unit in a resource grid is called a resource element. Each resource grid includes a number of resource blocks that describe the mapping of particular physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest amount of resources that can currently be allocated. There are several different physical downlink channels that are transmitted using such resource blocks.

The physical shared downlink channel (PDSCH) may provide user data and higher level signaling to the UEs 101 and 102 wear. The physical downlink control channel (PDCCH) may, among other things, carry information about the transport format and the resource allocations associated with the PDSCH channel. He can do the UEs 101 and 102 also provide information about the transport format, resource allocation, and Hybrid Automatic Repeat Request (H-ARQ) information related to the shared uplink channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) at each of the RAN nodes 111 and 112 based on channel quality information received from one of the UEs 101 and 102 be fed back. The downlink resource allocation information may be transmitted on the PDCCH corresponding to each of the UEs 101 and 102 is used (for example, is assigned).

The PDCCH may use control channel elements (CCEs) to convey the control information. Prior to mapping to resource elements, the complex-valued PDCCH symbols may first be organized into quads, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four QPSK symbols (Quadrature Phase Shift Keying - quadrature phase shift keying) can be assigned to each REG. The PDCCH may be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. In LTE, four or more different PDCCH formats with different CCE numbers can be defined (eg, degree of aggregation, L = 1, 2, 4, or 8).

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

The RAN 110 is communicative with a core network (CN) 120 coupled - via an S1 interface 113 , In embodiments, the CN 120 an Evolved Packet Core (EPC) network, a NextGen Packet Core (NPC) network, or any other type of CN. In this embodiment, the S1 interface is 113 divided into two parts: the S1-U interface 114 , the traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122 and the S1 Mobility Management Unit (MME) interface 115 providing a signaling interface between the RAN nodes 111 and 112 and MMEs 121 is, carries.

In this embodiment, the CN comprises 120 the MMEs 121 , the S-GW 122 , the Packet Data Network (PDN) Gateway (P-GW) 123 and a home subscriber server (HSS) 124 , The MMEs 121 may be similar in function to the control level of outdated General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 can manage mobility issues when accessing gateway selections and tracking range list management. The HSS 124 may include a database for network users, including subscriber-related information, to assist the network entities in handling communication sessions. The CN 120 can have one or more HSSs 124 Depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc. For example, the HSS 124 Provide support for routing / roaming, authentication, authorization, name / address resolution, location dependencies, and more.

The S-GW 122 can be the S1 interface 113 to the RAN 110 stop and route data packets between the RAN 110 and the CN 120 , In addition, the S-GW 122 be a local mobility anchor point for inter-RAN node handoffs and also provide an anchor for inter-3GPP mobility. Other responsibilities include lawful interception, charging and enforcing policy enforcement.

The P-GW 123 can terminate an SGi interface towards a PDN. The P-GW 123 can data packets between the EPC network 123 and external networks, such as a network that hosts the application server 130 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 125. In general, the application server 130 be an element that offers applications that use IP bearer resources with the core network (for example, UMTS packet service (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 123 communicatively with an application server 130 via an IP communication interface 125 shown coupled. The application server 130 may also be configured to provide one or more communication services (e.g., Voice Over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) to the UEs 101 and 102 over the CN 120 to support.

The P-GW 123 may also be a node for Policy Enforcement and Charging data collection. The Policy and Charging Enforcement Function (PCRF) 126 is the Policy and Charging control of the CN 120 , In a non-roaming scenario, a single PCRF may be present in the Home Public Land Mobile Network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of a UE. In a roaming scenario with local interruption of traffic, two PCRFs may be assigned to the IP-CAN session of a UE: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a visited Public Land Mobile Network (VPLMN). The PCRF 126 can via the P-GW 123 communicatively with the application server 130 be coupled. The application server 130 can the PCRF 126 signal a new service flow and select the appropriate quality of service (QoS) and load parameters. The PCRF 126 may provide this rule in a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and the QoS class of the identifier (QCI) which provides QoS and billing as from the application server 130 specified begins.

2 illustrates example components of a device 200 according to some embodiments. In some embodiments, the device may 200 an application circuit 202 , a baseband circuit 204 , a radio frequency (RF) circuit 206 , a front-end module (FEM) circuit 208, one or more antennas 210 and a power management circuit (PMC) 212, which are coupled together at least as shown. The components of the illustrated device 200 may be included in a UE or a RAN node. In some embodiments, the device may 200 have fewer elements (eg, a RAN node can not have an application circuit 202 and instead have a processor / controller for processing IP data received from an EPC). In some embodiments, the device may 200 additional elements such as memory / memory, display, camera, sensor or input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (eg, the circuits may be included separately in more than one device for cloud RAN (C-RAN) implementations).

The application circuit 202 may include one or more application processors. For example, the application circuit 202 a circuit such as, but not limited to, one or more single-core or multi-core processors. The processor (s) may include any combination of general-purpose processors and dedicated processors (eg, graphics processors, application processors, etc.). The processors may be coupled to or have a random access memory / memory and may be configured to execute instructions stored in the memory / memory to enable various applications or operating systems on the device 200 to run. In some embodiments, processors may be the application circuit 202 Process IP data packets received from an EPC.

The baseband circuit 204 may include, but is not limited to, a circuit such as one or more single core or multi-core processors. The baseband circuit 204 may include one or more baseband processors or control logic for processing baseband signals received from a receive signal path of the RF circuit 206 and for generating baseband signals for a transmission signal path of the RF circuit 206 contain. The baseband processing circuit 204 can with the application circuit 202 for generating and processing the baseband signals and for controlling operations of the RF circuit 206 be connected via an interface with it. For example, the baseband circuit 204 in some embodiments, a baseband processor 204A the third generation ( 3G) , a baseband processor 204B the fourth generation ( 4G) , a baseband processor 204C the fifth generation ( 5G) or other baseband processors 204D developed for other existing generations, generations in development or in the future (eg second generation ( 2G) sixth generation ( 6G) etc.). The baseband circuit 204 (eg, one or more of the baseband processors 204A D) can handle various radio control functions that require communication with one or more radio networks via the RF circuit 206 enable. In other embodiments, some or all of the functionality of the baseband processors may be used 204A-D contained in modules that are in memory 204G stored and via a central processing unit (CPU) 204E be executed. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit may be the baseband circuit 204 a Fast Fourier Transform (FFT), precoding or constellation mapping / demapping functionality. In some embodiments, the encoding / decoding circuit may be the baseband circuit 204 Convolutional code, tailbiting convolutional code, turbo, Viterbi or low density parity check (LDPC) encoding / decoding functionality. Embodiments of modulation / demodulation and encoding / decoding functionality are not limited to these examples, and may have other suitable functionalities in other embodiments.

In some embodiments, the baseband circuitry may be 204 one or more digital audio signal processor (s) (DSP) 204F exhibit. The audio DSP 204F may include compression / decompression and echo cancellation elements and may include other suitable processing elements in other embodiments. Baseband circuit components may, in some embodiments, be suitably combined into a single chip, a single chipset, or disposed on a same circuit board. In some embodiments, some or all of the individual components may be the baseband circuit 204 and the application circuit 202 be implemented together, such. On a system-on-chip (SOC system on a chip).

In some embodiments, the baseband circuitry may be 204 provide communication that is compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may be 204 support communication with a developed Universal Terrestrial Radio Access Network (E-UTRAN) or other Wireless Urban Area Networks (WMAN), a Wireless Local Area Network (WLAN), a Wireless Personal Area Network (WPAN). Embodiments in which the baseband circuit 204 is configured to support radio communications from more than one wireless protocol, may be referred to as multi-mode baseband circuits.

The RF circuit 206 may enable communication with wireless networks that use modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit 206 Switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 206 may comprise a receive signal path comprising a circuit for downconverting RF signals received from the FEM circuit 208 and to provide baseband signals to the baseband circuit 204 can have. The RF circuit 206 may also comprise a transmission signal path, which may comprise a circuit for upconverting baseband signals received from the baseband circuit 204 and RF output signals for transmission to the FEM circuit 208 provide.

In some embodiments, the receive signal path of the RF circuit 206 a mixer circuit 206a , an amplifier circuit 206b and a filter circuit 206c exhibit. In some embodiments, the transmission signal path of the RF circuit 206 a filter circuit 206c and a mixer circuit 206a exhibit. The RF circuit 206 can also be a synthesizer circuit 206d for synthesizing a frequency for use by the mixer circuit 206a the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 206a the receive signal path to be configured to receive RF signals from the FEM circuit 208 are received, based on the synthesized frequency provided by the synthesizer circuit 206d is provided to convert downwards. The amplifier circuit 206b may be configured to amplify the down-converted signals, and the filter circuit 206c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the downconverted signals to generate output baseband signals. The output baseband signals may be the baseband circuitry 204 be provided for further processing. In some embodiments, the output baseband signals may be null frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuit 206a of the received signal path comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuit 206a of the transmit signal path, input baseband signals based on the synthesized frequency provided by the synthesizer circuit 206d is to be extrapolated to RF output signals for the FEM circuit 208 to generate. The baseband signals may be from the baseband circuitry 204 can be provided and through the filter circuit 206c be filtered.

In some embodiments, the mixer circuit 206a the received signal path and the mixer circuit 206a of the transmit signal path have two or more mixers and may be configured for quadrature downconversion. In some embodiments, the mixer circuit 206a the received signal path and the mixer circuit 206a of the transmit signal path have two or more mixers and be designed for image suppression (eg Hartley image suppression). In some embodiments, the mixer circuit 206a the received signal path and the mixer circuit 206a be designed respectively for a direct down conversion and direct upconversion. In some embodiments, the mixer circuit 206a the received signal path and the mixer circuit 206a of the transmit signal path for the superheterodyne operation.

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 regard. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternative embodiments, the RF circuit 206 Analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits and the baseband circuit 204 may be a digital baseband interface for communicating with the RF circuit 206 exhibit.

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

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

The synthesizer circuit 206d may be configured to have an output frequency for use by the mixer circuit 206a the RF circuit 206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuit 206d be an N / N + 1 break synthesizer.

In some embodiments, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), although this is not a requirement. The divider control input can be either through the baseband circuit 204 or the application processor 202 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be from a look-up table based on a value determined by the application processor 202 specified channel can be determined.

The synthesizer circuit 206d the RF circuit 206 may include a divider, a delay 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 + 1 (eg, based on an output) to provide a fractional ratio. In some embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D flip-flop. In these embodiments, the delay elements may be configured to break a VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to ensure that the total delay through the delay line is a VCO cycle.

In some embodiments, the synthesizer circuit 206d 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 in conjunction with a quadrature generator and divider circuit can be used to generate a plurality of signals at the carrier frequency having a plurality of different phases with respect to each other. In some embodiments, the output frequency may be an LO frequency (fLO). In some embodiments, the RF circuit 206 have an IQ / polar converter.

The FEM circuit 208 may include a receive signal path that may include circuitry configured to operate with RF signals received from one or more antennas 210 are received, the received signals amplify and the amplified versions of the received signals of the RF circuit 206 provide for further processing. The FEM circuit 208 may also comprise a transmit signal path, which may comprise a circuit configured to amplify signals for transmission transmitted by the RF circuit 206 for transmission through one or more of the one or more antennas 210 to be provided. In various embodiments, the gain through the transmit or receive signal paths may be exclusive in the RF circuit 206 , exclusively in the FEM 208 or in both the RF circuit 206 as well as the FEM 208 respectively.

In some embodiments, the FEM circuit 208 a Tx / Rx switch to toggle between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (eg, to the RF circuit 206 ). The transmission signal path of FEM circuit 208 may include a power amplifier (PA) for amplifying RF input signals (eg from the RF circuit 206 provided) and one or more filters for generating RF signals for subsequent transmission (eg, through the one or more antennas 210 ) exhibit.

In some embodiments, the PMC 212 manage the power of the baseband circuit 204 provided. In particular, the PMC 212 control power source selection, voltage scaling, battery charging or DC conversion. The PMC 212 can often be integrated when the device 200 can be operated by a battery, for. When the device is contained in an UE. The PMC 212 can increase power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

2 shows the PMC 212 only with baseband connection 204 coupled. In other embodiments, the PMC 212 however, additionally or alternatively coupled to other components and perform similar power management operations on other components, such as, for example, B. for the application circuit 202 , the RF circuit 206 or the FEM 208 without being limited to it.

In some embodiments, the PMC 212 various energy saving mechanisms of the device 200 control or otherwise be part of it. When the device 200 For example, if it is in an RRC_Connected state where it is still connected to the RAN node because it expects traffic in the short term, it may enter a state called DIContinuous Reception Mode (DRX) after an inactivity period becomes. During this condition, the device may become 200 Switch off for short periods of time and thus save energy.

If there is no traffic activity for a long period of time, the device may 200 transition to an RRC_Idle state, where it disconnects from the network and does not perform any operations such as channel quality feedback, handover, and so on. The device 200 goes into a low power state and paging, waking up at periodic intervals to listen to the network and then turning off again. The device 200 may not receive data in this state to receive data, it must go back to the RRC_Connected state.

An additional power-saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (which can range from seconds to several hours). During this time, the device is completely inaccessible to the network and may be completely off. Any data sent during this time will cause a large delay and it is assumed that this delay is acceptable.

Processors of the application circuit 202 and processors of the baseband circuit 204 can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuit 204 Used alone or in combination to enhance the functionality of the layer 3 , Layer 2 or layer 1 while processors of the application circuit 204 Use data (eg, packet data) received from these layers, and also the functionality of the layer 4 (e.g., transmit communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned here, the layer 3 a radio resource control layer (RRC layer), which will be described in more detail below. As mentioned herein, the layer may 2 a Medium Access Control (MAC) layer, a Radio Link Control Layer (RLC), and a Packet Data Convergence Protocol (PDCP) layer, which are described in more detail below. As mentioned herein, the layer may 1 a physical (PHY) layer of a UE / RAN node, which will be described in more detail below.

3 FIG. 12 illustrates exemplary interfaces of the baseband circuitry according to some embodiments. FIG. As explained above, the baseband circuit 204 out 2 the processors 204A - 204E and a memory 204G which is used by the processors. Each of the processors 204A - 204E can each have a memory interface 304A - 304E to the Sending / receiving data to / from the memory 204G exhibit.

The baseband circuit 204 may further include one or more interfaces for communicatively coupling to other circuitry / devices, such as a memory interface 312 (For example, an interface for transmitting / receiving data to / from a memory external to the baseband circuit 204 ), an application circuit interface 314 (eg, an interface for sending / receiving data to / from the application circuit 202 out 2 ), an RF circuit interface 316 (eg, an interface for transmitting / receiving data to / from the RF circuit 206 out 2 ), a wireless hardware connectivity interface 318 (For example, an interface for transmitting / receiving data to / from Near Field Communication (NFC) components, Bluetooth® components (eg, Bluetooth® Low Energy), Wi-Fi® components, and other communication components) and one energy management interface 320 (eg, an interface to send / receive power or control signals to / from the PMC 212 ).

In addition, although the above exemplary discussion of the device may be 300 in the context of a UE device, in various aspects, a similar device is used in conjunction with a base station (BS) such as an Evolved NodeB (eNB), etc.

To enable low-latency transmission for extended mobile broadband communication, a self-contained TDD (Time Division Duplexing) subframe may be employed. Referring to 4 is an exemplary type of standalone TDD subframe structure 400 in DL (downlink), which may be used in conjunction with various aspects discussed herein. Especially for the exemplary subframe 400 out 4 For example, the PDSCH (Physical Downlink Control Channel, eg 5G PDCCH) 420 PDSCH (Physical Downlink Control Channel, eg 5G (5th generation) PDSCH) 420 may be scheduled by PDCCH (Physical Downlink Control Channel, eg 5G PDCCH) 410 and right after the PDCCH 410 be transmitted. The hold time (GT - Guard Time) 430 can optionally be between PDSCH 420 and PUCCH (physical uplink control channel) 440 are inserted to accommodate the DL-to-UL (uplink) and UL-to-DL switching time and round trip propagation delay.

For 5G systems, high frequency band communication has attracted much attention in the industry as it can provide wider bandwidth to support the future integrated communication system. The beamforming technology may facilitate the implementation of a high frequency band system due to the fact that the beamforming gain can compensate for the high path loss caused by atmospheric damping, which can improve SNR (Signal-to-Noise Ratio) and increase the coverage area can. By aligning the transmission beam with the target UE, the radiated energy can be focused for higher energy efficiency, and the mutual UE interference can be suppressed.

As in 4 For example, the PUCCH and a data channel (eg, PDSCH, in the example DL subframe 400 ) are multiplexed by Time Division Multiplexing (TDM). In scenarios where a symbol for PUCCH is assigned, increasing the number of resources in the frequency for the PUCCH transmission may not improve the connection budget accordingly. This is mainly due to the fact that as more resources are allocated for PUCCH, the coding rate is reduced at the expense of increased noise performance. For the same transmission power, the maximum coupling loss (MCL) between the UE and eNB and thus the connection budget for the PUCCH transmission remains the same. In scenarios where a UE is equipped with multiple switchboards or sub-arrays, a dual beam or multi-beam transmission for PUCCH may be applied to improve the connection budget by taking advantage of spatial diversity, as discussed in greater detail herein.

The aspects discussed herein relate to techniques that may be used in conjunction with PUCCH. In a first set of techniques, dual beam transmission techniques discussed herein may be used. Additionally or alternatively, in a second set of techniques, rapid ARQ (Hybrid Automatic Repeat Request (ARQ)) ACK / NACK feedback mechanisms may be employed on PUCCH techniques discussed herein.

Referring to 5 is a block diagram of a system 500 which is applicable to a UE (user equipment) that enables techniques discussed herein for enhancing the PUCCH according to various aspects described herein. The system 500 can be one or more processors 510 (For example, one or more baseband processors such as one or more of the baseband processors associated with 2 and or 3 comprising a processing circuit and associated memory interface (s) (eg, memory interface (s) used in conjunction with 3 was discussed (n)), a transceiver circuit 520 (eg, comprising one or more transmission circuits or receiver circuits that may use common circuit elements, different circuit elements, or a combination thereof) and a memory 530 (which may each comprise a plurality of storage media and store instructions and / or data associated with one or more of the processors 510 or the transceiver circuit 520 are assigned). In different aspects, the system can 500 contained in a user equipment (UE). As will be described in more detail below, the system 500 allow for double or multi-beam PUCCH transmission and / or fast HARQ-ACK / NACK feedback techniques discussed here in a UE.

Referring to 6 is a block diagram of a system 600 which may be employed at a BS (base station) which facilitates techniques discussed herein for an improved PUCCH from a UE according to various aspects described herein. The system 600 can be one or more processors 610 (For example, one or more baseband processors such as one or more of the baseband processors associated with 2 and or 3 comprising a processing circuit and associated memory interface (s) (eg, memory interface (s) used in conjunction with 3 was discussed (n)), a communication circuit 620 (which may include, for example, a circuit for one or more wired (eg, X2, etc.) links and / or transceiver circuitry that includes one or more transmitter circuits (eg, associated with one or more transmitter chains) or Receiver circuits (eg in conjunction with one or more receive chains), wherein the transmitter circuit and the receiver circuit may employ common circuit elements, different circuit elements or a combination thereof), and a memory 630 (which may include any of a variety of storage media and may store instructions and / or data associated with one or more of the processors 610 or the communication circuit 620 are assigned). In different aspects, the system can 600 in a developed universal terrestrial radio access network (E-UTRAN) Node B (Evolved Node B, eNodeB or eNB) or other base station in a wireless communication network. In some aspects, the processor (s) may 610 , the communication circuit 620 and the memory 630 may be included in a single device, while in other aspects they may be included in different devices, as part of a distributed architecture. As will be described in more detail below, the system may 600 allow a dual or multi-beam transmission of PUCCH from a UE and / or fast HARQ-ACK / NACK feedback techniques through a UE, according to various aspects discussed herein.

Double or multi-beam transmission for PUCCH

In scenarios where a UE (eg a UE, the system 500 equipped with two or more sub-arrays or switchboards, the UE (eg via transceiver circuit 520 ) the PUCCH (eg by the processor (s) 510 can be generated) with simultaneous use of two or more sub-arrays to improve the connection budget. Referring to 7 FIG. 3 is a diagram of an exemplary dual transmission scheme for PUCCH according to various aspects discussed herein. As in 7 For example, a UE may display two Tx beams (the solid line beams) at the same time for transmission of PUCCH (eg, through the processor (s) 510 generated) (eg, by beam weightings generated by the processor (s) 510 determined and through the transceiver circuit 520 be applied). In the example scenario off 7 For example, two eNBs or receiving points (RPs) may receive the PUCCH from a UE (eg, each via a communication circuit 620 ). However, in other scenarios, for example, an eNB may poll the PUCCH (eg, from the processor (s) 510 generated) from a UE using two beams (e.g., via the communications circuit 620 ), similar to the scenario 7 , In addition, though 7 2 illustrates a dual beam embodiment, in various aspects, multiple beams (eg, N) are employed (eg, by the transceiver circuitry) 520 ) to PUCCH (eg from the processor (s) 510 was generated) to one or more RPs (for example, in different aspects, from 1 to N) (each representing the PUCCH via its communication circuitry 620 receive this and their processors 610 can process). Although various dual beam embodiments and aspects are discussed herein as examples, similar embodiments and aspects with more than two beams may additionally be employed.

Depending on the type of received signal or message received, processing (eg, by the processor (s) 510 , the processor (s) 610 etc.) of one or more of: identifying physical resources associated with the signal / message, recognizing the signal / message, resource element group deinterleaving, demodulation, descrambling, and / or decoding. Depending on the type of generated signal or message generated, the output may be for transmission (eg, by the processor (s) 510 , the processor (s) 610 etc.) comprise one or more of: generating a set of associated bits indicative of the content of the signal or message, encoding (e.g., adding a cyclic redundancy check (CRC) and / or coding, via one or more multiple of turbo code, low density parity check (LDPC) code, tailbiting convolutional code (TBCC), etc.), scrambling (eg, based on a scrambling seed), modulating (eg, via one of binary phase shift keying) (BPSK), quadrature phase shift keying (QPSK) or some form of Quadrature Amplitude Modulation (QAM), etc.) and / or resource allocation (e.g., to a scheduled set of resources, to a set of time and frequency resources granted for the uplink transmission, etc .).

Aspects of Various Embodiments (eg, the System 500 and / or the system 600 ), which can support double or multi-beam transmission for PUCCH by a UE, are discussed below.

In one set of embodiments, an indication of whether two (or more) subarrays are to be used for PUCCH transmission may be provided by higher layers via UE-specific RRC (Radio Resource Control Radio) control signaling (e.g. the processor (s) 610 is generated via the communication circuit 620 is transmitted through the transceiver circuit 520 is received and by the processor (s) 510 is processed). After a UE UE exchanges capabilities (eg, via a UE capability information message that may include an indication of whether the UE can support dual / multi-beam transmission) with an eNB, the eNB may transmit the UE with a dual beam transmission for Configure PUCCH.

In some of these aspects, the best Tx (transmit) beams (eg, based on a beam measurement report, etc.) for the two of the PUCCH transmission (eg, through the transceiver circuit 520 from PUCCH, that of the processor (s) 510 generated) are also configured by the eNB via UE-specific RRC signaling (eg generated by the processor (s)) 610 , sent by the communication circuit 620 , received from the transceiver circuit 520 and processed by the processor (s) 510 ). After the UE receives a beam measurement report (eg, by the processor (s) 510 generated) based on a beam reference signal (BRS) (eg, by the processor (s) 610 was generated by the communication circuit 620 was transmitted by the transceiver circuit 520 was received and by the processor (s) 510 measured) (for example, by the transceiver circuit 520 ), the eNB may signal the best eNB Tx beam index to the UE (eg, via UE-specific RRC signaling, as discussed above) for each of the two sub-arrays. Then, for each sub-array, the UE may select the best UE-Tx beam for the PUCCH transmission according to eNB and UE-Tx / Rx beam pair assignment (eg, as previously, by the processor (s) 510 determined and in memory 530 stored) (eg via the processor (s) 510 ).

In another set of embodiments, an indication of using two or more sub-arrays for PUCCH transmission may be indicated in downlink control information (DCI) (eg, generated (eg, encoded, etc.) of the one or more processors 610 sent by the communication circuit 620 , received from the transceiver circuit 520 and processes (eg, decodes, etc.) from the processor (s) 510 ). In some aspects, a 1-bit field may be used in the DCI to indicate the triggering of PUCCH using a dual beam transmission. For example, a value "1" may indicate that a dual beam transmission is to be applied for the PUCCH transmission, while a value of "0" may indicate that a single beam transmission is to be used for PUCCH transmission (eg, or vice versa etc.).

In some of these aspects, a UE Tx beam ID (identifier) or an eNB Rx beam ID for the secondary subarray may be included in the DCI format for triggering PUCCH, which is dynamic beam switching for uplink transmission can facilitate.

Referring to 8th FIG. 10 is an exemplary diagram of a subframe showing resources configured for dual beam PUCCH transmission, according to various aspects discussed herein. Even though 8th represents different resources that are configured for different beams for PUCCH, either the same or different PUCCH resources may be configured by higher layers or in DCI format (eg, in a DCI message or RRC signaling that may be different from the one or more PUCCHs) the processors 610 is generated by the communication circuit 620 transmitted through the transceiver circuit 520 received and by the processor (s) 510 processed). In various aspects, PUCCH resources may be multiplexed to multiple frequency division (FDM) or code division multiple access (CDM) users. In addition, in scenarios where the UE is configured with two antenna ports in a Tx beam, spatial frequency block coding (SFBC) or spatial orthogonal resource transmission diversity (SORTD) may be applied depending on the PUCCH format (s).

Depending on the embodiment, several different resource allocation options may be used for the dual or multi-beam PUCCH transmission.

In one set of embodiments, the same resources for two beams may be configured for PUCCH transmission. In this case, the eNB may allocate the resources for PUCCH transmission for a single beam over high layers or a DCI message (eg, through the processor (s) 610 generated by the communication circuit 620 transmitted by the transceiver circuit 520 received and from the processor (s) 510 processed), which can reduce the signaling overhead.

In another set of embodiments, a constant frequency offset between two PUCCH resources may be used for two beams (or between N PUCCH resources for N beams, the second beam being offset from the first by the constant frequency offset, the third beam from the first second offset by the constant frequency offset, etc.). In various aspects, the constant frequency offset may be predetermined (eg in the specification); may be configured by higher layers via a MIB (master information block (eg 5G MIB, etc.), a SIB (system information block (eg 5G SIB, etc.) or a dedicated RRC signaling, or may be in the DCI In one example, the constant frequency offset may be defined depending on the system bandwidth.

In another set of embodiments, two PUCCH resources may be explicitly specified in the DCI format (and thereby, for example, in a DCI message sent by the processor (s) 610 generated by the communication circuit 620 transmitted from the transceiver circuit 520 received and from the processor (s) 510 processed will be specified). This option may increase scheduling flexibility, but may require more signaling overhead than some other embodiments.

In another set of embodiments, a set of frequency resources for each AP (antenna port) in each beam may be transmitted through higher layers via RRC signaling (eg, through the processor (s) 610 generated by the communication circuit 620 transmitted through the transceiver circuit 520 received and by the processor (s) 510 processed). For dual beam transmission, 4 APs can be defined, where the first two APs can be defined for the first Tx beam and the last two APs can be defined for the second Tx beam.

(p = 0,1,2,3) für die Doppelstrahl-PUCCH-Übertragung definiert werden. Tabelle1: PUCCH-Ressourcenwert für PUCCH-Ressourcenzuweisung Bitfeld in DCI für die PUCCH-Ressourcenzuweisung $n_{xPUCCH}^{\left(p\right)}$

‚00‘ Der erste PUCCH-Ressourcenwert, der von den höheren Schichten konfiguriert wurde ‚01‘ Der zweite PUCCH-Ressourcenwert, der von den höheren Schichten konfiguriert wurde ‚10‘ Der dritte PUCCH-Ressourcenwert, der von den höheren Schichten konfiguriert wurde ‚11‘ Der vierte PUCCH-Ressourcenwert, der von den höheren Schichten konfiguriert wurde In some aspects, a resource allocation field may be included in the DCI message (eg, by the processor (s) 610 generated by the communication circuit 620 transmitted through the transceiver circuit 520 received and by the processor (s) 510 processed) may be used to specify the PUCCH resource index from more than one possible PUCCH resource index for transmission of the PUCCH. To reduce signaling overhead, a resource allocation field may be used to signal the resource for PUCCH transmission using two beams. The following Table 1 shows an example of specifying a PUCCH resource value using the DCI from 4 possible configured PUCCH resource values. In this example can $n_{xPUCCH}^{\left(p\right)}.$

(p = 0,1,2,3) for the double-jet PUCCH transmission. Table 1: PUCCH Resource Value for PUCCH Resource Assignment Bit field in DCI for PUCCH resource allocation $n_{xPUCCH}^{\left(p\right)}$

, 00 ' The first PUCCH resource value configured by the higher layers , 01 ' The second PUCCH resource value configured by the higher layers , 10 ' The third PUCCH resource value configured by the higher layers , 11 ' The fourth PUCCH resource value configured by the higher layers

ACK / NACK feedback mechanism on PUCCH

For a DL HARQ (Hybrid ARQ) (Automatic Repeat Request) operation, the eNB may schedule the UE to transmit HARQ ACK / NACK to PUCCH in certain time and frequency resources (eg, via the determination and generation of the signaling or Messaging, which the planning by the processor (s) 610 , the transmission through the communication circuit 620 , the reception by the transceiver circuit 520 and the determination of display scheduling by the processor (s) 510 indicates). The time and frequency resources for PUCCH transmission can either be configured by higher layers or specified in the DCI message.

Referring to 9 FIG. 3 is a diagram showing an exemplary time of DL HARQ that may be employed in various aspects discussed herein. In the example scenario off 9 For example, the delay for the PDSCH transmission in the subframe #n and the corresponding HARQ ACK / NACK on PUCCH 7 may be subframes (as represented by k = 7 for the subframe #n in FIG 9 shown). Similarly, the delays for PDSCH transmission in subframes # (n + 1), # (n + 2), and # (n + 3) and corresponding HARQ ACK / NACK on PUCCH may be 6, 5, and 4 subframes, respectively. For this example, the eNB may be the UE (eg, via the determination and generation of the signaling or messaging which the scheduling by the processor (s) 610 , the transmission through the communication circuit 620 , the reception by the transceiver circuit 520 and determining the specification by the processor (s) 510 for the feedback of HARQ ACK / NACK for PDSCH in 4 subframes on the PUCCH in the same subframe (eg subframe # (n + 7) as in 9 as shown), which, due to the existence of the hold period and the PUCCH, can save on overhead and thereby improve the peak data rate. In various aspects, the HARQ ACK / NACK delay counter may be included in the DCI message.

In some aspects, a HARQ ACK / NACK feedback for PDSCH may be coded together for multiple subframes and may be shared with a PUCCH resource (eg, by the processor (s) 510 ). In one embodiment, the PUCCH format 2 may be used to transmit HARQ ACK / NACK feedback for multiple subframes, and a PUCCH transmission may occupy 6 PRBs.

In these aspects, the UE may buffer the HARQ ACK / NACK bits for the PDSCH in previous subframes (eg, by buffering by the processor (s) 510 In the storage room 530 etc.) and may perform a common encoding (eg, by the processor (s) 510 after the PDSCH decoding has been performed (eg by the processor (s) 510 ). In some scenarios, additional processing delay in preparing the PUCCH transmission may result from using such an approach. For even faster HARQ ACK / NACK feedback processing, independent HARQ ACK / NACK feedback can be defined on PUCCH.

Three states can be defined for DL-HARQ feedback for each PDSCH transmission on PUCCH: (1) an ACK state that can indicate that the UE has successfully decoded a Transport Block (TB) (e.g. UE return the bit "1" to PUCCH to indicate ACK); (2) a NACK state, which may indicate that the UE correctly receives the DCI for PDSCH scheduling but can not decode the transport block (eg, the UE may loop back bit "0" to PUCCH to NACK specify); and (3) a DTX state that may indicate that the UE has failed in decoding the DCI (eg, the UE may avoid any transmission on the configured PUCCH resource to specify DTX).

In a scenario where two (or more) transport blocks are transferred to PDSCH, one bit ACK / NACK can be defined for each transport block. In some of these aspects, ACK / NACK feedback on each TB can be transmitted on independent PUCCH resources. Alternatively, spatial clustering may be used for ACK / NACK on these two TBs, for example, an AND operation may be used on these 2 ACK / NACK bits.

Various mechanisms for independent HARQ ACK / NACK feedback can be used, as described below.

In a set of embodiments that use independent HARQ ACK / NACK feedback, a HARQ ACK / NACK feedback for PDSCH may be multiplexed on multiple subframes in a frequency division multiplex (FDM) (eg, by one or more processors 510 ). Further, a localized or distributed resource allocation mapping mode may be used for HARQ ACK / NACK feedback (eg, by one or more processors 510 ) are used.

In some aspects, the PUCCH resource for HARQ ACK / NACK may be indicated on each TB in the DCI message. In other aspects, the resource may be derived from the downlink assignment index (DAI) or the delay counter, as in the DCI message (eg, by the processor (s) 510 ) contain. In such an example, the resource index for the PUCCH transmission may be the same as the DAI so that the PUCCH resource index for the HARQ ACK / NACK feedback for a first PDSCH transmission may be 0 for a second PDSCH transmission can etc.

Referring to 10 FIG. 12 is a diagram showing examples of localized and distributed transmission modes for HARQ ACK / NACK feedback on PUCCH according to various aspects discussed herein. FIG. Using a localized transfer mode may potentially improve the connection budget, while using a distributed transfer mode may provide frequency diversity. In the examples 10 each PUCCH transmission occupies 6 PRBs (from PRB # 0 - # 5), and the HARQ ACK / NACK feedback for 4 subframes (as indicated by numbers 0, 1, 2 and 3) is carried in the PUCCH. As in 10 "0" indicates the HARQ ACK / NACK feedback for the first subframe, "1" indicates the HARQ ACK / NACK feedback for the second subframe, and so forth 10 shown examples of each HARQ ACK / NACK feedback 12 REs.

worin α der zyklische Verschiebungswert und n_DAI der DAI-Index ist. In einem Beispiel, wie in den Gleichungen (2) gezeigt, $$\begin{array}{c}{a}_{\tilde{p}}\left(n_{\text{s}}\right)=2\pi \cdot n_{\text{cs}}^{\left(\tilde{p}\right)}\left(n_{\text{s}}\right)/N_{\text{sc}}^{\text{RB}}\\ n_{\text{cs}}^{\left(\tilde{p}\right)}\left(n_{\text{s}}\right)=\left[n_{\text{cs}}^{\text{cell}}\left(n_{\text{s}}\right)+n_{\text{xPUCCH}}^{\left(1\right)}+a_0\cdot n_{\text{DAI}}+\frac{N_{\text{sc}}^{\text{RB}}\tilde{p}}{P}\right]\text{mod}{N}_{\text{sc}}^{\text{RB}}\end{array}$$

worin $n_{\text{xPUCCH}}^{\left(1\right)}\in \left\{\mathrm{0,2,3,4,6,8,9,10}\right\}$

durch höhere Schichten konfiguriert wird, ist $n_{\text{cs}}^{\text{cell}}\left(n_{\text{s}}\right)$

ein zellspezifischer zyklischer Verschiebungswert; $N_{\text{sc}}^{\text{RB}}$

ist die Anzahl der Unterträger für einen physischen Ressourcenblock (PRB), d. h. $N_{\text{sc}}^{\text{RB}}=12$

P ist die Anzahl der APs und P̃ ist der AP-Index. α₀ ist eine Konstante.In various aspects, a ZC (Zadoff-Chu) sequence or a computer generated sequence may be applied (eg, by one or more processors 510 ) to distribute the HARQ ACK / NACK feedback bit. In various aspects, a cyclic shift value may be defined depending on the cell-specific, UE-specific and / or antenna-specific cyclic shift value. In scenarios where independent HARQ ACK / NACK feedback is used, the DAI index may be included to generate the cyclic shift value. In various aspects, the cyclic shift value may be generated as in equation (1) (eg, by one or more processors 510 ): $$a=f\left(n_{DAI}\right)$$

where α is the cyclic shift value and n _{DAI is} the DAI index. In an example, as shown in equations (2), $$\begin{array}{c}{a}_{\tilde{p}}\left(n_{\text{s}}\right)=2\pi \cdot n_{\text{cs}}^{\left(\tilde{p}\right)}\left(n_{\text{s}}\right)/N_{\text{sc}}^{\text{RB}}\\ n_{\text{cs}}^{\left(\tilde{p}\right)}\left(n_{\text{s}}\right)=\left[n_{\text{cs}}^{\text{cell}}\left(n_{\text{s}}\right)+n_{\text{xPUCCH}}^{\left(1\right)}+a_0\cdot n_{\text{DAI}}+\frac{N_{\text{sc}}^{\text{RB}}\tilde{p}}{P}\right]\text{mod}{N}_{\text{sc}}^{\text{RB}}\end{array}$$

wherein $n_{\text{xPUCCH}}^{\left(1\right)}\in \left\{\mathrm{0,2,3,4,6,8,9,10}\right\}$

is configured by higher layers is $n_{\text{cs}}^{\text{cell}}\left(n_{\text{s}}\right)$

a cell-specific cyclic shift value; $N_{\text{sc}}^{\text{RB}}$

is the number of subcarriers for a physical resource block (PRB), ie $N_{\text{sc}}^{\text{RB}}=12$

P is the number of APs and P is the AP index. α ₀ is a constant.

In another set of embodiments, a HARQ ACK / NACK feedback for PDSCH may be provided on multiple subframes in a code division multiple access (CDM) or a combination of FDM and CDM (eg, by the processor (s) 510 ) are multiplexed. In such aspects, different cyclic shift values may be applied to the HARQ ACK / NACK feedback for different subframes (eg, by the processor (s) 510 ). For example, one or more cyclic shift values (eg, by the processor (s) 510 ) depending on the DAI index.

In scenarios where the eNB plans the HARQ ACK / NACK for a relatively large number of subframes (eg, more than 4) (eg, by signaling or messages sent by the processor (s) 610 be generated and through the communication circuit 620 PUCCH resources CDM can be multiplexed (e.g., by the processor (s) 510 ). Referring to 11 For example, examples of PUCCH resources are presented for a relatively large number of HARQ ACK / NACK feedbacks, according to various aspects discussed herein. As in 11 "0/4" indicates the HARQ ACK / NACK feedbacks for the first subframe and the fifth subframe, "1/5" indicates the HARQ ACK / NACK feedback for the second and sixth subframes, etc. If HARQ ACK / NACK for different subframes in the same resources (e.g., by the processor (s)) 510 ), various cyclic shift values may be defined (eg, predefined or defined by signaling by the processor (s) 610 is generated by the communication circuit 620 is transmitted by the transceiver circuit 520 is received and by the processor (s) 510 processed) and applied (eg, by the processor (s) 510 ) to differentiate the PUCCH resources.

Referring to 12 FIG. 10 is a flowchart of an example method. FIG 1200 which facilitates PUCCH double or multi-beam transmission to a UE according to various aspects discussed herein. In other aspects, a machine-readable medium may store instructions that correspond to the method 1200 which, when executed, may cause a UE to cause the actions of methods 1200 performs.

at 1210 For example, a UE capability information message may be sent that may indicate support for a dual beam or multi-beam uplink transmission.

at 1220 For example, a configuration may be received to use dual / multi-beam transmission for PUCCH.

Additionally or alternatively, the method 1200 have one or more other actions associated with dual or multi-beam PUCCH transmission aspects of the system herein 500 are described.

Referring to 13 FIG. 10 is a flowchart of an example method. FIG 1300 which is usable on a BS that enables PUCCH double or multi-beam transmission of one or more UEs according to various aspects discussed herein. In other aspects, a machine-readable medium may store instructions that correspond to the method 1300 and, when executed, can cause a BS to perform the actions of procedures 1300 performs.

at 1310 For example, a UE capability information message may be received from a UE that may indicate support for a dual beam or multi-beam uplink transmission.

at 1220 For example, the UE may be configured to use dual / multi-beam transmission for PUCCH.

Additionally or alternatively, the method 1300 have one or more other actions associated with dual or multi-beam PUCCH transmission aspects of the system herein 600 are described.

Referring to 14 FIG. 10 is a flowchart of an example method. FIG 1400 which facilitates fast HARQ ACK / NACK feedback techniques to a UE according to various aspects discussed herein. In other aspects, a machine-readable medium may store instructions that correspond to the method 1400 and, when executed, may cause a UE to perform the actions of procedures 1400 performs.

at 1410 HARQ ACK / NACK feedback can be generated for multiple TBs.

at 1420 For example, the HARQ ACK / NACK feedback for the multiple TBs can be transmitted via a single icon.

Additionally or alternatively, the method 1400 have one or more other actions related to ACK / NACK feedback aspects of the system 500 are described.

Referring to 15 FIG. 10 is a flowchart of an example method. FIG 1500 which is applicable to a BS that enables HARQ ACK / NACK feedback from a UE according to various aspects discussed herein. In other aspects, a machine-readable medium may store instructions that correspond to the method 1500 and, when executed, can cause a BS to perform the actions of procedures 1500 performs.

at 1510 PUCCH can be received via a single symbol, where the PUCCH HARQ comprises ACK / NACK for several TBs.

at 1520 For example, the received PUCCH may be decoded to determine the HARQ ACK / NACK for the multiple TBs.

Additionally or alternatively, the method 1500 have one or more other actions related to ACK / NACK feedback aspects of the system 600 are described.

Examples herein may include an article such as a method, means for performing actions or blocks of the method, at least one machine-readable medium having executable instructions that when executed by a machine (eg, a processor with memory, an application-specific integrated Circuitry (ASIC), a Field Programmable Gate Array (FPGA), or the like) cause the machine to perform actions of the method or apparatus or system for simultaneous communication using a variety of communication technologies in accordance with the described embodiments and examples.

Example 1 is an apparatus configured for deployment in a user equipment (UE), comprising: a memory interface; and a processing circuit configured to: generate a UE capability information message indicating that the UE supports uplink transmission over two or more subarrays; Processing the configuration signaling, comprising an indicator indicating that two or more beams are being used for a PUCCH (Physical Uplink Control Channel); and sending the indicator to a memory via the memory interface.

Example 2 includes the subject matter of each variation of Example 1, wherein the configuration signaling comprises signaling the first higher layer.

Example 3 includes the subject matter of each variation of Example 2, wherein the first higher layer signaling comprises a first set of UE-specific RRC signaling.

Example 4 includes the subject matter of each variation of Example 1, wherein the processing circuitry is further configured to process a second set of UE-specific RRC signaling indicating the two or more beams by specifying a best ray for each of the two or more sub-arrays.

Example 5 includes the subject matter of each variation of Example 1, wherein the configuration signaling comprises a first DCI (Downlink Control Information) message.

Example 6 includes the subject matter of each variation of Example 5, wherein the DCI message has at least one UE Tx (transmit) beam ID (identifier) or at least one eNB (evolved Node B-developed Node B) Rx (receiver). ) Specifies ray ID associated with a secondary subarray of the two or more subarrays.

Example 7 includes the subject matter of each variation of Examples 1-6, wherein the processing circuitry is further configured to: process the resource configuration signaling indicating a set of resources for the PUCCH for a single beam; and associating the PUCCH with the resource set for each of the two or more beams, wherein the resource configuration signaling comprises a second higher layer signaling or a second Downlink Control Information (DCI) message.

Example 8 includes the subject matter of each variation of Examples 1-6, wherein the processing circuitry is further configured to: assign the PUCCH to a different resource set for each of the two or more beams, wherein adjacent resource sets of the different resource sets from each other in a frequency domain by a constant frequency offset where the constant frequency offset is predefined or via a MIB (Master Information Block), a SIB (System Information Block), a dedicated RRC (Radio Resource Control) signaling or a third DCI message (Downlink Control Information) is specified.

Example 9 includes the subject matter of each variation of Examples 1 through 6, wherein the processing circuitry is further configured to: Process a fourth DCI message (downlink). Control information message) indicating a different resource set for the PUCCH for each of the two or more beams; and assigning the PUCCH to the other resource set for each of the two or more beams.

Example 10 includes the subject matter of each variation of Examples 1-6, wherein the processing circuitry is further configured to: process a third higher layer signaling indicating an associated frequency resource set for each AP (antenna port) of the two or more beams; Processing a fifth DCI message (downlink control information) comprising a resource assignment field indicating a specified PUCCH resource index of the two or more PUCCH resource indices; and assigning the PUCCH based at least in part on the specified PUCCH resource index.

Example 11 includes the subject matter of each variation of Examples 1-6, wherein the processing circuitry is further configured to associate the PUCCH into a single symbol, the PUCCH providing an independent HARQ (Automatic Transmission Request (ACK)) ACK (Acknowledgment ) / NACK (Negative Acknowledgment) feedback for more than one TB (transport block).

Example 12 includes the subject matter of each variation of Examples 1-3, wherein the processing circuitry is further configured to process a second set of UE-specific RRC signaling that identifies the two or more beams by specifying a best ray for each of the two or more sub-arrays indicates.

Example 13 includes the subject matter of each variation of Examples 1-10, wherein the processing circuitry is further configured to associate the PUCCH into a single symbol, the PUCCH providing an independent HARQ (Automatic Transmission Request (ACK)) ACK (Acknowledgment ) / NACK (Negative Acknowledgment) feedback for more than one TB (transport block).

Example 14 is an apparatus configured for use in an Evolved NodeB (eNB), comprising: a memory interface; and a processing circuit configured to: process a UE (User Equipment) capability information message indicating that a UE supports uplink transmission over two or more subarrays; Generating a configuration signaling indicating to use two or more beams for a Physical Uplink Control Channel (PUCCH); and sending the UE capability information message to a memory via the memory interface.

Example 15 includes the subject matter of each variation of Example 14, wherein the configuration signaling comprises UE-specific RRC (Radio Resource Control) signaling.

Example 16 includes the subject matter of each variation of Example 15, wherein the configuration signaling indicates a best ray for each of the two or more sub-arrays.

Example 17 includes the subject matter of each variation of Example 14, wherein the configuration signaling comprises a first DCI (downlink control information) message including at least one UE Tx (transmit) beam ID (identifier) or at least one eNB (evolved node B - developed node B) indicates Rx (receive) beam ID associated with a secondary subarray of the two or more subarrays.

Example 18 includes the subject matter of each variation of Examples 14-17, wherein the processing circuitry is further configured to generate a resource configuration signaling indicating a single set of resources to be employed for the PUCCH for each of the two or more beams.

Example 19 includes the subject matter of each variation of Examples 14-17, wherein the processing circuitry is further configured to generate a second DCI message (downlink control information message) indicating for each of the two or more beams a different set of resources used for PUCCH should.

Example 20 includes the subject matter of each variation of Examples 14-17, wherein the processing circuitry is further configured to generate a resource configuration signaling indicative of a constant frequency offset used to allocate PUCCH to resources, wherein the Resource configuration signaling comprises a MIB (Master Information Block), a SIB (System Information Block), a dedicated RRC (Radio Resource Control) signaling or a third DCI (Downlink Control Information) message.

Example 21 includes the subject matter of each variation of Examples 14-17, wherein the processing circuitry is further configured to generate a resource configuration signaling indicating a different frequency resource set to be employed for the PUCCH for each AP (antenna port) of the two or more beams.

Example 22 is an apparatus configured for deployment in a user equipment (UE), comprising: a memory interface; and processing circuits configured to: generate HARQ (Hybrid ARQ (Automatic Repeat Request)) ACK (Acknowledgment) / NACK (Negative Acknowledgment) feedback for two or more TBs (Transport Blocks); Associate the HARQ ACK / NACK feedback for the two or more TBs with a Physical Uplink Control Channel (PUCCH) in a single symbol; and sending the HARQ ACK / NACK feedback to a memory via the memory interface.

Example 23 includes the subject matter of each variation of Example 22, wherein the processing circuitry is further configured to multiplex the HARQ ACK / NACK feedback via FDM (Frequency Division Multiplexing).

Example 24 includes the subject matter of each variation of Example 23, wherein the processing circuitry is configured to associate the HARQ ACK / NACK feedback based on a localized transmission mode or a distributed transmission mode.

Example 25 includes the subject matter of each variation of Examples 23-24, wherein the processing circuitry is further configured to decode a downlink control information (DCI) message indicating another PUCCH resource for each of the two or more TBs. wherein the processing circuitry is configured to associate the HARQ ACK / NACK feedback for the two or more TBs with the different PUCCH resources for each of the two or more TBs.

Example 26 includes the subject matter of each variation of Examples 23-24, wherein the processing circuitry is further configured to decode a Downlink Control Information (DCI) message indicating a Downlink Assignment Index (DAI), and a delay counter, wherein the processing circuit is configured to associate the HARQ ACK / NACK feedback for the two or more TBs based at least in part on one or more of DAI or delay counters.

Example 27 includes the subject matter of each variation of Example 26, wherein the processing circuitry is further configured to apply a cyclic shift to the HARQ ACK / NACK feedback, wherein the cyclic shift is based at least in part on the DAI.

Example 28 includes the subject matter of each variation of Example 22, wherein the processing circuitry is further configured to multiplex the HARQ ACK / NACK feedback via one of Code Division Multiplexing (CDM) or a combination of CDM and FDM (Frequency Division Multiplexing) ).

Example 29 includes the subject matter of each variation of Example 28, wherein the two or more TBs include more than four TBs and wherein the processing circuitry is further configured to multiplex the HARQ ACK / NACK feedback via CDM.

Example 30 is an apparatus configured for use in an Evolved NodeB (eNB), comprising: a memory interface; and a processing circuit configured to: decode the PUCCH (Physical Uplink Control Channel) from a single symbol of a subframe; Determining HARQ (Hybrid ARQ (Automatic Repeat Request)) ACK (Acknowledgment) / NACK (Negative Acknowledgment) Feedback for two or more TBs (Transport Blocks) from the PUCCH decoded by the single symbol; and sending the HARQ ACK / NACK feedback to a memory via the memory interface.

Example 31 includes the subject matter of each variation of Example 30 wherein the HARQ ACK / NACK feedback is multiplexed by CDM (Code Division Multiplex), FDM (Frequency Division Multiplex), or a combination of CDM and FDM.

Example 32 includes the subject matter of each variation of Examples 30-31, wherein the HARQ ACK / NACK feedback for the two or more TBs is associated with the single symbol based on a localized transmission mode or a distributed transmission mode.

Example 33 includes an apparatus comprising means for performing each of the described operations of Examples 1 to 32.

Example 34 includes a machine-readable medium that stores instructions for execution by a processor to perform one of the described operations of Examples 1-32.

The above description of the illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for purposes of illustration, various modifications are possible that are within the scope of such embodiments and examples, as those skilled in the relevant art will recognize.

Although the disclosed subject matter has been described in this regard in connection with various embodiments and the corresponding figures, when applicable, it is to be understood that other similar embodiments may be utilized or modifications or additions may be made to the described embodiments to the same the use similar, alternative or substitutive functions of the disclosed subject matter without departing from it. Therefore, the disclosed subject matter should not be limited to any particular embodiment described herein, but rather construed in breadth and scope according to the appended claims.

In particular, with regard to the various functions performed by the above-described components or structures (arrangements, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components shall unless expressly stated otherwise, correspond to any component or structure that performs the specified function of the described component (eg, whose functionality is equivalent), even if it is not structurally equivalent to the disclosed structure having the function in the example implementations illustrated herein. In addition, while a particular feature has been disclosed in relation to only one of various implementations, such feature may be combined with one or more other features of the other implementations, as desired and advantageous for a given or particular application.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited patent literature

• US 62332985 [0001]

Claims (31)

Claimed is: Apparatus configured for insertion in a user equipment (UE), comprising: a memory interface; and Processing circuits configured for: Generating a UE capability information message indicating that the UE supports uplink transmission over two or more subarrays; Processing the configuration signaling, comprising an indicator indicating that two or more beams are being used for a Physical Uplink Control Channel (PUCCH); and Send the indicator to a memory via the memory interface. Device after Claim 1 wherein the configuration signaling comprises signaling a first higher layer. Device after Claim 2 wherein the first higher layer signaling comprises a first set of UE-specific RRC signaling. Device after Claim 1 wherein the processing circuit is further configured to process a second set of UE-specific RRC signaling indicating the two or more beams by specifying a best ray for each of the two or more sub-arrays. Device after Claim 1 wherein the configuration signaling comprises a first Downlink Control Information (DCI) message. Device after Claim 5 wherein the DCI message indicates at least one UE Tx (transmit) beam ID (identifier) or at least one eNB (evolved Node B) Rx (receive) beam ID corresponding to a secondary subarray which is associated with two or more subarrays. Device according to one of Claims 1 to 6 wherein the processing circuit is further configured to: process the resource configuration signaling indicating a resource set for the PUCCH for a single beam; and assigning the PUCCH to the resource set for each of the two or more beams, wherein the resource configuration signaling comprises a second higher layer signaling or a second Downlink Control Information (DCI) message. Device according to one of Claims 1 to 6 wherein the processing circuitry is further configured to: assign the PUCCH to a different resource set for each of the two or more beams, wherein adjacent resource sets of the other resource sets in a frequency range are offset from one another by a constant frequency offset, wherein the constant frequency offset is predefined or above a from a Master Information Block (MIB), a System Information Block (SIB), a Radio Resource Control (RRC) dedicated signaling, or a Downlink Control Information (DCI) third DCI message , Device according to one of Claims 1 to 6 wherein the processing circuit is further configured to: process a fourth Downlink Control Information (DCI) message indicating for each of the two or more beams a different resource set for the PUCCH; and assigning the PUCCH to the other resource set for each of the two or more beams. Device according to one of Claims 1 to 6 wherein the processing circuit is further configured to: process a third higher layer signaling indicating an associated frequency resource set for each AP (antenna port - antenna port) of the two or more beams; Processing a fifth DCI (Downlink Control Information) message, comprising a resource allocation field indicating a specified PUCCH resource index of the two or more PUCCH resource indices; and assigning the PUCCH based at least in part on the specified PUCCH resource index. Device according to one of Claims 1 to 6 wherein the processing circuitry is further configured to associate the PUCCH with a single symbol, the PUCCH providing an independent HARQ (Hybrid ARQ (Automatic Repeat Request)) ACK (Acknowledgment Confirmation) / NACK (Negative Acknowledgment). Feedback for more than one TB (Transport Block - Transport Block). An apparatus configured to be deployed in an evolved NodeB (evolved node - eNB), comprising: a memory interface; and Processing circuits configured for: Processing a UE (User Equipment) capability information message indicating that a UE supports uplink transmission over two or more subarrays; Generating a configuration signaling indicating to use two or more beams for a Physical Uplink Control Channel (PUCCH); and Sending the UE capability information message to a memory via the memory interface. Device after Claim 12 wherein the configuration signaling comprises UE-specific RRC (Radio Resource Control) signaling. Device after Claim 13 wherein the configuration signaling indicates a best ray for each of the two or more subarrays. Device after Claim 12 wherein the configuration signaling comprises a first downlink control information (DCI) message including at least one UE Tx (transmit) beam ID (identifier) or at least one evolved Node B (evolved Node B). Indicates Rx (receive) beam ID associated with a secondary subarray of the two or more subarrays. Device according to one of Claims 12 to 15 wherein the processing circuit is further configured to generate a resource configuration signaling indicating a single set of resources to be employed for the PUCCH for each of the two or more beams. Device according to one of Claims 12 to 15 wherein the processing circuit is further configured to generate a second DCI (Downlink Control Information) message indicating a different set of resources to be used for the PUCCH for each of the two or more beams. Device according to one of Claims 12 to 15 wherein the processing circuitry is further configured to generate resource configuration signaling indicative of a constant frequency offset used to allocate PUCCH to resources, the resource configuration signaling of one of a MIB (Master Information Block), a SIB (System Information Block). System information block), a dedicated RRC (Radio Resource Control) signaling, or a third Downlink Control Information (DCI) message. Device according to one of Claims 12 to 15 wherein the processing circuit is further configured to generate a resource configuration signaling indicating a different frequency resource set to be employed for the PUCCH for each AP (antenna port antenna port) of the two or more beams. Apparatus configured for insertion in a user equipment (UE), comprising: a memory interface; and processing circuits configured to: generate HARQ (Automatic Transmission Request) ACK (Acknowledgment) / Negative Acknowledgment (NACK) feedback for two or more TBs (Transport Blocks); Associating the HARQ ACK / NACK feedback for the two or more TBs with a Physical Uplink Control Channel (PUCCH) in a single symbol; and sending the HARQ ACK / NACK feedback to a memory via the memory interface. Device after Claim 20 wherein the processing circuit is further configured to multiplex the HARQ ACK / NACK feedback via FDM (Frequency Division Multiplexing). Device after Claim 21 wherein the processing circuitry is configured to associate the HARQ ACK / NACK feedback based on a localized transmission mode or a distributed transmission mode. Device according to one of Claims 21 to 22 wherein the processing circuit is further configured to decode a Downlink Control Information (DCI) message indicating another PUCCH resource for each of the two or more TBs, wherein the processing circuitry is configured to associate the HARQ ACK / NACK -Feedbacks for the two or more TBs to the other PUCCH resources for each of the two or more TBs. Device according to one of Claims 21 to 22 wherein the processing circuit is further configured to decode a Downlink Control Information (DCI) message indicating a Downlink Assignment Index (DAI) and a Delay Counter, the processing circuit being configured to associate the HARQ ACK / NACK feedbacks for the two or more TBs based at least in part on one or more of DAI or delay counters. Device after Claim 24 wherein the processing circuit is further configured to apply a cyclic shift to HARQ ACK / NACK feedback, wherein the cyclic shift is based at least in part on the DAI. Device after Claim 20 wherein the processing circuit is further configured to multiplex the HARQ ACK / NACK feedback via one of Code Division Multiplexing (CDM) or a combination of CDM and Frequency Division Multiplexing (FDM). Device after Claim 26 wherein the two or more TBs comprise more than four TBs and wherein the processing circuitry is further configured to multiplex the HARQ ACK / NACK feedback via CDM. An apparatus configured to be deployed in an evolved NodeB (evolved node - eNB), comprising: a memory interface; and Processing circuits configured for: Decoding the Physical Uplink Control Channel (PUCCH) from a single symbol of a subframe; Determine HARQ (Automatic Transmission Request) ACK (Acknowledgment) / Negative Acknowledge (NACK) feedback for two or more TBs (transport blocks) from the PUCCH, that of the single symbol is decoded; and Send the HARQ ACK / NACK feedback to a memory through the memory interface. Device after Claim 28 wherein the HARQ ACK / NACK feedback is multiplexed from one of Code Division Multiplexing (CDM), Frequency Division Multiplexing (FDM), or a combination of CDM and FDM. Device according to one of Claims 28 to 29 wherein the HARQ ACK / NACK feedback for the two or more TBs is associated with the single symbol based on a localized transmission mode or a distributed transmission mode.

Images