throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`
`
`
`APPLE INC.,
`
`Petitioner
`
`v.
`
`LBT IP I LLC,
`
`Patent Owner
`___________
`
`
`
`Case No. IPR2020-01189
`U.S. Patent No. 8,497,774
`____________
`
`
`PETITIONER APPLE INC.’S SUR-REPLY TO PATENT OWNER’S
`REPLY TO PETITIONER’S OPPOSITION TO MOTION TO AMEND
`
`
`
`
`
`

`

`
`
`B.
`
`C.
`
`TABLE OF CONTENTS
`1
`INTRODUCTION
`I.
`II. CLAIM CONSTRUCTION ....................................................................... 1
`THE DISCLOSURES OF THE ’774 PATENT RELIED UPON BY PATENT
`A.
`OWNER DO NOT SUPPORT SUCH AN INTERPRETATION .......................... 1
`PATENT OWNER’S DISTINCTION BETWEEN “TIMING SCHEDULE”
`AND “REFRESH RATE” IS UNSUPPORTED BY THE ’774 PATENT .............. 3
`PATENT OWNER’S NEWLY PROPOSED CONSTRUCTION FOR
`“VALUE” IMPROPERLY IMPORT LIMITATIONS INTO THE CLAIMS............ 5
`III. THE PROPOSED REPLACEMENT CLAIMS ARE NOT
`PATENTABLE ........................................................................................... 7
`THE PROPOSED REPLACEMENT ARE UNPATENTABLE UNDER
`A.
`35 U.S.C. § 103 .................................................................................. 7
`1.
`Ground 1: Claims 20–34 Are Obvious over Sakamoto .............. 7
`2.
`Ground 4: Claims 20–34 Are Obvious over Sakamoto in
`View of Huang........................................................................ 10
`IV. CONCLUSION ......................................................................................... 12
`
`
`
`
`
`
`
`i
`
`

`

`
`
`TABLE OF AUTHORITIES
`
`
`Statutes:
`35 U.S.C. § 103 .................................................................................. 1, 6, 12
`
`
`Regulations:
`37 C.F.R. § 42.6 ........................................................................................................ 15
`
`37 C.F.R. § 42.6(e) ................................................................................................... 15
`
`
`
`
`
`
`
`
`ii
`
`

`

`
`
`I.
`
`INTRODUCTION
`
`Petitioner, Apple Inc., submits this Sur-Reply responsive to Patent Owner’s
`
`Reply to Petitioner’s Opposition to Patent Owner’s Motion to Amend (Paper 30,
`
`“Reply to Opposition”). As set out below and in Petitioner’s Opposition to Patent
`
`Owner’s Motion to Amend (Paper 26, “Opposition”), Patent Owner’s Motion to
`
`Amend (Paper 16, “MTA”) should be denied because the amended claims improperly
`
`use claim construction to import limitations into the claims, lack written description
`
`under Patent Owner’s proposed constructions, and are unpatentable under § 103.
`
`II. CLAIM CONSTRUCTION
`Patent Owner maintains that the newly added claim limitation “timing
`
`schedule” should be interpreted to mean “when to listen for location coordinates and
`
`transmit those location coordinates” as opposed to simply how often to listen or
`
`transmit updates. See, e.g., Reply to Opposition at 4. Patent Owner also proposes,
`
`for the first time, that the claim term “value,” which is responsive to a user input
`
`request, be limited to a “time value.” Id at 10. Such claim interpretations are not
`
`supported by the disclosure of the ’774 Patent and should be rejected.
`
`A. The Disclosures of the ’774 Patent Relied upon by Patent Owner Do
`Not Support Such an Interpretation
`
`In support of its proposed interpretation, Patent Owner cites disclosure
`
`specifying that the tracking device “‘checks internal time schedule to determine if it
`
`should listen for (perform a location lookup of) location coordinates’ and ‘based on
`
`
`
`1
`
`

`

`
`
`the internal time schedule, portable location tracking device determines whether to
`
`transmit [location coordinates 422] to target host 452.’” Reply to Opposition at 3
`
`(quoting Ex. 2017, ’451 Application, at p. 18, ll. 9–11 and 16–18). However,
`
`disclosures are consistent with the teaching elsewhere in the ’774 Patent that the
`
`timing schedule is a refresh rate. For example, using the embodiment of FIG. 4, the
`
`device determines whether to transmit the location coordinates based on the
`
`specified update interval of 10 minutes, rather than based on any schedule indicating
`
`“when” (i.e., a specific time) an update should occur.
`
`
`
`Ex. 1001, ’774 Patent, FIG. 4 (colored annotations added). As depicted, FIG. 4 itself
`
`characterizes “timing schedule 446” as an “update interval,” and the “timing
`
`schedule 446” is the same “timing schedule” that is “responsive to a user input
`
`request.” See ’774 Patent, 15:13–15 (“user readjusts the initial timing schedule 446
`
`for communication of signaling parameters in accordance with a local request by
`
`remote user using an Internet accessible icon 432.”) Thus, the “time schedule” relied
`
`upon by Patent Owner is an update interval rather than an absolute time “when to
`
`listen for location coordinates.” Reply to Opposition at p. 4.
`2
`
`
`
`

`

`
`
`Next, Patent Owner argues that because a “refresh rate” is included in the
`
`updated set of network signaling protocols that is used to adjust the “internal time
`
`schedule,” the internal time schedule must be something other than the refresh rate.
`
`Reply to Opposition at 3–4. However, the same language cited by Patent Owner
`
`explains this distinction: the received update rate (refresh rate) is used to update the
`
`internal update rate (time schedule) by replacing the internally stored value with the
`
`newly received update rate. As such, Patent Owner’s interpretation finds no support
`
`in the ’774 Patent because the ’774 Patent simply uses “internal time schedule” to
`
`describe the internally stored refresh rate specified by the update. ’774 Patent at
`
`4:43–49 (describing updating the internal time schedule “in accordance with” the
`
`user specified update rate). In sum, Patent Owner provides no example in the ’774
`
`Patent of a timing schedule representing absolute times because the ’774 Patent
`
`includes none.
`
`B.
`
`Patent Owner’s Distinction Between “Timing Schedule” and “Refresh
`Rate” is Unsupported by the ’774 Patent
`
`Patent Owner argues that the Opposition “attempts to conflate the claim term
`
`timing schedule” with “refresh rate.” Reply to Opposition at 5. Indeed, the
`
`Opposition shows how the ’774 Patent uses the terms “refresh rate,” “update rate”
`
`and “timing schedule” interchangeably. For example, reference numeral 446 is
`
`variously described as “update rate 446 (e.g., refresh rate) of location coordinate
`
`packets,” “timing schedule (e.g., refresh rate 446),” and “timing schedule 446.” ’774
`
`
`
`3
`
`

`

`
`
`Patent at 11:56–57; 12:59–60; 13:33. Indeed, in describing how the user adjusts the
`
`tradeoff between update frequency and battery lifetime, the ’774 Patent refers to both
`
`“timing schedule 446” and “update rate 446” within the same paragraph. Id. at
`
`15:13–21. As such, the examples of an “update rate” and a “refresh rate” discussed
`
`in the Opposition are also examples of the claimed “timing schedule,” and (what is
`
`more) they are the only examples of the timings for updates given in the ’774 Patent.
`
`Patent Owner attempts to explain away the express statements of the ’774
`
`disclosures that a “refresh rate” is one example of a “timing schedule” by rewriting
`
`the disclosure of the ’774 Patent:
`
`
`
`Reply to Opposition at 4 (colored annotations added). However, contrary to Patent
`
`Owner’s rewriting, “e.g.” does not mean “based on,” and Patent Owner offers no
`
`evidence or even argument as to why “e.g.” should be read differently for “timing
`
`schedule” than for the “local battery adjustment mechanism” in the immediately
`
`
`
`4
`
`

`

`
`
`previous line. In sum, to the extent the Patent Owner’s proposed construction for
`
`“timing/time schedule” excludes a refresh rate, it is wholly unsupported by the ’774
`
`Patent and should be rejected.
`
`C.
`
`Patent Owner’s Newly Proposed Construction
`Improperly Import Limitations into the Claims
`
`for “Value”
`
`Patent Owner proposes, in passing and for the first time, that the claim term
`
`“value” in the limitations “the updated set of network communication signaling
`
`protocols having a value that is responsive to a user input request” and “the local
`
`battery power adjustment mechanism activates or deactivates at least one portion of
`
`the transceiver circuitry or the processor circuitry in response to the value” be
`
`interpreted so as to require a “time value.” Reply to Opposition at p. 10. Such a claim
`
`interpretation would import a limitation from the Specification of the ’774 Patent
`
`into the claims and is inconsistent with the sole described example in that
`
`Specification. Patent Owner’s proposed constructions should be rejected, and
`
`“value” should be accorded its plain and ordinary meaning.
`
`First, the Specification describes this “value” with respect to reference
`
`numeral 419 of FIG. 4, which depicts a cursor allowing the user to “adjust battery
`
`performance” rather than any “time value”:
`
`
`
`5
`
`

`

`
`
`
`
`’774 Patent, FIG. 4 (colored annotations added); see also ’774 Patent 11:46–53
`
`(“local battery power adjustment mechanism 416 … communicates a message to
`
`active or deactivate a portion of transceiver circuitry 102 or processor circuitry 104
`
`or location tracking circuitry 114 to conserve battery charge level 406 responsive to
`
`value 419 (e.g., a user input screen control or mouse adjustable cursor value).”).
`
`Similarly, the value of the “set of network communication signaling
`
`protocols” itself is not “time value.” The ’774 Patent gives, as one example of a
`
`value of a communication signaling protocol, “(X Y Z).” ’774 Patent, 11:42. These
`
`same X, Y, and Z values are described, in the context of FIG. 5, as “request rate
`
`420,” “location coordinates packet 422,” and “listen rate 425,” respectively. Id. at
`
`13:1-12. Neither the collection of these values nor any of the individual component
`
`values is a “time value” as Patent Owner appears to propose. For at least these
`
`reasons, Patent Owner’s belated attempt to insert the requirement that a “value” be
`
`a “time value” is unsupported and should be rejected.
`
`
`
`
`
`
`
`6
`
`

`

`
`
`III. THE PROPOSED REPLACEMENT CLAIMS ARE NOT
`PATENTABLE
`A. The Proposed Replacement Are Unpatentable Under 35 U.S.C. § 103
`1.
`Ground 1: Claims 20–34 Are Obvious over Sakamoto
`
`a)
`
`Sakamoto teaches “a communication signaling protocol having a
`value that is responsive to a user input request”
`
`Patent Owner argues that Sakamoto fails to teach the claim limitation
`
`requiring that “the updated set of network communication signaling protocols hav[e]
`
`a value that is responsive to a user input request” because, as Patent Owner interprets
`
`the Petition, a “preset threshold value” (set by a user) is used to meet this limitation
`
`in the original mapping for claim 1, and this preset threshold value does not
`
`“represent a timing schedule” as required by replacement claim 20. Reply to
`
`Opposition at pp. 6-7. In making this argument, however, Patent Owner
`
`mischaracterizes (or misunderstands) the original mapping in the Petition:
`
`specifically, the Petition devotes § VI.C.6.d to explaining how Sakamoto teaches
`
`that the terminal user A can select the positioning mode (and therefore the value of
`
`the communication signaling protocol). Paper 1, Petition, at pp. 34-36; see also
`
`Paper 9, Institution Decision at 21-23 (setting out this mapping finding it
`
`persuasive). Furthermore, as set out in § IV.A.3 of the Opposition, Sakamoto’s
`
`positioning mode represents a timing schedule for at least one of the request rate and
`
`the listen rate. Opposition at pp. 13-15.
`
`
`
`7
`
`

`

`
`
`Sakamoto’s refresh rate is a “refresh rate”
`
`b)
`Curiously, Patent Owner contends that Sakamoto’s “refresh rate” is not the
`
`same as the “update rate 446/refresh rate 446/refresh rate” in the ’774 Patent. Reply
`
`to Opposition at p. 7. However, the ’774 Patent describes one embodiment where
`
`the refresh rate is described as “global positioning system (GPS) system refresh rate
`
`446.” ’774 Patent, 13:40–43. In other words, the ’774 Patent contemplates that
`
`“refresh rate 446” could be a GPS system refresh rate. This is, as pointed out in both
`
`the Petition and the Opposition, the refresh rate for the listen rate in Sakamoto’s high
`
`sensitivity positioning mode.
`
`Petition at p. 34 (red box added). Thus, contrary to Patent Owner’s arguments,
`
`Sakamoto teaches a positioning mode that adjusts the refresh rate to be that of the
`
`GPS system refresh rate, which is specifically given as one example of a “refresh
`
`
`
`rate 446” in the ’774 Patent.
`
`
`
`8
`
`

`

`
`
`Sakamoto teaches updating the refresh rate
`
`c)
`Patent Owner next concedes that Sakamoto discloses changing between
`
`positioning modes and, as a result of changing positioning modes, applies different
`
`refresh rates. Reply to Opposition at 7. Patent Owner contends, however, that while
`
`Sakamoto teaches a set of network communication signaling protocols associated
`
`with a positioning mode (the listen rate and response rate), it “does not disclose an
`
`updated set of network communication signaling protocols that has a user-input
`
`request responsive value and represents a timing schedule.” Id. at p. 8. This again
`
`misrepresents (or misunderstands) the mapping in the Petition. As explained in the
`
`Petition, “switching the mode in this way [manually or automatically based on
`
`battery level] is generating an updated set of network communication signaling
`
`protocols as claimed.” Petition at p. 30. In other words, if the original set of protocols
`
`represents the listen and response rate of high sensitivity positioning mode, then the
`
`updated set of protocols represents the listen and response rate of normal sensitivity
`
`positioning mode generated after the user instructs a switch from high to normal
`
`sensitivity in response to a battery level warning. As described in the Petition, these
`
`communication signaling protocols are generated “substantially in real time” in
`
`response to the user input instructing the switch. Petition at pp. 29-30.
`
`Similar to the original “set of network communication signaling protocols,”
`
`the original “cycle timing” is that timing associated with high sensitivity positioning
`
`
`
`9
`
`

`

`
`
`mode and the adjusted cycle timing is that timing associated with normal sensitivity
`
`positioning mode after an automatic switch from high sensitivity to normal
`
`sensitivity in response based on the battery charge level.
`
`2.
`
`Ground 4: Claims 20–34 Are Obvious over Sakamoto in View of
`Huang
`a) Huang teaches dynamically updating refresh rates
`First, Patent Owner argues that “Ground 4 continues to rely on Sakamoto’s
`
`disclosure that … each positioning mode has an associated refresh rate and changing
`
`to a different positioning mode results in a different refresh rate.” Reply to
`
`Opposition at p. 10. This is simply incorrect. The proposed combination of Sakamoto
`
`and Huang replaces Sakamoto’s discrete positioning modes with a user-
`
`configurable, continuous mapping function that dynamically and continuously
`
`updates the GPS update frequency based on battery level:
`
`is
`listen rate
`the proposed combination, Sakamoto’s GPS
`In
`dynamically adapted according to the mapping function disclosed by
`Huang. Rather than the user specifying the battery thresholds where the
`system switches to normal sensitivity positioning mode (as taught by
`Sakamoto), the user would specify the battery thresholds where update
`frequency begins to decrease (e.g., 75% in Huang’s FIG. 5) and where
`it reaches its minimum value (e.g., 25% in Huang’s FIG. 5).
`
`Opposition at pp. 17-18; see also Ex. 1077, Andrews Supplemental Declaration, ¶ 9
`
`(describing the advantages of continuous adaptation rather than the abrupt stepped
`
`
`
`10
`
`

`

`
`
`transitions associated with Sakamoto’s transitions between positing modes). As
`
`such, Patent Owner’s arguments with respect to Sakamoto do not apply to the
`
`combination of Sakamoto and Huang at least because Huang teaches dynamically
`
`updating refresh rates without discrete positioning modes. For this reason, the
`
`combination of Sakamoto and Huang renders the amended claims obvious.
`
`b)
`
`The proposed combination includes a set of communication
`signaling protocols having a value responsive to a user input
`request
`
`Finally, based on their proposed construction for “value,” Patent Owner
`
`argues that Huang does not teach “an updated set of communication signaling
`
`protocols having a value that is responsive to a user input request.” Reply to
`
`Opposition at p. 10. Patent Owner does not, however, address the mapping for the
`
`claim limitation in the Opposition. In the proposed combination, “the user would
`
`specify the battery thresholds where update frequency begins to decrease (e.g., 75%
`
`in Huang’s FIG. 5) and where it reaches its minimum value (e.g., 25% in Huang’s
`
`FIG. 5).” Opposition at p. 18. In other words, in the proposed combination, the user
`
`provides inputs that control the shape of the curve that controls the update rate. For
`
`example, Huang depicts one exemplary curve (set of communication signaling
`
`protocols) in FIG. 5. As proposed, the user could provide inputs specifying that the
`
`update frequency decreased more rapidly such that the minimum update frequency
`
`is reached when the battery reaches 50% rather than 25% as depicted below.
`
`
`
`11
`
`

`

`
`
`
`
`Andrews Supplemental Declaration, ¶ 8 (annotating Huang FIG. 5); alternative
`
`curve. As such, the proposed combination of Sakamoto and Huang teaches a set of
`
`communication signaling protocols having a value responsive to a user input request.
`
`IV. CONCLUSION
`For the reasons discussed herein, Apple submits that LBT’s proposed
`
`substitute claims are unpatentable over at least 35 U.S.C. § 103.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ERISE IP, P.A.
`
`BY: /s/ Jennifer C. Bailey
`Jennifer C. Bailey, Reg. No. 52,583
`Adam P. Seitz, Reg. No. 52,206
`7015 College Blvd., Suite 700
`Overland Park, KS 66211
`P: (913) 777-5600
`jennifer.bailey@eriseip.com
`adam.seitz@eriseip.com
`
`ATTORNEYS FOR PETITIONER
`APPLE INC.
`
`
`
`12
`
`

`

`
`
`APPENDIX OF EXHIBITS
`
`Exhibit 1001 U.S. Patent No. 8,497,774 to Scalisi et al. entitled “Apparatus and
`Method for Adjusting Refresh Rate of Location Coordinates of a
`Tracking Device,” filed on April 7, 2009 and issued on July 30,
`2013
`Exhibit 1002 File History of U.S. Patent No. 8,497,774
`Exhibit 1003 Declaration of Scott Andrews
`Exhibit 1004 Certified English Translation of Japanese Unexamined Patent
`Application Publication No. JP 2004-37116A to Sakamoto
`(“Sakamoto”); Certified English Translation of Figures of
`Japanese Unexamined Patent Application Publication No. JP
`2004-37116A to Sakamoto; Affidavit for Sakamoto Translation;
`Affidavit for Sakamoto Figures Translation
`Exhibit 1005
`Intentionally Left Blank
`Exhibit 1006
`Intentionally Left Blank
`Exhibit 1007
`Intentionally Left Blank
`Exhibit 1008
`Intentionally Left Blank
`Exhibit 1009
`Intentionally Left Blank
`Exhibit 1010 U.S. Patent No. 6,799,050 to Krasner, filed June 4, 2001 and
`published September 28, 2004 (“Krasner”)
`Exhibit 1011 U.S. Patent No. 5,845,142 to Hayasaka, filed August 29, 1997 and
`published December 1, 1998 (“Hayasaka”)
`Exhibit 1012
`Intentionally Left Blank
`Exhibit 1013 U.S. Patent No. 5,902,347 to Backman et al. (“Backman”)
`Exhibit 1014
`Intentionally Left Blank
`Exhibit 1015 U.S. Patent No. 6,308,134 to Croyle et al. (“Croyle”)
`Exhibit 1016 U.S. Patent No. 7,024,321 to Deninger et al. (“Deninger”)
`Exhibit 1017 U.S. Patent No. 7,196,661 to Harvey (“Harvey”)
`Exhibit 1018
`Intentionally Left Blank
`Exhibit 1019 U.S. Patent Application Publication No. 2006/0167647A1 to
`Krumm et al. (“Krumm”)
`Exhibit 1020 U.S. Patent No. 5,592,173 to Lau et al. (“Lau”)
`Exhibit 1021 U.S. Patent No. 7,430,675 to Lee (“Lee”)
`Exhibit 1022 U.S. Patent No. 8,467,804 to Lindquist (“Lindquist”)
`Exhibit 1023 U.S. Patent No. 7,760,137 to Martucci et al. (“Martucci”)
`Exhibit 1024 U.S. Patent No. 7,181,192 to Panasik et al. (“Panasik”)
`Exhibit 1025 U.S. Patent No. 7,126,536 to Rabinowitz et al. (“Rabinowitz”)
`Exhibit 1026 U.S. Patent No. 8,797,214 to Taylor et al. (“Taylor”)
`
`
`
`13
`
`

`

`
`
`Exhibit 1027 U.S. Patent No. 7,239,271 to Vyas et al. (“Vyas”)
`Exhibit 1028 U.S. Patent No. 6,850,844 to Walters et al. (“Walters”)
`Exhibit 1029 U.S. Patent No. 7,439,907 to Wang et al. (“Wang”)
`Exhibit 1030 U.S. Patent No. 5,491,486 to Welles, II et al. (“Welles”)
`Exhibit 1031
`Intentionally Left Blank
`Exhibit 1032 Vehicle Location and Navigation Systems, pp. 43-81 (“Zhao”)
`Exhibit 1033
`Intentionally Left Blank
`Exhibit 1034
`Intentionally Left Blank
`Exhibit 1035 Curriculum Vitae of Scott Andrews
`Exhibit 1036 LBT IP I LLC v. Apple Inc., 1:19-cv-01245, No. 1 (D. Del. July 1,
`2019) (“LBT Complaint”)
`Exhibit 1037
`Intentionally Left Blank
`Exhibit 1038
`Intentionally Left Blank
`Exhibit 1039 U.S. Patent Application Publication No. 2007/005243A1 to
`Horvitz et al. (“Horvitz”)
`Exhibit 1040 U.S. Patent Application Publication No. 2007/0005363A1 to
`Cucerzan et al. (“Cucerzan”)
`Exhibit 1041
`Intentionally Left Blank
`Exhibit 1042
`Intentionally Left Blank
`Exhibit 1043
`Intentionally Left Blank
`Exhibit 1044 U.S. Patent No. 6,657,587 to Mohan et al. (“Mohan”)
`Exhibit 1045-
`Intentionally Left Blank
`1066
`Exhibit 1067 District Court Complaint DDE-1-19-cv-01245-1
`Exhibit 1068 Scott Andrews Deposition Transcript
`Exhibit 1069 Email Regarding Motion to Amend
`Exhibit 1070 Email from Board Re Hearing
`Exhibit 1071 Attorneys for LBT IP I LLC v. Apple Inc. DDE-1-19-cv-01245
`Exhibit 1072 Annotated NOTICE OF SERVICE of Apples Production of Core
`Technical Documents
`Exhibit 1073 2020-05-01 DI-29 Agreed Protective Order Regarding
`Disclosure and Use of Discovery Materials
`Exhibit 1074 Transcripts of Proceedings - May 20, 2021 Hearing
`Exhibit 1075 Butzel Long Website
`Exhibit 1076 dictionary.com definition for “multitude”
`Exhibit 1077 Supplemental Declaration of Scott Andrews
`
`
`the
`
`
`
`
`
`
`
`14
`
`

`

`CERTIFICATE OF SERVICE ON PATENT OWNER
`UNDER 37 C.F.R. § 42.6
`
`Pursuant to 37 C.F.R. § 42.6(e), the undersigned certifies that on November
`19, 2021 the foregoing Petitioner Apple Inc.’s Opposition to Patent Owner’s Motion
`to Amend was served via electronic filing with the Board and via Electronic Mail on
`the following practitioners of record for Patent Owner:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Mitchell S. Zajac (zajac@butzel.com)
`Shaun D. Gregory (gregorysd@butzel.com)
`Brian S. Seal (seal@butzel.com)
`
`
`
`
`
`
`
`
`
`
`/s/ Jennifer C. Bailey
`Jennifer C. Bailey, Reg. No. 52,583
`
`
`
`
`
`
`
`ATTORNEY FOR PETITIONER
`
`15
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket