JP2016152547A - Mobile communication system and route selection method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable the selection of a route in a mobile communication core network, on the basis of each domain associated with a service type on the Internet accessed by a user.SOLUTION: Domain identification means monitors a packet forwarded from the core network to a gateway which comes to a connection window to the Internet, and performs reverse lookup inquiry processing of a DNS server using the destination IP address of the packet to acquire a domain name, so as to feedback output, to the entry of the core network, route selection information including predetermined network information in the core network, which is preset corresponding to the domain name, and a transmission source IP address. At the entry of the core network, route selection control means selects an identified network route, as a packet transfer destination which is transmitted from the user terminal and includes the transmission source IP address.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a mobile communication system and a route selection method, and more particularly, to a mobile communication system and a route selection method for selecting a route in a mobile communication core network for each domain of a service used by a user.

  As a technique related to route selection in a mobile communication core network, a method of using a route selection table in a network device and a method of dynamically changing a route by looking at network resource status are generally known.

  For example, Patent Document 1 discloses a technology that can realize flexible and efficient route selection and QoS (Quality of Service) control in a mobile communication core network. The technology disclosed in Patent Literature 1 is based on the communication quality requirement conditions for each predetermined packet type (control packet, priority packet, non-priority packet), and the control device determines the optimal route according to the usage status of the core network. It is determined for each.

  Patent Document 2 discloses a technique for selecting an optimum transfer route when there are a plurality of route candidates to be transferred between edge devices of a core network. The technology disclosed in Patent Document 2 determines a transfer destination for each flow by determining a transfer destination or a route to a transfer destination in a certain aggregated flow unit in a table associating a flow with a transfer route. To do.

  In addition, Patent Document 3 discloses a technique for switching the path of a signaling message in an IMS (IP Multimedia System) to a different CSCF (Call Session Control Function) on the SIP (Session Initiation Protocol) protocol. The technology disclosed in Patent Document 3 changes the route information of the flow switch device and rewrites the label added by the gateway and the SIP server.

  In addition, a gateway serving as a connection window from the core network of the mobile phone operator to an external network such as the Internet is designated according to an APN (Access Point Name) set in the user terminal of the mobile communication system. That is, the user terminal starts data communication according to a procedure defined by the standard, and then uses the APN as a packet destination when using a service such as Internet connection.

JP 2010-034961 A JP 2000-253058 A JP 2013-098597 A

  However, the technique described above is path control performed using information in the core network of the communication carrier. Therefore, the route cannot be changed according to the type of content on the Internet accessed by the user.

  Content and application services provided by businesses that are not telecommunications carriers but only supply content exist on the Internet. Most of them are provided by a protocol based on TCP (Transmission Control Protocol) / UDP (User Datagram Protocol). Furthermore, most of them are provided by HTTP (Hypertext Transfer Protocol) / HTTPS (HTTP over SSL: Secure Socket Layer / TLS: Transport Layer Security), and service providers are distinguished by domain names. .

  Therefore, the techniques disclosed in Patent Documents 1 to 3 cannot switch the route in the core network according to the service type actually used by the user on the Internet. For example, in the technologies disclosed in Patent Documents 1 to 3, there is a route control in which communication related to a communication service using LINE, Twitter, etc. used by a large number of users is preferentially passed during a disaster or the like. Can not.

  The present invention provides a mobile communication system and a route selection method for solving the above-described problems and enabling route selection in a mobile communication core network in units of domain names corresponding to service types on the Internet accessed by users. It is to provide.

  In order to achieve the above object, a mobile communication system according to one aspect of the present invention monitors a packet from a core network to a gateway serving as a connection window to an external network including the Internet, and a destination IP included in the packet. The core network predetermined corresponding to the domain name is obtained by performing a reverse query process for a DNS (Domain Name System) server using an (Internet Protocol) address to obtain a domain name corresponding to the destination IP address A domain identification means for identifying a predetermined network in the packet and outputting a route selection information including the identified network IP address and the identified network to the entrance of the core network; and installed at the entrance of the core network And the domain identification means outputs the Based on the road selection information, as the transfer destination of a packet transmitted from a user terminal including the source IP address, characterized in that it comprises a and a path selection control means for selecting the path of the identified networks.

  The route selection method according to another aspect of the present invention monitors a packet from a mobile communication core network toward a gateway serving as a connection window to an external network including the Internet, and a destination IP (Internet Protocol) included in the packet. A domain name corresponding to the destination IP address is obtained by performing a reverse query process for a DNS (Domain Name System) server using the address, and the mobile communication core network defined in advance corresponding to the domain name A predetermined network is identified, route selection information including the source IP address included in the packet and the identified network is fed back to the entrance of the mobile communication core network, and the route is received at the entrance of the mobile communication core network. The source IP address is included based on the selection information. As a transfer destination of a packet transmitted from the user terminal, selects a path of the identified network, characterized in that.

  The present invention can select a route in the mobile communication core network with a domain name corresponding to a service type on the Internet accessed by a user as a unit.

It is a block diagram which shows the structure of 1st Embodiment of the mobile communication system of this invention. It is a flowchart which shows operation | movement of 1st Embodiment of the route selection method of this invention. It is a block diagram which shows the structure of 2nd Embodiment of the mobile communication system of this invention. It is a block part which shows the structure of a domain identification device. It is a figure which shows the content of the control table with which a domain identification device is provided. It is a flowchart which shows operation | movement of the flow setting update part of a domain identification device. It is a flowchart which shows operation | movement of the domain identification control part of a domain identification device. It is a sequence diagram explaining operation | movement of 2nd Embodiment of the route selection method of this invention. It is a sequence diagram explaining another operation | movement of 2nd Embodiment of the route selection method of this invention.

  DESCRIPTION OF EMBODIMENTS Embodiments for carrying out the present invention will be described with reference to the drawings.

The embodiments are examples, and the disclosed apparatus and system are not limited to the configurations of the following embodiments.
(First embodiment)
FIG. 1 is a block diagram showing the configuration of the first embodiment of the mobile communication system of the present invention.

  The mobile communication system 1 according to the first embodiment of the present invention has a domain identification unit 11 and a route selection control unit 12 as main components.

  The domain identification unit 11 monitors a packet from the core network toward the gateway 50 serving as a connection window from the external network including the Internet 60.

  The domain identification unit 11 performs a reverse query process for a DNS (Domain Name System) server 20 using a destination IP (Internet Protocol) address included in the packet to obtain a domain name corresponding to the destination IP address.

  The domain identification unit 11 identifies a predetermined network in a core network that is predetermined in correspondence with the domain name. Then, route selection information including the network identified as the source IP address included in the packet is fed back and output to the entrance of the core network.

  The route selection control means 12 is installed at the entrance of the core network. Here, FIG. 1 shows an example in which the core network includes a first network 31 and a second network 32.

  The route selection control unit 12 selects the identified network route as a transfer destination of the packet transmitted from the user terminal 40 including the transmission source IP address, based on the route selection information output by the domain identification unit.

  FIG. 2 is a flowchart showing the operation of the first embodiment of the route selection method of the present invention.

  First, a packet from a mobile communication core network to a gateway serving as a connection window to an external network such as the Internet is monitored to obtain an IP address (S101).

  Using a destination IP (Internet Protocol) address included in the packet, a reverse query process for a DNS (Domain Name System) server is performed to obtain a domain name corresponding to the destination IP address (S102).

  A predetermined network in the mobile communication core network that is predetermined in correspondence with the domain name is identified (S103).

  The route selection information including the network identified as the transmission source IP address included in the monitored packet is fed back to the entrance of the mobile communication core network (S104).

  At the entrance of the mobile communication core network, based on the route selection information, route selection control is performed to select the route of the network identified as the transfer destination of the packet transmitted from the user terminal including the source IP address (S105). .

As described above, the service type accessed by the user can be specified by performing the reverse query process for the DNS server based on the destination IP address of the packet destined for the Internet and acquiring the domain name corresponding to the destination IP address. Then, by determining the correspondence between the service type and the network used in the core network, it is possible to select a route in the mobile communication core network in units of domain names corresponding to the service. This also enables load distribution within the mobile communication network according to the service type accessed by the user.
(Second Embodiment)
Next, a second embodiment will be described.

  FIG. 3 is a block diagram showing the configuration of the second embodiment of the mobile communication system of the present invention.

  In the mobile communication system 2 according to the second embodiment, a UE (User Equipment) 41 that is a user terminal is connected to an endode 42 that is a radio base station in a radio access network. The endode 42 is a radio base station in the LTE (Long Term Evolution) standard.

  The A network 301 and the B network 302 exemplify networks that constitute the core network in the mobile communication system 2. Each network includes a group of exchanges such as S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway). The A network 301 and the B network 302 share C-PLANE (Control plane) status information. 3 shows only the A network 301 and the B network 302, the core network may include three or more networks.

  An Internet GW (Gateway) 51 is a connection server that connects a carrier network of a communication carrier that operates the mobile communication system and the Internet 60.

  A service 70 indicates an application service provided on the Internet.

  In the mobile communication system 2 of the present embodiment, a network in the core network used for connecting to the Internet GW 51 based on an APN (Access Point Name) set in the UE 41 is referred to as an A network.

  The DNS server 20 is a DNS (Domain Name System) server used by the UE 41. The DNS server 20 is a server that manages the correspondence between domain names and host names and IP addresses on a TCP / IP network.

  The mobile communication system 2 of this embodiment includes a domain identification device 101, a flow control device 102, and a flow switch 103 in addition to the above configuration. The domain identification device 101 corresponds to the domain identification unit 11 in the first embodiment, and the flow control device 102 and the flow switch 103 correspond to the route selection control unit 12 in the first embodiment.

  The domain identification device 101 is installed at the exit of the core network of the mobile communication system 2 of this embodiment.

  The domain identification device 101 monitors a packet directed to the Internet GW 51 serving as a connection window with the Internet 60, and identifies a connection destination domain name of the packet. In identifying the connection destination domain name, the domain identification device 101 performs a reverse query process for the DNS server 20 using the destination IP address included in the packet. That is, a reverse lookup query is performed with the destination IP address to the DNS server 20 that manages the correspondence between the domain name and the IP address, and the domain name corresponding to the destination IP address is acquired from the DNS server 20.

  The domain identification device 101 identifies a predetermined network in a core network that is determined in advance corresponding to the acquired domain name. Then, route selection information including correspondence information between the source IP address included in the packet and the identified network is output to the flow control apparatus 102.

  The flow control device 102 is a device that controls the flow switch 103 installed at the entrance of the core network. The flow control apparatus 102 receives the route selection information including the transmission source IP address notified from the domain identification apparatus 101, and specifies the flow switch 103 to be controlled. Then, the flow control apparatus 102 notifies the specified flow switch 103 of a rewrite rule for packet information.

  The flow switch 103 is installed between the radio access network of the mobile communication system 2 and the core network. The flow switch 103 receives a packet information rewrite rule from the flow control apparatus 102, and rewrites an IP address or the like in a GTP (General packet radio service Tunneling Protocol) header of a packet related to the UE 1 according to the rule.

  Details of the domain identification device 101 will be described with reference to FIGS.

  FIG. 4 is a block diagram showing the configuration of the domain identification device 101.

  The domain identification device 101 includes an IP address acquisition unit 1011, a domain / network correspondence table 1012, a flow table 1013, a flow setting update unit 1014, and a domain identification control unit 1015.

  The IP address acquisition unit 1011 monitors a packet toward the Internet GW 51, and acquires a transmission source IP address and a destination IP address included in the packet.

  The domain / network correspondence table 1012 is a table in which a network constituting a core network in the mobile communication system is associated with a domain name of a service used by a user in advance. A telecommunications carrier operating the mobile communication system 2 determines an exchange group (network) to be used in the core network in accordance with various services provided on the Internet 60. Then, a domain / network correspondence table 1012 is generated by previously associating the domain name providing the service with the network used in the core network. There may be domain names that are not registered in the domain / network correspondence table 1012.

  The flow table 1013 is a table including a transmission source IP address and a destination IP address included in a packet directed to the Internet GW 51, a network used by the user, and a flag for domain identification control described later. In other words, the flow table 1013 is a table in which a source IP address included in a packet is used as an entry key and a destination IP address and a network used when the packet is transferred in the core network are associated with each other. The flow table 1013 manages user flow generation, destination change, and the like.

  FIG. 5 is a diagram showing the contents of these control tables (domain / network correspondence table, flow table) provided in the domain identification apparatus 101.

  The flow setting update unit 1014 generates entries in the flow table 1013 and updates entry contents based on the transmission source IP address and destination IP address acquired by the IP address acquisition unit 1011. The operation of the flow setting update unit 1014 will be described later with reference to FIG.

  The domain identification control unit 1015 executes domain identification control with reference to the flow table 1013 and the domain / network correspondence table 1012.

  In the domain identification control, the domain identification control unit 1015 performs a reverse query process for the DNS server 20 using the destination IP address registered in the flow table 1013. Then, the domain identification control unit 1015 identifies a predetermined network in the core network used by the flow with reference to the domain / network correspondence table 1012 based on the acquired domain name. Further, the domain identification control unit 1015 executes control based on the contents of the flow table 1013 and outputs route selection information to the flow control apparatus 102 as necessary. The operation of the domain identification control unit 1015 will be described later with reference to FIG.

  The operation of the flow setting update unit 1014 will be described with reference to FIG.

  A user request originated from the UE 41 reaches the domain identification device 101 via the node B 42, the flow switch 103, and the A network 301 according to the APN set in the UE 41.

  In the domain identification device 101, the IP address acquisition unit 1011 monitors a packet directed to the Internet GW 51, and acquires a transmission source IP address and a destination IP address included in the packet. The acquired transmission source IP address and destination IP address are notified to the flow setting update unit 1014 (S201).

  When receiving the notification of the IP address, the flow setting update unit 1014 searches the flow table 1013 using the transmission source IP address as a search key, and checks whether there is an entry of the transmission source IP address (S202).

  When there is no entry of the transmission source IP address in the flow table 1013 (S202, none), the flow setting update unit 1014 adds the entry of the transmission source IP address to the flow table 1013 (S203) and ends the process.

  The added entries are a source IP address, a corresponding destination IP address, and a set flag. At this time, the A network used by default is set in the used network column. That is, the A network in the core network used for connecting to the Internet GW 51 is set based on the APN set in the UE 41. Note that the flag of the flow table 1013 displays on the domain identification control unit 1015 that processing for the entry is necessary.

  On the other hand, if there is an entry for the source IP address in the flow table 1013 (Yes in S202), the flow setting update unit 1014 determines whether the acquired destination IP address is the same as the destination IP address set in the flow table 1013. Is determined (S204).

  If the acquired destination IP address and the destination IP address set in the flow table 1013 are the same (S204, the same), the flow setting update unit 1014 does nothing and ends the process.

  On the other hand, when the acquired destination IP address and the destination IP address set in the flow table 1013 are different (S204, different), the flow setting update unit 1014 updates the entry contents (S205) of the flow table 1013 and performs the processing. finish. At this time, the flow setting update unit 1014 rewrites the destination IP address set in the flow table 1013 to the acquired destination IP address, and sets a flag. This considers processing when the user surfs the net or the like and the domain to which the UE 41 is connected changes. Since the destination IP address has been rewritten, the domain identification control unit 1015 displays that processing for the entry is necessary by setting the flag, as in the case of entry generation.

  The domain identification control unit 1015 performs domain identification control with reference to the flow table 1013 set and updated by the flow setting update unit 1014 as described above.

  The operation of the domain identification control unit 1015 will be described with reference to FIG.

  The domain identification control unit 1015 periodically monitors the flag setting of the flow table 1013 (S301).

  When an entry with a flag set is found in the flow table 1013, domain identification is started (S302, yes).

  The domain identification control unit 1015 makes a reverse DNS inquiry to the DNS server 20 based on the destination IP address set in the entry of the flow table 1013 in which the flag is set (S303).

  Then, the domain / network correspondence table 1012 is searched based on the domain name acquired by the reverse DNS query, and the used network set corresponding to the domain name is identified (S304).

  At this time, if the network corresponding to the domain name is not registered, the network used as a default may be identified as being used. In the case of this embodiment, the network used as a default is an A network that is route-selected based on the APN set in the UE 41.

  The domain identification control unit 1015 determines whether or not the current use network needs to be changed (S305). The domain identification control unit 1015 makes this determination by comparing the use network identified by searching the domain / network correspondence table 1012 with the use network set in the flow table 1013.

  As a result of the comparison, when both the used networks are the same, the domain identification control unit 1015 determines that the used network does not need to be changed (S305, unnecessary).

  The domain identification control unit 1015 that has determined that the use network does not need to be changed resets the flag of the corresponding entry in the flow table 1013 and ends the process (S307). That is, when the network used by the new entry flow is the A network and the used network set corresponding to the domain of the service to which the UE 41 is connected is the A network, such processing is performed. It becomes. In addition, even when the user surfs the net or the like and the domain to which the UE 41 is connected has changed, the network that has been used corresponding to the domain to which the connection has been changed is the network that has been used so far. The same processing is performed in the same case.

  On the other hand, if the identified used network is different from the used network set in the flow table 1013, the domain identification control unit 1015 determines that the used network needs to be changed (S305, required).

  The domain identification control unit 1015 that has determined that the network to be used needs to be changed performs processing for feedback notification of route selection information to the flow control apparatus 102 (S306). That is, the domain identification control unit 1015 changes the route at the entrance of the core network so that the transfer destination of the packet having a predetermined transmission source IP address is a network set corresponding to the domain name to which the UE 41 is connected. . Therefore, the domain identification control unit 1015 notifies the flow control apparatus 102 of the route selection information including the transmission source IP address for specifying the target packet and the network information specifying the transfer destination of the packet.

  In the above feedback notification process, the domain identification control unit 1015 rewrites the used network set in the corresponding entry of the flow table 1013. Then, the flag of the entry in the flow table 1013 is reset and the process is terminated (S307).

  The flow control apparatus 102 that has received the route selection information notified by the domain identification control unit 1015 identifies the flow switch 103 to be controlled based on the transmission source IP address, and notifies the flow switch 103 of the rewrite rule of the packet information. . A packet transmitted from the UE 41 after completion of the packet information rewrite rule registration process in the flow switch 103 is transferred within the core network via the designated network.

  8 and 9 are sequence diagrams for explaining the operation of the second embodiment of the route selection method of the present invention.

  The operation of the domain identification device 101 described above is performed asynchronously with packet transfer. In other words, before and after the registration processing of the new route selection information to the flow switch 103 based on the notification from the domain identification device 101 and the packet transfer processing are not guaranteed. That is, the user request is connected to the service 70 on the Internet 60 regardless of the completion of the above-described processing. Then, the response packet is returned to the UE 41, and a response delay to the user request is not generated.

  FIG. 8 shows an example in which the domain identification and the packet information rewriting rule registration process in the flow switch 103 described above are completed by the first user request, and the subsequent user request is transferred through the newly selected B network as a route. Show.

  FIG. 9 shows an example in which the above-described operation of the domain identification device 101 in response to the first user request is not completed even at the time when the subsequent user request is transferred.

  That is, in the case of FIG. 9, the first user request and the next user request are transferred through the A network as a route. However, even in this case, if the operation of the domain identification device 101 is completed when a subsequent user request is transferred, the user request is transferred through the newly selected B network. (Not shown).

  As shown in FIG. 8 and FIG. 9, in this embodiment, not all user requests in a possible range are put into a specific network, but the total communication amount is reduced after minimizing the influence on users. Consideration to control.

  As described above, in this embodiment, a route in the mobile communication core network can be selected in units of domains corresponding to services on the Internet accessed by the user.

  Therefore, in this embodiment, it is possible to change the switch group in the core network used between services having different properties such as Web content and streaming, and efficient resource utilization is possible. In the event of a disaster, it is possible to pass a huge resource to an important service, and it is possible to provide disaster countermeasure support.

  In addition, this embodiment can be realized by performing domain identification processing at the exit of the core network and introducing flow control by a flow switch at the entrance of the core network to an existing mobile communication system, thereby reducing the additional cost. be able to.

  In the above-described embodiment, the case where the networks in the mobile communication core network are physically separated is taken as an example. However, the present invention is effective not only in the case where the use network is physically separated but also in the virtual network.

  In the virtual network, a network management device is installed instead of the flow control device 102 shown in FIG. 3 (not shown).

  The network management device performs both the connection destination switching instruction (route selection control) to the flow switch 103 and resource control for increasing / decreasing the number of processing devices in the B network 302. OpenFlow may be used for route selection control, and OpenStack may be used for resource control. By combining these, the allocation amount of physical resources such as CPU (Central Processing Unit), memory, network I / O (input / output), disk I / O, etc. can be dynamically changed for each domain used by the user. Can do.

  For example, in the domain / network correspondence table provided in the domain identification device, a configuration may be used in which a service usage status in a domain unit or a network load status corresponding to the domain is acquired from outside and dynamically set. When a domain identification device identifies a network corresponding to a domain, the domain identification device can know the service usage status or load status corresponding to the network. Then, the service use status or load status corresponding to the network may be included in the route selection information that is fed back and output to the entrance of the mobile communication core network.

  In this way, in the virtual network, the network management device receives the service usage status of each domain from the domain identification device, so that the resource allocation status of the usage network according to the domain can be dynamically changed. Become.

DESCRIPTION OF SYMBOLS 1, 2 Mobile communication system 11 Domain identification means 12 Path selection control means 20 DNS server 31 1st network 32 2nd network 40 User terminal 41 UE
42 enodeB
50 Gateway 51 Internet GW
60 Internet 70 Service 101 Domain Identification Device 102 Flow Control Device 103 Flow Switch 301 A Network 302 B Network 1011 IP Address Acquisition Unit 1012 Domain / Network Correspondence Table 1013 Flow Table 1014 Flow Setting Update Unit 1015 Domain Identification Control Unit

Claims (10)

Monitors packets going from the core network to a gateway serving as a connection window to an external network including the Internet, and performs reverse query processing for a DNS (Domain Name System) server using a destination IP (Internet Protocol) address included in the packet. To obtain a domain name corresponding to the destination IP address, identify a predetermined network in the core network predetermined corresponding to the domain name, and identify the source IP address included in the packet and the identification Domain identification means for feedback-outputting route selection information including the selected network to the entrance of the core network;
Based on the route selection information that is installed at the entrance of the core network and output by the domain identification unit, the route of the identified network is used as a transfer destination of a packet transmitted from the user terminal including the source IP address. Route selection control means to select;
A mobile communication system comprising: The domain identification means includes
A domain / network correspondence table in which a network constituting the core network and a domain name of a service used by a user are associated in advance;
Using the source IP address included in the packet as an entry key, the destination IP address included in the packet, the network used for forwarding the packet in the core network, and a flag indicating an entry generation or update request The attached flow table,
Based on the source IP address and destination IP address included in the packet, a flow setting update unit that performs entry generation or entry content update of the flow table and sets the flag;
Based on the destination IP address included in the entry in which the flag of the flow table is set, the reverse query process for the DNS server is executed to obtain the corresponding domain name, and the domain / network correspondence table is referred to A domain identification control unit that identifies the network corresponding to the acquired domain name and generates the route selection information to notify the route selection control means, and resets the flag at the end of processing;
The mobile communication system according to claim 1, further comprising: The flow setting update unit
When there is no entry corresponding to the source IP address included in the packet in the flow table, a new entry including the destination IP address corresponding to the source IP address and the network is generated and included in the packet And the destination IP address set in the entry is different when the destination IP address included in the packet is different from the destination IP address set in the entry. The mobile communication system according to claim 2, wherein the IP address is updated with a destination IP address included in the packet. The domain identification control unit
When the network corresponding to the domain name identified with reference to the domain / network correspondence table is different from the network set in the corresponding entry of the flow table, the route selection information is generated, and the flow table The network according to claim 2 or 3, wherein the network set in the corresponding entry is updated with a network corresponding to the domain name identified by referring to the domain / network correspondence table. Communications system. The route selection control means
A flow switch that is installed between the radio access network and the core network and rewrites an IP address of a packet that passes through a designated rewrite rule;
A flow control device that identifies the flow switch to be controlled based on the notified route selection information and notifies the flow switch of the rewrite rule for rewriting an IP address of a packet passing therethrough. The mobile communication system according to any one of claims 1 to 4, wherein the mobile communication system is characterized. The network constituting the core network is a virtual network, and the route selection control means includes:
A flow switch that is installed between the radio access network and the core network and rewrites an IP address of a packet that passes through a designated rewrite rule;
In response to the notification of the route selection information including the service usage status in domain units, the flow switch to be controlled is specified, and the rewrite rule for rewriting the IP address of the passing packet is notified to the flow switch, 5. The migration according to claim 1, further comprising a network management device that dynamically changes and controls a resource allocation amount of the virtual network used corresponding to a domain name. Communications system. Monitor packets going from the mobile communication core network to the gateway that serves as a connection window to external networks including the Internet.
Using a destination IP (Internet Protocol) address included in the packet, perform reverse query processing for a DNS (Domain Name System) server to obtain a domain name corresponding to the destination IP address,
A predetermined network in the mobile communication core network predetermined corresponding to the domain name is identified, and a source IP address included in the packet and route selection information including the identified network are included in the mobile communication core network Feedback output to the
Selecting a path of the identified network as a transfer destination of a packet transmitted from a user terminal including the transmission source IP address based on the path selection information at an entrance of the mobile communication core network;
A route selection method characterized by the above. A domain / network correspondence table in which a network constituting the mobile communication core network and a domain name of a service used by a user are associated in advance, and a source IP address included in the packet is included in the packet as an entry key. A flow table in which a destination IP address, the network used for forwarding the packet in the core network, and a flag indicating an entry generation or update request are associated with each other, and
Based on the source IP address and the destination IP address included in the packet, perform entry generation or update of the entry contents of the flow table, set the flag,
Based on the destination IP address included in the entry in which the flag of the flow table is set, a reverse query process is performed on the DNS server to obtain a corresponding domain name,
8. The domain / network correspondence table is referred to, the route selection information is generated by identifying the network corresponding to the acquired domain name, and the flag is reset at the end of processing. The described route selection method. The flow table entry generation or entry content update is as follows:
If there is no entry corresponding to the source IP address included in the packet in the flow table, a new entry including the destination IP address corresponding to the source IP address and the network is generated,
When there is an entry corresponding to the source IP address included in the packet in the flow table, the destination IP address included in the packet is different from the destination IP address set in the entry. 9. The route selection method according to claim 8, wherein the set destination IP address is updated with a destination IP address included in the packet. When the network corresponding to the domain name identified with reference to the domain / network correspondence table is different from the network set in the corresponding entry of the flow table, the route selection information is generated,
10. The network set in the corresponding entry of the flow table is updated with a network corresponding to the domain name identified with reference to the domain / network correspondence table. The described route selection method.

Images