KR200413066Y1 - Device for passing ongoing communication sessions between heterogeneous networks - Google Patents

Abstract

A procedure for handing over an ongoing communication session between a mobile station (MS) and a communicator node (CoN) from a first path comprising a first type of first network to a second path comprising a second type of second network is provided. An apparatus for triggering is provided. The communication session continuity conveys communication session context information when handover is urgent from the network component of the first network path to the network component of the second network path, a second path is established and an ongoing communication session is directed to the second network path. This is maintained by sending downlink and uplink signals through the network components of both the first and second network paths until they can be handed over. The context information includes session communication parameters, so that the second network path can allocate resources and establish routing between the MS and CoN.

Description

Apparatus for transferring on-going communication sessions between heterogeneous networks {APPARATUS FOR TRANSFER OF AN ONGOING COMMUNICATION SESSION BETWEEN HETEROGENEOUS NETWORKS}

1A, 1B and 1C are in communication with the mobile station MS from via a first path comprising a first network NW1 to via a second path comprising a second network NW2 according to the present invention. Schematic diagram illustrating a process of handing over a communication session between child nodes (CoNs).

2 is a flow chart showing the handover procedure of Figure 1 in accordance with the present invention.

3 shows a communication session between an MS and a CoN via a first path including a first network NW1 connected to a general network GN via a first gateway GW1 and then to a CoN. A diagram illustrating a general purpose networking scenario.

4A, 4B and 4C are schematic diagrams showing handover of a communication session from an 802.3 LAN to an 802.X WLAN in accordance with the present invention.

5A, 5B and 5C are schematic diagrams showing handover from an 802.X WLAN to an 802.3 LAN in accordance with the present invention.

6A, 6B and 6C are schematic diagrams showing handover from an 802.X WLAN to a 3GPP cellular network in accordance with the present invention.

7A, 7B, 7C and 7D are schematic diagrams showing handover from a 3GPP cellular network to an 802.X WLAN in accordance with the present invention.

<Explanation of symbols for the main parts of the drawings>

10: mobile station (MS)

20: operator node (CoN)

30: first network (NW1)

40, 50, 70, 80: link

60: second network (NW2)

The present invention relates to the field of wireless communication. More specifically, the present invention provides a communication session between heterogeneous network types, for example, any of various cellular network types, wireless IEEE 802 compliant network types, and wired IEEE 802 compliant network types. Relates to conveying communication session context information to facilitate handover of the device.

Wired and wireless communication systems are well known. Recently, the widespread deployment of different types of networks has created locations that enable access to more than one type of network. Communication devices incorporating two or more different network access technologies within a single communication device have been developed. For example, a communication device capable of communicating over one or more types of wired and / or wireless standards, such as IEEE 802 compliant wired local area network (LAN) and wireless local area network (WLAN), and code division multiple access (e.g. Cellular technologies such as CDMA), Global System for Mobile Communications (GSM), and General Packet Radio System (GPRS) standards. Communication through each standard is called a communication mode, and devices capable of communicating through one or more communication standards are called multi-mode devices.

Existing systems that support integrating two or more network access technologies in one device generally do not provide inter-working between different access technologies. In other words, a communication device that supports multimode functionality, unless there are several, cannot provide interworking between the other access technologies required to enable the transfer of an ongoing communication session between different access technologies. . Accordingly, there is a need for an apparatus that enables full handover-type functionality from one type of network to another without disrupting on-going communication sessions. For example, a user should be able to initiate a communication session that has advantages at high data rates such as video calls in a cellular network, but if a WLAN hotspot with greater capacity is used by a user entering a service area, for example If possible, the video call should be able to switch to the WLAN. If, during the call, the WLAN becomes unavailable to a user outside of its service area, the session must be able to switch back to the cellular network.

The present invention provides a convention, protocol for determining how related context information can be transferred between heterogeneous communication systems to facilitate handover of an ongoing communication session from a first network to another type of second network. And methods.

A method and apparatus are provided for facilitating mobility in handling multimode communication devices over other communication technologies by transmitting context information about an ongoing communication session over a heterogeneous network. The present invention is intended to trigger the transfer of communication session context information and to trigger a handover procedure from a first network path comprising a first network of a first type to a second network path comprising a second type of another network. In the specification, a message called a media independent handover-handover prepare (MIH_HO_PREPARE) message is used. The MIH_HO_PREPARE message can also be used to trigger Mobile Internet Protocol (MIP) procedures if necessary. It should be understood here that the MIH_HO_PREPARE message is not limiting but is merely used as a convenient way to refer to a message that triggers the transfer of context information and handover procedures.

In one embodiment, the handover of a multimode mobile station (MS) is between a wireless system and a wired system, for example between a wireless local area network (WLAN) and a wired local area network (LAN). In this embodiment, the handover procedure is preferably triggered by a prompt in the MS when establishing or destroying the physical wired connection.

In another embodiment, handoff occurs between other wireless systems, for example between a WLAN and a cellular network. In one such embodiment, the handover procedure is triggered by a prompt from within the MS, such as when the signal strength of an active connection is below a predetermined threshold. Alternatively, during a communication session, the MS may monitor the availability of one or more other network types and trigger a handover procedure based on the strength of the signal from such a network that crosses a predetermined threshold. For example, the handover procedure may be triggered by a prompt from within the MS when the MS detects that a more preferred network type is available. In another embodiment, the handover procedure is triggered by a prompt from the active network to the MS, for example when an MS with an active cellular connection enters a coverage area of a WLAN hotspot. In this embodiment, the cellular network may track the location of the MS, compare that location with a known location of the WLAN hotspot, and notify the MS when the location is within range of the hotspot. To extend MS battery life, there is an advantage to having an active network that notifies the MS when other networks are available, instead of having an MS monitor for those other networks.

In all embodiments, after the handover decision is made, the media independent handover component of the MS generates a MIH_HO_PREPARE message, which causes the MS to connect to the second network, and the second from the network component of the first network path. The network component of the network path triggers a handover of the communication session context information and reestablishes the communication session over a second network, including the second network. The context information may include header compression context, point-to-point protocol (PPP) context, user data, and the like. If Mobile IP (MIP) is involved in the handover, the MIH_HO_PREPARE message may also trigger the MIP procedure.

More specific details of the present invention will be understood from the following description with reference to the accompanying drawings, which are presented by way of example.

The present invention is described with reference to the drawings in which like reference numerals refer to like elements throughout. The term mobile ststion (MS) as used herein is not limited to user equipment and includes one type, including mobile stations, mobile subscriber units, pagers, portable computers, or other types of devices capable of operating in a wired or wireless networking environment. A multimode mobile station capable of operating over a network of more than one type.

The term network (NW) as used herein refers to any network with which the MS communicates to access network services, such as conducting a communication session with a correspondent node (CoN). NW is not limited to all types of wired and wireless networks, but all types of IEEE 802 based compliant networks such as 802.3, 802.11 and 802.16 compliant networks and all types such as 3GPP, GSM and GPRS compliant networks. Cellular network.

Between a mobile station (MS) and a communicator node (CoN), from a first network path comprising a first network using a first communication standard to a second network path comprising a second network using a second communication standard. A method and apparatus for delivering an ongoing communication session are described. After the handover decision is made, forwarding the on-going communication session means that the MS makes a connection with the second network, passing communication session context information from the network component of the first network path to the network component of the second network path, It is necessary to continue the ongoing communication session through the second network path. Handover typically also includes performing communication during a temporary period over network components of both the first and second network paths before the communication session is established over the second network path.

1A, 1B, and 1C illustrate an example of utilizing the present invention in a general purpose multimode networking handover scenario. In FIG. 1A, a communication session is performed between a mobile station (MS) 10 and a communicator node (CoN) 20. The communication session consists of communication signals sent over the first network (NW1) 30 between the MS 10 and the CoN 20. The MS 10 is communicatively coupled to the first network 30 via a communication link 40, and the CoN 20 is communicatively coupled to the first network 30 via a communication link 50. The link 40, the first network 30, and the link 50 form a first signal path (path 1) between the MS 10 and the CoN 20. Also shown in dashed lines is a second network (NW2) 60 that uses a different communication standard than the first network 30, a potential link 70 between the MS 10 and the second network 60, and CoN ( 20 is a potential link 80 between the second network 60. The link 70, the second network 60, and the link 80 form a second signal path (path 2) between the MS 10 and the CoN 20.

In FIG. 1B, a decision is made to handover an on-going communication session from via path 1 to via path 2. The handover decision may be made by the MS 10 itself, or the handover decision may be made by another entity and sent to the MS 10. For example, an apparatus within or in communication with the first network may make a handover decision and send the handover decision to the MS 10 over the link 40.

If the MS 10 makes a handover decision, this decision may be made because the link 40 is unavailable. For example, if the link 40 is a wired link provided over a network cable and the network cable is unplugged from the MS 10, the MS 10 determines to hand over the ongoing communication session to path 2. . Alternatively, the MS 10 may make a handover decision because the upper link 70 is available. For example, if the link 40 is a wireless link and the link 70 is a wired link established by plugging a network cable into the MS 10, the MS 10 hands over the communication session to path 2. You can decide to. Alternatively, the link 70 may be a wireless link that is higher and available to the link 40 as occurs when the MS 10 moves to the service area of the second network. The MS 10 may be aware of the availability of the link 70 by monitoring the availability of a network, such as a second network, or the MS 10 may be serviced by a second network, such as by the first network. You may be notified that you have moved to the area.

Alternatively, the network entity may make a handover decision and send the decision to the MS 10 via, for example, the link 40. This determination can be made, for example, to better manage network resources.

When a decision is made to handover the communication session via path 2, the media independent handover component (MIHC) of the MS 10 generates a MIH_HO_PREPARE message, which indicates that the mode component of the MS 10 is selected from the second network ( 60, and the second network 60 is connected to CoN 20 to form path 2. The MIH_HO_PREPARE message also allows a link 90 to be formed between the first network 30 and the second network 60 and allows communication session context information to be passed from the first network 30 to the second network 60. In turn, the ongoing communication session is established and continues through path 2 based on the context information. The context information may include header compression context, point-to-point protocol (PPP) context, user data, and the like. In addition, while the link 80 is established between the second network 60 and the CoN 20 and path 2 is ready to continue the communication session, the downlink from the first network 30 to the MS 10 ( DL) signals may be sent from the first network 30 to the MS 10 via the link 90, the second network 60, and the link 70. Alternatively, the DL signal may be stored in the first network 30 and a copy of it may be sent to the MS 10 via the link 90, the second network 60 and the link 70. The DL signal may be sent from the first network to the MS 10 in this manner until an ongoing communication session is established over path 2, or alternatively for a predetermined length of time. Optionally, the uplink (UL) signal is configured from the MS 10 via the path 70, the second network 60, and the link 90 to the first network (1) until an ongoing communication session is established through path 2. 30) and then to CoN 20 as well.

In FIG. 1C, path 2 including the link 70, the second network 60, and the link 80 is established and communicates the communication session context information transmitted from the first network 30 to the second network 60. To continue an on-going communication session over path 2 between the MS 10 and the CoN 20.

2 is a block diagram summarizing the handover process 100. Initially, at step 110, MS 10 and CoN 20 execute a communication session via path 1. In step 120, a decision is made to handover the communication session over path 2. The media independent handover (MIH) component of the MS 10 sends a MIH_HO_PREPARE message to the mode component of the MS 10 capable of communicating with the second network 60 in step 130. The MIH_HO_PREPARE message also triggers a subsequent procedure to hand over the ongoing communication session to path 2 and the session continues. In step 140, the MS 10 is connected to the second network 60, and establishes a link 80 between the second network 60 and the CoN 20 to form path 2. In step 150, the procedures triggered by the MIH_HO_PREPARE message cause the link 90 to be formed between the first network 30 and the second network 60, and the first network 30 sends the session context information to the second network. (60). In step 160, the first network 30 sends the context information to the second network 60, optionally the first network 30 causes the DL signal to be sent to the second network, and the second network then The DL signal is sent to the MS 10. The UL signal may also optionally be sent to the first network 30 by the second network 60, which is configured to maintain the CoN 20 until the ongoing communication session is handed over path 2. Sends a UL signal to In step 170, the second network establishes an ongoing communication session between the MS 10 and the CoN 20 via path 2 using the context information. The session then continues via path 2.

3 illustrates the present invention in which a universal network (GN) 300, such as the Internet or a cellular core network, exists between the first network 30 and the CoN 20 and also between the second network 60 and the CoN 20. It illustrates an embodiment of. The first network 30 may be connected to the GN 300 via a first gateway (GW1) 310, and the second network 60 may be connected to the GN 300 via a second gateway (GW2) 320. Can be connected to. In addition, in FIG. 3, the first mode component MC1 12 in the MS 10 is in communication with the first network 30 via a link 40, and the second mode component MC2 14 is linked. It is shown that the communication with the second network 60 through 70. Also shown at MS 10 is a Media Independent Handover Component (MIHC) 16 that generates a MIH_HO_PREPARE message.

In FIG. 3, the first mode component 12 is initially communicatively coupled with the first network 30, whereby the MS 10 allows the first network 30, the first gateway 310, and the general purpose. A communication session is executed with CoN 20 via path 1 including network 300. A decision is made to hand over the communication session to path 2 including the second network 60, the second gateway 320, and the general purpose network 300. Handover is initiated by the MIHC 16 sending a MIH_HO_PREPARE message to the second mode component 14, where the second mode component 14 establishes a connection with the second network 60 and establishes path 2. Trigger The MIH_HO_PREPARE message also triggers the transfer of context information from at least one network component of path 1 to at least one network component of path 2; Optionally sending a DL signal from at least one network component of path 1 to at least one network component of path 2 so that the DL signal is sent to MS 10; Optionally sending an UL signal from at least one network component of path 2 to at least one network component of path 1 so that the UL signal is sent to CoN 20; The transferred context information is used to continue an on-going communication session over path 2 between the MS 10 and the CoN 20. In an actual implementation, one or more of the first network, the first gateway, the second network, the second gateway, and the general purpose network may include multiple network components. The network components of path 1 and path 2 related to carrying context information and sending DL and UL signals will depend on the specific configuration of each implementation. The following describes an exemplary embodiment.

4A, 4B and 4C show the MS 10 from path 1 in which the ongoing communication session between the MS 10 and the CoN 20 includes a wired connection between the MS 10 and the 802.3 network in accordance with the present invention. Exemplary implementations are handed over to path 2 including a wireless connection between a wireless network and an 802.X wireless network. In FIG. 4A, the 802.3 mode component 412 of the MS 10 is initially communicatively coupled to an 802.3 access network (AN) 430 via a network cable 440, thereby allowing the MS 10 to 802.3. Establish a communication session with the CoN 20 via a route 1 including an access network (AN) 430, an 802.3 access gateway (AG) 410 including an 802.3 access router (AR) (not shown), and the Internet 400; Run Alternative route 2 (indicated by the dotted lines) includes an 802.X access network 460, an 802.X access gateway 420 including an 802.X access router (not shown), and the Internet 400.

In FIG. 4B, a decision is made to handover the communication session over path 2. Handover is initiated, for example, by unplugging network cable 440 from MS 10 while MS 10 is located in the service area of 802.X access network 460. The handover is initiated by the MIHC 16 sending a MIH_HO_PREPARE message to the 802.X mode component 414 of the MS 10, where the 802.X mode component 414 is the 802.X access network 460. Establish a connection with, and associate and authenticate at the 802.X access gateway 420.

MS 10 obtains the IP address of 802.X access gateway 420. The MS 10 then triggers a context transfer procedure and a data transfer procedure from the 802.3 access gateway 410 to the 802.X access gateway 420. If Mobile IP (MIP) is used and the context is passed to 802.X access gateway 420, data is sent from 802.3 access gateway 410 to 802.X access gateway 420 and to MS 10. This allows the MS 10 to receive user data before a new care of address (CoA) is negotiated with the 802.X access router. The MS 10 negotiates with the new CoA using a conventional MIP message. When a new CoA is ready and a connection is established, the user data path can be switched from CoN 20 to 802.X access gateway 420. The old CoA may then be de-registered. If layer 3 soft handover (L3SH) is used, the context may be activated after a new connection is established from the 802.X access router to the CoN 20. 4C illustrates an ongoing communication session between the MS 10 and the CoN 20 after the ongoing communication session is handed over through path 2. FIG.

5A, 5B and 5C show that the on-going communication session between the MS 10 and the CoN 20 is a wireless connection between the MS 10 and the 802.X access network (AN) 460 according to the present invention. Exemplary implementations are handed over from path 1 including 470 to path 2 including the wired connection between MS 10 and 802.3 access network 430. In FIG. 5A, the 802.X mode component 414 of the MS 10 is initially connected to the 802.X access network 460 via the air interface 470, whereby the MS 10 is connected to the 802.X. A communication session is established with CoN 20 via path 1 including an access network 460, an 802.X access gateway (AG) 420 including an 802.X access router (AR) (not shown), and the Internet 400. Run Route 2, shown in dashed lines, includes an 802.3 access network (AN) 430, an 802.3 access gateway (AG) 410 including an 802.3 access router (AR) (not shown), and the Internet 400.

In FIG. 5B, a decision is made to handover the communication session over path 2. Handover may be initiated, for example, by plugging in network cable 440 to MS 10. The handover is initiated by the MIHC 16 sending a MIH_HO_PREPARE message to the 802.3 mode component 412 of the MS 10, where the 802.3 mode component 412 establishes a connection with the 802.3 access network 430, The 802.3 access gateway 410 is associated and authenticated.

MS 10 obtains the IP address of 802.3 access gateway 410. The MS 10 then triggers a context transfer procedure and a data transfer procedure from the 802.X access gateway 420 to the 802.3 access gateway 410. If mobile IP is used and the context is passed to 802.3 access gateway 410, data may be sent from 802.X access gateway 420 to 802.3 access gateway 410 and to MS 10. This allows the MS 10 to receive user data before the new Care of Address (CoA) is negotiated with the 802.3 access router. The MS 10 negotiates with the new CoA using a conventional MIP message. When a new CoA is ready and a connection is established, the user data path can be switched from CoN 20 to 802.3 access gateway 410. The old CoA may then be de-registered. If layer 3 soft handover (L3SH) is used, the context may be activated after a new connection from the 802.3 access router to the CoN 20 is established. 5C shows an ongoing communication session between the MS 10 and the CoN 20 after the ongoing communication session is handed over through path 2. FIG.

6A, 6B and 6C show that an on-going communication session between the MS 10 and the CoN 20 establishes a wireless connection 470 between the MS 10 and the 802.X access network 460 according to the present invention. Illustrating an example implementation that is handed over from path 1 including path 1 through path 2 (indicated by dashed lines) that includes a wireless connection between the MS 10 and the 3GPP base transceiver station (BTS) 610. will be. In FIG. 6A, the 802.X mode component 414 of the MS 10 is initially communicatively coupled to the 802.X access network (AN) 460 via the air interface 470, whereby the MS ( 10) 802.X access network 460, wireless access gateway (WAG) 660, packet data gateway (PDG) 670, 802.X gateway GPRS support node (GGSN) 680 and cellular core network ( A communication session is established with CoN 20 via path 1 including CN) 600. Path 2, shown in dashed lines, includes a BTS 610, a radio network controller (RNC) 630, a serving GPRS support node (SGSN) 640, a 3GPP GGSN 650, and an SN 600. A decision is made to handover the communication session from over path 1 to over path 2. Handover may be initiated, for example, by an MS moving out of the coverage area of 802.X access network 460. Handover is initiated by the MIHC 16 sending a MIH_HO_PREPARE message to the 3GPP mode component 612 of the MS 10.

In FIG. 6B, the MS 10 initiates cell selection and performs routing region update, whereby the 3GPP component 612 establishes communication coupling with the BTS 610, the RNC 620, and the SGSN 640. To establish. The MS 10 causes the SGSN 640 to request delivery of communication session context information from the PDG 670 to the SGSN 640. PDG 670 sends context information of both UL and DL flows to SGSN 640 including the Packet Data Protocol (PDP) context. PDG 670 then stops sending DL packets to MS 10. PDG 670 buffers the DL packet, establishes a Gateway Tunneling Protocol (GTP) that tunnels to SGSN 640, and sends a copy of each buffered packet towards SGSN 640. This is done for a period of time, or until SGSN 640 is ready to process DL packets from 3GPP GGSN 650.

In FIG. 6C, the PDP context is updated at 3GPP GGSN 650 and a new GTP tunnel is established between 3GPP GGSN 650 and SGSN 640. This allows the communication session to be successfully activated in path 2 and the ongoing communication session continues between the MS 10 and the CoN 20. The 802.X radio connection is then released.

7A, 7B, 7C and 7D show that an ongoing communication session between the MS 10 and the CoN 20 establishes a wireless connection 470 between the MS 10 and the 3GPP BTS 610 according to the present invention. Exemplary implementations are handed over from path 1 including path 1 through path 2 (indicated by dashed lines) that includes a wireless connection between MS 10 and 802.X access network 460. In FIG. 7A, the 3GPP component 612 of the MS 10 is initially communicatively coupled to the BTS 610 via an air interface, whereby the MS 10 is connected to the BTS 610, radio network controller (RNC). 630, a serving GPRS support node (SGSN) 640, a 3GPP GGSN 650, and a path 1, including path 600, to execute a communication session with CoN 20. Path 2 shown in dashed lines includes an 802.X access network 460, a WAG 660, a PDG 670, an 802.X GGSN 680, and a CN 600. A decision is made to handover the communication session from over path 1 to over path 2. The handover may be initiated, for example, by the MS moving to the service area of 802.X AN 460 and notified by BTS 610 that the 802.X network is available, and the 802.X component 414. Scans the 802.X network. Alternatively, the 802.X component 414 may perform periodic scanning when continuously or when prompted by system information received from the 3GPP mode component 612. Handover is initiated by MIHC 16 sending a MIH_HO_PREPARE message to 3GPP component 612.

In FIG. 7B, MS 10 performs 802.X system association and authentication directed to 802.X access network 460, whereby 802.X component 414 causes 802.X access network 460. Establish a communication coupling with the WAG 660, the PDG 670, the 802.X GGSN 680, and the CN 600. The MS 10 constructs a fully qualified domain name (FQDN) using the WLAN identity and associated public land mobile network (PLMN), and uses the domain name through a Domain Naming System (DNS) query. The relevant address of the PDG 670 is obtained. MS 10 establishes a tunnel from this 3GPP component to PDG 670 via BTS 610, RNC 620 and SGSN 640 using this address and for example Layer 2 Tunneling Protocol (L2TP). . When the tunnel has been established, the MS 10 performs a routing area update towards the PDG 670. The routing data update received at PDG 670 triggers a context transfer request from PDG 670 towards SGSN 640. Context information, including PDP context information, is taken from RNC 620 and sent to PDG 670 via SGSN 640. Both UL and DL context information are sent. After the PDP context is delivered, the RNC 620 stops sending DL packets towards the MS 10. The RNC 620 buffers the DL packet.

In FIG. 7C, when the PDG 670 is ready to initiate packet processing, the RNC 620 establishes a new GTP tunnel towards the PDG 670 and copies the buffered packet through the SGSN 640 to the PDG ( 670). PDG 670 sends the DL packet to 802.X mode component 414. This is done for a fixed time period.

In FIG. 7D, the PDP context is updated at 802.X GGSN 680 and a new GTP tunnel is established between PDG 670 and GGSN 680. Packets can then be sent directly from the 802.X GGSN 680 to the PDG 670. This allows the communication session to be successfully activated in path 2 and the ongoing communication session continues between the MS 10 and the CoN 20. The 3GPP radio connection may then be released.

Other scenarios are possible, such as a handover between an IEEE 802.3 wired network and a cellular network, which is within the scope of the present invention. Although the features and elements of the present invention have been described as preferred embodiments of a particular combination, each feature or element may be used alone (without other features and elements of the preferred embodiments), or other features and elements of the present invention may be used. It can be used in various combinations with or without.

According to the present invention, relevant context information can be efficiently transferred between heterogeneous communication systems to facilitate handover of an ongoing communication session from the first network to another type of second network.

Claims (7)

A multimode mobile station (MS) having at least two mode components, wherein the MS uses a second communication standard from a first network path including a plurality of network components in which communication session context information uses a first communication standard. A multimode mobile station configured to make a handover of an ongoing communication session with a communicator node (CoN) defined up to a second network path including A first mode component configured to communicate using a first communication standard; A second mode component configured to communicate using a second communication standard; A media independent handover component (MIHC), wherein the MIHC comprises: Send a message to the second mode component to establish a second network path, Establish a communication connection between the network component of the first network path and the network component of the second network path, Communicate communication session context information from the first network path to a second network path via the communication connection, Send an uplink signal and receive a downlink signal through the second mode component, Thereby causing the on-going communication session to be handed off from the first mode component and the first network path to the second mode component and the second network path. 2. The multimode mobile station of claim 1, wherein the message also triggers a mobile IP (MIP) procedure. 2. The multimode mobile station of claim 1, wherein the message stores the downlink (DL) signals in a network component of a first path. 2. The multimode mobile station of claim 1, wherein the message sends DL signals from a network component of a first path to a second mode component through a network component of a second path. 5. The multimode mobile station of claim 4, wherein DL signals are sent from a network component of the first path through a network component of the second path for a predetermined time period. 5. The method of claim 4, wherein the DL signals are sent from the network component of the first path to the second mode component through the network component of the second path until the communication session is established over the second path, wherein the communication signals are generated. A multimode mobile station that is sent only over two paths. 5. The method of claim 4, wherein the first mode component is an IEEE 802.3 compliant network, an IEEE 802.11 compliant network, an IEEE 802.16 compliant network, a GSM network, a GPRS network, a 3GPP-based W-CDMA FDD network, a 3GPP-based TDD. Network, a 3GPP-based TD-SCDMA network, a 3GPP2-based CDMA2000 network, a 3GPP2-based 1x network, a 3GPP2-based EV-DO network, or a 3GPP2-based EV-DV network, the second mode component being an IEEE 802.3 compliant network, IEEE 802.11 compliant network, IEEE 802.16 compliant network, GSM network, GPRS network, 3GPP based W-CDMA FDD network, 3GPP based TDD network, 3GPP based TD-SCDMA network, 3GPP2 based CDMA2000 network, 3GPP2 based 1x network And a 3GPP2-based EV-DO network or a 3GPP2-based EV-DV network.

Images