in fig1 , the overall architecture of the ip - based mobile system is shown with a mobile mode 125 , a home network 110 and foreign networks 130 and 150 , respectively . as shown in fig1 , the home network 110 has a home agent or local mobility anchor 113 . the local mobility anchor 113 is coupled to the mobility agent gateway 155 on foreign network 150 by communication link 112 , and local mobility anchor 113 is coupled to the mobility agent gateway 135 on foreign network 130 by communication link 115 . the mobility agent gateway 135 is coupled to the mobile node 125 through the radio access system comprised of the base station transceiver 139 coupled to the antenna / transmitter 137 through the wireless communication link 127 . the mobility agent gateway 155 is coupled the mobile node 125 using a second communication access type , such as wimax or wifi , which is supported by the interface 141 and wireless communication link 157 . fig1 also shows a connection to mobile node 125 from the foreign agent 135 through connection 176 and second access interface 177 . this interface is connected to mobile node 125 through wireless communication link 180 . in this embodiment , the communication access type supported by connection interface 177 is the same as the second communication access type supported by interface 141 . this embodiment has a limitation that multiple interfaces may be supported on the networks , but on any given foreign network ( such as network 150 or 130 ), only one interface will be supported for each communication access type . mobile node 125 is shown electronically coupled to the foreign networks 150 and 130 via the wireless communication link 157 and 127 , respectively . the mobile node 125 , however , can communicate with any transceiver or access network coupled to a foreign network . that is , communications links 127 and 157 are radio transmitted links , but these links can be composed of any connection between two or more nodes on a network or users on networks or administrative domains . the terms local mobility anchor , home agent , and foreign agent may be as defined in the mobile ip protocol ( rfc 2002 ), but these agents are not restricted to a single protocol or system . in fact , the term home agent , as used in this application , can refer to a home mobility manager , home location register , home serving entity , or any other agent at a home network 110 having the responsibility to manage mobility - related functionality for a mobile node 125 . likewise , the term mobility agent gateway , as used in this application , can refer to a foreign agent , serving mobility manager , visited location register , visiting serving entity , or any other agent on a foreign network having the responsibility to manage mobility - related functionality for a mobile node 125 . in the mobile ip communications system shown in fig1 , the mobile node 125 is identified by a permanent ip address . while the mobile node 125 is coupled to its home network 110 , the mobile node 125 receives information packets like any other fixed node on the home network 110 . when mobile , the mobile node 125 can also locate itself on foreign network , such as network 130 or 150 . when located on foreign network 130 or 150 , the home network 110 sends data communications to the mobile node 125 by “ tunneling ” the communications to the foreign network 130 or 150 . the mobile node 125 keeps the local mobility anchor 113 informed of its current location , or foreign network association , by registering a care - of address with the local mobility anchor 113 . essentially , the care - of address represents the foreign network where the mobile node 125 is currently located . if the local mobility anchor 113 receives an information packet addressed to the mobile node 125 while the mobile node 125 is located on a foreign network 130 , the local mobility anchor 113 will “ tunnel ” the information packet to foreign network 130 for subsequent transmission to mobile node 125 . the foreign agent 135 participates in informing the local mobility anchor 113 of the mobile node 125 current care - of address . the foreign agent 135 also receives information packets for the mobile node 125 after the information packets have been forwarded to the foreign agent 135 by the local mobility anchor 113 . moreover , the foreign agent 135 serves as a default router for out - going information packets generated by the mobile node 125 while connected to the foreign network 130 . the mobile node 125 participates in informing the local mobility anchor 125 of its current location and requests connections to the associated foreign network . when the mobile node 125 transitions to connecting to a different access type on the foreign network or a wholly different foreign network ( handover ), the mobile node 125 obtains appropriate information regarding the address of the foreign network and / or the foreign agent from an agent advertisement . when first connected to the local mobility anchor 113 , mobile node 125 would have created an entry on the binding cache entry table in fig2 that specified the mobile node identification for the mobile node 125 . the access type field of information is included in the proxy binding update request and the binding cache entry table in fig2 , with the mobile node identification field . fig2 is a binding cache entry table 160 that possesses at least column and row entries for the mobile node identification 165 and the access type 167 . other fields are maintained on the binding cache entry table , but these are the pertinent entries for the consideration of the present invention . because each access type on the networks shown on fig1 are limited to a single interface from each foreign network , the local mobility anchor will check subsequent proxy binding update requests received from the mobile node 125 to determine if this proxy binding update request has the same access type indicator as previously maintained on the binding cache entry table 160 for that mobile node 125 . if the same access type indicator is found in a proxy binding update request as previously maintained on the binding cache entry table 160 for that mobile node 125 , the local mobility anchor 113 will recognize the situation as a handover of the mobile node 125 to a new foreign network , such as a handover of mobile node 125 from foreign network 130 to foreign network 150 . the local mobility anchor 113 will create a new binding cache entry for the mobile node , and the care - of addressing and home network prefix will be changed to designate the new foreign network as the network where the mobile node 125 can be located , which information will be transmitted to the proper mobility access gateway 135 and the mobile node 125 . if the comparison with the information in the proxy binding update request shows a different access type connection for the mobile node 125 , the local mobility anchor will determine if the home network prefix should designate the foreign network where the mobile node 125 was previously located without any indication of a handover to a new foreign network . if that is the case , the entry for the mobile node 125 will be modified on the binding cache entry table to indicate that the mobile node 125 is still connected to the first foreign network 130 , which information will be transmitted to the proper mobility access gateway 135 and the mobile node 125 . that is , this comparison may simple show the new connection for the mobile node 125 is to a new access type , as opposed to a handover to a new foreign network . if so , the local mobility anchor 113 will respond to the proxy binding update request with a proxy binding update response having a home network prefix indicator that points to the first foreign network 130 . in this manner , a receipt of new proxy binding update request at the local mobility anchor 113 does not automatically create a new home network prefix for this mobile node , which solves some of the problems with determining when a mobile node is simply connecting to a new access type on the same network or being handed over to a new foreign network . in fig3 , the overall architecture of the ip - based mobile system is shown with a mobile mode 225 , a home network 210 and foreign networks 230 and 250 , respectively . as shown in fig3 , the home network 210 has a home agent or local mobility anchor 213 . the local mobility anchor 213 is coupled to the mobility agent gateway 255 on foreign network 250 by communication link 212 , and local mobility anchor 213 is coupled to the mobility agent gateway 235 on foreign network 230 by communication link 215 . the mobility agent gateway 235 is coupled to the mobile node 225 through the radio access system comprised of the base station transceiver 239 coupled to the antenna / transmitter 237 through the communication link 227 . the mobility agent gateway 255 is coupled to a second access type , such as wimax or wifi , through interface 241 coupled to the mobile node 225 by communication link 257 . fig3 also shows a second connection of the same access type as supported by interface 241 for the connection of the mobile node 225 to foreign agent 255 through connection 276 and second access interface 277 . this interface is connected to mobile node 225 through communication link 280 . mobile node 225 is shown electronically coupled to the foreign networks 250 and 230 via the wireless communication link 257 ( or 280 ) and 227 , respectively . the mobile node 225 , however , can communicate with any transceiver or access network coupled to a foreign network . that is , communications links 227 , 280 and 241 are radio transmitted links , but these links can be composed of any connection between two or more nodes on a network or users on networks or administrative domains . the terms local mobility anchor , home agent , and foreign agent may be as defined in the mobile ip protocol ( rfc 2002 ), but these agents are not restricted to a single protocol or system . in fact , the term home agent , as used in this application , can refer to a home mobility manager , home location register , home serving entity , or any other agent at a home network 210 having the responsibility to manage mobility - related functionality for a mobile node 225 . likewise , the term mobility agent gateway , as used in this application , can refer to a foreign agent , serving mobility manager , visited location register , visiting serving entity , or any other agent on a foreign network having the responsibility to manage mobility - related functionality for a mobile node 225 . in the mobile ip communications system shown in fig3 , the mobile node 225 is identified by a permanent ip address . while the mobile node 225 is coupled to its home network 210 , the mobile node 225 receives information packets like any other fixed node on the home network 210 . when mobile , the mobile node 225 can also locate itself on foreign network , such as network 230 or 250 . when located on foreign network 230 or 250 , the home network 210 sends data communications to the mobile node 225 by “ tunneling ” the communications to the foreign network 230 or 250 . the mobile node 225 keeps the local mobility anchor 213 informed of its current location , or foreign network association , by registering a care - of address with the local mobility anchor 213 . essentially , the care - of address represents the foreign network where the mobile node 225 is currently located . if the local mobility anchor 213 receives an information packet addressed to the mobile node 225 while the mobile node 225 is located on a foreign network 230 , the local mobility anchor 213 will “ tunnel ” the information packet to foreign network 230 for subsequent transmission to mobile node 225 . the foreign agent 235 participates in informing the local mobility anchor 213 of the mobile node 225 current care - of address . the foreign agent 235 also receives information packets for the mobile node 225 after the information packets have been forwarded to the foreign agent 235 by the local mobility anchor 213 . moreover , the foreign agent 235 serves as a default router for out - going information packets generated by the mobile node 225 while connected to the foreign network 230 . the mobile node 225 participates in informing the local mobility anchor 225 of its current location and requests connections to the associated foreign network . when the mobile node 225 transitions to connecting to foreign network 250 , the mobile node 225 obtains appropriate information regarding the address of the foreign network 250 and / or the foreign agent 255 from an agent advertisement . when first connected to the local mobility anchor 213 , mobile node 225 would have created an entry on the binding cache entry table in fig2 that specified the mobile node identification for the first access type . the access type field of information is included in this binding cache entry table in fig2 , with the mobile node identification field . fig2 is a binding cache entry table 260 that possesses at least column and row entries for the mobile node identification 265 and the access type 267 . in the system shown on fig3 , multiple access types on a single foreign network 250 are supported by multiple interfaces , such as interface 241 and 277 . because the correspondence of the same access type on the binding cache entry table of fig2 may not indicate an inherent handover to a different foreign network from the prior connected foreign network , the proxy binding update request will include a handover indicator for the analysis by the local mobility anchor 213 . the handover indicator would include a new field in the transmission packet that would indicate a handover to the same access type on the same foreign network or a handover to a new foreign network . this information could also be indicated by a flag or other indicator to show the type of handover that will be initiated , e . g . flag “ 1 ” equals handover to same access type on same foreign network , flag “ 0 ” equals handover to different foreign network . the new field could also indicate if the handover status is unknown , or this is an initial request for a proxy binding update request . other fields can be maintained on the binding cache entry table , and the transmission packets may be expanded to accommodate the new access type field of information . the local mobility anchor 213 will check subsequent proxy binding update requests received from the mobile node 225 to determine the handover indicator status . if the handover indicator indicates that the mobile node is being connected to a different foreign network , the local mobility anchor 113 will initiate a protocol for a handover of the mobile node 225 to a new foreign network , such as a handover of mobile node 225 from foreign network 250 to foreign network 230 . the local mobility anchor 213 will create a new binding cache entry for the mobile node , and the care - of addressing and home network prefix will be changed to designate the new foreign network as the network where the mobile node 225 can be located , which information will be transmitted to the proper mobility access gateway 235 and the mobile node 225 . if the handover indicator indicates that a handover is being requested to different access type connection for the mobile node 225 on the same foreign network 250 , the local mobility anchor 213 will initiate a protocol for designating a home network prefix for the foreign network 250 where the mobile node 225 was previously located without any indication of a handover to a new foreign network . if that is the case , the entry for the mobile node 225 will be modified on the binding cache entry table to indicate that the mobile node 225 is still connected to the first foreign network 250 , which information will be transmitted to the proper mobility access gateway 235 and the mobile node 225 . that is , this handover indicator may simply show the new connection for the mobile node 225 is to a new interface for the same access type on the same foreign network 250 , as opposed to a handover to a new foreign network . if so , the local mobility anchor 213 will respond to the proxy binding update request with a proxy binding update response having a home network prefix indicator that points to the first foreign network 250 . in this manner , a receipt of new proxy binding update request at the local mobility anchor 213 does not automatically create a new home network prefix for this mobile node , which solves some of the problems with determining whether a handover of the mobile node care - of addressing is necessary and whether it is necessary to designate a new foreign network or the same foreign network for this care - of addressing for the mobile node . as an alternative embodiment that is covered by the scope of the invention , when first connected to the local mobility anchor 213 , mobile node 225 would have created an entry on the binding cache entry table in fig4 that specified the mobile node identification for the first access type and interface identification information . the access type field of information is included in this binding cache entry table in fig4 , with the mobile node identification field , and the interface identification information in column 269 would have indicated the specific interface information for interface 241 or 277 . fig2 is a binding cache entry table 260 that possesses at least column and row entries for the mobile node identification 265 , the access type 267 , and the interface 269 . in the system shown on fig3 , multiple access types on a single foreign network 250 are supported by multiple interfaces , such as interface 241 and 277 . because the correspondence of the same access type on the binding cache entry table of fig4 would include additional information that the local mobility anchor would use to analyze whether the proxy binding update request relates to a handover to a different foreign network 230 from the prior connected foreign network 250 or a handover to a different interface for the same access type on the same foreign network 250 . in addition to the access type information and the handover indicator described above , the proxy binding update request would include a new field in the transmission packet that would identify the interface that will be used to connect the mobile node to the foreign network . the new field could also indicate if the interface identification is unknown . other fields can be maintained on the binding cache entry table , and the transmission packets may be expanded to accommodate the new access type field of information . the local mobility anchor 213 will check subsequent proxy binding update requests received from the mobile node 225 to determine the handover indicator status . if the access type , handover indicator and interface identification information indicates that the mobile node is being connected to a different foreign network , the local mobility anchor 113 will initiate a protocol for a handover of the mobile node 225 to a new foreign network , such as a handover of mobile node 225 from foreign network 250 to foreign network 230 . the local mobility anchor 213 will create a new binding cache entry for the mobile node , and the care - of addressing and home network prefix will be changed to designate the new foreign network as the network where the mobile node 225 can be located , which information will be transmitted to the proper mobility access gateway 235 and the mobile node 225 . if the access type , handover indicator , and interface identification information indicates that a handover is being requested to different access type connection for the mobile node 225 on the same foreign network 250 , the local mobility anchor 213 will initiate a protocol for designating a home network prefix for the foreign network 250 where the mobile node 225 was previously located without any indication of a handover to a new foreign network . if that is the case , the entry for the mobile node 225 will be modified on the binding cache entry table to indicate that the mobile node 225 is still connected to the first foreign network 250 , which information will be transmitted to the proper mobility access gateway 235 and the mobile node 225 . that is , the access type , handover indicator , and interface information may simply show the new connection for the mobile node 225 is to a new interface for the same access type on the same foreign network 250 , as opposed to a handover to a new foreign network . if so , the local mobility anchor 213 will respond to the proxy binding update request with a proxy binding update response having a home network prefix indicator that points to the first foreign network 250 . in this manner , a receipt of new proxy binding update request at the local mobility anchor 213 does not automatically create a new home network prefix for this mobile node , which solves some of the problems with determining whether a handover of the mobile node care - of addressing is necessary and whether it is necessary to designate a new foreign network or the same foreign network for this care - of addressing for the mobile node . while preferred embodiments of the invention have been shown and described , modifications thereof can be made by one skilled in the art without departing from the spirit and teachings of the invention . the embodiments described herein are exemplary only , and are not intended to be limiting . many variations and modifications of the invention disclosed herein are possible and are within the scope of the invention .