PTO/AIN14 (08-12)
`Approved for use through 01/31/2014. 0MB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid 0MB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`JOHNS-001 US3
`
`Application Number
`
`Title of Invention
`
`I System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications
`
`The application data sheet is part of the provisional or nonprovisional application for which it is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`document may be printed and included in a paper filed application.
`
`Secrecy Order 37 CFR 5.2
`Portions or all of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuant to
`D 37 CFR 5.2 (Paper filers only. Applications that fall under Secrecy Order may not be filed electronically.)
`Inventor Information:
`
`1
`Inventor
`Legal Name
`
`I Remove I
`
`Prefix Given Name
`
`Middle Name
`
`Family Name
`
`Suffix
`
`Johnson
`J.
`William
`0 Non US Residency 0 Active US Military Service
`Residence Information (Select One) (!) US Residency
`I State/Province I TX
`I Country of Residence i I US
`City
`Flower Mound
`
`Mailing Address of Inventor:
`
`1704 Katherine Court
`
`Address 1
`Address 2
`I State/Province
`City
`I Flower Mound
`I us
`I Country 1
`I 75022
`Postal Code
`All Inventors Must Be Listed - Additional Inventor Information blocks may be
`generated within this form by selecting the Add button.
`
`I TX
`
`I Add I
`
`Correspondence Information:
`Enter either Customer Number or complete the Correspondence Information section below.
`For further information see 37 CFR 1.33(a).
`□ An Address is being provided for the correspondence Information of this application.
`Customer Number
`42640
`
`Email Address
`
`patents@yudellisidore.com
`
`I I Add Email I
`
`!Remove Emaill
`
`Application Information:
`System and Method for Location Based Exchanges of Data Facilitating Distributed Locational
`Annlications
`Attorney Docket Number JOHNS-001 US3
`
`Title of the Invention
`
`I Small Entity Status Claimed ~
`
`Application Type
`
`Nonprovisional
`
`Subject Matter
`Suggested Class (if any)
`Suggested Technology Center (if any)
`
`Utility
`
`Isub Class (if any)
`
`I
`
`Total Number of Drawing Sheets (if any)
`
`70
`
`I Suggested Figure for Publication (if any) I
`
`EFS Web 2.2.3
`
`Exhibit 1002
`IPR2022-00426
`Page 1 of 755
`
`

`

`PTO/AIN14 (08-12)
`Approved for use through 01/31/2014. 0MB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid 0MB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`JOHNS-001 US3
`
`Application Number
`
`Title of Invention
`
`System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications
`
`Publication Information:
`D Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`Request Not to Publish. I hereby request that the attached application not be published under
`D 35 U.S.C. 122(b) and certify that the invention disclosed in the attached application has not and will not be the
`subject of an application filed in another country, or under a multilateral international agreement, that requires
`publication at eighteen months after filing.
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a power of attorney in the application (see 37 CFR 1.32).
`Either enter Customer Number or complete the Representative Name section below. If both sections are completed the customer
`Number will be used for the Representative Information during processing.
`
`Please Select One:
`
`Customer Number
`
`® Customer Number
`42640
`
`I O US Patent Practitioner 10 Limited Recognition (37 CFR 11.9)
`
`Domestic Benefit/National Stage Information:
`This section allows for the applicant to either claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(c) or indicate
`National Stage entry from a PCT application. Providing this information in the application data sheet constitutes the
`specific reference required by 35 U.S.C. 119(e) or 120, and 37 CFR 1.78.
`I Remove I
`Filing Date (YYYY-MM-DD)
`
`Application Number
`
`Continuity Type
`
`Prior Application Number
`
`Prior Application Status Pending
`
`Continuation of
`
`12077041
`
`Additional Domestic Benefit/National Stage Data may be generated within this form
`by selecting the Add button.
`
`2008-03-14
`I
`
`Add
`
`I
`
`Foreign Priority Information:
`This section allows for the applicant to claim benefit of foreign priority and to identify any prior foreign application for which priority is
`not claimed. Providing this information in the application data sheet constitutes the claim for priority as required by 35 U.S.C. 119(b)
`and 37 CFR 1.55(a).
`
`Application Number
`
`Country i
`
`Additional Foreign Priority Data may be generated within this form by selecting the
`Add button.
`
`I Remove I
`Filing Date (YYYY-MM-DD)
`Priority Claimed
`0 Yes ® No
`I
`
`I
`
`Add
`
`EFS Web 2.2.3
`
`Exhibit 1002
`IPR2022-00426
`Page 2 of 755
`
`

`

`PTO/AIN14 (08-12)
`Approved for use through 01/31/2014. 0MB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid 0MB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`JOHNS-001 US3
`
`Application Number
`
`Title of Invention
`
`System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications
`
`Authorization to Permit Access:
`
`~ Authorization to Permit Access to the Instant Application by the Participating Offices
`
`If checked, the undersigned hereby grants the USPTO authority to provide the European Patent Office (EPO),
`the Japan Patent Office (JPO), the Korean Intellectual Property Office (KIPO), the World Intellectual Property Office (WIPO),
`and any other intellectual property offices in which a foreign application claiming priority to the instant patent application
`is filed access to the instant patent application. See 37 CFR 1.14(c) and (h). This box should not be checked if the applicant
`does not wish the EPO, JPO, KIPO, WIPO, or other intellectual property office in which a foreign application claiming priority
`to the instant patent application is filed to have access to the instant patent application.
`
`In accordance with 37 CFR 1.14(h)(3), access will be provided to a copy of the instant patent application with respect
`to: 1) the instant patent application-as-filed; 2) any foreign application to which the instant patent application
`claims priority under 35 U.S.C. 119(a)-(d) if a copy of the foreign application that satisfies the certified copy requirement of
`37 CFR 1.55 has been filed in the instant patent application; and 3) any U.S. application-as-filed from which benefit is
`sought in the instant patent application.
`
`In accordance with 37 CFR 1.14(c), access may be provided to information concerning the date offiling this Authorization.
`
`Applicant Information:
`
`Providing assignment information in this section does not substitute for compliance with any requirement of part 3 of Title 37 of CFR
`to have an assignment recorded by the Office.
`
`Applicant 1
`If the applicant is the inventor (or the remaining joint inventor or inventors under 37 CFR 1.45), this section should not be completed.
`The information to be provided in this section is the name and address of the legal representative who is the applicant under 37 CFR
`1.43; or the name and address of the assignee, person to whom the inventor is under an obligation to assign the invention, or person
`who otherwise shows sufficient proprietary interest in the matter who is the applicant under 37 CFR 1.46. If the applicant is an
`applicant under 37 CFR 1.46 (assignee, person to whom the inventor is obligated to assign, or person who otherwise shows sufficient
`proprietary interest) together with one or more joint inventors, then the joint inventor or inventors who are also the applicant should be
`identified in this section.
`
`I Remove I
`
`Assignee
`
`0
`0
`If applicant is the legal representative, indicate the authority to file the patent application, the inventor is:
`
`Person to whom the inventor is obligated to assign.
`
`Person who shows sufficient proprietary interest
`
`lo Legal Representative under 35 U.S.C. 117
`lo
`
`Name of the Deceased or Legally Incapacitated Inventor : I
`
`If the Assignee is an Organization check here.
`
`Prefix
`
`Given Name
`
`□
`Middle Name
`
`I
`
`Family Name
`
`Suffix
`
`EFS Web 2.2.3
`
`Exhibit 1002
`IPR2022-00426
`Page 3 of 755
`
`

`

`PTO/AIN14 (08-12)
`Approved for use through 01/31/2014. 0MB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid 0MB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`JOHNS-001 US3
`
`Application Number
`
`Title of Invention
`
`System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications
`
`Mailing Address Information:
`
`Address 1
`
`Address 2
`
`City
`
`Country ii
`
`Phone Number
`
`Email Address
`
`State/Province
`
`Postal Code
`
`Fax Number
`
`Additional Applicant Data may be generated within this form by selecting the Add button.
`
`I Add I
`
`Signature:
`NOTE: This form must be signed in accordance with 37 CFR 1.33. See 37 CFR 1.4 for signature requirements and
`certifications
`
`Remove
`
`Signature
`
`/Craig J. Yudell/
`
`Date (YYYY-MM-DD) 2013-09-23
`
`First Name
`
`Craig
`
`I Last Name I Yudell
`
`Additional Signature may be generated within this form by selecting the Add button.
`
`Registration Number
`I Add I
`
`39083
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet 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.
`
`EFS Web 2.2.3
`
`Exhibit 1002
`IPR2022-00426
`Page 4 of 755
`
`

`

`Privacy Act Statement
`
`The Privacy Act of 1974 (P .L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to
`a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised that: (1) the general authority for the collection
`of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is
`used by the U.S. Patent and Trademark Office is to process and/or examine your submission related to a patent application or patent. If you do not
`furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may
`result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552)
`and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Department of Justice to determine
`whether the Freedom of Information Act requires disclosure of these records.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a court, magistrate, or
`administrative tribunal, including disclosures to opposing counsel in the course of settlement negotiations.
`
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a request involving an
`individual, to whom the record pertains, when the individual has requested assistance from the Member with respect to the subject matter of
`the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in
`order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as
`amended, pursuant to 5 U.S.C. 552a(m).
`
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of records may be disclosed,
`as a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant to the Patent Cooperation Treaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of National Security
`review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or his/her designee,
`during an inspection of records conducted by GSA as part of that agency's responsibility to recommend improvements in records
`management practices and programs, under authority of 44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the
`GSA regulations governing inspection of records for this purpose, and any other relevant (i.e., GSA or Commerce) directive. Such
`disclosure shall not be used to make determinations about individuals.
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuan
`to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37
`CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were
`terminated and which application is referenced by either a published application, an application open to public inspections or an issued
`patent.
`
`9.
`
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law enforcement agency, if the
`USPTO becomes aware of a violation or potential violation of law or regulation.
`
`EFS Web 2.2.3
`
`Exhibit 1002
`IPR2022-00426
`Page 5 of 755
`
`

`

`SYSTEM AND METHOD FOR
`
`LOCATION BASED EXCHANGES OF DATA
`
`FACILITATING DISTRIBUTED LOCATIONAL APPLICATIONS
`
`5
`
`CROSS-REFERENCES TO RELATED APPLICATIONS
`
`This application is a continuation of application serial number 12/077,041 filed
`
`March 14, 2008 and entitled "System and Method for Location Based Exchanges of Data
`
`Facilitating Distributed Locational Applications". This application contains an identical
`
`specification to serial number 12/077,041 except for the abstract, claims, and minor
`
`10
`
`modifications resulting from a Preliminary Amendment filed November 17, 2008 and a
`
`Preliminary Amendment B filed February 10, 2009.
`
`FIELD OF THE INVENTION
`
`The present disclosure relates generally to location based services for mobile data
`
`15
`
`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.
`
`20
`
`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
`
`25
`
`(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
`
`30
`
`services provided, having a supervisory point of control, providing an administrator with
`
`WJJ0701B
`
`Exhibit 1002
`IPR2022-00426
`Page 6 of 755
`
`

`

`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
`
`5
`
`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
`
`devices, various handheld mobile data processing systems, and other mobile data
`
`10
`
`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
`
`15
`
`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,
`
`20
`
`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
`
`25
`
`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
`
`30
`
`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
`
`WJJ0701B
`
`2
`
`Exhibit 1002
`IPR2022-00426
`Page 7 of 755
`
`

`

`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
`
`5
`
`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.
`
`Publication 2006/0022048 (Johnson) could cause large numbers of users to inundate the
`
`10
`
`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.
`
`15
`
`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
`
`20
`
`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
`
`25
`
`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
`
`30
`
`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
`
`WJJ0701B
`
`3
`
`Exhibit 1002
`IPR2022-00426
`Page 8 of 755
`
`

`

`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
`
`5
`
`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),
`
`iPhones (iPhone is a trademark of Apple, Inc.), various handheld mobile data processing
`
`10
`
`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
`
`15
`
`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
`
`20
`
`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
`
`25
`
`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.
`
`30
`
`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
`
`WJJ0701B
`
`4
`
`Exhibit 1002
`IPR2022-00426
`Page 9 of 755
`
`

`

`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
`
`5
`
`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
`
`10
`
`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
`
`15
`
`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-
`
`20
`
`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
`
`25
`
`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.
`
`30
`
`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
`
`WJJ0701B
`
`5
`
`Exhibit 1002
`IPR2022-00426
`Page 10 of 755
`
`

`

`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
`
`5
`
`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
`
`registering with a service. MSs interact as peers in preferred embodiments, rather than as
`
`10
`
`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)
`
`15
`
`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 stationary located antenna, presence detection at a wired
`
`connectivity stationary network location, or other conventional locating systems and
`
`20
`
`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
`
`25
`
`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
`
`30
`
`plurality of DLMs, detecting the ILM being within the vicinity of at least one OLM,
`
`triangulating an ILM location using a plurality of other ILMs, detecting the ILM being within
`
`the vicinity of at least one other ILM, triangulating an ILM location using a mixed set of
`
`WJJ0701B
`
`6
`
`Exhibit 1002
`IPR2022-00426
`Page 11 of 755
`
`

`

`DLM(s) and ILM(s), determining the ILM location from heterogeneously located DLMs
`
`and/or ILMs, and other novel methods.
`
`MSs are automatically located without using direct conventional means for being
`
`automatically located. The conventional locating capability (i.e. conventional locating
`
`5
`
`methods) described above is also referred to as direct methods. Conventional methods
`
`are direct methods, but not all direct methods are conventional. There are new direct
`
`techniques disclosed below. Provided herein is an architecture, as well as systems and
`
`methods, for immediately bringing automatic location detection to every MS in the world,
`
`regardless of whether that MS is equipped for being directly located. MSs without
`
`10
`
`capability of being directly located are located by leveraging the automatically detected
`
`locations of MSs that are directly located. This is referred to as being indirectly located. An
`
`MS which is directly located is hereinafter referred to as a Directly Located Mobile data
`
`processing system (OLM). For a plural acronym, MSs which are directly located are
`
`hereinafter referred to as Directly Located Mobile data processing systems (DLMs). MSs
`
`15
`
`with