US20140289234A1 - System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications - Google Patents
System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications Download PDFInfo
- Publication number
- US20140289234A1 US20140289234A1 US14/299,910 US201414299910A US2014289234A1 US 20140289234 A1 US20140289234 A1 US 20140289234A1 US 201414299910 A US201414299910 A US 201414299910A US 2014289234 A1 US2014289234 A1 US 2014289234A1
- Authority
- US
- United States
- Prior art keywords
- data processing
- information
- processing system
- block
- location
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G06F17/30424—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/023—Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
Definitions
- ILMs Indirectly Located Mobile data processing systems
- DLMs Directly Located Mobile data processing systems
- ILMs are provided with the ability to participate in the same LBS, or LBX, as a DLM (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.
- Another advantage is providing synergy between different locating technologies for smooth operations as an MS travels.
- FIG. 2C depicts an illustration for discussing an example of automatically locating a MS through the MS coming into range of some stationary antenna
- FIG. 8A heterogeneously depicts a locating by arbitrary wave spectrum illustration for discussing automatic location of a MS
- PIP data 8 contains intelligence data for driving LBX processing logic of the present disclosure when interacting with other MSs.
- Self management processing code 18 comprises executable code in software, firmware, or hardware form for carrying out the local user interface LBX processing logic of the present disclosure.
- Self management processing data 20 contains intelligence data for driving processing logic of the present disclosure as disclosed for locally maintained LBX features.
- WDR queue 22 contains Whereabouts Data Records (WDRs) 1100 , and is a First-In-First-Out (FIFO) queue when considering housekeeping for pruning the queue to a reasonable trailing history of inserted entries (i.e. remove stale entries).
- Queue embodiments may contain fixed length records, varying length records, pointers to fixed length records, or pointers to varying length records. If pointers are used, it is assumed that pointers may be dynamically allocated for record storage on insertions and freed upon record use after discards or retrievals.
- NTP use among participating systems has the advantage of a single unidirectional broadcast data packet containing all a receiving system requires to measure TDOA, by knowing when the data was sent (date/time stamp in packet) and when the data was received (signal detected and processed by receiving system).
- a NTP clock source e.g. atomic clock
- a NTP clock source used in a network is to be reasonably granular to carry out measurements, and ensures participating MSs are updated timely according to anticipated time drifts of their own clocks.
- There are many well known methods for accomplishing NTP some which require dedicated thread(s) for NTP processing, and some which use certain data transmitted to and from a source to keep time in synch.
- FIG. 1E depicts a network illustration for discussing various deployments of whereabouts processing aspects of the present disclosure.
- a cellular network cluster 102 and cellular network cluster 104 are parts of a larger cellular network.
- Cellular network cluster 102 contains a controller 106 and a plurality of base stations, shown generally as base stations 108 .
- Each base station covers a single cell of the cellular network cluster, and each base station 108 communicates through a wireless connection with the controller 106 for call processing, as is well known in the art.
- Wireless devices communicate via the nearest base station (i.e. the cell the device currently resides in), for example base station 108 b .
- procedure processing starts at block 270 and continues to block 272 where parameters passed from the invoking block of processing, for example block 240 , are determined.
- the variable WDRREF is set by the caller to a reference or pointer to the WDR so subsequent blocks of FIG. 2F can access the WDR.
- the variable DELETEQ is set by the caller so that block 292 knows how to discard obsolete location queue entries.
- the MS completes its own WDR at block 334 for adding to WDR queue 22 to know its own whereabouts whenever possible, and block 336 prepares parameters for invoking WDR insertion processing at block 338 .
- the MS invokes FIG. 2F processing already described. After block 338 , processing continues back to block 312 .
- FIG. 6B depicts a flowchart for describing a preferred embodiment of a MS whereabouts update event of a physically, or logically, connected MS, for example a DLM 200 .
- a MS may be newly located and physically/logically connected, whereby communications between the MS and service is over a physical/logical connection as described in FIG. 6A above.
- Relevant processing begins at block 640 and continues to block 642 where an MS device is physically/logically connected. Thereafter, at block 644 the MS accesses the connectivity service and waits for an acknowledgement indicating a successful connection. Upon acknowledgement receipt, processing continues to block 646 where the MS requests WDR information via the connectivity service and waits for the data (i.e.
- a well placed and recognizable vertical line 710 a and horizontal line 710 b which are preferably perpendicular to each other, have known lengths and positions.
- the objects which come into the field of view are measured based on the known lengths and positions of the lines 710 a and 710 b which may be landscape markings (e.g. parking lot lines) for additional purpose.
- Field of view 704 may contain many lines and/or objects of known dimensions strategically placed or recognized within the field of view 704 to facilitate image processing by service 700 .
- Building 714 may serve as a reference point having known dimension and position in measuring objects such as a person 716 or DLM 200 .
- block 868 determines a timeout was encountered from the service broadcast request, then block 872 provides the user with an error to the user interface, and processing continues back to block 852 . If block 868 determines there was no timeout (i.e. whereabouts successfully determined), then block 870 receives WDR information from the locating interface of the responding service, block 874 completes a WDR, and blocks 876 and 878 do as already described above.
- a MS may go in and out of DLM or ILM roles as it is mobile. Direct location methods are not always available to the MS as it roams, therefore the MS preferably does all of 1 through 5 above.
- the WDR 1100 contains a MS ID field 1100 a matching the MS which owns queue 22 , that WDR contains the location (location field 1100 c ) with a specified confidence (field 1100 d ) at a particular time (date/time stamp field 1100 b ) for that MS.
- the MS ID field 1100 a , date/time stamp field 1100 b and confidence field 1100 d is all that is required for searching from the queue 22 the best possible, and most timely, MS whereabouts at the time of searching queue 22 .
- Sent date/time stamp field 1100 n is optionally present in a WDR when the WDR is in transmission between systems (e.g. wireless communications) such as in data 1302 or 1312 .
- Field 1100 n contains when the WDR was transmitted.
- a time zone, day/light savings time, and NTP indicator is preferably maintained as part of field 1100 n .
- Field 1100 n is preferably not present in WDRs of queue 22 (but can be if TDOA measurement calculation is delayed to a later time). In some embodiments, there is no need for field 1100 n .
- Received date/time stamp field 1100 p is preferably present in a WDR when inserted to queue 26 by receiving thread(s) upon received data 1302 or 1312 .
- Field 1100 p contains when the WDR was received by the MS.
- a time zone, day/light savings time, and NTP indicator is preferably maintained as part of field 1100 p .
- Field 1100 p is preferably not present in WDRs of queue 22 (but can be if TDOA measurement calculation is delayed to a later time). In some embodiments, there is no need for field 1100 p .
- thread(s) 1912 may be listening directly on applicable channel(s) and can determine when the data is received.
- block 1232 spawns (starts) the process (e.g. 1952 ) of FIG. 29A to start execution of subordinate worker thread(s) (e.g. process 1952 thread(s)) and saves the real PID (Process Identifier) to the PID variable (e.g. 1952 -PID) returned by the operating system process spawn interface.
- Block 1232 passes as a parameter to the process of FIG. 29A which process name to start (e.g. 1952 ), and continues to block 1234 . If block 1230 determines the current process PID variable (e.g. 1952 -PID) is not greater than 0 (i.e. not to be started; also implies is disabled as used in FIGS.
- Block 2016 causes broadcasting data 1302 containing CK 1304 wherein CK 1304 contains WDR information prepared as described above for block 2014 .
- Alternative embodiments of block 2010 may not search a specified confidence value, and broadcast the best entry available anyway so that listeners in the vicinity will decide what to do with it.
- a semaphore protected data access (instead of a queue peek) may be used in embodiments where there is always one WDR current entry maintained for the MS.
- FIG. 20 sends repeated timely pulsed broadcasts of new data 1302 (per SPTP) for MSs in the vicinity of the first MS to receive.
- appropriate implementation should ensure field 1100 n is as accurate as possible for when data 1302 is actually sent.
- Blocks 2134 and 2136 may be replaced with an alternative embodiment for starting a thread 1952 . Block 2136 continues back to block 2106 .
- Processing begins at block 2602 , continues to block 2604 where the process worker thread count 1952 -Ct is accessed and incremented by 1 (using appropriate semaphore access (e.g. 1952 -Sem)), and continues to block 2606 for interim housekeeping of pruning the WDR queue by invoking a Prune Queues procedure of FIG. 27 .
- Block 2604 may also check the 1952 -Ct value, and signal the process 1952 parent thread that all worker threads are running when 1952 -Ct reaches 1952 -Max.
- Block 2606 may not be necessary since pruning may be accomplished at block 2620 when invoking FIG. 2F (block 292 ).
- Block 2682 preferably keeps track of (or checks THIS_MS for) what it has thus far determined whereabouts for in this FIG. 26B thread processing to prevent inserting the same WDR to THIS_MS using the same REMOTE_MS data. Repeated iterations of blocks 2676 through 2682 will see the same data from previous iterations and will use the best of breed data in conjunction with each other at each iteration (in current thread context). While inserting duplicates to THIS_MS at block 2682 does not cause failure, it may be avoided for performance reasons. Duplicate insertions are preferably avoided at block 2674 for performance reasons as well, but they are again not harmful. Block 2678 preferably keeps track of previous diversity order in this FIG.
- Block 2818 destroys semaphore(s) created at block 1220 . Thereafter, block 2820 destroys queue(s) created at block 1218 (may have to remove all entries first in some embodiments), block 2822 saves persistent variables to persistent storage (for example to persistent storage 60 ), block 2824 destroys shared memory created at block 1212 , and block 2826 checks the NTP use variable (saved prior to destroying shared memory at block 2824 ).
- FIG. 29B depicted is a flowchart for describing a preferred embodiment of a procedure for terminating a process started by FIG. 29A .
- the procedure starts at block 2952 and continues to block 2954 where parameters passed are determined.
- the type of process is set to 0 for a process which has worker threads which are a slave to a queue.
- the type of process is set to a valid O/S PID when the process worker threads are slave to a timer.
- block 2968 inserts a special WDR queue 22 entry enabling a queue peek for worker thread termination.
- the reader will notice that the process termination order of block 2806 ensures processes which were slaves to the WDR queue 22 have already been terminated. This allows processes which are slaves to a timer to see the special termination queue entry inserted at block 2968 since no threads (which are slaves to queue) will remove it from queue 22 .
- block 2970 waits until the 19 xx process name (parameter) worker threads have been terminated using a preferred choice of waiting described for blocks 2918 and 2920 .
- the 19 xx process (e.g.
- the MS ID (or pseudo MS ID) in transmissions is useful for a receiving data processing system to target a response by addressing the response back to the MS ID.
- Targeted transmissions target a specific MS ID (or group of MS IDs), while broadcasting is suited for reaching as many MS IDs as possible. Alternatively, just a correlation is enough to target a data source.
Abstract
Provided is a distributed system and method for enabling new and useful location dependent features and functionality to mobile data processing systems. Mobile data processing systems interact with each other as peers in communications and interoperability. A mobile data processing system may dynamically take on roles, depending on the environment and capabilities available at a particular time. Reference whereabouts data is appropriately shared between mobile data processing systems to carry out automatic location techniques ensuring mobile data processing systems are kept up to date with their own whereabouts and whereabouts of others, regardless of the freely moving travels of any of the mobile data processing systems involved, and the location technologies that may or may not be available when needed. A confidence is associated to whereabouts data shared for facilitating selection of the best candidate data used in determining new whereabouts information.
Description
- This application is a continuation of application Ser. No. 14/033,539 (U.S. Pat. No. 8,750,823 to be issued on Jun. 10, 2014) filed Sep. 23, 2013 and entitled “System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications” which is a continuation of application Ser. No. 12/077,041 (now U.S. Pat. No. 8,600,341 issued on Dec. 3, 2013) filed Mar. 14, 2008 and entitled “System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications”. This application contains an identical specification to Ser. No. 14/033,539 except for the claims which are very similar.
- 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.
- 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 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. Pat. Nos. 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 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), 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.
- 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 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-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 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 stationary 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 DLM (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 the vicinity of at least one DLM, 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 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 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 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 (DLM). For a plural acronym, MSs which are directly located are hereinafter referred to as Directly Located Mobile data processing systems (DLMs). MSs without capability of being directly located are located using the automatically detected locations of MSs that have already been located. An MS which is indirectly located is hereinafter referred to as an Indirectly Located Mobile data processing system (ILM). For a plural acronym, MSs which are indirectly located are hereinafter referred to as Indirectly Located Mobile data processing systems (ILMs). A DLM can be located in the following ways:
-
- A) New triangulated wave forms;
- B) Missing Part Triangulation (MPT) as disclosed below;
- C) Heterogeneous direct locating methods;
- D) Assisted Direct Location Technology (ADLT) using a combination of direct and indirect methods;
- E) Manually specified; and/or
- F) Any combinations of A) through E);
DLMs provide reference locations for automatically locating ILMs, regardless of where the DLMs are currently located. It is preferable to assure an accurate location of every DLM, or at least provide a confidence value of the accuracy. A confidence value of the accuracy is used by relative ILMs to determine which are the best set (e.g. which are of highest priority for use to determine ILM whereabouts) of relative DLMs (and/or ILMs) to use for automatically determining the location of the ILM.
- In one example, the mobile locations of several MSs are automatically detected using their local GPS chips. Each is referred to as a DLM. The mobile location of a non-locatable MS is triangulated using radio waves between it and three (3) of the GPS equipped DLMs. The MS becomes an ILM upon having its location determined relative the DLMs. ILMs are automatically located using DLMs, or other already located ILMs. An ILM can be located in the following ways:
-
- G) Triangulating an ILM location using a plurality of DLMs with wave forms of any variety (e.g. AOA, TDOA, MPT (a heterogeneous location method));
- H) Detecting the ILM being within the reasonably close vicinity of at least one DLM;
- I) Triangulating an ILM location using a plurality of other ILMs with wave forms of any variety;
- J) Detecting the ILM being within the reasonable close vicinity of at least one other ILM;
- K) Triangulating an ILM location using a mixed set of DLM(s) and ILM(s) with wave forms of any variety (referred to as ADLT);
- L) Determining the ILM location from heterogeneously located DLMs and/or ILMs (i.e. heterogeneously located, as used here, implies having been located relative different location methodologies);
- M) A) through F) Above; and/or
- N) Any combinations of A) through M).
- Locating functionality may leverage GPS functionality, including but not limited to GPS, AGPS (Adjusted GPS), DGPS, (Differential GPS), or any improved GPS embodiment to achieve higher accuracy using known locations, for example ground based reference locations. The NexTel GPS enabled iSeries cell phones provide excellent examples for use as DLMs (Nextel is a trademark of Sprint/Nextel). Locating functionality may incorporate triangulated locating of the MS, for example using a class of Radio Frequency (RF) wave spectrum (cellular, WiFi, bluetooth, etc), and may use measurements from different wave spectrums for a single location determination (depends on communications interface(s) 70 available). A MS may have its whereabouts determined using a plurality of wave spectrum classes available to it (cellular, WiFi, bluetooth, etc). Locating functionality may include in-range proximity detection for detecting the presence of the MS. Wave forms for triangulated locating also include microwaves, infrared wave spectrum relative infrared sensors, visible light wave spectrum relative light visible light wave sensors, ultraviolet wave spectrum relative ultraviolet wave sensors, X-ray wave spectrum relative X-ray wave sensors, gamma ray wave spectrum relative gamma ray wave sensors, and longwave spectrum (below AM) relative longwave sensors. While there are certainly more common methods for automatically locating a MS (e.g. radio wave triangulation, GPS, in range proximity detection), those skilled in the art recognize there are methods for different wave spectrums being detected, measured, and used for carrying information between data processing systems.
- Kubler et al (
U.S. PTO publications 2004/0264442, 2004/0246940, 2004/0228330, 2004/0151151) disclosed methods for detecting presence of mobile entities as they come within range of a sensor. In Kubler et al, accuracy of the location of the detected MS is not well known, so an estimated area of the whereabouts of the MS is enough to accomplish intended functionality, for example in warehouse installations. A confidence value of this disclosure associated with Kubler et al tends to be low (i.e. not confident), with lower values for long range sensors and higher values for short range sensors. - GPS and the abundance of methods for improving GPS accuracy has led to many successful systems for located MSs with high accuracy. Triangulation provides high accuracies for locating MSs. A confidence value of this disclosure associated with GPS and triangulating location methods tends to be high (i.e. confident). It is preferred that DLMs use the highest possible accuracy method available so that relative ILMs are well located. Not all DLMs need to use the same location methods. An ILM can be located relative DLMs, or other ILMs, that each has different locating methodologies utilized.
- Another advantage herein is to generically locate MSs using varieties and combinations of different technologies. MSs can be automatically located using direct conventional methods for accuracy to base on the locating of other MSs. MSs can be automatically located using indirect methods. Further, it is an advantage to indirectly locate a MS relative heterogeneously located MSs. For example, one DLM may be automatically located using GPS. Another DLM may be automatically located using cell tower triangulation. A third DLM may be automatically located using within range proximity. An ILM can be automatically located at a single location, or different locations over time, relative these three differently located DLMs. The automatically detected location of the ILM may be determined using a form of triangulation relative the three DLMs just discussed, even though each DLM had a different direct location method used. In a preferred embodiment, industry standard IEEE 802.11 Wi-Fi is used to locate (triangulate) an ILM relative a plurality of DLMs (e.g. TDOA in one embodiment). This standard is prolific among more compute trended MSs. Any of the family of 802.11 wave forms such as 802.11a, 802.11b, 802.11g, or any other similar class of wave spectrum can be used, and the same spectrum need not be used between a single ILM and multiple DLMs. 802.x used herein generally refers to the many 802.whatever variations.
- Another advantage herein is to make use of existing marketplace communications hardware, communications software interfaces, and communications methods and location methods where possible to accomplish locating an MS relative one or more other MSs. While 802.x is widespread for Wi-Fi communications, other RF wave forms can be used (e.g. cell phone to cell tower communications). In fact, any wave spectrum for carrying data applies herein.
- Still another advantage is for support of heterogeneous locatable devices. Different people like different types of devices as described above. Complete automation of locating functionality can be provided to a device through local automatic location detection means, or by automatic location detection means remote to the device. Also, an ILM can be located relative a laptop, a cell phone, and a PDA (i.e. different device types).
- Yet another advantage is to prevent the unnecessary storing of large amounts of positioning data for a network of MSs. Keeping positioning data for knowing the whereabouts of all devices can be expensive in terms of storage, infrastructure, performance, backup, and disaster recovery. A preferred embodiment simply uses a distributed approach to determining locations of MSs without the overhead of an all-knowing database maintained somewhere. Positions of MSs can be determined “on the fly” without storing information in a master database. However, there are embodiments for storing a master database, or a subset thereof, to configurable storage destinations, when it makes sense. A subset can be stored at a MS.
- Another advantage includes making use of existing location equipped MSs to expand the network of locatable devices by locating non-equipped MSs relative the location of equipped MSs. MSs themselves help increase dimensions of the locatable network of MSs. The locatable network of MSs is referred to as an LN-Expanse (i.e. Location-Network Expanse). An LN-Expanse dynamically grows and shrinks based on where MSs are located at a particular time. For example, as users travel with their personal MSs, the personal MSs themselves define the LN-Expanse since the personal MSs are used to locate other MSs. An ILM simply needs location awareness relative located MSs (DLMs and/or ILMs).
- Yet another advantage is a MS interchangeably taking on the role of a DLM or ILM as it travels. MSs are chameleons in this regard, in response to location technologies that happen to be available. A MS may be equipped for DLM capability, but may be in a location at some time where the capability is inoperable. In these situations the DLM takes on the role of an ILM. When the MS again enters a location where it can be a DLM, it automatically takes on the role of the DLM. This is very important, in particular for emergency situations. A hiker has a serious accident in the mountains which prevents GPS equipped DLM capability from working. Fortunately, the MS automatically takes on the role of an ILM and is located within the vicinity of neighboring (nearby) MSs. This allows the hiker to communicate his location, operate useful locational application functions and features at his MS, and enable emergency help that can find him.
- It is a further advantage that MS locations be triangulated using any wave forms (e.g. RF, microwaves, infrared, visible light, ultraviolet, X-ray, gamma ray). X-ray and gamma ray applications are special in that such waves are harmful to humans in short periods of times, and such applications should be well warranted to use such wave forms. In some medical embodiments, micro-machines may be deployed within a human body. Such micro-machines can be equipped as MSs. Wave spectrums available at the time of deployment can be used by the MSs for determining exact positions when traveling through a body.
- It is another advantage to use TDOA (Time Difference Of Arrival), AOA (Angle Of Arrival), and Missing Part Triangulation (MPT) when locating a MS. TDOA uses time information to determine locations, for example for distances of sides of a triangle. AOA uses angles of arrival to antennas to geometrically assess where a MS is located by intersecting lines drawn from the antennas with detected angles. MPT is disclosed herein as using combinations of AOA and TDOA to determine a location. Exclusively using all AOA or exclusively using all TDOA is not necessary. MPT can be a direct method for locating MSs.
- Yet another advantage is to locate MSs using Assisted Direct Location Technology (ADLT). ADLT is disclosed herein as using direct (conventional) location capability together with indirect location capability to confidently determine the location of a MS.
- Still another advantage is to permit manual specification for identifying the location of a MS (a DLM). The manual location can then in turn be used to facilitate locating other MSs. A user interface may be used for specification of a DLM location. The user interface can be local, or remote, to the DLM. Various manual specification methods are disclosed. Manual specification is preferably used with less mobile MSs, or existing MSs such as those that use dodgeball.com (trademark of Google). The confidence value depends on how the location is specified, whether or not it was validated, and how it changes when the MS moves after being manually set. Manual specification should have limited scope in an LN-expanse unless inaccuracies can be avoided.
- Another advantage herein is locating a MS using any of the methodologies above, any combinations of the methodologies above, and any combinations of direct and/or indirect location methods described.
- Another advantage is providing synergy between different locating technologies for smooth operations as an MS travels. There are large numbers of methods and combinations of those methods for keeping an MS informed of its whereabouts. Keeping an MS informed of its whereabouts in a timely manner is critical in ensuring LBX operate optimally, and for ensuring nearby MSs without certain locating technologies can in turn be located.
- It is another advantage for locating an MS with multiple location technologies during its travels, and in using the best of breed data from multiple location technologies to infer a MS location confidently. Confidence values are associated with reference location information to ensure an MS using the location information can assess accuracy. A DLM is usually an “affirmifier”. An affirmifier is an MS with its whereabouts information having high confidence of accuracy and can serve as a reference for other MSs. An ILM can also be an affirmifier provided there is high confidence that the ILM location is known. An MS (e.g. ILM) may be a “pacifier”. A pacifier is an MS having location information for its whereabouts with a low confidence for accuracy. While it can serve as a reference to other ILMs, it can only do so by contributing a low confidence of accuracy.
- It is an advantage to synergistically make use of the large number of locating technologies available to prevent one particular type of technology to dominate others while using the best features of each to assess accurate mobile locations of MSs.
- A further advantage is to leverage a data processing system with capability of being located for co-locating another data processing system without any capability of being located. For example, a driver owns an older model automobile, has a useful second data processing system in the automobile without means for being automatically located. The driver also own a cell phone, called a first data processing system, which does have means for being automatically located. The location of the first data processing system can be shared with the second data processing system for locating the second data processing system. Further still, the second data processing system without means for being automatically located is located relative a first set (plurality) of data processing systems which are not at the same location as the second data processing system. So, data processing systems are automatically located relative at least one other data processing which can be automatically located.
- Another advantage is a LBX enabled MS includes a service informant component for keeping a supervisory service informed. This prevents an MS from operating in total isolation, and prevents an MS from operating in isolation with those MSs that are within its vicinity (e.g. within maximum range 1306) at some point in time, but to also participate when the same MSs are great distances from each other. There are LBX which would fit well into an LBS model, but a preferred embodiment chooses to use the LBX model. For example, multiple MS users are seeking to carpool to and from a common destination. The service informant component can perform timely updates to a supervisory service for route comparisons between MSs, even though periods of information are maintained only at the MSs. For example, users find out that they go to the same church with similar schedules, or coworkers find out they live nearby and have identical work schedules. The service informant component can keep a service informed of MS whereabouts to facilitate novel LBX applications.
- It is a further advantage in leveraging the vast amount of MS WiFi deployment underway in the United States. More widespread WiFi availability enhances the ability for well performing peer to peer types of features and functionality disclosed.
- It is a further advantage to prevent unnecessary established connections from interfering with successfully triangulating a MS position. As the MS roams and encounters various wave spectrum signals, that is all that is required for determining the MS location. Broadcast signaling contains the necessary location information for automatically locating the MS.
- Yet another advantage is to leverage Network Time Protocol (NTP) for eliminating bidirectional communications in determining Time of Arrival (TOA) and TDOA (Time Difference Of Arrival) measurements (TDOA as used in the disclosure generally refers to both TOA and TDOA). NTP enables a single unidirectional transmission of data to carry all that is necessary in determining TDOA, provided the sending data processing system and the receiving data processing system are NTP synchronized to an adequate granulation of time.
- A further advantage herein is to leverage existing “usual communications” data transmissions for carrying new data that is ignored by existing MS processing, but observed by new MS processing, for carrying out processing maximizing location functions and features across a large geography. Alternatively, new data can be transmitted between systems for the same functionality.
- Further features and advantages of the disclosure, as well as the structure and operation of various embodiments of the disclosure, are described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference number, except that
reference numbers 1 through 99 may be found on the first 4 drawings ofFIGS. 1A through 1D . None of the drawings, discussions, or materials herein is to be interpreted as limiting to a particular embodiment. The broadest interpretation is intended. Other embodiments accomplishing same functionality are within the spirit and scope of this disclosure. It should be understood that information is presented by example and many embodiments exist without departing from the spirit and scope of this disclosure. - There is no guarantee that there are descriptions in this specification for explaining every novel feature found in the drawings. The present disclosure will be described with reference to the accompanying drawings, wherein:
-
FIG. 1A depicts a preferred embodiment high level example componentization of a MS in accordance with the present disclosure; -
FIG. 1B depicts a Location Based eXchanges (LBX) architectural illustration for discussing the present disclosure; -
FIG. 1C depicts a Location Based Services (LBS) architectural illustration for discussing prior art of the present disclosure; -
FIG. 1D depicts a block diagram of a data processing system useful for implementing a MS, ILM, DLM, centralized server, or any other data processing system disclosed herein; -
FIG. 1E depicts a network illustration for discussing various deployments of whereabouts processing aspects of the present disclosure; -
FIG. 2A depicts an illustration for describing automatic location of a MS through the MS coming into range of a stationary cellular tower; -
FIG. 2B depicts an illustration for describing automatic location of a MS through the MS coming into range of some stationary antenna; -
FIG. 2C depicts an illustration for discussing an example of automatically locating a MS through the MS coming into range of some stationary antenna; -
FIG. 2D depicts a flowchart for describing a preferred embodiment of a service whereabouts update event of an antenna in-range detected MS when MS location awareness is monitored by a stationary antenna or cell tower; -
FIG. 2E depicts a flowchart for describing a preferred embodiment of an MS whereabouts update event of an antenna in-range detected MS when MS location awareness is monitored by the MS; -
FIG. 2F depicts a flowchart for describing a preferred embodiment of a procedure for inserting a Whereabouts Data Record (WDR) to an MS whereabouts data queue; -
FIG. 3A depicts a locating by triangulation illustration for discussing automatic location of a MS; -
FIG. 3B depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a triangulated MS when MS location awareness is monitored by some remote service; -
FIG. 3C depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a triangulated MS when MS location awareness is monitored by the MS; -
FIG. 4A depicts a locating by GPS triangulation illustration for discussing automatic location of a MS; -
FIG. 4B depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a GPS triangulated MS; -
FIG. 5A depicts a locating by stationary antenna triangulation illustration for discussing automatic location of a MS; -
FIG. 5B depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a stationary antenna triangulated MS; -
FIG. 6A depicts a flowchart for describing a preferred embodiment of a service whereabouts update event of a physically or logically connected MS; -
FIG. 6B depicts a flowchart for describing a preferred embodiment of a MS whereabouts update event of a physically or logically connected MS; -
FIGS. 7A , 7B and 7C depict a locating by image sensory illustration for discussing automatic location of a MS; -
FIG. 7D depicts a flowchart for describing a preferred embodiment of graphically locating a MS, for example as illustrated byFIGS. 7A through 7C ; -
FIG. 8A heterogeneously depicts a locating by arbitrary wave spectrum illustration for discussing automatic location of a MS; -
FIG. 8B depicts a flowchart for describing a preferred embodiment of locating a MS through physically contacting the MS; -
FIG. 8C depicts a flowchart for describing a preferred embodiment of locating a MS through a manually entered whereabouts of the MS; -
FIG. 9A depicts a table for illustrating heterogeneously locating a MS; -
FIG. 9B depicts a flowchart for describing a preferred embodiment of heterogeneously locating a MS; -
FIGS. 10A and 10B depict an illustration of a Locatable Network expanse (LN-Expanse) for describing locating of an ILM with all DLMs; -
FIG. 10C depicts an illustration of a Locatable Network expanse (LN-Expanse) for describing locating of an ILM with an ILM and DLM; -
FIGS. 10D , 10E, and 10F depict an illustration of a Locatable Network expanse (LN-Expanse) for describing locating of an ILM with all ILMs; -
FIGS. 10G and 10H depict an illustration for describing the infinite reach of a Locatable Network expanse (LN-Expanse) according to MSs; -
FIG. 10I depicts an illustration of a Locatable Network expanse (LN-Expanse) for describing a supervisory service; -
FIG. 11A depicts a preferred embodiment of a Whereabouts Data Record (WDR) 1100 for discussing operations of the present disclosure; -
FIGS. 11B , 11C and 11D depict an illustration for describing various embodiments for determining the whereabouts of an MS; -
FIG. 11E depicts an illustration for describing various embodiments for automatically determining the whereabouts of an MS; -
FIG. 12 depicts a flowchart for describing an embodiment of MS initialization processing; -
FIGS. 13A through 13C depict an illustration of data processing system wireless data transmissions over some wave spectrum; -
FIG. 14A depicts a flowchart for describing a preferred embodiment of MS LBX configuration processing; -
FIG. 14B depicts a continued portion flowchart ofFIG. 14A for describing a preferred embodiment of MS LBX configuration processing; -
FIG. 15A depicts a flowchart for describing a preferred embodiment of DLM role configuration processing; -
FIG. 15B depicts a flowchart for describing a preferred embodiment of ILM role configuration processing; -
FIG. 15C depicts a flowchart for describing a preferred embodiment of a procedure for Manage List processing; -
FIG. 16 depicts a flowchart for describing a preferred embodiment of NTP use configuration processing; -
FIG. 17 depicts a flowchart for describing a preferred embodiment of WDR maintenance processing; -
FIG. 18 depicts a flowchart for describing a preferred embodiment of a procedure for variable configuration processing; -
FIG. 19 depicts an illustration for describing a preferred embodiment multithreaded architecture of peer interaction processing of a MS in accordance with the present disclosure; -
FIG. 20 depicts a flowchart for describing a preferred embodiment of MS whereabouts broadcast processing; -
FIG. 21 depicts a flowchart for describing a preferred embodiment of MS whereabouts collection processing; -
FIG. 22 depicts a flowchart for describing a preferred embodiment of MS whereabouts supervisor processing; -
FIG. 23 depicts a flowchart for describing a preferred embodiment of MS timing determination processing; -
FIG. 24A depicts an illustration for describing a preferred embodiment of a thread request queue record; -
FIG. 24B depicts an illustration for describing a preferred embodiment of a correlation response queue record; -
FIG. 24C depicts an illustration for describing a preferred embodiment of a WDR request record; -
FIG. 25 depicts a flowchart for describing a preferred embodiment of MS WDR request processing; -
FIG. 26A depicts a flowchart for describing a preferred embodiment of MS whereabouts determination processing; -
FIG. 26B depicts a flowchart for describing a preferred embodiment of processing for determining a highest possible confidence whereabouts; -
FIG. 27 depicts a flowchart for describing a preferred embodiment of queue prune processing; -
FIG. 28 depicts a flowchart for describing a preferred embodiment of MS termination processing; -
FIG. 29A depicts a flowchart for describing a preferred embodiment of a process for starting a specified number of threads in a specified thread pool; and -
FIG. 29B depicts a flowchart for describing a preferred embodiment of a procedure for terminating the process started byFIG. 29A . - With reference now to detail of the drawings, the present disclosure is described. Obvious error handling is omitted from the flowcharts in order to focus on the key aspects of the present disclosure. Obvious error handling includes database I/O errors, field validation errors, errors as the result of database table/data constraints or unique keys, data access errors, communications interface errors or packet collision, hardware failures, checksum validations, bit error detections/corrections, and any other error handling as well known to those skilled in the relevant art in context of this disclosure. A semicolon may be used in flowchart blocks to represent, and separate, multiple blocks of processing within a single physical block. This allows simpler flowcharts with less blocks in the drawings by placing multiple blocks of processing description in a single physical block of the flowchart. Flowchart processing is intended to be interpreted in the broadest sense by example, and not for limiting methods of accomplishing the same functionality. Preferably, field validation in the flowcharts checks for SQL injection attacks, communications protocol sniff and hack attacks, preventing of spoofing MS addresses, syntactical appropriateness, and semantics errors where appropriate. Disclosed user interface processing and/or screenshots are also preferred embodiment examples that can be implemented in other ways without departing from the spirit and scope of this disclosure. Alternative user interfaces (since this disclosure is not to be limiting) will use similar mechanisms, but may use different mechanisms without departing from the spirit and scope of this disclosure.
- Locational terms such as whereabouts, location, position, area, destination, perimeter, radius, geofence, situational location, or any other related two or three dimensional locational term used herein to described position(s) and/or locations and/or whereabouts is to be interpreted in the broadest sense.
Location field 1100 c may include an area (e.g. on earth), a point (e.g. on earth), or a three dimensional bounds in space. In another example, a radius may define a sphere in space, rather than a circle in a plane. In some embodiments, a planet field forms part of the location (e.g. Earth, Mars, etc as part offield 1100 c) for which other location information (e.g. latitude and longitude on Mars also part offield 1100 c) is relative. In some embodiments, elevations (or altitudes) from known locatable point(s), distances from origin(s) in the universe, etc. can denote where exactly is a point of three dimensional space, or three dimensional sphere, area, or solid, is located. That same point can provide a mathematical reference to other points of the solid area/region in space. Descriptions for angles, pitches, rotations, etc from some reference point(s) may be further provided. Three dimensional areas/regions include a conical shape, cubical shape, spherical shape, pyramidal shape, irregular shapes, or any other shape either manipulated with a three dimensional graphic interface, or with mathematical model descriptions. Areas/regions in space can be occupied by a MS, passed through (e.g. by a traveler) by a MS, or referenced through configuration by a MS. In a three dimensional embodiment, nearby/nearness is determined in terms of three dimensional information, for example, a spherical radius around one MS intersecting a spherical radius around another MS. In a two dimensional embodiment, nearby/nearness is determined in terms of two dimensional information, for example, a circular radius around one MS intersecting a circular radius around another MS. Points can be specified as a point in a x-y-z plane, a point in polar coordinates, or the like, perhaps the center of a planet (e.g. Earth) or the Sun, some origin in the Universe, or any other origin for distinctly locating three dimensional location(s), positions, or whereabouts in space. Elevation (e.g. for earth, or some other planet, etc) may be useful to the three dimensional point of origin, and/or for the three dimensional region in space. A region in space may also be specified with connecting x-y-z coordinates together to bound the three dimensional region in space. There are many methods for representing a location (field 1100 c) without departing from the spirit and scope of this disclosure. MSs, for example as carried by users, can travel by airplane through three dimensional areas/regions in space, or travel under the sea through three dimensional regions in space. - Various embodiments of communications between MSs, or an MS and service(s), will share channels (e.g. frequencies) to communicate, depending on when in effect. Sharing a channel will involve carrying recognizable and processable signature to distinguish transmissions for carrying data. Other embodiments of communications between MSs, or an MS and service(s), will use distinct channels to communicate, depending on when in effect. The number of channels that can be concurrently listened on and/or concurrently transmitted on by a data processing system will affect which embodiments are preferred. The number of usable channels will also affect which embodiments are preferred. This disclosure avoids unnecessary detail in different communication channel embodiments so as to not obfuscate novel material. Independent of various channel embodiments within the scope and spirit of the present disclosure, MSs communicate with other MSs in a peer to peer manner, in some aspects like automated walkie-talkies.
- Novel features disclosed herein need not be provided as all or none. Certain features may be isolated in some MS embodiments, or may appear as any subset of features and functionality in other embodiments.
-
FIG. 1A depicts a preferred embodiment high level example componentization of a MS in accordance with the present disclosure. AMS 2 includes processing behavior referred to asLBX Character 4 andOther Character 32.LBX character 4 provides processingbehavior causing MS 2 to take on the character of a Location Based Exchange (LBX) MS according to the present disclosure.Other Character 32 provides processing behavior causing MS to take on character of prior art MSs in context of the type of MS.Other character 32 includes at leastother processing code 34,other processing data 36, andother resources 38, all of which are well known to those skilled in the art for prior art MSs. In some embodiments,LBX character 4 components may, or may not, make use ofother character 32components Other character 32 components may, or may not, make use ofLBX character 4components 6 through 30. -
LBX character 4 preferably includes at least Peer Interaction Processing (PIP)code 6, Peer Interaction Processing (PIP)data 8, selfmanagement processing code 18, selfmanagement processing data 20,WDR queue 22, sendqueue 24, receivequeue 26,service informant code 28, andLBX history 30. Peer interaction processing (PIP)code 6 comprises executable code in software, firmware, or hardware form for carrying out LBX processing logic of the present disclosure when interacting with another MS. Peer interaction processing (PIP)data 8 comprises data maintained in any sort of memory ofMS 2, for example hardware memory, flash memory, hard disk memory, a removable memory device, or any other memory means accessible toMS 2.PIP data 8 contains intelligence data for driving LBX processing logic of the present disclosure when interacting with other MSs. Selfmanagement processing code 18 comprises executable code in software, firmware, or hardware form for carrying out the local user interface LBX processing logic of the present disclosure. Selfmanagement processing data 20 contains intelligence data for driving processing logic of the present disclosure as disclosed for locally maintained LBX features.WDR queue 22 contains Whereabouts Data Records (WDRs) 1100, and is a First-In-First-Out (FIFO) queue when considering housekeeping for pruning the queue to a reasonable trailing history of inserted entries (i.e. remove stale entries).WDR queue 22 is preferably designed with the ability of queue entry retrieval processing similar to Standard Query Language (SQL) querying, wherein one or more entries can be retrieved by querying with a conditional match on any data field(s) ofWDR 1100 and returning lists of entries in order by an ascending or descending key on one or any ascending/descending ordered list of key fields. - All disclosed queues (e.g. 22, 24, 26, 1980 and 1990 (See
FIG. 19 )) are implemented with an appropriate thread-safe means of queue entry peeking (makes copy of sought queue entry without removing), discarding, retrieval, insertion, and queue entry field sorted search processing. Queues are understood to have an associated implicit semaphore to ensure appropriate synchronous access to queue data in a multi-threaded environment to prevent data corruption and misuse. Such queue interfaces are well known in popular operating systems. In MS operating system environments which do not have an implicit semaphore protected queue scheme, queue accesses in the present disclosure flowcharts are to be understood to have a previous request to a queue-assigned semaphore lock prior to queue access, and a following release of the semaphore lock after queue access. Operating systems without semaphore control may use methods to achieve similar thread-safe synchronization functionality. Queue functionality may be accomplished with lists, arrays, databases (e.g. SQL) and other methodologies without departing from the spirit and scope of queue descriptions herein. -
Queue 22 alternate embodiments may maintain a plurality of WDR queues which segregateWDRs 1100 by field(s) values to facilitate timely processing.WDR queue 22 may be at least two (2) separate queues: one for maintaining theMS 2 whereabouts, and one for maintaining whereabouts of other MSs.WDR queue 22 may be asingle instance WDR 1100 in some embodiments which always contains the mostcurrent MS 2 whereabouts for use byMS 2 applications (may use asister queue 22 for maintaining WDRs from remote MSs). At least one entry is to be maintained toWDR queue 22 at all times forMS 2 whereabouts. - Send queue 24 (Transmit (Tx) queue) is used to send communications data, for example as intended for a peer MS within the vicinity (e.g. nearby as indicated by maximum range 1306) of the
MS 2. Receive queue 26 (Receive (Rx) queue) is used to receive communications data, for example from peer MSs within the vicinity (e.g. nearby as indicated by maximum range 1306) of theMS 2.Queues Queues MS 2 in persistent storage, memory, or any other storage means. In some embodiments,queues other character 32 will already have accessible resources for carrying out someLBX character 4 processing. - Queue embodiments may contain fixed length records, varying length records, pointers to fixed length records, or pointers to varying length records. If pointers are used, it is assumed that pointers may be dynamically allocated for record storage on insertions and freed upon record use after discards or retrievals.
- As well known to those skilled in the art, when a thread sends on a
queue 24 in anticipation of a corresponding response, there is correlation data in the data sent which is sought in a response received by a thread atqueue 26 so the sent data is correlated with the received data. In a preferred embodiment, correlation is built using a round-robin generated sequence number placed in data for sending along with a unique MS identifier (MS ID). If data is not already encrypted in communications, the correlation can be encrypted. While the unique MS identifier (MS ID) may help the MS identify which (e.g. wireless) data is destined for it, correlation helps identify which data at the MS caused the response. Upon receipt of data from a responder atqueue 26, correlation processing uses the returned correlation (e.g. field 1100 m) to correlate the sent and received data. In preferred embodiments, the sequence number is incremented each time prior to use to ensure a unique number, otherwise it may be difficult to know which data received is a response to which data was sent, in particular when many data packets are sent within seconds. When the sequence number reaches a maximum value (e.g. 2**32−1), then it is round-robinned to 0 and is incremented from there all over again. This assures proper correlation of data between the MS and responders over time. There are other correlation schemes (e.g. signatures, random number generation, checksum counting, bit patterns, date/time stamp derivatives) to accomplish correlation functionality. If send and receive queues ofOther Character 32 are used, then correlation can be used in a similar manner to correlate a response with a request (i.e. a send with a receipt). - There may be good reason to conceal the MS ID when transmitting it wirelessly. In this embodiment, the MS ID is a dependable and recognizable derivative (e.g. a pseudo MS ID) that can be detected in communications traffic by the MS having the pseudo MS ID, while concealing the true MS ID. This would conceal the true MS ID from would-be hackers sniffing wireless protocol. The derivative can always be reliably the same for simplicity of being recognized by the MS while being difficult to associate to a particular MS. Further still, a more protected MS ID (from would-be hackers that take time to deduce how an MS ID is scrambled) can itself be a dynamically changing correlation anticipated in forthcoming communications traffic, thereby concealing the real MS ID (e.g. phone number or serial number), in particular when anticipating traffic in a response, yet still useful for directing responses back to the originating MS (with the pseudo MS ID (e.g. correlation)). A MS would know which correlation is anticipated in a response by saving it to local storage for use until it becomes used (i.e. correlated in a matching response), or becomes stale. In another embodiment, a correlation response queue (like CR queue 1990) can be deployed to correlate responses with requests that contain different correlations for pseudo MS IDs. In all embodiments, the MS ID (or pseudo MS ID) of the present disclosure should enable targeting communications traffic to the MS.
-
Service informant code 28 comprises executable code in software, firmware, or hardware form for carrying out of informing a supervisory service. The present disclosure does not require a connected web service, but there are features for keeping a service informed with activities of MS LBX.Service informant code 28 can communicate as requested anydata MS 2. -
LBX history 30 contains historical data useful in maintaining atMS 2, and possibly useful for informing a supervisory service throughservice informant code 28.LBX History 30 preferably has an associated thread of processing for keeping it pruned to the satisfaction of a user of MS 2 (e.g. prefers to keep last 15 days of specified history data, and 30 days of another specified history data, etc). With a suitable user interface toMS 2, a user may browse, manage, alter, delete, or add toLBX History 30 as is relevant to processing described herein.Service informant code 28 may be used to cause sending of an outbound email, SMS message, outbound data packet, or any other outbound communication in accordance with LBX of the MS. -
PIP data 8 preferably includes atleast permissions 10,charters 12,statistics 14, and aservice directory 16.Permissions 10 are configured to grant permissions to other MS users for interacting the way the user ofMS 2 desires for them to interact. Therefore,permissions 10 contain permissions granted from theMS 2 user to other MS users. In another embodiment,permissions 10 additionally, or alternatively, contain permissions granted from other MS users to theMS 2 user. Permissions are maintained completely local to theMS 2.Charters 12 provide LBX behavior conditional expressions for how MSs should interact withMS 2.Charters 12 are configured by theMS 2 user for other MS users. In another embodiment,charters 12 additionally, or alternatively, are configured by other MS users for theMS 2 user. Some charters expressions depend onpermissions 10.Statistics 14 are maintained atMS 2 for reflecting peer (MS) to peer (MS) interactions of interest that occurred atMS 2. In another embodiment,statistics 14 additionally, or alternatively, reflect peer (MS) to peer (MS) interactions that occurred at other MSs, preferably depending onpermissions 10.Service informant code 28 may, or may not, inform a service ofstatistics 14 maintained.Service directory 16 includes routing entries for howMS 2 will find a sought service, or how another MS can find a sought service throughMS 2. - In some embodiments, any code (e.g. 6, 18, 28, 34, 38) can access, manage, use, alter, or discard any data (e.g. 8, 20, 22, 24, 26, 30, 36, 38) of any other component in
MS 2. Other embodiments may choose to keep processing ofLBX character 4 andother character 32 disjoint from each other. Rectangular component boundaries are logical component representations and do not have to delineate who has access to what. MS (also MSs) references discussed herein in context for the new and useful features and functionality disclosed is understood to be an MS 2 (MSs 2). -
FIG. 1B depicts a Location Based eXchanges (LBX) architectural illustration for discussing the present disclosure. LBX MSs are peers to each other for locational features and functionality. AnMS 2 communicates with other MSs without requiring a service for interaction. For example,FIG. 1B depicts awireless network 40 of five (5) MSs. Each is able to directly communicate with others that are in the vicinity (e.g. nearby as indicated by maximum range 1306). In a preferred embodiment, communications are limited reliability wireless broadcast datagrams having recognizable data packet identifiers. In another embodiment, wireless communications are reliable transport protocols carried out by the MSs, such as TCP/IP. In other embodiments, usual communications data associated withother character 32 include new data (e.g. Communications Key 1304) in transmissions for being recognized by MSs within the vicinity. For example, as an MS conventionally communicates, LBX data is added to the protocol so that other MSs in the vicinity can detect, access, and use the data. The advantage to this is that as MSs use wireless communications to carry out conventional behavior, new LBX behavior is provided by simply incorporating additional information (e.g. Communications Key 1304) to existing communications. - Regardless of the embodiment, an
MS 2 can communicate with any of its peers in the vicinity using methods described below. Regardless of the embodiment, a communication path 42 between any two MSs is understood to be potentially bidirectional, but certainly at least unidirectional. The bidirectional path 42 may use one communications method for one direction and a completely different communications method for the other, but ultimately each can communicate to each other. When considering that a path 42 comprises two unidirectional communications paths, there are N*(N−1) unidirectional paths for N MSs in anetwork 40. For example, 10 MSs results in 90 (i.e. 1*9) one way paths of communications between all 10 MSs for enabling them to talk to each other. Sharing of the same signaling channels is preferred to minimize the number of MS threads listening on distinct channels. Flowcharts are understood to process at incredibly high processing speeds, in particular for timely communications processing. -
FIG. 1C depicts a Location Based Services (LBS) architectural illustration for discussing prior art of the present disclosure. In order for a MS to interact for LBS with another MS, there isservice architecture 44 for accomplishing the interaction. For example, to detect thatMS 1 is nearby MS N, the service is indispensably involved in maintaining data and carrying out processing. For example, to detect thatMS 1 is arriving to, or departing from, a geofenced perimeter area configured by MS N, the service was indispensably involved in maintaining data and carrying out processing. For example, for MS N to locateMS 1 on a live map, the service was indispensably involved in maintaining data and carrying out processing. In another example, to grant and revoke permissions fromMS 1 to MS N, the service was indispensably involved in maintaining data and carrying out processing. While it is advantageous to require a singlebidirectional path 46 for each MS (i.e. two unidirectional communications paths; (2*N) unidirectional paths for N MSs), there are severe requirements for service(s) when there are lots of MSs (i.e. when N is large). Wireless MSs have advanced beyond cell phones, and are capable of housing significant parallel processing, processing speed, increased wireless transmission speeds and distances, increased memory, and richer features. -
FIG. 1D depicts a block diagram of a data processing system useful for implementing a MS, ILM, DLM, centralized server, or any other data processing system described herein. AnMS 2 is adata processing system 50.Data processing system 50 includes at least one processor 52 (e.g. Central Processing Unit (CPU)) coupled to abus 54.Bus 54 may include a switch, or may in fact be aswitch 54 to provide dedicated connectivity between components ofdata processing system 50. Bus (and/or switch) 54 is a preferred embodiment coupling interface betweendata processing system 50 components. Thedata processing system 50 also includesmain memory 56, for example, random access memory (RAM).Memory 56 may include multiple memory cards, types, interfaces, and/or technologies. Thedata processing system 50 may includesecondary storage devices 58 such aspersistent storage 60, and/orremovable storage device 62, for example as a compact disk, floppy diskette, USB flash, or the like, also connected to bus (or switch) 54. In some embodiments, persistent storage devices could be remote to thedata processing system 50 and coupled through an appropriate communications interface.Persistent storage 60 may include flash memory, disk drive memory, magnetic, charged, or bubble storage, and/or multiple interfaces and/or technologies, perhaps in software interface form of variables, a database, shared memory, etc. - The
data processing system 50 may also include adisplay device interface 64 for driving a connected display device (not shown). Thedata processing system 50 may further include one or more input peripheral interface(s) 66 to input devices such as a keyboard, keypad, Personal Digital Assistant (PDA) writing implements, touch interfaces, mouse, voice interface, or the like. User input (“user input”, “user events” and “user actions” used interchangeably) to the data processing system are inputs accepted by the input peripheral interface(s) 66. Thedata processing system 50 may still further include one or more output peripheral interface(s) 68 to output devices such as a printer, facsimile device, or the like. Output peripherals may also be available via an appropriate interface. -
Data processing system 50 will include a communications interface(s) 70 for communicating to anotherdata processing system 72 via analog signal waves, digital signal waves, infrared proximity, copper wire, optical fiber, or other wave spectrums described herein. A MS may have multiple communications interfaces 70 (e.g. cellular connectivity, 802.x, etc). Otherdata processing system 72 may be an MS. Otherdata processing system 72 may be a service. Otherdata processing system 72 is a service data processing system whenMS 50 communicates to otherdata processing system 72 by way ofservice informant code 28. In any case, the MS and other data processing system are said to be interoperating when communicating. - Data processing system programs (also called control logic) may be completely inherent in the processor(s) 52 being a customized semiconductor, or may be stored in
main memory 56 for execution by processor(s) 52 as the result of a read-only memory (ROM) load (not shown), or may be loaded from a secondary storage device intomain memory 56 for execution by processor(s) 52. Such programs, when executed, enable thedata processing system 50 to perform features of the present disclosure as discussed herein. Accordingly, such data processing system programs represent controllers of the data processing system. - In some embodiments, the disclosure is directed to a control logic program product comprising at least one
processor 52 having control logic (software, firmware, hardware microcode) stored therein. The control logic, when executed by processor(s) 52, causes the processor(s) 52 to provide functions of the disclosure as described herein. In another embodiment, this disclosure is implemented primarily in hardware, for example, using a prefabricated component state machine (or multiple state machines) in a semiconductor element such as aprocessor 52. - Those skilled in the art will appreciate various modifications to the
data processing system 50 without departing from the spirit and scope of this disclosure. A data processing system, and more particularly a MS, preferably has capability for many threads of simultaneous processing which provide control logic and/or processing. These threads can be embodied as time sliced threads of processing on a single hardware processor, multiple processors, multi-core processors, Digital Signal Processors (DSPs), or the like, or combinations thereof. Such multi-threaded processing can concurrently serve large numbers of concurrent MS tasks. Concurrent processing may be provided with distinct hardware processing and/or as appropriate software driven time-sliced thread processing. Those skilled in the art recognize that having multiple threads of execution on an MS is accomplished in many different ways without departing from the spirit and scope of this disclosure. This disclosure strives to deploy software to existing MS hardware configurations, but the disclosed software can be deployed as burned-in microcode to new hardware of MSs. - Data processing aspects of drawings/flowcharts are preferably multi-threaded so that many MSs and applicable data processing systems are interfaced with in a timely and optimal manner.
Data processing system 50 may also include its own clock mechanism (not shown), if not an interface to an atomic clock or other clock mechanism, to ensure an appropriately accurate measurement of time in order to appropriately carry out processing described below. In some embodiments, Network Time Protocol (NTP) is used to keep a consistent universal time for MSs and other data processing systems in communications with MSs. This is most advantageous to prevent unnecessary round-tripping of data between data processing systems to determine timing (e.g. Time Difference of Arrival (TDOA)) measurements. A NTP synchronized date/time stamp maintained in communications is compared by a receiving data processing system for comparing with its own NTP date/time stamp to measure TOA (time of arrival (i.e. time taken to arrive)). Of course, in the absence of NTP used by the sender and receiver, TOA is also calculated in a bidirectional transmission using correlation. In this disclosure, TOA measurements from one location technology are used for triangulating with TOA measurements from another location technology, not just for determining “how close”. Therefore, TDOA terminology is generally used herein to refer to the most basic TOA measurement of a wave spectrum signal being the difference between when it was sent and when it was received. TDOA is also used to describe using the difference of such measurements to locate (triangulate). NTP use among participating systems has the advantage of a single unidirectional broadcast data packet containing all a receiving system requires to measure TDOA, by knowing when the data was sent (date/time stamp in packet) and when the data was received (signal detected and processed by receiving system). A NTP clock source (e.g. atomic clock) used in a network is to be reasonably granular to carry out measurements, and ensures participating MSs are updated timely according to anticipated time drifts of their own clocks. There are many well known methods for accomplishing NTP, some which require dedicated thread(s) for NTP processing, and some which use certain data transmitted to and from a source to keep time in synch. - Those skilled in the art recognize that NTP accuracy depends on participating MS clocks and processing timing, as well as time server source(s). Radio wave connected NTP time server(s) is typically accurate to as granular as 1 millisecond. Global Positioning System (GPS) time servers provide accuracy as granular as 50 microseconds. GPS timing receivers provide accuracy to around 100 nanoseconds, but this may be reduced by timing latencies in time server operating systems. With advancements in hardware, microcode, and software, obvious improvements are being made to NTP. In NTP use embodiments of this disclosure, an appropriate synchronization of time is used for functional interoperability between MSs and other data processing systems using NTP. NTP is not required in this disclosure, but it is an advantage when in use.
-
FIG. 1E depicts a network illustration for discussing various deployments of whereabouts processing aspects of the present disclosure. In some embodiments, a cellular network cluster 102 and cellular network cluster 104 are parts of a larger cellular network. Cellular network cluster 102 contains a controller 106 and a plurality of base stations, shown generally as base stations 108. Each base station covers a single cell of the cellular network cluster, and each base station 108 communicates through a wireless connection with the controller 106 for call processing, as is well known in the art. Wireless devices communicate via the nearest base station (i.e. the cell the device currently resides in), forexample base station 108 b. Roaming functionality is provided when a wireless device roams from one cell to another so that a session is properly maintained with proper signal strength. Controller 106 acts like a telephony switch when a wireless device roams across cells, and it communicates with controller 110 via a wireless connection so that a wireless device can also roam to other clusters over a larger geographical area. Controller 110 may be connected to a controller 112 in a cellular cluster through a physical connection, for example, copper wire, optical fiber, or the like. This enables cellular clusters to be great distances from each other. Controller 112 may in fact be connected with a physical connection to its base stations, shown generally as base stations 114. Base stations may communicate directly with the controller 112, for example, base station 114 e. Base stations may communicate indirectly to the controller 112, for example base station 114 a by way of base station 114 d. It is well known in the art that many options exist for enabling interoperating communications between controllers and base stations for the purpose of managing a cellular network. A cellular network cluster 116 may be located in a different country. Base controller 118 may communicate with controller 110 through a Public Service Telephone Network (PSTN) by way of a telephony switch 120, PSTN 122, and telephony switch 124, respectively. Telephony switch 120 and telephony switch 124 may be private or public. In one cellular network embodiment of the present disclosure, the services execute at controllers, for example controller 110. In some embodiments, the MS includes processing that executes at a wireless device, for example mobile laptop computer 126, wireless telephone 128, a personal digital assistant (PDA) 130, an iPhone 170, or the like. As the MS moves about, positional attributes are monitored for determining location. The MS may be handheld, or installed in a moving vehicle. Locating a wireless device using wireless techniques such as Time Difference of Arrival (TDOA) and Angle Of Arrival (AOA) are well known in the art. The service may also execute on a server computer accessible to controllers, for example server computer 132, provided an appropriate timely connection exists between cellular network controller(s) and the server computer 132. Wireless devices (i.e. MSs) are preferably known by a unique identifier, for example a phone number, caller id, device identifier, or like appropriate unique handle. - In another embodiment of the present disclosure, GPS satellites such as
satellite 134,satellite 136, andsatellite 138 provide information, as is well known in the art, to GPS devices on earth for triangulation locating of the GPS device. In this embodiment, a MS has integrated GPS functionality so that the MS monitors its positions. The MS is preferably known by a unique identifier, for example a phone number, caller id, device identifier, or like appropriate unique handle. - In yet another embodiment of the present disclosure, a physically connected device, for example, telephone 140, computer 142, PDA 144, telephone 146, and fax machine 148, may be newly physically connected to a network. Each is a MS, although the mobility is limited. Physical connections include copper wire, optical fiber, USB, or any other physical connection, by any communications protocol thereon. Devices are preferably known by a unique identifier, for example a phone number, caller id, device identifier, physical or logical network address, or like appropriate unique handle. The MS is detected for being newly located when physically connected. A service can be communicated to upon detecting connectivity. The service may execute at an Automatic Response Unit (ARU) 150, a telephony switch, for example telephony switch 120, a web server 152 (for example, connected through a gateway 154), or a like data processing system that communicates with the MS in any of a variety of ways as well known to those skilled the art. MS detection may be a result of the MS initiating a communication with the service directly or indirectly. Thus, a user may connect his laptop to a hotel network, initiate a communication with the service, and the service determines that the user is in a different location than the previous communication. A local area network (LAN) 156 may contain a variety of connected devices, each an MS that later becomes connected to a local area network 158 at a different location, such as a PDA 160, a server computer 162, a printer 164, an internet protocol telephone 166, a computer 168, or the like. Hard copy presentation could be made to printer 164 and fax 148.
- Current technology enables devices to communicate with each other, and other systems, through a variety of heterogeneous system and communication methods. Current technology allows executable processing to run on diverse devices and systems. Current technology allows communications between the devices and/or systems over a plethora of methodologies at close or long distance. Many technologies also exist for automatic locating of devices. It is well known how to have an interoperating communications system that comprises a plurality of individual systems communicating with each other with one or more protocols. As is further known in the art of developing software, executable processing of the present disclosure may be developed to run on a particular target data processing system in a particular manner, or customized at install time to execute on a particular data processing system in a particular manner.
-
FIG. 2A depicts an illustration for describing automatic location of a MS, for example aDLM 200, through the MS coming into range of a stationary cellular tower. ADLM 200, or any of a variety of MSs, travels within range of a cell tower, forexample cell tower 108 b. The known cell tower location is used to automatically detect the location of theDLM 200. In fact, any DLM that travels within the cell served bycell tower 108 b is identified as the location ofcell tower 108 b. The confidence of a location of aDLM 200 is low when the cell coverage ofcell tower 108 b is large. In contrast, the confidence of a location of aDLM 200 is higher when the cell coverage ofcell tower 108 b is smaller. However, depending on the applications locating DLMs using this method, the locating can be quite acceptable. Location confidence is improved with a TDOA measurement for the elapsed time of communication betweenDLM 200 and cell tower to determine how close the MS is to the cell tower.Cell tower 108 b can process all locating by itself, or with interoperability to other services as connected tocell tower 108 b inFIG. 1E .Cell tower 108 b can communicate the location ofDLM 200 to a service, to theDLM 200, to other MSs within its coverage area, any combination thereof, or to any connected data processing system, or MS, ofFIG. 1E . -
FIG. 2B depicts an illustration for describing automatic location of a MS, for example aDLM 200, through the MS coming into range of some stationary antenna.DLM 200, or any of a variety of MSs, travels within range of astationary antenna 202 that may be mounted to astationary object 204. The known antenna location is used to automatically detect the location of theDLM 200. In fact, any DLM that travels within the coverage area served byantenna 202 is identified as the location ofantenna 202. The confidence of a location of aDLM 200 is low when the antenna coverage area ofantenna 202 is large. In contrast, the confidence of a location of aDLM 200 is higher when the antenna coverage area ofantenna 202 is smaller. However, depending on the applications locating DLMs using this method, the locating can be quite acceptable. Location confidence is improved with a TDOA measurement for the elapsed time of communication betweenDLM 200 and a particular antenna to determine how close the MS is to the antenna.Antenna 202 can process all locating by itself (with connected data processing system (not shown) as well known to those skilled in the art), or with interoperability to other services as connected toantenna 202, for example with connectivity described inFIG. 1E .Antenna 202 can be used to communicate the location ofDLM 200 to a service, to theDLM 200, to other MSs within its coverage area, any combination thereof, or to any connected data processing system, or MS, ofFIG. 1E . -
FIG. 2C depicts an illustration for discussing an example of automatically locating a MS, for example aDLM 200, through the MS coming into range of some stationary antenna.DLM 200, or any of a variety of MSs, travels within range of astationary antenna 212 that may be mounted to a stationary object, such asbuilding 210. The known antenna location is used to automatically detect the location of theDLM 200. In fact, any DLM that travels within the coverage area served byantenna 212 is identified as the location ofantenna 212. The confidence of a location of aDLM 200 is low when the antenna coverage area ofantenna 212 is large. In contrast, the confidence of a location of aDLM 200 is higher when the antenna coverage area ofantenna 212 is smaller. However, depending on the applications locating DLMs using this method, the locating can be quite acceptable. Location confidence is improved with a TDOA measurement as described above.Antenna 212 can process all locating by itself (with connected data processing system (not shown) as well known to those skilled in the art), or with interoperability to other services as connected toantenna 212, for example with connectivity described inFIG. 1E .Antenna 212 can be used to communicate the location ofDLM 200 to a service, to theDLM 200, to other MSs within its coverage area, any combination thereof, or to any connected data processing system, or MS, ofFIG. 1E . - Once
DLM 200 is within thebuilding 210, a strategically placedantenna 216 with a desired detection range within the building is used to detect theDLM 200 coming into its proximity.Wall breakout 214 is used to see theantenna 216 through thebuilding 210. The knownantenna 216 location is used to automatically detect the location of theDLM 200. In fact, any DLM that travels within the coverage area served byantenna 216 is identified as the location ofantenna 216. The confidence of a location of aDLM 200 is low when the antenna coverage area ofantenna 216 is large. In contrast, the confidence of a location of aDLM 200 is higher when the antenna coverage area ofantenna 216 is smaller. Travels ofDLM 200 can be limited by objects, pathways, or other limiting circumstances of traffic, to provide a higher confidence of location ofDLM 200 when located byantenna 216, or when located by any locating antenna described herein which detects MSs coming within range of its location. Location confidence is improved with a TDOA measurement as described above.Antenna 216 can process all locating by itself (with connected data processing system (not shown) as well known to those skilled in the art), or with interoperability to other services as connected toantenna 216, for example with connectivity described inFIG. 1E .Antenna 216 can be used to communicate the location ofDLM 200 to a service, to theDLM 200, to other MSs within its coverage area, any combination thereof, or to any connected data processing system, or MS, ofFIG. 1E . Other in-range detection antennas of aFIG. 2C embodiment may be strategically placed to facilitate warehouse operations such as in Kubler et al. -
FIG. 2D depicts a flowchart for describing a preferred embodiment of a service whereabouts update event of an antenna in-range detected MS, for example aDLM 200, when MS location awareness is monitored by a stationary antenna, or cell tower (i.e. the service thereof).FIGS. 2A through 2C location detection processing are well known in the art.FIG. 2D describes relevant processing for informing MSs of their own whereabouts. Processing begins atblock 230 when a MS signal deserving a response has been received and continues to block 232 where the antenna or cell tower service has authenticated the MS signal. A MS signal can be received for processing byblocks 230 through 242 as the result of a continuous, or pulsed, broadcast or beaconing by the MS (FIG. 13A ), perhaps as part of usual communication protocol in progress for the MS (FIG. 13A usual data 1302 with embedded Communications Key (CK) 1304), or an MS response to continuous, or pulsed, broadcast or beaconing via the service connected antenna (FIG. 13C ). MS and/or service transmission can be appropriately correlated for a response (as described above) which additionally facilitates embodiments using TDOA measurements (time of communications between the MS and antenna, or cell tower) to determine at least how close is the MS in range (or use in conjunction with other data to triangulate the MS location). The MS is preferably authenticated by a unique MS identifier such as a phone number, address, name, serial number, or any other unique handle to the MS. In this, and any other embodiments disclosed, an MS may be authenticated using a group identifier handle indicating membership to a supported/known group deserving further processing. Authentication will preferably consult a database for authenticating that the MS is known.Block 232 continues to block 234 where the signal received is immediately responded back to the MS, via the antenna, containing at least correlation along with whereabouts information for a Whereabouts Data Record (WDR) 1100 associated with the antenna (or cell tower). Thereafter, the MS receives the correlated response containing new data atblock 236 and completes a local whereabouts data record 1100 (i.e. WDR 1100) using data received along with other data determined by the MS. - In another embodiment, blocks 232 through 234 are not required. A service connected antenna (or cell tower) periodically broadcasts its whereabouts (WDR info (e.g.
FIG. 13C )) and MSs in the vicinity use that directly atblock 236. The MS can choose to use only the confidence and location provided, or may determine a TDOA measurement for determining how close it is. If the date/time stamp field 1100 b indicates NTP is in use by the service, and the MS is also using NTP, then a TDOA measurement can be determined using the one unidirectional broadcast via the antenna by using the date/time stamp field 1100 b received with when the WDR information was received by the MS (subtract time difference and use known wave spectrum for distance). If either the service or MS is not NTP enabled, then a bidirectional correlated data flow between the service and MS is used to assess a TDOA measurement in terms of time of the MS. One embodiment provides the TDOA measurement from the service to the MS. Another embodiment calculates the TDOA measurement at the MS. - Network Time protocol (NTP) can ensure MSs have the same atomic clock time as the data processing systems driving antennas (or cell towers) they will encounter. Then, date/time stamps can be used in a single direction (unidirectional) broadcast packet to determine how long it took to arrive to/from the MS. In an NTP embodiment, the MS (FIG. 13A) and/or the antenna (
FIG. 13C ) sends a date/time stamp in the pulse, beacon, or protocol. Upon receipt, the antenna (or cell tower) service data processing system communicates how long the packet took from an MS to the antenna (or cell tower) by comparing the date/time stamp in the packet and a date/time stamp of when it was received. The service may also set the confidence value, before sending WDR information to the MS. Similarly, an MS can compare a date/time stamp in the unidirectional broadcast packet sent from a locating service (FIG. 13C ) with when received by the MS. So, NTP facilitates TDOA measurements in a single broadcast communication between systems through incorporation tousual communications data 1302 with a date/time stamp in Communications Key (CK) 1304, or alternatively innew data 1302. Similarly, NTP facilitates TDOA measurement in a single broadcast communication between systems through incorporation tousual communications data 1312 with a date/time stamp in Communications Key (CK) 1314, or alternatively innew data 1312. - The following template is used in this disclosure to highlight field settings. See
FIG. 11A descriptions. Fields are set to the following upon exit from block 236: -
MS ID field 1100 a is preferably set with: Unique MS identifier of theMS invoking block 240. This field is used to uniquely distinguish this MS WDRs onqueue 22 from other originated WDRs.
DATE/TIME STAMP field 1100 b is preferably set with: Date/time stamp for WDR completion atblock 236 to the finest granulation of time achievable by the MS. The NTP use indicator is set appropriately.
LOCATION field 1100 c is preferably set with: Location of stationary antenna (or cell tower) as communicated by the service to the MS.
CONFIDENCE field 1100 d is preferably set with: The same value (e.g. 76) for any range within the antenna (or cell tower), or may be adjusted using the TDOA measurement (e.g. amount of time detected by the MS for the response at block 234). The longer time it takes between the MS sending a signal detected atblock 232 and the response with data back received by the MS (block 234), the less confidence there is for being located because the MS must be a larger distance from the antenna or cell tower. The less time it takes between the MS sending a signal detected atblock 232 and the response with data back, the more confidence there is for being located because the MS must be a closer distance to the antenna or cell tower. Confidence values are standardized for all location technologies. In some embodiments ofFIG. 2D processing, a confidence value can be set for 1 through 100 (1 being lowest confidence and 100 being highest confidence) wherein a unit of measurement between the MS and antenna (or cell tower) is used directly for the confidence value. For example, 20 meters is used as the unit of measurement. For each unit of 20 meters distance determined by the TDOA measurement, assign a value of 1, up to a worst case of 100 (i.e. 2000 meters). Round the 20 meter unit of distance such that 0 meters to <25 meters is 20 meters (i.e. 1 unit of measurement), 26 meters to <45 meters is 40 meters (i.e. 2 units of measurement), and so on. Once the number of units is determined, subtract that number from 101 for the confidence value (i.e. 1 unit=confidence value 100, 20 units=confidence value 81; 100 units or greater=confidence value of 1). Yet another embodiment will use a standard confidence value for this “coming in range” technology such as 76 and then further increase or decrease the confidence using the TDOA measurement. Many embodiments exist for quantifying a higher versus lower confidence. In any case, a confidence value (e.g. 76) is determined by the MS, service, or both (e.g. MS uses TDOA measurement to modify confidence sent by service).
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Server Antenna Range” for an antenna detecting the MS, and is set to “Server Cell Range” for a cell tower detecting the MS. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: The period of time for communications between the antenna and the MS (a TDOA measurement), if known; a communications signal strength, if available; wave spectrum used (e.g. from MS receive processing), if available;particular communications interface 70, if available. The TDOA measurement may be converted to a distance using wave spectrum information. The values populated here should have already been factored into the confidence value atblock 236.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Parameters uniquely identifying a/the service (e.g. antenna (or cell tower)) and how to best communicate with it again, if available. May not be set, regardless if received from the service.
SPEED field 1100 h is preferably set with: Data received by MS atblock 234, if available.
HEADING field 1100 i is preferably set with: Data received by MS atblock 234, if available.
ELEVATION field 1100 j is preferably set with: data received by MS atblock 234, if available. Elevation field 1100 j is preferably associated with the antenna (or cell tower) by the elevation/altitude of the antenna (or cell tower).
APPLICATION FIELDS field 1100 k is preferably set with: Data received atblock 234 by the MS, or set by data available to the MS, or set by both the locating service for the antenna (or cell tower) and the MS itself. Application fields include, and are not limited to, MS navigation APIs in use, social web site identifying information, application information for applications used, accessed, or in use by the MS, or any other information complementing whereabouts of the MS.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). - A service connected to the antenna (or cell tower) preferably uses historical information and artificial intelligence interrogation of MS travels to determine
fields 1100 h and 1100 i.Block 236 continues to block 238 where parameters are prepared for passing toFIG. 2F processing invoked atblock 240. Parameters are set for: WDRREF=a reference or pointer to the WDR; DELETEQ=FIG. 2D location queue discard processing; and SUPER=FIG. 2D supervisory notification processing. Thereafter, block 240 invokesFIG. 2F processing andFIG. 2D processing terminates atblock 242.FIG. 2F processing will insert to queue 22 so this MS knows at least its own whereabouts whenever possible. A single data instance embodiment ofWDR queue 22 will causeFIG. 2F to update the single record of WDR information for being current upon exit from block 240 (this is true for all flowchart blocks invokingFIG. 2F processing). - With reference now to
FIG. 2F , depicted is a flowchart for describing a preferred embodiment of a procedure for inserting a Whereabouts Data Record (WDR) 1100 toMS WDR queue 22. Appropriate semaphores are used for variables which can be accessed simultaneously by another thread other than the caller. With reference now toFIG. 2F , procedure processing starts at block 270 and continues to block 272 where parameters passed from the invoking block of processing, forexample block 240, are determined. The variable WDRREF is set by the caller to a reference or pointer to the WDR so subsequent blocks ofFIG. 2F can access the WDR. The variable DELETEQ is set by the caller so thatblock 292 knows how to discard obsolete location queue entries. The DELETEQ variable can be a multi-field record (or reference thereof) for how to prune. The variable SUPER is set by the caller so that block 294 knows under what condition(s), and which data, to contact a supervisory service. The SUPER variable can be a multi-field record (or reference thereof) for instruction. -
Block 272 continues to block 274 where the DLMV (seeFIG. 12 and later discussions for DLMV (DLM role(s) List Variable)), or ILMV (seeFIG. 12 and later discussions for ILMV (ILM role(s) List Variable)), is checked for an enabled role matching the WDR for insertion (e.g. DLM: location technology field 1100 e (technology and originator indicator) when MS ID=this MS; ILM: DLM or ILM indicator when MS ID not this MS). If no corresponding DLMV/ILMV role is enabled for the WDR to insert, then processing continues to block 294 (the WDR is not inserted to queue 22). If the ILMV/DLMV role for the WDR is enabled, then processing continues to block 276 where the confidence of theWDR 1100 is validated prior to insertion. An alternate embodiment toFIG. 2F will not have block 274 (i.e. block 272 continues directly to block 276) since appropriate DLM and/or ILM processing may be terminated anyway when DLM/mM role(s) are disabled (see FIG. 14A/B). - If
block 276 determines the data to be inserted is not of acceptable confidence (e.g. field 1100 d<confidence floor value (see FIG. 14A/B)), then processing continues to block 294 described below. Ifblock 276 determines the data to be inserted is of acceptable confidence (e.g. field 1100 d>70), then processing continues to block 278 for checking the intent of the WDR insertion. - If
block 278 determines the WDR for insert is a WDR describing whereabouts for this MS (i.e. MS ID matching MS ofFIG. 2F processing (DLM:FIGS. 2A through 9B , or ILM: FIG. 26A/B)), then processing continues to block 280. Ifblock 278 determines the WDR for insert is from a remote ILM or DLM (i.e. MS ID does not match MS ofFIG. 2F processing), then processing continues to block 290.Block 280 peeks theWDR queue 22 for the most recent highest confidence entry for this MS whereabouts by searchingqueue 22 for: theMS ID field 1100 a matching the MS ID ofFIG. 2F processing, and a confidence field 1100 d greater than or equal to the confidence floor value, and a most recent date/time stamp field 1100 b. Thereafter, ifblock 282 determines one was found, then processing continues to block 284, otherwise processing continues to block 286 where a Last Whereabouts date/Time stamp (LWT) variable is set to field 1100 b of the WDR for insert (e.g. first MS whereabouts WDR), and processing continues to block 288. - If
block 284 determines the WDR for insertion has significantly moved (i.e. using a movement tolerance configuration (e.g. 3 meters) withfields 1100 c of the WDR for insert and the WDR peeked at block 280), then block 286 sets the LWT (Last Whereabouts date/Time stamp) variable (with appropriate semaphore) tofield 1100 b of the WDR for insert, and processing continues to block 288, otherwise processing continues directly to block 288 (thereby keeping the LWT as its last setting). The LWT is to hold the most recent date/time stamp of when the MS significantly moved as defined by a movement tolerance. The movement tolerance can be system defined or configured, or user configured inFIG. 14 by an option for configuration detected atblock 1408, and then using the Configure Value procedure ofFIG. 18 (like confidence floor value configuration). - Block 288 accesses the DLMV and updates it with a new DLM role if there is not one present for it. This ensures a correct list of DLMV roles are available for configuration by
FIG. 14 . Preferably, by default an unanticipated DLMV role is enabled (helps inform the user of its availability). Likewise in another embodiment, ILMV roles can be similarly updated, in particular if a more granulated list embodiment is maintained to the ILMV, or if unanticipated results help to identify another configurable role. By default, block 274 should allow unanticipated roles to continue with WDR insertion processing, and then block 288 can add the role, enable it, and a user can decide what to do with it in configuration (FIG. 14A/B). - Thereafter, the
WDR 1100 is inserted to theWDR queue 22 atblock 290, block 292 discards any obsolete records from the queue as directed by the caller (invoker), and processing continues to block 294. TheWDR queue 22 preferably contains a list of historically MS maintained Whereabouts Data Records (WDRs) as the MS travels. When the MS needs its own location, for example from an application access, or to help locate an ILM, the queue is accessed for returning the WDR with the highest confidence value (field 1100 d) in the most recent time (field 1100 b) for the MS (field 1100 a).Block 292 preferably discards by usingfields 1100 b and 1100 d relative to other WDRs. The queue should not be allowed to get too large. This will affect memory (or storage) utilization at the MS as well as timeliness in accessing a sought queue entry. Block 292 also preferably discards WDRs fromqueue 22 by moving selected WDRs toLBX History 30. - As described above, queue interfaces assume an implicit semaphore for properly accessing
queue 22. There may be ILMs requesting to be located, or local applications of the MS may request to access the MS whereabouts. Executable thread(s) at the MS can accesses the queue in a thread-safe manner for responding to those requests. The MS may also have multiple threads of processing for managing whereabouts information from DLMs, ILMs, or stationary location services. The more concurrently executable threads available to the MS, the better the MS is able to locate itself and respond to others (e.g. MSs). There can be many location systems and methods used to keeping a MS informed of its own whereabouts during travel. While the preferred embodiment is to maximize thread availability, the obvious minimum requirement is to have at least 1 executable thread available to the MS. As described above, in operating system environments without proper queue interfaces, queue access blocks are first preceded by an explicit request for a semaphore lock to access queue 22 (waits until obtained), and then followed by a block for releasing the semaphore lock to another thread for use. Also, in the present disclosure it is assumed in blocks which access data accessible to more than 1 concurrent thread (e.g. shared memory access to DLMV or ILMV at block 274) that an appropriate semaphore (created at block 1220) protect synchronous access. - If block 294 determines information (e.g. whereabouts) should be communicated by
service informant code 28 to a supervisory service, for example aservice 1050, then block 296 communicates specified data to the service and processing terminates atblock 298 by returning to the invoker (caller). If block 294 determines a supervisory service is not to be informed, then processing terminates with an appropriate return to the caller atblock 298.Service informant code 28, atblock 296, can send information as data that is reliably acknowledged on receipt, or as a datagram which most likely (but unreliably) is received. - Depending on the SUPER variable, block 294 may opt to communicate every time a WDR is placed to the queue, or when a reasonable amount of time has passed since last communicating to the supervisory service, or when a WDR confidence reaches a certain sought value, or when any WDR field or fields contain certain sought information, or when a reasonably large number of entries exist in
WDR queue 22, or for any processing condition encountered by blocks 270 through 298, or for any processing condition encountered by caller processing up to the invocation ofFIG. 2F processing. Different embodiments will send asingle WDR 1100 atblock 296, a plurality ofWDRs 1100, or any other data. Various SUPER parameter(s) embodiments forFIG. 2F caller parameters can indicate what, when, where and how to send certain data.Block 296 may send an email, an SMS message, or use other means for conveying data.Service informant code 28 may sendLBX history 30,statistics 14 and/or anyother data 8,data 20, queue data,data 36 orresources 38.Service informant code 28 may update data inhistory 30,statistics 14 or anyother data 8,data 20, queue data,data 36 and/orresources 38, possibly using conditions of this data to determine what is updated.Blocks 294 and 296 may be omitted in some embodiments. - If a single WDR is sent at
block 296 as passed toFIG. 2F processing, then the WDR parameter determined atblock 272 is accessed. If a plurality of WDRs is sent atblock 296, then block 296 appropriately interfaces in a thread-safe manner to queue 22, and sends the WDRs. - Some preferred embodiments do not incorporate
blocks 278 through 286. (i.e. block 276 continues to block 288 if confidence ok).Blocks 278 through 286 are for the purpose of implementing maintaining a date/time stamp of last MS significant movement (using a movement tolerance).Architecture 1900 usesFIG. 2F , as does DLM processing.FIG. 2F must perform well for the preferredmultithreaded architecture 1900.Block 280 performs a peek, and block 284 can be quite timely depending on embodiments used forlocation field 1100 c. A movement tolerance incorporated at the MS is not necessary, but may be nice to have. Therefore, blocks 278 through 286 are optional blocks of processing. -
FIG. 2F may also maintain (with appropriate semaphore) the most recent WDR describing whereabouts of the MS ofFIG. 2F processing to a single data record every time a new one is to be inserted. This allows applications needing current whereabouts to simply access a current WDR, rather than interface to a plurality of WDRs atqueue 22. For example, there could be a new block 289 for updating the single WDR 1100 (just prior to block 290 such that incoming blocks to block 290 go to new block 289, and new block 289 continues to block 290). - With reference now to
FIG. 2E , depicted is a flowchart for describing a preferred embodiment of an MS whereabouts update event of an antenna in-range detected MS, for example aDLM 200, when MS location awareness is monitored by the MS.FIG. 2E describes relevant processing for MSs to maintain their own whereabouts. Processing begins atblock 250 when the MS receives a signal from an antenna (or cell tower) deserving a response and continues to block 252 where the antenna or cell tower signal is authenticated by the MS as being a legitimate signal for processing. The signal can be received for processing byblocks 250 through 264 as the result of a continuous, or pulsed, broadcast or beaconing by the antenna, or cell tower (FIG. 13C ), or as part of usual communication protocol in progress with at least one MS (FIG. 13C usual data 1312 with embedded Communications Key 1314), or as a response via antenna to a previous MS signal (FIG. 13A ). The signal is preferably authenticated by a data parsed signature deserving further processing.Block 252 continues to block 254 where the MS sends an outbound request for soliciting an immediate response from the antenna (or cell tower) service. The request by the MS is appropriately correlated (e.g. as described above) for a response, which additionally facilitates embodiments using TDOA measurements (time of communications between the MS and antenna, or cell tower) to determine how close is the MS in range.Block 254 waits for a response, or waits until a reasonable timeout, whichever occurs first. There are also multithreaded embodiments to breaking upFIG. 2E whereblock 254 does not wait, but rather terminatesFIG. 2E processing and depends on another thread to correlate the response and then continue processingblocks 256 through 260 (like architecture 1900). - Thereafter, if
block 256 determines the request timed out, then processing terminates atblock 264. Ifblock 256 determines the response was received, then processing continues to block 258.Block 258 completes aWDR 1100 with appropriate response data received along with data set by the MS. SeeFIG. 11A descriptions. Fields are set to the following upon exit from block 258: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: Same as was described forFIG. 2D (block 236) above.
CONFIDENCE field 1100 d is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Client Antenna Range” for an antenna detecting the MS, and is set to “Client Cell Range” for a cell tower detecting the MS. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: Same as was described forFIG. 2D (block 236) above.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Same as was described forFIG. 2D (block 236) above.
SPEED field 1100 h is preferably set with: Same as was described forFIG. 2D (block 236) above.
HEADING field 1100 i is preferably set with: Same as was described forFIG. 2D (block 236) above.
ELEVATION field 1100 j is preferably set with: Same as was described forFIG. 2D (block 236) above.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). - The longer time it takes between sending a request and getting a response at
block 254, the less confidence there is for being located because the MS must be a larger distance from the antenna or cell tower. The less time it takes, the more confidence there is for being located because the MS must be a closer distance to the antenna or cell tower. Confidence values are analogously determined as described forFIG. 2D .FIG. 2D NTP embodiments also apply here. NTP can be used so no bidirectional communications is required for TDOA measurement. In this embodiment, the antenna (or cell tower) sets a NTP date/time stamp in the pulse, beacon, or protocol. Upon receipt, the MS instantly knows how long the packet took to be received by comparing the NTP date/time stamp in the packet and a MS NTP date/time stamp of when it was received (i.e. no request/response pair required). If location information is also present with the NTP date/time stamp in data received atblock 252, then block 252 can continue directly to block 258. - An alternate MS embodiment determines its own (direction) heading and/or speed for WDR completion based on historical records maintained to the
WDR queue 22 and/orLBX history 30. -
Block 258 continues to block 260 for preparing parameters for: WDRREF=a reference or pointer to the WDR; DELETEQ=FIG. 2E location queue discard processing; and SUPER=FIG. 2E supervisory notification processing. Thereafter, block 262 invokes the procedure (FIG. 2F processing) to insert the WDR to queue 22. AfterFIG. 2F processing ofblock 262,FIG. 2E processing terminates atblock 264. - In alternative “coming within range” (same as “in range”, “in-range”, “within range”) embodiments, a unique MS identifier, or MS group identifier, for authenticating an MS for locating the MS is not necessary. An antenna emitting signals (
FIG. 13C ) will broadcast (inCK 1314 of data 1312) not only its own location information (e.g. location field 1100 c), but also an NTP indicated date/time stamp field 1100 b, which the receiving MS (also having NTP for time synchronization) uses to perform a TDOA measurement upon receipt. This will enable a MS to determine at least how close (e.g. radius 1318 range,radius 1320 range,radius 1322 range, orradius 1316 range) it is located to the location of the antenna by listening for and receiving the broadcast (e.g. ofFIG. 13C ). Similarly, in another embodiment, an NTP synchronized MS emits signals (FIG. 13A ) and an NTP synchronized data processing system associated with a receiving antenna can make a TDOA measurement upon signal receipt. In other embodiments, more than a single unidirectional signal may be used while still preventing the requirement to recognize the MS to locate it. For example, an antenna emitting signals (e.g.FIG. 13C hotspot WiFi 802.x) will contain enough information for a MS to respond with correlation for being located, and visa-versa. In any case, there can be multi-directional exchanged signals for determining a TDOA measurement. -
FIG. 3A depicts a locating by triangulation illustration for discussing automatic location of a MS, forexample DLM 200.DLM 200 is located through triangulation, as is well known in the art. At least three base towers, for example,base tower 108 b, base tower 108 d, andbase tower 108 f, are used for locating the MS. A fourth base tower may be used if elevation (or altitude) was configured for use in locatingDLM 200. There are cases where only two base towers are necessary given routes of travel are limited and known, for example, in spread out roadways or limited configured locations. Base towers may also beantennas -
FIG. 3B depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a triangulated MS, forexample DLM 200, when MS location awareness is monitored by some remote service. WhileFIG. 3A location determination with TDOA and AOA is well known in the art,FIGS. 3B and 3C include relevant processing for MSs to maintain their own whereabouts. Processing begins atblock 310 and continues to block 312 where base stations able to communicate to any degree with a MS continue reporting to their controller the MS signal strength with an MS identifier (i.e. a unique handle) and Time Difference of Arrival (TDOA) information, Angle of Arrival (AOA) information, or heterogeneously both TDOA and AOA (i.e. MPT), depending on the embodiment. The MS can pick signals from base stations. In some embodiments, the MS monitors a paging channel, called a forward channel. There can be multiple forward channels. A forward channel is the transmission frequency from the base tower to the MS. Either the MS provides broadcast heartbeats (FIG. 13A ) for base stations, or the base stations provide heartbeats (FIG. 13C ) for a response from the MS, or usual MS use protocol signals are detected and used (incorporatingCK 1304 inusual data 1302 by MS, orCK 1314 in “usual data” 1312 by service). Usual data is the usual communications traffic data in carrying outother character 32 processing. Communication from the MS to the base tower is on what is called the reverse channel. Forward channels and reverse channel are used to perform call setup for a created session channel. - TDOA is calculated from the time it takes for a communication to occur from the MS back to the MS via the base tower, or alternatively, from a base tower back to that base tower via the MS. NTP may also be used for time calculations in a unidirectional broadcast from a base tower (
FIG. 13C ) to the MS, or from the MS (FIG. 13A ) to a base tower (as described above). AOA is performed through calculations of the angle by which a signal from the MS encounters the antenna. Triangle geometry is then used to calculate a location. The AOA antenna is typically of a phased array type. - See “Missing Part Triangulation (MPT)” section below with discussions for
FIGS. 11A through 11E for details on heterogeneously locating the MS using both TDOA and AOA (i.e. Missing Part Triangulation (MPT)). Just as high school taught geometry for solving missing parts of a triangle, so to does MPT triangulate an MS location. Think of the length of a side of a triangle as a TDOA measurement—i.e. length of time, translatable to a distance. Think of the AOA of a signal to an antenna as one of the angles of a triangle vertice. Solving with MPT analogously uses geometric and trigonometric formulas to solve the triangulation, albeit at fast processing speeds. - Thereafter, if the MS is determined to be legitimate and deserving of processing (similar to above), then block 314 continues to block 316. If
block 314 determines the MS is not participating with the service, in which case block 312 did little to process it, then processing continues back to block 312 to continue working on behalf of legitimate participating MSs. The controller atblock 316 may communicate with other controllers when base stations in other cellular clusters are picking up a signal, for example, when the MS roams. In any case, atblock 316, the controller(s) determines the strongest signal base stations needed for locating the MS, atblock 316. The strongest signals that can accomplish whereabouts information of the MS are used. Thereafter, block 318 accesses base station location information for base stations determined atblock 316. The base station provides stationary references used to (relatively) determine the location of the MS. Then, block 320 uses the TDOA, or AOA, or MPT (i.e. heterogeneously both AOA and TDOA) information together with known base station locations to calculate the MS location. - Thereafter, block 322 accesses historical MS location information, and block 324 performs housekeeping by pruning location history data for the MS by time, number of entries, or other criteria.
Block 326 then determines a heading (direction) of the MS based on previous location information.Block 326 may perform Artificial Intelligence (AI) to determine where the MS may be going by consulting many or all of the location history data. Thereafter, block 328 completes aservice side WDR 1100, block 330 appends the WDR information to location history data and notifies a supervisory service if there is one outside of the service processing ofFIG. 3B . Processing continues to block 332 where the service communicates the WDR to the located MS. - Thereafter, the MS completes its own WDR at
block 334 for adding toWDR queue 22 to know its own whereabouts whenever possible, and block 336 prepares parameters for invoking WDR insertion processing atblock 338. Parameters are set for: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 3B location queue discard processing; and SUPER=FIG. 3B supervisory notification processing (e.g. no supervisory notification processing because it was already handled atblock 330, or by being in context of theFIG. 3B service processing). Atblock 338, the MS invokesFIG. 2F processing already described. Afterblock 338, processing continues back to block 312. Of course, block 332 continues directly to block 312 at the service(s) since there is no need to wait for MS(s) processing inblocks 334 through 338.FIG. 3B processing is continuous for every MS in thewireless network 7 days a week, 24 hours a day. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 334: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The triangulated location of the MS as communicated by the service.
CONFIDENCE field 1100 d is preferably set with: Confidence of triangulation determined by the service which is passed to the MS atblock 332. The confidence value may be set with the same value (e.g. 85) regardless of how the MS was triangulated. In other embodiments, field 1100 d will be determined (completely, or adjusting the value of 85) by the service for TDOA measurements used, AOA measurements, signal strengths, wave spectrum involved, and/or the abundance of particular MS signals available for processing byblocks 312 through 320. Higher confidences are assigned for smaller TDOA measurements (shorter distances), strong signal strengths, and numerous additional data points beyond what is necessary to locate the MS. Lower confidences are assigned for larger TDOA measurements, weak signal strengths, and minimal data points necessary to locate the MS. A reasonable confidence can be assigned using this information as guidelines where 1 is the lowest confidence and 100 is the highest confidence.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Server Cell TDOA”, “Server Cell AOA”, “Server Cell MPT”, “Server Antenna TDOA”, “Server Antenna AOA”, or “Server Antenna MPT”, depending on how the MS was located and what flavor of service was used. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set) for indicating that all triangulation data was factored into determining confidence, and none is relevant for a single TDOA or AOA measurement in subsequent processing (i.e. service did all the work).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Same as was described forFIG. 2D (block 236) above.
SPEED field 1100 h is preferably set with: Service WDR information atblock 332, wherein the service used historical information and artificial intelligence interrogation of MS travels to determine, if available.
HEADING field 1100 i is preferably set with: Service WDR information atblock 332, wherein the service used historical information and artificial intelligence interrogation of MS travels to determine, if available.
ELEVATION field 1100 j is preferably set with: Elevation/altitude, if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). -
FIG. 3C depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a triangulated MS, for example aDLM 200, when MS location awareness is monitored by the MS. Communications between the base stations and MS is similar toFIG. 3B processing except the MS receives information (FIG. 13C ) for performing calculations and related processing. Processing begins atblock 350 and continues to block 352 where the MS continues receiving (FIG. 13C ) pulse reporting from base stations (or antennas). AOA, TDOA, and MPT (See “Missing Part Triangulation (MPT)” section below with discussions forFIGS. 11A through 11E for details on heterogeneously locating the MS using both TDOA and AOA) can be used to locate the MS, so there are many possible signal types received atblock 352. Then, block 354 determines the strongest signals which can accomplish a completed WDR, or at least a location, of the MS. Thereafter, block 356 parses base station location information from the pulse messages that are received by the MS.Block 358 communicates with base stations to perform TDOA and/or AOA measurements and calculations. The time it takes for a communication to occur from the MS back to the MS for TDOA, or alternatively, from a base tower back to that base tower can be used. NTP may also be used, as described above, so that base towers (or antennas) broadcast signals (FIG. 13C ) picked up by the MS which already contain the base tower locations and NTP date/time stamps for TDOA calculations.Block 358 uses the TDOA and/or AOA information with the known base station information to determine the MS location. While AOA information from the base stations (or antennas) is used by the MS, various MS embodiments can use AOA information detected at an MS antenna provided the heading, yaw, pitch, and roll is known at the MS during the same time as signal reception by the MS. A 3-axis accelerometer (e.g. in iPhone) may also provide yaw, pitch and roll means for proper AOA calculation. - Thereafter, block 360 accesses historical MS location information (e.g.
WDR queue 22 and/or LBX history 30) to prevent redundant information kept at the MS, and block 362 performs housekeeping by pruning theLBX history 30 for the MS by time, number of entries, or other criteria.Block 364 then determines a heading (direction) of the MS based on previous location information (unless already known fromblock 358 for AOA determination).Block 364 may perform Artificial Intelligence (AI) to determine where the MS may be going by consultingqueue 22 and/orhistory 30. Thereafter, block 366 completes aWDR 1100, and block 368 prepares parameters forFIG. 2F processing: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 3C location queue discard processing; and SUPER=FIG. 3B supervisory notification processing.Block 368 continues to block 370 for invokingFIG. 2F processing already described above. Afterblock 370, processing continues back to block 352.FIG. 3C processing is continuous for the MS as long as the MS is enabled. In various multithreaded embodiments, many threads at the MS work together for high speed processing atblocks 352 through 358 for concurrently communicating to many stationary references. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 366: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The triangulated location of the MS as determined by the MS.
CONFIDENCE field 1100 d is preferably set with: The confidence of triangulation as determined by the MS. Confidence may be set with the same value (e.g. 80 since MS may be moving during triangulation) regardless of how the MS was triangulated. In other embodiments, field 1100 d will be determined (completely, or adjusting the value of 80) by the MS for TDOA measurements used, AOA measurements, signal strengths, wave spectrum involved, and/or the abundance of particular service signals available for processing. Higher confidences are assigned for smaller TDOA measurements (shorter distances), strong signal strengths, and numerous additional data points beyond what is necessary to locate the MS. Lower confidences are assigned for larger TDOA measurements, weak signal strengths, and minimal data points necessary to locate the MS. A reasonable confidence can be assigned using this information as guidelines where 1 is the lowest confidence and 100 is the highest confidence.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Client Cell TDOA”, “Client Cell AOA”, “Client Cell MPT”, “Client Antenna TDOA”, “Client Antenna AOA”, or “Client Antenna MPT”, depending on how the MS located itself. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: Data associated with selected best stationary reference(s) used by the MS: the selection location/whereabouts, TDOA measurement to it, and wave spectrum (and/or particular communications interface 70) used, if reasonable. The TDOA measurement may be converted to a distance using wave spectrum information. Also, preferably set herein is data associated with a selected best stationary reference used by the MS (may be same or different than for TDOA measurement): the selection location, AOA measurement to it, and heading, yaw, pitch, and roll values (or accelerometer readings), if reasonable. Values that may be populated here should have already been factored into the confidence value. There may be one or more stationary reference whereabouts with useful measurements maintained here forFIG. 26B processing of block 2652.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Parameters referencing MS internals, if desired.
SPEED field 1100 h is preferably set with: Speed determined by the MS using historical information (queue 22 and/or history 30) and artificial intelligence interrogation of MS travels to determine, if reasonable.
HEADING field 1100 i is preferably set with: Heading determined by the MS using historical information (queue 22 and/or history 30) and artificial intelligence interrogation of MS travels to determine, if reasonable.
ELEVATION field 1100 j is preferably set with: Elevation/altitude, if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). - In alternative triangulation embodiments, a unique MS identifier, or MS group identifier, for authenticating an MS for locating the MS is not necessary. An antenna emitting signals (
FIG. 13C ) will broadcast (CK 1314 of data 1312) not only its own location information, but also an NTP date/time stamp, which the receiving MS (also having NTP for time synchronization) uses to perform TDOA measurements upon receipt. This will enable a MS to determine how close (e.g. radius 1318 range,radius 1320 range,radius 1322 range, orradius 1316 range) it is located to the location of the antenna by listening for and receiving the broadcast (e.g. ofFIG. 13C ). Similarly, in another embodiment, an NTP synchronized MS emits signals (FIG. 13A ) and an NTP synchronized data processing system associated with a receiving antenna can determine a TDOA measurement upon signal receipt. In other embodiments, more than a single unidirectional signal may be used while still preventing the requirement to recognize the MS to locate it. For example, an antenna emitting signals will contain enough information for a MS to respond with correlation for being located. Alternatively, an MS emitting signals will contain enough information for a service to respond with correlation for being located. In any case, there can be multi-directional exchanged signals for determining TDOA. Similarly, a service side data processing system can interact with a MS for AOA information without requiring a known identifier of the MS (use request/response correlation). -
FIG. 4A depicts a locating by GPS triangulation illustration for discussing automatic location of a MS, for example aDLM 200. A MS, forexample DLM 200, is located through GPS triangulation as is well known in the art. At least three satellites, for example,satellite 134,satellite 136, andsatellite 138, are necessary for locating the MS. A fourth satellite would be used if elevation, or altitude, was configured for use by the present disclosure. Ground based stationary references can further enhance whereabouts determination. -
FIG. 4B depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a GPS triangulated MS, for example aDLM 200. Repeated continuous GPS location processing begins atblock 410 and continues to block 412 where the MS initializes to the GPS interface, then to block 414 for performing the conventional locating of the GPS enabled MS, and then to block 416 for calculating location information. In some embodiments, block 412 may only be necessary a first time prior to repeated invocations ofFIG. 4B processing.Block 414 may be an implicit wait for pulses from satellites, or an event driven mechanism when GPS satellite pulses are received for synchronized collection, or a multithreaded implementation concurrently listening for, and processing collaboratively, the signals.Block 414 and block 416 processing is well known in the art. Thereafter, the MS completes aWDR 1100 atblock 418, block 420 prepares parameters forFIG. 2F invocation, and block 422 invokes, with the WDR, theFIG. 2F processing (described above). Processing then terminates atblock 424. Parameters prepared atblock 420 are: WDRREF=a reference or pointer to the WDR; DELETEQ=FIG. 4B location queue discard processing; and SUPER=FIG. 4B supervisory notification processing. GPS location processing is preferably continuous for the MS as long as the MS is enabled. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 418: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The GPS location of the MS.
CONFIDENCE field 1100 d is preferably set with: Confidence of GPS variety (usually high) which may be set with the same value (e.g. 95 for DGPS, 93 for AGPS, and 90 for GPS). In other embodiments, field 1100 d will be determined (completely, or amending the defaulted value) by the MS for timing measurements, signal strengths, and/or the abundance of particular signals available for processing, similarly to as described above. An MS may not be aware of the variety of GPS, in which case straight GPS is assumed.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “GPS”, “A-GPS”, or “D-GPS”, depending on (if known) flavor of GPS. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set) for indicating that data was factored into determining confidence, and none is relevant for a single TDOA or AOA measurement in subsequent processing.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Parameters referencing MS internals, if desired.
SPEED field 1100 h is preferably set with: Speed determined by the MS using a suitable GPS interface, or historical information (queue 22 and/or history 30) and artificial intelligence interrogation of MS travels to determine, if reasonable.
HEADING field 1100 i is preferably set with: Heading determined by the MS using a suitable GPS interface, or historical information (queue 22 and/or history 30) and artificial intelligence interrogation of MS travels to determine, if reasonable.
ELEVATION field 1100 j is preferably set with: Elevation/altitude, if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). -
FIG. 5A depicts a locating by stationary antenna triangulation illustration for discussing automatic location of a MS, forexample DLM 200. There may be communication/transmission issues when an MS is taken indoors. Shown is a top view of anindoor floor plan 502. Antenna stations 504 (shown generally as 504) are strategically placed over the area so that an MS can be located. Triangulation techniques again apply. At least three antenna stations, for example, station 504 f,station 504 h, and station 504 i are used to locate the MS, forexample DLM 200. In floor plan embodiments where aisles delimit travel, only two antenna stations may be necessary, for example at either end of the particular aisle. While most stations 504 may receive signals from the MS, only the strongest stations are used.FIG. 5A and associated discussions can also be used for an outside triangulation embodiment using a similar strategic antenna placement scheme. Processing described forFIGS. 3A to 3C can also be used for an indoor embodiment as described byFIG. 5A . -
FIG. 5B depicts a flowchart for describing a preferred embodiment of the whereabouts update event of a stationary antenna triangulated MS, for example aDLM 200. In one embodiment, indoor location technology of Pinpoint corporation (Pinpoint is a trademark of Pinpoint Corporation) is utilized to locate any MS that moves about the indoor location. The Pinpoint corporation methodology begins at block 510 and continues to block 512. A cell controller drives antenna stations to emit a broadcast signal from every station. Any MS within range (i.e. indoors) will phase modulate its unique identifier onto a return signal it transmits, atblock 514. Stations atblock 516 receive the transmission and strength of signal. The cell controller that drives stations sorts out and selects the strongest (e.g. 3) signals. The cell controller, atblock 518, also extracts the unique MS identifier from the return signal, and TDOA is used to calculate distances from the stations receiving the strongest signals from the MS atblock 520. Alternative embodiments can use AOA or MPT to determine locations. The locations of the controller selected stations are registered in an overlay map in an appropriate coordinate system, landmark system, or grid of cells.Block 522 locates the MS using the overlay map, locations of the (e.g. 3) selected stations, and the calculated distances triangulated from the selected stations, using TDOA, AOA, or MPT in various embodiments. Thereafter, block 524 calculates location information of the MS. Processing continues with repeated broadcast atblock 512 and subsequent processing for every MS within range. - Thereafter, block 526 accesses historical MS location information, performs housekeeping by pruning location history data for the MS by time, number of entries, or other criteria, and determines a heading (direction) of the MS based on previous location information.
Block 526 may perform Artificial Intelligence (AI) to determine where the MS may be going by consulting many or all of the location history data. Thereafter, block 528 completes aservice side WDR 1100, block 530 appends the WDR information to location history data and notifies a supervisory service if there is one outside of the service processing ofFIG. 5B . Processing continues to block 532 where the service communicates the WDR to the located MS. - Thereafter, the MS completes the WDR at block 534 for adding to
WDR queue 22. Thereafter, block 536 prepares parameters passed toFIG. 2F processing for: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 5B location queue discard processing; and SUPER=FIG. 5B supervisory notification processing (e.g. no supervisory notification processing because it was already handled atblock 530, or by being in context of theFIG. 5B service processing).Block 536 continues to block 538 where the MS invokesFIG. 2F processing already described above. Afterblock 538, processing continues back to block 514. Of course, block 532 continues directly to block 514 at the service(s) since there is no need to wait for MS(s) processing in blocks 534 through 538.FIG. 5B processing is continuous for every MS in thewireless network 7 days a week, 24 hours a day. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 534: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The triangulated location of the MS as communicated by the service.
CONFIDENCE field 1100 d is preferably set with: Confidence of triangulation determined by the service which is passed to the MS atblock 532. The confidence value may be set with the same value (e.g. 95 (normally high for triangulation using densely positioned antennas)) regardless of how the MS was triangulated. In other embodiments, field 1100 d will be determined (completely, or adjusting the value of 95) by the service for TDOA measurements used, AOA measurements, signal strengths, wave spectrum involved, and/or the abundance of particular MS signals available for processing. Higher confidences are assigned for smaller TDOA measurements (shorter distances), strong signal strengths, and numerous additional data points beyond what is necessary to locate the MS. Lower confidences are assigned for larger TDOA measurements, weak signal strengths, and minimal data points necessary to locate the MS. A reasonable confidence can be assigned using this information as guidelines where 1 is the lowest confidence and 100 is the highest confidence.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Server Antenna TDOA”, “Server Antenna AOA”, or “Server Antenna MPT”, depending on how the MS was located and what flavor of service was used. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set) for indicating that all triangulation data was factored into determining confidence, and none is relevant for a single TDOA or AOA measurement in subsequent processing (i.e. service did all the work).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Same as was described forFIG. 2D (block 236) above.
SPEED field 1100 h is preferably set with: Service WDR information atblock 532, wherein the service used historical information and artificial intelligence interrogation of MS travels to determine, if available.
HEADING field 1100 i is preferably set with: Service WDR information atblock 532, wherein the service used historical information and artificial intelligence interrogation of MS travels to determine, if available.
ELEVATION field 1100 j is preferably set with: Elevation/altitude, if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). -
FIG. 6A depicts a flowchart for describing a preferred embodiment of a service whereabouts update event of a physically, or logically, connected MS, for example aDLM 200. A MS may be newly located and physically, or logically, connected, whereby communications between the MS and service is over a physical/logical connection. Physical connections may occur by connecting a conduit for communications to the MS, or from the MS to a connection point. Conduits include ethernet cables, optical fiber, firewire, USB, or any other means for conduit for communications through a physical medium. Conduits also include wireless mediums (air) for transporting communications, such as when an MS comes into physical wireless range eligible for sending and receiving communications. Logical connections may occur, after a physical connection already exists, for example through a successful communication, or authenticated, bind between a MS and other MS, or MS and service. Logical connections also include the result of: successfully logging into an application, successfully authenticated for access to some resource, successfully identified by an application, or any other logical status upon a MS being certified, registered, signed in, authenticated, bound, recognized, affirmed, or the like. - Relevant processing begins at
block 602 and continues to block 604 where an MS device is physically/logically connected to a network. Thereafter, the MS accesses a service atblock 606. Then, atblock 608, the service accesses historical MS location history along with the connectivity address, and block 610 performs housekeeping by pruning the location history data maintained for the MS by time, number of entries, or other criteria.Block 610 may perform Artificial Intelligence (AI) to determine where the MS may be going (e.g. using heading based on previous locations) by consulting much or all of the location history data. Thereafter, service processing atblock 612 completes aservice side WDR 1100, then the service appends WDR information to location history data atblock 614, and may notify a supervisory service if there is one outside of the service processing ofFIG. 6A . Processing continues to block 616 where the service communicates WDR information to the newly physically/logically connected MS. There are many embodiments for determining a newly connected MS location using a physical or logical address, for example consulting a database which maps locations to network addresses (e.g. location to logical ip address; location to physical wall jack/port; etc). Then, atblock 618 the MS completes its own WDR using some information fromblock 616,FIG. 2F parameters are prepared atblock 620, block 622 invokesFIG. 2F processing already described above, and processing terminates atblock 624. Parameters are set atblock 620 for: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 6A location queue discard processing; and SUPER=FIG. 6A supervisory notification processing (e.g. no supervisory notification processing because it was already handled atblock 614, or by being in context of theFIG. 6A service processing). Of course, block 616 continues directly to block 624 at the service(s) since there is no need to wait for MS processing inblocks 618 through 622.FIG. 6A processing is available at any appropriate time in accordance with the underlying service. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 618: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The location of the MS as communicated by the service.
CONFIDENCE field 1100 d is preferably set with: Confidence (determined by the service) according to how the MS was connected, or may be set with the same value (e.g. 100 for physical connect, 77 for logical connect (e.g. short range wireless)) regardless of how the MS was located. In other embodiments, field 1100 d will be determined by the service for anticipated physical conduit range, wireless logical connect range, etc. The resulting confidence value can be adjusted based on other parameters analogously to as described above.
LOCATION TECHNOLOGY field 1100 e is preferably set with “Service Physical Connect” or “Service Logical Connect”, depending on how the MS connected. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set), but if a TDOA measurement can be made (e.g. short range logical connect, and using methodologies described above), then a TDOA measurement, a communications signal strength, if available; and wave spectrum (and/or particular communications interface 70) used, if available. The TDOA measurement may be converted to a distance using wave spectrum information. Possible values populated here should have already been factored into the confidence value.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Same as was described forFIG. 2D (block 236) above.
SPEED field 1100 h is preferably set with: null (not set), but can be set with speed required to arrive to the current location from a previously known location, assuming same time scale is used.
HEADING field 1100 i is preferably set with: null (not set), but can be set to heading determined when arriving to the current location from a previously known location.
ELEVATION field 1100 j is preferably set with: Elevation/altitude (e.g. of physical connection, or place of logical connection detection), if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). -
FIG. 6B depicts a flowchart for describing a preferred embodiment of a MS whereabouts update event of a physically, or logically, connected MS, for example aDLM 200. A MS may be newly located and physically/logically connected, whereby communications between the MS and service is over a physical/logical connection as described inFIG. 6A above. Relevant processing begins atblock 640 and continues to block 642 where an MS device is physically/logically connected. Thereafter, atblock 644 the MS accesses the connectivity service and waits for an acknowledgement indicating a successful connection. Upon acknowledgement receipt, processing continues to block 646 where the MS requests WDR information via the connectivity service and waits for the data (i.e. connectivity service may be different than the location service, or may be one in the same). As part of connectivity, location service pointer(s) (e.g. ip address for http://11112.34.323.18 referencing or a Domain Name Service (DNS) name like http://www.servicename.com) are provided with the connectivity acknowledgement from the connectivity service atblock 644, so the MS knows how to proceed atblock 646 for retrieving location information. There are various embodiments for the location service determining a MS location as described above forFIG. 6A . In an alternative embodiment, the MS already knows how to locate itself wherein block 644 continues directly to block 648 (no block 646) because the MS maintains information for determining its own whereabouts using the physical or logical address received in the acknowledgement atblock 644. Similar mapping of a network address to the MS location can be in MS data, forexample data 36,data 8, ordata 20. Atblock 648, the MS completes itsWDR 1100. Thereafter, block 650 preparesFIG. 2F parameters, block 652 invokesFIG. 2F processing already described above, and processing terminates atblock 654. Parameters set atblock 650 are: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 6B location queue discard processing; and SUPER=FIG. 6B supervisory notification processing.FIG. 6B processing is available at any appropriate time to the MS. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 648: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The location determined for the MS.
CONFIDENCE field 1100 d is preferably set with: Confidence (determined by the service) according to how the MS was connected, or may be set with the same value (e.g. 100 for physical connect, 77 for logical connect (e.g. short range wireless)) regardless of how the MS was located. In other embodiments, field 1100 d will be determined by the service for anticipated physical conduit range, wireless logical connect range, etc. The resulting confidence value can be adjusted based on other parameters analogously to as described above.
LOCATION TECHNOLOGY field 1100 e is preferably set with “Client Physical Connect” or “Client Logical Connect”, depending on how the MS connected. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set), but if a TDOA measurement can be made (e.g. short range logical connect, and using methodologies described above), then a TDOA measurement, a communications signal strength, if available; and wave spectrum (and/or particular communications interface 70) used, if available. The TDOA measurement may be converted to a distance using wave spectrum information. Possible values populated here should have already been factored into the confidence value.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Same as was described forFIG. 2D (block 236) above.
SPEED field 1100 h is preferably set with: null (not set), but can be set with speed required to arrive to the current location from a previously known location using, assuming same time scale is used.
HEADING field 1100 i is preferably set with: null (not set), but can be set to heading determined when arriving to the current location from a previously known location.
ELEVATION field 1100 j is preferably set with: Elevation/altitude (e.g. of physical connection, or place of logical connection detection), if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). -
FIGS. 7A , 7B and 7C depict a locating by image sensory illustration for discussing automatic location of a MS, for example aDLM 200. With reference now toFIG. 7A , animage capture device 702 is positioned for monitoring MSs that come into the field ofview 704 ofdevice 702.Device 702 may be a camcorder, video camera, image camera that takes at least one snapshot, timely snapshots, or motion/presence detection snapshots, or any other device capable of producing at least a snapshot image at some point in time containing objects in the field ofview 704. In one preferred embodiment,DLM 200 is sensed within the vicinity ofdevice 702, perhaps by antenna (or cell tower) 701, prior to being photographed bydevice 702. In another embodiment,DLM 200 is sensed by movement within the vicinity ofdevice 702 with well know motion detection means. In yet another embodiment,device 702 periodically or continually records.Device 702 is connected to alocating service 700 for processing as described byFIG. 7D . Locatingservice 700 has means for communicating wirelessly toDLM 200, for example through a connected antenna (or cell tower) 701.FIG. 7A illustrates thatdevice 702 participates in pattern recognition for identifying the location of a MS. The MS can have on its exterior a string of characters, serial number, barcode, license plate, graphic symbol(s), textual symbols, combinations thereof, or any other visually perceptible, or graphical,identification 708 that can be recognized optically, or in a photograph.Device 702 is to have graphical/pixel resolution capability matching the requirements for identifying a MS with the sought graphical identification.Graphical identification 708 can be formed on the perceptible exterior ofDLM 200, or can be formed as part of a housing/apparatus 706 which hostsDLM 200.Graphical identification 708 can be automatically read from an image using well known barcode reader technology, an Optical Character Recognition (OCR) process, a license tag scanner, general pattern recognition software, or the like.Housing 706 is generally shown for representing an automobile (license plate recognition, for example used in prior art toll tag lanes), a shopping cart, a package, or any other hosting article of manufacture which has aDLM 200 as part of it. Upon recognition,DLM 200 is associated with the location ofdevice 702. Error in locating an MS will depend on the distance within the field ofview 704 fromdevice 702. A distance may be estimated based on the anticipated size ofidentification 708, relative its size determined within the field ofview 704. - With reference now to
FIG. 7B ,image capture device 702 is positioned for monitoring MSs that come into the field ofview 704 ofdevice 702. MSs are preferably distinguishable by appearance (e.g. color, shape, markings, labels, tags, etc), or as attached (e.g. recognized mount to host) or carried (e.g. recognized by its recognized user). Such techniques are well known to those skilled in the art.Device 702 is as described above with connectivity to locatingservice 700 and antenna (or cell tower) 701.FIG. 7B illustrates thatdevice 702 uses known measurements within its field of view for determining how large, and where located, are objects that come into the field ofview 704. For example, a well placed and recognizablevertical line 710 a andhorizontal line 710 b, which are preferably perpendicular to each other, have known lengths and positions. The objects which come into the field of view are measured based on the known lengths and positions of thelines view 704 may contain many lines and/or objects of known dimensions strategically placed or recognized within the field ofview 704 to facilitate image processing byservice 700. Building 714 may serve as a reference point having known dimension and position in measuring objects such as aperson 716 orDLM 200. A moving object such as a shopping cart 712 can have known dimensions, but not a specific position, to facilitateservice 700 in locating an MS coming into the field ofview 704. Those skilled in the art recognize that known dimensions and/or locations of anticipated objects in field ofview 704 have measurements facilitating discovering positions and measurements of new objects that may travel into the field ofview 704. UsingFIG. 7B techniques withFIG. 7A techniques provides additional locating accuracy. A distance may be estimated based on the anticipated sizes of references in the field of view, relative size of the recognized MS. - With reference now to
FIG. 7C ,image capture device 702 is positioned for monitoring MSs that come into the field ofview 704 ofdevice 702.Device 702 is as described above with connectivity to locatingservice 700 and antenna (or cell tower) 701. MSs are preferably distinguishable by appearance (e.g. color, shape, markings, labels, tags, etc), or as attached (e.g. recognized mount to host) or carried (e.g. recognized by its user), or as identified byFIG. 7A and/orFIG. 7B methodologies.FIG. 7C illustrates thatdevice 702 uses known locations within its field of view for determining how large, and where located, are objects that come into the field ofview 704. For example, building 714,tree 720, andtraffic sign 722 have its locations known in field ofview 704 byservice 700. Solving locations of objects that move into the field of view is accomplished with graphical triangulation measurements between known object reference locations (e.g. building 714,tree 720, and sign 722) and the object to be located. Timely snapshots bydevice 702 provide an ongoing locating of an MS, forexample DLM 200. Line segment distances 724 (a, b, c) can be measured using references such as those ofFIG. 7B . Whereabouts are determined by providing known coordinates to anticipated objects such asbuilding 714,tree 720, and sign 722. Similarly, graphical AOA measurements (i.e. graphical angle measurements) and graphical MPT measurements can be used in relation to anticipated locations of objects within the field ofview 704. There may be many anticipated (known) object locations within field ofview 704 to further facilitate locating an MS. Being nearby an object may also be enough to locate the MS by using the object's location for the location of the MS. UsingFIG. 7C techniques withFIG. 7A and/orFIG. 7B techniques provides additional locating accuracy. - The system and methodologies illustrated by
FIGS. 7A through 7C are preferably used in optimal combination by locatingservice 700 to provide a best location of an MS. In some embodiments, MS whereabouts is determined as the location of adevice 702 by simply being recognized by thedevice 702. In other embodiments,multiple devices 702 can be strategically placed within a geographic area for being used in combination to acommon locating service 700 for providing a most accurate whereabouts of an MS. Multiple field ofviews 704 from difference angles ofdifferent devices 702 enable more precise locating within three dimensional space, including precise elevations. -
FIG. 7D depicts a flowchart for describing a preferred embodiment of graphically locating a MS in accordance with locatingservice 700 described above, for example as illustrated byFIGS. 7A through 7C . Locatingservice 700 may be a single capable data processing system, or many connected data processing systems for enhanced parallel processing. Locatingservice 700 may be connected to services involved with any other locating technology described in this application for synergistic services as an MS is mobile. Locatingservice 700 begins atblock 732 and continues to block 734 where theservice 700 is initialized in preparation of MS whereabouts analysis.Block 734 initializes its table(s) of sought identifying criteria which can be pattern recognized. In one preferred embodiment, color/shade, shape, appearance and applicable sought information is initialized for each sought identifying criteria. Pattern recognition is well known in the art and initialization is specific for each technology discussed above forFIGS. 7A through 7C . ForFIGS. 7B and 7C discussions, positions, measurements, and reference points of known landmarks are additionally accounted. Thereafter, block 736 gets the next snapshot from device(s) 702. If there is none waiting to get, block 736 waits for one. If there is one queued up for processing, then block 736 continues to block 738.FIG. 7D is processing of a service, and is preferably multi-threaded. For example, blocks 736 through 754 can occur concurrently in many threads for processing a common queue of snapshots received from adevice 702, ormany devices 702. Each thread may process all sought criteria, or may specialize in a subset of sought criteria wherein if nothing is found, the thread can place the snapshot back on a queue for thread processing for another sought criteria after marking the queue entry as having been processed for one particular subset. So, threads may be specialized and work together in seeking all criteria, or may each work in parallel seeking the same criteria. In preferred embodiments, there is at least one queue of snapshots received by block(s) 736.Block 736 continues to block 738 which attempts to detect an MS having sought criteria using pattern recognition techniques ofFIGS. 7A through 7C , in particular, or in combination. In one example embodiment, asdevice 702 providesservice 700 with at least one timely snapshot to block 736, the snapshot graphic is scanned atblock 738 for identifying characters/symbols/appearance of sought criteria.Block 738 continues with its search result to block 740. Ifblock 740 determines no MS was detected, then processing continues back to block 736. Ifblock 738 detected at least one MS (as determined at block 740), then block 742 calculates WDR information for the MS(s) detected, block 744 notifies a supervisory service of MS whereabouts if applicable, block 746 communicates the WDR information to MS(s) detected (for example via antenna 701), and processing continues to block 748. - There may be a plurality of MSs in the field of view, so communications at
block 746 targets each MS recognized. A MS should not rely on the service to have done its job correctly. At a MS, block 748 checks the MS ID communicated for validation. Ifblock 748 determines the MS ID is incorrect, then processing continues back to block 736 (for the particular MS). Ifblock 748 determines the MS ID is correct, then processing continues to block 750 where the particular MS completes itsWDR 1100 received fromservice 700. Thereafter, MS(s) prepare parameters atblock 752, invoke localFIG. 2F processing already described above (at block 754), and processing continues forservice 700 back to block 736. Of course, block 746 continues directly to block 736 at the service(s) since there is no need to wait for MS(s) processing inblocks 748 through 754. Parameters set atblock 752 are: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 7D location queue discard processing; and SUPER=FIG. 7D supervisory notification (e.g. no supervisory notification processing because it was already handled atblock 744, or by being in context of theFIG. 7D service processing). No snapshots fromdevice 702 are to be missed atblock 736. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 750: -
MS ID field 1100 a is preferably set with: Unique MS identifier of the MS, after validating at the MS that theservice 700 has correctly identified it. This field is used to uniquely distinguish this MS WDRs onqueue 22 from other originated WDRs. Theservice 700 may determine a MS ID from a database lookup using above appearance criteria.Field 1100 a may also be determined using the transmission methods as described forFIGS. 2A through 2E , for example by way ofantenna 701. For example, when the MS comes within range ofantenna 701,FIG. 7D processing commences. Another embodiment prevents recognizing more than one MS within the field ofview 704 at any time (e.g. a single file entryway), in which case the service can solicit a “who are you” transmission to identify the MS and then send back its whereabouts (in which case the MS sets its own MS ID here).
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The location determined for the MS by the service.
CONFIDENCE field 1100 d is preferably set with: same value (e.g. 76) regardless of how the MS location was determined. In other embodiments, field 1100 d will be determined by the number of distance measurements and/or the abundance of particular objects used in the field ofview 704. The resulting confidence value can be adjusted based on other graphical parameters involved, analogously to as described above.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Server Graphic-Patterns” “Server Graphic-Distances”, “Server Graphic Triangulate”, or a combination field value depending on how the MS was located and what flavor of service was used. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set) for indicating that all whereabouts determination data was factored into the confidence, and none is relevant for a single TDOA or AOA measurement in subsequent processing (i.e. service did all the work).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Same as was described forFIG. 2D (block 236) above.
SPEED field 1100 h is preferably set with: null (not set), but can be set with speed required to arrive to the current location from a previously known time at a location (e.g. using previous snapshots processed), assuming the same time scale is used.
HEADING field 1100 i is preferably set with: null (not set), but can be set to heading determined when arriving to the current location from a previously known location (e.g. using previous snapshots processed).
ELEVATION field 1100 j is preferably set with: Elevation/altitude, if available, if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). - In an alternative embodiment,
MS 2 may be equipped (e.g. as part of resources 38) with itsown device 702 and field ofview 704 for graphically identifying recognizable environmental objects or places to determine its own whereabouts. In this embodiment, the MS would have access to anticipated objects, locations and dimensions much the same way described forFIGS. 7A through 7D , either locally maintained or verifiable with a connected service. Upon a successful recognition of an object, place, or other graphically perceptible image which can be mapped to a location, the MS would complete a WDR similarly to above. The MS may recognize addresses, buildings, landmarks, of other pictorial data. Thus, the MS may graphically determine its own location. The MS would then complete aWDR 1100 forFIG. 2F processing exactly as described forFIG. 7D with the exceptions of fields that follow: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: The location determined for the MS by the MS.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Client Graphic-Patterns” “Client Graphic-Distances”, “Client Graphic Triangulate”, or a combination field value depending on how the MS located itself. The originator indicator is set to DLM.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: null (not set). -
FIG. 8A heterogeneously depicts a locating by arbitrary wave spectrum illustration for discussing automatic location of a MS. In the case of acoustics or sound, prior art has shown that a noise emitting animal or object can be located by triangulating the sound received using TDOA by strategically placed microphones. It is known that by figuring out time delay between a few strategically spaced microphones, one can infer the location of the sound. In a preferred embodiment, an MS, forexample DLM 200, emits a pulsed or constant sound (preferably beyond the human hearing range) which can be sensed bymicrophones 802 though 806. Data is superimposed on the sound wave spectrum with variations in pitch or tone, or data occurs in patterned breaks in sound transmission. Data may contain a unique identifier of the MS so service(s) attached tomicrophones 802 through 806 can communicate uniquely to an MS. In some embodiments, sound used by the MS is known to repel certain pests such as unwanted animals, rodents, or bugs in order to prevent the person carrying the MS from encountering such pests during travel, for example during outdoor hiking or mountain climbing. In submarine acoustics, AOA is a method to locate certain objects. TheFIGS. 3B and 3C flowcharts occur analogously for sound signals received bymicrophones 802 through 806 which are connected to service processing ofFIGS. 3B and 3C . The only difference is wave spectrum used. - It has been shown that light can be used to triangulate position or location information (e.g. U.S. Pat. No. 6,549,288 (Migdal et al) and U.S. Pat. No. 6,549,289 (Ellis)).
Optical sensors 802 through 806 detect a light source of, or illumination of, an MS, forexample DLM 200. Data is superimposed on the light wave spectrum with specified frequency/wavelength and/or periodicity, or data occurs in patterned breaks in light transmission. Data may contain a unique identifier of the MS so service(s) attached tosensors 802 through 806 can communicate uniquely to an MS. Mirrors positioned atoptical sensors 802 through 806 may be used to determine an AOA of light at the sensor, or alternatively TDOA of recognizable light spectrum is used to position an MS. TheFIGS. 3B and 3C flowcharts occur analogously for light signals received bysensors 802 through 806 which are connected to service processing ofFIGS. 3B and 3C . The only difference is wave spectrum used. - Heterogeneously speaking,
FIG. 8A illustrates having strategically placedsensors 802 through 806 for detecting a wave spectrum and using TDOA, AOA, or MPT. Those skilled in the art appreciate that a wave is analogously dealt with byFIGS. 3B and 3C regardless of the wave type, albeit withdifferent sensor types 802 through 806 and different sensor interface to service(s) ofFIGS. 3B and 3C . Wave signal spectrums for triangulation by analogous processing toFIGS. 3B and 3C include microwaves, infrared, visible light, ultraviolet light, X-rays, gamma rays, longwaves, magnetic spectrum, or any other invisible, visible, audible, or inaudible wave spectrum.Sensors 802 through 806 are appropriately matched according to the requirements. Alternatively, a MS may be sensing wave spectrums emitted bytransmitters 802 through 806. - Those skilled in the relevant arts appreciate that the point in all this discussion is all the wave forms provide methods for triangulating whereabouts information of an MS. Different types of wave forms that are available for an MS can be used solely, or in conjunction with each other, to determine MS whereabouts. MSs may be informed of their location using the identical wave spectrum used for whereabouts determination, or may use any other spectrum available for communicating WDR information back to the MS. Alternatively, the MS itself can determine WDR information relative applicable sensors/transmitters. In any case, a
WDR 1100 is completed analogously toFIGS. 3B and 3C . -
FIG. 8B depicts a flowchart for describing a preferred embodiment of locating a MS through physically sensing a MS, for example aDLM 200. Processing begins atblock 810 upon contact with a candidate MS and continues to block 812 where initialization takes place. Initialization includes determining when, where, and how the contact was made. Then, block 814 takes the contact sample and sets it as input containing a unique identifier or handle of the MS which was sensed. There are various known embodiments of how the MS is sensed: -
- a) Touching sensors contact the MS (or host/housing having MS) to interpret physical characteristics of the MS in order to uniquely identify it (e.g. Braille, embossed/raised/depressed symbols or markings, shape, temperature, depressions, size, combinations thereof, etc);
- b) Purchase is made with MS while in vicinity of device accepting purchase, and as part of that transaction, the MS is sensed as being at the same location as the device accepting purchase, for example using a cell phone to purchase a soft drink from a soft drink dispensing machine;
- c) Barcode reader is used by person to scan the MS (or host/housing having MS), for example as part of shipping, receiving, or transporting;
- d) The MS, or housing with MS, is sensed by its odor (or host/housing having MS), perhaps an odor indicating where it had been, where it should not be, or where it should be. Various odor detection techniques may be used;
- e) Optical sensing wherein the MS is scanned with optical sensory means, for example to read a serial number; and/or
- f) Any sensing means which can identify the MS through physical contact, or by nearby/close physical contact with some wave spectrum.
Block 814 continues to block 816 where a database is accessed for recognizing the MS identifier (handle) by mapping sensed information with an associated MS handle. If a match is found atblock 818, then block 822 determinesWDR 1100 information using the location of where sensing took place. Ifblock 818 determines no match was found, then data is saved atblock 820 for an unrecognized entity such as is useful when an MS should have been recognized, but was not. In another embodiment, the MS handle is directly sensed so block 814 continues directly to block 818 (no block 816).Block 820 continues to block 834 where processing terminates.Block 816 may not use the entire MS identifier for search, but some portion of it to make sure it is a supported MS for being located by sensing. The MS identifier is useful when communicating wirelessly the WDR information to the MS (at block 826).
- Referring now back to block 822, processing continues to block 824 where a supervisory service may be updated with the MS whereabouts (if applicable), and block 826 communicates the WDR information to the MS. Any available communication method can be used for communicating the WDR information to the MS, as described above. Thereafter, the MS completes the WDR at
block 828, block 830 preparesFIG. 2F parameters, and block 832 invokesFIG. 2F processing already described above. Processing terminates thereafter atblock 834. Parameters set atblock 830 are: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 8B location queue discard processing; and SUPER=FIG. 8B supervisory notification (e.g. no supervisory notification processing because it was already handled atblock 824, or by being in context of theFIG. 8B service processing).FIG. 8B processing is available at any appropriate time for the MS. In an alternate embodiment, the MS senses its environment to determine whereabouts. - See
FIG. 11A descriptions. Fields are set to the following upon exit from block 828: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: Location of the sensor sensing the MS.
CONFIDENCE field 1100 d is preferably set with: Should be high confidence (e.g. 98) for indisputable contact sensing and is typically set with the same value.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Contact”, or a specific type of Contact. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: Same as was described forFIG. 2D (block 236) above.
SPEED field 1100 h is preferably set with: null (not set), but can be set with speed required to arrive to the current location from a previously known time at a location, assuming the same time scale is used.
HEADING field 1100 i is preferably set with: null (not set), but can be set to heading determined when arriving to the current location from a previously known location.
ELEVATION field 1100 j is preferably set with: Elevation/altitude, if available.
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). -
FIG. 8C depicts a flowchart for describing a preferred embodiment of locating a MS, for example aDLM 200, through a manually entered location of the MS. MS user interface processing begins atblock 850 when a user starts the user interface fromcode 18 and continues to block 852. Any of a variety of user interfaces, dependent on the type of MS, is used for manually entering the location of the MS. A user interfaces with the MS atblock 852 until one of the monitored actions relevant to this disclosure are detected. Thereafter, if block 854 determines the user has selected to set his location manually, then processing continues to block 860. If block 854 determines the user did not select to manually set his location, then block 856 determines if the user selected to force the MS to determine its location. If the user did select to force the MS to get its own location, then block 856 continues to block 862. If the user did not select to force the MS to get its own location as determined byblock 856, then processing continues to block 858. Ifblock 858 determines the user wanted to exit the user interface, then block 880 terminates the interface and processing terminates atblock 882. Ifblock 858 determines the user did not want to exit the user interface, then block 884 handles any user interface actions which caused exit fromblock 852 yet were not handled by any action processing relevant to this disclosure. - With reference back to block 860, the user interfaces with the MS user interface to manually specify WDR information. The user can specify:
-
- 1) An address or any address subset such as a zip code;
- 2) Latitude, longitude, and elevation;
- 3) MAPSCO identifier;
- 4) FEMA map identifier;
- 5) USDA map identifier;
- 6) Direct data entry to a
WDR 1100; or - 7) Any other method for user specified whereabouts of the MS.
- The user can specify a relevant confidence value for the manually entered location, however, processing at
block 860 preferably automatically defaults a confidence value for the data entered. For example, a complete address, validated atblock 860, will have a high confidence. A partial address such as city and state, or a zip code will have a low confidence value. The confidence value will reflect how large an area is candidate for where the MS is actually located. To prevent completely relying on the user atblock 860 for accurate WDR information, validation embodiments may be deployed. Some examples: -
- Upon specification (e.g. FEMA), the MS will access connected service(s) to determine accuracy (FEMA conversion tables);
- Upon specification (e.g. MAPSCO), the MS will access local resources to help validate the specification (e.g. MAPSCO conversion tables); and/or
- Upon specification (e.g. address), the MS can access
queue 22 and/orhistory 30 for evidence proving likelihood of accuracy. The MS may also access services, or local resources, for converting location information for proper comparisons.
In any case, a confidence field 1100 d value can be automatically set based on the validation results, and the confidence may, or may not, be enabled for override by the user.
- After WDR information is specified at
block 860, the MS completes the WDR atblock 874, block 876 prepares parameters forFIG. 2F processing, and (at block 878) the MS invokesFIG. 2F processing already described above before returning back to block 852. Parameters set atblock 876 are: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 8C location queue discard processing; and SUPER=FIG. 8C supervisory notification processing. Various embodiments permit override of the confidence floor value by the user, or byFIG. 8C processing.Block 874 may convert the user specified information into a standardized more usable form in an LN-expanse (e.g. convert to latitude and longitude if possible, truncated precision for more area coverage).WDR 1100 fields (seeFIG. 11A ) are set analogously in light of the many variations already described above. - With reference back to block 862, if it is determined that the MS is equipped with capability (e.g. in range, or in readiness) to locate itself, then processing continues to block 864 where the MS locates itself using MS driven capability described by
FIGS. 2E , 3C, 4B, 6B, and 8A or MS driven alternative embodiments toFIGS. 2D , 3B, 5B, 6A, 7D, 8A, and 8B, or any other MS capability for determining its own whereabouts with or without help from other data processing systems or services. Interfacing to locating capability preferably involves a timeout in case there is no, or slow, response, therefore block 864 continues to block 868 where it determined whether or not block 864 timed out prior to determining a location. Ifblock 868 determines a timeout was encountered, then block 872 provides the user with an error to the user interface, and processing continues back to block 852.Block 872 preferably requires use acknowledgement prior to continuing to block 852. - If
block 868 determines there was no timeout (i.e. whereabouts successfully determined), then block 870 interfaces to the locating interface to get WDR information, block 874 completes a WDR, and blocks 876 and 878 do as described above. Ifblock 862 determines the MS cannot locate itself and needs help, then block 866 emits at least one broadcast request to any listening service which can provide the MS its location. Appropriate correlation is used for an anticipated response. Example services listening are service driven capability described byFIGS. 2D , 3B, 5B, 6A, 7D, 8A, and 8B, or service side alternative embodiments ofFIGS. 2E , 3C, 4B, 6B, and 8A, or any other service capability for determining MS whereabouts with or without help from the MS or other data processing systems or services.Block 866 then continues to block 868. - If
block 868 determines a timeout was encountered from the service broadcast request, then block 872 provides the user with an error to the user interface, and processing continues back to block 852. Ifblock 868 determines there was no timeout (i.e. whereabouts successfully determined), then block 870 receives WDR information from the locating interface of the responding service, block 874 completes a WDR, and blocks 876 and 878 do as already described above. - See
FIG. 11A descriptions. Depending how the MS was located via processing started atblock 856 to block 862, a WDR is completed analogous to as described in Figs. above. If the user manually specified whereabouts atblock 860, fields are set to the following upon exit from block 874: -
MS ID field 1100 a is preferably set with: Same as was described forFIG. 2D (block 236) above.
DATE/TIME STAMP field 1100 b is preferably set with: Same as was described forFIG. 2D (block 236) above.
LOCATION field 1100 c is preferably set with: Location entered by the user, or converted from entry by the user; preferably validated.
CONFIDENCE field 1100 d is preferably set with: User specified confidence value, or a system assigned value per a validated manual specification. Confidence should reflect confidence of location precision (e.g. validated full address high; city and zip code low, etc). Manually specified confidences are preferably lower than other location technologies since users may abuse or set incorrectly, unless validated. Specifying lower confidence values than technologies above, for completely manual WDR specifications (i.e. no validation), ensures that manual specifications are only used by the MS in absence of other technologies.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “Manual”, or “Manual Validated”. Types of validations may further be elaborated. The originator indicator is set to DLM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: null (not set).
SPEED field 1100 h is preferably set with: null (not set).
HEADING field 1100 i is preferably set with: null (not set).
ELEVATION field 1100 j is preferably set with: null (not set).
APPLICATION FIELDS field 1100 k is preferably set with: Same as was described forFIG. 2D (block 236) above; or as decided by the user.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). -
FIG. 9A depicts a table for illustrating heterogeneously locating a MS, for example aDLM 200. While many location methods and systems have been exhausted above, there may be other system and methods for locating an MS which apply to the present disclosure. The requirement for LBX is that the MS be located, regardless of how that occurs. MSs disclosed herein can be located by one or many location technologies discussed. As MS prices move lower, and capabilities increase, an affordable MS will contain multiple abilities for being located. GPS, triangulation, in-range detection, and contact sensory may all be used in locating a particular MS as it travels. Equipping the MS with all techniques is straightforward and is compelling when there are competing, or complementary, technologies that the MS should participate in. - The
FIG. 9A table has DLM location methods for rows and a single column for the MS (e.g. DLM 200). Each location technology can be driven by the client (i.e. the MS), or a service (i.e. the location server(s)) as denoted by a row qualifier “C” for client or “S” for service. An MS may be located by many technologies. The table illustrated shows that the MS with unique identifier 0A12:43EF:985B:012F is able to be heterogeneously located, specifically with local MS GPS capability, service side cell tower in-range detection, service side cell tower TDOA, service side cell tower MPT (combination of TDOA and AOA), service side antenna in-range detection, service side antenna AOA, service side antenna TDOA, service side antenna MPT, service side contact/sensory, and general service side MPT. The unique identifier in this example is a universal product identifier (like Host Bus Adapter (HBA) World Wide Name (WWN) identifiers are generated), but could be in other form as described above (e.g. phone #214-403-4071). An MS can have any subset of technologies used to locate it, or all of the technologies used to locate it at some time during its travels. An MS is heterogeneously located when two or more location technologies are used to locate the MS during MS travels and/or when two or more location technologies with incomplete results are used in conjunction with each other to locate the MS during MS travels, such as MPT. MPT is a heterogeneous location technology because it uses at least two different methods to accomplish a single location determination. Using combinations of different location technologies can be used, for example a TDOA measurement from an in-range antenna with a TDOA measurement relative a cell tower (e.g. as accomplished in MS processing ofFIG. 26B ), using completely different services that have no knowledge of each other. Another combination is to use a synergy of whereabouts data from one technology with whereabouts data from another technology. For example, in-range detection is used in combination with graphical identification to provide better whereabouts of a MS. In another example, a GPS equipped MS travels to an area where GPS does not work well (e.g. downtown amidst large and tall buildings). The DLM becomes an ILM, and is triangulated relative other MSs. So, an MS is heterogeneously located using two or more technologies to determine a single whereabouts, or different whereabouts of the MS during travel. -
FIG. 9B depicts a flowchart for describing a preferred embodiment of heterogeneously locating a MS, forexample DLM 200. While heterogeneously locating an MS can occur by locating the MS at different times using different location technologies, flowchart 9B is shown to discuss a generalization of using different location technologies with each other at the same time to locate an MS. Processing begins atblock 950 and continues to block 952 where a plurality of parameters from more than one location technology are examined for locating an MS. Processing begins atblock 950 by a service (or the MS) when a location technology by itself cannot be used to confidently locate the MS. Data deemed useful atblock 952, when used in conjunction with data from a different location technology to confidently locate the MS, is passed for processing to block 954.Block 954 heterogeneously locates the MS using data from at least two location technologies to complement each other and to be used in conjunction with each other in order to confidently locate the MS. Once the MS whereabouts are determined atblock 954, WDR information is communicated to the MS for further processing atblock 956. In some embodiments where a service is heterogeneously locating the MS, block 956 communicates WDR information wirelessly to the MS before processing begins atblock 958. In another embodiment where the MS is heterogeneously locating itself, block 956 communicates WDR information internally to WDR completion processing atblock 958. In preferred embodiments, the MS completes its WDR information atblock 958,FIG. 2F parameters are prepared atblock 960, and the MS invokesFIG. 2F processing already described above (at block 962), before processing terminates atblock 964. Parameters set atblock 960 are: WDRREF=a reference or pointer to the MS WDR; DELETEQ=FIG. 9B location queue discard processing; and SUPER=FIG. 9B supervisory notification processing.WDR 1100 fields (seeFIG. 11A ) are set analogously in light of many variations already described above. - In some embodiments of
FIG. 9B processing, Missing Part Triangulation (MPT) is used to heterogeneously locate an MS. For a service side embodiment example, block 950 begins service processing when TDOA information itself cannot be used to confidently locate the MS, or AOA information itself cannot be used to confidently locate the MS, however using angles and distances from each in conjunction with each other enables solving whereabouts confidently. See “Missing Part Triangulation (MPT)” section below with discussions forFIGS. 11A through 11E for MPT processing ofblocks block 952 and processed byblock 954 depends on the embodiment, what stationary reference point locations are known at the time ofblocks - While MPT has been discussed by example, flowchart 9B is not to be interpreted in a limiting sense. Any location technologies, for example as shown in
FIG. 9A , can be used in conjunction with each other when not all information required is available in a single location technology to confidently deduce an MS location. Data available from the different location technologies available will be examined on its own merits, and optionally used in conjunction to deduce a confident location. For example, a TDOA (difference between when signal sent and when received) measurement from “coming within range” technology can be used to distinguish how close, or how far, is an MS in the vicinity. That measurement may be used to more confidently locate the MS using other TDOA measurements from other unrelated “coming within range” whereabouts information. - With the many DLM examples above, it should be clear now to the reader how to set the
WDR 1100 for DLM invokedFIG. 2F processing. There can be other location technologies that will setWDR 1100 fields analogously. Locating methodologies ofFIGS. 2A through 9B can be used in any combination, for example for more timely or accurate locating. Furthermore, a MS automatically takes on a role of a DLM or ILM depending on what capability is available at the time, regardless of whether or not the MS is equipped for being directly located. As a DLM roams to unsupported areas, it can remain a DLM using different DLM technologies, and it can become an ILM to depend on other MSs (ILMs or DLMs) in the vicinity to locate it. -
FIGS. 10A and 10B depict an illustration of a Locatable Network expanse (LN-Expanse) 1002 for describing locating of an ILM with all DLMs. With reference now toFIG. 10A ,DLM 200 a,DLM 200 b,DLM 200 c,DLM 200 d, andDLM 200 e (referred to generally inFIGS. 10A and 10B discussions as DLMs 200) are each automatically and directly located, for example using any of the automatic location technologies heretofore described.ILM 1000 b is automatically located using the reference locations ofDLM 200 b,DLM 200 c, andDLM 200 e.DLMs 200 can be mobile while providing reference locations for automatically determining the location ofILM 1000 b. Timely communications between MSs is all that is required for indirectly locating MSs. In some embodiments,DLMs 200 are used to triangulate the position ofILM 1000 b using aforementioned wave spectrum(s) reasonable for the MSs. Different triangulation embodiments can triangulate the location ofILM 1000 b using TDOA, AOA, or MPT, preferably by theILM 1000 b seeking to be located. In other embodiments, TDOA information is used to determine howclose ILM 1000 b is to a DLM for associating the ILM at the same location of a DLM, but with how close nearby. In other embodiments, an ILM is located by simply being in communications range to another MS.DLMs 200 can be referenced for determining elevation of an ILM. The same automatic location technologies used to locate a DLM can be used to automatically locate an ILM, except the DLMs are mobile and serve as the reference points. It is therefore important that DLM locations be timely known when references are needed for locating ILMs. Timely ILM interactions with other MSs, and protocol considerations are discussed inarchitecture 1900 below.DLMs ILM 1000 b by their WDR high confidence values, however any other WDR data may be used whereby wave spectrum, channel signal strength, time information, nearness, surrounded-ness, etc is considered for generating a confidence field 1100 d of theWDR 1100 for the located ILM. Preferably, those considerations are factored into a confidence value, so that confidence values can be completely relied upon. - With reference now to
FIG. 10B ,ILM 1000 c has been located relative a plurality of DLMs, namelyDLM 200 b,DLM 200 d, andDLM 200 e.ILM 1000 c is located analogously toILM 1000 b as described forFIG. 10A , except there are different DLMs involved with doing the locating ofILM 1000 c because of a different location ofILM 1000 c.FIGS. 10A and 10B illustrate that MSs can be located using other MSs, rather than fixed stationary references described forFIGS. 2A through 9B .ILM 1000 b andILM 1000 c are indirectly located usingDLMs 200. -
FIG. 10C depicts an illustration of a Locatable Network expanse (LN-Expanse) 1002 for describing locating of an ILM with an ILM and DLM.ILM 1000 a is automatically located using the reference locations ofDLM 200 c,DLM 200 b, andILM 1000 b.DLM 200 b,DLM 200 c andILM 1000 b can be mobile while providing reference locations for automatically determining the location ofILM 1000 a. In some embodiments, MSs are used to triangulate the position ofILM 1000 a using any of the aforementioned wave spectrum(s) (e.g. WiFi 802.x, cellular radio, etc) reasonable for the MSs. Different triangulation embodiments can triangulate the location ofILM 1000 a using TDOA, AOA, or MPT, preferably by theILM 1000 a seeking to be located. In other embodiments, TDOA information is used to determine howclose ILM 1000 a is to a MS (DLM or ILM) for associating the ILM at the same location of a MS, but with how close nearby. In other embodiments, an ILM is located by simply being in communications range to another MS. DLMs or ILMs can be referenced for determining elevation ofILM 1000 a. The same automatic location technologies used to locate a MS (DLM or ILM) are used to automatically locate an ILM, except the MSs are mobile and serve as the reference points. It is therefore important that MS (ILM and/or DLM) locations be timely known when references are needed for locating ILMs. Timely ILM interactions with other MSs, and protocol considerations are discussed inarchitecture 1900 below.DLM 200 b,DLM 200 c, andILM 1000 b are preferably selected for locatingILM 1000 a by their WDR high confidence values, however any other WDR data may be used whereby wave spectrum, channel signal strength, time information, nearness, surrounded-ness, etc is considered for generating a confidence field 1100 d of theWDR 1100 for the located ILM. Preferably, those considerations were already factored into a confidence value so that confidence values can be completely relied upon.ILM 1000 a is indirectly located using DLM(s) and ILM(s). -
FIGS. 10D , 10E, and 10F depict an illustration of a Locatable Network expanse (LN-Expanse) 1002 describing locating of an ILM with all ILMs. With reference now toFIG. 10D ,ILM 1000 e is automatically located using the reference locations ofILM 1000 a,ILM 1000 b, andILM 1000 c.ILM 1000 a,ILM 1000 b andILM 1000 c can be mobile while providing reference locations for automatically determining the location ofILM 1000 e. Timely communications between MSs is all that is required. In some embodiments, MSs are used to triangulate the position ofILM 1000 e using any of the aforementioned wave spectrum(s) reasonable for the MSs. Different triangulation embodiments can triangulate the location ofILM 1000 e using TDOA, AOA, or MPT processing (relative ILMs 1000 a through 1000 c), preferably by theILM 1000 e seeking to be located. ILMs can be referenced for determining elevation ofILM 1000 e. The same automatic location technologies used to locate a MS (DLM or ILM) are used to automatically locate an ILM, except the MSs are mobile and serve as the reference points. It is therefore important that ILM locations be timely known when references are needed for locating ILMs. Timely ILM interactions with other MSs, and protocol considerations are discussed inarchitecture 1900 below.ILM 1000 a,ILM 1000 b, andILM 1000 c are preferably selected for locatingILM 1000 e by their WDR high confidence values, however any other WDR data may be used whereby wave spectrum, channel signal strength, time information, nearness, surrounded-ness, etc is considered for generating a confidence field 1100 d of theWDR 1100 for the located ILM. Preferably, those considerations were already factored into a confidence value so that confidence values can be completely relied upon.ILM 1000 e is indirectly located usingILM 1000 a,ILM 1000 b, andILM 1000 c. - With reference now to
FIG. 10E ,ILM 1000 g is automatically located using the reference locations ofILM 1000 a,ILM 1000 c, andILM 1000 e.ILM 1000 a,ILM 1000 c andILM 1000 e can be mobile while providing reference locations for automatically determining the location ofILM 1000 g.ILM 1000 g is located analogously toILM 1000 e as described forFIG. 10D , except there are different ILMs involved with doing the locating ofILM 1000 g because of a different location ofILM 1000 g. Note that as ILMs are located in the LN-expanse 1002, the LN-expanse expands with additionally located MSs. - With reference now to
FIG. 10F ,ILM 1000 i is automatically located using the reference locations ofILM 1000 f,ILM 1000 g, andILM 1000 h.ILM 1000 f,ILM 1000 g andILM 1000 h can be mobile while providing reference locations for automatically determining the location ofILM 1000 i.ILM 1000 i is located analogously toILM 1000 e as described forFIG. 10D , except there are different ILMs involved with doing the locating ofILM 1000 i because of a different location ofILM 1000 i.FIGS. 10D through 10F illustrate that an MS can be located using all ILMs, rather than all DLMs (FIGS. 10A and 10B ), a mixed set of DLMs and ILMs (FIG. 10C ), or fixed stationary references (FIGS. 2A through 9B ).ILMs FIG. 10 illustrations the LN-expanse 1002 has expanded down and to the right from DLMs directly located up and to the left. It should also be noted that locating any MS can be done with at least one other MS. Three are not required as illustrated. It is preferable that triangulation references used surround an MS. -
FIGS. 10G and 10H depict an illustration for describing the reach of a Locatable Network expanse (LN-Expanse) according to MSs. Location confidence will be dependent on the closest DLMs, how stale an MS location becomes for serving as a reference point, and how timely an MS refreshes itself with a determined location. An MS preferably has highest available processing speed with multithreaded capability in a plurality of hardware processors and/or processor cores. A substantially large number of high speed concurrent threads of processing that can occur within an MS provides for an optimal capability for being located quickly among its peer MSs, and for serving as a reference to its peer MSs. MS processing described in flowcharts herein assumes multiple threads of processing with adequate speed to accomplish an optimal range in expanding the LN-Expanse 1002. - With reference now to
FIG. 10G , an analysis of an LN-Expanse 1002 will contain at least oneDLM region 1022 containing a plurality of DLMs, and at least one DLM indirectly locatedregion 1024 containing at least one ILM that has been located with all DLMs. Depending on the range, or scope, of an LN-Expanse 1002, there may be amixed region 1026 containing at least one ILM that has been indirectly located by both an ILM and DLM, and there may be anexclusive ILM region 1028 containing at least one ILM that has been indirectly located by all ILMs. The further in distance the LN-Expanse has expanded fromDLM region 1022 with a substantial number of MSs, the more likely there will anexclusive ILM region 1028. NTP may be available for use in some regions, or some subset of a region, yet not available for use in others. NTP is preferably used where available to minimize communications between MSs, and an MS and service(s). An MS has the ability to make use of NTP when available. - With reference now to
FIG. 10H , all MSs depicted know their own locations. The upper left-hand portion of the illustration consists ofregion 1022. As the reader glances more toward the rightmost bottom portion of the illustration, there can beregions 1024 andregions 1026 in the middle of the illustration. At the very rightmost bottom portion of the illustration, remaining ILMs fall inregion 1028. An ILM is indirectly located relative all DLMs, DLMs and ILMs, or all ILMs. An “Affirmifier” in a LN-expanse confidently knows its own location and can serve as a reference MS for other MSs. An affirmifier is said to “affirmify” when in the act of serving as a reference point to other MSs. A “Pacifier” can contribute to locating other systems, but with a low confidence of its own whereabouts. The LN-Expanse is a network of located/locatable MSs, and is preferably expanded by a substantial number of affirmifiers. -
FIG. 10I depicts an illustration of a Locatable Network expanse (LN-Expanse) for describing a supervisory service, for examplesupervisory service 1050. References in flowcharts for communicating information to a supervisory service can refer to communicating information to supervisory service 1050 (e.g. blocks 294 and 296 from parameters passed to block 272 for many processing flows). The only requirement is thatsupervisory service 1050 be contactable from an MS (DLM or ILM) that reports to it. An MS reporting toservice 1050 can communicate directly to it, through another MS (i.e. a single hop), or through a plurality of MSs (i.e. a plurality of hops). Networks of MSs can be preconfigured, or dynamically reconfigured as MSs travel to minimize the number of hops between a reporting MS andservice 1050. A purely peer to peer preferred embodiment includes a peer to peer network of located/locatable MSs that interact with each other as described herein. The purely peer to peer preferred embodiment may have no need to include aservice 1050. Nevertheless, a supervisory service may be warranted to provide certain processing centralization, or for keeping information associated with MSs. In some embodiments,supervisory service 1050 includes at least one database to house data (e.g. data 8;data 20;data 36;data 38,queue data -
FIG. 11A depicts a preferred embodiment of a Whereabouts Data Record (WDR) 1100 for discussing operations of the present disclosure. A WDR takes on a variety of formats depending on the context of use. There are several parts to a WDR depending on use. There is an identity section which contains aMS ID field 1100 a for identifying the WDR.Field 1100 a can contain a null value if the WDR is for whereabouts information received from a remote source which has not identified itself. MSs do not require identities of remote data processing systems in order to be located. There is a core section which is required in WDR uses. The core section includes date/time stamp field 1100 b,location field 1100 c, and confidence field 1100 d. There is a transport section of fields wherein any one of the fields may be used when communicating WDR information between data processing systems. Transport fields includecorrelation field 1100 m, sent date/time stamp field 1100 n, and received date/time stamp field 1100 p. Transport fields may also be communicated to send processing (e.g. queue 24), or received from receive processing (e.g. queue 26). Other fields are of use depending on the MS or applications thereof, however location technology field 1100 e and locationreference info field 1100 f are of particular interest in carrying out additional novel functionality of the present disclosure. Communications referenceinformation field 1100 g may be valuable, depending on communications embodiments in the LN-expanse. - Some fields are multi-part fields (i.e. have sub-fields). Whereabouts Data Records (WDRs) 1100 may be fixed length records, varying length records, or a combination with field(s) in one form or the other. Some WDR embodiments will use anticipated fixed length record positions for subfields that can contain useful data, or a null value (e.g. −1). Other WDR embodiments may use varying length fields depending on the number of sub-fields to be populated. Other WDR embodiments will use varying length fields and/or sub-fields which have tags indicating their presence. Other WDR embodiments will define additional fields to prevent putting more than one accessible data item in one field. In any case, processing will have means for knowing whether a value is present or not, and for which field (or sub-field) it is present. Absence in data may be indicated with a null indicator (−1), or indicated with its lack of being there (e.g. varying length record embodiments).
- When a WDR is referenced in this disclosure, it is referenced in a general sense so that the contextually reasonable subset of the WDR of
FIG. 11A is used. For example, when communicating WDRs (sending/receivingdata 1302 or 1312) between data processing systems, a reasonable subset ofWDR 1100 is communicated in preferred embodiments as described with flowcharts. When a WDR is maintained to queue 22, preferably most (if not all) fields are set for a complete record, regardless if useful data is found in a particular field (e.g. some fields may be null (e.g. −1)). Most importantly, Whereabouts Data Records (WDRs) are maintained to queue 22 for maintaining whereabouts of the MS which ownsqueue 22. LBX is most effective the more timely (and continuous) a MS has valid whereabouts locally maintained. WDRs are designed for maintaining whereabouts information independent of any location technology applied. Over time, a MS may encounter a plurality of location technologies used to locate it. WDRs maintained to afirst MS queue 22 have the following purpose: -
- 1) Maintain timely DLM whereabouts information of the first MS independent of any location technology applied;
- 2) Maintain whereabouts information of nearby MSs independent of any location technology applied;
- 3) Provide DLM whereabouts information to nearby MSs for determining their own locations (e.g. provide whereabouts information to at least a second MS for determining its own location);
- 4) Maintain timely ILM whereabouts information of the first MS independent of any location technology applied; and
- 5) Provide ILM whereabouts information to nearby MSs so they can determine their own locations (e.g. first MS providing whereabouts information to at least a second MS for the second MS determining its own whereabouts).
- A MS may go in and out of DLM or ILM roles as it is mobile. Direct location methods are not always available to the MS as it roams, therefore the MS preferably does all of 1 through 5 above. When the
WDR 1100 contains aMS ID field 1100 a matching the MS which ownsqueue 22, that WDR contains the location (location field 1100 c) with a specified confidence (field 1100 d) at a particular time (date/time stamp field 1100 b) for that MS. Preferably theMS ID field 1100 a, date/time stamp field 1100 b and confidence field 1100 d is all that is required for searching from thequeue 22 the best possible, and most timely, MS whereabouts at the time of searchingqueue 22. Other embodiments may consult any other fields to facilitate the best possible MS location at the time of searching and/orprocessing queue 22. TheWDR queue 22 also maintains affirmifier WDRs, and acceptable confidence pacifier WDRs (block 276), which are used to calculate a WDR having matchingMS field 1100 a so the MS knows its whereabouts via indirect location methods. Affirmifier and pacifier WDRs haveMS ID field 1100 a values which do not match theMS owning queue 22. This distinguishes WDRs ofqueue 22 for A) accessing the current MS location; from B) the WDRs from other MSs. All WDR fields of affirmifier and pacifier originated WDRs are of importance for determining a best location of the MS which ownsqueue 22, and in providing LBX functionality. -
MS ID field 1100 a is a unique handle to an MS as previously described. Depending on the installation,MS ID field 1100 a may be a phone #, physical or logical address, name, machine identifier, serial number, encrypted identifier, concealable derivative of a MS identifier, correlation, pseudo MS ID, or some other unique handle to the MS. An MS must be able to distinguish its own unique handle from other MS handles infield 1100 a. For indirect location functionality disclosed herein, affirmifier and pacifier WDRs do not need to have a correct originatingMS ID field 1100 a. The MS ID may be null, or anything to distinguish WDRs for MS locations. However, to accomplish other LBX features and functionality, MS Identifiers (MS IDs) of nearby MSs (or unique correlations thereof) maintained inqueue 22 are to be known for processing by an MS.MS ID field 1100 a may contain a group identifier of MSs in some embodiments for distinguishing between types of MSs (e.g. to be treated the same, or targeted with communications, as a group), as long as theMS containing queue 22 can distinguish its own originatedWDRs 1100. A defaulted value may also be set for a “do not care” setting (e.g. null). - Date/
Time stamp field 1100 b contains a date/time stamp of when theWDR record 1100 was completed by an MS for its own whereabouts prior to WDR queue insertion. It is in terms of the date/time scale of the MS inserting the local WDR (NTP derived or not). Date/Time stamp field 1100 b may also contain a date/time stamp of when theWDR record 1100 was determined for the whereabouts of an affirmifier orpacifier originating record 1100 to help an MS determine its own whereabouts, but it should still be in terms of the date/time scale of the MS inserting the local WDR (NTP derived or not) to prevent time conversions when needed, and to promoteconsistent queue 22 searches/sorts/etc. The date/time stamp field 1100 b should use the best possible granulation of time, and may be in synch with other MSs and data processing systems according to NTP. A time zone, day/light savings time, and NTP indicator is preferably maintained as part offield 1100 b. The NTP indicator (e.g. bit) is for whether or not the date/time stamp is NTP derived (e.g. the NTP use setting is checked for setting this bit when completing the WDR forqueue 22 insertion). In some embodiments, date/time stamp field 1100 b is measured in the same granulation of time units to an atomic clock available to MSs of an LN-Expanse 1002. When NTP is used in a LN-Expanse, identical time server sources are not a requirement provided NTP derived date/time stamps have similar accuracy and dependability. -
Location field 1100 c depends on the installation of the present disclosure, but can include a latitude and longitude, cellular network cell identifier, geocentric coordinates, geodetic coordinates, three dimensional space coordinates, area described by GPS coordinates, overlay grid region identifier or coordinates, GPS descriptors, altitude/elevation (e.g. in lieu of using field 1100 j), MAPSCO reference, physical or logical network address (including a wildcard (e.g. ip addresses 145.32.*.*)), particular address, polar coordinates, or any other two/three dimensional location methods/means used in identifying the MS location. Data offield 1100 c is preferably a consistent measure (e.g. all latitude and longitude) for all location technologies that populateWDR queue 22. Some embodiments will permit using different measures tolocation field 1100 c (e.g. latitude and longitude for one, address for another; polar coordinates for another, etc) which will be translated to a consistent measure at appropriate processing times. - Confidence field 1100 d contains a value for the confidence that
location field 1100 c accurately describes the location of the MS when the WDR is originated by the MS for its own whereabouts. Confidence field 1100 d contains a value for the confidence thatlocation field 1100 c accurately describes the location of an affirmifier or pacifier that originated the WDR. A confidence value can be set according to known timeliness of processing, communications and known mobile variables (e.g. MS speed, heading, yaw, pitch, roll, etc) at the time of transmission. Confidence values should be standardized for all location technologies used to determine which location information is of a higher/lower confidence when using multiple location technologies (as determined byfields 1100 e and 1100 f) for enabling determination of which data is of a higher priority to use in determining whereabouts. Confidence value ranges depend on the implementation. In a preferred embodiment, confidence values range from 1 to 100 (as discussed previously) for denoting a percentage of confidence. 100% confidence indicates thelocation field 1100 c is guaranteed to describe the MS location. 0% confidence indicates thelocation field 1100 c is guaranteed to not describe the MS location. Therefore, the lowest conceivable value of aqueue 22 for field 1100 d should be 1. Preferably, there is a lowest acceptable confidence floor value configured (by system, administrator, or user) as used at points of queue entry insertion—seeblock 276 to prevent frivolous data to queue 22. In most cases, WDRs 1100 contain a confidence field 1100 d up to 100. In confidence value preferred embodiments, pacifiers know their location with a confidence of less than 75, and affirmifiers know their location with a confidence value 75 or greater. The confidence field is skewed to lower values as the LN-expanse 1002 is expanded further fromregion 1022. Confidence values are typically lower when ILMs are used to locate a first set of ILMs (i.e. first tier), and are then lower when the first set of ILMs are used to locate a second set of ILMs (second tier), and then lower again when the second set of ILMs are used to locate a third set of ILMs (third tier), and so on. Often, examination of a confidence value in aWDR 1100 can indicate whether the MS is a DLM, or an ILM far away from DLMs, or an MS which has been located using accurate (high confidence) or inaccurate (low confidence) locating techniques. - Location Technology field 1100 e contains the location technology used to determine the location of
location field 1100 c. An MS can be located by many technologies. Location Technology field 1100 e can contain a value from a row ofFIG. 9A or any other location technology used to locate a MS. WDRs inserted to queue 22 for MS whereabouts set field 1100 e to the technology used to locate the MS. WDRs inserted to queue 22 for facilitating a MS in determining whereabouts set field 1100 e to the technology used to locate the affirmifier or pacifier. Field 1100 e also contains an originator indicator (e.g. bit) for whether the originator of theWDR 1100 was a DLM or ILM. When received from a service that has not provided confidence, this field may be used by a DLM to determine confidence field 1100 d. - Location
Reference Info field 1100 f preferably contains one or more fields useful to locate a MS in processing subsequent of having been inserted toqueue 22. In other embodiments, it contains data that contributed to confidence determination. LocationReference Info field 1100 f may contain information (TDOA measurement and/or AOA measurement—see insertedfield 1100 f forFIGS. 2D , 2E and 3C) useful to locate a MS in the future when the WDR originated from the MS for its own whereabouts.Field 1100 f will contain selected triangulation measurements, wave spectrum used and/or particular communications interfaces 70, signal strength(s), TDOA information, AOA information, or any other data useful for location determination.Field 1100 f can also contain reference whereabouts information (FIG. 3C ) to use relative a TDOA or AOA (otherwise WDR location field assumed as reference). In one embodiment,field 1100 f contains the number of DLMs and ILMs which contributed to calculating the MS location to break a tie between using WDRs with the same confidence values. In another embodiment, a tier of ILMs used to locate the MS is maintained so there is an accounting for the number of ILMs in the LN-expanse between the currently located MS and a DLM. In other embodiments, MS heading, yaw, pitch and roll, or accelerometer values are maintained therein, for example for antenna AOA positioning. When wave spectrum frequencies or other wave characteristics have changed in a transmission used for calculating a TDOA measurement, appropriate information may be carried along, for example to properly convert a time into a distance.Field 1100 f should be used to facilitate correct measurements and uses, if needed conversions have not already taken place. - Communications reference
information field 1100 g is a multipart record describing the communications session, channel, and bind criteria between the MS and MSs, or service(s), that helped determine its location. In some embodiments,field 1100 g contains unique MS identifiers, protocol used, logon/access parameters, and useful statistics of the MSs which contributed to data of thelocation field 1100 c. An MS may usefield 1100 g for WDRs originated from affirmifiers and pacifiers for subsequent LBX processing. -
Speed field 1100 h contains a value for the MS speed when the WDR is originated by the MS for its own whereabouts. Speed field 1100 d may contain a value for speed of an affirmifier or pacifier when the WDR was originated elsewhere. Speed is maintained in any suitable units. - Heading field 1100 i contains a value for the MS heading when the WDR is originated by the MS for its own whereabouts. Heading field 1100 i may contain a value for heading of an affirmifier or pacifier when the WDR was originated elsewhere. Heading values are preferably maintained in degrees up to 360 from due North, but is maintained in any suitable directional form.
- Elevation field 1100 j contains a value for the MS elevation (or altitude) when the WDR is originated by the MS for its own whereabouts. Elevation field 1100 j may contain a value for elevation (altitude) of an affirmifier or pacifier when the WDR was originated elsewhere. Elevation (or altitude) is maintained in any suitable units.
-
Application fields 1100 k contains one or more fields for describing application(s) at the time of completing, or originating, theWDR 1100.Application fields 1100 k may include field(s) for: -
- a) MS Application(s) in use at time;
- b) MS Application(s) context(s) in use at time;
- c) MS Application(s) data for state information of MS Application(s) in use at time;
- d) MS Application which caused
WDR 1100; - e) MS Application context which caused
WDR 1100; - f) MS Application data for state information of MS Application which caused
WDR 1100; - g) Application(s) in use at time of remote MS(s) involved with WDR;
- h) Application(s) context(s) in use at time of remote MS(s) involved with WDR;
- i) MS Application(s) data for state information of remote MS(s) involved with WDR;
- j) Remote MS(s) criteria which caused
WDR 1100; - k) Remote MS(s) context criteria which caused
WDR 1100; - l) Remote MS(s) data criteria which caused
WDR 1100; - m) Application(s) in use at time of service(s) involved with WDR;
- n) Application(s) context(s) in use at time of service(s) involved with WDR;
- o) MS Application(s) data for state information of service(s) involved with WDR;
- p) Service(s) criteria which caused
WDR 1100; - q) Service(s) context criteria which caused
WDR 1100; - r) Service(s) data criteria which caused
WDR 1100; - s) MS navigation APIs in use;
- t) Web site identifying information;
- u) Physical or logical address identifying information;
- v) Situational location information as described in U.S. Pat. Nos. 6,456,234; 6,731,238; 7,187,997 (Johnson);
- w) Transactions completed at a MS;
- x) User configurations made at a MS;
- y) Environmental conditions of a MS;
- z) Application(s) conditions of a MS;
- aa) Service(s) conditions of a MS;
- bb) Date/time stamps (like
field 1100 b) with, or for, any item of a) through aa); and/or - cc) Any combinations of a) through bb).
-
Correlation field 1100 m is optionally present in a WDR when the WDR is in a transmission between systems (e.g. wireless communications) such as indata Field 1100 m provides means for correlating a response to an earlier request, or to correlate a response to an earlier broadcast.Correlation field 1100 m contains a unique handle. In a LN-expanse which globally uses NTP, there is no need for correlation indata Correlation field 1100 m may be present in WDRs ofqueues - Sent date/
time stamp field 1100 n is optionally present in a WDR when the WDR is in transmission between systems (e.g. wireless communications) such as indata Field 1100 n contains when the WDR was transmitted. A time zone, day/light savings time, and NTP indicator is preferably maintained as part offield 1100 n.Field 1100 n is preferably not present in WDRs of queue 22 (but can be if TDOA measurement calculation is delayed to a later time). In some embodiments, there is no need forfield 1100 n. Whereabouts determined for MSs of an LN-Expanse may be reasonably timely, facilitating simplicity of settingoutbound field 1100 b to the transmission date/time stamp at the sending data processing system, rather than when the WDR was originally completed for whereabouts (e.g. when substantially the same time anyway). Sent date/time field 1100 n may be present in WDRs ofqueues - Received date/
time stamp field 1100 p is preferably present in a WDR when inserted to queue 26 by receiving thread(s) upon receiveddata Field 1100 p contains when the WDR was received by the MS. A time zone, day/light savings time, and NTP indicator is preferably maintained as part offield 1100 p.Field 1100 p is preferably not present in WDRs of queue 22 (but can be if TDOA measurement calculation is delayed to a later time). In some embodiments, there is no need forfield 1100 p. For example, thread(s) 1912 may be listening directly on applicable channel(s) and can determine when the data is received. In another embodiment, thread(s) 1912 process fast enough to determine the date/time stamp of whendata time stamp field 1100 p is preferably added to records placed to queue 26 by receiving thread(s) feedingqueue 26. - Any fields of
WDR 1100 which contain an unpredictable number of subordinate fields of data preferably use a tagged data scheme, for example an X.409 encoding for a Token, Length, and Value (called a TLV encoding). Therefore, aWDR 1100, or field therein, can be a variable sized record. For example, LocationReference info field 1100 f may contain TTA, 8, 0.1456 where the Token=“TTA” for Time Till Arrival (TDOA measurement between when sent and when received), Length=8 for 8 bytes to follow, and Value=0.1456 in time units contained within the 8 bytes; also SS, 4, 50 where Token=“Signal Strength”, 4=4 for 4 bytes to follow, and Value=50 dBu for the signal strength measurement. This allows on-the-fly parsing of unpredictable, but interpretable, multipart fields. The TLV encoding also enables-on-the-fly configuration for parsing new subordinate fields to anyWDR 1100 field in a generic implementation, for example in providing parse rules to a Lex and Yacc implementation, or providing parse rules to a generic top down recursive TLV encoding parser and processor. - Any field of
WDR 1100 may be converted: a) prior to insertion to queue 22; or b) after access toqueue 22; or c) byqueue 22 interface processing; for standardized processing. Any field ofWDR 1100 may be converted when sending/receiving/broadcasting, or related processing, to ensure a standard format. Other embodiments will store and access values ofWDR 1100 field(s) which are already in a standardized format.WDR 1100 fields can be in any order, and a different order when comparing what is in data transmitted versus data maintained to queue 22. - An alternate embodiment to WDRs maintained to queue 22 preserves
transport fields queue 22. This would enable 1952 thread(s) to perform TDOA measurements that are otherwise calculated in advance and kept infield 1100 f. However,queue 22 size should be minimized and the preferred embodiment uses transport fields when appropriate to avoid carrying them along to other processing. -
FIGS. 11B , 11C and 11D depict an illustration for describing various embodiments for determining the whereabouts of an MS, for example anILM 1000 e. With reference now toFIG. 11B , aMS 1000 e location is located by using locations of three (3) other MSs: MS4, MS5, and MS6 (referred to generally as MSj). MSj are preferably located with a reasonably high level of confidence. In some embodiments, MSj are all DLMs. In some embodiments, MSj are all ILMs. In some embodiments, MSj are mixed DLMs and ILMs. Any of the MSs may be mobile during locating ofMS 1000 e. Wave spectrums in use, rates of data communications and MS processing speed, along with timeliness of processing described below, provide timely calculations for providing whereabouts ofILM 1000 e with a high level of confidence. The most confident MSs (MSj) were used to determine theMS 1000 e whereabouts. For example, MSj were all located using a form of GPS, which in turn was used to triangulate the whereabouts ofMS 1000 e. In another example, MS4 was located by a form of triangulation technology, MS5 was located by a form of “coming into range” technology, and MS6 was located by either of the previous two, or some other location technology. It is not important how an MS is located. It is important that each MS know its own whereabouts and maintain a reasonable confidence to it, so that other MSs seeking to be located can be located relative highest confidence locations available. TheWDR queue 22 should always contain at least one entry indicating the location of theMS 2 which ownsWDR queue 22. If there are no entries contained onWDR queue 22, theMS 2 does not know its own location. - With reference now to
FIG. 11C , a triangulation ofMS 1000 e atlocation 1102 is explained using location (whereabouts) 1106 of MS4, location (whereabouts) 1110 of MS5, and location (whereabouts) 1114 of MS6. Signal transmission distance from MSj locations are represented by the radiuses, with r1 the TDOA measurement (time difference between when sent and when received) between MS4 andMS 1000 e, with r2 the TDOA measurement (time difference between when sent and when received) between MS5 andMS 1000 e, with r3 the TDOA measurement (time difference between when sent and when received) between MS6 andMS 1000 e. In this example, the known locations of MSj which are used to determine the location ofMS 1000 e allow triangulating theMS 1000 e whereabouts using the TDOA measurements. In fact, less triangular data in the illustration can be necessary for determining a highly confident whereabouts ofMS 1000 e. - With reference now to
FIG. 11D , a triangulation ofMS 1000 e atlocation 1102 is explained using location (whereabouts) 1106 of MS4, location (whereabouts) 1110 of MS5, and location (whereabouts) 1114 of MS6. In some embodiments, AOA measurements taken at a positioned antenna ofMS 1000 e atlocation 1102 are used relative thewhereabouts 1106,whereabouts 1110, whereabouts 1114 (AOA 1140, AOA 1144 and AOA 1142), wherein AOA measurements are detected for incoming signals during known values for MS heading 1138 with MS yaw, pitch, and roll (or accelerometer readings). AOA triangulation is well known in the art.Line segment 1132 represents the direction of signal arrival to the antenna atwhereabouts 1102 from MS4 atwhereabouts 1106.Line segment 1134 represents the direction of signal arrival to the antenna atwhereabouts 1102 from MS5 atwhereabouts 1110.Line segment 1136 represents the direction of signal arrival to the antenna atwhereabouts 1102 from MS6 atwhereabouts 1114. In this example, the known locations of MSj which are used to determine the location ofMS 1000 e allow triangulating theMS 1000 e whereabouts using the AOA measurements. In fact, less triangular data in the illustration can be necessary for determining a highly confident whereabouts ofMS 1000 e. Alternative embodiments will use AOA measurements of outbound signals from the MS atwhereabouts 1102 detected at antennas ofwhereabouts 1106 and/or 1110 and/or 1114. -
FIGS. 11C and 11D illustrations can be used in a complementary manner when only one or two TDOA measurements are available and/or not all stationary locations, or MS reference locations, are known at the time of calculation. Another example is when only one or two AOA angles is available and/or not all stationary locations, or MS reference locations, are known at the time of calculation. However, using what is available from each technology in conjunction with each other allows solving the MS whereabouts (e.g. blocks 952/954 processing above). MPT is one example of solving for missing parts using more than one location technology. Condition of data known for locating a MS (e.g. whereabouts -
- 1) AAS=two angles and a side;
- 2) ASA=two angles and a common side;
- 3) SAS=two sides and the included angle; or
- 4) SSA=two sides and a non-included angle.
TDOA measurements are distances (e.g. time difference between when sent and when received), and AOA measurements are angles. Each of the four conditions are recognized (e.g. block 952 above), and data is passed for each of the four conditions for processing (e.g. block 954 above). For AAS (#1) and ASA (#2), processing (e.g. block 954) finds the third angle by subtracting the sum of the two known angles from 180 degrees (i.e. using mathematical law that triangles' interior angles add up to 180 degrees), and uses the mathematical law of Sines (i.e. a/sin A=b/sin B=c/sin C) twice to find the second and third sides after plugging in the knowns and solving for the unknowns. For SAS (#3), processing (e.g. block 954) uses the mathematical law of Cosines (i.e. a2=b2+c2−2bc cos A) to find the third side, and uses the mathematical law of Sines (sin A/a=sin B/b=sin C/c (derived from law of Sines above)) to find the second angle. For SSA (#4), processing (e.g. block 954) uses the mathematical law of Sines (i.e. (sin A/a=sin B/b=sin C/c) twice to get the second angle, and mathematical law of Sines (a/sin A=b/sin B=c/sin C) to get the third side. Those skilled in the art recognize other useful trigonometric functions and formulas, and similar uses of the same trigonometric functions, for MPT depending on what data is known. The data discovered and processed depends on an embodiment, what reference locations are available, and which parts are missing for MPT. MPT uses different distances (time used to determine length in TDOA) and/or angles (from AOA or TDOA technologies) for deducing a MS location confidently (e.g. MPT). Those skilled in the art recognize that having known reference locations facilitates requiring less triangular information for deducing a MS location confidently. MPT embodiments may exist for any aforementioned wave spectrums.
-
FIG. 11E depicts an illustration for describing various embodiments for automatically determining the location of an MS. An MS can be located relative other MSs which were located using any of a variety of location technologies, for example any of those ofFIG. 9A . An MS is heterogeneously located when one of the following conditions are met: -
- More than one location technology is used during travel of the MS;
- More than one location technology is used to determine a single whereabouts of the MS;
- MPT is used to locate the MS; and/or
- ADLT is used to locate the MS.
TheWDR queue 22 and interactions between MSs as described below cause the MS to be heterogeneously located without special consideration to any particular location technology. WhileWDR 1100 contains field 1100 e, field 1100 d provides a standard and generic measurement for evaluating WDRs from different location technologies, without concern for the location technology used. The highest confidence entries to aWDR queue 22 are used regardless of which location technology contributed to theWDR queue 22.
-
FIG. 12 depicts a flowchart for describing an embodiment of MS initialization processing. Depending on the MS, there are many embodiments of processing when the MS is powered on, started, restarted, rebooted, activated, enabled, or the like.FIG. 12 describes the blocks of processing relevant to the present disclosure as part of that initialization processing. It is recommended to first understand discussions ofFIG. 19 for knowing threads involved, and variables thereof. Initialization processing starts atblock 1202 and continues to block 1204 where the MS Basic Input Output System (BIOS) is initialized appropriately, then to block 1206 whereother character 32 processing is initialized, and then to block 1208 to see if NTP is enabled for this MS.Block 1206 may start the preferred number of listen/receive threads for feedingqueue 26 and the preferred number of send threads for sending data inserted to queue 24, in particular when transmittingCK 1304 embedded inusual data 1302 and receivingCK usual data other character 32 threads are appropriately altered for embedded CK processing (sending at first opportune outbound transmission; receiving in usual inbound transmission). - If
block 1208 determines NTP is enabled (as defaulted or last set by a user (i.e. persistent variable)), then block 1210 initializes NTP appropriately and processing continues to block 1212. Ifblock 1208 determines NTP was not enabled, then processing continues to block 1212.Block 1210 embodiments are well known in the art of NTP implementations (also see block 1626).Block 1210 may cause the starting of thread(s) associated with NTP. In some embodiments, NTP use is assumed in the MS. In other embodiments, appropriate NTP use is not available to the MS. Depending on the NTP embodiment, thread(s) may pull time synchronization information, or may listen for and receive pushed time information. Resources 38 (or other MS local resource) provides interface to an MS clock for referencing, maintaining, and generating date/time stamps at the MS. Afterblock 1210 processing, the MS clock is synchronized to NTP. Because of initialization of the MS inFIG. 12 ,block 1210 may rely on a connected service to initially get the startup synchronized NTP date/time. MS NTP processing will ensure the NTP enabled/disabled variable is dynamically set as is appropriate (using semaphore access) because an MS may not have continuous clock source access during travel when needed for resynchronization. If the MS does not have access to a clock source when needed, the NTP use variable is disabled. When the MS has (or again gets) access to a needed clock source, then the NTP use variable is enabled. - Thereafter,
block 1212 creates shared memory to maintain data shared between processes/threads, block 1214 initializes persistent data to shared memory, block 1216 initializes any non-persistent data to shared memory (e.g. some statistics 14),block 1218 creates system queues, andblock 1220 creates semaphore(s) used to ensure synchronous access by concurrent threads to data in shared memory, before continuing to block 1222. Shared memory data accesses appropriately utilize semaphore lock windows (semaphore(s) created at block 1220) for proper access. In one embodiment,block 1220 creates a single semaphore for all shared memory accesses, but this can deteriorate performance of threads accessing unrelated data. In the preferred embodiment, there is a semaphore for each reasonable set of data of shared memory so all threads are fully executing whenever possible. Persistent data is that data which maintains values during no power, for example as stored topersistent storage 60. This may include data 8 (includingpermissions 10,charters 12,statistics 14, service directory 16),data 20,LBX history 30,data 36,resources 38, and/or other data. Persistent data preferably includes at least the DLMV (see DLM role(s) list Variable below), ILMV (see ILM role(s) list Variable below), process variables 19 xx-Max values (19 xx=1902, 1912, 1922, 1932, 1942 and 1952 (seeFIG. 19 discussions below)) for the last configured maximum number of threads to run in the respective process, process variables 19 xx-PID values (19 xx=1902, 1912, 1922, 1932, 1942 and 1952 (seeFIG. 19 discussions below)) for multi-purpose of: a) holding an Operating System Process Identifier (i.e. O/S PID) for a process started; and b) whether or not the respective process was last enabled (i.e. PID>0) or disabled (i.e. PID<=0), the confidence floor value (seeFIG. 14A ), the WTV (see Whereabouts Timeliness Variable (see FIG. 14A)), the NTP use variable (seeFIG. 14A ) for whether or not NTP was last set to disabled or enabled (used at block 1208), and the Source Periodicity Time Period (SPTP) value (seeFIG. 14B ). There are reasonable defaults for each of the persistent data prior to the first use of MS 2 (e.g. NTP use is disabled, and only becomes enabled upon a successful enabling of NTP at least one time). Non-persistent data may include data involved in some regard to data 8 (and subsets ofpermissions 10,charters 12,statistics 14, service directory 16),data 20,LBX history 30,data 36,resources 38, queues, semaphores, etc.Block 1218 createsqueues Queues Queues - All queues disclosed herein are understood to have their own internally maintained semaphore for queue accesses so that queue insertion, peeking, accessing, etc uses the internally maintained semaphore to ensure two or more concurrently executing threads do not corrupt or misuse data to any queue. This is consistent with most operating system queue interfaces wherein a thread stays blocked (preempted) after requesting a queue entry until a queue entry appears in the queue. Also, no threads will collide with another thread when inserting, peeking, or otherwise accessing the same queue. Therefore, queues are implicitly semaphore protected. Other embodiments may use an explicit semaphore protected window around queue data accessing, in which case those semaphore(s) are created at
block 1220. - Thereafter, block 1222 checks for any ILM roles currently enabled for the MS (for example as determined from persistent storage of an ILM role(s) list Variable (ILMV) preferably preconfigured for the MS at first use, or configured as last configured by a user of the MS). ILM roles are maintained to the ILM role(s) list Variable (ILMV). The ILMV contains one or more entries for an ILM capability (role), each entry with a flag indicating whether it is enabled or disabled (marked=enabled, unmarked=disabled). If
block 1222 determines there is at least one ILM role enabled (i.e. as marked by associated flag), then block 1224 artificially sets the corresponding 19 xx-PID variables to a value greater than 0 for indicating the process(es) are enabled, and are to be started by subsequentFIG. 12 initialization processing. The 19 xx-PID will be replaced with the correct Process Identifier (PID) upon exit fromblock 1232 after the process is started. Preferably, every MS can have ILM capability. However, a user may want to (configure) ensure a DLM has no ILM capability enabled (e.g. or having no list present). In some embodiments, by default, every MS has an unmarked list of ILM capability maintained to the ILMV for 1) USE DLM REFERENCES and 2) USE ILM REFERENCES. USE DLM REFERENCES, when enabled (marked) in the ILMV, indicates to allow the MS ofFIG. 12 processing to determine its whereabouts relative remote DLMs. USE ILM REFERENCES, when enabled (marked) in the ILMV, indicates to allow the MS ofFIG. 12 processing to determine its whereabouts relative remote ILMs. Having both list items marked indicates to allow determining MS whereabouts relative mixed DLMs and ILMs. An alternative embodiment may include a USE MIXED REFERENCES option for controlling the MS ofFIG. 12 processing to determine its whereabouts relative mixed DLMs and/or ILMs. Alternative embodiments will enforce any subset of these options without exposing user configurations, for example on a MS without any means for being directly located. - For any of the ILMV roles of USE DLM REFERENCES, USE ILM REFERENCES, or both, all
processes process 1912 started. Block 1224 continues to block 1226. Ifblock 1222 determines there are no ILMV role(s) enabled, then block processing continues to block 1226. -
Block 1226 initializes an enumerated process name array for convenient processing reference of associated process specific variables described inFIG. 19 , and continues to block 1228 where the first member of the set is accessed for subsequent processing. The enumerated set of process names has a prescribed start order forMS architecture 1900. Thereafter, ifblock 1230 determines the process identifier (i.e. 19 xx-PID such that 19 xx is 1902, 1912, 1922, 1932, 1942, 1952 in a loop iteration ofblocks 1228 through 1234) is greater than 0 (e.g. this first iteration of 1952-PID>0 implies it is to be started here; also impliesprocess 1952 is enabled as used inFIGS. 14A , 28, 29A and 29B), then block 1232 spawns (starts) the process (e.g. 1952) ofFIG. 29A to start execution of subordinate worker thread(s) (e.g. process 1952 thread(s)) and saves the real PID (Process Identifier) to the PID variable (e.g. 1952-PID) returned by the operating system process spawn interface.Block 1232 passes as a parameter to the process ofFIG. 29A which process name to start (e.g. 1952), and continues to block 1234. Ifblock 1230 determines the current process PID variable (e.g. 1952-PID) is not greater than 0 (i.e. not to be started; also implies is disabled as used inFIGS. 14A , 28, 29A and 29B), then processing continues to block 1234.Block 1234 checks to see if all process names of the enumerated set (pattern of 19 xx) have been processed (iterated) byblocks 1228 through 1234. Ifblock 1234 determines that not all process names in the set have been processed (iterated), then processing continues back to block 1228 for handling the next process name in the set. Ifblock 1234 determines that all process names of the enumerated set were processed, then block 1236 checks the DLMV (DLM role(s) list Variable).Blocks 1228 through 1234 iterate every process name ofFIG. 19 to make sure that each is started in accordance with non-zero 19 xx-PID variable values atFIG. 12 initialization.Block 1236 checks for any DLM roles currently enabled for the MS (for example as determined from persistent storage of a DLM role(s) list Variable (DLMV) preferably preconfigured for the MS at first use if the MS contains DLM capability). DLM capability (roles), whether on-board at the MS, or determined during MS travels (see block 288), is maintained to the DLM role(s) list Variable (DLMV). The DLMV contains one or more entries for a DLM capability (role), each (role) entry with a flag indicating whether it is enabled or disabled (marked=enabled, unmarked=disabled). Ifblock 1236 determines there is at least one DLM role enabled (i.e. as marked by associated flag), then block 1238 initializes enabled role(s) appropriately and processing continues to block 1240.Block 1238 may cause the starting of thread(s) associated with enabled DLM role(s), for DLM processing above (e.g.FIGS. 2A through 9B ).Block 1238 may invoke API(s), enable flag(s), or initialize as is appropriate for DLM processing described above. Such initializations are well known in the art of prior art DLM capabilities described above. Ifblock 1236 determines there are no DLM roles to initialize at the MS, then processing continues to block 1240. Any of theFIG. 9A technologies are eligible in the DLMV as determined to be present at the MS and/or as determined by historical contents of the WDR queue 22 (e.g. location technology field 1100 e withMS ID field 1100 a for this MS) and/or determined byLBX history 30. Application Programming Interfaces (APIs) may also be used to determine MS DLM capability (role(s)) for entry(s) to the DLMV. - Block 1240 completes LBX character initialization, and
FIG. 12 initialization processing terminates thereafter atblock 1242. Depending on what threads were started as part ofblock 1206, Block 1240 may startup the preferred number of listen/receive threads for feedingqueue 26 and the preferred number of send threads for sending data inserted to queue 24, in particular when transmittingnew data 1302 and receivingnew data block 1242, the MS is appropriately operational, and a user at the MS ofFIG. 12 processing will have the ability to use the MS and applicable user interfaces thereof. - With reference now to
FIG. 29A , depicted is a flowchart for describing a preferred embodiment of a process for starting a specified number of threads in a specified thread pool.FIG. 29A is in itself an O/S process, has a process identifier (PID) after being started, will contain at least two threads of processing after being started, and is generic in being able to take on the identity of any process name passed to it (e.g. 19 xx) with a parameter (e.g. from block 1232).FIG. 29A represents the parent thread of a 19 xx process. The FIG. 29A process is generic for executing any of processes 19 xx (i.e. 1902, 1912, 1922, 1932, 1942 and 1952) with the prescribed number of worker threads using the 19 xx-Max configuration (i.e. 1902-Max, 1912-Max, 1922-Max, 1932-Max, 1942-Max and 1952-Max).FIG. 29A will stay running until it (first all of its worker thread(s)) is terminated.FIG. 29A consists of an O/S Process 19 xx with at least a parent thread (main thread) and one worker thread (or number of worker threads forFIG. 19 processing as determined by 19 xx-Max). The parent thread has purpose to stay running while all worker threads are running, and to own intelligence for starting worker threads and terminating the process when all worker threads are terminated. The worker threads are started subordinate to theFIG. 29A process atblock 2912 using an O/S start thread interface. - A 19 xx (i.e. 1902, 1912, 1922, 1932, 1942 and 1952) process starts at
block 2902 and continues to block 2904 where the parameter passed for which process name to start (i.e. take on identity of) is determined (e.g. 1952). Thereafter,block 2906 creates a RAM semaphore (i.e. operating system term for a well performing Random Access Memory (RAM) semaphore with scope only within the process (i.e. to all threads of the process)). The local semaphore name preferably uses the process name prefix (e.g. 1952-Sem), and is used to synchronize threads within the process. RAM semaphores perform significantly better than global system semaphores. Alternate embodiments will have process semaphore(s) created atblock 1220 in advance. Thereafter,block 2908 initializes a thread counter (e.g. 1952-Ct) to 0 for counting the number of worker threads actually started within the 19 xx process (e.g. 1952), block 2910 initializes a loop variable J to 0, and block 2912 starts a worker thread (the first one upon first encounter ofblock 2912 for a process) in this process (e.g. process 1902 starts worker threadFIG. 20 , . . . ,process 1952 starts worker thread FIG. 26A—seearchitecture 1900 description below). Thereafter, block 2914 increments the loop variable by 1 and block 2916 checks if all prescribed worker threads have been started.Block 2916 accesses the 19 xx-Max (e.g. 1952-Max) variable from shared memory using a semaphore for determining the maximum number of threads to start in the process worker thread pool. Ifblock 2916 determines all worker threads have been started, then processing continues to block 2918. Ifblock 2916 determines that not all worker threads have been started for the process ofFIG. 29A , then processing continues back to block 2912 for starting the next worker thread.Blocks 2912 through 2916 ensure the 19 xx-Max (e.g. 1952-Max) number of worker threads are started within the process ofFIG. 29A . -
Block 2918 waits until all worker threads ofblocks 2912 through 2916 have been started, as indicated by the worker threads themselves.Block 2918 waits until the process 19 xx-Ct variable has been updated to the prescribed 19 xx-Max value by the started worker threads, thereby indicating they are all up and running. When all worker threads are started (e.g. 1952-Ct=1952-Max), thereafter block 2920 waits (perhaps a very long time) until the worker thread count (e.g. 1952-Ct) has been reduced back down to 0 for indicating that all worker threads have been terminated, for example when the user gracefully powers off the MS.Block 2920 continues to block 2922 when all worker threads have been terminated.Block 2922 sets the shared memory variable for the 19 xx process (e.g. 1952-PID) to 0 using a semaphore for indicating that the 19 xx (e.g. 1952) process is disabled and no longer running. Thereafter, the 19 xx process terminates atblock 2924. Waiting atblocks -
- Detect signal sent to process by last started (or terminated) worker thread that thread count is now MAX (or 0); or
- Loop on checking the thread count with sleep time between checks, wherein within the loop there is a check of the current count (use RAM semaphore to access), and processing exits the loop (and block) when the count has reached the sought value; or
- Use of a semaphore for a count variable which causes the parent thread of
FIG. 29A to stay blocked prior to the count reaching its value, and causes the parent thread to become cleared (will leave wait block) when the count reaches its sought value.
- Starting threads of processing in
FIG. 29A has been presented from a software perspective, but there are hardware/firmware thread embodiments which may be started appropriately to accomplish the same functionality. If the MS operating system does not have an interface for returning the PID atblock 1232, thenFIG. 29A can have a block (e.g. 2905) used to determine its own PID for setting the 19 xx-PID variable. -
FIGS. 13A through 13C depict an illustration of data processing system wireless data transmissions over some wave spectrum. Embodiments may exist for any of the aforementioned wave spectrums, and data carried thereon may or may not be encrypted (e.g. encrypted WDR information). With reference now toFIG. 13A , a MS, for example aDLM 200 a, sends/broadcasts data such as adata 1302 in a manner well known to those skilled in the art, for exampleother character 32 processing data. When a Communications Key (CK) 1304 is embedded withindata 1302,data 1302 is considered usual communications data (e.g. protocol, voice, or any other data over conventional forward channel, reverse channel, voice data channel, data transmission channel, or any other prior art use channel) which has been altered to containCK 1304.Data 1302 contains aCK 1304 which can be detected, parsed, and processed when received by another MS or other data processing system in the vicinity of the MS (e.g. DLM 200 a) as determined by the maximum range oftransmission 1306.CK 1304 permits “piggy-backing” on current transmissions to accomplish new functionality as disclosed herein. Transmission from the MS radiate out from it in all directions in a manner consistent with the wave spectrum used. Theradius 1308 represents a first range of signal reception from theMS 200 a, perhaps by another MS (not shown). Theradius 1310 represents a second range of signal reception from theMS 200 a, perhaps by another MS (not shown). Theradius 1311 represents a third range of signal reception from theMS 200 a, perhaps by another MS (not shown). Theradius 1306 represents a last and maximum range of signal reception from theMS 200 a, perhaps by another MS (not shown). MS design formaximum radius 1306 may take into account the desired maximum range versus acceptable wave spectrum exposure health risks for the user of the MS. The time of transmission fromMS 200 a toradius 1308 is less than times of transmission fromMS 200 a toradiuses MS 200 a toradius 1310 is less than times of transmission fromMS 200 a toradiuses MS 200 a toradius 1311 is less than time of transmission fromMS 200 a toradius 1306. - In another embodiment,
data 1302 contains a Communications Key (CK) 1304 becausedata 1302 is new transmitted data in accordance with the present disclosure.Data 1302 purpose is for carryingCK 1304 information for being detected, parsed, and processed when received by another MS or other data processing system in the vicinity of the MS (e.g. DLM 200 a) as determined by the maximum range oftransmission 1306. - With reference now to
FIG. 13B , a MS, for example anILM 1000 k, sends/broadcasts data such as adata 1302 in a manner well known to those skilled in the art.Data 1302 andCK 1304 are as described above forFIG. 13A .Data 1302 orCK 1304 can be detected, parsed, and processed when received by another MS or other data processing system in the vicinity of the MS (e.g. ILM 1000 k) as determined by the maximum range oftransmission 1306. Transmission from the MS radiate out from it in all directions in a manner consistent with the wave spectrum used, and as described above forFIG. 13A . - With reference now to
FIG. 13C , a service or set of services sends/broadcasts data such as adata packet 1312 in a manner well known to those skilled in the art, for example to serviceother character 32 processing. When a Communications Key (CK) 1314 is embedded withindata 1312,data 1312 is considered usual communications data (e.g. protocol, voice, or any other data over conventional forward channel, reverse channel, voice data channel, data transmission channel, or any other prior art use channel) which has been altered to containCK 1314.Data 1312 contains aCK 1314 which can be detected, parsed, and processed when received by an MS or other data processing system in the vicinity of the service(s) as determined by the maximum range oftransmission 1316.CK 1314 permits “piggy-backing” on current transmissions to accomplish new functionality as disclosed herein. Transmissions radiate out in all directions in a manner consistent with the wave spectrum used, and data carried thereon may or may not be encrypted (e.g. encrypted WDR information). Theradius 1318 represents a first range of signal reception from the service (e.g. antenna thereof), perhaps by a MS (not shown). Theradius 1320 represents a second range of signal reception from the service (e.g. antenna thereof), perhaps by a MS (not shown). Theradius 1322 represents a third range of signal reception from the service (e.g. antenna thereof), perhaps by a MS (not shown). Theradius 1316 represents a last and maximum range of signal reception from the service (e.g. antenna thereof), perhaps by a MS (not shown). The time of transmission from service toradius 1318 is less than times of transmission from service toradiuses radius 1320 is less than times of transmission from service toradiuses radius 1322 is less than time of transmission from service toradius 1316. In another embodiment,data 1312 contains a Communications Key (CK) 1314 becausedata 1312 is new transmitted data in accordance with the present disclosure.Data 1312 purpose is for carryingCK 1314 information for being detected, parsed, and processed when received by another MS or data processing system in the vicinity of the service(s) as determined by the maximum range of transmission. - In some embodiments,
data detectable CK 1304 and/orCK 1314, respectively. Usual data communications of MSs are altered to additionally contain the CK so data processing systems in the vicinity can detect, parse, and process the CK. Appropriate send and/or broadcast channel processing is used. In other embodiments,data CK 1304 andCK 1314, respectively. A MS may use sendqueue 24 for sending/broadcasting packets to data processing systems in the vicinity, and may use the receivequeue 26 for receiving packets from other data processing systems in the vicinity. Contents of CKs (Communications Keys) depend on which LBX features are in use and the functionality intended. - In the case of “piggybacking” on usual communications, receive
queue 26 insertion processing simply listens for the usual data and when detecting CK presence, inserts CK information appropriately to queue 26 for subsequent processing. Also in the case of “piggybacking” on usual communications, sendqueue 24 retrieval processing simply retrieves CK information from the queue and embeds it in anoutgoing data 1302 at first opportunity. In the case of new data communications, receivequeue 26 insertion processing simply listens for the new data containing CK information, and inserts CK information appropriately to queue 26 for subsequent processing. Also in the case of new data communications, sendqueue 24 retrieval processing simply retrieves CK information from the queue and transmits CK information as new data. -
FIG. 14A depicts a flowchart for describing a preferred embodiment of MS LBX configuration processing.FIG. 14 is of SelfManagement Processing code 18. MS LBX configuration begins atblock 1402 upon user action to start the user interface and continues to block 1404 where user interface objects are initialized for configurations described below with current settings that are reasonable for display to available user interface real estate. Thereafter, applicable settings are presented to the user at block 1406 with options. Block 1406 preferably presents to the user at least whether or not DLM capability is enabled (i.e. MS to behave as a DLM=at least one role of DLMV enabled), whether or not ILM capability is enabled (i.e. MS to behave as an ILM=at least one role of ILMV enabled), and/or whether or not this MS should participate in the LN-expanse as a source location for other MSs (e.g. process 1902 and/or 1942 enabled). Alternative embodiments will further present more or less information for each of the settings, or present information associated with otherFIG. 14 blocks of processing. Other embodiments will not configure DLM settings for an MS lacking DLM capability (or when all DLMV roles disabled). Other embodiments will not configure ILM settings when DLM capability is present. Block 1406 continues to block 1408 where processing waits for user action in response to options.Block 1408 continues to block 1410 when a user action is detected. Ifblock 1410 determines the user selected to configure DLM capability (i.e. DLMV role(s)), then the user configures DLM role(s) atblock 1412 and processing continues back to block 1406.Block 1412 processing is described byFIG. 15A . Ifblock 1410 determines the user did not select to configure DLM capability (i.e. DLMV role(s)), then processing continues to block 1414. Ifblock 1414 determines the user selected to configure ILM capability (i.e. ILMV role(s)), then the user configures ILM role(s) atblock 1416 and processing continues back to block 1406.Block 1416 processing is described byFIG. 15B . Ifblock 1414 determines the user did not select to configure ILM capability (i.e. ILMV role(s)), then processing continues to block 1418. Ifblock 1418 determines the user selected to configure NTP use, then the user configures NTP use atblock 1420 and processing continues back to block 1406.Block 1420 processing is described byFIG. 16 . - If
block 1418 determines the user did not select to configure NTP use, then processing continues to block 1422. - If
block 1422 determines the user selected to maintain the WDR queue, then the user maintains WDRs atblock 1424 and processing continues back to block 1406.Block 1424 processing is described byFIG. 17 .Blocks block 1422 determines the user did not select to maintain the WDR queue, then processing continues to block 1426. Ifblock 1426 determines the user selected to configure the confidence floor value, then block 1428 prepares parameters for invoking a Configure Value procedure (parameters for reference (address) of value to configure; and validity criteria of value to configure), and the Configure Value procedure ofFIG. 18 is invoked atblock 1430 with the two (2) parameters. Thereafter, processing continues back to block 1406.Blocks - The confidence floor value is the minimum acceptable confidence value of any field 1100 d (for example as checked by block 276). No WDR with a field 1100 d less than the confidence floor value should be used to describe MS whereabouts. In an alternative embodiment, the confidence floor value is enforced as the same value across an LN-expanse with no user control to modify it. One embodiment of
FIG. 14 does not permit user control over a minimum acceptable confidence floor value. Various embodiments will default the floor value.Block 1812 enforces an appropriate value in accordance with the confidence value range implemented (e.g. value from 1 to 100). Since the confidence of whereabouts is likely dependent on applications in use at the MS, the preferred embodiment is to permit user configuration of the acceptable whereabouts confidence for the MS. A new confidence floor value can be put to use at next thread(s) startup, or can be used instantly with the modification made, depending on the embodiment. The confidence floor value can be used to filter out WDRs prior to inserting to queue 22, filter out WDRs when retrieving fromqueue 22, filter out WDR information when listening on channel(s) prior to inserting to queue 26, and/or used in accessingqueue 22 for any reason (depending on embodiments). While confidence is validated on both inserts and queries (retrievals/peeks), one or the other validation is fine (preferably on inserts). It is preferred that executable code incorporate checks where applicable since the confidence floor value can be changed afterqueue 22 is in use. Also, various present disclosure embodiments may maintain all confidences to queue 22, or a particular set of acceptable confidences. - If
block 1426 determines the user did not select to configure the confidence floor value, then processing continues to block 1432. Ifblock 1432 determines the user selected to configure the Whereabouts Timeliness Variable (WTV), then block 1434 prepares parameters for invoking the Configure Value procedure (parameters for reference (address) of value to configure; and validity criteria of value to configure), and the Configure Value procedure ofFIG. 18 is invoked atblock 1430 with the two (2) parameters. Thereafter, processing continues back to block 1406.Blocks - A critical configuration for MS whereabouts processing is whereabouts timeliness. Whereabouts timeliness is how often (how timely) an MS should have accurate whereabouts. Whereabouts timeliness is dependent on how often the MS is updated with whereabouts information, what technologies are available or are in the vicinity, how capable the MS is of maintaining whereabouts, processing speed(s), transmission speed(s), known MS or LN-expanse design constraints, and perhaps other factors. In some embodiments, whereabouts timeliness is as soon as possible. That is, MS whereabouts is updated whenever possible as often as possible. In fact, the present disclosure provides an excellent system and methodology to accomplish that by leveraging location technologies whenever and wherever possible. However, there should be balance when considering less capable processing of a MS to prevent hogging CPU cycles from other applications at the MS. In other embodiments, a hard-coded or preconfigured time interval is used for keeping an MS informed of its whereabouts in a timely manner. For example, the MS should know its own whereabouts at least every second, or at least every 5 seconds, or at least every minute, etc. Whereabouts timeliness is critical depending on the applications in use at the MS. For example, if MS whereabouts is updated once at the MS every 5 minutes during high speeds of travel when using navigation, the user has a high risk of missing a turn during travel in downtown cities where timely decisions for turns are required. On the other hand, if MS whereabouts is updated every 5 seconds, and an application only requires an update accuracy to once per minute, then the MS may be excessively processing.
- In some embodiments, there is a Whereabouts Timeliness Variable (WTV) configured at the MS (
blocks -
- Define the maximum period of time for MS whereabouts to become stale at any particular time;
- Cause the MS to seek its whereabouts if whereabouts information is not up to date in accordance with the WTV; and
- Prevent keeping the MS too busy with keeping abreast of its own whereabouts.
In another embodiment, the WTV is automatically adjusted based on successes or failures of automatically locating the MS. As the MS successfully maintains timely whereabouts, the WTV is maintained consistent with the user configured, system configured, or preset value, or in accordance with active applications in use at the time. However, as the MS fails in maintaining timely whereabouts, the WTV is automatically adjusted (e.g. to longer periods of time to prevent unnecessary wasting of power and/or CPU resources). Later, as whereabouts become readily available, the WTV can be automatically adjusted back to the optimal value. In an emergency situation, the user always has the ability to force the MS to determine its own whereabouts anyway. (Blocks
- If
block 1432 determines the user did not select to configure the WTV, then processing continues to block 1436. Ifblock 1436 determines the user selected to configure the maximum number of threads in a 19 xx process (see 19 xx-Max variable inFIG. 19 discussions), then block 1438 interfaces with the user until a valid 19 xx-max variable is selected, and processing continues to block 1440. Ifblock 1440 determines the 19 xx process is already running (i.e. 19 xx-PID>0 implies it is enabled), then an error is provided to the user atblock 1442, and processing continues back to block 1406. Preferably,block 1442 does not continue back to block 1406 until the user acknowledges the error (e.g. with a user action). Ifblock 1440 determines the user selected 19 xx process (process 1902,process 1912,process 1922,process 1932,process 1942, or process 1952) is not already running (i.e. 19 xx-PID=0 implies it is disabled), then block 1444 prepares parameters for invoking the Configure Value procedure (parameters for reference (address) of 19 xx-Max value to configure; and validity criteria of value to configure), and the Configure Value procedure ofFIG. 18 is invoked atblock 1430 with the two (2) parameters. Thereafter, processing continues back to block 1406.Blocks - If
block 1436 determines the user did not select to configure a process thread maximum (19 xx-Max), then block 1446 checks to see if the user selected to (toggle) disable or enable a particular process (i.e. a 19 xx process ofFIG. 19 ). If block 1446 determines the user did select to toggle enabling/disabling a particularFIG. 19 process, then block 1448 interfaces with the user until a valid 19 xx process name is selected, and processing continues to block 1450. Ifblock 1450 determines the 19 xx process is already running (i.e. 19 xx-PID>0 implies it is enabled), then block 1454 prepares parameters (just as does block 2812). Thereafter, block 1456 invokesFIG. 29B processing (just as does block 2814). Processing then continues back to block 1406. Ifblock 1450 determines the 19 xx process is not running (i.e. 19 xx-PID=0 implies it is disabled), then block 1452 invokesFIG. 29A processing (just as does block 1232). Processing then continues back to block 1406. Block 1456 does not continue back to block 1406 until the process is completely terminated.Blocks - Preferred embodiments of
blocks 1446 and 1448 use convenient names of processes being started or terminated, rather than convenient brief process names such as 1902, 1912, 1922, 1932, 1942, or 1952 used in flowcharts. In some embodiments, the long readable name is used, such as whereabouts broadcast process (1902), whereabouts collection process (1912), whereabouts supervisor process (1922), timing determination process (1932), WDR request process (1942), and whereabouts determination process (1952). For example, the user may know that the whereabouts supervisor process enabled/disabled indicates whether or not to have whereabouts timeliness monitored in real time. Enabling the whereabouts supervisor process enables monitoring for the WTV in real time, and disabling the whereabouts supervisor process disables monitoring the WTV in real time. - In another embodiment of
blocks 1446 and 1448, a completely new name or description may be provided to any of the processes to facilitate user interface usability. For example, a new name Peer Location Source Variable (PLSV) can be associated to thewhereabouts broadcast process 1902 and/or 1942. PLSV may be easier to remember. If the PLSV was toggled to disabled, thewhereabouts broadcast process 1902 and/or 1942 terminates. If the PLSV was toggled to enabled, thewhereabouts broadcast process 1902 and/or 1942 is started. It may be easier to remember that the PLSV enables/disables whether or not to allow this MS to be a location source for other MSs in an LN-expanse. - In other embodiments, a useful name (e.g. PLSV) represents starting and terminating any subset of 19 xx processes (a plurality (e.g. 1902 and 1942)) for simplicity. In yet other embodiments, FIG. 14A/14B can be used to start or terminate worker thread(s) in any process, for example to throttle up more worker threads in a process, or to throttle down for less worker threads in a process, perhaps modifying thread instances to accommodate the number of channels for communications, or for the desired performance. There are many embodiments for fine tuning the
architecture 1900 for optimal peer to peer interaction. In yet other embodiments, toggling may not be used. There may be individual options available atblock 1408 for setting any data of this disclosure. Similarly, the 19 xx-Max variables may be modified via individual user friendly names and/or as a group of 19 xx-Max variables. - Referring back to block 1446, if it is determined the user did not select to toggle for enabling/disabling process(es), then processing continues to block 1458. If
block 1458 determines the user selected to exit FIG. 14A/14B configuration processing, then block 1460 terminates the user interface appropriately and processing terminates atblock 1462. Ifblock 1458 determines the user did not select to exit the user interface, then processing continues to block 1466 ofFIG. 14B by way of offpage connector 1464. - With reference now to
FIG. 14B , depicted is a continued portion flowchart ofFIG. 14A for describing a preferred embodiment of MS LBX configuration processing. Ifblock 1466 determines the user selected to configure the Source Periodicity Time Period (SPTP) value, then block 1468 prepares parameters for invoking the Configure Value procedure (parameters for reference (address) of value to configure; and validity criteria of value to configure), and the Configure Value procedure ofFIG. 18 is invoked atblock 1470 with the two (2) parameters. Thereafter, processing continues back to block 1406 by way of offpage connector 1498.Blocks - If
block 1466 determines the user did not select to configure the SPTP value, then processing continues to block 1472. Ifblock 1472 determines the user selected to configure service propagation, then the user configures service propagation atblock 1474 and processing continues back to block 1406 by way of offpage connector 1498. Ifblock 1472 determines the user did not select to configure service propagation, then processing continues to block 1476. - If
block 1476 determines the user selected to configurepermissions 10, then the user configures permissions atblock 1478 and processing continues back to block 1406 by way of offpage connector 1498. Ifblock 1476 determines the user did not select to configurepermissions 10, then processing continues to block 1480. Ifblock 1480 determines the user selected to configurecharters 12, then the user configurescharters 12 atblock 1482 and processing continues back to block 1406 by way of offpage connector 1498. Ifblock 1480 determines the user did not select to configurecharters 12, then processing continues to block 1484. Ifblock 1484 determines the user selected to configurestatistics 14, then the user configuresstatistics 14 atblock 1486 and processing continues back to block 1406 by way of offpage connector 1498. Ifblock 1484 determines the user did not select to configurestatistics 14, then processing continues to block 1488. Ifblock 1488 determines the user selected to configureservice informant code 28, then the user configurescode 28 atblock 1490 and processing continues back to block 1406 by way of offpage connector 1498. Ifblock 1488 determines the user did not select to configurecode 28, then processing continues to block 1492. Ifblock 1492 determines the user selected to maintainLBX history 30, then the user maintains LBX history atblock 1494 and processing continues back to block 1406 by way of offpage connector 1498. Ifblock 1492 determines the user did not select to maintainLBX history 30, then processing continues to block 1496. -
Block 1496 handles other user interfaceactions leaving block 1408, and processing continues back to block 1406 by way of offpage connector 1498. - Details of
blocks FIGS. 14A and 14B processing, while a general user may not. Any subset ofFIG. 14 configuration may appear in alternative embodiments, with or without authenticated administrator access to perform configuration. -
FIG. 15A depicts a flowchart for describing a preferred embodiment of DLM role configuration processing ofblock 1412. Processing begins atblock 1502 and continues to block 1504 which accesses current DLMV settings before continuing to block 1506. If there were no DLMV entries (list empty) as determined byblock 1506, then block 1508 provides an error to the user and processing terminates atblock 1518. The DLMV may be empty when the MS has no local DLM capability and there hasn't yet been any detected DLM capability, for example as evidenced by WDRs inserted to queue 22. Preferably, the error presented atblock 1508 requires the user to acknowledge the error (e.g. with a user action) beforeblock 1508 continues to block 1518. Ifblock 1506 determines at least one entry (role) is present in the DLMV, then the current DLMV setting(s) are saved atblock 1510, the manage list processing procedure ofFIG. 15C is invoked atblock 1512 with the DLMV as a reference (address) parameter, and processing continues to block 1514. -
Block 1514 determines if there were any changes to the DLMV fromFIG. 15C processing by comparing the DLMV afterblock 1512 with the DLMV saved atblock 1510. If there were changes viaFIG. 15C processing, such as a role which was enabled prior to block 1512 which is now disabled, or such as a role which was disabled prior to block 1512 which is now enabled, then block 1514 continues to block 1516 which handles the DLMV changes appropriately.Block 1516 continues to block 1518 which terminatesFIG. 15A processing. Ifblock 1514 determines there were no changes viablock 1512, then processing terminates atblock 1518. -
Block 1516 enables newly enabled role(s) as does block 1238 described forFIG. 12 .Block 1516 disables newly disabled role(s) as does block 2804 described forFIG. 28 . -
FIG. 15B depicts a flowchart for describing a preferred embodiment of ILM role configuration processing ofblock 1416. Processing begins atblock 1522 and continues to block 1524 which accesses current ILMV settings before continuing to block 1526. If there were no ILMV entries (list empty) as determined byblock 1526, then block 1528 provides an error to the user and processing terminates atblock 1538. The ILMV may be empty when the MS is not meant to have ILM capability. Preferably, the error presented atblock 1528 requires the user to acknowledge the error beforeblock 1528 continues to block 1538. Ifblock 1526 determines at least one entry (role) is present in the ILMV, then the current ILMV setting(s) are saved atblock 1530, the manage list processing procedure ofFIG. 15C is invoked with a reference (address) parameter of the ILMV atblock 1532, and processing continues to block 1534. -
Block 1534 determines if there were any changes to the ILMV fromFIG. 15C processing by comparing the ILMV afterblock 1532 with the ILMV saved atblock 1530. If there were changes viaFIG. 15C processing, such as a role which was enabled prior to block 1532 which is now disabled, or such as a role which was disabled prior to block 1532 which is now enabled, then block 1534 continues to block 1536 which handles the ILMV changes appropriately.Block 1536 continues to block 1538 which terminatesFIG. 15B processing. Ifblock 1534 determines there were no changes viablock 1532, then processing terminates atblock 1538. -
Block 1536 enables newly enabled role(s) as does blocks 1224 through 1234 described forFIG. 12 .Block 1536 disables newly disabled role(s) as doesblocks 2806 through 2816 described forFIG. 28 . -
FIG. 15C depicts a flowchart for describing a preferred embodiment of a procedure for Manage List processing. Processing starts atblock 1552 and continues to block 1554.Block 1554 presents the list (DLM capability if arrived to by way ofFIG. 15A ; ILM capability if arrived to by way ofFIG. 15B ) to the user, as passed toFIG. 15C processing with the reference parameter by the invoker, with which list items are marked (enabled) and which are unmarked (disabled) along with options, before continuing to block 1556 for awaiting user action.Block 1554 highlights currently enabled roles, and ensures disabled roles are not highlighted in the presented list. When a user action is detected atblock 1556, thereafter, block 1558 checks if a list entry was enabled (marked) by the user, in whichcase block 1560 marks the list item as enabled, saves it to the list (e.g. DLMV or ILMV), and processing continues back to block 1554 to refresh the list interface. Ifblock 1558 determines the user did not respond with an enable action, then block 1562 checks for a disable action. Ifblock 1562 determines the user wanted to disable a list entry, then block 1564 marks (actually unmarks it) the list item as disabled, saves it to the list (e.g. DLMV or ILMV), and processing continues back toblock 1554. Ifblock 1562 determines the user did not want to disable a list item, then block 1566 checks if the user wanted to exitFIG. 15C processing. Ifblock 1566 determines the user did not select to exit list processing, then processing continues to block 1568 where other user interface actions are appropriately handled and then processing continues back toblock 1554. Ifblock 1566 determines the user did select to exit manage list processing, thenFIG. 15C processing appropriately returns to the caller atblock 1570. -
FIG. 15C interfaces with the user for desired DLMV (viaFIG. 15A ) or ILMV (viaFIG. 15B ) configurations. In some embodiments, it makes sense to have user control over enabling or disabling DLM and/or ILM capability (roles) to the MS, for example for software or hardware testing. -
FIG. 16 depicts a flowchart for describing a preferred embodiment of NTP use configuration processing ofblock 1420. Processing starts atblock 1602 and continues to block 1604 where the current NTP use setting is accessed. Thereafter, block 1606 presents the current NTP use setting to its value of enabled or disabled along with options, before continuing to block 1608 for awaiting user action. When a user action is detected atblock 1608, block 1610 checks if the NTP use setting was disabled atblock 1608, in whichcase block 1612 terminates NTP use appropriately, block 1614 sets (and saves) the NTP use setting to disabled, and processing continues back to block 1606 to refresh the interface.Block 1612 disables NTP as does block 2828. - If
block 1610 determines the user did not respond for disabling NTP, then block 1616 checks for a toggle to being enabled. Ifblock 1616 determines the user wanted to enable NTP use, then block 1618 accesses known NTP server address(es) (e.g. ip addresses preconfigured to the MS, or set with another user interface at the MS), and pings each one, if necessary, atblock 1620 with a timeout. As soon as one NTP server is determined to be reachable,block 1620 continues to block 1622. If no NTP server was reachable, then the timeout will have expired for each one tried atblock 1620 for continuing to block 1622.Block 1622 determines if at least one NTP server was reachable atblock 1620. Ifblock 1622 determines no NTP server was reachable, then an error is presented to the user atblock 1624 and processing continues back to block 1606. Preferably, the error presented atblock 1624 requires the user to acknowledge the error beforeblock 1624 continues to block 1606. Ifblock 1622 determines that at least one NTP server was reachable, then block 1626 initializes NTP use appropriately, block 1628 sets the NTP use setting to enabled (and saves), and processing continues back to block 1606.Block 1626 enables NTP as does block 1210. - Referring back to
block 1616, if it is determined the user did not want to enable NTP use, then processing continues to block 1630 where it is checked if the user wanted to exitFIG. 16 processing. Ifblock 1630 determines the user did not select to exitFIG. 16 processing, then processing continues to block 1632 where other user interfaceactions leaving block 1608 are appropriately handled, and then processing continues back to block 1606. Ifblock 1630 determines the user did select to exit processing, thenFIG. 16 processing terminates atblock 1634. -
FIG. 17 depicts a flowchart for describing a preferred embodiment of WDR maintenance processing ofblock 1424. Processing starts atblock 1702 and continues to block 1704 where it is determined if there are any WDRs ofqueue 22. Ifblock 1704 determines there are no WDRs for processing, then block 1706 presents an error to the user and processing continues to block 1732 whereFIG. 17 processing terminates. Preferably, the error presented atblock 1706 requires the user to acknowledge the error beforeblock 1706 continues to block 1732. Ifblock 1704 determines there is at least one WDR, then processing continues to block 1708 where the current contents ofWDR queue 22 is appropriately presented to the user (in a scrollable list if necessary). Thereafter,block 1710 awaits user action. When a user action is detected atblock 1710, block 1712 checks if the user selected to delete a WDR fromqueue 22, in whichcase block 1714 discards the selected WDR, and processing continues back to block 1708 for a refreshed presentation ofqueue 22. Ifblock 1712 determines the user did not select to delete a WDR, then block 1716 checks if the user selected to modify a WDR. Ifblock 1716 determines the user wanted to modify a WDR ofqueue 22, then block 1718 interfaces with the user for validated WDR changes before continuing back toblock 1708. Ifblock 1716 determines the user did not select to modify a WDR, then block 1720 checks if the user selected to add a WDR to queue 22. Ifblock 1720 determines the user selected to add a WDR (for example, to manually configure MS whereabouts), then block 1722 interfaces with the user for a validated WDR to add to queue 22 before continuing back toblock 1708. Ifblock 1720 determines the user did not select to add a WDR, then block 1724 checks if the user selected to view detailed contents of a WDR, perhaps because WDRs are presented in an abbreviated form atblock 1708. If it is determined atblock 1724 the user did select to view details of a WDR, then block 1726 formats the WDR in detail form, presents it to the user, and waits for the user to exit the view of the WDR before continuing back toblock 1708. Ifblock 1724 determines the user did not select to view a WDR in detail, then block 1728 checks if the user wanted to exitFIG. 17 processing. Ifblock 1728 determines the user did not select to exitFIG. 17 processing, then processing continues to block 1730 where other user interfaceactions leaving block 1710 are appropriately handled, and then processing continues back toblock 1708. Ifblock 1728 determines the user did select to exit processing, thenFIG. 17 processing terminates atblock 1732. - There are many embodiments for maintaining WDRs of
queue 22. In some embodiments,FIG. 17 (i.e. block 1424) processing is only provided for debug of an MS. In a single instance WDR embodiment, block 1708 presents the one and only WDR which is used to keep current MS whereabouts whenever possible. Other embodiments incorporate any subset ofFIG. 17 processing. -
FIG. 18 depicts a flowchart for describing a preferred embodiment of a procedure for variable configuration processing, namely the Configure Value procedure, for example for processing ofblock 1430. Processing starts atblock 1802 and continues to block 1804 where parameters passed by the invoker ofFIG. 18 are determined, namely the reference (address) of the value for configuration to be modified, and the validity criteria for what makes the value valid. Passing the value by reference simply means thatFIG. 18 has the ability to directly change the value, regardless of where it is located. In some embodiments, the parameter is an address to a memory location for the value. In another embodiment, the value is maintained in a database or some persistent storage, andFIG. 18 is passed enough information to know how to permanently affect/change the value. -
Block 1804 continues to block 1806 where the current value passed is presented to the user (e.g. confidence floor value), and then to block 1808 for awaiting user action. When a user action is detected atblock 1808, block 1810 checks if the user selected to modify the value, in whichcase block 1812 interfaces with the user for a validated value using the validity criteria parameter before continuing back toblock 1806. Validity criteria may take the form of a value range, value type, set of allowable values, or any other criteria for what makes the value a valid one. - If
block 1810 determines the user did not select to modify the value, then block 1814 checks if the user wanted to exitFIG. 18 processing. Ifblock 1814 determines the user did not select to exitFIG. 18 processing, then processing continues to block 1816 where other user interfaceactions leaving block 1808 are appropriately handled, and then processing continues back toblock 1806. Ifblock 1814 determines the user did select to exit processing, thenFIG. 18 processing appropriately returns to the caller atblock 1818. -
FIG. 19 depicts an illustration for describing a preferred embodiment multithreaded architecture of peer interaction processing of a MS in accordance with the present disclosure.MS architecture 1900 preferably includes a set of Operating System (O/S) processes (i.e. O/S terminology “process” with O/S terminology “thread” or “threads (i.e. thread(s))), including awhereabouts broadcast process 1902, awhereabouts collection process 1912, awhereabouts supervisor process 1922, atiming determination process 1932, aWDR request process 1942, and awhereabouts determination process 1952. Further included are queues for interaction of processing, and process associated variables to facilitate processing. All of theFIG. 19 processes are ofPIP code 6. There is preferably a plurality (pool) of worker threads within each of said 19 xx processes (i.e. 1902, 1912, 1922, 1932, 1942 and 1952) for high performance asynchronous processing. Each 19 xx process (i.e. 1902, 1912, 1922, 1932, 1942 and 1952) preferably has at least two (2) threads: -
- 1) “parent thread”; and
- 2) “worker thread”.
A parent thread (FIG. 29A ) is the main process thread for: - starting the particular process;
- starting the correct number of worker thread(s) of that particular process;
- staying alive while all worker threads are busy processing; and
- properly terminating the process when worker threads are terminated.
The parent thread is indeed the parent for governing behavior of threads at the process whole level. Every process has a name for convenient reference, such as thenames FIG. 19 in a form 19 xx. There must be at least one worker thread in a process. Worker thread(s) are described with a flowchart as follows: - 1902—
FIG. 20 ; - 1912—
FIG. 21 ; - 1922—
FIG. 22 ; - 1932—
FIG. 23 ; - 1942—
FIG. 25 ; and - 1952—
FIG. 26A .
Threads of architecture MS are presented from a software perspective, but there are applicable hardware/firmware process thread embodiments accomplished for the same functionality. In fact, hardware/firmware embodiments are preferred when it is known that processing is mature (i.e. stable) to provide the fastest possible performance.Architecture 1900 processing is best achieved at the highest possible performance speeds for optimal wireless communications processing. There are two (2) types of processes for describing the types of worker threads: - 1) “Slave to Queue”; and
- 2) “Slave to Timer”.
- A 19 xx process is a slave to queue process when its worker thread(s) are driven by feeding from a queue of
architecture 1900. A slave to queue process stays “blocked” (O/S terminology “blocked”=preempted) on a queue entry retrieval interface until the sought queue item is inserted to the queue. The queue entry retrieval interface becomes “cleared” (O/S terminology “cleared”=clear to run) when the sought queue entry is retrieved from the queue by a thread. These terms (blocked and cleared) are analogous to a semaphore causing a thread to be blocked, and a thread to be cleared, as is well known in the art. Queues have semaphore control to ensure no more than one thread becomes clear at a time for a single queue entry retrieved (as done in an O/S). One thread sees a particular queue entry, but many threads can feed off the same queue to do the same work concurrently. Slave to queue type of processes are 1912, 1932, 1942 and 1952. A slave to queue process is properly terminated by inserting a special termination queue entry for each worker thread to terminate itself after queue entry retrieval. - A 19 xx process is a slave to timer process when its worker thread(s) are driven by a timer for peeking a queue of
architecture 1900. A timer provides the period of time for a worker thread to sleep during a looped iteration of checking a queue for a sought entry (without removing the entry from the queue). Slave to timer threads periodically peek a queue, and based on what is found, will process appropriately. A queue peek does not alter the peeked queue. The queue peek interface is semaphore protected for preventing peeking at an un-opportune time (e.g. while thread inserting or retrieving from queue). Queue interfaces ensure one thread is acting on a queue with a queue interface at any particular time. Slave to timer type of processes are 1902 and 1922. A slave to timer process is properly terminated by inserting a special termination queue entry for each worker thread to terminate itself by queue entry peek. -
Block 2812 knows the type of 19 xx process for preparing the process type parameter for invocation ofFIG. 29B atblock 2814. The type of process has slightly different termination requirements because of the worker thread(s) processing type. Alternate embodiments of slave to timer processes will make them slave to queue processes by simply feeding off Thread Request (TR)queue 1980 for driving a worker thread when to execute (and when to terminate). New timer(s) would insert timely queue entries to queue 1980, and processes 1902 and 1922 would retrieve from the queue (FIG. 24A record 2400). The queue entries would become available to queue 1980 when it is time for a particular worker thread to execute. Worker threads ofprocesses queue 1980 until an entry was inserted by a timer for enabling a worker thread (field 2400 a set to 1902 or 1912).TR queue 1980 is useful for starting any threads ofarchitecture 1900 in a slave to queue manner. This may be a cleaner architecture for all thread pools to operate the same way (slave to queue). Nevertheless, the two thread pool methods are implemented. - Each 19 xx process has at least four (4) variables for describing present disclosure processing:
-
- 19 xx-PID=The O/S terminology “Process Identifier (PID)” for the O/S PID of the 19 xx process. This variable is also used to determine if the process is enabled (PID>0), or is disabled (PID=0 (i.e. <=0));
- 19 xx-Max=The configured number of worker thread(s) for the 19 xx process;
- 19 xx-Sem=A process local semaphore for synchronizing 19 xx worker threads, for example in properly starting up worker threads in process 19 xx, and for properly terminating worker threads in process 19 xx; and
- 19 xx-Ct=A process local count of the number of worker thread(s) currently running in the 19 xx process.
19 xx-PID and 19 xx-Max are variables ofPIP data 8. 19 xx-Sem and 19 xx-Ct are preferably process 19 xx stack variables within the context ofPIP code 6. 19 xx-PID is a semaphore protected global variable inarchitecture 1900 so that it can be used to determine whether or not a particular 19 xx process is enabled (i.e. running) or disabled (not running). 19 xx-Max is a semaphore protected global variable inarchitecture 1900 so that user configuration processing outside ofarchitecture 1900 can be used to administrate a desired number of worker threads for a 19 xx process. Alternate embodiments will not provide user configuration of 19 xx-Max variables (e.g. hard coded maximum number of threads), in which case no 19 xx-Max global variable is necessary. “Thread(s) 19 xx” is a brief form of stating “worker thread(s) of the 19 xx process”.
- Receive (Rx)
queue 26 is for receivingCK 1304 orCK 1314 data (e.g. WDR or WDR requests), for example from wireless transmissions.Queue 26 will receive at least WDR information (destined for threads 1912) and WDR requests (FIG. 24C records 2490 destined for threads 1942). At least one thread (not shown) is responsible for listening on appropriate channel(s) and immediately depositing appropriate records to queue 26 so that they can be processed byarchitecture 1900. Preferably, there is a plurality (pool) of threads for feedingqueue 26 based on channel(s) being listened on, anddata queue 26. Alternative embodiments of thread(s) 1942 may themselves directly be listening on appropriate channels and immediately processing packets identified, in lieu of aqueue 26.Queue 26 is preferred to isolate channel(s) (e.g. frequency(s)) and transmission reception processing in well known modular (e.g. Radio Frequency (RF)) componentry, while providing a high performance queue interface to other asynchronous threads of architecture 1900 (e.g. thread(s) of process 1912). Wave spectrums (via particular communications interface 70) are appropriately processed for feedingqueue 26. As soon as a record is received by an MS, it is assumed ready for processing atqueue 26. Allqueue 26 accesses are assumed to have appropriate semaphore control to ensure synchronous access by any thread at any particular time to prevent data corruption and misuse. Queue entries inserted to queue 26 may have arrived on different channel(s), and in such embodiments a channel qualifier may further direct queue entries fromqueue 26 to aparticular thread 1912 or 1942 (e.g. thread(s) dedicated to channel(s)). In other embodiments, receiveprocessing feeds queue 26 independent of any particular channel(s) monitored, or received on (the preferred embodiment described). Regardless of how data is received and then immediately placed onqueue 26, a received date/time stamp (e.g. fields queue 26 insert interface tells the waiting thread(s) when the data was actually received. This ensures a most accurate received date/time stamp as close to receive processing as possible (e.g. enabling most accurate TDOA measurements). An alternate embodiment could determine applicable received date/time stamps in thread(s) 1912 or thread(s) 1942. Other data placed into received WDRs are: wave spectrum and/or particular communications interface 70 of the channel received on, and heading/yaw/pitch/roll (or accelerometer readings) with AOA measurements, signal strength, andother field 1100 f eligible data of the receiving MS. Depending on alternative embodiments,queue 26 may be viewed metaphorically for providing convenient grounds of explanation. - Send (Tx)
queue 24 is for sending/communicatingCK 1304 data, for example for wireless transmissions. At least one thread (not shown) is responsible for immediately transmitting (e.g. wirelessly) anything deposited to queue 24. Preferably, there is a plurality (pool) of threads for feeding off ofqueue 24 based on channel(s) being transmitted on, anddata 1302 anticipated for being sent. Alternative embodiments of thread(s) ofprocesses queue 24.Queue 24 is preferred to isolate channel(s) (e.g. frequency(s)) and transmission processing in well known modular (e.g. RF) componentry, while providing a high performance queue interface to other asynchronous threads of architecture 1900 (e.g. thread(s) 1942). Wave spectrums and/orparticular communications interface 70 are appropriately processed for sending fromqueue 24. Allqueue 24 accesses are assumed to have appropriate semaphore control to ensure synchronous access by any thread at any particular time to prevent data corruption and misuse. As soon as a record is inserted to queue 24, it is assumed sent immediately. Preferably, fields sent depend on fields set. Queue entries inserted to queue 24 may contain specification for which channel(s) to send on in some embodiments. In other embodiments, send processing feeding fromqueue 24 has intelligence for which channel(s) to send on (the preferred embodiment described). Depending on alternative embodiments,queue 24 may be viewed metaphorically for providing convenient grounds of explanation. - When interfacing to queue 24, the term “broadcast” refers to sending outgoing data in a manner for reaching as many MSs as possible (e.g. use all participating communications interfaces 70), whereas the term “send” refers to targeting a particular MS or group of MSs.
-
WDR queue 22 preferably contains at least oneWDR 1100 at any point in time, for at least describing whereabouts of the MS ofarchitecture 1900.Queue 22 accesses are assumed to have appropriate semaphore control to ensure synchronous access by any thread at any particular time to prevent data corruption and misuse. A single instance of data embodiment ofqueue 22 may require an explicit semaphore control for access. In a WDR plurality maintained to queue 22, appropriate queue interfaces are again provided to ensure synchronous thread access (e.g. implicit semaphore control). Regardless, there is still a need for aqueue 22 to maintain a plurality of WDRs from remote MSs. The preferred embodiment of all queue interfaces uses queue interface maintained semaphore(s) invisible to code making use of queue (e.g. API) interfaces. Depending on alternative embodiments,queue 22 may be viewed metaphorically for providing convenient grounds of explanation. - Thread Request (TR)
queue 1980 is for requesting processing by either a timing determination (worker) thread of process 1932 (i.e. thread 1932) or whereabouts determination (worker) thread of process 1952 (i.e. thread 1952). When requesting processing by athread 1932,TR queue 1980 has requests (retrieved viaprocessing 1934 after insertion processing 1918) from athread 1912 to initiate TDOA measurement. When requesting processing by athread 1952,TR queue 1980 has requests (retrieved viaprocessing 1958 afterinsertion processing 1918 or 1930) from athread thread 1952 performs whereabouts determination of the MS ofarchitecture 1900. Requests ofqueue 1980 compriserecords 2400. Preferably, there is a plurality (pool) ofthreads 1912 for feeding queue 1980 (i.e. feeding from queue 26), and for feeding a plurality each ofthreads queue 1980. Allqueue 1980 accesses are assumed to have appropriate semaphore control to ensure synchronous access by any thread at any particular time to prevent data corruption and misuse. Depending on alternative embodiments,queue 1980 may be viewed metaphorically for providing convenient grounds of explanation. - With reference now to
FIG. 24A , depicted is an illustration for describing a preferred embodiment of a thread request queue record, as maintained to Thread Request (TR)queue 1980.TR queue 1980 is not required when a LN-expanse globally uses NTP, as found in thread 19 xx processing described forarchitecture 1900, however it may be required at a MS which does not have NTP, or a MS which interacts with another data processing system (e.g. MS) that does not have NTP. Therefore, TR queue record 2400 (i.e. queue entry 2400) may, or may not, be required. This is the reasonFIG. 1A does not depictqueue 1980. When NTP is in use globally (in LN-expanse), TDOA measurements can be made using a single unidirectional data (1302 or 1312) packet containing a sent date/time stamp (of when the data was sent). Upon receipt, that sent date/time stamp received is compared with the date/time of receipt to determine the difference. The difference is a TDOA measurement. Knowing transmission speeds with a TDOA measurement allows calculating a distance. In this NTP scenario, no thread(s) 1932 are required. -
Threads 1912 and/or DLM processing may always insert the MS whereabouts without requirement for thread(s) 1952 by incorporatingthread 1952 logic intothread 1912, or by directly starting (without queue 1980) athread 1952 from athread 1912. Therefore,threads 1952 may not be required. Ifthreads 1952 are not required,queue 1980 may not be required by incorporatingthread 1932 logic intothread 1912, or by directly starting (without queue 1980) athread 1932 from athread 1912. Therefore,queue 1980 may not be required, andthreads 1932 may not be required. - Records 2400 (i.e. queue entries 2400) contain a
request type field 2400 a anddata field 2400 b.Request type field 2400 a simply routes the queue entry to destined thread(s) (e.g. thread(s) 1932 or thread(s) 1952). Athread 1932 remains blocked onqueue 1980 until arecord 2400 is inserted which has afield 2400 a containing thevalue 1932. Athread 1952 remains blocked onqueue 1980 until arecord 2400 is inserted which has afield 2400 a containing thevalue 1952.Data field 2400 b is set to zero (0) whentype field 2400 a contains 1952 (i.e. not relevant).Data field 2400 b contains an MS ID (field 1100 a) value, and possibly a targeted communications interface 70 (or wave spectrum if one to one), when type field contains 1932.Field 2400 b will contain information for appropriately targeting the MS ID with data (e.g. communications interface to use if MS has multiple of them). An MS with only one communications interface can store only a MS ID infield 2400 b. -
Records 2400 are used to cause appropriate processing by 19 xx threads (e.g. 1932 or 1952) as invoked when needed (e.g. by thread(s) 1912).Process 1932 is a slave to queue type of process, and there are noqueue 1980entries 2400 which will not get timely processed by athread 1932. No interim pruning is necessary to queue 1980. - With reference now back to
FIG. 19 , Correlation Response (CR)queue 1990 is for receiving correlation data for correlating requests transmitted indata 1302 with responses received indata Records 2450 are inserted to queue 1990 (via processing 1928) from thread(s) 1922 so that thread(s) 1912 (after processing 1920) correlatedata records 2450 are inserted to queue 1990 (via processing 1936) from thread(s) 1932 so that thread(s) 1912 (after processing 1920) correlatedata queue 1990 and for feeding from queue 1990 (feeding fromqueue 1990 with thread(s) 1912). Allqueue 1990 accesses are assumed to have appropriate semaphore control to ensure synchronous access by any thread at any particular time to prevent data corruption and misuse. Depending on alternative embodiments,queue 1990 may be viewed metaphorically for providing convenient grounds of explanation. - With reference now to
FIG. 24B , depicted is an illustration for describing a preferred embodiment of a correlation response queue record, as maintained to Correlation Response (CR)queue 1990.CR queue 1990 is not required when a LN-expanse globally uses NTP, as found in thread 19 xx processing described forarchitecture 1900, however it may be required at a MS which does not have NTP, or a MS which interacts with another data processing system (e.g. MS) that does not have NTP. Therefore, CR record 2450 (i.e. queue entry 2450) may, or may not, be required. This is the reasonFIG. 1A does not depictqueue 1990. The purpose ofCR queue 1990 is to enable calculation of TDOA measurements using correlation data to match a request with a response. When NTP is used globally in the LN-expanse, no such correlations between a request and response is required, as described above. In the NTP scenario, thread(s) 1912 can deduce TDOA measurements directly from responses (seeFIG. 21 ), and there is no requirement forthreads 1932. - TDOA measurements are best taken using date/time stamps as close to the processing points of sending and receiving as possible, otherwise critical regions of code may be required for enabling process time adjustments to the measurements when processing is “further out” from said points. This is the reason MS receive processing provides received date/time stamps with data inserted to queue 26 (
field queue 24 processing inserts to queue 1990 so the date/time stamp field 2450 a for when sent is as close to just prior to having been sent as possible. However, there is still the requirement for processing time spent inserting to queue 1990 prior to sending anyway. Anticipated processing speeds ofarchitecture 1900 allow reasonably moving sent date/time stamp setting just a little “further out” from actually sending to keep modular send processing isolated. A preferred embodiment (as presented) assumes thesend queue 24 interface minimizes processing instructions from when data is placed ontoqueue 24 and when it is actually sent, so that the sending thread(s) 19 xx (1902, 1922, 1932 and 1942) insert to queue 1990 with a reasonably accurate sent/date stamp field 2450 a. This ensures a most accurate sent date/time stamp (e.g. enabling most accurate TDOA measurements). An alternate embodiment makes appropriate adjustments for more accurate time to consider processing instructions up to the point of sending afterqueue 1990 insertion. - Records 2450 (i.e. queue entries 2450) contain a date/
time stamp field 2450 a and acorrelation data field 2450 b. Date/time stamp field 2450 a contains a date/time stamp of when a request (data 1302) was sent as set by the thread inserting thequeue entry 2450.Correlation data field 2450 b contains unique correlation data (e.g. MS id with suffix of unique number) used to provide correlation for matching sent requests (data 1302) with received responses (data 1302 or 1312), regardless of the particular communications interface(s) used (e.g. different wave spectrums supported by MS). Upon a correlation match, a TDOA measurement is calculated using the time difference betweenfield 2450 a and a date/time stamp of when the response was received (e.g. field 1100 p). Athread 1912 accessesqueue 1990 for arecord 2450 usingcorrelation field 2450 b to match, whendata thread 1912 then uses thefield 2450 a to calculate a TDOA measurement.Process 1912 is not a slave to queue 1990 (but is to queue 26). Athread 1912peeks queue 1990 for a matching entry when appropriate.Queue 1990 may containobsolete queue entries 2450 until pruning is performed. Some WDR requests may be broadcasts, therefore records 2450 may be used for correlating a plurality of responses. In anotherrecord 2450 embodiment, an additional field 2450 c is provided for specification of which communication interface(s) and/or channel(s) to listen on for a response. - With reference now back to
FIG. 19 , any reasonable subset ofarchitecture 1900 processing may be incorporated in a MS. For example in one minimal subset embodiment, a DLM which has excellent direct locating means only needs a single instance WDR (queue 22) and asingle thread 1902 for broadcasting whereabouts data to facilitate whereabouts determination by other MSs. In a near superset embodiment,process 1942 processing may be incorporated completely intoprocess 1912, thereby eliminatingprocessing 1942 by havingthreads 1912 feed fromqueue 26 for WDR requests as well as WDR information. In another subset embodiment,process 1922 may only send requests to queue 24 for responses, or may only start athread 1952 for determining whereabouts of the MS. There are many viable subset embodiments depending on the MS being a DLM or ILM, capabilities of the MS, LN-expanse deployment design choices, etc. A reference toFIG. 19 accompanies thread 19 xx flowcharts (FIGS. 20 , 21, 22, 23, 25 and 26A). The user, preferably an administrator type (e.g. for IbxPhone™ debug) selectively configures whether or not to start or terminate a process (thread pool), and perhaps the number of threads to start in the pool (seeFIG. 14A ). Starting a process (and threads) and terminating processes (and threads) is shown in flowcharts 29A and 29B. There are other embodiments for properly starting and terminating threads without departing from the spirit and scope of this disclosure. -
FIG. 20 depicts a flowchart for describing a preferred embodiment of MS whereabouts broadcast processing, for example to facilitate other MSs in locating themselves in an LN-expanse.FIG. 20 processing describes aprocess 1902 worker thread, and is ofPIP code 6. Thread(s) 1902 purpose is for the MS ofFIG. 20 processing (e.g. a first, or sending, MS) to periodically transmit whereabouts information to other MSs (e.g. at least a second, or receiving, MS) to use in locating themselves. It is recommended that validity criteria set at block 1444 for 1902-Max be fixed at one (1) in the preferred embodiment. Multiple channels for broadcast atblock 2016 should be isolated to modular send processing (feeding from a queue 24). - In an alternative embodiment having multiple transmission channels visible to
process 1902, there can be aworker thread 1902 per channel to handle broadcasting on multiple channels. If thread(s) 1902 (block 2016) do not transmit directly over the channel themselves, this embodiment would provide means for communicating the channel for broadcast to send processing when interfacing to queue 24 (e.g. incorporate a channel qualifier field with WDR inserted to queue 24). This embodiment could allow specification of at least one (1) worker thread per channel, however multiple worker threads configurable forprocess 1902 as appropriated for the number of channels configurable for broadcast. - Processing begins at
block 2002, continues to block 2004 where the process worker thread count 1902-Ct is accessed and incremented by 1 (using appropriate semaphore access (e.g. 1902-Sem)), and continues to block 2006 for peekingWDR queue 22 for a special termination request entry.Block 2004 may also check the 1902-Ct value, and signal theprocess 1902 parent thread that all worker threads are running when 1902-Ct reaches 1902-Max. Thereafter, ifblock 2008 determines that a worker thread termination request was not found inqueue 22, processing continues to block 2010.Block 2010 peeks the WDR queue 22 (using interface 1904) for the most recent highest confidence entry for this MS whereabouts by searchingqueue 22 for: theMS ID field 1100 a matching the MS ID ofFIG. 20 processing, and a confidence field 1100 d greater than or equal to the confidence floor value, and a most recent NTP enabled date/time stamp field 1100 b within a prescribed trailing period of time (e.g. preferably less than or equal to 2 seconds). For example, block 2010 peeks the queue (i.e. makes a copy for use if an entry found for subsequent processing, but does not remove the entry from queue) for a WDR of this MS (i.e. MS ofFIG. 20 processing) which has the greatest confidence over 75 and has been most recently inserted to queue 22 with an NTP date/time stamp in the last 2 seconds. Date/time stamps for MS whereabouts which are not NTP derived have little use in the overall palette of process 19 xx choices ofarchitecture 1900 because receiving data processing systems (e.g. MSs) will have no means of determining an accurate TDOA measurement in the unidirectional transmission from an NTP disabled MS. A receiving data processing system will still require a bidirectional correlated exchange with the MS ofFIG. 20 processing to determine an accurate TDOA measurement in its own time scale (which is accomplished with thread(s) 1922 pulling WDR information anyway). An alternate embodiment to block 2010 will not use the NTP indicator as a search criteria so that receiving data processing systems can receive to athread 1912, and then continue for appropriate correlation processing, or can at least maintain whereabouts to queue 22 to know who is nearby. -
Thread 1902 is of less value to the LN-expanse when it broadcasts outdated/invalid whereabouts of the MS to facilitate locating other MSs. In an alternate embodiment, a movement tolerance (e.g. user configured or system set (e.g. 3 meters)) is incorporated at the MS, or at service(s) used to locate the MS, for knowing when the MS has significantly moved (e.g. more than 3 meters) and how long it has been (e.g. 45 seconds) since last significantly moving. In this embodiment, the MS is aware of the period of time since last significantly moving and the search time criteria is set using the amount of time since the MS significantly moved (whichever is greater). This way a large number of (perhaps more confident candidates) WDRs are searched in the time period when the MS has not significantly moved.Optional blocks 278 through 284 may have been incorporated toFIG. 2F for movement tolerance processing just described, in which case the LWT is compared to the current date/time ofblock 2010 processing to adjustblock 2010 search time criteria for the correct trailing period. In any case, a WDR is sought atblock 2010 which will help other MSs in the LN-expanse locate themselves, and to let other MSs know who is nearby. - Thereafter, if
block 2012 determines a useful WDR was found, then block 2014 prepares the WDR for send processing,block 2016 broadcasts the WDR information (using send interface 1906) by inserting to queue 24 so that send processing broadcasts data 1302 (e.g. on all available communications interface(s) 70), for example as far asradius 1306, and processing continues to block 2018. The broadcast is for reception by data processing systems (e.g. MSs) in the vicinity. Atleast fields FIG. 11A descriptions. Fields are set to the following upon exit from block 2014: -
MS ID field 1100 a is preferably set with:Field 1100 a fromqueue 22, or transformed (if not already) into a pseudo MS ID (possibly for future correlation) if desired. This field may also be set to null (not set) because it is not required when the NTP indicator offield 1100 b is enabled and the broadcast is sent with an NTP enabledfield 1100 n.
DATE/TIME STAMP field 1100 b is preferably set with:Field 1100 b fromqueue 22.
LOCATION field 1100 c is preferably set with:Field 1100 c fromqueue 22.
CONFIDENCE field 1100 d is preferably set with: Field 1100 d fromqueue 22.
LOCATION TECHNOLOGY field 1100 e is preferably set with: Field 1100 e fromqueue 22.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set). Null indicates to send processing feeding fromqueue 24 to use all available comm. interfaces 70 (i.e. Broadcast). Specifying a comm. interface targets the specified interface (i.e. send).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: null (not set). If MS ID (or pseudo MS ID) is sent, this is all that is required to target this MS.
SPEED field 1100 h is preferably set with:Field 1100 h fromqueue 22.
HEADING field 1100 i is preferably set with: Field 1100 i fromqueue 22.
ELEVATION field 1100 j is preferably set with: Field 1100 j fromqueue 22.
APPLICATION FIELDS field 1100 k is preferably set with:Field 1100 k fromqueue 22. An alternate embodiment will add, alter, or discard data (with or without date/time stamps) here at the time of block 2014 processing.
CORRELATION FIELD 1100 m is preferably set with: null (not set).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Sent date/time stamp as close in processing the broadcast ofblock 2016 as possible.
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. N/A for sending). -
Block 2018 causesthread 1902 to sleep according to the SPTP setting (e.g. a few seconds). When the sleep time has elapsed, processing continues back to block 2006 for another loop iteration ofblocks 2006 through 2016. Referring back toblock 2012, if a useful WDR was not found (e.g. candidates too old), then processing continues to block 2018. Referring back toblock 2008, if a worker thread termination request entry was found atqueue 22, then block 2020 decrements the worker thread count by 1 (using appropriate semaphore access (e.g. 1902-Sem)), andthread 1902 processing terminates atblock 2022.Block 2020 may also check the 1902-Ct value, and signal theprocess 1902 parent thread that all worker threads are terminated when 1902-Ct equals zero (0). -
Block 2016 causesbroadcasting data 1302 containingCK 1304 whereinCK 1304 contains WDR information prepared as described above for block 2014. Alternative embodiments ofblock 2010 may not search a specified confidence value, and broadcast the best entry available anyway so that listeners in the vicinity will decide what to do with it. A semaphore protected data access (instead of a queue peek) may be used in embodiments where there is always one WDR current entry maintained for the MS. - In the embodiment wherein usual
MS communications data 1302 of the MS is altered to containCK 1304 for listening MSs in the vicinity, send processing feeding fromqueue 24, caused byblock 2016 processing, will place WDR information asCK 1304 embedded inusual data 1302 at the next opportune time of sendingusual data 1302. If an opportune time is not timely, send processing should discard the send request ofblock 2016 to avoid broadcasting outdated whereabouts information (unless using a movement tolerance and time since last significant movement). As the MS conducts its normal communications, transmitteddata 1302 containsnew data CK 1304 to be ignored by receiving MSother character 32 processing, but to be found by listening MSs within the vicinity which anticipate presence ofCK 1304. Otherwise, when LN-Expanse deployments have not introducedCK 1304 tousual data 1302 communicated on a receivable signal by MSs in the vicinity,FIG. 20 sends repeated timely pulsed broadcasts of new data 1302 (per SPTP) for MSs in the vicinity of the first MS to receive. In any case, appropriate implementation should ensurefield 1100 n is as accurate as possible for whendata 1302 is actually sent. - An alternate embodiment to
architecture 1900 for elimination ofprocess 1902 incorporates a trigger implementation for broadcasting MS whereabouts at the best possible time—i.e. when the MS whereabouts is inserted to queue 22. As soon as a new (preferably NTP enabled) WDR candidate becomes available, it can be broadcast at a new block 279 ofFIG. 2F . (e.g. new block 279 continued to fromblock 278 and then continuing to block 280). Fields are set as described above forFIG. 20 . Preferably, the new block 279 starts an asynchronous thread consisting ofblocks 2014 and 2016 so thatFIG. 2F processing performance is not impacted. In a further embodiment, block 279 can be further enhanced using the SPTP value to make sure that too many broadcasts are not made. The SPTP (Source Periodicity Time Period) could be observed for getting as close as possible to broadcasting whereabouts in accordance with SPTP (e.g. worst case there are not enough broadcasts). -
FIG. 21 depicts a flowchart for describing a preferred embodiment of MS whereabouts collection processing.FIG. 21 processing describes aprocess 1912 worker thread, and is ofPIP code 6. Thread(s) 1912 purpose is for the MS ofFIG. 21 processing (e.g. a second, or receiving, MS) to collect potentially useful WDR information from other MSs (e.g. at least a first, or sending, MS) in the vicinity for determining whereabouts of the receiving (second) MS. It is recommended that validity criteria set at block 1444 for 1912-Max be set as high as possible (e.g. 10) relative performance considerations ofarchitecture 1900, with at least one thread per channel that WDR information may be received on by the receiving MS. Multiple channels for receiving data fed to queue 26 should be isolated to modular receive processing (feeding a queue 26). - In an alternative embodiment having multiple receiving transmission channels visible to process 1912 (e.g. thread(s) 1912 receiving directly), there can be a
worker thread 1912 per channel to handle receiving on multiple channels simultaneously. If thread(s) 1912 do not receive directly from the channel, the preferred embodiment of FIG. 21 would not need to convey channel information to thread(s) 1912 waiting onqueue 26 anyway. Embodiments could allow specification/configuration of many thread(s) 1912 per channel. - Processing begins at block 2102, continues to block 2104 where the process worker thread count 1912-Ct is accessed and incremented by 1 (using appropriate semaphore access (e.g. 1912-Sem)), and continues to block 2106 for interim housekeeping of pruning the WDR queue by invoking a Prune Queues procedure of
FIG. 27 . Block 2104 may also check the 1912-Ct value, and signal theprocess 1912 parent thread that all worker threads are running when 1912-Ct reaches 1912-Max.Block 2106 may not be required sinceblock 2130 can causequeue 22 pruning (block 292). - Thereafter, block 2108 retrieves from queue 26 a WDR (using interface 1914), perhaps a special termination request entry, or a WDR received in data 1302 (CK 1304) or data 1312 (CK 1314), and only continues to block 2110 when a WDR has been retrieved.
Block 2108 stays blocked on retrieving fromqueue 26 until any WDR is retrieved. Ifblock 2110 determines that a special WDR indicating to terminate was not found inqueue 26, processing continues to block 2112.Block 2112 adjusts date/time stamp field 1100 b if necessary depending on NTP use in the LN-expanse and adjusts the confidence field 1100 d accordingly. In a preferred embodiment,fields 1100 b and 1100 d for the WDR in process is set as follows for certain conditions: -
-
Fields fields 1100 b and 1100 d as is; or -
Fields field 1100 m) present?: No, then set confidence (field 1100 d) to 0 (for filtering out at block 2114)/Yes, then setfield 1100 b to 1100 p (in time terms of this MS) and adjust confidence lower based on differences betweenfields -
Fields field 1100 b to 1100 p (in time terms of this MS) and adjust confidence lower based on differences betweenfields -
Fields 1100 b NTP indicated, 1100 n and 1100 p not: Is correlation present?:
-
- No, then set confidence to 0 (for filtering out at block 2114)/Yes, then set
field 1100 b to 1100 p (in time terms of this MS) and adjust confidence lower based on differences betweenfields -
-
Field 1100 b not NTP indicated, 1100 n and 1100 p are: Is correlation present?: No, then set confidence to 0 (for filtering out at block 2114)/Yes, then setfield 1100 b to 1100 p (in time terms of this MS) and adjust confidence lower based on differences betweenfields -
Fields field 1100 b to 1100 p (in time terms of this MS) and adjust confidence lower based on differences betweenfields -
Fields field 1100 b to 1100 p (in time terms of this MS) and adjust confidence lower based on differences betweenfields -
Fields field 1100 b to 1100 p (in time terms of this MS) and adjust confidence lower based on differences betweenfields
NTP ensures maintaining a high confidence in the LN-expanse, but absence of NTP is still useful. Confidence values should be adjusted with the knowledge of the trailing time periods used for searches when sharing whereabouts (e.g. thread(s) 1942 searches).Block 2112 continues to block 2114.
-
- If at block 2114, the WDR confidence field 1100 d is not greater than the confidence floor value, then processing continues back to
block 2106. If block 2114 determines that the WDR field 1100 d is satisfactory, then block 2116 initializes a TDOA_FINAL variable to False, and block 2118 checks if the WDR fromblock 2108 contains correlation (field 1100 m). - If
block 2118 determines the WDR does not contain correlation, then block 2120 accesses the ILMV, block 2122 determines the source (ILM or DLM) of the WDR using the originator indicator of field 1100 e, and block 2124 checks suitability for collection of the WDR. While processes 19 xx running are generally reflective of the ILMV roles configured, it is possible that the more descriptive nature of ILMV role(s) not be one to one in relationship to 19 xx processes, in particular depending on the subset ofarchitecture 1900 in use.Block 2124 is redundant anyway because of block 274. Ifblock 2124 determines the ILMV role is disabled for collecting this WDR, then processing continues back toblock 2106. Ifblock 2124 determines the ILMV role is enabled for collecting this WDR, then processing continues to block 2126. - If
block 2126 determines both the first (sending) and second (receiving) MS are NTP enabled (i.e.Fields queue 22 insertion,block 2130 prepares parameters forFIG. 2F processing andblock 2132 invokesFIG. 2F processing (interface 1916). Parameters set atblock 2130 are: WDRREF=a reference or pointer to the WDR completed at block 2128; DELETEQ=FIG. 21 location queue discard processing; and SUPER=FIG. 21 supervisory notification processing. Block 2128 calculates a TDOA measurement whenever possible and inserts to field 1100 f. SeeFIG. 11A descriptions. Fields are set to the following upon exit from block 2128: -
MS ID field 1100 a is preferably set with:Field 1100 a fromqueue 26.
DATE/TIME STAMP field 1100 b is preferably set with: Preferred embodiment discussed forblock 2112.
LOCATION field 1100 c is preferably set with:Field 1100 c fromqueue 26.
CONFIDENCE field 1100 d is preferably set with: Confidence at equal to or less than field 1100 d received from queue 26 (see preferred embodiment for block 2112).
LOCATION TECHNOLOGY field 1100 e is preferably set with: Field 1100 e fromqueue 26.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: All available measurements from receive processing (e.g. AOA, heading, yaw, pitch, roll, signal strength, wave spectrum,particular communications interface 70, etc), and TDOA measurement(s) as determined inFIG. 21 (blocks 2128 and 2148).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with:Field 1100 g fromqueue 26.
SPEED field 1100 h is preferably set with:Field 1100 h fromqueue 26.
HEADING field 1100 i is preferably set with: Field 1100 i fromqueue 26.
ELEVATION field 1100 j is preferably set with: Field 1100 j fromqueue 26.
APPLICATION FIELDS field 1100 k is preferably set with:Field 1100 k fromqueue 26. An alternate embodiment will add, alter, or discard data (with or without date/time stamps) here at the time of block 2128 processing.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22). Was used byFIG. 21 processing.
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22). Was used byFIG. 21 processing.
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). Was used byFIG. 21 processing. -
Block 2132 continues to block 2134 where arecord 2400 is built (i.e.field 2400 a=1952 andfield 2400 b is set to null (e.g. −1)) and then block 2136 inserts therecord 2400 to TR queue 1980 (using interface 1918) so that athread 1952 will perform processing.Blocks thread 1952.Block 2136 continues back toblock 2106. - Referring now back to block 2126, if it is determined that a TDOA measurement cannot be made (i.e. (
field block 2138 determines there is none, then processing continues back to block 2106 because there is no way to distinguish one MS from another with respect to the WDR retrieved atblock 2108 for directing bidirectional correlation. An alternate embodiment will use a providedcorrelation field 1100 m received atblock 2108, instead of afield 1100 a, for knowing how to target the originating MS for TDOA measurement processing initiated by athread 1932. Ifblock 2138 determines there is a usable MS ID (or correlation field), then block 2140 builds a record 2400 (field 2400 a=1932,field 2400 b=the MS ID (or pseudo MS ID, or correlation) and particular communications interface fromfield 1100 f (if available) of the WDR ofblock 2108, and block 2142 inserts therecord 2400 to queue 1980 (interface 1918) for starting athread 1932.Block 2142 continues back toblock 2106. An alternate embodiment causesblock 2126 to continue directly to block 2140 (no block 2138) for a No condition fromblock 2126. Regardless of whether the originating MS ID can be targeted, a correlation (in lieu of an MS ID) may be used when the MS responds with a broadcast. The WDR request made bythread 1932 can be a broadcast rather than a targeted request. Thread(s) 1932 can handle sending targeted WDR requests (to a known MS ID) and broadcast WDR requests. - Referring back to
block 2118, if it is determined the WDR does contain correlation (field 1100 m),block 2144 peeks the CR queue 1990 (using interface 1920) for arecord 2450 containing a match (i.e.field 1100 m matched tofield 2450 b). Thereafter, ifblock 2146 determines no correlation was found on queue 1990 (e.g. response took too long and entry was pruned), then processing continues to block 2120 already described. Ifblock 2146 determines the correlation entry was found (i.e.thread 1912 received a response from an earlier request (e.g. from athread 1922 or 1932), then block 2148 uses date/time stamp field 2450 a (from block 2144) withfield 1100 p (e.g. from block 2108) to calculate a TDOA measurement in time scale of the MS ofFIG. 21 processing, and setsfield 1100 f appropriately in the WDR. Note thatcorrelation field 2450 b is valid across all available MS communications interfaces (e.g. all supported active wave spectrums). The TDOA measurement considers duration of time between the earlier sent date/time ofrecord 2450 and the later time of received date/time field 1100 p. The TDOA measurement may further be altered atblock 2148 processing time to a distance knowing the velocity of the wave spectrum used as received toqueue 26.Block 2148 continues to block 2150 where the TDOA_FINAL variable is set to True, then to block 2120 for processing already described. - Referring back to
block 2110, if a WDR for a worker thread termination request was found atqueue 26, then block 2152 decrements the worker thread count by 1 (using appropriate semaphore access (e.g. 1912-Sem)), andthread 1912 processing terminates atblock 2154.Block 2152 may also check the 1912-Ct value, and signal theprocess 1912 parent thread that all worker threads are terminated when 1912-Ct equals zero (0). - In the embodiment wherein usual
MS communications data 1302 of the MS is altered to containCK processing feeding queue 26 will place WDR information to queue 26 asCK usual communication data data new data CK other character 32 processing, but to be found by listening MSs within the vicinity which anticipate presence ofCK FIG. 21 receives new data 1302 (or 1312) sent. In any case,field 1100 p should be as accurate as possible for when data 1302 (or 1312) was actually received. Critical regions of code and/or anticipated execution timing may be used to affect a best setting offield 1100 p. - So,
FIG. 21 is responsible for maintaining whereabouts of others to queue 22 with data useful for triangulating itself. -
FIG. 22 depicts a flowchart for describing a preferred embodiment of MS whereabouts supervisor processing, for example to ensure the MS ofFIG. 22 processing (e.g. first MS) is maintaining timely whereabouts information for itself.FIG. 22 processing describes aprocess 1922 worker thread, and is ofPIP code 6. Thread(s) 1922 purpose is for the MS ofFIG. 22 processing (e.g. a first, or sending, MS), after determining its whereabouts are stale, to periodically transmit requests for whereabouts information from MSs in the vicinity (e.g. from at least a second, or receiving, MS), and/or to start athread 1952 for immediately determining whereabouts. Alternative embodiments toFIG. 22 will implement processing of blocks 2218 through 2224, or processing ofblocks 2226 through 2228, or both as depicted inFIG. 22 . It is recommended that validity criteria set at block 1444 for 1922-Max be fixed at one (1) in the preferred embodiment. Multiple channels for broadcast atblock 2224 should be isolated to modular send processing feeding from aqueue 24. - In an alternative embodiment having multiple transmission channels visible to
process 1922, there can be aworker thread 1922 per channel to handle broadcasting on multiple channels. If thread(s) 1922 (block 2224) do not transmit directly over the channel, this embodiment would provide means for communicating the channel for broadcast to send processing when interfacing to queue 24 (e.g. incorporate a channel qualifier field with WDR request inserted to queue 24). This embodiment could allow specification of one (1) thread per channel, however multiple worker threads configurable forprocess 1922 as determined by the number of channels configurable for broadcast. - Processing begins at
block 2202, continues to block 2204 where the process worker thread count 1922-Ct is accessed and incremented by 1 (using appropriate semaphore access (e.g. 1922-Sem)), and continues to block 2206 for interim housekeeping of pruning the CR queue by invoking a Prune Queues procedure ofFIG. 27 .Block 2204 may also check the 1922-Ct value, and signal theprocess 1922 parent thread that all worker threads are running when 1922-Ct reaches 1922-Max.Block 2206 continues to block 2208 for peeking WDR queue 22 (using interface 1924) for a special termination request entry. Thereafter, ifblock 2210 determines that a worker thread termination request was not found inqueue 22, processing continues to block 2212.Block 2212 peeks the WDR queue 22 (using interface 1924) for the most recent highest confidence entry for this MS whereabouts by searchingqueue 22 for: theMS ID field 1100 a matching the MS ID ofFIG. 22 processing, and a confidence field 1100 d greater than or equal to the confidence floor value, and a most recent date/time stamp field 1100 b within a prescribed trailing period of time ofblock 2212 search processing using a function of the WTV (i.e. f(WTV)=short-hand for “function of WTV”) for the period. For example, block 2212 peeks the queue (i.e. makes a copy for use if an entry found for subsequent processing, but does not remove the entry from queue) for a WDR of the first MS which has the greatest confidence over 75 and has been most recently inserted to queue 22 in the last 3 seconds. Since the MS whereabouts accuracy may be dependent on timeliness of the WTV, it is recommended that the f(WTV) be some value less than or equal to WTV, but preferably not greater than the WTV.Thread 1922 is of less value to the MS when not making sure in a timely manner the MS is maintaining timely whereabouts for itself. In an alternate embodiment, a movement tolerance (e.g. user configured or system set (e.g. 3 meters)) is incorporated at the MS, or at service(s) used to locate the MS, for knowing when the MS has significantly moved (e.g. more than 3 meters) and how long it has been (e.g. 45 seconds) since last significantly moving. In this embodiment, the MS is aware of the period of time since last significantly moving and the f(WTV) is set using the amount of time since the MS significantly moved (i.e. f(WTV)=as described above, or the amount of time since significantly moving, whichever is greater). This way a large number of (perhaps more confident candidates) WDRs are searched in the time period when the MS has not significantly moved.Optional blocks 278 through 284 may have been incorporated toFIG. 2F for movement tolerance processing just described, in which case the LWT is compared to the current date/time to adjust the WTV for the correct trailing period. In any case, a WDR is sought atblock 2212 which will verify whether or not MS whereabouts are current. - Thereafter, if
block 2214 determines a satisfactory WDR was found, then processing continues to block 2216.Block 2216 causesthread 1922 to sleep according to a f(WTV) (preferably a value less than or equal to the WTV (e.g. 95% of WTV)). When the sleep time has elapsed, processing continues back to block 2206 for another loop iteration ofblocks 2206 through 2214. - If
block 2214 determines a current WDR was not found, then block 2218 builds a WDR request (e.g. containingrecord 2490 withfield 2490 a for the MS ofFIG. 22 processing (MS ID or pseudo MS ID) so receiving MSs in the LN-expanse know who to respond to, andfield 2490 b with appropriate correlation for response),block 2220 builds a record 2450 (using correlation generated for the request at block 2218),block 2222 inserts therecord 2450 to queue 1990 (using interface 1928), and block 2224 broadcasts the WDR request (record 2490) for responses. Absence offield 2490 d indicates to send processing feeding fromqueue 24 to broadcast on all available comm. interfaces 70. - With reference now to
FIG. 24C , depicted is an illustration for describing a preferred embodiment of a WDR request record, as communicated to queue 24 or 26. When a LN-expanse globally uses NTP, as found in thread 19 xx processing described forarchitecture 1900, aWDR request record 2490 may, or may not, be required. TDOA calculations can be made using a single unidirectional data (1302 or 1312) packet containing a sent date/time stamp (of when the data was sent) as described above. -
Records 2490 contain aMS ID field 2490 a andcorrelation field 2490 b.MS ID field 2490 a contains an MS ID (e.g. a value offield 1100 a). An alternate embodiment will contain a pseudo MS ID (for correlation), perhaps made by a derivative of the MS ID with a unique (suffix) portion, so that receiving MSs can directly address the MS sending the request without actually knowing the MS ID (i.e. they know the pseudo MS ID which enables the MS to recognize originated transmissions).Correlation data field 2490 b contains unique correlation data (e.g. MS id with suffix of unique number) used to provide correlation for matching sent requests (data 1302) with received WDR responses (data 1302 or 1312). Upon a correlation match, a TDOA measurement is calculated using the time difference betweenfield 2450 a and a date/time stamp of when the response was received (e.g. field 1100 p). Received date/time stamp field 2490 c is added by receiveprocessing feeding queue 26 when an MS received the request from another MS.Comm interface field 2490 d is added by receive processing inserting to queue 26 for how to respond and target the originator. Many MSs do not have choices of communications interfaces, sofield 2490 d may not be required. If available it is used, otherwise a response can be a broadcast.Field 2490 d may contain a wave spectrum identifier for uniquely identifying how to respond (e.g. one to one with communications interface), or any other value for indicating how to send given how the request was received. - With reference back to
FIG. 22 , block 2218 builds a request that receiving MSs will know is for soliciting a response with WDR information. Block 2218 generates correlation forfield 2450 b to be returned in responses to the WDR request broadcast atblock 2224.Block 2220 also setsfield 2450 a to when the request was sent. Preferably,field 2450 a is set as close to the broadcast as possible. In an alternative embodiment, broadcast processing feeding fromqueue 24 makes therecord 2450 and inserts it to queue 1990 with a most accurate time of when the request was actually sent.Fields 2450 a are to be as accurate as possible.Block 2224 broadcasts the WDR request data 1302 (using send interface 1926) by inserting to queue 24 so that sendprocessing broadcasts data 1302, for example as far asradius 1306. Broadcasting preferably uses all available communications interface(s) 70 (e.g. all available wave spectrums). Therefore, thecomm interface field 2490 d is not set (which implies to send processing to do a broadcast). -
Block 2224 continues to block 2226 where arecord 2400 is built (i.e.field 2400 a=1952 andfield 2400 b is set to null (e.g. −1)) and then block 2228 inserts therecord 2400 to TR queue 1980 (using interface 1930) so that athread 1952 will perform processing.Blocks thread 1952.Block 2228 continues back toblock 2216. - Referring back to
block 2210, if a worker thread termination request entry was found atqueue 22, then block 2230 decrements the worker thread count by 1 (using appropriate semaphore access (e.g. 1922-Sem)), andthread 1922 processing terminates atblock 2232.Block 2230 may also check the 1922-Ct value, and signal theprocess 1922 parent thread that all worker threads are terminated when 1922-Ct equals zero (0). - In the embodiment wherein usual
MS communications data 1302 of the MS is altered to containCK 1304 for listening MSs in the vicinity, send processing feeding fromqueue 24, caused byblock 2224 processing, will place the request asCK 1304 embedded inusual data 1302 at the next opportune time of sendingusual data 1302. This may require the alternative embodiment of adding the entry to queue 1990 being part of send processing. As the MS conducts its normal communications, transmitteddata 1302 containsnew data CK 1304 to be ignored by receiving MSother character 32 processing, but to be found by listening MSs within the vicinity which anticipate presence ofCK 1304. Otherwise, when LN-Expanse deployments have not introducedCK 1304 tousual data 1302 communicated on a receivable signal by MSs in the vicinity,FIG. 22 sends newWDR request data 1302. -
FIG. 23 depicts a flowchart for describing a preferred embodiment of MS timing determination processing.FIG. 23 processing describes aprocess 1932 worker thread, and is ofPIP code 6. Thread(s) 1932 purpose is for the MS ofFIG. 23 processing to determine TDOA measurements when needed for WDR information received. It is recommended that validity criteria set at block 1444 for 1932-Max be set as high as possible (e.g. 12) relative performance considerations ofarchitecture 1900, to servicemultiple threads 1912. - Processing begins at
block 2302, continues to block 2304 where the process worker thread count 1932-Ct is accessed and incremented by 1 (using appropriate semaphore access (e.g. 1932-Sem)), and continues to block 2306 for interim housekeeping of pruning the CR queue by invoking a Prune Queues procedure ofFIG. 27 .Block 2304 may also check the 1932-Ct value, and signal theprocess 1932 parent thread that all worker threads are running when 1932-Ct reaches 1932-Max. - Thereafter, block 2308 retrieves from queue 1980 a record 2400 (using interface 1934), perhaps a special termination request entry, or a
record 2400 received from thread(s) 1912, and only continues to block 2310 when arecord 2400 containingfield 2400 a set to 1932 has been retrieved.Block 2308 stays blocked on retrieving fromqueue 1980 until arecord 2400 withfield 2400 a=1932 is retrieved. Ifblock 2310 determines a special entry indicating to terminate was not found inqueue 1980, processing continues to block 2312. - If at
block 2312, therecord 2400 does not contain a MS ID (or pseudo MS ID) infield 2400 b, processing continues to block 2314 for building a WDR request (record 2490) to be broadcast, and then to block 2318. Broadcasting preferably uses all available communications interface(s) 70 (e.g. all available wave spectrums). Ifblock 2312 determines thefield 2400 b is a valid MS ID (not null),block 2316 builds a WDR request targeted for the MS ID, and processing continues to block 2318. A targeted request is built for targeting the MS ID (and communications interface, if available) fromfield 2400 b. Send processing is told which communications interface to use, if available (e.g. MS has multiple), otherwise send processing will target each available interface. In the unlikely case a MS ID is present infield 2400 b without the communications interface applicable, then all communications interfaces 70 are used with the targeted MS ID. In MS embodiments with multiple communications interfaces 70, then 2400 b is to contain the applicable communication interface for sending.Block 2318 generates appropriate correlation for afield 2450 b (e.g. to be compared with a response WDR at block 2144),block 2320 setsfield 2450 a to the current MS date/time stamp, block 2322 inserts therecord 2450 to queue 1990 (using interface 1936), andblock 2324 sends/broadcasts (using interface 1938) a WDR request (record 2490). Thereafter, processing continues back to block 2306 for another loop iteration. An alternative embodiment will only target a WDR request to a known MS ID. For example, block 2312 would continue back to block 2306 if no MS ID is found (=null), otherwise it will continue to block 2316 (i.e. no use for block 2314). -
Block 2318 setsfield 2450 b to correlation to be returned in responses to the WDR request sent/broadcast atblock 2324.Block 2320 setsfield 2450 a to when the request is sent. Preferably,field 2450 a is set as close as possible to when a send occurred. In an alternative embodiment, send processing feeding fromqueue 24 makes therecord 2450 and inserts it to queue 1990 with a most accurate time of when the request was actually sent.Fields 2450 a are to be as accurate as possible.Block 2324 sends/broadcasts the WDR request data 1302 (using send interface 1938) by inserting to queue 24 a record 2490 (2490 a=the targeted MS ID (or pseudo MS ID) OR null if arrived to fromblock 2314,field 2490 b=correlation generated at block 2318) so that send processing sendsdata 1302, for example as far asradius 1306. A null MS ID may be responded to by all MSs in the vicinity. A non-null MS ID is to be responded to by a particular MS. Presence offield 2490 d indicates to send processing feeding fromqueue 24 to target the MS ID over the specified comm. interface (e.g. when MS has a plurality of comm. interfaces 70 (e.g. cellular, Wifi, Bluetooth, etc; i.e. MS supports multiple classes of wave spectrum)). - Referring back to
block 2310, if a worker thread termination request was found atqueue 1980, then block 2326 decrements the worker thread count by 1 (using appropriate semaphore access (e.g. 1932-Sem)), andthread 1932 processing terminates atblock 2328.Block 2326 may also check the 1932-Ct value, and signal theprocess 1932 parent thread that all worker threads are terminated when 1932-Ct equals zero (0). - In the embodiment wherein usual
MS communications data 1302 of the MS is altered to containCK 1304 for listening MSs in the vicinity, send processing feeding fromqueue 24, caused byblock 2324 processing, will place the WDR request asCK 1304 embedded inusual data 1302 at the next opportune time of sendingusual data 1302. As the MS conducts its normal communications, transmitteddata 1302 containsnew data CK 1304 to be ignored by receiving MSother character 32 processing, but to be found by listening MSs within the vicinity which anticipate presence ofCK 1304. This may require the alternative embodiment of adding the entry to queue 1990 being part of send processing. Otherwise, when LN-Expanse deployments have not introducedCK 1304 tousual data 1302 communicated on a receivable signal by MSs in the vicinity,FIG. 22 sends/broadcasts newWDR request data 1302. - An alternate embodiment to block 2324 can wait for a response with a reasonable timeout, thereby eliminating the need for
blocks 2318 through 2322 which is used to correlate the subsequent response (to thread 1912) with the request sent atblock 2324. However, this will cause a potentially unpredictable number of simultaneously executing thread(s) 1932 when many MSs are in the vicinity. - Thread(s) 1932 are useful when one or both parties to WDR transmission (sending and receiving MS) do not have NTP enabled. TDOA measurements are taken to triangulate the MS relative other MSs in real time.
-
FIG. 25 depicts a flowchart for describing a preferred embodiment of MS WDR request processing, for example when a remote MS requests (e.g. fromFIG. 22 or 23) a WDR. Receive processing identifies targeted requests destined (e.g.FIG. 23 ) for the MS ofFIG. 25 processing, and identifies general broadcasts (e.g.FIG. 22 ) for processing as well.FIG. 25 processing describes aprocess 1942 worker thread, and is ofPIP code 6. Thread(s) 1942 purpose is for the MS ofFIG. 25 processing to respond to incoming WDR requests. It is recommended that validity criteria set at block 1444 for 1942-Max be set as high as possible (e.g. 10) relative performance considerations ofarchitecture 1900, to service multiple WDR requests simultaneously. Multiple channels for receiving data fed to queue 26 should be isolated to modular receive processing. - In an alternative embodiment having multiple receiving transmission channels visible to
process 1942, there can be aworker thread 1942 per channel to handle receiving on multiple channels simultaneously. If thread(s) 1942 do not receive directly from the channel, the preferred embodiment ofFIG. 25 would not need to convey channel information to thread(s) 1942 waiting onqueue 24 anyway. Embodiments could allow specification/configuration of many thread(s) 1942 per channel. - Processing begins at
block 2502, continues to block 2504 where the process worker thread count 1942-Ct is accessed and incremented by 1 (using appropriate semaphore access (e.g. 1942-Sem)), and continues to block 2506 for retrieving from queue 26 a record 2490 (using interface 1948), perhaps a special termination request entry, and only continues to block 2508 when arecord 2490 is retrieved.Block 2506 stays blocked on retrieving fromqueue 26 until anyrecord 2490 is retrieved. Ifblock 2508 determines a special entry indicating to terminate was not found inqueue 26, processing continues to block 2510. There are various embodiments for thread(s) 1912 and thread(s) 1942 to feed off aqueue 26 for different record types, for example, separate queues 26A and 26B, or a thread target field with either record found at queue 26 (e.g. likefield 2400 a). In another embodiment, thread(s) 1912 are modified with logic of thread(s) 1942 to handle all records described for aqueue 26, since thread(s) 1912 are listening forqueue 26 data anyway. -
Block 2510 peeks the WDR queue 22 (using interface 1944) for the most recent highest confidence entry for this MS whereabouts by searchingqueue 22 for: theMS ID field 1100 a matching the MS ID ofFIG. 25 processing, and a confidence field 1100 d greater than or equal to the confidence floor value, and a most recent date/time stamp field 1100 b within a prescribed trailing period of time ofblock 2510 search processing (e.g. 2 seconds). For example, block 2510 peeks the queue (i.e. makes a copy for use if an entry found for subsequent processing, but does not remove the entry from queue) for a WDR of the MS (ofFIG. 25 processing) which has the greatest confidence over 75 and has been most recently inserted to queue 22 in the last 2 seconds. It is recommended that the trailing period of time used byblock 2510 be never greater than a few seconds.Thread 1942 is of less value to the LN-expanse when it responds with outdated/invalid whereabouts of the MS to facilitate locating other MSs. In an alternate embodiment, a movement tolerance (e.g. user configured or system set (e.g. 3 meters)) is incorporated at the MS, or at service(s) used to locate the MS, for knowing when the MS has significantly moved (e.g. more than 3 meters) and how long it has been (e.g. 45 seconds) since last significantly moving. In this embodiment, the MS is aware of the period of time since last significantly moving and the trailing period of time used byblock 2510 is set using the amount of time since the MS significantly moved, or the amount of time since significantly moving, whichever is greater. This way a large number of (perhaps more confident candidate) WDRs are searched in the time period when the MS has not significantly moved.Optional blocks 278 through 284 may have been incorporated toFIG. 2F for movement tolerance processing just described, in which case the LWT is compared to the current date/time to adjust the trailing period of time used byblock 2510 for the correct trailing period. In any case, a WDR is sought atblock 2510 to satisfy a request helping another MS in the LN-expanse locate itself. - Thereafter, if
block 2512 determines a useful WDR was not found, then processing continues back to block 2506 for another loop iteration of processing an inbound WDR request. Ifblock 2512 determines a useful WDR was found, then block 2514 prepares the WDR for send processing withcorrelation field 1100 m set fromcorrelation field 2490 b retrieved atblock 2506, andblock 2516 sends/broadcasts (perfield 2490 a) the WDR information (using send interface 1946) by inserting to queue 24 so that send processing transmitsdata 1302, for example as far asradius 1306, and processing continues back toblock 2506. Atleast fields FIG. 11A descriptions. Fields are set to the following upon exit from block 2514: -
MS ID field 1100 a is preferably set with:Field 2490 a fromqueue 26.
DATE/TIME STAMP field 1100 b is preferably set with:Field 1100 b fromqueue 22.
LOCATION field 1100 c is preferably set with:Field 1100 c fromqueue 22.
CONFIDENCE field 1100 d is preferably set with: Field 1100 d fromqueue 22.
LOCATION TECHNOLOGY field 1100 e is preferably set with: Field 1100 e fromqueue 22.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set) for Broadcast by send processing, otherwise set to field 2490 d for Send by send processing.
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: null (not set).
SPEED field 1100 h is preferably set with:Field 1100 h fromqueue 22.
HEADING field 1100 i is preferably set with: Field 1100 i fromqueue 22.
ELEVATION field 1100 j is preferably set with: Field 1100 j fromqueue 22.
APPLICATION FIELDS field 1100 k is preferably set with:Field 1100 k fromqueue 22. An alternate embodiment will add, alter, or discard data (with or without date/time stamps) here at the time ofblock 2514 processing.
CORRELATION FIELD 1100 m is preferably set with:Field 2490 b fromqueue 26.
SENT DATE/TIME STAMP field 1100 n is preferably set with: Sent date/time stamp as close in processing the send/broadcast ofblock 2516 as possible.
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. N/A for sending). - Embodiments may rely completely on the
correlation field 2490 b with no need forfield 2490 a. Referring back toblock 2508, if a worker thread termination request was found atqueue 26, then block 2518 decrements the worker thread count by 1 (using appropriate semaphore access (e.g. 1942-Sem)), andthread 1942 processing terminates atblock 2520.Block 2518 may also check the 1942-Ct value, and signal theprocess 1942 parent thread that all worker threads are terminated when 1942-Ct equals zero (0). -
Block 2516 causes sending/broadcasting data 1302 containingCK 1304, depending on the type of MS, whereinCK 1304 contains WDR information prepared as described above forblock 2514. Alternative embodiments ofblock 2510 may not search a specified confidence value, and broadcast the best entry available anyway so that listeners in the vicinity will decide what to do with it. A semaphore protected data access (instead of a queue peek) may be used in embodiments where there is always one WDR current entry maintained for the MS. - In the embodiment wherein usual
MS communications data 1302 of the MS is altered to containCK 1304 for listening MSs in the vicinity, send processing feeding fromqueue 24, caused byblock 2516 processing, will place WDR information asCK 1304 embedded inusual data 1302 at the next opportune time of sendingusual data 1302. If an opportune time is not timely, send processing should discard the send request ofblock 2516 to avoid broadcasting outdated whereabouts information (unless using a movement tolerance and time since last significant movement). As the MS conducts its normal communications, transmitteddata 1302 containsnew data CK 1304 to be ignored by receiving MSother character 32 processing, but to be found by listening MSs within the vicinity which anticipate presence ofCK 1304. Otherwise, when LN-Expanse deployments have not introducedCK 1304 tousual data 1302 communicated on a receivable signal by MSs in the vicinity,FIG. 25 sends/broadcasts newWDR response data 1302. In any case,field 1100 n should be as accurate as possible for whendata 1302 is actually sent. Critical regions of code (i.e. prevent thread preemption) and/or anticipated execution timing may be used to affect a best setting offield 1100 n. - In an alternate embodiment,
records 2490 contain a sent date/time stamp field 2490 e of when the request was sent by a remote MS, and the received date/time stamp field 2490 c is processed at the MS inFIG. 25 processing. This would enable block 2514 to calculate a TDOA measurement for returning infield 1100 f of the WDR sent/broadcast atblock 2516. -
FIG. 26A depicts a flowchart for describing a preferred embodiment of MS whereabouts determination processing.FIG. 26A processing describes aprocess 1952 worker thread, and is ofPIP code 6. Thread(s) 1952 purpose is for the MS ofFIG. 26A processing to determine its own whereabouts with useful WDRs from other MSs. It is recommended that validity criteria set at block 1444 for 1952-Max be set as high as possible (e.g. 10) relative performance considerations ofarchitecture 1900, to servicemultiple threads 1912. 1952-Max may also be set depending on what DLM capability exists for the MS ofFIG. 26A processing. In an alternate embodiment, thread(s) 19 xx are automatically throttled up or down (e.g. 1952-Max) per unique requirements of the MS as it travels. - Processing begins at
block 2602, continues to block 2604 where the process worker thread count 1952-Ct is accessed and incremented by 1 (using appropriate semaphore access (e.g. 1952-Sem)), and continues to block 2606 for interim housekeeping of pruning the WDR queue by invoking a Prune Queues procedure ofFIG. 27 .Block 2604 may also check the 1952-Ct value, and signal theprocess 1952 parent thread that all worker threads are running when 1952-Ct reaches 1952-Max.Block 2606 may not be necessary since pruning may be accomplished at block 2620 when invokingFIG. 2F (block 292). - Thereafter, block 2608 retrieves from queue 1980 a record 2400 (using interface 1958), perhaps a special termination request entry, or a
record 2400 received from thread(s) 1912, and only continues to block 2610 when arecord 2400 containingfield 2400 a set to 1952 has been retrieved. Block 2608 stays blocked on retrieving fromqueue 1980 until arecord 2400 withfield 2400 a=1952 is retrieved. If block 2610 determines a special entry indicating to terminate was not found inqueue 1980, processing continues to block 2612. -
Block 2612 peeks the WDR queue 22 (using interface 1954) for the most recent highest confidence entry for this MS whereabouts by searchingqueue 22 for: theMS ID field 1100 a matching the MS ID ofFIG. 26A processing, and a confidence field 1100 d greater than or equal to the confidence floor value, and a most recent date/time stamp field 1100 b within a prescribed trailing period of time ofblock 2612 search processing using a f(WTV) for the period. For example, block 2612 peeks the queue (i.e. makes a copy for use if an entry found for subsequent processing, but does not remove the entry from queue) for a WDR of the MS (ofFIG. 26A processing) which has the greatest confidence over 75 and has been most recently inserted to queue 22 in the last 2 seconds. Since MS whereabouts accuracy may be dependent on timeliness of the WTV, it is recommended that the f(WTV) be some value less than or equal to WTV. In an alternate embodiment, a movement tolerance (e.g. user configured or system set (e.g. 3 meters)) is incorporated at the MS, or at service(s) used to locate the MS, for knowing when the MS has significantly moved (e.g. more than 3 meters) and how long it has been (e.g. 45 seconds) since last significantly moving. In this embodiment, the MS is aware of the period of time since last significantly moving and the f(WTV) is set using the amount of time since the MS significantly moved (i.e. f(WTV)=as described above, or the amount of time since significantly moving, whichever is greater). This way a large number of (perhaps more confident candidate) WDRs are searched in the time period when the MS has not significantly moved.Optional blocks 278 through 284 may have been incorporated toFIG. 2F for movement tolerance processing just described, in which case the LWT is compared to the current date/time to adjust the WTV for the correct trailing period. - Thereafter, if
block 2614 determines a timely whereabouts for this MS already exists to queue 22 (current WDR found), then processing continues back to block 2606 for another loop iteration of processing. If 2614 determines a satisfactory WDR does not already exist inqueue 22, then block 2600 determines a new highest confidence WDR for this MS (FIG. 26B processing) usingqueue 22. - Thereafter, if
block 2616 determines a WDR was not created (BESTWDR variable=null) for the MS ofFIG. 26A processing (by block 2600), then processing continues back toblock 2606. Ifblock 2616 determines a WDR was created (BESTWDR=WDR created byFIG. 26B ) for the MS ofFIG. 26A processing byblock 2600, then processing continues to block 2618 for preparingFIG. 2F parameters andFIG. 2F processing is invoked with the new WDR at block 2620 (for interface 1956) before continuing back toblock 2606. Parameters set atblock 2618 are: WDRREF=a reference or pointer to the WDR completed atblock 2600; DELETEQ=FIG. 26A location queue discard processing; and SUPER=FIG. 26A supervisory notification processing. - Referring back to block 2610, if a worker thread termination request was found at
queue 1980, then block 2622 decrements the worker thread count by 1 (using appropriate semaphore access (e.g. 1952-Sem)), andthread 1952 processing terminates atblock 2624.Block 2622 may also check the 1952-Ct value, and signal theprocess 1952 parent thread that all worker threads are terminated when 1952-Ct equals zero (0). - Alternate embodiments to
FIG. 26A will have a pool of thread(s) 1952 per location technology (WDR field 1100 e) for specific WDR field(s) selective processing.FIG. 26A processing is shown to be generic with handling all WDRs atblock 2600. -
FIG. 26B depicts a flowchart for describing a preferred embodiment of processing for determining a highest possible confidence whereabouts, for example in ILM processing, such as processing ofFIG. 26A block 2600. Processing starts at block 2630, and continues to block 2632 where variables are initialized (BESTWDR=null, THIS_MS=null, REMOTE_MS=null). BESTWDR will reference the highest confidence WDR for whereabouts of the MS ofFIG. 26B processing (i.e. this MS) upon return toFIG. 26A when whereabouts determination is successful, otherwise BESTWDR is set to null (none found). THIS_MS points to an appropriately sorted list of WDRs which were originated by this MS and are DLM originated (i.e. inserted by the DLM ofFIG. 26B processing). REMOTE_MS points to an appropriately sorted list of WDRs which were originated by other MSs (i.e. from DLMs and/or ILMs and collected by the ILM ofFIG. 26B processing). - Thereafter, block 2634 peeks the WDR queue 22 (using interface 1954) for most recent WDRs by searching
queue 22 for: confidence field 1100 d greater than or equal to the confidence floor value, and a most recent date/time stamp field 1100 b within a prescribed trailing period of time of block 2634 search processing using a f(WTV) for the period. For example, block 2634 peeks the queue (i.e. makes a copy of all WDRs to a result list for use if any found for subsequent processing, but does not remove the entry(s) from queue) for all WDRs which have confidence over 75 and has been most recently inserted to queue 22 in the last 2 seconds. It is recommended that the f(WTV) used here be some value less than or equal to the WTV (want to be ahead of curve, so may use a percentage (e.g. 90%)), but preferably not greater than a couple/few seconds (depends on MS, MS applications, MS environment, whereabouts determination related variables, etc). - In an alternative embodiment, thread(s) 1952 coordinate with each other to know successes, failures or progress of their sister threads for automatically adjusting the trailing f(WTV) period of time appropriately. See “Alternative IPC Embodiments” below.
-
Thread 1952 is of less value to the MS when whereabouts are calculated using stale WDRs, or when not enough useful WDRs are considered. In an alternate embodiment, a movement tolerance (e.g. user configured or system set (e.g. 3 meters)) is incorporated at the MS, or at service(s) used to locate the MS, for knowing when the MS has significantly moved (e.g. more than 3 meters) and how long it has been (e.g. 45 seconds) since last significantly moving. In this embodiment, the MS is aware of the period of time since last significantly moving and the f(WTV) is set using the amount of time since the MS significantly moved (i.e. f(WTV)=as described above, or the amount of time since significantly moving, whichever is greater). This way a large number of (perhaps more confident candidates) WDRs are searched in the time period when the MS has not significantly moved.Optional blocks 278 through 284 may have been incorporated toFIG. 2F for movement tolerance processing just described, in which case the LWT is compared to the current date/time to adjust the WTV for the correct trailing period. In any case, all useful WDRs are sought at block 2634 and placed into a list upon exit from block 2634. - Thereafter, block 2636 sets THIS_MS list and REMOTE_MS list sort keys to be used at blocks 2644 and 2654. Blocks 2638 through 2654 will prioritize WDRs found at block 2634 depending on the sort keys made at block 2636. A number of variables may be used to determine the best sort keys, such as the time period used to peek at block 2634 and/or the number of entries in the WDR list returned by block 2634, and/or other variables. When the time period of search is small (e.g. less than a couple seconds), lists (THIS_MS and REMOTE_MS) should be prioritized primarily by confidence (fields 1100 d) since any WDRs are valuable for determining whereabouts. This is the preferred embodiment.
- When the time period is great, careful measure must be taken to ensure stale WDRs are not used (e.g. >few seconds, and not considering movement tolerance). Depending on decision embodiments, there will be preferred priority order sort keys created at exit from block 2636, for example “key1/key2/key3” implies that “key1” is a primary key, “key2” is a second order key, and “key3” is a third order key. A key such as “field-1100 b/field-1100 d/field-1100 f:signal-strength” would sort WDRs first by using date/
time stamp fields 1100 b, then by confidence value fields 1100 d (sorted within matching date/time stamp WDRs), then by signal-strength field 1100 f sub-field values (sorted within matching WDR confidences; no signal strength present=lowest priority). Another sort key may be “field-1100 d/field-1100 b” for sorting WDRs first by using confidence values, then by date/time stamps (sorted within matching WDR confidences). The same or different sort keys can be used for lists THIS_MS and REMOTE_MS. Any WDR data (fields or subfields) can be sorted with a key, and sort keys can be of N order dimension such that “key1/key2/ . . . /keyN”. Whatever sort keys are used, block 2686 will have to consider confidence versus being stale, relative to the WTV. In the preferred embodiment, the REMOTE_MS and THIS_MS lists are set with the same sort keys of “field-1100 d/field-1100 b” (i.e. peek time period used at block 2634 is less than 2 seconds) so that confidence is primary. - Thereafter, block 2638 gets the first (if any) WDR in the list returned at block 2634 (also processes next WDR in list when encountered again in loop of blocks 2638 through 2654), and block 2640 checks to see if all WDRs have already been processed. If block 2640 finds that all WDRs have not been processed, then block 2642 checks the WDR origination. If block 2642 determines the WDR is one that originated from a remote MS (i.e. MS ID does not match the MS of
FIG. 26B processing), then block 2644 inserts the WDR into the REMOTE_MS list using the desired sort key (confidence primary, time secondary) from block 2636, and processing continues to block 2638 for another loop iteration. If block 2642 determines the WDR is one that originated from this MS (MS ID field 1100 a matches the MS ofFIG. 26B processing (e.g. this MS being a DLM at the time of WDR creation (this MS ID=field 1100 a) or this MS being an ILM at the time of WDR creation (previous processing of FIG. 26A)), then processing continues to block 2646 to determine how to process the WDR which was inserted by “this MS” for its own whereabouts. - Block 2646 accesses
field 1100 f for data found there (e.g.FIGS. 2D and 2E may have inserted useful TDOA measurements, even though DLM processing occurred; orFIG. 3C may have inserted useful TDOA and/or AOA measurements with reference station(s) whereabouts; or receive processing may have inserted AOA and related measurements). Thereafter, if block 2648 determines presence of TDOA and/or AOA data, block 2650 checks if reference whereabouts (e.g.FIG. 3C selected stationary reference location(s)) is also stored infield 1100 f. If block 2650 determines whereabouts information is also stored tofield 1100 f, then block 2652 makes new WDR(s) from the whereabouts information containing at least the WDR Core andfield 1100 f containing the AOA and/or TDOA information as though it were from a remote DLM or ILM. Block 2652 also performs the expected result of inserting the WDR of loop processing into the THIS_MS list using the desired sort key from block 2636. Processing then continues to block 2644 where the newly made WDR(s) is inserted into the REMOTE_MS list using the desired sort key (confidence primary, time secondary) from block 2636. Block 2644 continues back to block 2638. - Referring back to block 2650, if it is determined that whereabouts information was not present with the AOA and/or TDOA information of
field 1100 f, then processing continues to block 2644 for inserting into the REMOTE_MS list (appropriately with sort key from block 2636) the currently looped WDR from block 2634. In-range location technology associates the MS with the antenna (or cell tower) location, so thatfield 1100 c already contains the antenna (or cell tower) whereabouts, and the TDOA information was stored to determine how close the MS was to the antenna (or cell tower) at the time. The WDR will be more useful in the REMOTE_MS list, then if added to the THIS_MS list (see loop of blocks 2660 through 2680). Referring back to block 2648, if it is determined that no AOA and/or TDOA information was infield 1100 f, then processing continues to block 2654 for inserting the WDR into the THIS_MS list (appropriately with sort key (confidence primary, time secondary) from block 2636). - Block 2654 handles WDRs that originated from the MS of
FIG. 26B (this MS), such as described inFIGS. 2A through 9B , or results from previousFIG. 26A processing. Block 2644 maintains remote DLMs and/or ILMs (their whereabouts) to the REMOTE_MS list in hope WDRs containuseful field 1100 f information for determining the whereabouts of the MS ofFIG. 26B processing. Block 2652 handles WDRs that originated from the MS ofFIG. 26B processing (this MS), but also processes fields from stationary references used (e.g.FIG. 3C ) by this MS which can be helpful as though the WDR was originated by a remote ILM or DLM. Thus, block 2652 causes inserting to both lists (THIS_MS and REMOTE_MS) when the WDR contains useful information for both. Blocks 2652, 2654 and 2644 cause the iterative loop of blocks 2660 through 2680 to perform ADLT using DLMs and/or ILMs. Alternate embodiments of blocks 2638 through 2654 may use peek methodologies to sort fromqueue 22 for the REMOTE_MS and THIS_MS lists. - Referring back to block 2640, if it is determined that all WDRs in the list from block 2634 have been processed, then block 2656 initializes a DISTANCE list and ANGLE list each to null, block 2658 sets a loop iteration pointer to the first entry of the prioritized REMOTE_MS list (e.g. first entry higher priority than last entry in accordance with sort key used), and block 2660 starts the loop for working with ordered WDRs of the REMOTE_MS list. Exit from block 2640 to block 2656 occurs when the REMOTE_MS and THIS_MS lists are in the desired priority order for subsequent processing. Block 2660 gets the next (or first) REMOTE_MS list entry for processing before continuing to block 2662. If block 2662 determines all WDRs have not yet been processed from the REMOTE_MS list, then processing continues to block 2664.
- Blocks 2664 and 2670 direct collection of all useful ILM triangulation measurements for TDOA, AOA, and/or MPT triangulation of this MS relative known whereabouts (e.g. other MSs). It is interesting to note that TDOA and AOA measurements (
field 1100 f) may have been made from different communications interfaces 70 (e.g. different wave spectrums), depending on interfaces the MS has available (i.e. all can participate). For example, a MS with blue-tooth, WiFi and cellular phone connectivity (different class wave spectrums supported) can be triangulated using the best available information (i.e. heterogeneous location technique). Examination offields 1100 f inFIG. 17 can show wave spectrums (and/or particular communications interfaces 70) inserted by receive processing for what the MS supports. If block 2664 determines an AOA measurement is present (field 1100 f sub-field), then block 2666 appends the WDR to the ANGLE list, and processing continues to block 2668. If block 2664 determines an AOA measurement is not present, then processing continues to block 2670. If block 2670 determines a TDOA measurement is present (field 1100 f sub-field), then block 2672 appends the WDR to the DISTANCE list, and processing continues to block 2674. Block 2674 uses WDRs for providing at least an in-range whereabouts of this MS by inserting to the THIS_MS list in sorted confidence priority order (e.g. highest confidence first in list, lowest confidence at end of list). Block 2674 continues to block 2668. Block 2674 may cause duplicate WDR(s) inserted to the THIS_MS list, but this will have no negative effect on selected outcome. - Block 2668 compares the ANGLE and DISTANCE lists constructed thus far from loop processing (blocks 2660 through 2682) with minimum triangulation requirements (e.g. see “Missing Part Triangulation (MPT)” above). Three (3) sides, three (3) angles and a side, and other known triangular solution guides will also be compared. Thereafter, if block 2676 determines there is still not enough data to triangulate whereabouts of this MS, then processing continues back to block 2660 for the next REMOTE_MS list entry, otherwise block 2678 maximizes diversity of WDRs to use for triangulating. Thereafter, block 2680 uses the diversified DISTANCE and ANGLE lists to perform triangulation of this MS, block 2682 inserts the newly determined WDR into the THIS_MS list in sort key order, and continues back to block 2660. Block 2680 will use heterogeneous (MPT), TDOA and/or AOA triangulation on ANGLE and DISTANCE lists for determining whereabouts.
- Block 2682 preferably keeps track of (or checks THIS_MS for) what it has thus far determined whereabouts for in this
FIG. 26B thread processing to prevent inserting the same WDR to THIS_MS using the same REMOTE_MS data. Repeated iterations of blocks 2676 through 2682 will see the same data from previous iterations and will use the best of breed data in conjunction with each other at each iteration (in current thread context). While inserting duplicates to THIS_MS at block 2682 does not cause failure, it may be avoided for performance reasons. Duplicate insertions are preferably avoided at block 2674 for performance reasons as well, but they are again not harmful. Block 2678 preferably keeps track of previous diversity order in thisFIG. 26B thread processing to promote using new ANGLE and DISTANCE data in whereabouts determination at block 2680 (since each iteration is a superset of a previous iteration (in current thread context)). Block 2678 promotes using WDRs from different MSs (different MS IDs), and from MSs located at significantly different whereabouts (e.g. to maximize surrounded-ness), preferably around the MS ofFIG. 26B processing. Block 2678 preferably uses sorted diversity pointer lists so as to not affect actual ANGLE and DISTANCE list order. The sorted pointer lists provide pointers to entries in the ANGLE and DISTANCE lists for a unique sorted order governing optimal processing at block 2680 to maximize unique MSs and surrounded-ness, without affecting the lists themselves (like a SQL database index). Different embodiments of blocks 2678 through 2682 should minimize inserting duplicate WDRs (for performance reasons) to THIS_MS which were determined using identical REMOTE_MS list data. Block 2682 causes using ADLT at blocks 2684 through 2688 which uses the best of breed whereabouts, either as originated by this MS maintained in THIS_MS list up to the thread processing point of block 2686, or as originated by remote MSs (DLMs and/or ILMs) processed by blocks 2656 through the start of block 2684. - Referring back to block 2662, if it is determined that all WDRs in the REMOTE_MS list have been processed, then block 2684 sets the BESTWDR reference to the head of THIS_MS (i.e. BESTWDR references first WDR in THIS_MS list which is so far the best candidate WDR (highest confidence) for this MS whereabouts, or null if the list is empty). It is possible that there are other WDRs with matching confidence adjacent to the highest confidence entry in the THIS_MS list. Block 2684 continues to block 2686 for comparing matching confidence WDRs, and if there are matches, then breaking a tie between WDRs with matching confidence by consulting any other WDR field(s) (
e.g. field 1100 f signal strength, or location technology field 1100 e, etc). If there is still a tie between a plurality of WDRs, then block 2686 may average whereabouts to the BESTWDR WDR using the matching WDRs. Thereafter processing continues to block 2688 where the BESTWDR is completed, and processing terminates at block 2690. Block 2688 also frees resources (if any) allocated byFIG. 26B processing (e.g. lists). Blocks 2686 through 2688 result in setting BESTWDR to the highest priority WDR (i.e. the best possible whereabouts determined). It is possible thatFIG. 26B processing causes a duplicate WDR inserted to queue 22 (at block 2620) for this MS whereabouts determination, but that is no issue except for impacting performance to queue 22. An alternate embodiment to queue 22 may define a unique index for erring out when inserting a duplicate to prevent frivolous duplicate entries, or block 2688 will incorporate processing to eliminate the chance of inserting a WDR of less use than what is already contained atqueue 22. Therefore, block 2688 may include processing for ensuring a duplicate will not be inserted (e.g. null the BESTWDR reference) prior to returning toFIG. 26A at block 2690. - Averaging whereabouts at block 2686 occurs only when there are WDRs at the head of the list with a matching highest confidence value and still tie in other WDR fields consulted, yet whereabouts information is different. In this case, all matching highest confidence whereabouts are averaged to the BESTWDR to come up with whereabouts in light of all matching WDRs. Block 2686 performs ADLT when finalizing a single whereabouts (WDR) using any of the whereabouts found in THIS_MS (which may contain at this point DLM whereabouts originated by this MS and/or whereabouts originated by remote DLMs and/or ILMs). Block 2686 must be cognizant of sort keys used at blocks 2652 and 2654 in case confidence is not the primary key (time may be primary).
- If no WDRs were found at block 2634, or no THIS_MS list WDRs were found at blocks 2652 and 2654, and no REMOTE_MS list entries were found at block 2644; or no THIS_MS list WDRs were found at blocks 2652 and 2654, and no REMOTE_MS list entries were found useful at blocks 2664 and/or 2670; then block 2684 may be setting BESTWDR to a null reference (i.e. none in list) in which case block 2686 does nothing. Hopefully, at least one good WDR is determined for MS whereabouts and a new WDR is inserted for this MS to queue 22, otherwise a null BESTWDR reference will be returned (checked at block 2616). See
FIG. 11A descriptions. If BESTWDR is not null, then fields are set to the following upon exit from block 2688: -
MS ID field 1100 a is preferably set with: MS ID of MS ofFIG. 26B processing.
DATE/TIME STAMP field 1100 b is preferably set with: Date/time stamp of block 2688 processing.
LOCATION field 1100 c is preferably set with: Resulting whereabouts after block 2688 completion.
CONFIDENCE field 1100 d is preferably set with: WDR Confidence at THIS_MS list head.
LOCATION TECHNOLOGY field 1100 e is preferably set with: “mM TDOA Triangulation”, “mM AOA Triangulation”, “mM MPT Triangulation” or “mM in-range”, as determined by the WDRs inserted to MS LIST at blocks 2674 and 2682. The originator indicator is set to ILM.
LOCATIONREFERENCE INFO field 1100 f is preferably set with: null (not set), but may be set with contributing data for analysis ofqueue 22 provided it is marked for being overlooked by future processing of blocks 2646 and 2648 (e.g. for debug purpose).
COMMUNICATIONSREFERENCE INFO field 1100 g is preferably set with: null (not set).
SPEED field 1100 h is preferably set with: Block 2688 may compare prioritized entries and their order of time (field 1100 b) in THIS_MS list for properly setting this field, if possible.
HEADING field 1100 i is preferably set with: null (not set). Block 2688 may compare prioritized entries and their order of time (field 1100 b) in THIS_MS list for properly setting this field, if possible.
ELEVATION field 1100 j is preferably set with: Field 1100 j of BESTWDR (may be averaged if WDR tie(s)), if available.
APPLICATION FIELDS field 1100 k is preferably set with: Field(s) 1100 k from BESTWDR or tie(s) thereof from THIS_MS. An alternate embodiment will add, alter, or discard data (with or without date/time stamps) here at the time of block 2688 processing.
CORRELATION FIELD 1100 m is preferably set with: Not Applicable (i.e. not maintained to queue 22).
SENT DATE/TIME STAMP field 1100 n is preferably set with: Not Applicable (i.e. not maintained to queue 22).
RECEIVED DATE/TIME STAMP field 1100 p is preferably set with: Not Applicable (i.e. not maintained to queue 22). - Block 2680 determines whereabouts using preferred guidelines, such as whereabouts determined never results in a confidence value exceeding any confidence value used to determine whereabouts. Some embodiments will use the mean (average) of confidence values used, some will use the highest, and some the lowest of the WDRs used. Preferred embodiments tend to properly skew confidence values to lower values as the LN-Expanse grows away from
region 1022. Blocks 2668 through 2680 may consult any of the WDR fields (e.g. field 1100 f sub-fields yaw, pitch, roll; speed, heading, etc) to deduce the most useful WDR inputs for determining an optimal WDR for this MS whereabouts. - Thread(s) 1952 are started for every WDR collected from remote MSs. Therefore, it is possible that identical new WDRs are inserted to queue 22 using the same WDR information at blocks 2634 of simultaneously executing
threads 1952, but this will not cause a problem since at least one will be found when needed, and duplicates will be pruned together when appropriate. Alternative embodiments provide IPC (Interprocess Communications Processing) coordination between 1952 threads for higher performance processing, for example: -
- As mentioned above, thread(s) 1952 can coordinate with each other to know successes, failures or progress of their
sister 1952 thread(s) for automatically adjusting the trailing f(WTV) period of time appropriately. The f(WTV) period of time used at block 2634 would be semaphore accessed and modified (e.g. increased) for another 1952 thread when a previous 1952 thread was unsuccessful in determining whereabouts (via semaphore accessed thread outcome indicator). After a successful determination, the f(WTV) period of time could be reset back to the smaller window. One embodiment of increasing may start with 10% of the WTV, then 20% at the next thread, 30% at the next thread, up to 90%, until a successful whereabouts is determined. After successful whereabouts determination, a reset to its original starting value is made. - A semaphore accessed
thread 1952 busy flag is used for indicating a certain thread is busy to prevent another 1952 thread from doing the same or similar work. Furthermore, other semaphore protected data for what work is actually being performed by a thread can be informative to ensure that nothread 1952 starts for doing duplicated effort. - Useful data of
statistics 14 may be appropriately accessed by thread(s) 1952 for dynamically controlling key variables ofFIG. 26B processing, such as the search f(WTV) time period, sort keys used, when to quit loop processing (e.g. on first successful whereabouts determination at block 2680), surrounded-ness preferences, etc. This can dynamically change theFIG. 26B logic from one thread to another for desired results.
- As mentioned above, thread(s) 1952 can coordinate with each other to know successes, failures or progress of their
-
FIG. 26B continues processing through every WDR retrieved at block 2634. An alternative embodiment will terminate processing after finding the first (which is highest priority data supported) successful triangulation at block 2682. -
FIG. 27 depicts a flowchart for describing a preferred embodiment of queue prune processing. Queue pruning is best done on an interim basis by threads which may insert to the queue being pruned. In an alternate embodiment, a background asynchronous thread will invokeFIG. 27 for periodic queue pruning to ensure no queue which can grow becomes too large. The Prune Queues procedure starts atblock 2702 and continues to block 2704 where parameters passed by a caller for which queue(s) (WDR and/or CR) to prune are determined. Thereafter, ifblock 2706 determines that the caller wanted to prune theWDR queue 22,block 2708 appropriately prunes the queue, for example discarding oldentries using field 1100 b, and processing continues to block 2710. Ifblock 2706 determines that the caller did not want to prune theWDR queue 22, then processing continues to block 2710. Ifblock 2710 determines that the caller wanted to prune theCR queue 1990, block 2712 appropriately prunes the queue, for example discarding oldentries using field 2450 a, and processing continues to block 2714. Ifblock 2710 determines that the caller did not want to prune theCR queue 1990, then processing continues to block 2714.Block 2714 appropriately returns to the caller. - The current design for
queue 1980 does not requireFIG. 27 to prune it. Alternative embodiments may add additional queues for similar processing. Alternate embodiments may useFIG. 27 like processing to prunequeues block 2704 may also include how to prune the queue, for example when using different constraints for what indicates entry(s) for discard. -
FIG. 28 depicts a flowchart for describing a preferred embodiment of MS termination processing. Depending on the MS, there are many embodiments of processing when the MS is powered off, restarted, rebooted, reactivated, disabled, or the like.FIG. 28 describes the blocks of processing relevant to the present disclosure as part of that termination processing. Termination processing starts atblock 2802 and continues to block 2804 for checking any DLM roles enabled and appropriately terminating if any are found (for example as determined from persistent storage variable DLMV).Block 2804 may cause the termination of thread(s) associated with enabled DLM role(s) for DLM processing above (e.g.FIGS. 2A through 9B ).Block 2804 may invoke API(s), disable flag(s), or terminate as is appropriate for DLM processing described above. Such terminations are well known in the art of prior art DLM capabilities described above.Block 2804 continues to block 2806. -
Blocks 2806 through 2816 handle termination of all processes/threads associated with the ILMV roles so there is no explicit ILMV check required.Block 2806 initializes an enumerated process name array for convenient processing reference of associated process specific variables described inFIG. 19 , and continues to block 2808 where the first member of the set is accessed for subsequent processing. The enumerated set of process names has a prescribed termination order forMS architecture 1900. Thereafter, ifblock 2810 determines the process identifier (i.e. 19 xx-PID such that 19 xx is 1902, 1912, 1922, 1932, 1942, 1952 in a loop iteration ofblocks 2808 through 2816) is greater than 0 (e.g. this first iteration of 1912-PID>0 implies it is to be terminated here; also impliesprocess 1912 is enabled as used inFIGS. 14A , 28, 29A and 29B), then block 2812 prepares parameters forFIG. 29B invocation, andblock 2814 invokes (calls) the procedure ofFIG. 29B to terminate the process (of this current loop iteration (19 xx)).Block 2812 prepares the second parameter in accordance with the type of 19 xx process. If the process (19 xx) is one that is slave to a queue for dictating its processing (i.e. blocked on queue until queue entry present), then the second parameter (process type) is set to 0 (directingFIG. 29A processing to insert a special termination queue entry to be seen by worker thread(s) for terminating). If the process (19 xx) is one that is slave to a timer for dictating its processing (i.e. sleeps until it is time to process), then the second parameter (process type) is set to the associated 19 xx-PID value (directingFIG. 29B to use in killing/terminating the PID in case the worker thread(s) are currently sleeping).Block 2814 passes the process name and process type as parameters toFIG. 29B processing. Upon return fromFIG. 29B ,block 2814 continues to block 2816. Ifblock 2810 determines that the 19 xx process is not enabled, then processing continues to block 2816. Upon return fromFIG. 29B processing, the process is terminated and the associated 19 xx-PID variable is already set to 0 (seeblocks -
Block 2816 checks to see if all process names of the enumerated set (19 xx) have been processed (iterated) byblocks 2808 through 2816. Ifblock 2816 determines that not all process names in the set have been processed (iterated), then processing continues back to block 2808 for handling the next process name in the set. Ifblock 2816 determines that all process names of the enumerated set were processed, then block 2816 continues to block 2818. -
Block 2818 destroys semaphore(s) created atblock 1220. Thereafter,block 2820 destroys queue(s) created at block 1218 (may have to remove all entries first in some embodiments), block 2822 saves persistent variables to persistent storage (for example to persistent storage 60),block 2824 destroys shared memory created atblock 1212, and block 2826 checks the NTP use variable (saved prior to destroying shared memory at block 2824). - If
block 2826 determines NTP is enabled, then block 2828 terminates NTP appropriately (also see block 1612) and processing continues to block 2830. Ifblock 2826 determines NTP was not enabled, then processing continues to block 2830.Block 2828 embodiments are well known in the art of NTP implementations.Block 2828 may cause terminating of thread(s) associated with NTP use. -
Block 2830 completes LBX character termination, then block 2832 completesother character 32 termination processing, andFIG. 28 processing terminates thereafter atblock 2834. Depending on what threads were started at block 1240, block 2830 may terminate the listen/receive threads for feedingqueue 26 and the send threads for sending data inserted to queue 24. Depending on what threads were started atblock 1206, block 2832 may terminate the listen/receive threads for feedingqueue 26 and the send threads for sending data inserted to queue 24 (i.e.other character 32 threads altered to cause embedded CK processing). Upon encounter ofblock 2834, the MS is appropriately terminated for reasons at set forth above for invokingFIG. 28 . - With reference now to
FIG. 29B , depicted is a flowchart for describing a preferred embodiment of a procedure for terminating a process started byFIG. 29A . When invoked by a caller, the procedure starts atblock 2952 and continues to block 2954 where parameters passed are determined. There are two parameters: the process name to terminate, and the type of process to terminate. The type of process is set to 0 for a process which has worker threads which are a slave to a queue. The type of process is set to a valid O/S PID when the process worker threads are slave to a timer. - Thereafter, if
block 2956 determines the process type is 0, then block 2958 initializes a loop variable J to 0, and block 2960 inserts a special termination request queue entry to the appropriate queue for the process worker thread to terminate. SeeFIG. 19 discussions for the queue inserted for which 19 xx process name. - Thereafter, block 2962 increments the loop variable by 1 and block 2964 checks if all process prescribed worker threads have been terminated.
Block 2964 accesses the 19 xx-Max (e.g. 1952-Max) variable from shared memory using a semaphore for determining the maximum number of threads to terminate in the process worker thread pool. Ifblock 2964 determines all worker threads have been terminated, processing continues to block 2966 for waiting until the 19 xx-PID variable is set to disabled (e.g. set to 0 by block 2922), and then to block 2978 which causes return to the caller.Block 2966 uses a preferred choice of waiting described forblocks block 2966 may use the 19 xx-PID variable, or may be signaled by the last terminating worker thread, or byblock 2922. - If
block 2964 determines that not all worker threads have been terminated yet, then processing continues back to block 2960 to insert another special termination request queue entry to the appropriate queue for the next process worker thread to terminate.Blocks 2960 through 2964 insert the proper number of termination queue entries to the same queue so that all of the 19 xx process worker threads terminate. - Referring back to
block 2956, if it is determined the process type is not 0 (i.e. is a valid O/S PID), then block 2968 inserts aspecial WDR queue 22 entry enabling a queue peek for worker thread termination. The reader will notice that the process termination order ofblock 2806 ensures processes which were slaves to theWDR queue 22 have already been terminated. This allows processes which are slaves to a timer to see the special termination queue entry inserted atblock 2968 since no threads (which are slaves to queue) will remove it fromqueue 22. Thereafter, block 2970 waits until the 19 xx process name (parameter) worker threads have been terminated using a preferred choice of waiting described forblocks block 2970 may use the 19 xx-PID variable, or may be signaled by the last terminating worker thread, or byblock 2922.Block 2970 also preferably waits for a reasonable timeout period in anticipation of known sleep time of the 19 xx process being terminated, for cases where anticipated sleep times are excessive and the user should not have to wait for lengthyFIG. 28 termination processing. If the timeout occurs before the process is indicated to be terminated, then block 2970 will continue to block 2972.Block 2970 also continues to block 2972 when the process has successfully terminated. - If
block 2972 determines the 19 xx process did terminate, the caller is returned to at block 2978 (i.e. 19 xx-PID already set to disabled (0)). Ifblock 2972 determines the 19 xx process termination timed out, then block 2974 forces an appropriate O/S kill to the PID thereby forcing process termination, and block 2976 sets the 19 xx-PID variable for disabled (i.e. process 19 xx was terminated). Thereafter, block 2978 causes return to the caller. - There are many embodiments for setting certain queue entry field(s) identifying a special queue termination entry inserted at
blocks queue 26 insertion of a WDR preferably sets the MS ID field with a value that will never appear in any other case except a termination request (e.g. −100). In the case of terminating thread(s) 1902, 1922 and 1952,queue 22 insertion of a WDR preferably sets the MS ID field with a value that will never appear in any other case except a termination request (e.g. −100). In the case of terminating thread(s) 1942,queue 26 insertion of a WDR request preferably sets the MS ID field with a value that will never appear in any other case except a termination request (e.g. −100). In the case of terminating thread(s) 1932,queue 1980 insertion of a threadrequest queue record 2400 preferably setsfield 2400 a with a value that will never appear in any other case except a termination request (e.g. −100). Of course, any available field(s) can be used to indicate termination to particular thread(s)). - Terminating threads of processing in
FIG. 29B has been presented from a software perspective, but there are hardware/firmware thread embodiments which may be terminated appropriately to accomplish the same functionality. If the MS operating system does not have an interface for killing the PID atblock 2974, then blocks 2972 through 2976 can be eliminated for relying on aFIG. 28 invocation timeout (incorporated for block 2814) to appropriately rob power from remaining thread(s) of processing. - An ILM has many methods and systems for knowing its own location. LBX depends on MSs maintaining their own whereabouts. No service is required to maintain the whereabouts of MSs in order to accomplish novel functionality.
- As mentioned above,
architecture 1900 provides a set of processes which can be started or terminated for desired functionality. Thus,architecture 1900 provides a palette from which to choose desired deployment methods for an LN expanse. - In some embodiments, all whereabouts information can be pushed to expand the LN-expanse. In such embodiments, the palette of processes to choose from includes at
least process 1902,process 1912 andprocess 1952. Additionally,process 1932 would be required in anticipation of LN-expanse participating data processing systems having NTP disabled or unavailable. Additionally,process 1922 could be used for ensuring whereabouts are timely (e.g. specifically using all blocks except 2218 through 2224). Depending on DLM capability of MSs in the LN-expanse, a further subset ofprocesses - In some embodiments, all whereabouts information can be pulled to expand the LN-expanse. In such embodiments, the palette of processes to choose from includes at least process 1922 (e.g. specifically using all blocks except 2226 and 2228),
process 1912,process 1952 andprocess 1942. Additionally,process 1932 would be required in anticipation of LN-expanse participating data processing systems having NTP disabled or unavailable. Depending on DLM capability of MSs in the LN-expanse, a further subset ofprocesses - There are many embodiments derived from
architecture 1900. Essential components are disclosed for deployment varieties. In communications protocols which acknowledge a transmission, processes 1932 may not be required even in absence of NTP use. A sending MS appends a sent date/time stamp (e.g. field 1100 n) on its time scale to outbound data 1302 and an acknowledging MS (or service) responds with the sent date/time stamp so that when the sending MS receives it (receivesdata 1302 or 1312), the sending MS (now a receiving MS) calculates a TDOA measurement by comparing when the acknowledgement was received and when it was originally sent. Appropriate correlation outside ofprocess 1932 deployment enables the sending MS to know which response went with whichdata 1302 was originally sent. A MS can make use of 19 xx processes as is appropriate for functionality desired. - In push embodiments disclosed above, useful summary observations are made. Service(s) associated with antennas periodically broadcast (beacon) their reference whereabouts (e.g. WDR information) for being received by MSs in the vicinity. When such services are NTP enabled, the broadcasts include a sent date/time stamp (
e.g. field 1100 n). Upon receipt by a NTP enabled MS in the vicinity, the MS uses the date/time stamp of MS receipt (e.g. 1100 p) with the date/time stamp of when sent (e.g. field 1100 n) to calculate a TDOA measurement. Known wave spectrum velocity can translate to a distance. Upon receipt of a plurality of these types of broadcasts from different reference antennas, the MS can triangulate itself for determining its whereabouts relative known whereabouts of the reference antennas. Similarly, reference antennas are replaced by other NTP enabled MSs which similarly broadcast their whereabouts. A MS can be triangulated relative a mixture of reference antennas and other NTP enabled MSs, or all NTP enabled MSs. Stationary antenna triangulation is accomplished the same way as triangulating from other MSs. NTP use allows determining MS whereabouts using triangulation achievable in a single unidirectional broadcast of data (1302 or 1312). Furthermore, reference antennas (service(s)) need not communicatenew data 1312, and MSs need not communicatenew data 1302.Usual communications data 1312 are altered with aCK 1314 as described above.Usual communications data 1302 are altered with aCK 1304 as described above. This enables a MS with not only knowing there are nearby hotspots, but also where all parties are located (including the MS). Beaconing hotspots, or other broadcasters, do not need to know who you are (the MS ID), and you do not need to know who they are in order to be located. Various bidirectional correlation embodiments can always be used for TDOA measurements. - In pull embodiments disclosed above, data processing systems wanting to determine their own whereabouts (requestors) broadcast their requests (e.g. record 2490). Service(s) or MSs (responders) in the vicinity respond. When responders are NTP enabled, the responses include a sent date/time stamp (
e.g. field 1100 n) that by itself can be used to calculate a TDOA measurement if the requestor is NTP enabled. Upon receipt by a requestor with no NTP, the requestor uses the date/time stamp of a correlated receipt (e.g. 1100 p) with the date/time stamp of when sent (e.g. fields - If NTP is available to a data processing system, it should be used whenever communicating date/time information (e.g. NTP bit of
field e.g. fields e.g. field 1100 n) and then becomes a first (sending) data processing as described in the send initiated embodiment. Whatever embodiment is used, it is beneficial in the LN-expanse to minimize communications traffic. - The NTP bit in date/time stamps enables optimal elegance in the LN-expanse for taking advantage of NTP when available, and using correlated transmissions when it is not. A NTP enabled MS is somewhat of a chameleon in using unidirectional data (1302 or 1312 received) to determine whereabouts relative NTP enabled MS(s) and/or service(s), and then using bidirectional data (1302/1302 or 1302/1312) relative MS(s) and/or service(s) without NTP. A MS is also a chameleon when considering it may go in and out of a DLM or ILM identity/role, depending on what whereabouts technology is available at the time.
- The MS ID (or pseudo MS ID) in transmissions is useful for a receiving data processing system to target a response by addressing the response back to the MS ID. Targeted transmissions target a specific MS ID (or group of MS IDs), while broadcasting is suited for reaching as many MS IDs as possible. Alternatively, just a correlation is enough to target a data source.
- In some embodiments where a MS is located relative another MS, this is applicable to something as simple as locating one data processing system using the location of another data processing system. For example, the whereabouts of a cell phone (first data processing system) is used to locate an in-range automotive installed (second) data processing system for providing new locational applications to the second data processing system (or visa-versa). In fact, the second data processing may be designed for using the nearby first data processing system for determining its whereabouts. Thus, as an MS roams, in the know of its own whereabouts, the MS whereabouts is shared with nearby data processing systems for new functionality made available to those nearby data processing systems when they know their own whereabouts (by associating to the MS whereabouts). Data processing systems incapable of being located are now capable of being located, for example locating a data processing equipped shopping cart with the location of an MS, or plurality of MSs.
-
Architecture 1900 presents a preferred embodiment for IPC (Interprocess Communications Processing), but there are other embodiments for starting/terminating threads, signaling between processes, semaphore controls, and carrying out present disclosure processing without departing from the spirit and scope of the disclosure. In some embodiments, threads are automatically throttled up or down (e.g. 1952-Max) per unique requirements of the MS as determined by how often threads loop back to find an entry already waiting in a queue. If thread(s) spend less time blocked on queue, they can be automatically throttled up. If thread(s) spend more time blocked on queue, they can be automatically throttled down. Timers can be associated with queue retrieval to keep track of time a thread is blocked. - LBX
history 30 preferably maintains history information of key points in processing where history information may prove useful at a future time. Some of the useful points of interest may include: -
- Interim snapshots of permissions 10 (for documenting who had what permissions at what time) at
block 1478; - Interim snapshots of charters 12 (for documenting charters in effect at what times) at
block 1482; - Interim snapshots of statistics 14 (for documenting useful statistics worthy of later browse) at
block 1486; - Interim snapshots of service propagation data of
block 1474; - Interim snapshots of service informant settings of
block 1490; - Interim snapshots of LBX history maintenance/configurations of
block 1494; - Interim snapshots of a subset of WDR
queue 22 using a configured search criteria; - Interim snapshots of a subset of Send
queue 24 using a configured search criteria; - Interim snapshots of a subset of
Receive queue 26 using a configured search criteria; - Interim snapshots of a subset of
PIP data 8; - Interim snapshots of a subset of
data 20; - Interim snapshots of a subset of
data 36; - Interim snapshots of
other resources 38; - Trace, debug, and/or dump of any execution path subset of processing flowcharts described; and/or
- Copies of data at any block of processing in any flowchart heretofore described.
Entries inLBX history 30 preferably have entry qualifying information including at least a date/time stamp of when added to history, and preferably an O/S PID and O/S TID (Thread Identifier) associated with the logged entry, and perhaps applicable applications involved (e.g. seefields 1100 k).History 30 may also be captured in such a way there are conditions set up in advance (at block 1494), and when those conditions are met, applicable data is captured tohistory 30. Conditions can include terms that are MS system wide, and when the conditions are met, the data for capture is copied to history. In these cases,history 30 entries preferably include the conditions which were met to copy the entry to history. Depending on what is being kept tohistory 30, this can become a large amount of information. Therefore,FIG. 27 can include new blocks for pruninghistory 30 appropriately. In another embodiment, a separate thread of processing has a sleeper loop which when awake will prune thehistory 30 appropriately, either in its own processing or by invoking newFIG. 27 blocks forhistory 30. A parameter passed to processing byblock 2704 may include how to prune the history, including what data to prune, how old of data to prune, and any other criteria appropriate for maintaininghistory 30. In fact, any pruning byFIG. 27 may include any reasonable parameters for how to prune particular data of the present disclosure.
- Interim snapshots of permissions 10 (for documenting who had what permissions at what time) at
- Location applications can use the WDR queue for retrieving the most recent highest confidence entry, or can access the single instance WDR maintained (or most recent WDR of block 289 discussed above). Optimally, applications are provided with an API that hides what actually occurs in ongoing product builds, and for ensuring appropriate semaphore access to multi-threaded accessed data.
- Correlation processing does not have to cause a WDR returned. There are embodiments for minimal exchanges of correlated sent date/time stamps and/or received date/time stamps so that exchanges are very efficient using small data exchanges. Correlation of this disclosure was provided to show at least one solution, with keeping in mind that there are many embodiments to accomplish relating time scales between data processing systems.
-
Architecture 1900 provides not only the foundation for keeping an MS abreast of its whereabouts, but also the foundation upon which to build LBX nearby functionality. Whereabouts of MSs in the vicinity are maintained to queue 22.Permissions 10 andcharters 12 can be used for governing which MSs to maintain to queue 22, how to maintain them, and what processing should be performed. For example, MS user Joe wants to alert MS user Sandy when he is in her vicinity, or user Sandy wants to be alerted when Joe is in her vicinity. Joe configures permissions enabling Sandy to be alerted with him being nearby, or Sandy configured permissions for being alerted. Sandy accepts the configuration Joe made, or Joe accepts the configuration Sandy made. Sandy'squeue 22 processing will ensure Joe's WDRs are processed uniquely for desired functionality. -
FIG. 8C was presented in the context of a DLM, howeverarchitecture 1900 should be applied for enabling a user to manually request to be located with ILM processing if necessary.Blocks 862 through 870 are easily modified to accomplish a WDR request (like blocks 2218 through 2224). In keeping with current block descriptions, block 872 would become a new series of blocks for handling the case when DLM functionality was unsuccessful. New block 872-A would broadcast a WDR request soliciting response (see blocks 2218 through 2224). Thereafter, a block 872-B would wait for a brief time, and subsequently a block 872-C would check to see if whereabouts have been determined (e.g. check queue 22). Thereafter, if a block 872-D determines whereabouts were not determined, an error could be provided to the user, otherwise the MS whereabouts were successfully determined and processing continues to block 874. Applications that may need whereabouts can now be used. There are certainly emergency situations where a user may need to rely on other MSs in the vicinity for being located. - To maintain modularity in interfaces to
queues e.g. field 1100 a), perhaps also withfield 1100 f indicating which communications interface to send on (e.g. MS has plurality of comm. interfaces 70). When WDRs are “broadcast” (e.g. null MS ID), the WDR is preferably outbound on all available comm. interfaces 70), unlessfield 1100 f indicates to target a comm. interface. Analogously, when WDR requests are “sent”, the request will be targeted (e.g. field 2490 a), perhaps also withfield 2490 d indicating which communications interface to send on (e.g. MS has plurality of comm. interfaces 70). When WDR requests are “broadcast” (e.g. null MS ID), the WDR is preferably outbound on all available comm. interfaces 70), unlessfield 1100 f indicates to target a comm. interface. -
Fields - An alternate embodiment to the BESTWDR WDR returned by
FIG. 26B processing may be set with useful data for reuse toward a futureFIG. 26B processing thread whereabouts determination.Field 1100 f (see pg. 168) can be set with useful data for that WDR to be in turn used at a subsequent whereabouts determination ofFIG. 26B . This is referred to as Recursive Whereabouts Determination (RWD) wherein ILMs determine WDRs for their whereabouts and use them again for calculating future whereabouts (by populating useful TDOA, AOA, MPT and/or whereabouts information to field 1100 f). - An alternate embodiment may store remote MS movement tolerances (if they use one) to
WDR field 1100 f so the receiving MS can determine how stale are other WDRs inqueue 22 from the same MS, for example when gathering all useful WDRs to start with in determining whereabouts ofFIG. 26B processing (e.g. block 2634). Having movement tolerances in effect may prove useful for maximizing useful WDRs used in determining a whereabouts (FIG. 26B processing). - While various embodiments of the present disclosure have been described above, it should be understood that 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.
Claims (20)
1. A program product that, when executed, causes operations comprising:
receiving, by a mobile data processing system, a plurality of wireless data records from a plurality of data processing systems determined by the mobile data processing system to have been in a wireless vicinity of the mobile data processing system, wherein the plurality of wireless data records are received by the mobile data processing system with a purely peer to peer interaction asynchronously from any user interface of the mobile data processing system;
storing, by the mobile data processing system, searchable information for each record of the plurality of wireless data records from the plurality of data processing systems in a historical collection for query with a conditional match specification, wherein the conditional match specification is for comparing to at least one data field of the searchable information for the each record in the historical collection for query, wherein the each record includes at least originating identifier information and application information;
storing, by the mobile data processing system, information for a data record of the mobile data processing system for comparison to the searchable information for the each record in the historical collection for query;
accepting, by the mobile data processing system, a search request for searching the searchable information for the each record in the historical collection for query, the search request including the conditional match specification for comparing to the at least one data field of the searchable information for the each record in the historical collection for query;
searching, by the mobile data processing system, the searchable information for the each record in the historical collection for query, upon the accepting;
retrieving, by the mobile data processing system, one or more entries from the historical collection for query, upon the searching, wherein the one or more entries correspond to one or more of the plurality of wireless data records and each of the one or more entries has at least one data field matching the conditional match specification; and
communicating, by the mobile data processing system, information for the one or more entries from the historical collection for query to request processing of the search request at the mobile data processing system.
2. The program product of claim 1 wherein the receiving, by the mobile data processing system, the plurality of wireless data records from the plurality of data processing systems determined by the mobile data processing system to have been in the wireless vicinity of the mobile data processing system includes receiving the plurality of wireless data records from a plurality of other mobile data processing systems.
3. The program product of claim 1 wherein the retrieving, by the mobile data processing system, one or more entries from the historical collection for query includes retrieving the one or more entries in a sorted order.
4. The program product of claim 3 wherein the sorted order is determined with a sort specification of the search request.
5. The program product of claim 3 wherein the sorted order is an order by sorting on a plurality of data fields of the searchable information for the each record in the historical collection for query.
6. The program product of claim 1 wherein the search request is a SQL search request.
7. The program product of claim 1 that, when executed, causes the operations including presenting the information for the one or more entries to a user interface.
8. The program product of claim 7 wherein the user interface is for a user to manage the one or more entries by at least one of: view the one or more entries, delete the one or more entries, modify the one or more entries, or add to the one or more entries.
9. The program product of claim 1 that, when executed, causes the operations including providing an alert for a device that is nearby.
10. The program product of claim 1 that, when executed, causes the operations including transmitting outbound, by the mobile data processing system, the information for the data record of the mobile data processing system.
11. The program product of claim 1 that, when executed, causes the operations including maintaining, by the mobile data processing system, a Location Based eXchange behavior conditional expression for how the mobile data processing system should interact with the plurality of data processing systems determined by the mobile data processing system to have been in the wireless vicinity of the mobile data processing system.
12. The program product of claim 1 that, when executed, causes the operations including maintaining the searchable information for the each record in the historical collection for query according to a permission configured by a particular user.
13. The program product of claim 1 wherein the searchable information for the each record in the historical collection for query includes at least one of:
information for a location technology,
information for a triangulation measurement,
information for a time difference of arrival measurement,
information for a time of arrival measurement,
information for an angle of arrival measurement,
information for a yaw measurement,
information for a pitch measurement,
information for a roll measurement,
information for an accelerometer measurement,
information for distinguishing an elevation or altitude,
information for a communications signal strength of a transmission,
information for a communications wave spectrum characteristic of a transmission,
information for a communications wave spectrum class of a transmission,
information for a communications wave spectrum frequency of a transmission,
information received by the particular data processing system from a remote data processing system that is remote to the particular data processing system,
information maintained by an application,
information for an application in use,
information for an application context of an application,
information for a navigation Application Programming Interface,
information for a location,
information for a situational location,
information for a speed,
information for a heading,
time information,
information for at least one service,
is information for service criteria,
information for an environmental condition,
information for a web site,
information for a physical address,
information for a logical address,
information for a transaction,
information for a user configuration,
information for monitoring movement,
information for an identifier associated with the particular data processing system, or
information in accordance with one or more permissions configured by a user associated with the particular data processing system.
14. The program product of claim 13 that, when executed, causes the operations including determining location information of the mobile data processing system.
15. The program product of claim 1 that, when executed, causes the operations including governing, by the mobile data processing system, with a user configuration what receipt processing should be performed for the each record of the plurality of wireless data records from the plurality of data processing systems, wherein the receipt processing depends on the user configuration for distinguishing one wireless data record of the plurality of wireless data records from another wireless data record of the plurality of wireless data records.
16. The program product of claim 15 wherein the user configuration is configured by a user of the mobile data processing system for providing permission to an identity of at least one of the plurality of data processing systems determined by the mobile data processing system to have been in the wireless vicinity of the mobile data processing system.
17. The program product of claim 15 wherein the user configuration is configured by a user of at least one of the plurality of data processing systems determined by the mobile data processing system to have been in the wireless vicinity of the mobile data processing system for providing permission to an identity of the mobile data processing system.
18. The program product of claim 15 wherein the user configuration enables providing an alert for a device that is nearby.
19. A storage device storing a program that, when executed, causes operations comprising:
receiving, by a mobile data processing system, a plurality of wireless data records from a plurality of data processing systems determined by the mobile data processing system to have been in a wireless vicinity of the mobile data processing system, wherein the plurality of wireless data records are received by the mobile data processing system with a purely peer to peer interaction asynchronously from any user interface of the mobile data processing system;
storing, by the mobile data processing system, searchable information for each record of the plurality of wireless data records from the plurality of data processing systems in a historical collection for query with a conditional match specification, wherein the conditional match specification is for comparing to at least one data field of the searchable information for the each record in the historical collection for query, wherein the each record includes at least originating identifier information and application information;
storing, by the mobile data processing system, information for a data record of the mobile data processing system for comparison to the searchable information for the each record in the historical collection for query;
accepting, by the mobile data processing system, a search request for searching the searchable information for the each record in the historical collection for query, the search request including the conditional match specification for comparing to the at least one data field of the searchable information for the each record in the historical collection for query;
searching, by the mobile data processing system, the searchable information for the each record in the historical collection for query, upon the accepting;
retrieving, by the mobile data processing system, one or more entries from the historical collection for query, upon the searching, wherein the one or more entries correspond to one or more of the plurality of wireless data records and each of the one or more entries has at least one data field matching the conditional match specification; and
communicating, by the mobile data processing system, information for the one or more entries from the historical collection for query to request processing of the search request at the mobile data processing system.
20. A memory device storing instructions for execution by one or more processors, wherein the instructions cause operations comprising:
receiving, by a mobile data processing system, a plurality of wireless data records from a plurality of data processing systems determined by the mobile data processing system to have been in a wireless vicinity of the mobile data processing system, wherein the plurality of wireless data records are received by the mobile data processing system with a purely peer to peer interaction asynchronously from any user interface of the mobile data processing system;
storing, by the mobile data processing system, searchable information for each record of the plurality of wireless data records from the plurality of data processing systems in a historical collection for query with a conditional match specification, wherein the conditional match specification is for comparing to at least one data field of the searchable information for the each record in the historical collection for query, wherein the each record includes at least originating identifier information and application information;
storing, by the mobile data processing system, information for a data record of the mobile data processing system for comparison to the searchable information for the each record in the historical collection for query;
accepting, by the mobile data processing system, a search request for searching the searchable information for the each record in the historical collection for query, the search request including the conditional match specification for comparing to the at least one data field of the searchable information for the each record in the historical collection for query;
searching, by the mobile data processing system, the searchable information for the each record in the historical collection for query, upon the accepting;
retrieving, by the mobile data processing system, one or more entries from the historical collection for query, upon the searching, wherein the one or more entries correspond to one or more of the plurality of wireless data records and each of the one or more entries has at least one data field matching the conditional match specification; and
communicating, by the mobile data processing system, information for the one or more entries from the historical collection for query to request processing of the search request at the mobile data processing system.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/299,910 US20140289234A1 (en) | 2008-03-14 | 2014-06-09 | System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/077,041 US8600341B2 (en) | 2008-03-14 | 2008-03-14 | System and method for location based exchanges of data facilitating distributed locational applications |
US14/033,539 US8750823B2 (en) | 2008-03-14 | 2013-09-23 | System and method for location based exchanges of data facilitating distributed locational applications |
US14/299,910 US20140289234A1 (en) | 2008-03-14 | 2014-06-09 | System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/033,539 Continuation US8750823B2 (en) | 2008-03-14 | 2013-09-23 | System and method for location based exchanges of data facilitating distributed locational applications |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140289234A1 true US20140289234A1 (en) | 2014-09-25 |
Family
ID=41063590
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/077,041 Expired - Fee Related US8600341B2 (en) | 2008-03-14 | 2008-03-14 | System and method for location based exchanges of data facilitating distributed locational applications |
US14/033,539 Expired - Fee Related US8750823B2 (en) | 2008-03-14 | 2013-09-23 | System and method for location based exchanges of data facilitating distributed locational applications |
US14/033,543 Active US8886226B2 (en) | 2008-03-14 | 2013-09-23 | System and method for timely whereabouts determination by a mobile data processing system |
US14/033,540 Active US8761804B2 (en) | 2008-03-14 | 2013-09-23 | System and method for location based exchanges of data facilitating distributed locational applications |
US14/299,910 Abandoned US20140289234A1 (en) | 2008-03-14 | 2014-06-09 | System and Method for Location Based Exchanges of Data Facilitating Distributed Locational Applications |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/077,041 Expired - Fee Related US8600341B2 (en) | 2008-03-14 | 2008-03-14 | System and method for location based exchanges of data facilitating distributed locational applications |
US14/033,539 Expired - Fee Related US8750823B2 (en) | 2008-03-14 | 2013-09-23 | System and method for location based exchanges of data facilitating distributed locational applications |
US14/033,543 Active US8886226B2 (en) | 2008-03-14 | 2013-09-23 | System and method for timely whereabouts determination by a mobile data processing system |
US14/033,540 Active US8761804B2 (en) | 2008-03-14 | 2013-09-23 | System and method for location based exchanges of data facilitating distributed locational applications |
Country Status (1)
Country | Link |
---|---|
US (5) | US8600341B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107944300A (en) * | 2017-11-01 | 2018-04-20 | 深信服科技股份有限公司 | A kind of method for writing data and device, verification method and device |
US11436534B2 (en) | 2020-05-20 | 2022-09-06 | Bank Of America Corporation | Distributed artificial intelligence model |
US11727306B2 (en) | 2020-05-20 | 2023-08-15 | Bank Of America Corporation | Distributed artificial intelligence model with deception nodes |
Families Citing this family (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8489669B2 (en) * | 2000-06-07 | 2013-07-16 | Apple Inc. | Mobile data processing system moving interest radius |
US8761751B2 (en) * | 2008-03-14 | 2014-06-24 | William J. Johnson | System and method for targeting data processing system(s) with data |
US8600341B2 (en) | 2008-03-14 | 2013-12-03 | William J. Johnson | System and method for location based exchanges of data facilitating distributed locational applications |
US9078095B2 (en) | 2008-03-14 | 2015-07-07 | William J. Johnson | System and method for location based inventory management |
US8634796B2 (en) | 2008-03-14 | 2014-01-21 | William J. Johnson | System and method for location based exchanges of data facilitating distributed location applications |
US8566839B2 (en) | 2008-03-14 | 2013-10-22 | William J. Johnson | System and method for automated content presentation objects |
US9250092B2 (en) | 2008-05-12 | 2016-02-02 | Apple Inc. | Map service with network-based query for search |
US20090325539A1 (en) * | 2008-06-25 | 2009-12-31 | Ajay Malik | Cell Phone Sensor Applications |
US8775454B2 (en) * | 2008-07-29 | 2014-07-08 | James L. Geer | Phone assisted ‘photographic memory’ |
US8806044B2 (en) | 2011-11-29 | 2014-08-12 | Maxlinear, Inc. | Method and system for cross-protocol time synchronization |
WO2011082182A1 (en) * | 2009-12-28 | 2011-07-07 | Maxlinear, Inc. | Gnss reception using distributed time synchronization |
US8457657B2 (en) * | 2010-01-22 | 2013-06-04 | Qualcomm Incorporated | Method and apparatus for peer-assisted localization |
CA2826369A1 (en) * | 2011-02-03 | 2012-08-09 | Endrelia Technologies Inc. | Methods and apparatus for tracking location of portable electronic device |
US9693333B2 (en) * | 2011-02-09 | 2017-06-27 | Commscope Technologies Llc | System and method for location boosting using proximity information |
US10168413B2 (en) | 2011-03-25 | 2019-01-01 | T-Mobile Usa, Inc. | Service enhancements using near field communication |
US8855671B1 (en) * | 2011-03-28 | 2014-10-07 | Google Inc. | System and method for determining position |
US8521190B2 (en) * | 2011-06-09 | 2013-08-27 | Qualcomm Incorporated | Methods and apparatus for leaving and/or discovering locally relevant pieces of information |
US9824199B2 (en) | 2011-08-25 | 2017-11-21 | T-Mobile Usa, Inc. | Multi-factor profile and security fingerprint analysis |
US9674661B2 (en) * | 2011-10-21 | 2017-06-06 | Microsoft Technology Licensing, Llc | Device-to-device relative localization |
US20140258526A1 (en) * | 2011-10-24 | 2014-09-11 | Schneider Electric Industries Sas | Systems and methods of remote communication |
WO2013117964A1 (en) * | 2012-02-09 | 2013-08-15 | Nokia Corporation | Estimating distances between devices |
WO2013133870A2 (en) | 2012-03-07 | 2013-09-12 | Snap Trends, Inc. | Methods and systems of aggregating information of social networks based on geographical locations via a network |
CN103813440A (en) * | 2012-11-07 | 2014-05-21 | 中兴通讯股份有限公司 | Positioning method of mobile terminal in LTE system and system thereof |
US9554244B2 (en) * | 2013-01-24 | 2017-01-24 | Sap Se | Distribution of location and movement information of meeting participants |
US9170112B2 (en) | 2013-02-08 | 2015-10-27 | Google Inc. | Mobile device position and orientation from multiple unsurveyed magnetic sources |
US9262915B2 (en) | 2013-05-09 | 2016-02-16 | KERBspace, Inc | Intelligent urban communications portal and methods |
US9455772B2 (en) | 2013-06-28 | 2016-09-27 | Huawei Technologies Co., Ltd. | System and method for network uplink measurement based operation using UE centric sounding |
US9202245B2 (en) | 2013-08-19 | 2015-12-01 | Estimote Polska Sp. Z O.O. | Wireless beacon and methods |
US9998863B2 (en) | 2013-08-19 | 2018-06-12 | Estimote Polska Sp. Z O. O. | System and method for providing content using beacon systems |
US9477991B2 (en) | 2013-08-27 | 2016-10-25 | Snap Trends, Inc. | Methods and systems of aggregating information of geographic context regions of social networks based on geographical locations via a network |
US9894489B2 (en) | 2013-09-30 | 2018-02-13 | William J. Johnson | System and method for situational proximity observation alerting privileged recipients |
US10078539B1 (en) | 2013-10-30 | 2018-09-18 | American Airlines, Inc. | System and method for logging and searching history events such as airline flight or crew history |
US9551561B2 (en) | 2013-12-04 | 2017-01-24 | Google Inc. | Determining location using magnetic fields from AC power lines |
CN103873485B (en) * | 2014-04-03 | 2017-03-08 | 重庆邮电大学 | Cluster MAC protocol implementation method based on the link persistent period in vehicular ad hoc network |
US10979862B2 (en) | 2014-06-10 | 2021-04-13 | Pb Inc. | Tracking device system |
US11792605B2 (en) | 2014-06-10 | 2023-10-17 | PB, Inc. | Tracking device systems |
US10580281B2 (en) | 2014-06-10 | 2020-03-03 | PB, Inc. | Tracking device system |
US9774410B2 (en) | 2014-06-10 | 2017-09-26 | PB, Inc. | Radiobeacon data sharing by forwarding low energy transmissions to a cloud host |
US11145183B2 (en) | 2014-06-10 | 2021-10-12 | PB, Inc | Tracking device programs, systems and methods |
US10937286B2 (en) | 2014-06-10 | 2021-03-02 | Pb Inc. | Radiobeacon data sharing by forwarding low energy transmissions to a cloud host |
US9295011B1 (en) | 2014-11-06 | 2016-03-22 | At&T Mobility Ii Llc | Low power chaining |
US9473510B2 (en) * | 2015-02-25 | 2016-10-18 | Guardtime IP Holdings, Ltd. | System and method for location verification |
US11609958B1 (en) * | 2015-07-17 | 2023-03-21 | EMC IP Holding Company LLC | System and method for managing log records of elements of a distributed computing environment |
US10136250B2 (en) | 2015-09-02 | 2018-11-20 | Estimote Polska Sp. Z O. O. | System and method for lower power data routing |
CN105338623A (en) * | 2015-10-19 | 2016-02-17 | 叶金凤 | Passive type geological position information system and method based on telecommunication mobile base station |
US10372515B1 (en) | 2015-10-30 | 2019-08-06 | American Airlines, Inc. | System agnostic front end application for legacy systems |
US10361800B2 (en) | 2015-11-18 | 2019-07-23 | PB, Inc | Radiobeacon data sharing by forwarding low energy transmissions to a cloud host |
KR102356954B1 (en) | 2016-01-05 | 2022-01-28 | 삼성전자주식회사 | Method and apparatus for estimating position of terminal |
DE102016114797A1 (en) * | 2016-02-22 | 2017-08-24 | Balluff Gmbh | Network arrangement and method for the radio location of objects within a limited space |
US10083068B2 (en) * | 2016-03-29 | 2018-09-25 | Microsoft Technology Licensing, Llc | Fast transfer of workload between multiple processors |
CN105979577A (en) * | 2016-05-11 | 2016-09-28 | 百度在线网络技术(北京)有限公司 | Method and system for obtaining visit information of user |
EP3246730A1 (en) * | 2016-05-19 | 2017-11-22 | Deutsche Telekom AG | Method to increase positioning accuracy of global navigation satellite systems by integration of correction service with a mobile communication network |
US10346400B2 (en) * | 2017-01-24 | 2019-07-09 | Visa International Service Association | Database conditional field access |
CN109286918B (en) * | 2018-07-03 | 2021-10-22 | 浙江绍兴苏泊尔生活电器有限公司 | Pairing processing method, device and system for cookware of induction cooker |
WO2020039252A1 (en) | 2018-08-22 | 2020-02-27 | Estimote Polska Sp Z.O.O. | System and method for verifying device security |
WO2020039251A2 (en) | 2018-08-24 | 2020-02-27 | Estimote Polska Sp z o.o. | A method and system for asset management |
US11184858B2 (en) | 2018-09-18 | 2021-11-23 | PB, Inc. | Bluecell devices and methods |
US11678141B2 (en) | 2018-09-18 | 2023-06-13 | Pb Inc. | Hybrid cellular Bluetooth tracking devices, methods and systems |
CN110971326B (en) * | 2018-09-28 | 2021-07-16 | 华为技术有限公司 | Time synchronization method and device |
US11037382B2 (en) * | 2018-11-20 | 2021-06-15 | Ford Global Technologies, Llc | System and method for evaluating operation of environmental sensing systems of vehicles |
CN109474894B (en) * | 2019-01-03 | 2020-09-11 | 腾讯科技(深圳)有限公司 | Terminal positioning processing method and device and electronic equipment |
CN110493711B (en) * | 2019-07-29 | 2021-07-06 | 深圳绿米联创科技有限公司 | Positioning method, device, system, electronic equipment and storage medium |
WO2021222968A1 (en) * | 2020-05-08 | 2021-11-11 | Robert Bosch (Australia) Pty Ltd | Asset tracking and asset management |
CN112887342B (en) * | 2021-04-29 | 2021-07-23 | 湖北亿咖通科技有限公司 | Service scheduling method, vehicle-mounted service processing system, electronic device and storage medium |
Family Cites Families (462)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS4830787B1 (en) | 1967-12-28 | 1973-09-22 | ||
US4021780A (en) | 1975-09-24 | 1977-05-03 | Narey James O | Ballot tallying system including a digital programmable read only control memory, a digital ballot image memory and a digital totals memory |
JPS5553767A (en) | 1978-10-14 | 1980-04-19 | Keihin Kiyuukou Dentetsu Kk | Computer system for motor school |
US4445118A (en) | 1981-05-22 | 1984-04-24 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Navigation system and method |
US4536647A (en) | 1983-07-15 | 1985-08-20 | Atalla Corporation | Pocket banking terminal, method and system |
US4644351A (en) | 1984-05-08 | 1987-02-17 | Motorola, Inc. | Two way personal message system with extended coverage |
US5375161A (en) | 1984-09-14 | 1994-12-20 | Accessline Technologies, Inc. | Telephone control system with branch routing |
EP0232418A4 (en) | 1985-08-08 | 1987-12-01 | Network Satellite Paging | Scanning receiver for nationwide radio paging system. |
US6443840B2 (en) | 1986-03-10 | 2002-09-03 | Response Reward Systems, L.C. | Evaluation of responses of participatory broadcast audience with prediction of winning contestants; monitoring, checking and controlling of wagering, and automatic crediting and couponing |
US4845504A (en) | 1987-04-08 | 1989-07-04 | M/A-Com, Inc. | Mobile radio network for nationwide communications |
US4757267A (en) | 1987-06-17 | 1988-07-12 | Applied Telematics, Inc. | Telephone system for connecting a customer to a supplier of goods |
US4973952A (en) | 1987-09-21 | 1990-11-27 | Information Resources, Inc. | Shopping cart display system |
US4841560A (en) | 1987-10-16 | 1989-06-20 | Harris Corp. | Direct access test unit for central office |
US6937998B1 (en) | 1987-12-28 | 2005-08-30 | Symbol Technologies, Inc. | Arrangement for and method of expediting transactions based on a customer's proximity to the transactions |
US4974170A (en) | 1988-01-21 | 1990-11-27 | Directional Data, Inc. | Electronic directory for identifying a selected group of subscribers |
US4922516A (en) | 1988-01-25 | 1990-05-01 | Communications Technology Corporation | Telephone technician's terminals with auto-selection of dial pulse on DTMF signalling |
JPH01194628A (en) | 1988-01-29 | 1989-08-04 | Nec Corp | Secrecy protecting system |
US5196031A (en) | 1988-02-08 | 1993-03-23 | Sandoz Ltd. | Exhaust dyeing process for mixed fibre substrate in single bath: disperse dye, copper complex dye, complexing agent and oxidizing agent |
CA1314101C (en) | 1988-02-17 | 1993-03-02 | Henry Shao-Lin Teng | Expert system for security inspection of a digital computer system in a network environment |
CA1341310C (en) | 1988-07-15 | 2001-10-23 | Robert Filepp | Interactive computer network and method of operation |
US7072849B1 (en) | 1988-07-15 | 2006-07-04 | International Business Machines Corporation | Method for presenting advertising in an interactive service |
US4977399A (en) | 1988-08-09 | 1990-12-11 | At&E Corporation | Mobile radio paging test system |
US5195031A (en) | 1988-10-24 | 1993-03-16 | Reuters Limited | Trading system for providing real time context sensitive trading messages based on conversation analysis |
US5089814A (en) | 1989-04-28 | 1992-02-18 | Motorola, Inc. | Automatic time zone adjustment of portable receiver |
US5572653A (en) | 1989-05-16 | 1996-11-05 | Rest Manufacturing, Inc. | Remote electronic information display system for retail facility |
US6484029B2 (en) | 1998-10-13 | 2002-11-19 | Symbol Technologies, Inc. | Apparatus and methods for adapting mobile unit to wireless LAN |
US6044205A (en) | 1996-02-29 | 2000-03-28 | Intermind Corporation | Communications system for transferring information between memories according to processes transferred with the information |
US6345288B1 (en) | 1989-08-31 | 2002-02-05 | Onename Corporation | Computer-based communication system and method using metadata defining a control-structure |
JPH03128540A (en) | 1989-09-14 | 1991-05-31 | Hitachi Ltd | Security system |
US5265070A (en) | 1989-11-08 | 1993-11-23 | Seiko Epson Corporation | Receiving device with timekeeping function |
US5870724A (en) | 1989-12-08 | 1999-02-09 | Online Resources & Communications Corporation | Targeting advertising in a home retail banking delivery service |
US5185857A (en) | 1989-12-13 | 1993-02-09 | Rozmanith A Martin | Method and apparatus for multi-optional processing, storing, transmitting and retrieving graphical and tabular data in a mobile transportation distributable and/or networkable communications and/or data processing system |
US5095532A (en) | 1989-12-29 | 1992-03-10 | Robert Bosch Gmbh | Method and apparatus for route-selective reproduction of broadcast traffic announcements |
US5131020A (en) | 1989-12-29 | 1992-07-14 | Smartroutes Systems Limited Partnership | Method of and system for providing continually updated traffic or other information to telephonically and other communications-linked customers |
US6389010B1 (en) | 1995-10-05 | 2002-05-14 | Intermec Ip Corp. | Hierarchical data collection network supporting packetized voice communications among wireless terminals and telephones |
US5321242A (en) | 1991-12-09 | 1994-06-14 | Brinks, Incorporated | Apparatus and method for controlled access to a secured location |
US5451757A (en) | 1990-04-22 | 1995-09-19 | Brink's Incorporated | Apparatus and method for controlled access to a secured location |
US5245608A (en) | 1990-09-26 | 1993-09-14 | International Business Machines Corporation | Logical grouping of layer entities in a layered communication architecture |
US5113430A (en) | 1990-10-01 | 1992-05-12 | United States Advanced Network, Inc. | Enhanced wide area audio response network |
US5303393A (en) | 1990-11-06 | 1994-04-12 | Radio Satellite Corporation | Integrated radio satellite response system and method |
US5610973A (en) | 1991-01-28 | 1997-03-11 | Bellsouth Corporation | Interactive roamer contact system for cellular mobile radiotelephone network |
US5264822A (en) | 1991-02-22 | 1993-11-23 | Vogelman Joseph H | System for transmitting audio advertising messages to shopping carts moving through spatially defined transmission zones arranged in a store |
US5121126A (en) | 1991-03-12 | 1992-06-09 | Bell Atlantic Network Services Inc. | Beacon enhanced telecommunications system and method |
US5214793A (en) | 1991-03-15 | 1993-05-25 | Pulse-Com Corporation | Electronic billboard and vehicle traffic control communication system |
US5365516A (en) | 1991-08-16 | 1994-11-15 | Pinpoint Communications, Inc. | Communication system and method for determining the location of a transponder unit |
US5361871A (en) | 1991-08-20 | 1994-11-08 | Digicomp Research Corporation | Product information system for shoppers |
US5390237A (en) | 1991-09-27 | 1995-02-14 | The Weather Radio Network, Inc. | Weather information interface system |
US5337044A (en) | 1991-10-08 | 1994-08-09 | Nomadic Systems, Inc. | System for remote computer control using message broadcasting system |
IT223337Z2 (en) | 1991-10-31 | 1995-06-21 | Gilardini Spa | REARVIEW MIRROR FOR VEHICLES. |
US5404505A (en) | 1991-11-01 | 1995-04-04 | Finisar Corporation | System for scheduling transmission of indexed and requested database tiers on demand at varying repetition rates |
US5461627A (en) | 1991-12-24 | 1995-10-24 | Rypinski; Chandos A. | Access protocol for a common channel wireless network |
US8208014B2 (en) | 1992-01-16 | 2012-06-26 | Klever Marketing, Inc. | Electronic shopping cart display system |
US6177880B1 (en) | 1992-01-16 | 2001-01-23 | Klever-Kart, Inc. | Automated shopping cart handle |
US5826195A (en) | 1992-01-27 | 1998-10-20 | Highwaymaster Communications, Inc. | Data messaging in a communications network |
US5586254A (en) | 1992-02-13 | 1996-12-17 | Hitachi Software Engineering Co., Ltd. | System for managing and operating a network by physically imaging the network |
US5353331A (en) | 1992-03-05 | 1994-10-04 | Bell Atlantic Network Services, Inc. | Personal communications service using wireline/wireless integration |
GB9207861D0 (en) | 1992-04-09 | 1992-05-27 | Philips Electronics Uk Ltd | A method of time measurement in a communications system,a communications system and a receiving apparatus for use in the system |
US5223844B1 (en) | 1992-04-17 | 2000-01-25 | Auto Trac Inc | Vehicle tracking and security system |
US5758049A (en) | 1992-05-01 | 1998-05-26 | International Business Machines Corporation | Method of and apparatus for providing automatic detection and processing of an empty multimedia data object |
US5432841A (en) | 1992-07-10 | 1995-07-11 | Rimer; Neil A. | System for locating and communicating with mobile vehicles |
US5243652A (en) | 1992-09-30 | 1993-09-07 | Gte Laboratories Incorporated | Location-sensitive remote database access control |
US6067082A (en) | 1992-11-09 | 2000-05-23 | Enmei; Toshiharu | Portable communicator |
US5704049A (en) | 1992-12-22 | 1997-12-30 | Electronic Retailing Systems International Inc. | Subglobal area addressing for electronic price displays |
US5325419A (en) | 1993-01-04 | 1994-06-28 | Ameritech Corporation | Wireless digital personal communications system having voice/data/image two-way calling and intercell hand-off |
US5666481A (en) | 1993-02-26 | 1997-09-09 | Cabletron Systems, Inc. | Method and apparatus for resolving faults in communications networks |
US6006090A (en) | 1993-04-28 | 1999-12-21 | Proxim, Inc. | Providing roaming capability for mobile computers in a standard network |
US5796727A (en) | 1993-04-30 | 1998-08-18 | International Business Machines Corporation | Wide-area wireless lan access |
US5714948A (en) | 1993-05-14 | 1998-02-03 | Worldwide Notifications Systems, Inc. | Satellite based aircraft traffic control system |
AU5538094A (en) | 1993-05-14 | 1994-12-12 | Worldwide Notification Systems, Inc. | Apparatus and method of notifying a recipient of an unscheduled delivery |
US6067008A (en) | 1993-05-25 | 2000-05-23 | Intellectual Property Development Associates Of Connecticut, Inc. | Methods and apparatus for inputting messages, including advertisements, to a vehicle |
US5806018A (en) | 1993-05-25 | 1998-09-08 | Intellectual Property Development Associates Of Connecticut, Incorporated | Methods and apparatus for updating navigation information in a motorized vehicle |
US5504482A (en) | 1993-06-11 | 1996-04-02 | Rockwell International Corporation | Automobile navigation guidance, control and safety system |
AU7210894A (en) | 1993-06-25 | 1995-01-17 | Xircom, Inc. | Virtual carrier detection for wireless local area network with distributed control |
US5701301A (en) | 1993-06-28 | 1997-12-23 | Bellsouth Corporation | Mediation of open advanced intelligent network in SS7 protocol open access environment |
US5455807A (en) | 1993-08-18 | 1995-10-03 | Seiko Corp. | Time maintenance and display in a time keeping system including a time zone boundary |
US5493309A (en) | 1993-09-24 | 1996-02-20 | Motorola, Inc. | Collison avoidance communication system and method |
US5581479A (en) | 1993-10-15 | 1996-12-03 | Image Telecommunications Corp. | Information service control point, which uses different types of storage devices, which retrieves information as blocks of data, and which uses a trunk processor for transmitting information |
US5511111A (en) | 1993-11-01 | 1996-04-23 | Engineering And Business Systems, Inc. | Caller name and identification communication system with caller screening option |
CA2134729C (en) | 1993-11-01 | 1999-09-07 | Thomas E. Buss | Location dependent information receiving device and method |
US5371794A (en) | 1993-11-02 | 1994-12-06 | Sun Microsystems, Inc. | Method and apparatus for privacy and authentication in wireless networks |
DE4338556A1 (en) | 1993-11-08 | 1995-05-11 | Mannesmann Ag | Device for recording route information |
US5881131A (en) | 1993-11-16 | 1999-03-09 | Bell Atlantic Network Services, Inc. | Analysis and validation system for provisioning network related facilities |
US5687212A (en) | 1995-07-25 | 1997-11-11 | Bell Atlantic Network Services, Inc. | System for reactively maintaining telephone network facilities in a public switched telephone network |
US5475735A (en) | 1993-12-02 | 1995-12-12 | Motorola, Inc. | Method of providing wireless local loop operation with local mobility for a subscribed unit |
US5960344A (en) | 1993-12-20 | 1999-09-28 | Norand Corporation | Local area network having multiple channel wireless access |
US5892454A (en) | 1993-12-21 | 1999-04-06 | Trimble Navigation Ltd. | Hybrid monitoring of location of a site confinee |
US5661492A (en) | 1994-01-31 | 1997-08-26 | Motorola, Inc. | Personal alarm location system and method |
EP0666700A1 (en) | 1994-02-03 | 1995-08-09 | AT&T Corp. | Virtual mobile location area |
WO1995021511A1 (en) | 1994-02-07 | 1995-08-10 | Harold Ii Pace | Mobile location reporting apparatus and methods |
JPH07234789A (en) | 1994-02-24 | 1995-09-05 | Hitachi Ltd | Supporting method for rule synthesis |
US5594782A (en) | 1994-02-24 | 1997-01-14 | Gte Mobile Communications Service Corporation | Multiple mode personal wireless communications system |
US5778304A (en) | 1994-03-10 | 1998-07-07 | Motorola, Inc. | Method for providing communication services based on geographic location |
US5561704A (en) | 1994-03-16 | 1996-10-01 | At&T Corp. | Proximity based toll free communication services |
US5485163A (en) | 1994-03-30 | 1996-01-16 | Motorola, Inc. | Personal locator system |
US5511233A (en) | 1994-04-05 | 1996-04-23 | Celsat America, Inc. | System and method for mobile communications in coexistence with established communications systems |
AU2291195A (en) | 1994-04-12 | 1995-10-30 | Qualcomm Incorporated | Method and apparatus for freight transportation using a satellite navigation system |
US5625668A (en) | 1994-04-12 | 1997-04-29 | Trimble Navigation Limited | Position reporting cellular telephone |
US7106843B1 (en) | 1994-04-19 | 2006-09-12 | T-Netix, Inc. | Computer-based method and apparatus for controlling, monitoring, recording and reporting telephone access |
JPH07288514A (en) | 1994-04-20 | 1995-10-31 | Mita Ind Co Ltd | Communication equipment |
US5497414A (en) | 1994-05-04 | 1996-03-05 | Bell Atlantic Network Services, Inc. | Telephone system processing of designated caller ID private calls |
US5469362A (en) | 1994-05-16 | 1995-11-21 | Pitney Bowes Inc. | Dispatching method and apparatus for monitoring scheduled mail |
JPH07319706A (en) | 1994-05-24 | 1995-12-08 | Hitachi Ltd | Rule synthesizing method |
US5896440A (en) | 1994-05-26 | 1999-04-20 | Gte Service Corporation | System and method for providing a unified communications link between divergent communication networks |
US5720033A (en) | 1994-06-30 | 1998-02-17 | Lucent Technologies Inc. | Security platform and method using object oriented rules for computer-based systems using UNIX-line operating systems |
US5512908A (en) | 1994-07-08 | 1996-04-30 | Lockheed Sanders, Inc. | Apparatus and method for locating cellular telephones |
US5625364A (en) | 1994-07-08 | 1997-04-29 | Lockheed Sanders, Inc. | Apparatus and method for finding a signal emission source |
US5544354A (en) | 1994-07-18 | 1996-08-06 | Ikonic Interactive, Inc. | Multimedia matrix architecture user interface |
CA2154335C (en) | 1994-07-21 | 2002-04-23 | Tom Gray | Integrated wired and wireless telecommunications system |
US5664948A (en) | 1994-07-29 | 1997-09-09 | Seiko Communications Holding N.V. | Delivery of data including preloaded advertising data |
CA2129200C (en) | 1994-07-29 | 1999-08-10 | Murray C. Baker | Access point switching for mobile wireless network node |
DE69502105T2 (en) | 1994-07-29 | 1998-08-06 | Seiko Comm Holding Nv | TWO-CHANNEL ADVERTISING WITH VEHICLE LOCATION REFERENCE |
JPH0844568A (en) | 1994-07-29 | 1996-02-16 | Hitachi Zosen Corp | Encryption method for fuzzy rule |
US5845293A (en) | 1994-08-08 | 1998-12-01 | Microsoft Corporation | Method and system of associating, synchronizing and reconciling computer files in an operating system |
US5636245A (en) | 1994-08-10 | 1997-06-03 | The Mitre Corporation | Location based selective distribution of generally broadcast information |
US5528248A (en) | 1994-08-19 | 1996-06-18 | Trimble Navigation, Ltd. | Personal digital location assistant including a memory cartridge, a GPS smart antenna and a personal computing device |
JPH0887296A (en) | 1994-09-16 | 1996-04-02 | Secom Co Ltd | Voice synthesizer |
US5559520A (en) | 1994-09-26 | 1996-09-24 | Lucent Technologies Inc. | Wireless information system for acquiring location related information |
US5596625A (en) | 1994-09-28 | 1997-01-21 | U S West Technologies, Inc. | Method for routing emergency calls during busy interface channel conditions |
US5590196A (en) | 1994-10-06 | 1996-12-31 | Connotech Experts Conseils Inc. | Secure payment method using facsimile |
US5724521A (en) | 1994-11-03 | 1998-03-03 | Intel Corporation | Method and apparatus for providing electronic advertisements to end users in a consumer best-fit pricing manner |
US5646632A (en) | 1994-11-14 | 1997-07-08 | Lucent Technologies Inc. | Method and apparatus for a portable communication device to identify its own location |
DE69532601T2 (en) | 1994-11-14 | 2004-12-23 | Harris Corp., Melbourne | Troubleshooting system for telephone system |
US6571279B1 (en) | 1997-12-05 | 2003-05-27 | Pinpoint Incorporated | Location enhanced information delivery system |
US5513263A (en) | 1994-11-30 | 1996-04-30 | Motorola, Inc. | Method for establishing classes within a communication network |
US5592470A (en) | 1994-12-21 | 1997-01-07 | At&T | Broadband wireless system and network architecture providing broadband/narrowband service with optimal static and dynamic bandwidth/channel allocation |
US5727057A (en) | 1994-12-27 | 1998-03-10 | Ag Communication Systems Corporation | Storage, transmission, communication and access to geographical positioning data linked with standard telephony numbering and encoded for use in telecommunications and related services |
CA2164896C (en) | 1994-12-27 | 2000-11-21 | Daniel Jitzchak Mayer | Context-based transactions using broadcast advertising |
US5983091A (en) | 1995-01-05 | 1999-11-09 | Omni Telecommunications, Inc. | Portable communication unit with discrete allocable blocks of airtime |
US5682525A (en) | 1995-01-11 | 1997-10-28 | Civix Corporation | System and methods for remotely accessing a selected group of items of interest from a database |
US5594779A (en) | 1995-01-12 | 1997-01-14 | Bell Atlantic | Mobile audio program selection system using public switched telephone network |
CA2210237A1 (en) | 1995-01-13 | 1996-07-18 | Gary R. Cantu | Solar powered price display system |
US5845211A (en) | 1995-01-13 | 1998-12-01 | Bell South Corporation | Wireless digital network |
GB9508283D0 (en) | 1995-02-07 | 1995-06-14 | British Telecomm | Information services provision and management |
FI99071C (en) | 1995-02-15 | 1997-09-25 | Nokia Mobile Phones Ltd | Procedure for use of applications in a mobile telephone as well as a mobile telephone |
US5696906A (en) | 1995-03-09 | 1997-12-09 | Continental Cablevision, Inc. | Telecommunicaion user account management system and method |
US5583864A (en) | 1995-03-28 | 1996-12-10 | Bell Atlantic Network Services, Inc. | Level 1 gateway for video dial tone networks |
US5677905A (en) | 1995-03-28 | 1997-10-14 | Bell Atlantic Network Services, Inc. | Access subnetwork controller for video dial tone networks |
US6236940B1 (en) | 1995-09-08 | 2001-05-22 | Prolink, Inc. | Display monitor for golf cart yardage and information system |
US6236360B1 (en) | 1995-04-18 | 2001-05-22 | Richard W. Rudow | Golf course yardage and information system |
US5689431A (en) | 1995-04-18 | 1997-11-18 | Leading Edge Technologies, Inc. | Golf course yardage and information system |
US5842010A (en) | 1995-04-24 | 1998-11-24 | Bell Communications Research, Inc. | Periodic wireless data broadcast |
US5608854A (en) | 1995-04-25 | 1997-03-04 | Motorola, Inc. | Method and apparatus for displaying information in a communication system |
US5922040A (en) | 1995-05-17 | 1999-07-13 | Mobile Information System, Inc. | Method and apparatus for fleet management |
US5889953A (en) | 1995-05-25 | 1999-03-30 | Cabletron Systems, Inc. | Policy management and conflict resolution in computer networks |
US6073062A (en) | 1995-05-31 | 2000-06-06 | Fujitsu Limited | Mobile terminal and moving body operation management system |
US6418324B1 (en) | 1995-06-01 | 2002-07-09 | Padcom, Incorporated | Apparatus and method for transparent wireless communication between a remote device and host system |
US6259405B1 (en) | 1995-06-06 | 2001-07-10 | Wayport, Inc. | Geographic based communications service |
US5835061A (en) | 1995-06-06 | 1998-11-10 | Wayport, Inc. | Method and apparatus for geographic-based communications service |
US5748724A (en) | 1995-06-30 | 1998-05-05 | Siemens Stomberg-Carlson | Method for transferring a subscriber to a new local service provider |
US6112186A (en) | 1995-06-30 | 2000-08-29 | Microsoft Corporation | Distributed system for facilitating exchange of user information and opinion using automated collaborative filtering |
CA2179337C (en) | 1995-08-22 | 2000-11-14 | Thomas F. Laporta | Network-based migrating user agents for personal communication services |
US5566235A (en) | 1995-10-05 | 1996-10-15 | Bell Atlantic Network Services, Inc. | Customer controlled service mediation management |
US5874914A (en) | 1995-10-09 | 1999-02-23 | Snaptrack, Inc. | GPS receiver utilizing a communication link |
US5771283A (en) | 1995-10-26 | 1998-06-23 | Lucent Technologies Inc. | Method for delivering enhanced caller identification service in a telecommunications network |
US6047165A (en) | 1995-11-14 | 2000-04-04 | Harris Corporation | Wireless, frequency-agile spread spectrum ground link-based aircraft data communication system |
US5855007A (en) | 1995-11-15 | 1998-12-29 | Jovicic; Neboisa | Electronic coupon communication system |
US5713075A (en) | 1995-11-30 | 1998-01-27 | Amsc Subsidiary Corporation | Network engineering/systems engineering system for mobile satellite communication system |
US5878126A (en) | 1995-12-11 | 1999-03-02 | Bellsouth Corporation | Method for routing a call to a destination based on range identifiers for geographic area assignments |
US5794210A (en) | 1995-12-11 | 1998-08-11 | Cybergold, Inc. | Attention brokerage |
US5905955A (en) | 1995-12-12 | 1999-05-18 | At&T Wireless Services Inc. | Method for selecting a wireless service provider in a multi-service provider environment using a geographic database |
EP0788084B1 (en) | 1996-02-01 | 2004-04-21 | Aisin Aw Co., Ltd. | Navigation system for vehicles and waypoint entering and storage method |
US6047327A (en) | 1996-02-16 | 2000-04-04 | Intel Corporation | System for distributing electronic information to a targeted group of users |
FI102869B (en) | 1996-02-26 | 1999-02-26 | Nokia Mobile Phones Ltd | A device, method, and system for transmitting and receiving information relating to various applications |
US5920846A (en) | 1996-02-27 | 1999-07-06 | Southwestern Bell Telephone Co. | Method and system for processing a service request relating to installation, maintenance or repair of telecommunications services provided to a customer premises |
US6157946A (en) | 1996-02-28 | 2000-12-05 | Netzero Inc. | Communication system capable of providing user with picture meeting characteristics of user and terminal equipment and information providing device used for the same |
JPH09261169A (en) | 1996-03-21 | 1997-10-03 | Sony Corp | Communication system, basf station for the communication system and portable communication terminal equipment for the communication system |
US5790974A (en) | 1996-04-29 | 1998-08-04 | Sun Microsystems, Inc. | Portable calendaring device having perceptual agent managing calendar entries |
US5933420A (en) | 1996-04-30 | 1999-08-03 | 3Com Corporation | Method and apparatus for assigning spectrum of a wireless local area network |
US5907544A (en) | 1996-05-10 | 1999-05-25 | Rypinski; Chandos A. | Hub controller architecture and function for a multiple access-point wireless communication network |
US5870555A (en) | 1996-05-23 | 1999-02-09 | Electronic Data Systems Corporation | Lan resource manager |
US5923702A (en) | 1996-06-10 | 1999-07-13 | Breeze Wireless Communications Ltd. | Frequency hopping cellular LAN system |
US6067297A (en) | 1996-06-28 | 2000-05-23 | Symbol Technologies, Inc. | Embedded access point supporting communication with mobile unit operating in power-saving mode |
US5838774A (en) | 1996-07-01 | 1998-11-17 | Bellsouth Corporation | Telephone polling method |
US5875401A (en) | 1996-07-12 | 1999-02-23 | At & T Corp. | Method and apparatus for initiating wireless messages |
US5799066A (en) | 1996-08-09 | 1998-08-25 | At&T Corp. | Automated message system for a calling party |
FI111428B (en) | 1996-08-29 | 2003-07-15 | Nokia Corp | Gallup that utilizes a wireless data communication connection |
US6185427B1 (en) | 1996-09-06 | 2001-02-06 | Snaptrack, Inc. | Distributed satellite position system processing and application network |
US6236365B1 (en) | 1996-09-09 | 2001-05-22 | Tracbeam, Llc | Location of a mobile station using a plurality of commercial wireless infrastructures |
US5852775A (en) | 1996-09-12 | 1998-12-22 | Earthweb, Inc. | Cellular telephone advertising system |
FI103469B1 (en) | 1996-09-17 | 1999-06-30 | Nokia Telecommunications Oy | Prevention of abuse of a copied subscriber code in a mobile telephone system |
US6055637A (en) | 1996-09-27 | 2000-04-25 | Electronic Data Systems Corporation | System and method for accessing enterprise-wide resources by presenting to the resource a temporary credential |
TW341678B (en) | 1996-10-24 | 1998-10-01 | Ibm | Method and apparatus for access level control in a metropolitan area network |
US5938721A (en) | 1996-10-24 | 1999-08-17 | Trimble Navigation Limited | Position based personal digital assistant |
US7848948B2 (en) | 1996-10-25 | 2010-12-07 | Ipf, Inc. | Internet-based product brand marketing communication network configured to allow members of a product brand management team to communicate directly with consumers browsing HTML-encoded pages at an electronic commerce (EC) enabled web-site along the fabric of the world wide web (WWW), using programable multi-mode virtual kiosks (MMVKS) driven by server-side components and managed by product brand management team members |
JP2000505271A (en) | 1996-10-28 | 2000-04-25 | シーメンス アクチエンゲゼルシヤフト | Method and telephone network for the exchange of telephone connections |
US5819155A (en) | 1996-11-20 | 1998-10-06 | David G. Worthy | Active system and method for remotely identifying RF broadcast stations |
US5982867A (en) | 1996-11-27 | 1999-11-09 | Ameritech Corporation | Method and system for providing the name of the state of a calling party |
US5991287A (en) | 1996-12-30 | 1999-11-23 | Lucent Technologies, Inc. | System and method for providing seamless handover in a wireless computer network |
US5963866A (en) | 1997-01-15 | 1999-10-05 | Lucent Technologies Inc. | Wireless location messaging |
US5798733A (en) | 1997-01-21 | 1998-08-25 | Northrop Grumman Corporation | Interactive position guidance apparatus and method for guiding a user to reach a predetermined target position |
US5961593A (en) | 1997-01-22 | 1999-10-05 | Lucent Technologies, Inc. | System and method for providing anonymous personalized browsing by a proxy system in a network |
EP0966815A4 (en) | 1997-02-02 | 2001-12-12 | Fonefriend Systems Inc | Internet switch box, system and method for internet telephony |
US5920861A (en) | 1997-02-25 | 1999-07-06 | Intertrust Technologies Corp. | Techniques for defining using and manipulating rights management data structures |
US5963913A (en) | 1997-02-28 | 1999-10-05 | Silicon Graphics, Inc. | System and method for scheduling an event subject to the availability of requested participants |
US5987381A (en) | 1997-03-11 | 1999-11-16 | Visteon Technologies, Llc | Automobile navigation system using remote download of data |
US6721306B1 (en) | 1997-03-11 | 2004-04-13 | Verizon Services Corp. | Public wireless/cordless internet gateway |
US5950130A (en) | 1997-03-18 | 1999-09-07 | Sbc Technology Resources, Inc. | Mobile station with intelligent roaming and over-the-air programming features |
JPH10281790A (en) | 1997-04-08 | 1998-10-23 | Aisin Aw Co Ltd | Route search device, navigation apparatus and medium on which computer program for navigation processing is stored |
US6246361B1 (en) | 1999-06-28 | 2001-06-12 | Gary Sutton | Method and apparatus for determining a geographical location of a mobile communication unit |
US6009398A (en) | 1997-04-18 | 1999-12-28 | U S West, Inc. | Calendar system with direct and telephony networked voice control interface |
FR2763198B1 (en) | 1997-05-07 | 1999-07-23 | France Telecom | TELECOMMUNICATIONS NETWORK WITH FIXED AND MOBILE SUBSCRIBERS |
SE509435C2 (en) | 1997-05-16 | 1999-01-25 | Ericsson Telefon Ab L M | Privacy protection in a telecommunications system |
US5968176A (en) | 1997-05-29 | 1999-10-19 | 3Com Corporation | Multilayer firewall system |
US6516416B2 (en) | 1997-06-11 | 2003-02-04 | Prism Resources | Subscription access system for use with an untrusted network |
US6028921A (en) | 1997-06-11 | 2000-02-22 | Bellsouth Intellectual Property Corporation | Method and system for delivery of a message to a display unit |
US6026151A (en) | 1997-06-12 | 2000-02-15 | At&T Corp. | Network based determination of cost effective access |
US6091956A (en) | 1997-06-12 | 2000-07-18 | Hollenberg; Dennis D. | Situation information system |
US6133853A (en) | 1998-07-30 | 2000-10-17 | American Calcar, Inc. | Personal communication and positioning system |
US6148070A (en) | 1997-07-02 | 2000-11-14 | Ameritech Corporation | Method, system, and database for providing a telecommunication service |
JPH1141643A (en) | 1997-07-04 | 1999-02-12 | Internatl Business Mach Corp <Ibm> | Radio information processing terminal and control method therefor |
IL133950A0 (en) | 1997-07-09 | 2001-04-30 | Winstar Communications Inc | Computer controlled broadband wireless system |
US6560461B1 (en) | 1997-08-04 | 2003-05-06 | Mundi Fomukong | Authorized location reporting paging system |
US6459704B1 (en) | 1997-08-12 | 2002-10-01 | Spectrum Tracking Systems, Inc. | Method and system for radio-location determination |
US6163274A (en) | 1997-09-04 | 2000-12-19 | Ncr Corporation | Remotely updatable PDA |
FI104604B (en) | 1997-09-19 | 2000-02-29 | Nokia Networks Oy | Updating Internet access point settings in the mobile system |
US6697783B1 (en) | 1997-09-30 | 2004-02-24 | Medco Health Solutions, Inc. | Computer implemented medical integrated decision support system |
US6157829A (en) | 1997-10-08 | 2000-12-05 | Motorola, Inc. | Method of providing temporary access of a calling unit to an anonymous unit |
US6421714B1 (en) | 1997-10-14 | 2002-07-16 | Lucent Technologies | Efficient mobility management scheme for a wireless internet access system |
US6393482B1 (en) | 1997-10-14 | 2002-05-21 | Lucent Technologies Inc. | Inter-working function selection system in a network |
US6226277B1 (en) | 1997-10-14 | 2001-05-01 | Lucent Technologies Inc. | Method for admitting new connections based on usage priorities in a multiple access system for communications networks |
US6414950B1 (en) | 1997-10-14 | 2002-07-02 | Lucent Technologies Inc. | Sequence delivery of messages |
US6327254B1 (en) | 1997-10-14 | 2001-12-04 | Lucent Technologies Inc. | Method for bandwidth sharing in a multiple access system for communications networks |
US6577643B1 (en) | 1997-10-14 | 2003-06-10 | Lucent Technologies Inc. | Message and communication system in a network |
US6512754B2 (en) | 1997-10-14 | 2003-01-28 | Lucent Technologies Inc. | Point-to-point protocol encapsulation in ethernet frame |
US6665718B1 (en) | 1997-10-14 | 2003-12-16 | Lucent Technologies Inc. | Mobility management system |
US6285665B1 (en) | 1997-10-14 | 2001-09-04 | Lucent Technologies Inc. | Method for establishment of the power level for uplink data transmission in a multiple access system for communications networks |
US6675208B1 (en) | 1997-10-14 | 2004-01-06 | Lucent Technologies Inc. | Registration scheme for network |
US6377982B1 (en) | 1997-10-14 | 2002-04-23 | Lucent Technologies Inc. | Accounting system in a network |
US6377548B1 (en) | 1997-10-14 | 2002-04-23 | Lucent Technologies Inc. | Method for admitting new connections based on measured quantities in a multiple access system for communications networks |
US6400722B1 (en) | 1997-10-14 | 2002-06-04 | Lucent Technologies Inc. | Optimum routing system |
JP3496479B2 (en) | 1997-10-16 | 2004-02-09 | トヨタ自動車株式会社 | Road data maintenance system |
US6058106A (en) | 1997-10-20 | 2000-05-02 | Motorola, Inc. | Network protocol method, access point device and peripheral devices for providing for an efficient centrally coordinated peer-to-peer wireless communications network |
US5903636A (en) | 1997-10-27 | 1999-05-11 | Bellsouth Corporation | System and method for providing caller identification in conjunction with calling card calls |
US6076080A (en) | 1997-11-04 | 2000-06-13 | The Standard Register Company | Forms order entry system |
US6148405A (en) | 1997-11-10 | 2000-11-14 | Phone.Com, Inc. | Method and system for secure lightweight transactions in wireless data networks |
US6505046B1 (en) | 1997-11-19 | 2003-01-07 | Nortel Networks Limited | Method and apparatus for distributing location-based messages in a wireless communication network |
US6185426B1 (en) | 1997-11-20 | 2001-02-06 | Ericsson Inc | System, method, and apparatus for delivery of location information about caller |
AU1600299A (en) | 1997-11-20 | 1999-06-15 | Ericsson Inc. | Regulatory database within the intelligent network |
US6138003A (en) | 1997-11-26 | 2000-10-24 | Ericsson Inc. | System and method for authorization of location services |
US6353664B1 (en) | 1997-12-01 | 2002-03-05 | Agere Systems Guardian Corp. | Caller ID equipment which displays location of caller |
FI113445B (en) | 1997-12-18 | 2004-04-15 | Nokia Corp | Mobile Internet Protocol |
US6266614B1 (en) | 1997-12-24 | 2001-07-24 | Wendell Alumbaugh | Travel guide |
US6519252B2 (en) | 1997-12-31 | 2003-02-11 | Ericsson Inc. | System and method for connecting a call to a mobile subscriber connected to the Internet |
US6229810B1 (en) | 1997-12-31 | 2001-05-08 | At&T Corp | Network server platform for a hybrid fiber twisted pair local loop network service architecture |
US6647257B2 (en) | 1998-01-21 | 2003-11-11 | Leap Wireless International, Inc. | System and method for providing targeted messages based on wireless mobile location |
US6252544B1 (en) | 1998-01-27 | 2001-06-26 | Steven M. Hoffberg | Mobile communication device |
US6285931B1 (en) | 1998-02-05 | 2001-09-04 | Denso Corporation | Vehicle information communication system and method capable of communicating with external management station |
US6122520A (en) | 1998-02-13 | 2000-09-19 | Xerox Corporation | System and method for obtaining and using location specific information |
US6449497B1 (en) | 1998-03-10 | 2002-09-10 | Qualcomm Incorporated | System and method for use of feature codes in a wireless communication device |
US6182226B1 (en) | 1998-03-18 | 2001-01-30 | Secure Computing Corporation | System and method for controlling interactions between networks |
US6192314B1 (en) | 1998-03-25 | 2001-02-20 | Navigation Technologies Corp. | Method and system for route calculation in a navigation application |
US6389055B1 (en) | 1998-03-30 | 2002-05-14 | Lucent Technologies, Inc. | Integrating digital data with perceptible signals |
CA2326332A1 (en) | 1998-03-31 | 1999-10-07 | Transaccess Corp. | Multi-service access switched system |
JP3514626B2 (en) | 1998-04-14 | 2004-03-31 | インクリメント・ピー株式会社 | Route information providing system and WWW server used therefor, route information providing method and WWW server used therefor |
GB9901789D0 (en) | 1998-04-22 | 1999-03-17 | Koninkl Philips Electronics Nv | Antenna diversity system |
US6999572B1 (en) | 1998-05-01 | 2006-02-14 | Siemens Communications, Inc. | Automated call connection system |
US6496491B2 (en) | 1998-05-08 | 2002-12-17 | Lucent Technologies Inc. | Mobile point-to-point protocol |
US6449272B1 (en) | 1998-05-08 | 2002-09-10 | Lucent Technologies Inc. | Multi-hop point-to-point protocol |
US6801509B1 (en) | 1998-05-08 | 2004-10-05 | Lucent Technologies Inc. | Mobile point-to-point protocol |
US6208854B1 (en) | 1998-05-14 | 2001-03-27 | Ameritech Corporation | System and method for routing a call to a called party's landline or wireless communication unit |
US6144645A (en) | 1998-05-26 | 2000-11-07 | Nera Wireless Broadband Access As | Method and system for an air interface for providing voice, data, and multimedia services in a wireless local loop system |
US6438585B2 (en) | 1998-05-29 | 2002-08-20 | Research In Motion Limited | System and method for redirecting message attachments between a host system and a mobile data communication device |
US6898569B1 (en) | 1998-06-02 | 2005-05-24 | At&T Corp. | Method and apparatus for advanced scheduling and messaging system |
US6308273B1 (en) | 1998-06-12 | 2001-10-23 | Microsoft Corporation | Method and system of security location discrimination |
AU5085699A (en) | 1998-07-01 | 2000-01-24 | Bellsouth Intellectual Property Corporation | Systems and methods for utilizing a communications network for providing mobile users access to legacy systems |
JP3654773B2 (en) | 1998-07-08 | 2005-06-02 | 富士通株式会社 | Information exchange method, information management distribution device, information management device, information distribution device, computer readable recording medium recording information management distribution program, computer readable recording medium recording information management program, and information distribution program Computer-readable recording medium |
US6167255A (en) | 1998-07-29 | 2000-12-26 | @Track Communications, Inc. | System and method for providing menu data using a communication network |
US6185484B1 (en) | 1998-08-05 | 2001-02-06 | Eaton Corporation | Method of operating a motor vehicle management computer system |
IL127569A0 (en) * | 1998-09-16 | 1999-10-28 | Comsense Technologies Ltd | Interactive toys |
KR100322578B1 (en) | 1998-10-02 | 2002-03-08 | 윤종용 | Data communication device and method between WAP terminal and WAP server |
US6229477B1 (en) | 1998-10-16 | 2001-05-08 | Hughes Electronics Corporation | Method and system for determining a position of a communication satellite utilizing two-way ranging |
KR100343172B1 (en) | 1998-10-29 | 2002-08-22 | 삼성전자 주식회사 | Wireless data transmission method and interworking device between mobile terminal and heterogeneous signal |
US6321092B1 (en) | 1998-11-03 | 2001-11-20 | Signal Soft Corporation | Multiple input data management for wireless location-based applications |
US6324396B1 (en) | 1998-11-04 | 2001-11-27 | Ericsson Inc. | Calling party number provisioning |
US6430276B1 (en) | 1998-11-18 | 2002-08-06 | Hewlett-Packard Company | Telecommunications system and method providing generic network access service |
US8135413B2 (en) | 1998-11-24 | 2012-03-13 | Tracbeam Llc | Platform and applications for wireless location and other complex services |
US6442479B1 (en) | 1998-12-04 | 2002-08-27 | Patrick Barton | Method and apparatus for a location sensitive database |
US6246948B1 (en) | 1998-12-10 | 2001-06-12 | Ericsson Inc. | Wireless intelligent vehicle speed control or monitoring system and method |
US6208866B1 (en) | 1998-12-30 | 2001-03-27 | Ericsson Inc. | System and method for location-based marketing to mobile stations within a cellular network |
US6496931B1 (en) | 1998-12-31 | 2002-12-17 | Lucent Technologies Inc. | Anonymous web site user information communication method |
US6360101B1 (en) | 1998-12-31 | 2002-03-19 | Ericsson Inc. | Cellular phone that displays or sends messages upon its arrival at a predetermined location |
US6184829B1 (en) | 1999-01-08 | 2001-02-06 | Trueposition, Inc. | Calibration for wireless location system |
US6876858B1 (en) | 1999-01-20 | 2005-04-05 | Lojack Operating Company, Lp | Methods of and system for portable cellular phone voice communication and positional location data communication using the cellular phone network control channel |
US6332127B1 (en) | 1999-01-28 | 2001-12-18 | International Business Machines Corporation | Systems, methods and computer program products for providing time and location specific advertising via the internet |
US6389426B1 (en) | 1999-02-09 | 2002-05-14 | Worldcom, Inc. | Central trouble ticket database and system and method for managing same to facilitate ticketing, trending, and tracking processes |
US6317718B1 (en) | 1999-02-26 | 2001-11-13 | Accenture Properties (2) B.V. | System, method and article of manufacture for location-based filtering for shopping agent in the physical world |
US6430562B1 (en) | 1999-03-01 | 2002-08-06 | Electronic Data Systems Corporation | Integrated resource management system and method |
US6618474B1 (en) | 1999-03-08 | 2003-09-09 | Morris Reese | Method and apparatus for providing to a customer a promotional message between ringing signals or after a call waiting tone |
US6311069B1 (en) | 1999-03-18 | 2001-10-30 | Ericsson Inc. | System and method for alerting a mobile subscriber being positioned |
US6470378B1 (en) | 1999-03-31 | 2002-10-22 | Intel Corporation | Dynamic content customization in a clientserver environment |
GB2348568A (en) | 1999-03-31 | 2000-10-04 | Ibm | Enabling conformance to legislative requirements for mobile devices |
US6954147B1 (en) | 1999-03-31 | 2005-10-11 | Lenovo Pte. Ltd. | Method and system for providing protection against theft and loss of a portable computer system |
US6463533B1 (en) | 1999-04-15 | 2002-10-08 | Webtv Networks, Inc. | System for generating site-specific user aliases in a computer network |
US6236362B1 (en) | 1999-04-20 | 2001-05-22 | Harris Corporation | Mitigation of antenna test range impairments caused by presence of undesirable emitters |
US6385591B1 (en) | 1999-05-11 | 2002-05-07 | Jeffrey W. Mankoff | Method and system for electronic organization of coupons |
US6298234B1 (en) | 1999-05-18 | 2001-10-02 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for providing access to the internet via a radio telecommunications network |
JP4639016B2 (en) | 1999-06-08 | 2011-02-23 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Mobile internet access |
US6377810B1 (en) | 1999-06-11 | 2002-04-23 | Motorola, Inc. | Method of operation of mobile wireless communication system with location information |
US6577644B1 (en) | 1999-06-22 | 2003-06-10 | Lucent Technologies Inc. | Quality of service (QoS) enhancement to multilink point-to-point protocol (PPP) |
JP3896728B2 (en) | 1999-06-23 | 2007-03-22 | トヨタ自動車株式会社 | Portable terminal device and in-vehicle information processing device |
US6704311B1 (en) | 1999-06-25 | 2004-03-09 | Lucent Technologies Inc. | Application-level switching server for internet protocol (IP) based networks |
US7005985B1 (en) | 1999-07-20 | 2006-02-28 | Axcess, Inc. | Radio frequency identification system and method |
US6263209B1 (en) | 1999-07-28 | 2001-07-17 | Motorola, Inc. | Method and apparatus in a wireless communication system for creating a learning function |
US20050026589A1 (en) | 1999-07-29 | 2005-02-03 | Bryan Holland | Remote locator system using A E911-enabled wireless system |
US6560442B1 (en) | 1999-08-12 | 2003-05-06 | Ericsson Inc. | System and method for profiling the location of mobile radio traffic in a wireless communications network |
US20060167986A1 (en) | 1999-08-30 | 2006-07-27 | Trzyna Peter K | Internet telephone system |
US6332163B1 (en) | 1999-09-01 | 2001-12-18 | Accenture, Llp | Method for providing communication services over a computer network system |
US6594482B1 (en) | 1999-09-07 | 2003-07-15 | Ericsson Inc. | Controlled transmission of wireless communications device identity |
US20020052781A1 (en) | 1999-09-10 | 2002-05-02 | Avantgo, Inc. | Interactive advertisement mechanism on a mobile device |
US6732080B1 (en) | 1999-09-15 | 2004-05-04 | Nokia Corporation | System and method of providing personal calendar services |
US6829475B1 (en) | 1999-09-22 | 2004-12-07 | Motorola, Inc. | Method and apparatus for saving enhanced information contained in content sent to a wireless communication device |
US6266615B1 (en) | 1999-09-27 | 2001-07-24 | Televigation, Inc. | Method and system for an interactive and real-time distributed navigation system |
US6622016B1 (en) | 1999-10-04 | 2003-09-16 | Sprint Spectrum L.P. | System for controlled provisioning of telecommunications services |
US6522876B1 (en) | 1999-10-04 | 2003-02-18 | Sprint Spectrum L.P. | System for managing telecommunications services through use of customized profile management codes |
US6366561B1 (en) | 1999-11-03 | 2002-04-02 | Qualcomm Inc. | Method and apparatus for providing mobility within a network |
US6571221B1 (en) | 1999-11-03 | 2003-05-27 | Wayport, Inc. | Network communication service with an improved subscriber model using digital certificates |
US7124101B1 (en) | 1999-11-22 | 2006-10-17 | Accenture Llp | Asset tracking in a network-based supply chain environment |
US6442687B1 (en) | 1999-12-02 | 2002-08-27 | Ponoi Corp. | System and method for secure and anonymous communications |
US6628928B1 (en) | 1999-12-10 | 2003-09-30 | Ecarmerce Incorporated | Internet-based interactive radio system for use with broadcast radio stations |
US6615131B1 (en) | 1999-12-21 | 2003-09-02 | Televigation, Inc. | Method and system for an efficient operating environment in a real-time navigation system |
US6405123B1 (en) | 1999-12-21 | 2002-06-11 | Televigation, Inc. | Method and system for an efficient operating environment in a real-time navigation system |
US6633633B1 (en) | 1999-12-22 | 2003-10-14 | Bellsouth Intellectuel Property Corporation | Method and system for providing calling number restoral |
US6343290B1 (en) | 1999-12-22 | 2002-01-29 | Celeritas Technologies, L.L.C. | Geographic network management system |
US6516055B1 (en) | 1999-12-29 | 2003-02-04 | Bellsouth Intellectual Property Corp. | Interface for trouble report input system and trouble report resolution system |
US6356841B1 (en) | 1999-12-29 | 2002-03-12 | Bellsouth Intellectual Property Corporation | G.P.S. management system |
US6505048B1 (en) | 1999-12-30 | 2003-01-07 | Samsung Electronics Co., Ltd. | Location privacy feature for wireless mobile stations and method of operation |
AU2627401A (en) | 2000-01-04 | 2001-07-16 | Callnetics Corporation | A method and system for coordinating real estate appointments |
US20020035493A1 (en) | 2000-01-04 | 2002-03-21 | Bahram Mozayeny | Method and system for coordinating appointments |
US6546257B1 (en) | 2000-01-31 | 2003-04-08 | Kavin K. Stewart | Providing promotional material based on repeated travel patterns |
US6662014B1 (en) | 2000-02-04 | 2003-12-09 | Sbc Properties, L.P. | Location privacy manager for a wireless communication device and method therefor |
US6415018B1 (en) | 2000-02-08 | 2002-07-02 | Lucent Technologies Inc. | Telecommunication system and method for handling special number calls having geographic sensitivity |
US6640098B1 (en) | 2000-02-14 | 2003-10-28 | Action Engine Corporation | System for obtaining service-related information for local interactive wireless devices |
US6484148B1 (en) | 2000-02-19 | 2002-11-19 | John E. Boyd | Electronic advertising device and method of using the same |
JP4529233B2 (en) | 2000-02-21 | 2010-08-25 | ソニー株式会社 | Control method of composite terminal and composite terminal device |
US7212829B1 (en) | 2000-02-28 | 2007-05-01 | Chung Lau | Method and system for providing shipment tracking and notifications |
WO2001065380A1 (en) | 2000-02-29 | 2001-09-07 | Iprivacy Llc | Anonymous and private browsing of web-sites through private portals |
US6650901B1 (en) | 2000-02-29 | 2003-11-18 | 3Com Corporation | System and method for providing user-configured telephone service in a data network telephony system |
US20020035474A1 (en) | 2000-07-18 | 2002-03-21 | Ahmet Alpdemir | Voice-interactive marketplace providing time and money saving benefits and real-time promotion publishing and feedback |
WO2001071591A1 (en) | 2000-03-24 | 2001-09-27 | Optim Corporation | Advertising system |
US6868074B1 (en) | 2000-03-30 | 2005-03-15 | Mci, Inc. | Mobile data device and method of locating mobile data device |
US6282486B1 (en) | 2000-04-03 | 2001-08-28 | International Business Machines Corporation | Distributed system and method for detecting traffic patterns |
US6526275B1 (en) | 2000-04-24 | 2003-02-25 | Motorola, Inc. | Method for informing a user of a communication device where to obtain a product and communication system employing same |
US6654610B1 (en) | 2000-05-05 | 2003-11-25 | Lucent Technologies Inc. | Two-way packet data protocol methods and apparatus for a mobile telecommunication system |
US20010051911A1 (en) | 2000-05-09 | 2001-12-13 | Marks Michael B. | Bidding method for internet/wireless advertising and priority ranking in search results |
US6937869B1 (en) | 2000-05-10 | 2005-08-30 | Sprint Spectrum L.P. | Route planning system for mobile telecommunications |
US20020091991A1 (en) | 2000-05-11 | 2002-07-11 | Castro Juan Carlos | Unified real-time microprocessor computer |
US20020174147A1 (en) | 2000-05-19 | 2002-11-21 | Zhi Wang | System and method for transcoding information for an audio or limited display user interface |
US6701160B1 (en) | 2000-05-22 | 2004-03-02 | Motorola, Inc. | Method and apparatus to locally block incoming selected calls |
JP2001333455A (en) | 2000-05-23 | 2001-11-30 | Aisin Aw Co Ltd | Mobile body advertisement information distribution method, mobile body advertisement information distribution system, mobile body advertisement information registration system, mobile body advertisement information charging system, mobile communication device and recording medium |
US8060389B2 (en) * | 2000-06-07 | 2011-11-15 | Apple Inc. | System and method for anonymous location based services |
US6456234B1 (en) | 2000-06-07 | 2002-09-24 | William J. Johnson | System and method for proactive content delivery by situation location |
US6754504B1 (en) | 2000-06-10 | 2004-06-22 | Motorola, Inc. | Method and apparatus for controlling environmental conditions using a personal area network |
US6477382B1 (en) | 2000-06-12 | 2002-11-05 | Intel Corporation | Flexible paging for packet data |
US6732101B1 (en) | 2000-06-15 | 2004-05-04 | Zix Corporation | Secure message forwarding system detecting user's preferences including security preferences |
US20020038384A1 (en) | 2000-06-16 | 2002-03-28 | Khan Umair A. | System, method and computer program product for transcoding tabular content for display on thin client devices by way of content addressing |
US6505049B1 (en) | 2000-06-23 | 2003-01-07 | Motorola, Inc. | Method and apparatus in a communication network for facilitating a use of location-based applications |
US6716101B1 (en) | 2000-06-28 | 2004-04-06 | Bellsouth Intellectual Property Corporation | System and method for monitoring the location of individuals via the world wide web using a wireless communications network |
US6738808B1 (en) | 2000-06-30 | 2004-05-18 | Bell South Intellectual Property Corporation | Anonymous location service for wireless networks |
US6675017B1 (en) | 2000-06-30 | 2004-01-06 | Bellsouth Intellectual Property Corporation | Location blocking service for wireless networks |
US6545596B1 (en) | 2000-06-30 | 2003-04-08 | Cisco Technology, Inc. | Presenting information to mobile targets |
US6874011B1 (en) | 2000-07-31 | 2005-03-29 | Cisco Technology, Inc. | Scalable IP-based notification architecture for unified messaging |
US7796998B1 (en) | 2000-08-01 | 2010-09-14 | At&T Intellectual Property, I, L.P. | Method and system for delivery of a calling party's location |
US6647269B2 (en) | 2000-08-07 | 2003-11-11 | Telcontar | Method and system for analyzing advertisements delivered to a mobile unit |
US6505163B1 (en) | 2000-08-09 | 2003-01-07 | Bellsouth Intellectual Property Corporation | Network and method for providing an automatic recall telecommunications service with automatic speech recognition capability |
US6628938B1 (en) | 2000-08-14 | 2003-09-30 | Koninklijke Philips Electronics N.V. | Wireless system, a method of selecting an application while receiving application specific messages and user location method using user location awareness |
US6415019B1 (en) | 2000-08-21 | 2002-07-02 | Ameritech Corporation | Method of providing 911 service to a private branch exchange |
US6618593B1 (en) | 2000-09-08 | 2003-09-09 | Rovingradar, Inc. | Location dependent user matching system |
US20020095312A1 (en) | 2000-09-22 | 2002-07-18 | Tammy Wheat | Facilitating realtime information interexchange between a telecommunications network and a service provider |
US6725048B2 (en) | 2000-09-22 | 2004-04-20 | Ericsson Inc. | Traffic congestion management when providing realtime information to service providers |
US20020037722A1 (en) | 2000-09-22 | 2002-03-28 | Tahir Hussain | Facilitating realtime information interexchange between a telecommunications network and a service provider |
US20020037709A1 (en) | 2000-09-22 | 2002-03-28 | Ranjit Bhatia | System, method and apparatus for facilitating the receipt of realtime information from telecommunications nodes |
US7043231B2 (en) | 2000-09-22 | 2006-05-09 | Ericsson Inc. | System, method and apparatus for polling telecommunications nodes for real-time information |
US7181529B2 (en) | 2000-09-22 | 2007-02-20 | Ericsson Inc. | Business to business engine and system for facilitating information interexchange using realtime data |
US6816720B2 (en) | 2000-09-22 | 2004-11-09 | Ericsson Inc. | Call-based provisioning of mobile equipment location information |
US7177651B1 (en) | 2000-09-22 | 2007-02-13 | Texas Instruments Incorporated | System and method for the exchange of location information in a telephone network |
US20020037744A1 (en) | 2000-09-22 | 2002-03-28 | Ranjit Bhatia | Telecommunications device for sending realtime information to a business-to-business engine for facilitating services to the telecommunications device |
US20020038362A1 (en) | 2000-09-22 | 2002-03-28 | Ranjit Bhatia | Apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider |
US7076275B1 (en) | 2000-10-13 | 2006-07-11 | Palmsource, Inc. | Method and system for single-step enablement of telephony functionality for a portable computer system |
US6414635B1 (en) | 2000-10-23 | 2002-07-02 | Wayport, Inc. | Geographic-based communication service system with more precise determination of a user's known geographic location |
DE60119062T2 (en) | 2000-10-31 | 2006-11-30 | Matsushita Electric Industrial Co., Ltd., Kadoma | navigation device |
US6640184B1 (en) | 2000-11-10 | 2003-10-28 | Motorola, Inc. | Method and apparatus for providing location information |
US6850758B1 (en) | 2000-11-28 | 2005-02-01 | Nortel Networks Limited | Method and system for integrating fixed terminals in a mobile telecommunication network |
US20020107027A1 (en) | 2000-12-06 | 2002-08-08 | O'neil Joseph Thomas | Targeted advertising for commuters with mobile IP terminals |
US7023995B2 (en) | 2000-12-08 | 2006-04-04 | Telefonaktiebolaget L M Ericsson (Publ) | Secure location-based services system and method |
US7245925B2 (en) | 2000-12-19 | 2007-07-17 | At&T Intellectual Property, Inc. | System and method for using location information to execute an action |
US7085555B2 (en) | 2000-12-19 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Location blocking service from a web advertiser |
US7181225B1 (en) | 2000-12-19 | 2007-02-20 | Bellsouth Intellectual Property Corporation | System and method for surveying wireless device users by location |
US7224978B2 (en) | 2000-12-19 | 2007-05-29 | Bellsouth Intellectual Property Corporation | Location blocking service from a wireless service provider |
US7428411B2 (en) | 2000-12-19 | 2008-09-23 | At&T Delaware Intellectual Property, Inc. | Location-based security rules |
US6799049B1 (en) | 2000-12-19 | 2004-09-28 | Bellsouth Intellectual Property Corporation | System and method for tracking movement of a wireless device |
US7116977B1 (en) | 2000-12-19 | 2006-10-03 | Bellsouth Intellectual Property Corporation | System and method for using location information to execute an action |
US7110749B2 (en) | 2000-12-19 | 2006-09-19 | Bellsouth Intellectual Property Corporation | Identity blocking service from a wireless service provider |
US7130630B1 (en) | 2000-12-19 | 2006-10-31 | Bellsouth Intellectual Property Corporation | Location query service for wireless networks |
US20020077897A1 (en) | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a web advertiser |
US6839552B1 (en) | 2000-12-26 | 2005-01-04 | Bellsouth Intellectual Property Corporation | System and method for reporting an emergency situation |
US7062469B2 (en) | 2001-01-02 | 2006-06-13 | Nokia Corporation | System and method for public wireless network access subsidized by dynamic display advertising |
US7076531B2 (en) | 2001-02-28 | 2006-07-11 | Microsoft Corporation | Broadband sign-off |
US6484092B2 (en) | 2001-03-28 | 2002-11-19 | Intel Corporation | Method and system for dynamic and interactive route finding |
US6867733B2 (en) | 2001-04-09 | 2005-03-15 | At Road, Inc. | Method and system for a plurality of mobile units to locate one another |
US6427119B1 (en) | 2001-04-16 | 2002-07-30 | General Motors Corporation | Method and system for providing multiple entry points to a vehicle navigation route |
US6701251B2 (en) | 2001-04-18 | 2004-03-02 | General Motors Corporation | Method and system for providing multiple beginning maneuvers for navigation of a vehicle |
US6526349B2 (en) | 2001-04-23 | 2003-02-25 | Motorola, Inc. | Method of compiling navigation route content |
US20030030731A1 (en) | 2001-05-03 | 2003-02-13 | Colby Steven M. | System and method for transferring image data between digital cameras |
US7139722B2 (en) | 2001-06-27 | 2006-11-21 | Bellsouth Intellectual Property Corporation | Location and time sensitive wireless calendaring |
US20030016233A1 (en) | 2001-06-29 | 2003-01-23 | Bitflash Graphics, Inc. | Method and system for manipulation of graphics information |
US6532418B2 (en) | 2001-07-02 | 2003-03-11 | Samsung Electronics, Co., Ltd. | Vehicle navigation network, apparatus and method for use in a mobile telecommunication system |
US20050043036A1 (en) | 2001-07-05 | 2005-02-24 | Ioppe Igor V | Apparatus and method for obtaining location information of mobile stations in a wireless communications network |
US7333820B2 (en) | 2001-07-17 | 2008-02-19 | Networks In Motion, Inc. | System and method for providing routing, mapping, and relative position information to users of a communication network |
US6407673B1 (en) | 2001-09-04 | 2002-06-18 | The Rail Network, Inc. | Transit vehicle multimedia broadcast system |
US6754582B1 (en) | 2001-10-25 | 2004-06-22 | Bellsouth Intellectual Property Corp. | Methods and systems for routing travel between origin and destination service locations using global satellite positioning |
US6772064B1 (en) | 2001-10-25 | 2004-08-03 | Bellsouth Intellectual Property Corporation | Methods and systems for determining a telecommunications service location using global satellite positioning |
GB0128027D0 (en) | 2001-11-22 | 2002-01-16 | Nokia Corp | Provision of location information |
US7362851B2 (en) | 2001-11-28 | 2008-04-22 | At&T Delaware Intellectual Property, Inc. | Location ID service for telephone calls |
US6721406B1 (en) | 2001-11-28 | 2004-04-13 | Bellsouth Intellectual Property Corporation | Telephone caller location data retrieval |
US20030135552A1 (en) * | 2002-01-14 | 2003-07-17 | Blackstock Michael A. | Method for discovering and discriminating devices on local collaborative networks to facilitate collaboration among users |
US20050060365A1 (en) | 2002-01-24 | 2005-03-17 | Robinson Scott L. | Context-based information processing |
US20030140088A1 (en) | 2002-01-24 | 2003-07-24 | Robinson Scott H. | Context-based information processing |
US7250846B2 (en) | 2002-03-05 | 2007-07-31 | International Business Machines Corporation | Method and apparatus for providing dynamic user alert |
WO2003096709A2 (en) | 2002-05-07 | 2003-11-20 | Teltier Technologies, Inc. | Method and system for supporting non-intrusive and effective voice communication among mobile users |
US7127400B2 (en) | 2002-05-22 | 2006-10-24 | Bellsouth Intellectual Property Corporation | Methods and systems for personal interactive voice response |
US7190960B2 (en) | 2002-06-14 | 2007-03-13 | Cingular Wireless Ii, Llc | System for providing location-based services in a wireless network, such as modifying locating privileges among individuals and managing lists of individuals associated with such privileges |
US7203502B2 (en) | 2002-06-14 | 2007-04-10 | Cingular Wireless Ii, Llc | System for providing location-based services in a wireless network, such as locating individuals and coordinating meetings |
US7236799B2 (en) | 2002-06-14 | 2007-06-26 | Cingular Wireless Ii, Llc | Apparatus and systems for providing location-based services within a wireless network |
DE10256457B4 (en) | 2002-12-03 | 2005-05-25 | Siemens Ag | Exchange of geographical position information between position information server and core network element |
GB2396779B (en) | 2002-12-23 | 2007-07-25 | Samsung Electronics Co Ltd | Mobile communications |
EP1435749A1 (en) | 2002-12-30 | 2004-07-07 | Evolium S.A.S. | Location based call barring |
JP4396245B2 (en) | 2003-02-04 | 2010-01-13 | 日本電気株式会社 | Mobile communication terminal operation restriction system with photographing function and mobile communication terminal with photographing function |
US6985747B2 (en) | 2003-02-05 | 2006-01-10 | Autodesk, Inc. | Use of triggers and a location hypercube to enable push-based location applications |
US7012506B2 (en) * | 2003-04-14 | 2006-03-14 | Woodstream Corporation | Ultrasonic pest repeller |
US20050050227A1 (en) | 2003-07-03 | 2005-03-03 | Cascade Basic Research Corp. | Method and system for peer-to-peer directory services |
WO2004080092A1 (en) | 2003-09-18 | 2004-09-16 | Siemens Aktiengesellschaft | Device and method for allowing or barring provision of a service and for generating a restriction rule for the same |
DE10345511B4 (en) * | 2003-09-30 | 2005-11-17 | Siemens Ag | Method for determining the spatial position of at least one mobile radio communication device, associated radio communication device and radio communication system |
US20050114777A1 (en) | 2003-11-26 | 2005-05-26 | Yahoo, Inc. | Calendar integration with instant messaging |
US8353028B2 (en) | 2004-06-21 | 2013-01-08 | Ebay Inc. | Render engine, and method of using the same, to verify data for access and/or publication via a computer system |
US7257387B2 (en) | 2004-06-30 | 2007-08-14 | At&T Intellectual Property, Inc. | Method and system for emergency control of a voice/data communications device |
WO2006017668A1 (en) | 2004-08-04 | 2006-02-16 | Celltitude, Inc. | Determining location of a wireless handset from another wireless handset |
US20060059043A1 (en) | 2004-09-14 | 2006-03-16 | Chan Wesley T | Method and system to provide wireless access at a reduced rate |
US7643833B2 (en) | 2004-09-29 | 2010-01-05 | Alcatel-Lucent Usa Inc. | Methods and systems for proximity communication |
US20060189332A1 (en) | 2005-02-24 | 2006-08-24 | Lucent Technologies Inc. | Customized location area cluster paging |
US8023937B2 (en) | 2005-03-04 | 2011-09-20 | Qualcomm Incorporated | Apparatus and methods for determining voice and/or data processing performance of a wireless device |
US7515909B2 (en) * | 2005-04-21 | 2009-04-07 | Qualcomm Incorporated | Wireless handoffs between multiple networks |
US7848765B2 (en) * | 2005-05-27 | 2010-12-07 | Where, Inc. | Location-based services |
US20080301561A1 (en) | 2005-08-30 | 2008-12-04 | David Bain | Apparatus and method for automation of multimedia-enabled correspondence management systems (MCMS) |
WO2007047798A1 (en) | 2005-10-21 | 2007-04-26 | Sensis Corporation | Method and apparatus for providing secure access control for protected information |
US20070124721A1 (en) | 2005-11-15 | 2007-05-31 | Enpresence, Inc. | Proximity-aware virtual agents for use with wireless mobile devices |
US7787887B2 (en) | 2005-12-26 | 2010-08-31 | Infosys Technolologies Ltd. | Providing location-based services via wireless networks |
US7552467B2 (en) | 2006-04-24 | 2009-06-23 | Jeffrey Dean Lindsay | Security systems for protecting an asset |
US20070281716A1 (en) * | 2006-06-01 | 2007-12-06 | Flipt, Inc | Message transmission system for users of location-aware mobile communication devices in a local area network |
US8407213B2 (en) | 2006-08-31 | 2013-03-26 | Ektimisi Semiotics Holdings, Llc | System and method for identifying a location of interest to be named by a user |
US20090054077A1 (en) | 2007-08-23 | 2009-02-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for sending data relating to a target to a mobile device |
US20090067593A1 (en) | 2007-09-07 | 2009-03-12 | Sony Ericsson Mobile Communications Ab | Method for Dynamically Assembling Voice Messages at a Wireless Communication Device |
US8731155B2 (en) | 2007-12-31 | 2014-05-20 | General Motors Llc | Method for remotely controlling vehicle features |
US20090233633A1 (en) | 2008-01-08 | 2009-09-17 | Mobile Traffic Network, Inc. | Mobile alerting network |
US8223941B2 (en) | 2008-01-29 | 2012-07-17 | At&T Intellectual Property I, Lp | System and method for call handling |
US8639267B2 (en) | 2008-03-14 | 2014-01-28 | William J. Johnson | System and method for location based exchanges of data facilitating distributed locational applications |
US8566839B2 (en) | 2008-03-14 | 2013-10-22 | William J. Johnson | System and method for automated content presentation objects |
US8600341B2 (en) | 2008-03-14 | 2013-12-03 | William J. Johnson | System and method for location based exchanges of data facilitating distributed locational applications |
US8634796B2 (en) | 2008-03-14 | 2014-01-21 | William J. Johnson | System and method for location based exchanges of data facilitating distributed location applications |
US8761751B2 (en) | 2008-03-14 | 2014-06-24 | William J. Johnson | System and method for targeting data processing system(s) with data |
US8750841B2 (en) | 2008-03-14 | 2014-06-10 | William J. Johnson | System and method for automatically leaving an outgoing caller message |
US9880954B2 (en) | 2008-12-01 | 2018-01-30 | Micron Technology, Inc. | Method and apparatus for providing data access |
US8948787B2 (en) | 2008-12-23 | 2015-02-03 | At&T Intellectual Property I, L.P. | Configuration of telephony services for phone based on user location |
-
2008
- 2008-03-14 US US12/077,041 patent/US8600341B2/en not_active Expired - Fee Related
-
2013
- 2013-09-23 US US14/033,539 patent/US8750823B2/en not_active Expired - Fee Related
- 2013-09-23 US US14/033,543 patent/US8886226B2/en active Active
- 2013-09-23 US US14/033,540 patent/US8761804B2/en active Active
-
2014
- 2014-06-09 US US14/299,910 patent/US20140289234A1/en not_active Abandoned
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107944300A (en) * | 2017-11-01 | 2018-04-20 | 深信服科技股份有限公司 | A kind of method for writing data and device, verification method and device |
US11436534B2 (en) | 2020-05-20 | 2022-09-06 | Bank Of America Corporation | Distributed artificial intelligence model |
US11727306B2 (en) | 2020-05-20 | 2023-08-15 | Bank Of America Corporation | Distributed artificial intelligence model with deception nodes |
Also Published As
Publication number | Publication date |
---|---|
US8886226B2 (en) | 2014-11-11 |
US20090233622A1 (en) | 2009-09-17 |
US8750823B2 (en) | 2014-06-10 |
US8761804B2 (en) | 2014-06-24 |
US8600341B2 (en) | 2013-12-03 |
US20140024393A1 (en) | 2014-01-23 |
US20140024396A1 (en) | 2014-01-23 |
US20140024397A1 (en) | 2014-01-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8750823B2 (en) | System and method for location based exchanges of data facilitating distributed locational applications | |
US9253597B2 (en) | System and method for determining mobile users of interest | |
US11589691B2 (en) | System and method for locational image processing | |
US10292011B2 (en) | System and method for location based exchange network | |
US7558851B2 (en) | Locating a mobile computing unit |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION |