JP2008532359A - Method and apparatus for setting network address of mobile terminal in mobile communication system - Google Patents

Abstract

A method for setting a network address of a mobile terminal in a mobile communication system when a mobile terminal is handed over from one network to another network.
A unified interface to a higher layer of a mobile terminal is set up to manage messages to / from one or more of a homogeneous network and a heterogeneous network; The mobile terminal for handover of the mobile terminal to one or more of the homogeneous network and heterogeneous network and for communicating one or more of the homogeneous network and heterogeneous network to communicate data In order to set a network address, a request from the unified interface is received at the upper layer, and the network address for one or more of the same type network and the different type network is set.
[Selection] Figure 6

Description

  The present invention relates to setting a network address of a mobile terminal in a mobile communication system, and more specifically, setting a network address when a mobile terminal is handed over from one network to another. About.

  Currently, the IEEE 802.21 standard committee is conducting deep research on international standards related to media independent handover (MIH) between heterogeneous networks. In addition to providing seamless handover, MIH also provides service continuity between heterogeneous networks that provides greater convenience to users with mobile terminals. IEEE 802.21 defines various functions (i.e., MIH function, event service, command service, and information service (IS)) as basic requirements.

  A mobile terminal (MSS) refers to a multi-mode node that supports two or more interface types. For example, the multimode node may be a wired interface type (or a wired-line interface type) such as Ethernet (Ethernet) based on the IEEE 802.3 standard, or a wired-line interface type. 802. Such as wireless interface types based on XX standards (broadband wireless access network systems, wireless LANs, wired LANs and cellular system interfaces) and other interfaces defined by cellular standard mechanisms (eg 3GPP or 3GPP2) Can support various interfaces.

  A Media Independent Handover Function (MIHF) reference model is shown in FIG. In the figure, the MIHF structure for interaction with other hierarchies and remote MIHF is shown. In order for MIHF to provide asynchronous and synchronous services to lower and upper layers, service access points (Service Access Point; SAP) such as MIH_MGMT_SAP, MIH_SME_SAP, and MIH_SAP are defined together with primitives. MIH_MGMT_SAP defines the interface between the management plane (management entity) of MIHF and other network interfaces, and MIH protocol messages between MIHF and local link layer entities as well as peer MIHF entities. Used to communicate with. MIH_SAP defines interfaces between higher layer entities such as MIHF and device administrator, handover policy control function, transport, layer 3 (L3) mobility management protocol, etc. for MIH configuration and operation Used for.

  The MIH_SME_SAP defines an interface between the MIHF and a station management entity (Station Management Entity) or a network management system (Network Management System), and is used for MIG configuration and operation.

  FIG. 2 is a structural diagram illustrating a multimode mobile station. As shown in FIG. 2, each multi-mode mobile station includes a physical (PHY) layer and a medium access control (MAC) layer for separate modes, and mediator independent handover (under the IP layer). MIH) Hierarchy is located.

  Mediator-independent handover (MIH) must be defined between IEEE 802 series interfaces or defined between IEEE 802 series interfaces and non-802 series interfaces (eg, 3GPP and 3GPP2). In addition, protocols for supporting higher layer mobility such as mobile IP and Session Initiation Protocol (SIP) must be supported for handover function and service continuity. .

  The MIH function is located below the IP layer and uses the input values received from the second layer (layer 2) (i.e., trigger event and information related to other networks) to prompt the handover process. The MIH function can include multiple input values based on both user policies and configurations that affect the handover process. A general interface between a third tier (tier 3) entity such as Mobile IP, Session Initiation Protocol (SIP) and the MIH tier is defined. In this case, the interface described above provides the first layer (ie, physical layer), the second layer (ie, MAC layer), and mobility management information. The MIH function acquires information related to lower layers and networks using an event and information service (IS) function.

  The upper layer includes operations of various links belonging to an upper management entity and a mobile station for state monitoring (Monitoring), and performs a handover control function and a device administrator function. In this case, the handover control function and the device administrator may be located at other independent locations, or the handover control function and the device administrator may be included as an upper management entity in the upper layer. .

  A network structure for supporting mobile IP includes a home agent (HA), a foreign agent (FA), and a mobile subscriber station (MSS). Various functions such as an agent discovery function, a registration function, and a routing function are required for the operation of the mobile IP.

  The agent discovery function allows the mobile terminal to determine whether the mobile terminal is connected to its own home network or an external network so that it can recognize whether the mobile terminal has moved to another network. Represents how to do.

  According to the registration function, when the mobile terminal moves to another network, the registration function forwards the current location information to the home agent in such a way that the registration function provides a highly adaptable mechanism, and the mobile terminal has no change To receive services from the home network.

  The routing function is required to properly route datagrams transferred / received to / from the mobile terminal when the mobile terminal is connected to the external network or attempts to connect. Define functions.

  Mobile IP provides two registration procedures for setting a temporary address (temporary address or Care of Address (CoA)) when a mobile terminal moves to another subnet. For example, the two registration procedures are FA-CoA and co-located CoA.

  When the FA-CoA is used, the CoA is supplied from the foreign agent (FA) through an agent advertisement message, and the IP address of the foreign agent is used as a temporary address (CoA). When the co-located CoA is used, the mobile terminal receives a temporary address (CoA) through a dynamic host configuration protocol (DHCP) server located in the external network.

  DHCP refers to a protocol that allows network managers to centrally manage / assign IP addresses required in the networks included in their network organization. When a computer user acquires a connection to the Internet within the organization, an IP address must be assigned to each individual computer. When the network administrator centrally manages / assigns IP addresses and the computer is connected to the Internet from elsewhere outside the network, DHCP automatically transfers the new IP address.

  DHCP adopts a rental (or lease; hereinafter referred to as “lending”) method in which a given IP address is controlled to be valid on a corresponding computer only during a predetermined time period. To do. The lending time can be changed by the internet connection time required by the user at a specific location. DHCP can also reduce IP address lending time to dynamically reconfigure the network when more computers are used than available IP addresses.

  If the system begins to operate, multiple clients request unique IP addresses for those systems from the DHCP server. When each client receives its IP address from the DHCP server, a TCP / IP setup is initiated and the client communicates with other hosts using the TCP / IP protocol. The DHCP server responds to the DHCP client's IP address lending request to maintain / manage the range of assignable IP addresses (i.e., 203.224.29.10 to 203.224.29.100).

  Table 1 below shows the DHCP message format.

下記の表２には、ＤＨＣＰメッセージの様々なタイプと使用を示す。

Table 2 below shows the various types and uses of DHCP messages.

移動ＩＰｖ６システム動作のための主要な構成要素及び個々の主要な構成要素の機能を次に説明する。

The main components for mobile IPv6 system operation and the functions of the individual main components are now described.

  A mobile node (MN) is a host or a router for switching its network connection. Corresponding node (CN) is a host or router that communicates with a mobile node (MN). The home agent (HA) functions as a router and has mobile node registration information obtained from a router included in the home network. Therefore, the home agent (HA) can transfer the datagram to the current location of the mobile node (MN) included in the external network.

  The temporary address (CoA) represents an IP address connected to the mobile node when the mobile node moves to a foreign node or a foreign agent (FA). “Binding” refers to a specific operation in which the mobile node matches the home address of the corresponding node with the CoA registered in the home agent. “Binding Update (BU) message” refers to a message used when the mobile node itself notifies the home agent (HA) and the corresponding node (CN) of the CoA of the mobile node. The “Binding Acknowledge (BACK)” message represents a response message to the “BU” message described above. The “Binding Request (BR)” message requests the “BU” message when the corresponding node (CN) fails to receive the “BU” message when the timer for the binding information of the mobile node expires. It is a message to do.

  The mobile node (MN) automatically configures location information using a moving neighbor discovery function and an address automatic configuration function. When the corresponding node (CN) saves the binding information, the corresponding node directly communicates with the mobile node through the home agent without passing through in the same manner as router optimization (Router Optimization) is performed.

  An IP address autoconfiguration method is a state-storage-type address autoconfiguration method for acquiring an address using a server such as a DHCP server, and for controlling a host so that a mobile node can generate an address by itself. There are two types of address autoconfiguration methods such as non-state-type address autoconfiguration methods.

  The state-storage-type address automatic configuration method assigns one of a plurality of addresses that can be assigned from the server to the host under the condition that the host requests an address from the DHCP server. The non-state-type address autoconfiguration method combines the mobile node's interface ID information with prefix information obtained from a router or well-known prefix information so that the mobile node forms an address.

  DHCPv6 represents the DHCP protocol for IPv6 systems and supports state-storage-type address autoconfiguration methods. DHCPv6 concentrates on a small number of DHCP servers with IP address, various information (ie, routing information) and network resource management functions, and shows a special mechanism that leads to reduction of storage cost.

  DHCPv6 adopts two multicast addresses such as “All_DHCP_Relay_Agents_and_Servers” address and “All_DHCP_Servers” address.

  The “All_DHCP_Relay_Agents_and_Servers” address represents a link local multicast address used by the client so that the client communicates with the agent belonging to the link on the condition that the link local address of the agent is not known. In this case, all services and agents act as members of the above multicast group.

  The “All_DHCP_Servers” address is used by the client or relay when the client or relay cannot forward the message to all servers or recognize the server's unicast address so that the client or relay can communicate with the server. Represents a site local multicast address. In order for the client to use the “All_DHCP_Servers” address described above, the client must have a range of addresses sufficient for the server to arrive. In this case, all servers in the site act as members of the multicast group described above.

  For example, various messages such as “SOLICIT” message, “ADVERTISE” message, “REQUEST” message, “REPLY” message, “RENEW” message and “RELEASE” message are used for basic operation of DHCPv6. be able to.

  The “SOLICIT” message is adjusted so that the client recognizes the location information of the server and is multitasked by the “All_DHCP_Servers” address. The “ADVERTISE” message represents a response message to the “SOLICIT” message. As much as possible, the DHCP server responds to a “SOLICIT” message. The “REQUEST” message is configured to obtain a configuration parameter with an IP address from the server selected by the client and multitasked with the “All_DHCP_Relay_Agents_and_Servers” address. The “REPLY” message represents a response message to the above-described “REQUEST”, “RENEW”, and “RELEASE” messages. The “RENEW” message represents a message that is requested when the client acquires the lifetime of the initially assigned client address and configuration parameters. The “RELEASE” message represents a message requested when the client returns one or more IP addresses to the server.

  FIG. 3 shows the MIH structure and transfer protocol. A heterogeneous network and handover technique will be described with reference to FIG. As shown in FIG. 3, the MIH function is located below the IP layer and uses the input value received from the second layer (Layer 2) (that is, a trigger event and information related to another network). Promote overprocessing.

  The MIH function can include multiple input values based on both user policy and configuration that can affect the handover process. A general interface between a third layer (Layer 3) entity such as Mobile IP, Session Initiation Protocol (SIP), and the MIH layer is defined. In this case, the interface described above provides the first layer (ie, physical layer), the second layer (ie, MAC layer), and mobility management information. The MIH function acquires information related to lower layers and networks using an event and information service (IS) function. Therefore, the upper layer must include an MIH function for supervising / controlling the state of various included links. The dotted lines in FIG. 3 indicate, for example, primitive information and event triggers.

  FIG. 4 is a diagram showing an event trigger. In order to perform the handover function quickly, the network layer must use information generated from the link layer so that the network layer quickly resets the connection state. Link hierarchy events are designed to anticipate user movement, helping mobile terminals and networks to provide handover functions.

  As shown in FIG. 4, a trigger for handover can be initiated from a physical (PHY) layer and a MAC layer. The trigger source can be determined to be a local stack or a remote stack. The event trigger provides current signal status information, other network status change information, and future predicted change information. The event trigger also includes physical and MAC layer change information or specific network attribute change information.

  The event types can be classified into, for example, a physical (PHY) layer event, a MAC layer event, a management event, a third layer (L3) event, and an application event.

  FIG. 5 shows triggers that are generated until the link setup process from the currently connected link to the new link is performed. Basic trigger events (ie, “Link_Up” event, “Link_Down” event, “Link_Going_Down” event, “Link_Going_Up” event, “Link_Event_Rollback” event, “Link_Available” event, “Link_Harm” event, “Link_Available” event, The IP_Renewal_Request "event) is described below with reference to FIG.

  The “Link_Up” event occurs when the second layer (L2) connection is set on a specific link interface and the upper layer can transfer the third layer (L3) packet. In this case, it is determined that all L2 layers included in the link are completely configured. The source of the “Link_Up” event corresponds to “local MAC” and “remote MAC”. Table 3 below shows the parameters of the “Link_Up” event.

“Ｌｉｎｋ＿Ｄｏｗｎ”イベントは、Ｌ２接続が特定のインターフェース上で解除され、Ｌ３パケットがあて先に転送されない時に発生する。“Ｌｉｎｋ＿Ｄｏｗｎ”イベントのソース（ｓｏｕｒｃｅ）は、ローカルＭＡＣを表す。下記の表４は、“Ｌｉｎｋ＿Ｄｏｗｎ”イベントのパラメータを示す。

The “Link_Down” event occurs when the L2 connection is released on a specific interface and the L3 packet is not forwarded to the destination. The source of the “Link_Down” event represents the local MAC. Table 4 below shows the parameters of the “Link_Down” event.

“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｄｏｗｎ”イベントは、Ｌ２接続が予め定められた時間内に“Ｌｉｎｋ＿Ｄｏｗｎ”状態に入ると予想される時に発生し、ハンドオーバープロセスを初期化するための信号としての役割を果たすことができる。“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｄｏｗｎ”のソースは、“Ｌｏｃａｌ ＭＡＣ”及び“Ｒｅｍｏｔｅ ＭＡＣ”に該当する。下記の表５に、“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｄｏｗｎ”イベントのパラメータを示す。

A “Link_Going_Down” event occurs when an L2 connection is expected to enter a “Link_Down” state within a predetermined time, and may serve as a signal to initialize the handover process. The source of “Link_Going_Down” corresponds to “Local MAC” and “Remote MAC”. Table 5 below shows parameters of the “Link_Going_Down” event.

“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｕｐ”イベントは、予め定められた時間内でＬ２接続が“Ｌｉｎｋ＿Ｕｐ”状態に進入すると予想される時に発生し、長い周期の時間が網を初期化するのに消費される時に用いられる。“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｕｐ”イベントのソースは、“Ｌｏｃａｌ ＭＡＣ”及び“Ｒｅｍｏｔｅ ＭＡＣ”に該当する。下記の表６は、“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｕｐ”イベントのパラメータを示す。

The “Link_Going_Up” event occurs when an L2 connection is expected to enter the “Link_Up” state within a predetermined time, and is used when a long period of time is consumed to initialize the network. The source of the “Link_Going_Up” event corresponds to “Local MAC” and “Remote MAC”. Table 6 below shows parameters of the “Link_Going_Up” event.

“Ｌｉｎｋ＿Ｅｖｅｎｔ＿Ｒｏｌｌｂａｃｋ”イベントは、“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｄｏｗｎ”イベントと“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｕｐ”イベントとを結合することによって形成される。“Ｌｉｎｋ＿Ｅｖｅｎｔ＿Ｒｏｌｌｂａｃｋ”イベントは、“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｕｐ”イベントまたは“Ｌｉｎｋ＿Ｇｏｉｎｇ＿Ｄｏｗｎ”イベントがあて先に転送される条件で、特定の時間内で“Ｌｉｎｋ＿ＵＰ”イベントまたは“Ｌｉｎｋ＿Ｄｏｗｎ”イベントがそれ以上生成されないと予想される時に生成されるトリガーを表す。“Ｌｉｎｋ＿Ｅｖｅｎｔ＿Ｒｏｌｌｂａｃｋ”イベントのソースは、“Ｌｏｃａｌ ＭＡＣ”及び“Ｒｅｍｏｔｅ ＭＡＣ”に該当する。下記の表７に、“Ｌｉｎｋ＿Ｅｖｅｎｔ＿Ｒｏｌｌｂａｃｋ”イベントのパラメータを示す。

The “Link_Event_Rollback” event is formed by combining the “Link_Going_Down” event and the “Link_Going_Up” event. The “Link_Event_Rollback” event is generated when the “Link_Going_Up” event or the “Link_Going_Down” event is forwarded to the destination, and no more “Link_UP” or “Link_Down” events are expected to be generated within a specific time period. Represents a trigger. The source of the “Link_Event_Rollback” event corresponds to “Local MAC” and “Remote MAC”. Table 7 below shows parameters of the “Link_Event_Rollback” event.

“Ｌｉｎｋ＿Ａｖａｉｌａｂｌｅ”イベントは、新しい特定リンクの利用可能な状態を表し、新しい基地局（ＢＳ）または新しい接続点（Ｐｏｉｎｔ ｏｆ Ａｔｔａｃｈｍｅｎｔ；ＰＯＡ）が、現在移動端末の接続された現在ＢＳまたは現在ＰＯＡに比べて品質上より優れたリンクを提供するようにする可能性を表す。“Ｌｉｎｋ＿Ａｖａｉｌａｂｌｅ”イベントのソースは、“Ｌｏｃａｌ ＭＡＣ”及び“Ｒｅｍｏｔｅ ＭＡＣ”に該当する。下記の表８に、“Ｌｉｎｋ＿Ａｖａｉｌａｂｌｅ”イベントのパラメータを示す。

The “Link_Available” event represents the availability of a new specific link, where a new base station (BS) or a new point of attachment (POA) is compared to the current BS or current POA to which the current mobile terminal is connected. Represent the possibility of providing better quality links. The source of the “Link_Available” event corresponds to “Local MAC” and “Remote MAC”. Table 8 below shows parameters of the “Link_Available” event.

“Ｌｉｎｋ＿Ｐａｒａｍｅｔｅｒ＿Ｃｈａｎｇｅ”イベントは、リンクパラメータ値の変化が特定臨界レベルよりも高い時に生成されるイベントのことを表す。“Ｌｉｎｋ＿Ｐａｒａｍｅｔｅｒ＿Ｃｈａｎｇｅ”イベントは、例えば、リンク速度（すなわち、リンクレート（ｒａｔｅ））、ＱｏＳ（サービス品質）及び暗号化された値などリンク階層パラメータを含む。“Ｌｉｎｋ＿Ｐａｒａｍｅｔｅｒ＿Ｃｈａｎｇｅ”イベントのソースは、“Ｌｏｃａｌ ＭＡＣ”及び“Ｒｅｍｏｔｅ ＭＡＣ”に該当する。下記の表９に、“Ｌｉｎｋ＿Ｐａｒａｍｅｔｅｒ＿Ｃｈａｎｇｅ”イベントのパラメータを示す。

The “Link_Parameter_Change” event represents an event that is generated when the change of the link parameter value is higher than a specific critical level. The “Link_Parameter_Change” event includes, for example, link hierarchy parameters such as link speed (ie, link rate), QoS (quality of service), and encrypted values. The source of the “Link_Parameter_Change” event corresponds to “Local MAC” and “Remote MAC”. Table 9 below shows parameters of the “Link_Parameter_Change” event.

情報サービス（Ｉｎｆｏｒｍａｔｉｏｎ Ｓｅｒｖｉｃｅ；ＩＳ）は、網発見及び網選択の両方のために要請される網と関連した詳細な情報を提供し、他の網のユーザによって自由に接続可能なように設計されなければならない。情報サービスは、例えば、リンク接続パラメータ、保安メカニズム、近隣（ｎｅｉｇｈｂｏｒｈｏｏｄ）マップ、位置、サービスプロバイダを示す情報及び他の接続情報のような様々な情報構成要素及びリンク費用（すなわち、ｃｏｓｔ ｏｆ ｌｉｎｋ）を含まなければならない。

Information Services (IS) provide detailed information related to the network required for both network discovery and network selection, and should be designed to be freely connectable by users of other networks. I must. An information service includes various information components and link costs (ie, cost of link) such as, for example, link connection parameters, security mechanisms, neighbor map, location, service provider information and other connection information. Must be included.

  FIG. 6 is a structural diagram showing a “Link Event” model and an “MIH Event” model. As shown in FIG. 6, the MIH event represents an event transferred from the MIH to an upper manager entity or an upper layer, and corresponds to an existing event trigger. The link event represents an event transferred from a lower layer (that is, a MAC layer or a physical (PHY) layer) to the MIH, and uses a primitive for use in an individual interface MAC or a physical layer.

  FIG. 7 is a structural diagram showing a “Remote Link Event” model. As shown in FIG. 7, when a lower layer (MAC or PHY) included in the local stack generates a link event and forwards the link event to the MIH included in the local stack, the MIH of the local stack Forward the link event to the stack's MIH.

  FIG. 8 is a structural diagram showing the “Remote MIH Event” model. As shown in FIG. 8, the local stack MIH function generates a remote MIH event and forwards the remote MIH event to a counterpart MIH function included in the remote stack. The MIH function of the remote stack forwards the received event to a higher management entity or higher layer included in the remote stack. Similarly, the MIH function of the remote stack generates an event to the MIH function of the local stack, and the MIH function of the local stack forwards the aforementioned event to the upper layer of the local stack.

  FIG. 9 is a structural diagram showing the “MIH command” model and the “Link Command” model. As shown in FIG. 9, an MIH command (MIH command) is generated from an upper management entity or an upper layer so as to instruct the MIH to perform a specific work, and is subsequently transferred to the MIH function. The link command (command) is generated from the MIH function so as to instruct the lower layer to perform a specific work, and is subsequently transferred to the lower layer.

  FIG. 10 is a structural diagram showing the “Remote MIH command” model. As shown in FIG. 10, a remote MIH command (remote MIH command) is generated from an upper management entity or an upper layer, and thereafter transferred to the MIH function. The MIH function transfers the received MIH command to the corresponding MIH function included in the remote stack. Similarly, an upper layer included in the remote stack generates an instruction and transfers the instruction to the MIH function of the remote stack, and the MIH function of the remote stack transfers the instruction to the MIH function of the local stack.

  FIG. 11 is a structural diagram showing a “Remote Link Command” model. As shown in FIG. 11, the MIH function included in the local stack generates a remote link command and transfers the remote link command to the corresponding MIH function included in the remote stack.

  The MIH function included in the remote stack transfers the remote link command to the lower layer included in the remote stack. Similarly, the MIH function included in the remote stack generates an instruction and transfers the instruction to the MIH function of the local stack, and the MIH function of the local stack transfers the instruction to a lower layer of the local stack.

  FIG. 12 is a diagram illustrating the operation of the mobile IPv4 system. As shown in FIG. 12, Mobile IPv4 has various functions (ie, a mobile host function, a home agent (HA) function, and a foreign agent (FA) function) so as to provide a clear mobility to an upper layer. ) In addition.

  However, if the router or route is not optimized, the corresponding node communicating with the mobile terminal does not need to be changed to another. In this case, the mobile host indicates an IP host whose mobility is supported. The home agent serves as a router for maintaining location information related to the mobile host and performing tunneling of the mobile host. The external agent indicates a router for supporting mobility in the external network.

  Next, the operation of the Gene Mobile IPv4 system shown in FIG. 12 will be described. As shown in FIG. 12, the mobile host moves from its home network to the external network in step S111. Thereafter, the mobile host receives an advertisement message currently broadcast from the external network to recognize that the mobile host has moved. Thereafter, in step S112, the mobile host registers a temporary address (temporary address or Care of Address (CoA)) indicating the current location of the mobile host in the home agent (HA) of the home network.

  In this case, the temporary address (CoA) may be the same as the IP address of the foreign agent (ie, the foreign agent (FA) -CoA) or the same as the co-located CoA. It is temporarily allocated to the mobile host via DHCP.

  Packets transferred from the external part to the mobile host are transferred to the home network. In step S113, these packets are intercepted by the home agent that recognizes the movement of the mobile terminal. The home agent that intercepts these packets sets the destination address of the packet transferred to the mobile host under the condition that FA-CoA is used as the address of the foreign agent (FA), and sets the destination address representing the FA address. Encapsulation is performed, and the encapsulated address is transferred in step S114.

  These encapsulated transfer packets are then transferred to the foreign agent (FA). Thereafter, the foreign agent (FA) de-capsulates the received packet to restore it to the original packet, and finally transfers the original packet to the mobile host in step S115.

  It should be noted that packets transferred from a mobile host to a corresponding host can be transferred directly via a foreign agent (FA). When an ingress filtering problem occurs, the above packet can also be forwarded via a reverse tunnel.

  The main functions required for Mobile IP are, for example, an agent discovery function, a registration function, and a routing function, which will be described in detail below.

  Agent discovery refers to a method of determining whether a mobile terminal is connected to its home network or an external network so that the mobile terminal can recognize whether or not it has moved to another network.

  Mobile IP extends the existing Internet Control Message Protocol (ICMP) router discovery (ie, IETF RFC 1256) to discover the desired agent. An agent advertisement message periodically broadcast by an agent (ie, home agent and foreign agent) includes a “Mobility Agent Advertisement Extension” message in an “ICMP Router Advertisement” message. And forward an "ICMP router advertisement" message containing a "mobility agent advertisement extension" message. The “Agent Solicitation” message transferred when the mobile terminal searches for an agent employs the same method as the existing “ICMP Router Solicitation” message.

  When the mobile terminal moves to another network, the registration function transfers the current location information to the home agent so that the mobile terminal can receive service from the home network without any change.

  Mobile IP provides two registration procedures, eg, FA-CoA and co-located CoA. When the mobile terminal uses FA-CoA, the mobile terminal performs registration via a foreign agent (FA). When the mobile terminal uses co-located CoA, the mobile terminal directly registers with the home agent.

  The routing function performs various functions required to properly route datagrams transferred / received to / from the mobile terminal when the mobile terminal connects to or approaches the external network. Define. The datagram includes a unicast packet, a multicast packet, and a broadcast packet.

  Next, the DHCP operation will be described. In order for DHCP to operate correctly, one or more DHCP servers and a single DHCP client must be included in the corresponding network. In addition to the TCP / IP address range, the network must further include a gateway address and subnet mask. The DHCP client obtains TCP / IP address information from the DHCP server during operation.

  However, it should be noted that the acquired TCP / IP address is not permanent. The DHCP server provides the client with a lease address that can be periodically expired or periodically updated.

  Multiple client DHCP states: an initialization state (INT), a selection state (SELECTING), a requesting state (requesting state; REQUESTING), a binding state (BOUND), and an updating state (renewing state) RENEWING) and rebinding state (REBINDING). The DHCP client obtains / maintains the lending address through a plurality of handshake stages, each stage being called a state.

  FIG. 13 is a flowchart showing the operation of the DHCP client-server model, and shows a method for allowing a DHCP client to automatically receive an IP address from a DHCP server. As shown in FIG. 13, in step S121, the client broadcasts a “DHCPDISCOVER” packet to the peripheral servers. When each server receives a “DHCPDISCOVER” packet from the client, in response to the received “DHCPDISCOVER” packet, a “DHCPOFFER” packet is transferred as a response signal in step S122.

  The client receives a “DHCPOFFER” packet from one or more servers in step S122, selects one of the servers that request configuration parameters, and broadcasts a “DHCPREQUEST” packet in step S123. In this case, servers not selected by the “DHCPREQUEST” packet recognize that the client has refused to provide these servers.

  The server selected by the “DHCPREQUEST” packet includes the address configuration information in the “DHCPACK” packet, and transfers the “DHCPACK” packet to the client as a response signal in step S124 together with the address configuration information. When the client receives a “DHCPACK” packet from the selected server, it constructs an address (construct). However, when the client receives a “DHCPPAK” packet, the client restarts the process described above. In addition, the client can transfer a “DHC PRELEASE” packet to the server in order to return the address lent in step S125.

  FIG. 14 is a flowchart showing the operation of the mobile IPv6 system. As shown in FIG. 14, when a mobile node (MN) moves from subnet A to another subnet B in phase 0, the mobile node (MN) in FIG. 1 prefixes router information (RA) message with prefix information and NUD. It recognizes that the mobile node (MN) has moved to another subnet B using the (Neighbor Unreachable Detection) mechanism.

  In step 2, the mobile node (MN) acquires a temporary address (CoA) by itself using the address automatic configuration method described above. Thereafter, in step 3, the mobile node (MN) forwards a binding update (BU) message so that the home agent recognizes the acquired CoA.

  Upon receiving the “BU” message, the home agent (HA) binds (or binds) the mobile node's home address with the temporary address (CoA), and in step 4, the “BACK” message is used as a response signal to the “BU” message. Forward.

  The corresponding node (CN) that communicates with the mobile node (MN) for the first time does not recognize that the mobile node has moved to another subnet so that the destination address is set as the home address of the mobile node (MN). The result packet is transferred to the home agent (HA).

  Thereafter, the home agent for managing the mobile node (MN) intercepts the packet of the corresponding node (CN), and performs tunneling of the packet to the current position of the mobile node in step 6. When the mobile node receives the tunneled packet, it determines that the corresponding node (CN) that forwarded the packet does not have binding information, and in step 7, the corresponding node (CN) moves to the mobile node (MN). The “BU” message is transferred to the corresponding node (CN).

  The corresponding node (CN) that has received the CoA of the mobile node stores the binding information and directly communicates with the mobile node (MN) using the binding information in step 8.

  FIG. 15 is a flowchart showing the operation of DHCPv6. As shown in FIG. 15, the client transfers the “SOLICIT” message to the “All_DHCP_Servers” address in step (1) to recognize the server location information. Thereafter, each DHCPv6 server outputs an “ADVERTISE” message including prefix information as a response to the “SOLICIT” message in step (2).

  Thereafter, the client selects one of the DHCPv6 servers, transfers a “REQUEST” message to the selected server, and simultaneously requests additional configuration parameters in step (3). Thereafter, the selected DHCPv6 server outputs a “REPLY” message in response to the “REQUEST” message in step (4).

  The client receiving the “REPLY” message forwards the “RENEW” message to the DHCPv6 server to update the existing configuration parameters and the lifetime of the assigned address, and starts the T1 timer operation in step (5). . Here, the reference symbol “T1” indicates a specific time for the client to connect to the server from which the old address was acquired in order to increase the lifetime of the current address.

  Thereafter, the DHCPv6 server transfers another “REPLY” message as a response signal of the “RENEW” message in step (6). Finally, in step (7), the client outputs a “RELEASE” message when the assigned address is no longer used so that the corresponding address is released.

  FIG. 16 is a flowchart illustrating a temporary address (CoA) re-setup procedure when a multi-mode mobile terminal is handed over from one interface network to another interface network. A multi-mode mobile terminal can use a mobile IPv4 system or a mobile IPv6 system to perform mobility management. Mobile IPv4 can use FA-CoA or co-located CoA as a temporary address (CoA). Mobile IPv6 can use a state-store-type address or a non-state-store-type address as a temporary address (CoA).

  A method for resetting the temporary address (CoA) when the multi-mode mobile terminal is handed over to another interface network will be described below with reference to FIG. First, the mobile terminal sets the link and connection status of the current interface network. When a high quality link is detected from the MAC layer of the new interface network, the mobile terminal forwards a “Link_Available” trigger signal to the MIH function.

  The new MAC layer sets a new point of attachment (POA) and connection state. When the new MAC layer sets the connection state with the new POA, the new MAC layer performs an authentication process to inform the MIH function of the mobile terminal and the MIH function of the new POA that it is in the link setup state. The mobile terminal periodically receives the “Agent Advertisement” message of the foreign agent so as to recognize that the subnet has been changed to another subnet. The mobile terminal registers a temporary address (FA-CoA) in the home agent (HA).

  If a multi-mode mobile terminal is handed over from one subnet to another subnet in the currently connected interface network, or if it is handed over to another interface network and the subnet address is changed to another address, the mobile terminal Must perform an IP temporary address (CoA) re-setup procedure. However, the multi-mode mobile terminal according to the prior art is designed to set the IP temporary address (CoA) resetting procedure described above using only network layer information. Therefore, the time delay increases as the address is reset.

  The present invention relates to setting a network address of a mobile terminal when the mobile terminal is handed over from one network to another.

  Additional features and advantages of the invention will be developed in the description that follows, and in part will be apparent from the description, or may be learned from the practice of the invention. The objectives and other advantages of the invention may be realized and obtained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

  To achieve the above objects and other advantages of the present invention as embodied and broadly described in this document, in one embodiment of the present invention, a method for setting a network address of a mobile terminal in a mobile communication system. Configuring a unified interface to the upper layer of the mobile terminal to manage messages to / from one or more of a homogeneous network and a heterogeneous network; Performing handover of the mobile terminal to one or more of the homogeneous network and heterogeneous network, and for one or more of the homogeneous network and heterogeneous network to communicate data Receiving a request from the unified interface at the higher layer to set a network address of the mobile terminal; and And setting the network address for one or more of the species of the network, and configured to include.

  Preferably, the network address is an Internet Protocol (IP) address. Preferably, the step of receiving a request in the upper layer occurs when a subnet of the mobile terminal is changed. Preferably, the step of performing a handover includes performing a handover from a medium access control layer of a current network to one or more medium access control layers of the same type network and different types of networks. Preferably, the homogeneous network is the current network.

  In one aspect of the present invention, the setting method indicates whether to set the network address of the mobile terminal for one or more of the homogeneous network and the heterogeneous network to communicate data. The method further includes receiving an indication from one or more of the same type network and the different type network in the medium access control layer of the mobile terminal.

  In another aspect of the present invention, the setting method determines whether to set the network address of the mobile terminal for one or more of the homogeneous network and the heterogeneous network to communicate data. The method further includes transferring an indicator from the medium access control layer of the mobile terminal to the unified interface for instructing.

  Preferably, the unified interface determines whether to set the network address of the mobile terminal for one or more of the homogeneous network and the heterogeneous network to communicate data. . Preferably, the upper layer includes one or more of a mobility management protocol and an upper management entity.

  In still another aspect of the present invention, the setting method sets the network address for one or more of the same type network and the different type network in the unified interface from the upper layer. It further includes the step of informing (IP_linksetup_complete).

  Preferably, the unified interface is a media independent handover (MIH) function. According to another embodiment of the present invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes one of the homogeneous network and the heterogeneous network. Requesting the IP address from one or more foreign agents; receiving the IP address from the foreign agent; and home the IP address for one or more of the same type network and the different type network. Registering with the home agent of the network. Preferably, the IP address is a temporary address (CoA).

  According to another embodiment of the present invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes one of the homogeneous network and the heterogeneous network. Discovering and selecting one or more dynamic host configuration protocol (DHCP) servers; and specifying the IP address for one or more of the homogeneous network and the heterogeneous network to the DHCP server Requesting from the DHCP server, receiving the IP address from the DHCP server, and registering the IP address with a home agent of a home network. Preferably, the IP address is a temporary address (CoA).

  According to another embodiment of the present invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes one of the homogeneous network and the heterogeneous network. Requesting prefix information associated with the configuration of the IP address for one or more of the homogeneous network and heterogeneous network to one or more connecting routers; and the prefix information from the connecting router. , Receiving the prefix information to configure the IP address, and registering the IP address with a home network home agent. Preferably, the IP address is a temporary address (CoA).

  According to another embodiment of the present invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes one of the homogeneous network and the heterogeneous network. Discovering and selecting one or more dynamic host configuration protocol v6 (DHCPv6) servers, and requesting from the DHCPv6 server the IP address for one or more of the same and different networks. And receiving the IP address from the DHCPv6 server, and registering the IP address with a home agent of a home network. The IP address is a temporary address (CoA).

  According to another embodiment of the present invention, the step of receiving in the upper layer a request for setting the network address of the mobile terminal from the unified interface occurs before performing a handover. .

  According to one aspect of the present invention, the setting method determines whether to set the network address of the mobile terminal for one or more of the homogeneous network and heterogeneous network to communicate data. And receiving an indication representing the current network from the current network within the medium access control layer of the mobile terminal.

  According to another aspect of the present invention, the setting method further includes setting a connection with one or more of the same type network and the different type network. Preferably, the step of setting the connection includes the step of setting a connection between the medium access control layer of the mobile terminal and one or more medium access control layers of the same type network and different types of networks.

  Preferably, the network address is an Internet Protocol (IP) address. Preferably, the step of receiving a request for setting a network address of the mobile terminal from the unified interface in the upper layer occurs when the subnet of the mobile terminal is changed. Preferably, the step of performing a handover includes performing a handover from a medium access control layer of a current network to one or more medium access control layers of the same type network and different types of networks.

  In still another aspect of the present invention, the setting method determines whether to set the network address of the mobile terminal for one or more of the same type network and the different type network to communicate data. Further including the step of transferring an indicator for instructing to the unified interface from the medium access control layer of the mobile terminal.

  More preferably, the unified interface determines whether to set the network address of the mobile terminal for one or more of the homogeneous network and the heterogeneous network to communicate data. To do. Preferably, the upper layer includes at least one of a mobility management protocol and an upper management entity.

  According to another aspect of the present invention, in the setting method, the network address for one or more of the same type network and the different type network is set from the upper layer to the unified interface. It further includes a step of informing the user.

  Preferably, the unified interface is a mediator independent handover (MIH) function.

  According to one aspect of the invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes the one or more of the homogeneous network and the heterogeneous network. Requesting the IP address from the foreign agent, receiving the IP address from the foreign agent, and obtaining the IP address for one or more of the same type network and the different type network. Registering with the home agent. The IP address is a temporary address (CoA).

  According to another aspect of the present invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes one of the homogeneous network and the heterogeneous network. Discovering and selecting the above dynamic host configuration protocol (DHCP) server, and obtaining the IP address for one or more of the same type network and the different type network from the DHCP server Requesting, receiving the IP address from the DHCP server, and registering the IP address with a home agent of a home network. The IP address is a temporary address (CoA).

  According to still another aspect of the present invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes one of the homogeneous network and the heterogeneous network. Requesting one or more connecting routers for prefix information associated with the configuration of the IP address for one or more of the same type network and different types of networks, and receiving the prefix information from the connected routers And configuring the IP address using the received prefix information, and registering the IP address with a home agent of a home network. Preferably, the IP address is a temporary address (CoA).

According to still another aspect of the present invention, the step of setting the IP address for one or more of the homogeneous network and the heterogeneous network includes one of the homogeneous network and the heterogeneous network. Discovering and selecting one or more dynamic host configuration protocol v6 (DHCPv6) servers, and requesting from the DHCPv6 server the IP address for one or more of the same and different networks. Receiving the IP address from the DHCPv6 server; registering the IP address with a home agent of a home network;
including. Preferably, the IP address is a temporary address (CoA).

  According to another embodiment of the present invention, a mobile terminal capable of setting a network address in a mobile communication system is a message to / from one or more of the upper layer of the mobile terminal, the same type network, and a different type network. A single interface for managing data, means for handing over the mobile terminal to one or more of the same type of network and different types of network, and the same type of network and different types of data for communicating data Means for receiving a request for setting a network address of the mobile terminal for one or more of the networks from the unified interface in the upper layer, the same type network, and the different type network Means for setting the network address for one or more of the devices.

  It is to be understood that both the foregoing general description of the invention and the following detailed description are exemplary and explanatory, and additional description of the invention may be provided as claimed. it is obvious.

  The present invention can be applied to a broadband wireless access system.

  The present invention relates to setting a network address of a mobile terminal when the mobile terminal is handed over from one network to another in a mobile communication system.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the drawings, the same components are denoted by the same reference numerals as much as possible.

  The invention is described below in connection with the standard IEEE 802.21. The event service and command service associated with the IP address re-setup procedure of the present invention will be described below.

  A new point of attachment (POA) of a mobile terminal such as a base station has received a “Link_Up” trigger signal and the IP address used to forward the IP packet to the mobile terminal has changed or not changed Trigger “IP_Renewal_Indication” to inform the state. Preferably, the IP address is set to a newly assigned IP address in the case of a DHCP system. Alternatively, the IP address is assigned to a new temporary address (CoA) in the case of a mobile IPv4 system. In the case of a mobile IPv6 system, the IP address is set to an automatic configuration address. The source of the “IP_Renewal_Indication” event corresponds to “Remote MAC” and “MIH”.

  The mobile terminal's previous POA (ie, base station) is used to communicate with the new POA that the mobile terminal arrives to obtain information associated with the mobile terminal's IP address and forward the IP packet to the mobile terminal. Trigger an “IP_Renewal_Indication” event to inform the mobile terminal of the IP address change or non-change state and the triggered event. Preferably, the IP address is set to a newly assigned IP address in the case of a DHCP system, a new temporary address (CoA) in the case of a Mobile IPv4 system, and an auto-configured address in the case of a Mobile IPv6 system. Set to

  Table 10 below shows parameters of the “IP_Renewal_Indication” event.

アドレス再設定状態を示す“ＩＰ＿Ｒｅｎｅｗａｌ＿Ｉｎｄｉｃａｔｉｏｎ”トリガー信号を受信すると、移動端末のＭＩＨ機能は、“ＩＰ＿Ｒｅｎｅｗａｌ＿ＲｅｑｕｅｓｔＭＩＨ”イベントを、上位管理エンティティにＩＰ臨時アドレス（ＣｏＡ）を再設定するよう命令するために、移動性管理エンティティを含む上位管理エンティティに転送する。ＭＩＨ機能が上位管理エンティティに“ＩＰ＿Ｒｅｎｅｗａｌ＿Ｉｎｄｉｃａｔｉｏｎ”イベントを転送すると、“ＩＰ＿Ｒｅｎｅｗａｌ＿Ｉｎｄｉｃａｔｉｏｎ”イベントは、“ＩＰ＿Ｒｅｎｅｗａｌ＿Ｒｅｑｕｅｓｔ ＭＩＨ”イベントのメッセージフォーマットと同一のメッセージフォーマットを持つ。“ＩＰ＿Ｒｅｎｅｗａｌ＿Ｉｎｄｉｃａｔｉｏｎ”イベントのソースは、ローカルＭＡＣ（Ｌｏｃａｌ ＭＡＣ）階層及びＭＩＨに該当する。

Upon receiving the “IP_Renewal_Indication” trigger signal indicating the address reset state, the MIH function of the mobile terminal moves the “IP_Renewal_RequestMIH” event to instruct the higher management entity to reset the IP temporary address (CoA). Transfer to higher level management entity including management entity. When the MIH function transfers the “IP_Renewal_Indication” event to the upper management entity, the “IP_Renewal_Indication” event has the same message format as the message format of the “IP_Renewal_Request MIH” event. The source of the “IP_Renewal_Indication” event corresponds to a local MAC (Local MAC) layer and MIH.

  Table 11 below shows parameters of the “IP_Renewal_Request” event.

上位管理エンティティがＭＩＨ機能から“ＩＰ＿Ｒｅｎｅｗａｌ＿Ｒｅｑｕｅｓｔ”イベントを受信すると、ＩＰＣｏＡ再設定手順を完了した後に“ＩＰ＿Ｌｉｎｋｓｅｔｕｐ＿Ｃｏｍｐｌｅｔｅ”イベントをＭＩＨ機能に転送する。“ＩＰ＿Ｌｉｎｋｓｅｔｕｐ＿Ｃｏｍｐｌｅｔｅ”イベントのソースは、遠隔ＭＡＣ階層に該当する。下記の表１２に、“ＩＰ＿ＬｉｎｋＳｅｔｕｐ＿Ｃｏｍｐｌｅｔｅ”イベントのパラメータを示す。

When the upper management entity receives the “IP_Renewal_Request” event from the MIH function, it transfers the “IP_Linksetup_Complete” event to the MIH function after completing the IPCoA reconfiguration procedure. The source of the “IP_Linksetup_Complete” event corresponds to the remote MAC layer. Table 12 below shows parameters of the “IP_LinkSetup_Complete” event.

次に、ＩＰアドレス再設定手順と関連したイベント／コマンドサービス及びマルチモード移動端末のスタック間の関係について説明する。

Next, the relationship between the event / command service and the stack of the multi-mode mobile terminal related to the IP address reset procedure will be described.

  FIG. 17 is a diagram illustrating a protocol stack and IP address setup trigger operation of a multi-mode mobile terminal according to an embodiment of the present invention.

  If the new network to which the multi-mode mobile terminal is handed over cannot use the IP address of the previous network, the “IP_Renewal_Indication” event is forwarded to the MIH function according to one of a plurality of methods depending on the network type. According to the first method, the MAC layer message (ie L2 message) can indicate that the new network can use the address previously used in the network. According to the second method, the MAC layer message can indicate that the new network cannot use the address previously used by the network.

  In the first method, a MAC layer message indicating an IP address re-setup state is transferred to the second layer (L2) so that the message is generated from the MAC layer.

  In the second method, the second layer (L2) cannot determine whether or not an IP address re-setup is required due to the handover of the multi-mode mobile terminal. Therefore, the MIH function included in the network (that is, the connected POA or base station) transfers specific information indicating the above situation to the MIH function of the mobile terminal. In this case, the L2 layer reliably transfers the message to the MIH function.

  The first method described above can be performed in association with bit # 3 of the HO Process Optimization TLV of the standard IEEE 802.16. Even if a handover occurs in another network, the first method can be implemented by an indicator similar to bit # 3.

  When a new IP layer address is set, the “IP_LinkSetup_Complete” event indicates a trigger signal that informs the MIH function of the new IP layer address setup and instructs the MIH function to perform the necessary operations. For example, in the “Make Before Break” handover, the release of the MAC / PHY layer that can maintain the connection (or link) state with the previous network will completely set the connection (or link) state to the current network. Done at a certain time. Thereafter, the IP mobile protocol completes the IP address setup process so that the “IP_LinkSetup_Complete” event indicates the specific time.

  The operation of the method of the present invention can be classified as a first case operation in which the FA-CoA or co-located CoA of the mobile IPv4 system is used as a temporary address (CoA). The second case includes an operation in which the state-store-type address or non-state-store-type address of the mobile IPv6 system is used as a temporary address (CoA).

  Next, a method for adopting the FA-CoA of the mobile IPv4 system as the CoA when the mobile terminal is handed over to another interface network will be described.

  FIG. 18 is a diagram illustrating an example of using a FA-CoA of a mobile IPv4 system as a temporary address (CoA) when a mobile terminal is handed over to another interface network so that a subnet is changed according to an embodiment of the present invention. It is a flowchart which shows the method of resetting an address.

  Referring to FIG. 18, the mobile terminal sets the link and connection state of the current interface network. When a high quality link is detected from a lower layer (LL) such as a MAC layer of a new interface network, the mobile terminal forwards a “Link_Available” trigger signal to the MIH function of the mobile terminal. Thereafter, the new MAC layer (LL New) sets a new connection point (POA) and connection state. When the new MAC layer sets the connection state with the new POA, the new MAC layer performs an authentication process and informs the mobile terminal MIH function and the new POA MIH function of the link setup state.

  The new POA MIH function forwards an “IP_Renewal_Indication” event to the mobile terminal MIH function to command the CoA re-setup process when the mobile terminal subnet is changed to another subnet. When the “IP_Renewal_Indication” event commands a CoA reconfiguration process, the MIH function of the mobile terminal sends an “IP_Renewal_Request” trigger signal to the network layer (network) in order to command the network layer to reconfigure CoA. to the upper layer (HL) of the mobile terminal such as layer).

  When the network layer of the mobile terminal receives the “IP_Renewal_Request” trigger signal, the network layer forwards an Agent Solicitation message to the foreign agent (FA) to acquire a new temporary address (CoA). The foreign agent (FA) transfers an “Agent_Advertisement” message to the mobile terminal as a response to the agent solicitation (Agent Solicitation) message. Upon receiving the “Agent_Advertisement” message, the network hierarchy of the mobile terminal registers the temporary address (CoA) with the home agent (HA). When the CoA reconfiguration (re-setup) process is completed, the network layer of the mobile terminal transfers an “IP_Linksetup_Complete” trigger message to the MIH function of the mobile terminal.

  Next, a method for adopting “co-located CoA” of the mobile IPv4 system as CoA when the mobile terminal is handed over to another interface network will be described.

  FIG. 19 shows that when a mobile terminal is handed over to another interface network so that a subnet is changed according to an embodiment of the present invention, an address is assigned using “co-located CoA” of the mobile IPv4 system as CoA. It is a flowchart which shows the method to reset.

  Referring to FIG. 19, the mobile terminal resets the IP temporary address using “co-located CoA”, and “IP_Renewal_Indication” indicating the CoA re-setup state from the MIH function of the new point of attachment (POA) When receiving the trigger signal, the MIH function of the mobile terminal transfers the “IP_Renewal_Request” trigger signal to the network layer. Upon receiving the “IP_Renewal_Request” trigger signal, the network layer of the mobile terminal forwards a “DHCP Discovery” message to receive the temporary address (CoA). When the network hierarchy of the mobile terminal receives the temporary address, the mobile terminal registers the received CoA with the home agent (HA). When the CoA is registered with the home agent (HA), the network layer of the mobile terminal transfers an “IP_Linksetup_Complete” trigger signal to the MIH function.

  Next, a method for adopting “non-state-stored-type address” of the mobile IPv6 system as CoA when the mobile terminal is handed over to another interface network will be described.

  FIG. 20 is a diagram illustrating a case where a “non-state-store-type address” of a mobile IPv6 system is set as a temporary address (when a mobile terminal is handed over to another interface network so that a subnet is changed, according to an embodiment of the present invention. It is a flowchart which shows the method of resetting an address using it as CoA).

  As shown in FIG. 20, when the subnet of the mobile terminal is changed to another subnet, the MIH function of the new point of attachment (POA) sends an “IP_Renewal_Indication” message to command the CoA reconfiguration process to the MIH of the mobile terminal. Transfer to function. The MIH function of the mobile terminal then forwards an “IP_Renewal_Request” trigger signal to the network layer to instruct the network layer to reset CoA. When the network layer of the mobile terminal receives the “IP_Renewal_Request” trigger signal, it transmits a “Router Solicitation” message to the connected router in order to form a new temporary address (CoA).

  Preferably, the router forwards its prefix and other address configuration information to the mobile terminal in response to the “Router Solicitation” message of the mobile terminal. Thereafter, the mobile terminal combines the interface ID and the received prefix information so that the mobile terminal sets CoA. Preferably, the mobile terminal determines whether or not there is a CoA collision configured by the “Neighbor Solicitation” message and the “Neighbor Advertisement” message. If the mobile terminal does not receive a “Neighbor Advertisement” message in a predetermined time period, the uniqueness of the configured CoA is authenticated so that it can be determined that the CoA is available.

  Thereafter, the mobile terminal registers the CoA configured through the binding update message with the home agent. The home agent (HA) transfers a binding acknowledgment message as a response to the binding update (Binding Update) message of the home agent (HA). After completing the above-described HA registration process, the mobile terminal transfers an “IP_Linksetup_Complete” trigger signal to the MIH function of the mobile terminal.

  Next, a method for adopting “state-store-type address” of the mobile IPv6 system as CoA when the mobile terminal is handed over to another interface network will be described.

  FIG. 21 shows a state-storage-type address of a mobile IPv6 system as a temporary address (CoA) when a mobile terminal is handed over to another interface network so that a subnet is changed according to an embodiment of the present invention. It is a flowchart which shows the method of resetting an address using it.

  As shown in FIG. 21, when the subnet of the mobile terminal is changed to another subnet, the MIH function of the new point of attachment (POA) sends an “IP_Renewal_Indication” message to command the CoA reconfiguration process to the MIH of the mobile terminal. Transfer to function. Thereafter, the MIH function of the mobile terminal forwards an “IP_Renewal_Request” trigger signal to the network layer to instruct to reset CoA in the network layer. When the network layer of the mobile terminal receives the “IP_Renewal_Request” trigger signal, it transmits a “SOLICIT” message to the DHCPv6 server via the multicast address to form a new temporary address (CoA).

  The DHCPv6 server then forwards an “ADVERTISE” message in response to the “SOLICIT” message. The mobile terminal that has received the “ADVERTISE” message selects the server to advertise and forwards the “REQUEST” message to obtain additional configuration parameters. The DHCPv6 server forwards the “REPLY” message in response to the “REQUEST” message. Preferably, the mobile terminal employs the CoA included in the “REPLY” message as a temporary address so that the CoA is registered with the home agent (HA) via a binding update message.

  Thereafter, the home agent (HA) transfers a binding acknowledgment message in response to the binding update message. When the above-described CoA setup procedure is completed, the mobile terminal transfers an “IP_Linksetup_Complete” trigger signal to the MIH function of the mobile terminal.

  These preferred embodiments described above are for reconfiguring a temporary address using a mobile IPv4 system and a mobile IPv6 system under the condition that a multi-mode mobile terminal is handed over to another interface network so that the subnet is changed. Various methods have been disclosed. However, even if the multi-mode mobile terminal is handed over to another subnet included in the currently connected interface network, the aforementioned trigger signals (ie, IP_Renewal_Indication, IP_Renewal_Request and IP_Linksetup_Complete) also reset the temporary address (CoA). Can be configured as follows.

  FIG. 22 is a diagram illustrating an operation of a protocol stack and an IP address setup event / command service of a multimode mobile terminal according to an embodiment of the present invention.

  As shown in FIG. 22, if the new network to which the multi-mode mobile terminal is handed over cannot use the IP address of the previous network, the MAC layer of the mobile terminal forwards the “IP_Renewal_Indication” message to the MIH function of the mobile terminal. Upon receipt of the “IP_Renewal_Indication” message, the MIH function transfers an “IP_Renewal_Request” message serving as an MIH event to the upper management entity of the mobile terminal. Thereby, the MIH function preferably instructs the upper management entity to set the IP address. The upper management entity that has received the “IP_Renewal_Request” message completes the IP address setup process via the IP layer, transfers an “IP_LinkSetup_Complete” message that functions as an MIH command to the MIH function, and notifies the MIH function of the completion of IP address setup. .

  FIG. 23 is a diagram illustrating a case where an upper management entity assigns a FA-CoA of a mobile IPv4 system to a temporary address (CoA) when a mobile terminal is handed over to another interface network so that a subnet is changed. ) Is used to reset the IP address.

  As shown in FIG. 23, the mobile terminal sets the link and connection state of the current interface network. When a high quality link is detected from a lower layer (LL) such as the MAC layer of a new interface network, the mobile terminal forwards a “Link_Available” trigger signal to the MIH function of the mobile terminal. Thereafter, the new MAC layer sets a new connection point (POA) and connection state. When the new MAC layer sets the connection state with the new POA, the new MAC layer performs an authentication process and informs the mobile terminal MIH function and the new POA MIH function of the link setup state.

  Preferably, the MIH function of the new point of attachment (POA) is used to instruct the MIA function of the mobile terminal to perform a CoA re-setup process when the mobile terminal subnet is changed to another subnet. Forwards an “IP_Renewal_Indication” message that serves as a link event. The MIH function of the mobile terminal that has received the “IP_Renewal_Indication” message transfers the “IP_Renewal_Request” message to the upper management entity in order to instruct the upper management entity to reset the CoA.

  When the upper management entity of the mobile terminal receives an “IP_Renewal_Request” message that serves as an MIH event, the upper management entity sends an “Agent Solicitation” message to the foreign agent (FA) to acquire a new temporary address (CoA). Forward. Thereafter, the foreign agent (FA) transfers an “Agent_Advertisement” message to the mobile terminal in response to the “Agent Solicitation” message. Upon receiving the “Agent_Advertisement” message, the network hierarchy of the mobile terminal registers the temporary address (CoA) with the home agent (HA). Preferably, when the CoA reconfiguration (re-setup) process is completed, the higher-level management entity of the mobile terminal transfers an “IP_Linksetup_Complete” MIH command to the MIH function of the mobile terminal.

  FIG. 24 illustrates that when a mobile terminal is handed over to another interface network so that the subnet is changed, the upper management entity assigns the co-located CoA of the mobile IPv4 system to the temporary address (CoA) according to an embodiment of the present invention. ) Is used to reset the address.

  As shown in FIG. 24, the mobile terminal resets the IP temporary address (CoA) using “co-located CoA”, and shows the CoA reset (re-setup) state from the MIH function of the new connection point. Upon receiving the “IP_Renewal_Indication” message (functioning as a link event), the MIH function of the mobile terminal forwards the “IP_Renewal_Request” message to the upper management entity of the mobile terminal. Upon reception of the “IP_Renewal_Request” message, the upper management entity forwards the “DHCP Discovery” message to receive the temporary address (CoA). When the upper management entity receives the temporary address (CoA) by the DHCP address assignment procedure, the mobile terminal registers the received CoA with the home agent (HA).

  When the upper management entity of the mobile terminal registers CoA in the home agent via the IP layer, the upper management entity transfers an “IP_Linksetup_Complete” message that functions as an MIH command to the MIH function of the mobile terminal.

  FIG. 25 illustrates that when a mobile terminal is handed over to another interface network so that the subnet is changed, the upper management entity temporarily sets the non-state-store-type address of Mobile IPv6 according to an embodiment of the present invention. It is a flowchart which shows the method of using an address (CoA) and resetting an address.

  As shown in FIG. 25, when the subnet of the mobile terminal is changed to another subnet, the MIH function of the new attachment point functions as “IP_Renewal_Indication” which functions as a link event to command the CoA re-setup process. "Transfer the message to the MIH function of the mobile terminal. The MIH function of the mobile terminal then forwards an “IP_Renewal_Request” message to the upper management entity to instruct the upper management entity to reset the CoA through the IP layer. When the upper management entity receives the “IP_Renewal_Request” message, the upper management entity forwards the “Router Solicitation” message to the connecting router to construct a new temporary address (CoA).

  Preferably, the router forwards the prefix and other address configuration information to the mobile terminal to respond to the mobile terminal's "Router Solicitation" message. The mobile terminal combines its own interface ID with the received prefix information so that the mobile terminal sets the CoA. Preferably, the mobile terminal determines whether or not there is a CoA collision configured using the “Neighbor Solicitation” message and the “Neighbor Advertisement” message. If the mobile terminal does not receive a “Neighbor Advertisement” message in a predetermined time period, the uniqueness of the configured CoA is authenticated so that the configured CoA is determined to be available.

  The mobile terminal registers its CoA with the home agent (HA) using a “Binding Update” message. Thereafter, the home agent (HA) transfers a “Binding Acknowledgment” message in response to the “Binding Update” message. After completing the above-described HA registration process, the mobile terminal transfers an “IP_Linksetup_Complete” message that functions as an MIH command to the MIH function of the mobile terminal.

  FIG. 26 illustrates that when a mobile terminal is handed over to another interface network so that a subnet is changed according to an embodiment of the present invention, an upper management entity assigns a state-storage-type address of the mobile IPv6 system to a temporary address. It is a flowchart which shows the method of using as (CoA) and resetting an address.

  As shown in FIG. 26, when the subnet of the mobile terminal is changed to another subnet, the MIH function of the new point of attachment (POA) is used to command the CoA re-setup process (as a link event). "IP_Renewal_Indication" message is transferred to the MIH function of the mobile terminal. The MIH function of the mobile terminal then forwards an “IP_Renewal_Request” message that serves as an MIH event to instruct the higher management entity to reset the CoA to the higher management entity. When the upper management entity receives the “IP_Renewal_Request” message, the upper management entity forwards the “SOLICIT” message to the DHCPv6 server via the multicast address to construct a new temporary address (CoA).

  Thereafter, the DHCPv6 server forwards the “ADVERTISE” message to the mobile terminal in response to the “SOLICIT” message. The mobile terminal that has received the “ADVERTISE” message selects the server to advertise and forwards the “REQUEST” message to obtain additional configuration parameters. The DHCPv6 server then forwards the “REPLY” message in response to the “REQUEST” message. Preferably, the mobile terminal employs the CoA included in the “REPLY” message as a temporary address so that the CoA is registered with the home agent (HA) via a binding update message.

  Thereafter, the home agent (HA) transfers a binding acknowledgment message in response to the binding update message. When the above CoA setup procedure is completed, the upper management entity of the mobile terminal transfers an “IP_Linksetup_Complete” message that functions as an MIH command to the MIH function of the mobile terminal.

  FIG. 27 is a diagram for receiving specific information indicating that a subnet is changed from a previous point of attachment (POA) before a mobile terminal is handed over to another interface network according to an embodiment of the present invention. 3 is a flowchart illustrating a method. FIG. 27 illustrates a method for performing an IP address re-setup procedure after a mobile terminal is handed over to another interface network according to an embodiment of the present invention.

  As shown in FIG. 27, when handover of a mobile terminal is requested due to deterioration of link quality at a previous connection point (POA), the mobile terminal can remotely communicate with the upper management entity and the MIH function of the current connection point (POA). Informs the deteriorated link quality through a “Link_Going_Down” message.

  When the previous point of contact (POA) recognizes specific information indicating whether the IP address for communication has to be changed after the mobile terminal moves to the new point of attachment (POA), the previous POA Inform the mobile terminal MIH function of specific information via an “IP_Renewal_Indication” message. Thereafter, the mobile terminal can directly inform the upper management entity of specific information. Alternatively, the mobile terminal can indirectly inform the upper management entity of specific information via an “IP_Renewal_Request” message. When the mobile terminal uses the link setup procedure to set the new POA and link state, the mobile terminal performs the IP address setup procedure quickly with reference to the IP address setup information obtained from the previous POA.

  The preferred embodiment described above reconfigures the temporary address (CoA) using the Mobile IPv4 system and the Mobile IPv6 system under the condition that the multi-mode mobile terminal is handed over to another interface network so that the subnet can be changed. Various methods for doing so have been disclosed. However, even if the multi-mode mobile terminal is handed over to another subnet included in the currently connected interface network, the above-described trigger signals (ie, IP_Renewal_Indication, IP_Renewal_Request and IP_Linksetup_Complete) will also reset the temporary address. be able to.

  As is clear from the above description, the method for resetting the temporary IP address according to the present invention can be handed over from one subnet to another subnet in the network, or the subnet can be changed. As described above, the IP temporary address is quickly reset without time delay under the condition of being handed over to another interface network.

  Although the present invention has been described in mobile communication above, the present invention can be used in any wireless communication system that uses mobile devices such as PDAs and laptop computers with wireless communication capabilities. Also, the use of any specific terminology to describe the invention should not limit the scope of the invention to a particular type of wireless communication system such as UMTS. The present invention is also applicable to other wireless communication systems using other wireless interfaces and / or physical layers, such as TDMA, CDMA, FDMA, WCDMA, etc.

  Preferred embodiments may be embodied as a method, apparatus or article of manufacture using standard programming and / or engineering techniques to produce software, firmware, hardware or any combination thereof. As used herein, the term product refers to hardware logic (ie, integrated circuit chips, field programmable gate arrays (FPGAs), custom semiconductors (ASICs), etc.) or computer readable medium ( Magnetic storage media (ie, hard disk drives, floppy disks, tapes, etc.), optical storage (CD-ROM, optical disks, etc.), volatile and non-volatile memory devices (ie, EEPROMs, ROMs, PROMs, RAMs) , DRAMs, SRAMs, firmware, programmable logic, and the like)).

  Code in the computer readable medium is executed by being connected by a processor. The code embodying the preferred embodiment can also be connected from a file server via a transfer medium (media) or a network. In those cases, the product in which the code is embodied may include a transfer medium such as a network transfer line, a wireless transfer medium, a signal propagated through space, a radio wave, an infrared signal, and the like. Of course, those skilled in the art can make various modifications to the configuration without departing from the scope of the present invention, and the product may be any information holding medium known in the related art. Obviously it can be included.

  It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Accordingly, the present invention may include any modifications and variations of the present invention that fall within the scope of the appended claims and their equivalents.

  The foregoing embodiments and advantages are merely exemplary and are not intended to limit the invention. The present invention can be readily applied to other types of devices. The description of the present invention is intended to be illustrative and not restrictive of the scope of the claims. Many alternatives, modifications, and changes will be apparent to those skilled in the art. In the claims, a function-plus-function includes not only the recited function and structural equivalent, but also the structure described herein so as to perform up to the equivalent structure.

1 shows a general media independent handover (MIH) function reference model. FIG. 2 is a structural diagram illustrating a multi-mode mobile terminal. FIG. 2 illustrates a mediator independent handover (MIH) structure and transfer protocol. It is a structural diagram which shows an event trigger (event trigger). Triggers generated until the link setup process is performed from the currently connected link to the new link. It is a structural diagram which shows a link event (Link Event) model and a MIH event (MIH Event) model. It is a structural diagram which shows a remote link event (Remote Link Event) model. It is a structural diagram showing a remote MIH event (Remote MIH Event) model. FIG. 3 is a structural diagram showing an MIH command (MIH command) model and a link command (Link command) model. It is a structural diagram which shows a remote MIH command (Remote MIH command) model. It is a structural diagram showing a remote link command (Remote Link command) model. It is a figure which shows operation | movement of a mobile IPv4 system. 2 is a flow chart illustrating a method for enabling a Dynamic Host Configuration Protocol (DHCP) client to automatically receive an Internet Protocol (IP) address from a DHCP server. It is a flowchart which shows operation | movement of a mobile IPv6 system. It is a flowchart which shows operation | movement of a DHCPv6 server. 10 is a flowchart showing a temporary address (temporary address or care of address (CoA)) re-setup procedure when a multi-mode mobile terminal is handed over from one interface network to another interface network. 6 illustrates a protocol stack and IP address setup trigger operation of a multi-mode mobile terminal according to an embodiment of the present invention. According to an embodiment of the present invention, a method for resetting an IP address using “FA-CoA” of a mobile IPv4 system as a temporary address when a mobile terminal is handed over to another interface network so that a subnet is changed. It is a flowchart to show. According to an embodiment of the present invention, when a mobile terminal is handed over to another interface network so that a subnet is changed, a method for resetting an address using “co-located CoA” of the mobile IPv4 system as a temporary address is provided. It is a flowchart to show. According to an embodiment of the present invention, when a mobile terminal is handed over to another interface network so that a subnet changes, the address is reset using the non-state-store-type address of the mobile IPv6 system as a temporary address. 3 is a flowchart illustrating a method. A method of resetting an address using a state-store-type address of a mobile IPv6 system as a temporary address when a mobile terminal is handed over to another interface network so that a subnet changes according to an embodiment of the present invention. It is a flowchart which shows. FIG. 6 is a diagram illustrating an operation of a protocol stack and IP address setup event / command service of a multi-mode mobile terminal according to an embodiment of the present invention. According to an embodiment of the present invention, when a higher-level management entity is handed over to another interface network so that a subnet is changed, “FA-CoA” of the mobile IPv4 system is used as a temporary address (CoA). It is a flowchart which shows the method of resetting an IP address. According to an embodiment of the present invention, the upper management entity uses “co-located CoA” of the mobile IPv4 system as a temporary address (CoA) when the mobile terminal is handed over to another interface network so that the subnet changes. 5 is a flowchart showing a method for resetting addresses. According to an embodiment of the present invention, when the mobile terminal is handed over to another interface network so that the subnet is changed, the non-state-store-type address of the mobile IPv6 system is set as a temporary address (CoA). It is a flowchart which shows the method of using and resetting an address. According to an embodiment of the present invention, when the mobile terminal is handed over to another interface network so that the subnet is changed, the mobile IPv6 system state-storage-type address is used as a temporary address (CoA). 5 is a flowchart showing a method for resetting addresses. According to an embodiment of the present invention, before the mobile terminal is handed over to another interface network, specific information indicating that the subnet is changed from the old point of attachment (POA) is received. It is a flowchart which shows the method to do. FIG. 27 illustrates a method for performing an IP address re-setup procedure after a mobile terminal is handed over to another interface network according to an embodiment of the present invention.

Claims (40)

A method for setting a network address of a mobile terminal in a mobile communication system,
Configuring a unified interface to the upper layer of the mobile terminal to manage messages to / from one or more of a homogeneous network and a heterogeneous network;
Handing over the mobile terminal to one or more of the same type network and different type network; and
A request from the unified interface is received at the upper layer to set a network address of the mobile terminal for one or more of the same type network and different type network to communicate data And the stage of
Setting the network address for one or more of the homogeneous network and the heterogeneous network;
A network address setting method.   The network address setting method according to claim 1, wherein the network address is an Internet Protocol (IP) address.   The method of claim 1, wherein the step of receiving a request in the upper layer occurs when a subnet of the mobile terminal is changed.   The step of performing a handover includes performing a handover from a medium access control layer of a current network to one or more medium access control layers of the same type network and different types of networks. The network address setting method according to claim 1, wherein:   5. The network address setting method according to claim 4, wherein the same kind of network is the current network.   An indication indicating whether to set the network address of the mobile terminal for one or more of the same type network and the different type network to communicate data, the medium access of the mobile terminal The method of claim 1, further comprising receiving from one or more of the same type network and the different type network in a control layer.   A medium access control layer of the mobile terminal to indicate whether to set the network address of the mobile terminal for one or more of the same type network and different type network to communicate data The network address setting method of claim 1, further comprising: transferring an indicator to the unified interface from the network.   The unified interface determines whether to set the network address of the mobile terminal for one or more of the same type network and the different type network to communicate data. The network address setting method according to claim 1.   The method of claim 1, wherein the upper layer includes one or more of a mobility management protocol and an upper management entity.   The method may further include notifying that the network address for one or more of the same type network and the different type network is set in the unified interface from the upper layer. Item 2. The network address setting method according to Item 1.   2. The network address setting method according to claim 1, wherein the unified interface is a media independent handover (MIH) function. The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Requesting the IP address from one or more foreign agents of the same type network and the different type network;
Receiving the IP address from the foreign agent;
Registering the IP address for one or more of the homogeneous network and the heterogeneous network with a home agent of the home network;
The network address setting method according to claim 2, further comprising:   The network address setting method according to claim 12, wherein the IP address is a temporary address (CoA). The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Discovering and selecting one or more dynamic host configuration protocol (DHCP) servers of the homogeneous network and the heterogeneous network;
Requesting the IP address from the DHCP server for one or more of the homogeneous network and the heterogeneous network;
Receiving the IP address from the DHCP server;
Registering the IP address with a home agent of a home network;
The network address setting method according to claim 2, further comprising:   15. The network address setting method according to claim 14, wherein the IP address is a temporary address (CoA). The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Prefix information associated with the configuration of the IP address for one or more of the homogeneous network and the heterogeneous network is transmitted to one or more connecting routers of the homogeneous network and the heterogeneous network. Requesting, and
Receiving the prefix information from the connecting router;
Configuring the IP address using the received prefix information;
Registering the IP address with a home agent of a home network;
The network address setting method according to claim 2, further comprising:   The method of claim 16, wherein the IP address is a temporary address (CoA). The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Discovering and selecting one or more dynamic host configuration protocol v6 (DHCPv6) servers from the homogeneous network and the heterogeneous network;
Requesting the DHCPv6 server for the IP address for one or more of the homogeneous network and the heterogeneous network;
Receiving the IP address from the DHCPv6 server;
Registering the IP address with a home agent of a home network;
The network address setting method according to claim 2, further comprising:   The network address setting method according to claim 18, wherein the IP address is a temporary address (CoA).   The method of claim 1, wherein the step of receiving a request for setting a network address of the mobile terminal from the unified interface in the upper layer occurs before performing a handover. Network address setting method.   An indication indicating whether to set the network address of the mobile terminal for one or more of the same type network and the different type network to communicate data, the medium access of the mobile terminal The network address setting method according to claim 20, further comprising receiving from the current network in the control hierarchy.   The network address setting method according to claim 21, further comprising setting a connection with at least one of the same type network and the different type network.   The step of setting the connection includes the step of setting a connection between the medium access control layer of the mobile terminal and one or more medium access control layers of the same type network and the heterogeneous network. The network address setting method according to claim 22.   The method of claim 20, wherein the network address is an Internet Protocol (IP) address.   The step of receiving a request for setting a network address of the mobile terminal from the unified interface in the upper layer occurs when a subnet of the mobile terminal is changed. The network address setting method according to claim 20.   The step of performing a handover includes performing a handover from a medium access control layer of a current network to one or more medium access control layers of the same type network and a heterogeneous network, The network address setting method according to claim 20.   An indicator for indicating whether to set the network address of the mobile terminal for one or more of the same type network and the different type network to communicate data; 21. The network address setting method according to claim 20, further comprising a step of transferring from the access control layer to the unified interface.   The unified interface determines whether to set the network address of the mobile terminal for one or more of the same type network and the different type network to communicate data. The network address setting method according to claim 20.   The method of claim 20, wherein the upper layer includes one or more of a mobility management protocol and an upper management entity.   The method of claim 1, further comprising: notifying the unified interface from the upper layer that the network address for one or more of the same type network and the different type network is set. 21. The network address setting method according to 20.   21. The network address setting method according to claim 20, wherein the unified interface is a mediator independent handover (MIH) function. The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Requesting the IP address from one or more foreign agents of the same type network and the different type network;
Receiving the IP address from the foreign agent;
Registering the IP address for one or more of the homogeneous network and the heterogeneous network with a home agent of the home network;
25. The network address setting method according to claim 24, comprising:   The network address setting method according to claim 32, wherein the IP address is a temporary address (CoA). The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Discovering and selecting one or more dynamic host configuration protocol (DHCP) servers of the homogeneous network and the heterogeneous network;
Requesting the IP address from the DHCP server for one or more of the homogeneous network and the heterogeneous network;
Receiving the IP address from the DHCP server;
Registering the IP address with a home agent of a home network;
25. The network address setting method according to claim 24, comprising:   The network address setting method according to claim 34, wherein the IP address is a temporary address (CoA). The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Requesting prefix information associated with the configuration of the IP address for one or more of the homogeneous network and the heterogeneous network to one or more connecting routers of the homogeneous network and the heterogeneous network. When,
Receiving the prefix information from the connecting router;
Configuring the IP address using the received prefix information;
Registering the IP address with a home agent of a home network;
25. The network address setting method according to claim 24, comprising:   The network address setting method according to claim 36, wherein the IP address is a temporary address (CoA). The step of setting the IP address for one or more of the homogeneous network and the heterogeneous network comprises:
Discovering and selecting one or more dynamic host configuration protocol v6 (DHCPv6) servers from the homogeneous network and the heterogeneous network;
Requesting the DHCPv6 server for the IP address for one or more of the homogeneous network and the heterogeneous network;
Receiving the IP address from the DHCPv6 server;
Registering the IP address with a home agent of a home network;
25. The network address setting method according to claim 24, comprising:   The network address setting method according to claim 38, wherein the IP address is a temporary address (CoA). A mobile terminal capable of setting a network address in a mobile communication system,
A unified interface for managing messages to / from higher layers of the mobile terminal and one or more of the same and different networks;
Means for performing handover of the mobile terminal to one or more of the same type network and different type network;
A request for setting a network address of the mobile terminal for one or more of the same type network and the different type network to communicate data is received from the unified interface in the upper layer. Means to
Means for setting the network address for one or more of the homogeneous network and the heterogeneous network;
A mobile terminal comprising:

Images