BACKGROUND

[0001] The present disclosure relates to networking ecosystems. More specifically, the present disclosure relates to systems and methods for providing and using an incentivized and decentralized ecosystem.

[0002] Nearly 40 percent of the global population does not have reliable internet access. Accordingly, these people cannot access and participate in various digital communities.

Additionally, due to the lack of internet accessibility, the prevalence of web3 decentralized technologies is significantly limited.

SUMMARY

[0003] In one exemplary embodiment, there is provided an incentivized system. The system includes one or more memories storing computer executable instructions and one or more processors. When executing the computer executable instructions, the one or more processors are configured to obtain user location data and travel data from a first user device of a first user, obtain owner data of an owner business associated with a wireless access point (WAP), prompt the first user to input WAP data associated with the WAP, and verify the WAP. The one or more processors are further configured to generate a WAP verification status, generate a WAP database based at least in part on the owner data, the WAP data, and the WAP verification status, and automatically connect subsequent user devices of subsequent users to the WAP.

[0004] In another exemplary embodiment, there is provided a computer-implemented method. The method includes the steps of obtaining user location data and travel data from a first user device of a first user, obtaining owner data of an owner business associated with a wireless access point (WAP), prompting the first user to input WAP data associated with the WAP, and verifying the WAP. The method further includes the steps of generating a WAP verification status, generating a WAP database based at least in part on the owner data, the WAP data, and the WAP verification status, and automatically connecting subsequent user devices of subsequent users to the WAP.

[0005] In another exemplary embodiment, there is provided a non-transitory computer- readable medium containing computer executable instructions that, when executed by one or more processors, cause the processors to perform a method. The method includes the steps of obtaining user location data and travel data from a first user device of a first user, obtaining owner data of an owner business associated with a wireless access point (WAP), prompting the first user to input WAP data associated with the WAP, and verifying the WAP. The method also includes the steps of generating a WAP verification status, generating a WAP database based at least in part on the owner data, the WAP data, and the WAP verification status, and automatically connecting subsequent user devices of subsequent users to the WAP.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The embodiments illustrated herein are not limited to the precise arrangements, sequential steps, and dimensions shown. Like numerals indicate like elements throughout the drawings. In the drawings:

[0007] FIG. 1 illustrates a schematic view of a system for providing an incentivized web3 ecosystem;

[0008] FIG. 2 illustrates a schematic view of the ecosystem server;

[0009] FIG. 3 illustrates a flowchart of a method for connecting users to a network;

[0010] FIG. 4 illustrates a flowchart of a method for mapping user locations and network access points on an interactive map;

[0011] FIG. 5 illustrates a flowchart of a method for facilitating communication between users based upon proximity;

[0012] FIG. 6 illustrates a flowchart of a method for facilitating communication between users based upon user characteristics;

[0013] FIG. 7 illustrates a schematic view of an interactive map displaying wireless access points;

[0014] FIG. 8 illustrates a schematic view of a streamlined user interface for viewing business information associated with one or more wireless access points;

[0015] FIG. 9 illustrates a flowchart of a method for generating the user interface of FIG. 8;

[0016] FIG. 10 illustrates a flowchart of a method for verifying a wireless access point; [0017] FIG. 11 illustrates a schematic view of an infinite caching system wherein certain wireless access points are grouped together for subsequent caching onto a user device; and [0018] FIG. 12 illustrates a flowchart of a method for infinitely caching wireless access points.

DETAILED DESCRIPTION

[0019] FIG. 1 illustrates an example of a system 100 for providing a web3 ecosystem including a crowdsourced network, an interactive map, and/or one or more communication systems. The system 100 generally comprises a network 102, one or more access points 104 for accessing the network 102, user devices 106, and an ecosystem server 200 connected to the devices 106 via the network 102. The system 100 may comprise an incentivized and gamified application 110 which is downloadable onto one or more devices 106, as shown in phantom in FIG. 1. It is conceivable that in other embodiments, the system 100 may include different or additional elements from what is illustrated in FIG. 1.

[0020] The system 100 functions as a bridge between the real world and the metaverse. The system 100 provides internet access and facilitates communication between users based upon unique blockchain identifiers, such as the ownership of a particular group of NFTs, via an interactive map 112 and one or more communication systems. The system 100 connects users to free crowd-sourced network access points 104. The system 100 also facilitates communication within and outside of its ecosystem. The system 100 rewards user contributions and validations through economic in-ecosystem incentives and acheivement-based gamification. The system 100 provides a rewarding user experience with effectively zero entry costs for its users. For example, users of the system 100 can earn economic prizes, e.g., tokens, and achievements by adding new, connecting to, and verifying network access points 104. Users can also be awared for fulfilling bounties, completing goals, and earning achievements. The system 100 can also provide a marketplace where users can buy, sell, and trade collectibles, such as Non-Fungible Tokens (NFTs) with other users. The system 100 can also generate access point data from one or more owner databases 130, which is associated with one or more owners such as commercial businesses, and a streamlined display within the application 110 to notify users of various information and incentives on behalf of the owners of the access points 104. [0021] The system 100 also comprises a blockchain 120. The ecosystem server 200 may be connected to and retrieve data relating to the users who use the blockchain 120. Any type of blockchain may be utilized. The system 100 may implement a blockchain ledger, manager, wallet, or like technology. The system 100 may connect to a blockchain of a third party. Any number of existing blockchain providers may be utilized, for example Ethereum, Bitcoin, Dfinity, or Blockphase.

[0022] The network 102 can be any type of communications network, such as a local area network (LAN), wide area network (WAN), a public network such as the internet, and/or some combination thereof. In general, communication between the various devices and systems may occur via any desired network interface using any type of wireless connection, using a variety of communication protocols (for example UDP, TCP/IP, HTTP, SlvlTP, FTP), encodings or formats (for example HTML, JSON, XML), or protection schemes (for example VPN, secure HTTP, SSL).

[0023] The system 100 may further comprise one or more WiFi or wireless access points (WAPs) 104, which can be identified, added, and verified by users. The WAPs 104 may only be WAPs associated with places of business, and thus may not be associated with homes or apartments. In more details below, the ecosystem server 200 identifies and verifies certain characteristics of the WAPs 104. Each access point 104 may or may not be associated with an owner database 130 which is in communication the ecosystem server 200.

[0024] The system 100 may further comprise one or more owner databases 130 associated with the one or more access points 104. Each owner database 130 can be associated with only one or multiple access points 104. Each owner database 130 may store data associated with the business, such as hours of operation, incentives like discounts or special deals, events, and the like. The ecosystem server 200 can be connected to each owner database 130 via the network 102.

[0025] The user devices 106 may connect to the network 102. For instance, the user devices 106 may connect to the network 102 through the one or more WAPs 104. Additionally or alternatively, the user devices 106 may connect to network 102 via their service provider or an unlisted WAP. The devices 106 can be associated with one or more users and/or with one another. A single user may have two or more devices 106. Each device 106 can be connected to the system 200 via one or more WAPs 104 and the network 102. Alternatively, one device 106 may not be directly connected to the network 102 and may instead be connected to another device 106 which is connected to the network 102.

[0026] Each user may have one or more devices 106 that may be stationary, portable, and/or wearable. The devices 106 can be in the form of smart devices. The devices 106 may be in the form of a computer, a smartphone, a tablet, a navigation system, a handheld GPS system, user equipment (UE), a portable gaming device, a media user head-mounted display (HMD), a virtual, augmented, and/or mixed reality device, such as a headset or glasses, smart glasses, smart clothes, smart shoes, data gathering implants, and/or or other suitable data gathering electronic devices. The user devices 106 may or may not be identical to one another. By way of example only, one user may have a smartphone 106 and a wearable device 106, such as a smartwatch, that is connected to the smartphone 106 and/or the network 102. It should be appreciated that the user may only have a smartphone 106, have both smartphone 106 and wearable device(s) 106, or just a wearable device(s) 106 only.

[0027] Each device 106 may include input/output devices, e.g., a display screen, lights, and speakers, a local data storage, one or more sensors, one or more applications, one or more application programming interfaces (APIs), and/or a notification module. Each device 106 may further include the application 110 of the ecosystem server 200. Each device 106 can display the interactive map 112 generated by the ecosystem server 200. The devices 106 may also include other components known to those skilled in the art. Therein, the devices 106 may include any desired hardware and/or software for generating user data.

[0028] The one or more sensors, integrated within the device 106, may include a location sensor, in the form of a timekeeping device, a positioning device, a speed sensor, an accelerometer, a gyroscope, an altimeter, a pedometer, a heart rate sensor, and/or a camera. For instance, the positioning device may monitor the position of the smartphone 106 and/or wearable device 106. However, the one or more sensors may include other and/or additional sensors as appreciated by the skilled artisan.

[0029] The positioning device can be any device or circuitry; for example, the positioning device may comprise a GPS system, a Galileo positioning system, a Global Navigation satellite system (GLONASS), a BeiDou Satellite Navigation, or a Positioning system. As the user moves around with the device 106 in the physical world, the positioning device can track the position of the user and provide user location data to the ecosystem server 200. [0030] The application 110 may monitor and collect user data, WAP data, access point owner or business data, and/or blockchain data. The application 110 may comprise part of the device's 106 operating system and/or additional software installed by the user. The application 110 may or may not include a data collection module. The application 110 may or may not retrieve data from other systems and/or applications on a device 106.

[0031] Referring now to FIG. 2, the ecosystem server 200 is configured for intaking and processing data from the devices 106, the WAPs 104, the blockchain 120, and/or the access point owner databases 130. The ecosystem server 200 may include a network interface 202, a computer-readable storage media 210, such as a memory, and a processing unit 220. The ecosystem server 200 may additionally include APIs for interacting with the devices 106, the WAPs 104, the blockchain 120, and/or the owner databases 130. In some embodiments, the ecosystem server 200 may contain different or additional elements, and the various functions thereof may be distributed among its various elements in a different manner than described herein.

[0032] The network interface 202 establishes communication between the ecosystem server 200 and the network 102. The network interface 202 can include any suitable components for interfacing with one or more networks, including, for example, transmitters, receivers, ports, controllers, antennas, or other suitable components.

[0033] The memory 210 stores WAP data, user data which may be inputted by the user or sensed by the user’s device 106, map data, and blockchain data associated with the users. The memory 210 may generally include any suitable computer readable media, transitory or non- transitory, for storing instructions.

[0034] In some embodiments, the memory 210 may include a WAP database 212 and a user database 214. The databases 212, 214 may be part of the ecosystem server 200 or separate from the ecosystem server 200 and accordingly be remotely accessed through the network 102. The WAP database 212 may store information associated with one or more WAPs 104, including WAP location, download and upload speed, range, security information, and/or associated interior or exterior spaces. The WAP database 212 may also store access point owner data, or business data associated with one or more businesses associated with one or more WAPs 104, retrieved from the owner databases 130 and/or the user devices 106. The user database 214 may store information associated with the past and present users. In some embodiments, the memory 210 may include a single database which stores all necessary data.

[0035] The processing unit 220 generally includes one or more processors 222 for executing computer-readable instructions. One or more of the processors can be an Al processor 222. The processing unit 220 may further include a universal module 224, a user data processing module 226, a generation module 228 for generating the GUI and the map 112 displayed on the devices 106, communication platforms, and digital elements, e.g., avatars, tokens, NFTs, etc., and a notification generation module 230. The processing unit 220 generates the interactive WAP map 112, which maps the digital onto the physical. The processing unit 220 may also generate a first communication system for allowing users to communicate with one another in the real world and/or digital world, and a second communication system for allowing users to meet up with one another in the real world and/or digital world.

[0036] The one or more processors 222 may perform the various functions of the processing unit 220 described herein. The Al processor 222 may comprise an artificial neural network using a machine learning algorithm. The Al processor 222 may train its artificial neural network using a training module. The training module may be included in the ecosystem server 200 or may be included in an external device. The training module can be implemented in hardware, software or a combination of hardware and software. The training module may be stored in the memory 210.

[0037] The universal module 224 hosts and generates content for the users. The universal module may conduct a user verification process, a WAP verification process, a blockchain verification process, update the map, and establish and facilitate communication between users. The universal module 224 may also govern device connectivity and the security thereof. It is noted that the user data processing module 226, the generation module 228, and/or the notification generation module 230 can be a part of or separate from the universal module 224. [0038] The user data processing module 226 may receive user data associated with various characteristics of the users, association data, i.e., blockchain data associated with the users, wallet data, NFT data, group status, past, present, and projected future location data, and/or user velocity. Therein, the user data processing module 226 may identify user inputted preferences, such as privacy requests or communication requests, determine whether a given user is alone or with a group, and determine whether the user is stationary, walking, or traveling by a mode of transportation.

[0039] The generation module 228 is configured to generate the WAP and user databases 212, 214, the WAP map 112, and various user interfaces and overlays to enable the users to interact with other users and access point owners. The generation module 228 may generate communication prompts between users based on blockchain data. The generation module 228 may also generate one or more virtual or digital elements. Such virtual elements can be viewed as part of the map 112, an AR, and/or a VR experience. The virtual element generated can be an avatar of the user, a profile, a digital object which may or may not be associated with the user’s avatar, a coupon, a generated and real time user status, a token, an NFT group or category, or a media display.

[0040] The virtual element can also be an NFT. The NFT may be an image, a video, a 2D and/or 3D digital object. The generation module 228 may automatically generate and mint the NFT depending upon the user data and/or display data. For instance, the generation module 228 may automatically create the NFT based on the actions of the user and/or access point owner data. Additionally, for instance, the generation module 228 may automatically create a user specific NFT based on the user’s inputted preferences, such as preferential selections of various options. The NFT can be used in any interface, marketplace, or metaverse. Additionally or alternatively, the user may identify a preexisting NFT which is verified by the processing unit 220. Additionally, for instance, instead of stamps on a coupon card, the user may be awarded NFT stickers on a digital coupon card which can be conglomerated into a special NFT or another award.

[0041] The notification generation module 230 is configured to generate one or more notifications for each user. The notification generation module 230 may generate one or more virtual, audio, and/or, visual notifications. The notification generation module 230 may generate a notification in real time. The notification generation module 230 may generate a notification depending upon user data and/or the user’s sensed location or activity. A notification may include a prompt for further action, such as communicating with another user who belongs to the same NFT community. The notification may also be a link to an associated webpage or an element generated by the processing unit 220. [0042] Referring collectively to FIGS. 1-10, the processing unit 220 can perform various functions to establish an ecosystem for facilitating the interaction and communication between users and access point owners. The processing unit 220 allows users to use the ecosystem server 200 to easily navigate to WAPs, connect to WAPs, communicate with members in their community, and interact with various businesses.

[0043] In operation, the processing unit 220 can initially receive user data inputted by the users. Such user data can include a user’s residency, preferred mode of transportation, crypto wallet, interest groups such as an ownership of various NFTs, a user’s profile picture which may be in the form of an NFT owned by the user, and a user’s communication preferences. The processing unit 220 may also receive user data which is sensed by the various sensors of the user’s device(s) 106, such as user location data and user travel data. From the user data, the processing unit 220 may determine a user location, a heading, a travel plan or schedule, a state of travel such as if the user is stationary, walking, biking, or traveling at higher speeds in a vehicle or train.

[0044] The processing unit 220 can also obtain owner data from a third party database which may or may not be associated with the access point owner, directly from the access point owner, and/or the users inputting the owner data. The owner data can indicate WAP data, such as connection speed, security, etc., a location, dimensions and boundaries of the buildings which house the WAPs, and information concerning the kind and operation of the business, such as the hours of operation, a menu, an incentivized award system, and/or any specific incentives such as coupons, awards, or deals.

[0045] To obtain and maintain a database of WAPs, the processing unit 220 can prompt one or more users to input WAP data, such as the location, name, and/or password of the WAP if required. Additionally or alternatively, the processing unit may obtain any requisite WAP data from the access point owner. The processing unit 220 can generate and maintain the WAP database, adding thereto upon identifying WAPs from third party databases, WAP data provided by access point owners, and/or WAP data provided by users and/or sensed by users connecting to and interacting with the WAPs. Furthermore, the processing unit 220 may intake, store, validate, and automatically connect user devices 106 to WAPs 104.

[0046] Upon generating the WAP database, the generation module 228 of the processing unit 220 may generate the interactive map 112. The map 112 may display the location of the WAPs 104, the location of the users, and various other geographical, building, and roadway information. As discussed in more detail below, the generation module 228 may additionally generate business interfaces, such as graphical user interfaces, to easily allow users to see and review various businesses, make orders, apply the various incentives such as discounts, and interact with other users at a particular business location.

[0047] FIG. 3 illustrates a flowchart of an auto connectivity method 300 for connecting user devices 106 to the network 102 via one or more access points 104, such as WAPs 104. The processing unit 220 may automatically connect user devices 106 to the WAPs 104. The processing unit 220 first requests the current location of the user, via the sensors of the user device(s) 106. The processing unit 220 may utilize a location API. The current location of the user is returned to the application 110. Subsequently, the current location of the user is sent from the application 110 and updated to the memory 210. The application 110 can continue by requesting from the memory 210 various WAPs 104, which are geographically nearby the present WAP 104. If found, the memory 210 will return nearby WAPs 104. The application 110 next registers and updates geofences around nearby WAPs 104, for example by utilizing a geofencing API.

[0048] When a user enters a known geofence within the application 110, the processing unit 220 will update the geofence and this will send the user’s current location back to the memory 210. The application 110 will then continue to request nearby WAPs 104. The memory 210 returns nearby WAPs 104, and the application 110 then updates the geofences via the geofence API. In parallel, the application 110 simultaneously requests user activity through an activity recognition API. If the activity recognition API returns the user’s travel state to the application 110 that the user is running, biking, or in an automobile, then the application 110 will ignore the geofence event between itself and the geofencing API. If the activity recognition API returns that the user is in a travel state of walking or stationary to the application 110, there are a few different responses based upon what software the user is utilizing. If the user is running Android 29+ the application will await WAP suggestions to auto connect to a Wi-Fi® or WAP connectivity API. If the user is utilizing less than Android 29 or iOS, the application will attempt manual connection to nearby WAPs 104 with the WAP connectivity API. A prompt will be pinged to the user device 106 and the user can easily confirm the desire to connect to the WAP 104, and thereafter the user device 106 will be automatically connected to the WAP 104. [0049] If the connection succeeds, the WAP connectivity API will return a success notification to the application 110, and then the application 110 will notify the user of a successful connection. If the connection fails, the user device 106 will not be connected to the WAP 104, and the processing system 220 will search for any surrounding WAPs 104 to initiate the automatic connection protocol. With either response from the WAP connectivity API to the application 110, the application 110 will update the result to the memory 210 to refine the connection process and prune any inactive WAPs 104.

[0050] The connectivity method 300 described herein reduces user involvement and energy consumption of the user device 106. The user does not need to actively search or log on to a nearby WAP 104 since the processing unit 220 will automatically connect the user’s device 106 to the network 102. Furthermore, the connection to WAPs 104 passively occurs based upon the processing unit’s 220 determination that the user is within a certain proximity of a validated WAP 104 and in an appropriate travel state. Therein, no energy or computational power is spent attempting to connect to WAPs 104 if the user is not at the appropriate location and in the appropriate travel state.

[0051] FIG. 4 illustrates a flowchart of a mapping method 400 for connecting users to WAPs 104 and also connecting the users to each other. The interactive map 112 of the system 100 may be displayed on the user’s device(s) 106. The map 112 is the primary interface between users and the ecosystem. As shown in FIG. 7, in the map 112, users can see WAPs 104, including location and characteristics thereof, other users Ul, U2 such as those who belong to the same or similar digital communities or groups associated with blockchain data, their own digital avatar and/or profile, and/or a UI or portal streamlining access point owner information. The map 112 may also display communication and/or meetup options among users.

[0052] In operation, a user opens the application 110. The application 110 requests user location from a location API. The location API updates the user location to the ecosystem server 200, e.g., memory 210. The location API returns user location to the application 110 and the application 110 displays current user location on the map 112. In parallel, the application 110 may display: the user's avatar Ul, nearby users and their avatars U2, users in the same digital community or group Ul, U2, and WAPs 104. To display other users on the map 112, the application 110 may submit a request to the memory 210, which returns nearby users within the bounds of the map 112 displayed on the screen of the device 106. To display other users in the same digital community or group, the application 1 10 may submit a request to the memory 210, which returns and displays such users on the map 112. To display WAPs 104, the application 110 may submit a request to the memory 210, which returns WAPs 104 within the bounds of the map 112 displayed on the screen of the device 106. As the user adjusts the map 112, e.g., panning, zooming, etc., the aforementioned avatars and WAPs 104 will dynamically change to show avatars and WAPs 104 that exist within the new bounds of the map 112.

[0053] The processing unit 220 may generate one or more communication systems 700, 702 for establishing communication among users. For example, the processing unit 220 may comprise a first communication system for allowing users to communicate with one another in the real world and/or digital world. The first communication system 700 may be in the form of a chat messenger or other messaging platform. The first communication system 700 may be integrated within the map 112. Thereby, the communication system 700 may prompt a user via a display on the map 112. For instance, once prompted the user may make a simple swiping gesture to automatically communicate a hello signal and/or a request-to-chat signal with another user. Specifically, the user may tap and hold on the icon of another user’s avatar U2 and a mini option overlay 704 can be displayed next to the other user U2. The communication option overlay 704 can include the user’s associations or other identifying information, a selectable option of the whether or not the user U1 is feeling friendly and wants to talk or not, and also one or more selectable communique icons to easily and efficiently notify the user and other nearby users via corresponding communique prompts generated by the processing unit 220.

[0054] The second communication system 702 may allow users to meet up with one another in the real world and/or digital world. The second communication system 702 may be integrated within the map 112. Thereby, the map 112 may display one or more digital communities associated with the users and/or the owner businesses. The communities can be displayed on the map 112 in relation to a physical location, in relation to the locations of multiple users, without a geographical relationship or physical location, and/or in relation to a set timeframe. The second communication system 702 thereby fosters physical and/or digital meetups.

[0055] As discussed, the communication system may be in the form of a messenger built into the map 112. This messaging platform allows users to start conversations quickly with digital and/or physical community members. It has built-in, customizable privacy settings that enable users to choose how they want to interact with others. In one privacy setting, for example named ghost mode, a user will be able to use the application 110 without showing their location to other users on map 112. Incoming chat requests will have to be approved manually. In another privacy setting, for example named private mode or community mode, the user may only allow fellow NFT community members to see them on the map or initiate a chat. The active NFT profile picture of the users may determine the associated active community and therefore user visibility on the map 112. However, other NFTs within a user’s wallet will allow a user to message other users in the same digital community; though, such users may not be displayed on the map 112. As an example, a user may only change their profile picture once every ten days to prevent abuse of the community mode. If a user transfers their NFT out of their wallet, they will immediately lose access to that community. However, the user may still retain active chat instances in the communication platform. In another privacy setting, named public mode, a user may allow any other users to send direct messages, provided the users are in the same community or within a 20-km, approximately 12-mile, radius.

[0056] Depending upon the users’ selected communication settings, the ecosystem server 200 may automatically and simultaneously notify users within a preselected community, group, or proximity. For instance, the ecosystem server 200 may automatically send a notification signal to the devices 106 of the users, such as an audio and/or visual indicator, so that the users may visually see and/or hear one another in the real world and/or digital world. For example, if both users have selected community mode, the processing unit 220 may automatically cause each users’ device 106 to emit an audio and/or visual signal so that the users may be notified of each other’s presence and easily identify one another, fostering an introduction between community members who may not have met one another yet.

[0057] The processing unit 220 may incentivize communication and/or physical and/or digital meetups of the users. For instance, the processing unit 220 may generate and grant achievements to the users based upon their communication, meeting attendance, and involvement in the meeting. The processing unit 220 may also grant achievements to meeting organizers based upon the number of attendees, the duration, location of the meeting, and/or the number of meetings held. This functionality aids users in building their own stories alongside their communities, maximizing social interaction and connectivity not just in the digital world but also in the physical world. [0058] FIGS. 5-6 illustrate flowcharts of communication methods 500, 600 for connecting users to one another. FIG. 5 illustrates a method 500 for connecting users based upon proximity. FIG. 6 illustrates a method 600 for connecting users based upon user characteristics, such as a community or group to which the users belong, such as a NFT community.

[0059] In operation, user 1 may open up the application 110. The map 112 may show the avatar of user 1 and the avatars of other users within a predefined community, group, and/or proximity. If desired, user 1 may request to start a chat with user 2. This request is sent to the ecosystem server 200, e g., memory 210. Then, the ecosystem server 200 sends the request to user 2. If user 2 accepts the request to chat, then the communication platform facilitates messages between the users. If user 2 rejects the request to chat, then the communication platform will not generate a chat instance between the users.

[0060] Referring to FIGS. 7-9, the processing unit 220 can streamline business information and incentives to travel to the businesses associated with the WAPs. Specifically, FIG. 9 illustrates a flowchart of a method 900 for establishing communication between businesses who operate WAPs 104 and the users. Initially, the processing unit 220 can obtain user location and travel data (block 902) and determine the location and travel state of the user (block 904). The processing unit 220 can also obtain owner data (block 906). Thereafter, the processing unit 220 can generate the WAP database 212 and the WAP map 112 (block 908). In one embodiment, the processing unit 220 can generate the WAP database 212 and the WAP map 112 utilizing user input adding various WAPs 104. In another embodiment, the processing unit 220 can generate the WAP database 212 and the WAP map 112 utilizing access owner input who may each add their respective WAP(s) 104. Upon the user entering the geofence, the processing unit 220 may automatically connect the user device 106 to the WAP 104 (block 910). The generation module 228 of the processing unit 220 can generate a streamlined common business user interface 800 (block 912). The interface is common or uniform in that it displays the same UI configuration for all businesses, allowing the users to easily identify the business’s information and input information themselves. The processing unit 220 may populate the common business user interface with the information of the relevant business (block 914). For instance, the processing unit 220 may populate the business user interface 800 upon the user connecting to the WAP 104 of the business. Alternatively, the processing unit 220 may populate the business user interface 800 upon the user selecting the desired business in the WAP map 112, allowing the user to easily and efficiently search for community and business information. The processing unit 220 can further prompt the user device 106 to display the business user interface 800 (block 916). The processing unit 220 may also generate a variable user incentive which is based on the user data and owner data (block 918). The incentive can be a digital asset, such as a digital award, a digital coupon card, a platform NFT, a business specific NFT, a discount code, a referral link for other users, or other award.

[0061] The processing unit 220 can also generate one or more overlays 710, 810, 850, 860 that can be displayed on the WAP map 112 and/or the business user interface 800 (block 920). In one embodiment, the processing unit 220 can generate an incentive overlay 710, 810 which can be in the form of an icon, a video, or a digital asset itself, such as an NFT, that is overlayed onto the display. Optionally, in another embodiment, the processing unit 220 can generate a business notification overlay or popup 850 which can relay to the user information about the goods and/or services of the business. For example, the processing unit 220 may query the business to and accordingly receive business data, which may indicate a special offering, a deal, or a limited supply, among other information. The business information displayed in the overlay 850 may not be related to the generated incentives. Optionally, in another embodiment, the processing unit 220 can generate a user status overlay 860 that can be displayed on the business user interface 800 and/or the WAP map 112, which informs the user of their status in relation to a business or group of businesses associated with one or more WAPs 104. The user status overlay 860 can be generated in real time by the processing unit 220 and may be based on the user data, business data, and/or the generated incentives. For example, the user status can be a tiered status, such as a silver, gold, or platinum status, based on the user’s interaction with the business or a categorical representation. For example, the user status can indicate that a user in a top percentage of users, such as the top 1 percent, 2 percent, or 10 percent, etc. The grouping can be based on how frequent one or more users visit the business or grouping of businesses, such as how many consecutive visits in a given time period, e.g., day, week, month, etc., an expenditure amount within a given time period, a number of particular items purchased, how many incentives used or awarded, such as a digital asset, a duration of time spent at the business, and/or a user inputted request to join a particular status. Therein, as the business develops more user traffic it may be more difficult for a given user to achieve a certain status, thereby incentivizing the given user to visit the business more frequently to achieve or maintain their current status. Therewith, users may be incentivized to visit new or other businesses within the ecosystem to more easily earn various incentives, such as special deals, discounts, limited offers, etc.

[0062] After generating the overlays 710, 810, 860, the processing unit 220 can output one or more of the overlays 710, 810, 860 to the user device 106 so that it is displayed on the WAP map 112 and/or the business user interface 800 on the user device 106 (block 922). The processing unit 220 can then prompt the user to input user data, such as whether or not the user wishes to take advantage of the generated incentive, special offering, etc. (block 924). The user may also select certain user icons that are fixed at a particular position in each business user interface 800, such as a “hungry” or “thirsty” button 820, 822 within the business user interface 800. The user’s inputted data can include, but not limited to, the user’s desire for food or liquid, an emotional state, and/or communication state. Once the processing unit 220 receives the inputted user data, the processing unit 220 will repopulate the business user interface 800 and/or regenerate the incentive and the overlay(s) 710, 810, 850, 860 (block 926). Alternatively, the processing unit 220 may remove the overlay(s) 710, 810, 850, 860 if the user has used the incentive, the incentive has become expired, or had a change in status. For example, if the user selected an “I’m thirsty” button 822, the processing unit 220 can display only drink items on the menu and regenerate the incentive to apply to a drink. Therein, the processing unit 220 may further streamline the business’s information and the available generated incentives based on sensed user data, inputted user data, and/or business data. Hence, the user does not need to scroll through non-pertinent information, saving time, decreasing data transfer size, and decreasing battery usage.

[0063] Referring specifically to FIG. 8, the business user interface 800 may effectively replace business specific apps or other modes of communication. The business user interface 800 informs the user of various information associated with the access point owners. The generation module 228 may also integrate access point owner information into the interactive map 112. For example, the business user interface 800 may include a designated business name overlay 802 that displays the name of the business. The business user interface 800 may also include an information portal 804 to display a menu, an event schedule, or other information of the business. The business user interface 800 and/or the interactive map 112 may comprise an indisplay overlay or popup 810 that allows the user to quickly and efficiently see any available incentives, e.g. discounts or deals, or events associated with the access point owners. Additionally, the business user interface 800 may include one or more designated buttons 820, 822 for selecting a state or mood of the user. The buttons 820, 822 can be used to streamline information and specifically tailor the information displayed within the information portal 804. Optionally, the business user interface 800 can include a background display or underlay 830, which displays one or more photos or videos related to the business, the user, and/or the community group or current event. The underlay 830 allows the user to obtain information without distracting from the most pertinent information displayed in the overlays and information portal 804. Additionally, the business user interface 800 may include designated buttons 840, 842 to view the WAP map 112 and the user’s profile.

[0064] The business user interface 800 significantly reduces the time it takes for a user to review and understand a business’s offerings. Furthermore, the business user interface 800 increases the efficiency reduces the overall amount of data being transferred, lag time, and energy needed to display non-pertinent information; thus, increasing the quality of life of the user, decreasing computational cost, and augmenting the battery life of the device 106.

[0065] The processing unit 220 also validates the system 100 with one or more incentivized validation protocols. For example, the processing unit 220 may conduct a multistaged validation protocol to identify and verify the WAP 104. The validation protocol can include the validation of the WAP 104 based upon WAP characteristics, such as its ownership, location, connection speed, profile, and other characteristics, the validation of the WAP 104 based upon user data, the validation of the WAP 104 based upon verification data inputted by one or more users, and/or the validation of the user who uses the WAP 104 and/or inputs verification data associated with the WAP 104.

[0066] The validation protocol may include a first validation procedure wherein the processing unit 220 verifies user information. The processing unit 220 may verify that the user owns the NFT(s) which is being identified and used by the user. The processing unit 220 may verify the NFT’s identifying characteristics, such as a number sequence and/or mint date.

[0067] The validation protocol may include a second validation procedure wherein the processing unit 220 checks that a WAP 104 is viable, checks the location and ownership of the WAP 104, for example via Google Places API, checks the location of the user, and verifies that the user is at the location of the WAP 104 which the user has added to the WAP database. [0068] The validation protocol may include a third validation procedure wherein the processing unit 220 checks the time at which the user adds a WAP 104 and a distance between subsequently added WAPs 104. This ensures that the user is physically traveling to each new WAP 104 added to the WAP database. The processing unit 220 may calculate whether the user is spoofing their location, for instance by checking a distance and an estimated time of travel between subsequent WAPs 104 and the user’s timeframe in adding subsequent WAPs 104 and determining that the user added the subsequent WAP 104 in an unreasonable amount of time. If the processing unit 220 determines that the user has spoofed their location, then the processing unit 220 may prevent the addition of the WAP 104 or delay the addition thereof. The processing unit 220 may also penalize the user or block the user from adding other WAPs 104.

[0069] The processing unit 220 may conduct a fourth validation procedure wherein the processing unit 220 queues a newly added WAP 104 for validation by another user. By way of example only, user 1 (“contributor”) may pair a WAP 104 with a publicly accessible place of business, and this WAP 104 may be automatically added to the WAP database and be listed to other users, for example user 2 (“validator”), to verify the newly added WAP 104 based upon location data of user 1 and 2, activity recognition, and connectivity APIs. If user 1 identifies a WAP 104, then the processing unit 220 may wait to add the WAP 104 to the map 112 until user 2 also accesses the WAP 104 and verifies its viability. The processing unit 220 will also verify the location of user 2 and the WAP 104 which user 2 is presently verifying. Once verified, the processing unit 220 will add the WAP 104 to the map 112. Connecting to a WAP 104 proves that the information stored in the memory 210 is correct and that the users in question are indeed at the location of the WAP 104. This latter proof allows the map 112 to show user avatars alongside other nearby users. Users can then see which establishment other nearby users are located at and when they checked in. If a user wishes to communicate with another user, the user may contact the other user via the communication system(s) of the system 100.

[0070] The processing unit 220 may conduct a fifth validation procedure wherein properties of the WAP 104 are securely stored as an additional check to detect spoofing. The processing unit 220 may determine and validate WAP location, upload and download speed, usage rates, and ranges.

[0071] Therein, the ecosystem server 200 relies on multiple proof mechanisms that reward good users and punish nefarious users. The processing unit 220 relies on existing network protocols, e.g., 802.11, TCP/IP, HTTPS, mobile smartphone hardware, e.g., GPS chips, Wi-Fi® chips, and mobile provider APIs for geolocation, device integrity, connectivity, and authentication. The ecosystem server 200 may also utilize device attestation and integrity services, e.g., Google Play Integrity, DeviceCheck, to detect modified copies of data. For example, the system 100 may detect modified copies of the application 110 which may be attempting to communicate with the server 200.

[0072] The processing unit 220 may also conduct a multi-staged validation protocol to verify communication and/or meetups between users. The processing unit 220 can utilize proof of connection to validate social connections. The communication platform verifies the location of users and their proximity to one another before enabling proximity -based conversations. Another communication platform, for example a real world meetup platform, utilizes user location data, WAP data, and user activity to validate meetup attendance, be it in the physical and/or virtual world.

[0073] The processing unit 220 may also conduct a multi-staged incentivization protocol to incentivize users to add new WAPs, communicate with one another, obtain NFTs, and keep using the application 110. The incentives may be web2 and/or web3 incentives. The incentives, e.g., awarded achievements and collectibles, may be earned by participating in proof-of- connection activities. The incentives may include but not limited to achievements, payments such as a token associated with the system 100, a crypto currency, an NFT related or unrelated to the system 100, custom avatars, avatar apparel, leaderboard status, and/or in-store credits, discounts, or awards specific to one or more businesses of a WAP 104 or group of WAPs 104. For example, the processing unit 220 may generate digital assets associated with the ecosystem platform and/or owner-specific digital assets, such as NFTs, associated with the access point owners and award such digital assets to the users upon assisting in the completion of certain verification protocols, attending events, and/or purchasing items at the business of the access point owners and/or partner access point owners.

[0074] Achievements may include basic, advanced, city, unique, fun, and/or early adopter achievements. Basic achievements include one or more tutorials on participating in the ecosystem. Other basic achievements may include adding new WAPs 104, starting a chat with a local or digital community member, and attending an in-person or virtual meetup. New categories of achievements unlock once the user has completed the minimum set of basic achievements. Early adopter achievements may be reserved only for the very first users of the system 100. City achievements showcase different cultures, landmarks, and establishments that give every city life. Holders of these achievements will help the system 100 generate a global ambassador program. Once a user is listed as an ambassador, the user can create new cityspecific achievements for other users to achieve. Unique, seasonal, and fun achievements may also be included. One example of a fun achievement is a “Coast-to-Coasf ’ achievement, which users achieve by validating two WAPs 104, each within 5km of the westernmost and easternmost points of the continental United States. New achievements can be submitted and approved by thoughtful contributions from the users. Hidden achievements not publicly advertised may also be included. Seasonal “scavenger hunts” achievements may also be included.

[0075] By way of example only and specifically referring now specifically to FIG. 10, there is shown a verification method 1000. In operation, the processing unit 220 can initially generate the WAP database 212 and the WAP map 112 (block 1002). The processing unit 220 can also generate an initial WAP profile (at block 1004). The WAP profile can comprise inputted, sensed, and generated characteristics of the WAP 104. For example, an initial WAP profile can comprise a generated geofence, generated by the processing unit 220, based on a known boundary line of the building, including its walls, floors, and ceilings, retrieved from a third party database.

[0076] The processing unit 220 can generate a preliminary WAP verification status (block 1006). The preliminary WAP verification status can comprise a status of whether or not the WAP 104 is associated with a particular business and in good working order. Therein, the processing unit 220 can create a confidence score on the likelihood the WAP 104 is viable and housed within a given building.

[0077] Thereafter, the processing unit 220 can verify the WAP and generate a WAP verification status, utilizing a neural network and/or user input from two or more users. To verify the WAP 104 utilizing the user input, the processing unit 220 may initially prompt a first user to input WAP data associated with a given WAP 104 (block 1008). Such data can include the name of the business, the name of the WAP 104, and/or the password of the WAP 104. Once a successful connection is determined, the processing unit 220 verify that WAP 104 is operational and generate a WAP verification status, such as active and unverified by a subsequent user (block 1010). As an added layer of protection and accuracy, the processing unit 220 may prompt a second user to input WAP data associated with the WAP 104 added by the first user (block 1012). The processing unit 220 can determine whether the second user inputted the same data as the first user, e.g., the passwords match, and is successfully connected to the WAP 104. Thereafter, the processing unit 220 can generate a user-based preliminary verification status based on the owner data and the inputted WAP data from the first and second users. The processing unit 220 may then generate a WAP verification status based on the preliminary userbased preliminary verification status. If and when a prior verification status was previously generated, based on user input and/or the neural network, the processing unit may regenerate the verification status to accordingly provide an updated verification status (block 1014). [0078] Optionally, the processing unit 220 may also prompt the first user and/or the second user to provide user feedback on the efficacy of the WAP 104. For example, if the WAP 104 has a strict firewall, then the processing unit 220 would likely generate a verified status as both first and second users would technically have provided the same information and be successfully connected to the WAP 104; however, the usability of the WAP 104 may be undesirably low due to the firewall. Thereby, the processing unit 220 may alter the verification status based on user feedback if the user indicates that the WAP 104 is practically unusable due to its firewall.

[0079] If the WAP 104 is verified, the processing unit 220 can add the WAP 104 to the WAP database 212 and update the WAP map 112 to indicate that the WAP 104 is verified and in good working condition (block 1016). If the WAP 104 is not verified, the processing unit 220 may prompt a third user to input WAP data associated with the WAP 104 in question (block 1018). The processing unit 220 will compare the inputted WAP data from the first, second, and third users and check for any dissimilarities. If the inputted WAP data all matches, then the processing unit 220 may determine an unverified status and shadow ban the WAP 104. If the inputted WAP data is dissimilar, then the processing unit 220 may prompt a fourth user to input WAP data and recalculate the accuracy of the inputted information. If the WAP data is dissimilar, the processing unit 220 may generate a probability verification status, indicative of a high or low likelihood efficacy, or a final unverified status output signal and communicate such to the access point owner so that they may remedy any issue with their WAP 104. Accordingly, the unverified WAP 104 can be removed from the WAP database 212. [0080] Additionally or alternatively to the user-based verification protocol, the processing unit 220 may generate the preliminary verification status via a neural network (block 1006). For example, the processing unit 220 may comprise a machine learning module that conducts a string similarity calculation using a machine learning algorithm. The neural network can include a training algorithm that was trained on identifying a dataset of previously verified WAPs. For example, the training data can comprise business names and names of wireless networks which match with one another, and the algorithm will identify the similarities in the names with natural language processing to ultimately generate a confidence score that the WAP 104 corresponds to a particular business based on the name similarity. Additionally, the training data can comprise business property lines, building dimensions, and RF signal strengths of the WAP 104 to train the neural network to identify progressively weaker RF signals with building dimension and/or property line limits. Hence, the neural network can determine a verified confidence score of the WAP 104 by conducting a string similarity calculation using the machine learning algorithm. The neural network can also generate a preliminary Al-based verification status based upon the verified confidence score. The processing unit 220 can then generate a WAP verification status that is based on the preliminary Al-based preliminary verification status (block 1010). If the WAP does not have a password, then the processing unit 220 may begin automatically connecting users to the WAP 104 upon detecting the users have entered the determined geofence of the WAP 104.

[0081] After adding a WAP 104 to the WAP database 212, the processing unit 220 may monitor the WAP 104 and determine the efficacy, e.g., usability, of a WAP 104 (block 1020). The efficacy score can be a measure of RF signal strength, connectivity speeds, and/or traffic patterns, ranging from unusable, poor, average, to great. The processing unit 220 can generate the WAP efficacy score based on sensed WAP data and/or user inputted WAP data.

[0082] The processing unit 220 can initially determine an efficacy threshold of the WAP 104. The efficacy threshold can be a predetermined minimum connectivity speed. Alternatively, the efficacy threshold can be a comparative value based upon comparing competing WAPs 104. For instance, the processing unit 220 can determine which WAP 104 has the strongest signal and fastest speeds and accordingly rank the competing WAPs 104 from best to worst. The processing unit 220 may then identify that a WAP 104, which is ranked in the middle, constitutes the efficacy threshold. To monitor the WAP 104, the processing unit 220 can track the ease of connectivity, the upload or download speed, the average time connected to the WAP 104, and RF signal strength.

[0083] In continuing the protocol, the processing unit 220 can generate additional or subsequent WAP profiles (block 1022) and automatically connect subsequent users to these WAPs 104 (block 1024). For each WAP 104, the processing unit 220 can generate an efficacy score. If in the event the processing unit 220 determines that a WAP 104 is below the efficacy threshold, then the processing unit 220 can remove the WAP 104 from the WAP database 212 (block 1026). The processing unit 220 may also conduct a decay or loss analysis, wherein the processing unit 220 may remove, or change the verification status of, certain WAPs 104. For instance, the processing unit 220 can determine a duration of inactivity of a WAP 104, and if the inactivity duration is below a preset duration, then the processing unit 220 may change a green, verified status to a yellow, unverified status or alternatively may remove the WAP 104 from the WAP database 212.

[0084] Where there are multiple, competing WAPs 104, either in a relatively close geographical region or within the same building or building complex, the processing unit 220 may monitor and generate efficacy scores for each WAP 104. The processing unit 220 may compare the WAP efficacy scores and accordingly rank the WAPs. The processing unit 220 can prioritize the WAPs based on their efficacy scores for preferentially connecting the user device to whichever WAP has a higher ranking.

[0085] Referring now collectively to FIGS. 7 and 10, when generating a WAP profile of a given WAP 104, the processing unit 220 may dynamically generate a geofence of the WAP 104. Initially, the processing unit 220 can generate an estimated geofence GP based on a proximity ring centered on a center point of a building or at a known location of a router. Therein, the processing unit 220 can determine the center point of a building and estimate the geofence of the WAP 104 to be approximately a circular perimeter of 50-150 ft (15-45 m) therearound. The processing unit 220 can also determine a dynamic geofence of the WAP 104, wherein the processing unit 220 determines the property lines and dimensions of the building on the property, which it may obtain from a third party database. From map data, the processing unit will then determine the building density, e.g., whether the building is in a city block or distanced from juxtaposed businesses. Thereafter, the processing unit 220 will generate the dynamic geofence GD which will range between the property line, an arbitrary set maximum, and an approximate center point of the building or location of the router, an arbitrary set minimum, depending upon adjacent buildings and/or adjacent WAPs 104. The processing unit 220 can also adjust the dynamic geofence GD to identify patios and outdoor seating environments within the property lines but outside of the building itself.

[0086] Therewith, the processing unit 220 can generate a dynamic geofence by additionally monitoring the RF signal strength. For instance, the Al processor 222 may incorporate building data, WAP characteristics, and/or user activity to determine the dynamic geofence GD. The Al processor 222 may determine the RF strength of the WAP 104 by logging the RF signal strength and connectivity speed between the user devices 106 and the WAP 104 and also the locations of the user devices 106. After determining where the weakest and slowest points are, the processing unit 220 will remove those regions from the geofence, resulting in a dynamic geofence based at least in part upon on RF signal strength of the WAP 104. Such a dynamic geofence can be especially useful when there are multiple WAPs 104 in a single building, such as an airport. The processing unit 220 can accordingly connect the users to the more suitable WAP 104 based on the dynamic geofence GD. For example, even though there may exist overlap between the WAPs 104 and even though the user device 106 may be physically closer to a less suitable WAP 104, the processing unit 220 can connect the user device 106 to the most connected to WAP 104, the WAP 104 with the highest connectivity success rate, and/or the WAP 104 with the greatest RF strength and/or speed.

[0087] The dynamic geofence GD is more accurate than the estimated, proximity based geofence GP. As can be appreciated, in densely populated cities, the dynamic geofence GD is preferred and will save on computations and battery as the processing unit 220 will not try to connect a user device 106 as the user walks by a building but will connect the user device 106 when the user enters the building and gets closer to the location of the router of the WAP 104. [0088] Referring now to FIGS. 11-12, the processing unit 220 can infinitely cache the ecosystem such that the users may be automatically connected to wireless internet wherever they travel, whether or not they are online, as the infinitely cached grouping of WAPs is stored in the memory of their user devices 106. FIG. 11 illustrates a schematic of an infinite caching system 1100. FIG. 12 illustrates a flowchart of a method 1200 for infinitely caching the most pertinent WAPs 104 on the user device 106. [0089] One reoccurring issue with user devices 106 is memory or storage space, which in turn limits the total number of cached WAPs 104 saved on a phone. Another reoccurring issue with user devices 106 is energy consumption depleting battery life, which in relation to caches effectively limits the number of times of user device 106 can connect to various WAPs 104. Another issue arises from offline usage, wherein if the user is not connected to the internet, the user device 106 cannot display the WAP map 112. The infinite caching system 1100 pregenerates groupings of WAPs 104, and similarly to a funnel, sifts through the various possible WAPs 104 and allows only the most pertinent WAPs 104 to be cached on the user device 106, saving storage space and decreasing energy consumption as non-pertinent WAPs 104 are effectively ignored. Additionally, the processing unit 220 can predictively and automatically save various data on the user device 106 for offline usage, such as portions of the WAP map 112, communication data, and business data associated with multiple different business in a given region of the WAP map 112. As a further benefit, the infinite caching system 1100 speeds up the query or synchronization process when connecting the user device 106 to a WAP 104 because the such data has been already cached in the user device 104 before the user has traveled to the location of the WAP 104.

[0090] The processing unit 220 may initially generate the WAP database 212 and the WAP map 112, as discussed above (block 1202). The processing unit 220 can obtain user location and travel data, as discussed above (block 1204). Therein, the processing unit 220 may not decide to conduct the method 1200 if the user is not walking or in a still state, effectively pausing the auto-connect capability to conserve battery life. The processing unit 220 can determine the location and travel state of the user, as discussed above (block 1206). Out of all the WAPs 104 in the WAP database 212, the processing unit 220 can generate a hierarchy of groupings of WAPs 104 which ranging from least to most pertinent. The processing unit 220 can group the WAPs 104 by geographical region, frequency of connectivity to the user device 106, relevancy, recency, user data, WAP data, type of access point owner, generated efficacy score, and/or generated WAP profile.

[0091] The processing unit 220 may generate a first, intermediate WAP grouping IG that is based upon a common geographical region associated with the particular user device 106, such as a state, city, or region wherein the user presently resides (block 1208). From the intermediate WAP grouping IG, the processing unit 220 can generate two or more sub WAP groupings SG, e.g., SG1 -SG4, composed of WAPs 104 that are more pertinent, (block 1210). The sub WAP groupings can be based upon the intermediate WAP grouping IG, WAP data, and user data, such as past connectivity data, the user location data, user travel data, and/or user interests.

[0092] The processing unit 220 can then generate a cache grouping CG based upon the two or more sub WAP groupings and the user data (1212). The cache grouping CG can be composed of only one or multiple WAPs 104, such as 1, 20, 40, or 100 WAPs 104. The processing unit 220 can also prioritize WAPs 104 by frequency of use. Thereby, processing unit 220 may always include one or more WAPs 104 in the cache grouping CG, which the user frequently uses, like the WAP 104 of their home address or favorite coffee shop. The processing unit 220 can then store the cache grouping CG on the user device 106 (1214).

[0093] Optionally, the processing unit 220 can predictively remove one or more WAPs 104 in the cache grouping CG stored on the user device 106 (block 1216). For example, if the processing unit 220 detects that the user is about to or already has traveled to a different region or a different country, then the processing unit will uncache the cache grouping CG from the user device 106. Alternatively, the processing unit 220 may not remove the WAPs unless and until a new grouping has been determined.

[0094] Additionally, as an optional step, the processing unit 220 can prompt the user to input user data indicative of any travel plans or schedule (block 1218). The prompt can be contingent on the user leaving or entering certain regions or geofences. For example, if the user travels out of a known proximity, such as a certain radius from their home or most connected to WAP 104; then, the processing unit 220 may prompt the user to input their travel plans. Additionally, for example, if the processing unit 220 detects that the user has entered the geofence of an airport, the processing unit may request that the user input their travel plans or an end destination to precache the desired WAPs 104.

[0095] Upon storing the cache grouping CG, the processing unit 220 can automatically save map data for offline usage, if and when the processing unit 220 determines that the user has traveled outside of a most frequented geofence, inputted travel or event data, and/or entered a certain geofence of a WAP 104, such as a transportation hub, e.g., international airport, train station, etc. Thereby, downloading data for offline usage can be contingent on the presently generated cache grouping CG. [0096] As the user travels, the processing unit 220 can regenerate one or more of the WAP groupings IG, SG, CG, based at least in part upon the user location and user travel data (block 1220). For example, the processing unit 220 can regenerate the sub WAP groupings SG and also regenerate the cache grouping CG based on the regenerated sub WAP groupings SG. The regenerated cache grouping CG is different from the previously stored cache grouping CG. Thereafter, the processing unit can update the previously stored cache grouping CG with the regenerated cache grouping CG (block 1222).

[0097] The method steps described herein of the various methods can be performed in any desired order, and thereby the embodiments of the methods are not limited to what has been shown and described herein. Other embodiments, which differ from the aforementioned embodiments, may be recognized by those skilled in the art without departing from the disclosure and the claims.