throbber
IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`Case No. 2:23-cv-496-JRG-RSP
`
`
`JURY TRIAL DEMANDED
`
`CELLSPIN SOFT, INC.,
`Plaintiff
`
`
`
`v.
`
`
`BYTEDANCE, LTD, BYTEDANCE PTE.
`LTD, TIKTOK PTE. LTD.,
`Defendants.
`
`
`
`
`
`DEFENDANTS’ P.R. 4-1 LIST OF PROPOSED CLAIM TERMS
`
`Pursuant to P.R. 4-1(a), and the Court’s Docket Control Order (Dkt. No. 35), Defendants
`
`Bytedance, Ltd, Bytedance Pte. Ltd., and TikTok Pte. Ltd. (collectively, “Defendants”) hereby
`
`provide their preliminary claim term identification for construction for U.S. Patent Nos. 8,756,336
`
`(the “’336 Patent”); 8,862,757 (the “’757 Patent”); 8,898,260 (the “’260 Patent”); 8,904,030 (the
`
`“’030 Patent”); 9,900,766 (the “’766 Patent”); 11,234,121 (the “’121 Patent”); and 11,695,381 (the
`
`“’381 Patent”) (collectively the “Asserted Patents”). Pursuant to P.R. 4-1(b), Defendants are
`
`prepared to meet and confer with Plaintiff Cellspin Soft, Inc., at a mutually agreeable time to
`
`combine and finalize the parties’ respective lists of claim terms and claim elements to be construed
`
`and to facilitate the preparation of the Joint Claim Construction and Prehearing Statement for the
`
`Patents-in-Suit.
`
`Defendants reserve the right to modify or supplement its preliminary proposed
`
`constructions after having an opportunity to review Plaintiff’s preliminary proposed constructions.
`
`Defendants reserve the right to offer further extrinsic evidence to rebut preliminary claim
`
`constructions, testimony, or extrinsic evidence Plaintiff offers in support of its claim construction
`
`positions. Defendants also reserve the right to supplement, amend, and/or modify the following
`
`1
`
`

`

`list of proposed claim terms and claim elements for claim construction to facilitate the ultimate
`
`preparation of the Joint Claim Construction and Pre-Hearing Statement.
`
`In addition, Defendants may provide declarations and/or testimony of one or more of their
`
`experts as evidence of how one having ordinary skill in the art would interpret the foregoing terms.
`
`Such declarations and/or testimony may address both the general understanding of the relevant
`
`terms and phrases in the field of the Asserted Patents as well as the understanding of terms and
`
`phrases in the context of the Asserted Patents’ specifications and claims. Defendants’ experts may
`
`also provide testimony concerning the appropriate level of skill in the art at the time of the
`
`inventions and the background of the technology at issue at the time of the inventions. Defendants
`
`reserve the right to introduce expert declarations or testimony to rebut Plaintiff's claim construction
`
`positions and any expert declarations or testimony introduced by Plaintiff.
`
`In the instances in which Defendants identify a phrase below as a proposed phrase for
`
`construction, Defendants identify for potential construction both the words within the phrase
`
`(individually) and the phrase as a whole. Further, Defendants may construe the longer phrase in
`
`which the identified term or phrase appears. Additionally, the inclusion of any claim terms,
`
`phrases, or clauses on this list is not intended to and does not constitute an admission that the term
`
`or phrase is capable of construction and not indefinite under 35 U.S.C. § 112, lacking enablement
`
`or adequate written description, or otherwise incapable of construction. Defendants reserve the
`
`right to contest any such terms and the validity of any claim of the patents-in-suit.
`
`
`
`2
`
`

`

`Dated: October 29, 2024
`
`Respectfully submitted,
`
`By:/s/ Michael J. Ballanco
`Melissa R. Smith
`Texas Bar No. 24001351
`melissa@gillamsmithlaw.com
`GILLAM & SMITH, LLP
`303 South Washington Avenue
`Marshall, TX 75670
`(903) 934-8450 (Telephone)
`(903) 934-9257 (Facsimile)
`
`Ruffin B. Cordell
`DC Bar No. 459780
`cordell@fr.com
`Michael J. Ballanco
`DC Bar No. 1030421
`ballanco@fr.com
`FISH & RICHARDSON P.C.
`1000 Maine Avenue, S.W., Suite 1000
`Washington, DC 20024
`(202) 783-5070 (Telephone)
`(202) 783-2331 (Facsimile)
`
`Ricardo J. Bonilla
`Texas Bar No. 24082704
`rbonilla@fr.com
`David B. Conrad
`Texas Bar No. 24049042
`conrad@fr.com
`Noel F. Chakkalakal
`Texas Bar No. 24053676
`chakkalakal@fr.com
`Adil A. Shaikh
`Texas Bar No. 24117039
`shaikh@fr.com
`FISH & RICHARDSON P.C.
`1717 Main Street, Suite 5000
`Dallas, Texas 75201
`Tel: (214) 747-5070
`Fax: (214) 747-2091
`
`COUNSEL FOR DEFENDANTS
`BYTEDANCE LTD., BYTEDANCE PTE.
`LTD., AND TIKTOK PTE. LTD.
`
`
`3
`
`
`
`

`

`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a true and correct copy of the above and foregoing
`
`document has been served on October 29, 2024, to all counsel of record who are deemed to have
`
`consented to electronic service via the Court’s CM/ECF system.
`
`
`
`
`
`
`
`/s/ Michael J. Ballanco
`Michael J. Ballanco
`
`
`
`
`
`
`
`4
`
`

`

`PROPOSED TERMS FOR CONSTRUCTION
`
`
`
`U.S. PATENT NO. 8,756,336
`
`Claim Terms, Phrases, or Clauses for Construction
`“segmented” / “segmenting”
`“Bluetooth enabled mobile device”
`“receiving a synchronization message” / “sending, a synchronization request” /
`“receiving, a synchronization reply”
`“using a segmented data transfer protocol due in part to present data size and
`data transfer capabilities of the Bluetooth enabled mobile device”
`“user identifier”
`“resuming, the segmented data transfer from the point immediately following
`the last successful receipt of the segmented data by the web service, for said
`user identifier.”
`“application layer level”
`“after a network connection to the web service is restored”
`“segment identifier”
`
`
`
`U.S. PATENT NO. 8,862,757
`
`Claim Terms, Phrases, or Clauses for Construction
`“segmented” / “segmenting”
`“Bluetooth enabled mobile device”
`
`“synchronization message” / “synchronization request” / “synchronization
`reply”
`“wherein said file is segmented in part due to size of said file and data transfer
`capabilities of said Bluetooth enabled mobile device, ”
`“user identifier”
`
`“corresponds to the content range”
`“after a network connection to the web service is restored”
`“segment identifier”
`
` U.S. PATENT NO. 8,898,260
`
`Claim Terms, Phrases, or Clauses for Construction
`“segmented” / “segmenting”
`“Bluetooth enabled mobile device”
`
`5
`
`Claim No(s).
`1
`1, 2, 3, 4
`1
`
`1
`
`1, 5
`1
`
`1
`1
`1
`
`Claim No(s).
`1, 8, 15, 21
`1, 5, 8, 12, 15,
`18, 21, 24
`1, 8, 15, 21
`
`1, 8, 15, 21
`
`1, 4, 8, 11, 15,
`17, 21, 23
`7, 14, 20, 26
`1
`1,7,8,14,15,20,
`21,26
`
`Claim No(s).
`1, 6, 10, 15
`1, 6, 10, 15
`
`

`

`Claim Terms, Phrases, or Clauses for Construction
`“synchronization message” / “synchronization request” / “synchronization
`reply”
`“user identifier”
`
`“making available, at the web service, the segmented data received from the
`Bluetooth enabled mobile device for public or private consumption over the
`internet. . .” / “making available, at the web service, the reassembled data
`received from the Bluetooth enabled mobile device for public or private
`consumption over the internet.”
`“corresponds to the content range”
`“after a network connection to the web service is restored”
`“segment identifier”
`
` U.S. PATENT NO. 8,904,030
`
`Claim Terms, Phrases, or Clauses for Construction
`Claims Elements Must be in an Ordered Combination
`“establishing a paired secure (Bluetooth) connection between the Bluetooth
`enabled mobile device and a Bluetooth enabled data capture device” /
`“Bluetooth paired wireless connection”
`“after the paired secure Bluetooth connection is established”
`“over the established paired secure Bluetooth connection”
`“supported data capability”
`“encrypting, using cryptographic encryption key”
`“transferring” / “receive” . . . “encrypted data”
`“cryptographic encryption key”
`“Bluetooth enabled data capture device”
`“detecting and signaling” / “determining existence of” / “acquiring” / “get” /
`“obtaining” / “transfer” / “encrypting” / “creation of” / “change in status of” . .
`. “new data”
`“receive[] / “process” / “listen for” / “enable” / . . . “event notification”
`
`“Bluetooth enabled mobile device listens for the event notification sent from
`the Bluetooth enabled data capture device” / “enabling event notification
`listening on the Bluetooth enabled mobile device, to listen for event
`notifications sent from the Bluetooth enabled data capture device, over the
`established paired secure Bluetooth connection”
`“data signal notification(s)”
`“user identifier”
`
`Claim No(s).
`1, 6, 10, 15
`
`1, 4, 6, 8, 10,
`13, 15, 17
`1, 6, 10, 15
`
`1, 6, 10, 15
`1, 6, 10, 15
`1, 6, 10, 15
`
`Claim No(s).
`1, 6, 12, 15
`1, 6, 12, 15
`
`1, 6
`1, 6, 12, 15
`1, 12
`1, 6
`1, 6, 12, 15
`1, 6, 12, 15
`1-3, 6-8, 12, 15
`1, 4-6, 9-10,
`12-17
`
`1, 5, 12, 14-15,
`17
`1, 12, 15
`
`6, 10
`1, 6, 12, 15
`
`6
`
`

`

`Claim Terms, Phrases, or Clauses for Construction
`“along with”
`“creating” / “encrypting” / “get” … “new data object”
`“HTTP”
`
`
`
`U.S. PATENT NO. 11,659,381
`
`Claim Terms, Phrases, or Clauses for Construction
`Claims Elements Must be in an Ordered Combination
`“a mobile software application for a Bluetooth enabled cellular phone”
`“establishing a paired Bluetooth connection between the Bluetooth enabled
`data capture device and the Bluetooth enabled cellular phone”
`“after establishing a paired Bluetooth connection”
`“over the established paired Bluetooth connection”
`“Bluetooth enabled data capture device”
`“cryptographically authenticating”
`“listen for an event notification”
`“detect and receive” / “store the received” / “transfer the received” . . . “new-
`data”
`“along with”
`“user authentication credential”
`“user preference” / “wherein the user preference comprises global positioning
`system information”
`“online data publishing web service”
`“user profile”
`“poll” / “polling”
`
` U.S. PATENT NO. 11,234,121
`
`Claim Terms, Phrases, or Clauses for Construction
`Claims Elements Must be in an Ordered Combination
`“short-range wireless communication device”
`“short-range paired wireless connection”
`“over the established short-range paired wireless connection”
`“after establishing the short-range paired wireless connection”
`“short-range wireless enabled data capture device”
`“cellular network communication device”
`“cryptographically authenticating”
`“event notification”
`“listen to the event notification”
`
`7
`
`Claim No(s).
`1, 6, 12, 15
`6, 15
`1, 4, 7, 9
`
`Claim No(s).
`1, 7, 12
`1, 7, 12
`1, 7, 12
`
`1, 7, 12
`1, 7, 12
`1, 7, 12
`1, 7, 12
`1, 7
`1, 3-4, 7, 8-10,
`12, 14-15
`1, 7, 12
`1-2, 7-8, 12-13
`1, 7, 12
`
`1
`1, 6
`12
`
`Claim No(s).
`1, 4, 7, 9
`1, 4, 7
`1, 4, 7
`1, 4, 9
`1, 4, 9
`1-4, 7, 9-10
`4, 7
`1, 4, 9
`1, 4, 7
`1,
`
`

`

`Claim Terms, Phrases, or Clauses for Construction
`“listen for the event notification” / “listen for an event notification”
`“mobile client application”
`“user authentication credential”
`“user preference” / “wherein the user preference comprises global positioning
`system information”
`“cellular network communication device”
`“timer setting on the single mobile client application” / “timer setting is no
`wait automatic or wait X minutes automatic”
`“acquire” / “store” / “upload”/ “detect”/ “transfer” / “receive” . . . “new-data”
`“user data publishing website”
`“user data publishing web service”
`“publish the new-data for private use”
`“polling request” / “polling”
`“HTTP”
`
`Claim No(s).
`4, 7
`1, 3-4, 7, 9,
`1-4, 6-7, 9
`1, 4, 7, 9
`
`4, 7
`1, 4, 7, 9
`
`1, 3, 4, 7, 9.
`1, 3-4, 6, 9
`7
`3
`9
`1, 4, 7, 9
`
` U.S. PATENT NO. 9,900,766
`
`Claim Terms, Phrases, or Clauses for Construction
`Claims Elements Must be in an Ordered Combination
`“short-range wireless communication device”
`“short-range paired wireless connection”
`
`“short-range wireless enabled cellular phone”
`“short-range wireless enabled data capture device”
`“after establishing the short-range paired wireless connection” / “after the
`short-range paired wireless connection is established”
`“over the established short-range paired wireless connection”
`“association protocol”
`“internet connected cellular phone”
`“establish a short-range paired wireless connection” . . . “between the short-
`range wireless enabled data capture device and a short-range wireless enabled
`cellular phone” / “with an internet connected cellular phone”
`“after establishing the short-range paired wireless connection” . . . “between
`the short-range wireless enabled data capture device and the short-range
`wireless enabled cellular phone” / “with the cellular phone”
`“cryptographically authenticating” / “cryptographically authenticated”
`“signal to notify”
`“listen to the signal to notify”, “listen for the signal to notify”, “listen and
`process the signal to notify”
`
`8
`
`Claim No(s).
`1, 4, 9, 13
`1, 4, 9, 13
`1-2, 4-6, 9-10,
`13-14
`1, 9-13
`1-3, 9, 13
`1, 4, 9, 12
`
`1, 4, 9
`1, 4, 5, 9, 13
`4
`1, 4, 9, 13
`
`1, 4
`
`1, 4, 8-9, 12-13
`1, 4, 9, 13
`1, 4, 9
`
`

`

`Claim Terms, Phrases, or Clauses for Construction
`“acquire” / “store” / “upload” / “signal” / “publish” / “create” . . . “new-data” /
`“new-data object”
`“user information”
`“along with”
`“user identifier”
`“private consumption”
`“mobile client application”
`“user data publishing website”
`“HTTP”
`
`Claim No(s).
`1-4, 7-9, 11-
`13, 15
`1, 4, 9, 13
`1, 4, 9, 13
`1, 4, 9, 13
`1, 4, 9, 13
`1, 4, 9, 13
`1, 4, 9, 13
`1, 4, 9, 13
`
`
`
`9
`
`

`

` IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`Case No. 2:23-cv-496-JRG-RSP
`
`
`JURY TRIAL DEMANDED
`
`CELLSPIN SOFT, INC.,
`Plaintiff
`
`
`
`v.
`
`
`BYTEDANCE, LTD, BYTEDANCE PTE.
`LTD, TIKTOK PTE. LTD.,
`Defendants.
`
`
`
`
`
`DEFENDANTS’ P.R. 4-2(a) PRELIMINARY CLAIM
`CONSTRUCTIONS AND EXTRINSIC EVIDENCE
`
`Pursuant to P.R. 4-2 and the Court’s Docket Control Order (Dkt. No. 35), Defendants
`
`Bytedance, Ltd, Bytedance Pte. Ltd., and TikTok Pte. Ltd. (collectively, “Defendants”) hereby
`
`provide their Patent L.R. 4.2(a) and 4.2(b) disclosures.
`
`The below chart includes Defendants’ preliminary claim constructions and extrinsic
`
`evidence. Defendants’ discovery is ongoing, and therefore Defendants reserve the right to modify
`
`the proposed claim constructions as well as to modify, add, or delete terms, phrases and/or clauses
`
`based on, without limitation, the constructions served or proposed by Plaintiff Cellspin Soft, Inc.
`
`(“Cellspin”), information learned in the course of meeting and conferring with Cellspin’s counsel,
`
`information learned through the course of discovery or other means, and any further changes or
`
`amendments to the parties’ infringement or invalidity contentions. Defendants reserve the right to
`
`rely on any evidence disclosed by Cellspin in its Patent L.R. 4.2(a) and 4.2(b) disclosures.
`
`Defendants also reserve the right to supplement its preliminary claim constructions with extrinsic
`
`evidence or expert testimony, including in rebuttal to Cellspin’s preliminary or subsequent claim
`
`constructions. Inclusion of evidence as extrinsic below, such as IPR proceedings, does not preclude
`
`the same evidence from being considered as intrinsic evidence.
`
`1
`
`

`

`Defendants reserve the right to modify, supplement, or amend its list of claim terms,
`
`phrases, clauses and/or constructions set forth below. Additionally, Defendants reserve the right
`
`to separately request construction of portions of the identified claim terms, phrases, and/or clauses.
`
`For example, these proposed claim constructions are based on Cellspin’s current infringement
`
`contentions. Should Cellspin assert that other claims are infringed, amend their infringement
`
`contentions, or should other claims otherwise become relevant, Defendants reserve the right to
`
`propose new claim constructions as required. Should Cellspin seek an improper interpretation of
`
`a term, phrase, and/or clause that has not been identified by the parties, Defendants reserve the
`
`right to seek the construction of that term, phrase, and/or clause. Defendants further reserve the
`
`right to identify additional extrinsic evidence to rebut the proposed constructions of Cellspin.
`
`The claim terms, phrases, and/or clauses are generally identified at least with respect to the
`
`patent where such terms, phrases, and/or clauses occur. Unless otherwise indicated below, any
`
`additional occurrence, including in related asserted patents, of a listed claim term, phrase, and/or
`
`clause is intended to receive the same construction as the listed term, phrase, and/or clause,
`
`regardless of whether the later occurrence is also listed below.
`
`Defendants’ preliminary claim constructions shall not act as a waiver of any defense of
`
`noninfringement, invalidity, or unenforceability of any of Cellspin’s asserted patents.
`
`Notwithstanding the preliminary claim constructions contained herein of any term, phrase, and/or
`
`clause, Defendants expressly reserve the right to challenge the validity of any or all claims in
`
`Cellspin’s asserted patents on all possible grounds.
`
`Defendants further reserve all rights to assert that terms, phrases, and/or clauses in the
`
`patents-in-suit are invalid under 35 U.S.C. § 112, including without limitation the terms, phrases,
`
`2
`
`

`

`and/or clauses listed in Defendants’ Invalidity Contentions and any amendments or supplements
`
`thereto.
`
`The inclusion of any claim terms, phrases, and/or clauses on this list is not intended, and
`
`should not be construed to mean, that any such terms, phrases, and/or clauses have a special or
`
`uncommon meaning. Additionally, the inclusion of any claim terms, phrases, and/or clauses on
`
`this list is not intended to and does not constitute an admission that the term, phrase, and/or clause
`
`is capable of construction and not indefinite under 35 U.S.C. § 112, lacking enablement or
`
`adequate written description, or otherwise incapable of construction. Defendants reserve the right
`
`to contest any such terms, phrases, and/or clauses and the validity of any claim of the patents-in-
`
`suit.
`
`To the extent the claim terms, phrases, and/or clauses set forth herein include particular
`
`terms, phrases, and/or clauses appropriate to be construed separately, such terms, phrases, and/or
`
`clauses are deemed part of this disclosed list. Similarly, to the extent it is appropriate to construe
`
`terms, phrases, and/or clauses listed herein in the context of additional claim language, such
`
`additional language is deemed part of this disclosure.
`
`3
`
`

`

`Dated: November 12, 2024
`
`Respectfully submitted,
`
`By:/s/ Michael J. Ballanco
`Melissa R. Smith
`Texas Bar No. 24001351
`melissa@gillamsmithlaw.com
`GILLAM & SMITH, LLP
`303 South Washington Avenue
`Marshall, TX 75670
`(903) 934-8450 (Telephone)
`(903) 934-9257 (Facsimile)
`
`Ruffin B. Cordell
`DC Bar No. 459780
`cordell@fr.com
`Michael J. Ballanco
`DC Bar No. 1030421
`ballanco@fr.com
`FISH & RICHARDSON P.C.
`1000 Maine Avenue, S.W., Suite 1000
`Washington, DC 20024
`(202) 783-5070 (Telephone)
`(202) 783-2331 (Facsimile)
`
`Ricardo J. Bonilla
`Texas Bar No. 24082704
`rbonilla@fr.com
`David B. Conrad
`Texas Bar No. 24049042
`conrad@fr.com
`Noel F. Chakkalakal
`Texas Bar No. 24053676
`chakkalakal@fr.com
`Adil A. Shaikh
`Texas Bar No. 24117039
`shaikh@fr.com
`FISH & RICHARDSON P.C.
`1717 Main Street, Suite 5000
`Dallas, Texas 75201
`Tel: (214) 747-5070
`Fax: (214) 747-2091
`
`COUNSEL FOR DEFENDANTS
`BYTEDANCE LTD., BYTEDANCE PTE.
`LTD., AND TIKTOK PTE. LTD.
`
`
`4
`
`
`
`

`

`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a true and correct copy of the above and foregoing
`
`document has been served on November 12, 2024, to all counsel of record who are deemed to have
`
`consented to electronic service.
`
`
`
`
`
`
`
`/s/ Michael J. Ballanco
`Michael J. Ballanco
`
`
`
`
`
`
`
`5
`
`

`

`PRELIMINARY PROPOSED CLAIM CONSTRUCTIONS
`
`
`
`U.S. PATENT NO. 8,756,336
`
`Claim Terms, Phrases, and/or
`Clauses for Construction
`“segmented” / “segmenting”
`
`“Bluetooth enabled mobile device”
`
`“receiving a synchronization
`message” / “sending, a
`synchronization request” / “receiving,
`a synchronization reply”
`
`“using a segmented data transfer
`protocol due in part to present data
`size and data transfer capabilities of
`the Bluetooth enabled mobile device”
`“user identifier”
`
`“resuming, the segmented data
`transfer from the point immediately
`following the last successful receipt of
`the segmented data by the web
`service, for said user identifier.”
`“application layer level”
`
`Preliminary Proposed Constructions
`and Extrinsic Evidence
`“divided/dividing a data file into
`multiple parts”
`“a mobile device that has the ability to
`send and/or receive Bluetooth wireless
`messages”
`
`Indefinite
`
`
`Alternatively,
`
`
`“receiving a message from the web
`server about synchronization of an
`interrupted segmented data transfer”
`
`
`“sending a request to the web service to
`synchronize segmented data transfer”
`
`
`“receiving a reply from the web service
`in response to request to synchronize
`segmented data transfer”
`
`“selecting a segmented data transfer
`protocol based on both the present data
`size and data transfer capabilities of the
`Bluetooth enabled mobile device”
`“a text string that identifies uniquely a
`user of a web service and contains
`sufficient information to authenticate a
`user of the web service.”
`“resuming, the segmented data transfer
`by transferring the next data segment in
`sequence after the last successfully
`transmitted data segment . . .”
`
`Claim
`No(s).
`1
`
`1, 2, 3,
`4
`
`1
`
`1
`
`1, 5
`
`1
`
`“performed by the client application”
`
`1
`
`6
`
`

`

`“after a network connection to the
`web service is restored”
`“segment identifier”
`
`“in response to a network connection
`being restored”
`"a text string that identifies uniquely a
`data segment”
`
`1
`
`1
`
`
`
`
`
`U.S. PATENT NO. 8,862,757
`
`Claim Terms, Phrases, and/or
`Clauses for Construction
`“segmented” / “segmenting”
`
`“Bluetooth enabled mobile device”
`
`“synchronization message” /
`“synchronization request” /
`“synchronization reply”
`
`“wherein said file is segmented in part
`due to size of said file and data transfer
`capabilities of said Bluetooth enabled
`mobile device”
`“user identifier”
`
`“corresponds to the content range”
`
`Preliminary Proposed Constructions
`and Extrinsic Evidence
`“divided/dividing a file into multiple
`parts”
`“a mobile device that has the ability to
`send and/or receive Bluetooth wireless
`messages”
`
`Indefinite
`
`
`Alternatively, “receiving a message
`from the web server about
`synchronization of an interrupted
`segmented data transfer”
`
`
`“sending a request to the web service to
`synchronize segmented data transfer”
`
`
`“receiving a reply from the web service
`in response to request to synchronize
`segmented data transfer”
`“selecting a segmented data transfer
`protocol based on both the present data
`size and data transfer capabilities of the
`Bluetooth enabled mobile device”
`“a text string that identifies uniquely a
`user of a web service and contains
`sufficient information to authenticate a
`user of the web service”
`Indefinite
`
`
`Claim
`No(s).
`1, 8, 15,
`21
`1, 5, 8,
`12, 15,
`18, 21,
`24
`1, 8, 15,
`21
`
`1, 8, 15,
`21
`
`1, 4, 8,
`11, 15,
`17, 21,
`23
`7, 14,
`20, 26
`
`7
`
`

`

`Claim Terms, Phrases, and/or
`Clauses for Construction
`
`“application layer level”
`
`“after a network connection to the web
`service is restored”
`“segment identifier”
`
` U.S. PATENT NO. 8,898,260
`
`Claim Terms, Phrases, and/or
`Clauses for Construction
`“segmented” / “segmenting”
`
`“Bluetooth enabled mobile device”
`
`“synchronization message” /
`“synchronization request” /
`“synchronization reply”
`
`“user identifier”
`
`Preliminary Proposed Constructions
`and Extrinsic Evidence
`Alternatively, “corresponds to the
`location of a portion of content, in
`bytes or other specified unit, in relation
`to the full body of content”
`“performed by the client application”
`
`“in response to a network connection
`being restored”
`"a text string that identifies uniquely a
`data segment”
`
`Preliminary Proposed Constructions
`and Extrinsic Evidence
`“divided/dividing a data file into
`multiple parts”
`“mobile device that has the ability to
`send and/or receive Bluetooth wireless
`messages”
`Indefinite
`
`Alternatively,
`
`
`“receiving a message from the web
`server about synchronization of an
`interrupted segmented data transfer”
`
`
`“sending a request to the web service to
`synchronize segmented data transfer”
`
`
`“receiving a reply from the web service
`in response to request to synchronize
`segmented data transfer”
`“a text string that identifies uniquely a
`user of a web service and contains
`
`8
`
`Claim
`No(s).
`
`1, 8, 15,
`21
`1
`
`1, 7, 8,
`14, 15,
`20, 21,
`26
`
`Claim
`No(s).
`1, 6, 10,
`15
`1, 6, 10,
`15
`
`1, 6, 10,
`15
`
`1, 4, 6,
`8, 10,
`
`

`

`Preliminary Proposed Constructions
`and Extrinsic Evidence
`sufficient information to authenticate a
`user of the web service”
`“making available, at the web service,
`the segmented data received from the
`Bluetooth enabled mobile device for
`public or private consumption over the
`internet”
`
`Claim
`No(s).
`13, 15,
`17
`1, 6, 10,
`15
`
`Claim Terms, Phrases, and/or
`Clauses for Construction
`
`“making available, at the web service,
`the segmented data received from the
`Bluetooth enabled mobile device for
`public or private consumption over the
`internet. . .” / “making available, at the
`web service, the reassembled data
`received from the Bluetooth enabled
`mobile device for public or private
`consumption over the internet.”
`“corresponds to the content range”
`
`“application layer level”
`
`Indefinite
`
`Alternatively, “corresponds to the
`location of a portion of content, in
`bytes or other specified unit, in relation
`to the full body of content”
`“performed by the client application”
`
`1, 6, 10,
`15
`
`1, 5, 6,
`9, 10,
`14, 15
`1, 6, 10,
`15
`1, 6, 10,
`15
`
`“after a network connection to the web
`service is restored”
`“segment identifier”
`
`“in response to a network connection
`being restored”
`"a text string that identifies uniquely a
`data segment”
`
`
`
` U.S. PATENT NO. 8,904,030
`
`Claim Terms, Phrases, and/or
`Clauses for Construction
`
`Claims Elements Must be in an
`Ordered Combination
`“establishing a paired secure
`(Bluetooth) connection between the
`Bluetooth enabled mobile device and a
`Bluetooth enabled data capture device”
`
`Preliminary Proposed
`Constructions and Extrinsic
`Evidence
`the elements must be performed in the
`order they appear in the claims
`“in the condition of having an
`exchanged link key (either before
`connection establishment was
`requested or during connecting phase)
`between the Bluetooth enabled data
`
`Claim
`No(s).
`
`1, 6, 12,
`15
`1, 6, 12,
`15
`
`9
`
`

`

`Claim Terms, Phrases, and/or
`Clauses for Construction
`
`/ “Bluetooth paired wireless
`connection”
`“after the paired secure Bluetooth
`connection is established”
`
`“over the established paired secure
`Bluetooth connection” /
`“Bluetooth paired wireless connection”
`
`
`“supported data capability”
`
`“encrypting, using cryptographic
`encryption key”
`
`“transferring” / “receive” . . .
`“encrypted data”
`
`“cryptographic encryption key”
`
`Preliminary Proposed
`Constructions and Extrinsic
`Evidence
`capture device and the Bluetooth
`enabled mobile device”
`“after the paired connection is
`established and maintained on a
`continuous basis between the
`Bluetooth enabled data capture device
`and the Bluetooth enabled mobile
`device”
`“through the continuous, secure
`Bluetooth connection between the
`Bluetooth enabled data capture device
`and the Bluetooth enabled mobile
`device”
`
`
`“in the condition of having an
`exchanged link key (either before
`connection establishment was
`requested or during connecting phase)
`between the Bluetooth enabled data
`capture device and the Bluetooth
`enabled mobile device”
`“format of data that the Bluetooth
`enabled data capture device is
`configured to send or receive”
`“encryption involving an algorithm
`performed by the Bluetooth enabled
`data capture device”
`“data verified as legitimate by use of
`encryption and decryption involving
`an algorithm performed by the
`Bluetooth enabled data capture
`device”
`“an exchanged link key (either before
`connection establishment was
`requested or during connecting
`phase)”
`
`Claim
`No(s).
`
`1, 6
`
`1, 6, 12,
`15
`
`1, 12
`
`1, 6
`
`1, 6, 12,
`15
`
`1, 6, 12,
`15
`
`10
`
`

`

`Claim Terms, Phrases, and/or
`Clauses for Construction
`
`“Bluetooth enabled data capture
`device”
`
`“detecting and signaling” /
`“determining existence of” /
`“acquiring” / “get” / “obtaining” /
`“transfer” / “encrypting” / “creation of”
`/ “change in status of” . . . “new data”
`“receive[] / “process” / “listen for” /
`“enable” / . . . “event notification”
`
`“Bluetooth enabled mobile device
`listens for the event notification sent
`from the Bluetooth enabled data
`capture device” / “enabling event
`notification listening on the Bluetooth
`enabled mobile device, to listen for
`event notifications sent from the
`Bluetooth enabled data capture device,
`over the established paired secure
`Bluetooth connection”
`“data signal notification(s)”
`
`“user identifier”
`
`“along with”
`
`“creating” / “encrypting” / “get” …
`“new data object”
`
`“HTTP”
`
`Preliminary Proposed
`Constructions and Extrinsic
`Evidence
`“separate and apart from the mobile
`device and has the ability to send and
`receive Bluetooth wireless messages”
`“an indication of the presence of
`newly acquired data by the Bluetooth
`enabled data capture device”
`
`“an indication of the presence of
`newly acquired data on the Bluetooth
`enabled data capture device”
`“an indication of the presence of
`newly acquired data on the Bluetooth
`enabled data capture device”
`
`Claim
`No(s).
`
`1-3, 6-8,
`12, 15
`
`1, 4-6, 9-
`10, 12-17
`
`1, 5, 12,
`14-15, 17
`
`1, 12, 15
`
`“an indication of the presence of
`newly acquired data on the Bluetooth
`enabled data capture device”
`“a text string that identifies uniquely a
`user of a web service and contains
`sufficient information to authenticate a
`user of the web service”
`“at the same time”
`
`“an indication of the presence of
`newly acquired data on the Bluetooth
`enabled data capture device”
`“Hypertext Transfer Protocol,
`excluding Hypertext Transfer Protocol
`Secure”
`
`6, 10
`
`1, 6, 12,
`15
`
`1, 6, 12,
`15
`6, 15
`
`1, 4, 7, 9
`
`11
`
`

`

`
`
`U.S. PATENT NO. 11,659,381
`
`Claim Terms, Phrases, and/or
`Clauses for Construction
`
`Claims Elements Must be in an
`Ordered Combination
`“a mobile software application for a
`Bluetooth enabled cellular phone”
`“establishing a paired Bluetooth
`connection between the Bluetooth
`enabled data capture device and the
`Bluetooth enabled cellular phone”
`
`“after establishing a paired Bluetooth
`connection”
`
`“over the established paired Bluetooth
`connection”
`
`“Bluetooth enabled data capture
`device”
`
`“cryptographically authenticating”
`
`“listen for an event notification”
`
`Preliminary Proposed
`Constructions and Extrinsic
`Evidence
`the elements must be performed in the
`order they appear in the claims
`“software application provided with a
`Bluetooth-enabled cellular phone”
`“in the condition of having an
`exchanged link key (either before
`connection establishment was
`requested or during connecting phase)
`between the Bluetooth enabled data
`capture device and the Bluetooth
`enabled cellular phone”
`“after the paired connection is
`established and maintained on a
`continuous basis between the
`Bluetooth enabled data capture device
`and the Bluetooth enabled cellular
`phone”
`“through the continuous, secure
`Bluetooth connection between the
`Bluetooth enabled data capture device
`and the Bluetooth enabled cellular
`phone”
`“separate and apart from the Bluetooth
`enabled cellular phone and has the
`ability to send and receive Bluetooth
`wireless messages”
`“verified as legitimate by use of
`encryption and decryption involving
`an algorithm performed by the
`Bluetooth enabled data capture device
`and the Bluetooth enabled cellular
`phone”
`“an indication of the presence of
`newly acquired data”
`
`Claim
`No(s).
`
`1, 7, 12
`
`1, 7, 12
`
`1, 7, 12
`
`1, 7, 12
`
`1, 7, 12
`
`1, 7, 12
`
`1, 7, 12
`
`1, 7
`
`12
`
`

`

`Claim Terms, Phrases, and/or
`Clauses for Construction
`
`“detect and receive” / “store the
`received” / “transfer the received” . . .
`“new-data”
`“along with”
`
`“user authentication credential”
`
`“user preference” / “wherein the user
`preference comprises global
`positioning system information”
`
`“online data publishing web service”
`
`“user profile”
`“poll” / “polling”
`
` U.S. PATENT NO. 11,234,121
`
`Claim Terms, Phrases, or Clauses
`for Construction
`
`Claims Elements Must be in an
`Ordered Combination
`“short-range wireless communication
`device”
`
`Claim
`No(s).
`
`1, 3-4, 7,
`8

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