Mechanism to support transparent roaming between IMP service providers in wireless networks

• US 20060047761A1
• Filed: 08/30/2004
• Published: 03/02/2006
• Est. Priority Date: 08/30/2004
• Status: Abandoned Application

• Current Assignee: Matsushita Electric Industrial Company Limited (Panasonic Holdings Corporation)
• Original Assignee: Matsushita Electric Industrial Company Limited (Panasonic Holdings Corporation)
• Inventors: Buford, John, Kaplan, Alan
• Application Number:
  US10/930,043
• Publication Number:
  US 20060047761A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The instant messaging and presence (IMP) protocol implementations are swapped in and out as a client application roams among various service provider networks. The IMP API, and hence the IMP application, remains unchanged. Moreover, the IMP application continues to operate seamlessly and transparently. When the client application roams and a service provider change is detected, the system signals to the new service provider a profile containing the old IMP session details. A new IMP implementation is swapped into the existing IMP application. The IMP implementation may be downloaded in real-time, or it may exist on a SIM card or an SD card, or other suitable memory device.

Claims

1. A method to support roaming in instant messaging systems comprising:

employing a first middleware component configured to support instant message communication through a first service provider;

detecting user roaming from said first service provider to a second service provider;

in response to detecting user roaming, dynamically swapping a second middleware component for said first middleware component, the second middleware component being configured to support instant message communication through said second service provider.

2. The method of claim 1 wherein instant messaging system employs an instant messaging appliance having an operating system and wherein said step of dynamically swapping is performed by dynamically linking said second middleware component to said operating system.

3. The method of claim 1 wherein instant messaging system employs an instant messaging appliance having an operating system and an instant messaging application hosted by said operating system and wherein said step of dynamically swapping is performed by dynamically linking said second middleware component between said operating system and said instant messaging application.

4. The method of claim 1 wherein said step of dynamically swapping is performed by enabling said second middleware component and disabling said first middleware component.

5. The method of claim 1 wherein said step of dynamically swapping is initiated by a system associated with said second service provider.

6. The method of claim 1 wherein said step of dynamically swapping is initiated by an instant messaging appliance and responded to by a system associated with said second service provider.

7. The method of claim 1 wherein said step of dynamic swapping includes the step of using a key to unlock said second middleware component.

8. The method of claim 1 wherein said step of dynamic swapping includes the step of sending a key from a system associated with said second service provider and using said key to unlock said second middleware component.

9. The method of claim 7 further comprising defining a contractual relationship between user and at least one of said service providers and tying use of said key to unlock said second middleware component to the terms of said contractual relationship.

10. The method of claim 1 further comprising maintaining a data store of state variables associated with said instant messaging communication through said first service provider and in response to detecting user roaming automatically transferring said state variables to at least one data structure associated with said second middleware component.

11. The method of claim 10 wherein said step of automatically transferring said state variables includes the step of performing mapping of said variables from a first grammar associated with said first service provider to a second grammar associated with said second service provider.

12. The method of claim 11 wherein said mapping step includes a syntactic mapping.

13. The method of claim 11 wherein said mapping step includes a semantic mapping.

14. The method of claim 1 further comprising maintaining a data store of state variables associated with user presence mediated by said first service provider and in response to detecting user roaming automatically transferring said state variables to a data store associated with said second service provider.

15. The method of claim 1 further comprising processing said instant message communication through a gateway that routes said instant message between said first and second service providers and performs protocol conversion upon said instant message to render said instant message compatible with both service providers.

16. A mechanism to support roaming between instant messaging service providers comprising:

a memory associated with an instant messaging appliance and configured to store an instant messaging middleware component;

said middleware component having a first interface for dynamically linking to an operating system associated with said instant messaging appliance;

said middleware component having a second interface for dynamically linking to an instant messaging application run on said instant messaging appliance.

17. The mechanism of claim 16 further comprising data structure associated with said middleware component, said data structure being configured to store state variables associated with an instant messaging service.

18. The mechanism of claim 16 wherein said middleware component is configured as a downloadable component.

19. The mechanism of claim 16 wherein said middleware component includes an instant messaging and presence protocol stack.

20. The mechanism of claim 16 wherein said middleware component includes a lock mechanism that inhibits use of said middleware component unless an associated key is supplied.