Patent Grant
9100396
1. Field of the Invention
The present invention relates to the management of information handling systems. More specifically, embodiments of the invention provide a system, method, and computer-readable medium for perpetuating a system's entitlement to digital assets when the system's components are replaced.
2. Description of the Related Art
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
In recent years, it has become common for manufacturers to offer standardized configurations of these systems bundled with an operating system (OS) and a selection of software applications, digital content, and associated services. Some of these same manufacturers also offer purchasers the ability to order a system custom-configured to their specification. These custom-configured systems, which are often ordered on-line, allow the purchaser to select the OS of their choice along with a selection of software and other digital assets to meet their individual needs. In some cases, the manufacturer may preinstall the OS and the selected digital assets on the system prior to delivery. In addition, the system may be further personalized (e.g., desktop themes and colors, etc.) as a service to the customer.
It is also common for such systems to comprise a unique identifier (ID), often referred to as a service tag, which may be an one, or a combination, of motherboard, processor, or other system component serial numbers or IDs. It is likewise common for digital assets to be bound to these unique IDs as they are being installed on the system for protection against illegal copying. However, approaches are known to spoof these unique IDs, which circumvent the aforementioned copy protection. Furthermore, this association may create issues as the binding between the unique ID and digital assets will become broken if one or more system components fail or are replaced. As a result, the digital assets will typically need to be re-bound (i.e., reassociated) with the new unique ID resulting from the new ID of the replaced component(s).
Current approaches to this issue include binding digital assets to a Trusted Platform Module (TPM), which provides hardware-based security. However, TPMs are generally not implemented on consumer grade systems. Alternatively, the user may contact the vendor of the digital assets, provide the new unique system ID, assuming they are able to access it, and request a new binding between the digital assets and the new ID. As yet another alternative, the user may uninstall the digital assets and then reinstall them. However, this approach may also require contacting the vendor of the digital assets. These processes are typically tedious, error-prone, and can significantly increase the amount of time it takes to restore the functionality of a digital asset after replacement of a system component. In view of the foregoing, there is a need for a more secure unique system ID that both allows the binding of digital assets to be transparently transferred when system components are replaced and does not require the use of a TPM.
A system, method, and computer-readable medium are disclosed for managing a system's entitlement to digital assets when the system's components are replaced. In various embodiments, a digital assets entitlement system is implemented for managing the entitlement of a system to process digital assets. In these and other embodiments, the system comprises a unique system identifier, which in turn comprises the unique identifiers of predetermined system components.
The digital assets entitlement system associates the unique system identifier with the digital assets to generate digital assets entitlement data. The digital assets data and the digital assets entitlement data is then provided to a personalization agent associated with the target system. In turn, the personalization agent processes the digital assets entitlement data and the digital assets data for installation on the target system, thereby entitling the system to process the installed digital assets data.
In one embodiment, the digital assets entitlement is perpetuated by an original unique system identifier when a first unique system component identifier of the original unique system identifier is replaced with a second unique system component identifier. In another embodiment, a second unique system identifier is generated if a first unique system component identifier of a first unique system identifier is changed to a second unique system component identifier. The first unique system identifier is disassociated with the digital assets entitlement data and the second unique system identifier is then associated with the digital assets entitlement data.
The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.
a-b are a simplified block diagram of a unique system identifier that remains the same when one of its associated system component identifiers has been changed;
a-b are a simplified block diagram of a unique system identifier that is changed when one of its associated system component identifiers has been changed;
a-b are a generalized flow chart of the performance of digital asset entitlement operations; and
a-8f, referred to herein as
A system, method, and computer-readable medium are disclosed for perpetuating a system's entitlement to digital assets when the system's components are replaced. For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.
As used herein, a digital asset 246 refers to any digital asset such as a software application, a deliverable or performable service, music, video, software activation key, personalization instructions, files, etc. that are digitally deliverable either wholly or partially. As likewise used herein, a digital assets entitlement refers to the association of a predetermined digital asset 246 with a target system 204. In various embodiments, an entitlement record contains the digital assets entitlement data (e.g., license information, etc.) that allows the digital asset 246 to be processed by a target system 204 identified by a corresponding unique system identifier 206. In these and other embodiments, the entitlement record is processed by the entitlement module 228 and stored in the entitlement data repository 214. Likewise, as used herein, a system 204 may comprise a personal computer, a laptop computer, or a tablet computer operable to establish an on-line session with the digital assets entitlement system 218 over a connection to network 252. The system 204 may also comprise a personal digital assistant (PDA), a mobile telephone, or any other suitable device operable to store a unique system ID 206, perform digital asset entitlement operations with a personalization agent, and likewise operable to establish a connection with network 252.
In this embodiment, digital assets entitlement and system personalization operations are performed by a user, such as a system purchaser 202, in either a physical environment or an on-line environment. As an example, a physical environment may comprise a retailer 240 operating a physical point-of-sale (POS) system 242. As another example, an on-line environment may comprise a system manufacturer 234, after-point-of-sale (APOS) vendor 236, or digital assets vendor 238, that respectively accepts on-line orders for systems or digital assets over a connection to network 252.
If the digital assets entitlement and system personalization operations are performed in an on-line environment, then the system purchaser 202 decides whether to purchase a custom-configured or pre-configured system 204. If the system 204 is to be pre-configured, then it is selected for on-line purchase by the system purchaser 202 and its unique identifier 206 is determined. In one embodiment, the unique system identifier 206 is stored in the Basic Input/Output System (BIOS) or other memory storage device of the pre-configured system 204. However, if the system 204 is to be custom-configured, then it is custom-configured for on-line purchase by the system purchaser 202. Once manufactured by the system manufacturer 234, a unique system identifier is generated as described in greater detail herein.
In various embodiments, the manufacturing integration module 232 coordinates the custom configuration of the system 204 with the digital assets entitlement system 218. Likewise, the system identification and security module 224 coordinates the generation of the unique system identifier 206 and its storage in the repository of system identifier data 216. The system purchaser then selects a digital asset 246 for on-line purchase, followed by selecting personalization options for the pre-configured or custom-configured system. In various embodiments, the personalization module 226 coordinates the selection of personalization options with the digital assets entitlement system 218. As used herein a system personalization option refers to any feature, capability, or function that may be applied to a target system. As an example, a personal computer desktop wallpaper or user interface options (e.g., a “classic” interface) are personalization options.
However, if the digital assets entitlement and system personalization operations are performed in a physical environment, then the system purchaser 202 selects a pre-configured system 204 and physical representations of a digital asset 246 to be purchased. In various embodiments, the digital asset 246 is physically represented as images and text on a card or a package, yet the digital assets themselves are not contained within the card or package. The system purchaser 202 then selects system personalization options for the pre-configured system. In various embodiments, the system personalization options are likewise physically represented as images and text on a card or a package.
The digital assets product identifier (ID) is then scanned with a scanner 244 from its corresponding physical representation, followed by scanning its corresponding digital assets activation key or other entitlement data. In various embodiments, it is not necessary to scan the digital assets activation key or other entitlement data as it is provided by the digital assets entitlement system 218 during digital asset entitlement operations described in greater detail herein. Data related to the previously selected personalization options are then likewise scanned, followed by determining the unique system identifier 206 of the pre-configured system 204. In various embodiments, the digital assets product ID, its associated activation key or entitlement data, the personalization option data, and the unique system identifier are represented by a bar code 248 or other indicia on a card or physical package. In various other embodiments, the digital assets product ID, its associated activation key or entitlement data, the personalization option data, and the unique system identifier is contained in a radio frequency identifier (RFID) 250 tag affixed to the physical representation of the digital asset. Those of skill in the art will realize that many such embodiments are possible and that the foregoing is not intended to limit the spirit, scope, or intent of the invention.
A purchase transaction for the custom-configured or pre-configured system 204 and any associated digital assets 246 and personalization options is then completed. In various embodiments, the processing of the purchase transaction is performed by the sales integration module 230. In these and other embodiments, the financial proceeds of the purchase transaction may be settled between multiple parties. For example, a system manufacturer 234 may receive a portion of the purchase transaction corresponding to the cost of the system 204. One or more digital assets vendors 238 may likewise receive a proportionate share of the purchase transaction corresponding to the digital asset 246 they respectively provide.
Digital asset entitlement operations, as described in greater detail herein, are then performed by the digital assets entitlement system 218 to bind the digital assets 246, the personalization options, and their respective digital assets entitlement data to the unique system identifier 206 of the target system 204. The resulting bound data, including data associated with the digital assets (e.g., installation files, etc.) is then stored in the repository of entitlement data 214 and the purchased system 204 is then delivered to the system purchaser 202. In various embodiments, the entitlement module 228 generates, and then processes, the digital assets entitlement data and the user service and support module 220 coordinates the delivery of the system 204 to the system purchaser 202.
Standard operating system (OS) out-of-the-box-experience (OOBE) or hypervisor boot operations are performed on the system 204, followed by loading a personalization agent 208. In various embodiments, the personalization agent 208 has a unique identifier that is associated with one or more unique system component identifiers. In one embodiment, the unique identifier of the personalization agent is uniquely associated with the current unique system identifier 206 associated with the system 204. In another embodiment, a portion of the personalization agent 208 is delivered to the system 204 in an encrypted form and is then decrypted prior to being loaded on the system 204. In this embodiment, the primary system identifier (e.g., service tag number, serial number, etc.), is used as a decryption key to decrypt the personalization agent 208.
In various other embodiments, primary and secondary system identifiers are stored on the system 204 (e.g., in the BIOS, in Flash memory, on a hard disk, etc.) as well as in the digital assets entitlement system 218. In these and other embodiments, the digital assets entitlement system 218 uses the primary and secondary system identifiers to encrypt a portion of the personalization agent 208 before it is downloaded to the system 204. Once downloaded, the unencrypted portion of the personalization agent 208 uses the primary and secondary system identifiers stored on the system 204 to decrypt the encrypted portion of the personalization agent 208. In one embodiment, the primary and secondary system identifiers are likewise encrypted and are first decrypted before they are used to decrypt the encrypted portion of the personalization agent 208. In another embodiment, the primary and secondary system identifiers are stored in a Trusted Platform Module (TPM). Skilled practitioners of the art will recognize that many such embodiments are possible and the foregoing is not intended to limit the spirit, scope, or intent of the invention.
The personalization agent 208 queries the target system for its unique system identifier 206. In various embodiments, the unique system identifier 206 associated with the system 204 is stored in the target system's BIOS, flash memory, a hard disk, or other memory device. The personalization agent 208 then automatically establishes a connection with the digital assets entitlement system 218 and uses the unique system identifier 206 to authenticate the system 204. The unique system identifier 206 is then used by the personalization agent 208 to determine entitled digital assets and personalization options corresponding to the unique system identifier 206.
Once determined, the corresponding personalization options and digital assets 246, along with their associated digital assets entitlement data, are respectively downloaded to the target system 204 from the repository of digital assets 212 and the repository of entitlement data 214. In one embodiment, the personalization options and digital assets, along with their associated digital assets entitlement data, are downloaded from a single server 210 on the network 252. In another embodiment, the personalization options and digital assets are downloaded from one or more servers 210 on the network 252. In yet another embodiment, the personalization options, digital assets, and associated digital assets entitlement data are respectively downloaded from a plurality of servers 210 on a network 252. As an example, a first digital asset 246 may be provided by the system manufacturer 234 and a second digital asset 246 may be provided by a digital assets vendor 238. Likewise, a plurality of digital assets 246 may be provided by a corresponding plurality of digital assets vendors 238. Skilled practitioners of the art will realize that many such embodiments and examples are possible and the foregoing is not intended to limit the spirit, scope, or intent of the invention.
In various embodiments, the digital assets entitlement system 218 manages the respective location of the personalization options, digital assets, and associated digital assets entitlement data to initiate its provision. Once downloaded, the personalization agent 208 uses the digital assets entitlement data to install the digital assets 246 and personalization options on the system 204.
Thereafter, the system purchaser 202 may decide to perform an after-point-of-sale (APOS) purchase of digital asset 246. As used herein, an APOS purchase of digital assets refers to any purchase of a digital asset 246 made after the initial on-line or physical purchase of the system 204. In various embodiments, the APOS purchase of a digital asset 246 may be performed in a physical, on-line, or enterprise point-of-sale environment. If the APOS purchase is performed in an on-line environment, such as from APOS vendor 236, then the system purchaser 202 selects a digital asset 246 for on-line purchase. The personalization agent 208 then determines the unique system identifier 206 of the system 204. An APOS purchase transaction is then performed for purchase of the selected digital asset 246. However, if the APOS purchase is performed in a physical environment, then the purchaser selects a physical representation of a digital asset 246 to be purchased. The digital assets product identifier (ID) is then scanned from its corresponding physical representation, followed by scanning its corresponding digital assets activation key or other entitlement data.
Digital asset entitlement operations, as described in greater detail herein, are then performed by the digital assets entitlement system 218 to bind the digital asset 246 and their respective digital assets entitlement data associated with the APOS purchase to the unique system identifier 206 of the target system 204. The resulting bound data, including data associated with the digital assets (e.g., installation files, etc.) is then stored, as described in greater detail herein, in the digital assets entitlement system 218. The personalization agent 208, as likewise described in greater detail herein, then automatically establishes a connection with the digital assets entitlement system 218, downloads the purchased digital asset 246 and their associated digital assets entitlement data. Once downloaded, the personalization agent 208 then uses the associated digital assets entitlement data to install the downloaded digital asset 246 on the system 204.
a-b are a simplified block diagram of a unique system identifier that remains the same when one of its associated system component identifiers has been changed in accordance with an embodiment of the invention. As shown in
As described in greater detail herein, once generated, the original unique system identifier 320 is associated, such as through a binding operation, with predetermined digital assets 332 to generate a digital assets entitlement 330. As likewise described in greater detail herein, the digital assets entitlement 330 entitles a target system, which is associated with the original unique system identifier 320, to process the digital assets 332. However, it is not uncommon for system components to be replaced due to failure, erratic performance, becoming outmoded, or for other reasons. It will be appreciated that the entitlement 330 between the original unique system identifier 320 and the digital assets 332 may be compromised as a result of such a replacement. For example, as illustrated in
In various embodiments, extract, transform, and load (ETL) and other database operations are performed to manage the integrity of the relationship between the original unique system identifier 320 and the plurality of unique system component identifiers 302. As an example, the Original Motherboard ID 314 ‘19374WS238017BH’ may remain as a subset of the original unique system identifier 320, even though it may have been deactivated or invalidated as a unique system component identifier 302. However, in these and other embodiments, relational database operations known to those of skill in the art may be applied to maintain the relationship between the original unique system identifier 320, the New Original Motherboard ID 334 ‘56812FR853945PL’, and the unchanged unique system component identifiers 302. Accordingly, the integrity of the entitlement 330 between the original unique system identifier 320 and the digital assets 332 is perpetuated. It will be apparent to skilled practitioners of the art that many such embodiments are possible and the foregoing is not intended to limit the spirit, scope, or intent of the invention.
a-b are a simplified block diagram of a unique system identifier that is changed when one of its associated system component identifiers has been changed in accordance with an embodiment of the invention. As shown in
As described in greater detail herein, once generated, the original unique system identifier 320 is associated, such as through a binding operation, with predetermined digital assets 332 to generate a digital assets entitlement 330. As likewise described in greater detail herein, the digital assets entitlement 330 entitles a target system, which is associated with the original unique system identifier 320, to process the digital assets 332. However, it is not uncommon for system components to be replaced due to failure, erratic performance, becoming outmoded, or for other reasons. It will be appreciated that the entitlement 330 between the original unique system identifier 320 and the digital assets 332 may be compromised as a result of such a replacement. For example, as illustrated in
In various embodiments, a first set of operations are performed to remove the entitlement 330 between the original unique system identifier 320 and digital assets 332. A second set of operations are then performed to associate the new unique system identifier 420 with the digital assets 332 to generate a new entitlement 430. In these and other embodiments, the original unique system identifier 320 is then invalidated. Accordingly, the integrity of the original entitlement 330 between the original unique system identifier 320 and the digital assets 332 is perpetuated by the new entitlement 430 between the new unique system identifier 420 and the digital assets 332. Skilled practitioners of the art will recognize that many such embodiments are possible and the foregoing is not intended to limit the spirit, scope, or intent of the invention.
An encryption operation 524 is then performed on the source unique system identifier 520 to generate an original encrypted unique system identifier 528. In various embodiments, the encryption operation may comprise the use of a private key, a public key, key pairs, or any combination of keys and cryptographic operations such as implemented in a public key infrastructure (PKI). As an example, the original encrypted unique system identifier 528 may be generated using a private key associated with the manufacturer of the system and a public key associated with the system itself. In one embodiment, the Timestamp Date 510 ‘111909’ and the Timestamp Time 512 ‘14:27:26:34’ are likewise used to generate the encrypted unique system identifier 528. Skilled practitioners of the art will be familiar with such cryptographic operations and recognize that the use of the Timestamp Date 510 ‘111909’ and the Timestamp Time 512 ‘14:27:26:34’ reduces the possibility of a replay attack to compromise the cryptographic integrity of the unique system identifier 528. Those of skill in the art will likewise realize that many such embodiments are possible and that the foregoing is not intended to limit the spirit, scope, or intent of the invention.
As described in greater detail herein, once generated, the original encrypted unique system identifier 528 is associated, such as through a binding operation, with predetermined digital assets 332 to generate a digital assets entitlement 530. As likewise described in greater detail herein, the digital assets entitlement 530 entitles a target system, which is associated with the original encrypted unique system identifier 528, to process the digital assets 332.
In various embodiments, the unique system component identifier of the replacement system component is unknown until it is replaced in the target system. In these and other embodiments, the system component is replaced in the target system, the target system is then initiated (e.g., booted), and an inventory of unique system component identifiers is performed. In one embodiment, one or more unique system component identifiers, such as a serial number or service tag, are visible and may be visually inventoried. In another embodiment, one or more unique system component identifiers, such as a motherboard, processor, or hard drive serial number, are not visible and may be automatically inventoried.
As shown in
An encryption operation 652 is then performed on the new source unique system identifier 650 to generate a new encrypted unique system identifier 628. As an example, the encryption operation may be performed using a private key associated with the target system and a public key associated with the provider of the replacement system component. The new encrypted unique system identifier 628 is then communicated to a digital assets entitlement system, which in turn performs a decryption operation 626 to generate a decrypted unique system identifier 622.
As likewise shown in
In various other embodiments, the provider of the replacement system component is able to determine its associated unique system component identifier. In one embodiment, the unique system component identifier is known in advance. In another embodiment, the unique system component identifier may be one of a pool of, or a range of, possible unique system component identifiers set aside for replacement purposes. As described in greater detail herein, a new source unique identifier is generated, using the unique system component identifier of the component to be replaced. Once the new source unique identifier is generated the unique system component identifier of the replaced system component is invalidated. In these and other embodiments, the system component is replaced in the target system, the target system is then initiated (e.g., booted), and an inventory of unique system component identifiers is performed. In one embodiment, one or more unique system component identifiers, such as a serial number or service tag, are visible and may be visually inventoried. In another embodiment, one or more unique system component identifiers, such as a motherboard, processor, or hard drive serial number, are not visible and may be automatically inventoried.
As shown in
Comparison operations 654 are then performed between the new source unique system identifier and the decrypted unique system identifier 622. If the comparison operations 654 are successful, then a first set of operations are performed to remove the entitlement between the original encrypted unique system identifier and digital assets 332. A second set of operations are then performed to associate the new encrypted unique system identifier 628 with the digital assets 332 to generate a new entitlement 630. Accordingly, the integrity of the original entitlement between the original encrypted unique system identifier and the digital assets 332 is perpetuated by the new entitlement 630 between the new encrypted unique system identifier 628 and the digital assets 332. Skilled practitioners of the art will recognize that many such embodiments are possible and the foregoing is not intended to limit the spirit, scope, or intent of the invention.
a-b are a generalized flow chart of the performance of digital asset entitlement operations in an embodiment of the invention, In this embodiment, digital asset entitlement operations are started in step 702, followed by the selection of a target system in step 704 for digital assets entitlement. The unique system identifier of the target system, as described in greater detail herein, is determined in step 706, followed by a determination being made in step 708 whether a device record has been established for the target system. If not, then the device record is generated in step 710. As used herein, a device record refers to a data record containing data related to a system which will receive an entitlement to process associated digital assets. In various embodiments, the unique system identifier of the target system is stored in the device record. In various embodiments, other records may be associated with the device record to further describe the system, such as its model, type, make, internal identifiers, etc.
Once the device record has been generated, or if it is determined in step 708 that it has already been established, then a determination is made in step 712 whether an account record has been established for a user. If not, then the account record is generated for the user in step 714. As used herein, an account record refers to a data record containing data related to the association of multiple devices or systems to one or more entities. In various embodiments, the entity may be a single individual or a group of individuals. As an example, the entity may be a household with multiple PCs, a small business with several employees, a large corporation with many employees, etc. Other records may be attached to the account to further describe the account holder, payment information related to the account, etc. Accounts may further be broken down or organized into sub-accounts as needed, such as to describe departments within an enterprise). In various embodiments, a user may be associated with a single device or system or multiple devices or systems in the account record. Conversely, a group of users may be associated with a single device or system or multiple devices in the account record. Further more groups of individual users may likewise be associated with groups of individual devices or systems. Those of skill in the art will recognize that many such associations are possible and the foregoing is not intended to limit the spirit, scope, or intent of the invention. Once the account record has been generated, or if it is determined in step 712 that it has already been established, then a determination is made in step 716 whether the account record is associated with the target system. If not, then the account record is associated with the target system in step 718.
Once the account record has been associated with the target system, or if it is determined in step 716 that it has already been associated, then a target list of digital assets is presented in step 720 for entitlement. A determination is then made in step 722 whether to generate an entitlement for a digital asset. If not, then a determination is made in step 732 whether to continue digital asset entitlement operations. If so, then the process is continued, proceeding with step 704. Otherwise digital asset entitlement operations are ended in step 734. However, if it is determined in step 722 to generate an entitlement for a digital asset, then a target digital asset is selected in step 724. A digital assets entitlement is then generated in step 726 by performing operations to associate the selected digital asset's corresponding license record with the aforementioned device record, account record, and other predetermined records. The resulting digital assets entitlement association is then added to the entitlement record in step 728. A determination is then made in step 730 whether to generate another digital assets entitlement. If so, the process is continued, proceeding with step 724. Otherwise, a determination is made in step 732 whether to continue digital asset entitlement operations. If so, then the process is continued, proceeding with step 704. Otherwise digital asset entitlement operations are ended in step 734.
The new target system is then delivered to the purchaser or user in step 818, followed by a determination being made in step 820 whether an operating system (OS) is present on the new target system. If not, then standard OS out-of-the-box-experience (OOBE) or hypervisor boot operations are performed on the new target system in step 822. Otherwise, or after the boot operations are performed in step 822, a personalization agent is loaded on the new target system in step 824.
A determination is then made in step 828 whether a personalization agent is loaded on the target system. If not, the personalization agent is loaded in on the target system in step 830. In various embodiments, the personalization agent may comprise a unique identifier that is associated with one or more unique system component identifiers. In one embodiment, the unique identifier of the personalization agent is uniquely associated with the stored unique system identifier associated with the target system. In another embodiment, a portion of the personalization agent is delivered to the target system in an encrypted form and is then decrypted prior to being loaded on the target system. In this embodiment, the primary system identifier (e.g., service tag number, serial number, etc.), is used as a decryption key to decrypt the personalization agent.
In various other embodiments, primary and secondary system identifiers are stored on the target system (e.g., in the BIOS, in Flash memory, on a hard disk, etc.) as well as in the digital assets entitlement system. In these and other embodiments, the digital assets entitlement system uses the primary and secondary system identifiers to encrypt a portion of the personalization agent before it is downloaded to the target system. Once downloaded, the unencrypted portion of the personalization agent uses the primary and secondary system identifiers stored on the target system to decrypt the encrypted portion of the personalization agent. In one embodiment, the primary and secondary system identifiers are likewise encrypted and are first decrypted before they are used to decrypt the encrypted portion of the personalization agent. In another embodiment, the primary or secondary system identifiers are stored in a Trusted Platform Module (TPM). Skilled practitioners of the art will recognize that many such embodiments are possible and the foregoing is not intended to limit the spirit, scope, or intent of the invention.
A determination is then made in step 832 whether the stored unique system identifier associated with the target system is stored in the target system's BIOS or other memory storage device. If not, then the primary system identifier (e.g., service tag number, serial number, etc.) of the target system is determined in step 834. Then, in step 836, the personalization agent inventories unique identifiers corresponding to selected system components contained in the target system. The personalization agent then generates a unique system identifier (the “current unique system identifier”) in step 838 from the primary system identifier and the inventoried unique system component identifiers. In various embodiments, the personalization agent uses a time variance value, such as a time and date stamp, in addition to the primary system identifier and the inventoried unique system component identifiers to generate the current unique system identifier. In various other embodiments, the personalization agent uses a system type identifier in addition to the primary system identifier and the inventoried unique system component identifiers to generate the current unique system identifier. As an example, a system type identifier, may comprise a brand name or system product family, such as “Dell Latitude,” “Dell Inspiron,” “Dell PowerEdge,” etc.
The personalization agent then automatically establishes a connection with the digital assets entitlement system in step 840 and uploads the current unique system identifier. The current unique system identifier is first stored in the digital assets entitlement system in step 842 and then in the BIOS or other memory storage device of the target system in step 844. Then, or after the personalization agent has been loaded on the new target system in step 824, the personalization agent reads the BIOS or other memory storage device of the target system in step 846 to determine its stored or current unique system identifier.
The personalization agent then automatically establishes a connection with the digital assets entitlement system in step 848 and uses the stored or current unique system identifier to authenticate the system. Then, in step 850, the stored or current unique system identifier is used by the digital asset entitlement system to determine entitled digital assets and personalization options corresponding to the stored or current unique system identifier. Once determined, the corresponding personalization options and digital assets, along with their associated digital assets entitlement data, is downloaded in step 851 to the target system. Once downloaded, the personalization agent uses the digital assets entitlement data in step 852 to install the digital assets and personalization options on the target system. The personalization agent then performs inventory operations in step 853 to inventory installed digital assets and personalization option setting data on the target system. Then, in step 854, the personalization agent uses the unique system identifier to compare the inventoried digital assets and personalization settings to the corresponding digital assets entitlement data stored on the digital assets entitlement system.
A determination is then made in step 855 whether all of the inventoried digital assets and personalization options installed on the target system have corresponding digital assets entitlement data stored in the digital assets entitlement system. As an example, the user may have previously installed digital assets and personalization options prior to the download and installation of entitled digital assets and personalization options respectively performed in steps 851 and 852. If it is determined in step 855 that not all of the digital assets and personalization options installed on the target system have corresponding digital assets entitlement data stored in the digital assets entitlement system, then those that do not are determined in step 856. The user is then prompted in step 857 to provide digital assets entitlement data (e.g., license keys, user ID, passwords, etc.) associated with the digital assets and personalization options not currently in the digital assets entitlement system. The requested digital assets entitlement data, and associated digital assets (e.g., installation files), are then provided by the user in step 858, and uploaded by the personalization agent in step 859, to the digital assets entitlement system. The digital assets entitlement system then uses the uploaded data in step 860 to generate digital assets entitlement associations with the stored or current unique system identifier as described in greater detail herein.
System service requests are then received in step 861, followed by a determination made in step 862 whether a request has been received to exchange a system component. If not, then a determination is made in step 897 whether to continue unique system identifier management operations. If so, then the process is continued, proceeding with step 861. Otherwise, unique system identifier management operations are ended in step 898. However, if it is determined in step 862 that a request has been received to exchange a system component, then the stored unique system identifier of the system to be serviced is determined in step 863. The stored unique system identifier is then used in step 864 to determine the unique system component identifiers corresponding to system components currently contained in the system corresponding to the stored unique system identifier.
A determination made in step 865 whether the unique system component identifier of the replacement component is known. If so, then in step 866, the digital assets entitlement system replaces the unique system component identifier of the component to be replaced with the unique system component identifier of the replacement component in the stored unique system identifier. The stored unique system identifier is then marked as changed in step 867. Then, or if it is determined in step 865 that the unique identifier of the replacement component is not known, the requested exchange of the system component is performed in step 868. Boot operations are performed on the target system in step 869 and the primary system identifier (e.g., service tag number, serial number, etc.) is determined in step 870.
A personalization agent associated with the target system then inventories the unique identifiers corresponding to selected system components (e.g., motherboard, processor, hard drive, etc.) installed on the target system in step 871. The personalization agent then generates a current unique system identifier from the primary system identifier and the inventoried unique system component identifiers corresponding to selected system components in step 875. A determination is then made in step 877 whether to encrypt the current unique system identifier prior to uploading it to the digital assets entitlement system. If not, then the personalization agent automatically establishes a connection with the digital assets entitlement system in step 878 and uploads the unencrypted current unique system identifier. Otherwise, encryption operations are performed in step 879 to encrypt the current unique system identifier. The personalization agent then automatically establishes a connection with the digital assets entitlement system in step 880 and uploads the encrypted current unique system identifier. The digital assets entitlement system then performs decryption operations in step 881 to generate a decrypted current unique system identifier. Once it is decrypted, the digital assets entitlement system performs parsing operations in step 882 on the current unique system identifier to determine its associated unique system component identifiers.
The digital assets entitlement system then performs comparison operations in step 883 between the stored and current unique system identifiers. A determination is then made in step 884 whether the stored unique system identifier is marked as having been changed in step 867. If so, then a determination is made in step 885 whether the stored and current unique system identifiers match. If not, or if it is determined in step 884 that the stored unique system identifier is not marked as changed, then the unique identifiers corresponding to selected system components in the stored and current unique system identifiers are compared in step 886 to identify replaced system components. The unique identifiers of replaced system components are then replaced in the stored unique system identifier with the unique identifiers of the replacement system components in step 887. Then the unique identifiers of the replaced system components are invalidated in step 888.
Then, in step 891, the old stored unique system identifier is replaced with the current unique system identifier to generate a new stored unique identifier. The digital assets entitlement system then removes any digital assets entitlement associations from the old stored unique system identifier in step 894 and then reestablishes the digital assets entitlement associations with the new stored system identifier. The digital asset entitlement system then invalidates the old stored unique system identifier in step 896. A determination is then made in step 897 whether to continue unique system identifier management operations. If so, then the process is continued, proceeding with step 861. Otherwise, unique system identifier management operations are ended in step 898.
The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.
For example, the above-discussed embodiments include software modules that perform certain tasks. The software modules discussed herein may include script, batch, or other executable files. The software modules may be stored on a machine-readable or computer-readable storage medium such as a disk drive. Storage devices used for storing software modules in accordance with an embodiment of the invention may be magnetic floppy disks, hard disks, or optical discs such as CD-ROMs or CD-Rs, for example. A storage device used for storing firmware or hardware modules in accordance with an embodiment of the invention may also include a semiconductor-based memory, which may be permanently, removably or remotely coupled to a microprocessor/memory system. Thus, the modules may be stored within a computer system memory to configure the computer system to perform the functions of the module. Other new and various types of computer-readable storage media may be used to store the modules discussed herein. Additionally, those skilled in the art will recognize that the separation of functionality into modules is for illustrative purposes. Alternative embodiments may merge the functionality of multiple modules into a single module or may impose an alternate decomposition of functionality of modules. For example, a software module for calling sub-modules may be decomposed so that each sub-module performs its function and passes control directly to another sub-module.
Consequently, the invention is intended to be limited only by the spirit and scope of the appended claims, giving full cognizance to equivalents in all respects.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5442541 | Hube et al. | Aug 1995 | A |
| 5490216 | Richardson, III | Feb 1996 | A |
| 5502831 | Grube et al. | Mar 1996 | A |
| 5659614 | Bailey, III | Aug 1997 | A |
| 5715314 | Payne et al. | Feb 1998 | A |
| 5745568 | O'Connor et al. | Apr 1998 | A |
| 5864664 | Capps, Jr. et al. | Jan 1999 | A |
| 5892900 | Ginter et al. | Apr 1999 | A |
| 5948078 | Joffe | Sep 1999 | A |
| 5956505 | Manduley | Sep 1999 | A |
| 6032859 | Muehlberger et al. | Mar 2000 | A |
| 6080207 | Kroening et al. | Jun 2000 | A |
| 6170059 | Pruett et al. | Jan 2001 | B1 |
| 6209089 | Selitrennikoff et al. | Mar 2001 | B1 |
| 6243468 | Pearce et al. | Jun 2001 | B1 |
| 6292941 | Jollands | Sep 2001 | B1 |
| 6301612 | Selitrennikoff et al. | Oct 2001 | B1 |
| 6321262 | Springer | Nov 2001 | B1 |
| 6324525 | Kramer et al. | Nov 2001 | B1 |
| 6389403 | Dorak, Jr. | May 2002 | B1 |
| 6425126 | Branson et al. | Jul 2002 | B1 |
| 6502205 | Yanai et al. | Dec 2002 | B1 |
| 6647532 | Boede et al. | Nov 2003 | B1 |
| 6694384 | Moeller et al. | Feb 2004 | B1 |
| 6721881 | Bian et al. | Apr 2004 | B1 |
| 6829704 | Zhang et al. | Dec 2004 | B2 |
| 6865655 | Andersen | Mar 2005 | B1 |
| 6931558 | Jeffe et al. | Aug 2005 | B1 |
| 7047411 | DeMello et al. | May 2006 | B1 |
| 7093032 | Minogue et al. | Aug 2006 | B2 |
| 7120593 | Fry et al. | Oct 2006 | B1 |
| 7278131 | Gunyakti et al. | Oct 2007 | B2 |
| 7290149 | Alabraba et al. | Oct 2007 | B2 |
| 7330997 | Odom | Feb 2008 | B1 |
| 7352999 | Miettinen | Apr 2008 | B2 |
| 7412534 | Tsang et al. | Aug 2008 | B2 |
| 7415439 | Kontio et al. | Aug 2008 | B2 |
| 7417546 | Llorca et al. | Aug 2008 | B2 |
| 7428413 | Fink | Sep 2008 | B2 |
| 7444436 | Wille | Oct 2008 | B2 |
| 7483860 | Cronce et al. | Jan 2009 | B2 |
| 7496739 | Raghavan et al. | Feb 2009 | B1 |
| 7503072 | Hughes et al. | Mar 2009 | B2 |
| 7506382 | Padole et al. | Mar 2009 | B2 |
| 7516104 | Scardino | Apr 2009 | B1 |
| 7519172 | Bruening et al. | Apr 2009 | B2 |
| 7523072 | Stefik et al. | Apr 2009 | B2 |
| 7526451 | Park et al. | Apr 2009 | B2 |
| 7546545 | Garbow et al. | Jun 2009 | B2 |
| 7555447 | Chinnappan et al. | Jun 2009 | B2 |
| 7565325 | Lenard et al. | Jul 2009 | B2 |
| 7593898 | Tsuei et al. | Sep 2009 | B1 |
| 7594275 | Zhu et al. | Sep 2009 | B2 |
| 7761921 | Gannon et al. | Jul 2010 | B2 |
| 7783737 | Fujino et al. | Aug 2010 | B2 |
| 7809945 | Kakii | Oct 2010 | B2 |
| 7925973 | Allaire et al. | Apr 2011 | B2 |
| 7971199 | Chen | Jun 2011 | B1 |
| 8065303 | Probst et al. | Nov 2011 | B2 |
| 8074287 | Barde et al. | Dec 2011 | B2 |
| 8126814 | Yellai et al. | Feb 2012 | B2 |
| 8219769 | Wilk | Jul 2012 | B1 |
| 8229858 | Mazza et al. | Jul 2012 | B1 |
| 8261258 | Jianu et al. | Sep 2012 | B1 |
| 8341455 | Maki et al. | Dec 2012 | B2 |
| 8452731 | Preslan et al. | May 2013 | B2 |
| 8468139 | O'Connor et al. | Jun 2013 | B1 |
| 8510226 | Coley et al. | Aug 2013 | B2 |
| 8533156 | Ryder | Sep 2013 | B2 |
| 8700533 | Levin et al. | Apr 2014 | B2 |
| 20010044782 | Hughes et al. | Nov 2001 | A1 |
| 20020046232 | Adams et al. | Apr 2002 | A1 |
| 20020059270 | Schlabach et al. | May 2002 | A1 |
| 20020076204 | Nakano et al. | Jun 2002 | A1 |
| 20020077986 | Kobata et al. | Jun 2002 | A1 |
| 20020088855 | Hodes | Jul 2002 | A1 |
| 20020091456 | O'Connor | Jul 2002 | A1 |
| 20030028439 | Cox | Feb 2003 | A1 |
| 20030028451 | Ananian | Feb 2003 | A1 |
| 20030033205 | Nowers et al. | Feb 2003 | A1 |
| 20030060157 | Henrick | Mar 2003 | A1 |
| 20030088571 | Ekkel | May 2003 | A1 |
| 20030110126 | Dunkeld et al. | Jun 2003 | A1 |
| 20030120928 | Cato et al. | Jun 2003 | A1 |
| 20040003039 | Humphrey et al. | Jan 2004 | A1 |
| 20040022227 | Lynch et al. | Feb 2004 | A1 |
| 20040044901 | Serkowski et al. | Mar 2004 | A1 |
| 20040059938 | Hughes et al. | Mar 2004 | A1 |
| 20040093273 | Laurent et al. | May 2004 | A1 |
| 20040128551 | Walker et al. | Jul 2004 | A1 |
| 20040133792 | Dublish et al. | Jul 2004 | A1 |
| 20040143746 | Ligeti et al. | Jul 2004 | A1 |
| 20040250066 | DiLuoffo et al. | Dec 2004 | A1 |
| 20040268267 | Moravcsik | Dec 2004 | A1 |
| 20050027657 | Leontiev et al. | Feb 2005 | A1 |
| 20050060388 | Tatsumi et al. | Mar 2005 | A1 |
| 20050229047 | Hanes et al. | Oct 2005 | A1 |
| 20050262573 | Bo et al. | Nov 2005 | A1 |
| 20050268115 | Barde et al. | Dec 2005 | A1 |
| 20060062426 | Levy et al. | Mar 2006 | A1 |
| 20060161635 | Lamkin et al. | Jul 2006 | A1 |
| 20060212649 | Roberts | Sep 2006 | A1 |
| 20060229904 | Hunter et al. | Oct 2006 | A1 |
| 20060276174 | Katz et al. | Dec 2006 | A1 |
| 20070124349 | Taylor | May 2007 | A1 |
| 20070130233 | Christensen | Jun 2007 | A1 |
| 20070157196 | Goicea et al. | Jul 2007 | A1 |
| 20070174621 | Ducharme | Jul 2007 | A1 |
| 20070233580 | Pike et al. | Oct 2007 | A1 |
| 20070255758 | Zheng et al. | Nov 2007 | A1 |
| 20070294566 | Solyanik | Dec 2007 | A1 |
| 20080005033 | Clark et al. | Jan 2008 | A1 |
| 20080109446 | Wang | May 2008 | A1 |
| 20080172583 | Mahajan et al. | Jul 2008 | A1 |
| 20080195871 | Peinado et al. | Aug 2008 | A1 |
| 20080208933 | Lyon | Aug 2008 | A1 |
| 20080215633 | Dunkeld et al. | Sep 2008 | A1 |
| 20080234047 | Nguyen | Sep 2008 | A1 |
| 20090063350 | Briggs et al. | Mar 2009 | A1 |
| 20090083843 | Wilkinson et al. | Mar 2009 | A1 |
| 20090089340 | Ohr et al. | Apr 2009 | A1 |
| 20090125393 | Hwang et al. | May 2009 | A1 |
| 20090164470 | Savage et al. | Jun 2009 | A1 |
| 20090187491 | Bull et al. | Jul 2009 | A1 |
| 20090193102 | Trujillo | Jul 2009 | A1 |
| 20090217352 | Shen et al. | Aug 2009 | A1 |
| 20090228368 | Brown | Sep 2009 | A1 |
| 20090228488 | Brand et al. | Sep 2009 | A1 |
| 20090234892 | Anglin et al. | Sep 2009 | A1 |
| 20090248883 | Suryanarayana et al. | Oct 2009 | A1 |
| 20090265545 | Satoh et al. | Oct 2009 | A1 |
| 20090300673 | Bachet et al. | Dec 2009 | A1 |
| 20090300719 | Ferris | Dec 2009 | A1 |
| 20100106687 | Marcy et al. | Apr 2010 | A1 |
| 20100106691 | Preslan et al. | Apr 2010 | A1 |
| 20100122030 | Peters et al. | May 2010 | A1 |
| 20100125903 | Devarajan et al. | May 2010 | A1 |
| 20100146425 | Lance et al. | Jun 2010 | A1 |
| 20100174918 | Hoffman et al. | Jul 2010 | A1 |
| 20100235921 | Foster | Sep 2010 | A1 |
| 20100257142 | Murphy et al. | Oct 2010 | A1 |
| 20100257185 | Dvir et al. | Oct 2010 | A1 |
| 20100257346 | Sosnosky et al. | Oct 2010 | A1 |
| 20100257403 | Virk et al. | Oct 2010 | A1 |
| 20100306227 | Fleming et al. | Dec 2010 | A1 |
| 20100306267 | Zamkoff et al. | Dec 2010 | A1 |
| 20100319072 | Abzarian et al. | Dec 2010 | A1 |
| 20100325735 | Etchegoyen | Dec 2010 | A1 |
| 20110016466 | Liu et al. | Jan 2011 | A1 |
| 20110022812 | van der Linden et al. | Jan 2011 | A1 |
| 20110072291 | Murase | Mar 2011 | A1 |
| 20110099200 | Blount et al. | Apr 2011 | A1 |
| 20110173405 | Grabarnik et al. | Jul 2011 | A1 |
| 20110184998 | Palahnuk et al. | Jul 2011 | A1 |
| 20110246766 | Orsini et al. | Oct 2011 | A1 |
| 20140059236 | Lo | Feb 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2445303 | Jul 2008 | GB |
| Entry |
|---|
| Yu et al., “An adaptive approach to hardware alteration for digital rights management” [Online], 2004 [Retrieved: Ar. 28, 2014] Proceedings of the 5th international conference on Information Security Applications (WISA'04), Springer-Verlag, pp. 238-250 [Retreived from: http://link.springer.com/content/pdf/10.1007%2F978-3-540-31815-6—20.pdf ]. |
| Hill, Keith, “A Perspective: The Role of Identifiers in Managing and Protecting Intellectual Property in the Digital Age” [Online], Jul. 1999 [Retrieved on: Apr. 28, 2014], Proceedings of the IEEE (vol. 87, Issue: 7), pp. 1228-1238, [Retrieved from: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=771074 ]. |
| Laplink, Laplink Offers Licensing for Windows XP to Windows 7 Upgrade Solution, Oct. 28, 2009. |
| Backup P2P Secured peer to peer backup, http://www.ohloh.net/p/p2pbackupsmile, printed Jun. 18, 2010. |
| Landers et al., PeerStore: Better Performance by Relaxing in Peer-to-Peer Backup, Fakultät Für Informatik , Technische Universität München, 2004 http://www.computer.org/portal/web/csdl/doi/10.1109/PTP.2004.1334933. |
| Peer-to-Peer Viral Backup: Cucku 2.0 Definitely Scores Points for Imagination, http://www.fileslinger.com/2009/05/peer-to-peer-viral-backup-cucku-20-definitely-scores-points-forimagination, printed Jun. 18, 2010. |
| T. Bonkenburg et al, LifeBoat—An Autonomic Backup and Restore Solution, http://www.usenix.org/event/lisa04/tech/full—papers/bonkenburg/bonkenburg.pdf, 2004 LISA XVIII—Nov. 14-19, 2004—Atlanta, GA. |
| M. Vrable, Cumulus: Filesystem Backup to the Cloud, http://cseweb.ucsd.edu/˜voelker/pubs/cumulus-fast09.pdf, Feb. 26, 2009. |
| L. Mearian, Start-up unveils hybrid cloud/on-site backup service, http://www.itworld.com/storage/64972/start-unveils-hybrid-cloudon-site-backup-service, Mar. 24, 2009. |
| Storage-Switzerland.com, Hybrid Cloud Backup for the SMB, http://www.storage-switzerland.com/Articles/Entries/2009/4/24—Hybrid—Cloud—Backup—for—the—SMB.html, Apr. 24, 2009. |
| M. Staimer, Asigra, Why Cloud Backup/Recovery (Private, Public, or Hybrid) Will be Your Data Protection, http://www.docstoc.com/docs/16851799/Why-Cloud-Backup-Recovery-(Private--Public--or-Hybrid)-WILL-be, printed Jun. 18, 2010. |
| CISCO License Manager 2.2, http://www.cisco.com/en/US/products/ps7138/index.html, printed Jun. 15, 2010. |
| Michigan Retailers Association, Member Services, Electronic Gift Card Processing FAQ, http://www.retailers.com/memberservices/giftcardsfaq.html, printed Apr. 19, 2010. |
| Proquest, Sprint and MercuryMD Team up to Offer Healthcare Providers One-Stop Shopping Opportunity for Mobility Solutions, PR Newswire, New York, Apr. 27, 2004. |
| Yu et al., An adaptive approach to hardware alteration for digital rights management [Online], 2004 [Retrieved: Ar. 28, 2014] Proceedings of the 5th international conference on Information Security Applications (WISA'04), Springer-Verlag, pp. 238-250, [Retrieved from: http://link.springer.com/content/pdf/1 0.1 007%2F978-3-540-31815-6—20.pdf]. |
| Hill, Keith, “A Perspective: The Role of Identifiers in Managing and Protecting Intellectual Property in the Digital Age” [Online], v Jul. 1999 [Retrieved on: Apr. 28, 2014], Proceedings of the IEEE (vol. 87, Issue: 7), pp. 1228-1238, [Retrieved from: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber= 771074]. |
| Number | Date | Country | |
|---|---|---|---|
| 20110191863 A1 | Aug 2011 | US |
