Communications – William J. Johnson
Abstract for “System and Method for Location Based Exchange Network”
“Mobile data processing systems (MSs), interact with other systems in their immediate vicinity and with each others in communications and interoperability. Information sent inbound to, and outbound from, information is in process at, or application modified at, a mobile data processor system triggers processing according to user configurations, such as to present content to users. A Location-Network Expandse is the name of the locatable network MSs.
Background for “System and Method for Location Based Exchange Network”
The internet is bursting with new service offerings. Google.com and iTunes.com are examples of websites that can provide valuable services to a wide audience via the internet. There are many types of web services that can be used for different functions. The advantages of using a service to act as an intermediary between clients, users, systems and services include centralized processing and centralized maintenance of data. This includes an all-knowing database that can be used to determine the scope of services offered, a supervisory point for control, giving an administrator access to the data maintained by web service users, as well other benefits associated with central control. These advantages are similar to those offered by the traditional mainframe computer to clients. The mainframe controls all resources, data and processing and provides central control over all users and systems (clients). As computers became cheaper, adequate processing power was made available to more distributed systems such as Open Systems (i.e. The mainframe no longer needed to be used for most computing tasks. High-powered mobile devices, as well as other mobile data processing platforms, can provide adequate processing power. Technology is enabling greater processing power and data storage in a smaller device. Open Systems took a lot of the computing load off mainframe computers. Mobile data processing systems can also offload tasks normally performed by web services. Mobile data processing systems have become more powerful and there’s no need to provide a service for middleman interactions between them.
While a central service can have its benefits, it also has its drawbacks. The service acts as a clearinghouse for all transactions in web services. The web service can be a bottleneck regardless of how many threads are processed across hardware and processor platforms. This can lead to poor performance and slow response times. It can also cause large amounts of data that must remain accessible for all users and/or systems. Even the largest web services are subject to overhead and poor performance. Web service responses will not be quick enough. Archive backups are necessary to allow for recovery in case of disaster. The service stores all data required to run its operations. Archive storage, processing power and planning are all necessary. To accommodate millions of users or systems that connect to the service, a large and expensive data center is required. This service requires a lot of overhead. It is very expensive to provide data center processing power, data bandwidth, speed, and data transmission bandwidth, as well as infrastructure entities and other performance considerations. Real estate costs, electricity and cooling bills, maintenance of the system, staff to manage a business, etc. are all included in these costs. It is necessary to find a way to reduce large data center expenses while ensuring that features are delivered as promised. As users demand more functionality and features on their mobile data processing systems, it is likely that processing will move closer to the device in order to maximize performance and reduce infrastructure costs.
U.S. Pat. Nos. 6,456,234; 6,731,238; 7,187,997 (Johnson). In U.S. PTO Publication 2006/0022048 (Johnson), anonymous location-based services were disclosed. The Johnson patents and the published application function in the same way as other web services. Clients who connect to the service are able to benefit from it by having some connectivity. U.S. U.S. This may not be a problem for a company with large web services resources but it could be a concern for smaller companies. It is necessary to enable location-dependent functionality and functionality without the need for a service.
As internet services grow, users are more concerned about their privacy. By its very nature, a service typically stores information about a user in a central service database. The service can store the user’s credentials, preferences, customizations, billing information and surfing habits. Access may be granted to company insiders and outside attackers. People are concerned about ensuring that personal information is not stored in a central database. This could lead to security breaches. Services that are location-based are more concerning, especially if the users’ locations are known to the centralized service. It is necessary to provide a system and method that allows users to feel more comfortable knowing their personal information is less at risk.
“It is reasonable to require mobile data processing system intelligence, such as knowing their locations and those of nearby mobile data processing units. Mobile data processing systems are able to handle many of their application requirements themselves without relying on remote services. Mobile data processing systems do not require a service provider to provide useful functionality or features that are location dependent. This is just like two employees in a company should not have to talk to one another. It should not be the end for social interaction implemented locally to mobile data processing systems. Rather, it should be the beginning point for many useful distributed local applications that don’t require a service.
“Different users have different types of Mobile Data Processing Systems (MSs), also known as mobile devices, such as laptops, tablet computers, Personal Computers, Personal Digital Assistants, (PDAs), personal computers, Personal Navigational Devices, (PNDs), iPhones (iPhone trademarked by Apple, Inc.), and various mobile data processing system. MSs can move freely and are unpredictable (i.e. They can be moved wherever and whenever they want. Mobile data processing systems (MSs), many of which are not capable of automatically being located, or do not use a service to automatically locate them. Conventional methods use direct relative stationary references like antennas, satellites, and so on. to locate MSs. Stationary references can be costly to deploy and are susceptible to becoming obsolete as new technologies become available. Stationary references are limited in their ability to locate MSs.
The United States E911 mandate to cellular devices defines requirements for automatic location of a Mobile Data Processing System (MS), such as a cell telephone. However, it does not promote real-time location and tracking, nor does it outline architecture for exploiting Location Based Services. Location Based Services (LBS) and other location-dependent features and functionality are some of the most promising technologies today. Automatically locating every Mobile Data Processing System (MS), is an evolutionary trend. To speed up the process of automatically locating each MS, a method is required. This goal is not possible with prior art technologies like GPS (Global Positioning System), radiowave triangulation, being within range of a known location sensor, and the like. Complex system infrastructures or additional hardware costs for the MSs make such ventures expensive and time-constrained due to schedules and costs associated with engineering, construction and deployment.
“A method is required to enable users to access location dependent features and functionality by having their mobile locations known. This is regardless of whether their MS is equipped for being found. A MS can also be provided with modern location-dependent features and functionality without the need for a connected service.
LBS (Location Based Services), a term that has grown in popularity as MSs include various locations capability, is “LBS” “Services” is a term that refers to services. The term “Services” is used in this terminology to refer to location-based functionality and features that involve interaction between two or more people. This disclosure introduces a new terminology and system called Location Based eXchanges. 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? For the plural term,?Location Based Services’. LBX refers to leveraging the distributed nature and connectivity between MSs instead of leveraging a centralized service nature. LBS and LBX can blur the line between them, as they provide similar or even identical features and functionality. In some cases, strengths from both could be combined. LBX differs from LBS in that it relies less on centralized services and more on distributed interactions among MSs. This is the underlying architectural shift. LBX provides server-free, server-less functionality and location-dependent features.
“Disclosed are many aspects of LBX. They start with the requirement that each MS must know their location at some time. LBX can be enabled when an MS knows whereabouts. It is therefore important to make sure that as many MSs as possible know whereabouts. LBX allows distributed locational applications that allow multiple MSs to know where they are. A server is not needed to facilitate social interactions between MSs. MSs can interact with each other as peers. LBX can be disclosed for peer-to-peer interactions, peer interaction for routing services and peer to peers for delivering distributed service. Peer to peer interactions are also available for location dependent features and functionality (e.g. A first mobile data processing device sends directly (e.g. Wirelessly) to another mobile data processing device without the need for an intermediary data processing system. An LBX-enabled MS can be described as an lbxPhone.
“It is advantageous to not have a centralized service that governs functionality and features based on location among MSs. A centralized service is not necessary to prevent performance problems, infrastructure costs, or solve many of the above issues. A user’s information can not be kept in one place by a centralized service. LBS stores personal data that users can access. This poses a security risk. This increases the chance that data disasters will affect multiple users. LBX distributes data across the participating systems to ensure that a disaster affecting one person does not affect another.
It is possible to enable useful distributed applications without having to have a service and without users or systems needing to register with the service. In preferred embodiments, MSs are considered peers rather than clients to a single service (e.g. “Internet connected web service.”
It is possible to locate as many MSs in a wireless network as possible, without any additional deployment costs for the MSs or network. The conventional locating capabilities include GPS (Global Positioning System), which uses stationary orbiting satellites. There are also improved versions of GPS such as AGPS (Adjusted GPS), and DGPS(Differential GPS) that use stationary-located ground stations. Wireless communications to fixed cell tower base stations can be used. TDOA (Time Difference of arrival) triangulation with stationary antennas. Also, presence detection within the vicinity of a stationary antenna, presence detection at a stationary wired connectivity location, and presence detection at a stationary antenna. Indirectly Located Mobile Data Processing Systems (ILMs) are automatically located by automatically detecting the locations of Directly Located Mobile Data Processing Systems (DLMs) or automatically detecting other ILMs. ILMs have the option to participate in the same LBS or LBX as a DLM (Directly Located Mobile Data Processing System). The conventional locating capability described above is used to locate DLMs. DLMs can be used to automatically locate ILMs regardless of their current location. For example, DLMs and ILMs are highly mobile when used by users. There are many novel ways to locate ILMs automatically. These include triangulating an ILM (Indirectly Located Mobile Data Processing System) location using a plurality ILMs; detecting the ILM’s presence within the vicinity at least one ILM; triangulating the ILM Location using a plurality ILMs; detecting the ILM’s existence within the vicinity at least one ILM; triangulating the ILM Location using a mixed set DLM(s), ILM(s); determining the ILMs/or ILMs and/or ILMs
“MSs can be automatically located by using any other means than direct conventional methods. The conventional locating ability (i.e. The conventional locating capability (i.e., the ability to locate objects using standard methods) is also known as direct methods. Direct methods can be described as conventional methods. However, not all direct methods can be called them that. Below are some new direct techniques. This document contains a system and method for instantly bringing automatic location detection (whether or not the MS is capable of being located directly) to all MSs around the globe. MSs without the ability to be directly located can be located using the automatically detected locations MSs that are directly situated. This is known as being indirect located. A Directly Located Mobile Data Processing System (DLM) is an MS that is located directly. MSs that are located directly are referred to hereinafter as Directly Located Mobile Data Processing Systems (DLMs) for a plural acronym. MSs which are not capable of being located directly can be located by using automatically detected locations of MSs already located. An MS that is located indirectly is hereinafter referred as an Indirectly Located Mobile Data Processing System (ILM). MSs that are located indirectly are hereinafter referred as Indirectly Located Mobile Data Processing Systems (ILMs). These are the ways you can locate a DLM:
“In one case, multiple MSs’ mobile locations are automatically detected by their local GPS chips. Each one is called a DLM. A radio wave is used to triangulate the mobile location of a non-locatable MS. It can be connected with three (3) GPS-equipped DLMs. After its location is determined relative to the DLMs, the MS becomes an ILM. DLMs or other ILMs can automatically locate ILMs. These are the ways you can locate an ILM:
“Locating functionality can leverage GPS functionality. This includes but is not limited to GPS (Adjusted GPS), GPS (Differential GPS), and any other improved GPS embodiment that achieves higher accuracy using known locations such as ground-based reference locations. Nextel is a trademark for Sprint/Nextel. Triangulated locating functionality can include triangulated location of the MS. This could be done by using a class radio frequency (RF) wave spectrum (cellular), WiFi (some WiFi embodiments are referred to as WIMax), etc. It may also use measurements from multiple wave spectrums for a single location determination depending on the available communications interface(s). 70). An MS’s location may be determined using any number of wave spectrum classes (cellular, WiFi and bluetooth). The term WiFi? This disclosure uses the term WiFi? In-range proximity detection may be used to detect the presence of the MS. Triangulated locating may also use wave forms such as microwaves, infrared waves spectrum relative infrared sensor, visible lightwave spectrum relative to visible lightwave sensors, ultraviolet waves spectrum relative ultraviolet wave sensor, Xray wave spectrum relator Xray wave sensor, gamma radiation wave spectrum relativity gamma-ray sensors, longwave spectrum (below am) relative longwave sensors. There are many methods that can automatically locate a MS, such as radio wave triangulation, GPS, in range proximity detection and longwave spectrum (below AM) relative longwave sensors. While radio wave triangulation, GPS and in range proximity detection are the most common methods of automatically locating a MS (e.g.
“Kubler et.al (U.S. PTO publication 2004/0264442, 2004,/0246940 and 2004/0228330,2004/0151151) described methods for detecting mobile entities when they are within the range of a sensor. Kubler and colleagues did not know the exact location of the MS. Therefore, an estimate of the MS’s area is sufficient to achieve the intended functionality. Kubler and colleagues tend to have a low confidence value (i.e. Not confident, with lower values for long-range sensors and higher for short-range sensors.
GPS and the many methods to improve GPS accuracy have led to many successful systems that locate MSs with high accuracy. Triangulation is a reliable method to locate MSs. This disclosure is associated with GPS and triangulating position methods tends be high (i.e. confident). DLMs should use the most accurate method possible to ensure relative ILMs are accurately located. All DLMs do not need to use the exact same location methods. You can locate an ILM relative to other DLMs or ILMs that use different locating methods.
“Another benefit is that MSs can be generically located using a variety and combination of technologies. MSs can be located automatically using conventional methods. This accuracy is based on the location of other MSs. Indirect methods can also be used to locate MSs. It is advantageous to indirect locate MSs that are located in different locations. One DLM could be automatically located by GPS. Cell tower triangulation may also be used to locate another DLM. Another DLM can be located automatically using within range proximity. The ILM may be located in a single place or at different locations as time passes. An algorithm for triangulation may be used to determine the location of an ILM automatically relative to the three DLMs. However, each DLM has a different location method. A preferred embodiment uses industry standard IEEE 802.11 WiFi to triangulate an ILM relative to a number of DLMs (e.g. TDOA is one embodiment. This standard is popular among the more compute-oriented MSs. You can use any of the 802.11 waveforms, such as 802.11a or 802.11b, or any similar class of wave spectrum, between multiple ILMs. 802.x is a general term that refers to all 802. whatever variants.
“Another benefit is to use existing market communications hardware, communications interfaces and communications methods and locations methods wherever possible to locate an MS relative one of more MSs. Although 802.x is the most common RF wave form for WiFi communications, there are other options (e.g. cell phone to cell tower communications. Any wave spectrum that can carry data is applicable herein. Any protocol may be used in the embodiments of these disclosures, e.g. TDMA, CDMA, H.323, SIP, 2G, 3G, ip phone, digital, analog, spectrum frequency, etc).”
“Another advantage is the support for heterogeneous locatable device. Different people prefer different types of devices, as explained above. A device can be fully automated with its location functionality by either remote or local automatic location detection. An ILM can also be found relative to a laptop, cell phone and a PDA (i.e. different device types).”
Another advantage is the inability to store large quantities of positioning data for a network MSs. It can be costly to store, back up, or recover positioning data that is used to determine the location of all devices. The preferred embodiment uses a distributed approach to determine locations of MSs, without having an all-knowing database. It is possible to determine the positions of MSs?on-the-fly? Without the need to store information in a master data base. There are ways to store a master or subset of a master database in configurable storage locations. One MS can store a subset of the master database.
“Another benefit is the use of existing location-equipped MSs to expand our network of locatable device by locating non equipped MSs relative to the location of the MSs that are equipped. The size of the MSs’ locatable network can be increased by MSs. LN-Expanse is the term used to describe the locatable network made up of MSs. Location-Network Expanse). LN-Expanse changes dynamically depending on the location of MSs at a given time. As users travel with their own MSs, LN-Expanse is defined by the MSs that they use to locate other MSs. An ILM requires location awareness relative to MSs (DLMs or ILMs).
A MS can interchangeably take on the role of an ILM or DLM while it travels. This is because MSs can adapt to the availability of location technologies. An MS might be equipped with DLM capability but be at a place where it is not possible to access the capability. In such situations, the DLM assumes the role of an ILM. The MS automatically assumes the role of DLM when it enters another location that can be used as a DLM. This is especially important in emergency situations. An accident occurs in the mountains that prevents GPS-equipped DLM capability from functioning. The MS assumes the role of an ILM automatically and is located in the vicinity of nearby MSs. This allows the hikers to communicate their location and use useful locational applications and features at his MS.
It is also advantageous that MS locations can be triangulated using any wave form (e.g. RF, microwaves, infrared, visible light, ultraviolet, X-ray, gamma ray). Gamma and X-ray applications are unique in that these waves can be harmful to humans for short periods of time. It is important to have the right to use such wave forms. Micro-machines can be used in medical applications to implant within the human body. These micro-machines may be outfitted as MSs. MSs can use wave spectrums that are available at the time they deploy to determine exact positions while traveling through a body.
It is also possible to use TDOA, AOA (Angle Of Arrival), or Missing Part Triangulation(MPT) to locate a MS. TDOA uses information about time to determine where the MS is located, such as distances between sides of a triangle. AOA uses angles to arrive to antennas to geometrially determine where a MS is by intersecting lines from antennas with detected angles. This document describes MPT as combining AOA and TDOA to locate a location. It is not necessary to use all AOA, or all TDOA. MPT can be used to locate MSs.
“Assisted Direct Location Technology (ADLT) is another option for locating MSs. ADLT can be described as the combination of direct (conventional), location capability and indirect location capability to determine the exact location of a MS.
“Another advantage is the ability to manually specify the location of a MS (a DLM). This manual location can be used to locate other MSs. An interface can be used to specify a DLM site. The interface may be remote or local to the DLM. Various manual specification methods are disclosed. Manual specification should be used with less mobile MSs or existing MSs like those that use dodgeball.com, a trademark of Google. The location, validation, and the way it changes as the MS moves, all affect the confidence value. If inaccuracies cannot be avoided, manual specification should limit the scope of an LN-expanse.
“Another benefit is that you can locate a MS using any combination of the methods above and any combinations or indirect location methods described.”
Another advantage is the ability to combine different locating technology for seamless operations when an MS travels. There are many ways to keep an MS updated about its location. It is crucial to keep an MS updated about its location in a timely fashion. This will ensure that LBX operates optimally and allow nearby MSs with locating technology to be located.
It is also a benefit for finding an MS using multiple location technologies on its travels and to using the best data from multiple locations technologies to determine a MS’ location. To ensure accuracy, reference location information is associated with confidence values. A DLM is often an ‘affirmifier?. An affirmifier is an MS that has its location information with high confidence and accuracy. It can be used as a reference for others MSs. An ILM can also serve as an affirmifier, provided that it is located in a location with high confidence. An MS (e.g. An MS (e.g. Pacifiers are MS that have location information about its whereabouts, but with low accuracy. It can be used to reference other ILMs but it cannot do so with a low level of accuracy.
It is another benefit for allowing user customization of confidence levels based on user experience. MS users can rely completely on MS system settings to set confidence values. Or they may “tweak” them. Location technology confidence values are used to account for experiences with specific location technologies encountered while traveling.
It is a benefit to combine the many locating technologies to avoid one type of technology dominating others, while still using the best features from each to determine the precise mobile location of MSs.
A data processing system that can be located to co-locate another data processing systems without being able to locate it is an additional advantage. A driver might have an older model car and a second data processing system that can be used to locate the vehicle. A cell phone belonging to the driver is also a first-data processing system. It can be used to automatically locate the vehicle. For the purpose of locating the second system, the location of the first processing system can be shared. The second data processor system is not automatically located. It is located relative to a plurality of data processing systems that are not located at the same place as the first. Data processing systems can automatically be located relative to at least one other data processing system that can be automatically found.
A LBX-enabled MS also includes a service informant component to keep a supervisory services informed. This prevents an MS operating in complete isolation and allows it to interact with other MSs within its immediate vicinity (e.g. Within the maximum range 1306, at any point in time, and to also participate when MSs are far apart. Although there are LBX that can be incorporated into an LBS model of the LBX model, a preferred embodiment prefers to use it. Multiple MS users may want to carpool to and fro a common destination. Even though information is not maintained at all MSs, the service informant component can provide timely updates to a supervisory services for route comparisons among MSs. Users may discover that they attend the same church and have similar work schedules. Coworkers might find out they live near each other and have identical work hours. To facilitate new LBX applications, the service informant component keeps a service updated on MS location. You can configure the service informant to communicate directly with another MS, to communicate to a data processing service through a propagateable service, or to invoke a?plugin? Home-grown interface: alerting the MS user by a specific alert or invoking an Atomic Command used for charter processing
It is an additional advantage to leverage the large amount of MS WiFi/WiMax deployments underway in the United States. The availability of WiFi/WiMax in greater numbers increases the performance of peer-to-peer types and functionality.
It is also a benefit to avoid established connections interfering with the successful triangulation of a MS location. The MS can be found by interacting with various wave spectrum signals as it roams the world. Broadcast signaling provides the location information necessary to automatically locate the MS.
“Network Time Protocol (NTP), which eliminates bidirectional communication in determining Time of Arrival and Time Difference Of Arrival measurements, is another advantage. TDOA as described in the disclosure refers to both TOA (Time of Arrival) and TDOA. NTP allows for a single, unidirectional transmission to carry all the data necessary to determine TDOA. This is provided that the sending and receiving data processing systems are NTP synchronized with an appropriate granulation of times.
“An additional advantage is the ability to make available to remote peer MSs certain MS Operating System resources such as memory and storage, semaphores or application data, depending on permissions. One MS can access the operating system resources of another MS. This is useful for charter processing, for instance. A network of peers MSs can achieve semaphore-controlled synchronization of processing without the need for a common server.
“It is an advantage to this disclosure to offer a superior alternative to server-based mobile technologies such U.S. Patent. Nos. 6,456,234 and 6,731,238 respectively; 7,187,997 and U.S. PTO Publication 2006.0022048 (Johnson). In order to enhance the user experience, it is a good idea to use both LBX and LBS technology within the same MS. In certain instances, the different technologies can be combined.
A further benefit is the ability to use existing “usual communications?” data transmissions can be used to carry new data that is not being processed by the existing MS processing but is observed by new MS Processing. This allows for processing of large geographic areas with location functions and features. Alternately, new data can also be transferred between systems to achieve the same functionality.
“It is a benefit herein in providing peer-to-peer service propagation. ILMs have the opportunity to take part in the same location-based services (LBS) as DLM(s). MSs may be able to access services that are not available to them. Any MS can share their accessible services to be accessible to other MSs, provided permissions are granted. An MS can, for example, get internet access from another MS with internet access nearby. Preferably, permissions are kept in a peer-to-peer manner before proper service sharing. Another embodiment specifies permissions and uses them at the time of sharing access to shared services. Services can be used as if they were being shared by the sharing user, or as if they are being shared by a new user. As MSs travel, routing paths can be dynamically reconfigured and transparently utilized. Hop counts change dynamically to ensure that MSs have access to the desired service with a minimum number of hops. The route communications depend on the location of the MS that needs the service and the minimal hops required to reach it through other MSs. Services can be transmitted from DLMs or DLMs directly to ILMs. ILMs and DLMs can also be used to propagate services.
“Services that are otherwise unavailable to the first MS (or MS user in the LNExpanse) become available through another MS that has access to the service. The connection may be made possible by multiple MSs (e.g. Hops) may be made from the first MS to last MS that publishes the service. MSs have the ability to access services from nearby MSs if they need them. The service directory is shared among MSs and propagated between them so that all the services in a LNExpanse can be accessed by any MS, regardless of whereabouts, ability, or inability to connect. To achieve the best performance, even for highly mobile MSs, a service route must be minimized. This means that there are fewer hops between MSs in order to reach a service.
It is another benefit for peer-to-peer permissions, authentication and access control. It is not required to maintain credentials and permissions between MSs. Permissions can be maintained locally by a MS. A centralized service model can lead to a large database when it comes to searching for permissions. Database size and performance were both a problem with permission searching and validation for U.S. PTO Publication 2006.0022048 (Johnson). It was costly to maintain who had permission for each permission granted. As described below, local permissions can be kept. This is because the owner of permissions is the MS user. Permission searching is also very fast as the MS needs to only search its local data for permissions applicable to its MS.
Another advantage is the ability to give a near, or nearness status, using a peer-to-peer system and method rather than intelligence kept in a central database for all MSs. It is very costly to maintain a large database that contains all locations of all MSs. This disclosure eliminates this overhead by using nearby detection methods of one MS to locate another MS. There are many controls that can be used to determine the generation of the nearby status. One aspect is that a MS can automatically call the MS nearby, connecting them to a conversation and allowing the user to not have to initiate the call. Locally maintained configurations control functionality when MSs become nearby or depart from being near. In a LBX fashion, queries, alerts, and status are sent to nearby MSs.
It is a further advantage for automatic call handling, call handling and call processing based upon the whereabouts or relative whereabouts a MS. Automatic call forwarding functionality can be affected by the nearness condition between two MSs.
Another advantage is peer-to-peer content delivery and local MS configuration. The service is not accessible from users’ computers. To enjoy content delivery from other MSs based on location, users can create local configurations. The content is delivered in a variety circumstances and for many different reasons. For nearby alerts, arrival and departure to geofenced areas and other predicated conditions, content that is local to an MS will be delivered asynchronously from other MSs. Although it might appear that there are LBS available to MS users, in reality there are LBX available to them.
“Another benefit is that a LBX-enabled MS can work in a peer-to-peer manner with data processing systems which control the environment. An example of this is when an automobile-equipped (or driver-owned) MS meets an intersection with a traffic light. The intersection can be controlled by a data processing device in the vicinity. This will allow for the control of the traffic light and interaction between MSs. Another embodiment allows a user to search for parking lots as he enters a parking lot. This is done in accordance with the available parking spaces. Other nearby data processing systems may also be processed to accommodate user preferences (as described in the MS), group preferences and/or locational preferences (see U.S. Pat. Nos. Nos. terminology) of MSs nearby.
An MS can keep a history of hotspot locations to provide graphical indications of hotspot location. The MS user can use this information to guide users in the future in order to access hotspot services. Hotspot growth can prevent a database from being updated with new locations in a timely manner. As appropriate to each MS, the MS can find hotspots. Hotspot information can be instantly accessed by the MS.
Peer to peer proximity detection is another advantage for identifying peer service targets within the MS area. An MS can act on a peer service target within its range using an application at the MS. An MS can notify the user about service availability by notifying them of the complementary location of the MS and peer service target. The MS application can be used by the user to make a payment or perform any transaction related to the peer service target.
“Another advantage of a MS is its ability to provide self-management capabilities such as automatically marking photos taken with location information, date/time stamps, and who was taking the photo.”
“Another advantage is being alerted nearby to people who need assistance, nearby fire engines, or police cars that require access to roads.”
The MS platform allows for the rapid introduction of new LBX functionality and features to the market. It caters to all levels of users: novice users, highly skilled software developers, and intermediate users. Rich programming environments are available that allow users to trigger privileged actions by exchanging whereabouts information with other MSs. You can embed the programming environment in or?plugged into? an existing software development environment or provide it on its own. An syntax can be specified using source code statements, XML or SQL database definitions. It is possible to create privileged actions in a user-friendly environment by exchanging whereabouts information with other MSs within the same vicinity. This platform is event-based. WDRs that contain certain sought information can be recognized at strategic processing routes for novel processing of actions. You can define events with complex expressions. Actions can also be defined using your own executables, APIs and scripts. There are many ways to define charters and permissions using the LBX platform. These include an internalized programmatic, a SQL database, a data record, a datastream, and a well-defined BNF grammar that can be used to generate other useful implementations (e.g. “lex and yacc”.
It is advantageous for permissions/or charters be configured in anticipation or all possible future travel, situations, environments, applications, or conditions of a MS (or MSuser) or a plurality (by permissions or charters), MSs (or MSusers). It’s powerful because permissions and charters that are configured in advance of expected events reveal novel, unpredicted automated actions and application behavior for new uses.
It is also possible to have a large number of privileges that can all be managed and configured in a peer-to-peer manner between MSs. Any peer-to-peer feature or set can be granted privileges from another user. This is a great advantage because it allows you to provide a variety of ways to manage privileges within a network of MSs.
It is an additional advantage to have a comprehensive set of options for charters. These can be configured, managed and processed in a peer-to-peer manner between MSs. Charters can be made effective by a variety of terms, conditions, and operators. This is a great advantage because it allows you to provide a variety of ways to manage and maintain charters within a networked MS. Charters can be modified by themselves to change permissions and charters “on the fly”. (i.e. ”
It is an additional advantage in multithreaded communications between MSs of permission and charter information, and transactions between MSs to facilitate peer-to-peer interactions. Depending on the MS, any signal spectrum that can be used to transmit and receive data is possible. Different signaling wave types and protocols can be used to interoperate between MSs or for single transactions.
It is another way to increase the LN-expanse’s range from a wireless area to potentially infinite surroundings through data processing (e.g. routing) equipment. Wireless proximity is used to govern automatic location determination. However, whereabouts information can be communicated between MSs that are far apart if there are privileges or charters making this information relevant for each MS. If there are no privileges to keep it, the whereabouts information of others cannot be kept. If there are no privileges granted to potential recipients MSs, whereabouts information cannot be shared.
Another advantage is the ability to configure a MS for any behavior based on whereabouts, location, and?in-the vicinity. Conditions for the MS and/or its peers MSs during travels. The user can provide a processing “character” with infinite control. The MS supports many MS applications with location-based functionality and features. Charts can be used to automate: MS configuration and system variable settings, clipboard and paste operations and MS input and out control. They also allow for automatic communications with MSs and data processing systems.
Another advantage is the use of a user interface such map navigation to generate a map term, such as a point or radius, or a set of points that define area(s), on a map. This map term can be referenced in a charter configuration, and then processed for replacement. A user can make selections on a map and the location information for those selections is generated automatically. Without having to know the exact location information, the user can give the information a name. For more information about the location details, the user can refer to the name. The WDR search criteria can be used to determine a map term. This is a WDR that was found in the MS of map terms creation or a peer MS. Recent WDR location (e.g. Queue 22; or Past whereabouts of WDRs found (e.g. History 30 may also be used. Queue 22 can be considered to be maintaining a short-term history while history 30 could be considered to be maintaining a long-term history. It can be difficult to specify locations in charter configurations. The user can use map terms to indicate locations and hide the complexity of how it was generated. Some embodiments allow map terms to be used in a wider scope, allowing substitutions where necessary. Some embodiments allow map terms to be used in a wider scope by allowing?special terms? to be created automatically by the user by selecting a MS from a map.”
It is a benefit for a convenient “charters starters?” User interface to browse, enable, disable, and maintain charters depending upon application, categories, or usable/cloneable snippets. A MS might come prepackaged with many different charters that have been marked and organized for specific applications. A user can search for, locate, manage, enable/disable, or disable a group of charters according to their category. They can also clone charter subsets to create new charters. MS users can manage their own charters or charters of privilege granted to others using the charters starters interfaces. A user can search, find, manage, and disable a set charters using any criteria contained in the charter definitions. An authorized or knowledgeable user can organize charters in any way he chooses, such as to assign charters to specific categories and applications. The user interface for charter starters organizes charters into easily identifiable groups (e.g. The user interface for charter starters organizes complex charter configurations in easily identifiable groups (e.g., folders, categories, and applications). It makes it easy to enable, disable, and organize any desired set of complex charter configurations.
It is a benefit to provide application term triggered processing for the LBX platform and all users and skill levels thereof. It provides a rich programming environment with a user-friendly configuration environment. Application data that is modified can trigger privileged actions by users. You can embed the programming environment in or?plug into? an existing software development environment or provide it on its own. An syntax can be specified using source code statements, XML or SQL database definitions. The platform uses an event-based environment in which events that modify application data containing specified sought values/information are recognized and processed. You can define complex events using complex expressions. Actions can also be defined using scripts, homegrown executables and APIs. There are many ways to use the LBX platform.
Another advantage is the extensive range of paste commands that allow you to past LBX data into either data entry fields, snapshots, or one or several video stream frames. You can access and paste data from queue 22, history 30, statistics 14, and 16; atomic terms, map terms, WDRTerm data, AppTerm data, any term or construct from the LBX BNF grammar. Data can describe current, past or futur LBX data. Averages of MS or LBX. Data derived from MSs within the area (e.g. Nearby; and data received, sent or processed at the MS. Before finalizing the paste action, the user can adjust the appearance of the paste data (font, size and color, or any other characteristic).
“Another advantage is the provision of?plug in? Application support allows an application to be easily integrated into the LBX framework and architecture through Prefix Registry Records 5300. Application data and executable interfaces can be plugged in. Charter processing has access to application data for configurable and conditional event-based charter processing. Various ?plug-in? Various plug-in? systems and methods are described. The LBX platform integrates well with MS applications of any variety to create a cohesive architecture.
Another advantage is the tight coupling/integration of LBX processing configurations and processing into a program environment for a WPL within the context of a rich PL. LBX processing may be a?plug in? To integrate LBX processing into PPLs or to provide rich WPLs, it can be a?plug-in? A variety of methods and systems are described to provide a complete LBX platform.
It is a benefit to facilitate the creation of charters that are appropriate for a specific MS application. A special context is defined for each application, and candidate charters (or portions thereof) are presented to the user. These are derived from the specific terms and the atomic operands for that particular application context. Pre-made charters and charter portions are available to minimize the effort required for creating charters that fit a specific application context. After being presented with suggestions, users can choose, or select and?tweak! to a desired charter configuration. You can also set privileges in the context of the selected charters or application.
It is a benefit for automatically comparing MS profile information for matches to trigger conditional actions for charters. Data can be configured by users and sent to MSs for automatic charter processing. MSs can be automated with social interaction to other MSs, so MS users are notified of MS users in their vicinity who might be interested in a variety of applications.
It is a benefit for sending application data field to peers MSs in your vicinity, receiving them from the peer MSs, and transmitting them to data processing system in the nearby in a peer-to-peer manner. This allows for interoperability between a variety of applications and automated trigger processing. MSs can communicate wirelessly and directly with one another as peers. Peer data processing systems share application data fields (e.g. MSs are preferred to be available as additional AppTerm data at a MS (see below). The user can control which fields of the application data are disabled or enabled. Privileges between MSs can be used to enforce the desired processing effects on MSs that send or receive data.
Another advantage is that MSs can access a wide range of location-based enhanced applications without the need for a service. A service is not required for geo-fence alerts and proactive content delivery. No. No. Alert processing, geo-fences, and content are maintained at a MS to a) be processed at the MS when interfacing directly with peers MSs; and, b) be shared with peers MSs to be processed at peer MSs. It is possible to deliver content faster and provide alerts because the processing happens at the MSs, without any interoperability with any’middleman’. service.”
“Another advantage lies in the multi-threaded, wireless multi-wave and multifrequency multi-channel capability of a disclosed MS for RFID/RDS integration. The LBX framework, as described below, is well suited for RFID and RDS interfaces.
“Another advantage is that the MS can automatically or upon request analyze a picture or video stream frame for the purpose of more confidently determining an MS location.” To drive the desired processing, user configurations can be used.”
“Another benefit is the ability to manage and maintain statistics and historical information in a MS. There are many options for when, where and how to save this information.
“An additional advantage is to provide Sudden Proximal Users Interfaces (SPUIs), at a MS, when detecting other data processors in the vicinity (e.g. Another MS, an RFID device, any data processing system that emulates a MS, and any other data processor system. SPUI is a GUI that notifies a MS user when a remote data processing device of interest is within the vicinity. It is determined by configured?in-the vicinity? conditions. The following configurations can trigger the SPUI at the MS: charter configurations (AppTerm trigger configurations), RFID trigger configurations, and application term (AppTerm). SPUI processing can be automated using many applications to save MS users from repetitive interactions with MS user interfaces for common tasks such as device and appliance interfaces. Automated authentication is possible. SPUIs can also save data from previous executions to default data in a subsequent operation. This prevents MS users from having to re-enter data that they have already entered. Many applications can be used within the SPUI framework. Some of these are listed below.
“Another benefit is the user’s ability to request/transmit outbound information manually with options for customizing such as a WDR or derivative of a WDR. A subset of a WDR. User-configured data sets. Customized data sets. A WDR, or derivative/subset thereof, may be requested to be sent. The WDR can be first searched at the MS using user-specified search criteria. It can then be transmitted outbound according the user-specified transmission criteria.
It is a benefit to offer a task monitor/trace interface that allows you to examine MS task status for past and current system states. Based on task status information, the task monitor interface allows for easy creation of contextual charters.
It is a benefit to provide generic application record sorting, based on: MS location, whereabouts a particular MS or other WDR search criteria, for sorting WDRs at the MS where the sort was requested.
“Another benefit is the provision of one or more nearby monitors to indicate MSs of concern that are near you. Multi-threaded MS allows for multiple nearby monitors. An MS user can set criteria/conditions (i.e. Expression) to be used by a nearby monitor to compare WDR information received at the MS. The result of the expression (True/False), determines whether the MS that generated the WDR should be monitored within the specific vicinity monitor. An asynchronous or polling event (e.g. Design may also be used, such as the WDRs received.
Another advantage is automatic inventory management processing for inventory objects that are within a MS’s reach at any given moment. An MS user can track an order, count the stock and track the location of specific items. An MS user can set payment information to automate order processing. Inventory items can be enabled to manage inventory in conjunction with a data processing system (e.g. (RFID tag, affixed/integrated MS, etc). An MS user can either manually place an order using the automatically calculated inventory count information or schedule the order for automatic ordering (e.g. You can use a calendar entry. You can order inventory items individually or in groups, such as as part of a group hierarchy. The typical uses of inventory items are to manage the daily life of MS users: products in the kitchen pantry, fridge, freezer, closets, offices, bathrooms, laundry rooms, office supply closets, and other areas of a MS user?s home, office, or place of work.
Another advantage is that MS users can easily map privileges and charters between identities. It could be time-consuming to find out which privileges, grants, and charters are granted to each MS user and then grant those rights to another MS user. This task can be time-consuming and error-prone. The resource mapper functionality allows all rights (e.g. Resource mapper functionality is provided that allows all rights (e.g. privileges) to be assigned to another identifier in one operation. You can also remove the same rights in a single operation. MS users have the ability to grant privileges or charters to an identity (e.g. You can then group, and assign or remove all of them in one operation to other identifiers.
Cross-application addressing is another advantage that allows different applications to be linked. This means that features and contexts from one application can automatically be applied to affect those of another. The contexts of an application’s identifiers can be correlated with another form. An example: an email address of a recipient is correlated with the phone number for the same MS. This allows the user to immediately see all the emails that are associated with a particular person during an active phone conversation. Correlation occurs without the need to know any addressing details. You can use multiple identifier forms to correlate with a single MS, depending on the application.
The accompanying drawings provide details on the additional features and benefits of the disclosure as well as the structure, operation, and operation of different embodiments. Similar reference numbers in the drawings generally refer to identical, functionally comparable, or structurally similar elements. The leftmost digit (s) of the reference number indicates the drawing where the element appears for the first time. However, reference numbers 1 through 99 can be found on the first four drawings in FIGS. FIG. 1A through 1D and FIG. 1F. 1F. Dashed outlines (e.g. process blocks, data records fields) can be used in drawings to highlight or indicate optional embodiments depending on MS performance considerations. The discussions, drawings, and materials contained herein are not intended to limit any particular embodiment. This is the intended broadest interpretation. Other embodiments that achieve the same functionality fall within the scope and spirit of this disclosure. Information is presented as an example. Many embodiments are possible without departing from this disclosure’s spirit and scope.
The present disclosure will be described with reference to the details of the drawings. To focus on the main aspects of the disclosure, flowcharts will not include obvious errors. 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. In flowchart blocks, a semicolon can be used to separate multiple processing blocks within one physical block. This allows for simpler flowcharts that use fewer blocks. Multiple processing blocks can be placed in one block of the diagram. Processing flowcharts should be understood in the most general sense possible. This is not to limit the functionality of the flowchart. Field validation in flowcharts is preferred to check for SQL injection attacks and communications protocol sniff attacks, preventing of MS addresses being spoof, syntactical correctness and semantics errors, and preventing of MS addresses being spoof. The disclosed user interface processing and/or screenshots can also be used as preferred embodiment examples. However, they are not limited to the scope and spirit of this disclosure. Alternate user interfaces may be used (since this disclosure does not limit) but will use the same mechanisms. However, they could use different mechanisms and still remain within the scope of this disclosure.
“Locional terms like whereabouts, location and position, area, destination and perimeter, radius, geofence and situational location or any other related two- or three-dimensional locational term used herein for described position(s), locations and/or whereabouts are to be understood in the broadest possible sense. One example of a location field 1100c is an area. On earth), a point (e.g. on earth), a point (e.g. Another example is that a radius can define a sphere within space rather than a circle within a plane. A planet field may form part of the location in some embodiments (e.g. Earth, Mars, etc. are all part of field 1100c. Other location information (e.g. It is also possible to include latitude and longitude for Mars in field 1100 c. Some embodiments may include elevations or altitudes from known locatable points, distances from the origin(s), etc. It can be used to indicate where a point in three-dimensional space or sphere, solid, is located. The same point can also be used to provide mathematical references to other points in the solid area/region. Further descriptions of angles, pitches and rotations from any reference point may be provided. A three-dimensional area/region can be conical, cubical, spherical, pyramidal, or irregular shape. It can also include any other shape that can be manipulated using a three-dimensional graphic interface or mathematical model descriptions. A MS can occupy areas/regions in space, or pass through (e.g. A MS can be used to occupy a space or pass through (e.g., by a traveler), or refer to configuration by a MS. Three-dimensional embodiments determine nearby/nearness using three-dimensional information. For example, a spherical circle around one MS intersects a radius around another MS. Nearby/nearness in a two-dimensional embodiment is determined using two-dimensional information. For example, a circle around one MS intersects a circle around another MS. A point can be defined as a point on an x-y?z plane, a position in polar coordinates or something similar, such as the center of a globe (e.g. Earth), or the Sun, any origin in the Universe or any other source for clearly locating three-dimensional locations, positions, or whereabouts within space. Elevation (e.g. Elevation (e.g. To define a region of space, you can connect x-y/z coordinates together to create a three-dimensional space. You can represent a location (field 1110 c) in many ways without violating the spirit or scope of this disclosure. MSs can be carried by users and travel through three-dimensional areas/regions in three dimensions. They also travel under the water through three-dimensional regions in three dimensions.
“Several embodiments of communication between MSs or an MS with service(s) will share channels (e.g. Depending on the time in effect, frequencies can be used to communicate. To share a channel, you will need to have a processable signature that can be used to identify transmissions and carry data. Depending on the time in effect, there will be different ways of communicating between MSs or service(s). Which embodiments are preferred will depend on the number of channels that can simultaneously be listened to and/or transmitted by a data processing device. Preference will also depend on the number of channels that can be used simultaneously. This disclosure does not include unnecessary details in the different communication channel embodiments to avoid confusing new material. MSs can communicate with each other in peer-to-peer fashion, regardless of which channel is used within the scope and spirit.
“Novel features described herein do not have to be presented as all or none. Some features can be used in a single MS embodiment, while others may include a subset of functionality and features in other embodiments.
“Location Based eXchanges Architecture (LBX).”
“FIG. “FIG. MS 2 also includes processing behavior referred as LBX Character 4 or Other Character 32. According to the disclosure, LBX Character 4 is processing behavior that causes MS 2 to assume the character of a Location Based Exchange MS (LBX). Other Character 32 is processing behavior that causes MS to assume the character of a prior art MS. This behavior is well-known to those who are skilled in the art. Other character 32 gives MS users a limited range of configuration and functionality. In certain embodiments, LBX component 4 may use other character 32 components 34-36, and 38. Other components of character 32 may or may not make use of LBX component 4 components 6 through 30.”
“LBX character 4 preferably contains at least Peer Interaction Processing code 6, Peer Interaction Processing data 8 and Peer Interaction Processing data 8 respectively. Self management processing code 18 is also preferred. WDR queue 22. Send queue 24. Receive queue 26. Service informant code 28. LBX history 30. Peer interaction processing code 6 includes executable code in hardware, firmware, and software for carrying out the LBX processing logic described herein when interacting with another MS. Peer interaction processing data (PIP data 8) includes data that is stored in any type of memory MS 2 has, including flash memory, hardware memory, hard drive memory, and any other available memory. PIP data 8 includes intelligence data to drive the LBX processing logic in the present disclosure when interfacing with other MSs. Self management code 18 is executable code that can be used in firmware, software, or hardware to carry out the local user interface LBX processing logic. Self management processing data 20 includes intelligence data to drive processing logic as disclosed for locally maintained LBX functions. WDR queue 22 includes Whereabouts Data Records 1100 and is a First In-First Out (FIFO) queue for housekeeping purposes to prune the queue to a reasonable trailing record of inserted entries. remove stale entries). WDR queue 22 has the advantage of queue entry retrieval processing that is similar to Standard Query Language querying. In this case, one or more entries may be retrieved by querying any data field(s), WDR 1100, and returning lists of entries sorted by ascending/descending key on any key field.
“All disclosed queues (e.g. 22, 24, 26, 1980, 1990 (See FIG. 22, 24, 26, 1980, 1990 (See FIG. Queues have an implicit semaphore that allows for synchronous access to queue data within a multi-threaded environment. This prevents data corruption and misuse. These queue interfaces are common in many operating systems. If an MS operating system environment does not provide an implicit semaphore-protected queue scheme, then queue accesses shown in the disclosure flowcharts will have to be understood as having a prior request to a queue assigned semaphore locking before queue access and a subsequent release of the lock after access. Other operating systems may employ methods to achieve thread-safe synchronization functionality. Queue functionality can be achieved with lists, arrays and databases (e.g. SQL) or other methods, without departing from this article’s spirit and scope.
Queue 22 alternative embodiments may have multiple WDR queues that segregate WDRs 1100 according to field(s), in order to facilitate timely processing. WDR queue 22 could contain at least two (2) separate queues. One for MS 2 whereabouts and one for MS 3 whereabouts. In some cases, WDR queue 22 could be one instance WDR 1100 that contains the most recent MS 2 whereabouts. MS 2 applications may use another queue 22 to maintain WDRs from distant MSs. For MS 2 whereabouts, at least one entry must be maintained to WDR Queue 22 at all times.”
“Send queue 24 (Transmit(Tx) queue), is used to transmit communications data to a peer MS in the immediate vicinity (e.g. Nearby as indicated by the MS 2’s maximum range 1306 Receiving queue 26 (Receive(Rx) queue), is used to receive communications data from peers MSs in the area (e.g. Nearby as indicated by the MS 2’s maximum range 1306 The MS 2 may indicate that Queues 24 & 26 have a plurality queues to segregate data. This facilitates interfacing with the queues, particularly when different types of queue entries and/or sizes are used. In multi-threaded systems, a queue interface is used to send/receive data to/from MS. However, alternative embodiments allow data to be sent/received directly from the processing thread described herein. Queues 22, 24 and/or 26, may be implemented as a data form or SQL database. They are maintained at MS 2 by persistent storage, memory or any other storage. Some embodiments do not require queues 24, 26 or 32, as other characters 32 already have the resources to perform some LBX 4 processing.
“Queue embodiments can contain fixed length records or varying length record, pointers for fixed length records, pointers towards fixed length records or pointers toward varying length record. Pointers can be used if dynamically allocated to record storage upon insertions. They may then be released after record use, discards, or retrievals.
As those who are skilled in the art know, when a thread sends data to a queue 24, in anticipation of a reply, there is correlation data in that data. This data is sought in a response from a thread at queue 26, so the sent data can be correlated with the received data. A preferred embodiment of correlation uses a round-robin sequence number that is placed in the data to be sent along with an unique MS ID (MS ID). Correlation can also be encrypted if data is not encrypted in communications. The unique MS ID (MS identifier) can be used to help identify which (e.g. Correlation helps to identify the data that caused the MS to respond. The data received from a queue 26 responder is used for correlation processing (e.g. Field 1100 m is used to correlate the received and sent data. Preferably, the sequence number is incremented every time before being used to ensure a unique number. Otherwise, it might be difficult to determine which data received is a reply to which data was sent. This is especially true when multiple data packets are sent in a matter of seconds. The sequence number is increased to a maximum value, such as 2**32?1. When the sequence number reaches a maximum value (e.g. 2**32?1) it is round-robinned and incremented again. This ensures that data are properly correlated between responders and MS over time. Other correlation schemes are available (e.g. Other correlation schemes (e.g., signatures, random numbers generation, checksum counting and bit patterns) can be used to achieve this functionality. Correlation can be used to correlate a reply with a request if send and receive queues of Other Character 32 is used. “Send with receipt”
“It may be a good idea to conceal the MSID when sending it wirelessly. The MS ID in this embodiment is a reliable and easily recognizable derivative (e.g. A pseudo MSID that is able to be detected by communications traffic. The pseudo MS ID can conceal the true MSID. This would hide the true MSID from hackers who could sniff wireless protocols. For simplicity, the derivative can be recognized by the MS and can be used to hide the true MS ID from hackers sniffing wireless protocol. Phone number or serial number, in particular when anticipating traffic in response. However, it can still be useful for directing replies back to the origin MS (with the pseudo MSID (e.g. correlation)). MS could know which correlation was anticipated in a response and save it to local storage until it is used (i.e. If the matching response is not correlated, or becomes stale, then a MS would know which correlation is anticipated in a response and save it to local storage. A correlation response queue, such as CR queue 1990, can be used in another embodiment to correlate responses with requests that have different correlations for pseudo MSIDs. All embodiments of the disclosure require that the MS ID (or pseudo MSID) be used to target communications traffic to the MS.
“Service informant code 28” is executable code in hardware, firmware, and software that allows for the execution of informing a supervisory services. Although the present disclosure doesn’t require a connected Web service, there are features that allow a service to be kept informed about MS LBX activities. The service informant code 28 is able to communicate any data 8, 22, 24, 26, 30, 32, 36, 38 or any other data processed by MS 2.
“LBX History 30 contains historical data that is useful in maintaining MS 2 and may be useful for informing a supervisory agency through service informant code 28, LBX History 30 should have an associated thread for processing to keep it pruned to the satisfaction MS 2 users (e.g. The user prefers to keep the last 15 days of specific history data and 30 days of other specified history data, respectively. A suitable interface to MS 2 allows users to browse, modify, delete, or add to LBX History 30 in the manner that is applicable to the processing described herein. To send an outbound email or SMS message, or any other outbound communication, the service informant code 28 can be used.
“PIP data 8 should include at least permissions 10, statistics 14, charters 12, and a service directory 16. Permissions 10 allow other MS 2 users to interact in the same way that the MS 2 user would like. Permissions 10 grant permissions from the MS 2 user to other MS 2 users. Permissions 10 may also, or alternatively contain permissions granted by other MS users to the MS 2U. Permissions can only be granted to MS 2 users. Charter 12 provides LBX behavior conditional expressions that describe how MSs should interact. The MS 2 user can configure charters 12 for other MS users. Charters 12 can be configured by MS 2 users to configure charters 12. Permissions are required for some charter expressions. Statistics 14 are kept at MS 2 to reflect peer (MS-to-MS) interactions that took place at MS 2. Statistics 14 may also, or alternatively reflect peer (MS to MS) to peer interactions of interest that occurred at MS 2. A service may be informed by the 28th service informant code. Service directory 16 contains routing entries that describe how MS 2 will locate a requested service or how another MS can access MS 2 to find it.
“In certain embodiments, any code (e.g. 6, 18, 28, 34 and 38 can access, modify, alter or dispose of any data (e.g. 8, 20, 22, 24, 26, 30, 38, 36, 38) for any other MS 2 component. Other embodiments might choose to separate the processing of LBX characters 4 and 32. Rectangular component boundaries can be used to represent logical components and they do not need to define who has access to which. MS (also MSs), references are discussed herein in context of the new and useful features.
“FIG. “FIG. LBX MSs can be considered peers for their functionality and locational features. MS 2 can communicate with MSs 2 without the need for a service. FIG. FIG. 1B shows a wireless network 40 consisting of five (5) MSs. Each MS can communicate directly with other MSs in the area (e.g. Nearby as indicated by the maximum range 1306). Communications are wireless broadcast datagrams with limited reliability and recognizable packet identifiers in a preferred embodiment. Another embodiment of wireless communications is reliable transport protocols such as TCP/IP that are carried out by MSs. Other embodiments include new data, such as the usual communications data associated to other character 32. Communications Key 1304 is used in transmissions to be recognized by MSs in the area. As an example, LBX data can be added to a protocol when an MS communicates conventionally. This allows other MSs within the area to access the data and detect it. This is advantageous because MSs can use wireless communications to perform conventional behavior. Additional information is added (e.g. Communications Key 1304 to existing communications
“Regardless of the embodiment, MS 2 can communicate with any other MSs in its vicinity using the methods described below. The communication path 42 between two MSs can be bidirectional or at least unidirectional depending on the embodiment. Although the bidirectional path 42 can use one communication method in one direction, and another in the other, they can still communicate with each other. A path 42 is composed of two unidirectional communication paths. There are N*(N??1) unidirectional routes for N MSs within a network 40. A network of 10 MSs would result in 90 (i.e. 10*9 one-way paths for communications between all 10 MSs to enable them to communicate with each other. To minimize the number MS threads listening to different channels, it is preferable to share the same signaling channels. Flowcharts can process at extremely high speeds, especially for communications processing. The MSs communicate wirelessly with each other. However, path 42 embodiments can involve any number intermediary systems or communication methods. For example, see FIG. 1E.”
Summary for “System and Method for Location Based Exchange Network”
The internet is bursting with new service offerings. Google.com and iTunes.com are examples of websites that can provide valuable services to a wide audience via the internet. There are many types of web services that can be used for different functions. The advantages of using a service to act as an intermediary between clients, users, systems and services include centralized processing and centralized maintenance of data. This includes an all-knowing database that can be used to determine the scope of services offered, a supervisory point for control, giving an administrator access to the data maintained by web service users, as well other benefits associated with central control. These advantages are similar to those offered by the traditional mainframe computer to clients. The mainframe controls all resources, data and processing and provides central control over all users and systems (clients). As computers became cheaper, adequate processing power was made available to more distributed systems such as Open Systems (i.e. The mainframe no longer needed to be used for most computing tasks. High-powered mobile devices, as well as other mobile data processing platforms, can provide adequate processing power. Technology is enabling greater processing power and data storage in a smaller device. Open Systems took a lot of the computing load off mainframe computers. Mobile data processing systems can also offload tasks normally performed by web services. Mobile data processing systems have become more powerful and there’s no need to provide a service for middleman interactions between them.
While a central service can have its benefits, it also has its drawbacks. The service acts as a clearinghouse for all transactions in web services. The web service can be a bottleneck regardless of how many threads are processed across hardware and processor platforms. This can lead to poor performance and slow response times. It can also cause large amounts of data that must remain accessible for all users and/or systems. Even the largest web services are subject to overhead and poor performance. Web service responses will not be quick enough. Archive backups are necessary to allow for recovery in case of disaster. The service stores all data required to run its operations. Archive storage, processing power and planning are all necessary. To accommodate millions of users or systems that connect to the service, a large and expensive data center is required. This service requires a lot of overhead. It is very expensive to provide data center processing power, data bandwidth, speed, and data transmission bandwidth, as well as infrastructure entities and other performance considerations. Real estate costs, electricity and cooling bills, maintenance of the system, staff to manage a business, etc. are all included in these costs. It is necessary to find a way to reduce large data center expenses while ensuring that features are delivered as promised. As users demand more functionality and features on their mobile data processing systems, it is likely that processing will move closer to the device in order to maximize performance and reduce infrastructure costs.
U.S. Pat. Nos. 6,456,234; 6,731,238; 7,187,997 (Johnson). In U.S. PTO Publication 2006/0022048 (Johnson), anonymous location-based services were disclosed. The Johnson patents and the published application function in the same way as other web services. Clients who connect to the service are able to benefit from it by having some connectivity. U.S. U.S. This may not be a problem for a company with large web services resources but it could be a concern for smaller companies. It is necessary to enable location-dependent functionality and functionality without the need for a service.
As internet services grow, users are more concerned about their privacy. By its very nature, a service typically stores information about a user in a central service database. The service can store the user’s credentials, preferences, customizations, billing information and surfing habits. Access may be granted to company insiders and outside attackers. People are concerned about ensuring that personal information is not stored in a central database. This could lead to security breaches. Services that are location-based are more concerning, especially if the users’ locations are known to the centralized service. It is necessary to provide a system and method that allows users to feel more comfortable knowing their personal information is less at risk.
“It is reasonable to require mobile data processing system intelligence, such as knowing their locations and those of nearby mobile data processing units. Mobile data processing systems are able to handle many of their application requirements themselves without relying on remote services. Mobile data processing systems do not require a service provider to provide useful functionality or features that are location dependent. This is just like two employees in a company should not have to talk to one another. It should not be the end for social interaction implemented locally to mobile data processing systems. Rather, it should be the beginning point for many useful distributed local applications that don’t require a service.
“Different users have different types of Mobile Data Processing Systems (MSs), also known as mobile devices, such as laptops, tablet computers, Personal Computers, Personal Digital Assistants, (PDAs), personal computers, Personal Navigational Devices, (PNDs), iPhones (iPhone trademarked by Apple, Inc.), and various mobile data processing system. MSs can move freely and are unpredictable (i.e. They can be moved wherever and whenever they want. Mobile data processing systems (MSs), many of which are not capable of automatically being located, or do not use a service to automatically locate them. Conventional methods use direct relative stationary references like antennas, satellites, and so on. to locate MSs. Stationary references can be costly to deploy and are susceptible to becoming obsolete as new technologies become available. Stationary references are limited in their ability to locate MSs.
The United States E911 mandate to cellular devices defines requirements for automatic location of a Mobile Data Processing System (MS), such as a cell telephone. However, it does not promote real-time location and tracking, nor does it outline architecture for exploiting Location Based Services. Location Based Services (LBS) and other location-dependent features and functionality are some of the most promising technologies today. Automatically locating every Mobile Data Processing System (MS), is an evolutionary trend. To speed up the process of automatically locating each MS, a method is required. This goal is not possible with prior art technologies like GPS (Global Positioning System), radiowave triangulation, being within range of a known location sensor, and the like. Complex system infrastructures or additional hardware costs for the MSs make such ventures expensive and time-constrained due to schedules and costs associated with engineering, construction and deployment.
“A method is required to enable users to access location dependent features and functionality by having their mobile locations known. This is regardless of whether their MS is equipped for being found. A MS can also be provided with modern location-dependent features and functionality without the need for a connected service.
LBS (Location Based Services), a term that has grown in popularity as MSs include various locations capability, is “LBS” “Services” is a term that refers to services. The term “Services” is used in this terminology to refer to location-based functionality and features that involve interaction between two or more people. This disclosure introduces a new terminology and system called Location Based eXchanges. 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? For the plural term,?Location Based Services’. LBX refers to leveraging the distributed nature and connectivity between MSs instead of leveraging a centralized service nature. LBS and LBX can blur the line between them, as they provide similar or even identical features and functionality. In some cases, strengths from both could be combined. LBX differs from LBS in that it relies less on centralized services and more on distributed interactions among MSs. This is the underlying architectural shift. LBX provides server-free, server-less functionality and location-dependent features.
“Disclosed are many aspects of LBX. They start with the requirement that each MS must know their location at some time. LBX can be enabled when an MS knows whereabouts. It is therefore important to make sure that as many MSs as possible know whereabouts. LBX allows distributed locational applications that allow multiple MSs to know where they are. A server is not needed to facilitate social interactions between MSs. MSs can interact with each other as peers. LBX can be disclosed for peer-to-peer interactions, peer interaction for routing services and peer to peers for delivering distributed service. Peer to peer interactions are also available for location dependent features and functionality (e.g. A first mobile data processing device sends directly (e.g. Wirelessly) to another mobile data processing device without the need for an intermediary data processing system. An LBX-enabled MS can be described as an lbxPhone.
“It is advantageous to not have a centralized service that governs functionality and features based on location among MSs. A centralized service is not necessary to prevent performance problems, infrastructure costs, or solve many of the above issues. A user’s information can not be kept in one place by a centralized service. LBS stores personal data that users can access. This poses a security risk. This increases the chance that data disasters will affect multiple users. LBX distributes data across the participating systems to ensure that a disaster affecting one person does not affect another.
It is possible to enable useful distributed applications without having to have a service and without users or systems needing to register with the service. In preferred embodiments, MSs are considered peers rather than clients to a single service (e.g. “Internet connected web service.”
It is possible to locate as many MSs in a wireless network as possible, without any additional deployment costs for the MSs or network. The conventional locating capabilities include GPS (Global Positioning System), which uses stationary orbiting satellites. There are also improved versions of GPS such as AGPS (Adjusted GPS), and DGPS(Differential GPS) that use stationary-located ground stations. Wireless communications to fixed cell tower base stations can be used. TDOA (Time Difference of arrival) triangulation with stationary antennas. Also, presence detection within the vicinity of a stationary antenna, presence detection at a stationary wired connectivity location, and presence detection at a stationary antenna. Indirectly Located Mobile Data Processing Systems (ILMs) are automatically located by automatically detecting the locations of Directly Located Mobile Data Processing Systems (DLMs) or automatically detecting other ILMs. ILMs have the option to participate in the same LBS or LBX as a DLM (Directly Located Mobile Data Processing System). The conventional locating capability described above is used to locate DLMs. DLMs can be used to automatically locate ILMs regardless of their current location. For example, DLMs and ILMs are highly mobile when used by users. There are many novel ways to locate ILMs automatically. These include triangulating an ILM (Indirectly Located Mobile Data Processing System) location using a plurality ILMs; detecting the ILM’s presence within the vicinity at least one ILM; triangulating the ILM Location using a plurality ILMs; detecting the ILM’s existence within the vicinity at least one ILM; triangulating the ILM Location using a mixed set DLM(s), ILM(s); determining the ILMs/or ILMs and/or ILMs
“MSs can be automatically located by using any other means than direct conventional methods. The conventional locating ability (i.e. The conventional locating capability (i.e., the ability to locate objects using standard methods) is also known as direct methods. Direct methods can be described as conventional methods. However, not all direct methods can be called them that. Below are some new direct techniques. This document contains a system and method for instantly bringing automatic location detection (whether or not the MS is capable of being located directly) to all MSs around the globe. MSs without the ability to be directly located can be located using the automatically detected locations MSs that are directly situated. This is known as being indirect located. A Directly Located Mobile Data Processing System (DLM) is an MS that is located directly. MSs that are located directly are referred to hereinafter as Directly Located Mobile Data Processing Systems (DLMs) for a plural acronym. MSs which are not capable of being located directly can be located by using automatically detected locations of MSs already located. An MS that is located indirectly is hereinafter referred as an Indirectly Located Mobile Data Processing System (ILM). MSs that are located indirectly are hereinafter referred as Indirectly Located Mobile Data Processing Systems (ILMs). These are the ways you can locate a DLM:
“In one case, multiple MSs’ mobile locations are automatically detected by their local GPS chips. Each one is called a DLM. A radio wave is used to triangulate the mobile location of a non-locatable MS. It can be connected with three (3) GPS-equipped DLMs. After its location is determined relative to the DLMs, the MS becomes an ILM. DLMs or other ILMs can automatically locate ILMs. These are the ways you can locate an ILM:
“Locating functionality can leverage GPS functionality. This includes but is not limited to GPS (Adjusted GPS), GPS (Differential GPS), and any other improved GPS embodiment that achieves higher accuracy using known locations such as ground-based reference locations. Nextel is a trademark for Sprint/Nextel. Triangulated locating functionality can include triangulated location of the MS. This could be done by using a class radio frequency (RF) wave spectrum (cellular), WiFi (some WiFi embodiments are referred to as WIMax), etc. It may also use measurements from multiple wave spectrums for a single location determination depending on the available communications interface(s). 70). An MS’s location may be determined using any number of wave spectrum classes (cellular, WiFi and bluetooth). The term WiFi? This disclosure uses the term WiFi? In-range proximity detection may be used to detect the presence of the MS. Triangulated locating may also use wave forms such as microwaves, infrared waves spectrum relative infrared sensor, visible lightwave spectrum relative to visible lightwave sensors, ultraviolet waves spectrum relative ultraviolet wave sensor, Xray wave spectrum relator Xray wave sensor, gamma radiation wave spectrum relativity gamma-ray sensors, longwave spectrum (below am) relative longwave sensors. There are many methods that can automatically locate a MS, such as radio wave triangulation, GPS, in range proximity detection and longwave spectrum (below AM) relative longwave sensors. While radio wave triangulation, GPS and in range proximity detection are the most common methods of automatically locating a MS (e.g.
“Kubler et.al (U.S. PTO publication 2004/0264442, 2004,/0246940 and 2004/0228330,2004/0151151) described methods for detecting mobile entities when they are within the range of a sensor. Kubler and colleagues did not know the exact location of the MS. Therefore, an estimate of the MS’s area is sufficient to achieve the intended functionality. Kubler and colleagues tend to have a low confidence value (i.e. Not confident, with lower values for long-range sensors and higher for short-range sensors.
GPS and the many methods to improve GPS accuracy have led to many successful systems that locate MSs with high accuracy. Triangulation is a reliable method to locate MSs. This disclosure is associated with GPS and triangulating position methods tends be high (i.e. confident). DLMs should use the most accurate method possible to ensure relative ILMs are accurately located. All DLMs do not need to use the exact same location methods. You can locate an ILM relative to other DLMs or ILMs that use different locating methods.
“Another benefit is that MSs can be generically located using a variety and combination of technologies. MSs can be located automatically using conventional methods. This accuracy is based on the location of other MSs. Indirect methods can also be used to locate MSs. It is advantageous to indirect locate MSs that are located in different locations. One DLM could be automatically located by GPS. Cell tower triangulation may also be used to locate another DLM. Another DLM can be located automatically using within range proximity. The ILM may be located in a single place or at different locations as time passes. An algorithm for triangulation may be used to determine the location of an ILM automatically relative to the three DLMs. However, each DLM has a different location method. A preferred embodiment uses industry standard IEEE 802.11 WiFi to triangulate an ILM relative to a number of DLMs (e.g. TDOA is one embodiment. This standard is popular among the more compute-oriented MSs. You can use any of the 802.11 waveforms, such as 802.11a or 802.11b, or any similar class of wave spectrum, between multiple ILMs. 802.x is a general term that refers to all 802. whatever variants.
“Another benefit is to use existing market communications hardware, communications interfaces and communications methods and locations methods wherever possible to locate an MS relative one of more MSs. Although 802.x is the most common RF wave form for WiFi communications, there are other options (e.g. cell phone to cell tower communications. Any wave spectrum that can carry data is applicable herein. Any protocol may be used in the embodiments of these disclosures, e.g. TDMA, CDMA, H.323, SIP, 2G, 3G, ip phone, digital, analog, spectrum frequency, etc).”
“Another advantage is the support for heterogeneous locatable device. Different people prefer different types of devices, as explained above. A device can be fully automated with its location functionality by either remote or local automatic location detection. An ILM can also be found relative to a laptop, cell phone and a PDA (i.e. different device types).”
Another advantage is the inability to store large quantities of positioning data for a network MSs. It can be costly to store, back up, or recover positioning data that is used to determine the location of all devices. The preferred embodiment uses a distributed approach to determine locations of MSs, without having an all-knowing database. It is possible to determine the positions of MSs?on-the-fly? Without the need to store information in a master data base. There are ways to store a master or subset of a master database in configurable storage locations. One MS can store a subset of the master database.
“Another benefit is the use of existing location-equipped MSs to expand our network of locatable device by locating non equipped MSs relative to the location of the MSs that are equipped. The size of the MSs’ locatable network can be increased by MSs. LN-Expanse is the term used to describe the locatable network made up of MSs. Location-Network Expanse). LN-Expanse changes dynamically depending on the location of MSs at a given time. As users travel with their own MSs, LN-Expanse is defined by the MSs that they use to locate other MSs. An ILM requires location awareness relative to MSs (DLMs or ILMs).
A MS can interchangeably take on the role of an ILM or DLM while it travels. This is because MSs can adapt to the availability of location technologies. An MS might be equipped with DLM capability but be at a place where it is not possible to access the capability. In such situations, the DLM assumes the role of an ILM. The MS automatically assumes the role of DLM when it enters another location that can be used as a DLM. This is especially important in emergency situations. An accident occurs in the mountains that prevents GPS-equipped DLM capability from functioning. The MS assumes the role of an ILM automatically and is located in the vicinity of nearby MSs. This allows the hikers to communicate their location and use useful locational applications and features at his MS.
It is also advantageous that MS locations can be triangulated using any wave form (e.g. RF, microwaves, infrared, visible light, ultraviolet, X-ray, gamma ray). Gamma and X-ray applications are unique in that these waves can be harmful to humans for short periods of time. It is important to have the right to use such wave forms. Micro-machines can be used in medical applications to implant within the human body. These micro-machines may be outfitted as MSs. MSs can use wave spectrums that are available at the time they deploy to determine exact positions while traveling through a body.
It is also possible to use TDOA, AOA (Angle Of Arrival), or Missing Part Triangulation(MPT) to locate a MS. TDOA uses information about time to determine where the MS is located, such as distances between sides of a triangle. AOA uses angles to arrive to antennas to geometrially determine where a MS is by intersecting lines from antennas with detected angles. This document describes MPT as combining AOA and TDOA to locate a location. It is not necessary to use all AOA, or all TDOA. MPT can be used to locate MSs.
“Assisted Direct Location Technology (ADLT) is another option for locating MSs. ADLT can be described as the combination of direct (conventional), location capability and indirect location capability to determine the exact location of a MS.
“Another advantage is the ability to manually specify the location of a MS (a DLM). This manual location can be used to locate other MSs. An interface can be used to specify a DLM site. The interface may be remote or local to the DLM. Various manual specification methods are disclosed. Manual specification should be used with less mobile MSs or existing MSs like those that use dodgeball.com, a trademark of Google. The location, validation, and the way it changes as the MS moves, all affect the confidence value. If inaccuracies cannot be avoided, manual specification should limit the scope of an LN-expanse.
“Another benefit is that you can locate a MS using any combination of the methods above and any combinations or indirect location methods described.”
Another advantage is the ability to combine different locating technology for seamless operations when an MS travels. There are many ways to keep an MS updated about its location. It is crucial to keep an MS updated about its location in a timely fashion. This will ensure that LBX operates optimally and allow nearby MSs with locating technology to be located.
It is also a benefit for finding an MS using multiple location technologies on its travels and to using the best data from multiple locations technologies to determine a MS’ location. To ensure accuracy, reference location information is associated with confidence values. A DLM is often an ‘affirmifier?. An affirmifier is an MS that has its location information with high confidence and accuracy. It can be used as a reference for others MSs. An ILM can also serve as an affirmifier, provided that it is located in a location with high confidence. An MS (e.g. An MS (e.g. Pacifiers are MS that have location information about its whereabouts, but with low accuracy. It can be used to reference other ILMs but it cannot do so with a low level of accuracy.
It is another benefit for allowing user customization of confidence levels based on user experience. MS users can rely completely on MS system settings to set confidence values. Or they may “tweak” them. Location technology confidence values are used to account for experiences with specific location technologies encountered while traveling.
It is a benefit to combine the many locating technologies to avoid one type of technology dominating others, while still using the best features from each to determine the precise mobile location of MSs.
A data processing system that can be located to co-locate another data processing systems without being able to locate it is an additional advantage. A driver might have an older model car and a second data processing system that can be used to locate the vehicle. A cell phone belonging to the driver is also a first-data processing system. It can be used to automatically locate the vehicle. For the purpose of locating the second system, the location of the first processing system can be shared. The second data processor system is not automatically located. It is located relative to a plurality of data processing systems that are not located at the same place as the first. Data processing systems can automatically be located relative to at least one other data processing system that can be automatically found.
A LBX-enabled MS also includes a service informant component to keep a supervisory services informed. This prevents an MS operating in complete isolation and allows it to interact with other MSs within its immediate vicinity (e.g. Within the maximum range 1306, at any point in time, and to also participate when MSs are far apart. Although there are LBX that can be incorporated into an LBS model of the LBX model, a preferred embodiment prefers to use it. Multiple MS users may want to carpool to and fro a common destination. Even though information is not maintained at all MSs, the service informant component can provide timely updates to a supervisory services for route comparisons among MSs. Users may discover that they attend the same church and have similar work schedules. Coworkers might find out they live near each other and have identical work hours. To facilitate new LBX applications, the service informant component keeps a service updated on MS location. You can configure the service informant to communicate directly with another MS, to communicate to a data processing service through a propagateable service, or to invoke a?plugin? Home-grown interface: alerting the MS user by a specific alert or invoking an Atomic Command used for charter processing
It is an additional advantage to leverage the large amount of MS WiFi/WiMax deployments underway in the United States. The availability of WiFi/WiMax in greater numbers increases the performance of peer-to-peer types and functionality.
It is also a benefit to avoid established connections interfering with the successful triangulation of a MS location. The MS can be found by interacting with various wave spectrum signals as it roams the world. Broadcast signaling provides the location information necessary to automatically locate the MS.
“Network Time Protocol (NTP), which eliminates bidirectional communication in determining Time of Arrival and Time Difference Of Arrival measurements, is another advantage. TDOA as described in the disclosure refers to both TOA (Time of Arrival) and TDOA. NTP allows for a single, unidirectional transmission to carry all the data necessary to determine TDOA. This is provided that the sending and receiving data processing systems are NTP synchronized with an appropriate granulation of times.
“An additional advantage is the ability to make available to remote peer MSs certain MS Operating System resources such as memory and storage, semaphores or application data, depending on permissions. One MS can access the operating system resources of another MS. This is useful for charter processing, for instance. A network of peers MSs can achieve semaphore-controlled synchronization of processing without the need for a common server.
“It is an advantage to this disclosure to offer a superior alternative to server-based mobile technologies such U.S. Patent. Nos. 6,456,234 and 6,731,238 respectively; 7,187,997 and U.S. PTO Publication 2006.0022048 (Johnson). In order to enhance the user experience, it is a good idea to use both LBX and LBS technology within the same MS. In certain instances, the different technologies can be combined.
A further benefit is the ability to use existing “usual communications?” data transmissions can be used to carry new data that is not being processed by the existing MS processing but is observed by new MS Processing. This allows for processing of large geographic areas with location functions and features. Alternately, new data can also be transferred between systems to achieve the same functionality.
“It is a benefit herein in providing peer-to-peer service propagation. ILMs have the opportunity to take part in the same location-based services (LBS) as DLM(s). MSs may be able to access services that are not available to them. Any MS can share their accessible services to be accessible to other MSs, provided permissions are granted. An MS can, for example, get internet access from another MS with internet access nearby. Preferably, permissions are kept in a peer-to-peer manner before proper service sharing. Another embodiment specifies permissions and uses them at the time of sharing access to shared services. Services can be used as if they were being shared by the sharing user, or as if they are being shared by a new user. As MSs travel, routing paths can be dynamically reconfigured and transparently utilized. Hop counts change dynamically to ensure that MSs have access to the desired service with a minimum number of hops. The route communications depend on the location of the MS that needs the service and the minimal hops required to reach it through other MSs. Services can be transmitted from DLMs or DLMs directly to ILMs. ILMs and DLMs can also be used to propagate services.
“Services that are otherwise unavailable to the first MS (or MS user in the LNExpanse) become available through another MS that has access to the service. The connection may be made possible by multiple MSs (e.g. Hops) may be made from the first MS to last MS that publishes the service. MSs have the ability to access services from nearby MSs if they need them. The service directory is shared among MSs and propagated between them so that all the services in a LNExpanse can be accessed by any MS, regardless of whereabouts, ability, or inability to connect. To achieve the best performance, even for highly mobile MSs, a service route must be minimized. This means that there are fewer hops between MSs in order to reach a service.
It is another benefit for peer-to-peer permissions, authentication and access control. It is not required to maintain credentials and permissions between MSs. Permissions can be maintained locally by a MS. A centralized service model can lead to a large database when it comes to searching for permissions. Database size and performance were both a problem with permission searching and validation for U.S. PTO Publication 2006.0022048 (Johnson). It was costly to maintain who had permission for each permission granted. As described below, local permissions can be kept. This is because the owner of permissions is the MS user. Permission searching is also very fast as the MS needs to only search its local data for permissions applicable to its MS.
Another advantage is the ability to give a near, or nearness status, using a peer-to-peer system and method rather than intelligence kept in a central database for all MSs. It is very costly to maintain a large database that contains all locations of all MSs. This disclosure eliminates this overhead by using nearby detection methods of one MS to locate another MS. There are many controls that can be used to determine the generation of the nearby status. One aspect is that a MS can automatically call the MS nearby, connecting them to a conversation and allowing the user to not have to initiate the call. Locally maintained configurations control functionality when MSs become nearby or depart from being near. In a LBX fashion, queries, alerts, and status are sent to nearby MSs.
It is a further advantage for automatic call handling, call handling and call processing based upon the whereabouts or relative whereabouts a MS. Automatic call forwarding functionality can be affected by the nearness condition between two MSs.
Another advantage is peer-to-peer content delivery and local MS configuration. The service is not accessible from users’ computers. To enjoy content delivery from other MSs based on location, users can create local configurations. The content is delivered in a variety circumstances and for many different reasons. For nearby alerts, arrival and departure to geofenced areas and other predicated conditions, content that is local to an MS will be delivered asynchronously from other MSs. Although it might appear that there are LBS available to MS users, in reality there are LBX available to them.
“Another benefit is that a LBX-enabled MS can work in a peer-to-peer manner with data processing systems which control the environment. An example of this is when an automobile-equipped (or driver-owned) MS meets an intersection with a traffic light. The intersection can be controlled by a data processing device in the vicinity. This will allow for the control of the traffic light and interaction between MSs. Another embodiment allows a user to search for parking lots as he enters a parking lot. This is done in accordance with the available parking spaces. Other nearby data processing systems may also be processed to accommodate user preferences (as described in the MS), group preferences and/or locational preferences (see U.S. Pat. Nos. Nos. terminology) of MSs nearby.
An MS can keep a history of hotspot locations to provide graphical indications of hotspot location. The MS user can use this information to guide users in the future in order to access hotspot services. Hotspot growth can prevent a database from being updated with new locations in a timely manner. As appropriate to each MS, the MS can find hotspots. Hotspot information can be instantly accessed by the MS.
Peer to peer proximity detection is another advantage for identifying peer service targets within the MS area. An MS can act on a peer service target within its range using an application at the MS. An MS can notify the user about service availability by notifying them of the complementary location of the MS and peer service target. The MS application can be used by the user to make a payment or perform any transaction related to the peer service target.
“Another advantage of a MS is its ability to provide self-management capabilities such as automatically marking photos taken with location information, date/time stamps, and who was taking the photo.”
“Another advantage is being alerted nearby to people who need assistance, nearby fire engines, or police cars that require access to roads.”
The MS platform allows for the rapid introduction of new LBX functionality and features to the market. It caters to all levels of users: novice users, highly skilled software developers, and intermediate users. Rich programming environments are available that allow users to trigger privileged actions by exchanging whereabouts information with other MSs. You can embed the programming environment in or?plugged into? an existing software development environment or provide it on its own. An syntax can be specified using source code statements, XML or SQL database definitions. It is possible to create privileged actions in a user-friendly environment by exchanging whereabouts information with other MSs within the same vicinity. This platform is event-based. WDRs that contain certain sought information can be recognized at strategic processing routes for novel processing of actions. You can define events with complex expressions. Actions can also be defined using your own executables, APIs and scripts. There are many ways to define charters and permissions using the LBX platform. These include an internalized programmatic, a SQL database, a data record, a datastream, and a well-defined BNF grammar that can be used to generate other useful implementations (e.g. “lex and yacc”.
It is advantageous for permissions/or charters be configured in anticipation or all possible future travel, situations, environments, applications, or conditions of a MS (or MSuser) or a plurality (by permissions or charters), MSs (or MSusers). It’s powerful because permissions and charters that are configured in advance of expected events reveal novel, unpredicted automated actions and application behavior for new uses.
It is also possible to have a large number of privileges that can all be managed and configured in a peer-to-peer manner between MSs. Any peer-to-peer feature or set can be granted privileges from another user. This is a great advantage because it allows you to provide a variety of ways to manage privileges within a network of MSs.
It is an additional advantage to have a comprehensive set of options for charters. These can be configured, managed and processed in a peer-to-peer manner between MSs. Charters can be made effective by a variety of terms, conditions, and operators. This is a great advantage because it allows you to provide a variety of ways to manage and maintain charters within a networked MS. Charters can be modified by themselves to change permissions and charters “on the fly”. (i.e. ”
It is an additional advantage in multithreaded communications between MSs of permission and charter information, and transactions between MSs to facilitate peer-to-peer interactions. Depending on the MS, any signal spectrum that can be used to transmit and receive data is possible. Different signaling wave types and protocols can be used to interoperate between MSs or for single transactions.
It is another way to increase the LN-expanse’s range from a wireless area to potentially infinite surroundings through data processing (e.g. routing) equipment. Wireless proximity is used to govern automatic location determination. However, whereabouts information can be communicated between MSs that are far apart if there are privileges or charters making this information relevant for each MS. If there are no privileges to keep it, the whereabouts information of others cannot be kept. If there are no privileges granted to potential recipients MSs, whereabouts information cannot be shared.
Another advantage is the ability to configure a MS for any behavior based on whereabouts, location, and?in-the vicinity. Conditions for the MS and/or its peers MSs during travels. The user can provide a processing “character” with infinite control. The MS supports many MS applications with location-based functionality and features. Charts can be used to automate: MS configuration and system variable settings, clipboard and paste operations and MS input and out control. They also allow for automatic communications with MSs and data processing systems.
Another advantage is the use of a user interface such map navigation to generate a map term, such as a point or radius, or a set of points that define area(s), on a map. This map term can be referenced in a charter configuration, and then processed for replacement. A user can make selections on a map and the location information for those selections is generated automatically. Without having to know the exact location information, the user can give the information a name. For more information about the location details, the user can refer to the name. The WDR search criteria can be used to determine a map term. This is a WDR that was found in the MS of map terms creation or a peer MS. Recent WDR location (e.g. Queue 22; or Past whereabouts of WDRs found (e.g. History 30 may also be used. Queue 22 can be considered to be maintaining a short-term history while history 30 could be considered to be maintaining a long-term history. It can be difficult to specify locations in charter configurations. The user can use map terms to indicate locations and hide the complexity of how it was generated. Some embodiments allow map terms to be used in a wider scope, allowing substitutions where necessary. Some embodiments allow map terms to be used in a wider scope by allowing?special terms? to be created automatically by the user by selecting a MS from a map.”
It is a benefit for a convenient “charters starters?” User interface to browse, enable, disable, and maintain charters depending upon application, categories, or usable/cloneable snippets. A MS might come prepackaged with many different charters that have been marked and organized for specific applications. A user can search for, locate, manage, enable/disable, or disable a group of charters according to their category. They can also clone charter subsets to create new charters. MS users can manage their own charters or charters of privilege granted to others using the charters starters interfaces. A user can search, find, manage, and disable a set charters using any criteria contained in the charter definitions. An authorized or knowledgeable user can organize charters in any way he chooses, such as to assign charters to specific categories and applications. The user interface for charter starters organizes charters into easily identifiable groups (e.g. The user interface for charter starters organizes complex charter configurations in easily identifiable groups (e.g., folders, categories, and applications). It makes it easy to enable, disable, and organize any desired set of complex charter configurations.
It is a benefit to provide application term triggered processing for the LBX platform and all users and skill levels thereof. It provides a rich programming environment with a user-friendly configuration environment. Application data that is modified can trigger privileged actions by users. You can embed the programming environment in or?plug into? an existing software development environment or provide it on its own. An syntax can be specified using source code statements, XML or SQL database definitions. The platform uses an event-based environment in which events that modify application data containing specified sought values/information are recognized and processed. You can define complex events using complex expressions. Actions can also be defined using scripts, homegrown executables and APIs. There are many ways to use the LBX platform.
Another advantage is the extensive range of paste commands that allow you to past LBX data into either data entry fields, snapshots, or one or several video stream frames. You can access and paste data from queue 22, history 30, statistics 14, and 16; atomic terms, map terms, WDRTerm data, AppTerm data, any term or construct from the LBX BNF grammar. Data can describe current, past or futur LBX data. Averages of MS or LBX. Data derived from MSs within the area (e.g. Nearby; and data received, sent or processed at the MS. Before finalizing the paste action, the user can adjust the appearance of the paste data (font, size and color, or any other characteristic).
“Another advantage is the provision of?plug in? Application support allows an application to be easily integrated into the LBX framework and architecture through Prefix Registry Records 5300. Application data and executable interfaces can be plugged in. Charter processing has access to application data for configurable and conditional event-based charter processing. Various ?plug-in? Various plug-in? systems and methods are described. The LBX platform integrates well with MS applications of any variety to create a cohesive architecture.
Another advantage is the tight coupling/integration of LBX processing configurations and processing into a program environment for a WPL within the context of a rich PL. LBX processing may be a?plug in? To integrate LBX processing into PPLs or to provide rich WPLs, it can be a?plug-in? A variety of methods and systems are described to provide a complete LBX platform.
It is a benefit to facilitate the creation of charters that are appropriate for a specific MS application. A special context is defined for each application, and candidate charters (or portions thereof) are presented to the user. These are derived from the specific terms and the atomic operands for that particular application context. Pre-made charters and charter portions are available to minimize the effort required for creating charters that fit a specific application context. After being presented with suggestions, users can choose, or select and?tweak! to a desired charter configuration. You can also set privileges in the context of the selected charters or application.
It is a benefit for automatically comparing MS profile information for matches to trigger conditional actions for charters. Data can be configured by users and sent to MSs for automatic charter processing. MSs can be automated with social interaction to other MSs, so MS users are notified of MS users in their vicinity who might be interested in a variety of applications.
It is a benefit for sending application data field to peers MSs in your vicinity, receiving them from the peer MSs, and transmitting them to data processing system in the nearby in a peer-to-peer manner. This allows for interoperability between a variety of applications and automated trigger processing. MSs can communicate wirelessly and directly with one another as peers. Peer data processing systems share application data fields (e.g. MSs are preferred to be available as additional AppTerm data at a MS (see below). The user can control which fields of the application data are disabled or enabled. Privileges between MSs can be used to enforce the desired processing effects on MSs that send or receive data.
Another advantage is that MSs can access a wide range of location-based enhanced applications without the need for a service. A service is not required for geo-fence alerts and proactive content delivery. No. No. Alert processing, geo-fences, and content are maintained at a MS to a) be processed at the MS when interfacing directly with peers MSs; and, b) be shared with peers MSs to be processed at peer MSs. It is possible to deliver content faster and provide alerts because the processing happens at the MSs, without any interoperability with any’middleman’. service.”
“Another advantage lies in the multi-threaded, wireless multi-wave and multifrequency multi-channel capability of a disclosed MS for RFID/RDS integration. The LBX framework, as described below, is well suited for RFID and RDS interfaces.
“Another advantage is that the MS can automatically or upon request analyze a picture or video stream frame for the purpose of more confidently determining an MS location.” To drive the desired processing, user configurations can be used.”
“Another benefit is the ability to manage and maintain statistics and historical information in a MS. There are many options for when, where and how to save this information.
“An additional advantage is to provide Sudden Proximal Users Interfaces (SPUIs), at a MS, when detecting other data processors in the vicinity (e.g. Another MS, an RFID device, any data processing system that emulates a MS, and any other data processor system. SPUI is a GUI that notifies a MS user when a remote data processing device of interest is within the vicinity. It is determined by configured?in-the vicinity? conditions. The following configurations can trigger the SPUI at the MS: charter configurations (AppTerm trigger configurations), RFID trigger configurations, and application term (AppTerm). SPUI processing can be automated using many applications to save MS users from repetitive interactions with MS user interfaces for common tasks such as device and appliance interfaces. Automated authentication is possible. SPUIs can also save data from previous executions to default data in a subsequent operation. This prevents MS users from having to re-enter data that they have already entered. Many applications can be used within the SPUI framework. Some of these are listed below.
“Another benefit is the user’s ability to request/transmit outbound information manually with options for customizing such as a WDR or derivative of a WDR. A subset of a WDR. User-configured data sets. Customized data sets. A WDR, or derivative/subset thereof, may be requested to be sent. The WDR can be first searched at the MS using user-specified search criteria. It can then be transmitted outbound according the user-specified transmission criteria.
It is a benefit to offer a task monitor/trace interface that allows you to examine MS task status for past and current system states. Based on task status information, the task monitor interface allows for easy creation of contextual charters.
It is a benefit to provide generic application record sorting, based on: MS location, whereabouts a particular MS or other WDR search criteria, for sorting WDRs at the MS where the sort was requested.
“Another benefit is the provision of one or more nearby monitors to indicate MSs of concern that are near you. Multi-threaded MS allows for multiple nearby monitors. An MS user can set criteria/conditions (i.e. Expression) to be used by a nearby monitor to compare WDR information received at the MS. The result of the expression (True/False), determines whether the MS that generated the WDR should be monitored within the specific vicinity monitor. An asynchronous or polling event (e.g. Design may also be used, such as the WDRs received.
Another advantage is automatic inventory management processing for inventory objects that are within a MS’s reach at any given moment. An MS user can track an order, count the stock and track the location of specific items. An MS user can set payment information to automate order processing. Inventory items can be enabled to manage inventory in conjunction with a data processing system (e.g. (RFID tag, affixed/integrated MS, etc). An MS user can either manually place an order using the automatically calculated inventory count information or schedule the order for automatic ordering (e.g. You can use a calendar entry. You can order inventory items individually or in groups, such as as part of a group hierarchy. The typical uses of inventory items are to manage the daily life of MS users: products in the kitchen pantry, fridge, freezer, closets, offices, bathrooms, laundry rooms, office supply closets, and other areas of a MS user?s home, office, or place of work.
Another advantage is that MS users can easily map privileges and charters between identities. It could be time-consuming to find out which privileges, grants, and charters are granted to each MS user and then grant those rights to another MS user. This task can be time-consuming and error-prone. The resource mapper functionality allows all rights (e.g. Resource mapper functionality is provided that allows all rights (e.g. privileges) to be assigned to another identifier in one operation. You can also remove the same rights in a single operation. MS users have the ability to grant privileges or charters to an identity (e.g. You can then group, and assign or remove all of them in one operation to other identifiers.
Cross-application addressing is another advantage that allows different applications to be linked. This means that features and contexts from one application can automatically be applied to affect those of another. The contexts of an application’s identifiers can be correlated with another form. An example: an email address of a recipient is correlated with the phone number for the same MS. This allows the user to immediately see all the emails that are associated with a particular person during an active phone conversation. Correlation occurs without the need to know any addressing details. You can use multiple identifier forms to correlate with a single MS, depending on the application.
The accompanying drawings provide details on the additional features and benefits of the disclosure as well as the structure, operation, and operation of different embodiments. Similar reference numbers in the drawings generally refer to identical, functionally comparable, or structurally similar elements. The leftmost digit (s) of the reference number indicates the drawing where the element appears for the first time. However, reference numbers 1 through 99 can be found on the first four drawings in FIGS. FIG. 1A through 1D and FIG. 1F. 1F. Dashed outlines (e.g. process blocks, data records fields) can be used in drawings to highlight or indicate optional embodiments depending on MS performance considerations. The discussions, drawings, and materials contained herein are not intended to limit any particular embodiment. This is the intended broadest interpretation. Other embodiments that achieve the same functionality fall within the scope and spirit of this disclosure. Information is presented as an example. Many embodiments are possible without departing from this disclosure’s spirit and scope.
The present disclosure will be described with reference to the details of the drawings. To focus on the main aspects of the disclosure, flowcharts will not include obvious errors. 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. In flowchart blocks, a semicolon can be used to separate multiple processing blocks within one physical block. This allows for simpler flowcharts that use fewer blocks. Multiple processing blocks can be placed in one block of the diagram. Processing flowcharts should be understood in the most general sense possible. This is not to limit the functionality of the flowchart. Field validation in flowcharts is preferred to check for SQL injection attacks and communications protocol sniff attacks, preventing of MS addresses being spoof, syntactical correctness and semantics errors, and preventing of MS addresses being spoof. The disclosed user interface processing and/or screenshots can also be used as preferred embodiment examples. However, they are not limited to the scope and spirit of this disclosure. Alternate user interfaces may be used (since this disclosure does not limit) but will use the same mechanisms. However, they could use different mechanisms and still remain within the scope of this disclosure.
“Locional terms like whereabouts, location and position, area, destination and perimeter, radius, geofence and situational location or any other related two- or three-dimensional locational term used herein for described position(s), locations and/or whereabouts are to be understood in the broadest possible sense. One example of a location field 1100c is an area. On earth), a point (e.g. on earth), a point (e.g. Another example is that a radius can define a sphere within space rather than a circle within a plane. A planet field may form part of the location in some embodiments (e.g. Earth, Mars, etc. are all part of field 1100c. Other location information (e.g. It is also possible to include latitude and longitude for Mars in field 1100 c. Some embodiments may include elevations or altitudes from known locatable points, distances from the origin(s), etc. It can be used to indicate where a point in three-dimensional space or sphere, solid, is located. The same point can also be used to provide mathematical references to other points in the solid area/region. Further descriptions of angles, pitches and rotations from any reference point may be provided. A three-dimensional area/region can be conical, cubical, spherical, pyramidal, or irregular shape. It can also include any other shape that can be manipulated using a three-dimensional graphic interface or mathematical model descriptions. A MS can occupy areas/regions in space, or pass through (e.g. A MS can be used to occupy a space or pass through (e.g., by a traveler), or refer to configuration by a MS. Three-dimensional embodiments determine nearby/nearness using three-dimensional information. For example, a spherical circle around one MS intersects a radius around another MS. Nearby/nearness in a two-dimensional embodiment is determined using two-dimensional information. For example, a circle around one MS intersects a circle around another MS. A point can be defined as a point on an x-y?z plane, a position in polar coordinates or something similar, such as the center of a globe (e.g. Earth), or the Sun, any origin in the Universe or any other source for clearly locating three-dimensional locations, positions, or whereabouts within space. Elevation (e.g. Elevation (e.g. To define a region of space, you can connect x-y/z coordinates together to create a three-dimensional space. You can represent a location (field 1110 c) in many ways without violating the spirit or scope of this disclosure. MSs can be carried by users and travel through three-dimensional areas/regions in three dimensions. They also travel under the water through three-dimensional regions in three dimensions.
“Several embodiments of communication between MSs or an MS with service(s) will share channels (e.g. Depending on the time in effect, frequencies can be used to communicate. To share a channel, you will need to have a processable signature that can be used to identify transmissions and carry data. Depending on the time in effect, there will be different ways of communicating between MSs or service(s). Which embodiments are preferred will depend on the number of channels that can simultaneously be listened to and/or transmitted by a data processing device. Preference will also depend on the number of channels that can be used simultaneously. This disclosure does not include unnecessary details in the different communication channel embodiments to avoid confusing new material. MSs can communicate with each other in peer-to-peer fashion, regardless of which channel is used within the scope and spirit.
“Novel features described herein do not have to be presented as all or none. Some features can be used in a single MS embodiment, while others may include a subset of functionality and features in other embodiments.
“Location Based eXchanges Architecture (LBX).”
“FIG. “FIG. MS 2 also includes processing behavior referred as LBX Character 4 or Other Character 32. According to the disclosure, LBX Character 4 is processing behavior that causes MS 2 to assume the character of a Location Based Exchange MS (LBX). Other Character 32 is processing behavior that causes MS to assume the character of a prior art MS. This behavior is well-known to those who are skilled in the art. Other character 32 gives MS users a limited range of configuration and functionality. In certain embodiments, LBX component 4 may use other character 32 components 34-36, and 38. Other components of character 32 may or may not make use of LBX component 4 components 6 through 30.”
“LBX character 4 preferably contains at least Peer Interaction Processing code 6, Peer Interaction Processing data 8 and Peer Interaction Processing data 8 respectively. Self management processing code 18 is also preferred. WDR queue 22. Send queue 24. Receive queue 26. Service informant code 28. LBX history 30. Peer interaction processing code 6 includes executable code in hardware, firmware, and software for carrying out the LBX processing logic described herein when interacting with another MS. Peer interaction processing data (PIP data 8) includes data that is stored in any type of memory MS 2 has, including flash memory, hardware memory, hard drive memory, and any other available memory. PIP data 8 includes intelligence data to drive the LBX processing logic in the present disclosure when interfacing with other MSs. Self management code 18 is executable code that can be used in firmware, software, or hardware to carry out the local user interface LBX processing logic. Self management processing data 20 includes intelligence data to drive processing logic as disclosed for locally maintained LBX functions. WDR queue 22 includes Whereabouts Data Records 1100 and is a First In-First Out (FIFO) queue for housekeeping purposes to prune the queue to a reasonable trailing record of inserted entries. remove stale entries). WDR queue 22 has the advantage of queue entry retrieval processing that is similar to Standard Query Language querying. In this case, one or more entries may be retrieved by querying any data field(s), WDR 1100, and returning lists of entries sorted by ascending/descending key on any key field.
“All disclosed queues (e.g. 22, 24, 26, 1980, 1990 (See FIG. 22, 24, 26, 1980, 1990 (See FIG. Queues have an implicit semaphore that allows for synchronous access to queue data within a multi-threaded environment. This prevents data corruption and misuse. These queue interfaces are common in many operating systems. If an MS operating system environment does not provide an implicit semaphore-protected queue scheme, then queue accesses shown in the disclosure flowcharts will have to be understood as having a prior request to a queue assigned semaphore locking before queue access and a subsequent release of the lock after access. Other operating systems may employ methods to achieve thread-safe synchronization functionality. Queue functionality can be achieved with lists, arrays and databases (e.g. SQL) or other methods, without departing from this article’s spirit and scope.
Queue 22 alternative embodiments may have multiple WDR queues that segregate WDRs 1100 according to field(s), in order to facilitate timely processing. WDR queue 22 could contain at least two (2) separate queues. One for MS 2 whereabouts and one for MS 3 whereabouts. In some cases, WDR queue 22 could be one instance WDR 1100 that contains the most recent MS 2 whereabouts. MS 2 applications may use another queue 22 to maintain WDRs from distant MSs. For MS 2 whereabouts, at least one entry must be maintained to WDR Queue 22 at all times.”
“Send queue 24 (Transmit(Tx) queue), is used to transmit communications data to a peer MS in the immediate vicinity (e.g. Nearby as indicated by the MS 2’s maximum range 1306 Receiving queue 26 (Receive(Rx) queue), is used to receive communications data from peers MSs in the area (e.g. Nearby as indicated by the MS 2’s maximum range 1306 The MS 2 may indicate that Queues 24 & 26 have a plurality queues to segregate data. This facilitates interfacing with the queues, particularly when different types of queue entries and/or sizes are used. In multi-threaded systems, a queue interface is used to send/receive data to/from MS. However, alternative embodiments allow data to be sent/received directly from the processing thread described herein. Queues 22, 24 and/or 26, may be implemented as a data form or SQL database. They are maintained at MS 2 by persistent storage, memory or any other storage. Some embodiments do not require queues 24, 26 or 32, as other characters 32 already have the resources to perform some LBX 4 processing.
“Queue embodiments can contain fixed length records or varying length record, pointers for fixed length records, pointers towards fixed length records or pointers toward varying length record. Pointers can be used if dynamically allocated to record storage upon insertions. They may then be released after record use, discards, or retrievals.
As those who are skilled in the art know, when a thread sends data to a queue 24, in anticipation of a reply, there is correlation data in that data. This data is sought in a response from a thread at queue 26, so the sent data can be correlated with the received data. A preferred embodiment of correlation uses a round-robin sequence number that is placed in the data to be sent along with an unique MS ID (MS ID). Correlation can also be encrypted if data is not encrypted in communications. The unique MS ID (MS identifier) can be used to help identify which (e.g. Correlation helps to identify the data that caused the MS to respond. The data received from a queue 26 responder is used for correlation processing (e.g. Field 1100 m is used to correlate the received and sent data. Preferably, the sequence number is incremented every time before being used to ensure a unique number. Otherwise, it might be difficult to determine which data received is a reply to which data was sent. This is especially true when multiple data packets are sent in a matter of seconds. The sequence number is increased to a maximum value, such as 2**32?1. When the sequence number reaches a maximum value (e.g. 2**32?1) it is round-robinned and incremented again. This ensures that data are properly correlated between responders and MS over time. Other correlation schemes are available (e.g. Other correlation schemes (e.g., signatures, random numbers generation, checksum counting and bit patterns) can be used to achieve this functionality. Correlation can be used to correlate a reply with a request if send and receive queues of Other Character 32 is used. “Send with receipt”
“It may be a good idea to conceal the MSID when sending it wirelessly. The MS ID in this embodiment is a reliable and easily recognizable derivative (e.g. A pseudo MSID that is able to be detected by communications traffic. The pseudo MS ID can conceal the true MSID. This would hide the true MSID from hackers who could sniff wireless protocols. For simplicity, the derivative can be recognized by the MS and can be used to hide the true MS ID from hackers sniffing wireless protocol. Phone number or serial number, in particular when anticipating traffic in response. However, it can still be useful for directing replies back to the origin MS (with the pseudo MSID (e.g. correlation)). MS could know which correlation was anticipated in a response and save it to local storage until it is used (i.e. If the matching response is not correlated, or becomes stale, then a MS would know which correlation is anticipated in a response and save it to local storage. A correlation response queue, such as CR queue 1990, can be used in another embodiment to correlate responses with requests that have different correlations for pseudo MSIDs. All embodiments of the disclosure require that the MS ID (or pseudo MSID) be used to target communications traffic to the MS.
“Service informant code 28” is executable code in hardware, firmware, and software that allows for the execution of informing a supervisory services. Although the present disclosure doesn’t require a connected Web service, there are features that allow a service to be kept informed about MS LBX activities. The service informant code 28 is able to communicate any data 8, 22, 24, 26, 30, 32, 36, 38 or any other data processed by MS 2.
“LBX History 30 contains historical data that is useful in maintaining MS 2 and may be useful for informing a supervisory agency through service informant code 28, LBX History 30 should have an associated thread for processing to keep it pruned to the satisfaction MS 2 users (e.g. The user prefers to keep the last 15 days of specific history data and 30 days of other specified history data, respectively. A suitable interface to MS 2 allows users to browse, modify, delete, or add to LBX History 30 in the manner that is applicable to the processing described herein. To send an outbound email or SMS message, or any other outbound communication, the service informant code 28 can be used.
“PIP data 8 should include at least permissions 10, statistics 14, charters 12, and a service directory 16. Permissions 10 allow other MS 2 users to interact in the same way that the MS 2 user would like. Permissions 10 grant permissions from the MS 2 user to other MS 2 users. Permissions 10 may also, or alternatively contain permissions granted by other MS users to the MS 2U. Permissions can only be granted to MS 2 users. Charter 12 provides LBX behavior conditional expressions that describe how MSs should interact. The MS 2 user can configure charters 12 for other MS users. Charters 12 can be configured by MS 2 users to configure charters 12. Permissions are required for some charter expressions. Statistics 14 are kept at MS 2 to reflect peer (MS-to-MS) interactions that took place at MS 2. Statistics 14 may also, or alternatively reflect peer (MS to MS) to peer interactions of interest that occurred at MS 2. A service may be informed by the 28th service informant code. Service directory 16 contains routing entries that describe how MS 2 will locate a requested service or how another MS can access MS 2 to find it.
“In certain embodiments, any code (e.g. 6, 18, 28, 34 and 38 can access, modify, alter or dispose of any data (e.g. 8, 20, 22, 24, 26, 30, 38, 36, 38) for any other MS 2 component. Other embodiments might choose to separate the processing of LBX characters 4 and 32. Rectangular component boundaries can be used to represent logical components and they do not need to define who has access to which. MS (also MSs), references are discussed herein in context of the new and useful features.
“FIG. “FIG. LBX MSs can be considered peers for their functionality and locational features. MS 2 can communicate with MSs 2 without the need for a service. FIG. FIG. 1B shows a wireless network 40 consisting of five (5) MSs. Each MS can communicate directly with other MSs in the area (e.g. Nearby as indicated by the maximum range 1306). Communications are wireless broadcast datagrams with limited reliability and recognizable packet identifiers in a preferred embodiment. Another embodiment of wireless communications is reliable transport protocols such as TCP/IP that are carried out by MSs. Other embodiments include new data, such as the usual communications data associated to other character 32. Communications Key 1304 is used in transmissions to be recognized by MSs in the area. As an example, LBX data can be added to a protocol when an MS communicates conventionally. This allows other MSs within the area to access the data and detect it. This is advantageous because MSs can use wireless communications to perform conventional behavior. Additional information is added (e.g. Communications Key 1304 to existing communications
“Regardless of the embodiment, MS 2 can communicate with any other MSs in its vicinity using the methods described below. The communication path 42 between two MSs can be bidirectional or at least unidirectional depending on the embodiment. Although the bidirectional path 42 can use one communication method in one direction, and another in the other, they can still communicate with each other. A path 42 is composed of two unidirectional communication paths. There are N*(N??1) unidirectional routes for N MSs within a network 40. A network of 10 MSs would result in 90 (i.e. 10*9 one-way paths for communications between all 10 MSs to enable them to communicate with each other. To minimize the number MS threads listening to different channels, it is preferable to share the same signaling channels. Flowcharts can process at extremely high speeds, especially for communications processing. The MSs communicate wirelessly with each other. However, path 42 embodiments can involve any number intermediary systems or communication methods. For example, see FIG. 1E.”
Click here to view the patent on Google Patents.