throbber

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`_____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`_____________
`
`GOOGLE LLC,
`Petitioner,
`
`v.
`
`SECURE COMMUNICATION TECHNOLOGIES, LLC,
`Patent Owner.
`_____________
`
`Case No. IPR2025-01183
`Patent No. 11,687,971
`_____________
`
`PETITION FOR INTER PARTES REVIEW
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. § 42.1 et seq
`
`
`
`

`

`
`
`TABLE OF CONTENTS
`
`INTRODUCTION ............................................................................................. 1
`I.
`II. STANDING CERTIFICATION ........................................................................ 5
`III. UNPATENTABILITY GROUNDS .................................................................. 6
`IV. ’971 PATENT .................................................................................................... 6
`A. Background .................................................................................................. 6
`B. Prosecution History ..................................................................................... 8
`C. POSITA ....................................................................................................... 9
`V. CLAIM INTERPRETATION ........................................................................... 9
`VI. GROUND 1: EAGLE IN VIEW OF BEHRENS AND OLKKONEN
`RENDERS OBVIOUS THE CHALLENGED CLAIMS ................................. 9
`A. Eagle (EX1005) ........................................................................................... 9
`B. Behrens (EX1006) ..................................................................................... 11
`C. Olkkonen (EX1007) .................................................................................. 12
`D. Eagle in view of Behrens, in further view of Olkkonen ............................ 13
`1. Receiving different identifying information from the same
`device ................................................................................................... 16
`2. Filtering beacon service identifiers ..................................................... 19
`3. Actions ................................................................................................. 26
`E. Mapping to Challenged Claims ................................................................. 29
`1. Claim 1 ................................................................................................ 29
`a. [1.PRE] “A method comprising:” ............................................... 29
`b. [1.A.I] “receiving, at a wireless device, via a short range
`wireless protocol, a first plurality of beacon transmissions,
`each beacon transmission comprising three fields” .................... 30
`c. [1.A.II] “(a) a MAC address,” .................................................... 33
`d. [1.A.III] “(b) a unique identifier, wherein the unique
`identifier of each respective beacon transmission does not
`directly identify a location of a beacon transmitter, and” ........... 34
`
`- 1 -
`
`

`

`
`
`i.
`
`j.
`
`f.
`
`e. [1.A.IV] “(c) a beacon service identifier, wherein the
`beacon service identifier of each respective beacon
`transmission identifies that the unique identifier is relevant
`to stored information associated with a wireless beacon
`service,” ....................................................................................... 36
`[1.A.V] “wherein the stored information is not otherwise
`accessible to the wireless device utilizing the short range
`wireless protocol;” ...................................................................... 38
`g. [1.B.I] “receiving, at the wireless device via a second
`wireless protocol, the stored information from one or more
`servers,” ....................................................................................... 39
`h. [1.B.II] “the stored information relating to a particular
`entity or object associated with a first unique identifier,
`and” ............................................................................................. 40
`[1.B.III] “wherein the second wireless protocol is different
`from the short range wireless protocol;” ..................................... 41
`[1.C] “causing selection of one or more of the unique
`identifiers from the first plurality of beacon transmissions,
`by filtering the beacon transmissions which include a
`particular beacon service identifier indicating that a
`particular received beacon transmission is associated with
`a particular wireless beacon service; and” .................................. 41
`k. [1.D] “taking first further action relating to the stored
`information, if the first unique identifier is present among
`the selected one or more unique identifiers.” ............................. 42
`2. Claim 2 ................................................................................................ 43
`a. [2.PRE] “The method of claim 1, wherein the receiving, at
`the wireless device, via a short range wireless protocol, of
`the first plurality of beacon transmissions occurs in a first
`time period, and” ......................................................................... 43
`b. [2.A] “wherein the method further comprises, during a
`second time period:” ................................................................... 44
`c. [2.B.I] “receiving, at the wireless device, via a short range
`wireless protocol, a second plurality of beacon
`transmissions, each of the second plurality of beacon
`transmissions comprising three fields” ....................................... 45
`
`- ii -
`
`

`

`
`
`f.
`
`d. [2.B.II] “(a) a MAC address,” ..................................................... 45
`e. [2.B.III] “(b) a unique identifier, wherein the unique
`identifier of each respective beacon transmission does not
`directly identify a location of a beacon transmitter, and” ........... 46
`[2.B.IV] “(c) a beacon service identifier, wherein the
`beacon service identifier of each respective beacon
`transmission identifies that the unique identifier is relevant
`to stored information associated with a wireless beacon
`service,” ....................................................................................... 46
`g. [2.B.V] “wherein the stored information is not accessible
`to the wireless device utilizing the short range wireless
`protocol;” ..................................................................................... 47
`h. [2.C] “causing selection of one or more of the unique
`identifiers from the second plurality of beacon
`transmissions, by filtering the beacon transmissions which
`include the same particular beacon service identifier
`indicating that the particular received beacon transmission
`is associated with the same particular wireless beacon
`service; and” ................................................................................ 47
`[2.D.I] “taking second further action relating to the stored
`information, if a second unique identifier is present among
`the one or more unique identifiers selected from the
`second plurality of beacon transmissions,” ................................. 48
`[2.D.II] “wherein the first unique identifier and the second
`unique identifier are both associated with the same
`particular entity or object, and wherein the second unique
`identifier is not equal to the first unique identifier, and
`further wherein the received beacon transmissions
`including the first and second unique identifiers are
`received from a same transmitting device.” ................................ 48
`3. Claim 3 ................................................................................................ 49
`a. [3.A] “The method of claim 2 wherein the MAC address
`received in a beacon transmission including the second
`unique identifier is different from the MAC address
`received in a beacon transmission including the first
`unique identifier, but each such beacon transmission
`includes the same particular beacon service identifier, and” ...... 49
`
`i.
`
`j.
`
`- iii -
`
`

`

`
`
`b. [3.B] “wherein a plurality of beacon transmissions
`including the particular service identifier and the first
`unique identifier are received in the first time period, and
`no beacon transmissions including the same particular
`service identifier and the second unique identifier are
`received in the first time period.” ............................................... 51
`4. Claims 4/40/53: “[Claim 3][Claim 37][Claim 53] wherein the
`second further action is based upon a function currently being
`performed on a device associated with the wireless beacon
`service.” ............................................................................................... 52
`5. Claims 5/41/54: “[Claim 4][Claim 40][Claim 53] wherein the
`function is related to a current phone call, music being played, a
`video being played, a multi-player game, or a shared
`application.” ........................................................................................ 54
`6. Claims 6/29/55/56: “[Claim 2][Claim 1][Claim 51][Claim 50]
`wherein the first [or the second] further action is [additionally]
`related to receiving advertising information for presentation to a
`user of the wireless device, based upon the first [or the second]
`unique [identifier][identifiers], or [based upon] information
`derived from the first [or second] unique identifier.” ......................... 55
`7. Claims 7/30/42/57/58: “[Claim 2][Claim1][Claim 37][Claim
`51][Claim 52] wherein [one or more of] the first [and the
`second] further action [additionally] includes
`[receiving][causing the wireless device to receive] content from
`a server based upon information derived from [either] the first
`unique identifier [or the second unique identifier].” ........................... 56
`8. Claims 8/43/59: “[Claim 2][Claim 37][Claim 51], wherein the
`first or second further action [additionally] includes [sending a
`message][or causing a server to send a message][causing the
`wireless device to send a message] to another device associated
`with an account related to the first and the second unique
`identifiers[, or information derived from the first or the second
`unique identifiers].” ............................................................................. 57
`9. Claims 10/44/62: “[Claim 2][Claim 37][Claim 51] wherein the
`second further action [additionally] includes
`[preventing][causing the wireless device to prevent] sending
`[of] the second unique identifier or information derived from
`
`- iv -
`
`

`

`
`
`the second unique identifier by the [mobile] wireless device to
`at least one of the one or more servers.” ............................................. 58
`10. Claims 12/64: “[Claim 1][Claim 50] wherein the [taking] first
`further action [further][additionally] includes causing the
`wireless device[,] to: send the first unique identifier or
`information derived from the first unique identifier to at least
`one of the one or more servers, and [subsequently] receive the
`stored information in response.” ......................................................... 59
`11. Claims 13/14/65/66: “[Claim 1][Claim 2][Claim 50][Claim 51]
`wherein the [computer program instructions, when executed by
`the one or more processors in the wireless device, further cause
`the wireless device to[:] receive] stored information [is
`received] at the wireless device from at least one of the one or
`more servers prior to [the taking of the first][performing one or
`more of the first and the second][performing the
`first][performing one or more of the first and the second]
`further action.” ..................................................................................... 59
`12. Claims 15/36/46/67/80: “[Claim 1 further comprising][Claim
`37 wherein the operations further comprise][Claim 50 wherein
`the computer program instructions… further cause the wireless
`device to][Claim 50 further comprising program instructions
`that… cause the wireless device to]: [using][use] the stored
`information to determine if the first unique identifier is present
`among the [first] selected one or more unique identifiers [from
`the first plurality of beacon transmissions].” ...................................... 60
`13. Claims 16/68: “[Claim 2][Claim 51] wherein all beacon
`transmitter devices participating in the particular wireless
`beacon service have the same particular beacon service
`identifier.” ............................................................................................ 61
`14. Claim 18: “[Claim 2] wherein the steps performed at the
`wireless device are performed as a result of an application
`program executing on the wireless device.” ....................................... 62
`15. Claims 19/34/72: “[Claim 2][Claim 1][Claim 51] wherein the
`[second][first] further action is [additionally] related to either a
`product tied to a location or an advertisement tied to a
`location.” ............................................................................................. 62
`
`- v -
`
`

`

`
`
`16. Claims 22/48/75: “[Claim 2][Claim 37][Claim 51] wherein the
`second further action [additionally] includes [allowing][causing
`the wireless device to allow] a user associated with the [mobile]
`wireless device to [be provided] access to an object or device
`associated with the wireless beacon service.” ..................................... 63
`17. Claims 23/35/49/76: “[Claim 2][Claim 3][Claim 37][Claim 51]
`wherein the [taking][first or] second further action additionally
`[comprises: controlling][includes causing the wireless device to
`control] further communications between the [mobile] wireless
`device and at least one [other] device or server associated with
`an entity or object in proximity to the wireless device [based
`upon information derived from the first or second unique
`identifier].” .......................................................................................... 64
`18. Claims 26/38/79: “[Claim 2 further comprising][Claim 37
`wherein the operations further comprise][Claim 51 wherein the
`computer program instructions, when executed by the wireless
`device, further cause the wireless device to]: [using][use] the
`stored information to determine if the second unique identifier
`is present among the selected one or more of the unique
`identifiers from the second plurality of beacon transmissions.” ......... 66
`19. Claims 27/39/81: “[Claim 1][Claim 37][Claim 50] wherein
`[the][each] MAC address is a randomly generated 48 bit
`number matching a format of a Bluetooth BD_ADDR.”.................... 66
`20. Claim 28: “[Claim 3] wherein the short range protocol is
`derived from Bluetooth.” ..................................................................... 66
`21. Claim 37 .............................................................................................. 67
`a. [37.PRE] “A mobile wireless device comprising:” .................... 67
`b. [37.A] “one or more radios for providing reception and
`transmission for each of a Bluetooth wireless protocol and
`a second wireless protocol; ......................................................... 67
`c. [37.B] “one or more processors; and” ......................................... 68
`d. [37.C] “one or more memory devices coupled to the one or
`more processors, the one or more memory devices storing
`a set of instructions that when executed by the one or more
`processors cause the one or more processors to perform
`operations including:” ................................................................. 68
`
`- vi -
`
`

`

`
`
`j.
`
`l.
`
`i.
`
`e. [37.D] “receiving from a beacon transmitter… a first
`plurality of beacon transmissions during a first time
`period…” ..................................................................................... 69
`[37.E] “receiving… stored information…;” ............................... 69
`f.
`g. [37.F] “selecting one or more unique identifiers… by
`filtering the beacon transmissions…;” ........................................ 69
`h. [37.G] “taking first further action… if the first unique
`identifier is present…;” ............................................................... 69
`[37.H] “receiving, during a second time period, a second
`plurality of beacon transmissions…;” ......................................... 69
`[37.I] “selecting one or more of the unique identifiers…
`by filtering the beacon transmissions…;” ................................... 69
`k. [37.J] “taking second further action… if a second unique
`identifier is present…, wherein the second unique
`identifier is associated with the same entity or object, and
`wherein the second unique identifier is not equal to the
`first unique identifier, and further wherein the received
`beacon transmissions including the first and second unique
`identifiers are received from a same transmitting device;
`and” ............................................................................................. 70
`[37.K] “wherein the [second beacon transmission] MAC
`address… is different from the [first beacon transmission]
`MAC address…, but each… includes the same particular
`beacon service identifier.” ........................................................... 70
`22. Claim 50 .............................................................................................. 70
`a. [50.PRE] “A computer program product for installation in
`a non-volatile memory in a wireless device, the computer
`program product comprising computer program
`instructions that, when read from the non-volatile memory,
`and then executed by one or more processors in the
`wireless device, cause the wireless device to:” ........................... 70
`b. [50.A] “process a first plurality of beacon transmissions…,
`each beacon transmission comprising three fields…;” ............... 71
`c. [50.B] “process stored information…;” ...................................... 71
`
`- vii -
`
`

`

`
`
`d. [50.C] “select one or more of the unique identifiers… by
`filtering the beacon transmissions…; and” ................................. 71
`e. [50.D] “perform a first further action… if the first unique
`identifier is present….” ............................................................... 71
`23. Claim 51 .............................................................................................. 72
`a. [51.PRE] “[Claim 50] wherein the computer program
`instructions, when executed by the one or more processors
`in the wireless device, cause the wireless device to:” ................. 72
`b. [51.A] “during a first time period: process the first
`plurality of beacon transmissions…, and” .................................. 72
`c. [51.B] “during a second time period:” ........................................ 72
`d. [51.C] “process a second plurality of beacon
`transmissions…, each beacon transmission comprising
`three fields…;” ............................................................................ 72
`e. [51.D] “select one or more of the unique identifiers… by
`filtering the beacon transmissions which include the same
`particular beacon service identifier…; and” ............................... 72
`[51.E] “perform a second further action… if a second
`unique identifier is present….” ................................................... 73
`24. Claim 52: “[Claim 51] wherein the [first and second beacon
`transmission] MAC address [are different], but each… includes
`the same particular beacon service identifier, and… no beacon
`transmissions including the same service identifier and the
`second unique identifier are received in the first time period.” .......... 73
`VII. CONCLUSION ................................................................................................ 74
`1. APPENDIX A: U.S. PATENT NO. 11,687,971 CLAIM LISTING .............. 75
`
`
`
`f.
`
`
`
`- viii -
`
`

`

`
`
`TABLE OF AUTHORITIES
`
`CASES
`KSR Int’l v. Teleflex,
`550 U.S. 398 (2007) .......................................................................... 18, 25, 28, 61
`Ohio Willow Wood Co. v. Alps South, LLC,
`735 F.3d 1333 (Fed. Cir. 2013) .............................................................................. 5
`OTHER AUTHORITIES
`MPEP §2111.05 ....................................................................................................... 55
`
`
`
`
`
`
`- ix -
`
`

`

`
`
`EXHIBIT LIST
`
`Exhibit Description
`1001 U.S. Patent No. 11,687,971
`1002
`Prosecution History of U.S. Patent No. 11,687,971
`1003 Declaration of Mark Lanning
`1004 Curriculum Vitae of Mark Lanning
`1005 U.S. Patent Application No. 2005/0250552 (“Eagle”)
`1006 U.S. Patent Application Publication No. 2010/0138481 (“Behrens”)
`1007 U.S. Patent No. 7,590,086 (“Olkkonen”)
`1008 Bluetooth Special Interest Group, Bluetooth Core Specification Version
`2.1 + EDR (July 26, 2007)
`1009 Bluetooth Special Interest Group, Assigned Numbers (December 14,
`2002)
`(https://web.archive.org/web/20021214114356/http://www.bluetooth.or
`g/assigned-numbers/baseband.htm)
`1010 U.S. Patent Application Publication No. 2002/0131445
`1011 U.S. Patent Application Publication No. 2002/0174364
`1012 U.S. Patent Application Publication No. 2005/0164717
`1013 U.S. Patent Application Publication No. 2006/0165100
`1014
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00903, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 8, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00903, Paper
`31 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00904, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 8, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00904, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00931, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 15, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00931, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00932, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 15, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00932, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00933, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 15, 2020)
`
`1015
`
`1016
`
`1017
`
`1018
`
`1019
`
`1020
`
`1021
`
`1022
`
`- x -
`
`

`

`
`
`
`
`1024
`
`1025
`
`1026
`
`1027
`
`1028
`
`1029
`
`1030
`
`1031
`
`Exhibit Description
`1023
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00933, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00934, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 27, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00934, Paper
`31 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00977, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 27, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00977, Paper
`31 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00978, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B. June 1, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00978, Paper
`10 (Decision Denying Institution) (P.T.A.B. Dec. 4, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00979, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B. June 1, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00979, Paper
`33 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00980, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B June 1, 2020)
`Target Corporation v. Proxicom Wireless, LLC, IPR2020-00980, Paper
`32 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`Target Corporation v. Proxicom Wireless, LLC, Nos. 2022-1282, 2022-
`1283, 2022-1338, 2022-1339, 2023 U.S. App. LEXIS 24861 (Fed. Cir.
`Sep. 20, 2023) (nonprecedential)
`1035 Apple Inc., iPhone 3G Technical Specifications
`(https://web.archive.org/web/20080725084414/http://www.apple.com/ip
`hone/specs.html)
`1036 Apple Inc., iPhone User Guide for iPhone OS 3.1 Software
`(https://cdsassets.apple.com/live/6GJYWVAV/user/ma616_iphone_ios3
`_1_user_guide.pdf)
`
`1032
`
`1033
`
`1034
`
`
`
`
`
`- xi -
`
`

`

`
`
`MANDATORY NOTICES
`
`A. Real Party-In-Interest
`
`Petitioner Google LLC1 is a real party-in-interest to this proceeding under 37
`
`C.F.R. §42.8(b)(1).
`
`B. Related Matters
`
`A decision in this proceeding could affect or be affected by the following.
`
`1. United States Patent & Trademark Office
`
`U.S. Patent No. 11,687,971 issued from application no. 17/942,197, filed
`
`2022-09-12, and claims priority to the following applications:
`
`Application No.
`17/366,826
`16/817,896
`15/271,410
`14/861,563
`14/472,477
`13/775,435
`13/212,723
`12/364,828
`61/095,359
`61/095,001
`
`Filing Date
`2021-07-02
`2020-03-13
`2016-09-21
`2015-09-22
`2014-08-29
`2013-02-25
`2011-08-18
`2009-02-03
`2008-09-09
`2008-09-08
`
`
`
`
`1 Google LLC is a subsidiary of XXVI Holdings Inc., which is a subsidiary of
`
`Alphabet Inc. XXVI Holdings Inc. and Alphabet Inc. are not real parties-in-interest
`
`to this proceeding.
`
`- xii -
`
`

`

`
`
`The following patent applications claim priority to U.S. Patent No.
`
`11,687,971 and application no. 17/942,197:
`
`Application No.
`19/027,075 (pending)
`19/027,020 (pending)
`18/437,306 (pending)
`18/204,528
`
`Filing Date
`2025-01-17
`2025-01-17
`2024-02-09
`2023-06-01
`
`
`U.S. Patent No. 11,687,971 is the subject of Samsung Electronics Co., Ltd.
`
`v. Secure Communication Technologies, LLC, IPR2025-01051, filed 2025-05-30.
`
`Petitioner is concurrently filing petitions for inter partes review of U.S.
`
`Patent Nos. 11,443,344 (application 17/366,826) and 11,344,918 (application
`
`15/217,410) and recommends assigning each case to the same panel.
`
`2. United States District Court
`
`a. Eastern District of Texas
`
`Secure Communication Technologies, LLC. v. Samsung Electronics Co.,
`
`Ltd., No. 2:24-cv-00484 (E.D. Tex.), filed 2024-07-03.
`
`- xiii -
`
`

`

`
`
`C. Counsel and Service Information - §§42.8(b)(3) and (4)
`
`Lead Counsel
`
`Service
`Information
`
`SMcKeown-PTAB@wolfgreenfield.com
` Elizabeth.DiMarco@WolfGreenfield.com
` VCheung-PTAB@wolfgreenfield.com
`
`Scott A. McKeown, Reg. No. 42,866
`
`Backup Counsel Libbie A. DiMarco (pro hac vice forthcoming)
`Victor Cheung, Reg. No. 66,229
`
`E-mail:
`
`
`
`Post and hand delivery: WOLF, GREENFIELD & SACKS, P.C.
`
`
`
`
`600 Atlantic Avenue
`
`
`
`
`Boston, MA 02210-2206
`
`Telephone: 617-646-8000
`Facsimile: 617-646-8646
`
`
`
` power of attorney is submitted with the Petition. Counsel for Petitioner
`
` A
`
`consents to service of all documents via electronic mail.
`
`- xiv -
`
`

`

`
`
`Petitioner requests inter partes review (IPR) and cancellation of claims 1-8,
`
`10, 12-16, 18-19, 22-23, 26-30, 34-44, 46, 48-59, 62, 64-68, 72, 75-76, and 79-81
`
`(“Challenged Claims”) of U.S. Patent No. 11,687,971 (EX1001, the “’971”).
`
`I.
`
`INTRODUCTION
`The ’971 is directed to a mobile communication architecture for “facilitating
`
`the exchange of information” between two wireless devices, each device
`
`employing short-range communication (e.g., Bluetooth) and long-range
`
`communication (e.g., cellular) wireless capabilities. EX1001, 1:5-24, 1:49-2:63. A
`
`first device may detect an identifier transmitted from a second device in short-
`
`range proximity and sends information identifying the second device to a server
`
`via long-range communications. EX1001, 1:49-2:4, 5:25-34, 5:57-67. Based on
`
`policy information stored at the server, the server may alert the first device to the
`
`second device’s presence with, e.g., the second device’s contact information.
`
`EX1001, 2:5-14, 6:7-14, 6:41-59, 6:60-7:8.
`
`This architecture of exchanging information between nearby devices and
`
`servers was claimed in earlier patents within the ’971’s family (all claiming
`
`priority to the same provisional applications) and previously cancelled by the
`
`PTAB as known in the art. As shown in the diagram below, a majority of the
`
`family’s earlier patents were challenged before the PTAB, and claims directed to
`
`- 1 -
`
`

`

`
`
`the device-server architecture were found unpatentable in all but one proceeding.2
`
`See EX1014-EX1033 (Petitions and Decisions in those IPRs). Unpatentability was
`
`further confirmed in the only two IPR proceedings appealed to the CAFC (from
`
`IPR2020-00931 and IPR2020-00933). See EX1034.
`
`
`2 IPR2020-00978 was denied institution for reasons/limitations not relevant to the
`
`’971 claims. EX1029, 15-18.
`
`- 2 -
`
`

`

`
`
`The ’971 claims were prosecuted while the above-described IPRs were
`
`pending, but the claims issued before final judgment (with appeals exhausted), to
`
`include three overall concepts: (1) the short-range and long-range communications
`
`
`
`- 3 -
`
`

`

`
`
`architecture described above and found to be squarely in the prior art; (2) changing
`
`device identifiers over time, also found to be in the prior art; and (3) filtering based
`
`on short-range service identifiers. The PTAB already determined that the first two
`
`features, in combination, were well-known—in Eagle (EX1005) and Behrens
`
`(EX1006).3 Likewise, the PTAB has previously found that criteria-based filtering
`
`of short-range communicated identifiers was also known.4 Patent Owner is
`
`estopped from challenging here the PTAB’s findings regarding the same prior art
`
`teachings. Ohio Willow Wood Co. v. Alps South, LLC, 735 F.3d 1333, 1342 (Fed.
`
`
`3 See EX1015, 7-8 and 15-34 (PTAB determining that Eagle anticipated claims
`
`including a server receiving a unique identifier from a wireless device over a “wide
`
`area link,” where that wireless device received the unique identifier from another
`
`wireless device over a “local wireless link,” and transmitting information back to
`
`the wireless device based on a policy); EX1031, 46-49 (PTAB acknowledging that
`
`Behrens teaches using “a combination of UIDs” and that users may “exercise
`
`control over which or how many UIDs are transmitted”).
`
`4 See EX1015, 17, 24 (PTAB finding that Eagle discloses determining which
`
`unique identifiers to send to the server); EX1033, 18-23 (PTAB determining that
`
`prior art systems disclosed suppressing/filtering communications to servers where
`
`unique identifiers were previously encountered).
`
`- 4 -
`
`

`

`
`
`Cir. 2013) (“Collateral estoppel protects a party from having to litigate issues that
`
`have been fully and fairly tried in a previous action and adversely resolved against
`
`a party-opponent.”).
`
`As Patent Owner’s claims were being cancelled in previous IPRs,
`
`continuation patents were pursued to switch its filtering criteria to a new but
`
`existing parameter (service identifier) of Bluetooth/WiFi communications. The
`
`addition of filtering for known Bluetooth service identifiers to the claims cannot
`
`confer patentability because the reception of service identifiers and their use in
`
`filtering search results was known in the prior art, as Olkkonen (EX1007)
`
`illustrates.
`
`Ground 1 explains how Eagle in view of Behrens renders obvious the same
`
`short-range/long-range architecture and changing identifiers previously presented
`
`to the PTAB—and Olkkonen renders obvious the “new” but trivial feature of using
`
`a service identifier for filtering.
`
`Accordingly, Petitioner requests that the Board institute IPR and cancel the
`
`Challenged Claims.
`
`II.
`
`STANDING CERTIFICATION
`Petitioner certifies that the ’971 is available for IPR and that Petitioner is
`
`neither barred nor estopped from requesting IPR of the Challenged Claims. 37
`
`C.F.R. §42.104(a).
`
`- 5 -
`
`

`

`
`
`III. UNPATENTABILITY GROUNDS
`The Challenged Claims are unpatentable as follows:
`
`Ground
`1
`
`References
`Eagle in view of
`Behrens and
`Olkkonen
`
`Claims
`1-8, 10, 12-16, 18-19, 22-23, 26-
`30, 34-44, 46, 48-59, 62, 64-68,
`72, 75-76, 79-81
`
`Pre-AIA Basis
`§103
`
`
`The ’971’s earliest possible effective filing date is 2008-09-08. EX1001,
`
`code (60). Each relied-upon reference is pre-AIA §102(b) and/or (e) prior art even
`
`under the earliest 2008 filing date.
`
`Name
`Eagle (EX1005)
`Behrens (EX1006)
`Olkkonen (EX1007)
`
`Filing Date
`2005-05-05
`2008-04-30 (PCT)
`2004-11-03
`
`Issue/Publication Date
`2005-11-10
`2010-06-03
`2009-09-15
`
`
`
`The Declaration of Mark Lanning (EX1003, ¶¶1-302; “Lanning”) describes
`
`the prior art’s scope and content at the time of the ’971.
`
`IV.
`
`’971 PATENT5
`A. Background
`The ’971 is directed to the exchange of information between two wireless
`
`devices using short-range communications (

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