JP4965420B2 - Content server system - Google Patents

Description

  The present invention relates to a content server system that securely manages content (data files) provided to users connected via an external network such as the Internet.

  In current systems that manage content provided to users via an external network on a Web basis, when users access content (files), URLs (Uniform Resource Locators) are used as file locations in the server. Yes.

  Here, in order to ensure security in conventional systems, management of files and information is concentrated or separate servers and separate authentication and file systems are prepared and operated independently (for example, the following patents) Reference 1). In some cases, security is ensured by centrally managing servers of the same interface or servers of the same type by the same management entity.

JP 2001-306521 A

  However, the above conventional techniques have the following problems.

First, since the problem on the web-based system, that is, when the user accesses the file in the conventional web-based system, the relationship between the file position in the server and the URL is closely related.
(1) It is easy to estimate the actual file position, and there is a problem in access safety.
(2) When the file position is changed, there is a problem that the URL to be accessed needs to be changed accordingly, and management is troublesome.
(3) In order to change the security level of a file, it is necessary to manage access level information of all registered users at the HTTP (Hypertext Transfer Protocol) server system level.

In addition, because intellectual property management issues, that is, file content also has an aspect of intellectual property, it is necessary to control the disclosure,
(4) It is assumed that the file content can be stored only in a specific location that is recognized (or trusted) by the owner of the intellectual property. In this case, the file content cannot be stored in a centralized location.
(5) Access with security must be implemented.
There are problems such as.

Furthermore, physical management of file systems, that is, centralizing management of files and information for the purpose of centralized management, concentrates a lot of data on one place (single server).
(6) The capacity of the storage device of the server is limited (a large capacity server is required).
(7) Large processing performance is required as server performance.
(8) If the amount of content is large and the amount of access is frequent, the load (traffic) on the network increases, so that functions such as security management in the HTTP server system may be hindered.
There are problems such as.

  The present invention has been made in view of the above, and it is an object of the present invention to provide a content server system in which it is difficult to specify a content storage location to improve security and to realize flexible access level setting.

  In order to solve the above-described problems and achieve the object, the present invention provides an HTTP server connected to a network, a content database, an access level for each content that can be provided by the content database, and access to the content database. Content stored in the content database, including a management information database that stores management information including an access level for each user that is permitted, and a CGI processing unit that manages the content database and the management information database Alternatively, when an access request to the content stored in the storage location indicated by the information stored in the content database is received via the network, the HTTP server transfers the received access request to the CGI processing unit, The CGI processing unit determines whether to permit access to the content corresponding to the content ID based on the content ID and user ID included in the access request received from the HTTP server and the management information. It is characterized by doing.

  According to the present invention, it is possible to make it difficult to specify the storage location of the content in the system. Also, for example, access management such as restricting editing of copyrighted content created by others to a user who is permitted to register and edit all content in the system is possible. That is, the access level can be set more flexibly than in the prior art.

  Embodiments of a content server system according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment 1 FIG.
FIG. 1 is a diagram showing a configuration example of Embodiment 1 of a content server system according to the present invention. The content server system according to the present embodiment includes an HPPT server 1, a CGI processing unit 2, a management information DB (database) 3, and a content DB 4 connected to a network, and a user terminal via the network. Connected.

  The HTTP server 1 communicates with a user connected via a network, and transfers information received from the user to the CGI processing unit 2 as necessary. When information addressed to the user is received from the CGI processing unit 2, the information is transferred. The CGI processing unit 2 is configured to execute CGI (Common Gateway Interface) processing, and executes processing according to various requests from the user received via the HTTP server 1. For example, the content stored in the content DB 4 is provided to the requesting user. The management information DB 3 stores, as management information data, information about users who are permitted to access the system. The content DB 4 stores content file data and the like.

  FIG. 2 is a diagram illustrating a configuration example of the management information DB 3 and the content DB 4 according to the first embodiment. As shown in FIG. 2, the management information DB 3 of the present embodiment includes access management data including content identification information (content ID) and access level information for each content, user identification information (user ID), and user. User management data including access level information for each, and common access level data used when determining an access permission range for a user who is permitted to access. In the content DB 4, the actual content data, the storage link data (hereinafter simply referred to as “storage destination data”), the content identification information (content ID), and registration (update) are stored. Content supplementary data, which is content management information including information such as date / time, creator, content status and search keyword used for content search, is included.

  The content server system according to the present invention having the above-described configuration can receive content received from a user in response to an access request (content registration request, content acquisition request, etc.) from a user connected via a network. Are stored in the content DB 4 and the information stored in the content DB 4 is provided to the user (reading + transmitting). The content received from the user may be stored in another database different from the content DB 4. In this case, the content DB 4 stores information indicating the storage location of the content.

  First, information used when the content server system according to the present invention determines whether or not to respond to an access request when an access request is received from a user will be described.

  In the present invention, whether or not to respond to an access request is determined based on the access level for content (access level information for each content, hereinafter referred to as content access level) and the access level for users (access level information for each user, hereinafter). , Called user access level). Hereinafter, these access levels will be described in detail.

(Content access level)
The content access level represents the right of access to specific content. For example, when the access level a is equal to or higher than another access level b for the content # 1, a user with an access level “a” can be executed by the user with an access level “b” for the content # 1. All the processes can be executed.

  The access level can be expressed as a bundle set. For example, when “a ≧ b” is used to indicate whether the access level a is higher than or equal to the access level b, this relationship “≧” satisfies the property of (partial) order as the symbol implies. The relationship between access levels a and b is expressed as follows.

An access level that has access levels a and b is expressed as “aVb”.
A common access level of the access levels a and b is expressed as “aΛb”.
-Indicates that there is no right at access level 0.

The basic relationship between access levels is shown below.
a ≧ 0
aΛ0 = 0
aV0 = a
aVa = a
aΛa = a
If a ≧ b, (aΛc) ≧ (bΛc)
If a ≧ b, (aVc) ≧ (bVc)
(AVb) Vc = aV (bVc)
(AΛb) Λc = aΛ (bΛc)
Since a ≧ b, aVb = a, and aΛb = b are the same value, if there is a table of Λ, it can be used to determine whether or not the relationship “≧” is established.

(User access level)
The user access level given to each user is generally recorded in a database. Note that the user access level may change dynamically. Assuming the two most common privileges, usr and admin, admin indicates that all access within the system (group) is possible, and usr indicates the access contents that a normal user can access within the system (group). It is often expressed in the form of showing. Of course, “admin ≧ usr”. It is also possible to divide the usr level into several types and to give different access levels for each user. Below, it demonstrates using a specific example.

As a precondition, it is assumed that the following expression (1) exists as the right of access in the system.
a (i) = <right to display cover of content i>
b (i) = <right to modify cover of content i>
c (i) = <right to display contents of content i>
d (i) = <Right to edit contents i>
(Where i is the content ID in the system) (1)

  For example, assuming that the access level of the general user u is usr1 (u), all the contents registered by the user can be edited at this access level, but the contents registered by others can only be viewed. That is, it has the authority to register content and edit the content registered by itself, and the authority to browse all content (cover and cover content). In addition, it is assumed that a browsing user whose access level is usr2 (u) has only the right to view and cover content, and does not have the right to manage (register and edit) content. Further, it is assumed that the restricted user whose access level is usr3 (u) has only the right to view the cover of each content. In this case, the access level of each user can be expressed as the following equation (2).

usr1 (u) = V {b (i) Vd (i): i is the content ID registered by the user u} V
V {a (i) Vc (i): i is the ID of the content in the system}
usr2 (u) = V {a (i) Vc (i): i is the ID of the content in the system}
usr3 (u) = V {a (i): i is the ID of the content in the system}
admin = V {a (i) Vb (i) Vc (i) Vd (i): i is a content ID in the system} (2)

  For convenience, the group grp having the access level stat is denoted as grp: stat. As a special case, there is a special group called “admin”, and a user having admin authority of this group can access all of the entire system.

In addition,
Ω = {a | a is the right of access in the system}
Ωgrp = {a | a is the right to access in group grp}
If
admin: admin = VΩ
grp: admin = VΩgrp
admin: admin ≧ grp: admin ≧ grp: usr
The relationship is established.

(Content access level and confirmation)
For example, when the access right of a general user is x and the access level set for the content is y, the access level that can be accessed by this user is xΛy. In addition, normally, the access is limited by the minimum necessary access at that time. For example, when requesting browsing (content acquisition), “(xΛy) Λ <right to browse>”, when requesting registration “(XΛy) Λ <registration right>” is the actual access level. In this case, for the sake of convenience, they will be referred to as “access level restricted by the right of browsing” and “access level restricted by the right of registration”.

  “XΛy = 0” indicates a case where the user does not have any authority to access, and “xΛy = y” indicates a case where all the contents have access authority.

  Then, in the management information DB 3 of the content server system according to the present invention, as shown in FIG. 2, the access level information for each user is used as information used to determine whether the user can access the content. Stored is access level information and common access level data for each content.

  Next, the detailed operation of the content server system according to the first embodiment of the present invention will be described with reference to the drawings. First, the operation when registering content in the content server system (including both new registration and update registration) will be described with reference to FIG. FIG. 3 is a flowchart illustrating an example of an operation when content is registered in the content server system according to the first embodiment.

  The CGI processing unit 2 monitors whether or not a content registration request (message) has been received via the HTTP server 1, and when the content registration request is received (step S11, Yes), the user who has transmitted the content registration request An authentication process (hereinafter referred to as a requesting user) is performed (step S12). For example, it is confirmed whether or not the user ID of the requesting user is registered in the user information included in the user management data in the management information DB 3, and if it is registered, it is determined that the user is permitted access. Continue processing. If it is not registered, the process ends.

  If it is determined that the processing is continued as a result of the authentication processing, the CGI processing unit 2 determines whether the requesting user is permitted to register the content indicated by the registration request based on the access management data and the user management data. It is determined whether or not (step S13). Specifically, the management information DB 3 is searched by using the user ID of the requesting user and the content ID of the content to be registered (the content that the user intends to register) included in the received content registration request as a key. The access level information for each user (in the user management data) corresponding to the user ID and the access level information for each content (in the access management data) corresponding to the content ID are acquired. Then, based on the access level information for each user and the access level information for each content, it is confirmed whether the user is authorized to register the content.

  For example, when the access level for each content indicates that registration processing is permitted for all users, the CGI processing unit 2 indicates that the access level for each user indicates that registration processing is permitted (request If the original user has authority to register), it is determined that the requesting user has authority to register content. Further, when the access level for each content indicates that registration processing is permitted for some users, the CGI processing unit 2 indicates that the access level for each user permits registration processing ( If the requesting user is not included in the “some users indicated by the access level for each content”, the requesting user has the content registration authority. Judge not to have. In addition, when newly registering content, confirmation is performed based only on access level information for each user. That is, if an authority to register content is given as an access level for each user, it is determined that the user is an authorized user.

  If it is determined that the authority to register the content is given (step S13, Yes), the CGI processing unit 2 continues the process. On the other hand, if it is determined that no authority is given, the process is terminated (No in step S13).

  In step S13, it may be determined whether or not the requesting user is permitted to register content by executing the following processing. That is, an approver who can determine whether to permit content registration is determined in advance, and an e-mail address is stored in the access management data as the contact information. When the content registration request is received, the CGI processing unit 2 acquires the contact information of the approver corresponding to the content ID from the management information DB 3, and includes the requesting user user ID and the content ID in the acquired contact information. Send an email. When the approver receives the e-mail, the approver performs an authentication process using the user ID included in the e-mail, determines whether the content registration is possible, and returns an e-mail including the determination result to the CGI processing unit 2. The CGI processing unit 2 continues the process when the content of the returned e-mail indicates that registration is permitted.

  If it is determined in step S13 that the process is to be continued, the CGI processing unit 2 stores the content ID of the content to be registered and its access condition (access level for each content) in the access management data in the management information DB 3. (Step S14). The access condition is information that is determined in advance by the requesting user and transmitted by a content registration request or a message that is transmitted subsequently.

  Finally, the CGI processing unit 2 stores the information (content (actual data) or content storage destination data and content-accompanying data) received from the user in the content DB 4 (step S15).

  The above is the operation for registering the information received from the user in the content server system. Next, the operation for providing the user with the information registered in the content server system will be described with reference to FIG. To do. FIG. 4 is a flowchart illustrating an example of an operation when providing information registered in the content server system of the first embodiment to a user.

  The CGI processing unit 2 monitors whether or not a content acquisition request (message) has been received via the HTTP server 1, and if the content acquisition request is received (Yes in step S21), the user who has transmitted the content acquisition request An authentication process (hereinafter referred to as a requesting user) is performed (step S22). The specific operation is the same as the authentication process (see step S12 in FIG. 3) in the operation for registering content.

  If it is determined that the process is continued as a result of the authentication process, the CGI processing unit 2 determines that the request source user obtains the content to be acquired (content that the user wants to acquire) based on the access management data and the user management data. It is determined whether the user is permitted to acquire (browse) (step S23). Specifically, the management information DB 3 is searched by using the user ID of the request source user and the content ID of the content to be acquired included in the received content acquisition request as keys, and the user ID (user management) Access level information for each user (in the data) and access level information for each content (in the access management data) corresponding to the content ID are acquired. Then, based on the access level information for each user and the access level information for each content, it is confirmed whether the user is authorized to acquire the content.

  When it is determined that the authority to acquire the content is given (step S23, Yes), the CGI processing unit 2 continues the process. On the other hand, if it is determined that no authority has been given, the process is terminated (No in step S23).

  In step S23, it may be determined whether or not the requesting user is permitted to access the content by executing the following process. That is, an approver who can determine whether or not to permit access to content is determined in advance, and an e-mail address is stored in the access management data as the contact address. When the content acquisition is received, the CGI processing unit 2 acquires the contact information of the approver corresponding to the content ID from the management information DB 3, and the acquired contact information includes the requesting user user ID and the content ID. send mail. When the approver receives the e-mail, the approver performs an authentication process using the user ID included therein, determines whether the content can be accessed, and returns the e-mail including the determination result to the CGI processing unit 2 To do. The CGI processing unit 2 continues the process when the content of the returned electronic mail indicates that access is permitted.

  When it is determined in step S23 that the process is continued, the CGI processing unit 2 specifies an access range based on the access level information for each user and the access level information for each content (step S24). Further, information (actual data or storage destination data) included in the specified access range is acquired from the content DB 4 and transmitted to the requesting user via the HTTP server 1 (step S25).

  The processing shown in steps S21 to S25 is an operation executed when a content acquisition request is received from the user (operation when providing information registered in the content server system to the user).

  In addition, the content server system according to the present invention has a function of displaying a list of content stored in the content DB 4 (displaying content-attached data as a list) in response to a request from the user. An operation when a content list display request is received from the user will be described below with reference to FIG. FIG. 5 is a diagram illustrating an example of an operation when a content list is displayed.

  The CGI processing unit 2 monitors whether or not a content list display request (message) has been received via the HTTP server 1, and if a content list display request (hereinafter referred to as a list display request) is received (step S1). (S31, Yes), authentication processing of the user who transmitted the list display request (hereinafter referred to as a requesting user) is performed (step S32). The specific operation is the same as the authentication process (see step S12 in FIG. 3) in the operation for registering content.

  If it is determined that the process is continued as a result of the authentication process, the CGI processing unit 2 searches the access level information for each user (in the user management data) in the management information DB 3 using the user ID of the requesting user as a key. Thus, the access authority of the requesting user is recognized, and it is determined whether the list can be displayed based on the recognition result (step S33). If it is determined that display is impossible (No at step S33), the process is terminated. On the other hand, if it is determined that display is possible (step S33, Yes), content supplementary data in the content management DB 4 is searched, and supplementary data of content that can be viewed with the access authority of the requesting user is acquired (step S34). Then, the acquired incidental data is displayed as a list. Alternatively, further necessary information is extracted from the acquired incidental data, displayed as a list (step S35).

  Note that the user can designate a search condition when transmitting the list display request. For example, conditions can be specified for information included in content-attached data, such as content update (registration) date and time, content category, and registrant. Therefore, when the search condition is received from the requesting user, in step S34, content incidental data that matches the acquired search condition is extracted.

  As described above, in this embodiment, the CGI processing unit manages content, and performs processing according to a content registration request received from an external user or content acquisition to the content, and the HTTP server and the CGI The information exchanged with the processing unit is relayed. Thereby, there is no direct access to content from an external user, and access to content with security can be realized. In addition, the load on the HTTP server can be reduced. In addition, the access level is set for each content and each user, and based on these two access levels, it is determined whether or not to permit access to each content. Access management such as restricting editing of copyrighted content created by others to a user who is permitted to register or edit is possible. That is, more flexible access level management than before can be realized.

Embodiment 2. FIG.
Next, the content server system according to the second embodiment will be described. In general, contents are revised due to various factors, and a plurality of versions (versions) exist as time passes. As a method for managing a plurality of contents of different versions by the content server, for example, there is a method of managing using version information in addition to the content ID. On the other hand, it is also possible to manage only by content ID without using version information. That is, there is a method of managing by assigning different content IDs when the versions are different even for the same content.

  Here, considering the case where the user accesses the desired content, when trying to manually extract the version without being aware of anything, the latest version is often requested. In addition, when a link is created and left unattended without being particularly aware of the version, and the user tries to retrieve the link again afterwards, the original version is often requested.

On the other hand, when acquiring the target content while being aware of the version, specify and acquire the latest version, specify the previous version, or acquire the latest version at a certain date and time. In many cases, the target content is acquired by specifying. That is, it is considered that the user acquires content by specifying the following conditions.
(1) "Content ID + <version number>"
(2) "Content ID + latest version"
(3) "Content ID + latest previous version"
(4) "Content ID + <date> Latest version before date"

  These are condition specifying methods assuming that contents are managed using version information, but there are also methods for managing without using version information as described above. Therefore, the content server needs to correctly identify and provide the specified version when receiving content specification using version information from the user while performing version management without using version information. is there.

  Therefore, in the present embodiment, a content server system that manages content without using version information in the system will be described. The configuration of the content server system according to the present embodiment is the same as that of the content server system according to the first embodiment (see FIG. 1).

  Also, version dependency is defined between contents as follows. That is, there are generally a plurality of dependency relationships, and as the revisions are repeated, the following combinations of version dependency relationships (information consisting of status and time stamp) are generated. Therefore, the content server system of this embodiment manages the version of the content by registering one version dependency as one record in the table. For example, the management information DB 2 manages, as version management data, the ID of the content (based on the content) generated by the revision, in association with the ID of the content generated by the revision.

(Example 1) The content (ID2) is created by revising the content (ID1).
ID1 → (based on) → ID2
(Date 1) (Date 2)
(Example 2) The content (ID3) is created by revising the content (ID1) and the content (ID2).
ID1 → (based on) → ID3
(Date 1) (Date 3)
ID2 → (based on) →
(Date 2)
(Example 3) When the content (ID2) is created by revising the content (ID1) and the content (ID3) is created by revising the content (ID1).
ID1 → (based on) → ID2
(Date 1) (Date 2)
→ (based on) → ID3
(Date 3)

  Next, the detailed operation will be described with reference to the drawings. Here, before starting detailed description, the data which management information DB3 with which the content server system of this Embodiment is provided are demonstrated. As shown in FIG. 6, the management information DB 3 according to the present embodiment includes a version of content in addition to the access management data, user management data, and common access level data held by the management information DB 3 according to the first embodiment. It holds version management data for management. The content DB 4 holds the same type of data as in the first embodiment.

  Next, an operation for registering information in the content server system of the present embodiment will be described with reference to FIG. FIG. 7 is a flowchart showing an example of the operation when content is registered in the content server system of the second embodiment, and the same step number is assigned to the same operation as the content registration of the first embodiment described above. is doing. Here, only processing different from the first embodiment will be described.

  In step S13a in which processing different from that in the first embodiment is executed, the CGI processing unit 2 first determines the content based on the content ID and content version information of the content to be registered included in the received content registration request. A local content ID used inside the server system and version dependency information registered as version management data in the management information DB 3 are generated. If the content version information is not included (omitted), for example, the processing is performed assuming that the content is the latest version. Then, based on the generated local content ID and version dependency information, access level information for each content and access level information for each user corresponding to the user ID of the requesting user, the content to the user Check if you are authorized to register

  In step S14a, the content ID of the content to be registered, the corresponding local content ID, access conditions (access level for each content), and version management data (version dependency information) are stored in the management information DB 3. Is stored.

  Next, an operation for providing information registered in the content server system of the present embodiment to the user will be described with reference to FIG. FIG. 8 is a flowchart showing an example of an operation when providing information registered in the content server system of the second embodiment to the user. The same operation as the content access of the first embodiment described above is the same. Step number is given. Here, only processing different from the first embodiment will be described. Also, it is assumed that a content acquisition request including information specifying the version (content version information) is received from the user.

  In step S23a for executing processing different from that in the first embodiment, the CGI processing unit 2 first includes the content ID of the content to be acquired and the version information of the content included in the received content acquisition request, and the management information DB 3 Local content ID corresponding to the version of the content requested by the user based on the version dependency information included in the version management data in the file and the creation (update) date / time information of the content (inside the content server system) The local content ID) used in. Next, the management information DB 3 is searched using the user ID of the requesting user included in the received content acquisition request and the specified local content ID as a key, and the user (in the user management data) corresponding to the user ID Based on the access level information for each content and the access level information for each content (in the access management data) corresponding to the local content ID, it is confirmed whether the user is authorized to acquire the content.

  As described above, in the present embodiment, when the information specifying the version of the content received from the user does not match the version management format in the own system, based on the received content ID and the information specifying the version, The local content ID uniquely indicating the specific version is specified, and the content is searched based on the specified local content ID. This makes it possible to correctly recognize the version and provide the requested content even to a user who designates the version by a method different from the method in the own system.

Embodiment 3 FIG.
Next, Embodiment 3 will be described. In the first and second embodiments described above, the content server system that restricts access by assigning an access level to each user has been described. However, users are grouped in advance into a plurality of groups, and an access level is assigned to each group. You may do it.

  Also in the present embodiment, each user can perform content registration, acquisition, and list display (list display of incidental data) using the content server system, as in the first embodiment described above. is there. Note that, except that the access level is assigned to each group, the operation is the same as in the first or second embodiment, and thus description of each operation (content registration operation, content acquisition operation, list display operation) is omitted.

Embodiment 4 FIG.
Next, the fourth embodiment will be described. In the content server system of the above-described embodiment, the example in which the user management data and the access management data are stored in the same database and the CGI processing unit manages a single content server has been described. 9, user management data and access management data are stored in different physically separated databases (user management DB, access management DB), and a plurality of physically separated content DBs The contents may be stored in a distributed manner. In the case where the content is distributed and stored in a plurality of content DBs, the storage location information of the content is stored in a content DB other than the content DB storing the actual data of the content. Thereby, the search speed of content can be increased. In addition, security is ensured by connecting the CGI processing unit and each database with a highly reliable network (SSL: Secure Sockets Layer or the like).

  Further, as shown in FIG. 10, it is possible to adopt a configuration including a plurality of combinations of the HTTP server, the CGI processing unit, the management information DB, and the content DB.

  In this way, various information and contents stored in the database can be stored and managed in physically different places, and in this case, the same effect as that of the above-described embodiment can be obtained. In addition, the amount of content (data amount) that can be managed can be increased, and the load on each device constituting the system can be distributed.

  As described above, the content server system according to the present invention is useful for a server system that manages content to be provided to users belonging to an external network, and in particular, performs security management by individually setting an access level for each content. Suitable for cases.

It is a figure which shows the structural example of Embodiment 1 of the content server system concerning this invention. It is a figure which shows the structural example of management information DB and content DB of Embodiment 1. FIG. 4 is a flowchart illustrating an example of an operation when registering content in the content server system according to the first embodiment. 6 is a flowchart illustrating an example of an operation when providing information registered in the content server system of the first embodiment to a user. It is a figure which shows an example of operation | movement in the case of displaying a content list. It is a figure which shows the structural example of management information DB and content DB of Embodiment 2. FIG. 10 is a flowchart illustrating an example of an operation when registering content in the content server system according to the second embodiment. 10 is a flowchart illustrating an example of an operation when providing information registered in the content server system of the second embodiment to a user. It is a figure which shows the structural example of the content server system of Embodiment 4. FIG. FIG. 10 is a diagram illustrating another configuration example of the content server system according to the fourth embodiment.

Explanation of symbols

1 HTTP server 2 CGI processing unit 3 Management information DB (database)
4 Content DB (database)

Claims (13)

An HTTP server connected to the network;
A content database;
A management information database for storing management information including an access level for each content that can be provided by the content database and an access level for each user permitted to access the content database;
A CGI processing unit for managing the content database and the management information database;
With
The content database and the management information database are connected to the HTTP server via the CGI processing unit,
When an access request to the content stored in the content database or the content stored in the storage location indicated by the information stored in the content database is received via the network,
The HTTP server transfers the received access request to the CGI processing unit,
The CGI processing unit determines whether to permit access to the content corresponding to the content ID based on the content ID and user ID included in the access request received from the HTTP server and the management information. And
When the access request is a content update request that is a content registration request or content storage location information registration request to the content database,
The CGI processing unit
Based on the access level for each content corresponding to the content ID and the access level for each user corresponding to the user ID, it is determined whether to respond to the content update request. The content or content storage location information received from, and content-accompanying data including various information related to the content are stored in the content database, and the content ID and content version information included in the content update request are stored in the content update request. Based on the content received from the user or the content stored in the storage location indicated by the content storage location information, and generates a local content ID uniquely indicating the content included in the local content ID and the content update request. Stores Ceiling ID to the management information database,
Furthermore, when the content received from the user or the content stored in the storage location indicated by the content storage location information is created by revising the original content that is the existing content, the content is revised to the original content. Dependency information indicating the relationship with the generated content is generated based on the content incidental data of the content created by the revision, and further, the generated dependency relationship information is generated for the content created by the revision. A content server system, which is stored in the management information database in association with a local content ID .   When the CGI processing unit permits access to the content corresponding to the content ID, the CGI processing unit further determines a process to be executed later based on the content ID, the user ID, and the management information. The content server system according to claim 1. The CGI processor is further content server system according to claim 1 or 2, characterized in that updating the management information database based on the contents supplementary data. The CGI processing unit, the content server system according to claim 1, 2 or 3, characterized in that to generate the dependency information based on the status information and the update time information included in the content accompanying data. When the access request indicates a read request for content stored in a content database,
The CGI processing unit determines whether to respond to the content read request based on an access level for each content specified based on the content ID and an access level for each user specified based on the user ID. If it is determined that respond, according to claim 1-4, characterized in that determining on the basis of the permission range allowed for a user of the user ID to the access level of the access levels and each corresponding user for each the content The content server system according to any one of the above. Unique local content in the database in which the management information database stores content assigned to content stored in the content database and content stored in the storage location indicated by the content storage location information stored in the content database Storing ID and dependency information indicating the mutual dependency between related contents;
When the access request indicates a read request for content stored in a content database,
The CGI processing unit specifies a local content ID corresponding to a content specified by a content ID and content version information included in the content read request based on the dependency relationship information and content update date / time information. And determining whether to respond to the content read request based on an access level for each content corresponding to the specified local content ID and an access level for each user corresponding to the user ID. 5. The content server system according to 5 . The management information database further stores a content ID of each content,
The CGI processing unit, when responding to the content read request, searches and reads the content indicated by the content read request based on the content ID, the local content ID, and the dependency relationship information. Item 7. The content server system according to Item 6 . When the access request indicates a list display request for content stored in the content database or content stored in a storage location indicated by information stored in the content database,
The CGI processing unit determines whether or not to respond to the content list display request based on an access level for each user corresponding to the user ID, and if it is determined to comply, the content stored in the content database The content supplementary data of the content accessible at the access level possessed by the user of the user ID is acquired from the supplementary data, and a content list is generated and displayed based on the acquired content supplementary data. Item 8. The content server system according to any one of Items 1 to 7 . Including a search keyword used in the search processing of the content corresponding to the content-accompanying data
When a search keyword is included in the content list display request,
The CGI processing unit selects the acquired content incidental data based on a search keyword included in the content list display request, and generates a content list based on the selected content incidental data. The content server system according to claim 8 . Group each user according to a predetermined rule,
The content server system according to any one of claims 1 to 9 , wherein, as an access level for each user, a user belonging to the same group is assigned and managed with the same access level. Before SL management information database and the content database, according to claim 1 wherein either directly connected to the CGI processor, or, characterized in that via a reliable network is connected to the CGI processor to 1 0 content server system according to any one of. Content server system according to any one of claims 1 to 1 1, characterized in that said a plurality of content databases and distributed management of content. The HTTP server, the content database, the management information database and the content server system according to any one of claims 1 to 1 2, characterized in that it comprises a plurality of configured basic building block by the CGI processor.

Images