Systems and methods for controlling network access

Disclosed are various embodiments for systems and methods for controlling access of networks. In one embodiment, an access control service receives requests to access network beacons from client devices. In response, the access control service determines whether the client devices satisfy authorization rules associated with the network beacons. If the access control service determines that the client devices satisfy the authorization rules associated with the network beacons, the access control service authorizes the client devices to access the network beacons. Subsequently, if the client devices cease to satisfy the authorization rules associated with the network beacons, the access control service terminates the authorization of the client devices to access the network beacons.

FIELD OF THE INVENTION

Embodiments of the disclosure relate generally to data security, and more particularly, to systems and methods for controlling network access.

BACKGROUND

Controlling network access is critical to ensure that only authorized client devices may gain access to sensitive information. To date, enterprises have utilized access lists to control which, if any, client devices may access networks. This method may control network access when the group of client devices that are authorized to access the network seldom fluctuates. However, this method is inadequate to control network access when the group of client devices that are authorized to access the network often fluctuates.

The group of client devices that are authorized to access a network seldom fluctuates when there is a non-transient relationship between a network and the client devices seeking access to the network. For example, a non-transient relationship may exist between a network and client devices where there is an employee-employer relationship between a network and the client devices seeking access to the network. On the contrary, the group of client devices that are authorized to access the network often fluctuates when there is a transient relationship between a network and client devices seeking access to the network. A transient relationship may exist between a network and client devices, for instance, where there is a service provider-customer relationship between a network and the client devices seeking access to the network. As many service providers wish to provide network access for their customers, systems and methods for controlling access to such networks are necessary to ensure that only authorized client devices may gain access to sensitive information.

BRIEF SUMMARY

Some or all of the above needs and/or problems may be addressed by certain embodiments of the disclosure. Certain embodiments may include systems and methods for controlling access to networks. According to one embodiment of the disclosure, there is disclosed a system. The system can include a memory that stores computer-executable instructions. The system can also include a processor configured to access the at least one memory. The processor is configured to execute the computer-executable instructions to perform a method including the steps of receiving one or more requests to access one or more network beacons from one or more client devices, determining whether the client devices satisfy one or more authorization rules associated with the network beacons, authorizing the client devices to access the network beacons in response to a determination that the client devices satisfy the authorization rules associated with the network beacons, and terminating the authorization of the client devices to access the network beacons if the client devices no longer satisfy the authorization rules associated with the network beacons.

According to another embodiment of the disclosure, there is disclosed a method. The method can include transmitting one or more requests to access one or more network beacons from one or more devices, receiving one or more resources associated with the network beacons on the client devices, and accessing the network beacons from the client devices.

Further, according to another embodiment of the disclosure, there is disclosed a non-transitory computer-readable medium embodying a program executable in a computing device, the program comprising code that, when executed by a computing device, causes the computing device to perform a method comprising the steps of identifying one or more client devices located within one or more transmission ranges of one or more network beacons, determining whether the client devices satisfy one or more authorization rules associated with the network beacons, and transmitting one or more resources associated with the network beacons to the client devices in response to a determination that the client devices satisfy the authorization rules associated with the network beacons.

Other embodiments, systems, methods, apparatus aspects, and features of the disclosure will become apparent to those skilled in the art from the following detailed description, the accompanying drawings, and the appended claims.

DETAILED DESCRIPTION

Illustrative embodiments of the disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the disclosure are shown. The disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. As noted above, like numbers refer to like elements throughout.

Illustrative embodiments of the disclosure are directed to, among other things, controlling access to networks. As an overview, access to networks may be controlled by limiting access to network beacons associated with a network to client devices that satisfy one or more authorization rules. In particular, the network beacons may include, for example, Wi-Fi beacons, cellular beacons, satellite beacons, Bluetooth beacons, radio beacons, and/or other beacons capable of transmitting data from a network to client devices. In certain embodiments, an access control service executed by an access control server may authorize one or more client devices that satisfy the authorization rules to access the network beacons.

The technical effects of certain embodiments of the disclosure may include establishing control of access to networks when access lists may not be predefined, and reducing and/or eliminating the burden of predefining access lists to control access to networks. Moreover, the technical effects of certain embodiments of the invention may include enhancing network access control by assigning specific access rights based on access lists to client devices120authorized to access the associated network beacons.

FIG. 1depicts certain illustrative components for a networked environment100according to various embodiments. The networked environment100may include a network110, a client device120, and an access control server150. The network110may be or include, for example, any type of wireless network such as a wireless local area network (WLAN), a wireless wide area network (WWAN), or any other type of wireless network now known or later developed. Additionally, the network110may be or include the Internet, intranets, extranets, microwave networks, satellite communications, cellular systems, PCS, infrared communications, global area networks, or other suitable networks, etc., or any combination of two or more such networks. In one embodiment, the network110facilitates transmission of resources165between one or more client devices120and an access control server150.

The client device120may comprise, for example, a cellular telephone, a smartphone and/or personal digital assistant, a tablet computer and/or web pad, a laptop computer, a desktop computer, a set-top box, a music player, a game console, and/or another device with like capability. For purposes of convenience, the client device120is referred to herein in the singular. Even though the client device120is referred to in the singular, it is understood that one or more client devices120may be employed in the arrangements as descried herein.

The client device120may include a wired network connectivity component (not shown inFIG. 1), for example, an Ethernet network adapter, a modem, and/or the like. The client device120may further include a wireless network connectivity interface (not shown inFIG. 1), for example, a PCI (Peripheral Component Interconnect) card, USB (Universal Serial Bus) interface, PCMCIA (Personal Computer Memory Card International Association) card, SDIO (Secure Digital Input-Output) card, NewCard, Cardbus, a modem, a wireless radio transceiver, and/or the like. The client device120is operable to communicate via wired connection with the access control server150with the aid of the wired network connectivity component. The client device120is further operable to communicate wirelessly with the access control server150with the aid of the wireless network connectivity component.

The client device120may comprise a memory for storing data and applications, a processor for executing applications stored in memory, a display136upon which the processor may execute one or more user interfaces137, and a local interface such as a bus, as will be described with respect toFIG. 5. The memory of the client device120may comprise a data store122. The data store122of the client device120may include a device profile123. In one embodiment, the device profile123may represent hardware, software, and security attributes that describe the client device120. For instance, the device profile123may represent hardware specifications of the client device120, version and configuration information of various software programs and hardware components installed on the client device120, transport protocols enabled on the client device120, version and usage information of various other resources stored on the client device120, and/or any other attributes associated with the state of the client device120. In another embodiment, the device profile123may further include characteristics describing the current state of the client device120, including indications of the location of the client device120, the current time associated with the client device120, the client device's120detection of one or more network beacons associated with one or more networks110, and the signal strength of the network beacons received by the client device120. In yet another embodiment, the device profile123may include data indicating a date of a last virus scan of the client device120, a date of a last access and/or service by an IT representative, a date of a last access by the access control service174, and/or any other data indicating a date of last maintenance of the client device120.

Additionally, the data store122of the client device120may include one or more user identifiers132. The user identifiers132may uniquely identify the user of the client device120. In one embodiment, the user identifiers132may include a username, a password, and/or biometric data related to facial recognition, retina recognition, fingerprint recognition, and the like. Similarly, the data store122of the client device120may include one or more device identifiers135. The device identifiers132may uniquely identify the client device120. In one embodiment, the device identifiers135may be a unique hardware identifier such as a GUID (Globally Unique Identifier), UUID (Universally Unique Identifier), UDID (Unique Device Identifier), serial number, IMEI (Internationally Mobile Equipment Identity), Wi-Fi MAC (Media Access Control) address, Bluetooth MAC address, a CPU ID, and/or the like, or any combination of two or more such hardware identifiers. In another embodiment, the device identifier135may be a unique software identifier such a token or certificate, based at least in part on the aforementioned unique hardware identifiers.

The client device120may be configured to execute various applications. For example, the client device120may be configured to execute applications such as containerized content applications, web browsing applications, email applications, instant messaging applications, word processing applications and/or other applications capable of receiving and/or rendering resources165on a display136associated with the client device120. Any application capable of receiving and/or rendering resources165on a display136of the client device120is generally referred to herein as a “client side application”126. The client side application126may be stored in the memory of the client device120. In one embodiment, the client side application126may be a containerized application that may be authorized to receive and render resources165in accordance with one or more resource rules171, as described herein. The client side application126may include a decryption key to decrypt resources165encrypted with an encryption key in order to prevent unauthorized access to the resources165. For instance, the client side application126may have a decryption key associated with an access control service174that may be used to decrypt resources165transmitted in an encrypted format to the client device120by the access control service174.

The client side application126may be executed to transmit one or more requests177to access one or more network beacons associated with the network110. In certain embodiments, the client side application126may transmit access requests177to an access control service174executed by an access control server150associated with the network beacons. In some embodiments, the client device120may be permitted to temporarily access the network beacons in order to transmit a request177to persistently access the network beacons. In particular, the client side application126may be permitted to render a web-based form via a user interface137that allows a user of the client device120to input one or more user identifiers132in order to compile a request177to persistently access the network beacons. In one embodiment, the request177may include the device profile123from the data store122of the client device120. In another embodiment, the request177may include user identifiers132from the data store122of the client device120. In yet another embodiment, the request177may include device identifiers135from the data store122of the client device120.

The client side application126may be further executed to receive an indication that the client device120is authorized to access the network beacons associated with the network110. In certain embodiments, the client side application126may receive an authorization indication from an access control service174executed by an access control server150associated with the network beacons. In one embodiment, the authorization indication may specify that the client device120is authorized to access the network beacons while the client device120is located within an authorized range of the network beacons. In particular, the authorized ranges associated with the network beacons may include one or more bounded physical areas where a client device120may be located within to access the network beacons, one or more ranges of IP addresses that may access the network beacons, one or more ranges of Wi-Fi SSID's that may access the network beacons, one or more ranges of client device120MAC addresses that may access the network beacons, one or more ranges of default gateway addresses and/or public internet addresses that may access the network beacons, one or more ranges of potential network beacon transmission associated with the network beacons, and one or more ranges of acceptable network beacon signal strength levels that may access the network beacons.

In another embodiment, the authorization indication may specify that the client device120is authorized to access the network beacons while one or more resources165associated with the network beacons are present on the client device120. For instance, the resources165associated with the network beacons may individually and/or collectively form a key that may unlock access to the network110while the resources165are present on the client device120. In yet another embodiment, the authorization indication may specify that the client device120is authorized to access specific domains and/or services provided via the network beacons based at least in part on one or more of the device profile123, user identifiers132, and device identifiers135associated with the client device120.

The client side application126may be further executed to receive one or more resources165. In certain embodiments, the client side application126may be configured to receive resources165associated with the network beacons if the client device120is located within an authorized range of the network beacons associated with the network110. In some embodiments, the client side application126may receive resources165that individually and/or collectively form a key that may unlock access to network beacons while the resources165are present on the client device120. In one embodiment, the client side application126may receive the resources165from an access control service174and/or another service executed by an access control server150. In another embodiment, the client side application126may receive the resources165from a distribution service associated with the network110according to a distribution approach as described in application Ser. Nos. 13/396,356 and 13/623,627 both entitled “CONTROLLING DISTRIBUTION OF RESOURCES ON A NETWORK,” which are incorporated herein by reference in their entirety.

In any instance, the resources165may include various types of electronic data that may be associated with the network110, such as settings, applications, and content. In one embodiment, settings-type resources165may include hardware settings, software settings, and/or the like that configure the functionality provided by the client device120. In another embodiment, application-type resources165may include book applications, business applications, catalogue applications, education applications, entertainment applications, finance applications, food and drink applications, games applications, health and fitness applications, lifestyle applications, medical applications, music applications, navigation applications, news applications, newsstand applications, photo and video applications, productivity applications, reference applications, social networking applications, sports applications, travel applications, utility applications, weather applications, and/or the like. In yet another embodiment, content-type resources165may include application content, video content, image content, audio content, text content, word processor content, presentation content, spreadsheet content, database content, compressed folder content, disk image content, encoded content, backup content, web content, page layout content, plug-in content, font content, system content, developer content, data content and/or the like.

Additionally, the resources165may include one or more resource rules171. In certain embodiments, the resource rules171may describe and/or regulate the use of the resources165. In one embodiment, the resources rules171may specify that the resources165may only be accessed by authorized and/or secure applications on the client device, such as the client side application126. In another embodiment, the resource rules171may specify that the resources165may not be cut, copied, pasted, transmitted, text messaged, emailed, printed, screen captured, and/or manipulated. In yet another embodiment, the resource rules171may specify that the resources165are encrypted and may specify that one or more authorized and/or secure applications on the client device120have an appropriate decryption key to unlock the resources165, such as the client side application126. Additionally, the resource rules171may specify whether the resources165may be rendered while the client device120is offline and/or not in communication with the access control service174, whether to permit synchronization of the resources165with a remote data store, whether to permit storing resources165locally on the client device120, and whether the resources165may only be accessed at certain locations and/or times.

In other embodiments, the resource rules171may be metadata and/or other indications that describe the resources165. In particular, the resources rules171may specify categories/sub-categories to which the resources165belong, that the resources165are considered favorites, the ownership of the resources165, the managing party of the resources165, that the resources165are confidential, that the resources165are password protected, that historical version of the resources165, one or more descriptions of the resources165, one or more comments regarding the resources165, the size and format of the resources165, the download priority associated with the resources165, an expiration date associated with the resources165, one or more effective dates associated with the resources165, and/or the like.

In some embodiments, the resource rules171associated with the resources165may change based on the state of the client device120. In certain embodiments, the stringency of the resource rules171may be increased, reduced, and/or eliminated based on the state of the client device120. In one embodiment, the stringency of the resource rules171may be increased, reduced, and/or eliminated if the client device120is located within the transmission range of certain network beacons. For example, the resource rules171may specify that the resources165require an 8-digit password to access the resources165if the client device120is not located within the transmission range of a specific network beacon, and the resource rules171may specify that the resources165only require a 4-digit password to access the resources165if the client device120is located within the transmission range of the specific network beacon. In another embodiment, the stringency of the resource rules171may be increased, reduced, and/or eliminated if the client device120is located within the transmission range of network beacons associated with a certain network. For example, the resource rules171may specify that the resources165require a 256-bit encryption if the client device120is not located within the transmission range of network beacons associated with a specific network, and the resource rules171may specify that the resources165only require 128-bit encryption if the client device120is located within the transmission range of network beacons associated with the specific network. In another embodiment, the stringency of the resource rules171may be increased, reduced, and/or eliminated if the client device120is located within the transmission range of certain network beacons associated with certain networks. For example, the resource rules171may not apply to a client device120that is not located within the transmission range of any unknown network beacons and/or is not located within the transmission range of any network beacons associated with unknown networks.

The client side application126may be yet further executed to access one or more resources165. In certain embodiments, the client side application126may access the resources165received from an access control service174and/or another distribution service. In some embodiments, the client side application126may access the resources165on the client device120in accordance with the resource rules171, as described herein. For example, the client side application126may determine that a given resource165may not be accessed on a client device120because the client device120is not located within an authorized location. In any instance, the client side application126may access the resources165on the client device120by installing, activating, and/or executing the resources165on the client device120. In one embodiment, the client side application126may access settings-type resources165by transmitting one or more associated settings files to the appropriate locations in the memory of the client device120, disabling and/or removing any conflicting settings files, and instructing the client device120to conform its operations to the settings-type resources165. In another embodiment, the client side application126may access application-type resources165by transmitting one or more associated application files to the appropriate locations in the memory of the client device120, disabling and/or removing any conflicting application files, and instructing the client device120to execute the application-type resources165.

In yet another embodiment, the client side application126may access content-type resources165by transmitting one or more associated content files to the appropriate locations in the memory of the client device120, disabling and/or removing any conflicting content files, and instructing the client device120to execute one or more applications on the client device120capable of rendering and/or presenting the content-type resources165to a user of the client device120. In particular, the client side application126may render and/or present the resources165in a user interface137by decompressing compressed files and presenting the uncompressed files, mounting disk image files and presenting the mounted image files, running executable files and presenting the executed files, by enabling a data search of the resources165and presenting the featured output in a user interface, by calling on another application on the client device120to respond to data links contained within the resources165, and/or by transmitting a part or the whole of the resources165to another application on the client device120. Additionally, the client side application126may render and/or present a single resource165or a series of resources165in a comprehensive manner, such as presenting image files in a slideshow-style presentation. Furthermore, the client side application126may render and/or present an environment that displays an array of resources165in a single view, such as a category-based tree or outline format.

Additionally, the client side application126may be a containerized application that is configured to protect one or more resources165associated with one or more network beacons from unauthorized access. In certain embodiments, the client side application126may protect resources that have been received from an access control service174and/or are accessible on the client device120. In one embodiment, the client side application126may be executed to identify metadata associated with the resources165and ensure that the resources165are accessed in accordance with the metadata. For instance, the client side application126may prohibit the cutting, copying, pasting, transmitting, emailing, text messaging, screen capturing, and/or otherwise manipulating the resources165while the resources165are being accessed. In another embodiment, the client side application126may prohibit other applications on the client device120and/or other services accessible to the client device120from accessing the resources165. In particular, the client side application126may monitor the data stream between the network110and the client device120, may block any access attempts by another application and/or service, may intercept the resources165, and may present the intercepted resource165in a user interface137rendered by the client side application126. In yet another embodiment, the client side application126may be executed to call on other services associated with the resources165that are executed on the access control server150or another server or device accessible to the client side application126, for instance, a technical support service that may be executed by the access control server150.

The access control server150may comprise, for example, a server computer or any other system providing access control capability. Alternatively, a plurality of access control servers150may be employed that are arranged, for example, in one or more server banks or computer banks or other arrangements. For example, a plurality of access control servers150together may comprise a cloud computing resource, a grid computing resource, and/or any other distributed computing arrangement. Such access control servers150may be located in a single installation or may be distributed among many different geographic locations. For purposes of convenience, the access control server150is referred to herein in the singular. Even though the access control server150is referred to in the singular, it is understood that a plurality of access control servers150may be employed in the arrangements as descried herein.

The access control server150may comprise a memory for storing data and applications and a processor for executing applications stored in memory, as will be described with respect toFIG. 5. The memory of the access control server150may comprise a data store153. The data store153may be representative of one or more data stores, as can be appreciated. The data store153may contain certain data that is accessible to the access control server150. In particular, the data store153may contain one or more authorization rules161, one or more resources165, and one or more resource rules171associated with the resources165, as described herein. The data in the data store153may be associated with the operation of certain applications and/or functionalities executed by the access control server150. The data store153may utilize strong encryption standards to protect the resources165from unauthorized access. For example, the data store153may utilize SHA-1 (Standard Hash Algorithm) or a similar strong encryption standard commonly utilized for server-side data storage.

The access control server150may execute certain applications and/or functionalities such the access control service174, as well as other applications, services, processes, systems, engines, or functionality not disclosed in detail herein. The access control service174may be executed to limit access to one or more network beacons associated with a network110. In particular, the access control service174may limit network beacon access to one or more client devices120that are authorized to access the network beacons associated with the network110. The access control service174may be further executed to distribute one or more resources165associated with the network beacons to one or more client devices120that are authorized to access the network beacons.

The access control service174may be executed to control access to one or more network beacons associated with a network110. In certain embodiments, the access control service174may limit authorization to access the network beacons to one or more client devices120that satisfy one or more authorization rules161associated with the network beacons. The authorization rules161may specify one or more required and/or permitted states that a client device120must satisfy in order for the client devices120to be authorized to access the network beacons. For example, the authorization rules161may include environment-related requirements, resource-related requirements, device-related requirements, and/or the like.

In one embodiment, the authorization rules161may include environment-related requirements that specify one or more locations where the client devices120may be authorized to access the network beacons and/or one or more times when the client devices120may be authorized to access the network beacons. For instance, the authorization rules161may specify that client devices120may be authorized to access the network beacons if the client devices120are located within one or more authorized locations associated with the network beacons. The authorized location may include a single location, a range of locations, and/or combinations thereof where the client devices120may be authorized to access the network beacons. Additionally, the authorization rules161may specify that the client devices120may be authorized to access the network beacons if the current times associated with the client devices120are within one or more authorized windows associated with the network beacons. The authorized windows may include a single time, a span of times, and/or combinations thereof when the client devices120may be authorized to access the network beacons.

In another embodiment, the authorization rules161may include resource-related requirements that specify that one or more resources165associated with the network beacons are required for the client devices120to be authorized to access the network beacons. In certain embodiments, the resources165associated with the network beacons may individually and/or collectively represent a key indicating that the client device120may be authorized to access the network beacons. In one embodiment, the resources165may represent a key while the resources165are accessed by the client devices120. In particular, the resources165may be accessed by the client devices120when the resources165are stored on, installed on, activated on, and/or executed by the client device120. In some embodiments, the authorization rules161may specify that the client devices120must further comply with one or more resource rules171associated with the resources165for the client devices120to access the resources165. For instance, the resource rules171associated with the resources165may specify that the resources165may be accessed by the client devices120while the client devices120are located within an authorized location.

In yet another embodiment, the authorization rules161may include device-related requirements that specify one or more hardware requirements, software requirements, configuration requirements, maintenance requirements, and/or the like must be satisfied by the client device120for the client device120to be authorized to access the network beacons. For example, device hardware requirements may include requirements associated with the CPU, memory, power supply, external storage, peripherals, and/or the like. Device software requirements may include requirements associated with the operating system type and version, operating system authenticity and jailbreak/rooted status, installed application types and versions, and/or the like. Device configuration requirements may include requirements associated with the configuration of the hardware, software, data encryption methods, transport protocols, and/or the like. Additionally, device maintenance requirements may include requirements associated with the date of last virus scan for the client device120, the date of the last access of the client device120by IT, the date of last communication between the client device120and the access control server150, the date of last tune-up of the client device120, and/or the like.

In some embodiments, the authorization rules161associated with the network beacons may change based on the state of the client device120. In certain embodiments, the stringency of the authorization rules161may be increased, reduced, and/or eliminated based on the state of the client device120. In one embodiment, the stringency of the authorization rules161may be increased, reduced, and/or eliminated if the client device120is located within the transmission range of certain network beacons. For example, the authorization rules161may specify that the network beacons require an 8-digit password to access the network beacons if the client device120is not located within the transmission range of a specific network beacon, and the resource rules171may specify that the network beacons only require a 4-digit password to access the network beacons if the client device120is located within the transmission range of the specific network beacon. In another embodiment, the stringency of the authorization rules161may be increased, reduced, and/or eliminated if the client device120is located within the transmission range of network beacons associated with a certain network. For example, the authorization rules161may specify that the network beacons require 256-bit encryption enabled if the client device120is not located within the transmission range of network beacons associated with a specific network, and the authorization rules161may specify that the network beacons only require 128-bit encryption if the client device120is located within the transmission range of network beacons associated with the specific network. In another embodiment, the stringency of the authorization rules161may be increased, reduced, and/or eliminated if the client device120is located within the transmission range of certain network beacons associated with certain networks. For example, the authorization rules161may not apply to a client device120that is not located within the transmission range of any unknown network beacons and/or is not located within the transmission range of any network beacons associated with unknown networks.

The access control service174may be executed to identify one or more client devices120that may potentially be authorized to access the network beacons. In certain embodiments, the access control service174identifies one or more client devices120that are located within the transmission range of the network beacons. In one embodiment, the access control service174may identify client devices120by receiving one or more requests177to access to the network beacons from the client devices120. The requests177may include a device profile123describing the state of the associated client device120, one or more user identifiers associated with the user of the client device120, and/or one or more device identifiers associated with the client device120. In another embodiment, the access control service174may identify client devices120that are located within one or more authorized locations associated with the network beacons. In yet another embodiment, the access control service174may identify client devices120whose current times are within one or more authorized windows associated with the network beacons.

The access control service174may be executed to determine whether one or more identified client devices120may be authorized access to the network beacons. In certain embodiments, the access control service174may determine whether one or more client devices120may be authorized access to the network beacons based on one or more authorization rules161associated with the network beacons. For example, the access control service174may determine whether the client devices120satisfy the authorization rules161based at least in part on a device profile123associated with the client devices120.

The access control service174may be executed to authorize one or more client devices120to access to the network beacons. In one embodiment, the access control service174may authorize a client device120by transmitting an authorization key to the client device120that allows the client device120to access the network beacons. In another embodiment, the access control service174may authorize a client device120by transmitting one or more resources165associated with the network beacons to the client device120that individually and/or collectively represent a key that may unlock access to the network beacons. In yet another embodiment, the access control service174may authorize a client device120by transmitting an indication to the network beacons that specifies that the client device120is authorized to access the network beacons.

In certain embodiments, the access control service174may specify one or more access rights associated with the client devices120when the access control service174authorizes the client devices120to access the network beacons. In some embodiments, the access control service174may rely on one or more access lists to determine one or more specific access rights associated with the client devices120which the access control service174has determined are authorized to access the network beacons. The access rights may specify which data and/or services associated with the network beacons may be accessed by the client devices120associated with the access rights that have been determined to be authorized to access the network beacons. As an example, an administrator of the access control service174may predefine an access list including the identities of a group of client devices associated with an enterprise. Once the access control service174has determined that a given client device120is authorized to access the network beacons, the access control service174may, for example, determine whether the client device120is a member of the predefined access list of client devices120associated with the enterprise and, if so, assign the access rights associated with the enterprise to the client device120.

The access control service174may be further executed to terminate the authorization of one or more client devices120to access to the network beacons. In certain embodiments, the access control service174may terminate the authorization of client devices120that do not satisfy the authorization rules161associated with the network beacons. For example, the access control service174may terminate the authorization of client devices120that are not located within an authorized range of the network beacons, that do not have resources165associated with the network beacons executed on the client device120, and that do not satisfy resource rules171associated with the resources165. In some embodiments, the access control service174may terminate the authorization of client devices120previously provided to the client devices120by the access control service174and/or another service controlling access to the network110. In one embodiment, the access control service174may terminate the authorization of client devices120by removing an authorization key from the client devices120that allows the client devices120to access the network beacons. In another embodiment, the access control service174may terminate the authorization of client devices120by removing one or more resources165from the client devices120that individually and/or collectively represent a key that allows the client device120to access to the network beacons. In yet another embodiment, the access control service174may terminate the authorization of client devices120by transmitting an indication to the network beacons that specifies that the client device120is no longer authorized to access the network beacons.

The access control service174may be further executed to provide one or more authorized client devices120with access to a network110associated with the network beacons. In certain embodiments, the access control service174may represent a gateway to a network110associated with the network beacons. In one embodiment, the access control service174may be configured to provide client devices120with access to the network110if the client devices120are authorized to access the network beacons based on the authorization rules161. In another embodiment, the access control service174may be configured to block client device120from accessing the network110if the client devices120are not authorized to access the network beacons based on the authorization rules161.

FIG. 2is a flowchart illustrating exemplary functionality performed by a access control service174executed by a access control server (FIG. 1) according to certain embodiments. It is understood that the flowchart ofFIG. 2provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the access control service174as described herein. As an alternative, the flowchart ofFIG. 2may be viewed as depicting an example of steps of a method implemented in the access control server150according to one or more embodiments.

Beginning with step203, the access control service174may receive one or more requests177from one or more client devices120that request access to one or more network beacons. In certain embodiments, the requests177may include data that may assist the access control service174in determining whether the client devices120from which the requests177were received are authorized to access the network beacons. In one embodiment, the requests177may include one or more device profiles123associated with client devices120. In another embodiment, the requests177may include one or more user identifiers132associated with the client devices120. In yet another embodiment, the requests177may include one or more device identifiers135associated with the client devices120.

Next, in step206, the access control service174may determine whether the client devices120from which the requests177were received are authorized to access the network beacons. In certain embodiments, the access control service174may determine whether the client devices120satisfy one or more authorization rules161(FIG. 1) associated with the network beacons that must be satisfied by the client devices120in order for the client devices120to be authorized to access the network beacons. In one embodiment, the authorization rules161may require that one or more resources165associated with the network beacons be accessed by the client devices120, as described herein. In another embodiment, the authorization rules161may require that the client devices120are located within one or more authorized ranges associated with the network beacons. In yet another embodiment, the authorization rules161may require that the current times associated with the client devices120are within one or more authorized windows associated with the network beacons.

If the access control service174determines that the client devices120do not satisfy the authorization rules161associated with the network beacons, then the access control service174may proceed to step209and may not authorize the client devices120to access the network beacons. In certain embodiments, the access control service174may transmit an indication to the client devices120and/or the network beacons specifying that the client devices120are not authorized to access the network beacons. In some embodiments, the access control service174may take no further action once it has been determined that the client devices120from which it received the requests177are not authorized to access the network beacons.

On the contrary, if the access control service174determines that the client devices120do satisfy the authorization rules161associated with the network beacons, then the access control service174may proceed to step212and may authorize the client devices120to access the network beacons. In one embodiment, the access control service174may transmit an indication to the client devices120and/or the network beacons specifying that the client devices120are authorized to access the network beacons. In another embodiment, the access control service174may transmit one or more resources165associated with the network beacons to the client devices120that unlock access to the network beacons.

Then, in step215, the access control service174may determine whether previously authorized client devices120continue to satisfy the authorization rules161associated with the network beacons. In certain embodiments, the access control service174may determine whether the client devices120satisfy the authorization rules161on a periodic basis. For example, an administrator of the access control service174may configure an interval upon which the access control service174determines whether the authorization rules161remain satisfied by the client devices120.

If the access control service174determines that the authorization rules161remain satisfied by the client devices120, then the access control service174may return to the beginning of step215and may again perform step215on a configured interval. However, if the access control service174determines that the client devices120no longer satisfy the authorization rules161associated with the network beacons, the access control service174may proceed to step218and may terminate the authorization of the client devices120to access the network beacons. In one embodiment, the access control service174may transmit an indication to the client devices120and/or the network beacons specifying that the client devices120are not authorized to access the network beacons. In another embodiment, the access control service174may remove one or more resources165from the client devices120that are required in order for the client devices120to access the network beacons.

FIG. 3is a flowchart illustrating exemplary functionality performed by one or more client side applications126executed by one or more client devices120(FIG. 1) according to certain embodiments. It is understood that the flowchart ofFIG. 3provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the client side applications126as described herein. As an alternative, the flowchart ofFIG. 3may be viewed as depicting an example of steps of a method implemented in the client devices120according to one or more embodiments.

Beginning with step303, one or more client side applications126executed by one or more client devices120may transmit one or more requests177(FIG. 1) to access one or more network beacons. In certain embodiments, the client side applications126may transmit the requests177to an access control service174(FIG. 1), as described herein. In some embodiments, the requests177may include data that may indicate whether the client devices120are authorized to access the network beacons. In one embodiment, the requests177may include one or more device profiles123associated with client devices120. In another embodiment, the requests177may include one or more user identifiers132associated with the client devices120. In yet another embodiment, the requests177may include one or more device identifiers135associated with the client devices120.

Next, in step306, the client devices120may receive one or more resources165associated with the network beacons. In certain embodiments, the client side applications126may receive the resources165from an access control service174. In some embodiments, the resources165may unlock access to the network beacons while the resources165are accessed by the client devices120. In any instance, the resources165may include, for example, settings-type resources165that may be activated on the client devices120, application-type resources165that may be installed and/or executed by the client devices120, and content-type resources165that may be stored and/or rendered on the client devices120.

Then, in step309, the client side applications126may determine whether the client devices120are authorized to access the network beacons. In certain embodiments, the client side applications126may determine whether the client devices120satisfy one or more authorization rules161(FIG. 1) associated with the network beacons. In one embodiment, the authorization rules161may require that one or more resources165associated with the network beacons be accessed by the client devices120, as described herein. In another embodiment, the authorization rules161may require that the client devices120are located within one or more authorized locations associated with the network beacons. In yet another embodiment, the authorization rules161may require that the current times associated with the client devices120are within one or more authorized windows associated with the network beacons.

If the client side applications126determine that the client devices120are not authorized to access the network beacons, then the client side applications126may proceed to step312and may not access the network beacons. On the other hand, if the client side applications126determine that the client devices120are authorized to access the network beacons, then the client side applications126may proceed to step315and may access the network beacons on the client devices120. In certain embodiments, the client side applications126may provide the client devices120with access to the network beacons by facilitating a communicative connection between the client devices120and the network110via the network beacons. The client side applications126may, for instance, receive data on the client devices120from a network110associated with the network beacons and may transmit data from the client device120to the network110associated with the network beacons.

Next, in step318, the client side applications126may determine whether the client devices120continue to satisfy the authorization rules161associated with the network beacons. In certain embodiments, the client side applications126may determine whether the client devices120satisfy the authorization rules161on a periodic basis. For example, an administrator of the client side applications126may configure an interval upon which the client side applications126may determine whether the authorization rules161are satisfied by the client devices120with access to the network beacons.

If the client side applications126determine that the authorization rules161remain satisfied by the client devices120, then the client side applications126may return to the beginning of step215and may again perform step215on a configured interval. However, if the client side applications126determine that the client devices120no longer satisfy the authorization rules161associated with the network beacons, the client side applications126may proceed to step321and may cease access to the network beacons. In one embodiment, the client side applications126may cease access to the network beacons by blocking access to the network beacons. In another embodiment, the client side applications126may cease access to the network beacons by removing resources165from the client devices that are required to access the network beacons. In yet another embodiment, the client side applications126may transmit an indication to the network beacons that specifies that the client devices120are no longer authorized to access the network beacons.

Then, in addition to ceasing access to the network beacons upon a determination that the client devices120do not satisfy the authorization rules161associated with the network beacons, the client side applications126may proceed to step324and remove one or more resources165associated with the network beacons from the client devices120. In certain embodiments, the client side applications126may delete the resources165associated with the network beacons from the client devices120. In some embodiments, the client side applications126may make the resources165inoperable while the client devices120do not satisfy the authorization rules161associated with the network beacons. In any instance, the client side applications126may stop the resources165from unlocking access to the network beacons.

FIG. 4is a flowchart illustrating exemplary functionality performed by one or more access control services174executed by one or more access control servers150(FIG. 1) according to certain embodiments. It is understood that the flowchart ofFIG. 4provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the access control service174as described herein. As an alternative, the flowchart ofFIG. 4may be viewed as depicting an example of steps of a method implemented in the access control server150according to one or more embodiments.

Beginning with step403, an access control service174may identify one or more client devices120located within one or more transmission ranges of one or more network beacons. In certain embodiments, the transmission ranges of the network beacons may include the area within which a client device120may transmit data to and/or receive data from the network beacons. In one embodiment, the access control service174may identify the locations of client devices120by requesting that the client devices120provide an indication of their respective locations. In another embodiment, the access control service174may identify the locations of client devices120from the device profiles123(FIG. 1) associated with the client devices120. In any instance, the access control service174may identify client devices120located within the transmission ranges of the network beacons by determining whether the locations of the client devices120are within the transmission ranges of the network beacons.

Next, in step406, the access control service174may determine whether the identified client devices120are authorized to access the network beacons. In certain embodiments, the access control service174may determine whether the client devices120satisfy one or more authorization rules161(FIG. 1) associated with the network beacons. In one embodiment, the authorization rules161may require that one or more resources165associated with the network beacons be accessed by the client devices120. In another embodiment, the authorization rules161may require that the client devices120are located within one or more authorized ranges associated with the network beacons. In yet another embodiment, the authorization rules161may require that the current times associated with the client devices120are within one or more authorized windows associated with the network beacons.

If the access control service174determines that the client devices120do not satisfy the authorization rules161associated with the network beacons, then the access control service174may proceed to step409and may not authorize the client devices120to access the network beacons. In certain embodiments, the access control service174may transmit an indication to the client devices120and/or the network beacons specifying that the client devices120are not authorized to access the network beacons. In some embodiments, the access control service174may take no further action once it has been determined that the identified client devices120are not authorized to access the network beacons.

On the contrary, if the access control service174determines that the client devices120satisfy the authorization rules161associated with the network beacons, then the access control service174may proceed to step412and may transmit one or more resources165associated with the network beacons to the client devices120. In certain embodiments, the access control service174may transmit the resources165to one or more client side applications126(FIG. 1) executed by the client devices120. The client side application126may be a containerized application, for example, that controls the manner in which the resources165may be accessed. For example, the client side application126may prohibit the resources165from being cut, copied, pasted, transmitted, screen captured, printed, and/or otherwise accessed outside of the containerized environment of the client side application126. In any instance, the resources165may include settings-type resources165, application-type resources165, and content-type resources165, as described herein.

Then, in addition to transmitting resources165associated with the network beacons to the client devices120upon a determination that the client devices120satisfy the authorization rules161associated with the network beacons, the access control service174may proceed to step415and may authorize the client devices120to access the network beacons. In certain embodiments, the access control service174may authorize the client devices120to access the network beacons by transmitting an authorization key to the client devices120that allows the client devices120to unlock access the network beacons. In some embodiments, the resources165associated with the network beacons that were transmitted to the client devices in step412may individually and/or collectively unlock access to the network beacons. In other embodiments, the access control service174may authorize the client devices120by transmitting an indication to the network beacons that specifies that the client devices120are authorized to access the network beacons.

Next, in step418, the access control service174may determine whether the client devices120continue to satisfy the authorization rules161associated with the network beacons. In certain embodiments, the access control service174may determine whether the client devices120satisfy the authorization rules161on a periodic basis. For example, an administrator of the access control service174may configure an interval upon which the access control service174may determine whether the authorization rules161are satisfied by the client devices120.

If the access control service174determines that the authorization rules161remain satisfied by the client devices120, then the access control service174may return to the beginning of step215and may again perform step215on a configured interval. However, if the access control service174determines that the client devices120no longer satisfy the authorization rules161associated with the network beacons, the access control service174may proceed to step421and may terminate the authorization of the client devices120to access the network beacons. In one embodiment, the access control service174may transmit one or more instructions to the client devices120that block access to the network beacons. In another embodiment, the access control service174may disable one or more resources165on the client devices120that are required to access the network beacons. In yet another embodiment, the access control service174may terminate the authorization of the client devices120by transmitting an indication to the network beacons that specifies that the client devices120are no longer authorized to access the network beacons.

Then, in addition to terminating the authorization of the client devices120to access the network beacons upon a determination that the client devices120do not satisfy the authorization rules161associated with the network beacons, the access control service174may proceed to step424and may remove one or more resources165associated with the network beacons from the client devices120. In certain embodiments, the access control service174may delete the resources165associated with the network beacons from the client devices120. In some embodiments, the access control service174may disable the resources165while the client devices120do not satisfy the authorization rules161associated with the network beacons. In any instance, the access control service174may stop the resources165from unlocking access to the network beacons.

FIG. 5shows schematic block diagrams of an exemplary access control server150and an exemplary client device120according to an embodiment of the present disclosure. The access control server150includes at least one processor circuit, for example, having a processor503and a memory506, both of which are coupled to a local interface509. To this end, the access control server150may comprise, for example, at least one server computer or like device. Similarly, the client device120includes at least one processor circuit, for example, having a processor553and a memory556, both of which are coupled to a local interface559. Additionally, the client device120may be in data communication with a display136for rendering user interfaces137(FIG. 1) and one or more other I/O devices563for inputting and outputting data. To this end, the client device120may comprise, for example, at least one client computer or like device.

The following is a general discussion of the components of the access control server150and the client device120. The local interface509and559may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated. Stored in the memory506and556are both data and several components that are executable by the processors503and553. In particular, with regard to the access control server150, stored in the memory506and executable by the processor503are an access control service174and potentially other applications. Additionally, with regard to the client device120, stored in the memory556and executable by the processor553are a client side application126and potentially other applications. Also stored in the memory506and556may be a data store153and122and other data. In addition, an operating system may be stored in the memory506and556and executable by the processor503and553.

It is to be understood that there may be other applications that are stored in the memory506and556and are executable by the processor503and553as can be appreciated. Where any component discussed herein is implemented in the form of software, any one of a number of programming languages may be employed such as, for example, C, C++, C#, Objective C, Java, JavaScript, Perl, PHP, Visual Basic, Python, Ruby, Delphi, Flash, or other programming languages.

A number of software components are stored in the memory506and556and are executable by the processor503and553. In this respect, the term “executable” means a program file that is in a form that can ultimately be run by the processor503and553. Examples of executable programs may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of the memory506and556and run by the processor503and553, source code that may be expressed in proper format such as object code that is capable of being loaded into a random access portion of the memory506and556and executed by the processor503and553, or source code that may be interpreted by another executable program to generate instructions in a random access portion of the memory506and556to be executed by the processor503and553, etc. An executable program may be stored in any portion or component of the memory506and556including, for example, random access memory (RAM), read-only memory (ROM), hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (CD) or digital versatile disc (DVD), floppy disk, magnetic tape, or other memory components.

Also, the processor503and553may represent multiple processors, and the memory506and556may represent multiple memories that operate in parallel processing circuits, respectively. In such a case, the local interface509and559may be an appropriate network110(FIG. 1) that facilitates communication between any two of the multiple processors503and553, or between any two of the memory506and556, etc. The local interface509and559may comprise additional systems designed to coordinate this communication, including, for example, performing load balancing. The processor503and553may be of electrical or of some other available construction.

The flowcharts ofFIGS. 2,3, and4show certain functionality and operations performed by the access control service174and client side application126, respectively. If embodied in software, each box may represent a module, segment, or portion of code that comprises program instructions to implement the specified logical function(s). The program instructions may be embodied in the form of source code that comprises human-readable statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as a processor503and553in a computer system or other system. The machine code may be converted from the source code, etc. If embodied in hardware, each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).