JP2008160791A - Mobile node and packet data serving node - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a flexible mobility framework for heterogeneous roaming, in the next-generation wireless networks. <P>SOLUTION: If a session is established between an MN (mobile node) and a PDSN (packet data serving node), then the PDSN acquires a first address from an HA (home agent) to assign it to the MN; the MN produces second and third addresses using a prefix of the first address and first and second interface IDs generated by the MN itself and notifies the second and third addresses to the PDSN; the PDSN registers the second and third addresses notified from the MN in the HA; the MN makes communication using the first, second and third addresses as addresses for SIP signaling, SIP media, and non-SIP based application, respectively; when the MN establishes a session with respect to another PDSN in hand-off, it produces the second and third addresses using the same first and second interface IDs as those prior to the hand-off. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a flexible mobility framework for heterogeneous roaming in a next generation wireless network, and more particularly, to a mobile node and a packet data serving node that realize flexible mobility for heterogeneous roaming in a next generation wireless network. .

Carriers on the wireless Internet have different mobility functions, and mobile clients can also have different mobility functions. In other words, IMS (IP Multimedia Subsystem) and MMD (Multimedia Domain) networks have heterogeneity in the mobility environment. For example, a certain carrier supports a mobile protocol controlled by a mobile node such as MIPv6 (Mobile IP version 6), and a certain carrier is controlled by a network such as PMIPv6 (Proxy Mobile IP version 6). The mobile node is provided with a mobility stack, and in some cases it is not provided. In the case of application-based, the mobile node uses an application layer mobility protocol.
3GPP2 X.S0013-002-A v1.0: “All-IP Core Network Multimedia Domain; IP Multimedia Subsystem-Stage 2”, November 2005 3GPP2 X.S0013-004-A v1.0: “All-IP Core Network Multimedia Domain: IP Multimedia Call Control based on SIP and SDP-Stage 3”, November 2005 IETF RFC3775 “Mobility Support in IPv6”

  Therefore, in order to support seamless roaming between different wireless carriers in the current heterogeneous mobility environment, there is no flexible mobility framework that supports seamless mobility between networks that support different mobility. It is important to provide a flexible mobility framework to enable roaming between carriers.

  The mobile node according to the first aspect of the present invention, after establishing a session with a packet data serving node, an address acquisition means for acquiring a first address acquired by the packet data serving node from a home agent in the same domain; Address generating means for generating the second and third addresses using the address prefix and the first and second interface IDs generated by itself, and an address for notifying the packet data serving node of the generated second and third addresses Communication means for communicating using the first, second, and third addresses as addresses for SIP signaling, SIP media, and non-SIP applications, respectively, and the address generation means comprises: , Other of the same domain by handoff When establishing a session with the packet data serving node generates a second and third address by using the same first and second interface ID as before the handoff.

  The packet data serving node according to the first aspect of the present invention, after establishing a session with a mobile node, obtains a first address from a home agent in the same domain and assigns it to the mobile node, and notifies from the mobile node Address registration means for registering the registered second and third addresses with the home agent of the same domain.

According to the first aspect of the present invention, when the session between the mobile node and the packet data serving node is established, the address allocation means of the packet data serving node acquires the first address from the home agent of the same domain and the mobile node The mobile node address acquisition means acquires the first address, and the mobile node address generation means uses the first address prefix and the first and second interface IDs generated by itself to obtain the second and third addresses. The mobile node address notification means notifies the packet data serving node of the generated second and third addresses, and the packet data serving node address registration means has the same second and third addresses notified from the mobile node. Register with domain home agent The mobile node communication means communicates using the first, second, and third addresses as addresses for SIP signaling, SIP media, and non-SIP applications, respectively. When a session with another packet data serving node in the same domain is established, second and third addresses are generated using the same first and second interface IDs as before handoff.
Therefore, the first, second, and third addresses do not change before and after handoff.
The first embodiment of the present invention includes both the case where the handoff is performed in the home domain and the case where the handoff is performed in the visited domain.

  The mobile node according to the second aspect of the present invention provides a second address acquired by the packet data serving node from a home agent in the same domain after establishing a session between the address holding means for holding the first address and the packet data serving node. The address acquisition means for acquiring the address, the address registration means for registering the acquired second address with the home agent of the same domain, the third address using the prefix of the second address and the first interface ID generated by itself. Address generating means for generating, address notifying means for notifying the generated third address to the packet data serving node, and the first, second and third addresses for SIP signaling, SIP media and non-SIP applications, respectively. A for The address generation means, when establishing a session with another packet data serving node in the same domain by handoff, using the same first interface ID as before handoff A third address is generated.

  The packet data serving node according to the second aspect of the present invention, after establishing a session with a mobile node, acquires a second address from a home agent in the same domain and assigns it to the mobile node, and notifies from the mobile node Address registration means for registering the registered third address with the home agent of the same domain.

According to the second aspect of the present invention, the address holding means of the mobile node holds the first address, and when the session between the mobile node and the packet data serving node is established, the address assignment means of the packet data serving node is the same. The second address is acquired from the home agent of the domain and assigned to the mobile node, the address acquisition unit of the mobile node acquires the second address, and the address registration unit of the mobile node transfers the acquired second address to the home agent of the same domain. The mobile node address generating means generates a third address using the second address prefix and the first interface ID generated by itself, and the mobile node address notifying means uses the generated third address as a packet data serving node. To the packet data service The address registration means of the mobile node registers the third address notified from the mobile node with the home agent of the same domain, and the communication means of the mobile node assigns the first, second and third addresses to SIP signaling, SIP media, When the mobile node address generation means establishes a session with another packet data serving node in the same domain by handoff, it uses the same first interface ID as before the handoff. To generate a third address.
Therefore, the first, second, and third addresses do not change before and after handoff.

  The mobile node according to the third aspect of the present invention comprises an address acquisition means for acquiring a first address acquired by the packet data serving node from a home agent of a home domain after establishing a session with the packet data serving node of the visited domain. Address generating means for generating third and fourth addresses using the first address prefix and the first and second interface IDs generated by itself, and the generated third and fourth addresses as the packet data serving node. Communication means for communicating using the first, third, and fourth addresses as addresses for SIP signaling, SIP media, and non-SIP applications, respectively, Address generation means can be When establishing a session with other packet data serving node of the serial visited domain, to generate a third and fourth address with the same first and second interface ID as before the handoff.

  The packet data serving node according to the third embodiment of the present invention obtains a second address from a home agent of the same domain after establishing a session with a mobile node having another domain as a home domain, and the home domain of the mobile node An address assignment means for obtaining a first address from the home agent and assigning the first address to the mobile node, and an address for registering the third and fourth addresses notified from the mobile node in the home agent of the same domain Registration means.

According to the third aspect of the present invention, when a session is established between a mobile node whose home domain is another domain and a packet data serving node in the visited domain, the address allocation means of the packet data serving node Obtaining the second address from the home agent, obtaining the first address from the home agent in the home domain of the mobile node, assigning the first address to the mobile node, and the address obtaining means of the mobile node obtains the first address; The mobile node address generation means generates the third and fourth addresses using the first address prefix and the first and second interface IDs generated by itself, and the mobile node address notification means generates the third and fourth addresses. Address packet data serving node The address registration means of the packet data serving node registers the third and fourth addresses notified from the mobile node with the home agent of the same domain, and the communication means of the mobile node assigns the first, third and fourth addresses. , Respectively, using SIP signaling, SIP media, and addresses for non-SIP applications, the address generation means of the mobile node establishes a session with other packet data serving nodes in the visited domain by handoff, Third and fourth addresses are generated using the same first and second interface IDs as before the handoff.
Therefore, the first, second, and third addresses do not change before and after handoff.

  The mobile node according to the fourth aspect of the present invention establishes a session between the address holding means for holding the first address and the packet data serving node in the visited domain, and then from the home agent in the visited domain to the packet data serving node. Using the address acquisition unit for acquiring the second address acquired by the user, the address registration unit for registering the second address with the home agent of the home domain, the prefix of the second address and the first interface ID generated by itself. Address generating means for generating three addresses, address notifying means for notifying the generated third address to the packet data serving node, and the first, second and third addresses respectively for SIP signaling, SIP media, SIP application Communication means using the address for the communication, and when the address generation means establishes a session with another packet data serving node in the visited domain by handoff, the first same as before the handoff A third address is generated using the interface ID.

  A packet data serving node according to a fourth aspect of the present invention obtains a second address from a home agent in the same domain after establishing a session with a mobile node having another domain as a home domain, and assigns the address to the mobile node. And address registration means for registering the third address notified from the mobile node with the home agent of the same domain.

According to the fourth aspect of the present invention, the address holding means of the mobile node holds the first address, and a session is established between the mobile node whose home domain is another domain and the packet data serving node of the visited domain. And the address assignment means of the packet data serving node obtains the second address from the home agent of the same domain and assigns it to the mobile node, the address acquisition means of the mobile node obtains the second address, and the address registration means of the mobile node is The second address is registered with the home agent of the home domain, the mobile node address generation means generates the third address using the second address prefix and the first interface ID generated by itself, and the mobile node address notification means The generated third address is used as the packet data The packet data serving node address registration means registers the third address notified from the mobile node with the home agent in the same domain, and the mobile node communication means assigns the first, second and third addresses. , Respectively, using SIP signaling, SIP media, and addresses for non-SIP applications, the address generation means of the mobile node establishes a session with other packet data serving nodes in the visited domain by handoff, A third address is generated using the same first interface ID as before handoff.
Therefore, the first, second, and third addresses do not change before and after handoff.

  Mobile nodes in next generation wireless networks may be under roaming that includes different types of mobility scenarios. These types of movement can be limited to the home domain or the visited domain. A mobile node is defined to be in roaming mode when the mobile node is in the visited domain away from the home domain. When a mobile node is in roaming mode, the mobile node moves between two subnetworks belonging to the same carrier domain or moves from one carrier domain to another carrier domain Is possible. In a roaming scenario, any mobile node can be in a local domain, including changing network components and mobility types supported in the mobile node stack, application types supported in the mobile node, and bearer manager It can be under some level of heterogeneity, such as the type of movement within the visited domain. Also, when present in the visited domain, the subscriber does not like its permanent IP address exposed to the visited carrier network.

  The present invention provides a comprehensive solution to solve IP address hiding issues for media by employing a multiple IP addressing approach where media (user data) and signaling use multiple different IP addresses . Also, the heterogeneity of applications supported in the mobile node (for example, based on SIP (Session Initiation Protocol) or not based on SIP), types of mobility support available in the mobile node and network, mobile node Consider some other parameters, such as the type of movement that the home network and visited network do. The framework described below can provide a solution for each possible combination including available mobility types, supported applications, and types of movement between networks.

  The present invention provides a series of solutions useful for different types of roaming such as home local, visited local, global mobility, and combinations. It mainly includes three types of mobility operations such as simple IP, proxy MIPv6, and client MIPv6, and builds a solution capable of providing seamless mobility support in a flexible manner. This framework uses a combination of mobile node mobility patterns, mobile node and network mobility capabilities, and application layer, network layer, and local mobility protocols that can be used based on the types of applications supported. For example, network layer mobility protocols such as MIPv6 and proxy MIP can use application layer solutions in the case of roaming that cannot provide the required seamless mobility. This solution is effective to support roaming between carriers including inter-domain and intra-domain global and local mobility.

FIG. 1 represents a roaming scenario. The carrier network plans to provide seamless mobility to mobile nodes in the home network along with the visited network. The communicating mobile node may be under different types of mobility based on movement within the home domain or visited domain. Home local mobility is defined as a mobile node moving between two different layer 3 attachment points in the home domain. When a mobile node moves from a home network to another carrier network, the movement is defined as global mobility. When a mobile node is in a new carrier network, it is placed under multiple types of handoffs. The carrier network can be divided into a number of sub-networks, and each sub-network is provided with a bearer manager called a visited bearer manager V-BM.
Similarly, a mobile node can move from one carrier network to another carrier network while away from the home network. In this case, each carrier network is provided with an individual bearer manager.
The following discussion focuses on providing seamless mobility while the mobile node is in the carrier network and is limited to local mobility. This scenario is defined as visited local mobility.

FIG. 2 illustrates visited global mobility, where a MN (Mobile Node) already exists in the visited domain, but in that domain a typical global moves from one subnetwork to another subnetwork. Represents a mobility scenario. In this case, each subnetwork has an individual visited bearer manager or home agent.
FIG. 3 represents visited global mobility, which is inter-domain roaming where a mobile node moves between two V-BMs.
FIG. 4 represents visited global mobility, where the mobile node already exists in the visited domain, but moves from one carrier network to another. This is called visited global mobility.

The types of movement described above are as follows.
Home local mobility-The movement of a mobile node is limited to the home domain.
Visited local mobility—The mobile node is in the visited domain and its movement is limited to the visited domain.
Global mobility—The mobile node moves from the home domain to the visited domain.
-The mobile node can move from one visited bearer domain (v-BM1) to another visited bearer domain (v-VM2).
A mobile node can move from one carrier network to another carrier network while away from the home network.
-Out of range here.

The above represents the kind of movement that a mobile node can be placed under during its roaming. When the movement of a mobile node is limited within its home domain, it is called home local mobility. When the mobile node leaves the home domain and moves to the carrier domain, it is called global mobility. During this movement, the mobile node can move to a carrier domain, which can be an A-IMS (Advances to IMS) based network or an MMD based network. It is also very likely that the target network does not support the same kind of mobility that is supported in the home domain. Once the mobile node is in the visited network and follows further movement, it is called visited local mobility unless the visited bearer manager changes.
There can be several types of global mobility. The first form of global mobility is when a mobile node moves from its home network to a new carrier network. The second form of global mobility includes when a mobile node moves from one visited bearer domain to another within the same carrier network. A third form of global mobility includes when a mobile node moves from one carrier network to another while away from the home network. In this case, it is natural to think that there are two VMs, one for each network.

The mobility stack (protocol stack for realizing the mobility function) is as follows.
・ Simple IPv6
-As the MN moves between PDSNs (Packet Data Serving Nodes), the temporary address changes.
One is for SIP signaling and the other is for media.
・ [MN] No MIP stack
・ [Network] No HA (Home Agent)
• Application-based mobility is required (eg SIP mobility)
・ CMIPv6 (Client Mobile IP version 6)
-When MN moves between PDSNs, CoA (Care of Address) changes, but HoA (Home Address) does not change.
-Static HoA is for SIP signaling and temporary HoA is for media.
[MN] MIP stack
・ [Network] HA
・ PMIPv6 (Proxy Mobile IP version 6)
-When MN moves between PDSNs, CoA changes but HoA does not change.
-Static HoA is for SIP signaling and temporary HoA is for media.
・ [MN] No MIP stack
[Network] PMA (Proxy Mobile Agent) in HA and PDSN

The above categorizes mobility solutions into three main categories such as simple IP, CMIP and PMIP. In the case of simple IP, there is no mobility stack at the mobile node, except for an application layer mobility stack such as SIP-based mobility. Since each mobile node is considered to have a SIP stack, no additional stack is required to support application layer mobility.
CMIPv6 is client mobile IPv6. In this case, the client has a mobile IP stack in addition to the home agent. When a mobile node uses CMIP, the mobile node is responsible for sending a MIP registration to the home agent when its care-of address changes. In order to implement CMIP, the network element should support signaling for the required mobility. A mobile node can use two different IP addresses, one for SIP signaling and one for media.
The third type of mobility support is to use PMIPv6. In this case, the mobile node's HoA does not change, but the CoA may change when the mobile node moves between PDSNs. For PMIPv6, a static HoA is used for SIP signaling and a temporary HoA is used for media. The CoA can change because there is no MIP stack at the mobile node, but there is a PMA at each PDSN. Usually, PMA is present in each PDSN.

The types of applications in application-based mobility are as follows.
A) SIP-based RTP (Real-time Transport Protocol) / UDP (for example, VoIP (Voice-over-IP))
B) RTP / UDP not based on SIP (for example, RTSP (Real Time Streaming Protocol) for IP / TV (Internet Protocol / TeleVision))
C) SIP / TCP / IP (eg chattcp)
D) TCP / IP not based on SIP (eg ftp, telnet)

  The above represents the types of applications that the mobile node can support. Each application type has different performance requirements with respect to delay and packet loss. Applications can basically be divided into two types, TCP / IP and RTP / UDP, depending on the type of transport. If the session is established using SIP-based signaling, the application is SIP-based. Examples of sessions based on SIP are Voice-over-IP and chattcp. Voice-over-IP is based on RTP / UDP, while chattcp is based on TCP. Similarly, there may be RTP / UDP applications that are not based on SIP, such as IP / TV. There are also TCP / IP applications that are not based on SIP, such as ftp and telnet.

  Table 1 represents possible mobility functions for each of the mobile node, home domain, and visited domain.

  In a roaming environment, clients and networks may have different types of mobility functions. For example, the mobile node can be a simple IP without a mobility stack. Alternatively, the mobile node can be provided with application layer SIP mobility, or can be provided with a client mobile IPv6 stack. The network also needs to be properly deployed to support client mobility capabilities. Therefore, the network does not support mobility except for basic routing support, or supports either MIPv6 or proxy MIP. In order to benefit from MIPv6 support in the network, the client also needs to be provided with a CMIPv6 stack. However, if the network does not support PMIP, clients that support either simple IP or SIP mobility can interoperate.

  The mobility protocol of the mobile node, that is, the terminal includes simple IP and CMIP (client mobile IP), and the mobility function of the network includes PMIP (proxy mobile IP) in addition to these. Table 2 shows the combination cases.

Hereinafter, among the combinations shown in Table 2, cases 1 to 4 will be described with respect to local mobility in the home domain, and cases 5 to 8 will be described with respect to local mobility in the visited domain.
Hereinafter, `` hMN '', `` hDHCP '', `` hPDSN '', `` hP-CSCF '', `` hS-CSCF '', `` hI-CSCF '', and `` hHA '' in the drawings and specification are present in the home domain, respectively. MN, DHCP (Dynamic Host Configuration Protocol) server, PDSN, P-CSCF (Proxy Call Session Control Function) server, S-CSCF (Serving Call Session Control Function) server , I-CSCF (Interrogate Call State Control Function) server, HA, where “hTemp”, “hHoA”, “hCoA” are temporary IP addresses assigned in the home domain, respectively , Home address, care-of address. Similarly, “vMN”, “vDHCP”, “vPDSN”, “vP-CSCF”, “vS-CSCF”, “vI-CSCF”, and “vHA” are the MN and DHCP server that exist in the visited domain, respectively. , PDSN, P-CSCF server, S-CSCF server, I-CSCF server, HA, where “vTemp”, “vHoA”, “vCoA” are temporary IP addresses assigned in the visited domain, It means home address and care-of address.

Below, the following points are considered as preconditions.
A media IP address is assigned for each application.
-The mobile IPv6 tunnel for media is not used between MN and HA. This is because, in EV-DO Rev.A (CDMA2000 1xEV-DO Revision A (IS-856-A)), one of the high-speed data communication standards belonging to CDMA2000, the overhead due to the encapsulation greatly affects the media stream. It is to do.

<Case 1>
With reference to FIG. 5, a procedure for acquiring an IP address of a mobile node in case 1 (MN: simple IP, home domain: simple IP) is shown.
After establishing a session with hPDSN1, hMN obtains IP address hTemp # 1 ((1) in FIG. 5). Subsequently, in order to obtain the address of the P-CSCF server (hP-CSCF), the hMN makes an inquiry to the DHCP server (hDHCP) ((2) in FIG. 5). At the same time, the hMN constructs addresses hTemp # 2 and hTemp # 3 using the acquired IPv6 prefix and the interface ID established by itself ((3) in FIG. 5). The hMN uses hTemp # 1 ((4) in FIG. 5) for the SIP signaling address, hTemp # 2 for the SIP media address, and hTemp # 3 for the non-SIP application.
Note that the generation of hTemp # 2 and hTemp # 3 is performed at the same time as the inquiry to the DHCP server before use in SIP media and non-SIP applications, respectively, as will be described below with reference to FIG. It does not have to be done.

FIG. 6 shows the sequence of case 1.
After the hMN establishes a session with hPDSN1 (LCP / CHAP), the hMN acquires an IP address hTemp # 1 (IPv6CP (hTemp # 1 Interface-ID), RA (hTemp # 1 Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN constructs addresses hTemp # 2 and hTemp # 3 using the acquired IPv6 prefix and the interface ID established by itself. hTemp # 1 is used for SIP signaling address, hTemp # 2 is used for SIP media address, hTemp # 3 is used for non-SIP applications (SIP Registration (hTemp # 1), SIP INVITE (SIP Signaling: hTemp # 1, Media : hTemp # 2), IP data (SIP: hTemp # 2, non-SIP: hTemp # 3)).

In this case, unless mobility at the application layer is performed, the IP address changes at the time of handoff, so it is disconnected once. That is, when hMN hands off,
After establishing a session with hPDSN2 (LCP / CHAP), hMN obtains IP address hTemp # 4 (IPv6CP (hTemp # 4 Interface-ID), RA (hTemp # 4 Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN constructs addresses hTemp # 5 and hTemp # 6 using the acquired IPv6 prefix and the interface ID established by itself. hTemp # 4 is used for SIP signaling address, hTemp # 5 is used for SIP media address, hTemp # 6 is used for non-SIP applications (SIP Registration (hTemp # 4), SIP INVITE (SIP Signaling: hTemp # 4, Media : hTemp # 5), IP data (SIP: hTemp # 5, non-SIP: hTemp # 6)).
As described above, in case 1, when handoff is performed in the home domain, the SIP signaling address, the SIP media address, and the non-SIP application address change.

<Case 2>
FIG. 7 shows an IP address acquisition procedure of the mobile node in case 2 (MN: simple IP, home domain: PMIP).
After establishing a session with hMN, hPDSN1 sends a PMIP BU (Proxy MIP Binding Update) to hHA in order to acquire IP address hHoA # 1 ((1) in FIG. 7). The hHA includes the hHoA # 1 address in the response to the hPDSN1. hPDSN1 assigns hHoA # 1 to hMN ((2) in FIG. 7). Subsequently, in order to obtain the address of the P-CSCF server (hP-CSCF), the hMN makes an inquiry to the DHCP server (hDHCP) ((3) in FIG. 7). At the same time, the hMN constructs addresses hHoA # 2 and hHoA # 3 using the acquired IPv6 prefix and the interface ID established by itself ((4) in FIG. 7). Subsequently, hMN transmits the information of hHoA # 2 and hHoA # 3 to hPDSN1, and hPDSN1 registers these addresses in hHA ((5) in FIG. 7), and sends PMIP BU from hPDSN1 to hHA. hHoA # 3 is notified). The hMN uses hHoA # 1 ((6) in FIG. 7) as a SIP signaling address, hHoA # 2 as a SIP media address, and hHoA # 3 as a non-SIP application.
Note that the generation of hHoA # 2 and hHoA # 3 is performed at the same time as inquiries to the DHCP server before use in SIP media and non-SIP applications, as described below with reference to FIG. It does not have to be done.

FIG. 8 shows the sequence of case 2.
After the hPDSN1 establishes a session with the hMN (LCP / CHAP), it sends a PMIP BU to the hHA, and the hHA includes the hHoA # 1 address in the response to the hPDSN1 (PMIP Reg./Reply (hHoA # 1)). The hPDSN1 assigns hHoA # 1 to the hMN (IPv6CP (hHoA # 1 Interface-ID), RA (hHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN constructs addresses hHoA # 2 and hHoA # 3 using the acquired IPv6 prefix and the interface ID established by itself. Subsequently, hMN transmits information on hHoA # 2 and hHoA # 3 to hPDSN1, and hPDSN1 registers these addresses in hHA (not shown in FIG. 8). hHoA # 1 is used for SIP signaling address, hHoA # 2 is used for SIP media address, hHoA # 3 is used for non-SIP applications (SIP Registration (hHoA # 1), SIP INVITE (SIP Signaling: hHoA # 1, Media : hHoA # 2), IP data (SIP: hHoA # 2, non-SIP: hHoA # 3)).

In this case, handoff is possible by using hHA. Addresses can be used continuously by building the same interface ID after handoff. That is, when hMN hands off and establishes a session with hPDSN2 (LCP / CHAP), hPDSN2 sends PMIP BU to hHA, and hHA includes the hHoA # 1 address in the response to hPDSN2 (PMIP Reg./Reply ( hHoA # 1)). The hPDSN 2 assigns hHoA # 1 to the hMN (IPv6CP (hHoA # 1 Interface-ID), RA (hHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN constructs addresses hHoA # 2 and hHoA # 3 using the acquired IPv6 prefix and the same interface ID as before the handoff. Subsequently, hMN transmits information on hHoA # 2 and hHoA # 3 to hPDSN2, and hPDSN2 registers these addresses in hHA (not shown in FIG. 8). hHoA # 1 is used for SIP signaling address, hHoA # 2 is used for SIP media address, and hHoA # 3 is used for non-SIP applications (IP data (SIP: hHoA # 2, non-SIP: hHoA # 3)).
As described above, in case 2, even if handoff is performed in the home domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change. That is, seamless handoff is supported.

<Case 3>
FIG. 9 shows a procedure for acquiring the IP address of the mobile node in case 3 (MN: CMIP, home domain: PMIP).
The hMN holds a home address hHoA # 1 as a mobile node that supports CMIP, or is assigned in a lower layer. After establishing a session with hMN, hPDSN1 sends a PMIP BU (Proxy MIP Binding Update) to hHA in order to obtain IP address hHoA # 2 ((1) in FIG. 9). hHA includes the hHoA # 2 address in the response to hPDSN1. hPDSN1 assigns hHoA # 2 to hMN ((2) in FIG. 9). Subsequently, in order to obtain the address of the P-CSCF server (hP-CSCF), the hMN makes an inquiry to the DHCP server (hDHCP) ((3) in FIG. 9). The hMN sends CMIP BU to the hHA and registers hHoA # 2 ((4) in FIG. 9). The hMN uses the acquired IPv6 prefix and the interface ID established by itself to construct an address hHoA # 3 ((5) in FIG. 9). Subsequently, the hMN transmits the information of hHoA # 3 to the hPDSN1, and the hPDSN1 registers this address in the hHA ((6) in FIG. 9, PMPM BU is sent from the hPDSN1 to the hHA to notify the hHoA # 3). The hMN uses hHoA # 1 ((7) in FIG. 9) as a SIP signaling address, hHoA # 2 as a SIP media address, and hHoA # 3 as a non-SIP application.
The generation of hHoA # 3 may be performed before use in a non-SIP application, as will be described below with reference to FIG.

FIG. 10 shows the case 3 sequence.
When the hPDSN1 establishes a session with the hMN (LCP / CHAP), the PMIP BU is sent to the hHA, and the hHA includes the hHoA # 2 address in the response to the hPDSN1 (PMIP Reg./Reply (hHoA # 2)). hPDSN1 assigns hHoA # 2 to hMN (IPv6CP (hHoA # 2 Interface-ID), RA (hHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hHA, hP-CSCF)). Also, the hMN sends CMIP BU to the hHA and registers hHoA # 2 (CMIP Update (CoA: hHoA # 2)). The hMN constructs the address hHoA # 3 using the acquired IPv6 prefix and the interface ID established by itself. Subsequently, hMN transmits the information of hHoA # 3 to hPDSN1, and hPDSN1 registers this address with hHA (not shown in FIG. 10). hHoA # 1 is used for SIP signaling address, hHoA # 2 is used for SIP media, hHoA # 3 is used for non-SIP applications (SIP Registration (hHoA # 1), SIP INVITE (SIP Signaling: hHoA # 1, Media : hHoA # 2), IP data (SIP: hHoA # 2, non-SIP: hHoA # 3)).

In this case, handoff is possible by using hHA. Addresses can be used continuously by building the same interface ID after handoff. That is, when hMN hands off and establishes a session with hPDSN2 (LCP / CHAP), hPDSN2 sends PMIP BU to hHA, and hHA includes the hHoA # 2 address in the response to hPDSN2 (PMIP Reg./Reply ( hHoA # 2)). hPDSN2 assigns hHoA # 2 to hMN (IPv6CP (hHoA # 2 Interface-ID), RA (hHoA # 2 Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hHA, hP-CSCF)). The hMN constructs the address hHoA # 3 using the acquired IPv6 prefix and the same interface ID as before the handoff. Subsequently, hMN transmits the information of hHoA # 3 to hPDSN2, and hPDSN2 registers this address with hHA (not shown in FIG. 10). hHoA # 1 is used for SIP signaling addresses, hHoA # 2 is used for SIP media addresses, and hHoA # 3 is used for non-SIP applications (IP data (SIP: hHoA # 2, non-SIP: hHoA # 3 )).
That is, CMIP supports handoff for SIP and PMIP supports handoff for media.
As described above, in case 3, even if handoff is performed in the home domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change. That is, seamless handoff is supported.

<Case 4>
FIG. 11 shows a procedure for acquiring an IP address of a mobile node in case 4 (MN: CMIP, home domain: CMIP).
The hMN holds a home address hHoA # 1 as a mobile node that supports CMIP, or is assigned in a lower layer. The hPDSN1 assigns hCoA # 2 to the hMN ((1) in FIG. 11). Subsequently, in order to obtain the address of the P-CSCF server (hP-CSCF), the hMN makes an inquiry to the DHCP server (hDHCP) ((2) in FIG. 11). At the same time, the hMN constructs an address hTemp # 3 using the acquired IPv6 prefix and the interface ID established by itself ((3) in FIG. 11). The hMN sends a CMIP BU (CMIP Binding Update) to the hHA in order to register the information of hCoA # 2 in the hHA ((4) in FIG. 11). The hMN uses hHoA # 1 ((5) in FIG. 11) as a SIP signaling address, hCoA # 2 as a SIP media address, and hTemp # 3 as a non-SIP application.
As will be described below with reference to FIG. 12, the generation of hTemp # 3 does not have to be performed simultaneously with the inquiry to the DHCP server before the address is used in a non-SIP application.

FIG. 12 shows the sequence of case 4.
When hPDSN1 establishes a session with hMN (LCP / CHAP), it assigns hCoA # 2 to hMN (IPv6CP (hCoA # 2 Interface-ID), RA (hCoA # 2 Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hHA, hP-CSCF)). In order to register hCoA # 2 information in hHA, hMN sends CMIP BU to hHA and registers hCoA # 2 (CMIP Update (CoA: hCoA # 2)). The hMN constructs an address hTemp # 3 by using the acquired IPv6 prefix and the interface ID established by itself. hHoA # 1 is used for SIP signaling address, hCoA # 2 is used for SIP media address, hTemp # 3 is used for non-SIP applications (SIP Registration (hHoA # 1), SIP INVITE (SIP Signaling: hHoA # 1, Media : hCoA # 2), IP data (SIP: hCoA # 2, non-SIP: hTemp # 3)).

In this case, although hHA exists, the mobile IP tunnel cannot be used in the wireless section due to bandwidth limitation. Therefore, since the home address is not used for the address used for the medium, a new IP address is acquired after the handoff. That is, when hMN hands off and establishes a session with hPDSN2 (LCP / CHAP), hPDSN2 assigns hCoA # 4 to hMN (IPv6CP (hCoA # 4 Interface-ID), RA (hCoA # 4 Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hHA, hP-CSCF)). The hMN sends CMIP BU to the hHA in order to register hCoA # 4 information in the hHA (CMIP Update (CoA: hCoA # 4)). The hMN constructs the address hTemp # 5 using the acquired IPv6 prefix and the interface ID established by itself. hHoA # 1 is used for SIP signaling address, hCoA # 4 is used for SIP media address, and hTemp # 5 is used for non-SIP applications (IP data (SIP: hCoA # 2, non-SIP: hTemp # 3)).
As described above, in case 4, when the handoff is performed in the home domain, the SIP signaling address does not change, but the SIP media address and the non-SIP application address change.

<Case 5>
FIG. 13 shows the IP address acquisition procedure of the mobile node in case 5 (MN: simple IP, home domain: simple IP, visited domain: simple IP).
The hMN operates as a mobile node that supports simple IP. The vPDSN 1 assigns vTemp # 1 to the hMN ((1) in FIG. 13). Subsequently, in order to obtain the address of the P-CSCF server (vP-CSCF), the hMN makes an inquiry to the DHCP server (vDHCP) ((2) in FIG. 13). At the same time, the hMN constructs addresses vTemp # 2 and vTemp # 3 using the acquired IPv6 prefix and the interface ID established by itself ((3) in FIG. 13). VTemp # 1 ((4) in FIG. 13) is used for the SIP signaling address, vTemp # 2 is used for the SIP media address, and vTemp # 3 is used for the non-SIP application.
Note that generation of vTemp # 2 and vTemp # 3 is performed at the same time as inquiries to the DHCP server before use in SIP media and non-SIP applications, as described below with reference to FIG. It does not have to be done.

FIG. 14 shows the case 5 sequence.
When vPDSN1 establishes a session with hMN (LCP / CHAP), vPDemp # 1 is allocated to hMN (IPv6CP (vTemp # 1 Interface-ID), RA (vTemp # 1 Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (vP-CSCF)). The hMN constructs addresses vTemp # 2 and vTemp # 3 using the acquired IPv6 prefix and the interface ID established by itself. vTemp # 1 is used for SIP signaling address, vTemp # 2 is used for SIP media address, vTemp # 3 is used for non-SIP applications (SIP Registration (vTemp # 1), SIP INVITE (SIP Signaling: vTemp # 1, Media : vTemp # 2), IP data (SIP: vTemp # 2, non-SIP: vTemp # 3)).

In this case, since it is a simple IP, a new IP address is acquired after handoff. That is, when hMN hands off and establishes a session with vPDSN2 (LCP / CHAP), vPDSN2 assigns vTemp # 4 to hMN (IPv6CP (vTemp # 4 Interface-ID), RA (vTemp # 4 Prefix)). Subsequently, in order to acquire the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN constructs addresses vTemp # 5 and vTemp # 6 using the acquired IPv6 prefix and the interface ID established by itself. vTemp # 4 is used for SIP signaling address, vTemp # 5 is used for SIP media address, vTemp # 6 is used for non-SIP applications (SIP Registration (vTemp # 4), SIP INVITE (SIP Signaling: vTemp # 4, Media : vTemp # 5), IP data (SIP: vTemp # 5, non-SIP: vTemp # 6)).
As described above, in case 5, when handing off within the visited domain, the SIP signaling address, the SIP media address, and the non-SIP application address change.

<Case 6>
FIG. 15 shows an IP address acquisition procedure of the mobile node in case 6 (MN: simple IP, home domain: simple IP, visited domain: PMIP).
The hMN operates as a mobile node that supports simple IP. The vPDSN 1 sends PMIP BU to the vHA, acquires vHoA # 1 ((1) in FIG. 15), and assigns it to the hMN ((2) in FIG. 15). Subsequently, in order to obtain the address of the P-CSCF server (vP-CSCF), the hMN makes an inquiry to the DHCP server (vDHCP) ((3) in FIG. 15). At the same time, the hMN constructs addresses vHoA # 2 and vHoA # 3 using the acquired IPv6 prefix and the interface ID established by itself ((4) in FIG. 15). Subsequently, the hMN transmits vHoA # 2 and vHoA # 3 information to the vPDSN1, and the vPDSN1 registers these addresses in the vHA ((5) in FIG. 5). VHoA # 1 ((6) in FIG. 15) is used for the SIP signaling address, vHoA # 2 is used for the SIP media address, and vHoA # 3 is used for the non-SIP application.
Note that vHoA # 2 and vHoA # 3 are generated at the same time as the inquiry to the DHCP server before being used in SIP media and non-SIP applications, as will be described below with reference to FIG. It does not have to be done.

FIG. 16 shows the sequence of case 6.
When vPDSN1 establishes a session with hMN (LCP / CHAP), it sends PMIP BU (PMIP Binding Update) to vHA to obtain vHoA # 1 (PMIP Reg./Reply (vHoA # 1)) and assigns it to hMN (IPv6CP (vHoA # 1 Interface-ID), RA (vHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (vP-CSCF)). The hMN constructs addresses vHoA # 2 and vHoA # 3 using the acquired IPv6 prefix and the interface ID established by itself. Subsequently, the hMN transmits vHoA # 2 and vHoA # 3 information to the vPDSN1, and the vPDSN1 registers these addresses in the vHA (PMIP Update (vHoA # 2), PMIP Update (vHoA # 3)). vHoA # 1 is used for SIP signaling address, vHoA # 2 is used for SIP media address, vHoA # 3 is used for non-SIP applications (SIP Registration (vHoA # 1), SIP INVITE (SIP Signaling: vHoA # 1, Media : vHoA # 2), IP data (SIP: vHoA # 2, non-SIP: vHoA # 3)).

In this case, hMN supports simple IP, but handoff is possible because PMIP is supported in the visited domain. After handoff, the same IP address is constructed by using the same interface ID as before handoff. That is, when hMN hands off and establishes a session with vPDSN2 (LCP / CHAP), vPDSN2 sends PMIP BU (PMIP Binding Update) to vHA to obtain vHoA # 1 (PMIP Reg./Reply (vHoA # 1)), assigned to hMN (IPv6CP (vHoA # 1 Interface-ID), RA (vHoA Prefix)). Subsequently, in order to acquire the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN constructs addresses vHoA # 2 and vHoA # 3 using the acquired IPv6 prefix and the same interface ID as before handoff. Subsequently, the hMN transmits vHoA # 2 and vHoA # 3 information to the vPDSN2, and the vPDSN2 registers these addresses in the vHA (PMIP Update (vHoA # 2, vHoA # 3)). vHoA # 1 is used for SIP signaling address, vHoA # 2 is used for SIP media address, and vHoA # 3 is used for non-SIP applications (IP data (SIP: vHoA # 2, non-SIP: vHoA # 3)).
As described above, in case 6, even if handoff is performed in the visited domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change. That is, seamless handoff is supported.

<Case 7>
FIG. 17 shows the IP address acquisition procedure of the mobile node in case 7 (MN: simple IP, home domain: PMIP, visited domain: PMIP).
The hMN operates as a mobile node that supports simple IP. vPDSN1 sends PMIP BU (PMIP Binding Update) to vHA and hHA to obtain vHoA # 2 and hHoA # 1 ((1) and (1 ′) in FIG. 17), and assigns hHoA # 1 to hMN ( FIG. 17 (2)). Also assign vHoA # 1 prefix. Subsequently, in order to obtain the address of the P-CSCF server (hP-CSCF), the hMN makes an inquiry to the DHCP server (hDHCP) ((3) in FIG. 17). At the same time, the hMN constructs addresses vHoA # 3 and vHoA # 4 using the same IPv6 prefix as the acquired vHoA # 1 and the interface ID established by itself ((4) in FIG. 17). Subsequently, the hMN transmits vHoA # 3 and vHoA # 4 information to the vPDSN1, and the vPDSN1 registers these addresses in the vHA ((5) in FIG. 5). HHoA # 1 ((6) in FIG. 17) is used for the SIP signaling address, vHoA # 3 is used for the SIP media address, and vHoA # 4 is used for the non-SIP application.
It should be noted that the generation of vHoA # 3 and vHoA # 4 is performed at the same time as the inquiry to the DHCP server before use in SIP media and non-SIP applications, as described below with reference to FIG. It does not have to be done.
Note that vHoA IP # 2 is not used. PMA (PDSN) needs to notify prefixes to two HAs.

FIG. 18 shows the sequence of case 7.
When vPDSN1 establishes a session with hMN (LCP / CHAP), it sends PMIP BU to vHA and hHA to obtain vHoA # 2 and hHoA # 1 respectively (PMIP Reg./Reply (vHoA # 2), PMIP Reg ./Reply (hHoA # 1)) and hHoA # 1 are allocated to the hMN (IPv6CP (hHoA # 1 Interface-ID)). A vHoA # 1 prefix is also assigned (RA (hHoA, vHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN uses the same IPv6 prefix as the acquired vHoA # 1 and the interface ID established by itself, and constructs addresses vHoA # 3 and vHoA # 4. Subsequently, the hMN transmits vHoA # 3 and vHoA # 4 information to the vPDSN1, and the vPDSN1 registers these addresses in the vHA (PMIP Update (vHoA # 3), PMIP Update (vHoA # 4)).

In this case, hMN supports simple IP, but handoff is possible because PMIP is supported in the visited domain. After handoff, the same IP address is constructed by using the same interface ID as before handoff. That is, when hMN hands off and establishes a session with vPDSN2 (LCP / CHAP), vPDSN2 sends PMIP BU to vHA and hHA to obtain vHoA # 2 and hHoA # 1 respectively (PMIP Reg./Reply ( vHoA # 2), PMIP Reg./Reply (hHoA # 1)) and hHoA # 1 are assigned to the hMN (IPv6CP (hHoA # 1 Interface-ID)). A vHoA # 1 prefix is also assigned (RA (hHoA, vHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hP-CSCF)). The hMN constructs addresses vHoA # 3 and vHoA # 4 using the same IPv6 prefix as the acquired vHoA # 1 and the same interface ID as before the handoff. Subsequently, the hMN transmits vHoA # 3 and vHoA # 4 information to the vPDSN2, and the vPDSN2 registers these addresses in the vHA (PMIP Update (vHoA # 3, vHoA # 4)). hHoA # 1 is used for SIP signaling address, vHoA # 3 is used for SIP media address, and vHoA # 4 is used for non-SIP applications (IP data (SIP: vHoA # 3, non-SIP: vHoA # 4)).
As described above, in case 7, even if handoff is performed in the visited domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change. That is, seamless handoff is supported.

<Case 8>
FIG. 19 shows an IP address acquisition procedure of the mobile node in Case 8 (MN: CMIP, home domain: PMIP, visited domain: PMIP).
The hMN holds a home address hHoA # 1 as a mobile node that supports CMIP, or is assigned in a lower layer. The vPDSN 1 sends a PMIP BU (PMIP Binding Update) to the vHA, acquires the vHoA # 2 ((1) in FIG. 19), and assigns it to the hMN ((2) in FIG. 19). Subsequently, in order to obtain the address of the P-CSCF server (hP-CSCF), the hMN makes an inquiry to the DHCP server (hDHCP) ((3) in FIG. 19). The hMN sends CMIP BU to the hHA and registers vHoA # 2 ((4) in FIG. 19). The hMN constructs vHoA # 3 by using the same IPv6 prefix as that of the acquired vHoA # 2 and the interface ID established by itself ((5) in FIG. 19). The vPDSN 1 sends PMIP BU to the vHA and notifies vHoA # 3 ((6) in FIG. 19). HHoA # 1 ((7) in FIG. 19) is used for the SIP signaling address, vHoA # 2 is used for the SIP media address, and vHoA # 3 is used for the non-SIP application.

FIG. 20 shows the sequence of case 8.
When vPDSN1 establishes a session with hMN (LCP / CHAP), it sends PMIP BU to vHA to obtain vHoA # 2 (PMIP Reg./Reply (vHoA # 2)) and assigns it to hMN (IPv6CP (vHoA # 2 Interface-ID), RA (hHoA, vHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hHA, hP-CSCF)). The hMN sends CMIP BU to the hHA and registers vHoA # 2 (CMIP Update (CoA: vHoA # 2)). Since the hMN establishes an interface ID by itself but has already acquired vHoA # 2, this interface ID is not used. vPDSN1 sends PMIP BU to vHA and notifies vHoA # 2 (PMIP Update (vHoA # 2)). The hMN constructs vHoA # 3 by using the same IPv6 prefix as that of the acquired vHoA # 2 and the interface ID established by itself. Subsequently, the hMN transmits vHoA # 3 information to the vPDSN1, and the vPDSN1 registers this address in the vHA (PMIP Update (vHoA # 3)). hHoA # 1 is used for SIP signaling address, vHoA # 2 is used for SIP media, and vHoA # 3 is used for non-SIP applications (SIP Registration (hHoA # 1), SIP INVITE (SIP Signaling: hHoA # 1, Media : vHoA # 2), IP data (SIP: vHoA # 2, non-SIP: vHoA # 3)).

In this case, handoff is possible by using vHA. After handoff, the same IP address is constructed by using the same interface ID as before handoff. That is, when hMN hands off and establishes a session with vPDSN2 (LCP / CHAP), vPDSN2 sends PMIP BU to vHA to obtain vHoA # 2 (PMIP Reg./Reply (vHoA # 2)), hMN (IPv6CP (vHoA # 2 Interface-ID), RA (hHoA, vHoA Prefix)). Subsequently, in order to obtain the address of the P-CSCF server, the hMN makes an inquiry to the DHCP server (DHCP Inform (hHA, hP-CSCF)). Since the hMN establishes an interface ID by itself but has already acquired vHoA # 2, this interface ID is not used. The hMN constructs vHoA # 3 using the same IPv6 prefix as that of the acquired vHoA # 2 and the same interface ID as before the handoff. Subsequently, the hMN transmits vHoA # 2 and vHoA # 3 information to the vPDSN2, and the vPDSN2 registers these addresses in the vHA (PMIP Update (vHoA # 2, vHoA # 3)). hHoA # 1 is used for SIP signaling address, vHoA # 2 is used for SIP media address, and vHoA # 3 is used for non-SIP applications (IP data (SIP: vHoA # 2, non-SIP: vHoA # 3)).
As described above, in case 8, even if handoff is performed in the visited domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change. That is, seamless handoff is supported.

<Summary of each case>
From the above, cases 2, 3, 6, 7, and 8 realize local mobility of the mobile node.
Table 3 shows details of these different cases. In Table 3, the column “home domain” represents the IP address before handoff in the home domain, the column “home local mobility” represents the IP address after handoff in the home domain, and “visited domain”. Column represents the IP address before handoff in the visited domain, and the “visited local mobility” column represents the IP address after handoff in the visited domain.

  In case 4 described in the top row of Table 3, as described with reference to FIGS. 11 and 12, when handoff is performed in the home domain, the SIP signaling address does not change, but the SIP media address, non-SIP The address of the system application changes.

Next, in case 5 described in the second row from the top of Table 3, as described with reference to FIGS. 13 and 14, when handoff is performed in the visited domain, the SIP signaling address, the SIP media address The address of the non-SIP application changes.
As can be seen from Table 2, since the protocol for the mobile node and the home domain is common in Case 5 and Case 1, the columns of “Home Domain” and “Home Local Mobility” in Case 5 of Table 3 are as follows: The IP addresses before and after the handoff in case 1 are described.
In case 1, as described with reference to FIGS. 5 and 6, when handoff is performed in the home domain, the SIP signaling address, the SIP media address, and the non-SIP application address change.

Next, in the case 6 described in the third row from the top of Table 3, as described with reference to FIGS. 15 and 16, even if handoff is performed in the visited domain, the SIP signaling address, the SIP media The address for non-SIP applications does not change.
As can be seen from Table 2, since the protocol for the mobile node and the home domain is common in Case 6 and Case 1, the columns of “Home Domain” and “Home Local Mobility” in Case 6 of Table 3 are as follows: The IP addresses before and after the handoff in case 1 are described. This is as described above.

Next, in the case 7 described in the third row from the bottom of Table 3, as described with reference to FIGS. 17 and 18, even if handoff is performed in the visited domain, the SIP signaling address, the SIP media The address for non-SIP applications does not change.
As can be seen from Table 2, since the protocols for the mobile node and the home domain are common in Case 7 and Case 2, the columns of “Home Domain” and “Home Local Mobility” in Case 7 of Table 3 are as follows: The IP addresses before and after the handoff in case 2 are described.
In case 2, as described with reference to FIGS. 7 and 8, even if handoff is performed in the home domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change.

Next, in the case 8 described in the second row from the bottom of Table 3, as described with reference to FIGS. 19 and 20, even if handoff is performed in the visited domain, the SIP signaling address, the SIP media The address for non-SIP applications does not change.
As can be seen from Table 2, since the protocols for the mobile node and the home domain are common in Case 8 and Case 3, the columns of “Home Domain” and “Home Local Mobility” in Case 8 of Table 3 are as follows: The IP addresses before and after the handoff in case 3 are described.
In case 3, as described with reference to FIGS. 9 and 10, even if handoff is performed in the home domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change.

Next, case 9 described at the bottom of Table 3 is omitted from the description. However, even if handoff is performed in the visited domain, the SIP signaling address, the SIP media address, and the non-SIP application address do not change. .
As can be seen from Table 2, since the protocols for the mobile node and the home domain are common in Case 9 and Case 3, the columns of “Home Domain” and “Home Local Mobility” in Case 9 of Table 3 are as follows: The IP addresses before and after the handoff in case 3 are described. This is as described above.

The issues related to global mobility are as follows.
• There can be three types of global mobility.
This has been described with reference to FIGS.
-A protocol for transmitting a new bearer IP address is required.
-It can be SIP or CMIP in A-IMS.
-For MMD, it can be PMIP, but PMIP must support binding update to home agent in home domain.
In this case, it is necessary to have an appropriate security association between the PMIP in the visited domain and the home agent in the home network.

In addition, the subject regarding the movement between A-IMS and an IMD network is as follows.
Mobility infrastructure support may differ between A-IMS and IMD networks.
-MMD clients may not support CMIP.
-A-IMS client always needs CMIP stack on client.
-A solution is needed to help mobility between MMD domain and A-IMS domain.

Represents a roaming scenario. Represents visited global mobility. Represents visited global mobility. Represents visited global mobility. Represents home local mobility (case 1). This represents a sequence of case 1 (MN: simple IP, home domain: simple IP). Represents home local mobility (Case 2). This represents the sequence of case 2 (MN: simple IP, home domain: PMIP). Represents home local mobility (Case 3). The sequence of case 3 (MN: CMIP, home domain: PMIP) is shown. Represents home local mobility (case 4). This represents a sequence of case 4 (MN: CMIP, home domain: CMIP). Represents visited local mobility (case 5). This represents a sequence of case 5 (MN: simple IP, home domain: simple IP, visited domain: simple IP). Represents visited local mobility (case 6). This represents the sequence of case 6 (MN: simple IP, home domain: simple IP, visited domain: PMIP). Represents visited local mobility (case 7). This represents a sequence of case 7 (MN: simple IP, home domain: PMIP, visited domain: PMIP). Represents visited local mobility (case 8). This represents a sequence of case 8 (MN: CMIP, home domain: PMIP, visited domain: PMIP).

Explanation of symbols

HA home agent MN mobile node PDSN packet data serving node V-BM visited bearer manager

Claims (8)

An address acquisition means for acquiring a first address acquired by the packet data serving node from a home agent of the same domain after establishing a session with the packet data serving node;
Address generating means for generating second and third addresses using the first address prefix and the first and second interface IDs generated by the first address;
Address notifying means for notifying the packet data serving node of the generated second and third addresses;
Communication means for communicating using the first, second and third addresses as addresses for SIP signaling, SIP media and non-SIP applications, respectively;
Comprising
The address generating means, when establishing a session with another packet data serving node in the same domain by handoff, generates a second and third address using the same first and second interface IDs as before the handoff. After establishing a session with the mobile node, an address assigning unit that obtains a first address from a home agent in the same domain and assigns it to the mobile node;
Address registration means for registering the second and third addresses notified from the mobile node with the home agent of the same domain;
A packet data serving node comprising: Address holding means for holding the first address;
An address acquisition means for acquiring a second address acquired by the packet data serving node from a home agent of the same domain after establishing a session with the packet data serving node;
Address registration means for registering the acquired second address with a home agent of the same domain;
Address generating means for generating a third address using the prefix of the second address and the first interface ID generated by itself;
Address notification means for notifying the packet data serving node of the generated third address;
Communication means for communicating using the first, second and third addresses as addresses for SIP signaling, SIP media and non-SIP applications, respectively;
Comprising
The address generating means, when establishing a session with another packet data serving node in the same domain by handoff, generates a third address using the same first interface ID as before handoff. After establishing a session with the mobile node, an address assignment means for acquiring a second address from a home agent of the same domain and assigning the second address to the mobile node;
Address registration means for registering the third address notified from the mobile node with the home agent of the same domain;
A packet data serving node comprising: An address acquisition means for acquiring a first address acquired by the packet data serving node from a home agent of a home domain after establishing a session with the packet data serving node of the visited domain;
Address generating means for generating third and fourth addresses using the first address prefix and the first and second interface IDs generated by the first address;
Address notification means for notifying the packet data serving node of the generated third and fourth addresses;
Communication means for communicating using the first, third and fourth addresses as addresses for SIP signaling, SIP media and non-SIP applications, respectively;
Comprising
When the address generation means establishes a session with another packet data serving node in the visited domain by handoff, the address generation means generates the third and fourth addresses using the same first and second interface IDs as before the handoff. node. After establishing a session with a mobile node whose home domain is another domain, a second address is obtained from a home agent of the same domain, a first address is obtained from a home agent of the home domain of the mobile node, and the first Address assignment means for assigning one address to the mobile node;
Address registration means for registering the third and fourth addresses notified from the mobile node with the home agent of the same domain;
A packet data serving node comprising: Address holding means for holding the first address;
Address acquisition means for acquiring a second address acquired by the packet data serving node from a home agent of the visited domain after establishing a session with the packet data serving node of the visited domain;
Address registration means for registering the second address with a home agent of a home domain;
Address generating means for generating a third address using the prefix of the second address and the first interface ID generated by itself;
Address notification means for notifying the packet data serving node of the generated third address;
Communication means for communicating using the first, second and third addresses as addresses for SIP signaling, SIP media and non-SIP applications, respectively;
Comprising
When the address generation means establishes a session with another packet data serving node in the visited domain by handoff, the mobile node generates a third address using the same first interface ID as before handoff. After establishing a session with a mobile node having another domain as a home domain, an address assignment unit that acquires a second address from a home agent in the same domain and assigns the second address to the mobile node;
Address registration means for registering the third address notified from the mobile node with the home agent of the same domain;
A packet data serving node comprising:

Images