JP2013020621A - System and method for linking pre-installed software to user account on online store - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide systems, methods, and non-transitory computer-readable storage media for associating an application for installation on a computer with a user account on an online store.SOLUTION: A server side 240 configured to practice the method presents an application available for download, receives from a client side 290 a software adoption request including an identifier associated with a user account 291 and a proof of entitlement associated with a software package or the user account 291, verifies the proof of entitlement by comparing the proof of entitlement to a database, and if the proof of entitlement is verified, adopts the software package as part of the user account 291.

Description

  The present invention relates generally to the distribution of digital products, and more particularly to techniques for linking software applications to online store user accounts.

  Electronic device manufacturers generally offer electronic device buyers a variety of available options to personalize or customize the electronic device prior to purchase. For example, a personal computer device such as a computer is customized by selecting a processor, memory, hard drive, or accessory. Manufacturers also collaborate with various software vendors to offer ("apply") software applications, or software programs, that can be purchased and pre-installed with a computer before receiving the computer. Software applications, which are typically created by the manufacturer or may include third party applications, some of which are free of charge, either manually or as part of the factory image Are pre-installed on computer devices. Accordingly, the hardware components and pre-installed software are modified for personal use by the purchaser so that the purchased product meets the purchaser's needs.

  After receiving the electronic device, you may want to reinstall or update its pre-installed software at some point in the future. For example, a software provider may have released an updated version of software pre-installed on an electronic device. This is commonly known as software update. To obtain software update data, a buyer visits the software provider's actual store or online store to purchase or obtain an updated version of the software. However, this process is time consuming and sometimes difficult to understand. Similarly, when a buyer reformats a storage device of an electronic device, the purchaser typically must reinstall the software. The purchaser is asked for various compact discs (CDs) or other media to store pre-installed software during this reinstallation. However, the purchaser may have misplaced the CD, and in this case, the reinstallation procedure becomes very complicated.

  Additional features and advantages of the invention will be set forth in the description that follows, or in part will be apparent from the description, or may be learned by practice of the principles disclosed herein. The features and advantages of the invention will be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims. These and other features of the present invention will become more fully apparent from the following description and appended claims, or may be learned by implementing the principles set forth herein.

  Described herein are systems, methods, and computer-readable media for associating an application (ie, a software package), a pre-installed application, a separately purchased application, or the like with a user account. A non-transitory storage medium is disclosed. Here, the user account is associated or stored on the online store. This process is referred to as “adjustment” processing (hereinafter “adoption” is referred to as “adoption”.) Admission processing refers to a specific privilege such as downloading, re-downloading, updating, etc. In other examples, an admission is the user's permission to allow other benefits to the adopted application (eg, gifting or selling the adopted application). • Configuring an account: As one common example, let's say a new computer contains certain pre-installed software, and the user can run the pre-installed software on that new computer. However, the user can In order to qualify to receive and / or use updates, backups, and / or other software-related content or services, the pre-installed software may be adopted to The installation software is associated with a specific user account, such as an online electronic store account, so that the online electronic store can handle updates, backups, restores, in-application purchases, etc. Another user may use the pre-installed software to perform certain functions that require a user account or access rights for this online electronic store account without “adopting” the pre-installed software. You can choose to use the pre-installed software with all the other full features, except when a user advertises the pre-installed software, the online electronic store will Modify the account, database and / or the software itself so that the software is ineligible for adoption by another user, another common example is that a user has already purchased, gifted, or A software package or software application that has been acquired in another way may be installed on the user's computer device, which is a software package that requests the software package or software application. To send a-adoption request to the server. The software adoption request includes an identifier or display of the software package associated with the user account. In some examples, credentials are further included in the admission request as proof of the authenticity of the software package. A credential is a value that can only be derived from having a software package. For example, the credential is associated with or derived from the serial number of the software package. The credential is a value derived from the metadata derived from the software package or associated with the electronic device. For example, the metadata associated with the electronic device is a value that can be derived from the hardware associated with the electronic device. Once the application is adopted, updates, backups, and / or other software-related content or services are available to the user.

  A system configured to implement the method presents a downloadable application, receives a download request for the application to a computer device, and determines that the application is a pre-installed application. The system then presents an authentication prompt to request user authentication to link the application with the user account, receives the user authentication, and in response to receiving the user authentication, a unique hardware identifier Or search for credentials associated with the computer device. The system determines that the application can be linked based on the unique hardware identifier or the credential, and if the application that can be linked is linkable, the application that can be adopted is determined by the user.・ Link with account. The system can present a downloadable application by receiving a page update request and collecting a stub receipt associated with the application upon receipt of such a request. This stub receipt contains the version number and name associated with the application. The system then determines that the application update is available for download on the server based on the version number and name and presents the name of the application.

  In another embodiment, the system receives a downloadable application presentation, receives a page purchase request, receives a manifest associated with the computing device, and presents a list of pre-installed applications based on the manifest This can be done. The manifest includes a list of pre-installed applications that can be downloaded from the server, and the server is a server having an application included in the list of pre-installed applications that can be downloaded. The system also searches the application database to see that the application has been updated available on the server, and stores the version number of the application stored on the computer device on the application database. The available updates are determined by comparing with the version number of the existing application. Based on the version number comparison, determine whether an update to the application exists in the application database. The system determines that the application is a pre-installed application by determining that the application is associated with a stub receipt. The system receives a manifest that includes a list of pre-installed applications associated with a computing device and determines that the application is included in the list of pre-installed applications that the application is a pre-installed application Judgment is made. The system sends a unique hardware identifier or proof of purchase to the server that the pre-installed application can be linked to determine if the pre-installed application is linked to another user account. Thus, it is determined that the pre-installed application can be linked. In yet another example, the system associates the pre-installed software with the user account, associates the pre-installed software with the user account, a unique hardware identifier, or a proof of purchase. The pre-installed software can be linked to the user account by updating the uniqueness table to include Here, the uniqueness table includes another unique hardware identifier associated with another electronic device having different pre-installed software, or proof of purchase, and another pre-installed application may Linked with account.

  In another variation, the system includes an online store user account and pre-installed configuration configured to send an application associated with the user account to one or more computing devices associated with the user account. Receive a request to link software. The system then generates a unique hardware identifier associated with the computing device, or proof of purchase, and the pre-installed application can be linked based on the unique hardware identifier or proof of purchase. judge. If the pre-installed application is linkable, the system links the pre-installed application with the user account. The unique hardware identifier is based on one or more hardware components of the electronic device, such as a MAC address, a UDID (Universal Device Identifier), a logic board serial number, or an Ethernet hardware address. In another example, proof of purchase is used. Proof of purchase can be based on hardware components of the electronic device, metadata associated with the gifting, purchase, or acquisition of the application. Determining that a pre-installed application is linkable sends a unique hardware identifier, or proof of purchase, to the server, and the pre-installed application, or proof of purchase is linked to another user account. It includes determining whether or not. The system determines that the pre-installed application can be linked by determining that the original settings of the computer device include the pre-installed application. Linking the pre-installed application with the user account includes associating the pre-installed application with the user account and updating the uniqueness table to include a unique hardware identifier or proof of purchase. The uniqueness table includes another unique hardware identifier associated with another electronic device having another pre-installed application linked to another user account, or proof of purchase. In yet another example, linking a pre-installed application with a user account includes deleting the metadata associated with the pre-installed application from the manifest, where the manifest is no longer a user. -Further comprising being configured to list pre-installed applications linked to the account.

To illustrate the above-described advantages and features of the present invention, as well as methods for obtaining other advantages and features, reference will now be made in greater detail to the principles described above with reference to specific embodiments of the invention as illustrated in the accompanying drawings. A simple description is shown. The principles herein will be further understood using the accompanying drawings, with the understanding that these drawings are not to be considered as limiting the scope of the invention to show only exemplary embodiments of the invention. It will be described and explained with specific details.
FIG. 1 is a diagram illustrating an exemplary system embodiment. FIG. 2 is a diagram illustrating an exemplary application distribution system. FIG. 3 is a diagram illustrating an exemplary client-server system. FIG. 4 is a diagram illustrating an exemplary method for processing a page update request. FIG. 5 is a diagram illustrating an example of an HTML page associated with a page update request. FIG. 6 is a diagram illustrating an example of an HTML page for requesting user authentication to adopt a pre-installed application. FIG. 7 is a diagram showing another example of an HTML page that requests user authentication to adopt a pre-installed application. FIG. 8 is a diagram illustrating an exemplary method for processing a page purchase request. FIG. 9 is a diagram illustrating an example of an HTML page associated with a page purchase request when the user is not signed in. FIG. 10 is a diagram showing another example of an HTML page associated with a page purchase request when the user is signed in. FIG. 11 is a diagram illustrating another example of an HTML page associated with a page purchase request including an authentication prompt. FIG. 12 is a diagram illustrating an exemplary method for linking a pre-installed application to a user account. FIG. 13 is a diagram illustrating an example of the admission warning. FIG. 14 is a diagram illustrating another example of the admission warning. FIG. 15 is a diagram illustrating an exemplary process for a recovery mode on an electronic device.

  Various embodiments of the invention are described in detail below. Although specific implementations are described, it should be understood that this is described for illustrative purposes only. It will be appreciated by those skilled in the art that other components and configurations may be used without departing from the scope of the present invention.

  The present invention is directed to the need in the art to associate pre-installed software on an electronic device with a distribution center or online store user account. Furthermore, the present invention addresses the need to associate other types of software with user accounts in addition to pre-installed software. For example, online store or online shop users who purchase purchased software, received software as gifts, distributed free of charge or software from software manufacturers, or acquired using other methods. Related to associating with an account. This process is called “adoption” of the software by the user account in the online store. By associating software with an online store user account, software updates and reinstallations are downloaded from the online store. It provides a simpler and more convenient way to manage software on an electronic device. Also, other computing devices associated with the user account further receive software updates and reinstalls from the online store. The following description of FIGS. 1-15 applies to pre-installed applications, software packages and applications acquired (eg, gifted, purchased, or otherwise distributed or acquired) through other means. Is possible. Thus, the term “pre-installed application” as used herein is used synonymously with gifted applications, purchased applications, distributed applications, acquired applications, and the like. In other words, a “pre-installed application” is any application that the user has ownership of. Similarly, a “unique hardware identifier” is any unique identifier that is configured to provide credentials or ownership to an application installed on a computing device. For example, the credentials have a unique value for each copy of the application that is created. The credential is also a redemption code for redeeming the application. In another example, the credential is a combination of a unique value and a non-unique value, such as a unique identifier associated with a redemption code (which may not be unique) and a user account (which is unique). Combine with. A brief introduction to a basic general-purpose system or general-purpose computer device employed to implement the concept is shown in FIG. The method of associating pre-installed software with a user account is described in further detail below. In the following, some modifications are included as various embodiments. Next, the disclosure of the present invention proceeds to FIG.

  With reference to FIG. 1, an exemplary system 100 includes various system configurations including a processing unit (CPU or processor) 120 and system memory 130 such as read only memory (ROM) 140 and random access memory (RAM) 150. A general purpose computing device 100 is included that includes a system bus 110 that couples elements to a processor 120. The system 100 includes a high-speed memory cache 122 that is directly connected to, adjacent to, or incorporated as part of the processor 120. System 100 copies data from memory 130 and / or storage device 160 to cache 122 for high speed access by processor 120. In this way, the cache provides a performance boost that avoids delaying the processor 120 while waiting for data. These modules and other modules control or are configured to control the processor 120 to perform various operations. Other system memory 130 may also be available. Memory 130 includes various memories that include various performance characteristics. It is understood that the present invention operates on a computing device 100 comprising two or more processors 120, or a group or cluster of computing devices networked together to provide more appropriate processing functions. The processor 120 is stored in the storage device 160 as any general-purpose processor, and is configured to control the processor 120 and a dedicated processor in which software instructions are incorporated into the actual processor design, module 1 164 and module 3 166. Etc., and a hardware module or software module. The processor 120 is essentially a fully self-contained computing system that includes multiple cores or processors, buses, memory controllers, caches, and the like. A multi-core processor may be symmetric or asymmetric.

  The system bus 110 is either a memory bus using any of a variety of bus architectures, or any of several types of bus structures including a memory controller, a peripheral bus, and a local bus. A basic input / output (BIOS) stored in the ROM 140 or the like provides a basic routine that supports the transfer of information between elements in the computer apparatus 100 during startup or the like. The computer apparatus 100 further includes a storage device 160 such as a hard disk drive, a magnetic disk drive, an optical disk drive, or a tape drive. The storage device 160 includes software modules 162, 164, 166 that control the processor 120. Other hardware modules or software modules are conceivable. The storage device 160 is connected to the system bus 110 by a drive interface. The drive and associated computer readable storage medium provide non-volatile storage of computer readable instructions, data structures, program modules and other data for the computer device 100. In one aspect, a hardware module that performs a particular function is stored on a computer-readable non-transitory storage medium in conjunction with the hardware components necessary to perform the function, such as processor 120, bus 110, display 170, etc. Included software components. The basic components are known to those skilled in the art and are appropriate depending on the type of device, for example whether the device 100 is a small, handheld computer device, desktop computer or computer server. Various modifications can be considered.

  The exemplary embodiments described herein employ a hard disk 160, but other types of computer-readable media that store computer-accessible data, such as magnetic cassettes, flash memory cards, digital universal disks, cartridges, It should be understood by one of ordinary skill in the art that random access memory (RAM) 150, read only memory (ROM) 140, cables, wireless signals including bitstreams, etc. may be further used in the exemplary operating environment. It is. Computer-readable non-transitory storage media explicitly exclude media such as energy, carrier wave signals, electromagnetic waves and the signal itself.

  In order to allow user interaction with the computer device 100, the input device 190 may include many microphones, gestures, or touch sensitive screens for graphic input, keyboards, mice, motion input and voice, for example. Indicates the input mechanism. Further, the output device 170 is one or more of many output mechanisms known to those skilled in the art. In some examples, a multi-mode system allows a user to provide many types of inputs for communicating with computing device 100. The communication interface 180 generally controls and manages user inputs and system outputs. Since there are no restrictions on operating on any particular hardware configuration, the basic functionality herein is easily replaced with an improved hardware configuration or firmware configuration as they are developed.

  For clarity of explanation, an illustrative system embodiment is presented as including individual functional blocks including “processors” or functional blocks labeled as processor 120. The functions shown by these blocks include hardware that can execute software and shared hardware including but not limited to hardware such as a processor 120 that is manufactured for the same purpose as software that runs on a general-purpose processor, or Provided using dedicated hardware. For example, the functions of one or more processors shown in FIG. 1 are provided by a single shared processor or multiple processors. (The use of the term “processor” should not be construed as indicating only hardware capable of executing software.) Exemplary embodiments may include microprocessor and / or digital signal processor (DSP) hardware. , A read only memory (ROM) 140 for storing software for executing the operations described below, and a random access memory (RAM) 150 for storing the results. Further provided are very large scale integrated circuit (VLSI) hardware embodiments and custom VLSI circuitry in combination with a general purpose DSP circuit.

  The logical operations of the various embodiments may be (1) a series of computer-implemented steps, operations or procedures executed on a programmable circuit in a general purpose computer, or (2) executed on a dedicated programmable circuit. A series of computer-implemented steps, operations, or procedures, and / or (3) interconnected machine modules in a programmable circuit, or program engine. The system 100 shown in FIG. 1 implements all or part of the listed methods, is part of the listed systems, and / or instructions on listed computer-readable non-transitory storage media. Works according to. Such logical operations are implemented as modules configured to control the processor 120 to perform specific functions according to the programming of the module. For example, FIG. 1 shows three modules Mod 1 162, Mod 2 164, and Mod 3 166 that are modules configured to control the processor 120. These modules are stored on storage device 160, loaded into RAM 150, memory 130 at runtime, or stored in other computer readable storage locations as is known in the art.

  Having disclosed several components of the computing system, the present disclosure is then directed to an online application distribution store or marketplace on a computer device such as a personal computer, laptop, game console, smartphone, mobile phone, or tablet PC. Return to the description of the technique of “associating” (similar to linking or adopting) a pre-installed software with a user account. The techniques described herein update the pre-installed software by linking the pre-installed software to a user account on an online store or online distribution site such as a distribution center, or a computer This improves the efficiency and convenience when re-installing the apparatus. The online distribution site sends pre-installed software associated with the user account to one or more computing devices linked to the user account. Both pre-installed software and updates to pre-installed software can be sent to one or more computer devices. In some examples, the distribution site may specify a limit on the number of computing devices associated with the given user account that are allowed to receive software associated with the given user account. it can. In another example, pre-installed software is part of a standard “image” that was generated once but then repeated for each of a group of computing devices. For example, a standard device “image” includes an operating system, drivers, programs, settings, and the like. Thus, each “imaged” device has the same software configuration, including pre-installed software, and after the end user (or other entity) sets up the device, the pre-installed software Adopted in online stores or online markets and can be associated with user accounts.

  FIG. 2 illustrates an exemplary application distribution system. In this example, the distribution system 200 shows a distribution center 210, an application database 220, a configuration server 230, the Internet 250 or other network, a computer device 260, a computer device 270, and a portable device 280. Distribution center 210, application database 220, and configuration server 230 together represent various independent components on the server side 240 of the client-server model. Similarly, computing device 260, computing device 270, and portable device 280 represent various independent components on the client side 290 of the client-server model. Thus, a broad overview of the distribution system 200 can include a server side 240 that communicates with the client side 290 via the Internet 250. As an example, the server side 240 can be expressed to the user as an online store that sells and distributes applications or multiple cloud servers. The client-side 290 device can communicate with the online store using an application management computer program stored on the device. In other examples, the Internet 250 can be replaced with other communication networks such as computer networks, telephone lines, Ethernet, local area networks, wired networks, and wireless networks.

  The computing device 260 can include an application 261. Application 261 may include an application pre-installed on computing device 260, an application provided as part of a package, or an application provided with some type of installation media. In one common example, the owner of computing device 260 may have purchased computing device 260 from a manufacturer that already has these applications installed. Among the applications 261 are applications acquired by the computer device 260 via other means (or software packages), for example, applications given, purchased, or distributed free of charge, to name a few. In addition. Application 261 may further include an application purchased from distribution center 210 by a user of computing device 260. When a user purchases a desired application from the distribution center 210, the user associates with metadata associated with the application that the user has already purchased, and payment information for paying the distribution center 210 in exchange for the desired application. Log in to the user account 291 that includes the metadata etc. When logged in, the user selects the application that he wants to purchase. If the user agrees to pay for the application purchase, the user's payment information is used to complete the transaction. When the transaction is complete, the desired application will be associated with the user account 291 and the user will be able to download the desired application and updates to the desired application. These applications and the like associated with the user account 291 can be further downloaded or re-downloaded to other devices associated with the user account 291.

  In some examples, the user may have an option not to associate the application with a user account at this point. For example, a user who receives an application as a gift may or may not have a user account and do not want to associate the application with the user account. In the first example, the user can install the application on the computing device 260 without having to set up a user account. If the user wants to receive updates or wants to install the application on other electronic devices he owns, the user selects a user account and links the application to the user account ( Ie Adopt). In this example, computing device 260, computing device 270, and portable device 280 are all associated with user account 291 and thus receive updates and re-downloads of all applications associated with user account 291. It is configured to be able to. In addition, the portable device 280 can communicate with the computer device 270 to transfer digital data and applications between the two devices. In one example, computing device 270 is configured to be a repository center (storage center) that stores all applications associated with user account 291 and to transfer selected applications to portable device 280. . As used herein, the term “application” refers to a software program provided by a software provider, or a copy or copy of an application. In other examples, in addition to software applications and software programs (e.g., system software, enterprise software, multimedia files, video files, audio files, and image files) that are first pre-installed on a computer device, etc., Other digital products, such as software applications that the user has ownership of, can also be distributed / redistributed by distribution center 210 in association with user account 291.

  Distribution center 210 is coupled to application database 220 and configured to sell, supply, and maintain applications from application database 220. The application database 220 can be configured to store some or all of the applications that can be distributed from the server side 240. These applications can be sold, updated, and delivered (ie, sent) to client-side 290 devices via the Internet 250. Accordingly, the distribution center 210 means an online store for applications. For example, the application database 220 receives a request for an application from the distribution center 210 and sends the requested application to the distribution center 210 in response to the request, which then sends the application to the requesting device. To do. A requested application is an application that can be purchased or previously associated with a user account (ie, an application that has been applied, acquired separately, or pre-installed). In other examples, the application database 220 can send the requested application directly to the requesting device. In yet another example, the application database 220 can reside on the client side 290, where the server side 240 is associated with access to a particular application in the application database 220 associated with the user account. Can be allowed based on different applications.

  The client-side 290 device sends a software admission request to link a pre-installed application on the device or a separately acquired but not adopted application to the user account (ie, Associated or adopted). By linking one application, the user can associate that application with one user account, so the user downloads the application to other devices that are also associated with the user account. be able to. This process is called “linking”, “adopting”, or “associating” the application. For example, computing device 260 may request that an application from application 261 be linked with user account 291. This request is sent to the distribution center 210 along with a unique identifier (eg, a unique hardware identifier) associated with the application or computing device 260 over the Internet 250, where the application is associated with the user account 291. It is determined whether or not A unique hardware identifier is a unique identifier used to distinguish a particular device from all other devices and can be based on the hardware of that device. For example, a manufacturer must ensure that the device that it manufactures is unique and therefore has a unique hardware identifier that is different from the unique hardware identifier of any other device. Can do. As an example, the unique hardware identifier may be based on the device's logic board serial number and / or Ethernet hardware address. In one example, these two values are concatenated and hashed to generate a unique hardware identifier. In other examples, other metadata specific to this device may be concatenated, hashed, or synthesized using various data manipulation algorithms to form a unique hardware identifier. In yet another example, the unique identifier used to determine whether the application can be associated with the user account 291 is that the application associated with the unique identifier (ie, the software package) is legal from the software manufacturer. Can be based on any other proof of purchase or qualification that provides evidence that In one example, the unique identifier is derived from metadata or attributes associated with the application. In another example, the unique identifier is from metadata associated with an application, client device, user account, other client devices associated with the user account, or any combination of one or more of the above, etc. Can be derived.

  In one embodiment, distribution center 210 receives the unique identifier and processes or parses it to determine if the application can be associated with the user account. In certain examples, an application cannot be associated with a user account. For example, if an application was previously associated with another user account, the device application is not associated with the user account. As another example, an application cannot be associated with a user account if it is not a legitimate copy. This occurs when the user manually copies an application that was originally installed from one device to another. As yet another example, this association process requires the user to be logged into the user's account on the electronic device in order to link the application to the user account.

  In another embodiment, distribution center 210 receives the unique identifier and processes or parses it to determine if the application is associated with a user account. As an example, processing the unique identifier includes validating the unique identifier by comparing the unique identifier with a database. The database has a plurality of entries each storing a unique identifier associated with a legitimate copy of the application. The result of the comparison is used to determine the application's application status, for example, whether the application is a legitimate copy, an illegal copy, or is already associated with a user account. As another example, the processing of the unique identifier can include entering the unique identifier into a hash table to determine the application's admission status. In yet another example, a unique identifier may be received by the verification engine so that the engine determines whether such an installation of the application is valid or not yet applied. . In yet another example, other data processing techniques can be applied to the unique identifier to determine whether an application can be associated with a user account. The application can be acquired by the user even recently. In other words, the application can appear to have been acquired by the user even after purchasing and receiving the electronic device from distribution or manufacture. Alternatively, the application can be acquired when the electronic device is purchased. When the distribution status is determined by the distribution center 210, a confirmation related to the application status is transmitted to the electronic device. A confirmation is sent to inform the electronic device of the status of the admission process. Based on the confirmation, the electronic device requests a download or update of the software package. In another example, the distribution center 210 automatically starts a software package download process or an update process for the electronic device according to the application status.

  Server side 240 incorporates a number of servers and tables to determine if a link request should be allowed. For example, the distribution center 210 includes a uniqueness server 211 that is configured to process the unique identifier to determine the legitimacy or legality of the link request. Uniqueness server 211 includes a uniqueness table configured to maintain a database, or a table of electronic devices having one or more pre-installed applications linked to user accounts. As an example, the uniqueness table may be a unique hardware identifier of a device that has already linked the pre-installed application to the user account (ie, a device that has already adopted the pre-installed application associated with the device). Configured to store. The uniqueness table is further configured to store metadata associated with the application associated with the user account. If the device adopts (ie, links) some or all of the applications with the user account, the device's unique hardware identifier, or the unique identifier of the adopted application, is stored in the uniqueness table. Stored in This prevents future requests to link applications that have already been adopted. For example, executing a query as to whether the unique identifier is in the uniqueness table determines whether the device associated with the unique hardware identifier has already linked the pre-installed application with the user account. Similarly, the query further determines whether the application associated with the unique identifier is already linked with the user account. As another example, the uniqueness table may be stored in the electronic device along with metadata associated with one or more pre-installed applications of the electronic device that have been previously adopted (ie, linked to a user account). It is configured to store a unique hardware identifier. In other words, the uniqueness table is configured as a one-to-many mapping between the device's unique hardware identifier and one or more metadata associated with the selectively installed device's pre-installed application. Is done. Querying the uniqueness table for a unique hardware identifier returns nothing if the unique hardware identifier does not exist in the uniqueness table, and the unique hardware identifier exists in the uniqueness table In some cases, metadata associated with a pre-installed application that is selectively adopted is returned. As a result, there is a function of selectively applying a pre-install application on the device with the first user account and selectively applying another pre-install application on the device with the second user account. can get. In yet another example, the uniqueness table is configured to maintain a database or table of applications linked to the user account. Already linked applications maintain a current database of applications that have been adopted by having a unique identifier stored in a uniqueness table.

  In one example, the configuration server 230 can verify the legitimacy of the link request by checking the original configuration of the electronic device, and the server can specify a specific time when the electronic device is shipped from the manufacturer. This verification is performed by verifying or determining whether the application has been pre-installed on the device. This configuration server can further verify or identify the application for which the user has ownership, regardless of whether the application is installed on the user device or associated with a user account. Thus, it is possible to further identify applications for which the user has ownership but is not associated or installed. The setting server 230 includes a database that stores the original settings of the electronic device created by the manufacturer. The original settings include the operating system version and application version supplied with the electronic device, if any. For example, a user who orders an electronic device through an online store can configure a device that includes one or more applications at the time of purchase. The application is installed in the electronic device at the time of manufacture based on the setting at the time of purchase. During manufacturing, the settings of the electronic device are communicated to the setting server 230 for subsequent reference. When the configuration server 230 receives a reference request including a unique hardware identifier from an electronic device, the configuration server 230 performs a search or query on the database and installs the operating system version installed on the device and / or the electronic device. Returns a list containing the application versions. The configuration server 230 compares the list of installed applications with the application that the user is trying to associate with the user account, and whether the application that the user is trying to associate is a legitimate installation or has previously been another user account. It is determined whether it is associated with. Alternatively, the setting server 230 passes a list of pre-installed applications to the distribution center 210 and determines whether the link request should be permitted. This check prevents the user from trying to bypass the distribution system 200 by copying the pre-installed application from one device to another.

  When one or more elements on the server side 240 validate the link request, the pre-installed application is associated with the user account (ie, application adopted). Also, the uniqueness server 211 or the setting server 230 can be updated to take into account application adoption. For example, because some or all of the pre-installed applications associated with the electronic device have been adopted, a new entry is added to the uniqueness table of the uniqueness server 211. In some examples, the distribution center 210 sends the pre-installed application update to the computing device 260 after the pre-installed application is associated with the user account. In another example, the distribution center 210 transmits the pre-install application to other devices associated with a user account, such as the computer device 270, even if the computer device 270 was not originally configured with a pre-install application. Through similar requests for application adoption, the pre-installation application of the computing device 270 stored in the application 271 and the pre-installation application of the mobile device 280 stored in the application 281 are associated with the user account 291 and finally To the computer device 260, the computer device 270, and / or the portable device 280.

  FIG. 3 illustrates an exemplary client-server system. The client-server system 300 includes a client device 350 and a server 360. Server 360 is configured to respond to requests from client device 350 and includes one or more elements on server side 240 of FIG. Client device 350 associates an application (pre-installed or otherwise obtained) with a user account by providing a page request to server 360. The client device 350 further associates other applications with the user account by providing the same or similar page request to the server 360 as in the pre-installed application.

  One type of page request is a page update request 301. A page update request 301 is a request transmitted to the server 360 and executes a query for updating available applications. In response to the page update request 301, the server 360 is configured to notify the user that an application stored on the client device 350 has an available update, and a hypertext markup language (“ HTML ") page 303 is returned. In some examples, the server 360 returns metadata to the client device 350 and swaps, and the client device 350 generates an HTML page for presentation to the user. The page update request 301 includes a digital receipt for each application stored in the client device 350. This receipt is associated with the application and includes metadata describing the purchase or ownership of the software. One type of receipt is an actual receipt associated with a purchased application or an adopted application. The actual receipt includes a description of the application, the version number of the application, information regarding the purchaser of the application when the application is purchased, information regarding the device on which the application is first installed, and the like. In other words, the actual receipt is a proof of purchase unique to the purchaser and / or the electronic device from which the application was purchased. Another type of receipt is a stub receipt. A stub receipt contains a subset of the information in the actual receipt and is part of the application if the application is not advertised by a user account. In one example, the stub receipt uniquely identifies a copy of this application from other copies. This allows the server to determine whether a copy of this particular application (given to the user or otherwise obtained by the user) can be adopted by the user. In another example, the stub receipt is generated by the manufacturer as a receipt associated with the pre-installed application. To facilitate and simplify application installation by manufacturers, stub receipts contain a minimum amount of information that is less than the actual receipt. For example, the stub receipt includes an application identifier that identifies the application to the server, and further includes a version number that identifies the version of the application. The application identifier is a name associated with the application. The stub receipt does not include information specific to the purchaser, such as when the application is purchased, and information regarding the purchaser of the application or the device on which the pre-installed application is installed. In other words, the stub receipt does not include user account, user account information, or information about client devices, computer devices, or other devices. The application identifier is a name associated with the pre-installed application. In some examples, the stub receipt is generated by the manufacturer when the application is pre-installed on the device or when the device is preparing to supply. In another example, the stub receipt is generated by the server 360 and then sent to the client device 350 associated with the pre-installed application. Server 360 generates a stub receipt in response to a request by client device 350 or a regularly scheduled communication between server 360 and client device 350. When the pre-installed application is adopted, the stub receipt is replaced with the actual receipt. In another example, a stub receipt is generated as a receipt that is associated with a purchase, gift, or otherwise acquired application that is not associated with a client device when the application is acquired. This stub receipt is generated by a manufacturer, an application distributor, or an online store. In some cases, stub receipts are batched for delivery and assigned to an application. The stub receipt is stored on the server and used to authenticate the admission request. Similar to the previous example, the stub receipt is replaced with the actual receipt during the application admission process. The actual receipt is generated by the client device 350, server 360, or other element of the client-server system 300.

  In this example, the page update request 301 includes a stub receipt A 311 associated with the pre-install application 310, a stub receipt B 321 associated with the pre-install application 320, and an actual receipt 331 associated with the application 330. . Since the application 330 is purchased from the server 360 after the purchase of the client device 350, the application 330 includes an actual receipt. In response to the page update request 301, the server 360 generates an HTML 303 that informs the user whether the pre-install application 310, the pre-install application 320, or the application 330 has an available update downloaded from the server 360. To do. Available updates associated with a pre-installed application that is not adopted (ie, not linked or associated with a user account) will cause the pre-installed application to be added to the user account. It will not be downloaded until it is activated. When an available update is downloaded and installed on the client device 350, the stub receipt is displayed when the application is purchased (i.e., the date when the available update was installed) and the user and application that purchased the application first. Is replaced with an actual receipt that includes other metadata such as the electronic device installed.

  Another type of page request is a page purchase request 302. The page purchase request 302 is transmitted to the server 360 and requests a list of applications purchased by the user of the client device 350. In response to the request, the server 360 returns an HTML page 303 configured to notify the user of applications purchased by the user of the client device 350 and applications installed on the client device 350 as needed. To do. Purchased applications that are not stored on the client device 350 are downloaded and installed. The HTML page 303 further includes an application that can be adopted (ie, linked to or associated with a user account). Applications on the client device that are not associated with a user account are selected for adoption via a page update request 301 or a page purchase request 302. The unadopted application sends a receipt in the request, or other form of credentials, and installs the application or desired application on the client device.

  The page purchase request 302 includes a manifest 340. Manifest 340 is configured to store information associated with pre-installed applications or otherwise obtained applications. This information is used by server 360 to inform the user of applications that can be adopted. The manifest 340 includes a list, table, or other data structure configured to store the version number of the application on the client device 350. The version number of the application can be found in the stub receipt associated with the application, or other metadata. In one example, the manifest 340 is generated only after the client device 350 is activated. For example, the manifest may utilize a spotlight (ie, search) function on the client device to search the computer for stub receipts that are later used to generate the manifest, thereby providing a first of the client device. Generated during boot. As described below, the manifest is stored on a configuration server that is accessed while linking the application with the user account or during the recovery mode of the electronic device.

  In this example, the client device 350 is queried to place a stub receipt 311 and a stub receipt 321 that are later used to generate the manifest 340. During the reformatting or recovery of the client device 350, both the pre-installed application and the application obtained by another method are deleted from the client device 350. The application linked to the user account is re-downloaded to the client device 350. However, pre-installed applications that are not linked to a user account are at risk of being completely lost. As described in more detail below, manifest 340 functions as a mechanism to prevent loss of unadopted applications. Adoptable applications are not downloaded until the pre-installed application is linked or associated with a user account. As available updates are downloaded and installed on client device 350, manifest 340 is edited to remove the stub receipt associated with the currently applied application. The installed application includes an actual receipt. In some examples, the processing of the HTML page 303 and the generation of the page update request 301 and the page purchase request 302 accompanied by the search are managed and processed by an application management program (not shown) installed in the client device 350. The application management program is developed in-house by the manufacturer and is specifically configured to communicate with a server belonging to the manufacturer.

  The client-server system 300 is acquired by the client device 350 but is not associated with a user account (eg, gifted, purchased but not linked to a user account, or to the client device via other means). Adopt more applications to be delivered. As an example, the acquired application is linked to a user account via a page update request, a page purchase request, or other page request. The request includes a stub receipt, metadata associated with the stub receipt, or metadata derived from the stub receipt. As another example, if an unadopted application (ie, an application that has not yet been linked to a user account) is obtained by client device 350, manifest 340 is updated.

  FIG. 4 illustrates an exemplary method for processing a page update request. The method 400 illustrating the operations performed by the client and server is configured to manage communication between the client and server during a page update request. Operations performed by the server are performed by a distribution program stored on the distribution center or other components located on the server side, and operations performed by the client are stored on the client's electronic device It is executed by an application management program. The method 400 begins with the user selecting an update tab link in a graphics user interface supplied by the client device. An exemplary update tab link is link 451 of FIG. When the client receives a user request for a page update (401), the client queries or searches the client device for a receipt associated with an application installed on the client device, or other form of credentials (403). In other examples, the query starts automatically without user interaction. For example, the server initiates a query by communicating with the client at a predetermined time interval or point in time. The search is performed using functionality associated with the operating system of the client device, or an application or routine stored on the client device. The receipt found or a copy of the receipt is sent to the server (405). Receipts are transferred via any communication network such as Ethernet, the Internet, and a local area network. The server receives the receipt and processes the receipt to determine if the application associated with the receipt has an update (407). This includes accessing an application database, such as application database 220 of FIG. 2, and comparing the receipt version number to the application version number stored in the application database. This further includes verifying that the application is subject to adoption by determining that the application installed on the client device is configured to be delivered by the server. In some embodiments, the server further verifies that the application has not been previously adopted at this point. This includes searching for a unique identifier that uniquely identifies a copy of the installed application (from a server or client) and verifying that the unique identifier is not associated with any user account. . The list of applications including updates is used to generate 408 HTML pages or to manipulate some other user interface such as a desktop application or a smartphone application. The HTML page contains information about the application including available updates. This information includes the original purchase date of the application, a description of the application and a description of changes or modifications in the updated application. HTML is just one example of a notification sent to the client to notify the client that one or more applications have updates or are available for adoption. Thereafter, the server transmits an HTML page to the client (409). In some examples, the server sends an HTML page over the same channel that the client sent the receipt. Rather than pre-packaging and sending an HTML page to the client, the server sends enough information to the client to update the locally installed client application.

  FIG. 5 shows an example of an HTML page associated with a page update request for a pre-installed application that is advertized in an online store or online marketplace or associated with a user account. The HTML page 450 includes an Updates link 451 that is selected by the user to request a page update. The update link 451 is arranged on the menu bar together with other links such as “Special Feature”, “Top Chart”, “Category” and “Purchase”, and is convenient for the user to access various functions of the application management program. Provide a quick way. In some examples, the icon indicating the update link 451 includes a number that defines the number of applications stored on the client device that have available updates. The number of icons is generated before the user selects the update tab link 451 through periodic communication between the server and the client device.

  For example, the client device periodically communicates with the server to retrieve the latest version number of the stored application that has available updates. In this example, update link 451 has been selected and one application containing available updates is presented in HTML page 450. One application is presented with an application description 457 that describes the application. Application description 457 includes the name of the application, the creator of the application, the version number of the application, the release date of the application, or other information associated with the application. The application description 457 further includes an icon 455 that provides identity to the application and a summary of changes 459 implemented in the updated version of the application. Thus, since the information is provided to the user, the user can determine whether or not to update the information after sufficiently obtaining the information. The HTML page 450 further includes a selectable link 461 that allows the user to select whether they want to receive application updates. The number of available updates is displayed in title 453. Title 453 is configured to provide another convenient place where a user can quickly determine the number of updates available. In some examples, the HTML page 450 further includes a selectable link adjacent to the title 453 that updates all applications that have available updates.

  Returning to FIG. 4, the client receives the transmitted HTML and presents the HTML page to the user (411). As described in FIG. 5, the HTML page provides a graphical user interface that lists the applications that contain available updates, a description of the application, and one or more links that can be selected by the user to allow application updates. Present. The client receives the user authentication and updates the application (413). If user authentication has been received, the client determines whether the application requires an admission before being updated (415). This includes checking the receipt of the application installed on the client to determine if the receipt is a stub receipt. If the receipt is a stub receipt, the application associated with the stub receipt is a pre-installed application that is potentially not yet applied to the user account. Accordingly, user authentication is required and the client presents an HTML page to the user requesting (417) user authentication to adopt or associate the application to the user account. User authentication includes transmitting personal information over a communication network. For privacy reasons, the HTML page informs the user that personal information will be sent during the authentication process and requests permission to transmit this personal information over the communication network.

  FIG. 6 shows an example of an HTML page that requires user authentication to adopt an application, which may have been sold together and / or pre-installed with the purchase of a computer device. It is unknown. The HTML page 470 is a page update that presents the user with four applications including available updates. Accordingly, the icon of the Updates link 471 includes the number “4”. In this example, the user has chosen to update all applications via the “UPDATE ALL” link 475. However, in other examples, the user may further choose to update a single application by selecting one of the update links 476, 477, 478, or 479. Applications that include available updates include pre-installed applications 472 and purchased applications 473. In some examples, there is no difference in the presentation of pre-installed applications and purchased applications at this stage. However, if the user chooses to update a pre-installed application or an application that is not linked to a user account, the HTML page 470 can present a prompt 480 to the user. In FIG. 7, prompt 480 is described in further detail.

  FIG. 7 shows another example of an HTML page that requires user authentication to adopt an application. Prompt 480, also known as an authentication prompt, refers to a just-obtained application that is not pre-installed on a computer and possibly not associated with a user account or associated with a user account. When the user selects to update, it is presented to the user. In this example, prompt 480 includes icon 481, login 482, password 483, password assistance 484, description 485, help link 486, account creation 487, cancel 488 and sign-in 489. Description 485 provides text information that informs that an application pre-installed (ie bundled) on this electronic device is associated with the user account if the user wants to update the application. . This description 485 further informs the user that the unique hardware identifier associated with the electronic device is sent to the server to determine whether the application admission should be allowed to adopt the application. Icon 481 is used to brand the application update function of the application management program. Login 482 and password 483 specify the user account that the user wishes to associate with the pre-installed application. Password assistance 484 is selected by a user who needs assistance with the password. Once the desired user account and correct password are entered, the user begins the admission process by selecting sign-in 489. If the user does not have a user account or wishes to associate the pre-installed application with a new account, the user selects Create Account 487. If the user cancels the application and does not want to update, the user selects cancel 488. The user selects help link 486 if he wants a more detailed description of any of the elements described above. In another example where the HTML page requires user authentication to associate an application that is not pre-installed on the electronic device but is otherwise acquired by the electronic device, description 485 carries the appropriate message to the user. Will be changed as follows. For example, description 485 states that “applications“ X ”,“ Y ”and“ Z ”are assigned to this applet ID to receive future updates. The unique identifier stored on the computer must be sent to Apple to verify the credentials. "

  Returning to FIG. 4, the client receives user authentication and adopts the application (419). This user authentication can be received by a user entering a user account and password at the prompt presented by the client as described in FIG. When the client receives the user authentication, the client proceeds to the application application (421). An exemplary process for applying an application to a user account is described below in FIG. In some examples, all pre-installed applications must be associated with a user account at the same time. Thus, a user cannot selectively link one pre-installed application associated with an electronic device to one user account, and cannot separate another pre-installed application associated with the electronic device. Cannot selectively link with other user accounts. By simultaneously applying all pre-installed applications on the electronic device, the unique hardware identifier associated with the electronic device is sufficient to notify the server to which the pre-installed application has been applied. Simplify the computational overhead of managing the admission process. In other examples, pre-installed applications on the electronic device are selectively associated with multiple accounts. Accordingly, the first pre-install application is associated with the first electronic device and the second pre-install application is associated with the second electronic device. However, managing a pre-installed application on the server requires storing the unique hardware identifier of the electronic device and the pre-installed application that has been adopted. These examples are also applicable to applications acquired separately from the purchase of electronic devices. For example, if a large number of applications are installed and gifted on an electronic device, they are associated with a user account individually or as a group.

  FIG. 8 illustrates an exemplary method for processing a page purchase request. Method 500 illustrates operations performed by a client and a server, and the method 500 is configured to manage communication between the client and server during a page purchase request. Operations performed by the server are performed by a distribution program stored on the distribution center or other components located on the server side, while operations performed by the client are performed on the electronic device on the client side. It is executed by the stored application management program. In some examples, the distribution program stored on the distribution center and the application management program stored on the electronic device are configured to further perform the method 400 of FIG. 4 during a page update request. The method 500 begins with the user selecting a purchase tab link in a graphics user interface supplied by the client device. An exemplary purchase tab link is link 551 of FIG. When the client receives a user request for page purchase (501), the client searches or queries the application information. In this exemplary method, the application information includes a manifest and / or a receipt (503). In other examples, the application information includes an application or software package that is not associated with a user account. The user account has ownership of the software package. Ownership is a credential such as a digital receipt. In some examples, the manifest is similar or substantially similar to manifest 340 of FIG. The search or query may be performed by one or more programs or functions available on the client. Application information, including manifests, receipts (actual and stub receipts), and user account information, etc. (e.g., credentials or ownership for applications that have not yet been adopted) It is transmitted to the server as an admission request (505). The application information is sent to the server to generate a page purchase that informs the user of installed applications, installable applications, and applications to be adopted (505). The application information sent depends on whether the user is signed in on the client. For example, user account information is accessible and is sent as part of the application information when the user is signed in on the client. As described above, the user account information includes information regarding the application associated with the user account. Similarly, the receipt includes information about the application associated with the electronic device that the client is executing. The manifest includes information about applications that were originally pre-installed on the electronic device, or information about applications that the user has ownership but is not installed on the user device or associated with a user account. Since other types of application information are further transmitted to the server to generate page purchases, these are only exemplary types of application information.

  The server receives the transmitted application information (ie, manifest, receipt, user account, and other user account information) and creates one or more lists of applications based on the received information (507). The application list and the process used to create the application list vary depending on the information received. The first application list includes applications installed on the client electronic device. The second application list includes applications associated with the user account and is installed on the client electronic device. The third application list includes applications that are sometimes linked with user accounts. The third list of applications includes applications pre-installed on the client's electronic device and / or applications that the client has ownership of, but is not adopted or installed. In addition, the other application list is an application generated by being purchased or otherwise obtained without being associated with the user account. Depending on the application information received by the server, one or more of the application lists described above are created. In some examples, creating the application list includes accessing an application database, such as application database 220 of FIG. The server generates an HTML page based on the created application list (508). Generation of the HTML page includes accessing an application database and receiving metadata associated with the application in the application list. For example, the metadata includes an application name, an application description, an application version number, an application purchase date, an image associated with the application, and the like. When the HTML page is generated, the server transmits the HTML page to the client (509). The client then presents the HTML page to the user (511). Depending on whether the user is signed in on the client, different information is presented to the user.

  FIG. 9 shows an example of an HTML page associated with a page purchase request when the user is not signed in. In this example, HTML page 550 presents a list 557 of applications that can be adopted to the user. Of the three applications that can be adopted, the applications “iMovie” and “GarageBand” have available updates (Update Available) as indicated by sentences 558 and 559, respectively. The HTML page 550 includes a purchase link 551. In some examples, purchase link 551 functions in a manner similar to or substantially similar to update link 451 of FIG. The HTML page 550 further includes a headline 553 that informs the user of the number of applications that can be adopted. Description 555 provides the user with an explanation of the admission process in the hope that it will assist the user in determining whether he wants to adopt the application. The HTML page 550 further includes instructions 552 that inform the user that they must sign in to the user account to receive information regarding purchases associated with the user account. In this example, HTML page 550 includes one acceptance (ACCEP) link 554 that initiates the admission process when selected by the user. In other examples, the HTML page 550 includes a consent link for each application that can be adopted, so that the user can adopt a single application that can be adopted, multiple applications that can be adopted, or all applications that can be adopted. You can choose to accept The user selects the consent link 554 via a touch screen, mouse click, keyboard, or other user input device.

  FIG. 10 shows another example of an HTML page associated with a page purchase request when the user is signed in. The HTML page 560 presents two application lists to the user. In this example, presentation of application list 562 includes applications that can be adopted, and presentation of application list 564 includes previously purchased applications. The two application lists are presented in separate and separate parts of the HTML page 560. The presentation of application list 564 includes metadata associated with previously purchased applications such as the name of the application, the image associated with the application, software manufacturer, purchase date and status 566. Status 566 is configured to display the current status of the purchased application. For example, if the application is currently installed on the client's electronic device, status 566 is “installed state”. The situation 566 is configured to display the sentence “Installed” in this state. In this example, all four purchased applications are installed on the client's electronic device. As another example, if the application is purchased but not installed on the client's electronic device, status 566 is “installed”. For example, the application has not been downloaded to this device or has been selectively deleted from the device. The situation 566 is configured to display the sentence “install” in this state. Furthermore, the status 566 includes a link that can be selected by the user in the case of “installed status”. As a result of the user selecting a selectable link, the application is downloaded and installed on the electronic device.

  Returning to FIG. 8, the client receives user input as a request to adopt the application (513). In some examples, the user input is to select the accept link 554 of FIG. The client requests user authentication to link the application to the user account (515). An example HTML page containing an authentication prompt requesting user authentication to link an application to a user account is shown in FIG.

  FIG. 11 shows another example of an HTML page associated with a page purchase request that includes an authentication prompt. If the user chooses to accept the pre-installed application admission, the HTML page 570 includes an authentication prompt 575. An authentication prompt 575 is included as part of the HTML page sent from the server and is presented to the user after the user chooses to accept the pre-installed application admission. In some examples, authentication prompt 575 is identical or substantially similar to authentication prompt 480 of FIG.

  Returning to FIG. 8, the client receives the user authentication and links the application to the user account. The user account is a user account that is input during user authentication. For example, the user enters a user name and password for a user account associated with the application. After receiving the user authentication, the client proceeds to the application application (519). An exemplary process for applying an application to a user account is described below in FIG. In some examples, all pre-installed applications must be associated with a user account at the same time. Thus, a user cannot selectively link one pre-installed application associated with an electronic device with one user account and another pre-installed application associated with the electronic device with another user account. Cannot selectively link. Since the unique hardware identifier associated with the electronic device is sufficient to notify the server that a pre-installed application is being applied, all pre-installed applications on the electronic device are simultaneously applied This simplifies the computational overhead in managing the admission process. In another example where a pre-installed application on an electronic device is selectively associated with a large number of accounts, managing the pre-installed application on the server is adopted in addition to the unique hardware identifier of the electronic device. Need to store pre-installed applications.

  FIG. 12 illustrates an exemplary method for linking a pre-installed application to a user account. The method 600 for indicating a communication protocol executed between a client and a server is configured to manage the process of linking a pre-installed application to a user account. Operations executed by the server are executed by a program on the distribution center or other components on the server side, and operations executed by the client are executed by an application management program stored on the client electronic device. . The application management program is configured to install, delete, maintain, or otherwise manage software applications stored on the client. In some examples, the distribution program stored on the distribution center and the application management program stored on the electronic device are configured to further perform the method 400 of FIG. 4 and / or the method 500 of FIG. . In some examples, the method 600 is performed after “Proceed to Application Adoption” (421) of FIG. 4 or “Proceed to Application Adoption” (519) of FIG.

  The method 600 generates a unique hardware identifier (620). The unique hardware identifier serves as a digital receipt of legitimate application ownership or entitlement. The unique hardware identifier is generated from combining one or more identifiers specific to the electronic device. For example, the unique hardware identifier is based on one or more identifiers associated with the hardware component of the electronic device. Because the hardware component identifier is unique, the two unique hardware identifiers are not identical. As an example, the unique hardware identifier is generated by combining the device's logic board serial number with the device's Ethernet hardware address. The logic board serial number and Ethernet hardware address are combined using concatenation, hashing, encoding, or other data manipulation algorithms. The unique hardware identifier is sent from the client to the server as part of the request to associate the pre-installed application with the user account (630). In other examples where the pre-installed application is selectively adopted, metadata associated with the pre-installed application is further transmitted from the client to the server. The metadata provides details to the server so that the server can identify the selected pre-installed application that the user is trying to apply to the user account. After receiving the unique hardware identifier and optional metadata, the server verifies the credentials by determining 640 whether the pre-installed application is already linked to the user account. The server determines whether the application is already linked by checking the uniqueness table for the unique hardware identifier. Because the uniqueness table stores an entry that contains the unique hardware identifier of the electronic device that has already applied the pre-installed application, the unique hardware identifier that is not found in the table is the one that the electronic device still has -Indicates that the installed application is not associated. If the method 600 allows selective application of a pre-installed application, the determination includes querying a uniqueness table for an entry associated with the unique hardware identifier. If a unique hardware identifier is found, the determination evaluates the entry with the pre-installed application metadata to determine if the selected pre-installed application has been previously adopted.

  If it is determined from searching (ie, querying) the uniqueness table that the application has been previously adopted, an error is again sent to the client (641). The client receives the error and presents a warning to the user that the application has already been adopted (642). FIG. 13 shows an example of the admission warning. Alert 700 informs the user that the pre-installed application has already been assigned to a different user account, so the user cannot assign one or more applications that he wants to associate with his user account. On the other hand, if it is determined from searching the uniqueness table that the application has not been previously applied, the server performs a sanity check and the pre-installed application is set to the original setting of the electronic device, ie the default setting. It is determined whether it is a part (650). In other words, the server determines whether the electronic device is configured with the pre-installed application installed and supplied from the manufacturer. Such a sanity check prevents a user from attempting to copy a pre-installed application that was originally installed on one electronic device to another electronic device and to associate the illegal copy with the user account. The server queries a configuration server that includes the unique hardware identifier and receives the original configuration of the electronic device associated with the unique hardware identifier. The original setting is examined to determine a list of pre-installed applications. This list of pre-applications is compared with the application that the user is trying to adopt to determine whether the application can be adopted. In another example, the unique hardware identifier can be fully evaluated at the distribution center by storing a copy of the database used to query the original configuration at the distribution center. This reduces network traffic to the configuration server.

  If it is determined that the application that the user wants to adopt is not part of the original configuration of the electronic device, an error message is sent to the client (651). Upon receiving the error message, the client presents a warning to the user that the electronic device is not subject to adoption (642). FIG. 14 shows another example of the admission warning. Alert 750 notifies the user that the application cannot be assigned to the user account because the electronic device (named “Mac” herein) is not eligible to associate the pre-installed application with the user account. . In other examples, alert 750 includes a diagram or other sentence provided to inform the user that the electronic device was not originally configured with a pre-installed application. On the other hand, if it is determined that the application that the user wants to adopt is part of the original settings of the electronic device, it is executed if there is a further sanity check. When the server verifies that the pre-installed application is linked to the user account, the server updates the uniqueness table and user account stored on the server (660), and the pre-installed application of the electronic device adopts the application. (Thus not being adopted by another user account). As described above, the preinstalled application being applied is the preinstalled application of the electronic device that is next associated with the user account, so updates and redownloads associated with the application are Downloaded to the associated electronic device. The server sends an authorization message to the client to inform the client that the request is authorized (670). The authorization message informs or informs the client that the pre-installed application is next associated with the user account on the server, since linking the request is evaluated and known to be a true request . The client receives the authorization message and links the pre-installed application with the user account stored on the client (680). In some examples, the client further updates the manifest stored on the electronic device by deleting from the manifest the metadata associated with the pre-installed application that is linked to the user account. Deleting the metadata associated with the pre-installed application simplifies the admission process by minimizing the checks performed to determine if the application is adoptable. The client sends the request to the distribution center or other component of the server to download the application (690).

  The method 600 is further configured to adopt a post-install application (ie, a user-installed application). Post-installation applications include applications that are installed on the user's device after the device is shipped from the manufacturer or purchased by the user, acquired, redeemed, or otherwise obtained. For example, the method 600 does not generate a unique hardware identifier, but generates a unique identifier associated with the application (620). The unique identifier is metadata associated with the application that is used to indicate credentials or proof of purchase of the application. The unique identifier is stored in the application metadata and then retrieved by the client device. Alternatively, the unique identifier is generated based on application metadata. For example, the unique identifier may be a unique receipt of the application or a non-unique receipt, metadata associated with receiving the application, such as the date and / or location where the application was obtained, a unique identifier associated with the client device. And / or from other metadata associated with the application or client device.

  In some examples, the communication protocol depends on whether the unique identifier is associated with a pre-installed application (ie, a manufacturer installed application) or a post-installed application (ie, a user installed application). For example, if the unique identifier received from the client is not part of the original setting of the electronic device because it is associated with the post-installed application, the communication protocol is part of the original setting of the electronic device. (650) is skipped. Instead, the server verifies the credentials, or ownership of the application, by comparing the unique identifier with a database of valid unique identifiers. Thereby, the server can distinguish and discriminate between a legitimate copy and an illegal copy of the application. Once the credentials are verified, the application is adopted as part of the user account. To determine whether the application is pre-installed or post-installed, the server parses a flag or other metadata associated with the unique identifier.

  In yet another example, the communication protocol depends on whether the unique identifier received from the client is based on metadata associated with the client electronic device. For example, the database or table accessed by the server to determine if the application is already linked depends on the unique identifier. The first database is accessed and updated by the server for a unique identifier associated with the client electronic device. The first database is keyed based on the hardware of the electronic device and can be searched. The second database is accessed and updated by the server for a unique identifier that is not associated with the client device. In other words, searching these second databases is based on credentials, or some variation of credentials, because these unique identifiers are based solely on credentials associated with the application.

  FIG. 15 illustrates an exemplary process for a recovery mode on an electronic device. In general, the recovery mode allows an electronic device to resolve an internal fatal error to an application or operating system. In the extreme case of recovering the entire operating system, this approach reformats the storage device and reinstalls the operating system. Depending on the specific implementation of the recovery mode, the operating system being reinstalled will vary. By way of example, a reinstalled operating system is an operating system that was originally installed on an electronic device and then updated manually and / or automatically. As another example, a reinstalled operating system incorporates one or more updates that have been released since the originally installed operating system. In yet another example, the latest operating system available from the manufacturer is reinstalled. In general, the recovery mode only reinstalls the operating system without reinstalling the pre-installed application. This results in the loss of pre-installed applications that are not associated with or linked to the user account. Process 800 solves this problem by retrieving the manifest from the configuration server during the recovery mode.

  Process 800 begins by entering 820 a recovery mode. Entering recovery mode triggers downloading the base operating system from the manufacturer. The base operating system is configured to generate unique hardware (830). The unique hardware identifier is generated using one of the methods described above. Once the unique hardware identifier is generated, the base operating system sends the unique hardware identifier to the configuration server (840). Based on the received unique hardware identifier, the configuration server returns a manifest that includes the applications pre-installed on the electronic device and the version numbers of these applications. The manifest further includes other applications for which the owner of the electronic device has ownership. In some examples, the communication server communicates with the distribution server to determine if the electronic device has already adopted the application. If the unique hardware identifier is found in the distribution center uniqueness table, one or more of the electronic device's pre-installed applications have already been adopted. Thus, the communication server returns an empty manifest or a manifest that does not include a particular pre-installed application that has already been adopted. This minimizes the page purchase request presenting the pre-installed application to the user for admission when the pre-installed application has already been adopted. In another example where the distribution center stores a local copy of the configuration database, the unique hardware identifier is sent to the distribution center rather than the configuration server. By using the unique hardware identifier, the distribution center determines applications that are already associated with pre-installed applications and user accounts.

  The configuration server (or distribution center) returns a manifest based on the version number of the operating system attached to the electronic device and the pre-installed application of the electronic device (850). In another example, the manifest further includes a post-install application for the electronic device that is not linked to the user account (850). When the electronic device installs an application that is not associated with a user account, the manifest stored on the configuration server is periodically updated. This can occur for various reasons, such as a network failure, a server failure, or a user selected option not to associate the application with a user account at this time. The version number of the operating system is transmitted to the operating system server (860). As a result, the original operating system is transmitted to the electronic device. The electronic device receives the original operating system (870) and installs the original operating system as needed. The electronic device then includes a new copy of the original operating system and manifest based on the electronic device's pre-installed application. If the user does not associate the pre-installed application with the user account, he does so by selecting the page purchase link as described above.

  Embodiments within the scope of the present invention further include a tangible computer readable storage medium and / or a computer readable non-transitory storage medium that retains or stores computer-executable instructions or data structures. . Such computer-readable non-transitory storage media are any general purpose computer or any usable media that can be accessed by a special purpose computer including the functional design of any special purpose processor as described above. By way of non-limiting example, such computer-readable non-transitory storage media may be RAM, ROM, EEPROM, CD-ROM, or other optical disk storage device, magnetic disk storage device, or other magnetic storage device, or a computer. It includes any other medium used to hold or store the executable program, data structure, or desired program code means in the form of a processor chip design. If information is transferred or provided to a computer via a network or another communication connection (either hardwired, wireless, or a combination thereof), the computer formally regards the connection as a computer-readable medium. Accordingly, any such connection is formally referred to as a computer readable medium. Combinations of the above should also be included within the scope of computer-readable media.

  For example, computer-executable instructions include instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing devices to perform a certain function or group of functions. The computer-executable instructions further include program modules that are executed by the computer in a stand-alone environment or a network environment. Generally, program modules include routines, programs, components, data structures, objects, functions, etc. that are specific to the design of a dedicated processor that performs a specific task or implements a specific abstract data type. Computer-executable instructions, associated data structures, and program modules represent examples of program code means for performing steps of the methods disclosed herein. A particular sequence of such executable instructions, or associated data structures, represents an example of a corresponding operation that implements the functionality described in such steps.

  Other embodiments of the present invention include personal computers, handheld devices, multiprocessor systems, microprocessor-based electronic equipment for buyers, or programmable electronic equipment for buyers, network PCs, minicomputers, mainframe computers, etc. It will be appreciated by those skilled in the art that many types of computer system configurations are implemented in a network computing environment, including: Embodiments are further implemented in distributed computing environments where tasks are performed by local and remote processing devices (either by hard wire drinks, wireless links, or combinations thereof) linked through a communications network. The In a distributed computing environment, program modules are located in both local and remote memory storage devices.

  The various embodiments described above are provided by way of illustration only and should not be construed to limit the scope of the invention. Various modifications and changes made to the principles described herein may be made without departing from the spirit and scope of the present invention without following the example embodiments and applications illustrated and described herein. Will be readily understood by those skilled in the art.

Claims (20)

Determining whether an application installed on the first client device is eligible for admission, and determining that the application installed on the first client device is configured to be distributed by a server; Verifying with the server,
A verification step for verifying by the server that the application has not been previously adopted,
Automatically searching for a unique identifier that uniquely identifies an individual copy of the installed application from metadata associated with the installed application;
Verifying that the unique identifier is not associated with any user account;
The verification step comprising:
Delivering a notification from the server to the first client device that the installed application is eligible for adoption;
A method comprising the steps of:   The server further comprises the step of adopting the application to a user account, wherein the admission is a benefit related to the application that has been adopted to one or more client devices associated with the user account. The method of claim 1, wherein the user account is configured to allow.   The method of claim 2, wherein the benefits include downloading, redownloading, and updating the application. Registering a second client device with the user account;
Transmitting the adopted application to the second client device;
The method according to claim 2, further comprising:   5. A method according to any one of the preceding claims, wherein the unique identifier is a credential for the individual copy.   6. A method according to any one of claims 2 to 5, wherein the application has been previously installed on one or more client devices associated with the user account.   The method according to claim 1, wherein the method is performed in response to a user request. Notifying the client device of a plurality of applications that can be adopted;
8. The method of any one of claims 1 to 7, further comprising accepting an input to select at least one application of the plurality of applications for adoption.   9. The method of any one of claims 1 to 8, wherein the step of automatically searching for the unique identifier comprises querying a database on the server for the unique identifier. Method.   10. A method as claimed in any preceding claim, wherein adopting a software package further comprises updating a database based on credentials for the software package.   The method according to any one of claims 1 to 9, wherein the unique identifier includes a value derivable from hardware associated with the client device. A processor;
A storage device;
A memory configured to store instructions for controlling the processor;
A system comprising:
Verifying that an application installed on a client device is eligible for adoption by determining that the application installed on the client device is configured to be delivered by a server; ,
Verifying by the server that the application has not been previously adopted,
A sub-step of automatically retrieving a unique identifier that uniquely identifies an individual copy of the installed application from metadata associated with the installed application;
Verifying, comprising verifying that the unique identifier is not associated with any user account;
Delivering a notification from the server to the client device that the installed application is eligible for adoption. The memory further comprises the step of applying the application to a user account by the server, the application being applied to the one or more client devices associated with the user account. Configure the user account to allow benefits related to the application;
The system according to claim 12.   The system of claim 13, wherein the benefits include downloading, redownloading, and updating the application.   15. The memory further comprising instructions for registering another client device with the user account and instructions for sending the adopted application to the other client device. The system according to any one of the above.   16. A system as claimed in any one of claims 12 to 15, wherein the application has been previously installed on one or more client devices associated with the user account.   The memory further comprises instructions for notifying the client device of a plurality of applications that can be adopted and an instruction for accepting an input to select one of the plurality of applications. The system according to any one of 12 to 16. A computer-readable non-transitory recording medium storing instructions to be executed by a computer device, wherein the instructions are executed by the computer device.
Whether the application installed on the client device is eligible for adoption is verified by the server by determining that the application installed on the client device is configured to be distributed by the server. Steps,
A verification step for verifying by the server that the application has not been previously adopted,
Automatically searching for a unique identifier that uniquely identifies an individual copy of the installed application from metadata associated with the installed application;
Verifying that the unique identifier is not associated with any user account;
The verification step comprising:
Causing the computing device to execute a notification from the server to the first client device that the installed application is eligible for adoption.
A computer-readable non-transitory storage medium.   In response to a user request, the step of verifying that the application is installed on a client device, the step of verifying that the application has not been previously applied, and the step of delivering the notification. The computer-readable non-transitory storage medium of claim 18, wherein the non-transitory storage medium is executed.   The server further comprises the step of adopting the application to a user account, wherein the admission is a benefit related to the application that has been adopted to one or more client devices associated with the user account. 20. A computer-readable non-transitory storage medium according to claim 18 or 19, wherein the user account is configured to allow.

Images