IN THE UNITED STATES DISTRICT COURT
`
`FOR THE EASTERN DISTRICT OF VIRGINIA
`Alexandria Division
`
`Plaintiff
`
`V.
`
`Case No. 1:14-cv-721-GBL—TCB
`
`
`
`SPHERIX INCORPORATED,
`
`
`
`
`VERIZON SERVICES CORR;
`
`VERIZON SOUTH INC.;
`VERIZON VIRGINIA LLC;
`
`VERIZON COMMUNICATIONS INC;
`
`VERIZON FEDERAL INC.;
`VERIZON BUSINESS NETWORK
`
`
`
`
`SERVICES INC;
`
`MCI COMMUNICATIONS SERVICES, INC.
`
`
`
`
`Defendants.
`
`PLAINTIFF SPHERIX INCORPORATED’S
`PROPOSED CONSTRUCTIONS FOR INDENTIFIED CLAIM TERMS
`
`Pursuant to Part VI of the Agreed Proposed Discovery Plan approved in paragraph 1.a. of
`
`the Scheduling Order (DI. 47), Plaintiff Spherix Incorporated, (“Spherix”), by and through its
`
`attorneys, provides the following proposed constructions for each claim term that the parties
`
`identified on October 21, 2014. Spherix’s investigation and discovery in this case is ongoing,
`
`and Spherix expressly reserves the right to revise, amend or supplement its constructions based
`
`on new information received in discovery, as permitted by the Federal Rules of Civil Procedure,
`
`local rules, and/or applicable orders of this Court.
`
`Page 1 0f 6
`
`VERIZON EXHIBIT 1007
`
`Page 1 of 6
`
`VERIZON EXHIBIT 1007
`
`

`

`U.S. Patent No. 6,980,564
`
`
`’564PatentTerm
`'
`g
`,
`j
`'
`:7:
`,
`SProposed on
`‘
`”
`
`
`network interface unit
`
`“a functionally independent customer premises
`module that receives data from and transmits data
`
`Spherix’s Terms
`
`
`
`
`
`to a iven network medium”
`
`
`
`
`
`“a functionally independent customer premises
` service delivery unit
`module that communicates with a separate
`
`network device with which the end user interacts
`
`to receive a network service”
`
`
`
`
`“service delivery units that are in distinct service
`
`family of different types [of service delivery
`
`
`categories, but each of which can physically and
`units]/ different types [of service delivery
`
`
`electrically connect with a common network
`units] in the family
`
`
`
`
`interface unit”
`
`
`network service
`
`
`“a service experienced by an end user that is
`
`delivered over a network b a service rovider”
`
`
`translate(ing)
`
`format
`
`
`
`
`
`“change the arrangement of data from one format
`to another format”
`
`“an arrangement of data into a defined structure
`with delimitin_ elements”
`Verizon ’s Terms
`
`
`
`
`
`
`
`
`
`
`
`an interface for connecting a service
`“an element providing a data connection between
`deliver unit to a _iven medium
`a service deliver unit and a _iven medium”
`
`
`
`
`the connector being a single size that
`“the connector on the network interface unit and
`corresponds to the size of connectors on
`the connector on each type of service delivery
`
`
`each of the types of service delivery units in
`unit in the family are the same size”
`
`
`the famil
`
`
`
`
`media control module
`
`uh sicall searated
`
`“media access control module”
`
`“s-aced aart”
`
`
`?:Spher1x’sfP7r6" oscd Cons ii
`
`V
`
`V Spherix’s Terms
`
`
`
`
`
`
`
`
`US. Patent No. 7,478,167
`
`
`11 Te‘
`92,167‘9Pa
`
`
`
`
`
`V
`
`r
`
`
`
`
`
`
`
`3.
`
`extension to an auto—discovery
`protocol
`
`1
`tunnel-based parameter
`“criteria that may be used in establishing and/or
`
`
`configuring a communication path between two
`
`
`
`provider edge devices”
`
`
`
`
`
`
`VPN capability discovery information
`“a collection of tunnel-based parameters”
`“use of auto-discovery protocols for distributing
`
`
`VPN capability discovery information”
`
`Page 2 0f 6
`
`Page 2 of 6
`
`

`

`
`Spherlx’ProposedC
`
`
`
`Function = distributing at least one VPN tunnel—
`based parameter
`
`
`
`
`
`determine(ing) VPN capability
`A “ascertain(ing) thedesiredVPN capability
`
`
`discovery information including the at
`discovery information for a task or application”
`
`least one tunnel-based parameter
`
`
`
`
`
`auto-discovery means
`Construed under § 112(6):
`
`
`Corresponding Structure = AD component 112
`using information distribution protocols such
`
`as Border Gateway Protocol (BGP), Domain
`
`Name Service (DNS), or Remote Authentication
`
`Dial In User Service (RADIUS) or structural
`
`equivalents thereof
`
`
`
`
`
`tunnel signalling means
`
`Construed under § 112(6):
`
`
`
`
`
`Function = determining VPN capability
`information and negotiating between at least two
`provider edge devices to automatically establish
`and configure a VPN tunnel based on the VPN
`
`capability information.
`
`
`Corresponding Structure = a provider edge device
`102, 104 having tunnel signal components 116,
`
`118 using protocols such as Resource Reservation
`
`Protocol (RSVP), RSVP-Traffic Engineered
`
`(RSVP-TE), Label Distribution Protocol (LDP),
`
`Constraint-based routing LDP (CR-LDP),
`
`Asynchronous Transfer Mode (ATM), Frame
`Relay, or Generic Routing Encapsulation (GRE)
`or structural equivalents thereof
`
`
`
`
`
`
`Verizon ’s Terms
`
`7. Virtual Private Network (VPN) tunnel
`“a communication path that uses a network, such
`
`
`between a first provider edge (PE)
`as the Internet, to provide secure access between
`
`
`device and a second provider edge
`two provider edge routers”
`
`
`(PE) device /
`
`VPN tunnel between the first and
`
`second PE devices
`
`tunnel—based parameter
`
`See above with respect to term number 1,
`“tunnel—based parameter.”
`
`Page 3 of 6
`
`Page 3 of 6
`
`

`

`
`
`
`
`begins”
`
`“non-manually establish and configure” / “non-
`manually configuring”
`
`
`
`
`
`
`
`“extension to an auto-discovery protocol” should
`extension to an auto—discovery
`be construed as above with respect to term
`protocol /
`number 3, “extension to an auto-discovery
`auto-discovery protocol
`
`
`protocol.” The term “auto—discovery protocol”
`does not require construction.
`
`
`
`
`
`
`negotiating
`“process of setting parameters of a
`communication channel between provider edge
`routers before communication over the channel
`
`
`
`“a device used to create, maintain, and/or
`configure one or more VPN tunnels”
`
`
` “auto-discovery means” should be construed as
`
`
`auto-discovery means for distributing
`
`at least one Virtual Private Network
`above with respect to term number 5, “auto—
`discovery means.” The remainder of this claim
`
`
`term does not require construction.
`
`13.
`
`14.
`
`15.
`
`(VPN) tunnel—based parameter to at
`least a first provider edge (PE) device
`and a second provider edge (PE)
`
`device using an extension to an auto-
`
`
` tunnel signalling means for
`
`
`“tunnel signalling means” should be construed as
`above with respect to term number 6, “tunnel
`determining VPN capability discovery
`
`
`signalling means.” The remainder of this claim
`information including the at least one
`
`
`term does not require construction.
`tunnel—based parameter, and
`
`
`
`negotiating between the first and
`
`second PE devices to automatically
`
`establish and configure a VPN tunnel
`
`between the first and second PE
`
`devices based upon the VPN
`
`capability discovery information
`
`
`“auto—discovery mechanism” should be construed
`auto-discovery mechanism for
`to mean “a device used to distribute VCDI
`distributing at least one VPN tunnel-
`
`
`information.” The remainder of this claim term
`based parameter to at least the first
`
`
`does not require construction.
`
`and second PE devices using an
`
`
`extension to an auto-discovery
`
`protocol
`
`
`
`
`
`
`11.
`
`automatically establish and configure/
`automatically configuring
`
`tunnel signalling mechanism
`
`discovery protocol
`
`
`Page 4 0f 6
`
`Page 4 of 6
`
`

`

`“tunnel signalling mechanism” should be
`construed as above with respect to term number
`12, “tunnel signalling mechanism.” The
`remainder of this claim term does not require
`
`construction.
`
`tunnel signalling mechanism adapted
`to determine VPN capability
`discovery information including the at
`least one tunnel—based parameter, and
`negotiate between the first and second
`PE devices to automatically establish
`and configure a VPN tunnel between
`the first and second PE devices based
`
`.
`
`upon the VPN capability discovery
`information
`
`US. Patent No. 8,166,533
`
`Sph erix ’s Terms
`pinhole/ pinhole communication port/ first
`“pinhole”: a dynamic opening in the firewall
`
`communication pinhole
`
`
`
`“pinhole communication port”: a dynamic
`communication port on the firewall
`
`“communication pinhole”: a communication
`d namic o uenin; in the firewall
`
`a trusted entity that is on the external side of the
`packet-based communication network firewall
`along the packet transmission flow (claims 8 and
`15)
`
`a trusted entity that is on the external side of the
`communications network firewall along the
`acket transmission flow (claim 21)
`a communication device that is on the internal
`
`side of the packet-based communication network
`firewall along the packet transmission fiow
`(claim 15)
`
`a communication device that is on the internal
`side of the communications network firewall
`
`acket transmission flow claim 21)
`
`a second entity that is on the internal side of the
`communications network firewall along the
`uacket transmission flow
`
`a trusted entity .
`
`.
`
`. [located] outside [of] the
`
`communication[s] network
`
`a communication device inside [of] the
`communications network
`
`a second entity inside of the
`communications network
`
`Page 5 of 6
`
`Page 5 of 6
`
`

`

`
`
`
`
`
`a trusted entity having an input and an
`
`
`
`
`
`
`m f:,
`" Spherlx’sProposed Instruction 7
`
`a trusted entlty that can receive and transm1t data
`
`.;
`
`’
`
`output
`
`Verizon ’s Terms
`
`communication network gateway
`
`plain and ordinary meaning
`
`firewall
`
`plain and ordinary meaning
`
`trusted entity
`
`plain and ordinary meaning
`
`communication pinhole; pinhole;
`pinhole communication port
`
`See above.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`create pinhole message;
`create pinhole request
`
`
`input of the trusted entity
`
`a packet request to open a pinhole
`
`plain and ordinary meaning
`
`Dated: October 24, 2014
`
`By: Ksenia Takhistova
`
`Erik C. Kane
`VA No. 68294
`
`Attorneyfor Plaintiff, Spherix Incorporated
`Kenyon & Kenyon LLP
`1500 K Street, N.W., Suite 700
`Washington, DC 20005
`Telephone: 202.220.4200
`Facsimile: 202.220.4201
`
`Email: Ekane@kenyon.com
`
`Walter E. Hanley, Jr
`John R. Kenny
`Lewis V. Popovski
`Ksenia Takhistova
`
`Attorneysfor Plaintiff, Spherix Incorporated
`KENYON & KENYON LLP
`
`One Broadway
`New York, NY 10004
`Telephone: 212.425.7200
`Facsimile: 212.425.5288
`
`Email: WHanley@kenyon.00m
`Email: JKennygagkenyoncom
`Email: LPopovsl<i@kenyon.com
`Email: KTal<histova@kenyon.com
`
`Page 6 0f 6
`
`Page 6 of 6
`
`