EP3420657A1 - Physical uplink control channel formats for 5g - Google Patents

Abstract

Embodiments of 5G physical uplink control channel (xPUCCH) are generally described herein. A user equipment (UE) includes processing circuitry and memory. The processing circuitry determines uplink control informal ion for xPUCCH. The processing circuitry facilitates a transmission of the xPUCCH to carry the determined uplink control informal ion to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information.

Description

PHYSICAL UPLINK CONTROL CHANNEL FORMATS FOR 5G PRIORITY CLAIM

[0001] This application claims priority under 35 U.S.C. § 119 to United

States Provisional Patent Application Serial No. 62/299,458, filed February 24, 2016, and titled, "PHYSICAL UPLINK CONTROL CHANNEL FORMATS FOR 5G," which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications. Some embodiments relate to physical uplink control channel (PUCCH) formats and radio access network layer 1 (RANI) in fifth generation (5G) systems.

BACKGROUND [0003] In a cellular network, a user equipment (UE) needs to communicate with an evolved NodeB (eNB), for example, to provide uplink control information (UCI). The UE transmits UCI to the eNB using physical uplink control channel (PUCCH). [0004] Thus, there are general needs for systems and methods for

PUCCH transmission in a cellular network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIGS. 1 A-1B are block diagrams of time-division duplex (TDD) subframe structures in the downlink (DL) in accordance with some

embodiments. [0006] FIG. 2 is a functional diagram of a wireless network in accordance with some embodiments.

[0007] FIG. 3 illustrates components of a communication device in accordance with some embodiments.

[0008] FIG. 4 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. S illustrates another block diagram of a communication device in accordance with some embodiments.

[0010] FIG. 6 is a flow chart of an example method for facilitating a transmission of 5G physical uplink control channel.

DETAILED DESCRIPTION

[0011] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0012] Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platform. The fifth generation (5G) wireless communication network system provides, among other things, access to information and sharing of data at many different locations and times, by various users and applications. SG network systems are designed to meet the needs of vastly different and sometimes conflicting performance dimensions and services. These needs are driven by different services or applications that users require of 5G network systems. In general and with some exceptions, 5G evolves from third generation partnership project (3 GPP) long-term evolution (LTE) and adds new radio access technologies (RATs) to 3 GPP LTE.

[0013] FIGS. 1 A-1B are block diagrams of time-division duplex (TDD) subframe structures 100 A and 100B in the downlink (DL) in accordance with some embodiments. Subframe structure 100A of FIG. 1 A is a low latency structure, and subframe structure 100B of FIG. IB is a high throughput structure.

[0014] As shown in FIG. 1A, subframe structure 100 A includes 5G physical downlink control channel (xPDCCH) 11 OA, 5G physical downlink shared channel (xPDSCH) 120A, guard time (GT) 130A, and 5G physical uplink control channel (xPUCCH) 140A. The blocks 110A, 120A, 130A, and 140A are within a single subframe 150 A. As shown in FIG. IB, subframe structure 100B includes, similarly to subframe structure 100 A, xPDCCH HOB, xPDSCH 120B, GT 130B, and xPUCCH 140B. Unlike subframe structure 11 OA, in subframe structure 100B, the blocks 110A, 120A, 130A, and 140A are divided between two subframes 150B-1 and 150B-2. Subframe 150B-1 includes xPDCCH HOB and part of xPDSCH 120B. Subframe 150B-2 includes the remaining part of xPDSCH 120B, GT 130B, and xPUCCH 140B.

[0015] To enable low latency transmission for enhanced mobile broadband communication, a self-contained TDD subframe 150A, as shown in FIG. 1A, can be introduced. FIGS. 1 A-1B illustrate two types of self-contained TDD subframe structures 100A/100B in the DL. For these subframe structures 100A/100B, xPDSCH 120A/120B is scheduled by xPDCCH 1 lOA/110B and is transmitted right after the xPDCCH 1 lOA/110B. The GT 130A/130B either is or is not inserted between xPDSCH 120A/120B and xPUCCH 140A/140B in order to accommodate the DL to uplink (UL) and UL to DL switching time and round- trip propagation delay.

[0016] In order to improve the data rate, two or more subframes 150B-1 and 150B-2 can be aggregated for one xPDSCH 120B transmission for a user equipment (UE) (e.g., as discussed in conjunction with FIG. 2). As shown in FIG. IB, in the high throughput structure 100B, the xPDSCH 120B spans two subframes 150B-1 and 150B-2. The GT 130B is inserted in the second subframe 150B-2. In this case, GT overhead can be reduced by half compared to the low latency structure 100 A of FIG. 1A. In some cases, additional xPDCCH (in addition to xPDCCH 110B) is inserted into the subframe 150B-2 to allow the same subframe scheduling for the DL data channel transmission. As shown in FIG. IB, the subframe structure 100B spans two subframes 150B-1 and 150B-2. However, in some cases, the subframe structure 100B spans more than two subframes, with the xPDSCH 120B expanding across the additional subframes.

[0017] According to some examples, in LTE, PUCCH is transmitted in a frequency region on the edges of the system bandwidth. Further, PUCCH and physical uplink shared channel (PUSCH) are multiplexed in a frequency division multiplexing (FDM) manner. However, as depicted in FIGS. 1 A-1B, xPUCCH 1 lOA/110B and data channel are multiplexed in a time division multiplexing (TDM) manner. In the case when uplink control information (UCI) includes hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, or channel state information (CSI) reports (e.g., channel quality indicator (CQI), pre-coding matrix indicator (ΡΜΓ), and rank indicator (RI)), depending on different payload sizes, different xPUCCH formats are defined. In some embodiments, the subject technology proposes detailed xPUCCH formats to carry UCI with various payload sizes.

[0018] As mentioned above, xPUCCH is used to carry uplink control information, which may include scheduling request, HARQ ACK/NACK feedback, CSI report and beam related information. Depending on payload size, various xPUCCH formats can be defined.

[0019] In one example, xPUCCH format 1/la/lb is used to carry scheduling request and 1 or 2 bit HARQ ACK/NACK feedback.

[0020] In one example, xPUCCH format 2 is used to carry scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI report and/or beam related information. The payload size is between 3 and 13 bits.

[0021] In one example, xPUCCH format 3 is used to carry scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI report and/or beam related information. The payload size is between 3 and 22 bits.

[0022] In one example, xPUCCH format 4 is used to carry scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI report and/or beam related information. The payload size is greater than 22 bits.

[0023] In some embodiments, one physical resource block group (RBG) correspond to six physical resource blocks (PRB), which is a minimum resource unit for xPUCCH transmission. In this case, the e Node B (eNB) may schedule the UE to transmit the xPUCCH using one or multiple RBGs according to the indication in the downlink control information (DO). (See the discussion of FIG. 2 for details of operation of the UE and eNB.)

[0024] The physical uplink control channel, xPUCCH, carries uplink control information. In some cases, the xPUCCH is transmitted in the last symbol of a subframe. All xPUCCH formats use a cyclic shift, n*"(«_s) , which varies with the slot number n_s according to Equation 1.

[0025] In Equation 1, is a cell specific cyclic shift value; is the number of symbols in one slot; n_s is the slot number within one frame. For 5G, n_s can be ranged from 0 to 99. In Equation 1, c(i) is a pseudo-random sequence. The pseudo-random sequence generator is initialized with The

physical uplink control channel supports multiple formats as shown in Table 1.

[0026] In Table 1, the modulation scheme QPSK refers to quadrature phase-shift keying, and the modulation scheme BPSK refers to binary phase- shift keying.

[0027] In some cases, xPUCCH format 1/la/lb is used to carry scheduling request and 1 or 2 bit HARQ ACK/NACK feedback. The detailed design for xPUCCH format 1/la/lb is provided below.

[0028] In one embodiment, within one xPUCCH resource, multiple UEs can be multiplexed in a code division multiplexing (CDM) manner. Further, in the case when UE is configured with two antenna ports, Zadoff-Chu (ZC) sequence with different cyclic shift values on each AP is applied to achieve transmit diversity. [0029] Further, in order to randomize inter-cell interference, cell specific and UE specific cyclic shift values are applied for ZC sequence, where UE specific cyclic shift value can be configured by higher layers via RRC signalling or indicated in the DCI via xPDCCH.

[0030] For xPUCCH format 1, information is carried by the

presence/absence of transmission of xPUCCH from the UE. In some cases, = 1 for xPUCCH format 1.

[0031] For xPUCCH formats la and lb, one or two explicit bits are transmitted, respectively. The block of bits are modulated as

described in Table 1, resulting in a complex-valued symbol The modulation schemes for the different xPUCCH formats are given by Table 2.

[0032] The complex-valued symbol is multiplied with a cyclically shifted length sequence for each of the antenna ports

used for PUCCH transmission according to Equation 2. q

[0033] In Equation is the modulated symbols; ^p is the

number of antenna ports; ? is the antenna port index; d(0) is the input symbol;

In Equation is defined with The antenna-port specific cyclic

<x~

shift ^p varies between slots as defined in Equation 3. [0034]

one frame; ? is the antenna port index; is the number of antenna ports; is the number of subcarriers in one resource block (RB). In Equation 3,

" is configured by higher layers. The block of complex-

valued symbols y is mapped to z according to Equation 4. q

[0035] In Equation is the number of RBs for one xPUCCH

transmission; is the transmitted data mapped to the corresponding xPUCCH resource; is the modulated symbols for xPUCCH; k is the modulated symbol index. In Equation 4:

[0036] Resources used for transmission of PUCCH format 1, 1a, and lb

q

[0037] In another embodiment, multiple UEs are multiplexed in a frequency division multiplexing (FDM) manner using assigned RBGs. [0038] For xPUCCH format 1, information is carried by the

presence/absence of transmission of xPUCCH from the UE. In some cases, d(0) = 1 is assumed for xPUCCH format 1.

[0039] For xPUCCH formats la and lb, one or two explicit bits are transmitted, respectively. The block of shall be modulated

as described in Table 5.4.1-1, resulting in a complex-valued symbol d(0) . The modulation schemes for the different xPUCCH formats are given by Table 3.

[0040] The complex-valued symbol is multiplied with a cyclically shifted length for each of the ^p antenna ports used for xPUCCH transmission according to Equation 6.

quation 6

[0041] In Equation 6, is the modulated symbols; is the number

of antenna ports; ? is the antenna port index; d(0) is the input symbol.

Furthermore, in Equation is defined with The antenna-

port specific cyclic shift is defined by Equation 7.

[0042] In Equation 7, is the cyclic shift; n_s is the slot number within one frame; is the antenna port index; is the number of antenna ports; is the number of subcarriers in one resource block (RB). Furthermore, in

Equation is configured by higher layers. The

block of complex-valued symbols y is mapped to∑ according to Equation 8. q

[0043] In Equation 8, i s the number of RBs for one xPUCCH transmission; is the transmitted data mapped to the corresponding xPUCCH resource; is the modulated symbols for xPUCCH; k is the modulated

symbol index. In Equation 8:

[0044] Resources used for transmission of xPUCCH format 1, 1a and lb are identified by a resource index which is configured by higher layers.

[0045] Below, xPUCCH formats 2, 3, and 4 are discussed.

[0046] As mentioned above, xPUCCH format 2 and 3 can be used to carry scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI report and/or beam related information. xPUCCH format 2 can be used to carry uplink control information with payload size between 3 and 13 bits; xPUCCH format 3 can be used to carry uplink control information with payload size between 3 and 22 bits; xPUCCH format 4 can be used to carry uplink control information with payload size greater than 22 bits.

[0047] In one embodiment, space frequency block code (SFBC) is applied for xPUCCH format 2, 3 and 4 in the case when two APs are configured for UE. Further, cell specific cyclic shift can be applied for the xPUCCH transmission in order to randomize the inter-cell interference.

[0048] More specifically, The block of bits shall be scrambled with a UE-specific scrambling sequence, resulting in a block of scrambled bits according to Equation 9.

[0049] In Equation is the scrambling sequence. The scrambling

sequence generator is initialized with Equation 10 at the start of each subframe.

[0050] In Equation 10, is the slot number within one frame; is the physical cell is the Cell Radio Network Temporary Identifier (C-

RNTI). The block of scrambled bits is Quadrature Phase Shift Keying (QPSK) modulated, resulting in a block of complex-valued modulation symbols

[0051] The complex-valued modulation symbols to be transmitted are mapped onto one or two layers. Complex-valued modulation symbols are mapped on to the layers

where " is the number of layers and is the number of

modulation symbols per layer.

[0052] For transmission on a single antenna port, a single layer is used, and the mapping is defined by: x with A , . For

transmission on two antenna ports and the mapping rule of , Equation 11

applies with

[0053] In some cases, precoding is used. The precoder takes as input a block of vectors from the layer mapping and generates a block of vectors to be

mapped onto resource elements. [0054] For transmission on a single antenna port, preceding is defined by

Equation 12.

transmission; is the transmitted data mapped to the corresponding

resource; is the modulated symbols for xPUCCH; k is the modulated symbol index. In Equation 14: [0060]

xPDCCH.

[0062] In another embodiment, per-resource element (RE) cyclic transmission mode are applied for xPUCCH format 2, 3 and 4 in the case where two APs are configured for UE.

[0063] In xPUCCH formats 3 and 4, the block of bits 6

are scrambled with a UE-specific scrambling sequence, resulting in a block of scrambled bits according to is

the scrambling sequence. The scrambling sequence generator is initialized with a^t the start of each subframe, where is the cell-radio network temporary identifier (C-RNTI). The block of scrambled bits is quadrature phase-shift keying (QPSK) modulated,

resulting in a block of complex-valued modulation symbols

where

[0064] Layer mapping is sometimes applied. The complex-valued modulation symbols to be transmitted are mapped onto one or two layers.

Complex-valued modulation symbols be mapped on to the is the number of

layers and is the number of modulation symbols per layer.

[0065] For transmission on a single antenna port, a single layer is used, and the mapping is defined by . For transmission on two antenna ports, and the mapping rule of υ = 2 can be defined by

[0072] In Equation 18, is the number of RBs for one xPUCCH

transmission; is the transmitted data mapped to the corresponding xPUCCH resource; is the modulated symbols for xPUCCH; k is the modulated

symbol index. In Equation 18:

[0073] Resources used for transmission of PUCCH format 2 are identified by a resource index fom which the PRB group index and the comb index are determined according to Equation 19.

[0074] In accordance with Equation 19, for xPUCCH format 2,

and which is configured by higher layers.

[0075] FIG. 2 shows an example of a portion of an end-to-end network architecture of a Long Term Evolution (LTE) network 200 with various components of the network in accordance with some embodiments. As used herein, an LTE network refers to both LTE and LTE Advanced (LTE- A) networks as well as other versions of LTE networks to be developed. The network 200 may comprise a radio access network (RAN) (e.g., as depicted, the E-UTRAN or evolved universal terrestrial radio access network) 201 and core network 220 (e.g., shown as an evolved packet core (EPC)) coupled together through an SI interface 215. For convenience and brevity, only a portion of the core network 220, as well as the RAN 201, is shown in the example. The network 200 includes the UE 202, which is configured to determine uplink control information for xPUCCH; and encode a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information. The network 200 includes eNBs 204. One or more of the eNBs 204 is configured to access xPUCCH from multiple user equipments (UEs), including a UE with two antenna ports; and multiplex the accessed xPUCCH, wherein, for the UE configured with the two antenna ports, a ZC sequence with a different cyclic shift value is applied on the xPUCCH received from each antenna port. In some examples, the UE 202 transmits xPUCCH to the eNB 204, which receives the xPUCCH from the UE 202.

[0076] The core network 220 may include a mobility management entity

(MME) 222, serving gateway (serving GW) 224, and packet data network gateway (PDN GW) 226. The RAN 201 may include evolved node Bs (eNBs) 204 (which may operate as base stations) for communicating with user equipment (UE) 202. The eNBs 204 may include macro eNBs 204a and low power (LP) eNBs 204b.

[0077] The MME 222 may be similar in function to the control plane of legacy Serving GPRS Support Nodes (SGSN). The MME 222 may manage mobility aspects in access such as gateway selection and tracking area list management. The serving GW 224 may terminate the interface toward the RAN 201, and route data packets between the RAN 201 and the core network 220. In addition, the serving GW 224 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 224 and the MME 222 may be implemented in one physical node or separate physical nodes.

[0078] The PDN GW 226 may terminate a SGi interface toward the packet data network (PDN). The PDN GW 226 may route data packets between the EPC 220 and the external PDN, and may perform policy enforcement and charging data collection. The PDN GW 226 may also provide an anchor point for mobility devices with non-LTE access. The external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domain. The PDN GW 226 and the serving GW 224 may be implemented in a single physical node or separate physical nodes. [0079] The eNBs 204 (macro and micro) may terminate the air interface protocol and may be the first point of contact for a UE 202. In some

embodiments, an eNB 204 may fulfill various logical functions for the RAN 201 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. In accordance with embodiments, UEs 202 may be configured to communicate orthogonal frequency division multiplexed (OFDM) communication signals with an eNB 204 over a multicarrier communication channel in accordance with an OFDMA communication technique. The OFDM signals may comprise a plurality of orthogonal subcarriers.

[0080] The S 1 interface 215 may be the interface that separates the RAN

201 and the EPC 220. It may be split into two parts: the Sl-U, which may carry traffic data between the eNBs 204 and the serving GW 224, and the SI -MME, which may be a signaling interface between the eNBs 204 and the MME 222. The X2 interface may be the interface between eNBs 204. The X2 interface may comprise two parts, the X2-C and X2-U. The X2-C may be the control plane interface between the eNBs 204, while the X2-U may be the user plane interface between the eNBs 204.

[0081] With cellular networks, LP cells 204b may be typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with dense usage. In particular, it may be desirable to enhance the coverage of a wireless communication system using cells of different sizes, macrocells, microcells, picocells, and femtocells, to boost system performance. The cells of different sizes may operate on the same frequency band, or may operate on different frequency bands with each cell operating in a different frequency band or only cells of different sizes operating on different frequency bands. As used herein, the term LP eNB refers to any suitable relatively LP eNB for implementing a smaller cell (smaller than a macro cell) such as a femtocell, a picocell, or a microcell. Femtocell eNBs may be typically provided by a mobile network operator to its residential or enterprise customers. A femtocell may be typically the size of a residential gateway or smaller and generally connect to a broadband line. The femtocell may connect to the mobile operator's mobile network and provide extra coverage in a range of typically 30 to 50 meters. Thus, a LP eNB 204b might be a femtocell eNB since it is coupled through the PDN GW 226. Similarly, a picocell may be 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 may generally connect through the X2 link to another eNB such as a macro eNB through its base station controller (BSC) functionality. Thus, LP eNB may be implemented with a picocell eNB since it may be coupled to a macro eNB 204a via an X2 interface. Picocell eNBs or other LP eNBs LP eNB 204b may incorporate some or all functionality of a macro eNB LP eNB 204a. In some cases, this may be referred to as an access point base station or enterprise femtocell.

[0082] In some embodiments, the UE 202 may communicate with an access point (AP) 204c. The AP 204c may use only the unlicensed spectrum (e.g., WiFi bands) to communicate with the UE 202. The AP 204c may communicate with the macro eNB 204A (or LP eNB 204B) through an Xw interface. In some embodiments, the AP 204c may communicate with the UE 202 independent of communication between the UE 202 and the macro eNB 204A. In other embodiments, the AP 204c may be controlled by the macro eNB 204A and use LWA, as described in more detail below.

[0083] Communication over an LTE network may be split up into 10ms frames, each of which may contain ten 1ms subframes. Each sub frame of the frame, in turn, may contain two slots of 0.5ms. Each subframe may be used for uplink (UL) communications from the UE to the eNB or downlink (DL) communications from the eNB to the UE. In one embodiment, the eNB may allocate a greater number of DL communications than UL communications in a particular frame. The eNB may schedule transmissions over a variety of frequency bands (fi and fz). The allocation of resources in subframes used in one frequency band and may differ from those in another frequency band. Each slot of the subframe may contain 6-7 OFDM symbols, depending on the system used. In one embodiment, the subframe may contain 12 subcarriers. A downlink resource grid may be used for downlink transmissions from an eNB to a UE, while an uplink resource grid may be used for uplink transmissions from a UE to an eNB or from a UE to another UE. The resource grid may be a time-frequency grid, which is the physical resource in the downlink in each slot. The smallest time-frequency unit in a resource grid may be denoted as a resource element (RE). Each column and each row of the resource grid may correspond to one OFDM symbol and one OFDM subcarrier, respectively. The resource grid may contain resource blocks (RBs) that describe the mapping of physical channels to resource elements and physical RBs (PRBs). A PRB may be the smallest unit of resources that can be allocated to a UE. A resource block may be 180 kHz wide in frequency and 1 slot long in time. In frequency, resource blocks may be either 12 x 15 kHz subcarriers or 24 x 7.5 kHz subcarriers wide. For most channels and signals, 12 subcarriers may be used per resource block, dependent on the system bandwidth. In Frequency Division Duplexed (FDD) mode, both the uplink and downlink frames may be 10ms and frequency (full-duplex) or time (half-duplex) separated. In Time Division Duplexed (TDD), the uplink and downlink subframes may be transmitted on the same frequency and are multiplexed in the time domain. The duration of the resource grid 400 in the time domain corresponds to one subframe or two resource blocks. Each resource grid may comprise 12 (subcarriers) *14 (symbols) =168 resource elements.

[0084] Each OFDM symbol may contain a cyclic prefix (CP) which may be used to effectively eliminate Inter Symbol Interference (ISI), and a Fast

Fourier Transform (FFT) period. The duration of the CP may be determined by the highest anticipated degree of delay spread. Although distortion from the preceding OFDM symbol may exist within the CP, with a CP of sufficient duration, preceding OFDM symbols do not enter the FFT period. Once the FFT period signal is received and digitized, the receiver may ignore the signal in the CP.

[0085] There may be several different physical downlink channels that are conveyed using such resource blocks, including the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). Each subframe may be partitioned into the PDCCH and the PDSCH. The PDCCH may normally occupy the first two symbols of each subframe and carries, among other things, information about the transport format and resource allocations related to the PDSCH channel, as well as H-ARQ information related to the uplink shared channel. The PDSCH may carry user data and higher layer signaling to a UE and occupy the remainder of the subframe. Typically, downlink scheduling (assigning control and shared channel resource blocks to UEs within a cell) may be performed at the eNB based on channel quality information provided from the UEs to the eNB, and then the downlink resource assignment information may be sent to each UE on the PDCCH used for (assigned to) the UE. The PDCCH may contain downlink control information (DCI) in one of a number of formats that indicate to the UE how to find and decode data, transmitted on PDSCH in the same subframe, from the resource grid. The DCI format may provide details such as number of resource blocks, resource allocation type, modulation scheme, transport block, redundancy version, coding rate etc. Each DCI format may have a cyclic redundancy code (CRC) and be scrambled with a Radio Network Temporary Identifier (RNTI) that identifies the target UE for which the PDSCH is intended. Use of the UE- specific RNTI may limit decoding of the DCI format (and hence the

corresponding PDSCH) to only the intended UE.

[0086] Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. FIG. 3 illustrates components of a UE in accordance with some embodiments. At least some of the components shown may be used in an eNB or MME, for example, such as the UE 202 or eNB 204 shown in FIG. 2. The UE 300 and other components may be configured to use the synchronization signals as described herein. The UE 300 may be one of the UEs 302 shown in FIG. 1 and may be a stationary, non-mobile device or may be a mobile device. In some embodiments, the UE 300 may include application circuitry 302, baseband circuitry 304, Radio Frequency (RF) circuitry 306, front-end module (FEM) circuitry 308 and one or more antennas 310, coupled together at least as shown. At least some of the baseband circuitry 304, RF circuitry 306, and FEM circuitry 308 may form a transceiver. In some embodiments, other network elements, such as the eNB may contain some or all of the components shown in FIG. 3. Other of the network elements, such as the MME, may contain an interface, such as the SI interface, to communicate with the eNB over a wired connection regarding the UE. [0087] The application or processing circuitry 302 may include one or more application processors. For example, the application circuitry 302 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, application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[0088] The baseband circuitry 304 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 304 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 306 and to generate baseband signals for a transmit signal path of the RF circuitry 306. Baseband processing circuity 304 may interface with the application circuitry 302 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 306. For example, in some embodiments, the baseband circuitry 304 may include a second generation (2G) baseband processor 304a, third generation (3G) baseband processor 304b, fourth generation (4G) baseband processor 304c, and/or other baseband processor(s) 304d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 304 (e.g., one or more of baseband processors 304a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 306. The radio control functions may include, but are not limited to, signal modulation/demodulation,

encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 304 may include FFT, precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 304 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other

embodiments.

[0089] In some embodiments, the baseband circuitry 304 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (E-UTRAN) 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. A central processing unit (CPU) 304e of the baseband circuitry 304 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processors) (DSP) 304f. The audio DSP(s) 304f may be include elements for

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

[0090] In some embodiments, the baseband circuitry 304 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 304 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network

(WPAN). Embodiments in which the baseband circuitry 304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. In some embodiments, the device can be configured to operate in accordance with communication standards or other protocols or standards, including Institute of Electrical and Electronic Engineers (IEEE) 802.16 wireless technology (WiMax), IEEE 802.11 wireless technology (WiFi) including IEEE 802.11 ad, which operates in the 60 GHz millimeter wave spectrum, various other wireless technologies such as global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE radio access network (GERAN), universal mobile telecommunications system (UMTS), UMTS terrestrial radio access network (UTRAN), or other 2G, 3G, 4G, 5G, etc. technologies either already developed or to be developed.

[0091] RF circuitry 306 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 306 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 306 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 308 and provide baseband signals to the baseband circuitry 304. RF circuitry 306 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 304 and provide RF output signals to the FEM circuitry 308 for transmission.

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

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

[0094] In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for quadrature downcon version and/or upconversion respectively. In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for image rej ection (e.g.,

Hartley image rejection). In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may be configured for super-heterodyne operation.

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

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

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

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

[0099] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 304 or the applications processor 302 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by the applications processor 302.

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

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

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

[00103] In some embodiments, the FEM circuitry 308 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 306). The transmit signal path of the FEM circuitry 308 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 306), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 310.

[00104] In some embodiments, the UE 300 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface as described in more detail below. In some embodiments, the UE 300 described herein may be part of 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 medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly. In some embodiments, the UE 300 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. For example, the UE 300 may include one or more of a keyboard, a keypad, a touchpad, a display, a sensor, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, one or more antennas, a graphics processor, an application processor, a speaker, a microphone, and other I/O components. The display may be an LCD or LED screen including a touch screen. The sensor may include a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.

[00105] The antennas 310 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. In some multiple-input multiple-output (MIMO) embodiments, the antennas 310 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[00106] Although the UE 300 is 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. For example, 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. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[00107] 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). For example, a computer-readable storage device may include read- only 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.

[00108] FIG. 4 is a block diagram of a communication device in accordance with some embodiments. The device may be a UE or eNB, for example, such as the UE 202 or eNB 204 shown in FIG. 2. The physical layer circuitry 402 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals. The communication device 400 may also include medium access control layer (MAC) circuitry 404 for controlling access to the wireless medium. The communication device 400 may also include processing circuitry 406, such as one or more single-core or multi-core processors, and memory 408 arranged to perform the operations described herein. The physical layer circuitry 402, MAC circuitry 404 and processing circuitry 406 may handle various radio control functions that enable communication with one or more radio networks compatible with one or more radio technologies. The radio control functions may include signal modulation, encoding, decoding, radio frequency shifting, etc. For example, similar to the device shown in FIG. 2, in some embodiments, communication may be enabled with one or more of a WMAN, a WLAN, and a WPAN. In some embodiments, the communication device 400 can be configured to operate in accordance with 3GPP standards or other protocols or standards, including WiMax, WiFi, WiGig, GSM, EDGE, GERAN, UMTS, UTRAN, or other 3G, 3G, 4G, 5G, etc. technologies either already developed or to be developed. The communication device 400 may include transceiver circuitry 412 to enable communication with other external devices wirelessly and interfaces 414 to enable wired communication with other external devices. As another example, the transceiver circuitry 412 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range.

[00109] The antennas 401 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. In some MIMO embodiments, the antennas 401 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[00110] Although the communication device 400 is 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 DSPs, and/or other hardware elements. For example, some elements may comprise one or more

microprocessors, DSPs, FPGAs, ASICs, RFICs and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, 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.

[00111] FIG. S illustrates another block diagram of a communication device 500 in accordance with some embodiments. The communication device 500 may correspond to the UE 202 or the eNB 204. In alternative embodiments, the communication device 500 may operate as a standalone device or may be connected (e.g., networked) to other communication devices. In a networked deployment, the communication device 500 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments. In an example, the communication device 500 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment. The communication device 500 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single communication device is illustrated, the term "communication device" shall also be taken to include any collection of communication devices 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.

[00112] 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. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or 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. In an example, the software may reside on a communication device readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[00113] Accordingly, the term "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. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where 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.

[00114] Communication device (e.g., computer system) 500 may include a hardware processor 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 504 and a static memory 506, some or all of which may communicate with each other via an interlink (e.g., bus) 508. The

communication device 500 may further include a display unit 510, an alphanumeric input device 512 (e.g., a keyboard), and a user interface (UI) navigation device 514 (e.g., a mouse). In an example, the display unit 510, input device 512 and UI navigation device 514 may be a touch screen display. The communication device 500 may additionally include a storage device (e.g., drive unit) 516, a signal generation device 518 (e.g., a speaker), a network interface device 520, and one or more sensors 521, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 500 may include an output controller 528, 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.).

[0011S] The storage device 516 may include a communication device readable medium 522 on which is stored one or more sets of data structures or instructions 524 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 524 may also reside, completely or at least partially, within the main memory 504, within static memory 506, or within the hardware processor 502 during execution thereof by the communication device 500. In an example, one or any combination of the hardware processor 502, the main memory 504, the static memory 506, or the storage device 516 may constitute communication device readable media.

[00116] While the communication device readable medium 522 is illustrated as a single medium, the term "communication device 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 524.

[00117] The term "communication device readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 500 and that cause the communication device 500 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 communication device readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of communication device readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks;

magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, communication device readable media may include non-transitory communication device readable media. In some examples, communication device readable media may include communication device readable media that is not a transitory propagating signal.

[00118] The instructions 524 may further be transmitted or received over a communications network 526 using a transmission medium via the network interface device 520 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 (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 520 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 526. In an example, the network interface device 520 may include a plurality of antennas to wirelessly

communicate using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) techniques. In some examples, the network interface device 520 may wirelessly communicate using Multiple User MIMO techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 500, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[00119] FIG. 6 is a flow chart of an example method 600 for facilitating a transmission of SG physical uplink control channel. In some examples, the method 600 is implemented at a UE.

[00120] The method 600 begins at operation 610, where the UE determines uplink control information for SG physical uplink control channel (xPUCCH).

[00121] At operation 620, the UE facilitates a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information, and wherein the transmission of the xPUCCH comprises xPUCCH format 3, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein a payload size of the transmitted xPUCCH is between 3 and 22 bits. After operation 620, the method 600 ends.

[00122] The subject technology is described below in conjunction with various examples.

[00123] Example 1 is an apparatus of a user equipment (UE), the apparatus comprising: processing circuitry; and memory, the processing circuitry to: determine uplink control information for SG physical uplink control channel (xPUCCH); and facilitate a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information, and wherein the xPUCCH has a format corresponding to a payload size of the xPUCCH.

[00124] In Example 2, the subject matter of Example 1 optionally includes that the transmission of the xPUCCH comprises xPUCCH format 1/1 a/lb, which carries scheduling request, and 1 or 2 bit HARQ ACK/NACK feedback.

[0012S] In Example 3, the subject matter of Example 2 optionally includes that the UE is configured with two antenna ports (AP), and wherein a Zadoff-Chu (ZC) sequence with different cyclic shift value on each antenna port (AP) is applied.

[00126] In Example 4, the subject matter of Example 1 optionally includes that the transmission of the xPUCCH comprises xPUCCH format 2, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein the payload size of the transmitted xPUCCH is between 3 and 13 bits.

[00127] In Example 5, the subject matter of Example 1 optionally includes that the transmission of the xPUCCH comprises xPUCCH format 3, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein the payload size of the transmitted xPUCCH is between 3 and 22 bits.

[00128] In Example 6, the subject matter of Example 1 optionally includes that the transmission of the xPUCCH comprises xPUCCH format 4, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein the payload size of the transmitted xPUCCH is greater than 22 bits.

[00129] In Example 7, the subject matter of any of Examples 4-6 optionally includes that a number of antenna ports (AP) is configured for the UE.

[00130] In Example 8, the subject matter of Example 7 optionally includes that a space frequency block code (SFBC) is applied for the xPUCCH format 2, 3 and 4 in a case when two antenna ports (AP) are configured for UE.

[00131] In Example 9, the subject matter of Example 7 optionally includes that per-resource element (RE) cyclic transmission mode is applied for the xPUCCH format 2, 3 and 4 in a case when two antenna ports (AP) are configured for UE. [00132] In Example 10, the subject matter of any of Examples 1, 2, 4, 5, and 6 optionally includes that cell specific cyclic shift is applied for xPUCCH transmission for inter-cell interference randomization.

[00133] In Example 11, the subject matter of any of claims 1, 2, 4, 5, and 6 optionally includes transceiver circuitry to transmit the xPUCCH; and an antenna coupled with the transceiver circuitry.

[00134] In Example 12, the subject matter of any of Examples 1, 2, 4, 5, 6 optionally includes that the processing circuitry comprises a baseband processor.

[00135] In Example 13, the subject matter of Example 1 optionally includes the processing circuitry to facilitate the transmission of the xPUCCH by formatting or encoding the determined uplink control information.

[00136] In Example 14, the subject matter of Example 1 optionally includes the processing circuitry to format the xPUCCH into the format corresponding to a payload size of the xPUCCH.

[00137] Example 15 is an apparatus of an evolved Node B (eNB), the apparatus comprising: processing circuitry; and memory, the processing circuitry to: receive 5G physical uplink control channel (xPUCCH) from multiple user equipments (UEs), including a UE with two antenna ports; and determine uplink control information from the received xPUCCH, wherein the xPUCCH has a format corresponding to a payload size of the xPUCCH.

[00138] In Example 16, the subject matter of Example 15 optionally includes cell specific and UE specific cycle shift values are applied for a Zadoff- Chu (ZC) sequence for the xPUCCH, wherein the UE specific cycle shift values are configured via radio resource control (RRC) signaling or indicated in downlink control information (OCT) via xPDCCH.

[00139] In Example 17, the subject matter of Example 15 optionally includes the multiple UEs are multiplexed in a frequency division multiplexing (FDM) manner using assigned physical resource block groups (RBGs).

[00140] In Example 18, the subject matter of Example 15 optionally includes the processing circuitry to multiplex the xPUCCH in a code division multiplexing (CDM) manner.

[00141] Example 19 is a machine-readable medium storing instructions which, when executed by processing circuitry of a user equipment (UE), cause the processing circuitry to: determine uplink control information for 5G physical uplink control channel (xPUCCH); and facilitate a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information, and wherein the transmission of the xPUCCH comprises xPUCCH format 3, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein a payload size of the transmitted xPUCCH is between 3 and 22 bits.

[00142] In Example 20, the subject matter of Example 19 optionally includes a number of antenna ports (AP) is configured for the UE.

[00143] In Example 21 , the subj ect matter of Example 20 optionally includes a space frequency block code (SFBC) is applied for the xPUCCH format 3 in a case when two antenna ports (AP) are configured for UE.

[00144] In Example 22, the subject matter of Example 20 optionally includes per-resource element (RE) cyclic transmission mode is applied for the xPUCCH format 3 in a case when two antenna ports (AP) are configured for UE.

[00145] In Example 23, the subject matter of Example 19 optionally includes cell specific cyclic shift is applied for xPUCCH transmission for inter- cell interference randomization.

[00146] Example 24 is an apparatus of a user equipment (UE), the apparatus comprising: means for determining uplink control information for 5G physical uplink control channel (xPUCCH); and means for facilitating a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information, and wherein the transmission of the xPUCCH comprises xPUCCH format 3, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein a payload size of the transmitted xPUCCH is between 3 and 22 bits.

[00147] In Example 25, the subject matter of Example 24 optionally includes a number of antenna ports (AP) is configured for the UE.

[00148] In Example 26, the subject matter of Example 24 optionally includes a space frequency block code (SFBC) is applied for the xPUCCH format 3 in a case when two antenna ports (AP) are configured for UE.

[00149] In Example 27, the subject matter of Example 24 optionally includes per-resource element (RE) cyclic transmission mode is applied for the xPUCCH format 3 in a case when two antenna ports (AP) are configured for UE.

[00150] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00151] Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

[00152] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00153] The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment (UE), the apparatus comprising:

processing circuitry; and memory, the processing circuitry to:

determine uplink control information for SG physical uplink control channel (xPUCCH); and

facilitate a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information, and wherein the xPUCCH has a format corresponding to a payload size of the xPUCCH.

2. The apparatus of claim 1 , wherein the transmission of the xPUCCH comprises xPUCCH format 1/1 a/lb, which carries scheduling request, and 1 or 2 bit HARQ ACK/NACK feedback.

3. The apparatus of claim 2, wherein the UE is configured with two antenna ports (AP), and wherein a Zadoff-Chu (ZC) sequence with different cyclic shift value on each antenna port (AP) is applied.

4. The apparatus of claim 1, wherein the transmission of the xPUCCH comprises xPUCCH format 2, which carries scheduling request, HARQ

ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein the payload size of the transmitted xPUCCH is between 3 and 13 bits.

5. The apparatus of claim 1, wherein the transmission of the xPUCCH comprises xPUCCH format 3, which carries scheduling request, HARQ

ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein the payload size of the transmitted xPUCCH is between 3 and 22 bits.

6. The apparatus of claim 1 , wherein the transmission of the xPUCCH comprises xPUCCH format 4, which carries scheduling request, HARQ

ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein the payload size of the transmitted xPUCCH is greater than 22 bits.

7. The apparatus of any of claims 4-6, wherein a number of antenna ports (AP) is configured for the UE.

8. The apparatus of claim 7, wherein a space frequency block code (SFBC) is applied for the xPUCCH format 2, 3 and 4 in a case when two antenna ports (AP) are configured for UE.

9. The apparatus of claim 7, wherein per-resource element (RE) cyclic transmission mode is applied for the xPUCCH format 2, 3 and 4 in a case when two antenna ports (AP) are configured for UE.

10. The apparatus of any of claims 1, 2, 4, 5, and 6, wherein cell specific cyclic shift is applied for xPUCCH transmission for inter-cell interference randomization.

11. The apparatus of any of claims 1, 2, 4, 5, 6, further comprising:

transceiver circuitry to transmit the xPUCCH; and

an antenna coupled with the transceiver circuitry.

12. The apparatus of any of claims 1, 2, 4, 5, 6, wherein the processing circuitry comprises a baseband processor.

13. The apparatus of claim 1, the processing circuitry to facilitate the transmission of the xPUCCH by formatting or encoding the determined uplink control information.

14. The apparatus of claim 1, the processing circuitry to format the xPUCCH into the format corresponding to a payload size of the xPUCCH.

15. An apparatus of an evolved Node B (eNB), the apparatus comprising: processing circuitry; and memory, the processing circuitry to:

receive 5G physical uplink control channel (xPUCCH) from multiple user equipments (UEs), including a UE with two antenna ports; and

determine uplink control information from the received xPUCCH, wherein the xPUCCH has a format corresponding to a payload size of the xPUCCH.

16. The apparatus of claim 15, wherein cell specific and UE specific cycle shift values are applied for a Zadoff-Chu (ZC) sequence for the xPUCCH, wherein the UE specific cycle shift values are configured via radio resource control (RRC) signaling or indicated in downlink control information (DCI) via xPDCCH.

17. The apparatus of claim 15, wherein the multiple UEs are multiplexed in a frequency division multiplexing (FDM) manner using assigned physical resource block groups (RBGs).

18. The apparatus of claim 15, the processing circuitry to multiplex the xPUCCH in a code division multiplexing (CDM) manner for xPUCCH format 1/la/lb.

19. A machine-readable medium storing instructions which, when executed by processing circuitry of a user equipment (UE), cause the processing circuitry to:

determine uplink control information for SG physical uplink control channel (xPUCCH); and

facilitate a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK NACK) feedback, channel state information (CSI) reports, and beam related information, and wherein the transmission of the xPUCCH comprises xPUCCH format 3, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related

information, and wherein a payload size of the transmitted xPUCCH is between 3 and 22 bits.

20. The machine-readable medium of claim 19, wherein a number of antenna ports (AP) is configured for the UE.

21. The machine-readable medium of claim 20, wherein a space frequency block code (SFBC) is applied for the xPUCCH format 3 in a case when two antenna ports (AP) are configured for UE.

22. The machine-readable medium of claim 20, wherein per-resource element (RE) cyclic transmission mode is applied for the xPUCCH format 3 in a case when two antenna ports (AP) are configured for UE.

23. The machine-readable medium of claim 19, wherein cell specific cyclic shift is applied for xPUCCH transmission for inter-cell interference

randomization.

24. An apparatus of a user equipment (UE), the apparatus comprising: means for determining uplink control information for SG physical uplink control channel (xPUCCH); and

means for facilitating a transmission of the xPUCCH to carry the determined uplink control information to an allocated resource, wherein the determined uplink control information includes one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgment/ no acknowledgement (ACK/NACK) feedback, channel state information (CSI) reports, and beam related information, and wherein the transmission of the xPUCCH comprises xPUCCH format 3, which carries scheduling request, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports or beam related information, and wherein a payload size of the transmitted xPUCCH is between 3 and 22 bits.

25. The apparatus of claim 24, wherein a number of antenna ports (AP) is configured for the UE.