throbber
Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 1 of 30 PageID #: 4298
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`
`
`
`
`
`§
`
`
`
`
`
`UNILOC USA, INC. et al.,
`
`§
`
`
`§
`
`
`
`
`
`
`§
`
`
`
`Plaintiffs,
`
`§
`
`
`
`
`
`
`§
`v.
`
`
`
`
`
`§
`
`
`
`
`
`SAMSUNG ELECTRONICS AM., INC., §
`
`
`
`
`
`
`§
`
`
`
`Defendant.
`
`§
`
`
`
`
`
`
`§
`v.
`
`
`
`
`
`§
`APPLE INC.
`
`
`
`§
`v.
`
`
`
`
`
`§
`BLACKBERRY CORP. et al.
`
`§
`v.
`
`
`
`
`
`§
`WHATSAPP INC.
`
`
`
`§
`v.
`
`
`
`
`
`§
`FACEBOOK, INC.
`
`
`
`§
`v.
`
`
`
`
`
`§
`GREEN TOMATO LIMITED.
`
`§
`v.
`
`
`
`
`
`§
`PLAYSTATION MOBILE INC.
`
`§
`
`
`Civil Action No. 2:16-cv-731-JRG
`
`Civil Action No. 2:16-cv-732-JRG
`
`JOINT CLAIM CONSTRUCTION CHART
`
`
`Civil Action No. 2:16-cv-642-JRG
`LEAD CASE
`
`Civil Action No. 2:16-cv-638-JRG
`
`Civil Action No. 2:16-cv-639-JRG
`
`Civil Action No. 2:16-cv-645-JRG
`
`Civil Action No. 2:16-cv-728-JRG
`
`Page 1 of 30
`
`Samsung Exhibit 1023
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 2 of 30 PageID #: 4299
`
`Pursuant to P.R. 4-5(d) and the Court’s Sixth Amended Docket Control Order (Dkt. No.
`
`230), Plaintiffs Uniloc USA, Inc. and Uniloc Luxembourg, S.A. (collectively “Uniloc”); and
`
`Consolidated Defendants, Samsung Electronics America, Inc. (“Samsung”); Apple, Inc.
`
`(“Apple”); Blackberry Corporation and Blackberry Limited (collectively “Blackberry”);
`
`WhatsApp, Inc. (“WhatsApp”); Facebook, Inc. (“Facebook”); Green Tomato Ltd. (“Green
`
`Tomato”); and PlayStation Mobile Inc. (“PlayStation Mobile”) (collectively “Defendants”)
`
`submit this joint claim construction chart of disputed constructions of the disputed claim terms of
`
`Uniloc’s U.S. Patent Nos. 7,535,890 (“the ’890 patent”), 8,199,747 (“the ’747 patent”),
`
`8,243,723 (“the ’723 patent”), 8,724,622 (“the ’622 patent”) and 8,995,433 (“the ’433 patent”)
`
`(collectively
`
`the
`
`“Asserted
`
`Patents”).1
`
`
`1 Defendant Green Tomato has yet to make an appearance in this action.
`
`
`
`1
`
`Page 2 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 3 of 30 PageID #: 4300
`
`The parties have yet to reach agreement as to the construction of the following claim terms, phrases and clauses recited in one
`
`or more of the patents-in-suit:2
`
`
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`connection object messages
`
`‘622 patent claim 24, 25, 26
`
`[AGREED]
`
`[AGREED]
`
`“messages containing data
`representing the state of the
`connection and code (one or
`more methods) for establishing
`and maintaining the logical
`connections between an instant
`voice messaging server and
`instant voice messaging clients”
`
`
`2 Uniloc has not asserted infringement of every patent against every defendant. Similarly, as to a given patent, not every claim is
`asserted against every defendant accused of infringing that patent. As such, only those Defendants who are currently accused of
`infringement of a given claim propose construction of a term within that claim. The remaining Defendants reserve their right to
`address those claims at the appropriate time, should they subsequently be accused of infringement.
`
`
`
`1
`
`Page 3 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 4 of 30 PageID #: 4301
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`“instant messaging software or
`hardware”
`
`Dkt. No. 211 (Uniloc’s
`Opening CC Br.) at 4-5.
`Dkt. No. 223 (Uniloc’s Reply
`CC Br.) at 1-2.
`
`
`
`“instant voice messaging
`terminal connected over a
`network to a server”3
`
`Dkt. No. 220 (Defs.’ Responsive
`CC Br.) at 12-14.
`
`“client”
`
`‘890 patent claim 1, 4, 6, 9,
`14, 15, 18, 20, 23, 28, 29, 32,
`34, 37, 40, 41, 43, 51, 52, 54,
`57, 62, 63, 65, 68, 69
`‘723 patent claim 1
`’622 patent claim 3, 24, 27,
`38
`’433 patent claim 1, 9
`
`
`3 Defendants Responsive Brief stated “To the extent Uniloc’s objection is to the wording ‘connected over a network to a server,’
`similar wording also would properly capture the client/server context such as ‘that connects over a network to a server’ or ‘for
`connecting over a network to a server.’” Dkt. No. 220 at 13.
`
`
`
`2
`
`Page 4 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 5 of 30 PageID #: 4302
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`“a voice message that is
`capable of being delivered
`immediately”
`
`Dkt. No. 211 at 5-7.
`Dkt. No. 223 at 2.
`
`
`
`“voice message to be delivered
`immediately to an available
`recipient”
`
`Dkt. No. 220 at 1-4.
`
`“instant voice message”
`
`‘890 patent claim 1, 5, 6, 9,
`14, 15, 19, 20, 23, 28, 29, 33,
`34, 37, 40, 41, 42, 43, 51, 53,
`54, 57, 62, 64, 65, 68, 69
`‘747 patent claim 1, 2, 3, 12,
`13
`‘723 patent claim 1, 2, 3
`‘622 patent claim 3, 4, 6, 7,
`8, 10, 11, 12, 13, 14, 15, 16,
`17, 18, 19, 21, 22, 23, 24, 26,
`27, 28, 29, 30, 31, 32, 33, 34,
`35, 36, 37, 38, 39
`‘433 patent claim 1, 2, 3, 4,
`5, 7, 8, 9, 11, 12, 14, 16, 17,
`18, 21, 25, 26
`
`
`
`3
`
`Page 5 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 6 of 30 PageID #: 4303
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`“messaging of voice messages
`that are capable of being
`delivered immediately”
`
`Dkt. No. 211 at 5-7.
`Dkt. No. 223 at 2.
`
`“messaging wherein a voice
`message is to be delivered
`immediately to an available
`recipient”
`
`Dkt. No. 220 at 1-4.
`
`“component that provides
`connectivity to the network”
`
`Dkt. No. 211 at 7.
`
`Plain and ordinary meaning.
`Alternatively, “component or
`functionality that provides
`connectivity to the network”
`
`Dkt. No. 220 at 16.
`
`Indefinite
`
`Dkt. No. 220 at 14-16.
`
`“instant voice messaging”
`
`’890 patent claim 1, 14, 28,
`40, 51, 62
`’747 patent claim 1, 2, 3, 12,
`13
`’723 patent claim 1-3
`’622 patent claim 13, 14, 16-
`19, 21, 22, 27, 28, 31-34, 38
`’433 patent claim 1, 9
`
`“network interface”
`
`‘622 patent claim 3, 24, 27,
`38
`‘433 patent claim 1
`
`“node”
`
`‘747 patent claim 2
`‘723 patent claim 1
`
`
`“potential recipient”
`
`Dkt. No. 211 at 7-8.
`Dkt. No. 223 at 2-3.
`
`
`
`
`
`4
`
`
`
`
`
`
`
`Page 6 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 7 of 30 PageID #: 4304
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`the server temporarily
`storing the instant voice
`message if a selected
`recipient is unavailable /
`temporarily storing at the
`server the instant voice
`message if a selected
`recipient is unavailable /
`temporarily storing the
`instant voice message at the
`external server if a selected
`recipient is unavailable /
`if there is no connection
`with the one of the plurality
`of instant voice message
`client system [sic] identified
`as the recipient, the instant
`voice message is stored /
`temporarily storing the
`instant voice message if a
`recipient is unavailable /
`the instant voice message is
`temporarily stored when at
`least one recipient is
`unavailable /
`stores the instant voice
`message for the one or
`more intended recipients
`
`
`
`Plain meaning
`
`Dkt. No. 211 at 8-10.
`Dkt. No. 223 at 3-5.
`
`
`
`“[the server] temporarily storing
`the instant voice message only if
`a selected recipient is
`unavailable”
`
`Dkt. No. 220 at 7-9.
`
`5
`
`Page 7 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 8 of 30 PageID #: 4305
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`Terms, Phrases and
`Clauses
`who are not currently
`available /
`temporarily storing the
`instant voice message if a
`selected recipient is
`unavailable
`
`‘890 patent claim 1, 14, 28,
`40, 51, 62
`‘622 patent claim 11
`‘723 patent claim 1
`‘747 patent claim 1, 2, 3
`‘433 patent claim 26
`
`
`
`
`
`
`6
`
`Page 8 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 9 of 30 PageID #: 4306
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`delivering the stored
`instant voice message to the
`selected recipient once the
`selected recipient becomes
`available /
`delivering from the server
`the stored instant voice
`message to the selected
`recipient once the selected
`recipient becomes available
`/
`delivered when the one of
`the plurality of instant
`voice message client
`systems identified as the
`recipient re-established
`[sic] a connection /
`delivering the stored
`instant voice message to the
`recipient once the recipient
`becomes available /
`delivers the instant voice
`message to the one or more
`intended recipients who are
`not currently available
`when the instant voice
`messaging server
`determines that the not
`currently available one or
`
`
`
`Plain meaning
`
`Dkt. No. 211 at 10-11.
`Dkt. No. 223 at 5-6.
`
`
`
`“pushing the stored instant voice
`message to the selected recipient
`when the selected recipient is
`determined to be available”
`
`Dkt. No. 220 at 9-12.
`
`7
`
`Page 9 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 10 of 30 PageID #: 4307
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`Plain meaning
`
`Dkt. No. 211 at 11-12.
`
`
`
`available/availability: “connected
`to the [network/server]”
`unavailable: “disconnected from
`the [network/server]”
`
`Dkt. No. 220 at 4-7.
`
`Terms, Phrases and
`Clauses
`more intended recipients
`become available /
`receiving a temporarily
`stored instant voice
`message when a recipient
`becomes available
`
`‘890 patent claim 1, 14, 28,
`40, 51, 62
`‘622 patent claim 11
`‘723 patent claim 1
`‘433 patent claim 26
`‘747 patent claim 1, 2, 3
`
`available / unavailable /
`availability
`
`‘890 patent claim 1, 5, 14,
`19, 28, 33, 40, 42, 51, 53, 62,
`64
`‘723 patent claim 1
`‘747 patent claim 1, 2, 3
`‘433 patent claim 25
`
`
`
`8
`
`Page 10 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 11 of 30 PageID #: 4308
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`object field
`
`‘622 patent claim 3
`
`action field
`
`‘622 patent claim 4
`
`identifier field
`
`‘622 patent claim 6
`
`source field
`
`‘622 patent claim 7
`
`destination field
`
`‘622 patent claim 8
`
`
`
`“A block of data being carried
`by the message object”
`
`Dkt. No. 211 at 12-14.
`
`Plain and ordinary meaning
`
`Dkt. No. 220 at 16-18.
`
`“A block of data identifying
`permitted actions”
`
`Dkt. No. 211 at 12-14.
`
`“A block of data uniquely
`identifying the message”
`
`Dkt. No. 211 at 12-14.
`
`“A block of data with a
`globally unique identifier of
`the sender”
`
`Dkt. No. 211 at 12-14.
`
`“A block of data with the
`globally unique identifier of
`the intended recipient”
`
`Dkt. No. 211 at 12-14.
`
`Plain and ordinary meaning
`
`Dkt. No. 220 at 16-18.
`
`Plain and ordinary meaning
`
`Dkt. No. 220 at 16-18.
`
`Plain and ordinary meaning
`
`Dkt. No. 220 at 16-18.
`
`Plain and ordinary meaning
`
`Dkt. No. 220 at 16-18.
`
`9
`
`
`
`
`
`
`
`
`
`
`
`Page 11 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 12 of 30 PageID #: 4309
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`one or more external
`recipients connected to the
`external and transmits . . .
`
`‘890 patent claim 29
`
`“document handler”
`
`‘622 patent claim 27
`‘433 patent claim 14
`
`
`
`
`
`
`
`
`
`Plain meaning
`
`Dkt. No. 211 at 14.
`
`Indefinite
`
`Dkt. No. 220 at 18-19.
`
`This term is subject to 35 U.S.C.
`§ 112(6), and should be analyzed
`in the context of the “document
`handler” terms discussed below.
`
`Dkt. No. 220 at 25-27.
`
`“component of the client
`platform that oversees the
`retrieving, sending, receiving
`and storing of one or more
`documents (or files) attached
`to instant voice messages
`from/to the one or more
`selected IVM recipients that
`may be communicating with
`the IVM client”
`
`Dkt. No. 211 at 15-17.
`Dkt. No. 223 at 6-10.
`
`
`
`10
`
`Page 12 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 13 of 30 PageID #: 4310
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`
`
`Subject to 35 U.S.C. § 112(6):
`Function: create a link between
`the instant voice message and the
`one or more files.
`Structure: Indefinite.
`
`Dkt. No. 220 at 25-27.
`
`document handler to create
`a link between the instant
`voice message and the one
`or more files
`
`‘433 patent claim 14
`
`Plain meaning and not subject
`to 35 U.S.C. § 112(6)
`
`If this term is found to be
`subject to § 112(6), then—
`
` Function: “create a link
`between the instant voice
`message and the one or more
`files”
`
` Structure: The document
`handler 306 is a component
`that oversees the retrieving,
`sending, receiving and storing
`of one or more documents (or
`files) attached to instant voice
`messages from/to the one or
`more selected IVM recipients
`that may be communicating
`with the IVM client 208.
`When an instant voice
`message is to be transmitted to
`the one or more IVM
`recipients, one or more
`documents may be attached to
`the instant voice message to
`be, stored or displayed by the
`
`
`
`11
`
`Page 13 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 14 of 30 PageID #: 4311
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`one or more selected IVM
`recipients, as described in the
`‘622 patent at 12:24-34 and
`Fig. 3, and/or equivalents.
`
`Dkt. No. 211 at 17-19.
`Dkt. No. 223 at 6-10.
`
`
`
`12
`
`
`
`
`
`Page 14 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 15 of 30 PageID #: 4312
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`
`
`Subject to 35 U.S.C. § 112(6):
`Function: attaching one or more
`files to the instant voice message.
`Structure: Indefinite.
`
`Dkt. No. 220 at 25-27.
`
`document handler system /
`document handler system
`for attaching one or more
`files to the instant voice
`message
`
`‘622 patent claim 27
`
`Plain meaning and not subject
`to 35 U.S.C. § 112(6)
`
`If this term is found to be
`subject to § 112(6), then—
`
` Function: “attaching one or
`more files to the instant voice
`message”
`
` Structure: The document
`handler 306 is a component
`that oversees the retrieving,
`sending, receiving and storing
`of one or more documents (or
`files) attached to instant voice
`messages from/to the one or
`more selected IVM recipients
`that may be communicating
`with the IVM client 208.
`When an instant voice
`message is to be transmitted to
`the one or more IVM
`recipients, one or more
`documents may be attached to
`the instant voice message to
`be, stored or displayed by the
`one or more selected IVM
`
`
`
`13
`
`Page 15 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 16 of 30 PageID #: 4313
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`recipients, as described in the
`‘622 patent at 12:24-34 and
`Fig. 3, and/or equivalents.
`
`Dkt. No. 211 at 17-19.
`Dkt. No. 223 at 6-10.
`
`
`
`14
`
`
`
`
`
`Page 16 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 17 of 30 PageID #: 4314
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`
`
`Subject to 35 U.S.C. § 112(6):
`Function: transmitting the instant
`voice message over the packet-
`switched network [via the
`network interface].
`Structure: Indefinite.
`
`Dkt. No. 220 at 23-25.
`
`messaging system for
`transmitting the instant
`voice message over the
`packet-switched network
`[via the network interface]
`
`‘622 patent claim 27, 38
`‘433 patent claim 1, 9
`
`Plain meaning and not subject
`to 35 U.S.C. § 112(6)
`
`If this term is found to be
`subject to § 112(6), then—
`
` Function: “transmitting the
`instant voice message over the
`packet-switched network via
`the network interface”
`
` Structure: The messaging
`system 320 is a component
`that, together with the client
`engine 304, communicates via
`standard inter-process
`communication. The
`messaging system 320 and
`client engine 304 also
`communicate with the IVM
`server 202 over the network
`interface via the network 204,
`as described in the ‘622 patent
`at 12:21-26 and Fig. 3, and/or
`equivalents. Alternatively, the
`messaging system 436
`component and the server
`engine 304 communicate via
`
`
`
`15
`
`Page 17 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 18 of 30 PageID #: 4315
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`standard inter-process
`communication. The
`messaging system 436 and the
`server engine are also able to
`communicate with the IVM
`clients 206, 208 over the
`network interface via the
`network 204. The messaging
`system 436 communicates to
`the server engine 404 via
`message objects, as described
`in the ‘622 patent at 13:55-
`14:5 and Fig. 4, and/or
`equivalents.
`
`Dkt. No. 211 at 20.
`Dkt. No. 223 at 6-10.
`
`
`
`
`
`
`
`16
`
`Page 18 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 19 of 30 PageID #: 4316
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`
`
`Subject to 35 U.S.C. § 112(6):
`Function: creating an audio file
`for the instant voice message
`based on input received via an
`audio input device coupled to the
`client device.
`Structure: Indefinite.
`
`Dkt. No. 220 at 30.
`
`audio file creation system
`creating an audio file for
`the instant voice message
`based on input received via
`an audio input device
`coupled to the client device.
`. .
`
`‘622 patent claim 18
`‘433 patent claim 4
`
`
`Plain meaning and not subject
`to 35 U.S.C. § 112(6)
`
`If this term is found to be
`subject to § 112(6), then—
`
` Function: “creating an
`audio file for the instant voice
`message based on input
`received via an audio input
`device coupled to the client
`device”
`
` Structure: The audio file
`creation 312 component
`creates an instant voice
`message as audio file 210, and
`is responsible for receiving
`input speech for the instant
`voice message from audio
`input device 212 or via
`network 204 and storing the
`input speech into audio file
`210, as described in the ‘622
`patent at 12:40-44 and Fig. 3,
`and/or equivalents.
`
`
`
`
`17
`
`Page 19 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 20 of 30 PageID #: 4317
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`
`
`The phrase “client platform
`system” should be construed in
`the context of the full claim
`limitation, which is subject to 35
`U.S.C. § 112(6):
`Function: generating an instant
`voice message.
`
`
`Structure: Indefinite.
`
`
`Dkt. No. 220 at 20-23.
`
`Terms, Phrases and
`Clauses
`
`“client platform system”
`(Uniloc)
`
`“client platform system for
`generating an instant voice
`message” (Defendants)
`
`‘622 patent claim 27, 38
`‘433 patent claim 1, 9, 18, 21
`
`Uniloc’s Proposed
`Construction
`Dkt. No. 211 at 21.
`Dkt. No. 223 at 6-10.
`
`“the system of the client
`engine which controls other
`components used to generate
`an instant voice message” and
`not subject to 35 U.S.C. §
`112(6)
`
`If this term is found to be
`subject to § 112(6), then—
`
` Function: “generating an
`instant voice message”
` Structure: The client
`platform 302 includes a client
`engine 304, which controls
`other components, including
`the document handler 306, file
`manager 308, audio file
`creation 312, signal
`processing 314, encryption /
`decryption 316, and
`compression / decompression
`318, as described by the ‘622
`patent at 12:17-21 and in Fig.
`3, and/or equivalents.
`
`
`
`18
`
`Page 20 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 21 of 30 PageID #: 4318
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`“communication platform
`system” (Uniloc)
`
`“communication platform
`system maintaining
`connection information for
`each of the plurality of
`instant voice message client
`systems indicating whether
`there is a current
`connection to each of the
`plurality of instant voice
`message client systems”
`(Defendants)
`
`‘622 patent claim 3, 11, 12,
`24, 26.
`
`
`Dkt. No. 211 at 22-23.
`Dkt. No. 223 at 6-10.
`
`“the system of the server
`which relays communications
`and/or tracks client connection
`information” and not subject
`to 35 U.S.C. § 112(6)
`
`If this term is found to be
`subject to § 112(6), then—
`
` Function: “maintaining
`connection information for
`each of the plurality of instant
`voice message client systems
`indicating whether there is a
`current connection to each of
`the plurality of instant voice
`message client systems”
`
` Structure: The
`communication platform 402
`includes a server engine 404,
`client manager 406, station
`manager 408, gateway
`
`
`
`The phrase “communication
`platform system” should be
`construed in the context of the
`full claim limitation, which is
`subject to 35 U.S.C. § 112(6):
`Function: maintaining
`connection information for each
`of the plurality of instant voice
`message client systems
`indicating whether there is a
`current connection to each of the
`plurality of instant voice message
`client systems.
`Structure: Indefinite.
`
`
`Dkt. No. 220 at 27-28.
`
`
`
`19
`
`Page 21 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 22 of 30 PageID #: 4319
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`manager 410, database
`manager 412 that accesses
`database 414, supplemental
`servers 416, as well as a
`control layer 426, as described
`in the ‘622 patent at 13:49-55
`and Fig. 4, and/or equivalents.
`Alternatively, the
`communication platform 702
`includes a server engine 704,
`which controls a user manager
`706, a local server manager
`708, and a storage manager
`710, as described in the ‘622
`patent at 22:40-43 and Fig. 7,
`and/or equivalents.
`Alternatively, the
`communication platform 802
`includes a server engine 804,
`which controls a local server
`manager 806, a user manager
`808, and a transport manager
`810, as described in the ‘622
`patent at 23:3-6 and Fig. 8,
`and/or equivalents.
`
`Dkt. No. 211 at 23-26.
`Dkt. No. 223 at 6-10.
`
`
`
`20
`
`
`
`
`
`Page 22 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 23 of 30 PageID #: 4320
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`
`
`The phrase “file manager
`system” should be construed in
`the context of the full claim
`limitation, which is subject to 35
`U.S.C. § 112(6):
`Function: [performing at least
`one of] storing, deleting and
`retrieving the instant voice
`messages from the message
`database in response to a user
`request.
`Structure: Indefinite.
`
`Dkt. No. 220 at 28-30.
`
`“file manager system”
`(Uniloc)
`
`“a file manager system
`performing at least one of
`storing, deleting and
`retrieving the instant voice
`messages from the message
`database” (Defendants)
`
`“a file manager system
`storing, deleting, and
`retrieving” (Defendants)
`
`‘622 patent claim 17, 31
`‘433 patent claim 1
`
`“system that services requests
`regarding files” and not
`subject to 35 U.S.C. § 112(6)
`
`If this term is found to be
`subject to § 112(6), then—
`
` Function: “[performing at
`least one of] storing, deleting
`and retrieving the instant
`voice messages from the
`message database”
`
` Structure: The file manager
`is a component which
`accesses a message database
`310, in which both the
`received and recorded instant
`voice messages are
`represented as database
`records, each record
`comprising a message
`identifier and the instant voice
`message. The file manager
`308 services requests from the
`user to record, delete or
`retrieve messages to/from the
`message database 310, as
`
`
`
`21
`
`Page 23 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 24 of 30 PageID #: 4321
`
`Defendants’ Proposed
`Construction
`
`Court’s
`Construction
`
`Terms, Phrases and
`Clauses
`
`Uniloc’s Proposed
`Construction
`described in the ‘622 patent at
`12:30-40, 12:63-67 and Fig. 3,
`and/or equivalents.
`
`Dkt. No. 211 at 26-27.
`Dkt. No. 223 at 6-10.
`
`
`
`
`
`22
`
`Page 24 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 25 of 30 PageID #: 4322
`
`Date: June 9, 2017
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`/s/ Aaron S. Jacobs
`Paul J. Hayes
`Kevin Gannon
`Aaron S. Jacobs
`PRINCE LOBEL TYE LLP
`One International Place, Suite 3700
`Boston, MA 02210
`Tel: (617) 456-8000
`Email: phayes@princelobel.com
`Email: kgannon@princelobel.com
`Email: ajacobs@princelobel.com
`
`
`Edward R. Nelson III
`ed@nelbum.com
`Texas State Bar No. 00797142
`Anthony M. Vecchione
`anthony@nelbum.com
`Texas State Bar No. 24061270
`NELSON BUMGARDNER PC
`3131 West 7th Street, Suite 300
`Fort Worth, TX 76107
`Tel: (817) 377-9111
`Fax: (817) 377-3485
`
`ATTORNEYS FOR THE PLAINTIFFS
`
`
`
`
`
`By: /s/ Srecko “Lucky” Vidmar
`
`Clayton C. James (CO #26110)
`clay.james@hoganlovells.com
`Srecko “Lucky” Vidmar (CO #34921)
`lucky.vidmar@hoganlovells.com
`HOGAN LOVELLS US LLP
`1601 Wewatta Street, Suite 900
`Denver, CO 80202
`Telephone:
`(303) 899-7300
`Facsimile:
`(303) 899-7333
`
`
`
`
`
`
`Page 25 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 26 of 30 PageID #: 4323
`
`
`
`
`
`Melissa R. Smith (TX #24001351)
`melissa@gillamsmithlaw.com
`GILLAM & SMITH, LLP
`303 South Washington Avenue
`Marshall, Texas 75670
`Telephone: (903) 934-8450
`Facsimile: (903) 934-9257
`
`Counsel for Defendant Apple Inc.
`
`
`/s/ Jason W. Cook
`Jason W. Cook
`Texas State Bar No. 24028537
`Shaun W. Hassett
`Texas State Bar No. 24074372
`MCGUIREWOODS LLP
`2000 McKinney Avenue
`Suite 1400
`Dallas, Texas 75201
`Tel: 214-932-6400
`Fax: 214-932-6499
`jcook@mcguirewoods.com
`shassett@mcguirewoods.com
`
`George B. Davis (VA 83165)
`MCGUIREWOODS LLP
`Gateway Plaza
`800 East Canal Street
`Richmond, VA 23219-1129
`Tel: (804) 775-1000
`Fax: (804) 225-5377
`gdavis@mcguirewoods.com
`
`Attorneys for Defendants BlackBerry Corporation
`and BlackBerry Limited.
`
`
`
`
`
`
`
`
`
`
`
`
`Page 26 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 27 of 30 PageID #: 4324
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`GREENBERG TRAURIG, LLP
`
`By: /s/ Stephen K. Shahida
`Mark G. Davis
`Bar No. 412228 (DC)
`Ronald J. Pabis
`Bar No. 473023 (DC)
`Stephen K. Shahida
`Bar No. 454970 (DC)
`Patrick J. McCarthy
`Bar No. 990490 (DC)
`Myomi T. Coad
`Bar No. 1017904 (DC)
`Minsoo Kim
`Bar No. 5328026 (NY)
`GREENBERG TRAURIG, LLP
`2101 L. Street, N.W., Suite 1000
`Washington, DC 20037
`Telephone: (202) 331-3104
`Facsimile: (202) 331-3101
`Email: davisma@gtlaw.com
`
`pabisr@gtlaw.com
`shahidas@gtlaw.com
`mccarthyp@gtlaw.com
`coadm@gtlaw.com
`
` kimmin@gtlaw.com
`
`Rene Trevino
`Bar No. 24051447 (TX)
`GREENBERG TRAURIG, LLP
`1000 Louisiana Street, Suite 1700
`Houston, TX 77002
`Telephone: (713) 374-3500
`Facsimile: (713) 374-3505
`Email: trevinor@gtlaw.com
`
`Richard Edlin
`Bar No. 2051696 (NY)
`GREENBERG TRAURIG, LLP
`MetLife Building
`200 Park Avenue
`New York, NY 10002
`Telephone: (212) 801-9200
`Facsimile: (212) 801-6400
`Email: edlinr@gtlaw.com
`
`
`
`Page 27 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 28 of 30 PageID #: 4325
`
`
`
`
`Melissa R. Smith (TX #24001351)
`melissa@gillamsmithlaw.com
`GILLAM & SMITH, LLP
`303 South Washington Avenue
`Marshall, Texas 75670
`Telephone: (903) 934-8450
`Facsimile: (903) 934-9257
`
`Attorneys for Defendant Samsung Electronics
`America, Inc.
`
`
`/s/ Heidi L. Keefe
`
`Deron Dacus (Texas Bar No. 00790553)
`The Dacus Firm, P.C.
`821 ESE Loop 323, Suite 430
`Tyler, TX 75701
`Phone: (903) 705-1117
`Fax: (903) 581-2543
`ddacus@dacusfirm.com
`
`Heidi L. Keefe (CA Bar 178960)
`Mark R. Weinstein (CA Bar 193043)
`Lowell D. Mead (CA Bar 223989)
`COOLEY LLP
`Five Palo Alto Square
`3175 Hanover Street
`Palo Alto, CA 94304
`Phone: (650) 843-5000
`Fax: (650) 857-0663
`hkeefe@cooley.com
`mweinstein@cooley.com
`
`Phillip E. Morton (DC Bar No. 1032243)
`James P. Hughes (DC Bar No. 974653)
`COOLEY LLP
`1299 Pennsylvania Ave., NW
`Washington, DC 20004
`Phone: (202) 842-7800
`Fax: (202) 842-7899
`pmorton@cooley.com
`jhughes@cooley.com
`
`Attorneys For Defendants
`Facebook, Inc. and WhatsApp Inc.
`
`
`
`
`
`Page 28 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 29 of 30 PageID #: 4326
`
`
`
`
`ERISE IP, P.A.
`
`By: /s/ Abran J. Kean
`Abran J. Kean (CO # 44660)
`Michelle A. Callaghan, pro hac vice (CO #50082)
`Erise IP, P.A.
`5600 Greenwood Plaza Blvd, Suite 200
`Greenwood Village, CO 80111
`T: (913) 777-5600
`F: (913) 777-5601
`abran.kean@eriseip.com
`michelle.callaghan@eriseip.com
`
`Eric A. Buresh (KS #19895)
`Erise IP, P.A.
`6201 College Blvd, Suite 300
`Overland Park, KS 66211
`T: (913) 777-5600
`F: (913) 777-5601
`eric.buresh@eriseip.com
`
`Counsel for Defendant PlayStation Mobile Inc.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 29 of 30
`
`

`

`Case 2:16-cv-00642-JRG Document 266 Filed 06/09/17 Page 30 of 30 PageID #: 4327
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that, on June 9, 2017, I filed a true and correct copy of the foregoing
`
`document via the Court’s CM/ECF system, which will serve the same on all counsel of record.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Srecko “Lucky” Vidmar
`Srecko “Lucky” Vidmar
`
`
`
`
`
`
`
`
`
`
`
`Page 30 of 30
`
`

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