WO2010010945A1

WO2010010945A1 - Mobile communication system, traffic transfer device, and traffic transfer method and program

Info

Publication number: WO2010010945A1
Application number: PCT/JP2009/063266
Authority: WO
Inventors: 和彦原崎
Original assignee: 日本電気株式会社
Priority date: 2008-07-24
Filing date: 2009-07-24
Publication date: 2010-01-28
Also published as: JP2010028774A; JP4506883B2

Abstract

Routing depending on the type of traffic is realized without adding a terminal function and complicating radio access bearer control. An MAG (100) operating as a traffic transfer device identifies the bearer type of a radio access bearer (300) set up between the MAG (100) and a user terminal or analyzes the flow in the radio access bearer (300). On the basis of the results of the identification of the bearer type of the radio access bearer (300) or the analysis of the flow, the MAG (100) determines whether or not the transfer destination is a proxy mobile IP client and transfers the traffic.

Description

Mobile communication system, traffic transfer apparatus, traffic transfer method and program

(Description of related applications)
The present invention is based on the priority claim of Japanese patent application: Japanese Patent Application No. 2008-191305 (filed on July 24, 2008), the entire contents of which are incorporated herein by reference. Shall.
The present invention relates to a mobile communication system, a traffic transfer apparatus, a traffic transfer method, and a program, and more particularly to a mobile communication system, a traffic transfer apparatus, and a traffic transfer that realizes IP mobility by detecting movement of a mobile terminal and managing movement on the network side. The present invention relates to a method and a program.

In recent years, standardization of next-generation networks such as SAE (System Architecture Evolution) and All-IP NETWORK (AIPN) has been studied (see Non-Patent Documents 1 and 2).

As the mobility control method in the network, there are a method in which a route change instruction is given on the terminal side represented by MIPv4 and MIPv6, and a method in which a route change function is provided on the network side represented by PMIPv4 and PMIPv6 (Proxy Mobile IPv6). Proposed. PMIPv6 is based on MIPv6 (Mobile IPv6; also referred to as “CMIP”), and is a method for performing movement management by detecting movement of a mobile terminal on the network side. PMIPv6 has an advantage that IP mobility can be realized without adding a protocol-specific function to a mobile terminal (see Non-Patent Document 3).

In addition, Patent Documents 1 and 2 disclose a mobile communication system using the former MIPv6.

Re-specialized WO2005 / 006674 JP 2006-222251 A

The entire disclosures of Patent Documents 1 and 2 and Non-Patent Documents 1 to 3 are incorporated herein by reference.
The following is an analysis of the related art according to the present invention.
The problems of the mobile communication systems described in Non-Patent Documents 1 and 2 will be described using FIGS.

FIG. 5 shows a case where a local breakout from the mobile access gateway (MAG) 100 on the visited network 600 side is selected. In this case, a SIP (Session Initiation Protocol) signal (broken line in FIG. 5) is also locally broken out, and the highly reliable mobile relay network 701 from the SIP server 501 in the home network 500 to the MAG 100 in the visited network 600. Instead, it goes through an unspecified network such as the Internet 700. For this reason, there is a high possibility that the reliability of the signal for controlling the voice call is impaired, or the connection service time is affected by a transmission delay or the like.

FIG. 6 shows a case where access via the MAG 100 on the home network 500 side is selected. In this case, although the SIP signal (broken line in FIG. 6) passes through the reliable mobile relay network 701, the voice data (the one-dot chain line in FIG. 6) always passes through the home network 500. For example, since a P2P communication via the home network 500 is always performed even in a voice call with the terminal 401 in the visited network, there is an adverse effect on service quality such as voice quality degradation due to meaningless transmission delay. Concerned.

In order to overcome the problem of inappropriate transfer of traffic, it is conceivable to make the radio access bearer 300 dual stack as shown in FIG. In the example of FIG. 7, the mobile IP client is activated on the terminal 400 side only with the IP version of the SIP signal (broken line in FIG. 7), and the client mobile IP tunnel is established between the home agent (HA) 506 in the home network 500 and the terminal 400. 507 is established, and the SIP signal is always passed through the HA 506 of the home network 500. In this case, it is necessary to start the mobile IP client on the terminal 400 side, and the traffic overhead between the terminal and the network and the mobile IP client function on the terminal side must be provided, so the advantage of PMIP is lost. In addition, since routing from the HA 506 to the client mobile IP tunnel 507 is user traffic routing addressed to the IP address of the terminal 400, there is a problem that there is a high possibility that the routing will be via an unspecified relay network.

As an approach different from that of FIG. 7, as shown in FIG. 8, a packet data network (PDN) is separated for signaling and voice packets, and a radio access bearer 300a and a radio access bearer 300b are established. A method of using

different MAGs

100 and 504 is also conceivable. In this case, radio access bearers for different PDNs are always set, and mobility & bearer control is performed under different mobile anchors. Therefore, it is necessary to perform multiple mobility management and bearer control. There is a problem that it becomes complicated.

The present invention has been made in view of the above-described circumstances, and the object thereof is to impair the advantages of a system having a route change function on the network side represented by PMIPv6 (Proxy Mobile IPv6) It is an object of the present invention to provide a mobile communication system, a traffic transfer apparatus, a traffic transfer method, and a program that can realize traffic selection routing.

According to a first aspect of the present invention, means for identifying a bearer type of a radio access bearer established with a user terminal for accessing a packet data network (PDN) (bearer type determination unit), In place of the user terminal, a traffic transfer comprising a proxy mobile IP client that manages the movement of the user terminal, and means (traffic transfer unit) for transferring traffic having a predetermined bearer type to the proxy mobile IP client An apparatus or a mobile communication system including the traffic transfer apparatus is provided.

According to a second aspect of the present invention, means (flow analysis unit) for analyzing a flow in a radio access bearer established with a user terminal to access a packet data network (PDN), the user A traffic comprising a proxy mobile IP client that manages movement of a user terminal on behalf of a terminal, and means (traffic forwarding unit) that forwards specific traffic identified by the analysis to the proxy mobile IP client A transfer apparatus or a mobile communication system including the traffic transfer apparatus is provided.

According to the third aspect of the present invention, a traffic transfer method implemented in the above-described mobile communication system is provided. According to this method, the traffic transfer apparatus analyzes the bearer type identification of the radio access bearer established with the user terminal or the flow in the radio access bearer. Then, the traffic transfer device determines whether to use the proxy mobile IP client as a transfer destination or a local breakout based on the bearer type or flow analysis result of the radio access bearer, and controls to transfer the traffic Is done. Note that this method is associated with a specific machine that performs identification of a bearer type of a radio access bearer or a flow in the radio access bearer and performs traffic transfer control based on the result.

According to the fourth aspect of the present invention, there is provided a program that is executed by a computer constituting the above-described traffic transfer apparatus. This program determines whether the proxy mobile IP client is a forwarding destination according to the means (or flow analysis means) for identifying the bearer type of the radio access bearer and the bearer type (or flow analysis result) of the radio access bearer. Alternatively, it is possible to make an arbitrary computer function as a means for determining whether a local breakout occurs and transferring traffic. This program can be recorded on a computer-readable storage medium. That is, the present invention can be embodied as a computer program product.

According to the present invention, routing according to the traffic type can be realized without adding a terminal function or complicating radio access bearer control. The reason is that the network-side traffic transfer apparatus is provided with means for estimating the traffic type and means for performing routing based on the estimation result.

It is a figure showing the structure of the mobile communication system which concerns on the 1st Embodiment of this invention. It is a block diagram showing the structure of the mobile access gateway (MAG) of the 1st Embodiment of this invention. It is a figure showing the structure of the mobile communication system which concerns on the 2nd Embodiment of this invention. It is a block diagram showing the structure of the mobile access gateway (MAG) of the 2nd Embodiment of this invention. It is a figure for demonstrating the problem of the mobile communication system which does not have a traffic transfer function. It is a figure for demonstrating the problem of the mobile communication system which does not have a traffic transfer function. It is a figure for demonstrating the problem of the mobile communication system which does not have a traffic transfer function. It is a figure for demonstrating the problem of the mobile communication system which does not have a traffic transfer function.

100 MAG
101 Bearer type determination unit 102 PMIPv6 client 110 Flow analysis unit 200

Mobile access network

300, 300a, 300b Radio access bearer 310 Default bearer 311 Dedicated

bearer

400, 401 Terminal 500 Home network 501 SIP server 504 MAG
505, 601 PDN (packet data network)
506 HA (Home Agent)
507 Client mobile IP tunnel (CMIP tunnel)
510 PMIPv6 inter-node tunnel 511 HA / MAP (home agent / mobile anchor point)
600 Visited network 700 Internet 701 Mobile relay network

Subsequently, preferred embodiments of the present invention will be described in detail with reference to the drawings.

[First Embodiment]
FIG. 1 is a diagram illustrating a configuration of a mobile communication system according to the first embodiment of the present invention. Referring to FIG. 1, a home network 500 in which a SIP server 501 and a home agent / mobile anchor point (HA / MAP) 511 are arranged, a packet data network (PDN), and a MAG 100 are arranged to provide services to

terminals

400 and 401. A visited network 600, the Internet 700, and a mobile relay network 701 are shown.

The MAG 100 includes a PMIPv6 client as described later, and implements IP mobility with the HA / MAP 511 of the home network 500 in place of the terminal 400 that does not have the PMIPv6 client. Further, the MAG 100 establishes a PMIPv6 internode tunnel 510 with high security between the home network 500 and the visited network 600 via the mobile relay network 701 in order to establish a mobility tunnel between network nodes. Furthermore, the MAG 100 according to the present embodiment further includes a bearer type determination unit, and operates as a traffic transfer device described later.

It is assumed that the MAG 100 and the terminal 400 support IPv4 / v6 dual stack on the same radio access bearer 300.

Further, the terminal 400 applies IPv6 to the always-connectable IMS SIP signal (broken line in FIG. 1) and dynamically establishes voice data (one point in FIG. 1) when a voice call is actually generated. It is assumed that IPv4 is applied to the chain line.

In the following description, a secure PMIPv6 inter-node tunnel 510 is established between the PMIPv6 client 102 of the MAG 100 of the visited network 600 and the HA / MAP 511 of the home network 500 via the mobile relay network 701. It shall be.

FIG. 2 is a block diagram showing a configuration example of the MAG 100 of the present embodiment. Referring to FIG. 2, a MAG 100 including a bearer type determination unit 101 and a PMIPv6 client 102 is illustrated.

2 represents a state in which a default bearer 310 and a dedicated bearer 311 are established in a radio access bearer accommodated by the MAG 100 in accordance with the S5 GTP model (see Non-Patent Document 1) of the SAE architecture.

The bearer type determination unit 101 identifies the bearer type in the radio access bearer 300 and performs an operation of changing the traffic forwarding destination based on each bearer type, the PDN 601 and the policy for each user. In the example of FIG. 2, the bearer type determination unit 101 determines that user traffic in the default bearer 310 is signaling for IMS SIP, and transfers it to the PMIPv6 client 102. The bearer type determination unit 101 determines that traffic in the Dedicated bearer 311 is voice data, and transfers the local breakout to the PDN 601. The bearer type (default bearer / Dedicated bearer) described above can be identified by a tunnel ID (TEID; Tunnel Endpoint ID) given to a tunnel header of GTP (GPRS Tunneling Protocol).

The PMIPv6 client 102 is a PMIPv6 client that operates on behalf of the terminal 400 that does not have a PMIPv6 client. The PMIPv6 client 102 transfers the transferred user traffic in the default bearer 310 to the SIP server 501 via the PMIPv6 inter-node tunnel 510.

Although the configuration of the present embodiment has been described above, the PMIPv6 client 102, the default bearer 310, and the Dedicated bearer 311 in FIG. 2 are given as specific examples of the present invention and are well known to those skilled in the art. Since it is not directly related to the present invention, its detailed description is omitted.

Subsequently, the operation of the present embodiment will be described in detail with reference to FIG. Hereinafter, an example in which a voice call is made from the terminal 400 to the terminal 401 via the SIP server 501 will be described. First, when the terminal 400 attaches to the mobile access network 200, the terminal 400 establishes a default bearer 310 in the radio access bearer 300 for PDN 601 access, and assigns it to the IPv6 SIP signal for IMS (broken line in FIG. 1).

The bearer type determination unit 101 determines the bearer type. Here, since the traffic is in the default bearer 310, it is determined as IMS SIP signaling, and the bearer type determination unit 101 connects the default bearer 310 and the PMIPv6 client 102.

The PMIPv6 client 102 establishes the PMIPv6 internode tunnel 510 with the HA / MAP 511 arranged in the user's home network 500 without passing through the PDN 601 after receiving the establishment of the default bearer 310.

Note that it is assumed that the above-described PMIPv6 inter-node tunnel 510 has a policy of passing through the mobile relay network 701 by agreement between mobile operators. Therefore, the SIP signal can always be transmitted and received between the home network 500 and the terminal 400 via a secure network.

Thereafter, when the terminal 400 establishes an IMS call with the SIP signal (broken line in FIG. 1) via the SIP server 501, the terminal 400 establishes a Dedicated bearer 311 for IPv4 voice data (dashed line in FIG. 1) communication. .

The bearer type determination unit 101 transfers the traffic in the Dedicated bearer 311 to the PDN 601 and realizes a local breakout of voice data.

Also, the bearer type determination unit 101 transfers the received traffic to the default bearer 310 or the dedicated bearer 311. At that time, the bearer type determination unit 101 performs a rule check on a packet to be received via PMIPv6 (IPv6) and a packet to be received via PDN 601 (IPv4), and has a function of preventing reception of a packet in violation of the rule. Shall have.

As described above, in the present embodiment, it is allowed to mix local breakout traffic and PMIPv6-compatible traffic, and optimal routing according to the traffic type is possible.

Also, as described above, since only the radio access bearer 300 addressed to a single PDN is used, it is not necessary to make the radio access bearer control in the mobile access network 200 complicated.

Further, in the present embodiment, the proxy mobile IP (PMIP) is applied to the traffic via the home network 500 such as the SIP signal without using the user packet routing logic of the client base mobile IP such as MIPv4 and MIPv6. The secure mobile relay network 701 can be used by routing with inter-node routing logic between the home node and the visited node.

Furthermore, in the present embodiment, since the proxy mobile IP (PMIP) is used as described above, it is not necessary to install the mobile IP function in the terminal 400, the terminal function can be simplified, and the mobile access network 200 There is also an advantage that signaling signals and data overhead between the terminal 400 and the MAG network can be reduced.

[Second Embodiment]
Next, a second embodiment of the present invention that assumes a case where there is no bearer type in the radio access bearer 300 accommodated by the MAG 100, such as the S5 IETF model of the SAE architecture, will be described.

FIG. 3 is a diagram showing the configuration of the mobile communication system according to the second embodiment of the present invention. The difference from the configuration of the first embodiment described above is that there is no bearer type in the radio access bearer 300. Hereinafter, the detailed configuration of the MAG 100, which is different from the configuration of the first embodiment, will be described in detail with reference to FIG.

FIG. 4 is a block diagram showing a configuration example of the MAG 100 of the present embodiment. Referring to FIG. 4, a MAG 100 including a flow analysis unit 110 and a PMIPv6 client 102 is shown.

The flow analysis unit 110 analyzes the user traffic in the radio access bearer 300, and changes the transfer destination of traffic based on the protocol type (IPv6 / v4) of the transfer packet obtained by the analysis, the PDN 601, and the policy for each user. Perform the action. In the example of FIG. 4, the flow analysis unit 110 determines that the IPv6 traffic is signaling for IMS SIP, and transfers it to the PMIPv6 client 102. Also. The bearer type determination unit 101 determines that the IPv4 traffic is voice data, and transfers the local breakout to the PDN 601. Note that the protocol type (IPv6 / v4) of the transfer packet can be obtained by analyzing information such as the port number of the IP packet header or the UDP header.

Other configurations and operations are the same as those of the first embodiment described above. As described above, by providing a function of determining a traffic transfer destination based on the IP version or the like instead of the bearer type, it is possible to perform optimum routing according to the traffic type.

The preferred embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments, and further modifications, replacements, and replacements may be made without departing from the basic technical idea of the present invention. Adjustments can be made. For example, the PMIPv6 client 102 has been described as being provided in the MAG 100. However, the PMIPv4 client 102 and a Foreign Agent (FA) may be used.

In the above-described embodiment, an example using PMIPv6 as a mobility protocol has been described. However, the present invention can also be applied to other mobility protocols.

In addition, the present invention is based on mobile core networks SAE / EPC (System Architecture Evolution / Evolved PP) standardized for LTE (Long Term Evolution), which is currently being standardized by 3GPP (Third Generation Partnership Project). It can be used in the mobile core network IP-CAN (Internet Protocol-Connectivity Access Network) for UMB (Ultra Mobile Broadband) that is being advanced.
The present invention has been described with reference to the above embodiment, but the present invention is not limited to the configuration of the above embodiment, and various modifications that can be made by those skilled in the art within the scope of the present invention. Of course, including modifications.
Within the scope of the entire disclosure (including claims) of the present invention, the embodiments and examples can be changed and adjusted based on the basic technical concept. Further, various combinations or selections of various disclosed elements are possible within the scope of the claims of the present invention (claims).

Claims

Means for identifying a bearer type of traffic in a radio access bearer established with a user terminal to access a packet data network;
In place of the user terminal, a proxy mobile IP client that manages the movement of the user terminal;
Means for forwarding traffic having a predetermined bearer type to the proxy mobile IP client;
A mobile communication system comprising:
Instead of means for identifying the bearer type of traffic in the radio access bearer and means for transferring traffic having a predetermined bearer type to the proxy mobile IP client,
Means for analyzing a flow in the radio access bearer;
Means for forwarding the specific traffic identified by the analysis to the proxy mobile IP client;
A mobile communication system according to claim 1.
Identifying a bearer type of traffic in the radio access bearer by a tunnel ID (TEID) given to a tunnel header of GTP (GPRS Tunneling Protocol);
The mobile communication system according to claim 1, wherein traffic passing through a default bearer is forwarded to the proxy mobile IP client.
The mobile communication system according to claim 2, wherein traffic identified as IPv6 as a result of the analysis is forwarded to the proxy mobile IP client.
The proxy mobile IP client is configured to establish an IP data transfer route with a route based on a predetermined policy with a mobility anchor point of a home network. Mobile communication system.
The mobile communication system according to any one of claims 1 to 5, wherein a mobile access gateway (MAG) operates as the traffic transfer device.
Means for identifying a bearer type of traffic in a radio access bearer established with a user terminal to access a packet data network;
In place of the user terminal, a proxy mobile IP client that manages the movement of the user terminal;
Means for forwarding traffic having a predetermined bearer type to the proxy mobile IP client;
A traffic transfer apparatus having
Instead of means for identifying the bearer type of traffic in the radio access bearer and means for transferring traffic having a predetermined bearer type to the proxy mobile IP client,
Means for analyzing a flow in the radio access bearer;
Means for forwarding the traffic specified by the analysis to the proxy mobile IP client;
The traffic transfer device according to claim 7.
Identifying a bearer type of traffic in the radio access bearer by a tunnel ID (TEID) given to a tunnel header of GTP (GPRS Tunneling Protocol);
The traffic transfer apparatus according to claim 7, wherein traffic passing through a default bearer is transferred to the proxy mobile IP client.
A traffic transfer apparatus connected to the packet data network identifies a bearer type of traffic in a radio access bearer established with a user terminal, and
A traffic forwarding method in which the traffic forwarding device forwards traffic having a predetermined bearer type to a proxy mobile IP client that manages movement of a user terminal on behalf of the user terminal.
Identifying a bearer type of traffic in the radio access bearer by a tunnel ID (TEID) given to a tunnel header of GTP (GPRS Tunneling Protocol);
The traffic forwarding method according to claim 10, wherein traffic passing through a default bearer is forwarded to the proxy mobile IP client.
The traffic transfer device connected to the packet data network analyzes the flow in the radio access bearer established with the user terminal,
A traffic forwarding method in which the traffic forwarding device forwards specific traffic identified by the analysis to a proxy mobile IP client that manages movement of a user terminal on behalf of the user terminal.
A process in which a traffic transfer apparatus connected to a packet data network identifies a bearer type of traffic in a radio access bearer established with a user terminal;
A process of transferring traffic having a predetermined bearer type to a proxy mobile IP client that performs mobility management of the user terminal on behalf of the user terminal;
A program for causing a computer constituting the traffic transfer apparatus of the mobile communication system to execute.
Identifying a bearer type of traffic in the radio access bearer by a tunnel ID (TEID) given to a tunnel header of GTP (GPRS Tunneling Protocol);
The program according to claim 13, wherein traffic passing through a default bearer is transferred to the proxy mobile IP client.
A process in which a traffic transfer apparatus connected to a packet data network analyzes a flow in a radio access bearer established with a user terminal;
A process of transferring the specific traffic identified by the analysis to a proxy mobile IP client that performs mobility management of the user terminal on behalf of the user terminal;
A program for causing a computer constituting the traffic transfer apparatus of the mobile communication system to execute.