WO2006106846A1 - 通信ハンドオーバ方法及び通信メッセージ処理方法 - Google Patents
通信ハンドオーバ方法及び通信メッセージ処理方法 Download PDFInfo
- Publication number
- WO2006106846A1 WO2006106846A1 PCT/JP2006/306704 JP2006306704W WO2006106846A1 WO 2006106846 A1 WO2006106846 A1 WO 2006106846A1 JP 2006306704 W JP2006306704 W JP 2006306704W WO 2006106846 A1 WO2006106846 A1 WO 2006106846A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- subnet
- access router
- address
- mobile terminal
- packet
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 90
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000003672 processing method Methods 0.000 title claims description 18
- 238000012546 transfer Methods 0.000 claims abstract description 177
- 230000005540 biological transmission Effects 0.000 claims abstract description 36
- 239000002775 capsule Substances 0.000 claims description 7
- 101000852224 Mus musculus THO complex subunit 5 homolog Proteins 0.000 abstract description 30
- 102100036436 THO complex subunit 5 homolog Human genes 0.000 abstract description 30
- 238000010295 mobile communication Methods 0.000 abstract description 10
- 230000000694 effects Effects 0.000 abstract description 9
- 238000012545 processing Methods 0.000 description 61
- 238000010586 diagram Methods 0.000 description 20
- 230000001413 cellular effect Effects 0.000 description 11
- 238000012544 monitoring process Methods 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 9
- 238000006243 chemical reaction Methods 0.000 description 8
- 238000005538 encapsulation Methods 0.000 description 7
- 239000003795 chemical substances by application Substances 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 101100454361 Arabidopsis thaliana LCB1 gene Proteins 0.000 description 3
- 101100171146 Oryza sativa subsp. japonica DREB2C gene Proteins 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 239000000872 buffer Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/12—Reselecting a serving backbone network switching or routing node
-
- 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
- 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 can provide a user with an efficient communication environment during or after handover when a mobile communication device such as a mopile node (mobile node) has multiple connections to a higher-level network.
- a mobile communication device such as a mopile node (mobile node) has multiple connections to a higher-level network.
- the present invention relates to a communication handover method and a communication message processing method.
- MIP Mobile IP: hereinafter referred to as MIP
- MN mobile communication device
- each MN has a home network and uses a global address assigned on the home network as a home address.
- a home network is a network that is assigned to at least one or more MNs that use MIP.
- An address assigned on the home network is called a home address.
- the communication partner Used as an address to identify the MN on the Internet.
- the MN uses a global address assigned on the network as a care-of address (hereinafter also referred to as CoA).
- the care-of address is a temporary address that the MN uses while staying in the destination network.
- the MN registers related information between the care-of address and the home address to a home agent existing on its own home network using a binding update message.
- the home agent receives a proxy for a packet destined for the home address of the MN that has registered the care-of address, and forwards the packet to the registered care-of address. Play a role.
- a CN that sends a packet to an MN can properly send the packet to the MN on the external network simply by sending the packet to the home address that does not need to know the fact that the MN is moving. It is done.
- Non-Patent Document 2 describes a fast handover for MIP (Fast Handovers for MobileIPv6: hereinafter referred to as F MIP) as a technique for solving such problems that occur when MIP is used. T ⁇ Oh, the technology is known.
- FIG. 14 shows an access router (AR) 21, an access point (AP) 22 connected to the access router 21, an access router 31, and an access point connected to the access router 31. 32 is illustrated.
- Access routers 21 and 31 are routers that manage subnets 24 and 34, which are sub-networks composed of subordinate APs. Node power that exists in these sub-networks To external networks for transmitted packets And routing of packets addressed to nodes in the subnetwork from the external network.
- AP22 constitutes a radio cover area 23
- AP32 constitutes a radio cover area 33.
- the MN 10 can connect to the subnetwork formed by the AR 21 or 31 via the AP 22 or 32, and can further connect to the IP network 15.
- AR21 and AR31 can communicate via the IP network 15.
- Connection between MN and AP Connection and disconnection are performed under the control of layer 2 (data link layer).
- layer 2 data link layer
- FIG. 15 shows a sequence when the MN force FMIP is executed.
- the MN 10 When the MN 10 enters the overlap area 25, the MN 10 receives the beacon transmitted from the AP 32 (S101). Then, the identifier of AP32 included in the received beacon is obtained, and an RtSolPr (Router Solicitation for Proxy Advertisement) message including the identifier is transmitted to AR21 (S102). The AR 21 that has received this message transmits the AR information (in this case, AR 31 information) under the AP having the identifier included in the message to the MN 10 using the PrR tAdv (Proxy Router Advertisement) message (S 103). .
- RtSolPr Raster Solicitation for Proxy Advertisement
- MN 10 When MN 10 decides to hand over to AR31, it uses the AR31 prefix acquired by the PrRtAdv message to use a new care-of address (New Care-of Address: hereinafter referred to as NCoA). ) Is generated (S104). The generated new care-of address is included in the Fast Binding Update message (hereinafter referred to as FBU message) and transmitted to the AR 21 (S105).
- FBU message Fast Binding Update message
- the AR 21 includes the new care-of address included in the FBU message in a Handover Initiate message (hereinafter referred to as HI message) and transmits it to the AR 31 (S106).
- HI message Handover Initiate message
- the AR31 Upon receipt of the HI message, the AR31 verifies whether the new care-of address included therein is valid, and the result is used as a Handover Acknowledgment message (hereinafter referred to as HA). (referred to as ck message) and transmitted to AR21 (S107).
- HA Handover Acknowledgment message
- the AR 21 that has received the HAck transmits an FBAck message including information such as the new! / Included in the HAck message and the verification result of the care-of address to the MN 10 (S108).
- the AR21 that sent the FBAck message receives the packet received to the old care-of address (Previous Care-of Address: hereafter may be called PCoA) used on the MN's subnet 24. Is transferred to the new care-of address (S109).
- PCoA Previous Care-of Address
- the AR 31 buffers the packet transmitted to the new care-of address of the MN 10 (S110).
- the MN 10 transmits a Fast Neighbor Advertisement message (hereinafter referred to as an FNA message) to the AR 31 (S112).
- FNA message a Fast Neighbor Advertisement message
- AR31 transfers the packet buffered in S110 to MN10 (S113).
- FMIP has two operation modes. When the FBU message is transmitted before the handover as described above and the FBAck message is received, it is called the Predictive mode. This is called Reactive mode, which sends an FBU message to AR21.
- the MN 10 can receive packets without loss even if it arrives between the start of layer 2 handover and the execution of MobilelP at the destination. There is a problem that packet reception is interrupted. If the MN has multiple interfaces, the above problem can be solved.
- a MN having a plurality of interfaces will be briefly described.
- a terminal having two wireless LANs such as IEEE802.Ua/b/g and a connection interface to cellular such as W-CDMA and UMTS can be considered.
- Currently, such terminals have already appeared on the market and are expected to become more common in the future.
- the advantage of combining the wireless LAN and cellular interface in this way is that the area covered by the cellular network is wider than the wireless LAN, and the MN goes out of the covered area of the wireless LAN, or Connect to another wireless LAN connection point Even if a handover is performed, if the cellular interface is always in the coverage area of the cellular network, there is a good chance that this will happen.
- wireless LANs have a wider bandwidth than cellular networks and are less expensive to use. Therefore, users have a demand to use wireless LANs preferentially over cellular networks. Can be considered.
- the MN can receive the packet addressed to the address from the connected interface.
- the need for a ring is eliminated. In other words, even if one interface is performing layer 2 handover, it is possible to receive packets that arrived at the other interface.
- Non-Patent Document 1 Johnson, D. B “Perkins, C. E” and Arkko, J “" Mobility Support in I Pv6 “, RFC3775, June 2004.
- Non-Patent Document 2 Rajeev Koodli, "Fast Handover for Mobile IPv, draft-ietf-mipshop-fast-mipv6-03.txt, 25 October 2004.
- a MN having a plurality of interfaces uses an ordinary FMIP and uses the address of another connected interface as a new care-of address.
- AR Previous Access Router: hereinafter referred to as PAR
- Packets delivered to PCoA continue to be forwarded to NCoA until the entry held by PAR times out.
- the MN simply switches the interface to be used, and the state of the interface that is actually performing the handover is not considered at all.
- the interface that is notified as the care-of address to the mopile node power PAR is cellular and the interface that is actually handed over is a wireless LAN, the above method is used. Even after a wireless LAN handover is completed, the packet is always forwarded to the cellular interface. In other words, the mobile node cannot use the WLAN interface effectively because handover is completed and broadband connection means can be secured.
- PAR sends a HI message to confirm whether the new care-of address notified from MN is valid or not, and sends a HAck message as a response.
- the NAR in FMIP is an access router on the subnet to which the MN's handover interface is newly connected. However, as described above, the MN assigns it to another connected interface as a new care-of address.
- PAR recognizes that the access router on the subnet where the address is valid is a NAR.
- the NAR is an access router that exists in the vicinity of the PAR.
- the AR information that the PAR can know includes the NAR of the MN! / Is expensive.
- PAR cannot know the destination address of the HI message, or even if the destination address is known, it cannot receive the HAck message because the access router does not support FMIP.
- FMIP implementation An event that can interfere with this can occur.
- the present invention facilitates FMIP processing even when FMIP is executed using the address of the connected interface as the transfer destination address of a mopile node power packet having a plurality of interfaces. It is an object of the present invention to provide a communication handover method and a communication message processing method capable of changing a transfer destination to an interface after the connection of the interface that has been executed and handed over is completed.
- the present invention provides a first access router belonging to a first subnet, a second access router belonging to a second subnet different from the first subnet, and the first and second subnets
- a communication system in which a third access router belonging to a third subnet different from the first subnet is connected by an IP network, the communication system has a plurality of interfaces, uses the first interface for the first subnet, and 3 is a communication hand-over method implemented when a mobile terminal connected to a subnet via a wireless communication using a second interface switches the connection from the first subnet to the second subnet. Together with the address information used by the mobile terminal on the second subnet for the first access router.
- the mobile terminal A step of receiving the packet transmitted to the packet transfer destination address of the mobile terminal encapsulated and transmitted to the second router, and the mobile terminal using the first interface to the second access router.
- a packet transfer stop instruction message for requesting the second access router to stop forwarding the packet when the connection to the second access router is completed; and the second access router sends the packet transfer stop instruction to the second access router.
- the present invention provides a first access router belonging to the first subnet, a second access router belonging to a second subnet different from the first subnet, and the first and second subnets.
- the communication system has a plurality of interfaces, the first interface is used for the first subnet, and the first 3 is a communication handover method implemented when switching the connection from the first subnet to the second subnet by connecting to the subnet via wireless communication using a second interface.
- the mobile terminal together with the address information used on the second subnet for the first access router, Transmitting an FBU message including packet transfer destination address information assigned to the second interface; storing the transfer destination address information of the mobile terminal packet included in the FBU message;
- the first access router sends an FB Ack message notifying the mobile terminal that the address used on the second subnet is valid; and the first access router Proxy receiving a packet addressed to the address on the first subnet of the mobile terminal, encapsulating it to the packet transfer destination address of the mobile terminal, and transmitting the packet to the mobile terminal Access router power Sent and sent to the packet transfer destination address of the mobile terminal.
- the packet transfer destination to the first access router is: The second subnet Transmitting a packet transfer destination switching instruction message for requesting switching to the address used above; and when the first access router receives the packet transfer destination switching instruction message, packet transfer of the mobile terminal.
- the step of switching the capsule to the destination address to the address used on the second subnet of the mobile terminal is a communication handover method.
- the present invention provides a first access router belonging to a first subnet, a second access router belonging to a second subnet different from the first subnet, A communication system in which a third access router belonging to a third subnet different from the first and second subnets is connected by an IP network has a plurality of interfaces, the first interface is used for the first subnet, and A communication hand-over method implemented when switching the connection from the first subnet to the second subnet by connecting to the third subnet via wireless communication using a second interface The mobile terminal is assigned to the second interface with respect to the first access router.
- Transmitting a FBU message including packet transfer destination address information and information indicating that the packet transfer destination address information is an address assigned to a currently connected interface includes: Storing the destination address information of the packet of the mobile terminal contained in the FBU message; and the first access router proxy-receives a packet addressed to the address on the first subnet of the mobile terminal. Transmitting the packet to the packet transfer destination address of the mobile terminal, and transmitting the mobile terminal encapsulated to the packet transfer destination address of the mobile terminal transmitted to the first access router Receiving the received packet also with the second interface force. It is obtained by the Shin handover method.
- FIG. 1 is a schematic diagram showing a configuration of a radio communication system according to a first embodiment of the present invention.
- FIG. 2 A block diagram showing a configuration of mobile communication apparatus MN10 in Embodiment 1 of the present invention.
- FIG. 3 A block diagram showing a configuration of access router AR21 in Embodiment 1 of the present invention.
- FIG. 5 is a block diagram showing a configuration of access router AR31 in the first embodiment.
- FIG. 5 is a sequence chart showing main processing by the radio communication system in the first embodiment of the present invention.
- FIG. 6A is a schematic diagram showing a first configuration of a data packet transferred by AR 31 to MN 10 in Embodiment 1 of the present invention.
- FIG. 6B is a schematic diagram showing a second configuration of the data packet transferred by AR 31 to MN 10 in Embodiment 1 of the present invention.
- FIG. 7 is a block diagram showing a configuration of mobile communication apparatus MN10 in Embodiment 2 of the present invention.
- FIG. 8 is a block diagram showing a configuration of access router AR21 in Embodiment 2 of the present invention. Sequence chart showing main processing by radio communication system in embodiment 2
- FIG. 10A is a schematic diagram showing a first configuration of a data packet transferred by the AR 21 to the MN 10 in Embodiment 2 of the present invention.
- FIG. 10B is a schematic diagram showing a second configuration of the data packet transferred by AR 21 to MN 10 in Embodiment 2 of the present invention.
- FIG. 11 is a block diagram showing a configuration of mobile communication apparatus MN10 in Embodiment 3 of the present invention.
- FIG. 12 is a block diagram showing a configuration of access router AR21 in Embodiment 3 of the present invention. Sequence chart showing main processes performed by radio communication system according to Embodiment 3
- FIG. 14 is a schematic diagram showing the configuration of a conventional wireless communication system
- FIG. 15 is a sequence chart showing main processing by a conventional wireless communication system. BEST MODE FOR CARRYING OUT THE INVENTION
- an MN when an MN performs handover between access routers connected to an IP network using FMIP, its own connection is used as an address used as a packet transfer destination. Sends an FBU message including the address assigned to the other interface to the access router before moving, and notifies PAR to that effect.
- the packet forwarding destination is changed to the address assigned to the reconnected interface. This makes it possible to receive packets using the interface with the address specified as the forwarding destination even while the connection of the interface being handed over is broken, and after completing the connection of the interface that performed the handover, It is possible to communicate using the same interface as before executing FMIP.
- FIG. 1 shows the configuration of a wireless communication system according to the present invention.
- the same components as those shown in the wireless communication system shown in FIG. 14 are denoted by the same numbers as those used in FIG. Then, the explanation is omitted.
- AR11, AP12, and wireless cover area 13 are newly shown.
- the AR 11 is connected to the IP network 15 and is a router that manages a subnet configured by the wireless cover area 13 of the subordinate AP 12.
- the MN 10 in the present embodiment has a plurality of interfaces, one of which is connected to the AP 12 and can communicate with the IP network 15 via the AR 11, while the other interface One is to connect to AP22 and move from wireless cover area 23 through overlap area 25 to wireless cover area 33 when it can communicate with IP network 15 via A R21.
- the other interface One is to connect to AP22 and move from wireless cover area 23 through overlap area 25 to wireless cover area 33 when it can communicate with IP network 15 via A R21.
- connection configuration of the MN, the AR, and the AP is not limited to the system configuration shown in FIG. 1, and may have different configurations as long as the present invention can be implemented.
- FIG. 2 is a block diagram showing an example of the configuration of the MN according to the present invention.
- the MN shown in Fig. 2 has two interfaces (interface 1 and interface 2), but the number of interfaces held by the MN involved in the present invention is not limited to two, and many more interfaces are available. You may have.
- Figure 2 shows the interface related to the present invention. Only the chair is shown, and the interface 1101 is connected to the AP 12 in FIG. 1, and the interface 1108 is connected to the AP 22 in FIG.
- the MN 10 shown in FIG. 2 includes an interface 1101 connected to the IP network 15, a transmission unit 1102, a reception unit 1103, a packet conversion unit 1104, a packet restoration unit 1105, a MIP processing unit 1106, an upper layer 1107, and an interface. 1108, transmission unit 1109, reception unit 1110, FBU generation unit 1111, packet transfer destination address selection unit 1112, packet transfer stop instruction message generation unit 1113, link status monitoring unit 1114, 8 8 1 ⁇ processing unit 1115, An FBU entry holding unit 1116 is provided.
- the interface 1101 and the interface 1108 can be connected to the IP network 15 via API 2, AP22, and AP32.
- the transmission unit 1102 and the reception unit 1103 transmit and receive packets using the interface 1101.
- the transmission unit 1109 and the reception unit 1110 transmit and receive packets using the interface 1108.
- the packet conversion unit 1104 Based on information about the transmitted FBU held by the FBU entry holding unit 1116 (such as the address of the access router to be connected), the packet conversion unit 1104 sends the packet notified of the output of the MIP processing unit 1106 to the PAR. And then encapsulating it to the NAR and notifying the transmitter 1102 of it.
- the MIP processing unit 1106 converts the transmission packet notified from the higher layer 1107 based on the MobilelP information, and notifies the packet conversion unit 1104 of it.
- the upper layer 1107 corresponds to a layer higher than the IP layer, and includes a TCP layer, a UDP layer, an application layer, and the like.
- the packet restoration unit 1105 decapsulates the received packet notified from the receiving unit 1103 based on the information on the transmitted FBU held by the FBU entry holding unit 1116 and sends it to the MIP processing unit 1106 Notice.
- the FBU generation unit 1111 generates an FBU message including the new care-of address used in the handover destination subnet 34 and the packet transfer destination address notified from the packet transfer destination address selection unit 1112, and transmits the FBU message. Part 1109 is notified and requested to be sent to AR21. Further, it requests the FBU entry holding unit 1116 to store the information included in the transmitted FBU message.
- the address included in the FBU message 1S is the new care-of address, or whether it is the packet forwarding address.
- These options may be represented by different types of options !, or the same option may be used to represent different fields within that option. For example, a new care-of address can use the Alternate CoA Option, which is one of the mobility options, and a new type of mobility option can be used for the forwarding address.
- the packet transfer destination address selection unit 1112 selects an appropriate interface as a packet transfer destination from the list of connected interfaces acquired from the link state monitoring unit 1114, and is assigned to the interface. Notify the address of! /, To the FBU generator 1111.
- the link status monitoring unit 1114 monitors the status of a plurality of interfaces held by the MN 10, receives a request from the packet transfer destination address selection unit 1112, and returns information including the status of each interface .
- the packet transfer stop instruction message generation unit 1113 knows from the information from the link state monitoring unit 1114 that the interface that has executed handover by executing FMIP has completed connection to the destination subnet 34 Based on the information held by the FBU entry holding unit 1116, a packet transfer stop instruction message for requesting to stop the packet transfer by the AR31 is generated, and this is sent to the sending unit 1109 to notify the AR31 To send to.
- FBAck ⁇ 3 ⁇ 43 ⁇ 41115 « processes the FBAck message received by the receiving unit 1110, obtains the reception result of the previously transmitted FBU message included in the message, and sends it to the FBU entry holding unit 1116 Notice.
- the FBU entry holding unit 1116 stores the information notified from the FBU generation unit 1111, and further continues the entry based on the FBU reception result notified from the FBAck processing unit 1115! Decide whether to keep it.
- FIG. 3 is a block diagram showing an example of the configuration of the AR 21 according to the present invention.
- the transmission unit 1201 and the reception unit 1204 are connected to the subordinate AP 22 and the IP network 15 to transmit and receive packets.
- the interface for connecting to the AP 22 and the interface for connecting to the IP network 15 are different, and a plurality of transmitters and receivers are provided for each interface.
- One transmitter for each It is illustrated as 1201 and a receiving unit 1204.
- the FBAck generation unit 1202 receives the instruction from the HAck processing unit 1206, and transmits the instruction to the MN 10.
- the FBAck message includes the status from the NAR notified from the HAck processing unit 1206.
- the HI generation unit 1203 Upon receiving an instruction from the FBU processing unit 1205, the HI generation unit 1203 generates a HI message including the new care-of address and the packet transfer destination address acquired by the FBU message,
- the FBU processing unit 1205 performs processing on the FBU message received from the MN 10 by the reception unit 1204, and notifies the HI generation unit 1203 of information included in the FBU message such as a care-of address and a transfer destination address. And request to generate a HI message.
- the HAck processing unit 1206 performs processing related to the HAck message received from the AR31 by the receiving unit 1204, notifies the FBAck generation unit 1202 of the status from the NAR included in the HAck message, and sends the FBAck message. Request to generate and send it to MN10.
- FIG. 4 is a block diagram showing an example of the configuration of the AR 31 according to the present invention.
- the transmission unit 1301 and the reception unit 1304 are connected to the subordinate AP 32 and the IP network 15 to transmit and receive packets.
- the interface for connecting to the AP32 and the interface for connecting to the IP network 15 are different, and a plurality of transmitters and receivers are provided for each interface. These are collectively shown as one transmitting unit 1301 and receiving unit 1304.
- the care-of-address-addressed packet transfer unit 1302 encapsulates the packet addressed to the new MN 10 received by the receiving unit 1304 with the packet transfer destination address acquired from the MN information holding unit 1306 as the destination. Then, it notifies the transmission unit 1301 to instruct it to transmit.
- the HAck generation unit 1303 Upon receiving an instruction from the HI receiving unit 1305, the HAck generation unit 1303 receives an HAck message including the validity verification result of the new care-of address of the MN 10 and information indicating that it corresponds to the packet transfer stop instruction request. Generate.
- the MN information holding unit 1306 includes the MN information (new information) acquired by the HI receiving unit 1305. Hold care-of address, packet forwarding address, etc.).
- a R31 holds a packet transfer stop instruction message reception processing unit, and when the MN 10 also receives the packet transfer stop instruction message, the A R31 receives a packet transfer unit 1302 addressed to the care-of address. Instruct to stop the proxy reception corresponding to the message. After this message reception process, the proxy reception of the packet addressed to the care-of address is not performed, so the normal routing process is performed for the packet addressed to the new care-of address.
- FIG. 5 is a sequence chart showing main processes in the wireless communication system of the present invention.
- the process from MN10 receiving a beacon from AP32 (S201), sending an RtSolPr message (S202), and receiving a PrRtAdv message (S203) is the same as the normal FMIP process, so the explanation is omitted. .
- the MN 10 selects a packet transfer destination from a plurality of interfaces held by itself and is in a state where packets can be transmitted and received.
- an interface is selected (here, interface 1101), and the address assigned to the interface is selected as the packet forwarding address (S204).
- a new care-of address is generated using the AR31 prefix acquired in S203 (S205).
- an FBU message including a care-of address and a new transfer destination address of the selected packet is generated and transmitted to the AR 21 (S206).
- the AR 21 Upon receiving the FBU message, the AR 21 includes the new care-of address and the packet transfer destination address included in the message in a normal HI message, and transmits it to the AR 31 (S207).
- AR31 When AR31 receives the HI message, it verifies the validity of the new care-of address included in the message, and further adds the HAck message with information indicating that it corresponds to the change of the packet forwarding destination to AR21. (S208).
- the AR21 Upon receiving the HAck message, the AR21 adds an FBAck message with information indicating that it corresponds to the packet transfer destination change of the AR31 notified by the HAck message to the FBAck message in normal FMIP. Generate and send to MN10 (S209). A After sending FBAck, R21 receives the packet sent to the care-of address before the movement of MN 10 by proxy, and starts the encapsulation process with the new care-of address NCoA of MN 10 as the destination for the packet ( S210). Then, the encapsulated packet is transmitted (S211).
- AR31 receives the packet forwarded to the new care-of address of MN10 transmitted from AR21, and starts the encapsulation process with the destination address of MN10 as the destination for that packet ( S212).
- the encapsulation here can be performed by decapsulating the NCoA address header and then encapsulating it to the forwarding address or by encapsulating the packet addressed to the NCoA to the forwarding address. Good. Then, the encapsulated packet is transmitted to the MN 10 (S213).
- the MN 10 receives the packet addressed to the packet transfer destination address received from the AR 31 using the interface 1101, performs decapsulation, and receives the internal packet (S214).
- the ability to decapsulate the packet destined for the forwarding address and receive the packet destined for PCoA, or the packet destined for the NCoA after decapsulating the packet destined for the forwarding address Furthermore, it decapsulates and receives the packet addressed to PCoA.
- the interface 1108 of the MN 10 performs a packet transfer stop instruction for requesting the AR 31 of the connection destination to stop the transfer of the packet addressed to the packet transfer destination address after performing the layer 2 handover (S215).
- a message is transmitted (S216).
- AR31 When AR31 also receives the packet transfer stop instruction message, AR31 stops proxy reception and encapsulation processing of MN10, and the packet addressed to MN10's new! /, Care-of address NCoA Similarly, normal routing processing is started (S217). As a result, the packet addressed to the new care-of address is transferred to the MN 10 (S218).
- the MN 10 receives the packet addressed to the new care-of address received from the AR 31 using the interface 1108, performs decapsulation, and receives the internal packet (S219).
- FIGS. 6A and 6B show the structure of a data packet transferred by the AR 31 to the MN 10.
- the packet in FIG. 6A has a configuration of a packet to be transmitted to the packet transfer destination address of the MN 10, and is a packet transmitted in the process of S213 in FIG. Outermost
- the address specified in the header is the packet transfer destination address of MN10 as the destination address, and the IP address of AR31 as the source address.
- the packet of FIG. 6A is received by the interface 1101 of the MN 10.
- the packet received from AR21 is used as is for the packet encapsulated by this header!
- AR21 is a packet that is encapsulated and transmitted to the new care-of address of MN10, and the internal packet includes a packet addressed to the care-of address before MN10 moves.
- the packet in FIG. 6B is a packet configuration that is transferred to the MN 10 after the AR 31 receives the packet transfer stop instruction message from the MN 10, and is a packet that is transmitted in the process of S218 in FIG. . Since AR31 only performs normal routing processing on packets sent by AR21, this packet is the packet sent by AR21.
- the packet in FIG. 6B is received by the interface 1108 of the MN 10.
- AR31 When proxy receiving a packet addressed to the new care-of address of MN10, AR31 removes the outer header addressed to the new care-of address, and then performs encapsulation to the packet transfer destination address.
- the packet that has been proxy-received from the AR 21 may be encapsulated to the packet transfer destination address.
- the MN 10 that has received the packet in any of these cases performs decapsulation an appropriate number of times to solve the capsules that have been applied! ⁇ Performs processing to correctly receive packets in the decapsulated state.
- the MN 10 can use another interface as a packet transfer destination instead of the interface that is actually handed over. 2 If communication can be continued even during the execution of handover, the effect can be obtained. Or, after the reconnection of the interface that has been executed by the handover is completed, the MN 10 returns the packet forwarding destination from another interface that was used as the forwarding destination of the packet to the interface that has been reconnected. In addition, it is possible to obtain an effect that communication can be performed using the same interface as before the handover. In addition, by changing the packet transfer destination to AR31 power MN10, the AR21 load can be reduced. it can.
- the MN 10 it is also possible for the MN 10 to notify information included in the FBU message by including it in the BU message in the mopile IP.
- one HA that can be used by MN10 plays the same role as AR21, and processes the BU message received from MN10.
- the MN 10 simply includes the new care-of address and the forwarding address in the BU message.
- the MN 10 receives the BU message as the destination address when forwarding the packet received by the HA as the destination address. It is desirable to include a managed home address.
- the other HA plays the same role as AR31, and forwards the proxy received packet to the forwarding address.
- the transfer to the transfer destination address is switched to the transfer to the care-of address.
- FIG. 7 is a block diagram showing an example of the configuration of the MN 10 according to the present invention. 7 includes an interface 1401, an interface 1408, a transmission unit 1402, a transmission unit 1409, a reception unit 1403, a reception unit 1410, a packet conversion unit 1404, a packet restoration unit 1405, a MIP processing unit 1406, an upper layer 1407, An FBU generation unit 1411, a packet transfer destination address selection unit 14 12, a packet transfer destination switching instruction message generation unit 1413, a link state monitoring unit 1414, an FB Ack reception unit 1415, and an FBU entry holding unit 1416 are included.
- An FBU generation unit 1411 a packet transfer destination address selection unit 14 12, a packet transfer destination switching instruction message generation unit 1413, a link state monitoring unit 1414, an FB Ack reception unit 1415, and an FBU entry holding unit 1416 are included.
- interface 1401, interface 1408, transmission unit 1402, transmission unit 1409, reception unit 1403, reception unit 1410, packet conversion unit 1404, packet restoration unit 1405, MIP processing unit 1406, upper layer 1407, FBU generation unit 1411, packet transfer destination address selection unit 14 12, link state monitoring unit 1414, FBAck reception unit 1415, FBU entry holding unit 1416 are the interface 1101, interface 1108, transmission unit 1102, transmission unit 11 09, reception unit shown in FIG. 1103, receiving unit 1110, packet converting unit 1104, packet restoring unit 1105, MIP processing unit 1106, upper layer 1107, 1; generating unit 1111, packet forwarding destination address selecting unit 1112, link state monitoring unit 1114, FBAck processing unit 1115, FBU entry holding unit 1116 and Are the same.
- the packet transfer destination switching instruction message generation unit 1413 learns from the information from the link state monitoring unit 1414 that the interface that executed the handover by executing FMIP has completed the connection to the destination subnet 34 Based on the information held by the FBU entry holding unit 1416, the transfer destination address is assigned to the AR 21 from the address selected by the packet transfer destination address selection unit 1412 to the interface 14 08 where the handover has been completed. Generate a transfer destination switching instruction message for requesting switching to a certain address, notify the transmission unit 1409 of the message, and request to transmit to AR21.
- FIG. 8 is a block diagram showing an example of the configuration of the AR 21 according to the present invention.
- AR2 1 shown in FIG. 8 includes a transmission unit 1501, a reception unit 1506, an old care-of-address addressed packet transfer unit 1502, an FBAck generation unit 1503, an HI generation unit 1504, an MN information holding unit 1505, an FBU processing unit 1507, and an HAck processing unit 1508.
- a packet transfer destination switching instruction message processing unit 1509 is provided.
- transmission unit 1501 and the reception unit 1506 are the same as the transmission unit 1201 and the reception unit 1204 shown in FIG.
- the packet transfer unit 1502 destined for the old care-of address receives the packet addressed to the care-of address (old care-of address) before the movement of the MN, received by the receiving unit 1506, and is held in the MN information holding unit 1505. Encapsulates the packet to the MN's packet transfer destination address, notifies the transmission unit 1501 of it, and instructs to transmit it. Also, in response to an instruction from the packet forwarding destination switching instruction message processing unit 1509, the forwarding destination of the packet addressed to the MN's old care-of address is renewed to the care-of address and the address is changed to the care-of address. Instructs the address to be sent to the address and notifies the sending unit 1501 of it.
- the FBAck generation unit 1503 receives an instruction from the HAck processing unit 1508, generates a normal FBAck message, adds information indicating whether or not the packet transfer is supported, and transmits it to the transmission unit. Instruct 1501 to send.
- the HI generating unit 1504 Upon receiving an instruction from the FBU processing unit 1507, the HI generating unit 1504 generates a normal HI message based on the information included in the FBU message received from the MN 10, and notifies the transmitting unit 15 01 of the normal HI message. Instruct to send.
- the MN information holding unit 1505 receives instructions from the FBU processing unit 1507 and the HAck processing unit 1508, and holds information included in the FBU message from the MN 10 and information from the AR 31 included in the HAck message.
- the FBU processing unit 1507 performs processing related to the FBU message from the MN 10, obtains a new MN10 care-of address, a packet transfer destination address, and the like included in the message, and stores them in the MN information holding unit. Instruct 1505 to keep.
- the HAck processing unit 1508 performs processing related to the HAck message received from the AR31, acquires information from the AR31 included in the HAck message, notifies the MN information holding unit 15 05, and instructs to hold it. .
- the FBAck generation unit 1503 is instructed to generate an FBAck message for notifying the MN 10 of information from the AR31.
- the packet transfer destination switching instruction message processing unit 1509 performs processing related to the packet transfer destination switching instruction message received from the MN 10, and sends the packet to the old care-of address to the old care-of-address address packet transfer unit 1502. The destination is instructed to change the packet destination address to the new care-of address of MN 10.
- FIG. 9 is a sequence chart showing the main processing of the present invention.
- the process from when MN10 receives a beacon from AP32 (S301), transmits an RtSolPr message (S302), and receives a PrRtAdv message (S303) is the same as normal FMIP processing. Omitted.
- the MN 10 selects a packet transfer destination from the interfaces that are connected and can send and receive packets among the plurality of interfaces held by itself.
- an interface is selected (here, interface 1101), and the address assigned to that interface is selected as the packet forwarding address (S304).
- a new care-of address is generated using the AR31 prefix obtained in S303 (S305).
- an FBU message including a care-of address and a new transfer destination address of the selected packet is generated and transmitted to the AR 21 (S306).
- the AR 21 Upon receiving the FBU message, the AR 21 generates a normal HI message using the information included in the message, and transmits it to the AR 31 (S307). [0089] Upon receiving the HI message, the AR 31 verifies the validity of the new care-of address included in the message, and transmits a normal HAck message including the verification result to the AR 21 (S308).
- AR21 Upon receipt of the HAck message, AR21 generates an FBAck message including information indicating that it is responding to the packet transfer destination change in the normal FBAck message, and transmits it to MN10 (S309). . After sending FBAck, AR21 receives the packet sent to the care-of address before the MN's movement by proxy, and starts the capsule processing with the packet transfer destination address of MN10 as the destination for that packet (S310) ). Note that Capsule Louis here encapsulates the packet addressed to PCoA directly to the forwarding address, or encapsulates the packet addressed to PCoA to NCoA and then encapsulates it to the forwarding address. Also good. Then, the encapsulated packet is transmitted to MN10 (S31 Do)
- the MN 10 receives the encapsulated packet from the AR 21 using the interface 1101, performs decapsulation, and receives the internal packet (S312).
- the processing corresponds to the encapsulation method in S310, the power to receive the packet addressed to PCoA after decapsulating the outer header addressed to the transfer destination address, or the key addressed to the transfer destination address.
- the packet destined for NCoA after decapsulating the header is further decapsulated and the packet destined for P CoA is received.
- the interface 1108 of the MN 10 performs the layer 2 handover (S313), and then transmits an FNA message to the AR31 that is the connection destination (S314), and also forwards the packet to the AR21 that is the access router before the movement.
- a switching instruction message is transmitted (S315). Note that this packet transfer destination switching instruction message arrives at AR31 via AR 31 newly connected at interface 1108 or AR connected at another interface 1101!
- the AR 21 that has received the transfer destination switching message from the MN 10 changes the packet transfer destination from the packet transfer destination address of the MN 10 to the new care-of address NCoA (S316). By doing so, the packet is forwarded to the new care-of address of MN 10 (S317), and MN 10 receives the packet using interface 1108.
- the MN 10 decapsulates the packet addressed to the new care-of address received from the AR 21 using the interface 1108, and receives the internal packet (S318).
- FIGS. 10A and 10B show the structure of a data packet that AR21 transfers to MN10.
- the packet in FIG. 10A is a packet configuration to be transmitted to the packet transfer destination address of the MN 10, and is a packet transmitted in the process of S311 in FIG.
- the address specified in the outermost header is the packet transfer destination address of MN10 as the destination address and the IP address of AR21 as the source address. For packets encapsulated by this header, the packet received from AR21 is used as it is.
- the packet in FIG. 10A is received by the interface 1101 of the MN 10.
- the packet in Fig. 10B is a packet configuration that is transferred to the MN 10 after the AR 21 receives the packet transfer destination switching instruction message from the MN 10, and is a packet that is transmitted in the process of S317 in Fig. 9.
- the packet in FIG. 10B is received by the interface 1108 of the MN 10.
- the AR21 may encapsulate the packet addressed to the care-of address before the movement to the packet transfer destination address.
- a packet that has been encapsulated to a care-of address may be encapsulated to a packet transfer destination address.
- the MN 10 that has received the packet in any of these cases performs decapsulation an appropriate number of times to solve the capsules that have been applied! ⁇ Performs processing to correctly receive packets in the decapsulated state.
- the MN 10 can use another interface as a packet transfer destination instead of the interface that is actually handed over. (2) The effect that communication can be continued even during the execution of handover! In addition, after the reconnection of the interface that has been handed over is completed, the MN 10 returns the packet transfer destination from another interface used as the packet transfer destination to the interface that has completed the reconnection. There is also an effect that communication can be performed using the same interface as before the handover. Furthermore, in this configuration, AR21 is Since the packet is transferred and the transfer destination is switched, it is possible to reduce the addition of the NAR 31 that is the movement destination of the MN 10.
- the MN 10 it is also possible for the MN 10 to notify information included in the FBU message by including it in the BU message in the mopile IP.
- HA plays the same role as AR21 and processes BU messages received from MN10.
- FIG. 11 is a block diagram showing an example of the configuration of the MN 10 according to the present invention.
- 11 includes an interface 1601, an interface 1608, a transmission unit 1602, a transmission unit 1609, a reception unit 1603, a reception unit 1610, a packet conversion unit 1604, a packet restoration unit 1605, a MIP processing unit 1606, an upper layer 1607, It has an FBU generation unit 1611, a packet transfer destination address selection unit 1612, a link state monitoring unit 1613, an FBAck processing unit 1614, and an FBU entry holding unit 1615.
- the address selection unit 1612, the link state monitoring unit 1613, the FBAck processing unit 1614, and the FBU entry holding unit 1615 are the interface 1101, the interface 1108, the transmission unit 1102, the transmission unit 1109, the reception unit 1103, and the reception unit 1110 shown in FIG.
- the FBU generation unit 1611 uses the packet transfer destination address notified from the packet transfer destination address selection unit 1612 as an equivalent to a new care-of address in a normal FBU message, and further uses the packet transfer destination address.
- F Generates an FBU message with information indicating that the address is assigned to the connected interface and sends it to the AR 21 by sending it to the sending unit 1609 and requesting it to be sent to the AR 21.
- the FBU entry holding unit 1615 is requested to store the information included in the transmitted FBU message.
- it is indicated by the difference in the option type including the forwarding address to be notified, and it is the same as the option for notifying the normal care-of address.
- An option may be used to represent the difference in fields within that option.
- the Alternate CoA Option which is one of the mobility options
- the mobility option with a new type is used for the forwarding address assigned to the connected interface. Can be used.
- FIG. 12 is a block diagram showing an example of the configuration of the AR 21 according to the present invention.
- the AR 21 shown in FIG. 12 includes a transmission unit 1701, a reception unit 1706, an old care-of-address addressed packet transfer unit 1702, an FBA ck generation unit 1703, an HI generation unit 1704, an MN information holding unit 1705, an FBU processing unit 1707, and HA ck processing. I have part 1708!
- the transmission unit 1701, the reception unit 1706, the FBAck generation unit 1703, the HI generation unit 1704, and the HAck processing unit 1708 are the transmission unit 1501, the reception unit 1506, the FBAck generation unit 1503, and the HI generation unit illustrated in FIG. 1504, same as HAck processing unit 1508.
- the packet transfer unit 1702 addressed to the old care-of address receives the packet addressed to the care-of address (old care-of address) before the movement of the MN, received by the reception unit 1706, and is held in the MN information holding unit 1705. Encapsulates the packet to the MN's packet transfer destination address, and notifies the transmission unit 1701 to send it.
- the MN information holding unit 1705 receives instructions from the FBU processing unit 1707 and the HAck processing unit 1708, and holds information included in the FBU message from the MN 10 and information from the AR 31 included in the HAck message.
- the FBU processing unit 1707 performs processing related to the FBU message from the MN 10, and is assigned to the packet transfer destination address of the MN 10 included in the message and to the other interfaces that the MN 10 has in connection. Information indicating that it is an address is acquired, and the MN information holding unit 1705 is notified and instructed to be held.
- the FBU processing unit 1707 does not instruct the HI generation unit 1704 to generate an HI message.
- the FBU message is an FBU message in normal FMIP and the address is an address assigned to the interface connected to the MN, the HI generator 1704 Is instructed to generate a HI message in normal FMIP.
- the HAck processing unit 1708 instructs the FBAck generation unit 1703 to generate an FBAck message for notifying the MN 10 of information from the AR31.
- FIG. 13 is a sequence chart showing main processes in the wireless communication system of the present invention.
- the process from when MN10 receives a beacon from AP32 (S401), transmits an RtSolPr message (S402), and receives a PrRtAdv message (S403) is the same as the normal FMIP process, so the explanation is omitted. .
- transmission / reception of the RtSolPr message and the PrRtAdv message is optional and not required! /.
- the MN 10 When the MN 10 recognizes that the interface 1108 will be handed over to the AR31 or that the connection with the AR21 is likely to be disconnected, the MN10 is currently connected and can send and receive packets. From the interfaces in the state, select the interface corresponding to the packet forwarding destination (in this case, interface 1101), and select the address assigned to that interface as the packet forwarding address ( S404). Then, an FBU message including the transfer destination address of the selected packet is generated and transmitted to the AR 21 (S405).
- the packet forwarding destination in this case, interface 1101
- AR21 determines whether the address included in the FBU message is an address assigned to the interface connected to MN10 (S406). If it is found that the address is assigned to the interface connected to MN10, it does not send the HI message to AR31, but supports the packet transfer to the connected interface to MN10. An FBAck message with information indicating that it is attached is transmitted (S407). After sending the FBAck message, AR21 receives the packet addressed to the address used on subnet 24 of MN10 by proxy and encapsulates it to the packet forwarding address of MN10. The transmission process is started (S408). Then, the encapsulated packet is transmitted to the MN 10 (S409).
- the MN 10 uses the interface 1101 to receive the encapsulated packet from the AR 21, decapsulates it, and receives the internal packet (S410).
- the interface 1 108 of the MN 10 performs the packet transfer to the AR 21 that is the access router before the movement after performing the layer 2 handover.
- a destination switching instruction message may be transmitted.
- the packet can be received by using the interface 1108 again.
- the MN 10 can use another interface as a packet transfer destination instead of the interface that is actually handed over. (2) The effect that communication can be continued even during the execution of handover! Also, AR21 can recognize that the address included in the FBU message from MN10 is an address assigned to another interface of MN10, and that the interface with that address is connected. If you can determine what you need, you can get a new effect. In the third embodiment of the present invention, it is also possible for the MN 10 to notify information included in the FBU message by including it in the BU message in the mopile IP. In this case, HA plays the same role as AR21 and processes BU messages received from MN10.
- each functional block used in the description of each embodiment of the present invention described above is typically realized as an LSI (Large Scale Integration) which is an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them. Note that, here, it is sometimes called IC (Integrated Circuit), system LSI, super LSI, or unroller LSI, depending on the difference in power integration.
- LSI Large Scale Integration
- the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. You can use an FPGA (Field Programmable Gate Array) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connection and settings of circuit cells inside the LSI. [0117] Further, if integrated circuit technology that replaces LSI emerges as a result of advances in semiconductor technology or other derived technology, it is naturally also possible to perform functional block integration using that technology. For example, biotechnology can be applied.
- FPGA Field Programmable Gate Array
- the present invention has an effect of improving the communication efficiency of a mobile communication device by effectively utilizing a plurality of interfaces held by the mobile communication device when handing over. It can be applied to network technology including mobile communication devices such as mopile nodes, and in particular to communication control technology when mobile communication devices perform handover between sub-networks using mobility support technology such as FMIP.
- mobile communication devices such as mopile nodes
- FMIP mobility support technology
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP06730652A EP1865671A4 (en) | 2005-03-30 | 2006-03-30 | COMMUNICATION HANDOVER METHOD AND COMMUNICATION MESSAGE PROCESSING METHOD |
JP2007512872A JP4617355B2 (ja) | 2005-03-30 | 2006-03-30 | 通信ハンドオーバ方法及び通信メッセージ処理方法 |
US11/909,269 US8009629B2 (en) | 2005-03-30 | 2006-03-30 | Communication handover method and communication message processing method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2005097400 | 2005-03-30 | ||
JP2005-097400 | 2005-03-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006106846A1 true WO2006106846A1 (ja) | 2006-10-12 |
Family
ID=37073402
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2006/306704 WO2006106846A1 (ja) | 2005-03-30 | 2006-03-30 | 通信ハンドオーバ方法及び通信メッセージ処理方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US8009629B2 (ja) |
EP (1) | EP1865671A4 (ja) |
JP (1) | JP4617355B2 (ja) |
CN (1) | CN101151855A (ja) |
WO (1) | WO2006106846A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008227565A (ja) * | 2007-03-08 | 2008-09-25 | Japan Radio Co Ltd | 情報中継システム |
JP2009239755A (ja) * | 2008-03-27 | 2009-10-15 | Kyocera Corp | 無線通信システム、無線基地局、無線端末及び無線通信方法 |
WO2011021292A1 (ja) * | 2009-08-20 | 2011-02-24 | 富士通株式会社 | 通信方法、通信システム、移動端末および基地局 |
CN101247317B (zh) * | 2007-02-15 | 2011-07-20 | 华为技术有限公司 | 路由切换方法及系统 |
JP2012151878A (ja) * | 2012-03-12 | 2012-08-09 | Kyocera Corp | 無線通信システム、無線基地局、無線端末及び無線通信方法 |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101461264B (zh) * | 2006-06-06 | 2010-12-29 | 松下电器产业株式会社 | 无线通信系统、无线终端、基站以及基站搜索方法 |
US20100175109A1 (en) * | 2007-05-25 | 2010-07-08 | Wassim Haddad | Route optimisation for proxy mobile ip |
JP5298540B2 (ja) * | 2008-01-22 | 2013-09-25 | 富士通株式会社 | ネットワークシステム、データ送受信方法、及びデータ送受信プログラム |
JPWO2010041440A1 (ja) * | 2008-10-08 | 2012-03-08 | パナソニック株式会社 | インタフェース切換システム、モバイルノード、代理ノード及び移動管理ノード |
US10938652B1 (en) * | 2019-08-20 | 2021-03-02 | Hughes Network Systems, Llc | Gateway diversity switching |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003125433A (ja) * | 2001-10-16 | 2003-04-25 | Ntt Docomo Inc | 通信制御方法及び移動端末 |
JP2004304841A (ja) * | 2004-06-04 | 2004-10-28 | Denso Corp | 無線通信システムおよび無線通信システムに用いられる移動端末 |
JP2004328593A (ja) * | 2003-04-28 | 2004-11-18 | Kyocera Corp | 無線通信端末 |
JP2006080981A (ja) * | 2004-09-10 | 2006-03-23 | Fujitsu Ltd | ハンドオーバ方法並びにこれを適用した移動通信システムおよび移動端末 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7031279B2 (en) * | 2000-12-30 | 2006-04-18 | Lg Electronics Inc. | Gatekeeper supporting handoff and handoff method in IP telephony system |
WO2003032588A1 (fr) * | 2001-10-02 | 2003-04-17 | Ntt Docomo, Inc. | Systeme de controle de mobilite, noeud mobile utilise dans ce systeme, procede de controle de mobilite, programme de controle de mobilite et noeud de controle de mobilite |
AU2003219353A1 (en) * | 2002-04-11 | 2003-10-20 | Nortel Networks Limited | Resource optimization in a wireless ip network |
JP2004015143A (ja) * | 2002-06-04 | 2004-01-15 | Fujitsu Ltd | 移動通信システムにおけるハンドオーバ方法、および移動通信システムにおいて使用されるルータ装置 |
US7917152B2 (en) * | 2003-06-27 | 2011-03-29 | Nokia Corporation | Enhanced fast handover procedures |
JP4196801B2 (ja) * | 2003-10-01 | 2008-12-17 | 株式会社日立製作所 | 無線システムおよび移動局 |
JP4466296B2 (ja) * | 2003-10-17 | 2010-05-26 | パナソニック株式会社 | ハンドオーバ方法および移動通信システム |
JP2005143086A (ja) * | 2003-10-17 | 2005-06-02 | Matsushita Electric Ind Co Ltd | 移動検知方法および移動端末 |
US7548525B2 (en) * | 2003-10-18 | 2009-06-16 | Samsung Electronics Co., Ltd | System and method for providing handover of a mobile IP terminal in a wireless network |
JP4567004B2 (ja) * | 2003-11-26 | 2010-10-20 | 韓國電子通信研究院 | アクセスルータを基盤としたモバイルIPv6の高速ハンドオーバ方法 |
US7813319B2 (en) * | 2005-02-04 | 2010-10-12 | Toshiba America Research, Inc. | Framework of media-independent pre-authentication |
US7508793B2 (en) * | 2005-03-07 | 2009-03-24 | Telefonaktiebolaget L M Ericsson (Publ) | Micro mobility management |
-
2006
- 2006-03-30 WO PCT/JP2006/306704 patent/WO2006106846A1/ja active Application Filing
- 2006-03-30 EP EP06730652A patent/EP1865671A4/en not_active Withdrawn
- 2006-03-30 JP JP2007512872A patent/JP4617355B2/ja not_active Expired - Fee Related
- 2006-03-30 US US11/909,269 patent/US8009629B2/en not_active Expired - Fee Related
- 2006-03-30 CN CNA2006800102013A patent/CN101151855A/zh active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003125433A (ja) * | 2001-10-16 | 2003-04-25 | Ntt Docomo Inc | 通信制御方法及び移動端末 |
JP2004328593A (ja) * | 2003-04-28 | 2004-11-18 | Kyocera Corp | 無線通信端末 |
JP2004304841A (ja) * | 2004-06-04 | 2004-10-28 | Denso Corp | 無線通信システムおよび無線通信システムに用いられる移動端末 |
JP2006080981A (ja) * | 2004-09-10 | 2006-03-23 | Fujitsu Ltd | ハンドオーバ方法並びにこれを適用した移動通信システムおよび移動端末 |
Non-Patent Citations (2)
Title |
---|
See also references of EP1865671A4 * |
YUAN B. ET AL.: "IN2004-95 Kaisokei Mobile IPv6 ni yoru Multicast Packet Seigyo Hoshiki", IEICE TECHNICAL REPORT, vol. 104, no. 340, 8 October 2004 (2004-10-08), pages 71 - 76, XP003003308 * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101247317B (zh) * | 2007-02-15 | 2011-07-20 | 华为技术有限公司 | 路由切换方法及系统 |
US9049625B2 (en) | 2007-02-15 | 2015-06-02 | Huawei Technologies Co., Ltd. | Route switching methods and systems |
JP2008227565A (ja) * | 2007-03-08 | 2008-09-25 | Japan Radio Co Ltd | 情報中継システム |
JP2009239755A (ja) * | 2008-03-27 | 2009-10-15 | Kyocera Corp | 無線通信システム、無線基地局、無線端末及び無線通信方法 |
WO2011021292A1 (ja) * | 2009-08-20 | 2011-02-24 | 富士通株式会社 | 通信方法、通信システム、移動端末および基地局 |
JP2012151878A (ja) * | 2012-03-12 | 2012-08-09 | Kyocera Corp | 無線通信システム、無線基地局、無線端末及び無線通信方法 |
Also Published As
Publication number | Publication date |
---|---|
US8009629B2 (en) | 2011-08-30 |
JPWO2006106846A1 (ja) | 2008-09-11 |
CN101151855A (zh) | 2008-03-26 |
EP1865671A1 (en) | 2007-12-12 |
US20090016298A1 (en) | 2009-01-15 |
JP4617355B2 (ja) | 2011-01-26 |
EP1865671A4 (en) | 2012-08-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1329124B1 (en) | Seamless handoff in mobile ip | |
JP4617355B2 (ja) | 通信ハンドオーバ方法及び通信メッセージ処理方法 | |
KR101111519B1 (ko) | 이동 통신 시스템에서 ip 주소 선 설정 방법 | |
USRE45465E1 (en) | Communication system using network base IP mobility protocol, control apparatus, router and communication method thereof | |
EP1869937B1 (en) | A method of reconfiguring an internet protocol address in handover between heterogeneous networks | |
US20100215019A1 (en) | Detection of mobility functions implemented in a mobile node | |
TWM294788U (en) | Wireless communication system for implementing media independent handover between technologically diversified access networks | |
KR101216081B1 (ko) | 이종망 간 핸드오버 시의 ip 주소 재설정 방법 | |
JP2008546304A (ja) | パケット・データ通信環境におけるハンドオーバを管理するための方法およびネットワーク・ノード | |
KR100800822B1 (ko) | 브리지 기반 셀룰러 이더넷 망의 시스템 및 그 핸드오버처리 방법 | |
JP5132570B2 (ja) | ハンドオーバ処理方法、及びその方法で用いられるアクセスポイント及び移動端末 | |
CN1961537B (zh) | 通信系统、移动终端和接入路由器 | |
CN1926823B (zh) | 通信系统、移动终端和接入路由器 | |
WO2008089671A1 (fr) | Procédé, système et terminal pour réduire le temps de transfert | |
KR101084138B1 (ko) | Map 도메인 간 핸드오버 수행 방법 | |
WO2010010693A1 (ja) | 垂直ハンドオフ方法、垂直ハンドオフシステム、ホームエージェント及びモバイルノード | |
JP4461155B2 (ja) | ネットワークベースipモビリティプロトコルを利用した通信システム、制御装置、ルータ及びその通信方法 | |
JP4500831B2 (ja) | ネットワークベースipモビリティプロトコルを利用した通信システム、制御装置、ルータ及びその通信方法 | |
Ali-Yahiya et al. | Mobility |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200680010201.3 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 11909269 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006730652 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007512872 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWP | Wipo information: published in national office |
Ref document number: 2006730652 Country of ref document: EP |