`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`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-01181
`Patent No. 11,334,918
`_____________
`
`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 ........................................................................ 6
`III. UNPATENTABILITY GROUNDS .................................................................. 6
`IV. ’918 PATENT .................................................................................................... 7
`A. Background .................................................................................................. 7
`B. Prosecution History ..................................................................................... 9
`C. POSITA ....................................................................................................... 9
`V. CLAIM INTERPRETATION ......................................................................... 10
`A. “determining…proximity” ........................................................................ 10
`VI. GROUND 1: EAGLE IN VIEW OF BEHRENS AND OLKKONEN
`RENDERS OBVIOUS CLAIMS 1-4, 8-20, 22-25, 27-28, AND 31 .............. 11
`A. Eagle .......................................................................................................... 11
`B. Behrens ...................................................................................................... 13
`C. Olkkonen ................................................................................................... 13
`D. Eagle in view of Behrens, in further view of Olkkonen ............................ 15
`1. Receiving different identifying information from the same
`device ................................................................................................... 17
`2. Filtering beacon service identifiers ..................................................... 20
`3. Networking applications ..................................................................... 25
`4. Blacklists and friend lists .................................................................... 27
`5. Re-alerting a previously alerted device ............................................... 30
`E. Mapping to Challenged Claims ................................................................. 32
`1. Claim 1 ................................................................................................ 33
`a. [1.PRE] “A mobile wireless device comprising:” ...................... 33
`b. [1.A] “a first radio; a second radio;” ........................................... 34
`c. [1.B] “one or more processors; one or more memory
`devices coupled to the one or more processors, the one or
`more memory devices storing a set of instructions that
`
`- 1 -
`
`

`

`
`
`when executed by the one or more processors cause the
`one or more processors to perform operations including:” ........ 35
`d. [1.D] “receiving, using the first radio, identifier related
`information associated with a proximity beacon service,
`from one or more servers;” ......................................................... 36
`e. [1.E.I] “receiving, using the second radio, a plurality of
`short range transmissions, including a plurality of
`proximity beacon transmissions when the device is located
`within a detection range of one or more beacon transmitter
`devices associated with the proximity beacon service, each
`of the proximity beacon transmissions including” ..................... 39
`[1.E.II] “a respective MAC address,” ......................................... 41
`f.
`g. [1.E.III] “a respective unique identifier, and” ............................ 43
`h. [1.E.IV] “a Proximity Beacon Service Identifier (PBSI);” ......... 44
`i.
`[1.F.I] “determining if a particular short range
`transmission of the plurality of short range transmissions
`a) includes a MAC address, and” ................................................ 44
`[1.F.II] “b) includes the proximity beacon service
`identifier (PBSI) and if c) the PBSI indicates the particular
`short range transmission is a proximity beacon
`transmission associated with the proximity beacon
`service;” ....................................................................................... 45
`k. [1.G] “then: determining if an entity or object associated
`with the proximity beacon service is in proximity to the
`mobile wireless device, by utilizing the identifier related
`information and the unique identifier.” ....................................... 46
`2. Claim 2: “[Claim 1], wherein the MAC address is a randomly
`generated 48 bit number matching a format of a Bluetooth
`BD_ADDR.” ....................................................................................... 50
`3. Claim 3 ................................................................................................ 51
`a. [3.PRE] “The mobile wireless device of claim 1 wherein
`the one or more processors further execute the instructions
`to perform operations including:” ............................................... 51
`
`j.
`
`- ii -
`
`

`

`
`
`f.
`
`b. [3.A] “receiving, by the second radio, a first proximity
`beacon transmission including a first MAC address and a
`first unique identifier at a first time; and” ................................... 52
`c. [3.B.I] “receiving, by the second radio, a second proximity
`beacon transmission including a second MAC address and
`a second unique identifier at a second time,” ............................. 52
`d. [3.B.II] “the second MAC address being different from the
`first MAC address and” ............................................................... 54
`e. [3.B.III] “the second unique identifier being different from
`the first unique identifier; and” ................................................... 55
`[3.C] “associating the first and second unique identifier
`with a single beacon transmitter device.” ................................... 55
`4. Claim 4: “[Claim 1], wherein the one or more processors
`further execute the instructions to perform operations including:
`further determining that at least one beacon transmitter device
`associated with the proximity beacon service is in proximity to
`the mobile wireless device, by utilizing an action function
`including one or more previously downloaded unique
`identifiers.” .......................................................................................... 56
`5. Claims 8/31 .......................................................................................... 58
`a. [8.PRE]/[31.PRE] “[Claim 1][Claim 3] wherein the one or
`more processors further execute the instructions to…:” ............. 58
`a. [8.A]/[31.A] “receiving, via a second radio, the plurality
`of proximity beacon transmissions further includes
`receiving a first unique identifier at a first time that is
`different from a second unique identifier received at a
`second time; and” ........................................................................ 58
`b. [8.B]/[31.B] “associating the first and second unique
`identifier with a single beacon transmitter device.” ................... 58
`6. Claim 9 ................................................................................................ 59
`a. [9.PRE] “A method for facilitating use of proximity
`beacons, the method executing within a mobile device,
`and the method comprising:” ...................................................... 59
`b. [9.A] “communicating… identifier related information…;” ...... 59
`
`- iii -
`
`

`

`
`
`f.
`
`c. [9.B] “receiving… a plurality of proximity beacon
`transmissions…;” ........................................................................ 59
`d. [9.C] “…a particular short range transmission… includes a
`MAC address,” ............................................................................ 59
`e. [9.D] “…(PBSI) is present, and c) determining that… the
`particular short range transmission is… associated with the
`proximity beacon service; and” .................................................. 60
`[9.E] “…then… determining that an entity or object… is
`within proximity….” ................................................................... 60
`7. Claim 10 .............................................................................................. 60
`a. [10.PRE] “The method of claim 9,” ............................................ 60
`b. [10.A] “wherein a first one of the plurality of proximity
`beacon transmissions received at a first time includes a
`first unique identifier, and wherein a second one of the
`plurality of proximity beacon transmissions received at a
`second time includes a second unique identifier the second
`unique identifier being different from the first unique
`identifier; and” ............................................................................ 60
`c. [10.B] “associating both the first unique identifier and the
`second unique identifier with a particular entity or object
`in proximity to the mobile device.” ............................................ 60
`8. Claim 11: “[Claim 9] wherein the MAC address is selected
`from a group consisting of (a) a randomly generated 48 bit
`number matching a format of a MAC address and (b) a
`Bluetooth BD_ADDR.” ...................................................................... 61
`9. Claim 12 .............................................................................................. 61
`a. [12.PRE] “The method of claim 9” ............................................. 61
`b. [12.A] “wherein a first one of the plurality of proximity
`beacon transmissions is received at a first time and
`includes a first unique identifier and first MAC address,
`and the Proximity Beacon Service Identifier (PBSI); and” ........ 61
`c. [12.B] “wherein a second one of the plurality of proximity
`beacon transmissions received at a second time includes a
`second unique identifier different from the first unique
`identifier and a second MAC address different from the
`
`- iv -
`
`

`

`
`
`first MAC address, and the Proximity Beacon Service
`Identifier; and” ............................................................................ 61
`a. [12.C] “associating both the first unique identifier and the
`second unique identifier with the same entity or object in
`proximity to the mobile device.” ................................................ 62
`10. Claims 13/15: “[Claim 9, further comprising][Claim 1, wherein
`the instructions further comprise:] preventing the sending of the
`unique identifier, using the first radio, to the one or more
`servers, based upon previous detections of the respective unique
`identifier associated with the proximity beacon transmission.” ......... 62
`11. Claims 14/19: “[Claim 1, wherein the instructions further
`comprise:][Claim 9, additionally comprising:] sending the
`unique identifier, using the first radio, to at least one server of
`the one or more servers, and receiving further information
`relating to an object or entity associated with being within
`proximity to the mobile device.” ......................................................... 63
`12. Claims 16/24: “[Claim 1, wherein the instructions further
`comprise:][Claim 9, additionally comprising:] controlling
`further communications between the mobile device and at least
`one device or server associated with an entity or object in
`proximity to the mobile device.” ......................................................... 64
`13. Claim 17: “[Claim 9], further comprising: receiving, using the
`first radio, access code information by the mobile device from
`at least one of the servers; and utilizing the access code
`information to gain access to the entity or object determined to
`be in proximity to the mobile device.” ................................................ 66
`14. Claims 18/28: “[Claim 9][Claim 1], wherein [the] receiving [of]
`the identifier related information, using the first radio, is
`performed in response to [executing instructions for] sending at
`least the unique identifier to at least one of the one or more
`servers using the first radio.” ............................................................... 67
`15. Claim 20: “[Claim 19] wherein the further information relates
`to… advertising content.” ................................................................... 67
`16. Claim 22: “[Claim 19] wherein the further information relates
`to a nearby user of an application on another device, in common
`with an application on the mobile device.” ......................................... 68
`
`- v -
`
`

`

`
`
`17. Claim 23: “[Claim 22] wherein the application is a multiuser
`game.” .................................................................................................. 70
`18. Claims 25/27: “[Claim 9, wherein the step of determining that
`an entity or object is within proximity further
`comprises:][Claim 1, wherein… the one or more processors
`further execute the instructions… for determining that an entity
`or object is within proximity by further:] comparing the
`identifier related information with the unique identifier or
`information derived from the unique identifier.” ................................ 70
`VII. GROUND 2: EAGLE IN VIEW OF BEHRENS, OLKKONEN, AND
`PERTTILA RENDERS OBVIOUS CLAIM 17 ............................................. 71
`VIII. GROUND 3: EAGLE IN VIEW OF BEHRENS, OLKKONEN, AND
`JONES RENDERS OBVIOUS CLAIM 29 .................................................... 73
`IX. CONCLUSION ................................................................................................ 75
`1. APPENDIX A: U.S. PATENT NO. 11,334,918 CLAIM LISTING .............. 76
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`- vi -
`
`

`

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

`

`
`
`EXHIBIT LIST
`
`Exhibit Description
`1001 U.S. Patent No. 11,334,918
`1002
`Prosecution History of U.S. Patent No. 11,334,918
`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
`
`- viii -
`
`

`

`
`
`
`
`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)
`1037 U.S. Patent Application Publication No. 2004/0243519 (“Perttila”)
`1038 U.S. Patent Application Publication No. 2007/0264991 (“Jones”)
`1039 U.S. Patent No. 8,321,497 (“Steiner”)
`1040 U.S. Patent Application Publication No. 2007/0219875 (“Toulotte”)
`
`
`1032
`
`1033
`
`1034
`
`
`
`- ix -
`
`

`

`
`
`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,334,918 issued from application no. 15/271,410, filed
`
`2016-09-21, and claims priority to the following applications:
`
`Application No.
`14/861,563
`14/472,477
`13/775,435
`13/212,723
`12/364,828
`61/095,359
`61/095,001
`
`Filing Date
`2015-09-22
`2014-08-29
`2013-02-25
`2011-08-18
`2009-02-03
`2008-09-09
`2008-09-08
`
`
`The following patent applications claim priority to U.S. Patent No.
`
`11,334,918 and application no. 15/271,410:
`
`
`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.
`
`- x -
`
`

`

`
`
`Application No.
`19/027,075 (pending)
`19/027,020 (pending)
`18/437,306 (pending)
`18/204,528
`17/942,197
`17/366,826
`16/817,896
`
`Filing Date
`2025-01-17
`2025-01-17
`2024-02-09
`2023-06-01
`2022-09-12
`2021-07-02
`2020-03-13
`
`
`U.S. Patent No. 11,334,918 is the subject of Samsung Electronics Co., Ltd.
`
`v. Secure Communication Technologies, LLC, IPR2025-01049, 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,687,971 (application
`
`17/942,197) 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.
`
`- xi -
`
`

`

`
`
`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.
`
`- xii -
`
`

`

`
`
`Petitioner requests inter partes review (IPR) and cancellation of claims 1-4,
`
`8-20, 22-25, 27-29, and 31 (“Challenged Claims”) of U.S. Patent No. 11,334,918
`
`(EX1001, the “’918”).
`
`I.
`
`INTRODUCTION
`The ’918 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, 2:66-5:12. 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, 3:4-28, 7:44-53, 8:9-25. 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,
`
`3:29-35, 8:26-33, 8:60-9:27.
`
`This architecture of exchanging information between nearby devices and
`
`servers was claimed in earlier patents within the ’918’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 (IPR Petitions and Decisions). Unpatentability was further
`
`confirmed in the only two IPR proceedings appealed to the CAFC (IPR2020-
`
`00931, IPR2020-00933). See EX1034.
`
`
`
`
`2 IPR2020-00978 was denied institution for reasons/limitations not relevant to the
`
`’918 claims. EX1029, 15-18.
`
`- 2 -
`
`

`

`
`
`The ’918 claims were prosecuted while the above-described IPRs were
`
`pending, but the claims issued before final judgment (with appeals exhausted), to
`
`
`
`- 3 -
`
`

`

`
`
`include 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—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 over a “local
`
`wireless link,” and transmitting information back to the wireless device based on a
`
`policy); EX1031, 46-49 (PTAB acknowledging Behrens’ “combination of UIDs”
`
`and users exercising control over transmitted UIDs).
`
`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.
`
`Ground 2 explains how Perttila (EX1037) further renders obvious the use of
`
`access codes in an interaction between wireless devices.
`
`Ground 3 explains how Jones (EX1038) further renders obvious the
`
`advertisement of Bluetooth services.
`
`Accordingly, Petitioner requests that the Board institute IPR and cancel the
`
`Challenged Claims.
`
`- 5 -
`
`

`

`
`
`II.
`
`STANDING CERTIFICATION
`Petitioner certifies that the ’918 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
`1
`
`References
`Eagle, Behrens, Olkkonen
`
`2
`
`3
`
`Eagle, Behrens, Olkkonen,
`Perttila
`Eagle, Behrens, Olkkonen,
`Jones
`
`Claims
`1-4, 8-20, 22-25, 27-
`28, 31
`17
`
`29
`
`Pre-AIA Basis
`§103
`
`
`The ’918’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)
`Perttila (EX1037)
`Jones (EX1038)
`
`
`
`Filing Date
`2005-05-05
`2008-04-30 (PCT)
`2004-11-03
`2003-06-02
`2006-05-15
`
`Issue/Publication Date
`2005-11-10
`2010-06-03
`2009-09-15
`2004-12-02
`2007-11-15
`
`- 6 -
`
`

`

`
`
`The Declaration of Mark Lanning (EX1003, ¶¶1-297; “Lanning”) describes
`
`the prior art’s scope and content at the time of the ’918.
`
`IV.
`
`’918 PATENT5
`A. Background
`The ’918 is directed to the exchange of information between two wireless
`
`devices using short-range communications (e.g., Bluetooth/WiFi), with the aid of a
`
`remote server using long-range communications (e.g., cellular). EX1001, 2:66-
`
`5:12.
`
`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, 7:44-53.
`
`
`5 Unless otherwise noted, all emphasis in the Petition (including figure annotations)
`
`is added.
`
`- 7 -
`
`

`

`
`
`
`
`Device 204 is associated with a museum exhibit that “transmits identifying
`
`information [to device 202] using short range wireless link 203,” which device 202
`
`“passes… to the central server 100,” and server 100 recognizes the identifying
`
`information as associated with device 204. EX1001, 7:49-65. Based on account
`
`settings and policies, the server determines “what information and under which
`
`situations information may be disclosed to another device or user” to facilitate
`
`further short-range communications. EX1001, 4:49-67, 9:12-21, 16:5-16.
`
`The ’918 claims that devices in short-range proximity identify themselves
`
`with beacon transmissions including a MAC address, unique identifier, and beacon
`
`service identifier. EX1001, claim 1. Examples of service identifiers in an ad hoc
`
`Wi-Fi network include basic service set identifiers (BSSIDs, such as a 48-bit
`
`- 8 -
`
`

`

`
`
`address) and service set identities (SSIDs, which are network names). EX1001,
`
`10:31-11:6; see also Olkkonen, 12:24-30, 18:60-39:39, 27:52-56, 32:20-25, 33:44-
`
`60 (describing functionality of known short-range BSSIDs, SSIDs, access codes,
`
`and service attributes). Lanning, ¶¶40-69.
`
`B.
`Prosecution History
`Prosecution of the ’918 included rounds of office actions/amendments and
`
`appeals based on §§101, 112, 102, and 103. See generally EX1002.
`
` In a Notice of Allowance, the Examiner stated that the prior art of record
`
`“does not disclose each of the proximity beacon transmissions including a MAC
`
`address and a unique identifier, determining if a particular short range transmission
`
`of the plurality of short range transmissions includes a MAC address, and utilizing
`
`the unique identifier.” EX1002, 2187-2190. Lanning, ¶¶70-71.
`
`C.
`POSITA
`On 2008-09-08, a person having ordinary skill in the art (“POSITA”) would
`
`have had a Bachelor’s degree in electrical or computer engineering, or a related
`
`field, with approximately 3-5 years of experience in wireless communications.6 A
`
`higher level of education may substitute for less experience. Lanning, ¶¶73-75.
`
`
`6 This same level was adopted in prior proceedings in the ’918 family and is now
`
`fixed by estoppel. See EX1019, 8-9.
`
`- 9 -
`
`

`

`
`
`V. CLAIM INTERPRETATION
`Claim terms are construed herein using the standard used in civil actions
`
`under 35 U.S.C. §282(b), in accordance with the ordinary and customary meaning
`
`as understood by a POSITA and the patent’s prosecution history. 37 C.F.R.
`
`§42.100(b).
`
`A.
`“determining…proximity”
`Claims [1.G] and [9.E] of the ’918 recite: “determining [if/that] an entity or
`
`object… is [in/within] proximity to the mobile wireless device, by utilizing the
`
`identifier related information.”
`
`During prosecution, Applicant provided examples of alleged support for
`
`these limitations to argue that they did not contain new matter. EX1002, 521-540.
`
`Thus, the limitations may encompass particular features in addition to their plain
`
`and ordinary meaning.
`
`For example, determining proximity may be satisfied by disclosing a
`
`device’s presence to another device. See EX1002, 524 (“Device 1… notifies the
`
`user that the entity… is in proximity”), 539 (“process… allows for disclosure of a
`
`user’s presence (that is, their ‘proximity’)”). That is, if one device’s presence is not
`
`disclosed (or not permitted to be disclosed) to another device, those devices are
`
`determined not to be in “proximity.”
`
`- 10 -
`
`

`

`
`
`Furthermore, utilizing identifier related information may be satisfied by
`
`using identifier information as a filter to determine which identifiers to pass to a
`
`server to determine whether there is permission to disclose a device’s presence to
`
`another. See EX1002, 524 (“if identifiers are found… employ an action… as a
`
`filter that determines which… identifiers should be passed to the server,”
`
`“permission… may require being on a friends list”).
`
`Lanning, ¶¶77-80.
`
`VI. GROUND 1: EAGLE IN VIEW OF BEHRENS AND OLKKONEN
`RENDERS OBVIOUS CLAIMS 1-4, 8-20, 22-25, 27-28, AND 31
`A. Eagle
`Eagle is directed to a mobile communication architecture or “social software
`
`introduction system” for “facilitating direct communications between consenting
`
`persons having similar interests.” Eagle, [0002], [0065].
`
`The system includes cellular phones enabled with Bluetooth that identify
`
`other nearby devices by a unique identification value such as a Bluetooth address.
`
`Eagle, [0003], [0018]. When one device (hereinafter a “Requester Device”) detects
`
`a device (hereinafter an “Identified Device”) using the Identified Device’s unique
`
`identification value, the Requester Device notifies a remote server of the unique
`
`identification value via a long-range cellular network. Eagle, [0003], [0020]. An
`
`example of devices 203 and 205, and a server 220, are shown in Fig. 2 (below).
`
`- 11 -
`
`

`

`
`
`
`
`The server stores profile data describing devices and their owners and
`
`“fetches th