JP2009110255A - Communication terminal, computer program thereof, data distribution method thereof, and data distribution system using the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for quickly and accurately notifying other specific user terminals of new user address data when user address data of a certain user terminal is changed. <P>SOLUTION: A center terminal 30 includes: a rule storage section for storing rule information for distributing user address data to acquaintance terminals 20 for every user terminal 10; a receiving section for receiving the new user address data from the user terminal 10 when the user address data are changed; and a distribution section for distributing the new user address data to other user terminals determined to be distributed by a determining section for determining whether to distribute the received user address data based on the rule information for every acquaintance terminal 20. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a communication terminal that connects a plurality of user terminals having a user destination folder for storing at least one user destination data via a network and distributes the user destination data to the user terminal, a computer program thereof, and a data distribution method thereof And a data distribution system using the same.

  In recent years, information (user destination data) such as e-mail addresses and telephone numbers has been overflowing due to the spread of the Internet and mobile phones. Therefore, user destination data can be created or changed relatively easily.

  It is necessary to contact many acquaintances at the same time for notification of changes in user destination data. In the business field, it is necessary to promptly and accurately communicate such changes in user destination data.

  Patent Document 1 describes a service that notifies a transfer customer of changes in phone numbers and mail addresses all at once to acquaintances, business partners, and the like.

  Patent Document 2 describes a technique for exchanging address information using short-range wireless communication between mobile phones.

  Patent Document 3 describes a technique for automatically updating the telephone number of the own terminal registered in a plurality of counterpart terminals when the telephone number of the own terminal is changed.

In recent years when communication network technology has been developed, in many cases, a user holds a plurality of user destination data depending on purposes. Taking an email address as an example of user destination data, many users use a private email address and an email address used at work. In the workplace, an email address assigned to each employee may be used separately from a common email address representing a certain organization. Further, there are cases where the e-mail address to be used is properly used depending on the business partner. Thus, even when a plurality of e-mail addresses are held, the user can select which e-mail address to use at the time of transmission by using a known application. Therefore, it is advantageous in terms of convenience to collectively manage these e-mail addresses with their own terminals.
JP-A-2005-136925 JP-A-2005-129990 JP 2005-237025 A

  However, when a part of the e-mail addresses collectively managed in this way is changed, the user wants to notify the change only to a specific party according to the purpose of use. In addition, since an e-mail address is a kind of personal information, some recipients may not want to be notified of the change. For example, it is not always necessary to inform business partners of changes in their private email addresses.

  On the other hand, when the user operates the user terminal and individually selects a partner to be notified for each changed e-mail address and transmits data, there is a problem of lack of speed. There is also a problem of erroneous notification.

  In the techniques described in Patent Documents 1 to 3, there is a problem that the change of user destination data cannot be distributed to a specific user terminal corresponding to the purpose of use for each user destination data.

  Such a problem is a common problem that arises when changing user destination data for contacting a user, such as a telephone number and an address, as well as an e-mail address.

  The present invention has been made in view of the above circumstances, and when there is a change in user destination data of a certain user terminal, the user destination data that has been changed quickly and accurately is notified to a specific other user terminal. It is an object of the present invention to provide a communication terminal, a computer program thereof, a data delivery method thereof, and a data delivery system using the same.

According to the present invention, a communication terminal is connected to a plurality of user terminals including a user destination folder for storing at least one user destination data via a network and distributes the user destination data to the user terminals.
Rule storage means for storing rule information for distributing user destination data to other user terminals for each user terminal;
Accepting means for accepting the changed user destination data from the user terminal when the user destination data is changed;
Determining means for determining whether or not to distribute the received user destination data based on the rule information for each of the other user terminals;
Distribution means for distributing the changed user destination data to other user terminals determined to be distributed;
A communication terminal is provided.

Moreover, according to the present invention,
A data distribution method for connecting a plurality of user terminals including a user destination folder storing at least one user destination data via a network and distributing the user destination data to the user terminals,
Storing rule information for distributing user destination data to other user terminals for each user terminal;
When the user destination data is changed, receiving the changed user destination data from the user terminal; and
Determining whether to distribute the received user destination data based on the rule information for each other user terminal; and
Distributing the changed user destination data to other user terminals determined to be distributed;
A data distribution method characterized by comprising:

Moreover, according to the present invention,
A computer program for a communication terminal, connected via a network to a plurality of user terminals having a user destination folder for storing at least one user destination data, and delivering user destination data to the user terminals,
A rule storage process for storing rule information for distributing user destination data to other user terminals for each user terminal;
When the user destination data is changed, a reception process for receiving the changed user destination data from the user terminal;
A determination process for determining whether to distribute the received user destination data based on the rule information for each other user terminal;
A distribution process for distributing the changed user destination data to other user terminals determined to be distributed;
A computer program for causing a communication terminal to execute is provided.

Furthermore, according to the present invention,
A data distribution system for connecting a plurality of user terminals including a user destination folder for storing at least one user destination data, and a communication terminal for distributing the user destination data to the user terminals via a network,
Communication terminal
Rule storage means for storing rule information for distributing user destination data to other user terminals for each user terminal;
Accepting means for accepting the changed user destination data from the user terminal when the user destination data is changed;
Determining means for determining whether or not to distribute the received user destination data based on the rule information for each of the other user terminals;
Distribution means for distributing the changed user destination data to other user terminals determined to be distributed;
A data distribution system is provided.

  It should be noted that the various components of the present invention need only be formed so as to realize their functions. For example, dedicated hardware that exhibits a predetermined function, data processing in which a predetermined function is provided by a computer program It can be realized as an apparatus, a predetermined function realized in the data processing apparatus by a computer program, an arbitrary combination thereof, or the like.

  In addition, the various components of the present invention do not have to be individually independent, a plurality of components are formed as a single member, and a single component is formed of a plurality of members. It may be that a certain component is a part of another component, a part of a certain component overlaps a part of another component, and the like.

  Moreover, although the several process is described in order in the data delivery method of this invention, the order of the description does not limit the order which performs a several process. For this reason, when implementing the data distribution method of this invention, the order of the some process can be changed in the range which does not interfere in content.

  Furthermore, the plurality of steps of the data distribution method of the present invention are not limited to being executed at different timings. For this reason, another process may occur during execution of a certain process, or a part or all of the execution timing of a certain process and the execution timing of another process may overlap.

  In addition, the communication terminal and the user terminal according to the present invention can read a computer program and execute corresponding data processing, so that a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), an I It can be implemented as hardware constructed with a general-purpose device such as an / F (Interface) unit, a dedicated logic circuit constructed so as to execute predetermined data processing, a combination thereof, and the like.

  In the present invention, causing the data processing apparatus to execute various operations corresponding to the computer program also means causing the data processing apparatus to control operations of the various devices.

  For example, storing various data in the communication terminal means that the CPU stores various data in an information storage medium such as an HDD (Hard Disc Drive) fixed to the data processing apparatus, and the data processing apparatus is interchangeably loaded. The CPU may store various data with a CD drive in an information storage medium such as a CD-R (Compact Disc-Recordable).

  When there is a change in user destination data of a certain user terminal, a specific other user terminal is identified and the changed user destination data is quickly notified while preventing unauthorized notification or erroneous notification.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In all the drawings, the same reference numerals are given to the same components, and the description will be omitted as appropriate.

  FIG. 1 is a schematic block diagram showing a logical structure of a data distribution system 1000 according to the present embodiment. In the present embodiment, data for connecting a user terminal 10 and an acquaintance terminal 20 having user destination folders for storing a plurality of user destination data and a center terminal 30 for delivering user destination data to the acquaintance terminal 20 via a network 400. This is a distribution system 1000.

  Specifically, the data distribution system 1000 is a system that automatically updates the user destination folder of the acquaintance terminal 20 when the user changes user destination data such as an email address or a telephone number. When the user destination folder is updated, the data distribution system 1000 distributes the user destination data changed based on the rule information stored in the center terminal 30 in advance, so that the received acquaintance terminal 20 automatically Means for updating the user destination folder. Note that the user destination data may be distributed after being converted into a predetermined data format (for example, XML format).

  The network 400 only needs to be able to exchange data by connecting with a cable such as a copper wire or an optical fiber, infrared rays, radio waves or the like. Specifically, it may be connected via a LAN (Local Area Network), a wireless LAN, a WAN (Wide Area Network), an intranet, a global Internet connecting a plurality of LANs and WANs, and the like.

  The user terminal 10 and the acquaintance terminal 20 are information processing apparatuses such as a personal computer or a portable terminal. The user terminal 10 and the acquaintance terminal 20 have a function of accessing the management system provided by the center terminal 30 and changing their personal information (user destination data). When the user destination data is changed, the changed user destination data is transmitted to the center terminal 30 via the network 400. The user terminal 10 is a terminal used by a user, and may be a terminal for each user. When the user logs in to a certain terminal using information for identifying the user, the logged-in terminal becomes the user terminal 10. Similarly, the acquaintance terminal 20 may be a terminal for each acquaintance or a terminal to which an acquaintance has logged in.

  FIG. 2 is a schematic block diagram showing a logical structure of user terminal 10 according to the present embodiment. The user terminal 10 includes an input unit 101, a user destination folder 103, a conversion unit 105, and a transmission unit 107.

  The user destination folder 103 stores a plurality of user destination data of the user. The user destination data includes, for example, information such as an email address, a telephone number, and an address. The user destination folder 103 may store user destination data in association with destination identification information for identifying user destination data.

  The input unit 101 accepts creation of various data by input from the user. The input unit 101 receives new user destination data and stores it in the user destination folder 103. Also, the user destination folder 103 is updated by accepting a change in user destination data in response to an input from the user. Furthermore, the input unit 101 may accept creation and change of rule information for distributing user destination data to the acquaintance terminal 20.

  The rule information is rule information predetermined by the user, for example, information indicating whether or not the acquaintance terminal 20 is allowed to transmit specific user destination data, whether or not the user destination data is received from the acquaintance terminal 20 and the like. is there. That is, in the rule information, a predetermined distribution rule is defined for each acquaintance terminal 20. For example, in the rule information, acquaintance identification information for identifying an acquaintance is associated with an authentication level. The authentication level is information indicating a threshold value for distributing user destination data.

  The user destination folder 103 stores user destination data in association with destination identification information for identifying user destination data. Further, the user destination folder 103 stores the authentication level in association with each user destination data. FIG. 3 shows an example of the data structure of the rule information. Acquaintance identification information (user ID) and an authentication level (Auth Level) are associated with each other. When the data structure shown in FIG. 3 is used as the rule information, the user destination folder 103 may store only the authentication level in the rule information in association with the user destination data. As will be described later, the rule information is registered in the rule storage unit 303 of the center terminal 30 in advance. When registering the rule information, the rule information may be transmitted to the center terminal 30 after the conversion unit 105 converts the data into XML format data. By adopting the XML format, it is possible to freely include rule information such as an authentication level in a tag with acquaintance identification information as a local sentence.

  The user destination folder 103 may store user destination data and a transmission flag indicating a transmission history in association with each other. When the user destination data is changed, the transmission flag is unchecked.

  When the input unit 101 receives a change of user destination data from the user, the conversion unit 105 converts the changed user destination data into data for distribution to the center terminal 30. The conversion unit 105 adds an authentication level corresponding to each changed user destination data.

  In addition, when the user destination data is changed, the conversion unit 105 extracts the changed user destination data from the plurality of user destination data stored in the user destination folder 103. When the transmission flag is associated with the user destination data, the conversion unit 105 extracts the user destination data without the transmission flag check from the user destination folder 103. When the conversion unit 105 extracts the user destination data, the conversion unit 105 checks the corresponding transmission flag. Thus, when the user destination data is changed, the user terminal 10 extracts the changed user destination data from the plurality of user destination data stored in the user destination folder 103 and transmits the extracted user destination data to the center terminal 30. Can do. For this reason, the load concerning the network 400 and the load to the acquaintance terminal 20 and the center terminal 30 can be reduced.

  The conversion unit 105 may add destination identification information to a plurality of user destination data stored in the user destination folder 103 when the user destination data is changed. The conversion unit 105 sends the converted user destination data to the transmission unit 107.

  Note that the conversion unit 105 may convert user destination data to which various data is added into XML format data. FIG. 4 shows the XML destination user destination data converted by the conversion unit 105. In this example, a tag is added to each user destination data with the user destination data as a sentence of the ground. The tag includes identification information for identifying user destination data (e-mail address (Email), telephone number (phone), address (Address), etc.)) and authentication level (Auth Level). In this way, by setting the user destination data in the XML format, the user destination data can be included in the tag, and the rule information such as identification information and authentication level for identifying the user destination data can be freely included in the tag. Can do. Furthermore, in the example of FIG. 4, an ID (01234567) that identifies the user terminal 10 is added. For this reason, the center terminal 30 can specify that the user destination data is that of the user terminal 10.

  The transmission unit 107 receives the user destination data thus converted from the conversion unit 105 and transmits it to the center terminal 30.

  FIG. 5 is a schematic block diagram showing a logical structure of the center terminal 30 according to the present embodiment. The center terminal 30 includes a destination storage unit 301, a rule storage unit 303, a determination unit 305, a distribution unit 307, and a reception unit 309. The center terminal 30 operates by program control. The center terminal 30 stores rule information. The center terminal 30 delivers user destination data to the acquaintance terminal 20 in accordance with the stored rule information.

  When the user destination data is changed, the receiving unit 309 receives the changed user destination data from the user terminal 10. The accepting unit 309 can accept the authentication level together with the changed user destination data. The user destination data may be XML format data, for example.

  The destination storage unit 301 stores a distribution destination of user destination data for each user terminal 10. Specifically, user destination data of the acquaintance terminal 20 is associated with acquaintance identification information (user ID, personal information number, etc.) for identifying the acquaintance. FIG. 7 is an example of a data structure stored in the destination storage unit 301. In the example of FIG. 7, the e-mail address of the acquaintance terminal 20 and the user ID are associated with each other as a destination. The distribution destination may be received from the user terminal 10 by the reception unit 309 via the network 400 or may be directly input to the reception unit 309. The accepting unit 309 sends the accepted delivery destination to the destination storage unit 301 and stores it in the destination storage unit 301. Further, user destination data communicated between the user terminal 10 and the acquaintance terminal 20 may be stored as a delivery destination. When acquaintances are divided into groups and managed, information for identifying the groups and distribution destinations may be associated with each other. A group is a group having some commonality with daily life of users, such as private, company, business partner, and so on.

  The rule storage unit 303 stores rule information for distributing user destination data to the acquaintance terminal 20 for each user terminal 10. The rule storage unit 303 stores the authentication level of the acquaintance terminal 20 for each acquaintance terminal 20 as rule information. Further, the acquaintance terminal 20 may be classified into groups and information for identifying the groups may be stored in association with the group authentication level. As described above, the rule information is rule information determined by the user in advance, for example, whether the user destination data to which the changed user destination data can be distributed is received from the terminal 20 operated by the acquaintance. This is information indicating whether or not, up to which user destination data can be distributed. The rule information stored in the rule storage unit 303 has a data structure shown in FIG. 3, for example. The storage of the rule information may be received directly by the receiving unit 309 or may be received from the user terminal 10 or the acquaintance terminal 20 via the network 400. The accepting unit 309 causes the rule storage unit 303 to store the accepted rule information. The rule information may be XML format data. Moreover, the change of rule information may be received for each user terminal 10.

  Further, the rule storage unit 303 may store distribution permission information indicating that distribution of user destination data is permitted for each acquaintance terminal 20 when the user terminal 10 changes the user destination data. The distribution information may be directly input from the reception unit 309 or may be received from the acquaintance terminal 20 via the network 400. Specifically, the distribution permission information is a list of user terminals 10 that the acquaintance terminal 20 permits distribution. The distribution permission information may be rule information of the acquaintance terminal 20.

  The determination unit 305 determines whether to accept the received user destination data based on the rule information for each acquaintance terminal 20. In addition, the determination unit 305 selects the acquaintance terminal 20 to be distributed from the acquaintance terminals 20 in which the distribution destinations are stored. The determination unit 305 determines that the user destination data is distributed when the authentication level of the acquaintance terminal 20 satisfies the authentication level of the user destination data. Specifically, when an authentication level is added to the received user destination data, the authentication level for each acquaintance terminal 20 stored in the rule storage unit 303 is compared with the authentication level for each user destination data, and the acquaintance terminal It is determined whether the authentication level corresponding to 20 satisfies the authentication level of the user destination data. When the level is met, it is decided to distribute the changed user destination data. In addition, the determination unit 305 selects the acquaintance terminal 20 to be distributed from the user terminals in which the distribution destinations are stored. Specifically, the determination unit 305 reads the corresponding delivery destination from the destination storage unit 301 based on the corresponding acquaintance identification information or group identification information, and outputs the read destination together with the user destination data to the delivery unit 307. When the authentication level is not satisfied, it is determined that the changed user destination data is not distributed to the acquaintance terminal 20.

  For example, it is assumed that the rule information illustrated in FIG. 3 is stored in the rule storage unit 303 and the user destination data illustrated in FIG. 4 (only data from <self> to </ self>) is received. Since the user IDs A123 and B123 satisfy all authentication levels (Auth Level) of the user destination data included in FIG. 4, the user destinations shown in FIG. Data is delivered. On the other hand, since the user ID: C123 does not satisfy the authentication level for the e-mail address and the mobile number, it is determined that the user ID: C123 is not distributed to the acquaintance terminal 20 of the user ID: C123.

  Note that the determination unit 305 may determine whether to distribute information for specifying the user. For example, since the user IDs C123 and F123 do not satisfy the authentication level of the nickname, the nickname is not distributed. In the example of FIG. 4, data from <Friends No = “1”> to </ Friends> is added. When such data is added, the user destination data is distributed by designating only the user ID: F123.

  Further, the determination unit 305 determines whether or not the user destination data changed based on the distribution permission information stored in the rule storage unit 303 is distributed to the acquaintance terminal 20. Specifically, with reference to the distribution permission information of the acquaintance terminal 20 determined to satisfy the authentication level, it is determined whether or not the distribution of the changed user destination data of the user terminal 10 is permitted. When the information for identifying the user terminal 10 is included in the distribution permission information, it is determined that the changed user destination data is distributed to the acquaintance terminal 20. On the other hand, when the information for identifying the user terminal 10 is not included in the distribution permission information, it is determined that the changed user destination data is not distributed to the acquaintance terminal 20. By doing so, the acquaintance terminal 20 can have only the user destination data of the user who wants to receive the change notification distributed. The acquaintance terminal 20 may store a list of user terminals 10 whose distribution is rejected in the rule storage unit 303.

  The distribution unit 307 distributes the changed user destination data to the acquaintance terminal 20 determined to be distributed. At this time, the distribution unit 307 adds the distribution destination of the acquaintance terminal 20 determined to be distributed and distributes the user destination data. The distribution unit 307 can also distribute the changed user destination data to the acquaintance terminal 20 that permits the distribution.

  In this way, the center terminal 30 can prevent unauthorized notification or erroneous notification by sending data in accordance with stored rules.

  FIG. 6 is a schematic block diagram showing the logical structure of the acquaintance terminal 20. The acquaintance terminal 20 includes a user destination folder 201, a reception unit 203, an update unit 205, and a transmission unit 207. The user terminal 10 also has the same function as the acquaintance terminal 20. This is because the acquaintance terminal 20 is the user terminal 10 and the user terminal 10 is in the relationship of the acquaintance terminal 20 when viewed from the acquaintance terminal 20.

  The user destination folder 201 stores a plurality of user destination data for each user. The user destination data includes, for example, information such as an email address, a telephone number, and an address. The user destination folder serves as an address book. The user destination folder 201 has the same function as the user destination folder 103.

  The receiving unit 203 receives the changed user destination data from the center terminal 30 when the user destination data of the user terminal 10 is changed. The receiving unit 203 sends the received user destination data to the update unit 205.

  The update unit 205 updates the user destination folder 201 when the user destination data is distributed from the center terminal 30. When the user destination data is distributed from the center terminal 30, the update unit 205 may update the corresponding user destination data based on the destination identification information. When XML destination user destination data is received, destination identification information for identifying user destination data is included in the tag. Therefore, the corresponding user destination data can be updated based on the destination identification information included in the tag.

  The acquaintance terminal 20 may create distribution permission information indicating that distribution of user destination data is permitted when the user terminal 10 changes the user destination data. The created distribution permission information is read from the user destination folder 201 by the transmission unit 207 and transmitted from the transmission unit 207 to the center terminal 30. As described above, the center terminal 30 distributes only the user destination data of the user included in the distribution permission information to the acquaintance terminal 20. By doing so, it is possible to receive only the user destination data of the user who wants to receive the change notification. The distribution permission information may be rule information of the acquaintance terminal 20.

  Next, the operation of the data distribution system 1000 according to the embodiment will be described with reference to FIGS. 1 and 2. The center terminal 30 stores rule information for distributing user destination data for each acquaintance terminal 20. When the user destination data is changed, whether or not the changed user destination data is distributed is determined for each acquaintance terminal 20 based on the rule information. The changed user destination data is distributed to the acquaintance terminal 20 determined to be distributed.

  FIG. 8 is a flowchart illustrating a data distribution method according to the embodiment. A specific operation of the data distribution system 1000 according to the embodiment will be described below.

  First, the user terminal 10 and the acquaintance terminal 20 register their rule information in the center terminal 30 (data notification rule registration). The registration contents of the user terminal 10 are acquaintance identification information for identifying an acquaintance who may be notified of the user destination data of the user terminal 10 and an acquaintance authentication level. The registration contents from the acquaintance terminal 20 are distribution permission information indicating that information from the user terminal 10 may be received and rule information of the acquaintance terminal 20.

  Thereafter, when the user destination data of the user terminal 10 is changed (own data update within the terminal), the user terminal 10 converts the data into XML data (XML data automatic update). FIG. 4 is an example of the structure of user destination data. As for this data, only the changed part is converted into data such as XML in the user terminal 10. An individual can be specified by giving an ID for identifying the individual, for example, a personal information number in the data. In the example of FIG. 4, it is specified that the user destination data is ID: 0123567 and that the data is distributed to a friend of ID: F123. The data that is permitted to be distributed is assigned a level number as the authentication level, and provides a mechanism that can be distributed only to the acquaintance terminal 20 corresponding thereto. The extraction work is performed at the center terminal 30. In addition, when the user terminal 10 is not stored as an acquaintance of the acquaintance terminal 20 in the rule storage unit 303, the acquaintance terminal 20 cannot receive.

  The acquaintance terminal 20 transmits the user destination data converted into XML format data to the center terminal 30 (transmits the data to the center terminal 30). Further, when the user terminal 10 changes the acquaintance's authentication level (updates acquaintance authentication data), the user terminal 10 also transmits the rule information.

  When the user destination data is transmitted from the user terminal 10 to the center terminal 30 (XML data transmission), the center terminal 30 refers to the rule information in the rule storage unit 303 and refers to the authentication level of the user destination data and the acquaintance terminal to be distributed. 20 authentication levels are compared (acquaintance authentication). When the user terminal 10 is stored as an acquaintance of the acquaintance terminal 20 with the data having the same authentication level, the distribution destination is added (XML data creation), and the user destination data is distributed to the acquaintance terminal 20 (acquaintance) To the terminal 20). When the user destination data is distributed from the center terminal 30 to the acquaintance terminal 20 (XML data transmission), the acquaintance terminal 20 can automatically update the user destination folder by reflecting the changed portion (data update). ). You may have the mechanism which can choose automatic registration and manual registration by option.

  Also, the registration of rule information can be realized by operating the user terminal 10 or the acquaintance terminal 20 and transmitting data in the XML format or the like to the center terminal 30.

  Each part of the center terminal 30 as described above is realized by using various hardware as necessary. However, it is realized by the function corresponding to the computer program in which the center terminal 30 is mounted.

  Such a computer program includes, for example, a rule storing process for storing rule information for distributing user destination data to other user terminals for each user terminal, and when the user destination data is changed, the changed user Reception processing for receiving destination data from the user terminal, determination processing for determining whether or not the received user destination data is to be distributed based on the rule information for each other user terminal, and other users determined to be distributed It is stored in an information storage medium such as a RAM as software for causing a CPU or the like to execute processing operations such as distribution processing for distributing user destination data changed to a terminal.

  Then, the effect of this Embodiment is demonstrated. According to the center terminal of the present embodiment, rule information for distributing user destination data is stored for each acquaintance terminal. When the user destination data is changed, whether or not the changed user destination data is distributed is determined for each other user terminal based on the rule information. The changed user destination data is distributed to the acquaintance terminal determined to be distributed. Therefore, when the user changes the user destination data, the user can distribute the changed user destination data to a specific acquaintance terminal according to a rule stored in advance.

  Even when there are a plurality of acquaintance terminals, a specific acquaintance terminal to be distributed can be extracted based on the rule information of the user destination data. Therefore, it is possible to notify the change of the user destination data quickly and easily while preventing the unauthorized notification and the erroneous notification. Even when there are a plurality of specific acquaintance terminals, a change in user destination data can be notified all at once.

  Conventionally, the personal information that has been updated or changed by the user needs to be individually contacted by the user. Therefore, leaks of communication and updates were frequently occurring. In addition, the acquaintance who was contacted was manually updated and changed. For this reason, there has been a problem that many acquaintances contacted or received acquaintances forget to renew or make mistakes. In addition, it is necessary to notify many acquaintances at the same time that the user destination data is changed. Further, in the business field, it is necessary to notify a change of user destination data quickly and accurately.

  According to the system of the present embodiment, it is possible to automatically notify the acquaintance terminal of changes in user destination data such as a telephone number or an e-mail address. This is because rule information for distribution to acquaintance terminals is collectively managed by the center terminal. Therefore, even when the user destination data is frequently changed, the user destination data changed to the acquaintance to be automatically distributed based on the rule information stored in advance can be distributed.

  Further, according to the system of the present embodiment, it is possible to prevent unauthorized notification and erroneous notification. The reason is that acquaintance terminals distributed by the center terminal can be selected by storing rule information in the center terminal in advance. The procedure for updating the rule information of the center terminal can be facilitated by changing the authentication level for each acquaintance.

  In addition, according to the system of the present embodiment, the center terminal 30 functions as a center server, and stores distribution rules for user destination data as rule information in the center server. The center server distributes the user destination data to the acquaintance terminal 20 according to the stored rule information, and updates the data. In the rule information, an authentication level is set for each user destination data, and only a specific acquaintance terminal 20 can be notified of a change in specific user destination data. Therefore, information leakage can be surely prevented. Moreover, since rule information is memorize | stored for every user terminal 10, the automatic update from other than the user terminal 10 can also be prevented.

  Furthermore, according to the system of the present embodiment, the user destination folder of the acquaintance terminal is automatically updated. This is because the data is converted into structured data such as XML and transmitted / received. Therefore, it is possible to extract and transmit only the changed user destination data among the plurality of user destination data held by the user. The acquaintance terminal can read the identification information of the user destination data from the structured data and update the corresponding user destination data. By doing so, the load on the acquaintance terminal 20, the center terminal 30, and the network 400 can be minimized.

  Also, according to the system of the present embodiment, a rule is created with an authentication level determined for each user terminal. For this reason, it is possible to define a rule as to what information may be distributed for each acquaintance terminal 20.

  Further, according to the system of the present embodiment, it is possible to make a determination by comparing the authentication level for each user destination data and each acquaintance based on the rule information stored in the center terminal. Therefore, it is possible to provide a system for selecting the acquaintance terminal 20 that distributes the user destination data and distributing the changed user destination data.

  Furthermore, according to the system of the present embodiment, the acquaintance terminal receives only the user destination data from the user terminal to be received. This is because the distribution permission information of the user terminal that the acquaintance terminal wants to receive is stored in the center terminal. For this reason, it is possible to prevent the acquaintance terminal from receiving data from the user terminal that the acquaintance terminal does not want to receive.

  As mentioned above, although embodiment of this invention was described with reference to drawings, these are the illustrations of this invention, Various structures other than the above are also employable.

  For example, when the user terminal purchases a new mobile terminal or when the user destination data is lost, the user terminal may acquire the user destination data of the acquaintance terminal.

  FIG. 9 is a flowchart for explaining a modification of the data distribution method according to the present embodiment. When the user terminal 10 creates a new user destination folder (creates a new address book), a new user destination folder creation inquiry is made to the center terminal 30 (acquaintance address inquiry). An inquiry is made to the terminal 20. Specifically, the destination storage unit 301 and the rule storage unit 303 are referred to, and the destination of the acquaintance terminal 20 registered as the rule information of the user terminal 10 is read from the destination storage unit 301. Also, the rule storage unit 303 checks whether or not the user terminal 10 is permitted to distribute from the acquaintance terminal 20 storing the rule information. And the user destination data of the acquaintance terminal 20 is inquired to the acquaintance terminal 20 permitted to distribute (address inquiry). At this time, if the authentication level of the user terminal 10 is associated with the distribution permission information, the center terminal 30 transmits the authentication level of the user terminal 10 to the acquaintance terminal 20 to inquire about the address. The acquaintance terminal 20 converts its user destination data into data such as XML so that the conversion unit (not shown) conforms to the authentication level of the user terminal 10 and transmits the data to the center terminal 30 (according to the authentication level). XML data generation and transmission). If the acquaintance terminal 20 stores the rule information, the center terminal 30 selects user destination data that matches the authentication level of the user terminal 10 based on the rule information of the acquaintance terminal 20, and sends the acquaintance to the user terminal 10. The user destination data of the terminal 20 can also be transmitted (XML data transmission). Thus, even when there are a plurality of acquaintance terminals 20, the user terminal 10 can simultaneously receive the user destination data of each acquaintance terminal 20 and store it in the user destination folder. For this reason, an address book in which user destination data of the acquaintance terminal 20 is stored can be created (data update).

  Therefore, the present invention can be applied to a user terminal that can use a network environment such as the Internet, such as personal information managed by a personal computer or a portable terminal, such as a user such as an address book.

  Moreover, the center terminal of this Embodiment may memorize | store the user destination data delivered from a user terminal to an acquaintance terminal as a delivery destination of a user terminal. When the center terminal receives the changed user destination data from the user terminal, the center terminal distributes the user destination data of the user terminal to the specific acquaintance terminal and also updates the distribution destination of the user terminal stored in the center terminal. By doing so, when the acquaintance terminal subsequently changes the user destination data, the center terminal accepts the changed user destination data from the acquaintance terminal, and sends the user destination data of the acquaintance terminal to the previously updated distribution destination of the user terminal. Can be delivered.

  Moreover, in this Embodiment, it illustrated that each part of a communication terminal was logically implement | achieved as various functions with a computer program. However, each of these units can be formed as unique hardware, or can be realized as a combination of software and hardware.

  Moreover, although the present Internet was illustrated as a network in the said form, this may be NGN (Next Generation Network) which is the next generation internet.

  Needless to say, the above-described embodiment and a plurality of modifications can be combined within a range in which the contents do not conflict with each other. Further, in the above-described embodiments and modifications, the structure of each part has been specifically described, but the structure and the like can be changed in various ways within a range that satisfies the present invention.

It is a typical block diagram which shows the logical structure of the data delivery system which concerns on embodiment. It is a typical block diagram which shows the logical structure of the user terminal which concerns on embodiment. An example of the data structure of the rule information which concerns on embodiment is shown. An example of the data structure of the user destination data which concerns on embodiment is shown. It is a typical block diagram which shows the logical structure of the center terminal which concerns on embodiment. It is a typical block diagram which shows the logical structure of the user terminal which concerns on embodiment. It is an example of the data structure of the destination memory | storage part which concerns on embodiment. It is a flowchart which shows the data delivery method which concerns on embodiment. It is a flowchart which shows the modification of the data delivery method which concerns on embodiment.

Explanation of symbols

10 user terminal 20 acquaintance terminal 30 center terminal 101 input unit 103 user destination folder 105 conversion unit 107 transmission unit 201 user destination folder 203 reception unit 205 update unit 207 transmission unit 301 destination storage unit 303 rule storage unit 305 determination unit 307 distribution unit 309 Reception unit 400 network 1000 data distribution system

Claims (13)

A communication terminal connected via a network to a plurality of user terminals having a user destination folder for storing at least one user destination data, and delivering the user destination data to the user terminal;
Rule storage means for storing rule information for distributing the user destination data to other user terminals for each user terminal;
Accepting means for accepting the changed user destination data from the user terminal when the user destination data is changed;
Determining means for determining whether to distribute the received user destination data based on the rule information for each of the other user terminals;
Distribution means for distributing the changed user destination data to the other user terminal determined to be distributed;
A communication terminal comprising: A destination storing means for storing a delivery destination of the user destination data for each user terminal;
The determination means selects the other user terminal to be distributed from the user terminals in which the distribution destination is stored,
The communication terminal according to claim 1, wherein the distribution unit adds the distribution destination of the other user terminal determined to be distributed and distributes the user destination data.   The communication terminal according to claim 1, wherein the rule storage unit stores an authentication level for each of the other user terminals as the rule information. The accepting means accepts the authentication level together with the changed user destination data from the user terminal,
The communication terminal according to claim 3, wherein the determination unit determines to distribute the user destination data when the authentication level of the other user terminal satisfies an authentication level of the user destination data. The rule storage means stores, for each of the other user terminals, distribution permission information indicating that distribution of the user destination data is permitted when a predetermined user terminal changes the user destination data.
The determination means determines whether or not to distribute the user destination data changed based on the distribution permission information to the other user terminal,
5. The communication terminal according to claim 1, wherein the distribution unit distributes the changed user destination data to the other user terminal that permits distribution. 6.   The communication terminal according to claim 1, wherein the reception unit receives the user destination data in an XML format.   The communication terminal according to claim 1, wherein the user destination data is information indicating any one of an e-mail address, a telephone number, and an address. A data distribution method for connecting a plurality of user terminals including a user destination folder for storing at least one user destination data via a network and distributing the user destination data to the user terminals,
Storing rule information for distributing the user destination data to other user terminals for each user terminal;
Receiving the changed user destination data from the user terminal when the user destination data is changed;
Determining whether to distribute the received user destination data based on the rule information for each of the other user terminals;
Delivering the changed user destination data to the other user terminal determined to deliver;
A data distribution method comprising: A computer program for a communication terminal, connected via a network to a plurality of user terminals comprising a user destination folder for storing at least one user destination data, and delivering the user destination data to the user terminal,
A rule storage process for storing rule information for distributing the user destination data to other user terminals for each user terminal;
When the user destination data is changed, a reception process for receiving the changed user destination data from the user terminal;
A determination process for determining whether to distribute the received user destination data based on the rule information for each of the other user terminals;
A distribution process for distributing the changed user destination data to the other user terminal determined to be distributed;
A computer program for causing the communication terminal to execute. A data distribution system for connecting a plurality of user terminals including a user destination folder for storing at least one user destination data, and a communication terminal for distributing the user destination data to the user terminals via a network,
The communication terminal is
Rule storage means for storing rule information for distributing the user destination data to other user terminals for each user terminal;
Accepting means for accepting the changed user destination data from the user terminal when the user destination data is changed;
Determining means for determining whether to distribute the received user destination data based on the rule information for each of the other user terminals;
Distribution means for distributing the changed user destination data to the other user terminal determined to be distributed;
A data distribution system comprising:   When the user destination data is changed, the user terminal extracts the changed user destination data from a plurality of user destination data stored in the user destination folder, and transmits the extracted user destination data to the communication terminal. The data distribution system according to claim 10.   The user terminal stores the user destination data in association with destination identification information for identifying the user destination data. When the user destination data is changed, the user terminal stores a plurality of user destination data stored in the user destination folder. 12. The data distribution system according to claim 11, wherein the destination identification information is added and transmitted to the communication terminal.   13. The data according to claim 12, wherein the other user terminal updates the corresponding user destination data based on the destination identification information when the user destination data is distributed from the communication terminal. Distribution system.

Images