TW200834440A - Method and system for allowing content protected by a first DRM system to be accessed by a second DRM system - Google Patents

Abstract

A method, system, and computer-readable media storing operational instructions for allowing content protected by a first DRM system to be accessed by a second DRM system are disclosed. In one embodiment, a request is received from a host application for a license for content protected by a first DRM system, the first DRM system being different from the host application's DRM system. A license supported by the host application's DRM system is then generated from a license supported by the first DRM system. In another embodiment, a request is received to store content protected by a first DRM system. In response to the request, a portable license for the content is generated from a license supported by the first DRM system. Alternatively or additionally, a portable file format for the content is generated from a file format supported by the first DRM system. The request can come from a first computing platform, and the portable license and/or file format can be generated by a second computing platform. Other embodiments are disclosed, and each of the embodiments can be used alone or together in combination.

Description

200834440 IX. Description of the invention: [Technical field to which the invention pertains] A Digital Rights Management ("DRM" system is used to provide or restrict access to content in accordance with a set of permissions normally stored in a license. Digital Rights Management, Differences in the first place (such as 'differences in the file format and/or the license format') prevent applications that are operated by the type-type digital rights management system from accessing content protected by different types of digital rights management systems. Consider, for example, an application that uses a digital rights management system that specifies a file format with a header that contains the beta that is required to allow the application to access the content. The right application attempts to access the recipient. If the content protected by the different digit rights management system of the header is not specified in its file format, the application will not find the required information and will not be able to access the content. [Invention] The present invention is applied for. The scope of patents is defined, and any intrinsic to this section should not be considered as a limitation of these applications. The specific embodiment provides a computer readable medium that allows content protected by the first digital rights management system to be accessed by the second digital rights management system, the first accessed method, system, and storage operation instructions. In an embodiment, a request for permission of content protected by the first digital rights management system is received from a host application, the digital rights authority system being different from the digital rights management system of the host application. And then, from a license supported by the first digital rights management system, a license supported by the digital rights management system of the host application is generated. In the specific embodiment, receiving a request to store the recipient 126727.doc 200834440 Content supported by a digital rights management system. In response to a request, a license is granted to the content from a license supported by the first digital rights management system. Alternatively or additionally, A file format supported by the first digital rights management system generates a portable file format for the content. The request can come A first computing platform, and the portable license and/or file format can be generated by a second computing platform. Other specific embodiments are disclosed, and each of the specific embodiments can be used alone or in combination. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The specific embodiments described below generally relate to allowing different types of digital rights to be protected by a type of digital rights management (',drm") system. The application of the management system is used. The "content" index media used in this document may include, but is not limited to, audio files, video files (with or without audio), games, #, maps, f files, or software programs. . A digital rights management system controls access to content. As used herein, "access" is any action taken with respect to content. Various types of "access" examples include, but are not limited to, play, display, print, copy, and execute. A digital rights management system is used to provide or restrict access to content in accordance with a set of permissions that are typically stored in a license associated with the content. (Allowly, "allows," to permit or bind ten licenses (which may also be referred to herein as "materials" or "content licenses") to store permission for access to content - Entity. For example, 'The license can limit the number of times the content can be accessed or set an effective date and time for such access. A license can also include 126727.doc 200834440 contains information on how to decrypt encrypted content (eg Key.) A license can be stored in any suitable location with or associated with its associated content. For example, in one embodiment, the license and the content are stored together in a portable memory device. In another embodiment, the content is stored in a host or network (or in a portable memory device) and stored in a portable memory device (or in In the network), therefore, it is not necessary to store the content and the license in the same device. ^The difference in the rights management system can prevent the use of the type-type digital rights government system to operate (four) access Content protected by different types of digital rights management systems. An application running under a certain type of digital rights management system may expect to be at some location (for example, in content or in a license) If the application cannot find the information at the location, the application may not be able to access the content. A difference between the digital rights management systems may be a file format. The content is typically stored in a feature of - in the file format - in the case (for example, whether the broadcast has a header or footer, where the content starts/stops in the file). Differences in the file format can lead to incompatibility. For example, The file format of the iMode digital rights management system is the file format of the rule. However, the file format for the OMA digital rights management system includes a header containing the information required by the OMA digital rights management system to access the content (for example, including Identification and location of the key and the permitted license.) Therefore, when using one of the OMA digital rights management systems, the application attempts to read: iMode digits When the application manages a file protected by the system, the application will not find the desired header (because - the header does not appear in the file protected by her heart 126727.doc 200834440), and the application will not The content can be accessed. Although OMA and iMode are used in this example, it should be understood that such specific embodiments can be used with any suitable type of digital rights management system. Another difference between digital rights management systems can be the license format. As for the file format, if an application running under a certain type of digital rights management system cannot find a certain information at a certain position in the license, the application may not be able to check the permission for the permission, and therefore May not be able to access and

Relevant content. Different digital rights management systems can also have different license acquisition agreements. The specific embodiment of the present disclosure provides a component that performs the conversion/conversion required to allow the content protected by the type of digital rights management system to be used with different types of digital rights management systems. Application compatible. In the following example, the component takes the form of a software agent in the line. As explained in more detail below, = privately take other forms and add positions in different locations (for example, in the second sacred room of each of the hexagram devices), the component can also be Assign among different components (for example, between one set). I ^ machine device and - portable memory device are seen in the reference figure 'Figure i shows a host device and body device 804 text" " main type of device and including but not limited to (four) access to content Ren:! Computer, handheld game console, audio player (example 2: benefit), video player (such as dvd audio and / or video recorder, digital video player), machine, frequency converter, display device (Example 126727.doc 200834440 eg TV), printer, car audio and navigation system. The host device 50 of Figure 1 includes one or more processors 55 that execute a host application 6 and a software agent 70. As explained below, the software agent provides "cross-digit rights management" compatibility and can provide other functions, such as security management functions (such as login and decryption mechanisms ρ host applications 6 and software agents 70 can be implemented) The computer readable instructions stored on the computer readable medium can be executed by - or a plurality of processors on the host device 5G. Although the host application 60 and the software agent 7 are displayed as separate components, However, in an alternative embodiment, the components may be combined into a single component. For simplicity purposes, other components of the host device 5, such as display devices and drivers, are not shown in Figure 1. The "host application" Programs " refers to any application that can be used to access content. Examples of host applications include, but are not limited to, audio players, video players, and file viewers. In addition to accessing content, a host application can have other functions. For example, download (four) and store the information in a mmm. In this example, the host application 6 is called in this article. "DRMx" operates under the digital rights management system. The host device 50 is in communication with the portable memory device 8(). In general, the second portable memory device includes any device that stores a medium. The storage medium can be stored in communication with a host device that can access content stored in the storage medium. The portable memory device can include only the body (and associated circuitry) or can also include other components. (eg processing:). Examples of portable memory devices include, but are not limited to, removable memory cards (eg, non-volatile, solid-state memory devices such as flash memory cards), light 126727.doc 200834440, disks And any of the examples of host devices listed above, in which case the devices have a storage medium and can be placed in a (wired or wireless) communication with a host device for accessing storage in the storage medium. Corruption. Therefore, a "host device" may in some cases be a "portable memory device" for another host device in other situations. For example, in some cases A cellular phone can be used as a host device. However, in other situations, a cellular phone can be connected when a cellular phone is connected to a personal computer so that content can be delivered from the cellular phone to the personal computer. It can be used as a portable memory device. As can be seen from these examples, a portable memory device can be used as a dedicated storage device or can include additional functions such as playing music, making calls, etc. It should be noted that Providing content and/or permissions to the host device without the use of a portable memory device (eg, when the host device downloads content and/or permissions from a server). Therefore, a host device does not necessarily have to be a good A portable memory device for receiving content and/or permission for the content. In this particular embodiment, the software agent 70 acts as a component that allows DRM X protected content to be subject to different types of digital rights. Accessed by the management system. FIG. 2 is a diagram showing more details of the software agent 70. As shown in Figure 2, the software agent 70 includes (1) a common interface 72 for protected content and digital rights management and (2) a host subscription layer 74 for licensing format conversion and generation. (Software agent 70 may have other components, which are not shown in FIG. 2 to simplify the figure.) The basic principle of compatibility in this particular embodiment is that software agent 70 is not only loaded into the host device of FIG. 50, and loaded on other hosts 126727.doc -12· 200834440 devices that want to achieve "cross-digit rights management" compatibility. The common interface 72 is the same in each of these software agents and the host subscription layer 74 is customized for a digital rights system for a particular host device. Assuming that the content protected by the digital rights management has a file format and a license format that the common interface 72 can understand, the host subscription layer can generate a license supported by the digital rights management system of the host application and provide content for the content. Access, even if the file format and/or the license format of the content protected by digital rights management is not supported by the digital rights management system of the host application. Referring now to FIG. 1, when the host application 60 wishes to save the protected content of the portable memory device 80, since the host application 6 is operating under DRM X, the host application 6 will issue a command to Save content with the DRM X file format and save licenses with the drm X license format (as indicated by arrow 125 in Figure 2). (Alternatively, the host application 6 can issue a command to save content using the cross-digit rights management format.) However, in this example, DRM X is not supported by the common interface 72. Therefore, if the content and license are saved in the DRM X format, the software agents in other host devices will not be able to read the content and permissions, thereby preventing host applications on other host devices from accessing the protected content. In order to make the content and license "cross-digit rights management" compatible, the software agent 70 performs the method as shown in the flowchart of FIG. First, the protected content is transmitted to the software agent 70 for processing (action i 50). Then, if the broadcast format of the ^:protected content is not discriminated by the common interface 72 of the software agent, the file format is changed to be compatible with the common interface 72 (action 155). This operation is schematically illustrated in Fig. 4. In Figure 4, the slot case 126727.doc -13- 200834440 88 contains protected content 100 (which is shown as encrypted) and header 1〇8 for storing information used in the DRM X system. This file format is not discerned by the common interface 72 of the software agent 70. Thus, the host subscription layer 72 cooperates with the common interface 72 to change the file format to be compatible with the common interface. As shown by the two arrows in Figure 4, to accomplish this, the content can be decrypted and then The encrypted content is stored on the portable memory device 8 or the encrypted content can be simply moved to the portable memory device 80. In either case, the result has a common interface 72 by the software agent 70. The file of the identified file format is 9; in this article, it has a header 11 containing digital rights management information (for example, only five times, etc.). As shown in the optional action 16〇 in Figure 3, it can be updated. The content information is specified to be processed by the software agent. In Figure 4, the information is displayed as "+ INF0" in the file header 110. When the software agent on the same or different host device attempts to save When the content is taken, it will discover this information and understand the cross-digit rights management function that needs to perform the following instructions. As shown in Figure 4, even if the file format has been identified, it may be better to update the content information to specify The content is intended to be processed by the software agent, as the software agent may be able to perform additional functions relative to this content. Such additional examples are described in the patent documents referenced below. Transferring the license associated with the content to the software agent 70 (act 165). The license may be directly transmitted instead of the special license of the digital rights management system. If the license format is not through the common interface of the software agent 7 72, the license format is changed to be in phase with the common interface 72 (action 17). In some cases, in a compatible object or as a portable 126727.doc •14·200834440-licensed structure The license is retrieved and entered. Therefore, as indicated by the arrow 13 如图 in FIG. 2, the software agent 7 generates a portable (ie, #DRM χ (eg, DRM ζ)) format and license, even if the software agent 7) receives a command (arrow 125) to store content and permissions in the DRM X format. The portable file 90 and the portable license 12 are then stored in the portable memory device 80, as shown in FIG. Shown. As described below, may be by the host device, the portable memory device or another device to perform a text file format and generate portable portable permitted by one or both of the operation.)

It is now explained that this portable file format and portable licenses are used to provide cross-digit rights management compatibility. Consider, for example, the situation illustrated in Figure 5, in which the portable memory device 80 is thus placed in communication with another host device 175. The host device 175 includes a host application that operates using a digital rights management system (DRM y), which is different from a host application that stores the inner valley 100 on the portable memory device. The program 60 digital rights management system (DRM X, and π π η μ ^ X) is different from the portable digital rights management system (DRM Ζ). The host device 175 also includes a software agent 185, which includes a common interface 186 and a host custom layer 187 as shown in FIG. The software agent 185 is the common interface of the North Moxibustion-, 冋 interface I86 and another software agent 70 (4). However, the host agent layer 187 of the software agent 186 is subscribed to (10) instead of for DRMx. Figure 7 is a private diagram of a method for allowing access by the +m machine application 180, which is protected by the DRM y, protected by the digitally managed digital management. The first action of the method is to select the content (act 205). The internal hemorrhoids can be selected in any suitable manner. For example, the host on the host device 175 should have a function table for the user to manually select content options for the user by using the program 180 (or another application). Many alternatives are available. For example, instead of using a menu, the user can type in the name of the content he wants to select, or the user can automatically select the content (eg, when the host application 180 automatically selects content based on previous selections made by the user) . As shown in Figure 7 and previously illustrated, the content is protected by portable digital rights management as identified by the common interface module of all software agents operating in this cross-digit rights management environment. After the content 100 has been selected, the host application 180 issues, opening the file " command to the software agent 185 to open the file 9 (action 21G). The software agent therefore checks the content to see if the content has been identified by the software agent 185 as being protected (act 215). In this particular embodiment, the common interface module 186e purchases the header 110 for the previously described stored information. The software agent 185 then sends the appropriate code back to the host application 18, and the host application 180 determines if the returned code is declared "protected," (action 22). (The code can, but does not have to use, the actual phrase "protected". That is, another phrase (or character, or more generally, material) can be used instead of the vocabulary, which is protected. If the returned code is not declared "protected, then the host application 18" retrieves the file 9 (ie, accesses the content 1) (action 258) and then closes the file 90 (act 260) The right-back code declaration "protected", the host application 18 sends a Know License command (see arrow 135 in Figure 6) to the software agent 185 (act 225). In response to the "Get Licensed" command, the software agent 185 (or 'subsystem'' as described below) obtains the portable license 120 (see arrow 140 of 126727.doc -16-200834440 in Figure 6), check The license in the portable license 12, and then generate a license with the digital rights management system of the host application 180 (ie, DRM is compatible (see arrow 146 in Figure 6). In operation, because of portability The license 120 is designed to be read by the common interface module of each participating software agent, so the common interface module 丨86 in the software agent 185 can read the portable license 12〇. Layer 187 understands the format required by the host application's Digital Rights Management System (DRM y) and cooperates with the common interface 186 to generate DRM y support from the portable license 12 = a license 'even if the portable license 120 is subject to The same is true for the support of different digital rights (4) systems (eg DRMz). The resulting license is then provided to the host application 180. It should be noted that the generated license can be the same as the license in the portable license 12或 or The same permit. For example, 'I's a license can have all or some of the permissions in the license (4) (for example, play five times, no age ^, etc.) and additional permission 'for example, can't move, can't copy, or play only Once ("cannot move,•and"cannot copy" constraints may be better, because if the generated licensed mobile broadcast is used, there may be incompatibility issues with other host applications.) The license in the license of the production ± does not necessarily match the license in the portable license accurately. In the case of a return permission, the license is checked to find out if there is a permission to access the content (action. If there is permission) The rights 9G is opened in a secure manner (act 235), and the file is read in a secure manner (action 24) (ie, the content is grouped in a secure manner (10) without the need for a digital rights management specification). 245) 126727.doc • 17- 200834440 Figure 8 is a flow chart showing more details of the check permission action (act 230). As shown in Figure 8, the host application 18 receives the request. (Action 1) The host application 18 then retrieves the grant (act 1010) and parses its required grant based on the requested access (action 1〇2〇). The requested access is then made using the parsed grant. Effective (action 1〇3〇). It should be noted that the software agent 70 can provide the license formatted according to the host digital rights management before the action 1. Then the host application is taken from the license extraction operation. 60 is charged (action 1〇1〇). However, instead of providing a license based on host digital rights management, the software agent 7 can provide permission for parsing. In this manner, the host application 18 will not need to capture permission and will not need to perform actions 1000 and 1010. There are several alternatives that can be used with these specific embodiments. For example, as described above, "subsystem," action 228 can be performed. The subsystem may be attached to the host device, the portable memory device, another device (e.g., a device in the network) or distributed to one or more of the devices. For example, the subsystem may be a digital rights management agent in the software agent that is connected to the portable memory device, reads the license from the portable memory device, checks the permissions, and provides the license : The L machine application. As another example, the portable memory device can (4) execute its own processor of the digital agent. In such a specific embodiment, the software agent can query whether the digital rights management agent running on the portable memory device allows the host application to access the content. The digit_(d) agent then (4) obtains the license, checks the permission, and provides the appropriate # permission to the software agent. More specifically 126727.doc -18- 200834440, by the first clock 瞀 吉 受 第 = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = A #忆体 device of the host device or a host device with the host device generates a feeding device, a tough license and/or a portable file for wired or wireless communication. Format. Should be > idea a portable and / or licensed to the host device ': does not necessarily need to provide content server download to the host two: two, content and / or perhaps from - feeding

" is wirelessly transmitted from another host device to the host device, or can be loaded from a P^ side (e.g., downloaded to a PC and moved to the portable memory device). (The phrase "wireless delivery" contains "benefitline: fetch") Therefore, the portable memory device is not required to be implemented and should not be misinterpreted in the scope of the patent application, unless It is explicitly stated. In addition, as suggested above, although the license is not stored in the same memory device as the text, it should be understood that the license can be stored in any suitable location and not necessarily : on the same memory device as the content. It should also be / thought that some of the actions described in this article can be performed in a different order. For example, 'can be generated before or after the generated-portable file format action is generated. The actions described in this specification are therefore not to be construed as requiring a specific order unless explicitly stated. In addition, certain actions are described herein as being represented by the software. , host application, host or subsystem to execute, but it should be noted that these actions can be performed by different entities named or unnamed in this article. For example, an environment can be designed to be executed by the host 126727.doc -19-200834440 application to perform some or all of the P actions performed by the software agent. In addition, the host and / Or the portable memory device can have an eight-part, and the device 'executes some or all of the actions. For example, the host or the portable memory device can have a digital rights management module that checks for permission and The license is updated. Accordingly, the performance of the actions described herein may be distributed in any suitable manner. Further, although specific embodiments may be implemented in any suitable environment, the presently preferred

The specific implementation of these implementations is implemented on the TrustedFlashT provided by SanDlsk. In a particular embodiment, a computer readable storage medium storage computer readable operational command (i.e., computer readable code) is operative to perform the actions involved in such specific embodiments. Examples of computer readable storage media include, but are not limited to, solid state storage devices, optical storage devices (eg, (3) or qing), and magnetic storage devices such as 'hard rhyme phrases, material read storage media'. Or a single-storage medium or a plurality of storage media in a plurality of devices. Thus, "brain readable storage media" can be located, for example, in a host device or a portable memory device or both. In a specific embodiment, the portable memory device can include a computer readable storage medium carrying an operation instruction (ie, a computer executable code (4) software agent. When the portable memory is used When the device is placed in communication with the host device, instructions can be provided to the host device. The instructions are then stored in a computer readable storage medium of the host device. In this manner, plug and play can be used. The software agent is placed on a host device. In another embodiment, the software agent is pre-loaded with the host device. 126727.doc -20- 200834440: The computer in the host device The readable media device sells the host device to the end user for the purpose of making a daily order to be able to 藓, ^ human agent in any case. or set another device (5), for example, in the network - Computer) Lieutenant: The body processor executes the operation instructions. In addition, as described above or the performance of the evening action. For example, 彳4彳 can be used to perform certain operations on a device in the portable device (the portable device can be read in the portable memory) Take the storage medium), and the set=host can execute other operation instructions (stored in the computer readable storage medium in the portable processor). In addition, the master can read the media and carry it out by the processor on the computer in hardware. Based on the simple purpose == there is an operation instruction in the text, the term "mechanical", the term "circuit", will be used to cover only hard-inviting implementations, software-only implementations and/or hardware and software. Implementer t. Therefore, "circuit, take, one type of health: - two towers privately take a processor or stored in a computer readable medium and can read the form of the code. "circuit" can also;:: : The computer circuit (ASIC), programmable I #< should be used in the form of integrated power, ^ 铒 ^, dare-in microcontroller and single-board computer. Therefore, good circuit should not be limited to this article or another month. Any particular type of implementation. In addition, "circuits•• should not be obligated to perform the functions described in this article. For example, when the circuit takes the form of a processor that performs the exercise, it should be understood that the processor can be executed. Functions other than those described above. A patent document contains specific % examples that can be used in the specific embodiments described herein. Each of these patent documents is the same as 126727.doc - 21-200834440 Proceeding to apply for 'transfer to the assignee of the present invention and incorporated herein by reference: "Method of Linking Content to Licenses, US Patent Application No. 1 1/599,655 ;"Content and license The device of the link ", U.S. Patent Application Serial No. 11/600,270;, the method of accessing content according to the conference ticket H, US Patent Application No. 11/600,263;,, the device for accessing content according to the conference ticket&quot ;, U.S. Patent Application Serial No. 11/600,273;

A method of separating a memory device, 'U.S. Patent Application Serial No. 11/600,262; A method of previewing content, 'US Patent Application No. 11/599,994; "A system that allows multiple users to access preview content, US Patent Application No. 11/599,995; allows for first digital rights management The system protects the content that can be accessed by the second digital rights management system ", US Patent Application No. 11/5 99, 991; "Method of Connecting to Content-Related Network Locations,", US Patent Application Case No. 11/600,300; and, the system connected to the content-related network location, US Patent Application No. nickname. The above detailed description is to be understood as illustrative of alternative forms that may be employed in the present invention rather than the definition of the invention. The following claims are intended to cover all such equivalents. Finally, it should be noted that any combination of any of the preferred embodiments described herein is used. Aspects may be used alone or in conjunction with each other. [Brief Description] Portable Memory Device FIG. 1 is a diagram of a host device and a description of a specific embodiment. 126727.doc -22- 200834440 Figure 2 is an illustration of a software agent in one embodiment. Figure 3 is a flow diagram of a method for converting a file format and a license format. Figure 4 is an illustration of one embodiment of a conversion of a file format. Figure 5 is an illustration of another host device in communication with the portable memory device. Figure 6 is an illustration of the software agent of the host device of Figure 5. Figure 7 is a flow diagram of a method of a particular embodiment that allows content protected by a first digital rights management system to be accessed by a second digital rights management system. Fig. 8 is a flow chart showing the operation of "checking permission" in Fig. 7. [Main component symbol description] 50 host device 55 processor 60 host application 70 software agent 72 common interface 74 host customized layer 80 portable Memory Device 88 File 90 File 100 Content 108 Header 110 Header 126727.doc -23 - 200834440 120 Portable License 175 Host Device 180 Host Application 185 Software Agent 186 Common Interface 187 Host Custom Layer 126727.doc - twenty four -

Claims (1)

200834440 X. Patent Application Scope 1. A method for providing a license to the application for content protected by a digital rights management system other than an application digital rights management (DRM) system, The method comprises: • (a) receiving, from an application, a request for permission by one of the content guaranteed by a first digital rights management system, the first digital rights management system being different from the application a digital rights management system; (b) generating, from a license supported by the first digital rights management system, a license supported by the application's digital rights management system; and (e) providing the generated license to the license application. 2. The method of claim 1, wherein the license supported by the first digital rights management system is identifiable by a component in communication with the application and wherein the component generates the license in (b). 3. The method of claim 2, wherein the component comprises a portion of an apparatus of an application. 4. The method of claim 2 wherein one of the first devices comprises the application, the component being a __second device in communication with the first device. . A method of claim 4, wherein the second device comprises a portable memory device. 6. The method of claim 2, wherein the component comprises a software agent. 7. The method of claim 6, wherein the software agent includes a first ',', and operable to identify the license supported by the digital rights management system to generate the application The second module of the license supported by the Digital Rights Management Department of the program 126727.doc 200834440. 8. The method of claim 2, wherein the content is stored in a file including a file format, wherein the file format is not supported by the application's digital rights management system but can be distinguished by the component . 9. The method of claim 2, wherein the component is also included in a plurality of devices, each device including an additional application, such that each application is supported by a digital rights management system of the application. A license. 10. The method of claim 1, wherein the generated license comprises at least one license from the license supported by the first digital rights. The method of claim 1, wherein the generated license includes at least one of the licenses not supported by the first digital rights management system. 12. The method of claim 2, wherein the at least one grant comprises one or both of a move constraint and a copy constraint. 13. A method for storing content protected by a first digital rights management (DRM) system in a portable format, the method comprising: (a) receiving a request to store a first digital right Administering the content protected by the system; and (b) performing one or both of the following steps: (b) generating a portable license for the content from a license supported by the first digital rights management system; (b2) generating a portable file format for the content from a file format supported by the first digital rights management system. 126727.doc -2 - 200834440 14·as in claim 13 Fang Ganshi# .^ ^ where hunting is performed by a component that communicates with a library program providing the request (b) e application 15. as requested 14 The part of the big &amp; sun device. The 'component' includes - an application's 16=== method, where a first-device includes the application, minutes. The device of the second device is provided as in the method of claim 16, the device is in the middle of the device. The device in the device comprises: a portable memory. 18. The method of claim 14, wherein the component comprises a software Acting. 19. According to the method of claim 13, 苴逸一吹', ν匕 includes storing a negative information related to the content, wherein the information specifies that when Dangda tries to access the content, it should provide The digit_management component is used to process the content. 20. The method of claim 13, further comprising performing both (bl) and (b2). 2i. - for storing in a portable-portable format A method of content protected by a first digital rights management (DRM) system, the method comprising: (4) receiving from a computing platform - requesting content protected by a first digital rights management system; and (b) Performing one or both of the following steps using a second computing platform in communication with the first computing platform: (bl) a license supported by the first digital rights management system to generate a portability for the content License; and (b2) from the A file 126727.doc 200834440 supported by the digital rights management system generates a portable file format for the content. 22. The method of claim 2, wherein the second meter includes Hosting t to a portable memory device in communication with the host device. 23. The method of claim 22, wherein the first computing platform comprises one of performing (b) Software agent. 24. The method of claim 21, further comprising storing a poor news associated with the content, wherein the information specifies that when attempting to access the content, the processing should be performed by providing a digital function. The content. 25. The method of claim 21, wherein the step further comprises executing (5) and (b2) a computer readable medium storing instructions for: U) receiving an application from an application a first digital rights management (drm) = the content of the protected content - the permission - the request, the first digital security system is different from the application of the digital rights management system; (b) from the first A license supported by the digital rights management system generates a license supported by the digital rights management system of the application; and (c) provides the generated license to the application. 27. The computer readable medium of the item 26, wherein the computer readable medium comprises a portion of a device of the application. 28. The computer readable medium of claim 26, wherein a first device comprises the application, and wherein the computer readable medium is part of a second device in communication with the first device. 29. The computer readable medium of claim 28, wherein the second device comprises a 126727.doc 200834440 portable memory device. 30. The computer readable medium of claim 26, further storing instructions for identifying the license supported by the first digital rights management system. 31. The computer readable medium of claim 26, wherein the content is stored in a file comprising a file format, and wherein the computer readable medium further stores instructions for identifying the file format. 32. The computer readable medium of claim 26, wherein the generated license comprises At least one of the licenses supported by the first digital rights management system. 33. The computer readable medium of claim 26, wherein the generated license comprises at least one of the licenses not supported by the first digital rights management system. 34. The computer readable medium of claim 33, wherein the at least one grant comprises one or both of a movement constraint and a copy constraint. 35. A computer readable medium storing operation instructions for: (a) receiving a request to store content protected by a first check sigh profit management (DRM) system; and One or both: (M) from a license supported by the first digital rights camp ~ &amp; amp 产生 to generate a portable license for the content; and (b2) from the first digital right The file format supported by the management system produces a portable format for the content. 36. The computer readable medium of claim 35, wherein the counter is stored in the device 126727.doc 200834440 including the application providing the operator θ. . A computer readable medium as claimed in claim 35, for the requested application, and wherein the operations to be used for (b) are stored in communication with the first device A computer readable medium as claimed in claim 37, wherein the second device comprises a portable memory device. 39. The computer readable medium of claim 35, further comprising storing An operational instruction to store information related to the content, wherein the information specifies that the content should be processed by providing a component of the digital rights management function when attempting to access the content. The computer is readable media as claimed in claim 35, which further stores operational instructions for performing (bl) and (b2). A system for storing content protected by a first digital rights management (DRM) system in a portable-portable format, the system comprising: a first-to-be-study communication with a second computing platform, The first computing platform includes circuitry operable to: (a) receive a request from the second computing platform to store content protected by a first digital rights management system; and (b) perform one of the following steps or Both (b) generating a portable license for the content from a license supported by the first digital rights management system; and (b2) supporting one from the first digital rights management system The file format produces a portable file format for the content. 42. The system of claim 41, wherein the second computing platform comprises a host device 126727.doc • 6 - 200834440 and wherein the first computing platform is a portable memory that is integrated with the host device Part of the device. &amp;</RTI> the system of claim 41 wherein the first computing platform includes a software agent executing (8). 44. The system of claim 41, wherein the circuitry is further operative to store information related to the content, wherein the information specifies that when attempting to access the content, one of the components of the cross-digit rights management function should be provided To handle the content. The system of claim 41, wherein the circuitry is further operative to perform both (bl) and (b2). 126727.doc