`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`______________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`______________
`
`SAMSUNG ELECTRONICS CO., LTD., AND
`SAMSUNG ELECTRONICS AMERICA, INC.,
`Petitioners
`v.
`
`EVOLVED WIRELESS, LLC
`Patent Owner
`______________
`
`Case IPR2016-01345
`Patent 7,881,236
`______________
`
`
`
`
`PATENT OWNER’S PRELIMINARY RESPONSE TO
`PETITIONERS’ PETITION FOR INTER PARTES REVIEW OF
`UNITED STATES PATENT NO. 7,881,236
`
`
`
`
`IPR2016-01345
`
`TABLE OF CONTENTS
`
`I.
`Introduction ........................................................................................................ 1
`II. The State of the art ............................................................................................. 2
`A. Mobile telephony and LTE ......................................................................... 2
`B. Identifying radio resources ......................................................................... 5
`C. Base station communicates the radio resources it has allocated to a
`UE with uplink grants ................................................................................. 6
`D. A UE having new data to upload, but lacking radio resources
`sufficient for the upload, uses the random access procedure to obtain
`the resources ................................................................................................ 7
`III. The claims ........................................................................................................ 11
`A. Independent claim 1 .................................................................................. 11
`B. Independent claim 7 .................................................................................. 13
`IV. Claim Construction .......................................................................................... 14
`A. Claim 1 ...................................................................................................... 15
`1. The claim language, properly read, excludes the possibility of
`transmitting new data along with the Msg3 buffer data .................... 15
`2. Petitioners’ claim construction is highly suspect because it claims
`an inoperative method ........................................................................ 18
`3. ZTE’s arguments all fail .................................................................... 19
`a. Petitioners improperly dissect differences in meaning between
`“only if” and “if” ......................................................................... 19
`b. Petitioners’ other arguments fail, too .......................................... 20
`4. The broadest reasonable construction for claim 1 must be
`consistent with the expressio unius principle .................................... 23
`B. Claim 7 ...................................................................................................... 23
`1. The broadest reasonable construction for claim 7 must be
`consistent with the expressio unius principle .................................... 25
`V. Petitioner’s argument that the 321 reference teaches limitation 1(e) is wrong,
`even using Petitioners’ unreasonable claim construction ........................................ 26
`VI. The petition is wholly redundant ...................................................................... 28
`VII. The claims, using the broadest reasonable construction, are not obvious ....... 28
`
`
`
`- i -
`
`
`
`
`
`
`
`IPR2016-01345
`
`A. Petitioners’ argument that the 320 reference teaches not transmitting
`the Msg3 buffer data along with the new data fails because it is
`based on a logical error ............................................................................. 29
`B. Petitioners failed to address the proper construction of limitation
`1(e), and then failed to find that limitation in the prior art, so Ground
`1 fails for this additional reason ................................................................ 33
`C. Petitioners address neither the proper construction of limitation 7(e)
`nor 7(g), and then failed to find those limitations in the prior art, so
`Ground 2 fails ........................................................................................... 33
`D. Petitioners’ simultaneous development argument is irrelevant and
`wrong ........................................................................................................ 34
`Conclusion ................................................................................................ 35
`
`VIII.
`
`- ii -
`
`
`
`
`
`
`
`
`
`
`
`
`
`TABLE OF AUTHORITIES
`
`IPR2016-01345
`
` Page(s)
`
`Cases
`AIA Eng’g Ltd. v. Magotteaux Int’l S/A,
`657 F.3d 1264 (Fed. Cir. 2011) .......................................................................... 18
`
`Chef Am., Inc. v. Lamb-Weston, Inc.,
`358 F.3d 1371 (Fed. Cir. 2004) .......................................................................... 20
`
`Chevron USA Inc. v. Echazabal,
`536 U.S. 77 (2002) .............................................................................................. 16
`
`Despoir, Inc. v. Nike USA, Inc.,
`2005 U.S. Dist. LEXIS 10845 (N.D. Ill. Feb. 9, 2005) ...................................... 16
`
`In re Cuozzo Speed Techs., LLC,
`793 F.3d 1268 (Fed. Cir. 2015), aff’d, 136 S. Ct. 2131 (2016) .......................... 14
`
`In re Magnum Oil Tools Int’l, Ltd.,
`2016 U.S. App. LEXIS 13461 (Fed. Cir July 25, 2016) .................................... 34
`
`Par Pharm., Inc. v. TWi Pharms., Inc.,
`
`773 F.3d 1186 (Fed. Cir. 2014) .......................................................................... 27
`
`PPC Broadband, Inc. v. Corning Optical Communs. RF, LLC,
`815 F.3d 747 (Fed. Cir. 2016) ...................................................................... 19, 20
`
`Pods, Inc. v. Porta Stor, Inc.,
`484 F.3d 1359 (Fed. Cir. 2007) .......................................................................... 21
`
`Shenyang Yuanda Aluminum Industry Eng’g. v. United States,
`776 F.3d 1351 (Fed. Cir. 2015) .......................................................................... 15
`
`Unified Patents, Inc. v. PersonalWeb Techs., LLC,
`Case No. IPR2014-00702, Paper 13 (PTAB July 24, 2014) .............................. 28
`
`
`Statutes
`
`35 C.F.R. § 42.107 ..................................................................................................... 1
`
`
`
`
`- iii -
`
`
`
`
`
`
`35 U.S.C. § 325 .................................................................................................... 1, 28
`35 U.S.C. § 325 .................................................................................................. ..1, 28
`
`
`IPR2016-01345
`
`IPR2016—01345
`
`
`
`- iv -
`
`_iV_
`
`
`
`
`
`IPR2016-01345
`
`Pursuant to 37 C.F.R. § 42.107, Patent Owner Evolved Wireless, LLC
`
`submits this Preliminary Response to the above-captioned Petition for Inter Partes
`
`Review of U.S. Patent No. 7,811,236 (“Pet.,” Paper 1).
`I.
`
`Introduction
`
`The Petition fails to establish a reasonable likelihood that Petitioners would
`
`prevail with respect to any claim challenged in the Petition. The Board need not
`
`reach the merits, however, because the present Petition presents exactly the same
`
`art and arguments that are already before the Board in IPR2016-00757, and the
`
`Board should therefore exercise its discretion to reject the present Petition under 35
`
`U.S.C. § 325(d).
`
`Turning to substantive issues, the Petition has many failings. First, the
`
`Petition offers unreasonably broad constructions for one limitation of the
`
`independent claims of U.S. Patent No. 7,811,236 (the “’236 patent”). Second, the
`
`Petition fails to apply the reasoning it used to come up with the first limitation’s
`
`construction to a second limitation. Then, the Petition fails to show how this
`
`second limitation is rendered obvious. For this reason alone, after construing the
`
`claims, the Board should deny the Petition.
`
`Perhaps recognizing the unreasonableness of its proposed construction, the
`
`Petition also offers a narrower construction, but the Board should deny the Petition
`
`under this construction too. This is because Petitioners’ argument that Exhibit 1002
`
`(“the 320 reference”) fills the gap in its primary reference (“the 321 reference”) is
`
`incorrect. The 320 reference shows only a simple case in the random access
`
`procedure that is at issue, and because the reference does not consider more
`
`
`
`- 1 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`complex cases (cases that the ’236 patent inventors did consider), the conclusion
`
`Petitioners drew from it is unsupported.
`
`Finally, even using Petitioners’ unreasonably broad construction, the Petition
`
`fails to demonstrate that the 321 reference teaches a claim element present in all
`
`grounds. Indeed, that reference, which allegedly discloses the two conditions
`
`required for transmitting the claimed buffer data, does not explicitly or inherently
`
`disclose this claim limitation. As such, all grounds should be denied.
`
`Accordingly, after the Board makes the correct, broadest reasonable
`
`construction, the Petition should be wholly denied.
`II. The State of the art
`A. Mobile telephony and LTE
`This section reviews the scope of the prior art. This review is mandated by
`
`Graham, because Petitioner’s grounds all rely on obviousness.
`
`Mobile telephony systems are divided into three parts. Ex. 1001 at 1:33-41.
`
`First, there are mobile phones, also called “user equipment” (“UE”). Id. Second are
`
`base stations, sometimes called “eNode B” or “Node B.” Id. Third is the core
`
`network. Id. Figure 1 from the ’236 patent shows these three parts.
`
`
`
`- 2 -
`
`
`
`
`
`
`
`
`
`IPR2016-01345
`
`Figure 1 (Ex. 1001 at 3 (sheet 1))
`
`Figure 2, below, also shows these three parts, and further shows that a mobile
`
`UE can communicate with more than one base station. In mobile telephony
`
`systems, a UE can move across a geographic region, at one time carrying out a
`
`two-way conversation with one base station and at a later time carrying out a two-
`
`way conversation with another base station. See Ex. 1036 at 5.
`
`
`
`Figure 2 (Ex. 20011 at 30)
`
`
`1 Ex. 2001 contains portions of the Dahlman textbook, Ex. 1036, that Petitioners
`did not cite.
`
`
`
`- 3 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`At the time of the invention, in 2008, the telecommunications industry was
`
`developing the cellular standard now known as Long Term Evolution (“LTE”).
`
`Pet. at 8. The LTE standard was finalized in December 2008, and the first publicly
`
`available LTE service was launched in December 2009. Ex. 2002 at 1-2.
`
`LTE systems did not simply spring into existence in 2008-2009, however.
`
`The development of LTE began in 2004. Ex. 2001 at 20. Development of LTE
`
`took place in a standard-setting organization called the Third Generation
`
`Partnership Project (“3GPP”), where members from virtually every
`
`telecommunications company and organization in the world, including Petitioner
`
`Samsung Electronics Co., Ltd., contributed. Pet. at 8; Ex. 1033 at 1-2. The 3GPP
`
`organized many working groups, each to develop the LTE standard. Pet. at 8.
`
`Documents these working groups created are Petitioners’ primary references,
`
`Exhibits 1002 and 1003. One working group relevant here was “WG2,” which
`
`helped define how a UE would initially access a base station. Ex. 1016 at ¶¶ 36-37.
`
`Critical to this was defining a “random access procedure” in which a base station
`
`could learn two important facts:
`
`1. The fact that a UE–perhaps a UE with which the base station had no
`previous communication–had new data to transmit to the base station.
`2. How much new data the UE had to transmit.
`
`Ex. 1003 at 21 (§ 5.4.5). With that information known, the base station is ready to
`
`receive the UE’s new data. How the LTE standard permitted the base station to
`
`learn these facts will be discussed below. When these facts are known, the base
`
`station can allocate “radio resources” to a UE.
`
`
`
`- 4 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`B.
`Identifying radio resources
`The ’236 patent relates to the allocation of radio resources to UEs. See Ex.
`
`1001 at 4:18-30. More specifically, the patent relates to allocations of radio
`
`resources for uploads. Id. An upload is transfer of data from the UE “up” to a base
`
`station, the data then being sent over the core network to a final destination(s). Id.
`
`at 4:42-47.
`
`Radio resources include the times and frequency bands a UE may use to send
`
`its data to a base station. See, e.g., Ex. 1003 at 7. Figure 3, below, shows radio
`
`resources assigned to two UEs. Each UE uses resource blocks that do not overlap
`in the time/frequency domain.
`
`
`
`Figure 3 (Ex. 2001 at 81)
`
`A base station must assign radio resources to UEs judiciously, accounting for
`
`the volume of data to be uploaded and that data’s priority. Ex. 2001 at 79. For
`
`example, if a base station assigned too many resources to one UE, then other UEs
`
`might be unable to operate adequately. Id. at 80. Similarly, if too many frequency
`
`bands were assigned to low priority data, then there might be insufficient radio
`
`resources to assign to UEs that had generated new, high priority data. Id. More
`
`
`
`- 5 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`specifically, for example, a base station may try not to run out of resources for
`
`voice calls, as voice calls can be easily disrupted in “high latency” situations. Id;
`
`see also Ex. 1002 at 25 (§ 5.2.7.1).
`
`To minimize latency, then, a base station should know how much new data
`
`the UEs in its cell have generated and stored for upload. Base stations that know
`
`how much new data is waiting to be uploaded by all the UEs with which they are
`
`in communication are able to identify the resources appropriate for each. Ex. 2001
`
`at 79-81.
`
`Once a base station has determined a suitable allocation of resources, it must
`
`communicate these resources to the UEs. This is the subject of the next section.
`
`Once the UEs know which resources each may use, each may carry out two-way
`
`communications with a base station, with each UE receiving an allocation,
`
`transmitting its data, receiving a new allocation, and so on until the UE is out of
`
`data.
`
`C. Base station communicates the radio resources it has allocated to a
`UE with uplink grants
`As a general matter, for LTE uploads, the base station transmits the
`
`allocations it has made through uplink grants (“UL Grant”). Ex. 1001 at 4:18-21.
`
`Each UL Grant contains the time(s) and frequency band(s) a UE may use to
`
`transmit its data. Id. at 4:21-26. There are two ways to provide UL Grants. Id.
`
`The first type of UL Grant is a message contained in a random access
`
`response. Id. at 5:14-17. UL Grants contained in random access responses are used
`
`by base stations when, for example, the UE is not in the midst of an ongoing two-
`
`
`
`- 6 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`way communication with the base station. Id. at 3:45-51. One example of this
`
`situation includes a UE’s initial access to a base station in a handover procedure.
`
`Id. at 3:49-50.
`
`Non-random access UL Grants are the second type of UL Grant. Id. at 5:9-11.
`
`One example is grants contained in a PDCCH communication. Id. The PDCCH
`
`(Physical Downlink Control Channel) is a radio channel used by base stations to
`
`deliver UL Grants once the base station has identified the specific UE to which it
`
`directs the UL Grant. See id. at 3:20-31. Non-random access UL Grants are grants
`
`contained in a PDCCH communication. UL Grants contained in a PDCCH
`
`communication are sent periodically by the network to provide opportunities for
`UEs to send, for example, Buffer Status Reports.2 See Ex. 1002 at 62 and Ex. 1003
`at 18.
`
`D. A UE having new data to upload, but lacking radio resources
`sufficient for the upload, uses the random access procedure to obtain
`the resources
`The prior art random access procedure enabled a UE that had no ongoing
`
`communication with a base station, but that had generated new data, to acquire
`
`radio resources for the upload. Ex. 1001 at 11:22-47. As previously discussed, in
`
`this circumstance the UE must first send two facts to the base station: 1) the fact
`
`that the UE has new data; and 2) how much new data it has to upload.
`
`
`2 By referring to non-random access UL Grants as PDCCH, Patent Owner does not
`represent that all non-random access UL Grants are delivered on the PDCCH.
`
`
`
`- 7 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`As explained by the ’236 patent, at least in a simple case, the prior art random
`
`access procedure requires four transmissions to be successfully transmitted before
`
`the UE can upload its new data to the base station for delivery to the ultimate
`
`recipient. Id. at 8:38-9:47. These four transmissions are illustrated in Figure 3. Id.
`
`at 6 (sheet 4). They are 1) the random access preamble; 2) the random access
`
`response; 3) the scheduled transmission; and 4) the contention resolution message.
`
`Figure 4 shows these same four messages, using different nomenclature. Ex. 1036
`
`at 10. (Figure 3’s Scheduled Transmission and the Contention Resolution messages
`
`are called “RRC Signaling” in Figure 4). Importantly, Figure 4 shows when new
`
`data (called “user data” in Figure 4) is transmitted with respect to the four
`
`messages shown in Figure 3’s random access procedure. It is the delivery of the
`
`new data/user data that is the ultimate goal of the UE that performed a random
`
`access procedure.
`
`
`
`
`
`
`
`
`
`- 8 -
`
`
`
`
`
`Figure 3 (Ex. 1001 at 6 (sheet 4))
`
`Figure 4 ( Ex. 1036 at 10)
`
`The four messages involved in the random access procedure each have unique
`
`IPR2016-01345
`
`
`
`
`
`purposes.
`
`The first of the four messages is a random access preamble. If a UE has high
`
`priority data (“new data”) to upload to the base station but it lacks radio resources
`
`for the new data, then it sends a random access preamble to the base station. Id. at
`
`8:41-47. In sending the random access preamble to the base station, then, the UE
`
`has delivered the first of the two important facts identified above.
`
`The second of the four messages is an UL Grant contained in a random access
`
`response. Successful receipt of this UL Grant by the UE triggers the UE to send the
`
`third message to the base station, as the UE now knows that the base station is
`
`aware that it has new data awaiting upload. Ex. 1001 at 8:48-9:5.
`
`The third of the four messages is the Scheduled Transmission. The Scheduled
`
`Transmission conveys information to the base station about how much new data
`
`the UE has to upload to the base station. Id. at 11:38-43; Ex. 1002 at 62. This
`
`information is often in the form of a buffer status report (“BSR”). Ex. 1001 at
`
`11:39-41. It is also referred to as the data stored in the message 3 buffer, or the
`
`“Msg3 buffer data.” Id. at 11:52-59. In sending the Scheduled Transmission/Msg3
`
`Buffer data to the base station, then, the UE has delivered the second of the two
`
`important facts identified above. But before the UE uploads the new data, it must
`
`receive an UL Grant sufficient for its data.
`
`The last of the four messages is the Contention Resolution (“CR”) message.
`
`The CR message serves two functions. First, the CR message is to permit each UE
`
`
`
`- 9 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`receiving it to recognize that the CR message was, or was not, directed to it. Ex.
`
`2001 at 94, 98-100. Second, the CR message contains an UL Grant sufficient for
`
`the new data the UE has to upload. Ex. 1003 at 14. Importantly, and in
`
`contradistinction to the UL Grant in the second message, the UL Grant that is part
`
`of the CR message is sent on the PDCCH channel, and is not sent in a random
`
`access response. Id. In other words, for example, even if two UEs both initiated a
`
`random access procedure using the same random access preamble, the CR message
`
`enables the correct UE to determine that the UL Grant is for its new data, and
`
`enables the other UE to determine that the UL Grant is not for its new data. In such
`
`a way, contentions between different UEs (simultaneous transmissions in the same
`
`frequency channels) are avoided.
`
`After the last of the four messages in the random access procedure is
`
`successfully received, the UE is finally able to upload its new data to the base
`
`station as illustrated in Figure 4, above.
`
`What is critical to note about the prior art—and the ’236 patent did not
`
`change this—is that the uploading of new data required two separate transmissions
`
`by the UE (not counting the preamble’s transmission):
`
`1. First, the UE sent the Scheduled Transmission, which delivered the
`buffer status report to the base station.
`
`
`2. Second, occurring after the Scheduled Transmission and separated
`from it by the UE’s reception of the CR message, the UE sent the
`new data to the base station.
`
`
`
`- 10 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`The Scheduled Transmission and the new data are transmissions that go hand
`
`in hand with each other: The former enables the base station to allocate radio
`
`resources for the latter’s transmission.
`
`Also critical to note about the prior art—and not changed by the ’236
`
`patent—is that the two separate UE transmissions just noted were each responsive
`
`to their own UL Grant. One UL Grant authorized the base station to transmit the
`
`Scheduled Transmission and a second UL Grant authorized the base station to
`
`upload its new data.
`III. The claims
`A.
`Independent claim 1
`
`Claim 1 reads as follows:
`
`1.
`
`1(b)
`
`A method of transmitting data by a user equipment through an uplink,
`the method comprising:
`receiving an uplink grant (UL Grant) signal from a base station on a
`specific message;
`1(c) determining whether there is data stored in a message 3 (Msg3) buffer
`when receiving the UL Grant signal on the specific message;
`1(d) determining whether the specific message is a random access response
`message;
`transmitting the data stored in the Msg3 buffer to the base station using
`the UL Grant signal received on the specific message, if there is data
`stored in the Msg3 buffer when receiving the UL Grant signal on the
`specific message and the specific message is the random access
`response message; and
`transmitting new data to the base station in correspondence with the
`UL Grant signal received on the specific message, if there is no data
`stored in the Msg3 buffer when receiving the UL Grant signal on the
`specific message or the specific message is not the random access
`response message.
`Ex. 1001 at 16:50-17:3 (emphasis added).
`
`1(e)
`
`1(f)
`
`A number of observations about claim 1 are relevant.
`
`
`
`- 11 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`First, reading the claim in light of the patent specification, claim 1 refers to
`
`the Scheduled Transmission as the transmission of “data stored in a message 3
`
`(Msg3) buffer.” Id. at 4:11-14. Also, claim 1’s reference to a specific message can
`
`in limitation 1(d) refer to either of the two types of UL Grant: in limitation 1(e) a
`
`UL Grant provided in a random access response is required, and in limitation 1(f)
`
`one provided in a PDCCH UL Grant is required.
`
`Second, limitations 1(e) and 1(f) both depend on a condition, here called
`
`Condition X. Condition X is the underlined language in limitations 1(e) and 1(f)
`
`copied above. It is this:
`
`Condition X–is there data stored in the Msg3 buffer when
`
`receiving the UL Grant signal on the specific message
`
`and the specific message is the random access response
`
`message?
`
`Using the Condition X language, limitations 1(e) and 1(f) read:
`transmitting the data stored in the Msg3 buffer to the base station using the
`UL Grant signal received on the specific message, if Condition X is met;
`and
`transmitting new data to the base station in correspondence with the UL
`Grant signal received on the specific message, if Condition X is not met.
`Evidently, these two limitations are of the form “If X, then do one thing, but if
`
`1(e)
`
`1(f)
`
`
`
`not X, do the other thing.” This simple observation is relevant to the claim
`
`construction.
`
`Finally, it is notable that one cannot simply perform the claimed steps 1(a)
`
`through 1(f) seriatim and transmit data in the message3 buffer and also transmit the
`
`new data. That is because claim 1 contemplates the receipt of only one uplink
`
`
`
`- 12 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`grant: the claim refers in limitation 1(b) to “an uplink grant . . . on a specific
`
`message” and limitations 1(c)-(f) then refer to “the UL Grant signal on the specific
`
`message.” And, as noted above at § II.D (page 11), two uplink grants must be
`
`received in order to transmit both the data stored in the Msg3 buffer (i.e., make the
`
`Scheduled Transmission) and the new data. Thus, making one pass through the
`
`steps of claim 1 is insufficient to transmit the Msg3 buffer data and to transmit the
`
`new data. This observation is relevant to whether Petitioners’ claim construction is
`
`operative (it is not).
`
`B.
`Independent claim 7
`Claim 7, the only other independent claim in the ’236 patent, reads as follows:
`
`
`A user equipment, comprising:
`7.
`7(b) a reception module adapted to receive an uplink grant (UL Grant) signal
`from a base station on a specific message;
`7(c) a transmission module adapted to transmit data to the base station using the
`UL Grant signal received on the specific message;
`7(d) a message 3 (Msg3) buffer adapted to store UL data to be transmitted in a
`random access procedure;
`7(e) a Hybrid Automatic Repeat Request (HARQ) entity adapted to determine
`whether there is data stored in the Msg3 buffer when the reception module
`receives the UL Grant signal and the specific message is a random access
`response message, acquiring the data stored in the Msg3 buffer if there is
`data stored in the Msg3 buffer when the reception module receives the UL
`Grant signal and the specific message is the random access response
`message, and controlling the transmission module to transmit the data stored
`in the Msg3 buffer to the base station using the UL Grant signal received by
`the reception module on the specific message; and
`7(f) a multiplexing and assembly entity used for transmission of new data,
`7(g) wherein the HARQ entity acquires the new data to be transmitted from the
`multiplexing and assembly entity if there is no data stored in the Msg3
`buffer when the reception module receives the UL Grant signal on the
`specific message or the received message is not the random access response
`message, and controls the transmission module to transmit the new data
`acquired from the multiplexing and assembly entity using the UL Grant
`signal received by the reception module on the specific message.
`
`
`
`- 13 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`Ex. 1001 at 17:30-18:7. There are many similarities between the method claim 1
`
`and the apparatus claim 7. In the next section, Patent Owner will identify some of
`
`these similarities and point out how Petitioners’ proposed claim construction
`
`ignores them.
`
`
`
`IV. Claim Construction
`
`The Board gives each claim “its broadest reasonable construction in light of
`
`the specification of the patent in which it appears.” In re Cuozzo Speed Techs.,
`
`LLC, 793 F.3d 1268, 1275 (Fed. Cir. 2015), aff’d, 136 S. Ct. 2131, 2142 (2016).
`
`Petitioners’ claim construction permits transmitting the data stored in the
`
`Msg3 buffer to be made along with a transmission of the new data:
`
`Petitioner anticipates Patent Owner might [wrongly]
`argue
`that
`the first “transmitting” feature [which
`Petitioner defined as the transmission of limitation 1(e)]
`defined as requires transmitting the Msg3 data only if
`those two conditions are met, attempting to transform the
`sufficient condition “if” into the necessary condition
`“only if.” Although the narrower “only if” interpretation
`matches an embodiment described in the specification,
`the plain claim language “if” encompasses a broader
`scope and is not limited to the more restrictive “only if”
`condition.
`Pet. at 18 (emphasis in original). In other words, Petitioners argue that the
`
`transmission of the Msg3 buffer data can occur even under the conditions of
`
`limitation 1(f), when the new data is sent, without receipt of an intervening CR
`
`
`
`- 14 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`message. That is because, in Petitioners’ view, the claim uses the language “if”
`
`rather than “only if” language. Id.
`
`
`
`Applying Petitioners’ reasoning that “if” in these limitations means “not only
`
`if” to both 1(e) and (f) limitations, then, Petitioners’ proposed construction is:
`
` 1(f)
`
` 1(e)
`
`transmitting the data stored in the Msg3 buffer to the base station using the
`UL Grant signal received on the specific message, if Condition X is met,
`and optionally transmitting the new data; and
`transmitting new data to the base station in correspondence with the UL
`Grant signal received on the specific message, if Condition X is not met,
`and optionally transmitting the data stored in the Msg3 buffer.
`Patent Owner notes that Petitioners did not apply their reasoning to the 1(f)
`
`limitation , so Patent Owner applies it here to assist the Board seeing the
`
`unreasonableness of Petitioners’ construction.
`A. Claim 1
`Petitioners’ proposed construction, which permits transmitting the Msg3
`
`buffer data along with new data (in limitation 1(f)), and which permits transmitting
`
`new data along with the Msg3 buffer data (in limitation 1(e)), is unreasonably
`
`broad.
`
`1. The claim language, properly read, excludes the possibility of
`transmitting new data along with the Msg3 buffer data
`The ’236 patent, as discussed above, describes initiating a random access
`
`procedure so that the UE can transmit its new data to a base station. Two UE
`
`transmissions, one for the Msg3 buffer data and one for the new data, each
`
`responsive to its own UL Grant, are required. In this circumstance, where there is a
`
`series of terms, a statement mentioning one term is reasonably interpreted as
`
`excluding the other term.
`
`
`
`- 15 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`That is the principle of expressio unius est exclusio alterius. The principle
`
`means “the express mention of one thing excludes all others.” Shenyang Yuanda
`
`Aluminum Industry Eng’g. v. United States, 776 F.3d 1351, 1359 (Fed. Cir. 2015).
`
`Under its guidance, the correct reading of limitation 1(f) excludes transmitting the
`
`Msg3 buffer data if the expressed claim limitations are present, and the correct
`
`reading of limitation 1(e) excludes transmitting the new data if the expressed claim
`
`limitations are present. As a result, the correct claim construction must exclude
`
`Petitioners’ claim construction.
`
`The expressio unius principle is applicable to patent law. Despoir, Inc. v. Nike
`
`USA, Inc., 2005 U.S. Dist. LEXIS 10845, *1 (N.D. Ill. Feb. 9, 2005) (using the
`
`principle to construe claim language, and “recognizing the validity of the canon of
`
`construction, expressio unius est exclusio alterius, in a discussion about the
`
`meaning of the term in patented items.”). It is applicable where, like here, the thing
`
`mentioned and the thing not mentioned, go hand in hand:
`
`
`
`The canon depends on identifying a series of two or more
`terms or things that should be understood to go hand in
`hand, which is abridged in circumstances supporting a
`sensible inference that the term left out must have been
`meant to be excluded . . . expressio unius properly
`applies only when in the natural association of ideas in
`the mind of the reader that which is expressed is so set
`over by way of strong contrast to that which is omitted
`that the contrast enforces the affirmative inference.
`
`
`
`- 16 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`Chevron USA Inc. v. Echazabal, 536 U.S. 77, 81 (2002) (citations and quotation
`
`marks omitted). In the present matter, the two things are transmitting the Msg3
`
`buffer data and transmitting the new data. These things go hand in hand, and are
`
`naturally associated by one of skill in the art when reading the patent’s
`
`specification, because they are the only two sets of user data the patent
`
`contemplates the UE transmitting.
`
`
`
`The ’236 patent’s Figure 9, copied below, confirms that the two things go
`
`hand in hand, because it identifies them as the only endpoints of the claimed
`
`process. This is visible in the figure’s two separate paths, one ending in step S909,
`
`the transmission of new data, and the other ending the step S908, the transmission
`
`of the Msg3 buffer data.
`
`
`
`Figure 5 (Ex. 1001 at 10 (sheet 8))
`
`
`
`- 17 -
`
`
`
`
`
`
`
`IPR2016-01345
`
`Notably, the block for S909 does not include the phrase “but do not transmit
`
`the Msg3 buffer data,” and the block for S908 does not incl