JP2016174321A - Call control device, call control method, program, storage device, and call control data - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the number of databases to be managed while achieving both of the conversion of an origination source number and the conversion of an origination destination number.SOLUTION: A call control device includes: a storage section for storing telephone set information included in the identification information of a telephone set before conversion, an attribute value indicating the attribute of the telephone set, and identification information after the conversion by associating them one another; an attribute value specification section for specifying the attribute value of an origination source on the basis of the identification information of an origination source of a call control signal; an origination source rewriting section for rewriting the identification information of the origination source of the call control signal into the identification information after conversion associated with the identification information and the attribute value specified by the attribute value specification section; and an origination destination rewriting section for rewriting the identification information of an origination destination of the call control signal into the identification information after conversion associated with the identification information and the attribute value specified by the attribute value specification section.SELECTED DRAWING: Figure 7

Description

  The present invention relates to a call control device, a call control method, a program, a storage device, and call control data.

  Patent Document 1 describes an example of a technique for converting a telephone number of a caller in an IP (Internet Protocol) telephone system. In the technique described in Patent Document 1, a destination telephone number is converted by referring to the calling number conversion database based on the telephone number of the transmission source. Patent Document 2 describes an example of a technique for performing both conversion of a caller telephone number and conversion of a callee telephone number in an IP telephone system. In the technique described in Patent Document 2, the caller telephone number is converted by referring to the called number conversion database based on the callee telephone number. Moreover, in the technique described in Patent Document 2, the destination telephone number is converted by referring to the calling number conversion database based on the source telephone number.

WO 98/41042 Pamphlet JP 2007-150711 A

  With the technique described in Patent Document 1, it is not possible to convert the telephone number of the call destination. On the other hand, in the technique described in Patent Document 2, it is possible to convert the telephone number of the caller and the callee, but for the conversion of the phone number of the callee and the database used for conversion of the caller telephone number. A database to be used is provided separately. For this reason, there is a problem that the number of databases to be managed increases and the resource consumption is large.

  An object of the present invention is to provide a call control device, a call control method, a program, a storage device, and call control data that solve the above-described problems.

  In order to solve the above problem, a call control device according to an aspect of the present invention associates telephone information included in identification information of a telephone before conversion, an attribute value indicating a telephone attribute, and identification information after conversion. Based on the identification information of the source of the call control signal, the attribute value specifying unit for specifying the attribute value of the source of the call control signal, the identification information of the source of the call control signal, and the identification information The identification information and the attribute value specifying unit specify the source rewriting unit that rewrites the converted identification information associated with the attribute value specified by the attribute value specifying unit, and the identification information of the call control signal transmission destination. A destination rewriting unit that rewrites the converted identification information associated with the attribute value.

  The call control method according to an aspect of the present invention also includes a storage unit that associates and stores telephone information included in telephone identification information before conversion, an attribute value indicating telephone attributes, and identification information after conversion. And identifying the attribute value of the source of the call control signal based on the identification information of the source of the call control signal, and identifying the identification information of the source of the call control signal with the attribute value identified with the identification information And rewriting the identification information of the destination of the call control signal with the identification information after conversion associated with the identification information and the specified attribute value. .

  In addition, the program according to one aspect of the present invention uses a storage unit that stores telephone information included in identification information of a telephone before conversion, an attribute value indicating a telephone attribute, and identification information after conversion in association with each other. And identifying the attribute value of the sender based on the identification information of the sender of the call control signal and associating the identification information of the sender of the call control signal with the identified attribute value and the identified attribute value. And rewriting the identification information of the destination of the call control signal to the identification information after conversion associated with the identification information and the specified attribute value. Let

  A storage device according to one embodiment of the present invention is a storage device that associates and stores telephone information included in identification information of a telephone before conversion, an attribute value indicating a telephone attribute, and identification information after conversion. A source conversion record in which the telephone information included in the identification information of the transmission source before conversion, the attribute value of the telephone of the transmission source, and the identification information after conversion of the transmission source are associated; Phone number information included in the identification information of the call destination, the attribute value of the caller of the call source, and the call destination conversion record associated with the converted identification information of the call destination.

  The call control data according to one aspect of the present invention has a structure in which telephone information included in telephone identification information before conversion, attribute values indicating telephone attributes, and identification information after conversion are associated with each other. Caller conversion data that is call control data and includes telephone information included in the identification information of the caller before conversion, the attribute value of the caller of the caller, and identification information after conversion of the caller A record, phone information included in the identification information of the destination before conversion, an attribute value of the telephone of the source, and a destination conversion record in which the identification information after conversion of the destination is associated.

  According to at least one aspect described above, the number of databases to be managed can be reduced while realizing both source number conversion and destination number conversion.

It is a block diagram for demonstrating the structural example of the call processing server apparatus which concerns on one Embodiment of this invention. It is a flowchart which shows the operation example of the call processing server apparatus 20 shown in FIG. 1 with FIG. 2B. It is a flowchart which shows the operation example of the call processing server apparatus 20 shown in FIG. 1 with FIG. 2A. It is explanatory drawing which showed the structural example of the subscriber management DB (database) part 22 shown in FIG. It is explanatory drawing which showed the structural example of the number conversion management DB part 23 shown in FIG. It is explanatory drawing which showed the specific example of the communication content in the flowchart shown to FIG. 2A and 2B. It is explanatory drawing which showed the other specific example of the communication content in the flowchart shown to FIG. 2A and 2B. It is the block diagram which showed the basic composition of the call control apparatus which concerns on one Embodiment of this invention. 1 is a configuration diagram showing a basic configuration of a storage device according to an embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a configuration diagram for explaining a configuration example of a call processing server device which is an embodiment of a call control device of the present invention.

  The call processing server device 20 shown in FIG. 1 is a computer, and includes hardware such as a CPU (Central Processing Unit), a main storage device, an auxiliary storage device, a communication device, and an input / output device. The call processing server device 20 implements a predetermined function related to call control by executing a predetermined program using those hardware.

  The call processing server device 20 includes a main processing unit 21, a subscriber management DB unit 22, and a number conversion management DB unit 23. The call processing server device 20 is connected to the call processing network 11 on the calling side. In this case, the call processing network 11 on the calling side is a private network. An extension telephone 10 is connected to the call processing network 11 on the calling side. A call processing network 12 on the called side is connected to the call processing network 11 on the calling side. The call processing network 12 on the called side is a public network. A telephone 13 is connected to the call processing network 12 on the called side.

  In the present embodiment, the call processing server device 20 functions as part of a network configuration for establishing a call using a SIP (Session Initiation Protocol) communication protocol. FIG. 1 shows an example of communication signals transmitted / received when a call is established using the extension telephone 10 as a calling telephone and the telephone 13 as a called telephone. In general, in the procedure for establishing a call using the SIP communication protocol, an INVITE request signal is delivered from the calling telephone to the called telephone through the call processing network on the calling side and the call processing network on the called side. There is a need to. If the calling phone user is a subscriber of a different carrier, the calling call processing network is operated by the calling carrier, and the called call processing network is the called communication. It is operated by a business operator. For this reason, FIG. 1 separately shows the call processing network 11 on the calling side and the call processing network 12 on the called side.

  In FIG. 1, a call processing network 11 on the calling side is a call processing network of an extension network, and accommodates an extension telephone 10 assigned an extension number. The call processing network 12 on the called side is a public call processing network and accommodates a telephone set 13 to which a telephone number is assigned.

  The call processing server device 20 includes all the functional requirements of SIP proxy, SIP registrar, and SIP redirect server whose functional requirements are defined in IETF (Internet Engineering Task Force) RFC (Request For Comment) 3261 (2002-06). Alternatively, it is a device that implements some functions. In this case, the call processing server device 20 has an INVITE request signal routing function and a subscriber information management function accommodated in the call processing network 11 on the calling side.

  The call processing server device 20 is a device that transmits and receives an INVITE request signal and relays it, and performs telephone number conversion processing for the INVITE request signal in the call processing network 11 on the calling side. The main processing unit 21 included in the call processing server device 20 transmits and receives an INVITE request signal to and from the outside of the call processing server device 20. The subscriber management DB unit 22 holds in advance information on telephones / subscribers accommodated in the call processing network 11 on the calling side. The number conversion management DB unit 23 holds in advance information necessary for conversion between the calling number and the called number.

  FIG. 3 shows a specific example of the table configuration of the database of the subscriber management DB unit 22. This table is for the purpose of designating the calling subscriber by “subscriber URI (Uniform Resource Identifier) information” and obtaining “subscriber location / group ID (identifier)” associated with the designation. Exists. That is, the subscriber management DB unit 22 returns data representing “subscriber's location / group ID” corresponding to the search key information in response to an inquiry using “subscriber URI information” as search key information. .

  The “subscriber URI information” is an identifier that uniquely identifies the subscriber, and includes a telephone number and a domain identifier. The telephone number only needs to be unique for each domain, and if the domains are different, the telephone numbers may overlap. For example, the extension number is unique for each company, and if the companies are different, the extension numbers may overlap. The domain is also called a domain name, and is a name that identifies a node such as a computer, a terminal device, or a communication control device on a network such as the Internet.

  The “subscriber location / group ID” is an identifier for specifying the geographical location of the telephone and the group of the extension telephone. Each extension telephone is assigned one location ID and one group ID. Here, the position ID is an identifier that uniquely identifies the position. The group ID is an identifier that uniquely identifies the group.

  In the example shown in FIG. 3, for example, “sip: 51-1001@company1.com” is stored in the “subscriber URI information” field of the top record. This “sip: 51-1001@company1.com” is an identifier that uniquely identifies the subscriber. In addition, among “sip: 51-1001@company1.com”, “51-1001” before the delimiter (or delimiter) “@” excluding “sip:” is the calling telephone number, and the delimiter “Company1.com” after the symbol “@” is a domain.

  Further, “3001; 3901” is stored in the “subscriber position / group ID” field of the top record. Among “3001; 3901”, “3001” before the delimiter “;” is the position ID, and “3901” after the delimiter “;” is the group ID.

  FIG. 4 shows a specific example of the table configuration of the database of the number conversion management DB unit 23. This table exists for two uses. The first point is a purpose of specifying the special number type and the position ID and acquiring the converted URI information associated with the specification. The second point is a purpose of specifying the domain type and group ID and acquiring the converted URI information associated with the specification. Therefore, the number conversion management DB unit 23 of the present embodiment configures a database as follows. That is, the database of the number conversion management DB unit 23 includes a table including the following first field 232, second field 233, and third field 234 in each record 231.

  The first field 232 is a “special number / domain type” field, and stores either the special number type or the domain type. The special number type is data representing a special number. The special number is also called a special number, and is a telephone number for a different use from a normal telephone number. Domestic phone numbers start with 0 or 1. However, the area code is not a special number. Also, the business operator identification number for selecting the telephone company to connect to is not a special number. The special number includes an emergency (report) special number which is a three-digit special number “110”, an outside special number which is a one-digit special number “0”, and the like. The special number type stored in the first field 232 includes, for example, 1 to 4 digits representing the special number. The domain type is data representing the above-described domain. The domain type may be the domain itself, or may be composed of a part of data necessary for uniquely specifying the URI information in the domain. That is, the domain type is composed of a part or all of the above-described domain.

  The second field 233 is a “position / group ID” field, and stores either the position ID or the group ID. The location ID and group ID are the same as those stored in the database of the subscriber management DB unit 22 described with reference to FIG. For example, in the same record 231, when the first field 232 stores the special number type, the second field 233 stores the position ID. In the same record 231, when the first field 232 stores the domain type, the second field 233 stores the group ID.

  The third field 234 is a field of “URI information after conversion”, and stores the URI information after conversion. There are two types of “converted URI information” stored in the third field 234: a case where the URI information of the transmission destination is represented and a case where the URI information of the transmission source is represented. The type of “URI information after conversion” stored in the third field 234 differs depending on whether the data stored in the first field 232 of the same record 231 is a special number type or a domain type. The “converted URI information” stored in the third field 234 is associated with the data stored in the first field and the data stored in the second field. That is, when the first field 232 of the same record 231 stores the special number type, the third field 234 indicates the special number transmission destination corresponding to the special number type of the first field 232 and the position ID of the second field 233. Stores URI information representing a telephone number. When the first field 232 of the same record 231 stores the domain type, the third field 234 is a representative number of the sender corresponding to the domain type of the first field 232 and the group ID of the second field 233. Is stored.

  The number conversion management DB unit 23 extracts the converted URI information using the special number type and the position ID as search key information or the domain type and group ID as the search key information as follows. That is, the call processing server device 20 performs a process for making an incoming call to the nearest emergency organization in the case of a call to an emergency special number. For this reason, the number conversion management DB unit 23 responds to an inquiry using the “special number type” and “position ID” from the main processing unit 21 as key information for search, and indicates “post-conversion” indicating the telephone number of the nearest emergency organization. "URI information". In addition, the call processing server device 20 performs a process of notifying the representative telephone number as the calling telephone number in association with the “domain type” and the “group ID” when calling from the extension telephone. Do. For this reason, the number conversion management DB unit 23 responds to an inquiry from the main processing unit 21 using the “domain type” and the “group ID” as search key information, and displays “converted URI information” representing the representative number. Send back.

  In the example shown in FIG. 4, “110” is stored in the first field 232 of the record 231a. This “110” is a special number type. In the second field 233 of the record 231a, “3001” is stored. This “3001” is a position ID. In the third field 234 of the record 231a, “sip: 03-0000-0001@public.jp” is stored. This “sip: 03-0000-0001@public.jp” is URI information associated with the special number type “110” and the position ID “3001”. “Sip: 03-0000-0001@public.jp” stored in the third field 234 is data representing the telephone number of the nearest emergency organization, for example. In this case, “03-0000-0001” is the telephone number of the nearest emergency organization.

  Further, in the example illustrated in FIG. 4, “company1.com” is stored in the first field 232 of the record 231b. This “company1.com” is a domain type. In the second field 233 of the record 231b, “3901” is stored. This “3901” is a group ID. In the third field 234 of the record 231b, “sip: 03-9000-0001@public.jp” is stored. This “sip: 03-9000-0001@public.jp” is URI information associated with the domain type “company1.com” and the group ID “3901”. “Sip: 03-9000-0001@public.jp” stored in the third field 234 is, for example, data representing a representative number on the calling side. In this case, “03-9000-0001” is the representative number.

  3 and 4, the symbol “-(hyphen)” included in the URI information is a notation for readability and may not be set in an actual communication signal.

  Further, the number conversion management DB unit 23 determines whether the data stored in the first field 232 is the special number type or the domain type based on the content or format of the data stored in the first field 232. be able to. For example, when the data stored in the first field 232 includes a delimiter “.” (Period) in a character string representing a domain, the number conversion management DB unit 23 determines that the data is a domain type. be able to. Alternatively, for example, when the data stored in the first field 232 is a 1 to 4 digit number starting from “0” or “1”, the number conversion management DB unit 23 is the special number type. Can be determined. The data stored in each field may be a character string (including a numeric string) itself, or may be data obtained by performing a predetermined conversion process, compression process, etc. on the character string.

  Next, the operation of the call processing server device 20 will be described with reference to FIGS. 2A and 2B. Note that the flowchart shown in FIG. 2A and the flowchart shown in FIG. 2B are respectively coupled by connectors A21, A22, and A23. Hereinafter, a case where the extension telephone 10 performs an outside line transmission in the configuration shown in FIG. 1 will be described.

  The extension telephone 10 transmits the pre-number conversion INVITE request 30 with the intention of calling the outside line. In the pre-number conversion INVITE request 30, a “Request-URI” parameter indicating a transmission destination and a “P-Asserted-Identity” parameter indicating a transmission source are set.

  In addition, since the value of a parameter may be misrepresented by the user of the extension telephone 10 when the “P-Assessed-Identity” parameter indicating the transmission source is given by the extension telephone 10, the following configuration may be used. That is, a call processing server device (not shown) that relays the pre-number conversion INVITE request 30 is arranged in the call processing network 11 on the calling side, and the “P-Asserted-Identity” parameter is verified and assigned by the call processing server device. There is also a case. A description of the verification mechanism is omitted.

  The call processing server device 20 receives the pre-number conversion INVITE request 30 (S101), and the main processing unit 21, the subscriber management DB unit 21, and the number conversion management DB unit 23 perform the following processing.

  The main processing unit 21 acquires “URI information of the calling subscriber” from the received “P-Asserted-Identity” parameter, and inputs the “URI information of the calling subscriber” to the subscriber management DB unit 22 ( S102, IN # 31). Here, the number following “S” represents the step number. The number following “IN #” or “OUT #” described later represents the number of information to be transmitted / received.

  The subscriber management DB unit 22 identifies the corresponding “location / group ID of the calling subscriber” using the “URI information of the calling subscriber” input from the main processing unit 21 as search key information, and the main processing unit 21 (S103 to S104, OUT # 32).

  The main processing unit 21 specifies whether or not the outgoing call is intended for an outside line from the “Request-URI” parameter received in S101 (S105). In S <b> 105, the main processing unit 21 specifies that the outgoing call is an outgoing call when, for example, the special call number “0” is set as the URI prefix.

  When it is specified that the call is an outside line transmission (in the case of “Yes” in S105), the main processing unit 21 processes the received “Request-URI” parameter into a format distributed on the public network (S106). For example, the outside line special number “0” is deleted and the domain part of the URI is replaced with the domain of the public network. Subsequently, when it is specified that the call is an outside line transmission, the main processing unit 21 acquires the “domain type of the calling subscriber” from the received “P-Asserted-Identity” parameter (S107). The main processing unit 21 inputs the “calling subscriber domain type” and the “calling subscriber group ID” acquired in S104 (OUT # 32) to the number conversion management DB unit 23 (S107, IN # 33). .

  In S107, the main processing unit 21 may acquire the domain type of the calling subscriber from a parameter different from the “P-Asserted-Identity” parameter. For example, when the “P-Private-Network-Indication” parameter defined in IETF RFC 7316 (2014-07) is set in the INVITE request, the domain type can be acquired from this parameter.

  Subsequently, the number conversion management DB unit 23 corresponds to the “converted URI information” using the “originating subscriber domain type” and the “calling subscriber group ID” input from the main processing unit 21 as search key information. And the obtained corresponding “converted URI information” is output to the main processing unit 21 (S108 to S109, OUT # 34).

  Subsequently, when it is specified that the call is an outside line transmission (in the case of “Yes” in S105), the main processing unit 21 sets the number so as to include the “URI information after conversion” acquired in S109 (OUT # 34). A “P-Asserted-Identity” parameter is set in the converted INVITE request signal 40 (S110). Finally, the setting value changed by this overwriting is the calling number that is notified to the callee as the representative number.

  Next, in the main processing unit 21, the destination is an emergency special number from the “Request-URI” parameter set in the pre-number conversion INVITE request 30 received in S101 or the post-number conversion INVITE request signal 40 processed in S110. Or not (S111). For example, when the URI after removing the outside line special number “0” is the emergency special number “110”, the main processing unit 21 specifies that the destination is the emergency special number.

  When it is specified that the destination is an emergency special number (in the case of “Yes” in S111), the main processing unit 21 obtains the “request-URI special number type” specified in S111 and S104 (OUT # 32). “Location ID of calling subscriber” is input to the number conversion management DB unit 23 (S112, IN # 35).

  The number conversion management DB unit 23 identifies the “converted URI information” using the “request-URI special number type” and the “subscriber location ID” input from the main processing unit 21 as search key information. Then, the obtained “converted URI information” is output to the main processing unit 21 (S113 to S114, OUT # 36).

  Subsequently, when it is specified that the call destination is an emergency special number (“Yes” in S111), the main processing unit 21 includes the “URI information after conversion” acquired in S114 (OUT # 36). Then, the “Request-URI” parameter is set in the INVITE request 30 before number conversion or the INVITE request signal 40 after number conversion (S115).

  The call processing server device 20 performs the following processing after performing the above processing by the main processing unit 21, the subscriber management DB unit 21, and the number conversion management DB unit 23. That is, the call processing server device 20 transmits the INVITE request signal 40 after number conversion after the above processing (or transmits it as the INVITE request signal 40 after number conversion without performing the conversion processing on the INVITE request 30 before number conversion). (S116).

  The number-converted INVITE request signal 40 transmitted in S116 finally reaches the telephone set 13 via a call processing server (not shown) arranged in the call processing network 12 on the called side. The telephone 13 displays the calling telephone number with reference to the received “P-Asserted-Identity” parameter.

  Next, a specific example of input / output parameters in the processing shown in FIGS. 2A and 2B will be described with reference to FIG. It is assumed that the subscriber management DB unit 22 stores the data shown in FIG. Further, it is assumed that the number conversion management DB unit 23 stores the data shown in FIG. FIG. 5 is a diagram showing a list of communication names, parameter names, setting values, and remarks or supplementary explanations for communication signals in the processing shown in FIGS. 2A and 2B.

  First, the extension telephone 10 transmits a pre-number conversion INVITE request 30 with the intention of calling an outside line (S101). In this example, as shown in FIG. 5, the pre-number conversion INVITE request 30 includes a “Request-URI” parameter “sip: 0-110 @ company1. com ”and a“ P-Asserted-Identity ”parameter“ sip: 51-1001 @ company1. com ”is set.

  The call processing server device 20 receives the pre-number conversion INVITE request 30 (S101), and the main processing unit 21, the subscriber management DB unit 21, and the number conversion management DB unit 23 perform the following processing.

  The main processing unit 21 receives the received “P-Asserted-Identity” parameter “sip: 51-1001 @ company1. com ”,“ URI information of calling subscriber ”“ sip: 51-1001 @ company1. com ”and the“ URI information of the calling subscriber ”“ sip: 51-1001@company1.com ”. com ”is input to the subscriber management DB unit 22 (S102, IN # 31).

  The subscriber management DB unit 22 receives the “URI information of the calling subscriber” “sip: 51-1001 @ company1. “com” as search key information, the corresponding “location / group ID of calling party” “3001; 3901” is specified and output to the main processing unit 21 (S103 to S104, OUT # 32, FIG. 3). .

  The main processing unit 21 receives the received “Request-URI” parameter “sip: 0-110 @ company1. com ”, it is specified whether or not the call is intended for an outside line (S105). In this example, the outside line special number “0” is set as the prefix of the URI, and the main processing unit 21 specifies that the outside line is transmitted (“Yes” in S105).

  When it is specified that the call is an outside line transmission, the main processing unit 21 receives the received “Request-URI” parameter “sip: 0-110 @ company1. com "is processed into a format distributed on the public network (S106). In this example, the outside line special number “0” is deleted, and the URI domain part “company1. com "to the public network domain" public. " ”com” is performed. The “Request-URI” parameter after processing is “sip: 110 @ public. com ".

  Subsequently, when it is specified that the outgoing line is outgoing, the main processing unit 21 receives the received “P-Asserted-Identity” parameter “sip: 51-1001 @ company1. com ”to“ domain type of calling subscriber ”“ company1. com "is acquired (S107). The main processing unit 21 sets the “domain type of the calling subscriber” “company1. com ”and“ Group ID of calling party ”“ 3901 ”acquired in S104 (OUT # 32) are input to the number conversion management DB unit 23 (S107, IN # 33).

  Subsequently, the number conversion management DB unit 23 receives the “domain type of calling subscriber” “company1. com ”and“ Group ID of calling party ”“ 3901 ”as search key information, the corresponding“ URI information after conversion ”“ sip: 03-9000-0001 @ public. com ”is output to the main processing unit 21 (S108 to S109, OUT # 34).

  Subsequently, when it is specified that the call is an outside line transmission, the main processing unit 21 acquires “URI information after conversion” “sip: 03-9000-0001 @ public.” Acquired in S109 (OUT # 34). com ”to the INVITE request signal 40 after number conversion, the“ P-Asserted-Identity ”parameter“ sip: 03-9000-0001 @ public. com "is set (S110). Note that this set value is finally the calling number notified as the representative number.

  Next, the main processing unit 21 processes the “Request-URI” parameter “sip: 110 @ public. com ”, whether or not the call destination is an emergency special number is specified (S111). In this example, since the telephone number of the URI after removing the outside line special number “0” is the emergency special number “110”, the destination is specified as the emergency special number (“Yes” in S111). In addition, a telephone number regarded as an emergency special number such as 110 is registered in advance in a predetermined storage device.

  When it is specified that the destination is an emergency special number, the main processing unit 21 specifies the “Request-URI special number type” “110” and the “location ID of the calling subscriber” acquired in S104 (OUT # 32). “3001” is input to the number conversion management DB unit 23 (S112, IN # 35).

  The number conversion management DB unit 23 uses the “request-URI special number type” “110” and “location ID of the calling subscriber” “3001” input from the main processing unit 21 as the search key information and the corresponding “ URI information after conversion ”“ sip: 03-0000-0001 @ public. com ”is output to the main processing unit 21 (S113 to S114, OUT # 36).

  Subsequently, when it is specified that the destination is an emergency special number, the main processing unit 21 obtains the “URI information after conversion” “sip: 03-0000-0001 @ public.” Acquired in S114 (OUT # 36). com ”in the INVITE request signal 40 after number conversion, the“ Request-URI ”parameter“ sip: 03-0000-0001 @ public. com "is set (S115).

  The call processing server device 20 performs the above processing by the main processing unit 21, the subscriber management DB unit 21, and the number conversion management DB unit 23, and then transmits the number converted INVITE request signal 40 (S116).

  The transmitted number-changed INVITE request signal 40 passes through a call processing server (not shown) arranged in the call processing network 12 on the called side, and finally the telephone set 13 “sip: 03-0000-0001 @ public. com ". Then, the telephone 13 “sip: 03-0000-0001 @ public. com ”is the received“ P-Asserted-Identity ”parameter“ sip: 03-9000-0001 @ public. com ”, the calling number display“ 03-9000-0001 ”is performed.

  Next, another specific example of input / output parameters in the processing shown in FIGS. 2A and 2B will be described with reference to FIG. It is assumed that the subscriber management DB unit 22 stores the data shown in FIG. Further, it is assumed that the number conversion management DB unit 23 stores the data shown in FIG. 6 is a diagram showing a list of communication names, parameter names, setting values, and remarks or supplementary explanations for the communication signals in the processing shown in FIGS. 2A and 2B, as in FIG. is there.

  First, the extension telephone 10 transmits a pre-number conversion INVITE request 30 with the intention of calling an outside line (S101). As shown in FIG. 6, the pre-number conversion INVITE request 30 includes a “Request-URI” parameter “sip: 0-09-9999-9999 @ ccompany2. com ”and a“ P-Asserted-Identity ”parameter“ sip: 51-1001 @ company2. com ”is set.

  The call processing server device 20 receives the pre-number conversion INVITE request 30 (S101), and the main processing unit 21, the subscriber management DB unit 21, and the number conversion management DB unit 23 perform the following processing.

  The main processing unit 21 receives the received “P-Asserted-Identity” parameter “sip: 51-1001 @ company2. com ”,“ URI information of calling subscriber ”“ sip: 51-1001 @ company2. com ”and the“ URI information of the calling subscriber ”“ sip: 51-1001 @ company2. com ”is input to the subscriber management DB unit 22 (S102, IN # 31).

  The subscriber management DB unit 22 receives the “URI information of the calling subscriber” “sip: 51-1001 @ company2. “com” as search key information, the corresponding “originating subscriber location / group ID” “3001; 3901” is specified and output to the main processing unit 21 (S103 to S104, OUT # 32).

  The main processing unit 21 receives the received “Request-URI” parameter “sip: 0-09-9999-9999 @ company2. com ”, it is specified whether or not the call is intended for an outside line (S105). In this example, the outside line special number “0” is set as the prefix of the URI, and is identified as an outside line transmission (“Yes” in S105).

  When it is specified that the call is an outside line transmission, the main processing unit 21 receives the received “Request-URI” parameter “sip: 0-09-9999-9999 @ company2. com "is processed into a format distributed on the public network (S106). In this example, the outside line special number “0” is deleted, and the URI domain part “company2. com "to the public network domain" public. " ”com” is performed. The “Request-URI” parameter after processing is “sip: 09-9999-9999 @ public. com ".

  Subsequently, when it is specified that the outgoing call is outgoing, the main processing unit 21 receives the received “P-Asserted-Identity” parameter “sip: 51-1001 @ company2. com ”to“ domain type of calling subscriber ”“ company2. com ”. The main processing unit 21 sets the “domain type of calling subscriber” “company2. com ”and“ Group ID of calling party ”“ 3901 ”acquired in S104 (OUT # 32) are input to the number conversion management DB unit 23 (S107, IN # 33).

  Subsequently, the number conversion management DB unit 23 receives the “domain type of the calling subscriber” “company2. com ”and“ Group ID of calling party ”“ 3901 ”as search key information, the corresponding“ URI information after conversion ”“ sip: 03-9001-1111 @ public. com ”is output to the main processing unit 21 (S108 to S109, OUT # 34).

  Subsequently, when it is specified that the call is an outside line transmission, the main processing unit 21 obtains “URI information after conversion” acquired in S109 (OUT # 34) “sip: 03-9001-1111 @ public. com ”in the INVITE request signal 40 after number conversion, the“ P-Asserted-Identity ”parameter“ sip: 03-9001-1111 @ public. com "is set (S110). Note that this set value is finally the calling number notified as the representative number.

  Next, the main processing unit 21 processes the “Request-URI” parameter “sip: 09-9999-9999 @ public. com ”, whether or not the destination is an emergency special number is specified. In this example, since the telephone number “09-9999-9999” of the URI after the outside line special number “0” is removed is not an emergency special number, the destination is identified as not being an emergency special number (“No” in S111). In addition, a telephone number regarded as an emergency special number such as 110 is registered in advance in a predetermined storage device.

  The call processing server device 20 performs the above processing by the main processing unit 21, the subscriber management DB unit 21, and the number conversion management DB unit 23, and then transmits the number converted INVITE request signal 40 (S116).

  The transmitted number-changed INVITE request signal 40 passes through a call processing server (not shown) arranged in the call processing network 12 on the called side, and finally the telephone set 13 “sip: 09-9999-9999 @ public. com ". Then, the telephone 13 “sip: 09-9999-9999 @ public. com ”is the received“ P-Asserted-Identity ”parameter“ sip: 03-9001-1111 @ public. com ”, caller number display“ 03-9001-1111 ”is performed.

  As described above, the call processing server device 20 of this embodiment shares a database with the function of “Called phone number conversion” and the function of “Called phone number conversion”. That is, the call processing server device 20 of the present embodiment can perform the function of “calling phone number conversion” and the function of “calling phone number conversion” with reference to the same DB. Accordingly, for example, it is not necessary to prepare a dedicated DB resource for the representative number notification service, and an efficient representative number notification service can be provided. “Called phone number conversion” is a function for converting an emergency special number into a phone number corresponding to the position of the terminal. “Caller number conversion” is a function for converting an extension number to a representative number of an outside line. The “representative number notification service” is the following service. In other words, in an IP telephone service where an external line is transmitted from an internal telephone, when an external line is transmitted from an internal telephone, a plurality of internal telephones are grouped and a common external telephone number is issued regardless of which of the internal telephones in the same group is transmitted. This is a service for notifying the telephone of the incoming side as a telephone number.

  Next, with reference to FIG.7 and FIG.8, the basic composition of embodiment which concerns on this invention is demonstrated. FIG. 7 is a schematic block diagram showing the basic configuration of the call control device. In the above-described embodiment, the configuration illustrated in FIG. 1 has been described as an embodiment of the call control device, but the basic configuration of the call control device is as illustrated in FIG. That is, the call control device 1 has a basic configuration of the storage unit 2, the attribute specifying unit 3, the source rewriting unit 4, and the destination rewriting unit 5.

  The storage unit 2 stores the telephone information 2-1 included in the identification information of the telephone before conversion, the attribute value 2-2 indicating the telephone attribute, and the identification information 2-3 after conversion in association with each other. The attribute value specifying unit 3 specifies the attribute value of the transmission source based on the identification information of the transmission source of the call control signal. The transmission source rewriting unit 4 rewrites the identification information of the transmission source of the call control signal into the converted identification information 2-3 associated with the identification information and the attribute value 2-2 specified by the attribute value specifying unit 3. . The destination rewriting unit 5 rewrites the identification information of the destination of the call control signal to the converted identification information 2-3 associated with the identification value and the attribute value 2-2 specified by the attribute value specifying unit 3. . Thereby, it is possible to reduce the number of databases to be managed while realizing both the conversion of the transmission source number and the conversion of the transmission destination number.

  FIG. 8 is a schematic block diagram showing the basic configuration of the storage device. In the above-described embodiment, the configuration illustrated in FIGS. 1, 3, and 4 has been described as an embodiment of the storage device, but the basic configuration of the storage device is as illustrated in FIG. 8. That is, the storage device 8 stores the telephone information included in the identification information of the telephone before conversion, the attribute value indicating the telephone attribute, and the identification information after conversion in association with each other. Further, the storage device 8 stores a transmission source conversion record 7 and a transmission destination conversion record 8. The transmission source conversion record 7 stores the telephone information included in the identification information of the transmission source before conversion, the attribute value of the transmission source telephone, and the identification information after conversion of the transmission source in association with each other. The destination conversion record 8 stores the telephone information included in the identification information of the transmission destination before conversion, the attribute value of the telephone of the transmission source, and the identification information after conversion of the transmission destination in association with each other. Thereby, it is possible to reduce the number of databases to be managed while realizing both the conversion of the transmission source number and the conversion of the transmission destination number.

  The embodiment of the present invention is not limited to the above. For example, the components shown in FIG. 1 can be integrated or divided as appropriate. In addition, a program executed by a processor included in each component can be distributed in part or in whole via a computer-readable recording medium or a communication line.

  The correspondence between the basic configuration according to the embodiment of the present invention shown in FIGS. 7 and 8 and the configuration of the above-described embodiment shown in FIGS. 1, 2A, 2B, 3 and 4 is as follows. Street. That is, the call processing server device 20 in FIG. 1 is an example of the call control device 1 in FIG. The number conversion management DB unit 23 in FIG. 1 is an example of the storage unit 2 in FIG. The calling number such as “51-1001” and the domain such as “company1.com” included in the “subscriber URI information” in FIG. 3 are examples of the telephone information 2-1 in FIG. “Subscriber position / group ID” in FIG. 3 is an example of the attribute value 2-2 in FIG. “URI information after conversion” in FIG. 4 is an example of identification information 2-3 after conversion in FIG. The pre-number conversion INVITE request signal 30 in FIG. 1 is an example of the call control signal in FIG. The processing of S102 to S104 by the main processing unit 21 and the subscriber management DB unit 22 in FIG. 2A is an example of the attribute value specifying unit 3 in FIG. The processing of S107 to S110 by the main processing unit 21 and the number conversion management DB unit 23 in FIG. 2A is an example of the source rewriting unit 4 in FIG. The processing of S111 to S115 by the main processing unit 21 and the number conversion management DB unit 23 in FIG. 2B is an example of the destination rewriting unit 5 in FIG. The number conversion management DB unit 23 in FIG. 1 is an example of the storage device 6 in FIG. A record 231a in FIG. 4 is an example of the destination conversion record 8 in FIG. And the record 231b of FIG. 4 is an example of the transmission source conversion record 7 of FIG. The subscriber management DB unit 22 in FIG. 1 is an example of the second storage unit of the present invention. Further, “subscriber URI information” in FIG. 3 is an example of telephone identification information before conversion according to the present invention.

DESCRIPTION OF SYMBOLS 1 Call control apparatus 2 Memory | storage part 2-1 Telephone information 2-2 Attribute value 2-3 Identification information 3 after conversion 3 Attribute value specific | specification part 4 Source rewriting part 5 Destination rewriting part 6 Storage device 7 Source conversion record 8 Call destination conversion record 11 Call processing network 12 on the calling side Call processing network 20 on the called side Call processing server device 21 Main processing unit 22 Subscriber management DB unit 23 Number conversion management DB unit

Claims (8)

A storage unit that associates and stores telephone information included in the identification information of the telephone before conversion, an attribute value indicating an attribute of the telephone, and identification information after conversion;
Based on the identification information of the source of the call control signal, an attribute value specifying unit for specifying the attribute value of the source,
A source rewriting unit that rewrites the identification information of the source of the call control signal with the converted identification information associated with the identification information and the attribute value identified by the attribute value identifying unit;
A call control device comprising: a destination rewriting unit that rewrites identification information of a destination of a call control signal to identification information after conversion associated with the identification information and the attribute value specified by the attribute value specifying unit. The call control device according to claim 1, wherein the storage unit stores the telephone information associated with the attribute value indicating position identification information and the telephone information associated with the attribute value indicating group identification information. . The storage unit stores the telephone information indicating a special number type, which is associated with the attribute value indicating position identification information, and the telephone information indicating a domain type, which is associated with the attribute value indicating group identification information. The call control device according to claim 2. A second storage unit for associating the identification information of the source of the call control signal with the attribute value of the source;
The attribute value specifying unit refers to the second storage unit, and specifies the attribute value of the caller based on the identification information of the caller signal transmission source. The call control device described. Using the storage unit that stores the telephone information included in the identification information of the telephone before conversion, the attribute value indicating the attribute of the telephone, and the identification information after conversion in association with each other,
Identifying the attribute value of the source based on the identification information of the source of the call control signal;
Rewriting the identification information of the originator of the call control signal to the converted identification information associated with the identification information and the identified attribute value;
Rewriting the identification information of the destination of the call control signal to identification information after conversion associated with the identification information and the specified attribute value. Using the storage unit that stores the telephone information included in the identification information of the telephone before conversion, the attribute value indicating the attribute of the telephone, and the identification information after conversion in association with each other,
Identifying the attribute value of the source based on the identification information of the source of the call control signal;
Rewriting the identification information of the originator of the call control signal to the converted identification information associated with the identification information and the identified attribute value;
A program for causing a computer to execute the step of rewriting identification information of a call control signal transmission destination with identification information after conversion associated with the identification information and the specified attribute value. A storage device that associates and stores telephone information included in identification information of a telephone before conversion, an attribute value indicating a telephone attribute, and identification information after conversion;
A telephone source conversion record in which the telephone information included in the identification information of the transmission source before conversion, the attribute value of the telephone of the transmission source, and the identification information after conversion of the transmission source are associated;
A storage device for storing telephone information included in identification information of a destination before conversion, an attribute value of the telephone of the source, and a destination conversion record in which identification information after conversion of the destination is associated. Call control data having a structure in which telephone information included in telephone identification information before conversion, attribute values indicating telephone attributes, and identification information after conversion are associated with each other,
A telephone source conversion record in which the telephone information included in the identification information of the transmission source before conversion, the attribute value of the telephone of the transmission source, and the identification information after conversion of the transmission source are associated;
Call control data including telephone information included in the identification information of the callee before conversion, the attribute value of the telephone of the caller, and the callee conversion record associated with the converted identification information of the callee .

Images