US20020055971A1 - Method and system for a low-overhead mobility management protocol in the internet protocol layer - Google Patents
Method and system for a low-overhead mobility management protocol in the internet protocol layer Download PDFInfo
- Publication number
- US20020055971A1 US20020055971A1 US10/026,060 US2606001A US2002055971A1 US 20020055971 A1 US20020055971 A1 US 20020055971A1 US 2606001 A US2606001 A US 2606001A US 2002055971 A1 US2002055971 A1 US 2002055971A1
- Authority
- US
- United States
- Prior art keywords
- host
- nat
- network
- home
- address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 11
- 230000027455 binding Effects 0.000 claims abstract description 66
- 238000009739 binding Methods 0.000 claims abstract description 66
- 238000004891 communication Methods 0.000 claims abstract description 35
- 238000013519 translation Methods 0.000 claims abstract description 11
- 230000008859 change Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013479 data entry Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/00835—Determination of neighbour cell lists
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
-
- C—CHEMISTRY; METALLURGY
- C07—ORGANIC CHEMISTRY
- C07C—ACYCLIC OR CARBOCYCLIC COMPOUNDS
- C07C43/00—Ethers; Compounds having groups, groups or groups
- C07C43/30—Compounds having groups
- C07C43/313—Compounds having groups containing halogen
-
- C—CHEMISTRY; METALLURGY
- C07—ORGANIC CHEMISTRY
- C07C—ACYCLIC OR CARBOCYCLIC COMPOUNDS
- C07C69/00—Esters of carboxylic acids; Esters of carbonic or haloformic acids
- C07C69/62—Halogen-containing esters
- C07C69/63—Halogen-containing esters of saturated acids
-
- C—CHEMISTRY; METALLURGY
- C07—ORGANIC CHEMISTRY
- C07D—HETEROCYCLIC COMPOUNDS
- C07D307/00—Heterocyclic compounds containing five-membered rings having one oxygen atom as the only ring hetero atom
- C07D307/77—Heterocyclic compounds containing five-membered rings having one oxygen atom as the only ring hetero atom ortho- or peri-condensed with carbocyclic rings or ring systems
- C07D307/78—Benzo [b] furans; Hydrogenated benzo [b] furans
- C07D307/79—Benzo [b] furans; Hydrogenated benzo [b] furans with only hydrogen atoms, hydrocarbon or substituted hydrocarbon radicals, directly attached to carbon atoms of the hetero ring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/26—Route discovery packet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2521—Translation architectures other than single NAT servers
- H04L61/2535—Multiple local networks, e.g. resolving potential IP address conflicts
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/255—Maintenance or indexing of mapping tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
- H04W40/36—Modification of an existing route due to handover
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/105—PBS [Private Base Station] network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/005—Data network PoA devices
Definitions
- the present invention relates to a system and method of mobile Internet communication. Specifically the present invention relates to managing the mobility of Mobile Nodes (MNs) within multiple administrative domains employing Network Address Translation enabled routers (NATs) for Internet communications.
- MNs Mobile Nodes
- NATs Network Address Translation enabled routers
- NATs Network Address Translation enabled routers
- IANA Internet Address Numbers Authority
- MNs Mobile Nodes
- a system and method for supporting mobile Internet communication has a plurality of networks.
- Each network has a Network Address Translation router (NAT) with a unique global address, at least one Host associated with the NAT and at least one Mobile Node (MN).
- NAT Network Address Translation router
- MN Mobile Node
- the Mobile Nodes (MNs) communicate within the system via the Hosts.
- Each Host is associated with one NAT and has a service area in which it can communicate data to the MNs.
- Each MN has a home Host within a home network which defines a default local address which is paired with the global address of the home network's NAT to define a default binding of the MN.
- the invention provides the NAT of each network with an associated Mobile-Home Database (MHD) which identifies each MN, which has the network as its home network, with a) a local address of a current association of the MN with a Host within the network or b) a binding defined by a local address of an association of the MN with a Host within a different network and the global address of the different network's NAT.
- MHD Mobile-Home Database
- Each network's NAT's MHD also identifies each visiting MN, i.e. an MN which is currently associated with a Host associated with the NAT, but has a different home network, with a local address of the current Host association of the MN.
- Each MN can be moved from a location where the MN communicates data via a first associated Host within a first network having a first NAT to a location within the service area of a second Host within the first network to communicate data via the second Host.
- MN communication via the second host is enabled by communicating to the MHB of the first NAT a local address reflecting the MN's association with the second Host.
- Each MN can also be moved from a location where the MN communicates data via the first associated Host within the first network to a location within the access range of a third Host within a different second network having a second NAT to communicate data via the third Host.
- MN communication via the third Host is enabled by communicating to the MHB of the second NAT a local address reflecting the MN's association with the third Host.
- the MN also communicates to the MHB of the MN's home network's NAT a binding including a new local address reflecting the MN's association with the third Host and the global address of the second NAT.
- the system enables a data communication from a corresponding node (CN) to a selected MN to be communicated to the selected MN by establishing a binding based on the MN's default binding or the binding reflected in the MHB of the MN's home network's NAT.
- the NAT with which the binding is established directs the communication to the local address identified in its MHB for the MN.
- a preferred the system includes at least one network associated with a plurality of Hosts and at least one Host which is the home Host for a plurality of MNs. Nodes that are not mobile may also be associated with the Hosts within the system. These nodes can be identified in the Host's network's MHD or the network's NAT can be configured to bypass the MHD for communications directed to non-mobile nodes.
- the NAT's MHD of each network identifies 24 bit local and global addresses and a location field.
- Each MN which has the network as its home network, is identified in the NAT's MHD with a) a local address of a current association of the MN with a Host within the network, a null global address, and a home flag in the location field or b) a binding defined by a local address of an association of the MN with a Host in a different network and a global address of the different network's NAT and an away flag in the location field.
- Each visiting MN is preferably identified in the visited network's NAT's MHD with a local address of the current Host association of the MN, a null global address, and a home flag in the location field.
- a binding is established between a source/corresponding node (CN) and an MN based on the binding reflected in the MHD of the MN's home network's NAT when the corresponding location field has an away flag.
- CN source/corresponding node
- the present invention can be used to implement an Internet architecture consisting of a large number private networks, individually connected to the Internet backbone via NATs. Hosts within the same private network can communicate with one another, and also with external Hosts via the Internet backbone.
- the routers in each private network maintain their own local routes and routers in the backbone maintain their own external routes. More specifically, the routers within a particular domain are not cognizant of routes outside that domain. Likewise, the backbone (public) routers are not cognizant of the routes to any local addresses.
- FIG. 1 is a schematic diagram of an architecture and topology of a mobile network associated with the Internet.
- FIG. 2 is a diagram of a conventional Internet communication binding.
- FIG. 3 illustrates a portion of a Mobile-Home Database (MHD) of one of the Network Address Translation Routers (NATs) illustrated in FIG. 1 in accordance with the teachings of the present invention.
- MHD Mobile-Home Database
- FIG. 4 illustrates a portion of a Mobile-Home Database (MHD) of one of the Network Address Translation Routers (NATs) illustrated in FIG. 1 in accordance with the teachings of the present invention.
- MHD Mobile-Home Database
- private networks 10 , 12 , 20 are connected to an external Internet backbone via Network Address Translation enabled routers (NATs).
- NATs Network Address Translation enabled routers
- large number of private networks can be connected to the external Internet backbone.
- Hosts within different private networks can communicate with each other via the backbone, using the NAT registered addresses assigned by IANA.
- Hosts within the same private network can communicate with each other using one of the unregistered addresses.
- the registered addresses are globally unique, while unregistered addresses have local significance only.
- the local addresses and the global addresses are mutually exclusive and are conventionally 24 bits each.
- networks 10 , 12 and 20 are connected to the Internet via NAT enabled routers NAT-A, NAT-B and NAT-N, respectively.
- NAT-A, NAT-B and NAT-N are each assigned a unique Global Address by IANA.
- Nodes within each private network 10 , 12 , 20 are assigned local address based upon the Host to which the node is connected.
- node MN 0,A0 is illustrated as connected to the private network 10 via Host A0 , so the local address of node MN 0,A0 at Host A0 is a 24 bit code which indicates this connection.
- the global address of a NAT is identified by the NAT name and the local address indicating a connection between a particular node MN X and a Host X is represented as MN X @Host X .
- a conventional NAT table is set up.
- the node initiating contact is referred to as a corresponding node (CN).
- the first set of actions is to establish a binding by the NATs for the networks to which the nodes are currently connected.
- the conventional process is described by the Internet Engineering Task Forces (IETF) Request for Comments (RFCs) 1631 and 3032.
- IP Internet Protocol
- FIG. 2 illustrates the format the conventional binding table established between the CN and the receiving node.
- the bindings are made up of the nodes' global and local address combinations.
- node MN 0,A0 in network 10 as CN may communicate node MN 0,B0 in network 20 .
- the binding data is the combined Global Address NAT-A and the local address MN 0,A0 @Host A0 .
- node MN 0,B0 the binding data is the combined Global Address NAT-B and local address MN 0,B0 @Host B0 .
- the procedure for sending out a data packet from node MN 0,A0 to node MN 0,B0 is as follows.
- the packet is encoded with the global address NAT-A as the source address and the global address NAT-B as the destination address is sent from the source node MN 0,A0 .
- the receiving NAT, NAT-B in this example, checks the binding in its table, and retrieves the local address of the receiving node's Host, Host 0B in this example.
- the packet is then forwarded to that Host through which it is received by the node MN 0,B0 .
- its binding data represents a permanent address to which any CN may send data under the conventional binding system and protocols.
- mobile nodes MN may change location so that simply addressing data to a prior known address does not assure delivery without some system to accommodate connection changes by the MN.
- FIGS. 3 and 4 illustrate the architecture used to implement a micro-mobility protocol between the private networks shown.
- the architecture includes an entity called a Mobile-Home Database (MHD) associated with each NAT. This is a large directory, tightly coupled to each NAT, for keeping track of the MNs within the private network. It also indicates when the MN has moved to a foreign network (FN).
- MHD Mobile-Home Database
- the MHD for each NAT preferably includes an index field for each mobile node, a home/away flag field indicating whether a mobile node is associated with the NAT, a local address or care of address (COA) field and a NAT address field.
- Each MN has a home Host in a home network which defines a Home Address (HA) which is analogous to the permanent local address of a non-mobile node in that it is the address that a CN will use to contact the MN.
- HA Home Address
- the default binding for an MN is a combination of the global address of the MN's home network's NAT and the MN's home address. If at home, the MN's default binding will be used to establish a NAT/NAT connection for the CN/MN communication.
- One convenient way to identify the mobile nodes is using their default or home address (HA), so the index field of a network's NAT's MHD preferably lists the HAs of all of the MNs whose home network is that network to identify the data record for each MN.
- HA home address
- the flag field represents a logical field, preferably having a value 0 or a value 1 to represent a home or an away status with respect to the network.
- 0 is used to indicate that the MN has a connection with a Host in the network
- 1 is used to indicate that the MN has a connection with a different network.
- the local address field (COA) is used to indicate to which Host the MN is currently connected.
- the local address field entry is a Host associated with a foreign network
- the global address field contains the global address of that foreign network's NAT. In such case the flag field is set to 1.
- the flag field is 0, the global address value is not needed since the relevant global address is that of the MHB's NAT.
- FIGS. 3 and 4 illustrate various example records for the MHDs of NAT-B and NAT-N of the networks 12 and 20 , respectively, at a given point in time as illustrated in FIG. 1.
- a MN is in communication with its home Host, as illustrated with respect to mobile nodes MN 0,B0 , MN B1 and MN 0,NK , the associated flag field is set to 0 and the local or COA field entry is the same as the home address. No NAT address information is required.
- the MHD of the MN's home network's NAT has data entries for the flag field as 0 and the local address (COA) as the current association of the MN with its non-home Host.
- COA local address
- mobile node MN 1,B0 has a home host Host B0 , but is illustrated in FIG. 1 as connected to host Host B1 .
- the MN is identified in the index field by its HA, MN 1,B0 @HoSt B0 , has 0 in the flag field and has MN 1,B0 @Host B1 as the COA as set forth in FIG. 3.
- the NAT address field information is not needed since the global address remains the same because Host B1 and Host B0 are associated with the same network with the associated global address, namely NAT-B.
- a MN from one network connects with a host of a different network
- the MN is registered in that network's NAT with a visiting address.
- node MN i,Nk has as its home host Host Nk in network 20 which communicates with the Internet via NAT-N.
- node MN i,Nk is illustrated as visiting network 12 in connection with Host B1 which is associated with NAT-B.
- mobile node MN i,Nk is assigned a visiting address VA represented as MN i,Nk @Host B1 in the MHD of NAT-B with a flag field 0 indicating its communication with the Internet through NAT-B and a local address of
- the mobile node such as MN i,Nk
- a communication is sent to the NAT of its home network, in this case, NAT-N, to enable efficient redirection of communications.
- the communication to the MNs home network's NAT changes the NAT's MHD data with respect to the listing for the MN by setting the flag field to 1 and providing binding data for further Internet communications.
- the binding data is comprised of the assigned visiting address VA and the global address of the NAT of the network which the MN is visiting.
- the MHD of NAT-N in FIG. 4 reflects a flag value of 1, a local address of MN i,Nk @Host B1 and a NAT address of NAT-B.
- a corresponding node attempting to communicate with mobile Node MN i,Nk will not be able to establish a binding with NAT-N since the flag in NAT-N's MHD is set to 1.
- the binding is established with the binding represented by the local address and NAT address fields for MN i,Nk 's entry in NAT-N's MHD. Communication is then conducted establishing a binding with the foreign NAT, in the example NAT-B.
- the visiting MN So long as the visiting MN does not establish an association with a Host of a different network, it will preferably retain its visiting address VA identification in the MHD of the NAT whose network is visiting, which VA will be also reflected in the MHD of the mobile node's home network's NAT.
- the visiting mobile node If the visiting mobile node establishes an association with another Host within the same network that it is visiting, it will retain its same VA identification in the MHD of the NAT which is visiting, but will be provided with a new local address. That new local address will be stored in the visiting MN's MHD record's COA field and the visited network's NAT will direct communications to the MN based on that COA data. No change is required in the MN's home network's NAT's MHD in such case.
- the hosts will periodically determine whether a connection is still established with a visiting MN. If the visited host determines that the MN has disconnected and the MN has not established a connection with another host, the visited host can communicate this fact to its associated NAT which will change the COA for the visiting MN's entry to a null data state.
- An example of this is the entry for visiting node MN h,Pq in FIG. 3. That entry indicates that MN h,Pq had connected with foreign Host B1 , but is no longer connected to network 12 . Thus, no connection of MN h,Pq is illustrated with any Host in FIG. 1.
- Such an entry will also indicate to a CN that the MN has not established a connection with another host, since the CN will only contact network 12 via the VA of MN h,Pq , namely MN h,Pq @Host B1 , if MN h,Pq 's home network's NAT's MHD record has not been updated. If a CN attempts to communicate with the visiting node at that time and is referred to the visited network's NAT by the MN's home Host's NAT, a binding will not be established and the communication will fail.
- a MN's home network's NAT When a MN's home network's NAT receives a communication to change the binding information for the MN from one foreign NAT to another, it preferably sends a message to the first foreign NAT reflecting the the MN is no longer visiting that NAT's network, so that the visiting node record can be deleted from the first foreign NAT's MHD. Such a message is preferably also sent, when a MN returns to its home network after visiting other networks.
- the CN never needs to know the current location of the MN.
- the CN only needs to be aware of the static, default binding based on a MN's home address (HA) and home network's global address. This arrangement saves the flurry of registration messages from being sent over the global Internet.
- HA home address
- the tight coupling of the MHDs to the NATs means that an IP data packet does not have to travel first to the home network.
- the packet can be tunneled directly to the foreign network where the MN is located. This avoids the infamous triangle routing problem.
- the micro-mobility protocol for MNs roaming across multiple foreign networks starts with the CN's NAT trying to establish a binding with the MN's home network's NAT.
- the process fails, when the status-bit in the MN's home network's NAT's MHD is a 1. This indicates that the MN is not currently in its home network (HN); it is in a FN.
- the FN has assigned a VA to the MN which is stored in the MN's home network's NAT's MHD along with the static global address of the FN. That binding data is sent back to the CN's NAT and the CN's NAT then establishes binding with the FN's NAT.
- the rest of the protocol then proceeds the same way as if the MN were connected with a host in its home network.
- the entries for the MN in the MHD of FN 1 are preferably set 0, NULL, NULL when the MN loses contact with the FN 1 .
- the MN then moves to the different FN 2 , it communicates with FN 2 via a host, Host 2 , associated with the NAT of FN 2 , NAT-FN 2 .
- the MN is assigned a VA of MN@Host 2 such that the entries for that VA in the MHD of NAT-FN 2 are set to 0, MN@Host 2 , NULL.
- the binding data (MN@Host 2 , NAT-FN 2 ) is sent to the MN's home network's NAT and the CN's NAT. A new binding is established between the CN's NAT and NAT-FN 2 . The rest of the protocol then proceeds as described above.
- a MN moves from a foreign network FN 1 to back to its home network HN
- the entry for the MN in the MHD of the NAT of FN 1 is preferably set 0, NULL, NULL when the MN loses contact with the FN 1 .
- the MN then moves to its HN, it communicates with its HN via a host, Host HN , associated with its HN's NAT, NAT-HN.
- Host HN may or may not be the MN's home host, Host Home .
- the MN already has a data record for its HA of MN@Host Home .
- That record is preferably then changed to set the associated data fields to 0, MN@Host HN , NULL.
- the binding data (MN@Host Home , NAT-HN) is sent to the CN's NAT. A new binding is established between the CN's NAT and NAT-HN. The rest of the protocol then proceeds as described above.
- the CN's NAT in the above cases would normally be the CN's home network's NAT. However, if the CN is a MN which is visiting a FN, the CN's NAT is the NAT of the FN being visited.
Abstract
A system and method for supporting mobile Internet communication is provided which employs a Mobile-Home Database (MHD) for Network Address Translation routers (NATs). A plurality of Mobile Nodes (MNs), each having a home network, communicate within the system via a plurality of Hosts. Each Host is associated with a NAT such that each NAT is associated with one network, but one or more Hosts. Each network's NAT's MHD identifies each network's home MNs, with a) a local address of a current association of the MN with a Host within the network or b) a binding defined by a local address of an association of the MN with a Host in a foreign network and the global address of the NAT of the foreign network. Each network's NAT's MHD also identifies each visiting MN with a local address of a current Host association of the MN.
Description
- This application claims priority from U.S. Provisional Patent Application Ser. No. 60/270,190, filed Feb. 21, 2001; U.S. Provisional Patent Application Ser. No. 60/270,767, filed Feb. 22, 2001; U.S. Provisional Patent Application Ser. No. 60/296,168, filed Jun. 6, 2001; U.S. Provisional Patent Application Ser. No. 60/293,847, filed May 25,2001; U.S. Provisional Patent Application Ser. No. 60/309,046, filed Jul. 31, 2001 and U.S. patent application Ser. No. 09/997,992, filed Nov. 30, 2001.
- The present invention relates to a system and method of mobile Internet communication. Specifically the present invention relates to managing the mobility of Mobile Nodes (MNs) within multiple administrative domains employing Network Address Translation enabled routers (NATs) for Internet communications.
- Network Address Translation enabled routers (NATs) are used for connecting private networks to the Internet. As illustrated in FIG. 2, conventional Internet communications are conducted by establishing 48 bit bindings between NATs which identify nodes which are communicating with each other. The address space is divided into a set of registered 24 bit global addresses and a set of unregistered 24 bit local addresses by the Internet Address Numbers Authority (IANA). Private networks can use any address from the unregistered address space. The public or global addresses are registered and one address from this pool is assigned to each NAT.
- The inventor has recognized that it would be desirable to modify the traditional Network Address Translation functions to handle the cases where Mobile Nodes (MNs) are allowed to migrate within their own private networks and where MNs are allowed to migrate from one private network to another.
- A system and method for supporting mobile Internet communication is provided which has a plurality of networks. Each network has a Network Address Translation router (NAT) with a unique global address, at least one Host associated with the NAT and at least one Mobile Node (MN). The Mobile Nodes (MNs) communicate within the system via the Hosts.
- Each Host is associated with one NAT and has a service area in which it can communicate data to the MNs. Each MN has a home Host within a home network which defines a default local address which is paired with the global address of the home network's NAT to define a default binding of the MN.
- The invention provides the NAT of each network with an associated Mobile-Home Database (MHD) which identifies each MN, which has the network as its home network, with a) a local address of a current association of the MN with a Host within the network or b) a binding defined by a local address of an association of the MN with a Host within a different network and the global address of the different network's NAT. Each network's NAT's MHD also identifies each visiting MN, i.e. an MN which is currently associated with a Host associated with the NAT, but has a different home network, with a local address of the current Host association of the MN.
- Each MN can be moved from a location where the MN communicates data via a first associated Host within a first network having a first NAT to a location within the service area of a second Host within the first network to communicate data via the second Host. MN communication via the second host is enabled by communicating to the MHB of the first NAT a local address reflecting the MN's association with the second Host.
- Each MN can also be moved from a location where the MN communicates data via the first associated Host within the first network to a location within the access range of a third Host within a different second network having a second NAT to communicate data via the third Host. MN communication via the third Host is enabled by communicating to the MHB of the second NAT a local address reflecting the MN's association with the third Host. Where the second network is not the MN's home network, the MN also communicates to the MHB of the MN's home network's NAT a binding including a new local address reflecting the MN's association with the third Host and the global address of the second NAT.
- The system enables a data communication from a corresponding node (CN) to a selected MN to be communicated to the selected MN by establishing a binding based on the MN's default binding or the binding reflected in the MHB of the MN's home network's NAT. The NAT with which the binding is established directs the communication to the local address identified in its MHB for the MN.
- A preferred the system includes at least one network associated with a plurality of Hosts and at least one Host which is the home Host for a plurality of MNs. Nodes that are not mobile may also be associated with the Hosts within the system. These nodes can be identified in the Host's network's MHD or the network's NAT can be configured to bypass the MHD for communications directed to non-mobile nodes.
- Preferably, the NAT's MHD of each network identifies 24 bit local and global addresses and a location field. Each MN, which has the network as its home network, is identified in the NAT's MHD with a) a local address of a current association of the MN with a Host within the network, a null global address, and a home flag in the location field or b) a binding defined by a local address of an association of the MN with a Host in a different network and a global address of the different network's NAT and an away flag in the location field. Each visiting MN is preferably identified in the visited network's NAT's MHD with a local address of the current Host association of the MN, a null global address, and a home flag in the location field. A binding is established between a source/corresponding node (CN) and an MN based on the binding reflected in the MHD of the MN's home network's NAT when the corresponding location field has an away flag.
- The present invention can be used to implement an Internet architecture consisting of a large number private networks, individually connected to the Internet backbone via NATs. Hosts within the same private network can communicate with one another, and also with external Hosts via the Internet backbone. The routers in each private network maintain their own local routes and routers in the backbone maintain their own external routes. More specifically, the routers within a particular domain are not cognizant of routes outside that domain. Likewise, the backbone (public) routers are not cognizant of the routes to any local addresses.
- Other objects and advantages of the system and method will become apparent to those skilled in the art from the following detailed description of the invention.
- FIG. 1 is a schematic diagram of an architecture and topology of a mobile network associated with the Internet.
- FIG. 2 is a diagram of a conventional Internet communication binding.
- FIG. 3 illustrates a portion of a Mobile-Home Database (MHD) of one of the Network Address Translation Routers (NATs) illustrated in FIG. 1 in accordance with the teachings of the present invention.
- FIG. 4 illustrates a portion of a Mobile-Home Database (MHD) of one of the Network Address Translation Routers (NATs) illustrated in FIG. 1 in accordance with the teachings of the present invention.
- As illustrated in FIG. 1,
private networks - For example,
networks private network private network 10 via HostA0, so the local address of node MN0,A0 at HostA0 is a 24 bit code which indicates this connection. For convenience, in FIGS. 3 and 4, the global address of a NAT is identified by the NAT name and the local address indicating a connection between a particular node MNX and a HostX is represented as MNX@HostX. - If a communication and/or data packet is to be sent from a node in one network to a node in another network, before data transfer can take place, a conventional NAT table is set up. By convention the node initiating contact is referred to as a corresponding node (CN). For node to node communication, the first set of actions is to establish a binding by the NATs for the networks to which the nodes are currently connected. The conventional process is described by the Internet Engineering Task Forces (IETF) Request for Comments (RFCs) 1631 and 3032. When a binding is established, an Internet Protocol (IP) data packet can be sent by the corresponding node (CN) which traverses the global Internet and reaches NAT of the receiving node based on the binding established
- FIG. 2 illustrates the format the conventional binding table established between the CN and the receiving node. The bindings are made up of the nodes' global and local address combinations. For example, node MN0,A0 in
network 10 as CN may communicate node MN0,B0 innetwork 20. For node MN0,A0 the binding data is the combined Global Address NAT-A and the local address MN0,A0@HostA0. For node MN0,B0, the binding data is the combined Global Address NAT-B and local address MN0,B0@HostB0. - The procedure for sending out a data packet from node MN0,A0 to node MN0,B0 is as follows. The packet is encoded with the global address NAT-A as the source address and the global address NAT-B as the destination address is sent from the source node MN0,A0. The receiving NAT, NAT-B in this example, checks the binding in its table, and retrieves the local address of the receiving node's Host, Host0B in this example. The packet is then forwarded to that Host through which it is received by the node MN0,B0. Where a node is not mobile, its binding data represents a permanent address to which any CN may send data under the conventional binding system and protocols. However, mobile nodes MN may change location so that simply addressing data to a prior known address does not assure delivery without some system to accommodate connection changes by the MN.
- FIGS. 3 and 4 illustrate the architecture used to implement a micro-mobility protocol between the private networks shown. The architecture includes an entity called a Mobile-Home Database (MHD) associated with each NAT. This is a large directory, tightly coupled to each NAT, for keeping track of the MNs within the private network. It also indicates when the MN has moved to a foreign network (FN).
- The MHD for each NAT preferably includes an index field for each mobile node, a home/away flag field indicating whether a mobile node is associated with the NAT, a local address or care of address (COA) field and a NAT address field. Each MN has a home Host in a home network which defines a Home Address (HA) which is analogous to the permanent local address of a non-mobile node in that it is the address that a CN will use to contact the MN. The default binding for an MN is a combination of the global address of the MN's home network's NAT and the MN's home address. If at home, the MN's default binding will be used to establish a NAT/NAT connection for the CN/MN communication.
- All of the MNs whose home Host is associated with a particular NAT, i.e. the home network's NAT, have data records in that NAT's MHD. One convenient way to identify the mobile nodes is using their default or home address (HA), so the index field of a network's NAT's MHD preferably lists the HAs of all of the MNs whose home network is that network to identify the data record for each MN.
- The flag field represents a logical field, preferably having a
value 0 or avalue 1 to represent a home or an away status with respect to the network. In the present example, 0 is used to indicate that the MN has a connection with a Host in the network and 1 is used to indicate that the MN has a connection with a different network. The local address field (COA) is used to indicate to which Host the MN is currently connected. Where the local address field entry is a Host associated with a foreign network, the global address field contains the global address of that foreign network's NAT. In such case the flag field is set to 1. When the flag field is 0, the global address value is not needed since the relevant global address is that of the MHB's NAT. - FIGS. 3 and 4 illustrate various example records for the MHDs of NAT-B and NAT-N of the
networks - Where a MN is in communication with its home Host, as illustrated with respect to mobile nodes MN0,B0, MNB1 and MN0,NK, the associated flag field is set to 0 and the local or COA field entry is the same as the home address. No NAT address information is required.
- For MNs which are associated with a Host which is not the MN's home Host, but is a Host in the MN's home network, the MHD of the MN's home network's NAT has data entries for the flag field as 0 and the local address (COA) as the current association of the MN with its non-home Host. For example, mobile node MN1,B0 has a home host HostB0, but is illustrated in FIG. 1 as connected to host HostB1. The MN is identified in the index field by its HA, MN1,B0@HoStB0, has 0 in the flag field and has MN1,B0@HostB1 as the COA as set forth in FIG. 3. The NAT address field information is not needed since the global address remains the same because HostB1 and HostB0 are associated with the same network with the associated global address, namely NAT-B.
- Where a MN from one network connects with a host of a different network, the MN is registered in that network's NAT with a visiting address. For example, node MNi,Nk has as its home host HostNk in
network 20 which communicates with the Internet via NAT-N. In FIG. 1, node MNi,Nk is illustrated as visitingnetwork 12 in connection with HostB1 which is associated with NAT-B. Accordingly, mobile node MNi,Nk is assigned a visiting address VA represented as MNi,Nk@HostB1 in the MHD of NAT-B with aflag field 0 indicating its communication with the Internet through NAT-B and a local address of - When the mobile node, such as MNi,Nk, first initiates communication with the foreign network, for example,
network 12, a communication is sent to the NAT of its home network, in this case, NAT-N, to enable efficient redirection of communications. The communication to the MNs home network's NAT changes the NAT's MHD data with respect to the listing for the MN by setting the flag field to 1 and providing binding data for further Internet communications. The binding data is comprised of the assigned visiting address VA and the global address of the NAT of the network which the MN is visiting. - For the example of mobile node MNi,Nk the MHD of NAT-N in FIG. 4 reflects a flag value of 1, a local address of MNi,Nk@HostB1 and a NAT address of NAT-B. A corresponding node attempting to communicate with mobile Node MNi,Nk will not be able to establish a binding with NAT-N since the flag in NAT-N's MHD is set to 1. In that case, the binding is established with the binding represented by the local address and NAT address fields for MNi,Nk's entry in NAT-N's MHD. Communication is then conducted establishing a binding with the foreign NAT, in the example NAT-B.
- So long as the visiting MN does not establish an association with a Host of a different network, it will preferably retain its visiting address VA identification in the MHD of the NAT whose network is visiting, which VA will be also reflected in the MHD of the mobile node's home network's NAT.
- If the visiting mobile node establishes an association with another Host within the same network that it is visiting, it will retain its same VA identification in the MHD of the NAT which is visiting, but will be provided with a new local address. That new local address will be stored in the visiting MN's MHD record's COA field and the visited network's NAT will direct communications to the MN based on that COA data. No change is required in the MN's home network's NAT's MHD in such case. For example, if MNi,Nk switches its association with HostB1 and connects to HostB0, the COA entry in the MHD of NAT-B will be changed from MNi,Nk@HostB1 to MNi,Nk@HostB0 and no change will be made in the entries in the MHD of NAT-N.
- Preferably, the hosts will periodically determine whether a connection is still established with a visiting MN. If the visited host determines that the MN has disconnected and the MN has not established a connection with another host, the visited host can communicate this fact to its associated NAT which will change the COA for the visiting MN's entry to a null data state. An example of this is the entry for visiting node MNh,Pq in FIG. 3. That entry indicates that MNh,Pq had connected with foreign HostB1, but is no longer connected to network 12. Thus, no connection of MNh,Pq is illustrated with any Host in FIG. 1. Such an entry will also indicate to a CN that the MN has not established a connection with another host, since the CN will only contact
network 12 via the VA of MNh,Pq, namely MNh,Pq@HostB1, if MNh,Pq's home network's NAT's MHD record has not been updated. If a CN attempts to communicate with the visiting node at that time and is referred to the visited network's NAT by the MN's home Host's NAT, a binding will not be established and the communication will fail. - When a MN's home network's NAT receives a communication to change the binding information for the MN from one foreign NAT to another, it preferably sends a message to the first foreign NAT reflecting the the MN is no longer visiting that NAT's network, so that the visiting node record can be deleted from the first foreign NAT's MHD. Such a message is preferably also sent, when a MN returns to its home network after visiting other networks.
- The CN never needs to know the current location of the MN. The CN only needs to be aware of the static, default binding based on a MN's home address (HA) and home network's global address. This arrangement saves the flurry of registration messages from being sent over the global Internet.
- The tight coupling of the MHDs to the NATs means that an IP data packet does not have to travel first to the home network. The packet can be tunneled directly to the foreign network where the MN is located. This avoids the infamous triangle routing problem.
- The micro-mobility protocol for MNs roaming across multiple foreign networks (FNs) starts with the CN's NAT trying to establish a binding with the MN's home network's NAT. The process fails, when the status-bit in the MN's home network's NAT's MHD is a 1. This indicates that the MN is not currently in its home network (HN); it is in a FN. The FN has assigned a VA to the MN which is stored in the MN's home network's NAT's MHD along with the static global address of the FN. That binding data is sent back to the CN's NAT and the CN's NAT then establishes binding with the FN's NAT. The rest of the protocol then proceeds the same way as if the MN were connected with a host in its home network.
- When during a communication with a CN, a MN moves from one foreign network FN1 to a different to a different foreign network FN2, the entries for the MN in the MHD of FN1 are preferably set 0, NULL, NULL when the MN loses contact with the FN1. When the MN then moves to the different FN2, it communicates with FN2 via a host, Host2, associated with the NAT of FN2, NAT-FN2. The MN is assigned a VA of MN@Host2 such that the entries for that VA in the MHD of NAT-FN2 are set to 0, MN@Host2, NULL. The binding data (MN@Host2, NAT-FN2) is sent to the MN's home network's NAT and the CN's NAT. A new binding is established between the CN's NAT and NAT-FN2. The rest of the protocol then proceeds as described above.
- When during a communication with a CN, a MN moves from a foreign network FN1 to back to its home network HN, the entry for the MN in the MHD of the NAT of FN1 is preferably set 0, NULL, NULL when the MN loses contact with the FN1. When the MN then moves to its HN, it communicates with its HN via a host, HostHN, associated with its HN's NAT, NAT-HN. Note that HostHN may or may not be the MN's home host, HostHome. In its HN's NAT's MHD, the MN already has a data record for its HA of MN@HostHome. That record is preferably then changed to set the associated data fields to 0, MN@HostHN, NULL. The binding data (MN@HostHome, NAT-HN) is sent to the CN's NAT. A new binding is established between the CN's NAT and NAT-HN. The rest of the protocol then proceeds as described above.
- The CN's NAT in the above cases would normally be the CN's home network's NAT. However, if the CN is a MN which is visiting a FN, the CN's NAT is the NAT of the FN being visited.
- Other variations and alternatives will be recognized by those of ordinary skill in the art as within the scope of the invention are intended to be included herein.
Claims (7)
1. A network system for supporting mobile Internet communication comprising:
a plurality of networks, each having:
a Network Address Translation router (NAT) with a unique global address;
at least one Host associated with the network's NAT; and
at least one Mobile Node (MN);
each Host having a service area in which it can communicate data to the MNs;
each MN having a home Host in a home network which defines a default local address which is paired with the global address of the home network's NAT to define a default binding of the MN;
the NAT of each network having an associated Mobile-Home Database (MHD) which identifies:
each MN, which has the network as its home network, with:
a local address of a current association of the MN with a Host in the network, or
a binding defined by a local address of an association of the MN with a Host in a different network and the global address of the different network's NAT; and
each visiting MN, which is a MN currently associated with a Host within the network, but has a different home network, with a local address of the current Host association of the MN;
each MN being movable from a location where the MN communicates data via a first associated Host in a first network having a first NAT to:
a location within the service area of a second Host within the first network to communicate data via the second Host by communicating to the MHB of the first NAT a local address reflecting the MN's association with the second Host; or
a location within the access range of a third Host within a different second network having a second NAT to communicate data via the third Host by communicating to the MHB of the second NAT a local address reflecting the MN's association with the third Host and, where the second network is not the MN's home network, by also communicating to the MHB of the MN's home network's NAT a binding including a new local address reflecting the MN's association with the third Host and the global address of the second NAT;
such that a data communication from a corresponding node (CN) to a selected MN is communicated to the selected MN by:
establishing a binding based on the MN's default binding or the binding reflected in the MHB of the MN's home network's NAT, and
directing the communication to the local address identified for the MN in the MHB of the NAT with which the binding is established.
2. A network system according to claim 1 wherein at least one network has a plurality of Hosts and at least one Host is the home Host for a plurality of MNs.
3. A network system according to claim 1 wherein each network's NAT's MHD identifies local and global addresses and a location field such that:
each MN, which has the network as its home network, is identified with:
a local address of a current association of the MN with a Host in the network, a null global address, and a home flag in the location field, or
a binding defined by a local address of an association of the MN with a Host in a different network and a global address of the different network's NAT and an away flag in the location field; and
each visiting MN is identified with:
a local address of the current Host association of the MN, a null global address, and a home flag in the location field.
4. A method for mobile Internet communication system which includes a plurality of networks each having a Network Address Translation router (NAT) and a unique global address, at least one Host associated with the NAT, and at least one Mobile Node (MN), each Host having a service area in which it can communicate data to the MNs, each MN having a home Host and a home network which defines a default local address which is paired with the global address of the HN's NAT to define a default binding of the MN, the method comprising:
providing an associated Mobile-Home Database (MHD) for the NAT of each network which identifies:
each MN, which has the network as its home network, with:
a local address of a current association of the MN with a Host within the network, or
a binding defined by a local address of an association of the MN with a Host within a different network and the global address of the different network's NAT; and
each visiting MN, which is a MN currently associated with a Host within the network, but has a different home network, with a local address of the current Host association of the MN;
when a MN moves from a location where the MN communicates data via a first associated Host within a first network having a first NAT to a location within the service area of a second Host within the first network to communicate data via the second Host, communicating to the MHB of the first NAT a local address reflecting the MN's association with the second Host;
when a MN moves from a location where the MN communicates data via the first associated Host within the first network to a location within the access range of a third Host within a different second network having a second NAT, to communicate data via the third Host, communicating to the MHB of the second NAT a local address reflecting the MN's association with the third Host and, where the second network is not the MN's home network, by also communicating to the MHB of the MN's home network's NAT a binding including a new local address reflecting the MN's association with the third Host and the global address of the second NAT; and
communicating a data communication from a corresponding node (CN) to a selected MN by:
establishing a binding with a NAT based on the MN's default binding or the binding reflected in the MHB of the MN's home network's NAT, and
directing the communication to the local address identified in the MHB of the NAT with which the binding is established for the MN.
5. A method according to claim 4 wherein:
each network's NAT's MHD identifies local and global addresses and a location field such that:
each MN, which has the network as its home network, is identified with:
a 24 bit local address of a current association of the MN with a Host in the network, a null global address, and a home flag in the location field, or
a binding defined by a local address of an association of the MN with a Host within a different network and a global address of the different network's NAT and an away flag in the location field; and
each visiting MN is identified with:
a local address of the current Host association of the MN, a null global address, and a home flag in the location field; and
a binding is established between the CN and an MN based on the binding reflected in the MHB of the MN's home network's NAT when the corresponding location field has an away flag.
6. A Network Address Translation router (NAT) for a network system which includes a plurality of networks, each having a NAT with a unique global address, at least one Host associated with the NAT and at least one Mobile Node (MN), each Host having a service area in which it can communicate data to the MNs, each MN having a home Host and home network which defines a default local address which is paired with the global address of the home network's NAT to define a default binding of the MN, the NAT comprising:
a Mobile-Home Database (MHD) which identifies:
each MN, which has as its home Host, a Host associated with the NAT, with:
a local address of a current association of the MN with a Host associated with the NAT, or
a binding defined by a local address of an association of the MN with a Host not associated with the NAT and the global address of the NAT associated with that Host; and
each MN, which is currently associated with a Host associated with the NAT, but has a home Host which is not associated with the NAT, with a local address of the current Host association;
such that a data communication from a corresponding node (CN) to a selected MN which has as its home Host, a Host associated with the NAT, is communicated to the selected MN by:
establishing a binding based on the MN's default binding or the binding reflected in the MHB of the NAT, and
if the binding is established is established with the NAT, directing the communication to the local address identified in the MHB.
7. A NAT according to claim 6 wherein the MHD identifies 24 bit local and global addresses and a location field such that:
each MN, which has as its home Host, a Host associated with the NAT, is identified with:
a 24 bit local address of a current association of the MN with a Host associated with the NAT, a null global address, and a home flag in the location field, or
a binding defined by a 24 bit local address of an association of the MN with a Host not associated with the NAT and a 24 bit global address of the NAT associated with that Host and an away flag in the location field; and
each MN, which is currently associated with a Host associated with the NAT, but has a home Host which is not associated with the NAT, is identified with:
a 24 bit local address of the current Host association of the MN, a null global address, and a home flag in the location field.
Priority Applications (34)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/026,060 US20020055971A1 (en) | 1999-11-01 | 2001-12-19 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
KR1020037010956A KR100604170B1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
CNA2009101498371A CN101605320A (en) | 2001-02-21 | 2002-02-14 | The method and system of low overhead mobility management protocol in the internet protocol layer |
EP20060009962 EP1701507B1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
KR1020077013445A KR100787085B1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
KR1020087002942A KR20080025755A (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
MXPA03007522A MXPA03007522A (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer. |
KR1020097003776A KR100974256B1 (en) | 2001-02-21 | 2002-02-14 | A communications network apparatus configured to facilitate communication of a plurality of mobile nodes over the internet |
AT02709525T ATE327627T1 (en) | 2001-02-21 | 2002-02-14 | SYSTEM AND METHOD FOR A MOBILITY MANAGEMENT PROTOCOL WITH LOW ADDITIONAL EFFORT IN AN INTERNET PROTOCOL LAYER |
JP2002570503A JP2004530327A (en) | 2001-02-21 | 2002-02-14 | Method and system for low overhead mobility management protocol at internet protocol layer |
CA 2704835 CA2704835A1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
KR1020077019555A KR100914697B1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
CNB028052730A CN100505739C (en) | 2001-02-21 | 2002-02-14 | Method and system for low-overhead mobility management protocol in internet protocol layer |
ES02709525T ES2262783T3 (en) | 2001-02-21 | 2002-02-14 | A METHOD AND SYSTEM FOR A REDUCED TARE MOBILITY MANAGEMENT PROTOCOL IN THE INTERNET PROTOCOL LAYER. |
CN2009101394156A CN101600194B (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
KR1020087016492A KR100935121B1 (en) | 2001-02-21 | 2002-02-14 | A communications network apparatus configured to facilitate communication of a plurality of mobile nodes over the internet |
KR1020037013811A KR100789797B1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
EP20020709525 EP1362462B1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
PCT/US2002/004372 WO2002071718A2 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
AU2002244005A AU2002244005A1 (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
CA 2438929 CA2438929C (en) | 2001-02-21 | 2002-02-14 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
DE2002611657 DE60211657T2 (en) | 2001-02-21 | 2002-02-14 | SYSTEM AND METHOD FOR A MOBILITY MANAGEMENT PROTOCOL WITH LOW ADDITIONAL EXPENSE IN AN INTERNET PROTOCOL LAYER |
TW92126762A TWI272809B (en) | 2001-02-21 | 2002-02-18 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
TW91102715A TW558891B (en) | 2001-02-21 | 2002-02-18 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
US10/078,946 US7136389B2 (en) | 2001-02-21 | 2002-02-20 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
ARP020100591 AR032817A1 (en) | 2001-02-21 | 2002-02-21 | A METHOD AND SYSTEM FOR A LOW PERFORMANCE MOBILITY MANAGEMENT PROTOCOL IN THE INTERNET PROTOCOL LAYER |
MYPI20020603A MY127553A (en) | 2001-02-21 | 2002-02-21 | A method and system for a low-overhead mobility management protocol in the internet protocol layer. |
NO20033676A NO20033676L (en) | 2001-02-21 | 2003-08-19 | Procedure and system for low management mobility management in the Internet protocol layer |
HK04110319A HK1067476A1 (en) | 2001-02-21 | 2004-12-29 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
US11/542,842 US7573890B2 (en) | 2001-02-21 | 2006-10-04 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
JP2008032217A JP5042874B2 (en) | 2001-02-21 | 2008-02-13 | Method and system for low overhead mobility management protocol in internet protocol layer |
US12/414,021 US8213385B2 (en) | 2001-02-21 | 2009-03-30 | Method and apparatus for wireless communication with low-overhead mobility management |
HK10105654.4A HK1138981A1 (en) | 2001-02-21 | 2010-06-09 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
US13/540,424 US8792323B2 (en) | 2001-02-21 | 2012-07-02 | Method and apparatus for wireless communication with low-overhead mobility management |
Applications Claiming Priority (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP311703/1999 | 1999-11-01 | ||
US27019001P | 2001-02-21 | 2001-02-21 | |
US27076701P | 2001-02-22 | 2001-02-22 | |
US29384701P | 2001-05-25 | 2001-05-25 | |
US29616801P | 2001-06-06 | 2001-06-06 | |
US30904601P | 2001-07-31 | 2001-07-31 | |
US09/997,922 US20020154613A1 (en) | 2001-02-21 | 2001-11-30 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US10/026,060 US20020055971A1 (en) | 1999-11-01 | 2001-12-19 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/997,992 Continuation-In-Part US6433195B1 (en) | 1999-11-01 | 2001-11-30 | Production methods of 5-phthalancarbonitrile compound and an intermediate therefor |
US09/997,922 Continuation-In-Part US20020154613A1 (en) | 1999-11-01 | 2001-11-30 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/997,922 Continuation-In-Part US20020154613A1 (en) | 1999-11-01 | 2001-11-30 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US10/078,946 Continuation-In-Part US7136389B2 (en) | 2001-02-21 | 2002-02-20 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
Publications (1)
Publication Number | Publication Date |
---|---|
US20020055971A1 true US20020055971A1 (en) | 2002-05-09 |
Family
ID=39880327
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/026,060 Abandoned US20020055971A1 (en) | 1999-11-01 | 2001-12-19 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US10/078,946 Expired - Fee Related US7136389B2 (en) | 2001-02-21 | 2002-02-20 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US11/542,842 Expired - Fee Related US7573890B2 (en) | 2001-02-21 | 2006-10-04 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US12/414,021 Expired - Fee Related US8213385B2 (en) | 2001-02-21 | 2009-03-30 | Method and apparatus for wireless communication with low-overhead mobility management |
US13/540,424 Expired - Fee Related US8792323B2 (en) | 2001-02-21 | 2012-07-02 | Method and apparatus for wireless communication with low-overhead mobility management |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/078,946 Expired - Fee Related US7136389B2 (en) | 2001-02-21 | 2002-02-20 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US11/542,842 Expired - Fee Related US7573890B2 (en) | 2001-02-21 | 2006-10-04 | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US12/414,021 Expired - Fee Related US8213385B2 (en) | 2001-02-21 | 2009-03-30 | Method and apparatus for wireless communication with low-overhead mobility management |
US13/540,424 Expired - Fee Related US8792323B2 (en) | 2001-02-21 | 2012-07-02 | Method and apparatus for wireless communication with low-overhead mobility management |
Country Status (16)
Country | Link |
---|---|
US (5) | US20020055971A1 (en) |
EP (2) | EP1701507B1 (en) |
JP (2) | JP2004530327A (en) |
KR (5) | KR100935121B1 (en) |
CN (3) | CN101600194B (en) |
AR (1) | AR032817A1 (en) |
AT (1) | ATE327627T1 (en) |
AU (1) | AU2002244005A1 (en) |
CA (2) | CA2704835A1 (en) |
DE (1) | DE60211657T2 (en) |
ES (1) | ES2262783T3 (en) |
HK (1) | HK1067476A1 (en) |
MX (1) | MXPA03007522A (en) |
NO (1) | NO20033676L (en) |
TW (2) | TWI272809B (en) |
WO (1) | WO2002071718A2 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002071718A2 (en) * | 2001-02-21 | 2002-09-12 | Interdigital Technology Corporation | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
US20030193952A1 (en) * | 2002-02-04 | 2003-10-16 | O'neill Alan | Mobile node handoff methods and apparatus |
US20030193912A1 (en) * | 2002-02-04 | 2003-10-16 | O'neill Alan | Packet forwarding methods for use in handoffs |
US20040013099A1 (en) * | 2002-04-15 | 2004-01-22 | O'neill Alan | Method and apparatus for extending mobile IP |
US20040047348A1 (en) * | 2002-02-04 | 2004-03-11 | O'neill Alan | Methods and apparatus for aggregating MIP and AAA messages |
EP1439673A2 (en) * | 2003-01-09 | 2004-07-21 | NTT DoCoMo, Inc. | Mobile communications system and routing management apparatus used in the mobile communications system |
US20050041650A1 (en) * | 2002-02-04 | 2005-02-24 | O'neill Alan | Method for extending mobile IP and AAA to enable integrated support for local access and roaming access connectivity |
US20070043876A1 (en) * | 2005-08-19 | 2007-02-22 | Nokia Corporation | Stimulation traffic for binding refreshment |
US7260649B1 (en) * | 2002-04-16 | 2007-08-21 | Cisco Technology, Inc. | Apparatus and methods for forwarding data between public networks via a private network |
US20080259788A1 (en) * | 2005-10-28 | 2008-10-23 | Huawei Technologies Co., Ltd. | Method For Routing Mobile Node In Wireless Mesh Network And A Communication System Thereof |
US20100061380A1 (en) * | 2008-09-05 | 2010-03-11 | Cisco Technology, Inc., A Corporation Of California | Load Balancing across Multiple Network Address Translation (NAT) Instances and/or Processors |
EP2371154A1 (en) * | 2008-12-31 | 2011-10-05 | Nortel Networks Limited | Creating a globally unique indentifier of a subscriber device |
US20190215300A1 (en) * | 2018-01-09 | 2019-07-11 | Circle Media Labs Inc. | Devices, networks, storage media, and methods for identifying client devices across a network address translation border |
Families Citing this family (56)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7486958B2 (en) * | 2001-09-05 | 2009-02-03 | Networks In Motion, Inc. | System and method for maintaining an online point-of-interest directory |
US7711819B2 (en) * | 2001-10-31 | 2010-05-04 | Fujitsu Limited | Load balancer |
US7574492B2 (en) * | 2002-09-12 | 2009-08-11 | Broadcom Corporation | Optimizing network configuration from established usage patterns of access points |
US8254935B2 (en) | 2002-09-24 | 2012-08-28 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
KR100510127B1 (en) * | 2002-12-31 | 2005-08-25 | 삼성전자주식회사 | A handover method and mobile node handover device in wireless LAN |
JP2004242019A (en) * | 2003-02-05 | 2004-08-26 | Ntt Docomo Inc | Mobile communication control system, network management server, mobile node, access node, and anchor node |
JP2004253914A (en) * | 2003-02-18 | 2004-09-09 | Ntt Docomo Inc | Communication system, address managing method, relay apparatus, and management apparatus |
US7535878B2 (en) * | 2003-03-28 | 2009-05-19 | Intel Corporation | Method, apparatus and system for ensuring reliable access to a roaming mobile node |
US7162253B2 (en) * | 2003-09-08 | 2007-01-09 | Nokia Corporation | Geographical position extension in messaging for a terminal node |
US7580396B2 (en) | 2003-11-05 | 2009-08-25 | Intel Corporation | Method, apparatus and system for obtaining and retaining a mobile node home address |
US20050113109A1 (en) * | 2003-11-25 | 2005-05-26 | Farid Adrangi | Method, apparatus and system for context-based registrations based on intelligent location detection |
US20050111454A1 (en) * | 2003-11-25 | 2005-05-26 | Narjala Ranjit S. | Method, apparatus and system for intelligently and dynamically routing mobile internet protocol packets |
US20050111380A1 (en) * | 2003-11-25 | 2005-05-26 | Farid Adrangi | Method, apparatus and system for mobile nodes to dynamically discover configuration information |
US8000297B2 (en) * | 2003-11-26 | 2011-08-16 | Electronics And Telecommunciations Research Institute | Access router based mobile IPv6 fast handover method |
US20050136924A1 (en) * | 2003-12-04 | 2005-06-23 | Farid Adrangi | Method, apparatus and system for enabling roaming mobile nodes to utilize private home IP addresses |
CN1926823B (en) * | 2004-01-07 | 2010-11-10 | 松下电器产业株式会社 | Communication system, mobile terminal and access router |
RU2377730C2 (en) * | 2004-01-07 | 2009-12-27 | Панасоник Корпорэйшн | Communication system, user equipment and access router |
US7330726B2 (en) * | 2004-06-07 | 2008-02-12 | Spyder Navigation Llc | Determining geographical position in IPv6 networks |
CN101053213B (en) | 2004-11-04 | 2011-06-22 | 松下电器产业株式会社 | Multi-interface communication equipment, terminal and path switching method |
US7760720B2 (en) * | 2004-11-09 | 2010-07-20 | Cisco Technology, Inc. | Translating native medium access control (MAC) addresses to hierarchical MAC addresses and their use |
KR100813793B1 (en) | 2004-12-23 | 2008-03-13 | 주식회사 케이티 | Mobile router switching method for mobile internet service with multiple mobile routers |
EP1839425A1 (en) * | 2005-01-07 | 2007-10-03 | Societe Anonyme Alcatel | Method and apparatus for providing route-optimized secure session continuity between mobile nodes |
CN100442751C (en) * | 2005-01-19 | 2008-12-10 | 华为技术有限公司 | System and method of delivering multicast service system on mobile host computers |
CN100372417C (en) * | 2005-02-07 | 2008-02-27 | 华为技术有限公司 | Method for discovering boundary object in local subnetwork |
US7894407B2 (en) * | 2005-03-25 | 2011-02-22 | Alcatel-Lucent Usa Inc. | Method and apparatus for seamless roaming for wireless networks |
US20090135822A1 (en) * | 2005-05-31 | 2009-05-28 | Matsushita Electric Industrial Co., Ltd. | Method and apparatus for controlling packet forwarding |
EP1739893A1 (en) * | 2005-06-30 | 2007-01-03 | Matsushita Electric Industrial Co., Ltd. | Optimized reverse tunnelling for packet switched mobile communication systems |
WO2007101628A1 (en) * | 2006-03-08 | 2007-09-13 | Matsushita Electric Industrial Co., Ltd. | Mobile ipv6 optimised reverse tunnelling for multi-homed terminals |
WO2007087110A2 (en) | 2005-12-22 | 2007-08-02 | Padcom Holdings, Inc | Multi-network seamless roaming mobile router with auto-discovery and migration of downstream devices on the mobile network |
US9161205B2 (en) * | 2006-02-14 | 2015-10-13 | Alcatel Lucent | Route optimization at a packet data switch node |
JP4990920B2 (en) * | 2006-03-08 | 2012-08-01 | パナソニック株式会社 | Mobile IPv6 optimized reverse tunneling for multihomed terminals |
CN100456742C (en) * | 2006-04-30 | 2009-01-28 | 国家数字交换系统工程技术研究中心 | Mobile Internet protocol route processing method and system and router |
JP2008015880A (en) * | 2006-07-07 | 2008-01-24 | Fuji Xerox Co Ltd | Network system, image processor and computer program |
US9210034B2 (en) * | 2007-03-01 | 2015-12-08 | Cisco Technology, Inc. | Client addressing and roaming in a wireless network |
US7908386B2 (en) * | 2007-04-04 | 2011-03-15 | Telefonaktiebolaget L M Ericsson Publ) | Large scale mobile network address translation |
EP2012489B1 (en) * | 2007-07-05 | 2009-05-06 | Conveneer AB | Method, apparatus and system for mobility management and efficient information retrieval in a communications network |
US7986667B2 (en) | 2007-10-19 | 2011-07-26 | Ericsson Ab | Forwarding data path optimization in a distributed environment for achieving micro-mobility |
JP4571968B2 (en) * | 2007-10-29 | 2010-10-27 | 富士通株式会社 | Mobile communication system, transfer method and base station in the same system |
US8179859B2 (en) | 2008-02-21 | 2012-05-15 | Wang Ynjiun P | Roaming encoded information reading terminal |
US9025563B2 (en) | 2008-03-13 | 2015-05-05 | Qualcomm Incorporated | Supporting communications in a wireless network using an IP address |
US20090265542A1 (en) * | 2008-04-18 | 2009-10-22 | Amit Khetawat | Home Node B System Architecture |
US8165090B2 (en) | 2008-05-15 | 2012-04-24 | Nix John A | Efficient handover of media communications in heterogeneous IP networks |
CN101605367A (en) * | 2008-06-13 | 2009-12-16 | 三星电子株式会社 | The method that UE switches between the family expenses base station |
US8165091B2 (en) * | 2008-06-27 | 2012-04-24 | Nix John A | Efficient handover of media communications in heterogeneous IP networks using LAN profiles and network handover rules |
US8305980B1 (en) | 2008-09-12 | 2012-11-06 | Nix John A | Efficient handover of media communications in heterogeneous IP networks using handover procedure rules and media handover relays |
US8072975B2 (en) * | 2008-11-12 | 2011-12-06 | Dell Products, Lp | Host discovery across different address spaces |
US8191785B2 (en) * | 2009-03-05 | 2012-06-05 | Hand Held Products, Inc. | Encoded information reading terminal operating in infrastructure mode and ad-hoc mode |
US20110185083A1 (en) * | 2010-01-27 | 2011-07-28 | Electronics And Telecommunications Research Institute | Identifier and locator structure, and communication method based on the structure |
CN102869122B (en) * | 2011-07-05 | 2018-08-28 | 北京三星通信技术研究有限公司 | The method for avoiding handover failure |
CN103580880B (en) | 2012-08-03 | 2017-12-29 | 华为技术有限公司 | Method, equipment and system abnormal a kind of fast notification CGN |
US9871717B2 (en) * | 2014-04-25 | 2018-01-16 | Metaswitch Networks Ltd | Data processing |
US9954777B2 (en) | 2016-01-14 | 2018-04-24 | International Business Machines Corporation | Data processing |
CN106658479B (en) * | 2016-11-16 | 2020-12-11 | 广东新岸线科技有限公司 | Method for realizing wireless network convergence |
US10142903B2 (en) | 2016-12-07 | 2018-11-27 | Wistron Neweb Corporation | Inter-domain handover method and system for user equipment and relay gateway device |
CN110730116B (en) * | 2019-10-21 | 2021-10-29 | 杭州鸿雁智能科技有限公司 | Operation method of communication equipment in local area network, communication equipment and gateway equipment |
US11589188B1 (en) | 2021-05-27 | 2023-02-21 | T-Mobile Usa, Inc. | Device-based timely emergency call routing |
Family Cites Families (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3411159B2 (en) | 1996-08-02 | 2003-05-26 | 株式会社日立製作所 | Mobile computer support system |
JPH10117207A (en) | 1996-10-11 | 1998-05-06 | Matsushita Electric Ind Co Ltd | Mobile terminal connection method and network router |
JPH10178421A (en) * | 1996-10-18 | 1998-06-30 | Toshiba Corp | Packet processor, mobile computer, packet transferring method and packet processing method |
US6173007B1 (en) * | 1997-01-15 | 2001-01-09 | Qualcomm Inc. | High-data-rate supplemental channel for CDMA telecommunications system |
US6587882B1 (en) * | 1997-08-01 | 2003-07-01 | Kabushiki Kaisha Toshiba | Mobile IP communication scheme using visited site or nearby network as temporal home network |
JP3641112B2 (en) * | 1997-09-05 | 2005-04-20 | 株式会社東芝 | Packet relay device, mobile computer device, mobile computer management device, packet relay method, packet transmission method, and mobile computer location registration method |
US6577643B1 (en) * | 1997-10-14 | 2003-06-10 | Lucent Technologies Inc. | Message and communication system in a network |
US6535493B1 (en) * | 1998-01-15 | 2003-03-18 | Symbol Technologies, Inc. | Mobile internet communication protocol |
JP3641128B2 (en) * | 1998-02-20 | 2005-04-20 | 株式会社東芝 | MOBILE COMPUTER DEVICE, MOBILE COMPUTER MANAGEMENT DEVICE, MOBILE COMPUTER MANAGEMENT METHOD, AND COMMUNICATION CONTROL METHOD |
US6058431A (en) * | 1998-04-23 | 2000-05-02 | Lucent Technologies Remote Access Business Unit | System and method for network address translation as an external service in the access server of a service provider |
JPH11353360A (en) | 1998-06-04 | 1999-12-24 | Hitachi Ltd | Operation plan designing method and operation assisting method |
JP3581251B2 (en) * | 1998-06-16 | 2004-10-27 | 株式会社東芝 | Communication system, data packet transfer method, router device, and packet relay device |
US6115580A (en) * | 1998-09-08 | 2000-09-05 | Motorola, Inc. | Communications network having adaptive network link optimization using wireless terrain awareness and method for use therein |
JP4057715B2 (en) | 1998-09-16 | 2008-03-05 | 株式会社東芝 | Router device, wireless terminal device, wireless base station, and message transmission control method |
US6328098B1 (en) | 1998-11-10 | 2001-12-11 | Valeo Inc. | Side member for heat exchanger and heat exchanger incorporating side plate |
JP2000149104A (en) | 1998-11-12 | 2000-05-30 | Fuji Electric Co Ltd | Automatic vending machine with information collection function and its system |
US6353607B1 (en) * | 1998-11-20 | 2002-03-05 | Ericsson Inc. | IP base GSM inter-MSC handover |
CA2287613A1 (en) * | 1998-12-07 | 2000-06-07 | Kenneth Carl Budka | Methods and apparatus for route optimization in a communications system |
US6434134B1 (en) * | 1998-12-11 | 2002-08-13 | Lucent Technologies, Inc. | Dynamic address assignment for wireless devices accessing packet-based wired networks |
US6496505B2 (en) * | 1998-12-11 | 2002-12-17 | Lucent Technologies Inc. | Packet tunneling optimization to wireless devices accessing packet-based wired networks |
US6654359B1 (en) * | 1998-12-11 | 2003-11-25 | Lucent Technologies Inc. | Wireless access to packet-based networks |
US6452920B1 (en) * | 1998-12-30 | 2002-09-17 | Telefonaktiebolaget Lm Ericsson | Mobile terminating L2TP using mobile IP data |
FI108834B (en) * | 1999-03-29 | 2002-03-28 | Nokia Corp | IP mobility management in a mobile communication system |
GB2348570B (en) * | 1999-03-31 | 2003-03-05 | Ericsson Telefon Ab L M | Mobile internet access |
JP3764016B2 (en) * | 1999-05-10 | 2006-04-05 | 財団法人流通システム開発センタ− | Integrated IP transfer network |
US6621810B1 (en) * | 1999-05-27 | 2003-09-16 | Cisco Technology, Inc. | Mobile IP intra-agent mobility |
KR100298371B1 (en) | 1999-06-09 | 2001-11-01 | 서평원 | Method for operating handover in packet mobile communication network |
US6487406B1 (en) * | 1999-06-16 | 2002-11-26 | Telcordia Technologies, Inc. | PCS-to-mobile IP internetworking |
WO2001006707A1 (en) * | 1999-07-19 | 2001-01-25 | British Telecommunications Public Limited Company | Telecommunications routing |
JP3895176B2 (en) * | 1999-07-22 | 2007-03-22 | 株式会社日立製作所 | Mobile IP network system and connection switching method |
US20020055971A1 (en) * | 1999-11-01 | 2002-05-09 | Interdigital Technology Corporation | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US6310222B1 (en) * | 1999-11-01 | 2001-10-30 | Sumika Fine Chemicals Co., Ltd. | Production method of 5-phthalancarbonitrile compound, intermediate therefor and production method of the intermediate |
US7197017B1 (en) * | 2000-01-04 | 2007-03-27 | Qualcomm, Incorporated | Method and apparatus for channel optimization during point-to-point protocol (PPP) session requests |
JP3633430B2 (en) * | 2000-03-27 | 2005-03-30 | 三菱電機株式会社 | COMMUNICATION METHOD, COMMUNICATION SYSTEM, COMMUNICATION DEVICE, AND RECORDING MEDIUM |
US6907017B2 (en) * | 2000-05-22 | 2005-06-14 | The Regents Of The University Of California | Mobility management in wireless internet protocol networks |
AU9615701A (en) * | 2000-10-18 | 2002-04-29 | Ericsson Telefon Ab L M | Seamless handoff in mobile ip |
CA2426737A1 (en) * | 2000-10-26 | 2002-05-02 | British Telecommunications Public Limited Company | Telecommunications routing |
JP3814185B2 (en) * | 2000-11-13 | 2006-08-23 | 松下電器産業株式会社 | Base station apparatus, mobile communication terminal apparatus, and radio access system using them |
US7079511B2 (en) * | 2000-12-06 | 2006-07-18 | Qualcomm, Incorporated | Method and apparatus for handoff of a wireless packet data services connection |
US7333482B2 (en) * | 2000-12-22 | 2008-02-19 | Interactive People Unplugged Ab | Route optimization technique for mobile IP |
US6856624B2 (en) * | 2001-02-21 | 2005-02-15 | Alcatel | Temporary unique private address |
US7480272B2 (en) * | 2001-04-02 | 2009-01-20 | Toshiba America Research, Inc | Soft handoff in IP-based CDMA networks by IP encapsulation |
WO2003015356A1 (en) * | 2001-08-08 | 2003-02-20 | Fujitsu Limited | Server, mobile communication terminal, radio device, communication method for communication system, and communication system |
US6993335B2 (en) * | 2002-11-15 | 2006-01-31 | Motorola, Inc. | Apparatus and method for mobile/IP handoff between a plurality of access technologies |
US7686641B2 (en) * | 2008-06-20 | 2010-03-30 | Nexus, Incorporated | Wire piercing electrical connector |
EP2352338A1 (en) * | 2008-11-07 | 2011-08-03 | Panasonic Corporation | Handover method, and mobile terminal and home agent used in the method |
-
2001
- 2001-12-19 US US10/026,060 patent/US20020055971A1/en not_active Abandoned
-
2002
- 2002-02-14 JP JP2002570503A patent/JP2004530327A/en active Pending
- 2002-02-14 AT AT02709525T patent/ATE327627T1/en not_active IP Right Cessation
- 2002-02-14 DE DE2002611657 patent/DE60211657T2/en not_active Expired - Lifetime
- 2002-02-14 KR KR1020087016492A patent/KR100935121B1/en not_active IP Right Cessation
- 2002-02-14 EP EP20060009962 patent/EP1701507B1/en not_active Expired - Lifetime
- 2002-02-14 KR KR1020077019555A patent/KR100914697B1/en not_active IP Right Cessation
- 2002-02-14 CA CA 2704835 patent/CA2704835A1/en not_active Abandoned
- 2002-02-14 EP EP20020709525 patent/EP1362462B1/en not_active Expired - Lifetime
- 2002-02-14 CN CN2009101394156A patent/CN101600194B/en not_active Expired - Fee Related
- 2002-02-14 CN CNB028052730A patent/CN100505739C/en not_active Expired - Fee Related
- 2002-02-14 KR KR1020087002942A patent/KR20080025755A/en not_active Application Discontinuation
- 2002-02-14 CN CNA2009101498371A patent/CN101605320A/en active Pending
- 2002-02-14 KR KR1020077013445A patent/KR100787085B1/en not_active IP Right Cessation
- 2002-02-14 ES ES02709525T patent/ES2262783T3/en not_active Expired - Lifetime
- 2002-02-14 MX MXPA03007522A patent/MXPA03007522A/en active IP Right Grant
- 2002-02-14 WO PCT/US2002/004372 patent/WO2002071718A2/en active IP Right Grant
- 2002-02-14 AU AU2002244005A patent/AU2002244005A1/en not_active Abandoned
- 2002-02-14 KR KR1020097003776A patent/KR100974256B1/en not_active IP Right Cessation
- 2002-02-14 CA CA 2438929 patent/CA2438929C/en not_active Expired - Fee Related
- 2002-02-18 TW TW92126762A patent/TWI272809B/en not_active IP Right Cessation
- 2002-02-18 TW TW91102715A patent/TW558891B/en not_active IP Right Cessation
- 2002-02-20 US US10/078,946 patent/US7136389B2/en not_active Expired - Fee Related
- 2002-02-21 AR ARP020100591 patent/AR032817A1/en not_active Application Discontinuation
-
2003
- 2003-08-19 NO NO20033676A patent/NO20033676L/en unknown
-
2004
- 2004-12-29 HK HK04110319A patent/HK1067476A1/en not_active IP Right Cessation
-
2006
- 2006-10-04 US US11/542,842 patent/US7573890B2/en not_active Expired - Fee Related
-
2008
- 2008-02-13 JP JP2008032217A patent/JP5042874B2/en not_active Expired - Fee Related
-
2009
- 2009-03-30 US US12/414,021 patent/US8213385B2/en not_active Expired - Fee Related
-
2012
- 2012-07-02 US US13/540,424 patent/US8792323B2/en not_active Expired - Fee Related
Cited By (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1701507A1 (en) * | 2001-02-21 | 2006-09-13 | Interdigital Technology Corporation | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
WO2002071718A3 (en) * | 2001-02-21 | 2003-02-06 | Interdigital Tech Corp | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
US8792323B2 (en) | 2001-02-21 | 2014-07-29 | Interdigital Technology Corporation | Method and apparatus for wireless communication with low-overhead mobility management |
US8213385B2 (en) | 2001-02-21 | 2012-07-03 | Interdigital Technology Corporation | Method and apparatus for wireless communication with low-overhead mobility management |
US20090238145A1 (en) * | 2001-02-21 | 2009-09-24 | Interdigital Technology Corporation | Method and apparatus for wireless communication with low-overhead mobility management |
US7573890B2 (en) | 2001-02-21 | 2009-08-11 | Interdigital Technolgy Corporation | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
WO2002071718A2 (en) * | 2001-02-21 | 2002-09-12 | Interdigital Technology Corporation | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
KR100787085B1 (en) * | 2001-02-21 | 2007-12-21 | 인터디지탈 테크날러지 코포레이션 | A method and system for a low-overhead mobility management protocol in the internet protocol layer |
US20070025366A1 (en) * | 2001-02-21 | 2007-02-01 | Interdigital Technology Corporation | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US7136389B2 (en) | 2001-02-21 | 2006-11-14 | Interdigital Technology Corporation | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US7525937B2 (en) | 2002-02-04 | 2009-04-28 | Qualcomm Incorporated | Method for extending mobile IP and AAA to enable integrated support for local access and roaming access connectivity |
US20030193912A1 (en) * | 2002-02-04 | 2003-10-16 | O'neill Alan | Packet forwarding methods for use in handoffs |
US20030193952A1 (en) * | 2002-02-04 | 2003-10-16 | O'neill Alan | Mobile node handoff methods and apparatus |
US20050041650A1 (en) * | 2002-02-04 | 2005-02-24 | O'neill Alan | Method for extending mobile IP and AAA to enable integrated support for local access and roaming access connectivity |
US8649352B2 (en) | 2002-02-04 | 2014-02-11 | Qualcomm Incorporated | Packet forwarding methods for use in handoffs |
US20060111102A1 (en) * | 2002-02-04 | 2006-05-25 | O'neill Alan | Controlling hand-off in a mobile node with two mobile IP clients |
US8179840B2 (en) | 2002-02-04 | 2012-05-15 | Qualcomm Incorporated | Method for extending mobile IP and AAA to enable integrated support for local access and roaming access connectivity |
US8095130B2 (en) | 2002-02-04 | 2012-01-10 | Qualcomm Incorporated | Controlling hand-off in a mobile node with two mobile IP clients |
US20090247155A1 (en) * | 2002-02-04 | 2009-10-01 | Qualcomm Incorporated | Controlling hand-off in a mobile node with two mobile ip clients |
US7509123B2 (en) | 2002-02-04 | 2009-03-24 | Qualcomm Incorporated | Controlling hand-off in a mobile node with two mobile IP clients |
US20090225688A1 (en) * | 2002-02-04 | 2009-09-10 | Qualcomm Incorporated | Method for extending mobile ip and aaa to enable integrated support for local access and roaming access connectivity |
US7564824B2 (en) | 2002-02-04 | 2009-07-21 | Qualcomm Incorporated | Methods and apparatus for aggregating MIP and AAA messages |
US20040047348A1 (en) * | 2002-02-04 | 2004-03-11 | O'neill Alan | Methods and apparatus for aggregating MIP and AAA messages |
US20040013099A1 (en) * | 2002-04-15 | 2004-01-22 | O'neill Alan | Method and apparatus for extending mobile IP |
US9226139B2 (en) | 2002-04-15 | 2015-12-29 | Qualcomm Incorporated | Methods and apparatus for extending mobile IP |
US7623497B2 (en) | 2002-04-15 | 2009-11-24 | Qualcomm, Incorporated | Methods and apparatus for extending mobile IP |
US7734819B1 (en) | 2002-04-16 | 2010-06-08 | Cisco Technology, Inc. | Apparatus and methods for forwarding data between public networks via a private network |
US7260649B1 (en) * | 2002-04-16 | 2007-08-21 | Cisco Technology, Inc. | Apparatus and methods for forwarding data between public networks via a private network |
EP1439673A3 (en) * | 2003-01-09 | 2005-10-19 | NTT DoCoMo, Inc. | Mobile communications system and routing management apparatus used in the mobile communications system |
EP1439673A2 (en) * | 2003-01-09 | 2004-07-21 | NTT DoCoMo, Inc. | Mobile communications system and routing management apparatus used in the mobile communications system |
US7307967B2 (en) | 2003-01-09 | 2007-12-11 | Ntt Docomo, Inc. | Mobile communications system and routing management apparatus used in the mobile communications system |
US20040196818A1 (en) * | 2003-01-09 | 2004-10-07 | Ntt Docomo, Inc. | Mobile communications system and routing management apparatus used in the mobile communications system |
US20070043876A1 (en) * | 2005-08-19 | 2007-02-22 | Nokia Corporation | Stimulation traffic for binding refreshment |
US8165040B2 (en) | 2005-10-28 | 2012-04-24 | Huawei Technologies Co., Ltd. | Method for routing mobile node in wireless mesh network and a communication system thereof |
US20080259788A1 (en) * | 2005-10-28 | 2008-10-23 | Huawei Technologies Co., Ltd. | Method For Routing Mobile Node In Wireless Mesh Network And A Communication System Thereof |
US20100061380A1 (en) * | 2008-09-05 | 2010-03-11 | Cisco Technology, Inc., A Corporation Of California | Load Balancing across Multiple Network Address Translation (NAT) Instances and/or Processors |
US8005098B2 (en) * | 2008-09-05 | 2011-08-23 | Cisco Technology, Inc. | Load balancing across multiple network address translation (NAT) instances and/or processors |
CN102273238A (en) * | 2008-12-31 | 2011-12-07 | 北方电讯网络有限公司 | Creating a globally unique identifier of a subscriber device |
EP2371154A1 (en) * | 2008-12-31 | 2011-10-05 | Nortel Networks Limited | Creating a globally unique indentifier of a subscriber device |
EP2371154A4 (en) * | 2008-12-31 | 2012-08-22 | Nortel Networks Ltd | Creating a globally unique indentifier of a subscriber device |
US8811988B2 (en) | 2008-12-31 | 2014-08-19 | Apple Inc. | Dynamically creating a globally unique identified of a subscriber device based on an identified of an aggregation device and identification information of the subscriber device for circuit-switched and packet-switched communication systems |
KR101503569B1 (en) | 2008-12-31 | 2015-03-17 | 애플 인크. | Creating a globally unique identifier of a subscriber device |
US20190215300A1 (en) * | 2018-01-09 | 2019-07-11 | Circle Media Labs Inc. | Devices, networks, storage media, and methods for identifying client devices across a network address translation border |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20020055971A1 (en) | Method and system for a low-overhead mobility management protocol in the internet protocol layer | |
US8005093B2 (en) | Providing connection between networks using different protocols | |
JP2008136243A6 (en) | Method and system for low overhead mobility management protocol in internet protocol layer | |
US20040184465A1 (en) | Mobile IP communication system using dual stack transition mechanism and method thereof | |
US8369293B2 (en) | Mobile router, home agent, and terminal position management method | |
JP4426580B2 (en) | Telecommunications system including two networks | |
RU2417556C2 (en) | System and method for routing and supporting domain name system of mobile node | |
US7706327B2 (en) | Mobile communication system and mobile communication terminal | |
US20020154613A1 (en) | Method and system for a low-overhead mobility management protocol in the internet protocol layer | |
JP2006114946A (en) | Mobile network system | |
KR20050079407A (en) | Method for providing soft handover using communication state information in wireless internet system | |
KR100789797B1 (en) | A method and system for a low-overhead mobility management protocol in the internet protocol layer | |
KR20050050455A (en) | Route optimazation method using prefix delegation protocol |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERDIGITAL TECHNOLOGY CORPORATION, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SHAHRIER, SHARIF M.;REEL/FRAME:012402/0432 Effective date: 20011218 |
|
AS | Assignment |
Owner name: INTERDIGITAL TECHNOLOGY CORPORATION, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHAHRIER, SHARIF M.;CHITRAPU, PRABHAKAR R.;REEL/FRAME:012505/0967 Effective date: 20020306 |
|
STCB | Information on status: application discontinuation |
Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION |