US20080214163A1 - System for and method of backing up content for use on a mobile device - Google Patents
System for and method of backing up content for use on a mobile device Download PDFInfo
- Publication number
- US20080214163A1 US20080214163A1 US12/011,399 US1139908A US2008214163A1 US 20080214163 A1 US20080214163 A1 US 20080214163A1 US 1139908 A US1139908 A US 1139908A US 2008214163 A1 US2008214163 A1 US 2008214163A1
- Authority
- US
- United States
- Prior art keywords
- content
- mobile device
- mobile
- link
- mobile phone
- 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.)
- Abandoned
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/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1461—Backup scheduling policy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- 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/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
Definitions
- This invention is related to transmitting content to electronic devices. More specifically, this invention is related to systems for and methods of restoring content, updating content, storing equivalent content, and offering content for mobile devices such as mobile phones.
- Mobile phones and other electronic devices contain ever increasing content, with upgrades, equivalents, and other content created for them each year.
- Mobile phones for example, store address books, user-generated content such as digital images, and third-party content such as ringtones, wallpaper, and music files, to name only a few types of content.
- Content is not easily restored when the phone is deactivated. It is difficult for a user to remember what content was stored on the phone, the correct version of the content for a particular phone, or even where she acquired the content. Even if she can discover all this information, the process of restoring content to the phone is still time-consuming, error prone, and tedious.
- the new phone may require different versions of content: a simple transfer of content from the old to the new mobile phone will not work.
- a method of providing content to a mobile device includes determining a source of the content (e.g., a content provider) and transmitting the content from the source to a storage location accessible to the mobile device, such as directly on the mobile device.
- the content is transmitted wirelessly.
- Mobile devices include, but are not limited to, mobile telephones, personal digital assistants, and personal computers.
- Content includes, but is not limited to, a mobile application program, a mobile ring tone, a mobile wallpaper, video data, audio data, a digital image, a ring back tone, or a combination of these.
- the method also includes storing on the mobile device a selectable link for accessing the content on the storage location and storing data that associates the source with the content, the mobile device, or both.
- This data is used to determine what content has been acquired for the mobile device and the source (e.g., one or more content providers) that can be accessed to retrieve the content.
- the data includes a pathname to the source, such as one containing a Uniform Resource Locator, and identifiers for the content itself.
- the data is parsed to determine the source and the content.
- the data is stored on a system remote from the mobile device, so that when the mobile device retrieves the content it contacts the system, which communicates with the source to transmit the content to the mobile device.
- the source is determined by querying one or more locations for the content, such as third-party content providers.
- the content providers respond by transmitting the content (e.g., wirelessly) to the mobile device.
- a single aggregation interface is used to automatically retrieve content from multiple sources.
- a method of accessing content from a device includes selecting on the device a link to content stored on a storage system and automatically receiving the content on the device in response to selecting the link.
- the storage system is remote to the device and when the link is selected, a copy of the content is transmitted from the storage system to the device.
- the content is accessed by determining that the content is not stored on the storage system and then receiving the content on the storage system.
- content is determined to be on the storage system using a hash. A list containing the hash for each content on the storage system is maintained. If it is determined that a hash for desired content is not in the list, it is determined that the content is not on the storage system and must be retrieved from a content provider.
- a method of offering content for a first device includes storing a history of acquisitions associated with one or more entities and displaying on the first device offers for content based on the history.
- the one or more entities correspond to a user, to a mobile device, or to both.
- offers can be based on what was acquired for a particular mobile phone, for a particular user, or both.
- the offers are for purchasing, subscribing to, licensing, upgrading, or replacing content, or any combination of these.
- Content is updated, in part, by transcoding or resizing using content in the history.
- the method also includes automatically receiving replacement or updated content on the first device.
- the history is stored at a content provider location but can be stored at other locations.
- the method also includes polling the content provider location for an acquisition associated with the one or more entities, automatically receiving notification from the content provider location of an acquisition for the one or more entities, storing metadata about content acquired by the one or more entities, or any combination of these.
- the metadata includes a name for content, a description of content, a size of content, a format of content, an encoding of content, an author of content, or any combination of these.
- the history includes a count of license usages.
- a method of offering content for a device includes displaying a first list of content acquired for one or more entities and transmitting one or more items in the first list to a first mobile device. Preferably, from this first list, one or more of the items are selected for storing on the device.
- the first list is automatically transmitted to the first mobile device.
- the first list is displayed, and one or more items are selected from it and transmitted to the first mobile device from a location remote to the first mobile device.
- the method also includes selecting a second list of mobile devices and transmitting the one or more items to the mobile devices in the second list.
- the first list is generated from a history of acquisitions associated with a second mobile device.
- a method of configuring a device includes constructing from a first device a link to content on a storage system and storing the link on a second device.
- the second device is configured to access the same content available to the first device.
- storing the link includes storing the content and data for selecting the content.
- the link, the content, or both are wirelessly transmitted from the storage system to the second device during an initial configuration of the second device.
- the link, the content, or both are stored on the second device at predetermined time intervals.
- a mobile device in a sixth aspect of the present invention, includes a client module containing a link and programmed to access content using the link, preferably wirelessly.
- the client module is programmed to display icons for selecting replacement content for replacing content acquired for the mobile device.
- the replacement content includes an upgrade to content acquired for the mobile device or a different version of the content acquired for the mobile device.
- a content management system for a mobile device includes a first content module containing content and a delivery interface programmed to transfer content from the content module to a mobile device.
- the delivery interface is programmed to transfer content from the content module to a mobile device using a link to the content accessible to the mobile device.
- the system also includes a data store of acquired content, a replacement module for mapping acquired content to replacement content, and an interface programmed to receive content from one or more sources and to poll the one or more sources to determine content acquired from the one or more sources.
- the interface includes a connection module for connecting to sources using Uniform Resource Indicators to the one or more sources.
- the system also includes a parser for parsing the content to thereby determine the one or more sources.
- the one or more sources are third-party sources.
- the system also includes an offer module for generating offers for replacement content on the mobile device.
- the offer module is programmed to transmit data associated with the offers to the mobile device and the mobile device is programmed to display and select the offers.
- the offer module is also programmed to generate the offers from a history of acquisitions for one or more entities such as users or mobile phones.
- the system also includes a metadata store containing metadata about content.
- Metadata includes information indicating a manufacturer of a mobile device, a version of a mobile device, operating capabilities of a mobile device, or any combination of these.
- the operating capabilities include a screen size, a number of pixels, or both.
- the system also includes a Web-based interface coupled to the content manager and programmed to manage the content, a multimedia content data store, a user-generated content data store, and an application data store.
- FIG. 1 shows a mobile phone, a platform for restoring content, and a content provider in accordance with one embodiment of the present invention.
- FIG. 2 shows a mobile phone, a platform for restoring content, and multiple content providers in accordance with one embodiment of the present invention.
- FIG. 3 shows metadata stored on the platform in FIGS. 1 and 2 and used to locate and restore content in accordance with the present invention.
- FIG. 4 is a flowchart showing the steps in a process for restoring content to a mobile phone in accordance with one embodiment of the present invention.
- FIG. 5 shows a display on a mobile device, allowing a user to store equivalent content on the mobile device in accordance with one embodiment of the present invention.
- FIG. 6 shows a display on a mobile device, allowing a user to upgrade content on the mobile device in accordance with one embodiment of the present invention.
- FIG. 7 is a sequence diagram showing the steps for acquiring equivalent content in accordance with one embodiment of the present invention.
- FIGS. 8A and 8B show transferring links to content from one mobile phone to another in accordance with one embodiment of the present invention.
- FIG. 9 shows a display on a mobile phone and icons of different content and the corresponding links for acquiring the content in accordance with one embodiment of the present invention.
- FIG. 10 is a use-case diagram for restoring/acquiring content in accordance with one embodiment of the present invention.
- FIG. 11 is a use-case diagram for backing up content in accordance with one embodiment of the present invention.
- FIG. 12 shows the steps of purchasing content, transferring content, storing information for restoring content in accordance with one embodiment of the present invention.
- FIG. 13 shows user data stored at a content provider in accordance with one embodiment of the present invention.
- FIGS. 14-17 show components for acquiring, backing up, and restoring content in accordance with embodiments of the present invention.
- FIG. 18 is a sequence diagram for acquiring and restoring content in accordance with one embodiment of the present invention.
- FIG. 19A shows an interface for selecting content and configuring one or more mobile phones to store the selected content, in accordance with one embodiment of the present invention.
- FIG. 19B shows the selected mobile phones of FIG. 17A , after being configured to store the selected content, in accordance with one embodiment of the present invention.
- Embodiments of the present invention are directed to restoring, updating, and offering content on electronic devices, such as mobile telephones, personal digital assistants, personal computers, and the like.
- a link to content is stored on a mobile phone, allowing the mobile phone to automatically access multiple content stored at one or more remote (e.g., third-party) locations. In this way, content is accessed and stored on the mobile phone only when needed, thus using memory on the mobile phone more efficiently.
- FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
- FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
- FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
- FIG. 1 A block diagram illustrating an exemplary computing device.
- the present invention ensures the integrity of customer purchase data, restores already purchased content when a handset is restored, provides customers the opportunity to upgrade applications previously stored on a handset, conserves bandwidth since content is transferred only when restored on a handset, and allows users to transfer content, upgrades, or equivalent content on new handsets.
- Content includes, but is not limited to, address book contact data, user-generated pictures and sound recordings, ringtones, wallpapers, and videos purchased or subscribed from third-party content provides, and Binary Runtime Environment for Wireless (BREW) applications purchased through a Content Provider BREW mobile shop.
- BREW Binary Runtime Environment for Wireless
- FIG. 1 is a high-level diagram of components of a system in accordance with one embodiment of the present invention.
- the system includes a mobile phone 101 coupled to an intermediate platform 110 , which in turn is coupled to a content provider 120 .
- the mobile phone 101 contains both user-generated and other content 105 , such as ringtones, calendars, video images, audio data, wallpaper, etc.
- the platform 110 stores a user record 115 that contains a link to the content 105 at a content provider 120 .
- the mobile device 101 must restore content 105 , such as when it is reactivated or initialized, it notifies the platform 110 .
- the platform 110 contacts the content provider 120 , identifying the mobile phone 101 and, using the link to the content 105 , the content 105 .
- the content provider 120 then transmits the content 105 to the mobile phone 101 , which restores the content 105 .
- a user purchases or otherwise acquires content for the mobile phone 101 .
- the user record 115 is added to the platform 110 , and the content provider 120 records that the user (identified, for example, by the telephone number of the mobile phone) has purchased the content. Any license usage counts are initialized at this stage, so that the user is able to retrieve the content 105 only the allowed number of times.
- An icon is stored on the mobile phone 101 to access the platform 110 and thus ultimately the content provider 120 , as described herein.
- the mobile phone 101 and the platform 110 do not require extra storage for the content 105 , storing only links to it.
- content is stored at a content provider, from which the content is retrieved.
- This structure allows the content provider to keep track of and notify the user that updates and equivalent content, which are generally under the control of the content provider, are available.
- the content provider 120 is also able to substitute equivalent or updated content when available.
- the content 105 is stored on the platform 110 , from where it is transmitted to the mobile 101 .
- FIG. 1 shows the mobile device 101 and platform 110 coupled to a single content provider
- the mobile device 101 is able to contain content acquired from and thus to be restored by multiple content providers.
- FIG. 2 shows a system in which the mobile device 101 and platform 110 are both coupled to multiple content providers 120 A-D, which all function similarly to the content provider 120 in FIG. 1 .
- FIG. 1 shows a single user record 115
- the platform 110 will generally store multiple user record, for multiple users.
- the platform 110 is coupled to the multiple content providers 120 A-D through an aggregator 140 , which receives a request for content from the platform 110 and routes the request to the appropriate one of the multiple content providers 120 A-D containing the content sought.
- the aggregator 140 queries all content providers 120 A-D, and the one content provider hosting the content sought transmits it to the mobile phone 101 .
- the aggregator 140 is part of the platform 110 ; in an alternative embodiment, the aggregator 140 and the platform 110 are separate components.
- FIGS. 1 and 2 show lines directly connecting the components (e.g., directly connecting the mobile device 101 to the platform 110 ), the components are preferably coupled over a wireless network, or are coupled over a wide area network such as the Internet, over a local area network, or any combination of these.
- FIG. 3 shows the user record 115 according to one embodiment of the present invention.
- the user record 115 contains an identifier of the mobile phone 201 (the phone number, 15555551212), a uniform resource locator (URL) of the content provider 203 (contentprovider.com), a name of the content 205 (Tetris), a classifier of the content 207 (game), a version number of the content 209 (4.0), a size of the content 211 (500 kB), a format for displaying the content on the mobile device 213 (720p 1080i), an encoding scheme for the content (JPEG) 215 , an author of the content 217 (GameMaker), an identifier of the mobile phone 219 (PhoneVendor1), and a model of the mobile phone 221 (3.1).
- the user record 115 is able to contain other metadata, a subset of the metadata shown in FIG. 3 , or any combination of metadata suitable for identifying the content and communicating with the content provider 120 to transmit the content to the mobile phone 101 .
- the platform 110 parses the user record 115 to determine the source (e.g., URL 203 ) of the content provider from which the content is retrieved for storing on the mobile device 101 .
- the aggregator 140 of FIG. 2 polls the content provider locations 120 A-D to determine whether they contain content to be restored to the mobile phone 101 .
- FIG. 4 shows the steps 250 that each content provider location 120 A-D takes in response to the polling.
- the content provider 120 A receives a request to restore content to the mobile phone 101 .
- the request includes the telephone number of the mobile phone 101 ; alternatively, the request includes some other identifier of the mobile phone 101 or some identifier of the user of the mobile phone.
- the content provider 120 A looks up all the content that has been acquired for the mobile phone 101 .
- the content provider 120 A determines whether any upgrades are available for the acquired content and substitutes upgrades when available.
- the content provider 120 A transmits the content (including upgrades, if available) to the mobile phone 101 .
- the process ends in the step 259 . It will be appreciated that new content may be resized, reformatted, or otherwise changed to ensure that it performs or is displayed properly on the mobile device 101 .
- FIG. 5 shows the mobile device 101 , with a display offering content equivalent to what was previously acquired for the mobile device 101 (Tetras 3.1) and a selectable link 190 for acquiring the equivalent content.
- FIG. 6 shows the mobile phone 101 offering a list of upgrades, which the user has the option of accepting or declining.
- FIG. 7 is a sequence diagram 300 showing user data (e.g., metadata) on the platform 110 , updated when equivalent (or upgraded) content is transmitted to the mobile phone 101 .
- the user is presented on the mobile phone 101 with a list from which she can select equivalent content.
- the mobile phone 101 transmits to the content provider 120 a request for particular equivalent content.
- the content provider 120 transmits the equivalent content to the mobile phone 101 .
- the content provider 305 transmits information (e.g., metadata) to the platform 110 to reflect that the mobile phone 101 has now acquired the equivalent content (e.g., the previously acquired content has been replaced).
- the user record ( FIG. 3 ) is then updated to reflect that equivalent content has been acquired.
- the system must ensure that equivalent or other replacement content is selected so that it is compatible with the mobile device.
- equivalent content must be selected so that its binary, image size and device form factor, and its encoding format are all suitable for the mobile device.
- content providers or intermediate platforms maintain mapping databases that map content suitable for one device to content suitable for another device.
- a history of purchases, subscriptions, and other acquisitions are generated for the mobile phone 101 .
- this history is used to determine upgrades or equivalent content for the content acquired for the mobile phone 101 .
- the user of the mobile phone 101 is offered upgrades and equivalent content for content previously acquired for the mobile phone 101 , as well as offers for content similar or related to previously purchased content.
- FIG. 8A shows mobile phone 101 coupled to the platform 110 , which in turn is coupled to the content provider 120 .
- FIG. 8B shows a mobile phone 350 , an upgrade of the mobile phone 101 , coupled to the platform 110 and the content provider 120 .
- the mobile phone 350 when the mobile phone 350 is first activated, it automatically communicates with the platform 120 .
- the platform 120 is programmed to recognize that the mobile phone 350 is an upgrade of the mobile phone 101 and performs the steps of “restoring” content previously acquired for the mobile phone 101 to the mobile phone 350 , such as described above. This may occur because, for example, the mobile phone 350 is given the same phone number as the mobile phone 101 . Alternatively, the user of the mobile phone 350 identifies herself to the platform 110 and initiates “restoration” of content, such as described above.
- a mobile phone is programmed to store content efficiently.
- the mobile phone rather than store links to content on a remote platform (e.g., platform 110 , FIG. 1 ), the mobile phone itself stores links to content.
- the content is accessed using one or more icons displayed on the mobile phone.
- FIG. 9 shows a mobile phone 400 in accordance with one embodiment of the invention.
- the mobile phone 400 includes a display screen 405 showing icons 401 (Tetris), 402 (Chess game), and 403 (Train schedule).
- Each icon 401 - 403 has an associated link, 401 A- 403 A, respectively, such that when one of the icons 401 - 403 is selected, its associated link is accessed, thereby connecting the mobile device 400 to a content provider associated with the selected content (e.g., a third-party content provider) to trigger the content provider to download the content to the mobile phone 400 .
- a content provider associated with the selected content e.g., a third-party content provider
- the link 401 A associated with the icon 401 is the URL, contentprovider.com/tertris/4.0/15555551212, which contains the Web address of the content provider (contentprovider.com), the name of the content to be retrieved (Tetris), the version of the content (4.0), and the phone number of the mobile phone (5555551212).
- the content provider parses this URL, determines what content to store on the mobile phone 400 , and then, using the phone number of the mobile phone, transmits the content to the mobile phone 400 .
- the content is no longer used on the mobile phone 400 (e.g., the application is closed), it is removed from the mobile phone 400 . In this way, because the mobile phone 400 does not persistently maintain all the content it has access to, it can access content larger than its available memory.
- the content is retrieved from the content provider, it is stored on both the mobile phone 400 and on an intermediate storage location. In this way, any future retrieval of the content (which may be deleted on the mobile phone after use) is from the intermediate storage location, which functions as a proxy server.
- the link 401 A is updated to refer to the intermediate storage location.
- the content is not automatically deleted from the mobile phone after it is used. Instead, the content is removed manually and remains of the mobile device for future use.
- the mobile device 400 is programmed to first determine whether the associated content is available on the mobile phone 400 .
- the mobile phone 400 stores a hash of the content as part of the metadata about the content. The mobile phone 400 compares this hash against the hashes of all other content stored on the mobile phone 400 . If the mobile phone 400 determines that it does not contain the content, it will retrieve the content from the content provider, as described above.
- the content is stored on an intermediate platform, which stores and uses a hash to determine available content in a similar manner.
- the link 401 A is able to include metadata similar to the metadata 200 , which also contains an address of a third-party content provider (element 203 ).
- the icons 401 - 403 and associated links 401 A- 403 A are all able to be transferred to the new mobile phone. This may occur during an initial configuration of the new mobile phone.
- FIGS. 10 and 11 are use-case diagrams 500 and 600 , respectively, used to model backing up and restoring content in accordance with embodiments of the present invention.
- the use-case diagrams shown in this application use the well-known labels “uses,” “extends,” and “includes.” To make the diagrams more readable, cases that use the relationship “uses” are left unlabeled.
- a mobile device is able to subscribe to an application 501 , purchase an application 502 , end an application subscription 503 , delete an application 504 , access a “mobile shop” for the first time 505 , and perform a device restore 507 .
- All of the cases 501 - 504 are able to be extended to update a user application status datastore 521 .
- the case of performing a device restore is also able to deliver applications to the device 521 , deliver equivalent content to the device 523 , deliver user-generated (UG) content to the device 525 , and query a user application status datastore 527 . From the case of accessing a mobile shop for the first time 505 , the system is also able to perform device restore 507 .
- any application or content purchase or subscription is reported to and maintained in the backup system datastores.
- the subscribed applications, application settings, purchased multimedia content, and user-generated content are restored to the mobile device, as described herein.
- the mobile shop application can be configured to launch the restore process when it is launched for the first time on a device.
- a stub application may be preloaded onto the device. The stub application will launch shortly after the mobile phone is activated and provisioned and will prompt the user to restore applications and purchased content.
- Any business logic desired may be implemented in the client: application or content-specific rules may be applied and an appropriate user interface displayed to the user.
- these rules and user-interfaces include automatic no-fee download and installation of subscription-based applications, reduced-fee “repurchases” prompt for pay-per-download applications and content, no-fee download of operator-determined number of previously purchased ringtones, special reduced fees for particular previously purchased ringtones, reminders about previously downloaded but deleted applications, offers to continue previously initiated but subsequently canceled application subscriptions, and simple reminders (or recommended alternative applications) detailing what content the user had previously.
- FIG. 11 is a high-level use case diagram 600 for application and content backup and restore.
- a client is able to restore a phone 601 and backup an application 603 .
- a phone can be restored by restoring standard data 605 , restoring user-generated content 610 , restoring premium content 620 , and restoring applications 640 .
- User-generated content restores 610 can be restored by delivering user-generated content to a device, which in turn performs image transcoding 613 , video file transcoding 614 , and audio file transcoding 615 .
- Premium content is restored 620 by getting a purchase premium content list 621 , delivering premium content to the device 623 , and displaying application and content specific repurchase user interface 630 .
- Premium content is delivered to the device 623 by looking up equivalent premium content 625 and delivering premium content to the device 627 .
- Premium content is delivered to the device 627 by checking a content delivery policy 629 .
- An application is restored 640 by displaying an application and content specific repurchase user interface 630 , getting a purchased application list 641 , getting a subscribed application list 645 , and delivering the application to the device 650 . Both the cases of getting a purchased application list 641 and getting a subscribed application list 645 are extended by querying the application state database 643 .
- Applications are delivered to a device 650 by looking up equivalent applications 651 , checking the application delivery policy 653 , and updating the application state database 655 .
- An application is backed up 603 by registering a purchased application 660 , registering a subscribed application 665 , and backing up multimedia content 670 .
- a purchased application is registered 660 and a subscribed application is registered 665 by updating the application state database 655 .
- Multimedia content is backed up 670 by registering multimedia content purchase, which is extended by updating the multimedia content state database 673 .
- FIG. 12 shows the steps 680 of a process for acquiring content (e.g., purchase, license, etc.) for a mobile phone in accordance with one embodiment of the present invention.
- the process starts in the step 681 , and in the step 682 , the content is requested.
- the content is transferred from the content provider 120 to the mobile phone 101 .
- the user record 115 is stored on the intermediate platform 110 .
- the content provider 120 records the acquisition (along with other acquisitions for the mobile phone 101 ), used to later restore the mobile phone 101 .
- the acquisition is recorded in an acquisition table, such as shown in FIG. 13 .
- the process ends in the step 686 .
- FIG. 13 shows an “acquisition table” 690 maintained at the content provider 120 in accordance with one embodiment of the present invention
- the acquisition table 690 contains a history of a user's past acquisitions for the mobile phone 101 . Individual purchases are stored in individual records of the acquisition table 690 .
- the acquisition table 690 can be used to determine what content the content provider 120 provided to the mobile phone 101 , and thus what content (or equivalents or upgrades) is to be restored to the mobile phone 101 .
- the acquisition table 690 includes rows 691 - 694 .
- the row (also referred to as a “record”) 691 is used, among other things, to identify the mobile phone 101 .
- the record 691 contains a telephone number 691 A (15555551212) of the mobile phone 101 , a name (e.g., owner) 691 B associated with the mobile phone (“Joe Smith”), and an Internet address 691 C associated with the mobile phone “Address@domain.com”).
- the telephone number 691 A, the Internet address 691 C, or both can be used to transmit content to the mobile phone 101 in accordance with the present invention.
- the records 692 - 694 all contain information about previously acquired content.
- the record 692 indicates that the game Tetris ( 692 A), version 3.0 ( 692 B), for the phone brand Phonemaker1 ( 692 C) was acquired for the mobile phone 101 .
- Tetris 3.0 is purchased for the mobile phone 101
- the record 692 is added to the acquisition table 690 .
- the record 693 indicates that Chessgame ( 693 A), version 1.0 ( 693 B), for the phone brand Phonemaker1 ( 693 C) was acquired; and the record 694 indicates that the application “Train schedule” ( 694 A), version 3.0 ( 694 B), for the phone brand Phonemaker1 ( 694 C), was also acquired.
- acquisition table 690 is only illustrative. Those skilled in the art will recognize that acquisition tables containing other information can also be used in accordance with the present invention.
- FIGS. 14-17 show components used to implement embodiments of the present invention. Some of these components are described below.
- the backup client is preloaded on the mobile device and is programmed to implement the client-side business logic required for an application and content backup and restore system.
- the client's primary function is to present a user interface to the user which allows the user to backup content on the device, and in the case of a device migration or new device, retrieve the content to the new device.
- HTTP with a simple protocol encoded in it is used.
- the interface may also use opaque tokens, such as used with the Application/Multimedia Purchase and Restore Manager.
- this interface is also be programmed to parse metadata to determine the source of content.
- Application/Multimedia Purchase and Restore Manager This manager interfaces with the application billing system to determine which applications a user has purchased, subscribed to, or both, what equivalent application is appropriate for a given device, and a mechanism to push that application to the backup client.
- this manager generates data for offers of new content from user purchase histories and transmits these offers to the backup client.
- the Restore Manager communicates with the mobile phone using a wireless protocol such as Wireless Application Protocol (WAP).
- WAP Wireless Application Protocol
- mapping database is populated by entries from the content providers when they submit content for inclusion on the application/content catalog and may be updated as new versions of applications are provided for new platforms.
- mapping datastore is utilized by the portability interface to report which instance of a piece of content is appropriate for a given platform.
- the mapping datastore recommends a substitute content instance, if appropriate.
- mapping and equivalence databases which contain information allowing the client to retrieve the device-appropriate version of an application or premium content. These datastores are queried at restore time before downloading an application or instance of premium content.
- the synchronization server When contacted by the backup client at restore time, the synchronization server connects to each third-party content provider and queries its content portability interface to determine which content belonging to the provider should be restored to the handset. The appropriate content is retrieved over the same interface and provided to the backup client, which installs it on the handset to complete the restore process.
- the synchronization server provides a standardized interface to Web sites (such as an operator's customer-facing Web sites), which enables the Web site to provide information and actionable interfaces pertaining to the user's content.
- This layer is a conduit that connects to each of the third-party content suppliers and uses their interfaces to implement the business logic in accordance with the present invention. This layer is also able to poll content providers to determine what content was provided to a particular user or mobile phone.
- the content provider purchase history databases are populated by queries by the server-side components in the course of determining which applications may be offered to a user when restoring to the new device.
- FIG. 14 is a block diagram of a backup and restore system 700 in accordance with one embodiment of the present invention.
- the system 700 allows an operator or original device manufacturer (ODM) the ability to maintain control of the applications and multimedia content and its delivery system, while relying on the synchronization server to handle the details of what is installed on the mobile device (along with user-generated content).
- ODM original device manufacturer
- the system 700 includes a mobile device 705 (e.g., a mobile phone) coupled to a synchronization server platform 720 .
- the mobile device 705 includes a backup client 709 , an application datastore 707 , and a multimedia content datastore 711 .
- the synchronization server platform 720 includes a content delivery interface 721 , an application/multimedia purchase and restore manager 723 , user purchase history datastores 730 , multimedia content/application mapping datastores 740 , a user-generated content and application settings datastore 751 , a multimedia content datastore 753 , an application datastore 755 , and synchronization server platform components 760 .
- the backup client 709 sends a request to restore data to the content delivery interface 721 .
- the Application/Multimedia Purchase and Restore Manager 723 queries the user purchase history databases 730 to determine what the user has previously subscribed to (using the datastore 731 ) or purchased (using the datastores 733 and 735 ).
- the manager 723 also queries the multimedia content/application mapping datastores 740 to determine any equivalent content, and also generates new offers, if applicable.
- the content delivery interface 721 responds to the mobile device 705 with a list of content to be restored, including upgrades, updates, equivalents, and new offers, if any.
- the client 705 responds with a list of content to be restored.
- the platform 720 responds with user-generated content and applications settings (to ensure that the content is formatted for use on the mobile phone), as well as the multimedia content (from the datastore 753 ) and the application (from the datastore 755 ).
- the content-delivery interface 721 and the backup client communicate using HTTP. It will be appreciated, however, that other protocols such as HTTPS (HTTP Secure) and Secure Sockets Layer (SSL) can also be used.
- HTTPS HTTP Secure
- SSL Secure Sockets Layer
- FIGS. 15-17 are high-level diagrams of backup and restore systems 800 , 900 , and 1000 , respectively, in accordance with other embodiments of the present invention. Throughout this application, the same label refers to the same component.
- the systems 800 , 900 , and 1000 provide different levels of control over content among the mobile phone operators and the third-party content providers.
- the system 800 in FIG. 15 includes the mobile device 705 coupled to a synchronization server platform 850 and third-party content/application catalog components 810 .
- the components 810 function similarly to the intermediate platform 110 of FIG. 1 .
- the operator or original device manufacturer is able to maintain control of the applications and multimedia content and its delivery system, while relying on a synchronization server platform component 851 to control what is installed on the mobile device 705 .
- the synchronization server platform 850 includes an application/multimedia restore manager 855 , the synchronization server platform component 851 , the user purchase history datastores 730 , and a user-generated content datastore 860 .
- the third-party content/application catalog components 810 includes the content delivery interface 721 , the application datastore 755 , the multimedia content datastore 753 , the “Equivalent Application” mapping datastore 741 , the “Equivalent Multimedia Content” mapping datastore 743 , and a third-party mapping interface 845 .
- the client 709 is coupled to the application/multimedia restore manager 855 and the content delivery interface 721 , preferably using an HTTP interface.
- the synchronization server 850 is coupled to the third-party mapping interface 845 , also preferably using an HTTP interface.
- a third-party controls equivalent mapping information.
- the mobile device 705 communicates with the content delivery interface 721 , which recognizes the mobile device 705 by the URL used to request content, such as described above.
- the components 810 store applications and multimedia ( 755 and 753 ), from which some requests for content can be satisfied.
- the components 810 determine equivalent content, if any, using the mapping data stores 741 and 743, and then communicate with the synchronization server platform 850 using the third-party mapping interface 845 .
- the synchronization server platform responds by transmitting the requested content, or its equivalent, to the mobile device 705 , such as described above.
- FIG. 16 shows a system 900 for backing up content in accordance with another embodiment of the present invention.
- purchase information, application equivalency, and content delivery are all provided by a third party.
- the system 900 includes the mobile device 705 coupled to a platform 910 and a third-party content/application catalog of components 950 .
- the third-party content/application catalog of components 950 is similar to the catalog of components 810 , except that the user purchase history datastores 730 is included on the catalog 950 but not on the catalog 810 .
- FIG. 17 shows a system 1000 for backing up content in accordance with another embodiment of the present invention.
- the system 1000 includes the mobile device 705 coupled to a third-party content/application catalog of components 1010 .
- the third-party content/application catalog of components 1010 is similar to the catalog of components 950 , except that third-party mapping interface 845 in FIG. 14 is replaced with a content/application restore manager 1015 , which is coupled to the backup client 709 .
- FIG. 18 is a sequence diagram 1100 of interactions between a mobile device client, a synchronization platform server, and a content repository in accordance with one embodiment of the invention.
- the user starts a routine for acquiring (e.g., purchasing, licensing, taking a subscription to, etc.) content, and in the step 1115 , the client communicates with the server to register the new application, thereby updating the appropriate application datastore in the step 1120 .
- the user selects to purchase the application, and in the step 1130 , the client registers the purchased application on the server, thereby updating the application datastore in the step 1135 .
- the user indicates that she is done acquiring new content, and in the step 1145 the client notifies the server that the purchasing is complete.
- the datastore is updated in the step 1150 .
- the client notifies the server to restore the device.
- the device sends a command to query the subscriptions that have been acquired for the device.
- the server retrieves a list of subscribed applications, including equivalents, and returns this list to the client in the step 1170 .
- the client presents this list to the user, allowing her to select the content that she wants.
- the client requests the applications (original, equivalent, upgrades, etc.), which are returned to the client in the step 1185 .
- the applications are installed on the device.
- the mobile device requests the settings for the applications, which are retrieved in the step 1195 and installed on the device in the step 1199 .
- third-party content providers support a queryable interface, which allows the synchronization platform to retrieve, for a given user, a list of previously purchased content, metadata about items in the content catalog, equivalency data about previously purchased content, and a mechanism for retrieving equivalent content on a new handset.
- the list of previously purchased content can include a unique identifier that the synchronization platform presents to the content provider on subsequent calls to these interfaces, which provides an instance of content (e.g., “Who Let The Dogs Out Ringtone in MP3 @ 128 kbps).
- Metadata can include information such as the name, description size, and format of a particular content item in the catalog.
- Equivalency data can include, given a previously purchased content ID, new content ID appropriate for a given BREW platform ID.
- a preferred mechanism for retrieving equivalent content includes an interface that returns an HTTP Uniform Resource Locator (URL) via which binary data can be retrieved. When this interface is accessed, a third-party content provider can apply any digital rights management (DRM) desired, such as the remaining number of downloads allowed.
- DRM digital rights management
- Third-content providers are able to be queried in many ways.
- a third-party content provider is queried by accessing it using a URL that contains the query command.
- the URL contains a base URL path (here, “/la/fl cpi”) and a string that includes an operation code, an operation version number, and a user telephone number.
- the URL has the general form:
- Accessing the third-party content provider using the URL will return results such as a list of persistent, unique content instance identifiers.
- the query is to retrieve content details such as metadata about a particular instance on content owned by a third-party content provider.
- the querying URL is given as:
- a content portability interface can be queried to return a list of correct equivalent content and to return content URLs usable by the synchronization platform to download the appropriate version of a particular premium content item.
- Embodiments of the present invention provide an interface for configuring or updating mobile devices to access content available to other mobile devices.
- FIG. 19A shows a system 1200 that displays icons 1210 , 1220 , and 1230 , corresponding to Tetris, a Chess game, and a Train schedule application, respectively, and icons 1215 , 1225 , and 1235 , corresponding to a first mobile phone (Mobile phone 1 ), a second mobile phone (Mobile phone 2 ), and a third mobile phone (Mobile phone 3 ).
- FIG. 19A shows a system 1200 that displays icons 1210 , 1220 , and 1230 , corresponding to Tetris, a Chess game, and a Train schedule application, respectively, and icons 1215 , 1225 , and 1235 , corresponding to a first mobile phone (Mobile phone 1 ), a second mobile phone (Mobile phone 2 ), and a third mobile phone (Mobile phone 3 ).
- FIG. 19A shows a system 1200 that displays icons 1210 , 1220
- the icon 1210 is dragged and dropped to the icon 1215
- the icon 1220 is dragged and dropped to the icon 1225
- the icon 1230 is dragged and dropped to the icon 1235 .
- a link to the game Tetris on a content provider e.g., a URL
- the icon to the Tetris 401 and the corresponding link 401 A are stored on the Mobile phone 1 and the Mobile phone 2 , such as shown in FIG. 9 .
- an icon to the Chess game 402 and its associated link are also stored on the Mobile phone 2
- an icon to the Train schedule application 403 and its associated link 403 A are stored on the Mobile phone 3 .
- the icons 401 - 403 and the associated links 401 A- 403 A are transmitted to the Mobile phones 1 - 3 wirelessly.
- the system 1200 is programmed to receive icons and associated links from any one of the Mobile phones 1 - 3 .
- the system 1200 receives an icon and related link from the Mobile phone 1 .
- the icon is then displayed on the system 1200 , alone or in a list of other icons.
- the icon and associated link are then selected and transferred to the Mobile phones 2 and 3 , as discussed above.
- system 1200 can also be used to offer new content for the Mobile phones 1 - 3 . These new offers can be based on previous acquisitions for any one or more of the Mobile phones 1 - 3 , such as found in purchase history databases discussed above.
- the system 1200 can be programmed to offer content, list prices for content, and transmit content to mobile phones.
- links to content are automatically and periodically transferred from one mobile device to another so that the two are synchronized.
- links to content are stored on a platform remote to a mobile phone.
- the mobile phone communicates with a platform that associates the content with one or more content providers.
- the platform contacts the one or more contact providers, which directly transmit the content to the mobile phone.
- Replacement content such as upgrades, equivalent content, related content, and the like, can be offered to the mobile phone user, who can then select the replacement content, for a regular fee, a reduced fee, or even for no fee.
- Replacement content can be determined from a history of the user's past purchases, which is stored and used for this purpose.
- a link to content is stored on the mobile phone; when an icon on the mobile phone is selected, the mobile phone communicates directly with the content provider, which transmits the content to the mobile phone.
- links to content are stored on a central device and transmitted to selected mobile phones. In this way, a mobile phone can be configured so that it can access content previously accessible to another mobile phone.
Abstract
Description
- This application claims priority under 35 U.S.C. § 119(e) of both the co-pending U.S. provisional patent application Ser. No. 60/897,789, filed Jan. 26, 2007, and titled “CONTENT LOCKER, APPLICATION AND CONTENT BACKUP,” and the co-pending U.S. provisional patent application Ser. No. 60/937,314, filed Jun. 26, 2007, and titled “CONTENT LOCKER, APPLICATION AND CONTENT BACKUP,” both of which are hereby incorporated by reference in their entireties.
- This invention is related to transmitting content to electronic devices. More specifically, this invention is related to systems for and methods of restoring content, updating content, storing equivalent content, and offering content for mobile devices such as mobile phones.
- Mobile phones and other electronic devices contain ever increasing content, with upgrades, equivalents, and other content created for them each year. Mobile phones, for example, store address books, user-generated content such as digital images, and third-party content such as ringtones, wallpaper, and music files, to name only a few types of content. Content is not easily restored when the phone is deactivated. It is difficult for a user to remember what content was stored on the phone, the correct version of the content for a particular phone, or even where she acquired the content. Even if she can discover all this information, the process of restoring content to the phone is still time-consuming, error prone, and tedious.
- When restoring content to a phone, the user is also unaware of upgrades to content. Unknown to the user, a content provider may have released a new version of content or an equivalent, more popular version. The user misses an opportunity to get upgraded, more desirable content, and the content provider misses an opportunity to sell, license, or offer a subscription to new content.
- Users face these same problems when upgrading to a new phone or other device. The new phone may require different versions of content: a simple transfer of content from the old to the new mobile phone will not work.
- In a first aspect of the present invention, a method of providing content to a mobile device includes determining a source of the content (e.g., a content provider) and transmitting the content from the source to a storage location accessible to the mobile device, such as directly on the mobile device. Preferably, the content is transmitted wirelessly. Mobile devices include, but are not limited to, mobile telephones, personal digital assistants, and personal computers. Content includes, but is not limited to, a mobile application program, a mobile ring tone, a mobile wallpaper, video data, audio data, a digital image, a ring back tone, or a combination of these.
- In one embodiment, the method also includes storing on the mobile device a selectable link for accessing the content on the storage location and storing data that associates the source with the content, the mobile device, or both. This data is used to determine what content has been acquired for the mobile device and the source (e.g., one or more content providers) that can be accessed to retrieve the content. The data includes a pathname to the source, such as one containing a Uniform Resource Locator, and identifiers for the content itself. The data is parsed to determine the source and the content. Preferably, the data is stored on a system remote from the mobile device, so that when the mobile device retrieves the content it contacts the system, which communicates with the source to transmit the content to the mobile device.
- In one embodiment, the source is determined by querying one or more locations for the content, such as third-party content providers. The content providers respond by transmitting the content (e.g., wirelessly) to the mobile device. In one embodiment, a single aggregation interface is used to automatically retrieve content from multiple sources.
- In a second aspect of the present invention, a method of accessing content from a device includes selecting on the device a link to content stored on a storage system and automatically receiving the content on the device in response to selecting the link. The storage system is remote to the device and when the link is selected, a copy of the content is transmitted from the storage system to the device.
- Preferably, the content is accessed by determining that the content is not stored on the storage system and then receiving the content on the storage system. As one example, content is determined to be on the storage system using a hash. A list containing the hash for each content on the storage system is maintained. If it is determined that a hash for desired content is not in the list, it is determined that the content is not on the storage system and must be retrieved from a content provider.
- In a third aspect of the present invention, a method of offering content for a first device includes storing a history of acquisitions associated with one or more entities and displaying on the first device offers for content based on the history. The one or more entities correspond to a user, to a mobile device, or to both. In other words, offers can be based on what was acquired for a particular mobile phone, for a particular user, or both. The offers are for purchasing, subscribing to, licensing, upgrading, or replacing content, or any combination of these.
- Content is updated, in part, by transcoding or resizing using content in the history. In one embodiment, the method also includes automatically receiving replacement or updated content on the first device. Preferably, the history is stored at a content provider location but can be stored at other locations.
- In one embodiment, the method also includes polling the content provider location for an acquisition associated with the one or more entities, automatically receiving notification from the content provider location of an acquisition for the one or more entities, storing metadata about content acquired by the one or more entities, or any combination of these. The metadata includes a name for content, a description of content, a size of content, a format of content, an encoding of content, an author of content, or any combination of these. The history includes a count of license usages.
- In a fourth aspect of the present invention, a method of offering content for a device includes displaying a first list of content acquired for one or more entities and transmitting one or more items in the first list to a first mobile device. Preferably, from this first list, one or more of the items are selected for storing on the device.
- In one embodiment, the first list is automatically transmitted to the first mobile device. The first list is displayed, and one or more items are selected from it and transmitted to the first mobile device from a location remote to the first mobile device. The method also includes selecting a second list of mobile devices and transmitting the one or more items to the mobile devices in the second list. The first list is generated from a history of acquisitions associated with a second mobile device.
- In a fifth aspect of the present invention, a method of configuring a device includes constructing from a first device a link to content on a storage system and storing the link on a second device. Thus, the second device is configured to access the same content available to the first device. Preferably, storing the link includes storing the content and data for selecting the content. The link, the content, or both are wirelessly transmitted from the storage system to the second device during an initial configuration of the second device. Alternatively, the link, the content, or both are stored on the second device at predetermined time intervals.
- In a sixth aspect of the present invention, a mobile device includes a client module containing a link and programmed to access content using the link, preferably wirelessly. The client module is programmed to display icons for selecting replacement content for replacing content acquired for the mobile device. The replacement content includes an upgrade to content acquired for the mobile device or a different version of the content acquired for the mobile device.
- In a seventh aspect of the present invention, a content management system for a mobile device includes a first content module containing content and a delivery interface programmed to transfer content from the content module to a mobile device. The delivery interface is programmed to transfer content from the content module to a mobile device using a link to the content accessible to the mobile device.
- The system also includes a data store of acquired content, a replacement module for mapping acquired content to replacement content, and an interface programmed to receive content from one or more sources and to poll the one or more sources to determine content acquired from the one or more sources. The interface includes a connection module for connecting to sources using Uniform Resource Indicators to the one or more sources. In one embodiment, the system also includes a parser for parsing the content to thereby determine the one or more sources. Preferably, the one or more sources are third-party sources.
- In one embodiment, the system also includes an offer module for generating offers for replacement content on the mobile device. The offer module is programmed to transmit data associated with the offers to the mobile device and the mobile device is programmed to display and select the offers. The offer module is also programmed to generate the offers from a history of acquisitions for one or more entities such as users or mobile phones.
- Preferably, the system also includes a metadata store containing metadata about content. Metadata includes information indicating a manufacturer of a mobile device, a version of a mobile device, operating capabilities of a mobile device, or any combination of these. The operating capabilities include a screen size, a number of pixels, or both.
- In one embodiment, the system also includes a Web-based interface coupled to the content manager and programmed to manage the content, a multimedia content data store, a user-generated content data store, and an application data store.
-
FIG. 1 shows a mobile phone, a platform for restoring content, and a content provider in accordance with one embodiment of the present invention. -
FIG. 2 shows a mobile phone, a platform for restoring content, and multiple content providers in accordance with one embodiment of the present invention. -
FIG. 3 shows metadata stored on the platform inFIGS. 1 and 2 and used to locate and restore content in accordance with the present invention. -
FIG. 4 is a flowchart showing the steps in a process for restoring content to a mobile phone in accordance with one embodiment of the present invention. -
FIG. 5 shows a display on a mobile device, allowing a user to store equivalent content on the mobile device in accordance with one embodiment of the present invention. -
FIG. 6 shows a display on a mobile device, allowing a user to upgrade content on the mobile device in accordance with one embodiment of the present invention. -
FIG. 7 is a sequence diagram showing the steps for acquiring equivalent content in accordance with one embodiment of the present invention. -
FIGS. 8A and 8B show transferring links to content from one mobile phone to another in accordance with one embodiment of the present invention. -
FIG. 9 shows a display on a mobile phone and icons of different content and the corresponding links for acquiring the content in accordance with one embodiment of the present invention. -
FIG. 10 is a use-case diagram for restoring/acquiring content in accordance with one embodiment of the present invention. -
FIG. 11 is a use-case diagram for backing up content in accordance with one embodiment of the present invention. -
FIG. 12 shows the steps of purchasing content, transferring content, storing information for restoring content in accordance with one embodiment of the present invention. -
FIG. 13 shows user data stored at a content provider in accordance with one embodiment of the present invention. -
FIGS. 14-17 show components for acquiring, backing up, and restoring content in accordance with embodiments of the present invention. -
FIG. 18 is a sequence diagram for acquiring and restoring content in accordance with one embodiment of the present invention. -
FIG. 19A shows an interface for selecting content and configuring one or more mobile phones to store the selected content, in accordance with one embodiment of the present invention. -
FIG. 19B shows the selected mobile phones ofFIG. 17A , after being configured to store the selected content, in accordance with one embodiment of the present invention. - Embodiments of the present invention are directed to restoring, updating, and offering content on electronic devices, such as mobile telephones, personal digital assistants, personal computers, and the like.
- Different embodiments of the present invention are able to restore content to an electronic device in different ways. In one embodiment, a link to content is stored on a mobile phone, allowing the mobile phone to automatically access multiple content stored at one or more remote (e.g., third-party) locations. In this way, content is accessed and stored on the mobile phone only when needed, thus using memory on the mobile phone more efficiently.
- Other embodiments ensure continued access to subscribed content, even when the mobile phone is deactivated. For example, when a mobile phone is deactivated and then reactivated, or when service to one mobile phone is migrated to another mobile phone, the user is able to seamlessly restore access to the subscribed content.
- Other embodiments allow a user to substitute content on a mobile device. As one example, when a mobile phone is reactivated, the mobile phone is restored with an upgrade of content previously stored on the mobile phone or its equivalent. The content provider thus increases its opportunities to sell to customers content or subscriptions to content, and gives customers opportunities to get the latest version of content.
- In general, the present invention ensures the integrity of customer purchase data, restores already purchased content when a handset is restored, provides customers the opportunity to upgrade applications previously stored on a handset, conserves bandwidth since content is transferred only when restored on a handset, and allows users to transfer content, upgrades, or equivalent content on new handsets. Content includes, but is not limited to, address book contact data, user-generated pictures and sound recordings, ringtones, wallpapers, and videos purchased or subscribed from third-party content provides, and Binary Runtime Environment for Wireless (BREW) applications purchased through a Content Provider BREW mobile shop.
-
FIG. 1 is a high-level diagram of components of a system in accordance with one embodiment of the present invention. The system includes amobile phone 101 coupled to anintermediate platform 110, which in turn is coupled to acontent provider 120. Themobile phone 101 contains both user-generated andother content 105, such as ringtones, calendars, video images, audio data, wallpaper, etc. Theplatform 110 stores auser record 115 that contains a link to thecontent 105 at acontent provider 120. When themobile device 101 must restorecontent 105, such as when it is reactivated or initialized, it notifies theplatform 110. Theplatform 110 contacts thecontent provider 120, identifying themobile phone 101 and, using the link to thecontent 105, thecontent 105. Thecontent provider 120 then transmits thecontent 105 to themobile phone 101, which restores thecontent 105. - During device set up, a user purchases or otherwise acquires content for the
mobile phone 101. When the purchase is made, theuser record 115 is added to theplatform 110, and thecontent provider 120 records that the user (identified, for example, by the telephone number of the mobile phone) has purchased the content. Any license usage counts are initialized at this stage, so that the user is able to retrieve thecontent 105 only the allowed number of times. An icon is stored on themobile phone 101 to access theplatform 110 and thus ultimately thecontent provider 120, as described herein. - Advantageously, the
mobile phone 101 and theplatform 110 do not require extra storage for thecontent 105, storing only links to it. Preferably, content is stored at a content provider, from which the content is retrieved. This structure allows the content provider to keep track of and notify the user that updates and equivalent content, which are generally under the control of the content provider, are available. Thecontent provider 120 is also able to substitute equivalent or updated content when available. In alternative embodiments, thecontent 105 is stored on theplatform 110, from where it is transmitted to the mobile 101. - While
FIG. 1 shows themobile device 101 andplatform 110 coupled to a single content provider, it will be appreciated that themobile device 101 is able to contain content acquired from and thus to be restored by multiple content providers. Thus,FIG. 2 shows a system in which themobile device 101 andplatform 110 are both coupled tomultiple content providers 120A-D, which all function similarly to thecontent provider 120 inFIG. 1 . It will also be appreciated that whileFIG. 1 shows asingle user record 115, theplatform 110 will generally store multiple user record, for multiple users. - Preferably, the
platform 110 is coupled to themultiple content providers 120A-D through anaggregator 140, which receives a request for content from theplatform 110 and routes the request to the appropriate one of themultiple content providers 120A-D containing the content sought. Alternatively, theaggregator 140 queries allcontent providers 120A-D, and the one content provider hosting the content sought transmits it to themobile phone 101. In a preferred embodiment, theaggregator 140 is part of theplatform 110; in an alternative embodiment, theaggregator 140 and theplatform 110 are separate components. - It will be appreciated that although
FIGS. 1 and 2 show lines directly connecting the components (e.g., directly connecting themobile device 101 to the platform 110), the components are preferably coupled over a wireless network, or are coupled over a wide area network such as the Internet, over a local area network, or any combination of these. -
FIG. 3 shows theuser record 115 according to one embodiment of the present invention. Theuser record 115 contains an identifier of the mobile phone 201 (the phone number, 15555551212), a uniform resource locator (URL) of the content provider 203 (contentprovider.com), a name of the content 205 (Tetris), a classifier of the content 207 (game), a version number of the content 209 (4.0), a size of the content 211 (500 kB), a format for displaying the content on the mobile device 213 (720p 1080i), an encoding scheme for the content (JPEG) 215, an author of the content 217 (GameMaker), an identifier of the mobile phone 219 (PhoneVendor1), and a model of the mobile phone 221 (3.1). Those skilled in the art will recognize that theuser record 115 is able to contain other metadata, a subset of the metadata shown inFIG. 3 , or any combination of metadata suitable for identifying the content and communicating with thecontent provider 120 to transmit the content to themobile phone 101. In operation, theplatform 110 parses theuser record 115 to determine the source (e.g., URL 203) of the content provider from which the content is retrieved for storing on themobile device 101. - As discussed above, in one embodiment, the
aggregator 140 ofFIG. 2 polls thecontent provider locations 120A-D to determine whether they contain content to be restored to themobile phone 101.FIG. 4 shows thesteps 250 that eachcontent provider location 120A-D takes in response to the polling. Referring to the exemplarycontent provider location 120A, first, in thestep 251, thecontent provider 120A receives a request to restore content to themobile phone 101. Preferably, the request includes the telephone number of themobile phone 101; alternatively, the request includes some other identifier of themobile phone 101 or some identifier of the user of the mobile phone. In thestep 253, thecontent provider 120A looks up all the content that has been acquired for themobile phone 101. In thestep 255, thecontent provider 120A determines whether any upgrades are available for the acquired content and substitutes upgrades when available. In thestep 257, thecontent provider 120A transmits the content (including upgrades, if available) to themobile phone 101. The process ends in thestep 259. It will be appreciated that new content may be resized, reformatted, or otherwise changed to ensure that it performs or is displayed properly on themobile device 101. - In other embodiments, discussed below, if neither previously acquired content nor an upgrade is available, equivalent content is transmitted to the
mobile phone 101 in thestep 257. In still other embodiments, the user of the mobile phone is given the option of acquiring an upgrade or equivalent content.FIG. 5 shows themobile device 101, with a display offering content equivalent to what was previously acquired for the mobile device 101 (Tetras 3.1) and aselectable link 190 for acquiring the equivalent content. -
FIG. 6 shows themobile phone 101 offering a list of upgrades, which the user has the option of accepting or declining. -
FIG. 7 is a sequence diagram 300 showing user data (e.g., metadata) on theplatform 110, updated when equivalent (or upgraded) content is transmitted to themobile phone 101. Preferably, the user is presented on themobile phone 101 with a list from which she can select equivalent content. After selecting equivalent content, in thestep 301, themobile phone 101 transmits to the content provider 120 a request for particular equivalent content. In thestep 303, thecontent provider 120 transmits the equivalent content to themobile phone 101. In thestep 305, thecontent provider 305 transmits information (e.g., metadata) to theplatform 110 to reflect that themobile phone 101 has now acquired the equivalent content (e.g., the previously acquired content has been replaced). The user record (FIG. 3 ) is then updated to reflect that equivalent content has been acquired. - The system must ensure that equivalent or other replacement content is selected so that it is compatible with the mobile device. Thus equivalent content must be selected so that its binary, image size and device form factor, and its encoding format are all suitable for the mobile device. To this end, content providers (or intermediate platforms) maintain mapping databases that map content suitable for one device to content suitable for another device.
- Preferably, a history of purchases, subscriptions, and other acquisitions are generated for the
mobile phone 101. As discussed below, this history is used to determine upgrades or equivalent content for the content acquired for themobile phone 101. Based on this history, the user of themobile phone 101 is offered upgrades and equivalent content for content previously acquired for themobile phone 101, as well as offers for content similar or related to previously purchased content. - It will be appreciated that embodiments of the present invention are able to be used, not only to restore content to a mobile phone, but also to migrate content from one mobile phone to another. Thus, for example, a user may upgrade his mobile phone and wishes to transfer content from the mobile phone to a new one.
FIG. 8A showsmobile phone 101 coupled to theplatform 110, which in turn is coupled to thecontent provider 120.FIG. 8B shows amobile phone 350, an upgrade of themobile phone 101, coupled to theplatform 110 and thecontent provider 120. In one embodiment, when themobile phone 350 is first activated, it automatically communicates with theplatform 120. Theplatform 120 is programmed to recognize that themobile phone 350 is an upgrade of themobile phone 101 and performs the steps of “restoring” content previously acquired for themobile phone 101 to themobile phone 350, such as described above. This may occur because, for example, themobile phone 350 is given the same phone number as themobile phone 101. Alternatively, the user of themobile phone 350 identifies herself to theplatform 110 and initiates “restoration” of content, such as described above. - In still other embodiments of the invention, a mobile phone is programmed to store content efficiently. In one embodiment, rather than store links to content on a remote platform (e.g.,
platform 110,FIG. 1 ), the mobile phone itself stores links to content. Preferably, the content is accessed using one or more icons displayed on the mobile phone.FIG. 9 shows amobile phone 400 in accordance with one embodiment of the invention. Themobile phone 400 includes adisplay screen 405 showing icons 401 (Tetris), 402 (Chess game), and 403 (Train schedule). Each icon 401-403 has an associated link, 401A-403A, respectively, such that when one of the icons 401-403 is selected, its associated link is accessed, thereby connecting themobile device 400 to a content provider associated with the selected content (e.g., a third-party content provider) to trigger the content provider to download the content to themobile phone 400. - As one example, the
link 401A associated with theicon 401 is the URL, contentprovider.com/tertris/4.0/15555551212, which contains the Web address of the content provider (contentprovider.com), the name of the content to be retrieved (Tetris), the version of the content (4.0), and the phone number of the mobile phone (5555551212). When contacted, the content provider parses this URL, determines what content to store on themobile phone 400, and then, using the phone number of the mobile phone, transmits the content to themobile phone 400. Preferably, once the content is no longer used on the mobile phone 400 (e.g., the application is closed), it is removed from themobile phone 400. In this way, because themobile phone 400 does not persistently maintain all the content it has access to, it can access content larger than its available memory. - In an alternative embodiment, once the content is retrieved from the content provider, it is stored on both the
mobile phone 400 and on an intermediate storage location. In this way, any future retrieval of the content (which may be deleted on the mobile phone after use) is from the intermediate storage location, which functions as a proxy server. In this embodiment, thelink 401A is updated to refer to the intermediate storage location. - In one embodiment, the content is not automatically deleted from the mobile phone after it is used. Instead, the content is removed manually and remains of the mobile device for future use. Again using the
icon 401 and its associated link as an example, when theicon 401 is selected, themobile device 400 is programmed to first determine whether the associated content is available on themobile phone 400. Preferably, themobile phone 400 stores a hash of the content as part of the metadata about the content. Themobile phone 400 compares this hash against the hashes of all other content stored on themobile phone 400. If themobile phone 400 determines that it does not contain the content, it will retrieve the content from the content provider, as described above. Alternatively, the content is stored on an intermediate platform, which stores and uses a hash to determine available content in a similar manner. - It will be appreciated that features of each embodiments described in this application can be used on other embodiments. For example, the
link 401A is able to include metadata similar to themetadata 200, which also contains an address of a third-party content provider (element 203). Similarly, when updating or changing mobile phones, the icons 401-403 and associatedlinks 401A-403A are all able to be transferred to the new mobile phone. This may occur during an initial configuration of the new mobile phone. -
FIGS. 10 and 11 are use-case diagrams 500 and 600, respectively, used to model backing up and restoring content in accordance with embodiments of the present invention. The use-case diagrams shown in this application use the well-known labels “uses,” “extends,” and “includes.” To make the diagrams more readable, cases that use the relationship “uses” are left unlabeled. - Referring to
FIG. 10 , a mobile device is able to subscribe to anapplication 501, purchase anapplication 502, end anapplication subscription 503, delete anapplication 504, access a “mobile shop” for thefirst time 505, and perform a device restore 507. All of the cases 501-504 are able to be extended to update a userapplication status datastore 521. The case of performing a device restore is also able to deliver applications to thedevice 521, deliver equivalent content to thedevice 523, deliver user-generated (UG) content to thedevice 525, and query a userapplication status datastore 527. From the case of accessing a mobile shop for thefirst time 505, the system is also able to perform device restore 507. - As illustrated in
FIG. 10 , any application or content purchase or subscription is reported to and maintained in the backup system datastores. When a restore is initiated, the subscribed applications, application settings, purchased multimedia content, and user-generated content are restored to the mobile device, as described herein. - One popular trigger for a mobile device restore is the initiation of the on-device mobile shop. The mobile shop application can be configured to launch the restore process when it is launched for the first time on a device. Alternatively, a stub application may be preloaded onto the device. The stub application will launch shortly after the mobile phone is activated and provisioned and will prompt the user to restore applications and purchased content.
- Any business logic desired may be implemented in the client: application or content-specific rules may be applied and an appropriate user interface displayed to the user. Examples of these rules and user-interfaces include automatic no-fee download and installation of subscription-based applications, reduced-fee “repurchases” prompt for pay-per-download applications and content, no-fee download of operator-determined number of previously purchased ringtones, special reduced fees for particular previously purchased ringtones, reminders about previously downloaded but deleted applications, offers to continue previously initiated but subsequently canceled application subscriptions, and simple reminders (or recommended alternative applications) detailing what content the user had previously.
-
FIG. 11 is a high-level use case diagram 600 for application and content backup and restore. As shown in the use-case diagram 600, a client is able to restore aphone 601 and backup anapplication 603. A phone can be restored by restoringstandard data 605, restoring user-generatedcontent 610, restoringpremium content 620, and restoringapplications 640. User-generated content restores 610 can be restored by delivering user-generated content to a device, which in turn performsimage transcoding 613,video file transcoding 614, andaudio file transcoding 615. - Premium content is restored 620 by getting a purchase
premium content list 621, delivering premium content to thedevice 623, and displaying application and content specificrepurchase user interface 630. Premium content is delivered to thedevice 623 by looking upequivalent premium content 625 and delivering premium content to thedevice 627. Premium content is delivered to thedevice 627 by checking acontent delivery policy 629. - An application is restored 640 by displaying an application and content specific
repurchase user interface 630, getting a purchasedapplication list 641, getting a subscribedapplication list 645, and delivering the application to thedevice 650. Both the cases of getting a purchasedapplication list 641 and getting a subscribedapplication list 645 are extended by querying theapplication state database 643. - Applications are delivered to a
device 650 by looking upequivalent applications 651, checking theapplication delivery policy 653, and updating theapplication state database 655. - An application is backed up 603 by registering a purchased
application 660, registering a subscribedapplication 665, and backing upmultimedia content 670. A purchased application is registered 660 and a subscribed application is registered 665 by updating theapplication state database 655. Multimedia content is backed up 670 by registering multimedia content purchase, which is extended by updating the multimediacontent state database 673. -
FIG. 12 shows thesteps 680 of a process for acquiring content (e.g., purchase, license, etc.) for a mobile phone in accordance with one embodiment of the present invention. Referring toFIGS. 1 and 12 , the process starts in thestep 681, and in thestep 682, the content is requested. In thestep 683, the content is transferred from thecontent provider 120 to themobile phone 101. In thestep 684, theuser record 115 is stored on theintermediate platform 110. In thestep 685, thecontent provider 120 records the acquisition (along with other acquisitions for the mobile phone 101), used to later restore themobile phone 101. In one embodiment, the acquisition is recorded in an acquisition table, such as shown inFIG. 13 . The process ends in thestep 686. -
FIG. 13 shows an “acquisition table” 690 maintained at thecontent provider 120 in accordance with one embodiment of the present invention The acquisition table 690 contains a history of a user's past acquisitions for themobile phone 101. Individual purchases are stored in individual records of the acquisition table 690. When thecontent provider 120 is later polled, the acquisition table 690 can be used to determine what content thecontent provider 120 provided to themobile phone 101, and thus what content (or equivalents or upgrades) is to be restored to themobile phone 101. - The acquisition table 690 includes rows 691-694. The row (also referred to as a “record”) 691 is used, among other things, to identify the
mobile phone 101. Therecord 691 contains a telephone number 691A (15555551212) of themobile phone 101, a name (e.g., owner) 691B associated with the mobile phone (“Joe Smith”), and anInternet address 691C associated with the mobile phone “Address@domain.com”). The telephone number 691A, theInternet address 691C, or both can be used to transmit content to themobile phone 101 in accordance with the present invention. - The records 692-694 all contain information about previously acquired content. For example, the
record 692 indicates that the game Tetris (692A), version 3.0 (692B), for the phone brand Phonemaker1 (692C) was acquired for themobile phone 101. Thus, for example, when Tetris 3.0 is purchased for themobile phone 101, therecord 692 is added to the acquisition table 690. In a similar manner, therecord 693 indicates that Chessgame (693A), version 1.0 (693B), for the phone brand Phonemaker1 (693C) was acquired; and therecord 694 indicates that the application “Train schedule” (694A), version 3.0 (694B), for the phone brand Phonemaker1 (694C), was also acquired. - It will be appreciated that the acquisition table 690 is only illustrative. Those skilled in the art will recognize that acquisition tables containing other information can also be used in accordance with the present invention.
-
FIGS. 14-17 show components used to implement embodiments of the present invention. Some of these components are described below. - The backup client is preloaded on the mobile device and is programmed to implement the client-side business logic required for an application and content backup and restore system. The client's primary function is to present a user interface to the user which allows the user to backup content on the device, and in the case of a device migration or new device, retrieve the content to the new device.
- This is a server-side interface that provides programmed retrieval of the applications and premium content from a server-side database. Preferably, HTTP with a simple protocol encoded in it is used. The interface may also use opaque tokens, such as used with the Application/Multimedia Purchase and Restore Manager. Preferably, this interface is also be programmed to parse metadata to determine the source of content. Application/Multimedia Purchase and Restore Manager This manager interfaces with the application billing system to determine which applications a user has purchased, subscribed to, or both, what equivalent application is appropriate for a given device, and a mechanism to push that application to the backup client. Preferably, this manager generates data for offers of new content from user purchase histories and transmits these offers to the backup client. Preferably, the Restore Manager communicates with the mobile phone using a wireless protocol such as Wireless Application Protocol (WAP).
- An extended version of the currently available datastore, which shows which applications supersede existing applications, and which application binary is appropriate for a given mobile device. Preferably, the mapping database is populated by entries from the content providers when they submit content for inclusion on the application/content catalog and may be updated as new versions of applications are provided for new platforms.
- These databases map from a particular piece of content (e.g., “Who Let the Dogs Out” ringtone) to a number of platform-specific formats. The mapping datastore is utilized by the portability interface to report which instance of a piece of content is appropriate for a given platform. Preferably, if a piece of content is not available for a given platform, the mapping datastore recommends a substitute content instance, if appropriate.
- Content and application providers provide and maintain mapping and equivalence databases, which contain information allowing the client to retrieve the device-appropriate version of an application or premium content. These datastores are queried at restore time before downloading an application or instance of premium content.
- This is the third-party implementation of a specified interface that allows the synchronization platform to determine which of the third-party's content a given user has purchased, metadata about the content in question (e.g., ringtone title and description), which equivalent content should be provided to the device, and a URL that the synchronization platform can access to retrieve the content from the third party.
- When contacted by the backup client at restore time, the synchronization server connects to each third-party content provider and queries its content portability interface to determine which content belonging to the provider should be restored to the handset. The appropriate content is retrieved over the same interface and provided to the backup client, which installs it on the handset to complete the restore process.
- The synchronization server provides a standardized interface to Web sites (such as an operator's customer-facing Web sites), which enables the Web site to provide information and actionable interfaces pertaining to the user's content.
- This layer is a conduit that connects to each of the third-party content suppliers and uses their interfaces to implement the business logic in accordance with the present invention. This layer is also able to poll content providers to determine what content was provided to a particular user or mobile phone.
- The content provider purchase history databases are populated by queries by the server-side components in the course of determining which applications may be offered to a user when restoring to the new device.
-
FIG. 14 is a block diagram of a backup and restoresystem 700 in accordance with one embodiment of the present invention. Thesystem 700 allows an operator or original device manufacturer (ODM) the ability to maintain control of the applications and multimedia content and its delivery system, while relying on the synchronization server to handle the details of what is installed on the mobile device (along with user-generated content). Thesystem 700 includes a mobile device 705 (e.g., a mobile phone) coupled to asynchronization server platform 720. Themobile device 705 includes abackup client 709, anapplication datastore 707, and amultimedia content datastore 711. Thesynchronization server platform 720 includes acontent delivery interface 721, an application/multimedia purchase and restoremanager 723, userpurchase history datastores 730, multimedia content/application mapping datastores 740, a user-generated content and application settings datastore 751, amultimedia content datastore 753, anapplication datastore 755, and synchronizationserver platform components 760. - In operation, when content is restored to the
mobile device 705, thebackup client 709 sends a request to restore data to thecontent delivery interface 721. The Application/Multimedia Purchase andRestore Manager 723 queries the userpurchase history databases 730 to determine what the user has previously subscribed to (using the datastore 731) or purchased (using thedatastores 733 and 735). Themanager 723 also queries the multimedia content/application mapping datastores 740 to determine any equivalent content, and also generates new offers, if applicable. Thecontent delivery interface 721 responds to themobile device 705 with a list of content to be restored, including upgrades, updates, equivalents, and new offers, if any. Theclient 705 responds with a list of content to be restored. Theplatform 720 responds with user-generated content and applications settings (to ensure that the content is formatted for use on the mobile phone), as well as the multimedia content (from the datastore 753) and the application (from the datastore 755). - Preferably, the content-
delivery interface 721 and the backup client communicate using HTTP. It will be appreciated, however, that other protocols such as HTTPS (HTTP Secure) and Secure Sockets Layer (SSL) can also be used. -
FIGS. 15-17 are high-level diagrams of backup and restoresystems systems - The
system 800 inFIG. 15 includes themobile device 705 coupled to asynchronization server platform 850 and third-party content/application catalog components 810. Preferably, thecomponents 810 function similarly to theintermediate platform 110 ofFIG. 1 . In thesystem 800, the operator or original device manufacturer is able to maintain control of the applications and multimedia content and its delivery system, while relying on a synchronizationserver platform component 851 to control what is installed on themobile device 705. Thesynchronization server platform 850 includes an application/multimedia restoremanager 855, the synchronizationserver platform component 851, the userpurchase history datastores 730, and a user-generatedcontent datastore 860. - The third-party content/
application catalog components 810 includes thecontent delivery interface 721, theapplication datastore 755, themultimedia content datastore 753, the “Equivalent Application”mapping datastore 741, the “Equivalent Multimedia Content”mapping datastore 743, and a third-party mapping interface 845. - As shown in
FIG. 15 , theclient 709 is coupled to the application/multimedia restoremanager 855 and thecontent delivery interface 721, preferably using an HTTP interface. Thesynchronization server 850 is coupled to the third-party mapping interface 845, also preferably using an HTTP interface. In this embodiment, a third-party controls equivalent mapping information. - In operation, the
mobile device 705 communicates with thecontent delivery interface 721, which recognizes themobile device 705 by the URL used to request content, such as described above. Thecomponents 810 store applications and multimedia (755 and 753), from which some requests for content can be satisfied. When content requested is not hosted on the components, thecomponents 810 determine equivalent content, if any, using themapping data stores synchronization server platform 850 using the third-party mapping interface 845. The synchronization server platform responds by transmitting the requested content, or its equivalent, to themobile device 705, such as described above. -
FIG. 16 shows asystem 900 for backing up content in accordance with another embodiment of the present invention. In thesystem 900, purchase information, application equivalency, and content delivery are all provided by a third party. Thesystem 900 includes themobile device 705 coupled to aplatform 910 and a third-party content/application catalog ofcomponents 950. The third-party content/application catalog ofcomponents 950 is similar to the catalog ofcomponents 810, except that the userpurchase history datastores 730 is included on thecatalog 950 but not on thecatalog 810. -
FIG. 17 shows asystem 1000 for backing up content in accordance with another embodiment of the present invention. Thesystem 1000 includes themobile device 705 coupled to a third-party content/application catalog ofcomponents 1010. The third-party content/application catalog ofcomponents 1010 is similar to the catalog ofcomponents 950, except that third-party mapping interface 845 inFIG. 14 is replaced with a content/application restoremanager 1015, which is coupled to thebackup client 709. -
FIG. 18 is a sequence diagram 1100 of interactions between a mobile device client, a synchronization platform server, and a content repository in accordance with one embodiment of the invention. In thestep 1110, the user starts a routine for acquiring (e.g., purchasing, licensing, taking a subscription to, etc.) content, and in thestep 1115, the client communicates with the server to register the new application, thereby updating the appropriate application datastore in thestep 1120. In thestep 1125, the user selects to purchase the application, and in thestep 1130, the client registers the purchased application on the server, thereby updating the application datastore in thestep 1135. In thestep 1140, the user indicates that she is done acquiring new content, and in thestep 1145 the client notifies the server that the purchasing is complete. The datastore is updated in thestep 1150. - Later, when the device is to be restored, such as when it has been deactivated and is to be reactivated, in the
step 1155, the client notifies the server to restore the device. In thestep 1160, the device sends a command to query the subscriptions that have been acquired for the device. In thestep 1165, the server retrieves a list of subscribed applications, including equivalents, and returns this list to the client in thestep 1170. In thestep 1175, the client presents this list to the user, allowing her to select the content that she wants. In thestep 1180, the client requests the applications (original, equivalent, upgrades, etc.), which are returned to the client in thestep 1185. In thestep 1190, the applications are installed on the device. In thestep 1195, the mobile device requests the settings for the applications, which are retrieved in thestep 1195 and installed on the device in thestep 1199. - As discussed above, third-party content providers support a queryable interface, which allows the synchronization platform to retrieve, for a given user, a list of previously purchased content, metadata about items in the content catalog, equivalency data about previously purchased content, and a mechanism for retrieving equivalent content on a new handset.
- The list of previously purchased content can include a unique identifier that the synchronization platform presents to the content provider on subsequent calls to these interfaces, which provides an instance of content (e.g., “Who Let The Dogs Out Ringtone in MP3 @ 128 kbps). Metadata can include information such as the name, description size, and format of a particular content item in the catalog. Equivalency data can include, given a previously purchased content ID, new content ID appropriate for a given BREW platform ID. A preferred mechanism for retrieving equivalent content includes an interface that returns an HTTP Uniform Resource Locator (URL) via which binary data can be retrieved. When this interface is accessed, a third-party content provider can apply any digital rights management (DRM) desired, such as the remaining number of downloads allowed. It will be appreciated that mechanisms other than HTTP are able to be used in accordance with the present invention.
- Third-content providers are able to be queried in many ways. As one example, a third-party content provider is queried by accessing it using a URL that contains the query command. In this example, the URL contains a base URL path (here, “/la/fl cpi”) and a string that includes an operation code, an operation version number, and a user telephone number. The URL has the general form:
- https://address/base URL path/cpi?op=operationcode&v=versionnumber&u=telephonenumber
where the address is the domain of the third-party content provider. - Thus, for example, if the address of the third-party content provider is “contentprovider.com,” the query is to retrieve a list of user content purchased by the user (operationcode=1), the operation version is 1, and the user is identified by the
telephone number 15555551212, then the querying URL is - https://contentprovider.com/al/fl cpi?op=1 &v=1 &u=115555551212
- Accessing the third-party content provider using the URL will return results such as a list of persistent, unique content instance identifiers.
- In another example, the query is to retrieve content details such as metadata about a particular instance on content owned by a third-party content provider. In this example, the querying URL is given as:
- https://contentprovider.com/al/fl cpi?op=2&v=1 &cid=A1123897ADFAD
where the operation code is 1 and the operation version number is 1. The string A123897ADFAD is the content instance ID in question. Accessing the third-party content provider using this URL will display the returned results such as delimiter separated fields containing metadata about content instances such as content file name, content description, content size, content format description, content encoding description, and content author. - In a similar manner, using an appropriate operation code and associated parameters, a content portability interface can be queried to return a list of correct equivalent content and to return content URLs usable by the synchronization platform to download the appropriate version of a particular premium content item.
- Embodiments of the present invention provide an interface for configuring or updating mobile devices to access content available to other mobile devices.
FIG. 19A , for example, shows asystem 1200 that displaysicons icons FIG. 19A , by the dotted lines, theicon 1210 is dragged and dropped to theicon 1215, theicon 1220 is dragged and dropped to theicon 1225, and theicon 1230 is dragged and dropped to theicon 1235. The result of this is that a link to the game Tetris on a content provider (e.g., a URL), such as described above, is stored on themobile phone 1. As shown inFIG. 19B , the icon to theTetris 401 and thecorresponding link 401A are stored on theMobile phone 1 and theMobile phone 2, such as shown inFIG. 9 . Similarly, an icon to theChess game 402 and its associated link are also stored on theMobile phone 2, and an icon to theTrain schedule application 403 and its associatedlink 403A are stored on theMobile phone 3. Preferably, the icons 401-403 and the associatedlinks 401A-403A are transmitted to the Mobile phones 1-3 wirelessly. - In one embodiment, the
system 1200 is programmed to receive icons and associated links from any one of the Mobile phones 1-3. As one example, thesystem 1200 receives an icon and related link from theMobile phone 1. The icon is then displayed on thesystem 1200, alone or in a list of other icons. The icon and associated link are then selected and transferred to theMobile phones - It will also be appreciated that while the
system 1200 is programmed to transfer content to mobile phones, thesystem 1200 can also be used to offer new content for the Mobile phones 1-3. These new offers can be based on previous acquisitions for any one or more of the Mobile phones 1-3, such as found in purchase history databases discussed above. Thesystem 1200 can be programmed to offer content, list prices for content, and transmit content to mobile phones. In accordance with one embodiment, links to content are automatically and periodically transferred from one mobile device to another so that the two are synchronized. - In operation, links to content are stored on a platform remote to a mobile phone. When content is to be restored on the mobile, the mobile phone communicates with a platform that associates the content with one or more content providers. The platform contacts the one or more contact providers, which directly transmit the content to the mobile phone. Replacement content, such as upgrades, equivalent content, related content, and the like, can be offered to the mobile phone user, who can then select the replacement content, for a regular fee, a reduced fee, or even for no fee. Replacement content can be determined from a history of the user's past purchases, which is stored and used for this purpose.
- In the operation of other embodiments, a link to content is stored on the mobile phone; when an icon on the mobile phone is selected, the mobile phone communicates directly with the content provider, which transmits the content to the mobile phone. In the operation of still other embodiments, links to content are stored on a central device and transmitted to selected mobile phones. In this way, a mobile phone can be configured so that it can access content previously accessible to another mobile phone.
- It will be appreciated that while many of the examples included in this application refer to mobile phones, other electronic devices are able to use embodiments of the present invention including, but not limited to, personal digital assistants and personal computers.
- It will be readily apparent to one skilled in the art that various modifications may be made to the embodiments without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (86)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/011,399 US20080214163A1 (en) | 2007-01-26 | 2008-01-25 | System for and method of backing up content for use on a mobile device |
US12/286,040 US8620286B2 (en) | 2004-02-27 | 2008-09-26 | Method and system for promoting and transferring licensed content and applications |
US13/007,070 US8621025B2 (en) | 2000-01-25 | 2011-01-14 | Mobile data transfer and synchronization system |
US13/479,216 US9432439B1 (en) | 2007-01-26 | 2012-05-23 | System for and method of backing up content for use on a mobile device |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US89778907P | 2007-01-26 | 2007-01-26 | |
US93731407P | 2007-06-26 | 2007-06-26 | |
US12/011,399 US20080214163A1 (en) | 2007-01-26 | 2008-01-25 | System for and method of backing up content for use on a mobile device |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/151,440 Continuation-In-Part US7643824B2 (en) | 2000-01-25 | 2008-05-06 | Wireless telephone data backup system |
Related Child Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/789,816 Continuation-In-Part US7505762B2 (en) | 2000-01-25 | 2004-02-27 | Wireless telephone data backup system |
US12/286,040 Continuation-In-Part US8620286B2 (en) | 2000-01-25 | 2008-09-26 | Method and system for promoting and transferring licensed content and applications |
US13/007,070 Continuation-In-Part US8621025B2 (en) | 2000-01-25 | 2011-01-14 | Mobile data transfer and synchronization system |
US13/479,216 Division US9432439B1 (en) | 2007-01-26 | 2012-05-23 | System for and method of backing up content for use on a mobile device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080214163A1 true US20080214163A1 (en) | 2008-09-04 |
Family
ID=39674686
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/011,399 Abandoned US20080214163A1 (en) | 2000-01-25 | 2008-01-25 | System for and method of backing up content for use on a mobile device |
US13/479,216 Active US9432439B1 (en) | 2007-01-26 | 2012-05-23 | System for and method of backing up content for use on a mobile device |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/479,216 Active US9432439B1 (en) | 2007-01-26 | 2012-05-23 | System for and method of backing up content for use on a mobile device |
Country Status (7)
Country | Link |
---|---|
US (2) | US20080214163A1 (en) |
EP (1) | EP2115611A4 (en) |
JP (1) | JP2010517173A (en) |
KR (1) | KR20090113310A (en) |
CN (1) | CN101606144A (en) |
BR (1) | BRPI0807406A2 (en) |
WO (1) | WO2008094508A2 (en) |
Cited By (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090307683A1 (en) * | 2008-06-08 | 2009-12-10 | Sam Gharabally | Network-Based Update of Application Programs |
US20090319639A1 (en) * | 2008-06-19 | 2009-12-24 | Huawei Technologies Co., Ltd. | Content identification method and system, and scidm client and server |
US7756515B1 (en) * | 2007-03-16 | 2010-07-13 | At&T Mobility Ii Llc | Systems and methods of merchandising content to mobile telephones based on subscriber's purchase history |
US20110016089A1 (en) * | 2009-07-16 | 2011-01-20 | Apple Inc. | Restoring data to a mobile device |
US20110051908A1 (en) * | 2009-09-02 | 2011-03-03 | Robert Garner | Target content distribution for telephone calls |
US20110083088A1 (en) * | 2006-08-04 | 2011-04-07 | Apple Inc. | Navigation Of Electronic Backups |
US7925245B1 (en) * | 2007-03-16 | 2011-04-12 | At&T Mobility Ii Llc | System and methods for wirelessly providing update information of and downloading previously obtained content to a newly activated mobile station |
US7974614B1 (en) * | 2007-03-16 | 2011-07-05 | At&T Mobility Ii Llc | Systems and methods for merchandising content to a second mobile telephone based on the content of a first mobile telephone |
US20110256846A1 (en) * | 2010-04-20 | 2011-10-20 | Sadana Rajeev | Systems and method for media transfer |
US8150425B1 (en) * | 2007-03-16 | 2012-04-03 | At&T Mobility Ii Llc | Systems and methods for merchandising new offers to mobile telephone users based on changes to the mobile telephone's components |
US8181111B1 (en) | 2007-12-31 | 2012-05-15 | Synchronoss Technologies, Inc. | System and method for providing social context to digital activity |
US20120185575A1 (en) * | 2009-09-27 | 2012-07-19 | Zte Corporation | BREW Service Download System and Implementation Method Thereof |
US20120185431A1 (en) * | 2007-10-31 | 2012-07-19 | At&T Intellectual Property I, L.P. | Methods, Systems, and Products for Data Backup |
US8255006B1 (en) | 2009-11-10 | 2012-08-28 | Fusionone, Inc. | Event dependent notification system and method |
US20120271951A1 (en) * | 2011-04-19 | 2012-10-25 | Samsung Electronics Co., Ltd. | Control method for providing storage space of application and terminal and server therefor |
US8307004B2 (en) | 2007-06-08 | 2012-11-06 | Apple Inc. | Manipulating electronic backups |
US8311988B2 (en) | 2006-08-04 | 2012-11-13 | Apple Inc. | Consistent back up of electronic information |
US8370853B2 (en) | 2006-08-04 | 2013-02-05 | Apple Inc. | Event notification management |
US20130138772A1 (en) * | 2011-11-24 | 2013-05-30 | Samsung Electronics Co., Ltd. | Display apparatus and control method thereof, apparatus providing application and control method thereof |
US8468136B2 (en) | 2007-06-08 | 2013-06-18 | Apple Inc. | Efficient data backup |
US8504527B2 (en) | 2006-08-04 | 2013-08-06 | Apple Inc. | Application-based backup-restore of electronic information |
US8566289B2 (en) | 2007-06-08 | 2013-10-22 | Apple Inc. | Electronic backup of applications |
US8620286B2 (en) | 2004-02-27 | 2013-12-31 | Synchronoss Technologies, Inc. | Method and system for promoting and transferring licensed content and applications |
US8621025B2 (en) | 2000-01-25 | 2013-12-31 | Synchronoss Technologis, Inc. | Mobile data transfer and synchronization system |
US20140006434A1 (en) * | 2010-10-29 | 2014-01-02 | France Telecom | Method and system to recommend applications from an application market place to a new device |
US8630899B1 (en) * | 2009-09-18 | 2014-01-14 | Alpine Audio Now, LLC | System and method for interactive advertisement augmentation via a called voice connection |
US8645471B2 (en) | 2003-07-21 | 2014-02-04 | Synchronoss Technologies, Inc. | Device message management system |
US8725965B2 (en) | 2007-06-08 | 2014-05-13 | Apple Inc. | System setup for electronic backup |
US8745523B2 (en) | 2007-06-08 | 2014-06-03 | Apple Inc. | Deletion in electronic backups |
US20140258481A1 (en) * | 2013-03-11 | 2014-09-11 | United Video Properties, Inc. | Systems and methods for auto-configuring a user equipment device with content consumption material |
US8924254B2 (en) * | 2009-09-18 | 2014-12-30 | Alpine Audio Now, LLC | System and method for interactive advertisement augmentation via a called voice connection |
US20150011204A1 (en) * | 2013-07-04 | 2015-01-08 | Lg Electronics Inc. | Mobile terminal and method of controlling the mobile terminal |
US8943026B2 (en) | 2011-01-14 | 2015-01-27 | Apple Inc. | Visual representation of a local backup |
US8984029B2 (en) | 2011-01-14 | 2015-03-17 | Apple Inc. | File system management |
US9009115B2 (en) | 2006-08-04 | 2015-04-14 | Apple Inc. | Restoring electronic information |
US9203624B2 (en) | 2012-06-04 | 2015-12-01 | Apple Inc. | Authentication and notification heuristics |
US9360995B2 (en) | 2007-06-08 | 2016-06-07 | Apple Inc. | User interface for electronic backup |
US9454587B2 (en) | 2007-06-08 | 2016-09-27 | Apple Inc. | Searching and restoring of backups |
KR20160122155A (en) * | 2014-02-17 | 2016-10-21 | 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 | Encoded associations with external content items |
US9538003B2 (en) | 2009-09-18 | 2017-01-03 | Audionow Ip Holdings, Llc | System and method for interactive advertisement augmentation via a called voice connection |
US9542076B1 (en) | 2004-05-12 | 2017-01-10 | Synchronoss Technologies, Inc. | System for and method of updating a personal profile |
US9715394B2 (en) | 2006-08-04 | 2017-07-25 | Apple Inc. | User interface for backup management |
US10706096B2 (en) | 2011-08-18 | 2020-07-07 | Apple Inc. | Management of local and remote media items |
US10992795B2 (en) | 2017-05-16 | 2021-04-27 | Apple Inc. | Methods and interfaces for home media control |
US10996917B2 (en) | 2019-05-31 | 2021-05-04 | Apple Inc. | User interfaces for audio media control |
US11283916B2 (en) | 2017-05-16 | 2022-03-22 | Apple Inc. | Methods and interfaces for configuring a device in accordance with an audio tone signal |
US11392291B2 (en) | 2020-09-25 | 2022-07-19 | Apple Inc. | Methods and interfaces for media control with dynamic feedback |
US11431836B2 (en) | 2017-05-02 | 2022-08-30 | Apple Inc. | Methods and interfaces for initiating media playback |
US11620103B2 (en) | 2019-05-31 | 2023-04-04 | Apple Inc. | User interfaces for audio media control |
US11683408B2 (en) | 2017-05-16 | 2023-06-20 | Apple Inc. | Methods and interfaces for home media control |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2764492A4 (en) | 2011-10-04 | 2015-07-15 | Google Inc | Combined activities history on a device |
CN107025147A (en) * | 2016-02-02 | 2017-08-08 | 中兴通讯股份有限公司 | Processing method, server and the system of data |
KR101886835B1 (en) * | 2016-05-30 | 2018-08-08 | 에스케이테크엑스 주식회사 | Apparatus for providing recommded contents using back-up data when data transfer between terminals and method using the same |
CN108475284B (en) * | 2016-11-30 | 2022-04-05 | 华为技术有限公司 | Method and device for displaying image and terminal equipment |
KR101986482B1 (en) * | 2017-12-12 | 2019-06-07 | 주식회사 디지캡 | Contents blockchain for storing and managing content information |
Citations (120)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5392390A (en) * | 1992-04-10 | 1995-02-21 | Intellilink Corp. | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
US5483352A (en) * | 1992-08-27 | 1996-01-09 | Fujitsu Limited | Computer able to link electronic mail functions with telephone functions |
US5485161A (en) * | 1994-11-21 | 1996-01-16 | Trimble Navigation Limited | Vehicle speed control based on GPS/MAP matching of posted speeds |
US5706509A (en) * | 1995-04-28 | 1998-01-06 | Intel Corporation | Application independent record level synchronization |
US5710922A (en) * | 1993-06-02 | 1998-01-20 | Apple Computer, Inc. | Method for synchronizing and archiving information between computer systems |
US5727202A (en) * | 1995-10-18 | 1998-03-10 | Palm Computing, Inc. | Method and apparatus for synchronizing information on two different computer systems |
US5727950A (en) * | 1996-05-22 | 1998-03-17 | Netsage Corporation | Agent based instruction system and method |
US5729735A (en) * | 1995-02-08 | 1998-03-17 | Meyering; Samuel C. | Remote database file synchronizer |
US5729743A (en) * | 1995-11-17 | 1998-03-17 | Deltatech Research, Inc. | Computer apparatus and method for merging system deltas |
US5729739A (en) * | 1994-04-26 | 1998-03-17 | International Business Machines Corporation | Persistent object mapping system and method with abstract schema mapper |
US5859973A (en) * | 1996-08-21 | 1999-01-12 | International Business Machines Corporation | Methods, system and computer program products for delayed message generation and encoding in an intermittently connected data communication system |
US5864864A (en) * | 1995-09-27 | 1999-01-26 | Sun Microsystems, Inc. | Method and apparatus for providing transparent persistent data support to foreign data types |
US5875296A (en) * | 1997-01-28 | 1999-02-23 | International Business Machines Corporation | Distributed file system web server user authentication with cookies |
US5884325A (en) * | 1996-10-09 | 1999-03-16 | Oracle Corporation | System for synchronizing shared data between computers |
US5884323A (en) * | 1995-10-13 | 1999-03-16 | 3Com Corporation | Extendible method and apparatus for synchronizing files on two different computer systems |
US6012063A (en) * | 1998-03-04 | 2000-01-04 | Starfish Software, Inc. | Block file system for minimal incremental data transfer between computing devices |
US6012088A (en) * | 1996-12-10 | 2000-01-04 | International Business Machines Corporation | Automatic configuration for internet access device |
US6014695A (en) * | 1996-11-19 | 2000-01-11 | Hitachi, Ltd. | Computer network system for packet-transferring data between computers, network file server in computer network system and data transferring method thereof |
US6016394A (en) * | 1997-09-17 | 2000-01-18 | Tenfold Corporation | Method and system for database application software creation requiring minimal programming |
US6016478A (en) * | 1996-08-13 | 2000-01-18 | Starfish Software, Inc. | Scheduling system with methods for peer-to-peer scheduling of remote users |
US6023708A (en) * | 1997-05-29 | 2000-02-08 | Visto Corporation | System and method for using a global translator to synchronize workspace elements across a network |
US6023723A (en) * | 1997-12-22 | 2000-02-08 | Accepted Marketing, Inc. | Method and system for filtering unwanted junk e-mail utilizing a plurality of filtering mechanisms |
US6026414A (en) * | 1998-03-05 | 2000-02-15 | International Business Machines Corporation | System including a proxy client to backup files in a distributed computing environment |
US6034621A (en) * | 1997-11-18 | 2000-03-07 | Lucent Technologies, Inc. | Wireless remote synchronization of data between PC and PDA |
US6038665A (en) * | 1996-12-03 | 2000-03-14 | Fairbanks Systems Group | System and method for backing up computer files over a wide area computer network |
US6044381A (en) * | 1997-09-11 | 2000-03-28 | Puma Technology, Inc. | Using distributed history files in synchronizing databases |
US6067582A (en) * | 1996-08-13 | 2000-05-23 | Angel Secure Networks, Inc. | System for installing information related to a software application to a remote computer over a network |
US6173311B1 (en) * | 1997-02-13 | 2001-01-09 | Pointcast, Inc. | Apparatus, method and article of manufacture for servicing client requests on a network |
US6173310B1 (en) * | 1999-03-23 | 2001-01-09 | Microstrategy, Inc. | System and method for automatic transmission of on-line analytical processing system report output |
US6182117B1 (en) * | 1995-05-31 | 2001-01-30 | Netscape Communications Corporation | Method and apparatus for workgroup information replication |
US6182141B1 (en) * | 1996-12-20 | 2001-01-30 | Intel Corporation | Transparent proxy server |
US6185598B1 (en) * | 1998-02-10 | 2001-02-06 | Digital Island, Inc. | Optimized network resource location |
US6189030B1 (en) * | 1996-02-21 | 2001-02-13 | Infoseek Corporation | Method and apparatus for redirection of server external hyper-link references |
US6189096B1 (en) * | 1998-05-06 | 2001-02-13 | Kyberpass Corporation | User authentification using a virtual private key |
US6195695B1 (en) * | 1998-10-27 | 2001-02-27 | International Business Machines Corporation | Data processing system and method for recovering from system crashes |
US6195794B1 (en) * | 1997-08-12 | 2001-02-27 | International Business Machines Corporation | Method and apparatus for distributing templates in a component system |
US6202085B1 (en) * | 1996-12-06 | 2001-03-13 | Microsoft Corportion | System and method for incremental change synchronization between multiple copies of data |
US6205448B1 (en) * | 1998-01-30 | 2001-03-20 | 3Com Corporation | Method and apparatus of synchronizing two computer systems supporting multiple synchronization techniques |
US6338096B1 (en) * | 1998-06-10 | 2002-01-08 | International Business Machines Corporation | System uses kernals of micro web server for supporting HTML web browser in providing HTML data format and HTTP protocol from variety of data sources |
US6339710B1 (en) * | 1996-12-20 | 2002-01-15 | Nec Corporation | Radio selective calling receiver having telephone directory function |
US20020007303A1 (en) * | 2000-05-01 | 2002-01-17 | Brookler Brent D. | System for conducting electronic surveys |
US6341316B1 (en) * | 1999-09-10 | 2002-01-22 | Avantgo, Inc. | System, method, and computer program product for synchronizing content between a server and a client based on state information |
US20020010868A1 (en) * | 2000-07-04 | 2002-01-24 | Yoshiyasu Nakashima | Data accumulation system |
US6345308B1 (en) * | 1998-02-27 | 2002-02-05 | Kabushiki Kaisha Toshiba | Network computer system and method for executing data synchronization process thereof |
US20020016818A1 (en) * | 2000-05-11 | 2002-02-07 | Shekhar Kirani | System and methodology for optimizing delivery of email attachments for disparate devices |
US20020016912A1 (en) * | 1996-11-19 | 2002-02-07 | Johnson R. Brent | System and computer based method to automatically archive and retrieve encrypted remote client data files |
US6353448B1 (en) * | 2000-05-16 | 2002-03-05 | Ez Online Network, Inc. | Graphic user interface display method |
US6356910B1 (en) * | 1998-08-07 | 2002-03-12 | Paul Zellweger | Method and apparatus for a self-service content menu |
US20020032751A1 (en) * | 2000-05-23 | 2002-03-14 | Srinivas Bharadwaj | Remote displays in mobile communication networks |
US6360330B1 (en) * | 1998-03-31 | 2002-03-19 | Emc Corporation | System and method for backing up data stored in multiple mirrors on a mass storage subsystem under control of a backup server |
US6360252B1 (en) * | 1999-09-20 | 2002-03-19 | Fusionone, Inc. | Managing the transfer of e-mail attachments to rendering devices other than an original e-mail recipient |
US6363249B1 (en) * | 2000-04-10 | 2002-03-26 | Motorola, Inc. | Dynamically configurable datagram message communication system |
US6363412B1 (en) * | 1997-11-21 | 2002-03-26 | Nec Corporation | Wireless communication method permitting efficient use of system resources |
US6507891B1 (en) * | 1999-07-22 | 2003-01-14 | International Business Machines Corporation | Method and apparatus for managing internal caches and external caches in a data processing system |
US6516327B1 (en) * | 1998-12-24 | 2003-02-04 | International Business Machines Corporation | System and method for synchronizing data in multiple databases |
US20030028554A1 (en) * | 2001-06-15 | 2003-02-06 | Oskari Koskimies | Selecting data for synchronization |
US20030028451A1 (en) * | 2001-08-03 | 2003-02-06 | Ananian John Allen | Personalized interactive digital catalog profiling |
US6523079B2 (en) * | 1993-02-19 | 2003-02-18 | Elonex Ip Holdings Ltd | Micropersonal digital assistant |
US6523063B1 (en) * | 1999-08-30 | 2003-02-18 | Zaplet, Inc. | Method system and program product for accessing a file using values from a redirect message string for each change of the link identifier |
US20030037020A1 (en) * | 2000-02-22 | 2003-02-20 | Lars Novak | Method and apparatus for synchronizing databases of portable devices without change logs |
US6535743B1 (en) * | 1998-07-29 | 2003-03-18 | Minorplanet Systems Usa, Inc. | System and method for providing directions using a communication network |
US6539494B1 (en) * | 1999-06-17 | 2003-03-25 | Art Technology Group, Inc. | Internet server session backup apparatus |
US20030061163A1 (en) * | 2001-09-27 | 2003-03-27 | Durfield Richard C. | Method and apparatus for verification/authorization by credit or debit card owner of use of card concurrently with merchant transaction |
US20030093797A1 (en) * | 2001-11-13 | 2003-05-15 | Paul Bazzaz | Transmission system for transmitting video streams relating to an event to spectators physically present at said event |
US20030115240A1 (en) * | 2000-05-16 | 2003-06-19 | Sok-Hyun Cho | Schedule managing character and information providing system and method using same |
US20030134623A1 (en) * | 2002-01-17 | 2003-07-17 | Tomokazu Kanamaru | Mobile communication system |
US20030172236A1 (en) * | 2002-03-07 | 2003-09-11 | International Business Machines Corporation | Methods and systems for distributed caching in presence of updates and in accordance with holding times |
US6684302B2 (en) * | 1999-01-19 | 2004-01-27 | Arm Limited | Bus arbitration circuit responsive to latency of access requests and the state of the memory circuit |
US6684206B2 (en) * | 2001-05-18 | 2004-01-27 | Hewlett-Packard Development Company, L.P. | OLAP-based web access analysis method and system |
US20040024834A1 (en) * | 2002-08-02 | 2004-02-05 | Andrew Alegria | Sharing personal information between computing devices |
US6694336B1 (en) * | 2000-01-25 | 2004-02-17 | Fusionone, Inc. | Data transfer and synchronization system |
US6694335B1 (en) * | 1999-10-04 | 2004-02-17 | Microsoft Corporation | Method, computer readable medium, and system for monitoring the state of a collection of resources |
US6701316B1 (en) * | 2000-04-07 | 2004-03-02 | Nec Corporation | Method and apparatus for intelligent network bandwidth and system resource utilization for web content fetch and refresh |
US6704849B2 (en) * | 2000-03-10 | 2004-03-09 | Alcatel | Process, data processing device, service provision server, back-up server and program modules for backing-up data |
US20040054746A1 (en) * | 2002-09-13 | 2004-03-18 | Nec Corporation | Telephone directory information sharing system with mobile phone |
US6714987B1 (en) * | 1999-11-05 | 2004-03-30 | Nortel Networks Limited | Architecture for an IP centric distributed network |
US20040128324A1 (en) * | 2002-12-30 | 2004-07-01 | Arnold Sheynman | Digital content preview generation and distribution among peer devices |
US20040210752A1 (en) * | 2003-02-11 | 2004-10-21 | Rao Bindu Rama | Electronic device supporting multiple update agents |
US6839568B2 (en) * | 2000-11-22 | 2005-01-04 | Nec Corporation | User setting information management method and management system for portable telephone |
US6842695B1 (en) * | 2001-04-17 | 2005-01-11 | Fusionone, Inc. | Mapping and addressing system for a secure remote access system |
US20050021571A1 (en) * | 2001-11-26 | 2005-01-27 | East Simon Jeremy | Method of replicating data between computing devices |
US6850944B1 (en) * | 2000-11-20 | 2005-02-01 | The University Of Alabama | System, method, and computer program product for managing access to and navigation through large-scale information spaces |
US20050032527A1 (en) * | 2003-08-08 | 2005-02-10 | Networks In Motion, Inc. | Method and system for collecting synchronizing, and reporting telecommunication call events and work flow related information |
US20050038863A1 (en) * | 2003-07-21 | 2005-02-17 | Richard Onyon | Device message management system |
US20050044404A1 (en) * | 2003-08-23 | 2005-02-24 | Bhansali Apurva Mahendrakumar | Electronic device security and tracking system and method |
US20050054354A1 (en) * | 2003-06-25 | 2005-03-10 | Manuel Roman | Method and apparatus for resource sharing over handset terminals |
US6868451B1 (en) * | 2000-06-20 | 2005-03-15 | Palm Source, Inc. | Data exchange between a handheld device and another computer system using an exchange manager via synchronization |
US20050060392A1 (en) * | 2003-09-17 | 2005-03-17 | Goring Bryan R. | System and method for management of mutating applications |
US6870921B1 (en) * | 1999-11-12 | 2005-03-22 | Metro One Telecommunications, Inc. | Enhanced directory assistance service providing individual or group directories |
US20050064859A1 (en) * | 2003-09-23 | 2005-03-24 | Motorola, Inc. | Server-based system for backing up memory of a wireless subscriber device |
US20050102329A1 (en) * | 2003-11-10 | 2005-05-12 | Jiang Zhaowei C. | Backup and restore in mobile applications |
US20050114470A1 (en) * | 2003-11-25 | 2005-05-26 | Balaji Bal | Communications system |
US20050125625A1 (en) * | 2003-12-09 | 2005-06-09 | Michael Kilian | Methods and apparatus for parsing a content address to facilitate selection of a physical storage location in a data storage system |
US20060021059A1 (en) * | 2004-04-30 | 2006-01-26 | Brown Michael K | System and method for handling restoration operations on mobile devices |
US6996631B1 (en) * | 2000-08-17 | 2006-02-07 | International Business Machines Corporation | System having a single IP address associated with communication protocol stacks in a cluster of processing systems |
US20060035647A1 (en) * | 2003-01-30 | 2006-02-16 | Intrado | Apparatus and method for displaying caller ID with location information |
US7003555B1 (en) * | 2000-06-23 | 2006-02-21 | Cloudshield Technologies, Inc. | Apparatus and method for domain name resolution |
US7003668B2 (en) * | 2000-11-03 | 2006-02-21 | Fusionone, Inc. | Secure authentication of users via intermediate parties |
US20060052091A1 (en) * | 2004-05-12 | 2006-03-09 | Richard Onyon | Advanced contact identification system |
US20060129627A1 (en) * | 1996-11-22 | 2006-06-15 | Mangosoft Corp. | Internet-based shared file service with native PC client access and semantics and distributed version control |
US20060148418A1 (en) * | 2004-12-06 | 2006-07-06 | Interdigital Technology Corporation | Method and apparatus for alerting a target that it is subject to sensing and restricting access to sensed content associated with the target |
US20060223530A1 (en) * | 2005-03-29 | 2006-10-05 | Research In Motion Limited | System and method for personal identification number messaging |
WO2006121084A1 (en) * | 2005-05-11 | 2006-11-16 | Ntt Docomo, Inc. | Digital right management system, content server, and mobile terminal |
US20060288112A1 (en) * | 2005-05-25 | 2006-12-21 | Cingular Wireless, Llc | System and methods for storing music selections in network storage and for streaming the selections to a wireless device for playback on the wireless device |
US20070005504A1 (en) * | 2005-06-30 | 2007-01-04 | Microsoft Corporation | Dynamic digital content licensing |
US7162494B2 (en) * | 2002-05-29 | 2007-01-09 | Sbc Technology Resources, Inc. | Method and system for distributed user profiling |
US7167728B1 (en) * | 1997-09-26 | 2007-01-23 | Sun Microsystems, Inc. | Graphical user interface for a portable telephone |
US20070043739A1 (en) * | 2005-08-19 | 2007-02-22 | Sony Corporation | Communication device and method thereof |
US20070050734A1 (en) * | 2004-04-20 | 2007-03-01 | Pluck Corporation | Method, system, and computer program product for saving a search result within a global computer network |
US20070053335A1 (en) * | 2005-05-19 | 2007-03-08 | Richard Onyon | Mobile device address book builder |
US20070094042A1 (en) * | 2005-09-14 | 2007-04-26 | Jorey Ramer | Contextual mobile content placement on a mobile communication facility |
US20070168721A1 (en) * | 2005-12-22 | 2007-07-19 | Nokia Corporation | Method, network entity, system, electronic device and computer program product for backup and restore provisioning |
US20070214149A1 (en) * | 2006-03-09 | 2007-09-13 | International Business Machines Corporation | Associating user selected content management directives with user selected ratings |
US7315826B1 (en) * | 1999-05-27 | 2008-01-01 | Accenture, Llp | Comparatively analyzing vendors of components required for a web-based architecture |
US20080022220A1 (en) * | 1998-10-13 | 2008-01-24 | Chris Cheah | Method and System for Controlled Distribution of Information Over a Network |
US20080039020A1 (en) * | 2001-02-01 | 2008-02-14 | Ack Venture Holdings Llc, A Connecticut Corporation | Mobile computing and communication |
US20080089299A1 (en) * | 2006-10-13 | 2008-04-17 | Motorola, Inc. | Method and system for distributing content in Ad-hoc networks using super peers |
US20080120199A1 (en) * | 2006-11-17 | 2008-05-22 | Tracy Pirnack | Method and system for upgrading a previously purchased media asset |
US20080127289A1 (en) * | 2006-10-19 | 2008-05-29 | Julia Luc E | System and method for programmatic link generation with media delivery |
US20080268823A1 (en) * | 2005-12-15 | 2008-10-30 | Shaul Shalev | System and methods for initiating, maintaining, and delivering personalized information by communication server |
Family Cites Families (106)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5204902A (en) | 1991-09-13 | 1993-04-20 | At&T Bell Laboratories | Cellular telephony authentication arrangement |
US5509070A (en) | 1992-12-15 | 1996-04-16 | Softlock Services Inc. | Method for encouraging purchase of executable and non-executable software |
US5801699A (en) | 1996-01-26 | 1998-09-01 | International Business Machines Corporation | Icon aggregation on a graphical user interface |
US5930350A (en) | 1996-06-27 | 1999-07-27 | Mci Communications Corporation | System, method and computer program for automated speed dialing |
US5909568A (en) | 1996-09-03 | 1999-06-01 | Apple Computer, Inc. | Process and apparatus for transferring data between different file formats |
US5828376A (en) | 1996-09-23 | 1998-10-27 | J. D. Edwards World Source Company | Menu control in a graphical user interface |
US6212529B1 (en) | 1996-11-13 | 2001-04-03 | Puma Technology, Inc. | Synchronization of databases using filters |
US5966717A (en) | 1996-12-20 | 1999-10-12 | Apple Computer, Inc. | Methods for importing data between database management programs |
US6023620A (en) * | 1997-02-26 | 2000-02-08 | Telefonaktiebolaget Lm Ecrisson | Method for downloading control software to a cellular telephone |
US5950193A (en) | 1997-12-16 | 1999-09-07 | Microsoft Corporation | Interactive records and groups of records in an address book database |
US6061063A (en) | 1998-06-30 | 2000-05-09 | Sun Microsystems, Inc. | Method and apparatus for providing feedback while scrolling |
DE19831720A1 (en) | 1998-07-15 | 2000-01-20 | Alcatel Sa | Method for determining a uniform global view of the system status of a distributed computer network |
US6430289B1 (en) | 1999-04-13 | 2002-08-06 | Microsoft Corporation | System and method for computerized status monitor and use in a telephone network |
US6757698B2 (en) | 1999-04-14 | 2004-06-29 | Iomega Corporation | Method and apparatus for automatically synchronizing data from a host computer to two or more backup data storage locations |
US6549937B1 (en) | 1999-07-21 | 2003-04-15 | Microsoft Corporation | System and method for multi-protocol communication in a computer network |
US6601071B1 (en) | 1999-08-04 | 2003-07-29 | Oracle International Corp. | Method and system for business to business data interchange using XML |
KR20010045359A (en) * | 1999-11-04 | 2001-06-05 | 조영선 | A Mobile telecommunication system with the remote managing function of file and data |
CA2394683A1 (en) | 1999-12-13 | 2001-06-14 | Connected Corporation | Multiple copy capability for network backup systems |
US6976229B1 (en) | 1999-12-16 | 2005-12-13 | Ricoh Co., Ltd. | Method and apparatus for storytelling with digital photographs |
US7505762B2 (en) | 2004-02-27 | 2009-03-17 | Fusionone, Inc. | Wireless telephone data backup system |
US6671757B1 (en) | 2000-01-26 | 2003-12-30 | Fusionone, Inc. | Data transfer and synchronization system |
US6684088B1 (en) | 2000-03-01 | 2004-01-27 | Axi Mobile Ltd. | System and method for displaying electronic mail messages on a low bandwidth device |
US20030154171A1 (en) | 2000-03-31 | 2003-08-14 | Hewlett Packard Company | Apparatus and method for selling personal information |
JP2001357010A (en) * | 2000-04-10 | 2001-12-26 | Mitsubishi Corp | Method for entrusting and managing file in web server on internet and a file entrusting and managing device to be used for the same |
US6629227B1 (en) * | 2000-05-04 | 2003-09-30 | Scientific-Atlanta, Inc. | System and method for a communication terminal to manage memory and maintain a current application version for multiple applications |
US20030158960A1 (en) | 2000-05-22 | 2003-08-21 | Engberg Stephan J. | System and method for establishing a privacy communication path |
JP2001331661A (en) * | 2000-05-22 | 2001-11-30 | Sony Corp | Method and system for information distribution, communication terminal, information distributing device, and repetitive distribution preventing method |
US6734883B1 (en) | 2000-05-25 | 2004-05-11 | International Business Machines Corporation | Spinlist graphical user interface control with preview and postview |
US8073954B1 (en) | 2000-07-19 | 2011-12-06 | Synchronoss Technologies, Inc. | Method and apparatus for a secure remote access system |
US20070047523A1 (en) | 2001-08-16 | 2007-03-01 | Roamware, Inc. | Method and system for call-setup triggered push content |
US6842770B1 (en) * | 2000-08-18 | 2005-01-11 | Apple Computer, Inc. | Method and system for seamlessly accessing remotely stored files |
US8701022B2 (en) | 2000-09-26 | 2014-04-15 | 6S Limited | Method and system for archiving and retrieving items based on episodic memory of groups of people |
US6718336B1 (en) | 2000-09-29 | 2004-04-06 | Battelle Memorial Institute | Data import system for data analysis system |
US6939223B1 (en) | 2000-10-05 | 2005-09-06 | Igt | Gaming device providing pay table information for a symbol through selection of the symbol |
JP2002185579A (en) | 2000-12-08 | 2002-06-28 | Nec Corp | Backup method for application software of portable telephone terminal |
US6668254B2 (en) | 2000-12-21 | 2003-12-23 | Fulltilt Solutions, Inc. | Method and system for importing data |
US6906717B2 (en) | 2001-02-27 | 2005-06-14 | Microsoft Corporation | Multiple chart user interface |
WO2002071191A2 (en) * | 2001-03-02 | 2002-09-12 | Kasenna, Inc. | Metadata enabled push-pull model for efficient low-latency video-content distribution over a network |
DE60236381D1 (en) | 2001-04-12 | 2010-06-24 | Research In Motion Ltd | System and method for dynamically shifting information to wireless communication devices |
CN1212565C (en) * | 2001-05-14 | 2005-07-27 | 株式会社Ntt都科摩 | System for managing program stored in storage block of mobile terminal |
GB0114317D0 (en) | 2001-06-13 | 2001-08-01 | Kean Thomas A | Method of protecting intellectual property cores on field programmable gate array |
US7308651B2 (en) | 2001-09-05 | 2007-12-11 | Sca Hygiene Products Ab | Data entry graphical user interface |
US7337229B2 (en) | 2001-11-08 | 2008-02-26 | Telefonktiebolaget Lm Ericsson (Publ) | Method and apparatus for authorizing internet transactions using the public land mobile network (PLMN) |
US7159036B2 (en) * | 2001-12-10 | 2007-01-02 | Mcafee, Inc. | Updating data from a source computer to groups of destination computers |
US20030163483A1 (en) | 2002-02-19 | 2003-08-28 | Abraham Zingher | Method and system for a data service to control access to personal information |
EP1347623A1 (en) | 2002-03-22 | 2003-09-24 | Nokia Corporation | Downloading of application software for an accessory device to a mobile terminal |
KR100424449B1 (en) * | 2002-03-23 | 2004-03-25 | 에스케이 텔레콤주식회사 | Multimedia Advertisment Service Method and Mobile Terminal Controlling Apparatus and Method for the service in mobile communication network |
EP1488342A1 (en) | 2002-03-28 | 2004-12-22 | Nokia Corporation | Enhanced storing of personal content |
JP3633580B2 (en) | 2002-04-17 | 2005-03-30 | 三菱電機株式会社 | Misfire detection device for internal combustion engine |
WO2003094031A1 (en) | 2002-05-03 | 2003-11-13 | Netbotz, Inc. | Method and apparatus for collecting and displaying network device information |
US6920486B2 (en) | 2002-05-20 | 2005-07-19 | Nokia Corporation | Method and apparatus for enabling synchronizing data in different devices having different capabilities and unmatched data fields |
US20030229898A1 (en) * | 2002-06-05 | 2003-12-11 | Babu Suresh P. | Multiple on-demand media vendor integration |
US7516182B2 (en) | 2002-06-18 | 2009-04-07 | Aol Llc | Practical techniques for reducing unsolicited electronic messages by identifying sender's addresses |
US20030236933A1 (en) | 2002-06-21 | 2003-12-25 | Daisuke Shigeta | Information processing apparatus, information equipment, information processing system, automatic backup method, data transmission and reception method, automatic backup program, data transmission and reception program, and record medium having the programs recorded thereon |
US20040003390A1 (en) | 2002-06-27 | 2004-01-01 | Microsoft Corporation | System and method for installing a software application in a non-impactfull manner |
US7606560B2 (en) | 2002-08-08 | 2009-10-20 | Fujitsu Limited | Authentication services using mobile device |
US20040203595A1 (en) | 2002-08-12 | 2004-10-14 | Singhal Tara Chand | Method and apparatus for user authentication using a cellular telephone and a transient pass code |
US7221748B1 (en) | 2002-11-12 | 2007-05-22 | Bellsouth Intellectual Property Corporation | Method for linking call log information to address book entries and replying using medium of choice |
US7870279B2 (en) * | 2002-12-09 | 2011-01-11 | Hrl Laboratories, Llc | Method and apparatus for scanning, personalizing, and casting multimedia data streams via a communication network and television |
US7460653B2 (en) | 2003-03-07 | 2008-12-02 | Callwave, Inc. | Apparatus and methods for telecommunication authentication |
US7555657B2 (en) * | 2003-03-28 | 2009-06-30 | Ricoh Company, Ltd. | Communication device, software update device, software update system, software update method, and program |
US8612590B1 (en) | 2003-04-11 | 2013-12-17 | International Business Machines Corporation | Method and apparatus for access management |
US6990187B2 (en) | 2003-04-25 | 2006-01-24 | Lucent Technologies Inc. | Methods for blocking repeated occurrences of nuisance calls |
US20040267676A1 (en) | 2003-06-30 | 2004-12-30 | Yan Feng | Method and apparatus for optimizing product distribution strategies and product mixes to increase profitability in complex computer aided pricing of products and services |
EP1664992A4 (en) * | 2003-08-15 | 2010-05-19 | Blackboard Inc | Content system and associated methods |
US20080027826A1 (en) | 2003-08-25 | 2008-01-31 | At&T Bls Intellectual Property, Inc. | Method, system and computer program product for facilitating the telecommunication equipment ordering process |
KR100762629B1 (en) | 2003-08-26 | 2007-10-01 | 삼성전자주식회사 | Method for processing back-up service of mobile terminal |
US20050055309A1 (en) * | 2003-09-04 | 2005-03-10 | Dwango North America | Method and apparatus for a one click upgrade for mobile applications |
US20050143111A1 (en) | 2003-12-30 | 2005-06-30 | Fitzpatrick Matthew D. | Determining availability of members of a contact list in a communication device |
US8478837B2 (en) | 2004-01-28 | 2013-07-02 | Microsoft Corporation | Offline global address list |
US7308250B2 (en) | 2004-03-16 | 2007-12-11 | Broadcom Corporation | Integration of secure identification logic into cell phone |
US7865181B1 (en) * | 2004-03-19 | 2011-01-04 | Single Touch Interactive, Inc. | Searching for mobile content |
US7558794B2 (en) | 2004-03-24 | 2009-07-07 | Sap Ag | Database system and method with assigned locks |
WO2005107137A2 (en) | 2004-04-23 | 2005-11-10 | Passmark Security, Inc. | Method and apparatus for authenticating users using two or more factors |
US7280652B2 (en) | 2004-09-13 | 2007-10-09 | Research In Motion Limited | Handheld electronic device having improved phone call log, and associated method |
CN100505927C (en) | 2004-10-22 | 2009-06-24 | 北京握奇数据系统有限公司 | Dynamic password identification method |
GB0428533D0 (en) | 2004-12-30 | 2005-02-09 | Nokia Corp | Presence services in a wireless communications network |
US20060199599A1 (en) * | 2005-01-03 | 2006-09-07 | Arun Gupta | Method for setting communication device and communication device thereof |
US7593925B2 (en) | 2005-02-25 | 2009-09-22 | Microsoft Corporation | Method and system for locating contact information collected from contact sources |
DE102005013238B4 (en) | 2005-03-22 | 2015-07-16 | Infineon Technologies Ag | Method and device for transferring adjustment information for data interface drivers of a RAM module |
JP2007006456A (en) | 2005-05-25 | 2007-01-11 | Sharp Corp | Receiving system, transmitting system |
US7359897B2 (en) | 2005-06-02 | 2008-04-15 | Toshiba Corporation | System and method for document management and retrieval |
EP1887759B1 (en) | 2005-06-15 | 2011-09-21 | Huawei Technologies Co., Ltd. | Method and system for realizing automatic restoration after a device failure |
WO2007005886A2 (en) * | 2005-07-01 | 2007-01-11 | Mvisible Technologies, Inc. | System and method for ringtone generation |
EP1905191B1 (en) | 2005-07-20 | 2014-09-03 | Verimatrix, Inc. | Network user authentication system and method |
US20100095238A1 (en) | 2005-09-14 | 2010-04-15 | Gilles Baudet | Device, Method, Computer Program Product and User Interface for Enabling a User to Vary Which Items are displayed to the user |
US20070127597A1 (en) | 2005-12-01 | 2007-06-07 | Idx Investment Corporation | System and method for facilitating visual comparison of incoming data with existing data |
WO2007082314A2 (en) * | 2006-01-13 | 2007-07-19 | Gogo Mobile, Inc. | Digital content metadata registry systems and methods |
EP1994737A4 (en) | 2006-01-24 | 2009-04-08 | Envio Networks Inc | Methods for marketing digital content to mobile communication device users |
US7761816B2 (en) | 2006-02-10 | 2010-07-20 | Vringo, Inc. | Personalization content sharing system and method |
US20070214264A1 (en) | 2006-03-09 | 2007-09-13 | Jari Koister | Device social-control system |
US20070226783A1 (en) | 2006-03-16 | 2007-09-27 | Rabbit's Foot Security, Inc. (A California Corporation) | User-administered single sign-on with automatic password management for web server authentication |
US20080005080A1 (en) | 2006-06-30 | 2008-01-03 | Whatsthefax, Llc | Interactive facsimile directory |
US8233894B2 (en) * | 2006-08-23 | 2012-07-31 | Resource Consortium Limited | System and method for sending mobile media content to another mobile device user |
US8224308B1 (en) * | 2006-09-29 | 2012-07-17 | Yahoo! Inc. | Mobile device catalog registration based on user agents and customer snapshots of capabilities |
US7953775B2 (en) | 2006-11-07 | 2011-05-31 | Yahoo! Inc. | Sharing tagged data on the internet |
CN101855861A (en) | 2007-11-16 | 2010-10-06 | 富士通天株式会社 | Authentication method, authentication system, on-vehicle device, and authentication device |
US20090143052A1 (en) | 2007-11-29 | 2009-06-04 | Michael Bates | Systems and methods for personal information management and contact picture synchronization and distribution |
US8209744B2 (en) | 2008-05-16 | 2012-06-26 | Microsoft Corporation | Mobile device assisted secure computer network communication |
US20090307486A1 (en) | 2008-06-09 | 2009-12-10 | Garret Grajek | System and method for secured network access utilizing a client .net software component |
US8463739B2 (en) | 2008-08-28 | 2013-06-11 | Red Hat, Inc. | Systems and methods for generating multi-population statistical measures using middleware |
US8307412B2 (en) | 2008-10-20 | 2012-11-06 | Microsoft Corporation | User authentication management |
US20100205448A1 (en) | 2009-02-11 | 2010-08-12 | Tolga Tarhan | Devices, systems and methods for secure verification of user identity |
CA2715067A1 (en) | 2009-09-23 | 2011-03-23 | Courtview Justice Solutions | System and method for providing judicial orders |
US8239290B2 (en) | 2009-12-15 | 2012-08-07 | Shutterfly, Inc. | Graphical user interface, system and method for managing contacts within an online stationery system |
US20120151345A1 (en) | 2010-12-10 | 2012-06-14 | Mcclements Iv James Burns | Recognition lookups for synchronization of media playback with comment creation and delivery |
-
2008
- 2008-01-25 WO PCT/US2008/001093 patent/WO2008094508A2/en active Application Filing
- 2008-01-25 EP EP08724873A patent/EP2115611A4/en not_active Ceased
- 2008-01-25 JP JP2009547321A patent/JP2010517173A/en not_active Withdrawn
- 2008-01-25 KR KR1020097017628A patent/KR20090113310A/en not_active Application Discontinuation
- 2008-01-25 BR BRPI0807406-2A patent/BRPI0807406A2/en not_active IP Right Cessation
- 2008-01-25 CN CNA2008800030230A patent/CN101606144A/en active Pending
- 2008-01-25 US US12/011,399 patent/US20080214163A1/en not_active Abandoned
-
2012
- 2012-05-23 US US13/479,216 patent/US9432439B1/en active Active
Patent Citations (122)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5392390A (en) * | 1992-04-10 | 1995-02-21 | Intellilink Corp. | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
US5483352A (en) * | 1992-08-27 | 1996-01-09 | Fujitsu Limited | Computer able to link electronic mail functions with telephone functions |
US6523079B2 (en) * | 1993-02-19 | 2003-02-18 | Elonex Ip Holdings Ltd | Micropersonal digital assistant |
US5710922A (en) * | 1993-06-02 | 1998-01-20 | Apple Computer, Inc. | Method for synchronizing and archiving information between computer systems |
US5729739A (en) * | 1994-04-26 | 1998-03-17 | International Business Machines Corporation | Persistent object mapping system and method with abstract schema mapper |
US5485161A (en) * | 1994-11-21 | 1996-01-16 | Trimble Navigation Limited | Vehicle speed control based on GPS/MAP matching of posted speeds |
US5729735A (en) * | 1995-02-08 | 1998-03-17 | Meyering; Samuel C. | Remote database file synchronizer |
US5706509A (en) * | 1995-04-28 | 1998-01-06 | Intel Corporation | Application independent record level synchronization |
US6182117B1 (en) * | 1995-05-31 | 2001-01-30 | Netscape Communications Corporation | Method and apparatus for workgroup information replication |
US5864864A (en) * | 1995-09-27 | 1999-01-26 | Sun Microsystems, Inc. | Method and apparatus for providing transparent persistent data support to foreign data types |
US5884323A (en) * | 1995-10-13 | 1999-03-16 | 3Com Corporation | Extendible method and apparatus for synchronizing files on two different computer systems |
US5727202A (en) * | 1995-10-18 | 1998-03-10 | Palm Computing, Inc. | Method and apparatus for synchronizing information on two different computer systems |
US5729743A (en) * | 1995-11-17 | 1998-03-17 | Deltatech Research, Inc. | Computer apparatus and method for merging system deltas |
US6189030B1 (en) * | 1996-02-21 | 2001-02-13 | Infoseek Corporation | Method and apparatus for redirection of server external hyper-link references |
US5727950A (en) * | 1996-05-22 | 1998-03-17 | Netsage Corporation | Agent based instruction system and method |
US6016478A (en) * | 1996-08-13 | 2000-01-18 | Starfish Software, Inc. | Scheduling system with methods for peer-to-peer scheduling of remote users |
US6067582A (en) * | 1996-08-13 | 2000-05-23 | Angel Secure Networks, Inc. | System for installing information related to a software application to a remote computer over a network |
US5859973A (en) * | 1996-08-21 | 1999-01-12 | International Business Machines Corporation | Methods, system and computer program products for delayed message generation and encoding in an intermittently connected data communication system |
US5884325A (en) * | 1996-10-09 | 1999-03-16 | Oracle Corporation | System for synchronizing shared data between computers |
US6014695A (en) * | 1996-11-19 | 2000-01-11 | Hitachi, Ltd. | Computer network system for packet-transferring data between computers, network file server in computer network system and data transferring method thereof |
US20020016912A1 (en) * | 1996-11-19 | 2002-02-07 | Johnson R. Brent | System and computer based method to automatically archive and retrieve encrypted remote client data files |
US20060129627A1 (en) * | 1996-11-22 | 2006-06-15 | Mangosoft Corp. | Internet-based shared file service with native PC client access and semantics and distributed version control |
US6038665A (en) * | 1996-12-03 | 2000-03-14 | Fairbanks Systems Group | System and method for backing up computer files over a wide area computer network |
US6202085B1 (en) * | 1996-12-06 | 2001-03-13 | Microsoft Corportion | System and method for incremental change synchronization between multiple copies of data |
US6012088A (en) * | 1996-12-10 | 2000-01-04 | International Business Machines Corporation | Automatic configuration for internet access device |
US6339710B1 (en) * | 1996-12-20 | 2002-01-15 | Nec Corporation | Radio selective calling receiver having telephone directory function |
US6182141B1 (en) * | 1996-12-20 | 2001-01-30 | Intel Corporation | Transparent proxy server |
US5875296A (en) * | 1997-01-28 | 1999-02-23 | International Business Machines Corporation | Distributed file system web server user authentication with cookies |
US6173311B1 (en) * | 1997-02-13 | 2001-01-09 | Pointcast, Inc. | Apparatus, method and article of manufacture for servicing client requests on a network |
US6023708A (en) * | 1997-05-29 | 2000-02-08 | Visto Corporation | System and method for using a global translator to synchronize workspace elements across a network |
US6195794B1 (en) * | 1997-08-12 | 2001-02-27 | International Business Machines Corporation | Method and apparatus for distributing templates in a component system |
US6044381A (en) * | 1997-09-11 | 2000-03-28 | Puma Technology, Inc. | Using distributed history files in synchronizing databases |
US6016394A (en) * | 1997-09-17 | 2000-01-18 | Tenfold Corporation | Method and system for database application software creation requiring minimal programming |
US7167728B1 (en) * | 1997-09-26 | 2007-01-23 | Sun Microsystems, Inc. | Graphical user interface for a portable telephone |
US6034621A (en) * | 1997-11-18 | 2000-03-07 | Lucent Technologies, Inc. | Wireless remote synchronization of data between PC and PDA |
US6363412B1 (en) * | 1997-11-21 | 2002-03-26 | Nec Corporation | Wireless communication method permitting efficient use of system resources |
US6023723A (en) * | 1997-12-22 | 2000-02-08 | Accepted Marketing, Inc. | Method and system for filtering unwanted junk e-mail utilizing a plurality of filtering mechanisms |
US6205448B1 (en) * | 1998-01-30 | 2001-03-20 | 3Com Corporation | Method and apparatus of synchronizing two computer systems supporting multiple synchronization techniques |
US6185598B1 (en) * | 1998-02-10 | 2001-02-06 | Digital Island, Inc. | Optimized network resource location |
US6345308B1 (en) * | 1998-02-27 | 2002-02-05 | Kabushiki Kaisha Toshiba | Network computer system and method for executing data synchronization process thereof |
US6012063A (en) * | 1998-03-04 | 2000-01-04 | Starfish Software, Inc. | Block file system for minimal incremental data transfer between computing devices |
US6026414A (en) * | 1998-03-05 | 2000-02-15 | International Business Machines Corporation | System including a proxy client to backup files in a distributed computing environment |
US6360330B1 (en) * | 1998-03-31 | 2002-03-19 | Emc Corporation | System and method for backing up data stored in multiple mirrors on a mass storage subsystem under control of a backup server |
US6189096B1 (en) * | 1998-05-06 | 2001-02-13 | Kyberpass Corporation | User authentification using a virtual private key |
US6338096B1 (en) * | 1998-06-10 | 2002-01-08 | International Business Machines Corporation | System uses kernals of micro web server for supporting HTML web browser in providing HTML data format and HTTP protocol from variety of data sources |
US6535743B1 (en) * | 1998-07-29 | 2003-03-18 | Minorplanet Systems Usa, Inc. | System and method for providing directions using a communication network |
US6356910B1 (en) * | 1998-08-07 | 2002-03-12 | Paul Zellweger | Method and apparatus for a self-service content menu |
US20080022220A1 (en) * | 1998-10-13 | 2008-01-24 | Chris Cheah | Method and System for Controlled Distribution of Information Over a Network |
US6195695B1 (en) * | 1998-10-27 | 2001-02-27 | International Business Machines Corporation | Data processing system and method for recovering from system crashes |
US6516327B1 (en) * | 1998-12-24 | 2003-02-04 | International Business Machines Corporation | System and method for synchronizing data in multiple databases |
US6684302B2 (en) * | 1999-01-19 | 2004-01-27 | Arm Limited | Bus arbitration circuit responsive to latency of access requests and the state of the memory circuit |
US6173310B1 (en) * | 1999-03-23 | 2001-01-09 | Microstrategy, Inc. | System and method for automatic transmission of on-line analytical processing system report output |
US7315826B1 (en) * | 1999-05-27 | 2008-01-01 | Accenture, Llp | Comparatively analyzing vendors of components required for a web-based architecture |
US6539494B1 (en) * | 1999-06-17 | 2003-03-25 | Art Technology Group, Inc. | Internet server session backup apparatus |
US6507891B1 (en) * | 1999-07-22 | 2003-01-14 | International Business Machines Corporation | Method and apparatus for managing internal caches and external caches in a data processing system |
US6523063B1 (en) * | 1999-08-30 | 2003-02-18 | Zaplet, Inc. | Method system and program product for accessing a file using values from a redirect message string for each change of the link identifier |
US6341316B1 (en) * | 1999-09-10 | 2002-01-22 | Avantgo, Inc. | System, method, and computer program product for synchronizing content between a server and a client based on state information |
US6360252B1 (en) * | 1999-09-20 | 2002-03-19 | Fusionone, Inc. | Managing the transfer of e-mail attachments to rendering devices other than an original e-mail recipient |
US6694335B1 (en) * | 1999-10-04 | 2004-02-17 | Microsoft Corporation | Method, computer readable medium, and system for monitoring the state of a collection of resources |
US6714987B1 (en) * | 1999-11-05 | 2004-03-30 | Nortel Networks Limited | Architecture for an IP centric distributed network |
US6870921B1 (en) * | 1999-11-12 | 2005-03-22 | Metro One Telecommunications, Inc. | Enhanced directory assistance service providing individual or group directories |
US7007041B2 (en) * | 2000-01-25 | 2006-02-28 | Fusionone, Inc. | Synchronization system application object interface |
US6694336B1 (en) * | 2000-01-25 | 2004-02-17 | Fusionone, Inc. | Data transfer and synchronization system |
US20030037020A1 (en) * | 2000-02-22 | 2003-02-20 | Lars Novak | Method and apparatus for synchronizing databases of portable devices without change logs |
US6704849B2 (en) * | 2000-03-10 | 2004-03-09 | Alcatel | Process, data processing device, service provision server, back-up server and program modules for backing-up data |
US6701316B1 (en) * | 2000-04-07 | 2004-03-02 | Nec Corporation | Method and apparatus for intelligent network bandwidth and system resource utilization for web content fetch and refresh |
US6363249B1 (en) * | 2000-04-10 | 2002-03-26 | Motorola, Inc. | Dynamically configurable datagram message communication system |
US20020007303A1 (en) * | 2000-05-01 | 2002-01-17 | Brookler Brent D. | System for conducting electronic surveys |
US20020016818A1 (en) * | 2000-05-11 | 2002-02-07 | Shekhar Kirani | System and methodology for optimizing delivery of email attachments for disparate devices |
US6353448B1 (en) * | 2000-05-16 | 2002-03-05 | Ez Online Network, Inc. | Graphic user interface display method |
US20030115240A1 (en) * | 2000-05-16 | 2003-06-19 | Sok-Hyun Cho | Schedule managing character and information providing system and method using same |
US20020032751A1 (en) * | 2000-05-23 | 2002-03-14 | Srinivas Bharadwaj | Remote displays in mobile communication networks |
US6868451B1 (en) * | 2000-06-20 | 2005-03-15 | Palm Source, Inc. | Data exchange between a handheld device and another computer system using an exchange manager via synchronization |
US7003555B1 (en) * | 2000-06-23 | 2006-02-21 | Cloudshield Technologies, Inc. | Apparatus and method for domain name resolution |
US20020010868A1 (en) * | 2000-07-04 | 2002-01-24 | Yoshiyasu Nakashima | Data accumulation system |
US6996631B1 (en) * | 2000-08-17 | 2006-02-07 | International Business Machines Corporation | System having a single IP address associated with communication protocol stacks in a cluster of processing systems |
US7003668B2 (en) * | 2000-11-03 | 2006-02-21 | Fusionone, Inc. | Secure authentication of users via intermediate parties |
US6850944B1 (en) * | 2000-11-20 | 2005-02-01 | The University Of Alabama | System, method, and computer program product for managing access to and navigation through large-scale information spaces |
US6839568B2 (en) * | 2000-11-22 | 2005-01-04 | Nec Corporation | User setting information management method and management system for portable telephone |
US20080039020A1 (en) * | 2001-02-01 | 2008-02-14 | Ack Venture Holdings Llc, A Connecticut Corporation | Mobile computing and communication |
US6842695B1 (en) * | 2001-04-17 | 2005-01-11 | Fusionone, Inc. | Mapping and addressing system for a secure remote access system |
US6684206B2 (en) * | 2001-05-18 | 2004-01-27 | Hewlett-Packard Development Company, L.P. | OLAP-based web access analysis method and system |
US20030028554A1 (en) * | 2001-06-15 | 2003-02-06 | Oskari Koskimies | Selecting data for synchronization |
US20030028451A1 (en) * | 2001-08-03 | 2003-02-06 | Ananian John Allen | Personalized interactive digital catalog profiling |
US20030061163A1 (en) * | 2001-09-27 | 2003-03-27 | Durfield Richard C. | Method and apparatus for verification/authorization by credit or debit card owner of use of card concurrently with merchant transaction |
US20030093797A1 (en) * | 2001-11-13 | 2003-05-15 | Paul Bazzaz | Transmission system for transmitting video streams relating to an event to spectators physically present at said event |
US20050021571A1 (en) * | 2001-11-26 | 2005-01-27 | East Simon Jeremy | Method of replicating data between computing devices |
US20030134623A1 (en) * | 2002-01-17 | 2003-07-17 | Tomokazu Kanamaru | Mobile communication system |
US20030172236A1 (en) * | 2002-03-07 | 2003-09-11 | International Business Machines Corporation | Methods and systems for distributed caching in presence of updates and in accordance with holding times |
US7162494B2 (en) * | 2002-05-29 | 2007-01-09 | Sbc Technology Resources, Inc. | Method and system for distributed user profiling |
US20040024834A1 (en) * | 2002-08-02 | 2004-02-05 | Andrew Alegria | Sharing personal information between computing devices |
US20040054746A1 (en) * | 2002-09-13 | 2004-03-18 | Nec Corporation | Telephone directory information sharing system with mobile phone |
US20040128324A1 (en) * | 2002-12-30 | 2004-07-01 | Arnold Sheynman | Digital content preview generation and distribution among peer devices |
US20060035647A1 (en) * | 2003-01-30 | 2006-02-16 | Intrado | Apparatus and method for displaying caller ID with location information |
US20040210752A1 (en) * | 2003-02-11 | 2004-10-21 | Rao Bindu Rama | Electronic device supporting multiple update agents |
US20050054354A1 (en) * | 2003-06-25 | 2005-03-10 | Manuel Roman | Method and apparatus for resource sharing over handset terminals |
US20050038863A1 (en) * | 2003-07-21 | 2005-02-17 | Richard Onyon | Device message management system |
US20050032527A1 (en) * | 2003-08-08 | 2005-02-10 | Networks In Motion, Inc. | Method and system for collecting synchronizing, and reporting telecommunication call events and work flow related information |
US20050044404A1 (en) * | 2003-08-23 | 2005-02-24 | Bhansali Apurva Mahendrakumar | Electronic device security and tracking system and method |
US20050060392A1 (en) * | 2003-09-17 | 2005-03-17 | Goring Bryan R. | System and method for management of mutating applications |
US20050064859A1 (en) * | 2003-09-23 | 2005-03-24 | Motorola, Inc. | Server-based system for backing up memory of a wireless subscriber device |
US20050102329A1 (en) * | 2003-11-10 | 2005-05-12 | Jiang Zhaowei C. | Backup and restore in mobile applications |
US20050114470A1 (en) * | 2003-11-25 | 2005-05-26 | Balaji Bal | Communications system |
US20050125625A1 (en) * | 2003-12-09 | 2005-06-09 | Michael Kilian | Methods and apparatus for parsing a content address to facilitate selection of a physical storage location in a data storage system |
US20070050734A1 (en) * | 2004-04-20 | 2007-03-01 | Pluck Corporation | Method, system, and computer program product for saving a search result within a global computer network |
US20060021059A1 (en) * | 2004-04-30 | 2006-01-26 | Brown Michael K | System and method for handling restoration operations on mobile devices |
US20060052091A1 (en) * | 2004-05-12 | 2006-03-09 | Richard Onyon | Advanced contact identification system |
US20060148418A1 (en) * | 2004-12-06 | 2006-07-06 | Interdigital Technology Corporation | Method and apparatus for alerting a target that it is subject to sensing and restricting access to sensed content associated with the target |
US20060223530A1 (en) * | 2005-03-29 | 2006-10-05 | Research In Motion Limited | System and method for personal identification number messaging |
WO2006121084A1 (en) * | 2005-05-11 | 2006-11-16 | Ntt Docomo, Inc. | Digital right management system, content server, and mobile terminal |
US20090083857A1 (en) * | 2005-05-11 | 2009-03-26 | Ntt Docomo, Inc., | Digital right management system, content server, and mobile terminal |
US20070053335A1 (en) * | 2005-05-19 | 2007-03-08 | Richard Onyon | Mobile device address book builder |
US20060288112A1 (en) * | 2005-05-25 | 2006-12-21 | Cingular Wireless, Llc | System and methods for storing music selections in network storage and for streaming the selections to a wireless device for playback on the wireless device |
US20070005504A1 (en) * | 2005-06-30 | 2007-01-04 | Microsoft Corporation | Dynamic digital content licensing |
US20070043739A1 (en) * | 2005-08-19 | 2007-02-22 | Sony Corporation | Communication device and method thereof |
US20070094042A1 (en) * | 2005-09-14 | 2007-04-26 | Jorey Ramer | Contextual mobile content placement on a mobile communication facility |
US20080268823A1 (en) * | 2005-12-15 | 2008-10-30 | Shaul Shalev | System and methods for initiating, maintaining, and delivering personalized information by communication server |
US20070168721A1 (en) * | 2005-12-22 | 2007-07-19 | Nokia Corporation | Method, network entity, system, electronic device and computer program product for backup and restore provisioning |
US20070214149A1 (en) * | 2006-03-09 | 2007-09-13 | International Business Machines Corporation | Associating user selected content management directives with user selected ratings |
US20080089299A1 (en) * | 2006-10-13 | 2008-04-17 | Motorola, Inc. | Method and system for distributing content in Ad-hoc networks using super peers |
US20080127289A1 (en) * | 2006-10-19 | 2008-05-29 | Julia Luc E | System and method for programmatic link generation with media delivery |
US20080120199A1 (en) * | 2006-11-17 | 2008-05-22 | Tracy Pirnack | Method and system for upgrading a previously purchased media asset |
Cited By (84)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8621025B2 (en) | 2000-01-25 | 2013-12-31 | Synchronoss Technologis, Inc. | Mobile data transfer and synchronization system |
US9615221B1 (en) | 2003-07-21 | 2017-04-04 | Synchronoss Technologies, Inc. | Device message management system |
US9723460B1 (en) | 2003-07-21 | 2017-08-01 | Synchronoss Technologies, Inc. | Device message management system |
US8645471B2 (en) | 2003-07-21 | 2014-02-04 | Synchronoss Technologies, Inc. | Device message management system |
US8620286B2 (en) | 2004-02-27 | 2013-12-31 | Synchronoss Technologies, Inc. | Method and system for promoting and transferring licensed content and applications |
US9542076B1 (en) | 2004-05-12 | 2017-01-10 | Synchronoss Technologies, Inc. | System for and method of updating a personal profile |
US8495024B2 (en) | 2006-08-04 | 2013-07-23 | Apple Inc. | Navigation of electronic backups |
US8370853B2 (en) | 2006-08-04 | 2013-02-05 | Apple Inc. | Event notification management |
US20110083088A1 (en) * | 2006-08-04 | 2011-04-07 | Apple Inc. | Navigation Of Electronic Backups |
US8504527B2 (en) | 2006-08-04 | 2013-08-06 | Apple Inc. | Application-based backup-restore of electronic information |
US9009115B2 (en) | 2006-08-04 | 2015-04-14 | Apple Inc. | Restoring electronic information |
US9715394B2 (en) | 2006-08-04 | 2017-07-25 | Apple Inc. | User interface for backup management |
US8775378B2 (en) | 2006-08-04 | 2014-07-08 | Apple Inc. | Consistent backup of electronic information |
US8311988B2 (en) | 2006-08-04 | 2012-11-13 | Apple Inc. | Consistent back up of electronic information |
US7925245B1 (en) * | 2007-03-16 | 2011-04-12 | At&T Mobility Ii Llc | System and methods for wirelessly providing update information of and downloading previously obtained content to a newly activated mobile station |
US8150425B1 (en) * | 2007-03-16 | 2012-04-03 | At&T Mobility Ii Llc | Systems and methods for merchandising new offers to mobile telephone users based on changes to the mobile telephone's components |
US7756515B1 (en) * | 2007-03-16 | 2010-07-13 | At&T Mobility Ii Llc | Systems and methods of merchandising content to mobile telephones based on subscriber's purchase history |
US7974614B1 (en) * | 2007-03-16 | 2011-07-05 | At&T Mobility Ii Llc | Systems and methods for merchandising content to a second mobile telephone based on the content of a first mobile telephone |
US9360995B2 (en) | 2007-06-08 | 2016-06-07 | Apple Inc. | User interface for electronic backup |
US8307004B2 (en) | 2007-06-08 | 2012-11-06 | Apple Inc. | Manipulating electronic backups |
US8468136B2 (en) | 2007-06-08 | 2013-06-18 | Apple Inc. | Efficient data backup |
US8965929B2 (en) | 2007-06-08 | 2015-02-24 | Apple Inc. | Manipulating electronic backups |
US8504516B2 (en) | 2007-06-08 | 2013-08-06 | Apple Inc. | Manipulating electronic backups |
US9354982B2 (en) | 2007-06-08 | 2016-05-31 | Apple Inc. | Manipulating electronic backups |
US8745523B2 (en) | 2007-06-08 | 2014-06-03 | Apple Inc. | Deletion in electronic backups |
US8725965B2 (en) | 2007-06-08 | 2014-05-13 | Apple Inc. | System setup for electronic backup |
US8566289B2 (en) | 2007-06-08 | 2013-10-22 | Apple Inc. | Electronic backup of applications |
US9454587B2 (en) | 2007-06-08 | 2016-09-27 | Apple Inc. | Searching and restoring of backups |
US10891020B2 (en) | 2007-06-08 | 2021-01-12 | Apple Inc. | User interface for electronic backup |
US10552244B2 (en) * | 2007-10-31 | 2020-02-04 | At&T Intellectual Property I, L.P. | Methods, systems and products for data backup |
US20120185431A1 (en) * | 2007-10-31 | 2012-07-19 | At&T Intellectual Property I, L.P. | Methods, Systems, and Products for Data Backup |
US20160188400A1 (en) * | 2007-10-31 | 2016-06-30 | At&T Intellectual Property I, Lp | Methods, systems and products for data backup |
US9311192B2 (en) * | 2007-10-31 | 2016-04-12 | At&T Intellectual Property I, L.P. | Methods, systems, and products for data backup |
US8181111B1 (en) | 2007-12-31 | 2012-05-15 | Synchronoss Technologies, Inc. | System and method for providing social context to digital activity |
US20090307683A1 (en) * | 2008-06-08 | 2009-12-10 | Sam Gharabally | Network-Based Update of Application Programs |
US8527651B2 (en) * | 2008-06-19 | 2013-09-03 | Huawei Technologies Co., Ltd. | Content identification method and system, and SCIDM client and server |
US20090319639A1 (en) * | 2008-06-19 | 2009-12-24 | Huawei Technologies Co., Ltd. | Content identification method and system, and scidm client and server |
US20110016089A1 (en) * | 2009-07-16 | 2011-01-20 | Apple Inc. | Restoring data to a mobile device |
US20110051908A1 (en) * | 2009-09-02 | 2011-03-03 | Robert Garner | Target content distribution for telephone calls |
US8924254B2 (en) * | 2009-09-18 | 2014-12-30 | Alpine Audio Now, LLC | System and method for interactive advertisement augmentation via a called voice connection |
US9538003B2 (en) | 2009-09-18 | 2017-01-03 | Audionow Ip Holdings, Llc | System and method for interactive advertisement augmentation via a called voice connection |
US8630899B1 (en) * | 2009-09-18 | 2014-01-14 | Alpine Audio Now, LLC | System and method for interactive advertisement augmentation via a called voice connection |
US20120185575A1 (en) * | 2009-09-27 | 2012-07-19 | Zte Corporation | BREW Service Download System and Implementation Method Thereof |
EP2482570A4 (en) * | 2009-09-27 | 2015-04-15 | Zte Corp | Brew service download system and implementing method thereof |
EP2482570A1 (en) * | 2009-09-27 | 2012-08-01 | ZTE Corporation | Brew service download system and implementing method thereof |
US8255006B1 (en) | 2009-11-10 | 2012-08-28 | Fusionone, Inc. | Event dependent notification system and method |
US8918094B2 (en) | 2010-04-20 | 2014-12-23 | Cellco Partnership | Systems and method for media transfer |
US8521150B2 (en) * | 2010-04-20 | 2013-08-27 | Cellco Partnership | Systems and method for media transfer |
US20110256846A1 (en) * | 2010-04-20 | 2011-10-20 | Sadana Rajeev | Systems and method for media transfer |
US9881050B2 (en) * | 2010-10-29 | 2018-01-30 | Orange | Method and system to recommend applications from an application market place to a new device |
US20140006434A1 (en) * | 2010-10-29 | 2014-01-02 | France Telecom | Method and system to recommend applications from an application market place to a new device |
US9411812B2 (en) | 2011-01-14 | 2016-08-09 | Apple Inc. | File system management |
US8943026B2 (en) | 2011-01-14 | 2015-01-27 | Apple Inc. | Visual representation of a local backup |
US10303652B2 (en) | 2011-01-14 | 2019-05-28 | Apple Inc. | File system management |
US8984029B2 (en) | 2011-01-14 | 2015-03-17 | Apple Inc. | File system management |
US20120271951A1 (en) * | 2011-04-19 | 2012-10-25 | Samsung Electronics Co., Ltd. | Control method for providing storage space of application and terminal and server therefor |
US11281711B2 (en) | 2011-08-18 | 2022-03-22 | Apple Inc. | Management of local and remote media items |
US11893052B2 (en) | 2011-08-18 | 2024-02-06 | Apple Inc. | Management of local and remote media items |
US10706096B2 (en) | 2011-08-18 | 2020-07-07 | Apple Inc. | Management of local and remote media items |
US20130138772A1 (en) * | 2011-11-24 | 2013-05-30 | Samsung Electronics Co., Ltd. | Display apparatus and control method thereof, apparatus providing application and control method thereof |
US9710252B2 (en) | 2012-06-04 | 2017-07-18 | Apple Inc. | Authentication and notification heuristics |
US9203624B2 (en) | 2012-06-04 | 2015-12-01 | Apple Inc. | Authentication and notification heuristics |
US10353693B2 (en) | 2012-06-04 | 2019-07-16 | Apple Inc. | Authentication and notification heuristics |
US9848276B2 (en) * | 2013-03-11 | 2017-12-19 | Rovi Guides, Inc. | Systems and methods for auto-configuring a user equipment device with content consumption material |
US20140258481A1 (en) * | 2013-03-11 | 2014-09-11 | United Video Properties, Inc. | Systems and methods for auto-configuring a user equipment device with content consumption material |
US20150011204A1 (en) * | 2013-07-04 | 2015-01-08 | Lg Electronics Inc. | Mobile terminal and method of controlling the mobile terminal |
KR102368945B1 (en) | 2014-02-17 | 2022-02-28 | 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 | Encoded associations with external content items |
US11727194B2 (en) | 2014-02-17 | 2023-08-15 | Microsoft Technology Licensing, Llc | Encoded associations with external content items |
KR20160122155A (en) * | 2014-02-17 | 2016-10-21 | 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 | Encoded associations with external content items |
US11431836B2 (en) | 2017-05-02 | 2022-08-30 | Apple Inc. | Methods and interfaces for initiating media playback |
US11201961B2 (en) | 2017-05-16 | 2021-12-14 | Apple Inc. | Methods and interfaces for adjusting the volume of media |
US11283916B2 (en) | 2017-05-16 | 2022-03-22 | Apple Inc. | Methods and interfaces for configuring a device in accordance with an audio tone signal |
US11683408B2 (en) | 2017-05-16 | 2023-06-20 | Apple Inc. | Methods and interfaces for home media control |
US11750734B2 (en) | 2017-05-16 | 2023-09-05 | Apple Inc. | Methods for initiating output of at least a component of a signal representative of media currently being played back by another device |
US11412081B2 (en) | 2017-05-16 | 2022-08-09 | Apple Inc. | Methods and interfaces for configuring an electronic device to initiate playback of media |
US11095766B2 (en) | 2017-05-16 | 2021-08-17 | Apple Inc. | Methods and interfaces for adjusting an audible signal based on a spatial position of a voice command source |
US10992795B2 (en) | 2017-05-16 | 2021-04-27 | Apple Inc. | Methods and interfaces for home media control |
US10996917B2 (en) | 2019-05-31 | 2021-05-04 | Apple Inc. | User interfaces for audio media control |
US11620103B2 (en) | 2019-05-31 | 2023-04-04 | Apple Inc. | User interfaces for audio media control |
US11755273B2 (en) | 2019-05-31 | 2023-09-12 | Apple Inc. | User interfaces for audio media control |
US11853646B2 (en) | 2019-05-31 | 2023-12-26 | Apple Inc. | User interfaces for audio media control |
US11010121B2 (en) | 2019-05-31 | 2021-05-18 | Apple Inc. | User interfaces for audio media control |
US11392291B2 (en) | 2020-09-25 | 2022-07-19 | Apple Inc. | Methods and interfaces for media control with dynamic feedback |
US11782598B2 (en) | 2020-09-25 | 2023-10-10 | Apple Inc. | Methods and interfaces for media control with dynamic feedback |
Also Published As
Publication number | Publication date |
---|---|
US9432439B1 (en) | 2016-08-30 |
CN101606144A (en) | 2009-12-16 |
WO2008094508B1 (en) | 2008-12-11 |
EP2115611A4 (en) | 2010-02-03 |
BRPI0807406A2 (en) | 2014-05-27 |
WO2008094508A2 (en) | 2008-08-07 |
WO2008094508A3 (en) | 2008-10-23 |
EP2115611A2 (en) | 2009-11-11 |
JP2010517173A (en) | 2010-05-20 |
KR20090113310A (en) | 2009-10-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9432439B1 (en) | System for and method of backing up content for use on a mobile device | |
US8620286B2 (en) | Method and system for promoting and transferring licensed content and applications | |
US20070100963A1 (en) | Remote Content Storage for Mobile Telephones | |
US9667515B1 (en) | Service image notifications | |
US9026605B2 (en) | Digital file distribution in a social network system | |
US20140237466A1 (en) | User experience and dependency management in a mobile device | |
US20110125926A1 (en) | System and method for communicating with electronic devices | |
US8412687B1 (en) | System and method for delivering content to a communication device in a content delivery system | |
US20160148301A1 (en) | System and method for strong and providing content to client devices | |
US20080313630A1 (en) | Method And System For Distributing A Software Application To A Specified Recipient | |
WO2006057738A2 (en) | System for automatically creating a metadata repository for multimedia | |
US7444386B2 (en) | Application programming interface for provisioning services | |
JP2012524346A (en) | Online content service using catalog-based interactive operations | |
EP2193434B1 (en) | Method and system for promoting and transferring licensed content and applications | |
US9355225B2 (en) | Smart super-distribution of rights-protected digital content | |
WO2008094154A1 (en) | System and method for digital file distribution | |
JP2002123538A (en) | Method and system for registering retrieval page for distributed contents | |
KR20070022390A (en) | System and method for content management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FUSIONONE, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ONYON, RICHARD;STANNARD, LIAM;RIDGARD, LEIGHTON;AND OTHERS;REEL/FRAME:020955/0602;SIGNING DATES FROM 20080424 TO 20080505 Owner name: FUSIONONE, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ONYON, RICHARD;STANNARD, LIAM;RIDGARD, LEIGHTON;AND OTHERS;SIGNING DATES FROM 20080424 TO 20080505;REEL/FRAME:020955/0602 |
|
AS | Assignment |
Owner name: SYNCHRONOSS TECHNOLOGIES, INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUSIONONE, INC.;REEL/FRAME:028175/0511 Effective date: 20120508 |
|
AS | Assignment |
Owner name: SYNCHRONOSS TECHNOLOGIES, INC., NEW JERSEY Free format text: CORRECTIVE SSIGNMENT TO CORRECT THE ASSIGNEE RECORDED ON MAY 8, 2012 ON REEL/FRAME 028175/0511, THE ASSIGNOR HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:FUSIONONE, INC.;REEL/FRAME:029926/0918 Effective date: 20120508 |
|
AS | Assignment |
Owner name: SYNCHRONOSS TECHNOLOGIES, INC., NEW JERSEY Free format text: RESPONSIVE TO THE NOTICE OF NON-RECORDATION OF AN ASSIGNMENT DOCUMENT,NO. 103652828,DATED JAN. 11,2013,THE APPLICANTS HEREWITH SUBMIT CORRECTIVE ASSIGNMENT DOCUMENTS FOR REEL/FRAME NO. 028175/0511;ASSIGNOR:FUSIONONE, INC.;REEL/FRAME:030091/0596 Effective date: 20120508 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW Y Free format text: SECURITY INTEREST;ASSIGNOR:SYNCHRONOSS TECHNOLOGIES, INC., AS GRANTOR;REEL/FRAME:041072/0964 Effective date: 20170119 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: SYNCHRONOSS TECHNOLOGIES, INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:GOLDMAN SACHS BANK USA;REEL/FRAME:044444/0286 Effective date: 20171114 |