WO2010052920A1 - ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント - Google Patents
ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント Download PDFInfo
- Publication number
- WO2010052920A1 WO2010052920A1 PCT/JP2009/005915 JP2009005915W WO2010052920A1 WO 2010052920 A1 WO2010052920 A1 WO 2010052920A1 JP 2009005915 W JP2009005915 W JP 2009005915W WO 2010052920 A1 WO2010052920 A1 WO 2010052920A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- address
- handover
- message
- home
- mobile terminal
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 124
- 238000004891 communication Methods 0.000 claims abstract description 49
- 230000005540 biological transmission Effects 0.000 claims description 24
- 238000012545 processing Methods 0.000 description 57
- 230000027455 binding Effects 0.000 description 21
- 238000009739 binding Methods 0.000 description 21
- 238000001514 detection method Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 8
- 238000010295 mobile communication Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 3
- 230000009977 dual effect Effects 0.000 description 2
- 238000000060 site-specific infrared dichroism spectroscopy Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
-
- 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
-
- 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 the 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. 7 is a sequence chart for explaining an example of a conventional handover processing procedure.
- the attach process is started (step S702).
- the attach process includes a connection authentication process (step S703) by the authentication server HSS / AAA 701.
- the attach process is completed.
- the UE 107 acquires an IPv4 address using the DHCP protocol or the like (IPv4 address acquisition request, IPv4 address assignment: step S704), and registers this in the HA together with the HoAv6 acquired previously as the care-of address (CoAv4).
- IPv4 address acquisition request, IPv4 address assignment: step S704 IPv4 address acquisition request, IPv4 address assignment: step S704
- a binding request message (Binding Update: BU) is transmitted (step S705).
- the UE 107 uses the BU to execute an IPv4 home address (HoAv4) allocation request based on the DSMIP protocol.
- HoAv4 home address (HoAv4) allocation request based on the DSMIP protocol.
- the HA 106 receives the BU with the HoAv4 assignment request, 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 assign the HoAv4 (step S706).
- BA Binding Acknowledge
- the UE 107 can perform home link detection from the viewpoint of the IPv4 subnet, which has not been implemented conventionally, by comparing the acquired HoAv4 and CoAv4 subnet parts (step S707).
- 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. 7 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 in a mobile communication system using DSMIP, when a mobile terminal having only an IPv6 home address detects a handover to an access network that supports only IPv4, To obtain the IPv4 home address and distribute the obtained IPv4 home address to the mobile terminal in the handover destination access network. 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. Even when the mobile terminal performs the key update process, To provide a handover method capable of completing a binding process before and enabling packet transmission / reception without waiting for completion of a time-consuming key update process, and a mobile terminal and a home agent used in the method With the goal.
- a handover method for a mobile terminal that moves between at least two networks respectively corresponding to different unique IP versions that are communication protocols of the mobile terminal, the mobile terminal comprising: When performing handover from the first access router of the pre-handover network to which the terminal is currently connected to the second access router of the other network of the handover destination, the IP version supported by the handover destination network and the When the IP version supported by the network before the handover is different, the mobile terminal sends a first message including a home address assignment request request in the handover destination network via the first access router.
- Sent to the agent A second message including a request is transmitted via the second access router; and the home agent determines the handover destination based on the home address allocation request request included in the first message. Transmitting a third message including a home address in the network to the mobile terminal, and transmitting a fourth message including the home address to the mobile terminal based on the address acquisition request.
- communication efficiency is improved by reducing the tunnel overhead between the mobile terminal and the home agent, and the binding process is completed before the key update process even when the mobile terminal performs the key update process. It is possible to transmit and receive packets without waiting for completion of the key update process that requires time.
- the mobile terminal performs handover between at least two networks respectively corresponding to different IP versions that are unique communication protocols of the mobile terminal, and the pre-handover to which the mobile terminal is currently connected
- the IP version supported by the handover destination network corresponds to the network before the handover
- a mobile terminal comprising receiving means for receiving a fourth message including the home address transmitted by the home agent based on the address acquisition request.
- 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 IP version supported by the handover-destination network corresponds to the network before the handover
- Receiving means for receiving, from the mobile terminal, a first message including a home address assignment request request and a second message including an address acquisition request in the handover destination network, The first message A message for generating a third message including the home address at the handover destination based on the home address assignment request request of the mobile station and for generating a fourth message including the home address based on the address acquisition request.
- a home agent comprising generation means and transmission means for transmitting the generated third message and fourth message to the mobile terminal.
- the handover method of the present invention the mobile terminal and the home agent used in the method are cases where the tunnel overhead between the mobile terminal and the home agent is reduced to improve communication efficiency and the mobile terminal performs a 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
- the block diagram which shows an example of a structure of the mobile terminal 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
- 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 home agent which concerns on embodiment of this invention Diagram for explaining the prior art
- FIG. 1 is a diagram for explaining a system configuration according to the present invention, 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, which may be IPv6 routers or IPv4 routers 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 following IP version detection methods supported by the UE 107 are available. As one of them, there is a method of searching a database describing correspondence between an access network and a supported IP version.
- the identification of the access network may be unique, or an identifier such as an SSID or base station ID advertised by the access point using a beacon signal or the like, or an access router identifier (IP address) is handed over If it can be obtained prior to, it may be used.
- the database may be acquired in advance from a server on the network, or the UE 107 may be uniquely constructed from connection histories to various access networks.
- a Router Solicitation (RS) message for acquiring an IPv6 address is transmitted immediately after completion of the attach process, but a response is not received for a certain time.
- RS Router Solicitation
- the IP version supported by the network was notified during the attach process, but the IP address was instructed to be acquired by DHCP, or there was no notification of the IP version, and the IP address was simply acquired by DHCP.
- UE 107 responds based on transmission of a predetermined database information and a predetermined message (for example, an RS message for obtaining an IPv6 address) stored in association with the access network and IP version information supported by the access network.
- IP version supported based on at least one of information on presence / absence of reception, information on presence / absence of detection of predetermined packet (IPv6 packet), and information on presence / absence of instruction to acquire IP address from DHCP Are determined (detected).
- the UE 107 When the UE 107 detects that the access network 102 is a network that supports only IPv4, the UE 107 transmits a BU (first message) to the HA 106 via the access network 101 that is the handover source (step S202). At this time, the HoAv4 allocation request request is included in the BU. Furthermore, the UE 107 is undergoing handover, and information (for example, a flag (hereinafter referred to as flag X)) that instructs the IPv4 address assigned to the UE 107 in the handover destination access network 102 to be HoAv4 to be assigned may be included.
- flag X a flag
- 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 also the flag X) via the access network 101, the HA 106 transmits the BA (third message) including the HoAv4 to be allocated to the UE 107 (step S203), and the UE 107 performs the attach process.
- An address acquisition request (for example, based on the DHCP protocol) issued by the UE 107 is instructed via the HSS / AAA 701 to be transferred to the HA 106 to the AR 105 that has already started the attach process or has started the attach process ( HoA allocation instruction: Step S204). This instruction may be transmitted directly to the AR 105 without solving the HSS / AAA 701 or transferred to the AR 105 via a node other than the HSS / AAA 701.
- the AR 105 When performing address acquisition / distribution based on DHCP, the AR 105 receives this and activates the DHCP relay (Relay) function (DHCP relay activation: step S205). UE107 receives BA and acquires HoAv4. Further, the HA 106 may instruct the AR 105 to activate the PMIP protocol and transmit the PBU to the HA 106 when receiving a DHCP request. Accordingly, communication using a standard PMIP tunnel used in standards such as 3GPP can be performed. Note that the HA 106 may select either DHCP or PMIP according to the support status of the network or the UE 107, the subscription content, or the like, or for the purpose of reducing the processing load on the network device.
- the process starts.
- the HSS / AAA 701 instructs the AR 105 to assign the HoAv4 notified from the HA 106.
- an address acquisition request message IPv4 address acquisition request
- DHCP DHCP
- the address acquisition request message is transferred to the HA 106 according to the instruction received from the HA 106 via the HSS / AAA 701 first (step S207).
- the HA 106 recognizes that it is an address acquisition request message from the UE 107, and transmits an address acquisition response message (IPv4 address allocation (HoAv4)) describing the HoAv4 previously allocated via the access network 101 to the AR 105 (step S208).
- AR 105 transfers to UE 107 (step S209).
- the HA 106 recognizes that the received address acquisition request message is from the UE 107 as follows.
- the AR 105 stores the identifier (for example, Network Access Identifier: NAI) of the UE 107 acquired during the attach process in association with the communication bearer established by the attach process (a bearer ID is assigned in the 3G access system). Since the address acquisition request message transmitted by the UE 107 is transferred on the communication bearer established by the attach process, the AR 105 identifies that the received address acquisition request message is transmitted from the UE 107 and stores it first.
- the identifier (for example, NAI) of the UE 107 that has been stored is acquired.
- the AR 105 describes the identifier (NAI) of the UE 107 in the address acquisition request message or PBU, and transfers or transmits it to the HA 106.
- NAI identifier
- the HA 106 can acquire a message in which the identifier (NAI) of the UE 107 is described and recognize that the message is transmitted from the UE 107.
- the UE 107 confirms that the address assigned from the access network 102 and the HoAv4 subnet (or the address itself) acquired via the access network 101 are the same, that is, the access network 102 is a home link.
- the UE 107 may omit confirmation that the access network 102 is a home link (ie, home link detection). it can. As a result, it is possible to reduce the processing load on the UE 107 and shorten the handover time.
- the mobile terminal can temporarily issue the attach process before the address distribution procedure and issue HoAv4 via the access network 101 (step S202).
- the HA 106 notifies the HoAv4 assigned via the access network 101 to the HSS / AAA 701, and the HSS / AAA 701 instructs the AR 105 to assign the HoAv4 when the attach process is resumed.
- the HSS / AAA 701 transmits the DHCP request from the UE 107 to the HA 106 or activates the PMIP process to transmit the PBU to the HA 106. To instruct.
- the UE 107 that has acquired the same address as the HoAv4 from the access network 102 transmits a BU for registering the binding between the HoAv6 and the 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 after obtaining the same address as HoAv4 in the access network 102 can be omitted, and the speeding up of the handover can be consulted. 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 mobile terminal UE 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 BU for acquiring HoAv4 via the access network 101 includes information (for example, a flag) instructing to distribute HoAv4 in the same manner in all cases where the connection is made to an access network that supports only IPv4 in the future.
- the HA 106 may be notified.
- the HA 106 and the HSS / AAA 701 instruct the allocation of the HoAv4 to the AR of the connection destination access network during the attachment process by the UE 107 thereafter (step S204), and the AR performs the processes after step S205.
- the UE 107 performs key update processing
- the key update is performed. Binding processing can be completed before processing, and packet transmission / reception can be performed without waiting for completion of time-consuming key update processing.
- the UE 107 that has obtained the IPv4 home address from the handover source access network 101 using the present invention understands that the already connected access network can be the home link, so that the IPv4 by DHCP to be performed thereafter is performed. Acquisition of the address (the same address as the already acquired IPv4 home address is distributed) may be omitted. Thereby, the waiting time and data processing time associated with the DHCP protocol processing can be reduced, and the handover time can be shortened.
- the HA 106 sets the home address assigned to the UE 107. Distribution via the access network 102 is not possible.
- Information on whether or not the access network 102 can be a home link (hereinafter referred to as home link setting availability information) is managed by the authentication server HSS / AAA 701 and other management servers, and the HA 106 The home link setting availability information can be acquired by making an inquiry.
- the address acquisition processing (DHCP, attach) is performed in the access network 102 immediately after the UE 107 receives the BA. Even if the processing is continued), a correctly assigned home address can be obtained.
- a server for managing home link setting availability information is remotely deployed or a secure communication path must be established for access, it may take time for the HA 106 to acquire information. .
- the home link setting availability information cannot be acquired even while the UE 107 receives the BA and performs the address acquisition process, and actually the access network 102 can be set as the home link.
- the HA 106 cannot set the AR 105 as a DHCP relay or instruct the HA 106 to transmit a PBU when receiving a DHCP request, the IP address that the UE 107 can acquire is a local address deployed in the access network 102. It is assigned by the DHCP server.
- the UE 107 is recognized as an external link and is forced to communicate with a tunnel overhead. In order to avoid such a problem, it may be possible to delay the BA transmission until the HA 106 can acquire the home link setting availability information. However, since the handover process is in progress, the communication state deteriorates while the UE 107 waits for the BA reception. For example, the access network 101 may be disconnected, which is not preferable.
- the UE 107 that receives the BA via the access network 101 and starts the address acquisition process in the access network 102 usually performs several retries to acquire the address by one DHCP process.
- the DHCP process is terminated when the same address as the home address acquired by the BA can be acquired.
- the communication link is disconnected by delaying the BA, and the home address cannot be acquired because the BA cannot be received, or communication with a tunnel overhead using the local IP address although it is originally a home link is strong. And the like, and further, the key update process becomes unnecessary, and direct communication using the home address can be started.
- the UE 107 Transmits a home address acquisition request a predetermined number of times (retry).
- the HA 106 sets the handover destination access network as the home link to the BA to be transmitted when the home link setting availability information cannot be acquired and it cannot be determined whether the handover destination access network can be set as the home link.
- the UE 107 that has received the BA with this flag repeats the trial until the home address can be acquired by the DHCP process. That is, the HA 106 acquires information (home link setting availability information) for determining whether or not the handover destination access network can be set as a home link from a predetermined server (HSS / AAA 701 or the like)
- a flag indicating that the handover destination access network can be set as the home link is being added to the BA.
- the UE 107 may notify the UE 107 of the same information or this flag as indicated by this flag, when the UE 107 attaches to the access network 102, or by including it in an address acquisition response message. You may notify the result of availability. Thereby, even if it takes time to acquire the home link setting availability information, it is possible to increase the probability that the UE 107 can acquire the notification by delaying the notification.
- the maximum number of times that the UE 107 repeats the address acquisition for the address and the time for repeatedly performing the trial may be provided.
- the BA is set so that the acquired IP address is used as the address used in the access network 102. May be used to notify the UE 107 (for example, a notification flag is provided).
- the address acquisition process of the UE 107 is completed, and the IP address acquired at that time is assigned to the access network 102. It can be determined that the address is assigned in step (b), and the handover process can be completed early.
- FIG. 3 is a configuration diagram for explaining an example of the configuration of the mobile terminal according to the embodiment of the present invention.
- the transmission / reception units 301 and 302 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 303 performs IP layer processing
- the MIP processing unit 304 performs Mobile IP protocol processing based on DSMIP.
- the DHCP processing unit 305 performs DHCP protocol processing (client function).
- the handover control unit 306 determines or detects the feasibility and timing of handover based on the communication status obtained from the transmission / reception units 301 and 302, and performs handover to the MIP processing unit 304, the transmission / reception units 301 and 302, the DHCP processing unit 305, and the like. An instruction for sending is sent to control the handover process.
- the home address acquisition unit 307 is characteristic in the present invention, and an example of the operation will be described with reference to FIG.
- the handover control unit 306 determines whether to perform handover (step S401). If it is determined that the handover is to be performed, the home address acquisition unit 307 receives an instruction to start handover processing from the handover control unit 306, and detects whether the handover destination network (access network 102) is an access network that supports only IPv4 (step S1). S402). Since the detection method has been described above, the description thereof is omitted. When it is detected that the handover destination network is an access network that supports only IPv4, the MIP processing unit 304 is instructed to transmit a BU requesting the IPv4 home address (HoAv4) via the handover source access network (access network 101).
- HoAv4 IPv4 home address
- the MIP processing unit 304 may add information (for example, a flag) requesting that the address assigned in the handover destination network be the home address to the BU.
- the MIP processing unit 304 transmits a BU (with flag) requesting an IPv4 home address (step S403), is sent to the access network 101 via the IP processing unit 303 and the transmission / reception unit 301, and is transferred to the HA 106.
- the MIP processing unit 304 receives the BA from the HA 106 via the transmission / reception unit 301 and the IP processing unit 303, acquires the IPv4 home address (HoAv4) described in the BA (step S404), and the home address
- the acquisition unit 307 is notified.
- the home address acquisition unit 307 instructs the handover control unit 306 to start the attach process to the access network 102, and the handover control unit 306 instructs the transmission / reception unit 302 to start the attach process (step S405).
- the transmission / reception unit 302 transfers and sets the IP address to the IP processing unit 303.
- the handover control unit 306 receives the notification that the attach process has been completed from the transmission / reception unit 302, and the handover control unit 306 The unit 305 is instructed to start IP address acquisition.
- the DHCP processing unit 305 sends a DHCP request message to the access network 102 via the IP processing unit 303 and the transmission / reception unit 302, and sends a DHCP response message including the assigned IPv4 address as a response via the transmission / reception unit 302 and the IP processing unit 303.
- Step S405 The acquired IP address is set in the IP processing unit 303.
- the handover control unit 306 instructs the transmission / reception unit 301 to start the detach process from the access network 101 (step S406), and completes the handover process upon completion of the detach process.
- a normal handover process is performed unless the access network supports only IPv4.
- the detaching process may be omitted or may be performed in response to an instruction from the network.
- the IP address acquired during the attach process or the DHCP process is compared with the IP address acquired by the home address acquiring unit 307 via the access network 101 to determine that the link is a home link. .
- the request of the UE 107 transmitted at the same time when acquiring the home address is accepted, it is guaranteed that the IP address distributed in the access network 102 is the same as the home address, and home link determination is performed.
- the main feature of the present invention is that it is not necessary.
- FIG. 5 is a configuration diagram for explaining 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 DHCP processing unit 505 performs DHCP protocol processing (server function).
- the home address assignment unit 506 is characteristic in the present invention, and an example of the operation will be described with reference to FIG.
- the MIP processing unit 503 determines whether or not the BU from the UE 107 is received via the transmission / reception unit 501 and the IP processing unit 502 (step S601).
- receive a BU confirm whether there is an IPv4 home address assignment request request (and a flag requesting 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 S602), if present, the home address assignment unit 506 assigns an IPv4 home address (HoAv4) and transmits a BA to the UE 107 (step S603).
- an instruction message for operating the AR 105 as a DHCP relay is issued.
- the data is transmitted to the authentication server HSS / AAA 701 via the IP processing unit 502 and the transmission / reception unit 501 (DHCP request transfer instruction: step S604).
- the authentication server HSS / AAA 701 issues a desired instruction to the AR 105.
- a DHCP request message from the UE 107 transferred from the AR 105 later is transferred to the DHCP processing unit 505 via the transmission / reception unit 501 and the IP processing unit 502 (DHCP request acquisition: step S605), and the DHCP processing unit 505 sets the IP address to be assigned to the home. Obtained from the address assignment unit 506, included in the DHCP response message, transmitted via the IP processing unit 502 and the transmission / reception unit 501 (HoAv4 distribution: step S606), and transferred to the UE 107 via the AR 105 operating as the DHCP relay .
- the received DHCP request message includes the identifier of the UE 107 (for example, Network Access Identifier: NAI), and the HA 106 can determine that it is a DHCP request from the UE 107.
- the home address assignment unit 506 instructs the HA 106 to issue a PBU when the AR 105 receives a DHCP request instead of an instruction message for operating the AR 105 issued simultaneously with the IPv4 home address assignment as a DHCP relay.
- a message may be sent.
- the PMIP processing unit 504 receives the PBU message, acquires the home address from the home address assignment unit 506, and transmits it in the PBA message.
- the identifier for example, NAI
- the HA 106 can determine that the address is assigned to the UE 107.
- 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, or 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.
- Whether the access network 102 can be set as a home link by the HA 106 is related to the QoS and billing acquired from a policy server such as PCRF (Policy and Charging Rule Function) or the like. You may perform based on a policy and a rule (or network environment). For example, only when the UE 107 is subscribed to a plan in which a home address can be freely specified (or a home link can be specified), the setting is permitted or the communication capacity between the core network 103 and the access network 102 is limited ( When it is desired to reduce the header overhead, the access network to which the UE 107 is connected can be positively designated (set) as a home link.
- PCRF Policy and Charging Rule Function
- the IPv4 address uniquely generated by the UE 107 may be included in the HoAv4 allocation request that the UE 107 transmits to the HA 106 via the access network 101.
- the HA 106 sets the IPv4 address notified by the UE 107 as the actual IPv4 home address (HoAv4), or assigns HoAv4 separately, and in actual communication, the IPv4 address notified by the UE 107 and the HoAv4 assigned by the HA 106.
- HoAv4 IPv4 home address
- communication between the UE 107 and the external node can be realized.
- the HA 106 may request the PCRF to assign a policy (or rule) relating to QoS or accounting for the HoAv4 before transmitting the BA including the HoAv4 to be assigned to the UE 107 (step S203). Further, in response to this (or at the same timing as step S204), the QoS / billing policy in the access network 102 may be issued from the PCRF to the AR 105. As a result, communication based on appropriate QoS and charging policy can be performed.
- 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.
- information regarding the IP type supported by the access network 102 may be acquired from an external node and used.
- information regarding an IP type supported by the access network 102 may be acquired from a server that distributes access network information, and compared with the IP type in the access network before the handover.
- the HA 106 includes a flag (for example, flag Y) indicating that the address distributed via the access network 102 is a home address in the BA (including the assigned HoAv4) transmitted to the UE 107 via the access network 101. May be.
- a flag for example, flag Y
- the UE 107 recognizes that the connected handover destination access network 102 can be a home link, and does not wait for the completion of the DHCP procedure that has already started processing (or is scheduled to start).
- the communication in the handover destination access network 102 is started using the already acquired IPv4 home address (HoAv4) without omitting or starting the DHCP process (without waiting for the end).
- HoAv4 home address HoAv4 home address
- 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 the mobile terminal and the home agent used in the method are cases where the tunnel overhead between the mobile terminal and the home agent is reduced to improve communication efficiency and the mobile terminal performs a key update process.
- the binding process can be completed before the key update process, and the packet can be transmitted / received in the handover destination network without waiting for the completion of the key update process which takes time. This is useful for a handover method in a communication system that performs communication while moving between compatible networks, 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)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (14)
- 移動端末の通信規約である固有の異なるIPバージョンにそれぞれ対応する少なくとも2つのネットワーク間を移動する前記移動端末のハンドオーバ方法であって、
前記移動端末が現在接続しているハンドオーバ前のネットワークの第一のアクセスルータからハンドオーバ先の他のネットワークの第二のアクセスルータへハンドオーバをする際、前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なる場合、
前記移動端末が、前記ハンドオーバ先のネットワークにおけるホームアドレスの割り当て依頼要求を含む第1のメッセージを前記第一のアクセスルータを介してホームエージェントに送信し、アドレス取得要求を含む第2のメッセージを前記第二のアクセスルータを介して送信するステップと、
前記ホームエージェントが、前記第1のメッセージに含まれる前記ホームアドレスの割り当て依頼要求に基づいて、前記ハンドオーバ先のネットワークにおけるホームアドレスを含む第3のメッセージを前記移動端末へ送信し、前記アドレス取得要求に基づいて、前記ホームアドレスを含む第4のメッセージを前記移動端末へ送信するステップとを、
有するハンドオーバ方法。 - 前記第1のメッセージは、前記アドレス取得要求に基づいて前記ハンドオーバ先のネットワークにおいて割り当てられるアドレスを前記割り当て依頼要求で割り当てられるホームアドレスと同じものにすべき旨の要求を含む請求項1に記載のハンドオーバ方法。
- 前記ホームエージェントが、前記ハンドオーバ先のネットワークをホームリンクに設定することができるか否かを判断するための情報が得られていない場合、
前記移動端末は、前記アドレス取得要求を含む前記第2のメッセージを所定の回数送信する請求項1又は2に記載のハンドオーバ方法。 - 前記ホームエージェントが、前記ハンドオーバ先のネットワークをホームリンクに設定することができるか否かを判断するための情報が得られていない場合、前記第3のメッセージに前記ハンドオーバ先のネットワークをホームリンクに設定することができるか否かを判断中である旨のフラグを付加する請求項1に記載のハンドオーバ方法。
- 前記ホームエージェントが、前記ハンドオーバ先のネットワークにおいて割り当てられるアドレスが前記ホームアドレスと同じものであることを示す情報をさらに含む前記第3のメッセージを前記移動端末に送信し、
前記移動端末が前記情報を含む前記第3のメッセージを受信した際、前記第4のメッセージの受信を待つことなく、前記第3のメッセージに含まれる前記ホームアドレスを用いて、前記ハンドオーバ先のネットワークにおける通信を開始する請求項1に記載のハンドオーバ方法。 - 移動端末の通信規約である固有の異なるIPバージョンにそれぞれ対応する少なくとも2つのネットワーク間をハンドオーバする前記移動端末であって、
前記移動端末が現在接続しているハンドオーバ前のネットワークの第一のアクセスルータからハンドオーバ先の他のネットワークの第二のアクセスルータへハンドオーバをする場合、
前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なるか否かを判断する判断手段と、
それぞれのIPバージョンが異なると判断した場合、前記ハンドオーバ先におけるホームアドレスの割り当て依頼要求を含む第1のメッセージ、及びアドレス取得要求を含む第2のメッセージを生成するメッセージ生成手段と、
生成された前記第1のメッセージを前記第一のアクセスルータを介してホームエージェントに送信し、前記第2のメッセージを前記第二のアクセスルータを介して送信する送信手段と、
前記第1のメッセージに含まれる前記ホームアドレスの割り当て依頼要求に基づいて、前記ホームエージェントが送信する前記ハンドオーバ先のネットワークにおけるホームアドレスを含む第3のメッセージを受信し、前記第2のメッセージに含まれる前記アドレス取得要求に基づいて、前記ホームエージェントが送信する前記ホームアドレスを含む第4のメッセージを受信する受信手段とを、
備える移動端末。 - 前記第1のメッセージは、前記ハンドオーバ先のネットワークにおいて割り当てられるアドレスを前記割り当て依頼要求で割り当てられるホームアドレスと同じものにすべき旨の要求を含む請求項6に記載の移動端末。
- 前記判断手段は、ネットワークと当該ネットワークに対応するIPバージョンの情報とを関連付けて格納した所定のデータベースの情報、所定のメッセージの送信に基づく応答の受信の有無の情報、所定のパケットの検出の有無の情報、IPアドレスを取得する旨の指示の有無の情報のうち、少なくともいずれか1つに基づいてIPバージョンが異なるか否かを判断する請求項6又は7に記載の移動端末。
- 前記ホームエージェントが、前記ハンドオーバ先のネットワークをホームリンクに設定することができるか否かを判断するための情報が得られていないことの通知を受けた場合、
前記送信手段は、前記アドレス取得要求を含む前記第2のメッセージを所定の回数送信する請求項6に記載の移動端末。 - 前記受信手段が、前記ハンドオーバ先のネットワークにおいて割り当てられるアドレスが前記ホームアドレスと同じものであることを示す情報を含む前記第3のメッセージを受信した場合、
前記第4のメッセージの受信を待つことなく、前記第3のメッセージに含まれる前記ホームアドレスを用いて、前記ハンドオーバ先のネットワークにおける通信を開始する請求項6に記載の移動端末。 - 移動端末の通信規約である固有の異なるIPバージョンにそれぞれ対応する少なくとも2つのネットワーク間をハンドオーバする前記移動端末のホームエージェントであって、
前記移動端末が現在接続しているハンドオーバ前のネットワークの第一のアクセスルータからハンドオーバ先の他のネットワークの第二のアクセスルータへハンドオーバをする際、前記ハンドオーバ先のネットワークが対応しているIPバージョンと前記ハンドオーバ前のネットワークが対応しているIPバージョンとが異なる場合、
前記ハンドオーバ先のネットワークにおけるホームアドレスの割り当て依頼要求を含む第1のメッセージ、及びアドレス取得要求を含む第2のメッセージを前記移動端末から受信する受信手段と、
前記第1のメッセージの前記ホームアドレスの割り当て依頼要求に基づいて、前記ハンドオーバ先におけるホームアドレスを含む第3のメッセージを生成し、前記アドレス取得要求に基づいて、前記ホームアドレスを含む第4のメッセージを生成するメッセージ生成手段と、
生成された前記第3のメッセージ及び第4のメッセージを前記移動端末に送信する送信手段とを、
備えるホームエージェント。 - 前記第1のメッセージは、前記ハンドオーバ先のネットワークにおいて割り当てられるアドレスを前記割り当て依頼要求で割り当てられるホームアドレスと同じものにすべき旨の要求を含む請求項11に記載のホームエージェント。
- 前記ハンドオーバ先のネットワークをホームリンクに設定することができるか否かを判断するための情報を所定のサーバから取得する取得手段を更に備え、
前記取得手段によって前記情報が取得できていない場合に、前記メッセージ生成手段は、前記第3のメッセージに前記ハンドオーバ先のネットワークをホームリンクに設定することができるか否かを判断中である旨のフラグを付加する請求項12に記載のホームエージェント。 - 前記メッセージ生成手段が、前記ハンドオーバ先のネットワークにおいて割り当てられるアドレスが前記ホームアドレスと同じものであることを示す情報を含む前記第3のメッセージを生成する請求項11に記載のホームエージェント。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09824620A EP2346299A1 (en) | 2008-11-07 | 2009-11-06 | Handover method and mobile terminal and home agent used in the method |
CN2009801430803A CN102204394A (zh) | 2008-11-07 | 2009-11-06 | 移交方法以及在该方法中使用的移动终端和归属代理 |
US13/126,375 US9148826B2 (en) | 2008-11-07 | 2009-11-06 | Handover method and mobile terminal and home agent used in the method |
JP2010536698A JPWO2010052920A1 (ja) | 2008-11-07 | 2009-11-06 | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008286448 | 2008-11-07 | ||
JP2008-286448 | 2008-11-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010052920A1 true WO2010052920A1 (ja) | 2010-05-14 |
Family
ID=42152733
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2009/005915 WO2010052920A1 (ja) | 2008-11-07 | 2009-11-06 | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント |
Country Status (5)
Country | Link |
---|---|
US (1) | US9148826B2 (ja) |
EP (1) | EP2346299A1 (ja) |
JP (1) | JPWO2010052920A1 (ja) |
CN (1) | CN102204394A (ja) |
WO (1) | WO2010052920A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110225517A (zh) * | 2018-04-08 | 2019-09-10 | 华为技术有限公司 | 一种信息发送方法、密钥生成方法以及装置 |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8964697B2 (en) * | 2009-07-03 | 2015-02-24 | Panasonic Intellectual Property Management Co., Ltd. | Connection management method, connection management system, mobile terminal, packet data gateway and mobile management gateway |
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 |
CN113038547B (zh) * | 2019-12-24 | 2022-09-16 | 深圳市万普拉斯科技有限公司 | 网络连接方法、装置及移动终端 |
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 (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050099976A1 (en) * | 2003-09-23 | 2005-05-12 | Shu Yamamoto | Enabling mobile IPv6 communication over a network containing IPv4 components using a tunnel broker model |
US20070086382A1 (en) * | 2005-10-17 | 2007-04-19 | Vidya Narayanan | Methods of network access configuration in an IP network |
JP2010503244A (ja) * | 2006-09-06 | 2010-01-28 | パナソニック株式会社 | 通信システム及びモバイルルータ並びにホームエージェント |
US20080095114A1 (en) * | 2006-10-21 | 2008-04-24 | Toshiba America Research, Inc. | Key Caching, QoS and Multicast Extensions to Media-Independent Pre-Authentication |
KR100819055B1 (ko) * | 2006-12-08 | 2008-04-02 | 한국전자통신연구원 | 이동 IPv6 네트워크에서 플로우 기반 QoS 보장을위한 3 계층 핸드오버 경로 설정 방법 |
CN101374356B (zh) * | 2008-10-15 | 2012-02-15 | 中兴通讯股份有限公司 | IMS域内VoIP的切换方法、IMS系统、终端及VCC应用服务器 |
-
2009
- 2009-11-06 US US13/126,375 patent/US9148826B2/en not_active Expired - Fee Related
- 2009-11-06 CN CN2009801430803A patent/CN102204394A/zh active Pending
- 2009-11-06 WO PCT/JP2009/005915 patent/WO2010052920A1/ja active Application Filing
- 2009-11-06 JP JP2010536698A patent/JPWO2010052920A1/ja not_active Withdrawn
- 2009-11-06 EP EP09824620A patent/EP2346299A1/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 (Release8", 3GPP TS23.402 V8.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 IPv6", IETF RFC3775, June 2004 (2004-06-01) |
H. SOLIMAN: "Mobile IPv6 Support for Dual Stack Hosts and Routers, draft-ietf-mext-nemo- v4traversal-06.txt", 3 November 2008 (2008-11-03), XP015058497 * |
HESHAM SOLIMAN, MOBILE IPV6 SUPPORT FOR DUAL STACK HOSTS AND ROUTERS, 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, - 26 December 2007 (2007-12-26), pages 1792 - 1796, XP031196273 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110225517A (zh) * | 2018-04-08 | 2019-09-10 | 华为技术有限公司 | 一种信息发送方法、密钥生成方法以及装置 |
WO2019196668A1 (zh) * | 2018-04-08 | 2019-10-17 | 华为技术有限公司 | 一种信息发送方法、密钥生成方法以及装置 |
CN110225517B (zh) * | 2018-04-08 | 2020-07-14 | 华为技术有限公司 | 一种信息发送方法、装置、系统以及计算机可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US9148826B2 (en) | 2015-09-29 |
EP2346299A1 (en) | 2011-07-20 |
JPWO2010052920A1 (ja) | 2012-04-05 |
CN102204394A (zh) | 2011-09-28 |
US20110211558A1 (en) | 2011-09-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Yokota et al. | Fast handovers for proxy mobile IPv6 | |
JP6068532B2 (ja) | アクセスポイントへのユーザ機器のマルチパケットデータ接続を設定する方法及びノード | |
US8463926B2 (en) | Technique for providing support for a plurality of mobility management protocols | |
EP2090064B1 (en) | Methods and apparatus for implementing proxy mobile ip in foreign agent care-of address mode | |
WO2011001628A1 (ja) | コネクション管理方法、コネクション管理システム、移動端末、パケットデータゲートウェイ並びに移動管理ゲートウェイ | |
US20110096660A1 (en) | Handover processing method, and mobile terminal used in the method | |
EP1560378A2 (en) | Wireless mobility gateway | |
TW201315262A (zh) | 交偕操作中資源管理方法及裝置 | |
JP2009500980A (ja) | パケット交換基盤のネットワークにおけるコアネットワーク個体間ハンドオーバを遂行する方法及び装置 | |
US20100103876A1 (en) | Mobile terminal and communication management device | |
WO2009006848A1 (fr) | Procédé de commutation de réseau d'accès, dispositif de gestion d'ancrage, et dispositif d'accès mobile | |
JPWO2011001594A1 (ja) | リダイレクション方法、リダイレクションシステム、モバイルノード、ホームエージェント及び代理ノード | |
WO2010052920A1 (ja) | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント | |
KR101659986B1 (ko) | 메시지 송신 방법 및 범용 무선 패킷 서비스 지원 노드 | |
WO2010073620A1 (ja) | ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント | |
WO2009028885A2 (en) | Method and system for managing mobility in a mobile communication system using proxy mobile internet protocol | |
US8761119B2 (en) | Handover method, and mobile terminal and home agent used in the method | |
KR101373354B1 (ko) | 프락시 모바일 아이피 및 모바일 아이피 정보 전달 방법을이용하는 이동 통신 시스템의 이동성 관리 방법 및 시스템 | |
CN101471840B (zh) | 网络连接方法和网络系统 | |
WO2011055478A1 (ja) | 移動端末及びパケットフィルタ設定方法 | |
JP2006229831A (ja) | 異種網間接続切替方法及び異種網間接続システム | |
KR101357511B1 (ko) | 이동통신 시스템에서 프록시 모바일 아이피를 이용한 이동성 관리 방법 및 이를 위한 장치 | |
WO2010146815A1 (ja) | 移動管理プロトコル選択方法、移動管理プロトコル選択システム、モバイルノード、ホームエージェント及び代理ノード | |
Abbas et al. | A review of mobility supporting tunneling protocols in wireless cellular networks | |
JP3885942B2 (ja) | 移動端末のデータ通信方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200980143080.3 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09824620 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2010536698 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13126375 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009824620 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |