JP5793767B2 - System and method for providing an electronic license - Google Patents

Description

  The system and method relate to digital rights management.

  With the growth of the Internet, the number of online consumers is increasing along with online companies that provide goods and services via the Internet. Thus, consumers are starting to expect more reliance on electronic transfer of information and instant access to information. While such easy access is a great benefit for consumers, while controlling consumer access is often a difficult task.

  One approach to controlling consumer access is to leverage digital rights management (DRM). DRM grants digital rights to information, thereby controlling user access and providing appropriate control to the information owner. For example, DRM allows information owners to receive royalties, track information usage, issue licenses, and so on.

  One common problem is that traditional approaches cannot adequately control consumer access to information. Consumers find ways to avoid owner control. For example, an owner sends a password to a consumer to access information. Once a consumer accesses the information, the consumer may copy the information and pass it on to others.

  Another common problem is that traditional approaches fail to provide a digital rights management system that can be used for various types of information. For example, some digital rights management systems may work for music files, but may not be appropriate for literary works.

  The present invention provides a system and associated method for authorizing access to data objects.

  The present invention relates to a system and method for providing a license management system in which a customer connects to a license management system via a communication medium using a computer. The customer exchanges information with the license management system through a communication medium in order to obtain various content copies, and a content cell including the requested content is created and transmitted to the customer. In addition, the customer exchanges information with the license management system through a communication medium to obtain a license to access the content, and a license cell including the requested license is created and transmitted to the customer. When the customer obtains both the content cell and the associated license cell, access to the content is allowed as specified in the content cell and license cell conditions.

  A feature of the system and method is that the license management system can fully manage access to customer information. The license management system can incorporate the license associated with the customer and the access rights related to the content in the content and / or the license. Thus, the customer can access the content after the license conditions are met. In addition, license rights allow the owner to manage various types of access to content. For example, the customer can view the content but cannot print the content.

  Another feature of the system and method is that the license management system can be used for a variety of different types of information. Since a wide range of content is created as a content cell and a license corresponding to the content cell is created, a license can be created for any content cell. For example, the customer can access various contents such as an audio file, an execution file, and a text file.

  Since the license management system can be accessed immediately through the communication medium, it is another benefit of this embodiment that the customer can receive and access the content without significant delay. The license management system allows the user to get a quick response to the request.

  For purposes of summarizing the invention, certain forms, features and novel features of the invention have been described herein. Not all of these features can be realized in a particular embodiment of the present invention. Thus, for example, as will be appreciated by one skilled in the art, the present invention may be implemented to implement one or more features taught herein, but not necessarily other features taught or implied herein. Is not something that is realized.

FIG. 2 is a high-level block diagram of one embodiment of the present invention illustrating information exchange between a license management system and a user computer. FIG. 2 is a high-level block diagram of one embodiment of the present invention showing the flow of information between a content manager, an offer manager, and a user computer. FIG. 3 is a block diagram of an embodiment of the user computer of FIG. 2. FIG. 3 is a block diagram of an embodiment of the content manager of FIG. FIG. 3 is a block diagram of an embodiment of the offer manager of FIG. FIG. 3 is a block diagram of an embodiment of a content cell. It is a block diagram of other embodiment of a content cell. FIG. 3 is a block diagram of one embodiment of a license cell. It is a block diagram of other embodiment of a license cell. 4 is a flowchart of one embodiment for providing access to content for a user. 6 is a flowchart of an embodiment for transmitting content. 3 is a flowchart of an embodiment for requesting a license. 6 is a flowchart of an embodiment for transmitting a license. FIG. 6 is a flowchart of an embodiment for checking content and licenses. FIG. 6 is a flowchart of an embodiment for generating content cells. 6 is a flowchart of an embodiment for generating a license cell.

  These and other features will be described with reference to the drawings. These drawings and the accompanying description are intended to illustrate embodiments of the invention and are not intended to limit the scope of the invention.

  Throughout the drawings, reference numbers are re-used to indicate correspondence between referenced elements. Further, the first digit of each reference number represents the drawing in which the element first appears.

  This application incorporates Benson et al. US Pat. No. 5,845,281, incorporated by reference.

  The present invention relates to a system and method for providing a license management system 120. FIG. 1 illustrates an embodiment in which a customer 110 is connected to a license management system 120 via a communication medium 130 using a user computer 115. In the illustrated system, the license management system 120 consists of two main components: an offer manager 122 and a content manager 124. The customer 110 exchanges information with the content manager 124 via the communication medium 130 to obtain various content copies. Content can be audio files, video files, text documents, email, database records, hypertext markup language (HTML) files, extensible markup language (XML) files, electronic data interchange (EDI) files, message-oriented middleware (MOM) ) Includes files, executable scripts, etc. Further, the customer 110 exchanges information with the offer manager 122 via the communication medium 130 and obtains a license for accessing the content.

I. Overview An overview of one embodiment of the license management system 120 is shown in FIG. In the illustrated system, user computer 115 communicates with offer manager 122 and contact manager 124 through communication medium 130. In the embodiment illustrated in FIG. 2, the offer manager 122 and content manager 124 of the license management system 120 are implemented as separate components connected to the communication medium 130. In other embodiments, offer manager 122 and content manager 124 may be part of a single directly connected system.

  FIG. 2 illustrates the flow of information when the customer 110 (FIG. 1) wants to access the content. For event A, user computer 115 requests content and the request is sent to content manager 124. At Event B, the content manager 124 sends a content cell 210 containing the requested content to the user computer 115. Next, at event C, user computer 115 requests a license and the request is sent to offer manager 122. At Event D, offer manager 122 sends license cell 220 containing the requested license to user computer 115. At events E and F, the user computer 115 verifies that it has both the content cell 210 and the corresponding license cell 220, and the user computer 115 grants access to the content.

  The advantage of this embodiment is that the user computer 115 receives the content and can access the content without significant delay because the license management system 120 is immediately accessible through the communication medium 130. The license management system 120 allows the user to receive a response to the request in a timely manner.

  Another advantage of this embodiment is that the license management system 120 manages the usage of the content of the user computer 115 with a license. The license management system 120 can incorporate license rights associated with the user computer 115 and access rights related to the content in the content cell 210 and / or the license cell 220.

II. Implementation of License Management System This section further describes one embodiment of a system for providing the electronic license shown in FIG. The illustrated system includes a communication medium 130, a user computer 115, and a license management system 120.

A. Communication Medium With respect to the communication medium 130 shown in FIG. 2, the presently preferred communication medium 130 includes the Internet, which is a global network of computers. The structure of the Internet, which is well known to those skilled in the art, includes a network backbone and a network that branches from the backbone. These branches have a further branched network. The router exchanges information packets at the network level, sends them from network to network, and sends them until they reach the vicinity of the destination. From the destination, a host in the destination network sends an information packet to an appropriate terminal or node. For a more detailed explanation of the structure and operation of the Internet, see “The Internet Complete Reference” (McGraw-Hill, 1994) by Harley Hahn and Rick Stout.

  In one advantageous embodiment, it is well known that the Internet routing hub comprises a Domain Name System (DNS) server. DNS is a Transfer Control Protocol / Internet Protocol (TCP / IP) service that is invoked when converting a domain name to an Internet Protocol (IP) address or from an Internet Protocol (IP) address to a domain name. The routing hub is connected to other routing hubs through high-speed communication links.

  However, one skilled in the art will recognize that a wide range of interactive communication media 130 can be used with the present invention. For example, the communication medium 130 includes an interactive television network, a telephone network, a wireless data transmission system, a two-way cable system, a customized computer network, an interactive kiosk network, an automated teller machine network, and the like.

  The World Wide Web is often used on the Internet. The World Wide Web includes different computers that store documents that can display graphics and text information. Computers that provide information on the World Wide Web are commonly referred to as “websites”. A website is specified by an Internet address, and an electronic page is attached to the Internet address. The electronic page is identified by a uniform research locator (URL). In general, an electronic page is a document that integrates the display of text, graphical images, audio, video, and the like.

B. User computer User computer 115 is shown in FIG. 3 and is a device through which a user exchanges information with communication medium 130 (FIG. 1). In one embodiment, user computer 115 is a conventional general purpose computer and includes one or more microprocessors, such as a Pentium® processor, a Pentium® II processor, a Pentium® Pro processor, an xx86 processor. , 8051 processor, MIPS processor, Power PC processor, Alpha processor are used. In one embodiment, user computer 115 may be a suitable operating system, such as Microsoft® Windows® 3.X, Microsoft® Windows® 98, Microsoft® Windows®. Trademark) NT, Microsoft (registered trademark) Windows (registered trademark) CE, Palm Pilot OS, Apple (registered trademark) MacOS (registered trademark), Disk Operating System (DOS), UNIX (registered trademark), Linux (registered trademark), Or IBM (registered trademark) OS / 2 (registered trademark) is running. In one embodiment, the user computer 115 can be a conventional modem or other network connection function, such as Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Data Link Interface (FDDI), Asynchronous transfer mode (ATM) is provided. As is conventional, in one embodiment, the operating system includes a TCP / IP stack that handles all message traffic entering and leaving the communication medium 130.

  In other embodiments, the user computer 115 is a computer workstation, a local area network of individual computers, an interactive television, an interactive kiosk, a personal digital assistant, an interactive wireless communication device, a handheld computer, a telephone, a router, a satellite, a smart card, for example. Any device that can exchange information with the communication medium 130, such as a built-in computing device, may be used. In such a system, although the operating system is different, it provides the appropriate communication protocol necessary to establish a communication link with the communication medium 130.

  The illustrated user computer 115 includes a browser module 310, a user manager 320, and a database collection 330.

1. Browser Module In one embodiment, the user computer 115 utilizes a plurality of operational modules including a user browser module 310. User browser module 310 (hereinafter referred to as user browser 310) is a software program that allows consumers to access different content providers through communication medium 130 (FIG. 1). In one embodiment, user browser 310 is Netscape® Navigator developed by Netscape, or Microsoft® Internet Explorer developed by Microsoft. However, those skilled in the art will appreciate that many other types of access software can implement embodiments of the present invention. Other types of access software may be, for example, other types of Internet browsers, custom network browsers, two-way communication software, cable modem software, point-to-point software, and the like.

2. User Manager In one embodiment, the user computer 115 includes a user manager 320. User manager 320 tracks and manages all content and licenses received by user computer 115. In one embodiment, the user manager 320 is loaded into the user computer 115 through a web-based download process. In the web-based download process, the user browser 310 can ask the user to download the user manager 320. If the user answers YES, the download process checks whether the user manager 320 supports the user browser 310. If so, the user browser 310 automatically downloads the user manager 320 onto the user computer. In other embodiments, the user manager download process may be performed without user intervention or the user manager 320 may be preinstalled on the user computer 115.

3. Database Collection In one embodiment, the user computer 115 includes the database collection 330 shown in FIG. The illustrated database collection 330 includes a plurality of databases, such as a license database 332, a content database 334, an encryption key database 336, and the encryption key database 336 can include one or more encryption keys.

  The license database 332 includes information regarding the license cell 220 received by the user computer 115. The information may include a copy of license cell 220 as received or decompressed information, such as license terms, license cell header information, and the like.

  The content database 334 includes information regarding the content cell 210 received by the user computer 115. The information may include a copy of the content cell 210 as received, or decompressed information, eg, encrypted content, content cell header information, etc.

  The encryption key database 336 contains the key received through the license cell 220, and the key is used by the user manager 320 to decrypt the encrypted content. In one embodiment, symmetric key encryption is used, but in other embodiments, other encryption methods can be used separately or in conjunction with symmetric encryption.

  In one embodiment, the database collection 330 can be implemented using a flat file database structure. In another embodiment, the database collection 330 can be implemented using other databases, such as using a Microsoft® SQL server, which is a relational database that can access data using Structure Query Language (SQL). it can. Furthermore, although the data collection 330 shown in FIG. 3 is comprised of a plurality of individual databases, in other embodiments, the database collection 330 can include other databases or can be combined with other databases. . In addition, the database collection 330 may be implemented as a single database having a plurality of individual tables, or may be implemented as another well-known data structure, such as a linked list, binary tree, or the like.

C. License Management System In one embodiment, the license management system 120 (FIG. 1) manages content and license generation and issuance. In another embodiment, license management system 120 primarily manages the issuance of content cell 210 and license cell 220, and separate modules may generate license cell 220 and / or content cell 210. As described above, the license management system 120 includes two main components, the content manager 124 and the offer manager 122. However, in other embodiments, there may be multiple content managers 124 and / or multiple offer managers 122.

1. Content Manager FIG. 4 illustrates one embodiment of the content manager 124. The illustrated content manager 124 includes web server software 410, a content manager component 420, and a database collection 430.

a. Web Server Software In one embodiment, content manager 124 includes web server software 410 as shown in FIG. The web server software 410 may be, for example, Netscape Internet server software, Microsoft Internet server software (ISS), or the like. Such web server software 410 is configured to process messages from the user computer 115 and the offer manager 122 as shown in FIG.

b. Content Manager Component In one embodiment, the content manager 124 includes a content manager component 420 that manages the creation and publication of content cells 210. The content manager component 420 shown in FIG. 4 includes two processes, a user manager download process 422 and a content cell generation process 424. The content manager component 420 may include other processes not shown, for example, a process for registering and managing users, a process for tracking inventory of content cells, and a process for providing a search engine.

  The user manager download process 422 downloads the user manager 320 to the user computer 115. In another embodiment, the user manager download process 422 may be performed by other modules, or the user manager 320 may be preinstalled on the user computer 115. Content cell generation process 424 is invoked when user computer 115 requests content and process 424 generates content cell 210 for the requested content. In this embodiment, the content manager 124 includes a content generation process 424, but in other embodiments, another module may generate the content cell 210, and the content manager 124 generates the content cell 210. The issue of the content cell 210 may be mainly managed by locating rather than locating.

c. Database Collection In one embodiment, the content manager 124 includes the database collection 430 shown in FIG. The illustrated database collection 430 includes a plurality of databases, such as a convention database 432, an encryption key database 434 (an encryption key database includes one or more symmetric keys), a public certificate database 436, a content database 438, a cell. A header information database 439 is included.

  The contract database 432 contains contracts regarding how and when to assign rights to content. The convention may be general (for example, content X requires license Y), or more specific (for example, anyone with license Y can print content X. print content X Requires a license Y, otherwise it jumps to URL C.). Although FIG. 4 shows the conventions as being stored in the convention database 432, in other embodiments, the conventions may be stored in other formats, eg, stored in a program or set of script formats. Also good.

  Cryptographic key database 434 includes a set of symmetric keys that are used by content manager 124 to decrypt the requested content. Symmetric keys can be generated using well-known techniques. For a more detailed description of symmetric and asymmetric cryptography, see Bruce Schneier's "Applied Cryptography: Protocols, Algorithms, and Source Code in C, Second Edition" (John Wiley & Sons, 1996). Although this embodiment uses symmetric ciphers, in other embodiments, other cipher methods may be used separately from or in connection with symmetric ciphers.

  Public certificate database 436 includes public certificates from other components with which content manager 124 communicates. The component's public encryption key is contained in the component's public certificate. For example, the public certificate database 436 includes the offer manager 122's public certificate (including the public encryption key of the offer manager 122) for encryption and authentication when the content manager 124 and the offer manager 122 communicate. Also good. The public certificate database 436 may include the public certificate of the user computer 115 that requested the content.

  The content database 438 includes various content itself and information regarding the content. Content includes audio files, text documents, emails, database records, hypertext markup language (HTML) files, extensible markup language (XML) files, electronic data interchange (EDI) files, message-oriented middleware (MOM) files An executable script or the like may be included. The content database 438 may include an issuer table, an issue table, an article table, and the like.

  The issuer table stores information about issuers. The issuer table may include fields such as issuer ID, status (indicating whether the issuer is active), issuer name, default price, and the like. Each issuer can issue one or more issues.

  The issue table stores information about the issue. The issue table includes issue ID, status (indicating whether the issue is active), issue code, attribute, issuer ID, domain, issue name, issue file type, issue web address, introduct Fields such as Lee credit, default price, number of free articles, print field (indicating whether printing is possible), copy field (indicating whether copying is possible), etc. Each issue contains one or more articles.

  The article table stores information about articles (each content). The term “article” is used, but the term “article” refers to audio files, video files, text documents, emails, database records, hypertext markup language (HTML) files, extensible markup languages ( It is recognized that content such as XML) files, electronic data interchange (EDI) files, message-oriented middleware (MOM) files, executable scripts, etc. may be included. The article table may include fields such as title, time stamp, issue ID, issuer ID, price, validity period, and cell type.

  The content database 438 may include other tables related to content such as an application table and an administrator table. The application table defines various applications and includes fields such as a description field, an application ID, and a price. The administrator table stores special accounts having authority to perform management tasks such as price, end date, and group settings. The administrator table may include fields such as name, password, email address, telephone number, issuer ID, administrator level, group account management permission, and promotion management permission.

  The cell header information database 439 includes information on the cell header. This information may include a unique identifier for each content cell 210, information about the various stores that produce the content, descriptive information, and authentication information (eg, expiration date / time).

  Regarding the database collection 430, in one embodiment, there may be a plurality of processes (not shown) such as an ID generator, a number generator, a statistics generator, a session generator, and a temporary storage unit that work with the database collection 430.

  In one embodiment, the database collection 430 is implemented using a Microsoft® SQL server, which is a relational database that can access data through a structured query language (SQL). SQL is a language standardized by the International Organization for Standardization (ISO) to define, update, and query relational databases.

  In another embodiment, the database collection 430 may be implemented using another relational database or another type of database (eg, a flat file database). Furthermore, although the database collection 430 shown in FIG. 4 is comprised of a plurality of individual databases, in other embodiments, the database collection 430 may include other databases or several databases may be combined. good. The database collection 430 may be implemented as a single database having individual tables, or may be implemented as another known data structure such as a linked list or a binary tree.

  In one embodiment, the database collection 430 is connected to a backend component (not shown) that receives database requests through a servlet (a small program that runs on the server) and sends SQL requests corresponding to the database 430. May be. In other embodiments, the way of accessing the data may be different, for example using different types of backend components or accessing the database collection 430 directly.

  A more detailed description of an embodiment of database collection 430 can be found in Appendix A attached. Appendix A database collection 430 illustrates license management system 120, where content manager 124 and offer manager 122 both access the same database collection, but in another embodiment, content manager 124 and offer manager 122. May have separate copies of various databases.

2. Offer Manager FIG. 5 illustrates one embodiment of the offer manager 122. The illustrated offer manager 122 includes web server software 510, an offer manager component 520, a license manager 530, and a database collection 540.

a. Web Server Software In one embodiment, offer manager 122 includes web server software 510 as shown in FIG. The web server software 510 may be, for example, Netscape Internet server software, Microsoft Internet server software (ISS), or the like. Such web server software 510 is configured to process messages from the user computer 115 and the content manager 124.

b. Offer Manager Component In one embodiment, as shown in FIG. 5, offer manager 122 includes an offer manager component 520 that manages the issuance of license cells 220. The offer manager component 520 manages information exchange with the user, determines whether the user request is satisfied before the license manager 530 is called, tracks payment of money, determines whether a license has been issued, and other processing (not shown). ) May be included.

c. License Manager Component In one embodiment, offer manager 122 includes a license manager 530 that manages the creation of license cells 220. The license manager 530 shown in FIG. 5 includes a license cell generation process 532. The license cell generation process 532 may be invoked after the user computer 115 requests a license for the content cell 210. The license cell generation process 532 generates a license cell 220 for the requested content. In this embodiment, the license manager 530 includes a content generation process 424, but in other embodiments, another module may generate the license cell 220.

  For example, offer manager 122 may include license cell generation process 532 to generate license cell 220. However, in one embodiment, another module may generate the license cell 220, and either the license manager 530 or the content manager 124 may place the appropriate license cell 220.

  The license manager 530 may include other processes (not shown) such as temporary storage of issued licenses. Note that in one embodiment, the license manager 530 includes an issued license database 547 that is tracked each time a new license is generated. With this management, the license manager 530 becomes an audit trail of the process of licensing, and can provide the requested license information to other modules.

d. Database Collection In one embodiment, offer manager 122 includes database collection 540 shown in FIG. The illustrated database collection 540 includes a convention database 541, an encryption key database 542 (including one or more symmetric keys), a public certificate database 543, a content database 544, a user database 545, a group database 546, and an issued license database. (“License database”) 547, charging database 548, cell header information database 549, and the like.

  The contract database 541 includes contracts regarding how and when to assign rights to content. The conventions can be general (eg, content X requires license Y) or more specific (eg, anyone with license Y can print content Y, print content X May require a license Y, otherwise it will jump to URL C). Although FIG. 5 shows the convention database 541, in other embodiments, the conventions may be stored in other formats such as programs and scripts.

  The encryption key database 542 includes a set of symmetric keys that the content manager 124 uses to encrypt the requested content. Symmetric keys can be generated using well-known techniques. For a more detailed description of symmetric and asymmetric cryptography, see "Applied Cryptography: Protocols, Algorithms, and Source Code in C, Second Edition" by Bruce Schneier (John Wiley & Sons, 1996). Although this embodiment uses symmetric ciphers, in other embodiments, other ciphers that are different or related to symmetric ciphers may be used.

  Public certificate database 543 includes a set of public certificates from other components with which offer manager 122 communicates. The component's public encryption key is in the component's public certificate. For example, the public certificate database 543 may include the public certificate of the content manager 124 (including the public key of the content manager 124) so that authentication can be performed when the content manager 124 and the offer manager 122 communicate. The public certificate database 543 may include a public certificate of the user computer 115 that requests a license.

  In certain embodiments, offer manager content database 544 may include some or all of content manager content database 438. The content database 544 uses well-known data replication techniques to copy data from the content manager content database 438 so that the offer manager 122 and the content manager 124 can copy the same data without compromising the identity of the data. You may make it have. Further, the offer manager content database 544 may include information not included in the content manager content database 438. Although this embodiment has shown that offer manager 124 and content manager 122 each have a copy of the same content database 544, 438, in another embodiment both offer manager 122 and content manager 124 have the same content. You may access the database. For more detailed information of one embodiment of the content database 544, please refer to the section titled “1. Content Manager c. Database Collection”.

  User database 545 tracks information about the user. The user database 545 may include tables such as a user information table, a user credit card information table, a user comment table, and a user account balance table.

  The user information table contains information about users of the system. User information table includes user account ID, name, last name, business, email address, account creation data, account status, current billing amount, current credit, balance limit, service level, promotional email, remote user, remote address, remote Fields such as host, billing name, billing address, password, password encryption type may be included. The user credit card information table holds a record of the user's encrypted credit card number and other credit card information. The user credit card information table may include fields such as a user account ID, a credit card encryption method, an encrypted credit card account number, a credit card expiration month, and a credit card expiration year. The user comment table tracks specific user comments and enables customized customer support. The user comment table includes fields such as a user account ID, a time stamp, and a comment field. The user account balance table keeps a record of the user's credit and billing amount for each specific issue accessed by the user. User account balance table includes fields such as user account ID, issue ID, credit generation time, available credit, applied credit amount, current charge amount, displayed price condition, and other information related to user account May be included.

  The group database 546 connects a plurality of users to one account such as a corporate account. The group database 546 may include tables such as a group table, a group user table, and an issue table.

  The group table maintains information related to the group. The group table includes fields such as group ID, group name, password, account type, number of days for which the account is valid, issue ID, and expiration date. The group user table identifies group members. The group user table may include fields such as a group ID, a user account ID, and an expiration date. The group publication table identifies publications accessible to group members. The group publication table may include fields such as group ID and publication ID.

  The license database 547 may include a plurality of tables such as issued license tables. The issued license table records each license issued to the user that allows access to the article. The fermented license table may include fields such as transaction ID, time stamp, article ID, content cell location, content cell ID, framework ID, issue ID, and billing amount.

  Billing database 548 manages billing transactions. The billing database 548 may include tables for current transactions, billable transactions, billable applications (summary), and the like. Other standard billing information may be included in billing database 548.

  Cell header information database 549 includes information for cell headers. This information includes a unique identifier for each license cell 220, a unique identifier for each content cell 210, information about the various stores that produce the content, descriptive information, and verification information (eg, expiration date and time). ) May be included.

  The database collection 540 may include other databases (not shown) to perform various management tasks. For example, the database collection 540 may include a user action database that tracks various user activities, such as user requests, and may use click-throughs (tracking each time a user selects a web link). The database collection 540 may include an error database that tracks various system errors, such as errors related to a specific article, errors related to a new user, errors related to a new license, and the like. Database collection 540 may include a database for maintaining data identity, such as various synchronization tables that alert the system when new information is added and / or when existing information must be changed. good. The database collection 540 may include a sales promotion database that tracks sales promotions sent to users via email and other communication means. Database collection 540 loads user manager 320 into one of the user's computers, such as when the user attempts to reinstall user manager 320 on one of the user's computers, or when the user verifies the user ID. May include user manager activation information for tracking the number of attempts made.

  With respect to database collection 540, in one embodiment, there may be multiple processes (not shown) such as an ID generator, number generator, statistics generator, session generator, temporary storage unit, etc. that work with database collection 540.

  In one embodiment, the database collection 540 is implemented using a Microsoft® SQL server, which is a relational database that can access data through Structured Query Language (SQL). SQL is a language standardized by the International Organization for Standardization to define, update, and query relational databases.

  In one embodiment, the database collection 540 can be implemented using different relational databases and different types of databases (eg, flat file databases). Furthermore, although the database collection 540 shown in FIG. 5 comprises a plurality of individual databases, in other embodiments, the database collection 540 may include other databases, or several databases may be combined. Also good. The database collection 540 may be implemented as a single database including individual tables, or may be implemented as other known data structures such as linked data and binary trees.

  In one embodiment, the database collection 540 is connected to a backend component (not shown) that receives database requests through a servlet (a small program that runs on the server) and sends SQL requests corresponding to the database collection 540. Also good. In other embodiments, access to the data may be done differently, for example, using different types of backend components, or directly accessing the database collection 540.

A more detailed description of an embodiment of the database collection 540 is in Appendix A attached. Appendix A database collection 540 shows license management system 120 in which both content manager 124 and offer manager 122 have access to the same database collection, but in another embodiment, content manager 124 and offer manager 122 You may have a database (similar, partially the same or different).
III. License Management System Cell In one embodiment, the license management system 120 generates a cell containing content (content cell 210) and a cell containing license (license cell 220).

A. Content Cell FIG. 6a is an embodiment of the content cell 210a. The illustrated content cell 210a includes a set of rules 612a, encrypted content 614a, a cell header 616a, a public certificate 618a, and a content cell signature 611a.

1. Convention The content cell convention 612a informs the user computer 115 what rights are associated with the content cell 210a and what is required to obtain that right. For example, content cell 210a may have a set of requirements for the right to print the article and a set of requirements for viewing the article. In one embodiment, the contract 612a may be written for a specific user, and in another embodiment, the contract 612a applies to a specific class of users written more generally. Things can be used.

2. Encrypted Content The content cell's encrypted content 614a contains the requested content that has been encrypted to the content manager 124. In one embodiment, the content is encrypted using a symmetric key. The symmetric key is encrypted by the license management system 120 using the offer manager's public key, and only the offer manager 122 can decrypt the target key, and the encrypted target key is sent to the user manager 320. When the user manager 320 requests a license, the user manager 320 sends the encrypted target key to the offer manager 122. When offer manager 122 verifies that user computer 115 has a valid license, offer manager 122 can decrypt the symmetric key, encrypt the symmetric key with the user manager's public key, and user manager 320 Allow the symmetric key to be decrypted and the content to be decrypted. For a more detailed description of symmetric and asymmetric encryption, see “Applied Cryptography: Protocols, Algorithms, and Source Code in C, Second Edition” by Bruce Schneier (John Wiley & Sons, 1996). This embodiment uses a combination of symmetric and asymmetric encryption, but other encryption methods may be used. For example, both the offer manager 122 and the content manager 124 may access a database of symmetric keys, and the symmetric key may not be transmitted to the user computer 115 until the user computer 115 obtains a license.

3. Cell Header The cell header 616a includes information regarding the content cell 210a. Such information includes the unique identifier of the content cell 210a, information about the store that produces the requested content, descriptive information, information for positioning the offer manager 122 (eg, the URL of the offer manager), and verification information ( For example, the date and time of the expiration date may be included.

4). Public Certificate The content cell public certificate 618a is a public certificate of the cell creator and includes the public key of the cell creator. For example, if content manager 124 creates content cell 210a, content manager 124 signs cell 210a and includes the public certificate in content cell 210a. The public certificate 618a allows a cell recipient (eg, user computer 115) to verify the authenticity of the sender (eg, content manager 124).

5. Content Cell Signature The content cell digital signature 611a is information based on both the content cell 210a and the content manager's private key. The digital signature 611a is used for the user computer 115 and used to authenticate the creator of the content cell 210a and the information contained in the content cell 210a.

  In general, a digital signature is a code that is unique to each message and to the sender of the message. Authentication using a digital signature ensures the recipient that the message is from the sender as expected and verifies that the message is complete and unmodified. Digital signatures are cryptographic means that can be used to verify the origin of the cell and the identity of the sender. For a more detailed explanation of digital signatures, see “Applied Cryptography: Protocols, Algorithms, and Source Code in C, Second Edition” by Bruce Schneier (John Wiley & Sons, 1996).

6). Other Signatures FIG. 6b shows another embodiment of content cell 210b. The convention 612b, encrypted content 614b, and cell header 616b are similar to those described above, but each component has its own digital signature 613b, 615b, 617b. Each digital signature 613b, 615b, 617b is generated by the module that generated the component. For example, the contract signature 613b is generated by the module that generated the contract 612b, and the cell header signature 617b is generated by the module that generated the cell header 616b. In another embodiment, different modules may generate different portions of the content cell 210, each module providing its own digital signature. This feature allows cell recipients to verify the identity of the component creator. In order to verify the creator's identity in this embodiment, the content cell 210 must include a public certificate 618b for each module that generated the content cell 210 portion.

  In another embodiment, the digital signature may be used for a separate convention or set of conventions. For example, if module A generates rules X, Y, and Z and module B generates rules M and N, module A can sign rules X, Y, and Z, and module B signs rules M and N. it can. Both module A and module B public certificates are sent in the content cell 210 and the user can verify the origin of each contract.

  In another embodiment, the content cell 210 may consist of different components or may include only a subset of the components described above. Furthermore, although various encryption techniques such as symmetric encryption, asymmetric encryption, and digital signature have been discussed, other security ensuring means may be used in other embodiments.

B. License Cell FIG. 7a shows one embodiment of a license cell 220a. The illustrated license cell 220a includes a set of encrypted rules 712a, an encrypted license 714a, a cell header 716a, a public certificate 718a, and a license cell signature 711a.

1. Rules The license cell rules 712a inform the user computer 115 what rights are associated with the license cell 220a and what is needed to obtain those rights. For example, license cell 220a may have a set of requirements for the right to print the article and another requirement for viewing the article. In one embodiment, the convention may be written for a specific user, and in another embodiment, the convention may be written more generally and applied to a specific class of users. In one embodiment, both license cell 220 and content cell 210 include conventions 612, 712. In another embodiment, only license cell 220 or only content cell 210 includes conventions 612, 712, or neither includes conventions 612,712.

2. Encrypted License The encrypted license 714a of the license cell includes the requested license encrypted by the license manager 530. In one embodiment, the license is a unique identifier. In another embodiment, the license may be another type of data, such as a record of information, and the license may include a contract.

  In one embodiment, the license is encrypted using a symmetric key. For example, the license may be encrypted using the same symmetric key that encrypted the content. In one embodiment, the symmetric key is encrypted by the license management system 120 using the user manager's public key, so that only the user manager 320 can decrypt the symmetric key and thus decrypt the license. Although this embodiment describes the use of symmetric and asymmetric keys, other encryption methods may be used.

3. Cell Header The cell header 716a includes information regarding the license cell 220a. Such information includes a unique identifier for the license cell 220a, an identifier associated with the content cell 210, information about the store producing the requested content, descriptive information, and verification information (eg, expiration date and time). May be included.

4). Public Certificate The license cell public certificate 718a is a public certificate of the cell generator and includes the public key of the cell generator. For example, if the license manager 530 generates the license cell 220a, the license manager 530 signs the cell 220a and includes the public certificate 718a in the license cell 220. The public certificate 718a allows a cell recipient (eg, user computer 115) to verify the authenticity of the sender (eg, license manager 530).

5. License Cell Signature The license cell digital signature 611a is information based on the license cell 220a and the private key of the license manager. Using the digital signature 611a, the user computer 115 confirms the creator of the license cell 220a and the information contained in the license cell 220a.

6). Another Signature FIG. 7b shows another embodiment of license cell 220b. The convention 712b, encrypted license 714b, and cell header 716b are similar to those described above, but each component has its own digital signature 713b, 715b, 717b. Each digital signature 713b, 715b, 717b is generated by the module that generated the components 712b, 715b, 716b. For example, the contract signature 713b is generated by the module that generated the contract 712b, and the cell header signature 715b is generated by the module that generated the cell header 714b. In another embodiment, different modules may generate different portions of license cell 220b, so that each module provides its own digital signature. This function allows the recipient of the cell to confirm that the component generator is authentic. In this embodiment, in order to verify the identity of the creator, the license cell 220b must include a public certificate 718b in each module that generated the portion of the license cell 220b.

  In another embodiment, digital signatures may be used to sign individual rules or a set of rules. For example, if module A generates rules X, Y, and Z and module B generates rules M and N, module A signs rules X, Y, and Z, and module B changes to rules M and N. Will sign. The public certificates of modules A and B will be sent in the license cell 220 and the user will be able to verify the origin of each contract.

In another embodiment, license cell 220 may consist of other components or may include some of the components described above. Furthermore, although various encryption techniques such as symmetric encryption, asymmetric encryption, and digital signature have been discussed, in another embodiment, security may be secured by another method.
IV. Overview of License Management Process FIG. 8 shows a flowchart of one embodiment of the information flow previously discussed in FIG. The flow chart shown in FIG. 8 corresponds to the information flow of FIG. 2, step 820 is event A, step 830 is event B, step 840 is event C, step 850 is event D, and step 860 is event E. Step 870 corresponds to event F, respectively.

  Beginning at start step 810, the process proceeds to user computer request step 820. At step 820, user computer 115 requests specific content and then proceeds to send content manager step 830. At step 830, the content manager 124 sends the requested content to the user computer 115 and proceeds to the next step 840 where the user computer 115 requests a license. At step 850, offer manager 122 sends the license to user computer 115 and proceeds to step 860 where there is a content requested by user computer 115 and a corresponding license. If they are found, the process proceeds to step 870 and calls the appropriate application for the content requested by the user manager 320. The process proceeds to end step 880.

A. User Requests Content In one embodiment, at step 820, the user uses browser 310 to view a web page. The user then requests content for viewing, printing, copying, or playing. In another embodiment, a user requests content by attempting to access a content cell 210 that has been sent using email or stored on a storage unit such as a CD-ROM, floppy disk, etc. You can also In another embodiment, content may be requested without the user's knowledge. For example, when a particular computer application is executed, the computer program application can automatically send a request for content to the content manager 124.

B. Content Manager Sends Content Cell With respect to step 830, content manager 124 finds the requested content and prepares the content for presentation to user computer 115. The flowchart corresponding to step 830 is further shown in FIG. Beginning at start step 830, the process proceeds to step 910 where the content manager 124 receives a content request. Proceeding to step 920, the content manager 124 creates a content cell 210 containing the requested content, and proceeding to step 930, the content manager 124 sends the content cell 210 to the user browser 310 of the user computer 115.

  In this embodiment, the content manager 124 creates the content cell 210, but in another embodiment, the content manager 124 may locate a pre-made content cell 210 in the database. As described above, another module may create and store a general content cell 210, and another module such as the content manager 124 may access the content cell 210 and transmit it to the user as requested. Further, the content cell 210 may be drawn from a disk, a CD-ROM, and other storage devices. After the content manager 124 creates the content cell 210 at step 920, the content manager 124 sends the content cell 210 to the user's browser 310 at step 930 and then proceeds to an end step 940. In another embodiment, the content cell 210 may be sent directly to the user manager 320 instead of the user browser 310.

C. FIG. 10 shows a flowchart corresponding to step 840 in which the user computer 115 requests a license. Beginning at start step 840, the process proceeds to step 1010 where the user browser 310 receives the content cell 210 and passes the content cell 210 to the user manager 320. The user manager 320 opens the content 210 at step 1020 and proceeds to step 1030 where the user manager 320 verifies that the content cell 210 is authentic. As described above, in one embodiment, the content cell 210 includes a signature and a public certificate so that the user manager 320 can use the public certificate to verify that the sender and creator of the content cell 210 are authentic. It has become. Proceeding to step 1040, the user manager 320 looks for a license for the content cell 210. If a license is found at step 1050, the process proceeds to end step 1090 and goes to step 870 where the user manager 320 calls the application and content. However, if no license is found, the process proceeds to step 1070 where the user manager 320 stores the content cell information in the content database 334 and proceeds to step 1080 where the user computer 115 requests a license. In one embodiment, user manager 320 causes user browser 310 to send a license request to content manager 124 and proceeds to end step 1090.

D. FIG. 11 shows a flowchart corresponding to step 850 in which the offer manager 122 sends a license to the user computer 115. Beginning at start step 850, the process proceeds to step 1110 where the offer manager 122 receives a license request and proceeds to step 1120 where the offer manager 122 uses the user browser 310 to allow the user to meet the requirements for issuing a license. For example, the user may have to send registration information, mailing information, answer questions, and send credit card information. Sample registration form includes name, last name, email address, business, credit card type, credit card number, expiration date, credit card name, billing address, city name, state name, postal code, country name, password It may come to fill in information such as. Proceeding to step 1130, if the user does not meet the requirements, the process proceeds to end step 1140. However, if the user meets the requirements, the process proceeds to step 1150 and the user manager 320 begins to create the license cell 220. After the license manager 530 creates the license cell 220, the process may proceed to step 1160 where the offer manager 122 may “charge” the license fee to the user computer 115. This billing occurs, for example, if the license issuance requirements include payment by credit card or other account information. In another embodiment, the billing transaction may be processed by other modules, such as a service provider, server, etc. Step 1170, offer manager 122 sends license cell 220 to the user's browser 310 and proceeds to end step 1180.

E. FIG. 12 shows a flowchart corresponding to step 860 in which the user computer 115 finds the content and license. Beginning at start step 860, the process proceeds to step 1210 where the user's browser 310 receives the license cell 220 and passes the license cell 220 to the user manager 320. At step 1220, user manager 320 opens license cell 220 and proceeds to step 1230, where user manager 320 verifies that license cell 220 is authentic. As described above, the license cell 220, in one embodiment, includes a signature and a public certificate, and the user manager 320 can use the license cell 220 to verify that the sender and creator are authentic. Proceeding to step 1240, the user manager 320 stores the license cell information in the user computer 115. In one embodiment, license manager 530 stores license cell information in license database 332. In other embodiments, other storage methods may be used. Proceeding to step 1250, the process verifies that the user still wants a license. If the user's answer is “no”, the process proceeds to end step 1255. If the user still wants a license, the process proceeds to step 1260 where the user computer 115 re-requests the license and proceeds to step 1270 where the user computer 115 looks for the license and proceeds to step 1280. At step 1280, user computer 115 searches for content and proceeds to step 1290.

F. User Manager Calls Application If user manager 320 has the license and content, user manager 320 calls the appropriate application for the requested content at step 870 and proceeds to end step 880. The user manager 320 allows appropriate access to the content according to the rules. For example, if the requested content is a song in MP3 format and by convention, the user computer 115 can play the first 20 seconds of the song, the user manager 320 may send an MP3 player on the user computer 115 along with the requested song. And play the song for 20 seconds. Various types of content access methods are possible depending on the contract, for example, viewing a part of the content, viewing the entire content, copying a part of the content, copying the entire content, etc. A type of printing a part of the content, printing the entire content only once, or printing the entire content twice may be possible.

G. Other Embodiments In one embodiment, content can be requested before the license is generated, but in other embodiments, the license may be generated or requested before the content is generated or requested. For example, a user can buy a license that subscribes to all new articles in a particular issue. The user receives a license for content that has not yet been generated. Furthermore, one content may relate to one or more licenses, and one license may correspond to one or more content.

  In one embodiment, the content manager 124 may send a content location cell to the user. The content location cell provides the user with information on where the content is. The user may still need the content cell 210 when ready to access the content. For example, assume that a user wants to watch a video file of a two-hour movie. Rather than sending the entire content at once, a license management system module, such as content manager 124, may send a content location cell to the user that can access the requested content location.

The content location cell may be similar to the content cell, but includes not the content itself but the encrypted content location information, such as a URL. Content location cells may be generated by the content manager 124 or other modules. When the user receives the content location cell, the user may request a license to access the content location. After the user receives a license to access a particular location, the user may access the content location. This access allows the user to view, for example, content fragments and access advertisements. The user may request access to the content itself, or may request an appropriate license if necessary.
V. Creating a Cell FIGS. 13 and 14 show one embodiment for creating a content cell 210 and a license cell 220. As described above, in another embodiment, another module may create the cell, and the cell may be created using other techniques.

A. Making a Content Cell A flow chart corresponding to an embodiment of the composition of the content cell 210 is shown in FIG. At start step 920, the process proceeds to step 1310 where the content manager 124 extracts the contract 612. As described above, the contract 612 informs what type of license and / or user can access various types of data and what is required to access the content. The rules 612 may be stored in the rules database, may be listed as text documents and / or programs, and the content manager 124 only needs to be able to determine which rules 612 are applied to the selected content.

  Proceeding to step 1320, the content manager 124 obtains content from the content database 438. In one embodiment, all content is stored in one database, and the content manager 124 can search the database and retrieve the requested content.

  Proceeding to step 1330, the content manager 124 encrypts the content. Various known techniques may be used as the encryption technique. However, as described above, in one embodiment, the content manager 124 encrypts the content using a symmetric key and encrypts the symmetric key using the offer manager's public key. When the encrypted content 614 and the encrypted symmetric key are sent to the user computer 115, the user computer 115 cannot decrypt the content and cannot decrypt the symmetric key until it has an appropriate license.

  Proceeding to step 1340, the content manager 124 generates a cell header 616. The cell header 616 may include a unique identifier of the content, the store from which the content was drawn, descriptive text, expiration date information, and other information.

  Proceeding to step 1350, the content manager 124 adds the extracted contract 612, the encrypted multi-content 614, the cell header 616, and its own public certificate 618 to the content cell 210. At step 1360, content manager 124 “signs” content cell 210. As described above, a module that signs the content cell 210 must also include the module's public certificate in the cell. Accordingly, at step 1350, the content manager 124 includes the public certificate and allows the recipient to verify that it was the content manager 124 that generated and sent the content cell 210. After the content manager 124 signs the content cell 210, the process proceeds to an end step 1370.

B. Creating a License Cell A flow chart corresponding to one embodiment of composing the license cell 220 is shown in FIG. In start step 1150, the process proceeds to step 1410 where the license manager 530 extracts the contract 712. As described above, the contract 712 informs what type of license and / or user has access to various types of data and what is required to access the content. The rules 712 may be stored in a rules database, or may be listed as text documents and / or programs, as long as the license manager 530 can decrypt and determine which rules 712 apply.

  Proceeding to step 1420, the license manager 530 generates a license. Proceeding to step 1430, the license manager 530 encrypts the license. Various known techniques can be used as the encryption technique. However, as described above, in one embodiment, the license manager 530 encrypts the license using a symmetric key and then encrypts the symmetric key using the user's public key. When the encrypted license 714 and the encrypted symmetric key are sent to the user computer 115, the user computer can decrypt the license.

  Proceeding to step 1440, the license manager 530 generates a cell header 716. The cell header 716 may include a unique identifier for the license cell, a unique identifier associated with the content, the store from which the content was drawn, descriptive text, information about the expiration date, and other information.

  Proceeding to step 1450, the license manager 530 adds the extracted contract 712, the encrypted license 714, the cell header 716, and its own public certificate 718 to the license cell 220. At step 1460, license manager 530 “signs” license cell 220. As described above, the module that signs the license cell 220 must include the module's public certificate in the cell. Accordingly, at step 1460, the license manager 530 includes the public certificate and allows the recipient to verify that the license manager 530 has generated and transmitted the license cell 220. After the license manager 530 signs the license cell 220, the process proceeds to an end step 1470.

In one embodiment, license manager 530 stores a copy of license cell information in license database 547 for later tracking of issued licenses.
VI. CONCLUSION While certain preferred embodiments of the invention have been described, these embodiments have been presented by way of example only and are not intended to limit the scope of the invention. Accordingly, the breadth and scope of the present invention should be determined only by the claims and their equivalents.

  In addition, the following additional notes are described in relation to the above embodiment.

(Supplementary note 1) A method of permitting access to a data object,
Create a data object cell,
Sending the data object cell to the computer over the network;
Generating a license object cell related to the data object cell;
Sending the license object cell to the computer over the network;
A method of permitting access to the data object cell based on information of the related license object cell.

    (Supplementary note 2) The method according to supplementary note 1, further comprising receiving a user request for a data object cell.

    (Supplementary note 3) The method according to supplementary note 1, further comprising receiving a user request for a license object.

    (Supplementary note 4) The method according to supplementary note 1, wherein allowing access to the object cell includes verifying that a license object cell related to the data object cell is on the computer.

    (Supplementary note 5) The method according to supplementary note 1, wherein the data object cell includes at least a data control element and a data object.

    (Supplementary note 6) The method according to supplementary note 5, wherein at least the data object is encrypted.

    (Supplementary note 7) The method according to supplementary note 1, wherein at least a part of the license object cell is encrypted.

(Supplementary note 8) The method according to supplementary note 1, wherein a data location cell related to the data object cell is further drawn,
Sending the data location cell to the computer over the network;
A method of permitting access to the data location cell based on information of related license object cells.

(Supplementary note 9) A method of permitting access to a data object,
Draw data object cell,
Sending the data object cell to the computer over the network;
Draw a license object cell related to at least one data object cell,
Sending the license object cell to the computer over a network;
A method of permitting access to the data object cell based on information of a related license object cell.

  (Supplementary note 10) The method according to supplementary note 9, further comprising receiving a user request for a data object cell.

    (Supplementary note 11) The method according to supplementary note 9, further comprising receiving a user request for a license object.

    (Supplementary note 12) The method according to supplementary note 9, wherein granting access to the data object cell includes verifying that the computer has a license object cell related to the data object cell.

    (Supplementary note 13) The method according to supplementary note 9, wherein the object cell includes at least one data control element and a data object.

    (Supplementary note 14) The method according to supplementary note 13, further comprising: encrypting at least the data object.

    (Supplementary note 15) The method according to supplementary note 9, wherein at least a part of the license object cell is encrypted.

    (Supplementary note 16) The method according to supplementary note 9, further comprising generating a data object cell.

    (Supplementary note 17) The method according to supplementary note 9, further comprising generating a license object cell.

(Supplementary note 18) The method according to supplementary note 9, wherein the data object cell and the license object cell are related by at least one unique identifier.
(Supplementary note 19) A method of managing data objects,
Send a request to the first computer for a data object;
Receiving a data object cell related to the requested data object from the first computer;
Sending a request for a license object related to the data object cell to a second computer;
Receiving a license object cell related to the requested license object from the second computer;
A method of permitting access to the data object cell based on information of the related license object cell.

    (Supplementary note 20) The method according to supplementary note 19, wherein the first computer and the second computer are the same computer.

(Supplementary note 21) A method of managing data objects,
Receives a request for a data object from a network node,
Identifying a data object cell associated with the requested data object;
Sending the data object cell to the network node;
Access to the data object cell requires an associated license object cell.

(Supplementary note 22) The method according to supplementary note 21, further comprising:
Accessing a license object cell related to the data object cell;
Sending the license object cell to the network node;
A method wherein the license object cell permits at least access to the data object cell.

(Supplementary note 23) A method of managing data objects,
Receive a request for a license object from a network node,
Accessing a license object cell related to the requested license object;
Sending the license object cell to the network node;
A method wherein the license object cell permits access to at least one data object cell.

(Appendix 24) Network
A user node coupled to the network is provided, the user node including a user manager module, requesting the network for data objects and related license objects;
A content manager node coupled to the network is provided, and the content server node receives a request for a data object from the network, retrieves the requested data object, and responds to the request for a data object from the network. ,
A license manager node coupled to the network is provided, and the content server node receives a request for a related license object from the network, retrieves the requested related license object, and retrieves the related license object from the network. A network that responds to the request to seek.

(Supplementary Note 25) Network
A content manager node is provided that responds to requests for provision of data objects,
A license manager node is provided that responds to a request for provision of a license object related to at least one data object;
A network provided with a user node that provides access to the data object with the associated license object.

(Supplementary note 26) The network according to supplementary note 25, wherein the user node further provides a user interface for requesting one or more data objects to the user,
Issue a request for the selected data object from the content manager node;
A network that determines whether the user node has access to data objects and license objects.

(Supplementary note 27) A system for managing data objects,
A content module is provided for receiving a request for a data object, retrieving the data object, and transmitting the requested data object;
A system provided with a license module that receives a request for a license object related to the data object, extracts a license object related to the data object, and transmits the requested license object.

(Supplementary note 28) A system for managing data objects,
Means for managing the data objects are provided;
Means for managing the license object is provided;
A system provided with means for allowing access to said data object based at least on the license object concerned.
(Supplementary note 29) A method of permitting access to a data object,
Data object cell extraction means are provided,
A data object cell transmission means is provided;
License object cell withdrawal means is provided,
A license object cell transmission means is provided;
A method provided with access permission means.

(Supplementary Note 30) A data object cell,
Data object cell with data control elements and data objects.

    (Supplementary note 31) The data object cell according to supplementary note 30, wherein the data object is encrypted.

    (Supplementary note 32) The data object cell according to supplementary note 30, further comprising a cell header.

    (Supplementary note 33) The data object cell according to supplementary note 30, further comprising at least one public certificate.

    (Supplementary note 34) The data object cell according to supplementary note 30, further comprising at least one signature.

(Supplementary Note 35) A license object cell,
A license object cell in which a license control element and a license object are provided.

    (Supplementary note 36) The license object cell according to supplementary note 30, wherein the license object is encrypted.

    (Supplementary note 37) The license object cell according to supplementary note 30, further comprising a cell header.

    (Supplementary note 38) The license object cell according to supplementary note 30, further comprising at least one public certificate.

    (Supplementary note 39) The data object cell according to supplementary note 30, further comprising at least one signature.

(Appendix 40) A database schema,
User data and
Content data and
A database schema that relates license data.

    (Supplementary note 41) The database schema according to supplementary note 40, wherein the user data includes group data.

(Supplementary note 42) The database schema according to supplementary note 40, wherein the content data includes issuer data,
Publication data is provided,
A database schema with article data.

    (Supplementary note 43) The database schema according to supplementary note 40, wherein the content data is a database schema provided with subscription data.

    (Supplementary note 44) The database schema according to supplementary note 40, wherein the content data is a database schema provided with billing data.

    (Supplementary note 45) The database schema according to supplementary note 40, wherein the license data is a database schema provided with issued license data.

Appendix A

ＡｃｔｉｖａｔｅｄＦｗｉｄｓテーブル
ユーザによるメディアセンターのすべての成功したインストレーションを登録する。各ユーザに活性化したフレームワークを割当てる。現在、ユーザと活性化したフレームワークの間には一対一の関係がある。この関係を変更して、一人のユーザが複数の活性化したフレームワークを持てるようにする計画がある。
フレームワークを活性化する前に、まずペンディングしなければならない。活性化する時、ＰｅｎｄｉｎｇＦｗｉｄｓテーブル中のフレームワークに関するすべての情報をＡｃｔｉｖａｔｅｄＦｗｉｄｓテーブルにコピーする。バックエンドは、この時、ユーザが誰で、どのフレームワークが使われるか分かる。

ActivatedFwids table Registers all successful installations of media centers by users. Assign an activated framework to each user. Currently there is a one-to-one relationship between users and activated frameworks. There are plans to change this relationship so that a single user can have multiple activated frameworks.
Before activating the framework, you must first make a pending. When activated, all information about the framework in the PendingFwids table is copied to the ActivatedFwids table. The backend knows who the user is and what framework is used at this time.

フィールドの説明
ＴｉｍｅＳｔａｍｐ
フレームワークが活性化された日付と時間
ＦｒａｍｅｗｏｒｋＩｄ
フレームワークユニーク識別子（例：ｆｗｉｄ０００１．００００００１１０１）。現在、一フレームワークに一ユーザアカウントＩｄが対応している。ユーザアカウントＩｄに多数の活性化されたフレームワークＩｄを許容する計画がある。
ＣｅｌｌＩｄ
フレームワークＩｄセルをユニークに識別する文字ストリング。フレームワークＩｄセル、コントラクトセル、コンテントセルを含む各セルはユニークなＩｄを有する。
Ｅｍａｉｌ
メディアセンターをインストールした時にユーザが入力した電子メールアカウント。
ＲｅｑｕｅｓｔＩｄ
どのフレームワークから来たものかを検証する。さらにセキュリティーを高める（即ち、バックエンドが応答しない場合、要求Ｉｄを活性化し送信するよう試みる。ハッカーを予防するために使う）。
ＵｓｅｒＨｏｓｔ
今は使用していない。
ＲｅｍｏｔｅＨｏｓｔ
今は使用していない。
Ａｕｔｈｅｎｔｉｃａｔｉｏｎ
ブール値。偽は電子メールアドレスが認証されていないことを表す。ユーザがバックエンドの確認電子メールを受信し、登録を完了すためにリンクをクリックしたことを示す。このプロセスは、ユーザが実際に電子メールを受信したことがバックエンドに分かるので、電子メールアドレスが正しいものであることを認証、または検証できる。
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
ユーザと同じ。
ＶａｌｉｄＴｈｒｏｕｇｈ
フレームワークＩｄの有効期限（例：６ヶ月、１年等）
Ａｄｍｉｎｉｓｔｒａｔｏｒｓテーブル
管理業務を行う権限を有する特別なユーザのリストを含む。このリスト中のアドミニストレータはユーザとは何の関係もない。アドミニストレータとしてログインすると、権限を有するメディアＤＮＡ社員及び発行者はナレッジスターのデータを管理することができる。

Field Description TimeStamp
Date and time the framework was activated FrameworkworkId
Framework unique identifier (example: fwid0001.0000001101). Currently, one user account Id corresponds to one framework. There are plans to allow a large number of activated framework Id user account Id.
CellId
A character string that uniquely identifies the framework Id cell. Each cell, including the framework Id cell, contract cell, and content cell, has a unique Id.
Email
The email account entered by the user when installing the Media Center.
RequestId
Verify which framework came from. Further increase security (ie, if the backend does not respond, try to activate and send the request Id, used to prevent hackers).
UserHost
Not used now.
RemoteHost
Not used now.
Authentication
Boolean value. False indicates that the e-mail address is not authenticated. Indicates that the user received a back-end confirmation email and clicked on the link to complete registration. This process can authenticate or verify that the email address is correct because the backend knows that the user actually received the email.
UserAccountId
Same as user.
ValidThrough
Expiration date of framework Id (eg 6 months, 1 year, etc.)
Administrators table Contains a list of special users who have the authority to perform management tasks. The administrators in this list have nothing to do with the user. When logged in as an administrator, authorized media DNA employees and publishers can manage knowledge star data.

フィールドの説明
Ｎａｍｅ
アドミニストレータの名前またはログインアカウント。
Ｐａｓｓｗｏｒｄ
アドミニストレータアカウントにアクセスするためのパスワード。
Ｅｍａｉｌ
アドミニストレータの電子メールアドレス。アドミニストレータと電子的に通信可能である（例：レポート、統計の送信）。
Ｐｈｏｎｅ
アドミニストレータの電話番号。
ＰｕｂｌｉｓｈｅｒＩｄ
このアドミニストレータが管理する権限を持つ発行物。
Ｔｙｐｅ
このアドミニストレータのタイプを定義する。現在はレギュラーとスーパーの２タイプのみがある。レギュラーアドミニストレータは指定された発行者とその発行物のみ取り扱える。スーパーアドミニストレータにはこの制限は無い。言い換えれば、スーパーアドミニストレータになるということは、ＰｕｂｌｉｓｈｅｒＩｄコラムを無効とすることである。このコラムで有効な値はＲとＳである。
ＭａｎａｇｅＣｏｒｐＡｃｃｏｕｎｔｓ
このアドミニストレータがコーポレートアカウントを管理する権限を有するかを示す。
ＭａｎａｇｅＰｒｏｍｏＥｍａｉｌ
このアドミニストレータが販促電子メールを管理する権限を有するかを示す。
ＡｒｔｉｃｌｅＳｙｎｃテーブル
ダイナミクスデータベース上でアップデートすべきＤＯＩ（アーティクル）の待ち行列を表す。ダイナミクスデータベース中のＤＯＩリストをナレッジスター上のＤＯＩリストと同期するためである。

Field Description Name
Administrator name or login account.
Password
Password for accessing the administrator account.
Email
Administrator email address. Can communicate electronically with the administrator (eg sending reports, statistics).
Phone
Administrator phone number.
PublisherId
Publications authorized by this administrator.
Type
Define the type of this administrator. Currently there are only two types, regular and super. Regular administrators can only handle designated issuers and their publications. Super administrators do not have this restriction. In other words, becoming a super administrator is invalidating the PublisherId column. Valid values in this column are R and S.
ManageCorpAccounts
Indicates whether this administrator has authority to manage corporate accounts.
ManagePromoEmail
Indicates whether this administrator has authority to manage promotional emails.
Represents a queue of DOIs (articles) to be updated on the ArticleSync table dynamics database. This is because the DOI list in the dynamics database is synchronized with the DOI list on the knowledge star.

フィールドの説明
Ｄｏｉ
同期する必要があるアーティクルのＤｏｉ。
Ｏｐｅｒａｔｉｏｎ
データベース間でアーティクルを同期するには何をすべきかを説明する。
現在、作成と更新という二つのＯｐｅｒａｔｉｏｎが可能である。有効な値はＣとＵである。
Ｓｔａｔｕｓ
Ｏｐｅｒａｔｉｏｎの状態を記述する。未決定（Ｐｅｎｄｉｎｇ）、進行中、エラーの３つの値が定義されている。有効な値はＰ、Ｉ、Ｅである。
ＥｒｒｏｒＲｅａｓｏｎ
同期中にエラーが発生した場合、ＳｔａｔｕｓがＥに設定され、エラーメッセージがこのフィールドに入る。
ＢｉｌｌａｂｌｅＳｕｍｍａｒｉｅｓテーブル
特定のフレームワーク（ユーザ）によってなされたすべての取引の要約をリストし、そのアカウントへの課金情報を有する。一つのエントリーはＢｉｌｌａｂｌｅＴｒａｎｓａｃｔｉｏｎｓテーブル中のたくさんの個別取引の合計である。

Field Description Doi
Article Doi that needs to be synchronized.
Operation
Explain what to do to synchronize articles between databases.
Currently, two operations, creation and update, are possible. Valid values are C and U.
Status
Describes the operation status. Three values are defined: Pending, In Progress, and Error. Valid values are P, I, E.
Error Reason
If an error occurs during synchronization, Status is set to E and the error message is in this field.
Billable Summaries Table Lists a summary of all transactions made by a particular framework (user) and has billing information for that account. One entry is the sum of many individual transactions in the Billable Transactions table.

フィールドの説明
ＴｒａｎｓａｃｔｉｏｎＩｄ
ユーザの一群の取引（一つまたは多数の）をユニークに識別する。
ＴｉｍｅＳｔａｍｐ
取引が発生した日付と時刻。
ＡｃｃｏｕｎｔＩｄ
取引を行ったユーザ。
ＦｉｒｓｔＮａｍｅ
ユーザのファーストネーム。
ＬａｓｔＮａｍｅ
ユーザのラストネーム。
Ｃｏｍｐａｎｙ
ユーザの勤務先。このフィールドは空欄でも良い。
Ｅｍａｉｌ
ユーザの電子メールアドレス。
ＡｃｃｏｕｎｔＳｔａｔｕｓ
ユーザアカウントの状態を定義する。ユーザアカウントには不活性（０）であるか、又はゲスト使用（１）、メンバー使用（２）、グループ使用（３）の状態がある。不使用（４）とすることもできる。
ＳｅｒｖｉｃｅＬｅｖｅｌ
将来、ユーザによって異なったレベルのサービスを提供するためのもの（例えば、ゴールド、シルバー、エリート等）。現在はゲストとメンバーという二つのレベルのみ。
ＮａｍｅＦｏｒＢｉｌｌｉｎｇ
このユーザに対する課金業務のための名前。
ＢｉｌｌｉｎｇＡｄｄｒｅｓｓ１
請求先住所フィールドＮｏ．１
ＢｉｌｌｉｎｇＡｄｄｒｅｓｓ２
請求先住所フィールドＮｏ．２
Ｃｉｔｙ
請求先住所（都市）。
Ｓｔａｔｅ
請求先住所（州）。
ＰｏｓｔａｌＣｏｄｅ
請求先郵便番号。
Ｃｏｕｎｔｒｙ
請求先住所（国）。
ＣａｒｄＴｙｐｅ
請求用クレジットカードタイプ（ビザ、マスター等）。
ＥｎｃｒｙｐｔｅｄＣａｒｄＮｕｍｂｅｒ
暗号化されたクレジットカード番号。セキュリティのために暗号化されている。
ＥｎｃｒｙｐｔｉｏｎＴｙｐｅ
クレジットカード番号を暗号化するのに使われた暗号タイプ。使えるのはＢａｓｉｃ（１）、ＲＳＡ（２）、ＳｉｍｐｌｅＨａｓｈ（３）である。
ＣａｒｄＥｘｐｉｒａｔｉｏｎＭｏｎｔｈ
クレジットカードの有効期限（月）。
ＣａｒｄＥｘｐｉｒａｔｉｏｎＹｅａｒ
クレジットカードの有効期限（年）。
ＣｏｕｎｔＯｆＴｒａｎｓａｃｔｉｏｎｓ
この要約書でグループ化された取引数。
Ａｍｏｕｎｔ
この要約書でグループ化された取引の金額。
Ｃｏｍｍｅｎｔ
一般的なコメントフィールド。ほとんど使わない。
ＢｉｌｌａｂｌｅＴｒａｎｓａｃｔｉｏｎｓテーブル
ナレッジスターで発生した課金可能な個々の取引をリストする。契約を発行するたびに取引が発生する。

Field Description TransactionId
Uniquely identifies a group of transactions (one or many) of a user.
TimeStamp
The date and time when the transaction occurred.
AccountId
The user who made the transaction.
FirstName
The user's first name.
LastName
The user's last name.
Company
The user's work location. This field may be blank.
Email
The user's email address.
AccountStatus
Define user account status. The user account is inactive (0) or has guest usage (1), member usage (2), and group usage (3) status. It can also be set as non-use (4).
ServiceLevel
To provide different levels of service for different users in the future (eg gold, silver, elite, etc.). Currently there are only two levels: guests and members.
NameForBilling
The name for billing for this user.
Billing Address 1
Billing address field No. 1
Billing Address 2
Billing address field No. 2
City
Billing address (city).
State
Billing address (state).
PostalCode
Billing postal code.
Country
Billing address (country).
CardType
Billing credit card type (visa, master, etc.).
EncryptedCardNumber
Encrypted credit card number. Encrypted for security.
EncryptionType
The encryption type that was used to encrypt the credit card number. Basic (1), RSA (2), and SimpleHash (3) can be used.
CardExpirationMonth
Credit card expiration date (months).
CardExpirationYear
Credit card expiration date (years).
CountOfTransactions
Number of transactions grouped by this summary.
Amount
Amount of transactions grouped in this summary.
Comment
General comment field. Almost no use.
BillableTransactions Table Lists each chargeable transaction that occurred in the Knowledge Star. A transaction occurs every time a contract is issued.

フィールドの説明。
ＴｒａｎｓａｃｔｉｏｎＩｄ
一ユーザの一群の取引の一部として取引を識別する。
ＴｉｍｅＳｔａｍｐ
このテーブルにエントリーされた日時。一般的には、ユーザが「支払い」ページにおいてクレジットカードへの課金を承諾した時である。
ＴｒａｎｓＴｉｍｅ
取引が発生した日時。ＴｉｍｅＳｔａｍｐに先立つ時間、日数、週数でも良い。一般的にはユーザが各ドキュメントを購入した時である。
Ｄｅｓｃｒｉｐｔｉｏｎ
何の取引かの記述。通常は購入されたアーティクルのタイトルを含み、または紹介文である。
Ｄｏｉ
取引されたアーティクル。
ＡｃｃｏｕｎｔＩｄ
取引したユーザ。
ＦｒａｍｅｗｏｒｋＩｄ
ユーザが使用するフレームワーク識別番号。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
アーティクルが属する発行物。
ＴｒａｎｓＴｙｐｅ
番号によって識別される取引タイプ。有効なタイプは、使用中（０）、導入クレジット（１）、購入（２）、要約（３）である。
Ａｍｏｕｎｔ
取引金額。
Ｃｏｍｍｅｎｔ
取引に関するコメント。通常は空欄である。
ＣｌｉｃｋＴｈｒｏｕｇｈｓテーブル
ユーザが発行されたウェブページに行くのにナレッジスターをクリックするたびにトラッキングする。

Field description.
TransactionId
Identify a transaction as part of a group of transactions for a user.
TimeStamp
The date and time entered in this table. Generally, it is when the user accepts the charge to the credit card on the “payment” page.
TransTime
The date and time when the transaction occurred. The time, days, and weeks prior to TimeStamp may be used. Generally, it is when the user purchases each document.
Description
A description of what the transaction is. Usually contains the title of the purchased article or an introductory text.
Doi
Articles traded.
AccountId
The user who traded.
FrameworkId
Framework identification number used by the user.
PublicationId
The issue to which the article belongs.
TransType
Transaction type identified by number. Valid types are in use (0), introductory credit (1), purchase (2), summary (3).
Amount
Transaction amount.
Comment
Comments about the transaction. Usually blank.
ClickThrows Table Tracks whenever a user clicks on a knowledge star to go to a published web page.

フィールドの説明。
ＴｉｍｅＳｔａｍｐ
クリックスルーされた日時。
ＦｒａｍｅｗｏｒｋＩｄ
クリックスルーしたフレームワーク。後でこのフレームワークを使っているユーザまでトラッキングする。
ＰｕｂｌｉｃａｔｉｏｎＣｏｄｅ
ユーザがクリックスルーし終わった発行物。
ＣｏｎｔｒａｃｔＳｔａｔｓテーブル
バックエンドをとめる時、エグジットする前に、バックエンドが取引数とそれに要した平均時間を記録する。この記録がこのテーブルに保管される。このテーブルはバックエンドスターデータベースの他のテーブルと直接関係は無い。デバッグ及びシステムモニタリングに使用するものである。

Field description.
TimeStamp
Date and time clicked through.
FrameworkId
Click-through framework. Track down to users who use this framework later.
PublicationCode
Publications that the user has clicked through.
When quitting the ContractStats table backend, it records the number of transactions and the average time taken by the backend before exiting. This record is stored in this table. This table is not directly related to other tables in the backend star database. Used for debugging and system monitoring.

フィールドの説明
ＴｉｍｅＳｔａｍｐ
バックエンドが実行を終了した日時。
ＮｕｍｂｅｒＣｏｎｔｒａｃｔｓ
バックエンドが前回初期化されてから今回終了されるまでに、バックエンドにより生成（発行）されたコントラクト数。
ＡｖｅｒａｇｅＴｉｍｅ
コントラクト生成に要した平均時間。この値は契約生成コードの性能をモニターするために使われる。
Ｃｏｍｍｅｎｔ
一般的なコメント。普通、バックエンドが実行終了したとのメッセージを表示する。
ＣｒｅｄｉｔＣａｒｄＮｕｍｂｅｒｓテーブル
各ユーザのクレジットカード番号を暗号化して保管する。クレジットカード番号を暗号化した暗号化のタイプも特定される。

Field Description TimeStamp
The date and time when the backend finished executing.
NumberContracts
The number of contracts generated (issued) by the backend since the last time the backend was last initialized.
AverageTime
Average time taken to generate the contract. This value is used to monitor the performance of the contract generation code.
Comment
General comment. Usually displays a message that the backend has finished executing.
CreditCardNumbers table The credit card number of each user is encrypted and stored. An encryption type obtained by encrypting the credit card number is also specified.

フィールドの説明
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
このカードが使用可能なアカウントを特定する。
ＥｎｃｒｙｐｔｉｏｎＴｙｐｅ
クレジットカード番号を暗号化するのに使用した方法。使用できるのは、Ｂａｓｉｃ（１）、ＲＳＡ（２）、ＳｉｍｐｌｅＨａｓｈ（３）である。
ＥｎｃｒｙｐｔｅｄＣａｒｄＮｕｍｂｅｒ
暗号化されたクレジットカード番号。
ＣｕｒｒｅｎｔＴｒａｎｓａｃｔｉｏｎｓテーブル
取引に関連した情報を保存する。各契約についてＣｕｒｒｅｎｔＴｒａｎｓａｃｔｉｏｎｓテーブルにエントリーがなされる。エントリーは借方または貸方でも良いし、これらのエントリーを消去するものでも良い。ユーザがアーティクルを購入するたびに、ＩｓｓｕｅｄＣｏｎｔｒａｃｔエントリーとＣｕｒｒｅｎｔＴｒａｎｓａｃｔｉｏｎエントリーがなされる。

Field Description UserAccountId
Identify accounts that can use this card.
EncryptionType
The method used to encrypt the credit card number. Basic (1), RSA (2), and SimpleHash (3) can be used.
EncryptedCardNumber
Encrypted credit card number.
CurrentTransactions table Stores information related to transactions. An entry is made in the Current Transactions table for each contract. Entries may be debited or credited, or they may be deleted. Each time a user purchases an article, an IssuedContract entry and a CurrentTransaction entry are made.

フィールドの説明
ＴｉｍｅＳｔａｍｐ
取引のなされた日時。
Ｄｅｓｃｒｉｐｔｉｏｎ
取引対象を説明する。通常、購入されたアーティクルのタイトルを含み、又は紹介クレジットを示す（即ち、購入取引の場合、アーティクルの名称が入力される）。
Ｄｏｉ
取引されたアーティクルである。
ＡｃｃｏｕｎｔＩｄ
ユーザを特定する。
ＦｒａｍｅｗｏｒｋＩｄ
この取引を処理すべきフレームワークを特定する。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
取引されたアーティクルの発行物を特定する。
ＴｒａｎｓＴｙｐｅ
数字で特定された取引タイプ。有効なタイプは未使用（０）、紹介クレジット（１）、購入（２）、要約（３）である。
Ａｍｏｕｎｔ
この取引の金額である。
Ｃｏｍｍｅｎｔ
一般的なコメントフィールド。
ＤＯＩｓテーブル
アーティクル関係の情報が入っている。アーティクルはＤＯＩとしても知られている。各エントリーはナレッジスターで取り扱えるＤＯＩを表す。このテーブルはアーティクルの在庫であり、ユーザがアクセスするだろうすべてのアーティクル、すべてのコンテントセルなどを含む。このテーブルはネーミングサーブレットである。

Field Description TimeStamp
The date and time when the transaction was made.
Description
Explain the transaction target. Usually includes the title of the purchased article or indicates an introductory credit (ie, for a purchase transaction, the name of the article is entered).
Doi
Articles traded.
AccountId
Identify users.
FrameworkId
Identify the framework that should handle this transaction.
PublicationId
Identify the issue of the traded article.
TransType
Transaction type identified by a number. Valid types are unused (0), referral credit (1), purchase (2), and summary (3).
Amount
The amount of this transaction.
Comment
General comment field.
Contains DOIs table article related information. The article is also known as DOI. Each entry represents a DOI that can be handled by a knowledge star. This table is an inventory of articles, including all articles that the user will access, all content cells, etc. This table is a naming servlet.

フィールドの説明
ＴｉｍｅＳｔａｍｐ
ＤＯＩが登録された日時。
Ｔｉｔｌｅ
アーティクルのタイトル。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
このＤＯＩが属する発行物の識別番号。
ＰｕｂｌｉｓｈｅｒＩｄ
このＤＯＩが属する発行者の識別番号。
Ｕｒｌ
アーティクルセルがあるアドレス（例：ｆｉｌｅ：／／／ｄ：￥ｄａｔａＤｉｒｅｃｔｏｒｙ￥ｃｅｌｌｓ￥ｃｏｍ．ｃａｄｃａｍｎｅｔ＿ｃａｄ＿０１８＿０１＿０１．ｍｄｎａ）
Ｐｒｉｃｅ
このアーティクルの価格。
ＶａｌｉｄＦｒｏｍ
このＤＯＩにアクセス可能となる最初の日を示す。アーティクルへのアクセスを制限する。
ＶａｌｉｄＴｈｒｏｕｇｈ
このＤＯＩにいつまでアクセスできるか示す。アーティクルへのアクセスを制限する。
ＣｏｎｔｅｎｔＣｅｌｌ
このＤＯＩで特定されたセルがコンテントセルかどうかを示す。値は真（１）又は偽（０）である。
ＥｍａｉｌＨｉｓｔｏｒｙテーブル
特定のユーザに送信された電子メールをトラッキングする。電子メールがユーザに送信された日付及び使用されたテンプレートも記録される。

Field Description TimeStamp
Date and time when the DOI was registered.
Title
The title of the article.
PublicationId
Identification number of the issue to which this DOI belongs.
PublisherId
Issuer identification number to which this DOI belongs.
Url
Address where the article cell is located (for example, file: ///d:\dataDirectory\cells\com.cadcamnet_cad_018 — 01 — 01.mdna)
Price
The price of this article.
ValidFrom
Indicates the first day on which this DOI can be accessed. Restrict access to articles.
ValidThrough
Indicates how long this DOI can be accessed. Restrict access to articles.
ContentCell
Indicates whether the cell specified by this DOI is a content cell. The value is true (1) or false (0).
Email History Table Tracks email sent to a specific user. The date when the email was sent to the user and the template used were also recorded.

フィールドの説明
ＴｅｍｐｌａｔｅＩｄ
使用した電子メールテンプレート。ＥｍａｉｌＴｅｍｐｌａｔｅｓ．ＴｅｍｐｌａｔｅＩＤへの外部キー。
ＤａｔｅＳｅｎｔ
電子メールが送信された日付。
ＴｏＨｅａｄｅｒ
電子メールが送信された電子メールアカウント。ユーザはこのデータをカスタマープロファイルで変更できるので、実際に使用されたアドレスを記憶させている。
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
電子メールを受信するユーザ。Ｕｓｅｒｓ．ＡｃｃｏｕｎｔＩｄへの外部キーである。
ＥｍａｉｌＴｅｍｐｌａｔｅｓテーブル
このテーブルは、電子メールメッセージを生成するためにシステムが使用できるテンプレートの集まりを収容している。電子メールメッセージを生成するには、システムはデータベースのエントリーからＦｒｏｍＨｅａｄｅｒ、ＳｕｂｊｅｃｔＨｅａｄｅｒ、Ｂｏｄｙを取り、メッセージを組み立てるのに使用する。テンプレートは特定の発行者が保有するか、システムが保有する。

Field Description TemplateId
The email template used. EmailTemplates. Foreign key to TemplateID.
DateSent
The date when the email was sent.
ToHeader
The email account from which the email was sent. Since the user can change this data in the customer profile, the address actually used is stored.
UserAccountId
The user who receives the email. Users. A foreign key to AccountId.
EmailTemplates Table This table contains a collection of templates that the system can use to generate email messages. To generate an email message, the system takes the FromHeader, SubjectHeader, and Body from the database entries and uses them to assemble the message. Templates are owned by a specific issuer or by the system.

フィールドの説明
ＴｅｍｐｌａｔｅＩｄ
この番号によりテンプレートがユニークに特定される。
ＰｕｂｌｉｓｈｅｒＩｄ
このテンプレートを所有する発行者。この欄が０（ゼロ）の場合はシステムテンプレートであることを示す。
Ｎａｍｅ
このテンプレートの名前。この名前は、この発行者が所有するテンプレート中でユニークである。
ＣｒｅａｔｉｏｎＤａｔｅ
テンプレートが作成された日付。
ＳｕｂｊｅｃｔＨｅａｄｅｒ
このテンプレートで電子メールを送信する時のＳｕｂｊｅｃｔライン。
ＦｒｏｍＨｅａｄｅｒ
このテンプレートを使用して送信される電子メールのＦｒｏｍＨｅａｄｅｒを定義する。
Ｂｏｄｙ
このテンプレートを使った電子メールの内容。
ＥｒｒｏｒＬｏｇＤｏｉテーブル
Ｄｏｉ関係のエラーを記録する。エラーが発生した日付、エラーのタイプ、エラーが発行されたフレームワーク（ユーザ）、及び試みられたＤｏｉがこのログに含まれる。

Field Description TemplateId
This number uniquely identifies the template.
PublisherId
The publisher who owns this template. When this field is 0 (zero), it indicates a system template.
Name
The name of this template. This name is unique among templates owned by this issuer.
CreationDate
The date when the template was created.
SubjectHeader
Subject line when sending an email with this template.
FromHeader
Define a FromHeader for emails sent using this template.
Body
Email content using this template.
ErrorLogDoi table Records errors related to Doi. This log includes the date the error occurred, the type of error, the framework (user) in which the error was issued, and the attempted Doi.

フィールドの説明
ＴｉｍｅＳｔａｍｐ
エラーが記録された日付と時刻。
ＥｒｒｏｒＮｕｍｂｅｒ
エラーの内容を記述するエラー番号。頻度が高いＤｏｉエラーは、Ｄｏｉが見つからない（１０１）とＤｏｉが解決されていない（ｕｎｒｅｓｏｌｖｅｄ）（１０２）である。
Ｄｏｉ
このアーティクルに対するアクセスがエラーとなった。
ＦｒａｍｅｗｏｒｋＩｄ
失敗したアーティクルを要求しているフレームワーク。
ＲｅｍｏｔｅＡＤｄｒ
Ｄｏｉエラーが発行されたリモートＩＰアドレス。
ＲｅｍｏｔｅＨｏｓｔ
Ｄｏｉエラーが発行されたリモートホスト名。
ＥｒｒｏｒＬｏｇＦｗｉｄテーブル
ＦｒａｍｅｗｏｒｋＩｄ関連のエラーを記録する。エラーが発生した日付、エラーのタイプ、エラーが発行されたフレームワーク（ユーザ）、試みられたＤｏｉがこのログに含まれる。

Field Description TimeStamp
The date and time when the error was recorded.
ErrorNumber
An error number describing the nature of the error. Doi errors with high frequency are Doi not found (101) and Doi unresolved (102).
Doi
Access to this article resulted in an error.
FrameworkId
A framework requesting a failed article.
RemoteADdr
The remote IP address where the Doi error was issued.
RemoteHost
The name of the remote host where the Doi error was issued.
ErrorLogFwid table Records errors related to FrameworkId. This log includes the date when the error occurred, the type of error, the framework (user) in which the error was issued, and the attempted Doi.

フィールドの説明。
ＴｒａｎｓａｃｔｉｏｎＩｄ
エラーを特定するユニークな取引番号。
ＴｉｍｅＳｔａｍｐ
エラーが記録された日付と時刻。
ＥｒｒｏｒＮｕｍｂｅｒ
エラーを記述する番号。起こりえるエラーは、Ｆｗｉｄが無い（２００１）、フォーマットが良くない（２００２）、未登録（２００３）、アカウントが見つからない（２００４）、活性化されていない（２００５）、期限超過（２００６）である。
ＦｒａｍｅｗｏｒｋＩｄ
エラーに巻き込まれたフレームワーク。
Ｄｏｉ
エラーに巻き込まれたＤｏｉ。
ＲｅｍｏｔｅＡｄｄｒ
エラーに巻き込まれたユーザＩＰアドレス。
ＲｅｍｏｔｅＨｏｓｔ
エラーに巻き込まれたユーザホスト名。
ＥｘｔｒａＴｅｘｔ
一般的なコメント。
ＥｒｒｏｒＬｏｇＦｗｉｄＡｃｔｉｖａｔｉｏｎテーブル
ＦｒａｍｅｗｏｒｋＩｄの活性化に関するエラーを記録する。

Field description.
TransactionId
A unique transaction number that identifies the error.
TimeStamp
The date and time when the error was recorded.
ErrorNumber
A number describing the error. Possible errors are Fwiid missing (2001), bad format (2002), unregistered (2003), account not found (2004), not activated (2005), overdue (2006) .
FrameworkId
A framework involved in an error.
Doi
Doi involved in an error.
RemoteAddr
User IP address involved in the error.
RemoteHost
User host name involved in the error.
ExtraText
General comment.
Error log FwidActivation table Records errors related to the activation of FrameworkId.

フィールドの説明
ＴｉｍｅＳｔａｍｐ
エラーが記録された日付及び時刻。
ＦｒａｍｅｗｏｒｋＩｄ
エラーに巻き込まれたフレームワーク。
ＣｅｌｌＩｄ
エラーを経験したフレームワークのＩＤセルをユニークに特定する文字ストリング。フレームワークＩＤセル、コントラクトセル、コンテントセルも含めて、各セルはユニークなＩＤを持つ。
Ｅｘｐｉｒｅｓ
フレームワークのＩＤセルが期限切れとなる時間。
ＵｓｅｒＨｏｓｔ
このカラムはもう使用しない。
ＲｅｑｕｅｓｔＩｄ
要求番号。
ＲｅｍｏｔｅＡｄｄｒ
ユーザのＩＰアドレス。
ＲｅｍｏｔｅＨｏｓｔ
このカラムはもう使用しない。
ＦｒａｍｅｗｏｒｋＲｅｉｎｓｔａｌｌｓテーブル
ユーザがフレームワークをリインストールしようと試みた回数をカウントし、成功したリインストールに新しいフレームワーク識別番号を割当てる。

Field Description TimeStamp
The date and time when the error was recorded.
FrameworkId
A framework involved in an error.
CellId
A character string that uniquely identifies the framework's ID cell that experienced the error. Each cell, including the framework ID cell, contract cell, and content cell, has a unique ID.
Expires
The time when the framework ID cell expires.
UserHost
This column is no longer used.
RequestId
Request number.
RemoteAddr
The user's IP address.
RemoteHost
This column is no longer used.
FrameReinstalls table Counts the number of times a user has attempted to reinstall a framework and assigns a new framework identification number to a successful reinstallation.

フィールドの説明
ＴｉｍｅＳｔａｍｐ
フレームワークのリインストールが記録された日付。
ＦｒａｍｅｗｏｒｋＩｄ
以前インストールされたフレームワーク。
ＩｎｓｔＦｗｉｄ
リインストールされたフレームワーク。
ＣｈａｉｎＬｅｎｇｔｈ
ユーザが試みたフレームワークのリインストールの数。回数が所定の制限に達したら、そのユーザはそれ以上のリインストールを許されない。
ＲｅｍｏｔｅＵｓｅｒ
このカラムはもう使われていない。
ＲｅｍｏｔｅＡｄｄｒ
フレームワークをリインストールしたユーザのＩＰアドレス。
ＲｅｍｏｔｅＨｏｓｔ
フレームワークをリインストールしたユーザのホスト名。
ＦｗｉｄＣｅｌｌｉｄＮｕｍｂｅｒＧｅｎｅｒａｔｏｒテーブル
ユニークなセル番号を生成するメカニズムである。ユニークなセルＩＤ番号をトラッキングする。このテーブルはナレッジスターデータベースのバックエンドの他のテーブルとは直接的な関係を持たない。

Field Description TimeStamp
Date when the reinstallation of the framework was recorded.
FrameworkId
A previously installed framework.
InstFwid
Reinstalled framework.
ChainLength
Number of framework reinstalls attempted by the user. If the number of times reaches a predetermined limit, the user is not allowed to reinstall further.
RemoteUser
This column is no longer used.
RemoteAddr
The IP address of the user who reinstalled the framework.
RemoteHost
The host name of the user who reinstalled the framework.
FwidCellidNumberGenerator table is a mechanism for generating a unique cell number. Track unique cell ID numbers. This table has no direct relationship with other tables in the Knowledge Star database back end.

フィールドの説明
ＮｅｘｔＣｅｌｌｉｄＮｕｍｂｅｒ
次のセルの識別番号をトラッキングする。
ＧｒｏｕｐＰｕｂｌｉｃａｔｉｏｎｓテーブル
ユーザグループメンバーによってアクセス可能な発行物を特定する。

Field Description NextCellidNumber
Track the identification number of the next cell.
Group Publications table Identifies publications accessible by user group members.

フィールドの説明
ＧｒｏｕｐＩｄ
グループの識別番号。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
発行物の識別番号。
Ｇｒｏｕｐｓテーブル
グループ関係の情報を保管する。コーポレートアカウントを実現するためグループを使い、コーポレートアカウントを使ってユーザを一つのアカウントにまとめる。

Field Description GroupId
Group identification number.
PublicationId
Issue identification number.
Stores Group table group-related information. Use groups to implement corporate accounts, and use corporate accounts to combine users into one account.

フィールドの説明
ＧｒｏｕｐＩｄ
グループの識別番号。この番号はユニークである。
Ｎａｍｅ
グループの名前。
Ｐａｓｓｗｏｒｄ
このグループのアカウントにアクセスするパスワード。
Ｔｙｐｅ
有効なグループアカウントのタイプ。現在許されているグレープアカウントは、デモアカウントＤ、標準アカウントＳである。それぞれのグループアカウントフィーが支払われれば、デモアカウントのユーザは標準アカウントに昇格される。
ＵｓｅｒＴＴＬ
このグループのグループアカウントが有効な日数。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
このグループのメンバーがアクセスできる発行物。
Ｅｘｐｉｒｅｓ
このグループアカウントの有効期限日。
ＧｒｏｕｐＵｓｅｒｓテーブル
ユーザをグループに結びつける。グループのメンバーを特定する。

Field Description GroupId
Group identification number. This number is unique.
Name
The name of the group.
Password
Password to access this group account.
Type
A valid group account type. Grape accounts currently permitted are a demo account D and a standard account S. If each group account fee is paid, demo account users are promoted to standard accounts.
UserTTL
The number of days this group account is valid.
PublicationId
Publications accessible to members of this group.
Expires
Expiration date for this group account.
GroupUsers table Associate users with groups. Identify group members.

フィールドの説明
ＧｒｏｕｐＩｄ
グループ識別番号。
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
ユーザアカウントの識別番号。
Ｅｘｐｉｒｅｓ
このユーザに関するこのグループアカウントの有効期限日。
ＩｓｓｕｅｄＣｏｎｔｒａｃｔｓテーブル
特定のユーザがアーティクルを入手する時発行された各契約を記録する。フレームワークに契約ごとにエントリーされる（発行されたアーティクルごとに一つの契約）。これらのエントリーは永久に保存され、ユーザが同じアーティクルをダウンロードしても課金されないようにする。

Field Description GroupId
Group identification number.
UserAccountId
User account identification number.
Expires
Expiration date of this group account for this user.
Issued Contracts table Records each contract issued when a particular user obtains an article. Each contract is entered into the framework (one contract for each issued article). These entries are stored permanently so that users are not charged for downloading the same article.

フィールドの説明
ＴｒａｎｓａｃｔｉｏｎＩｄ
ユニークな番号であり、監査に使用するこの取引の識別子である。
ＴｉｍｅＳｔａｍｐ
この取引が登録された日時。
Ｄｏｉ
この契約がなされたアーティクルを示す。
ＣｏｎｔｒａｃｔＵｒｌ
契約セルがある場所を特定する（ディスクをきれいにするため、しばらくすると契約セルは破棄される）。
ＣｅｌｌＩｄ
契約セルをユニークに特定する文字ストリング。フレームワークＩＤセル、契約セル、コンテントセルを含め、各セルはユニークなＩＤを有する。
ＦｒａｍｅｗｏｒｋＩｄ
フレームワークＩＤはＤｏｉで特定されたセルにアクセスできる。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
この契約のＤｏｉがどの発行物に属するか示す。
Ａｍｏｕｎｔ
ユーザが課金された金額。デバッグとトラッキングに使用される。
ＯｎｌｉｎｅＳｕｂｓｃｒｉｐｔｉｏｎＤｅｆｓテーブル
ナレッジスターが管理するオンライン購読に関する定義を含む。

Field Description TransactionId
It is a unique number and an identifier for this transaction used for auditing.
TimeStamp
The date and time when this transaction was registered.
Doi
Indicates the article for which this contract was made.
ContractUrl
Identify where the contract cell is (the contract cell is discarded after a while to clean the disk).
CellId
A character string that uniquely identifies the contract cell. Each cell, including the framework ID cell, contract cell, and content cell, has a unique ID.
FrameworkId
The framework ID can access the cell specified by Doi.
PublicationId
Indicates which issue the Doi of this contract belongs to.
Amount
The amount that the user was charged. Used for debugging and tracking.
OnlineSubscriptionDefs table Contains definitions for online subscriptions managed by the Knowledge Star.

フィールドの説明
Ｄｅｓｃｒｉｐｔｉｏｎ
オンライン購読の特徴を記述する。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
オンライン購読をサポートする発行物。
Ｐｒｉｃｅ
この発行物をオンライン購読するための価格。
ＰｅｎｄｉｎｇＦｗｉｄｓテーブル
ペンディングとなっているすべてのフレームワークをリストする。ペンディングフレームワークは通常ゲストユーザに属する。ＰｅｎｄｉｎｇＦｗｉｄが活性化された時、そのエントリーはこのテーブルからＡｃｔｉｖａｔｅｄＦｗｉｄｓテーブルに「移動」する。

Field Description Description
Describe the characteristics of an online subscription.
PublicationId
Publications that support online subscriptions.
Price
The price for subscribing to this issue online.
List all frameworks that are PendingFwids table pending. The pending framework usually belongs to a guest user. When PendingFwid is activated, its entries “move” from this table to the ActivatedFwids table.

フィールドの説明
ＣｅｌｌＩｄ
フレームワークＩＤセルをユニークに定義する文字ストリング。フレームワークＩＤセル、コントラクトセル、コンテントセルを含め、セルごとにユニークなＩＤを有する。
ＦｒａｍｅｗｏｒｋＩｄ
ペンディングされたフレームワーク。
Ｅｍａｉｌ
ペンディングフレームワークを有するゲストユーザの電子メール。
ＶａｌｉｄＴｈｒｏｕｇｈ
このペンディングフレームワークが有効な期限日。
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
このペンディングフレームワークを持つユーザアカウント。
ＰｒｏｍｏｔｉｏｎａｌＥｍａｉｌテーブル
バックエンドにある販促電子メールごとの特性と特徴を登録する。

Field Description CellId
A character string that uniquely defines the framework ID cell. Each cell has a unique ID including a framework ID cell, a contract cell, and a content cell.
FrameworkId
Pending framework.
Email
Guest user email with a pending framework.
ValidThrough
The expiration date for which this pending framework is valid.
UserAccountId
A user account with this pending framework.
Register the characteristics and characteristics of each promotional email in the PromotionalEmail table backend.

フィールドの説明
ＰｕｂｌｉｃａｔｉｏｎＩｄ
この販促電子メールに関係する発行物。
ＴｅｍｐｌａｔｅＩｄ
この販促電子メールに使用されたテンプレート。
Ｅｎａｂｌｅｄ
この販促電子メールがイネーブルかどうかを示す。
ＥｎａｂｌｅＤａｔｅ
この販促電子メールがイネーブルされた日付。
Ｐｕｂｌｉｃａｔｉｏｎｓテーブル
ナレッジスター上の各発行物に関する情報を有する。一つの発行物が多数のアーティクル又はＤＯＩを含んでも良い。

Field Description PublicationId
Publications related to this promotional email.
TemplateId
The template that was used for this promotional email.
Enabled
Indicates whether this promotional email is enabled.
EnableDate
Date when this promotional email was enabled.
Information about each publication on the Publications table knowledge star. An issue may contain multiple articles or DOIs.

フィールドの説明
ＰｕｂｌｉｃａｔｉｏｎＩｄ
各発行物のユニークな番号。内部的に発行物を特定する。
Ｓｔａｔｕｓ
発行物の状態は「ａｃｔｉｖｅ」又は「ｉｎａｃｔｉｖｅ」である。
ＰｕｂｌｉｃａｔｉｏｎＣｏｄｅ
発行物を特定する短いコード、通常は３文字のコードである（例：ｃｓｎ、ｏｌｒ、又はｃａｄ）。
ＲｅｓｏｕｒｃｅＦｉｌｅ
この発行物があるファイルを示す（例：ｃ：￥ｂａｃｋ￥ｐｒｏｐｅｒｔｉｅｓ／ＡＴＣｏｎｔｅｎｔＣｅｌｌ．ｐｒｏｐｅｒｔｉｅｓ）。
ＰｕｂｌｉｓｈｅｒＩｄ
この発行物を所有する発行者。
Ｄｏｍａｉｎ
この発行物の発行者ドメイン（例：ｃｏｍ．ｇ２ｎｅｗｓ、ｃｏｍ．ｃａｄｃａｍｎｅｔなど）
Ｎａｍｅ
発行物の名称。
ＣｏｎｔｅｎｔＣｅｌｌＥｘｔｅｎｓｉｏｎ
この発行物のコンテントのセルフォーマット（例：ＭＤＮＡ、ＸＤＮＡ）
ＵｒｌＨｏｍｅＰａｇｅ
この発行物のウェブアドレス（例：ｈｔｔｐ：／／ｗｗｗ．ｇ２ｎｅｗｓ．ｃｏｍ／ｃｓｎｉｎｄｅｘ．ｈｔｍｌ）。
ＩｎｔｒｏＣｒｅｄｉｔ
この発行物からアーティクルにアクセスするユーザに提供される紹介クレジット。金額はＵＳドルである。
ＤｅｆａｕｌｔＰｒｉｃｅ
この発行物のアーティクルのデフォルト価格。金額はＵＳドルである。
ＦｒｅｅＡｒｔｉｃｌｅｓ
ユーザに提供される無料アーティクルの数。
ＰｅｒｍｉｔＰｒｉｎｔｉｎｇ
この発行物のアーティクルのプリントが許されているかどうかを示す。有効な値は真（１）又は偽（０）である。
ＰｅｒｍｉｔＣｏｐｙｉｎｇ
この発行物のアーティクルのコピーが許されているかどうかを示す。有効な値は真（１）又は偽（０）である。
Ｐｕｂｌｉｓｈｅｒｓテーブル
ナレッジスターにコンテントを有する各発行者からの情報を含む。一発行者は多数の発行物を有していても良い。

Field Description PublicationId
A unique number for each issue. Identify issues internally.
Status
The status of the issue is “active” or “inactive”.
PublicationCode
A short code identifying the issue, usually a three letter code (eg csn, olr or cad).
ResourceFile
A file in which this publication is located is indicated (for example, c: \ back \ properties / ATContentCell.properties).
PublisherId
The issuer who owns this issue.
Domain
Issuer domain of this issue (eg com.g2news, com.cadcamnet, etc.)
Name
The name of the issue.
ContentCellExtension
Cell format of the content of this publication (eg MDNA, XDNA)
UrlHomePage
Web address of this issue (eg http://www.g2news.com/csnindex.html).
IntroCredit
Referral credit provided to users accessing articles from this publication. The amount is US dollars.
DefaultPrice
The default price for articles in this issue. The amount is US dollars.
FreeArticles
The number of free articles provided to the user.
PermitPrinting
Indicates whether printing of articles for this publication is allowed. Valid values are true (1) or false (0).
PermitCopying
Indicates whether a copy of an article for this issue is allowed. Valid values are true (1) or false (0).
Contains information from each publisher who has content in the Publishers table knowledge star. An issuer may have multiple publications.

フィールドの説明
ＰｕｂｌｉｓｈｅｒＩｄ
発行者のユニークな識別番号。
Ｓｔａｔｕｓ
発行物の状態は「ａｃｔｉｖｅ」又は「ｉｎａｃｔｉｖｅ」である。
ＰｕｂｌｉｓｈｅｒＮａｍｅ
発行者の名称。
ＤｅｆａｕｌｔＰｒｉｃｅ
この発行物のアーティクルのデフォルト価格。金額はＵＳドルである。
ＴｒａｎｓａｃｔｉｏｎＮｕｍｂｅｒＧｅｎｅｒａｔｏｒテーブル
ユニークな取引ＩＤ番号が生成されるメカニズムである。ユニークな取引ＩＤ番号をトラッキングする。このテーブルはナレッジスターデータベースのテーブルとは直接的な関係を持たない。

Field Description PublisherId
The issuer's unique identification number.
Status
The status of the issue is “active” or “inactive”.
PublisherName
The name of the issuer.
DefaultPrice
The default price for articles in this issue. The amount is US dollars.
TransactionNumberGenerator table is a mechanism by which a unique transaction ID number is generated. Track unique transaction ID numbers. This table has no direct relationship with the table in the Knowledge Star database.

フィールドの説明
ＮｅｘｔＴｒａｎｓａｃｔｉｏｎＮｕｍｂｗｅｒ
次の取引番号を保管する。
ＵｓｅｒＢａｌａｎｃｅｓテーブル
ユーザのクレジット及び特定の発行物に対する課金の記録を保管する。ユーザがアクセスした発行物に関するエントリーがある。

Field Description NextTransactionNumber
Store the next transaction number.
UserBalances Table Stores user credits and billing records for specific issues. There is an entry for the issue accessed by the user.

フィールドの説明
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
アーティクルにアクセスするユーザ。
ＰｕｂｌｉｃａｔｉｏｎＩｄ
アクセスされたアーティクルが属する発行物。
ＴｉｍｅＣｒｅｄｉｔＣｒｅａｔｅｄ
この発行物からのアーティクルについてこのユーザにクレジットされた日時。
ＡｖａｉｌａｂｌｅＣｒｅｄｉｔ
使用可能なクレジットの金額をＵＳドルで示す。
ＣｒｅｄｉｔＡｐｐｌｉｅｄ
適用されたクレジットの金額をＵＳドルで示す。
ＣｕｒｒｅｎｔＣｈａｒｇｅｓ
この発行物からのアーティクルについてこのユーザに課金されている金額をＵＳドルで示す。
ＨａｖｅＳｈｏｗｎＰｒｉｃｉｎｇＴｅｒｍｓ
ユーザがこの発行物のアーティクルの契約条件を見たかどうかを示す。有効な値は真（１）又は偽（０）である。
ＵｓｅｒＣｏｍｍｅｎｔｓテーブル
各ユーザのコメントを保管する。このテーブルはカスタム化サポートで使われる。

Field Description UserAccountId
User who accesses the article.
PublicationId
The issue to which the accessed article belongs.
TimeCreditCreated
The date and time that this user was credited for an article from this issue.
AvailableCredit
The amount of available credit is shown in US dollars.
CreditApplied
The amount of credit applied is shown in US dollars.
CurrentCharges
The amount charged to this user for articles from this issue is shown in US dollars.
HaveShowPricingTerms
Indicates whether the user has viewed the terms of the article for this issue. Valid values are true (1) or false (0).
UserComments table Stores the comments of each user. This table is used for customization support.

フィールドの説明
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
コメントが登録されているユーザ。
ＴｉｍｅＳｔａｍｐ
コメントが登録された日時。
Ｃｏｍｍｅｎｔ
このユーザのコメント。
Ｕｓｅｒｓテーブル
ナレッジスターのユーザアカウントの情報を保管する。この情報は各ユーザについてアドレス、アカウント状態、クレジット、課金などを含む。ユーザごとにＵｓｅｒｓテーブルにエントリーがある。ユーザがフレームワークＩＤ番号を必要とする事を何かすると、エントリーが作成されフレームワークＩＤ番号が送信される。

Field Description UserAccountId
The user to whom the comment is registered.
TimeStamp
The date and time when the comment was registered.
Comment
Comments from this user.
Stores user account information of Users table knowledge star. This information includes address, account status, credits, billing, etc. for each user. There is an entry in the Users table for each user. If the user does something that requires a framework ID number, an entry is created and the framework ID number is sent.

フィールドの説明
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
各ユーザを識別する。
ＦｉｒｓｔＮａｍｅ
ユーザのファーストネーム。
ＬａｓｔＮａｍｅ
ユーザのラストネーム。
Ｃｏｍｐａｎｙ
ユーザの勤務先。空欄でも良い。
Ｅｍａｉｌ
ユーザの電子メールアドレス。
ＡｃｃｏｕｎｔＣｒｅａｔｉｏｎＤａｔｅ
このユーザアカウントが作成された日付。
ＡｃｃｏｕｎｔＳｔａｔｕｓ
ユーザアカウントの状態。ユーザアカウントはｉｎａｃｔｉｖｅ（０）、ゲスト（１）、メンバー（２）、又はグループメンバー（３）である。ディスエーブル（４）とすることも可能である。「ゲスト」はナレッジスターに完全には登録していないユーザである。「メンバー」は課金情報も含めて完全な情報を提供したユーザである。
ＣｕｒｒｅｎｔＣｈａｒｇｅｓ
このユーザアカウントへの課金をＵＳドルで表す。
ＣｕｒｒｅｎｔＣｒｅｄｉｔｓ
このユーザが使えるクレジットをＵＳドルで表す。
ＯｕｔｓｔａｎｄｉｎｇＬｉｍｉｔ
ユーザに支払いを督促する限度額。ユーザごとに設定できる。
ＳｅｒｖｉｃｅＬｅｖｅｌ
ユーザに様々なレベルのサービスを提供するために将来使用する（例：「ゴールド」、「シルバー」、「エリート」など）。現在は「ゲスト」と「メンバー」の２レベルある。
ＰｒｏｍｏｔｉｏｎａｌＥｍａｉｌ
ユーザが販促電子メールを欲しているかどうかを示す。有効な値は真（１）と偽（０）である。
ＲｅｍｏｔｅＵｓｅｒ
このカラムは使用していない。
ＲｅｍｏｔｅＡｄｄｒ
ユーザのＩＰアドレス。
ＲｅｍｏｔｅＨｏｓｔ
このカラムは使用していない。
ＮａｍｅＦｏｒＢｉｌｌｉｎｇ
請求先名。
ＢｉｌｌｉｎｇＡｄｄｒｅｓｓ１
ユーザの請求先アドレスＮｏ．１
ＢｉｌｌｉｎｇＡｄｄｒｅｓｓ２
ユーザの請求先アドレスＮｏ．２
Ｃｉｔｙ
ユーザの住所（都市名）。
Ｓｔａｔｅ
ユーザの住所（州名）。
ＰｏｓｔａｌＣｏｄｅ
ユーザの郵便番号。
Ｃｏｕｎｔｒｙ
ユーザの住所（国名）。
Ｐａｓｓｗｏｒｄ
ユーザのパスワード。
ＰａｓｓｗｏｒｄＥｎｃｒｙｐｔｉｏｎＴｙｐｅ
ユーザのパスワードを暗号化した暗号タイプ。使用可能なのはＢａｓｉｃ（１）、ＲＳＡ（２）、ＳｉｍｐｌｅＨａｓｈ（３）である。
ＣａｒｄＴｙｐｅ
クレジットカードのタイプ（例：Ｖｉｓａ、ＭａｓｔｅｒＣａｒｄ等）
ＣａｒｄＡｃｃｏｕｎｔＮｕｍｂｅｒ
表示しても安全なクレジットカード番号で、例えば「ｘｘｘｘｘｘｘｘｘｘｘｘ１２３４」。
ＣａｒｄＥｘｐｉｒａｔｉｏｎＭｏｎｔｈ
クレジットカードの有効期限が切れる月。
ＣａｒｄＥｘｐｉｒａｔｉｏｎＹｅａｒ
クレジットカードの有効期限が切れる年。
ＵｓｅｒＳｙｎｃテーブル
ダイナミクスデータベースでアップデートされるのを待つユーザのキュー。主な目的は、ダイナミクスデータベースのユーザリストをナレッジスターデータベースのユーザリストとシンクロナイズすることである。

Field Description UserAccountId
Identify each user.
FirstName
The user's first name.
LastName
The user's last name.
Company
The user's work location. It can be blank.
Email
The user's email address.
AccountCreationDate
Date when this user account was created.
AccountStatus
User account status. The user account is inactive (0), guest (1), member (2), or group member (3). It can also be disabled (4). “Guest” is a user who is not completely registered with Knowledge Star. “Member” is a user who provides complete information including billing information.
CurrentCharges
The charge for this user account is expressed in US dollars.
Current Credits
Credits available to this user are expressed in US dollars.
OutstandingLimit
The limit amount that prompts the user to pay. Can be set for each user.
ServiceLevel
Used in the future to provide users with various levels of service (eg “Gold”, “Silver”, “Elite”, etc.). Currently there are two levels, “Guest” and “Member”.
PromotionalEmail
Indicates whether the user wants a promotional email. Valid values are true (1) and false (0).
RemoteUser
This column is not used.
RemoteAddr
The user's IP address.
RemoteHost
This column is not used.
NameForBilling
Billing name.
Billing Address 1
User billing address No. 1
Billing Address 2
User billing address No. 2
City
User address (city name).
State
User's address (state name).
PostalCode
The user's zip code.
Country
User address (country name).
Password
User password.
PasswordEncryptionType
Encryption type that encrypts the user's password. Usable are Basic (1), RSA (2), and SimpleHash (3).
CardType
Credit card type (eg Visa, MasterCard, etc.)
CardAccountNumber
A credit card number that is safe to display, for example, “xxxxxxxxxxxx1234”.
CardExpirationMonth
Month when credit card expires.
CardExpirationYear
Year when credit card expires.
A queue of users waiting to be updated in the UserSync table dynamics database. The main purpose is to synchronize the user list of the dynamics database with the user list of the knowledge star database.

フィールドの説明
ＵｓｅｒＡｃｃｏｕｎｔＩｄ
両方のデータベースをシンクロナイズするためのユーザアカウント。
Ｏｐｅｒａｔｉｏｎ
データベース間でアーティクルをシンクロナイズするために何をするかを記述する。現在、ＣｒｅａｔｅとＵｐｄａｔｅという二つの動作が許されている。有効な値はＣとＵである。
Ｓｔａｔｕｓ
Ｏｐｅｒａｔｉｏｎの状態を記述する。ペンディング、進行中、エラーという３つの値が定義されている。有効な値はＰ、Ｉ、Ｅである。
ＥｒｒｏｒＲｅａｓｏｎ
エラーが発生しＳｔａｔｕｓがＥとマークされると、エラーメッセージがここに表される。

Field Description UserAccountId
A user account to synchronize both databases.
Operation
Describe what to do to synchronize articles between databases. Currently, two operations, Create and Update, are allowed. Valid values are C and U.
Status
Describes the operation status. Three values are defined: pending, in progress, and error. Valid values are P, I, E.
Error Reason
If an error occurs and Status is marked E, an error message is displayed here.

Claims (10)

A method of granting access to content using a content manager and a license manager,
Generating a content cell using the content manager , the content manager comprising :
To get the content database or Raco intents,
Extract content cell contracts that establish constraints to access the content,
Generating the content cell by adding the content and content cell conventions to the content cell;
Transmitting the content cell over a network to a receiving computing device;
Generating a license cell for the content cell using the license manager, the license manager comprising:
Supply the license,
Generating the license cell by adding the license to the license cell;
Transmitting the license cell to the receiving computing device via the network;
Granting access to the content based on the associated license cell information and content cell conventions. The step of generating the content cell includes:
Generating a content cell header including information identifying the content;
Digitally signing the content cell so that a receiving computing device can verify that the content manager is the content manager that created and transmitted the content cell;
Said content cell header, and a public certificate identifying the content manager, further comprising the step of adding to the content cell,
The step of generating the license cell includes:
Extracting a license cell contract that establishes a constraint to access the content;
Generating the license; and
Generating a license cell header including information identifying the license cell;
Adding the extracted license cell contract, the generated license, a license cell header, and a public certificate identifying the license manager to the license cell;
Digitally signing the license cell so that the receiving computing device can verify that the license manager is the license manager that generated and sent the license cell.
The method of claim 1.   The method of claim 1, further comprising receiving a user request for the content cell.   The method of claim 1, further comprising receiving a user request for the license cell. Granting access to the content comprises confirming that a license cell for the content cell is present on the receiving computing device;
The method of claim 1.   The method of claim 1, further comprising encrypting at least the content.   The method of claim 1, further comprising encrypting at least the license. Receiving a content location cell associated with the content cell;
Transmitting the content location cell to the receiving computing device via the network;
Further granting access to the content location cell based on information in an associated license cell.
The method of claim 1.   The method of claim 1, wherein the content cell contract includes at least one right associated with the content cell and a requirement to access at least one right associated with the content cell. The license cell convention, the includes at least one right associated with the license cell, and requirements for accessing at least one right associated with the license cell The method of claim 2.

Images