Program, server and file management method

Abstract

To provide a program, server, and file management method, which enable provision of services that are highly convenient for users in file management.SOLUTION: Multiple pieces of setting information with different content can be set for one management unit, and different inquiry information is generated for each piece of setting information when multiple pieces of setting information are set. Upon receipt of an access to the inquiry information from a given user, the user is enabled to receive files managed in the management unit corresponding to the inquiry information at a user terminal.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present invention relates to a program, a server, and a file management method. [Background technology]

[0002] In the prior art, there exist content management systems that create collection folders and generate links to file requests.

[0003] For example, the content management system of Patent Document 1 generates a link to a file request used to collect content items and distributes the generated link to the submitter. The content management system then prohibits one submitter from viewing the file by other submitters (see paragraph 0020 of Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Special Publication No. 2018-513486 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the conventional technology shown in Patent Document 1 requires complicated content management and further improvement is required. It is desirable to provide a service in file management that is highly convenient for users.

[0006] The present invention has been made in consideration of the above-mentioned problems, and has an object to provide a program, a server, and a file management method that can realize a service that is highly convenient for users in file management. [Means for solving the problem]

[0007] (1) The present invention provides A program for causing a computer to perform file management processing, a storage processing unit that stores a file transmitted from a terminal of a transmitting user in a storage unit based on an instruction from the transmitting user; a management unit section for setting a management unit for managing the file; a setting unit that sets setting information based on input information of the sending user in association with the management unit; a query information control unit that generates query information corresponding to the management unit and associates the query information with the setting information; causing a computer to function as a file control unit that enables a given user to receive, when access to the inquiry information is received from the given user, the file managed in the management unit corresponding to the inquiry information; The setting unit is A plurality of pieces of setting information with different contents can be set for one of the management units, The inquiry information control unit: The present invention relates to a program that generates different query information for each piece of setting information when multiple pieces of setting information are set in the setting unit.

[0008] The present invention also relates to a server including the above-mentioned units, and to an information storage medium on which the above-mentioned program is stored.

[0009] Here, the "query information" refers to, for example, a uniform resource locator (URL) for uniquely specifying a web page on the Internet using a protocol such as HTTP (Hyper Text Transfer Protocol) or HTTPS (Hyper Text Transfer Protocol Secure). Note that the "query information" may also be information on a server capable of sending and receiving data using other communication protocols such as FTP (File Transfer Protocol). Furthermore, "when access to the query information is received" refers to, for example, when access to information specified by a URL is received.

[0010] Additionally, "receiving" refers to at least one of downloading, viewing, printing, and saving in a specified storage area.

[0011] According to the present invention, the sending user notifies the receiving user of the generated reference information (e.g., a URL), and the receiving user can receive the file sent by the sending user by accessing the reference information.

[0012] In addition, since the present invention allows a plurality of setting information with different contents to be set, the sending user can set various setting information.

[0013] Furthermore, when multiple setting information are set, the present invention can generate different query information for each setting information, making it possible to use different query information depending on the content of the setting information, thereby providing a file transfer service that is highly convenient for the sending user.

[0014] (2) The server, program, and information storage medium of the present invention are The setting information includes information of a recipient user who is to receive the file; The setting unit is A plurality of pieces of setting information each having different information on a receiving user can be set for one management unit, The inquiry information control unit: Different inquiry information may be generated for each recipient user's information.

[0015] Here, "receiving user information" refers to information about the receiving user, such as the receiving user's email address, email address domain, account, and so on.

[0016] According to the present invention, different query information can be generated for each receiving user's information. Therefore, it is possible to avoid sharing common query information between receiving users. Therefore, it is possible to make the query information different depending on the receiving user, and it is possible to provide a service that is highly convenient for the sending user.

[0017] (3) The server, program, and information storage medium of the present invention are The setting information includes information of a recipient user who is to receive the file; The setting unit is Information on a plurality of recipient users may be set for one setting information.

[0018] According to the present invention, since information of multiple receiving users can be set for one setting information, for example, a predetermined number of receiving users can share the same inquiry information, and as a result, a service that is highly convenient for the sending user can be provided.

[0019] (4) The server, program, and information storage medium of the present invention are The setting information includes security information, The setting unit is A plurality of pieces of setting information each having different security information can be set for one management unit, The inquiry information control unit: Different reference information may be generated for each piece of security information.

[0020] Here, the "security information" refers to information related to security such as authentication, encryption, etc. For example, the "security information" is at least one of the user authentication information and the authentication information corresponding to the query information.

[0021] According to the present invention, different query information can be generated for each piece of security information, so that sharing of common query information can be avoided, thereby providing a service that is highly secure and convenient for the sending user.

[0022] (5) The server, program, and information storage medium of the present invention are The setting information includes user authentication information of a recipient user who is to receive the file; The setting unit is A plurality of pieces of setting information each having different user authentication information can be set for one management unit, The inquiry information control unit: Different reference information can be generated for each user authentication information; The file control unit When access to the inquiry information is accepted from a given user, the user may be authenticated based on user authentication information of the receiving user, and if the authentication is permitted, the user may receive the file.

[0023] Here, "user authentication information" refers to at least one of the following: information on whether user authentication is enabled or disabled, whether a target receiving user for user authentication is specified, and, if a target receiving user for user authentication is specified, information on the target receiving user (e.g., the email address of the target receiving user).

[0024] According to the present invention, user authentication can be performed based on the user authentication information of the recipient user depending on the user who has accessed the query information, and files can be received by authorized users, thereby improving security.

[0025] Furthermore, according to the present invention, different query information can be generated for each user authentication information. For example, it is possible to generate a first query information in which the user authentication is valid and a second query information in which the user authentication is invalid, and the sending user can use the first query information and the second query information appropriately. As a result, it is possible to provide a service that is highly convenient for the sending user.

[0026] (6) The server, program, and information storage medium of the present invention are The setting information includes authentication information corresponding to the query information, The setting unit is A plurality of pieces of setting information each having different authentication information can be set for one management unit, The inquiry information control unit: different reference information can be generated for each of the authentication information; The file control unit When an access to the reference information is accepted from a given user, authentication is performed for the reference information based on the authentication information, and when the authentication is permitted, the user It may be possible to receive files.

[0027] Here, "authentication for the query information" refers to authentication of the site of the query information (e.g., password authentication). "Authentication information corresponding to the query information" refers to, for example, information on whether authentication corresponding to the query information is valid or invalid (e.g., information on whether password authentication required when accessing the query information is valid or invalid). Furthermore, "authentication information corresponding to the query information" also includes information used for authentication (e.g., password) when authentication corresponding to the query information is valid.

[0028] According to the present invention, authentication can be performed for the query information depending on the user who has accessed the query information, and only authorized users can receive files, thereby improving security.

[0029] Furthermore, according to the present invention, different query information can be generated for each piece of authentication information. For example, it is possible to generate a first query information in which password authentication is valid and a second query information in which password authentication is invalid, and the sending user can use the first query information and the second query information appropriately. As a result, it is possible to provide a service that is highly convenient for the sending user.

[0030] (7) The server, program, and information storage medium of the present invention are The setting unit is After generating the inquiry information, the setting information corresponding to the inquiry information is made changeable; The inquiry information control unit: Regardless of whether or not the setting information is changed, the valid state of the query information corresponding to the setting information may be maintained.

[0031] According to the present invention, even if the setting information is changed, the valid state of the query information corresponding to the setting information is maintained, so that after the setting information is changed, the sending user can save the trouble of notifying the user at the receiving end of the file of the query information.

[0032] (8) The server, program, and information storage medium of the present invention are The management unit includes: Depending on the state of the file set in the management unit, the state of the management unit may be forcibly invalidated.

[0033] According to the present invention, for example, if the status of a file set in a management unit is a virus-infected status, the status of the management unit can be forcibly invalidated. Therefore, according to the present invention, since the status of the management unit can be forcibly invalidated according to the status of the file, a highly convenient service can be provided.

[0034] (9) The present invention also provides A file management method for providing information on file management to a sending user from a server that performs file management processing, comprising the steps of: The server, storing the file transmitted from the terminal of the transmitting user in a storage unit based on an instruction from the transmitting user; setting a management unit for managing the file; setting setting information based on input information of the sending user in association with the management unit; generating query information corresponding to the management unit; A step of associating the query information with the setting information; When an access to the inquiry information is received from a given user, and enabling the user to receive the file managed in the management unit, The step of setting the setting information includes: A plurality of pieces of setting information with different contents can be set for one of the management units, The generating step includes: In a case where a plurality of pieces of setting information are set in the step of setting the setting information, different query information is generated for each piece of setting information, Transmitting the input information of the sending user received by the sending user's terminal to the server; The present invention relates to a file management method, characterized in that information regarding file management is received from the server. [Brief description of the drawings]

[0035] [Figure 1] FIG. 2 is an example of a network diagram of the file management system according to the present embodiment. [Diagram 2] FIG. 2 is a functional block diagram of the server 10 according to the present embodiment. [Diagram 3] FIG. 2 is a diagram showing an overview of file management according to the embodiment. [Figure 4] FIG. 4 is an explanatory diagram of a screen displayed on a terminal 20A according to the present embodiment. [Diagram 5] FIG. 4 is an explanatory diagram regarding file uploading according to the embodiment. [Figure 6] 13 is an example of information related to a management unit according to the present embodiment. [Figure 7] 4 shows an example of query information (URL) and setting information according to the present embodiment. [Figure 8] FIG. 4 is an explanatory diagram of a screen displayed on a terminal 20A according to the present embodiment. [Figure 9] FIG. 4 is an explanatory diagram of a screen displayed on a terminal 20A according to the present embodiment. [Figure 10] 4 shows an example of query information and setting information according to the present embodiment. [Figure 11] FIG. 4 is an explanatory diagram of a screen displayed on a terminal 20A according to the present embodiment. [Figure 12] FIG. 4 is an explanatory diagram of a screen displayed on a terminal 20A according to the present embodiment. [Figure 13] FIG. 4 is a flowchart showing the flow of processing according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] The present embodiment will be described below. Note that the present embodiment described below does not unduly limit the contents of the present invention described in the claims. Furthermore, not all of the configurations described in the present embodiment are necessarily essential components of the present invention.

[0037] [1] Network 1 shows an example of a network diagram of a file management system. In the file management system of this embodiment, a server 10 and a user terminal 20 are connected via a network (such as the Internet or an intranet). Hereinafter, the terminal 20 refers to any one of terminals 20A, 20B, and 20C.

[0038] The server 10 is an information processing device capable of providing a file management service to a terminal 20 communicatively connected via the Internet. For example, the server 10 provides information relating to file management to the user's terminal 20.

[0039] For example, the sending user's terminal 20 transmits input information of the sending user to the server 10 and receives information relating to file management from the server 10.

[0040] Specifically, the server 10 of this embodiment receives a file from a sending user (a first user, for example, a user of the terminal 20A) and transmits the file to a receiving user (a second user, for example, a user of the terminal 20B). In short, the server 10 is also called a transfer device or an information processing device that transfers files.

[0041] The terminal 20 is a client device, and is an information processing device such as a smartphone, a mobile phone, a PHS, a computer, a game device, a PDA, or an image generating device, and is a device that can be connected to the server 10 via a network such as the Internet (WAN) or a LAN.

[0042] [2] Configuration Fig. 2 is an example of a functional block diagram of the server 10 of this embodiment. Note that the server 10 of this embodiment does not need to include all the units in Fig. 2, and may have a configuration in which some of them are omitted.

[0043] The storage unit 170 stores programs and various data for causing a computer to function as each unit of the processing unit 100, and also functions as a storage area for the processing unit 100.

[0044] The storage unit 170 includes a temporary storage area and storage. The storage is a device that permanently stores data, such as a hard disk, an optical disk, a flash memory, or a magnetic tape. The storage unit 170 may also store programs and data stored in the information storage medium 180.

[0045] The storage unit 170 may be a storage area of ​​the server 10 or a storage area on the cloud. In other words, it may be a storage area (storage device) on the Internet (on the cloud) that can be connected to the server 10 via a network (Internet).

[0046] The storage unit 170 of this embodiment includes a main storage unit 171 used as a work area, a user information storage unit 172, a management data storage unit 173, and a file storage unit 175. Note that some of these may be omitted.

[0047] The main storage unit 171 can be realized by a RAM or the like. The main storage unit 171 is a storage area used in the processing of this embodiment. The user information storage unit 172 stores user information (user account, password, email address, etc.). The user information storage unit 172 may be configured by a DB (DB is an abbreviation for database, the same applies below).

[0048] File information is stored in the management data storage unit 173 in association with a management ID (management identification information) that manages the file. The file information includes the file name, file size, virus scan status, MD5 checksum for determining the integrity of the file, expiration date, status (state) indicating valid or invalid, and the creator's email address.

[0049] The management data storage unit 173 may be configured with a DB. Furthermore, the management data storage unit 173 stores the query information and the setting information in association with the management ID.

[0050] The file storage unit 175 stores files transmitted from the terminal 20 of a sending user based on an instruction from the sending user.

[0051] The server 10 functions as a file server having a file storage unit 175 that stores and manages files. The file storage unit 175 may be provided in a device different from the server 10, or in a predetermined storage device connected to the server 10 via a network (Internet), or in a storage area on the Internet (cloud).

[0052] Information storage medium 180 (computer-readable medium) stores programs, data, etc., and its functions can be realized by storage such as an optical disk (CD, DVD), magneto-optical disk (MO), magnetic disk, hard disk, magnetic tape, or memory (ROM).

[0053] The communication unit 196 is for communicating with the outside (for example, a terminal, another server, or another network system), and the function thereof can be realized by hardware such as various processors or communication ASICs, programs, and the like.

[0054] The processing unit 100 performs various processes of this embodiment based on programs (data) stored in the storage unit 170 or the information storage medium 180 .

[0055] The processing unit 100 (processor) performs various processes using a main memory unit 171 in a storage unit 170 as a work area. The functions of the processing unit 100 can be realized by hardware such as various processors (CPU, DSP, etc.) or programs.

[0056] The processing unit 100 includes a communication control unit 110 , a storage processing unit 111 , a management unit 112 , a setting unit 113 , a query information control unit 114 , a file control unit 115 , an authentication control unit 116 , a notification unit 117 , and a Web processing unit 120 .

[0057] The communication control unit 110 transmits and receives data to and from the terminal 10. For example, the communication control unit 110 receives (accepts) information (for example, files, setting information, instruction information) transmitted from the sending user's terminal 20. In addition, the communication control unit 110 provides information related to file management to the sending user's terminal 20.

[0058] The storage processor 111 stores a file transmitted from the terminal 20 of the transmitting user in the storage unit 170 (for example, the file storage unit 175) based on an instruction from the transmitting user.

[0059] The storage processing unit 111 may encrypt a file when storing the file. The storage processing unit 111 also performs processing to register, update, and delete data stored in the management data storage unit 173 and the file storage unit 175. For example, the storage processing unit 111 may perform processing to update a database based on data received from the terminal 20.

[0060] The management unit 112 sets a management unit for managing files transmitted from the sending user's terminal 20. For example, the management unit 112 assigns a management ID to each management unit, and manages the file information by associating it with the management ID. The management ID is a unique ID and has identification power.

[0061] In addition, the management unit section 112 can forcibly invalidate the state of the management unit according to the state of the file set in the management unit. The "file state" set in the management unit is, for example, when the file is infected with a virus.

[0062] The setting unit 113 sets the setting information based on the input information of the sending user in association with the management unit. For example, the setting information is information of the receiving user who is to receive the file (for example, the receiving user's email address (destination), the domain of the receiving user's email address, the receiving user's account, etc.).

[0063] The setting unit 113 can set multiple pieces of setting information with different contents for one management unit. For example, the setting unit 113 can set multiple pieces of setting information with different information on the receiving user for one management unit. For example, for the management unit with management ID=001, first setting information in which the email address of user B is set and second setting information in which the email address of user C is set can be set.

[0064] In addition, the setting unit 113 can set information of a plurality of recipient users for one setting information. For example, for the management unit with the management ID=001, the email address and user ID of user B are set. The first setting information in which the email address of user D is set, and the second setting information in which the email addresses of user C and user E are set, are set.

[0065] Furthermore, for example, the setting information may include security information, and the setting unit 113 is capable of setting a plurality of pieces of setting information having different security information for one management unit.

[0066] Specifically, the setting information may be user authentication information of a recipient user who is to receive the file. Note that the user authentication information is an example of security information.

[0067] For example, the setting unit 113 can set multiple pieces of setting information with different user authentication information for one management unit. For example, for a management unit with management ID=001, first setting information that enables user authentication and sets the email address of user B, and second setting information including a second password that enables user authentication and sets the email address of user C can be set.

[0068] The setting information may be authentication information corresponding to the inquiry information (for example, information for password authentication). Note that the authentication information corresponding to the inquiry information is an example of security information.

[0069] For example, the setting unit 113 can set a plurality of pieces of setting information with different authentication information corresponding to the reference information for one management unit. For example, for a management unit with management ID=001, first setting information that enables password authentication and includes a first password for accessing the reference information, and second setting information that enables password authentication and includes a second password for accessing the reference information can be set.

[0070] In addition, after generating the query information, the setting unit 113 makes it possible to change the setting information corresponding to the query information. That is, the setting unit 113 makes it possible to change (for example, add, delete, and / or edit) a part or all of the setting information.

[0071] For example, the setting unit 113 makes it possible to change part or all of the receiving user's information (for example, email address) and security information corresponding to the inquiry information, based on the sending user's input information.

[0072] The reference information control unit 114 generates reference information corresponding to the management unit, and associates the reference information with the setting information set by the setting unit 113.

[0073] In particular, when a plurality of pieces of setting information are set in the setting unit 113, the query information control unit 114 of this embodiment generates different query information for each piece of setting information.

[0074] In addition, the query information control unit 114 can generate different query information for each piece of information of a receiving user. For example, the query information control unit 114 can generate the first query information based on the first setting information in which the email address of user B of the management unit of management ID=001 is set, and generate the second query information based on the second setting information in which the email address of user C of the management unit of management ID=001 is set.

[0075] Furthermore, the query information control unit 114 may be capable of generating different query information for each piece of security information.

[0076] For example, the query control unit 114 may be capable of generating different query information for each piece of user authentication information.

[0077] Furthermore, the query information control unit 114 may be capable of generating different query information for each piece of authentication information corresponding to the query information.

[0078] Furthermore, the query information control unit 114 may maintain the valid state (status) of the query information corresponding to the setting information, regardless of whether the setting information has been changed. In other words, when the status of the query information corresponding to the setting information is valid, the query information control unit 114 maintains the valid state regardless of whether the setting information has been changed. Note that, when the status of the query information corresponding to the setting information is invalid, the query information control unit 114 maintains the invalid state regardless of whether the setting information has been changed.

[0079] When the file control unit 115 receives access to query information (query information generated by the query information control unit 114) from a given user, it enables the user to receive a file managed in a management unit corresponding to the query information.

[0080] Here, "a user receives a file" means that a user who has accessed the reference information receives a file. To be more specific, "a user receives a file" means at least one of the following five cases:

[0081] In other words, "a user receives a file" means at least one of the following: (1) the terminal 20 of the user who accessed the inquiry information downloads the file to the memory area of ​​the terminal 20; (2) the terminal 20 of the user stores the file in the memory area of ​​the terminal 20; (3) the terminal 20 of the user presents (displays for viewing) the contents of the file on the display unit; (4) the terminal 20 of the user prints the contents of the file; and (5) the server 10 or the terminal 20 of the user stores the file in the memory area associated with the user ID of the user.

[0082] In addition, in (5), “storing a file in a storage area associated with the user ID of the user” means storing a file in a storage area on the Internet (on the cloud) that can be connected to the user's terminal 20 via the Internet and that is associated with the user ID of the user.

[0083] Furthermore, when multiple files exist in one management unit, file control unit 115 enables the user to receive the multiple files.

[0084] Furthermore, if the file is encrypted, the file control unit 115 decrypts the encrypted file and enables the user to receive the decrypted file.

[0085] Furthermore, when a user receives a file, file control unit 115 may perform anti-virus processing (processing to detect viruses (including malware) that infect a computer and remove the viruses) on the file.

[0086] When a file infected with a virus is detected by the antivirus processing, the notification unit 117 may notify the sending user of the infection information. The infection information is, for example, information about the file, information indicating that a file infected with a virus has been found by the antivirus processing, etc.

[0087] Furthermore, when an antivirus process detects a file infected with a virus, file control unit 115 may set the status (state) of the infected file managed by the management unit to invalid.

[0088] Furthermore, when an antivirus process detects a file infected with a virus, the management unit section 112 may forcibly set the status of all management units that contain the infected file to invalid.

[0089] In addition, if an anti-virus process detects a virus-infected file, the file control unit 115 may prohibit the destination user from receiving the file or all files associated with the management unit, regardless of the authentication result, etc.

[0090] In addition, when the file control unit 115 receives access to inquiry information from a given user, it authenticates the user based on the user authentication information of the receiving user, and if the authentication is permitted, enables the user to receive a file managed in a management unit corresponding to the inquiry information.

[0091] For example, when the file control unit 115 receives access to inquiry information from a given user, the file control unit 115 performs authentication processing of the user based on the user authentication information of the receiving user in the authentication control unit 116. Then, when it is determined that authentication of the user is permitted (i.e., when it is determined that the user is a legitimate user), it allows the user to receive a file managed by the management unit corresponding to the inquiry information.

[0092] On the other hand, if it is determined that authentication of the user is not permitted (i.e., if it is determined that the user is an unauthorized user), the user is not allowed to receive files managed by the management unit corresponding to the inquiry information.

[0093] In addition, when the file control unit 115 receives access to query information from a given user, it performs authentication (e.g., password authentication) based on the authentication information corresponding to the query information, and if the authentication is permitted, it enables the user to receive files managed by the management unit corresponding to the query information.

[0094] For example, when the file control unit 115 accepts access to the query information from a given user, the file control unit 115 performs authentication processing (e.g., password authentication processing) for the query information in the authentication control unit 116. Then, when it is determined that the authentication is permitted, it allows the user to receive files managed by the management unit corresponding to the query information. On the other hand, when it is determined that the authentication is not permitted, it does not allow the user to receive files managed by the management unit corresponding to the query information.

[0095] Furthermore, file control unit 115 may perform anti-virus processing on the file before storing the file.

[0096] Furthermore, file control unit 115 may prohibit a user from receiving a specific file based on instructions from the creator of the management unit (the sending user) or instructions from a specific user (such as a system manager or a receiving user's administrator).

[0097] In addition, the file control unit 115 may enable a specific user (system manager, administrator of the receiving user, etc.) to receive a file managed by the management unit corresponding to the inquiry information at the instruction of the creator of the management unit (sending user).

[0098] When receiving inquiry information from a user, the authentication control unit 116 judges whether or not the user authentication (e.g., email address authentication) is valid. If the user authentication is valid, the authentication control unit 116 compares the password received from the user with the email address registered on the server side. It is determined whether the password matches the password associated with the managed inquiry information, and if they match, authentication of the user is permitted, that is, the user is determined to be legitimate.

[0099] When receiving inquiry information from a user, the authentication control unit 116 judges whether or not the authentication for the inquiry information is valid. If the authentication is valid, the authentication control unit 116 judges whether or not the password received from the user matches the password associated with the inquiry information registered and managed on the server side, and if they match, permits authentication of the user. In other words, it judges that the user is legitimate.

[0100] The notification unit 117 notifies a given user of given information. Here, the "notification" means at least one of the following: the server 10 transmits (deliveries, distributes, relays, transfers) an e-mail (may be a mail magazine, etc.) transmitted and received by SMTP (Simple Mail Transfer Protocol) to the terminal 20; the server 10 transmits by a given protocol, not limited to SMTP; the server 10 issues a push notification; the server 10 presents (controls to display and make viewable) a given screen (banner display screen, notice screen, pop-up screen, etc.) of a given application; and the server 10 notifies by a web page, and indicates that the server 10 actively transmits to the user's terminal 20. Note that the server 10 may also transmit information to the requested terminal 20 in response to a request from the user's terminal 20, which is also one aspect of the "notification". Note that the push notification means displaying a message window in a partial area (such as the top edge) of the screen of the terminal (smartphone).

[0101] In addition, sending an e-mail includes the process of sending a received e-mail to another MTA via SMTP, the process of sending to a local delivery agent MDA (Mail Delivery Agent) for sending to a user who has an account in the same system in which server 10 is running, and the process of sending to a user who has an account in the same system in which server 10 is running without going through an MDA.

[0102] For example, the notification unit 117 may notify the query generated by the query control unit 114 to a recipient user corresponding to the query.

[0103] In addition, when the notification unit 117 receives access to the query information from a given user and the user authentication (email address authentication) is valid, it notifies the destination (email address) of the receiving user associated with the query information of the password (one-time password) associated with the query information.

[0104] The Web processing unit 120 performs processing to transmit (provide) data such as HTML (HyperText Markup Language) documents and images in response to requests from client software such as a Web browser installed in the terminal 20 via HTTP (Hypertext Transfer Protocol), and processing to receive data accepted by the Web browser of the terminal. The server then performs file processing, DB update processing, etc., based on information received from each terminal of the administrator or user.

[0105] The Web processing unit 120 may perform processing to send (provide) data for management settings, etc. to the administrator's terminal 20 in response to an access request from the Web browser of the administrator's terminal 20, and may also perform processing to receive information from the administrator's terminal 20.

[0106] That is, the Web processing unit 120 may add, delete, update, and the like each piece of data to the DB based on an input from the administrator. Note that only the administrator is given the authority to access the Web page (URL) for the administrator.

[0107] Furthermore, the Web processing unit 120 performs login processing and, in response to a request from the Web browser of the terminal 20, processing for presenting a Web page of information related to the logged-in user.

[0108] For example, the Web processing unit 120 may present a management unit creation screen, a URL creation screen, an editing screen, or the like in response to a request from a Web browser on the terminal 20 of the sending user.

[0109] For example, the Web processing unit 120 may present screens such as a user authentication screen, a password input screen, and a file receiving screen for downloading a file in response to a request from the Web browser of the terminal 20 of a given user who has accessed the query information.

[0110] Note that some or all of the processing of the processing unit 100 and the memory unit 170 may be executed by a single device, or each process may be distributed to different devices depending on the purpose of the process.

[0111] [3] Overview of the file management system The file management system of the present embodiment relates to control for managing files. Since the file management system transfers files, it may be called a file transfer system.

[0112] The file management system of this embodiment is made up of a server 10, a terminal 20 of a sending user who sends a file, and a terminal 20 of a receiving user who receives the file.

[0113] For example, as shown in Fig. 3, the server 10 transfers a file from the terminal 20A of the user A to the terminal 20B of the user B. In other words, the user A is a sending user (also called a sending user or a transfer source user) that sends the file, and the user B is a receiving user (also called a receiving user) that receives the file.

[0114] The terminal 20A of the user A transmits (uploads, etc.) a file to the server 10. Then, the server 10 stores the file transmitted from the terminal 20A of the user A in the file storage unit 175 and manages it.

[0115] Then, the server 10 sets a management unit for managing the files, and generates a URL (reference information) that can access the files in the management unit.

[0116] User A notifies User B of the URL using chat or email functions. In other words, the URL is shared with other users. User B can then access the URL and receive (download, view, print, etc.) the file sent by User A.

[0117] In this way, the file management system of this embodiment can provide a highly convenient service that allows the sending user to easily manage files. In addition, according to this embodiment, the receiving user is notified of an appropriate URL, so that the receiving user can also enjoy a highly convenient service.

[0118] In the following description, the present embodiment will be described in further detail. In the following description, unless otherwise specified, an example will be described in which a file is transferred from a terminal 20A of a sending user A to a terminal 20B of a receiving user B.

[0119] [4] File storage description First, a description will be given of a file storage process of the server 10. As shown in Fig. 4, the server 10 of this embodiment stores files (e.g., "Proposal A.pdf" and "Confidentiality Agreement.pdf") transmitted from the terminal 20A of the user A in response to an instruction from the user A in the file storage unit 175 of the server 10.

[0120] For example, user A causes terminal 20A to display screen 45 of the management unit of server 10. User A can then upload a file stored in terminal 20A to server 10 by dragging the file to upload area 46 on screen 45.

[0121] In other words, the screen 45 where user A uploads is a screen for storing one or more files to be managed in one management unit. The number of files to be managed in one management unit may be one, or two or more.

[0122] The number of files managed in one management unit may be limited to a predetermined number (for example, "20"). The size of the files may also be limited. For example, the size of one file may be limited to 20 GB (gigabytes) or less.

[0123] Fig. 5 shows an example of a screen 30 displayed on the terminal 20A of the user A after a file is uploaded. When the server 10 receives a file from the terminal 20A of the user A, as shown in Fig. 5, the server 10 presents (displays) a list of files managed in the management unit in the area 31 of the management unit screen 30 on the terminal 20A of the user A.

[0124] In this embodiment, when the server 10 receives a file from the terminal 20A of the user A and stores the file in the file storage unit 175, the server 10 may automatically encrypt the file and store the encrypted file in the file storage unit 175. In this way, security can be further improved.

[0125] [5] Description of management unit Then, based on an instruction from user A, server 10 sets a management unit for managing files (for example, "proposal A.pdf" and "non-disclosure agreement.pdf") transmitted from user A's terminal 20A.

[0126] The "management unit" is a unit for managing one or more files. The server 10 of this embodiment sets the management unit for managing files based on an instruction from the user A.

[0127] The server 10 also internally assigns a unique management ID (management identification information) to each management unit. For example, the server 10 assigns "001" to the management ID that manages the files (e.g., "Proposal A.pdf" and "Confidentiality Agreement.pdf") transmitted from the terminal 20A of the user A.

[0128] Furthermore, in this embodiment, it is possible to add and delete files to be managed in management units based on instructions from user A. Note that the management units in this embodiment are a different concept from folders and directories. For example, this simplifies file exchange and temporarily stores files in the storage area of ​​server 10. Note that it is not denied that the management units are the concepts of folders and directories. In other words, the management units may be folders and directories. The management units may also be rephrased as management frames, management areas, or transfers.

[0129] 6 shows an example of information about management units. The server 10 stores the file name, size, virus scan status, MD5 check, and other information about each file managed by the management ID (management ID=001). The management data storage unit 173 stores the checksum, expiration date, status indicating valid or invalid, and information on the creator (sending user) of the management unit (for example, the email address of sending user A).

[0130] The status indicates whether the management unit is valid or invalid. If the management unit is valid, the destination user can receive the file. On the other hand, if the status of the management unit is invalid, the server 10 prohibits the destination user from receiving the file stored in the file storage unit 175.

[0131] Also, for example, when the server 10 receives an instruction to invalidate the status of a management unit from a predetermined user, the server 10 may set the status to invalid.

[0132] The "predetermined user" is at least one of the user who created the management unit, the system administrator, and the user who is the creator's superior.

[0133] Furthermore, the server 10 may receive a management name corresponding to the management unit based on input information from the sending user, and set the management name in association with the management ID.

[0134] [6] Explanation of setting information Next, the setting information of this embodiment will be described. Here, the "setting information" is information used for generating a URL (link). For example, the "setting information" includes at least one of the following: a title related to the URL, a download limit, information on the receiving user, and security information (type of security).

[0135] For example, when user A clicks an instruction 33 for creating setting information (eg, a "Create URL" button 33) as shown in FIG. 5, a screen 34 for inputting setting information is displayed on the right side of the screen.

[0136] Before generating a URL, server 10 accepts input of setting information to be associated with the URL from user A. Then, when user A clicks create button 44, server 10 receives a URL creation instruction, management ID=001, and setting information from terminal 20A, and generates a URL based on the setting information. The generated URL is associated with management ID=001.

[0137] [6.1] Titles for URLs The server 10 accepts input of a title related to a URL from the user A. For example, as shown in Fig. 5, the user A inputs information such as "Sales Group" in the title field 35 for the files (e.g., "Proposal A.pdf" and "Confidentiality Agreement.pdf") managed by the management unit.

[0138] [6.2] Download limit The server 10 also accepts input of the download limit number from the user A. For example, the user A inputs "10" in the download limit number input field 36 as shown in Fig. 5. The download limit number indicates the number of times that a file managed in a management unit (e.g., "Proposal Document A.pdf", "Confidentiality Agreement.pdf") can be downloaded when the created URL is accessed.

[0139] That is, the server 10 sets a count number (initial value=0) in advance for each URL, and counts the count number every time a file is downloaded. That is, the count number is incremented by 1 every time a file is downloaded. For example, if the download limit number is "10," and the count number reaches "10," downloading of the file is prohibited thereafter. In this embodiment, a limit is imposed on the number of downloads, but a similar method may be used to limit the number of views, the number of prints, the number of times saved in a storage area, and the like.

[0140] [6.3] Recipient user information and user authentication information 5, user A can set information about the receiving user on screen 34. In this embodiment, when the information about the receiving user is set, user authentication of the receiving user is performed. Therefore, according to this embodiment, a high level of security can be achieved.

[0141] Here, the information on the receiving user is, for example, the receiving user's email address (for example, Buser@hennge.com) and the domain to which the receiving user belongs (for example, hennge.com).

[0142] In this embodiment, email address authentication is adopted as the user authentication. For example, email address authentication is processed as follows.

[0143] For example, user A sets the email address (e.g., Buser@hennge.com) of the recipient user (e.g., user B). Then, when a given user (e.g., user B) accesses the URL, the server 10 requests the user to input an email address. If the email address matches the set email address (e.g., Buser@hennge.com), the server 10 notifies the set email address (e.g., Buser@hennge.com) of the one-time password. In other words, only a legitimate recipient user (e.g., user B) who has been registered in advance can obtain this one-time password. The server 10 then requests the user to input a one-time password, and if the one-time password received from the user matches the one-time password managed by the server, the server 10 allows authentication as if the user is a legitimate user.

[0144] Also, for example, if user A sets a domain (e.g., hennge.com), the process is as follows: When a URL is accessed by a given user (e.g., user B), server 10 requests the user to input an email address. Then, if the domain of the email address accepted from the user matches the set domain, server 10 notifies the accepted email address of a one-time password. Then, server 10 requests the user to input a one-time password, and if the one-time password accepted from the user matches the one-time password managed by the server, server 10 permits authentication as a legitimate user.

[0145] A specific example of user A's input for email address authentication will be explained with reference to Fig. 5. If user A desires email address authentication, he or she checks check box 37. If check box 37 is checked, it means that email address authentication is valid, and if check box 37 is not checked, it means that email address authentication is invalid.

[0146] Then, User A decides whether or not to specify the recipient user for which email address authentication is to be performed, and inputs the decision. For example, as shown in FIG. 5, User A selects and inputs either one of the options 38 "Allow any email address" or 39 "Restrict to specified email addresses only."

[0147] If user A wishes to send to a specific user B, he or she selects the "Limit to specified email addresses only" option 39 and enters user B's email address (eg, Buser@hennge.com) in input field 40.

[0148] In other words, the email address authentication information in this embodiment is at least one of the following: information on whether email address authentication is valid or invalid, whether a receiving user for whom email address authentication is to be performed is specified, and, if a receiving user for whom email address authentication is to be performed is specified, information on the target receiving user (e.g., Buser@hennge.com).

[0149] When user A does not specify an email address and allows any email address to receive files, the user selects the option 38 "allow any email address."

[0150] "Allow any email address" means that the recipient user's email address is not specified, but when the user accesses the inquiry information, the user is requested to input an email address, a one-time password is notified to that email address, and authentication is performed based on the one-time password.

[0151] The one-time password in this embodiment is a password that is valid only once and is used for email address authentication.

[0152] The one-time password will now be described in detail. For example, a one-time password generation program that generates a one-time password with the same algorithm as that of the server 10 is installed in advance on the terminal 20, and authentication processing is performed using the one-time password. For example, the algorithm and seed number of the one-time password generation program installed on the terminal 20 and the one-time password generation program installed on the server 10 match. As a result, the one-time password generated on the terminal side and the password generated on the server 10 match. For example, the one-time password generation program generates a one-time password based on the time and seed number at a predetermined interval (for example, every 30 seconds). The server 10 then stores the generated one-time password in the storage unit 170 in association with a URL.

[0153] [6.4] Setting up password authentication User A can set password authentication for the URL on screen 34, as shown in Fig. 5. If password authentication is enabled for the URL, an even higher security level can be achieved. Note that password authentication is an example of authentication corresponding to the URL.

[0154] For example, user A can enable password authentication by checking the password authentication checkbox 41 and entering a password in the input field 42.

[0155] In other words, if the check box 41 is checked, it means that password authentication is set to enabled, and if the check box 41 is not checked, it means that password authentication is set to disabled. If password authentication is disabled, access to the receiving screen is possible without password authentication.

[0156] [7] URL generation 5, user A inputs setting information regarding the title, download limit, receiving user information, user authentication information, and password authentication information, and clicks the Create button 44. User A's terminal 20A then transmits the setting information to server 10 together with a URL creation instruction and a management ID (management ID=001). Then, upon receiving this information, server 10 generates a URL in association with the management ID based on the URL creation instruction. Then, server 10 associates the URL with the setting information and stores them in management data storage unit 173.

[0157] For example, the server 10 may access the URL https: / / hennge.com / te Generate st1.

[0158] That is, the server 10 generates referral information (e.g., a URL) to which a given user refers in order to receive (e.g., download) a file, i.e., the user needs the URL to obtain the file.

[0159] A URL is information generated based on a specific standard (URL format) and is an identifier for unique identification (also called UUID). A URL may also be called a link or hyperlink.

[0160] In addition, the email address of the creator, User A, and the file name may be encoded and entered in the parameter portion according to the URL format.

[0161] [8] URL and setting information management FIG. 7 shows an example of the URL and setting information stored in the storage unit 170 (for example, the management data storage unit 173) of the server 10. As shown in FIG.

[0162] As shown in FIG. 7, the server 10 stores the generated URL (https: / / hennge.com / test1) in the management data storage unit 173 in association with the management ID=001, for example.

[0163] Furthermore, the server 10 stores the setting information in the management data storage unit 173 in association with the URL (https: / / hennge.com / test1).

[0164] For example, when the server 10 receives an input of a title related to a URL from the terminal 20A of the user A, the server 10 sets "Sales Group" as the title in association with the URL (https: / / hennge.com / test1).

[0165] Furthermore, when the server 10 receives a download limit number (for example, "10") selected by the user A from the terminal 20A of the user A, the server 10 sets the download limit number to 10 in association with the URL (https: / / hennge.com / test1).

[0166] If the server 10 does not receive an input of the download limit number from the user A, it sets the limit to an initial value (for example, "100").

[0167] Furthermore, the server 10 sets information on the status of the email address authentication (for example, valid or invalid) in association with the URL (https: / / hennge.com / test1).

[0168] For example, enable is set to 1, and disable is set to 0. In the example of Figure 7, the email address authentication associated with the URL (https: / / hennge.com / test1) is set to enable (1).

[0169] In addition, the server 10 sets an option for email address authentication in association with the URL (https: / / hennge.com / test1). For example, the server 10 sets a value according to the option of "Allow any email address" or the option of "Limit to specified email addresses only." For example, the option of "Allow any email address" is set to "1," and the option of "Limit to specified email addresses only" is set to "2."

[0170] The server 10 accepts the option to "restrict to specified email addresses only" from the user A. In this case, as shown in Figure 7, set "2" as the email address authentication option to be associated with the URL (https: / / hennge.com / test1).

[0171] Furthermore, the server 10 sets the recipient user's email address in association with the URL (https: / / hennge.com / test1).

[0172] For example, when the server 10 receives information of the receiving user (e.g., the email address of user B) based on the input information of user A, it sets the email address of receiving user B (e.g., Buser@hennge.com) in association with the URL (https: / / hennge.com / test1).

[0173] The server 10 also sets the status information (for example, valid or invalid) of the password authentication of the URL (https: / / hennge.com / test1). For example, 1 is set for valid, and 0 is set for invalid.

[0174] When the server 10 receives information to enable password authentication from the user A, it sets the status of the password authentication associated with the URL (https: / / hennge.com / test1) to enabled (1) as shown in FIG.

[0175] The server 10 sets a password for password authentication, for example, in association with the management ID.

[0176] For example, when the server 10 receives a password (12Sdu6&23) from the user A, the server 10 sets "12Sdu6&23" as the password in association with the URL (https: / / hennge.com / test1) as shown in Fig. 7. Note that the password data stored in the management data storage unit 173 may not be the password itself, but may be a character string (such as a hash value) for determining the password.

[0177] In addition, when the server 10 accepts the request to disable email address authentication, it sets the email address authentication to invalid and enables the given user to receive files (e.g., "Proposal A.pdf" and "Confidentiality Agreement.pdf") managed by a management unit (e.g., management ID=001).

[0178] In addition, based on user A's instructions, the server 10 accepts the setting of validity of email address authentication, and if it further accepts option 38 of "allow any email address," it sets email address authentication to valid and sets "1" as the option for arbitrary email address authentication.

[0179] When the server 10 receives a request to disable password authentication, the server 10 sets the password authentication to be disabled.

[0180] The server 10 also sets a status indicating whether the URL itself is valid (1) or invalid (0). When generating a URL, the server 10 sets valid (1) in association with the URL.

[0181] [9] Display control of generated URL When the URL (https: / / hennge.com / test1) is generated in the server 10, the URL and the like are displayed on the terminal 20A of the user A. Fig. 8 shows an example of a screen 50 including the URL that is displayed on the terminal 20A.

[0182] For example, the server 10 presents the title (eg, "Sales Group"), the download limit (eg, "10"), and security information to the user A in the URL content display area 51 as shown in FIG.

[0183] For example, the server 10 presents information 54 indicating that the email address authentication of the designated recipient user is valid, and the recipient user's email address 55.

[0184] The server 10 also presents the generated URL 56. For example, "https: / / hennge.com / test1" is displayed as the generated URL. The server 10 also presents the user A with a message 57 used to notify the recipient user B.

[0185] User A can copy message 57 by clicking copy button 58. In this way, he can paste message 57 into the body of a given email or chat, and can easily inform user B of the URL.

[0186] Also, by user A clicking on the email creation button 59, the server 10 may automatically start an email creation application and create an email to include the message 57 in the body of the email. For example, an email may be created with user A's email address (Auser@hennge.com) as the sender and recipient user B's email address (Buser@hennge.com) as the destination.

[0187]

[10] Add URL In this embodiment, multiple URLs can be generated for one management unit. For example, as shown in Fig. 8, User A can input new setting information corresponding to the management unit (management ID = 001) by clicking the Create button 33 for creating a URL.

[0188] For example, when a setting information instruction 33 (e.g., the "Create URL" button 33) is clicked, a screen 80 for inputting new setting information is displayed on the right side of the screen, as shown in Fig. 9. Then, in the screen 80, User A can input new setting information.

[0189] That is, before generating a new URL, server 10 accepts input of setting information to be associated with the URL from user A. Then, when user A clicks create button 44, server 10 receives a URL creation instruction, management ID=001, and setting information from terminal 20A, and generates a new URL based on the setting information. The generated URL is associated with management ID=001.

[0190] Then, when the server 10 generates a URL (https: / / hennge.com / test2), the server 10 stores the setting information in the management data storage unit 173 in association with the URL (https: / / hennge.com / test2).

[0191] For example, as shown in FIG. 10, the server 10 sets a new title "support group" to be associated with the management ID=001 and the URL (https: / / hennge.com / test2), and sets "5" as the download limit number to be associated with the URL.

[0192] Furthermore, the server 10 sets email address authentication to valid (1) in association with the URL, and sets "2 (Limited to designated email address only)" as an option for email address authentication.

[0193] In addition, the server 10 may, for example, st2) The email addresses of the recipient users to be associated with are set to "Juser@hennge.com" for user J and "Kuser@hennge.com" for user K. For example, user J and user K are support staff.

[0194] Furthermore, the server 10 sets the password authentication associated with the URL (https: / / hennge.com / test2) to invalid (0), for example.

[0195]

[11] URL deletion 8, the server 10 can delete a given URL associated with a management unit based on an instruction from user A. For example, if user A wishes to delete the URL of "Sales Group", user A can delete the URL of "Sales Group" (https: / / hennge.com / test1) by clicking the delete button 63.

[0196] When the server 10 receives a deletion instruction from the user A regarding the URL, the server 10 deletes the URL and / or invalidates the status of the URL.

[0197] Furthermore, when the server 10 receives a deletion instruction from the user A regarding the URL, the server 10 may delete the setting information associated with the URL.

[0198]

[12] Change the setting information Server 10 can change the setting information on a per-URL basis even after the URLs are generated. Even if the setting information is changed, server 10 maintains the validity of the URL corresponding to the setting information. For example, when the status information of the URL corresponding to the setting information is valid (1), if the setting information is changed, the validity (1) of the URL is maintained. This eliminates the need to regenerate URLs, and enables file management that is highly convenient for users.

[0199] FIG. 11 shows an example of a screen for changing setting information related to a URL (https: / / hennge.com / test2). For example, user A can additionally specify user L's email address (Luser@ifpat.gr.jp) as the receiving user. In addition, user A selects (checks) password authentication to be enabled and enters a password (for example, "F8#syFs8"). User A's terminal 20A then clicks the Create button 44 to send a change instruction and the changed setting information to the server 10. When sending to the server 10, the management ID=001 and the URL (https: / / hennge.com / test2) are sent.

[0200] Upon receiving the information, the server 10 updates the setting information based on the changed setting information received from the terminal 20A in accordance with the change instruction, by associating the setting information with the URL (https: / / hennge.com / test2). For example, the receiving user information is set to "Juser@hennge.com, Kuser@hennge.com, Luser@hennge.com".

[0201] Also, associate it with the URL (https: / / hennge.com / test2), update password authentication to enabled (1), and set the password to "F8#syFs8".

[0202]

[13] Description of management unit Based on an instruction from user A, the server 10 can check, add, and delete management units, or check, add, and delete files managed in management units.

[0203] FIG. 12 is an example of a management unit history screen 90 displayed on the user A's terminal 20A. That is, the history screen 90 displays the management units created by user A. Note that, in each management unit, if a file has already been uploaded by the sending user, a sent mark 97 may be displayed. Note that, although not shown, the server 10 may display an invalid mark when the expiration date of the management unit has arrived or when the status of the management unit is invalid. Also, when the management unit has been deleted, a deleted mark may be displayed.

[0204] For example, user A selects a management unit that he or she wishes to edit from among the management units. Since the history screen 90 displays the file names managed by each management unit, user A can easily make a selection.

[0205] For example, as shown in FIG. 12, when user A selects management units 91, "Proposal A.pdf" and "Confidentiality Agreement.pdf", from among a plurality of management units, a details screen 92 for management unit 91 is displayed on the right side of the screen.

[0206] For example, server 10 presents to terminal 20A status information (e.g., valid or invalid) of the current management unit (management ID=001). The example in FIG. 12 shows that the management unit is valid. When the status of the management unit is valid, the recipient user (e.g., user B) can receive each file managed in that management unit. On the other hand, when the status of the management unit is invalid, the recipient user (e.g., user B) cannot receive each file managed in that management unit.

[0207] Also, for example, the server 10 presents the expiration date of the current management unit (management ID=001) and the creator (for example, the creator's email address) on the terminal 20A.

[0208] Also, for example, in area 95 of screen 90, server 10 presents information on the files managed in the current management unit (management ID=001) and the status of the files (e.g., valid or invalid), the virus scan status, and a button to delete the files.

[0209] If User A wishes to delete any file, he or she can delete the file by clicking the delete button for the relevant file.

[0210] For example, when user A clicks the delete button for "Proposal A.pdf", the server 10 deletes "Proposal A.pdf" from the file storage unit 175 based on the instruction of user A. Also, "Proposal A.pdf" is deleted from the screen 90 and displayed.

[0211] If user A wishes to add a file, he or she can perform an operation of dragging and dropping the file stored in terminal 20A into area 95, thereby additionally uploading the file to server 10.

[0212] For example, when the server 10 receives a new file "Clock-out management.pdf" based on an instruction from user A, the server 10 stores the file in the file storage unit 175, and the new file "Clock-out management.pdf" is additionally displayed in the area 95.

[0213] In this embodiment, the status of the generated URL is maintained regardless of whether a file is added or deleted in the management unit (management ID=001). For example, when the URL status is valid, the validity is maintained even if a file is added or deleted. Therefore, even after notifying the receiving user of the URL, it is possible to add a new file (e.g., "Clockout Management.pdf") or delete a file (e.g., "Proposal A.pdf"), realizing file management that is highly convenient for the sending user and the receiving user.

[0214] Also, for example, the server 10 may display a list of URLs generated in the current management unit (management ID=001) in the terminal 20A.

[0215] For example, the server 10 may present, at the bottom of the screen 90, information on the status of the URL (eg, valid or invalid), the title of the URL, the number of downloads / download limit, an edit button 93, and a delete button 96 for each URL.

[0216] Also, for example, user A can change the setting information regarding the support group URL by clicking the support group edit button 93. For example, the server 10 can edit (change) the setting information of the support group URL based on an instruction from user A (for example, clicking the edit button 93), as shown in FIG.

[0217] The server 10 may also present a URL creation button 94 for creating a new URL.

[0218] Although not shown, the server 10 may delete the management unit (e.g., management ID=001) based on an instruction from the creator of the management unit, user A. The server 10 may invalidate the status of the management unit (e.g., management ID=001) based on an instruction from the creator of the management unit, user A.

[0219] Furthermore, when the validity period of a management unit has elapsed, the server 10 sets the status of the management unit to invalid.

[0220]

[14] The role of URLs According to this embodiment, when there are multiple pieces of setting information in which at least one of the title, download limit number, user authentication information (e.g., information for email address authentication), and authentication information corresponding to the URL (e.g., information for site password authentication) is different, the server 10 of this embodiment generates a different URL for each piece of setting information.

[0221] Therefore, User A, who is the sending user, can input setting information with a high degree of freedom in response to the identification of the receiving user and the degree of security level, and can generate URLs with a variety of setting patterns.

[0222] For example, for users outside the company (e.g., users whose email address domain is not a specified domain), a URL can be generated with email address authentication and passwords set to enabled, and for users within the company (e.g., users whose email address domain is a specified domain), a URL can be generated with email address authentication and passwords set to disabled. In this way, User A can use different URLs depending on the settings. Therefore, in this embodiment, a highly convenient service can be provided to User A.

[0223]

[15] Flowchart The flow of processing by the server 10 will be described with reference to Fig. 13. For convenience of explanation, user A will be described as an example of a sending user.

[0224] First, the file transmitted from the terminal 20A of the user A is stored in management units (step S11).

[0225] Then, the setting information is accepted from the user A (step S12). It is determined whether or not an instruction to generate a URL is accepted from the user A (step S13).

[0226] When an instruction to generate a URL is received from user A (Y in step S13), a URL corresponding to the management unit is generated (step S14).

[0227] Then, the URL and the setting information are associated (step S15). Then, the generated URL is displayed to user A (step S16). If an instruction to generate a URL is not received from user A (N in step S13), the process returns to step S12. This ends the process.

[0228]

[16] Receiving files When the server 10 receives a URL access from a given user, the server 10 controls the user to receive the file. If the file is encrypted, the server 10 controls the user to decrypt the file and to receive the decrypted file.

[0229] [16.1] Download Limit If the number of downloads corresponding to the URL (e.g., https: / / hennge.com / test1) for which access has been accepted is equal to or less than the download limit (e.g., 10 or less), the server 10 allows the file to be received. After the file is received, the number of downloads is counted as 1.

[0230] If the number of downloads corresponding to the accessed URL has reached the download limit (for example, 10), the server 10 prohibits the reception of the file.

[0231] [16.2] Processing when user authentication is valid If the user authentication (eg, email address authentication) corresponding to the URL accessed by the user is valid, the server 10 presents the user with an input screen for an email address and a domain.

[0232] Then, the server 10 performs a user authentication process, and if authentication is permitted, presents a file reception screen on the terminal 20 of the user.

[0233] When the server 10 receives an instruction to receive a file from a user (e.g., user B) whose user authentication has been permitted, the server 10 transmits the file managed by the management unit associated with the URL to the terminal 20 of the user (e.g., user B). In other words, the user (e.g., user B) can receive (e.g., download) the file to the terminal 20 of the user.

[0234] When the server 10 has denied the user authentication, the server 10 does not present a file reception screen to the user's terminal 20. For example, the server 10 presents to the user's terminal 20 information indicating that the file cannot be received.

[0235] The authentication details are explained below. For the sake of convenience, an example of the process when an access to the URL (https: / / hennge.com / test1) with management ID=001 is accepted will be explained.

[0236] (1) Authentication process for the specified email address When the email address of the recipient user for which user authentication is to be performed is specified, the server 10 performs the following process.

[0237] First, the server 10 displays a screen for accepting input of an email address to the user. Present.

[0238] Then, when the server 10 accepts input of an email address from the user, it determines whether the accepted email address matches the email address (Buser@hennge.com) associated with the URL (https: / / hennge.com / test1) of management ID=001.

[0239] If the accepted email address matches the email address (Buser@hennge.com) associated with the URL (https: / / hennge.com / test1) for management ID=001, a password (one-time password) is generated based on a given encryption algorithm.

[0240] Then, the server 10 stores the generated password in the management data storage unit 173 in association with the URL.

[0241] In addition, the server 10 notifies the recipient user's email address (Buser@hennge.com) associated with the URL (https: / / hennge.com / test1) of the password.

[0242] In addition, even if a URL is received from user X, who is unrelated to user B, the password will be notified to the email address of the receiving user associated with the URL (Buser@hennge.com), preventing the password from being leaked to anyone other than user B.

[0243] The server 10 then presents a password entry screen to the user, and when it receives a password entry from the user, performs a password authentication process.

[0244] For example, the server 10 determines whether the password received from the user matches the password associated with the URL stored in the management data storage unit 173, and if they match, allows authentication, but if they do not match, denies authentication.

[0245] (2) Processing for designated domains When the domain of the recipient user for which user authentication is to be performed is specified, the server 10 performs the following process.

[0246] First, the server 10 presents the user with a screen for accepting input of an email address.

[0247] When the server 10 accepts input of an email address from a user, it determines whether the domain of the accepted email address matches the domain associated with the URL, and if they match, it generates a password (one-time password) based on a given encryption algorithm, associates it with the URL, and stores it in the management data storage unit 173.

[0248] The server 10 also notifies the user of the password to the email address from which the password was received. The server 10 then presents a password entry screen to the user, and performs password authentication processing when it receives a password entry from the user.

[0249] For example, the server 10 determines whether the password received from the user matches the password associated with the URL stored in the management data storage unit 173, and if they match, allows authentication, but if they do not match, denies authentication.

[0250] (3) Processing of any email address When an arbitrary email address is designated as a target for user authentication, the server 10 performs the following process.

[0251] First, the server 10 presents the user with a screen for accepting input of an email address.

[0252] When the server 10 receives an input of an email address from the user, the server 10 notifies the received email address of a password (one-time password) generated based on a given encryption algorithm. The server 10 stores the generated password in the management data storage unit 173 in association with a URL.

[0253] The server 10 then presents a password entry screen to the user, and when it receives a password entry from the user, performs a password authentication process.

[0254] For example, the server 10 determines whether the password received from the user matches the password associated with the URL stored in the management data storage unit 173, and if they match, allows authentication, but if they do not match, denies authentication.

[0255] In this way, when allowing any user to receive a file in management units, at least an email address is required, so the creator, User A, can find out who downloaded the file by viewing the download history, etc.

[0256] [16.3] Password authentication When the password authentication corresponding to the URL accessed by the user is valid, the server 10 presents a password entry screen to the user.

[0257] Then, when the server 10 receives a password input from the user, it determines whether the password received from the user matches the password associated with the URL, and if they match, it allows authentication, and if they do not match, it denies authentication.

[0258] If the password authentication is permitted, the server 10 presents a file reception screen to the terminal 20 of the user. Then, in the same manner as when the user authentication is permitted, the server 10 enables the user to receive files.

[0259] In this embodiment, when the email address authentication is valid and the password authentication is valid, the authentication process may be executed for both the email address authentication and the password authentication.

[0260] [16.4] When authentication is invalid If both the email address authentication and the password authentication are invalid, the server 10 allows the user who has accessed the reference information to receive the files managed by the management unit.

[0261] [16.5] Invalid URL When a given user accesses a URL, if the status of the URL is invalid, the server prohibits the user from accessing the URL and prohibits the user from receiving the file stored in the file storage unit 175. Note that the server prohibits the user from receiving the file regardless of whether or not the email address or password authentication of the site is permitted.

[0262] Also, for example, when the server 10 receives an instruction to invalidate the status of a URL from the user who created the URL or a specific user, the server 10 may set the status of the URL to invalid. In this way, even if the URL creator mistakenly uploads a file, it is possible to prevent information leakage of the file.

[0263]

[17] Controlling file status information The server 10 may set a status indicating whether the file managed by the management unit is valid or invalid. If the file is valid, the destination user is allowed to receive the file. On the other hand, if the file is invalid, the destination user is prohibited from receiving the file even if authentication (email address authentication and / or email address authentication) is permitted.

[0264] Furthermore, for example, when the server 10 receives an instruction to invalidate the status of a file from the user who created the file or a specific user, the server 10 may set the status to invalid.

[0265]

[18] Receiving files from a specific user The server 10 may control the file so that it can be received by a terminal of a specific user based on an instruction from the specific user.

[0266] When enabling a specific user to receive the message, user authentication (for example, email address authentication) may be performed to determine the legitimacy of the specific user using the various authentication methods described in the present embodiment.

[0267]

[19] Other examples of user authentication In the present embodiment, the example of adopting email address authentication as the user authentication has been described, but the present invention is not limited to this, and various other types of user authentication may be adopted. For example, the legitimacy of a user may be determined by telephone number authentication or authentication processing using a terminal device (smartphone) of the user.

[0268] Furthermore, the server 10 of the present embodiment may determine the authentication of a user by an external authentication server (authentication authority). For example, the authentication server is an authentication server such as Google (registered trademark).

[0269]

[20] Other examples of authentication corresponding to referral information (URL) In the present embodiment, an example has been described in which password authentication is adopted as authentication corresponding to the query information (URL), but the present invention is not limited to this, and various other types of user authentication may be adopted.

[0270]

[21] Recipient information In this embodiment, for example, as shown in FIG. 5, a method has been described in which when user A sets information about a receiving user on screen 34, user authentication of the receiving user is performed at the same time. However, it is also possible to set information about a receiving user without performing user authentication.

[0271] For example, user A sets the email address (e.g., Buser@hennge.com) of the recipient user (e.g., user B). Then, when a URL is accessed by a given user (e.g., user B), the server 10 requests the user to input an email address. When the email address received from the user matches the set email address (e.g., Buser@hennge.com), the server 10 may enable the user to receive a file managed in the management unit corresponding to the inquiry information.

[0272]

[22] In case of viral infection In this embodiment, it may be possible to forcibly invalidate the status of a management unit according to the state of each file set in that management unit.

[0273] For example, if a file (such as "Proposal A.pdf") set in the management unit of management ID=001 is infected with a virus, the status corresponding to management ID=001 is forcibly set to invalid.

[0274] If the status corresponding to management ID=001 is invalid, then regardless of the results of user authentication and password authentication, the destination user (e.g., user B) will be unable to receive the file in question (e.g., "Proposal A.pdf") or all files associated with management ID=001 (e.g., "Proposal A.pdf", "Confidentiality Agreement.pdf").

[0275] In other words, in this embodiment, if it is detected that at least one file (e.g., "proposal A.pdf") managed by management ID=001 is infected with a virus, the destination user (e.g., user B) will be prevented from receiving the file (e.g., "proposal A.pdf") or all files associated with management ID=001 (e.g., "proposal A.pdf", "non-disclosure agreement.pdf"), regardless of the results of user authentication and password authentication.

[0276] In this way, the status of the management unit can be invalidated depending on the status of the file, making it possible to provide a highly convenient service.

[0277]

[23] Other The present invention is not limited to the above-described embodiment, and various modifications are possible. For example, a term cited as a broadly defined or synonymous term in the description in the specification or drawings can be replaced with a broadly defined or synonymous term in other descriptions in the specification or drawings.

[0278] The present invention includes configurations that are substantially the same as the configurations described in the embodiments (for example, configurations with the same functions, methods and results, or configurations with the same purpose and effect). The present invention also includes configurations in which non-essential parts of the configurations described in the embodiments are replaced. The present invention also includes configurations that achieve the same effects as the configurations described in the embodiments or that can achieve the same purpose. The present invention also includes configurations in which publicly known technology is added to the configurations described in the embodiments.

[0279] Although the embodiments of the present invention have been described in detail as above, it will be easily understood by those skilled in the art that many modifications are possible without substantially departing from the novel features and effects of the present invention. Therefore, all such modifications are intended to be included within the scope of the present invention. [Explanation of symbols]

[0280] 10 Server, 20, 20A, 20B, 20C Terminal, 100 processing unit, 110 communication control unit, 111 storage processing unit, 112 management unit, 113 setting unit, 114 inquiry information control unit, 115 file control unit, 116 authentication control unit, 117 notification unit, 120 Web processing unit, 170 storage unit, 171 main memory unit, 172 user information memory unit, 173 management data memory unit, 175 file storage unit, 180 information storage medium, 196 communication unit

Claims

1. A program for causing a computer to perform file management processing, a storage processing unit that stores a file transmitted from a terminal of a transmitting user in a storage unit based on an instruction from the transmitting user; a management unit section for setting a management unit for managing the file; a setting unit that sets setting information based on input information of the sending user in association with the management unit; a query information control unit that generates query information corresponding to the management unit and associates the query information with the setting information; causing a computer to function as a file control unit that enables a given user to receive, when access to the inquiry information is received from the given user, the file managed in the management unit corresponding to the inquiry information; The setting unit is A plurality of pieces of setting information can be set for one of the management units, the setting information being different in at least one of the user authentication information of a receiving user who is a target for receiving a file and the authentication information corresponding to the inquiry information; The inquiry information control unit: When a plurality of pieces of setting information are set for one of the management units in the setting unit, different reference information is generated for each piece of setting information; The setting unit is For one of the management units, for an external user, setting information can be set by validating authentication information corresponding to the user authentication information and the inquiry information, and for an internal user, setting information can be set by invalidating authentication information corresponding to the user authentication information and the inquiry information; The inquiry information control unit: A program capable of generating different inquiry information for a single management unit between an external user and an internal user.

2. In claim 1, The file control unit A program characterized by the fact that, when access to inquiry information is received from a given user, if user authentication corresponding to the inquiry information is valid, the program authenticates the user, and if the authentication is permitted, allows the user to receive the file.

3. In claim 1, The file control unit A program characterized by, when access to inquiry information is received from a given user, performing authentication if authentication corresponding to the inquiry information is valid, and allowing the user to receive the file if the authentication is permitted.

4. In claim 1, The setting unit is After generating the inquiry information, the setting information corresponding to the inquiry information is made changeable; The inquiry information control unit: A program characterized in that, regardless of changes to setting information, a valid state of reference information corresponding to the setting information is maintained.

5. In claim 1, The management unit includes: A program for forcibly invalidating a state of a management unit according to a state of the file set in the management unit.

6. A server that performs file management processing, a storage processing unit that stores a file transmitted from a terminal of a transmitting user in a storage unit based on an instruction from the transmitting user; a management unit section for setting a management unit for managing the file; a setting unit that sets setting information based on input information of the sending user in association with the management unit; a query information control unit that generates query information corresponding to the management unit and associates the query information with the setting information; a file control unit that enables a given user to receive, when access to the query information is received from the given user, the file that is managed in the management unit that corresponds to the query information; The setting unit is A plurality of pieces of setting information can be set for one of the management units, the setting information being different in at least one of the user authentication information of a receiving user who is a target for receiving a file and the authentication information corresponding to the inquiry information; The inquiry information control unit: When a plurality of pieces of setting information are set for one of the management units in the setting unit, different reference information is generated for each piece of setting information; The setting unit is For one of the management units, for an external user, setting information can be set by validating authentication information corresponding to the user authentication information and the inquiry information, and for an internal user, setting information can be set by invalidating authentication information corresponding to the user authentication information and the inquiry information; The inquiry information control unit: A server capable of generating different inquiry information for a single management unit for users inside and outside the company.

7. A file management method in which a server performs file management processing, Based on the instruction of the sending user, the file transmitted from the terminal of the sending user is stored in the storage unit. and storing the setting a management unit for managing the file; setting setting information based on input information of the sending user in association with the management unit; generating query information corresponding to the management unit; A step of associating the query information with the setting information; when an access to the inquiry information is accepted from a given user, the step of enabling the given user to receive the file managed in the management unit corresponding to the inquiry information, The step of setting the setting information includes: A plurality of pieces of setting information can be set for one of the management units, the setting information being different in at least one of the user authentication information of a receiving user who is a target for receiving a file and the authentication information corresponding to the inquiry information; The generating step includes: When a plurality of pieces of setting information are set for one of the management units in the step of setting the setting information, different reference information is generated for each piece of setting information; The step of setting the setting information includes: For one of the management units, for an external user, setting information can be set by validating authentication information corresponding to the user authentication information and the inquiry information, and for an internal user, setting information can be set by invalidating authentication information corresponding to the user authentication information and the inquiry information; The generating step includes: A file management method comprising the steps of: making it possible for an external user and an internal user to generate different inquiry information for one of said management units.

Images