[go: up one dir, main page]

WO2003088600A1 - Appareil de communication - Google Patents

Appareil de communication Download PDF

Info

Publication number
WO2003088600A1
WO2003088600A1 PCT/JP2002/003839 JP0203839W WO03088600A1 WO 2003088600 A1 WO2003088600 A1 WO 2003088600A1 JP 0203839 W JP0203839 W JP 0203839W WO 03088600 A1 WO03088600 A1 WO 03088600A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
network
mobile terminal
public
isp
Prior art date
Application number
PCT/JP2002/003839
Other languages
English (en)
Japanese (ja)
Inventor
Hiroyuki Tanaka
Original Assignee
Mitsubishi Denki Kabushiki Kaisha
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Mitsubishi Denki Kabushiki Kaisha filed Critical Mitsubishi Denki Kabushiki Kaisha
Priority to PCT/JP2002/003839 priority Critical patent/WO2003088600A1/fr
Publication of WO2003088600A1 publication Critical patent/WO2003088600A1/fr

Links

Classifications

    • 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/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • 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/06—Registration at serving network Location Register, VLR or user mobility server
    • 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]

Definitions

  • the present invention relates to a complex network system that performs communication using a mopile IP, and relates to a communication device that operates as a foreign agent or a proxy of the foreign agent.
  • Mopile IP is proposed as a method of maintaining communication without interrupting a session when a mobile terminal having an IP (Internet Protocol) address moves from one network to another network. Have been. It is stipulated in the Internet Engineering Task Force (IETF: Request for Comment: a document that conveys information about the Internet) 2002 of the Internet Engineering Task Force (IETF).
  • IETF Internet Engineering Task Force
  • a mobile terminal can perform IP communication in a destination network other than the network to which the mobile terminal originally belongs without changing the IP address, as in the case where the mobile terminal exists in the original network.
  • Fig. 15 shows an example of the configuration of a complex network system using Mopile IP.
  • 60 is a 13? Network
  • 61 is an HA (home agent)
  • 62 and 63 are FAs (foreign agents)
  • 64 to 66 are IP access networks
  • 67 is an IP access network.
  • the illustrated composite network system is used, for example, by the same company.
  • the ISP network 60 is an ISP's own communication network owned by an Internet service provider (ISP). ISP network 60 ), And are connected to the FA 62 of the IP access network 64, the FA 62 of the IP access network 65, and the FAs 62 and 63 of the IP access network 66.
  • the HA 61 and the FAs 62, 63 are provided, for example, in a gateway for network interworking.
  • the HA 61 is a home agent for mobile terminals originally belonging to the IP access network 64 (for example, the mobile terminal 67), and the IP addresses of those terminals valid in the IP access network 64 are provided. Stores dresses (home addresses) and manages the mobility of those terminals.
  • the IP access network 64 can be considered as a LAN provided in an office of a certain company.
  • a mobile terminal (for example, mobile terminal 67) that originally belongs to the IP access network 64 can move to a location under the IP access networks 65 and 66 and connect to the ISP network 60.
  • the FA 62 enables communication between the mobile terminal and another network.
  • the moving mobile terminal registers the address indicating the FA 62 or the IP access network 65 (care-of address) with the HA 61 as a destination address of the mobile terminal through the FA 62. I do.
  • the HA 61 When the HA 61 captures the packet destined for the mobile terminal 67, the HA 61 converts the packet to a force and assigns a care-of address indicating the FA 62 or the IP access network 65 to the header of the encapsulated packet. And send. When the FA 62 receives the encapsulated packet, it extracts the original IP packet from here and transfers it to the destination mobile terminal 67.
  • the FA 63 establishes a connection between the mobile terminal and another network. Enable communication.
  • a router may not exist inside each of the IP access networks 64 to 66.
  • mobile terminal 6 7 and HA 6 1 or FA 6 Communication between 2 and 63 may be performed using the de-link layer (layer 2) of the OSI (open systems interconnection) reference model.
  • the FA for example, FA 62
  • the agent advertisement message to the IP access network ( For example, it is broadcast in the IP access network 65).
  • the mobile terminal 67 newly entered in the IP access network 65 sends a location registration request message to the FA 62, and the FA 62 transmits the location registration request message to its own address.
  • a location registration request message specifying the home address of the mobile terminal 67 is transmitted to the HA 61.
  • the HA 61 can register the care-of address of the mobile terminal 67 (the address of the FA 62 or the IP access network 65).
  • the communication device operating as the conventional FA 62 specifies a care-of address and a roof address in an agent advertisement message.
  • the IP access network 65 is modified so that it can be accessed by a plurality of mobile terminals subscribed to different Internet service providers, the IP access network 65 is only an ISP network 60 It must also be connected to an ISP network owned by another SP. In this case, the IP access network 65 is not only an FA 62 but also an additional ISP network.
  • FA must be the first hop for the mobile terminal.
  • the mobile terminal is physically connected to a location remote from the FA. In such a case, Mopile IP cannot be used.
  • the present invention has been made in order to solve the above-described problems, and uses Mopile IP even in a public IP access network that can be accessed by a plurality of mobile terminals contracted to different Internet service providers. It is an object of the present invention to obtain a communication device which can perform a communication, and which operates as a foreign agent or a proxy of a foreign agent component. Disclosure of the invention
  • a communication device includes: a plurality of mobile terminals located in a public IP access network that can be accessed by a plurality of mobile terminals subscribed to different Internet service providers; A broadcast section that broadcasts an agent advertisement message containing ISP identification information indicating a designated in-net service provider, which is one of the service providers, and an address indicating the communication device itself.
  • a receiving unit for receiving a registration request message transmitted in response to the agent advertisement message from a mobile terminal that has subscribed to the designated Internet service provider and has moved to the public IP access network.
  • a care-of address indicating the public IP access network together with the registration request message received by the receiving unit.
  • the communication device operates as a foreign agent that operates for the mobile terminal subscribed to the designated Internet service provider.
  • the agent advertisement transmitted from multiple FAs for multiple ISPs From the message, the mobile terminal can specify the FA for the ISP to which the mobile terminal has subscribed, and can communicate the specified FA with Mopile IP. Therefore, it is possible to perform communication using the mobile IP even in a public IP access network that can be accessed by a plurality of mobile terminals subscribed to different Internet service providers.
  • a communication device is a public device accessible by a plurality of mobile terminals subscribed to separate Internet service providers.
  • a plurality of mobile terminals located on a public IP access line of a public IP access network are provided with ISP identification information indicating a designated Internet service provider, which is one of the Internet service providers, and the designated Internet service provider.
  • ISP identification information indicating a designated Internet service provider, which is one of the Internet service providers, and the designated Internet service provider.
  • Evening A professional advertisement message including a communication device address indicating a foreign agent operating for a mobile terminal that has subscribed to a network service provider and has moved to the public IP access network is to be produced.
  • a receiving unit for receiving a message, and the communication device together with a registration request message received by the receiving unit.
  • the ⁇ dress showing themselves, in which a transmission unit to be transferred to the
  • the communication device operates as a proxy for the foreign agent that operates for the mobile terminal that has subscribed to the designated instantaneous Internet service provider. Since the ISP identification information is added to the Mopile IP agent advertisement message that this communication device broadcasts on behalf of the Foreign Agent, the agent sent from multiple communication devices for multiple ISPs From the advertisement message, the mobile terminal identifies the FA for the ISP to which it has subscribed, and can communicate with the identified FA via mobile IP. Therefore, it is possible to perform communication using Mopile IP even in a public IP access network that can be accessed by multiple mobile terminals subscribed to different Internet service providers. Also, since this communication device broadcasts the agent advertisement message on behalf of the FA, the FA does not need to be the first hop for mobile terminals.
  • a communication device comprises: a receiving unit that receives a registration request message from a transmitting unit of the communication device; and a care-of address indicating a public IP access network.
  • the communication device that broadcasts the agent advertisement message on behalf of the FA is interposed between the communication device as the FA and the mobile terminal, and the communication device as the FA is transmitted to the mobile terminal. There is no need to be the first hop. Therefore, even if there is a router between the mobile terminal and this communication device as the FA, communication by the mopile IP becomes possible.
  • FIG. 1 is a schematic diagram showing a composite IP network including a communication device according to Embodiment 1 of the present invention.
  • FIG. 2 is a block diagram showing a configuration of the FA, which is a communication device according to the first embodiment.
  • FIG. 3 is an information flow sequence diagram showing the operation of the first embodiment.
  • FIG. 4 is a format diagram showing the contents of an agent advertisement message used in the first embodiment.
  • Fig. 5 is a format diagram showing the contents of an ordinary advertisement message of the mopile IP.
  • FIG. 6 shows a composite IP network according to a modification of the first embodiment of the present invention. It is a schematic diagram.
  • FIG. 7 is a schematic diagram showing a composite IP network including a communication device according to Embodiment 2 of the present invention.
  • FIG. 8 is a block diagram showing a configuration of F A-GW which is a communication device according to Embodiment 2.
  • FIG. 9 is a block diagram showing a configuration of a GW which is another communication device according to the second embodiment.
  • FIG. 10 is an information flow sequence diagram showing an operation of registering a mopile IP according to the second embodiment.
  • FIG. 11 is a format diagram of the terminal information table stored by the GW of the second embodiment.
  • FIG. 12 is a format diagram of a second terminal information table stored by FA-GW of the second embodiment.
  • FIG. 13 is an information flow sequence diagram showing an operation of terminal communication of a mobile IP according to the second embodiment.
  • FIG. 14 is a schematic diagram showing a composite IP network according to a modification of the second embodiment of the present invention.
  • FIG. 15 is a schematic diagram showing a conventional composite IP network using a mopile IP.
  • FIG. 1 shows a composite IP network according to Embodiment 1 of the present invention.
  • 1 and 2 are mobile terminals
  • 3 is a public IP access network
  • 4 is a bridge
  • 5 9 is an access line
  • 6 is an uplink client
  • 7 and 8 are FAs (foreign agents and communication devices)
  • 9 and 10 are ISP networks
  • 11 and 12 are HAs (home agents)
  • 13, 15 and 16 indicate IP access networks
  • 14 indicates FA.
  • the ISP networks 9, 10 are proprietary communication networks owned by different Internet service providers (ISPs). Each of the ISP networks 9, 10 has a network (not shown).
  • the ISP network 9 is connected to the HA 11 of the IP access network 15, the FA 7 of the public IP access network 3, and the FA 14 of the IP access network 13. These HA 11 and FAs 7 and 14 are provided, for example, in a gateway for interworking a network.
  • the HA 11 is a home agent for mobile terminals (for example, mobile terminal 1) that originally belong to the IP access network 15, and those those that are valid in the IP access network 15 and the ISP network 9. Stores terminal IP addresses (home addresses) and manages the mobility of those terminals.
  • the IP access network 15 can be considered as a LAN provided in an office of a certain company.
  • a mobile terminal (for example, mobile terminal 1) which originally belongs to the IP access network 15 can move to a location under the IP access networks 3 and 13 and connect to the ISP network 9. For example, when mobile terminal 1 moves to IP access network 3, FA 7 enables communication between the mobile terminal and another network. When a mobile terminal (eg, mobile terminal 1) to which the mobile terminal belongs moves to the IP access network 13, communication between the mobile terminal and another network is enabled.
  • the ISP network 10 is composed of the HA 12 of the IP access network 16 and the public IP network. Access Network 3 is connected to FA 8. These HAs 12 and FAs 8 are provided, for example, in gateways for network interworking.
  • the HA 12 is a home agent for mobile terminals (for example, mobile terminal 2) originally belonging to the IP access network 16, and those which are effective in the IP access network 16 and the ISP network 10. It stores the IP addresses (home addresses) of these terminals and manages the mobility of those terminals.
  • the IP access network 16 can be considered as a LAN provided in an office of a certain company different from the IP access network 15.
  • a mobile terminal (for example, mobile terminal 2) that originally belongs to the IP access network 16 can move to a location under the public IP access network 3 and connect to the ISP network 10.
  • the FA 8 enables communication between the mobile terminal and another network.
  • the mobile terminal 1 is one of the terminals originally belonging to the public IP access network 15.
  • the owner of a terminal that originally belongs to the public IP access network 15 is an ISP contractor who owns the ISP network 9.
  • the mobile terminal 2 is one of the terminals originally belonging to the public IP access network 16.
  • the owner of a terminal inherently belonging to the public IP access network 16 is a subscriber of the IS P who owns the I SP network 10.
  • the mobile terminals 1 and 2 may be a mobile computer or a mobile phone handset. Each of the mobile terminals 1 and 2 has a function of generating, transmitting, receiving, and processing an E-packet according to an ordinary mopile IP.
  • the non-volatile memory of each of the mobile terminals 1 and 2 stores an identification code for identifying the ISP to which the owner has subscribed, and each of the mobile terminals 1 and 2 can identify the ISP. It is possible.
  • the ISP network 9 is connected to the IP access networks 3 and 13 via FAs 7 and 14.
  • ISP network 10 provides public IP access via FA 8. Connected to network 3.
  • IP access networks 3 13, 15, 15 and 16, and between each mobile terminal 1 and HA 11 or FA 7, 14 in each network is 0.
  • Communication is performed using the overnight link layer (Layer 2) of the SI reference model, and mobile terminal 2 and HA 12 or FA 8 also communicate using the data link layer in each network.
  • the public IP access network 3 is the data link layer (layer 2) of the OSI reference model A bridge-connected network that communicates using For example, the public IP access network 3 can use Ethernet.
  • the public IP access network 3 includes a bridge 4, at least one access line 5 connected to the bridge 4, and a plurality of application clients interconnecting the bridge 4 and the ISP FAs 7 and 8. 6
  • the public IP access network 3 has an access line 5 for public access.
  • mobile terminals 1 and 2 can access this public IP access network 3 by connecting to access line 5.
  • access line 5 for public access.
  • mobile terminals 1 and 2 can access this public IP access network 3 by connecting to access line 5.
  • two access lines 5 are shown in the figure, since multiple mobile terminals can be connected to one access line 5, the number of access lines 5 is limited to the number of expected users. It can be determined arbitrarily depending on the situation. Both the mobile terminal 1 subscribing to the ISP network 9 and the mobile terminal 2 subscribing to the ISP network 10 may be connected to the same access line 5.
  • the public IP access network 3 relays network packets using a layer 2 address that can absolutely identify a mobile terminal, for example, a MAC (media access control) address.
  • a layer 2 address that can absolutely identify a mobile terminal, for example, a MAC (media access control) address.
  • the mobile terminals 1 and 2 are split by the access line 5 of the cable. Connected to page 4.
  • the owners of the mobile terminals 1 and 2 move to the environment of the public IP access network 3 and connect to the ports of the mobile terminals 1 and 2 and the jack or port provided on the access line 5.
  • a wireless communication port through which the mobile terminal can communicate may be provided on the access line 5 so that the mobile terminal can be linked to the public IP access network 3.
  • the FA 7 interconnecting the public IP access network 3 and the ISP network 9 uses the mobile terminal (for example, the mobile terminal 1) of the subscriber of the ISP network 9 originally located in the IP access network 15.
  • the mobile terminal can communicate with another network.
  • the FA 8 interconnecting the public IP access network 3 and the ISP network 10 uses the mobile terminal (for example, the mobile terminal 2) of the ISP network 10 subscriber who is originally located in the IP access network 16.
  • the mobile terminal can communicate with other networks.
  • FIG. 2 shows the configuration of F A7.
  • 7a indicates a processing device
  • 7b indicates a first communication unit
  • 7c indicates a second communication unit.
  • the first communication unit (broadcast unit, reception unit) 7b communicates with mobile terminals in the public IP access network 3.
  • the first communication unit 7b also broadcasts an agent advertisement message described later and receives a location registration request message from the mobile terminal.
  • the second communication unit 7c performs communication using the ISP network 9.
  • the second communication unit 7c also transfers a position registration request message described later.
  • the processing device 7a corrects the information received by the first communication unit ⁇ b in accordance with the network topology of the ISP network 9 and passes it to the second communication unit ⁇ c, and the second communication unit The information received at 7c is corrected according to the network topology of the public IP access network 3 and passed to the first communication unit 7b.
  • FA 8 has a similar structure to FA 7. Unlike a normal LAN, this public IP access network 3 is connected to a plurality of ISP networks 9,10. The mobile terminals 1 and 2 that have moved to the public IP access network 3 must notify their HAs 11 and 12 that they have moved to the public IP access network 3. For this purpose, mobile terminals 1 and 2 need to identify FAs 7 and 8 that operate for themselves. Next, the operation will be described.
  • FIG. 3 which is an information flow sequence diagram regarding the operation of the mobile terminal 1 will be referred to.
  • FAs 7 and 8 for different ISPs send agent advertisement messages to many mobile terminals (including mobile terminals 1 and 2) in public IP access network 3 via bridge 4. Broadcast periodically. However, the timing at which FA 7 and FA 8 broadcast agent advertisement messages may be quite different.
  • FIG. 4 shows the details of the agent advertisement message.
  • the agent advertisement message used in this embodiment is the same as the normal mobile IP agent advertisement message shown in FIG. 0 is added.
  • the usual Mopile IP agent advertisement message shown in Figure 5 is: ICMP (internet control message protocol specified in RFC 1256) and RFC 202 It adds some specified extensions.
  • the agent advertisement message used in this embodiment is composed of an IP header, an ICMP router advertisement, a mobility agent advertisement extension, a prefix length extension, and an ISP.
  • Has display extension 20 the prefix length extension is optional and need not be used.
  • the IP header is specified in RFC 791. Details are not shown, The IP header contains information such as the service type, the total length of the message, the identifier, the IP source address (for example, if the FA 7 sends a message, the address of the FA 7), and the IP destination address. . In the agent advertisement message, a value indicating a multicast is used as the IP destination address.
  • the I CMP rule advertisement is specified by RFC 125 and represents the I CMP rule available to the target mobile terminal.
  • the agent advertisement message sent by the FA 7 is essentially the IP access network.
  • the ICMP router advertisement indicates FA 7.
  • the total number of addresses in the ICMP router advertisement is 1, and the router address [1] indicates the address of FA7. Since only F A7 is available, the rule address [2] and subsequent fields are not used.
  • the mobility agent advertisement extension is specified in RFC 2022, and represents a foreign agent or network available to the target mobile terminal. For example, for an agent advertisement message sent by the FA 7, the mobility agent advertisement extension indicates the FA 7 or the public IP access network 3. In this case, the care-of address [1] during the mobile agent advertisement extension indicates the address of the FA 7 or the public IP access network 3. Since the only available FAs are the FA 7 or the public IP access network 3, the care-of address [2] and the following fields are not used.
  • the prefix length extension is specified in RFC 2002 and is optionally used for agent advertisement messages.
  • the prefix length extension indicates the network number of the router address indicated in the I CMP router advertisement.
  • Use Agent Advertising messages sent by FA 7 Since only one possible ICMP file is FA 7, only the prefix length [1] is used. The mobile terminal that has received the agent advertisement message can recognize that it has moved from the network where it was previously located to another network by referring to the prefix length.
  • the ISP display extension 20 used in this embodiment stores ISP information indicating an ISP available to the target mobile terminal.
  • the type field 21 of the ISP display extension 20 indicates that the following information includes the ISP information. 1 3? Identification code 2 2 indicates the ISP that can be used by the mobile terminal to be broadcast.
  • the ISP identification code 22 indicates the ISP that owns the ISP network 9.
  • the agent advertisement message transmitted by the FA 8 indicates the ISP that owns the ISP network 10.
  • the non-volatile memory of the mobile terminal to be linked to the FA 7 (for example, mobile terminal 1) has an identification code for identifying the ISP (ISP corresponding to the ISP network 9) contracted by the owner. Is stored in the non-volatile memory of the mobile terminal to be linked to the FA 8 (for example, mobile terminal 2), and identifies the ISP (ISP corresponding to the ISP network 10) contracted by the owner. Contains the identification code.
  • the agent advertisement message becomes itself. It can be recognized as a message for ISPs (ISP information check in Fig. 3). Specifically, upon receiving an agent advertisement message transmitted from Bridge 4 using FA 7 or FA 8 as a source, mobile terminal 1 transmits from ISP display extension 20 of the agent advertisement message. The ISP identification code 22 is taken out, and the ISP identification code 22 stored therein and the ISP identification code 22 are compared. If the message is an agent advertisement message transmitted from the FA 8, the mobile terminal 1 identifies that this message is not a message for itself by the ISP identification code 22, and discards the message.
  • mobile terminal 1 uses ISP identification code 22 to convert this message to its own message (the ISP to which it has subscribed). Identify the IP source address of the IP header in this message.
  • the mobile terminal 1 sends out a location registration request message of the Mopile IP having the held IP source address as a destination.
  • the destination address is the address of FA7. Since the home address indicating mobile terminal 1 is specified in the location registration request message, FA 7 recognizes that mobile terminal 1 having this home address has moved to public IP access network 3.
  • the FA 7 Upon receiving the location registration request message, the FA 7 associates the address (for example, MAC address) of the mobile terminal 1 valid in the public IP access network 3 with the home address of the mobile terminal 1 and performs an internal process. Store and send another type of location registration request message (second location registration request message) to the HA 11.
  • This second location registration request message specifies the home address of the mobile terminal 1 and the IP address (care-of address) indicating the transmission port of the FA 7 and the public IP access network 3. Therefore, the HA 11 recognizes that the mobile terminal 1 is in a state where it can receive the service by the FA 7.
  • the HA 11 Upon receiving the second location registration request message, the HA 11 updates the registration information portion of the mobile terminal 1 in its own storage unit according to the location registration request message. That is, the destination address of mobile terminal 1 And register the notice address. At the time of this location registration, the authentication processing of the mobile terminal 1 and the parameter inspection may be performed, but the detailed description thereof will be omitted.
  • the mobile terminal 1 can perform the IP communication using the FA 7. For example, when HA 11 captures a packet addressed to mobile terminal 1, HA 11 encapsulates the packet and assigns a care-of address indicating public IP access network 3 to the header of the encapsulated packet. Send. When the F A 7 receives the encapsulated packet, it extracts the original IP packet from here and transfers it to the destination mobile terminal 1. In the reverse communication, the mobile terminal 1 transmits a packet via the FA 7.
  • the mobile terminal 2 receives the broadcasted agent advertisement message from the FA 7 and FA 8
  • the ISP identification code 22 in the agent advertisement message indicates that the mobile terminal 2 has an appropriate ISP identification code for itself.
  • Mopile IP By specifying the FA 8 and communicating with the FA 8, it is possible to execute communication compliant with Mopile IP. After the mobile terminal recognizes the agent advertisement message for itself, the communication between these FA and HA is the same as that of the ordinary mobile IP.
  • each of the plurality of ISPs is transmitted from the FA:
  • the mobile terminal identifies the FA for the ISP with which the mobile terminal is subscribed from the agent advertisement message received, and the mobile terminal can communicate with the identified FA via Mopile IP. can get.
  • FIG. 6 shows a composite IP network according to a modification of the first embodiment of the present invention.
  • the HA 11 corresponding to the ISP network 9 is connected only to the ISP network 9, and the mobile terminal of the ISP subscriber corresponding to the ISP network 9 (for example, a mobile terminal).
  • IP access network 15 in Fig. 1 There is no IP access network (IP access network 15 in Fig. 1) to which the mobile terminal 1) originally belongs.
  • the HA 12 corresponding to the ISP network 10 is connected only to the ISP network 10, and the mobile terminal (for example, the mobile terminal 2) of the ISP contractor corresponding to the ISP network 10 is inherently connected.
  • the mobile terminal (for example, mobile terminal 1) of the ISP contractor corresponding to ISP network 9 is arbitrarily connected to IP access network 13 or public IP access network 3. It is possible to move to access. Also, the mobile terminal (for example, mobile terminal 2) of the ISP subscriber corresponding to the ISP network 10 can be arbitrarily moved to access the public IP access network 3 or another network (not shown). . Also in the composite IP network of such a modification, the same effects as achieved in the first embodiment can be achieved.
  • FIG. 7 shows a composite IP network according to Embodiment 2 of the present invention.
  • 30 is a public IP access network
  • 31 is a public IP access line
  • 32 is a public IP access line transit network
  • 33 is a GW (gateway)
  • 34 is a router
  • 3 Reference numerals 5 and 36 denote FA—GW (foreign agent gate ⁇ A)
  • 37 and 38 denote connection ports
  • 39 denotes a communication terminal.
  • the same reference numerals are used to indicate the same components as those in FIG. 1, and these components will not be described in detail.
  • mobile terminal 1 is one of the terminals inherently belonging to public IP access network 15.
  • the owner of a terminal originally belonging to the public IP access network 15 is an ISP contractor who owns the ISP network 9
  • the mobile terminal 2 is one of the terminals originally belonging to the public IP access network 16.
  • the owner of a terminal originally belonging to the public IP access network 16 is an ISP contractor who owns the ISP network 10.
  • the mobile terminals 1 and 2 may be a mobile computer or a mobile phone handset. Each of the mobile terminals 1 and 2 has a function of generating, transmitting, receiving, and processing an IP bucket according to a normal mopile IP.
  • the non-volatile memory of each of the mobile terminals 1 and 2 stores an identification code for identifying the ISP to which the owner subscribes, and each of the mobile terminals 1 and 2 must identify the ISP. Is possible.
  • the ISP network 9 is connected to the IP access network 13 via the FA 14, and the public IP access line relay network of the public IP access network 30 is connected via the FA-GW 35, particularly the connection port 37. 3 Connected to 2. Further, the ISP network 10 is connected to the public IP access line relay network 32 of the public IP access network 30 via 810 ⁇ 36, in particular, the connection port 38.
  • the public IP access network 30 is composed of at least one GW 33, at least one public IP access line 31, one public IP access line relay network 32, a router 34 and a FA—GW 35, 36. Is provided.
  • the public IP access line transit network 32 can route IP packets between the GW 33, 34, and FA-GW 35, 36 by setting the routing protocol and routing protocol. It is a net.
  • the public IP access line relay network 32 is a network that communicates using the network layer (layer 3) of the 0SI reference model.
  • the network 34 is a normal network that relays packets between the GW 33 and the FAs 35 and 36, and is a network topology in the public IP access line relay network 32. Transfer the IP packet according to.
  • the public IP access network 30 has a public IP access line 31, and each public IP access line 31 is connected to the public IP access line relay network 3 by the GW 33. Connected to two.
  • mobile terminals 1 and 2 can access this public IP access network 30 by connecting to public IP access line 31.
  • two public IP access lines 31 are shown in the figure, since a plurality of mobile terminals can be connected to one public IP access line 31, the number of public IP access lines 31 is It can be arbitrarily determined according to the number of users planned. Both the mobile terminal 1 subscribing to the ISP network 9 and the mobile terminal 2 subscribing to the ISP network 10 may be connected to the same public IP access line 31.
  • the public IP access line 31 connecting the GW 33 and the mobile terminal communicates using the data link layer (Layer 2) of the OSI reference model.
  • Layer 2 the data link layer
  • the public IP access line 31 can use Ethernet.
  • the public IP access line 31 uses a layer 2 address that can absolutely identify a mobile terminal, for example, a MAC address.
  • mobile terminals 1 and 2 are connected to a public IP access line relay network 32 by a cable public IP access line 31.
  • the owners of the mobile terminals 1 and 2 move to the environment of the public IP access network 30, and the ports of the mobile terminals 1 and 2 and the jack or port provided on the public IP access line 31.
  • a wireless communication port through which the mobile terminal can communicate may be provided on the public IP access line 31 so that the mobile terminal can link to the public IP access network 30.
  • FA—GW 35 for ISP network 9 is originally located in IP access network 15 It is a gateway that functions as a foreign agent for mobile terminals (for example, mobile terminal 1) of subscribers of the existing ISP network 9. That is, when such a mobile terminal moves to the public IP access network 30, the FA-GW 35 enables communication between the mobile terminal and another network.
  • the FA-GW 35 has a connection port 37 connected to the ISP network 9 and the public IP access line relay network 32.
  • the network & 13 for the network 13 is the domain for the mobile terminal (for example, mobile terminal 2) of the subscriber of the ISP network 10 originally located in the IP access network 16. It is a gateway that functions as an agent. That is, when such a mobile terminal moves to the public IP access network 30, the FA-GW 36 enables the mobile terminal to communicate with another network.
  • the F A—GW 36 is provided with a connection port 38 connected to the I SP network 10 and the public IP access line relay network 32.
  • FIG. 8 shows the configuration of F A—GW 35.
  • 35a indicates a processing device
  • 35b indicates a first communication unit (receiving unit)
  • 35c indicates a second communication unit (transmitting unit)
  • 35d indicates a storage unit.
  • the communication units 35b and 35c are provided in the connection port 37, and the first communication unit 35b communicates with ⁇ 33 via the public IP access line relay network 32.
  • the first communication unit 35b also receives a location registration request message from the GW 33 described later.
  • the second communication unit 35 c performs communication using the ISP network 9.
  • the second communication unit 35c also transfers a location registration request message to the HA 11 described later.
  • the processing unit 35a corrects the information received by the first communication unit 35b in accordance with the network topology of the ISP network 9, passes it to the second communication unit 35c, and The information received by the communication unit 35c is corrected according to the network topology of the public IP access line relay network 32 and passed to the first communication unit 35b. With these operations, the processing unit 35a is stored in the storage unit 35d. Acquired information as needed.
  • FA-GW35 also has a similar configuration to FA-GW35.
  • addresses 5 ° to 54 are stored in the storage section 35d.
  • the FA—GW 35 has its own IP address 51 valid in the public IP access line transit network 32.
  • This IP address 51 is an address conforming to the network topology of the public IP access line transit network 32, and is used only in the public IP access line transit network 32, It is not notified to the roo (not shown) in network 9.
  • the FA-GW 35 has its own IP address 54 valid in the ISP network 9.
  • the IP address 54 is an address conforming to the network topology 1 of the ISP network 9, is used only in the ISP network 9, and is used in the public IP access line relay network 32. Will not be notified.
  • FA valid on the public IP access line transit network 32—IP address 51 on the GW 35 and IP address 54 valid on the ISP network 9 will differ if the corresponding network topology is followed. Value may be indicated.
  • connection port 37 mounted on the FA-GW 35 has its own IP address 50 valid in the public IP access line relay network 32.
  • This IP address 50 is a format conforming to the network topology of the public IP access line transit network 32, and is used only in the public IP access line transit network 32. However, it is not notified to the router (not shown) in the ISP network 9.
  • the connection port 37 has its own IP address 53 valid in the ISP network 9.
  • This IP address 53 is an address conforming to the network topology 1 of the ISP network 9, is used only in the ISP network 9, and is used in the public IP access line relay network 32. Not notified on evening 34.
  • public The IP address 50 of the connection port 37 valid for the public IP access line transit network 32 and the IP address 53 valid for the ISP network 9 are different if they follow the respective network topologies. Value may be indicated.
  • connection port 37 has a care-of address 52 effective in the ISP network 9.
  • the care-of address 52 is an address indicating the public IP access line relay network 32 in a format conforming to the network topology of the ISP network 9, and is used only within the ISP network 9, and is used only in the ISP network 9. It is not notified to the router 34 in the access line relay network 32.
  • the care-of address 52 may be the same as the IP address 50 indicating the connection port 37 itself.
  • a routing table is set so that the connection port 37 can be routed based on the care-of address 52.
  • the FA—GW 36 for the ISP network 10 has an IP address 51 1 indicating its own in the public IP access line relay network 32 and an IP address indicating its own in the ISP network 10.
  • the connection port 38 of the FA—GW 36 also has an IP address 50 indicating its own valid in the IP access line relay network 32 and an IP address 5 indicating its own valid in the ISP network 10.
  • the ISP network 10 have a care-of address 52 that is valid.
  • the care-of address 52, the IP address 53 of the connection port valid in the ISP network, and the IP address 54 of the FA—GW valid in the SP network differ for each IPS (for each FA—GW). Is also good.
  • FIG. 9 shows the configuration of GW33.
  • 33a denotes a processing device
  • 33b denotes a first communication unit
  • 33 denotes a second communication unit
  • 33d denotes a storage unit.
  • the first communication unit (broadcast unit, reception unit) 33 b communicates with mobile terminals on the public IP access line 31. Agent advertising
  • the first communication unit 33b also performs broadcast of messages and reception of location registration request messages from mobile terminals.
  • the second communication unit 33c performs communication using the public IP access line relay network 32.
  • the second communication unit 33c also transfers a location registration request message described below to the FA-GW.
  • the processing unit 33a corrects the information received by the first communication unit 33b in accordance with the network topology of the public IP access line relay network 32 and sends it to the second communication unit 33c. Then, the information received by the second communication unit 33c is corrected according to the network topology of the public IP access line 31 and passed to the first communication unit 33b. Through these operations, the processing device 33a acquires the information stored in the storage unit 33d as necessary.
  • each GW 33 stores, in its own storage unit 33 d, an IP address 50 of a connection port 37, 38 valid for the network 32, and a valid address for the network 9 of the network 9.
  • the care-of address 52 of the connection ports 37 and 38, the FA valid for the network 32—the ISP identification code indicating the ISP corresponding to the IP address 51 of the GW 35 and 36 and the networks 9 and 10 Stores 1 2 2 and Mopile IP parameters. That is, each GW 33 knows this information in advance.
  • each GW 33 broadcasts an agent advertisement message to the corresponding public IP access line 31 on behalf of both the FA-GW 35 and the FA-GW 36.
  • the agent advertisement message sent by GW33 on behalf of FA-GW35 is different from the agent advertisement message sent by GW33 on behalf of FA-GW36.
  • this public IP access network 30 is connected to a plurality of ISP networks 9,10.
  • the mobile terminals 1 and 2 that have moved to the public IP access network 30 must notify their HAs 11 and 12 that they have moved to the public IP access network 30. To do this, The mobile terminals 1 and 2 need to identify the FA—GWs 35 and 36 that operate for themselves. Agent advertisement messages are used for this identification.
  • FIG. 10 is an information flow sequence diagram for the operation of the mobile terminal 1.
  • the router 34 in the public IP access network 30 is omitted in FIG. 10 because it performs only transfer of IP packets.
  • each GW 3 3 has a number of mobile terminals (mobile terminals 1 and 2) connected to the corresponding public IP access line 31. (Including ST), the agent advertisement message is broadcast periodically (steps ST101, ST102). However, the timing of broadcasting the agent advertisement message for the FA-GW35 and the agent advertisement message for the FA-GW36 may be considerably different.
  • the agent advertisement message used in this embodiment is also a message including the ISP display extension 20 shown in FIG. FA—Agent 1 for GW 35, advertising message shows that the IP source address in the IP header is the IP address of FA-GW 35 that is valid on the public IP access line transit network 32 1 Is specified.
  • the IP address of FA—GW35 is specified in the rule address [1], and the rule address [2] and subsequent fields are not used.
  • the care-of address [1] specifies the care-of address 52 of F A—GW 35, and the care-of address [2] and subsequent fields are not used.
  • the ISP possessing the ISP network 9 is represented by the ISP identification code 22.
  • the FA—Agent Advertising Message for GW36 The IP address 51 of the FA—GW 36 valid for the public IP access line relay network 32 is specified as the IP source address in the P header.
  • the FA-GW36 IP address is specified in the router address [1], and the router address [2] and the following fields are not used.
  • the care-of address [1] specifies the care-of address 52 of FA—GW36, and the care-of address [2] and subsequent fields are not used.
  • the ISP display extension 20 the ISP that owns the ISP network 10 is represented by the ISP identification code 22.
  • the non-volatile memory of the mobile terminal (for example, mobile terminal 1) to be linked to the FA—GW 35 identifies the ISP (ISP corresponding to the ISP network 9) contracted by the owner.
  • the identification code is stored, and the non-volatile memory of the mobile terminal (for example, mobile terminal 2) that should be linked to the FA—GW 36 corresponds to the ISP (ISP network 10) contracted by the owner. ISP) is stored.
  • the mobile terminal determines that the agent advertisement message is for itself. (ISP identification in step ST103 in FIG. 10). Specifically, upon receiving the broadcasted agent advertisement message from the GW 33, the mobile terminal 1 extracts the ISP identification code 22 from the ISP display extension 20 of the agent advertisement message and sends it to itself. Compare the stored ISP identification code with ISP identification code 22. FA—If it is an agent advertisement message for GW 36, mobile terminal 1 identifies that this message is not a message for itself by ISP identification code 22; Discard this message.
  • the mobile terminal 1 uses the ISP identification code 22 to identify this message as a message for itself (agent advertisement message from the ISP to which it is subscribed), and determines the message.
  • the IP source address of the P header in the table is retained (the ISP in step ST103 in FIG. 10 is retained).
  • the mobile terminal 1 transmits a location registration request message to register the mopile IP (step ST104). In other words, it sends a mopile IP position registration request message using the held IP source address as the destination address.
  • the format of the location registration request message is the same IP packet as that used in normal mobile IP, the location registration request message is not layered for communication over the public IP access line 31. It is stored in two frames or a layer 2 packet.
  • the retained IP source address is the IP address 51 of the FA—GW 35 that is valid in the public IP access line relay network 32, but this location registration request message is in the middle of GW3. 3 received. Since the home address indicating the mobile terminal 1 is specified in the location registration request message, the GW 33 transmits the mobile terminal 1 having the home address to the public IP access line 31 corresponding to itself. Recognize that the link has been made.
  • the GW 33 Upon receiving the location registration request message, the GW 33 creates the terminal information table 71 shown in FIG. 11 in step ST105 and stores it in its own storage section 33d.
  • the terminal information table 71 has a connection port 72, a terminal IP address 73, a terminal layer 2 address 74, FA—GW IP address 75, FA— Each field has the IP address 76 of the GW port.
  • the connection port 72 is a port to which the mobile terminal 1 in the GW 33 is linked (the mobile terminal 1 uses the port for transmitting the location registration request message). Port).
  • the terminal IP address 73 is the IP source address of the IP packet received from the mobile terminal 1, that is, the home address of the mobile terminal 1.
  • the terminal layer 2 address 74 is the source address (address of the mobile terminal 1 in layer 2) specified by the layer 2 packet or the layer 2 frame in which the location registration request message received from the mobile terminal 1 is stored. is there. If the layer 2 used by the public IP access line 31 is Ethernet, the terminal layer 2 address 74 may be a MAC address.
  • the IP address 75 of the FA-GW is the IP destination address of the IP packet received from the mobile terminal 1, that is, the IP address 51 of the FA—GW 35 valid in the public IP access network 30. .
  • the terminal information table 71 in which the mobile terminal 1 is associated with information necessary for communication in this way is referred to by the GW 33 in subsequent data transfer.
  • FA—GW port IP address 76 is not written in step ST105.
  • the IP address 76 of the FA-GW port will be described later.
  • GW33 which has received the IP packet of the location registration request message, generates a second location registration request message, and transmits it to FA-GW35 via file overnight 34 in step ST106.
  • This second location registration request message is obtained by transmitting the location registration request message (IP packet) issued by the mobile terminal 1 to the IP routing table of the network topology of the public IP access line relay network 32.
  • IP packet location registration request message
  • This is an IP bucket encapsulated according to a pull.
  • the outer IP header of the IP packet that has been converted into a packet includes the IP address of FA—GW35 as the IP destination address (the IP destination address of the IP packet received from mobile terminal 1). ) Is specified, and mobile terminal 1 in GW3 3 is linked as the IP source address.
  • the FA—GW 35 that has received the second registration request message that has been force-packaged transmits the outer IP header in step ST107 because the IP destination address in the outer IP header indicates itself. Remove and extract the original location registration request message in IP bucket format (decapsulate). Further, since the IP destination address of the decapsulated IP packet also indicates FA—GW35, FA—GW35 examines the message content of the original IP packet. If the original IP bucket is a location registration request message, the FA—GW 35 creates the second terminal information table 77 shown in FIG. 12 based on the encapsulated location registration request message. Then, it stores it in its own storage unit 35 d.
  • the second terminal information table 77 has fields of a terminal IP address 78, a GW IP address 79 and a care-of address 80.
  • the terminal IP address 78 is a home address indicating the IP source address indicated in the inner IP header of the second position registration request message converted into a force, that is, the mobile terminal 1.
  • the IP address 79 of the GW is the IP source address indicated in the outer IP header of the second location registration request message, that is, the IP address of the port of the GW 33 to which the mobile terminal 1 is linked, particularly the mobile terminal. This is the IP address of the port that received the location registration request message from 1.
  • Care-of address 80 indicates connection port 37 of FA—GW35 13?
  • the care-of address 52 (see FIG. 8) valid in the network 9 and the FA—GW 35 receives the care-of address 5 from the care-of address field in the payload of the second location registration request message. Copy 2.
  • the mobile terminal 1, the GW 33 to which it is connected and the second terminal information table 77 associated with the FA-GW 35 are stored in the FA-GW 35.
  • the IP packet received and decapsulated by the FA—GW 35 is an original IP packet from the mobile terminal 1, and the message in the IP packet is a location registration request message. Therefore, in step ST108, the FA-GW35 performs the registration process of the mopile IP. In this registration process, as in the normal registration process of the mopile IP, the validity check such as the authentication and the mopile IP parameter is performed based on the information included in the original location registration request message.
  • the FA_GW 35 If the results of these authentication and validity checks are successful, the FA_GW 35 generates a third location registration request message and the IP destination address of this third location registration request message. Then, the output port of FA—GW35 is determined and transmitted to the ISP network 9 in step ST109.
  • This third location registration request message is obtained by rewriting the IP header of the location registration request message (IP packet decapsulated by FA—GW 35) issued by the mobile terminal 1.
  • the HA 11 IP address is specified as the IP destination address, and the IP—address is connected to the ISP network 9 to communicate with the HA 11 FA—GW 35 Port IP address is specified.
  • the HA 11 address may be copied from the home agent field in the pay mouth of the original location registration request message to the IP destination address.
  • the ISP network 9 transfers the third location registration request message to the HA 11 according to the routing table of the network topology.
  • HA 11 Upon receiving the third location registration request message, HA 11 performs an authentication process and a registration validity check in the same manner as a normal mobile IP registration process, and a result of the authentication process and the validity check. If the password is normal, save the home address of mobile terminal 1 in association with care-of address 52 of connection port 37. (Step ST110).
  • HA11 transmits a registration response message to FA-GW35.
  • the IP source address in the IP header of this registration response message is the IP address of HA11, and the IP destination address is the IP packet of the received third location registration request message.
  • Use the IP source address IP address of the port that communicates with HA 11 on FA-GW35).
  • FA—IP address of the port that communicates with HA 11 in GW 35 FA—GW 35 receiving the registration response message from HA 11 proceeds to step ST 1 1 2 Then, a normal mobile IP registration response process is performed, and an IP packet of a different type of registration response message is generated.
  • the IP destination address in the IP header of this IP packet is the home address of the mobile terminal 1
  • the IP source address is the IP address of the FA—GW 35 that is valid in the public IP access line relay network 32. Is one.
  • the home address of the mobile terminal 1 may be copied from the home address field of the mobile node in the payload of the original registration response message from the HA 11 to the IP destination address.
  • the IP packet of this registration response message is encapsulated so as to conform to the public IP access line relay network 32.
  • the IP address of the GW33 port to which the mobile terminal 1 is linked is specified as the IP destination address
  • the public IP access line relay is specified as the IP source address.
  • the IP address 50 of the connection port 37 valid on the network 32 is specified.
  • the FA-GW 35 searches the second terminal information table 77 (FIG. 12).
  • the second terminal information table 77 a terminal IP address 78 matching the home address of the mobile terminal 1 is found, and the IP address of the GW corresponding to the terminal IP address 78 is found. Copy 7 9 to the IP destination address in the outer IP header. Further, in the second terminal information table 77, the care-of address 80 corresponding to the terminal IP address 78 is captured, and the connection corresponding to the care-of address 80 (that is, the care-of address 52) is acquired. Copy the IP address 50 (Fig. 8) of port 37 to the IP source address of the outer IP header.
  • the IP address of the GW33 port to which the mobile terminal 1 is linked is used as the IP destination address in the outer IP header.
  • the IP address 50 of the connection port 37 valid in the public IP access line transit network 32 is specified as the IP source address in the outer IP header, and the IP destination address in the inner IP header is specified.
  • the home address of mobile terminal 1 is specified, and for the IP source address in the inner IP header, the IP address 51 of FA—GW 35 that is valid in the public IP access line relay network 32 is specified. Is done.
  • the FA—GW 35 transmits the encapsulated IP packet to the target GW 33 as a second registration response message using the connection port 37 corresponding to the IP source address in the outer IP header. (Step ST 1 1 4).
  • the GW 33 Upon receiving the encapsulated IP packet (second registration response message), the GW 33 decapsulates the IP packet in step ST115. That is, the IP destination destination in the outer IP Since the dress indicates the port of GW33, remove the outer IP header and take out the inner IP packet.
  • the GW 33 in step ST116, sets the IP destination address of the inner IP header, that is, the home address of the mobile terminal 1, and the outer IP header.
  • the terminal information table 71 in FIG. 11 is searched based on the IP source address, that is, the IP address 51 of the FA—GW 35 effective in the public IP access line relay network 32. Specifically, in the terminal information table 71, the terminal IP address ⁇ 3 that matches the home address of the mobile terminal 1 and the IP address 75 of the FA—GW that matches the IP address 51 are found. Write the IP address 50 of the connection port 37 of the FA_GW 35 valid in the public IP access line relay network 32 to the IP address 76 of the FA—GW port corresponding to these, Used for subsequent transfers. In this case, the IP address 50 may be copied from the IP source address in the outer IP header of the second registration response message that has been converted into the IP address 76 of the FA—GW port. .
  • the GW 33 connects the connection port 72 corresponding to the terminal IP address 73 matching the home address of the mobile terminal 1 and the IP address 75 of the FA GW. And terminal layer 2 address 7 4 are captured.
  • the connection port 72 indicates the port to which the mobile terminal 1 in the GW 33 is linked, and the terminal layer 2 address 74 indicates the address of the mobile terminal 1 in layer 2.
  • the GW 33 uses the decapsulated IP packet as a third registration response message to the public IP access line.
  • the third registration response message is the inner packet of the second response message
  • the home address of the mobile terminal 1 is specified in the destination address in the IP header
  • the IP address 51 of the FA—GW 35 valid for the public IP access line relay network 32 is specified.
  • a third registration response message is stored in a Layer 2 frame or a Layer 2 bucket, and the Layer 2 frame or Layer 2 packet is stored.
  • the terminal layer 2 address 74 indicating the mobile terminal 1 is used.
  • connection port 72 need not be determined.
  • the mobile terminal 1 that has received the third registration response message enters a state in which communication can be started, similarly to the normal mobile IP.
  • the mobile terminal 1 that originally belongs to the IP access network 15 but is connected to the public IP access line 31 is replaced by the communication terminal 39 (the seventh terminal) that is located in the IP access network 15.
  • the operation when communicating with (Fig.) Will be described. This description refers to the information flow sequence diagram of FIG.
  • the mobile terminal 1 sends an IP packet addressed to the communication terminal 39 to the public IP access line 31.
  • This IP packet has the same format as the IP packet of a normal mobile IP.
  • the IP destination address is the IP address of the communication terminal 39
  • the IP source address is the IP source address.
  • the home address of mobile terminal 1 is specified.
  • the IP address of the communication terminal 39 is recorded in a file such as a host address file stored in the mobile terminal 1.
  • the GW 33 receiving the IP packet in step ST202, stores the IP packet in the layer 2 packet or the source address specified by the layer 2 frame (the mobile terminal 1's layer 2 address). Search for the terminal information table 71 (Fig. 11) using the dress) as a key.
  • the terminal information table 71 finds a terminal layer 2 address 74 that matches this source address, and the IP address of the FA—GW port corresponding to the terminal layer 2 address 74 (IP address 50 of connection port 37) is captured. That is, the transfer destination is determined.
  • the reason why the terminal information template 71 is searched using the layer 2 address as a key in step ST202 is that the layer 2 address, for example, the MAC address is uniquely assigned to the mobile terminal. .
  • the layer 2 address for example, the MAC address is uniquely assigned to the mobile terminal.
  • various IPs are assigned independently to the IP address (home address) of the mobile terminal, there may be a plurality of mobile terminals having the same IP address for different IPSs. Moreover, it cannot be said that there is no possibility that such a mobile terminal accidentally links to the same public IP access line 31.
  • the terminal information table 71 since the duplicate terminal IP address 73 exists, the GW 33 cannot uniquely determine the transfer destination of the IP packet. 7 Duplicate terminal layer 2 address 74 in 1 cannot be registered.
  • the GW33 encapsulates the original IP packet.
  • the IP destination address is the IP address 76 of the FA—GW port determined in step ST202, and the IP source address. Is the IP address of the receiving port of GW33.
  • GW33 transfers the encapsulated IP packet to FA-GW35 in step ST204.
  • the FA—GW 35 receives this force-packaged IP bucket, it decapsulates it because the IP destination address of the outer IP header is the IP address of its own connection port 37. Then, the inner IP packet is taken out (step ST205). Since the IP destination address of the extracted IP packet is the IP address of the communication terminal 39 and is an effective address in the ISP network 9, the FA-GW 35 follows the routing table of the ISP network 9. Then, a routing decision is made, and the IP packet is transmitted to the communication terminal 39 via the ISP network 9 (steps ST206 and ST207).
  • the communication terminal 39 transmits an IP packet to the mobile terminal 1
  • the communication terminal 39 generates an IP bucket 1 in which the IP destination address is the home address of the mobile terminal 1 and the IP source address is the IP address of the communication terminal 39 itself. Sends to ISP network 9 with 0.
  • the IP packet is transmitted according to the home address of the mobile terminal 1, so that the IP packet transmitted from the communication terminal 39 is received by the HA 11.
  • the IP destination address of the IP packet indicates the mobile terminal 1, and the HA 11 stores the care-of address of the mobile terminal 1 by the registration of the mobile IP. Accordingly, HA 11 capsulates the received IP packet in accordance with the normal processing of the mopile IP (step ST 211).
  • the IP destination address is the care-of address of the mobile terminal 1 (the care-of address 52 indicating the connection port 37) and the IP source address is the HA 11 It is an IP address.
  • step ST212 the HA 11 sends the encapsulated IP packet to the ISP network 9.
  • the encapsulated IP packet Since the care-of address is also valid in the ISP network 9, the encapsulated IP packet is transferred to the connection port 37 of the FA-GW35 indicated by the care-of address.
  • the operation from step ST210 to step ST212 is equivalent to the operation of a normal mopile IP.
  • the port of the care-of address in the FA-GW 35 that is, the public IP access network connection port 37 receives the encapsulated IP packet of Mopile IP
  • the IP destination address of the outer IP header is the connection port. Since the address is the care-of address shown in FIG. 37, the FA-GW 35 decapsulates and extracts the inner IP packet (step ST213).
  • the FA-GW35 searches for the second terminal information table 77 (Fig. 12). Specifically, in the second terminal information template 77, a terminal IP address 78 that matches the IP destination address of the inner IP packet, that is, the home address of the mobile terminal 1, is found. The GW IP address 79 corresponding to the terminal IP address 78 is captured. That is, the transfer destination is determined.
  • step ST 215 the FA-GW 355 forces the inner IP packet again.
  • the IP destination address is valid for the GW IP address 79 obtained in step ST214, and the IP source address is valid for the public IP access network 30. IP address 50 of connection port 37.
  • the FA-GW 35 sends the encapsulated IP packet to the public IP access line relay network 32.
  • routing is performed using the IP destination address (IP address indicating the port of GW33) of the outer IP header of the IP packet converted into a capsule and the capsule.
  • IP packet is transferred to GW33.
  • the GW 33 refers to the IP destination address in the outer IP header of the encapsulated IP packet and recognizes that this indicates the port of the GW 33 itself in step ST 217. Remove the outer IP header and remove the inner IP packet (decapsulate).
  • the GW 33 further checks the IP source address (FA—IP address 50 of the connection port 37 of the GW 35) and the IP destination address (moved) of the inner IP header in the outer IP header.
  • the terminal information table 71 shown in FIG. 11 is searched using the terminal 1's home address) as a key. That is, the terminal IP address 73 matching the home address of the mobile terminal 1 and the IP address 76 of the FA—GW port matching the IP address 50 are found, and the connection ports corresponding to these are found.
  • the terminal 72 and the terminal layer 2 address 74 In this way, the port and the layer 2 address used to deliver the IP packet to the mobile terminal 1 are determined.
  • connection port 72 need not be obtained if the force-packaging IP bucket is routed to the output port of the GW 33.
  • the ISP 33 is added to the agent advertisement message of the Mopile IP broadcasted by the GW 33 on behalf of the FA-GW, so that a plurality of agents are provided.
  • the mobile terminal can identify the FA for the ISP to which it has subscribed, and communicate with the identified FA for Mopile IP. And the like.
  • the GW 33 broadcasts the agent advertisement message on behalf of the FA-GW and applies an IP tunnel using the encapsulated IP packet between the GW 33 and the FA-GW, FA—GW does not need to be the first route for mobile terminals. Therefore, even if there is a router between the mobile terminal and the FA-GW, relaying of the packet by the Mopile IP becomes possible.
  • FIG. 14 shows a composite IP network according to a modification of the second embodiment of the present invention.
  • the IP access network to which the mobile terminal (for example, mobile terminal 1) of the ISP subscriber corresponding to ISP network 9 originally belongs (the IP access network in FIG. 1) '15) does not exist, and the IP access network (IP access network 16 in Fig. 1) to which the mobile terminal (for example, mobile terminal 2) of the ISP subscriber corresponding to ISP network 10 originally belongs is not exist .
  • the composite IP network shown in FIG. 14 is used in the same manner as described above with reference to FIG. Also in the composite IP network of such a modified example, the same effect as achieved in the second embodiment can be achieved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Dans un réseau public d'accès IP, auquel peuvent accéder plusieurs terminaux mobiles, possédant des contrats avec plusieurs fournisseurs de services sur l'Internet (ISP), on met en oeuvre plusieurs agents étrangers (FA) concernant les fournisseurs de service respectifs. A tous les terminaux mobiles présents dans le réseau public d'accès IP, chaque agent étranger diffuse un message d'annonce d'agent contenant une information d'identification ISP correspondant à l'agent étranger ainsi que l'adresse de l'agent étranger lui-même. Par la suite, l'agent étranger relaie un message de requête d'enregistrement de position concernant un terminal mobile qui a répondu au message d'annonce de l'agent.
PCT/JP2002/003839 2002-04-17 2002-04-17 Appareil de communication WO2003088600A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2002/003839 WO2003088600A1 (fr) 2002-04-17 2002-04-17 Appareil de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2002/003839 WO2003088600A1 (fr) 2002-04-17 2002-04-17 Appareil de communication

Publications (1)

Publication Number Publication Date
WO2003088600A1 true WO2003088600A1 (fr) 2003-10-23

Family

ID=29227596

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2002/003839 WO2003088600A1 (fr) 2002-04-17 2002-04-17 Appareil de communication

Country Status (1)

Country Link
WO (1) WO2003088600A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001168906A (ja) * 1999-12-06 2001-06-22 Nippon Telegr & Teleph Corp <Ntt> 位置情報管理システム
EP1117225A2 (fr) * 2000-01-11 2001-07-18 Sharp Kabushiki Kaisha Transmission de donnés vers et depuis un terminal mobile dans un réseau
EP1156626A2 (fr) * 2000-05-17 2001-11-21 Hitachi, Ltd. Réseau de communication mobile, terminal, procédé de comande de communication de paquets, et passerelle

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001168906A (ja) * 1999-12-06 2001-06-22 Nippon Telegr & Teleph Corp <Ntt> 位置情報管理システム
EP1117225A2 (fr) * 2000-01-11 2001-07-18 Sharp Kabushiki Kaisha Transmission de donnés vers et depuis un terminal mobile dans un réseau
EP1156626A2 (fr) * 2000-05-17 2001-11-21 Hitachi, Ltd. Réseau de communication mobile, terminal, procédé de comande de communication de paquets, et passerelle

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HIROYUKI ONISHI ET AL.: "Mobile Ipv6 VPN service teikyo hoshiki ni kansuru ichi kento", 2002 NEN THE INSTITUTE OF ELECTRONICS, INFORMATION AND COMMUNICATION ENGINEERS SOGO TAIKAI KOEN RONBUNSHU, COMMUNICATIONS(2) (B-6-121), 7 March 2002 (2002-03-07), pages 135, XP002953594 *

Similar Documents

Publication Publication Date Title
US7616615B2 (en) Packet forwarding apparatus for connecting mobile terminal to ISP network
JP4431112B2 (ja) 端末及び通信システム
JP3633430B2 (ja) 通信方法、通信システム、通信装置、及び記録媒体
AU745274B2 (en) Mobile data routing
JP4005898B2 (ja) 通信システム
US20010017862A1 (en) IP router device having a TCP termination function and a medium thereof
JP5349466B2 (ja) トンネルオーバヘッドの削減
US20030012179A1 (en) Mobile communication system
US20040136337A1 (en) Routing method for mobile wireless nodes having overlapping internet protocol home addresses
EP1677482B1 (fr) Système de distribution de paquets, dispositif d&#39;enregistrement pour un PAN, dispositif de commande pour un PAN, dispositif de transfert de paquets, et procédé de distribution de paquets
JP2001197558A (ja) ネットワークシステム
US20080112414A1 (en) Mobility management system and method for mobile internet protocol network
US7388850B2 (en) Communication system, communication controlling method, communication node, communication mediator node, communication mediating program, session moving method, and session moving program
WO2007058228A1 (fr) Méthode de communication, dispositif agent mobile et dispositif agent domestique
JP3709816B2 (ja) モバイルｉｐの経路制御方法
JP2008541516A (ja) ＩＰｖ６通信相手ノード及び移動ＩＰｖ６ノード間の通信方法、並びに通信相手ノードプロキシーゲートウエイ
JP3838363B2 (ja) 移動ネットワークおよびその通信方法
JP3496641B2 (ja) 端末位置情報管理方法，この方法を用いる端末位置情報管理システム、並びにこのシステムに用いるホームエージェントおよびボーダゲートウェイ
JP2004215120A (ja) 移動通信システム及びそれに用いる最適化経路通信方法
JP2006222616A (ja) 異種網間移動制御システム
CN1870633B (zh) 通过双栈移动IPv6节点支持移动IPv4的方法
Tsao Enhanced GTP: an efficient packet tunneling protocol for General Packet Radio Service
WO2003088600A1 (fr) Appareil de communication
JP2002223236A (ja) 通信システムにおけるゲートウェイ装置及び通信システムにおけるルート最適化方法
JP3900157B2 (ja) トランスレータ

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP