User attribute validation based on location request

Abstract

An aspect of the present application corresponds to processing a request for user attribute information. One or more computing devices may transmit a request for user attribute information including at least one captured piece of information associated with an identified user. A user attribute information request processing service processes the request based on a location profile according to verified attribute information associated with the captured information. The user attribute information request processing service then generates a processing result in response to the request, such as identifying loan rate information based on the verified attribute information.

Description

[Technical Field]

[0001] Generally, computing devices and communication networks may be utilized to exchange data and / or information. In a typical application, a computing device may request content from another computing device over a communication network. For example, a computing device may utilize software applications to collect various data and exchange content with a server computing device over a network (e.g., the Internet). Such software applications may include general communication applications for accessing a network, such as a browser application. Such general communication applications may access functionality provided by a network-based service. Software applications may also include custom or dedicated software applications configured to implement specific functionality, alone or in combination with a network-based service.

[0002] There are several scenarios in which user attributes, such as location-based information, can influence one or more user interactions. For example, in one embodiment, a location may wish to set different loan rates based on residence information for a particular user. In another example, access to a particular location or service within a location may be further based on user attributes, such as proximity to the particular location. Summary of the Invention [Means for solving the problem]

[0003] The present disclosure is described herein with reference to drawings of several embodiments that are intended to illustrate the disclosure, not to limit it. It should be understood that the accompanying drawings, which are incorporated into and constitute a part of this specification, are for the purpose of illustrating the concepts disclosed herein and may not be to scale. [Brief explanation of the drawings]

[0004] [Figure 1] FIG. 1 is a block diagram of an example environment for providing and validating user attributes, in accordance with one or more aspects of the present application. [Figure 2A] FIG. 1 illustrates an exemplary architecture for implementing a location processing service, according to aspects of the present application. [Figure 2B] FIG. 1 illustrates an exemplary architecture for implementing a client computing device according to aspects of the present application. [Figure 3A] 2 is a block diagram of the example environment of FIG. 1 illustrating initiation and processing of a user attribute information request according to an example embodiment. [Figure 3B] 2 is a block diagram of the example environment of FIG. 1 illustrating initiation and processing of a user attribute information request according to an example embodiment. [Figure 3C] 2 is a block diagram of the example environment of FIG. 1 illustrating initiation and processing of a user attribute information request according to an example embodiment. [Figure 4] 10 is a flow diagram illustrating a location request monitoring routine implemented by a location processing service according to an exemplary embodiment. [Figure 5] 4 is a flow diagram illustrating a location request monitoring routine implemented by a client device, according to an example embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0005] Generally, aspects of the present application correspond to processing a request for user attribute information. One or more computing devices may transmit a request for user attribute information that includes at least one captured piece of information associated with an identified user. A user attribute information request processing service processes the request based on a location profile according to verified attribute information associated with the captured information. The user attribute information request processing service then generates a processing result in response to the request, such as identifying loan rate information based on the verified attribute information.

[0006] According to an exemplary embodiment, locations within a geographic region may define certain attributes, such as loan rates, based on user attribute information. For example, parking fees within a location, such as a parking lot, may vary based on user location attributes, such as current residence information. According to this example, parking fees may vary depending on whether a user requesting to pay the parking fee can be characterized as a visitor or as residing within a defined geographic region (e.g., a state, country, city, neighborhood, street, house, etc.). In another example, locations within a geographic region may require certain types of user attribute information to gain access to a location (or service) or to achieve an available loan rate. In this example, a location corresponding to a boat marina may require a combination of user attributes (e.g., residence) and vehicle attributes (e.g., valid registration, insurance premium, etc.).

[0007] One approach for providing user attribute verification corresponds to the pre-configuration or pre-validation of a user's attribute information, such as through a submission and approval process. Such approaches generally require time and significant advance notice to complete the pre-configuration / pre-approval process. In addition, such approaches are generally limited to scenarios that are static in nature, where the locations to be pre-configured / pre-approved are known in advance and the pre-configuration / pre-approval criteria are also known in advance. For example, approaches that may enable a fixed computing device to obtain limited customer information are generally inefficient for allowing customers to utilize the submission process for different locations corresponding to different geographic regions. Such approaches are generally inefficient for adequately handling dynamically changing criteria, such as changing lending criteria, dynamically changing geographic criteria, or changes in the underlying information used to validate user location attribute information. Thus, pre-approval / pre-configuration processes may further lack the ability to dynamically collect the required information or simultaneously associate the collection of user attribute information with the intended access or use of the location (e.g., associate the submission / verification of the user attribute information).

[0008] To at least partially address the above-mentioned inefficiencies, aspects of the present application address processing a request for user attribute information. More specifically, one or more aspects of the present application address processing a request for user location attribute information. One or more computing devices may obtain an instantiation of a request for user attribute information, such as a request for loan criteria (or validation of loan criteria), based on the user location attribute information. The request for user attribute information may include at least one captured information associated with an identified user, such as an image showing a portion of a user identification card, mailing information, etc. By way of example, the image may show information including location information, such as a mailing address, a city of residence, a state of residence, a country of residence, etc. The captured information may include additional or alternative forms of captured information, including, but not limited to, barcode information, location information (e.g., Global Positioning System (GPS) information), electronically transmitted information / identifiers, etc.

[0009] The user attribute information request processing service receives the request and identifies a location profile based on the received request. The user attribute information request processing service also verifies attribute information associated with the captured information and parses image data or other data to obtain location information / attributes. The user attribute information request processing service may also validate the parsed information, such as by matching biometric data or image data. The user attribute information request processing service then generates a processing result in response to the request, such as identifying loan rate information, based on the verified attribute information. The processing result may be utilized to complete one or more transactions. Additionally, the processing result (e.g., loan rate information) may be associated with maturity criteria.

[0010] While various aspects are described with exemplary embodiments and combinations of features, those skilled in the art will appreciate that the example and combinations of features are exemplary in nature and should not be construed as limiting. More specifically, aspects of the present application may be applicable to various types of client devices, location attributes, captured user attribute information, etc. Accordingly, the illustrative examples should not be construed as limiting.

[0011] FIG. 1 illustrates a block diagram of an exemplary environment 100 for collecting, processing, and using user attribute information in accordance with one or more aspects of the present application. Environment 100 is a logical representation of one or more physical objects, articles, devices, components, etc. Environment 100 may be a set of physical locations, generally represented as locations 102. By way of example, locations may be physical assets such as parking lots, buildings, marinas, parks, streets, walkways, etc. In one embodiment, locations 102 are not associated with any form of computing device. In other embodiments, as illustrated in FIG. 1, locations 102 may have one or more computing devices that may have some form of communication with a communications network. As described in more detail below, locations 102 may be associated with some form of information distribution mechanism, both physical and electronic, to provide computing devices with network address information for accessing network services. For example, locations may include barcode information, near-field communication (NFC) information, etc., that provide access to a communications network address or other contact information.

[0012] The environment 100 may include one or more client devices 104 and a network service 110. By way of example, the computing device 104, as shown in FIG. 1, may be any computing device, such as a desktop, laptop, personal computer, tablet computer, wearable computer, server, personal digital assistant (PDA), hybrid PDA / mobile phone, mobile phone, smartphone, set-top box, voice command device, digital media player, etc. The computing device 104 may execute applications (e.g., browsers, standalone applications, etc.) that allow a user to access interactive user interfaces, view images, analytics, aggregated data, etc., as described herein. The computing device 104 may represent a standalone or stand-alone computing device. The computing device 104 may also represent computing processing functionality integrated within other devices or components, such as computing device functionality accessible in a vehicle. Exemplary components of the computing device 104 are described in FIG. 2B.

[0013] As an example, various aspects related to network service 110 may be implemented as one or more components associated with one or more functions or services. These components may correspond to software modules implemented or executed by one or more external computing devices, which may be separate, standalone external computing devices. Thus, the components of network service 110 should be considered as logical representations of services that do not require any specific implementation on one or more external computing devices.

[0014] By way of example, network service 110 may include multiple network-based services that can provide functionality upon request based on location profiles according to verified attribute information associated with the captured information. As shown in FIG. 1 , network-based service 110 may include user attribute information request processing service 112 that processes requests from client devices 104. The network-based service may include multiple data stores for maintaining various information related to aspects of the present application, including profile data store 114 and user information data store 116. The data stores of FIG. 1 are logical in nature and may be implemented in various ways within network service 110. Exemplary components of user attribute information request processing service 112 are described with respect to FIG. 2A .

[0015] 1 connects devices and system modules. The network 106 may connect any number of devices. The network 106 may include any combination of wired and / or wireless networks, such as, for example, one or more direct communication channels, a local area network, a wide area network, a personal area network, and / or the Internet. In some embodiments, communication between the client device 104 and computing devices associated with the location 102 may be implemented via short-range communication protocols, such as Bluetooth, Bluetooth Low Energy (“BLE”), and / or near field communication (“NFC”). Communication between the client device 104 and the service provider 110 may occur over one or more secure networks, such as a local area network that communicates securely over the Internet.

[0016] Environment 100 may further include one or more third-party services 120, which may include any one of several services / entities that may be configured to either provide input to network service 110 or receive processing results based on the process user attribute processing request. As an illustrative example, third-party service 120 may provide one or more data / information that may be utilized to identify an individual, such as a licensing authority, an identity provider, etc. One or more third-party services 120 may include service providers that can provide additional information that may be utilized in processing the user attribute request, such as an insurance company, a rental car agency, a bank / finance company, a landlord / location management company, etc. Third-party services 120 further include entities that may utilize the processing results, such as a security company, a financing company, a rental car agency, a landlord / location management company, etc.

[0017] 2A, an exemplary architecture for implementing the user attribute information request processing service 112 on one or more local resources or network services will be described. The user attribute information request processing service 112 may be a component / part of a system that provides functionality related to machine learning algorithms for object recognition, navigation, location services, etc.

[0018] The architecture of Figure 2A is exemplary in nature and should not be construed as requiring any particular hardware or software configuration for the user attribute information request processing service 112. The general architecture of the user attribute information request processing service 112 shown in Figure 2A includes an arrangement of computer hardware and software components that can be used to implement aspects of the present disclosure. As shown, the user attribute information request processing service 112 includes a processing unit 202, a network interface 204, a computer-readable medium drive 206, and an input / output device interface 208, all of which can communicate with each other via a communication bus. The components of the user attribute information request processing service 112 may be physical hardware components or may be implemented within a virtual environment.

[0019] The network interface 204 may provide connectivity to one or more networks or computing systems, such as the network of FIG. 1. The processing unit 202 can therefore receive information and instructions from other computing systems or services via the network. The processing unit 202 can communicate with memory 210 and can further provide output information for an optional display (not shown) via the input / output device interface 208. In some embodiments, the user attribute information request processing service 112 may include more (or fewer) components than those shown in FIG. 2A.

[0020] The memory 210 may include computer program instructions that the processing unit 202 executes to implement one or more embodiments. The memory 210 generally includes RAM, ROM, or other persistent or non-transitory memory. The memory 210 may store interface software 212 and an operating system 214 that provides computer program instructions for use by the processing unit 202 in the general management and operation of the user attribute information request processing service 112. The memory 210 may further include computer program instructions and other information for implementing aspects of the present disclosure. For example, in one embodiment, the memory 210 includes a user attribute verification component 216 for receiving and processing user attribute information as described herein. By way of example, the user attribute verification component 216 may include executable code or components that facilitate identification of submitted user attribute information (e.g., within captured information submitted by the client device 104) and validation or verification of the information. The memory 210 may further include a location attribute processing component 218 for processing the processed user attribute information according to the location profile information as described herein. As an example, the location attribute processing component 218 can generate processing results related to loan rates, access authorizations, notifications, and the like.

[0021] 2B, an exemplary architecture for implementing the user attribute information request processing service 112 on one or more local resources or network services will be described. The client device 104 may be part of a component / system that provides functionality related to machine learning algorithms for object recognition, navigation, location services, etc.

[0022] The architecture of FIG. 2B is exemplary in nature and should not be construed as requiring any particular hardware or software components for an exemplary client device 104. The architecture of FIG. 2B should be considered exemplary in nature and should not be construed as limiting with respect to the computing device corresponding to the client device 104. The general architecture of the client device 104 shown in FIG. 2B includes an arrangement of computer hardware and software components that may be used to implement aspects of the present disclosure. As shown, the client device 104 includes a processing unit 252, a network interface 254, a computer-readable medium drive 256, and an input / output device interface 258, all of which can communicate with each other via a communication bus. The components of the client device 104 may be physical hardware components or may be implemented within a virtual environment.

[0023] Network interface 254 may provide connectivity to one or more networks or computing systems, such as the network of FIG. 1. Processing unit 252 can therefore receive information and instructions from other computing systems or services over the network. Processing unit 252 can communicate with memory 260 and may further provide output information for an optional display (not shown) via input / output device interface 258. In some embodiments, client device 104 may include more (or fewer) components than those shown in FIG. 2B.

[0024] Memory 260 may include computer program instructions that processing unit 252 executes to implement one or more embodiments. Memory 260 generally includes RAM, ROM, or other persistent or non-transitory memory. Memory 260 may store interface software 262 and an operating system 264 that provides computer program instructions for use by processing unit 252 in the general management and operation of client device 104. Memory 260 may further include computer program instructions and other information for implementing aspects of the present disclosure. By way of example, the computing program or computer program instructions may be embodied as executable code executed by a general-purpose application, such as a browser application or other executable environment. In this aspect, client device 104 is not required to download or maintain a dedicated application. In other embodiments, the computing program in memory 260 may be embodied as a standalone application or persistent / semi-persistent code.

[0025] In one embodiment, memory 260 includes a sensor interface component 266 for receiving or capturing user attribute information that may be included as part of a user attribute information processing request. Sensor interface 266 can acquire image data for capturing image data indicative of identification information (e.g., an identification card, mail, etc.). In another example, sensor interface 266 can acquire information embedded in a barcode or transmitted via NFC. In yet another example, sensor interface 266 can acquire information transmitted via wireless-based communication with another computing device.

[0026] Additionally, memory 260 may include a user attribute processing component 268 for locally receiving and processing user attribute information as described herein. Similar to the functionality described above with respect to user attribute verification component 216, user attribute verification component 266 may include executable code or components that facilitate identification of submitted user attribute information (e.g., within captured information submitted by client device 104) and validation or verification of that information. This component may be omitted in some embodiments. Memory 260 may further include a location interface component 270 for processing processing results generated by user attribute information request processing service 112, such as completing a transaction using loan rate information, processing and displaying notifications, sending additional information, etc.

[0027] 3A-3C, exemplary interactions of components of an environment for generating and processing a user attribute information processing request will be described. For illustrative purposes, FIGS. 3A-3B depict interactions between a single client device 104, a single location 102, and a network service 110. Thus, in some aspects, interactions between multiple client devices 104, multiple locations 102, and a network service 110 may occur in parallel or serially. At (1), a client device 104 initiates a location request process. By way of example, the client device 104 may initiate the location request process by accessing a web page (via a browser application) or by selecting a software application. The client device 104 may receive information from a location 102, such as network address information, a location identifier, etc. Such information may be provided manually (e.g., via signage) or via electronic transmission (e.g., barcode, visual information, NFC, etc.).

[0028] In (2), the client device 104 may be configured to collect and capture user attribute information to be included as part of the request process. By way of example, the captured information is associated with the identified user, such as an image showing a portion of a user identification card, mailing information, etc. By way of example, the image may show information including location information such as a mailing address, city of residence, state of residence, country of residence, etc. The captured information may include additional or alternative forms of captured information, including, but not limited to, barcode information, location information (e.g., Global Positioning System (GPS) information), electronically transmitted information / identifiers, etc. The captured information may include biometric information, such as facial scan data, fingerprint data, eye scan data (e.g., iris pattern), voice pattern scan, etc.

[0029] In (3), the client device 104 may process the collected and captured data (e.g., sensor data). For example, the client device 104 may implement processes for randomizing the collected data, encrypting the data, correcting errors, normalizing the data, etc. The client device 104 may also obtain supplemental information, such as from a third-party service 120. Furthermore, the client device 104 may also perform some form of authentication or authorization process, such as independent security assessment, face mapping, etc.

[0030] At (4), the client device 104 transmits a user attribute processing request with the captured information. By way of example, the request may be facilitated through a browser application or a standalone component. The request may include the captured information, as described above. The request may include additional information utilized in processing the request, such as a user profile identifier, a location identifier, location information (e.g., GPS information), an account identifier, etc. The transmission of the request may correspond to one or more application programming interfaces ("APIs").

[0031] 3B, exemplary processing of a user attribute processing request will be described. At (1), user attribute information request processing service 112 may receive one or more third-party data from third-party service 120. As previously described, in one aspect, third-party service 120 may include any one of several services / entities that may be configured to provide input to network service 110. As an illustrative example, third-party service 120 may provide one or more data / information that may be utilized to identify an individual, such as a licensing authority, an identity provider, etc. One or more third-party services 120 may include service providers that can provide additional information that may be utilized in processing a user attribute request, such as an insurance company, a rental car agency, a bank / finance company, a landlord / location management company, etc. In some embodiments, network service 110 may not interact with the third-party data, or in other cases, the third-party data may not be provided.

[0032] In (2), the user attribute information request processing service 112 may process the received request. In one aspect, the user attribute information request processing service 112 may parse the received attribute request to determine the captured user attribute information. For example, the user attribute information request processing service 112 may determine / distinguish between different types of captured information, etc. The user attribute information request processing service 112 may further decipher or validate the accuracy / validity of the captured information. The user attribute information request processing service 112 may also provide error correction, duplicate removal, normalization, etc.

[0033] In (3), the user attribute information request processing service 112 processes the captured information. As an example, in the case of captured image data, the user attribute information request processing service 112 may perform image analysis or other analytical processes to identify information indicated in the image data. For example, the user attribute information request processing service 112 may attempt to extract address information (complete or partial) as verification of user location attributes. In another example, the user attribute information request processing service 112 may attempt to ascertain the user's physical attribute information from the image data and match it to the user's physical appearance (e.g., using third-party image data). In another aspect, the user attribute information request processing service 112 may implement additional processing to process biometric information included in the captured information submitted in the user attribute request. The user attribute information request processing service 112 may also utilize a third-party service 120 to complete the process. In addition, the user attribute information request processing service 112 may maintain some form of caching or other verification information (e.g., hash values) to enable reuse of previously performed processing.

[0034] At (4), the user attribute information request processing service 112 identifies one or more location profiles. By way of example, a location profile corresponds to one or more processing rules or structural logic used to evaluate the verified user attribute information. For example, a location profile can provide financing rate information (e.g., parking fees) based on determined residence information. A location profile can also select from different potential rates based on multiple factors / criteria, such as time of day, frequency of use, user classification (e.g., preferred customer), etc. In other embodiments, a location profile can be used to authorize actions, such as providing permission, notification, or physically providing access to goods / services. A location profile can be unique to an individual location, sorted by location identifier, or corresponding to a submitted graphic identifier / coordinate. In other embodiments, a location profile can be applied to a set of locations based on organizational criteria (e.g., a company-specific location profile versus one or more profiles), etc. Furthermore, a location profile can include a default profile or a single profile that belongs to all locations.

[0035] In (5), the user attribute information request processing service 112 may generate a processing result. In one embodiment, the processing result may include generation / identification of determined loan rate information to be utilized in subsequent transactions related to the corresponding location. For example, the user attribute information request processing service 112 may return parking fee information to be utilized to charge parking fees. In another embodiment, the processing result may include a notification, an access code, a communication, etc. Still further, in some embodiments, the processing result may include additional executable code or instructions that may be executed by the client device 104, such as to complete a transaction or to perform additional actions.

[0036] 3C , after generating the processing result in (1), the user attribute information request processing service 112 may transmit the processing result to multiple potential recipients, such as the location 102, the client device 104, and the third-party service 120. By way of example, the user attribute information request processing service 112 need not transmit to all three recipients, but may be configured in various embodiments to transmit to any subset of the recipients. As previously described, the processing result may include the generation / identification of determined loan rate information to be utilized in a subsequent transaction related to the corresponding location. For example, the user attribute information request processing service 112 may return parking fee information to be utilized to charge parking fees. In another embodiment, the processing result may include a notification, an access code, a communication, or the like. By way of example, in some embodiments, the processing result may include additional executable code or instructions that can be executed by the client device 104, such as to complete a transaction or to perform additional actions. Thus, in (2), the client device processes / executes the processing result.

[0037] Referring now to FIG. 4 , a routine 400 for processing a location request will be described. The routine 400 is illustratively implemented by the user attribute information request processing service 112. At block 402, the user attribute information request processing service 112 obtains a request from the client device 104, the request including the captured information and other additional information. As previously described, the request may be facilitated through a browser application or a standalone component. The request may include the captured information, as described above. The request may include additional information utilized in processing the request, such as a user profile identifier, a location identifier, location information (e.g., GPS information), an account identifier, etc. The transmission of the request may correspond to one or more APIs.

[0038] Additionally, user attribute information request processing service 112 may receive one or more third-party data from third-party services 120. As previously described, in one aspect, third-party services may include any one of several services / entities that may be configured to provide input to network service 110. As an illustrative example, third-party service 120 may provide one or more data / information that may be utilized to identify an individual, such as a licensing authority, an identity provider, etc. One or more third-party services 120 may include service providers that can provide additional information that may be utilized in processing a user attribute request, such as an insurance company, a rental car agency, a bank / finance company, a landlord / location management company, etc. In some embodiments, network service 110 may not interact with the third-party data, or in other cases, the third-party data may not be provided.

[0039] In block 404, the user attribute information request processing service 112 may process the received attribute request. In one aspect, the user attribute information request processing service 112 may parse the received attribute request to determine the captured user attribute information. For example, the user attribute information request processing service 112 may determine / distinguish between different types of captured information, etc. The user attribute information request processing service 112 may further decipher or validate the accuracy / validity of the captured information. The user attribute information request processing service 112 may also provide error correction, duplicate removal, normalization, etc.

[0040] In block 406, the user attribute information request processing service 112 identifies one or more location profiles. By way of example, a location profile corresponds to one or more processing rules or structural logic used to evaluate the verified user attribute information. For example, a location profile can provide financing rate information (e.g., parking fees) based on determined residence information. A location profile can also select from different potential rates based on multiple factors / criteria, such as time of day, frequency of use, user classification (e.g., preferred customer), etc. In other embodiments, a location profile can be used to authorize actions, such as providing permission, notification, or physically providing access to goods / services. A location profile can be unique to an individual location, sorted by location identifier, or corresponding to a submitted graphic identifier / coordinate. In other embodiments, a location profile can be applied to a set of locations based on organizational criteria (e.g., a company-specific location profile versus one or more profiles), etc. Furthermore, a location profile can include a default profile or a single profile that belongs to all locations.

[0041] In block 408, the user attribute information request processing service 112 processes the captured information. As an example, in the case of captured image data, the user attribute information request processing service 112 may perform image analysis or other analytical processes to identify information indicated in the image data. For example, the user attribute information request processing service 112 may attempt to extract address information (complete or partial) as verification of user location attributes. In another example, the user attribute information request processing service 112 may attempt to locate the user's physical attribute information from the image data and match it to the user's physical appearance (e.g., using third-party image data). In another aspect, the user attribute information request processing service 112 may implement additional processing to process biometric information included in the captured information submitted in the user attribute request. The user attribute information request processing service 112 may also utilize a third-party service 120 to complete the process. In addition, the user attribute information request processing service 112 may maintain some form of caching or other verification information (e.g., hash values) to enable reuse of previously performed processing.

[0042] At block 410, the user attribute information request processing service 112 may generate a processing result. In one embodiment, the processing result may include generation / identification of determined loan rate information to be utilized in subsequent transactions related to the corresponding location. For example, the user attribute information request processing service 112 may return parking fee information to be utilized to charge parking fees. In another embodiment, the processing result may include a notification, an access code, a communication, etc. Still further, in some embodiments, the processing result may include additional executable code or instructions that may be executed by the client device 104, such as to complete a transaction or to perform additional actions.

[0043] Referring to FIG. 5, a routine 500 for processing a location request will be described. The routine 500 is, by way of example, implemented by the client device 104. At block 502, the client device 104 initiates a location request process. By way of example, the client device 104 may initiate the location request process by accessing a web page (via a browser application) or by selecting a software application. The client device 104 may receive information from the location 102, such as, by way of example, network address information, a location identifier, etc. Such information may be provided manually (e.g., signage) or via electronic transmission (e.g., barcode, visual information, NFC, etc.).

[0044] At block 504, the client device 104 may be configured to collect and capture user attribute information to be included as part of the request process. By way of example, the captured information is associated with the identified user, such as an image showing a portion of a user identification card, mailing information, etc. By way of example, the image may show information including location information such as a mailing address, city of residence, state of residence, country of residence, etc. The captured information may include additional or alternative forms of captured information, including, but not limited to, barcode information, location information (e.g., Global Positioning System (GPS) information), electronically transmitted information / identifiers, etc. The captured information may include biometric information, such as facial scan data, fingerprint data, eye scan data (e.g., iris pattern), voice pattern scan, etc.

[0045] At block 506, the client device 104 may process the collected and captured data (e.g., sensor data). For example, the client device 104 may implement processes for randomizing the collected data, encrypting the data, error correcting, data normalization, etc. The client device 104 may also obtain supplemental information, such as from a third-party service 120. Furthermore, the client device 104 may also perform some form of authentication or authorization process, such as independent security assessment, face mapping, etc.

[0046] At block 508, the client device 104 transmits a user attribute processing request with the captured information. By way of example, the request may be facilitated through a browser application or a standalone component. The request may include the captured information, as described above. The request may include additional information utilized in processing the request, such as a user profile identifier, a location identifier, location information (e.g., GPS information), an account identifier, etc. The transmission of the request may correspond to one or more APIs.

[0047] At block 510, the client device 104 may receive the processing result sent by the user attribute information request processing service 112. As previously described, the processing result may include generation / identification of determined loan rate information to be utilized in subsequent transactions related to the corresponding location. For example, the user attribute information request processing service 112 may return parking fee information to be utilized to charge parking fees. In another embodiment, the processing result may include a notification, an access code, a communication, or the like. Accordingly, at block 512, the client device processes / executes the processing result. For example, in some embodiments, the processing result may include additional executable code or instructions that may be executed by the client device 104, such as to complete a transaction or to perform additional actions, such as generating a barcode or an access code via a user interface or wireless signal. At block 514, the routine 500 ends.

[0048] The foregoing disclosure is not intended to limit the present disclosure to the precise forms or particular fields of use disclosed. Accordingly, various alternative embodiments and / or modifications to the present disclosure, whether expressly described or implied herein, are contemplated as possible in light of the present disclosure. While embodiments of the present disclosure have been so described, those skilled in the art will recognize that changes can be made in form and detail without departing from the scope of the present disclosure. Accordingly, the present disclosure is limited only by the claims.

[0049] In the foregoing specification, the present disclosure has been described with reference to specific embodiments. However, as those skilled in the art will appreciate, the various embodiments disclosed herein may be modified or otherwise implemented in various other ways without departing from the spirit and scope of the present disclosure. Accordingly, this description is to be considered illustrative and is intended to teach those skilled in the art how to make and use various embodiments of the disclosed decision and control algorithms. It should be understood that the forms of the disclosure shown and described herein are representative embodiments. Equivalent elements, materials, processes, or steps may be substituted for those shown and described herein as representative. Moreover, some features of the present disclosure may be utilized independently of the use of other features, all of which will be apparent to those skilled in the art with the benefit of this description of the present disclosure. The terms "including," "comprising," "incorporating," "consisting of," "have," "is," and the like, used to describe and claim the present disclosure, are intended to be construed in a non-exclusive manner, i.e., allowing for the presence of items, components, or elements not expressly described. References in the singular should be construed to also relate to the plural.

[0050] Furthermore, the various embodiments disclosed herein should be understood to be exemplary and explanatory and should not be construed as limiting the present disclosure in any way. All joinder references (e.g., attached, attached, coupled, connected, etc.) are used merely to aid the reader in understanding the present disclosure and may not pose any limitations with respect to the location, orientation, or use of the systems and / or methods disclosed herein in particular. Accordingly, joinder references, if any, should be interpreted broadly. Moreover, the reference of such joinder references does not necessarily infer that those two elements are directly connected to each other.

[0051] Additionally, all numerical terms, such as, but not limited to, "first," "second," "third," "primary," "secondary," "main," or any other generic and / or numerical term, should also be understood as merely identifiers to aid the reader in understanding the various elements, embodiments, variations and / or modifications of the present disclosure, and in particular may not impose any limitations regarding the order or preference of any element, embodiment, variation and / or modification relative to or over another element, embodiment, variation and / or modification.

[0052] It will also be appreciated that one or more of the elements shown in the drawing / figure may be implemented in a more separate or integrated manner, or in some cases may even be removed or rendered inoperative, as may be useful according to a particular application.

[0053] The foregoing can be better understood in light of the following set of clauses: Clause 1. A system for requesting user attribute information, comprising: a plurality of computing devices, each configured to generate a request for user attribute information associated with one or more locations; one or more computing systems including a processing device and memory for executing computer-executable instructions for implementing a user attribute information request processing service; The user attribute information request processing service includes: obtaining, from one or more computing devices, a request for user attribute information, the request for user location attribute information corresponding to an identified location within a geographic area, the request for user location attribute information including at least one captured information associated with the identified user; identifying one or more profiles associated with the identified location, the one or more profiles defining processing rules for determining loan rate information based on a request for user attribute information; processing a request for user attribute information based on the identified one or more profiles, the processing including verifying user attributes based on at least one captured information associated with the identified user, and processing the verified user attributes according to the one or more profiles; generating a processing result associated with the processed request for user attribute information, the processing result including an identification of at least one loan rate information to be applied to the request for user attribute information; transmitting a processing result generated in response to the obtained request for user attribute information; The system is operable to: Clause 2. The system of clause 1, wherein the captured information associated with the identified user includes an image showing an identification card. Clause 3. The system of clause 2, wherein the image showing the identification card includes at least a portion of address information, and wherein processing the request for user attribute information includes verifying user attributes based on at least one captured information associated with the identified user, including parsing the shown address information to verify location attributes attributed to the identified user. Clause 4. The system of clause 1, wherein the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information include one or more profiles including a plurality of loan rate information that depend at least in part on location attributes attributed to the identified user. Clause 5. The system of clause 4, wherein the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information include the one or more profiles including a plurality of loan rate information that further depend at least in part on timing information associated with the request for user attribute information. Clause 6. The system of clause 1, wherein the user attribute information request processing service is further operable to cause a financial transaction to be processed based on the user attribute information request processing service and an identification of at least one loan rate information to be applied to the request for user attribute information. Clause 7. The system of clause 1, wherein the user attribute information request processing service is further operable to obtain at least one additional piece of information from a third party service in response to the request for the user attribute information. Clause 8. A method for managing requests for user attribute information, comprising: obtaining, from one or more computing devices, a request for user attribute information, the request for user attribute information corresponding to an identified location within a geographic area, the request for user attribute information including at least one captured information associated with the identified user; processing a request for user attribute information based on identified one or more profiles applicable to the identified location, the step including verifying user attributes based on at least one captured information associated with the identified user, and processing the verified user attributes according to the one or more profiles; generating a processing result associated with the processed request for user attribute information; transmitting a processing result generated in response to the obtained request for user attribute information; A method comprising: Clause 9. The method of clause 8, further comprising identifying one or more profiles associated with the identified location, the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information. Clause 10. The method of clause 8, wherein the captured information associated with the identified user includes at least one of an image indicative of an identification card or biometric data associated with the identified user. Clause 11. The method of clause 10, wherein the image showing the identification card includes at least a portion of address information, and wherein processing the request for user attribute information includes verifying user attributes based on at least one captured information associated with the identified user, including parsing the shown address information to verify location attributes attributed to the identified user. Clause 12. The method of clause 8, wherein the processing results include identification of at least one loan rate information to be applied to the request for user attribute information. Clause 13. The method of clause 12, including one or more profiles defining processing rules for determining loan rate information based on a request for user attribute information, the one or more profiles including a plurality of loan rate information that depends at least in part on location attributes attributed to an identified user. Clause 14. The method of clause 13, including one or more profiles defining processing rules for determining loan rate information based on requests for user attribute information, the one or more profiles including a plurality of loan rate information further dependent at least in part on timing information associated with the requests for user attribute information. Clause 15. The method of clause 12, further comprising processing the financial transaction based on the user attribute information request processing service and the identification of at least one loan rate information to be applied to the request for user attribute information. Clause 16. The method of clause 8, wherein the user attribute information request includes location information for validating the location attributed to the location request. Clause 17. The method of clause 8, wherein the user attribute information request processing service is further operable to obtain at least one additional piece of information from a third party service in response to the request for the user attribute information. Clause 18. A method for managing requests for user attribute information, comprising: sending a request for user attribute information to a user attribute information request processing service, the request for user attribute information corresponding to an identified location within a geographic area, the request for user attribute information including at least one captured information associated with the identified user; obtaining a processing result associated with the processed request for user attribute information, the processing result based on processing the request for user attribute information based on identified one or more profiles applicable to the identified location, wherein processing the request for user attribute information includes verifying user attributes based on at least one captured information associated with the identified user, and processing the verified user attributes according to the one or more profiles; completing at least one additional transaction based on the obtained processing result; A method comprising: Clause 19. The method of clause 18, wherein the captured information associated with the identified user includes at least one of an image indicative of an identification card or biometric data associated with the identified user. Clause 20. The method of clause 19, wherein the image showing the identification card includes at least a portion of address information, and wherein processing the request for user attribute information includes verifying user attributes based on at least one captured information associated with the identified user, including parsing the shown address information to verify location attributes attributed to the identified user. Clause 21. The method of clause 18, wherein the processing result is associated with at least one expiry criterion. Clause 22. The method of clause 21, further comprising completing at least one additional transaction based on the processing result and a determination that at least one expiration criterion has not been met.

[0054] It should be emphasized that many variations and modifications may be made to the above-described embodiments, and that elements thereof should be understood to fall within other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims. [Explanation of symbols]

[0055] 100 Environment 102 Location 104 Client Devices, Computing Devices 106 Network 110 Network services, network-based services, service providers 112 User attribute information request processing service 114 Profile Data Store 116 User Information Data Store 120 Third Party Services 202 Processing Unit 204 Network Interface 206 Computer-readable medium drive 208 Input / Output Device Interface 210 memory 212 Interface Software 214 Operating Systems 216 User Attribute Verification Component 218 Location Attribute Processing Component 252 processing units 254 network interfaces 256 Computer Readable Media Drive 258 Input / Output Device Interface 260 memory 262 Interface Software 264 Operating System 266 Sensor Interface Component, Sensor Interface, User Attribute Verification Component 268 User Attribute Processing Component 270 Location Interface Components 400 Routines 500 Routines

Claims

1. 1. A system for requesting user attribute information, comprising: a plurality of computing devices, each configured to generate a request for user attribute information associated with one or more locations; one or more computing systems including a processing device and memory for executing computer-executable instructions for implementing a user attribute information request processing service; wherein the user attribute information request processing service comprises: obtaining, from one or more computing devices, a request for user attribute information, the request for user location attribute information corresponding to an identified location within a geographic area, the request for user location attribute information including at least one captured information associated with the identified user; identifying one or more profiles associated with the identified location, the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information; processing the request for user attribute information based on the identified one or more profiles, the processing including verifying user attributes based on the at least one captured information associated with an identified user, and processing the verified user attributes in accordance with the one or more profiles; generating a processing result associated with the processed request for user attribute information, the processing result including an identification of at least one loan rate information to be applied to the request for user attribute information; transmitting the generated processing result in response to the obtained request for user attribute information; The system is operable to:

2. The system of claim 1 , wherein the captured information associated with the identified user includes an image showing an identification card.

3. 3. The system of claim 2, wherein the image showing the identification card includes at least a portion of address information, and processing the request for user attribute information includes verifying user attributes based on the at least one captured information associated with the identified user, including parsing the shown address information to verify location attributes attributed to the identified user.

4. The system of claim 1, wherein the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information include one or more profiles including a plurality of loan rate information that depend at least in part on location attributes attributed to the identified user.

5. 5. The system of claim 4, wherein the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information include one or more profiles including a plurality of loan rate information that further depends at least in part on timing information associated with the request for user attribute information.

6. 2. The system of claim 1, wherein the user attribute information request processing service is further operable to cause a financial transaction to be processed based on the user attribute information request processing service and the identification of at least one loan rate information to be applied to the request for user attribute information.

7. The system of claim 1 , wherein the user attribute information request processing service is further operable to obtain at least one additional piece of information from a third party service in response to the request for user attribute information.

8. 1. A method for managing requests for user attribute information, comprising: obtaining, from one or more computing devices, a request for user attribute information, wherein the request for user attribute information corresponds to an identified location within a geographic area, and the request for user attribute information includes at least one captured information associated with the identified user; processing the request for user attribute information based on identified one or more profiles applicable to the identified location, the step including verifying user attributes based on the at least one captured information associated with an identified user, and processing the verified user attributes in accordance with the one or more profiles; generating a processing result associated with the processed request for user attribute information; transmitting the generated processing result in response to the obtained request for user attribute information; A method comprising:

9. 9. The method of claim 8, further comprising identifying one or more profiles associated with the identified location, the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information.

10. 9. The method of claim 8, wherein the captured information associated with the identified user includes at least one of an image showing an identification card or biometric data associated with the identified user.

11. 11. The method of claim 10, wherein the image showing the identification card includes at least a portion of address information, and wherein processing the request for user attribute information includes verifying user attributes based on the at least one captured information related to the identified user, including parsing the shown address information to verify location attributes attributed to the identified user.

12. The method of claim 8 , wherein the processing results include an identification of at least one loan rate information to be applied to the request for user attribute information.

13. 13. The method of claim 12, wherein the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information include one or more profiles including a plurality of loan rate information that depend at least in part on location attributes attributed to the identified user.

14. 14. The method of claim 13, wherein the one or more profiles defining processing rules for determining loan rate information based on the request for user attribute information include one or more profiles including a plurality of loan rate information that further depends at least in part on timing information associated with the request for user attribute information.

15. 13. The method of claim 12, further comprising processing a financial transaction based on a user attribute information request processing service and the identification of at least one loan rate information to be applied to the request for user attribute information.

16. 10. The method of claim 8, wherein the user attribute information request includes location information for validating the location attributed to the location request.

17. 10. The method of claim 8, wherein the user attribute information request processing service is further operable to obtain at least one additional piece of information from a third party service in response to the request for user attribute information.

18. 1. A method for managing requests for user attribute information, comprising: sending a request for user attribute information to a user attribute information request processing service, the request for user attribute information corresponding to an identified location within a geographic area, the request for user attribute information including at least one captured piece of information associated with the identified user; obtaining a processing result associated with the processed request for user attribute information, the processing result being based on processing the request for user attribute information based on identified one or more profiles applicable to the identified location, wherein processing the request for user attribute information includes verifying user attributes based on the at least one captured information associated with an identified user, and processing the verified user attributes in accordance with the one or more profiles; completing at least one additional transaction based on the obtained processing result; A method comprising:

19. 20. The method of claim 18, wherein the captured information associated with the identified user includes at least one of an image showing an identification card or biometric data associated with the identified user.

20. 20. The method of claim 19, wherein the image showing the identification card includes at least a portion of address information, and wherein processing the request for user attribute information includes verifying user attributes based on the at least one captured information related to the identified user, including parsing the shown address information to verify location attributes attributed to the identified user.

21. The method of claim 18 , wherein the processing result is associated with at least one expiration criterion.

22. 22. The method of claim 21, further comprising completing at least one additional transaction based on the processing result and a determination that the at least one expiration criterion has not been met.

Images