Patent Application
20230297559
The number and variety of applications or “apps” for mobile stations or smartphones continuously increases. One issue that hinders some potential users from obtaining an app is the user registration process. It would be useful to app providers to provide an easier or streamlined process that allows new users to sign up for access to an app.
An illustrative example embodiment of a system for registering a user includes at least one computing device that is configured to determine that a user response to a prompt was received from a remote user device. The user response indicates at least two identifiers of the user. The computing device initiates a user account for the user. The computing device determines whether a database includes additional identifiers of the user and associates information with the user account. The information, which is required for the user account, is based on the two identifiers and any additional identifiers of the user from the database. The computing device causes a request to be sent to the remote user device requesting the user to review the accuracy of the information associated with the user account and to complete creation of the user account.
The various features and advantages of at least one example embodiment will become apparent to those skilled in the art from the following detailed description. The drawings that accompany the detailed description can be briefly described as follows.
A server 22 includes at least one computing device having a processor and associated memory. In the illustrated example embodiment, the memory includes a non-transitory storage medium that contains instructions that are executable by the processor to realize the functions of the server 22 included in this description.
The server 22 includes a user communication module 24 that facilitates communications over a network 26 with remote user devices 28. The user communication module 24 comprises hardware, firmware, software or a combination of these configured to use known communication protocols. The network 26 includes, for example, the Internet and appropriate communication equipment to allow the server 22 to communicate with the remote user device 28. In some situations, the network 26 is a local area network (LAN) or an ad hoc network. Example remote user devices 28 include mobile stations, such as smartphones and portable computing devices.
The server 22 includes a registration module 30 that comprises hardware, firmware, software or a combination of them. The registration module 30 includes an input module 32 for receiving user information from the remote user device 28. The user information is provided in response to a prompt 33 that is understandable to the user. For example, the prompt 33 may be a display instructing the user to text selected information to a particular number if the user desires to acquire a product or service, such as an application that can be downloaded to and used on the remote user device 28.
The registration module 30 includes a database interface 34 that is configured to access a user information database 36 that is part of the memory of the server 22 or otherwise associated with the server 22. In the illustrated example, the user information database 36 is maintained by the entity that controls the server 22, such as a provider of the product or service that the user desires.
The registration module 30 also includes a user account creator 38 that is configured to initiate a user account when an individual desires to acquire a product or service for which a user account is needed.
The system 20 shown in
Assuming at least one individual uses a remote user device 28 to respond to the prompt by sending an appropriate text message, at 46, the user communication module 24 of the server 22 receives the user response to the prompt from the remote user device 28. The user response indicates at least two identifiers of the user. The identifiers are unique to the individual user. In an embodiment where the user response is a text message, the phone number or account number of the device from which the text message was sent is one of the at least two identifiers of the user. Other example identifiers include the user's name, birthdate or other identifying information requested through the prompt. In some embodiments, the prompt will instruct the user to send an image, such as a selfie, when sending the text in response to the prompt. In those situations, the image is one of the at least two identifiers of the user. More than two identifiers may be indicated by the user response.
At 48, the registration module 30 initiates a user account for the individual who responded to the prompt 33. The registration module 30 has information regarding the prompt 33, such as an association between the number to which a text message response was sent and the appropriate product or service the individual desires. The input module 32 of the registration module 30 identifies the user information indicated by the received response. At 50, the database interface 34 determines whether the user information database 36 includes any additional identifiers of the user. For example, the entity controlling the server 22 may offer more than one product or service. An individual may have previously created a user account with that entity that is associated with one of those products or services. In such a case, the user information database 36 may contain previously collected information from that individual. The database interface 34 can obtain that information based upon a match between the information indicated in the user response and information stored in the database 36.
At 52, the user account creator 38 associates information with the new user account by including the identifiers that were indicated in the response to the prompt and any additional identifiers that were obtained from the database 36 to include the data needed for corresponding data fields required to create a new user account. The registration module 30 pre-fills the user account information on behalf of the individual who responded to the prompt with as much information as is available to the registration module 30 at that time. In many cases, not all of the required information to establish a user account is available to the user account creator 38. Pre-populating as much as possible of the required information for establishing a new user account at 52 simplifies the user registration process for the individual.
At 54, the server 22 sends a request to the remote user device 28 requesting the user to review the associated information that has been pre-filled into the user account data and to complete creation of the user account. In a situation where all of the required information is already associated with the new user account and the user verifies the accuracy of that information, completing the user account simply requires an acknowledgement from the user. In situations where only some of the required information for establishing the user account has been pre-populated or pre-filled by the registration module 30, completing the user account involves the user providing the remaining required information.
The process summarized in
The individual user is represented at 60 in
A request dispatcher 70 provides the information included in or indicated by the request to the user account creator 38 where the account is created at 72 and the information from the request, such as a selfie image, is added at 74. The provider back end 76, which is part of the server 22 in the embodiment of
This example includes a check in process represented at 78. The check in process is used in a situation where the prompt is provided at an event that the user is attending. The check in process includes comparing the facial recognition data associated with the new user account against any video or still image data from that event to identify any video or images that will be available to that user. In this embodiment, a response to the prompt that includes a selfie or another image of the individual triggers the check in process at 78.
In this example, the user request includes an indication of the user's favorite team, which is pre-populated into the user account information at 80.
Once the user account is pre-populated with as much information as is available to the registration module 30, a text notifier 82 sends an appropriate message through an outgoing texting API 86 to the user's smartphone 28. In this example, the message texted back to the user 60 includes a link that can be selected by the user when viewing the text received at the smartphone 28.
At 90, the user selects the link from the text message. That link directs the processor of the smartphone 28 to a site for downloading the application at 92. At 94, the user is presented with a user account form that is pre-populated with the information received or obtained by the registration module 30. In this example, the user texted name and favorite team information along with a selfie image. If no other information was available from a database, such as the database 36 or 40 shown in
Once properly installed, the application allows the user 60 to obtain video or still image data through the application at 100.
Those skilled in the art who have the benefit of this description will realize how to use the pre-populating features of the disclosed example embodiments to facilitate user registration for their particular situation. Simplifying the user registration process as described above increases user adoption of products and services by streamlining the user registration and user account creation process.
The preceding description is exemplary rather than limiting in nature. Variations and modifications to the disclosed example embodiment and scenarios may become apparent to those skilled in the art that do not necessarily depart from the essence of this invention. The scope of legal protection given to this invention can only be determined by studying the following claims.
