Claim 1 of ’629
`1. A method for
`assigning future
`slots of a
`transmission frame
`to a data packet in
`the transmission
`frame for
`transmission over
`a wireless
`medium,
`comprising:
`
`U.S. Patent No. 6,628,629
`T-Mobile & Ericsson Infringement Contentions
`Claims 1-4
`T-Mobile & Ericsson Infringement Contentions
`T-Mobile and Ericsson each directly infringe claim 1 under 35 U.S.C. § 271 (a) by literally performing every claimed
`method step.
`T-Mobile performs all steps of claim 1 and its dependent claims literally by making, installing, maintaining, configuring,
`testing, or operating a wireless telecom network in accordance with Long-Term Evolution (“LTE”) standards. The base
`stations in the T-Mobile network are Evolved Node-Bs (“eNodeB” or “eNB”) provided by Ericsson. See IVMN00008638-
`8640 (Ericsson Press Release, Sep. 23, 2014); IVMN00008641-42 (Ericsson Press Release, May 8, 2012);
`IVMN00008649-51 (T-Mobile Press Release, May 7, 2012). T-Mobile performs all steps either by itself, or by directing or
`controlling its subscribers.
`Ericsson performs all steps of claim 1 and its dependent claims literally by operating, maintaining, installing, or testing,
`wireless base stations, e.g., eNodeBs, in the T-Mobile network. See, e.g., IVMN00008638-8640 (Ericsson Press Release,
`Sep. 23, 2014); IVMN00008641-42 (Ericsson Press Release, May 8, 2012); IVMN00008649-51 (T-Mobile Press Release,
`May 7, 2012).
`Ericsson indirectly infringes claim 1 under 35 U.S.C. § 271 (b) by inducing T-Mobile to literally perform every
`claimed method step, and under 35 U.S.C. § 271 (c) by selling material or apparatus for use in practicing every
`claimed method step.
`Ericsson has induced, and continues to induce, T-Mobile to infringe claim 1 and its dependent claims, and has committed
`contributory infringement of claim 1 and its dependent claims by providing the hardware and software necessary for T-
`Mobile to perform the claimed method, along with instructions that induce T-Mobile to perform said method.
`Ericsson has taken, and continues to take, active steps to induce T-Mobile to infringe claim 1 and its dependent claims,
`knowing that those steps will induce, encourage, and facilitate direct infringement by T-Mobile. Such active steps are
`described in detail below and include, but are not limited to, configuring Ericsson eNodeBs to provide semi-persistent
`scheduling, providing instructions on the use of the semi-persistent scheduling feature, and participating in the construction,
`operation, and maintenance of the T-Mobile network specifically for the purpose of performing the claimed method.
`To the extent the preamble is found to be limiting, T-Mobile and Ericsson each perform a method conforming to the
`preamble language.
`
`Ericsson Exhibit 1011
`Page 1
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`OVERVIEW OF LTE NETWORK
`Figure 4.1-1 (below) shows an eNB connected to an Evolved Packet Core (“EPC”). TS 36.3001 § 4.1; TS 23.401 § 1.
`
`TS 36.300 § 4.1.
`An eNB communicates wirelessly with user equipment (“UE,” e.g., smart phones). TS 36.300 §§ 3.2, 4.1; TS 23.401
`§ 4.4.3.2; TR 21.905 §§ 3B, 3E, 3N. EPC components include: a signaling gateway (“S-GW”); a mobility management
`entity (“MME”); and a packet gateway (“P-GW”) that interfaces with packet data networks (“PDNs”) such as the Internet.
`TS 23.401 §§ 4.1 & 4.4; TS 36.300 § 4.1; TS 23.228 § 4. The eNB and UEs communicate via a protocol stack having
`physical (“PHY”), medium access control (“MAC”), radio link control (“RLC”), and packet data convergence protocol
`(“PDCP”) layers. TS 36.300 §§ 4 & 6. The eNB also operates a radio resource control (“RRC”) plane. Id.
`
`1 Citations to TR __.___ and TS __.___ refer to 3rd Generation Partnership Project (“3GPP”) LTE documentation listed in the Notice of Disclosure
`and Infringement Contentions served concurrently herewith. Unless a specific version is noted, the citation refers to the version listed in the
`Notice of Disclosure and Infringement Contentions. Where a section is cited, the citation refers to all subsections within that section.
`- 2 -
`
`Ericsson Exhibit 1011
`Page 2
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`OVERVIEW OF LTE RADIO TRANSMISSION SCHEMES AND RADIO RESOURCES
`The wireless transmissions between an eNodeB and UE include downlink (“DL”) transmissions (i.e., from an eNB to a UE),
`and uplink (“UL”) transmissions (i.e., from a UE to an eNB) organized in either of two frame structures: frequency division
`duplex (“FDD”), and time division duplex (“TDD”). TS 36.300 § 5. On information and belief, the T-Mobile network
`operates at least in accordance with FDD. Id. at §§ 5 & 5.1.1; TS 36.211 §§ 4 & 6. The FDD and TDD frame structures
`both divide frequency into subcarriers, and divide time into frames, subframes and slots. Id. As shown in Figure 5-1
`(below), each frame includes ten subframes, each subframe includes two slots, wherein each frame has a duration of 10ms,
`each subframe has a duration of 1ms, and each slot has a duration of 0.5ms. Id.
`
`TS 36.300 § 5.
`Figures 5.2.1-1 and 6.2.2-1 (below) show UL and DL resource grids, respectively. TS 36.211 §§ 5.1.1, 5.2.1, 5.6 & 6.2.2.
`Both grids plot time and frequency on horizontal and vertical axes, and both divide time into frames, subframes, and slots
`as described above. Id.; see also TS 36.300 § 5. Both grids also divide frequency into subcarriers, but they use different
`types of modulation. Id. Referring to Figure 6.2.2-1 (below), DL transmission uses orthogonal frequency division
`multiplexing (“OFDM”). Id. OFDM divides frequency into sub-carriers spaced 15 kHz apart. Id. The DL grid includes
`resource elements (“REs”) and resource blocks (“RBs”). Id. at § 6.2. Each RE includes one subcarrier for a duration of one
`symbol period. Id. Each RB contains 12 subcarriers for a duration of one slot. Id. When using a normal cyclic prefix2,
`each slot has seven symbols. Id. So, with a normal cyclic prefix, each RB has 84 REs (12 rows by 7 columns). Id.
`
`2 A cyclic prefix is part of an OFDM symbol. TS 36.211 §§ 4.1, 4.2 & 6.2.3. LTE transmission schemes use either a normal cyclic prefix (7 OFDM
`symbols per slot) or an extended cyclic prefix (6 OFDM symbols per slot). TS 36.300 § 5.1.1.
`- 3 -
`
`Ericsson Exhibit 1011
`Page 3
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`Referring to Fig. 5.2.2-1 (above), the UL resource grid also includes REs and RBs. TS 36.211 § 5.2. On information and
`belief, the T-Mobile network uses Single Carrier Frequency Division Multiple Access (“SC-FDMA”) modulation for uplink
`transmission. Id. at §§ 5.2. & 5.3. SC-FDMA divides frequency into sub-carriers spaced 15 kHz apart. Id. When using a
`normal cyclic prefix, each RB in the UL resource grid includes 84 REs (12 rows by 7 columns of REs). Id.
`OVERVIEW OF LTE PHYSICAL CHANNELS CARRYING DATA AND CONTROL MESSAGES
`The DL radio resources are used to transport downlink physical channels that are shared by multiple UEs communicating
`with a single eNB in the DL direction. Likewise, UL radio resources are used to transport uplink physical channels that are
`shared by the UEs to communicate with the eNB in the UL direction. TS 36.300 §§ 5, 6, 6.1 & 11; TS 36.211 § 6.2.1. The
`- 4 -
`
`Ericsson Exhibit 1011
`Page 4
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`eNB and UEs must exchange control messages in order to allocate resources (i.e., specified RBs) for transmitting data to
`and from UEs. Id. These resource allocations may be valid for one or more subframes, wherein each subframe corresponds
`to a transmission time interval (“TTI”) of one millisecond. See TS 36.300 §§ 5, 5.1.1 and 11. Physical channels used in
`LTE include:
`• physical downlink control channel (“PDCCH”) carrying control information sent from an eNB to one or more UEs,
`including downlink resource allocations, and uplink scheduling grants;
`• enhanced physical downlink control channel (“EPDCCH”) carrying control information sent from an eNB to a UE,
`including downlink resource allocations, and uplink scheduling grants;
`• physical downlink shared channel (“PDSCH”) carrying data sent from an eNB to one or more UEs;
`• physical uplink control channel (“PUCCH”) carrying control information sent from one or more UEs to an eNB; and
`• physical uplink shared channel (“PUSCH”) carrying data sent from one or more UEs to an eNB.
`TS 36.300 V12.0.0 § 5.
`Discussions in this document about resource allocation and grant control information sent on a PDCCH, or about a UE
`monitoring a PDCCH for control information, applies also to resource allocation and grant control information sent on an
`EPDCCH, when an EDPCCH is configured.
`LTE TRANSPORT CHANNELS, LOGICAL CHANNELS, AND RADIO BEARERS
`Figures 6-1 and 6-2 (below) show relationships between transport channels, logical channels, and radio bearers for
`downlink and uplink communications. TS 36.300 §§ 4.1 & 6.
`
`- 5 -
`
`Ericsson Exhibit 1011
`Page 5
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`TS 36.300 § 6.
`The MAC layer (above) transfers data (i.e., “transport blocks”) to and from the PHY layer (not shown). TS 36.300 §§ 4.3.1
`& 6. Transport channels provide data transfer services between the MAC and PHY layers. Id. Data flows between the
`MAC and RLC layers are referred to as “logical channels.” Id.
`Downlink data is transmitted on the PDSCH in units of transport blocks (“TBs”), each TB corresponding to a MAC layer
`protocol data unit (“PDU”). TS 36.300 §§ 5, 6.1.1 & 6.1.2. Uplink data is similarly transmitted on the PUSCH in units of
`TBs. TS 36.300 §§ 5, 6.1.1 & 6.1.2. “In both uplink and downlink, only one transport block is generated per TTI in the
`non-MIMO case.” TS 36.300 § 6. Transport blocks may be passed from the MAC to the PHY layer once per TTI. Id.; TR
`21.905 p. 28.
`GENERAL OVERVIEW OF LTE SCHEDULING
`In an eNodeB, the MAC layer includes downlink and uplink schedulers that allocate PHY layer resources for transport
`channels including a downlink shared channel (“DL-SCH”) and an uplink shared channel (“UL-SCH”). TS 36.300 § 11.1.
`“Different schedulers may operate for the DL-SCH and UL-SCH transport channels.” Id. The schedulers take account of
`quality of service (“QoS”) requirements of UEs and radio bearers. Id.
`OVERVIEW OF DOWNLINK SCHEDULING AND CONTROL CHANNELS
`The eNB performs downlink scheduling to determine resources (e.g., specified RBs) on PDSCH for transmitting data to
`UEs. TS 36.300 § 11.1.1. Each UE may read different portions of the PDSCH—specified by allocated resources—to
`receive downlink data. Id. at §§ 5.1.3 & 11.1.1; TS 36.211 §§ 6.3 & 6.4, TS 36.300 V12.0.0 § 5.1.3. When an eNB
`- 6 -
`
`Ericsson Exhibit 1011
`Page 6
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`transmits data to a UE, it sends a Downlink Control Information (“DCI”) message to the UE via the PDCCH, specifying
`resources (e.g., specified RBs) for a UE. TS 36.211 § 6.8; TS 36.211 V12.0.0 § 6.8A; TS 36.213 §§ 3, 7 & 7.1.6. Each UE
`monitors PDCCH for allocations. TS 36.211 § 6.2.1; TS 36.300 § 11.1.2. Formats of DCI messages indicating downlink
`resource allocation include “DCI format 1, 1A, 1B, 1C, 1D, 2, 2A, 2B, 2C, or 2D.” TS 36.213 V12.0.0 § 7.1.
`OVERVIEW OF UPLINK SCHEDULING AND CONTROL CHANNELS
`The eNB determines uplink resources (e.g., specified RBs) on the PUSCH to be used by UEs to transmit data to the
`eNodeB. TS 36.300 § 11.1.2; TS 36.211 § 6.2.1. Before a UE can send data to an eNodeB, it must obtain an uplink
`resource grant. TS 36.213 §§ 8, 8.1 & 8.4. An eNB issues an uplink resource grant by sending a DCI message to the UE
`on the PDCCH to specify a right for a UE to transmit data using specified RBs in future subframes. TS36.211 § 6.8; TS
`36.211 V12.0.0 § 6.8A; TS 36.213 §§ 8, 8.1 & 8.4; TS 36.213 §§ 3, 7 & 7.1.6. Each UE monitors PDCCH for grants. TS
`36.211 § 6.2.1; TS 36.300 § 11.1.2. Formats of DCI messages indicating uplink resource grants include DCI format 0 and
`format 4. TS 36.213 §§ 8.1 & 8.4; TS 36.212 § 5.3.3.1.1; TS 36.213 V10.0.0 §§ 8.0, 8.1 & 8.4; TS 36.213 V12.0.0 §§ 8.0,
`8.1 & 8.4; TS 36.212 V10.0.0 §§ 5.3.3.1.1 & 5.3.3.1.8; TS 36.212 V10.7.0 §§ 5.3.3.1.1 & 5.3.3.1.8.
`The eNB issues resource grants in response to a scheduling request (“SR”) and/or buffer status report (“BSR”) received
`from a UE. TS 36.321 §§ 5.4.4 & 5.4.5. A UE sends a BSR to an eNodeB on the PUSCH, either alone or along with
`uplink data using a prior resource grant. Id. at §§ 6.1.2 & 6.1.3.1. If the UE did not obtain a prior resource grant, it must
`send an SR to obtain one. TS 36.300 § 5. BSRs are “needed to provide support for QoS-aware packet scheduling.” Id. at
`§ 11.3.
`The Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data
`available for transmission in the UL buffers of the UE. TS 36.321 §§ 5.4.5 & 6.1.3.1. A BSR reports to an eNB which
`radio bearers need UL resources and how much resources they need. Id. By reading a BSR, an eNB is able to schedule the
`UE based on the QoS characteristic of the corresponding radio bearers and the reported buffer status. Id.
`LTE defines the concept of a “logical channel” as “an information stream dedicated to the transfer of a specific type of
`information over the radio interface.” TR 21.905, p. 18. BSRs reference logical channels in groups known as logical
`channel groups (“LCGs”). TS 36.321 §§ 5.4.5 & 6.1.3.1.
`Figures 6.1.3.1-1 and 6.1.3.1-2 (below) show two formats for BSR MAC control elements. TS 36.321 § 6.1.3.1.
`
`- 7 -
`
`Ericsson Exhibit 1011
`Page 7
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`Referring to the figures above, the LTE standards further explain:
`“Buffer Status Report (BSR) Control Elements consist of either:
` - Short BSR format: one [logical channel group] LCG ID field and one corresponding Buffer Size (“BS”) field
`(figure 6.1.3.1-1); or
` - Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2) …
`* * * * *
`The fields LCG ID and BS are defined as follows:
`- LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is
`being reported. The length of the field is 2 bits.
`- BS: The Buffer Size field identifies the total amount of data available across all logical channels of a logical
`channel group after the MAC PDU has been built. The amount of data is indicated in number of bytes ….”
`TS 36.321 § 6.1.3.1.
`
`[a] applying a
`reservation
`algorithm;
`
`The eNodeBs apply a reservation algorithm by invoking software that is used to reserve future slots for data packets
`according to the Semi-Persistent Scheduling Protocol (“SPS”). TS 36.321 § 5.1; TS 36.331 § 6.3;
`. The manner in which this is accomplished is complex and is
`
`described below.
`DYNAMIC SCHEDULING VERSUS SEMI-PERSISTENT SCHEDULING
`The uplink and downlink schedulers in Ericsson eNBs are configured to perform “dynamic scheduling” and “semi-
`persistent scheduling (“SPS”). TS 36.300 §§ 11.1 & 11.1.2; TS 36.321 §§ 5.1 & 5.10. A dynamic resource allocation or
`grant specifies RBs that may be used for one subframe during one TTI. Id. SPS differs from dynamic scheduling in that an
`SPS resource allocation or grant may be valid for more than one subframe and TTI. TS 36.321 §§ 5.1 & 5.10; TS 36.331
`§ 6.3.2. Ericsson eNBs are configured with the SPS option enabled. See, e.g., IVMN00008675-90 (3GPP TDocs written
`contribution 08-2007), IVMN00008691-8760 (Ericsson LTE L11 Training Program Course Catalog), IVMN00008761-
`8852 (Ericsson LTE L14 Training Program Course Catalog), IVMN00008853-55 (R2-073214 Aug 2007 Meeting Ericsson
`- 8 -
`
`
`
`Ericsson Exhibit 1011
`Page 8
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`Submission), IVMN00008856-58 (R2-073215 Aug 2007 Meeting Ericsson Submission),
`.
`
`.
`
`
`
`
`
`
`
`
`BEARER SET-UP
`LTE systems support many different types of communication services (typically corresponding to applications) including
`voice services, gaming services, video services, web services, and many others. TS 23.203 § 6.1.7;
`; see also IVMN00008946 (T-Mobile-One-End-
`of-Data-Plans). These different types of services have different requirements or tolerances with respect to transmission
`errors, delays and other characteristics collectively known as quality of service (“QOS”) parameters. Id.
`Before any data packet of an IP flow is transmitted uplink or downlink across the wireless interface between an eNB and a
`UE, the LTE system must first set up and configure a data bearer for transporting the IP data flow. TS 23.401 § 5.3.2; TS
`36.300 § 13.
`Bearers are established during an “attach procedure” utilizing an exchange of control messages between the UE, eNodeB,
`MME, S-GW, P-GW, policy charging and rules function (“PCRF”), and home subscriber server (“HSS”). TS 23.401
`§§ 3.1, 4.1, 5.3.2.1, 5.4.1; TS 36.413 §§ 8.2.1, 9.1 & 9.2.2.2; TS 36.300 § 19.2. One of the exchanged messages is described
`below:
`“18. The eNodeB sends the RRC Connection Reconfiguration message including the EPS Radio Bearer Identity to the
`UE, and the Attach Accept message will be sent along to the UE. The UE shall store the QoS Negotiated, Radio
`Priority, Packet Flow Id and TI, which it received in the Session Management Request, for use when accessing via
`GERAN or UTRAN. The APN is provided to the UE to notify it of the APN for which the activated default bearer is
`associated. For further details, see TS 36.331 [37]. The UE may provide EPS Bearer QoS parameters to the
`application handling the traffic flow(s) ….”
`TS 23.401 § 5.3.2.1.
`Downlink packets are received at the P-GW from packet data networks such as the Internet. TS 23.401 §§ 4.1 & 4.4; TS
`36.300 § 4.1; TS 23.228 § 4. Each downlink-bound packet received at the P-GW is part of a corresponding IP data flow
`being sent to a particular UE. TS 36.300 § 13.1 & 13.2; TS 23.401 §§ 4.7.2.2. The eNB, P-GW and S-GW include
`hardware and software configured to receive and analyze each data packet received from a PDN (e.g., the Internet) to
`determine which data flow it belongs to, and which bearer should be used to transport the packet to a destination UE. Id.
`The T-Mobile network also includes an MME, which provides “[b]earer management functions including dedicated bearer
`- 9 -
`
`Ericsson Exhibit 1011
`Page 9
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`establishment.” TS 36.300 § 4.1 and Fig. 4.1-1; TS 23.401 §§ 1 & 4.4.2.
`An eNB sends an RRC Connection Reconfiguration Message to a UE during bearer setup, configuration or reconfiguration.
`TS 23.401 § 5.3.2.1;
`. This message may
`include different information elements (“IEs”). Id. For example, this message may include a
`RadioResourceConfigDedicated IE as defined below:
`
`* * * * * *
`
`See TS 36.331 § 6.2 at p. 127-28.
`As shown above, the RadioResourceConfigDedicated IE may contain an SPS-Config IE, which specifies an SPS scheduling
`configuration as shown below.
`
`- 10 -
`
`Ericsson Exhibit 1011
`Page 10
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`TS 36.331 § 6.2 at pp. 130-31.
`As shown above, the SPS-Config IE may include: SPS subframe interval parameters (see “semiPersistSchedIntervalDL”
`and “semiPersistSchedIntervalUL”); and an SPS cell radio network temporary identifier (“C-RNTI”) (see “semiPersist
`SchedC-RNTI”) (hereinafter “SPS Parameters”). Id. As also shown above, each of the SPS intervals may assume a value
`selected from the set “sf10,” “sf20,” “sf32,” “sf40,” “sf64,” “sf80,” “sf128,” “sf160,” “sf320,” and “sf640,” corresponding
`to 10, 20, 32, 40, 64, 80, 128, 160, 320 or 640 subframes, respectively. Id. Selected interval values are stored in the
`eNodeB and UE, and later used by the eNodeB to schedule SPS resource allocations and grants. Id. Each SPS C-RNTI
`
`- 11 -
`
`Ericsson Exhibit 1011
`Page 11
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`value uniquely identifies a particular UE for SPS scheduling. TS 36.300 § 8.1; TS 36.321 § 5.10.
`The LTE standards further explain the SPS functionality in the table below:
`
`TS 36.331 § 6.2 at p. 131.
`Each IP flow transmitted in the downlink direction from the P-GW to a UE via the eNodeB is mapped to a corresponding
`bearer associated with certain QoS parameters. TS 36.300 §§ 11.1 & 13;
`
`. A service data flow (“SDF”) is an aggregate of IP traffic flows mapped to a
`radio bearer. TS 23.401 § 4.7. Each service flow is transmitted on its corresponding bearer in accordance with its
`corresponding “minimum level of QoS.” Id.; see also TS 23.303 § 6.1.7.2.
`The LTE standards explain:
`“An EPS bearer/E-RAB [radio bearer] is the level of granularity for bearer level QoS control … SDFs mapped to the
`same EPS bearer receive the same bearer level packet forwarding treatment (e.g. scheduling policy, queue management
`policy, rate shaping policy, RLC configuration, etc.) [17].
`“[A default bearer] … is established when the UE connects to a PDN … Any additional EPS bearer/E-RAB …
`established to the same PDN is referred to as a dedicated bearer. The initial bearer level QoS parameter values of the
`default bearer are assigned by the network, based on subscription data. The decision to establish or modify a dedicated
`bearer can only be taken by the EPC, and the bearer level QoS parameter values are always assigned by the EPC.
`“An EPS bearer/E-RAB is referred to as a GBR bearer if dedicated network resources related to a Guaranteed Bit Rate
`(GBR) value that is associated with the EPS bearer/E-RAB are permanently allocated …”
`TS 36.300 § 13.
`
`- 12 -
`
`Ericsson Exhibit 1011
`Page 12
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`“The standardized characteristics are not signalled on any interface. They should be understood as guidelines for
`the preconfiguration of node specific parameters for each QCI. The goal of standardizing a QCI with corresponding
`characteristics is to ensure that applications / services mapped to that QCI receive the same minimum level of QoS
`in multi-vendor network deployments and in case of roaming. A standardized QCI and corresponding
`characteristics is independent of the UE's current access (3GPP or Non-3GPP).”
`TS 23.303 § 6.1.7.2; see also TS 23.203 § 6.1.7; TS 23.401 §§ 4.7.2.2 & 5.3.2.1.
`Figure 13.1-1 (reproduced below) shows the EPS Bearer Service Architecture used in the T-Mobile network.
`
`TS 36.300 § 13.1.
`Referring to Figure 13.1-1 (above), LTE standards explain:
`“- An UL TFT [UL traffic flow template] in the UE binds an SDF to an EPS bearer in the uplink direction ...
`- A DL TFT in the PDN GW binds an SDF to an EPS bearer in the downlink direction ...
`* * * * * * *
`- An S1 bearer transports the packets of an E-RAB [radio bearer] between an eNodeB and a Serving GW [S-GW].
`- An S5/S8 bearer transports the packets of an EPS bearer between a Serving GW [S-GW] and a PDN GW [P-GW].
`- A UE stores a mapping between an uplink packet filter and a data radio bearer to create the binding between an SDF and
`a data radio bearer in the uplink.
`- A PDN GW stores a mapping between a downlink packet filter and an S5/S8a bearer to create the binding between an
`SDF and an S5/S8a bearer in the downlink.
`- An eNB stores a one-to-one mapping between a data radio bearer and an S1 bearer to create the binding between a data
`
`- 13 -
`
`Ericsson Exhibit 1011
`Page 13
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`radio bearer and an S1 bearer in both the uplink and downlink.
`- A Serving GW [S-GW] stores a one-to-one mapping between an S1 bearer and an S5/S8a bearer to create the binding
`between an S1 bearer and an S5/S8a bearer in both the uplink and downlink.”
`TS 36.300 § 13.1. See also TS 23.401 § 4.7.2.2.
`Still referring to Fig. 13.1-1 (above), the S1 and S5/S8 interfaces both use a General Packet Radio Service (“GPRS”)
`Tunneling Protocol for User Plane (“GTP-U”). TS 29.281 §§ 4, 5; TS 29.060 §§ 6, 7; TS 23.401 § 5. This protocol uses
`headers including Tunnel Endpoint Identifiers (“TEIDs”) to identify EPS bearers. TS 23.401 §§ 4.6.2.2, 5.2.1; TS 29.281
`§§ 5 & 5.1. Figure 4.7.2.2-1 (below) explains use of TFT’s and TEID values. Id.
`
`TS 23.401 § 4.7.2.2.
`Upon receiving a downlink packet from a PDN (e.g., the Internet), P-GW analyzes the packet’s header including “IP 5 tuple
`(source IP address, destination IP address, source port number, destination port number, protocol ID of the protocol above
`IP),” and uses its DL-TFT to map the packet to an EPS bearer. TS 23.203 §§ 6.1.7 & 6.2.2.2; TS 23.401 § 4.7.2.2. The P-
`GW adds a GTP-U header including an S5/S8 TEID to the packet, and forwards it to the S-GW. TS 29.281 §§ 4, 5;
`TS 29.060 §§ 5.1 & 7; TS 23.401 §§ 4.6.2.2, 5.2.1. S-GW removes and analyzes the S5/S8 TEID, and then adds a GTP-U
`header with an S1-TEID before sending the packet to the eNB. TS 29.281 §§ 4-5; TS 29.060 §§ 6, 7. The eNB then uses
`S1 TEID to determine a specific radio bearer. TS 29.281 §§ 4-5; TS 29.060 §§ 6-7; TS 23.401 § 5. Finally, the eNB uses
`the radio bearer with its corresponding QoS requirements to transport the packet to the destination UE. TS 36.300 § 13.1.
`Similarly, when a UE has a packet to transmit (e.g. from a voice or video application running on the UE), an uplink traffic
`flow template in the UE associates that packet with an EPS bearer in the uplink direction. Id.; TS 23.401 § 4.7.2.2. When
`- 14 -
`
`Ericsson Exhibit 1011
`Page 14
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`the eNB receives the packet, it uses a stored mapping from radio bearers to uplink S1-TEID values to add a GTP-U header
`with an uplink S1-TEID. Id.; TS 29.060 §§ 6-7; TS 29.281 §§ 4-5. It then sends the packet with the S1-TEID to the S-GW.
`Id. The S-GW removes and analyzes the S1-TEID, and then adds a GTP-U header with an S5/S8 TEID before sending the
`packet to the P-GW. Id.
`APPLICATION OF QUALITY OF SERVICE PARAMETERS
`As mentioned, each eNodeB, has downlink and uplink schedulers that take account of quality of service (“QoS”)
`requirements of UEs and radio bearers when scheduling packets for transmission across the wireless interface between the
`eNodeB and each UE. Id.; TS 36.300 § 11.1.
`
`
`
`
`
`
`Each bearer has an associated “EPS bearer QoS profile” including a QoS Class Identifier (“QCI”) parameter, which is used
`to “access node-specific parameters that control bearer level packet forwarding treatment (e.g. scheduling weights,
`admission thresholds, queue management thresholds, link layer protocol configuration, etc.).” TS 23.401 § 4.7.3. Each
`eNodeB considers QOS parameters including QCI values when making resource allocation and scheduling decisions. TS
`36.300 §§ 11.1 & 13; TS 23.401 § 4.7.3;
`; TS
`36.300 §§ 11.1 & 13; TS 23.401 § 4.7.3. A QCI value is assigned to a bearer when the bearer is established and indicates:
`(a) a priority level for that bearer relative to other bearers with other QCI values; (b) a target packet delay budget (c) a
`target packet error loss rate; (d) whether a bearer is to be provided a guaranteed bit rate (“GBR”) or a non-guaranteed bit
`rate (non-GBR) service; and (e) an application or service type for which the QCI value is assigned (voice, web/email traffic,
`etc.) TS 23.203 § 6.1.7. Each bearer is assigned QoS parameters including a QCI parameter, which is associated with a tier
`or level of service. Id.
`Table 6.1.7 (below) shows QCI values associated with different Services (i.e., application types) and QoS parameters (i.e.,
`Priority, Packet Delay Budget and Packet Error Loss Rate) associated with each QCI value. TS 23.203 § 6.1.7.
`
`- 15 -
`
`Ericsson Exhibit 1011
`Page 15
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`Each QCI value has an associated “priority” level, with level “1” being the highest. Id. The eNB schedulers use the QCI
`and other QoS parameters associated with each bearer to determine priorities (scheduling weights) of bearers for allocating
`resources. TS 23.401 § 4.7.3; TS 36.300 § 11.1;
`
`.
`As shown in Table 6.1.7 (above), priority level “1” is assigned to an IP multimedia subsystem signaling (“IMS Signaling”)
`service associated with QCI number 5, which may be used to control signaling to establish, modify, or end a voice call. TS
`23.203 § 6.1.7; IVMN00008586-92 (Validating voice over LTE end-to-end, Ericsson Review, 2012) at p. 7. Priority level
`“2” is assigned to “Voice” services such as voice over LTE (“VoLTE”) audio data flows associated with QCI number 1. Id.
`
`
`
`
`
`
`
`
`- 16 -
`
`
`
`
`
`
`
`Ericsson Exhibit 1011
`Page 16
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`T-MOBILE AND ERICSSON USE SPECIFIC QCI MAPPINGS FOR VOLTE CALLS
`
`
`
`
`
`
`
`
`
`
`
`
`
`TS 23.203 § 6.1.7.2.
`
`As mentioned, the Buffer Status reporting procedure provides a serving eNB with information about the amount of data
`available for transmission in the UL buffers of the UE. TS 36.321 §§ 5.4.5 & 6.1.3.1. A BSR informs the eNB which radio
`bearers need UL resources and how much of the available resources they need. Id. By reading a BSR, an eNB is able to
`schedule the UE based on the QoS characteristics of the corresponding radio bearers and the reported buffer status. Id.
`In the uplink direction, bearers are grouped into Logical Channel Groups (“LCGs”). TS 36.321 §§ 5.4.5 & 6.1.3.1. The
`local channel groups are established for each UE by exchanging control messages—including the RRC Connection
`Reconfiguration Message—between the eNB and UE. Id.; see also TS 36.331 § 6.2. The eNB and UE store information
`describing the logical channel groupings for each UE. Id. An IE carried by the RRC Connection Reconfiguration Message
`is the DRB-ToAddMod IE (below), which contains another IE called “logicalChannelConfig.” TS 36.331 § 6.2 at p. 127-
`28. As shown below, the LogicalChannelConfig IE includes a parameter called “logicalChannelGroup,” which takes on a
`value of 0, 1, 2, or 3, and specifies the LCG to which a bearer will be assigned. Id.
`
`- 17 -
`
`Ericsson Exhibit 1011
`Page 17
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`Id.
`Further details of the LogicalChannelConfig IE are shown below. TS 36.331 § 6.2 at p. 116.
`
`
`
`
`
`
`
`
`Id.
`
`- 18 -
`
`Ericsson Exhibit 1011
`Page 18
`
`

`

`Claim 1 of ’629
`
`T-Mobile & Ericsson Infringement Contentions
`
`ERICSSON ENODEBS APPLY SEMI-PERSISTENT SCHEDULING TO VOICE DATA FLOWS
`As mentioned, LTE supports SPS in which a downlink resource allocation or uplink grant is valid for more than one
`subframe. See TS 36.321 § 5.1; TS 36.331 § 6.3.2.
`Ericsson eNodeBs use SPS for voice data flows—including voice over IP (“VoIP”) and VoLTE—as follows:
`“Semi persistent scheduling
`› Every VoIP packet is received / sent every 20ms when the user is talking.
`› in silence period, discontinuous transmission (DTX) is used to reduce the transmission rate. Also, in order to sustain
`voice quality, silent insertion descriptor (SID) packet arrives every 160ms.
`› The frequent arrival/transmission of VoIP packet means large control overhead for lower layers (L1/L2) in the radio
`protocol stack.
`› In case of semi persistent scheduling, eNB can assign predefined chunk of radio resources for VoIP users with
`interval of 20ms. Therefore, UE is not required to request resources each TTI, saving control plan overhead. This
`scheduling is semi-persistent in the sense that eNB can change the resource allocation type or location if required for
`link adaptation or other factors.
`› SPS can be used in UL and DL”
`See IVMN00008859-939 (Volte RAN Features Session-2, Ericsson, 2011) at p. 44.
`UPLINK SEMI-PERSISTENT SCHEDULING
`As discussed above, each BSR sent by a UE to an eNodeB includes: one or more LCGs, each LCG identifying a group of
`logical channels (i.e., bearers); and a buffer size field for each LCG. TS 36.321 § 6.1.3.1. The buffer size field identifies
`the total amount of data (in bytes) waiting to be sent by the UE to the eNodeB for all logical channels in the corresponding
`- 19 -
`
`Ericsson Exhibit 1011
`Page 19
`
`

`

`Claim 1 of ’629
`
`LCG. Id.
`
`T-Mobile & Ericsson Infringement Contentions
`
`
`
`
`As mentioned, an eNB sends DCI messages on the PDCCH t