U.S. provisional patent application No.62/299,457 entitled "UCI channel coding ON XPUCCH (UCI channel coding ON XPUCCH)" filed 2016, 24.s.c. § 119, hereby incorporated by reference in its entirety.
Detailed Description
The following description and the annexed drawings set forth in detail certain illustrative embodiments sufficiently 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 others. Embodiments set forth in the claims encompass all available equivalents of those claims.
Mobile communications have evolved from early voice systems to the current highly sophisticated integrated communication platforms. Fifth generation (5G) wireless communication network systems provide access to information and sharing of data, etc. at many different locations and times by various users and applications. 5G network systems aim to meet the demands for performance dimensions and services that are very different and sometimes conflicting with each other. These requirements are driven by the different services or applications of the 5G network system that the user desires. In general, with some exceptions, 5G was developed from the third generation partnership project (3GPP) Long Term Evolution (LTE) and new Radio Access Technologies (RATs) were added to the 3GPP LTE.
Fig. 1A-1B are block diagrams of Time Division Duplex (TDD) subframe structures 100A and 100B in the Downlink (DL) according to some embodiments. The subframe structure 100A of fig. 1A is a low-latency structure, and the subframe structure 100B of fig. 1B is a high-throughput structure.
As shown in fig. 1A, the subframe structure 100A includes a 5G physical downlink control channel (xPDCCH)110A, a 5G physical downlink shared channel (xPDSCH)120A, a Guard Time (GT)130A, and a 5G physical uplink control channel (xPUCCH) 140A. Blocks 110A, 120A, 130A, and 140A are within a single subframe 150A. As shown in fig. 1B, subframe structure 100B is similar to subframe structure 100A, including xPDCCH 110B, xPDSCH 120B, GT 130B, and xPUCCH 140B. Unlike the subframe structure 110A, in the subframe structure 100B, the blocks 110A, 120A, 130A, and 140A are divided between two subframes 150B-1 and 150B-2. Subframe 150B-1 includes a portion of xPDCCH 110B and xPDSCH 120B. Subframe 150B-2 includes the remainder of xPDSCH 120B, GT 130B, and xPUCCH 140B.
To enable low delay transmission for enhanced mobile broadband communications, a self-contained TDD subframe 150A may be introduced, as shown in fig. 1A. Fig. 1A-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 xPDCCH110A/110B and is transmitted immediately after xPDCCH 110A/110B. GT 130A/130B is inserted or not inserted between xPDSCH 120A/120B and xPUCCH140A/140B in order to accommodate DL-to-Uplink (UL) and UL-to-DL handover times and round trip propagation delays.
To increase the data rate, two or more subframes 150B-1 and 150B-2 may be aggregated for one xPDSCH 120B transmission for a User Equipment (UE) (e.g., as discussed in connection with fig. 2). As shown in fig. 1B, xPDSCH 120B spans two subframes 150B-1 and 150B-2 in high throughput structure 100B. GT 130B is inserted into second subframe 150B-2. In this case, the GT overhead can be reduced by half compared to the low delay structure 100A of fig. 1A. In some cases, additional xpdcchs (other than xPDCCH 110B) are inserted in subframe 150B-2 to allow the same subframe scheduling for DL data channel transmission. As shown in FIG. 1B, 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 xPDSCH 120B extending across additional subframes.
According to some examples, in LTE, the PUCCH is transmitted in a frequency region on the edge of the system bandwidth. In addition, the PUCCH and the Physical Uplink Shared Channel (PUSCH) are multiplexed in a Frequency Division Multiplexing (FDM) manner. However, as shown in fig. 1A-1B, xPUCCH 110A/110B and data channels are multiplexed in a Time Division Multiplexing (TDM) manner. In the case where Uplink Control Information (UCI) includes hybrid automatic repeat request (HARQ) acknowledgement/non-acknowledgement (ACK/NACK) feedback or Channel State Information (CSI) reports (e.g., Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), and Rank Indicator (RI)), different xPUCCH formats are defined according to different payload sizes. In some embodiments, the subject technology proposes a specific xPUCCH format for carrying UCI with various payload sizes.
As described above, the xPUCCH is used to carry uplink control information, which may include scheduling request, HARQ ACK/NACK feedback, CSI report, and beam related information. Various xPUCCH formats may be defined according to a payload size.
In one example, xPUCCH format 1/1a/1b is used to carry scheduling requests and 1 or 2 bit HARQ ACK/NACK feedback.
In one example, xPUCCH format 2 is used to carry scheduling requests, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports and/or beam related information. The payload size is between 3 and 13 bits.
In one example, xPUCCH format 3 is used to carry scheduling requests, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports and/or beam related information. The payload size is between 3 and 22 bits.
In one example, xPUCCH format 4 is used to carry scheduling requests, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports and/or beam related information. The payload size is greater than 22 bits.
In some embodiments, one physical Resource Block Group (RBG) corresponds to six Physical Resource Blocks (PRBs), which is the smallest resource unit for xPUCCH transmission. In this case, the eNode B (eNB) may schedule the UE to transmit xPUCCH using one or more RBGs according to the indication in the Downlink Control Information (DCI) (see discussion of fig. 2 for details of the operation of the UE and eNB).
The physical uplink control channel xPUCCH carries uplink control information. In some cases, xPUCCH is transmitted in the last symbol of a subframe. All xPCCH formats use cyclic shiftWhich varies with the number of slots according to equation 1.
In the case of the equation 1, the,is a cell-specific cyclic shift value;is the number of symbols in one slot; n issIs the slot number within a frame. For 5G, nsIn the range of 0 to 99. In equation 1, c (i) is a pseudo random sequence. To be provided withTo initialize the pseudo-random sequence generator. The physical uplink control channel supports a variety of formats as shown in table 1.
Table 1: supported xPCCH format
xPCH format |
Modulation scheme |
Number of bits per frame, Mbit |
1 |
N/A |
N/A |
1a |
BPSK |
1 |
1b |
QPSK |
2 |
2 |
QPSK |
48 |
3 |
QPSK |
96 |
4 |
QPSK |
192 |
In table 1, the modulation scheme QPSK refers to quadrature phase shift keying, and the modulation scheme BPSK refers to binary phase shift keying.
In some cases, xPUCCH format 1/1a/lb is used to carry scheduling requests and 1 or 2 bit HARQ ACK/NACK feedback. The detailed design of xPCH format 1/1a/1b is provided below.
In one embodiment, within one xPUCCH resource, a plurality of UEs may be multiplexed in a Code Division Multiplexing (CDM) manner. Further, in case that the UE is configured with two Antenna Ports (APs), a Zadoff-Chu (ZC) sequence having a different cyclic shift value is applied to each AP to achieve transmission diversity.
Further, in order to randomize inter-cell interference, cell-and UE-specific cyclic shift values are applied to the ZC sequence, wherein the UE-specific cyclic shift values may be configured by a higher layer via RRC signaling or indicated in DCI via xPDCCH.
For xPUCCH format 1, information is conveyed by the presence/absence of transmission of xPUCCH from the UE. In some cases, for xPUCCH format 1, d (0) ═ 1.
For xPCH formats 1a and 1b, one is transmitted respectivelyOne or two explicit bits. Blocks b (0), …, b (M) were aligned as described in Table 1bit-1) to obtain complex-valued symbols d (0). Table 2 gives the modulation schemes for different xPUCCH formats.
Table 2: modulation symbol d (0) of xPUCCH.
According to equation 2, for each of the P antenna ports used for PUCCH transmission, the complex-valued symbol d (0) and the cyclic shift lengthOf (2) aMultiplication.
In the case of the equation 2, the,is a modulated symbol; p is the number of antenna ports;is the antenna port index; d (0) is an input symbol; in equation 2, theTo defineAntenna port specific trackingRing displacementVarying between slots as defined in equation 3.
In the case of the equation 3,is a cyclic shift; n issIs the slot number within a frame;is the antenna port index; p is the number of antenna ports;is the number of subcarriers in one Resource Block (RB). In the case of the equation 3,configured by higher layers. The block of complex-valued symbols y is mapped to z according to equation 4.
In the case of the equation 4, the,is the number of RBs for one xPCCH transmission;Is the transmission data mapped to the corresponding xPUCCH resource;is a modulated symbol for xPUCCH; k is the modulated symbol index. In equation 4:
m'=0,1,2,...,5
resources for transmission of PUCCH formats 1, 1a and 1b are indexed by resourceIdentification, determining PRB group index from the resource index according to equation 5And combinatorial indexingWherein N iscomb=2。
In another embodiment, multiple UEs are multiplexed in a Frequency Division Multiplexing (FDM) manner by using the assigned RBGs.
For xPUCCH format 1, information is conveyed by the presence/absence of transmission of xPUCCH from the UE. In some cases, for xPUCCH format 1, it is assumed that d (0) ═ 1.
For xPUCCH formats 1a and 1b, one or two explicit bits are sent, respectively. Blocks b (0), …, b (M) are aligned as described in Table 5.4.1-1bit-1) to obtain complex-valued symbols d (0). Table 3 gives the modulation schemes for different xPUCCH formats.
Table 3: modulation symbol d (0) of xPUCCH.
According to equation 6, for each of the P antenna ports used for PUCCH transmission, the complex-valued symbol d (0) and the cyclic shift lengthOf (2) aMultiplication.
In the case of the equation 6,is a modulated symbol; p is the number of antenna ports;is the antenna port index; d (0) is an input symbol; furthermore, in equation 6To defineAntenna port specific cyclic shift is defined by equation 7
In the case of the equation 7,is a cyclic shift; n issIs the slot number within a frame;is the antenna port index; p is the number of antenna ports;is the number of subcarriers in one Resource Block (RB). In addition, in equation 7,configured by higher layers. The block of complex-valued symbols y is mapped to z according to equation 8.
In the case of the equation 8,is the number of RBs for one xPUCCH transmission;is the transmission data mapped to the corresponding xPUCCH resource;is a modulated symbol for xPUCCH; k is the modulated symbol index. In equation 8:
m′=0,1,2,…,5
resources for transmission of PUCCH formats 1, 1a and 1b are indexed by resources configured by higher layersTo identify.
xPUCCH formats 2, 3, and 4 are discussed below.
As described above, xPUCCH formats 2 and 3 may be used to carry scheduling requests, HARQ ACK/NACK feedback for multiple HARQ processes, CSI reports, and/or beam related information. xPUCCH format 2 may be used to carry uplink control information with a payload size between 3 and 13 bits; xPUCCH format 3 may be used to carry uplink control information with a payload size between 3 and 22 bits; xPUCCH format 4 may be used to carry uplink control information with a payload size greater than 22 bits.
In one embodiment, in case that two APs are configured for the UE, a Space Frequency Block Code (SFBC) is applied to xPUCCH formats 2, 3 and 4. In addition, a cell-specific cyclic shift may be applied to xPUCCH transmission to randomize inter-cell interference.
More specifically, according to equation 9, bit blocks b (0), …, b (M)bit-1) should be scrambled with a scrambling sequence specific to the UE, resulting in a block of scrambled bits
In equation 9, c (i) is a scrambling sequence. The scrambling sequence generator is initialized by equation 10 at the beginning of each subframe.
In equation 10, nsIs the slot number within a frame;is a physical cell ID; n isRNTIIs a cell radio network temporary identifier (C-RNTI). Scrambled bit blockIs Quadrature Phase Shift Keying (QPSK) modulated, resulting in blocks of complex valued modulation symbols d (0), …, d (M)symb-1), wherein Msymb=Mbit/2。
The complex-valued modulation symbols to be transmitted are mapped onto one or two layers. Complex-valued modulation symbols d (0), …, d (M)symb-1) is mapped to layer x (i) ═ x(0)(i)…x(v-1)(i)]T, Wherein v is the number of layers, andis the number of modulation symbols in each layer.
For transmission on a single antenna port, using a single layer v-1, the mapping is defined as: x is the number of(0)(i) D (i), wherein,for transmissions on both antenna ports and with a mapping rule v 2, willIs applied to equation 11.
x(0)(i)=d(2i)
x(1)(i)=d(2i+1)
Equation 11
In some cases, precoding is used. Precoder blocks vector x from layer mapping(0)(i)…x(v-1)(i)]T,As input and generate a vector block y to be mapped to a resource element(0)(i)…y(P-1)(i)]T,
For transmission on a single antenna port, precoding is defined by equation 12:
y(0)(i)=x(0)(i)
equation 12
Andin conjunction with equation 12. For two antenna portsOn-going transmission, the output of precoding operation y (i) — [ y(0)(i)y(1)(i)]T,Defined by equation 13.
In the case of the equation 13,and isThe mapping to resource elements is defined by an operation on quadruples of complex-valued symbols. Let Indicating antenna portsSymbol quadruple i.
Quaternary block(wherein M isquad=Msymb/4) are cyclically shifted fromTo obtainWherein,
for xPUCCH format 2, a block of complex valued symbols is mapped according to equation 14Mapping to z.
In the case of the equation 14,is the number of RBs for one xPUCCH transmission;is the transmission data mapped to the corresponding xPUCCH resource;is a modulated symbol for xPUCCH; k is the modulated symbol index. In equation 14:
for the xPUCCH format 3, the format is,and is Configured by higher layers and indicated in xPDCCH.
For the xPUCCH format 4, the format is,and isWhich is configured by higher layers and indicated in xPDCCH.
In another embodiment, in case that two APs are configured for the UE, a cyclic transmission mode per Resource Element (RE) is applied for xPUCCH formats 2, 3 and 4.
In xPUCCH formats 3 and 4, bit blocks b (0), …, b (M)bit-1) scrambling with a scrambling sequence specific to the UE, thereby to be in accordance withObtaining a block of scrambled bitsWhere c (i) is a scrambling sequence. At the beginning of each sub-frame byInitializing a scrambling sequence generator, wherein nRNTIIs a cell radio network temporary identifier (C-RNTI). Scrambled bit blockIs Quadrature Phase Shift Keying (QPSK) modulated, resulting in blocks of complex valued modulation symbols d (0), …, d (M)symb-1), wherein Msymb=Mbit/2。
Layer mapping is sometimes applied. The complex-valued modulation symbols to be transmitted are mapped onto one or two layers. Complex-valued modulation symbols d (0), …, d (M)symb-1) should be mapped to layer x (i) ═ x(0)(i)…x(v-1)(i)]T,Wherein v is the number of layers, andis the number of modulation symbols in each layer.
For transmission on a single antenna port, using a single layer v-1, the mapping is defined as: x is the number of(0)(i) D (i), wherein,the mapping rule for transmission on two antenna ports with v-2 is defined by equation 15, where
x(0)(i)=d(i)
x(1)(i)=d(i)
Equation 15
In some embodiments, precoding is used. Precoder blocks vector x from layer mapping(0)(i)…x(v-1)(i)]T,As input and generate a vector block y to be mapped to a resource element(0)(i)…y(P-1)(i)]T,For transmission on a single antenna port, precoding is defined by equation 16:
y(0)(i)=x(0)(i)
Equation 16
In the case of the equation 16,and is
For two antenna portsOn-going transmission, the output of precoding operation y (i) — [ y(0)(i)y(1)(i)]T,Defined by equation 17.
y(0)(2i)=x(0)(i),y(0)(2i+1)=0
y(1)(2i)=0,y(1)(2i+1)=x(1)(i)
Equation 17
In the case of the equation 17,and is
The mapping to resource elements is defined by an operation on quadruples of complex-valued symbols. In some cases, it is possible to use,indicating antenna portsSymbol quadruple i.
Quaternary block(wherein M isquad=Msymb/4) are cyclically shifted, thereby obtainingWherein, the complex-valued symbol block is formed according to equation 14Mapping to z.
In the case of the equation 18, the,is the number of RBs for one xPUCCH transmission;is the transmission data mapped to the corresponding xPUCCH resource;is a modulated symbol for xPUCCH; k is the modulated symbol index. In equation 18:
resources for transmission of PUCCH format 2 are indexed by resourceIdentifying, from the resource index, a PRB group index determined according to equation 19And Combined index (comb index)
According to equation 19, for xPUCCH format 2,and is For the xPUCCH format 3, the format is,and isThis is configured by higher layers.
Fig. 2 illustrates an example of portions of an end-to-end network architecture of a Long Term Evolution (LTE) network 200 having various components of the network, in accordance with some embodiments. As used herein, LTE networks refer to LTE and LTE-advanced (LTE-a) networks and other releases of LTE networks to be developed. Network 200 may include a Radio Access Network (RAN) (e.g., as shown, E-UTRAN or evolved universal terrestrial radio access network) 201 and a core network 220 (e.g., shown as Evolved Packet Core (EPC)) coupled together by an S1 interface 215. For convenience and brevity, only portions of the core network 220 and the RAN 201 are shown in this example. The network 200 includes a UE202 configured to determine uplink control information for xPUCCH; and encode a transmission of xPUCCH to carry the determined uplink control information to the allocated resources, wherein the determined uplink control information comprises one or more of: scheduling request, hybrid automatic repeat request (HARQ) acknowledgement/non-acknowledgement (ACK/NACK) feedback, Channel State Information (CSI) reporting, and beam related information. UE202 is configured to access a 5G physical uplink control channel (xPUCCH) format for transmitting Uplink Control Information (UCI), wherein the xPUCCH format corresponds to a payload size of the xPUCCH; accessing UCI, wherein data in the UCI comprises one or more of hybrid automatic repeat request (HARQ) Acknowledgements (ACKs), Scheduling Requests (SRs), Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Beam Indicators (BI); and encoding the UCI based on the xPCH format and the data in the UCI. The network 200 includes an eNB 204. One or more of enbs 204 are configured to access xpucchs from a plurality of User Equipments (UEs), including UEs with two antenna ports; and multiplexing the accessed xpucchs, wherein ZC sequences having different cyclic shift values are applied on the xpucchs received from each antenna port for a UE configured with two antenna ports. In some examples, UE202 transmits xPUCCH to eNB204, which receives xPUCCH from UE 202.
The core network 220 may include a Mobility Management Entity (MME)222, a serving gateway (serving GW)224, and a packet data network gateway (PDN GW) 226. RAN 201 may include an evolved node B (eNB)204 (which may operate as a base station) for communicating with User Equipment (UE) 202. The enbs 204 may include a macro eNB204a and a Low Power (LP) eNB204 b.
The MME 222 may be similar in function to the control plane of a conventional Serving GPRS Support Node (SGSN). The MME 222 may manage mobility aspects in access such as gateway selection and tracking area list management. Serving GW 224 may terminate the interface towards RAN 201 and route data packets between RAN 201 and core network 220. In addition, serving GW 224 may be a local mobility anchor for inter-eNB handover and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement. The serving GW 224 and the MME 222 may be implemented in one physical node or separate physical nodes.
The PDN GW 226 may terminate the SGi interface towards the Packet Data Network (PDN). The PDN GW 226 may route data packets between the EPC220 and the external PDN, and may perform policy enforcement and charging data collection. The PDN GW 226 may also provide an anchor for mobile devices with non-LTE access. The external PDN may be any type of IP network and IP Multimedia Subsystem (IMS) domain. The PDN GW 226 and the serving GW 224 may be implemented in a single physical node or in separate physical nodes.
The eNB204 (macro eNB and micro eNB) may terminate the air interface protocol and may be the first point of contact for the UE 202. In some embodiments, the eNB204 may implement various logical functions of the RAN 201, including but not limited to RNCs (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. According to an embodiment, the UE202 may be configured to communicate Orthogonal Frequency Division Multiplexed (OFDM) communication signals with the eNB204 via a multicarrier communication channel in accordance with an OFDMA communication technique. The OFDM signal may include a plurality of orthogonal subcarriers.
S1 interface 215 may be an interface that separates RAN 201 and EPC 220. It can be divided into two parts: S1-U, which may carry traffic data between eNB204 and serving GW 224; and S1-MME, which may be a signaling interface between eNB204 and MME 222. The X2 interface may be an interface between enbs 204. The X2 interface may include two parts, X2-C and X2-U. X2-C may be a control plane interface between eNBs 204, while X2-U may be a user plane interface between eNBs 204.
With cellular networks, LP cell 204b may generally be used to extend coverage to indoor areas where outdoor signals do not reach well, or to increase network capacity in heavily used areas. In particular, it may be desirable to enhance the coverage of a wireless communication system using different sized cells (macro, micro, pico, and femto cells) to improve system performance. The different sized cells 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 the different sized cells operating on different frequency bands. As used herein, the term LP eNB refers to an eNB for implementing any suitable relative LP for a smaller cell (smaller than a macro cell), such as a femto cell, pico cell, or micro cell. Femto cell enbs may typically be provided by mobile network operators to their residential or business customers. A femto cell may typically be the size of a residential gateway or smaller and is typically connected to a broadband line. Femto cells can connect to the mobile operator's mobile network and provide additional coverage, typically in the range of 30 to 50 meters. Thus, LP eNB204b may be a femto cell eNB as it is coupled through the PDN GW 226. Similarly, a picocell may be a wireless communication system that generally covers a small area, such as indoors (offices, malls, train stations, etc.), or more recently, within a cabin. A picocell eNB may typically connect through its Base Station Controller (BSC) functionality to another eNB, such as a macro eNB, via an X2 link. Thus, the LP eNB may be implemented with a picocell eNB as it may be coupled to a macro eNB204a via an X2 interface. The pico eNB or other LP eNB204b may incorporate some or all of the functionality of the macro eNB LP eNB204 a. In some cases, this may be referred to as an access point base station or an enterprise femtocell.
In some embodiments, the UE202 may communicate with an Access Point (AP)204 c. AP 204c may communicate with UE202 using only unlicensed spectrum (e.g., WiFi frequency bands). The AP 204c may communicate with the macro eNB204A (or LP eNB204B) over an Xw interface. In some embodiments, the AP 204c may communicate with the UE202 independently of communication between the UE202 and the macro eNB 204A. In other embodiments, the AP 204c may be controlled by the macro eNB204A and use LWA as described in more detail below.
Communications over an LTE network may be divided into 10ms frames, each of which may contain 10 1ms subframes. Each subframe of a frame may in turn contain two 0.5ms slots. Each subframe may be used for Uplink (UL) communication from the UE to the eNB or Downlink (DL) communication 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 various frequency bands (f)1And f2) Or (c) is transmitted. The resource allocation in a subframe used in one frequency band may be different from the resource allocation in another frequency band. Each slot of a subframe may contain 6-7 OFDM symbols, depending on the system used. In one embodiment, a subframe may contain 12 subcarriers. The downlink resource grid may be used for downlink transmissions from the eNB to the UE, while the uplink resource grid may be used for uplink transmissions from the UE to the eNB or from the UE to another UE. The resource grid may be a time-frequency grid, which is a physical resource in the downlink in each slot. The smallest time-frequency unit in the 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) describing the mapping of physical channels to resource elements and Physical RBs (PRBs). A PRB may be the smallest resource unit that may be allocated to a UE. The frequency of a resource block may be 180kHz wide and the time may be 1 slot long. In frequency, a resource block may be 12 × 15kHz subcarrier wide or 24 × 7.5kHz subcarrier wide. For most channels and signals, 12 subcarriers may be used per resource block, depending on the system bandwidth. In Frequency Division Duplex (FDD) mode, both uplink and downlink frames can be 10ms and frequency (full duplex) or time (half duplex) separated. In Time Division Duplex (TDD), uplink and downlinkSubframes may be transmitted on the same frequency and 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 include 12 (subcarriers) × 14 (symbols) ═ 168 resource elements.
Each OFDM symbol may contain a Cyclic Prefix (CP), which may be used to effectively cancel inter-symbol interference (ISI), and a Fast Fourier Transform (FFT) period. The duration of the CP may be determined by the highest degree of delay spread expected. Although distortion from the previous OFDM symbol may exist within the CP, where the CP has sufficient duration, the previous OFDM symbol does not enter the FFT period. Once the FFT period signal is received and digitized, the receiver can ignore the signal in the CP.
There may be several different physical downlink channels, including a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH), that are communicated using such resource blocks. Each subframe may be partitioned into PDCCH and PDSCH. The PDCCH may typically occupy the first two symbols of each subframe and carry information about a transmission format and resource allocation related to a PDSCH channel, etc., as well as H-ARQ information related to an uplink shared channel. The PDSCH may carry user data and higher layer signaling to the UE and occupy the remainder of the subframe. In general, downlink scheduling (allocation of 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 downlink resource allocation information may be transmitted to each UE on a PDCCH used for (allocated to) the respective UE. The PDCCH may contain Downlink Control Information (DCI) in one of a number of formats that instruct the UE how to find and decode data transmitted on the PDSCH in the same subframe from the resource grid. The DCI format may provide details such as the number of resource blocks, resource allocation type, modulation scheme, transport block, redundancy version, coding rate, and the like. 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. Using UE-specific RNTIs may restrict decoding of DCI formats (and thus the corresponding PDSCHs) to only intended UEs.
The embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. Fig. 3 illustrates components of a UE according to some embodiments. At least some of the illustrated components may be used in an eNB or MME, such as UE202 or eNB204 shown in fig. 2, for example. The UE 300 and other components may be configured to use synchronization signals as described herein. The UE 300 may be one of the UEs 302 shown in fig. 1 and may be a fixed, 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 constitute a transceiver. In some embodiments, other network elements (such as enbs) may contain some or all of the components shown in fig. 3. Other network elements, such as the MME, may contain interfaces, such as the S1 interface, to communicate with the eNB over a wired connection with the UE.
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 special-purpose processors (e.g., graphics processors, application processors, etc.). The processor 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.
Baseband circuitry 304 may include circuitry such as, but not limited to: one or more single-core or multi-core processors. Baseband circuitry 304 may include one or more baseband processors and/or control logic to process baseband signals received from the receive signal path of RF circuitry 306 and to generate baseband signals for the transmit signal path of RF circuitry 306. Baseband processing circuitry 304 may interface with application circuitry 302 to generate and process baseband signals and to control the operation of RF circuitry 306. For example, in some embodiments, the baseband circuitry 304 may include a second generation (2G) baseband processor 304a, a third generation (3G) baseband processor 304b, a fourth generation (4G) baseband processor 304c, and/or one or more other baseband processors 304d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). Baseband circuitry 304 (e.g., one or more of baseband processors 304 a-d) may handle various radio control functions that support communication with one or more radio networks via 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, the modulation/demodulation circuitry of baseband circuitry 304 may include FFT, precoding, and/or constellation mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of baseband circuitry 304 may include convolution, tail-biting convolution, turbo, Viterbi (Viterbi), and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.
In some embodiments, baseband circuitry 304 may include elements of a protocol stack, e.g., elements of an evolved universal terrestrial radio access network (E-UTRAN) protocol, including, for example: physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and/or radio link control (RRC) elements. A Central Processing Unit (CPU)304e of the baseband circuitry 304 may be configured to run elements of a 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 (DSPs) 304 f. The audio DSP 304f may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, components of the baseband circuitry may be combined in a single chip, a single chipset, or disposed on the same circuit board, as appropriate. In some embodiments, some or all of the constituent components of baseband circuitry 304 and application circuitry 302 may be implemented together, for example, on a system on a chip (SOC).
In some embodiments, baseband circuitry 304 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 304 may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), Wireless Personal Area Networks (WPANs). 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 may be configured to operate in accordance with communication standards or other protocols or standards, including Institute of Electrical and Electronics Engineers (IEEE)802.16 wireless technology (WiMax), IEEE 802.11 wireless technology (WiFi) including IEEE 802.11ad (operating in the 60GHz 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 that have been or will be developed.
RF circuitry 306 may support communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 306 may include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. RF circuitry 306 may include a receive signal path that may include circuitry to down-convert RF signals received from FEM circuitry 308 and provide baseband signals to baseband circuitry 304. RF circuitry 306 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by baseband circuitry 304 and provide RF output signals to FEM circuitry 308 for transmission.
In some embodiments, RF circuitry 306 may include a receive signal path and a transmit signal path. The receive signal path of RF circuitry 306 may include mixer circuitry 306a, amplifier circuitry 306b, and filter circuitry 306 c. The transmit signal path of RF circuitry 306 may include filter circuitry 306c and mixer circuitry 306 a. RF circuitry 306 may also include synthesizer circuitry 306d for synthesizing frequencies for use by mixer circuitry 306a of the receive signal path and the transmit signal path. In some embodiments, mixer circuitry 306a of the receive signal path may be configured to down-convert RF signals received from FEM circuitry 308 based on a synthesized frequency provided by synthesizer circuitry 306 d. Amplifier circuit 306b may be configured to amplify the downconverted signal, and filter circuit 306c may be a Low Pass Filter (LPF) or a Band Pass Filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 304 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some embodiments, mixer circuit 306a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.
In some embodiments, mixer circuitry 306a of the transmit signal path may be configured to upconvert the input baseband signal based on a synthesis frequency provided by synthesizer circuitry 306d to generate the RF output signal of FEM circuitry 308. The baseband signal may be provided by baseband circuitry 304 and may be filtered by filter circuitry 306 c. Filter circuit 306c may include a Low Pass Filter (LPF), although the scope of the embodiments is not limited in this respect.
In some embodiments, mixer circuitry 306a of the receive signal path and mixer circuitry 306a of the transmit signal path may comprise two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion, respectively. In some embodiments, mixer circuit 306a of the receive signal path and mixer circuit 306a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, mixer circuitry 306a of the receive signal path and mixer circuitry 306a of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, mixer circuit 306a of the receive signal path and mixer circuit 306a of the transmit signal path may be configured for superheterodyne operation.
In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 304 may include a digital baseband interface to communicate with RF circuitry 306.
In some dual-mode embodiments, separate radio IC circuits may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
In some embodiments, synthesizer circuit 306d may be a fractional-N synthesizer or a fractional-N/N +1 synthesizer, although the scope of embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 306d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.
The synthesizer circuit 306d may be configured to synthesize an output frequency for use by the mixer circuit 306a of the RF circuit 306 based on the frequency input and the divider control input. In some embodiments, synthesizer circuit 306d may be a fractional-N/N +1 synthesizer.
In some embodiments, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), but this is not required. The divider control input may be provided by baseband circuitry 304 or application processor 302 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application processor 302.
Synthesizer circuit 306d of RF circuit 306 may include frequency dividers, Delay Locked Loops (DLLs), multiplexers, and phase accumulators. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD) and the phase accumulator may be a Digital Phase Accumulator (DPA). In some embodiments, the DMD may be configured to divide an input signal by N or N +1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, a 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 decompose the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this manner, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
In some embodiments, synthesizer circuit 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 with a quadrature generator and divider circuit to generate a plurality of signals having a plurality of mutually different phases at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuitry 306 may include an IQ/polarity converter.
FEM circuitry 308 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 310, amplify the received signals, and provide amplified versions of the received signals to RF circuitry 306 for further processing. FEM circuitry 308 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuitry 306 for transmission by one or more of one or more antennas 310.
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 the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuitry 306). The transmit signal path of the FEM circuitry 308 may include: a Power Amplifier (PA) for amplifying an input RF signal (e.g., provided by RF circuitry 306) and one or more filters for generating RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 310).
In some embodiments, the UE 300 may include additional elements, such as memory/storage, a display, a camera, sensors, and/or an 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 network tablet, a wireless telephone, a smart phone, 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 a user to interact with the system, and/or peripheral component interfaces designed to enable peripheral components to interact with the system. For example, the UE 300 may include one or more of a keyboard, keypad, touchpad, display, sensor, non-volatile memory port, Universal Serial Bus (USB) port, audio jack, power interface, one or more antennas, graphics processor, application processor, speaker, microphone, and other I/O components. The display may be an LCD or LED screen including a touch screen. The sensors may include a gyroscope 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, such as Global Positioning System (GPS) satellites.
Antenna 310 may include 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, antennas 310 may be effectively separated to take advantage of spatial diversity and possibly different channel characteristics.
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 one of the functions described herein. In some embodiments, a functional element 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). 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.
Fig. 4 is a block diagram of a communication device according to some embodiments. The device may be a UE or eNB, such as UE202 or eNB204 shown in fig. 2, for example. Physical layer circuitry 402 may perform various encoding and decoding functions, which may include forming a baseband signal for transmission and decoding a received signal. The communication device 400 may also include a medium access control layer (MAC) circuit 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 a memory 408 arranged to perform the operations described herein. Physical layer circuitry 402, MAC circuitry 404, and processing circuitry 406 may handle various radio control functions that enable communications with one or more radio networks to be compatible with one or more radio technologies. The radio control functions may include signal modulation, encoding, decoding, radio frequency shifting, and the like. For example, similar to the device shown in fig. 2, in some embodiments, one or more of WMAN, WLAN, and WPAN may be utilized to enable communication. In some embodiments, the communication device 400 may 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 2G, 3G, 4G, 5G, etc. technologies that have been or will be developed. The communication device 400 may include a transceiver circuit 412 to enable wireless communication with other external devices, and an interface 414 to enable wired communication with other external devices. As another example, transceiver circuitry 412 may perform various transmit and receive functions, such as signal conversion between the baseband range and the Radio Frequency (RF) range.
Antenna 401 may include 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, antennas 401 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
Although 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 Digital Signal Processors (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 one of the functions described herein. In some embodiments, a functional element 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.
Fig. 5 illustrates another block diagram of a communication device 500 according to some embodiments. The communication device 500 may correspond to the UE202 or 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 a server-client network environment. In an example, the communications device 500 may act as a peer to peer communications device in a peer to peer (P2P) (or other distributed) network environment. The communication device 500 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smart phone, web appliance, network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by the communication device. Further, while only a single communication device is shown, 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 (e.g., cloud computing, software as a service (SaaS), other computer cluster configurations).
As described herein, an example may include, or may operate on, logic or multiple components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, a circuit (e.g., internally or with respect to an external entity such as other circuits) may be arranged as a module in a specified manner. In an example, all or a portion of one or more computer systems (e.g., a stand-alone client or server computer system) or one or more hardware processors may be operated by firmware or software (e.g., instructions, application portions, or applications) 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.
Thus, the term "module" is understood to encompass a tangible entity, either a physical construct, a permanent configuration (e.g., hardwired), or a temporary configuration (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which modules are temporarily configured (e.g., programmed), each module need not be configured or instantiated at any one time. For example, if the modules include a general purpose processor configured using software, the general purpose processor may be configured at different times as respective different modules. Software may thus configure a hardware processor to, for example, constitute a particular module at one time and to constitute a different module at a different time.
A 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 interconnection link (e.g., bus) 508. The communication device 500 may also 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, the input device 512, and the 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 for communicating or controlling one or more peripheral devices (e.g., printer, card reader, etc.).
The storage device 516 may include a communication device readable medium 522 on which is stored one or more data structures or sets of instructions 524 (e.g., software) embodying or used 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.
While the communication device-readable medium 522 is shown to be a single medium, the term "communication device-readable medium" can 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.
The term "communication device-readable medium" may include any medium that is capable of storing, encoding or carrying instructions for execution by communication device 500 and that cause communication device 500 to perform any one or more of the techniques of this disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting examples of communication device readable media may include solid state memory and optical and magnetic media. Specific examples of the communication device readable medium may include: non-volatile memories 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, the communication device readable medium may include a non-transitory communication device readable medium. In some examples, the communication device readable medium may include a communication device readable medium of a non-transitory propagating signal.
The instructions 524 may further be transmitted or received using a transmission medium via the network interface device 520 and over a communication network 526 using any one of a number of transmission 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), a mobile telephone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, and a wireless data network (e.g., referred to as a "POTS") networkOf the Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards, known asIEEE 802.16 family of standards), IEEE 802.15.4 family of standards, Long Term Evolution (LTE) family of standards, Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, and the like. 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 connected to the communication network 526. In an example, the network interface device 520 may include multiple wireless antennas to 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 multi-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 communication signals or other intangible medium to facilitate communication of such software.
Fig. 6 illustrates a process 600 for xPUCCH formats 1a, 1b, 2, and 3 according to some embodiments. Process 600 occurs at UE 202. According to this process 600, data arrives at a coding unit (e.g., a coding unit of the UE 202) in the form of HARQ-ACKs, channel quality information, beam measurement indications, and indicators of scheduling requests.
One form of channel coding as shown in fig. 6 is for transmitting HARQ-ACK on xPUCCH format 1a/1b, and for transmitting at least one or a combination of HARQ-ACK, channel quality information (CQI and/or PMI), beam related information, and rank indicator on xPUCCH format 2 or format 3.
As shown in fig. 6, at block 610, processing circuitry of the UE applies channel coding to hybrid automatic repeat request (HARQ) Acknowledgements (ACKs) and CQI bits (a) when encoding UCI0...aA-1) To obtain an encoded output bit sequence (b)0...bB-1). The length of the HARQ-ACK and CQI bit sequence is a and the length of the encoded output bit sequence is B. In FIG. 6, aiAnd bjRepresenting the bits in the HARQ-ACK and CQI bit sequences or the encoded output bit sequence, respectively.
Fig. 7 illustrates a process 700 for 5G physical uplink control channel (xPUCCH) format 4, according to some embodiments. The process 700 occurs at the UE 202. Process 700 of fig. 7 may be used in the case where a >22 and at least one of a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), beam-related information, and a rank indicator is transmitted on xPUCCH format 3 or xPUCCH format 4.
As shown in FIG. 7, at block 710, the UE202 appends Cyclic Redundancy Check (CRC) bits to HARQ-ACK and Channel Quality Information (CQI) bits (a)0...aA-1) To obtain a CRC-appended bit sequence (c)0...cK-1)。
At block 720, the UE202 applies channel coding to the CRC appended bit sequence (c)0...cK-1) Obtaining an encoded bit sequence (d)(1) 0…d(1) D-1)。
At block 730, the UE202 applies rate matching to the encoded bit sequence (d)(1) 0…d(1) D-1) To obtain a rate-matched bit sequence (e)0…eE-1)。
For each subframe, HARQ-ACK bits are received from a higher layer. HARQ-ACK consists of 1 bit of information, i.e., b0Or consist of 2 bits of information, i.e. b0b1Wherein b is0ACK/NACK bit corresponding to codeword 0 and b1Corresponding to the ACK/NACK bit of codeword 1. Each positive Acknowledgement (ACK) is decoded as a binary '1' and each Negative Acknowledgement (NACK) is decoded as a binary '0'. For the case where xPUCCH format 3 is configured or scheduled, the HARQ-ACK feedback includes a concatenation of HARQ-ACK bits that the UE needs to feedback for the downlink subframe. For cells configured with transmission mode 1 or 2 (i.e., single codeword transmission mode), 1 bit of HARQ-ACK information akFor that cell. For cells configured with other transmission modes, 2-bit HARQ-ACK information (i.e., a)k、ak+1) Is used for these cells, wherein akHARQ-ACK bit and a corresponding to codeword 0k+1HARQ-ACK bits corresponding to codeword 1. The HARQ-ACK bits are processed for transmission.
In some cases, it is possible to use,is the number of HARQ-ACK bits when xPUCCH format 2 is used for transmission of HARQ-ACK feedback. Bit sequenceAre obtained from HARQ-ACK bits of different downlink subframes. In some cases, it is possible to use,is the number of downlink subframes that the UE needs to feed back HARQ-ACK bits in cell c. The following pseudo code is used to calculate the number of HARQ-ACK bits to be transmitted by the UE.
If k ≦ 22, multiplexing of HARQ-ACK bits is performed according to the following pseudo code.
In case that transmission of HARQ-ACK feedback using xPUCCH format 2 includes coincidence with a subframe configured to the UE by a higher layer for transmission of a Scheduling Request (SR), and if k <22, a scheduling request bit is appended at the end of the concatenated HARQ-ACK bit sequence (1 positive SR; 0 negative SR).
For theBit sequenceBy setting upTo obtain the final product.
For theIf i is even, the bit sequenceBy setting upIs obtained and is set if i is oddTo obtain the final product.
For theEncoding a bit sequence according to equation 20
In equation 20, i is 0,1,2i,nDefined in table 4.
Table 4: base sequence for (32, O) codes
i |
Mi,0 |
Mi,1 |
Mi,2 |
Mi,3 |
Mi,4 |
Mi,5 |
Mi,6 |
Mi,7 |
Mi,8 |
Mi,9 |
Mi,10 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
1 |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
2 |
1 |
0 |
0 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
1 |
3 |
1 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
1 |
0 |
1 |
4 |
1 |
1 |
1 |
1 |
0 |
0 |
0 |
1 |
0 |
0 |
1 |
5 |
1 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
1 |
0 |
1 |
6 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
7 |
1 |
0 |
0 |
1 |
1 |
0 |
0 |
1 |
1 |
0 |
1 |
8 |
1 |
1 |
0 |
1 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
9 |
1 |
0 |
1 |
1 |
1 |
0 |
1 |
0 |
0 |
1 |
1 |
10 |
1 |
0 |
1 |
0 |
0 |
1 |
1 |
1 |
0 |
1 |
1 |
11 |
1 |
1 |
1 |
0 |
0 |
1 |
1 |
0 |
1 |
0 |
1 |
12 |
1 |
0 |
0 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
1 |
13 |
1 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
1 |
14 |
1 |
0 |
0 |
0 |
1 |
1 |
0 |
1 |
0 |
0 |
1 |
15 |
1 |
1 |
0 |
0 |
1 |
1 |
1 |
1 |
0 |
1 |
1 |
16 |
1 |
1 |
1 |
0 |
1 |
1 |
1 |
0 |
0 |
1 |
0 |
17 |
1 |
0 |
0 |
1 |
1 |
1 |
0 |
0 |
1 |
0 |
0 |
18 |
1 |
1 |
0 |
1 |
1 |
1 |
1 |
1 |
0 |
0 |
0 |
19 |
1 |
0 |
0 |
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
20 |
1 |
0 |
1 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
1 |
21 |
1 |
1 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
22 |
1 |
0 |
0 |
0 |
1 |
0 |
0 |
1 |
1 |
0 |
1 |
23 |
1 |
1 |
1 |
0 |
1 |
0 |
0 |
0 |
1 |
1 |
1 |
24 |
1 |
1 |
1 |
1 |
1 |
0 |
1 |
1 |
1 |
1 |
0 |
25 |
1 |
1 |
0 |
0 |
0 |
1 |
1 |
1 |
0 |
0 |
1 |
26 |
1 |
0 |
1 |
1 |
0 |
1 |
0 |
0 |
1 |
1 |
0 |
27 |
1 |
1 |
1 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
0 |
28 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
0 |
1 |
0 |
0 |
29 |
1 |
0 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
0 |
0 |
30 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
31 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Output bit sequence b0,b1,b2,...,,bB-1By cyclically repeating sequencesTo obtain a mixture of, among others,wherein i ═ 0,1,2,., B-1, and wherein,and isIn another embodiment, B andother values may be used. For the Encoding a bit sequence according to equations 21 and 22And
in equations 21 and 22, where i is 0,1,2i,nDefined in table 4. Output bit sequence b0,b1,b2,...,,bB-1(wherein,) By a sequence of bitsAndas listed in the pseudo code below.
For the case of using xPCH format 3, a is used for channel quality bits input to a channel coding block0,a1,a2,…,aA-1Where A is the number of bits. The number of channel quality bits depends on the transmission format of the wideband report.
The channel quality information may be encoded using a (20, a) code. The code words of the (20, A) code are 13 in terms of Mi,nThe linear combinations of the base sequences represented are defined in table 5.
Table 5: base sequence for (20, a) code.
i |
Mi,0 |
Mi,1 |
Mi,2 |
Mi,3 |
Mi,4 |
Mi,5 |
Mi,6 |
Mi,7 |
Mi,8 |
Mi,9 |
Mi,10 |
Mi,11 |
Mi,12 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
0 |
1 |
1 |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
1 |
0 |
2 |
1 |
0 |
0 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
1 |
1 |
1 |
3 |
1 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
1 |
0 |
1 |
1 |
1 |
4 |
1 |
1 |
1 |
1 |
0 |
0 |
0 |
1 |
0 |
0 |
1 |
1 |
1 |
5 |
1 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
1 |
0 |
1 |
1 |
1 |
6 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
1 |
1 |
7 |
1 |
0 |
0 |
1 |
1 |
0 |
0 |
1 |
1 |
0 |
1 |
1 |
1 |
8 |
1 |
1 |
0 |
1 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
1 |
1 |
9 |
1 |
0 |
1 |
1 |
1 |
0 |
1 |
0 |
0 |
1 |
1 |
1 |
1 |
10 |
1 |
0 |
1 |
0 |
0 |
1 |
1 |
1 |
0 |
1 |
1 |
1 |
1 |
11 |
1 |
1 |
1 |
0 |
0 |
1 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
12 |
1 |
0 |
0 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
1 |
1 |
1 |
13 |
1 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
1 |
14 |
1 |
0 |
0 |
0 |
1 |
1 |
0 |
1 |
0 |
0 |
1 |
0 |
1 |
15 |
1 |
1 |
0 |
0 |
1 |
1 |
1 |
1 |
0 |
1 |
1 |
0 |
1 |
16 |
1 |
1 |
1 |
0 |
1 |
1 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
17 |
1 |
0 |
0 |
1 |
1 |
1 |
0 |
0 |
1 |
0 |
0 |
1 |
1 |
18 |
1 |
1 |
0 |
1 |
1 |
1 |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
19 |
1 |
0 |
0 |
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
After encoding, the code is encoded according to equation 23To represent these bits.
In equation 23, i is 0,1, 2. Output bit sequence b0,b1,b2,...,,bB-1By cyclically repeating sequencesTo obtain a mixture of, among others,wherein i is 0,1,2, …, B-1, wherein,
table 6 shows some examples of fields and corresponding bit widths for channel quality information feedback for wideband reporting of PDSCH transmissions. These fields include a Beam Indicator (BI), a Rank Indicator (RI), a wideband Precoding Matrix Indicator (PMI), and a wideband Channel Quality Indicator (CQI).
Table 6: a field for CQI feedback for wideband CQI reporting.
Field(s) |
Bit width |
BI |
3 |
RI |
1 |
Wideband PMI |
2 |
Wideband CQI |
4 |
Fig. 8 is a flow diagram of a method 800 for UCI channel coding on xPUCCH according to some embodiments. The method 800 is implemented at the UE202 of fig. 2.
The method 800 begins with operation 810, wherein the UE202 accesses an xPUCCH format for transmitting UCI. The xPUCCH format corresponds to a payload size of xPUCCH. In some cases, the xPUCCH format is one of xPUCCH formats 1, 1a, 1b, 2, 3, and 4.
At operation 820, the UE202 accesses the UCI. The data in the UCI includes HARQ-ACK. In some cases, the data in the UCI may also include one or more of SR, CQI, PMI, RI, and BI.
At operation 830, the UE202 encodes UCI based on the xPUCCH format and data in the UCI. After operation 830, the method 800 ends.
The subject technology is described below in connection with various examples.
Example 1 is an apparatus of a User Equipment (UE), the apparatus comprising: processing circuitry and memory, the processing circuitry to: accessing a 5G physical uplink control channel (xPUCCH) format for transmitting Uplink Control Information (UCI), wherein the xUCCH format corresponds to a payload size of the xUCCH; accessing UCI, wherein data in the UCI comprises one or more of hybrid automatic repeat request (HARQ) Acknowledgements (ACKs), Scheduling Requests (SRs), Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Beam Indicators (BI); and encoding the UCI based on the xPCH format and the data in the UCI.
In example 2, the subject matter of example 1 optionally includes: the xPUCCH format includes one of xPUCCH formats 1, 1a and 1b, and wherein the UCI includes HARQ-ACK; and the processing circuitry applies channel coding to the HARQ-ACK bit sequence (a) when encoding the UCI0...aA-1) To obtain an encoded output bit sequence (b)0...bB-1)。
In example 3, the subject matter of example 1 optionally includes: the xPUCCH format includes xPUCCH format 2, and the UCI includes HARQ-ACK; the processing circuitry, when encoding the UCI, is configured to: determining the number of downlink subframes for feeding back HARQ-ACK bits to a cell c by UE; setting a HARQ-ACK bit counter (k) to 0; for each downlink subframe of the number of downlink subframes: incrementing the HARQ-ACK bit counter (k) by 1 if the configured transmission mode for cell c is 1:1HARQ-ACK feedback, or if the configured transmission mode for cell c is not 1:1HARQ-ACK feedback, then increment HARQ-ACK bit counter (k) by 2; and encoding the UCI based on the final value of the HARQ-ACK bit counter (k).
In example 4, the subject matter of example 3 optionally includes: the processing circuit, when encoding the UCI, is further configured to: determining that a HARQ-ACK bit counter (k) is less than or equal to 22; upon determining that the HARQ-ACK bit counter (k) is less than or equal to 22, for each downlink subframe of the number of downlink subframes: transmitting one downlink packet in a downlink subframe in case that the transmission mode is 1:1 bit HARQ-ACK feedback; and transmitting two downlink packets in a downlink subframe if the transmission mode is not 1:1 bit HARQ-ACK feedback.
In example 5, the subject matter of example 1 optionally includes: the xPUCCH format includes one of xPUCCH formats 2 and 3; and processing circuitry applies channel coding to hybrid automatic repeat request (HARQ) Acknowledgements (ACKs) and CQI bits (a) when encoding UCI0...aA-1) To obtain an encoded output bit sequence (b)0...bB-1)。
In example 6, the subject matter of example 1 optionally includes: the xPUCCH format includes xPUCCH format 4; and the processing circuitry, when encoding the UCI, is configured to: appending Cyclic Redundancy Check (CRC) bits to HARQ-ACK and Channel Quality Information (CQI) bits (a)0...aA-1) Sequence to obtain a CRC-appended bit sequence (c)0...cK-1) (ii) a Applying a channel coding to the CRC addition bit sequence (c)0...cK-1) To obtain an encoded bit sequence (d)(i) 0...d(i) D-1) (ii) a And applying rate matching to said coded bit sequence (d)(i) 0...d(i) D-1) To obtain a rate-matched bit sequence (e)(i) 0...e(i) E-1)。
In example 7, the subject matter of any of examples 2, 3, 5, and 6 optionally includes: at least one of the UCI bits includes information indicating a decoding result of reception data, radio channel state information, or preferred beam direction information.
In example 8, the subject matter of examples 5-6 optionally includes: the processing circuit is used for: calculating a codeword as a linear combination of a plurality of stored sequences; and encoding the UCI bits using the codeword.
In example 9, the subject matter of example 1 optionally includes: the processing circuitry is to encode UCI for transmission to an evolved NodeB (eNB) using an error correction coding technique.
In example 10, the subject matter of example 1 optionally includes: the xPUCCH format includes one of xPUCCH formats 1, 1a, 1b, 2, 3, and 4.
In example 11, the subject matter of example 1 optionally includes: the UCI includes HARQ-ACK and SR, and wherein an SR bit is appended after the HARQ-ACK bit in the UCI.
In example 12, the subject matter of examples 1,2, 3, 5, and 6 optionally includes: a transceiver circuit for transmitting xPCH; and an antenna coupled to the transceiver circuitry.
Optional inclusion in example 13 according to the subject matter of examples 1,2, 3, 5, and 6: the processing circuitry includes a baseband processor.
Example 14 is a machine-readable medium storing instructions that, when executed by processing circuitry of a User Equipment (UE), cause the processing circuitry to: accessing a 5G physical uplink control channel (xPUCCH) format for transmitting Uplink Control Information (UCI), wherein the xUCCH format corresponds to a payload size of the xUCCH; accessing UCI, wherein data in the UCI comprises hybrid automatic repeat request (HARQ) Acknowledgement (ACK); and encoding the UCI based on the xPCH format and the data in the UCI.
In example 15, the subject matter of example 14 can optionally include: the xPUCCH format includes one of xPUCCH formats 1, 1a, and 1 b; the processing circuitry applies channel coding to the HARQ-ACK bit sequence (a) when encoding the UCI0...aA-1) To obtain an encoded output bit sequence (b)0...bB-1)。
In example 16, the subject matter of example 14 optionally includes: the xPUCCH format includes xPUCCH format 2, and the UCI includes HARQ-ACK; the processing circuitry, when encoding the UCI, is configured to: determining the number of downlink subframes for feeding back HARQ-ACK bits to a cell c by UE; setting a HARQ-ACK bit counter (k) to 0; for each downlink subframe of the number of downlink subframes: incrementing the HARQ-ACK bit counter (k) by 1 if the configured transmission mode for cell c is 1:1HARQ-ACK feedback, or if the configured transmission mode for cell c is not 1:1HARQ-ACK feedback, then increment HARQ-ACK bit counter (k) by 2; and encoding the UCI based on the final value of the HARQ-ACK bit counter (k).
In example 17, the subject matter of example 16 optionally includes: the processing circuit, when encoding the UCI, is further configured to: determining that a HARQ-ACK bit counter (k) is less than or equal to 22; upon determining that the HARQ-ACK bit counter (k) is less than or equal to 22, for each downlink subframe of the number of downlink subframes: transmitting one downlink packet in a downlink subframe in case that the transmission mode is 1:1 bit HARQ-ACK feedback; and transmitting two downlink packets in a downlink subframe if the transmission mode is not 1:1 bit HARQ-ACK feedback.
In example 18, the subject matter of example 14 can optionally include: the xPUCCH format includes one of xPUCCH formats 2 and 3; and processing circuitry applies channel coding to hybrid automatic repeat request (HARQ) Acknowledgements (ACKs) and CQI bits (a) when encoding UCI0...aA-1) To obtain an encoded output bit sequence (b)0...bB-1)。
In example 19, the subject matter of example 14 can optionally include: the xPUCCH format includes xPUCCH format 4; and the processing circuitry, when encoding the UCI, is configured to: appending Cyclic Redundancy Check (CRC) bits to HARQ-ACK and Channel Quality Information (CQI) bits (a)0...aA-1) Sequence to obtain a CRC-appended bit sequence (c)0...cK-1) (ii) a Applying channel coding to the CRC appended bit sequence (c)0...cK-1) To obtain an encoded bit sequence (d)(i) 0...d(i) D-1) (ii) a And applying rate matching to said coded bit sequence (d)(i) 0...d(i) D-1) To obtain a rate-matched bit sequence (e)(i) 0...e(i) E-1)。
In example 20, the subject matter of example 19 optionally includes: at least one of the UCI bits includes information indicating a decoding result of reception data, radio channel state information, or preferred beam direction information.
In example 21, the subject matter of example 19 optionally includes: the processing circuitry is configured to: calculating the codeword as a linear combination of a plurality of stored sequences; and encoding the UCI bits using the codeword.
In example 22, the subject matter of example 14 can optionally include: the processing circuitry is configured to encode UCI for transmission to an evolved NodeB (eNB) using an error correction coding technique.
In example 23, the subject matter of example 14 can optionally include: the UCI includes HARQ-ACK and SR, and wherein an SR bit is appended after the HARQ-ACK bit in the UCI.
Example 24 is an apparatus of a User Equipment (UE), the apparatus comprising: processing circuitry and memory, the processing circuitry to: accessing a 5G physical uplink control channel (xPUCCH) format for transmitting Uplink Control Information (UCI), wherein the xPUCCH comprises one of xPUCCH formats 1, 1a, 1b, 2, 3, and 4; accessing UCI, wherein data in the UCI comprises one or more of hybrid automatic repeat request (HARQ) Acknowledgements (ACKs), Scheduling Requests (SRs), Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Beam Indicators (BI); and encoding the UCI based on the xPCH format and the data in the UCI.
Example 25 is an apparatus of a User Equipment (UE), the apparatus comprising: means for accessing a 5G physical uplink control channel (xPUCCH) format for transmitting Uplink Control Information (UCI), wherein the xUCCH format corresponds to a payload size of the xUCCH; accessing UCI, wherein data in the UCI comprises one or more of hybrid automatic repeat request (HARQ) Acknowledgements (ACKs), Scheduling Requests (SRs), Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Beam Indicators (BI); and means for encoding the UCI based on the xPUCCH format and the data in the UCI.
In example 26, the subject matter of example 1 optionally includes: the processing circuit is to encode (code) the UCI based on the xPUCCH format and the data in the UCI by encoding (encode) the UCI based on the xPUCCH format and the data in the UCI.
Throughout this document, the terms "code" and "encoding" encompass their plain and ordinary meaning and may be used interchangeably.
Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments. The specification and drawings are, accordingly, 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. Sufficient detail to enable those skilled in the art to practice the teachings disclosed herein is described. Other embodiments may be derived therefrom and utilized, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The detailed description is, therefore, 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.
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.
In this document, the terms "a" or "an" are used generically in the patent document, to include one or more than one, and are not limited by the use of any other examples or "at least one" or "one or more". In this document, the term "or" is used to denote a non-exclusive or, whereby "a or B" includes "a but not B", "B but not a", and "a and B", unless otherwise specified. In this document, the terms "including" and "in which" are used as the plain-english equivalents of the respective terms "comprising" and "wherein". Furthermore, in the appended claims, the terms "comprising" and "including" are open-ended, i.e., the claims are intended to include within their scope other elements than those listed after the term, a system, UE, article, composition, concept, or process. Furthermore, in the appended claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.
The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.