Automatic Account Setup
The automatic account setup system uses a code with user information to streamline account creation across devices, addressing the repetitive nature of manual account setup by enabling quick and efficient account establishment on multiple systems.
Patent Information
- Application Number
- PCT/US2023/067653
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-31
- Publication Date
- 2024-12-05
AI Technical Summary
Users face a repetitive and laborious process when setting up multiple accounts on various systems, requiring manual entry of information for each account creation.
A system that generates a code, such as a QR code, on a first communication device, which includes user information and a link to an account server, allowing automatic account creation on a second communication device when scanned or sent.
Streamlines account setup by automating the process, reducing manual input and enabling quick creation of user accounts across multiple devices and systems.
Smart Images

Figure US2023067653_05122024_PF_FP_ABST
Abstract
Description
Automatic Account SetupFIELD
[0001] The disclosure relates generally to account setup on a communication device and particularly to automatically creating an account on multiple communication devices using a computer-generated code / digital certificate in a visual representation.BACKGROUND
[0002] Users today typically have a lot of different accounts. For example, a user may have a banking account, multiple social network accounts (e.g., Facebook®, Twitter®, Instagram®), a work account, multiple online shopping accounts, organization accounts, and / or the like. Setting up a lot of user accounts on multiple systems is a repetitive and laborious process. Each time the user has to create a new account, the user has to manually enter his / her information for each website / account.SUMMARY
[0003] These and other needs are addressed by the various embodiments and configurations of the present disclosure. The present disclosure can provide a number of advantages depending on the particular configuration. These and other advantages will be apparent from the disclosure contained herein.
[0004] A request is received, from a first communication device, to create a code (e.g., the request is to create a Quick Response (QR) code). The created code is for automatically creating a user account on a second communication device. For example, the second communication device may be a corporate web server. User information for automatically creating the user account on the second communication device is received. The code is created. The created code comprises at least one of the user information for creating the user account; and a link to an account server, where the account server contains the user information. The created code is sent to the first communication device. The first communication device uses the code to create the account on the second communication device.
[0005] The phrases "at least one", "one or more", “or,” and "and / or" are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions "at least one of A, B and C", "at least one of A, B, or C", "one or more of A, B, and C", "one or more of A, B, or C", "A, B, and / or C", and "A, B, or C" means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, Band C together.
[0006] The term "a" or "an" entity refers to one or more of that entity. As such, the terms "a" (or "an"), "one or more" and "at least one" can be used interchangeably herein. It is also to be noted that the terms “comprising,” “including,” and “having” can be used interchangeably.
[0007] The term “automatic” and variations thereof, as used herein, refers to any process or operation, which is typically continuous or semi-continuous, done without material human input when the process or operation is performed. However, a process or operation can be automatic, even though performance of the process or operation uses material or immaterial human input, if the input is received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be “material.”
[0008] Aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium.
[0009] A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
[0010] A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part ofa carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0011] The terms “determine,” “calculate” and “compute,” and variations thereof, as used herein, are used interchangeably, and include any type of methodology, process, mathematical operation, or technique.
[0012] T he term “means” as used herein shall be given its broadest possible interpretation in accordance with 35 U.S.C., Section 112(f) and / or Section 112, Paragraph 6. Accordingly, a claim incorporating the term “means” shall cover all structures, materials, or acts set forth herein, and all of the equivalents thereof. Further, the structures, materials or acts and the equivalents thereof shall include all those described in the summary, brief description of the drawings, detailed description, abstract and claims themselves.
[0013] As described herein and in the claims, a “code” is any type of code that can be scanned or created that produces information, such as, a Quick Response (QR) code, a color QR code, a barcode, a one dimensional bar code, a two dimensional bar code, an EAN barcode, a data matrix barcode, a PDF417 code, and / or the like. In addition, a code may also include a digital certificate that contains user account information. In this case, the digital certificate may be encrypted or protected via other mechanisms. A code may also include an encrypted file.
[0014] The preceding is a simplified summary to provide an understanding of some aspects of the disclosure. This summary is neither an extensive nor exhaustive overview of the disclosure and its various embodiments. It is intended neither to identify key or critical elements of the disclosure nor to delineate the scope of the disclosure but to present selected concepts of the disclosure in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the disclosure are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below. Also, while the disclosure is presented in terms of exemplary embodiments, it should be appreciated that individual aspects of thedisclosure can be separately claimed.BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Fig. l is a block diagram of a first illustrative system for automatically creating an account.
[0016] Fig. 2 is a block diagram of a second illustrative system for automatically filling in fields in a graphical user interface.
[0017] Fig. 3 is a flow diagram of a process for automatically creating a user account via an account server.
[0018] Fig. 4 is a flow diagram of a process for automatically creating an account directly from a code.
[0019] Fig. 5 is a flow diagram of a process for automatically filling in fields in a graphical user interface.
[0020] Fig. 6 is a diagram of an exemplary graphical user interface.
[0021] In the appended figures, similar components and / or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a letter that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.DETAILED DESCRIPTION
[0022] Fig. 1 is a block diagram of a first illustrative system 100 for automatically creating an account. The first illustrative system 100 comprises communication devices 101A-101N, a network 110, an account server 120, and server(s) 130. In addition, users 105A-105N are shown for convenience. A user 105 is a user 105 of a communication device 101.
[0023] The communication devices 101 A- 10 IN can be or may include any device can manage the use of a code, such as a Personal Computer (PC), a telephone, a video system, a cellular telephone, a Personal Digital Assistant (PDA), a tablet device, a notebook device, a smartphone, and the like. As shown in Fig. 1, any number of communication devices 101 A- 10 IN may be connected to the network 110, including only a single communication device 101.
[0024] The communication devices 101A-101N further comprise code scanners 102A- 102N, and code / certificate managers 103A-103N. The code scanners 102A-102N are used to scan codes. For example, a code scanner 102 may be a camera that is embeddedinto a smartphone. A code may contain various types of information based on how the code is created.
[0025] The code / certificate managers 103A-103N are used to manage the receipt of the codes from the account server 120 and / or the code scanners 102A-102N on the communication devices 101A-101N.
[0026] The network 110 can be or may include any collection of communication equipment that can send and receive electronic communications, such as the Internet, a Wide Area Network (WAN), a Local Area Network (LAN), a packet switched network, a circuit switched network, a cellular network, a combination of these, and the like. The network 110 can use a variety of electronic protocols, such as Ethernet, Internet Protocol (IP), Hyper Text Transfer Protocol (HTTP), Web Real-Time Protocol (Web RTC), and / or the like. Thus, the network 110 is an electronic communication network configured to carry messages via packets and / or circuit switched communications.
[0027] The account server 120 can be any networked device that can manage account information, such as, an application server, a web server, a communication server, a network server, and / or the like. In one embodiment, the account server 120 may be a type of communication device 101. In one embodiment, the account server 120 may be part of a cloud service. The account server 120 further comprises a code / certificate creator 121, an account manager 122, and user profile(s) 123.
[0028] The code / certificate creator 121 is used to generate a code / certificate based on a request from a communication device 101. The code / certificate creator 121 may create different kinds of codes / certificates. For example, the code / certificate creator 121 may create a digital certificate and / or a QR code that contains information for creating a user account on the server 130. Alternatively, the digital certificate and / or QR code may only have a link to the account server 120 (e.g., a Universal Resource Locator URL). The code could be an encrypted file.
[0029] The account manager 122 is used to manage information for individual user accounts. For example, the account manager 122 may manage different accounts for multiple users 105A-105N to create user accounts on multiple servers 130.
[0030] The user profile(s) 123 are profiles that define how the user’s account information is managed. The user profile(s) 123 defines what information is shared by the account server 120. For example, one user profile 123 may be a work profile that has the user’s work information, and one profile may be a home profile. Each user profile 123 may define different passwords, biometrics, other access methods, etc. The user profile123 may define which fields are actually sent / used to create a code. The user 105 may use different user profiles 123 to generate different codes that have different user information.
[0031] The server(s) 130 are communication devices 101 that, based on receiving a code / certificate, automatically create an account for the user 105. The server(s) 130 further comprise an account generation module(s) 131. The account generation module(s) 131 is used to get the information necessary (either from the code / certificate or from the account server 120) to automatically create a user account.
[0032] Fig. 2 is a block diagram of a second illustrative system 200 for automatically filling in fields 223 in a graphical user interface 222. The second illustrative system 200 comprises communication devices 101A-101N, the network 110, the account server 120, and an auto fill server 220.
[0033] The in Fig. 2, the communication devices 101 A-101N also comprise the code scanners 102A-102N and the code / certificate managers 103A-103N. The account server 120 is similar to the account server 120 in Fig. 2. The primary difference is that account server 120 generates codes for automatically filling fields 223 in a graphical user interface 222 versus automatically creating a user account.
[0034] The auto fill server(s) 220 are communication devices 101 that can receive a code and based on the code, automatically fill in fields 223 in a graphical user interface 222. The autofill server(s) 220 further comprise application(s) 221, a graphical user interface 222, and an auto fill module 225.
[0035] The application(s) 221 can be any application 221 that has a graphical user interface 222. For example, the application(s) 221 may be a database application, a security application, a human resource application, a web application, a financial application, an online shopping application, and / or the like.
[0036] The graphical user interface 222 can be any type of computer-based user interface that has fields 223 where a user 105 can enter data. The graphical user interface 222 comprises the fields 223. An example of a graphical user interface 222 is shown in Fig. 6.
[0037] The auto fill module 224 manages the capture of a code and uses the data from the code to automatically fill in one or more fields 223 in the graphical user interface 222. In one embodiment, the auto fill module 224 can request a user 105 to scan or send a code that is sent to the auto fill module 224. The auto fill module 224 in turn then automatically fills in the appropriate fields 223 on the graphical user interface 222.
[0038] Fig. 3 is a flow diagram of a process for automatically creating a user account viaan account server 120. Illustratively, the communication devices 101A-101N, the code scanners 102A-102N, the code / certificate managers 103A-103N, the account server 120, the code / certificate creator 121, the account manager 122, the server(s) 130, the account generation module(s) 131, the auto fill server(s) 220, the application(s) 221, and the auto fill module 224 are stored-program-controlled entities, such as a computer or microprocessor, which performs the method of Figs. 3-6 and the processes described herein by executing program instructions stored in a computer readable storage medium, such as a memory (i.e., a computer memory, a hard disk, and / or the like). Although the methods described in Figs. 3-6 are shown in a specific order, one of skill in the art would recognize that the steps in Figs. 3-6 may be implemented in different orders and / or be implemented in a multi-threaded environment. Moreover, various steps may be omitted or added based on implementation.
[0039] The idea is to create a digital certificate and / or a code that is used to automatically create a user account. Fig. 3 shows a first example of using an account server 120 that is to automatically create a user account on a server 130 (e.g., a web server).
[0040] The process starts in step 300 where the user 105, via the communication device 101, makes a request to create a code on the account server 120. The account server 120 asks the user 105 to provide their account information in step 302. For example, the account server 120 serves a web page asking for the user information. The user 105, via the communication device 101, provides the user information, in step 304, to the account server 120. The user information can include things like a username, suggested account name(s), address information, biometrics (e.g., a facial scan, a voiceprint, an iris scan, a fingerprint scan, etc.), email address(es), security questions, credit card number(s), phone number(s), password(s), a social security number, and / or the like.
[0041] A suggested account username could be a list of potential account names that the website could pick when creating the account. For example, if the user’s name is John Max Doe, the suggested account names could be johndoe, johnmdoe, john.doe, jmdoe, jdoe, etc. The password(s) may be a password that is automatically used when an account is created. The password(s) may be a temporary password that is used to initially set up an account or an initial permanent password (e.g., one that may be permanent or may be changed later on).
[0042] The account server 120 generates a code or a digital endorsement certificate in step 306. The account server 120 sends the code / digital certificate to the communicationdevice 101 in step 308. In one embodiment, the user 105, via the code scanner 102 may scan the code (e.g., where the code is on another device). The user 105, via the communication device 101, makes a request to create an account on the server 130 in step 312. The request includes the code and / or digital certificate.
[0043] The server 130 sends, in step 314, a request to validate the code / digital certificate to the account server 120. The validation of step 314 may be accomplished using a digital endorsement certificate verification if a digital certificate is used. If the digital certificate / code is not valid / expired, in step 314, the account server 120 rejects the request in step 318 and the process ends. For example, the digital certificate may have expired based on a time period associated with the digital certificate. In addition, the account server 120 may reject the request of step 314 if the necessary access methods are not supported. For example, if the account server 120 requires a biometric and the website does not support that type of biometric, the request may be rejected.
[0044] Otherwise, if the code / digital certificate is valid in step 314, the account server 120 responds, in step 316, that the code / digital certificate is valid. Step 316 may also include the user’s information (or it could be sent in a separate message).
[0045] The user information that is sent in step 316 may be based on a defined user profile 123 created by the user 105, may be based on what the server 130 needs (e.g., negotiated by the server 130), may be based on an administration, and / or the like. For example, during step 304, the user 105 could be asked to select one of multiple user profiles 123 along with whether a digital certificate / code will be used. For example, one user profile 123 may be a work profile that has the user’s work information and one user profile 123 may be a home profile that has different user information. Each user profile 123 may have different passwords, biometrics, other access methods, etc. The user profile 123 may define which types of user information are actually passed in step 316. The user 105 may have a certificate / code that is created for each user profile 123.
[0046] If the code / digital certificate is valid in step 316, the server 130, creates a valid account for the user 105 in step 320. For example, the user’s name, address, phone number(s), email address, credit card numbers, and a predefined password are created for the user account. Based on the code / digital certificate, access privileges may be automatically administered. For example, the user 105 may be given access to specific applications, databases, devices, and / or the like as part of the automatic account creation. In one embodiment, the username for signing in may be generated based on the user’s actual name. For example, if the user’s name is John Doe, the server 130 may generatethe username johndoe orjdoe@companyx.com based on an algorithm for creating the username.
[0047] If a password from the account server 120 is used, the user 105 can then log in in step 324. If a temporary password is used (either sent by the account server 120 or generated locally), the server 130 emails the user 105 the username and temporary password in step 322. The user 105 then logs in in step 324 to the server 130 using the username and temporary password and access privileges. This process could be tied to a single sign-on process where the account server 120 provides a single sign-on process. For example, the server 130 may redirect a login request to the account server 120 that manages the login process / multi-factor authentication.
[0048] The process described in Fig. 3 can be used with other servers 130 that subscribe to the account server 120. For example, the same user 105 may go to a second server 130 provided by a different company and provide the same credential / code to create an account on the second server 130. In one embodiment, a different digital certificate / code may be generated for each server 130 based on different user profiles 123.
[0049] Fig. 4 is a flow diagram of a process for automatically creating an account directly from a code. In a second embodiment, a code (or possibly a digital certificate that is encrypted with the user information) is used to create an account. Fig. 4 is an example of where the user account can be created using fields 223 in a code. The information to create the user account is stored in the code / digital certificate.
[0050] The process starts, in step 400, where the user 105 logs in and requests a unique code / certificate. The user 105 provides the user information in step 402. The account server 120 generates the code / certificate using the user information in step 404. The account server 120 sends the code / certificate to the communication device 101 in step 406.
[0051] The user 105 wants to access the server 130 in step 410. The server 130 may request the user 105 to scan or send the code / certificate that was sent in step 408. The code / certificate is then sent to the server 120 in step 412. The server 130 validates the code / certificate in step 414. If the code is a certificate, the server 130 validates the certificate (using existing certificate validation processes) and unencrypts the certificate.
[0052] In step 416, the server 130, if the code / certificate is valid, automatically creates an account (similar to described in Fig. 3) using the user information from the scanned the code / certificate. The process of using the information in the code / certificate may be based on the code / certificate comprising name / value pairs as shown below. The name / value pairs will work with any of the embodiments described herein.<username> <John Doe><address> < 842 North Sprint Crt ><city> <Salt Lake City><state> <Utah><country> <United States><ZIP code> <83723><phone number> <801-332-4637><email address> <jdoe@companyX.com><credit card number> <37719-334379-22042><default password> <HaveFunTodayl&>
[0053] While the above name / value paring is only an example, other formats may be used or required by different servers 130. For example, a space in a username may not be acceptable on some servers 130.
[0054] The server 130 uses each value pair to create a corresponding record that is part of the automatically created user account. Once the user account is created, the user 105 may be sent an email with the generated / supplied username and a temporary / default password in step 418. The user 105 can then login in step 420 with the usemame / temporary password.
[0055] Although the process is described using a digital certificate, other tokens or data can be used. For example, instead of a code / certificate, an encrypted file could be used. The server 130 can then unencrypt the file (e.g., using PKI or some other method).
[0056] Fig. 5 is a flow diagram of a process for automatically filling in fields 223 in a graphical user interface 222. In addition to automatically creating a user account, a code can be used to prepopulate fields 223 that are displayed by the server 130 via the graphical user interface 222. The process for generating a code for populating fields 223 in the graphical user interface 222 is similar to steps 400-406. In this process, the data that can be auto filled in the graphical user interface 222 may be any kind of data. For example, the data may be user account data, device data, application parameters, administration parameters, parts lists, and / or the like.
[0057] Once the code / certificate is received in step 406, the code / certificate is sent to the auto fill server 220 in step 500. The auto fill server 220 identifies the fields 223 in the code / certificate. For example, as described above, the username field (username) has a value of John Doe. This is repeated for all the name / value pairs. The auto fill server 220 identifies the corresponding fields 223 in the graphical user interface 222 in step 504.This can include filtering out any fields 223 in the code / certificate that are not in the graphical user interface 222. The auto fill server 220 automatically fills in the fields 223in the graphical user interface 222 in step 506.
[0058] Fig. 6 is a diagram of an exemplary graphical user interface 222. The graphical user interface 222 comprises a populate button 600 and fields 223 A-223N. The process can be initiated in various ways. For example, the user 105 could click on the populate button 600 to initiate sending of the code / certificate. The communication device 101 then sends the code to the auto fill server 220. As described above in Fig. 4, the auto fill server 220 identifies the corresponding fields 223 in the graphical user interface 222. The auto fill server 220 then automatically fills in the corresponding fields 223 A-223N in the graphical user interface 222.
[0059] Examples of the processors as described herein may include, but are not limited to, at least one of Qualcomm® Snapdragon® 800 and 801, Qualcomm® Snapdragon® 610 and 615 with 4G LTE Integration and 64-bit computing, Apple® A7 processor with 64-bit architecture, Apple® M7 motion coprocessors, Samsung® Exynos® series, the Intel® Core™ family of processors, the Intel® Xeon® family of processors, the Intel® Atom™ family of processors, the Intel Itanium® family of processors, Intel® Core® i5- 4670K and i7-4770K 22nm Haswell, Intel® Core® i5-3570K 22nm Ivy Bridge, the AMD® FX™ family of processors, AMD® FX-4300, FX-6300, and FX-8350 32nm Vishera, AMD® Kaveri processors, Texas Instruments® Jacinto C6000™ automotive infotainment processors, Texas Instruments® OMAP™ automotive-grade mobile processors, ARM® Cortex™-M processors, ARM® Cortex-A and ARM926EJ-S™ processors, other industry-equivalent processors, and may perform computational functions using any known or future-developed standard, instruction set, libraries, and / or architecture.
[0060] Any of the steps, functions, and operations discussed herein can be performed continuously and automatically.
[0061] However, to avoid unnecessarily obscuring the present disclosure, the preceding description omits a number of known structures and devices. This omission is not to be construed as a limitation of the scope of the claimed disclosure. Specific details are set forth to provide an understanding of the present disclosure. It should however be appreciated that the present disclosure may be practiced in a variety of ways beyond the specific detail set forth herein.
[0062] Furthermore, while the exemplary embodiments illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and / or theInternet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined in to one or more devices or collocated on a particular node of a distributed network, such as an analog and / or digital telecommunications network, a packet-switch network, or a circuit-switched network. It will be appreciated from the preceding description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system. For example, the various components can be located in a switch such as a PBX and media server, gateway, in one or more communications devices, at one or more users’ premises, or some combination thereof. Similarly, one or more functional portions of the system could be distributed between a telecommunications device(s) and an associated computing device.
[0063] Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and / or communicating data to and from the connected elements. These wired or wireless links can also be secure links and may be capable of communicating encrypted information. Transmission media used as links, for example, can be any suitable carrier for electrical signals, including coaxial cables, copper wire and fiber optics, and may take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
[0064] Also, while the flowcharts have been discussed and illustrated in relation to a particular sequence of events, it should be appreciated that changes, additions, and omissions to this sequence can occur without materially affecting the operation of the disclosure.
[0065] A number of variations and modifications of the disclosure can be used. It would be possible to provide for some features of the disclosure without providing others.
[0066] In yet another embodiment, the systems and methods of this disclosure can be implemented in conjunction with a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device or gate array such as PLD, PLA, FPGA, PAL, special purpose computer, any comparable means, or the like. In general, any device(s) or means capable of implementing the methodology illustrated herein can be used to implement the various aspects of this disclosure. Exemplary hardware that can be used for the present disclosure includes computers, handheld devices,telephones (e.g., cellular, Internet enabled, digital, analog, hybrids, and others), and other hardware known in the art. Some of these devices include processors (e.g., a single or multiple microprocessors), memory, nonvolatile storage, input devices, and output devices. Furthermore, alternative software implementations including, but not limited to, distributed processing or component / object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
[0067] In yet another embodiment, the disclosed methods may be readily implemented in conjunction with software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms. Alternatively, the disclosed system may be implemented partially or fully in hardware using standard logic circuits or VLSI design. Whether software or hardware is used to implement the systems in accordance with this disclosure is dependent on the speed and / or efficiency requirements of the system, the particular function, and the particular software or hardware systems or microprocessor or microcomputer systems being utilized.
[0068] In yet another embodiment, the disclosed methods may be partially implemented in software that can be stored on a storage medium, executed on programmed general- purpose computer with the cooperation of a controller and memory, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this disclosure can be implemented as program embedded on personal computer such as an applet, JAVA® or CGI script, as a resource residing on a server or computer workstation, as a routine embedded in a dedicated measurement system, system component, or the like. The system can also be implemented by physically incorporating the system and / or method into a software and / or hardware system.
[0069] Although the present disclosure describes components and functions implemented in the embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Other similar standards and protocols not mentioned herein are in existence and are considered to be included in the present disclosure. Moreover, the standards and protocols mentioned herein, and other similar standards and protocols not mentioned herein are periodically superseded by faster or more effective equivalents having essentially the same functions. Such replacement standards and protocols having the same functions are considered equivalents included in the present disclosure.
[0070] The present disclosure, in various embodiments, configurations, and aspects, includes components, methods, processes, systems and / or apparatus substantially as depicted and described herein, including various embodiments, sub combinations, and subsets thereof. Those of skill in the art will understand how to make and use the systems and methods disclosed herein after understanding the present disclosure. The present disclosure, in various embodiments, configurations, and aspects, includes providing devices and processes in the absence of items not depicted and / or described herein or in various embodiments, configurations, or aspects hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and\or reducing cost of implementation.
[0071] The foregoing discussion of the disclosure has been presented for purposes of illustration and description. The foregoing is not intended to limit the disclosure to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the disclosure are grouped together in one or more embodiments, configurations, or aspects for the purpose of streamlining the disclosure. The features of the embodiments, configurations, or aspects of the disclosure may be combined in alternate embodiments, configurations, or aspects other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention that the claimed disclosure requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment, configuration, or aspect. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the disclosure.
[0072] Moreover, though the description of the disclosure has included description of one or more embodiments, configurations, or aspects and certain variations and modifications, other variations, combinations, and modifications are within the scope of the disclosure, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments, configurations, or aspects to the extent permitted, including alternate, interchangeable and / or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and / or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.
Claims
CLAIMSWhat is claimed is:
1. An account server comprising: a microprocessor; and a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that, when executed by the microprocessor, cause the microprocessor to: receive, from a first communication device, a request to create a code, wherein the created code is for automatically creating a first user account on a second communication device; receive user information for automatically creating the first user account; create the code, wherein the created code comprises at least one of: the user information for creating the first user account; and a link to an account server, wherein the account server contains the user information; and send the created code to the first communication device.
2. The system of claim 1, wherein the created code comprises the user information for creating the first user account.
3. The system of claim 2, wherein the created code is a digital certificate and wherein the digital certificate is encrypted.
4. The system of claim 1, wherein the created code is one of a Quick Response (QR) code, a color QR code, and a barcode.
5. The system of claim 1, wherein the user information comprises one or more of a username, a suggested username, address information, biometric information, an email address, a security question, a credit card number, a phone number, a password, a social security number, an access privilege.
6. The system of claim 1, wherein the created code is sent to the second communication device for automatically creating the first user account on the second communication device.
7. The system of claim 6, wherein the created code is sent to a third communicationdevice for automatically creating a second user account on the third communication device.
8. The system of claim 1, wherein the first user account is automatically created on the second communication device, wherein the user information comprises a temporary password and a user email address, and wherein an email is sent to the first communication device so the user can login to second communication device.
9. The system of claim 1, wherein the created code comprises the link to the account server and wherein the microprocessor readable and executable instructions further cause the microprocessor to: receive, from the second communication device, the created code; determine that created code received from the second communication device is valid; and in response to the created code received from the second communication device being valid, send a message to the second communication device that the created code is valid.
10. The system of claim 1, wherein the account server comprises a plurality of user profiles, wherein different codes are generated based on a selected user profile, and wherein different user information is used in the creation of the code based on the selected profile.
11. A method comprising: receiving, by a microprocessor, from a first communication device, a request to create a code, wherein the created code is for automatically creating a first user account on a second communication device; receiving, by the microprocessor, user information for automatically creating the first user account; creating, by the microprocessor, the code, wherein the created code comprises at least one of: the user information for creating the first user account; and a link to an account server, wherein the account server contains the user information; and sending, by the microprocessor, the created code to the first communication device.
12. The method of claim 11, wherein the created code comprises the user information for creating the first user account.
13. The method of claim 12, wherein the created code is a digital certificate and wherein the digital certificate is encrypted.
14. The method of claim 11, wherein the created code is sent to the second communication device for automatically creating the first user account on the second communication device.
15. The method of claim 14, wherein the created code is sent to a third communication device for automatically creating a second user account on the third communication device.
16. The method of claim 11, wherein the first user account is automatically created on the second communication device, wherein the user information comprises a temporary password and a user email address, and wherein an email is sent to the first communication device so the user can login to second communication device.
17. The method of claim 11, wherein the created code comprises the link to the account server and wherein the microprocessor readable and executable instructions further cause the microprocessor to: receive, from the second communication device, the created code; determine that created code received from the second communication device is valid; and in response to the created code received from the second communication device being valid, send a message to the second communication device that the created code is valid.
18. The method of claim 11, wherein the account server comprises a plurality of user profiles, wherein different codes are generated based on a selected user profile, and wherein different user information is used in the creation of the code based on the selected profile.
19. A communication device comprising: a microprocessor; and a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that, when executed by themicroprocessor, cause the microprocessor to: send, to an account server, a request to create a code, wherein the created code is for automatically creating a first user account on a second communication device; send, to the account server, user information for automatically creating the first user account; receive, from the account server, the created code, wherein the created code comprises at least one of: the user information for creating the first user account; and a link to the account server, wherein the account server contains the user information; and send the created code to the second communication device.
20. A system comprising: a microprocessor; and a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that, when executed by the microprocessor, cause the microprocessor to: receive a code from a first communication device, wherein the received code comprises one or more fields for automatically filling in a graphical user interface; in response to receiving the code from the first communication device: identify the one or more fields in the code; identify a corresponding one or more fields in a graphical user interface; and automatically fill the corresponding one or more fields in the graphical user interface with the one or more fields in the code.
Citation Information
Patent Citations
Method for generating, issuing and managing user integrated account based on blockchain
KR102047260B1
Certified identification system and method
US20150304111A1
Notification system
US20180144307A1
Methods and systems for network-enabled account creation using optical detection
US20200092272A1
Generation and validation of user credentials
US9742781B1
