Seamless network interface selection, handoff and management in multi-IP network interface mobile devices

• US 7,835,743 B2
• Filed: 08/03/2005
• Issued: 11/16/2010
• Est. Priority Date: 08/03/2005
• Status: Active Grant

• Current Assignee: Telcordia Legacy Inc.
• Original Assignee: Telcordia Technologies Incorporated (Telefonaktiebolaget LM Ericsson), Toshiba Corporation
• Inventors: Baba, Shinichi, Tauil, Miriam, Byungsusk, Kim, Zhang, Tao, Kodama, Toshikazu
• Primary Examiner(s): Taylor; Barry W
• Application Number:
  US11/196,517
• Publication Number:
  US 20070030826A1
• Time in Patent Office: 1,931 Days
• Field of Search: 455/436, 455/437, 455/438
• US Class Current: 455/436
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04W 36/0011 for data sessions of end-to-end connection
• CPC Class Codes: H04W 36/14 Reselecting a network or an air interface
• CPC Class Codes: H04W 36/24 Reselection being triggered by specific parameters
• CPC Class Codes: H04W 36/36 by user or terminal equipment
• CPC Class Codes: H04W 36/385 of the core network
• CPC Class Codes: H04W 48/18 Selecting a network or a communication service
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

A Multi-Interface Mobility Management (MIMM) client is provided on a mobile Multi-Interface Device (MID) to support seamless network connectivity and switching of the MID. The MIMM client communicates with a MIMM Server. The MIMM Server collects information from MIMM Clients and provides information to the MIMM Clients pertaining to the network(s) to which the mobile MID has access, such as information concerning the availability of a network, the quality of network connectivity, etc. The MIMM Client is responsible for determining whether and when a handoff or roaming operation should be initiated by the mobile MID, and which network interface the mobile MID should use after the handoff/roam operation has been completed. The MIMM Client also is responsible for performing mobility-related functions that are required prior and subsequent to the handoff/roam operation. The MIMM Client uses the information received from the MIMM Server in order to make these determinations.

Claims

1. A mobile multi-interface device (MID) having a plurality of network interfaces, comprising:

a multi-interface mobility management (MIMM) client residing on said MID, said MIMM client including an interface monitor that monitors status of said plurality of network interfaces, and a mobility manager that determines which one of said plurality of network interfaces should be used by said MID and when said MID should switch from one interface to another, using information from said interface monitor;

wherein said plurality of network interfaces provide access to a plurality of subnets, and said MIMM client further includes a plurality of virtual subnet devices, with each of said virtual subnet devices corresponding to a respective one of said plurality of subnets, wherein each of said virtual subnet devices aggregates a plurality of physical interfaces that are connected to the respective subnet, and wherein each of said virtual subnet devices is assigned an IP address from the respective subnet and is configured to appear as a network interface to IP and higher layers,

further including each of said virtual subnet devices performing layer two handoffs between network interfaces in response to signals from said mobility manager.

2. The mobile MID as set forth in claim 1, wherein said mobility manager further performs an interface configuration operation.

3. The mobile MID as set forth in claim 1, wherein said mobility manager further performs user authentication and authorization operations.

4. The mobile MID as set forth in claim 1, wherein in connection with determination of when said MID should switch from one interface to another, said mobility manager utilizes a plurality of predefined network signal threshold levels.

5. The mobile MID as set forth in claim 4, wherein said mobility manager activates a selected interface for a future handoff operation prior to said handoff operation being determined as being necessary.

6. The mobile MID as set forth in claim 4, wherein said plurality of predefined signal threshold levels comprises a minimum signal level that indicates an interface is available for use.

7. The mobile MID as set forth in claim 4, wherein said plurality of predefined signal threshold levels comprises a minimum signal level that indicates an interface is active.

8. The mobile MID as set forth in claim 7, wherein said plurality of predefined signal threshold levels comprises a second threshold signal level that indicates that an active interface has become inactive and a handoff operation should be performed, when an active network signal level crosses below said second threshold signal level.

9. The mobile MID as set forth in claim 4, wherein said plurality of predefined signal threshold levels comprises a minimum signal level that indicates an interface is stable, allowing alternate interfaces of said MID to be disconnected or turned off.

10. The mobile MID as set forth in claim 4, wherein said plurality of predefined signal threshold levels comprises a first threshold signal level that indicates that at least one alternate interface should be proactively prepared for a handoff operation, when a stable network signal level crosses below said first threshold signal level, and a second threshold signal level below said first threshold signal level that indicates that an active interface has become inactive and a handoff operation should be performed, when an active network signal level crosses below said second threshold signal level.

11. A mobile MID as set forth in claim 1, further including a plurality of virtual subnet devices that aggregate physical interfaces connected to respective subnets, and wherein a separate one of said virtual subnet devices is instantiated for each respective subnet to which the mobile MID is connected.

12. A multi-interface mobility management system, comprising:

a mobile multi-interface device (MID) having a plurality of network interfaces;

a multi-interface mobility management (MIMM) client residing on said MID, said MIMM client including an interface monitor that monitors status of said plurality of network interfaces, and a mobility manager that determines which one of said plurality of network interfaces should be used by said MID and when said MID should switch from one interface to another, using information from said interface monitor and from a MIMM server; and

a multi-interface mobility management (MIMM) server that collects information from said mobile MIDs, collects information from entities on other networks, and provides information to said mobile MIDs concerning whether and when to execute handoff operations to switch from an active network interface of said plurality of network interfaces to an alternative network interface of said plurality of network interfaces;

wherein said plurality of network interfaces provide access to a plurality of subnets, and said MIMM client further includes a plurality of virtual subnet devices, with each of said virtual subnet devices corresponding to a respective one of said plurality of subnets, wherein each of said virtual subnet devices aggregates a plurality of physical interfaces that are connected to the respective subnet, and wherein each of said virtual subnet devices is assigned an IP address from the respective subnet and is configured to appear as a network interface to IP and higher layers,

further including each of said virtual subnet devices performing layer two handoffs between network interfaces in response to signals from said mobility manager.

13. A multi-interface mobility management system as set forth in claim 12, wherein said mobility manager further performs an interface configuration operation.

14. A multi-interface mobility management system as set forth in claim 12, wherein said mobility manager further performs user authentication and authorization operations.

15. A multi-interface mobility management system as set forth in claim 12, wherein in connection with determination of when said MID should switch from one interface to another, said mobility manager utilizes a plurality of predefined network signal threshold levels.

16. A multi-interface mobility management system as set forth in claim 15, wherein said mobility manager activates a selected interface for a future handoff operation prior to said handoff operation being determined as being necessary when signal strength drops below a first threshold, but does not use the new interface unless signal strength drops below a second threshold lower than said first threshold.

17. A multi-interface mobility management system as set forth in claim 15, wherein said plurality of predefined signal threshold levels comprises a minimum signal level that indicates an interface is available for use.

18. A multi-interface mobility management system as set forth in claim 15, wherein said plurality of predefined signal threshold levels comprises a minimum signal level that indicates an interface is active.

19. A multi-interface mobility management system as set forth in claim 18, wherein said plurality of predefined signal threshold levels comprises a second threshold signal level that indicates that an active interface has become inactive and a handoff operation should be performed, when an active network signal level crosses below said second threshold signal level.

20. A multi-interface mobility management system as set forth in claim 15, wherein said plurality of predefined signal threshold levels comprises a minimum signal level that indicates an interface is stable, allowing alternate interfaces of said MID to be disconnected or turned off.

21. A multi-interface mobility management system as set forth in claim 20, wherein said plurality of predefined signal threshold levels comprises a first threshold signal level that indicates that at least one alternate interface should be proactively prepared for a handoff operation, when a stable network signal level crosses below said first threshold signal level.

22. A multi-interface mobility management system as set forth in claim 12, wherein said MIMM server further communicates with a Real-Time Session (RTS) server to acquire information pertinent to network conditions.

23. A multi-interface mobility management system as set forth in claim 22, wherein said RTS server is a SIP server.

24. A multi-interface mobility management system as set forth in claim 12, wherein information provided to said mobile MIDs includes information regarding network connectivity quality.

25. A multi-interface mobility management system as set forth in claim 12, wherein information provided to said mobile MIDs includes proactive advice on whether and when to execute a handoff or roam operation into a particular network.

26. A multi-interface mobility management system as set forth in claim 12, wherein information provided to said mobile MIDs includes reactive advice to execute an immediate handoff or roam operation from the active network into another particular network when active network connectivity conditions have deteriorated below a predetermined level or upon occurrence of an unexpected network event necessitating switching to another network.

27. A multi-interface mobility management system, comprising:

a mobile multi-interface device (MID) having a plurality of network interfaces;

a multi-interface mobility management (MIMM) client residing on said MID, said MIMM client including an interface monitor that monitors status of said plurality of network interfaces, and a mobility manager that determines which one of said plurality of network interfaces should be used by said MID and when said MID should switch from one interface to another;

wherein in connection with determination of when said MID should switch from one interface to another, said mobility manager utilizes a plurality of predefined network signal threshold levels;

wherein said mobility manager activates a selected interface for a future handoff operation prior to said handoff operation being determined as being necessary when signal strength drops below a first threshold, but does not use the new interface unless signal strength drops below a second threshold lower than said first threshold.