`C.
`Approved for use through 0613012010. 0MB 0651-0032
`00')
`U.S. Patent and Trademark Office. U.S. DEPARTMENT OF COMMERCE
`l:J er the Pa erwork Reduction Act of 1995 no ersons are re uired to res nd to a collection of information unless it dis la s a valid 0MB control number.
`
`U.S. PTO
`12/077041
`03/14/2008
`
`UTILITY
`PATENT APPLICATION
`TRANSMITTAL
`
`Attorney Docket No.
`
`Johnson.000600
`
`First Inventor
`
`Title
`
`William J. Johnson
`
`System and Method for Location ..
`
`(Only for new nonprovisional applications under 37 CFR 1.53(b))
`
`Express Mail Label No.
`
`EV277957782US
`
`APPLICATION ELEMENTS
`See MPEP chapter 600 concerning utility patent application contents.
`
`ADDRESS TO:
`
`Commissioner for Patents
`P.O. Box 1450
`Alexandria VA 22313-1450
`
`1. 11]
`
`2.[Z]
`
`3.11]
`
`4.(Z]
`
`Fee Transmittal Form (e.g., PTOISB/17)
`(Submit an original and a duplicate for fee processing)
`Applicant claims small entity status.
`See 37 CFR 1.27.
`Specification
`187
`[Total Pages
`Both the claims and abstract must start on a new page
`(For information on the preferred anangement. see MPEP 608.01 (a))
`Drawing(s)(35 U.S.C. 113)
`[Total Sheets
`70
`
`5. Oath or Declaration
`3
`[Total Sheets
`a. [l] Newly executed (original or copy)
`b. D A copy from a prior application (37 CFR 1.63(d))
`_l!_or continuation/divisional with Box 18 completed)
`i. LJ DELETION OF INVENTOR(Sl
`Signed statement attached deleting inventor(s)
`name in the prior application. see 37 CFR
`1.63(d)(2) and 1.33(b).
`
`6. [Z] Application Data Sheet. See 37 CFR 1. 76
`
`7. D
`
`CD-ROM or CD-R in duplicate, large table or
`~puter Program (Appendix)
`LJ Landscape Table on CD
`
`8.
`
`Nucleotide and/or Amino Acid Sequence Submission
`(if apeJ!E.able, items a.
`c. are required)
`a. LJ Computer Readable Form (CRF)
`b.
`Specification Sequence Listing on:
`i. □
`CD-ROM or CD-R (2 copies); or
`Paper
`i1.0
`
`ACCOMPANYING APPLICATION PARTS
`
`9. D Assignment Papers (cover sheet & document(s))
`
`Name of Assignee. _____________ _
`
`10. D 37 CFR 3.73(b) Statement
`[Z]Powerof
`Attorney
`(when there is an assignee)
`11. D English Translation Document (if applicable)
`12. D lnfo~tion Disclosure Statement (PTO/SB/OB or PTO-1449)
`LJ Copies of citations attached
`
`13. D Preliminary Amendment
`14. [Z] Return Receipt Postcard (MPEP 503)
`(Should be specifically itemized)
`15. D Certified Copy of Priority Document(s)
`(if foreign priority is claimed)
`
`16. D Nonpublication Request under 35 U.S.C. 122(b)(2)(B)(i).
`Applicant must attach form PTO/SB/35 or equivalent.
`
`17. Dother: _______________ _
`
`Statements verifying identity of above copies
`c. D
`18. If a CONTINUING APPLICATION, check appropriate box, and supply the requisite information below and in the first sentence of the
`specification following the title, or in an Application Data Sheet under 37 CFR 1. 76:
`D Continuation-in-part (CIP)
`D Continuation
`□ Divisional
`
`of prior application No.: ................ ..
`
`Prior application information:
`
`Examiner _____________ _
`
`Art Unit: ____________ _
`
`[ { ] The address associated with Customer Number:
`
`42640
`
`OR D Correspondence address below
`
`19. CORRESPONDENCE ADDRESS
`
`Name
`
`Address
`
`City
`
`Country
`
`Signature
`
`Name
`Print/T e
`
`State
`
`Telephone
`
`Zip Code
`
`
`.J,
`
`Date
`
`/J(
`28,429
`
`FR 1.53(b). The information is required to obtain or retain a benefit by the public which is to file (and by the
`uired by
`This collection of informs ·o 1s
`ication. Confidentality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection is estimated to take 12 minutes to
`USPTO to process) an ap
`complete, including gathering. preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any
`comments on the amount of time you require to complete this form and/or suggestions for reducing this burden. should be sent to the Chief Information Officer,
`U.S. Patent and Trademark Office, U.S. Department of Commerce. P.O. Box 1450. Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED
`FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313,1450.
`If you need assistance in completing the form, ca/11-800-PTO-9199 and select option 2.
`
`Exhibit 1009
`IPR2022-00426
`Page 1 of 1302
`
`
`
`PTO/S8/17 (10-07)
`Approved for use through 06/30/2010. 0MB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`r,,.l.l'i:ii;lii;ihe Panerwork Reduction Act of 1995 no oersons are required to respond to a collection of information unless it displays a valid 0MB control number
`"I
`~ ~
`Complete if Known
`Effective on 12/08/2004.
`F~rs11ant to the Consolidated Appropriations Act, 2005 (H.R. 4818).
`TBD
`Filing Date
`03/14/08
`First Named Inventor William J. Johnson
`Examiner Name
`TBD
`Art Unit
`TBD
`Attorney Docket No.
`Johnson.000600US
`
`~SE TRANSMITTAL Application Number
`For FY 2008
`@ Applicant claims small entity status. See 37 CFR 1.27
`\.. TOTAL AMOUNT OF PAYMENT I ($)'I O 35 . 00
`
`..J
`
`METHOD OF PAYMENT (check all that apply)
`
`D Check D Credit Card D Money Order 0None Oother (please identify):
`0 Deposit Account Deposit Account Number: 50-3083
`
`Deposit Account Name: Dillon & Yudell
`For the above-identified deposit account. the Director is hereby authorized to: (check all that apply)
`
`[Z]charge fee(s) indicated below
`[{] Charge any additional fee(s) or underpayments of fee(s)
`under 37 CFR 1.16 and 1.17
`WARNING: Information on this form may become public. Credit card information should not be included on this form. Provide credit card
`information and authorization on PTO-2038.
`FEE CALCULATION
`
`D Charge fee(s) indicated below, except for the filing fee
`ll] Credit any overpayments
`
`Fees Paid 1$1
`515
`
`1. BASIC FILING, SEARCH, AND EXAMINATION FEES
`FILING FEES
`SEARCH FEES
`EXAMINATION FEES
`Small Entlfy
`Small Entify
`Small Entify
`A1rnlication TJ111e ~ ~ ~ Fee($,) ~ Fee(i)
`Utility
`310
`155
`510
`210
`255
`105
`Design
`210
`105
`100
`130
`50
`65
`Plant
`210
`105
`310
`160
`155
`80
`Reissue
`310
`155
`510
`620
`255
`310
`Provisional
`210
`0
`105
`0
`0
`0
`2. EXCESS CLAIM FEES
`Fee Descri11tion
`Each claim over 20 (including Reissues)
`Each independent claim over 3 (including Reissues)
`Multiple dependent claims
`Extra Claims ~ Fee Paid m
`Total Claims
`=
`2Q
`20 or HP
`0
`X
`HP = highest number of total daims paid for, if greater than 20.
`Extra Claims ~ Fee Paid 1$1
`lnde11. Claims
`- 3 or HP =
`=
`3
`0
`X
`HP highest number of independent daims paid for, if greater than 3.
`3. APPLICATION SIZE FEE
`If the specification and drawings exceed 100 sheets of paper (excluding electronically filed sequence or computer
`listings under 37 CFR 1.52(e)), the application size fee due is $260 ($ 130 for small entity) for each additional 50
`sheets or fraction thereof. See 35 U.S.C. 41 (a)( I )(G) and 37 CFR I. I 6(s).
`Number of each additional 50 or fraction thereof ~ Fee Paid ($1
`Total Sheets
`Extra Sheets
`130 =
`-100 =
`(round up to a whole number) X
`150 =
`257
`157
`520
`4
`4. OTHER FEE(S)
`Fees Paid 1$1
`Non-English Specification, $130 fee (no small entity discount)
`Other (e.g., late filing surcharge):
`
`Small Entify
`~ ~
`50
`25
`105
`210
`370
`185
`Multi11le De11endent Claims
`~ Fee Paid 1$1
`
`SUBMITTED BY
`'6 / ~/\/\
`Signature
`"I. /obe 'I
`Name (PrinVType) Jona!)<i ri
`This collection of inform:I re~ed br~yf CFR 1.136. The information is required to obtain or retain a benefit by the public which is to file (and by the
`USPTO to process) an a pli
`tioj Confid ntiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This collection is estimated to take 30 minutes to complete,
`· g. an submitting th~ completed applicatio~ form to the USPT~. Time will vary depending upon t_he individu~I case. Any comments
`induding gathering, prep
`on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent
`and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS
`ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`If you need assistance in completing the form, ca/11-800-PTO-9199 and select option 2.
`
`\
`
`./\ ~
`
`II
`
`I Registration No. 28429
`
`IAttornev/Aclent)
`
`Telephone 512-343-6116
`Date 3/14/08
`
`Exhibit 1009
`IPR2022-00426
`Page 2 of 1302
`
`
`
`CERTIFICATE OF MAILING
`37 C.F.R. § 1.S(a)
`
`I hereby certify that this correspondence is being deposited with the United States Postal Service on the below
`listed date with sufficient postage for express-mail in an envelope addressed to: Commissioner for Patents,
`P.O. Box 1450, Alexandria, VA 22313-1450.
`Date: 3l,i.\loY
`
`B~ ~tctA...___,
`Signature
`
`Exhibit 1009
`IPR2022-00426
`Page 3 of 1302
`
`
`
`PTO/SB/05 (07-07)
`C.
`Approved for use through 0613012010. 0MB 0651-0032
`00')
`U.S. Patent and Trademark Office. U.S. DEPARTMENT OF COMMERCE
`l:J er the Pa erwork Reduction Act of 1995 no ersons are re uired to res nd to a collection of information unless it dis la s a valid 0MB control number.
`
`U.S. PTO
`12/077041
`03/14/2008
`
`UTILITY
`PATENT APPLICATION
`TRANSMITTAL
`
`Attorney Docket No.
`
`Johnson.000600
`
`First Inventor
`
`Title
`
`William J. Johnson
`
`System and Method for Location ..
`
`(Only for new nonprovisional applications under 37 CFR 1.53(b))
`
`Express Mail Label No.
`
`EV277957782US
`
`APPLICATION ELEMENTS
`See MPEP chapter 600 concerning utility patent application contents.
`
`ADDRESS TO:
`
`Commissioner for Patents
`P.O. Box 1450
`Alexandria VA 22313-1450
`
`1. 11]
`
`2.[Z]
`
`3.11]
`
`4.(Z]
`
`Fee Transmittal Form (e.g., PTOISB/17)
`(Submit an original and a duplicate for fee processing)
`Applicant claims small entity status.
`See 37 CFR 1.27.
`Specification
`187
`[Total Pages
`Both the claims and abstract must start on a new page
`(For information on the preferred anangement. see MPEP 608.01 (a))
`Drawing(s)(35 U.S.C. 113)
`[Total Sheets
`70
`
`5. Oath or Declaration
`3
`[Total Sheets
`a. [l] Newly executed (original or copy)
`b. D A copy from a prior application (37 CFR 1.63(d))
`_l!_or continuation/divisional with Box 18 completed)
`i. LJ DELETION OF INVENTOR(Sl
`Signed statement attached deleting inventor(s)
`name in the prior application. see 37 CFR
`1.63(d)(2) and 1.33(b).
`
`6. [Z] Application Data Sheet. See 37 CFR 1. 76
`
`7. D
`
`CD-ROM or CD-R in duplicate, large table or
`~puter Program (Appendix)
`LJ Landscape Table on CD
`
`8.
`
`Nucleotide and/or Amino Acid Sequence Submission
`(if apeJ!E.able, items a.
`c. are required)
`a. LJ Computer Readable Form (CRF)
`b.
`Specification Sequence Listing on:
`i. □
`CD-ROM or CD-R (2 copies); or
`Paper
`i1.0
`
`ACCOMPANYING APPLICATION PARTS
`
`9. D Assignment Papers (cover sheet & document(s))
`
`Name of Assignee. _____________ _
`
`10. D 37 CFR 3.73(b) Statement
`[Z]Powerof
`Attorney
`(when there is an assignee)
`11. D English Translation Document (if applicable)
`12. D lnfo~tion Disclosure Statement (PTO/SB/OB or PTO-1449)
`LJ Copies of citations attached
`
`13. D Preliminary Amendment
`14. [Z] Return Receipt Postcard (MPEP 503)
`(Should be specifically itemized)
`15. D Certified Copy of Priority Document(s)
`(if foreign priority is claimed)
`
`16. D Nonpublication Request under 35 U.S.C. 122(b)(2)(B)(i).
`Applicant must attach form PTO/SB/35 or equivalent.
`
`17. Dother: _______________ _
`
`Statements verifying identity of above copies
`c. D
`18. If a CONTINUING APPLICATION, check appropriate box, and supply the requisite information below and in the first sentence of the
`specification following the title, or in an Application Data Sheet under 37 CFR 1. 76:
`D Continuation-in-part (CIP)
`D Continuation
`□ Divisional
`
`of prior application No.: ................ ..
`
`Prior application information:
`
`Examiner _____________ _
`
`Art Unit: ____________ _
`
`[ { ] The address associated with Customer Number:
`
`42640
`
`OR D Correspondence address below
`
`19. CORRESPONDENCE ADDRESS
`
`Name
`
`Address
`
`City
`
`Country
`
`Signature
`
`Name
`Print/T e
`
`State
`
`Telephone
`
`Zip Code
`
`
`.J,
`
`Date
`
`/J(
`28,429
`
`FR 1.53(b). The information is required to obtain or retain a benefit by the public which is to file (and by the
`uired by
`This collection of informs ·o 1s
`ication. Confidentality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection is estimated to take 12 minutes to
`USPTO to process) an ap
`complete, including gathering. preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any
`comments on the amount of time you require to complete this form and/or suggestions for reducing this burden. should be sent to the Chief Information Officer,
`U.S. Patent and Trademark Office, U.S. Department of Commerce. P.O. Box 1450. Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED
`FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313,1450.
`If you need assistance in completing the form, ca/11-800-PTO-9199 and select option 2.
`
`Exhibit 1009
`IPR2022-00426
`Page 4 of 1302
`
`
`
`PTO/S8/17 (10-07)
`Approved for use through 06/30/2010. 0MB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`r,,.l.l'i:ii;lii;ihe Panerwork Reduction Act of 1995 no oersons are required to respond to a collection of information unless it displays a valid 0MB control number
`"I
`~ ~
`Complete if Known
`Effective on 12/08/2004.
`F~rs11ant to the Consolidated Appropriations Act, 2005 (H.R. 4818).
`TBD
`Filing Date
`03/14/08
`First Named Inventor William J. Johnson
`Examiner Name
`TBD
`Art Unit
`TBD
`Attorney Docket No.
`Johnson.000600US
`
`~SE TRANSMITTAL Application Number
`For FY 2008
`@ Applicant claims small entity status. See 37 CFR 1.27
`\.. TOTAL AMOUNT OF PAYMENT I ($)'I O 35 . 00
`
`..J
`
`METHOD OF PAYMENT (check all that apply)
`
`D Check D Credit Card D Money Order 0None Oother (please identify):
`0 Deposit Account Deposit Account Number: 50-3083
`
`Deposit Account Name: Dillon & Yudell
`For the above-identified deposit account. the Director is hereby authorized to: (check all that apply)
`
`[Z]charge fee(s) indicated below
`[{] Charge any additional fee(s) or underpayments of fee(s)
`under 37 CFR 1.16 and 1.17
`WARNING: Information on this form may become public. Credit card information should not be included on this form. Provide credit card
`information and authorization on PTO-2038.
`FEE CALCULATION
`
`D Charge fee(s) indicated below, except for the filing fee
`ll] Credit any overpayments
`
`Fees Paid 1$1
`515
`
`1. BASIC FILING, SEARCH, AND EXAMINATION FEES
`FILING FEES
`SEARCH FEES
`EXAMINATION FEES
`Small Entlfy
`Small Entify
`Small Entify
`A1rnlication TJ111e ~ ~ ~ Fee($,) ~ Fee(i)
`Utility
`310
`155
`510
`210
`255
`105
`Design
`210
`105
`100
`130
`50
`65
`Plant
`210
`105
`310
`160
`155
`80
`Reissue
`310
`155
`510
`620
`255
`310
`Provisional
`210
`0
`105
`0
`0
`0
`2. EXCESS CLAIM FEES
`Fee Descri11tion
`Each claim over 20 (including Reissues)
`Each independent claim over 3 (including Reissues)
`Multiple dependent claims
`Extra Claims ~ Fee Paid m
`Total Claims
`=
`2Q
`20 or HP
`0
`X
`HP = highest number of total daims paid for, if greater than 20.
`Extra Claims ~ Fee Paid 1$1
`lnde11. Claims
`- 3 or HP =
`=
`3
`0
`X
`HP highest number of independent daims paid for, if greater than 3.
`3. APPLICATION SIZE FEE
`If the specification and drawings exceed 100 sheets of paper (excluding electronically filed sequence or computer
`listings under 37 CFR 1.52(e)), the application size fee due is $260 ($ 130 for small entity) for each additional 50
`sheets or fraction thereof. See 35 U.S.C. 41 (a)( I )(G) and 37 CFR I. I 6(s).
`Number of each additional 50 or fraction thereof ~ Fee Paid ($1
`Total Sheets
`Extra Sheets
`130 =
`-100 =
`(round up to a whole number) X
`150 =
`257
`157
`520
`4
`4. OTHER FEE(S)
`Fees Paid 1$1
`Non-English Specification, $130 fee (no small entity discount)
`Other (e.g., late filing surcharge):
`
`Small Entify
`~ ~
`50
`25
`105
`210
`370
`185
`Multi11le De11endent Claims
`~ Fee Paid 1$1
`
`SUBMITTED BY
`'6 / ~/\/\
`Signature
`"I. /obe 'I
`Name (PrinVType) Jona!)<i ri
`This collection of inform:I re~ed br~yf CFR 1.136. The information is required to obtain or retain a benefit by the public which is to file (and by the
`USPTO to process) an a pli
`tioj Confid ntiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This collection is estimated to take 30 minutes to complete,
`· g. an submitting th~ completed applicatio~ form to the USPT~. Time will vary depending upon t_he individu~I case. Any comments
`induding gathering, prep
`on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent
`and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS
`ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`If you need assistance in completing the form, ca/11-800-PTO-9199 and select option 2.
`
`\
`
`./\ ~
`
`II
`
`I Registration No. 28429
`
`IAttornev/Aclent)
`
`Telephone 512-343-6116
`Date 3/14/08
`
`Exhibit 1009
`IPR2022-00426
`Page 5 of 1302
`
`
`
`CERTIFICATE OF MAILING
`37 C.F.R. § 1.S(a)
`
`I hereby certify that this correspondence is being deposited with the United States Postal Service on the below
`listed date with sufficient postage for express-mail in an envelope addressed to: Commissioner for Patents,
`P.O. Box 1450, Alexandria, VA 22313-1450.
`Date: 3l,i.\loY
`
`B~ ~tctA...___,
`Signature
`
`Exhibit 1009
`IPR2022-00426
`Page 6 of 1302
`
`
`
`SYSTEM AND METHOD FOR
`
`LOCATION BASED EXCHANGES OF DATA
`FACILITATING DISTRIBUTED LOCATIONAL APPLICATIONS
`
`FIELD OF THE INVENTION
`The present disclosure relates generally to location based services for mobile data
`processing systems, and more particularly to location based exchanges of data between
`distributed mobile data processing systems for locational applications. A common
`connected service is not required for location based functionality and features. Location
`based exchanges of data between distributed mobile data processing systems enable
`location based features and functionality in a peer to peer manner.
`
`BACKGROUND OF THE INVENTION
`The internet has exploded with new service offerings. Websites yahoo.com,
`google.com, ebay.com, amazon.com, and iTunes.com have demonstrated well the ability
`to provide valuable services to a large dispersed geographic audience through the internet
`(ebay, yahoo, google, amazon and iTunes (Apple) are trademarks of the respective
`companies). Thousands of different types of web services are available for many kinds of
`functionality. Advantages of having a service as the intermediary point between clients,
`users, and systems, and their associated services, includes centralized processing,
`centralized maintaining of data, for example to have an all knowing database for scope of
`services provided, having a supervisory point of control, providing an administrator with
`access to data maintained by users of the web service, and other advantages associated
`with centralized control. The advantages are analogous to those provided by the
`traditional mainframe computer to its clients wherein the mainframe owns all resources,
`data, processing, and centralized control for all users and systems (clients) that access its
`services. However, as computers declined in price and adequate processing power was
`brought to more distributed systems, such as Open Systems (i.e. Windows, UNIX, Linux,
`and Mac environments), the mainframe was no longer necessary for many of the daily
`computing tasks. In fact, adequate processing power is incorporated in highly mobile
`
`WJJ0701
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Exhibit 1009
`IPR2022-00426
`Page 7 of 1302
`
`
`
`devices, various handheld mobile data processing systems, and other mobile data
`processing systems. Technology continues to drive improved processing power and data
`storage capabilities in less physical space of a device. Just as Open Systems took much
`of the load of computing off of mainframe computers, so to can mobile data processing
`systems offload tasks usually performed by connected web services. As mobile data
`processing systems are more capable, there is no need for a service to middleman
`interactions possible between them.
`While a centralized service has its advantages, there are also disadvantages. A
`service becomes a clearinghouse for all web service transactions. Regardless of the
`number of-threads of processing spread out over hardware and processor platforms, the
`web service itself can become a bottleneck causing poor performance for timely response,
`and can cause a large amount of data that must be kept for all connected users and/or
`systems. Even large web services mentioned above suffer from performance and
`maintenance overhead. A web service response will likely never be fast enough.
`Additionally, archives must be kept to ensure recovery in the event of a disaster because
`the service houses all data for its operations. Archives also require storage, processing
`power, planning, and maintenance. A significantly large and costly data center is
`necessary to accommodate millions of users and/or systems to connect to the service.
`There is a tremendous amount of overhead in providing such a service. Data center
`processing power, data capacity, data transmission bandwidth and speed, infrastructure
`entities, and various performance considerations are quite costly. Costs include real
`estate required, utility bills for electricity and cooling, system maintenance, personnel to
`operate a successful business with service(s), etc. A method is needed to prevent large
`data center costs while eliminating performance issues for features sought. It is inevitable
`that as users are hungry for more features and functionality on their mobile data
`processing systems, processing will be moved closer to
`the device for optimal
`performance and infrastructure cost savings.
`Service delivered location dependent content was disclosed in U.S. Patents
`6,456,234; 6,731,238; 7,187,997 (Johnson). Anonymous location based services was
`disclosed in U.S. PTO Publication 2006/0022048 (Johnson). The Johnson patents and
`published application operate as most web services do in that the clients connecting to the
`service benefit from the service by having some connectivity to the service. U.S.
`
`WJJ0701
`
`2
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Exhibit 1009
`IPR2022-00426
`Page 8 of 1302
`
`
`
`Publication 2006/0022048 (Johnson) could cause large numbers of users to inundate the
`service with device heartbeats and data to maintain, depending on the configurations
`made. While this may be of little concern to a company that has successfully deployed
`substantially large web service resources, it may be of great concern to other more frugal
`companies. A method is needed for enabling location dependent features and functionality
`without the burden of requiring a service.
`Users are skeptical about their privacy as internet services proliferate. A service by
`its very nature typically holds information for a user maintained in a centralized service
`database. The user's preferences, credential information, permissions, customizations,
`billing information, surfing habits, and other conceivable user configurations and activity
`monitoring, can be housed by the service at the service. Company insiders, as well as
`outside attackers, may get access. Most people are concerned with preventing personal
`information of any type being kept in a centralized database which may potentially
`become compromised from a security standpoint. Location based services are of even
`more concern, in particular when the locations of the user are to be known to a centralized
`service. A method and system is needed for making users comfortable with knowing that
`their personal information is at less risk of being compromised ..
`A reasonable requirement is to push intelligence out to the mobile data processing
`systems themselves, for example, in knowing their own locations and perhaps the
`locations of other nearby mobile data processing systems. Mobile data processing
`systems can intelligently handle many of their own application requirements without
`depending on some remote service. Just as two people in a business organization should
`not need a manager to speak to each other, no two mobile data processing systems
`should require a service middleman
`for useful
`location dependent features and
`functionality. The knowing of its own location should not be the end of social interaction
`implementation local to the mobile data processing systems, but rather the starting place
`for a large number of useful distributed local applications that do not require a service.
`Different users use different types of Mobile data processing Systems (MSs) which
`are also called mobile devices: laptops, tablet computers, Personal Computers (PCs),
`Personal Digital Assistants (PDAs), cell phones, automobile dashboard mounted data
`processing systems, shopping cart mounted data processing systems, mobile vehicle or
`apparatus mounted data processing systems, Personal Navigational Devices (PNDs),
`
`WJJ0701
`
`3
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Exhibit 1009
`IPR2022-00426
`Page 9 of 1302
`
`
`
`iPhones (iPhone is a trademark of Apple, Inc.), various handheld mobile data processing
`systems, etc. MSs move freely in the environment, and are unpredictably moveable (i.e.
`can be moved anywhere, anytime). Many of these Mobile data processing Systems (MSs)
`do not have capability of being automatically located, or are not using a service for being
`automatically located. Conventional methods use directly relative stationary references
`such as satellites, antennas, etc. to locate MSs. Stationary references are expensive to
`deploy, and risk obsolescence as new technologies are introduced to the marketplace.
`Stationary references have finite scope of support for locating MSs.
`While
`the United States E911 mandate
`for cellular devices documents
`requirements for automatic location of a Mobile data processing System (MS) such as a
`cell phone, the mandate does not necessarily promote real time location and tracking of
`the MSs, nor does it define architecture for exploiting Location Based Services (LBS). We
`are in an era where Location Based Services (LBS), and location dependent features and
`functionality, are among the most promising technologies in the world. Automatic locating
`of every Mobile data processing System (MS) is an evolutionary trend. A method is
`needed to shorten the length of time for automatically locating every MS. Such a goal can
`be costly using prior art technologies such as GPS (Global Positioning System), radio
`wave triangulation, coming within range to a known located sensor, or the like. Complex
`system infrastructure, or added hardware costs to the MSs themselves, make such
`ventures costly and time constrained by schedules and costs involved in engineering,
`construction, and deployment.
`A method is needed for enabling users to get location dependent features and
`functionality through having their mobile locations known, regardless of whether or not
`their MS is equipped for being located. Also, new and modern location dependent features
`and functionality can be provided to a MS unencumbered by a connected service.
`
`BRIEF SUMMARY OF THE INVENTION
`LBS (Location Based Services) is a term which has gained in popularity over the
`years as MSs incorporate various location capability. The word "Services" in that
`terminology plays a major role in location based features and functionality involving
`interaction between two or more users. This disclosure introduces a new terminology,
`system, and method referred to as Location Based exchanges (LBX). LBX is an acronym
`
`WJJ070I
`
`4
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Exhibit 1009
`IPR2022-00426
`Page 10 of 1302
`
`
`
`used
`interchangeably/contextually throughout this disclosure for the singular term
`"Location Based Exchange" and for the plural term "Location Based Exchanges", much
`the same way LBS is used interchangeably/contextually for the single term "Location
`Based Service" and for the plural term "Location Based Services". LBX describes
`leveraging the distributed nature of connectivity between MSs in lieu of leveraging a
`. common centralized service nature of connectivity between MSs. The line can become
`blurred between LBS and LBX since the same or similar features and functionality are
`provided, and in some cases strengths from both may be used. The underlying
`architectural shift differentiates LBX from LBS for depending less on centralized services,
`and more on distributed interactions between MSs. LBX provide server-free and server(cid:173)
`less location dependent features and functionality.
`Disclosed are many different aspects to LBX, starting with the foundation
`requirement for each participating MS to know, at some point in time, their own
`whereabouts. LBX is enabled when an MS knows its own whereabouts. It is therefore a
`goal to first make as many MSs know their own whereabouts as possible. When two or
`more MSs know their own whereabouts, LBX enables distributed locational applications
`whereby a server is not required to middleman social interactions between the MSs. The
`MSs interact as peers. LBX disclosed include purely peer to peer interactions, peer to
`peer interactions for routing services, peer to peer interactions for delivering distributed
`services, and peer to peer interactions for location dependent features and functionality.
`One embodiment of an LBX enabled MS is referred to as an lbxPhone ™.
`It is an advantage herein to have no centralized service governing location based
`features and
`functionality among MSs. Avoiding a centralized service prevents
`performance issues, infrastructure costs, and solves many of the issues described above.
`No centralized service also prevents a user's information from being kept in one
`accessible place. LBS contain centralized data that is personal in nature to its users. This
`is a security concern. Having information for all users in one place increases the likelihood
`that a disaster to the data will affect more than a single user. LBX spreads data out across
`participating systems so that a disaster affecting one user does not affect any other user.
`It is an advantage herein for enabling useful distributed applications without the
`necessity of having a service, and without the necessity of users and/or systems
`
`WJJ0701
`
`5
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Exhibit 1009
`IPR2022-00426
`Page 11 of 1302
`
`
`
`registering with a service. MSs interact as peers in preferred embodiments, rather than as
`clients to a common service (e.g. internet connected web service).
`It is an advantage herein for locating as many MSs as possible in a wireless
`network, and without additional deployment costs on
`the MSs or the network.
`Conventional
`locating capability
`includes GPS (Global Positioning System) using
`stationary orbiting satellites, improved forms of GPS, for example AGPS (Adjusted GPS)
`and DGPS (Differential GPS) using stationary
`located ground stations, wireless
`communications to stationary located cell tower base stations, TDOA (Time Difference of
`Arrival) or AOA (Angle of Arrival) triangulation using stationary located antennas, presence
`detection in vicinity of a sta~ionary located antenna, presence detection at a wired
`connectivity stationary network location, or other conventional locating systems and
`methods. Mobile data processing systems, referred to as Indirectly Located Mobile data
`processing systems (ILMs), are automatically located using automatically detected
`locations of Directly Located Mobile data processing systems (DLMs) and/or automatically
`detected locations of other ILMS. ILMs are provided with the ability to participate in the
`same LBS, or LBX, as a OLM (Directly Located Mobile data processing system). DLMs
`are located using conventional locating capability mentioned above. DLMs provide
`reference locations for automatically locating ILMs, regardless of where any one is
`currently located. DLMs and ILMs can be highly mobile, for example when in use by a
`user. There are a variety of novel methods for automatically locating ILMs, for example
`triangulating an ILM (Indirectly Located Mobile data processing system) location using a
`plurality of DLMs, detecting the ILM being within th