JP2014199626A - Providing program, providing device, and providing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a providing program and the like capable of reliably providing to a recipient a content at a storage destination indicated by a storage destination address written in email text.SOLUTION: When mail text includes a URL indicating a storage destination of a content and a sharing server 5 detects a lock request for storing the content at the URL in a saving destination folder from a client at a transmission source or a transmission destination, the sharing server 5 accesses the URL, obtains the content, and stores the content in the saving destination folder. The sharing server further stores the URL and a saving destination URL in association with each other in a content management table. When detecting a request to refer to the content stored in the storage destination indicated by the URL from the client at the transmission destination, the sharing server refers to the content management table to provide a saving destination URL corresponding to the URL to the client who made the reference request.

Description

  The present invention relates to a providing program, a providing apparatus, and a providing method.

  In some cases, the sender transmits the mail by describing a URL (Uniform Resource Locator), which is a storage address indicating the storage destination of the content, in the mail text. Furthermore, the recipient who receives the mail may access the URL storage location described in the mail text using the OS hyperlink function.

  At this time, if the storage destination content indicated by the URL is a third-party home page, the content may be changed by the third party. Moreover, the timing of the change depends on the third party. Accordingly, the content stored in the URL storage location may be different between the time when the sender sends the mail describing the URL and the time when the receiver receives the mail describing the URL.

  FIG. 15 is an explanatory diagram illustrating an example of a content screen when a click operation is performed on a URL described on the mail reference screen. The mail reference screen shown in FIG. 15 is, for example, a mail reference screen received from Mr. A. For example, suppose that Mr. A describes a URL indicating the storage location of the content in the mail text in order to introduce the content related to the recipe of the omelet rice. Accordingly, when the terminal device on the receiver side detects a click operation on the URL described in the mail body of the received mail from Mr. A, it accesses the storage location indicated by the URL and acquires the content stored in the storage location. To do. As a result, the recipient can view the contents of the recipe of the omelet rice stored in the storage location indicated by the URL.

International Publication No. 2006/046395 JP 2000-215127 A

  However, a third party who manages the content of the storage location indicated by the URL changes the content of the content from, for example, an omelet rice recipe to a mapo tofu recipe before the recipient accesses the storage location indicated by the URL. Suppose that it has changed. In this case, the receiver browses the content of the mapo tofu recipe stored in the storage location indicated by the URL, contrary to the intention of the sender. That is, a situation occurs in which the content intended by Mr. A who is the sender cannot be provided to the receiver.

  In one aspect, an object of the present invention is to provide a providing program, a providing apparatus, and a providing method capable of providing a recipient with storage destination information indicated by a storage destination address described in a mail text.

  In one proposal, when the computer has a first storage destination address indicating the storage destination of information in the mail body of the mail, the first storage destination address is sent from the terminal device of the mail transmission source or transmission destination. A process for detecting a storage request to the storage unit for information stored in the storage location indicated is executed. When the computer detects a storage request, the computer accesses the first storage destination address to acquire information, and executes processing for storing the acquired information in the storage unit. The computer is caused to execute processing for associating the first storage destination address with the second storage destination address indicating the storage destination of the storage unit storing the information in the management storage unit. When the computer detects a reference request for information stored in the storage destination indicated by the first storage destination address from the terminal device to which the mail is sent, the management storage unit is referenced and the first storage destination address is supported. A process of providing the second storage destination address to the terminal device that has requested the reference request is executed.

  The storage location information indicated by the storage location address described in the mail text can be provided to the recipient.

FIG. 1 is an explanatory diagram showing an example of a mail management system. FIG. 2 is an explanatory diagram illustrating an example of a content management table. FIG. 3 is an explanatory diagram illustrating an example of a link table. FIG. 4A is an explanatory diagram illustrating an example of a mail creation screen. FIG. 4B is an explanatory diagram illustrating an example of a menu screen on the mail creation screen. FIG. 4C is an explanatory diagram illustrating an example of a mail creation screen after a lock button operation. FIG. 5A is an explanatory diagram illustrating an example of a mail reference screen. FIG. 5B is an explanatory diagram illustrating an example of a menu screen on the mail reference screen. FIG. 5C is an explanatory diagram illustrating an example of a mail reference screen after a lock button operation. FIG. 6 is an explanatory diagram showing an example of the mail reference screen and the content screen after the reference button operation. FIG. 7 is an explanatory diagram showing an example of the forwarded mail reference screen and the content screen after the reference button operation. FIG. 8 is a flowchart illustrating an example of a processing operation of the control unit on the client side related to the menu screen display process. FIG. 9 is a flowchart illustrating an example of a processing operation of the control unit on the client side related to the lock request processing. FIG. 10 is a flowchart illustrating an example of the processing operation of the control unit on the shared server side involved in the lock processing. FIG. 11 is a flowchart illustrating an example of the processing operation of the client-side control unit related to the reference request processing. FIG. 12 is a flowchart illustrating an example of the processing operation of the control unit on the shared server side involved in the content list transmission processing. FIG. 13 is a flowchart showing an example of the processing operation of the control unit on the mail server side related to the outgoing mail link processing. FIG. 14 is an explanatory diagram illustrating an example of an information processing apparatus that executes a provided program. FIG. 15 is an explanatory diagram illustrating an example of a content screen when a click operation is performed on a URL described on the mail reference screen.

  Hereinafter, embodiments of a providing program, a providing apparatus, and a providing method disclosed in the present application will be described in detail based on the drawings. The disclosed technology is not limited by the present embodiment. Moreover, you may combine suitably each Example shown below in the range which does not cause contradiction.

  FIG. 1 is an explanatory diagram showing an example of a mail management system. A mail management system 1 shown in FIG. 1 includes a client 2, a mail server 3, a Web server 4, and a shared server 5. The client 2, the mail server 3, the Web server 4, and the shared server 5 are connected to each other via the Internet. It is connected at 6 mag.

  The client 2 is an information terminal such as a personal computer or a smartphone on the user side having a mail browser function, a web browser function, or the like. The client 2 includes a communication interface 11, an operation unit 12, a display unit 13, a storage unit 14, a ROM (Read Only Memory) 15, a RAM (Random Access Memory) 16, and a control unit 17. The communication interface 11 is an interface that manages communication with the Internet 6 and the like. The operation unit 12 is an input interface such as a mouse or a touch panel for inputting various commands. The display unit 13 is, for example, an output interface that displays various types of information on the screen. The storage unit 14 is a storage area for storing and managing various types of information. The storage unit 14 stores an operating environment table 14A. For example, the URL address of the shared server 5 is stored in the operating environment table 14A. The ROM 15 is an area that stores information such as various programs. Examples of the various programs include a mail browser program 15A, a web browser program 15B, and a request program 15C. The RAM 16 is an area that stores various information.

  The control unit 17 controls the entire client 2. The control unit 17 reads out various programs 15A to 15C stored in the ROM 15, and executes various processes as functions based on these programs 15A to 15C. The control unit 17 includes a mail browser processing unit 17A, a Web browser processing unit 17B, and a request processing unit 17C as functions.

  The mail browser processing unit 17 </ b> A is, for example, a processing unit that manages a mail browser function that communicates with the mail server 3. The web browser processing unit 17B is a processing unit that manages a web browser function that communicates with the web server 4, for example. The request processing unit 17C is, for example, a processing unit that requests the shared server 5 to perform various processes and displays various information such as contents provided by the shared server 5 on the display unit 13 on the screen.

  The mail server 3 is, for example, a server that manages mail transmission / reception from the client 2. The mail server 3 includes a communication interface 21, a storage unit 22, a ROM 23, a RAM 24, and a control unit 25. The communication interface 21 is an interface that manages communication with the Internet 6 and the like. The storage unit 22 is a storage area for storing and managing various types of information. The storage unit 22 stores an operating environment table 22A. The ROM 23 is an area that stores information such as various programs. Examples of the various programs include a mail server program 23A and a transmission mail link program 23B. The RAM 24 is an area that stores various information.

  The control unit 25 controls the entire mail server 3. The control unit 25 reads out various programs 23A and 23B stored in the ROM 23, and executes various processes as functions based on these programs 23A and 23B. The control unit 25 includes a mail server processing unit 25A and a transmission mail link processing unit 25B as functions. The mail server processing unit 25 </ b> A is a processing unit that controls the mail server function of the mail server 3, for example. The outgoing mail link processing unit 25B performs outgoing mail link processing described later.

  The Web server 4 is a server that provides a Web service such as content stored in a URL link destination to the client 2 or the like, for example.

The shared server 5 includes a communication interface 31, a storage unit 32, a ROM 33, a RAM 34, and a control unit 35. The communication interface 31 is an interface that manages communication with the Internet 6 and the like. The storage unit 32 is a storage area for storing and managing various types of information.
The ROM 33 is an area that stores information such as various programs. Examples of the various programs include a Web server program 33A, a lock program 33B, and a provision program 33C. The RAM 34 is an area that stores various information. The control unit 35 controls the entire shared server 5.

  The control unit 35 reads out various programs 33A to 33C stored in the ROM 33, and executes various processes as functions based on these programs 33A to 33C. The control unit 35 includes a Web server processing unit 35A, a lock processing unit 35B, and a provision processing unit 35C as functions. The web server processing unit 35A is, for example, a processing unit that provides a web service to a client. When the lock processing unit 35B detects a lock request related to the URL from the client 2 related to the mail when there is a URL indicating the storage destination of the content in the mail text, the lock processing unit 35B accesses the storage destination indicated by the URL and accesses the content To get. Further, the lock processing unit 35B stores a copy of the acquired content in a storage destination folder in the shared folder 34. Locking is a process of saving a copy of the content at the URL storage location described in the mail text when the lock is requested. Further, the lock processing unit 35B stores the URL related to the mail and the storage destination URL indicating the storage folder in the storage unit 32 in association with each other. The lock processing unit 35B is, for example, a storage processing unit or a management processing unit.

  When the provision processing unit 35C detects a reference request related to the URL from the client 2, the provision processing unit 35C refers to the storage unit 32 and provides a storage destination URL corresponding to the URL to the client 2 of the reference request.

  The storage unit 32 includes a content management table 41, a link table 42, and a shared folder 43. FIG. 2 is an explanatory diagram showing an example of the content management table 41. The content management table 41 shown in FIG. 2 stores content management information, and stores a content management key 41A, a saver 41B, a save date and time 41C, an original URL 41D, and a save destination URL 41E in association with each other. The content management key 41A is an ID for identifying content. The saver 41B is identification information such as an e-mail address that identifies a saver who has requested to save the content. The storage date and time 41 </ b> C is the date and time when the copy of the content is stored in the storage destination folder in the shared folder 43. The original URL 41D is a URL indicating the original storage destination where the content is stored. The storage destination URL 41E is a storage destination URL indicating a storage destination folder in the shared folder 43 that stores a copy of the content in response to the lock request.

  FIG. 3 is an explanatory diagram showing an example of the link table 42. The link table 42 shown in FIG. 3 manages the link information of the content management key and the message ID, and manages the message ID 42A, the URL 42B, and the content management key 42C in association with each other. The message ID 42A is an ID for identifying the original mail that describes the URL indicating the storage location of the content. The URL 42B is a URL indicating the original storage location where the content is stored. The content management key 42C is an ID for identifying content. The content management table 41 and the link table 42 correspond to, for example, a management storage unit. The shared folder 43 is an area for storing a copy of the storage destination content indicated by the URL in response to the lock request. The shared folder 43 corresponds to, for example, a storage unit.

  FIG. 4A is an explanatory diagram illustrating an example of the mail creation screen 50. A mail creation screen 50 shown in FIG. 4A is a screen for creating a mail by the client 2 on the sender side. The mail creation screen 50 includes a destination 50A, a subject 50B, a mail text 50C, and a send button 50D. The destination 50A is a mail transmission destination. The subject 50B is the subject of the mail. The mail text 50C is the contents of the mail text. The send button 50D is a button for instructing transmission of this mail. In the mail text 50C, a URL 50E, for example, a URL indicating the storage location of the content introducing the omelet rice recipe is described.

  FIG. 4B is an explanatory diagram illustrating an example of the menu screen 51 on the mail creation screen 50. For example, when the control unit 17 on the client 2 side selects a range of the URL 50E in the mail text 50C and detects a click, it displays a menu screen 51 on the mail creation screen 50 shown in FIG. 4B. The menu screen 51 includes a lock button 51A and a reference button 51B. The lock button 51A is a button for requesting a lock on the storage destination content indicated by the URL 50E. The reference button 51B is a button for referring to locked content. Since the mail creation screen 50 is a screen for newly creating the mail text 50C, the operation of the reference button 51B is invalidated.

  FIG. 4C is an explanatory diagram illustrating an example of the mail creation screen 50 after the lock button 51A is operated. When detecting an operation on the lock button 51A on the menu screen 51 shown in FIG. 4C, the control unit 17 requests the shared server 5 to lock the storage destination content indicated by the URL 50E in the mail text 50C. Then, after the lock request, the control unit 17 acquires the content management key from the shared server 5 and adds the content management key 50F to the head portion of the URL 50E in the mail body 50C.

  FIG. 5A is an explanatory diagram illustrating an example of the mail reference screen 60. The mail reference screen 60 shown in FIG. 5A is a screen for referring to the received mail by the client 2 on the receiver side. The mail reference screen 60 includes a destination 50A, a subject 50B, a mail text 50C, a reply button 50G, and a transfer button 50H. The reply button 50G is a button for instructing a reply of this mail. The transfer button 50H is a button for instructing transfer of this mail.

  FIG. 5B is an explanatory diagram illustrating an example of the menu screen 51 on the mail reference screen 60. For example, when the range is selected in the URL 50E in the mail text 50C and the click is detected, the control unit 17 displays the menu screen 51 on the mail reference screen 60 shown in FIG. 5B. The reference button 51B on the mail reference screen 60 is in an operable state.

  FIG. 5C is an explanatory diagram illustrating an example of the mail reference screen 60 after the lock button 51A is operated. When detecting an operation on the lock button 51A on the menu screen 51 of the mail reference screen 60 shown in FIG. 5C, the control unit 17 requests the shared server 5 to lock the content corresponding to the storage location indicated by the URL 50E in the mail body 50C. To do.

  FIG. 6 is an explanatory diagram illustrating an example of the mail reference screen 60 and the content screen 53 after the reference button 51B is operated. When the control unit 17 detects an operation on the reference button 51B on the menu screen 51 on the mail reference screen 60, the control unit 17 displays a content list 52 described later on the screen. The content list 52 is a list that displays a list of locked contents 52A of the URL 51E in the mail body 51C. Note that the content 52A in the content list 52 indicates a saver and save date and time related to the content for each lock request related to the same URL 51E. When the control unit 17 detects a selection operation for the content 52A on the content list 52, the control unit 17 accesses the storage destination URL related to the selected content 52A, acquires the content, and displays the content screen 53 on the screen.

  FIG. 7 is an explanatory diagram showing an example of the forwarded mail reference screen 61 and the content screen 53 after the reference button 51B is operated. When the control unit 17 detects an operation on the reference button 51B on the menu screen 51 of the forwarded mail reference screen 61, the control unit 17 displays the content list 52 on the screen. The content list 52 is a list that displays a list of locked contents 52A of the URL 51E in the mail body 51C. When the control unit 17 detects a selection operation for the content 52A on the content list 52, the control unit 17 accesses the storage destination URL related to the selected content 52A, acquires the content, and displays the content screen 53 on the screen.

  Next, the operation of the mail management system 1 according to the embodiment will be described. FIG. 8 is a flowchart showing an example of the processing operation of the control unit 17 on the client 2 side related to the menu screen display processing. The menu screen display process shown in FIG. 8 is a process for displaying the menu screen 51 in accordance with the selection or input operation of the URL 50E on the screen.

  In FIG. 8, the control unit 17 on the client 2 side determines whether selection or input for the URL 50E on the screen has been detected (step S11). For example, the control unit 17 selects a range of the URL 50E illustrated in FIG. 4A and detects selection of the URL 50E by a click operation or the like. The control unit 17 detects an input to the URL 50E by a line feed code input after the URL 50E is input. When the selection or input of the URL 50E is detected (Yes at Step S11), the control unit 17 determines whether or not the current display screen is a mail editor window (Step S12). The mail editor window is a mail editing screen.

  When it is a mail editor window (Yes at Step S12), the control unit 17 loads a menu screen (Step S13). The menu screen 51 has a lock button 51A and a reference button 51B shown in FIG. 4B or 5B.

  The control unit 17 determines whether or not the mail editor window is the mail creation screen 50 (step S14). For example, the control unit 17 determines whether the mail creation screen 50 is displayed based on the presence / absence of the send button 50D on the mail editor window. In the case of the mail creation screen 50 shown in FIG. 4A (Yes at Step S14), the control unit 17 invalidates the reference button 51B on the menu screen 51 as shown in FIG. 4B (Step S15). Note that the invalidation of the reference button 51B indicates an inoperable state, and a button non-display state may be used.

  The control unit 17 displays the menu screen 51 in which the reference button 51B is invalidated on the display unit 13 (step S16), and ends the processing operation illustrated in FIG. If the selection or input for the URL 50E is not detected (No at Step S11), or if it is not a mail editor window (No at Step S12), the control unit 17 ends the processing operation shown in FIG.

  When the mail editor window is not the mail creation screen 50 (No at Step S14), the control unit 17 determines that the mail editor window is the mail reference screen 60 shown in FIG. 5A and displays the menu screen 51 shown in FIG. 5B on the screen. The process proceeds to step S16.

  When the control unit 17 of the menu screen display process illustrated in FIG. 8 detects a selection or input operation on the URL 50E, in the case of the mail creation screen 50, the control unit 17 displays the menu screen 51 in which the reference button 51B is invalidated. As a result, the user on the client 2 side can operate the lock button 51 </ b> A on the menu screen 51 in the mail creation screen 50.

  When the control unit 17 detects a selection or input operation on the URL 50E, in the case of the mail reference screen 60, the control unit 17 displays the menu screen 51 on the screen. As a result, the user on the client 2 side can operate the lock button 51A and the reference button 51B on the menu screen 51 in the mail reference screen 60.

  FIG. 9 is a flowchart showing an example of the processing operation of the control unit 17 on the client 2 side related to the lock request processing. The lock request process shown in FIG. 9 is a process for requesting the shared server 5 to lock the content stored in the storage location indicated by the currently selected URL 50E when the operation of the lock button 51A on the menu screen 51 is detected.

  In FIG. 9, the request processing unit 17C in the control unit 17 on the client 2 side determines whether an operation on the lock button 51A on the menu screen 51 has been detected (step S21). When the request processing unit 17C detects an operation on the lock button 51A (Yes at Step S21), the request processing unit 17C determines whether or not the current display screen is the mail reference screen 60 illustrated in FIG. 5C (Step S22).

  In the case of the mail reference screen 60 (Yes at Step S22), the request processing unit 17C reads the mail header on the mail reference screen 60 (Step S23). The request processing unit 17C determines whether or not a Reference phrase exists in the mail header on the mail reference screen 60 (step S24). In the Reference phrase, a message ID for identifying the message history in the mail is recorded.

  When the Reference phrase exists (Yes at Step S24), the request processing unit 17C extracts the message ID for identifying the first sender mail in the Reference phrase, that is, the original message ID. Then, the request processing unit 17C sets the extracted message ID as the parameter α (step S25). The message ID of the parameter α is an ID for identifying the sender mail that first describes the URL 50E.

  The request processing unit 17C sets the selected URL 50E as the parameter β and its own mail address as the parameter γ (step S26). The URL 50E of the parameter β is a URL currently selected by the user of the client 2. The mail address of parameter γ is a mail address that identifies the user of the client 2 who operated the lock button 51A.

  The request processing unit 17C requests the shared server 5 to lock the content (step S27). The request processing unit 17C requests the shared server 5 for a lock request including the parameters α, γ, and β. In addition, when requesting the lock of the content of the URL 50E in the mail reference screen 60, the request processing unit 17C includes the original message ID as a parameter α in the lock request. When requesting the lock of the content of the URL 50E in the mail creation screen 50, the request processing unit 17C includes “no set value” as the parameter α in the lock request.

  The request processing unit 17C determines whether or not the content management key for the lock request has been received from the shared server 5 (step S28). When the request processing unit 17C receives the content management key (Yes at Step S28), the request processing unit 17C determines whether or not the current display screen is the mail creation screen 50 (Step S29).

  When the current display screen is the mail creation screen 50 (Yes at Step S29), the request processing unit 17C displays the content management key 50F at the head of the selected URL 50E in the mail text 50C in the mail creation screen 50 shown in FIG. 4C. Is added (step S30). Since the user displays the content management key 50F in the mail text 50C in the mail creation screen 50, the user can identify the content lock URL 50E. The request processing unit 17C closes the menu screen 51 (step S31), and ends the processing operation illustrated in FIG.

  When the request processing unit 17C does not detect an operation on the lock button on the menu screen 51 (No in step S21), the request processing unit 17C ends the processing operation illustrated in FIG. If the current display screen is not the mail reference screen 60 (No at Step S22), the request processing unit 17C proceeds to Step S26 in order to set the currently selected URL 50E and mail address to the parameters β and γ.

  When the reference phrase does not exist (No at Step S24), the request processing unit 17C sets the message ID to the parameter α (Step S32), and sets the selected URL 50E and the mail address to the parameters β and γ at Step S26. Migrate to

  When the request processing unit 17C has not received the content management key (No at Step S28), the request processing unit 17C proceeds to Step S28 to determine whether or not the content management key has been received. If the current display screen is not the mail creation screen 50 (No at Step S29), the request processing unit 17C proceeds to Step S31 to close the menu screen 51. That is, when the current display screen is the mail reference screen 60, the request processing unit 17C closes the menu screen 51 without executing the process of step S30 for adding the content management key 50F to the currently selected URL 50E.

  When the control unit 17 of the lock request process shown in FIG. 9 detects an operation on the lock button 51A on the mail reference screen 60, the control unit 17 generates a lock request including the original message ID in the mail reference screen 60, the selected URL 50E, and the mail address. Request to shared server 5. As a result, the user of the client 2 can request the shared server 5 to lock the content related to the URL 50E in the mail text 50C on the mail reference screen 60.

  When the control unit 17 detects an operation on the lock button 51 </ b> A on the mail creation screen 50, the control unit 17 sends a lock request including the selected URL 50 </ b> E, the mail address, and the original message ID set value in the mail creation screen 50 to the shared server 5. Request. As a result, the user on the client 2 side can request the shared server 5 to lock the content related to the URL 50E in the mail text 50C on the mail creation screen 50.

  Furthermore, when the content management key is received from the shared server 5 in response to the lock request, the control unit 17 adds the content management key 50F to the head portion of the URL 50E in the mail text 50C on the mail creation screen 50 and displays it. . As a result, the user on the client 2 side can identify the content lock URL 50E on the mail creation screen 50.

  FIG. 10 is a flowchart illustrating an example of the processing operation of the control unit 35 on the shared server 5 side related to the lock processing. The lock process shown in FIG. 10 is a process of accessing the storage location indicated by the URL 50E of the lock request and saving a copy of the content in the save destination folder in the shared folder 43.

  In FIG. 10, the lock processing unit 35B in the control unit 35 on the shared server 5 side determines whether or not a lock request has been received from the client 2 (step S41). The lock request includes the original message ID or “no set value” in the parameter α, the URL 50E in the parameter β, and the mail address in the parameter γ.

  When the lock processing unit 35B receives the lock request (Yes at Step S41), the lock processing unit 35B generates a storage destination folder for storing the storage destination content indicated by the URL 50E in the shared folder 43 in the storage unit 32 (Step S42). The lock processing unit 35B accesses the URL 50E of the lock request and acquires content (step S43). The lock processing unit 35B stores the acquired content in the storage destination folder (step S44), and generates a content management key (@key) for identifying the content (step S45).

  The lock processing unit 35B adds the set record to the content management table 31 (step S46). The set record includes @key for the content management key 41A, γ (mail address) for the saver 41B, the current time for the save date 41C, β (URL character string) for the original URL 41D, and the save destination folder 41E for the save destination URL 41E. A record in which a URL is set. As a result, the lock processing unit 35B refers to the content management table 41 and sets the content management key 41A, the saver 41B, the save date and time 41C, the original URL 41D, and the save destination URL 41E for each content of the URL 50E saved in the save destination folder. Can be identified.

  After adding a new record to the content management table 41, the lock processing unit 35B determines whether or not the parameter α has a set value (step S47). When the parameter α has a set value (Yes at Step S47), the lock processing unit 35B adds a record in which the parameter ID is set to the message ID 42A, the parameter β is set to the URL 42B, and the @key is set to the content management key 42C to the link table 42 ( Step S48).

  The lock processing unit 35B returns a content management key for identifying the content of the URL 50E to the client 2 in response to the lock request from the client 2 (step S49), and ends the processing operation shown in FIG.

  When the lock processing unit 35B does not receive the lock request (No at Step S41), the processing operation illustrated in FIG. If the parameter α has no set value (No at Step S47), the lock processing unit 35B proceeds to Step S49 in order to return the content management key for the lock request to the client 2.

  When detecting the lock request from the client 2, the lock processing control unit 35 shown in FIG. 10 accesses the lock request URL 50E to acquire the content, and stores the acquired content in the storage destination folder. As a result, the control unit 35 saves the storage destination content indicated by the URL 50E of the lock request in the save destination folder. That is, the content of the URL 50E at the time of the lock request can be locked to the save destination folder.

  When the lock request content is saved in the save destination folder, the control unit 35 registers the content management key 41A, the saver 41B, the save date and time 41C, the original URL 41D, and the save destination URL 41E in the content management table 41 for each content. To do. As a result, the user can identify the content management key 41A, the saver 41B, the save date and time 41C, the original URL 41D, and the save destination URL 41E for each content with reference to the content management table 41.

  The control unit 35 manages the content by the message ID and the content management key, and can refer to the content stored in the storage destination folder even by a secondary recipient by mail transfer or reply.

  FIG. 11 is a flowchart showing an example of the processing operation of the control unit 17 on the client 2 side related to the reference request processing. The reference request process shown in FIG. 11 is a process for requesting the shared server 5 to refer to the content stored in the storage destination folder in accordance with the operation of the reference button 51B on the menu screen 51.

  In FIG. 11, the request processing unit 17C determines whether or not an operation on the reference button 51B on the menu screen 51 has been detected (step S51). When the request processing unit 17C detects an operation on the reference button 51B (Yes at Step S51), the request processing unit 17C reads the mail header of the reference mail screen 60 (Step S52). The request processing unit 17C determines whether or not a Reference phrase exists in the mail header (step S53).

  When the Reference phrase is present in the mail header (Yes at Step S53), the request processing unit 17C extracts the original message ID in the Reference, and sets the extracted message ID as the parameter α (Step S54). The request processing unit 17C sets the selected URL character string as the parameter β (step S55).

  The request processing unit 17C requests the shared content list from the shared server 5 (step S56). The shared content list request includes parameters α and β. The request processing unit 17C determines whether or not the shared content list has been received from the shared server 5 (step S57). The shared content list is a content list including a message ID of parameter α (no setting value) and a URL 50E of parameter β.

  When the request processing unit 17C receives the shared content list from the shared server 5 (Yes in step S57), the request processing unit 17C loads the content list (step S58). The request processing unit 17C determines whether there are a plurality of contents in the shared content list (step S59).

  When there is a plurality of contents in the shared content list (Yes at Step S59), the request processing unit 17C sets the shared content list (Step S60), and the content list list 52 shown in FIG. Output (step S61). As a result, the user can recognize the saver, the save date and time, and the request status related to the content stored in the storage location indicated by the URL 50E. The request status can be realized by the shared server 5 managing the status at the time of lock request or reference request.

  The request processing unit 17C determines whether a selection operation for the content 52A on the content list 52 has been detected (step S62). When the request processing unit 17C detects a selection operation for the content 52A (Yes at Step S62), the request processing unit 17C acquires the storage destination URL 41E in the record including the storage person 41B of the content 52A of the selection operation from the content management table 41 (Step S63). ). Then, the request processing unit 17C accesses the storage destination indicated by the storage destination URL 41E (step S64). The request processing unit 17C accesses the storage destination indicated by the storage destination URL 41E and acquires the content. The request processing unit 17C closes the content list 52 (step S65), closes the menu screen 51 (step S66), and ends the processing operation illustrated in FIG.

  If the request processing unit 17C does not detect an operation on the reference button 51B on the menu screen 51 (No at Step S51), the request processing unit 17C ends the processing operation illustrated in FIG. If the reference phrase does not exist (No at Step S53), the request processing unit 17C sets the message ID to the parameter α (Step S67), and proceeds to Step S55 to set the selected URL 50E to the parameter β.

  When the request processing unit 17C has not received the shared content list from the shared server 5 (No at Step S57), the request processing unit 17C proceeds to Step S57 to determine whether or not the shared content list has been received. If there is no plurality of contents in the shared content list (No at Step S59), the request processing unit 17C proceeds to Step S61 to output the content list 52 to the display unit 13. If the selection operation for the content 52A is not detected (No at Step S62), the request processing unit 17C proceeds to Step S62 to determine whether the selection operation for the content 52A is detected.

  When the control unit 17 of the reference request process illustrated in FIG. 11 detects an operation on the reference button 51B, the control unit 17 requests the shared server 5 for a shared content list related to the content of the reference request. As a result, the control unit 17 can acquire a shared content list related to the content requested for reference.

  When receiving the shared content list, the control unit 17 displays the content list 52 on the display unit 13 on the screen. As a result, the user can visually recognize the content list 52 related to the content requested for reference.

  When the control unit 17 detects a selection operation for the desired content 52A in the content list 52 displayed on the screen, the control unit 17 accesses the storage destination URL 42E corresponding to the selected content 52A and displays the content at each lock time on the screen. . As a result, the user on the client 2 side can refer to the content at the time of each lock from the content list 52. Therefore, if the recipient locks the content of the URL 50E described in the mail body 50C, even if the content that is the access destination of the URL 50E is changed after the lock, the content before the change at the time of the lock is made. The contents can be viewed reliably.

  FIG. 12 is a flowchart showing an example of the processing operation of the control unit 35 on the shared server 5 side related to the content list transmission processing. The content list transmission process shown in FIG. 12 is a process for transmitting to the client 2 a shared content list related to the content of the reference request when a shared content list request is detected from the client 2.

  In FIG. 12, the provision processing unit 35C in the control unit 35 determines whether or not a shared content list request has been received from the client 2 (step S71). The shared content list request is a request including the original message ID of the parameter α and the URL being selected for the parameter β related to the content of the reference request on the client 2 side.

  When receiving the shared content list request (Yes at Step S71), the provision processing unit 35C extracts the record group @A of the content management key 42C from the link table 42 (Step S72). Note that the record group @A of the content management key 42C is a record group of the content management key 42C including the parameter α in the message ID 42A and the parameter β in the URL 42B shown in FIG. The provision processing unit 35C extracts the record group @B including the record group @A of the content management key 41A shown in FIG. 2 from the content management table 41 (step S73).

  The provision processing unit 35C sorts the extracted record groups @B in order of the storage date 41C (step S74). The reason why the record group is sorted in the order of the storage date 41C is that there is a high possibility that the content date will not change if the storage date is earlier. The provision processing unit 35C generates a shared content list including the record group @B, returns the shared content list to the client 3 (step S75), and ends the processing operation illustrated in FIG.

  When the provision processing unit 35C does not receive the shared content list request (No at Step S71), the provision processing unit 35C ends the processing operation illustrated in FIG.

  When the control unit 35 of the content list transmission process shown in FIG. 12 detects a shared content list request from the client 2, the content management key 42C corresponding to the message ID 42A and the URL 42B is extracted from the link table 42. The control unit 35 extracts a record group including the extracted content management key from the content management table 41, sorts the extracted record group by the storage date 41C, generates a shared content list, and returns the shared content list to the client 2 To do. As a result, the client 2 can acquire the shared content list.

  FIG. 13 is a flowchart showing an example of the processing operation of the control unit 25 on the mail server 3 side related to the outgoing mail link processing. The outgoing mail link process shown in FIG. 13 is a process for numbering a message ID when there is a URL 50E with a content management key 50F in the mail body 50C as shown in FIG. It is.

  In FIG. 13, the control unit 25 determines whether or not a mail transmission request has been received (step S81). When receiving the mail transmission request (Yes at Step S81), the control unit 25 searches the URL 50E with the content management key 50F from the new part (outside the reference range) of the mail text 50C to be transmitted shown in FIG. 4C (Step S81). S82).

  After searching the URL 50E with the content management key 50F, the control unit 25 determines whether or not there is a target character string of the content management key 50F in the mail body 50C (step S83). When there is a target character string of the content management key 50F (Yes at Step S83), the control unit 25 extracts one target character string (Step S84). The control unit 25 decomposes the extracted target character string and extracts the content management key 50F (@key) and URL 50E (@URL) (step S85).

  Further, after extracting the content management key 50F and the URL 50E, the control unit 25 assigns a message ID (step S86). Furthermore, the control unit 25 instructs the shared server 5 to register a record in which the parameter α is set in the message ID 42A, @URL is set in the URL 42B, and @key is set in the content management key 42C in the link table 42 (step S87).

  The control unit 25 replaces the target character string portion in the mail text 50C with @URL (step S88). As a result, the URL 50E with the content management key 50F on the mail body 50C is only the URL 50E. Then, the control unit 25 determines whether or not processing of all target character strings with the content management key 50F has been completed (step S89). When the processing of all the target character strings with the content management key 50F in the mail body 50C is completed (Yes at Step S89), the control unit 25 transmits the mail (Step S90) and performs the processing operation shown in FIG. finish.

  When the control unit 25 does not receive the mail transmission request (No at Step S81), the control unit 25 ends the processing operation illustrated in FIG. When there is no target character string of the content management key 50F (No at Step S83), the control unit 25 proceeds to Step S90 to transmit the mail. When the processing of all the target character strings with the content management key 50F in the mail body 50C has not been completed (No at Step S89), the control unit 25 performs a step to extract one unprocessed target character string. The process proceeds to S84.

  The transmission mail link processing control unit 25 shown in FIG. 13 assigns a message ID when there is a URL 50E with the content management key 50F added in the mail body 50C at the time of mail transmission request. Further, the control unit 25 instructs the shared server 5 to register the message ID as well as the URL and the content management key in the link table 42 in the shared server 5. As a result, the shared server 5 can register the message ID 42A, URL 42B, and content management key 42C for each content in the link table 42.

  Further, after numbering the message ID, the control unit 25 transmits the mail with the URL 50E with the content management key 50F in the mail body as a normal URL.

  In this embodiment, the contents at the time when the mail sender creates the mail and the contents at the time when the broadcast recipient accesses the URL destination are stored in the shared WEB server, and the mail receiver stores the stored information at that time. You can refer to it. Therefore, information is not missed even if there is a broken link or content change. Since shared content is managed using email as a key, secondary recipients of reply emails and forwarded emails can refer to the shared content of the original email.

  When the shared server 5 of the embodiment detects a lock request for the content stored at the URL 50E in the mail text from the client 2, the shared server 5 accesses the storage location of the URL 50E and stores the content in the storage folder. Further, the shared server 5 stores the URL 50E and the storage destination URL of the storage folder in association with each other in the shared folder 43 in the storage unit 32. As a result, the user on the client 2 side can lock the content stored in the storage location indicated by the URL at the time of the lock request and save it in the save destination folder.

  Further, when the shared server 5 detects a reference request for the URL 50E from the client 2, the shared server 5 refers to the storage unit 32 and provides a storage destination URL corresponding to the URL to the client 2 of the reference request. As a result, the user on the client 2 side can refer to the content related to the URL at the time of locking. The shared server 5 can provide the content at the time of the lock to the reference requesting user even when there is a change in the content of the storage location indicated by the original URL after the lock.

  When the shared server 5 saves the content in the save destination folder in response to the lock request, the oldest message ID is extracted from the message ID in the Reference phrase when there is a Reference phrase in the mail text describing the URL. Furthermore, the shared server 5 stores the extracted message ID in the storage unit 32 in association with the URL and the storage destination URL. Further, the shared server 5 refers to the storage unit 32 and provides a storage destination URL corresponding to the URL related to the message ID to the client 2 of the reference request. As a result, the shared server 5 can manage the association between the URL and the storage destination URL using the message ID.

  When the shared server 5 stores the content in the storage destination folder in response to the lock request, the content management key for identifying the content of the URL described in the mail body is obtained when there is no Reference clause in the mail body describing the URL. To do. The shared server 5 adds the content management key 50F to the head part of the URL 50E in the mail text. As a result, the user on the client 2 side can recognize it as a locked URL by looking at the URL 50E added with the content management key 50F on the mail creation screen 50.

  Furthermore, the shared server 5 stores the acquired content management key in the storage unit 32 in association with the URL and the storage destination URL. Further, the shared server 5 refers to the storage unit 32 and provides a storage destination URL corresponding to the URL related to the content management key to the client 2 of the reference request. As a result, the user on the client 2 side can refer to the content related to the URL at the time of locking.

  In the above embodiment, the mail server 3 and the shared server 5 are separated. However, the shared server 5 may incorporate the function of the mail server 3. It is executed by the control unit 35 in the inside.

  The shared server 5 of the present embodiment stores the content of the URL character string of the lock request in the storage destination folder in the shared folder 43 in the storage unit 32. However, the storage destination folder is not limited to the shared server, for example, A storage unit in the mail server 3 or another Web server 4 may be used.

  In addition, each component of each part illustrated does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each part is not limited to the one shown in the figure, and all or a part thereof may be functionally or physically distributed / integrated in arbitrary units according to various loads and usage conditions. Can be configured.

  Furthermore, various processing functions performed in each device are performed on a CPU (Central Processing Unit) (or a microcomputer such as an MPU (Micro Processing Unit), MCU (Micro Controller Unit), etc.) in whole or in part. You may make it perform. Various processing functions may be executed entirely or arbitrarily on a program that is analyzed and executed by a CPU (or a microcomputer such as an MPU or MCU) or hardware based on wired logic. Needless to say.

  By the way, the various processes described in the present embodiment can be realized by executing a program prepared in advance by the information processing apparatus. Therefore, in the following, an example of an information processing apparatus that executes a program having the same function as in the above embodiment will be described. FIG. 14 is an explanatory diagram illustrating an example of the information processing apparatus 100 that executes the provided program.

  The information processing apparatus 100 that executes the provided program in FIG. 14 includes a ROM 110, a RAM 120, a CPU 130, and a communication unit 140.

  The ROM 110 stores in advance a providing program that exhibits the same function as in the above embodiment. The provided program may be recorded not on the ROM 110 but on a recording medium readable by a drive (not shown). Further, as the recording medium, for example, a portable recording medium such as a CD-ROM, a DVD disk, a USB memory, an SD card, or a semiconductor memory such as an HDD or a flash memory may be used. The provided programs are a storage program 110A, a management program 110B, and a provided program 110C. Note that the programs 110A to 110C may be integrated or distributed as appropriate.

  Then, the CPU 130 reads these programs 110A to 110C from the ROM 110, and executes each of the read programs. Then, the CPU 130 causes the programs 110A to 110C to function as a storage process 130A, a management process 130B, and a provision process 130C.

  When there is a first storage destination address indicating the storage destination of information in the mail body of the mail, the CPU 130 stores the information in the storage destination indicated by the first storage destination address from the mail transmission source or destination terminal device. A request for storing the received information in the first area in the RAM 120 is detected. When the CPU 130 detects a storage request, the CPU 130 accesses the first storage destination address to acquire information, and stores the acquired information in the first area in the RAM 120. The CPU 130 associates the first storage destination address with the second storage destination address indicating the storage destination in the RAM 120 that stores the information and stores it in the second area in the RAM 120. When the CPU 130 detects a reference request for information stored in the storage destination indicated by the first storage destination address from the terminal device of the mail transmission destination, the CPU 130 refers to the second area and corresponds to the first storage destination address. The second storage destination address is provided to the terminal device that has requested the reference request. As a result, the storage destination information indicated by the storage destination address described in the mail text can be reliably provided to the recipient who is the terminal device of the transmission destination.

DESCRIPTION OF SYMBOLS 1 Mail management system 2 Client 3 Mail server 4 Web server 5 Shared server 17 Control part 17C Request processing part 35 Control part 35B Lock processing part 35C Provision processing part 41 Content management table 42 Link table 43 Shared folder

Claims (5)

On the computer,
When there is a first storage location address indicating the storage location of information in the email body of the email, the email is stored in the storage location indicated by the first storage location address from the transmission source or destination terminal device. When a storage request to the storage unit for the received information is detected, the information is acquired by accessing the first storage destination address, the acquired information is stored in the storage unit,
Storing the first storage destination address and the second storage destination address indicating the storage destination of the storage unit storing the information in the management storage unit in association with each other;
When a reference request for information stored in the storage destination indicated by the first storage destination address is detected from the terminal device to which the mail is sent, the management storage unit is referred to correspond to the first storage destination address A program for causing the terminal device that requested the reference request to execute the second storage destination address. In the computer,
When the information is stored in the storage unit in response to the storage request, it is determined whether or not there is a message history in the mail in the mail text describing the first storage destination address. And further executing a process of extracting the oldest message identification information from the message identification information in the message history,
As a process of associating and storing the first storage destination address and the second storage destination address in the management storage unit,
In association with the extracted message identification information, the first storage destination address and the second storage destination address are stored in the management storage unit,
As a process of providing the second storage destination address to the terminal device that has requested the reference request,
The management storage unit is referred to, and the second storage destination address corresponding to the first storage destination address of the message identification information is provided to the terminal apparatus that has requested the reference request. Item 2. The program according to Item 1. In the computer,
When the information is stored in the storage unit in response to the storage request, it is determined whether or not there is a message history in the mail in the mail text describing the first storage destination address, and there is no message history To obtain identification information for identifying information stored in the storage location indicated by the first storage location address described in the mail text;
A process of adding the acquired identification information to the mail body,
As a process of associating and storing the first storage destination address and the second storage destination address in the management storage unit,
In association with the acquired identification information, the first storage destination address and the second storage destination address are stored in the management storage unit,
As a process of providing the second storage destination address to the terminal device that has requested the reference request,
Referring to the management storage unit, providing the second storage destination address corresponding to the first storage destination address of the identification information added to the mail text to the terminal device that has requested the reference request. The providing program according to claim 1 or 2. When there is a first storage location address indicating the storage location of information in the email body of the email, the email is stored in the storage location indicated by the first storage location address from the transmission source or destination terminal device. A storage processing unit that accesses the first storage destination address to acquire the information and stores the acquired information in the storage unit;
A management processing unit that stores the first storage destination address in a management storage unit in association with a second storage destination address indicating a storage destination of the storage unit that stores the information;
When a reference request for information stored in the storage destination indicated by the first storage destination address is detected from the terminal device to which the mail is sent, the management storage unit is referred to correspond to the first storage destination address A providing processing unit for providing the second storage destination address to the terminal device that has requested the reference request. Information processing device
When there is a first storage location address indicating the storage location of information in the email body of the email, the email is stored in the storage location indicated by the first storage location address from the transmission source or destination terminal device. When a storage request to the storage unit for the received information is detected, the information is acquired by accessing the first storage destination address, the acquired information is stored in the storage unit,
Storing the first storage destination address and the second storage destination address indicating the storage destination of the storage unit storing the information in the management storage unit in association with each other;
When a reference request for information stored in the storage destination indicated by the first storage destination address is detected from the terminal device to which the mail is sent, the management storage unit is referred to correspond to the first storage destination address And providing the second storage destination address to the terminal device that has requested the reference request.

Images