JP2002538529A - Card, device, product and product management system - Google Patents

Abstract

(57) [Summary] The present invention relates to a management system for cards, devices and merchandise, the system including a card management means, wherein the card manager's participant has a card-related product. , And can perform the role of card management independently without managing the device, and includes device management means. It is intended to perform the role of device management alone without managing related products and without managing cards, and also includes a product management means, which is a participant who is a product owner. Can perform the role of merchandise management alone without managing the card and without managing the device, where all three roles are performed by separate entities. Is shall.

Description

DETAILED DESCRIPTION OF THE INVENTION

The present invention relates to products associated with cards and devices (eg, payments, royalties,
A system for managing identity, access, insurance, information and transportation products.

[0002] By "card" we broadly mean any instrument that can be used to facilitate commodity transactions (typically with a card-receiving device). This includes magnetic stripe cards, smart cards, "virtual" cards ("wallets"), memory cards, microprocessor cards, contactless cards, optical cards, laser cards, embossed cards, tickets, boarding passes, coupons, and Printed cards. Also included are any devices that may not be cards but can provide similar functions.

[0003] By "apparatus" we broadly mean any instrument that can be used to facilitate a commodity transaction (typically with a card). This includes ATMs,
EFTPOS terminal, draft capture terminal, card receiver, contactless card reader, optical reader, laser reader, ticket reader, boarding pass reader, coupon reader, stamper, and (
For example, a "virtual" device (for reading a "wallet").

[0004] Appliances, such as cards and / or devices, are used everywhere to facilitate commodity transactions. It should be noted that "goods" refers to the application where the applicants place cards and / or devices associated with the goods to facilitate. There are a large number of such products and more candidates. These include (but are not limited to) the following:

[0005] 1. Settlement products-e.g., credits, fees, debt, prepaid (stored value)
, Purchasing, payphone, calling, and billing goods. 2. Loyalty products-For example, airline frequent fliers, product coupons, retail discounts, and customer frequency products. 3. Identifying product-for example, a product with a license, ID, passport, and electronic signature. 4. Access products-for example, buildings, computers, mobile phones, devices, and security access products. 5. Insurance products-for example, health, automobile, and regular insurance products. 6. Information products-For example, products for medical, health, personal, computer, automotive services, and portable information files. 7. Transportation Ticketing Products-For example, airline and boarding pass, rapid transit ticketing, parking lots, parking meters, and toll road goods. These products are often card-based, but not the only one.

[0006] The management of card and / or device related goods and associated message data is complex. Each product often requires the involvement of many different participants. For credit card products, for example, the participants involved will likely include the following: Card issuer. This may be an entity such as a bank that issues and / or subsequently manages cards to facilitate credit products to cardholders. The card issuer provides certain functions to third parties (e.g., card manufacturing,
Note that it may be outsourced (to the secretariat that manufactures the card according to the specifications provided by the card issuer). 2. Card holder. This is usually the person holding the card. Note that the cardholder may be an inanimate object, such as a car, or a company that assigns cards to status or function. 3. Transaction Acquirer. This may be an entity, such as a bank, which normally (but not exclusively) installs and / or subsequently manages a card accepting device at a card acceptor to facilitate credit transaction. The merchant contractor is responsible for managing transactions initiated from these devices (eg, routing of merchandise transactions received from and transmitted to the devices, processing devices that facilitate approval and / or processing of the merchandise transactions). Responsible for the routing of commodity trades). The merchant contractor may, in some cases, be the same entity as the card issuer (eg, if the same bank issuing the card acquires the merchandise transaction). Merchant contractors may provide certain features to third parties (
It should be noted that, for example, the switching of merchandise transactions may be outsourced (to a secretariat that switches transactions according to specifications provided by the merchant contractor). 4. Card recipient. This is usually the participant who receives the card and presents the merchandise transaction to the merchant contractor via the device. The card recipient may be a retailer for a credit card.

In addition to the above, especially in the case of credit cards, “scheme operator” participants may also be involved. The merchandise transaction may be routed via the scheme operator from the device or merchant contractor to the card issuer for approval and / or processing of the merchandise transaction. Examples of scheme operators include VISA®
And MASTERCARD®.

The merchant contractor may need to have the card issuer authorize the merchandise transaction before the merchandise transaction is approved. Authorization of transactions can be performed online directly from the card issuer, by the scheme operator (if a scheme is involved) or by a third party (
Can be attempted via "Replacement").

The merchant contractor clears the merchandise transaction, pays the card issuer, and
You will need to provide merchandise transactions to card issuers so they can process them. For credit card transactions, this can be done in a number of ways. If the merchant contractor and the card issuer are the same participant, it may be settled and provided for direct processing by the card issuer ("on-us product transaction").
If the merchant contractor and the card issuer are different participants, it may be settled and provided for processing via an exchange agreement or via a scheme operator (if a scheme is involved) exchange agreement ( "Off us".

In a credit card system, the card recipient pays a fee to the merchant contractor, and then the merchant contractor often pays the card issuer (and, if appropriate, the scheme operator or third party). pay. In some cases, the cardholder will also pay the card issuer and / or card recipient. Alternatively, the flow of fees between the various participants may be reversed in some cases.

[0011] Products of a type other than a credit card may include the variants described above.
They will be substantially similar. In the case of a loyalty program, the secretariat may be involved, for example, for calculating loyalty points.

Managing the relationships between such products and the participants involved is complex.
Any management system (s) must be able to perform a number of processes and manage information that allows for the management of goods and relationships. For example,
The management system (s) must be able to: 1. Make decisions and execute processing based on the volume of goods traded; 2. Route merchandise transactions to and from devices and other participants; 3. Obtain and maintain information about cardholders, cardholders, and other participants; Support cryptographic processing (messages can be encrypted).

[0013] The execution of any product may involve negotiating business negotiations with various entities involved in determining the product that will manipulate the parameters and data that may be needed.
The management system (s) will then be designed to operate the goods (including the equipment and the processing system for processing the required goods transactions and other data). Such dedicated systems are not readily amenable to modification or adaptation to facilitate operation of additional or other goods.

For example, product schemes and product packages can be combined with products of one package, for example, in regions where VISA® or MASTERCARD® credit products issued by one bank are limited. (For example, Qantas / Telstra / Vis in Australia)
a Scheme, or American Express / A in North America
American Airlines / Hilton Hotels scheme),
May overlap.

Therefore, current card and / or device merchandise management systems suffer from a number of problems. First, as discussed above, they are not easily flexible to support significant changes in goods.

Second, if a card or device is lost or damaged and needs to be replaced,
Obtaining all the information needed to reissue a card or reinstall a device can be a complex problem. This is especially the case when the card and / or device may be associated with more than one item (eg, the same card and / or
Or credit card products and loyalty scheme products supported by the device). In order to reissue a card and / or reinstall a device, information may have to be obtained from a number of different entities.

Currently available management systems limit the extent to which cards associated with different commodities (multi-commodity cards) can be executed. Similarly, currently available management systems also limit the extent to which devices supporting different products can be installed (multi-product devices). The more merchandise associated with the card and / or device, the more negotiating negotiations between different participants will be required, and the required management system (s) will be more complex. One of the main advantages of a well-advertised smart card is its ability to support many different products on a single card. Thus, cardholders may only need to carry one or two cards that support all the products they may need. Current management systems are adapted for the implementation of multi-item cards and multi-item devices.

Current management systems often result in product operation errors and delays in completing transactions (especially when the product is one of a multi-product system). Current multi-commodity systems are generally created by adding additional products to already existing card / device-based products. The management system has been modified or added to address additional merchandise. For example, if the additional product includes a loyalty scheme, current transaction information from the first product (eg, a credit card product) will be subjected to further processing to establish data associated with the loyalty product. The first participant in the system is a credit card product manager (eg, a merchant contractor and a credit card product card issuer).
It is. To enable the loyalty product, the first participant provides further processing. For example, the merchant contractor and the card issuer may be banks. Banks are responsible for processing transactions received from devices associated with credit card products. As with transactions related to credit card products, in a separate process (usually done at one time), the bank must determine which of the credit card product transactions is associated with a cardholder belonging to the loyalty scheme. No. The data from those transactions is then used to calculate loyalty points. Loyalty points are often calculated by another office that receives relevant transaction data from the bank. The loyalty points may then be passed to a loyalty product manager. The transaction data processed by the merchant contractor will include the same data whether the transaction is associated with a loyalty scheme. The merchant contractor (or other entity that processes the transaction) first matches the transaction data with the loyalty scheme (this identifies the cardholder to whom the transaction relates and allows the cardholder May be by deciding whether or not to be a member), and then pass only the relevant transactions to the loyalty product manager (or secretariat). Thus, in current systems, a transaction must first pass through a merchant contractor for first processing before it is passed on for additional processing that allows execution of the loyalty product.
This complicates the process.

This system can introduce errors and delays. For example, it may take weeks or months for loyalty points to be refunded to the cardholder account. In some cases, no loyalty points may be allocated.

In addition, redemption of loyalty points is performed as a completely separate process, which is also slow and requires effort by the cardholder.

In such a system, there is no substantial control of the royalties by the royalties manager. In addition, there are no goods on the card or device. The card and device system is configured to support a first device (eg, a credit card product) and the operation of the additional product is performed “behind the scenes”. There is no information on transactions for loyalty product managers. Another "batch process" must be provided by the merchant contractor.

The current “card processing environment” may be a single role environment (if all merchandise transactions are “in-scope”) or a dual role environment (at least some merchandise transactions may be “
Out of range "). In the case of a single role environment, the card issuer is also a merchant contractor. In a dual role environment, the card issuer and merchant contractor may be separate. It should be noted that there may be multiple participants performing a particular role (i.e., multiple card issuers and multiple merchant contractors in a dual role environment).

If the additional merchandise involves being managed by another merchant participant, as described above, the merchandise manager is an indirect participant. Indirect participants rely on participants in a single role or dual role environment to provide them with the information they need to manage products. They do not directly participate in the "card processing environment". The raw data provided in the transaction cannot be used by further indirect participants. Further processing must be provided by another processing.

Applicants have an additional role involved in the card processing environment to facilitate the management of card device based merchandise, especially if multiple merchandise is to be supported by the card and / or device. Confirmed the possibility of. Applicants have determined that this third
Has been named "Product Owner". A merchandise owner is an entity that can be considered to "own" the merchandise associated with the card and / or device. The merchandise owner may be responsible for managing the merchandise in isolating what is needed to manage other cards and / or devices (ie, they are not responsible for issuing or managing cards) And may not be responsible for the installation or management of the equipment). Applicants have renamed the previous card issuer role to "card manager" because some of the card issuer's aforementioned functions may be transferred to the merchant owner. Similarly, some of the aforementioned features of merchant contractors are:
Applicants may change the role of the former merchant contractor to "
Device Administrator ".

Note that the merchandise may be implemented as a merchandise application distributed on a card, on a device, or on both a card and a device. In particular, smart cards facilitate the supply of merchandise applications on the card. However, while the management system of the present invention is particularly suitable for a smart card environment, the merchandise (which may or may not be on a card, on a device, or on a card or device) May also be performed to manage the data.

The present invention provides a management system for a card, a device, and a product,
A card management means, which means that a card manager participant can perform the role of card management alone without managing the goods associated with the card and without managing the device; Including device management means, which means that a participant who is a device manager can perform the role of device management independently without managing products related to the card and without managing the card. Means for managing goods, which means that the participant who is the goods owner can perform the role of goods management alone without managing the card and without managing the device, A management system in which all roles can be performed by separate entities.

The terms “card”, “apparatus”, and “goods” have the definitions as described above and are detailed as follows: “card” includes a card holder and a card administrator. Any means are provided that allow the relationship to be presented. In the simplest terms, it need only include an identification number or account number. It is a guarantee that the cardholder is able to transact goods. It may include a substitute currency or electronic wallet available from the cardholder's PC over a computer network such as the Internet

Similarly, a “device” is anything that can present a relationship between a device manager (merchant contractor) and a card recipient (merchant). It may be, for example, a "virtual" device accessible via a web page on the Internet.

The addition of the merchandise owner role to a single or dual environment preferably creates a “tripartite environment” where cards and / or There may be three roles required to facilitate the management of equipment related products: Card management performed by the card administrator. 2. Device management performed by the device administrator. 3. Product management performed by the product owner.

It should be noted that in some cases, all these roles may be performed by the same participant (ie, operating each of the device management means, the merchandise management means, and the card management means).

Each of the merchandise management means, the card management means and the device management means preferably includes a software module for controlling processing means for facilitating the roles of the merchandise owner, the card manager and the device manager.

The system preferably further comprises message management means arranged to manage the routing of message data between the card, the device and the card / device / merchandise management system. In a preferred embodiment, the message management means comprises a software module capable of controlling the processing means for controlling the routing of the message data. Note that message data means any data needed to be routed through the system, including transaction data. Preferably, each participant of the system is provided with a message management module. For example, if the card manager, merchandise owner and device manager are separate entities, each of these entities controls the routing of message data within the system, ie between the management means and the card / device. Would have message management means for.

Preferably, the device management means includes a product owner identification data for identifying a participant who is a product owner responsible for managing a product related to a device managed by a participant who is a device manager. And storage means for storing card recipient identification data for identifying a card recipient using a device managed by a participant who is a device manager.

Preferably, the product management means is arranged to store card manager identification data for verifying the identity of a card manager managing a card supporting a product managed by a participant who is a product owner. Storage means.

The merchandise management means also includes cardholder identification data for identifying a cardholder who owns a card having a merchandise managed by a participant who is a merchandise owner;
Card recipient identification data for identifying a card recipient having a device that supports a product managed by a participant who is a product owner may be stored.

[0036] Preferably, the card management means includes a merchandise owner identity for identifying a participant who is a merchandise owner responsible for managing merchandise associated with the card managed by the card manager participant. It is arranged to store the confirmation data. The card management means may also store cardholder identification data identifying the cardholder who owns the card managed by the cardman participant.

Preferably, each of the management means also stores a link to the management means of the other participant.

In each management means, the database can store necessary data.

In each case, the identity data need not be the actual identity of the entity. For example, the product owner need not necessarily have the name of the cardholder holding the product of the product owner. Even without knowing the actual name of the cardholder, having an ID number may be sufficient. It may only be necessary for the card administrator to know the actual identity of the cardholder. In many cases, cardholders will not want to provide their identity to more entities than necessary. The system allows merchandise to be offered to a cardholder without the cardholder having to provide his identity to the merchandise owner.

Typically, it will be necessary for the card administrator to have the actual identity of the cardholder, and for the device administrator to have the actual identity of the card recipient. In addition, the actual identity need not necessarily be provided to any other participants.

Each merchandise owner must have a relationship with the cardholder. The relationship with the cardholder need not be direct. It may be via a card administrator. What the merchandise owner needs in relation to the cardholder is merchandise data in an accurate format that allows for merchandise management. This can be any data that the merchandise owner needs from the cardholder as well as any data that the merchandiseholder provides to the cardholder. This includes merchandise transactions, cardholder names and addresses, applying cards to merchandise, unique identifiers for cards and cardholders (
(Eg, card number), or any other information.

All merchandise owners must have a relationship with the card recipient. The relationship with the card recipient need not be direct. It may be via a device manager. What the merchandise owner needs in relation to the card recipient is accurate form merchandise data that allows the merchandise to be managed. This can be any data that the merchandise owner needs from the card recipient as well as any data that the merchandise holder provides to the card recipient. It can be a merchandise transaction, the name and address of the card recipient, the application of the device to the item, the unique identifier of the device and the card recipient (eg, device number), or any other information.

The relationship between the card recipient and the cardholder can be performed dynamically. That is, this relationship may only occur if the card recipient and the cardholder become to operate the product (eg, the product may be loaded by the card recipient and the cardholder at any time).

In order to manage the relationship between card holders (the merchandise owner is referred to as “merchandise holder”), the merchandise owner usually requests data such as the card holder's identity. This identity does not need to be an actual identity and may simply be an ID number. In some cases, even identity information may not be needed, i.e., it may be sufficient for the merchandise holder to receive transaction data indicating that a cardholder is present. Also, the relationship with the cardholder may be indirect, and any information about the cardholder may be provided by another party in the system (eg, a card administrator).

In order to manage the relationship of the card recipient (the merchandise owner will call the “merchandise recipient”), the merchandise owner typically requests data such as the card recipient's identity. This identity does not need to be an actual identity and may simply be an ID number. In some cases, even identity information may not be required, i.e., it is sufficient to simply receive transaction information from the cardholder so that the merchandise owner is aware that the cardholder is present. Maybe. Also, the relationship with the card recipient may be indirect, and any information about the card recipient may be provided by other parties in the system (eg, a device administrator).

Separating merchandise management from other aspects of card management offers many advantages. Any card and / or device merchandise may be managed separately from all other aspects of the card-related environment and / or device-related environment. Thus, the role of the merchandise owner is simplified (management of merchandise only), so that the merchandise owner has to be involved, for example, in the supply and management of the equipment and cards necessary to support these goods. Disappears. In addition, this reduces the effort on some of the card managers and device managers who support the merchandise owner's merchandise. For example, a restaurant chain has a loyalty scheme.
), Where they become product owners of the loyalty scheme. These merchandise management systems only need to be able to manage the information needed to manage the loyalty scheme, and need a broader aspect of card and / or equipment management that is not related to these loyalty schemes. Not. These other aspects of card management and device management will be performed by card managers and device managers who have agreed to support the products of the restaurant chain.

The aspect of the card-related environment related to the card manager is preferably managed by the card management means. Preferably, the card manager management system (s) uniquely identifies each card managed by the system, maintains data associated with the card, and provides such data to the merchant owner. And share it with the device administrator.

The device management means preferably manages aspects of the device-related environment related to the device manager. Preferably, the device manager management system (s)
It should be possible to uniquely identify each device managed by the system, maintain data associated with the device, and share such data with merchandise owners and card administrators.

Therefore, according to the management system (s) of the present invention, the applicant is involved in any one of the three card environments (product management, card management and device management) devised by the applicant. Entities wishing to do so should have appropriate management of the systems involved in managing the aspects of the environment that these systems are responsible for, along with message management means that allow communication between management systems of different entities in a three-way environment. Only part is needed.

Therefore, for example, the product owner manages the product independently from all other tasks. The merchandise aspect may be updated via the merchandise management means of the three-way environment (eg, a new version of the merchandise application on the card), and thus the entity may use the card management means and / or device management means. Eliminates the need to have more means.

This serves to illustrate an important aspect of the present invention. Prior art systems discussed in the introduction (here, a third party operates a product similar to a second product that receives data from a system designed to operate the first product, such as a loyalty scheme) According to the owner of the loyalty product, he is not actually a participant in this management system. The prior art environment is a two-role or one-role environment, where a third party relies on the first product party for any information, transaction information, and arbitrarily modifies the product. If the item is present on the card or device, the first participant must modify the item application.

According to the invention, the merchandise owner can preferably influence the control of the merchandise. For example, if the merchandise application resides on either the device or the card (e.g., a smart card), or both, the merchandise owner will probably be able to access this system without any other administrative participant in the system. It may be possible to download the updated application via the management system. The transaction data created in relation to the product may be routed to the product owner via the other participant's message management means without processing by the other participant's management module. Therefore, the management system of the present invention preferably allows the product holder to easily contact the product directly (for example, to put information into the product or to receive information from the product). This is not feasible in the prior art and is by a third party operator who is not directly involved in the two role or one role environment of the prior art.

Further, according to the management system according to the present invention, exchange of cards and devices due to loss, theft, damage, breakage, “re-issuance”, and the like is further facilitated. Cards or devices include many products known as card manager and device manager management system (s) that also maintain specific data other than the product.
The management system (s) of the card administrator and the device administrator may further maintain or obtain specific data for the product provided by each product owner. A link to each merchandise owner's management system may be maintained to allow for this. In this way, the card manager or device manager may obtain data from the product owner's management system (s), or the card or device manager may store the data along with the data maintained in the product owner's own management system. Could be rebuilt and replaced.

The management system according to the invention makes it easier to supply and manage a plurality of merchandise cards and devices. If the merchandise owner wants to place the merchandise on the card or device, they will obtain a merchandise management system and a message management package, and establish a relationship with the card manager and device manager for this merchandise All that is needed. The card manager can then help the merchandise owner place the goods on their cards, and the device manager can help the merchandise holder place the goods on these devices. . When the product becomes operable, the device manager and the card manager can configure these management systems and manage transactions facilitated by the product. For example, a device manager's management system routes merchandise transactions received from these devices directly to the merchandise owner's management system, and the card manager's management system manages the address details of the cardholder's address details. Any changes may be notified to the merchant management system.

The security and privacy aspects of the system of the present invention are also particularly advantageous. Cardholders are often reluctant to present too many personal items to a particular entity. According to the present invention, the product management system requires only enough information to manage the product. The personal identity of the cardholder need not be required. Such an aspect may be left to the card administrator. Thus, if the card custodian is a standard bank, for example, the merchandise owner will not need this information per se, as he can "trust" the bank assuring the integrity of the cardholder . This limits the number of entities that need detailed personal information, but still allows cardholders to gain access to multiple products and thus protects personal privacy This is advantageous for the card holder. If the merchandise holder has to contact the cardholder, this can link the cardholder's unique identifier maintained by the merchandiseholder with the merchandise owner's personal information and then contact the latter directly This can be accomplished via a card administrator.

The system of the present invention also facilitates customer service. If the product does not work satisfactorily, the cardholder only has to make one contact (usually with the card administrator). The cardholder appeals the claim to a card manager who can deal with the claim itself, or who can communicate the claim directly to the merchandise owner (or other related party) via the management system. Cardholders,
There is no need to make multiple contacts for each of the plurality of items.

The management system of the present invention preferably further comprises interface means for connecting the external system to the management system by an interface. This interface means is preferably provided in the form of a software module, which applicant calls a "business module", which operates the processing means which interfaces with the desired external system. For example, merchandise owners may already own or want to design their own external system for processing aspects of a merchandise. Thus, the business module may provide a link between the external system and the management system, and convert the data received by the management system into a form that can be used by the product owner's external system. Also, the modules may be interfaced with legacy systems so that the management system of the present invention can be compatible with existing systems.

The present invention further provides a product management system including a product management unit that allows a participant who is a product owner to execute only the role of product management without managing a card and without managing a device. However, the system is arranged so that it is easy for the participant who is the merchandise owner to directly influence the control of the merchandise associated with the card or device.

“Easy” means that the system provides a mechanism by which data can be transmitted directly between the merchandise associated with the card or device and the merchandise holder. The merchandise may reside on the merchandise card or device in that the software is installed on a card or device associated with the merchandise. A card or device can be interpreted as a "real estate" term, for example, a smart card is a number of storage locati that a card administrator can "rent" to a merchandise owner.
on). Card owners provide "keys" so that merchant owners can access the guaranteed location on the card, and merchant owners actually provide their own keys, Interference with the product on the card can be prevented. This is because in the current multiple product arrangements (where the card or device manager requires a first action and the product owner (eg, loyalty point owner) can manage the product). Impossible.

The invention further provides a card management means, wherein the card management participant manages the card management without managing the goods associated with the card and without managing the device. A card management system that allows a role to be performed independently.

The present invention further provides a device management means, which means that a participant who is a device manager manages a device without managing a product associated with the card and without managing the card. A device management system that enables a role to be performed independently.

The present invention further provides a card, device and merchandise management system, which includes a plurality of service processing means, wherein each service processing means is configured such that a participant in the system can use a card. , At least one of device and product management, including message management means,
Provided to each participant in the system, and wherein the means is arranged to operate as a communication interface for routing message data between each service processing means and between the card and the device; The means is the system as described above, arranged to enable the network of service processing means and a plurality of participants to be interfaced and to perform management of cards, devices and goods.

The service processing means preferably includes the card management means, the device management means, and the product management means as described above.

The present invention further provides a management system for cards, devices, and merchandise, including a network, the network having a plurality of nodes, each of which includes a service processing unit. Means for enabling a system participant to perform at least one of card, device and merchandise management;
And each node has message management means, which are arranged to operate as a communication interface for routing message data between the service processing means of each node and between the card and the device. Is the system.

The present invention further provides a method of managing cards, devices, and merchandise, the method including a step of defining a three-party environment for card management, wherein the three-way management of the card management is performed. Is the card administrator responsible for managing the operation of specific non-commodity cards, and the device administrator responsible for managing the device, receiving cards and performing merchandise transactions. , And a participant who is a product manager responsible for managing the product-related scope of the card environment, and is a device manager, a card management participant, and a participant who is a product manager. May be separate entities.

The present invention further provides a method of managing merchandise, the method comprising: managing a merchandise that is solely responsible for merchandise management without managing a card or managing a device. A participant who is a merchandise manager and a step of facilitating a participant who is a merchandise manager to directly influence control of merchandise associated with the card or the device.

The present invention further provides a method for managing a card, the method performing card management independently without managing a product associated with the card and without managing a device. Has the role of limiting the participants who are card managers.

The present invention further provides a method of managing a device, the method performing device management independently without managing a product associated with the card and without managing the card. Has a step of limiting the participant who is a device manager whose role is to be performed.

The present invention further provides a comprehensive system for managing cards, devices, and merchandise, the system including a card management module, a device management module, and a merchandise management module; These are used separately and to allow different entities to perform card management, equipment management and merchandise management alone and to facilitate card, equipment and merchandise management. Networked together to enable networking with other similar systems.

Preferably, any entity wishing to be involved obtains the necessary modules (depending on whether they are a card administrator, a device administrator, or a merchandise administrator) and their requirements Configure the module according to. Such a comprehensive system, specially designed to facilitate the management of cards, devices and goods, is a new concept. Many entities can become involved in networked systems.

The system of this aspect of the invention may include any or all of the features of the above aspects.

The present invention provides a card, apparatus, and product comprising a computer computing system having a storage location for receiving a plurality of product applications, and security means for selectively accessing storage locations of a plurality of product owners. An arrangement is further provided whereby the merchandise owner may access separately or manage the merchandise owner's merchandise stored in its storage location.

For example, when the card is a smart card, the storage location for receiving the product application may be mounted on the card itself, may be mounted on the device, or may be shared between the card and the device. May be. The storage location can be interpreted in the "real estate" term above, and the card or equipment manager can "rent" the real estate to the merchandise owner so that the merchant owner can use the arrangement. Thus, the merchandise of the merchandise owner can be released. The security means may comprise a key, which is preferably in the form of any token that allows the merchant to access the storage location (the token may be any identifier, for example a PIN) ). Security measures may also be provided to prevent a card or device administrator from accessing a particular merchant storage location once the storage location is rented to the merchandise owner.

It should be noted that the storage location need not be mounted on a card or device, and may be located anywhere in the computer system or located within the computer system.

The arrangement of the card, device and merchandise of the present invention is preferably provided in a card, device and merchandise management system according to the above aspect of the present invention. Indeed, the use of such a system facilitates the management of the merchandise owner's merchandise application stored in this storage location by the merchant owner.

The features and advantages of the present invention will become apparent from the following description of embodiments thereof, which is provided by way of example only, with reference to the accompanying drawings.

FIG. 1 shows the current environment for card merchandise management. The environment includes card issuer 1. The card issuer is responsible for issuing and managing the card 2 to the cardholder 3 (possibly by another card manufacturing office). The card issuer may be, for example, a bank or other financial institution that wants to issue a card with a credit card product to a cardholder. The card issuer needs details such as the cardholder's identity, address, and credit grade.

The environment also includes a merchant contractor 4. The merchant contractor is responsible (perhaps by a third party merchant) for deploying and managing the device 5 to the card acceptor 6. The merchant contractor may be, for example, a bank or other organization that wishes to deploy the device to a card recipient that supports credit card products. The merchant contractor requires the details of the card recipient's identity, address, and bank deposit items.

Traditionally, dedicated computer systems have been used to manage card merchandise in the current environment. These systems suffer from the issues discussed in the introduction.

Referring to FIG. 2, a modification environment facilitated by a card management system in a preferred embodiment of the present invention is shown. In addition to the card administrator 1 (the renamed card issuer) and the device administrator 4 (the renamed merchant contractor), there is a further entity, the merchandise owner 7. The merchandise owner 7 is responsible for managing aspects of the environment for the particular merchandise supported by the card 2 and the device 5.
The merchandise owner is solely responsible for the merchandise. The merchant owner is not responsible for other aspects of the card and device environment that are not particularly relevant merchandise, such as card issuance and management, device deployment and management. The merchandise owner only needs information on the card, device, cardholder and card recipient, and this information is needed to operate the merchandise. The product owner 7 has a relationship with a card receiver and a card holder that support the product.

The functions of merchandise owner, card administrator, and device administrator may be performed by one or more entities, which may perform one of many functions. In this way, many scenarios are supported. For example, one entity may perform only the function of the product owner, while another entity may
The third entity may perform all three functions while the last entity may perform only the device management functions, while the third entity may perform the functions of the card manager and the merchandise owner.

The configuration of the management system according to an embodiment of the present invention is schematically illustrated in FIG. The management system includes a message management module 10, a card management module 11, a device management module 12, and a product management module 13.

The message management module is arranged to receive the message data (for example, from the device) and to forward the message data to the appropriate service management module 11, 12, 13. Similarly, message data can be received from the management modules 11, 12, 13 and this data can be transferred out of the system or to another management module.

Each of the management system modules has a function of enabling card management (card management module 11) and a function of enabling device management (device management module 1).
2) and a function (product management module 13) that enables product management.

The system also includes one or more business modules 14. These modules contain the functions required to fulfill the specific business requirements of one or more entities involved in the card environment utilizing the management system according to the invention. Business modules provide extensions and / or constraints to the management system to support specific business requirements. For example, supporting the technical means of the MULTOS card platform, supporting interfaces to legacy database systems, supporting transaction processing specific to a particular product, or managing transactions received from a particular device May be.

Card 11, device 12, and product management 13 module (service module)
Each include relevant databases and processing means to provide: a merchandise management module 1. It provides merchandise for cardholders (cardholder merchandise for merchandise owners) and card receivers (forms of cardholder merchandise for merchandise receivers). 2. Restrict product establishment within the card manager / device manager. 3. Process merchandise transactions. 4. Managing relationships with suppliers, cardholders / recipients and card / device managers. 5. Supports management of product life (including product data and applications) and management of supported device / card relationships per product (including relationships with card managers and device managers). 6. Manage card products and related information. 7. Product description. Identify card and device applications, compatible card and device platforms, card / device required memory, parameters and data requirements. 8. Product relationships, for example, relationships between different products. 9. Commodity parameters / composition. 10. Initial product certificate, ciphertext. 11. Card administrator and device administrator information. A plurality of card managers and device managers may support the product. 12. Link to or data from the card management module for cardholders using the product. 13. Device management link. A link to or data from the device management module for the card recipient supporting the product. 14． Transaction data may need to be accurately mimicked for reconstruction. 15. Card / device application. 16. Application regulations. Dynamic download of applications to the card.

Device Management Module Establish and manage the equipment used by the card recipient. 2. Establish equipment at the card recipient's location. 3. Deployment of products from product owners. 4. Manage relationships with suppliers, cardholders and merchandise owners. 5. Order equipment from a vendor. 6. Maintenance and management of equipment inventory and installed equipment, including data and applications on the equipment. 7. Management of supported product relationships (including relationships with product owners) per device.
8. Device specification data. Define device maintenance / management processes-provide details about the capacity of the application, etc. 9. Equipment parameter / configuration data required for the equipment installation rebuild process.
A specific configuration is specified for the device manager of the device data. 10. Initial device warranty, key-ciphertext. 11. Device product applications and links. The product application may be managed by the transaction processor, but at least a link is maintained for the device rebuilding process. 12. Card recipient data, such as business details, full title, demographic information, etc. 13. Card recipient / device related. Multiple devices may be linked to a card recipient. 14． By establishing a cardholder, eg, manual data entry, electronic file import. 15. Card recipient communication. Statement. 16. Application distribution. Tracks are stored, applications are distributed to devices, and card applications are distributed to smart cards. 17． Device utilization provides a device administrator with tools to identify the data contained in the device. 18. Device update reconfiguration updates and reconfigures the device. 19. General equipment / card recipient management. Fees, management, reporting.

Card Management Module Issue and manage cards used by cardholders. 2. Issuing cards to cardholders (including reissue / rebuild). 3. Deployment of products from product owners. 4. Managing relationships with suppliers, cardholders and merchandise owners. 5. Ordering a card from a vendor. 6. Management of card stock and issued cards, including data and applications on the card. 7. Management of supported product relationships per card (including relationships with product owners). 8. Cardholder data. Data related to all cardholders (for example,
The cardholder's name, contact details, identification number, demographic information, market research results and diary) need to be captured and retained by the card management module. 9. Card / cardholder relationships (relationship links required for many relationships between cards and cardholders; multiple cardholders may be linked to the same group (eg, family card)-there is Multiple cards for card holders (company and corporate cards) 10. Card details data, issued card platform, memory capacity, memory type, application capacity 11. Card parameters / configuration data-card production About the / update / rebuild process: how the card memory space is used and how data / applications are downloaded onto the card, and the specific card issuer of the card data, , Products do not contain specific data / applications) 12. Specify the personalized data for the card making / rebuilding process to identify the cardholder data provided on the card, which may be data for multiple cardholders. 13. Initial card warranty / key (ciphertext) 14. Card merchandise application / link-maintain link to merchandise manager to enable card rebuild 15. Establish cardholder, manual data 16. By input, electronic file import 16. Cardholder communication, for example, event date / time / date such as card issuance 17. Card making / issuance identifies the data contained on the card and the card's unique ID 18. Provide tools for card managers to provide: 18. Update / Rebuild Card-Identify Card or The ability to update and rebuild a set of cards-may require the need for normal "arbitration" with the card in an online environment 19. General card management, card / cardholder requirements (reporting) Requests related to the participant (eg, fees to be paid, sustainable fees).

The message management module enables the following functions: message management module 1. Manage the flow of messages and data for and between service modules and business modules. 2. Capture transaction / message formatting, forwarding and records. 3. Transmission and reception of transactions / messages in and between connected management systems and external system devices and cards. 4. Includes data encryption and authentication. 5. Record billable events and support activity-based and general rates. 6. Creation of standard and ad hoc reports. 7. Includes system administration, installation, deployment, access control, monitoring, repair and storage. 8. Includes adherence to generally accepted standards, performance and operating standards, and arrangement of measures. 9. Manages and routes messages to / from interconnected systems, devices and cards. 10. Communication to / from individuals and organizations (eg customer questions,
Letter). 11. Create information that indicates the fee. 12. Perform system administration tasks (eg, installation and uninstallation placement, performance monitoring, logging, user notification, exception detection and analysis, backup and restoration, storage and retrieval). 13. Supports proper access control, physical security and cryptographic processing (eg, authentication, encryption). 14． Record and investigate the current and historical state of the system (eg, for accounting purposes). 15. Convert from transaction format to internal transaction format of service module or external system. 16. Capture transactions and fill them in log sheets for mediation, accounting, etc. 17． Transaction split. Some of the transactions received may be compound transactions (some transactions apply to multiple products or applications) and need to be split into two or more micro-transactions-the transactions are possible In order to ensure the highest possible data privacy, it must be forwarded as early as possible in the transaction chain.

For a particular operator of the management system according to the invention, they depend on their function as entities in the environment, one of the three management modules 11, 12, 13, or You may have everything. FIG.
With reference to, for example, Entity 1 is an organization that wants to provide a particular product and be required to pay. All that is needed for the system is a creation module and a merchandise management module, as well as any business modules needed to support a particular business function. Entity 2 is the card and device manager, while entity 3 is the card manager, device manager and merchandise owner.

[0091] Each of the entity 1, entity 2 and entity 3 management systems may be connected to support various commodities. For example, merchandise owners may establish commercial relationships with Entity 1 and / or Entity 2 as card managers and / or device managers for their particular merchandise.

In operation, the cardholder 1 in need of an available product may retrieve the product from the product owner. The product may be provided as a software application downloaded via the device 5. The cardholder can, in fact, interact directly with the device to solicit the goods and provide any details that may be needed (they are already available from the cardholder's details about the cardholder). If can not be provided). The merchandise can then be recorded on the cardholder's card.

FIG. 5 is an illustration of a configuration example of the use of the management system according to the present invention. Two participants are illustrated. Participant "A" is a bank or other financial institution operating a credit card product. They operate a management system (including a message management module 20, a card management module 21, a device management module 22, and a product management module 23) according to the present invention. Business management module a24
And a business management module b25 are also provided. Participant A not only manages credit card products using product management module 23, but also manages device 26 and card 27 using device management module 22 and card management module 21, respectively.

The participant “B” is an airline that owns the royalty product. They are,
The system according to the present invention includes a message management module 28, a product management module 29, a business management module c30, and a loyalty system application 31. The loyalty system application 31 is an application designed specifically for participant B to process its loyalty system transactions.

The card holder 32 has a card 27 that supports both the credit card product of the participant A and the loyalty product of the participant B.

The card holder 32 purchases goods from the card receiver 33. To pay for the goods, the cardholder uses the credit card product on card 27 via device 26. The message data 34 generated by the device 26 is transferred directly to the participant A of the message management module 20. The message management module 20 forwards the message data to the device management module 22. The device management module determines that the message data relates to transactions relating to those credit card products and the loyalty product of Participant B. The device management module 22 operates to split the transaction data into message data for participant B and message data for participant A's merchandise management module 23. The message data for the product management module 23 is sent to the product management module 23 via the message management means 20. The credit transaction is a “duty” transaction, and the merchandise management module 23 determines that the participant A is also the card administrator 21. Appropriate transaction information may be provided to the card management module 21 via the message management module 20, and the business module a24
May be converted to the appropriate (different) form required by the external credit card processing system 34 and then provided to the external credit card processing system 34. System 34 may be a legacy system that was already in place for participant A prior to installation of the management system of the present invention.

The message data intended for participant B is firstly forwarded by the business management module b25 for appropriate cryptographic conversion. Participant B requests that this cryptographic process be performed for security purposes. After the processing by the business management module b25, the encrypted message data is transferred to the message management module 28 of the participant B via the message management module 20.
The message management module 28 ignores the message data sent to the product management module 29. The product management module 29 calculates, for example, royalty points. In this particular case, participant B has another loyalty product system 31 that needs to be updated with loyalty points. Further message data generated by the merchandise management module 29 and including the loyalty point information is converted to a suitable format for the loyalty point system 31 via the business management module c30 and the loyalty points via the message management module 28. Proceed to system 31.

Another application of the management system of the present invention is in handling complex transactions.

A complex transaction is a single transaction that applies to multiple applications managed by the same or different processing / management systems of the present invention. For example,
Credit merchandise transactions with attached royalties may generate one transaction between the smart card and the device; however, small transactions of credit and royalties may be routed to different systems. . Complex transactions occur each hour, and multiple applications generate complex transactions during the interaction between the smart card and the device.

FIG. 6 illustrates the transaction flow for a complex transaction. The steps involved are described in detail below.

1. During the interaction between smart card 40 and device 41, multiple applications generate complex transactions. 2. Periodically, the device calls the device manager 42 to upload all transactions, which are recorded by the message manager module 43 of the device manager 42. 3. The device management 42 applies the predefined rules to the recorded transactions. Complex transaction rules generate multiple micro-trades defined for multiple management or legacy systems according to the present invention. 4. Device management 42 transfers the micro-transaction to one or more merchandise management modules 44, 45 and / or one or more legacy systems 46 for further processing. 5. Device management may forward notifications to one or more card management systems as needed to notify of changed smart card data or applications.

Other possibilities are the following: Multiple applications that are operated simultaneously may each generate a small transaction, and therefore do not generate a complex transaction. 2. Complex transactions may be broken down into smaller transactions on the device before periodic batch transfers to device management.

[0103] The process of recreating a smart card may be necessary if the cardholder notifies the card issuer that the smart card has been lost or stolen. Recreating smart cards involves blocking lost / stolen cards, storing data from applications and card management systems, and personalizing new smart cards.

Card management may recreate only smart card applications and data for which card management has been explicitly authorized by the cardholder. The cardholder is responsible for recreating personal data. For example, the encryption key may be unambiguous from the cardholder, either by the cardholder or via a request to the merchandise management module, which may require a cardholder key for the application from the CA. It may be obtained only by authorized card management.

FIG. 7 illustrates a transaction flow for recreating a smart card. The steps involved are described in detail below.

The steps of the transaction flow may be described as follows: The cardholder 50 requests the card issuer 51 to recreate the smart card and gives the card issuer 51 the desired permission for the rebuilding process. 2. The card issuer instructs the card management module 52 to block the previous card and schedule the rebuild process, and request a smart card rebuild. 3. The card management 52 creates a new card number and stores the cardholder data,
Card data that has been approved by one or more merchandise management modules 53 and / or one or more legacy systems 54 that incorporates the card application reference and is referenced in the application and possibly the card application reference (the card data is stored in the card management module). Should not exist). 4. The merchandise management module 53 and / or legacy system 54 may review the authorization, request appropriate data from other sources, eg, CA, update the appropriate database with the new card number, and And possibly transfer the card data to the card management module 52. 5. The card management module 52 creates a personalized file using all imported applications and data. The personalization file may be processed in the form of a report by an independent card personalization machine 55, and the card 56 is submitted to the cardholder 50.

Variations: 1. Card management may require a smart card or set of smart cards to be rebuilt, for example, the expiration date is printed on the card surface.

One of the main advantages of the management system according to the present invention is that it allows the dynamic loading and unloading of merchandise applications from smart cards and / or devices after the issuance of a smart card or the installation of a device. It is.

Dynamic application loading is to ensure that new applications may be loaded on the smart card after the card is issued and that they are loaded on the device after they have been installed. Transfer the application to a smart card or device. The application load transaction occurs with a request, which may be issued by the management system module or by the cardholder or cardholder.

FIG. 8 illustrates one possible transaction flow for an application load transaction for a smart card. The steps involved in this variation are described in detail below.

The steps of a transaction flow to facilitate loading of an application onto a smart card may be described as follows: During the interaction between the smart card 60 and the device 61, the device provides the smart card 60 with applications that are not resident on the smart card 60. (A) The smart card 60 may verify that the application may be legally present on the card administrator's card (e.g., between the card administrator and the device administrator for this application). Make sure there is consent).
2. The cardholder agrees to load the application on the smart card 60, and the smart card 60 requests the device 61 to provide the application to the smart card 60 and load it into its memory. 3. The device calls the device management 62 of the management system of the present invention. 4. The device management 62 sends an application request to the product management 63. (A) The smart card 60 and the device 61 should not be able to verify the legality of the application on the smart card 60 and before the application request is submitted to the merchandise management 63, the device management 62 and the card management A match between 64 and 64 may be required. Also, if the application has value associated with the application, device manager 62 may confirm that smart card 60 is not blocked. 5. The product management 63 provides the requested application to the device management 62. 6. The device management 62 provides the requested application to the device 61. 7. Device 61 interrupts the online link to device management 62 and provides the required application to smart card 60. 8. The smart card 60 installs an application in its memory. 9. The smart card 60 may send a notification of successful loading to the device 61 for batch upload to the device manager 62 for distribution to the requesting participant. This notification may be required for mission critical applications, while other merchandise or card management 64 may not require notification. Device management 6
2, the card management 64, the product management 63, and the notification may be transferred to both.

Dynamic application loading for a device may be facilitated in a manner similar to instructions for loading from either the device, the device management module or the merchandise management module.

The device management 62, the merchandise management 63, and the card management 64 may belong to the same entity or different entities.

Other possibilities for loading the application on the variation smart card are: The cardholder requests by phone that the application be loaded on the smart card (eg, the next time the smart card is online for another transaction). Merchandise management schedules loading and requires device management to provide applications to the device on demand (eg, when the smart card is online). 2. Merchandise management mediates consent with card management to provide applications to all smart cards managed by card management. Either card management or merchandise management directs device management to: (a) On demand (e.g., when the smart card is next online) to all devices managed by device management. (B) All devices managed by device management should now have the device installed so that loading of the application may be facilitated offline if the smart card interacts with the device. Deliver applications when you are online. 3. Card management directs device management to load the application into the smart card set in one of the following ways: (a) The next time the smart card is online for transactions; (b) Offline application By pre-loading the application to the device for loading.

Other possibilities for loading the application on the device are the following: For example, to process a transaction using a smart card that possesses an unknown application, the device requires that the application be loaded online. Device management requests an application from one or more product management modules. The application is loaded onto the device in a manner similar to loading a smart card application. Once the application is installed on the device, the transaction using the smart card may proceed. 2. Device management requests the device application from the merchandise management module and transfers the application to the set / all devices for installation during interaction with the next device. 3. Merchandise management requests device management to provide an application to the device during interaction with the next device.

Dynamic application unloading can be performed on the smart card 70n or the device 71.
To ensure that the application is unloaded from the smart card after it has been issued and that the device is unloaded from the device after it has been installed. I do. The application unloading transaction may occur automatically (eg, a single use coupon) or upon request, the request being issued by a module of the management system of the present invention, a cardholder or May be issued by the card recipient.

FIG. 9 shows a transaction flow for an unload transaction. The steps involved are described in detail below.

The steps of the transaction flow for facilitating application unloading from a smart card are as follows. 1. The card management 72 requests the device management 73 to remove the application from the range of smart cards managed by the card management 73, and (a) the next device 71 online for the transaction With one of the cards 70; (b) broadcast the request to the device 71, the next time the device 71 is online for interaction with the device manager 73 and offline smart during the transaction interaction. An unload request is communicated to the card (this mode may be mandatory if the card manager 71 suspends application support or the cardholder misuses the application).

[0119] 2. During the interaction between the smart card 70 and the device 71. (A) The device must then dial in to device management 73 to complete the transaction, and device management 73 requests device 71 as part of the response to device 71 to unload The request is transmitted to the smart card 70. The device 71 suspends communication with the device management 73, completes the transaction, and transmits an unload request to the smart card 70. (B) Transmit the unload request broadcast to the smart card.

[0120] 3. The smart card 70 deletes the application from its memory with optional advice to the device 71 that the application has been deleted. The advice may be uploaded to the device management 73 during the next interaction and may be communicated to the card management 72 and the product 73 management module.

[0121] Dynamic application unloading for a device may be facilitated in a similar manner, with instructions for loading originating from any of the device, device management module, or merchandise management module.

1. Merchandise management may request device management to unload the application from all smart cards and / or all devices. For example, an interrupted application. 2. The smart card may delete the application from its memory after a single use of the application (eg, a single use coupon). 3. After a single use of the application (eg, a single use coupon), the device may request the smart card to delete the application from its memory. 4. Device management may request that the device delete applications from the device's memory that are no longer supported by the device management.

Implementation of the management system according to the present invention may allow a way to operate and make useful goods that are not currently in practical use. Merchandise owners meeting these criteria can submit the merchandise for use with the cards and devices managed by the card and device managers. There is no need for any complicated negotiations to establish the parameters of the relationship between the merchandise owner, the device manager and the card manager. The merchandise owner simply has to arrange his merchandise to meet the criteria and make the merchandise available to the card and equipment managers, and this time the card manager And the device administrator make the product available to the cardholder. Goods that are already fully compliant are offered for use by the system.

It will be apparent to those skilled in the art that many variations and / or modifications can be made to the invention illustrated by the specific embodiments without departing from the spirit and scope of the invention as generally described. Will be recognized by This aspect therefore provides:
It is illustrative in all respects and is not to be considered as limiting.

[Brief description of the drawings]

FIG. 1 is a schematic diagram of a current card-related environment.

FIG. 2 is a schematic diagram of a card-related environment facilitated by the card management system of the present invention.

FIG. 3 is a block diagram of a system configuration of a card management system according to an embodiment of the present invention.

FIG. 4 is a schematic diagram illustrating an example of an all-linked system for managing transactions for a plurality of merchandise cards, the system executing a plurality of card management systems according to an embodiment of the present invention. It has an entity to do.

FIG. 5 illustrates an application of a management system according to an embodiment of the present invention.

FIG. 6 is a schematic diagram illustrating the processing of a complex transaction in a management system according to an embodiment of the present invention.

FIG. 7 is a schematic diagram illustrating a smart card reconfiguration process using a management system according to an embodiment of the present invention.

FIG. 8 is a schematic diagram showing an application downloaded to a smart card using the management system according to the present invention.

FIG. 9 is a schematic diagram illustrating a process of erasing an application from a smart card using a management system according to an embodiment of the present invention.

[Procedural Amendment] Submission of translation of Article 34 Amendment

[Submission date] May 25, 2001 (2001.5.25)

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] Claims

[Correction method] Change

[Contents of correction]

[Claims]

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/60 514 G06F 17/60 514 ZEC ZEC G06K 17/00 G06K 17/00 A (81) Designated country EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, IT, LU, MC, NL, PT, SE), OA (BF, BJ, CF, CG, CI) , CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, KE, LS, MW, SD, SL, SZ, TZ, UG, ZW), EA ( AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AE, AL, AM, AT, AU, AZ, BA, BB, BG, BR, B Y, CA, CH, CN, CR, CU, CZ, DE, DK, DM, EE, ES, FI, GB, GD, GE, GH, GM, HR, HU, ID, IL, IN, IS, JP , KE, KG, KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MA, MD, MG, MK, MN, MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI, SK, SL, TJ, TM, TR, TT, TZ, UA, UG, US, UZ, VN, YU, ZA, ZW (72) Inventor Walters, Michael Charles Alfred Street, New South Wales, Australia, 2040, Alfred Street 28 (72) Inventor Shardy, Rita Australia, New South Wales, 2000, Sydney, George Street 695-699, Les Le 4, Cars etcetera proprietary Limited Incorporated in F term (Reference) 5B058 CA01 CA31 CA33 CA35 KA02 KA04 YA20

Claims (51)

[Claims] 1. A card, device and merchandise management system, comprising card management means, wherein a card manager participant manages the device without managing the merchandise associated with the card. That can perform the role of card management by itself without any means, including device management means, wherein the participant who is the device manager manages the card without managing products related to the card. Device management role alone, and includes a product management means, wherein the participant who is the product owner does not manage the card and manages the device. The system wherein the role of merchandise management can be performed by itself, wherein all three roles can be performed by separate entities. 2. The system further comprises message management means, wherein said means for managing cards,
The system of claim 1, wherein the system is arranged to manage routing of message data between the device and the card, and between the device and the merchandise management system. 3. The message management means is also arranged to operate as a communication interface for routing message data between the card management means, the device management means and the merchandise management means. 2
The described system. 4. The system according to claim 2, wherein the message management means is also arranged to manage the routing of the message data to the external system. 5. The system according to claim 2, wherein each of the card management unit, the device management unit, and the merchandise management unit has an associated message management unit. 6. The participant, who is the merchandise owner, does not require any other participant intervention.
Any of the preceding claims, wherein the merchandise management means is arranged and the system is arranged so as to facilitate direct action on the control of the merchandise associated with the card or device. The system described in Crab. 7. The system of claim 6, wherein controlling the item comprises loading data into the item. 8. The system according to claim 6, wherein the control includes receiving the data from the product by the product management means through the system. 9. The system of claim 8, wherein the data is transaction data. 10. The system according to claim 6, wherein the control includes that the merchandise management means downloads the merchandise application directly to the card or the device. 11. Data related to the product and data provided to the product management means, or data provided from the product management means to the card or the device, can be used to manage the message management means of another entity participating in the system. A system according to any of claims 6 to 10, wherein the system is arranged to be routed through. 12. Card management means arranged to store merchandise owner identification data, the data being used to manage merchandise associated with a card managed by a card manager participant. A system according to any of the preceding claims, wherein the system identifies a participant who is the responsible owner of the goods. 13. A device management means is arranged to store merchandise identification data, wherein the data manages merchandise associated with a device managed by a participant who is a device manager. Is responsible for identifying the participant who is the merchandise owner and is arranged to store card recipient identification data, the data comprising:
The system according to any of the preceding claims, wherein the system confirms that a card recipient is using a device managed by a participant who is a device manager. 14. A merchandise management means is arranged to store card manager identification data, the data comprising a card supporting a merchandise managed by a participant who is a merchandise owner. The system according to any of the preceding claims, wherein the system identifies a person under control. 15. A merchandise management system, comprising merchandise management means, wherein a participant who is a merchandise owner has a sole role of merchandise management without managing a card and without managing a device. In which the system is arranged to facilitate the participant, the merchandise owner, to directly influence the control of the merchandise associated with the card or device. Is,
The system. 16. The system of claim 15, wherein controlling the item comprises loading data into the item. 17. The system of claim 15, wherein the control includes receiving data from the product by the product management means. 18. The system according to claim 17, wherein the data is transaction data. 19. The control of claim 15, 16, or 1, wherein the merchandise management means downloads the merchandise application to a card or device.
A system according to any one of the preceding claims. 20. A merchandise management means arranged to store card manager identification data, wherein the data includes a card supporting a merchandise managed by a participant who is a merchandise owner. 21. The system according to any one of claims 15 to 20, wherein the system confirms the identity of the user. 21. Card management means, which means that a card administrator participant can independently perform the card management role without managing the merchandise associated with the card and without managing the device. Card management system. 22. The card management system is arranged to store merchandise owner identification data, the data managing merchandise associated with a card managed by a participant who is a card manager. 20. The card management system according to claim 19, wherein the card management system is for identifying a participant who is a product owner who is responsible for the product. 23. Device management means, which means that a participant who is a device manager can independently perform the role of device management without managing products associated with the card and without managing the card. Device management system. 24. Apparatus management means arranged to store merchandise owner identification data, the data managing a merchandise associated with the apparatus managed by a participant who is an apparatus manager. Is responsible for identifying the participant who is the merchandise owner and is arranged to store card recipient identification data, the data comprising:
22. The device management system according to claim 21, wherein the device management system is for confirming that the card receiver uses the device managed by the participant who is the device manager. 25. A management system for a card, a device, and a product, comprising a plurality of service processing means, wherein each service processing means allows a participant in the system to manage a card, a device, and a product. Enabling at least one of them to be performed, including message management means, which are provided to each participant in the system, and which are provided between each service processing means. , And arranged to operate as a communication interface for routing message data between the card and the device, said means for interfacing a network of service processing means and a plurality of participants, the card, the device and The above-mentioned system, wherein the system is arranged so that management of the product can be performed. 26. A management system for cards, devices and goods, comprising a network, the network having a plurality of nodes, each having service processing means, said means comprising: System participants are cards,
Enabling at least one of device and product management, and each node having message management means, between the service processing means of each node, and a card Is arranged to act as a communication interface for routing message data between the device and the device.
The system. 27. The service processing means includes device management means, which means that a participant who is a device manager manages a device without managing products related to the card and without managing the card. 27. The system of claim 26, wherein the system is capable of running alone. 28. The service processing means includes card management means, said means comprising:
28. The system according to claim 26 or 27, wherein a card administrator participant can perform the card management role alone without managing the merchandise associated with the card and without managing the device. 29. The service processing means includes merchandise management means, which means that a participant who is the merchandise owner can independently perform the role of merchandise management without managing a card and without managing a device. Claims 26, 27, and 2
The system according to any one of claims 8 to 13. 30. A method for managing cards, devices, and merchandise, comprising the step of defining a three-party environment for card management, wherein the three-party environment for card management comprises: A participant who is the card administrator responsible for managing the operation of a particular card, and a participant who is the device administrator responsible for managing the device, receiving the card, and performing merchandise transactions. And the participant who is the product manager responsible for managing the product-related scope of the card environment, and the participant who is the equipment manager, the card management participant, and the participant who is the product manager Said method being a separate entity. 31. The computer system further comprising providing a computer system, wherein each of the roles of a participant who is a card administrator, a participant who is a device administrator, and a participant who is a merchandise administrator. 31. The method of claim 30, including modules that allow the modules to be performed separately from each other. 32. The system allows a participant, a merchandise manager, to easily have direct access to merchandise to directly affect control of merchandise associated with a card or device. 32. The method according to claim 30 or claim 31, comprising steps. 33. The method of claim 30, further comprising the step of enabling a participant who is a product owner to load data into the product. 34. The method according to claim 32, further comprising the step of enabling a participant who is a product owner to receive data from the product. 35. The method of claim 34, wherein the data is transaction data. 36. The method according to any of claims 32-35, wherein the participant who is the merchandise owner comprises downloading the merchandise application to a card or device. 37. A method of managing merchandise, comprising: limiting a participant who is a merchandise manager who is solely responsible for managing merchandise without managing a card and without managing a device; and Providing the participant who is the merchandise manager with the ease of directly acting on the control of the merchandise associated with the card or device. 38. The method of claim 37, including the step of providing ease for allowing a participant who is a product owner to load data into the product. 39. A method as claimed in claim 37 or claim 38, including the step of providing an ease to enable a participant who is a merchandise manager to receive data from the merchandise on the card or device. . 40. The method of claim 39, wherein the data is transaction data. 41. A method according to any of claims 37 to 40, comprising the step of providing an ease to allow a merchant owner to download merchandise applications to a card or device. . 42. A method for managing a card, the card manager having a role of performing card management independently without managing products related to the card and without managing devices. Having the step of limiting participants,
The method. 43. A method of managing a device, the device manager having a role of performing device management independently without managing products related to the card and without managing the card. The method above comprising the step of limiting participants. 44. A comprehensive system for managing cards, devices, and merchandise, the system including a card management module, a device management module, and a merchandise management module, which are used separately. , And other similar systems and networks to allow different entities to perform card management, equipment management and merchandise management alone, and to facilitate management of cards, equipment and merchandise Said systems being networked together to enable them to do so. 45. The system further comprises a message management module for managing routing of message data among the card, device, merchandise, card management module, merchandise management module, and device management module. It is arranged to operate as a communication interface,
46. The system of claim 44, wherein each participant in the comprehensive system utilizes the message management module. 46. An arrangement of cards, devices, and merchandise, comprising a computer computing system, having a storage location for receiving a plurality of merchandise applications, including security means, the means comprising: Enabling selective access to the storage location for the merchandise owner, whereby the merchandise owner separately accesses and manages their merchandise stored in the memory location Said arrangement. 47. The card, device, or merchandise arrangement of claim 46, wherein the storage location is mounted on the card. 48. The card, device, or merchandise arrangement of claim 47 or 48, wherein the storage location is mounted on the device. 49. The card, device, or merchandise arrangement according to claim 46, 47 or 48, wherein the security means comprises a token serving as a key to enable access to the storage location. 50. A merchandise management system according to any one of claims 15 to 20, wherein the merchandise management system according to any one of claims 15 to 20 is included so that merchandise owners can manage merchandise.
9. The arrangement of cards, devices, and merchandise according to any one of 9 above. 51. A card, a device, and a product management system according to any one of claims 1 to 15, so as to enable management of the arrangement. Placement of cards, devices and products described in.