JP2016019069A - Telephone number inspection method and system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To notify a telephone call receiver of attribute information of a telephone caller with confirmed reliability.SOLUTION: Telephone call origination including the telephone number of a receiver and the telephone number of a caller are received from a telephone terminal of the caller. The received telephone number of the caller is acquired. Attribute information of the caller is acquired based on the telephone number. A telephone exchange section transmits the call origination, the telephone number of the caller, and the attribute information of the caller to a telephone terminal of the receiver on the basis of the telephone number of the receiver. Consequently, the telephone call receiver obtains the reliable information of the caller, so as to safely talk on the telephone.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a technique for informing a receiver of information guaranteed by a telephone caller.

  In recent years, so-called “transfer scams” have occurred frequently, which make people believe that the call is from a financial institution or police station and take a large amount of cash. For example, when pretending to be a phone from a police station, the criminal declares the victim a fraud victim (hereinafter referred to as `` victim '') verbally as a phone call from the police, and makes the victim believe that the call is from the police station. There is a trick.

  Such “spoofing” can be avoided to some extent by notifying the recipient of the identity (corporate name, etc.) of the caller.

  For example, a caller telephone number notification service provided by a telecommunications carrier can display the caller's telephone number on the receiver's telephone when a call is received. In addition, the name of a corporation or the like registered in advance in the local phone book can be displayed by a phone book function (hereinafter referred to as “local phone book”) of the telephone itself.

  In addition, there is a function of blocking non-notification calls by a communication company or a telephone terminal. If you block all unannounced calls, calls from non-frauders will also be blocked, so a list of phone numbers to block calls (hereinafter referred to as `` black list '') is prepared in advance by the carrier and sent. Japanese Patent Application Laid-Open No. 2004-151867 discloses a technique for blocking communication only when a person's telephone number is included in the black list.

JP 2013-005205 A

  However, it is difficult to realize that all the latest nationwide telephone numbers are registered in advance in the receiver's telephone directory. In addition, when the call is blocked by the black list, the scammers can avoid this by using new phone numbers one after another, which is not a solution.

  In view of the above problems, an object of the present invention is to inform the receiver of the identity of the caller so that the receiver can deal more appropriately.

  In order to solve the above-mentioned problem, in the present invention, a call origination including the recipient's phone number and the caller's phone number are accepted from the caller's phone terminal, and the accepted caller's phone number is acquired. The caller's attribute information is acquired based on the telephone number, and the telephone exchange receives the call, the caller's telephone number, and the caller's attribute information based on the receiver's telephone number. To the phone terminal.

ADVANTAGE OF THE INVENTION According to this invention, a sender | caller's attribute information can be notified to a receiver and a receiver can recognize a sender | caller's identity more appropriately.

It is a functional block diagram which shows the example of 1 structure of the telephone number verification system concerning embodiment of this invention. It is a figure which shows the structural example of the communication carrier A System in FIG. It is a figure which shows the structural example of Verify System in FIG. It is a figure which shows the structural example of the corporate ledger system in FIG. It is a figure which shows the structural example of the communication carrier B System in FIG. It is a figure which shows the structural example of number conversion DB in FIG. It is a figure which shows the structural example of contractor attribute DB in FIG. It is a figure which shows the structural example of corporate ledger DB in FIG. It is a sequence diagram which shows the operation example of the telephone verification system of FIG. It is a sequence diagram which shows the operation example of the telephone verification system of FIG. It is a sequence diagram which shows the operation example of the telephone verification system of FIG.

  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 block diagram showing a configuration of a telephone verification system and related devices according to an embodiment of the present invention.

  In FIG. 1, a system 1 of a telecommunications carrier A in which a caller is subscribed to a telephone, a corporate ledger system 3, a certificate authority system 7, and a system 4 of a telecommunications carrier B in which a receiver is subscribed to a telephone are described. doing. When the communication carrier A system 1 of this example is transmitted from the caller terminal 5, the caller terminal 5 searches the caller attribute information based on the telephone number of the caller terminal 5, and notifies the receiver terminal 6 of the search result. It has a function to do. Referring to FIG. 1, a telecommunications carrier A System 1 in this example includes a World Wide Web (hereinafter referred to as WWW) server WWW 11, a Short Message Service Gateway (hereinafter referred to as SMS GW) SMS GW 12, and A telephone exchange 13, a number conversion DB 14, and a Verify System 2 are provided. The Verify System 2 includes a telephone number verification server 21, a contractor attribute DB 22, and a CVS 23.

  The corporate ledger system 3 according to the present embodiment includes a corporate search server 31 and a corporate ledger DB 32. The communication carrier B System 4 includes an SMS GW 41 and a telephone switch 42. The certificate authority system 7 includes a CRL (Certificate Revocation List) 72, a CA (Certificate Authority) 71, and a certificate DB 73.

  Each of these component devices can be realized by each CPU executing a program for realizing each function described later.

  Each configuration will be described below.

(WWW)
In the WWW 11, when there is a call from the caller terminal 5, the telephone number verification server 21 registers the caller's attribute information, and the call receiver terminal 6 related to the call is described in the SMS Message described later. The attribute information is disclosed in a state where it can be acquired based on the Uniform Resource Identifier (hereinafter referred to as “URI”). In addition to the method via the WWW 11, the notification method of the sender's attribute information is a means for describing the attribute information directly in the SMS Message and transmitting it to the receiver's terminal via the SMSGW 12 and the SMS GW 41 described later. Alternatively, it is also possible to store and notify the telephone message from the telephone exchange 13 to the telephone exchange 42 as a character string.

(SMS GW: Short Message Service Gateway)
When there is a call from the caller terminal 5, the SMS GW 12 notifies the receiver of the attribute information of the caller via the SMS GW 12 and the SMS GW 41. In addition, the notification method of a sender | caller's attribute information can also be notified via said WWW11 or the telephone switch 13 and the telephone switch 42 separately from the method via SMS GW12 and SMS GW41.

(Telephone switch)
The telephone switch 13 receives a call from the caller terminal 5 and performs a call operation to the receiver terminal 6 via the telephone switch 42. In addition, the telephone exchange 13 notifies the recipient of the attribute information of the sender sent from the telephone number verification server 21 via the telephone exchange 42. When the caller and the receiver are subscribed to the same carrier, the telephone switch 13 also serves as the telephone switch 42.

(Phone number verification server)
The telephone number verification server 21 receives the verification query from the telephone exchange 13 and searches the attribute information of the caller in a contractor attribute DB 22 to be described later. If the attribute information of the caller exists as a result of the search, the caller The recipient's attribute information is notified. When the attribute information of the sender does not exist as a result of the search, a verification query is transmitted to the corporate search server 31 of the corporate ledger system 3 to be described later to search for the attribute information of the sender on the corporate ledger system 3 to be described later. When there is no caller attribute information on the telecommunications carrier A System side, the corporate search server 31 receives a verification query from the telephone number verification server 21 and searches the corporate ledger DB 32 described below for the caller attribute information. . If the attribute information of the caller exists as a result of the search, the caller's attribute information is returned to the telephone number verification server 21. If the attribute information of the sender does not exist as a result of the search, a message to that effect is returned to the telephone number verification server 21.

(Number conversion DB)
A configuration example of the number conversion DB 14 is shown in FIG. In the figure, the number conversion DB 14 of this example is composed of items of a contractor telephone number and a representative telephone number. A phone number set by contract for a voice call. This telephone number is not limited to that of a mobile phone, but may be that of a fixed telephone. The telecommunications carrier A only needs to store the telephone number of its own contractor who becomes the caller, and can construct a number conversion DB from the contract of the own contractor. The number conversion DB 14 accepts processing for converting the mobile phone number of the caller and the representative phone number of the organization to which the caller belongs. For example, the telephone number verification server 21 transmits a verification query to the number conversion DB 14 using the mobile phone number of the caller as a key. As a result, when there is a representative telephone number associated with the mobile phone number, the representative telephone number is returned to the telephone number verification server 21. If the contractor attribute DB, which will be described later, stores attributes and the like for each telephone number, number conversion can be omitted.

(Contractor attribute DB)
A configuration example of the contractor attribute DB 22 is shown in FIG. In the figure, the contractor attribute DB 22 of this example is composed of items of representative telephone number, attribute, name, and certificate. A phone number set by contract for a voice call. This telephone number is not limited to that of a mobile phone, but may be that of a fixed telephone. The contractor attribute DB 22 receives the verification query from the telephone number verification server 21 and searches for the attribute information of the caller. If the attribute information of the caller exists as a result of the search, the attribute information and certificate of the caller are retrieved. It returns to the telephone number verification server 21. If the attribute information of the sender does not exist as a result of the search, a message to that effect is returned to the telephone number verification server 21. Here, the attributes include notary and bank, as well as business types such as police, city hall, XX school, XX store, and the like. Moreover, it is good also as occupations, such as a lawyer and a police officer, and you may combine affiliation and occupation. The name may be an individual name or a corporation. It may also be a department name within the company.

  The contractor attribute information is created by the telecommunications carrier or the guarantor confirming the identity of the applicant among the contractors of the company, and storing a certificate that guarantees the identity. Since it is an in-house contractor and only the applicant, it is not necessary to make it to all telephone holders including other telecommunications carriers. Here, it is assumed that those who have a useful identity guarantee for business purposes, such as public institutions and companies. The certificate may be an organization / corporation or an individual associated with the name, or may be a person of an organization / corporation to which the individual belongs.

(CVS: Certificate Validation Server)
After the telephone number verification server 21 receives the caller attribute information and certificate from the contractor attribute DB 22 or the corporate search server 31, the CVS 23 refers to the CRL 72 to be described later, and follows the procedure specified in RFC5280 (Chapter 6). To check whether the certificate is valid (hereinafter referred to as certificate verification). If the result is not valid, a message to that effect is returned to the telephone number verification server 21.

(Corporate ledger DB)
A configuration example of the corporate ledger DB 32 is shown in FIG. In the figure, the corporate ledger DB 32 of the present embodiment is configured by each item of a contractor telephone number, an attribute, a name, an address, and a certificate. The contractor telephone number is a telephone number set by contract for a voice call. This telephone number is not limited to that of a mobile phone, but may be that of a fixed telephone. This information is stored in the corporate ledger DB 32 when the operating organization of the corporate ledger DB 32 confirms that the organization / corporate etc. is properly operated through a predetermined procedure or when the individual is verified. Is done. You may impose eligibility to register in this DB, such as the soundness of operations and economic conditions, as conditions for confirmation. The certificate is renewed every predetermined period and the validity is maintained. When the certificate cannot be confirmed by the organization / corporate or the individual, the certificate is not renewed and expires. Also, certificates copied from this DB to other storage devices are similarly revoked when not updated. In the present embodiment, the certificate is also stored in the contractor attribute DB 22. The contractor attribute DB 22 is owned by a telecommunications carrier, and instead of being accessed quickly from a telecommunications carrier node such as the telephone number verification server 21, the validity of the certificate is insufficient or the legitimacy is high. The certificate may not be renewed. On the other hand, the corporate ledger DB stores a certificate that has been strictly examined and confirmed by its operating organization, updated regularly, and is highly reliable.

  The corporate ledger DB 32 receives the verification query from the corporate search server 31 and searches the attribute information of the caller. If the attribute information of the caller exists as a result of the search, the corporate ledger DB 32 sends the attribute information of the caller to the corporate search server 31. Send back. If the attribute information of the sender does not exist as a result of the search, the fact is returned to the corporate search server 31. Further, the attribute information registered in the corporate ledger DB 32 includes the certificate 73 acquired from the CA 71 which is a Certificate Authority (hereinafter referred to as “CA”), which will be described later by the corporation or the like (Ministry, Bank, etc.). It is provided that the attribute information is authentic by the operating organization of the corporate ledger DB.

(Sender terminal and receiver terminal)
In this example, the caller terminal 5 is a telephone terminal used by a caller of a telephone including a transfer fraud. In this example, the receiver terminal 6 is a telephone terminal used by a telephone receiver who is the target of a transfer fraud. The caller terminal 5 and the receiver terminal 6 are devices that have a predetermined telephone number and are capable of voice calls, and include a smartphone in addition to a normal mobile phone terminal. In addition, a fixed telephone may be used as long as predetermined information processing such as SMS and Web browsing is possible.

(CA: Certificate Authority)
The CA 71 is a certificate authority that issues a certificate 73 provided by the external organization to the corporate ledger DB 32 or a Certificate Revocation List (hereinafter referred to as CRL) 72 to be described later.

(CRL: Certificate Revocation List)
The CRL 72 is used to check whether the CVS 23 checks whether the attribute information of the caller received from the telephone number verification server 21 has expired. 509 is a certificate revocation list issued from the CA 71. In this system, the CRL 72 can be read as the revocation list.

(Operation sequence example of telephone verification system)
The outline of the operation of this system will be described below. In this system, the caller's attribute information is acquired during the call of the contractor (regardless of whether it is outgoing or incoming), and the caller's attribute information is converted into Hypertext Transfer Protocol Secure (hereinafter referred to as HTTPS) when the call ends. Notify the recipient via SMS or telephone exchange. When the attribute information of the sender is not registered in the contractor attribute DB 22 or the corporate ledger DB 32, the receiver is notified that the registration is not made at the end of the call.

  FIG. 9 is an operation sequence example showing the operation of the telephone verification system. In the figure, the caller terminal 5 sends a call request directed to the receiver together with the telephone number of the terminal itself to the telephone exchange 13 (step S1). The telephone exchange 13 makes a call to the telephone exchange 42 on the receiver side based on the telephone number of the call destination, and transmits the contractor's telephone number of the caller to the telephone number verification server 21 (step S2).

  The telephone number verification server 21 transmits the received contractor telephone number of the caller to the number conversion DB 14 (step S3). The number conversion DB 14 converts the contractor telephone number into a representative telephone number when there is a representative telephone number associated with the received contractor telephone number of the caller (step S4), and converts the representative telephone number into the telephone number. It returns to the verification server 21 (step S5). If the contractor telephone number is the same as the representative telephone number, a reply to that effect is sent or the contractor telephone number is returned as the representative telephone number. Note that when the contractor attribute DB 22 stores attributes and the like for each contractor telephone number as well as the representative telephone number, steps S3 to S5 are not required.

  The telephone number verification server 21 transmits the received representative telephone number to the contractor attribute DB 22 (step S6). The contractor attribute DB 22 searches the attribute information and certificate using the received representative telephone number as a key, and returns it when stored in the DB (step S7). If the attribute information and certificate are not found, a message to that effect is returned and the next steps S8 to 10 are omitted.

  The telephone number verification server 21 transmits the received certificate to the CVS 23 (step S8), and the CVS 23 performs certificate verification (step S9). The CVS 23 returns the certificate verification result to the telephone number verification server 21 (step S10). Here, when there is attribute information and the certificate has not expired, steps S12 to S14 are omitted, and the telephone number verification server 21 notifies the receiver of the attribute information of the sender via the telephone switch 13 ( Steps S15-16).

  If there is no attribute information or certificate, or if the certificate has expired, the telephone number verification server 21 searches the corporate ledger system 3 to retrieve the caller's attribute information. A representative telephone number is transmitted (step S11). The corporate search server 31 searches the corporate ledger DB 32 for the attribute of the caller using the received representative telephone number as a key (step S12). Here, when the attribute information of the caller does not exist in the corporate ledger DB 32, the fact is returned to the corporate search server 31. When the attribute information exists in the corporate ledger DB 32, the corporate ledger DB 32 informs the corporate search server 31. The sender attribute information and certificate are returned (step S13). The corporate search server 31 transmits the received caller attribute information and certificate to the telephone number verification server 21 (step S14).

  The telephone number verification server 21 transmits the received caller attribute information and certificate to the communication carrier with which the receiver has a contract via the telephone switch 13 (steps S15 → S16). Further, the telephone verification server 21 transmits the received attribute information and certificate to the contractor attribute DB 22 (step S17). The contractor attribute DB 22 registers the received attribute information and certificate (step S18).

  FIG. 10 is an example of an operation sequence showing an operation on the receiver side in the telephone verification system. In the figure, the calling side telephone exchange 13 sends a calling telegram for starting a call to the receiving side telephone exchange 42, and the telephone exchange 42 further sends it to the receiver terminal 6 (step S21). When the receiver presses the call button on the terminal 6, a call with the sender is started. Thereafter, the telephone exchange 13 that acquired the caller's attribute information transmits a calling telegram including the attribute information (step S22). The telephone exchange 42 transmits a call telegram including the received attribute information of the caller to the receiver terminal 6 (step S23). In this embodiment, a call telegram for starting a call and a call telegram for transmitting attribute information are transmitted separately. However, if the time for the telephone switch 13 to acquire attribute information is short, it is transmitted together. May be. In addition, the former may wait for the latter and transmit together.

  FIG. 11 is an example of an operation sequence showing an operation on the receiver side in the telephone verification system that transmits attribute information by SMS or Web. In the figure, the SMS GW 12 on the caller side transmits an SMS Message including the caller's telephone number and attribute information (step S24). The destination of the SMS message is specified by the SMS GW 12 by acquiring the recipient's telephone number from the outgoing call. The SMS GW 41 on the receiver side transmits an SMS Message including the received caller's telephone number and attribute information to the receiver terminal 6 (step S25). The recipient who has received the SMS Message can access the WWW server based on the URI included in the SMS Message to check the attribute information of the sender on the Web (HTTPS) (Steps S26 → S27). ).

  In any example, a certificate or information that the certificate is valid may be sent together with the attribute information. The recipient terminal that has received the attribute information may store it in the reception history information (the received telephone number and the reception date / time etc.) in association with the reception, or the address book (name / name, telephone number) The number or the like may be stored in association with the information of the caller in the memory. In addition, a profile that can be trusted by the caller (for a company, company profile, career, business details, etc.) may be transmitted.

  If the attribute of the sender is that of a trusted institution or company, the receiver can make a call with peace of mind. If the telephone number is stored in the telephone directory of the receiver terminal 6, the receiver terminal 6 displays the name together with the telephone number, and can make a call with confidence because the receiver knows the other party. If there is no attribute information and there is no registration in the phone book of the terminal, it is a call from a party whose identity is not guaranteed, so the recipient will be careful to answer the phone or not answer, so the possibility of fraud etc. is reduced .

  As described above, according to the present invention, since the information indicating the reliability of the caller is transmitted together with the transmission of the call, the call from a reliable organization or the like can be guaranteed and the possibility of fraud can be reduced.

1 Telecommunications carrier A System
11 WWW
12 SMS GW
13 Telephone exchange 14 Number conversion DB
2 Verify System
21 Telephone number verification server 22 Contractor attribute DB
23 CVS
3 Corporate Ledger System
31 Corporate Search Server 32 Corporate Ledger DB
4 Telecommunications carrier B System
5 Caller terminal 6 Receiver terminal 7 Certificate authority 71 CA
72 CRL
73 Certificate

Claims (9)

A telephone call accepting step in which the telephone exchange receives a call from the caller's phone terminal, including the caller's phone number, and the caller's phone number;
An attribute information acquisition step in which the telephone number verification unit acquires the telephone number of the caller accepted by the telephone exchange unit, and acquires the attribute information of the caller based on the telephone number;
Based on the recipient's phone number, the phone exchange unit sends the call, the caller's phone number, and the caller's attribute information to the recipient's phone terminal. Process,
Phone number verification method including. In claim 1,
The telephone exchange unit is a caller side telephone exchange unit, and in the call outgoing call exchange step, the telephone number verification is sent to the receiver side terminal via the receiver side telephone exchange unit Method. In claim 1 or 2,
In the sender information acquisition step, the certificate is acquired together with the attribute information,
In the call origination exchange step, the certificate or the validity of the certificate is sent together with the attribute information. In any one of Claims 1 thru | or 3,
Converting the telephone number into a representative telephone number of the caller;
In the attribute information acquisition step, the caller attribute information is acquired based on the representative phone number. In claim 3,
Including a certificate verification step of verifying the acquired certificate;
If the verification of the certificate is successful, send that the certificate or the certificate is valid,
A telephone number verification method, comprising: acquiring a new certificate when the verification of the certificate fails, and storing the new certificate in a storage unit in which the verified certificate is stored. In any one of Claims 1 thru | or 5,
A telephone number verification method for sending the call, sending the caller's telephone number, and then sending the caller's attribute information. In any one of Claims 1 thru | or 5,
The telephone exchange unit, after obtaining the caller attribute information, sends the call origination, the caller telephone number, and the caller attribute information based on the recipient phone number A phone number verification method characterized by In any one of Claims 1 thru | or 7,
The telephone number verification method, wherein the attribute information of the inventor is transmitted to the recipient's terminal by SMS Message or Web. A telephone exchange unit that accepts a call transmission including the telephone number of the recipient from the telephone terminal of the caller, and the telephone number of the caller;
A telephone number verification unit that acquires the telephone number of the caller accepted by the telephone exchange unit, and acquires attribute information of the caller based on the telephone number;
With
The telephone exchange unit sends the call origination, the caller's phone number, and the caller's attribute information to the recipient's phone terminal based on the recipient's phone number;
That the phone number verification system.

Images