CN106030645B

CN106030645B - Registration system and method

Info

Publication number: CN106030645B
Application number: CN201480076181.4A
Authority: CN
Inventors: 丹尼斯·斯通
Original assignee: Dan NisiSitong
Current assignee: Dan NisiSitong
Priority date: 2013-12-31
Filing date: 2014-12-28
Publication date: 2021-05-11
Anticipated expiration: 2034-12-28
Also published as: WO2015103091A1; CN113378028A; EP3090402A1; CN106030645A; EP3090402A4

Abstract

Systems and methods provide a registration service to a mobile device using a registration-enabled network. When a mobile computer device attempts to access a registration-enabled network, a connection is established between the mobile computer device and the registration-enabled network. Registration information is communicated between the mobile computer device and the registration-enabled network to register a user of the mobile computer device with an entity providing the registration-enabled network. The method may further include determining whether any additional actions are available for provision to the mobile device via the registration-enabled network, the additional actions being presented to the user via the mobile device when available; and receiving input from the mobile device to take additional action. Many additional actions may be available and are disclosed herein. The system can be used to provide financial transactions while protecting the user's personal information.

Description

Registration system and method

Technical Field

The present invention relates to electronic check-in services, and more particularly to a system and method for electronically checking in upon arrival at an enabled location.

Background

Often, when a customer arrives at a restaurant, hotel, medical clinic, or another facility, the user is required to check-in before receiving the desired attention. In some cases, these registration processes may be time consuming, requiring a client to stand or "pick" and otherwise be time consuming. To reduce the difficulties associated with certain enrollment procedures, certain methods for streamlined enrollment have been developed. However, in some cases, current registration methods are unnecessarily laborious and limited in their flexibility. Additionally, some current registration methods fail to adequately leverage modern technology to enhance such methods.

Thus, while techniques currently exist for streamlining enrollment procedures, challenges still remain, including those discussed above. Accordingly, improvements in the art that supplement or even replace current techniques will be realized using other techniques.

Disclosure of Invention

Systems, methods, and non-transitory computer-readable media storing instructions for providing check-in services are disclosed. According to embodiments of the present invention, a method for providing a registration service may be provided to a system having a mobile device and a registration-enabled network. The method may include locating a registration-enabled network when the mobile computing device is within sufficient physical proximity to the registration-enabled network; accessing a registration-enabled network; and providing registration information to the registration-enabled network to cause a user of the mobile computing device to register with an entity that provides (or otherwise uses) the registration-enabled network.

The method may further include determining whether any additional actions are available to the mobile device from the registration-enabled network; providing the additional action to the user via the mobile device when the additional action is available; and receiving input from the user that causes the mobile device to take the additional action. The additional action may be an action selected from: providing payment to an entity operating a registration-enabled network; providing additional information about the user to the registration-enabled network; providing purchase information to a registration-enabled network; using the mobile computer device to fill out paperwork required by the user to complete the check-in at the enterprise operating the check-in enabled network; providing customer loyalty information from the mobile computer device to the check-in enabled network; providing a coupon to or from a mobile computer device; guiding or directing the user within a store (or other location) operating the check-in enabled network; tracking a user within a store operating a check-in enabled network; completing a checkout transaction associated with the purchase of the item within the store operating the registration-enabled network; directing the user to a parking location for order pickup; tracking the arrival and readiness of a user's party for sitting at a restaurant; notifying the user of the updated status by an action selected from the group consisting of: a text message; notification by a registration application; automated telephone calls; an email; and a notification method provided by the mobile computer device; generating a notification to an account holder of an account for enrollment that an enrollment event has occurred; obtaining a special request from a user; obtaining, by a mobile computer device, an authentication of a user; and/or otherwise take any other appropriate action associated with the enrollment.

When the additional action involves providing payment for goods and/or services to an entity operating the registration-enabled network, the payment may be provided to the location, entity, person, and/or other business while protecting the user's personal information. While the personal information of the user may be protected in any suitable manner, in certain embodiments, the personal information of the user is protected by storing the payment information of the user at a third party repository such that the actual transfer of funds occurs between the repository and the business. The repository may obtain authorization for the funds transfer from the user via the enrollment-enabled network and/or the mobile computer device. Alternatively, the repository may obtain authorization for the funds transfer from the user via a third party network and/or a mobile computer device.

According to another embodiment of the present invention, a method for providing a registration service includes providing a registration-enabled network using a wireless network device, detecting when a mobile computer device attempts to access the registration-enabled network, establishing a connection between the mobile computer device and the registration-enabled network, and receiving registration information to the registration-enabled network to cause a user of the mobile computer device to register with an entity providing the registration-enabled network.

In some embodiments, the method further optionally includes determining whether any additional actions are available for provision to the mobile device via the registration-enabled network, presenting the additional actions to the user via the mobile device when the additional actions are available, and receiving input from the mobile device to take the additional actions. The additional actions may include those discussed above. The user's personal information may also be protected as discussed above.

The system and method may be modified in any suitable manner. Indeed, in some embodiments, instead of requiring the user's mobile device to register with the enterprise prior to the user registering with the enterprise, the user's mobile device (e.g., a smartphone, tablet, handheld computer, cellular phone, feature phone, and/or any other suitable known or new mobile device) is configured (e.g., via an application installed on the device and/or a web page accessible through the device) to register with the enterprise using the device's own communication method (e.g., its phone service, WiFi, bluetooth, etc.). Such an enrollment process may be initiated in any suitable manner, including without limitation by having the user initiate the enrollment process via an application and/or website and/or by having the device automatically initiate the enrollment process when the device is determined to be proximate to the desired enterprise. In this regard, the proximity of the mobile device to the enterprise may be determined in any suitable manner, including but not limited to using GPS location; using the multilateration of radio signals between radio towers and/or transmitters for appropriate mobile devices (e.g., cellular tower triangulation); bluetooth location technology, WiFi location technology, and/or any suitable technology capable of substantially determining the proximity of a user's mobile device to a particular enterprise location.

While the methods and processes of the present invention are particularly useful in the field of registering a user with a restaurant, those skilled in the art will recognize that the methods and processes may be used in a variety of different applications and in a variety of different fields to assist a user with registering with a facility, location, service provider, store, and/or other business. For example, the systems and methods may be used to enroll one or more users into a hotel, motel, auto repair shop, medical office, dentist office, law office, movie theater, store, amusement park ride, registration process, test tone, and/or any other suitable business and/or enrollment process.

These and other features and advantages of the present invention will be set forth or will become more fully apparent in the description that follows and in the appended claims. The features and advantages may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. Furthermore, the features and advantages of the invention may be learned by the practice of the invention or will be obvious from the description, as set forth hereinafter.

Drawings

The objects and features of the present disclosure will become more fully apparent from the following description and appended claims, taken in conjunction with the accompanying drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

FIG. 1 illustrates a representative embodiment of a computer system for use with certain embodiments of the present invention;

FIG. 2 illustrates a representative embodiment of a networked computer system for use with certain embodiments of the present invention;

FIG. 3 illustrates a representative embodiment of a browser window for accessing the Internet;

FIG. 4 illustrates a representative embodiment of a system for providing check-in services to a user of a mobile device; and

fig. 5 shows a representative flow diagram illustrating the steps of a registration method in accordance with some embodiments of the present invention.

Detailed Description

A description will now be given of embodiments of the present invention with reference to the accompanying drawings. It is expected that the invention may take many other forms and circumstances and therefore the following disclosure is intended to be illustrative and not limiting and the scope of the invention should be determined by reference to the appended claims.

Systems, methods, and non-transitory computer-readable media storing instructions for providing check-in services are disclosed. According to some embodiments of the present invention, a method for providing registration services may be provided to a system having a mobile device and a registration-enabled network. Certain embodiments of the method include locating a registration-enabled network when the mobile computing device is within sufficient physical proximity to the registration-enabled network; accessing a registration-enabled network; and providing registration information to the registration-enabled network to cause a user of the mobile computing device to register with an entity that provides the registration-enabled network.

In some embodiments, the method further comprises determining whether there are any additional actions available to the mobile device from the registration-enabled network; providing the additional action to the user via the mobile device when the additional action is available; and receiving input from the user that causes the mobile device to take the additional action. The additional action may be one or more actions selected from: providing payment to an entity operating a registration-enabled network; providing additional information about the user to the registration-enabled network; providing purchase information to a registration-enabled network; using the mobile computer device to fill out paperwork required to complete the enrollment of the user at the enterprise operating the enrollment-enabled network; providing customer loyalty information from the mobile computer device to the check-in enabled network; providing a coupon to or from a mobile computer device; guiding or directing the user within the store, location, and/or other enterprise operating the registration-enabled network; tracking a user within a store operating a check-in enabled network; completing a checkout transaction associated with the purchase of the item within the store operating the registration-enabled network; directing the user to a parking location for order pickup; obtaining a list of special requests (e.g., high chair, seat preferences, and/or any other request) and/or conveniences (e.g., wheelchair accessibility, allergy notifications, and/or any other convenience) for a user; tracking the arrival and readiness of a user's party for sitting at a restaurant; notifying the user of the updated status by an action selected from the group consisting of: a text message; notification by a registration application; an automated telephone call; an email; a notification method provided by the mobile computer device; and/or any other suitable notification method; generating a notification to a holder of an account for enrollment that an enrollment event has occurred; obtaining, by a mobile computer device, an authentication of a user; and/or any other suitable action.

In some embodiments, when the additional action involves providing payment for the good or service to an entity operating the registration-enabled network, the payment is optionally provided to the business while protecting the user's personal information. While the personal information of the user may be protected in any suitable manner, in certain embodiments, the personal information of the user is protected by storing the payment information of the user at a third party repository such that the actual funds transfer occurs between the repository and the business.

The repository may obtain authorization for the funds transfer in any suitable manner, including, without limitation, obtaining authorization for the funds transfer from the user via the enrollment-enabled network and the mobile computer device. Alternatively, in certain embodiments, the repository may obtain authorization for the funds transfer from the user via a third party network and/or a mobile computer device.

According to some other embodiments of the present invention, a method for providing a registration service includes providing a registration-enabled network using a wireless network device, detecting when a mobile computer device attempts to access the registration-enabled network, establishing a connection between the mobile computer device and the registration-enabled network, and receiving registration information for the registration-enabled network to cause a user of the mobile computer device to register with an entity providing the registration-enabled network.

In some embodiments, the method may further optionally include determining whether any additional actions available may be provided to the mobile device via the registration-enabled network, the additional actions, when available, being provided to the user via the mobile device; and receiving input from the mobile device to take additional action. The additional actions may include those discussed above. The user's personal information may also be protected as discussed above.

FIG. 1 and the corresponding discussion are intended to provide a general description of a suitable operating environment in which embodiments of the invention may be implemented. Those skilled in the art will recognize that embodiments of the present invention may be implemented by one or more computing devices and in a variety of system configurations, including networked configurations. However, while the methods and processes of the present invention have proven to be particularly useful in connection with systems including general purpose computers, embodiments of the present invention include utilizing the methods and processes in a variety of environments including, without limitation, embedded systems with general purpose processing units, digital/media signal processors ("DSP/MSP"), application specific integrated circuits ("ASIC"), stand alone electronic devices, and other such electronic environments.

Embodiments of the present invention include one or more computer-readable media, where each medium may be configured to include data or computer-executable instructions for manipulating data thereon. Computer-executable instructions include data structures, objects, programs, routines, or other program modules that are accessible by a processing system, such as a processing system associated with a general-purpose computer capable of performing various different functions or a processing system associated with a special-purpose computer capable of performing a limited number of functions. The computer-executable instructions cause the processing system to perform a particular function or group of functions and are examples of program code means for implementing steps of the methods disclosed herein. Moreover, the particular sequence of executable instructions provides examples of corresponding acts that may be employed to implement such steps. Examples of computer-readable media include random access memory ("RAM"), read only memory ("ROM"), programmable read only memory ("PROM"), erasable programmable read only memory ("EPROM"), electrically erasable programmable read only memory ("EEPROM"), compact disk read only memory ("CD-ROM"), or any other device or component that can provide data or executable instructions that are accessible by a processing system. While embodiments of the invention encompass the use of all types of computer-readable media, certain embodiments as recited in the claims may be limited to the use of tangible, non-transitory computer-readable media, and the phrases "tangible computer-readable media" and "non-transitory computer-readable media" (or plural variations) as used herein are intended to exclude transitory propagating signals per se.

With reference to FIG. 1, a representative system for implementing embodiments of the invention includes a computing device 10, which may be a general purpose or special purpose computer or any of a variety of consumer electronic devices. For example, computer device 10 may be a personal computer, notebook or laptop computer, netbook, personal digital assistant ("PDA") or other palmtop device, smart phone, tablet computer, workstation, minicomputer, mainframe, supercomputer, multiprocessor systems, network computer, processor-based consumer electronics, a computer device integrated into another device or vehicle, and the like.

Computing device 10 includes a system bus 12 that may be configured to connect the various components thereof and enable data to be exchanged between two or more components. The system bus 12 may include one of several bus structures, including a memory bus or memory controller, a peripheral bus, or a local bus using any of a variety of bus architectures. Representative components connected by system bus 12 include a processing system 14 and a memory 16. Other components may include one or more mass storage device interfaces 18, input interfaces 20, output interfaces 22, and/or network interfaces 24, each of which will be described below.

The processing system 14 includes one or more processors, such as a central processor and optionally one or more other processors designed to perform specific functions or tasks. Which is typically a processing system 14 executing instructions provided on a computer readable medium such as memory 16, a magnetic hard disk, a removable magnetic disk, magnetic cassettes, an optical disk, or a communications connection also considered to be a computer readable medium.

Memory 16 includes one or more computer-readable media that may be configured to include data or instructions for manipulating data thereon, and that may be accessed by processing system 14 via system bus 12. Memory 16 may include, for example, ROM28 for permanently storing information and/or RAM 30 used to temporarily store information. ROM28 may include a basic input/output system ("BIOS") having one or more routines for establishing communications, such as during start-up of computer device 10. RAM 30 may include one or more program modules, such as one or more operating systems, applications, and/or program data.

One or more mass storage device interfaces 18 may be used to connect one or more mass storage devices 26 to the system bus 12. The mass storage device 26 may be incorporated into the computer device 10 or may be a peripheral device to the computer device 10 and allows the computer device 10 to hold large amounts of data. Optionally, one or more of the mass storage devices 26 may be removable from the computer device 10. Examples of mass storage devices include hard disk drives, magnetic disk drives, tape drives, and optical disk drives. The mass storage device 26 may read from and/or write to a magnetic hard disk, a removable magnetic disk, a magnetic tape cartridge, an optical disk, or another computer readable medium. The mass storage device 26 and its corresponding computer-readable media provide nonvolatile storage of data and/or executable instructions, which may include one or more program modules, such as an operating system, one or more applications, other program modules, or program data. Such executable instructions are examples of program code means for implementing steps of the methods disclosed herein.

One or more input interfaces 20 may be employed to enable a user to input data and/or instructions to computing device 10 via one or more respective input devices 32. Examples of such input devices include a keyboard and alternative input devices, such as a mouse, trackball, light pen, stylus or other pointing device, microphone, joystick, game pad, satellite dish, scanner, video camera, digital camera, and the like. Likewise, examples of an input interface 20 that can be used to connect an input device 32 to the system bus 12 include a serial port, a parallel port, a game port, a universal serial bus ("USB"), an integrated circuit, a firewire ("IEEE 1394"), or another interface. For example, in some embodiments, input interface 20 comprises an ASIC designed for a particular application. In another embodiment, the ASIC is embedded and connected to an existing circuit building block.

One or more output interfaces 22 may be employed to connect one or more corresponding output devices 34 to the system bus 12. Examples of output devices include a monitor or display screen, speakers, printer, multifunction peripheral, and so forth. The particular output device 34 may be integral with or peripheral to computer device 10. Examples of output interfaces include video adapters, audio adapters, parallel ports, and the like.

One or more network interfaces 24 enable computer device 10 to exchange information with one or more other local or remote computer devices, shown as computer device 36, via a network 38, which may include hard-wired and/or wireless links. Examples of a network interface include a network adapter for connecting to a local area network ("LAN") or a modem, a wireless link, or other adapter for connecting to a wide area network ("WAN"), such as the Internet. Network interface 24 may be incorporated with or peripheral to computer device 10. In a networked system, accessible program modules, or portions thereof, may be stored in the remote memory storage device. Further, in a networked system, the computer device 10 may participate in a distributed computing environment in which functions or tasks are performed by multiple networked computer devices.

Thus, those skilled in the art will recognize that embodiments of the present invention may be implemented in many types of system configurations in a number of different environments, and FIG. 2 provides a representative networked system configuration that may be used in connection with embodiments of the present invention. The representative system of FIG. 2 includes a computer device, shown as client 40, connected across network 38 to one or more other computer devices, shown as client 42 and client 44, and one or more peripheral devices 46. Although fig. 2 illustrates a client 40 connected to network 38, two additional clients, client 42 and client 44, one peripheral device 46, and an optional server 48 that may be a printer server, alternative embodiments include more or fewer clients, more than one peripheral device, no server 48, and/or more than one server 48 connected to network 38. Other embodiments of the present invention include local, networked, or peer-to-peer environments in which one or more computer devices may be connected to one or more local or remote peripheral devices. Embodiments in accordance with the invention also encompass single electronic consumer devices, wireless networking environments, and/or wide area network environments such as the Internet.

As such, certain embodiments of the present invention encompass a cloud-based architecture in which one or more computer functions are performed by one or more remote computer systems and devices at the request of a local computer device. Thus, returning to FIG. 2, client 40 may be a computer device having a limited set of hardware and/or software resources. Since client 40 is connected to network 38, it may be able to access the provided hardware and/or software resources across network 38 by other computer devices and resources, such as client 42, client 44, server 48, or any other resource. Client 40 may access these resources through an access program, such as a web browser, and may deliver the results or resources of any computer functionality to the user of client 40 through the access program. In such a configuration, the client 40 may be any type of computer device or electronic device discussed above or known to the cloud computing world, including conventional desktop and laptop computers, smart phones and other smart devices, tablet computers, or any other device capable of providing access to remote computing resources through an access program such as a browser.

To minimize the need to download and/or install programs on a user's computer, certain embodiments of the present invention utilize existing and/or new web browser technology. Many browser programs currently exist or are under development and it would not be possible to enumerate all such browser programs, but non-limiting examples of such programs include Microsoft corporation's Internet Explorer, Mozilla Firefox, Google Chrome, Apple Safari, Opera's browser, and myriad browsers specifically configured for a particular device, such as an Internet-connected smartphone. The precise display for each browser may be different for different browsers and most browsers are moderate to highly configurable in order to vary the precise display, fig. 3 shows a representative embodiment of a browser window 50 that is similar to the browser window that might be displayed on a user's computer device. It will be appreciated that many of the features described below with respect to the illustrated browser window 50 are optional or alternatively displayed or hidden according to the desires of the user, but each feature is typical or illustrative of a feature common to many browser programs.

According to some embodiments, the browser window 50 of FIG. 3 includes a title bar 52. The title bar 52 is often used to display the page name of any page being actively viewed. Most commonly, the displayed page name is selected by the administrator of the website being viewed, and often includes one or more phrases associated with the website and/or administrator of the page being viewed. In some embodiments, the browser window 50 also includes a menu bar 54, which includes items that can be selected to provide access to various menu functions, as is well known in the art. Of course, in some embodiments, the menu functions provided in menu bar 54 vary depending on the particular browser program, among other considerations, and access to the menu functions may be provided other than through a menu bar similar to menu bar 54.

The browser window 50 of fig. 3 also includes (according to some embodiments) an address bar 56, which includes a plurality of browser controls 58 and an address entry area 60 in the browser window 50 shown in fig. 3. In some embodiments, the browser control 58 and address input area 60 facilitate browsing using windows, allowing a user to, for example, back one or more pages, advance one or more pages, refresh a page, and/or type in an address of a destination website to directly access the page. Such browser features are well known in the art and need not be discussed further.

In some embodiments, the browser window 50 also includes a bookmark column 62, which the user may populate 62 with the bookmarks for the most frequently visited web pages, so that the user may quickly revisit the page by clicking on the associated bookmark button. In some of the most common browser programs, as shown in FIG. 3, a user may open multiple different websites simultaneously through various tabs 64, and the browser may provide quick access to, switch between, and manage the various open sites. In some embodiments, each tag 64 provides access to an open web site. The tabs 64 facilitate navigation between different open web sites. The content of each open and actively viewed website may be displayed in the content area 66. Thus, the content displayed in the content area 66 may vary depending on which tab 64 is selected and which website is being viewed.

While the tabs facilitate navigation between different websites in some embodiments, the browser window 50 optionally includes features to facilitate navigation within the website, as is known in the art. Specifically, in some embodiments, the browser window optionally includes one or more scroll bars 68. As is known in the art, when a portion of a website being viewed falls outside of the viewable portion of the content area 66, the user may use the scroll bar 68 to access the non-viewable portion.

Many currently available browser programs allow for the installation of additional features, such as through what is commonly referred to as a "browser extension". Browser extensions are becoming more and more common in today's browser programs and, where not standard, have become one of the means for extending the functionality of browser programs. Other mechanisms and installed programs are often available to provide similar functionality for browsers that do not currently support browser extensions. Some embodiments of the invention utilize browser extensions or similar formats to provide functionality according to embodiments of the invention. The use and installation of browser extensions is typically significantly less complex and less complex than the use and installation of separate programs, and is not as computer-enhanced.

Methods according to embodiments of the present invention are provided using a user's mobile computing device, and as described above, may be provided using a stand-alone program on the device, using a browser extension installed on the device, and/or through a browser interface. Fig. 4 illustrates the main components of an illustrative configuration of devices and parties according to features of an embodiment of the invention. A user of the present registration system accesses the system through his mobile device, shown in fig. 4 as mobile device 70. The mobile device 70 may be any type of mobile device that is currently available, whether or not specifically discussed herein (e.g., a smartphone, a cellular phone, a PDA, a tablet, a laptop, a feature phone, a handheld computing device, and/or other mobile device), or that later becomes available. It has become common to use applications to provide functionality to devices such as the mobile device 70, and embodiments of the present invention include using applications to provide the functionality discussed herein.

In certain embodiments, the mobile device 70 is at least intermittently communicatively connected to one or more other devices. In many cases, the mobile device 70 may be communicatively connected to the network 38 (e.g., the Internet) through a wide area connection, typically wireless, such as a cellular site 72 provided and operated by a mobile provider 74 or an entity affiliated with the mobile provider 74. For example, many mobile devices are purchased under contract from a mobile provider and are used to make phone calls and send data to and from the network 38, allowing the user to access and connect anywhere a wide area connection is available. At least some of the features of embodiments of the present invention may be provided using a connection between the mobile device 70 and the network 38 provided by a third party, such as the mobile provider 74.

In some embodiments, when the user of the mobile device 70 is substantially physically proximate to the enterprise 76 (either a wireless network maintained by the enterprise 76 or a wireless network provided for the enterprise 76), the user's mobile device is configured to access a local area connection, typically wirelessly, provided by the wireless access device 78 of the enterprise 76. The wireless access device 78 may be any desired type of access device (e.g., wireless access point, wireless router, etc.) and may use any desired communication mechanism and protocol (e.g., bluetooth, IEEE 802.11, etc.), including those now utilized or later devised. While references are made herein to businesses such as business 76, it should be understood that such references are merely exemplary, and embodiments encompass the use of local area networks maintained by or at a residence, by or at a school, by or at a mobile device, by or at a church, and/or by or at any desired location or entity.

When a user of one of the mobile devices 70 enters a physical area covered by the enterprise's local area network, the user may utilize (directly or indirectly) the mobile device 70 to access the enrollment features provided by the enterprise using, for example, an enrollment application on the mobile device 70. While the remaining examples discussed herein will utilize a registration application on a mobile device to provide the features discussed herein, it should be kept in mind that embodiments of the present invention encompass the provision of such features, for example, through a web portal accessed by a browser of the mobile device, through a browser extension, and/or using any other desired mechanism.

Fig. 5 illustrates an exemplary process by which the registration application on the mobile device 70 provides features to the user of the mobile device. According to some embodiments, execution begins at step 80, where the user accesses the mobile device 70 and opens or accesses a registration application. Execution then proceeds to decision block 82, where the registration application utilizes the communication capabilities of the mobile device (e.g., telephone, wireless (802.11), bluetooth, and/or any other suitable method) to determine whether any registration-enabled networks are available. If no registration-enabled network is available, then execution loops here until the registration-enabled network becomes available or execution ends (e.g., the user ends the registration application).

The enterprise 76 providing the local area network provides a registration-enabled local area network. When the local area network is a registration-enabled local area network, it is distinguished from a standard local area network in some way. The network may provide additional security features, may use additional or different communication protocols, and may identify itself to access devices (such as mobile device 70) and programs (such as a registration application on mobile device 70) differently than standard networks. This allows the registration application of the user to recognize the registration-enabled network for possible connections and registrations.

In some embodiments, once the registration-enabled network is located, execution proceeds to decision block 84, where a determination is made as to whether to register with the network. This may involve displaying available check-in enabled networks to the user and allowing the user to select one of the available check-in enabled networks (e.g., the one corresponding to enterprise 76 in which the user wishes to check-in). In some embodiments, when the user selects a network to register with, the system optionally uses user information stored by the user's mobile device 70 (e.g., in a registration application) or provided by the user at the time of registration to communicate with the network and register.

Thus, in some embodiments, if the user elects to register with the network, execution proceeds to step 86 where the mobile device 70 accesses the network and step 88 where the mobile device 70 provides registration information. Encryption or other security techniques may be used to provide the information, as is known in the art. In some embodiments, enrollment notifies enterprise 76 that the user of mobile device 70 is at enterprise 76 and allows enterprise 76 and the user to act accordingly, such as by placing the user in a queue to be seen, or taking any other action as will be discussed further below.

However, if the user does not choose to register with an available network (e.g., the network that the user wishes to register with is not available), then execution loops back to decision block 82. The mobile device 70 may then manually or automatically refresh the available registration-enabled networks from time to time until the desired registration-enabled network is available (e.g., sufficiently physically proximate to and located by the user's mobile device 70).

The registration information for the user may be manually entered by the user at the time of registration, or the registration information may have been previously entered by the user (or another person, including, without limitation, the user's legal guardian) and may be automatically transmitted by the user's mobile device 70 (e.g., by the registration application) over the registration-enabled network.

In some embodiments, the information transmitted by the mobile device 70 may include the user's unique registration ID (and/or unique transaction ID for one or more transactions performed by the user (as discussed below)), and in some embodiments, the information transmitted by the mobile device is optionally limited to the user's unique registration ID (and/or transaction ID), thereby preventing others from intercepting the user's personal data over a wireless link (and/or any other suitable network connection). Thus, the user has previously set his or her information using a central repository of information maintained by (or otherwise associated with) the enrollment provider. Such information may include, but is not limited to, identification information such as name, address, telephone, email, and any other contact information, medical information (such as prescriptions, medical records, healthcare provider contact information, medical records, and any other medical information), payment information such as credit card information, debit card information, bank account information, PayPal, or other electronic payment account information, any other type of payment information, and/or any other type of information related to the user, the business 76, or any transaction that will occur between the user and the business 76. Then, when the user registers and the mobile device 70 sends the user's registration ID (and/or specific transaction ID) to the enterprise 76 through the registration-enabled network, the enterprise 76 securely contacts the central repository and can retrieve the user's previously stored information using the user's unique registration ID (and/or transaction ID).

In various examples, the enterprise 76 requests certain information from a central repository. The central repository then determines that access to the requested information requires authorization by the user. While this determination may occur in any suitable manner, in certain embodiments, the determination occurs based on the nature of the information (e.g., medical information or records may always be subject to authorization requirements, while address information is not) and/or based on preferences previously identified by the user (such as providing the information to a central repository). In certain embodiments, once the central repository has identified a need for authorization, the central repository (or the entity providing the central repository) contacts the user to request authorization. The central repository may contact the user using the registration application on the local network (and/or any other suitable communication channel) and the user's mobile device 70. Alternatively, in some embodiments, the central repository uses a mechanism to request authorization that is independent of the local network (and/or other networks provided for or by enterprise 76) to ensure that enterprise 76 cannot falsely indicate that authorization has been received. For example, in some embodiments, in addition to using a connection between the mobile device 70 and the internet (e.g., using a connection provided by the mobile provider 74), the central repository requests authorization through the registration application. As another example, the central repository requests authorization through email, text message, and/or any other suitable means.

In some embodiments, the user is provided with additional control over the posting of information to the enterprise 76. In a first example, enterprise 76 notifies users of information that enterprise 76 wishes to obtain at enrollment, and the users authorize enterprise 76 to retrieve the information by providing the user's unique enrollment ID (and/or a specific transaction ID) and/or by responding to an authorization dialog provided by the enrollment application for communicating authorization of enterprise 76 with the user's enrollment ID. In another example, the enterprise 76 identifies information about the user that it wishes to receive after the user has registered, and requests authorization from the user over the local network (and/or another suitable communication channel). In both examples, the enterprise 76 delivers authorization to the central repository along with the request for information.

In some cases, the user may optionally selectively authorize the publication of less than all of the information requested by enterprise 76. For example, the enterprise 76 may request home and cell phone numbers, addresses, and dates of birth. In this example, the user may believe that the needs of enterprise 76 justify publishing all of the requested information except for the birth date, and may authorize publishing all of the information except for the birth date. Limited publication of less than all of the information requested may occur automatically (e.g., publication is automatically controlled by a user's previously established rules), semi-automatically (e.g., a user authorizes publication of information, but only information allowed by previously established rules), and/or under the direct control of a user at the time of the request (e.g., a user authorizes each publication of information).

In some embodiments, the enrollment process is not limited to notifying the enterprise 76 that the user has arrived, but may also provide additional actions to the user and the enterprise 76. The provision of additional information about the user is just one example of additional actions that may occur at or after the time of the registration. Thus, returning to FIG. 5, execution proceeds to decision block 90, where a determination is made as to whether there are any additional actions available to the user of the mobile device 70 or the enterprise 76. If additional actions are found, execution proceeds to decision block 92, where a determination is made as to whether any available additional actions are taken. If so, execution proceeds to step 94, where any steps required to take additional action are performed. Examples of additional actions may vary according to the circumstances and needs of the user and/or enterprise 76.

As another example in the medical field (and/or any other suitable field), enterprise 76 may wish to provide users with the opportunity to fill out any required registration forms using mobile device 70 (and/or otherwise), thereby reducing the workload on the receptionist. Users benefit from not having to wait in line for registration and fill out the registration form. Thus, when the user arrives at the medical office, the user is aware that the enterprise 76 provides the registration feature or becomes aware, such as by a logo design (and/or in any other suitable manner) that is posted at the medical office. In some embodiments, the user then accesses his or her mobile device 70 and opens or otherwise accesses the registration application. The application finds an available network with the enabled enrollment feature and displays the available network. The user selects a network and the registration application notifies the enterprise of the user's arrival. As previously discussed, additional information may be obtained.

Also, in some embodiments, the enterprise 76 has software that is notified of the arrival of the user and is able to look up the user in the appointment schedule and notify (and/or otherwise prepare) office assistants, attendants, and or other personnel of the user's arrival. The enterprise software may also have the option of pushing any forms that the customer must complete. In some embodiments, the user then completes the paperwork and electronically signs the document on his or her mobile device 70. In some such embodiments, the completed and signed document is then returned to enterprise 76, and the enterprise software is updated and the appointment proceeds through the workflow process, without any time consuming interaction between the user and the office assistant/attendant and without any user queuing to wait.

In some cases, other additional actions are optionally made available. For example, users arriving at a medical appointment are often required to provide medical insurance information and/or make a common payment at the time of service. The user's insurance information may be stored by the central repository as discussed above and may be provided to the enterprise 76 upon request and/or upon authorization of the user using the enrollment application. In some embodiments, the registration application also allows the user to make payments, such as a common payment. The payment may be made without issuing any confidential payment information for the user.

For example, the user may store payment data for providers having a check-in application (and/or in any other suitable repository), including credit card payment data for one or more credit cards, medical insurance card payment data, check and/or savings account payment data, and/or any other suitable data. In some embodiments, when a user is connected to the registration-enabled network, enterprise 76 requests payment for services that have been or will be provided. In some such embodiments, the user then uses his or her registration application to view the payment request, select a payment source from the available sources, and authorize the payment. When payment is authorized and completed, the enrollment application need not send the user's confidential payment data to the enterprise 76. Alternatively, the one-time authorization is sent to enterprise 76, which uses the authorization to receive payment from the enrollment application provider. Thus, the enrollment application and associated features provide an additional layer of security for the user's private information.

Other examples may occur in a retail context (and/or any other suitable location). The user arrives at the business 76, such as at a grocery store or department store. Again, when the user arrives at the store, the user is aware that the business 76 provides an enrollment feature or becomes aware, such as by a logo pattern posted at the store. The user then accesses his or her mobile device 70 and opens or otherwise accesses the registration application. The application finds an available network with the enabled enrollment feature and displays the available network. The user selects a network and the registration application notifies the enterprise of the user's arrival. Additional information may be obtained as previously discussed, including, in this example, customer loyalty information, coupons previously stored by the user, user preferences, special requests, and/or any other suitable information.

Enterprise 76 may also immediately provide any available periodicals, such as weekly or daily, to the user via the registration application. Additionally, the user may be provided with an opportunity to search for items sold by the store, such as looking for "children's bicycles" or any other suitable search related to the supply of the business 76. In some embodiments, the store may use multiple networked units provided throughout the store (and/or other locations) to assess the relative signal strength between the units and the user's mobile device 70, to triangulate the user's location within the store and provide directions to the user through the mobile device 70 and the check-in application that guide the user to a desired location.

In some embodiments, when the user completes his or her shopping experience and checks out, the retailer logs all items into the cash register and creates a total. In some such embodiments, the purchaser reviews the total and chooses to pay the total through the registration application. Additionally and alternatively, in certain embodiments, the user utilizes the enrollment application to apply coupon deposits stored by the user and/or available through the enrollment system. When payment is to occur, the total may be sent directly to the mobile device 70 and the registration application through a scanning operation performed by the mobile device, by entering a code provided by the retailer at the checkout point, by triangulation of the user's location, by geolocation techniques, and/or by any other relevant means. When the user checks and pays for the total, the payment may be processed as discussed above, the user selects a payment source and makes the payment, and the retailer is never aware of or obtains the user's payment information. In some embodiments, the retailer updates the loyalty account information of the user, and the update is linked to the check-in account information.

The enrollment features and benefits as discussed herein may be provided to the enterprise 76, such as a medical office, retailer, food provider, hotel, motel, service provider, recreational fitness center, repair shop, laundromat, and the like, at little to no cost. When each enterprise 76 signs up for the check-in system, it provides its exact physical address to the check-in provider. In some embodiments, the enrollment provider can then use this address information to provide additional features to the user. For example, a user of the mobile device 70 may access the enrollment application to perform a search for the enterprise 76 that provides the enrollment feature. The user may be provided with a map of the city or other location in which the user is currently located or traveling or a map of any desired location (e.g., for future planning). The location of the business 76 providing the enrollment features as discussed herein may be marked on the map with relevant information such as business type. In some cases, the user is provided with an opportunity to make a reservation or appointment, and the user can then register upon arrival as discussed above.

Additionally, in some embodiments, the enterprise 76 is optionally provided with an opportunity to purchase search terms and/or advertise with respect to the enrollment system. Then, in some embodiments, when the user operates the registration application and the enterprise 76 has purchased an advertisement, the advertisement (e.g., an advertisement purchased and/or otherwise provided by the enterprise 76) is displayed to the user. Alternatively, when a user performs a keyword search using the enrollment application and the business 76 has purchased a related keyword, the business 76 may be characterized in the search results.

As a further extension of these concepts, in some embodiments, the user uses a registration application to place an order prior to arrival. Thus, a user may use a map, an advertisement, or some other search feature to locate a desired business 76, such as a fast food restaurant. In some embodiments, upon selection of the business 76, the registration application obtains a menu or other ordering information for the business and provides that information to the user who uses the registration application to place the order. In some embodiments, where the user's personal information is not sent to the enterprise 76, the user may even use the registration application to pay for the order in a manner similar to that discussed above. All of this may occur before the user is connected to the enterprise's home network. Alternatively, the registration application and the mobile device 70 communicate by other means, such as using a cellular site 72 and an internet connection provided by a mobile provider 74 or using another connection to the internet available to the mobile device 70 (e.g., bluetooth, WiFi, etc.).

Various options may be used to provide the user with his or her order (and/or other goods, services, convenience, etc.) immediately upon arrival at the enterprise 76. As one example, when a user arrives at a business, he or she logs into the business using a logging application in a manner similar to that discussed above. Upon check-in, the enterprise 76 may direct the user to the appropriate parking lot (e.g., to pick up the user order) using the check-in application, or the user may pass through the drive-thru service window as normal and know that the order will be ready shortly after check-in. As another alternative, when placing an order, a registration application is used to query the user whether the system is authorized to track the user's location using the tracking features of the user's mobile device (e.g., GPS, cellular tower triangulation, etc.) and provide the location to enterprise 76. The user's location information may be provided to the enterprise 76 upon user authorization, so the enterprise 76 may know where and when the user will prepare the user's order so that it will be ready immediately upon user arrival. Likewise, the restaurant may use the location information to determine that the user will not arrive at his or her scheduled appointment time, and may rearrange the queue to service other customers while still maintaining an appointment for the user's arrival.

There are other examples of additional actions that may be taken after check-in to the enterprise. For example, once a user has registered at enterprise 76, in some embodiments, the registration application becomes interactive in one or more of a variety of ways. In a restaurant (and/or another enterprise), for example, the application may allow the user to identify how many people are in the user's party and whether all members of the party are present. If not all members of the party are present, the application may allow the user to update the arrival status as the members of the party arrive so that the restaurant knows when to sit the party. At the same time, the user may be placed in a queue in the restaurant. The restaurant may inform the user of his or her wait time (and changes in wait time over time), and may even use the notification features of the mobile device (ring tone, vibration, voice announcement, etc.) to inform the user that the restaurant is ready to sit the user's party. Thus, the restaurant will no longer need to provide a separate notification device to the guest as sometimes happens currently.

In some cases, the notification to the user may occur regardless of whether the user is within range of the enterprise's local registration-enabled network. Such notification may occur with or without disclosing information about the user to enterprise 76. In one example, the enterprise 76 may notify the provider of the check-in service/application of the relevant information (updated latency, readiness to get a party to sit, etc.), and the provider of the check-in service or application may then contact the user through a text message, an automated phone call, through the check-in application, and/or in any other suitable manner capable of communicating the relevant information. In another example, enterprise 76 optionally causes the registration application to request additional information from the user (e.g., a user phone number associated with the mobile device) and then use that information to contact the user (e.g., by text message, automated phone call, real-time phone call by personnel of enterprise 76, and/or in any other suitable manner).

While some forms of security have been previously discussed herein, additional levels or kinds of security may also be provided. For example, in some cases, information provided to users of enterprise 76 may be provided in a manner that limits the amount of time enterprise 76 may electronically store the information. Thus, the user's information may expire after a certain amount of time, presumably no longer needed by the enterprise 76 to access the information.

As another example of enhanced security, additional protection may be used to protect a unique user enrollment ID (and/or a unique transaction ID (as discussed below)) provided by an enrollment application to prevent others from attempting to use the user's enrollment ID (and/or transaction ID). In some embodiments, each user has a single unique registration ID for all purposes. In some embodiments, in embodiments that enhance security, the enrollment application generates a new unique enrollment ID (and/or transaction ID) at each enrollment so that it will not function properly if the enrollment ID (and/or transaction ID) is intercepted by another party or if the enterprise 76 (or dishonest employee of the enterprise 76) will attempt to use the enrollment ID (and/or transaction ID) elsewhere.

In some embodiments, to further protect the user and/or enterprise, the system creates a unique transaction ID (as described above) associated with one (or in some cases more than one) transaction between the user and a particular enterprise. In some such embodiments, the transaction ID is attached to (and/or otherwise associated with) the user's registration ID and the business's registration ID. Additionally, in some such embodiments, most (but not all) of the actions (e.g., provision of insurance information, payment, completed form, registration procedure, and/or other additional actions) reference a corresponding transaction ID.

In some embodiments, the system uses the transaction ID to ensure that additional actions (as discussed below) can only be implemented if the transaction with the corresponding transaction ID is open or pending. In certain other embodiments, when the transaction is closed (e.g., closed by the client, timed out, expired, completed, checked out by the user, or otherwise left the enterprise, and/or the transaction otherwise terminated), additional actions cannot be performed under the ID unless the user previously authorized such actions.

In one example, when a patient uses an embodiment of the system to register with a doctor's office, a transaction begins and a transaction ID is assigned to that particular transaction. In this example, as the patient completes the required form, payment for a single common payment is authorized, the office is authorized to bill third party insurance, the office is allowed to share relevant patient information with the insurance company, the office is allowed to upload medical information (e.g., laboratory reports, diagnoses, etc.) to the patient's personal health database, the office is allowed to further access the patient's personal health information for a period of time not exceeding sixty days from the patient's access to the office, a transaction ID is associated with each such action. In this example, even if the transaction is still open, the system will deny payment to any other business that is not authorized by the patient, and will further deny further payment to the doctor's office at that transaction ID unless additional authorization is given. Further, in this example, the system will further prevent the doctor's office from viewing the patient's personal health information after an authorized sixty-day period.

While the transaction ID (and user and/or business registration ID) may be set at any suitable time and in any suitable manner, in some embodiments, the transaction ID is created as part of the registration process for specific access to the business before the actual registration process occurs (e.g., when an appointment is made) and/or at any other suitable time. In fact, in some embodiments, the transaction ID is created when the reservation is made, and the transaction is maintained in a pending state, an inactive state, and/or another appropriate state ("pending") until further action is taken by the user (e.g., when the registration process actually occurs). In such embodiments, when a user enrolls in a business, the system will check for pending transactions (e.g., for particular authorizations, information, etc. provided by the user) during enrollment in order to provide the user with one or more enrollment options (e.g., discounts, coupons, additional benefits, services, goods, etc.).

Where the systems and methods allow pending transactions to be created (e.g., by using a corresponding transaction ID), such transactions may be terminated in any suitable manner. Indeed, in certain embodiments, such transactions are terminated by automatic expiration after a certain date, closing after a certain period of time has elapsed, closing after a certain period of user inactivity, and the like. In this manner, the transaction ID may further prevent unauthorized actions from occurring.

Further security may be provided by tracking each use of the check-in system, the user's check-in ID, and/or the particular transaction ID. For example, each usage may be tracked and stored at a central repository. In addition, each use of the registration ID associated with the user (and/or transaction ID) may generate an email, text message, and/or other log message to the user in a summary manner (as in a statement or periodic communication) at the time of use or from time to time. In some embodiments, the system marks suspicious activity. For example, since the enrollment system is largely intended for use by people who are physically close to the business of interest, attempts to enroll the same user in close temporal proximity but at different locations (e.g., geographically separated cities and/or other locations) may be flagged as potentially fraudulent. In some embodiments, and in such cases, any further attempts at registration are disabled until the authentication program ensures that the user has control of his mobile device 70 and his registration information.

Additional security may be provided at the mobile device 70 by the registration application in a manner known in the art. For example, because the check-in application may be used to make payments, in some embodiments, the check-in application will require a password and/or other authentication steps to access the check-in application and/or the payment functionality of the check-in application. In some embodiments, the authentication step includes biometric authentication (such as face matching authentication, fingerprint authentication, etc.), password or other input authentication, question/answer authentication, and/or any type of authentication known in the art. In some embodiments, the security of the mobile device ensures that the mobile device 70 can be secured from theft and the check-in application can be used fraudulently.

The system and method may be modified in any suitable manner. Indeed, in some embodiments, instead of requiring the user's mobile device to register with the enterprise prior to the user registering with the enterprise, the user's mobile device (e.g., a smartphone, tablet, handheld computer, cellular phone, feature phone, and/or any other suitable known or new mobile device) is configured (e.g., via an application installed on the device and/or a web page accessible through the device) to register with the enterprise using the device's own communication method (e.g., its phone service, WiFi, bluetooth, etc.). Such an enrollment process may be initiated in any suitable manner, including without limitation, by having the user initiate the enrollment process via an application and/or website, by having the device prompt the user to enroll into the enterprise when the device is proximate to the enterprise (e.g., via an application and/or web page), and/or by having the device automatically initiate the enrollment process when the device is determined to be proximate to the desired enterprise. In this regard, the proximity of the mobile device to the enterprise may be determined in any suitable manner, including but not limited to using GPS location coordinates; using the multilateration of radio signals between radio towers and/or transmitters for appropriate mobile devices (e.g., cellular tower triangulation); bluetooth location technology, WiFi location technology, and/or any suitable technology capable of substantially determining the proximity of a user's mobile device to a particular enterprise location.

While many examples of the use of registration services and methods have been provided and discussed herein, the examples should be understood to be illustrative and not limiting. In fact, the enrollment service may be provided at any location or enterprise where the service may be desired. For example, check-in services may be provided at businesses that provide a variety of services, such as the auto repair/service industry, salons (hair, manicure, etc.), take-out and eating restaurants, golf courses, bowling alleys, other appointment-based sports industries, medical offices, law offices, dental offices, any other business that provides treatment and/or services, state agencies, any other office with waiting lines or lists, parking services, and so forth. The present systems and methods can be modified as needed to provide the desired characteristics.

The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A non-transitory computer-readable medium storing instructions to cause a system comprising a mobile computer device to perform a method for providing check-in services, the method comprising:

locating a registration-enabled network when the mobile computer device is within sufficient physical proximity to the registration-enabled network;

accessing the registration-enabled network; and

providing registration information to the registration-enabled network to cause a user of the mobile computer device to register with an entity associated with the registration-enabled network,

wherein the check-in information comprises a unique identifier configured to be sent to a third party information repository and used to retrieve pre-stored information related to the user from the third party information repository and transfer the pre-stored information to the entity in response to the third party information repository receiving the check-in information,

wherein the user is required to identify at least a portion of the pre-stored information and selectively authorize a portion of the transfer from the third party information repository to the entity,

wherein the user is placed in a queue once the user has registered at the entity and the entity notifies the user of the waiting time,

wherein the system tracks the user's location using the tracking features of the user's mobile computer device and provides location information to the entity, the entity uses the location information to determine when an order for the user will be prepared so that the order will be ready immediately upon user arrival, or the entity determines that the user will not arrive at a predetermined time by using the location information and rearranges the user in the queue.

2. The non-transitory computer-readable medium of claim 1, wherein the method further comprises:

determining whether any additional actions are available to the mobile computer device from the registration-enabled network;

presenting, via the mobile computer device, an additional action to the user when the additional action is available; and

receiving input from the user that causes the mobile computer device to take the additional action.

3. The non-transitory computer-readable medium of claim 2, wherein the additional action is an action selected from the group consisting of:

providing payment to the entity;

providing additional information about the user to the registration-enabled network;

providing purchase information to the registration-enabled network;

using the mobile computer device to fill out information required by the user to complete the registration at the entity;

providing customer loyalty information from the mobile computer device to the check-in enabled network;

providing a coupon to the mobile computer device;

applying a coupon from the mobile computer device;

guiding or directing the user within a store associated with the check-in enabled network;

tracking the user within the store;

completing a checkout transaction associated with a purchase of goods within the store;

directing the user to a parking location for order pickup;

tracking the arrival and readiness of the user for sitting at a facility;

notifying the user of the updated status through an action selected from the group consisting of: a text message; notification by a registration application; automated telephone calls; and/or e-mail;

generating a notification to an account holder of an account for enrollment that an enrollment event has occurred; and/or

Obtaining, by the mobile computer device, authentication of the user.

4. The non-transitory computer-readable medium of claim 2, wherein the additional action comprises providing a payment for goods or services to the entity, wherein the payment is provided to the entity while protecting personal information of the user.

5. The non-transitory computer-readable medium of claim 4, wherein the personal information of the user is protected by storing payment information of the user at the third-party information repository, and wherein the actual transfer of funds occurs between the third-party information repository and the entity.

6. The non-transitory computer-readable medium of claim 5, wherein the third party information repository obtains authorization for the actual funds transfer from the user via the check-in enabled network and the mobile computer device.

7. The non-transitory computer-readable medium of claim 5, wherein the third party information repository obtains authorization for the transfer of funds from the user via a third party network and the mobile computer device.

8. The non-transitory computer-readable medium of claim 2, wherein the additional action comprises obtaining information about a particular convenience of the user.

9. The non-transitory computer-readable medium of claim 1, wherein a unique transaction ID is associated with the registration information, and the method further comprises associating the transaction ID with an action approved by the user.

10. The non-transitory computer-readable medium of claim 9, wherein the method further comprises denying actions that are not associated with the transaction ID.

11. The non-transitory computer-readable medium of claim 9, wherein the transaction ID is configured to be marked off, and wherein the method further comprises allowing actions associated with the transaction ID previously approved by the user to be performed after the transaction ID is marked off.

12. A non-transitory computer-readable medium storing instructions to cause a system comprising a mobile computer device and a wireless network device to perform a method for providing check-in services, the method comprising:

using the wireless network device to provide a registration-enabled network,

detecting when the mobile computer device attempts to access the registration-enabled network;

establishing a connection between the mobile computer device and the registration-enabled network; and

receiving registration information to the registration-enabled network to cause a user of the mobile computer device to register with an entity associated with the registration-enabled network,

wherein the registration information is configured to be transmitted to the registration-enabled network when the mobile computer device is within sufficient physical proximity to the registration-enabled network,

wherein the registration information includes a unique identifier associated with at least one of the user and a current transaction,

wherein the unique identifier is configured to be electronically transmitted to an information repository to retrieve pre-stored information for the user and to cause the information repository to electronically transmit the pre-stored information to the entity in response to receiving the enrollment information,

wherein the user is required to identify at least a portion of the pre-stored information and selectively authorize a portion to be transferred from the information repository to the entity,

wherein the retrieved pre-stored information identifies the user,

wherein the information repository is configured to send the pre-stored information to the entity only after the information repository receives the unique identifier;

wherein the user is placed in a queue once the user has registered at the entity, and

wherein the entity rearranges the queue based on the location of the mobile computer device.

13. The non-transitory computer-readable medium of claim 12, wherein the method further comprises:

determining whether any additional actions are available for provision to the mobile computer device via the registration-enabled network;

receiving input from the mobile computer device to take the additional action.

14. The non-transitory computer-readable medium of claim 13, wherein the additional action is an action selected from the group consisting of:

providing payment to an entity operating the registration-enabled network;

providing purchase information to the registration-enabled network;

using the mobile computer device to provide information required by the user to complete the registration at the entity;

providing a coupon to the mobile computer device;

applying a coupon from the mobile computer device;

guiding or directing the user within a location associated with the registration-enabled network;

tracking the user within the location;

completing a checkout transaction associated with a purchase of goods within the location;

directing the user to a parking location for order pickup;

tracking the arrival and readiness of the user for sitting at a facility;

notifying the user of the updated status by an action selected from the group consisting of: a text message; notification by a registration application; automated telephone calls; and/or e-mail;

Obtaining, by the mobile computer device, authentication of the user.

15. The non-transitory computer-readable medium of claim 13, wherein the additional action comprises providing a payment for goods or services to the entity, wherein the payment is provided to the entity while protecting personal information of the user.

16. The non-transitory computer-readable medium of claim 15, wherein the user's personal information is protected by storing payment information for the user at an information repository, and wherein the actual transfer of funds occurs between the information repository and the entity.

17. The non-transitory computer-readable medium of claim 16, wherein the information repository obtains authorization for the funds transfer from the user via the check-in enabled network and the mobile computer device.

18. The non-transitory computer-readable medium of claim 16, wherein the information repository obtains authorization for the transfer of funds from the user via a third party network and the mobile computer device.

19. The non-transitory computer-readable medium of claim 13, wherein the additional action comprises obtaining information about a particular convenience of the user.

20. A non-transitory computer-readable medium storing instructions to cause a mobile computer device to perform a method for providing check-in services, the method comprising:

determining a proximity of the mobile computer device to an entity having a registration procedure;

prompting a user to register with the entity using the mobile computer device once the mobile computer device is within a set distance from the entity; and

communicating registration information from the mobile computer device to the entity to register the user with the entity,

wherein the registration information comprises a unique identifier associated with payment information,

wherein the unique identifier is configured to be electronically transmitted to a third party information repository to retrieve the payment information and information identifying the user from the third party information repository and to cause payment to be made to the entity and information identifying the user to be communicated to the entity,

wherein the user is required to identify at least a portion of the retrieved information and selectively authorize a portion of the transfer from the third party information repository to the entity,

wherein the third party information repository is configured to send the payment information to the entity only after the third party information repository receives the enrollment information;

wherein a transaction involving the unique identifier is configured to be marked as closed, an

Wherein the method further comprises allowing an action associated with a transaction previously approved by the user to be performed after marking the transaction as closed.

21. The non-transitory computer-readable medium of claim 20, further comprising allowing the user to communicate special convenience information to the entity through the mobile computer device.

22. The non-transitory computer-readable medium of claim 20, further comprising providing, by the mobile computer device, a payment to the entity for goods or services, wherein the payment is provided to the entity while protecting personal information of the user.

23. The non-transitory computer-readable medium of claim 20, wherein the personal information of the user is protected by storing payment information of the user at the third-party information repository, and wherein the actual funds transfer is configured to occur between the third-party information repository and the entity.