Source: https://patents.google.com/patent/US20030014487A1/en
Timestamp: 2019-09-21 16:51:10
Document Index: 582960995

Matched Legal Cases: ['art, 502', 'art, 503', 'art, 504', 'art, 512', 'art 501', 'art 502', 'art 503', 'art 511', 'art 513', 'art 512', 'art 504', 'art 505', 'art 110', 'art 120', 'art 210', 'art 121', 'art 122', 'art 121', 'art 110', 'art 122', 'art 210', 'art 220', 'art 211', 'art 212', 'art 210', 'art 213', 'art 210', 'art 214', 'art 215', 'art 210', 'art 210', 'art 120', 'art 211', 'art 212', 'art 211', 'art 220', 'art 211', 'art 220', 'art 220', 'art 310', 'art 320', 'art 311', 'art 310', 'art 312', 'art 313', 'art 312', 'art 313', 'art 220', 'art 110', 'art 120', 'art 120', 'art 122', 'art 211', 'art 211', 'art 211', 'art 212', 'art 213', 'art 311', 'art 213', 'art 311', 'art 220', 'art 320', 'art 310', 'art 312', 'art 313', 'art 215', 'art 122', 'art 330', 'art 210', 'art 330', 'art 340', 'art 122', 'art 122', 'art 330', 'art 320', 'art 330', 'art 340', 'art 122', 'art 320', 'art 122', 'art 310', 'art 312', 'art 313', 'art 340', 'art 340', 'art 340', 'art 350', 'art 330', 'art 340', 'art 360', 'art 313', 'art 215', 'art 123', 'art 120', 'art 123', 'art 221', 'art 220', 'art 221', 'art 320', 'art 321', 'art 330', 'art 331', 'art 321', 'art 221', 'art 331', 'art 123', 'art 340', 'art 340', 'art 340', 'art 350', 'art 350', 'art 340']

US20030014487A1 - Introduction system - Google Patents
Introduction system Download PDF
US20030014487A1
US20030014487A1 US09/995,815 US99581501A US2003014487A1 US 20030014487 A1 US20030014487 A1 US 20030014487A1 US 99581501 A US99581501 A US 99581501A US 2003014487 A1 US2003014487 A1 US 2003014487A1
US09/995,815
2001-07-16 Priority to JP2001-215759 priority Critical
2001-07-16 Priority to JP2001215759A priority patent/JP4804663B2/en
2001-11-29 Assigned to FUJITSU LIMITED reassignment FUJITSU LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: IWAKAWA, AKINORI, OKUYAMA, SATOSHI
2003-01-16 Publication of US20030014487A1 publication Critical patent/US20030014487A1/en
The present invention relates to an introduction system for allowing an introduction origin system to introduce an introduction target system to an introduction destination system through an on-line network system. [0002]
With the widespread use of the Internet, communications are being actively conducted through an on-line network system. In order to conduct smooth communications, a system using a user list, in particular, a buddy list system is being used on a worldwide basis. A buddy list system is used for supporting communications with a partner side system, displaying the state of a partner side system, and the like. [0004]
In the case where a buddy list system is used for supporting communications with a partner side system, user entry information on a partner side system with which communications are conducted often is previously registered on a list called a buddy list, and user entry information on a partner side system is selected from the buddy list when communications are conducted, whereby a partner side system can easily be specified. The current buddy list system is generally used in instant message delivery service for delivering a simple message, and the like. There is no particular limit to the communication means of the delivery service, and various means such as a telephone and electronic mail can be used. [0005]
In the case where the buddy list system is used for displaying the state of a partner side system, if user entry information on a partner side system from which a state display is desired to be obtained is previously registered to a buddy list, state information is displayed in a predetermined region on a computer display screen, which represents the state of a registered partner side system at all times or at a predetermined timing. Thus, the state of a partner side system can be displayed, which represents whether or not the partner side system is in operation, whether or not an event has occurred in the partner side system, and the like. Furthermore, by synchronizing the buddy list system with an entry/exit system, the state representing whether or not a user of a partner side system is in meeting or on the business trip can be displayed. [0006]
FIG. 23 is a view showing a conventional configuration of a buddy list system configured between users A and B. In FIG. 23, reference numeral [0007] 500 denotes a system used by the user A, 501 denotes a buddy list registering part, 502 denotes a buddy list storing part, 503 denotes a registration information notifying part, 504 denotes a state information receiving part, and 505 denotes a state information display part. Furthermore, reference numeral 510 denotes a system used by the user B, 511 denotes a registration information receiving part, 512 denotes a state information generating part, and 513 denotes a state information notifying part.
A flow of a basic operation of the above-mentioned buddy list system is as follows. First, the user A specifies and inputs user entry information of the user B with respect to the buddy list registering part [0008] 501. The buddy list registering part 501 registers a user to a buddy list in the buddy list storing part 502. The registration information notifying part 503 notifies a user system 510 of the user B of registration information containing identifier information of a user system 500. The user system 510 receives the registration information at the registration information receiving part 511. Herein, the user system 510 has a function of notifying the user system 500 of its own state at a predetermined timing or in the case where there is a change in its state information. More specifically, the state information notifying part 513 sends state information generated by the state information generating part 512 to the user system 500, based on the identifier information of the user system 500 contained in the registration information. The user system 500 of the user A receives the state information at the state information receiving part 504, and displays the state information by the state information display part 505. In the above description, the state information is sent from a system registered to the buddy list to a registering system, using a so-called “push” technique. However, the state information may be sent from a registering system to a registered system, using a so-called “pull” technique.
As described above, in the buddy list system, a user who desires to register a system of another user to a buddy list specifies a partner to be registered by using an identifier assigned to each user system. The buddy list system generally has a function of detecting an actual position of a user system on a network from its identifier by using known means such as a domain name system (DNS), and sending/receiving required information to the detected user system, and a user system on a registering side automatically obtains state information of a user system on a registered side. [0009]
The buddy list system as described above is important to a service provider conducting commercial activities. More specifically, if user entry information on a service provider is registered to a buddy list in a user system, the state regarding the provision of service can be displayed on a customer system, which is useful for presentation. Furthermore, due to the communication support function of the buddy list system, when a user desires to use service, a service provider becomes more likely to allow the user to use its service. As a result, the service provider has the advantage over the other providers. [0010]
The above-mentioned buddy list system is considered to be an important technique to a service provider in terms of sales strategy. More specifically, if a service provider has its user entry information registered to a buddy list in a user system, its advertising information and the like can be provided as a state display using the buddy list, and communications with a user become active. As a result, the service provider has the advantage over the other providers. Herein, there is a problem of how a service provider has its user entry information registered to a buddy list in a user system. [0011]
JP 2000-364371 A discloses an effective technique of giving a user an incentive to register user entry information of a service provider to a buddy list of a user. According to this technique, a user registers user entry information on a service provider to a buddy list and notifies the service provider of the registration, whereby the service provider notified of the registration issues coupons regarding the provision of service to the user. Issuance of coupons attracts users, so that registration of the service provider to a buddy list can be expected to some degree. [0012]
However, according to the technique of JP 2000-364371 A, it is required that a user finds a service provider that actively issues coupons, obtains user entry information on the service provider, registers the user entry information on the service provider to a buddy list, and notifies the service provider of the registration of the user entry information. If such time and labor involved in these operations can be reduced, the registration to a buddy list is expected to be promoted. [0013]
Furthermore, although issuance of coupons is attractive to a user, a user is not sure about whether or not the service provider issuing coupons is reliable, and the quality of service provided by the service provider is good. Therefore, a user hesitates to register all the service providers issuing coupons to a buddy list. If this psychological anxiety can be reduced, the registration to a buddy list is expected to be promoted. [0014]
In general commercial activities, a goods sales promoting method and a service use promoting method are known, in which when a service user introduces another user to a service provider, the service provider gives an incentive (e.g., payback) to an introducing user or an introduced user. According to this method, the introduced user can confirm the reliability of the service provider and the excellence of the quality of service provided by the service provider through the introducing user. Therefore, smooth sales of goods and provision of service, combined with personal reliability of the introducing user, are promoted. [0015]
However, the above-mentioned goods sales promotion method and service use promotion method have the following drawbacks. Generally, an incentive is given based on introduction when an introduced user determines to use service or when at least planned use of service is confirmed. Therefore, psychological pressure for the introduced user to use service is high, and if the desire of the introduced user for use of service is not high enough, the incentive providing method is unlikely to be used. [0016]
In order to overcome the above-mentioned problem, the following may also be possible: at a time of introduction, sales of goods and provision of service are not conducted immediately, and an incentive is given when a user actually utilizes service later. However, according to this method, there is a strong possibility that, with the passage of time after introduction, the impression of an introduced user with respect to introduced service may become weak, and the introduced user may forget user entry information for accessing a service provider. In order to call attention of a user, it is also possible to regularly send direct mail. However, some users may have a bad impression on such direct mail, which may have the opposite effect. [0017]
Therefore, with the foregoing in mind, it is an object of the present invention to support the registration of a user on a user list. In particular, it is an object of the present invention to reduce time and labor involved in registration of a service provider into a buddy list system, enhance reliability of the service provider through introduction of another user, and promote the registration of a service provider to a buddy list system. [0018]
In order to achieve the above-mentioned object, the introduction system of the present invention allows an introduction origin system to introduce an introduction target system to an introduction destination system through an on-line network system, wherein the introduction origin system includes an introducing part for notifying the introduction destination system of “introducing” information containing user entry information of the introduction target system, the introduction destination system includes a registering part for receiving the “introducing” information notified from the introducing part of the introduction origin system and registering user entry information of the introduction target system on a user list, and an “introduced” information notifying part for detecting registration of the user entry information of the introduction target system on the user list in the registering part and notifying the introduction target system of “introduced” information representing that a registration action based on introduction has been conducted, and the introduction target system includes an “introduced” recognizing part for receiving “introduced” information from the “introduced” information notifying part of the introduction destination system and recognizing a registration action to the user list in the introduction destination system. [0019]
Because of the above-mentioned configuration, the introduction target system can recognize that an “introducing” action from the introduction origin system to the introduction destination system and a registration action to a user list have been conducted. [0020]
It is preferable that the user list is a buddy list, and a buddy list system is configured between the introduction destination system and the introduction target system, based on registration of a user entry of the introduction target system to the buddy list of the introduction destination system, the introduction target system notifies the introduction destination system of state information representing a state of the introduction target system through a network, and the introduction destination system obtains the state information of the introduction target system through the network and refers to it. [0021]
Because of the above-mentioned configuration, the introduction system of the present invention can be applied to a buddy list system. [0022]
Herein, the state information refers to information representing the state of a partner side system or a user, for example, information represented by an icon or a message. The state of a partner side system and the state of a user representing that the user is on the business trip or the like can be grasped by referring to the state information. [0023]
It is preferable that, in the above-mentioned introduction origin system, the introducing part has a function of notifying the introduction target system that an “introducing” action has been conducted, and the introduction target system further includes an “introducing” recognizing part for receiving “introducing” information notified from the introducing part of the introduction origin system and recognizing the “introducing” action in the introduction origin system based on the “introducing” information, and an “introduction” confirming part for comparing contents recognized by the “introduced” recognizing part with contents recognized by the “introducing” recognizing part, and confirming an introduction relationship between the introduction origin system and the introduction destination system. [0024]
Because of the above-mentioned configuration, the introduction target system receives so-called self-declaration of an “introducing” action from the introduction origin system, and compares the contents of the “introducing” action with the contents of a registration action notified from the introduction destination system, thereby confirming the “introducing” action. [0025]
It is preferable that, in order to provide an incentive, the introduction target system is a service provider, and the introduction target system includes an incentive providing part for giving an incentive to change conditions for providing service with respect to either one or both of the introduction origin system and the introduction destination system, in a case where the “introduced” recognizing part recognizes an introduction relationship between the introduction origin system and the introduction destination system. [0026]
It is preferable that, in order to provide an incentive, the introduction target system is a service provider, and the introduction target system includes an incentive providing part for giving an incentive to change conditions for providing service with respect to either one or both of the introduction origin system and the introduction destination system, in a case where the “introduction” confirming part confirms an introduction relationship between the introduction origin system and the introduction destination system. [0027]
Because of the above-mentioned configuration, an incentive can be given to an introduction origin system or an introduction destination system in which an “introducing” action and a registration action have been recognized and confirmed, whereby registration to a buddy list of the introduction target system can be promoted. [0028]
It is also preferable that the introduction target system includes an incentive notifying part for notifying the introduction origin system or the introduction destination system of contents of an incentive given by the incentive providing part based on a past “introducing” action and registration action or contents of an incentive to be provided by the incentive providing part based a future introduction relationship. [0029]
This is because it is possible to grasp to which degree an incentive is currently given or to which degree an incentive will be given if an “introducing” action and a registration action is conducted, whereby an “introducing” action and a registration action can be promoted. [0030]
It is preferable that, in a registering part of the introduction destination system, in a case where the entry information of the introduction target system is deleted from the user list or the introduction destination system is not used by a user any more, the introduction relationship between the introduction origin system and the introduction target system is cancelled. [0031]
This is because the introduction relationship can be considered to be cancelled. [0032]
These and other advantages of the present invention will become apparent to those skilled in the art upon reading and understanding the following detailed description with reference to the accompanying figures.[0033]
FIG. 1 is a view showing a schematic configuration of an introduction system of Embodiment 1 according to the present invention. [0034]
FIG. 2 is a view showing an example of “introducing” information generated in an introduction origin system. [0035]
FIG. 3 is a view showing an example of “introduced” information generated in an introduction destination system. [0036]
FIG. 4 is a view showing an example of “introduced” recognition information generated in an introduction target system. [0037]
FIG. 5 is a view showing an exemplary configuration of an exchange server. [0038]
FIG. 6 is a flow chart showing “introducing” processing in an introduction origin system. [0039]
FIG. 7 is a flow chart showing registration processing in an introduction destination system. [0040]
FIG. 8 is a flow chart showing registration recognition processing in an introduction target system. [0041]
FIG. 9 is a view showing an example of a display screen of a buddy list. [0042]
FIG. 10 is a view illustrating an “introducing” operation using a buddy list. [0043]
FIG. 11 is a view showing an example of a selection screen for whether or not “introducing” information is registered. [0044]
FIG. 12 is a view showing a schematic configuration of an introduction system of Embodiment 2 according to the present invention. [0045]
FIG. 13 is a view showing an example of “introducing” information generated in an introduction origin system. [0046]
FIG. 14 is a flow chart showing “introducing” processing in an introduction origin system. [0047]
FIG. 15 is a flow chart showing registration recognition processing and registration confirmation processing in an introduction target system. [0048]
FIG. 16 is a view showing a schematic configuration of an introduction system of Embodiment 3 according to the present invention. [0049]
FIG. 17 is a view showing another schematic configuration of the introduction system of Embodiment 3 according to the present invention. [0050]
FIG. 18 is a view showing a configuration in the case of presenting the contents of an incentive in Embodiment 3 according to the present invention. [0051]
FIG. 19 is a view showing a schematic configuration of an introduction system of Embodiment 4 according to the present invention. [0052]
FIG. 20 shows update processing of an introduction relationship by an “introduction” confirming part. [0053]
FIG. 21 shows update confirmation processing of an introduction relationship by an “introduction” confirming part. [0054]
FIG. 22 shows examples of a recording medium storing a processing program for realizing an introduction system of Embodiment 5 according to the present invention. [0055]
FIG. 23 is a view showing a configuration of a conventional buddy list system.[0056]
An introduction system of the present invention will be described by way of embodiments. In the following description of the embodiments of the introduction system according to the present invention, a buddy list is used as a user list, and a buddy list system is configured between an introduction destination system and an introduction target system. [0057]
“Introducing” information refers to information for an introduction origin system to notify an introduction destination system or an introduction target system of the contents of an “introducing” action, when the “introducing” action is conducted. The “introducing” information contains information specifying an introduction origin system and an introduction destination system or an introduction target system. [0058]
“Introduced” information refers to information for an introduction destination system to notify an introduction target system that the introduction destination system has received introduction, when receiving “introducing” information from the introduction origin system. The “introduced” information contains information specifying an introduction origin system, an introduction destination system, and an introduction target system. [0059]
In an introduction system of Embodiment 1 according to the present invention, an introduction origin system introduces an introduction target system to an introduction destination system through an on-line network system. Introduction may be conducted on the basis of service provided by the introduction target system. Introduction is conducted in such a manner that user entry information of the introduction target system is registered on a user list of the introduction destination system. For example, an identifier is assigned to service of the introduction target system, and the introduction origin system notifies the introduction destination system of user entry information containing identifier information of the introduction target system, and the user entry information is registered as a user on a user list of the introduction destination system. [0060]
In a buddy list system described in the present embodiment, the introduction destination system sends registration information containing its identifier information to the introduction target system when adding a new user entry to its buddy list. Furthermore, state information of the introduction target system is sent to the introduction destination system by a “push” technology from the introduction target system to the introduction destination system. The introduction system of the present embodiment is also applicable even if the introduction destination system does not send its identifier information to the introduction target system when adding a new user entry to the buddy list of the introduction destination system, and state information of the introduction target system is sent to the introduction destination system by a “pull” technology from the introduction destination system to the introduction target system. [0061]
FIG. 1 is a view showing a schematic configuration of the introduction system of Embodiment 1 according to the present invention. [0062]
Reference numeral [0063] 100 denotes an introduction origin system, 200 denotes an introduction destination system, and 300 denotes an introduction target system. Herein, it is assumed that an identifier is assigned to each system, and an identifier of the introduction origin system 100 is “A”, an identifier of the introduction destination system 200 is “B”, and an identifier of the introduction target system 300 is “C”.
The introduction origin system [0064] 100 includes a buddy list managing part 110 and an introducing part 120.
The buddy list managing part [0065] 110 stores and manages a buddy list of the introduction origin system 100. Although not shown in FIG. 1, in order to display state information using the buddy list and the like, the introduction origin system 100 may also have the same configuration as that of a buddy list managing part 210 of the introduction destination system 200.
The introducing part [0066] 120 includes an “introducing” information generating part 121 and an “introducing” information notifying part 122. Upon detecting an operation instruction of introducing a user (introduction target system 300) to another user (introduction destination system 200) on the buddy list in an operation by a user A of the introduction origin system 100, the “introducing” information generating part 121 extracts user entry information that becomes an introduction target from the buddy list managing part 110 and generates “introducing” information. The “introducing” information to be generated is, for example, as shown in FIG. 2. This example includes items such as identifier information of an introduction origin system, identifier information of an introduction destination system, identifier information of an introduction target system, and other information. In this example, the respective items are provided with item values “A”, “B”, “C”, and “introduction date and time”.
The introducing part [0067] 120 notifies the introduction destination system 200 of the generated “introducing” information through the “introducing” information notifying part 122.
The introduction destination system [0068] 200 includes a buddy list managing part 210 and an “introduced” information notifying part 220.
The buddy list managing part [0069] 210 includes a buddy list registering part 211 and a buddy list storing part 212, and stores and manages the buddy list of the introduction destination system 200. The buddy list managing part 210 also includes a registration information notifying part 213, and sends registration information containing its identifier information to the introduction target system 300 that is a partner side system, when new user entry information is added to the buddy list. The buddy list managing part 210 also includes a state information receiving part 214 and a state information display part 215, and upon being notified of state information from the introduction target system 300, the buddy list managing part 210 displays the state of the introduction target system 300 based on the state information, as described later.
The buddy list managing part [0070] 210 may also have a communication support function with respect to a system registered to the buddy list. In the case where a user of the introduction destination system 200 desires to communicate with the introduction target system 300, the buddy list managing part 210 supports formation of a communication path to the introduction target system 300 by selecting a user entry of the introduction target system 300 displayed on the buddy list.
The buddy list registering part [0071] 211 receives “introducing” information notified from the introducing part 120 of the introduction origin system 100. Although not shown in FIG. 1, the buddy list registering part 211 may include a registration selection function. The purpose of this is to give discretion in selecting whether or not an entry of an introduced user is registered to the buddy list. The registration selection function has a function of presenting a selection dialog for asking whether or not a user introduced to a user B is registered and a function of accepting the selection instruction. In the case where the user B selects registration, user entry information of the introduction target system is extracted from the received “introducing” information, and registered to the buddy list of the buddy list storing part 212. As a result, the introduction target system 300is registered to the buddy list of the introduction destination system as a user. When the registration of the user entry information of the introduction target system 300 to the buddy list is completed, the buddy list registering part 211 notifies the “introduced” information notifying part 220 of the completion of the registration.
Upon being notified of the completion of the registration of the user entry information of the introduction target system [0072] 300 to the buddy list from the buddy list registering part 211, the “introduced” information notifying part 220 generates “introduced” information. The “introduced” information is, for example, as shown in FIG. 3. This example includes four items: identifier information of an introduction origin system, identifier information of an introduction destination system, identifier information of an introduction target system, and other information. In this example, the respective items are provided with item values “A”, “B”, “C”, and “introduction date and time”. Although the items in this example are the same as those of the “introducing” information shown in FIG. 2, they are not necessarily required to be the same. The “introduced” information notifying part 220 notifies the introduction target system 300 of the generated “introduced” information.
The introduction target system [0073] 300 includes a buddy list control part 310 and an “introduced” recognizing part 320.
The buddy list control part [0074] 310 includes a registration information receiving part 311, which receives registration information notified from the introduction destination system 200 and extracts identifier information “B” of the introduction destination system 200. Furthermore, the buddy list control part 310 includes a state information generating part 312 and a state information notifying part 313. The state information generating part 312 generates state information, and the state information notifying part 313 sends the state information to the introduction destination system 200 based on the identifier “B” of the introduction destination system 200.
The “introduced” recognizing part [0075] 320 receives “introduced” information notified from the “introduced” information notifying part 220 of the introduction destination system 200, and generates “introduced” recognition information from the received “introduced” information. The “introduced” recognition information to be generated is, for example, as shown in FIG. 4. This example includes three items: identifier information of an introduction origin system, identifier information of an introduction destination system, and other information. The respective items are provided with item values “A”, “B”, and “introduction date and time”.
The “introduced” recognizing part [0076] 320 stores the generated “introduced” recognition information.
Thus, the introduction origin system [0077] 100 introduces the introduction target system 300 to the introduction destination system200, and the introduction target system 300 recognizes that it has been registered as a user to the buddy list of the introduction destination system 200.
In the configuration shown in FIG. 1, the respective terminals are directly connected to each other. However, in actual operation, communications are conducted by obtaining an address of a system to be a communication partner on a network, based on identifier information. In Embodiment 1, it is assumed that communications are conducted via an information exchange server. [0078]
FIG. 5 shows an exemplary configuration of an exchange server [0079] 400. The exchange server 400 manages an identifier of each user system, and its position (e.g., an IP address and a port number) on the network. When information in which an identifier of a user system to be a destination is written in a particular part (e.g., a header part of leading 20 bytes) is sent to the exchange server 400, the contents of information are transferred to the introduction destination system according to the IP address and the port number registered as information on a destination. It is assumed that the position of the exchange server 400 on the network is managed by a name, for example, based on the DNS, and each user system is uniquely determined.
If the exchange server [0080] 400 is used as described above, information can be transferred among the respective user systems. The description of transfer of information is omitted here.
Next, a processing flow of the introduction system of Embodiment 1 according to the present invention will be described in detail by illustrating specific examples. [0081]
The processing flow of the introduction system is shown by flow charts in FIGS. [0082] 6 to 8.
(1) “Introducing” Processing in the Introduction Origin System [0083] 100 (FIG. 6)
The user A of the introduction origin system [0084] 100 inputs an “introducing” operation (Operation 601). For example, although not shown in FIG. 1, the buddy list managing part 110 includes a buddy list display function, and the buddy list is displayed on a display screen as shown in FIG. 9. In this example, “Iwakawa”, “Sano”, and “Supermarket α” are registered as users to the buddy list. In the following description, “Okuyama” who is a user of the introduction origin system 100 introduces the user “Supermarket α” on the buddy list to the user “Iwakawa”. More specifically, in this case, the user of the introduction origin system 100 is “Okuyama”, the user of the introduction destination system 200 is “Iwakawa”, and the use entity of the introduction target system 300 is “Supermarket α”.
In the above example, it is assumed that a user can conduct an “introducing” operation by using a user interface on the buddy list with respect to the introducing part [0085] 120. For example, the user conducts an “introducing” operation as shown in FIG. 10, using the buddy list display screen shown in FIG. 9. More specifically, the user “Okuyama” of the introduction origin system 100 drags an icon of “Supermarket α” on the buddy list and drops it on an icon of “Iwakawa” on the buddy list. By providing such a user interface, an “introducing” operation becomes simple, and the effect of promoting an “introducing” action can be expected.
Next, “introducing” information is generated by the “introducing” information generating part [0086] 121 based on the “introducing” operation (Operation 602). The introducing part 120 of the introduction origin system 100 always monitors the operation with respect to the buddy list. When the above-mentioned “introducing” operation is conducted, the introducing part 120 detects the operation and generates the “introducing” information shown in FIG. 2.
As identifier information of the introduction origin system [0087] 100, i.e., identifier information of the user “Okuyama”, “A” is set; as identifier information of the introduction destination system 200, i.e., identifier information of the user “Iwakawa”, “B” is set; and as identifier information of the introduction target system 300, i.e., identifier information of the user “Supermarket α”, “C” is set.
Then, the introduction origin system [0088] 100 that is the user system of “Okuyama” notifies the introduction destination system 200 that is the user system of “Iwakawa” of “introducing” information through the “introducing” information notifying part 122 (Operation 603).
After notification processing (Operation [0089] 603) of the “introducing” information in the introduction origin system 100, registration processing starts in the introduction destination system 200.
(2) Registration Processing in the Introduction Destination System [0090] 200 (FIG. 7)
The introduction destination system [0091] 200 is notified of the “introducing” information from the introduction origin system 100 (Operation 603), and starts registration processing.
The buddy list managing part [0092] 210 of the introduction destination system 200 that is the user system of “Iwakawa” receives the “introducing” information notified from the introduction origin system 100, and passes it to the buddy list registering part 211 (Operation 701).
Next, the introduction destination system [0093] 200 of “Iwakawa” displays in the buddy list registering part 211 that the user “Supermarket α” is introduced by the user “Okuyama” as shown in FIG. 11, and a selection dialog for selecting whether or not the user “Supermarket α” is registered in the buddy list (Operation 702).
When the user “Iwakawa” of the introduction destination system [0094] 200 selects “Registration” (Operation 703: Y), the buddy list registering part 211 registers the user “Supermarket α” that is the introduction target system 300 on the buddy list in the buddy list storing part 212 (Operation 704).
In the case where the user “Supermarket α” that is the introduction target system [0095] 300 is registered to the buddy list, the introduction destination system 200 sends registration information containing the identifier “B” to the user “Supermarket α” that is the introduction target system 300 through the registration information notifying part 213 (Operation 705). The registration information is received by the registration information receiving part 311 in the introduction target system 300.
The “introduced” information notifying part [0096] 220 generates “introduced” information as shown in FIG. 3, and notifies the user “Supermarket α” that is the introduction target system 300 of the “introduced” information (Operation 706).
After the notification processing of the “introduced” information in the introduction destination system [0097] 200 (Operation 706), registration recognition processing is started in the introduction target system 300. Herein, although the order of Operations 705 and 706 are as described above for convenience, it may be changed, or these operations may be conducted in parallel.
When the user “Iwakawa” of the introduction destination system [0098] 200 selects “Non-Registration” (Operation 703: N), Operations 704 to 706 are not conducted, and registration processing in the introduction destination system 200 is completed. Furthermore, the registration recognition processing is not started in the introduction target system 300, and the processing of the introduction system is completed.
(3) Registration Processing in the Introduction Target System [0099] 300 (FIG. 8)
The user “Supermarket α” that is the introduction target system [0100] 300 is notified of the “introduced” information of the introduction destination system 200 (Operation 706), and starts the following registration processing.
The buddy list control part [0101] 310 of the introduction target system 300 receives registration information notified from the registration information notifying part 213 of the introduction destination system 200 through the registration information receiving part 311 (Operation 801), extracts the identifier “B” of the introduction destination system 200 from the registration information, and registers the introduction destination system as a system to be notified of state information (Operation 802).
The “introduced” recognizing part [0102] 320 receives the “introduced” information notified from the “introduced” information notifying part 220 of the introduction destination system 200 (Operation 803). The “introduced” recognizing part 320 generates “introduced” recognition information in the form of a table in which the identifier information of the introduction origin system 100 contained in the received “introduced” information is associated with the identifier information of the introduction destination system 200, as shown in FIG. 4, and stores the generated “introduced” recognition information (Operation 804).
After the above-mentioned registration processing (Operations [0103] 801 to 804), the buddy list control part 310 of the introduction target system 300 notifies the introduction destination system 200 of state information generated by the state information generating part 312 at a predetermined timing through the state information notifying part 313, based on the identifier of the registered introduction destination system 200 (Operation 805).
(4) State Display Processing of the Introduction Target System [0104] 300 in the Introduction Destination System 200, and Communication Support Processing from the Introduction Destination System 200 to the Introduction Target System 300
Upon being notified of the state information from the introduction destination system [0105] 200, the state information display part 215 of the introduction destination system 200 displays the state of the introduction target system 300 based on the state information.
The processing flow of the introduction system of Embodiment 1 mainly based on the “introducing” processing and the “introduced” recognition processing is as described above. [0106]
In the case where, in the introduction destination system [0107] 200 that is notified of the state information and displays it, a user desires to communicate with the introduction target system 300, it is preferable that the user can receive support for formation of a communication path to the introduction target system 300 by selecting a user entry of the introduction target system 300 displayed on the buddy list.
Due to the above-mentioned series of operations, the user “Supermarket α” of the introduction target system [0108] 300 refers to the “introduced” recognition information, thereby recognizing that the user “Okuyama” of the introduction origin system 100 has introduced the “Supermarket α” to the user “Iwakawa” of the introduction destination system 200, and the user entry information of the “Supermarket α” has been registered in the buddy list system of the user system “Iwakawa”.
An introduction system of Embodiment 2 according to the present invention is obtained by modifying the introduction system of Embodiment 1, and is provided with a function of confirming whether or not an “introducing” action has been conducted. As a method for confirming an introduction relationship representing who is an introducer and who is an introduced person, various methods can be considered. Herein, the simplest example will be shown. More specifically, the “introducing” information representing the relationship between an introduction origin system and an introduction destination system obtained from the introduction origin system is compared with the “introduced” information representing the relationship between the introduction origin system and the introduction destination system obtained from the introduction destination system, and it is determined if there is matching therebetween, whereby the introduction relationship is confirmed. [0109]
The introduction system of Embodiment 2 according to the present invention conducts the “introducing” processing in the introduction origin system, the registration processing in the introduction destination system, and the registration processing and the “introduced” recognition processing in the introduction target system, in the same way as in Embodiment 1. In addition to these, the introduction system of Embodiment 2 conducts “introducing” information notification processing in the introduction origin system with respect to the introduction target system and “introducing” recognition processing and introduction confirmation processing in the introduction target system. In the same way as in Embodiment 1, introduction may be conducted on the basis of service provided by the introduction target system. [0110]
FIG. 12 shows a schematic configuration of the introduction system of Embodiment 2 according to the present invention. [0111]
Reference numeral [0112] 100 a denotes an introduction origin system, 200 a denotes an introduction destination system, and 300 a denotes an introduction target system. In the same way as in Embodiment
[0113] 1, the identifier of the introduction origin system 100 is “A”, the identifier of the introduction destination system 200 is “B”, and the identifier of the introduction target system 300 is “C”.
The introduction origin system [0114] 100 a has the same configuration as that of the introduction origin system 100 in FIG. 1. However, in Embodiment 2, the “introducing” information notifying part 122 notifies an “introducing” recognizing part 330 of the introduction target system 300 a of “introducing” information as well as the buddy list managing part 210 of the introduction destination system 200 a of “introducing” information. Herein, the “introducing” information may be, for example, the same as that in Embodiment 1 shown in FIG. 2.
Next, the introduction destination system [0115] 200 a may have the same configuration as that of the introduction destination system 200 in Embodiment 1 shown in FIG. 1.
Compared with the configuration of the introduction target system [0116] 300 of Embodiment 1, the introduction target system 300 a further includes the “introducing” recognizing part 330 and an “introduction” confirming part 340.
The “introducing” recognizing part [0117] 330 receives “introducing” information notified from the “introducing” information notifying part 122 of the introduction origin system 100 a, and recognizes an “introducing” action in the introduction origin system 100 a based on the “introducing” information.
The “introducing” recognizing part [0118] 330 receives “introducing” information notified from the “introducing” information notifying part 122 of the introduction origin system 100 a, and generates “introducing” recognition information from the received “introducing” information. The “introducing” recognition information to be generated is, for example, as shown in FIG. 13. This example includes three items: identifier information of an introduction origin system, identifier information of an introduction destination system, and other information (herein, introduction date and time). In this example, the respective items are provided with item values “A”, “B”, and “2001.07.03”. The “introducing” recognizing part 330 stores the generated “introducing” recognition information.
The “introduction” confirming part [0119] 340 compares the contents of a registration act in the introduction destination system 200 a shown by the “introduced” recognition information recognized by the “introduced” recognizing part 320 with the contents of an “introducing” action in the introduction origin system 100 a shown by the “introducing” recognition information recognized by the “introducing” recognizing part 330, thereby confirming matching therebetween. More specifically, in the case where the contents of the registration act are matched with those of the “introducing” action, the “introducing” action between the introduction origin system 100 a and the introduction destination system 200 a, and the registration act with respect to the buddy list conducted by accepting introduction are confirmed. The “introduction” confirming part 340 stores the results of introduction confirmation.
A processing flow of the introduction system of Embodiment 2 is shown by flow charts in FIGS. 14 and 15. In this example, a user of the introduction origin system [0120] 100 a is “Okuyama”, a user of the introduction destination system 200 a is “Iwakawa”, and a use entity of the introduction target system 300 a is “Supermarket α”, and the user “Okuyama” of the introduction origin system 100 introduces the user “Supermarket α” on the buddy list to the user “Iwakawa”.
(1) “Introducing” Processing in the Introduction Origin System [0121] 100 a (FIG. 14)
The processing operations from Operations [0122] 1401 to 1403 are the same as the input processing of an “introducing” operation by the user “Okuyama” of the introduction origin system 100 a (Operation 601), the generation processing of “introducing” information (Operation 602), and the notification processing of the “introducing” information with respect to the introduction destination system 200 a (Operation 603) shown in the flow chart of FIG. 6. The detailed description thereof will be omitted here.
After the notification processing of the “introducing” information in the introduction origin system [0123] 100 a (Operation 1403), the introduction destination system 200 a starts the registration processing upon being notified of the “introducing” information.
In the introduction system of Embodiment 2, after the notification processing of the “introducing” information with respect to the introduction destination system [0124] 200 a (Operation 1403), the notification processing of “introducing” information with respect to the introduction target system 300 a is conducted in the introduction origin system 100 a. More specifically, the “introducing” information notifying part 122 notifies the introduction target system 300 a of the “introducing” information (Operation 1404).
The introduction target system [0125] 300 a starts the “introducing” recognition processing upon being notified of the “introducing” information in the introduction origin system 100 a.
In the above-mentioned example, although the notification processing of the “introducing” information with respect to the introduction target system [0126] 300 a (Operation 1404) is conducted after Operation 1403, the notification processing of the “introducing” information with respect to the introduction target system 300 a may be conducted in parallel with the notification processing of the “introducing” information with respect to the introduction destination system 200 a (Operation 1403).
(2) Registration Processing in the Introduction Destination System [0127] 200 a
Upon being notified of the “introducing” information of the introduction origin system [0128] 100 a (Operation 1403), the introduction destination system 200 a starts registration processing.
The registration processing is the same as that (FIG. 7) in the introduction destination system [0129] 200 in Embodiment 1, and the description thereof will be omitted here.
(3) Registration Processing and “Introduced” Recognition Processing, “Introducing” Recognition Processing, Introduction Confirmation Processing in the Introduction Target System [0130] 300 a (FIG. 15)
The introduction target system [0131] 300 a is subjected to the registration information notification processing (Operation 705) and the “introduced” information notification processing (Operation 706) from the introduction destination system 200 a, and starts registration processing and “introduced” recognition processing.
Furthermore, the introduction target system [0132] 300 a is notified of “introducing” information (Operation 1404) from the introduction origin system 100 a, and starts “introducing” recognition processing.
Furthermore, the introduction target system [0133] 300 a receives the results of the registration recognition processing and the “introducing” recognition processing, and starts introduction confirmation processing.
The registration recognition processing is the same as that (FIG. 8) in the introduction target system [0134] 300 in Embodiment 1. Therefore, the detailed description thereof will be omitted here. Receiving processing of the registration information of the introduction destination system 200 a (Operation 1501), registration processing of the state information notification destination system (Operation 1502), receiving processing of the “introduced” information (Operation 1503), and generation/storing processing of the “introduced” recognition information (Operation 1504) correspond to Operations 801 to 804 in FIG. 8. As a result of the registration recognition processing, the “introduced” recognizing part 320 stores the “introduced” recognition information shown in FIG. 4.
The “introducing” recognition processing is conducted in the following flow. [0135]
First, the “introducing” recognizing part [0136] 330 of the introduction target system 300 a receives “introducing” information from the “introducing” information notifying part 122 of the introduction origin system 100 a (Operation 1505).
The “introducing” recognizing part [0137] 330 generates and stores “introducing” recognition information as shown in FIG. 13, in the form of a table in which the identifier information of the introduction origin system 100 a contained in the received “introducing” information is associated with the identifier information of the introduction destination system 200 a (Operation 1506).
The introduction confirmation processing is conducted in the following flow. [0138]
First, the “introduction” confirming part [0139] 340 receives “introduced” recognition information obtained as the results of the “introduced” recognition processing in Operations 1503 and 1504 and “introducing” recognition information obtained as the results of the “introducing” recognition processing in Operations 1505 and 1506, and compares the contents of the “introduced” recognition information with those of the “introducing” recognition information (Operation 1507).
In the case where the contents of the “introduced” recognition information are matched with those of the “introducing” recognition information, the introduction confirmation processing succeeds. As a result, the “introduction” confirming part [0140] 340 can confirm the introduction relationship between the introduction origin system 100 a and the introduction destination system 200 a.
In the case where the contents of the “introduced” recognition information are not matched with those of the “introducing” recognition information, the introduction confirmation processing fails. As a result, the “introduction” confirming part [0141] 340 cannot confirm the introduction relationship between the introduction origin system 100 a and the introduction destination system 200 a.
The “introduction” confirming part [0142] 340 stores the introduction confirmation results thus obtained (Operation 1508).
After the above-mentioned processing (Operations [0143] 1501 to 1508), the buddy list control part 310 of the introduction target system 300 a notifies the introduction destination system 200 a of the state information generated by the state information generating part 312 through the state information notifying part 313 at a predetermined timing, based on the registered identifier of the introduction destination system 200 a (Operation 1509).
The state display processing of the introduction target system [0144] 300 a in the introduction destination system 200 a and the communication support processing from the introduction destination system 200 a to the introduction target system 300 a are the same as those in Embodiment 1. Therefore, the description thereof will be omitted here.
The processing flow of the introduction system of Embodiment 2 mainly based on the “introducing” processing, the “introduced” recognition processing, the “introducing” recognition processing, and the introduction confirmation processing is as described above. [0145]
It is also possible to present the introduction confirmation results in the “introduction” confirming part [0146] 340 to a user. For example, a shopkeeper of the use entity “Supermarket α” of the introduction target system specifies the identifier information of the user “Okuyama” of the introduction origin and the identifier information of the user “Iwakawa” of the introduction destination, of which introduction relationship the shopkeeper desires to confirm, for example, by inputting a character string on a user interface of a terminal. The “introduction” confirming part 340 receives notification from the user interface, searches for the introduction confirmation results, and checks whether or not the user “Iwakawa” has been registered as the introduction destination of the user “Okuyama”. In the case where the introduction relationship is not confirmed, the “introduction” confirming part 340 displays that confirmation of the introduction relationship has failed. In the case where the introduction relationship is confirmed, the “introduction” confirming part 340 displays that confirmation of the introduction relationship has succeeded.
In an introduction system of Embodiment 3, it is assumed that a use entity of an introduction target system is a service provider providing some service and goods, and a user of an introduction origin system and a user of an introduction destination system are customers of the service provider. In this introduction system, a user is given an incentive to register user entry information of the service provider to a buddy list of the user, whereby configuration of an introduction relationship is promoted. [0147]
FIG. 16 is a view showing a schematic configuration of the introduction system of Embodiment 3 according to the present invention. [0148]
FIG. 16 shows a configuration in which an incentive providing part [0149] 350 is added to the configuration in Embodiment 1 shown in FIG. 1. Reference numeral 100 b denotes an introduction origin system, 200 b denotes an introduction destination system, and 300 b denotes an introduction target system. The introduction target system 300 b further includes the incentive providing part 350, compared with the configuration of the introduction target system 300 in FIG. 1.
The incentive providing part [0150] 350 determines and gives an incentive such as a reduction in a service use fee or the like with respect to either one or both of the introduction origin system 100 b and the introduction destination system 200 b, in the case where the “introducing” recognizing part 330 recognizes an “introducing” action and a registration action between the introduction origin system 100 b and the introduction destination system 200 b.
FIG. 17 shows another schematic configuration of the introduction system of Embodiment 3 according to the present invention. FIG. 17 shows a configuration in which an incentive providing part [0151] 350 is added to the configuration in Embodiment 2 shown in FIG. 12. Reference numeral 100 c denotes an introduction origin system, 200 c denotes an introduction destination system, and 300 c denotes an introduction target system.
The incentive providing part [0152] 350 determines and gives an incentive such as a reduction in a service use fee or the like with respect to either one or both of the introduction origin system 100 c and the introduction destination system 200 c, in the case where the “introduction” confirming part 340 confirms an “introducing” action and a registration action between the introduction origin system 100 c and the introduction destination system 200 c.
For example, the following can be assumed as an incentive: all goods are discounted by 5% with respect to an introducing user (a user of the introduction origin system [0153] 100 b or 100 c) or all goods are discounted by 5% with respect to an introduced user (a user of the introduction destination system 200 b or 200 c). By giving such an incentive, a service user can be motivated to introduce a new user.
The introduction system of the present invention can also present the contents of an incentive given based on the past “introducing” action and registration action or the contents of an incentive to be provided based on the future “introducing” action and registration action with respect to the introduction origin system and the introduction destination system. [0154]
FIG. 18 shows a configuration in the case of presenting the contents of an incentive. An introduction target system [0155] 300 d is provided with an incentive information notifying part 360.
The incentive information notifying part [0156] 360 generates display information regarding the contents of an incentive given based on the past “introducing” action and registration action or the contents of an incentive to be provided based on the future “introducing” action and registration action, and gives the display information to the state information notifying part 313.
The state information notifying part [0157] 313 notifies an introduction destination system 200 d of display information regarding the contents of an incentive as one state information. In the introduction destination system 200 d, information regarding the contents of an incentive is displayed as one state display of the introduction target system 300 through the state information display part 215. Thus, the incentive information is notified to the introduction destination system as a state display of a buddy list system. For example, “now, all goods are discounted by 5% for you”, “if you introduce a new customer, all goods are discounted by 7% for you”, and the like are displayed.
Incentive information may be displayed with respect to the introduction origin system [0158] 100 d in the same way.
Incentive information may be sent when a user refers to presence information of service or when a service provider changes incentive information. In the former case, identifier information of a user attempting to refer to presence information is obtained, and incentive information corresponding to the user is obtained. These pieces of information are converted into character strings, and displayed on a user's buddy list screen as presence information. [0159]
In an introduction system of Embodiment 4, in the case where an introduction relationship between an introduction origin system and an introduction destination system is cancelled, recognition or confirmation of an “introducing” action and a registration action between the introduction origin system and the introduction destination system is invalidated to cancel an incentive. Herein, the case where the introduction relationship between the introduction origin system and the introduction destination system is cancelled corresponds to the case where entry information of an introduction target system is deleted from a buddy list in the introduction destination system and the case where the introduction destination system itself is not used any more (e.g., a terminal is abandoned). It should be noted that even in the case where these situations occur in the introduction origin system and a combination of these situations occurs, an embodiment similar to the present embodiment can be used. [0160]
FIG. 19 shows a schematic configuration of an introduction system of Embodiment 4 according to the present invention. [0161]
An introduction origin system [0162] 100 e includes an “introducing” update information notifying part 123 in an introducing part 120 e. The “introducing” update information notifying part 123 generates “introducing” update information representing that the “introducing” action of the introduction origin system 100 e is effective at a predetermined update timing, and notifies the introduction target system 300 e of the “introducing” update information.
An introduction destination system [0163] 200 e includes an “introduced” update information notifying part 221 in an “introduced” information notifying part 220 e. The “introduced” update information notifying part 221 generates “introduced” update information representing that the registration action of the introduction destination system 200 e having received introduction is effective, i.e., that user entry information of the introduction target system 300 e is registered to a buddy list, and a state display and the like are conducted, at a predetermined update timing, and notifies the introduction target system 300 e of the “introduced” update information.
In the introduction target system [0164] 300 e, an “introduced” recognizing part 320 e includes an “introduced” update recognizing part 321, and an “introducing” recognizing part 330 e includes an “introducing” update recognizing part 331. The “introduced” update recognizing part 321 recognizes “introduced” update information notified from the “introduced” update information notifying part 221 of the introduction destination system 200 e, and the “introducing” update recognizing part 331 recognizes “introducing” update information notified from the “introducing” update information notifying part 123 of the introduction origin system 100 e. An “introduction” confirming part 340 e confirms that the introduction relationship is effective.
The “introduction” confirming part [0165] 340 e has an “introducing” update parameter and an “introduced” update parameter. The “introduction” confirming part 340 e updates the “introducing” update parameter, upon being notified of the “introducing” update information from the introduction origin system 100 e. Similarly, the “introduction” confirming part 340 e updates the “introduced” update parameter, upon being notified of “introduced” update information from the introduction destination system 200 e.
FIG. 20 shows an example of update processing of an introduction relationship based on the “introducing” update information and the “introduced” update information by the “introduction” confirming part [0166] 340 e. In the following example, it is assumed that the base value of the “introducing” update parameter and the “introduced” update parameter is “2”, the value is updated to “2” by update processing, and the value is decreased by “1” every time the update confirmation processing described later is conducted. According to this configuration, if the “introducing” update parameter and the “introduced” update parameter are not updated by the time when the update confirmation processing is conducted twice continuously, the value of the update parameter becomes “0”.
First, the “introduction” confirming part [0167] 340 e receives “introducing” update information or “introduced” update information (Operation 2001).
The “introduction” confirming part [0168] 340 e checks the value of the “introducing” update parameter or the “introduced” update parameter. In this example, it is checked whether or not the value is “2” (Operation 2002), and if the value is “2” (Operation 2002: Y), it is determined that update has already been completed, and update processing is completed.
If the value of the “introducing” update parameter or the “introduced” update parameter is not “2” (Operation [0169] 2002: N), it is checked whether or not the value is “1” (Operation 2003). If the value is “1” (Operation 2003: Y), the value is updated to “2” (Operation 2004). After the value is updated, update processing is completed.
If the value of the “introducing” update parameter or the “introduced” update parameter is not “1” (Operation [0170] 2003: N), update processing is completed.
The update confirmation processing of the introduction relationship in FIG. 21 is conducted in the following procedure. [0171]
The “introduction” confirming part [0172] 340 e checks the value of the “introducing” update parameter and the “introduced” update parameter at a predetermined timing (e.g., 12:00 a.m. once per day) (Operation 2101: Y). In the case where the value of the “introducing” update parameter or the “introduced” update parameter is “2” (Operation 2102: Y), it is determined that confirmation of the introduction relationship succeeds, and the parameter value is decreased by “1” (Operation 2103). In the case where the value of the “introducing” update parameter or the “introduced” update parameter is not “2” (Operation 2102: N) but “1” (Operation 2104: Y), it is determined that confirmation of the introduction relationship has succeeded, and the parameter value is decreased by “1” (Operation 2105). In the case where the “introducing” update parameter or the “introduced” update parameter is not “1” (Operation 2104: N) but “0”, it is determined that the update confirmation of the introduction relationship has failed (Operation 2106), and the update confirmation of the introduction relationship is not conducted.
The case where the confirmation of the introduction relationship has failed corresponds to the case where “introducing” update information or “introduced” update information cannot be notified or received from the introduction origin system [0173] 100 e or the introduction destination system 200 e, and while the “introducing” update parameter and the “introduced” update parameter are not updated to “2”, first update confirmation is conducted at a predetermined timing to decrease the value by “1”, and the second update confirmation is further conducted.
In the above-mentioned example, the base value of the “introducing” update parameter and the “introduced” update parameter is set at “2”, and when update confirmation fails twice and the value becomes “0”, it is determined that an introduction relationship is not effective. This is because notification of the “introducing” update information and confirmation of the “introduced” update information are conducted asynchronously. So, there is provided a margin to be considered in terms of an actual operation of a system. Thus, a margin is not inevitable matter. In the case where a margin is not required to be considered, the base value of the “introducing” update parameter and the “introduced” update parameter can be set at “1”. Alternatively, the base value of the “introducing” update parameter and the “introduced” update parameter can be set at “3” or higher with a larger margin. Furthermore, an update confirmation timing is set to be a predetermined timing (12:00 a.m. once per day). However, update confirmation processing of the introduction relationship may be conducted when the contents of incentive information is updated. [0174]
The introduction target system [0175] 300 e can also conduct an initialization operation of incentive information on a predetermined period basis, and limit a period in which incentive can be provided to a predetermined period. When the incentive providing part 350 described in Embodiment 3 is used, the incentive providing part 350 continues to give an incentive at a predetermined timing in the case of being notified of update of the introduction relationship from the “introduction” confirming part 340 e, and stops providing an incentive in the case of not being notified of update of the introduction relationship.
The present embodiment has been described mainly based on the case where a terminal of an introduction destination system is present. However, in the case where the terminal of the introduction destination system is abandoned, required “introduced” update information is not sent from the introduction destination system. Therefore, update confirmation cannot be obtained in the “introduction” confirming part. [0176]
The introduction system of the present invention can be configured by providing a program describing processing operations for realizing the above-mentioned configuration and installing the program onto a computer. The program containing processing operations for realizing the introduction system of the present invention can be provided by being recorded onto a recording medium [0177] 1000 in a recording apparatus on a network and a recording medium 1005 such as a hard disk and a RAM of a computer, as well as a portable recording medium 1001 such as a CD-ROM 1002 and a flexible disk 1003. Furthermore, the program can be downloaded through the network. In execution, the program is loaded onto a computer 1004.
According to the introduction system of the present invention, an “introducing” action from an introduction origin system to an introduction destination system and a registration action with respect to a buddy list are smoothly conducted, and an introduction target system can recognize that there is an registration action onto a buddy list. [0178]
Furthermore, according to the introduction system of the present invention, the introduction target system receives notification of “introducing” action from the introduction origin system, and compares the received notification of the “introducing” action with the contents of the notification of the registration action from an introduction destination system, thereby confirming the “introducing” action. [0179]
Furthermore, according to the introduction system of the present invention, an incentive can be given to users of an introduction origin system and an introduction destination system in which an “introducing” action and a registration action are recognized and confirmed, and registration onto a buddy list of the introduction target system can be promoted. [0180]
The invention may be embodied in other forms without departing from the spirit or essential characteristics thereof. The embodiments disclosed in this application are to be considered in all respects as illustrative and not limiting. The scope of the invention is indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are intended to be embraced therein. [0181]
US09/995,815 2001-07-16 2001-11-29 Introduction system Abandoned US20030014487A1 (en)
JP2001-215759 2001-07-16
JP2001215759A JP4804663B2 (en) 2001-07-16 2001-07-16 Introduction system
US20030014487A1 true US20030014487A1 (en) 2003-01-16
ID=19050342
US09/995,815 Abandoned US20030014487A1 (en) 2001-07-16 2001-11-29 Introduction system
US (1) US20030014487A1 (en)
JP (1) JP4804663B2 (en)
US20060224929A1 (en) * 2005-03-29 2006-10-05 Fujitsu Limited Content generating apparatus and method
WO2005103972A1 (en) * 2004-04-22 2005-11-03 Enagic Co., Ltd. Sales management system
JP4522837B2 (en) * 2004-12-09 2010-08-11 株式会社日立製作所 Shareholders coupon distribution methods and shareholders' coupon distribution system,
JP5233320B2 (en) * 2008-02-27 2013-07-10 ソニー株式会社 Data processing system and data processing method
JP2001167147A (en) * 1999-12-07 2001-06-22 Soshiaru Shitei:Kk Method for advertisement service with reward and system for advertisement service with reward conducting the method
2001-07-16 JP JP2001215759A patent/JP4804663B2/en active Active
2001-11-29 US US09/995,815 patent/US20030014487A1/en not_active Abandoned
JP4804663B2 (en) 2011-11-02
JP2003030381A (en) 2003-01-31
US20070005429A1 (en) 2007-01-04 Method for controlling the distribution of advertisements to informational client devices using a plurality of operating modes