JP2008072290A - Network managing device and call processor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform route control considering the kind of a communication terminal as a speech communication partner, in communication between a communication terminal on a network and the communication as the speech communication partner thereof. <P>SOLUTION: A carrier network 10 includes a plurality of logical networks 10α to 10γ. An SIP server 16 having received a speech communication request message (INVITE message) from a calling-side communication terminal (CN21) to a called-side communication terminal (MIN 13 on the carrier network) extracts information regarding identification information of the MN and the kind of the CN from the speech communication request message and passes them to a network managing server 17. The network managing server specifies an interface ID of the MN from the identification information of the MN and constitutes a global address of the MN by using a subnet ID of a logical network corresponding to the kind of the CN. Consequently, route control over packets from the CN to the MN is performed which depends upon the logical specified network on the carrier network. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a network management device and a call processing device for managing incoming calls from communication terminals (telephones) existing on various types of networks, and in particular, performs communication using an IP (Internet Protocol) network. The present invention relates to a network management device and a call processing device for managing incoming calls to mobile communication terminals.

  Currently, there are various types of networks, and mobile communication terminals (for example, mobile phones) connected to a carrier network (cell phone network) are called from communication terminals (phones) on various networks. It is possible to receive a call (incoming call).

  A conventional telephone communication system will be described with reference to FIG. FIG. 11 is a diagram schematically illustrating an example of a communication system according to a conventional technique. In FIG. 11, a PE (Provider Edge Router) 610 is arranged at the edge on the core network (provider network) side, and a CE (Customer Edge Router) 620 is arranged at the edge on the customer network (customer network) side. A carrier network 600 is shown. The PE 610 can relay communication with various networks, and the mobile communication terminal 630 connects to the CE 620 to perform a call with a communication terminal connected to the various networks through the carrier network 600. Is possible.

  In FIG. 11, a mobile communication terminal 630 (for example, having a unique telephone number: 090-xxxx-xxx1) connected to the CE 620 is connected to a softphone terminal 110 (for example, a unique telephone number). Identification information: xxx @ dom), IP telephone 120 (for example, having a unique telephone number: 050-aaa-aaa1), and fixed telephone 310 (for example, a unique telephone number) connected to the fixed telephone network 300 Mobile phone 410 connected to the mobile phone network 400 (for example, having a unique telephone number: 090-yyyy-yyy2), an emergency connected to the emergency call line network 500 Reporting phone 510 (for example, 110 (for police reporting) and 11 (Fire, for emergency report) having a) the communication terminal and the call capable of performing states on various networks, such as are illustrated.

  On the other hand, VoIP (Voice over IP) is known as a technique for transmitting and receiving call data using an IP network such as the Internet. This VoIP is a technology that enables a call on an IP network, and at the same time, a technology that integrates an existing telephone service and an IP technology to enable a call between an existing telephone and a communication terminal on the IP network. is there. As a protocol for realizing VoIP, for example, H323 and SIP (Session Initiation Protocol) are known.

  As a telephone call technique using SIP, for example, Patent Document 1 below discloses a telephone charge discount method for managing charging. According to the technology disclosed in Patent Document 1, the SIP server device monitors calls made by user terminals existing on the IP network, and the call time that is the monitoring result is supplied to the discount service providing device. In the service providing device, a lottery is performed as to whether to provide a discount service for telephone charges. As a result of the lottery, a call fee discount service is performed for calls that have been selected for discount service provision.

The IPv6 address structure used in IP communication is described in Non-Patent Document 1 below, for example. FIG. 12 is a diagram illustrating an example of an IPv6 address structure according to the related art. As shown in FIG. 12, the IPv6 address is composed of a global routing prefix 2001, a subnet ID 2002, and an interface ID 2003. Note that the IPv6 address is a 128-bit identifier. In a normal unicast address, for example, an interface ID 2003 including the identifier of each communication terminal generated from a MAC (Media Access Control) address or the like is fixed to 64 bits. And the remaining 64 bits are requested to be assigned to the global routing prefix 2001 and the subnet ID 2002. Hereinafter, in this specification, when the global routing prefix 2001 is I, the subnet ID 2002 is S, and the interface ID 2003 is H, the IPv6 address may be described as [I | S | H].
Japanese Patent Laying-Open No. 2005-322981 (FIGS. 1 and 5) R. Hinden, S. Deering and E. Nordmark, “IPv6 Global Unicast Address Format”, RFC 3587, August 2003

  In FIG. 11 described above, the mobile communication terminal 630 can make calls to communication terminals on various types of networks, and at the same time, the mobile communication terminal 1300 can receive calls from various types of communication terminals on the network. Can be called. At this time, the communication terminals on various networks make a call to the unique telephone number (090-xxxx-xxx1) of the mobile communication terminal 6300, and the call is started.

  However, various types of networks in which a communication terminal on the calling side is present have various requirements relating to calls depending on the type. For example, since the softphone terminal 110 and the IP telephone 120 are connected to the Internet 100 using IP, it is desirable to perform throughput priority route control (or traffic control) as in conventional IP routing. On the other hand, the fixed telephone 310 and the mobile phone 410 are connected to an existing telephone network, and a short delay time equivalent to a call on the existing telephone network is provided so that the users of the fixed telephone 310 and the mobile telephone 410 do not feel uncomfortable. In order to realize this, it is desirable to perform route control (or traffic control) that minimizes the delay.

  In addition, for example, the usage fee paid by each user is significantly different from the use of various communication terminals such as the soft phone terminal 110, the IP phone 120, the fixed phone 310, and the mobile phone 410 described above. In consideration of services and charges provided by various communication terminals that make calls to the mobile communication terminal 630, a low charge and a low charge are required for a calling communication terminal that pays a high charge. It is desirable to realize a call with higher quality and less delay than the communication terminal on the calling side that receives a quality service so that the relationship between the charge and the service is balanced.

  Furthermore, the mobile communication terminal 630 may receive an incoming call from the emergency call telephone 510 (so-called emergency call callback). In such a callback, it is desirable that route control (or traffic control) be performed so that both throughput and delay have the highest priority.

  As described above, it is desirable that route control can be performed according to the requirements of various types of networks. However, in the conventional technology, the called mobile communication terminal 630 is identified by one piece of identification information, for example, IP communication. Is performed, the IP address of the called mobile communication terminal 630 is set as the destination address of the packet transferred from the calling communication terminal to the called communication terminal 630. Therefore, in the normal routing technique, the route of the packet transferred from the calling communication terminal to the called mobile communication terminal 630 is the same in the carrier network 600 regardless of the type of the calling communication terminal. There is a problem of being aggregated in the route.

  As a conventional technique for performing the above-described throughput control and delay control, a QoS (Quality of Service) technique is known, which is performed between the mobile communication terminal 630 and various communication terminals. Since communication is a voice call, there is a problem that all communication is accommodated in the same QoS class.

  Further, Patent Document 1 discloses a charging management technique in communication using SIP, but this technique is used when a call of the mobile communication terminal 630 existing in the carrier network 600 is terminated. It is used to determine whether or not to discount a charge that accompanies a call, and the usage fee of the calling communication terminal when the mobile communication terminal 630 existing in the carrier network 600 receives an incoming call. Is not considered. Furthermore, the technique disclosed in Patent Document 1 is a route that takes into account the type of network (the type of communication terminal that is the call partner) in which the communication terminal that is the call partner of the mobile communication terminal 630 in the carrier network 1000 exists. It does not control.

  In view of the above problems, when the communication terminal in the carrier network makes a call with the communication terminal on various networks, the network type of the communication terminal (the type of the communication terminal) as the communication partner An object of the present invention is to provide a network management device and a call processing device that can perform route control in consideration of the above.

In order to achieve the above object, a network management device of the present invention is a network management device that manages a predetermined management network,
Interface ID management means for managing an interface ID of a communication terminal connected to the management network;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
Subnet ID specifying means for specifying a subnet ID corresponding to the type of communication terminal on the calling side received by the address inquiry receiving means with reference to information managed by the subnet ID management means;
As a response to the address inquiry received by the address inquiry receiving means, information including at least the subnet ID specified by the subnet ID specifying means and the interface ID specified by the interface ID specifying means is the call processing device. First address information notifying means for notifying to,
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal. ,
Have.
With the above configuration, when a communication terminal connected to a predetermined carrier network receives a call from a communication terminal serving as a communication partner, the calling side serves as the global address of the called communication terminal. By assigning global addresses having different subnet IDs according to the types of communication terminals, it is possible to realize packet transfer path control according to the types of communication terminals on the calling side within the carrier network. It becomes possible.

In order to achieve the above object, the network management device of the present invention is a network management device that manages a predetermined management network,
Interface ID management means for managing an interface ID of a communication terminal connected to the management network;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
Subnet ID specifying means for specifying a subnet ID corresponding to the type of communication terminal on the calling side received by the address inquiry receiving means with reference to information managed by the subnet ID management means;
As a response to the address inquiry received by the address inquiry reception unit, information including at least a subnet ID representing the management network and an interface ID specified by the interface ID specifying unit is notified to the call processing device. First address information notifying means;
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal;
Address management means for managing the subnet ID specified by the subnet ID specifying means and the interface ID of the communication terminal on the called side in association with each other;
Have.
With the above configuration, when a communication terminal connected to a predetermined carrier network receives a call from a communication terminal serving as a communication partner, the calling side serves as the global address of the called communication terminal. By assigning global addresses having different subnet IDs according to the types of communication terminals, it is possible to realize packet transfer path control according to the types of communication terminals on the calling side within the carrier network. It becomes possible. Furthermore, the global address of the called communication terminal can be made independent of the connection point, and the information related to the connection point of the called communication terminal can be hidden from the calling communication terminal. Is possible.

In order to achieve the above object, the network management device of the present invention is a network management device that manages a predetermined management network,
An interface ID / connection point management means for managing an interface ID of a communication terminal connected to the management network and a current connection point of the communication terminal;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and connection points of the management network and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
With reference to the information managed by the interface ID management means, the current connection point of the called communication terminal is identified from the identification information of the called communication terminal received by the address inquiry receiving means. Connection point identification means to
Referring to the information managed by the subnet ID management means, based on the connection point specified by the connection point specifying means and the type of the communication terminal on the calling side received by the address inquiry receiving means Subnet ID specifying means for specifying the subnet ID to be performed;
As a response to the address inquiry received by the address inquiry receiving means, information including at least the subnet ID specified by the subnet ID specifying means and the interface ID specified by the interface ID specifying means is the call processing device. First address information notifying means for notifying to,
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal. ,
Have.
With the above configuration, when a communication terminal connected to a predetermined carrier network receives a call from a communication terminal serving as a communication partner, the calling side serves as the global address of the called communication terminal. By assigning global addresses having different subnet IDs according to the types of communication terminals, it is possible to realize packet transfer path control according to the types of communication terminals on the calling side within the carrier network. It becomes possible. In addition, since the subnet ID and the connection point are associated with each other, the route control is surely performed even when the carrier network has a multi-level hierarchical structure or when there are many connection points. Can be done.

In order to achieve the above object, the network management device of the present invention is a network management device that manages a predetermined management network,
An interface ID / connection point management means for managing an interface ID of a communication terminal connected to the management network and a current connection point of the communication terminal;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and connection points of the management network and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
With reference to the information managed by the interface ID management means, the current connection point of the called communication terminal is identified from the identification information of the called communication terminal received by the address inquiry receiving means. Connection point identification means to
Referring to the information managed by the subnet ID management means, based on the connection point specified by the connection point specifying means and the type of the communication terminal on the calling side received by the address inquiry receiving means Subnet ID specifying means for specifying the subnet ID to be performed;
As a response to the address inquiry received by the address inquiry reception unit, information including at least a subnet ID representing the management network and an interface ID specified by the interface ID specifying unit is notified to the call processing device. First address information notifying means;
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal;
Address management means for managing the subnet ID specified by the subnet ID specifying means and the interface ID of the communication terminal on the called side in association with each other;
Have.
With the above configuration, when a communication terminal connected to a predetermined carrier network receives a call from a communication terminal serving as a communication partner, the calling side serves as the global address of the called communication terminal. By assigning global addresses having different subnet IDs according to the types of communication terminals, it is possible to realize packet transfer path control according to the types of communication terminals on the calling side within the carrier network. It becomes possible. In addition, since the subnet ID and the connection point are associated with each other, the route control is surely performed even when the carrier network has a multi-level hierarchical structure or when there are many connection points. Can be done. Furthermore, the global address of the called communication terminal can be made independent of the connection point, and the information related to the connection point of the called communication terminal can be hidden from the calling communication terminal. Is possible.

Furthermore, in addition to the above configuration, the network management apparatus of the present invention is specified by the global network prefix that specifies the management network, the subnet ID specified by the subnet ID specifying means, and the interface ID specifying means. An address configuration means for generating a global address of the called communication terminal by combining with an interface ID;
In one or both of the notification to the call processing device by the first address information notification unit and the notification to the communication terminal by the second address information notification unit, the global address generated by the address configuration unit is notified. It is comprised so that.
With the above configuration, the network management apparatus can generate and provide a global address of the communication terminal.

In order to achieve the above object, a call processing device of the present invention is a call processing device that performs processing related to a call control protocol for realizing a call on an IP network,
A call request message receiving means for receiving a call request message for requesting a call with a communication terminal of the called side by the calling communication terminal;
Information extracting means for extracting information specifying the type of the calling communication terminal and identification information of the called communication terminal from the call request message;
Network management for managing the network to which the communication terminal is currently connected based on the information specifying the type of the calling communication terminal extracted by the information extraction means and the identification information of the called communication terminal Address inquiry means for making an inquiry about the address of the communication terminal to the device;
As the response corresponding to the address inquiry means, the called side specified by the network management device by the subnet ID corresponding to the type of the calling side communication terminal and the identification information of the called side communication terminal Address information receiving means for receiving information including at least the interface ID of the communication terminal;
The address configured by the subnet ID and the interface ID received by the address information receiving unit and the global routing prefix that identifies the network to which the communication terminal is connected is the global address of the called communication terminal. A call request processing means for performing processing related to the call request message,
Have.
With the above configuration, when a communication terminal connected to a predetermined carrier network receives a call from a communication terminal serving as a communication partner, the calling side serves as the global address of the called communication terminal. By providing the network management device with information for allowing a global address having a different subnet ID to be assigned depending on the type of communication terminal in the carrier network, depending on the type of communication terminal on the calling side Packet transfer path control can be realized.

In order to achieve the above object, a call processing device of the present invention is a call processing device that performs processing related to a call control protocol for realizing a call on an IP network,
A call request message receiving means for receiving a call request message for requesting a call with a communication terminal of the called side by the calling communication terminal;
Information extracting means for extracting information specifying the type of the calling communication terminal and identification information of the called communication terminal from the call request message;
Network management for managing the network to which the communication terminal is currently connected based on the information specifying the type of the calling communication terminal extracted by the information extraction means and the identification information of the called communication terminal Address inquiry means for making an inquiry about the address of the communication terminal to the device;
As the response corresponding to the address inquiry means, the incoming call specified by the network management device by the subnet ID representing the network to which the communication terminal is currently connected and the identification information of the communication terminal on the called side Address information receiving means for receiving information including at least the interface ID of the communication terminal on the side;
The address configured by the subnet ID and the interface ID received by the address information receiving unit and the global routing prefix that identifies the network to which the communication terminal is connected is the global address of the called communication terminal. A call request processing means for performing processing related to the call request message,
Have.
With the above configuration, when a communication terminal connected to a predetermined carrier network receives a call from a communication terminal serving as a communication partner, the calling side serves as the global address of the called communication terminal. By providing the network management device with information for allowing a global address having a different subnet ID to be assigned depending on the type of communication terminal in the carrier network, depending on the type of communication terminal on the calling side Packet transfer path control can be realized. Further, the global address of the called communication terminal is configured not to depend on the connection point, and the information related to the connection point of the called communication terminal can be concealed from the calling communication terminal. It becomes possible.

Further, in the call processing device according to the present invention, in addition to the above configuration, the address information receiving means includes a global network prefix that specifies the management network, a subnet ID specified by the subnet ID specifying means, and the interface A global address of the called communication terminal generated by combining the interface ID specified by the ID specifying means is received from the network management device.
With the above configuration, the global address of the communication terminal generated in the network management apparatus can be acquired.

  The present invention has the above-described configuration, and when a communication terminal in a carrier network makes a call with a communication terminal on various networks, the network type of the communication terminal (communication terminal) as a communication partner Route control in consideration of the type).

  Hereinafter, first and second embodiments of the present invention will be described with reference to the drawings.

<First Embodiment>
First, a first embodiment of the present invention will be described. FIG. 1 is a diagram schematically illustrating an example of a communication system according to the first embodiment of the present invention. In the communication system shown in FIG. 1, a PE (Provider Edge Router) 11 is arranged at the edge on the core network (provider network) side, and a CE (Customer Edge Router) is arranged on the edge on the customer network (customer network) side. ) 12 is provided on the carrier network 10. A plurality of CEs 12 can be arranged.

  The PE 11 is connected to an external network such as the Internet 20 and functions as a packet relay device that is transferred between the carrier network 10 and the external network. The CE 12 is configured to accommodate (connect) a mobile communication terminal (hereinafter referred to as MN: mobile node) 13 or the like under the CE 12. Therefore, the MN 13 connected to the CE 12 can communicate with a communication terminal (for example, a CN (Correspondent Node) 21 connected to the Internet 20) 21 on an arbitrary external network through the carrier network 10 and the PE 11. is there.

  The carrier network 10 includes a single physical network and a plurality of logical networks having different network addresses (subnet IDs). FIG. 1 schematically shows a state in which three logical networks 10α to 10γ exist in a carrier network 10 that is a physical network. The plurality of logical networks 10α to 10γ are identified by different subnet IDs. For example, Sα is preset as a subnet ID for specifying the logical network 10α, Sβ as a subnet ID for specifying the logical network 10β, and Sα as a subnet ID specifying the logical network 10γ. In each of the plurality of logical networks 10α to 10γ, path control based on different requirements (throughput priority, minimum delay, etc.) can be realized.

  The PE 11 and the CE 12 belong to all of the plurality of logical networks 10α to 10γ, and are configured to perform transfer processing of packets transferred through the logical networks 10α to 10γ. Also, the arbitrary router 14 in the carrier network 10 belongs to all of the plurality of logical networks 10α to 10γ and performs transfer processing of packets transferred in the logical networks 10α to 10γ, similarly to the PE 11 and the CE 12. It may be configured, or may belong to only a part of the plurality of logical networks 10α to 10γ, and may be configured to perform transfer processing only for packets transferred in the logical networks 10α to 10γ to which the network belongs. .

  In this specification, basically, Greek letters (α, β, γ,...) Are used as elements for identifying each of a plurality of logical networks, and Roman letters are used as elements for identifying each of a plurality of CEs. The notation (a, b, c,...) Is used.

  In addition to the function as a conventional SIP server that processes SIP messages, the SIP server 16 can obtain a network of the CN 21 that can be acquired from information included in an INVITE message (session participation request message) from the CN 21 to the MN 13. It is possible to receive a response including the subnet ID of the logical network corresponding to the type of the CN 21 (the type of the network to which the CN 21 is connected) by making an inquiry to the network management server 17 using the information on the type of the network. It is.

  In addition, the network management server 17 defines in advance the correspondence between the type of CN 21 that communicates with the MN 13 connected to the carrier network 10 (the type of network to which the CN 21 is connected) and each of the plurality of logical networks. A subnet ID correspondence information database 171 in which the information (subnet ID correspondence information) is stored is held. For example, when the network management server 17 receives an inquiry from the SIP server 16 regarding information regarding the type of the CN 21, the network management server 17 refers to the subnet ID correspondence information database 171, acquires the subnet ID corresponding to the information, and makes a response. Is possible.

  Next, an example of information stored in the subnet ID correspondence information database 171 in the first embodiment of the present invention will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of information in the subnet ID correspondence information database held by the network management server according to the first embodiment of this invention.

  As shown in FIG. 2, in the subnet ID correspondence information database 171, the correspondence between the network type (CN type) and the subnet ID assigned to the called MN that receives a call from the CN. Relationships are stored. In the subnet ID correspondence information shown in FIG. 2, when CN is a softphone terminal, the subnet ID assigned to MN is S (α), and when CN is an IP phone, the subnet ID assigned to MN is S (β ) When the CN is a fixed telephone, the subnet ID assigned to the MN is S (γ), when the CN is a mobile phone, the subnet ID assigned to the MN is S (δ), and when the CN is an emergency call telephone, the subnet ID is assigned to the MN. The subnet ID defines a correspondence relationship of S (ε).

  Note that the subnet IDs (S (α) to S (ε) in FIG. 2) in the first embodiment of the present invention identify the logical network. The subnet ID further has a role of specifying the position of a hierarchical network (for example, a state where a plurality of CEs 12 exist and subnets exist under each CE 12). What is necessary is just to be solved by the arbitrary rules defined in each logical network. When there are a plurality of CEs 12, for example, the subnet of each CE 12 in the logical network 10α is, for example, subnet ID = [S (α) | y] (y is an arbitrary setting value for identifying the subnet of each CE 12) The values of S (α) to S (ε) may be set shorter than the total subnet ID length so that they can be identified.

  In addition, the network management server 17 holds a position information database 172 in which information for managing the current connection points (currently connected CEs 12) of all the MNs 13 connected to the carrier network 10 is stored. ing.

  In the location information database 172, correspondence information between identification information of the MN 13 and information for specifying the CE 12 (that is, information indicating which CE 12 the MN 13 is currently connected to) is managed. The network management server 17 can grasp which connection point (CE12) the MN 13 connected to the carrier network 10 is connected to by referring to the information in the location information database 172. In order to update the location information database 172, the network management server 17 always communicates with the MN 13 (regularly or irregularly) for confirming the location of the MN13.

  Next, an example of information stored in the position information database 172 according to the first embodiment of the present invention will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of information in the location information database held by the network management server according to the first embodiment of the present invention.

  As shown in FIG. 3, the location information database 172 stores correspondence information between the MN interface ID and the MN connection point. 3, the connection point of the MN whose interface ID is H1 is CE (a), the connection point of the MN whose interface ID is H2 is CE (b), and the connection point of the MN whose interface ID is H3 Corresponding information is held such that the point is CE (d), the connection point of the MN whose interface ID is H4 is CE (c), and the connection point of the MN whose interface ID is H5 is CE (b).

  Also, as shown in FIG. 3, in the location information database 172, an IP address request message received from the SIP server 16 corresponding to the interface ID of each MN (transmitted in step S1003 in FIG. 4 described later). MN identification information (MN1_ID to MN5_ID in FIG. 3) included in the message may be stored. The identification information of the MN in the location information database 172 is key information for specifying which MN the IP address request from the SIP server 16 relates to. The type of information used as the identification information of the MN is SIP It depends on the information handled by the server 16.

  For example, the SIP server 16 receives E.E. as the MN identification information in the IP address request message. When the 164 number or SIP-URL is used, the identification information of the MN in the location information database 172 includes an E.P. 164 number and SIP-URL are stored. In this case, the network management server 17 has a function close to an ENUM (Telephone Number Mapping) server. In addition, when the SIP server 16 uses the MN interface ID acquired by itself using any mechanism as the MN identification information in the IP address request message, the interface ID itself of the location information database 172 is the key information. Therefore, it is not necessary to provide an MN identification information column.

  Further, the network management server 17 notifies the MN 13 on the callee side that receives the call from the CN 21 of the subnet ID specified by the inquiry from the SIP server 16, and the MN 13 receives the global IP including this subnet ID. It has a function of setting an address or a function of automatically setting a global IP address including a subnet ID specified by an inquiry from the SIP server 16 in a stateless manner.

  In FIG. 1, the SIP server 16 and the network management server 17 are illustrated so as to exist outside the carrier network 10, but may be arranged inside the carrier network 10 or at any other position. Further, in FIG. 1, the PE 11, the SIP server 16, and the network management server 17 are illustrated as different communication devices, but a part or all of the functions may be provided in the same communication device. Furthermore, a plurality of functions that the network management server 17 has may be distributed to a plurality of communication devices.

  Next, an example of the operation of the communication system according to the first embodiment of the present invention will be described with reference to FIG. FIG. 4 is a sequence chart showing an example of the operation of the communication system according to the first embodiment of the present invention.

  In FIG. 4, as an initial state, it is assumed that the MN 13 is connected to the CE 12 as shown in FIG. 1 and has a site local IP address set (step S1000). Also, the CN 21 sets the E.M. of the MN 13 that is about to make a call. Assume that you already know the 164 number.

  The CN 21 that wants to make a call to the MN 13 first transmits an INVITE message defined by SIP to the SIP server 16 (step S1001). The SIP server 16 that has received this INVITE message extracts the identification information (the E.164 number of the MN 13) of the MN 13 (the call partner that the CN 21 is trying to make a call) contained in the INVITE message.

  Here, although the CN 21 itself directly transmits the INVITE message to the SIP server 16, the operation may be performed in the proxy mode in which processing is requested to another SIP server. The INVITE message includes E.E. “.164” generated from the 164 number. e164. The identification information of the MN 13 may be inserted in a format such as “arpa” or SIP-URL (Uniform Resource Locator). All of these operations depend on the operations defined by the SIP, and a detailed description thereof will be omitted here.

  The SIP server 16 extracts the identification information of the MN 13 from the INVITE message, and at the same time, extracts information that can specify the type of the CN 21 from the INVITE message (step S1002). Arbitrary information can be used as information that can specify the type of the CN 21. For example, the station number (03, 050, 090, etc.) of the telephone number assigned to the CN 21 and the format of the CN 21 identification information By referring to the above, it is possible to easily grasp the type of the CN 21.

  Then, the SIP server 16 transmits a message including the identification information of the MN 13 (identification information for identifying the called party of the INVITE message) and information regarding the type of the CN 21 to the network management server 17, so that the MN 13 Is requested (step S1003).

  The network management server 17 that has received the IP address request message from the SIP server 16 refers to the subnet ID correspondence information database 171 to acquire the subnet ID corresponding to the type of the CN 21 included in the message, and With reference to the information database 172, the interface ID of the MN 13 corresponding to the identification information of the MN 13 included in this message is acquired (step S1004).

  Here, the SIP server 16 specifies the identification information of the MN 13 from the INVITE message, and the network management server 17 obtains the interface ID of the MN 13 from this identification information. The SIP server 16 may notify the network management server 16 of the interface ID of the MN 13 if it is possible to acquire the interface ID of the MN 13 from the INVITE message using. In this case, as described above, the MN interface ID can be used as the MN identification information, and the column of the MN identification information in the location information database 172 shown in FIG. 3 is unnecessary. In addition, E.M. A 164 number or SIP-URL may be used.

  In step S1004, the network management server 17 that has acquired the interface ID of the MN 13 and the subnet ID corresponding to the type of the CN 21 necessary for the configuration of the global IP address of the MN 13 returns a response of the global IP address of the MN 13 to the SIP server 16. And also notifies the MN 13 of the information necessary for the configuration of the global IP address (step S1005). Note that the SIP server 16 may be able to grasp the global network prefix of the carrier network 10 by itself. Therefore, in step S1005, the network management server 17 may notify the SIP server 16 of at least the interface ID and subnet ID. Further, the MN 13 can grasp its own interface ID and can also grasp the global network prefix of the carrier network 10. Therefore, in step S1005, the network management server 17 may notify at least the subnet ID to the MN 13.

  There are roughly two methods for notification of IP addresses from the network management server 17 to the SIP server 16 and the MN 13. The first method is a method in which the network management server 17 directly notifies the SIP server 16 and the MN 13 of the interface ID of the MN 13 acquired in step S1004 and the subnet ID corresponding to the type of the CN 21. At this time, the network management server 17 may simultaneously notify the global routing prefix (fixed value I for the carrier network 10) used for identifying the carrier network 10 in the global network. In this case, the SIP server 16 and the MN 13 need to configure the global IP address of the MN 13 based on the information notified from the network management server 17.

  On the other hand, the second method is based on the global routing prefix for identifying the carrier network 10 in addition to the interface ID of the MN 13 and the subnet ID corresponding to the type of the CN 21 acquired by the network management server 17 in step S1004. , A global IP address of the MN 13 is generated, and the generated global IP address is notified to the SIP server 16 and the MN 13. In this case, the MN 13 does not need to generate a global IP address by itself in step S1007 to be described later, and only needs to set the global IP address notified from the network management server 17 as its own global IP address.

  The MN 13 that has received the notification of the global IP address of the MN 13 in step S1005 generates (or sets) its own global IP address (step S1007). The SIP server 16 that has received the response of the global IP address of the MN 13 in step S1005 transmits an INVITE message in which the global IP address of the MN 13 is set as a transmission destination address to the MN 13 (step S1009) and received in step S1001. A 100 Trying message notifying that the INVITE message is currently being processed is transmitted to the CN 21 (step S1011).

  Subsequent processing is the same as the sequence defined in the conventional SIP. That is, as a response to the INVITE message, the MN 13 transmits a 180 Ringing message indicating that it is currently being called (step S1013). This 180 Ringing message is transferred through a path opposite to that of the INVITE message and is delivered to the CN 21 (step S1015). If the MN 13 is off-hook, the MN 13 transmits a 200 OK message indicating acceptance of the communication request (step S1017). This 200 OK message is also transferred through a path opposite to that of the INVITE message and delivered to the CN 21 (step S1019). The CN 21 that has received the 200 OK message transmits an ACK message indicating confirmation (step S1021). This ACK message is delivered to the MN 13 through the same route as the INVITE message (step S1023).

  With the above processing, IP communication is started between the MN 13 and the CN 21. A packet related to this IP communication (a packet from the CN 21 to the MN 13) corresponds to a subnet ID (for example, S (α)) included in the global IP address of the MN 13 in the carrier network 10 (between the PE 13 and the CE 12). It is transferred on a logical network (for example, logical network 10α). In addition, since the global routing prefix is referenced outside the carrier network 10 (between the PE 13 and the CN 21), it is transferred in the same manner as a conventional packet.

  Next, a communication operation started based on the operation shown in FIG. 4 will be described with reference to FIG. FIG. 5 is a diagram schematically illustrating an example of a communication operation according to the first embodiment of the present invention.

  As described above, a different subnet ID is assigned to the MN 13 depending on the type of the communication partner (CN21 in FIG. 1). That is, the MN 13 is assigned a global IP assigned a different subnet ID depending on the type of the communication partner. Use the address as its own global IP address.

  For example, as shown in FIG. 5, when the MN 13 receives a call from the softphone terminal 22, according to the subnet ID correspondence information shown in FIG. The global IP address (α) is assigned. Therefore, the global IP address of the MN 13 whose subnet ID is S (α) is set as the destination address of the packet transmitted from the softphone terminal 22 to the MN 13. This packet reaches the PE 11 from the softphone terminal 22 through the Internet 20 in the same manner as other packets. In the PE 11, this packet is processed by a virtual PE (α) 11α belonging to the logical network 10α, and is sent out into the carrier network (logical network) 10α. The logical network 10α is a network in which, for example, throughput-prioritized route control is performed, and packets sent from the PE (α) 11α pass to the CE 12 via a route with priority setting (route 40α of S (α)). Delivered to MN13.

  On the other hand, as shown in FIG. 5, for example, when the MN 13 receives a call (callback) from the emergency call telephone 31, according to the subnet ID correspondence information shown in FIG. Is assigned a global IP address with a subnet ID of S (ε). Therefore, the global IP address of the MN 13 whose subnet ID is S (ε) is set as the destination address of the packet transmitted from the emergency call telephone 31 to the MN 13. This packet arrives at the PE 11 through the emergency call line network 30 from the emergency call telephone 31, as with other packets. In the PE 11, this packet is processed by a virtual PE (ε) 11ε belonging to the logical network 10ε, and sent out into the carrier network (logical network) 10ε. The logical network 10ε is a network in which, for example, route control with throughput priority and minimum delay is performed, and a packet transmitted from the PE (ε) 11ε is a route with throughput priority and minimum delay setting (route 40ε of S (ε)). To CE12 and reach MN13.

  As described above, according to the first embodiment of the present invention, when there is a call from a communication partner (communication terminal) to an MN connected to a predetermined carrier network, By assigning a global IP address having a different subnet ID according to the type of the communication terminal as the global IP address, a packet transfer route according to the type of the communication terminal that is the communication partner in the carrier network Control can be realized.

<Second Embodiment>
Next, a second embodiment of the present invention will be described. In the first embodiment of the present invention described above, subnet IDs are assigned to the respective carrier networks (logical networks) 10α to 10γ. For example, when the total number of carrier networks (logical networks) is N, N subnet IDs are prepared. On the other hand, in the second embodiment of the present invention, a subnet ID is further assigned to each CE 12. Therefore, for example, when the total number of CEs 12 is M, (N × M) subnet IDs are prepared. In the following, for example, a subnet ID that belongs to the logical network 10α and is assigned to a specific CE (a) is denoted as Sa (α).

  The system configuration in the second embodiment of the present invention is almost the same as that of the communication system shown in FIG. 1, but the subnet ID of the above Sa (α) suitable for the MN 13 is specified when the subnet ID is assigned. Is added to the PE 11 and the network management server 17, and the contents of the subnet ID correspondence information database 171 and the location information database 172 held by the network management server 17 are changed. Furthermore, a function for changing the global IP address of the MN 13 at the time of packet transfer is added to the PE 11 and the CE 12.

  In the second embodiment of the present invention, the subnet ID correspondence information database 171 and the location information database 172 have, for example, the contents shown in FIGS. 6 and 7, respectively.

  First, an example of information stored in the subnet ID correspondence information database 171 in the second embodiment of the present invention will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of information in the subnet ID correspondence information database held by the network management server according to the second embodiment of the present invention.

  As shown in FIG. 6, in the subnet ID correspondence information database 171, the correspondence between the network type (CN type) and the subnet ID assigned to the called MN that receives a call from the CN. Relationships are stored. The structure of the subnet ID correspondence information database 171 shown in FIG. 6 is the same as that of the subnet ID correspondence information database 171 shown in FIG. 2 except that the subnet ID correspondence database 171 shown in FIG. Is in the subdivision.

  In the subnet ID correspondence information shown in FIG. 6, when CN is a softphone terminal, the subnet ID assigned to the MN connected to CE (a) is Sa (α), and when CN is a softphone terminal, CE The subnet ID assigned to the MN connected to (b) is Sb (α), and when the CN is an IP phone, the subnet ID assigned to the MN connected to CE (a) is Sa (β), and the CN is an IP phone. In this case, the subnet ID assigned to the MN connected to the CE (b) is Sb (β), and when the CN is a fixed telephone, the subnet ID assigned to the MN connected to the CE (a) is Sa (γ), When CN is a fixed telephone, the subnet ID assigned to the MN connected to CE (b) is Sb (γ), and when CN is a mobile phone, it is connected to CE (a). The subnet ID assigned to the MN is Sa (δ), and when the CN is a mobile phone, the subnet ID assigned to the MN connected to the CE (b) is Sb (δ), and when the CN is an emergency call phone, CE ( The subnet ID assigned to the MN connected to a) is Sa (ε), and when the CN is an emergency call telephone, the subnet ID assigned to the MN connected to CE (b) is Sb (ε). It is prescribed.

  Next, an example of information stored in the position information database according to the second embodiment of the present invention will be described with reference to FIG. FIG. 7 is a diagram illustrating an example of information in the location information database held by the network management server according to the second embodiment of the present invention.

  As illustrated in FIG. 7, the location information database 172 stores correspondence information between the MN interface ID and the MN connection point, and may further store MN identification information. These pieces of information are the same as those in the first embodiment of the present invention (see FIG. 3). Further, the location database 172 shown in FIG. 7 has a column for storing a subnet ID currently assigned to each MN.

  In FIG. 7, the subnet ID of Sb (δ) is assigned to the MN whose interface ID is H2, and the subnet ID of Sd (α) is assigned to the MN whose interface ID is H3. The state where the subnet ID of Sc (β) is assigned to the MN whose ID is H4 is illustrated. The current subnet ID information is changed when the type of the MN's other party is changed or when the MN moves (changes the CE of the connection destination). In FIG. 7, the current subnet ID of the MN with the interface IDs H1 and H5 is blank, which means that the MN with the interface IDs H1 and H5 has not acquired a global IP address. To do.

  Next, an example of the operation of the communication system according to the second embodiment of the present invention will be described. The operation of the communication system according to the second embodiment of the present invention is basically the same as the operation of the communication system according to the first embodiment of the present invention, and performs the same processing as in FIG. However, the details of the operation when the network management server 17 acquires the subnet ID of the MN 13 in step S1004 are different.

  Details of the operation in step S1004 (see FIG. 4) in the second embodiment of the present invention will be described below. The network management server 17 that has received the IP address request message from the SIP server 16 can extract information on the type of the CN 21 and identification information of the MN 13 from this message. The network management server 17 can obtain the interface ID of the MN 13 and the identification information of the CE 12 to which the MN 13 is currently connected based on the identification information of the MN 13 with reference to the location information database 172. Further, the network management server 17 refers to the subnet ID correspondence information database 171, and based on the information regarding the type of the CN 21 and the identification information of the CE 12 to which the MN 13 is currently connected acquired as described above, the CN 21 It is possible to acquire a subnet ID corresponding to the type of CE 12 and the identification information of the CE 12. Then, the network management server 17 updates the location information database 172 by inserting the subnet ID obtained as described above into the current subnet column of the MN 13 in the location information database 172, as shown in FIG. The process after step S1005 shown in the figure is performed.

  For example, in the example illustrated in FIGS. 6 and 7, the network management server 17 extracts information from the IP address request message that the type of the CN 21 is a fixed telephone and the identification information of the MN 13 is MN1_ID. To do. At this time, the network management server 17 can grasp from the location information database 172 of FIG. 7 that the interface ID of the MN 13 is H1 and the identification information of the CE to which the MN 13 is currently connected is CE (a). Is possible. Further, the network management server 17 uses the subnet ID correspondence information database 171 in FIG. 6 as the subnet ID assigned to the MN 13 connected to the CE (a) with the fixed telephone as the communication partner, Sa (γ). It is possible to grasp that. Note that the network management server 17 performs processing so that the global IP address including the specified subnet ID (Sa (γ)) is set in the MN 13 and also corresponds to the identification information (MN1_ID) of the MN 13 The specified subnet ID (Sa (γ)) is registered in the subnet ID field.

  Subsequently, a communication operation started in the second embodiment of the present invention will be described with reference to FIGS. In the second embodiment of the present invention, when a packet transmitted from the CN 21 to the MN 13 is transferred in the carrier network 10, for example, packet transfer according to the following three operation examples can be executed. is there.

  Note that the sequence charts shown in FIGS. 8 to 10 show the flow of packets transmitted and received between the CN 21 and the MN 13, but the packets in the downstream direction (direction from the CN 21 to the MN 13) are shown. The flow describes the subnet ID of the global IP address of the MN 13 set as the packet destination address. The packet flow in the upstream direction (direction from the MN 13 to the CN 21) sets the packet source address. The subnet ID of the global IP address of the MN 13 is described.

<First operation example>
First, a first operation example in the communication operation started in the second embodiment of the present invention will be described with reference to FIG. FIG. 8 is a sequence chart showing a first operation example in the communication operation started in the second embodiment of the present invention.

  In the first operation example, as in the first embodiment of the present invention described above, the global IP address of the MN 13 set as the source address or the destination address of the packet transmitted / received between the CN 21 and the MN 13 ( For example, packet transfer is performed without any particular change to [I | Sa (α) | H1]).

  In other words, in FIG. 8, the downstream packet transmitted from CN 21 to MN 13 has a destination address of [I | Sa (α) | H1], and CN 21 to PE 11, PE 11 to CE 12, and CE 12 to MN 13. (Steps S1201 to S1205).

  As described above, according to the first operation example of the second embodiment of the present invention, the downlink direction transmitted from the CN 21 toward the MN 13 as in the first embodiment of the present invention described above. In the carrier network 10 can be distributed to the logical network so as to receive route control according to the type of the CN 21.

  Also, with respect to an upstream packet transmitted from the MN 13 to the CN 21, the packet is forwarded from the MN 13 to the CE 12, from the CE 12 to the PE 11, and from the PE 11 to the CN 21 in a state where the source address is [I | Sa (α) | H 1]. (Steps S1207 to S1211).

<Second operation example>
Next, a second operation example in the communication operation started in the second embodiment of the present invention will be described with reference to FIG. FIG. 9 is a sequence chart showing a second operation example in the communication operation started in the second embodiment of the present invention.

  In the second operation example, in PE11 and CE12, the global IP address (for example, [I | Sx (α) |) of MN13 set as the source address or the destination address of the packet transmitted and received between CN21 and MN13. H1]) is subjected to address conversion (subnet ID value conversion), route control based on the address according to the logical network is performed within the carrier network 10, and the MN 13 is connected outside the carrier network. An address that does not depend on the existing CE 12 is used.

  In order to realize the second operation example, it is necessary to slightly modify the above-described operation at the time of address assignment (that is, the operation of the sequence chart shown in FIG. 4). Specifically, when the network management server 17 notifies the CN 21 and MN 13 of the global IP address (IP address response in step S1005 in FIG. 4), it depends on the types of CE 12 and CN 21 to which the MN 13 is connected. Instead of the subnet ID (eg, Sa (α)), a global IP address including a subnet ID (eg, Sx (α)) that depends only on the type of the CN 21 is notified. Thus, in the second operation example, the global IP address of the MN 13 includes a subnet ID that depends only on the type of the CN 21 regardless of which CE 12 the MN 13 is connected to. The MN 13 itself uses the global IP address including the subnet ID that depends only on the type of the CN 21 as the global IP address of the MN 13 and starts communication. In the second operation example, the subnet ID (Sx (α), Sx (β),...) That depends only on the type of CN 21 is the number of logical networks (that is, the number set as the type of CN 21). Only prepared.

  In FIG. 9, the downstream packet transmitted from the CN 21 to the MN 13 is transferred from the CN 21 to the PE 11 with the destination address being [I | Sx (α) | H1] (step S1301). The PE 11 extracts the interface ID “H1” of the destination address of the packet, and inquires of the network management server 17 about the subnet ID currently assigned to the MN identified by the interface ID “H1”. The network management server 17 refers to the location information database 172 in response to this inquiry, identifies the subnet ID (for example, Sa (α)) corresponding to the interface ID “H1”, and responds to the PE 11. With this operation, the PE 11 acquires the corresponding subnet ID (for example, Sa (α)) from the interface ID “H1” of the destination address of the packet, and the destination address of the packet from [I | Sx (α) | H1]. It is possible to convert to [I | Sa (α) | H1] (step S1303). Then, the destination address converted packet is transferred from the PE 11 to the CE 12 (step S1305).

  On the other hand, the CE 12 has a function of mechanically converting the subnet ID of the destination address of the downstream packet from Sa (α) to Sx (α). Accordingly, the CE 12 converts the destination address of the packet received in step S1305 from [I | Sa (α) | H1] to [I | Sx (α) | H1] (step S1307). Then, the destination address converted packet is transferred from the CE 12 to the MN 13 (step S1309).

  As described above, according to the second operation example of the second embodiment of the present invention, the downlink direction transmitted from the CN 21 toward the MN 13 as in the first embodiment of the present invention described above. In the carrier network 10 can be distributed to the logical network so as to receive route control according to the type of the CN 21. Furthermore, in the second operation example of the second embodiment of the present invention, a global IP address independent of the connection destination CE 12 is generated as the global IP address of the MN 13, so the MN 13 changes the connection destination CE 12. In this case, it is not necessary to change the global IP address, and it is possible to hide which CE 12 the MN 13 is connected to from the CN 21.

  On the other hand, regarding an upstream packet transmitted from the MN 13 to the CN 21, if it is assumed that routing is performed only depending on the destination address of the packet (in this case, the address of the CN 21), the packet transmission The original address [I | Sx (α) | H1] is transferred from the MN 13 to the CN 21 without conversion. However, when security processing (for example, ingress filtering) or error processing (for example, return of an error message) is performed, or when routing of an upstream packet is realized, the packet source address is referenced. Therefore, it is desirable that the upstream packet passes through the same logical network as the logical network used for the downstream packet transfer.

  In order to transfer the uplink packet on the same logical network as that used for the downlink packet transfer, for example, the operation after step S1311 in FIG. 9 is desirably performed.

  In FIG. 9, an upstream packet transmitted from the MN 13 to the CN 21 is transmitted from the MN 13 to the CE 12 with the source address being [I | Sx (α) | H1] (step S1311). The CE 12 determines that it is desirable to perform packet transfer on the logical network 10α from Sx (α) included in the subnet ID of the transmission source address, and the Sa 12 that is the subnet ID belonging to the logical network 10α that identifies the CE 12 itself. α) is used to mechanically convert the source address from [I | Sx (α) | H1] to [I | Sa (α) | H1] (step S1313). Then, the packet after the source address conversion is transferred from the CE 12 to the PE 11 via the logical network 10α (step S1315).

  The PE 11 mechanically converts the source address of the packet received in step S1315 from [I | Sa (α) | H1] to [I | Sx (α) | H1] (step S1317). Then, the packet after the source address conversion is sent from the PE 11 to the outside of the carrier network 10 and transferred to the CN 21 (step S1319).

<Third operation example>
Next, a third operation example in the communication operation started in the second embodiment of the present invention will be described with reference to FIG. FIG. 10 is a sequence chart showing a third operation example in the communication operation started in the second embodiment of the present invention.

  The third operation example is similar to the second operation example described above, but the subnet ID of the global IP address of the MN 13 is not a subnet ID (eg, Sx (α)) that depends only on the type of the CN 21, A representative subnet ID (eg, Sx) representing the carrier network 10 is used. Thus, in the third operation example, the representative subnet ID is used for the global IP address of the MN 13 regardless of which CE 12 the MN 13 is connected to and any type of CN 21. The CN 21 and the MN 13 themselves use the global IP address including the representative subnet ID as the global IP address of the MN 13 and start communication. In the third operation example, only one representative subnet ID (Sx only) needs to be prepared.

  In FIG. 10, a downstream packet transmitted from the CN 21 to the MN 13 is transferred from the CN 21 to the PE 11 with the destination address being [I | Sx | H1] (step S1401). The PE 11 extracts the interface ID “H1” of the destination address of the packet, and inquires of the network management server 17 about the subnet ID currently assigned to the MN identified by the interface ID “H1”. The network management server 17 refers to the location information database 172 in response to this inquiry, identifies the subnet ID (for example, Sa (α)) corresponding to the interface ID “H1”, and responds to the PE 11. By this operation, the PE 11 acquires the corresponding subnet ID (for example, Sa (α)) from the interface ID “H1” of the packet destination address, and changes the packet destination address from [I | Sx | H1] to [I | Sa (α) | H1] can be converted (step S1403). Then, the destination address converted packet is transferred from the PE 11 to the CE 12 (step S1405).

  On the other hand, the CE 12 has a function of mechanically converting the subnet ID of the destination address of the downstream packet from Sa (α) to Sx. The destination address of the packet received in step S1405 is [I | Sa ( α) | H1] is converted to [I | Sx | H1] (step S1407). Then, the destination address converted packet is transferred from the CE 12 to the MN 13 (step S1409).

  As described above, according to the third operation example of the second embodiment of the present invention, the downlink direction transmitted from the CN 21 to the MN 13 as in the first embodiment of the present invention described above. In the carrier network 10 is distributed to each logical network so as to receive route control according to the type of the CN 21. In the third operation example of the second embodiment of the present invention, a global IP address that does not depend on the connection destination CE 12 is generated as the global IP address of the MN 13, so the MN 13 changes the connection destination CE 12. Even in this case, it is not necessary to change the global IP address, and it is possible to conceal which CE 12 the MN 13 is connected to from the CN 21. Furthermore, in the third operation example of the second embodiment of the present invention, a global IP address independent of the type of the CN 21 is generated as the global IP address of the MN 13, so the MN 13 communicates with a different type of CN 21. Even in this case, it is not necessary to change the global IP address. Accordingly, a global IP address is assigned to the MN 13 before the call is made from the CN 21 to the MN 13, and when the call is received from the CN 21, the subnet ID assignment for route control in the carrier network 10 is assigned according to the type of the CN 21. Is possible.

  On the other hand, regarding an upstream packet transmitted from the MN 13 to the CN 21, if it is assumed that routing is performed only depending on the destination address of the packet (in this case, the address of the CN 21), the packet transmission The original address [I | Sx | H1] is transferred from the MN 13 to the CN 21 without conversion. However, as in the above-described second operation example, it is desirable that the upstream packet passes through the same logical network as the logical network used for transferring the downstream packet.

  In order to transfer the uplink packet on the same logical network as that used for the downlink packet transfer, for example, the operation after step S1411 in FIG. 10 is desirably performed.

  In FIG. 10, an uplink packet transmitted from the MN 13 to the CN 21 is transmitted from the MN 13 to the CE 12 with its source address being [I | Sx | H1] (step S1411). The CE 12 extracts the interface ID “H1” of the source address of the packet, and inquires of the network management server 17 about the subnet ID currently assigned to the MN identified by the interface ID “H1”. The network management server 17 refers to the location information database 172 in response to this inquiry, identifies the subnet ID (for example, Sa (α)) corresponding to the interface ID “H1”, and responds to the CE 12. With this operation, the CE 12 acquires the corresponding subnet ID (for example, Sa (α)) from the interface ID “H1” of the destination address of the packet, and changes the source address of the packet from [I | Sx | H1] to [I | Sa (α) | H1] can be converted (step S1413). Then, the packet after the source address conversion is transferred from the CE 12 to the PE 11 (step S1415).

  The PE 11 mechanically converts the source address of the packet received in step S1415 from [I | Sa (α) | H1] to [I | Sx | H1] (step S1417). Then, the packet after the source address conversion is transmitted from the PE 11 to the outside of the carrier network 10 and transferred to the CN 21 (step S1419).

  Note that the first and second embodiments of the present invention described above, and further the communication according to the first to third operation examples of the second embodiment of the present invention are arbitrarily combined. It is also possible to build a system. For example, in the first embodiment of the present invention, the representative subnet ID representing the carrier network 10 is used as in the second or third operation example of the second embodiment of the present invention, and the CN The subnet ID specified from the type may be used only within the carrier network 10. It is also possible to construct a communication system by arbitrarily combining the technique of the present invention and the conventional technique.

  According to the present invention, when a communication terminal in a carrier network makes a call with a communication terminal on various networks, route control in consideration of the network type (communication terminal type) of the communication terminal that is the communication partner is performed. The present invention has an effect of being realized, and can be applied to a technology related to communication (especially a phone call) between communication terminals (telephones) existing on various networks. Applicable.

The figure which shows typically an example of the communication system in the 1st Embodiment of this invention. The figure which shows an example of the information in the subnet ID corresponding | compatible information database which the network management server in the 1st Embodiment of this invention hold | maintains The figure which shows an example of the information in the positional information database which the network management server in the 1st Embodiment of this invention hold | maintains The sequence chart which shows an example of operation | movement of the communication system in the 1st Embodiment of this invention The figure which shows typically an example of the communication operation | movement in the 1st Embodiment of this invention The figure which shows an example of the information in the subnet ID corresponding | compatible information database which the network management server in the 2nd Embodiment of this invention hold | maintains The figure which shows an example of the information in the positional information database which the network management server in the 2nd Embodiment of this invention hold | maintains Sequence chart showing a first operation example in the communication operation started in the second embodiment of the present invention Sequence chart showing a second operation example in the communication operation started in the second embodiment of the present invention Sequence chart showing a third operation example of the communication operation started in the second embodiment of the present invention The figure which shows an example of the communication system in a prior art typically The figure which shows an example of the address structure of IPv6 which concerns on a prior art

Explanation of symbols

10,600 Carrier network (physical network)
10α-10γ, 10ε Carrier network (logical network)
11, 610 PE (Provider Edge Router)
11α PE (α)
11ε PE (ε)
12,620 CE (Customer Edge Router)
13 Mobile communication terminals (MN, mobile node)
14 router 16 SIP server 17 network management server 20, 100 Internet 21 CN (call partner, communication terminal)
22, 110 Softphone terminal 30, 500 Emergency call network 31, 510 Emergency call phone 40α S (α) route 40ε S (ε) route 120 IP phone 171 Subnet ID correspondence information database 172 Location information database 300 Fixed phone Network 310 Fixed phone 400 Mobile phone network 410 Mobile phone 630 Mobile communication terminal (mobile phone)

Claims (8)

A network management device for managing a predetermined management network,
Interface ID management means for managing an interface ID of a communication terminal connected to the management network;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
Subnet ID specifying means for specifying a subnet ID corresponding to the type of communication terminal on the calling side received by the address inquiry receiving means with reference to information managed by the subnet ID management means;
As a response to the address inquiry received by the address inquiry receiving means, information including at least the subnet ID specified by the subnet ID specifying means and the interface ID specified by the interface ID specifying means is the call processing device. First address information notifying means for notifying to,
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal. ,
A network management device. A network management device for managing a predetermined management network,
Interface ID management means for managing an interface ID of a communication terminal connected to the management network;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
Subnet ID specifying means for specifying a subnet ID corresponding to the type of communication terminal on the calling side received by the address inquiry receiving means with reference to information managed by the subnet ID management means;
As a response to the address inquiry received by the address inquiry reception unit, information including at least a subnet ID representing the management network and an interface ID specified by the interface ID specifying unit is notified to the call processing device. First address information notifying means;
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal;
Address management means for managing the subnet ID specified by the subnet ID specifying means and the interface ID of the communication terminal on the called side in association with each other;
A network management device having. A network management device for managing a predetermined management network,
An interface ID / connection point management means for managing an interface ID of a communication terminal connected to the management network and a current connection point of the communication terminal;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and connection points of the management network and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
With reference to the information managed by the interface ID management means, the current connection point of the called communication terminal is identified from the identification information of the called communication terminal received by the address inquiry receiving means. Connection point identification means to
Referring to the information managed by the subnet ID management means, based on the connection point specified by the connection point specifying means and the type of the communication terminal on the calling side received by the address inquiry receiving means Subnet ID specifying means for specifying the subnet ID to be performed;
As a response to the address inquiry received by the address inquiry receiving means, information including at least the subnet ID specified by the subnet ID specifying means and the interface ID specified by the interface ID specifying means is the call processing device. First address information notifying means for notifying to,
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal. ,
A network management device having. A network management device for managing a predetermined management network,
An interface ID / connection point management means for managing an interface ID of a communication terminal connected to the management network and a current connection point of the communication terminal;
Subnet ID management means for managing correspondence information between types of communication terminals connected to external networks and connection points of the management network and subnet IDs;
A call processing device that performs processing related to a call control protocol for realizing a call on an IP network from a calling communication terminal belonging to an external network to a called communication terminal connected to the management network. When a call request message requesting a call is received, information specifying the type of the calling communication terminal extracted from the call request message by the call processing device and identification information of the called communication terminal Address inquiry reception means for receiving an inquiry about the address of the called communication terminal from the call processing device,
An interface for identifying the interface ID of the called communication terminal from the identification information of the called communication terminal received by the address inquiry receiving means with reference to the information managed by the interface ID managing means ID identification means;
With reference to the information managed by the interface ID management means, the current connection point of the called communication terminal is identified from the identification information of the called communication terminal received by the address inquiry receiving means. Connection point identification means to
Referring to the information managed by the subnet ID management means, based on the connection point specified by the connection point specifying means and the type of the communication terminal on the calling side received by the address inquiry receiving means Subnet ID specifying means for specifying the subnet ID to be performed;
As a response to the address inquiry received by the address inquiry reception unit, information including at least a subnet ID representing the management network and an interface ID specified by the interface ID specifying unit is notified to the call processing device. First address information notifying means;
Second address information notifying means for notifying the called communication terminal of information including at least the subnet ID specified by the subnet ID specifying means for use in the global address of the called communication terminal;
Address management means for managing the subnet ID specified by the subnet ID specifying means and the interface ID of the communication terminal on the called side in association with each other;
A network management device. A global network prefix that identifies the management network, a subnet ID that is identified by the subnet ID identifying means, and an interface ID that is identified by the interface ID identifying means are combined to create a global of the communication terminal on the called side Having address configuration means for generating addresses;
In one or both of the notification to the call processing device by the first address information notification unit and the notification to the communication terminal by the second address information notification unit, the global address generated by the address configuration unit is notified. The network management device according to any one of claims 1 to 4, wherein the network management device is configured to be configured as described above. A call processing device that performs processing related to a call control protocol for realizing a call on an IP network,
A call request message receiving means for receiving a call request message for requesting a call with a communication terminal of the called side by the calling communication terminal;
Information extracting means for extracting information specifying the type of the calling communication terminal and identification information of the called communication terminal from the call request message;
Network management for managing the network to which the communication terminal is currently connected based on the information specifying the type of the calling communication terminal extracted by the information extraction means and the identification information of the called communication terminal Address inquiry means for making an inquiry about the address of the communication terminal to the device;
As the response corresponding to the address inquiry means, the called side specified by the network management device by the subnet ID corresponding to the type of the calling side communication terminal and the identification information of the called side communication terminal Address information receiving means for receiving information including at least the interface ID of the communication terminal;
The address configured by the subnet ID and the interface ID received by the address information receiving unit and the global routing prefix that identifies the network to which the communication terminal is connected is the global address of the called communication terminal. A call request processing means for performing processing related to the call request message,
A call processing device. A call processing device that performs processing related to a call control protocol for realizing a call on an IP network,
A call request message receiving means for receiving a call request message for requesting a call with a communication terminal of the called side by the calling communication terminal;
Information extracting means for extracting information specifying the type of the calling communication terminal and identification information of the called communication terminal from the call request message;
Network management for managing the network to which the communication terminal is currently connected based on the information specifying the type of the calling communication terminal extracted by the information extraction means and the identification information of the called communication terminal Address inquiry means for making an inquiry about the address of the communication terminal to the device;
As the response corresponding to the address inquiry means, the incoming call specified by the network management device by the subnet ID representing the network to which the communication terminal is currently connected and the identification information of the communication terminal on the called side Address information receiving means for receiving information including at least the interface ID of the communication terminal on the side;
The address configured by the subnet ID and the interface ID received by the address information receiving unit and the global routing prefix that identifies the network to which the communication terminal is connected is the global address of the called communication terminal. A call request processing means for performing processing related to the call request message,
A call processing device.   The address information receiving means is generated by combining a global network prefix for specifying the management network, a subnet ID specified by the subnet ID specifying means, and an interface ID specified by the interface ID specifying means 8. The call processing device according to claim 6, wherein the call processing device is configured to receive a global address of the called communication terminal from the network management device.

Images