Automated facility access and payment processing systems and methods

CROSS REFERENCE TO RELATED APPLICATION

0001This application claims priority from U.S. Provisional Application Ser. No. 62/036,086, filed Aug. 11, 2014, the contents of which are incorporated herein by reference.

FIELD OF THE INVENTION

0002The present disclosure is generally related to communication between a mobile device and a gateway device having Internet connectivity. More particularly, the disclosure is related to systems and methods for automated facility access and payment processing. Most particularly, the facility may be a parking facility.

BACKGROUND OF THE INVENTION

0003There is an increasing demand by users for convenient systems based on Internet-connected devices, including mobile telephones, hand-held devices, car-phones, laptop computers, or other electronic devices to obtain and pay for goods or services. Often, these devices use software commonly known as an application, or “app”; a piece of software that can run on the Internet, on a computer, on a mobile phone or other electronic device.

0004Entry systems use a variety of ways to record when a person or vehicle enters and exits a facility or space. Some entry systems may charge an entrance fee, either flat or incremental. When charging an increment fee, many existing systems time-stamp entry and exit to determine elapsed time and calculate the proper incremental rate.

0005As a non-limiting description of related art, some entry and exit transactions occur at parking facilities. Attended parking facilities may have a worker on site to record vehicle arrival and accept payment upon the vehicle leaving. These attended parking facilities may charge a variable fee based on the length of time that a vehicle is parked in the lot, garage or other parking facility.

0006Unattended parking facilities may not have an attendant on site throughout the entire day, so the attendant is not there to record when vehicles arrive or leave. Therefore these parking facilities typically charge a flat fee. Other unattended facilities do not have a gate or full-time attendant, and a worker goes to the facility at various times during the day to determine if all parked vehicles have paid the entrance fee. Alternatively, some unattended parking facilities charge a variable fee based on the length of time parked; however, these facilities make a substantial investment in gates, gate arms or other movable barriers, and terminals to record the time of entrance, exit and determine elapsed time and incremental fee.

0007Thus, a heretofore unaddressed need exists in the industry to address the aforementioned deficiencies and inadequacies.

SUMMARY OF THE INVENTION

0008Embodiments of the present disclosure provide parking facility access and payment processing systems and methods. Briefly described, in architecture, one embodiment of a system, among others, can be implemented as follows. The system includes a parking facility server located proximate to a parking facility, a central authentication and payment processing server for authenticating and processing payment for a user of parking facilities, a gate controller positioned proximate to a barrier gate at the parking facility, and at least one of an identification module connected to a vehicle, and a user computer device including or accessing an automated parking and payment processing application. The gate controller is configured to receive, via Bluetooth communication with the at least one of an identification module and a user computer device, identification information about a user seeking entry into the parking facility, and to relay the identification information to the parking facility server. The central authentication and payment processing server is configured to receive the identification information from the parking facility server and verify that the user is a valid account holder within the system. The parking facility server is configured to receive verification from the central authentication and payment processing server and to signal the gate controller to open the barrier gate and allow the user's vehicle to enter the parking facility. The gate controller is further configured to detect entry of the vehicle into the parking facility and to provide notification to the central authentication and payment processing server, via the parking facility server, for payment processing.

0009In accordance with one aspect of the present invention, there is disclosed an automated facility access and payment processing system, comprising:

0010an access control device located at a facility, said access control device being configured to grant or deny a user access to or from said facility;

0011an access control device controller operatively connected to said access control device and configured to cause said access control device to grant or deny said user access to or from said facility;

0012at least one of: an identification module connected to a vehicle, and a user computer device, each containing user identification information; and

0013a two-way communication means between said at least one of said identification module and said user computer device, and said access control device controller to allow said at least one of said identification module and said user computer device to transmit said user identification information to said access control device controller in response to receiving a request for said user identification information from said access control device controller;

0014at least one server operatively connected to said access control device controller, said at least one server being configured to: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0015">a. receive said user identification information from said access control device controller;</li><li id="ul0002-0002" num="0016">b. use said received user identification information to authenticate and process payment for said user; and</li><li id="ul0002-0003" num="0017">c. signal said access control device controller to cause said access control device to grant said user access to or from said facility.</li></ul></li></ul>

0018In accordance with another aspect of the present invention, there is disclosed an automated parking facility access and payment processing system, comprising:

0019a parking facility server located proximate to a parking facility;

0020a central authentication and payment processing server for authenticating and processing payment for a user of parking facilities;

0021a gate controller positioned proximate to a barrier gate at the parking facility; and

0022at least one of: an identification module connected to a vehicle, and a user computer device including or accessing an automated parking and payment processing application;

0023wherein the gate controller is configured to receive, via Bluetooth communication with the at least one of an identification module and a user computer device, identification information about a user seeking entry into the parking facility, and to relay the identification information to the parking facility server;

0024wherein the central authentication and payment processing server is configured to receive the identification information from the parking facility server and verify that the user is a valid account holder within the system;

0025wherein the parking facility server is configured to receive verification from the central authentication and payment processing server and to signal the gate controller to open the barrier gate and allow the user's vehicle to enter the parking facility; and

0026wherein the gate controller is further configured to detect entry of the vehicle into the parking facility and to provide notification to the central authentication and payment processing server, via the parking facility server, for payment processing.

0027Other systems, methods, features, and advantages of the present disclosure will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present disclosure, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

0028Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.

0029<figref idref="DRAWINGS">FIG. 1</figref> is a schematic illustration of an automated parking facility access and payment processing system, in accordance with a first exemplary embodiment of the present disclosure.

0030<figref idref="DRAWINGS">FIG. 2</figref> is a flow chart which schematically illustrates use of the system of <figref idref="DRAWINGS">FIG. 1</figref> when a user seeks entry to a parking facility, in accordance with embodiments of the present disclosure.

0031<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart which schematically illustrates use of the system of <figref idref="DRAWINGS">FIG. 1</figref> when a user seeks to exit the parking facility, in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

0032Many embodiments of the disclosure may take the form of computer-executable instructions, including algorithms executed by a programmable computer. However, the disclosure can be practiced with other computer system configurations as well. Certain aspects of the disclosure can be embodied in a special-purpose computer or data processor that is specifically programmed, configured or constructed to perform one or more of the computer-executable algorithms described below. Accordingly, the term “computer” as generally used herein refers to any data processor and includes Internet appliances, hand-held devices (including palm-top computers, wearable computers, cellular or mobile phones, multi-processor systems, processor-based or programmable consumer electronics, network computers, minicomputers) and the like.

0033The disclosure also can be practiced in distributed computing environments, where tasks or modules are performed by remote processing devices that are linked through a communications network. Moreover, the disclosure can be practiced in Internet-based or cloud computing environments, where shared resources, software and information may be provided to computers and other devices on demand. In a distributed computing environment, program modules or subroutines may be located in both local and remote memory storage devices. Aspects of the disclosure described below may be stored or distributed on computer-readable media, including magnetic and optically readable and removable computer disks, fixed magnetic disks, floppy disk drive, optical disk drive, magneto-optical disk drive, magnetic tape, hard-disk drive (HDD), solid state drive (SSD), compact flash or non-volatile memory, as well as distributed electronically over networks including the cloud. Data structures and transmissions of data particular to aspects of the disclosure are also encompassed within the scope of the disclosure.

0034<figref idref="DRAWINGS">FIG. 1</figref> is a schematic illustration of an automated parking facility access and payment processing system <b>10</b>, in accordance with a first exemplary embodiment of the present disclosure. The automated parking facility access and payment processing system <b>10</b>, which may also be referred to as ‘system <b>10</b>’, includes one or more parking facility servers <b>20</b> and a central authentication and payment processing server <b>22</b>. One or more access control device controllers, or gate controllers <b>30</b> are included in the system <b>10</b>, and are located on or proximate to one or more parking facility gates <b>35</b> or other such structures located, for example, at a parking facility entry and/or exit. Most preferably, the gate controllers <b>30</b> are operatively connected to gate structures <b>35</b> which structures are used for limiting access to the facility. A user computer device (e.g., a smartphone or other mobile computing device) includes or otherwise accesses an automated parking facility access and payment application <b>40</b>. An identification module <b>50</b> may be located onboard a vehicle <b>60</b>.

0035The servers <b>20</b>, <b>22</b> may be or include any database capable of storing and/or providing access to information, such as an electronic database, a computer and/or computerized server, database server or generally any network host capable of storing data and connected to any type of data network. Further, the servers <b>20</b>, <b>22</b> may include or be a part of a distributed network or cloud computing environment. Any type of electronic and/or computerized device that is capable of storing information may be included as the servers <b>20</b>, <b>22</b> and is considered within the scope of this disclosure. The servers <b>20</b>, <b>22</b> may include computer-readable storage media, and a processor for processing data and executing algorithms, including any of the processes and algorithms set forth in this disclosure. Furthermore, in other embodiments of the present invention the functionality of the parking facility servers <b>20</b> and the central authentication and payment processing server <b>22</b> may be combined into a single server, or separated out further to additional servers. Although these other embodiments are comprehended by the present invention, their implementation will be generally understood by those skilled in the art, and so they are not described further herein.

0036The user computer device may be any device that is capable of communicating with the central authentication and payment processing server <b>22</b> via the application <b>40</b> (which may be hosted, for example, on the user computer device, the central authentication and payment processing server <b>22</b> and/or some combination thereof), and may be operated by any user of the system <b>10</b>, and particularly those users who use the system <b>10</b> to gain access to parking facilities. Any number of user computer devices may use the system <b>10</b> at any given time. The user computer device may be any computer, including any personal computer, Internet appliance, hand-held device (including palm-top computers, wearable computers, cellular or mobile phones, multi-processor systems, processor-based or programmable consumer electronics, network computers, minicomputers), onboard vehicle systems, and the like.

0037The automated parking facility access and payment application <b>40</b> may be fully or partially hosted on the central authentication and payment processing server <b>22</b> and accessible to a user via a user computer device, through two-way communication through the facility. The application <b>40</b> may include any tool, device, system, process or combination thereof, which assists or makes possible providing, for example, automated parking facility access to registered users of the system <b>10</b>. For example, the application <b>40</b> may facilitate the authentication of a registered user through interaction with a parking facility server <b>20</b> and/or gate controller <b>30</b> at a parking facility which the user is seeking to enter, and may further facilitate automated payment processing for such parking facility access and use. The application <b>40</b> may include any computer-readable memory or databases, which may be stored in any computer-readable medium, and may be accessible by a computer processor. The application <b>40</b> may further include or access computer program instructions which may cause a processor to perform any algorithms and/or functions which may be described in this disclosure.

0038The gate controller <b>30</b> may, for example, grant access and exit to the parking facility through interaction with the central authentication and payment processing server <b>22</b>. Communication with the vehicle <b>60</b> and/or driver, including credentials and messaging prompts or push notifications issued to the user by the parking facility server <b>20</b>, and responses issued by the user to the parking facility server <b>20</b>), is enabled via the application <b>40</b>, the identification module <b>50</b>, or a combination thereof, which may be provided by means of local two-way communication between the parking facility server <b>20</b> (via the gate controller <b>30</b>) and the user computer device.

0039The application <b>40</b> may be installed onto each of a plurality of user computer devices (e.g., smartphones) by each end user. The details of each user account can be configured, added and updated either directly from the user's computer device (e.g., by accessing the application <b>40</b>) or from a dedicated secure website (e.g., which may provide access to the application <b>40</b>). The user computer device may include Bluetooth communications functionality, which may be required to be turned on in order for the user to seamlessly utilize the automated parking facility access and payment processing system <b>10</b>.

0040The automated parking facility access and payment application <b>40</b> communicates with: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0041">The gate controller <b>30</b> using Bluetooth or Wi-Fi, where identification data is exchanged.</li><li id="ul0004-0002" num="0042">The central authentication and payment processing server <b>22</b> via the gate controller <b>30</b> (e.g., via communication between the gate controller <b>30</b> and the parking facility server <b>20</b>, and communication between the parking facility server <b>20</b> and the central authentication and payment processing server <b>22</b>) using Bluetooth or Wi-Fi, identifying itself, the account holder and location. (Link <b>2</b> in <figref idref="DRAWINGS">FIG. 1</figref>).</li><li id="ul0004-0003" num="0043">The central authentication and payment processing server <b>22</b> using a mobile network communication protocol such as GPRS and/or LTE (e.g., when cellular signal is available), identifying itself, the account holder and location. (Link <b>1</b> in <figref idref="DRAWINGS">FIG. 1</figref>).</li></ul></li></ul>

0044The automated parking facility access and payment application <b>40</b> can be used on user computer devices without Bluetooth-functionality (or with Bluetooth disabled) by communicating directly with the central authentication and payment processing server <b>22</b> (e.g., via Link <b>1</b>); however, this has limitations due to the sporadic availability of cellular access in heavily shielded underground parking locations. The use of Bluetooth mode for devices using the application <b>40</b> is thus preferred where Wi-Fi or any other two-way communication is not otherwise available.

0045The onboard identification module <b>50</b> may be installed in each vehicle <b>60</b> near the front drivers' side headlight assembly, which may ensure close proximity to the gate controller <b>30</b> when approaching a gate at a parking facility. Left hand drive vehicles would thus locate the identification module <b>50</b> near the front left headlight, while right hand drive vehicles, such as those in the U.K., Singapore and India, would locate the identification module <b>50</b> near the right side headlight.

0046The identification module <b>50</b> communicates with: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0047">The application <b>40</b>, where identification data is exchanged. When the onboard identification module <b>50</b> is present, use of the application <b>40</b> is optional, as the requisite registered user identification, account information and/or other credentials may be provided from the identification module <b>50</b>.</li><li id="ul0006-0002" num="0048">The parking facility server <b>20</b> via the gate controller <b>30</b> (e.g., via communication between the gate controller <b>30</b> and the parking facility server <b>20</b>, and communication between the parking facility server <b>20</b> and the central authentication and payment processing server <b>22</b>) using Bluetooth or Wi-Fi, using a Bluetooth transceiver, identifying itself and the account holder. (Link <b>2</b> in <figref idref="DRAWINGS">FIG. 1</figref>).</li></ul></li></ul>

0049Because the connection between the onboard identification module <b>50</b> and gate controller <b>30</b> is made using Bluetooth, the identification module <b>50</b> avoids cellular signal limitations which exist in most underground parking facilities. Further, when the identification module <b>50</b> is pre-installed in a vehicle <b>60</b>, access to the system <b>10</b> can be made via the credentials or user identification information attached to the vehicle <b>60</b> (e.g., via the identification module <b>50</b>), without need for users to have a mobile phone or other mobile computer device. By way of example, on detecting an approaching vehicle using for example a vehicle detector, mentioned below, the gate controller <b>30</b> may initiate a two-way communication with the identification module <b>50</b>, and request the user identification information (i.e. credentials) attached to the vehicle <b>60</b>. In response to such a request, the identification module <b>50</b> may be configured to transmit the requested user identification information to the gate controller <b>30</b>, without user input. It is also contemplated that the identification module may be configured to detect the presence of the gate controller <b>30</b> and initiate a two-way communication before transmitting the user identification information to the gate controller <b>30</b>, also without user input. In this sense, the identification module <b>50</b> will preferably be a closed system, having the user identification information and certain other preselected user parameters (i.e. permitted parking facilities, permitted parking location(s) within a parking facility, parking fee structure, permitted parking duration, permitted parking times, etc.) stored in a memory of the identification module. By being a closed structure, the user's parking options may be controlled by the fleet operator, who would have access to modify the preselected user parameters (i.e. the preselected parameters may not be modified by the user), or grant such access to others. It is contemplated that such an identification module <b>50</b> will be useful for fleet vehicles, so that the users will not need to be distracted from the task of driving by the need to review and select the same user parameters over and over again. However, like the embodiment of the invention utilizing the user computer device, the identification module <b>50</b> is adapted to establish two-way communication with the gate controller <b>30</b> to send user identification information, and to receive information from the central authentication and payment processing server <b>22</b> (i.e. via the gate controller <b>30</b> and the parking facility server <b>20</b>) and store same in a memory for subsequent retrieval by, for example, the same or another gate controller <b>30</b>, or a separate commercial hub, for billing purposes and/or inventory management. In this way, the system can keep track of, for example, the location of each fleet vehicle, and the location of empty and occupied parking locations.

0050A fused 5 VDC power supply may be required when connecting the identification module <b>50</b> to the vehicle <b>60</b>. Each identification module <b>50</b> contains a unique ID that identifies the vehicle <b>60</b> and account holder (or registered user of the system <b>10</b>) to the central authentication and payment processing server <b>22</b>.

0051In a preferred embodiment, the gate controller <b>30</b> is operatively connected to one or more barrier gates at a parking facility. In this sense, operatively connected means that the gate controller <b>30</b> can communicate with and control the opening and closing of the barrier gates of other facility access control devices. More preferably, the gate controller <b>30</b> may be located in close proximity to the one or more barrier gates. The gate controller <b>30</b> is the intermediate device that links the onboard identification module <b>50</b> to the parking facility server. The gate controller <b>30</b> may be required to be located within a certain distance from the parking facility server <b>20</b>, such as, for example, 1000 m.

0052The gate controller <b>30</b> may house or otherwise include: <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0053">A Bluetooth transceiver to communicate with the onboard identification module <b>50</b>.</li><li id="ul0008-0002" num="0054">A Radio transceiver (e.g., 433 MHz) to communicate with the parking facility server <b>20</b>.</li><li id="ul0008-0003" num="0055">RJ45 Ethernet port to communicate with the parking facility server <b>20</b>.</li></ul></li></ul>

0056The gate controller <b>30</b> also acts as a control board to communicate with the barrier gate <b>35</b> (e.g., to control the raising of the gate upon successful authentication). Preferably, the system <b>10</b> may include a user detector such as, for example, a radar device, a camera or an induction loop, for detecting entry of a user to, or exit of a user from the facility. Preferably the user detector may be operatively connected to the gate controller <b>30</b>. For example, in a parking facility where the user will be inside of a vehicle, the user detector may be selected to detect the vehicle (i.e. a vehicle detector), as opposed to the user himself.

0057The parking facility server <b>20</b> is the intermediary interface that functions as the gate keeper, handling transaction queries on behalf of the central authentication and payment processing server <b>22</b>. The parking facility server <b>20</b> may be required to be located within a certain distance from the gate controller <b>30</b>, such as, for example, 1000 m.

0058The parking facility server <b>20</b> may communicate via: <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0000"><ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0059">433 MHz Radio transceiver to communicate with the gate controller <b>30</b>.</li><li id="ul0010-0002" num="0060">RJ45 Ethernet port to communicate with the gate controller <b>30</b>.</li><li id="ul0010-0003" num="0061">RJ45 Ethernet port to communicate with the central authentication and payment processing server <b>22</b> via the Internet.</li><li id="ul0010-0004" num="0062">Optional Cellular (3G/LTE) connection to the central authentication and payment processing server <b>22</b>.</li></ul></li></ul>

0063The parking facility server <b>20</b> relays account queries, recording the ID of each identification module <b>50</b>, along with the location, allowing vehicular access to the parking facility (e.g., upon successful authentication). The parking facility server <b>20</b> also signals the gate controller <b>30</b> to open/close the barrier gate <b>35</b>.

0064The central authentication and payment processing server <b>22</b> performs the transactions for account and client management by communicating with the parking facility server <b>20</b>.

0065The central authentication and payment processing server <b>22</b> may communicate via: <ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0000"><ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0066">433 MHz Radio transceiver to communicate with the parking facility server <b>20</b> via the Internet.</li><li id="ul0012-0002" num="0067">Optional Cellular (GPRS/LTE) connection to the parking facility server <b>20</b>.</li><li id="ul0012-0003" num="0068">Optional Cellular (GPRS/LTE) connection with user computer devices including the automated parking facility access and payment application <b>40</b>.</li></ul></li></ul>

0069The central authentication and payment processing server <b>22</b> handles all account validation and access/exit requests from the parking facility server <b>20</b> and the application <b>40</b>, and also consolidates transactions and performs billing invoicing.

0070The system <b>10</b> performs its functions in two separate operational sequences: parking facility entrance, and parking facility exit and payment.

0071<figref idref="DRAWINGS">FIG. 2</figref> is a flow chart <b>200</b> which schematically illustrates operation of the system <b>10</b> during parking facility entrance. It should be noted that any process descriptions or blocks in flow charts should be understood as representing modules, segments, portions of code, or steps that include one or more instructions for implementing specific logical functions in the process, and alternate implementations are included within the scope of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.

0072As shown in <figref idref="DRAWINGS">FIG. 2</figref>, when the customer is ready to enter the parking facility, the following actions will occur: <ul id="ul0013" list-style="none"><li id="ul0013-0001" num="0000"><ul id="ul0014" list-style="none"><li id="ul0014-0001" num="0073">1. The parking customer will enter the parking facility with a vehicle <b>60</b> containing the onboard identification module <b>50</b> and/or a smartphone or other user computer device loaded with the automated parking facility access and payment application <b>40</b>.</li><li id="ul0014-0002" num="0074">2. Using, for example, Bluetooth, the identification module <b>50</b> and/or application <b>40</b> communicates with the gate controller <b>30</b>, identifying the vehicle <b>60</b> and the physical location of the parking facility. The application <b>40</b> also identifies the user.</li><li id="ul0014-0003" num="0075">3. The gate controller <b>30</b> relays vehicle and/or user information from the identification module <b>50</b> and/or the application <b>40</b> to the parking facility server <b>20</b>, which will forward information (e.g. location, license plate, user account details, etc.) to the central authentication and payment processing server <b>22</b>.</li><li id="ul0014-0004" num="0076">4. The central authentication and payment processing server <b>22</b> will record this data and confirm the validity of the account.</li><li id="ul0014-0005" num="0077">5. The central authentication and payment processing server <b>22</b>, after confirming the validity of the account, will communicate this information back to the parking facility server <b>20</b> with authorization to open the barrier gate <b>35</b>.</li><li id="ul0014-0006" num="0078">6. The parking facility server <b>20</b> will signal the gate controller <b>30</b> to open the barrier gate <b>35</b> to allow the vehicle <b>60</b> to enter and proceed to park.</li><li id="ul0014-0007" num="0079">7. As the vehicle <b>60</b> passes the barrier gate <b>35</b> and triggers the detector(s), the gate controller <b>30</b> will notify the parking facility server <b>20</b> that the vehicle <b>60</b> has cleared the entrance and entered the parking facility. The parking facility server <b>20</b> will once again notify the central authentication and payment processing server <b>22</b>, and the billing cycle will commence. Preferably the central authentication and payment processing server <b>22</b> will record data such as the entry time and associate it with the other information mentioned above (e.g. location, license plate, user account details, etc.). A notification that the billing cycle has commenced may be transmitted or otherwise accessible to the user (e.g., through email, regular mail, access through the application <b>40</b> and so on).</li></ul></li></ul>

0080<figref idref="DRAWINGS">FIG. 3</figref> is a flow chart <b>300</b> which schematically illustrates operation of the system <b>10</b> during parking facility exit. When the customer is ready to depart the parking facility, the following actions will occur: <ul id="ul0015" list-style="none"><li id="ul0015-0001" num="0000"><ul id="ul0016" list-style="none"><li id="ul0016-0001" num="0081">1. The parking customer will exit the parking facility with a vehicle <b>60</b> containing an onboard identification module <b>50</b> and/or a smartphone or other user computer device loaded with the automated parking facility access and payment application <b>40</b>.</li><li id="ul0016-0002" num="0082">2. Using, for example, Bluetooth, the identification module <b>50</b> and/or automated parking facility access and payment application <b>40</b> communicates with the gate controller <b>30</b>, identifying the vehicle and the physical location of the parking facility. The application <b>40</b> also identifies the user.</li><li id="ul0016-0003" num="0083">3. The gate controller <b>30</b> relays vehicle and/or user information from the identification module <b>50</b> and/or the application <b>40</b> to the parking facility server <b>20</b>, which will forward information (e.g., location, license plate, user account details, etc.) to the central authentication and payment processing server <b>22</b>.</li><li id="ul0016-0004" num="0084">4. The central authentication and payment processing server <b>22</b> will record this data and confirm the validity of the account.</li><li id="ul0016-0005" num="0085">5. The central authentication and payment processing server <b>22</b>, after confirming the validity of the account, will communicate this information back to the parking facility server <b>20</b> with authorization to open the barrier gate <b>35</b>.</li><li id="ul0016-0006" num="0086">6. The parking facility server <b>20</b> will signal the gate controller <b>30</b> to open the barrier gate <b>35</b> to allow the vehicle <b>60</b> to exit.</li><li id="ul0016-0007" num="0087">7. As the vehicle <b>60</b> passes the barrier gate <b>35</b> and triggers the detector(s), the gate controller <b>30</b> will notify the parking facility server <b>20</b> that the vehicle <b>60</b> has cleared the barrier <b>35</b> and exited the parking facility. The parking facility server <b>20</b> will once again notify the central authentication and payment processing server <b>22</b>. Preferably the central authentication and payment processing server <b>22</b> will record data such as the exit time.</li><li id="ul0016-0008" num="0088">8. The central authentication and payment processing server <b>22</b> then calculates the parking costs, adjusts the user's account balance and bills accordingly and creates a record of the completed parking transaction, which may be transmitted or otherwise accessible to the user (e.g., through email, regular mail, access through the application <b>40</b> and so on).</li></ul></li></ul>

0089While the present invention has been described primarily with respect to automated access to a parking facility, it should be noted that the invention more broadly encompasses a system for communicating via Bluetooth (or Bluetooth low energy) between a mobile device (e.g., a smartphone) and an Internet-connected gateway device (e.g., the gate controller <b>30</b> as shown in the example provided by <figref idref="DRAWINGS">FIG. 1</figref>), and thereby gaining full Internet access. Conventionally, Bluetooth low energy (BLE) has been used as a beacon, similar to RFID or NFC, which simply conveys key information between the BLE endpoints. However, the present invention provides full Internet accessibility to a mobile device via BLE communications with an Internet-connected gateway device. As will be readily appreciated by those skilled in the relevant field, this has applications vastly beyond parking. For example, it is contemplated that the system may be used to open and close a) access control devices such as barriers, gates, turnstiles, doors, and locks; b) activate and inactivate access control devices such as visual or aural indicators (i.e. enter or exit lights, signs, or sounds); and c) activate or deactivate utilities (i.e. lights, environmental systems such as heating, air conditioning, refrigeration, ventilation, electrical power, water supply, and air supply, computer equipment, facility equipment, and other equipment), in a building, whether residential (i.e. house or apartment) or commercial (i.e. restaurant or hotel). What is important is that the user's computer device (i.e. smart phone) or identification module (i.e. device connected to vehicle) is configured to communicate with an Internet-connected gateway device via Bluetooth, the Internet-connected gateway device is configured to communicate, via the Internet, with one or more servers (including local servers and remote servers in the Internet “Cloud”), and the one or more servers are configured to signal the Internet-connected gateway device to perform an action. In this context, Bluetooth allows for quick, two-way communication with the user's computing device, enabling the user to interact with the one or more servers in the Internet “Cloud” through prompts and/or push notifications on the user's computing device. In a preferred embodiment, the Internet-connected gateway device establishes a Bluetooth connection with the user's computer device, and enables communication between the user's computer device and the one or more servers, even in areas where neither cellular, nor Wi-Fi connectivity exists.

0090It should be emphasized that the above-described embodiments of the present disclosure, particularly, any “preferred” embodiments, are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the disclosure. While reference has been made to various preferred embodiments of the invention other variations, implementations, modifications, alterations and embodiments are comprehended by the broad scope of the appended claims. Some of these have been discussed in detail in this specification and others will be apparent to those skilled in the art. For example, while the present disclosure has been described primarily with respect to parking facilities and barrier gates, the features and advantages of the present disclosure can readily be incorporated into other constructs requiring payment or authentication before granting access, such as, for example, toll roads, bridges, ferries, residential and commercial buildings, and so on. Those of ordinary skill in the art having access to the teachings herein will recognize these additional variations, implementations, modifications, alterations and embodiments, all of which are within the scope of the present invention, which invention is limited only by the appended claims.