WO2010052919A1 - ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント - Google Patents
ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント Download PDFInfo
- Publication number
- WO2010052919A1 WO2010052919A1 PCT/JP2009/005914 JP2009005914W WO2010052919A1 WO 2010052919 A1 WO2010052919 A1 WO 2010052919A1 JP 2009005914 W JP2009005914 W JP 2009005914W WO 2010052919 A1 WO2010052919 A1 WO 2010052919A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- address
- handover
- message
- mobile terminal
- home
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
-
- 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]
- H04W80/045—Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6
Definitions
- the present invention relates to a handover method in a communication system that performs communication while moving between networks corresponding to different IP versions, and a mobile terminal and a home agent (location management server) used in the method.
- Mobile IPv4 MIPv4
- MIPv6 MIPv6
- IP communication Internet protocol communication
- DSMIP Dual Stack Mobile IP
- the mobile terminal registers the IPv6 home address (HoAv6) and the IPv6 care-of address (CoAv6) in the home agent (location management server) using the MIPv6 protocol based on Non-Patent Document 2, and the relationship (binding) of these addresses in the home agent
- all messages are based on the IPv6 protocol and could only be used from an access network that supports IPv6.
- DSMIP is an extension of MIPv6, and when a mobile terminal connects to an access network that supports only IPv4, the IPv4 care-of address (CoAv4) acquired from the access network is bound to HoAv6 and also from an access network that supports only IPv4. Communication using HoAv6 is made possible.
- DSMIP assumes that the home agent has an IPv4 address, and encapsulates the CoAv4 and the IPv4 address of the home agent with the IPv4 header described in the address field, thereby binding control message (Binding Update (BU) based on MIPv6 or Binding Acknowledge (BA), etc.) can be exchanged, or an IPv4 home address (HoAv4) can be assigned to a mobile terminal to enable communication with a communication partner (Correspondent Node: CN) having only an IPv4 address.
- BU Binding Update
- BA Binding Acknowledge
- Non-Patent Document 4 discloses a handover method from a 3GPP access network (LTE, etc.) to a non-3GPP access network (wireless LAN network system, WiMAX network system, 3GPP2 network system, etc.) using DSMIP.
- LTE 3GPP access network
- non-3GPP access network wireless LAN network system, WiMAX network system, 3GPP2 network system, etc.
- the mobile terminal has only performed home link detection for the IPv6 home prefix to which the home address HoAv6 belongs.
- home link detection using the IPv4 address is not performed, and even if the subnet of the IPv4 address (corresponding to CoAv4) acquired from the access network and the subnet of HoAv4 are the same, the IPv6 prefix acquired from the access network and the IPv6 home The access network was not considered a home link unless the prefix was the same.
- FIG. 1 is a configuration diagram of an example of a mobile communication system using DSMIP, in which an access network 101 that supports IPv6, an access network 102 that supports only IPv4, and a core network 103 that can be connected via these access networks are arranged.
- Each access network is provided with access routers AR104 and AR105, and each access router may be an IPv6 router or an IPv4 router depending on the operation of the access network system.
- a home agent HA 106 based on DSMIP is provided in the core network 103.
- the mobile terminal UE 107 is connected to the HA 106 via the access network 101 to acquire an IPv6 home address (HoAv6), and then moves to the access network 102 to perform a handover process.
- HoAv6 IPv6 home address
- FIG. 8 is a sequence chart for explaining an example of a conventional handover processing procedure.
- the attach process is started (step S802).
- the attach process includes a connection authentication process (step S803) by the authentication server HSS / AAA 801.
- the attach process is completed.
- the UE 107 acquires an IPv4 address during the attach process or using the DHCP protocol after the attach process is completed (IPv4 address acquisition request, IPv4 address assignment: step S804), and uses this as a care-of address (CoAv4) first.
- a binding request message (Binding Update: BU) for registering with the HA together with the acquired HoAv6 is transmitted (step S805).
- the UE 107 uses the BU to execute an IPv4 home address (HoAv4) allocation request based on the DSMIP protocol.
- HoAv4 IPv4 home address
- the HA 106 registers the pair of HoAv6 and CoAv4 in the binding cache, and notifies the UE 107 using a binding response message (Binding : Acknowledge: BA) to allocate the HoAv4 (step S806).
- a pair of HoAv4 and CoAv4 is registered in the binding cache.
- the UE 107 can perform home link detection from the viewpoint of the IPv4 subnet that has not been implemented conventionally by comparing the acquired HoAv4 and CoAv4 subnet parts (step S807).
- the access network 102 can be regarded as a home link from the viewpoint of IPv4, and there is no need to give a redundant IPv4 tunnel header to a packet exchanged with the HA 106.
- the access network 102 is not a home link, so it is necessary to add an IPv4 tunnel header to all packets exchanged with the HA 106.
- home link detection from the viewpoint of IPv4 has not been performed, so an IPv4 tunnel header is added to all packets exchanged with the HA 106.
- IPv4 addresses belonging to can be distributed.
- the mobile terminal may perform a key update process as shown in FIG. 8 with the HA after acquiring CoAv4 and before transmitting the BU.
- a mobile terminal that does not support dynamic key update must update the key every time the care-of address is changed. Since the key update requires a long time process involving cryptographic calculation in both the mobile terminal and the HA, it takes a considerable time until the mobile terminal completes the home link detection from the IPv4 viewpoint and can actually transmit and receive packets. become.
- the present invention provides a case where, in a mobile communication system using DSMIP, an address assigned from a handover destination access network is only an IPv4 address during a handover process by a mobile terminal having only an IPv6 home address. Then, it is detected that the handover destination access network is an access network that supports only IPv4, and the assigned IPv4 address is set to the home agent via the handover source access network as the IPv4 home address. As a result, the handover destination access network is used as the home link, and the tunnel overhead between the mobile terminal and the home agent is reduced to improve the communication efficiency, and the key update is performed even when the mobile terminal performs the key update process.
- a handover method capable of completing binding processing before processing and enabling packet transmission / reception without waiting for completion of time-consuming key update processing, and a mobile terminal and home agent used in the method The purpose is to do.
- a handover method of the mobile terminal that moves between at least two networks respectively corresponding to different IP versions that are unique communication protocols of the mobile terminal, the mobile terminal When performing handover from the access router before the handover to which the terminal is currently connected to the access router of the other network of the handover destination, based on the first address assigned to the mobile terminal from the handover destination network, If it is determined that the IP version supported by the handover destination network is different from the IP version supported by the network before the handover, the mobile terminal sends a home address assignment request in the handover destination network Assigned Transmitting a message including the first address to the home agent via the access router before the handover, the home agent performing a predetermined process based on the message, and responding to the allocation request And a step of transmitting a response message including a home address to the mobile terminal.
- the handover destination access network is a home link
- the tunnel overhead between the mobile terminal and the home agent is reduced to improve communication efficiency, and even if the mobile terminal performs key update processing,
- the binding process can be completed before the update process, and packets can be transmitted / received without waiting for the completion of the key update process that takes time.
- the mobile terminal method for performing handover between at least two networks respectively corresponding to different unique IP versions that are communication protocols of the mobile terminal, wherein the mobile terminal is currently connected.
- the handover destination network responds based on the first address assigned to the mobile terminal from the handover destination network.
- Determining means for determining whether or not an IP version that is different from an IP version supported by the network before handover, and a home address assignment request in the handover destination network if it is determined that the IP version is different
- Message generating means for generating a message including the received first address, transmitting means for transmitting the generated message to a home agent via the access router before the handover, and based on the message
- a mobile terminal comprising receiving means for receiving a response message including a home address for the assignment request transmitted from a home agent.
- the handover destination access network is a home link
- the tunnel overhead between the mobile terminal and the home agent is reduced to improve communication efficiency, and even if the mobile terminal performs key update processing,
- the binding process can be completed before the update process, and packets can be transmitted / received without waiting for the completion of the key update process that takes time.
- a home agent of the mobile terminal that performs handover between at least two networks respectively corresponding to different IP versions that are communication protocols of the mobile terminal, and the mobile terminal is currently connected.
- the handover destination network is supported based on the first address assigned to the mobile terminal from the handover destination network. If it is determined that the IP version being used is different from the IP version supported by the network before the handover, the message is transmitted by the mobile terminal, and the allocation of the home address in the handover destination network is performed.
- a home agent comprising message generating means for generating and transmitting means for transmitting the generated response message to the mobile terminal.
- the handover method of the present invention uses the handover destination access network as a home link, reduce the tunnel overhead between the mobile terminal and the home agent, improve communication efficiency, and move Even when the terminal performs the key update process, the binding process can be completed before the key update process, and packets can be transmitted / received without waiting for the completion of the key update process that takes time. .
- the block diagram which shows an example of a structure of the communication system in embodiment of this invention Sequence chart for explaining an example of a handover method in the embodiment of the present invention
- Other sequence charts for explaining an example of the handover method in the embodiment of the present invention The block diagram which shows an example of a structure of the mobile terminal which concerns on embodiment of this invention
- the block diagram which shows an example of a structure of the home agent which concerns on embodiment of this invention The flowchart which shows an example of the processing flow in the mobile terminal which concerns on embodiment of this invention
- FIG. 1 is a diagram for explaining a system configuration according to an embodiment of the present invention.
- An access network 101 that supports IPv6, an access network 102 that supports only IPv4, and a core network 103 that can be connected via these access networks are arranged. Is done.
- Each access network is provided with access routers AR104 and AR105, and each access router may be an IPv6 router or an IPv4 router depending on the operation of the access network system.
- the access router can be an access gateway (Access Gateway: AGW), a mobility anchor gateway (Mobility Anchor Gateway: MAG), a packet data gateway (Packet Data Gateway: PDG, enhanced). Packet Data ⁇ Gateway: ePDG), serving gateway (Serving Gateway: SGW), serving GPRS serving node (Serving GPRS Serving Node: SGSN), etc.
- a home agent (HA) based on DSMIP is arranged in the core network, and this HA is a packet data network gateway (Packet Data Network Gateway: PDN GW), gateway GPRS serving node according to the standard adopted by the core network. (Gateway GPRS Serving Node: GGSN).
- the mobile terminal UE 107 connects to the HA 106 via the access network 101 to acquire the IPv6 home address (HoAv6), then moves to the access network 102 and performs a handover process.
- HoAv6 IPv6 home address
- FIG. 2 is a sequence chart for explaining an example of the handover method in the embodiment of the present invention.
- the UE 107 detects the start of the handover process to the access network 102 (step S201)
- the UE 107 starts the attach process to the access network 102 (step S202).
- the attach process is accompanied by an authentication process (step S203) in the core network 103.
- an IP address is assigned to the UE 107 in the response message.
- no IP address is assigned in the response message, and after the attach process is completed, the UE 107 acquires an IP address using a protocol such as DHCP (steps S204 and S205).
- the assigned IP address is distributed by a DHCP server in the access network 102, or the AR 105 becomes a DHCP relay and forwards the DHCP request to the HA 106, and the HA 106 receives the DHCP response and distributes it.
- the AR 105 distributes the IP address already acquired from the HA 106 by the PBA message to the UE 107 by the DHCP response, or the AR 105 transmits a PBU message to the HA 106 in response to the DHCP request.
- CoAv4 is assigned when an IP address is assigned by a DHCP server in the access network 102, and HoAv4 is assigned otherwise.
- the IP address assigned in the access network 102 is IPv4_AN2.
- the UE 107 recognizes that the access network 102 is a network that supports only IPv4 because the IPv4_AN2 that is the assigned IP address is an IPv4 address and the IPv6 address is not assigned.
- the UE 107 may perform the following process in order to ensure that the IP version supported by the access network 102 is only IPv4.
- IPv4_AN2 when IPv4_AN2 is acquired or immediately after acquisition, an RS (Router Solicitation) message for acquiring an IPv6 address is transmitted, but when a response cannot be received for a certain period of time, it is recognized that the supported IP version is only IPv4. You may do it.
- IPv4_AN2 when IPv4_AN2 is acquired or before and after acquisition, a packet on the link may be monitored to recognize that IPv4 is the only supported IP version when an IPv6 packet cannot be detected.
- the UE 107 When recognizing that the access network 102 is a network that supports only IPv4, the UE 107 transmits a BU to the HA 106 via the access network 101 of the handover source (step S206). At this time, the IP address IPv4_AN2 acquired by the access network 102 is described in the BU, including the HoAv4 allocation request. Further, information indicating that the UE 107 is performing handover and that the IPv4 address (IPv4_AN2) assigned in the access network 102 to which the handover is made becomes HoAv4 assigned by the HA 106 from now on (for example, a flag (hereinafter referred to as flag X)). May be included.
- a flag hereinafter referred to as flag X
- information of the access network 102 (for example, an identifier of an access network such as an SSID, an identifier of an access point, a PLMN identifier, etc.) is notified to the HA 106 using BU, and a database or the like is stored in the HA 106. If the IP version supported by the access network 102 is detected and it is detected that only the IPv4 is supported, the same operation as when the flag X is added to the BU may be performed.
- the HA 106 When the HA 106 receives the BU including the HoAv4 allocation request (and the flag X) in which IPv4_AN2 is described via the access network 101, the HA 106 performs one of the following processes (actions 1 to 3), and assigns IPv4_AN2 as the allocated HoAv4. Is transmitted to the UE 107 (step S207). Note that the HA 106 may receive an approval from the authentication server HSS / AAA 801 for using the requested IPv4_AN2 as a home address before performing any action.
- the action 1 process will be described.
- the HA 106 assigns an address different from IPv4_AN2 (here, IPv4_HoA) as the actual HoAv4 of the UE 107 (step S208), and creates a conversion table describing the correspondence between IPv4_AN2 and IPv4_HoA (step S209). Thereafter, the packet transmitted from the UE 107 with IPv4_AN2 as the transmission source address is forwarded with the header modified so as to originate from IPv4_HoA, and the packet addressed to IPv4_HoA is modified and forwarded so as to be directed to IPv4_AN2.
- IPv4_HoA IPv4_HoA
- mapping with the IPv4_HoA actually assigned by the HA 106 is performed by the HA 106, so that the response on the access network 102 (AR 105) side to which the IPv4_AN2 has already been assigned becomes unnecessary, and the expandability of the network can be ensured.
- this method can cope with a change in the IP address (equivalent to IPv4_AN2) acquired at the handover destination when the UE 107 repeats the handover. That is, when the IP address acquired in the handover destination access network is used as the home address used in actual communication, the home address changes at every handover, which is not preferable for the UE 107 that wants to continue the session.
- the HA 106 separately assigns a home address (IPv4_HoA) to the UE 107 and performs conversion processing with the IPv 106 that is the IP address acquired by the UE 107 in the access network, the IPv4_AN2 is changed by handover.
- IPv4_HoA home address
- the actual home address IPv4_HoA assigned by the HA 106 may be notified to the UE 107 by describing it in the BA transmitted via the access network 101, and the UE 107 may manage the same conversion table as the HA 106.
- packet processing using IPv4_HoA which is the real home address, is performed in the application processing inside the UE 107, and packet processing using IPv4_AN2 is performed in the transport processing lower than the application and connected.
- IPv4_HoA and IPv4_AN2 are notified to the UE 107 as home addresses by the BA, but a flag is provided for clarifying which is the actual home address (which is actually used in communication with the outside). Also good.
- the UE 107 may interpret that it is a real home address, and change the existing message format.
- the present invention can be realized without any problem.
- only the IPv4_HoA is described in the BA, and the IPv4_AN2 is not described. Instead, a flag instructing the packet processing using the translation table may be provided in the BA. By notifying the UE 107 using a small number of flags, transmission efficiency can be improved.
- the HA 106 transmits a PBU request message requesting transmission of a PBU (Proxy Binding Update) to the AR 105 (step S210).
- the PBU request message may be one in which the HA 106 instructs the AR 105 via the authentication server (HSS / AAA 801) or the like.
- the AR 105 transmits a PBU to the HA 106 (step S211), and the HA 106 returns a PBA (Proxy Binding Acknowledge) message describing IPv4_AN2 to the AR 105 (step S212).
- PBA Proxy Binding Acknowledge
- the AR 105 that has received the PBA assumes that the IPv4_AN2 is the home address assigned by the HA 106, and the UE 107 uses a DHCP refresh request or the like.
- the DHCP request may be performed again. That is, the UE 107 acquires the home address from the handover destination network 102 again.
- the mobile terminal 107 can detect that the handover destination access network 102 has officially become a home link, and can correctly notify the mobile terminal 107 of the timing at which communication that does not require a tunnel can be started.
- the access network 102 receives the certification as the home address assigned from the core network 103 (HA 106) by the IPv4_AN2, though already assigned, via the PMIP tunnel connected between the AR 105 and the HA 106. Thereafter, mobility control of the UE 107 can be performed using a standard PMIP protocol. Note that it is necessary to control the DHCP server in the access network 102 that has previously issued IPv4_AN2 so as not to temporarily manage IPv4_AN2, and when the UE 107 stops using IPv4_AN2, the control is performed again. Rights are given to the DHCP server. Accordingly, it is possible to prevent the DHCP server arranged in the access network 102 from independently releasing IPv4_AN2 and performing reassignment, thereby preventing a session in communication from being unexpectedly disconnected.
- the action 3 process will be described. If the IPv4_AN2 acquired via the access network 102 is actually assigned by the HA 106 (that is, if the IPv4_AN2 is a home address), the HA 106 performs special processing because the desired state has already been obtained. Not performed (step S213), a BA having IPv4_AN2 as a home address is returned to the UE 107 (step S207).
- the UE 107 confirms that the address assigned from the access network 102 and the home address acquired via the access network 101 are the same IPv4_AN2, that is, the access network 102 is a home link.
- the UE 107 indicates that the access network 102 is a home link. Confirmation (ie home link detection) can be omitted.
- the UE 107 that has confirmed that the access network 102 is the home link transmits a BU for registering the binding of HoAv6 and HoAv4 to the HA 106 according to the conventional handover procedure, and receives the BA from the HA 106.
- the HA 106 can generate HoAv6 and HoAv4 bindings.
- the BU / BA exchange via the access network 102 can be omitted, and the speed of the handover can be increased. Furthermore, since BU / BA can be omitted here, packets can be transmitted and received immediately, and the effect of speeding up the handover is particularly greater than when the UE 107 requires key update processing. This is because the key update process needs to be performed before the BU / BA exchange (because the purpose is to update the IPsec key for protecting the BU / BA), and the BU / BA exchange is omitted. The key update process can be performed at an arbitrary timing after the handover process is completed.
- the HA 106 has a subnet (prefix) range of the IPv4_AN2 of the IP address requested by the UE 107 to be a home link that is different from that assigned to the operator who manages the HA 106, or the HA 106 has an external network (for example, ISP or corporate).
- PDN Packet ⁇ Domain Network
- the IPv4_AN2 may be refused to be a home link.
- the HA 106 performs, for example, the processing of the action 1 described above, or assigns a different home address (IPv4_HoA) to the UE 107 and notifies the UE 107 with the BA (see IPv4_AN2 as shown in action 4 in FIG. 3). Do not notify).
- the UE 107 determines that the access network 102 is an external link (that is, not a home link) and uses the home address notified by the BA and the IPv4_AN2 of the IP address acquired by the access network 102 to perform standard mobile communication. Communication is performed by IP (Mobile IP) (tunnel communication between the UE 107 and the HA 106 is performed with the IPv4 address of the IPv4_AN2 and the HA 106 as an endpoint).
- IP Mobile IP
- the HA 106 when the HA 106 refuses to use the address IPv4_AN2 acquired from the handover destination access network 102 as the home address, the HA 106 notifies the UE 107 of the regular home address (IPv4_HoA) different from the IPv4_AN2 using the BA. (Step S311).
- IPv4_HoA regular home address
- the IPv4_HoA assigned by the HA 106 can be distributed to the UE 107 via the access network 102. That is, the HA 106 allocates IPv4_HoA and transmits a PBU request message to the AR 105 at the same time (step S308).
- the AR 105 transmits a PBU to the HA 106 (step S309), the HA 106 returns a PBA describing IPv4_HoA to the AR 105 (step S310), and the UE 107 makes a DHCP request again (step S312).
- IPv4_HoA a regular home address
- the AR 105 that has received the PBA may prompt the UE 107 to execute the DHCP request again using a DHCP-refresh request or the like. That is, the UE 107 acquires the home address from the handover destination network 102 again. Further, the UE 107 may release the previously acquired IPv4_AN2 (DHCP release), so that address resources can be effectively used.
- the AR 105 may include the address (IPv4_AN2) distributed to the UE 107 in the PBU transmitted to the HA 106.
- IPv4_AN2 the address (IPv4_AN2) distributed to the UE 107 in the PBU transmitted to the HA 106.
- the AR 105 allocates and distributes a local address
- the HA 106 collates with the IPv4_AN2 acquired by the BU via the access network 101. That is, the HA 106 receives from the AR 105 the address (first address) already assigned to the UE 107 by the AR 105 of the handover destination network 102, and the address included in the message and the received address (first address) Verification can be performed, and the safety of the system can be improved.
- the HA 106 may issue a PBU request message to the AR 105 to receive a PBU including IPv4_AN2, thereby achieving the same effect.
- the PBU message based on PMIP is one specific example, and other messages may be used.
- the UE 107 may not be able to receive the BA transmitted by the HA 106. Assuming such a situation, the HA 106 transmits the BA via the network 101 before the handover and the network 102 of the handover destination, or transmits the BA to the access network 101, and the access network 102 uses IKEv2 based on DSMIP. The UE 107 may be notified via the access network 102 that the IPv4_AN2 has been recognized as the home address by starting the bootstrapping process.
- the processing result (the handover destination access network 102 can be used as the home link reliably via the access network 102 which is the handover destination). You can receive)
- the UE 107 when the UE 107 acquires an IP address from the access network 102 at the time of attach processing or using the DHCP protocol, it may be notified that the IP address to be acquired from now is considered to be the home address. Specifically, a flag is provided in the attach message or DHCP request message transmitted from the UE 107.
- the authentication server HSS / AAA 801 interprets the notification and instructs the HA 106 to allocate a home address, and the HA 106 allocates a home address and forwards it to the UE 107 with an attach response message.
- the UE 107 is instructed to acquire by DHCP.
- the AR 105 that has received the DHCP request from the UE 107 receives the PMIP protocol or the GTP protocol during the attach process.
- the home address acquired from the HA 106 is distributed to the UE 107 by a DHCP response using the above, the DHCP request is transferred to the HA 106 to request allocation, and the PMIP protocol is newly activated for the HA 106 (transmission of a PBU message) Then, the home address assigned by the HA 106 is transferred to the UE 107.
- the IP address to be acquired will be the home address, or the connected access network is the home link.
- the notification requesting that the mobile terminal wishes to do is to notify the network to the mobile terminal as an option when selecting one from various mobility protocols such as PMIP, DSMIP, and MIPv4 (RFC3344) (Mobility Mode Selection). There may be.
- FIG. 4 is a diagram showing an example of the configuration of the mobile terminal according to the embodiment of the present invention.
- the transmission / reception units 401 and 402 correspond to communication interfaces for connecting to the access networks 101 and 102, respectively, and perform communication protocol processing and modem processing lower than the IP layer.
- the IP processing unit 403 performs IP layer processing
- the MIP processing unit 404 performs Mobile IP protocol processing based on DSMIP.
- the DHCP processing unit 405 performs DHCP protocol processing (client function).
- the handover control unit 406 determines or detects handover feasibility and execution timing from the communication status obtained from the transmission / reception units 401 and 402, and performs handover execution to the MIP processing unit 404, transmission / reception units 401 and 402, DHCP processing unit 405, and the like. Instructions are sent out to control the handover process.
- the home address registration control unit 407 is characteristic in the present invention, and its operation will be described with reference to FIG.
- the handover control unit 406 determines whether to start handover (step S601). When the start of the handover is determined, the transmission / reception unit 402 is instructed to start the attach process. When an IP address (IPv4_AN2) is assigned from the access network 102 during the attach process, the transmission / reception unit 402 transfers and sets the IPv4_AN2 to the IP processing unit 403 (step S502: attach process, IP address acquisition). In addition, when an IP address is not assigned at the time of the attach process and an IP address is acquired using DHCP after the attach process is completed, the handover control unit 406 receives a notification from the transmission / reception unit 402 that the attach process has been completed, and the handover control unit 406 Instruct 405 to start IP address acquisition.
- IPv4_AN2 IP address
- the handover control unit 406 receives a notification from the transmission / reception unit 402 that the attach process has been completed, and the handover control unit 406 Instruct 405 to start IP address acquisition.
- the DHCP processing unit 405 sends a DHCP request message to the access network 102 via the IP processing unit 403 and the transmission / reception unit 402, and sends a DHCP response message including IPv4_AN2 assigned as a response via the transmission / reception unit 402 and the IP processing unit 403. get.
- IPv4_AN2 acquired is set in the IP processing unit 403.
- the home address registration control unit 407 determines whether or not the handover destination access network 102 is an access network that supports only IPv4 based on the version of the assigned IP address (step S603). When it is determined (detected) that the network only supports IPv4 (the detection method is as described above), the transmission of BU for notifying the HA 106 of the acquired IPv4 address via the handover source access network (access network 101) is performed. The processing unit 404 is instructed. At this time, information (for example, a flag) requesting that the IPv4 address notified at the same time be the home address may be added to the BU.
- step S603 to reliably determine that the IP version (IPv4) supported by the access network 102 at the handover destination is different from the IP version (IPv6) supported by the access network 101 before the handover.
- the home address registration control unit 407 has failed to receive a response (RA message; Router Advertisement) to a predetermined message (e.g., RS message; Router Solicitation) transmitted when acquiring the assigned address, and / or Alternatively, it is detected that the access network supports only IPv4 based on the fact that a predetermined packet (for example, IPv6 packet) could not be detected (monitored) at the time of obtaining the assigned address.
- RA message Router Advertisement
- RS message Router Solicitation
- the MIP processing unit 404 transmits a BU requesting an IPv4 home address (IPv4_AN2 is described in the IPv4 home address option) via the handover source network (step S604).
- the BU is sent to the access network 101 via the IP processing unit 403 and the transmission / reception unit 401 and transferred to the HA 106.
- the BA is received from the HA 106 (step S605).
- the BA received from the HA 106 is transferred to the MIP processing unit 404 via the transmission / reception unit 401 and the IP processing unit 403, and is described in the IPv4 home address (IPv4_HoA) described in the BA.
- IPv4_HoA IPv4 home address
- step S606 Is the same as the previously notified IPv4 address (IPv4_AN2) (step S606), and if it is the same, the handover control unit 406 finally performs the detach processing from the access network 101 to the transmission / reception unit 401.
- the start is instructed (step S608), and the handover process is completed when the detach process is completed.
- the handover destination network 102 acquires the IP address again using DHCP (step S607).
- the detach process (step S608) may be omitted or may be performed in response to an instruction from the network.
- the IPv4 address acquired at the time of the attach process or the DHCP process is compared with the IP address acquired via the access network 101 to determine that the link is a home link.
- the IPv4 address obtained via the access network 102 is notified to the HA 106 via the access network 101 to request that the access network 102 be the home link of the UE 107, and the home address included in the BA is the access network 102. Confirm that it is the same as the IPv4 acquired in step (1). That is, since the IP address distributed in the access network 102 is the same as the home address, the main feature of the present invention is that it is not necessary to perform home link determination.
- FIG. 5 is a diagram showing an example of the configuration of the HA according to the embodiment of the present invention.
- the transmission / reception unit 501 corresponds to a communication interface for communicating with a node in the core network 103, and performs communication protocol processing and modem processing lower than the IP layer.
- the IP processing unit 502 performs IP layer processing
- the MIP processing unit 503 performs Mobile IP protocol processing based on DSMIP.
- the PMIP processing unit 504 performs PMIP protocol processing.
- the home address assignment unit 505 and the conversion table management unit 506 are characteristic in the present invention, and their operations will be described with reference to FIG.
- Step S701 It is determined whether or not the MIP processing unit 503 has received a BU from the UE 107 via the transmission / reception unit 501 and the IP processing unit 502 (step S701). Upon reception of the BU, it is determined whether or not there is a notification of the IPv4 home address (and a flag that requests that the IP address distributed to the UE 107 in the access network that is the handover destination of the UE 107 be the IPv4 home address assigned here). (Step S702) If one exists, one of the following processes (actions 1, 2, 4) is performed.
- the conversion table management unit 506 creates a conversion table in which an address included in the BU is associated with a newly assigned home address different from the address (action 1), and the PMIP processing unit 504
- action 1 an address included in the BU
- action 2 the conversion table management unit 506 and the PMIP processing unit 504 transmit the BA to the UE 107.
- the home address to be notified is an address included in the BU.
- the processing means assigns a home address to be assigned in response to a home address assignment request from the UE 107 as another address (second address) different from the address (IPV4_AN2) included in the BU, and sets this different address as the handover destination.
- the PMIP processing unit 504 sets the home address notified to the UE 107 by the BA as the other address.
- IPv4_HoA IPv4 home address
- IPv4_AN2 IPv4 home address
- IPv4_HoA IPv4 home address
- the home address allocation unit 505 controls the PMIP processing unit 504 to transmit a message for instructing (requesting) transmission of the PBU to the AR 105.
- the PBU transmission instruction message from the PMIP processing unit 504 is transmitted to the network via the IP processing unit 502 and the transmission / reception unit 501 (step S705).
- the destination address (AR105) of the PBU transmission instruction message may be obtained by inquiring a server such as the authentication server HSS / AAA801.
- the PMIP processing unit 504 receives the PBU of the AR 105 via the transmission / reception unit 501 and the IP processing unit 502, the home address (IPv4_AN2) notified to the UE 107 is acquired from the home address allocation unit 505 and described in the PBA message. (Step S706).
- IPv4_HoA IPv4 home address
- BA step S707
- the home address allocation unit 505 controls the PMIP processing unit 504 to transmit a message for instructing (requesting) transmission of the PBU to the AR 105.
- the PBU transmission instruction message from the PMIP processing unit 504 is transmitted to the network via the IP processing unit 502 and the transmission / reception unit 501 (step S708).
- the destination address (AR105) of the PBU transmission instruction message may be acquired by an inquiry to a server such as the authentication server HSS / AAA801.
- the PMIP processing unit 504 receives the PBU of the AR 105 via the transmission / reception unit 501 and the IP processing unit 502, the home address (HoAv4) notified to the UE 107 is acquired from the home address allocation unit 505 and described in the PBA message. (Step S709).
- the mobile terminal uses a DHCP request message and a DHCP response message in order to obtain an IP address.
- the DHCP request message is a message for starting an IP address acquisition process, and when the DHCP DISCOVER message in the DHCP protocol, the DHCP server is already known, or the transmission of the DHCP DISCOVER message is omitted.
- the DHCP response message is a message in which the IP address is notified to the mobile terminal in the IP acquisition process, and corresponds to a DHCPDACK message or a DHCP OFFER message in the DHCP protocol.
- the HA 106 acquires whether or not IPv4_AN2 can be used as a home address from a policy server such as a PCRFCharging Rules Function, or a policy or rule related to QoS or charging determined in advance or a network environment. It may be determined. For example, only when the UE 107 is subscribed to a plan in which the home address (home link) can be set arbitrarily (or freely), the setting can be permitted, and the network function managed by the operator is impaired. Thus, the present invention can be realized.
- a policy server such as a PCRFCharging Rules Function, or a policy or rule related to QoS or charging determined in advance or a network environment. It may be determined. For example, only when the UE 107 is subscribed to a plan in which the home address (home link) can be set arbitrarily (or freely), the setting can be permitted, and the network function managed by the operator is impaired.
- the present invention can be realized.
- a predetermined QoS condition (for example, given by the PCRF) is performed by the address translation processing in the HA 106. Policy or rules related to QoS that have been or have been negotiated in advance), if it is determined that QoS is not impaired, perform Action 1, and if it is determined that it will be impaired May not perform action 1.
- the present invention can be implemented without deteriorating the optimum or designated QoS, and the convenience of the user and the operator can be improved.
- the UE 107 may be an IPv4 address (private address or global address) from the acquired IPv4 subnet or entirely independently. ) May be generated and notified (registered) to the HA 106 using a BU message.
- the HA 106 converts the IPv4 address uniquely generated by the UE 107 into an IPv4 address (or may be an IPv6 address) that can be communicated with the external node by performing action 1 or the like. Realize communication. Further, the UE 107 may independently generate an IPv4 address without receiving the IP address distributed from the access network 102 and notify (register) it to the HA 106, thereby shortening the connection (handover) time. Can do.
- a QoS policy (rule) and a charging policy (rule) to be set are acquired from a policy server such as a PCRF (or based on a prior agreement) and applied.
- a policy server such as a PCRF (or based on a prior agreement)
- the HA 106 that has received the BU message from the UE 107 sets the same QoS / billing policy as previously applied, but it has already been set at the time of address distribution via the access network 102.
- Setting by the HA 106 at the time of BU reception may be omitted (conventionally, when the types of the access networks 101 and 102 are different, for example, 3GPP access and non-3GPP access, the QoS / billing policy is reset.
- the HA 106 assigns an IPv4 home address separately from the IPv4 address notified by the UE 107 (for example, when the HA also operates as a NAT), QoS / billing policy setting by the HA 106 is performed as usual.
- QoS / billing policy settings are correctly made (in the core network and the access network, the IPv4 address and core network notified by UE 107).
- QoS / billing policy is applied to the IPv4 home address assigned by the HA 106, and QoS / billing management according to the address application range becomes possible.
- the handover between the 3GPP access network and the non-3GPP access network is particularly exemplified.
- the attach procedure is not performed as in the handover between 3GPP access networks
- the access is performed in the handover procedure.
- the network 102 is a network that supports only IPv4 and the network side (eg PGW or SGW) determines that the UE 107 does not have an IPv4 address
- the network side eg PGW or SGW
- DHCP A procedure or the like may be used to notify the IPv4 address to the UE 107 (push notification is made regardless of whether there is a request from the UE 107), or the IPv4 address may be notified to the UE 107 during the handover procedure.
- Each functional block used in the description of the above embodiment is typically realized as an LSI that 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.
- the name used here is LSI, but it may also be called IC, system LSI, super LSI, or ultra LSI depending on the degree of integration.
- the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible.
- An FPGA Field Programmable Gate Array
- a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used.
- integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. For example, biotechnology can be applied.
- the handover method of the present invention uses the handover destination access network as a home link, reduce the tunnel overhead between the mobile terminal and the home agent, improve communication efficiency, and move Even when the terminal performs key update processing, binding processing can be completed before key update processing, and packets can be transmitted and received in the handover destination network without waiting for completion of key update processing that requires time. Therefore, the method is useful for a handover method in a communication system that performs communication while moving between networks corresponding to different IP versions, a mobile terminal used in the method, a home agent, and the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (20)
- 移動端末の通信規約である固有の異なるIPバージョンにそれぞれ対応する少なくとも2つのネットワーク間を移動する前記移動端末のハンドオーバ方法であって、
前記移動端末が現在接続しているハンドオーバ前のアクセスルータからハンドオーバ先の他のネットワークのアクセスルータへハンドオーバをする際、前記ハンドオーバ先のネットワークから前記移動端末に割り当てられた第一のアドレスに基づいて、前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なると判断された場合、
前記移動端末が、前記ハンドオーバ先のネットワークにおけるホームアドレスの割り当て要求と、割り当てられた前記第一のアドレスとを含むメッセージを前記ハンドオーバ前のアクセスルータを介してホームエージェントへ送信するステップと、
前記ホームエージェントが、前記メッセージに基づいて、所定の処理を行うとともに、前記割り当て要求に対するホームアドレスを含む応答メッセージを前記移動端末へ送信するステップとを、
有するハンドオーバ方法。 - 前記メッセージは、割り当てられた前記第一のアドレスを前記ホームエージェントが割り当てるホームアドレスとするよう指示するフラグを含む請求項1に記載のハンドオーバ方法。
- 前記所定の処理が、前記ハンドオーバ先のネットワークのアクセスルータへ前記メッセージに含まれるアドレスを通知することである場合に、
前記ホームエージェントは、前記応答メッセージに含まれるホームアドレスを前記メッセージに含まれるアドレスとする請求項1又は2に記載のハンドオーバ方法。 - 前記ホームエージェントは、前記ハンドオーバ先のネットワークのアクセスルータへ前記メッセージに含まれるアドレスを通知する前に、前記ハンドオーバ先のネットワークによって前記移動端末に既に割り当てられた前記第一のアドレスを前記ハンドオーバ先のネットワークのアクセスルータから受信し、前記メッセージに含まれるアドレスと受信された前記第一のアドレスとの照合を行う請求項3に記載のハンドオーバ方法。
- 前記所定の処理が、前記メッセージに含まれるアドレスとは異なる第二のアドレスを前記ハンドオーバ先のネットワークのアクセスルータへ通知することである場合に、
前記ホームエージェントは、前記応答メッセージに含まれるホームアドレスを前記第二のアドレスとする請求項1に記載のハンドオーバ方法。 - 前記ホームエージェントが前記応答メッセージに含まれるホームアドレスを前記第二のアドレスとした場合、
前記移動端末は、前記ハンドオーバ先のネットワークからアドレスを取得し、取得した前記アドレスをホームアドレスとして使用する請求項5に記載のハンドオーバ方法。 - 前記ホームエージェントは、前記第二のアドレスを前記ハンドオーバ先のネットワークのアクセスルータへ通知する前に、前記ハンドオーバ先のネットワークによって前記移動端末に既に割り当てられた前記第一のアドレスを前記ハンドオーバ先のネットワークのアクセスルータから受信し、前記メッセージに含まれるアドレスと受信された前記第一のアドレスとの照合を行う請求項5に記載のハンドオーバ方法。
- 前記移動端末は、前記第一のアドレスの取得の際に送信した所定のメッセージに対する応答を受信できなかったこと、及び/又は前記第一のアドレスの取得の際に所定のパケットを検出できなかったことに基づいて、前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なることを判断する請求項1に記載のハンドオーバ方法。
- 前記ホームエージェントは、前記ハンドオーバ前のネットワーク及び前記ハンドオーバ先のネットワークを経由させて前記応答メッセージを送信する請求項1に記載のハンドオーバ方法。
- 移動端末の通信規約である固有の異なるIPバージョンにそれぞれ対応する少なくとも2つのネットワーク間をハンドオーバする前記移動端末であって、
前記移動端末が現在接続しているハンドオーバ前のアクセスルータからハンドオーバ先の他のネットワークのアクセスルータへハンドオーバをする際、
前記ハンドオーバ先のネットワークから前記移動端末に割り当てられた第一のアドレスに基づいて、前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なるか否かを判断する判断手段と、
IPバージョンが異なると判断された場合、前記ハンドオーバ先のネットワークにおけるホームアドレスの割り当て要求と、割り当てられた前記第一のアドレスとを含むメッセージを生成するメッセージ生成手段と、
生成された前記メッセージを前記ハンドオーバ前のアクセスルータを介してホームエージェントへ送信する送信手段と、
前記メッセージに基づいて前記ホームエージェントから送信される、前記割り当て要求に対するホームアドレスを含む応答メッセージを受信する受信手段とを、
備える移動端末。 - 前記メッセージ生成手段は、割り当てられた前記第一のアドレスを前記ホームエージェントが割り当てるホームアドレスとするよう指示するフラグを前記メッセージに含める請求項10に記載の移動端末。
- 前記ホームエージェントによって、前記ハンドオーバ先のネットワークのアクセスルータへ前記メッセージに含まれるアドレスを通知する処理がされた場合、又は前記応答メッセージに含まれるホームアドレスが前記メッセージに含まれるアドレスとは異なる第二のアドレスとされた場合、
前記メッセージ生成手段は、前記ハンドオーバ先のネットワークからアドレスを取得するための取得要求メッセージを生成し、
前記送信手段は、生成された前記取得要求メッセージを前記ハンドオーバ先のネットワークのアクセスルータへ送信する請求項10又は11に記載の移動端末。 - 前記判断手段は、前記第一のアドレスの取得の際に送信した所定のメッセージに対する応答を受信できなかったこと、及び/又は前記第一のアドレスの取得の際に所定のパケットを検出できなかったことに基づいて前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なることを判断する請求項10に記載の移動端末。
- 移動端末の通信規約である固有の異なるIPバージョンにそれぞれ対応する少なくとも2つのネットワーク間をハンドオーバする前記移動端末のホームエージェントであって、
前記移動端末が現在接続しているハンドオーバ前のアクセスルータからハンドオーバ先の他のネットワークのアクセスルータへハンドオーバをする際、前記ハンドオーバ先のネットワークから前記移動端末に割り当てられた第一のアドレスに基づいて、前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なると判断された場合、
前記移動端末によって送信されるメッセージであって、前記ハンドオーバ先のネットワークにおけるホームアドレスの割り当て要求と、割り当てられた前記第一のアドレスとを含むメッセージを受信する受信手段と、
受信した前記メッセージに基づいて所定の処理を行う処理手段と、
前記割り当て要求に対するホームアドレスを含む応答メッセージを生成するメッセージ生成手段と、
生成された前記応答メッセージを前記移動端末へ送信する送信手段とを、
備えるホームエージェント。 - 前記メッセージには、割り当てられた前記アドレスを前記ホームエージェントが割り当てるホームアドレスとするよう指示するフラグが更に含まれる請求項14に記載のホームエージェント。
- 前記処理手段が、前記所定の処理として前記ハンドオーバ先のネットワークのアクセスルータへ前記メッセージに含まれるアドレスを通知する場合に、
前記メッセージ生成手段は、前記応答メッセージに含まれるホームアドレスを前記メッセージに含まれるアドレスとする請求項14又は15に記載のホームエージェント。 - 前記受信手段は、前記送信手段が前記ハンドオーバ先のネットワークのアクセスルータへ前記メッセージに含まれるアドレスを通知する前に、前記ハンドオーバ先のネットワークによって前記移動端末に既に割り当てられた前記第一のアドレスを前記ハンドオーバ先のネットワークのアクセスルータから受信し、
前記処理手段は、前記メッセージに含まれるアドレスと受信された前記第一のアドレスとの照合を行う請求項16に記載のホームエージェント。 - 前記処理手段が、前記所定の処理として前記割り当て要求に対するホームアドレスを前記メッセージに含まれる前記アドレスとは異なる第二のアドレスとし、前記第二のアドレスを前記ハンドオーバ先のネットワークのアクセスルータへ通知する場合に、
前記メッセージ生成手段は、前記応答メッセージに含まれるホームアドレスを前記第二のアドレスとする請求項14に記載のホームエージェント。 - 前記受信手段は、前記送信手段が前記第二のアドレスを前記ハンドオーバ先のネットワークのアクセスルータへ通知する前に、前記ハンドオーバ先のネットワークのアクセスルータによって前記移動端末に既に割り当てられた前記第一のアドレスを前記ハンドオーバ先のネットワークのアクセスルータから受信し、
前記処理手段は、前記メッセージに含まれるアドレスと受信された前記第一のアドレスとの照合を行う請求項18に記載のホームエージェント。 - 前記送信手段は、前記ハンドオーバ前のネットワーク及び前記ハンドオーバ先のネットワークを経由させて前記応答メッセージを送信する請求項14に記載のホームエージェント。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09824619A EP2352338A1 (en) | 2008-11-07 | 2009-11-06 | Handover method, and mobile terminal and home agent used in the method |
JP2010536697A JPWO2010052919A1 (ja) | 2008-11-07 | 2009-11-06 | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント |
US13/126,682 US8761119B2 (en) | 2008-11-07 | 2009-11-06 | Handover method, and mobile terminal and home agent used in the method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008-286450 | 2008-11-07 | ||
JP2008286450 | 2008-11-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010052919A1 true WO2010052919A1 (ja) | 2010-05-14 |
Family
ID=42152732
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2009/005914 WO2010052919A1 (ja) | 2008-11-07 | 2009-11-06 | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント |
Country Status (5)
Country | Link |
---|---|
US (1) | US8761119B2 (ja) |
EP (1) | EP2352338A1 (ja) |
JP (1) | JPWO2010052919A1 (ja) |
KR (1) | KR20110082541A (ja) |
WO (1) | WO2010052919A1 (ja) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020055971A1 (en) * | 1999-11-01 | 2002-05-09 | Interdigital Technology Corporation | Method and system for a low-overhead mobility management protocol in the internet protocol layer |
US8509244B2 (en) | 2009-08-14 | 2013-08-13 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for providing host node awareness for multiple NAT64 environments |
US8509185B2 (en) * | 2010-02-26 | 2013-08-13 | Telefonaktiebolaget Lm Ericsson | Enabling IPV6 mobility with NAT64 |
US8504722B2 (en) | 2010-06-14 | 2013-08-06 | Telefonaktiebolaget Lm Ericsson | Enhancing DS-lite with private IPV4 reachability |
KR101707543B1 (ko) * | 2010-06-24 | 2017-02-16 | 주식회사 케이티 | Pmip 기반의 서비스에 따른 핸드오버 수행 방법 및 그 시스템 |
US9094873B2 (en) * | 2012-05-14 | 2015-07-28 | Wei Lu | Classified relation networking optimization platform in open wireless architecture (OWA) mobile cloud terminal device |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005073271A (ja) | 2003-08-25 | 2005-03-17 | Kddi Corp | ISATAPを用いてIPv4コンポーネントを備えたネットワーク上でのモバイルIPv6通信を可能とするシステム及び方法並びに記録媒体 |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU9615701A (en) * | 2000-10-18 | 2002-04-29 | Ericsson Telefon Ab L M | Seamless handoff in mobile ip |
US6832087B2 (en) * | 2001-11-30 | 2004-12-14 | Ntt Docomo Inc. | Low latency mobile initiated tunneling handoff |
KR101166765B1 (ko) * | 2004-05-07 | 2012-07-27 | 엘지전자 주식회사 | IPv4 및 IPv6을 지원하기 위한 IP 주소 설정 |
US8724582B2 (en) * | 2004-06-28 | 2014-05-13 | Nokia Corporation | Method and apparatus providing context transfer for inter-PDSN handoffs in a wireless communication system |
KR100594819B1 (ko) * | 2004-08-03 | 2006-07-03 | 한국전자통신연구원 | 핸드오버 방법 |
FR2888078B1 (fr) * | 2005-06-30 | 2007-08-10 | Alcatel Sa | Procede de transfert d'une communication impliquant un noeud mobile en situation de macro-mobilite au sein d'un reseau de communication ip a routage hierarchique |
US7969945B2 (en) * | 2006-01-11 | 2011-06-28 | Starent Networks Llc | Systems and methods for mobility management on wireless networks |
US20070189218A1 (en) * | 2006-02-11 | 2007-08-16 | Yoshihiro Oba | Mpa with mobile ip foreign agent care-of address mode |
KR100739803B1 (ko) * | 2006-04-21 | 2007-07-13 | 삼성전자주식회사 | 이동 노드에서의 핸드오버 장치 및 방법 |
EP1871069A1 (en) * | 2006-05-25 | 2007-12-26 | Samsung Electronics Co., Ltd. | Apparatus and method for controlling layer 3 handover of mobile node |
US7961685B2 (en) * | 2006-07-28 | 2011-06-14 | Samsung Electronics Co., Ltd | Method and system for performing handoff for mobile station in a mobile communication system using proxy mobile IP |
US8483174B2 (en) * | 2007-04-20 | 2013-07-09 | Qualcomm Incorporated | Method and apparatus for providing gateway relocation |
US8175056B2 (en) * | 2007-08-28 | 2012-05-08 | Samsung Electronics Co., Ltd | Method and system for managing mobility in a mobile communication system using proxy mobile internet protocol |
US8165091B2 (en) * | 2008-06-27 | 2012-04-24 | Nix John A | Efficient handover of media communications in heterogeneous IP networks using LAN profiles and network handover rules |
-
2009
- 2009-11-06 KR KR1020117010156A patent/KR20110082541A/ko not_active Application Discontinuation
- 2009-11-06 WO PCT/JP2009/005914 patent/WO2010052919A1/ja active Application Filing
- 2009-11-06 US US13/126,682 patent/US8761119B2/en active Active
- 2009-11-06 JP JP2010536697A patent/JPWO2010052919A1/ja not_active Withdrawn
- 2009-11-06 EP EP09824619A patent/EP2352338A1/en not_active Withdrawn
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005073271A (ja) | 2003-08-25 | 2005-03-17 | Kddi Corp | ISATAPを用いてIPv4コンポーネントを備えたネットワーク上でのモバイルIPv6通信を可能とするシステム及び方法並びに記録媒体 |
Non-Patent Citations (6)
Title |
---|
"Architecture enhancements for non-3GPP accesses (Release 8", 3GPP TS 23.402 V.8.2.0, June 2008 (2008-06-01), pages 136 - 139 |
C. PERKINS: "IP Mobility Support for IPv4", IETF RFC3344, August 2002 (2002-08-01) |
D. JOHNSON, C. PERKINS, J. ARKKO: "Mobility Support in lPv6", IETF RFC3775, June 2004 (2004-06-01) |
H. SOLIMAN, MOBILE IPV6 SUPPORT FOR DUAL STACK HOSTS AND ROUTERS, 3 November 2008 (2008-11-03), XP015058497 * |
HESHAM SOLIMAN, MOBILE IPV6 SUPPORT FOR DUAL STACK HOSTS AND ROUTERS (DSMIP, July 2008 (2008-07-01) |
NARAYANAN, U. ET AL.: "Signaling Cost Analysis of Handoffs in a Mixed IPv4/IPv6 Mobile Environment", GLOBAL TELECOMMUNICATIONS CONFERENCE, 2007. GLOBECOM '07. IEEE, pages 1792 - 1796, XP031196273 * |
Also Published As
Publication number | Publication date |
---|---|
JPWO2010052919A1 (ja) | 2012-04-05 |
US20110208877A1 (en) | 2011-08-25 |
US8761119B2 (en) | 2014-06-24 |
EP2352338A1 (en) | 2011-08-03 |
KR20110082541A (ko) | 2011-07-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5989868B2 (ja) | 第2のサービスドメインにおけるホームエージェントでの第1のサービスドメインに属する移動局のサービスの固定 | |
US8824430B2 (en) | Wireless mobility gateway | |
EP1560378B1 (en) | Wireless mobility gateway | |
US8599843B2 (en) | Apparatus and method for route optimization for proxy mobile internet protocol version six local routing | |
JP5371987B2 (ja) | 移動端末及びネットワークノード | |
US20100103876A1 (en) | Mobile terminal and communication management device | |
WO2009116246A1 (ja) | 通信方法、通信システム、モバイルノード及びアクセスルータ | |
WO2011001594A1 (ja) | リダイレクション方法、リダイレクションシステム、モバイルノード、ホームエージェント及び代理ノード | |
US8788826B1 (en) | Method and apparatus for dynamically allocating a mobile network prefix to a mobile terminal | |
WO2005107178A1 (en) | A method and system for providing ipv6 service | |
WO2010052919A1 (ja) | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント | |
US8411658B2 (en) | Mobile terminal and network node | |
WO2009028885A2 (en) | Method and system for managing mobility in a mobile communication system using proxy mobile internet protocol | |
WO2010073620A1 (ja) | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント | |
US9148826B2 (en) | Handover method and mobile terminal and home agent used in the method | |
US20110170531A1 (en) | Prefix assigning method, prefix assigning system and mobile node | |
US8634394B1 (en) | Mechanism to verify packet data network support for internet protocol mobility | |
WO2011055478A1 (ja) | 移動端末及びパケットフィルタ設定方法 | |
WO2010146815A1 (ja) | 移動管理プロトコル選択方法、移動管理プロトコル選択システム、モバイルノード、ホームエージェント及び代理ノード | |
Andersson et al. | Rethinking IP mobility management | |
KR20090021817A (ko) | 이동통신 시스템에서 프록시 모바일 아이피를 이용한이동성 관리 방법 및 이를 위한 시스템 | |
WO2010108349A1 (zh) | 静态家乡代理访问的实现方法、系统以及移动节点 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09824619 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2010536697 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13126682 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20117010156 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009824619 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |