JP4500830B2 - Communication system, control apparatus, router and communication method using network-based IP mobility protocol - Google Patents

Description

  The present invention relates to a communication technique using a network-based IP mobility protocol.

  In recent years, research and development of mobility support in the IP layer such as Mobile IPv6 (Internet Protocol version 6) has been active. Mobile IP is a network layer protocol that is the third layer in the OSI (Open Systems Interconnection) basic reference model established by ISO (International Organization for Standardization). This is a technology that conceals communication interruptions and continues communication.

  TCP / IP (Transmission Control Protocol / Internet Protocol), which is a communication protocol generally used in the current Internet, means an IP address as an identifier, and also a position on a network. For this reason, when a node connected to a certain network is changed to another network, the IP address changes, and the session cannot be continued.

  Therefore, Mobile IP assigns a unique address to a node and replaces it with the IP address actually used in the TCP / IP stack. Provides a mechanism that makes it appear as if it is communicating (for example, see Non-Patent Document 1).

  The Mobile IP includes a mobile node (Mobile Node, mobile terminal, hereinafter referred to as “MN”), a home agent (Home Agent, hereinafter referred to as “HA”), a correspondent node (Correspondent Node, an opposite node, hereinafter, “CN”). ”)).

  The MN always has an invariable address called a home address (hereinafter referred to as “HoA”), and the node that manages the address is the HA. When the MN connects to a network other than the home link, which is a link of the HA, an address that is actually used for communication called a care-of address (care-of-address, hereinafter referred to as “CoA”) For example, it is obtained by router advertisement (Router Advertisement, hereinafter referred to as “RA”) with stateless address automatic setting or DHCP (Dynamic Host Configuration Protocol) v6 with stateful address automatic setting. The MN notifies the HA of the CoA obtained here with a message of a registration request (Binding Update, hereinafter referred to as “BU”).

  As a result, when a node (= CN) that wants to communicate with the MN transmits a packet to the HoA, the HoA is a link address managed by the HA, and therefore reaches the HA once. At that time, the HA transfers to the CoA associated with the HoA. As a result, the MN can always communicate with HoA. In the MN, an application operating on the MN always uses the IP address called HoA for communication.

  CoA is used as the source address or destination address of the actual IPv6 packet. Further, in order to conceal the movement from the upper application, techniques such as IPv6 in IPv6 encapsulation and mobility header are used. As a result, HoA is notified to the application, and the IPv6 address (CoA) actually used is concealed.

  However, since Mobile IPv6 cannot perform high-speed handover, FM IPv6 (Fast Hands for Mobile IPv6) has been proposed (see, for example, Non-Patent Document 2).

  FIG. 15 is a sequence diagram illustrating a processing procedure in FMIPv6. FIG. 15 will be described as an example.

  RtSolPr (Router Solicitation for Proxy Advertisement, hereinafter referred to as “RtSolPr”) of S601 in FIG. 15 is a message that is sent by a host used in normal IPv6 to generate a router advertisement to the router. Router solicitation (router solicitation) is extended for FMIPv6.

  In step S602, the PAR (Previous Access Router, hereinafter referred to as “PAR”) that has received this RtSolPr from the MN sends the PrRtAdv (Proxy Router Advertisement, proxy router advertisement, hereinafter referred to as “PrRtAdv”) to the MN. Send to. PrRtAdv is an extension of the RA used for normal IPv6 for FMIPv6.

  The MN that has received this PrRtAdv transmits an FBU (Fast Binding Update), which is a binding update for fast handover, to the PAR in S603. This FBU includes NCoA (New Care of Address, new CoA, hereinafter referred to as “NCoA”) information, and NCoA is NAR (New Access Router, destination access router, hereinafter referred to as “NAR”). Since the address belongs to the link, the PAR can transfer the packet to the NAR.

  The PAR that has received the FBU transmits HI (Handover Initiate, hereinafter referred to as “HI”) to initialize the MN switching and handover to the NAR in S604.

  The NAR transmits HAck (Handover Acknowledge, hereinafter referred to as “HAck”) to the PAR as confirmation for the HI in S605, and packet transfer between the PAR and the NAR is started in S606.

  When the MN finishes moving and completes moving under the NAR (same link), it transmits FNA (Fast Neighbor Advertisement, hereinafter referred to as “FNA”) to the NAR in S607. This is to notify the NAR that the movement has been completed. As a result, in S608, the NAR starts delivering a packet to the MN.

  MIPv6 and FMIPv6 are called host-based mobility protocols because they control mobility based on the MN. On the other hand, a network-based IP mobility protocol that performs mobility control on the network side and enables the MN to move without installing a special protocol for movement has been further proposed by IETF (Internet Engineering Task Force). (For example, refer nonpatent literature 3).

  This eliminates the need for the MN to handle CoA, eliminates packet encapsulation by the MN, and eliminates signaling for movement by the MN. This network-based IP mobility protocol handover method will be described with reference to FIG.

  First, after the movement, in S701, the MN moves to the router and mobile access gateway (Mobile Access Gateway, hereinafter referred to as “MAG”) of the link of the movement destination indicated as “NewMAG” in FIG. A Router Configuration, a router request, hereinafter referred to as “RS”) or a network configuration (network setting) request message such as DHCP Request is transmitted.

MAG is a router that relays between a MN that has moved to a link and a root router, which is a control device that controls IP Mobile, and a local mobility anchor (hereinafter referred to as “LMA”). It is.
The LMA controls a plurality of MAGs connected via a network. The LMA manages the identifiers and IP addresses of the MN and MAG in the storage unit.
The MAG also manages the identifiers and IP addresses of the MN and LMA in the storage unit. Information managed by these MAGs can be acquired by communicating with the LMA.
Between MAG and LMA, packets are IPv6 in IPv6 encapsulated, and a header is attached with reference to information managed in the storage unit, so that tunneling can be performed and routing can be performed correctly.
In the network as described above, it is assumed that the MN transmits, for example, an RS here to the MAG of the same link at the movement destination.

  When MAG (NewMAG) receives RS from MN, it transmits location registration (location registration request) to LMA in S702.

  When the LMA receives the location registration, it detects that it is a handover, transmits a routing setup to the MAG (NewMAG) in S703, and sets a tunnel path between the MAG (NewMAG) and the LMA.

  Here, the setting of the tunnel path means that the LMA encapsulates the packet for the MN and transmits the destination as the MAG, and the received MAG is set to remove the capsule and forward it to the MN.

  Upon receiving this routing setup, the MAG (NewMAG) transmits a confirmation routing setup Ack (Acknowledgement) to the LMA in S704.

  The LMA that has received the location registration from the MAG (NewMAG) transmits a confirmation location registration Ack to the MAG (NewMAG) in S705.

  In step S706, the MAG (NewMAG) transmits an RA to the MN, and the MN performs address configuration (address setting).

  After that, in S707, the MN uses DAD (Duplicate Address Detection, hereinafter referred to as “DAD”) for NA (Neighbor Advertisement, hereinafter referred to as “NA”) to MAG (NewMAG). Confirm that the address is single and complete the address configuration. Further, the MAG (NewMAG) transmits the MN address setup to the LMA in S708, and in S709, the LMA transmits the MN address setup Ack to the MAG (NewMAG).

  As a result of completion of the LMA-MAG tunnel path setting and the MN address configuration, the packet can reach the MN. This is the handover method of the network-based mobility protocol. That is, since the packet addressed to the MN is sent via the LMA, the tunnel can be routed to the MN by completing the tunnel between the LMA and the MAG.

  Also, a Proxy Mobile IP method using a network-based IP mobility protocol in which MAG performs an MN proxy (proxy) function in MobileIP using an AAA (Authentication Authorization Accounting) server that performs authentication and the like is also proposed. (For example, refer nonpatent literature 4).

  A handover procedure according to the Proxy Mobile IP system of the second network-based IP mobility protocol will be described with reference to the sequence diagram of FIG.

  First, in S801, after movement, the MN transmits authentication information including the MN-ID that is its own ID to the MAG (NewMAG).

  In step S802, the MAG that has received the authentication information from the MN (NewMAG) transmits the authentication information including the MN-ID to the AAA server that is the authentication server for authentication.

  The AAA server that has received the authentication information from the MAG (NewMAG) confirms the validity of the MN in S803, and returns a policy profile if it is determined to be valid. This policy profile includes MN address configuration information including information such as a home network prefix and a configuration method (stateless setting or stateful setting).

  In the MAG (NewMAG) that has received the policy profile including the address configuration information from the AAA server, the RA can be transmitted to the MN. In S804, the RA is transmitted to the MN.

  In step S805, the MN that has received the RA from the MAG (NewMAG) configures an address and performs NA or DAD. This step may be omitted.

When the MAG (NewMAG) transmits the RA, in order to generate a tunnel with the LMA, a proxy registration request (Proxy Binding Update) is transmitted to the LMA in S806.
This message includes the MN-ID, the home prefix of the MN, and the like.

  In step S807, the LMA that has received the Proxy Binding Update returns a Proxy Binding Update Ack to the MAG (NewMAG) for confirmation.

  In this way, a bidirectional tunnel is generated between the LMA and MAG, and routing to the MN becomes possible.

  Further, as a technique for compressing the header of IP / UDP / RTP (Internet Protocol / User Datagram Protocol / Real-time Transport Protocol), robust header compression (hereinafter referred to as “ROHC”) is known. (For example, refer nonpatent literature 5).

  In this ROHC, a CID (Context ID), which is an identification ID notified at initialization, is associated with a predictable header field, and the information is shared by the compressor that compresses the data and the decompressor that restores the compressed data, The compressor sends a CID instead of the header, and the decompressor restores the header from the CID.

  The predictable header field also includes information on the source IP address indicating the transmission source and the destination IP address indicating the transmission destination.

  Furthermore, by assigning sequence numbers by W-LSB (Window-Based Last-Significant Bit), other fields can be predicted, and robustness against packet loss is also provided.

  ROHC has a state and a mode. The state adjusts the amount of compression according to the state of the link in three stages: full header / difference / maximum compressed header. The mode is selected from three types of feedback timing by the decompressor: no feedback, feedback if there is a problem, and always feedback.

  By selecting this state and mode according to the link state and W-LSB, ROHC provides high compression performance and high robustness.

  Also, a header compression context rearrangement method is disclosed (see, for example, Patent Document 1).

According to the invention, the old serving support node (SGSN) forwards the context on header compression to the new SGSN and reuses it at the new SGSN.
Special table 2004-517580 gazette Request for Comments (RFC) 3775, “Mobility Support in IPv6” Request for Comments (RFC) 4068, “Fast Handovers for Mobile IPv6” Internet Draft “draft-gearetta-netlmm-dt-protocol” Internet Draft “draft-sgandave-mip6-proxymip6” Request for Comments (RFC) 3095, “RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed”

  However, it is difficult to use this ROHC in the network-based IP mobility protocol.

  The main purpose of header compression in this way is to save the bandwidth of the last one hop (in many cases, a radio link), which is the narrowest band. Otherwise, the effect is small, and the effect is small unless the compressor of the packet from the MN is also the MN.

  In other words, the decompressor for packets destined for the MN should be the MN. At this time, the compressor is LMA or MAG. Here, if compression is performed with LMA, the MAG through which the packet arrives from the LMA has no IP address information of the MN when decapsulating the packet, so it is not known to which MN the packet should be delivered. End up.

  In addition, when transmitting a packet from the MN, it is impossible to determine which MN the packet sent via the MAG has come from, and therefore cannot be decompressed by the LMA.

  In addition, when compression is performed by MAG, since the MAG to which the MN is moved does not have a state after the handover, the state compression must be performed again, and the effect of header compression is diminished. . That is, it is difficult to perform header compression efficiently in either method.

  Further, even if the technique of Patent Document 1 is to be used, the source MAG of the MN cannot be used because it does not know the address of the destination MAG.

  Furthermore, when fast handover is performed, the packet order may be nested. In ROHC, synchronization loss occurs due to the nesting relationship of packets, and the header compression efficiency is reduced.

  In addition, when the communication partner is a Mobile IP terminal, signaling for Mobile IP occurs, or compression efficiency decreases due to the presence of an option header.

  The present invention has been made to solve the above-described problems, and its object is to enable the MN to communicate with the Mobile IP terminal without reducing the compression efficiency in the network-based IP mobility protocol. Even when the MN moves, the MN or MAG becomes a compressor / decompressor, and the communication system, the control device, and the network-based IP mobility protocol that can save the narrowest band, the last one-hop band, It is to provide a router and its communication method.

In view of such a situation, the communication system using the network-based IP mobility protocol according to the first invention uses the network-based IP mobility protocol, and data is transmitted from routers belonging to the same link by addresses uniquely assigned to mobile terminals. Is a communication system that switches communication under the control of a control device when the mobile terminal moves to another network.
The router in the destination network of the mobile terminal receives a notification including the identifier or IP address of the mobile terminal from the mobile terminal, and sends the identifier or IP address of the mobile terminal and the identifier of the router to the control device Alternatively, the control device transmits a notification including an IP address, and the control device moves the mobile terminal to perform relay using the Mobile IP protocol from the source router to the destination router. Binding cache transfer instruction notification for instructing transfer of binding cache, which is communication information regarding the terminal, header compression information transfer instruction notification for instructing transfer of header compression information, and buffer transfer instruction for instructing transfer of data addressed to the mobile terminal The notification is synthesized and transmitted.

  In the communication system using the network-based IP mobility protocol according to the second invention, the control device instructs the movement source router to cancel the transfer setting between the control device and the movement source router. A cancellation instruction notification is transmitted, and the binding / cache transfer instruction notification, the header compression information transfer instruction notification, and the buffer transfer instruction notification are combined with the transfer setting cancellation instruction notification.

Further, a communication system using the network-based IP mobility protocol according to the third invention uses the network-based IP mobility protocol to transmit / receive data from routers belonging to the same link using addresses uniquely assigned to the mobile terminal. A communication system for performing communication and switching the communication by control of a control device when the mobile terminal moves to another network,
The router in the destination network of the mobile terminal receives a notification including the identifier or IP address of the mobile terminal from the mobile terminal, and sends the identifier or IP address of the mobile terminal and the identifier of the router to the control device Alternatively, the control device transmits a notification including an IP address, and the control device transmits a notification including the IP address of the source router to the destination router of the mobile terminal. Send a notification containing the identifier or IP address of the mobile terminal and the IP address of the router to the original router;
The source router transmits to the destination router a binding cache, header compression information, and data addressed to the mobile terminal, which are communication information related to the mobile terminal for relaying using the Mobile IP protocol. It is characterized by that.

  In the communication system using the network-based IP mobility protocol according to the fourth invention, the router buffers the sequence number included in the header of the received data, and transfers the data to the mobile terminal in the sequence number order. It is characterized by that.

According to a fifth aspect of the present invention, there is provided a control device that uses a network-based IP mobility protocol, and in which a mobile terminal performs communication by transmitting and receiving data from routers belonging to the same link using a uniquely assigned address. A control device that performs control to switch communication when a terminal moves to another network,
Communication means for receiving a notification including the identifier or IP address of the mobile terminal and the identifier or IP address of the router from the router in the network to which the mobile terminal is moved, and the communication relating to the router and the mobile terminal performing relay Storage means for storing information, and referring to the storage means for communication information of the mobile terminal from the identifier of the mobile terminal included in the notification from the router, information on the router of the destination and data transfer between the routers A binding cache transfer instruction notification for updating the information and instructing the transfer of the binding cache, which is communication information related to the mobile terminal, to be relayed by the mobile IP protocol from the source router to the destination router; Header compressed information transfer instruction that instructs the transfer of header compressed information And a control means for generating a buffer transfer instruction notice for instructing transfer of data addressed to the mobile terminal, and the communication means sends the binding cache transfer instruction notice, the header compression to the source router. An information transfer instruction notification and the buffer transfer instruction notification are transmitted.

  In the control device according to a sixth aspect of the invention, the control means sends a transfer setting release instruction notification for instructing the movement source router to release the transfer setting between the control device and the movement source router via the communication means. The binding setting transfer instruction notification, the header compression information transfer instruction notification, and the buffer transfer instruction notification are combined with the transfer setting release instruction notification.

A router according to a seventh aspect of the invention is a router that uses a network-based IP mobility protocol and performs data transmission / reception with a mobile terminal belonging to the same link that performs communication using a uniquely assigned address under the control of a control device. And
A binding cache that is communication information related to the mobile terminal for relaying using the Mobile IP protocol; a storage unit that stores header compression information when data is transmitted to the mobile terminal; and the binding cache A binding cache transfer instruction notification including an identifier or IP address of the mobile terminal for instructing transfer of the header compression information and data addressed to the mobile terminal, and an identifier or IP address of the destination router, and a header compression information transfer instruction notification And a communication means for receiving a buffer transfer instruction notification, and a control means for transferring the binding cache, the header compression information and the buffer data to the destination router of the mobile terminal by the transfer instruction notification, With the mobile terminal, A data header compression / decompression process is performed, and a proxy function of the mobile terminal is executed when data is transmitted / received using the Mobile IP protocol.

A router according to an eighth invention is a router that uses a network-based IP mobility protocol and transmits / receives data to / from a mobile terminal belonging to the same link that performs communication using a uniquely assigned address under the control of a control device. And
A binding cache that is communication information related to the mobile terminal for relaying using Mobile IP protocol, storage means for storing header compression information when data is transmitted to the mobile terminal, and the router to which the mobile terminal is moved Communication means for receiving a notification including the identifier or IP address of the mobile terminal and the IP address of the router, and the movement of the binding cache, header compression information and buffer to the destination router by the notification. Control means for transferring data addressed to the terminal, and performs compression / decompression processing of data headers with the mobile terminal, and when performing transmission / reception of data using the Mobile IP protocol, A proxy function is executed.

According to a ninth aspect of the present invention, in the router according to the ninth aspect , after the control means transfers the data received from the source router of the mobile terminal to the mobile terminal, the data received from the control device is transferred to the mobile terminal. It is characterized by doing.

In the router according to the tenth invention, the control means buffers the sequence number included in the header of the data received from the control device or the source router of the mobile terminal, and sends the sequence to the mobile terminal in the sequence number order. The data is transferred.

A communication method according to an eleventh invention uses a network-based IP mobility protocol to cause a mobile terminal to transmit and receive data from a router belonging to the same link using a uniquely assigned address. When moving to a network, a communication method for causing a control device to perform control for switching communication of the mobile terminal,
Detecting the movement of the mobile terminal to the same link to the router in the destination network of the mobile terminal by notification from the mobile terminal; and notifying the control apparatus of the movement of the mobile terminal. Let it run
The control device sends a binding cache transfer instruction notification for instructing transfer of a binding cache, which is communication information related to the mobile terminal for relaying using the Mobile IP protocol, and header compression information to the source router. A step of combining and transmitting a header compression information transfer instruction notification to be instructed and a buffer transfer instruction notification to instruct transfer of data addressed to the mobile terminal is executed.

The communication method according to the twelfth invention uses a network-based IP mobility protocol to cause a mobile terminal to transmit and receive data from a router belonging to the same link using a uniquely assigned address. When moving to a network, a communication method for causing a control device to perform control for switching communication of the mobile terminal,
Detecting the movement of the mobile terminal to the same link to the router in the destination network of the mobile terminal by notification from the mobile terminal; and notifying the control apparatus of the movement of the mobile terminal. Let it run
Causing the control device to execute a step of sending a notification including the IP address of the source router to the destination router;
Causing the destination router to send a notification including the identifier or IP address of the mobile terminal and the IP address of the router to the source router;
The moving source router is caused to execute a step of transmitting a binding cache, header compression information, and data addressed to the mobile terminal to the moving destination router.

  According to the present invention, in the network-based IP mobility protocol, the router (MAG) provides the Mobile IP proxy function, and when the mobile terminal (MN) is handed over, the control device (LMA) By sending the information of the destination router to the destination router, the source router sends the compression information (ROHC context), the MIP BC and the tunnel request to the destination router, and the state of the ROHC and the MIP Handover is possible while maintaining the state.

  In addition, the control device transmits the information of the source router to the destination router, so that the destination router can notify the source router of its own identifier and address. Can send a notification including compression information, MIP BC and tunnel request to the destination router.

  This tunnel also enables fast handover support at the same time. After the offer to create this tunnel, ROHC context, and MIP BC are combined and transmitted, an increase in messages is prevented, and after the buffer is transferred from the source router to the destination router By starting packet transfer from the control device to the destination router, packet nesting can be prevented.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing a schematic configuration of a network in the present embodiment.
FIG. 2 is a block diagram showing the configuration of the MAG in this embodiment.
FIG. 3 is a block diagram showing the configuration of the LMA in this embodiment.

  As shown in FIG. 1, initially, NetLMM-MNa1 is under MAGa2. In addition, it is assumed that NetLMM-MNa1 is communicating with MIP-MN4 via Internet / WAN / CoreNetwork3. In addition to NetLMM-MNa1, there is also NetLMM-MNb5 under MAGa2.

  A description will be given of an example in which NetLMM-MNa1 moves from MAGa2 to MAGb6 under the movement. Here, it is assumed that NetLMM-MNa1 is managed by LMA7 and MIP-MN4 is managed by HA8. The MIP-MN 4 is located on the external link, that is, the link of the Router 9.

  The MAG in FIG. 2 and the LMA in FIG. 3 will be described below.

  As shown in FIG. 2, the MAGs 2 and 6 perform a tunnel processing unit 11 that performs packet encapsulation and decapsulation, a Mobile IP proxy processing unit 12 that performs control related to Mobile IP, and compression or decompression of a header by ROHC. A header compression / decompression processing unit 13, a storage unit 14 including a database unit and a temporary storage unit that can be temporarily stored, a tunnel processing unit 11, and network-based IP mobility protocol message exchange (protocol-like) Network-based IP mobility protocol processing unit 15 that performs generation and control of the tunnel processing unit 11 / header compression / decompression unit 13, storage / deletion of data in the storage unit 14, and the like.

  The MAG communication means typically corresponds to a device processing unit in an OS (Operating System) associated with an actual communication interface. The MAG of this embodiment has two such communication means, one for the NetLMM domain 16 and the other for the wireless device 17.

  The wireless device communication unit 17 has a function of identifying the MN from the MAC address or the like, and can notify the MN-ID to the tunnel processing unit 11 or the network-based IP mobility protocol processing unit 15. Can be notified to the tunnel processing unit 11 and the network-based IP mobility protocol processing unit 15, or a pseudo device is created for each MN, so that the MN is assigned to the tunnel processing unit 11 and the network-based IP mobility protocol processing unit 15. It is possible to pass information to identify. When the MN is specified from the MAC address, the MN-ID and the MAC address are stored in association with the storage unit 14.

  On the other hand, the Mobile IP proxy processing unit 12 / tunnel processing unit 11 / header compression / decompression processing unit 13 is a pseudo device processing unit that receives the same treatment on the OS as described above.

  As shown in FIG. 3, the LMA 7 also includes a tunnel processing unit 18, a storage unit 19, and a network-based IP mobility protocol processing unit 20.

  The communication means of the LMA 7 typically corresponds to a device processing unit in an OS associated with an actual communication interface (for example, an Ethernet (registered trademark) card). The LMA of this embodiment has two such communication means, one for WAN (Wide Area Network) (WAN may be Internet / CoreNetwork, etc.) and the other is for NetLMM domain 22. The NetLMM domain 23 is, for example, a RAN (Radio Access Network) in a mobile phone.

  On the other hand, the tunnel processing unit 18 is a pseudo device processing unit that receives the same handling on the OS as the above device processing unit.

  First, a description will be given from the start of communication when NetLMM-MNa1 is under the control of MAGa2.

  FIG. 4 is a sequence diagram showing a procedure for performing the proxy function processing of the CN in the initial Mobile IP in the present embodiment.

  When communication is started, communication is started via HA8 from either NetLMM-MNa1 or MIP-MN4.

  Thereafter, the MIP-MN 4 performs RR for route optimization. The destination of this RR is NetLMM-MNa-IP and reaches MAGa2 via the LMA7-MAGa2 tunnel.

The MAGa2 storage unit 14 holds a database for network-based IP mobility protocol as shown in FIG.
The Mobile IP proxy processing unit 12 makes the following determination with reference to this database.

  FIG. 6 is an MIP proxy function provision determination flow according to this embodiment.

  The Mobile IP proxy processing unit 12 of the MAGa2 determines whether to provide MIP proxy processing along this flow.

Mobile IP proxy processing is roughly divided into three functions.
A function of proxying the mobile IP CN, a function of transferring a packet with an option header received from the MIP-MN 4 as a normal IP packet, and a normal IP packet received from the NetLMM-MN and addressed to the MIP-MN Is transmitted as a Mobile IP packet with an option header.

  First, when a packet arrives at the Mobile IP proxy processing unit 12 of the MAGs 2 and 6, the Mobile IP proxy processing unit 12 determines whether or not it is destined for a terminal managed by itself in S201.

  Here, if “Yes”, the Mobile IP proxy processing unit 12 determines whether or not the packet is a signaling packet related to MIP in S202.

  Here, if “Yes”, the Mobile IP proxy processing unit 12 performs MIP proxy function processing (signaling proxy function processing) in S203.

  If “No” in S201, the Mobile IP proxy processing unit 12 determines in S204 whether the packet is from a terminal managed by itself.

  Here, if “Yes”, the Mobile IP proxy processing unit 12 determines whether or not the storage unit 14 has a BC related to the communication partner terminal in S205.

  Here, if “Yes”, Mobile IP proxy processing unit 12 performs MIP proxy function processing (MIP packetization processing) in S206.

  If “No” in S202, the Mobile IP proxy processing unit 12 determines whether or not the packet is a packet with an MIP option header in S207.

  Here, if “Yes”, Mobile IP proxy processing unit 12 performs MIP proxy function processing (normal IP packetization processing) in S208.

  If “No” in S204, S205, or S207, Mobile IP proxy processing unit 12 performs normal IP routing processing in S209, S210, or S211.

  First, MAGa2 receives HoTI in S101 and S102 and CoTI in S103 from communication means (NetLMM domain) 16 via LMA7.

  First, the Mobile IP proxy processing unit 12 of MAGa refers to the database of FIG. 5 stored in the storage unit, and the destination address of these packets is NetLMM-MNa-IP and is a node managed by itself. Recognize that it is addressed.

  Since HoTI and CoTI are MIP signaling packets, the Mobile IP proxy processing unit 12 of MAGa2 provides the MIP proxy function (signaling proxy function) in S203. As a result, the Mobile IP proxy processor 12 of MAGa2 generates HoT and CoT packets for HoTI and CoTI with the source address as NetLMM-MNa-IP, HoT in S104 and S105, and CoT in S106 as communication means ( (NetLMM domain) 16 transmits to MIP-MN 4 via LMA 7.

  The MIP-MN 4 that has received the HoT and the CoT generates a BU in S107 and transmits the BU to the NetLMM-MNa-IP.

  As with RR, the destination of the BU is NetLMM-MNa-IP and reaches MAGa2 via the LMA7-MAGa2 tunnel, and MAGa2 is received from the communication means (NetLMM domain) 16.

  The MAIP Mobile IP proxy processing unit 12 recognizes from FIG. 5 that it is addressed to the node managed by the MAGa. Since BU is a MIP signaling packet, the MIP proxy function (signaling proxy function) of S203 is provided.

  Here, since BU is received, a BC as shown in FIG. 7A is generated and stored in the storage unit in association with NetLMM-MNa in the data of FIG.

  Similarly, in association with NetLMM-MNa1, the storage unit 14 stores the ROHC context for compression as shown in FIGS. 7B and 7C, as shown in FIGS. 7D and 7E. Such a decompression ROHC context is held. Strictly speaking, the ROHC context is not held at the start of communication, but is generated and updated as communication continues. The ROHC context stores values for various fields other than those shown in the figure, but FIGS. 7B to 7E are simplified and only a part of them is shown.

  Thereafter, if necessary, the Mobile IP proxy processing unit 12 of the MAGa2 transmits the BA to the MIP-MN 4 from the communication means (NetLMM domain) 16 via the LMA 7 in S108.

  After S109, route optimization is performed, and the packet of MIP-MN4 does not pass through HA8 but reaches MAGa2 via LMA7.

  Next, processing when the route optimization packet arrives from MIP-MN4 to NetLMM-MNa1 will be described.

FIG. 8 shows an example of a packet format in this embodiment.
The packet from the MIP-MN 4 is, for example, as shown in FIG. 8A before arriving at the LMA 7. Originally, there are various other fields in the IP / UDP / RTP header, but here they are simplified and omitted.

  The LMA 7 that has received the packet from the communication means (for WAN) 21 transfers this packet to the tunnel processing unit 18, and the tunnel processing unit 18 encapsulates the packet as shown in FIG. 8B.

  Thereafter, the network-based IP mobility protocol processing unit 20 of the LMA 7 transfers a packet as shown in FIG. 8B to the MAGa 2 via the communication means (NetLMM domain) 22.

  In MAGa2, first, the packet is transferred to the tunnel processing unit 11 via the communication means (NetLMM domain) 16.

  The tunnel processing unit 11 decapsulates the packet as shown in FIG. 8B and restores it as shown in FIG.

  Next, the tunnel processing unit 11 transfers a packet as shown in FIG. 8A to the Mobile IP proxy processing unit 12, and the Mobile IP proxy processing unit 12 provides the MIP proxy function according to the flow of FIG. Judge.

  The Mobile IP proxy processor 12 recognizes that the destination address is NetLMM-MNa-IP by referring to the data in FIG. 5 in the storage unit 14, and determines that it is addressed to the terminal managed by itself in the determination of S201. . Next, in the determination of S202, it is determined that this packet is not MIP signaling. Furthermore, since the destination option header is attached in the determination in S207, the Mobile IP proxy processing unit 12 determines the BC for NetLMM-MNa1 in the storage unit 14 in order to determine whether this packet is a MIP packet. refer. As a result, it is determined that BC exists and is a MIP packet, and the Mobile IP proxy processing unit 12 provides the MIP proxy function (normal IP packetization processing) in S208, and the packet is as shown in FIG. Normally, it is converted into IP packets.

  Thereafter, the Mobile IP proxy processing unit 12 outputs the packet to the header compression / decompression processing unit 13, and the header compression / decompression processing unit 13 performs compression processing on the header. From the packet as shown in FIG. 8C and the compression context as shown in FIG. 7B, the CID is found to be 4, and from the sequence number as shown in FIG. The sequence number (W-LSB) is calculated, the ROHC header is generated, and the packet is as shown in FIG. 8D. The network-based IP mobility protocol processing unit 15 communicates with the NetLMM-MNa1 as a communication means (wireless) 17. Is sent to NetLMM-MNa1.

  Next, processing of packets from NetLMM-MNa1 to MIP-MN4 will be described.

  A packet from NetLMM-MNa1 arrives at MAGa2 in the form as shown in FIG. The packet is transferred to the header compression / decompression processing unit 13 via the communication means (wireless) 17. Here, the communication means (wireless) 17 is determined from the NetLMM-MNa1 by the bearer information such as the MAC address, and the ROHC expansion context of the NetLMM-MNa1 {FIG. 7 (d), FIG. 7 (e)} , Header expansion processing is performed. As a result, it is assumed that it has been expanded as shown in FIG. For example, it is determined as the third line in FIG. 7D, and the sequence number is calculated from FIG. Next, the header compression / decompression processing unit 13 outputs this packet to the Mobile IP proxy processing unit 12.

  The Mobile IP proxy processing unit 12 refers to FIG. 5 of the storage unit 14 and determines whether to provide the MIP proxy function according to the flow of FIG. The Mobile IP proxy processing unit 12 does not address this packet to the terminal managed by itself in the determination of S201, but from the terminal managed by itself in the determination of S204. Refer to the storage unit 14 in the determination of S205. Then, since it is recognized that the BC related to the partner as shown in FIG. 7A is held, it is determined that the MIP proxy function (MIP packetization process) of S206 is provided. As a result, the packet of FIG. 9B has the destination address addressed to MIP-MN-CoA, the routing option header type 2 is inserted, and the MIP packet as shown in FIG. Forward.

  The tunnel processing unit 11 determines the LMA 7 from the source address with reference to FIG. 5 of the storage unit 14, and performs packet encapsulation.

  As a result, the packet is encapsulated as shown in FIG. 9D, and the network-based IP mobility protocol processing unit 15 is transferred to the LMA 7 via the communication means (NetLMM domain) 16.

  The LMA 7 receives the packet via the communication means (NetLMM domain) 22 and transfers the packet to the tunnel processing unit 18.

  The tunnel processing unit 18 deletes the outer header and transfers it to the MIP-MN 4 via the communication means (WAN) 21 as shown in FIG. 9C.

Next, processing when a handover is performed will be described.
10, 11 and 12 are sequence diagrams at the time of handover in the present embodiment. First, the handover procedure in FIG. 10 will be described.

  NetLMM-MNa1 is handed over from MAGa2 to MAGb6.

  In S301, NetLMM-MNa1 disconnects from MAGa2 and starts to connect to MAGb6.

  Since the connection with NetLMM-MNa1 is disconnected, MAGa2 starts buffering packets addressed to NetLMM-MNa1 in S302.

  In S303, the NetLMM-MNa1 transmits a message including the NetLMM-MNa-ID that is its own identifier and the LMA-ID that is the identifier of the LMA7 that manages itself to the MAGb6 in order to connect. This message may be RS, NS, NA, DHCP request, or the like.

  When the MAGb 6 receives this message via the communication means (wireless) 17, the MAGb 6 outputs the message to the network-based IP mobility protocol processing unit 15, and the network-based IP mobility protocol processing unit 15 receives the NetLMM-MNa-ID, A location registration message including the ID MAGb-ID is generated and transmitted to the LMA 7 via the communication means (NetLMM domain) 16.

  At this time, the network-based IP mobility protocol processing unit 15 of the MAGb 6 generates data related to NetLMM-MNa1 as shown in FIG. At this time, only limited information such as NetLMM-MNa-ID and LMA7 is included.

  The LMA 7 that has received the location registration from the communication means (NetLMM domain) 22 transfers the message to the network-based IP mobility protocol processing unit 20, and the network-based IP mobility protocol processing unit 20 stores the NetLMM-MN-ID as a key. The database of the unit 19 is searched, and NetLMM-MNa1 detects that it is currently under MAGa2. As a result, the network-based IP mobility protocol processing unit 20 determines that it is a handover, and performs location deregistration via the communication means (NetLMM domain) 22 with respect to the migration source MAG 2 in S305. Send. At this time, the network-based IP mobility protocol processing unit 20 also instructs to transfer the buffer, BC, and ROHC context to the MAGb 6. For this reason, this location deregistration includes NetLMM-MNa-ID and MAGb-ID. At this time, the communication means (NetLMM domain) 22 deletes the LMA-MAGa tunnel in the tunnel processing unit 18. Thereafter, the LMA 7 buffers packets addressed to NetLMM-MNa-IP.

  In MAGa 2 that has received the location deregistration via the communication means (NetLMM domain) 16, the message is transferred to the network-based IP mobility protocol processing unit 15, and the network-based IP mobility protocol processing unit 15 The LMA7-MAGa2 tunnel is deleted, and a tunnel generation request is transmitted to the MAGb 6 via the communication means (NetLMM domain) 16 in S306. This tunnel generation request is transmitted including ROHC context information as shown in FIGS. 7B to 7E and BC as shown in FIG.

  In MAGb 6 that has received the tunnel generation request from the communication means (NetLMM domain) 16, the message is transferred to the network-based IP mobility protocol processing unit 15, and the network-based IP mobility protocol processing unit 15 stores the received BC and ROHC context. The MAGa 2 -MAGb 6 tunnel is generated in the tunnel processing unit 11. The MAGa2-MAG6 tunnel in MAGb6 is a one-way tunnel from MAGa2 to MAGb6 and is a tunnel that performs decapsulation processing. When these are completed, in S307, the network-based IP mobility protocol processing unit 15 of the MAGb 6 transmits a tunnel generation request Ack to the MAGa 2 via the communication means (NetLMM domain) 16.

  In MAGa2 that has received the tunnel generation request Ack via the communication means (NetLMM domain) 16, the message is transferred to the network-based IP mobility protocol processing unit 15, and the network-based IP mobility protocol processing unit 15 transfers the buffer in S308. The packet is transferred to the MAGb 6 via the communication means (NetLMM domain) 16. This transfer packet is realized by encapsulating MAGa-IP as an outer source address and MAGb-IP as an outer destination address, as shown in FIG. 14 (a) or 14 (b).

  When the transfer of the buffer is completed, the network-based IP mobility protocol processing unit 15 of MAGa2 transmits a location deregistration Ack to the LMA 7 via the communication means (NetLMM domain) 16 in S309. Further, the network-based IP mobility protocol processing unit 15 transmits a tunnel deletion request to the MAGb 6 in S310.

  In MAGb6, the transfer packet is received from MAGa2. The packet is transferred as shown in FIG. 14 (a) or FIG. 14 (b). In MAGb6, when these packets are received from the communication means (NetLMM domain) 16, since they are tunnel packets, they are transferred to the tunnel processing unit 11.

The tunnel processing unit 11 deletes the outer header as shown in FIG. 14C in the case of FIG. 14A and as shown in FIG. 14D in the case of FIG. 14B. When the outer header is deleted, the tunnel processing unit 11 buffers the packet (I).
Thereafter, the MAGb 6 that has received the tunnel deletion request from the MAGa 2 via the communication means (NetLMM domain) 16 deletes the MAGa2-MAGb 6 tunnel from the tunnel processing unit 11, and transmits a tunnel deletion request Ack to the MAGa 2 in S 311. In some cases, this tunnel deletion request Ack may not be transmitted.

  The LMA 7 that has received the location deregistration Ack via the communication means (NetLMM domain) 22 transfers the message to the network-based IP mobility protocol processing unit 20, and the network-based IP mobility protocol processing unit 20 generates a routing setup. . This routing setup includes NetLMM-MNa-ID, MAGb-ID, LMA-ID, NetLMM-MNa-IP, and the like. In step S312, this routing setup is transmitted to the MAGb 6 via the communication means (NetLMM domain) 22.

  At this time, the LMA 7 generates an LMA 7-MAGb 6 tunnel in the tunnel processing unit 18. This tunnel performs an encapsulation process for a packet delivered to NetLMM-MNa1 via MAGb6 and a decapsulation process for a capsule packet delivered from NetLMM-MNa1 via MAGb6.

  The MAGb 6 that has received the routing setup via the communication means (NetLMM domain) 16 transfers the message to the network-based IP mobility protocol processing unit 15. 11 to generate. This tunnel performs decapsulation processing for packets delivered to NetLMM-MNa1 via MAGb6 and encapsulation processing for packets delivered from NetLMM-MNa1 via MAGb6.

  In S313, the routing setup Ack is transmitted to the LMA 7 via the communication means (NetLMM domain 16). At this time, the network-based IP mobility protocol processing unit 15 of the MAGb 6 overwrites FIG. Rewriting is performed as shown in FIG.

  The LMA 7 that has received the routing setup Ack via the communication means (NetLMM domain) 22 transfers the message to the network-based IP mobility protocol processing unit 20, and the network-based IP mobility protocol processing unit 20 performs location registration Ack in S314. Is transmitted to the MAGb 6 via the communication means (NetLMM domain) 22. This location registration Ack contains the prefix information of NetLMM-MNa1.

  Thereafter, the network-based IP mobility processing unit 20 of the LMA 7 starts to transfer a packet routed to the MAGb 6 in the buffer or to the LMA 7 to the MAGb 6.

  The MAGb 6 that has received the location registration Ack via the communication means (NetLMM domain) 16 transfers the message to the network-based IP mobility protocol processing unit 15. In S 315, the network-based IP mobility protocol processing unit 15 performs the address configuration. The message is generated and transmitted to NetLMM-MNa1 via the communication means (wireless) 17. The address configuration message may be RA, DHCP-Advertise, NS, NA, or the like. In the present embodiment, it is assumed that DHCP-Advertise is used as a stateful address configuration, and there is no subsequent signaling. In the case of stateless configuration in RA, DAD is essential.

  Thereafter, the MAGb 6 can transfer the packet to the NetLMM-MNa1, and sequentially transfers the packet transferred from the MAGa2 to the NetLMM-MNa1 in the order of the sequence numbers included in the UDP header or the RTP header. Also, the packet from NetLMM-MNa1 is transferred to LMA7.

  Next, transfer to NetLMM-MNa1 will be described.

  In MAGb6, packets from MAGa2 and packets from LMA7 are buffered. After arrival of these packets, the tunnel processing unit 11 performs only packet decapsulation tunnel processing and is buffered. As a result, the packet is buffered in the format of FIGS. 14 (c) and 14 (d).

  These buffer packets are transferred to the Mobile IP proxy processing unit 12, and it is determined whether or not the Mobile IP proxy processing is necessary according to the flow of FIG. The Mobile IP proxy processing unit 12 refers to the data as shown in FIG. 13C in the storage unit 14 for the packet as shown in FIG. 14C, so that the packet managed by itself is determined in S201. However, since it is not a signaling packet in the determination in S202 and no option header is attached in the determination in S207, it is determined as a normal IP transfer process in S209 and is transferred to the header compression / decompression processing unit 13.

  If the packet is as shown in FIG. 14D, the Mobile IP proxy processing unit 12 refers to the data as shown in FIG. 13C in the storage unit 14 to determine its own in the determination of S201. It is addressed to the packet to be managed, and it is further determined in step S202 that the packet is not MIP signaling. Next, since the destination option header is attached, the BC for NetLMM-MNa1 in the storage unit 14 is referred to in order to determine whether or not this packet is a MIP packet in the determination in S207. As a result, the BC transferred from MAGa2 is present and is determined to be a MIP packet, and the MIP proxy function provision (normal IP packetization processing) of S208 is performed.

The Mobile IP proxy processing unit 12 converts the packet as shown in FIG. 14D into a normal IP packet as shown in FIG. 14C by normal IP packetization processing, and transfers the packet to the header compression / decompression processing unit 13.
The packet from the LMA 7 is omitted because it does not replace the process in the MAGa 2 described above.

  Next, the header compression / decompression processing unit 13 rearranges the packets transferred from the Mobile IP proxy processing unit 12 in order according to the sequence numbers of the UDP header and RTP header, and then performs the compression / decompression processing of the header. . Since the ROHC context transferred from MAGa2 exists in the header compression / decompression process, the header is compressed along this ROHC context and transmitted to NetLMM-MNa1 via communication means (wireless) 17.

  In the present invention, buffering or the like is performed. In (I), for example, the buffering is performed after the tunneling process. However, the buffering may be performed without performing the tunneling process, or the Mobile IP proxy process is performed. You may buffer it later. Finally, when transferring to NetLMM-MNa1, it is only necessary to process so that packets are not nested (the order is not changed).

  It should be noted that if the header compression process is performed before buffering, the order may be changed. This is because the sequence number after compressing the header is about 4 bits. Therefore, when the packet is buffered after compressing the header, it may be buffered together with the sequence number. What is necessary is just to buffer so that it may not be nested when transmitting to NetLMM-MNa1 finally.

From here, based on FIG.11 and FIG.12, the derivation | leading-out form of the hand-over sequence in this embodiment is demonstrated.
In FIG. 11 and FIG. 12, handover is performed by the Proxy Mobile IP method. As shown in FIG. 1, it is assumed that the AAA server 31 is connected via the Internet / WAN / CoreNetwork 3.
First, the sequence of FIG. 11 will be described.

  In S401, NetLMM-MNa1 disconnects from MAGa2.

  Since the connection with NetLMM-MNa1 is disconnected, MAGa2 starts buffering packets addressed to NetLMM-MNa1 in S402.

  In S403, NetLMM-MNa1 notifies MAGb6 of authentication, which is a connection request. This notification includes NetLMM-MNa-ID, which is an identifier of NetLMM-MNa1.

  The MAGb 6 that has received the authentication notification from the NetLMM-MNa 1 transmits a notification including the NetLMM-MNa-ID as authentication to the AAA server 31 in S404.

  In S <b> 405, the MAGb 6 receives a policy profile notification from the AAA server 31. This policy profile includes address information (network prefix, configuration method, etc.) of NetLMM-MNa1.

  In S406, MAGb 6 creates an RA for NetLMM-MNa from the policy profile, and transmits the RA to NetLMM-MNa.

  When MAGb 6 transmits RA to NetLMM-MNa, it transmits Proxy Binding Update to LMA 7 in S407. This Proxy Binding Update includes the IP address or prefix of NetLMM-MNa, and also includes the IP address of MAGb6.

  In step S408, the LMA returns Proxy Binding Update Ack, which is an Ack for confirmation, to MAGb6. At this time, transmission is performed including the IP address of MAGa2, which is MAG, to which NetLMM-MNa previously belonged. Note that when this Proxy Binding Update Ack is returned, the LMA7-MAGb6 tunnel is completed in the tunnel processing unit 18 of the LMA7.

  As a result, the LMA 7 starts transferring the packet addressed to the NetLMM-MNa1 to the MAGb 6 in S409.

  Upon receiving Proxy Binding Update Ack, MAGb 6 creates a Proxy FBU from the MAGa2 address included in Proxy Binding Update Ack, and transmits it to MAGa2 in S410. This Proxy FBU includes the IP address or address information of NetLMM-MNa1 and the IP address of MAGb6.

  MAGa2 which received Proxy FBU creates Proxy FBAck which is Ack for confirmation, and transmits it in S411. This Proxy FBAck includes BC information and ROHC context. During transmission / reception of this Proxy FBAck, a MAGa2-MAGb6 tunnel is created in the MAGa2 tunnel processing unit 11.

  As a result of the creation of the MAGa2-MAGb6 tunnel, the buffer held in MAGa2 is transferred to MAGb6 in S412. As for the transfer method, the method described above (using an option header or the like) is used.

  The MAGa 2 that has received the Proxy FBAck does not need a tunnel with the LMA 7 related to the NetLMM-MNa 1, and therefore, in S 413, transmits a Proxy Binding Update (Deregistration) to delete the tunnel. Note that this step can be omitted if timer management is performed.

  As a result, MAGb6 can be transferred to NetLMM-MNa1 in S414 without packet loss.

  Next, the derivation format of the handover sequence in this embodiment of FIG. 12 will be described.

  In S501, NetLMM-MNa1 disconnects from MAGa2. In this example, it is assumed that NetLMM-MNa1 spontaneously disconnects communication with MAGa2.

  In S502, since MAGa2 cannot deliver the packet to NetLMM-MNa1, it starts buffering.

  In S503, NetLMM-MNa1 notifies MAGb6 of authentication, which is a connection request. This notification includes NetLMM-MNa-ID, which is the identifier of NetLMM-MNa1.

  The MAGb 6 that has received the authentication notification from the NetLMM-MNa1 transmits a notification including the NetLMM-MNa-ID as authentication to the AAA server 31 in S504.

  In step S <b> 505, the MAGb 6 receives a policy profile notification from the AAA server 31. This policy profile includes address information (network prefix, configuration method, etc.) of NetLMM-MNa1.

  In step S506, MAGb 6 creates an RA for NetLMM-MNa1 from the policy profile, and transmits the RA to NetLMM-MNa1.

When MAGb 6 transmits the RA to NetLMM-MNa 1, MAGb 6 transmits Proxy Binding Update to LMA 7 in S 507. This Proxy Binding Update includes the IP address or prefix of NetLMM-MNa1 and the IP address of MAGb6.

In step S508, the LMA 7 returns a Proxy Binding Update Ack, which is an Ack for confirmation, to the MAGb 6. At this time, transmission is performed including the IP address of MAGa2, which is MAG, to which NetLMM-MNa1 previously belonged.
Note that when this Proxy Binding Update Ack is returned, the LMA7-MAGb6 tunnel is completed in the tunnel processing unit 18 of the LMA7. As a result, in S510, the packet can be transferred from the LMA 7 to the MAGb 6.

  The LMA 7 that has returned the Proxy Binding Update Ack instructs the MAGa 2 to transfer the context in S509. This message includes the address of MAGb6.

  The MAGa 2 that has received the context transfer instruction transmits a message Proxy HI (Handover Initiate) for creating a tunnel with the MAGb 6 in S511. This Proxy HI includes a ROHC context and BC.

  In step S512, the MAGb 6 transmits Proxy HAck, which is an Ack for confirming the Proxy HI, to the MAGa2. As a result, a MAGa2-MAGb6 tunnel is created.

  Since the tunnel has been established, MAGa2 transfers the buffer to MAGb6 in S513. The transfer method described above is used.

  In step S514, the MAGb 6 rearranges the packets transferred from the MAGa2 or LMA 7 in order and transfers them to the NetLMM-MNa1.

In the above, based on FIG.11 and FIG.12, the derivative form of the sequence of a handover was mentioned.
These common points are that, by controlling the LMA 7, the MAGa 2 address is the MAGb 6 address, or the MAGb 6 address is the MAGa 2 address, the buffer is transferred between the MAGa 2 and the MAGb 6 by the tunnel formation, and the ROHC text transfer And BC can be transferred.

  Note that the communication system, control device, router and communication method using the network-based IP mobility protocol of the present invention are not limited to the above-described illustrated examples, and may be variously within the scope of the present invention. Of course, changes can be made.

It is the figure shown about the schematic structure of the network in this invention. It is the block diagram which showed the structure of MAG in this invention. It is the block diagram which showed the structure of LMA in this invention. In the present invention, MAG is a sequence diagram showing a procedure for performing an initial Mobile IP proxy function process. It is an example of the database for network-based IP mobility protocols. It is a MIP proxy function provision determination flow in the present invention. (A) is an example of BC, and (b) to (e) are examples of a ROHC context. It is an example of the format of the packet in this invention. It is an example of the format of the packet in this invention. It is a sequence diagram at the time of handover in the present invention. It is a sequence diagram at the time of handover in the present invention. It is a sequence diagram at the time of handover in the present invention. It is an example of the data regarding NetLMM-MNa stored in the memory | storage part of MAG. It is an example of the format of the packet in this invention. It is the sequence diagram which showed the procedure of the process of the conventional fast handover method. It is the sequence diagram which showed the procedure of the process of the hand-over method in the conventional network base IP mobility protocol. It is the sequence diagram which showed the procedure of the process of the hand-over by the proxy MobileIP system of the conventional network base mobility protocol.

Explanation of symbols

1, 5 NetLMM-MN
2, 6 MAG
3 Internet / WAN / CoreNetwork
4 MIP-MN
7 LMA
8 HA
9 Router
11, 18 Tunnel processing unit 12 Mobile IP processing unit 13 Header compression / decompression processing unit 14, 19 Storage unit 15, 20 Network-based IP mobility protocol processing unit 16, 17, 21, 22 Communication means 23 NetLMM domain 31 AAA server

Claims (12)

Using a network-based IP mobility protocol, a mobile terminal performs communication by transmitting and receiving data from a router belonging to the same link using a uniquely assigned address. When the mobile terminal moves to another network, control is performed. A communication system for switching communication by controlling a device,
The router in the destination network of the mobile terminal receives a notification including the identifier or IP address of the mobile terminal from the mobile terminal, and sends the identifier or IP address of the mobile terminal and the identifier of the router to the control device Or send a notification containing the IP address,
The control device sends a binding cache that is communication information about the mobile terminal for relaying from the source router to the destination router by using the Mobile IP protocol to the source router of the mobile terminal. A combined cache / cache transfer instruction notification for instructing transfer, a header compression information transfer instruction notification for instructing transfer of header compression information, and a buffer transfer instruction notification for instructing transfer of data addressed to the mobile terminal are combined and transmitted. A communication system using a network-based IP mobility protocol.   The control device transmits a transfer setting release instruction notification for instructing transfer cancellation between the control device and the source router to the source router, and the binding cache is transmitted to the transfer setting release instruction notification. The communication system using the network-based IP mobility protocol according to claim 1, wherein the transfer instruction notification, the header compressed information transfer instruction notification, and the buffer transfer instruction notification are combined. Using a network-based IP mobility protocol, a mobile terminal performs communication by transmitting and receiving data from a router belonging to the same link using a uniquely assigned address. When the mobile terminal moves to another network, control is performed. A communication system for switching communication by controlling a device,
The router in the destination network of the mobile terminal receives a notification including the identifier or IP address of the mobile terminal from the mobile terminal, and sends the identifier or IP address of the mobile terminal and the identifier of the router to the control device Or send a notification containing the IP address,
The control device sends a notification including the identifier or IP address of the source router to the destination router of the mobile terminal,
The destination router transmits a notification including the identifier or IP address of the mobile terminal and the IP address of the router to the source router;
The source router transmits to the destination router a binding cache, header compression information, and data addressed to the mobile terminal, which are communication information related to the mobile terminal for relaying using the Mobile IP protocol. A communication system using a network-based IP mobility protocol.   The said router buffers according to the sequence number contained in the header of the received data, and transfers the said data to the said mobile terminal in the said sequence number order, It is any one of Claims 1-3 characterized by the above-mentioned. A communication system using the network-based IP mobility protocol. When a mobile terminal moves to another network in a system that uses a network-based IP mobility protocol and communicates by transmitting and receiving data from a router belonging to the same link using an address uniquely assigned to the mobile terminal. A control device that performs control for switching communication,
Communication means for receiving a notification including the identifier or IP address of the mobile terminal and the identifier or IP address of the router from the router in the network to which the mobile terminal is moved;
Storage means for storing communication information related to the router and the mobile terminal for relaying;
Refer to the storage means for communication information of the mobile terminal from the identifier of the mobile terminal included in the notification from the router, update the information on the destination router and data transfer between the routers,
Binding cache transfer instruction notification for instructing transfer of binding cache, which is communication information related to the mobile terminal for relaying by Mobile IP protocol from the source router to the destination router, transfer of header compression information Control means for generating a header compression information transfer instruction notification for instructing and a buffer transfer instruction notification for instructing transfer of data addressed to the mobile terminal,
The communication device transmits the binding / cache transfer instruction notification, the header compression information transfer instruction notification, and the buffer transfer instruction notification to the source router.   The control means transmits, to the transfer source router, a transfer setting release instruction notification for instructing release of the transfer setting between the control device and the transfer source router via the communication means. 6. The control apparatus according to claim 5, wherein the binding cache transfer instruction notification, the header compressed information transfer instruction notification, and the buffer transfer instruction notification are combined. A router that transmits and receives data to and from a mobile terminal that belongs to the same link that communicates with a uniquely assigned address under the control of a control device using a network-based IP mobility protocol,
A storage unit that stores a binding cache that is communication information related to the mobile terminal for relaying using the Mobile IP protocol, and header compression information when data is transmitted to the mobile terminal;
Binding cache transfer including the binding cache, the header compression information and the identifier or IP address of the mobile terminal that instructs to transfer the data addressed to the mobile terminal and the identifier or IP address of the destination router from the control device A communication means for receiving an instruction notification, a header compression information transfer instruction notification, and a buffer transfer instruction notification;
A control means for transferring the binding cache, the header compression information and the buffer data to the destination router of the mobile terminal by the transfer instruction notification;
A router for performing compression / decompression processing of a data header with the mobile terminal and executing a proxy function of the mobile terminal when transmitting / receiving data using the Mobile IP protocol. A router that transmits and receives data to and from a mobile terminal that belongs to the same link that communicates with a uniquely assigned address under the control of a control device using a network-based IP mobility protocol,
A storage unit that stores a binding cache that is communication information related to the mobile terminal for relaying using the Mobile IP protocol, and header compression information when data is transmitted to the mobile terminal;
Communication means for receiving a notification including the identifier or IP address of the mobile terminal and the IP address of the router from the router to which the mobile terminal has moved;
A control means for transferring the data addressed to the mobile terminal in the binding cache, header compression information and buffer to the destination router by the notification;
A router for performing compression / decompression processing of a data header with the mobile terminal and executing a proxy function of the mobile terminal when transmitting / receiving data using the Mobile IP protocol. Said control means, the data received from the router of the moving source of the mobile terminal after transferring to the mobile terminal, the controller data received from and wherein the forwarding to the mobile terminal according to claim 7 or The router according to claim 8 . The control means buffers in the order of sequence numbers included in a header of data received from the control device or a source router of the mobile terminal, and transfers the data to the mobile terminals in the order of the sequence numbers. The router according to claim 9 . Using the network-based IP mobility protocol, the mobile terminal is made to transmit and receive data from a router belonging to the same link using a uniquely assigned address. When the mobile terminal moves to another network, the control device A communication method for performing control for switching communication of the mobile terminal,
In the router in the network to which the mobile terminal is moving,
Detecting the movement of the mobile terminal to the same link by notification from the mobile terminal;
Notifying the control device of the movement of the mobile terminal,
In the control device,
Binding cache transfer instruction notification for instructing transfer of a binding cache, which is communication information related to the mobile terminal for relaying using the Mobile IP protocol, header compression information for instructing transfer of header compression information to the source router A communication method, comprising: combining and transmitting a transfer instruction notification and a buffer transfer instruction notification for instructing transfer of data addressed to the mobile terminal. Using the network-based IP mobility protocol, the mobile terminal is made to transmit and receive data from a router belonging to the same link using a uniquely assigned address. When the mobile terminal moves to another network, the control device A communication method for performing control for switching communication of the mobile terminal,
In the router in the network to which the mobile terminal is moving,
Detecting the movement of the mobile terminal to the same link by notification from the mobile terminal;
Notifying the control device of the movement of the mobile terminal,
In the control device,
Sending a notification containing the IP address of the source router to the destination router;
To the destination router,
Transmitting the notification including the identifier or IP address of the mobile terminal and the IP address of the router to the source router;
To the source router,
A communication method, comprising causing a step of transmitting a binding cache, header compression information, and data addressed to the mobile terminal to the destination router.

Images