System and method for providing mobility with a split home agent architecture
13 claims: 6 independent, 7 dependent
- 1ワイド・エリア・ネットワークにおいてネットワーク要素によって実装される方法であって、前記ネットワーク要素はモバイル・インターネット・プロトコル・バージョン6(MIPv6)を使用して対応ノード(CN)と通信するモバイル・ノード(MN)に対するホーム・エージェント(HA)として機能し、 事前に定義されたポリシーに基づき前記HAよりも良好なサービスを用いて前記MNにホーム・エージェント・サービスを提供するために、前記HAによって前記ネットワーク内の仮想ホーム・エージェント(VHA)を選択するステップと、 前記CNからホームkeygenトークンを取得するために前記CNにホスト・テスト開始メッセージを送信するステップであって、前記ホームkeygenトークンは前記 CN を認証するためのものである、送信するステップと、 前記ホームkeygenトークンを含むホスト・テスト・メッセージを前記CNから受信するステップと、 前記選択されたVHAにフロー・スイッチ要求(FSR)メッセージを送信するステップであって、前記FSRメッセージは前記ホームkeygenトークンと前記CNのアドレスと前記MNの気付けアドレスとを含み、前記FSRメッセージは、前記MNに関するデータ・トラフィックを前記HAの代わりに前記選択されたVHAに送信するように前記CNに指示する気付けテスト開始メッセージ及び結合更新メッセージを、前記選択されたVHAに生成及び送信させるためのものであり、前記FSRメッセージは前記MNへのトンネルを前記選択されたVHAに確立させるためのものである、送信するステップと、 前記選択されたVHAが前記CNからの前記データ・トラフィックを正常にリダイレクトし、前記データ・トラフィックを前記MNの前記気付けアドレスにトンネリングしている旨を示すフロー・スイッチ肯定応答(FSA)メッセージを前記VHAから受信するステップと、を含み、 これによって前記MNは、前記VHAを介して前記CNと通信している場合、前記HAを介している場合よりも良好なサービス品質を受け取る、方法。
- 2前記VHAを介して前記CNにデータ・パケットをトンネリングするように前記MNに指示するために、前記選択されたVHAのアドレスを前記MNに通知するステップをさらに含む、請求項1に記載の方法。
- 3前記事前に定義されたポリシーが、前記MNの前記気付けアドレスと前記仮想ホーム・エージェントを含む複数の仮想ホーム・エージェントの各アドレスとの比較、位相情報、サービス品質要件、帯域幅メトリクス、及び待ち時間メトリクスのうちの1つ又は複数である、請求項1に記載の方法。
- 4ワイド・エリア・ネットワークにおいてネットワーク要素によって実装される方法であって、前記ネットワーク要素はモバイル・インターネット・プロトコル・バージョン6(MIPv6)を使用して対応ノード(CN)と通信するモバイル・ノード(MN)に対する仮想ホーム・エージェント(VHA)として機能し、 前記VHAでホーム・エージェントからフロー・スイッチ要求(FSR)メッセージを受信するステップであって、前記FSRメッセージは前記MNの気付けアドレスと前記CNのアドレスと前記CNのホームkeygenトークンとを含み、前記ホームkeygenトークンは 前記CN を認証するためのものであり、前記FSRメッセージは前記VHAにホーム・エージェント・サービスを割り当てるものである、受信するステップと、 気付けkeygenトークンを取得するために前記CNに気付けテスト開始メッセージを送信するステップであって、前記気付けkeygenトークンは前記CNを認証するためのものである、送信するステップと、 前記CNから前記気付けkeygenトークンと共に気付けテスト・メッセージを受信するステップと、 前記VHAを認証するため、及び前記VHAにデータ・パケットを送信するように前記CNに指示するために、前記ホームkeygenトークン及び気付けkeygenトークンを使用して前記CNに結合更新メッセージを送信するステップと、 前記結合更新メッセージに応答して前記CNから結合確認応答メッセージを受信するステップであって、前記結合確認応答は前記MN宛のデータ・パケットに関する前記CNによる前記VHAへのリダイレクトを示す、受信するステップと、 前記結合確認応答メッセージの受信に応答して前記VHAと前記MNとの間にトンネルを確立するステップと、 前記結合確認応答メッセージに応答して前記HAにフロー・スイッチ確認応答(FSA)メッセージを送信するステップであって、前記FSAメッセージは前記MN宛のデータ・パケットに関する前記CNによる前記VHAへのリダイレクトを示す、送信するステップと、 前記CNから受信したデータ・パケットを前記トンネルを介して前記MNの前記気付けアドレスにトンネリングするステップと、を含み、 これによって前記MNは、前記VHAを介して前記CNと通信している場合、前記HAを介している場合よりも良好なサービス品質を受け取る、方法。
- 5前記トンネリングするステップがインターネット・プロトコル・トンネリングにおけるインターネット・プロトコルである、請求項4に記載の方法。
- 6前記トンネルを介して前記MNからデータ・パケットを受信するステップと、 前記データ・パケットを前記CNに転送するステップと、をさらに含む、請求項4に記載の方法。
- 7ホーム・エージェント(HA)として機能するように構成されたネットワーク要素であって、前記ネットワーク要素は、モバイル・ノード(MN)、対応ノード(CN)、及び複数の仮想ホーム・エージェント(VHA)とワイド・エリア・ネットワークを介して通信しており、 前記ネットワークを介してデータ・パケットを 送信 するように構成された出口モジュールと、 前記ネットワークを介して前記データ・パケットを 受信 するように構成された入口モジュールと、 前記入口モジュール及び前記出口モジュールと通信可能に結合され、ネットワーク移動性管理モジュール、結合管理モジュール、及び仮想ホーム・エージェント 管理 モジュールを実行するように構成された、ネットワーク・プロセッサと、 前記MNと前記CNとの間の通信セッションを管理するように構成された前記ネットワーク移動性管理モジュールと、 前記ネットワーク移動性管理モジュールと通信可能に結合され、結合エントリのセットを含む結合テーブルを維持するように構成された、結合管理モジュールであって、各結合エントリは前記MNに関する気付けアドレス、前記HAのアドレス、前記CNのアドレス、及び前記VHAのアドレスを含み、前記結合管理モジュールは前記結合エントリのセットを作成及び更新するように構成された、前記結合管理モジュールと、 前記MNにホーム・エージェント・サービスを提供するために前記複数のVHAからVHAを選択するように構成された前記仮想ホーム・エージェント管理モジュールであって、前記選択は事前に定義されたポリシーに基づき、前記仮想ホーム・エージェント管理モジュールは、前記CNからホームkeygenトークンを取得し、前記MNに関する気付けアドレス、前記CNのアドレス、及び前記ホームkeygenトークンを含むフロー・スイッチ要求(FSR)メッセージを前記選択されたVHAに送信するように構成され、前記FSRメッセージは、前記選択されたVHAに前記CNとHAとの間のデータ・トラフィックを前記選択されたVHAへとリダイレクトさせるため、前記選択されたVHAに前記MNへのトンネルを確立させるため、及び前記選択されたVHAに前記CNから前記トンネルを介して前記MNへとトラフィックを転送させるためのものであり、前記仮想ホーム・エージェント管理モジュールは前記選択されたVHAからフロー・スイッチ確認応答(FSA)メッセージを受信するように構成された、仮想ホーム・エージェント管理モジュールと、を備え、 これによって前記MNは、前記VHAを介して前記CNと通信している場合、前記HAを介している場合よりも良好なサービス品質を受け取る、ネットワーク要素。
- 8前記ネットワーク内の前記複数のVHAの位置及びトポロジのうちの1つ又は複数に関する情報を記憶するように構成された、仮想ホーム・エージェント・データベースをさらに備える、請求項7に記載のネットワーク要素。
- 9前記事前に定義されたポリシーが、前記MNの前記気付けアドレスと前記複数のVHAの各アドレスとの比較、位相情報、サービス品質要件、帯域幅及び待ち時間メトリクスのうちの1つ又は複数を含む、請求項7に記載のネットワーク要素。
- 10前記仮想ホーム・エージェント管理モジュールが、前記モバイル・ノードに前記選択されたVHAを通知するように構成された、請求項7に記載のネットワーク要素。
- 11仮想ホーム・エージェント(VHA)として機能するように構成されたネットワーク要素であって、前記ネットワーク要素は、モバイル・ノード(MN)、対応ノード(CN)、及びホーム・エージェント(HA)とワイド・エリア・ネットワークを介して通信しており、 前記ネットワークを介してデータ・パケットを 送信 するように構成された出口モジュールと、 前記ネットワークを介して前記データ・パケットを 受信 するように構成された入口モジュールと、 前記入口モジュール及び前記出口モジュールと通信可能に結合され、ネットワーク移動性管理モジュール、結合管理モジュール、及び仮想ホーム・エージェント・モジュールを実行するように構成された、ネットワーク・プロセッサと、 前記MNと前記CNとの間の通信セッションを管理するように構成された前記ネットワーク移動性管理モジュールと、 前記ネットワーク移動性管理モジュールと通信可能に結合され、結合エントリのセットを含む結合テーブルを維持するように構成された、前記結合管理モジュールであって、各結合エントリは前記MNに関する気付けアドレス、前記HAのアドレス、前記CNのアドレス、及び前記VHAのアドレスを含み、前記結合管理モジュールは前記結合エントリのセットを作成及び更新するように構成された、前記結合管理モジュールと、 前記MNにホーム・エージェント・サービスを提供するように構成された、前記仮想ホーム・エージェント・モジュールであって、前記仮想ホーム・エージェント・モジュールは前記HAから受信したフロー・スイッチ要求(FSR)メッセージからホームkeygenトークンを取得するように構成され、前記FSRメッセージはMNに関する前記気付けアドレス、前記CNに関する前記アドレス、及び前記ホームkeygenトークンを含み、前記仮想ホーム・エージェント・モジュールは気付けテスト開始メッセージを前記CNに送信し、気付けkeygenトークンと共に気付けテスト・メッセージを受信し、前記VHAを認証するために前記ホームkeygenトークン及び気付けkeygenトークンを使用して前記CNに結合更新メッセージを送信し、前記MNへのトンネルを確立し、前記HAにフロー・スイッチ確認応答(FSA)メッセージを送信し、前記トンネルを介して前記CNから前記MNにデータ・トラフィックを転送するように構成された、仮想ホーム・エージェント・モジュールと、を備え、 これによって前記MNは、前記VHAを介して前記CNと通信している場合、前記HAを介している場合よりも良好なサービス品質を受け取る、ネットワーク要素。
- 12前記仮想ホーム・エージェント・モジュール及びネットワーク移動性管理モジュールが、インターネット・プロトコル・トンネリングにおけるインターネット・プロトコルを使用して前記CNから前記MNへデータをトンネリングするように構成された、請求項 11 に記載のネットワーク要素。
- 13前記仮想ホーム・エージェント・モジュール及びネットワーク移動性管理モジュールが、前記MNからデータ・パケットを受信し、前記データ・パケットを前記CNに転送するように構成された、請求項 11 に記載のネットワーク要素。
Independent claims13
41 paragraphs, as filed
0001This application was cross-referenced to a co-pending application named "System and method for mobility with a split home agent architecture using MPTCP" filed on the same day as the present application and owned by the owner of the present application, July 21, 2010. It claims priority from US Provisional Patent Application No. 61/366314 of the date application. Cross-reference applications are incorporated herein by reference.
0002Mobile Internet Protocol Version 6 (MIPv6) allows mobile devices to maintain continuous connectivity with other devices that support Mobile Internet Protocol Version 6. MIPv6 supports two separate communication modes: two-way tunneling (BT) mode and route optimization (RO) mode. Mobile IPv6 uses a home agent node to manage the transfer of data traffic to a mobile node if it is not in the home network.
0003When a mobile node moves to an external network, it registers with that network and reports the registration to the home agent node. The home agent node receives data traffic from the corresponding node and uses the IP tunneling IP in BT mode to forward the traffic to the mobile node in the external network. In RO mode, the home agent facilitates communication between the corresponding node and the mobile node, resulting in the corresponding node being notified of the new location and address of the mobile node in the external network and the corresponding node. Allows direct communication with mobile nodes in the external network without interrupting the Transmission Control Protocol (TCP) connection.
<p num="0004"> In mobile IPv6, mobile nodes have global and continuous reachability to mobile nodes regardless of their current topological position (ie, within their home network or connected to an external network). Has a static home agent that acts as an anchor point for assurance. However, if the home agent fails or the home agent becomes overloaded, mobile IPv6 will not solve it. BT mode is secure and requires a large amount of signaling messages to establish and maintain a tunnel between the mobile node and the home agent. BT mode is also under the control of the mobile node. In contrast, RO mode requires the direct involvement of both mobile and corresponding nodes and requires more resources in the overhead mobility signal to establish and maintain RO mode compared to BT mode. I need to spend.</p>
<p num="0005"> A method implemented by a network element in a wide area network, where the network element is for a mobile node (MN) that communicates with a corresponding node (CN) using Mobile Internet Protocol version 6 (MIPv6). Acting as a home agent (HA), the method is to provide home agent services to MN with better services than HA based on predefined policies, virtual homes in the network by HA. -The step of selecting an agent (VHA) and the step of sending a host test start message to the CN to obtain the home keygen token from the CN, and the home keygen token is for authenticating HA. The steps to send, the step to receive a host test message from the CN containing the home keygen token, and the step to send a flow switch request (FSR) message to the selected VHA, where the FSR message is the home keygen token. The FSR message, which includes the address of the CN and the care-of address of the MN, tells the CN to send data traffic about the MN to the selected VHA instead of the HA and a care-of test start message and The steps to send and the selected VHA are for the selected VHA to generate and send the combined update message, and the FSR message is for the selected VHA to establish a tunnel to the MN. Includes the step of successfully redirecting data traffic from the CN and receiving a Flow Switch Positive Response (FSA) message from the VHA indicating that it is tunneling the data traffic to the MN's care address. By MN, when communicating with CN via VHA, it receives better quality of service than when communicating via HA.</p><p num="0006"> A method implemented by a network element in a wide area network, where the network element is for a mobile node (MN) that communicates with a corresponding node (CN) using Mobile Internet Protocol version 6 (MIPv6). Acting as a virtual home agent (VHA), the method is to receive a flow switch request (FSR) message from the home agent on the VHA, where the FSR message is the MN care address, the CN address, and the CN. Including the home keygen token, the home keygen token is for authenticating the home agent (HA), and the FSR message is for assigning the home agent service to the VHA, the step to receive and the care keygen token. The step of sending a notice test start message to the CN to get the notice keygen token is for authenticating the CN, the step of sending and receiving the notice test message with the care keygen token from the CN. And the step of sending a join update message to the CN using the home keygen token and the care keygen token to authenticate the VHA and to instruct the CN to send data packets to the VHA. The step of receiving a join acknowledgment message from the CN in response to the join update message, the join acknowledgment is the receiving step and the join acknowledgment message indicating the CN's redirect to VHA for the data packet destined for the MN. The FSA message is the step of establishing a tunnel between the VHA and the MN in response to the reception of, and the step of sending a flow switch acknowledgment (FSA) message to the HA in response to the join acknowledgment message. A step to send, indicating the CN's redirect to VHA for data packets destined for the MN, and a ton of data packets received from the CN to the MN's care address via a tunnel.It includes a step of nailing, which allows the MN to receive better quality of service when communicating with the CN via VHA than via HA.</p><p num="0007"> A network element configured to act as a home agent (HA), which is a mobile node (MN), a corresponding node (CN), and multiple virtual home agents (VHA) and wide. Communicating over an area network, network elements are configured to transport data packets over the network with egress modules that are configured to receive data packets over the network. A network processor that is communicatively coupled with an ingress module and an ingress and exit module and is configured to run a network mobility management module, a join management module, and a virtual home agent module. And a network mobility management module configured to manage communication sessions between MN and CN, and a network mobility management module that is communicably joined to maintain a join table containing a set of join entries. A join management module configured in, where each join entry contains a care address for the MN, an HA address, a CN address, and a VHA address, so that the join management module creates and updates a set of join entries. A pre-defined combination management module and a virtual home agent management module configured to select a VHA from multiple VHAs to provide home agent services to the MN. Based on the policy, the virtual home agent management module gets the home keygen token from the CN and selects a Flow Switch Request (FSR) message containing the care address, CN address, and home keygen token for the MN. Configured to send to the VHA, FSR messages establish a tunnel to the MN on the selected VHA to redirect data traffic between the CN and HA to the selected VHA. To let, And to allow the selected VHA to forward traffic from the CN to the MN through the tunnel, and the Virtual Home Agent Management Module receives a Flow Switch Acknowledgment (FSA) message from the selected VHA. With a virtual home agent management module, configured to This allows the MN to receive better quality of service when communicating with the CN via VHA than over HA.</p><p num="0008"> A network element configured to act as a virtual home agent (VHA), which is a mobile node (MN), a corresponding node (CN), and a home agent (HA) and a wide area. Communicating over the network, the network elements include an exit module configured to receive data packets over the network and an ingress module configured to transport data packets over the network. Between the MN and CN, a network processor communicatively coupled with the inlet and exit modules and configured to run network mobility management modules, coupling management modules, and virtual home agent modules. A network mobility management module that is configured to manage communication sessions and a join management module that is communicable with the network mobility management module and is configured to maintain a join table containing a set of join entries. Each join entry contains a care address for the MN, an HA address, a CN address, and a VHA address, and the join management module is configured to create and update a set of join entries. And a virtual home agent module configured to provide home agent services to MN, which is a home keygen token from a flow switch request (FSR) message received from HA. The FSR message contains a care address for MN, an address for CN, and a home keygen token, and the virtual home agent module sends a care test start message to CN and care test with the care keygen token. · Receive the message and send a join update message to the CN using the home keygen token and the care keygen token to authenticate the VHA and tunnel to the MN.It features a virtual home agent module that is configured to establish and send flow switch acknowledgment (FSA) messages to HA and forward data traffic from CN to MN over the tunnel. By MN, when communicating with CN via VHA, it receives better quality of service than when communicating via HA.</p><p num="0009"> The present invention is shown as an example, not as a limitation, in the illustrations of the accompanying drawings where the same references show similar elements. It should be noted that different references to "some" or "one" embodiments in the present disclosure do not necessarily refer to the same embodiment, and such references mean at least one. Further, where a particular function, structure, or feature is described in connection with an embodiment, such function, structure, or feature, whether explicitly described or not, is incorporated into another embodiment. It is presented that the related actions are within the knowledge of those skilled in the art.</p>
0010<figref num="1">It is a figure which shows one Embodiment of the network which implements a split home agent architecture.</figref><figref num="2">FIG. 5 is a flowchart showing an embodiment of a process executed by a home agent to configure a virtual home agent.</figref><figref num="3">FIG. 5 is a flowchart showing an embodiment of a process executed by a virtual home agent to configure a virtual home agent.</figref><figref num="4">It is a figure which shows one Embodiment of the split home agent architecture messaging.</figref><figref num="5">It is a figure which shows one Embodiment of a home agent.</figref><figref num="6">It is a figure which shows one Embodiment of a virtual home agent.</figref>
0011In the following description, a number of specific details are shown. However, it will be appreciated that embodiments of the present invention are feasible without these particular details. In other instances, well-known circuits, structures, and techniques are not shown in detail so as not to obscure the understanding of the description. However, those skilled in the art will appreciate that the present invention can be practiced without these particular details. Those skilled in the art will be able to implement appropriate functionality without undue experimentation using this included description.
0012The operation of the flowchart will be described with reference to the exemplary embodiments shown in FIGS. 1 and 4 to 6. However, the operation of the flowchart can be performed by embodiments of the present invention other than those discussed with reference to FIGS. 1 and 4-6, and the embodiments discussed with reference to FIGS. 1 and 4-6 , It should be understood that it is possible to perform actions different from those discussed with reference to the flowcharts of FIGS. 2 and 3.
0013The techniques shown in the figure can be implemented using code and data stored and executed on one or more electronic devices (eg, end stations, network elements, etc.). Such electronic devices include non-transient machine-readable or computer-readable storage media (eg, magnetic disks, optical disks, random access memory, read-only memory, flash memory devices, and phase change memory). Store and communicate codes and data (internally and / or with other electronic devices over a network) using non-transient machine-readable or computer-readable media. In addition, these electronic devices are typically one or more storage devices, user input / output devices (eg, keyboards, touch screens, and / or displays), and one or more other configurations, such as network connections. Contains a set of one or more processors combined into an element. The coupling of a set of processors and other components is usually via one or more buses and bridges (also called bus controllers). Storage devices represent one or more non-transient machine-readable or computer-readable storage media, and non-transient machine-readable or computer-readable communication media. Thus, a storage device for a given electronic device typically stores code and / or data for execution on one or more sets of processors for that electronic device. Of course, one or more parts of certain embodiments of the invention can be implemented using different combinations of software, firmware, and / or hardware.
0014As used herein, network elements (eg routers, switches, bridges, etc.) are hardware that interconnects other devices on the network (eg, other network elements, end stations, etc.) in a communicable manner. And one of the networking devices including software. Some network elements provide support for multiple networking capabilities (eg routing, bridging, switching, Layer 2 aggregation, session boundary control, multicasting, and / or subscriber management), and / or multiple application services. A "multi-service network element" that provides support for (eg, data, audio, and video). Subscriber end stations (eg servers, workstations, laptops, palmtops, mobile phones, smartphones, multimedia phones, voice over internet protocol (VOIP) phones, portable media players, GPS units, games · Systems, set-top boxes (STBs, etc.) access content / services provided over the Internet and / or content / services provided over virtual private networks (VPNs) overlaid on the Internet. To do. Content and / or services are typically provided by one or more end stations (eg, server end stations) that belong to a service or content provider or end station participating in a peer-to-peer service and are available on the public web. -Can include pages (free content, storefronts, search services, etc.), corporate networks via VPN, IPTV, etc. Typically, subscriber end stations are coupled to edge network elements (eg, via customer premises equipment that is coupled to an access network (wired or wirelessly)), which (eg to other edge network elements). One or more core networks
0015Embodiments of the present invention provide methods and systems for avoiding the drawbacks of prior art. Disadvantages of prior art include bidirectional tunneling (BT) mode, which is not optimal when the mobile node is away from its home network. For example, if a mobile node is in the United States and communicates with a corresponding node located in the United States, but its home network is in Japan, all traffic between the mobile node and the corresponding node is mobile. -You must go to a Japanese home agent before returning to the node. We are experiencing significant growth in telecommunications landscapes, real-time applications, services, and web-enabled high-definition televisions, and these types of applications are not only growing, but also a major driver of revenue for telecommunications service operators. It is expected to become. Therefore, in an increasingly competitive environment, it is important to ensure high quality of service to our customers. In addition, these particular types of applications can lead to "bottlenecks" in home agents, in which case all clients suffer a loss of quality of service.
0016Embodiments of the present invention overcome these shortcomings of the prior art. Instead of deploying a cluster of home agents within the home network, a split control architecture is used, which allows the central home agent to not deal directly with the mobile node, but by the home agent and from the mobile node. Connect to a new set of lightweight virtual home agents (VHAs) that can provide specific services, such as those requested based on your feedback. In addition, the virtual home agent can be located anywhere and does not need to exchange direct signaling (ie, mobility-related signaling or other signaling) with the mobile node. Instead, virtual home agents aim to provide specific home agent functionality for mobile nodes without knowledge of mobile nodes. The home agent has a secure connection with each virtual home agent and has complete knowledge of the location of each virtual home agent.
0017The architecture and method of the split home agent is suitable for multi-homed mobile nodes. It is expected that Mobile Node will have at least two different interfaces (eg, interface with Wired Terminal Equipment (LTE) and interface with WLAN), in which case both interfaces will have the same operator network (eg, for example). Means connected to AT & T, Verizon, T-Mobile, and similar operators). The architecture based on this split home agent provides better mobility performance than the performance provided by BT mode.
0018Thus, a split home architecture can be described as having one central policy control node that receives input from mobile nodes and makes decisions accordingly. The central control node works to create a kind of "location-based" virtual home agent, but a home agent node connected to a large set of lightweight home agents that have no direct relationship to the mobile node. Is executed by. The mobile node updates its home agent with the new care address (CoA) and lets the home agent determine the correct virtual home agent (if it is available).
0019The main benefit of having a virtual home agent is to optimize data traffic routing, provide better quality of service (QoS), and offload home agent services whenever needed. is there. Such optimization involves implementing an equivalent route optimization mode without the need for the two real endpoints (ie, the mobile node and the corresponding node) to deal with each other with respect to the mobile signaling protocol. The virtual home agent can be placed anywhere and does not cause scalability issues. In addition, the home agent can move sessions from one virtual home agent (VHA) to the other depending on the location of the mobile node, resulting in the mobile node being the closest virtual home. -Can be assigned to agents at all times.
0020On the other hand, MIPv6 RO mode can perform data packet switching on a direct path between a mobile node and a corresponding node. The split home agent architecture is better suited between BT and RO modes, which is more advantageous because it allows the operator to maintain full control of traffic flow while optimizing data packet routing. Implement quickly.
0021FIG. 1 is a diagram showing an embodiment of a network that implements a split home agent architecture. The network includes a mobile node 103, a set of home agents 105 located within the home network 101, a set of external networks 121, 131, 141, and a set of virtual home agents 107A-107E. The home network 101 and the external networks 121, 131, and 141 can be connected by the core network 111. Each of these networks can be a local area network (LAN), a wide area network (WAN), the Internet, or a similar network. Mobile node 103 is mobile between networks 101, 121, 131, and 141 and can maintain connectivity with corresponding nodes over network 111.
0022Mobile node 103, home agent nodes 105, and virtual home agents 107A-107E are laptop computers, routers, switchers, desktop computers, servers, handheld devices, console devices, and similar computing. And can be any type of computing device or networking element, including networking devices. Networks 101, 111, 121, 131, and 141 can include any combination of wired and wireless connections, as well as any number of intermediate computers or networking devices.
0023In one embodiment, the mobile node 103 and the home agent 105 can maintain a connection with a corresponding node (eg, a TCP connection) when the mobile node 103 moves between networks and changes network connections. Implement Mobile Internet Protocol Version 6 (MIPv6) or similar communication protocol. Virtual Home Agents 107A-107E are controlled by Home Agent 105, which selects virtual Home Agents 107A-107E and instructs it to perform home agent functions, thereby making these functions home. Offload from agent 105 to virtual home agents 107A-107E, or work with home agent 105 to share these features with virtual home agents 107A-107E.
0024Using these virtual home agents 107A-107E to provide any subset of the functionality of the home agent 105 improves the quality of service provided to mobile node 103. By using virtual home agents 107A-107E instead of home agent 105, virtual home agents 107A-107E can be significantly closer to mobile node 103. As a result, higher quality of service can be provided to the mobile node 103 if the home agent 105 is not as close to the mobile node and the corresponding node 109 as the virtual home agents 107A-107E. Improved quality of service includes increased bandwidth, lower latency, and mobile nodes 103 and corresponding nodes 109 that use virtual home agents 107A-107E compared to using home agents 105. Similar improvements in communication metrics between can be included.
0025The mobile node 103 connects to the home agent 105 regardless of the current network to which the mobile node 103 is connected in order to keep the home agent 105 up to date at the current location of the mobile node 103. As a result, the home agent 105 can determine which virtual home agents 107A-107E should be used to provide the home agent service to the mobile node 103. At any given point in time, mobile node 103 can connect to multiple virtual home agents 107A-107E in addition to being connected to home agent 105. Each network can include NAT66 to perform network address translation so that data packets destined for mobile node 103 can be properly translated to their local addresses within external networks 121 and 141. Each virtual home agent 107A-107E receives communications and instructions from the home agent 105 and makes a secure connection to the home agent 105 to maintain notification of its status and location to the home agent 105. It is also possible to have.
0026FIG. 2 is a flowchart showing an embodiment of a process performed by a home agent to configure a virtual home agent. In one embodiment, the home agent responds to notifications from mobile nodes that include its location in the external network (eg, join update messages) and home agent functionality (corresponding node-to-mobile node data). You can start the process of assigning responsibility for providing (such as forwarding traffic) to a virtual home agent.
0027A virtual home agent can be used if it is closer than the home agent or if it can provide better quality of service to the mobile node. The home agent node compares the location of the mobile node and other information with the local database of virtual home agent information to provide the best set of virtual home agents to service the mobile node. Can be decided. Virtual home agents can be selected based on a predefined policy that defines the improved quality of service that can be provided to mobile nodes by the available virtual home agents (block 201). Predefined policies include comparing the mobile node's care address with the virtual home agent address, using phase information, quality of service requirements, bandwidth and latency metrics, and the virtual home agent home. It can include similar standards that can be used in determining that it can provide improved quality of service compared to agents. You can choose a single virtual home agent or any number of virtual home agents to provide any combination of home agent services. The virtual home agent can process the flow switch request message, remember the parameters provided in the flow switch request message (for example, in private cache memory), and return the flow switch acknowledgment message. .. The virtual home agent can perform both BT and RO modes of MIPv6, including receiving join update messages, sending join acknowledgment messages, and processing RO mode mobile signaling messages.
0028After the virtual home agent or set of virtual home agents is selected, the home agent sends a host test start (HoTI) message to the corresponding node to obtain the home keygen token (block 203). The host test start message is a message defined in the Mobile Internet Protocol v6. Availability is tested on a particular node, in this case the corresponding node, using the host test start message and the corresponding host test message defined as the response. The response message is received from the corresponding node in the form of a host test message containing the home keygen token (block 205). A home keygen token is a key identifier or similar data that can be used by a corresponding node and a home agent to authenticate the corresponding node. The home agent uses this home keygen token to allow the virtual home agent to set up a connection with the corresponding node and redirect the traffic flow on the corresponding node to the virtual home agent instead of the home agent. It can be served to a virtual home agent, which allows the virtual home agent to serve mobile nodes with improved quality of service compared to home agents.
0029The home keygen token is provided to the virtual home agent via a flow switch request message. The presence of the home keygen token (along with the address of the corresponding node) in the flow switch request message is used with the home keygen token subsequently received in the flow switch request message to obtain the care keygen token. Indicates to the virtual home agent that the test start (CoTI) and awareness test (CoT) messages must be exchanged with the corresponding node. The flow switch request message will be sent to the corresponding node to trigger the virtual home agent and perform the redirect of traffic from the home agent to the virtual home agent. Awareness test start message and subsequent joins. Generate an update message (block 207).
0030After the virtual home agent completes the redirect with a notice test start message and a subsequent join update message, the virtual home agent will send a flow switch acknowledgment message to the home agent. This flow indicates that the home agent has successfully redirected traffic from the corresponding node to the virtual home agent and set up a tunnel to the mobile node through which the corresponding node forwards the traffic. · Receive a switch acknowledgment message from the virtual home agent (block 209).
0031In one embodiment, the home agent can then notify the mobile node of each virtual home agent selected to provide the home agent service to the mobile node (block 211). .. This notification can be in the form of providing the address of the virtual home agent. However, the mobile node still provides the home agent with all updates of its status and location, allowing the home agent to manage the proper use of the virtual home agent. In other embodiments, the use of the virtual home agent can be transparent to the mobile node.
0032FIG. 3 is a flowchart showing an embodiment of a process executed by a virtual home agent. In one embodiment, the process is initiated by the reception of a flow switch request message on the virtual home agent, including the address of the mobile node, the address of the corresponding node, and the home keygen token of the corresponding node (block 301). .. The flow switch request message from the home agent indicates that the virtual home agent has been selected to execute at least one set of home agent services or services for the specified mobile node and corresponding node connection. Is shown. In response to receiving a flow switch request, the virtual home agent records the correlation of mobile node address, corresponding node address, home agent address, home keygen token, and care keygen token in the join entry. You can update the local join table to do so. The virtual home agent then initiates the process of redirecting traffic on the corresponding node by sending a notice test start message to the corresponding node (block 303). The awareness test start message defined by Mobile Internet Protocol version 6 enables the awareness test of the awareness address to be performed.
0033The corresponding node sends an awareness test message with the awareness keygen token in response to receiving the awareness test start message. The virtual home agent receives this awareness test message from the corresponding node along with the awareness keygen token for the corresponding node (block 305). The virtual home agent then uses the home keygen token received from the home agent and the awareness keygen token received from the corresponding node to virtual home from the home agent for data traffic between the corresponding node and the mobile node. · Send a join update message to the corresponding node to perform a redirect to the agent (block 307). The existence of a combination of home keygen token and care keygen token serves to enable verification and authentication on the corresponding node. The corresponding node then responds with a join acknowledgment message received by the virtual home agent (block 309). The virtual home agent then either checks for the join update in its own join table or creates an appropriate join entry in the join table at this point.
0034The virtual home agent then sends a flow switch acknowledgment message to the home agent to establish a tunnel to the mobile node care address (block 313). The tunnel of the mobile node can be an IP tunnel or an IP within a similar tunnel. The mobile node can be unaware that the virtual home agent, not the home agent, is forwarding data traffic or is providing other home agent services.
0035FIG. 4 is a diagram illustrating an embodiment of a split home agent architecture that illustrates the message exchange described above with respect to FIGS. 2 and 3. In this figure, Home Agent (HA) 403 receives Join Update (BU) Message 423 from Mobile Node 401, which is close to Virtual Home Agent 405. The home agent 403 then selects the virtual home agent 405 to service the mobile node (MN) 401 with respect to its connection to the corresponding node 407. This process is initiated by the corresponding node sending a Host Test Start (HoTI) message 409 that responds with a host test (HoT) message 411. These messages verify the reachability of the corresponding node and provide the home agent with the corresponding node's home keygen token.
0036The home agent then generates a flow switch request (FSR) message 413 that contains the home keygen token and sends this message 413 to the virtual home agent 405. Virtual Home Agent 405 then generates Awareness Test Start (CoTI) message 415 on Corresponding Node 407. Corresponding node 407 responds with an awareness test (CoT) message 410 containing an awareness keygen token. The virtual home agent then generates a join update message 417 to redirect traffic from the corresponding node 407 to the virtual home agent 405. The virtual home agent 405 then creates tunnel 421 to mobile node 401. In one embodiment, the virtual home agent 405 employs a BT mode that communicates with the mobile node 401. In addition, the virtual home agent 405 replies to the home agent with a flow switch acknowledgment (FSA) message 423 confirming that the flow switch is affected.
0037FIG. 5 is a diagram illustrating an embodiment of a network element that acts as a home agent node. The network element 500 can include an inlet module 501, an exit module 505, and a network processor 503. Ingress module 501 can handle the processing of data packets received by network elements at the physical and data link levels. Exit module 505 handles processing and data packets transmitted by network elements at the physical and data link levels. Network processor 503 handles the routing, forwarding, and higher level of processing of data traffic. The network processor 503 can execute or include the IPv6 network mobility management module 507, the join table 509, the join management module 513, and the virtual home agent management module 515.
0038The network mobility management module 507 receives data traffic from the mobile node and forwards the data traffic to the corresponding node if no virtual home agent is assigned. The mobility management module implements basic mobile IPv6 features including BT and RO mode support, tunneling, and address translation. The network mobility management module 503 also receives data traffic from the corresponding node and forwards it to the mobile node. Any combination of these features can be outsourced to a virtual home agent.
0039The join management module 513 receives a join update message from the mobile node when the mobile node connects to the external network. Each of the combined update messages contains an IPv6 care address assigned by the external network to which the mobile node is currently connected. In addition, the join management module 513 responds to each of the received join update messages in order for the home NAT node to join the home address of the mobile node with the prefix of the outer NAT node in its outer network. , Configured to send a join request message to the home NAT node. In addition, the join management module 513 receives a join update message or request from the virtual home agent management module 515. Join management module 513 updates and maintains join entry 511 in join table 509. These join entries 511 are the Care Address (COA), Home Agent Address (HOA), Virtual Home Agent Address (VHA), Corresponding Node Address (CN), and Mobile Node and Corresponding Node. Correlate similar data that will be used to forward data traffic between and to track the delegation of home agent services to virtual home agents.
0040The Virtual Home Agent (VHA) Management Module 515 selects the virtual home agent and performs the transfer of the home agent service to the virtual home agent, as described above with respect to FIG. Virtual Home Agent Database 521 or similar storage system or data structure keeps track of properties, topologies, and similar Virtual Home Agent information needed to select and transfer services to available Virtual Home Agents. .. The virtual home agent database can also be used to track the assignment of home agent services to each virtual home agent.
0041FIG. 6 is a diagram showing an embodiment of the virtual home agent. The network element 600 can include an inlet module 601, an exit module 605, and a network processor 603. Ingress module 601 can handle the processing of data packets received by network elements at the physical and data link levels. Exit module 605 handles processing and data packets transmitted by network elements at the physical and data link levels. Network processor 603 handles the routing, forwarding, and higher level of processing of data traffic. Network processor 603 can execute or include IPv6 network mobility management module 607, join table 609, join management module 613, and virtual home agent module 615.
0042The network mobility management module 607 receives data traffic from the mobile node and forwards the data traffic to the corresponding node if no virtual home agent is assigned. The mobility management module implements basic mobile IPv6 features including BT and RO mode support, tunneling, and address translation. The network mobility management module 603 also receives data traffic from the corresponding node and forwards it to the mobile node.
0043The join management module 613 receives a join update message or request from the virtual home agent module 615. The join management module updates and maintains join entry 611 in join table 609. These join entries are the Care Address (COA), Home Agent Address (HOA), Virtual Home Agent Address (VHA), Corresponding Node Address (CN), and between the mobile node and the Corresponding Node. Correlate similar data that will be used to forward data traffic in and to track home agent services that will be performed on each mobile node or home agent node.
0044The virtual home agent (VHA) module 615 receives a request from the home agent to forward the home agent service to the virtual home agent, as described above with respect to FIG. The virtual home agent module 615 processes the flow switch request message from the home agent and redirects data traffic from the corresponding node to the virtual home agent using join update messages and / or CoTI messages. .. The virtual home agent can also run other services entrusted by the home agent.
0045The methods, systems, and devices for making the split home agent architecture executable have been described above. It will be appreciated that the above description is intended to be exemplary and not limiting. Those skilled in the art will appreciate many other embodiments by reading and understanding the above description. Therefore, the scope of the present invention should be determined with reference to the appended claims and the full scope of the equivalents to which such claims are entitled.
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2008547339A | Cites | Japan |
| WO2008132780A1 | Cites | World Intellectual Property Organization (WIPO) |
| US20090016270A1 | Cites | United States of America |
| Siemens,Comments on S3-060257 on "Security aspects for inter-access mobility between non 3GPP and 3GPP access network",3GPP TSG SA WG3 Security - SA3#44 S3-060486,2006年 7月 4日 | Non-patent | – |
| Takahiro Hirofuchi, Hidemoto Nakada, Satoshi Itoh, Satoshi Sekiguchi,Kagemusha: A guest-transparent Mobile IPv6 mechanism for wide-area live VM migration,Network Operations and Management Symposium (NOMS), 2012 IEEE,2012年 4月16日,DOI:10.1109/NOMS.2012.6212069 | Non-patent | – |
21 members in 7 offices
Members21
| Document | Office | Kind | |
|---|---|---|---|
| US2012020284A1 | United States of America | A1 | |
| US2012023211A1 | United States of America | A1 | |
| WO2012010994A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2012080901A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AR082383A1 | Argentina | A1 | |
| CN102986192A | China | A | |
| US8428024B2 | United States of America | B2 | |
| EP2596610A1 | European Patent Office (EPO) | A1 | |
| JP2013532920A | Japan | A | |
| CN103262587A | China | A | |
| US2013223407A1 | United States of America | A1 | |
| EP2652975A1 | European Patent Office (EPO) | A1 | |
| US8699433B2 | United States of America | B2 | |
| US8811329B2 | United States of America | B2 | |
| EP2596610B1 | European Patent Office (EPO) | B1 | |
| EP2652975B1 | European Patent Office (EPO) | B1 | |
| JP5777713B2This record | Japan | B2 | |
| BR112013000432A2 | Brazil | A2 | |
| CN102986192B | China | B | |
| CN103262587B | China | B | |
| BR112013000432B1 | Brazil | B1 |
17 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 5777713
- Application
- 2013520245
Titles2
- Japanese
- 分割ホーム・エージェント構造を用いて移動性を提供するためのシステム及び方法
- English
- Systems and methods for providing mobility using a split home agent structure
Classification
- CPC, 11
- H04W8/12
- H04W8/065
- H04W8/082
- H04W8/26
- H04W28/18
- H04W48/08
- H04W80/06
- H04W88/14
- H04L69/14
- H04W76/22
- H04W76/12
- IPC, 4
- H04W8 04
- H04W8 08
- H04W12 06
- H04W80 04
