WO2017160350A1 - Équipement utilisateur (ue), nœud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) destinés aux aménagements d'agrégation de porteuse - Google Patents

Équipement utilisateur (ue), nœud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) destinés aux aménagements d'agrégation de porteuse Download PDF

Info

Publication number
WO2017160350A1
WO2017160350A1 PCT/US2016/062042 US2016062042W WO2017160350A1 WO 2017160350 A1 WO2017160350 A1 WO 2017160350A1 US 2016062042 W US2016062042 W US 2016062042W WO 2017160350 A1 WO2017160350 A1 WO 2017160350A1
Authority
WO
WIPO (PCT)
Prior art keywords
sub
pdcchs
harq
sps
frame
Prior art date
Application number
PCT/US2016/062042
Other languages
English (en)
Inventor
Hwan-Joon Kwon
Hong He
Alexei V. Davydov
Gang Xiong
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
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Priority to EP16894787.7A priority Critical patent/EP3430754A4/fr
Publication of WO2017160350A1 publication Critical patent/WO2017160350A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK

Definitions

  • Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, including 3 GPP LTE (Long Term Evolution) networks and 3GPP LTE-A (LTE Advanced) networks. Some embodiments relate to hybrid automatic repeat request (HARQ). Some embodiments relate to mapping of acknowledgement (ACK) bits to HARQ-ACK bit sequences. Some embodiments relate to carrier aggregation (CA) arrangements.
  • 3GPP Three Generation Partnership Project
  • 3 GPP LTE Long Term Evolution
  • 3GPP LTE-A Long Term Evolution Advanced
  • HARQ hybrid automatic repeat request
  • Some embodiments relate to mapping of acknowledgement (ACK) bits to HARQ-ACK bit sequences.
  • CA carrier aggregation
  • a mobile network may support communication with mobile devices.
  • an increased data rate and/or demand for services may provide various challenges.
  • an increased bandwidth may be used to increase an available data rate.
  • multiple channels may be aggregated for downlink data transmission by a base station to a mobile device in accordance with a carrier aggregation (CA) arrangement.
  • CA carrier aggregation
  • Some operations, such as exchanging of control information between the base station and the mobile device may be challenging in various scenarios, such as CA scenarios and others. Accordingly, there is a general need for methods and systems to enable communication in these and other scenarios.
  • FIG. 1 is a functional diagram of a 3GPP network in accordance with some embodiments
  • FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments
  • FIG. 3 is a block diagram of an Evolved Node-B (eNB) in accordance with some embodiments
  • FIG. 4 is a block diagram of a User Equipment (UE) in accordance with some embodiments.
  • UE User Equipment
  • FIG. 5 illustrates example carrier aggregation (CA) arrangements in accordance with some embodiments
  • FIG. 6 illustrates the operation of a method of communication in accordance with some embodiments
  • FIG. 7 illustrates examples of hybrid automatic repeat request (HARQ) acknowledgement in accordance with some embodiments
  • FIG. 8 illustrates additional examples of HARQ
  • FIG. 9 illustrates additional examples of HARQ
  • FIG. 10 illustrates the operation of another method of communication in accordance with some embodiments.
  • FIG. 1 1 illustrates additional examples of HARQ
  • FIGs. 12A-B illustrate additional examples of HARQ acknowledgement in accordance with some embodiments
  • FIG. 13 illustrates additional examples of HARQ
  • FIG. 14 illustrates the operation of another method of communication in accordance with some embodiments.
  • FIG. 1 is a functional diagram of a 3GPP network in accordance with some embodiments. It should be noted that embodiments are not limited to the example 3GPP network shown in FIG. 1, as other cellular networks and/or other networks may be used in some embodiments. As an example, a Fifth Generation (5G) network may be used in some cases. As another example, a wireless local area network (WLAN) may be used in some cases. Embodiments are not limited to these example networks, however, as other networks may be used in some embodiments. In addition, in some embodiments, one or more networks, including these example networks and/or other networks, may be used in combination.
  • 5G Fifth Generation
  • WLAN wireless local area network
  • the UE 102 may be configured to communicate with two networks (such as a 3 GPP LTE network and a 5G network), in some embodiments.
  • two networks such as a 3 GPP LTE network and a 5G network
  • handovers between the two networks may be performed, in some cases.
  • the networks of these embodiments and/or other embodiments may include one or more of the components shown in FIG. 1, and may include additional components and/or alternative components in some cases.
  • the eNB 104 and the UE 102 may be configured to operate in accordance with a carrier aggregation (CA) arrangement.
  • CA carrier aggregation
  • the eNB 104 may transmit downlink data to the UE 102 on multiple component carriers (CCs).
  • CCs component carriers
  • the network shown in FIG. 1 may comprise a radio access network (RAN) (e.g., as depicted, the E-UTRAN (evolved universal terrestrial radio access network)) 100 and the core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together through an S I interface 115.
  • RAN radio access network
  • EPC evolved packet core
  • the S 1 interface 115 may be a link between an eNB 104 and the MME 122 or S-GW 124.
  • a separate SI interface 115 may be used for each eNB 104 to provide a link between the eNB 104 and the MME 122 and/or S-GW 124, in some embodiments.
  • the core network 120 As well as the RAN 100, is shown.
  • the core network 120 includes a mobility management entity
  • the RAN 100 may include one or more Evolved Node-B's (eNBs) 104 (which may operate as base stations) for communicating with User Equipment (UE) 102.
  • eNBs Evolved Node-B's
  • the eNBs 104 may include macro eNBs and low power (LP) eNBs also known as micro-, pico-, femto- or small-cell eNBs.
  • the UE 102 may receive downlink medium access control (MAC) protocol data units (PDUs) from the eNB 104.
  • the MAC PDUs may be transmitted by the eNB 104 and received by the UE 102 in accordance with a 3 GPP protocol and/or other protocol.
  • the MME 122 is similar in function to the control plane of legacy
  • the MME 122 manages mobility aspects in access such as gateway selection and tracking area list management.
  • the serving GW 124 terminates the interface toward the RAN 100, and routes data packets between the RAN 100 and the core network 120. In addition, it may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.
  • the PDN GW 126 terminates an SGi interface toward the packet data network (PDN).
  • PDN packet data network
  • the PDN GW 126 routes data packets between the EPC 120 and the external PDN, and may be a key node for policy enforcement and charging data collection. It may also provide an anchor point for mobility with non-LTE accesses.
  • the external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domain.
  • IMS IP Multimedia Subsystem
  • the PDN GW 126 and the serving GW 124 may be implemented in one physical node or separated physical nodes.
  • the eNBs 104 terminate the air interface protocol and may be the first point of contact for a UE 102. In some
  • an eNB 104 may fulfill various logical functions for the RAN 100 including but not limited to RNC (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller functions
  • UEs 102 may be configured to communicate Orthogonal Frequency Division Multiplexing (OFDM) communication signals with an eNB 104 over a multicarrier communication channel in accordance with an Orthogonal Frequency Division Multiple Access (OFDMA) communication technique.
  • the OFDM signals may comprise a plurality of orthogonal subcarriers.
  • the S 1 interface 1 15 is the interface that separates the RAN 100 and the EPC 120. It is split into two parts: the S l-U, which carries traffic data between the eNBs 104 and the serving GW 124, and the S I -MME, which is a signaling interface between the eNBs 104 and the MME 122.
  • the X2 interface is the interface between eNBs 104.
  • the X2 interface comprises two parts, the X2-C and X2-U.
  • the X2-C is the control plane interface between the eNBs 104
  • the X2-U is the user plane interface between the eNBs 104.
  • LP cells are typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with very dense phone usage, such as train stations.
  • the term low power (LP) eNB refers to any suitable relatively low power eNB for implementing a narrower cell (narrower than a macro cell) such as a femtocell, a picocell, or a micro cell.
  • Femtocell eNBs are typically provided by a mobile network operator to its residential or enterprise customers.
  • a femtocell is typically the size of a residential gateway or smaller and generally connects to the user's broadband line.
  • a picocell is a wireless communication system typically covering a small area, such as in-building (offices, shopping malls, train stations, etc.), or more recently in-aircraft.
  • a picocell eNB can generally connect through the X2 link to another eNB such as a macro eNB through its base station controller (BSC)
  • LP eNB may be implemented with a picocell eNB since it is coupled to a macro eNB via an X2 interface.
  • Picocell eNBs or other LP eNBs may incorporate some or all functionality of a macro eNB. In some cases, this may be referred to as an access point base station or enterprise femtocell.
  • a downlink resource grid may be used for downlink transmissions from an eNB 104 to a UE 102, while uplink transmission from the UE 102 to the eNB 104 may utilize similar techniques.
  • the grid may be a time-frequency grid, called a resource grid or time -frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time -frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid correspond to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • Each resource grid comprises a number of resource blocks (RBs), which describe the mapping of certain physical channels to resource elements.
  • RBs resource blocks
  • Each resource block comprises a collection of resource elements in the frequency domain and may represent the smallest quanta of resources that currently can be allocated.
  • the physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to a UE 102 (FIG. 1).
  • the physical downlink control channel (PDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It also informs the UE 102 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel.
  • HARQ hybrid automatic repeat request
  • downlink scheduling (e.g., assigning control and shared channel resource blocks to UEs 102 within a cell) may be performed at the eNB 104 based on channel quality information fed back from the UEs 102 to the eNB 104, and then the downlink resource assignment information may be sent to a UE 102 on the control channel (PDCCH) used for (assigned to) the UE 102.
  • PDCCH control channel
  • the PDCCH uses CCEs (control channel elements) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols are first organized into quadruplets, which are then permuted using a sub-block inter-leaver for rate matching. Each PDCCH is transmitted using one or more of these control channel elements (CCEs), where each CCE corresponds to nine sets of four physical resource elements known as resource element groups (REGs). Four QPSK symbols are mapped to each REG.
  • CCEs control channel elements
  • REGs resource element groups
  • 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.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.
  • FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments.
  • the machine 200 is an example machine upon which any one or more of the techniques and/or methodologies discussed herein may be performed.
  • the machine 200 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 200 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 200 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the machine 200 may be a UE 102, eNB 104, access point (AP), station (STA), mobile device, base station, personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • the term "machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
  • Examples as described herein may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a machine readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general -purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • the machine 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208.
  • the machine 200 may further include a display unit 210, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse).
  • the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display.
  • the machine 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors 221, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • the machine 200 may include an output controller 228, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • NFC near field communication
  • the storage device 216 may include a machine readable medium 222 on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, or within the hardware processor 202 during execution thereof by the machine 200.
  • one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the storage device 216 may constitute machine readable media.
  • the machine readable medium may be or may include a non-transitory computer-readable storage medium.
  • the machine readable medium may be or may include a computer-readable storage medium.
  • machine readable medium 222 is illustrated as a single medium, the term “machine readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.
  • the term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 200 and that cause the machine 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media.
  • Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable
  • machine readable media may include non-transitory machine readable media.
  • machine readable media may include machine readable media that is not a transitory propagating signal.
  • the instructions 224 may further be transmitted or received over a communications network 226 using a transmission medium via the network interface device 220 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers
  • Wi-Fi® Wi-Fi 802.16 family of standards known as WiMax®
  • WiMax® WiMax 802.5.4 family of standards
  • the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 226.
  • the network interface device 220 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques.
  • SIMO single-input multiple-output
  • MIMO multiple-input multiple-output
  • MISO multiple-input single-output
  • the network interface device 220 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
  • FIG. 3 is a block diagram of an Evolved Node-B (eNB) in accordance with some embodiments.
  • the eNB 300 may be a stationary non-mobile device.
  • the eNB 300 may be suitable for use as an eNB 104 as depicted in FIG. 1, in some embodiments.
  • the eNB 300 may be a legacy eNB 104, a 3 GPP LTE eNB (such as 104), a fourth generation (4G) eNB, a 5G eNB and/or other type of eNB or base station.
  • 4G fourth generation
  • the eNB 300 may include physical layer circuitry 302 and a transceiver 305, one or both of which may enable transmission and reception of signals to and from the UE 102, other eNBs, other UEs or other devices using one or more antennas 301.
  • the physical layer circuitry 302 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals.
  • the transceiver 305 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range. Accordingly, the physical layer circuitry 302 and the transceiver 305 may be separate components or may be part of a combined component.
  • the eNB 300 may also include medium access control layer (MAC) circuitry 304 for controlling access to the wireless medium.
  • the eNB 300 may also include processing circuitry 306 and memory 308 arranged to perform the operations described herein.
  • the eNB 300 may also include one or more interfaces 310, which may enable communication with other components, including other eNBs 104 (FIG. 1), components in the EPC 120 (FIG. 1) or other network components.
  • the interfaces 310 may enable communication with other components that may not be shown in FIG. 1, including components external to the network.
  • the interfaces 310 may enable communication between the eNB 300 and an access point (AP) and/or other component of a WLAN.
  • the interfaces 310 may be wired or wireless or a combination thereof.
  • an eNB or other base station may include some or all of the components shown in either FIG. 2 or FIG. 3 or both.
  • FIG. 4 is a block diagram of a User Equipment (UE) in accordance with some embodiments.
  • the UE 400 may be suitable for use as a UE 102 as depicted in FIG. 1.
  • the UE 400 may include application circuitry 402, baseband circuitry 404, Radio Frequency (RF) circuitry 406, front-end module (FEM) circuitry 408 and one or more antennas 410, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • other circuitry or arrangements may include one or more elements and/or components of the application circuitry 402, the baseband circuitry 404, the RF circuitry 406 and/or the FEM circuitry 408, and may also include other elements and/or components in some cases.
  • processing circuitry may include one or more elements and/or components, some or all of which may be included in the application circuitry 402 and/or the baseband circuitry 404.
  • a "transceiver” or “transceiver circuitry” may include one or more elements and/or components, some or all of which may be included in the RF circuitry 406 and/or the FEM circuitry 408. These examples are not limiting, however, as the processing circuitry, the transceiver and/or the transceiver circuitry may also include other elements and/or components in some cases. It should be noted that in some embodiments, a UE or other mobile device may include some or all of the components shown in either FIG. 2 or FIG. 4 or both.
  • the application circuitry 402 may include one or more application processors.
  • the application circuitry 402 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors,
  • 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.
  • the baseband circuitry 404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 404 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 406 and to generate baseband signals for a transmit signal path of the RF circuitry 406.
  • Baseband processing circuitry 404 may interface with the application circuitry 402 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 406.
  • the baseband circuitry 404 may include a second generation (2G) baseband processor 404a, third generation (3G) baseband processor 404b, fourth generation (4G) baseband processor 404c, and/or other baseband processor(s) 404d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 404 e.g., one or more of baseband processors 404a-d
  • the radio control functions may include, but are not limited to, signal modulation/demodulation,
  • modulation/demodulation circuitry of the baseband circuitry 404 may include Fast-Fourier Transform (FFT), precoding, and/or constellation
  • encoding/decoding circuitry of the baseband circuitry 404 may include convolution, tail-biting convolution, turbo, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 404 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
  • EUTRAN evolved universal terrestrial radio access network
  • a central processing unit (CPU) 404e of the baseband circuitry 404 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 404f.
  • the audio DSP(s) 404f may be include elements for
  • compression/decompression and echo cancellation 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.
  • some or all of the constituent components of the baseband circuitry 404 and the application circuitry 402 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 404 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 404 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
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WLAN wireless personal area network
  • Embodiments in which the baseband circuitry 404 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 406 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 406 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 406 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 408 and provide baseband signals to the baseband circuitry 404.
  • RF circuitry 406 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 404 and provide RF output signals to the FEM circuitry 408 for transmission.
  • the RF circuitry 406 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 406 may include mixer circuitry 406a, amplifier circuitry 406b and filter circuitry 406c.
  • the transmit signal path of the RF circuitry 406 may include filter circuitry 406c and mixer circuitry 406a.
  • RF circuitry 406 may also include synthesizer circuitry 406d for synthesizing a frequency for use by the mixer circuitry 406a of the receive signal path and the transmit signal path.
  • the mixer circuitry 406a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 408 based on the synthesized frequency provided by synthesizer circuitry 406d.
  • the amplifier circuitry 406b may be configured to amplify the down-converted signals and the filter circuitry 406c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 404 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 406a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 406a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 406d to generate RF output signals for the FEM circuitry 408.
  • the baseband signals may be provided by the baseband circuitry 404 and may be filtered by filter circuitry 406c.
  • the filter circuitry 406c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • LPF low-pass filter
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a of the transmit signal path may be configured for super-heterodyne operation.
  • 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.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 406 may include analog -to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 404 may include a digital baseband interface to communicate with the RF circuitry 406.
  • ADC analog -to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 406d may be a fractional -N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 406d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 406d may be configured to synthesize an output frequency for use by the mixer circuitry 406a of the RF circuitry 406 based on a frequency input and a divider control input.
  • the synthesizer circuitry 406d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 404 or the applications processor 402 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by the applications processor 402.
  • Synthesizer circuitry 406d of the RF circuitry 406 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • 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.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • 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.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 406d 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.
  • the output frequency may be a LO frequency (fLo).
  • the RF circuitry 406 may include an IQ/polar converter.
  • FEM circuitry 408 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 410, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 406 for further processing.
  • FEM circuitry 408 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 410, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 406 for further processing.
  • a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 406 for transmission by one or more of the one or more antennas 410.
  • the FEM circuitry 408 may include a
  • TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 406).
  • the transmit signal path of the FEM circuitry 408 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 406), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 410.
  • the UE 400 may include additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface.
  • the antennas 230, 301, 410 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • MIMO multiple-input multiple-output
  • the antennas 230, 301 , 410 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • the UE 400 and/or the eNB 300 may be a mobile device and may be a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device such as a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • a laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device such as a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or
  • Mobile devices or other devices in some embodiments may be configured to operate according to other protocols or standards, including IEEE 802.11 or other IEEE standards.
  • the UE 400, eNB 300 or other device may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the UE 400 and the eNB 300 are each illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may comprise one or more microprocessors, DSPs, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements may refer to one or more processes operating on one or more processing elements.
  • Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
  • a computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • UE may include various components of the UE 400 and/or the machine 200 as shown in FIGs. 2 and 4. Accordingly, techniques and operations described herein that refer to the UE 400 (or 102) may be applicable to an apparatus for a UE, in some embodiments.
  • an apparatus for an eNB may include various components of the eNB 300 and/or the machine 200 as shown in FIGs. 3 and 4. Accordingly, techniques and operations described herein that refer to the eNB 300 (or 104) may be applicable to an apparatus for an eNB, in some embodiments.
  • the UE in a sub-frame, the UE
  • UE 102 may receive, from an eNB 104 on multiple component carriers (CCs) of a carrier aggregation (CA), one or more physical downlink control channels (PDCCHs) and one or more physical downlink shared channel (PDSCH) transmissions scheduled by the PDCCHs.
  • the UE 102 may also receive, from the eNB, a semi-persistent scheduling (SPS) PDSCH transmission that is scheduled in the sub-frame by an SPS schedule configured prior to the sub- frame.
  • SPS semi-persistent scheduling
  • HARQ-ACK bits for the PDSCH transmissions may be mapped to bit positions of a HARQ-ACK bit sequence that are indicated by the PDCCHs.
  • a HARQ-ACK bit for the SPS PDSCH transmission may be mapped to a predetermined bit position of the HARQ-ACK bit sequence that is reserved for the SPS PDSCH transmission.
  • the UE 102 may transmit the HARQ-ACK bit sequence to the eNB 104.
  • FIG. 5 illustrates example carrier aggregation (CA) arrangements in accordance with some embodiments. It should be noted that embodiments are not limited by the example CA arrangements 500, 550 in terms of number, type or arrangement of the channel resources or component carriers (CCs) shown in FIG. 5.
  • CCs channel resources or component carriers
  • contiguous CCs 515 may be used, as indicated by 510.
  • non-contiguous CCs 555 may be used.
  • CCs may be used in contiguous or non-contiguous CA arrangements. As a non-limiting example, up to 5 CCs may be used. As another non-limiting example, up to 32 CCs may be used. In some cases, although a certain number of CCs may be available for usage, it may be possible that a portion of the CCs are configured for usage as part of a particular communication. For instance, a fraction of 32 available CCs may be used for a downlink communication between the eNB 104 and the UE 102.
  • FIG. 6 illustrates the operation of a method of communication in accordance with some embodiments. It is important to note that embodiments of the method 600 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 6. In addition, embodiments of the method 600 are not necessarily limited to the chronological order that is shown in FIG. 6. In describing the method 600, reference may be made to FIGs. 1-5 and 7- 14, although it is understood that the method 600 may be practiced with any other suitable systems, interfaces and components.
  • the method 600 and other methods described herein may refer to eNBs 104 and/or UEs 102 operating in accordance with 3GPP standards, embodiments of those methods are not limited to just those devices.
  • the methods may be practiced by other devices, such as a Wi-Fi access point (AP) or user station (STA) or a 5G device.
  • the UE 102 and/or other device may be arranged to operate in accordance with multiple protocols, such as a 3GPP protocol and a 5G protocol.
  • the method 600 and other methods described herein may be practiced by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various IEEE standards such as IEEE 802.1 1.
  • the method 600 may also refer to an apparatus for a UE 102, eNB 104, 5G device and/or other device.
  • one or more operations of the method 600 may be performed in accordance with carrier aggregation (CA) techniques, although the scope of embodiments is not limited in this respect.
  • CA carrier aggregation
  • embodiments are not limited by references herein (such as in descriptions of the methods 600, 1000, 1400 and/or other descriptions herein) to transmission, reception and/or exchanging of elements such as frames, messages, requests, indicators, signals or other elements.
  • an element may be generated, encoded or otherwise processed by processing circuitry (such as by a baseband processor included in the processing circuitry) for transmission.
  • the transmission may be performed by a transceiver or other component, in some cases.
  • such an element may be decoded, detected or otherwise processed by the processing circuitry (such as by the baseband processor).
  • the element may be received by a transceiver or other component, in some cases.
  • the processing circuitry and the transceiver may be included in a same apparatus. The scope of embodiments is not limited in this respect, however, as the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.
  • the UE 102 may configure one or more semi- persistent scheduling (SPS) arrangements.
  • the UE 102 and the eNB 104 may exchange one or more control messages to establish the one or more SPS arrangements.
  • an SPS schedule may be established in which the eNB 104 may transmit a physical downlink shared channel (PDSCH) transmission to the UE 102 in predetermined time resources and/or channel resources during a subsequent time period.
  • PDSCH physical downlink shared channel
  • Such PDSCH transmissions may be referred to herein, for purpose of clarity, as SPS PDSCH transmissions.
  • a periodicity of the SPS PDSCH transmissions may be established, although embodiments are not limited to periodic SPS PDSCH transmissions.
  • the eNB 104 may transmit an SPS PDSCH transmission in same resource blocks (RBs) during a same group of one or more OFDM symbol periods of every Nth sub-frame.
  • RBs resource blocks
  • a transmission of a physical downlink shared channel (PDCCH) by the eNB 104 to schedule the SPS PDSCH may not be necessary.
  • the SPS PDSCH transmission may be performed without a PDCCH, in some cases.
  • a PDSCH transmission that is not an SPS PDSCH transmission may be scheduled by a PDCCH in a same sub-frame.
  • the PDCCH may include scheduling information for the PDSCH transmission, in some cases.
  • the UE 102 may receive one or more PDCCHs during a sub-frame.
  • the UE 102 may receive the one or more PDCCHs from the eNB 104 during the sub-frame, although the scope of embodiments is not limited in this respect.
  • the sub-frame may be referred to, for purpose of clarity, as a current sub-frame.
  • the UE 102 may receive one or more data blocks, control blocks, data messages, control messages and/or other elements in accordance with time resources and/or channel resources that may be allocated for PDCCH transmission of such elements by the eNB 104 to one or more UEs 102. Reception of the one or more
  • PDCCHs may refer to reception of one or more such elements by the UE 102, in some embodiments.
  • the UE 102 may receive one or more PDCCH blocks, PDCCH control blocks and/or other elements.
  • the PDCCHs may be formatted in accordance with one or more downlink control information (DCI) formats.
  • DCI downlink control information
  • the PDCCHs may be formatted in accordance with different DCI formats, although the scope of embodiments is not limited in this respect.
  • a common DCI format may be used for multiple PDCCHs received by the UE 102 in the sub-frame.
  • Example DCI formats may include, but are not limited to, types
  • the UE 102 may receive one or more PDSCH transmissions during the current sub-frame.
  • the UE 102 may receive the one or more PDSCH transmissions from the eNB 104 during the current sub-frame, although the scope of embodiments is not limited in this respect.
  • the UE 102 may receive one or more data blocks, control blocks, data messages, control messages and/or other elements in accordance with time resources and/or channel resources that may be allocated for PDSCH transmission of such elements by the eNB 104 to one or more UEs 102.
  • Reception of the one or more PDSCH transmissions may refer to reception of one or more such elements by the UE 102, in some embodiments.
  • the UE 102 may receive one or more PDSCH blocks, PDSCH data blocks and/or other elements.
  • the PDCCHs may include scheduling information, such as RB(s), OFDM symbol period(s) and/or other information, to be used by the UE 102 to receive the PDSCH transmissions. Accordingly, the PDCCHs may schedule the PDSCH transmissions, in some cases. In some embodiments, each PDSCH transmission may be scheduled by one of the PDCCHs, although the scope of embodiments is not limited in this respect.
  • the UE 102 may receive one or more SPS
  • the UE 102 may receive the one or more SPS PDSCH transmissions from the eNB 104 in the sub-frame, although the scope of embodiments is not limited in this respect.
  • one or more SPS schedules may be established prior to the current sub-frame. Accordingly, an SPS PDSCH transmission may or may not be scheduled during the current sub-frame. This may be determined by the UE 102, in some cases, by a comparison of a sub-frame index of the current sub- frame with a pattern of sub-frame indexes of the SPS schedule (such as the indexes of sub-frames in which the SPS PDSCH transmissions are to be performed).
  • the UE 102 may decode (or attempt to decode) the SPS PDSCH transmission.
  • an over-ride of a scheduled SPS PDSCH transmission may be sent from the eNB 104 to the UE 102.
  • a PDCCH (which may be referred to herein as an SPS over-ride PDCCH for purposes of clarity) may indicate such an over-ride.
  • channel resources used for downlink data transmission may comprise multiple component carriers (CCs) in a carrier aggregation (CA).
  • the UE may be configured to simultaneously receive, on each CC of a sub-group of the CCs in the sub-frame: one of the PDCCHs, one of the PDSCH transmissions, one of the SPS PDSCH transmissions, or another PDCCH (such as an SPS over-ride PDCCH) that indicates an over-ride of one of the SPS PDSCH transmissions scheduled for the CC in the sub-frame.
  • the UE 102 may receive one of the above elements on each CC, although the scope of embodiments is not limited in this respect.
  • scheduling of the PDSCH transmissions by the PDCCHs may be configurable for a self-scheduling arrangement or a cross-carrier scheduling arrangement.
  • each PDSCH transmission may be scheduled by a corresponding PDCCH that is received on a same CC as the PDSCH transmission.
  • the PDCCHs may be received on one or more CCs.
  • the CCs may be configured by the eNB 104, in some cases.
  • the PDCCHs may be received on a same CC and may schedule the PDSCH transmissions on the multiple CCs (which may include the CC on which the PDCCHs are received, in some cases).
  • the PDCCHs may be received on multiple CCs, but one or more of the PDCCHs may schedule PDSCH transmissions on other CCs.
  • the UE 102 may determine HARQ-ACK bits for the PDSCH transmissions and/or SPS PDSCH transmission(s). The UE 102 may determine the HARQ-ACK bits for the decoded PDSCH transmissions based on whether the PDSCH transmissions are successfully decoded. The UE 102 may determine a HARQ-ACK bit for the decoded SPS PDSCH transmission based on whether the SPS PDSCH transmission is successfully decoded.
  • the UE 102 may map the HARQ-ACK bits to bit positions of a HARQ-ACK bit sequence.
  • the UE 102 may transmit the HARQ-ACK bit sequence.
  • the UE 102 may transmit the HARQ-ACK bit sequence to the eNB 104, although the scope of embodiments is not limited in this respect.
  • Various techniques may be used to map the HARQ-ACK bits to the HARQ-ACK bit sequence. Some or all of those techniques may be performed to enable a common understanding between the UE 102 and the eNB 104 about a size of the HARQ-ACK bit sequence and/or ordering of bits within the HARQ-ACK bit sequence. In some scenarios, a misalignment of the size and/or ordering of the HARQ-ACK bit sequence may occur between what is encoded by the UE 102 and what is interpreted by the eNB 104. In some cases, techniques described herein may mitigate, prevent or reduce such occurrences. Example scenarios of misalignment will be presented below.
  • HARQ-ACK bits for the PDSCH transmissions may be mapped to bit positions of the HARQ-ACK bit sequence that are indicated by the PDCCHs.
  • a HARQ-ACK bit for the received SPS PDSCH transmission may be mapped to the HARQ-ACK bit sequence in a predetermined bit position reserved for the SPS PDSCH transmissions.
  • the bit position for the SPS PDSCH transmission may be a least significant bit (LSB) of the HARQ-ACK bit sequence.
  • the bit position for the SPS PDSCH transmission may be a most significant bit (MSB) of the HARQ-ACK bit sequence.
  • MSB most significant bit
  • Embodiments are not limited to the LSB or MSB, however, as any suitable bit position(s) may be reserved.
  • embodiments are not limited to a single SPS PDSCH transmission or to a single bit of the HARQ-ACK bit sequence.
  • multiple HARQ-ACK bits for multiple SPS PDSCH are not limited to a single SPS PDSCH transmission or to a single bit of the HARQ-ACK bit sequence.
  • multiple HARQ-ACK bits for multiple SPS PDSCH are not limited to a single SPS PDSCH transmission or to a single bit of the HARQ-ACK bit sequence.
  • multiple HARQ-ACK bits for multiple SPS PDSCH are not limited to a single SPS PDSCH transmission or to a single bit of the HARQ-ACK bit sequence.
  • transmissions may be mapped to multiple predetermined bit positions of the HARQ-ACK sequence. For instance, a top portion of bit indexes (such as MSBs) or a bottom portion of bit indexes (such as LSBs) may be reserved for HARQ-ACK bits for SPS PDSCH transmissions.
  • a top portion of bit indexes such as MSBs
  • a bottom portion of bit indexes such as LSBs
  • PDCCHs may include a total downlink assignment indicator (DAI) field and a DAI counter field.
  • the total DAI field may be based on a count for the sub-frame that includes PDSCH transmissions, SPS PDSCH transmissions, and PDCCHs that over-ride SPS PDSCH transmissions. For instance, PDSCH transmissions scheduled for the sub-frame, SPS PDSCH transmissions scheduled for the sub-frame, and PDCCHs to be transmitted in the sub-frame that over-ride SPS PDSCH transmissions may be included in the count.
  • the DAI counter field may be based on a count for the sub-frame that includes the PDSCH transmissions and the PDCCHs that over-ride SPS PDSCH transmissions and excludes the SPS PDSCH transmissions.
  • downlink channel resources used by the eNB 104 may comprise multiple CCs in a CA arrangement.
  • the UE 102 may be configured to simultaneously receive, on each CC of a sub-group of the CCs in the sub-frame: one of the PDCCHs, one of the PDSCH transmissions, one of the SPS PDSCH transmissions, or another PDCCH that indicates an override of one of the SPS PDSCH transmissions scheduled for the CC in the sub- frame.
  • the total DAI field may be based on a summation of: a number of the CCs of the sub-group on which one of the PDSCH transmissions is scheduled in the sub-frame by one of the PDCCHs, a number of the CCs of the sub-group on which one of the SPS PDSCH transmissions is scheduled for the sub-frame, and a number of the CCs of the sub-group on which an SPS over-ride PDCCH is to be received in the sub-frame.
  • the SPS over-ride PDCCH may indicate an over- ride of a previously scheduled SPS PDSCH transmission previously scheduled for the sub-frame.
  • the CCs of the downlink channel resources may be mapped to an ordered sequence of CC indexes.
  • the DAI counter may include the CCs of the sub-group on which one of the PDSCH transmissions is scheduled by one of the PDCCHs in the sub-frame.
  • the DAI counter may exclude the CCs of the sub-group on which one of the SPS PDSCH transmissions is scheduled in the sub-frame.
  • the DAI counter may include the CCs of the sub-group on which an over-ride PDCCH is to be received in the sub-frame.
  • HARQ-ACK bits for PDSCH transmissions scheduled by PDCCHs may be mapped to bit positions of the HARQ-ACK bit sequence based on values of DAI counter fields of the PDCCHs that schedule the PDSCH transmissions.
  • total DAI fields of the PDCCHs may indicate a size of the HARQ-ACK bit sequence and the DAI counter fields may indicate bit positions of the HARQ-ACK bit sequence to be used.
  • a particular PDCCH may schedule a particular PDSCH transmission.
  • the particular PDCCH may be formatted in accordance with a DCI format that comprises a total DAI field that indicates a size of the HARQ-ACK bit sequence.
  • the total DAI may be based on a summation that includes a count of the SPS PDSCH transmissions scheduled in the sub-frame and further includes a count of the PDSCH transmissions scheduled in the sub-frame by the PDCCHs.
  • the DCI format may further comprise a DAI counter field that indicates an index of the particular PDSCH transmission in a range between one and the total DAI. Accordingly, a bit position to which the HARQ-ACK bit for the particular PDSCH is to be mapped may be indicated by the DAI counter field.
  • the PDSCH transmissions may be received in multiple CCs in accordance with a CA arrangement.
  • the CCs of the CA may be mapped to an ordered sequence of CC indexes.
  • the PDCCHs may indicate the CCs on which the PDSCH transmissions are to be received in the sub-frame.
  • the CC on which the particular PDSCH is received may be mapped to a particular CC index.
  • the DAI counter of the particular PDCCH may be based on a count of the PDSCH transmissions received in the sub-frame for which CC indexes are lower than the particular CC index.
  • the DAI counter of the particular PDCCH may be exclusive to a count of the SPS PDSCH transmissions received in the sub-frame.
  • PDCCHs may be included in either a UE specific search space (USS) or a common search space (CSS) accessible to the UE 102 and to other UEs 102.
  • each PDCCH may be scrambled by a UE-specific radio network temporary identifier (RNTI) of the UE 102.
  • RNTI radio network temporary identifier
  • Each PDCCH included in the USS may include a total DAI field that is based on a count of CCs on which one of the PDSCH transmissions is scheduled by one of the PDCCHs included in either the USS or the CSS.
  • Each PDCCH of the USS may further include a DAI counter.
  • the DAI counter may include a count of CCs on which one of the PDSCH transmissions is scheduled by one of the PDCCHs included in the USS.
  • the DAI counter may exclude a count of CCs on which one of the PDSCH transmissions is scheduled by one of the PDCCHs included in the CSS.
  • each PDCCH may be scrambled by a common RNTI, and each PDCCH may exclude the total DAI and the DAI counter fields.
  • HARQ-ACK bits for the PDSCH transmissions scheduled by the PDCCHs included in the USS may be mapped to the HARQ-ACK bit sequence in bit positions that are based on values of the DAI counter fields of the PDCCHs.
  • PDSCH transmissions scheduled by the PDCCHs included in the CSS may be mapped to the HARQ-ACK bit sequence in bit positions that are reserved for PDSCH transmissions scheduled by the PDCCHs included in the CSS. For instance, one or more LSBs, one or more MSBs or other suitable bit(s) may be reserved.
  • the UE 102 may decode a plurality of
  • the PDSCH transmissions received in a sub-frame from the eNB 104 on a plurality of component carriers (CCs) of a carrier aggregation (CA).
  • the PDSCH transmissions may be scheduled by a plurality of PDCCHs received in the sub- frame from the eNB 104.
  • the UE 102 may decode a semi-persistent scheduling (SPS) PDSCH transmission received in the sub-frame from the eNB 104 on one of the CCs.
  • SPS semi-persistent scheduling
  • the SPS PDSCH transmission may be scheduled prior to the sub- frame and exclusively to the PDCCHs.
  • the UE 102 may encode, for transmission to the eNB 104, a HARQ-ACK bit sequence of HARQ-ACK bits.
  • HARQ-ACK bits for the PDSCH transmissions may be mapped to bit positions of the HARQ-ACK bit sequence in accordance with information included in the PDCCHs.
  • a HARQ-ACK bit of the SPS PDSCH transmission may be mapped to a fixed position of the HARQ-ACK bit sequence reserved for the HARQ- ACK bit of the SPS PDSCH transmission.
  • FIGs. 7-9 and 1 1-13 illustrate examples of hybrid automatic repeat request (HARQ) acknowledgement in accordance with some
  • FIG. 10 illustrates the operation of another method of communication in accordance with some embodiments.
  • FIGs. 7-13 may illustrate some or all of the concepts, operations and/or techniques described herein, although the scope of embodiments is not limited by the examples. It should be noted that embodiments are not limited by the examples in terms of arrangement, ordering, type, size, number and/or other aspects of the elements of the examples shown in FIGs. 7- 13.
  • CA carrier aggregation
  • a CA feature may enable aggregation of up to five carriers of the same frame structure. In some cases, deployments may become capacity limited due to interference and the volume of data delivered.
  • a standard such as 3GPP may use a CA feature in which up to 32 component carriers (CCs) may be used. For instance, a frequency band such as the C-band (3.4-4.2 GHz) licensed band, a 5 GHz band (which may include about 500 MHz of unlicensed spectrum in some cases) may be used. Accordingly, an increased amount of resources may be provided for data capabilities and to better manage interference, in some cases.
  • CCs component carriers
  • 32 DL carriers may increase significantly the amount of hybrid automatic repeat request (HARQ) acknowledgement (ACK) bits to be fed back from the UE 102 to the eNB 104.
  • HARQ hybrid automatic repeat request
  • ACK acknowledgement
  • a single UL sub-frame may be used, in some cases.
  • the UE 102 may not necessarily be scheduled on all cells that are configured in the CA arrangement. For instance, some secondary cells (SCells) may even be deactivated, in some cases.
  • SCells secondary cells
  • the HARQ-ACK feedback size is semi-statistically determined according to the number of configured serving cells, the UE 102 may, in some cases, transmit a considerable number of HARQ-ACK feedback bits associated with non-scheduled serving cells. As a result, PUCCH overhead may be increased unnecessarily.
  • a HARQ-ACK codebook size may be adapted dynamically to enable the UE 102 to provide the HARQ-ACK feedback to the UE 102.
  • the HARQ-ACK codebook size may be adapted dynamically in accordance with a number of scheduled serving cells and/or sub- frames, in some cases.
  • a downlink control information (DCI) message may include one or more fields related to communication of the HARQ-ACK feedback. For instance, a Counter Downlink Assignment Index (DAI) field of two bits (or any suitable size), a total DAI field of two bits (or any suitable size) and/or other parameter(s) may be used.
  • DAI Counter Downlink Assignment Index
  • one or more rules, behaviors, guidelines and/or operations of a standard may be used.
  • a standard such as a 3 GPP standard and/or other standard.
  • codebooksizeDetermination-rl3 and/or similar parameter of a particular value (such as 0 or other suitable value) for a frequency division duplex (FDD) arrangement and a sub-frame "n,” the value of the counter Downlink Assignment Indicator (DAI) in DCI format
  • 1/1A/1B/1D/2/2A/2B/2C/2D may denote the accumulative number of serving cell(s) with PDSCH transmission(s) associated with PDCCH/EPDCCH and serving cell with PDCCH/EPDCCH indicating downlink SPS release, up to the present serving cell in increasing order of serving cell index;
  • the value of the total DAI in DCI format 1/1A/1B/1D/2/2A/2B/2C/2D may denote the total number of serving cell(s) with PDSCH transmission(s) associated with
  • PDCCH/EPDCCH(s) and serving cell with PDCCH/EPDCCH indicating downlink SPS release may be part of a 3GPP standard, it is understood that the scope of embodiments is not limited in this respect.
  • the total DAI field may count a number of PDCCH / EPDCCH(s) transmitted, but may refrain from counting PDSCHs that are transmitted without a corresponding PDCCH. More specifically, the total DAI field as described above may cause a different understanding between the eNB 104 and the UE 102, in some cases, on HARQ-ACK codebook size as well as on the order of reported HARQ-ACK bits when semi-persistent scheduling (SPS) PDSCH (such as on the primary cell (PCell) and/or otherwise) is activated.
  • SPS semi-persistent scheduling
  • the UE 102 configured with DL SPS may monitor PDCCH using C-RNTI in each non-DRX subframe for dynamic allocation and the PDCCH allocation using C-RNTI may overrides an existing SPS allocation for that TTI.
  • FIG.7 illustrates a potential error case that may occur for some designs of counter DAI and total DAI.
  • the UE 102 is configured with 16 activated CCs and SPS PDSCH may be configured on the PCell.
  • both eNB 104 and UE 102 will assume 6 CCs are scheduled and correspondingly generate 6 HARQ- ACK bits (here assume 1 HARQ-ACK bit per CC) ordered by counter DAI value as illustrated in the middle of FIG.7.
  • the UE 102 may generate 7 HARQ-ACK bits assuming one DL grant on either CC1 or CC2 was missed.
  • eNB still assume 6 HARQ-ACK bits due to lack of information about the PDCCH detection result at the UE 102.
  • ACK codebook size adaptation method is how to map the HARQ-ACK bits associated with PDSCH scheduled by PDCCH on Common Search Space (CSS).
  • CSS Common Search Space
  • inclusion of counter DAI and total DAI fields may be limited to DCI formats in UE specific Search Space (USS) and may not necessarily be present for DCI formats in CSS.
  • This design may also result in the HARQ-ACK codebook misalignment between eNB 104 and UE 102 as illustrated in FIG. 8. If the total DAI onllly counts the PDCCH in CSS only, misalignment between eNB 104 and UE 102 in terms of HARQ-ACK bits ordering would happen when PDCCH in CSS was missed by UE 102.
  • dynamic HARQ-ACK codebook size adaptation may be supported with activated SPS PDSCH on PCell.
  • the value of a total DAI field may count the total number of serving cell(s) with following PDSCH transmissions: PDSCH associated with PDCCH/EPDCCH(s), including dynamic DL grant and SPS overridden by dynamic grant; serving cell with PDCCH/EPDCCH indicating downlink SPS release; and SPS PDSCH transmission without a corresponding PDCCH.
  • PDSCH transmission in a SPS sub-frame may not be counted for a counter DAI value accumulation operation, regardless of SPS PDSCH transmission or PDSCH transmission that is scheduled by PDCCH.
  • the value of counter DAI field may include (or be restricted to) an accumulative number of ⁇ serving cells, non-SPS sub-frame> pairs in which PDSCH transmission(s) associated with PDCCH/ EPDCCH and serving cell with PDCCH/EPDCCH indicating downlink SPS release up to the present serving cell and present sub-frame, first in increasing order of serving cell index and then in increasing order of sub-frame index within HARQ-ACK bundling window.
  • the value of counter DAI and total DAI of PDCCH using C-RNTI in a SPS DL sub-frame may be set to a predefined value and then ignored by UE 102.
  • HARQ-ACK associated with a PDSCH transmission in SPS sub-frame may be mapped to a fix or pre-known position within a HARQ-ACK bits sequence to ensure a same understanding between UE 102 and eNB 104 on HARQ-ACK bit ordering.
  • the HARQ-ACK bit associated with PDSCH in a SPS sub-frame may be mapped to the least significant bit (LSB) or most significant bit (MSB) of the HARQ-ACK bits sequence.
  • FIG. 9 illustrates the details of setting counter DAI and total DAI disclosed as described herein, which can address the problem in FIG. 7.
  • the error case happens when a dynamic DL grant is transmitted in a SPS sub-frame on CC0 to override the SPS PDSCH
  • CC3/CC4/CC5/CC14/CC15 does NOT count the dynamic DL grant transmitted in SPS sub-frame in CCO, while the value of total DAI field counts the SPS sub- frame.
  • the UE 102 may map the HARQ-ACK bit associated with SPS sub- frame to the MSB of the HARQ-ACK bit sequence, which is followed by the HARQ-ACK bits for non-SPS sub-frame(s) on SCells. Consequently, the problem of misalignment on the HARQ-ACK codebook size and ordering may be eliminated, in some cases.
  • FIG. 10 another exemplary design 1000 for sending
  • the value of counter DAI in DCI formats denotes the accumulative number of assigned PDSCH transmission with corresponding PDCCH(s) and serving cell with PDCCH/EPDCCH indicating downlink SPS release up to the ⁇ serving cells, subframe> pairs.
  • SPS PDSCH without PDCCH is not counted for counter DAI accumulation operations.
  • which can be zero or one as the number of PDSCH transmissions without a corresponding PDCCH (i.e. SPS PDSCH) within the HARQ-ACK bundling window.
  • the UE 102 may determine the number of HARQ-ACK codebook size Q& Q according to the value of total DAI field and the HARQ-ACK feedback ordering
  • the HARQ-ACK for a PDSCH transmission with a corresponding counter DAI value CJ Alfyn* k) in PDCCH in subframe k on CC m may be associated with HARQ-ACK bits of ⁇ eH JiM ⁇ mJ0-iV 3 ⁇ 43 ⁇ 4C3 ⁇ 4I -1 > if the hi ⁇ her la y er P arameter
  • spatialBundlingPUCCH is set to FALSE and the UE 102 is configured with a transmission mode supporting two transport blocks in at least one configured serving cell or associated with ⁇ ?e3 ⁇ 4itm 3 ⁇ 4:)-I' otherwise.
  • Ngps £- the HARQ-ACK associated with a PDSCH transmission without a corresponding PDSCH is mapped to Q ⁇ _. L (block 1040).
  • the value of total DAI IEs and counter DAI IEs are shown for configured DL CCs in which the eNB 104 transmits a PDCCH to a UE 102, including non-SPS sub-frame as well as SPS sub-frame.
  • the total DAI is set as "6" with counting the dynamic PDCCH on PCell (i.e. CCO) although it has been configured as an SPS sub-frame.
  • the counter DAI IE values in this example starts from CCO in a SPS sub-frame, where a dynamic PDCCH using C-R TI is used to override an existing SPS allocation. As the UE 102 does not detect SPS allocation (i.e. Nsps
  • the HARQ-ACK bit associated with PDSCH scheduled by PDCCH in CSS may be mapped to a fixed or known position within a HARQ-ACK bits sequence.
  • the value of total DAI field on USS on other CCs may count the PDSCH associated with PDCCH in CSS.
  • the counter DAI may be designed in different manners for FDD and TDD system. In a first example design of counter DAI for FDD system as illustrated in FIG. 12a, the PDSCH scheduled by CSS on PCell may be NOT counted for counter DAI accumulation operation.
  • the HARQ- ACK bit associated with PDSCH scheduled by PDCCH in CSS may be mapped to the LSB or MSB of the HARQ-ACK bits sequence if it is detected by UE.
  • the UE receives the PDSCH 1210 in CCO and correspondingly maps the associated HARQ-ACK bit 1220 to the fixed position (i.e. MSB or LSB) of HARQ-ACK bits sequence.
  • the PDSCH scheduling by CSS on PCell may be also counted for counter DAI accumulation, same as PDSCH scheduled by PDCCH in USS.
  • the UE 102 may determine the total HARQ-ACK bits number based on total DAI field value (i.e.
  • 2-bits DAI IE is included in each DL DCI formats in CSS, in some cases. This makes DAI design for CSS in TDD different than FDD system.
  • the 2-bits DAI IE can be reused as a counter DAI IE if dynamic HARQ-ACK codebook determination is configured by higher layers for HARQ-ACK feedback.
  • PDSCH scheduled by PDCCH in CSS may be counted for total DAI value accumulation.
  • UE determines HARQ-ACK codebook size based on the value of total DAI field of PDCCH in USS and orders HARQ-ACK bits based on counter DAI value of PDCCH in USS as well as CSS.
  • the 2-bit DAI field of Rel-8 may be reused as total DAI field if the dynamic HARQ-ACK codebook determination is configured by higher layers for HARQ-ACK feedback.
  • HARQ-ACK for PDCCH in CSS can map to LSB (or MSB) in UCI payload in accordance with the corresponding sub-frame index.
  • the HARQ-ACK for SPS PDSCH without PDCCH, if present, is mapped to MSB (or LSB) in UCI payload on
  • FIG. 13 illustrates the usage of 2-bits DAI field as the counter DAI of PDCCH in CSS for TDD system.
  • 2-bit counter DAI field of PDCCH in CSS is set value to 4 in sub-frame 1 on CC0 1310.
  • the UE 102 can identify that it received 3 DL SAs and generates 3 HARQ-ACK bits 1350 assuming it has been configured with a TM enabling the reception of 1 TB.
  • the UE receives SPS PDSCH 1330 without PDCCH on Cell 0 and maps a HARQ-ACK bit to a fixed position 1340 (e.g. MSB bl 1) of a HARQ-ACK bits sequence.
  • a fixed position 1340 e.g. MSB bl 1
  • FIG. 14 illustrates the operation of another method of communication in accordance with some embodiments.
  • embodiments of the method 1400 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 14.
  • Embodiments of the methods 1400 are not necessarily limited to the chronological order that is shown in FIG. 14.
  • embodiments of the method 1400 may be applicable to UEs 102, eNBs 104, STAs, APs and/or other wireless or mobile devices.
  • the method 1400 may be applicable to an apparatus for a UE 102, eNB 104, STA, AP and/or other wireless or mobile device, in some embodiments.
  • the method 1400 may be practiced by an eNB 104 or other base station.
  • the method 600 may be practiced by a UE 102 or other mobile device. It should be noted that one or more operations of one of the methods 600 and/or 1400 may be reciprocal to, similar to and/or related to one or more operations included in the other method.
  • an operation of the method 1400 may include transmission of an element (such as a PDCCH, a PDSCH transmission or other element) and an operation of the method 600 may include reception of the same element or similar element by the UE 102.
  • an element such as a PDCCH, a PDSCH transmission or other element
  • the eNB 104 may configure one or more SPS arrangements.
  • the UE 102 and the eNB 104 may exchange one or more control messages to establish the one or more SPS arrangements.
  • Previously described techniques may be used, in some embodiments, although the scope of embodiments is not limited in this respect.
  • the eNB 104 may
  • the eNB 104 may transmit one or more
  • the eNB 104 may transmit the one or more PDCCHs to the UE 102, although the scope of embodiments is not limited in this respect.
  • the eNB 104 may transmit one or more PDSCH transmissions. In some embodiments, the eNB 104 may transmit the one or more PDSCH transmissions to the UE 102, although the scope of embodiments is not limited in this respect.
  • the eNB 104 may transmit one or more SPS PDSCH transmissions. In some embodiments, the eNB 104 may transmit the one or more SPS PDSCH transmissions to the UE 102, although the scope of embodiments is not limited in this respect.
  • the eNB 104 may receive a HARQ-ACK bit sequence.
  • the eNB 104 may receive the HARQ-ACK bit sequence from the UE 102, although the scope of embodiments is not limited in this respect.
  • the transmissions may be performed by the eNB 104 on one or more component carriers (CCs) of a carrier aggregation (CA) in some embodiments.
  • CCs component carriers
  • CA carrier aggregation
  • the HARQ-ACK bit sequence may include one or more HARQ-
  • the HARQ- ACK bits for the PDSCH transmissions may be mapped to bit positions indicated by the PDCCHs and a HARQ-ACK bit for the SPS-PDSCH transmission may be mapped to a predetermined bit position reserved for the HARQ-ACK bit of the SPS PDSCH transmission.
  • downlink channel resources used by the eNB 104 may comprise multiple component carriers (CCs) for usage in a carrier aggregation (CA).
  • the eNB 104 may be configured to transmit, on each CC of a sub-group of the CCs in the sub-frame: one of the PDSCH
  • a downlink control information (DCI) format used for at least one of the PDCCHs may includes a total downlink assignment indicator (DAI) field and a DAI counter field.
  • DCI downlink control information
  • the total DAI field may be based on a summation of: a number of the CCs of the sub-group on which one of the
  • PDSCH transmissions is scheduled by one of the PDCCHs in the sub-frame, a number of the CCs of the sub-group on which an SPS PDSCH transmission is scheduled for the sub-frame, and a number of the CCs of the sub-group on which an SPS over-ride PDCCH is to be transmitted to indicate an over-ride of an SPS
  • the CCs of the downlink channel resources may be mapped to an ordered sequence of CC indexes.
  • the DAI counter field of the particular PDCCH may be based on a count that includes the CCs of the sub-group on which one of the PDSCH transmissions is scheduled in the sub-frame by one of the PDCCHs.
  • the count may exclude the CCs of the sub-group on which an SPS PDSCH transmission is scheduled in the sub-frame.
  • the count may also include the CCs of the sub-group on which an SPS over-ride PDCCH is transmitted.
  • embodiments may be described herein in terms of downlink communication, but embodiments are not limited to downlink communication.
  • some or all concepts, techniques, operations and/or methods described herein for the downlink communication may be applicable to uplink communication.
  • one or more transmit operations described herein may be performed by an eNB 104 as part of downlink communication with a UE 102.
  • the UE 102 may perform one or more of those transmit operations and/or similar operations as part of an uplink communication.
  • one or more receive operations described herein may be performed by the UE 102 as part of the downlink communication with the eNB 104.
  • the eNB 104 may perform one or more of those operations and/or similar operations as part of the uplink communication.
  • an apparatus of a User Equipment may comprise memory.
  • the apparatus may further comprise processing circuitry.
  • the processing circuitry may be configured to decode one or more physical downlink control channels (PDCCHs) received in a sub-frame.
  • the processing circuitry may be further configured to decode one or more physical downlink shared channel (PDSCH) transmissions received in the sub-frame, wherein the PDSCH transmissions are scheduled by the PDCCHs.
  • the processing circuitry may be further configured to map hybrid automatic repeat request
  • the processing circuitry may be further configured to determine whether one or more semi-persistent scheduling (SPS) PDSCH transmissions are scheduled in the sub-frame by SPS schedules that are configured prior to the sub-frame and are exclusive to the PDCCHs.
  • SPS semi-persistent scheduling
  • the processing circuitry may be further configured to, when at least one of the SPS PDSCH transmissions is received in the sub-frame, decode the received SPS PDSCH transmission and map a HARQ-ACK bit for the received SPS PDSCH transmission to the HARQ- ACK bit sequence in a predetermined bit position reserved for the SPS PDSCH transmissions.
  • Example 2 the subject matter of Example 1, wherein the
  • a DCI format of at least a particular PDCCH that schedules a particular PDSCH may include: a total downlink assignment indicator (DAI) field to indicate a size of the HARQ-ACK bit sequence, and a DAI counter field to indicate the bit position of the HARQ-ACK bit sequence to which the HARQ-ACK bit of the particular PDSCH is mapped.
  • DCI Downlink Control Information
  • Example 3 the subject matter of one or any combination of
  • Examples 1-2 wherein the total DAI field may be based on a count that includes PDSCH transmissions, SPS PDSCH transmissions, and PDCCHs that over-ride SPS PDSCH transmissions.
  • the DAI counter field may be based on a count that includes the PDSCH transmissions and the PDCCHs that over-ride SPS PDSCH transmissions and excludes the SPS PDSCH transmissions.
  • Example 4 the subject matter of one or any combination of
  • Examples 1-3 wherein the PDSCH transmissions may be received in multiple component carriers (CCs) in accordance with a carrier aggregation (CA).
  • the CCs of the CA may be mapped to an ordered sequence of CC indexes.
  • the PDCCHs may indicate the CCs on which the PDSCH transmissions are to be received in the sub-frame.
  • the CC on which the particular PDSCH is received may be mapped to a particular CC index.
  • the DAI counter of the particular PDCCH may be based on a count of the PDSCH transmissions received in the sub-frame for which CC indexes are lower than the particular CC index.
  • the DAI counter of the particular PDCCH may be exclusive to a count of the SPS PDSCH transmissions received in the sub-frame.
  • downlink channel resources may comprise multiple component carriers (CCs) in a carrier aggregation (CA).
  • the UE may be configured to simultaneously receive, on each CC of a sub-group of the CCs in the sub-frame: one of the PDCCHs, one of the PDSCH transmissions, one of the SPS PDSCH transmissions, or another PDCCH that indicates an over-ride of one of the SPS PDSCH transmissions scheduled for the CC in the sub-frame.
  • Example 6 the subject matter of one or any combination of
  • a DCI format of at least one of the PDCCHs may include a total downlink assignment indicator (DAI) field that is based on a summation of: a number of the CCs of the sub-group on which one of the PDSCH transmissions is scheduled in the sub-frame by one of the PDCCHs, a number of the CCs of the sub-group on which one of the SPS PDSCH transmissions is scheduled for the sub-frame, and a number of the CCs of the sub-group on which an SPS over-ride PDCCH is to be received in the sub-frame, wherein the SPS over-ride PDCCH indicates an over-ride of a previously scheduled SPS PDSCH transmission previously scheduled for the sub-frame.
  • DAI total downlink assignment indicator
  • Example 7 the subject matter of one or any combination of
  • the DCI format may further include, for a particular PDCCH that schedules a particular PDSCH transmission on a particular CC of a particular CC index, a DAI counter, wherein: the DAI counter includes the CCs of the sub-group on which one of the PDSCH transmissions is scheduled by one of the PDCCHs in the sub-frame, the DAI counter excludes the CCs of the sub-group on which one of the SPS PDSCH transmissions is scheduled in the sub-frame, and the DAI counter includes the CCs of the sub-group on which an over-ride PDCCH is to be received in the sub- frame.
  • Example 8 the subject matter of one or any combination of
  • processing circuitry may be further configured to encode the HARQ-ACK bit sequence for transmission.
  • the HARQ-ACK bits for the PDSCH transmissions may be mapped to bit positions of the HARQ- ACK bit sequence based on values of DAI counter fields of the PDCCHs.
  • Example 9 the subject matter of one or any combination of
  • Examples 1-8 wherein the scheduling of the PDSCH transmissions by the PDCCHs may be configurable for a self-scheduling arrangement or a cross- carrier scheduling arrangement.
  • each PDSCH transmission may be scheduled by a corresponding PDCCH that is received on a same CC as the PDSCH transmission.
  • the PDCCHs may be received on one or more CCs.
  • Example 10 the subject matter of one or any combination of
  • each PDCCH may be scrambled by a UE-specific radio network temporary identifier (RNTI) of the UE, each PDCCH may include a total downlink assignment index (DAI) field that is based on a count of CCs on which one of the PDSCH transmissions is scheduled by one of the PDCCHs included in either the USS or the CSS, and each PDCCH may further include a DAI counter that includes a count of CCs on which one of the PDSCH transmissions is scheduled by one of the PDCCHs included in the USS and excludes a count of CCs on which one of the PDSCH transmissions is scheduled by one of the PDCCHs included in the CSS.
  • each PDCCH may be scrambled by a UE-specific radio network temporary identifier (RNTI) of the UE, each PDCCH may include a total downlink assignment index (DAI) field that is based on a count of CCs on which one of the PDSCH transmissions is scheduled by one of the
  • Example 11 the subject matter of one or any combination of
  • HARQ-ACK bits for the PDSCH transmissions scheduled by the PDCCHs included in the USS may be mapped to the HARQ- ACK bit sequence in bit positions that are based on values of the DAI counter fields of the PDCCHs.
  • HARQ-ACK bits for the PDSCH transmissions scheduled by the PDCCHs included in the CSS may be mapped to the HARQ- ACK bit sequence in bit positions that are reserved for PDSCH transmissions scheduled by the PDCCHs included in the CSS.
  • Example 12 the subject matter of one or any combination of
  • Examples 1- 11, wherein the predetermined bit position reserved for the SPS PDSCH transmissions may be a least significant bit (LSB) or most significant bit (MSB) of the HARQ-ACK bit sequence.
  • LSB least significant bit
  • MSB most significant bit
  • Example 13 the subject matter of one or any combination of
  • the SPS schedules may be pre-established schedules of periodic reception, by the UE, of SPS PDSCH transmissions without corresponding PDCCHs.
  • the determination of whether the SPS PDSCH transmissions are to be received in the sub-frame may be based on one or more comparisons between a time index of the sub-frame and time indexes of the SPS schedules.
  • Example 14 the subject matter of one or any combination of Examples 1-13, wherein the UE may be arranged to operate in accordance with a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) protocol to receive the PDCCHs, PDSCH transmissions, and SPS PDSCH transmission from an Evolved Node-B (eNB).
  • 3GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • Example 15 the subject matter of one or any combination of Examples 1-14, wherein the apparatus may further include a transceiver to receive the PDCCHs, the PDSCH transmissions, and the SPS PDSCH transmission from an Evolved Node-B (eNB).
  • eNB Evolved Node-B
  • Example 16 the subject matter of one or any combination of
  • processing circuitry may include a baseband processor to decode the PDCCHs, the PDSCH transmissions, and the SPS PDSCH transmission.
  • a computer-readable storage medium may store instructions for execution by one or more processors to perform operations for communication by a User Equipment (UE).
  • the operations may configure the one or more processors to decode a plurality of physical downlink shared channel (PDSCH) transmissions received in a sub-frame on a plurality of component carriers (CCs) of a carrier aggregation (CA).
  • the PDSCH transmissions may be scheduled by a plurality of physical downlink control channels (PDCCHs) received in the sub-frame.
  • the operations may further configure the one or more processors to decode a semi-persistent scheduling (SPS) PDSCH transmission received in the sub-frame on one of the CCs.
  • SPS semi-persistent scheduling
  • the SPS PDSCH transmission may be scheduled prior to the sub-frame and exclusively to the PDCCHs.
  • the operations may further configure the one or more processors to encode, for transmission, a hybrid automatic repeat request acknowledgement (HARQ-ACK) bit sequence of HARQ-ACK bits.
  • HARQ-ACK bits for the PDSCH transmissions may be mapped to bit positions of the HARQ-ACK bit sequence in accordance with information included in the PDCCHs.
  • a HARQ-ACK bit of the SPS PDSCH transmission may be mapped to a fixed position of the HARQ-ACK bit sequence reserved for the HARQ- ACK bit of the SPS PDSCH transmission.
  • Example 18 the subject matter of Example 17, wherein the operations may further configure the one or more processors to determine the HARQ-ACK bits for the decoded PDSCH transmissions based on whether the PDSCH transmissions are successfully decoded.
  • the operations may further configure the one or more processors to determine the HARQ-ACK bit for the decoded SPS PDSCH transmission based on whether the SPS PDSCH transmission is successfully decoded.
  • an apparatus of an Evolved Node-B may comprise memory.
  • the apparatus may further comprise processing circuitry.
  • the processing circuitry may be configured to encode, for transmission in a sub- frame: one or more physical downlink shared channel (PDSCH) transmissions, one or more physical downlink control channels (PDCCHs) that include scheduling information for the PDSCH transmissions, and a semi-persistent scheduling (SPS) PDSCH transmission that is scheduled by an SPS schedule configured prior to the sub-frame.
  • the processing circuitry may be further configured to decode a hybrid automatic repeat request acknowledgement (HARQ-ACK) bit sequence of HARQ-ACK bits.
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • the HARQ-ACK bits for the PDSCH transmissions may be mapped to bit positions indicated by the PDCCHs and a HARQ-ACK bit for the SPS-PDSCH transmission may be mapped to a predetermined bit position reserved for the HARQ-ACK bit of the SPS PDSCH transmission.
  • downlink channel resources may comprise multiple component carriers (CCs) for usage in a carrier aggregation (CA).
  • CA carrier aggregation
  • the eNB may be configured to transmit, on each CC of a sub-group of the CCs in the sub-frame: one of the PDSCH transmissions, one of the PDCCHs or the SPS PDSCH transmission.
  • a downlink control information (DCI) format used for at least one of the PDCCHs may include a total downlink assignment indicator (DAI) that is based on a summation of: a number of the CCs of the sub-group on which one of the PDSCH transmissions is scheduled by one of the PDCCHs in the sub-frame, a number of the CCs of the sub-group on which an SPS PDSCH transmission is scheduled for the sub-frame, and a number of the CCs of the sub-group on which an SPS over-ride PDCCH is to be transmitted to indicate an over-ride of an SPS PDSCH transmission previously scheduled in the sub-frame.
  • DCI total downlink assignment indicator
  • Example 21 the subject matter of one or any combination of Examples 19-20, wherein the CCs of the downlink channel resources may be mapped to an ordered sequence of CC indexes.
  • the DCI format may further include, for a particular PDCCH that schedules a particular PDSCH transmission on a particular CC of a particular CC index, a DAI counter.
  • the DAI counter may include the CCs of the sub-group on which one of the PDSCH
  • the DAI counter may exclude the CCs of the sub-group on which an SPS PDSCH transmission is scheduled in the sub-frame.
  • the DAI counter may include the CCs of the sub-group on which an SPS over-ride PDCCH is transmitted.
  • Example 22 the subject matter of one or any combination of Examples 19-21, wherein the apparatus may further include a transceiver to transmit the PDCCHs, the PDSCH transmissions, and the SPS PDSCH transmission.
  • Example 23 the subject matter of one or any combination of
  • processing circuitry may include a baseband processor to encode the PDCCHs, the PDSCH transmissions, and the SPS PDSCH transmission.
  • an apparatus of a User Equipment may comprise means for decoding a plurality of physical downlink shared channel (PDSCH) transmissions received in a sub-frame on a plurality of component carriers (CCs) of a carrier aggregation (CA), the PDSCH transmissions scheduled by a plurality of physical downlink control channels (PDCCHs) received in the sub-frame.
  • the apparatus may further comprise means for decoding a semi-persistent scheduling (SPS) PDSCH transmission received in the sub-frame on one of the CCs, the SPS PDSCH transmission scheduled prior to the sub-frame and exclusively to the PDCCHs.
  • SPS semi-persistent scheduling
  • the apparatus may further comprise means for encoding, for transmission, a hybrid automatic repeat request acknowledgement (HARQ-ACK) bit sequence of HARQ-ACK bits.
  • HARQ-ACK bits for the PDSCH transmissions may be mapped to bit positions of the HARQ-ACK bit sequence in accordance with information included in the PDCCHs.
  • a HARQ-ACK bit of the SPS PDSCH transmission may be mapped to a fixed position of the HARQ-ACK bit sequence reserved for the HARQ- ACK bit of the SPS PDSCH transmission.
  • Example 25 the subject matter of Example 24, wherein the apparatus may further comprise means for determining the HARQ-ACK bits for the decoded PDSCH transmissions based on whether the PDSCH transmissions are successfully decoded.
  • the apparatus may further comprise means for determining the HARQ-ACK bit for the decoded SPS PDSCH transmission based on whether the SPS PDSCH transmission is successfully decoded.

Abstract

La présente invention concerne un Équipement Utilisateur (UE), un Nœud-B évolué (eNB) et des procédés destinés à la communication en conformité avec une opération de demande de répétition automatique hybride (HARQ). Dans une sous-trame, l'UE peut recevoir, à partir d'un eNB sur de multiples porteuses de composant (CCs) d'une agrégation de porteuse (CA), au moins un canal de commande de liaison descendante physique (PDCCHs) et au moins une transmission de canal partagé de liaison descendante physique (PDSCH) organisée par le PDCCHs. L'UE peut recevoir une transmission PDSCH d'organisation semi-persistante (SPS) organisée dans la sous-trame au moyen d'une organisation SPS précédant la sous-trame. Des éléments binaires HARQ-ACK destinés aux transmissions PDSCH peuvent être mappés à des positions d'éléments binaires d'une séquence d'élément binaire HARQ-ACK indiquée par le PDCCHs. Un élément binaire HARQ-ACK destiné à la transmission SPS PDSCH peut être mappé à une position d'élément binaire prédéterminée d'une séquence d'élément binaire HARQ-ACK réservée pour la transmission SPS PDSCH.
PCT/US2016/062042 2016-03-17 2016-11-15 Équipement utilisateur (ue), nœud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) destinés aux aménagements d'agrégation de porteuse WO2017160350A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP16894787.7A EP3430754A4 (fr) 2016-03-17 2016-11-15 Équipement utilisateur (ue), noeud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) destinés aux aménagements d'agrégation de porteuse

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662309819P 2016-03-17 2016-03-17
US62/309,819 2016-03-17

Publications (1)

Publication Number Publication Date
WO2017160350A1 true WO2017160350A1 (fr) 2017-09-21

Family

ID=59850370

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/062042 WO2017160350A1 (fr) 2016-03-17 2016-11-15 Équipement utilisateur (ue), nœud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) destinés aux aménagements d'agrégation de porteuse

Country Status (2)

Country Link
EP (1) EP3430754A4 (fr)
WO (1) WO2017160350A1 (fr)

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019137459A1 (fr) * 2018-01-11 2019-07-18 Mediatek Inc. Réservation de ressources harq-ack dans des informations de commande de liaison montante dans des communications sans fil
CN110149175A (zh) * 2018-02-12 2019-08-20 电信科学技术研究院有限公司 一种资源映射方法及装置
WO2019160483A1 (fr) * 2018-02-15 2019-08-22 Telefonaktiebolaget Lm Ericsson (Publ) Traitement de libération sps pour livre de codes harq-ack dynamique basé sur un groupe de blocs de code
WO2019157950A1 (fr) * 2018-02-13 2019-08-22 电信科学技术研究院有限公司 Procédé de transmission de planification semi-persistante, dispositif côté réseau et terminal utilisateur
WO2020025063A1 (fr) * 2018-08-02 2020-02-06 华为技术有限公司 Procédé et dispositif de communication
CN111226406A (zh) * 2017-10-04 2020-06-02 高通股份有限公司 用于针对半持久调度(sps)的超可靠低延时混合自动重传请求(harq)重传的技术和装置
CN111865511A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 传输混合自动重传请求harq反馈信息的方法和通信装置
WO2020225917A1 (fr) * 2019-05-09 2020-11-12 株式会社Ｎｔｔドコモ Terminal utilisateur et procédé de communication sans fil
CN112219420A (zh) * 2018-04-04 2021-01-12 株式会社Ntt都科摩 用户终端以及无线基站
WO2021022998A1 (fr) * 2019-08-02 2021-02-11 中兴通讯股份有限公司 Procédé et dispositif de comptage de messages, station de base et support de stockage informatique
WO2021026917A1 (fr) * 2019-08-15 2021-02-18 富士通株式会社 Procédé et appareil de transmission de signal, et système
WO2021032001A1 (fr) * 2019-08-16 2021-02-25 维沃移动通信有限公司 Procédé de rétroaction et dispositif terminal pour planification semi-persistante de canal partagé de liaison descendante physique
TWI747355B (zh) * 2019-07-18 2021-11-21 財團法人資訊工業策進會 用於行動通訊系統之使用者裝置及基地台
WO2022078360A1 (fr) * 2020-10-15 2022-04-21 北京紫光展锐通信技术有限公司 Procédé de communication et produit associé
EP3905808A4 (fr) * 2018-12-29 2022-08-10 ZTE Corporation Procédé et appareil de traitement de planification de ressources
EP4030659A4 (fr) * 2019-10-09 2022-09-14 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de communication sans fil, dispositif terminal et dispositif de réseau
EP3920444A4 (fr) * 2019-02-01 2023-01-11 ZTE Corporation Procédé de transmission d'informations d'indice, dispositif, support de stockage et dispositif électronique associés
EP4132180A4 (fr) * 2020-04-10 2023-05-03 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif de configuration de dai, procédé et dispositif d'indication de dai, procédé et dispositif d'envoi de dai, et support
WO2023137703A1 (fr) * 2022-01-21 2023-07-27 Lenovo (Beijing) Limited Procédé et appareil pour des réceptions de multidiffusion sur de multiples porteuses

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120039280A1 (en) * 2010-08-16 2012-02-16 Qualcomm Incorporated Ack/nack transmission for multi-carrier operation with downlink assignment index
US20120320805A1 (en) 2010-09-30 2012-12-20 Lg Electronics Inc. Method and apparatus for transmitting control information
EP2648355A2 (fr) 2010-12-02 2013-10-09 LG Electronics Inc. Procédé et dispositif de transmission de ack/nack dans système de communication sans fil duplex à répartition dans le temps (tdd)
US20160021655A1 (en) * 2012-02-20 2016-01-21 Lg Electronics Inc. Method and device for transmitting ack/nack in carrier aggregating system
EP3319259A1 (fr) 2015-07-01 2018-05-09 LG Electronics Inc. Procédé et appareil pour émettre des signaux dans un système de communication sans fil

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120039280A1 (en) * 2010-08-16 2012-02-16 Qualcomm Incorporated Ack/nack transmission for multi-carrier operation with downlink assignment index
US20120320805A1 (en) 2010-09-30 2012-12-20 Lg Electronics Inc. Method and apparatus for transmitting control information
EP2648355A2 (fr) 2010-12-02 2013-10-09 LG Electronics Inc. Procédé et dispositif de transmission de ack/nack dans système de communication sans fil duplex à répartition dans le temps (tdd)
US20160021655A1 (en) * 2012-02-20 2016-01-21 Lg Electronics Inc. Method and device for transmitting ack/nack in carrier aggregating system
EP3319259A1 (fr) 2015-07-01 2018-05-09 LG Electronics Inc. Procédé et appareil pour émettre des signaux dans un système de communication sans fil

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Corrections on HARQ-ACK transmission for eCA", RI-160289, 3GPP TSG RAN WG1 MEETING #84, 6 February 2016 (2016-02-06), St Julian' s, Malta, pages 6 - 8, XP051053629 *
HUAWEI ET AL.: "Open issues on HARQ-ACK transmission for eCA", RI-160286, 3GPP TSG RAN WG1 MEETING #84, 6 February 2016 (2016-02-06), St Julian' s, Malta, XP051053626 *
SAMSUNG: "Correction on HARQ-ACK Reporting Procedure", RI-160509, 3GPP TSG RAN WG1 MEETING #84, 5 February 2016 (2016-02-05), St Julian' s , Malta, XP051053842 *
See also references of EP3430754A4 *

Cited By (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111226406B (zh) * 2017-10-04 2023-05-26 高通股份有限公司 用于针对半持久调度(sps)的超可靠低延时混合自动重传请求(harq)重传的技术和装置
CN111226406A (zh) * 2017-10-04 2020-06-02 高通股份有限公司 用于针对半持久调度(sps)的超可靠低延时混合自动重传请求(harq)重传的技术和装置
WO2019137459A1 (fr) * 2018-01-11 2019-07-18 Mediatek Inc. Réservation de ressources harq-ack dans des informations de commande de liaison montante dans des communications sans fil
US10790955B2 (en) 2018-01-11 2020-09-29 Mediatek Inc. Reservation of HARQ-ACK resources in uplink control information in wireless communications
CN110149175A (zh) * 2018-02-12 2019-08-20 电信科学技术研究院有限公司 一种资源映射方法及装置
CN110149175B (zh) * 2018-02-12 2022-06-21 大唐移动通信设备有限公司 一种资源映射方法及装置
WO2019157950A1 (fr) * 2018-02-13 2019-08-22 电信科学技术研究院有限公司 Procédé de transmission de planification semi-persistante, dispositif côté réseau et terminal utilisateur
RU2754678C1 (ru) * 2018-02-15 2021-09-06 Телефонактиеболагет Лм Эрикссон (Пабл) Обработка отмены планирования sps для динамической кодовой книги для квитирования запроса повторной передачи (harq-ack) на основе группы кодовых блоков
JP7263372B2 (ja) 2018-02-15 2023-04-24 テレフオンアクチーボラゲット エルエム エリクソン（パブル） コードブロックグループベースの動的ｈａｒｑ－ａｃｋコードブックに対するｓｐｓ解放処理
WO2019160483A1 (fr) * 2018-02-15 2019-08-22 Telefonaktiebolaget Lm Ericsson (Publ) Traitement de libération sps pour livre de codes harq-ack dynamique basé sur un groupe de blocs de code
JP2021536147A (ja) * 2018-02-15 2021-12-23 テレフオンアクチーボラゲット エルエム エリクソン（パブル） コードブロックグループベースの動的ｈａｒｑ−ａｃｋコードブックに対するｓｐｓ解放処理
CN112219420B (zh) * 2018-04-04 2024-03-26 株式会社Ntt都科摩 终端、无线通信方法、基站以及系统
CN112219420A (zh) * 2018-04-04 2021-01-12 株式会社Ntt都科摩 用户终端以及无线基站
US11902943B2 (en) 2018-08-02 2024-02-13 Huawei Technologies Co., Ltd. Communication method and communications apparatus
WO2020025063A1 (fr) * 2018-08-02 2020-02-06 华为技术有限公司 Procédé et dispositif de communication
EP3905808A4 (fr) * 2018-12-29 2022-08-10 ZTE Corporation Procédé et appareil de traitement de planification de ressources
EP3920444A4 (fr) * 2019-02-01 2023-01-11 ZTE Corporation Procédé de transmission d'informations d'indice, dispositif, support de stockage et dispositif électronique associés
WO2020221271A1 (fr) * 2019-04-30 2020-11-05 华为技术有限公司 Procédé de transmission d'informations de renvoi de demande de répétition automatique hybride (harq) et appareil de communication
CN111865511A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 传输混合自动重传请求harq反馈信息的方法和通信装置
CN111865511B (zh) * 2019-04-30 2022-01-11 华为技术有限公司 传输混合自动重传请求harq反馈信息的方法和通信装置
WO2020225917A1 (fr) * 2019-05-09 2020-11-12 株式会社Ｎｔｔドコモ Terminal utilisateur et procédé de communication sans fil
CN114041316A (zh) * 2019-05-09 2022-02-11 株式会社Ntt都科摩 用户终端以及无线通信方法
JP7269331B2 (ja) 2019-05-09 2023-05-08 株式会社Ｎｔｔドコモ 端末、無線通信方法、基地局及びシステム
JPWO2020225917A1 (fr) * 2019-05-09 2020-11-12
CN114041316B (zh) * 2019-05-09 2023-08-15 株式会社Ntt都科摩 用户终端以及无线通信方法
TWI747355B (zh) * 2019-07-18 2021-11-21 財團法人資訊工業策進會 用於行動通訊系統之使用者裝置及基地台
US11777657B2 (en) 2019-07-18 2023-10-03 Institute For Information Industry User equipment and base station for mobile communication system
WO2021022998A1 (fr) * 2019-08-02 2021-02-11 中兴通讯股份有限公司 Procédé et dispositif de comptage de messages, station de base et support de stockage informatique
CN115276918A (zh) * 2019-08-02 2022-11-01 中兴通讯股份有限公司 信息计数方法、装置和计算机存储介质
CN115276918B (zh) * 2019-08-02 2024-04-26 中兴通讯股份有限公司 信息计数方法、装置和计算机存储介质
WO2021026917A1 (fr) * 2019-08-15 2021-02-18 富士通株式会社 Procédé et appareil de transmission de signal, et système
WO2021032001A1 (fr) * 2019-08-16 2021-02-25 维沃移动通信有限公司 Procédé de rétroaction et dispositif terminal pour planification semi-persistante de canal partagé de liaison descendante physique
EP4030659A4 (fr) * 2019-10-09 2022-09-14 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de communication sans fil, dispositif terminal et dispositif de réseau
EP4132180A4 (fr) * 2020-04-10 2023-05-03 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif de configuration de dai, procédé et dispositif d'indication de dai, procédé et dispositif d'envoi de dai, et support
WO2022078360A1 (fr) * 2020-10-15 2022-04-21 北京紫光展锐通信技术有限公司 Procédé de communication et produit associé
WO2023137703A1 (fr) * 2022-01-21 2023-07-27 Lenovo (Beijing) Limited Procédé et appareil pour des réceptions de multidiffusion sur de multiples porteuses

Also Published As

Publication number Publication date
EP3430754A4 (fr) 2019-11-20
EP3430754A1 (fr) 2019-01-23

Similar Documents

Publication Publication Date Title
US11122580B2 (en) Evolved node-b (ENB), user equipment (UE) and methods for flexible duplex communication
US20200213982A1 (en) Physical downlink control channel for fifth-generation networks
US11737171B2 (en) 5G FDD low latency transmission subframe structure system and method of use
EP3430754A1 (fr) Équipement utilisateur (ue), noeud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) destinés aux aménagements d'agrégation de porteuse
US11265053B2 (en) User equipment (UE) and methods for communication using directional transmission and reception
US10581537B2 (en) Devices and methods for robust measurement and data receiving
US20190335536A1 (en) User equipment (ue), evolved node-b (enb) and methods for dynamic hybrid automatic repeat request (harq)
US20190372736A1 (en) User equipment and methods for physical uplink control channel (pucch) resource allocation and communication
EP3178281B1 (fr) Équipement d'utilisateur et procédés d'allocation et de signalisation de ressources de temps pour les communications de dispositif à dispositif (d2d)
US10560174B2 (en) Latency reduction for wireless data transmission
US20190191453A1 (en) User equipment (ue), evolved node-b (enb) and methods for multiplexing new radio (nr) physical uplink shared channel (nr pusch) and nr physical uplink control channel (nr pucch)
WO2018085044A1 (fr) Équipement utilisateur (ue), nœud-b évolué (enb) et procédés de signalisation d'attributions de canal de commande de liaison montante physique (pucch) de nouvelle radio (nr)
EP3311516B1 (fr) Réduction de collision entre ressources de liaison montante dans un système fd-mimo
EP3453131B1 (fr) Équipement d'utilisateur (ue) et procédés de réception de paquets sur un support radio divisé

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16894787

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2016894787

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016894787

Country of ref document: EP

Effective date: 20181017