JP2005107877A - Business card, business card information management system, business card information management method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To simply manage a plurality of types of personal business cards while ensuring data integrity with paper business cards, appropriately manage target parties to which changes in business card information should be reflected, and accommodate even business card information and a personal address book managed by different entities. <P>SOLUTION: A business card information management system comprises a user data saving space 132 having an address book data saving area for associating and saving business card information about parties to business card exchange and a user's business card IDs given to the parties for business card exchange, and a career record saving area for associating and saving the user's business card information and the parties' business card IDs given for business card exchange; address book maintaining means 127 for, upon the update of the user's business card information, updating the user's business card information in the user data saving space and updating the user's business card information in update target users' user data saving spaces; and outputting means 128 for outputting the business card information in the user data saving space. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a technology for linking a paper business card and an address book on a network, and in particular, a business card and a business card capable of creating / updating an address book from the business card information with other providers providing a business card creation service. The present invention relates to an information management system, a business card information management method, and a program.

In general, paper business cards (this is called Paper Business Card, abbreviated as PBC) are widely used in the world.
Conventionally, in the PBC usage model, a business card service provider (a business card printing business or a business card printing department in a company, which is selected by a company or various organizations (collectively referred to as an organization)). Provider (abbreviated as SP)) is the original data (name of organization, name and title of organization member, location of organization, contact information, etc.) written on the organization member's PBC with the permission of the organization. Called master data). The SP generates (inputs) and updates PBC data with the provision of information and permission from the organization. By this mechanism, the credibility and reliability of PBC data is secured by the organization.

  While PBC master data is stored by the SP, organization members are allowed by the organization to always store a certain number of PBCs at hand. In other words, organization members can order a certain number of business cards from a business card service provider with the permission of the organization when the number of business cards on hand decreases (generally, each box contains 100 cards per order). it can). With this mechanism, when an organization member needs a PBC for various daily business activities as an organization member (referred to as an activity), the PBC can be requested from the business card box on hand without asking the SP each time. It can be taken out and handed over to the exchange partner.

  Organizational members can always carry a PBC and give it to various people they meet during the activity. In other words, members of the organization can expand their PBC exchange partners by meeting new people during the activity.

  In recent years, business activities of corporations have become more sophisticated and complicated, and there are increasing cases of forming cross-organizational project teams apart from the existing organizational structure. In addition, there are many people who work for a plurality of companies or who belong to a plurality of organizations and engage in various activities. These individuals carry multiple PBCs and use different PBCs depending on the situation. In other words, when an individual who belongs to multiple organizations and engages in multiple activities meets a new person, the PBC presents a different PBC to the other party according to the context of the encounter, and uses their own identity (societal positioning). Make it possible.

However, PBC has the following disadvantages.
In other words, if the number of exchange partners increases and the number of PBCs to be stored increases, it becomes increasingly difficult to manage the PBC, such as taking time to search for the PBC you want to see or making it impossible to search.
In addition to the information described in the PBC, if you want to describe additional information about the situation and the other party during the PBC exchange (appearance, details of work in charge, personality, etc.), you can write it by writing in the margin of the PBC Limited amount of information.
When a PBC recipient wants to enter and manage the information on the PBC on a personal computer, PDA, or mobile phone (collectively referred to as an information device), the PBC recipient manually enters the information. It is necessary to input the description information into the information device.
The information on the PBC becomes obsolete when the business card provider's position (position, role) in the organization changes or the organization's office moves. In order to update to the latest information, it is necessary to contact the other party by telephone or e-mail and have them receive the latest information.
For those who carry multiple PBCs and use different PBCs depending on the context of the activity, it is difficult to manage which PBCs were passed to which party.
People belonging to multiple organizations often work in multiple offices depending on their activities. Each office has a business card folder, and the PBC is managed by sorting it into the corresponding business card folder according to the person who meets in the context of the activity. In such a case, there is a problem that it is difficult to centrally view all business cards stored by the user.

In order to solve or supplement the disadvantages of the PBC described above, several systems utilizing information technology have been devised and put into practical use.
First, as a method to solve the troublesome manual input when importing PBC description information into information equipment, a system that imports all character strings printed on PBC directly into information equipment using OCR and character recognition software, PBC description A system has been devised in which information is encoded into a bar code or a two-dimensional code, printed on a PBC, and loaded into an information device with a code reader. (For example, see Patent Document 1).

In either method, since the data master is printed on the PBC, there is a problem that the acquired information becomes obsolete as the PBC changes when the organization or role of the other party is changed.
In addition, as a system to solve the problem of information obsolescence, a personal "online address book" is opened on the information device or server, and when your business card information changes, the online address book of the other party is sent through the network. A system that automatically rewrites information (called an electronic business card) has been devised. (For example, see Patent Documents 2 to 3.) This electronic business card system has the following problems.

1) The electronic business card is a model for generating and managing its own business card information. In other words, there is an area for storing your business card information on the information device or server, and you enter your business card information in that area yourself, and if you change your business card information, you can enter your own changes. . For this reason, it has lost the advantage that PBC has as an advantage that business card information is secured by the organization.

2) In electronic business cards, the exchange of business card information between online address books is not associated with the exchange of PBC. In other words, the PBC is exchanged when meeting people in daily activities, and the electronic business card is exchanged when meeting people via the information network. When trying to exchange a business card with a new person in the electronic business card world, the business card information of another person is searched by some method, and then the electronic business card is sent to the other party. In other words, it is a premise for exchanging business cards that other people publish business card information on the network. In practice, however, many people do not want to disclose and search their business card information on the network, and as a result, exchange of electronic business cards is not activated. On the other hand, in the world of PBC, as already mentioned, new encounters between people occur in various daily activities, and new business card exchange opportunities are created each time, so business card exchange is activated. It has a mechanism. There is a problem of how to link electronic business cards with the PBC mechanism to promote business card exchange on the network.

3) In the conventional electronic business card system, it is assumed that one individual has a single business card information (personal profile information). The system manages "who exchanged business cards with", and when an individual updates business card information, the system is updated to the online address book of all the parties to whom the individual handed the electronic business card. Go to write information. However, as already mentioned, nowadays, an increasing number of individuals have a plurality of business card information and use different business card information (= different identities) depending on the context of the encounter. In order to accurately grasp the business card exchange relationship between people in such a modern environment, it is not enough to manage "who exchanged business cards with", and "who exchanged business cards with whom." It is necessary to manage.
JP 2001-260575 A JP 2003-67392 A JP 2003-108479 A JP 2003-122762 A

  The present invention has been made in response to such a conventional situation, and can easily manage a plurality of types of business cards owned by an individual while ensuring data linkage with a paper business card, and change business card information. Business card, business card information management system, business card information management that can properly manage the target (update target) to reflect the change, and can also handle business card information and personal address book of different management subject It is an object to provide a method and a program.

  In order to achieve the above object, a business card information management system according to the present invention is a business card information management system for inputting business card information and storing it as address book information. Address book data storage area in which the business card ID submitted to the other party for exchange is stored in association with each other, and the other party presented for exchange of the business card information and the business card A user data storage area having a carrier record storage area stored in association with each other's business card ID, and updating the own business card information in the user data storage area when updating the own business card information Address book maintenance means for updating the business card information in the user data storage area of the target user and the business card information in the user data storage area are output. Output means.

  Here, “update” means not only the case where new information is overwritten on old information, but also the case where new information is sequentially added while leaving old information as it is. In the latter case, information before a predetermined period or when a predetermined number of updates has been exceeded may be deleted from old information.

Preferably, the address book data storage area and the carrier record storage area may be configured such that different access authorities can be set.
By managing the business card information separately in the address book data storage area and the carrier record storage area, for example, you can use your business card information stored in the carrier record storage area and secure the security of address book data with high confidentiality. Can be secured. Conversely, since the data in the carrier record storage area can be used as its own history information, it can be operated with high security.

  The address book data storage area and the carrier record storage area do not need to be physically stored in the same storage area, and part or all of the business card ID such as user identification information may be linked as an index.

  It is also effective to store both storage areas in different databases so that the security level of the databases can be changed. In particular, the information in the address book data storage area is preferably constructed with a high security level because highly confidential information stored with personal activities is stored. In this way, only important information of the address book data can be specially managed, and a high security system can be realized at low cost compared to managing all information at the same security level.

  Here, changing the security level means, for example, that special authentication is required when accessing the database, or that a firewall protects against external threats. The business card ID means information capable of identifying a business card such as a business card creator, a user, a role (role), or a version (version). Business card IDs include those that are encoded and encrypted. As information included in the business card ID, identification information may be provided in a database or business card management unit owned by the business card creator instead of the identification information of the business card creator.

In the business card information management system according to the present invention, the address book data storage area further includes a reception status indicating that the business card provided by the other party has been received, and a reception notification reception status indicating that the business card provided by the partner has been received. The address book data storage area and the carrier record storage area are set on the basis of both statuses, and each has an exchange status indicating that the business card exchange has been established.
By using the reception status, the reception notification reception status, and the exchange status, it is possible to appropriately manage the exchange state of the business card.
In particular, when the management authority is different between the address book data storage area and the carrier record storage area, they are operated independently. Therefore, it is effective to provide an exchange status for each.

  Preferably, the information-coded business card ID written on the business card includes operation control information capable of changing the operation of the business card information management system, and the user requesting the business card information based on the business card ID including the operation control information When a business card information acquisition request is made, it is preferable to operate in accordance with the operation control information included in the business card ID.

  The operation control information is, for example, information for determining whether or not to automatically permit business card exchange. When this information is included in the business card ID, it is necessary to input the permission of the user to whom the business card information is requested. Instead, the exchange is immediately established. In this case, normally, the exchange may be automatically established, and depending on the operation control information, a license input may be required. When a business card is distributed, a business card to be distributed depending on whether it is automatically exchanged when the other party requests business card information, that is, to be updated or whether permission input (such as scanning the business card you have acquired) is required. If it is changed, it is not necessary to input a license every time an exchange is established, so convenience is improved.

  The design of the business card, such as the print position or color of the information code, may be changed according to the operation control information. This is because the information described on the business card is not changed and only the design is slightly changed, so that the operation control information can be identified without affecting the social activity.

  As the operation control information, in addition to the above, there is a prompt for input as to whether or not to be updated on the confirmation screen, or a disclosure level of self information. The self-information disclosure level refers to the storage of personal information other than business card information in the address book data storage area. When a business card exchange request is received from a business card exchange partner, it is determined according to the disclosure level. It provides personal information in a range.

  The business card information management system according to the present invention further includes a request source processing unit and a request destination processing unit for managing the exchange state between the request source user and the request destination user regarding the transfer of business card information. Then, the request source processing unit sends a business card information acquisition request including the business card information of the request source user and the business card ID of the request destination user to the request destination processing unit, and the request destination processing unit receives the business card information acquisition request. The business card information of the request source user is stored in the user data storage area of the request destination user, the business card information corresponding to the business card ID stored in the user data storage area is extracted and sent to the request source processing unit. When the processing unit receives the business card information of the request destination user, the processing unit stores it in the user data storage area of the request source user and sets a reception status flag of the business card information, and sends a receipt notification to the request destination processing unit. In the section, upon receipt of the receipt notification, the receipt notification reception status flag of the user data storage area of the request destination user is set, and then when the request source user's business card information acquisition request is transmitted from the request destination user terminal, The request processing unit sets the requesting user's receipt status flag and sets the exchange status flag on the condition that the requesting user's business card information already exists in the user data storage area of the requesting user. The request source processing unit is provided with business card information exchange management means for setting a receipt notification reception status flag and setting an exchange status flag when the receipt notification is sent to the user.

By operating the reception status, the reception notification reception status, and the exchange status as described above, it is possible to appropriately manage business card exchanges that are normally performed asynchronously.
Here, in the two parties who exchanged the business cards, the one who made the business card information acquisition request first is called “request source”, and the one who made the business card information acquisition request later is called “request destination”.

  Further, the business card information management system according to the present invention further includes, for each business card creator, one or more business card information conversion algorithms for converting the business card creator's business card format into a unified format, A business card information acquisition means for receiving a business card information and a business card ID sent from the server; a means for selecting a business card information conversion algorithm to be used by using information contained in the business card ID; and a selected business card information conversion algorithm. And a business card information conversion means for converting the business card information received by the business card information acquisition means into a unified format and storing it in the carrier record storage area of the user data storage area corresponding to the business card ID. .

  By providing a conversion algorithm for each business card creator, it is possible to convert different business card formats from one business card creator to a unified format. The “information included in the business card ID” includes database identification information (D-ID) assigned to each business card creator. The “business card information conversion algorithm” means means for converting the format of business card information according to a specific rule, and includes a data item correspondence table and logic for executing conversion by referring to the table.

Instead of storing the conversion algorithm for each business card creator, the conversion algorithm may be patterned and a correspondence table between the business card creator and the pattern may be stored.
Here, the unified format means a format for management by the business card information management system. In general, a general-purpose format such as the vCard format is adopted.

In the business card information management system according to the present invention, the user data storage area further includes a user data storage area of a transfer source and a transfer destination of business card information stored in the address book data storage area and / or the carrier record storage area. Business card information is transferred within the allowable transfer count based on the user data storage area identification information, including identification information and allowable transfer count, and the transfer count is only the original owner of the address book data and / or carrier record Is provided with a business card information transfer means configured to be controllable.
By making the number of transfers controllable, unlimited transfers can be prevented.

Preferably, the business card information transfer means may determine whether or not transfer can be performed based on the attribute information of the transfer destination user.
For example, a transfer condition table is provided so that transfer is not performed unless the attribute of the transfer destination user satisfies the condition. Thus, in principle, it is possible to prevent transfer to a user who does not conform to the intention of the owner of the business card information while permitting transfer for the designated number of times.

The business card information management system according to the present invention further includes means for storing the terminal model and the address book data format of the terminal in association with each other, means for inputting identification information of the user terminal, and the input user terminal Means for extracting the terminal model based on the identification information, converting the user's address book data into the address book data format of the user terminal, and transmitting the data to the user terminal.
By transmitting the address book data in a format suitable for the user terminal, it is possible to download and view it on the terminal, thereby improving convenience.
Here, the terminal model means a group of terminals according to their functions. For example, in the case of a mobile phone, it includes a carrier company or model.

  Also, the business card information management method according to the present invention inputs the business card information sent from one or more business card creators' servers to the electronic business card manager's server, stores it as address book information, A business card information management method for transmitting information of the address book to a terminal, for each business card creator, storing one or more business card information conversion algorithms for converting the business card creator's business card format into a unified format A step of selecting a business card information conversion algorithm to be used by using information included in the business card ID, receiving business card information sent from a server of a business card creator, and selecting the received business card information. Using a business card information conversion algorithm to convert to a unified format and store it in the user data storage area corresponding to the business card ID, and sent from the user terminal A step of inputting the business card ID read from the incoming business card, and extracting the corresponding business card information from the user data storage area corresponding to the business card ID, and address book data in the user data storage area associated with the user terminal Storing in the storage area; and transmitting information stored in the address book data storage area to the user terminal.

Preferably, an information code coded based on the business card ID is written on the business card, the business card ID is restored by reading this information code with input means (for example, QR code reader) of the user terminal, and the electronic business card management It is good to transmit to the server of a trader.
As a method for acquiring the business card information from the business card creator, for example, the business card creator server requests the business card creator together with a business card ID capable of identifying the user at the business card creator, and the business card creator server responds to this request. There is a way to send business card information.
Here, “the user at the business card creator can be identified” means that the user of the business card creator can be identified directly from the user identification information, and in the server or business card information management system of the business card creator, This is intended to include cases in which identification is possible indirectly, such as specifying a user in the business card creator by providing a correspondence table with identification information of the user of the business card creator.

  Although business card information that has changed may be sent spontaneously from the server of the business card creator, if a large amount of business card information is sent simultaneously from multiple servers, the load on the system may be concentrated Therefore, for example, the number of business card information to be transmitted from the server of the business card creator is notified in advance to the business card information management system, and the load can be distributed by sending based on the transmission request from the system.

The storage of the business card information conversion algorithm and the conversion to the unified format by the algorithm may be performed by a server of the business card creator.
In this case, the business card manufacturer's server stores the business card information stored by the business card creator based on the data format conversion means for converting the business card information format of the business card creator into the address book data format which is a unified format. A step of storing business card information specifying means for specifying information, a step of extracting business card information to be transmitted by the business card information specifying means when there is a business card information transmission request together with a business card ID from an electronic business card management company, and extracted This includes a step of converting the business card information into the address book data format by the data format conversion means, and a step of transmitting the business card information in the address book data format to the server of the electronic business card manager. Note that the business card information may be converted into a unified format when the business card information is changed in the server of the business card creator, and the business card ID and the business card information may be transmitted to the server of the electronic business card manager.

The business card information management method according to the present invention further includes a step of acquiring business card information update information at the server of the business card creator, and a business card ID and business card information related to the update when the business card information is updated. A step of acquiring, converting the business card information into a unified format, storing the business card information in a carrier record storage area of a user data storage area associated with the business card ID, and associating the business card ID with the business card ID The method includes a step of extracting a business card ID in a business card exchange state and a step of updating business card information in an address book data storage area of the business card ID in the exchange state.
When a business card creator updates the business card information of the user, the business card information is acquired and stored in the carrier record storage area for the user and the business card in the exchanged user's address book data storage area Update information.

  In the present invention, the user is conscious of whether or not the business card information is updated by giving the right to write business card information to a person other than himself (for example, a person who manages business card information such as a company to which he belongs) in the carrier record storage area. Even if it is not, the user's own business card information is automatically updated, and the business card information of the address book of the other party in the state where the business card exchange has been established can be updated.

  On the other hand, by not giving the user the authority to write the carrier record storage area, the company can prevent falsification of the business card information. In addition to this, the writing authority of data items in the address book data storage area and the carrier record storage area, for example, the business card information part, the memo, and the message part may be divided.

  In the business card information management method according to the present invention, the business card information is encrypted and stored using the business card ID of the user who owns the business card information or information associated therewith. Then, at the stage where the communication connection with the user terminal is established, authentication by terminal identification information is performed, and then decryption processing of business card information stored in the address book storage area of the user corresponding to this terminal identification information is started, The business card information that has been decrypted is transmitted to the user terminal in response to a business card information read request from the user.

  In the present invention, the terminal identification information and the encrypted business card information are stored in association with each other. When communication (session) with the user terminal is established, the terminal identification information is input and authentication is performed using the information. The corresponding business card information is decrypted. As a result, since the decryption process can be executed while the user inputs the user ID and password and the business card information transmission request process is performed, the response performance of the system can be improved and the data is being saved. Security can be increased. Furthermore, since the business card information cannot be normally acquired unless the authentication based on the terminal identification information and the user authentication based on the user ID or the like match, data leakage can be prevented even if the terminal or the user ID is stolen.

  In addition to the above, encryption may be performed between the business card creator and the business card information management system. In this case, the security at the time of updating the business card information can be ensured by encrypting with the ID (identification information) of the business card information management entity (for example, company) for each exchanged data.

A business card according to the present invention is a business card used in the business card information management method described above, and includes a business card ID including at least business card creator identification information, user identification information, and information capable of identifying the business card information in the business card creator. An information code is described.
Since the business card ID is written on the business card in a coded state, in order to obtain another person's business card ID, it is basically necessary to exchange the business card. Can be prevented. Moreover, if the partner who exchanged the business card is not required to provide the business card information on the server, the burden on the user can be reduced.

  The business card according to the present invention includes the identification information of the business card creator in the business card ID, so that the business card information of each user who creates business cards with a plurality of different business card creators can be acquired, and can be centrally managed as address book information . Moreover, in this invention, since it describes with an information code, when exchanging business card information on a server after exchanging business cards, it can carry out smoothly and simply. In addition, since the personal information (name, work place, address, etc.) itself described on the business card itself is not coded, the size of the information code can be small, and the limited space on the business card is occupied by the information code. Can be avoided.

In addition, in order to make it possible to use different business cards depending on the situation, such as corporate or personal use, as the scope of social activities of users expands, role identification information (role ID) and business card version (version) are included in the above information codes. Information may be included.
Here, the information code means information coded like a barcode of a one-dimensional information code or a QR code of a two-dimensional information code. In particular, it is effective to use a code such as a QR code that can be easily restored even if some information is missing, such as a business card that is easily damaged.

Preferably, the information code includes an encrypted business card ID and non-encrypted business card information management service information.
Thereby, even when an information code is read by a terminal without a decryption function, the address of the service provider and the service content can be known, so that the subscription to this service can be promoted. Further, a business card ID that is not coded may be described in the vicinity of the information code on the business card so that a business card information acquisition request can be made manually from the terminal. In the case of this manual input, it may be linked to the service introduction screen.
Here, the business card information management service information means the URL of the business card information management service provider and information related to the contents of the service.

  The program according to the present invention inputs business card data sent from a server of one or more business card makers, stores it as address book information, and transmits the address book information to the user terminal. A management program for each business card creator, storing one or more business card information conversion algorithms for converting the business card format of the business card creator into a unified format of the business card information management system, and a business card ID The processing for selecting the business card information conversion algorithm to be used using the information included in the information, and the business card information conversion algorithm for receiving the business card information sent from the server of the business card creator and selecting the received business card information Use this to convert to a unified format and save it in the user data storage area corresponding to the business card ID, and read from the business card sent from the user terminal Processing to input the taken business card ID, and the corresponding business card information is extracted from the user data storage area corresponding to the business card ID and stored in the address book data storage area of the user data storage area associated with the user terminal And a process of transmitting the business card information stored in the address book data storage area to the user terminal.

A user terminal program according to the present invention is a user terminal program that reads an information code written on a business card and transmits a business card information acquisition request to a server of an electronic business card management company. Processing for extracting a business card ID from the server, processing for adding address information for transmission to the server to the extracted business card ID, processing for displaying the address information and business card ID on the screen of the user terminal, and confirmation card The computer is caused to execute a process of transmitting a request for acquiring business card information including an ID to a server.
By masking information other than the business card ID necessary for acquiring the business card information, such as unencrypted business card information management service information, the confirmation process can be performed quickly and smoothly.

  In the present invention, business card information can be efficiently obtained using an information code written on the business card, and a carrier record storage area for storing the user's own business card information and address book data storage for storing the acquired business card information Address book information or business card exchange establishment status is managed separately for each area, making it possible to use a wide range of business card information. When changing business card information, the person to be updated can be selected appropriately, and business card information is managed. Database or business card creator identification information and user (member) identification information for managing personal address book data are individually provided and written or pasted on the business card as business card identification information. It is possible to deal with different business card information and personal address book data.

  Embodiments of the present invention will be described below. FIG. 1 is a functional block diagram of a business card information management system according to the present embodiment, a user terminal connected to the system via a communication network, and a server of a business card creator (hereinafter referred to as a business card creation service provider or SP). is there.

  In this figure, a business card information management system 1 includes a transmission / reception unit 11 that transmits / receives data through a communication network 4, a central processing unit 12 that processes data received from the transmission / reception unit 11, and a storage unit 13 that stores data. It is composed of

  Further, the central processing unit 12 has a basic information registration means (function) 122 for registering personal information of the user, a terminal communication means (function) 123 for establishing communication with the user terminal 2, and the SP server 3. Business card information requesting means (function) 124 for requesting business card information, business card information obtaining means (function) 125 for receiving business card information sent from the SP server 3, and executing business card information exchange processing and reflecting it in the address book Business card information exchange management means (function) 126 to be performed, address book maintenance means (function) 127 for updating business card information in the address book of the person to be updated when the business card information is changed, and transfer of user data such as the address book A business card information transfer means (function) 128 to be performed and an output means (function) 129 for transmitting address book information to the user terminal 2 are provided.

  The storage unit 13 includes a user information database (DB) 131 that stores personal information such as user identification information and name, and a user data table (users) that stores business card information of the user and business card information of a business card exchange partner for each user. Data storage area) 132 and an SP database (DB) 133 for storing information related to the business card creation service provider.

  The business card information management system 1 functions as a server operated by an electronic business card management company (hereinafter referred to as a DBC service company).

  The user terminal 2 includes an input unit 24 that reads information codes and inputs data, a display unit 25 that displays data transmitted from the business card information management system 1, and a transmission / reception unit 21 that transmits and receives data through the communication network 4. And a central processing unit 22 that performs data processing.

  The SP server 3 includes a transmission / reception unit 31 that transmits / receives data through the communication network 4, a central processing unit 32 that performs data processing, and a storage unit 33 that stores data such as business card information.

  FIG. 2 shows a detailed functional block diagram of the SP server. Here, the central processing unit 32 receives a request information input means (function) 332 for receiving a business card information request from the business card information management system 1, and a business card ID (business card identification information) sent from the business card information management system 1. Business card information specifying means (function) 323 for extracting business card information to be converted into SP server identification information and transmitted, data format conversion means (function) 324 for converting the extracted business card information into a unified format, and data format conversion It has a business card information transmitting means (function) 325 for transmitting subsequent business card information to the business card information management system. The storage unit 33 also includes an ID management database (DB) 332 that stores the correspondence between identification information between the business card information management system and the SP server, and a business card information database (DB) that stores the business card information of the user of the SP service. 331 is stored.

  The SP server 3 may be a server of a person who creates a business card, and may be a server of a business card print department in a company in addition to a server of a business card creator. The business card information specifying unit 323 and / or the data format conversion unit 324 may be provided on the business card information management system 1 side.

[1. Overview of DBC service]
Next, a DBC (Digital Business Card) service performed using the system 1 will be described.
As shown in FIG. 37, the DBC service refers to a paper business card 5 and business card information (information for business card creation) on a database of an existing business card creation service provider (hereinafter abbreviated as “SP”) corresponding thereto. An information code 6 that is an index for connection is described, and a user who receives provision of this service can obtain business card information corresponding to the information code simply by inputting the information code. The business card information can be managed as a book, and when the user's business card information is changed, the address book of the person to be updated is automatically updated.

  As shown in FIG. 3, this information code is written on a business card as a two-dimensional code (QR code), for example, and is input by scanning with means having a code reader function such as a mobile phone (user terminal). Then, it is sent to the business card information management system 1 which is the server of the DBC service provider via the communication network.

On the other hand, a user who does not have a mobile phone with a code reader function can receive the same service by manually inputting the character string described below the information code after connecting to the business card information management system.
It is assumed that normal business card information is expanded and a business card image, a memo area (memos of both the business card hander and the receiver), and other business card management information added are called DBC data.

The DBC service provides a dedicated user data storage area (hereinafter also referred to as a DBC frame) for each user account. In the DBC frame, each user saves and manages the address book data storage area (hereinafter also referred to as the Address Book) where the business card exchange partner DBC data is stored and managed. A carrier record storage area (hereinafter also referred to as “career record”) to be performed, and other management data.
Users receive services by connecting to their DBC frames from the mobile phone or PC via the Internet.

  The business card information management system 1 always obtains the latest business card information by cooperating with the database 33 of the business card creation service provider (SP) compatible with DBC. Thereby, the latest information can always be used on each user's address book data storage area and carrier record storage area.

  The information code written on the business card is obtained by encoding the business card ID like a two-dimensional QR code. As shown in FIG. 4, the business card ID includes identification information (hereinafter referred to as a member ID or M-ID) of a user (business card owner), identification information of a service provider to which the user is subscribed (hereinafter referred to as a database ID). Or DB-ID), role identification information (hereinafter referred to as role ID or R-ID), and business card version identification information (hereinafter referred to as version number or V-ID).

[2. Business card ID configuration]
Next, the configuration of the business card ID (hereinafter also referred to as DMRV-ID) will be described in detail with reference to FIG. The business card ID is mainly composed of information for identifying the user and information for identifying the business card.

(2.1 Information for user identification)
In the DBC service, identification of each member is realized by a two-tiered mechanism of managing a business account information on the SP side and managing user accounts (herein, members and expressions) in the database. An ID is issued from the DBC service to a database storing business card information on the SP side, and each SP issues a member ID to a user (user) of the service.

By combining the database ID and member ID in this way, the DBC service user can be uniquely identified.
Here, D-ID (database ID) is an identification number of a database in which business card information is stored. The database is usually managed by each SP. In general, one SP has one database. In the case of a company user, the company has a database. When one SP owns a plurality of databases, it can be identified by this D-ID.

M-ID is an identification number of each member in the DB. A DM-ID (user identification ID) is a unit for granting a service use account in the DBC service. One DBC frame is allocated for each DM-ID. A single user may have multiple accounts for the DBC service and have multiple DM-IDs. DM-ID is expressed as follows.
<DM-ID> = <D-ID> + <M-ID>

  The above formula means that a combination of D-ID and M-ID is defined as DM-ID. However, it is possible to generate DM-ID from D-ID and M-ID by a predetermined algorithm and to extract D-ID and M-ID from DM-ID instead of simply arranging IDs. .

(2.2 Information for business card identification)
In the DBC service, one user account has a plurality of (for example, ten) roles (role or type) at the same time, and each role can have a business card. (For example, business cards for business, business cards for engineers, business cards for campaigns, etc.)
Each role is identified by an identification number (DM-ID) of each user and a role number (hereinafter referred to as branch number or R-ID).
The R-ID is numbered on each SP side at the request of the user.
Here, the DMR-ID is expressed as follows.
<DMR-ID> = <DM-ID> + <R-ID>

A V-ID (referred to as a version number or a version ID) enables identification of a business card in units of version numbers corresponding to the occurrence of information update for each business card (DMR-ID).
The version number is assigned on the SP side by a user request (change of business card information).
From the above, the identification number (abbreviated as DMRV-ID) of each business card is expressed as follows.
<DMRV-ID> = <DMR-ID> + <V-ID>
When an SP that does not manage M-ID, R-ID, or V-ID participates in the DBC service, the system shall be customized so that these can be managed.

[3. Configuration of user data storage area]
Next, the configuration of the user data storage area (DBC frame) stored in the business card information management system 1 will be described in detail.
A DBC frame is a data area for each user reserved on the DBC service side. One DBC frame is secured for one DM-ID.

  FIG. 5 shows a conceptual diagram of the DBC frame. In this figure, the DBC frame has two types of storage areas (an address book data storage area for storing information on the name card exchange partner and a carrier record storage area for storing information on the business card creation history of the DBC frame owner) There is a so-called cabinet, in which the data body (DBC data) used by the user is stored for each DM-ID.

Next, FIG. 6 shows items of data areas managed in the DBC frame.
Here, the DBC frame number is a number used for managing the DBC frame on the DBC service side.
The DM-ID is a DM-ID registration area of the owner (owner) of the DBC frame.
The default value (Default Value) is obtained by storing each entry data (DBC data) stored in the address book data storage area and the carrier record storage area in the DBC frame by another business card information transfer means 128, which will be described later, with another DM-ID. This is the initial value when trying to transfer to another DBC frame.

  The address book forwarding information (Address Book Forward Info) in the default value column sets an initial value when an entry in the address book data storage area is to be transferred to a DBC frame of another DM-ID. The transfer destination can be set by the owner of the DBC frame, and a plurality of transfer destinations can be set.

  As a specific data item, AB-F CNT is the default number of transfers, and entries in the address book data storage area continue to be transferred indefinitely, adding load to the system and inadvertent due to careless settings. In order to prevent the transfer from being performed to the transfer destination, a prescribed value for the number of transfers is set. The initial value is 1.

AB-F To LST is a default transfer destination, and is a list of DM-IDs of transfer destination DBC frames recorded in this area according to the transfer setting of the owner.
AB-F From LST is a list of DM-IDs that are recorded when a transfer setting is made from a DBC frame of any DM-ID to the DBC frame. When the DM-ID of this DBC frame is changed or deleted, this information is recorded in order to convey it to the transfer source DBC frame.
Carrier record forwarding information (Career Record Forward Info) in the default value column is when transferring DBC data stored in the carrier record storage area of the relevant DBC frame, that is, the owner's business card creation history to another DM-ID It is used for.

As a specific data item, CR-F CNT is a default transfer count and sets a prescribed value for the transfer count. The initial value is 1.
CR-F To LST is a default transfer destination, and is a list of DM-IDs of transfer destination DBC frames recorded in this area according to the transfer setting of the owner.
CR-F From LST is a list of DM-IDs that are recorded when a transfer setting is made from a DBC frame of any DM-ID to the DBC frame.

The address book data storage area is an area for storing information such as business card exchange partners. Registered as each entry is the partner's DBC data obtained by scanning the partner's business card ID obtained by scanning the DBC code (information code), and the contact information manually registered from the keyboard, etc. Information, a collection of DBC data.
The carrier record storage area is an area for storing DBC data related to the owner. This is a set of DBC data that stores DBC data of all version numbers (DMRV-ID) of all DMR-IDs under the DM-ID.

The access authority of each data area is recorded when the DBC frame number (management number) is generated for the first time, and is not changed until the DBC frame is discarded.
The DM-ID is registered by the basic information registration unit 122 when a DBC frame is generated by a service application from a user, and is changed by a DM-ID change application from the owner.

The address book data storage area is registered when the owner of the DBC frame scans a DBC code printed on another user's DBC card, or performs a manual input search for a business card ID. It is also possible to register manually. Each entry can be referred to or entered by the owner, and can be changed or deleted.
Regarding the carrier record storage area, when the master data on the business card creator (business card creation service provider) used by the owner of the relevant DBC frame is updated, the update is notified to the DBC service side, and this data is stored in this area. Stored in The owner can input / change / delete a reference / memo.

  In addition, as shown in FIG. 7, the address book data storage area shows the business card of the other party who exchanged the business card (AB-YC: Your Card) and the business card of the owner (owner) offered to the partner for the exchange of the business card. ID (MCIE: My Cards In Exchange) is stored in association with each other. Also, in the career record storage area, your business card information (CR-MC: My Card) and the business card ID of your partner (YCIE: Your Cards In Exchange) Associated and saved.

(3.1 Structure of each data entry in the address book data storage area)
Next, each data item in the address book data storage area will be described with reference to FIG.

  In this figure, the address book data storage area includes folder management data generated for each DM-ID, file management data generated for each DMR-ID, card management data generated for each DMRV-ID, and business card. It consists of card data such as information. As card data, business card information of a partner who exchanged business cards is stored. Hereinafter, each item name will be described.

<Folder management data>
A folder number is assigned to each DM-ID. Each time a new DM-ID DMRV-ID DBC data is received, a folder entry is added.
DM-ID is a DM-ID of DBC data stored in the folder entry.
The folder entry creation date / time is the date / time when the folder entry was created.
The DM-ID status records the validity / invalidity of the DM-ID of the DBC data stored in the folder entry.

<File management data>
A file management number is assigned to each DMR-ID under the DM-ID. Each time a new DMR-ID DMRV-ID DBC data is received, a file entry is added.
The DMR-ID is a DMR-ID of DBC data stored in the file entry.
The file entry creation date is the date when the file entry was created.
The expiration date is the expiration date of the DMR-ID of the DBC data stored in the file entry. The expiration date is set for each role (DMR-ID) by the principal user of that DM-ID.
The takeover DMR-ID is a DMR-ID that takes over the information when the DMR-ID of the DBC data stored in the file entry becomes invalid. The takeover DMR-ID is set by the principal user of the DM-ID together with the expiration date for each role (DMR-ID).

AB-F From records the DM-ID of the transfer source DBC frame when the file entry is transferred from another DBC frame. When file entries with the same DMRV-ID are transferred from a plurality of DBC frames, it becomes one file entry, but a plurality of transfer source DM-IDs are recorded in this area.
AB-F To records the DM-ID of the transfer destination DBC frame when transferring the file entry to another DBC frame. The initial value is the default transfer destination of the DBC frame (that is, the AB-F To LST value of Default Value).
AB-F Count can limit the number of transfers to other DBC frames on the side that acquired the DBC data of the entry. The number of times can be set in this area only when the AB-F From area is NULL. When transferred, it is decremented each time it is executed. If the value of this area is 0, no further transfer is performed. The initial value is the default transfer count of the DBC frame (that is, the AB-F CNT value of Default Value).

The priority is a priority set on the user side of the DM-ID when there are a plurality of DMR-IDs in the same DM-ID.
The display order is the priority of the display that can be set on the DBC frame owner (Address Book owner) side when the DBC data of multiple DMR-IDs are received from the same DM-ID partner. It is. The initial value is the same as the aforementioned priority.
The DMR exchange status indicates that the exchange is established with the DMR-ID DBC data, that is, the exchange is established even at the roll level when the exchange is established at the DMRV-ID level (card level). It is assumed that

<Card management data>
A card management number is assigned to each DMRV-ID under the DMR-ID. Each time a new DMRV-ID DBC data is received, a card is added.
DMRV-ID is the DMRV-ID of the DBC data of the card.
The card reception date and time is the date and time when the DBC data of the card is received.
The receipt status is an identifier of whether or not the owner has received the DBC data of the card (approval of receipt).
The date and time of receipt is the date and time when the owner received the DBC data of the card.

MCIE DMRV-ID (MCIE: My Cards In Exchange) is the DMRV-ID of your business card data provided for exchange with respect to the DBC frame of the exchange partner (= the DBC data transfer source side of the card) is there.
The receipt notification reception status is set to “Y” when a receipt notification from the exchange partner is received.
The reception date / time of receipt notification is the date / time when the above-mentioned MCIE is received by the exchange partner side (= the DBC data transfer source side of the card) and the received receipt notification is received in the DBC frame on this side.
If the receipt status is “Y” and the receipt notification reception status is “Y”, the exchange status is set to “Y” and the exchange is considered to be established.

<Card data body (DBC data)>
Business card information is recorded according to the item of vCard which is a unified format. If the SP-side DB is not vCard, the data item conversion TBL is customized and created by the data format conversion means 324 (DBC-SP Translator) installed at the time of SP service participation.

  The business card image image can hold a business card image file designed at the time of business card printing in addition to the business card information.

The personal message number is a management number assigned when storing a message or the like input on the business card exchange partner side. When a message is received a plurality of times with the business card information of the same DMRV-ID, a plurality of management numbers and messages are held in order to register all of the history.
The message reception date and time is the date and time when the message is received.
The message content stores the message body input to the business card information in the carrier record storage area of the business card exchange partner.

The owner memo number is a management number assigned when the DBC frame owner records the visit history and other information as a memo. Multiple memos can be recorded with the same DMRV-ID business card.
The owner memo recording date is the date when the memo was recorded.
The owner memo content is the content of the memo recorded by the DBC frame owner.

(3.2 Structure of each data entry in the carrier record storage area)
Next, each data item in the carrier record storage area will be described with reference to FIG. The carrier record storage area is the same as the address book data storage area, folder management data generated for each DM-ID, file management data generated for each DMR-ID, card management data generated for each DMRV-ID, and And card data such as business card information. As card data, personal card information is stored. Hereinafter, each item name will be described.

<Folder management data>
The meaning of each corresponding item in the address book data storage area is the same.

<File management data>
CR-F From records the DM-ID of the transfer source DBC frame when the file entry is transferred from another DBC frame. When file entries with the same DMRV-ID are transferred from a plurality of DBC frames, it becomes one file entry, but a plurality of transfer source DM-IDs are recorded in this area.
CR-F To records the DM-ID of the transfer destination DBC frame when transferring the file entry to another DBC frame. The initial value is the default transfer destination of the DBC frame (that is, the CR-F To LST value of Default Value).
CR-F Count can limit the number of transfers to other DBC frames on the side that acquired the DBC data of the entry. The number of times can be set in this area only when the CR-F From area is NULL. When transferred, it is decremented each time it is executed. If the value of this area is 0, no further transfer is performed. The initial value is the default transfer count of the DBC frame (that is, CR-F CNT value of Default Value).
The other items of the file management data are the same as the meanings of the corresponding items in the address book data storage area.

<Card management data>
YCIE DMRV-ID (YCIE: Your Cards In Exchange) is the DMRV-ID of the partner's business card data sent for exchange from the DBC frame of the exchange partner (= the recipient's DBC data recipient) It is.
The other items of the card management data are the same as the meanings of the corresponding items in the address book data storage area.

<Card data body (DBC data)>
The business card information of the user (owner) is stored. The meaning of each item is the same as the corresponding item in the address book data storage area.

[4. Management of DBC data receipt status and exchange status]
As described above, an outline of the status necessary for connecting the business card exchange to the address book update in the configuration in which the DBC frame is divided into the address book data storage area and the carrier record storage area will be described with reference to FIG.
The AB-YC area of the address book data storage area (storage area of the exchanged business card information) is provided with a receipt status, and the MCIE area (storage area of the ID of the business card of the self that was presented to the business card exchange partner) A receipt notification reception status and an exchange status are provided. In addition, the CR-MC area (storage area for own business card information) in the carrier record storage area and the YCIE area (storage area for the ID of the partner's business card sent in exchange for own business card) have an exchange status. Is provided.

  In this configuration, when the receipt status of AB-YC is “N”, it means “provisional receipt”, and when “Y”, it means “present acceptance”. Here, provisional receipt means a state in which DBC data of a business card exchange partner is placed in the DBC frame regardless of whether or not the owner is conscious. “Accepted” means that the provisionally received DBC data is officially received after the owner has approved the storage.

  Also, when the reception status of the MCIE receipt notification is “N”, the business card data sent to the exchange partner is provisionally received, and when “Y”, the business card data sent to the exchange partner is received. It means being in a state.

  When the exchange status of MCIE is “N”, both the above reception status and / or the reception notification reception status is “N”, and when “Y”, both the reception status and the reception notification reception status are both Means “Y”.

When the YCIE exchange status of the carrier record storage area is “N”, the exchange status of the address book data storage area is “N”, and when it is “Y”, the exchange status of the address book data storage area is “N”. It means “Y”.
As a series of flag control operations, when the reception status is “Y” (actual reception) and the reception notification reception status is “Y”, the MCIE exchange status is “Y”, and the carrier record storage area YCIE The exchange status becomes “Y”.

[5. Data transfer between business card creator (SP) and business card information management system]
Next, a procedure for keeping the business card information on the business card information management system (DBC service) side in the latest state will be described with reference to FIG.

(5.1 Business Card Identification Information and Business Card Information Conversion Process)
In this figure, first, the business card information of the user is stored in the SP side DB from the service provider side database (SP side DB) to the business card information specifying means 323 (DBCSP ID Manager) installed in the service provider network. Pass along with the management ID number.

Next, DBCSP ID Manager generates DMRV-ID based on the user management ID number and converts the header information. Subsequently, the data format conversion means 324 (DBCSP Translator) converts user card information recorded in a unique format for each SP into a DBC service compatible format (vCard system) and sends it to the DBC service side DB 13.
Then, in the DBC service side DB, the received business card information is stored in the personal information area of the user.

In this way, the DBCSP ID Manager first converts the header information, that is, the management ID number on the SP side to the DMRV-ID that is the management identification number on the business card information management system side, and then converts the DBCSP Translator business card The information format is converted into the vCard format, which is a unified format in the business card information management system.
DBC-SP ID Manager and DBCSP Translator can be provided on either the SP side or the business card information management system side.

  When the DBCSP Translator is provided on the business card information management system side, the format of the business card information may be different for each SP. Therefore, for each SP, the conversion algorithm from the SP side format to a unified format compatible with the DBC service (for example, , A data item correspondence table for format conversion and a logic for performing conversion by referring to the table) are stored in the storage unit 13 of the business card information management system 1, and the SP based on the D-ID of the business card ID is stored. It is good to extract the conversion algorithm of this and to convert a format according to the algorithm.

(5.2 Business card information delivery process)
Next, the timing of delivery of business card information between the SP server 3 and the business card information management system 1 will be described in detail.

  When the business card information management system 1 stores business card information in the user data table (user data storage area) 132, the business card information request unit 124 stores the business card information from the DM-ID corresponding to the user. That is, the SP server 3 is specified, and a business card information transmission request is sent to the SP server 3 together with the user identification information. Upon receiving this request, the SP server 3 transmits the DMRV-ID and business card information generated by the above processing to the business card information management system 1.

  Upon receiving the DMRV-ID and the business card information sent from the SP server 3, the business card information acquisition unit 125 of the business card information management system 1 creates a card entry of the DMRV-ID in the carrier record storage area of the corresponding user. Save business card information.

  On the other hand, when the business card information is changed on the SP server 3 side, the business card information related to the change and the DMRV-ID obtained by incrementing the version (V-ID) are sent to the business card information management system 1. This information is received by the business card information acquisition means 125 and stored in the carrier record storage area of the corresponding user in the same manner as described above. The same applies when an R-ID is added.

  In the above description, the business card information is voluntarily sent from the SP server when there is a change in the business card information. However, the business card information of the SP server may be periodically downloaded from the business card information management system 1 side. Good. In this way, data inconsistency between the SP server and the business card information management system can be avoided.

  At this time, the SP server sends only the latest DMRV-ID information in response to the inquiry from the business card information management system 1, and the business card information management system 1 stores the sent DMRV-ID information. When the latest DMRV-ID information is compared with each other and if they do not match, the DMRV-ID may be specified to request business card information. In this way, the transmission load can be reduced even when communicating with many SP servers.

  Furthermore, as another delivery method when there is a change in the business card information, the number of changes that occurred during the inquiry may be notified. The number of changes in each SP server is counted by the business card information management system 1, and the load is distributed by adjusting the inquiry interval according to the number of changes, for example, shortening the inquiry cycle for an SP server with a high change frequency. be able to.

[6. Business card information exchange process]
Next, the operation of the business card information exchange management unit 126 will be described with reference to FIGS.

(6.1 Business card information request from user A)
FIG. 11 is a flowchart showing a series of processes when the user A scans the DBC code (information code) attached to the business card of the user B obtained by the business card exchange and acquires the business card information of the user B. is there.

  First, the user A scans the DBC code written on the business card of the user B with his / her mobile phone (user terminal) 2 (S101). Examples of screen transitions of the user terminal at this time are shown in FIGS. In FIG. 29 (4), the business card information to be exchanged is designated and the execution key is selected to request the business card information of the other party.

Next, the user A makes a connection request to the business card information management system 1 and a business card information acquisition request through the user terminal 2 (S102).
By this connection request, the terminal communication unit of the business card information management system 1 separates the terminal identification ID and the information acquisition request command (S103), and the mobile identification ID registered in the user information DB 131 of the business card information management system 1 in advance. With reference to the list (mobile identification ID, DM-ID, password correspondence table, etc.), it is determined whether or not the acquired mobile identification ID exists (S104). If the acquired mobile identification ID exists in this list, a login process is executed (S106). On the other hand, if the acquired mobile identification ID does not exist in this list, anonymous processing for unspecified users is executed (S105). In step S103, if an information acquisition request command is included in the received message, the business card information exchange management unit 126 is activated and the subsequent processing is executed.

First, referring to the correspondence table between DM-ID and DBC frame, the DBC frame number is acquired based on DM-ID (S107), and connected to the DBC frame of user A, which is the request source processing unit (S108). ).
Then, it is determined whether or not the folder entry (data storage area) of the DM-ID of the user B exists in the address book data storage area of the user A (S109). If there is no folder entry, the DM-ID of the user B is determined. An ID folder entry is created (S110). In the figure, the DM-ID of user B is displayed as DM-ID (b). Hereinafter, the ID subject is displayed in parentheses in the same manner.

  If "YES" in the step S109, it is next determined whether or not there is a file entry of the user B's DMR-ID in the address book data storage area (S111). If there is no file entry, the user B's DMR is determined. A file entry of -ID is created (S112). If “YES” in the step S111, it is determined whether or not there is a card entry of the user B's DMRV-ID in the address book data storage area (S113). If there is no card entry, the DMRV of the user B is determined. -Create a card entry of ID (S114). Then, DMRV-ID of user A is added as MCIE of the created card entry (S115). Further, DMRV-ID of user B is added as YCIE of DMRV-ID of user A in the carrier record storage area (S116). Thereafter, a request message for business card information is sent to the user B (S117). This request message includes DMRV-ID of user A and business card information of the ID. If “YES” in the step S113, the process after the step S315 in FIG. 14 is executed.

On the other hand, as a process on the DBC frame side of the user B, which is the request destination processing unit shown in FIG. 12, when a request message for the business card information of the user B is received from the user A, the message information is first separated (S201). Then, as in S109 to S114, it is determined whether or not there is an entry (data storage area) of the folder, file, and card of user A in the address book data storage area of user B. If there is no entry, Those entries are created (S202 to S207).
Next, the received business card information of the user A is stored in the business card information storage area of the card entry of the user A's DMRV-ID (S208), and the reception time is recorded (S209). Then, the DMRV-ID of user B is added to the MCIE of the card entry of DMRV-ID of user A (S210), and the DMRV-ID of user A is added to the YCIE of DMRV-ID of user B on the carrier record storage area side. (S211). Thereafter, the business card information of the ID is transmitted to the user A together with the DMRV-ID of the user B (S212).

  On the other hand, as the processing on the DBC frame side of user A shown in FIG. 13, the received business card information of user B is stored in the business card information storage area of the card entry of user B's DMRV-ID (S213). The current time is recorded (S214).

Then, the reception status of the card entry of the user B's DMRV-ID is set to “Y” (S215), and the current time is recorded as the reception date and time of the card entry (S216).
Next, a receipt notice is sent to user B (S217), and business card information is sent to the terminal of user A (S218).
The user A's terminal receives the business card information (S219) and displays it on the terminal display (S220). FIG. 29 (5) is a display example of the acquired business card information. Thereafter, registration in the address book data storage area can be performed as shown in FIG.

On the other hand, as a process on the DBC frame side of the user B, when a receipt notification is received from the user A (S221), the DMRV-ID receipt notification reception status of the user B in the MCIE of the card entry of the user A DMRV-ID is set to “ Y ”(S222), and the current time is recorded in the reception date and time of receipt notification of the user B's DMRV-ID in the MCIE of the card entry of the user A's DMRV-ID (S223).
As described above, business card information is exchanged and receipt notification is exchanged.

(6.2 Business card information request from user B)
Next, with reference to FIG. 14 and FIG. 15, a description will be given of processing when the user B requests a business card information by scanning the DBC code on the business card of the user A after the user A requests the business card information of the user B. To do.

First, in FIG. 14, the DBC code of user A is read by the terminal of user B (S301), and a terminal connection request and an information acquisition request are sent (S302).
When the request information is received in the DBC frame side processing of user B, the message is first separated. (S303) Authentication is performed using the terminal identification ID (S304).
Henceforth, since the process from step S305 to step S314 is the same as the process from step S105 to step S114 of FIG. 11, description is abbreviate | omitted.

  If “YES” in the step S313, the reception status of the card entry of the user A's DMRV-ID is set to “Y” (S315), and the current time is recorded in the reception date and time (S316).

Next, the exchange status of the user B's DMRV-ID in the MCIE of the user A's DMRV-ID card entry is set to "Y" (S317), and the YCIE of the user B's DMRV-ID on the carrier record storage area side is set. The exchange status of the user A's DMRV-ID is set to “Y” (S318).
Then, a receipt notification is sent to the user A (S319), and the business card information of the user A is transmitted to the terminal of the user B (S320). This business card information is received by the terminal of user B (S321) and displayed on the display (S322).

  On the other hand, in the process on the DBC frame side of user A shown in FIG. 15, when the receipt notification from user B is received (S323), the receipt of DMRV-ID of user A in the MCIE of the card entry of DMRV-ID of user B is received. The notification reception status is set to “Y” (S324), and the current time is recorded in the reception notification reception date and time (S325). Then, the exchange status of the user A DMRV-ID in the MCIE of the card entry of the user B DMRV-ID is set to “Y” (S326). Also, the exchange status of the DMRV-ID of user B in the YCIE of DMRV-ID of user A on the carrier record storage area side is set to “Y” (S327).

  The business card exchange process is performed as described above, and the exchange status is managed. When the exchange status becomes “Y”, the address book maintenance unit 127 reflects one business card information update in the address book of the other party.

  Also, the owner can arbitrarily reset the exchange status. By this reset, the exchange status of the other party is also reset, and thereafter, the other party's address book is not updated along with the update of the business card information.

  In addition, FIG. 30 (1)-(3) shows the example of a screen when inputting the business card ID described in the business card manually at the time of requesting business card information in step S101. This makes it possible to receive the provision of this service even in a user terminal that does not have a two-dimensional code reader function.

  Further, it is preferable that business card information can be registered in the address book data storage area by manual input from the user terminal. Examples of screen transitions at this time are shown in FIGS. As a result, it can be widely used as an address book because it can be registered including business card information of users who have not subscribed to this service.

  In steps S301 to S302, the other party also makes a request for acquiring business card information by scanning the business card. A message indicating that the request has been received may be output. In this service, when business card information is requested, the user's own business card information is presented, so a message indicating that new DBC data has arrived is displayed on the partner user terminal. Examples of screen display of the user terminal at this time are shown in FIGS. By confirming this message and selecting an approval key, the user can immediately establish a replacement state (see screen display examples in FIGS. 34 (4) and (5)).

[7. Business card information update process]
Next, the operation of the address book maintenance unit 127 will be described. FIGS. 16 to 19 are flowcharts showing a series of processes when the business card information of the user A is updated and the address book of the user B in the exchange establishment state is updated.

  First, as a process on the business card creator (SP) side of the user A, when the SP system accepts an update of the business card information (S401), the V-ID of the DMR-ID is added (S402). That is, the V-ID that is the version identification number of the previous DMRV-ID is incremented. Then, the updated business card information (hereinafter, updated business card information) and the DMRV-ID are stored in association with each other (S403). Thereafter, the connection request, the updated business card information, and the DMRV-ID are transmitted to the business card information management system (S404). This transmission message includes an SP-ID, a login password, an updated business card information notification command, various parameters (DMRV-ID related to update, business card information), and the like.

  Next, as processing on the DBC frame side of the user A of the business card information management system, the received message is separated (S405), and authentication based on SP-ID is performed (S406). This authentication is performed with reference to a correspondence table of SP login data consisting of SP-ID and password and D-ID. If “NO” in the step S406, an end process is executed (S407). On the other hand, if “YES” in the step S406, a login process is executed (S408). In step S405, if the updated received business card information notification command is included in the separated received message, the address book maintenance unit 127 is activated and the subsequent processing is executed.

  First, referring to the correspondence table between DM-ID and DBC frame, the DBC frame number is obtained from DM-ID (S409), and connected to the DBC frame of user A (S410).

  Then, the presence / absence of the folder entry of the DM-ID of the user A in the carrier record storage area (S411), the presence / absence of the file entry of the DMR-ID (S413), and the presence / absence of the card entry of the DMRV-ID (S415) are respectively determined. If there is no corresponding entry, it is created (S412, S414, S417). If “YES” in the step S415, exception processing is executed (S416).

After step S417, the received updated business card information is stored in the business card information portion of the card entry of the user A's DMRV-ID (S418), and the current time is stored in the reception date and time (S419).
Then, the DMRV-ID in the YCIE of the previous version of the card entry whose exchange status is “Y” is copied to the latest DMRV-ID YCIE (S420), and the copied DMRV The ID exchange status is set to “Y” (S421).

Next, the latest DMRV-ID of user A is added to the MCIE of the card entry in the address book data storage area corresponding to each DMRV-ID stored in YCIE of the carrier record storage area (S422). Then, a business card information update message is sent to each user of all DMRV-IDs stored in YCIE in the carrier record storage area (S423).
This business card information update message includes the DMRV-ID of the user A involved in the update and the business card information.

As processing on the DBC frame side of the user B, when the business card information update message from the user A is received, the message is separated (S501).
Then, the presence or absence of a DM-ID folder entry for user A in the address book data storage area (S502), the presence or absence of a file entry for DMR-ID (S504), and the presence or absence of a card entry for DMRV-ID (S506) are determined. If there is no corresponding entry, it is created (S503, S505, S508). If “YES” in the step S506, exception processing is executed (S507).

After step S508, the received business card information is stored in the business card information portion of the card entry of user A (S509), and the current time is recorded in the card reception date and time (S510).
Then, the DMRV-ID in the MCIE of the previous card entry whose exchange status is “Y” is copied to the MCIE of the latest DMRV-ID (S511), and the copied DMRV The ID reception notification reception status is set to “Y” (S512), and the current time is recorded in the reception notification reception date and time (S513).

Next, DMRV-ID of user A is added to YCIE of DMRV-ID of user B in the carrier record storage area (S514), and the receipt status of the card entry of that DMRV-ID is set to “Y” ( (S515), the current time is recorded in the date and time of receipt of the card entry (S516).
Then, the exchange status of the DMRV-ID in the MCIE of the card entry of the user A's DMRV-ID is set to “Y” (S517), and a receipt notification is sent to the user A (S518).

  On the other hand, as a process on the DBC frame side of the user A, when a receipt notification from the user B is received (S519), a receipt notification reception status of the user A's DMRV-ID in the MCIE of the card entry of the user B's DMRV-ID Is set to “Y” (S520), the current time is recorded in the reception notification reception date and time (S521), and the exchange status is set to “Y” (S522).

  As described above, when the business card information is updated, the business card information of the other party is updated and the exchange status is managed. When there are a plurality of business card exchange partners corresponding to the user B, the processing from step S423 onward is performed for each exchange partner.

[8. Address book data storage area transfer process]
Along with the diversification of individual social activities, one user owns multiple DM-IDs and DBC frames, or corporate users want to share and use a member's address book on a project, department, or company basis and so on. In order to cope with such a case, the data in the address book data storage area and the carrier record storage area can be centrally managed by the business card information transfer means 128 of the business card information management system 1.

The outline of the transfer function will be described below using an address book as an example.
Address book transfer is performed in units of DMR-ID in the address book data storage area, from the address book data storage area of the transfer source DBC frame to the address book data storage area of the transfer destination DBC frame. The entry data is copied.

  At this time, the number of transfers is set on the transfer source side in order to cope with the risk and system load due to infinite transfer.

  In addition, when a DBC frame set to transfer from another address book data storage area changes the DM-ID, the transfer source DB-ID can be notified that the transfer destination DM-ID has changed. In addition, an AB-F From List that is a list of DM-IDs of the transfer source is held.

(Setting by transfer source and approval of transfer destination)
At the transfer source, the default transfer destination is specified in a batch for the DBC frame. After specifying from the transfer source, "Enter the transfer destination DM-ID and password" or "Get approval of the transfer destination user (= Notify by alert display etc. at the next login of the transfer destination user and get OK" The setting is completed.

  The specified DM-ID is the AB-F To LST of the Address Book Forward Info of the Default Value of the forwarding DBC frame and the AB-F From LST of the Address Book Forward Info of the Default Value of the forwarding DBC frame. Registered in

(Setting by transfer destination and approval of transfer source)
This is a request to transfer the address book data to a specific DM-ID.
After specifying the transfer destination to the transfer source, "Enter the transfer source DM-ID and password" or "Get approval of the transfer source user (= Notify by alert display etc. at the next login of the transfer source user, OK" The setting is completed.

  The specified DM-ID is the AB-F Forward From LST of the Address Book Forward Info of the Default Value of the DBC frame of the forwarding destination and the AB-F Forward To LST of the Address Book Forward Info of the Default Value of the forwarding DBC frame. To be recorded.

(Exception setting)
For each DMR-ID unit in the Address Book, you can change the transfer settings to the transfer destination set in the default settings.
Specifically, this can be realized by rewriting the AB-F To area in each file entry. When set as an exception, the specified DM-ID is not transferred to the DBC frame. It is also possible to set a transfer destination for each individual file entry by designating it in the AB-F To area in the individual file entry.

(Startup timing)
This function stores new DMRV-ID data in a new DMR-ID folder when a new DMR-ID data is acquired in the address book data storage area when a transfer destination is newly registered. It is activated when

FIG. 20 shows a conceptual diagram of the transfer operation when updating each entry of the folder, file, and card.
In this figure, first, (1) the information update of the exchange partner is notified to the person's DBC frame, and (2) the address book information on the person's DBC frame is updated. Copy the entry data to the address book. The AB-F CNT value is decremented and registered.

  Next, the procedure for reflecting in the transfer destination Address Book will be described with reference to FIG. In this figure, first, (1) when each entry information in the Address Book is updated, (2) referring to the forwarding destination registered in the AB-F field of the entry, (3) forwarding destination Update data is added to the DBC frame. (4) On the transfer destination Address Book side, the received business card data of the new DMRV-ID is stored in the entry corresponding to the DMR-ID.

  Next, transfer setting processing of the business card information transfer unit 128 will be described with reference to FIGS.

(Address book data storage area transfer setting process)
First, with reference to FIGS. 22 and 23, a process when user A requests user B to approve transfer of business card information of user B and user B approves transfer acceptance will be described.

  First, a connection request with the business card information management system is made from the terminal of user A (S601, S602), and as a process on the DBC frame side of user A, the received message is separated (S603), the mobile identification ID and DM-ID, Authentication with the terminal identification ID is performed with reference to the password correspondence table and the user login data (S604). After authentication, through a login process (S606), a frame number is obtained from the DM-ID by referring to the correspondence table between the DM-ID and the DBC frame (S607).

  Then, the user A is connected to the DBC frame of the user A (S608), the transfer destination DM-ID is designated (S609), and the transfer acceptance approval request message is transmitted to the user B who is the transfer approval destination (S610). This request message is received and stored on the DBC frame side of user B (S611).

  On the other hand, as a process on the DBC frame side of the user B, when the user B transmits a connection request / information acquisition request from the terminal (S701), the request message is sent to the business card information management system, and the message is separated. (S702), authentication by terminal identification ID (S703), login processing is performed (S705), a frame number is acquired from the DM-ID (S706), and connected to the DBC frame of user B. (S707). At this time, the transfer approval request message from user A stored in step S611 is displayed (S708). An example of the screen of user B's terminal at this time is shown in FIGS.

  When an approval input is made from the user B terminal (S709), in the user B DBC frame side processing, the DM-ID of the user A is added to the AB-F From LST of the Address Book Forward Info of the Default Value of the user B DBC frame. Is added (S710), and a transfer acceptance approval message is transmitted (S711).

  This message is received by the user A DBC frame processing routine (S712), and the DM-ID of user B is added to the AB-F To LST of the Address Book Forward Info of the Default Value of the DBC frame of user A (S713). . Then, the DM-ID of the user B is added to the AB-F To of all file entries currently in the address book data storage area (S714), and the folder, file, and card in the address book data storage area are added to the user B. The entry is sent (S715). Then, a setting completion message is transmitted (S716), and a setting completion message is displayed on the terminal of user A (S717).

  On the other hand, in the DBC frame side processing of user B, processing at the time of transfer reception described later is executed (S718).

(Address book data storage area transfer process)
The transfer process of the address book data storage area after the transfer setting as described above will be described with reference to FIG.

  First, in the DBC frame processing of the user A who is the transfer source, when business card information acquisition or information update processing is performed and a new card entry is acquired (S801), all DBCs having DM-IDs in the AB-F To field exist. The acquired card entry is sent to the frame (S802). At this time, if the card entry to be transferred is a new file entry, the value of AB-F CNT is decremented and sent. This business card information update message includes the DMRV-ID of the user B who is the card entry person to be transferred, the card entry data thereof, the value of the decremented AB-F CNT in the case of file transmission, and the like.

  On the other hand, when this message is received in the DBC frame processing of user B as the transfer destination, the message is separated (S803), and whether or not the folder entry of the user B DM-ID exists in the address book data storage area is determined. If it does not exist, a folder entry is created (S805). Next, it is determined whether or not the file entry of the user B's DMR-ID exists (S806). If it does not exist, the file entry of the user B is created (S807), and the AB-F From field is created. The transfer source DMRV-ID is recorded (S808).

Further, it is determined whether or not the card entry of the user B exists in the address book data storage area (S809), and if not, the card entry is created (S810). Then, the received business card information of the user B's DMRV-ID is stored in the business card information portion of the user B's card entry (S811), and the current time is recorded in the card reception date and time (S812). In step S809, if “YES”, exception processing is executed (S813).
As described above, the transfer process is performed.

(Transfer setting processing and transfer processing in the carrier record storage area)
The flowchart of the carrier record storage area transfer setting process is shown in FIGS. 25 and 26, and the flowchart of the transfer process is shown in FIG.

Except that the transfer target is data in the carrier record storage area, it is basically the same as the processing in FIGS.
In the above description of the transfer process, the approval request is sent to the transfer destination. However, it is also possible to obtain the transfer source approval by inputting the DM-ID that the transfer destination wants to accept the transfer. An example of a screen display of the transfer destination user terminal at this time is shown in FIGS.

  Further, at the time of transfer approval, each entry may be excluded from transfer targets. Examples of user terminal screens at this time are shown in FIGS.

[9. Local address book linkage function]
A linkage function between DBC data and a local address book of a personal computer or mobile phone may be provided.
In order to realize this function, first, the business card information management system 1 stores the model of the user terminal 2 and the address book data format of the terminal in association with each other.
Then, an address book data cooperation request is input from the user terminal 2. Examples of screen display on the user terminal at this time are shown in FIGS.

The business card information management system 1 determines the model from the terminal identification information, converts it into an address book data format corresponding to the model, and transmits it to the user terminal 2 through the output means 129. Note that the terminal identification information is sufficient if the model can be determined. For example, the model may be determined based on the manufacturing number sent from the terminal.
In this way, for example, the user does not need to recognize the data format of a mobile phone address book or the like, and does not need to input the mobile phone model each time, thereby improving convenience.

[10. Business card creation function]
FIG. 33 shows an example of a business card ordering screen displayed on the terminal. In this figure, first, a business card pattern is selected, then input data is confirmed and corrected, and then order information is input and an order request is transmitted.

At this time, on the screen of FIG. 33 (2), in addition to the business card information, when there is a request for business card information from a business card exchange partner, operation control information such as whether or not the exchange is established unconditionally is also displayed. Thus, the design of the business card may be made changeable based on the information.
By including operation control information in the business card ID and including it on the business card, the business card owner can grasp what kind of operation control is performed from the design of the business card, so the range of utilization is expanded.

  In addition to the above, as the operation control information, personal information can be stored in addition to the business card information, and whether or not the personal information is provided to the other party may be used as the operation control information.

  Further, an operation pattern table may be provided so that the above-described operation control information items can be selected. For example, when pattern 1 is selected, if there is a request for acquiring business card information together with a DBC code from the partner who exchanged the business card, the business card exchange is accepted unconditionally. When pattern 2 is selected, an alert screen as shown in FIG. 28 is displayed to confirm acceptance. Note that it is effective to set whether or not to provide a business card image when the DBC code is not scanned as an operation pattern.

  Instead of printing the entire business card image, an information code sticker may be printed. Since the information code can be output basically with only the business card ID, the information code sticker can be printed and pasted on the existing business card.

  According to the present embodiment, since a business card with an information code is used, it is possible to perform a simple procedure / operation when exchanging business card information on a server after exchanging business cards, and smooth update processing of the address book. Can be done. In addition, since the personal information (name, work place, address, etc.) itself described on the business card itself is not coded, the size of the information code can be small, and the limited space on the business card is occupied by the information code. Can be avoided.

  Furthermore, since the identification information of the business card creator is included in the business card ID, the business card information of each user who creates business cards with a plurality of different business card creators can be acquired, and can be centrally managed as address book information. In addition, since the business card ID is written on the business card in a coded state, it is basically necessary to exchange the business card in order to obtain another person's business card ID. Can be prevented from leaking. It should be noted that it is possible to eliminate the need for permission for providing business card information to the partner who exchanged the business card, and the burden on the user can be reduced.

  Since the business card information is managed separately in the carrier record storage area and the address book data storage area in the user data storage area of the business card information management system, the address book data can be managed easily while ensuring security. If the address book data is encrypted and stored with the business card ID or the terminal identification information of the user, the security during data storage can be enhanced. Also, if the terminal authentication is automatically performed when communication between the terminal and the system is established, and the address book data corresponding to the terminal identification information is started when the authentication is OK, the user can Since the decryption process can be executed while the business card information transmission request process is performed by inputting the ID and password, the response performance of the system can be improved.

  Furthermore, in this embodiment, the structure of the carrier record storage area is divided into folders for each user in the DM-ID unit that is a database for creating a business card and user identification information, and in the folder, in units of roles. Since a file is created and a card (name card information) is inserted for each version of the name card in the file, it becomes easy to manage the update of the name card.

  Moreover, according to this Embodiment, asynchronous business card exchange on a network can be performed smoothly. By the exchange status flag processing, the partner to be updated can be appropriately managed, and when the business card information of the partner is updated, the address book of the partner can be surely updated. Furthermore, by separating the address book data and carrier record storage areas, it is possible to manage a personal address book consisting of data stored in the address book data storage area with high security.

  In particular, the address book data storage area can be personalized as data for user management, and the carrier record storage area can be personalized as data for management of a person (company etc.) who manages business card information. By giving different management authority, it is possible to prevent data tampering by those without management authority. In addition, it is possible to manage such that only business card information that has undergone the company approval process is stored in the carrier record storage area.

  Further, in addition to the management authority, the access level may be settable. For example, level 1 can be written and read, level 2 can only be read, and so on. As a result, the address book data storage area can be flexibly operated, such as allowing the administrator only to read. For example, the sales representative scans the business card of the person who has met and records the business card information of the other party as the actual visit (= start of business negotiations). It is also possible to manage sales representative activities by viewing the date and time of receipt of information.

  Further, according to the present embodiment, since the business card information is automatically updated, the customer list in the exchange establishment state is always kept up-to-date, so that it can also be used as a CRM (information cooperation platform regarding customers). In addition, it is possible to quickly identify a person whose information has been updated and send a congratulatory letter without searching for a newspaper or the like when there is a personnel change.

  In addition, as another example of the two-dimensional DBC code written on the business card, the DBC code attached to the business card and the DMRV-ID described therebelow are simply changed in encoding or encryption, The information itself may be changed. For example, for the DBC code, in addition to the DMRV-ID information, information such as keywords set by the user is added. As a result, it is possible to determine whether the card has been scanned from a business card or by manual input. Furthermore, even if a DMRV-ID is obtained illegally, security can be maintained by changing the operation with the two-dimensional DBC code. When reading the DBC code with the scanner function, save the information indicating that it was read with the scanner at the same time, and when you request business card information, send that information together, It is possible to easily distinguish between scanning and manual input.

  Further, the D-ID may be provided for each manager who manages the business card information, instead of the business card creator database. Then, the administrator can access the business card information in the carrier record storage area in the D-ID. For example, if the other party's DMRV-ID in a folder within the same D-ID is made available, the administrator can also obtain the other party's business card information based on the DMRV-ID. The manager of the employee can know the information of the partner whom the employee has met in the work.

  This is because the other party who gave you the business-related business card specifies the business card ID (DMRV-ID) attached to the business card and makes a request to obtain business card information. By making it available to the public, the administrator can know the status of the work activities of the employees, while the address book data storage area is managed by another access authority, so the confidentiality of so-called personal activity information can be obtained. Can be secured.

  Further, as an application example of the present embodiment, it is possible to search for a connection between users using a business card exchange history (or transfer information). For example, it is possible to search for a connection with a person who has a specific technique or personality as personal information. If you can select the category information and save it in association with the category information when you save the business card information, you can know which category linkage is effective for your activity, and in a specific direction It can be used for the formation of human relations.

In the present embodiment, the DBC code is described on the business card. However, the DBC code may be described on things other than the business card, such as a general document, a telephone directory, and an advertisement. As a result, the reader can easily obtain business card information, so that the connection of human relations on the network can be promoted.
In addition, since the accumulation of personal card information in the carrier record storage area becomes personal history information, it can also be used as a resume.

Furthermore, it can be used for Biz Connect (a mechanism for introducing people) using the connection function. In particular, according to the present embodiment, the latest information can be introduced, and the relationship can be maintained by a message transmission mechanism. It is also possible to follow the connections (Prime Minister, President, etc.) and enjoy the number of times. As a method of tracing, there are a method of tracing from a transfer function and a method of tracing from a business card exchange record / history. Thereby, the motivation of the formation of human relations can be increased.
Moreover, by registering business card information in a plurality of languages in the carrier record storage area, business card information in a language that cannot be posted on the business card can be distributed.

Note that this embodiment can also be used as address information for other purposes, such as New Year's cards. At this time, it is easy to update the information by coordinating with the address writing software, writing the address two-dimensional code on the New Year's card, and reading and registering it.
It can also be used as a mechanism for distributing public keys via electronic authentication and encrypted communication (easier to use than LDAP).

It is a functional block diagram of the business card information management system concerning this Embodiment, the user terminal connected with this system through a communication network, and the server of a business card creator. It is a functional block diagram of SP server of FIG. It is explanatory drawing of the DBC service concerning embodiment of this invention. It is a block diagram of business card ID concerning embodiment of this invention. It is a conceptual diagram of a DBC frame. It is explanatory drawing of a structure of the user data storage area | region of FIG. It is explanatory drawing of the data stored in an address book data storage area and a carrier record storage area. It is explanatory drawing of each data item of an address book data storage area. It is explanatory drawing of each data item of a carrier record storage area. It is explanatory drawing of operation | movement of the business card information specific | specification means and data format conversion means of FIG. It is a flowchart for demonstrating the process procedure by the side of the request source (user A) of the request source (user A) when the entry of the request destination user of the business card information exchange management means of FIG. 1 does not exist. It is a flowchart for demonstrating the process procedure by the side of the request destination (user B) of the request destination (user B) when the entry of the request destination user of the business card information exchange management means of FIG. 1 does not exist. It is a flowchart for demonstrating the process procedure by the side of the DBC frame of the user A when the business card information of the user B when the entry of the request destination user of the business card information exchange management means of FIG. 1 does not exist is sent. 7 is a flowchart for explaining a processing procedure on the DBC frame side of user B when there is an entry of a request destination user of the business card information exchange management means of FIG. It is a flowchart for demonstrating the process sequence by the side of the DBC frame of the user A when the entry of the request destination user of the business card information exchange management means of FIG. 1 exists. It is a flowchart for demonstrating the process procedure by the side of the DBC frame of the update source (user A) of the business card information of the address book maintenance means of FIG. FIG. 17 is a continuation flowchart of FIG. 16 for explaining the processing procedure on the DBC frame side of the business card information update source (user A) of the address book maintenance means of FIG. 1; 6 is a flowchart for explaining a processing procedure on the DBC frame side of an update target (user B) of the address book maintenance unit of FIG. 1. FIG. 19 is a flowchart continued from FIG. 18 for explaining the processing procedure on the DBC frame side of the update target (user B) of the address book maintenance unit of FIG. 1; It is a conceptual diagram of the transfer operation | movement at the time of the data entry update by embodiment of this invention. It is explanatory drawing of the procedure of reflection to the transfer destination Address Book at the time of the data entry update by embodiment of this invention. It is a flowchart for demonstrating the transfer setting process sequence of the address book data storage area by embodiment of this invention. FIG. 24 is a flowchart continued from FIG. 22 for describing the transfer setting processing procedure of the address book data storage area according to the embodiment of the present invention; It is a flowchart for demonstrating the transfer processing procedure of the address book data storage area by embodiment of this invention. It is a flowchart for demonstrating the transfer setting processing procedure of the carrier record preservation | save area by embodiment of this invention. FIG. 26 is a continuation flowchart of FIG. 25 for describing the transfer setting processing procedure of the carrier record storage area according to the embodiment of the present invention. It is a flowchart for demonstrating the transfer processing procedure of the carrier record preservation | save area by embodiment of this invention. It is an example of a display screen of a caution message when a business card exchange request according to an embodiment of the present invention is received. It is a screen transition figure of a user terminal when scanning an information code and requesting business card information. It is a screen transition diagram of the user terminal when manually entering a business card ID and requesting business card information. It is a screen transition figure of a user terminal when inputting business card information manually. It is a screen transition diagram of a user terminal when cooperating with a local address book of a mobile phone. It is a screen transition diagram of a user terminal when ordering a business card. It is a screen transition diagram of the user terminal when a request for business card information is received in the business card information exchange process. In the transfer process by embodiment of this invention, it is a screen transition figure of the user terminal at the time of transfer acceptance designation | designated. It is a screen transition figure of a user terminal when approving a transfer request in transfer processing by an embodiment of the invention. It is explanatory drawing of the business card with which the information code by embodiment of this invention was described.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Business card information management system 2, 2A, 2B User terminal 3 SP server 4 Communication network 5 Business card 6 Information code 11, 21, 31 Transmission / reception part 12, 22, 32 Central processing part 13, 33 Storage part 24 Input part 25 Display part 121, 321 Transmission / reception processing means 122 Basic information registration means 123 Terminal communication means 124 Business card information request means 125 Business card information acquisition means 126 Business card information exchange management means 127 Address book maintenance means 128 Business card information transfer means 129 Output means 131 User information DB
132 User data storage area (DB)
133 SP DB
322 Request information input means 323 Business card information identification means 324 Data format conversion means 325 Business card information transmission means 331 Business card information DB
332 ID management DB

Claims (16)

A business card information management system for inputting business card information and storing it as address book information,
The address book data storage area where the business card information of the partner who exchanged the business card and the business card ID of the business card that was sent to the partner for exchange are stored in association with each other, and the business card information and its business card A user record storage area having a carrier record storage area in which the business card ID of the other party submitted for exchange is stored in association with each other,
Address book maintenance means for updating own business card information in the user data storage area of the update target user and updating the own business card information in the user data storage area when updating the own business card information;
Output means for outputting business card information in the user data storage area;
A business card information management system characterized by comprising:   2. The business card information management system according to claim 1, wherein the address book data storage area and the carrier record storage area are configured such that different access authorities can be set. The address book data storage area includes a reception status indicating that the business card provided by the other party has been received, and a reception notification reception status indicating that the business card provided by the partner has been received,
The said address book data storage area and the said carrier record storage area are each provided with the exchange status which is set based on the said both status, and represents the business card exchange establishment state, respectively. Business card information management system. The information-coded business card ID written on the business card includes operation control information capable of changing the operation of the business card information management system,
4. When a user requesting business card information makes a business card information acquisition request based on a business card ID including the operation control information, the user operates according to the operation control information included in the business card ID. Business card information management system described. A request source processing unit and a request destination processing unit for managing an exchange state between the request source user and the request destination user with respect to exchange of business card information;
The request source processing unit sends a business card information acquisition request including the business card information of the request source user and the business card ID of the request destination user to the request destination processing unit,
Upon receiving the business card information acquisition request, the request destination processing unit stores the business card information of the request source user in the user data storage area of the request destination user and corresponds to the business card ID stored in the user data storage area Business card information to be extracted and sent to the request source processing unit,
When the request source processing unit receives the business card information of the request destination user, the request source processing unit stores it in the user data storage area of the request source user and sets a reception status flag of the business card information and sends a receipt notification to the request destination processing unit. ,
Upon receiving the receipt notification, the request destination processing unit sets a receipt notification reception status flag in the user data storage area of the request destination user,
Thereafter, when a requesting user's business card information acquisition request is transmitted from the requesting user terminal, the requesting destination processing unit has the requesting user's business card information already in the user data storage area of the requesting user. Set the receiving status flag of the requesting user on the condition, and set the exchange status flag, send a receipt notification to the request source processing unit,
4. The business card information according to claim 3, wherein the request source processing unit comprises business card information exchange management means for setting a receipt notification reception status flag and setting an exchange status flag when receiving the receipt notification. Management system. For each business card creator, one or more business card information conversion algorithms for converting the business card format of the business card creator into a unified format,
A business card information acquisition means for receiving the business card information and the business card ID sent from the server of the business card creator;
Means for selecting a business card information conversion algorithm to be used, using information included in the business card ID;
Using this selected business card information conversion algorithm, the business card information received by the business card information acquisition means is converted into a unified format and stored in the carrier record storage area of the user data storage area corresponding to the business card ID Conversion means;
The business card information management system according to any one of claims 1 to 5, further comprising: The user data storage area includes user data storage area identification information of the transfer source and transfer destination of business card information stored in the address book data storage area and / or the carrier record storage area, and a transfer allowable number of times,
Based on the user data storage area identification information, business card information is transferred within the allowable transfer count, and the transfer count can be controlled only by the original owner of the address book data and / or carrier record. The business card information management system according to claim 1, further comprising a transfer unit.   8. The business card information management system according to claim 7, wherein the business card information transfer means determines whether or not transfer can be executed based on attribute information of a transfer destination user. Means for associating and storing the terminal model and the address book data format of the terminal;
Means for inputting identification information of the user terminal;
Means for extracting the terminal model based on the input identification information of the user terminal, converting the address book data of the user into the address book data format of the user terminal, and transmitting to the user terminal;
The business card information management system according to any one of claims 1 to 8, further comprising: Business card information sent from the server of one or more business card makers to the electronic business card manager's server, stored as address book information, and sent to the user terminal A management method,
For each business card creator, storing one or more business card information conversion algorithms for converting the business card manufacturer's business card format into a unified format;
Selecting a business card information conversion algorithm to be used, using information included in the business card ID;
The business card information sent from the server of the business card creator is received, the received business card information is converted into a unified format using the selected business card information conversion algorithm, and stored in the user data storage area corresponding to the business card ID Saving step;
Inputting the business card ID read from the business card sent from the user terminal;
Extracting the corresponding business card information from the user data storage area corresponding to the business card ID and storing it in the address book data storage area of the user data storage area associated with the user terminal;
Transmitting information stored in the address book data storage area to the user terminal;
A business card information management method comprising: Obtaining business card information update information on the server of the business card creator;
Obtaining a business card ID and business card information related to the update when the business card information is updated;
Converting business card information into a unified format and storing it in a carrier record storage area of a user data storage area associated with the business card ID;
Extracting a business card ID in a business card exchange state associated with the business card ID in the carrier record storage area;
Updating the business card information in the address book data storage area of the business card ID in the exchange state;
The business card information management method according to claim 10, further comprising:   The business card information is encrypted and stored using the business card ID of the user who owns the business card information or information associated therewith, and a communication connection with the user terminal is established when the business card information is read. Then, authentication is performed using the terminal identification information, and then decryption processing of the business card information stored in the user address book storage area corresponding to the terminal identification information is started. The business card information management method according to claim 10 or 11, wherein the business card information that has been processed is transmitted to the user terminal.   A business card used in the business card information management method according to any one of claims 10 to 12, comprising at least a business card creator identification information, user identification information, and information capable of identifying the business card information of the business card creator. A business card characterized by an information code.   14. The business card according to claim 13, wherein the information code includes an encrypted business card ID and non-encrypted business card information management service information. A business card information management program for inputting business card data sent from a server of one or more business card creators, storing it as address book information and transmitting the address book information to a user terminal,
For each business card creator, a process of storing one or more business card information conversion algorithms for converting the business card format of the business card creator into a unified format of the business card information management system;
Using the information included in the business card ID, selecting the business card information conversion algorithm to be used,
The business card information sent from the server of the business card creator is received, the received business card information is converted into a unified format using the selected business card information conversion algorithm, and stored in the user data storage area corresponding to the business card ID Processing to save,
A process of inputting the business card ID read from the business card sent from the user terminal;
Processing for extracting corresponding business card information from the user data storage area corresponding to the business card ID and storing it in the address book data storage area of the user data storage area associated with the user terminal;
A process of transmitting business card information stored in the address book data storage area to the user terminal;
A program that causes a computer to execute. A program for a user terminal that reads an information code written on a business card according to claim 14 and transmits an acquisition request for business card information to a server of an electronic business card manager,
A process of extracting a business card ID from the information code;
Processing for adding address information for transmission to the server to the extracted business card ID;
Processing for displaying the address information and business card ID on the screen of the user terminal;
A program for causing a computer to execute a process of transmitting an acquisition request for business card information including the business card ID to the server by confirmation input.