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. IPR2026-00098
`Patent No. 11,995,685
`_____________
`
`
`
`PETITION FOR INTER PARTES REVIEW
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. § 42.1 et seq
`
`
`
`
`
`
`
`
`- i -
`TABLE OF CONTENTS
`I. INTRODUCTION ............................................................................................. 1
`II. STANDING CERTIFICATION ........................................................................ 6
`III. UNPATENTABILITY GROUNDS .................................................................. 6
`IV. ’685 PATENT .................................................................................................... 7
`A. Background .................................................................................................. 7
`B. Prosecution History ..................................................................................... 9
`C. POSITA ....................................................................................................... 9
`V. CLAIM INTERPRETATION ......................................................................... 10
`VI. GROUND 1: EAGLE IN VIEW OF BEHRENS AND OLKKONEN
`RENDERS OBVIOUS CLAIMS 1-8, 10, 12-16, 19, 22-23, 26-27, 31-
`41, 44-48, 52-54, 57-58, 60-64, 67-71, 73, 76-77, 79-81, 85-86 .................... 10
`A. Eagle (EX1005) ......................................................................................... 10
`B. Behrens (EX1006) ..................................................................................... 12
`C. Olkkonen (EX1007) .................................................................................. 12
`D. Eagle in view of Behrens, in further view of Olkkonen ............................ 14
`1. Receiving different identifying information from the same
`device ................................................................................................... 16
`2. Filtering beacon service identifiers ..................................................... 19
`3. Actions ................................................................................................. 24
`E. Mapping to Claims .................................................................................... 26
`1. Claim 1 ................................................................................................ 26
`a. [1.PRE] “A method comprising:” ............................................... 26
`b. [1.A.I] “causing processing, at a wireless device, of a first
`plurality of beacon transmissions received at the wireless
`device via a short range wireless protocol, each beacon
`transmission comprising three fields” ......................................... 27
`
`c. [1.A.II] “(a) a MAC address,” .................................................... 30
`
`
`
`
`
`
`
`
`- ii -
`d. [1.A.III] “(b) a unique identifier, wherein the unique
`identifier of each respective beacon transmission is a
`numeric value, and” .................................................................... 31
`e. [1.A.IV] “(c) a beacon service identifier, wherein the
`beacon service identifier of each respective beacon
`transmission identifies a wireless beacon service in which
`the unique identifier is relevant to stored information
`relating to an entity or object associated with a transmitter
`of a respective beacon transmission;” ......................................... 32
`
`f. [1.B.I] “causing a transfer of the stored information
`between the wireless device and one or more servers via a
`second wireless protocol,” .......................................................... 34
`g. [1.B.II] “wherein at least a portion of the stored
`information relates to a particular entity or object
`associated with a first unique identifier, and” ............................. 35
`
`h. [1.B.III] “wherein the second wireless protocol is different
`from the short range wireless protocol;” ..................................... 36
`i. [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; and” ................................... 36
`
`j. [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.” ............................. 38
`
`2. Claim 2 ................................................................................................ 39
`a. [2.PRE] “The method of claim 1, wherein the processing
`of the first plurality of beacon transmissions occurs in a
`first time period, and” ................................................................. 39
`b. [2.A] “wherein the method further comprises, during a
`second time period:” ................................................................... 39
`c. [2.B.I] “causing processing, at the wireless device, of a
`second plurality of beacon transmissions received at the
`wireless device via the short range wireless protocol, each
`of the second plurality of beacon transmissions comprising
`three fields” ................................................................................. 40
`
`d. [2.B.II] “(a) a MAC address,” ..................................................... 40
`
`
`
`
`
`
`
`
`- iii -
`e. [2.B.III] “(b) a unique identifier, wherein the unique
`identifier of each respective beacon transmission is a
`numeric value, and” .................................................................... 41
`f. [2.B.IV] “(c) a beacon service identifier, wherein the
`beacon service identifier of each respective beacon
`transmission identifies a wireless beacon service in which
`the unique identifier is relevant to the stored information
`relating to an entity or object associated with a transmitter
`of a respective beacon transmission;” ......................................... 41
`
`g. [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; and” ....... 42
`
`h. [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,” ................................. 43
`i. [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.” ................................ 43
`
`3. Claims 3/37 .......................................................................................... 44
`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” ...... 44
`
`b. [3.B]/[37] “[cont. from 3.A][The mobile wireless device
`of claim 34] wherein a plurality of beacon transmissions
`including the particular beacon service identifier and the
`first unique identifier are received in the first time period,
`and no beacon transmissions including the same particular
`
`
`
`
`
`
`
`
`- iv -
`beacon service identifier and the second unique identifier
`are received in the first time period.” .......................................... 46
`4. Claims 4/38/61: “[Claim 3][Claim 37][Claim 60] wherein the
`second further action is based upon a function currently being
`performed on a device associated with the wireless beacon
`service.” ............................................................................................... 47
`5. Claims 5/39/62: “[Claim 4][Claim 38][Claim 61] wherein the
`function is related to a current phone call.” ........................................ 49
`6. Claims 6/26/80: “[Claim 2][Claim 1][Claim 60] wherein the
`first [or the second] further action is 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 information derived from the first [or
`second] unique identifier.” .................................................................. 50
`
`7. Claims 7/27/40/63/81: “[Claim 2][Claim 1][Claim 37][Claim
`60][Claim 60] wherein [one or more of] the first further action
`[and the second further action] includes receiving content from
`a server based upon information derived from [either] the first
`unique identifier [or the second unique identifier].” ........................... 51
`8. Claims 8/41/64: “[Claim 2][Claim 37][Claim 60], wherein the
`first or second further action includes sending a message to
`another device associated with an account related to the first
`and the second unique identifiers.” ..................................................... 52
`9. Claim 10: “[Claim 2] wherein the second further action
`includes preventing sending of the second unique identifier or
`information derived from the second unique identifier by the
`wireless device to at least one of the one or more servers.” ............... 53
`10. Claims 12/44/67: “[Claim 2][Claim 37][Claim 60] wherein the
`[taking] first further action [further] 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 receive the stored
`information in response.” .................................................................... 53
`
`11. Claims 13/14/45/46/68/69: “[Claim 2][Claim 37][Claim
`39][Claim 60][Claim 62] wherein the 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 the
`
`
`
`
`
`
`
`
`- v -
`second][performing one or more of the first and the second]
`further action.” ..................................................................................... 54
`12. Claims 15/47/70: “[Claim 1][Claim 45][Claim 68] further
`comprising: using the stored information to determine if the
`first unique identifier is present among the first selected one or
`more unique identifiers.” ..................................................................... 54
`13. Claims 16/48/71: “[Claim 2][Claim 37][Claim 60] wherein all
`beacon transmitter devices participating in the particular
`wireless beacon service have the same particular beacon service
`identifier.” ............................................................................................ 56
`
`14. Claims 19/31/73: “[Claim 2][Claim 1][Claim 60] wherein the
`[second][first] further action is related to either a product tied to
`a location or an advertisement tied to a location.” .............................. 56
`15. Claims 22/52/76: “[Claim 2][Claim 37][Claim 60] wherein the
`second further action includes allowing a user associated with
`the wireless device to be provided access to an object or device
`associated with the wireless beacon service.” ..................................... 57
`16. Claims 23/32/53/57/77/85 ................................................................... 58
`a. Claims [23.A][32][53.A][57][77.A][85]: “[Claim 3][Claim
`37][Claim 60] wherein the taking second further action
`additionally comprises: controlling further
`communications between the wireless device and at least
`one device or server associated with an entity [or object]
`in proximity to the wireless device[.][, and]” ............................. 58
`
`b. Claims [23.B]/[53.B]/[77.B]: “wherein the stored
`information includes contact information of the entity in
`proximity utilized to determine the presence of the second
`unique identifier prior to taking the second further action.” ...... 59
`17. Claims 33/54/58/79/86: “[Claim 2][Claim 37][Claim 37][Claim
`60][Claim 60] further comprising: using 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.” ......................................... 60
`18. Claim 34 .............................................................................................. 60
`a. [34.PRE] “A mobile wireless device comprising:” .................... 61
`
`
`
`
`
`
`
`
`- vi -
`b. [34.A] “one or more radios for providing reception and
`transmission for each of a Bluetooth wireless protocol and
`a second wireless protocol;” ....................................................... 61
`c. [34.B] “one or more processors; and” ......................................... 61
`d. [34.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:” ................................................................. 62
`e. [34.D] “receiving from a beacon transmitter… a first
`plurality of beacon transmissions during a first time
`period…” ..................................................................................... 62
`
`f. [34.E] “transferring… stor ed information…;” ........................... 62
`g. [34.F] “selecting one or more unique identifiers… by
`filtering the beacon transmissions…;” ........................................ 63
`h. [34.G] “taking first further action… if the first unique
`identifier is present…;” ............................................................... 63
`i. [34.H] “receiving… during a second time period, a second
`plurality of beacon transmissions…;” ......................................... 63
`j. [34.I] “selecting one or more of the unique identifiers…
`by filtering the beacon transmissions…;” ................................... 63
`k. [34.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” ............................................................................................. 63
`
`l. [34.K] “wherein the [second beacon transmission] MAC
`address… is different from the [first beacon transmission]
`MAC address…, but each… incl udes the same particular
`beacon service identifier.” ........................................................... 63
`19. Claim 35 .............................................................................................. 64
`
`
`
`
`
`
`
`
`- vii -
`a. [35.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:” ........................... 64
`b. [35.A] “process a first plurality of beacon transmissions…,
`each beacon transmission comprising three fields…;” ............... 65
`c. [35.B] “transfer stored information…;” ...................................... 65
`d. [35.C] “select one or more of the unique identifiers… by
`filtering the beacon transmissions…; and” ................................. 65
`e. [35.D] “perform a first further action… if the first unique
`identifier is present….” ............................................................... 65
`20. Claim 36 .............................................................................................. 65
`a. [36.PRE] “[Claim 35] wherein the computer program
`instructions, when executed by the one or more processors
`in the wireless device, cause the wireless device to:” ................. 65
`b. [36.A] “during a first time period: process the first
`plurality of beacon transmissions…, and” .................................. 65
`c. [36.B] “during a second time period:” ........................................ 66
`d. [36.C] “process a second plurality of beacon
`transmissions…, each beacon transmission comprising
`three fields…;” ............................................................................ 66
`e. [36.D] “select one or more of the unique identifiers… by
`filtering the beacon transmissions which include the same
`particular beacon service identifier; and” ................................... 66
`f. [36.E] “perform a second further action… if a second
`unique identifier is present….” ................................................... 66
`21. Claim 60: “[Claim 36] wherein the [first and second beacon
`transmission] MAC address [are different], but each… beacon
`transmission includes the same particular beacon service
`identifier, and… no beacon transmissions including the same
`particular beacon service identifier and the second unique
`identifier are received in the first time period.” .................................. 66
`
`
`
`
`
`
`
`
`- viii -
`VII. GROUND 2: EAGLE IN VIEW OF BEHRENS, OLKKONEN, AND
`KALLIO RENDERS OBVIOUS CLAIMS 25, 55, AND 78 ......................... 67
`VIII. GROUND 3: EAGLE IN VIEW OF BEHRENS, OLKKONEN, AND
`JONES RENDERS OBVIOUS CLAIMS 53 AND 59 ................................... 69
`A. Interpretation ............................................................................................. 69
`B. Eagle-Behrens-Olkkonen-Jones ................................................................ 71
`IX. GROUND 4: EAGLE IN VIEW OF BEHRENS, OLKKONEN,
`KALLIO, AND JONES RENDERS OBVIOUS CLAIM 87 .......................... 76
`X. CONCLUSION ................................................................................................ 76
`
`
`
`
`
`
`
`
`
`
`
`- ix -
`TABLE OF AUTHORITIES
`CASES
`Apple Inc. v. FastVDO LLC,
`IPR2016-01203, Paper 39, 9-10 (Dec. 11, 2017) ................................................. 71
`Google Inc. v. Spring Ventures Ltd.,
`IPR2017-01653, Paper 68 (Jan. 15, 2019) ........................................................... 71
`K/S HIMPP v. III Holdings 4, LLC,
`IPR2017-00782, Paper 8 (Jul. 27, 2017) .............................................................. 71
`KSR Int’l v. Teleflex,
`550 U.S. 398, 417 (2007) ............................................................................. passim
`Ohio Willow Wood Co. v. Alps South, LLC,
`735 F.3d 1333 (Fed. Cir. 2013) .............................................................................. 5
`
`
`
`
`
`
`
`
`
`
`
`
`- x -
`EXHIBIT LIST
`Exhibit Description
`1001 U.S. Patent No. 11,995,685
`1002 Prosecution History of U.S. Patent No. 11,995,685
`1003 Declaration of Mark Lannin g
`1004 Curriculum Vitae of Mark Lannin g
`1005 U.S. Patent Applica tion No. 2005/0250552 (“Eagle”)
`1006 U.S. Patent Application Publ ication 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 Gr oup, 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)
`1015 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00903, Paper
`31 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`1016 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00904, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 8, 2020)
`1017 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00904, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`1018 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00931, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 15, 2020)
`1019 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00931, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`1020 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00932, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 15, 2020)
`1021 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00932, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`1022 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00933, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 15, 2020)
`
`
`
`
`
`
`
`
`- xi -
`Exhibit Description
`1023 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00933, Paper
`30 (Final Written Decision) (P.T.A.B Nov. 8, 2021)
`1024 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00934, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 27, 2020)
`1025 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00934, Paper
`31 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`1026 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00977, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B May 27, 2020)
`1027 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00977, Paper
`31 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`1028 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00978, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B. June 1, 2020)
`1029 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00978, Paper
`10 (Decision Denying Institution) (P.T.A.B. Dec. 4, 2020)
`1030 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00979, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B. June 1, 2020)
`1031 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00979, Paper
`33 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`1032 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00980, Paper
`2 (Petition for Inter Partes Review) (P.T.A.B June 1, 2020)
`1033 Target Corporation v. Proxicom Wireless, LLC, IPR2020-00980, Paper
`32 (Final Written Decision) (P.T.A.B Nov. 30, 2021)
`1034 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 Guid e for iPhone OS 3.1 Software
`(https://cdsassets.apple.com/live/6GJYWVAV/user/ma616_iphone_ios3
`_1_user_guide.pdf)
`1037 [RESERVED]
`1038 U.S. Patent Application Publ ication No. 2007/0264991 (“Jones”)
`1039-
`1046
`[RESERVED]
`1047 U.S. Patent Application Publ ication No. 2003/0224756 (“Kallio”)
`
`
`
`
`
`
`
`
`
`- xii -
`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,995,685 issued from application no. 18/204,528, filed
`2023-06-01, and claims priority to the following applications:
`Application No. Filing Date
`17/942,197 2022-09-12
`17/366,826 2021-07-02
`16/817,896 2020-03-13
`15/271,410 2016-09-21
`14/861,563 2015-09-22
`14/472,477 2014-08-29
`13/775,435 2013-02-25
`13/212,723 2011-08-18
`12/364,828 2009-02-03
`61/095,359 2008-09-09
`61/095,001 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.
`
`
`
`
`
`
`
`
`- xiii -
`The following patent applications claim priority to U.S. Patent No.
`11,995,685 and application no. 18/204,528:
`Application No. Filing Date
`19/027,075 (pending) 2025-01-17
`19/027,020 (pending) 2025-01-17
`18/437,306 2024-02-09
`
`Petitioner recently filed petitions for inter partes review of U.S. Patent Nos.
`11,687,971 (application 17/942,197; IPR2025-01183), 11,443,344 (application
`17/366,826; IPR2025-01182), and 11,344,918 (application 15/217,410; IPR2025-
`01181), and recommends assigning this case to the same panel.
`2. United States District Court
`a. Western District of Texas
`Secure Communication Technologies, LLC. v. Google LLC, No. 1:25-cv-
`01207 (W.D. Tex.), filed 2025-08-04. U.S. Patent No. 11,995,685 was added to
`this district court case in an amended complaint filed 2025-09-08.
`
`
`
`
`
`
`
`
`- xiv -
`C. Counsel and Service Information - §§42.8(b)(3) and (4)
`Lead Counsel Scott A. McKeown, Reg. No. 42,866
`
`Backup Counsel Elizabeth A. DiMarco (pro hac vice forthcoming)
`Victor Cheung, Reg. No. 66,229
`
`Service
`Information
`E-mail: SMcKeown-PTAB@wolfgreenfield.com
` Elizabeth.DiMarco@WolfGreenfield.com
` VCheung-PTAB@wolfgreenfield.com
`
`Post and hand delivery: W
`OLF, GREENFIELD & SACKS, P.C.
` 600 Atlantic Avenue
` Boston, MA 02210-2206
`
`Telephone: 617-646-8000
`Facsimile: 617-646-8646
`
`A power of attorney is submitted with the Petition. Counsel for Petitioner
`consents to service of all documents via electronic mail.
`
`
`
`
`
`
`
`
`- 1 -
`Petitioner requests inter partes review (IPR) and cancellation of claims 1-8,
`10, 12-16, 19, 22-23, 25-27, 31-41, 44-48, 52-55, 57-64, 67-71, 73, 76-81, 85-87
`(“Challenged Claims”) of U.S. Patent No. 11,995,685 (EX1001, the “’685”).
`I. INTRODUCTION
`The ’685 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 ’685’s family (all claiming
`priority to the same provisional applications) and previously cancelled by the
`PTAB as known in the art. Shown in the diagram below, a majority of the family’s
`earlier patents were challenged before the PTAB, and claims directed to the
`
`
`
`
`
`
`
`
`- 2 -
`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
`’685 claims. EX1029, 15-18.
`
`
`
`
`
`
`
`
`- 3 -
`
`The ’685 claims were prosecuted while the above-described IPRs were
`pending and follow a similar structure to its parents that issued during that time
`
`
`
`
`
`
`
`
`
`- 4 -
`(e.g., US 11,687,971), by including three overall concepts: (1) the short-range and
`long-range communications 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
`based on 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
`
`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).
`
`
`
`
`
`
`
`
`- 5 -
`PTAB’s findings regarding the same prior art teachings. Ohio Willow Wood Co. v.
`Alps South, LLC, 735 F.3d 1333, 1342 (Fed. 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 newly claimed
`but existing parameter (service identifier) of Bluetooth communications taken from
`the prior art. 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 most of
`the challenged claims reciting 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.
`Ground 2 explains how Kallio (EX1047) further renders obvious dependent
`claims reciting MAC-address-formatted numbers as identifiers.
`Grounds 3-4 explain how Jones (EX1038) further renders obvious
`dependent claims reciting the selection of an image in a user interface.
`
`
`
`
`
`
`
`
`- 6 -
`Accordingly, Petitioner requests that the Board institute IPR and cancel the
`Challenged Claims.
`II. STANDING CERTIFICATION
`Petitioner certifies that the ’685 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).
`III. UNPATENTABILITY GROUNDS
`The Challenged Claims are unpatentable as follows:
`Ground References Claims Pre-AIA Basis
`1 Eagle in view of
`Behrens and
`Olkkonen
`1-8, 10, 12-16, 19, 22-23, 26-27,
`31-41, 44-48, 52-54, 57-58, 60-64,
`67-71, 73, 76-77, 79-81, 85-86
`§103
`2 Eagle in view of
`Behrens,
`Olkkonen, and
`Kallio
`25, 55, 78
`3 Eagle in view of
`Behrens,
`Olkkonen, and
`Jones
`53, 59
`4 Eagle in view of
`Behrens,
`Olkkonen,
`Kallio, and
`Jones
`87
`
`
`
`
`
`
`
`
`
`- 7 -
`The ’685’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 Filing Date Issue/Publication Date
`Eagle (EX1005) 2005-05-05 2005-11-10
`Behrens (EX1006) 2008-04-30 (PCT) 2010-06-03
`Olkkonen (EX1007) 2004-11-03 2009-09-15
`Kallio (EX1047) 2002-05-30 2003-12-04
`Jones (EX1038) 2006-05-15 2007-11-15
`
`The Declaration of Mark Lanning (EX1003, ¶¶1-315; “Lanning”) describes
`the prior art’s scope and content at the time of the ’685.
`IV. ’685 PATENT5
`A. Background
`The ’685 is directed to the exchange of information between two wireless
`devices using short-range communications (e.g., Bluetooth), with the aid of a
`remote server using long-range communications (e.g., cellular). EX1001, 1:5-24,
`1:49-2:63.
`
`5 Unless otherwise noted, all emphasis in the Petition (including figure annotations)
`is added.
`
`
`
`
`
`
`
`
`- 8 -
`Fig. 2 (below) shows one implementation with devices 202 and 204 in short-
`range communication, and device 202 and server 100 in long-range
`communication. EX1001, 5:25-34.
`
`Device 204 is associated with a museum exhibit that “transmits identifying
`information [to device 202] using s

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