Methods and apparatus for extending mobile ip

The present application relates to communication methods, in particular methods and devices for supporting paging and / or end-to-end security associations in communication systems capable of handing off application processing responsibility from end nodes such as mobile nodes to application proxies. Regarding.

Mobile IP (v4 / v6), also known as MIPv4 and MIPv6, allows the mobile node (MN) to register its temporary location, indicated by the awareness address (CoA), with its home agent (HA). MIPv4 is described in Non-Patent Document 1. MIPv6 is described in Non-Patent Document 2. In MIP, HA holds a mapping (also called binding) between a permanent fixed address, also known as the MN's home address (HoA), and a registered CoA, so packets destined for that MN are IP at its current location. It can be redirected using encapsulation techniques (tunneling).

The CoA used by MN can be an address that belongs to a foreign agent (FA) when using MIPv4, and in MIPv4 and MIPv6 it is called a concatenated awareness address (CCoA) that is temporarily assigned to MN itself. It can be an address.

The concepts and solutions described here are applicable to both MIPv4 and MIP unless otherwise noted.

MIPv4 / v6 also has a feature called reverse tunneling. This ensures that all uplink traffic from the MN goes through the HA before reaching its final destination. This traffic is basically reverse tunneled to HA by either the MN itself or the FA to which the MN is connected. If the MN has not registered the CoA / CCoA with the HA, the HA will not accept packets reverse tunneled from the given CoA or CCoA as before.

In Mobile IP, the home subnet is the location of HA and the location of MN in general. When the MN is on its home subnet, it responds to Address Resolution Protocol (ARP) requests for that HoA. When the MN is away from home, the HA will instead use proxy ARP to respond to ARP requests for the MN's HoA, so packets destined for the MN will be routed by the HA to the current CoA. When MN returns home, HA and MN are all to notify that MN is currently at home and the HoA link layer address is now the MN link layer address, not the HA link layer address. Updates the ARP cache of and sends unnecessary ARP signals. If the MN is not home and the HA does not have the current CoA binding to the MN, both the HA and the absent MN will ignore the incoming packet and the incoming packet will be blindly dropped on this subnet. It will be. For AR processing, IETF RFC It is described in Section 4.6 of 3220. In mobility systems such as 3G cellular or 802.11, MN generally does not have a home subnet, especially when dynamic addressing is used, so ARP requests if the current CoA binding maintained by MN is not in HoA. There is no MN that can respond to.

Also, in multiple mobility systems, MN can be absent on the system for a variety of reasons. Whether the MN is powered off, the MN is in an unreachable part of the Internet fabric (private domain), or is in various forms of labor-saving sleep, it is simply unreachable on a particular HoA. You may want to keep it (privacy, vacation, etc.). Therefore, if the MN does not maintain its CoA binding in its absence, incoming packets destined for that HoA will simply be dropped on the local subnet.<nplcit num="1"><text>http://www.ietf.org/rfc/rfc3220.txt</text></nplcit><nplcit num="2"><text>http://www.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-2l.txt</text></nplcit><nplcit num="3"><text>http://www.ietf.org/proceedings/99nov/ID/draft-ietf-mobileip-optim-08.txt</text></nplcit>

<p> The methods and devices of the invention are servers referred to as proxy MN servers for one or more active applications when the MN is unresponsive, absent, or unreachable, for example in sleep mode. Allows you to act as a proxy for MN. Therefore, even in the absence of MN, applications that can time out due to no signal from MN can be maintained. This allows the MN to continue interacting with the application after waking up, for example after releasing sleep mode.</p><p> Describes methods and devices that facilitate mobile node paging in systems where mobile nodes can hand off application processing to application proxies. The paging determination is made based on the processing result of the application corresponding to the processing of the contents of the payloads of a plurality of packets. In some cases, the paging determination is made based on the processing of the payload of a single packet in association with the information received from the mobile node, for example, the intermediate processing result of the application, the state information of the mobile node, and the like. End-to-end transparent to the peer node throughout the communication session with the peer node to facilitate handoff of application processing in a way that is transparent to the peer node involved in the ongoing communication session with the mobile node. Security information may be exchanged between the mobile node and the application proxy node in a way that allows the security association to be maintained.</p><p> Many other features, advantages, and exemplary embodiments are described in detail below.</p>

FIG. 1 shows an exemplary access node 12, such as an access router or base station, implemented in accordance with the present invention. The access node 12 includes antennas 203 and 205 and corresponding receivers and transmitter circuits 202 and 204, respectively. Receiver circuit 202 includes decoder 233 and transmitter circuit 204 includes encoder 235. Circuits 202 and 204 are coupled by bus 230 to the I / O interface 208, the processor (eg CPU) 206, and the memory 210. I / O interface 208 connects access nodes 12, such as base stations, to the Internet. The memory 210 includes a plurality of routines, which, when executed by processor 206, cause the access node 12 to operate in accordance with the present invention. The memory includes a plurality of communication routines 223 used to control the access node 12 to perform various communication operations and implement various communication protocols. The memory 210 further includes an access node control routine 225 for controlling the operation and signals of an access node 12 such as a base station in order to carry out the steps of the method of the present invention. The access node control routine 225 includes a scheduler module 222 for controlling transmission scheduling and / or communication resource allocation. Therefore, module 222 can also function as a scheduler. The memory 210 further includes a mobility agent module 226 for processing and transmitting mobility-related signals that implements the steps of the method of the invention. Therefore, module 226 can also function as a mobile IPv4 foreign agent or mobile IPv6 attendant. The memory 210 further includes information 212 used by the communication routine 223, the control routine 225, and the mobility agent module 226. Information 212 also includes entries 213, 213'for each active end node (EN1, ENn), respectively. These entries include each end no Includes context states 243, 243'in the access node associated with (EN1, ENn). The context state is exchanged between access nodes during an end node handoff and includes information such as end node profiles, security associations, and end node multicast membership. Entries 213, 213'also include states 214, 214' of the MIP visitor list associated with said end node (EN1, ENn) at the access node, respectively. In particular, the information for end node 1 213 includes the context state 243 of end node 1 213 and also includes state 214 of the MIP visitor list as detailed in FIG.

FIG. 2 shows an exemplary end node 14 implemented in accordance with the present invention. The end node 14 may be used by the user as a mobile terminal (MT) or may function as a mobile node proxy server (MNPS) for the mobile terminal (MT). When the end node 14 is connected to the access node 12 via a wireless link, the end node 14 includes receive and transmit antennas 303, 305 coupled to receiver and transmitter circuits 302, 304, respectively. Receiver circuit 302 includes decoder 333 and transmitter circuit 304 includes encoder 335. The receiver and transmission circuits 302 and 304 are connected to the memory 310, the processor 306, and the I / O interface 308 by the bus 330. If the end node 14 is connected to the access node via a fixed link, I / O interface 308 is used. Processor 306 operates the end node 14 according to the method of the present invention under the control of one or more routines stored in memory 310. To control the operation of the end node 14, the memory 310 includes a communication routine 323 and an end node control routine 325. The end node communication routine 323 is used to control the end node 14 to perform various communication operations and execute various communication protocols. The role of the end node control routine 325 is to operate the end node according to the method of the present invention and perform the steps described for the operation and signal of the end node. Memory 310 further includes MNPS control routine 326. The role of the MNPS control routine 326 is to operate the end nodes according to the methods of the invention to perform the steps described for MNPS operation and signals. The memory 310 is a data structure used to carry out the present invention and / or user / device / application / session / resource information 312 that can be accessed and used to carry out the method of the present invention. Also includes. In particular, the user / device / application / session / resource information 312 includes the MIP visitor status information 313 described in detail in FIG. Information 312 also includes MNPS state 314. The MNPS state 314 includes the MNPS address if the end node is MT and the MT home address if the end node 14 is MNPS. The MNPS state information also indicates the corresponding security association to ensure signal transmission between the MT and its MNPS, and whether the MT or MNPS is currently exchanging packets with the home address of the end node 14. And include. Information 312 also includes application state 315. Application state 315 contains the intended behavior of the application software on MT14 and MNPS14, the application state sent from MT14 to MNPS14, which packet flow is destined for MT14, and which flow is sent to MNPS14 on MT14. The described classification information sent to the home agent is described.

FIG. 3 shows an exemplary home mobility agent node 15 implemented in accordance with the present invention. The home mobility agent node 15 includes a bus 430 that connects the I / O interface 408, the processor (eg, CPU) 406, and the memory 410. I / O interface 408 connects the home mobility agent node 15 to the Internet. The memory 410 includes a plurality of routines, which, when executed by processor 406, cause the home mobility agent node 15 to operate in accordance with the present invention. The memory 410 includes a communication routine group 423 for controlling the mobility agent node 15 to perform various communication operations and to execute various communication protocols. The memory 410 also includes a mobility agent control routine 425 for controlling the operation and signals of the mobility agent node 15 to carry out the steps of the method of the invention. Mobility agent node control routine 425 includes scheduler module 422 for controlling transmission scheduling and / or communication resource allocation. Therefore, module 422 can act as a scheduler. The memory 410 also includes a mobility agent module 426 for processing and transmitting mobility-related signals that carry out the steps of the method of the invention. Therefore, module 426 can act as a mobile IP home agent. Memory 410 also includes information 412 used by communication routine 423, control routine 425, and mobility agent module 426. Information 412 includes entries 413, 413'for each active end node (EN1, ENn). In particular, the information on end node 1413 includes visitor list state 414, as detailed in FIG. Information about end node N 413'includes visitor list state 414', which is also detailed in Figure 4.

FIG. 4 is associated with a given mobility agent, such as end node 14, access node (foreign agent) 12, or home mobility agent node (home agent) 15, with list state 313 in FIG. 2 and visitor list state in FIG. An exemplary visitor list state 100 is shown which implements the visitor list states 414, 414', respectively, 214, 214', and FIG. From the perspective of access node 12 and end node 14, respectively in FIGS. 1 and 2, visitor list state 100 can include multiple state entries 110, 120.

The visitor state 100 according to the present invention includes a plurality of entries applicable to at least one MN14 mobility agent. These entries include the MN home address (HoA) 112, the home agent (HA) address 115, the awareness address (CoA) 116, the binding lifetime 113, the MIP signal flag 117, and the MIP security state association 114. It is a state related to. If the mobility agent is a home mobility agent, the visitor list state information 100 further includes the default CoA state information 110. The default CoA status information 110 is an end node 1 such as a mobile node (MN) or mobile terminal (MT) used by the home agent 15 when a valid CoA116 for the home address 112 is not in the visitor list. Includes the default CoA118 of. The default CoA state information 110 also includes the MIP control state 119 used for the signal and transfer operation of the MIP between the end node 14 and the home agent node 15. In addition, if the mobility agent is a home mobility agent, the visitor list status information 100 is provided by the home agent node 15 if the visitor list is maintained by the corresponding MNPS of the end node 1 rather than the end node 1 itself, such as MT. Includes MNPS CoA status information 120 with home address 112 used. MNPS CoA state 120 includes MNPS CoA127, which is used instead of the default CoA118 or CoA116 of end node 1 when MNPS issues a MIP location registration to home agent node 15. State 120 further includes MIP security state 128 to ensure such location registration at the home agent and MIP control state 129 used during the MIP signal and transfer operation between the MNPS 14 and the home agent 15. ..

FIG. 5 shows an exemplary system 500 including a plurality of access nodes 505, 505', 505'' implemented in accordance with the present invention. FIG. 5 also shows communication cells 501, 501'that surround each access node 505, 505', respectively. Communication cells 501, 501'represent the coverage area of the radio technology used by the corresponding access nodes 505, 505', which each have a plurality of end nodes. On the other hand, the access node 505'' uses a fixed link to the end node, so it is part of the network in another way without using a communication cell. Since the same physical and functional elements are shown differently in communication cells 501, 501'and in the network, the following description of each element in cell 501 surrounding access node 505 is given in cells 501, 501', and The same applies to the network part including access node 505''. Access node 505 is a simplified representation of access node 12 shown in FIG. For simplicity, the illustrated access node 505 includes one mobility agent module 507 responsible for signaling that implements the present invention. Figure 5 shows an access node 505 that provides connections to N end nodes 502, 504 (end node (MT) 1, end node (MT) N (X)) via the corresponding access links 506, 508. .. End nodes 502 and 504 are shorthand notations for end node 14 shown in FIG.

The interconnection between access nodes 505, 505', 505'' is made via network links 510, 511, 512 and intermediate network node 520. The home network 530 of FIG. 5 is connected to the rest of the system via link 522 and node 520. The home network 530 further includes a network node 536 connected to link 522 and a mobility agent node 532 connected to node 536 via link 538 and acting as a mobility agent for at least end node N504. The network 540 of FIG. 5 is connected to the rest of the system via link 523 and node 520. The network 540 is a communication that operates as a communication partner terminal in a data session between a network node 546 connected to the link 523 and an end node N504 connected to the node 546 via the link 548 and at least for explaining the method of the present invention. Further includes the partner node (CN) 542. The access node 505 is, for example, an end node (end node (MT) 1) in a communication network 500 that provides wireless communication. It is considered to support mobile terminals (MT) via links (506, 508) with 502, end node (MT) N (X) 504). Similarly, the access node 505'in the communication network 500 providing wireless communication, for example, a link (506', 508' with an end node (end node (MT) 1 502', end node (MT) N 504')). ) Is considered to support MT. On the other hand, the access node 505'' is considered to support a fixed link to the end node which is the MNPS, and the MNPS is considered to further support the end node which is the MT in the communication system 500. The access node 505'' shown in the figure becomes an end node (end node (MNPS) 1 502'', end node (MNPS) N (Y) 504'') via a fixed link (506'', 508''), respectively. It is combined.

6-8 show exemplary embodiments of the various methods of the invention. 6 to 8 are simplified versions of the system of FIG. 5 and include elements necessary to further illustrate the invention. The access nodes 505 and 505'' illustrated in FIG. 6 are mobility agents that provide access to the MT end node X504 and access to the MNPS end node Y504'' that provides functionality to the MT end node X504, respectively. Includes modules 507, 507''. FIG. 6 further shows home mobility agent node 532 serving end node (MT) X504 and CN node 542 during a communication session with said end node (MT) X504. The thin solid arrow in FIG. 6 represents internal data traffic, and the direction of the arrow points to the destination of the data traffic. The thick solid line indicates the encapsulated internal data traffic, and the direction of the arrow points to the destination of the tunnel. The dashed line indicates a signal message for registering the location of the end node with the foreign mobility agent 507 and the home mobility agent 532, and the direction of the arrow points to the destination of the signal. Dashed lines are also used for other signal types related to MIP handoff and control of MNPS functions.

FIG. 6 shows packet forwarding and signaling of a preferred example of the present invention in operation within network 500. Dashed arrows indicate signal messages and solid arrows are packet flows. Thin solid arrows are internal packets and thick arrows are internal packets encapsulated with external headers. In FIG. 6, the end node (MT) X504 first receives the packet from CN542 as packet flow 616 to home mobility agent node 532. When the home mobility agent node 532 tunnels these packets as packet flow 610 to access node 505, foreign agent 507 in access node 505 deencapsulates packet 610 and forwards it as packet 617 to end node (MT) X504. In order for the end node (MT) X504 to call the MNPS function of the present invention, the end node (MT) X504 sends location registration request signals 601 and 602 to the home mobility agent 532 via foreign agent 507 and by messages 603 and 604. Receive the location registration response. Location registration message 601 is the home address of the end node (MT) X504, the address of the mobility agent node 532, the address of the access node 505, and the end node X for the home address of the end node (MT) X504. Includes the CoA field and the requested location registration lifetime. The location registration message is intended to break the binding between the home address and the CoA of the end node (MT) X504 on foreign and home agents 507, 532. To achieve this goal without loss of generality, CoA may be set to be the same as the home address, and / or duration may be set to zero or a very short term value. When the end node (MT) X504 cancels or modifies the dynamic binding between the home address and the dynamic CoA in the home agent 532, the home agent changes the dynamic CoA entry in the binding to the default CoA entry. The default CoA is preset to the home agent by the management process, can be delivered in the MN profile from the policy server, or the default CoA is included in this location or previous location message ( MT) X504 can be set dynamically. The default CoA is a permanent address and is removed from Home Agent Mobility Node 532 when the default CoA feature becomes unavailable, such as when the home address is no longer assigned to End Node (MT) X504. Limited. The home agent 532 then tunnels the arriving packet destined for the home address of the end node (MT) X504 to the default CoA of the end node (MNPS) Y504'' instead of the dynamic CoA of the end node (MT) X504. To do. The default CoA in Figure 6 is the address of the agent node 505'' to which the end node (MNPS) Y504'' is connected. Since the end node (MNPS) Y504'' is the MNPS of the end node (MT) X504, the packet addressed to the home address of the end node (MT) X504 is here, the end node where the application proxy of the end node (MT) X504 is located. (M Delivered to NPS) Y504''. Access node 505'' is home agent 532 because the forwarding at access node 505'' is preset by the binding between the home address of end node (MT) X504 and end node (MNPS) Y504''. Packets from can be deencapsulated and forwarded as packet 617'' to the end node (MNPS) Y504''. While the default CoA is active on the home agent 532, the end node (MNPS) Y504'' becomes the network endpoint for packet 617 destined for the home address of end node (MT) X504.

In yet another embodiment, on the packet flow path between the home mobility agent node 532, foreign mobility agent 507'', end node (MNPS) Y504'', or home agent 532 and end node (MNPS) Y504''. The intermediate node at is an end node because it acts as a network translator and can translate the destination address of packets in the packet flow from the home address of the end node (MT) X504 to the interface address of the end node (MNPS) Y504''. The (MNPS) Y504'' application proxy does not have to reuse the home address of the end node (MT) X504 as the network address.

These features of the present invention allow the end node (MT) X504 to redirect its packets to the end node (MNPS) Y504'' and its home agent 532 under the control of the end node (MT) X504.

The end node (MNPS) Y504'' receives the packet 617'' as if it were the end node (MT) X504, and undertakes the processing of this packet and the application data in this packet. Because the end node (MNPS) Y504'' has an interface that matches the destination address of packet 617'', the application data in this packet is the application in the application proxy that is configured to process this packet data. Pass it to the software. The processing of packet data is controlled by the configuration state of the application proxy. Depending on this configuration state, the MNPS at the end node Y (MNPS) 504'' can provide services to the CN542 instead of the MN in the end node (MT) X504. These services generate application data, create packets, and send the packets to CN542 as part of an ongoing communication session, or to any other end node, including the end node (MT) X504. Features are included. The application proxy can also send and receive signal data that can be used to create, maintain, and terminate a communication session with the CN in signal packets.

Signals or application data packets generated by end node (MNPS) Y504'' instead of end node (MT) X504 as part of a session with CN542 are generally via foreign agent 507'' and home agent 532. Returned to CN542 by reverse route and related processing. When an alternative node other than the home agent 532 has a dynamic CoA state, the CN542 describes the default CoA described in the present invention, for example when using mobile IP route optimization (Non-Patent Document 3). It may have more states.

In yet another embodiment of the invention, the home agent 532 can have a filter associated with the default CoA of the home address of the end node (MT) X504. This filter identifies a specific subset of packets destined for the home address of End Node (MT) X504 that will be forwarded to the default CoA when the dynamic CoA is inactive. Since the application proxy on the end node (MNPS) Y504'' can provide application services for the subset of packets, there is no need to support other applications available on the end node (MT) X504. Filters can be delivered or configured using any of the multiple methods used for the default CoA. Similarly, to configure the application proxy, application packets that the application proxy can send from the source address of the end node (MT) X504 or from either corresponding source address that is translated to the home address of the end node (MT) X504. You can include filters that limit the types of. Alternatively, a filter can be installed on the foreign agent 507'' to regulate packet flow in either direction between the CN542 and the end node (MNPS) Y504''.

In yet another embodiment of the invention, message 601 can include the address of access node 505'' and an instruction that triggers message 624 and acknowledgment 622. This instruction transfers the context state associated with the end node (MT) X504 on the access node 505 to the access node 505'', so that the access node 505'' has the access node 505 as the end node (MT). It is possible to regulate the packet flow 617'' and provide the service to the end node Y (MNPS) 504'' as it is for the X504 and the packet 617. Specific examples of contextual states include policy profiles, paging classifiers, multicast group membership, and security associations required by access nodes 505, 505'' for end node (MT) X504. Alternatively, a similar context state, such as an AAA signal for delivering the context state to access node 505, and message 624, which is used only to carry incremental and / or transient changes to the preconfigured state. It can also be preconfigured on access node 505'' by a policy process. Messages 624 and 622 can also be used to configure a tunnel 620 between access nodes 505 and 505'' to send packets being forwarded to end node (MT) X504 to end node (MNPS) Y504''. be able to. Following messages 622/624, message 618'' is sent from access node 505'' to end node (MNPS) Y504'', and the responsibility for packets exchanged with the home address of end node (MT) X504 is the end node ( Notify the end node (MNPS) Y504'' that it has moved to MNPS) Y504''.

Prior to issuing message 601 to foreign agent 505, the end node (MT) X504Message 634 can be issued to the end node (MNPS) Y504'' using the home address of the end node (MT) X504 as the source address and the interface address of the end node (MNPS) Y504'' as the destination address. Message 634 produces response message 632. Message 634 is used to request that the end node (MNPS) Y504'' be the endpoint of packets that are exchanged with the home address of the end node (MT) X504, whereas the end node (MNPS) Y504'' responds with acknowledgment message 632. Message 634 contains changes to the application's configuration, such as application control or data state in the application proxy on the end node (MNPS) 504'', as well as packet flows that the application proxy processes on behalf of the end node (MT) X504. Can include changes to the filter state etc. used by the end node (MNPS) Y504'' to select a subset of. The response message 632 can include the address of the access node 505'' to which the end node (MNPS) Y504'' is connected, so the end node (MT) X504 sends that address to message 601 to the access node 505. By including it in, the access node 505 can be informed of the address of the access node 505'' for context transfer as part of message 624. Alternatively, the end node (MT) X504 can know in advance both the interface address of the end node (MNPS) Y504'' and its access node 505''. To avoid packet flow hijacking, messages 632 and 634 should be at least authenticated and protected in integrity. Therefore, the end node (MT) X504 and the end node (MNPS) Y504'' are messages between both nodes. To secure the security, the security association associated with the home address of the end node (MT) X504 and the interface address of the end node (MNPS) Y504'' is shared. This security association can be preconfigured, provided by the Policy Server, or dynamically generated. The end node (MT) X504 needs to know the interface address of its MNPS end node Y504'' prior to sending message 634, but the end node (MNPS) Y504'' is in the application proxy service. The home address of the provider can be dynamically notified by the content of message 634.

When the end node (MT) X504 wants to regain packet flow from the end node (MNPS) Y504'', the end node (MT) X504 exchanges messages 601, 602, 603, and 604 to its current access node 505. , 505'by disabling the default CoA of the home agent 532 by setting the dynamic CoA of the home agent 532 and the foreign agent 507. Prior to this, the end node (MT) X504 can regain the packet flow and terminate the application proxy on the end node (MNPS) Y504'' by sending message 634 to the end node (MNPS) Y504''. The end node (MNPS) Y504'' then notifies the end node (MT) X504 with message 632. When the application data is ready (ie, the application data is at the appropriate stage for transfer of control), the relevant application The control state or data can be returned to the end node (MT) X504 so that the end node (MT) X504 can continue processing the application. The access node 505 is then messaged by message 601 to set up a tunnel 620'' to return the packet being forwarded to the access node 505'' of the end node (MNPS) Y504'' back to the access node 505. You can also trigger 624 and 622 to create a route in the opposite direction of packet flow 620. If a change has occurred on access node 505'', messages 624 and 622 can also be used to restore the contextual state containing the change from access node 505'' to access node 505. As a result, if the access node deletes the context state associated with the end node (MT) X504 by leaving the access node 505, the access node 505'' is temporarily in the context state. With memory points Can function. Message 618'' informs the end node (MNPS) Y504'' that the end node (MNPS) Y504'' is no longer responsible for the packet set exchanged with the home address of the end node (MT) X504. used.

Figure 7 shows MNPS instead of the default CoA on Home Agent 532. An alternative embodiment of the present invention using CoA is shown. In this case, the location registration signal containing the home address of the end node (MT) X504 and the CoA of the end node (MNPS) Y504'' is sent to the home agent 532 via the foreign agent 507'' as messages 601'' and 602''. It is the end node (MNPS) Y504'' that sends. As a result, the response messages 603'' and 604'' are returned and the binding in the home agent 532 is updated so that the packet is redirected from tunnel 610 to tunnel 610''. The end node (MNPS) Y504'' can then redirect packets destined for the home address from the end node (MT) X504. End node (MNPS) Y504'' and foreign agent 507'' need to share a security association with home agent 532 to protect these messages from redirect attacks from rogue nodes. The location registration status issued by the end node (MT) X504 itself is not deleted by the location registration from the end node (MNPS) Y504'', and both location registrations are treated separately, but the end node (MNPS) The location registration status from Y504'', specifically CoA, takes precedence over that of the end node (MT) X504. Therefore, even if the end node (MT) X504 is disconnected from the network or malfunctions, the packet flow of the end node (MT) X504 is safely redirected by the end node (MNPS) Y504''.

At this time, message 601'' triggers message 622 and returns response message 624. Again, these messages set up a temporary packet transfer 620 between the access node 505 and the access node 505'' and get the context state from the access node 505. Similarly, when the end node (MNPS) Y504'' no longer needs to receive packets addressed to the home address of the end node (MT) X504, messages 601'', 602'', 603'', 604'', 622, MNPS of home agent 532 by and 624 The CoA is canceled and the packet flow is redirected to the end node (MT) X504 and its access node 505. As a result of messages 622, 624, message 618 informs the end node (MT) X504 if the end node (MT) X504 is currently responsible for packets destined for its home address. To either get or release the packet redirection, the end node (MT) X504 can trigger the end node (MNPS) Y504'' to send message 601''. At this time, the end node (MT) X504 first sends message 634 to the end node (MNPS) Y504''. In response, the end node (MNPS) Y504'' returns message 632. Other nodes, such as access node 505, CN542, or home agent 532, can instead trigger end node (MNPS) Y504'' to issue message 601'' with a message similar to message 634. ..

FIG. 8 is the same as FIG. 6 except that the MNPS CoA of the end node (MNPS) Y504'' is a concatenated CoA equal to the interface address of the end node (MNPS) Y504''. Therefore, the redirected packet flow 611'is a tunnel that directly connects the home agent 532 and the end node (MNPS) Y504'', so the access node 505'' does not require the foreign agent function 507''. .. In addition, the in-transit packet 620 can be sent directly to the CCoA of the end node (MNPS) Y504'' without going through the access node 505''. However, the issuer of message 601'' is not the end node (MT) X504 as shown in Fig. 6, but the end node (MNPS) Y504'' as shown in Fig. 7, and the location registration is via the access node 505''. Foreign agent 507'' may still be required if packet 620 in transit is still sent to access node 505.

Figure 9 shows an alternative embodiment of the default CoA function in the special case where the end node (MNPS) Y504'' is on the same MAC tier network as the home agent 532, that is, on the home network 530'of the end node (MT) X504. Is shown. FIG. 9 shows the networking between CN542 and the components of network 530 in FIG. In Figure 9, links 508'''and 506''' are introduced to connect the end node (MT) X504 and the end node (MNPS) Y504'' to the home agent 532. These nodes execute a protocol for distributing the mapping between the MAC layer address of each interface and its corresponding IP address, as in the case of Neodymium Discovery or Address Resolution Protocol (ARP) in IPv6 (ND). To do. If the end node (MT) X504 is not on the home network 530'and is connected to a foreign access node such as 505, and the end node (MT) X504 has dynamic CoA on the home agent 532, the home agent is a proxy. Packets destined for that home address are forwarded to it by a node on the MAC layer network by sending an association between that MAC layer address and the home address of the end node X504 with the ARP signal 902'''. Indicates that it should be. The home agent 532 then tunnels these packets to the currently registered dynamic CoA, as indicated by the thick solid arrow. However, if the end node X (MT) 504 is on the home network 530', the end node X (MT) 504 will send an ARP message 915'''with its MAC layer address on link 508'''to the MAC layer. Since it is issued on the network, such packets 920''' are forwarded to end node X (MT) 504 instead. This ARP message 915'''is from home agent 532 to everything else on the MAC tier network. Cancel the proxy ARP message 902'''to the node. Note that the home agent normally does not send message 902'''.

In one exemplary embodiment of the invention, the end node (MNPS) Y504'' is, for example, the home address of the end node (MT) X504 by issuing a proxy ARP message 905''' without losing generality. Packets destined for can be redirected to the end node (MNPS) Y504'' to create a packet flow 910'''. This allows MNPS, but only when the end node (MNPS) Y504'' is on the home network. The CoA redirection function is reproduced. Proxy ARP message 902'''' sent by home agent 532, proxy ARP message 915'''' sent by end node (MT) X504, and proxy ARP message 905'''' sent by end node (MNPS) Y504'' Can be strictly ordered by using a priority flag in each ARP message, or instead consider the final message to be the latest configuration. It is also possible to use a message suppression method that uses the internal priority used by each node to identify who is the current recipient of packets destined for the home address of the end node (MT) X504. In this special case, the default ARP binding that is driven when the end node (MT) X504 is not on the home network and no valid dynamic CoA is registered with the home agent 532 is replaced by the home agent 532. By storing it, the default CoA function can be reproduced. This default ARP binding is then advertised by the home agent to identify the MAC layer address of the end node (MNPS) Y504'' instead of the MAC layer address of home agent 532.

There are various alternative embodiments in the practice of the present invention. First, access node 505'' can accommodate home agent 532 while using the default CoA and MNPS CoA features. In addition, there can be multiple MNPSs for each home address, and filters can route packets to the correct MNPS function for each subset of packet flow. One of the MNPS can be placed on the same node as the home agent 532. In addition, MNPS software can be placed on access node 505''. The present invention includes signaling and forwarding schemes, including various forwarding options such as mobile IPv4 and / or v6 routing optimization. The various messages detailed in the present invention can be used in different subsets and combinations to meet the requirements of the application proxy for packet subsets redirected from the end node (MT) X504.

Next, some examples of application proxy features will be described.

First, using the default CoA, all packets destined for the assigned home address that do not have a dynamic CoA registered with the home agent 532 are destined for the application proxy, which acts as an error logger by simply capturing the packet header. You can redirect.

Second, an enhanced version that allows access node 505 to put the end node (MT) X504 to sleep and the paging classifier to redirect packets to access node 505'' that is contained in the context state of end node (MT) X504. Can support IP paging system. The paging classifier can determine whether to drop the packet, forward it to MNPS, or trigger a paging message to the current location of the end node (MT) X504 accessible from access node 505''. Packets forwarded to the end node (MNPS) Y504'' are processed by the MNPS and then the application event triggers message 601'' to forward the packet forward to the current position of the end node (MT) X504, message 602. '' Can be used to return to the position set in the home agent 532 as CoA. Alternatively, MNPS can simply send message 632 to end node X504, in which case message 632 is passed to access node 505'' and then at that access node to the current position of end node (MT) X504. Trigger the paging function towards. As a result of this paging feature, the end node (MT) X504 may want to wake and recover its packet reception and forwarding. Therefore, the end node (MT) X504 uses message 601 to update the home agent to its current CoA, triggering 622/624 to restore its context state from access node 505'', and messages 634 and 622. Use to restore the application state from MNPS.

While the end node (MT) X504 sleeps, MNPS can issue keepalive packets to any application and protocol in CN that requires keepalive packets to maintain a session. The end node (MT) X504 uses the exchange of messages 634/632 and the preconfigured application proxy state to keep the session to be refreshed, the refresh interval, and the security state to secure the keepalive signal. Notify MNPS of alive peers and response behavior when a session ends or an incoming data packet arrives in that session. This allows the end node X (MT) 504 to enter a power efficient extended sleep without losing connectivity with the application server and network gateway.

In the third application of the present invention, the end node (MT) X504 can instruct the delivery of one content, and the delivery destination can be the MNPS of the end node (MNPS) Y504'' by using the filter of the home agent 532. Can develop a distribution system. Then, depending on the state of the MNPS application proxy, when the entire content is delivered, you can send a message to the end node (MT) X504, or simply until the end node (MT) X504 inquires about its delivery status. You can also wait. The end node (MT) X504 or end node (MNPS) Y504'' can then redirect the packet back to the end node (MT) X504 using the method of the invention and then the end node (MNPS). ) Y504'' can deliver the content to the end node (MT) X504. This allows the end node X (MT) 504 to go to sleep or use its bandwidth for other purposes while the content is being delivered to the end node (MNPS) Y504'', and then Delivery can be requested at the optimal time for the end node (MT) X504.

In the alternative content distribution system, the end node (MNPS) Y504'' can act as the content server for the content from the end node (MT) X504. The end node (MT) X504 then wakes up and uses a filter to send content requests to the end node (MNPS) Y504'' content server while updating the content to the end node (MNPS) Y504'. Can be delivered efficiently to'. This allows the end node (MT) X504 to supply its content locally because it does not need to publish its content from the end node (MT) X504 itself, the fixed node. In addition, the end node (MT) X504 has a subset of the flow because the server address is the same regardless of whether the actual source of the content is the end node (MT) X504 or the end node (MNPS) Y504''. It can be supplied as appropriate during the entire time or a part of the time. Messages 634/632 synchronize each application on the end node, while messages 601, 602, 603, 604, 622, 624, and 618 manage packet forwarding.

FIG. 10 shows an exemplary communication system 1000 according to a particular exemplary embodiment of the invention. System 1000 has a first node such as mobile node 1001, a second node such as access node 1003 that can be used as a MIP foreign agent, and a third node such as intraregional mobility agent node 1005 that can be used as a MIP home agent. It includes a node, a fourth node such as a communication peer node 1007, which is also called a communication partner node, a fifth node such as a network node 1009, and a sixth node such as an access node 1011. Mobile node (MN) 1001 is coupled to access node 1003 via wireless link 1013. Network node 1009 is joined to access node 1011 via link 1017. The home agent, or regional mobility agent node 1005, is included in routing system 1019. The home agent, or regional mobility agent node 1005, is coupled to access node 1003, access node 1011, and communication peer node 1007, respectively, via links 1023, 1025, and 1027. Access nodes 1003, 1011 are usually part of the routing system 1019. The second node, such as the access node 1003, is defined by a defined route for forwarding a packet having a CoA corresponding to the mobile node 1001 to the mobile node, for example, a routing table included in the internal memory. Has a route. The sixth node, such as access node 1011, is the mobile node if the mobile node proxy server (MNPS) of the fifth node 1009 is responsible for processing application packets corresponding to the shared address common to both MN1001 and MNPS1009. A defined route for forwarding a packet with a CoA corresponding to 1001 to the mobile node proxy server (MNPS) of the fifth node 1009, for example, a route specification included in the internal memory. It has a route defined by the table. Each of these various nodes may be located in a different addressing domain, in which case the address associated with each domain contains a different address prefix to identify each addressing domain. System 1000 includes at least two addressing domains, but the number of addressing domains may be higher, for example three. The home mobility agent node 1005 is typically located in a different domain than the FA node, eg, the second node 1003, and the FA node 1003 is typically located in the same domain as the regional mobility agent 1005. The other nodes 1011, 1009 may be located on the same node as FA node 1003 or home agent 1005, or may be located in a completely different domain, such as a third addressing domain, and may be located in a third addressing domain. It may be identified by a third prefix contained in the address corresponding to the node.

The MN1001 includes an application state 1029, an application routine 1031 containing an IP-based communication application 1033 and a second application 1035, and a shared address 1037. Access node 1003 includes mobility agent 1039 and encapsulation / decapsulation and forwarding routine 1041. Access node 1003 may be the access router or base station used by MN1001. While the MN1001 is in the foreign domain where the access node 1003 is located, the mobility agent 1039 can act as a foreign agent (FA) for the MN1001. Home agent or regional mobility agent node 1005 contains binding table 1043 and encapsulation / decapsulation transfer routine 1045. Lifetime information may be included in the address binding information contained in binding table 1043. Node 1005 can act as a home agent (HA) for MN1001. Communication peer node 1007 includes a set of application routines 1047, such as software applications, including an IP-based communication application (first application) 1049 and a second application 1051. The fourth node 1007 is a communication partner node (CN) with which the MN1001 communicates in an exemplary communication session involving the first application 1033. The network node 1009 may be a mobile node proxy server (MNPS) as it acts as an application proxy for at least a portion of the period during which the MN1001 is unable to continue interacting with the first application. As part of its role as an application proxy, the MNPS1009 receives packets corresponding to the application flow with a destination address corresponding to the MN1001 and processes these received packets. Two as part of the process At least one packet may be generated from the main body of the received packet of, and the generated packet may be transmitted to CN1007. The unresponsiveness of a node may be due to a decision made by the MN1001 such as going to sleep, or due to an event outside the control of the MN1003 such as a signal interruption due to interference. When node 1009 is acting as MNPS, node 1009 can communicate with CN1007 instead of MN1001. In order to exchange application processing and control between MN1001 and MNPS1009, information about the application status, for example, the current processing status of the application and / or the processing result of the packet received from CN1007 is between MN1001 and MNPS1009. Will be exchanged at. In this exchange, the application processing may be handed off to the MNPS1009, and then the responsibility of the application may be returned to the MN1001 with a state indicating how far the MNPS1009 has performed the application processing. The responsibilities of multiple different applications between the MN1001 and MNPS1009 may be handed off at different times. The routing control signal sent to the routing system 1019 ensures that the packet flow corresponding to one application is routed to the MN, or to the MNPS responsible for processing the packet corresponding to that particular application at a given point in time. It is specified. Therefore, a plurality of different packet flows corresponding to a plurality of different MN applications 1033 and 1035 can be classified by the routing system 1019 and routed to different nodes. In fact, when the MN1001 is not available, it is possible to use multiple different MNPS nodes 1009 instead of the MN1001 to support multiple different applications. In addition, if the MN is unable to accommodate one application, the MN can continue to process packets for another application. Therefore, it is actively used by MN. Responsibility for one or more subsets of application 1033, 1035 may be handed off to MNPS1009 at different times. Since it is not necessary to notify the communication partner node 1007 whether the MN1001 or the MNPS1009 is receiving and processing the packet corresponding to the specific application, the communication partner node 1007 always has the communication partner MN1001 for the specific application. The operation can be continued under the assumption that. As described below, the signal sent to the routing system 1019 regarding the redirection of packets corresponding to a particular application associated with the MN1001 may be sent from either the MN1001 or the MNPS1009 to the RS1019. These signals typically include a routing identifier that identifies the node 1001 or 1009 to which the application packet is destined. In some cases, the routing identifier identifies an intermediate node, eg, FA1003, that has a defined route to the destination node of the application packet. In such a case, when the identified intermediate node receives the packets destined for MN or MNPS, it forwards these packets to the destination node having the routing relationship, for example, MN or MNPS. This relationship is typically reflected in the binding table for routing packets to MN or MNPS and is contained in intermediate nodes 1003 or 10011. The routing identifier sent to RS1019 may be, for example, the address corresponding to MN or MNPS, or the address and some other routing information, such as a weighted value to influence the routing decision by RS1019. It may be a combination of. In some cases, by including additional information such as a packet classifier in the routing identifier, the routing system detects packets belonging to the first or second application 1049, 1051 of CN1007, and the first and second Application packet May be able to be sent to different nodes 1001 and 1009, respectively. If the packet classifier is not in the routing identifier, the routing system redirects all packets in the first packet flow 1069 to the node identified by the routing identifier.

Node 1009 contains an application state 1053 and an application proxy routine 1055 that includes an IP-based communication application proxy routine corresponding to the first application 1057 and a second application proxy routine 1059 corresponding to the supported second application. And the shared address 1037. The shared address 1037 corresponds to both the MN1001 and the network node (MNPS) 1009. Access node 1011 includes a mobility agent 1061 and an encapsulation / decapsulation transfer routine 1063. Access node 1011 joins network node 1009 to the rest of system 1000.

During system operation according to the present invention, the MN1001 or network node (MNPS) 1009 sends a first message 1065 to the routing system 1019 and its node 1005. Figure 10 shows message 1065 sent by Network Node (MNPS) 1009. The first message 1065 contains the routing identifier 1067. The routing identifier 1067 is a node in a node group that includes a MN1001, a network node (MNPS) 1009, and a node that has a defined route to the MN1001 or MNPS1009, such as a second node 1003 and a sixth node 1011. Is uniquely identified. The routing system 1019 sends the first packet flow 1069 from CN1007, for example the flow corresponding to the first application, to MN1001 or network node (MNPS) 1009. At least some of the packets in packet flow 1069 correspond to packet 1071 of the first application. One of the nodes identified by the routing identifier, eg, MN1001 or Network Node (MNPS) 1009, receives the first packet flow 1069 at a given point in time. Packet flows are sent at a given point in time to node 1001, or 1009, which is responsible for processing the application and interacting with CN1007. The first packet flow 1069 is, for example, the first packet flow 1069a from CN1007 to the home agent mobility node 1005 and the first packet flow from the home agent mobility node 1005 to the access node 1003 during the first period. It may include 1069b and a first packet flow 1069c from access node 1003 to MN1001. Alternatively, the first packet flow 1069 is, for example, the first packet flow 1069a from CN1007 to the home agent mobility node 1005 and the home agent mobility node during the second period.

When the MN1001 receives the first packet flow 1069c, the IP-based communication application routine 1033 processes the received packet, and as a result of this application processing, generates an additional packet containing the application data 1071 and adds these packets to the additional packet. Send to CN1007 by flow 1073. The additional packet flow 1073 includes an additional packet flow 1073a from the MN1001 to the access node 1003, an additional packet flow 1073b from the access node 1003 to the home agent mobility node 1005, and an additional packet flow 1073c from the home agent mobility node 1005 to CN1007. including. Similarly, if the network node (MNPS) 1009 receives the first alternate packet flow 1069e, the IP-based communication application proxy routine 1057 processes the received packet and generates additional packets as a result of the application processing by this proxy. Then, these packets are transmitted by the additional packet flow 1073. The additional packet flow 1073 includes an alternative additional packet flow 1073d from the network node (MNPS) 1009 to the access node 1011, an alternative additional packet flow 1073e from the access node 1011 to the home agent mobility node 1005, and a home agent mobility node 1005 to CN1007. Includes additional packet flow 1073c to.

According to one embodiment of the invention, the forwarded message 1075 is sent from the MN1001 to the network node (MNPS) 1009 prior to the transmission of the first message 1065. By this message 1075, the transfer of processing responsibility for the application packet originating from CN1007 is performed from the first node 1001 or the fifth node 1009 at the time of the application processing transfer message 1075 among the first and fifth nodes. Started for a node that is not responsible for processing. Forwarding message 1075 may include a routing identifier that identifies the node that takes responsibility for processing the application. The network node (MNPS) 1009 sends a first message 1065 containing a routing identifier in response to the forwarded message. The additional message 1077 from the MN1001 to the network node (MNPS) 1009 defines the requirements of the MN1001 for packet processing by the application proxy of the network node (MNPS) 1009, and the MNPS1009 is responsible for processing the application. If you accept from, it will be sent. Status information such as MN application status 1029 may also be included in message 1077 and transferred to MNPS application status 1053. This allows the MNPS to continue processing the application from the moment the MN1001 transfers responsibility for processing the application to the MNPS1009. The processing result / status message 1079 from the network node (MNPS) 1009 to the MN1001 returns the information derived from the packet processing by the application proxy of the network node (MNPS) 1009 to the MN1001. The returned information may include packets such as application data packets generated from the processing of the body of at least two packets corresponding to the first packet flow received by the MNPS1009. This message is the responsibility of the application

CN1007 supports a second application with a second application routine 1051. The MN1001 supports this second application by the second application routine 1035, and the network node (MNPS) 1009 by the second application proxy routine 1059. A second application packet flow 1081 including a second application packet 1083 is shown in FIG. The second application packet flow 1081 includes a second application packet flow 1081a from CN1007 to the home agent mobility node 1005, a second application packet flow 1081b from the home agent mobility node 1005 to the access node 1003, and an access node 1003. Includes a second application packet flow 1081c from to MN1001. Alternatively, this packet flow can be sent to the network node (MNPS) 1009 at another time instead of the MN1001. The associated messages, signals, return packet flows, and alternative flows are the same or similar as described for the first application and will not be repeated for the second application for brevity. Therefore, the routing system can act as a filter, sending application packets corresponding to one MN application to the MN proxy 1009, while sending application packets corresponding to the second MN application to the mobile node 1001. It should be understood that the availability of mobile nodes can vary among several different applications supported by MN at the same time. Thus, in various embodiments, the first message redirects packets corresponding to each particular single application or multiple applications identified in the message to the identified node, or by the MN1001. Indicates whether to redirect packets corresponding to all supported applications to, for example, MNPS1009. Therefore, even if multiple packets have one source address corresponding to the CN address and one destination address corresponding to the shared addresses of the first and fifth nodes 1001 and 1009, they correspond to different applications. In the case of packets, they may be associated with different packet flows depending on the purpose of the routing method.

In yet another embodiment, the third node 1005, the fifth node 1009, and the sixth node 1011 are on the same network and therefore share the MAC layer connection. In this case, the third node and the sixth node may be the same node including both the home and foreign mobility agents. The fifth node can issue the first message 1065 containing the routing identifier 1067, which is the MAC layer address of the fifth node. The MAC layer address is entered in the binding table 1043 of the third node as the current MAC layer CoA of the first packet flow, so the packet goes to the fifth node via the MAC layer address of the fifth node. Transferred. In addition, this MAC layer CoA can be stored in the binding table 1043 as the default MAC layer CoA, so if the binding table entry pointing to the second address (CoA) of the first node expires on the second node. , The packet is automatically redirected to the 5th node by forwarding the MAC layer on the 3rd node. When the first node returns to the network containing the third, fifth, and sixth nodes, the first node can issue the first message 1065 with the routing identifier 1067 equal to its MAC address. This message 1065 is received by the third, fifth, and sixth nodes by this type of broadcast. As a result, the fifth node stops refreshing its MAC address in the binding table for the first packet flow. This new MAC layer CoA is used in place of the previously issued MAC layer CoA by the fifth node, so that the first packet flow is destined for the first node.

According to the present invention, the addresses assigned to various nodes may be arranged in the same addressing domain or in a plurality of different addressing domains. In some embodiments, the addresses assigned to the first, third, and fifth nodes are in the first addressing domain. In such a case, the home address of the MN1001 has the same address prefix as the address of the third node and is shared with the fifth node. The fifth address associated with the fifth or sixth node is often in the second addressing domain (for example, the MNPS1009 CoA address is usually the same address prefix as the access router's address). .. The second node and the second address corresponding to the second node can also be placed in yet another addressing domain, such as a third addressing domain. This may be due to the MN1001 moving onto the foreign subnet and the second address becoming the CoA of the MN1001. In various embodiments, the first, second, and third addressing domains include and correspond to at least two different addressing domains. In other cases, the first, second, and third addresses are in three different addressing domains. In yet a plurality of other embodiments, the first, second, and third addresses are all in the same addressing domain. Therefore, the present invention has a wide range of possibilities regarding which address, and thus which node, can be placed in the same addressing domain or a plurality of different addressing domains. Addressing domains are different if the addresses used within the domain have different address prefixes with the same prefix length, that is, if the N most significant address bits are different. Therefore, addresses having the same prefix of length N are determined to be in the same domain. Here, N is the prefix length, that is, the number of bits for distinguishing between different domains. Various fruits In embodiments, at least one of the first, second, and third addressing domains has addresses corresponding to different domains, including different address prefixes. Different from another one of the addressing domains in. In one of these various embodiments, the first and third addressing domains are the same, and the second addressing domain is different from the first and second addressing domains. .. In another embodiment of these various embodiments, the second and third addressing domains are the same, and the first addressing domain is the first and second addressing domains. Different from domain. Each node may be associated with one or more addresses having an address prefix of the domain to which the node belongs.

Various features of the invention are packets that trigger network paging when the first node is sleeping or otherwise absent and incoming packets destined for the first node are unreachable. Allows paging of the first node by arriving at the second node and generating application events in the application agent module that processes packets on behalf of the first node in the absence of the first node. It is designed to be. This allows for more advanced paging, so that the first node goes to sleep, notifies the application agent to complete the task or detect an application event, and when that task completes or an event occurs. Sometimes the first node can be paged. The page can be generated when the file is delivered or when a voice is received from a specific person, not by each packet or any voice call that contributes to the delivery of the file. For example, to allow fast paging and its connectivity to respond immediately to a call request, the paging mechanism can not only deliver the parameters to the first and third nodes, but also the first after paging is complete. You can configure redirect forwarding to the first node without the paging message from the first node. This allows paging and routing updates to proceed in parallel with dynamic address and mobility agent allocation.

FIG. 11 shows a drawing 1000 illustrating an exemplary node, packet flow, and paging signal in an exemplary system according to the invention. Although Figures 11 and 12 show communication from CN114 to MN1102, it should be understood that packets and messages can also travel from MN to CN1114. FIG. 11 shows an end node, for example, mobile node (MN) 1102, as the first node, which becomes a third node, such as access node (AN) 1104, via wireless link 1106. Combined, this access node (AN) 1104 contains profile state 1108 associated with MN1102 (first node), and any of the communication sessions normally performed by MN1102 using this profile state 1108. Controls whether the application agent module 1138 or 1138'can be executed. Application agent module 1138 may be on a second node, for example Regional Mobility Agent (RMA) node 1110. The application agent module 1138'may be on the mobile node proxy server (MNPS) 1140 of a fourth node, such as an application proxy node. RMA node 1110 is joined to AN1104 via network link 1112. Peer nodes such as communication partner node (CN) 1114 are coupled to RMA node 1110. CN1114 may be another MN that communicates with MN1102 in a communication session. Figure 11 also includes the paging policy server 1160, which is coupled to RMA node 1110 via link 1162. The paging policy server 1160 may send information indicating a paging trigger event to application agent modules 1138, 1138'. RMA node 1110 contains mobility agent module 1120 and mobility agent module 1120 contains forwarding table 1152. It includes a transfer module 1122, a first paging module 1124 that includes a first paging information 1125, a second paging module 1126 that contains a second paging information 1127, a network paging routine 1128, and a location routine 1130. In FIG. 11, the packet flow is indicated by a thick solid arrow and the signal is indicated by a thick dashed arrow. The forwarding module 1122 forwards the packet 1150 to MN1102 received from peer node CN1114 as packet 1150A (via AN1104) to MN1102, or as packets 1150C and 1150D to the first and second paging modules 1124 and 1126, respectively. By comparing packets 1150C and 1150D sent to the first and second paging modules 1124 and 1126 with the first paging information 1125 and the second paging information 1127, respectively (matching the paging state or categorized by the paging state). Determine subsequent packet processing.

When packet (group) 1150C matches the first paging information 1125, packet (group) 1150E triggers network paging routine 1128 and sends first paging message 1170 to the current location of MN1102. In the example of FIG. 11, at this current position, MN1102 is bound to AN1104. Alternatively, the current location of the MN1102 may be different, in which case the MN1102 is attached to one of the similar access nodes in the system. The first paging message 1170 can be sent directly to the address of MN1102 or to the address of AN1104. In either case, given the packet type that triggered the page identified by the matching entry in the first paging information 1125, the first paging message 1170 contains an instruction for paging the MN1102. The location of MN1102 is determined by networking paging routine 1128 querying location server 1132 directly or indirectly. Location server 1132 may be on RMA node 1110 or on another node 1134 that is attached to RMA node 1110 via link 1136 as shown in Figure 11. In response to an inquiry from network paging routine 1128, location routine 1130 may obtain location state information 1133 for MN1102 (first node) by exchanging signal 1135 with location server 1132. The network paging routine 1128 can use various techniques to contact the MN1102 via its current location and make the MN1102 reachable by the availability of packets for the MN1102. The first paging module 1124 ensures that contact with the MN1102 is attempted when a packet of sufficient importance to the MN1102 reaches RMA node 1110. In the first paging message 1170 , The information of the entry in the first paging information 1125 that triggered paging for MN1102 (and thus the nature of the received packet) can be included. The information in the first paging message 1170 can also include delivery of MN (first node) profile state 1108 to AN1104, so AN1104 becomes MN1102 (identifier, IP address, paging slot, security association). It can be contacted and then the operation of the MN1102 can be regulated with respect to its communication. The information in the first paging message 1170 can further include the dynamically assigned address and the mobility agent state in which the paging trigger triggered the assignment by the first paging information 1125. Alternatively, the first paging message 1170 can include information for the MN1102 and AN1104 to acquire the profile state 1108 and dynamically assign parameters (such as the policy server address and the MN1102 identifier). Since the response to the first paging message 1170 is made by MN1102 or AN1104 instead of MN1102, the network paging routine 1128 determines the result of the paging message. As a result of this one, MN1102 becomes reachable, so packets destined for MN1102, including packets initially routed via the first paging module 1124, are packet 1150A, with forwarding module 1122 using forwarding table 1152. Transfer to MN1102 via AN1104 on 1150B. Changes in transfer table 1152 can be made in various ways as described below. Therefore, AN1104 can contact MN1102 (identifier, IP address, paging slot, security association) and then regulate the operation of MN1102 with respect to its communication. The information in the first paging message 1170 can further include the dynamically assigned address and the mobility agent state in which the paging trigger triggered the assignment by the first paging information 1125. Alternatively, the first paging message 1170 can include information for the MN1102 and AN1104 to acquire the profile state 1108 and dynamically assign parameters (such as the policy server address and the MN1102 identifier). Since the response to the first paging message 1170 is made by MN1102 or AN1104 instead of MN1102, the network paging routine 1128 determines the result of the paging message. As a result of this one, MN1102 becomes reachable, so packets destined for MN1102, including packets initially routed via the first paging module 1124, are packets destined for MN1102 by forwarding module 1122 using forwarding table 1152, packet 1150A, Transfer to MN1102 via AN1104 on 1150B. Changes in transfer table 1152 can be made in various ways as described below. Therefore, AN1104 can contact MN1102 (identifier, IP address, paging slot, security association) and then regulate the operation of MN1102 with respect to its communication. The information in the first paging message 1170 can further include the dynamically assigned address and the mobility agent state in which the paging trigger triggered the assignment by the first paging information 1125. Alternatively, the first paging message 1170 can include information for the MN1102 and AN1104 to acquire the profile state 1108 and dynamically assign parameters (such as the policy server address and the MN1102 identifier). Since the response to the first paging message 1170 is made by MN1102 or AN1104 instead of MN1102, the network paging routine 1128 determines the result of the paging message. As a result of this one, MN1102 becomes reachable, so packets destined for MN1102, including packets initially routed via the first paging module 1124, are packets destined for MN1102 by forwarding module 1122 using forwarding table 1152, packet 1150A, Transfer to MN1102 via AN1104 on 1150B. Changes in transfer table 1152 can be made in various ways as described below. It can include a receipt server address and an MN1102 identifier, etc.). Since the response to the first paging message 1170 is made by MN1102 or AN1104 instead of MN1102, the network paging routine 1128 determines the result of the paging message. As a result of this one, MN1102 becomes reachable, so packets destined for MN1102, including packets initially routed via the first paging module 1124, are packets destined for MN1102 by forwarding module 1122 using forwarding table 1152, packet 1150A, Transfer to MN1102 via AN1104 on 1150B. Changes in transfer table 1152 can be made in various ways as described below. It can include a receipt server address and an MN1102 identifier, etc.). Since the response to the first paging message 1170 is made by MN1102 or AN1104 instead of MN1102, the network paging routine 1128 determines the result of the paging message. As a result of this one, MN1102 becomes reachable, so packets destined for MN1102, including packets initially routed via the first paging module 1124, are packets destined for MN1102 by forwarding module 1122 using forwarding table 1152, packet 1150A, Transfer to MN1102 via AN1104 on 1150B. Changes in transfer table 1152 can be made in various ways as described below.

When packet (group) 1150D matches the second paging information 1127, packet (group) 1150D is forwarded as packet 1150F to application agent module 1138 or 1138'. The application agent module 1138 or 1138'is on the RMA node 1110 but is attached to the RMA node 1110 via link 1142 shown in Figure 11, for example, the mobile node proxy server (MNPS) of the application proxy node. ) May be at 1140. Specifically, RMA node 1110 can include multiple entries in the second paging information 1127 that sends packet 1150D to multiple local and remote application agent modules 1138, 1138'. Application agent modules 1138, 1138'contains application event and related paging behavior tables 1144, 1144', as well as application paging routines 1146, 1146' and MN proxy applications (groups) 1147, 1147'. Application agent modules 1138, 1138'can process the payload of received packet 1150F matching the second paging information 1127 under the control of one or more MN proxy applications 1147, 1147', instead of MN1102. The payload contains application data, and the processing generates application data and additional transmission packets that are returned to peer node CN1114, destined for MN1102, or destined for an alternate peer node. The MN proxy applications (s) 1147, 1147'may include, for example, communication applications, data processing applications, file download communication applications, spreadsheet applications, and decoder applications. For processing the packets, packet payloads, and application data Therefore, application events are generated and these application events are compared to tables 1144, 1144'of such events associated with MN1102. When these application events occur, such as downloading a complete file or instructing the availability of a new mail message addressed to MN1102, the corresponding application paging event is triggered. One such paging event sends a second paging message 1172 to network paging routine 1128, triggering the first paging message 1170. This allows network reachability to MN1102 to be reestablished in forwarding table 1152. Alternatively, application paging routines 1146, 1146'can send a second paging message 1172A directly to the current location of MN1102 indicated by location information 1133. The second paging message 1172A differs from the first paging message 1170 in that application events and corresponding application states can be delivered to AN1104 and / or MN1102 by paging message 1172A. This gives the MN1102 more accurate information about the reason for paging and the pros and cons of waking up, so the MN1102 gives further instructions to this page to application agents 1138, 1138'and then goes back to sleep. be able to. However, the second paging message 1172A contains (or triggers to be fetched by AN1104) the dynamically assigned parameters and the MN profile state 1108, as described for the information in the first paging message 1170. )be able to. Compared to 144'. When these application events occur, such as downloading a complete file or instructing the availability of a new mail message addressed to MN1102, the corresponding application paging event is triggered. One such paging event sends a second paging message 1172 to network paging routine 1128, triggering the first paging message 1170. This allows network reachability to MN1102 to be reestablished in forwarding table 1152. Alternatively, application paging routines 1146, 1146'can send a second paging message 1172A directly to the current location of MN1102 indicated by location information 1133. The second paging message 1172A differs from the first paging message 1170 in that application events and corresponding application states can be delivered to AN1104 and / or MN1102 by paging message 1172A. This gives the MN1102 more accurate information about the reason for paging and the pros and cons of waking up, so the MN1102 gives further instructions to this page to application agents 1138, 1138'and then goes back to sleep. be able to. However, the second paging message 1172A contains (or triggers to be fetched by AN1104) the dynamically assigned parameters and the MN profile state 1108, as described for the information in the first paging message 1170. )be able to. Compared to 144'. When these application events occur, such as downloading a complete file or instructing the availability of a new mail message addressed to MN1102, the corresponding application paging event is triggered. One such paging event sends a second paging message 1172 to network paging routine 1128, triggering the first paging message 1170. This allows network reachability to MN1102 to be reestablished in forwarding table 1152. Alternatively, application paging routines 1146, 1146'can send a second paging message 1172A directly to the current location of MN1102 indicated by location information 1133. The second paging message 1172A differs from the first paging message 1170 in that application events and corresponding application states can be delivered to AN1104 and / or MN1102 by paging message 1172A. This gives the MN1102 more accurate information about the reason for paging and the pros and cons of waking up, so the MN1102 gives further instructions to this page to application agents 1138, 1138'and then goes back to sleep. be able to. However, the second paging message 1172A contains (or triggers to be fetched by AN1104) the dynamically assigned parameters and the MN profile state 1108, as described for the information in the first paging message 1170. )be able to. Message 1172 is sent to network paging routine 1128, triggering the first paging message 1170. This allows network reachability to MN1102 to be reestablished in forwarding table 1152. Alternatively, application paging routines 1146, 1146'can send a second paging message 1172A directly to the current location of MN1102 indicated by location information 1133. The second paging message 1172A differs from the first paging message 1170 in that application events and corresponding application states can be delivered to AN1104 and / or MN1102 by paging message 1172A. This gives the MN1102 more accurate information about the reason for paging and the pros and cons of waking up, so the MN1102 gives further instructions to this page to application agents 1138, 1138'and then goes back to sleep. be able to. However, the second paging message 1172A contains (or triggers to be fetched by AN1104) the dynamically assigned parameters and the MN profile state 1108, as described for the information in the first paging message 1170. )be able to. Message 1172 is sent to network paging routine 1128, triggering the first paging message 1170. This allows network reachability to MN1102 to be reestablished in forwarding table 1152. Alternatively, application paging routines 1146, 1146'can send a second paging message 1172A directly to the current location of MN1102 indicated by location information 1133. The second paging message 1172A differs from the first paging message 1170 in that application events and corresponding application states can be delivered to AN1104 and / or MN1102 by paging message 1172A. This gives the MN1102 more accurate information about the reason for paging and the pros and cons of waking up, so the MN1102 gives further instructions to this page to application agents 1138, 1138'and then goes back to sleep. be able to. However, the second paging message 1172A contains (or triggers to be fetched by AN1104) the dynamically assigned parameters and the MN profile state 1108, as described for the information in the first paging message 1170. )be able to. And / or be able to deliver to MN1102. This gives the MN1102 more accurate information about the reason for paging and the pros and cons of waking up, so the MN1102 gives further instructions to this page to application agents 1138, 1138'and then goes back to sleep. be able to. However, the second paging message 1172A contains (or triggers to be fetched by AN1104) the dynamically assigned parameters and the MN profile state 1108, as described for the information in the first paging message 1170. )be able to. And / or be able to deliver to MN1102. This gives the MN1102 more accurate information about the reason for paging and the pros and cons of waking up, so the MN1102 gives further instructions to this page to application agents 1138, 1138'and then goes back to sleep. be able to. However, the second paging message 1172A contains (or triggers to be fetched by AN1104) the dynamically assigned parameters and the MN profile state 1108, as described for the information in the first paging message 1170. )be able to.

FIG. 1200 of FIG. 12 shows the exchange of signals in preparation for or in response to network or application layer paging. FIG. 12 shows MN1102 (first node), AN1104 (second node), RMA node 1110 (third node), MNPS1140, and MNPS1140 as a group of nodes that are the same as or similar to those described in FIG. Includes location server node 1134 and CN1114. Receiving a page on the MN1102 triggers the first routing message 1202. This can generally be a MIP location request or binding update, which sets the CoA of the MN1102 to the mobility agent module 1120 so that packets are redirected from the paging modules 1124, 1126 to the MN1102. Become. When the MN1102 goes to sleep, a second routing information message 1204 is sent from either the MN1102 or AN1104, and the first entry details when the MN1102 can be paged when there is an arrival packet. Paging information is set to 1125. The result of this setting is returned by the response message. Since the first paging information 1125 can be specifically included in the MN profile state 1108, the second routing message 1204 moves the MN1102 profile state 1108 to the first paging information 1125. When a page is triggered, the first or second paging message 1170, 1172 (A) returns it to AN1104. By sending a third routing message 1206 from the MN1102 or AN1104 to the application events and paging tables 1144, 1144', it specifies which event and the corresponding paging process should be processed. Next, the application agent modules 1138, 1138'use the fourth routing message 1208 to provide the second paging information 11 Setting 27 to Mobility Agent Module 1120 ensures that packets of the correct type are forwarded and processed to Application Agent Modules 1138, 1138'. Mobility module 1120 responds to application agent modules 1138, 1138', and application agent modules 1138, 1138' responds to MN1102 or AN1104, which initiated a third routing message 1206. Network paging routines 1128 or application paging routines 1146, 1146'send packets to / from MN1102 and thus to first and second paging modules 1124 by updating forwarding table 1152 with fifth routing message 1210. , Redirect to / from 1126. Fifth message 1210 can be triggered by, for example, paging routine 1128 prior to sending first and / or second paging messages 1170, 1172 (A) when a request for a paging sequence is received by paging routine 1128. .. Alternatively, after sending the first and / or second paging messages 1170, 1172 (A), the fifth routing message 1210 can be triggered upon receipt of the paging response from AN1104 or MN1102. Finally, reception of the second, third, or fourth routing message 1204, 1206, or 1208 on the mobility agent module 1120 or application agent modules 1138, 1138'can trigger the fifth routing message 1210. In response, the application agent modules 1138, 1138'respond to the MN1102 or AN1104 that initiated the third routing message 1206. Network paging routines 1128 or application paging routines 1146, 1146'send packets to / from MN1102 and thus to first and second paging modules 1124 by updating forwarding table 1152 with fifth routing message 1210. , Redirect to / from 1126. Fifth message 1210 can be triggered by, for example, paging routine 1128 prior to sending first and / or second paging messages 1170, 1172 (A) when a request for a paging sequence is received by paging routine 1128. .. Alternatively, after sending the first and / or second paging messages 1170, 1172 (A), the fifth routing message 1210 can be triggered upon receipt of the paging response from AN1104 or MN1102. Finally, reception of the second, third, or fourth routing message 1204, 1206, or 1208 on the mobility agent module 1120 or application agent modules 1138, 1138'can trigger the fifth routing message 1210. In response, the application agent modules 1138, 1138'respond to the MN1102 or AN1104 that initiated the third routing message 1206. Network paging routines 1128 or application paging routines 1146, 1146'send packets to / from MN1102 and thus to first and second paging modules 1124 by updating forwarding table 1152 with fifth routing message 1210. , Redirect to / from 1126. Fifth message 1210 can be triggered by, for example, paging routine 1128 prior to sending first and / or second paging messages 1170, 1172 (A) when a request for a paging sequence is received by paging routine 1128. .. Alternatively, after sending the first and / or second paging messages 1170, 1172 (A), the fifth routing message 1210 can be triggered upon receipt of the paging response from AN1104 or MN1102. Finally, the reception of the second, third, or fourth routing message 1204, 1206, or 1208 on the mobility agent module 1120 or application agent modules 1138, 1138'can trigger the fifth routing message 1210. When this is done, it can be triggered, for example, by paging routine 1128, prior to sending the first and / or second paging messages 1170, 1172 (A). Alternatively, after sending the first and / or second paging messages 1170, 1172 (A), the fifth routing message 1210 can be triggered upon receipt of the paging response from AN1104 or MN1102. Finally, the reception of the second, third, or fourth routing message 1204, 1206, or 1208 on the mobility agent module 1120 or application agent modules 1138, 1138'can trigger the fifth routing message 1210. When this is done, it can be triggered, for example, by paging routine 1128, prior to sending the first and / or second paging messages 1170, 1172 (A). Alternatively, after sending the first and / or second paging messages 1170, 1172 (A), the fifth routing message 1210 can be triggered upon receipt of the paging response from AN1104 or MN1102. Finally, reception of the second, third, or fourth routing message 1204, 1206, or 1208 on the mobility agent module 1120 or application agent modules 1138, 1138'can trigger the fifth routing message 1210.

The sixth routing message 1212 is a location update message from the location server from MN1102 or AN1104 to update the location state 1133 of MN1102 with respect to the IP address of AN1104, or another identifier unique to each access node in the system. Sent to 1132. This allows the paging message to be sent to AN1104 when the MN1102 is unaddressable or unreachable. Paging messages can be sent directly to the address of MN1102, but can be forwarded via AN1104 if there is no route within RMA node 1110 (ie tunneling to AN1104) (instead, packets are sent to the first and second paging modules 1124. , Send to 1126). Since the location information 1133 can include an application identifier such as a SIP URI, it can reach AN1104 and then MN1102 using the application routing instead of the IP routing.

First, fourth, and fifth routing messages 1202, 1208, and 1210 (for brevity), depending on the relocation signals sent by the MN1102, or AN1104 on behalf of the MN1102. It is also possible to indirectly update the position of MN1102 by generating a sixth routing message 1212 (not shown).

Next, a specific embodiment of a processing example executed according to the method of the present invention and a flow of processing steps of FIGS. 14 to 17 showing the steps of the exemplary method 1700 will be described. Needless to say, various changes can be made to the order of steps and / or which node performs a particular step with respect to an exemplary flowchart showing one possible embodiment.

Method 1400 begins at 1402, followed by initialization step 1404. Initialization step 1404 initializes various network elements such as mobile nodes, application proxy modules, and mobility agent modules. The operation continues from step 1404 to steps 1406 and 1410, but steps 1406 and 1410 may be performed in parallel. In step 1406, the mobile node, the access node acting as the network connection point for this mobile node, and / or the paging policy server is manipulated to propagate the first paging trigger event information to the mobility agent, and in some cases further. Propagate the second paging trigger event information to the application agent. The first paging trigger event information may include, for example, other information for deciding whether to paging the mobile node based on the packet header information and / or the content of the received packet. Such network paging information usually does not include the payload of the packet, but may in some cases. The second paging information is application event paging information, as opposed to the first paging information. This information indicates one or more application events, such as the processing results of the application that should trigger the paging behavior. The application event used to trigger the paging operation is often the result of processing the payload of multiple packets containing application information or data. Examples of application events are successful download of a complete file for a particular communication application, such as a web browser, decryption of data for the downloaded file, and / or one or more for one application. Completion of calculation can be mentioned. Received in multiple packets as a complete example of a calculation that could trigger an application paging event Completion of multiple calculations corresponding to one spreadsheet using the data received, completion of scientific and technological calculations using the data received in multiple packets, and so on. A particularly useful case for such an application-triggered event is that the proxy application server processes the application until the processing is completed to some extent on the behalf of the proxy, for example, until the mobile node wants to resume direct control of the application's processing. For example, you don't want to page your mobile node until that point.

The operation proceeds from step 1406 to step 1408, in which step 1408 operates an application agent such as an MN application proxy to receive and store paging trigger event information, such as the information transmitted in step 1406. The operation is illustrated to proceed from step 1408 to step 1406, which allows the paging trigger information to be sent at multiple different points in time, such as when the desired application proxy and paging operation need to be performed. Indicates that it can be sent.

In step 1410, the mobile node is manipulated to handle one or more applications, such as a communication application for communicating with a peer node, and one or more for processing content such as the payload of packets received from the peer node. Run the application. The application to be executed is a file download application, a decoder application for decoding received data, a spreadsheet application, and / or a calculation using information and / or data received in one or more packets from a peer node. Another application is mentioned.

As part of the process of running one or more applications in step 1410, the mobile node may be launched to begin downloading files or other data from the peer node. Step 1412 illustrates such an exemplary operation. In step 1412, the mobile node's communication application begins downloading the file from the peer node and processing the information in the downloaded file. The information processed is a plurality of parts, information, or data of a download file transmitted in a plurality of packets from a peer node to a mobile node.

In step 1414, the access node, which acts as the mobile node and / or the network connection point of the mobile node, signals the application proxy to take over the processing of the application from the mobile node. The transmission of such a signal may be started, for example, by the mobile node before going to sleep, or by an access node that detects that the mobile node can no longer continue to interact with the peer node. As part of signal delivery to the application proxy, the mobile node propagates information to the application proxy about one or more application events that trigger the application to stop and / or resume processing. Further, the security association between the mobile node and the application proxy may be used to convey the shared secret, that is, the security association information for securing the communication between the peer node and the mobile node, to the application proxy. This security communication may be another shared secret used to encrypt / decrypt the information transmitted between the mobile node and the peer node. In some embodiments of the present invention, it is not necessary to notify the peer node of the transfer of the security association information to the application proxy, so that the notification is not performed. In this case, even if an end-to-end security association exists between the peer node and the mobile node, the processing handoff to the application proxy is transparent to the peer node.

The operation proceeds from step 1416 to step 1422. In step 1422, the mobile node, or access node acting as the mobile node's network connection point, sends packet filtering and redirection information to the mobile node's mobility agent. Based on this information, the mobility agent redirects the packet addressed to the destination address corresponding to the mobile node and the specific application (group) for which the application proxy has taken over the processing responsibility to the application proxy. With this information, all or part of the packet with the destination address corresponding to the mobile node may be redirected to the application proxy. However, it is possible to redirect packets for one or a few selected applications. In such a case, the processing of the plurality of different packet flows destined for the mobile node may be different, and some packet flows may be redirected to the application proxy of the mobile node and other packet flows may be subjected to other processing. Often, for example, filtering may be performed based on the packet content to determine whether the MN should be paged.

In step 1424, the mobile node is operated to put it to sleep. This is an example of the operation of the mobile node after transferring the processing responsibility of the application to the mobile node application proxy. As shown in step 1426, the sleeping mobile node periodically monitors for paging messages. Receiving a paging message may cause the mobile node to transition to a more active state, such as the on state, and resume application processing and interaction with peer nodes. The operation proceeds from step 1426 to step 1432 via the connection node 1430.

In step 1432, the mobility agent is operated to receive a packet containing a destination address corresponding to the mobile node. This is part of the normal process of packet communication between peer nodes and mobile nodes. Mobility agents typically send such packets to mobile nodes. However, according to the present invention, the mobility agent may redirect the packet to the application proxy of the mobile node. In step 1434, the mobility agent is manipulated to send information in a received packet with a destination address corresponding to a mobile node and to multiple different flows of the received packet, for example, multiple flows corresponding to different mobile node applications. Compare with the first and second packet type information for classifying into. When the received packet is the first type, the operation process proceeds from step 1434 to step 1436. In step 1436, the mobility agent compares at least a portion of the content of the received packet with the first paging trigger information to determine whether the mobile node should be paging. Assuming that the content of the packet matches the paging trigger, a match between the content of the received packet and the paging trigger is detected, so in step 1438, the mobility agent sends, for example, a paging message to the mobile node as a paging action. The paging trigger information may be updated to reflect the state of the mobile node. For example, when the mobile is in sleep mode, the reception of some packets may trigger paging, or when the mobile is active, the received packets may simply be forwarded. In step 1440, the first type of packet is forwarded to the mobile node. In step 1442, after receiving the page, the mobile node is operated to receive and process the first type packet. The operation is illustrated to go from step 1442 to step 1436,

If a second type packet is detected in step 1434, the operation proceeds to step 1444 instead of step 1436. Multiple types of packets corresponding to a plurality of different flows may be processed in parallel. In step 1444, the mobility agent redirects the second type of packet to the application proxy on the mobile node instead of the mobile node. Then, in step 1448, the application proxy receives the redirected processed packet. In the next step 1450, the application proxy is manipulated to execute the processing of the application using the contents of the payloads of the received multiple redirect packets. An application event occurs as a result of processing by this application. Application events include the completion of a file download, the completion of calculations based on data / values received in multiple packets for a particular application, and / or decryption of the downloaded file. Along with the application that executes such processing, even if you implement a communication application that monitors communication with the peer node that thinks that it is continuing the dialogue with the mobile node based on the information from the application proxy of the mobile node. Good. Examples of applications run by mobile node application proxies include spreadsheet applications, file decryption applications, and various other applications normally run by mobile nodes.

The operation proceeds from step 1450 through connection node 1452 to step 1454. In step 1454, the application proxy compares the stored paging event trigger information with one or more application events that are the result of processing the application executed in step 1450. If a match with the trigger event is detected, the operation proceeds from step 1454. In step 1454, the application comparison result is typically the result of processing the payload of multiple packets, but the application result is some information from the mobile node, such as state information indicating the status of the mobile node, before the mobile node. It can also be the result of information in a single packet that has been applied for application processing using the application result of, or some other information transmitted from the mobile node. Therefore, a combination of a single packet and some information from the mobile node may trigger paging on the mobile node.

When it is detected that the triggering requirements for a paging event have been met, the application proxy initiates the paging operation in step 1456. This may be done, for example, by sending a paging message to the mobility agent of the mobile node to initiate the paging operation. In some cases, the paging message contains a first-class packet containing information for initiating paging on the mobile node. Substep 1457 shows sending a paging message to trigger paging on a mobile node.

The operation proceeds from step 1456 to steps 1458 and 1462. In step 1458, the mobility agent is manipulated to paging the mobile node in response to receiving a paging message from the application proxy. In the next step 1460, when the mobile node is in the sleep state, the state transition of the mobile node from the sleep state to the active state is performed in response to the reception of the page message. Therefore, by the time the packet flow redirection is completed and the packet is sent to the mobile again, the mobile is sufficiently active to receive the packet and continue application processing. The operation proceeds from step 1460 to step 1470.

In step 1462, the application proxy is operated to send the application processing result and the application status information to the mobile node. This allows the mobile node to resume processing the application when the application proxy is no longer responsible for processing the application. In the next step 1464, the application proxy sends a message to the mobility agent to stop the mobility agent from redirecting packets having a destination address corresponding to the mobile node to the application proxy. This message may cause the Mobility Agent to update the packet flow filtering information to stop the redirection of Type 2 packets to the application proxy, which is often the case. The operation proceeds from step 1464 to step 1468. When the mobile node receives the application state information from the application proxy at step 1468, the operation proceeds to step 1470.

In step 1470, the mobile node receives the packet from the peer node and resumes processing of the application when the application proxy detects the processing result of the application that caused the mobile node to paging. The operation relating to the mobile exemplary processing corresponding to the communication session with the peer node is then stopped at step 1472 upon termination of a particular communication session with the peer node or otherwise completion. Although a single handoff is illustrated in the exemplary flow of FIGS. 14-17, multiple processing handoffs are possible between the mobile node and the mobile node's application proxy during a single communication session.

Next, various security features of the present invention will be described. FIG. 1300 of FIG. 13 shows the communication partner node CN1114, the mobile node MN1102, and the MNPS1140 (including the application agent module). CN1114 includes a first security association 1302, which includes a first secret 1304 and a first security routine group 1306, and a communication routine group 1308. The MN1102 includes a first security association 1328 that includes a first secret 1330 and a first security routine group 1332, a communication routine 1334, and a second that includes a second secret 1338 and a second security routine group 1340. Includes Security Association 1336 and Header and Payload Processing Routine 1342. The MNPS1140 includes a first security association 1310 containing a first secret 1312 and a first security routine group 1314, a communication routine 1316, and a second including a second secret 1320 and a second security routine group 1322. Includes Security Association 1318, Header and Payload Checking and Modifying Routine 1324, and Header and Payload Processing Routine 1326. According to one feature of the invention, the shared first secrets 1304, 1330 exist between CN1114 and MN1102 and are securely transferred by MN1102 to MNPS1140 using the second security associations 1336, 1318. Therefore, the MNPS1140 can take over the security process and packet processing on behalf of the MN1102. The security routines 1306 and 1332 may be the same as the encryption / decryption routines used by CN1114, and can be used to encode and decrypt the information transmitted between CN1114 and MN1102.

Next, three possible configurations will be described. In the first configuration, when the MN1102 receives a packet from CN1114 via the MNPS1140, the MNPS1140 performs a security check and correction of the packet header and / or payload by the header and payload checking and correction routine 1324, and then this. Packets can be forwarded to MN1102. This creates a legitimate "interventor" in the MNPS1140 that securely receives the first shared secret 1330 from the MN1102, allowing the MNPS1140 to act as such an intervener. The first shared secret 1330 received from the MN1102 is stored in the first secret 1312 of the MNPS1140. This can also be achieved if the first shared secret 1330 is used for packet authentication, packet integrity protection, and / or packet encryption. The same processing can be performed for packets from MN1102 to CN1114, and CN1114 is usually unaware of the existence of MNPS1140, which is a support node for MN1102. Discarding malicious packets claiming to be packets from / to MN1102 by processing by MNPS1140 was also transmitted to MNPS1140 by MN1102 in order to control service features such as SIP signals and resource reservations. You can also read and adjust the parameters.

In the second configuration, the MN1102 can propagate its first shared secret 1330 to the MNPS1140, allowing the MNPS1140 to securely participate in a communication session with the CN1114 as a proxy for the MN1102. Thus, the MN1102 can, for example, go to sleep or otherwise temporarily leave the communication system. Again, CN1114 is unaware of the absence of MN1102 because MNPS1140 operates on behalf of MN1102 with the same communication parameters used by MN1102 (such as IP address and security process).

In hybrid mode, the MNPS1140 can act as either an intervener or a proxy for each packet flow, and can switch between intervener mode and proxy mode in time under the control of the MN1102, so the processing by the MNPS1140 allows the intervener mode Can cause a transition from / to. Note that in proxy mode, packets resulting from proxy processing on the MNPS1140 then use the first shared secret 1330 with CN1114 (first secret 1304) and MNPS1140 (first secret 1312). Alternatively, the second security association 1318 between the MN1102 and MNPS1140 used to securely transfer the first shared secret 1330 from the MN1102 to the MNPS1140 (the second shared secret 1320 may or may not be used). ) Can be used to securely transfer to the MN1102.

Figure 13 shows the flow when the second shared secret 1320/1338 is used in the second security association 1318/1336. CN1114 is coupled to MNPS1140 by packet flow 1348. The MNPS1140 is coupled to the MN1102 by packet flow 1350. CN1114 is also coupled to MN1102 by packet flow 1344. CN1114 has a first security association 1302 with a first shared secret 1304 and a first security routine group 1306, the first security routine group 1306 as directed by the first security association 1302. , Apply the first shared secret 1304 to packets 1348 and 1344 to secure packets 1348 and 1344. The MN1102 also includes a corresponding first security association 1328, a first secret 1330, and a first set of security routines 1332, first to facilitate authentication, integrity checking, and decryption. Check security information for packets 1344 and 1350 as directed by Security Association 1328. CN1114, MN1102, and MNPS1140 further include communication routines 1308, 1334, and 1316 to facilitate the generation and reception of packet flows 1344, 1348, and 1350, respectively.

The MN1102 uses signal message 1346 because the MN1102 and MNPS1140 further include a second security association (1336, 1318), a second secret (1338, 1320), and a second security routine (1340, 1322), respectively. Then, the secret 1330 of the first security association can be safely sent to the MNPS1140. The secret 1330 is held by the first secret 1312. If the MNPS1140 has a first security association state that includes a first secret 1312 and a first security routine group 1314, packets between CN1114 and MN1102 are routed via MNPS1140 like flow 1344A. The MNPS1140 can then intercept these packets 1344A and use header and payload checking and correction routines 1324 to validate and tune the packets in the flow. These packets can then be dropped (bad packets with poor security) or forwarded to the packet's destination address, the MN1102 or CN1114 (checked and possibly tuned packets). Note that the header and payload check and modify routine 1324 extracts information from the header or payload that is used for processing such as network address translation, authorization control, or accounting and policy processes on the MNPS1140 without modifying these packets. You can also do it. In one alternative embodiment, if the packet is addressed to the MNPS1140, which acts as a proxy for the MN1102, as in Flow 1348, the MNPS1140 will use the first or second security associations 1310, 1318 to secure the packet. Forward the checked and modified packets 1350 to the MN1102 using, respectively. In addition, flow 1350 is a packet

The MN1102 and MNPS1140 further include header and payload processing routines 1342 and 1326, respectively. These routines represent the receipt of a packet and the subsequent payload processing, such as the generation of application state undertaken by the endpoint of the communication flow. The MNPS1140 header and payload processing 1326 allows the MNPS1140 to act as a proxy and issue flows from incoming flows 1348 to 1350. Flow 1348 is the same as Flow 1350 except for the source and destination addresses and the transmission period. On the other hand, the flow 1352 is a flow derived from the flow 1348 and triggered, and the number of packets, the size, the contents of the payload, etc. are different from the flow 1350, reflecting the application processing of the packet flow 1348. Again, the flow 1352 can be secured using either the first or second security associations 1310, 1318 and can be sent out when or after the flow 1348 is received by the MNPS1140. The MN1102 header and payload processing routine 1342 then receives flows 1344, 1350, and 1352, and from the source and destination addresses of the packet and the security header information, the security associations to apply and the source of the packet. After understanding, the application data from this packet flow can be safely acquired.

The method by which the MNPS1140 obtains the first security association 1328 (first secret 1330) of the MN1102 using the second security association 1318/1336 and message 1346 has already been described. Alternatively, access the three nodes CN1114, MN1102, and MNPS1140 and set the first security association (first secret) 1302 (1304), 1328 (1330), 1310 (1312) to the respective nodes 1114, 1102, 1140. During the security negotiation signal phase, which includes messages 1354 that can be deployed in a secure manner, the first security association becomes the first security association 1302 (first secret 1304) of CN1114 and the first security association of MN1102 When deployed as 1328 (1st Secret 1330), the 1st Security Association l310 (1st Secret 1312) can also be deployed to MNPS1140 at the same time.

In various embodiments described herein, a node described herein is a plurality of steps corresponding to one or more methods of the invention, such as signal processing, message generation, and / or transmission. Performed with one or more modules to perform the steps. Therefore, in some embodiments, various features of the invention are implemented with modules. Such modules may be implemented using software, hardware, or a combination of software and hardware. Many of the above methods or method steps are on machine-readable media, such as RAM, memory devices such as floppy disks, to control machines such as general purpose computers with or without additional hardware. It can be performed by implementing all or part of the above method on, for example, one or more nodes, using machine-readable instructions such as included software. Accordingly, the present invention is particularly directed to a machine-readable medium containing machine-readable instructions for causing a machine, such as a processor and associated hardware, to perform one or more steps of the above methods (s). .. The methods and devices of the present invention are applicable to a wide range of communication systems, including many OFDM, CDMA, and other non-OFDM systems.

The methods and devices of the present invention can be used for CDMA, Orthogonal Frequency Division Multiple Access (OFDM), and / or various other types of other types that can be used to provide wireless or fixed communication links between access nodes and mobile nodes. It may be used in communication techniques and is used in various embodiments. In some embodiments, the access node is implemented as a base station that uses OFDM and / or CDMA to establish a communication link with the mobile node. In various embodiments, the mobile node is a notebook computer, a personal digital assistant (PDA), or other portable device that includes a receiver / transmitter circuit and logic and / or routines for implementing the methods of the invention. Will be implemented.

Many additions and modifications to the methods and devices of the invention described above will be apparent to those skilled in the art from the above description of the invention. Such modifications are considered to be within the scope of the present invention.

<figref num="1">An exemplary access node implemented in accordance with the present invention is shown.</figref><figref num="2">Shown are exemplary endnodes implemented in accordance with the present invention.</figref><figref num="3">An exemplary Home Mobility Agent node implemented in accordance with the present invention is shown.</figref><figref num="4">An exemplary content of a visitor list state, which is an example of a state that can be included in the visitor list state illustrated in any one of FIGS. 1, 2, and 3, is shown.</figref><figref num="5">The network diagram of the exemplary communication system to which this invention is applied is shown.</figref><figref num="6">An example of signal and packet flow for the network in Figure 5 is shown.</figref><figref num="7">A second example of signal and packet flow for the network in Figure 5 is shown.</figref><figref num="8">Another example of signal and packet flow for the network in Figure 5 is shown.</figref><figref num="9">An example of the signal and packet flow of this network is shown along with a network diagram of an exemplary alternative communication system to which the present invention is applicable.</figref><figref num="10">Yet another exemplary communication system and associated signal scheme is shown.</figref><figref num="11">Shown are exemplary systems and signaling schemes used in various embodiments of the invention in which paging is supported in a system in which a mobile node proxy can perform application processing on behalf of a mobile node.</figref><figref num="12">Shown are exemplary systems and signaling schemes used in various embodiments of the invention in which paging is supported in a system in which a mobile node proxy can perform application processing on behalf of a mobile node.</figref><figref num="13">An exemplary system and security-related signal used in various embodiments of the invention that allow the peer node to maintain an end-to-end security association throughout the communication session even when application processing between the mobile node and the application proxy is handed off. Is shown.</figref><figref num="14">The processing performed according to the characteristics of the paging and application processing handoffs of the present invention in one specific embodiment is shown.</figref><figref num="15">The processing performed according to the characteristics of the paging and application processing handoffs of the present invention in one specific embodiment is shown.</figref><figref num="16">The processing performed according to the characteristics of the paging and application processing handoffs of the present invention in one specific embodiment is shown.</figref><figref num="17">The processing performed according to the characteristics of the paging and application processing handoffs of the present invention in one specific embodiment is shown.</figref>

Code description

12 Access node 14 End node 15 Home mobility agent node 203,205 Antenna 230,330,430 Bus