Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 1 of 32 PageID #: 224
`
`Exhibit 9
`
`
`
`
`
`
`
`
`

`

`(12) United States Patent
`LÖhr et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 8,320,319 B2
`Nov. 27, 2012
`
`USOO832O319B2
`
`(54) SEMI-PERSISTENT SCHEDULED
`RESOURCE RELEASE PROCEDURE INA
`MOBILE COMMUNICATION NETWORK
`
`(75) Inventors: Joachim Löhr, Langen (DE);
`Alexander Golitschek Edler Von
`Elebwart, Langen (DE); Martin
`Feuersänger, Langen (DE); Christian
`Wengerter, Langen (DE)
`
`Assignee: Panasonic Corporation, Osaka (JP)
`
`(73)
`(*)
`
`Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`13/062,674
`Aug. 11, 2009
`
`PCT/EP2009/005831
`
`May 13, 2011
`
`Appl. No.:
`(21)
`(22) PCT Filed:
`(86). PCT No.:
`S371 (c)(1),
`(2), (4) Date:
`PCT Pub. No.: WO2O10/031470
`PCT Pub. Date: Mar. 25, 2010
`
`(87)
`
`(65)
`
`Prior Publication Data
`US 2011/022.3924 A1
`Sep. 15, 2011
`
`(30)
`
`Foreign Application Priority Data
`
`Sep. 17, 2008
`Dec. 19, 2008
`
`(EP) ..................................... O8O16365
`(EP) ..................................... O8O22171
`
`(51)
`
`(52)
`(58)
`
`Int. C.
`(2009.01)
`H0474/00
`U.S. C. ......... 370/329; 370/341; 370/252; 370/431
`Field of Classification Search ........................ None
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`OTHER PUBLICATIONS
`3GPP TSG RAN2#63 meeting, “C-RNTI and NDI for SPS.”
`Samsung, Todoc R2-084464, Aug. 18-24, 2008, pp. 1-3.
`International Search Report dated Nov. 25, 2009.
`3GPP TSG RAN WG1 Meeting #52bis, “PDCCH message informa
`tion content for persistent scheduling.” Philips, NXP. Todoc
`R1-081506, Mar. 31-Apr. 4, 2008, pp. 1-3.
`3GPP TSG RAN WG2 #61bis, “Configuration for semi-persistent
`scheduling.” Panasonic, R2-08 1575, Mar. 31-Apr. 4, 2008, pp. 1-4.
`3GPP TSG RAN WG2 #62, “UL semi-persistent resource deactiva
`tion.” NTT DoCoMo, Inc., R2-082483 (resubmission of
`R2-08 1859), May 5-9, 2008, pp. 1-2.
`3GPP TSG-RAN WG2 meeting #62, “Release of semi-persistent
`resources,” Qualcomm Europe, R2-082500 (was R2-081828), May
`5-9, 2008, pp. 1-2.
`3GPP TSG RAN WG2 #62bis, “Remaining issues on Persistent
`scheduling.” Panasonic, R2-083311, derived from R2-082228 and
`R2-082229, Jun. 30-Jul. 4, 2008, pp. 1-4.
`3GPP TSG-RAN Meeting #26, “Proposed Study Item on Evolved
`UTRA and UTRAN, NTT DoCoMo, et al., RP-040461, Dec. 8-10,
`2004, pp. 1-5, p. 1, Line 18.
`(Continued)
`Primary Examiner — Kibrom T Hailu
`(74) Attorney, Agent, or Firm — Seed IP Law Group PLLC
`
`ABSTRACT
`(57)
`The invention relates to a method for deactivating a semi
`persistent resource allocation of a user equipment in an LTE
`based mobile communication system. Furthermore, the
`invention also related to a user equipment and a eNode B
`implementing this method. To provide a mechanism for deac
`tivating a semi-persistent resource allocation in a LTE system
`which is not requiring any changes to the Physical layer-to
`MAC layer interface and/or preferably no changes to the
`PDCCH formats agreed by the 3GPP a combination of NDI
`value and MCS index is defined that is commanding the
`release of SPS resources. Alternatively, another solution pro
`posed to define a special transport block size that when sig
`naled in a PDCCH is commanding the release of SPS
`SOUCS.
`
`22 Claims, 9 Drawing Sheets
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 2 of 32 PageID #: 225
`
`
`
`intensii
`Packet-switchednetworks)
`
`ro-3GPP Systems)
`
`N a u?e 8
`
`l/
`
`s
`
`i
`
`i
`s
`
`&
`
`Y
`
`

`

`US 8,320,319 B2
`Page 2
`
`OTHER PUBLICATIONS
`3GPP TR25.912V7.2.0, "3rd Generation Partnership Project; Tech
`nical Specification Group Radio Access Network; Feasibility study
`for evolved Universal Terrestrial Radio Access (UTRA) and Univer
`sal Terrestrial Radio Access Network (UTRAN) (Release 7).” Jun.
`2007, pp. 1-65, p. 1, Line 19.
`3GPP TR25.913 V7.3.0, "3rd Generation Partnership Project; Tech
`nical Specification Group Radio Access Network; Requirements for
`Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)
`(Release 7).” Mar. 2006, pp. 1-18, p. 1, Line 24.
`3GPP TS 36.212 V8.3.0, "3rd Generation Partnership Project; Tech
`nical Specification Group Radio Access Network: Evolved Universal
`Terrestrial Radio Access (E-UTRA); Multiplexing and channel cod
`ing (Release 8).” May 2008, pp. 1-48, p. 13, Line 4.
`
`3GPP TS 36.213 V8.4.0, "3rd Generation Partnership Project; Tech
`nical Specification Group Radio Access Network: Evolved Universal
`Terrestrial Radio Access (E-UTRA); Physical layer procedures
`(Release 8).” Sep. 2008, pp. 1-60, p. 14, Line 6.
`3GPP TS 36.300 V8.5.0, "3rd Generation Partnership Project; Tech
`nical Specification Group Radio Access Network: Evolved Universal
`Terrestrial Radio Access (E-UTRA) and Evolved Universal Terres
`trial Radio Access Network (E-UTRAN); Overall description; Stage
`2 (Release 8).” May 2008, pp. 1-134, p. 15, Line 5.
`3GPP TS 36.321 V8.2.0, "3rd Generation Partnership Project; Tech
`nical Specification Group Radio Access Network: Evolved Universal
`Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC)
`protocol specification (Release 8).” May, 2008, pp. 1-33, p. 15, Line
`7.
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 3 of 32 PageID #: 226
`
`

`

`U.S. Patent
`
`US 8,320,319 B2
`
`A.
`
`
`
`
`
`
`
`
`
`
`
`
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 4 of 32 PageID #: 227
`
`

`

`U.S. Patent
`
`Nov. 27, 2012
`
`Sheet 2 of 9
`
`US 8,320,319 B2
`
`MME! Serving GW MME i Serving GW
`
`
`
`S1 interface
`X2 interface
`
`SPS interval (rns
`
`min TBS (bits
`
`maxTBS (bits
`
`release TBS bits)
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 5 of 32 PageID #: 228
`
`SPS interval (ms
`DL release TBS (bits
`
`
`
`
`
`Fig. 12
`
`min TBS (bits
`UL&D release TBS (bits
`
`Fig. 13
`
`maxTBS (bits
`
`UL release TBS bits
`
`

`

`U.S. Patent
`
`Nov. 27, 2012
`
`Sheet 3 of 9
`
`US 8,320,319 B2
`
`
`
`User 1
`User 2
`
`User 3
`
`User 4
`
`2
`
`1. 2.
`Aa Y.
`a
`
`3 % 2
`3 3 3.
`
`22 al
`
`--
`Tit
`
`
`
`K &
`
`
`
`&
`
`A.
`
`& : S :
`S33
`S
`
`& XXXX
`XXXX: &
`
`
`
`
`
`
`
`
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 6 of 32 PageID #: 229
`
`s
`
`ul.
`
`RB
`
`TBs FHE
`Fig. 5
`
`

`

`U.S. Patent
`
`Nov. 27, 2012
`
`Sheet 4 of 9
`
`US 8,320,319 B2
`
`YN
`
`9:61-I
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 7 of 32 PageID #: 230
`
`

`

`U.S. Patent
`
`US 8,320,319 B2
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 8 of 32 PageID #: 231
`
`

`

`U.S. Patent
`
`Nov. 27, 2012
`
`Sheet 6 of 9
`
`US 8,320,319 B2
`
`8:613
`
`
`
`a->
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 9 of 32 PageID #: 232
`
`SS
`
`

`

`U.S. Patent
`
`Nov. 27, 2012
`
`Sheet 7 of 9
`
`US 8,320,319 B2
`
`Physical layer
`
`receive POCCH
`
`N
`901
`
`process as dynamic grant K
`
`
`
`raisked with
`SPS C-RNT
`
`process as dynamic grant
`for SPS retransmission
`
`
`
`
`
`
`
`
`
`calculate TBS and report
`TBS, NDI
`and RW to MAC
`
`report undefined TBS,
`NDE and RW to MAC
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 10 of 32 PageID #: 233
`
`Fig. 9
`
`MAC Layer
`
`SPS activation,
`storelupate SPS grant
`
`908
`
`SPS deactivation,
`release SPS grant
`Y
`90
`
`

`

`U.S. Patent
`
`Nov. 27, 2012
`
`Sheet 8 of 9
`
`US 8,320,319 B2
`
`Physical Layer
`
`receive PDCCH
`
`
`
`
`
`
`
`
`
`process as
`dynamic grant
`
`masked with
`SPS-C-RNR
`
`SPS activation or
`reactivation
`
`104
`
`106
`
`MAC layer
`
`calculate TBS
`
`
`
`report TBS,
`ND and RV to MAC
`
`Y
`
`
`
`txi X retransmission
`acording to PDCCH
`
`1010
`N
`
`SPS deactivation,
`release SPS grant
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 11 of 32 PageID #: 234
`
`Fig. 10
`
`

`

`U.S. Patent
`
`Nov. 27, 2012
`
`Sheet 9 of 9
`
`US 8,320,319 B2
`
`{{}}}
`
`10? ?
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`18ÅET OVW
`
`
`
`HOOGd ?A?008)
`
`
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 12 of 32 PageID #: 235
`
`

`

`US 8,320,319 B2
`
`1.
`SEM-PERSISTENT SCHEDULED
`RESOURCE RELEASE PROCEDURE INA
`MOBILE COMMUNICATION NETWORK
`
`FIELD OF THE INVENTION
`
`The invention relates to a method for deactivating a semi
`persistent resource allocation of a user equipment in an LTE
`based mobile communication system. Furthermore, the
`invention also related to a user equipment and a eNode B
`implementing this method.
`
`10
`
`TECHNICAL BACKGROUND
`
`2
`spectrum is possible as both time-division and frequency
`division duplex is supported by AML-OFDM.
`LTE Architecture
`The overall architecture is shown in FIG. 1 and a more
`detailed representation of the E-UTRAN architecture is given
`in FIG. 2. The E-UTRAN consists of base stations (referred to
`as Node Bs or eNode Bs in the 3GPP terminology), providing
`the E-UTRA user plane (PDCP/RLC/MAC/PHY) and con
`trol plane (Radio Resource Control RRC) protocol termina
`tions towards the mobile terminal (referred to as UE in the
`3GPP terminology).
`The eNodeB hosts the Physical (PHY), Medium Access
`Control (MAC), Radio Link Control (RLC), and Packet Data
`Control Protocol (PDCP) layers that include the functionality
`of user-plane header-compression and encryption. It also
`offers Radio Resource Control (RRC) functionality corre
`sponding to the control plane. It performs many functions
`including radio resource management, admission control,
`scheduling, enforcement of negotiated UL QoS. cell infor
`mation broadcast, ciphering/deciphering of user and control
`plane data, and compression/decompression of DL/UL user
`plane packet headers.
`The eNode Bs are interconnected with each other by means
`of the X2 interface. The eNode Bs are also connected by
`means of the S1 interface to the EPC (Evolved Packet Core),
`more specifically to the MME (Mobility Management Entity)
`by means of the S1-MME and to the Serving Gateway (SGW)
`by means of the S1-U. The S1 interface supports a many-to
`many relation between MMES/Serving Gateways and eNode
`Bs. The SGW routes and forwards user data packets, while
`also acting as the mobility anchor for the user plane during
`inter-eNodeB handovers and as the anchor for mobility
`between LTE and other 3GPP technologies (terminating S4
`interface and relaying the traffic between 2G/3G systems and
`PDNGW). For idle state UEs, the SGW terminates the down
`link data path and triggers paging when downlink data arrives
`for the UE. It manages and stores UE contexts, e.g. param
`eters of the IP bearer service, network internal routing infor
`mation. It also performs replication of the user traffic in case
`of lawful interception.
`The MME is the key control-node for the LTE access
`network. It is responsible for idle mode UE tracking and
`paging procedure including retransmissions. It is involved in
`the bearer activation/deactivation process and is also respon
`sible for choosing the SGW for a UE at the initial attach and
`at time of intra-LTE handover involving Core Network (CN)
`node relocation. It is responsible for authenticating the user
`(by interacting with the HSS).
`The Non-Access Stratum (NAS) signaling terminates at
`the MME and it is also responsible for generation and allo
`cation of temporary identities to UES. It checks the authori
`zation of the UE to camp on the service provider's Public
`Land Mobile Network (PLMN) and enforces UE roaming
`restrictions. The MME is the termination point in the network
`for ciphering/integrity protection for NAS signaling and
`handles the security key management. Lawful interception of
`signaling is also supported by the MME. The MME also
`provides the control plane function for mobility between LTE
`and 2G/3G access networks with the S3 interface terminating
`at the MME from the SGSN. The MME also terminates the
`S6a interface towards the home HSS for roaming UEs.
`OFDM with Frequency-Domain Adaptation
`The AML-OFDM-based (AML-OFDM Adaptive Multi
`Layer-Orthorgonal Frequency Division Multiplex) downlink
`has a frequency structure based on a large number of indi
`vidual sub-carriers with a spacing of 15 kHz. This frequency
`granularity facilitates to implement dual-mode UTRA/E-
`
`Long Term Evolution (LTE)
`Third-generation mobile systems (3G) based on WCDMA
`(Wideband Code Division Multiple Access) radio-access
`technology are being deployed on abroad Scale all around the
`world. A first step in enhancing or evolving this technology
`entails introducing High-Speed Downlink Packet Access
`(HSDPA) and an enhanced uplink, also referred to as High
`Speed Uplink Packet Access (HSUPA), giving a radio-access
`technology that is highly competitive.
`In a longer time perspective it is, however, necessary to be
`prepared for further increasing user demands and an even
`tougher competition from new radio access technologies. To
`meet this challenge, 3GPP has initiated the study item
`Evolved UTRA and UTRAN (see 3GPP Taoc. RP-040461,
`“Proposed Study Item on Evolved UTRA and UTRAN, and
`3GPP TR 25.912: “Feasibility study for evolved Universal
`Terrestrial Radio Access (UTRA) and Universal Terrestrial
`Radio Access Network (UTRAN), version 7.2.0, June 2007,
`available at http://www.3gpp.org and both being incorporated
`herein by reference), aiming at Studying means to achieve
`additional Substantial leaps in terms of service provisioning
`and cost reduction. As a basis for this work, 3GPP has con
`cluded on a set of targets and requirements for this long-term
`evolution (LTE) (see 3GPP TR 25.913, “Requirements for
`Evolved UTRA and Evolved UTRAN, version 7.3.0, March
`2006, available at http://www.3gpp.org, incorporated herein
`by reference) including for example:
`Peak data rates exceeding 100 Mbps for the downlink
`direction and 50 Mbps for the uplink direction.
`Mean user throughput improved by factors 2 and 3 for
`uplink and downlink respectively
`Cell-edge user throughput improved by a factor 2 for
`uplink and downlink
`Uplink and downlink spectrum efficiency improved by
`factors 2 and 3 respectively.
`Significantly reduced control-plane latency.
`Reduced cost for operator and end user.
`Spectrum flexibility, enabling deployment in many differ
`ent spectrum allocations.
`The ability to provide high bit rates is a key measure for
`LTE. Multiple parallel data stream transmission to a single
`terminal, using multiple-input-multiple-output (MIMO)
`techniques, is one important component to reach this. Larger
`transmission bandwidth and at the same time flexible spec
`trum allocation are other pieces to consider when deciding
`what radio access technique to use. The choice of adaptive
`multi-layer OFDM, AML-OFDM, in downlink will not only
`facilitate to operate at different bandwidths in general but also
`large bandwidths for high data rates in particular. Varying
`spectrum allocations, ranging from 1.25MHz to 20 MHz, are
`65
`Supported by allocating corresponding numbers of AML
`OFDM subcarriers. Operation in both paired and unpaired
`
`15
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 13 of 32 PageID #: 236
`
`

`

`US 8,320,319 B2
`
`5
`
`10
`
`15
`
`25
`
`30
`
`35
`
`40
`
`45
`
`3
`UTRA terminals. The ability to reach high bit rates is highly
`dependent on short delays in the system and a prerequisite for
`this is short sub-frame duration. Consequently, the LTE sub
`frame duration is set as short as 1 mS in order to minimize the
`radio-interface latency. In order to handle different delay
`spreads and corresponding cell sizes with a modest overhead
`the OFDM cyclic prefix length can assume two different
`values. The shorter 4.7 ms cyclic prefix is enough to handle
`the delay spread for most unicast scenarios. With the longer
`cyclic prefix of 16.7 ms very large cells, up to and exceeding
`120km cell radius, with large amounts of time dispersion can
`be handled. In this case the length is extended by reducing the
`number of OFDM symbols in a sub-frame.
`The basic principle of Orthogonal Frequency Division
`Multiplexing (OFDM) is to split the frequency band into a
`number of narrowband channels. Therefore, OFDM allows
`transmitting data on relatively flat parallel channels (Subcar
`riers) even if the channel of the whole frequency band is
`frequency selective due to a multipath environment. Since the
`Subcarriers experience different channel states, the capacities
`of the Subcarriers vary and permit a transmission on each
`subcarrier with a distinct data-rate. Hence, Subcarrier-wise
`(frequency domain) Link Adaptation (LA) by means of Adap
`tive Modulation and Coding (AMC) increases the radio effi
`ciency by transmitting different data-rates over the Subcarri
`ers. OFDMA allows multiple users to
`transmit
`simultaneously on the different subcarriers per OFDM sym
`bol. Since the probability that all users experience a deep fade
`in a particular Subcarrier is very low, it can be assured that
`Subcarriers are assigned to the users who see good channel
`gains on the corresponding Sub-carriers. When allocating
`resources in the downlink to different users in a cell, the
`scheduler takes information on the channel status experi
`enced by the users for the subcarriers into account. The con
`trol information signaled by the users, i.e. CQI, allows the
`scheduler to exploit the multi-user diversity, thereby increas
`ing the spectral efficiency.
`Localized vs. Distributed Mode
`Two different resource allocation methods can be distin
`guished upon when considering a radio access scheme that
`distribute available frequency spectrum among different
`users as in OFDMA. The first allocation mode or “localized
`mode' tries to benefit fully from frequency scheduling gain
`by allocating the subcarriers on which a specific UE experi
`ences the best radio channel conditions. Since this scheduling
`mode requires associated signaling (resource allocation sig
`naling, COI in uplink), this mode would be best suited for
`non-real time, high data rate oriented services. In the local
`ized resource allocation mode a user is allocated continuous
`blocks of Subcarriers.
`The second resource allocation mode or “distributed
`mode” relies on the frequency diversity effect to achieve
`transmission robustness by allocating resources that are scat
`tered over time and frequency grid. The fundamental differ
`ence with localized mode is that the resource allocation algo
`rithm does not try to allocate the physical resources based on
`Some knowledge on the reception quality at the receiver but
`select more or less randomly the resource it allocates to a
`particular UE. This distributed resource allocation method
`seems to be best Suited for real-time services as less associ
`ated signaling (no fast CQI, no fast allocation signaling)
`relative to “localized mode” is required.
`The two different resource allocation methods are shown in
`FIG.3 and FIG. 4 for an OFDMA based radio access scheme.
`As can be seen from FIG. 3, which depicts the localized
`transmission mode, the localized mode is characterized by the
`transmitted signal having a continuous spectrum that occu
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 14 of 32 PageID #: 237
`
`50
`
`55
`
`60
`
`65
`
`4
`pies a part of the total available spectrum. Different symbol
`rates (corresponding to different data rates) of the transmitted
`signal imply different bandwidths (time/frequency bins) of a
`localized signal. On the other hand, as can be seen from FIG.
`4, the distributed mode is characterized by the transmitted
`signal having a non-continuous spectrum that is distributed
`over more or less the entire system bandwidth (time/fre
`quency bins).
`Hybrid ARQ Schemes
`A common technique for error detection and correction in
`packet transmission systems over unreliable channels is
`called hybrid Automatic Repeat request (HARQ). Hybrid
`ARQ is a combination of Forward Error Correction (FEC)
`and ARQ.
`If a FEC encoded packet is transmitted and the receiver
`fails to decode the packet correctly (errors are usually
`checked by a CRC (Cyclic Redundancy Check)), the receiver
`requests a retransmission of the packet. Generally (and
`throughout this document) the transmission of additional
`information is called "retransmission (of a packet), although
`this retransmission does not necessarily mean a transmission
`of the same encoded information, but could also mean the
`transmission of any information belonging to the packet (e.g.
`additional redundancy information).
`Depending on the information (generally code-bits/sym
`bols), of which the transmission is composed, and depending
`on how the receiver processes the information, the following
`Hybrid ARQ schemes are defined:
`In Type I HARQ schemes, the information of the encoded
`packet is discarded and a retransmission is requested, if the
`receiver fails to decode a packet correctly. This implies that all
`transmissions are decoded separately. Generally, retransmis
`sions contain identical information (code-bits/symbols) to
`the initial transmission.
`InType II HARO schemes, a retransmission is requested, if
`the receiver fails to decode a packet correctly, where the
`receiver stores the information of the (erroneous received)
`encoded packet as soft information (soft-bits/symbols). This
`implies that a soft-buffer is required at the receiver. Retrans
`missions can be composed out of identical, partly identical or
`non-identical information (code-bits/symbols) according to
`the same packet as earlier transmissions. When receiving a
`retransmission the receiver combines the stored information
`from the soft-buffer and the currently received information
`and tries to decode the packet based on the combined infor
`mation. (The receiver can also try to decode the transmission
`individually, however generally performance increases when
`combining transmissions.) The combining of transmissions
`refers to so-called soft-combining, where multiple received
`code-bits/symbols are likelihood combined and solely
`received code-bits/symbols are code combined. Common
`methods for soft-combining are Maximum Ratio Combining
`(MRC) of received modulation symbols and log-likelihood
`ratio (LLR) combining (LLR combing only works for code
`bits).
`Type II schemes are more Sophisticated than Type I
`schemes, since the probability for correct reception of a
`packet increases with receive retransmissions. This increase
`comes at the cost of a required hybrid ARQ soft-buffer at the
`receiver. This scheme can be used to perform dynamic link
`adaptation by controlling the amount of information to be
`retransmitted. E.g. if the receiver detects that decoding has
`been "almost Successful, it can request only a small piece of
`information for the next retransmission (smaller number of
`code-bits/symbols than in previous transmission) to be trans
`mitted. In this case it might happen that it is even theoretically
`
`

`

`US 8,320,319 B2
`
`Case 2:20-cv-00310-JRG Document 1-9 Filed 09/20/20 Page 15 of 32 PageID #: 238
`
`5
`not possible to decode the packet correctly by only consider
`ing this retransmission by itself (non-self-decodable retrans
`missions).
`Type III HARQ schemes may be considered a subset of
`Type II schemes: In addition to the requirements of a Type if 5
`scheme each transmission in a Type III scheme must be self
`decodable.
`HARO Protocol Operation for Unicast Data Transmissions
`A common technique for error detection and correction in
`packet transmission systems over unreliable channels is 10
`called hybrid Automatic Repeat request (HARQ). Hybrid
`ARQ is a combination of Forward Error Correction (FEC)
`and ARQ.
`If a FEC encoded packet is transmitted and the receiver
`fails to decode the packet correctly (errors are usually 15
`checked by a CRC (Cyclic Redundancy Check)), the receiver
`requests a retransmission of the packet
`In LTE there are two levels of re-transmissions for provid
`ing reliability, namely, HARQ at the MAC layer and outer
`ARQ at the RLC layer. The outer ARQ is required to handle 20
`residual errors that are not corrected by HARQ that is kept
`simple by the use of a single bit error-feedback mechanism,
`i.e. ACK/NACK. An N-process stop-and-wait HARQ is
`employed that has asynchronous re-transmissions in the
`25
`downlink and synchronous re-transmissions in the uplink.
`Synchronous HARQ means that the re-transmissions of
`HARO blocks occurat pre-defined periodic intervals. Hence,
`no explicit signaling is required to indicate to the receiver the
`retransmission schedule.
`Asynchronous HARQ offers the flexibility of scheduling 30
`re-transmissions based on air interface conditions. In this case
`some identification of the HARQ process needs to be signaled
`in order to allow for a correct combing and protocol opera
`tion. In 3GPP LTE systems, HARQ operations with eight
`processes is used. The HARQ protocol operation for down- 35
`link data transmission will be similar or even identical to
`HSDPA
`In uplink HARQ protocol operation there are two different
`options on how to schedule a retransmission. Retransmis
`sions are either'scheduled by a NACK (also referred to as a 40
`synchronous non-adaptive retransmission) or are explicitly
`scheduled by the network by transmitting a PDCCH (also
`referred to as synchronous adaptive retransmissions). In case
`ofa synchronous non-adaptive retransmission the retransmis
`sion will use the same parameters as the previous uplink 45
`transmission, i.e. the retransmission will be signaled on the
`same physical channel resources, respectively uses the same
`modulation scheme/transport format.
`Since synchronous adaptive retransmission are explicitly
`scheduled via PDCCH, the eNodeB has the possibility to 50
`change certain parameters for the retransmission. A retrans
`mission could be for example scheduled on a different fre
`quency resource in order to avoid fragmentation in the uplink,
`or eNodeB could change the modulation scheme or alterna
`tively indicate to the user equipment what redundancy ver- 55
`sion to use for the retransmission. It should be noted that the
`HARQ feedback (ACK/NACK) and PDCCH signaling
`occurs at the same timing. Therefore the user equipment only
`needs to check once whether a synchronous non-adaptive
`retransmission is triggered (i.e. only a NACK is received) or 60
`whether eNode B requests a synchronous adaptive retrans
`mission (i.e. PDCCH is signaled).
`L1/L2 Control Signaling
`In order to inform the scheduled users about their alloca
`tion status, transport format and other data related informa- 65
`tion (e.g. HARO) L1/L2 control signaling is transmitted on
`the downlink along with the data. This control signaling is
`
`6
`multiplexed with the downlink data in a Sub-frame (assuming
`that the user allocation can change from Sub-frame to Sub
`frame). Here, it should be noted, that user allocation might
`also be performed on a TTI (Transmission Time Interval)
`basis, where the TTI length is a multiple of the sub-frames.
`The TTI length may be fixed in a service area for all users,
`may be different for different users, or may even by dynamic
`for each user. Generally, then the L1/2 control signaling needs
`only be transmitted once per TTI.
`The L1/L2 control signaling is transmitted on the Physical
`Downlink Control Channel (PDCCH). It should be noted that
`assignments for uplink data transmissions, uplink (Schedul
`ing) grants, are also transmitted on the PDCCH.
`Generally, the information sent on the L1/L2 control sig
`naling may be separated into the two categories, Shared Con
`trol Information and Dedicated Control information:
`Shared Control Information (SCI) Carrying Cat 1 Informa
`tion
`The SCI part of the L1/L2 control signaling contains infor
`mation related to the resource allocation (indication). The
`SCI typically contains the following information:
`User identity, indicating the user which is allocated
`RB allocation information, indicating the resources (Re
`source Blocks, RBs) on which a user is allocated. Note,
`that the number of RBs on which a user is allocated can
`be dynamic.
`Duration of assignment (optional), if an assignment over
`multiple sub-frames (or TTIs) is possible
`Depending on the setup of other channels and the setup of
`the Dedicated Control Information (DCI), the SCI may addi
`tionally contain information such as ACK/NACK for uplink
`transmission, uplink scheduling information, information on
`the DCI (resource, MCS, etc.).
`Dedicated Control Information (DCI) Carrying Cat 2/3 Infor
`mation
`The DCI part of the L1/L2 control signaling contains infor
`mation related to the transmission format (Cat 2) of the data
`transmitted to a scheduled user indicated by Cat 1. Moreover,
`in case of application of (hybrid) ARQ it carries HARQ (Cat
`3) information. The DCI needs only to be decoded by the user
`scheduled according to Cat 1.
`The DCI typically contains information on:
`Cat 2: Modulation scheme, transport-block (payload) size
`(or coding rate), MIMO related information, etc. (Note,
`either the transport-block (or payload size) or the code
`rate can be signaled. In any case these parameters can be
`calculated from each other by using the modulation
`Scheme information and the resource information (num
`ber of allocated RBS)).
`Cat3: HARQ related information, e.g. hybrid ARQ process
`number, redundancy version, retransmission sequence
`number.
`Details on L1/L2 control signaling information
`For downlink data transmissions L1/L2 control signaling is
`transmitted on a separate physical channel (PDCCH). This
`L1/L2 control signaling typically contains information on:
`The physical resource(s) on which the data is transmitted
`(e.g. subcarriers or subcarrier blocks in case of OFDM,
`codes in case of CDMA). This information allows the
`UE (receiver) to identify the resources on which the data
`is transmitted.
`The transport format, which is used for the transmission.
`This can be the transport block size of the data (payload
`size, information bits size), the MCS (Modulation and
`Coding Scheme) level, the Spectral Efficiency, the code
`rate, etc. This information (usually together with the
`resource allocation) allows the user equipment (re
`
`

`

`US 8,320,319 B2
`
`5
`
`10
`
`25
`
`35
`
`40
`
`45
`
`7
`ceiver) to identify the information bit size, the modula
`tion scheme and the code rate in order to start the
`demodulation, the de-rate-matching and the decoding
`process. In some cases the modulation scheme maybe
`signaled explicitly.
`Hybrid ARQ (HARQ) information:
`Process number: Allows the user equipment to identify
`the Hybrid ARQ process on which the data is mapped
`Sequence number or new data indicator: Allows the user
`equipment to identify if the transmission is a new
`packet or a retransmitted packet
`Redundancy and/or constellation version: Tells the user
`equipment, which hybrid ARQ redundancy version is
`used (required for de-rate-matching) and/or which
`modulation constellation version is used (required for
`demodulation)
`UE Identity (UEID): Tells for which user equipment the
`L1/L2 control signaling is intended for. In typical imple
`mentations this information is used to mask the CRC of
`the L1/L2 control signaling in order to prevent other user
`equipments to read this information.
`To enable an uplink packet data transmission, L1/L2 con
`trol signaling is transmitted on the downlink (PDCCH) to tell
`the user equipment about the transmission details. This L1/L2
`control signaling typically contains information on:
`The physical resource(s) on which the user equipment
`should transmit the data (e.g. Subcarriers or Subcarrier
`blocks in case of OFDM, codes in case of CDMA).
`The transport Format, the UE should use for the transmis
`sion. This can be the transport block size of the data
`(payload size, information bits size), the MCS (Modu
`lation and Coding Scheme) level, the Spectral Effi
`ciency, the code rate, etc. This information (usually
`together with the resource allocation) allows the user
`equipment (transmitter) to pick the information bit size,
`the modulation scheme and the code rate in order to start
`the modulation, the rate-matching and the encoding pro
`cess. In some cases the modulation scheme maybe sig
`naled explicitly.
`Hybrid ARQ information:
`Process number: Tells the user equipment from which
`Hybrid ARQ process it should pick the data
`Sequence number or new data indicator: Tells the user
`equipment to transmit a new packet or to retransmit a
`packet
`Redundancy and/or constellation version: Tells the user
`equipment, which hybrid ARQ redundancy version to
`use (required for rate-matching) and/or which modu
`lation constellation version to use (required for modu
`50
`lation)
`UE Identity (UEID): Tells which user equipment should
`transmit data. In typical implementations this informa