USRE44836E1 - System and method for efficient transfer of applications and data during device swap - Google Patents

System and method for efficient transfer of applications and data during device swap Download PDF

Info

Publication number
USRE44836E1
USRE44836E1 US13/973,033 US201313973033A USRE44836E US RE44836 E1 USRE44836 E1 US RE44836E1 US 201313973033 A US201313973033 A US 201313973033A US RE44836 E USRE44836 E US RE44836E
Authority
US
United States
Prior art keywords
applications
wireless device
identification information
wireless
application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US13/973,033
Inventor
Kenneth Wallis
Viera Bibr
Michael Shenfield
Brindusa L. FRITSCH
Kamen B. VITANOV
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Malikie Innovations Ltd
Original Assignee
BlackBerry Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by BlackBerry Ltd filed Critical BlackBerry Ltd
Priority to US13/973,033 priority Critical patent/USRE44836E1/en
Assigned to RESEARCH IN MOTION LIMITED reassignment RESEARCH IN MOTION LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SHENFIELD, MICHAEL, BIBR, VIERA, FRITSCH, BRINDUSA L., VITANOV, KAMEN B., WALLIS, KENNETH
Assigned to BLACKBERRY LIMITED reassignment BLACKBERRY LIMITED CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: RESEARCH IN MOTION LIMITED
Application granted granted Critical
Publication of USRE44836E1 publication Critical patent/USRE44836E1/en
Assigned to MALIKIE INNOVATIONS LIMITED reassignment MALIKIE INNOVATIONS LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BLACKBERRY LIMITED
Assigned to MALIKIE INNOVATIONS LIMITED reassignment MALIKIE INNOVATIONS LIMITED NUNC PRO TUNC ASSIGNMENT (SEE DOCUMENT FOR DETAILS). Assignors: BLACKBERRY LIMITED
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/48—Indexing scheme relating to G06F9/48
    • G06F2209/482—Application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching

Definitions

  • the invention relates to management of applications and application registration information. More specifically, it relates to a method and a system for maintaining applications and application registration information during a device swap.
  • Such data existing on the old device includes user applications the data associated with the user applications and application registration information, for applications which are registered with a mediating service in order to access a backend application service provider.
  • FIG. 1 is a block diagram of a communication network system adapted in accordance with an embodiment of the present invention
  • FIG. 2 is a block diagram of a system for efficient transfer of applications from a first wireless device to a second wireless device, according to an embodiment of the present invention.
  • FIG. 3 is a flow chart of a method for efficient transfer of applications from a first wireless device to a second wireless device, according to an embodiment of the present invention.
  • a method for automatically registering applications with an application gateway when transferring said applications from a first wireless device to a second wireless device comprising: registering an application installed on said first wireless device with said application gateway by providing identification information for said first wireless device and said application; said application gateway maintaining a registration list of identification information of registered wireless devices and applications installed on said registered wireless devices; creating a back-up of said applications and registration information for said applications installed on said first wireless device; installing said applications and said registration information for said applications from said back-up onto a second wireless device; communicating to said application gateway identification information regarding said second wireless device and said restored applications; and said application gateway registering said second wireless device by updating said registration list with said identification information for said second wireless device and said applications installed on said second wireless device.
  • an application gateway for automatically registering applications therewith when transferring said applications from a first wireless device to a second wireless device, comprising: memory means storing a registration list of identification information of registered wireless devices and applications installed on said registered wireless devices; communication means for receiving identification information regarding said second wireless device and said restored applications; and update means for updating said registration list with said identification information for said second wireless device and said applications installed on said second wireless device.
  • a network system 10 comprises mobile communication devices 11 for interacting with one or more backend data sources 21 , 23 , 25 (e.g. a schema based service such as web services or database that provides enterprise services used by an application) via a wireless network 13 coupled to an application gateway 15 .
  • the devices 11 A, 11 B, 11 C are devices such as, but not limited to, mobile telephones, PDAs, two-way pagers, dual-mode communication devices.
  • the network 10 can also have desktop computers (not shown) coupled though a local area network.
  • the devices 11 A, 11 B, 11 C and desktop computers of the network 10 are hereafter referred to as the devices 11 for the sake of simplicity.
  • the application gateway 15 and data sources 21 , 23 , 25 can be linked via extranets (e.g. the Internet) and/or intranets as is known in the art.
  • the application gateway 15 handles request/response messages initiated by the applications on the devices 11 , as well as subscription notifications pushed to the devices 11 from the data sources 21 , 23 , 25 .
  • the Application Gateway 15 can function as a Data Mapping Server for mediating messaging between a client runtime environment (RE) on the device 11 and a backend server of the data sources 21 , 23 , 25 .
  • the Runtime Environment (RE) is an intelligent container that executes application components and provides common services as needed for execution of the applications.
  • the application gateway 15 can provide for asynchronous messaging for the applications and can integrate and communicate with legacy backend data sources 21 , 23 , 25 .
  • the devices 11 transmit and receive the Wireless Component Applications technology or wireless component applications, as further described below, when in communication with the data sources 21 , 23 , 25 , as well as transmit/receive messaging associated with operation of the applications.
  • the devices 11 can operate as web clients of the data sources 21 , 23 and 25 through execution of the applications when provisioned on respective runtime environments (RE) of the devices 11 .
  • RE runtime environments
  • the application gateway 15 communicates with the data sources 21 , 23 and 25 through various protocols (such as but not limited to HTTP, SQL, and component API) for exposing relevant business logic (methods) to the applications once provisioned on the devices 11 .
  • the applications can use the business logic of the data sources 21 , 23 and 25 similarly to calling a method on an object (or a function). It is recognized that the applications can be downloaded/uploaded in relation to data sources 21 , 23 , 25 via the network and application gateway 15 directly to the devices 11 .
  • the application gateway 15 is coupled to a provisioning server 17 and a discovery server 19 for providing a mechanism for optimized over-the-air provisioning of the applications, including capabilities for application discovery from the device 11 as listed in a UDDI (for example) registry 18 .
  • the Registry 18 can be part of the Discovery Service implemented by the server 19 , and the registry 18 is used for publishing the applications.
  • the application information in the registry 18 can contain such as but not limited to a Deployment Descriptor DD (contains information such as application name, version, and description) as well as the location of this application in an application repository 16 .
  • the RE receives the application gateway 15 URL. If the operating environment is defined to be secure, then the RE will include its public key in a security handshake with the application gateway 15 . The application gateway 15 will pass its public key in the synchronous response to the security handshake. While use of the MDS service book is one possible way of implementing the device initialization/configuration protocol, those skilled in the art will appreciate that other implementations are also possible. For example, the above functionality may also be implemented using IT Policies.
  • the runtime environment RE uses this information to connect to the gateway 15 for initial handshaking. It is recognized there could be more than one gateway 15 in the network 10 , as desired. Once initialized, access to the applications by the devices 11 , as downloaded/uploaded, can be communicated via the gateway 15 directly from the application repository 16 , and/or in association with data source 21 , 23 , 25 direct access (not shown) to the application repository 16 .
  • a first wireless device 11 a is in communication with an application gateway (AG) 15 .
  • the application gateway 15 is a server (or servers) responsible for managing communication between wireless devices and backend applications (which may include, but is not limited to, databases, internet web services).
  • the AG 15 handles transforming wireless device messages encoded in a specific format into the format expected by the particular backend application the message is intended for.
  • the AG 15 also handles discovery and provisioning requests from wireless devices, and, in certain embodiments, provides many administrative functions for managing the wireless devices themselves.
  • the AG 15 is in communication with a plurality of backend application service providers 23 a, 23 b, supporting a plurality of user applications.
  • An example of a backend service 23 could be a web service that provides random famous historic quotes.
  • a component application would be written to request a random quote from the web service 23 and display it on the device 11 .
  • the component application would encode this request in a compact, efficient way and send it to the application gateway 15 .
  • the application gateway 15 would transform this request into a format compatible with the web services communication protocol and forward the request to the appropriate backend service provider 23 .
  • the reverse process would happen with the response from the web service containing the random quote.
  • the AG 15 maintains a registration list storing identification information for registered wireless devices 11 and applications installed on the registered wireless devices 11 . For example, when the first wireless device 11 a first communicates with the server 19 , the identification information of the first wireless device 11 is stored on the AG 15 . This way, a record will be created for the first wireless device 11 a on the AG 15 . At the time of provisioning of each application on the wireless device 11 , the AG 15 will make an entry in the wireless device 11 record to associate this application with this device. This is done so that the application gateway 15 may know which devices have which applications installed thereon.
  • the device 11 sends a “security handshake” to the AG 15 , including the device's public key if operating in a secure environment.
  • This handshake is preferably a synchronous communication.
  • the response back from the AG 15 gives the device 11 the AG public key (if in a secure environment), as well as other administrative information.
  • the device 11 then sends a status message to the AG 15 including information such as the runtime environment version installed on the device 11 , etc.
  • the status message is a generic status message that would normally include more information, but not on a first registration. It is used as a trigger for the rest of the registration sequence.
  • the AG 15 When the AG 15 receives this status message, it then sends to the device 11 (asynchronously) administrative privilege information and other information.
  • administrative privileges would be specifying whether the AG 15 allows the device 11 to discover applications, or if the device 11 is allowed to request an application to be provisioned.
  • the first wireless device 11 a contains component applications and associated data and the application gateway registration information.
  • the AG registration information allows the new device to detect that there has been a device swap.
  • One possible way of detecting that there has been a device swap is to use the device PIN which is part of the registration information contained in the runtime environment and therefore backed up.
  • the registration information When the registration information is loaded onto the new (second) device and the RE starts for the first time, it compares the stored device PIN against the current device's PIN, and if they are different, a device swap will be detected.
  • the backup data storage 27 may be a hard disk, a floppy disk, or any other memory means, portable or not, which can be connected to a first wireless device 11 a in order to store the existing applications and applications data, as well as the MS registration information, before a device swap.
  • the backup data storage 27 is also connected to a second wireless device 11 b for transferring the applications and application data, as well as the AG registration information, backed-up from the first wireless device 11 a.
  • the second wireless device 11 b just like the first one, has installed a mediating service-enabling container application (MSCA), or a runtime environment, which acts as a container for applications wishing to interact with the AG 15 .
  • MSCA mediating service-enabling container application
  • the second wireless device 11 b is in communication with the AG 15 for synchronizing the registration information and the component applications installed following a transfer.
  • the MSCA determines that the wireless device has been changed and notifies the AG 15 accordingly.
  • the AG 15 updates its internal registration list by either a) modifying the record of the first wireless device to refer to the second wireless device or b) adding a new entry for the second wireless device.
  • the MSCA of the second wireless device 24 also sends a status message to the AG 15 including information regarding the set of installed (restored) applications.
  • the AG 15 will synchronize with this list, updating its registration list of installed applications for the wireless device 11 b.
  • the AG 15 also maintains a support list of all applications supported and their respected application service providers. Following transfer of applications from the first device 11 a to the second device 11 b, the AG 15 will consult the support list and determine whether any one of the restored applications is no longer supported, i.e. not found on the support list.
  • This step is necessary in order to synchronize for changes on the wireless device side and/or the AG 15 side between the time the backup was performed and the restore occurred. If any of the applications on the second wireless device 11 b are not found on the support list, the AG 15 proceeds to delete those applications from the wireless device 11 b.
  • a flow chart of a method for efficient transfer of applications from a first wireless device to a second wireless device there is illustrated a flow chart of a method for efficient transfer of applications from a first wireless device to a second wireless device, according to the present invention.
  • the application installed on the first wireless device is registered with the application gateway by providing identification information for the first wireless device and the application.
  • the application gateway maintains a registration list of identification information of registered wireless devices and applications installed on the registered wireless devices.
  • a back-up is created for the applications and registration information for the applications installed on the first wireless device.
  • the applications and the registration information for the applications from the back-up are installed onto a second wireless device.
  • identification information regarding the second wireless device and the restored applications is communicated to the application gateway.
  • the application gateway registers the second wireless device by updating the registration list with the identification information for the second wireless device and the applications installed on the second wireless device.

Abstract

A method for automatically registering the runtime environment and related component applications with an application gateway when transferring the applications from a first wireless device to a second wireless device is provided. Applications installed on the first wireless device are registered with an application gateway, which maintains a registration list of identification information for all registered wireless devices and applications installed thereon. A back-up is created of the applications and registration information for the runtime environment installed on the first wireless device for transfer to a second wireless device. An application container of the second wireless device determining installation and communicating to the application gateway identification information regarding the second wireless device and the restored applications. The application gateway registers the second wireless device by updating the registration list with the identification information for the second wireless device and the applications installed thereon.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims the benefit of U.S. Provisional Patent Application No. 60/672,089, filed Apr. 18, 2005.
FIELD OF THE INVENTION
The invention relates to management of applications and application registration information. More specifically, it relates to a method and a system for maintaining applications and application registration information during a device swap.
BACKGROUND OF THE INVENTION
When replacing an old wireless device with a new wireless device, it is convenient for users to be able to backup data saved on the old device and to restore it onto the new device. Such data existing on the old device includes user applications the data associated with the user applications and application registration information, for applications which are registered with a mediating service in order to access a backend application service provider.
Current systems of backup/restore usually allow a user to transfer only application data from one device to another, while the user applications themselves and their associated application registration information cannot be saved and restored. With such systems, once the application data is transferred, all user-installed applications must be re-installed onto the new device, which may be time-consuming and inconvenient for the user. While some systems may allow for back-up of user-installed applications, these applications will need to be re-registered with the application mediating service following the transfer, which necessitates user/IT administrator intervention.
There exists therefore a need for a system allowing the replacement of one wireless device with another while maintaining the mediating service environment and without requiring user interaction.
BRIEF DESCRIPTION OF THE DRAWINGS
These and other features, aspects and advantages of the present invention will become better understood with regard to the following description and accompanying drawings wherein:
FIG. 1 is a block diagram of a communication network system adapted in accordance with an embodiment of the present invention;
FIG. 2 is a block diagram of a system for efficient transfer of applications from a first wireless device to a second wireless device, according to an embodiment of the present invention; and
FIG. 3 is a flow chart of a method for efficient transfer of applications from a first wireless device to a second wireless device, according to an embodiment of the present invention.
 DETAILED DESCRIPTION
According to a first broad aspect of the present invention, there is provided a method for automatically registering applications with an application gateway when transferring said applications from a first wireless device to a second wireless device, comprising: registering an application installed on said first wireless device with said application gateway by providing identification information for said first wireless device and said application; said application gateway maintaining a registration list of identification information of registered wireless devices and applications installed on said registered wireless devices; creating a back-up of said applications and registration information for said applications installed on said first wireless device; installing said applications and said registration information for said applications from said back-up onto a second wireless device; communicating to said application gateway identification information regarding said second wireless device and said restored applications; and said application gateway registering said second wireless device by updating said registration list with said identification information for said second wireless device and said applications installed on said second wireless device.
According to a second broad aspect of the present invention, there is provided an application gateway for automatically registering applications therewith when transferring said applications from a first wireless device to a second wireless device, comprising: memory means storing a registration list of identification information of registered wireless devices and applications installed on said registered wireless devices; communication means for receiving identification information regarding said second wireless device and said restored applications; and update means for updating said registration list with said identification information for said second wireless device and said applications installed on said second wireless device.
Referring to FIG. 1, a network system 10 comprises mobile communication devices 11 for interacting with one or more backend data sources 21, 23, 25 (e.g. a schema based service such as web services or database that provides enterprise services used by an application) via a wireless network 13 coupled to an application gateway 15. The devices 11A, 11B, 11C are devices such as, but not limited to, mobile telephones, PDAs, two-way pagers, dual-mode communication devices. The network 10 can also have desktop computers (not shown) coupled though a local area network. The devices 11A, 11B, 11C and desktop computers of the network 10 are hereafter referred to as the devices 11 for the sake of simplicity. It is recognized that the application gateway 15 and data sources 21, 23, 25 can be linked via extranets (e.g. the Internet) and/or intranets as is known in the art. The application gateway 15 handles request/response messages initiated by the applications on the devices 11, as well as subscription notifications pushed to the devices 11 from the data sources 21, 23, 25. The Application Gateway 15 can function as a Data Mapping Server for mediating messaging between a client runtime environment (RE) on the device 11 and a backend server of the data sources 21, 23, 25. The Runtime Environment (RE) is an intelligent container that executes application components and provides common services as needed for execution of the applications. The application gateway 15 can provide for asynchronous messaging for the applications and can integrate and communicate with legacy backend data sources 21, 23, 25. The devices 11 transmit and receive the Wireless Component Applications technology or wireless component applications, as further described below, when in communication with the data sources 21, 23, 25, as well as transmit/receive messaging associated with operation of the applications. The devices 11 can operate as web clients of the data sources 21, 23 and 25 through execution of the applications when provisioned on respective runtime environments (RE) of the devices 11.
For satisfying the appropriate messaging associated with the applications, the application gateway 15 communicates with the data sources 21, 23 and 25 through various protocols (such as but not limited to HTTP, SQL, and component API) for exposing relevant business logic (methods) to the applications once provisioned on the devices 11. The applications can use the business logic of the data sources 21, 23 and 25 similarly to calling a method on an object (or a function). It is recognized that the applications can be downloaded/uploaded in relation to data sources 21, 23, 25 via the network and application gateway 15 directly to the devices 11. For example, the application gateway 15 is coupled to a provisioning server 17 and a discovery server 19 for providing a mechanism for optimized over-the-air provisioning of the applications, including capabilities for application discovery from the device 11 as listed in a UDDI (for example) registry 18. The Registry 18 can be part of the Discovery Service implemented by the server 19, and the registry 18 is used for publishing the applications. The application information in the registry 18 can contain such as but not limited to a Deployment Descriptor DD (contains information such as application name, version, and description) as well as the location of this application in an application repository 16.
Referring to FIG. 1, in one embodiment of the present invention, for initialization of the runtime environment RE, the RE receives the application gateway 15 URL. If the operating environment is defined to be secure, then the RE will include its public key in a security handshake with the application gateway 15. The application gateway 15 will pass its public key in the synchronous response to the security handshake. While use of the MDS service book is one possible way of implementing the device initialization/configuration protocol, those skilled in the art will appreciate that other implementations are also possible. For example, the above functionality may also be implemented using IT Policies.
The runtime environment RE uses this information to connect to the gateway 15 for initial handshaking. It is recognized there could be more than one gateway 15 in the network 10, as desired. Once initialized, access to the applications by the devices 11, as downloaded/uploaded, can be communicated via the gateway 15 directly from the application repository 16, and/or in association with data source 21, 23, 25 direct access (not shown) to the application repository 16.
Now, with respect to FIG. 2, a system enabling transfer of applications and data during a swap will be described. A first wireless device 11a is in communication with an application gateway (AG) 15. As explained above, the application gateway 15 is a server (or servers) responsible for managing communication between wireless devices and backend applications (which may include, but is not limited to, databases, internet web services). The AG 15 handles transforming wireless device messages encoded in a specific format into the format expected by the particular backend application the message is intended for. The AG 15 also handles discovery and provisioning requests from wireless devices, and, in certain embodiments, provides many administrative functions for managing the wireless devices themselves.
The AG 15 is in communication with a plurality of backend application service providers 23a, 23b, supporting a plurality of user applications.
An example of a backend service 23 could be a web service that provides random famous historic quotes. A component application would be written to request a random quote from the web service 23 and display it on the device 11. The component application would encode this request in a compact, efficient way and send it to the application gateway 15. The application gateway 15 would transform this request into a format compatible with the web services communication protocol and forward the request to the appropriate backend service provider 23. The reverse process would happen with the response from the web service containing the random quote.
The AG 15 maintains a registration list storing identification information for registered wireless devices 11 and applications installed on the registered wireless devices 11. For example, when the first wireless device 11a first communicates with the server 19, the identification information of the first wireless device 11 is stored on the AG 15. This way, a record will be created for the first wireless device 11a on the AG 15. At the time of provisioning of each application on the wireless device 11, the AG 15 will make an entry in the wireless device 11 record to associate this application with this device. This is done so that the application gateway 15 may know which devices have which applications installed thereon.
The registration protocol between the device 11 and the application gateway will now be described. Following the device 11 receiving the AG URL in some way, as previously described, the device 11 sends a “security handshake” to the AG 15, including the device's public key if operating in a secure environment. This handshake is preferably a synchronous communication. The response back from the AG 15 gives the device 11 the AG public key (if in a secure environment), as well as other administrative information. The device 11 then sends a status message to the AG 15 including information such as the runtime environment version installed on the device 11, etc. The status message is a generic status message that would normally include more information, but not on a first registration. It is used as a trigger for the rest of the registration sequence. When the AG 15 receives this status message, it then sends to the device 11 (asynchronously) administrative privilege information and other information. An example of administrative privileges would be specifying whether the AG 15 allows the device 11 to discover applications, or if the device 11 is allowed to request an application to be provisioned.
The first wireless device 11a contains component applications and associated data and the application gateway registration information.
The ability to backup the component applications themselves, as opposed to just the application data, is facilitated by the fact that the component applications themselves are defined as “metadata”, by using a combination of XML and ECMAscript.
In case of transfer of the applications from the first device to a new (second) device, the AG registration information allows the new device to detect that there has been a device swap. One possible way of detecting that there has been a device swap is to use the device PIN which is part of the registration information contained in the runtime environment and therefore backed up. When the registration information is loaded onto the new (second) device and the RE starts for the first time, it compares the stored device PIN against the current device's PIN, and if they are different, a device swap will be detected.
The backup data storage 27 may be a hard disk, a floppy disk, or any other memory means, portable or not, which can be connected to a first wireless device 11a in order to store the existing applications and applications data, as well as the MS registration information, before a device swap.
The backup data storage 27 is also connected to a second wireless device 11b for transferring the applications and application data, as well as the AG registration information, backed-up from the first wireless device 11a. The second wireless device 11b, just like the first one, has installed a mediating service-enabling container application (MSCA), or a runtime environment, which acts as a container for applications wishing to interact with the AG 15. The second wireless device 11b is in communication with the AG 15 for synchronizing the registration information and the component applications installed following a transfer. When the information is restored to the second wireless device 11b, the MSCA determines that the wireless device has been changed and notifies the AG 15 accordingly. The AG 15 updates its internal registration list by either a) modifying the record of the first wireless device to refer to the second wireless device or b) adding a new entry for the second wireless device. The MSCA of the second wireless device 24 also sends a status message to the AG 15 including information regarding the set of installed (restored) applications. The AG 15 will synchronize with this list, updating its registration list of installed applications for the wireless device 11b. In one embodiment of the present invention, the AG 15 also maintains a support list of all applications supported and their respected application service providers. Following transfer of applications from the first device 11a to the second device 11b, the AG 15 will consult the support list and determine whether any one of the restored applications is no longer supported, i.e. not found on the support list. This step is necessary in order to synchronize for changes on the wireless device side and/or the AG 15 side between the time the backup was performed and the restore occurred. If any of the applications on the second wireless device 11b are not found on the support list, the AG 15 proceeds to delete those applications from the wireless device 11b.
With respect to FIG. 3, there is illustrated a flow chart of a method for efficient transfer of applications from a first wireless device to a second wireless device, according to the present invention. In a first step 31, the application installed on the first wireless device is registered with the application gateway by providing identification information for the first wireless device and the application. In a next step 33, the application gateway maintains a registration list of identification information of registered wireless devices and applications installed on the registered wireless devices. In step 35, a back-up is created for the applications and registration information for the applications installed on the first wireless device. In step 37, the applications and the registration information for the applications from the back-up are installed onto a second wireless device. In step 39, identification information regarding the second wireless device and the restored applications is communicated to the application gateway. In step 41, the application gateway registers the second wireless device by updating the registration list with the identification information for the second wireless device and the applications installed on the second wireless device.
While illustrated in the block diagrams as groups of discrete components communicating with each other via distinct data signal connections, it will be understood by those skilled in the art that the preferred embodiments are provided by a combination of hardware and software components, with some components being implemented by a given function or operation of a hardware or software system, and many of the data paths illustrated being implemented by data communication within a computer applications or operating system. The structure illustrated is thus provided for efficiency of teaching the present preferred embodiment.
It will be understood that numerous modifications thereto will appear to those skilled in the art. Accordingly, the above description and accompanying drawings should be taken as illustrative of the invention and not in a limiting sense. It will further be understood that it is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains and as may be applied to the essential features herein before set forth, and as follows in the scope of the appended claims.

Claims (3)

What is claimed is:
1. An application gateway for automatically registering applications therewith when transferring said applications from a first wireless device to a second wireless device, comprising:
a data storage storing a registration list of identification information of registered wireless devices and applications installed on said registered wireless devices, and a back-up of applications, said back-up including said applications and registration information for said applications installed on said first wireless device;
a receiver for receiving identification information for said first wireless device and said applications installed on said first wireless device, and receiving identification information regarding said second wireless device and said applications installed from said back-up of applications and associated registration information in said data storage onto said second wireless device;
a processor configured for updating said registration list with said identification information for said second wireless device and said applications installed from said back-up on said second wireless device;
wherein said data storage further comprises a support list of applications supported by application service providers;
and wherein said processor is further configured for, following transfer of applications from said first device to said second device, matching said applications installed from said back-up of applications and associated registration information in said data storage onto said second wireless device with applications on said support list and deleting unmatched applications from said second wireless device.
2. A method of automatically registering applications in an application gateway when said applications are being transferred from a first wireless device to a second wireless device in a wireless network comprising a plurality of wireless devices registered with said application gateway, comprising:
registering applications installed on said first wireless device by receiving front said first wireless device identification information for said first wireless device and said applications;
maintaining a registration list of identification information of registered wireless devices and applications installed on said registered wireless devices;
receiving identification information regarding said second wireless device and applications installed from a backup stored in a back-up storage onto said second wireless device, said back-up comprising said applications and registration information for said applications installed on said first wireless device;
registering said second wireless device by updating said registration list with said identification information for said second wireless device and said applications installed from said back-up on said second wireless device;
maintaining, at said application gateway, a support list of applications supported by application service providers;
following transfer of applications from said first device to said second device, matching said applications installed from said back-up onto said second wireless device with applications on said support list; and
deleting unmatched applications from said second wireless device following said transfer.
3. The method as claimed in claim 2, wherein said updating said registration list comprises modifying a record of said first wireless device to refer to said identification information of said second wireless device.
US13/973,033 2005-04-18 2013-08-22 System and method for efficient transfer of applications and data during device swap Active 2028-12-19 USRE44836E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/973,033 USRE44836E1 (en) 2005-04-18 2013-08-22 System and method for efficient transfer of applications and data during device swap

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US67208905P 2005-04-18 2005-04-18
US11/360,573 US7680910B2 (en) 2005-04-18 2006-02-24 System and method for efficient transfer of applications and data during device swap
US13/973,033 USRE44836E1 (en) 2005-04-18 2013-08-22 System and method for efficient transfer of applications and data during device swap

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/360,573 Reissue US7680910B2 (en) 2005-04-18 2006-02-24 System and method for efficient transfer of applications and data during device swap

Publications (1)

Publication Number Publication Date
USRE44836E1 true USRE44836E1 (en) 2014-04-08

Family

ID=37114659

Family Applications (3)

Application Number Title Priority Date Filing Date
US11/360,573 Ceased US7680910B2 (en) 2005-04-18 2006-02-24 System and method for efficient transfer of applications and data during device swap
US12/692,675 Active 2027-03-28 US8554887B2 (en) 2005-04-18 2010-01-25 System and method for efficient transfer of applications and data during device swap
US13/973,033 Active 2028-12-19 USRE44836E1 (en) 2005-04-18 2013-08-22 System and method for efficient transfer of applications and data during device swap

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US11/360,573 Ceased US7680910B2 (en) 2005-04-18 2006-02-24 System and method for efficient transfer of applications and data during device swap
US12/692,675 Active 2027-03-28 US8554887B2 (en) 2005-04-18 2010-01-25 System and method for efficient transfer of applications and data during device swap

Country Status (4)

Country Link
US (3) US7680910B2 (en)
EP (1) EP1872255A4 (en)
CA (1) CA2601730C (en)
WO (1) WO2006110989A1 (en)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7840955B1 (en) * 2005-12-30 2010-11-23 United Services Automobile Association (Usaa) Method and system for restoring software
US8726271B1 (en) 2005-12-30 2014-05-13 United Services Automobile Association (Usaa) Method and system for installing software
US8566820B1 (en) 2005-12-30 2013-10-22 United Services Automobile Association (Usaa) Method and system for installing software
US20090254857A1 (en) * 2006-07-11 2009-10-08 Christopher Romine Wireless communication device pre-purchase personalization
US8060874B2 (en) * 2007-01-29 2011-11-15 Symbol Technologies, Inc. Efficient provisioning of software packages to mobile handheld devices
DE102009048303A1 (en) 2009-05-07 2010-11-18 Siemens Aktiengesellschaft Beacon for a star network, sensor node in a star network, method for initializing a gateway in a star network and method for operating a star network
EP2398213B1 (en) * 2010-06-17 2019-08-07 BlackBerry Limited Wireless device swap
US20110314170A1 (en) * 2010-06-17 2011-12-22 Research In Motion Limited Wireless Device Swap
US9641606B2 (en) 2010-06-22 2017-05-02 Blackberry Limited Peer to peer secure synchronization between handheld devices
US8744367B2 (en) 2010-08-31 2014-06-03 At&T Intellectual Property I, L.P. Tail optimization protocol for cellular radio resource allocation
WO2012037675A2 (en) 2010-09-24 2012-03-29 Research In Motion Limited Storage of applications and associated digital goods for use in wireless communication devices and systems
US8527627B2 (en) 2010-12-14 2013-09-03 At&T Intellectual Property I, L.P. Intelligent mobility application profiling with respect to identified communication bursts
GB2487046A (en) * 2011-01-04 2012-07-11 Kevin George Stalker Duplicate mobile phones with mirrored data and functions
US9220066B2 (en) 2011-06-20 2015-12-22 At&T Intellectual Property I, L.P. Bundling data transfers and employing tail optimization protocol to manage cellular radio resource utilization
US9264872B2 (en) 2011-06-20 2016-02-16 At&T Intellectual Property I, L.P. Controlling traffic transmissions to manage cellular radio resource utilization
KR101844512B1 (en) * 2011-11-18 2018-05-21 삼성전자주식회사 Method for using an application, gateway using thereof, terminal using thereof, and terminal system using thereof
US9723058B2 (en) * 2013-05-28 2017-08-01 Vmware, Inc. Dynamic registration of an application with an enterprise system
RU2584447C2 (en) * 2013-10-21 2016-05-20 Общество С Ограниченной Ответственностью "Яндекс" Method and system for simultaneous installation of plurality of applications using false backup archive recovery
US10917263B1 (en) * 2014-05-29 2021-02-09 Modius Inc. Universal configurable device gateway
US10693973B2 (en) 2016-07-18 2020-06-23 Wistron Aiedge Corporation System and method for work distribution in a fog network via code offloading
EP3416056A1 (en) * 2017-06-16 2018-12-19 Fujitsu Limited Method for migrating a workload, computer arrangement and non-volatile storage medium
CN108234774A (en) * 2018-01-30 2018-06-29 维沃移动通信有限公司 The method for down loading and terminal of a kind of application program
KR20220017075A (en) * 2020-08-04 2022-02-11 삼성전자주식회사 A recovering method of a home screen and an electronic device applying the same

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2294787A (en) 1994-11-07 1996-05-08 Motorola Israel Ltd Electronic device and method of cloning
WO2002041141A2 (en) 2000-11-20 2002-05-23 Axeda Systems Operating Company, Inc. A device registration mechanism
US6425126B1 (en) 1999-05-19 2002-07-23 International Business Machines Corporation Apparatus and method for synchronizing software between computers
US20020178178A1 (en) 2001-04-24 2002-11-28 Luosheng Peng Apparatus and methods for intelligently caching applications and data on a gateway
US20030101246A1 (en) 2001-11-29 2003-05-29 Nokia Corporation System and method for identifying and accessing network services
US20030228866A1 (en) 2002-05-24 2003-12-11 Farhad Pezeshki Mobile terminal system
US20040187012A1 (en) 2003-03-21 2004-09-23 Hitachi, Ltd. Hidden data backup and retrieval for a secure device
US20050027831A1 (en) 2003-07-30 2005-02-03 International Business Machines Corporation Build time determination and installation of drivers on cloned systems
US20050064868A1 (en) 2000-02-09 2005-03-24 Coppinger Paul D. System and method for registration for application program deployment
GB2406664A (en) 2003-10-03 2005-04-06 Sendo Int Ltd Registering an application program of a mobile information device
US20060230081A1 (en) 2002-10-10 2006-10-12 Craswell Ronald J Backing up a wireless computing device
US7187935B1 (en) 2001-10-16 2007-03-06 International Business Machines Corporation Method and software for low bandwidth presence via aggregation and profiling

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1170967B1 (en) * 2000-07-04 2003-10-22 Siemens Aktiengesellschaft System and method for operating an interactive server in a cellular network
JP4235177B2 (en) * 2002-12-11 2009-03-11 富士通株式会社 BACKUP SYSTEM, BACKUP CONTROL DEVICE, BACKUP DATA MANAGEMENT METHOD, BACKUP CONTROL PROGRAM, AND COMPUTER-READABLE RECORDING MEDIUM CONTAINING THE PROGRAM

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2294787A (en) 1994-11-07 1996-05-08 Motorola Israel Ltd Electronic device and method of cloning
US6425126B1 (en) 1999-05-19 2002-07-23 International Business Machines Corporation Apparatus and method for synchronizing software between computers
US20050064868A1 (en) 2000-02-09 2005-03-24 Coppinger Paul D. System and method for registration for application program deployment
WO2002041141A2 (en) 2000-11-20 2002-05-23 Axeda Systems Operating Company, Inc. A device registration mechanism
US20020178178A1 (en) 2001-04-24 2002-11-28 Luosheng Peng Apparatus and methods for intelligently caching applications and data on a gateway
US7187935B1 (en) 2001-10-16 2007-03-06 International Business Machines Corporation Method and software for low bandwidth presence via aggregation and profiling
US20030101246A1 (en) 2001-11-29 2003-05-29 Nokia Corporation System and method for identifying and accessing network services
US20030228866A1 (en) 2002-05-24 2003-12-11 Farhad Pezeshki Mobile terminal system
US20060230081A1 (en) 2002-10-10 2006-10-12 Craswell Ronald J Backing up a wireless computing device
US20040187012A1 (en) 2003-03-21 2004-09-23 Hitachi, Ltd. Hidden data backup and retrieval for a secure device
US20050027831A1 (en) 2003-07-30 2005-02-03 International Business Machines Corporation Build time determination and installation of drivers on cloned systems
GB2406664A (en) 2003-10-03 2005-04-06 Sendo Int Ltd Registering an application program of a mobile information device

Non-Patent Citations (14)

* Cited by examiner, † Cited by third party
Title
Canadian Intellectual Property Office, Examiner's Requisition dated Aug. 29, 2011, issued in Canadian Patent Application No. 2,601,730.
Canadian Intellectual Property Office, Examiner's Requisition dated Jun. 3, 2009, issued in Canadian Patent Application No. 2,601,730.
Canadian Intellectual Property Office, Examiner's Requisition dated Oct. 26, 2010, issued in Canadian Patent Application No. 2,601,730.
European Patent Office, Office Communication dated Jul. 14, 2008 issued in European Patent Application No. 06705230.8.
Ipulse, Response to Office Communication dated Feb. 20, 2009 submitted on European Patent Application No. 06705230.8.
Norton Rose, Response to Examiner's Requisition dated Dec. 9, 2011, submitted on Canadian Patent Application No. 2,601,730.
Norton Rose, Response to Office Action dated Jun. 20, 2011, submitted on U.S. Appl. No. 12/692,675.
Norton Rose, Response to Office Action dated Nov. 1, 2011, submitted on U.S. Appl. No. 12/692,675.
Ogilvy Renault, Response to Examiner's Requisition dated Dec. 1, 2009, submitted on Canadian Patent Application No. 2,601,730.
Ogilvy Renault, Response to Examiner's Requisition dated Feb. 4, 2011, submitted on Canadian Patent Application No. 2,601,730.
Ogilvy Renault, Response to Office Action dated Jan. 7, 2011, submitted on U.S. Appl. No. 12/692,675.
United States Patent and Trademark Office, Office Action dated Aug. 30, 2011, issued in U.S. Appl. No. 12/692,675.
United States Patent and Trademark Office, Office Action dated Mar. 30, 2011, issued in U.S. Appl. No. 12/692,675.
United States Patent and Trademark Office, Office Action dated Oct. 8, 2010, issued in United U.S. Appl. No. 12/692,675.

Also Published As

Publication number Publication date
US7680910B2 (en) 2010-03-16
WO2006110989A1 (en) 2006-10-26
US20060234623A1 (en) 2006-10-19
EP1872255A4 (en) 2008-08-13
EP1872255A1 (en) 2008-01-02
US20100179942A1 (en) 2010-07-15
CA2601730C (en) 2013-07-02
CA2601730A1 (en) 2006-10-26
US8554887B2 (en) 2013-10-08

Similar Documents

Publication Publication Date Title
USRE44836E1 (en) System and method for efficient transfer of applications and data during device swap
US7747724B2 (en) System and method of device-to-server registration
US7870288B2 (en) Sharing data in scalable software blade architecture
US7779157B2 (en) Recovering a blade in scalable software blade architecture
US20140250068A1 (en) System for an open architecture deployment with centralized synchronization
US20060259523A1 (en) System and method of synchronization of internal data cache with wireless device application data repositories
GB2403040A (en) Application programming interface for provisioning services
US8340652B2 (en) System and method of waste management
US20070083664A1 (en) System and method of presenting entities of standard device applications in wireless devices
US7933880B2 (en) System and method of application persistence

Legal Events

Date Code Title Description
AS Assignment

Owner name: RESEARCH IN MOTION LIMITED, CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WALLIS, KENNETH;VITANOV, KAMEN B.;BIBR, VIERA;AND OTHERS;SIGNING DATES FROM 20060216 TO 20060217;REEL/FRAME:031060/0291

AS Assignment

Owner name: BLACKBERRY LIMITED, ONTARIO

Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:031847/0499

Effective date: 20130709

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552)

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12

AS Assignment

Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103

Effective date: 20230511

AS Assignment

Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND

Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064269/0001

Effective date: 20230511