MX2007010740A

MX2007010740A - Providing mobility management protocol information to a mobile terminal for performing handover in a mobile communication system.

Info

Publication number: MX2007010740A
Application number: MX2007010740A
Authority: MX
Inventors: Yong Won Kwak; Yong Ho Kim; Jin Lee
Original assignee: Lg Electronics Inc
Priority date: 2005-03-07
Filing date: 2006-03-07
Publication date: 2007-11-07
Also published as: KR20060097518A; CN101138268B; IL185710A0; JP2008532453A; CN101138268A; IL185710A; JP4902634B2; KR101141646B1

Abstract

The present invention relates to providing mobility management protocol information to a multi-mode mobile terminal for performing handover between heterogeneous networks. Preferably, the present invention establishes a unified interface to an upper layer of the mobile terminal for managing messages to and from at least one of a homogeneous network and a heterogeneous network, establishes a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network for performing handover, and receives in the upper layer information from the unified interface related to the established connection. Preferably, the step of receiving the information includes receiving mobility management protocol information of the at least one of a homogeneous network and a heterogeneous network. Accordingly, the mobile terminal reduces a time duration for establishing a Care of Address (CoA) using a new mobility management protocol of a new network the mobile terminal has been handed over to.

Description

PROPORTION OF PROTOCOL INFORMATION OF ADMINISTRATION OF MOBILITY TO A MOBILE TERMINAL TO MAKE TRANSFER IN A MOBILE COMMUNICATION SYSTEM Technical Field The present invention relates to a transfer method for a mobile terminal of a mobile communication system, and more particularly to providing mobility management protocol information to a multimodal mobile terminal for performing transfer between heterogeneous networks.

Background Technique Currently, the IEEE 802.21 standards committee conducts intensive research on international standards associated with independent media transfer (MIH) between heterogeneous networks. MIH provides not only a continuous transfer but also a continuity of service between heterogeneous networks, which results in greater convenience for a user carrying a mobile terminal. IEEE 802.21 defines a variety of functions (for example, an MIH function, an event service, a command service, and an information service (IS) function) as basic requirements. A mobile terminal (MSS) is indicative of a node multimodal to support at least two types of interface. For example, the multimode node can support a variety of interface types, such as a type of wired interface (also called a cable line interface type) such as Ethernet based on an IEEE 802.3 standard specification, a type of wireless interface based on IEEE 802. XX standard specifications (eg, IEEE 802.11, IEEE 802.15, IEEE 802.16), and other interface types defined by a cellular standardization organization (eg, 3GPP or 3GPP2). A reference model of General Independent Media Transfer Function (MIHF) is represented in FIGURE 1. In the figure, the MIHF architecture for interaction with other layers and with the remote MIHF is illustrated. For the MIHF to provide asynchronous and synchronous services to lower layers and higher layers, Service Access Points (SAP) such as MIH_MGMT_SAP, MIH_SME_SAP and MIH_SAP along with primitives are defined. MIH_MGMT_SAP defines the interface between the MIHF and the administration plane (Management Entity) of different network interfaces and is used to transport MIH protocol messages between the MIHF and the local link layer entities as well as similar MIHF entities. MIH_SAP defines the interface between the MIHF and the higher layer entities such as the device manager, the control function of transfer policy, transport, mobility management protocol layer 3 (L3) etc. and it is used for the configuration and operation of MIH. MIH_SME_SAP defines the interface between the MIHF and the Station Management Entity or the Network Management System, and is used for the MIH operation configuration. FIGURE 2 is a structural diagram illustrating a protocol layer of a multimodal mobile terminal. With reference to FIGURE 2, the protocol stack of the multimodal mobile terminal includes a MAC structure that includes the IEEE 802.11, the IEEE 802.16 and the 3G interface, and locates an MIH function under an Internet Protocol layer (IP). ). A variety of mobility management protocols are included in a network layer contained in the mobile terminal. The mobile terminal selects a mobility management protocol contained in the network layer according to a type of mobility management protocol supported at a junction point (POA) to which the mobile terminal is connected, and establishes an IP connection. . The MIH function, an event service, a command service and an Information Service (IS) will be described after this. With reference to FIGURE 2, the multimodal mobile terminal includes a physical layer (PHY), or a first layer (Ll), and a layer of Medium Access Control (MAC), or a second layer (L2), for individual modes, and locate the MIH layer under the IP layer. The MIH function located under the IP layer, ie, the Independent Media Transfer (MIH) must be defined between the IEEE 802 serial interfaces, or between an IEEE 802 serial interface and an 802 seriesless interface (for example, 3GPP) or 3GPP2). The MIH function facilitates a transfer process using input values (for example, an activating event and information associated with other networks) received from a second layer (Layer 2). The MIH function can include a plurality of input values based on a user policy and configuration that can affect the transfer process. The general interfaces between the mobile IP, a third layer entity (L3) such as a SIP (Session Initiation Protocol), and the MIH layer are defined. In this case, the aforementioned interfaces provide the first layer (i.e., the physical layer), the second layer (i.e., the MAC layer), and the mobility management training. The MIH function acquires information associated with a lower layer and a network that uses events and information service (IS) functions. A top layer includes a superior management entity to monitor states and operations of several links contained in a mobile terminal, so that which performs a transfer control function and a device manager function. In this case, the transfer control function and the device manager can be located in different locations independent of each other, or the transfer control function and the device manager can be included as the top management entities in the upper layer. FIGURE 3 shows an MIH structure and a transmission protocol. In more detail, FIGURE 3 shows a mobile terminal function entity including the MIH function, a network function entity and a transmission protocol. The dashed lines in FIGURE 3 are indicative of primitive information and an event trigger, etc. In order to quickly perform a transfer function, a network layer uses information generated from a link layer so that the network layer can quickly reestablish a connection state. The link layer event is adapted to predict the movement of a user, and assists a mobile terminal and a network to prepare the transfer function. An activator for the transfer can be initiated from the physical layer (PHY) and the MAC layer. An activator source can be determined to be a local stack or a remote stack. FIGURE 4 is a block diagram illustrating an activating model. An event trigger provides status information of a current signal, status change information of another network, and future predicted change information. The event trigger also includes change information of the physical and MAC layers or the change information of attributes of a specific network. Event types can be classified into a physical layer event (PHY), a MAC layer event, an administration event, a third layer event (L3), and an application event, for example. There is a plurality of basic trigger events, such as "Link_Up" event, a "Link_Down" event, a "Link_Going_Down" event, a "Link_Going_Up" event, an * "Ling_Event_Rollback" event, an "Link_Available" event ", an event of" Link_Parameters_Change ", an event of" IP_Renewal_Indication ", an event of" IP_Renewal_Request ", for example. The aforementioned triggering events will be described thereafter with reference to the following tables. The following Table 1 shows parameters of the "Link Jp" event. The "Link_Up" event occurs when a second layer connection (L2) is established in a specific link interface and an upper layer is capable of transmitting third layer packages (L3). In this case, it is determined that all the L2 layers contained in a link have been completely configured. A source of the "Link_Up" event corresponds to a "Local MAC" and a "Remote MAC".

[Table 1] The following Table 2 shows parameters of the "Link_Down" event. The "Link_Down" event occurs when the L2 connection is released in a specific interface and the L3 packets can not be transmitted to a destination. The source of the "Link Down" event is indicative of a local MAC.

[Table 2] The following Table 3 shows parameters of the "Link_Going_Down" event. The "Link_Going_Down" event occurs when it is expected that the L2 connection will enter a "Link_Down" state within a predetermined time, and may serve as a signal to initialize a transfer procedure. A source of the "Link_Going_Down" corresponds to a "Local MAC" and a "Remote MAC".

[Table 3] The following Table 4 shows parameters of the "Link_Going_Up" event. The "Link_Going_Up" event occurs when it is expected that the L2 connection will enter a "Link_Up" state within a predetermined time, and is used when a long period of time is consumed to start a network. A source of the "Link_Going_Up" event corresponds to a "Local MAC" and a "Remote MAC".

[Table 4] The following Table 5 shows parameters of the "Link_Event_Rollback" event. The "Link_Event_Rollback" event is formed by combining the "Link_Going_Down" event with the "Link_Going_Up" event. The "Link_Event_Rollback" event is indicative of a trigger generated when it is expected that the "Link-Up" event or the "Link_Down" event will no longer be generated within a specific time in the condition that the "Link_Going_Up" event "or the" Link_Going_Down "event are transmitted to a destination. A source of the "Link_Event_Rollback" event corresponds to a "Local MAC" and a "Remote MAC".

[Table 5] The following Table 6 shows parameters of the "Link_Available" event. The "Link_Available" event is indicative of an available state of a new specific link, and indicates the possibility of allowing a new base station (BS) or a new Union Point (POA) to provide a superior link in quality when compared with a current BS or a current POA to which the current mobile terminal is connected. A source of the "Link_Available" event corresponds to a "Local MAC" and a "Remote MAC".

[Table 6] The following Table 7 shows parameters of the event of "Link_Parameter_Change". The "Link_Parameter_Change" event is indicative of an event generated when a change of a link parameter value is higher than a specific threshold level. The "Link_Parameter_Change" event includes link layer parameters, for example, a link speed (ie, a link rate), a QoS (Quality of Service), and an encrypted value, etc. A source of the "Link_Parameter_Change" event corresponds to a "Local MAC" and a "Remote MAC".

[Table 7] The following Table 8 shows parameters in the event of "IP_Renewal_Indication". A new POA (for example, a base station or POA) of the mobile terminal receives the "Link_Up" trigger signal, and activates the "IP_Renewal__Ind? cat? on" event to inform the mobile terminal of a changed state or without change of an IP address used to transmit the IP packets to the mobile terminal. The IP address is set to a newly assigned IP address in the case of a dynamic central configuration protocol (DHCP) system, to a new temporary address (CoA) in the case of a mobile IPv4 system, and to an address of Auto-configuration in the case of a mobile IPv6 system. A source of the event "IP_Renewal_Ind? Cat? On" corresponds to a "Remote MAC" and an "MIH".

[Table 8] The following Table 9 shows parameters of the event of "IP_Renewal_Request". Upon receiving the "IP_Renewal_Indication" trigger signal indicative of an address reset state, the MIH function of the mobile terminal transmits an "IP_Renewal_Request" signal to a network layer, so that it requests the network layer to reestablish a network layer. temporary IP address. An event source of "IP_Renewal_Request" corresponds to a "Remote MAC" and an "MIH".

[Table 9] FIGURE 5 shows event triggers generated when a transfer occurs. In more detail, FIGURE 5 shows exemplary triggers generated when a quality of a current access link deteriorates. Activators are generated until a new link is established. A command service allows a top layer to command a lower layer to perform an operation default For example, the upper layer transmits a specific command to the MIH function so that the MIH function performs a corresponding operation. The MIH function can also transmit a specific command to the lower layer so that the lower layer performs a corresponding operation. The aforementioned commands are adapted to transmit a decision from the upper layer to the lower layer, and control the behavior or tasks of the lower layer entities. An information service provides detailed information associated with a network required for network discovery and network selection, and is designed to be freely accessed by a user over any network. The information service includes a variety of information components, for example, a link access parameter, a security mechanism, a neighborhood map, a location, information indicative of a service provider and other access information, and a link cost (that is, link cost). FIGURE 6 is a flow diagram illustrating a method for controlling a multimodal mobile terminal to acquire information associated with the network by means of an information server. As shown in FIGURE 6, the multimodal mobile terminal acquires varied information associated with the network through the information server and performs a transfer evaluation operation, a link selection operation and a transfer procedure. In more detail, the multimodal mobile terminal receives a message of "Request / Response of Information" and a message of "List of Answers of the Available Networks". The multimodal terminal then acquires varied information associated with the network of an information server through a current point of attachment (POA) using the "Request / Information Response" message and the "Available Network Response List" message so that the multimodal terminal performs a transfer evaluation operation and a link selection operation. If a new link is selected, the mobile terminal acquires information associated with a new network through the new junction point (POA) and a message of "Consultation / Response of MIH Resources". A variety of protocols (eg, mobile IPv4, DHCPv4, Mobile IPvd, and DHCPvβ, etc.) to support the mobility of a mobile terminal after this will be described. FIGURE 7 is a diagram illustrating operations of a mobile IPv4 system. The mobile IPv4 system requires a variety of functions (ie, a mobile central function, a local agent function and a foreign agent function), so that it can provide the layer superior with clear mobility. However, if a path is not optimized, there is no need for a corresponding node communicating with the mobile terminal to be changed to another. In this case, the mobile central computer is indicative of an IP central computer to which it supports mobility. The local agent maintains the location information associated with the mobile central computer, and serves as a router to perform the channeling of the mobile central computer. The foreign agent is indicative of a router to support mobility over a foreign network. The operations of the mobile IPv4 system shown in FIGURE 7 will be described after this. With reference to FIGURE 7, the mobile central computer moves from its local network to a foreign network in step S10. The mobile central computer then receives an advertising message currently broadcast over the foreign network, so that the mobile central computer recognizes that it has been changed. After this, the mobile central computer registers a temporary address or voltage address (CoA) indicative of a current location of the mobile central computer with the local agent (HA) in step S20. In this case, the temporary address (CoA) may be equal to an IP address (ie, foreign agent (FA) - CoA) of the foreign agent, or equal to a Co-localized CoA temporarily assigned to the mobile central computer by the DHCP in the foreign network.

The packets transmitted from an external part to the mobile central computer are transmitted to the local network. These packets are intercepted by the local agent in step S30, which recognizes the movement of the mobile terminal. The local agent that has intercepted the above packets establishes a destination address of the packets transmitted to the mobile central computer at a foreign agent (FA) address with the condition that the FA-CoA is used. The mobile host computer then encapsulates the destination address indicative of the address of FA and transmits the address encapsulated in step S40. After this, the encapsulated transmission packets are transmitted to the foreign agent (FA), where the foreign agent (FA) de-encapsulates the received packets to recover the original packets and transmits the original packets when ordering mobile exchange in step S50. The packets transmitted from the mobile central computer to the corresponding node can be transmitted directly by the foreign agent (FA). If an entry filtering problem occurs, the aforementioned packages can also be transmitted through a reverse tunnel. The main functions required for the mobile IP are an agent discovery function, a registration function, and a routing function, etc., and its detailed description will be described after this. The discovery of agents is indicative of a method for allowing a mobile terminal to determine whether the mobile terminal is connecting to its own local network or to a foreign network, so that the mobile terminal itself can recognize whether it has been switched to another network. The mobile IP extends a conventional ICMP Router Discovery (Internet Control Message Protocol) (i.e., IETF RFC 1256) to discover a desired agent. The agent advertising message broadcast periodically by the agents (ie, local agent and foreign agent) includes a message of "Mobility Agent Advertising Extension" in a message of "ICMP Router Advertising", and transmits the message of "ICMP Router Advertising" that includes the message of "Mobility Agent Advertising Extension". An "Agent Request" message transmitted when the mobile terminal searches for an agent uses the same method as in a conventional "ICMP Router Request" message. When the mobile terminal is switched to another network, a registration function transmits the current location information to the local agent, and allows the mobile terminal to receive services from the local network without any change, so that a highly adaptive mechanism is provided. Mobile IP provides two procedures for register (ie, FA-CoA and CoA co-localized), so that you can establish a temporary address or service address (CoA) when the mobile terminal is switched to another subnet. If the mobile terminal uses the FA-CoA, it performs the registration through the foreign agent (FA). If the mobile terminal uses the co-localized CoA, the mobile terminal directly registers with the local agent. Also, if the FA-CoA is used, the CoA is provided from a foreign agent by means of an agent advertisement message, and an IP address of the foreign agent (FA) is used as a temporary address (CoA). If the co-localized CoA is used, the mobile terminal receives a temporary address (CoA) through a DHCP server located in the foreign network. A routing function defines a variety of functions required to properly route a datagram transmitted to / received from the mobile terminal when the mobile terminal connects or accesses a foreign network. The datagram includes a unicast packet, a multicast packet, and a broadcast packet. A Dynamic Central Configuration Protocol (DHCP) is indicative of a protocol that allows network administrators to centrally manage / assign necessary IP addresses in a network contained in their organization. When computer users get access to the Internet in an organization, an IP address it must be assigned to individual computers. When the network administrator centrally manages / assigns the IP address, and connects to a computer to the Internet at points outside the network, DHCP automatically transmits a new IP address to the computer. DHCP uses a rent (or rent) scheme to control a given IP address. According to the scheme, the given IP address is valid in a corresponding computer only for a predetermined period of time. A rental time can be changed according to a time of Internet access required by a user in a specific location. DHCP reduces the IP address rental time when much more computers are used than the available IP addresses, so that DHCP can dynamically rebuild a network. In order to operate DHCP correctly, at least one DHCP server and one simple DHCP client is included in a corresponding network. Also, the network must also include not only the scope of a TCP / IP address (for example, 203.224.29.10 - 203.224.29.100) but also a link port address and a subnet mask. The DHCP client acquires the TCP / IP address information from the DHCP server while it is in operation. However, it should be noted that the TCP / IP address acquired is not permanent. The DHCP server It provides a customer with a rental address that may periodically expire or be periodically updated. The DHCP customer acquires / maintains the rental address through a plurality of invitation stages, each of which is referred to as a state. There is a plurality of client DHCP states, i.e., an initialization state (INT), a selection state (SELECT), a request status (REQUEST), a link status (LINK), a renewal status ( RENEWAL), and a re-link status (REENLACE), etc. FIGURE 8 shows a DHCP message format. FIGURE 9 is a flow diagram illustrating operations of a DHCP client-server model, and shows a method for allowing the DHCP client to automatically receive a DHCP server IP address. The following Table 10 shows various types and uses of the DHCP messages shown in FIGURE 9.

[Table 10] FIGURE 9 is a diagram illustrating the operations of a DHCPv4 system. With reference to FIGURE 9, the DHCPvd system is indicative of a DHCP protocol for the IPv4 system. Specifically, a method for controlling the DHCP client to automatically receive a DHCP server IP address after this will be described with reference to FIGURE 9 and Table 10. First, the client broadcasts a "DHCPDISCOVER" message in the stage SllO. If individual servers receive the "DHCPDISCOVER" message from the client, they reply to the message received from "DHCPDISCOVER" and transmit a message of "DHCPOFFER" as a response signal in step S120. The client who has spread the message of "DHCPDISCOVER" receives the "DHCPOFFER" message from one or more servers, and selects one of the servers to request a configuration parameter. After this, the client broadcasts a "DHCPREQUEST" message in step S130. In this case, servers not selected by the "DHCPREQUEST" message acknowledge that the client has declined their respective offers. The server selected by the "DHCPREQUEST" message includes address configuration information in a "DHCPACK" message, and transmits the "DHCPACK" message with the address configuration information as a response signal in step S140. If the client receives the "DHCPACK" message from the selected server, it constructs an address in step S150. However, if the client receives a "DHCPNAK" message, the client restarts the aforementioned process. The client may also transmit a "DHCPRELEASE" message to the server when it returns a rented address in step S160. FIGURE 10 is a flow diagram illustrating operations of a mobile IPv6 system. The mobile IPv6 system can more effectively support mobility of a mobile terminal than the mobile IPv4 system, and it has superior extensibility. The main components for operations of the mobile IPv6 system and the functions of the individual main components will be described afterwards with reference to FIGURE 10. With reference to FIGURE 10, a mobile node (MN) is a central computer or router that changes its network of access. A corresponding node (CN) is a central computer or router that communicates with the mobile node (MN). A local agent (HA) acts as a router, and contains registration information of the mobile node (MN) obtained from other routers contained in a local network so that the HA can transmit a datagram to a current position of the mobile node (MN) content in a foreign network. A temporary address or care address (CoA) is indicative of an IP address connected to the mobile node when the mobile node is switched to a foreign node. A term "Link" is indicative of a specific operation in which the mobile node compares the CoA registered in the local agent with a local address of a corresponding node. A "Link Update (BU)" message is indicative of a message used when the mobile node itself reports to the local agent (HA) and the corresponding node (CN) of a CoA of the mobile mode. A "Link Confirmation (BACK)" message is indicative of a response message to the aforementioned "BU" message. A "Link Request (BR)" message is indicative of a message to request the "BU" message when the corresponding node (CN) does not receive the "BU" message until a timer for the binding information of the mobile node expires. A term "Acquisition of CoA" is indicative of a specific operation in which the mobile node automatically constructs its location information while it is in motion using a neighbor discovery function and an address auto-configuration function. A term "Router Optimization" is indicative of a specific procedure during which the corresponding node (CN) communicates directly with the mobile node without passing through the local agent after storing the link information. The aforementioned address self-configuration function is classified into two methods of auto-address configuration. For example, a first method is a method of state self-configuration address maintenance to acquire an address using a server, such as the DHCP server. A second method is a non-state type address auto-configuration method, where the mobile node controls a central computer to generate an address on its own. The auto-configuration method of state maintenance type address is adapted to assign one of a plurality of addresses capable of being assigned from the server to the central computer with the condition that the central computer requests an address from the DHCP server. The Stateless type address auto-configuration method combines the interface ID information of the mobile node with the prefix information acquired from the router, so that the mobile node forms an address. The operations of the mobile IPv6 system shown in FIGURE 10 will be described after this. With reference to FIGURE 10, if the mobile node (MN) is changed from one subnet A to another subnet B in the step S200, the mobile node (MN) recognizes that it has been changed to another subnet B using the prefix information of a Router Advertising message (RA) and a Neighbor Unreachable Detection (NUD) mechanism in step S210. The mobile node (MN) then acquires a temporary address or care address (CoA) by itself using the aforementioned address self-configuration method in step S220. After this, the mobile node (MN) transmits the "BU" message so that the local agent recognizes the CoA acquired in step S230. The local agent (HA) that has received the "BU" message combines (or links) the local address of the mobile node (MN) with a temporary address (CoA) and transmits a "BACK" message as a response signal to the "BU" message in S240. The corresponding node (CN) communicating first with the mobile node (MN) does not recognize that the mobile node (MN) has been changed to another subnet. Accordingly, the CN establishes a destination address at a local address of the mobile node (MN), and transmits the resulting packet to the local agent (HA) in step S250. The local agent (HA) to handle the mobile node (MN) intercepts the packet of the corresponding node (CN), and performs the channelization of the packet in a current location of the mobile node (MN) in step S260. If the mobile node (MN) receives the piped packet, it determines that the corresponding node (CN) that has transmitted the packet does not have the link information, and transmits the "BU" message to the corresponding node (CN), so that informs the corresponding node (CN) of a CoA of the mobile node (MN) in step S270. The corresponding node (CN) that has received the CoA from the mobile node (MN) stores the link information, and communicates directly with the mobile node (MN) using the link information in step S280. FIGURE 11 is a flow diagram illustrating the operations of a DHCPv6 system. With reference to FIGURE 11, the DHCPv6 system is indicative of a DHCP protocol for IPv6, and supports the method of self-configuration of type address and state maintenance.

The DHCPv6 system is indicative of a specific mechanism by which an IP address, varied information (for example, routing information), and a network resource management function are concentrated in a small number of DHCP servers, which result in the reduction of maintenance costs. The DHCPvd uses two multicast addresses, such as an address of "All_DHCP_Relay_Agents_and_Servers" and an address of "All_DHCP_Servers". The address of "All_DHCP_Relay_Agents_and_Servers" is indicative of a local link multicast address, which is used by a client to allow the client to communicate with an agent contained in a link with the condition that a local agent link address do not know All servers and agents act as components of the previous multicast group. The address of "All_DHCP_Servers" is indicative of a local site multicast address, which is used by a client or a relay when the client or relay transmits a message to all servers or does not recognize unicast addresses of the servers, so that the client or the relay can communicate with a server. In order to allow the client to use the aforementioned "All_DHCP_Servers" address, the client must have sufficient margin addresses in which the client arrives. server. All the servers contained in a site act as components of the aforementioned multicast group. A variety of messages can be used for basic operations of the DHCPv6 system, such as a "REQUEST" message, an "ANNOUNCE" message, an "ASK" message, an "ANSWER" message, a "RENEW" message , a message of "RELEASE", for example. The "REQUEST" message is adapted for the client to recognize the server location information, and is subjected to multitasking using the address of "All_DHCP_Servers". The "ANNOUNCE" message is indicative of a response message to the "REQUEST" message. If possible, the DHCP server responds to the "REQUEST" message. The "ORDER" message is adapted to acquire constituent parameters equipped with an IP address of the server selected by the client, and is subjected to multitasking using the address of "All_DHCP_Relay_Agents_and_Servers". The "RESPOND" message is indicative of a response message to the aforementioned "ASK", "RENEW" and "RELEASE" messages. The "RENEW" message is indicative of a message required when the customer acquires an initially assigned customer address and the duration of the constituent parameters. The message "RELEASE" is indicative of a message required when the client returns at least one IP address to the server. The operations of the DHCPvd system shown in FIGURE 11 will be described after this. With reference to FIGURE 11, the client transmits the "REQUEST" message to the address of "All_DHCP_Servers" to recognize the location information of the server in step S310. The individual DHCPvd servers then produce the message "ANNOUNCE" to respond to the "REQUEST" message in step S320. In this case, the "ANNOUNCE" message includes the prefix information. After this, the client selects one of the DHCPvd servers, transmits an "ASK" message to the selected server, and at the same time requests an additional constituent parameter in step S330. The selected DHCPvd server produces the "ANSWER" message to answer the "ASK" message in step S340. The client that has received the "RESPONDER" message transmits the "RENEW" message to the DHCPvd server, so that it updates the conventional constituent parameters and the duration of the assigned addresses, and the operation of the TI timer begins in step S350 . In this case, the reference symbol "TI" is indicative of a specific time during which the customer accesses the server that has acquired an old address to increase the duration of a current address. The DHCP server then transmits the "RESPOND" message as a response signal to the "RENEW" message in step S360. After this, the client produces the "RELEASE" message when an assigned address is no longer used, so that a corresponding address is released in step S370. FIGURE 12 is a flow diagram illustrating an IP address setting procedure. In more detail, the IP address setting procedure indicates the operations carried out when the multimodal mobile terminal is transferred to a new network, and a mobility management protocol of the new network is different from that of an old network. With reference to FIGURE 12, the old network supports the mobility management protocol of the mobile IPv4 system. The new network supports the mobility management protocol of the mobile IPvd system. It is assumed that the multimodal mobile terminal installs the mobility management protocols of the mobile IPv4 system and the mobile IPvd system in a stack. If the multimodal mobile terminal is transferred to a new network, it receives an activating signal of "IP_Renewal_Indication", and performs a procedure of reestablishment of CoA. In more detail, the mobile terminal that has used the mobile IPv4 as the mobility management protocol in an old network broadcasts the message "Agent Request" to acquire a new CoA. However, the new network (to which the mobile terminal is currently transferred) provides the mobile IPvd as the mobility management protocol, so that the "Agent Request" message is discarded. Accordingly, the mobile terminal does not receive an "Agent Advertising" message in response to the "Agent Request" message after a duration of the "Agent Request" message expires. After retrying transmitting the "Agent Request" message several times, the mobile terminal determines that it can no longer be operated by IPv4, and performs a CoA establishment procedure using the mobile IPvd message. As described in the above, with the proviso that the multimodal mobile terminal is transferred to an interface network (ie, a new network), and a mobility management protocol of an old network is different from that of the new one. network, the mobile terminal requires a very long period of time until it recognizes that it can no longer be operated by the mobility management protocol of the old network in the new network. Only then the mobile terminal establishes a CoA using a protocol of network mobility management. In other words, a long time delay occurs before the mobile terminal determines that it can not be operated by the old mobility and management protocol of the old network of the new network and establishes a CoA using the new mobility management protocol. Therefore, due to the aforementioned problems, the mobile terminal to perform the transmission / reception of traffic in real time finds a damaged package and an extended service time.

Description of the Invention The present invention is directed to providing mobility management protocol information to a multimodal mobile terminal to perform transfer between heterogeneous networks. Additional features and advantages of the invention will be set forth in the description that follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and obtained by a structure particularly indicated in the written description and claims thereof and the attached drawings. To achieve these and other advantages and in accordance with the purpose of the present invention, as it is widely represented and described, the present invention is represented in a method for providing mobility management protocol information to a mobile terminal, the method comprising establishing a unified interface to an upper layer of the terminal mobile to handle messages to and from at least one of a homogeneous network and a heterogeneous network, discover an access link of at least one of a homogeneous network and a heterogeneous network to perform transfer, and inform the upper layer of the link accessible through the unified interface, wherein the step of informing the upper layer comprises providing the upper layer with mobility management protocol information of at least one of a homogeneous network and a heterogeneous network before establishing a connection with the link accessible In an aspect of the invention, the method further comprises requesting an exploration of at least one of a homogeneous network and a heterogeneous network through the unified interface to determine the presence of the accessible link of at least one of a homogeneous network and a network heterogeneous to perform the transfer. In another aspect of the invention, the method further comprises requesting information related to the accessible link from at least one of a homogeneous network and a network heterogeneous of an information server operationally connected to at least one of a homogeneous network and a heterogeneous network. Preferably, the information request step comprises requesting mobility management protocol information from at least one of a homogeneous network and a heterogeneous network. Preferably, the unified interface is a media-independent transfer function (MIHF) entity. Preferably, the upper layer comprises a higher management entity for handling homogeneous and heterogeneous network links associated with the mobile terminal. Preferably, the top layer comprises at least one of a mobility management protocol for handling a respective mobile terminal mobility method. According to another embodiment of the present invention, a method for providing mobility management protocol information to a mobile terminal comprises establishing a unified interface in a top layer of the mobile terminal to handle messages to and from at least one of a homogeneous network and a heterogeneous network, establish a function with an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer, and receive in the upper layer information of the unified interface related to the established connection, wherein the step of receiving information comprises receiving mobility management protocol information from at least one of a homogeneous network and a heterogeneous network. Preferablysee , the step of receiving the information comprises receiving in the upper layer a request from the unified interface to establish a network address for at least one of a homogeneous network and a heterogeneous network where the network address is a protocol address of Internet (IP). Preferably, the unified interface is a media-independent transfer function (MIHF) entity. Preferably, the upper layer comprises a higher management entity for handling homogeneous and heterogeneous network loops associated with the mobile terminal. Preferably, the upper layer comprises at least one mobility management protocol for handling a respective mobile terminal mobility method. In an aspect of the invention, the step of receiving the information comprises providing the upper layer with the mobility management protocol information to a specific mobility management protocol related to the information. In another aspect of the invention, the method further comprises providing the upper layer with mobility management protocol information by providing the information to a specific mobility management protocol related to the information, and establishing the network address for at least one of a homogeneous network and a heterogeneous network when the mobility management protocol information is provided to the specific mobility protocol. In a further aspect of the invention, the method further comprises establishing the network address for at least one of a homogeneous network and a heterogeneous network. According to another embodiment of the present invention, a method for providing mobility management protocol information to a mobile terminal comprises establishing a unified interface to a top layer of the mobile terminal to handle messages to and from at least one of a homogeneous network and a heterogeneous network, establish a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer, and inform the upper layer of the connection established with the link accessible through the unified interface, wherein the step of informing the upper layer comprises providing the upper layer with mobility management protocol information of at least one of a homogeneous network and a heterogeneous network. Preferably, the unified interface is a entity as a function of independent media transfer (MIHF). Preferably, the upper layer comprises a higher management entity for handling homogeneous and heterogeneous network links associated with the mobile terminal. Preferably, the upper layer comprises at least one mobility management protocol for handling a respective mobile terminal mobility method. Preferably the step to provide the upper layer with mobility management protocol information comprises providing information to a specific mobility management protocol related to the information. According to another embodiment of the present invention, a method for providing mobility management protocol information to a mobile terminal comprises establishing a unified interface to a top layer of the mobile terminal to handle messages to and from at least one homogeneous network and a heterogeneous network, establish a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer, and receive in the upper layer a request from the unified interface to establish a network address for less one of a homogeneous network and a heterogeneous network, where the stage of receiving a request to establish a network address comprises providing the upper layer with mobility management protocol information of at least one homogeneous network and a heterogeneous network. Preferably, the network address is an Internet Protocol (IP) address. Preferably, the unified interface is a media-independent transfer function (MIHF) entity. Preferably, the upper layer comprises a higher management entity for handling homogeneous and heterogeneous network links associated with the mobile terminal. Preferably, the upper layer comprises at least one mobility management protocol for handling a respective mobile terminal mobility method. In an aspect of the invention, the step of providing the upper layer with the mobility management protocol information comprises providing the information to a specific mobility management protocol related to the information. Preferably, the method further comprises setting the network address for at least one of a homogeneous network and a heterogeneous network when the mobility management protocol information is provided to the specific mobility management protocol. In another aspect of the invention, the method further comprises establishing the network address for at least one of a homogeneous network and a heterogeneous network. According to another embodiment of the present invention, a mobile terminal for receiving mobility management protocol information comprises a unified interface in the upper layer of the mobile terminal for handling messages to and from at least one homogeneous network and a heterogeneous network, means for discovering an accessible link of at least one of a homogeneous network and a heterogeneous network for performing the transfer, and means for informing the upper layer of the link accessible through the unified interface, where the means for reporting to the upper layer comprises means for providing the upper layer with mobility management protocol information in at least one of a homogeneous network and a heterogeneous network before establishing a connection with the accessible link. In accordance with another embodiment of the present invention, a mobile terminal for receiving modality management protocol information comprises a unified interface on a top layer of the mobile terminal for handling messages to and from at least one homogeneous network and a heterogeneous network. means for establishing a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network for performing transfer, and means for receiving in the upper layer unified interface information related to the established connection, wherein the means for receiving the information comprises means for receiving mobility management protocol information from at least one of a homogeneous network and a heterogeneous network. According to another embodiment of the present invention, a mobile terminal for receiving mobility management protocol information comprises a unified interface in a top layer of the mobile terminal for handling messages to and from at least one homogeneous network and a heterogeneous network. means for establishing a connection with accessible link of at least one of a homogeneous network and a heterogeneous network for performing transfer, and means for informing the upper layer of the connection established with the link accessible through the unified interface, wherein the means for informing the upper layer comprises means for providing the upper layer with mobility management protocol information of at least one of a homogeneous network and a heterogeneous network. According to another embodiment of the present invention, the mobile terminal for receiving mobility management protocol information comprises a unified interface in a top layer of the mobile terminal for handling messages to and from at least one homogeneous network and a heterogeneous network , means to establish a connection to an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer, and means to receive in the upper layer a request from the unified interface to establish a network address for at least one of a network homogeneous and a heterogeneous network, wherein the means for receiving a request to establish a network address comprises means for providing the upper layer with mobility management protocol information of at least one of a homogeneous network and a heterogeneous network. It will be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide a further explanation of the invention as claimed.

Brief Description of the Drawings In the drawings: FIGURE 1 illustrates a general independent media transfer function (MIHF) reference model. FIGURE 2 is a structural diagram illustrating a protocol stack structure of a multimodal mobile terminal. FIGURE 3 is a block diagram illustrating an independent media transfer structure (MIH) and a transmission protocol. FIGURE 4 is a structural diagram illustrating an activating model. FIGURE 5 illustrates triggers of events generated when a transfer operation occurs. FIGURE 6 is a flow chart illustrating a method for allowing a multimodal mobile terminal to acquire information associated with the network through an information server. FIGURE 7 is a diagram illustrating operations of a mobile IPv4 system. FIGURE 8 is a structural diagram illustrating a Dynamic Central Configuration Protocol (DHCP) message. FIGURE 9 is a flow chart illustrating operations of a DHCP client-server model. FIGURE 10 is a flow diagram illustrating operations of a mobile IPvd system. FIGURE 11 is a flow diagram illustrating operations of a DHCPvd system. FIGURE 12 is a flow chart illustrating an Internet Protocol (IP) address setting procedure. FIGURE 13 is a structural diagram that illustrates a "Link Event" model and an "MIH Event" model according to one embodiment of the present invention. FIGURE 14 is a structural diagram illustrating a "Remote Link Event" model according to one embodiment of the present invention. FIGURE 15 is a structural diagram illustrating a "Remote MIH Event" model according to one embodiment of the present invention. FIGURE 16 is a structural diagram illustrating an "MIH command" model and a "Link command" model in accordance with one embodiment of the present invention. FIGURE 17 is a structural diagram illustrating a "remote MIH command" model according to one embodiment of the present invention. FIGURE 18 is a structural diagram illustrating a "Remote Link Command" model according to an embodiment of the present invention. FIGURE 19 is a structural diagram illustrating a protocol stack structure according to an embodiment of the present invention. FIGURE 20 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 21 is a flow diagram illustrating a IP address setting procedure according to one embodiment of the present invention. FIGURE 22 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 23 is a flow chart illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 24 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 25 is a structural diagram illustrating a protocol stack structure that includes a higher management entity according to one embodiment of the present invention. FIGURE 26 is a flow chart illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 27 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 28 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 29 is a flow diagram illustrating a IP address setting procedure according to one embodiment of the present invention. FIGURE 30 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. FIGURE 31 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention.

Best Mode for Carrying Out the Invention The present invention relates to providing mobility management protocol information to a multimodal mobile terminal to perform transfer between heterogeneous networks. Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Whenever possible, the same reference numbers will be used throughout the drawings to refer to the same or similar parts. Before describing the present invention, it should be noted that two methods are adapted to provide preferably a mobile terminal with mobility management protocol information supported by a new network. For example, a first method provides the mobile terminal with mobility management protocol information by an event service, and a second method provides the mobile terminal with mobility management protocol information by means of an information service. FIGURE 13 is a structural diagram illustrating a "Local Event" model and an "MIH Event" model according to an embodiment of the present invention, with reference to FIGURE 13, the MIH event is indicative of an event transmitted from the MIH to either the upper management entity or the upper layer, and corresponds to conventional event triggers. A link event is indicative of an event transmitted from a lower layer (i.e., a MAC layer or a physical layer (PHY)) to the MIH, and uses primitives for use in the individual MAC or physical interface layers. FIGURE 14 is a structural diagram illustrating a "Remote Link Event" model according to one embodiment of the present invention. With reference to FIGURE 14, if a lower layer contained in a local stack generates an event and transmits the event to the MIH contained in a local stack, the MIH of the local stack transmits the aforementioned event to the MIH of a remote stack. FIGURE 15 is a structural diagram illustrating a "Remote MIH Event" model according to a embodiment of the present invention. With reference to FIGURE 15, the MIH function of the local stack generates a remote MIH event, and transmits the remote MIH event to a corresponding MIH function contained in a remote stack. The corresponding MIH function transmits the received event to a higher management entity or a higher layer contained in a stack of the corresponding MIH function. FIGURE 16 is a structural diagram illustrating an "MIH command" model and a "Link command" model in accordance with one embodiment of the present invention. With reference to FIGURE 16, the MIH command is generated from the upper management entity or the upper layer, and then it is transmitted to the MIH function, so that it orders the MIH to perform a specific task. The link command is generated from the MIH function, and then it is transmitted to the lower layer, so that it instructs the lower layer to perform a specific task. FIGURE 17 is a structural diagram illustrating a "remote MIH command" model according to one embodiment of the present invention. With reference to FIGURE 17, the remote MIH command is generated from the upper management entity or the upper layer, and is then transmitted to the MIH function. The MIH function transmits the received MIH command to a corresponding MIH function contained in a remote stack. FIGURE 18 is a structural diagram illustrating a "Remote Link Command" model according to an embodiment of the present invention. With reference to FIGURE 18, the MIH function contained in the local stack generates a remote link command, and transmits the remote link command to a corresponding MIH function contained in a remote stack. The corresponding MIH function transmits the remote link command to the lower layer contained in the remote stack. The following preferred embodiments of the present invention relate to a method for providing a mobile terminal with mobility management protocol information through an event service. FIGURE 19 is a structural diagram illustrating a protocol stack structure according to an embodiment of the present invention. As shown in FIGURE 19, if a multimodal mobile terminal is transferred from an IEEE 802.11 network (ie, an old network) that supports a mobile IPv4 as a mobility management protocol, to an IEEE 802.16 network (it is say, a new network) that supports an MlPvd as a mobility management protocol, a method for transmitting mobility management protocol information supported by the IEEE network 802. 16 (i.e., the new network) uses the inventive event service of the present invention using a protocol stack structure. If a mobile terminal acting as a multimodal mobile terminal is transferred to a new network, the Media Access Control (MAC) layer of the mobile terminal includes information of mobility management protocol type supported by the new network in an event of MIH (eg, "Link_Available" or "Link_Up") and transmits the MIH event equipped with the mobility management protocol type information to an MIH function (also called an MIH layer). The MIH function then transmits a "Link_Up" event to a corresponding mobility management protocol (ie, MlPvd). The method for providing the mobile terminal with the mobility management protocol information via an event service adds new parameters to the "Link_Up", "Link_Available" or "IP_Renewal_Indication" event to provide the mobile terminal with new protocol information. mobility management supported by a new network. Accordingly, the mobile terminal recognizes a mobility management protocol supported by a new network by the newly added parameters mentioned above. The parameters before mentioned include information associated with a current mobility management protocol. However, if a new mobility management protocol is to be developed in the future, the information associated with the newly developed mobility management protocol can also be added to the aforementioned parameters when necessary. A newly added parameter, such as a bitmap of management protocol and mobility support type, is indicative of several types of mobility management protocol capable of being supported by the new network. For example, a bit of "1" indicates that a corresponding mobility management protocol can be provided from a network. FIGURE 20 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing the mobile terminal to receive new mobility management protocol information from a new network through a "Link_Available" event is shown. With reference to FIGURE 20, whether a mobile terminal equipped with a mobile IPv4 mobility management protocol and a mobile IPvd mobility management protocol accesses a network that supports the mobility management protocol of Mobile IPv4, and then transferred to a new network that supports the mobile IPvd mobility management protocol, a mobility management protocol support bitmap of the present invention is contained in the "Link_Available" event. Accordingly, a type of mobility management protocol supported by the new network is provided to the mobile terminal before the mobile terminal establishes a connection state with the new network (i.e., new link). Preferably, a new lower layer (new LL) or new MAC layer of the multimodal mobile terminal requires mobility management protocol information (e.g., mobile IPv6) from a new attachment point (POA) using a scan operation and other messages The new LL then includes the information acquired in the "Link_Available" event and transmits the "Link_Available" event that includes the information acquired to the MIH layer. Accordingly, if the MIH layer receives a "Link_Up" event indicating that the mobile terminal has established a connection establishment with a corresponding link when the MIH layer temporarily maintains the mobility management protocol information associated with a point corresponding link (POA), the MIH layer transmits an "Link Jp MIH" event to a protocol of corresponding mobility management (ie mobile IPv6) when referring to the above-mentioned maintained information. After this, a top layer or network layer of the mobile terminal performs a procedure for establishing IPv6 Service Address (CoA) to acquire a new CoA, and registers the new CoA with a local agent. The following table 11 shows exemplary parameters of the "Link_Available" event which includes a bitmap of the mobility management protocol support type.

[Table 11] FIGURE 21 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing a mobile terminal to receive mobility management protocol information from a new network through the "Link_Up" event is shown in FIGURE 21. Preferably, as shown in FIGURE 21, if a terminal mobile equipped with a mobile IPv4 mobility management protocol and a mobile IPv6 mobility management protocol accesses a network capable of supporting the mobility management protocol of mobile IPv4, and then it is transferred to a new network that supports the mobile IPv6 mobility management protocol, a mobility management protocol support bitmap of the present invention is contained in the "Link p" event. Accordingly, a type of mobility management protocol supported by the new network is provided to the mobile terminal before a network layer transfer procedure is executed. Preferably, a new lower layer (new LL), such as a MAC layer, of the multimodal mobile terminal establishes a connection state with a new link by means of a "Link Establishment Request / Response" message, so that the new LL acquires mobility management protocol information (e.g., MlPvd) from a new junction point (POA). After this, if the multimodal mobile terminal establishes a connection state with the new link, a "Link_Up MIH" event that includes the mobility management protocol information is transmitted to the MIH layer, the MIH layer then transmits. an event service corresponding to a corresponding mobility management protocol (MIPv6) when referring to the bitmap of the mobility management protocol support type of the "Link_Up" trigger event The following Table 12 shows exemplary parameters of the "Link_Up" event that includes the bitmap of mobility management protocol support type.

[Table 12] FIGURE 22 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing a mobile terminal to receive mobility management protocol information from a new network by the "IP_Renewal_Indication" event is shown in FIGURE 22. Preferably, as shown in FIGURE 22, if a terminal mobile equipped with a mobile IPv4 mobility management protocol and a mobile IPvd mobility management protocol accesses a network capable of supporting the mobile IPv4 mobility management protocol, and then it is transferred to a new network that supports the mobile IPv6 mobility management protocol, the mobility management protocol support type bitmap of the present invention is contained in the event of "IP_Renewal_Indication". Accordingly, a type of mobility management protocol supported by the new network is provided to the mobile terminal before the network layer transfer procedure is executed. Preferably, a new junction point (POA) of the mobile terminal receives a "Remote Link_Up MIH" event from the mobile terminal. The new POA then transmits an "IP_Renewal_Indication Link" event, which includes information from mobility management protocol provided from a network of the mobile terminal, to the MIH layer of the mobile terminal. The MIH layer of the mobile terminal then transmits an "IP_Renewal_Request" event to a corresponding mobility management protocol (MIPv6) when referring to the event mobility protocol support bitmap of the event "IP_Renewal_Indication link. " The preferred embodiment mentioned above shows an example in which the trigger signal of "IP_Renewal_Indication" after a link establishment between the mobile terminal and the new junction point (POA) is completed. However, with the proviso that the old binding point (POA) acquires IP address information from the new junction point (POA) using a signal message between MIH (ie, a signal message between MIH functions) , the old POA can provide the aforementioned trigger signal of "IP_Renewal_Indication" before the mobile terminal establishes a link with the new POA. The following Table 13 shows exemplary parameters of the "IP_Renewal_Indication" event including the bitmap of mobility management protocol support type.

[Table 13] FIGURE 23 is a flow chart illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing a mobile terminal to receive management protocol information from Mobility in a new network by means of the information service is shown in FIGURE 23. With reference to FIGURE 23, according to one embodiment of the present invention, a parameter similar to the bitmap of the protocol management support The aforementioned mobility is contained in a message of "Consultation List (Response) of Available Networks" (ie, a signal message between the MIH of the mobile terminal and the MIH of the current point of attachment (POA) or access point ), so that the mobile terminal can receive management and mobility protocol information supported by a corresponding network. FIGURE 24 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing a mobile terminal to receive mobility management protocol information from a new network through the information service is shown in FIGURE 24. With reference to FIGURE 24, according to one embodiment of the present invention, a parameter similar to the aforementioned mobility management protocol support type bitmap is contained in a message of "Query More (Response) Information about Networks of 902. and" (ie, a signal message between the MIH of the mobile terminal and the MIH of the current junction point (POA) or access point), so that the mobile terminal can receive mobility management protocol information supported by a corresponding network. FIGURE 25 is a structural diagram illustrating a protocol stack structure that includes a higher management entity according to one embodiment of the present invention. With reference to FIGURE 25, if a multimodal mobile terminal is transferred from an IEEE 802.11 network (i.e., an older network) that supports a mobile IPv4 mobility management protocol to an IEEE 802.16 network, (i.e. a new network) that supports an IPvd mobility management protocol, a method for transmitting mobility management protocol information supported by the aforementioned IEEE 802.16 network (i.e., the new network) and uses the inventive event service of the present invention is represented in FIGURE 25 using a protocol stack structure. If a mobile terminal acting as a multimodal mobile terminal is transferred to a new network, the MAC layer of the mobile terminal includes mobility management protocol type information supported by the new network at a predetermined event (eg, "Link_Available"). "or" Link_Up ", and transmits the event equipped with the information of type of administration protocol of aforementioned mobility to a higher management entity. The higher management entity then transmits the "Link_Up" event to a corresponding mobility management protocol (ie, MIPv6). The method for providing the mobile terminal with the mobility management protocol information via an event service adds new parameters to the "Link_Up", "Link_Available" or "IP_Renewal_Indication" event in order to provide the mobile terminal with new protocol information. mobility management supported by a new network. The mobile terminal recognizes that a mobility management protocol supported by a new network using the newly added parameters mentioned above. The aforementioned parameters include information associated with a current mobility management protocol. However, if a new mobility management protocol is to be developed in the future, the associated information may also be added to the aforementioned parameters as necessary. The newly added parameter (i.e., a bitmap of mobility management protocol support type) is indicative of several types of mobility management protocol capable of being supported by the new network. A bit of "1" indicates that a protocol of Corresponding mobility management can be provided from a network. FIGURE 26 is a flow chart illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, as shown in FIGURE 26, if a mobile terminal equipped with a mobile IPv4 mobility management protocol and a mobile IPvd mobility management protocol accesses a network capable of supporting the IPv4 mobility management protocol mobile, and then transferred to a new network to support the mobile IPvd mobility management protocol, a mobility management protocol support bitmap of the present invention is contained in a "Link_Available MIH" event. . Accordingly, a type of mobility management protocol supported by the new network is provided to the mobile terminal before the mobile terminal establishes a connection state with the new network (i.e., new link). According to a preferred embodiment shown in FIGURE 26, the upper management entity includes a top layer (eg, upper L3), a device manager, and a transfer control function. Preferably, a new lower layer (new LL), such as a new MAC layer, of the mobile terminal multimodal acquires mobility management protocol information (eg mobile IPv6) from a new junction point (POA) using a scan operation and other messages. The new MAC layer includes the information acquired in an MIH event of "Link_Available MIH", and transmits the MIH event of "Link_Available MIH" which includes the information acquired from the superior management entity through the MIH function. Preferably, the higher management entity transmits mobility management protocol information associated with a corresponding junction point (POA) to the upper layer, so as to instruct the corresponding mobility management protocol (i.e., mobile IPvd) to enter a state of "Link_Up". After this, a network layer of the mobile terminal performs an IPvd Service Address (CoA) establishment procedure to acquire a new CoA, and registers the new CoA with a local agent. FIGURE 27 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing the mobile terminal to receive mobility management protocol information associated with a new network through a "Link p" event is shown in FIGURE 27.

Preferably, as shown in FIGURE 27, if a mobile terminal equipped with a mobile IPv4 mobility management protocol and a mobile IPv6 mobility management protocol accesses a network capable of supporting the mobility management protocol of Mobile IPv4, and then transferred to a new network that supports the mobile IPvd mobility management protocol, a mobility management protocol support type bit map of the present invention is contained in the "Link_Up" event . Accordingly, a type of mobility management protocol supported by the new network is provided to the mobile terminal before the network layer transfer procedure is executed. In accordance with the preferred embodiment shown in FIGURE 26, the upper management entity includes an upper layer (eg, L3 and higher), a device manager, and a transfer control function. Preferably, a new lower layer (New LL), such as a new MAC layer, of the multimodal mobile terminal establishes a connection state with a new link by means of a "Link Establishment Request / Response" message, so which acquires mobility management protocol information (e.g., MIPv6) from a new junction point (POA). After this, if the multimodal mobile terminal establishes a connection state with the new link, the "Link_Up MIH" event includes the mobility management protocol information transmitted to the MIH layer. The MIH layer then transmits an event service corresponding to a corresponding mobility management protocol (MlPvd) by referring to the bitmap of the mobility management protocol support type of the "Link_Up" trigger event. FIGURE 28 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing the mobile terminal to receive mobility management protocol information associated with a new network by an "IP_Renewal_Indication" event is shown in FIGURE 28. Preferably, as shown in FIGURE 28, if a mobile terminal equipped with a mobile IPv4 mobility management protocol and a mobile IPvd mobility management protocol accesses a network capable of supporting the mobile IPv4 mobility management protocol, and is then transferred to a new network that supports the mobile IPvd, a bitmap of mobility management protocol support type of the present invention is contained in the event of "IP_Renewal_Indication". Therefore, one type of The mobility management protocol supported by the new network is provided to the mobile terminal before the network layer transfer procedure is executed. In accordance with the preferred embodiment shown in FIGURE 28, the upper management entity includes an upper layer (eg, L3 and higher), a device manager, and a transfer control function. Preferably, a new junction point (POA) of the mobile terminal receives a "Remote LinkJp MIH" event from the mobile terminal. The new POA then transmits an "IP_Renewal_Indication Link" event, which includes mobility management protocol information provided from a network of the mobile terminal, to the higher management entity. The upper management entity then transmits an "IP_Renewal_Request" event to a corresponding mobility management protocol (MIPv6) when referring to the bit map of the mobility management protocol support type of the event of "IP_Renewal_Indication link". The aforementioned preferred embodiment shows an example in which the "IP_Renewal_Indication" trigger signal occurs after a link establishment between the mobile terminal and a new junction point (POA) is completed. However, with the condition that the old POA acquires IP address information from the new POA using a signal message between MIH (ie, a signal message between MIH functions), the old POA may provide the aforementioned "IP_Renewal_Indication" trigger signal, before the mobile terminal establishes a link with the new one POA FIGURE 29 is a flow chart illustrating an IP address setting procedure according to an embodiment of the present invention. Preferably, a method for allowing the mobile terminal to receive mobility management protocol information associated with a new network by means of an information service is shown in FIGURE 29. As shown in FIGURE 29, a parameter similar to the map of Mobility management protocol support type bit mentioned above is contained in a "Query (Reply) List of Available Networks" message (that is, a signal message between the MIH of a mobile terminal and the MIH of a point current union (POA) or access point), and then transmitted to a higher management entity, so that the higher management entity can receive mobility management protocol information supported by a corresponding network. FIGURE 30 is a flow chart illustrating an IP address setting procedure of according to one embodiment of the present invention. Preferably, a method for allowing the mobile terminal to receive mobility management protocol information associated with a new network by the information service is shown in FIGURE 30. As shown in FIGURE 30, a parameter similar to the map of The aforementioned mobility management protocol support type bit is contained in a message of "Query More (Response) Information about 802. Networks and" (ie, a signal message between the MIH of the mobile terminal and the MIH of the current point of attachment (POA) or access point), and then it is transmitted to a higher management entity, so that the higher management entity can receive mobility management protocol information supported by a corresponding network. FIGURE 31 is a flow diagram illustrating an IP address setting procedure according to an embodiment of the present invention. With reference to FIGURE 31, similar to the aforementioned preferred embodiment of FIGURE 28, although the mobility management protocol type information is contained in an "IP_Renewal_Indication" trigger signal, the "IP_Renewal_Indication" trigger occurs after that the mobile terminal transmits a remote trigger signal of "Link_Going_Down" to an old POA. The old POA receives the remote activating signal of "Link_Going_Down" from the mobile terminal, acquires the information associated with IP associated with a new POA by means of the signal message between MIH, includes the associated information of IP acquired in the activating signal of "IP_Renewal_Indication ", and finally transmits the activating signal of" IP_Renewal_Indication "which includes the new associated IP information from POA to the mobile terminal. Although the aforementioned preferred embodiments of the present invention use mobile IPv4 and mobile IPvd mobility management protocols as examples, it should be noted that the scope or spirit of the present invention is not limited to only the mobile IPv4 and the mobile IPv4. Mobile IPvd, and that can also be applied to other segments and modifications. As apparent from the above description, a transfer method for a mobile communication system in accordance with the present invention previously provides a mobile terminal with mobility management protocol information supported by a new network through an event service or an information service, when a multimodal mobile terminal equipped with a plurality of mobility management protocols is transferred to a new interface network.

Therefore, the present invention greatly reduces a delay time consumed while the mobile terminal recognizes that it can no longer be operated by an old mobility management protocol of an old network in the new network, and establishes a Service Address (CoA) that uses a new mobility management protocol of the new network, so that the new CoA can be established quickly without generating a damaged package and extended service time. Although the present invention is described in the context of mobile communication, the present invention can also be used in any of the wireless communication systems that use mobile devices such as PDAs and laptop computers equipped with wireless communication capabilities. In addition, the use of certain terms to describe the present invention should not limit the scope of the present invention to a certain type of wireless communication system, such as UMTS. The present invention can also be applied to other wireless communication systems using different air interfaces and / or physical layers, for example, TDMA, CDMA, FDMA, WCDMA, etc. Preferred embodiments can be implemented as a method, apparatus or article of manufacture that uses standard programming and / or design techniques to produce software, firmware, hardware, or any combination thereof. The term "article of manufacture" as used herein refers to a code or logic implemented in hardware logic (e.g., an integrated circuit chip, Field Programmable Port Layout (FPGA), Integrated Application Specific Circuit (ASIC), etc.) or a computer-readable medium (for example, a magnetic storage medium (for example, hard disk drives, floppy disks, tapes, etc.), optical storage (CD-ROMs) , optical disks, etc.), volatile and non-volatile memory devices (eg, EEPROM, ROM, PROM, RAM, DRAM, SRAM, firmware, programmable logic, etc.). The code in the medium that can be read by computer is accessed and executed by a processor.The code in which the preferred modalities are implemented can also be accessible through a transmission medium or from a file server over a network.In such cases, the article of manufacture in which implied The code may comprise a transmission medium, such as a network transmission line, wireless transmission medium, signals propagating through space, radio waves, infrared signals, etc. Of course, those skilled in the art will recognize that many modifications can be made to this configuration without departing from the scope of the present invention, and that the The article of manufacture may comprise any means carrying information known in the art. It will be apparent to those skilled in the art that various modifications and variations may be made in the present invention without departing from the spirit or scope of the inventions. Thus, it is intended that the present invention cover the modifications and variations of this invention with the proviso that they fall within the scope of the appended claims and their equivalents. The above embodiments and advantages are exemplary only and will not be construed as limiting the present invention. The present teaching can be easily applied to other types of apparatus. The description of the present invention is intended to be illustrative, and does not limit the scope of the claims. Many alternatives, modifications and variations will be apparent to those with experience in the art. In the claims, clauses of means plus function are intended to cover the structure described herein as performing the narrated function and not only the structural equivalents but also the equivalent structures.

Industrial Applicability The present invention can be applied to communication systems that use mobile devices, such as PDA and laptop-type computers equipped with wireless communication capabilities. The present invention can also be applied to other wireless communication systems using different air interfaces and / or physical layers, for example, TDMA, CDMA, FDMA, WCDMA, etc.

Claims

CLAIMS 1. A method for providing mobility management protocol information to a mobile terminal, the method comprising: establishing a unified interface in a top layer of the mobile terminal to manage messages to and from at least one of a homogeneous network and a heterogeneous network; discover an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer; and informing the upper layer of the link accessible through the unified interface, wherein the step of informing the upper layer comprises providing the upper layer with mobility management protocol information of at least one of a homogeneous network and a heterogeneous network before establish a connection with the accessible link. The method of claim 1, further comprising requesting a scan of at least one of a homogeneous network and a heterogeneous network through the unified interface to determine the presence of the accessible link of at least one of a homogeneous network and a heterogeneous network to perform the transfer. 3. The method of claim 1, which also it comprises requesting information related to the accessible link of at least one of a homogeneous network and a heterogeneous network of an information server operationally connected to at least one of a homogeneous network and a heterogeneous network. The method of claim 3, wherein the requesting information step comprises requesting mobility management protocol information from at least one of a homogeneous network and a heterogeneous network. The method of claim 1, wherein the unified interface is a media-independent transfer function (MIHF) entity. The method of claim 1, wherein the upper layer comprises a higher management entity for managing homogeneous and heterogeneous network links associated with the mobile terminal. The method of claim 1, wherein the top layer comprises at least one administration or mobility protocol for administering a respective mobile terminal mobility method. 8. A method for providing mobility management protocol information to a mobile terminal, the method comprising: establishing a unified interface in a top layer of the mobile terminal to manage messages up to and from at least one of a homogeneous network and a heterogeneous network; establish a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer; and receiving in the upper layer information of the unified interface related to the established connection, wherein the step of receiving the information comprises receiving mobility management protocol information from at least one of a homogeneous network and a heterogeneous network. The method of claim 8, wherein the step of receiving the information comprises receiving in the upper layer a request from the unified interface to establish a network address of at least one of a homogeneous network and a heterogeneous network. The method of claim 9, wherein the network address is an Internet protocol address (IP) • The method of claim 8, wherein the unified interface is a media independent transfer function (MIHF) entity. The method of claim 8, wherein the upper layer comprises a higher management entity for managing homogeneous network links and heterogeneous associated with the mobile terminal. The method of claim 8, wherein the top layer comprises at least one mobility management protocol for administering a respective mobile terminal mobility method. The method of claim 8, wherein the step of receiving the information comprises providing the upper layer with mobility management protocol information in a specific mobility management protocol related to the information. The method of claim 9, further comprising: providing the upper layer with mobility management protocol information by providing information to a specific mobility management protocol related to the information; and establishing the network address for at least one of a homogeneous network and a heterogeneous network when the mobility management protocol information is provided to the specific mobility management protocol. 16. The method of claim 9, further comprising establishing the network address for at least one of a homogeneous network and a heterogeneous network. 17. A method to provide information of mobility management protocol in a mobile terminal, the method comprising: establishing a unified interface in a top layer of the mobile terminal to manage messages to and from at least one of a homogeneous network and a heterogeneous network; establish a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer; and informing the upper layer of the established connection with the link accessible through the unified interface, where the step of informing the upper layer comprises providing the upper layer with mobility management protocol information from at least one of a network homogeneous and a heterogeneous network. 18. The method of claim 17, wherein the unified interface is an independent media transfer and function entity (MIHF). The method of claim 17, wherein the upper layer comprises a higher management entity for managing homogeneous and heterogeneous network links associated with the mobile terminal. The method of claim 17, wherein the top layer comprises at least one protocol of mobility management to administer a respective mobile terminal mobility method. The method of claim 17, wherein the step of providing the upper layer with mobility management protocol information comprises providing the information to a specific mobility management protocol related to the information. 22. A method for providing mobility management protocol information to a mobile terminal, the method comprising: establishing a unified interface to a top layer of the mobile terminal to manage messages to and from at least one of a homogeneous network and a heterogeneous network; establish a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network to perform transfer; and receiving in the upper layer a request from the unified interface to establish a network address for at least one of a homogeneous network and a heterogeneous network, wherein the step of receiving a request to establish a network address comprises providing the layer superior with mobility management protocol information from at least one of a homogeneous network and a heterogeneous network. 23. The method of claim 22, wherein the network address is an Internet protocol address (IP) • 24. The method of claim 22, wherein the unified interface is a media independent transfer function entity (MIHF). The method of claim 22, wherein the upper layer comprises a higher management entity for managing homogeneous and heterogeneous network links associated with the mobile terminal. 26. The method of claim 22, wherein the top layer comprises at least one mobility management protocol for administering a respective mobile terminal mobility method. The method of claim 22, wherein the step of providing the upper layer with the mobility management protocol information comprises providing the information to a specific mobility management protocol related to the information. The method of claim 27, further comprising setting the network address for at least one of a homogeneous network and a heterogeneous network when the mobility management protocol information is provided to the specific mobility management protocol. 29. The method of claim 22, further comprising setting the network address for at least one of a homogeneous network and a heterogeneous network. 30. A mobile terminal for receiving mobility management protocol information, the mobile terminal comprises: a unified interface to a top layer of the mobile terminal for managing messages to and from at least one of a homogeneous network and a heterogeneous network; means for discovering an accessible link of at least one of a homogeneous network and a heterogeneous network for performing transfer; and means for informing the upper layer of the link accessible through the unified interface, wherein the means for informing the upper layer comprises means for providing the upper layer with the mobility management protocol information of at least one of a network homogeneous and a heterogeneous network before establishing a connection with the accessible link. 31. A mobile terminal for receiving mobility management protocol information, the mobile terminal comprises: a unified interface in a top layer of the mobile terminal for managing messages to and from at least one of a homogeneous network and a heterogeneous network; means for establishing a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network for performing transfer; and means for receiving in the upper layer information of the unified interface related to the established connection, wherein the means for reporting comprises means for receiving mobility management protocol information from at least one of a homogeneous network and a heterogeneous network. 32. A mobile terminal for receiving mobility management protocol information, the mobile terminal comprising: a unified interface in a top layer of the mobile terminal for managing messages to and from at least one of a homogeneous network and a heterogeneous network; means for establishing a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network for performing transfer; and means for informing the upper layer of the established connection with the link accessible through the unified interface, wherein the means for informing the upper layer comprises means for providing the upper layer with the mobility management protocol information of at least one of a homogeneous network and a heterogeneous network. 33. A mobile terminal for receiving mobility management protocol information, the mobile terminal comprising: a unified interface in a top layer of the mobile terminal for managing messages to and from at least one of a homogeneous network and a heterogeneous network; means for establishing a connection with an accessible link of at least one of a homogeneous network and a heterogeneous network for performing transfer; and means for receiving in the upper layer a request from the unified interface to establish a network address for at least one of a homogeneous network and a heterogeneous network, wherein the means for receiving a request to establish a network address comprises to provide the top layer with the mobility management protocol information of at least one of a homogeneous network and a heterogeneous network.