`
`available under
`
`the
`
`Patent Cooperation Treaty (PCT)
`
`International application number: PCT/SE2011/050052
`
`International filing date:
`
`18 January 201 1 (1801.201 1)
`
`Document type:
`
`Certified copy of priority document
`
`Document details:
`
`Country/Office: US
`Number:
`61/295,885
`
`Filing date:
`
`18 January 2010 (18.01.2010)
`
`Date of receipt at the International Bureau:
`
`21 January 2011 (21.01.2011)
`
`Remark:
`
`Priority document submitted or transmitted to the International Bureau in
`compliance with Rule 17.1(a),(b) or (b-bz's)
`
`
`
`World Intellectual Property Organization (WIPO) - Geneva, Switzerland
`Organisation Mondiale de la Propriété Intellectuelle (OMPI) - Geneve, Suisse
`
`Ericsson Exhibit 1120
`
`ERICSSON v. ETRI
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`m—meoqu-MMESE.was; SM. @0._._I_.M’8
`
`UNITED STATES DEPARTMENT OF COMMERCE
`
`United States Patent and Trademark Office
`
`October 15, 2010
`
`OFFICE OF THOSE PAPERS OF THE BELOW IDENTIFIED PATENT
`
`APPLICATION THAT MET THE REQUIREMENTS TO BE GRANTED A
`FILING DATE UNDER 35 USC 111.
`
`APPLICATION NUMBER: 61/295,885
`
`FILING DATE: January 18, 2010
`
`THE COUNTRY CODE AND NUMBER OF YOUR PRIORITY
`
`APPLICATION, TO BE USED FOR FILING ABROAD UNDER THE PARIS
`
`CONVENTION, IS US6I/295,885
`
`mVIImncmgfl‘l“uv. iEE.EQl’r
`3gLE.EEEZIf..i-a
`
`v.
`
`
`
`-uu-nm-‘wnmwmn-u-u..n.-
`
`
`
`THIS IS TO CERTIFY THAT ANNEXED HERETO IS A TRUE COPY FROM
`THE RECORDS OF THE UNITED STATES PATENT AND TRADEMARK
`
`
`
`
`
`
`By Authority of the
`
`Under Secretary of Commerce for Intellectual Property
`and Director of the United States Patent and Trademark Office
`
`M. K. CARTER
`
`Certifying Officer
`
`
`
`
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`
`
`Electronic Acknowledgement Receipt
`
`
`“—
`
`
`—_
`
`
`__
`
`
`
`
`PUCCH Transmission for Carrier Aggregation in LTE-Advanced with Improved
`Inter-Cell Interference Mitigation Title of Invention:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`“—
`
`——
`
`Payment information:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`_—
`_—
`
`Document
`
`.
`
`.
`
`File Size(Bytes)I
`
`Multi
`
`Pages
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Ericsson Exhibit 1120
` Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Provisional Cover Sheet (5316)
`
`ProvisionalSB.pdf
`
`1001554
`
`a123b200158m21dc191d255bd‘le‘2c013e4 ;
`3:9
`
`Fee Worksheet (PTO-875)
`
`fee-info.pdf
`
`2&9158h31813da976d944a60m7fee2
`7950
`
`Information:
`
`
`
`This Acknowledgement Receipt evidences receipt on the noted date by the USPTO of the indicated documents,
`characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a
`Post Card, as described in MPEP 503.
`
`New Applications Under 35 U.S.C. 1 1 1
`If a new application is being filed and the application includes the necessary components for a filing date (see 37 CFR
`1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this
`Acknowledgement Receipt will establish the filing date of the application.
`
`National Stage of an International Application under 35 U.S.C. 371
`If a timely submission to enter the national stage of an international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCTIDOIEOI903 indicating acceptance of the application as a
`national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.
`
`New International Application Filed with the USPTO as a Receiving Office
`Ifa new international application is being filed and the international application includes the necessary components for
`an international filing date (see PCT Article 1 1 and MPEP 1 810), a Notification of the lntemational Application Number
`and of the International Filing Date (Form PCTIROI1 05) will be issued in due course, subject to prescriptions concerning
`national security, and the date shown on this Acknowledgement Receipt will establish the international filing date of
`the application.
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`v. ETRI
`
`Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`I 00 Code: TR.PROV
`
`I . cument Description: Provisional Cover Sheet (8816)
`
`PTO/$3116 (04-07)
`Approved for use through 06/30/2010 OMB 0651-0032
`US. Patent and Trademark Ofl'me: US. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995. no persons are required to respond to a collection of information unless it displays a valid OMB control number
`
`Provisional Application for Patent Cover Sheet
`This is a request for filing a PROVISIONAL APPLICATION FOR PATENT under 37 CFR 1.53(c)
`
`Inventor(s)
`
`Inventor 1
`
`Given Name
`
`Inventor 2
`
`Inventor 3
`
`Inventor 4
`
`Family NameMiddle Name__
`
`
`_-
`
`City “—
`
`Remove
`
`.All Inventors Must Be Listed — Addifional Inventor Information blocks may be
`generated within this form by selecting the Add button.
`
`
`
`T'tle of Invention
`I
`
`PUCCH Transmission for Carrier Aggregation in LTE—Advanced with Improved
`Inter—Cell Interference Mitigation
`
`Attorney Docket Number (if applicable)
`
`4015 6792
`
`Correspondence Address
`
`Direct all correspondence to (select one):
`
`O The address corresponding to Customer Number 0 Firm or Individual Name
`
`Customer Number
`
`241 12
`
`he invention was made by an agency of the United States Government or under a contract with an agency of the United
`States Govern ment.
`
`0 Yes, the name of the U.S. Government agency and the Government contract number are:
`
`FS — Web1.0
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`'
`
`' ‘ V-
`
`'
`
`Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`oc Code: TR.PROV
`
`ocument Description: Provisional Cover Sheet (8316)
`
`PTO/SW16 (04-07)
`Approved for use through 06l30l2010 OMB 0651-0032
`US Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995. no persons are required to respond to a collection of information unless it displays a valid OMB control number
`
`. ntity Status
`‘ oocplint claims small entity status under 37 CFR 1.27
`
`0 Yes, applicant qualifies for small entity status under 37 CFR 1.27
`
`'etitionerlapplicant is cautioned to avoid submitting personal information in documents filed in a patent application that may
`entribute to identity theft. Personal information such as social security numbers, bank account numbers, or credit card
`umbers (other than a check or credit card authorization form PTO-2038 submitted for payment purposes) is never required
`y the USPTO to support a petition or an application.
`If this type of personal information is included in documents submitted
`0 the USPTO, petitioners/applicants should consider redacting such personal information from the documents before
`submitting them to USPTO. Petitioner/applicant is advised that the record of a patent application is available to the public
`afler publication of the application (unless a non—publication request in compliance with 37 CFR 1 .213(a) is made in the
`application) or issuance of a patent. Furthermore, the record from an abandoned application may also be available to the
`public if the application is referenced in a published application or an issued patent (see 37 CFR1.14). Checks and credit
`card authorization forms PTO-2038 submitted for payment purposes are not retained in the application file and therefore are
`not publicly available.
`
`Signature
`
`Please see 37 CFR 1.4(d) for the form of the signature.
`
`
`
`Signature
`
`First Name
`
`Daniel P. Homiller/
`
`Date (YYYY-MM-DD)
`
`Jan 18, 2010
`
`Last Name
`
`Homiller
`
`Registration Number
`(If appropriate)
`
`55275
`
`This collection of information is required by 37 CFR 1 .51 . The information is required to obtain or retain a benefit by the public which is to
`file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1 .11 and 1.14. This collection
`ii? estimated to take 8 hours to complete, including gathering, preparing, and submitting the completed application form to the USPTO.
`ime will vary depending upon the individual wse. Any comments on the amount of time you require to complete this form and/or
`suggestions for reducing this burden, should be sent to the Chief Information Officer, US. Patent and Trademark Office, US. Department
`of Commerce, PO. Box 1450, Alexandria, VA 22313—1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. This
`form can only be used when in conjunction with EFs-Web. If this form is mailed to the USPTO. it may cause delays in handling
`the provisional application.
`
`
`
`FS - Web 1.0
`
`
`
`Copy provided by USPTO from the IFW Image Database on 10/1212010
`
` Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Privacy Act Statement
`
`"he Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of
`1a attached form related to a patent application or paten. Accordingly, pursuant to the requirements of the Act, please be
`tdvised that :
`(1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the
`1fonnation solicited is voluntary; and (3) the principal purpose for which the information is used by the US. Patent and
`'rademark Office is to process and/or examine your submission related to a patent application or patent.
`If you do not
`Jmish the requested information, the US. Patent and Trademark Office may not be able to process and/or examine your
`ubmission, which may result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`"he information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`9.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of lnfomration
`Act (5 U.S.C. 552) and the Privacy Act (5 U.S.C 552a). Records from this system of records may be disclosed to the
`Department of Justice to determine whether disclosure of these records is required by the Freedom of lnfonnation
`Act.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenfing evidence to
`a court, magistrate, or administrative tribunal, including disclosures to opposing counsel in the course of settlement
`negotiations.
`A record in this system of records may be disclosed, as a routine use. to a Member of Congress submitting a
`request involving an individual, to whom the record pertains, when the individual has requested assistance from the
`Member with respect to the subject matter of the record.
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need
`for the information in order to perform a contract. Recipients of information shall be required to comply with the
`requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m).
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of
`records may be disclosed, as a routine use, to the lntemational Bureau of the World Intellectual Property
`Organization, pursuant to the Patent Cooperation Treaty.
`A record in this system of records may be disclosed, as a routine use. to a n other federal agency for purposes
`of National Security review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services,
`or his/her designee, during an inspection of records conducted by GSA as part of that agency's responsibility to
`recommend improvements in records management practices and programs, under authority of 44 U.S.C. 2904 and
`2906. Such disclosure shall be made in accordance with the GSA regulations governing inspection of records for this
`purpose, and any other relevant (i.e., GSA or Commerce) directive. Such disclosure shall not be used to make
`determinations about individuals.
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of
`the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record
`may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an
`application which became abandoned or in which the proceedings were terminated and which application is
`referenced by either a published application, an application open to public inspection or an
`issued patent.
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law
`enforcement agency, if the USPTO becomes aware of a violation or potential violation of law or regulation.
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`El {ICSSON 5- E I
`
`I {I
`
`Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015-6792
`
`PUCCH Transmission for Carrier Aggregation in LTE-Advanced with Improved
`
`Inter-Cell Interference Mitigation
`
`1
`
`1.1
`
`Background
`
`Technical Background/Existing Technology
`
`1 .1.1
`
`LTE Rel-8
`
`The LTE Rel-8 standard has recently been standardized, supporting
`
`bandwidths up to 20 MHz and using OFDM in the downlink and DFT-spread OFDM in
`
`the uplink. The basic LTE downlink physical resource can thus be seen as a time-
`
`frequency grid as illustrated in Figure H, where each resource element corresponds to
`
`one OFDM subcarrier during one OFDM symbol interval.
`
`One resource element
`
`
`
`One OFDM symbol including cyclic prefix
`
`Figure 1-1 The LTE downlink physical resource
`
`In the time domain, LTE downlink transmissions are organized into radio
`
`frames of 10 ms, each radio frame consisting of ten equally-sized subframes of length
`
`Tsubframe= 1 m5-
`
`
`
`Ericsson Exhibit 1120
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015-6792
`
`.34
`:- ._‘:-
`
`
`
`#9
`+ —————————————————————————————————————————————————————————————————————————————————— a
`Radio frame (71mm =. 10 ms)
`
`Figure 1-2 LTE time-domain structure
`
`Furthermore, the resource allocation in LTE is typically described in terms of
`
`resource blocks, where a resource block corresponds to one slot (0.5 ms) in the time
`
`domain and 12 contiguous subcarriers in the frequency domain. Resource blocks are
`
`numbered in the frequency domain, starting with 0 from one end of the system
`
`bandwidth.
`
`Downlink transmissions are dynamically scheduled, i.e., in each subframe
`
`the base station transmits control information about to which terminals data is
`
`transmitted and upon which resource blocks the data is transmitted, in the current
`
`downlink subframe. This control signaling is typically transmitted in the first 1, 2, 3 or 4
`
`OFDM symbols in each subframe. A downlink system with 3 OFDM symbols as control
`
`is illustrated in Figure 1-3.
`
`One subframe
`
`
`..-.-...-../
`
`
`-llllf...l|ll..-Illl.-/
`
`
`,IIIIT...IIII.-.I|Il'-’./
`.-..~..-.-/
`
`.IIII_.‘IIII.-.IIII'../
`..--.-..-/
`
`
`
`All|!-’-IIII_-’-illl!-’-/
`
`__—-—-__—-—_—_——__—-__
`
`
`Control region
`
`W Control my Reference
`signaling
`symbOlS
`
`Figure 1-3 Downlink subframe
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`ERICSSON V. ETRI
`
`Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-USl
`
`Attorney Ref. 4015-6792
`
`0
`
`LTE uses hybrid-ARQ, where, after receiving downlink data in a subframe,
`
`the terminal attempts to decode it and reports to the base station using uplink control
`
`signaling whether the decoding was successful (ACK) or not (NAK). In case of an
`
`unsuccessful decoding attempt, the base station can retransmit the erroneous data.
`
`Uplink control signaling from the terminal to the base station consists of
`
`-
`
`0
`
`hybrid-ARQ acknowledgements for received downlink data;
`
`terminal reports related to the downlink channel conditions, used as
`
`assistance for the downlink scheduling;
`
`-
`
`scheduling requests, indicating that a mobile terminal needs uplink
`
`resources for uplink data transmissions.
`
`Uplink control information can be transmitted in two different ways:
`
`0
`
`on PUSCH (Physical Uplink shared Channel). If the terminal has been
`
`assigned resources for data transmission in the current subframe, uplink control
`
`information (including hybrid-ARQ acknowledgements) is transmitted together with data
`
`on the PUSCH.
`
`0
`
`On PUCCH (Physical Uplink Control Channel). If the terminal has not been
`
`assigned resources for data transmission in the current subframe, uplink control
`
`information is transmitted separately on PUCCH, using resource blocks specifically
`
`assigned for the purpose.
`
`Ericsson Exhibit 1120
` Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015-6792
`
`In the discussion that follows, we focus on the latter case, i.e., ACK/NAK
`
`transmission on PUCCH. As illustrated in Figure 1-4, PUCCH resources are located at
`
`the edges of the total available cell bandwidth. Each such resource consists of twelve
`
`“subcarriers” (one resource block) within each of the two slots of an uplink subframe. In
`
`order to provide frequency diversity, these frequency resources are frequency hopping
`
`on the slot boundary, i.e. one “resource” consists of 12 subcarriers at the upper part of
`
`the spectrum within the first slot of a subframe and an equally sized resource at the
`
`lower part of the spectrum during the second slot of the subframe or vice versa. If more
`
`resources are needed for the uplink L1/L2 control signaling, eg. in case of very large
`
`overall transmission bandwidth supporting a large number of users, additional resources
`
`blocks can be assigned next to the previously assigned resource blocks.
`
`The bandwidth of one resource block during one subframe is too large for the control
`
`signaling needs of a single terminal. Therefore, to efficiently exploit the resources set
`
`aside for control signaling, multiple terminals can share the same resource block. This is
`
`done by assigning the different terminals different orthogonal phase rotations of a cell-
`
`specific length-12 frequency—domain sequence.
`
`The resource used by a PUCCH is therefore not only specified in the time-
`
`frequency domain by the resource-block pair, but also by the phase rotation applied.
`
`Similarly to the case of reference signals, there are up to twelve different phase
`
`rotations specified, providing up to twelve different orthogonal sequences from each
`
`cell-specific sequence. However, in the case of frequency-selective channels, not all the
`
`twelve phase rotations can be used if orthogonality is to be retained. Typically, up to six
`
`rotations are considered usable in a cell.
`
`Ericsson Exhibit 1120
` Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015—6792
`
` 1 ms subfrarne
`
`Figure 1-4: Uplink L1/L2 control signaling transmission on PUCCH.
`
`As mentioned above, uplink L1/L2 control signaling include hybrid-ARQ
`
`acknowledgements, channel-status reports and scheduling requests. Different
`
`combinations of these types of messages are possible, using one of two available
`
`PUCCH formats, capable of carrying different number of bits.
`
`1.1.1.1
`
`PUCCH format 11
`
`PUCCH format 1 is used for hybrid-ARQ acknowledgements and scheduling requests. It
`
`is capable of carrying up to two information bits in addition to DTX. If no information
`
`transmission was detected in the downlink, no acknowledgement is generated, also
`
`known as DTX. Hence, there are 3 or 5 different combinations, depending on whether
`
`MIMO was used on the downlink or not. This is illustrated in
`
`1 There are actually three formats, 1, 1a, and 1b in the specifications, although herein they are all referred
`to as format 1 for simplicity.
`
`Ericsson Exhibit 1120
` Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015-6792
`
`
`
`PUCCH format 1 uses the same structure in the two slots of a subframe, as illustrated in
`
`Figure 1-5. For transmission of a hybrid-ARQ acknowledgement, the single hybrid-ARQ
`
`acknowledgement bit is used to generate a BPSK symbol (in case of downlink spatial
`
`multiplexing the two acknowledgement bits are used to generate a QPSK symbol). For
`
`a scheduling request, on the other hand, the BPSK/QPSK symbol is replaced by a
`
`constellation point treated as negative acknowledgement at the eNodeB. The
`
`modulation symbol is then used to generate the signal to be transmitted in each of the
`
`two PUCCH slots.
`
`
`
`
`
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006—US1
`Attorney Ref. 4015-6792
`
`One/two bi‘ls hybrid-ARC admwfedgemem
`
`.
`
`One BFSK/OPSK symbl
`
`
`
`
`Leng1h-12 phase-«mast! semence s
`'-
`(varying P:r SW1“)
`E
`
`LengthAsquence [we
`Length«3 sequence la,
`
`“5]
`
`Same processing as first slot
`
`
`
`1 ms subframe
`
`
`
`Figure 1-5 PUCCH format 1 (normal cyclic prefix).
`
`1.1.1.2
`
`PUCCH format 22
`
`Channel-status reports are used to provide the eNodeB with an estimate of
`
`the channel properties at the terminal in order to aid channel-dependent scheduling. A
`
`channel-status report consists of multiple bits per subframe. PUCCH format 1, which is
`
`capable of at most two bits of information per subframe, can obviously not be used for
`
`this purpose. Transmission of channel-status reports on the PUCCH is instead handled
`
`by PUCCH format 2, which is capable of multiple information bits per subfrarne.
`
`PUCCH format 2, illustrated for normal cyclic prefix in Figure 1-6, is based on a phase
`
`rotation of the same cell-specific sequence as format 1.
`
`
`
`2 There are actually three variants in the LTE specifications, formats 2, 2a and 2b, where the last two
`formats are used for simultaneous transmission of hybrid-ARQ acknowledgements as discussed later in
`this section. However, for simplicity, they are all referred to as format 2 herein.
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`ERICSSCN V. E I RI
`
`Ericsson Exhibit 1120
`
`
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006—US1
`
`Attorney Ref. 4015-6792
`
`Chanel-status report
`
`
`
`From wing: 10 QPSK symbols
`I».
`user».
`a.
`Fl............i.....l.....l...........1-.
`
`(varying per symbol)
`
`Same processing as first slot Laugh-12 phaseru‘lated sequeme
`
`
`
`Figure 1-6 PUCCH format 2 (normal CP).
`
`1.1.2
`
`LTE Rel-10
`
`In order to meet
`
`the upcoming lMT—Advanced requirements, 3GPP is
`
`currently standardizing LTE Rel-10 (“LTE-Advanced”). One property of Rel-10 is the
`
`support of bandwidths larger than 20 MHz while still providing backwards compatibility
`
`with Rel-8. This is achieved by aggregating multiple component carriers, each of which
`
`can be Rel-8 compatible, to form a larger overall bandwidth to an Rel-10 terminal. This
`
`is illustrated in Figure 7.
`
` \\
`
`
`
`
`
`§m\\\\\\&§s\
`'
`
`
`s\\\§s\‘\\\\\\
`
`
`
`Aggregated bandwidth of 100 MHz
`
`Figure 7: Carrier aggregation.
`
`
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`V.
`
`Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`
`
`Client Ref. P31006-U81
`
`Attorney Ref. 4015-6792
`
`In essence, each of the component carriers in Figure 7 is separately
`
`processed. For example, hybrid ARC is operated separately on each component
`
`carrier, as illustrated in Figure 8. For the operation of hybrid-ARQ, acknowledgements
`
`informing the transmitter on whether the reception of a transport block was successful
`
`or not is required. A straightforward way of realizing this is to transmit multiple
`
`acknowledgement messages, one per component carrier3.
`
`Multiple data flows (to same user)
`
`\\\\\\
`
`
`\\\\‘\V§\\\\\\
`
`
`
`\\\\\\\\
`
`'~\
`
`
`
`MAC
`
`
`
`
`Figure 8: MAC and PHY layers for carrier aggregation.
`
`3 In case of spatial multiplexing, an acknowledgement message would correspond to two bits as there are
`two transport blocks on a component carrier in this case already in the first release of LTE. In absence of
`spatial multiplexing, an acknowledgement message is a single bit as there is only a single transport block
`per component carrier.
`
`Ericsson Exhibit 1120
` Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`Attorney Ref. 4015-6792
`
`1 .2
`
`Problems with existing solutions
`
`Transmitting multiple hybrid-ARQ acknowledgement messages, one per
`
`component carrier, can in some situations be troublesome. If the current LTE FDD
`
`uplink control signaling structures are to be reused, at most two bits of information can
`
`be sent back to the eNodeB.
`
`One possibility is to bundle multiple acknowledgement bits into a single
`
`message. For example, ACK could be signaled only if all transport blocks on all
`
`component carriers are correctly received in a given subframe, othewvise a NAK is fed
`
`back. A drawback of this is that some transport blocks might be retransmitted even if
`
`they were correctly received, which could reduce performance of the system,.
`
`Introducing a multi-bit hybrid-ARQ acknowledgement format is an alternative solution.
`
`However, in case of multiple downlink component carriers, the number of
`
`acknowledgement bits in the uplink may become quite large. For example, with five
`
`component carriers, each using MIMO, there are 55 different combinations (remember,
`
`the DTX is preferable accounted for as well), requiring at least logz(55)~11.6 bits. The
`
`situation can get even worse in TDD, where multiple downlink subframes may need to
`
`be acknowledged in a single uplink subframe. For example, in a TDD configuration with
`
`4 downlink subframes and 1 uplink subframe per 5 ms, there are 55'“, corresponding to
`
`more than 46 bits of information.
`
`Currently, there is no PUCCH format in LTE specified capable of carrying
`
`such a large number of bits.
`
`10
`
`‘
`
`
`
`
`
`
`
`
`
`Copy provided by USPTO from the IFW Image Database on 10l12/2010
`
`
`
`Ericsson Exhibit 1120
`
`ERICSSON v. ETRI
`
`
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`Attorney Ref. 4015-6792
`
`2
`
`Summary
`
`In some embodiments of the present invention, the basic transmission
`
`format is block spread DFTS-OFDM, and all ACK/NACK information from all component
`
`carriers of a single user are jointly encoded. This code word is then scrambled to
`
`mitigate inter-cell interference and mapped onto symbols. This symbol sequence is then
`
`DFTS—OFDM modulated and transmitted within one DFl'S-OFDM symbol. Multiplexing
`
`of users is enabled with block spreading, i.e. the same signal (possibly scrambled with a
`
`different sequence) is spread across all DFTS-OFDM symbols within one slot or
`
`subframe.
`
`3
`
`3.1
`
`Detailed description
`
`Detailed Technical Description of the Invention
`
`Figure 9 together with Figure 10 depict one embodiment of the invention.
`
`Figure 9 shows how the ACK/NACK sequence a is transmitted within one DFl'S-OFDM
`
`symbol. The sequence a contains ACK/NACK from all aggregated component carriers.
`
`Alternatively the individual bits may also present the logical AND connection of
`
`individual ACK/NACK bits. This sequence may not only represent ACK/NACK, but DTX
`
`states can be encoded as well, e.g., if no scheduling assignment has been received for
`
`certain component carriers.
`
`
`
`Figure 9: Transmission chain that maps ACK/NACK sequence onto one
`
`DFTS-OFDM symbol.
`
`11
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`ERICSSON V. ETR|
`
`Ericsson Exhibit 1120
`
`
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006—USl
`Attorney Ref. 4015-6792
`
`In the first step the sequence a is encoded to make it more robust against
`
`transmission errors. The error correction scheme can be Block codes, Convolution
`
`codes, etc. The error correction module can possible contain also interleaver
`
`functionality.
`
`In order to randomize neighbor cell interference cell specific scrambling with
`
`code c is applied resulting ins. The scrambled sequences is then mapped to symbols —
`
`using QPSK, for example — and transmitted with a DFl'S-OFDM modulator (DFT, IFFT
`
`(which contains subcarrier mapping),.and CP insertion blocks) resulting in the
`
`sequencev .
`
`The structure depicted in Figure 9 does not yet allow multiplexing of users.
`
`Therefore the encoded bits are transmitted over several DFTS-OFDM symbols. In the
`
`simplest case the same signal is block spread, i.e. repeated several times and each
`
`copy is weighted by a scalar w[k].
`
`If we have K DFTS-OFDM symbols the block
`
`spreading sequence has length K, Le. w[k], k = 0,1,...K —1. We can construct
`
`K orthogonal sequences and thus multiplex K users. This is shown in Figure 10 where
`
`each box labeled “Mod” contains an arrangement according to Figure 9. Equivalent
`
`implementations allow application of the weight factor at other positions anywhere after
`
`the symbol mapper.
`
`
`
`’ '
`
`12
`
`Copy provided by uspro from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSgfiN v. ETRI
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015-6792
`
`In an alternative setup the signal transmitted in the K DFl'S-OFDM symbols
`
`is not a copy (ignoring the scaling by w[k]) but each block “Mod” in Figure 10 actually
`
`performs scrambling with a different sequence c. Otherwise Figure 10 is still valid. In
`
`this case cdepends in addition to the cell ID also on DFl'S-OFDM
`
`symbol/slot/subframe/radio frame number. Scrambling — and especially that the
`
`scrambling sequence can depend on cell ID as well as DFSTS-
`
`OFDM/slot/subframe/radio frame number — is a key part of some embodiments of the
`
`invention, since it provides better inter-cell interference randomization and mitigation
`
`than state-of-the-art DFTS-OFDM PUCCH transmissions.
`
`Assuming, for example, 1 reference symbol per slot, K could be 6
`
`(assuming normal cyclic prefix) in LTE. Alternatively, if no frequency hopping is used
`
`K could be 12 assuming 1 reference signal per slot. The exact design of reference
`
`signals is outside the scope of this invention and not further discussed.
`
`
`
`13
`
`Ericsson Exhibit 1120
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015-6792
`
`
`
`DFTS-OFDM
`symbol 0
`
`DFTS-OFDM
`symbol 1
`
`DFTS-OFDM
`symbol K-1
`
`Figure 10: Multiplexing of users is enabled by block spreading.
`
`Each box “Mod” contains a modulator outlined in Figure 9
`
`(excluding error correction functionality) with possibly different
`
`scrambling sequences.
`
`Depending on the number of allocated resource blocks in the DFTS-OFDM
`
`modulator the number of coded bits and thus the code rate and/or payload size (length
`
`of ACK/NACK sequencea) can be controlled. For example, if only a single resource
`
`block is allocated in frequency domain 24 coded bits are available per DFTS-OFDM
`
`symbol (assuming QPSK symbols). If this is not sufficient, the number of allocated
`
`resource blocks can be increased. More coded bits also allow for a longer scrambling
`
`code cresulting in higher scrambling gain.
`
`
`
`14
`
`Copy provided by USPTO from the IFW Image Database on 10/12/2010
`
`ERICSSCN V. E I RI
`
`Ericsson Exhibit 1120
`
`Ericsson Exhibit 1120
`ERICSSON v. ETRI
`
`
`
`Client Ref. P31006-US1
`
`Attorney Ref. 4015-6792
`
`It is worthwhile to mention the proposed scheme allows multiplexing of
`
`users with different resource block allocations. In Figure 11 an example is provided
`
`where 3 users are multiplexed. The first user requires a higher ACK/NACK payload and
`
`occupies therefore 2 resource blocks. The remaining 2 users suffice with 1 resource
`
`block each and are FDM multiplexed. Since they are FDM multiplexed they can reuse
`
`the same block spreading sequence, but of course could also use different sequences.
`
`frequency
`
`DFTS-OFDM
`
`DFrS-OFDM DFTS-OFDM
`
`DFTS-OFDM
`
`symbol 0
`
`symbol 1
`
`symbol 2
`
`symbol 3
`
`Figure 11: Users with different resource block allocations can be
`
`multiplexed. In this example the spreading factor is 4. The user
`
`allocating 2 resource blocks uses the spreading code [1 -1 1 -1]
`
`and the remaining users [1 1 1 1].
`
`A variation of the above embodiment is where the scrambled sequence s is
`
`not mapped onto one DFl'S-OFDM symbol but onto several. Figure 12 shows an
`
`example where s is transmitted over 2 DFl'S-OFDM symbols. Here a 48 bit long
`
`scrambled sequence s is mapped to 24=2x12 QPSK symbols and transmitted in 2
`
`DFTS—OFDM symbols (assuming 1 resource block allocation and each DFl'S-OFDM
`
`symbol carriers 12 symbols). The accordingly modified block spreading is depicted in
`
`1
`
`Figure 13. Each