JP2008252481A - Incoming notice information registration control system, and incoming notice information registration control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent a billing fraud or the like by notifying the attribute information which has been registered corresponding to the telephone number of a caller user, when receiving an incoming call. <P>SOLUTION: An allowed sharer table 220 is used to register only a registration request from a user allowed by a receiving side user in an incoming notice information database 210. A telephone number is associated with the attribute information and registered in the incoming notice information database 210, and the attribute information corresponding to the telephone number of a registered caller user is notified when receiving an incoming call to thereby distinguish whether the incoming call is from an acquaintance or an impersonating caller so that a billing fraud or the like can be prevented. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an incoming call notification information registration control system and an incoming call notification information registration control method, and more particularly to an incoming call notification information registration control system and incoming call notification information registration for controlling registration of information to be notified when a caller receives an incoming call. It relates to a control method.

  In general, when an incoming call is received by a telephone, it is convenient to know who the caller is. If the caller is an acquaintance, you can immediately answer the call and start a call. In particular, it is possible to respond appropriately to so-called wire fraud calls that have been increasing in recent years. That is, when an incoming call comes from a caller who calls an acquaintance, if you know who the caller is (that is, if you know the telephone number of the calling phone), the call comes from an acquaintance or a caller Can be determined.

Here, Patent Document 1 describes a technique in which user information related to a caller is registered in a database in advance, and when there is an incoming call from the caller, the user information is acquired from the database and notified to the called party. Has been.
Patent Document 2 prompts the user to enter a personal identification number when the caller's telephone number matches a pre-registered telephone number. When the inputted personal identification number matches the registered one, the call can be made. It describes the technology to prevent fraud damage by impersonation by controlling.
JP 2005-197827 A JP 2006-262270 A

In the technique described in Patent Literature 1, prior notification by a caller is required when notifying user information about the caller. Since it is usually impossible for a malicious actor to pre-register himself / herself, even if the technique described in Patent Document 1 is adopted, it cannot be discriminated whether it is an incoming call from an acquaintance or an incoming person.
On the other hand, in the technique described in Patent Document 2, it is necessary to register a password in advance and to teach the registered password to an authorized party. Therefore, there is a problem that if the password is forgotten, it cannot be received.
An object of the present invention is to provide an incoming call notification information registration control system and an incoming call notification information registration control capable of registering in a database information for determining whether an incoming call is from an acquaintance or an incoming call when there is an incoming call. Is to provide a method.

  According to the first aspect of the present invention, a database (for example, corresponding to the incoming call notification information database 210 in FIG. 2) in which information to be notified at the time of an incoming call from the caller side to the user is registered for each user. An incoming call notification information registration control system that controls registration, and an allowed sharer table (for example, corresponding to the allowed sharer table 220 in FIG. 2) in which information related to other users permitted to be registered in the database is registered. And a determination means (for example, corresponding to steps S12 and S17 in FIG. 5) for determining whether the registration request is from a user registered in the allowed sharer table when there is a registration request to the database. And registration of information on registration requests from users registered in the allowed sharer table. To provide.

  According to the first aspect of the present invention, it is possible to discriminate whether an incoming call is from an acquaintance or from a person who has received an incoming call by allowing other users to register using the allowed sharer table. Can be registered in the database. Therefore, by notifying the information registered in this database when an incoming call is received, it is possible to notify that the incoming call is from the user himself / herself and to prevent a transfer fraud.

According to a second aspect of the present invention, in the incoming call notification information registration control system according to the first aspect, when the determination unit has a registration request from the user himself / herself to the database, the information is registered for the registration request. It is characterized by performing.
According to the invention of claim 2, by registering the name of the user himself / herself, it is possible to notify who the call is from when the call is received.

According to a third aspect of the present invention, in the incoming call notification information registration control system according to the first aspect, when there is a registration request regarding a group to which a plurality of users belong, the determination means It is characterized in that it is sequentially determined whether it is registered in the allowable sharer table.
According to the third aspect of the present invention, it is possible to specify a plurality of users at once by inputting a group name, and it is not necessary to perform a registration operation for the same telephone number a plurality of times.

According to a fourth aspect of the present invention, in the incoming call notification information registration control system according to any one of the first to third aspects, the information to be notified includes an ID of the sender and a notification. And the ID of the person who registered the information.
According to the invention of claim 4, it is possible to determine whether the call is from the user himself / herself or from the person who is talking by notifying the ID such as the telephone number, so that the incoming call is from the user himself / herself. In addition to being able to notify, it is possible to prevent wire fraud.

The invention according to claim 5 of the present invention is the incoming call notification information registration control system according to any one of claims 1 to 4, wherein the database registers the information in a database of another user. The sharer information is set for each piece of information to be notified.
According to the fifth aspect of the present invention, the registered content can be reflected in the database of another user based on the set sharer information.

  The invention of claim 6 of the present invention is an incoming call notification information registration control method for controlling registration in a database in which information to be notified at the time of an incoming call from a caller to a user is registered for each user, When there is a registration request to the database, refer to an allowed sharer table in which information related to other users permitted to be registered in the database is registered, and the registration request is registered in the allowed sharer table A step (for example, corresponding to steps S12 and S17 in FIG. 5) for determining whether the request is a registration request from a user, and a step for registering information on a registration request from a user registered in the allowed sharer table (for example, , Corresponding to steps S13 and S18 in FIG. 5), an incoming call notification information registration control method is provided.

  According to the invention of claim 6, by permitting the registration of other users using the allowable sharer table, it is discriminated whether the incoming call is from an acquaintance or the person who is speaking when there is an incoming call. Can be registered in the database. Therefore, by notifying the information registered in this database when an incoming call is received, it is possible to notify that the incoming call is from the user himself / herself and to prevent a transfer fraud.

  According to the present invention, an arbitrary telephone number and its attribute information are registered in association with each other by a user permitted by the called user, and the attribute information corresponding to the registered telephone number of the calling user is received. By notifying sometimes, it is possible to prevent wire fraud.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings referred to in the following description, the same parts as those in the other drawings are denoted by the same reference numerals.
(System configuration)
FIG. 1 is a diagram showing a configuration example of a mobile communication network to which an incoming call notification information registration control system according to the present invention is applied. In the figure, the mobile communication network of this example includes a base station 21 for realizing the radio cell 10, a base station controller 31 for controlling the base station 21, and a base station 22 for realizing the radio cell 20. And the base station control device 32 that controls the base station 22, the exchange 1 that is connected to the base station control devices 31 and 32 and performs the exchange process, and the information about the user who receives the mobile communication service is registered. (Home Location Register) 2.

In such a mobile communication network, the communication device 11 located in the radio cell 10 can receive provision of a mobile communication service. In addition, the communication device 12 located in the radio cell 20 can be provided with a mobile communication service.
In the system of this example, an incoming call notification information database in which information to be notified at the time of incoming call is registered for each subscriber is stored in the HLR 2. In addition, an allowed sharer table in which information as a condition for registration in the incoming call notification information database is registered is also stored in the HLR 2. This system implements a process of notifying attribute data to the communication device 11 and the communication device 12 using the incoming call notification information database and the allowable sharer table.

(Incoming call notification information database, allowable sharer table)
FIG. 2 is a diagram showing an example of the incoming call notification information database 210 and the allowable sharer table 220 registered in the HLR 2 in FIG. 2A shows an example of an incoming call notification information database 210 in which information to be notified at the time of incoming call is registered for each user, and FIG. 2B shows registration in the incoming call notification information database 210. It is a figure which shows the example of the permissible sharer table 220 in which the information used as the conditions for being registered is registered.

  Referring to FIG. 5A, in this example, the incoming call notification information database 210 includes a “target telephone number” that is a telephone number (that is, an ID) to which information is to be notified, and contents to be notified when an incoming call is received. “Notification information”, “registrant” that is a telephone number corresponding to the registrant of information, and “sharer” that is a telephone number that is allowed to share registration. In the state of the figure, “090-1234-5678”, which is the telephone number of the user of the communication apparatus, is “target telephone number”, and “Ichiro Yamada”, who is the name of the user of the communication apparatus, is “notification information”. , Each is registered. Further, in this example, “guarantee” indicating that the communication service carrier company guarantees that the registration is related to the user is “registrant”, and “all users” for allowing registration to all users is “ Each is registered as a “sharer”. In “Sharer”, the telephone number of the user who wants to share the information of the item is registered.

  The incoming call notification information database 210 shown in FIG. 4A is provided for each user. The registered contents can be changed. The registered contents can be changed by the user himself (that is, Ichiro Yamada in this example) or a person registered in the allowable sharer table 220 in FIG. The user authentication may be performed by inputting a password.

  On the other hand, referring to FIG. 5B, in the present example, in the allowed sharer table 220, another user who allows the user “Ichiro Yamada” to register in his / her incoming notification information database is registered. In the state of the figure, a friend “Jiro Tanaka” and his telephone number “090-4321-4477”, his mother “Yamada Haha” and his telephone number “090-1212-9999” are registered. Has been. Therefore, only “Jiro Tanaka” and “Yamada Haha” registered in the allowable sharer table 220 are registered in the incoming call notification information database 210 described with reference to FIG. be able to.

  Also, the allowed sharer table 220 shown in FIG. 5B can change the registered contents only for the user himself (that is, Ichiro Yamada in this example). Therefore, it is possible to allow registration to the incoming call notification information database only for a user trusted by the user himself / herself. This means that a group centered on the user himself / herself is set for each user individually.

(Registration screen display example)
FIG. 3 is a diagram showing a screen display example for registering in the incoming call notification information database. This example is a screen display example when the communication device in FIG. 1 is a mobile phone.
In the figure, the display screen displays a “registration number” that you want to register in the incoming call notification information database, “notification contents” such as a reason for registration and an explanation of the registration number, and other information you want to register in the database. A column for inputting “sharer number (group name)” for each user is displayed.
In this example, a telephone number is entered in the “registration number” field. In this example, an arbitrary sentence can be entered in the “notification content” column.
In the column of “sharer number (group name)”, in this example, a telephone number of a user who desires registration, that is, a registration destination user, or a group name desired to be registered can be input. If a group name can be entered and a plurality of users can be specified at once, it is convenient that a registration operation for the same telephone number need not be performed a plurality of times.

(Group management table)
In order to input a group name, it is necessary to register “group name” and “phone number” in the management table in association with each other. For example, in the group management table shown in FIG. 4, a “group name” indicating a group is set, and a “telephone number” to belong to the group is registered in the table in association with each other. In the figure, groups of “friend”, “family”, and “company” are set, and telephone numbers belonging to each group are registered. If “friend” is entered in the “sharer number (group name)” field, registration is performed for the telephone number belonging to the group.
If registration of other users in the incoming notification information database is not desired, the “sharer number (group name)” field is blank.

(registration process)
FIG. 5 is a flowchart showing an example of registration control by this system.
In the figure, the system waits until there is a registration request to the incoming call notification information database (FIG. 2A) (step S10). When there is a registration request to the incoming call notification information database, it is determined whether the group name is input as the sharer number (step S11).
If the group name is not entered as a sharer number, whether the person who made the registration request is registered in the allowed sharer table (FIG. 2B) of the user himself or the user who is trying to register (that is, sharing) Is registered as a user) (step S11 → S12). As a result of this determination, in the case of a registration request by the user himself / herself or registration in the allowed sharer table (that is, registration as a sharer), registration in the incoming call notification information database is performed (step S12 → S13), the process ends (step S14).

On the other hand, if it is not registered in the allowed sharer table, that is, if it is not registered as a sharer, registration in the incoming call notification information database is not performed (step S12 → S15), and the process ends (step S14). .
In step S11, when a group name is input as a sharer number, it is necessary to determine whether each user belonging to the group is registered as a sharer. For this reason, first, the telephone number of each user is acquired (step S11-> S16). Then, it is determined whether the person who made the registration request is the user himself / herself or registered in the allowed sharer table (FIG. 2B) of the user who is going to register (ie, registered as a sharer) (step) S16 → S17). As a result of this determination, in the case of a registration request by the user himself / herself or registered in the allowed sharer table (ie, registered as a sharer), registration in the incoming call notification information database is performed (step S17 → S18). On the other hand, if it is not registered in the allowable sharer table, that is, if it is not registered as a sharer, registration in the incoming call notification information database is not performed (steps S17 → S19).

Thereafter, it is determined whether the processing has been completed for all users belonging to the group (step S20). If the process has not been completed for all users, the process returns to step S17 and the process is continued. When the process is completed for all users, the process is terminated (step S20 → S14).
Since the registration process is performed as described above, in this system, only registration requests from users who are registered in the permitted sharer table, that is, permitted users, are registered requests from users other than the user himself / herself. Registration requests from users who are accepted and not allowed are not accepted. Therefore, even if a malicious person tries to register with an acquaintance, the registration is not performed.

(Specific example of registration process)
Next, a specific example of the registration process will be described with reference to FIG. In the same figure, an example of registration processing in the incoming call notification information database 210 is shown. In the figure, among the contents registered in the incoming call notification information database 210, the A part and the C part are parts registered by user input, and the B part is a part automatically registered by the exchange.

  FIG. 4A shows a case where the call partner is notified of his / her name. In the case of (a) in the figure, registration is performed for notifying one's own name when receiving a call in order to receive a call with peace of mind. In this example, Mr. Ichiro Yamada who is the user himself / herself transmits an attribute data registration request to the exchange. Here, a registration request is sent with the target registration number “090-1234-5678”, the notification information “Ichiro Yamada”, and the sharer “all users”. Then, the exchange accesses user information registered in the HLR, and registers the registrant in the Yamada attribute DB in the figure as “guarantee” indicating that the communication carrier company guarantees. This Mr. Yamada attribute DB is the incoming call notification information database 210.

  FIG. 4B shows a case where the attribute information is shared by an acquaintance. In the case of FIG. 5B, Mr. Ichiro Yamada who received a persistent solicitation by telephone performs registration for sharing the information with his mother “Haha Yamada” and his friend “Jiro Tanaka”. In this example, Mr. Ichiro Yamada who is the user himself / herself transmits an attribute data registration request to the exchange. Here, the target registration number is “090-1122-3344”, the notification information is “attention and persistent solicitation”, the shared person is Yamada Haha's telephone number “090-4321-4477”, and Tanaka Jiro's telephone number “090-1212”. -9999 "is sent. Then, the exchange is registered in the incoming call notification information database 210 with the registrant as the “principal” as in the case of FIG.

  In addition, the target registration number “090-1122-3344” and the notification information “attention / stubborn solicitation” are registered in the incoming notification information database of Yamada Haha registered as a sharer. However, they are registered only when the telephone number “090-1234-5678” of Yamada Ichiro is registered in the allowed sharer table of Yamada Haha.

Similarly, the target registration number “090-1122-3344” and the notification information “attention and persistent solicitation” are registered in the incoming notification information database of Jiro Tanaka registered as a sharer. However, they are registered only when the telephone number “090-1234-5678” of Ichiro Yamada is registered in the permitted sharer table of Jiro Tanaka.
Registration request with target registration telephone number “090-1234-8888”, notification information “XX company sales department: Ichiro's office”, and sharer Jiro Tanaka's telephone number “090-1212-9999” Similarly, the registrant is registered in the incoming call notification information database 210 as “person”.

  FIG. 6C shows a case where attribute information is shared by an acquaintance and a case where the attribute information is shared with a friend's attribute database. In the case of (c) in the figure, Jiro Tanaka (that is, a friend of Mr. Ichiro Yamada) who has received a so-called wire fraud call registers for sharing information with Mr. Ichiro Yamada to call attention. In this example, Mr. Jiro Tanaka sends an attribute data registration request to the exchange. Here, a registration request is sent with the target registration number “03-4455-6666” and the notification information “probably transfer”. Then, the exchange refers to Mr. Jiro Tanaka's incoming notification information database (friend attribute DB in the figure) and designates the registrant as “090-4321-4477” (that is, Mr. Jiro Tanaka's telephone number). Register at 210.

FIG. 4D shows a case where attribute information is shared by an acquaintance and is shared with a mother's attribute database. In the case of (d) in the figure, Hada Yamada, who wanted to let his son know that the call was from the hospital he was in, was registered so that his son, Ichiro Yamada, could share the hospital phone number. I do. In this example, Tanaka Haha transmits an attribute data registration request to the exchange. Here, a registration request is sent with the target registration number as “045-777-4444”, which is the telephone number of the hospital where the target registration number is located, and the notification information as “hospital where the mother is visited”. In addition, “Yamada Ichiro” is registered in the “Sharer” field of the hospital in the mother's incoming call notification information database.
The exchange that has received the registration request refers to the incoming notification information database of Yamada Haha (the mother attribute DB in the figure) and designates the registrant as “090-1212-9999” (in the same manner as in FIG. That is, it is registered in the incoming call notification information database 210 as the telephone number of Tanaka Haha).

(Notification processing)
FIG. 7 is a flowchart showing an example of notification processing by the present system.
In the figure, it is in a standby state until an incoming call is received by the user (step S21). If there is an incoming call, the telephone number of the calling user is acquired (step S22). Then, it is determined whether the acquired telephone number is registered as “target telephone number” in the incoming call notification information database (FIG. 2A) (step S23).
When the acquired telephone number is registered in the incoming call notification information database, the contents of the “notification information” corresponding to the “target telephone number” are notified to the destination user (steps S23 → S24). Note that it is desirable to notify the destination user using a C-Plane signal for call connection control. Thereafter, the process proceeds to call connection processing (steps S24 → S25).
On the other hand, if the acquired telephone number is not registered in the incoming call notification information database, the process directly proceeds to call connection processing (steps S23 to S25).

(Specific example of notification processing)
Next, a specific example of the notification process will be described with reference to FIG. This figure is a diagram showing an example of notification processing when registration in the incoming call notification information database is performed as shown in FIG. 6 described above.
FIG. 4A shows a case where the call partner is notified of his / her name. This corresponds to the case of registration as shown in FIG. From the communication device of Mr. Ichiro Yamada, the call is sent to the telephone number “090-1212-9999” of the communication device of his mother, Yamaha Haha. Then, attribute authentication processing is performed in the exchange. In this case, since the caller is Mr. Ichiro Yamada, the characters “090-1234-5678” and “incoming” are registered in the incoming notification information database (Mr. Yamada attribute DB in the figure). And the notification information “Ichiro Yamada” and “registrant: guarantee” corresponding to the target telephone number are displayed. Having seen this display, Haha Yamada can answer the call from his son with peace of mind.

FIG. 5B shows a case where attribute information is shared by acquaintances. This corresponds to the case of registration as shown in FIG. An unknown caller makes a call to the telephone number “090-1212-9999” of Yamada Haha's communication device in order to make a persistent call invitation. Then, attribute authentication processing is performed in the exchange. In this case, the telephone number of the caller, that is, the target telephone number “090-1122-3344” is registered in the incoming call notification information database (the mother attribute DB in the figure). For this reason, the characters “090-1122-3344” and “incoming” are displayed on the screen of the mother's communication device, and the notification information corresponding to the target phone number “attention and persistent invitation” and “registration” Person: 090-1234-5678 "is displayed. It is also possible to provide a correspondence table between telephone numbers and names, convert the telephone numbers into names using this correspondence table, and display them instead of the registrant's telephone number. For example, “Registrant: Ichiro Yamada” may be displayed. Further, both the name of the registrant and its telephone number may be displayed. For example, “Registrant: Ichiro Yamada: 090-1234-5678” may be displayed.
Yamaha Haha, who sees these displays, can hang up the phone immediately, so there is no need to be bothered by persistent telephone invitations.

  FIG. 5C shows a case where attribute information is shared by an acquaintance and a case where the attribute information is shared with a friend's attribute database. This corresponds to the case of registration as shown in FIG. A wire fraudster sends a message to the telephone number “090-1234-5678” of Mr. Ichiro Yamada's communication device for fraud. Then, attribute authentication processing is performed in the exchange. In this case, the caller's telephone number, that is, the target telephone number “03-4455-6666” is registered in the incoming call notification information database (in the figure, Mr. Yamada attribute DB). For this reason, the characters “03-4455-6666” and “incoming” are displayed on the screen of the communication device of Mr. Ichiro Yamada, and the notification information “Transferable” and “ “Registrant: 090-4321-4477” is displayed. Mr. Ichiro Yamada, who saw this display, can hang up the phone immediately and avoid the damage caused by fraud.

  FIG. 4D shows a case where attribute information is shared by an acquaintance and is shared with a mother's attribute database. This corresponds to the case of registration as shown in FIG. The staff in charge of the hospital of his mother, Yamaha Haha, sends a message to the telephone number “090-1234-5678” of Mr. Ichiro Yamada's communication device for communication. Then, attribute authentication processing is performed in the exchange. In this case, the caller's telephone number, that is, the target telephone number “045-777-4444” is registered in the incoming call notification information database (Yamada attribute DB in the figure). For this reason, the characters “045-777-4444” and “incoming” are displayed on the screen of the communication device of Mr. Ichiro Yamada, and the notification information “hospital for mothers” corresponding to the target phone number and “Registrant: 090-1212-9999” is displayed. Mr. Ichiro Yamada who sees this display can recognize that it is a phone call about his mother and can answer the phone immediately.

(Summary)
By adopting the system described above, the following services can be realized.
(1) By designating an arbitrary telephone number and registering information for that number, registration information can be displayed from the next time onward without registering the telephone book.
For example, if you received an unpleasant call and you want to be careful from the next time, but you do not want to register the phone number of such a person in the phone book, notify the attribute information as described above. We can meet your needs. In addition, the phone number of the caller who received the call was not notified, so it cannot be registered in the phone book, but if you want to display information that warns you from the next time, notify the attribute information as above This can meet that demand. In this case, however, a function for discriminating a telephone number from a call history is required in a network-side device such as an exchange.

(2) The registered content can be reflected in a third party database. Since the telephone number of the registrant is also registered in the reflected person database, registration due to mischief can be prevented. For example, if you want to display your name on the other party's communication device when you make a call to someone who is not registered in the phone book, register your name, You can notify it. If you want to display only the name without displaying the number, because you received an unpleasant call, you want to share information with acquaintances to call attention, or if you want to register on behalf of someone who can not register the phone book yourself Such a request can be met by notifying attribute information.

(3) When a communication service carrier company guarantees a subscriber name of a telephone number and wants to display that it is guaranteed when an incoming call is received, the request can be met by notifying attribute information as described above. This guarantee is not a guarantee of the sender's identity but a guarantee of the telephone number contractor name. For example, if you want to prove yourself and want to protect an acquaintance from the damage of fraud that deceives you, you can respond to the request by notifying the attribute information as described above.

As mentioned above, although embodiment of this invention was described, this invention is not limited to the said embodiment, A various deformation | transformation is possible within the range of the technical thought. As modifications, for example, the following can be considered.
(1) In the above description, the database and the table are provided in the HLR. However, one or both of them may be provided in the exchange. Further, they may be provided anywhere in the communication network, not limited to within the HLR or the exchange.

(2) In the above description, the mobile phone is used as a communication device. However, the present invention can be similarly applied to a fixed phone. For example, the present invention can also be applied to a case where it is desired to display a name on an acquaintance's mobile phone so that the user can identify himself / herself even if he / she makes a call from a landline at his / her office, but he / she is bothered to register the phone book.
(3) In the above description, the attribute information registered in advance when a call is received has been described. However, the attribute information may be similarly notified for e-mail and Web access.

  The present invention can be used when notifying attribute information registered in advance when an incoming call is received.

It is a figure which shows the example structure of the incoming call notification information registration control system which concerns on embodiment of this invention. (A) is a diagram showing an example of an incoming call notification information database in which information to be notified at the time of incoming call is registered for each subscriber; (b) is a condition for registration in the incoming call notification information database; It is a figure which shows the example of the permissible sharer table where the information which becomes is registered. It is a figure which shows the example of a screen display for performing registration to an incoming call notification information database. It is a figure which shows the example of the table which matches and registers and manages a group name and a telephone number. It is a flowchart which shows the example of the registration process by this system. (A)-(d) is a flowchart which shows the example of the registration process by this system. It is a flowchart which shows the example of a notification process by this system. This figure is a diagram showing an example of notification processing when registration in the incoming call notification information database is performed as shown in FIG. 6 described above.

Explanation of symbols

1 Exchange 2 HLR
10, 20 Wireless cell 11, 12 Communication device 21, 22 Base station 31, 32 Base station controller 210 Incoming notification information database 220 Allowable sharer table

Claims (6)

  An incoming call notification information registration control system for controlling registration in a database in which information to be notified when a call is received from a caller side is registered for each user, and allows other users to be registered in the database An allowable sharer table in which information relating to information is registered, and a determination unit that determines whether a registration request is received from a user registered in the allowable sharer table when there is a registration request to the database, An incoming call notification information registration control system for registering information regarding a registration request from a user registered in an allowable sharer table.   2. The incoming call notification information registration control system according to claim 1, wherein, when there is a registration request from the user himself / herself to the database, the determination unit registers information regarding the registration request.   2. The incoming call according to claim 1, wherein when there is a registration request regarding a group to which a plurality of users belong, the determination unit sequentially determines whether the users belonging to the group are registered in the allowed sharer table. Notification information registration control system.   The information to be notified includes an ID on the sender side, a comment to be notified, and an ID of a person who has registered the information. The incoming call notification information registration control system described in 1.   5. The database according to any one of claims 1 to 4, wherein sharer information for registering the information in another user's database is set for each piece of information to be notified. The incoming call notification information registration control system according to the item.   An incoming notification information registration control method for controlling registration in a database in which information to be notified at the time of an incoming call to the user from the caller side is registered for each user, and when there is a registration request to the database, A step of determining whether or not the registration request is a registration request from a user registered in the allowable sharer table with reference to an allowable sharer table in which information related to other users permitted to be registered in the database is registered And a method of registering information on a registration request from a user registered in the allowable sharer table.

Images