# Patent

## Title
Systems, methods, and computer program products for processing a request relating to a mobile communication device

## Abstract

Systems, methods, and computer program products are provided for processing a request relating to a mobile device. A request, including a mobile device identifier and a partner system identifier corresponding to the partner system, is received from a partner system via a communication network. An authorization procedure is executed based on the mobile device identifier and the partner system identifier. The authorization procedure includes determining whether a partner system account list, associated with the mobile device identifier, includes the partner system identifier. Authorization of the request is granted if the partner system account list includes the partner system identifier; and is denied if the partner system account list does not include the partner system identifier. A response to the request is transmitted to the partner system via the communication network, based on a result of the authorization procedure.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
The present application claims priority to U.S. Provisional Application Nos. 61/835,974, filed on Jun. 17, 2013, and 61/845,094, filed on Jul. 11, 2013. The entire contents of these applications are hereby incorporated by reference herein.


BACKGROUND
1. Field
Example aspects described herein relate generally to mobile communication devices, and more particularly to systems, methods, and computer program products for processing requests relating to mobile communication devices.
2. Related Art
Mobile communication devices (also referred to herein as mobile devices) are becoming more and more versatile, and are being used in an increasing number of ways to make various everyday tasks simpler and/or more efficient. For example, mobile devices are being made to include mobile applications, such as mobile wallets, which may be used to conduct financial transactions (e.g., payments) and/or non-financial transactions (e.g., venue admissions), without the need for physical cash, checks, credit cards, tickets, and/or the like.
In order to enable consumer care systems and/or agents to provide consumer care to mobile device users, e.g., when issues arise relating to mobile devices and/or mobile applications stored thereon, it would be beneficial to provide the consumer care systems and/or agents with access to information relating to mobile devices or applications, and/or enable the agents to perform various operations relating to mobile devices or applications. However, because information relating to mobile devices or applications can be sensitive or confidential, access to such information and to operations relating to mobile devices or applications must be restricted for security and privacy reasons.
Given the foregoing, it would be beneficial to safeguard information relating to mobile communication devices and restrict access to operations relating to mobile communication devices, while also providing consumer care systems and/or agents with a level of access to such information and/or operations that is sufficient for consumer care purposes.
One technical challenge in doing so lies in the processing of mobile communication device information and/or operation requests that are received from different entities (e.g., a mobile wallet provider, external partners, such as payment product issuers (also referred to herein as “issuers”) and/or mobile network operators (MNOs), and/or the like) and/or personnel that may provide consumer care in connection with mobile communication devices. Moreover, different levels of access may be appropriate for specific levels of personnel (e.g., consumer care agents) within a particular entity.
SUMMARY
The example embodiments herein provide systems, methods, and computer program products for processing a request relating to a mobile communication device. The request, in some example embodiments herein, may relate to a mobile application, such as a mobile wallet, stored on the mobile communication device.
In accordance with one example aspect herein, a request, including a mobile device identifier and a partner system identifier corresponding to the partner system, is received from a partner system via a communication network. An authorization procedure is executed based on the mobile device identifier and the partner system identifier. The authorization procedure includes determining whether a partner system account list, associated with the mobile device identifier, includes the partner system identifier. Authorization of the request is granted if the partner system account list includes the partner system identifier; and is denied if the partner system account list does not include the partner system identifier. A response to the request is transmitted to the partner system via the communication network, based on a result of the authorization procedure.
In another example embodiment, the step of receiving the request includes receiving the request from the partner system by way of a portal and a gateway, and the method further comprises steps of: (1) authenticating the partner system at the gateway; and (2) appending the partner system identifier to the request at the gateway.
In one example herein, the request further includes an agent identifier, and the portal includes a graphical user interface (GUI) that enables the partner system to generate a predetermined set of requests based on a predetermined access level associated with the partner system and the agent identifier.
In accordance with some example aspects herein, the request is a request for consumer data relating to a mobile wallet associated with the mobile device identifier, the consumer data including any one or a combination of: (1) a consumer profile, (2) wallet information, (3) wallet event history, (4) service account information, (5) service account history, and (6) service account event status.
If the authorization of the request is granted, in one example, the method further comprises steps of: (1) retrieving the consumer data from a wallet server; and (2) including the consumer data in the response.
In another example herein, the request is a request for performance of an operation relating to a mobile wallet associated with the mobile device identifier, and the operation includes any one or a combination of: (1) updating a service account state, (2) updating a mobile wallet state, (3) resetting a password, and (4) resetting a security question and answer.
If the authorization of the request is granted, the method further comprises a step of performing the operation by transmitting one or more commands to the mobile wallet, in accordance with another example herein.



BRIEF DESCRIPTION OF THE DRAWINGS
The features and advantages of the example embodiments presented herein will become more apparent from the detailed description set forth below when taken in conjunction with the following drawings.
FIG. 1 is a diagram of an example system for processing a request relating to a mobile device, in accordance with various example embodiments herein.
FIG. 2 shows an example procedure for processing a request relating to a mobile device, in accordance with an example embodiment herein.
FIG. 3 shows an example procedure for authorizing a request relating to a mobile device, in accordance with an example embodiment herein.
FIG. 4 shows an example procedure for processing a request for consumer profile information relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 5 shows an example procedure for processing a request for mobile wallet information, in accordance with an example embodiment herein.
FIG. 6 shows an example procedure for processing a request for wallet event history relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 7 shows an example procedure for processing a request for status regarding executions of predetermined processing workflows relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 8 shows an example procedure for processing a request to update a mobile wallet state, in accordance with an example embodiment herein.
FIG. 9 shows an example procedure for processing a request to reset a password relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 10 shows an example procedure for processing a request to reset a security question and answer relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 11 shows an example procedure for authorizing a request relating to a mobile device, in accordance with an example embodiment herein.
FIG. 12 shows an example procedure for processing a request for consumer profile information relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 13 shows an example procedure for processing a request for mobile wallet information, in accordance with an example embodiment herein.
FIG. 14 shows an example procedure for processing a request for service account information relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 15 shows an example procedure for processing a request for wallet event history relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 16 shows an example procedure for processing a request for service account history relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 17 shows an example procedure for processing a request for service account event status relating to a mobile wallet, in accordance with an example embodiment herein.
FIG. 18 shows an example procedure for processing a request to update a service account state, in accordance with an example embodiment herein.
FIG. 19 is a block diagram of a general and/or special purpose computer that may be employed in accordance with various example embodiments herein.



DETAILED DESCRIPTION
I. Overview
The terms “payment product” and “card” may be used interchangeably herein to refer to a product, such as a credit card, a general purpose reloadable (GPR) card, and/or the like, that may be used to conduct financial transactions.
The term “service provider data” as used herein generally refers to data relating to one or more service providers, service provider systems, and/or services provided by one or more service providers. In some example embodiments herein, service provider data refers to any data associated with a service provider that is stored in a wallet database and/or in a wallet client database.
The term “wallet instance” as used herein generally refers to one instance of a wallet, mobile wallet, and/or mobile wallet application that is deployed and/or stored on a mobile device.
Presented herein are novel and inventive systems, methods, and computer program products for processing a request relating to a mobile communication device. The request, in some examples herein, may relate to a mobile application, such as a mobile wallet (which may also be referred to as a “mobile wallet client” or a “wallet client”), stored on the mobile communication device. In accordance with some aspects described herein, systems, methods, and computer program products are provided that enable the safeguarding of information relating to mobile communication devices and the restriction of access to operations relating to mobile communication devices, while also providing consumer care systems and/or agents with a level of access to such information and/or operations that is sufficient for consumer care purposes.
Some example aspects described herein facilitate the processing of mobile wallet information and/or operation requests that are received from systems managed by different entities (e.g., a mobile wallet provider, external partners, such as payment product issuers and/or mobile network operators (MNOs), and/or the like) and/or personnel managing those systems who may provide consumer care in connection with mobile wallets. Different levels of access may be provided for specific levels of personnel (e.g., consumer care agents) within a particular entity, in accordance with some example aspects herein.
II. System
FIG. 1 is a diagram of an example system 100 for processing a request relating to a mobile device, in accordance with various example aspects herein. The system 100 includes an enterprise service bus (ESB) 101, a wallet server 104 (which may also be referred to as a “mobile wallet server” or a “server”), a gateway 105, portals 106-1, 106-2, and 106-3 (individually and/or collectively referenced as “106”), a network 107, and one or more external partner system(s) 108.
The ESB 101 is communicatively coupled to the wallet server 104 by any suitable communication channel. In some example embodiments, the ESB 101 is communicatively coupled to the wallet server 104 by way of a direct connection, a proprietary network, a private network, a virtual private network (VPN), a network employing Hypertext Transfer Protocol (HTTP) standards, the Internet, and/or another type of network. The ESB 101, in another example, is communicatively coupled to the wallet server 104 via a secured communication channel.
The gateway 105 communicatively couples the ESB 101 to the one or more portal(s) 106 and to the external partner system(s) 108 by way of the network 107. The network 107 may be a mobile phone cellular network, a radio network, a proprietary network, a private network, a VPN, a network employing HTTP standards, the Internet, and/or another type of network.
The portals 106 are systems including interfaces, such as graphical user interfaces (GUIs), that enable a system and/or user (e.g., a consumer care agent of an entity (e.g., an MNO, an issuer, or another entity) associated with a mobile wallet account) to log into a partner care account and generate certain requests relating to mobile wallet accounts associated with the entity. In one example embodiment, the GUI of each portal 106 enables the corresponding partner system to generate a predetermined set of requests based on a predetermined access level associated with the particular partner system and an agent identifier that uniquely identifies the user logged into the GUI of the portal 106. The requests that can be generated by way of the portals 106 include (1) requests for information stored in the wallet server 104 and associated with mobile wallets, and/or (2) requests for execution of operations relating to such mobile wallets.
In one example embodiment herein, the wallet server 104 stores numerous types of information relating to each of a plurality of mobile wallet accounts provided by a mobile wallet provider. For instance, the wallet server 104 stores, for each mobile wallet account, (1) a consumer profile, (2) wallet information, (3) wallet event history, (4) service account information, (5) service account history, and (6) service account event status. Although not shown in FIG. 1 for purposes of convenience, in some example embodiments the wallet server 104 may include, or be communicatively coupled to, a wallet database that stores information on behalf of the wallet server 104.
The wallet server 104 also is configured to execute numerous types of operations relating to mobile wallet accounts. For instance, the wallet server 104 is configured to execute, for each mobile wallet account, (1) an update of a service account state, (2) an update of a mobile wallet state, (3) a reset of a password, and (4) a reset of a security question and answer.
As will be described in further detail below, in accordance with various example aspects herein, the ESB 101 acts as an intermediary between the portals 106 and the wallet server 104. In one example embodiment herein, the ESB 101 represents a central ESB managed by a mobile wallet provider. In particular, the ESB 101 processes requests received from the one or more portals 106 relating to mobile wallets that have information stored in the wallet server 104, and orchestrates procedures among such systems, for example, to provide integrated access to information and/or operations relating to such mobile wallets. In some example embodiments, the system 100 does not include the ESB 101 and the functions implemented by the ESB 101 are implemented by the wallet server 104 instead, or by any other interconnected system (e.g., a trusted service manager) programmed to execute such functionality.
As shown in FIG. 1, the ESB 101 includes an ESB proxy service 102 and an ESB task/utility service 103 (which may also be referred to herein as an “ESB task service”). The ESB proxy service 102 acts as an intermediary for requests received, by way of the network 107 and the gateway 105, from external systems (e.g., the portals 106 and/or the external partner system(s) 108) seeking resources (e.g., mobile-wallet-related information and/or operations) from the wallet server 104.
As described in further detail below, upon receiving such a request, the gateway 105 executes an authentication procedure to authenticate the system from which the request originated (e.g., the portals 106 or the external partner system 108, also referred to herein as the “requestor” or the “requesting system”). In some example aspects herein, after authenticating the requesting system, the gateway 105 appends and/or adds to the request a partner system identifier that uniquely identifies the entity with which the requesting system is associated. After the requestor has been authenticated, the gateway 105 forwards the request to the ESB proxy service 102.
Upon receiving the request from the gateway 105, the ESB proxy service 102 cooperates with the ESB task service 103 to execute an authorization procedure for the request and/or further process the request. In particular, the proxy service 102 forwards the request, and/or instructions that the proxy service 102 prepares based on the request, to the ESB task service 103 for further processing. Upon receiving a request and/or other instructions from the proxy service 102, the ESB task service 103 executes one or more tasks (e.g., an authorization procedure, the retrieval and transmission of mobile-wallet-related information from the wallet server 104 to the partner system, the execution of a mobile-wallet-related operation) based on the request and/or the other instructions.
In some example embodiments, the external partner system(s) 108 are systems owned, operated, maintained, and/or provided by external partners (e.g., service providers, MNOs, payment product issuers, and/or the like) with which the ESB 101 interacts to execute operations (e.g., suspension of a mobile wallet account, and/or the like) requested by a partner system relating to one or more mobile wallet accounts associated with the partner system.
III. Procedure
Having described an example system 100 for processing a request relating to a mobile device, reference will now be made to FIG. 2 to describe an example procedure 200 for processing a request relating to a mobile device, in accordance with an example embodiment herein.
At step 201, the gateway 105 receives, from one of the portals 106 associated with a corresponding partner system by way of the network 107, a request relating to a mobile device. As described in further detail below, depending on the type of request, the request may include various types of data elements. In one example embodiment, the request includes a mobile device identifier and a partner system identifier corresponding to the partner system.
In another example embodiment, the request also includes an agent identifier identifying the user (e.g., a consumer agent) of the partner system and/or identifying a predetermined access level associated with the portal 106, the corresponding partner system, and/or the user. The portal 106 includes a graphical user interface (GUI) that enables the user to generate a predetermined set of requests based on a predetermined access level associated with the partner system and the agent identifier.
The request may be for consumer data relating to a mobile wallet associated with the mobile device identifier, and the consumer data may include any one or a combination of: (1) a consumer profile, (2) wallet information, (3) wallet event history, (4) service account information, (5) service account history, and (6) service account event status.
The request may also or alternatively be for performance of an operation relating to a mobile wallet associated with the mobile device identifier. The operation may include any one or a combination of: (1) updating a service account state, (2) updating a mobile wallet state, (3) resetting a password, and (4) resetting a security question and answer.
At step 202, the gateway 105 executes an authentication procedure (e.g., in a known manner by employing standard HTTP authentication certificates and/or a secure sockets layer (SSL) protocol) to authenticate the partner system associated with the portal 106.
At step 203, a determination is made as to whether the partner system associated with the portal 106 was successfully authenticated by the authentication procedure executed at step 202. If the partner system associated with the portal 106 is not successfully authenticated by the authentication procedure executed at step 202 (“No” at step 203), then control passes to step 208 (described below) to transmit a response to the portal 106 indicating that the corresponding partner system was not successfully authenticated.
If, on the other hand, the partner system associated with the portal 106 is successfully authenticated by the authentication procedure executed at step 202 (“Yes” at step 203), then control passes to step 204. At step 204, the gateway 105 appends and/or adds to the request a partner system identifier that uniquely identifies the partner system from which the request originated. The gateway 105 then forwards the request to the ESB 101 for further processing.
At step 205, the ESB 101 executes an authorization procedure based on the mobile device identifier and the partner system identifier. Example authentication procedures that may be executed at step 205 are described in further detail below in connection with FIGS. 3 and 11. In general, however, the step of executing the authorization procedure may include steps of: (1) determining whether a partner system account list, associated with the mobile device identifier, includes the partner system identifier; (2) granting authorization of the request, if the partner system account list includes the partner system identifier; and (3) denying authorization of the request, if the partner system account list does not include the partner system identifier.
At step 206, a determination is made as to whether authorization of the request has been granted at step 205. If authorization of the request has not been granted at step 205 (“No” at step 206), then control passes to step 208 (described below) to transmit a response to the portal 106 indicating that the request has not been authorized.
If, on the other hand, authorization of the request has been granted at step 205 (“Yes” at step 206), then control passes to step 207. At step 207, the ESB 101 and/or the wallet server 104 cooperate to fulfill the request by (1) retrieving the requested information from the wallet server 104 and/or (2) executing the requested operation (e.g., by transmitting one or more commands to a corresponding mobile wallet). At step 208, the ESB 101 transmits, to the portal 106 via the communication network, a response to the request (e.g., including the requested information and/or indicating whether or not the requested operation has been executed successfully).
A. Overview of Requests
As discussed above, various types of requests may be received by the ESB 101 from the portals 106 by way of the network 107 and the gateway 105. Various aspects of such requests will be described in further detail below. In general, the request may be a request for consumer data relating to a mobile device associated with a mobile wallet identifier included in the request. Alternatively, the request may be a request for performance of an operation relating to the mobile wallet associated with the mobile device identifier included in the request.
Depending on the type of request and/or on the type of entity from which the request originates, the request may include different types of messages, data elements, and/or may be communicated via different data flows. As described below in further detail, in one example embodiment, different types of messages, data elements, and data flows are employed for requests that originate from portals 106 associated with MNOs than for requests that originate from portals 106 associated with issuers.
B. Mobile Network Operators
Reference will now be made to FIGS. 3 through 10 to describe various aspects of messages, data elements, and/or data flows that may be employed in connection with requests that originate from a portal 106 associated with an MNO, in accordance with various example embodiments herein.
1. Message Structure
In one example, a request that originates from a portal 106 associated with an MNO includes three components: a message header, a customer proprietary network information (CPNI) header, and a message body. An example set of data elements that may be included in the message header are described below in Table 1.











TABLE 1








Multi-
Data 


Element
Description
Required
plicity
Type







Reference ID
A unique message
Optional
1
String



identifier (UUID) for


(256)



each message generated






by the calling client.






Used for tracking






purposes. Same reference






ID will be provided back






to the synchronous






response and also






asynchronous call back






response.





Transaction ID
This is a unique message
Optional
1
String



identifier (UUID) for


(256)



each message generated






in ESB Layer. Also






called GUID in Oracle






ESB terms.





Originator ID
Originator who creates
Optional
1
String


(also referred 
message; in some cases


(32)


to as a “partner 
may be appended/added





system 
to request by gateway





identifier”)
105.





DateTime Stamp
Date and time when the
Optional
1
DateTime



message is invoked.






Provided by calling






client.









An example set of data elements that may be included in the CPNI header are described below in Table 2.











TABLE 2








Multi-
Data 


Element
Description
Required
plicity
Type







Agent ID
The ID for the agent
Optional
1
String



who creates the


(32)



request.





Consumer MDN
Mobile Device
Required
1
Restricted


(also referred to 
Number.


String(10)


as a “mobile






device identifier”)









2. Authorization Procedure

Having described an example procedure 200 for processing a request relating to a mobile device, reference will now be made to FIG. 3 to describe an example procedure 300 for authorizing a mobile wallet-related request that originates from a portal 106 associated with an MNO, in accordance with an example embodiment herein. In one example embodiment, the procedure 300 further represents the procedure described above in connection with step 206 of FIG. 2.
Although not shown in FIG. 3 for purposes of convenience, prior to step 301, the ESB proxy service 102 extracts a value of a consumer MDN (also referred to as a “mobile device identifier”, described above in Table 2) from the CPNI header, and extracts a value of an originator ID (also referred to as a “partner system identifier”, described above in Table 1) from the message header.
At step 301, the ESB proxy service 102 transmits an authorization request message to the ESB task service 103. This causes the ESB task service 103 to communicate, at step 302, a getInfo message, including the consumer MDN, to the wallet server 104 to retrieve a partner system account list associated with the mobile device identifier.
At step 303, the wallet server 104 communicates a response to the ESB task service 103 including the partner system account list associated with the mobile device identifier.
At step 304, the ESB task service 103 determines whether the partner system account list associated with the mobile device identifier includes the partner system identifier that was extracted from the message header. If the partner system account list associated with the mobile device identifier includes the partner system identifier that was extracted from the message header, then the ESB task service 103 grants authorization of the request. If, on the other hand, the partner system account list associated with the mobile device identifier does not include the partner system identifier that was extracted from the message header, then the ESB task service 103 denies authorization of the request. In this way, each MNO entity is limited to accessing only data and/or operations relating to that particular MNO entity, and is prevented from accessing data and/or operations relating to other MNO entities.
At step 305, the ESB task service 103 communicates a response to the ESB proxy service 102 (and, in some example embodiments, to the gateway 105 and/or the portal 106), indicating whether authorization of the request has been granted or denied.
3. Requests
Having described an example procedure 300 for authorizing a request relating to a mobile device, reference will now be made to FIGS. 4 through 10 to describe example types of requests, message flows/service invocations, messages, and message parameters, in accordance with various example embodiments herein relating to MNOs.
a. Request for Consumer Profile Information
FIG. 4 shows an example procedure 400 for processing a request for consumer profile information relating to a mobile wallet, in accordance with an example embodiment herein. In one example embodiment, procedure 400 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve information, such as a user ID and/or user name, from the wallet server 104.
At step 401, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get consumer profile message), including, for example, the data element described below in Table 3.











TABLE 3








Multi-



Element
Description
Required
plicity
Data Type







MobileDeviceNumber
Mobile Device 
Required
1
Restricted



Number.


String(10)









At step 402, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 3.
If authorization of the request is denied at step 402, then at step 403, the ESB proxy service 102 communicates a message (e.g., a not-authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 402, then at step 404, the ESB proxy service 102 communicates a message (e.g., a get consumer profile message) to the ESB task service 103.
At step 405, the ESB task service 103 communicates the message to the wallet server 104 to request consumer profile information relating to a particular mobile wallet.
At step 406, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 407). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 408). An example set of data elements that may be included in the response is described below in Table 4.











TABLE 4








Multi-



Element
Description
Required
plicity
Data Type







Response
This sub-element
Required
1
Container



specifies the






structure for






generic ESB






response.





ConsumerProfile
This sub-element
Optional
1
Container



specifies the






structure of






Consumer






Profile.









Although not shown in FIG. 4 for purposes of convenience, in some example embodiments herein, the ESB 101 (e.g., the ESB proxy service 102 and/or the ESB task service 103) filters data elements that are included in the response communicated from the wallet server 104 at step 406, for example, to meet requirements of the request communicated at step 401. The filtering may be performed based on, for example, one or more requirements of the request, a predetermined access level associated with a partner system from which the request originated, an agent identifier associated with the request, and/or any other suitable criteria. The response 408 provided by the ESB 101 can include, for instance, all the data elements included in the response communicated at step 406 or only a subset of the data elements included in the response communicated at step 406, the subset having been determined as a result of the filtering. Likewise, the ESB 101 can perform such filtering of other responses (e.g., responses 506, 606, 706, 806, 906, 1006, 1107, 1206, 1306, 1406, 1506, 1606, 1706, and/or 1806 described below in connection with FIGS. 5 through 18, respectively, although not explicitly shown in FIGS. 5 through 18 for purposes of convenience).
An example set of data elements that may be included in the response element shown in Table 4 is described below in Table 5.











TABLE 5








Multi-



Element
Description
Required
plicity
Data Type







ResponseCode
This sub-element
Required
1
Restricted



specifies the






SUCCESS (0) or






FAILURE (1) of






the operation.





ServiceDetails
Specifies the
Required
1
Container



service






information such






as service name,






operation name






and version






number.





InstanceID
Specifies ESB
Required
1
String(256)



Process Instance






ID.





TransactionID
Specifies ESB
Required
1
String(256)



generated Unique






Identifier for a






specific






transaction.





Timestamp
Specifies time of 
Required
1
DateTime



the response.





Error
The Error element 
Optional
0 to 10
Container



is of type






ErrorType which






contains the






structure of






Error/Exception






occurrences during






the execution of






Operation.









An example set of data elements that may be included in the ServiceDetails element shown in Table 5 is described below in Table 6.











TABLE 6








Multi-



Element
Description
Required
plicity
Data Type







ServiceName
Specifies the 
Required
1
String(32)



name of the






service.





OperationName
Specifies the
Required
1
String(32)



name of the






operation within a






service.





Version
Specifies the
Required
1
String(32)



version of the






service.









An example set of data elements that may be included in the Error element shown in Table 5 is described below in Table 7.











TABLE 7








Multi-



Element
Description
Required
plicity
Data Type







ErrorCode
This specifies error code 
Required
1
Integer



associated for each 






exception.





ErrorType
This specifies the type 
Required
1
Restricted



of error/exception. 






Valid values are:






APPLICATION_






EXCEPTION - any 






validations or business 






rules violations.






BUSINESS_






EXCEPTION-






Actual exception 






generated from the 






outbound end system. 






SYSTEM_






EXCEPTION - Any






internal system failure 






exception within the 






ESB layer.





ErrorSeverity
Error Severity. 
Required
1
Restricted



Valid values includes 






1 - Fatal/Critical, 






2 - Medium, 3 - low.





ErrorMessage
Human Readable error 
Required
1
String 



message.


(256)


ErrorDescription
Description of error.
Optional
1
String


ErrorTrace
Specifies detailed error.
Optional
1
String









An example set of data elements that may be included in the ConsumerProfile element shown in Table 4 is described below in Table 8.











TABLE 8








Multi-



Element
Description
Required
plicity
Data Type







SecurityAnswer
Indicates whether user
Required
1
BooleanType


Available
has set up security






question/answer; the






default value is ‘false’.





PersonalInfo
This sub-element
Optional
1
Container



specifies the structure






of personal Info.





ConsumerStatus
Status of the
Optional
1
Restrict



consumer. Defined






statuses include:






ACTIVE, INACTIVE,






LOCKED,






SUSPENDED.





Consumer
Date Timestamp when
Optional
1
DateTime


CreationDate
consumer record is






created.









An example set of data elements that may be included in the PersonalInfo element shown in Table 8 is described below in Table 9.











TABLE 9








Multi-



Element
Description
Required
plicity
Data Type







UserNameInfo
Contains user name
Optional
1
Container



related info.





ContactInfo
Contains user contact
Optional
1
Container



info.









An example set of data elements that may be included in the UserNameInfo element shown in Table 9 is described below in Table 10.











TABLE 10








Multi-



Element
Description
Required
plicity
Data Type







Salutation
This specifies the
Optional
1
Restricted



salutation of






username. Valid






values are: Mr., Ms.,






Mrs.





Firstname
First Name.
Optional
1
String (32)


MiddleName
Middle Name.
Optional
1
String (16)


Lastname
Last Name.
Optional
1
String (32)


Suffix
Suffix of the user.
Optional
1
String (2)









A data element that may be included in the ContactInfo element shown in Table 9 is described below in Table 11.











TABLE 11








Multi-



Element
Description
Required
plicity
Data Type







EmailID
Email address - this is 
Optional
1
Restricted



the email ID used for






wallet activation, it






will return as part of






the response for an






existing consumer.









b. Request for Mobile Wallet Information

FIG. 5 shows an example procedure 500 for processing a request for mobile wallet information, in accordance with an example embodiment herein. In one example embodiment, procedure 500 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 information relating to a mobile wallet, such as a handset profile and/or a number of payment cards associated with the mobile wallet.
At step 501, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get wallet info. message), including, for example, the data element described below in Table 12.











TABLE 12








Multi-
Data 


Element
Description
Required
plicity 
Type







MobileDeviceNumber
Mobile Device
Required
1
Restricted



Number.


String(10)









At step 502, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 3.
If authorization of the request is denied at step 502, then at step 503, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 502, then at step 504, the ESB proxy service 102 communicates a message (e.g., a get wallet info. message) to the ESB task service 103.
At step 505, the ESB task service 103 communicates the message to the wallet server 104 to request consumer profile information relating to a particular mobile wallet.
At step 506, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 507). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 508). An example set of data elements that may be included in the response is described below in Table 13.











TABLE 13








Multi-



Element
Description
Required
plicity 
Data Type







Response
This sub-element 
Required
1
Container



specifies the






structure for






generic ESB






response.





WalletInfo
This sub-element
Optional
1
Container



specifies the






structure of






WalletInfo.









An example set of data elements that may be included in the WalletInfo element shown in Table 13 is described below in Table 14.











TABLE 14








Multi-



Element
Description
Required
plicity
Data Type







WalletInstance
This sub-element
Optional
1
Container



contains aspects






of wallet.





Handset
This sub-element
Optional
1
Container



contains aspects






of handset.





ServiceAccount
This sub-element
Required
1
Container



contains aspects






of service






account.









An example data element that may be included in the WalletInstance element shown in Table 14 is described below in Table 15.











TABLE 15








Multi-



Element
Description
Required
plicity
Data Type







WalletState
Indicates the
Required
1
String (32)



current status of






the wallet






instance.





WalletStateReasonCode
Describes the
Required
1
String



reasons that






land the wallet






in its current






state.





WalletCreationDate
Date timestamp
Optional
1
DateTime



that the wallet






instance is






created. Equates






to the date that






the customer






activates his/her






wallet.





WalletClientVersion
Version number
Required
1
String (10)



of the wallet






client app.





WalletStateUpdateInitiator
Who is
Optional
1
String



responsible for






the last state of






the wallet.









An example set of data elements that may be included in the HandSet element shown in Table 14 is described below in Table 16.











TABLE 16








Multi- 



Element
Description
Required
plicity
Data Type







HandsetID
This sub-
Required
1
Container



element contains






choices of






handset ID.





HandsetProfile
This sub-
Required
1
Container



element contains






aspects of






handset profile.





HandsetState
Indicates the 
Required
1
Restricted



current state of


String 



the handset.


(16)


MobileDeviceNumber
The phone
Required
1
Restricted



number


String 



associated to


(10)



this handset.





MobileNetwork 
This sub-
Required
1
Container


Operator (MNO)
element contains






MNO-related






info.









An example set of data elements that may be included in the HandSetID element shown in Table 16 is described below in Table 17.











TABLE 17








Multi-



Element
Description
Required
plicity
Data Type







IMEI
The International
Required
0 . . . 1
String (15)



Mobile Equipment
while other





Identity or IMEI is 
options not





a number, usually
given





unique, to identify






global system for






mobile






communications






(GSM), wideband






code division






multiple access






(WCDMA), and






integrated digital






enhanced network






(iDEN) mobile






phones, as well as






some satellite






phones. It is






usually found






printed inside the






battery






compartment of the






phone.





MEID
Mobile Equipment
Required
0 . . . 1
String (14)



Identifier (MEID)
while other





is a globally unique 
options not





number identifying
given





a physical piece of






code division






multiple access






(CDMA) mobile






station equipment.





MACAddress
A unique identifier
Required
0 . . . 1
String (12)



assigned to
while other





network interfaces
options not





for
given





communications on






the physical






network segment.









An example set of data elements that may be included in the HandsetProfile element shown in Table 16 is described below in Table 18.











TABLE 18





Element
Description
Required
Multiplicity
Data Type







ModelNumber
Model number
Required
1
String 



associated with


(64)



the handset.





HandsetManufacturer
This sub-
Required
1
Container



element






contains






manufacturer






details of the






handset.





ModelName
Name of the
Required
1
String 



handset model.


(64)


OSPlatform
Name of the
Optional
1
String



operation






system






platform.





OSVersion
Version of the
Optional
1
String 



operation


(32)



system






platform.





DeviceSoftwareClass
This is the
Optional
1
String 



device software


(32)



class of the






handset.









An example set of data elements that may be included in the HandsetManufacturer element shown in Table 18 is described below in Table 19.











TABLE 19









Data 


Element
Description
Required
Multiplicity
Type







ManufacturerID
Manufacturer
Required
1
String 



ID of the


(32)



handset.





ManufacturerName
Name of the
Optional
1
String 



handset


(32)



manufacturer.





ManufacturerDescription
Description of
Optional
1
String 



the


(256)



manufacturer.









An example set of data elements that may be included in the MobileNetworkOperator (MNO) element shown in Table 16 is described below in Table 20.











TABLE 20








Multi-
Data 


Element
Description
Required
plicity
Type







MobileNetworkOperatorID
Unique
Required
1
Restricted



Identifier for


String 



the Mobile


(16)



Network






Operator;






Valid values,






e.g.: MNO1,






MNO2,






MNO3.





MobileNetworkOperator
MNO name.
Required
1
String 


Name



(16)


MobileNetworkOperator
MNO
Optional
1
String 


Description
description.


(256)


MobileNetworkOperator
MNO contact
Optional
1
String 


ContactNumber
number.


(16)









An example data element that may be included in the ServiceAccount element shown in Table 14 is described below in Table 21.











TABLE 21








Multi-
Data 


Element
Description
Required
plicity
Type







NumberOfPaymentCards
Indicates the
Required
1
Integer



number of






payment cards






in the wallet.









c. Request for Wallet Event History

FIG. 6 shows an example procedure 600 for processing a request for wallet event history relating to a mobile wallet, in accordance with an example embodiment herein. In one example embodiment, procedure 600 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 wallet event history information, such as an event date or an event source.
At step 601, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get wallet event history message), including, for example, the data elements described below in Table 22.











TABLE 22








Multi-
Data 


Element
Description
Required
plicity
Type







MobileDeviceNumber
Unique
Required
1
Restricted



consumer


String



identifier.


(10)


StartFrom
Index to specify
Required
1
Integer



from where to






get history






event. The






value needs to






be >0.





Size
Size of history
Required
1
Integer



event to be






returned; the






value depends






on pagination






practice at the






presentation






layer. It cannot






exceed 100






based on the






upper bound






number defined






in wallet event






history list.









At step 602, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 3.
If authorization of the request is denied at step 602, then at step 603, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 602, then at step 604, the ESB proxy service 102 communicates a message (e.g., a get wallet event history message) to the ESB task service 103.
At step 605, the ESB task service 103 communicates the message (e.g., the get wallet event history message) to the wallet server 104 to request wallet event history information relating to a particular mobile wallet.
At step 606, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 607). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 608). An example set of data elements that may be included in the response is described below in Table 23.











TABLE 23








Multi-
Data 


Element
Description
Required
plicity
Type







Response
This sub-element 
Required
1
Container



specifies the






structure for






generic ESB






response.





TotalCount
The total count
Optional
1
Integer



of wallet event






history records.





StartIndex
Where to start
Optional
1
Integer



the records.





EndIndex
Where to end the 
Optional
1
Integer



records.





WalletEventHistory
List of wallet
Optional
0 to 100
Container



event history.









An example set of data elements that may be included in the WalletEventHistory element shown in Table 23 is described below in Table 24.











TABLE 24








Multi-
Data


Element
Description
Required
plicity
Type







EventlD
Event
Required
1
String



identifier.


(32)


EventName
Event name.
Required
1
String


EventDescription
Description for 
Required
1
String



the event.





EventDetails
Event Details.
Required
1
String


EventSource
The source that 
Required
1
String



generates the






event.





EventDateTime
Timestamp
Required
1
DateTime



when event






occurs.









d. Request for Predetermined Processing Workflow Execution Status

FIG. 7 shows an example procedure 700 for processing a request for status regarding executions of predetermined processing workflows relating to a mobile wallet, in accordance with an example embodiment herein. A predetermined processing workflow (also referred to as an ICE cube), in one example, can be executed for one or more mobile devices, and can include instructions that cause one or more systems to perform multiple steps (e.g., by executing specific functions) in succession. In one example embodiment, procedure 700 enables a partner system, such as for example, elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 overall aggregated status from all executions of predetermined processing workflows for a particular mobile device number (associated with a mobile wallet).
At step 701, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get ICE cube status message), including, for example, the data element described below in Table 25.











TABLE 25








Multi-
Data 


Element
Description
Required
plicity
Type







MobileDeviceNumber
Mobile Device 
Required
1
Restricted



Number.


String(10)









At step 702, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 3.
If authorization of the request is denied at step 702, then at step 703, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 702, then at step 704, the ESB proxy service 102 communicates a message (e.g., a get ICE cube status message) to the ESB task service 103.
At step 705, the ESB task service 103 communicates the message (e.g., the get ICE cube status message) to the wallet server 104 to request ICE cube status information relating to a particular mobile wallet.
At step 706, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 707). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 708). An example set of data elements that may be included in the response is described below in Table 26.











TABLE 26





Element
Description
Required
Multiplicity
Data Type







OverallICECube
Aggregated ICE
Optional
1
Restricted


ExecutionStatus
Cube execution


String



status. Valid


(50)



values include:






SUCCESS,






FAILED and






IN_PROCESS.





LastUpdateTime
Date timestamp
Optional
1
DateTime



of the last






update.









e. Request to Update a Mobile Wallet State

FIG. 8 shows an example procedure 800 for processing a request to update a mobile wallet state, in accordance with an example embodiment herein. In one example embodiment, procedure 800 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to request to suspend, reactivate, or terminate a mobile wallet.
At step 801, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., an update wallet state message), including, for example, the set of data elements described below in Table 27.











TABLE 27








Multi-
Data 


Element
Description
Required
plicity
Type







WalletStateUpdatelnitiator
Initiator of the
Required
1
Restricted



wallet state


String



update.





WalletStateUpdateReason
Reason for
Required
1
String(256)



wallet state






update.





MobileDeviceNumber
Mobile Device
Required
1
Restricted



Number.


String(10)


WalletlnstanceID
Unique number
Optional
1
Positive



used to identify


Integer (17



a specific


digits)



wallet instance.





WalletState
State to which
Required
1
Restricted



the wallet


String(32)



needs to be






changed.









At step 802, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 3.
If authorization of the request is denied at step 802, then at step 803, the ESB proxy service 102 communicates a message (e.g., a success/failure message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 802, then at step 804, the ESB proxy service 102 communicates a message (e.g., an update wallet state message) to the ESB task service 103.
At step 805, the ESB task service 103 communicates the message (e.g., the update wallet state message) to the wallet server 104 to request that a wallet state relating to a particular mobile wallet be updated.
At step 806, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 807). An example data element that may be included in the response is described below in Table 28.











TABLE 28





Element
Description
Required
Multiplicity
Data Type







Response
This sub-element
Required
1
Container



specifies the






structure for






generic ESB






response.









f. Request to Reset a Password

FIG. 9 shows an example procedure 900 for processing a request to reset a password associated with a mobile wallet, in accordance with an example embodiment herein. In one example embodiment, procedure 900 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to reset a password relating to a mobile wallet (e.g., a web account password).
At step 901, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a reset password message), including, for example, the data element described below in Table 29.











TABLE 29








Multi-
Data 


Element
Description
Required
plicity
Type







MobileDeviceNumber
Mobile Device
Required
1
Restricted



Number.


String(10)









At step 902, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 3.
If authorization of the request is denied at step 902, then at step 903, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 902, then at step 904, the ESB proxy service 102 communicates a message (e.g., a reset password message) to the ESB task service 103.
At step 905, the ESB task service 103 communicates the message (e.g., the reset password message) to the wallet server 104 to request that a password associated with a particular mobile wallet be reset.
At step 906, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 907). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 908). An example data element that may be included in the response is described below in Table 30.











TABLE 30





Element
Description
Required
Multiplicity
Data Type







Response
This sub-element
Required
1
Container



specifies the






structure for






generic ESB






response.









g. Request to Reset a Security Question and Answer

FIG. 10 shows an example procedure 1000 for processing a request to reset a security question and answer relating to a mobile wallet, in accordance with an example embodiment herein. In one example embodiment, procedure 1000 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to reset a security question and answer relating to a mobile wallet.
At step 1001, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a reset security Q&A message), including, for example, the data element described below in Table 31.











TABLE 31








Multi-



Element
Description
Required
plicity
Data Type







MobileDeviceNumber
Mobile Device
Required
1
Restricted



Number.


String(10)









At step 1002, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 3.
If authorization of the request is denied at step 1002, then at step 1003, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1002, then at step 1004, the ESB proxy service 102 communicates a message (e.g., a reset security Q&A message) to the ESB task service 103.
At step 1005, the ESB task service 103 communicates the message (e.g., the reset security Q&A message) to the wallet server 104 to request that a security question and answer relating to a particular mobile wallet be reset.
At step 1006, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 1007). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 1008). An example data element that may be included in the response is described below in Table 32.











TABLE 32





Element
Description
Required
Multiplicity
Data Type







Response
This sub-element
Required
1
Container



specifies the






structure for






generic ESB






response.









C. Issuers

Having described various example embodiments for processing a mobile wallet-related request received from a MNO with respect to FIGS. 3 through 10, reference will now be made to FIGS. 11 through 17 to describe various aspects of messages, data elements, and/or data flows that may be employed in connection with requests that originate from a portal 106 associated with an issuer, in accordance with various example embodiments herein.
1. Message Structure
In one example, a request that originates from a portal 106 associated with an issuer includes at least three components: a message header, an HTTP header, and a message body. An example set of data elements that may be included in the message header are described below in Table 33.











TABLE 33









Data


Element
Description
Required
Multiplicity
Type







Reference ID
A unique message
Optional
1
String



identifier (UUID) 


(256)



for each message






generated by the






calling client. Used 






for tracking purpose






from client. Same






Reference ID will






be provided back to






the synchronous 






response and also






asynchronous call






back response.





Transaction ID
UUID for each 
Optional
1
String



message generated


(256)



in ESB Layer. Also






called GUID in






Oracle ESB terms.





Originator ID
Originator who 
Optional
1
String


(also referred 
creates message; in 


(32)


to as a “partner
some cases may be 





system
appended/added to 





identifier”)
request by gateway 






105.





DateTime 
Date and time when 
Optional
1
DateTime


Stamp
the message is 






invoked. Provided 






by calling client.









An example data element that may be included in the HTTP header is described below in Table 34.










TABLE 34





Element
Description
Required
Data type







SERVICE_PROVIDER_ID
Service_ID or identifier
Mandatory
String



of the issuer or service





provider who initiates





the request.









2. Authorization Procedure

FIG. 11 shows an example procedure 1100 for authorizing a mobile device-related request that originates from a portal 106 associated with an issuer, in accordance with an example embodiment herein. In one example embodiment, the procedure 1100 further represents the procedure described above in connection with step 206 of FIG. 2.
Although not shown in FIG. 11 for purposes of convenience, prior to step 1101, the ESB proxy service 102 extracts a value of a service provider ID (also referred to as a “partner system identifier”, described above in Table 34) from the HTTP header, and extracts a value of a consumer MDN (also referred to as a “mobile device identifier”) from the message body.
At step 1101, the ESB proxy service 102 receives a request message (e.g., an invocation message) from the portal 106.
At step 1102, the ESB proxy service 102 transmits an authorization request message to the ESB task service 103. This causes the ESB task service 103 to communicate, at step 1103, a getInfo message, including the extracted consumer MDN, to the wallet server 104 to retrieve a partner system account list associated with the mobile device identifier.
At step 1104, the wallet server 104 communicates a response to the ESB task service 103 including the partner system account list associated with the mobile device identifier.
The ESB task service 103 then determines whether the partner system account list associated with the mobile device identifier includes the partner system identifier that was extracted from the message header. If the partner system account list associated with the mobile device identifier includes the partner system identifier that was extracted from the message header, then the ESB task service 103 grants authorization of the request. If, on the other hand, the partner system account list associated with the mobile device identifier does not include the partner system identifier that was extracted from the message header, then the ESB task service 103 denies authorization of the request. In this way, each issuer entity is limited to accessing only data and/or operations relating to or permitted for that particular issuer entity, and is prevented from accessing data and/or operations relating to other issuer entities.
At step 1105, the ESB task service 103 communicates a response (e.g., an “is authorized” response or an “is not authorized” response) to the ESB proxy service 102, indicating whether authorization of the request has been granted or denied.
At step 1106, if authorization of the request is granted, then the ESB proxy service 102 communicates, based on the invocation message received at step 1101, to the wallet server 104 a request for information and/or performance of an operation relating to a mobile device.
At step 1107, the wallet server 104 communicates a response to the ESB proxy service 102, which, in turn, communicates the response to the portal 106 at step 1108.
3. Requests
Having described an example procedure 1100 for authorizing a request relating to a mobile device, reference will now be made to FIGS. 12 through 17 to describe example types of requests, message flows/service invocations, messages, and message parameter, in accordance with various example embodiments herein relating to issuers.
a. Request for Consumer Profile Information
FIG. 12 shows an example procedure 1200 for processing a request for consumer profile information relating to a mobile wallet, in accordance with an example embodiment herein. In one example embodiment, procedure 1200 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve information, such as a user ID and/or user name, from the wallet server 104.
At step 1201, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get consumer profile message), including, for example, the set of data elements described below in Table 35.











TABLE 35





Element
Description
Required
Multiplicity
Data Type







GetConsumerProfile
A root element for the request
Required
1
Container


Request
message which is used by






GetConsumerProfile operation.





MobileDeviceNumber
Mobile Device Number.
Required
1
String









At step 1202, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 11.
If authorization of the request is denied at step 1202, then at step 1203, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1202, then at step 1204, the ESB proxy service 102 communicates a message (e.g., a get consumer profile message) to the ESB task service 103.
At step 1205, the ESB task service 103 communicates the message to the wallet server 104 to request consumer profile information relating to a particular mobile wallet.
At step 1206, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 1207). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 1208). An example set of data elements that may be included in the response is described below in Table 36.











TABLE 36





Element
Description
Required
Multiplicity
Data Type







Response
This sub-element
Required
1
Container



specifies the






structure for generic






ESB response.





UserNamelnfo
This sub-element
Optional
1
Container



specifies the






structure for






UserName.





UserID
The user ID that
Optional
1
String



the consumer will






be used to sign-in






to the portal






application. This ID






must be unique.





ConsumerStatus
Status of the
Optional
1
Restricted



consumer.






Potential statuses






include:—ACTIVE,






INACTIVE,






LOCKED,






SUSPENDED.





ZipCode
Zip Code of
Optional
1
Integer



consumer.









An example set of data elements that may be included in the UserNameInfo element shown in Table 36 is described below in Table 37.











TABLE 37





Element
Description
Required
Multiplicity
Data Type







Salutation
This specifies the
Optional
1
Restricted



salutation of






username. Valid






values are: Mr.,






Ms., Mrs.





Firstname
First name of user
Optional
1
String(32)



name.





MiddleName
Middle name of
Optional
1
String(16)



user name.





Lastname
Last name of user
Optional
1
String(32)



name.





Suffix
Suffix of the user.
Optional
1
String(2)









An example set of data elements that may be included in the Response element shown in Table 36 is described below in Table 38.











TABLE 38





Element
Description
Required
Multiplicity
Data Type







ResponseCode
This sub-element
Required
1
Restricted



specifies the






SUCCESS (0) or






FAILURE (1) of






the operation.





ServiceDetails
Specifies the
Required
1
Container



service






information like






service name,






operation name






and version






number.





InstanceId
Specifies ESB
Required
1
String(256)



Process Instance






ID.





TransactionID
Specifies ESB
Required
1
String(256)



generated Unique






Identifier for a






specific






transaction.





Timestamp
Specifies time of
Required
1
DateTime



the Response.





Error
The Error element
Optional
0 to 10
Container



is of type






ErrorType which






contains the






structure of






Error/Exception






occurs during the






execution of






operation.









An example set of data elements that may be included in the ServiceDetails element shown in Table 38 is described below in Table 39.











TABLE 39





Element
Description
Required
Multiplicity
Data Type







ServiceName
Specifies the
Required
1
String(32)



name of the






Service.





OperationName
Specifies the
Required
1
String(32)



name of the






operation within 






a service.





Version
Specifies the
Required
1
String(32)



version of the






service.









An example set of data elements that may be included in the Error element shown in Table 38 is described below in Table 40.











TABLE 40





Element
Description
Required
Multiplicity
Data Type







ErrorCode
This specifies error code
Required
1
Integer



associated for each exception.





ErrorType
This specifies the type of
Required
1
Restricted



error/exception. Valid values






are APPLICATION_






EXCEPTION—any validations 






or business rules violations.






BUSINESS_ EXCEPTION—






Actual exception generated






from the outbound end system.






SYSTEM_EXCEPTION—Any






internal system failure






exception within the ESB layer.





ErrorSeverity
Error Severity. Valid values
Required
1
Restricted



include: 1—Fatal, 2—Critical.





ErrorMessage
Human Readable error
Required
1
String (256)



message.





ErrorDescription
Description of error.
Optional
1
String


ErrorTrace
Specifies detailed error stack
Optional
1
String



trace.









b. Request for Mobile Wallet Information

FIG. 13 shows an example procedure 1300 for processing a request for mobile wallet information, in accordance with an example embodiment herein. In one example embodiment, procedure 1300 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 information relating to a mobile wallet, such as a handset profile and/or a number of payment cards associated with the mobile wallet.
At step 1301, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get wallet info. message), including, for example, the data elements described below in Table 41.











TABLE 41





Element
Description
Required
Multiplicity
Data Type







GetWalletInfoRequest
A root element for the
Required
1
Container



request message which is






used by GetWalletInfo






operation.





MobileDeviceNumber
Unique consumer identifier.
Required
1
String









At step 1302, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 11.
If authorization of the request is denied at step 1302, then at step 1303, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1302, then at step 1304, the ESB proxy service 102 communicates a message (e.g., a get wallet info. message) to the ESB task service 103.
At step 1305, the ESB task service 103 communicates the message to the wallet server 104 to request consumer profile information relating to a particular mobile wallet.
At step 1306, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 1307). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 1308). An example set of data elements that may be included in the response is described below in Table 42.











TABLE 42





Element
Description
Required
Multiplicity
Data Type







Response
This sub-element
Required
1
Container



specifies the






structure for






generic ESB






response.





WalletInfo
This sub-element
Optional
0 to 100
Container



specifies the






structure of






WalletInfo.









An example set of data elements that may be included in the WalletInfo element shown in Table 42 is described below in Table 43.











TABLE 43





Element
Description
Required
Multiplicity
Data Type







HandSet
This sub-element specifies the
Optional
1
Container



structure for HandSet.





WalletCreationDate
The Wallet Creation Date.
Optional
1
DateTime


WalletState
Indicates the current wallet state.
Optional
1
Restricted



Valid values include: WALLET_






ACTIVE—Wallet is Active;






WALLET_ACTIVATION_






PENDING—Wallet Activation is






Pending;






WALLET_SUSPENDED—Wallet






is Suspended;






WALLET_SUSPENSION_






PENDING—Wallet Suspension






is Pending;






WALLET_RESETPASSCODE_






PENDING—Wallet ResetPasscode






is Pending;






WALLET_TERMINATED—






Wallet is Terminated;






WALLET_TERMINATION_






PENDING—Wallet Termination






is Pending;






WALLET_LOCKED—Wallet is






locked;






WALLET_RESUME_PENDING






Wallet ReActivation is Pending;






WALLET_MDN_VALIDATION_






PENDING Wallet MDN validation






is Pending;






CHANGE_ DETECTED






Change Detected;






APP_DATA_ERASED






Wallet is terminated and the






application data has been






successfully removed from the






consumer device.





WalletStateReasonCode
Describes the reason that the wallet
Optional
1
String



is in its current state. Potential 






reason codes include the following:






MNO Initiated, Consumer Initiated,






Mobile Wallet Provider Initiated, 






Lost/Stolen, Expiration Date






Reached.





WalletlnstanceID
Unique number used to identify a
Optional
1
Wallet



specific wallet instance.


Instance ID






Type


WalletClientVersion
Represents Wallet Client App
Optional
1
String 10



Version.


Type (string:






with 10






characters)









An example set of data elements that may be included in the HandSet element shown in Table 43 is described below in Table 44.











TABLE 44





Element
Description
Required
Multiplicity
Data Type







HandsetID
Unique identifier 
Required
1
Container



of the handset.






Handset ID is the






IMEI for GSM






devices and the






MEID for 






CDMA handsets.





HandsetProfile
This sub-element
Required
1
Container



specifies the 






structure for






HandSet Profile.





HandsetState
Current state of 
Optional
1
Restricted



the handset. List 






of valid status 






includes: Active,






Inactive, 






Suspended.









An example set of data elements that may be included in the HandSetID element shown in Table 44 is described below in Table 45.











TABLE 45





Element
Description
Required
Multiplicity
Data Type







IMEI
The
Required
0...1
String (15)



International
while other





Mobile
options not





Equipment
given





Identity or IMEI






is a number,






usually unique,






to identify






global system






for mobile






communications






(GSM),






wideband code






division






multiple access






(WCDMA), and






integrated






digital enhanced






network (iDEN)






mobile phones,






as well as some






satellite phones.






It is usually






found printed






inside the






battery






compartment of






the phone.





MEID
Mobile
Required
0...1
String (14)



Equipment
while other





Identifier
options not





(MEID) is a
given





globally unique






number






identifying a






physical piece






of code division






multiple access






(CDMA)






mobile station






equipment.





MACAddress
A unique
Required
0...1
String (12)



identifier
while other





assigned to
options not





network
given





interfaces for






communications






on the physical






network






segment.









An example set of data elements that may be included in the HandsetProfile element shown in Table 44 is described below in Table 46.











TABLE 46





Element
Description
Required
Multiplicity
Data Type







ModelNumber
Model number
Required
1
String (64)



associated with the






handset.





HandsetManufacturer
This sub-element
Required
1
Container



contains






manufacturer






details of the






handset.





ModelName
Name of the handset
Required
1
String (64)



model.





OSPlatform
Name of the operation
Optional
1
String



system platform.





OSVersion
Version of the
Optional
1
String (32)



operation system






platform.





Device SoftwareClass
Device software class
Optional
1
String (32)



of the handset.





MobileDeviceNumber
Mobile Number of the
Required
1
String(10)



handset.





MobileNetworkOperator
Mobile Network
Required
1
Container



Operator—Refers






to the participating






wireless service






providers.









An example set of data elements that may be included in the HandsetManufacturer element shown in Table 46 is described below in Table 47.











TABLE 47





Element
Description
Required
Multiplicity
Data Type







ManufacturerID
The unique ID for
Required
1
iwt: Manufacturer



the Manufacturer


ID Type



in Wallet Platform.





ManufacturerName
Name of the handset
Optional
1
iwt: Manufacturer



manufacturer.


ID Type


ManufacturerDescription
Description of the
Optional
1
String (256)



manufacturer.









An example set of data elements that may be included in the MobileNetworkOperator (MNO) element shown in Table 46 is described below in Table 48.











TABLE 48





Element
Description
Required
Multiplicity
Data Type







MobileNetworkOperatorID
Unique Identifier
Required
1
Restricted



for the Mobile






Network






Operator; valid






values: MNO1,






MNO2, MNO3.





MobileNetworkOperator 
Textual name
Required
1
String (16)


Name
associated with






the MNO.





MobileNetworkOperator
Textual
Optional
1
String (256)


Description
description of






the MNO.





MobileNetworkOperator
Operator
Optional
1
String (16)


ContactNumber
Contact Phone






Number.









c. Request for Service Account Information

FIG. 14 shows an example procedure 1400 for processing a request for service account information relating to a mobile wallet, in accordance with an example embodiment herein. In one example embodiment, procedure 1400 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 service account information, such as a record of history for a service account relating to a mobile wallet.
At step 1401, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get service account info. message), including, for example, the data elements described below in Table 49.











TABLE 49





Element
Description
Required
Multiplicity
Data Type







GetServiceAccount
A root element for the
Required
1
Container


InfoRequest
request message which 






is used by






GetServiceAccountInfo






operation.





MobileDeviceNumber
Unique consumer Identifier.
Required
1
String









At step 1402, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 11.
If authorization of the request is denied at step 1402, then at step 1403, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1402, then at step 1404, the ESB proxy service 102 communicates a message (e.g., a get service account info. message) to the ESB task service 103.
At step 1405, the ESB task service 103 communicates the message (e.g., the get service account info. message) to the wallet server 104 to request service account information relating to a particular mobile wallet.
At step 1406, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 1407). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 1408). An example set of data elements that may be included in the response is described below in Table 50.











TABLE 50





Element
Description
Required
Multiplicity
Data Type







Response
This sub-element
Required
1
Container



specifies the






structure for






generic ESB






response.





ServiceAccount
This sub-element
Optional
0 to 2500
Container



specifies the






structure for






Service Account.









An example set of data elements that may be included in the ServiceAccount element shown in Table 50 is described below in Table 51.











TABLE 51





Element
Description
Required
Multiplicity
Data Type







Service
A unique number provided by the
Required
1
Restricted


AccountRef Nbr
service provider to uniquely identify






a service account.





ServiceProduct
Type of the Service Product.
Required
1
Restricted


Type
Service Product Types:






CREDIT,






LINKED_CHECKING_OR_DEBIT,






PRE_PAID, CASH.





ProductBrand
Unique identifier for the service 
Required
1
Restricted


ProfileID
product associated with the






service account.





Payment Network
The network for payment processing.
Required
1
Restricted



Valid values:






NETWORK1, NETWORK2,






NETWORK3.





ServiceAccount
Indicates the current state of the
Optional
1
Restricted


State
service account. Possible status values






are:






REGISTERED—indicates the service






account has been sent to the handset






but the wallet instance associated






with the MDN has not yet been 






activated;






WAITING_FOR_ACTIVATION—






service account has been provisioned






to the handset but the user has not






activated the account;






ACTIVE—service account is active 






on the handset and usable by the user;






SUSPENDED—use of the service






account has been frozen by the issuer/






service provider. Service account in






SUSPENDED state cannot be used






for purchases but can be used for






payments applied to the account. A






service account in frozen state can be






changed back to Active state;






CLOSED_TO_NEW_PURCHASES—






service account has been closed by






either the owner or the issuer/service






provider. An account in this state






cannot be used for purchases but is still






available for payments to be applied to






the account;






CLOSED—service account has been






closed by either the owner or the issuer/






service provider. Service account in






Closed state cannot be used and cannot






be changed back to Active state.









d. Request for Wallet Event History

FIG. 15 shows an example procedure 1500 for processing a request for wallet event history relating to a mobile wallet, in accordance with an example embodiment herein. There can be various events recorded in connection with a mobile wallet, such as, for example the provision of the wallet, the termination of the wallet, and/or the like. In one example embodiment, procedure 1500 enables a partner system, such as for example, elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 wallet event history information, such as an event date or an event source.
At step 1501, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get wallet event history message), including, for example, the data elements described below in Table 52.











TABLE 52





Element
Description
Required
Multiplicity
Data Type







GetWalletEvent
A root element for the request
Required
1
Container


HistoryRequest
message which is used by






GetWalletEventHistory






operation.





MobileDevice
Unique consumer identifier.
Required
1
String


Number






StartFrom
Index to specify from where to get
Required
1
Integer



history event.





Size
Size of history event to be returned.
Required
1
Integer









At step 1502, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 11.
If authorization of the request is denied at step 1502, then at step 1503, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1502, then at step 1504, the ESB proxy service 102 communicates a message (e.g., a get wallet event history message) to the ESB task service 103.
At step 1505, the ESB task service 103 communicates the message (e.g., the get wallet event history message) to the wallet server 104 to request wallet event history information relating to a particular mobile wallet.
At step 1506, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 1507). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 1508). An example set of data elements that may be included in the response is described below in Table 53.











TABLE 53





Element
Description
Required
Multiplicity
Data Type







Response
This sub-
Required
1
Generic



element


Response



specifies the 


Type



structure for 






generic ESB






response.





TotalCount
The total 
Optional
1
Integer



count of






wallet event 






history 






records.





StartIndex
Where to 
Optional
1
Integer



start the






records.





EndIndex
Where to 
Optional
1
Integer



end the






records.





WalletEventHistory
List of 
Optional
0 to 100
Wallet 



wallet event


Event



history.


History 






Type









An example set of data elements that may be included in the WalletEventHistory element shown in Table 53 is described below in Table 54.











TABLE 54





Element
Description
Required
Multiplicity
Data Type







EventID
Event ID.
Required
1
String(32)


EventName
Event name.
Required
1
String


EventDescription
Description for
Required
1
String



the event.





EventDetails
Event Details.
Required
1
String


EventSource
The source that
Required
1
String



generates the






event.





EventDateTime
Timestamp
Required
1
DateTime



when event






occurs.









e. Request for Service Account History

FIG. 16 shows an example procedure 1600 for processing a request for service account history relating to a mobile wallet, in accordance with an example embodiment herein. In one example embodiment, procedure 1600 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 service account history information associated with a mobile wallet.
At step 1601, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get service account history message), including, for example, the data elements described below in Table 55.











TABLE 55





Element
Description
Required
Multiplicity
Data Type







GetServiceAccount
A root element for the
Required
1
Container


HistoryRequest
request message which






is used by






GetServiceAccount






History operation.





MobileDeviceNumber
Unique consumer identifier.
Required
1
String


StartFrom
Index to specify from
Required
1
Integer



where to get history






event.





Size
Size of history event to
Required
1
Integer



be returned.









At step 1602, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 11.
If authorization of the request is denied at step 1602, then at step 1603, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1602, then at step 1604, the ESB proxy service 102 communicates a message (e.g., a get service account history message) to the ESB task service 103.
At step 1605, the ESB task service 103 communicates the message (e.g., the get service account history message) to the wallet server 104 to request wallet event history information relating to a particular mobile wallet.
At step 1606, the wallet server 104 communicates a response to the ESB task service 103, which in turn communicates the response to the ESB proxy service 102 (step 1607). The ESB proxy service 102 in turn communicates the response to the portal 106 (step 1608). An example set of data elements that may be included in the response is described below in Table 56.











TABLE 56





Element
Description
Required
Multiplicity
Data Type







Response
This sub-element specifies the
Required
1
Generic



structure for generic ESB response.


Response




Type




TotalCount
The total count of
Optional
1
Integer



ServiceAccountEvent History records.





StartIndex
Where to start the records.
Optional
1
Integer


EndIndex
Where to end the records.
Optional
1
Integer


ServiceAccountEvent
List of service account event history.
Optional
0 to 100
Service


History



Account






Event






History






Type









An example set of data elements that may be included in the ServiceAccountEvent element shown in Table 56 is described below in Table 57.











TABLE 57





Element
Description
Required
Multiplicity
Data Type







ServiceAccountRefNbr
A unique
Optional
1
String 



number


100



provided by 






the service






provider to






uniquely






identify a






service






account.





EventID
Event ID.
Required
1
String 32


EventName
Event name.
Required
1
String


EventDescription
Description 
Required
1
String



for the event.





EventDetails
Event 
Required
1
String



Details, Data






associated 






with event






shall also be






presented






here.





EventSource
The source 
Required
1
String



that generates 






the event.





EventDateTime
Timestamp
Required
1
DateTime



when event






occurs.









f. Request for Service Account Event Status

FIG. 17 shows an example procedure 1700 for processing a request for service account event status relating to a mobile wallet, in accordance with an example embodiment herein. During the lifecycle of a service account, there are various events for a service account, for instance, the provision of the service account. In one example embodiment, procedure 1700 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to retrieve from the wallet server 104 service account event status information relating to a mobile wallet service account.
At step 1701, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., a get service account event status message), including, for example, the data elements described below in Table 58.











TABLE 58





Element
Description
Required
Multiplicity
Data Type







GetServiceAccount
A root element for the request
Required
1
Container


EventStatusRequest
message which is used by






GetServiceAccount






EventStatus operation.





MobileDeviceNumber
Unique consumer identifier.
Required
1
String









At step 1702, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 11.
If authorization of the request is denied at step 1702, then at step 1703, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1702, then at step 1704, the ESB proxy service 102 communicates a message (e.g., a get service account event status message) to the ESB task service 103.
At step 1705, the ESB task service 103 communicates the message (e.g., the get service account event status message) to the wallet server 104 to request wallet event history information relating to a particular mobile wallet.
At step 1706, the wallet server communicates a response to the ESB task service 103, which communicates the response to the ESB proxy service 102 (step 1707), which communicates the response to the portal 106 (step 1708). An example set of data elements that may be included in the response is described below in Table 59.











TABLE 59





Element
Description
Required
Multiplicity
Data Type







Response
This sub-
Required
1
Container



element






specifies the






structure for






generic ESB






response.





ServiceAccountEvent
Service 
Optional
0 to 25
Container


Status
Account






event status.









An example set of data elements that may be included in the ServiceAccountEventStatus element shown in Table 59 is described below in Table 60.











TABLE 60









Data 


Element
Description
Required
Multiplicity
Type







Name
Name.
Required
1
String


Status
Unique
Required
1
String



identifier for






the status 






of the event 






of a service






account with 






a specific






provider.





ErrorMessage
Error 
Optional
1
String



Message






in the event.





EventDateTime
Time that 
Required
1
DateTime



the event






occurs.





ServiceAccountRefNr
A reference
Optional
1
String 



number


100



provided by






the service






provider to






identify the






payment






account 






used in the






transaction.









g. Request for Update to Service Account State

FIG. 18 shows an example procedure for processing a request to update a service account state, in accordance with an example embodiment herein. In one example embodiment, procedure 1800 enables a partner system, such as elements 106 and/or 108 of FIG. 1 (which may be operated by an agent), to request that a service account state associated with a mobile wallet be updated. At step 1801, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., an update service account message), including, for example, the data elements described below in Table 61.











TABLE 61





Element
Description
Required
Multiplicity
Data Type







UpdateServiceAccount
A root element for the request
Required
1
Container


StateRequest
message which is used by






UpdateServiceAccount






State operation.





MobileDeviceNumber
Unique consumer identifier.
Required
1
String


ServiceAccountRefNbr
Service Account Reference
Required
1
String



Number.





ServiceAccountState
Service Account State.
Required
1
String









At step 1801, the portal 106 transmits to the ESB proxy service 102 a request message (e.g., an update service account state message), including, for example, the data elements described below in Table 62.











TABLE 62





Element
Description
Required
Multiplicity
Data Type







UpdateServiceAccount
A root element for the
Required
1
Container


StateRequest
request message which is






used by






UpdateServiceAccount






State operation.





MobileDeviceNumber
Unique consumer
Required
1
String



identifier.





ServiceAccountRefNbr
Service Account
Required
1
String



Reference Number.





ServiceAccountState
Service Account State.
Required
1
String









At step 1802, the ESB proxy service 102 executes an authorization procedure for the request, in the manner described above in connection with FIG. 11.
If authorization of the request is denied at step 1802, then at step 1803, the ESB proxy service 102 communicates a message (e.g., a not authorized response message) to the portal 106 to indicate that authorization of the request is denied.
If, on the other hand, authorization of the request is granted at step 1802, then at step 1804, the ESB proxy service 102 communicates a message (e.g., an update service account state message) to the ESB task service 103.
At step 1805, the ESB proxy service 102 communicates an acknowledge message to the portal 106 to confirm that the service account state is being updated.
At step 1806, the ESB task service 103 communicates a response to the ESB proxy service 102, which confirms that the service account state has been updated.
As can be appreciated in view of the above, the systems, methods, and computer program products presented herein for processing a request relating to a mobile communication device enable the safeguarding of information relating to mobile communication devices and the restriction of access to operations relating to mobile communication devices, while also providing consumer care systems and/or agents with a level of access to such information and/or operations that is sufficient for consumer care purposes.
Example aspects described herein also facilitate the processing of mobile wallet information and/or operation requests that are received from different entities (e.g., a mobile wallet provider, external partners, such as payment product issuers and/or mobile network operators (MNOs), and/or the like) and/or personnel that may provide consumer care in connection with mobile wallets. Different levels of access are provided for specific levels of personnel (e.g., consumer care agents) within a particular entity, in accordance with various example aspects herein.
IV. Example Computer-readable Medium Implementations
The example embodiments described above, such as the systems and procedures depicted in or discussed in connection with FIGS. 1 through 18 or any part or function thereof, may be implemented by using hardware, software or a combination of the two. The implementation may be in one or more computers or other processing systems. While manipulations performed by these example embodiments may have been referred to in terms commonly associated with mental operations performed by a human operator, no human operator is needed to perform any of the operations described herein. In other words, the operations may be completely implemented as machine operations. Useful machines for performing the operation of the example embodiments presented herein include general-purpose digital computers or similar devices.
FIG. 19 is a block diagram of a general and/or special purpose computer 1900 that may be employed in accordance with various example embodiments herein. The computer 1900 may be, for example, a user device, a user computer, a client computer, and/or a server computer, among other things.
The computer 1900 may include without limitation a processor device 1910, a main memory 1925, and an interconnect bus 1905. The processor device 1910 may include without limitation a single microprocessor, or may include a plurality of microprocessors for configuring the computer 1900 as a multi-processor system. The main memory 1925 stores, among other things, instructions and/or data for execution by the processor device 1910. The main memory 1925 may include banks of dynamic random access memory (DRAM), as well as cache memory.
The computer 1900 may further include a mass storage device 1930, peripheral device(s) 1940, portable storage medium device(s) 1950, input control device(s) 1980, a graphics subsystem 1960, and/or an output display 1970. For explanatory purposes, all components in the computer 1900 are shown in FIG. 19 as being coupled via the bus 1905. However, the computer 1900 is not so limited. Devices of the computer 1900 may be coupled via one or more data transport means. For example, the processor device 1910 and/or the main memory 1925 may be coupled via a local microprocessor bus. The mass storage device 1930, peripheral device(s) 1940, portable storage medium device(s) 1950, and/or graphics subsystem 1960 may be coupled via one or more input/output (I/O) buses. The mass storage device 1930 may be a nonvolatile storage device for storing data and/or instructions for use by the processor device 1910. The mass storage device 1930 may be implemented, for example, with a magnetic disk drive or an optical disk drive. In a software embodiment, the mass storage device 1930 is configured for loading contents of the mass storage device 1930 into the main memory 1925.
The portable storage medium device 1950 operates in conjunction with a nonvolatile portable storage medium, such as, for example, a compact disc read only memory (CD-ROM), to input and output data and code to and from the computer 1900. In some embodiments, the software for storing an internal identifier in metadata may be stored on a portable storage medium, and may be inputted into the computer 1900 via the portable storage medium device 1950. The peripheral device(s) 1940 may include any type of computer support device, such as, for example, an input/output (I/O) interface configured to add additional functionality to the computer 1900. For example, the peripheral device(s) 1940 may include a network interface card for interfacing the computer 1900 with a network 1920.
The input control device(s) 1980 provide a portion of the user interface for a user of the computer 1900. The input control device(s) 1980 may include a keypad and/or a cursor control device. The keypad may be configured for inputting alphanumeric characters and/or other key information. The cursor control device may include, for example, a mouse, a trackball, a stylus, and/or cursor direction keys. In order to display textual and graphical information, the computer 1900 may include the graphics subsystem 1960 and the output display 1970. The output display 1970 may include a cathode ray tube (CRT) display and/or a liquid crystal display (LCD). The graphics subsystem 1960 receives textual and graphical information, and processes the information for output to the output display 1970.
Each component of the computer 1900 may represent a broad category of a computer component of a general and/or special purpose computer. Components of the computer 1900 are not limited to the specific implementations provided here.
Portions of the example embodiments of the invention may be conveniently implemented by using a conventional general-purpose computer, a specialized digital computer and/or a microprocessor programmed according to the teachings of the present disclosure, as is apparent to those skilled in the computer art. Appropriate software coding may readily be prepared by skilled programmers based on the teachings of the present disclosure.
Some embodiments may also be implemented by the preparation of application-specific integrated circuits, field programmable gate arrays, or by interconnecting an appropriate network of conventional component circuits.
Some embodiments include a computer program product. The computer program product may be a storage medium or media having instructions stored thereon or therein which can be used to control, or cause, a computer to perform any of the procedures of the example embodiments of the invention. The storage medium may include without limitation a floppy disk, a mini disk, an optical disc, a Blu-Ray Disc, a DVD, a CD-ROM, a micro-drive, a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory, a flash card, a magnetic card, an optical card, nanosystems, a molecular memory integrated circuit, a RAID, remote data storage/archive/warehousing, and/or any other type of device suitable for storing instructions and/or data.
Stored on any one of the computer-readable medium or media, some implementations include software for controlling both the hardware of the general and/or special computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the example embodiments of the invention. Such software may include without limitation device drivers, operating systems, and user applications. Ultimately, such computer-readable media further includes software for performing example aspects of the invention, as described above.
Included in the programming and/or software of the general and/or special purpose computer or microprocessor are software modules for implementing the procedures described above.
As can be appreciated in view of the foregoing description, the example aspects herein provide a system, method, and computer-readable medium for managing access control that enable access rules to be updated and enforced in an efficient manner that improves both the user's experience and the utilization of computing resources (e.g., the utilization of processor power, processor time, memory, communication channels, and the like).
Unlike existing approaches to managing access control, which employ an inefficient polling scheme whereby, for example, a refresh tag associated with access rules is periodically polled, irrespective of whether any updates have been made to the access rules, in accordance with the example aspects described herein, updates to access rules are retrieved only upon the rules having been updated.
Also, the example aspects described herein, unlike existing approaches, avoid the need to poll the refresh tag upon receiving a request for information and/or an action protected by the access rules. The user's experience is thus improved since the granting of the request need not be delayed until after both the polling of the refresh tag and the updating of the local access rules have been completed.
While various example embodiments of the invention have been described above, it should be understood that they have been presented by way of example, and not limitation. It is apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein. Thus, the invention should not be limited by any of the above described example embodiments, but should be defined only in accordance with the following claims and their equivalents.
In addition, it should be understood that the figures are presented for example purposes only. The architecture of the example embodiments presented herein is sufficiently flexible and configurable, such that it may be utilized and navigated in ways other than that shown in the accompanying figures.
Further, the purpose of the Abstract is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract is not intended to be limiting as to the scope of the example embodiments presented herein in any way. It is also to be understood that the procedures recited in the claims need not be performed in the order presented.

## Claims

1. A method to process requests relating to mobile devices, comprising:
receiving, from a partner system via a communication network by way of a portal and a gateway, a request including a mobile device identifier, an agent identifier, and a partner system identifier corresponding to the partner system, wherein the portal includes a graphical user interface (GUI) that enables the partner system to generate a predetermined set of requests based on a predetermined access level associated with the partner system and the agent identifier;
authenticating the partner system at the gateway;
executing an authorization procedure based on the mobile device identifier and the partner system identifier, wherein the step of executing the authorization procedure includes steps of:
determining whether a partner system account list, associated with the mobile device identifier, includes the partner system identifier;
granting authorization of the request, if the partner system account list includes the partner system identifier;

transmitting, to the partner system via the communication network, a response to the request, based on a result of the executing step.

2. The method of claim 1, wherein the request is a request for consumer data relating to a mobile wallet associated with the mobile device identifier, the consumer data including any one or a combination of:
a consumer profile,
wallet information,
wallet event history,
service account information,
service account history, and
service account event status.

3. The method of claim 1, wherein, if the authorization of the request is granted, the method further comprises steps of:
retrieving the consumer data from a wallet server; and
including the consumer data in the response.

4. The method of claim 1, wherein the request is a request for performance of an operation relating to a mobile wallet associated with the mobile device identifier, the operation including any one or a combination of:
updating a service account state,
updating a mobile wallet state,
resetting a password, and
resetting a security question and answer.

5. The method of claim 4, wherein, if the authorization of the request is granted, the method further comprises a step of performing the operation by transmitting one or more commands to the mobile wallet.

6. A system to process requests relating to mobile devices, comprising:
a processor; and
at least one memory accessible by the processor and storing at least one of:
computer code executable by the computer processor, and
data used by the computer code,

wherein the computer code includes:
a receiving module that:
receives, from a partner system via a communication network by way of a portal and a gateway, a request including a mobile device identifier, an agent identifier, and a partner system identifier corresponding to the partner system, wherein the portal includes a graphical user interface (GUI) that enables the partner system to generate a predetermined set of requests based on a predetermined access level associated with the partner system and the agent identifier;
authenticates the partner system at the gateway; and

an execution module that executes an authorization procedure based on the mobile device identifier and the partner system identifier, wherein the authorization procedure includes:
determining whether a partner system account list, associated with the mobile device identifier, includes the partner system identifier,
granting authorization of the request, if the partner system account list includes the partner system identifier, and
a transmitting module that transmits, to the partner system via the communication network, a response to the request, based on a result of the authorization procedure executed by the executing module.

7. The system of claim 6, wherein the request is a request for consumer data relating to a mobile wallet associated with the mobile device identifier, the consumer data including any one or more combination of:
a consumer profile,
wallet information,
wallet event history,
service account information,
service account history, and
service account event status.

8. The system of claim 7, wherein the computer code further includes:
a retrieval module that, if the authorization of the request is granted, retrieves the consumer data from a wallet server; and
an inclusion module that, if the authorization of the request is granted, includes the consumer data in the response.

9. The system of claim 6, wherein the request is a request for performance of an operation relating to a mobile wallet associated with the mobile device identifier, the operation including any one or a combination of:
updating a service account state,
updating a mobile wallet state,
resetting a password, and
resetting a security question and answer.

10. The system of claim 9, wherein the computer code further includes:
a performance module that, if the authorization of the request is granted, performs the operation by transmitting one or more commands to the mobile wallet.

11. A non-transitory computer-readable medium having stored thereon sequences of instructions that, when executed by a computer processor, cause the computer processor to:
receive, from a partner system via a communication network by way of a portal and a gateway, a request including a mobile device identifier, an agent identifier, and a partner system identifier corresponding to the partner system, wherein the portal includes a graphical user interface (GUI) that enables the partner system to generate a predetermined set of requests based on a predetermined access level associated with the partner system and the agent identifier;
authenticate the partner system at the gateway; and
execute an authorization procedure based on the mobile device identifier and the partner system identifier, wherein the authorization procedure includes:
determining whether a partner system account list, associated with the mobile device identifier, includes the partner system identifier,
granting authorization of the request, if the partner system account list includes the partner system identifier, and

transmit, to the partner system via the communication network, a response to the request, based on a result of the executing of the authentication procedure.

12. The non-transitory computer-readable medium of claim 11, wherein the request is a request for consumer data relating to a mobile device associated with the mobile wallet identifier, the consumer data including any one or a combination of:
a consumer profile,
wallet information,
wallet event history,
service account information,
service account history, and
service account event status.

13. The non-transitory computer-readable medium of claim 12, wherein the sequences of instructions, when executed by the computer processor, further cause the computer processor to:
retrieve the consumer data from a wallet server, if the authorization of the request is granted; and
include the consumer data in the response, if the authorization of the request is granted.

14. The non-transitory computer-readable medium of claim 11, wherein the request is a request for performance of an operation relating to a mobile wallet associated with the mobile device identifier, the operation including any one or a combination of:
updating a service account state,
updating a mobile wallet state,
resetting a password, and
resetting a security question and answer.

15. The non-transitory computer-readable medium of claim 14, wherein if the authorization of the request is granted, the sequences of instructions, when executed by the computer processor, further cause the computer processor to perform the operation by transmitting one or more commands to the mobile wallet.