US010292011B2
`
`US 10,292,011 B2
`(10) Patent No:
`a2) United States Patent
`Johnson
`(45) Date of Patent:
`May14, 2019
`
`
`(54) SYSTEM AND METHOD FOR LOCATION
`BASED EXCHANGE NETWORK
`
`(71) Applicant: William J. Johnson, Flower Mound,
`TX (US)
`
`(72)
`
`Inventor: William J. Johnson, Flower Mound,
`TX (US)
`
`(*) Notice:
`
`Subject to any disclaimer, the termof this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21) Appl. No.: 16/147,532
`
`(22) Filed:
`
`Sep. 28, 2018
`
`(65)
`
`Prior Publication Data
`
`(2012.01)
`(2012.01)
`
`G060 10/08
`GN6Q 30/06
`(52) U.S. Cl.
`GPG,
`sxeeseevenes HOAW 4/023 (2013.01); HO4H 20/16
`(2013.01); HO4L 41/0816 (2013.01); HO4L
`43/16 (2013.01); HO4L 67/104 (2013.01);
`HO4W 4/02 (2013.01); HO4W 12/06
`(2013.01); HO4W 40/20 (2013.01); HO4W
`40/244 (2013.01); HO4W64/00 (2013.01);
`G06Q 10/087 (2013.01); G06Q 10/0833
`(2013.01); GO6O 30/0633 (2013.01)
`(58) Field of Classification Search
`GPE wes: HO04W4/02; H04W 64/00; HO4W 4/023;
`HO4W12/06; HO4W40/20; HO4W
`40/244; HO4W92/18, HO4W4/21; HO4W
`4/50; HO4W4/80; HO4W 68/005; HO4W88/02
`See application file for complete search history.
`
`US 2019/0037354 Al
`
`Jan. 31, 2019
`
`(56)
`
`References Cited
`
`Related U.S. Application Data
`(63) Continuation of application No. 15/218,039, filed on
`Stil. 2, 2018, snow Pat. ING. JO UCLOS4,
`‘waktieh. #8 4
`continuation of application No. 14/752,945, filed on
`Jun. 28, 2015, now Pat. No. 9,456,303, which is a
`(Continued)
`/
`continuation of application No. 13/972,125, filed on
`;
`Aug. 21, 2013, now Pat. No. 9,078,095, which isa=Primary Examiner — Liton Miah
`(Continued)
`(74) Attorney, Agent, or Firm — Yudell Isidore PLLC
`
`U.S. PATENT DOCUMENTS
`6,427,115 BI*
`7/2002 Sekiyama.......... GO1C ;sess
`2001/0022558 AL*
`9/2001 Karty It. sacs GOIS 1/026
`342/450
`
`(51)
`
`Int. CL
`HOAM 11/04
`HO4M 3/42
`HOAW 4/02
`HOAH 20/16
`HOAL 12/24
`HO4L 1226
`HOAL 29/08
`HOAW 40/20
`HOAW 40/24
`HO4AW 64/00
`HO4AW 12/06
`
`(2006.01)
`(2006.01)
`(2018.01)
`(2008.01)
`(2006.01)
`(2006.01)
`(2006.01)
`(2009.01)
`(2009.01)
`(2009.01)
`(2009.01)
`
`ABSTRACT
`(57)
`Mobile data processing Systems (MSs) interact with systems
`in their vicinity, and with each other, in communications and
`interoperability. Information transmitted inboundto, trans-
`mitted outbound from,
`is in process at, or is application
`modified at a mobile data processing system triggers pro-
`cessing of actions in accordance with user configurations,
`for example to present content
`to a user. The locatable
`network of MSs is referred to as a Location-Network
`Fxpanse.
`
`20 Claims, 322 Drawing Sheets
`
`
`‘START- Thread for
`Antenna locate MS when
`
`
`
`detected in range
`
`
`
`Authenticated MS
`signal detected
`
`
`
`Respond pack asap 10:
`MSwith current
`antenna whereaboute
`info
`
`
`
`
`MScompletes a
`
`
`
`whereabouts data
`Insertion
`
`Invoke.
`Whereabouts Data
`
`
`BILLJCO
`EX2027 - Page 1 of 2
`
`BILLJCO
`EX2027 - Page 1 of 2
`
`

`

`US 10,292,011 B2
`
`
`
`LS
`
`ty25
`
`3D
`
`447
`disclosure. For example, a proven popular MS charter
`configuration may be replaced by providing a privilege
`which can be used between MSs, thereby eliminating the
`need to go through the time to configure the charter. The
`privilege itselfreplaces what the charter provided. In another
`example, a new atomic command maybeused to replace
`complex charter configurations, or replaces a set of specific
`use of a plurality of other atomic commands, in order to
`prevent burdening MSusers with configuring desirable MS
`behavior.
`There are many embodiments for synchronizing key
`regions of executable code of this disclosure, and locking
`into a single detailed design is not intended. A synchroni-
`zation design can vary based on software programming
`decisions. In some embodiments, a MS is equipped with
`a
`
`different synchronization models which are configurable at
`manufacturing time, or by an administrator or user. In some
`embodiments,
`a prescribed synchronization model
`is
`nN Cc
`deployed based onthe type of MS and anticipated use of the 2
`MS. For example, WI'T'S processing, or subsets therein, may
`be semaphore protected so that only a single WDR is
`processedat critical regions in charter processing. Identify-
`ing critical regions can be dependent on different uses of the
`LBXarchitecture. In one example, this can be advantageous
`for WITS processing involving many MSs with privileged
`configurationsin the vicinity of a receiving MS. Consider an
`electronic tag example. In this example, one MSis “it” and
`a plurality of other MSs are avoiding becoming “it”. When
`the “at” MS becomes close enoughto an other MS, the other
`MSbecomes “it”. But what happens when the MS becomes
`close enough to a plurality of other MSs? Which MS
`becomes “it”? It is important to prevent making more than
`one MS “it”, thus synchronization provides a more conve-
`nient method for preventing this from happening. To provide
`clear explanation, assume that only a single iWITS WDR
`processing thread can execute FIG. 57 at a time. Whilc it is
`certainly better performance to identify the processing
`block(s) (.e. subset(s)) of FIG. 57 processing that should be
`synchronized rather than the entire FIG. 57 processing,
`doing so here for exemplification simplifies the electronic
`tag discussion. Thus, if there is a group of MSs in a group
`called PlayTag known to each participating MS, every
`privileged MScanhave the following charter configuration
`in light of the synchronization to FIG. 57 processing:
`(_1_msid*PlayTag” & \loc_my $(1M)_I_location &
`T_it):
`Invoke Data (T_il, True, _]_msid),
`Invoke Data (1_it, False, \thisMS);
`Notice that the charter configuration assumesa single unit of :
`work including the time of checking the T_it variable
`(True=your“it”), marking the MS which is within 1 meter
`to this MS locationas being “it”, and the time ofclearing the
`local application variable which marks this MSas being “it”.
`Synchronization becomes quite important for this charter to
`operatorcorrectly, otherwise another MS can cause process-
`ing the same charter at substantially the same time for
`unpredictable results. ‘hus, thread processing synchroniza-
`tion is to be analyzed and incorporated as is appropriate in
`context of the various embodiments for deployment. In the
`example,
`the electronic tag application (e.g. with prefix
`“T_”) may additionally monitor the T_itAppTermvariable
`to cause a beaconing sound, and/or beaconing visual indi-
`cation (flashing bright red screen) so that nearby MS users
`knowwho is “it”.
`Various company name and/or product name trademarks
`used herein belong to their respective companies.
`
`
`
`45
`
`55
`
`65
`
`448
`While various embodiments of the present disclosure
`have been described above,it should be understoodthat they
`have been presented by way of example only, and not
`limitation. Thus,
`the breadth and scope of the present
`disclosure should not be limited by any of the above-
`described exemplary embodiments, but should be defined
`only in accordance with the following claims and their
`equivalents.
`
`Whatis claimed is:
`1. A system including one or more sending data process-
`ing systems wherein each sending data processing system of
`the one or more sending data processing systems comprise:
`one or more processors; and
`memory coupled to the one or more processors and
`sloring instructions, wherein the one or more proces-
`sors, based on the instructions, perform operations
`comprising:
`periodically beaconing outbound a broadcast unidirec-
`tional wireless data record for physically locating in
`a regionofthe sending data processing system one or
`more receiving user carried mobile data processing
`systems, the broadcast unidirectional wireless data
`record received directly from the sending data pro-
`cessing system in each receiving user carried mobile
`data processing system ofthe one or more receiving
`user carried mobile data processing systems, and
`including:
`no physical location coordinates of the sending data
`processing system,
`a data field containing a signal strength of the
`sending data processing system. and
`application context identifier data identifying loca-
`tion based content for presenting by a location
`based application of the receiving user carried
`mobile data processing system to a user interface
`of the reeciving user carried mobile data process-
`ing system uponthe receiving user carried mobile
`data processing system determining with a local
`memory maintained location based configuration
`monitored with background processing of the
`receiving user carried mobile data processing sys-
`tem during mobility of the receiving user carried
`mobile data processing systemanticipating receipt
`of the broadcast unidirectional wireless data
`record having the application context identifier
`data in response to a user activating the location
`based application with the user interface of the
`receiving user carried mobile data processing sys-
`tem wherein the location based application:
`invokes a location based APIofthe receiving user
`carried mobile data processing system for the
`location based configuration anticipating, the
`receipt of the broadcast unidirectional wireless
`data record having the application context iden-
`tifier data,
`is notified upon the receipt of the broadcast uni-
`directional wireless data record having the
`application context identificr data configured in
`the location based configuration, and
`presents the location based content
`to the user
`interface of the receiving user carried mobile
`data processing system, the location based con-
`tent originating from another data processing
`system that is remote to both the sending data
`processing system and the receiving user car-
`ried mobile data processing system.
`
`BILLJCO
`EX2027 - Page 2 of 2
`
`BILLJCO
`EX2027 - Page 2 of 2
`
`