Selecting ecosystem features for inclusion in operational tiers of a multi-domain ecosystem platform for secure personalized transactions

• US 10,026,079 B2
• Filed: 12/04/2013
• Issued: 07/17/2018
• Est. Priority Date: 10/06/2005
• Status: Active Grant

• Current Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Original Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Inventors: Desai, Mehul, Pitroda, Satyan G., Maniar, Nehal
• Primary Examiner(s): Zeender, Florian M
• Assistant Examiner(s): Racic, Milena
• Application Number:
  US14/096,711
• Publication Number:
  US 20140089113A1
• Time in Patent Office: 1,686 Days
• Field of Search: 705 16, 705 21
• CPC Class Codes: G05B 2219/25107 Pluggable card, magnetic or smart with configuration data, staying in device
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 3/08 from or to individual record carriers, e.g. punched card , memory card, integrated circuit [IC] card or smart card
• CPC Class Codes: G06K 7/0065 comprising keyboard or display, e.g. a pocket calculator sized casing suitable for off-line checking the remaining money on a smart banking card
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Selecting ecosystem features for inclusion in operational tiers includes taking a reference implementation of a specific application adapted to operate in a multi-domain computing ecosystem and, using a computer, breaking down the reference implementation into service related components, determining ecosystem participants for the reference implementation, and using a feature allocation engine to configure operational features that enable one of the service related components.

Claims

1. A method of automating configuration of servers and mobile clients as new participants in a multi-domain ecosystem comprising:

taking a data structure of a reference implementation of a specific server-executable application operating across a client device and a server, the application using each of a service tier, a personalization tier, and an enablement tier in a multi-domain computing ecosystem;

using heuristics in an analysis of the data structure, the analysis performed by a computer to automatically break down the reference implementation into ecosystem configurable features selected from the list consisting of;

service requirements, customer requirements, end-user requirements, regulatory mandates, regulatory guidelines, security mandates, security guidelines, security requirements, trust models, economic models, business logic, business workflow, commonality with other services, operational factors, design factors, technology factors, devices, platforms, projected technology evolution, and operating constraints;

automatically determining with a networked computing device participants for the reference implementation selected from the list consisting of;

end users, network providers, merchants, service providers, transaction instrument acquirers, transaction instrument issuers, widget providers, wallet providers, and trusted service managers;

analyzing the broken down ecosystem configurable features of the reference implementation in view of service provider requirements for participating in the multi-domain ecosystem, thereby automatically establishing multi-domain ecosystem feature configuration parameters for effecting the implementation of each of the service tier, the enabling tier, and the personalization tier for at least a server of the service provider and at least one target mobile client device; and

configuring a server of a new networked computing participant in the ecosystem with a service tier module that performs server-side transaction functions, the service tier module being configured based on the analyzed broken down features of the reference implementation, the configuring occurring over a network through which the participants in the ecosystem perform secure personalized transactions;

configuring the new networked computing participant server further with a personalization tier module that performs server-side personalization of mobile device executable modules that upon execution by the mobile device enables a mobile device participant to perform secure personalized transactions with the newly configured server, the personalization tier being configured based on the analyzed broken down features of the reference implementation and occurring over the network through which the participants in the ecosystem perform secure personalized transactions, and

configuring, over the network through which the participants in the ecosystem perform secure personalized transactions, the new networked computing participant server yet further with an enabling tier module, the enabling tier module being configured based on the analyzed broken down features of the reference implementation, the configured enabling tier providing device independence to the configured service tier module and the configured personalization tier module via at least one Application Programming Interface.

2. The method of claim 1, wherein the reference implementation is accessed by a server in a software development environment preparing each of the personalization, service, and enablement tiers.

3. The method of claim 1, wherein the reference implementation comprises an application selected from the list of reference applications consisting of finance, retail, health, and government.

4. The method of claim 1, wherein enablement tier set of operational features for the client device are selected from a client enablement feature list consisting of:

user interface interpretation engine, business execution environment, widget lifecycle management, wallet lifecycle management, and over-the-air (OTA) transaction patterns.

5. The method of claim 1, wherein enablement tier set of operational features for a server are selected from a server enablement feature list consisting of:

wallet management, stateful transaction engine, object lifecycle management, channel specific communication, multi-domain security policy and risk management, and over-the-air provisioning.

6. The method of claim 1, wherein service tier set of operational features for a client are selected from a client enablement feature list consisting of client side workflows, transaction service-specific templates, wallet instruments that facilitate mapping to real-world instruments, transaction-specific data, and authentication scheme trust models.

7. The method of claim 1, wherein the service tier set of operational features for a client are selected from a library of common ecosystem services that are used to implement a plurality of business use cases.

8. The method of claim 1, wherein service tier set of operational features for a server are selected from a library of business-specific components and associated service templates comprising wallet services, wallet lifecycle management services, and payment token management services.

9. The method of claim 1, wherein configuring a service tier for a server comprises configuring a plurality of service tier units that correspond with the specific application, comprising configuring a client-side workflow that supports various transaction services of a use case unit, configuring an electronic instrument or token unit, and a trust model unit.

10. The method of claim 1, wherein configuring a personalization tier for a client comprises configuring at least one of a wallet and a widget.

11. The method of claim 1, wherein personalization tier set of operational features for a client are selected from the client personalization feature list consisting of wallet services, privileged APIs, personal identification number size, exit confirmation, and handset-specific features.

12. The method of claim 1, wherein personalization tier set of operational features for a server are selected from the server personalization feature list consisting of wallet communication, widget content formatting, wallet application access to services, customization of parameters exposed to the user, and interfacing to third party services.

13. A method comprising:

taking a reference implementation of a specific application operating in a multi-domain computing ecosystem;

using a server to apply a set of rules that govern use of services by participants of the ecosystem to;

break down the reference implementation into components selected from the list consisting of;

service requirements, customer requirements, end-user requirements, regulatory mandates, regulatory guidelines, security mandates, security guidelines, security requirements, trust models, economic models, business logic, business workflow, commonality with other services, operational factors, design factors, technology factors, target devices, platforms, projected technology evolution, and operating constraints, wherein automatically breaking down the reference implementation is based, in least in part, on one or more of analytics and heuristics and is performed using an expert engine the operation of which is based, at least in part, on artificial intelligence; and

determine with a server participants for the reference implementation selected from the list consisting of;

end users, network providers, merchants, service providers, transaction instrument acquirers, transaction instrument issuers, widget providers, wallet providers, and trusted service managers; and

configuring a server of a new networked computing participant in the ecosystem with a service tier module that performs server-side transaction functions, the service tier module being configured based on the broken down components of the reference implementation, the configuring occurring over a network through which the participants in the ecosystem perform secure personalized transactions;

configuring the new networked computing participant server further with a personalization tier module that performs server-side personalization of mobile device executable modules that upon execution by the mobile device enables a mobile device participant to perform secure personalized transactions with the newly configured server, the personalization tier being configured based on the broken down components of the reference implementation and occurring over the network through which the participants in the ecosystem perform secure personalized transactions, and

configuring, over the network through which the participants in the ecosystem perform secure personalized transactions, the new networked computing participant server yet further with an enabling tier module, the enabling tier module being configured based on the broken down components of the reference implementation, the configured enabling tier providing device independence to the configured service tier module and the configured personalization tier module via at least one Application Programming Interface.

14. The method of claim 13, wherein the reference implementation is accessed by a server in a software development environment preparing each of the personalization, service, and enablement tiers.

15. The method of claim 13, wherein the reference implementation comprises an application selected from the list of reference applications consisting of finance, retail, health, and government.

16. The method of claim 13, wherein the set of rules further govern at least two participant behaviors selected from the list consisting of:

accessing services, removal, cross-participant cooperation, acquiring customers, supporting customers, capturing user and transaction data, use of captured data, and monetizing captured data.