JP5891899B2 - Information providing program, information providing apparatus, and information providing method - Google Patents

Description

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

  In recent years, many users have not only transmitted information using e-mail (hereinafter referred to as “mail”), which is a general communication tool, but also a variety other than e-mail such as SNS (Social Networking Service) and chat. Information transmission using a message providing system, which is a powerful communication tool, is increasing. As described above, when using another communication tool, a dedicated application is installed and used in the information terminal device.

  As related prior art, for example, there is one that provides a communication service in which a social networking service and mail are integrated (see, for example, Patent Document 1 below).

Special table 2009-506427 gazette

  However, depending on the environment of the information terminal device, a dedicated application for each communication tool is not always installed. Therefore, depending on the information terminal device, a message in a message providing system that is another communication tool is confirmed. It may not be possible. Even in an environment where all messages can be confirmed, there are multiple message delivery systems that are communication tools, so it is troublesome to confirm all of them, and any message may be missed in a timely manner. There is also.

  In order to solve the above-described problems caused by the prior art, the present invention provides an information providing program, an information providing apparatus, and an information providing method capable of efficiently transmitting information using a message providing system as a plurality of communication tools. The purpose is to provide.

  In order to solve the above-described problems and achieve the object, according to one aspect of the present invention, a display request for a mail message creation screen is accepted, sender information and destination information on the received message creation screen are acquired, Based on the acquired sender information and destination information, a message stored in a message storage unit of another message providing system is extracted, a first input area for inputting a mail message, an extracted message, Creating a message creation screen including a second input area for inputting a message for the message, outputting the created message creation screen, accepting a message transmission request input to the output message output screen, In response to the accepted transmission request, the message input in the first input area is sent to the electronic mail. Information providing program, information providing apparatus, and information for storing a message input to the second input area in the message storage unit of the other message providing system in response to the received transmission request A provision method is proposed.

  According to one aspect of the present invention, there is an effect that a message providing system that is a plurality of communication tools can be efficiently used using electronic mail.

FIG. 1 is an explanatory diagram of an example of the information providing method according to the embodiment. FIG. 2 is an explanatory diagram of a system configuration example of the mail system 200 according to the embodiment. FIG. 3 is a block diagram of a hardware configuration example of the information providing apparatus 201 according to the embodiment. FIG. 4 is a block diagram of a hardware configuration example of the client terminal 202 according to the embodiment. FIG. 5 is an explanatory diagram of an example of the contents stored in the user authentication DB 220 according to the embodiment. FIG. 6 is an explanatory diagram of an example of the contents stored in the SNS user DB 230 according to the embodiment. FIG. 7 is an explanatory diagram of an example of the contents stored in the mail DB 240 according to the embodiment. FIG. 8 is an explanatory diagram of an example of the contents stored in the SNS message DB 250 according to the embodiment. FIG. 9 is an explanatory diagram of a screen example of a mail list display screen according to the embodiment. FIG. 10 is an explanatory diagram (part 1) of a screen example of a message creation screen according to the embodiment. FIG. 11 is an explanatory diagram (part 2) of a screen example of the message creation screen according to the embodiment. FIG. 12 is an explanatory diagram (part 3) of a screen example of the message creation screen according to the embodiment. FIG. 13 is an explanatory diagram (part 1) of a screen example of an SNS message display screen according to the embodiment. FIG. 14 is an explanatory diagram (part 2) of the screen example of the message display screen of the SNS according to the embodiment. FIG. 15 is a block diagram illustrating a functional configuration example of the information providing apparatus 201 according to the embodiment. FIG. 16 is a flowchart (part 1) illustrating an example of an information providing process (mail program) procedure of the information providing apparatus 201 according to the embodiment. FIG. 17 is a flowchart (part 2) illustrating an example of an information providing process (mail program) procedure of the information providing apparatus 201 according to the embodiment. FIG. 18 is a flowchart illustrating an example of a specific processing procedure of the creation process of the creation screen with the cooperation application according to the embodiment. FIG. 19 is a flowchart (part 1) illustrating an example of an information processing procedure of the client terminal 202 according to the embodiment. FIG. 20 is a flowchart (part 2) illustrating an example of an information processing procedure of the client terminal 202 according to the embodiment.

  Exemplary embodiments of an information providing program, an information providing apparatus, and an information providing method according to the present invention will be described below in detail with reference to the accompanying drawings.

(Embodiment)
FIG. 1 is an explanatory diagram of an example of the information providing method according to the embodiment. In FIG. 1, a user (Mr. A, Mr. B) installs a mail program 101 and a SNS (Social Networking Service) program in each client terminal, and uses mail and SNS.

  Here, SNS is a service that allows users to exchange information by building social connections on the Internet. By using SNS, the community between users is expanded. Can continue.

  If Mr. A replies to mail sent from Mr. B to Mr. A using the mail program, a message creation screen (for reply) 101 is displayed on Mr. A's client terminal. The message creation screen (for reply) 101 displays that the destination is Mr. B and the sender is Mr. A, and the reply sentence input by Mr. A on the article input screen.

  In the present invention, a message (SNS message A) of a community common to both Mr. A and Mr. B is displayed on the message creation screen (for reply) 101. Reference numerals 102-1 and 102-2 denote SNS message display screens. The SNS message a on the message display screen 102-1 is displayed on the message creation screen (for reply) 101.

  When the message is input in the comment input field on the message creation screen (for reply) 101, the input SNS message b is additionally displayed on the message display screen 102-2. Therefore, an SNS message can be registered on the message creation screen (for reply) 101 without starting up an SNS application.

  As described above, the SNS message can be confirmed from the e-mail message creation screen, and the message for the SNS message can be input and registered together with the e-mail reply from the e-mail message creation screen. . Therefore, Mr. A can confirm the message transmitted from Mr. B by the SNS without starting the SNS application, and can transmit (reply) the message corresponding to the confirmed message to the SNS. Thereby, Mr. A does not fail to confirm the message from Mr. B by SNS, and Mr. B can also confirm the message from Mr. A with respect to the message transmitted by SNS by SNS.

(System configuration example of the mail system 200)
Next, a system configuration example of the mail system 200 according to the embodiment will be described. FIG. 2 is an explanatory diagram of a system configuration example of the mail system 200 according to the embodiment. 2, the mail system 200 includes an information providing apparatus 201 and a plurality of client terminals 202 (three in the drawing).

  In the mail system 200, the information providing apparatus 201 and the plurality of client terminals 202 are connected to each other via a wired or wireless network 210 so that they can communicate with each other. The network 210 is, for example, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or the like.

  Here, the information providing apparatus 201 is a computer that includes a user authentication DB (database) 220, an SNS user DB 230, a mail DB 240, and an SNS message DB 250, and transmits and receives mail in the mail system 200. The information providing apparatus 201 is, for example, a mail server. The user authentication DB 220, the SNS user DB 230, the mail DB 240, and the SNS message DB 250 will be described later with reference to FIGS.

  The client terminal 202 is a computer that displays, creates, and transmits / receives mail. The client terminal 202 is, for example, a PC (Personal Computer), a notebook PC, a mobile phone, a PDA (Personal Digital Assistant), a smartphone, or a tablet terminal used by a user of the mail system 200. The mail is, for example, a web mail displayed, created, and transmitted / received by the browser of the client terminal 202.

(Example of hardware configuration of information providing apparatus 201)
FIG. 3 is a block diagram of a hardware configuration example of the information providing apparatus 201 according to the embodiment. In FIG. 3, an information providing apparatus 201 includes a CPU (Central Processing Unit) 301, a ROM (Read-Only Memory) 302, a RAM (Random Access Memory) 303, an I / F (Interface) 304, and a magnetic disk drive. 305, a magnetic disk 306, an optical disk drive 307, an optical disk 308, and an input device 309. Each component is connected by a bus 300.

  Here, the CPU 301 governs overall control of the information providing apparatus 201. The ROM 302 stores a program such as a boot program. The RAM 303 is used as a work area for the CPU 301. The I / F 304 is connected to the network 210 through a communication line, and is connected to other devices such as the client terminal 202 via the network 210. The I / F 304 controls an internal interface with the network 210 and controls input / output of data from other devices. For example, a modem or a LAN adapter may be employed as the I / F 304.

  The magnetic disk drive 305 controls the reading / writing of the data with respect to the magnetic disk 306 according to control of CPU301. The magnetic disk 306 stores data written under the control of the magnetic disk drive 305. The optical disk drive 307 controls reading / writing of data with respect to the optical disk 308 according to the control of the CPU 301. The optical disk 308 stores data written under the control of the optical disk drive 307, and causes the computer to read data stored on the optical disk 308.

  The input device 309 inputs data such as characters, numbers, and various instructions. The input device 309 is, for example, a keyboard having keys for input or a touch panel type input pad. Note that the information providing apparatus 201 may include a display for displaying data in addition to the above-described components. The information providing apparatus 201 may not include the optical disk drive 307 and the optical disk 308 among the above-described components, for example.

(Hardware configuration example of client terminal 202)
FIG. 4 is a block diagram of a hardware configuration example of the client terminal 202 according to the embodiment. 4, the client terminal 202 includes a CPU 401, a ROM 402, a RAM 403, a magnetic disk drive 404, a magnetic disk 405, an optical disk drive 406, an optical disk 407, a display 408, an I / F 409, a keyboard 410, and the like. , A mouse 411, a scanner 412, and a printer 413. Each component is connected by a bus 400.

  Here, the CPU 401 governs overall control of the client terminal 202. The ROM 402 stores programs such as a boot program. The RAM 403 is used as a work area for the CPU 401. The magnetic disk drive 404 controls the reading / writing of the data with respect to the magnetic disk 405 according to control of CPU401. The magnetic disk 405 stores data written under the control of the magnetic disk drive 404.

  The optical disk drive 406 controls reading / writing of data with respect to the optical disk 407 according to the control of the CPU 401. The optical disk 407 stores data written under the control of the optical disk drive 406, or causes the computer to read data stored on the optical disk 407.

  The display 408 displays data such as a document, an image, and function information as well as a cursor, an icon, or a tool box. As the display 408, for example, a CRT, a TFT liquid crystal display, a plasma display, an organic EL display, or the like can be adopted.

  The I / F 409 is connected to the network 210 through a communication line, and is connected to another device such as the information providing device 201 via the network 210. The I / F 409 controls an internal interface with the network 210 and controls input / output of data from other devices. For example, a modem or a LAN adapter may be employed as the I / F 409.

  The keyboard 410 includes keys for inputting characters, numbers, various instructions, and the like, and inputs data. Moreover, a touch panel type input pad or a numeric keypad may be used. The mouse 411 moves the cursor, selects a range, moves the window, changes the size, and the like. A touch panel, a trackball, a joystick, or the like may be used as long as it has the same function as a pointing device.

  The scanner 412 optically reads an image and takes in the image data into the client terminal 202. The scanner 412 may have an OCR (Optical Character Reader) function. The printer 413 prints image data and document data. As the printer 413, for example, a laser printer or an ink jet printer can be adopted. Note that the client terminal 202 may not include the optical disk drive 406, the optical disk 407, the scanner 412, the printer 413, and the like among the above-described components.

(Storage contents of various DBs 220, 230, 240, 250)
Next, the contents stored in the various DBs 220, 230, 240, and 250 included in the information providing apparatus 201 will be described with reference to FIGS. The various DBs 220, 230, 240, and 250 are realized by storage devices such as the RAM 303, the magnetic disk 306, and the optical disk 308 of the information providing apparatus 201 illustrated in FIG.

<Storage contents of user authentication DB 220>
FIG. 5 is an explanatory diagram of an example of the contents stored in the user authentication DB 220 according to the embodiment. In FIG. 5, the user authentication DB 220 includes at least a “user ID” field and a “password” field. By setting information in each field, authentication information of each user (for example, authentication information 500- 1 to 500-3) are stored as records.

  Here, the user ID is an identifier of the user of the mail system 200. The password is a code for authenticating the user of the mail system 200. For example, the authentication information 500-1 indicates the password “kljkfadojaf” of the user with the user ID “yamada@xxx.ww”. In the embodiment, the user ID “yamada@xxx.ww” is also used as “sender ID” and “destination” of the mail DB 240 described later.

<Storage contents of SNS user DB 230>
FIG. 6 is an explanatory diagram of an example of the contents stored in the SNS user DB 230 according to the embodiment. In FIG. 6, the SNS user DB 230 has at least fields of “user ID”, “nickname”, “icon”, and “registered community”, and by setting information in each field, each SNS user information (For example, SNS user information 600-1 to 600-5) is stored.

  Here, the user ID is an identifier of the user of the mail system 200, like the user authentication DB 220 shown in FIG. The nickname is user identification information in the SNS, and corresponds to the user ID on a one-to-one basis. The icon is an image (illustration, photograph, etc.) added to the user's message, and makes it easy to visually distinguish between the user's message and other users' messages.

  The registered community is a group space on the SNS in which the user corresponding to the user ID participates with interest. In the present invention, in the process of creating a creation screen with a cooperative application, which will be described later, in order to obtain a message (speech) from the SNS message DB 250, the group is registered in advance corresponding to the user ID and nickname. There may be one registered community or a plurality of registered communities. All or part of the registered community can be added, changed, or deleted by a predetermined operation of each user.

  For example, in the SNS user information 600-1, the user's nickname “yamada@xxx.ww” is “Yamada”, the icon is a male illustration image, and the registered community is “education community”. It shows that there is. The SNS user information 600-2 is an illustration image of a man whose user ID “kuroda@xxx.ww” has a nickname “Kuroda”, and whose icon is different from “Yamada”. This shows that the registered communities are “education community”, “patent community”, and “tennis”.

<Storage contents of mail DB 240>
FIG. 7 is an explanatory diagram of an example of the contents stored in the mail DB 240 according to the embodiment. As an example, it is assumed to exist for each user ID. FIG. 7 shows an example of a mail DB whose user ID is “satoh@xxx.ww”. In FIG. 7, the mail DB 240 has at least fields of “type”, “message ID”, “sender ID”, “sending date / time”, “subject”, “text”, and “destination”. Mail information (for example, mail information 700-1 to 700-3) is stored by setting information in each field.

  In FIG. 7, the mail DB 240 is shown to be provided for each user. However, for a plurality of users, fields such as “sender ID” and “destination” in a common database, or illustrations are shown. In addition to omission, it may be possible to distinguish and manage for each user from the provided fields. Therefore, FIG. 7 shows “yamada @ xxx.” Which is the user ID from the “sender ID” and “destination” fields. Only information corresponding to “ww” may be collected from the mail DB 240.

  The type is information for distinguishing between received mail (“receive”) and transmitted mail (“transmit”). In the mail DB 240 of FIG. 7, mail information 700-2 and 700-3 are received mails, and mail information 700-1 is a transmitted mail.

  The message ID is an identifier for uniquely identifying mail transmitted / received by the mail system 200. Normally, the character string should be unique as a whole, but in general, the right side of the @ mark is the domain name, the left side is the date and time, user ID, etc. As a whole, the string is unique. In this embodiment, the character string is such that the mail can be easily identified.

  The sender ID is an identifier of a mail transmission source, for example, a user ID of a user who is a transmission source. The outgoing date / time is the outgoing date / time of the mail.

  The subject is the subject of the mail. The subject is displayed as a part of the mail summary information on the mail list display screen 900 shown in FIG. The body is the body of the mail message. The destination is a mail destination, for example, a mail address of a user who is a mail transmission destination. The destination includes, for example, CC (Carbon Copy) and BCC (Blind Carbon Copy).

  For example, the mail information 700-1 has a user ID “satoh @ xxx. ww ”user's transmitted mail. The “type” of the mail is “transmission”, and the “message ID” is “system3 @ xxx. “ww” and “sender ID” are “satoh @ xxx. “ww”, “date of transmission” is “2011/11/31 16:50:32”, “subject” is “Re: Re: Re: About XX system”, and “text” is “Sato”. .. "" Destination "is" yamada @ xxx. www, Kuroda @ xxx. www.tanaka@xxx. ww ”.

  In addition, the mail information 700-2 has a user ID “satoh @ xxx. The information regarding the received mail of the user “ww”. The “type” of the mail is “reception”, and the “message ID” is “system2 @ xxx. www "and" sender ID "are" yamada @ xxx. “ww”, “date of transmission” is “2011/11/31 16:39:29”, “subject” is “Re: Re: About the XX system”, and “text” is “Yamada”. As an example, ... "," Destination "is" sat @@ xxx. www, Kuroda @ xxx. www.tanaka@xxx. ww ”.

<Storage contents of SNS message DB 250>
FIG. 8 is an explanatory diagram of an example of the contents stored in the SNS message DB 250 according to the embodiment. In FIG. 8, the SNS message DB 250 is a database that stores SNS message information in the SNS, and includes at least fields of “sender nickname”, “sending date / time”, “content of speech”, and “reader nickname”, By setting information in the field, SNS message information (for example, SNS message information 800-1, 800-2) is stored as a record.

  The sender nickname is user (speaker) identification information, and the sender nickname field information corresponds to the nickname field information of the SNS user DB 230 shown in FIG. Thereby, the user ID of the SNS message information can be specified. The transmission date / time is the transmission date / time of the message. The content of the remark is the content of the message remarked by the user.

  The already-read nickname is the nickname of the user who has read the content of the message concerning the SNS message information. When the user reads the SNS message information, specifically, when the display screen on which the SNS message information is displayed is opened, the nickname of the user is stored in the field of the reader nickname. When no nickname is stored in the field of the nickname of the reader, this indicates that there is no reader in the SNS message information.

(Email list display screen example)
Next, a mail list display screen displayed on the display 408 of the client terminal 202 shown in FIG. 4 will be described. The screen information of the mail list display screen is created by, for example, the information providing apparatus 201 and transmitted to the client terminal 202.

  FIG. 9 is an explanatory diagram of a screen example of a mail list display screen according to the embodiment. When the user requests to display the mail list display screen, the mail list display screen 900 shown in FIG. 9 is displayed on the display 408. In FIG. 9, on the mail list display screen 900, summary information (for example, summary information 900-1 and 900-2) of the email transmitted to the user with the user ID “satoh@xxx.www” is displayed. ing. Although only the received mail is displayed on the mail list display screen 900 shown in FIG. 9, the mail transmitted by the user with the user ID “yamada@xxx.ww” is displayed together with the received mail. May be.

  Further, the mail list display screen 900 is provided with a “message creation” button B1, a “reply” button B2, and a “logout” button B3. When the “Create Message” button B1 is clicked, a message creation screen 1000 shown in FIG. 10 to be described later is displayed on the display 408 as a result of a message creation screen display request for creating a new mail being sent to the information providing apparatus 201. The

  When the user selects any of the email summary information displayed on the email list display screen 900 and clicks the “Reply” button B2, a request to display a message creation screen for creating a reply email to the selected email is displayed. Is transmitted to the information providing apparatus 201, a message creation screen 1100 shown in FIG. When the “logout” button B3 is clicked, the logout request is transmitted to the information providing apparatus 201. As a result, the display of the mail list display screen 900 ends.

  In FIG. 9, the mail list display screen 900 displays summary information (for example, summary information 900-1 and 900-2) of the email transmitted to the user with the user ID “satoh@xxx.www”. Yes.

  The summary information is information indicating the sender of the mail, the transmission date and time, and the subject. Here, the mail sender ID is shown as the mail sender. In addition, the title of the email is shown as the subject of the email. For example, the summary information 900-1 includes a mail sender “yamada@xxx.ww”, a transmission date and time “2011/2/20 16:39:29”, and a subject “Re: Re: XX system”, summary information 900. -2 indicates the mail sender “kuroda@xxx.www”, the transmission date and time “2011/2/20 16:20:38”, and the subject “Re: about the OO system”.

  On the mail list display screen 900, any outline information is displayed by moving a cursor (not shown) displayed on the mail list display screen 900 by a user operation input using the keyboard 410 or the mouse 411 shown in FIG. When clicked, the mail corresponding to the summary information is selected.

(Example of message creation screen)
Next, a message creation screen displayed on the display 408 of the client terminal 202 will be described. For example, the message creation screen is displayed on the display 408 when either button B1 or B2 is clicked on the mail list display screen 900 shown in FIG.

  FIG. 10 is an explanatory diagram showing a screen example (for new creation) of the message creation screen. In FIG. 10, a message creation screen 1000 is displayed when button B1 is clicked, and includes boxes 1001 to 1004. In the message creation screen 1000, a new mail can be created by inputting various information into the boxes 1001 to 1004, for example, by user operation input using the keyboard 410 or the mouse 411.

  The message creation screen 1000 includes an SNS cooperation screen 1006, and the SNS cooperation screen 1006 includes a “latest cooperation” button B7.

  Here, a box 1001 is a box into which a mail destination is input. A box 1002 is a box into which a mail CC destination is input. A box 1003 is a box in which the subject of the mail is input. A box 1004 is an article input screen box, and is a box in which the text of an email is input.

  Further, when the button B4 is clicked on the message creation screen 1000, the created mail to be transmitted is transmitted to the information providing apparatus 201.

  In addition, when button B5 is clicked on message creation screen 1000, the destination information input in “destination” box 1001 or “CC:” box 1002 (including the “BCC:” box not shown) is applied. A group (a community in the case of SNS) common to the user and the user related to the sender information, and a message registered in the group are displayed on the SNS cooperation screen 1006.

  When button B6 is clicked on message creation screen 1000, the logout request is transmitted to information providing apparatus 201, and as a result, display of message creation screen 1000 ends.

  In addition, when the “latest cooperation” button B7 is clicked on the message creation screen 1000, the latest cooperation information displayed on the SNS cooperation screen 1006, that is, since the previous display request for the message creation screen 1000 has been issued, When a new message has been registered up to the present time, the contents reflecting it are displayed on the SNS cooperation screen 1006.

  In addition, when one of the mail summary information is selected on the mail list display screen 900 shown in FIG. 9 and the button B2 is clicked, a message creation screen 1100 shown in FIG. 11 is displayed. FIG. 11 is an explanatory diagram showing a screen example (for reply) of the message creation screen. For example, an address, a title, and a quotation are displayed on the display 408 in the boxes 1101, 1103, and 1104 of the message creation screen 1100 in a state of being inserted using the information of the reply source mail. When button B3 is clicked on mail list display screen 900, for example, a state in which titles and quotes are inserted in boxes 1103 and 1104 of message creation screen 1100 using information on the mail of the transfer source. Is displayed on the display 408. The buttons B4 to B7 are the same as the buttons B4 to B7 in FIG.

  In FIG. 11, the message creation screen 1100 displays the community name in which both the user and the sender related to the destination information are participating in the SNS cooperation screen 1106 and the destination information of the user related to the community. In FIG. 11, “patent community (tanaka@xxx.ww)”, “tennis community (kuroda@xxx.ww)”, and “education community (yamada@xxx.ww)” are displayed in a list. Thus, among the destination information, the destination information of the users participating in the common community is displayed in the vicinity of the community name, so that the user can have a plurality of users related to the destination information. Even so, the reason why the community name is displayed (who is the community in common) can be easily recognized, and can be used as a reference when selecting a community.

  The display content of the SNS cooperation screen 1106 may be displayed at the same time when the message creation screen 1100 is displayed, and is not displayed when the message creation screen 1100 is displayed, and the button B5 is pressed. You may make it display after it is made.

  On the SNS cooperation screen 1106, a user's operation input using the keyboard 410 or the mouse 411 shown in FIG. 4 moves a cursor (not shown) displayed on the SNS cooperation screen 1106 and any community name is clicked. Then, as shown in FIG. 12, a message corresponding to the community is selected.

  FIG. 12 is an explanatory diagram (part 3) of a screen example of the message creation screen according to the embodiment. A message creation screen 1200 shown in FIG. 12 shows a state where the tennis community name is clicked and the tennis community is selected in the message creation screen 1100 of FIG. In FIG. 12, the message creation screen 1200 shows “Kuroda. This is the utterance content of the SNS message information 800-1 of the SNS message DB 250 shown in FIG. “Tomorrow's tennis tournament...” Is displayed on the SNS cooperation screen 1206 and a comment input field 1207 is displayed.

  If there are a plurality of messages in the selected community, a message ("I am Sato. Tennis tournament ...") and a plurality of comment input fields (comment input field 1208) are displayed. If there are too many cases to display, display by scrolling or switching the display. The rest is the same as the message creation screen 1100 shown in FIG.

  When a “Send” button B4 is pressed in a state where a message is input in the article input screen 1104 and the comment input fields 1207 and 1208, the message input in the article input screen 1104 is stored in the mail DB 240, and a comment is input. Messages input in the fields 1207 and 1208 are stored in the SNS message DB 250. More specifically, “Sato is entered in the article input screen box 1104. "..." is stored in the mail DB 240 as the mail information 700-1, and "Thank you," entered in the comment input field 1207. I will be saved. Is stored in the SNS message DB 250 as SNS message information 800-2.

(Screen example of SNS message display screen)
13 and 14 are explanatory diagrams illustrating screen examples of the message display screen of the SNS according to the embodiment. The message display screens 1300 and 1400 display SNS message information in a predetermined display format based on the contents stored in the SNS message DB 250. 13 shows a state before transmission of the message creation screen 1200 shown in FIG. 12, and FIG. 14 shows a state after transmission of the message creation screen 1200 shown in FIG.

  The message display screen 1300 displays SNS message information 1300-1, whereas the message display screen 1400 appears as if input from the SNS application in addition to the SNS message information 1300-1. , SNS message information 1400-1 is displayed. In this way, it can be seen from the message creation screen 1200 shown in FIG. 12 that an SNS message can be written.

  Although illustration is omitted, identification information that can distinguish whether the message is input from the SNS application or the message input from the mail creation screen 1200 may be displayed together.

(Functional configuration example of the information providing apparatus 201)
FIG. 15 is a block diagram illustrating a functional configuration example of the information providing apparatus 201 according to the embodiment. In FIG. 15, the information providing apparatus 201 includes a reception unit 1501, an acquisition unit 1502, an extraction unit 1503, a creation unit 1504, an output unit 1505, and a storage unit 1506. The receiving unit 1501 to the storage unit 1506 are functions as a control unit. Specifically, for example, a program stored in a storage device such as the ROM 302, the RAM 303, the magnetic disk 306, and the optical disk 308 illustrated in FIG. The function is realized by executing the function or by the I / F 304.

  The accepting unit 1501 accepts a display request for a new mail message creation screen. In addition, the reception unit 1501 receives a display request for a reply message creation screen for the received mail. Specifically, as the display request, the “Create Message” button B1 is pressed on the mail list display screen 900 shown in FIG. 9, or one of the summary information 900-1 and 900-2 is selected. This is done by pressing the “Reply” button B2.

  The acquisition unit 1502 acquires sender information and destination information related to the received message creation screen. Specifically, the acquisition unit 1502 refers to the SNS user DB 230 from the mail addresses input in the “Destination” box 1001 and the “CC:” box 1002 of the message creation screen 1000 shown in FIG. And the user information is acquired as destination information. Also, the user ID of the user is acquired as the sender.

  In addition, when the receiving unit 1501 receives a request to display a reply message creation screen for the received e-mail, the acquiring unit 1502 sets the user ID of the user as the sender, the sender as the destination, the sender information and the destination. Each piece of information may be acquired. Even when a request to display a reply message creation screen for a received e-mail is received, destination information input to the “Destination” box 1101 and “CC:” box 1102 has been added, changed, or deleted. More preferably, the acquisition unit 1502 acquires the destination information according to the contents of addition, change, and deletion.

  The extraction unit 1503 extracts a message stored in a message storage unit (for example, the SNS message DB 250 illustrated in FIG. 8) of another message providing system based on the acquired sender information and destination information. Specifically, it is stored in the message storage unit of the other information providing system as a message of a group of another information providing system in which both the user concerning the sender information and the user concerning the destination information are registered. The messages that are present.

  For example, when the other message providing system is an SNS providing system that stores a message for each community, the extraction unit 1503 includes sender information and destination information among the messages stored in the message storage unit of the SNS providing system. Based on the above, both the user concerning the sender information and the user concerning the destination information extract messages in the community registered in the “registered community” field of the SNS user DB 230.

  Further, the extraction unit 1503 extracts a message unread by the user related to the sender information from among the messages stored in the message storage unit of another information providing system stored as a group message. Whether or not the user related to the sender information is an unread message is determined based on whether or not the sender's nickname is stored in the “reader nickname” field of the SNS message DB 250 shown in FIG. If the sender's nickname is not stored, it is determined that the SNS message information is unread.

  The creation unit 1504 creates a message creation screen including a first input area for inputting an e-mail message, an extracted message, and a second input area for inputting a message for the message. Specifically, for example, the first input area for inputting an e-mail message is the article input screen 1104 of the message creation screen 1200 shown in FIG. 12, and the extracted message is the SNS of the message creation screen 1200. The second input area for inputting a message for the extracted message, which is a message displayed on the cooperation screen 1206, is a comment input field 1207, 1208.

  The output unit 1505 outputs the created message creation screen. Specifically, for example, the message creation screen information is transmitted to the client terminal 202, and the message creation screen is displayed on the display 408 of the client terminal 202 shown in FIG.

  The accepting unit 1501 accepts a message transmission request input on the output message output screen. Specifically, the transmission request is made by pressing the “Send” button B4 on the message creation screens 1000, 1100, and 1200. The transmission request may include mail information and SNS message information.

  The storage unit 1506 stores the message input in the first input area in the email message storage unit in response to the accepted transmission request. Specifically, a new message ID is assigned in the mail DB 240, and mail information included in the transmission request is stored in each field. The storage unit 1506 stores the message input in the second input area in the e-mail message storage unit in response to the accepted transmission request. Specifically, the SNS message information included in the transmission request is stored in each field of the SNS message DB 250.

  More specifically, the message “I am Sato ...” in the article input screen 1104 of the message creation screen 1200 shown in FIG. 12 is stored in the mail DB 240 in the mail information 700-1 (message ID is “system3 @ xx. www ”). Also, “Thank you,” in the comment input field 1207 of the message creation screen shown in FIG. I will be saved. Is stored in the SNS message DB 250 as SNS message information 800-2. As a result, a message 1400-1 is added to the SNS message display screen 1300 shown in FIG. 13 as in the SNS message display screen 1400 shown in FIG.

(Information provision processing procedure of the information provision apparatus 201)
Next, an information provision processing procedure of the information provision apparatus 201 according to the embodiment will be described. FIGS. 16 and 17 are flowcharts illustrating an example of an information provision processing procedure (mail program) of the information provision apparatus 201 according to the embodiment.

  In the flowchart of FIG. 16, first, the CPU 301 determines whether a mail display request has been received from the client terminal 202 (step S1601). Here, the CPU 301 waits to receive a mail display request (step S1601: No). When the mail display request is received by the CPU 301 (step S1601: Yes), the screen information of the user ID and password input screen (not shown) is transmitted to the client terminal 202 (step S1602). Next, the CPU 301 determines whether a user ID and password are received from the client terminal 202 (step S1603).

  Here, the CPU 301 waits for reception of the user ID and password (step S1603: No). When the user ID and password are received by the CPU 301 (step S1603: Yes), the user authentication processing is executed with reference to the user authentication DB 220 shown in FIG. 5 (step S1604).

  Specifically, for example, the CPU 301 refers to the user authentication DB 220 and specifies a password corresponding to the received user ID. The CPU 301 determines whether the received password matches the specified password. As a result, when the passwords match, the CPU 301 authenticates the user. On the other hand, if the passwords do not match or the user ID is not included in the user authentication DB 220, the CPU 301 does not authenticate the user.

  Next, the CPU 301 determines whether or not the user has been authenticated (step S1605). If the user is not authenticated (step S1605: No), the CPU 301 transmits screen information of an authentication error screen (not shown) to the client terminal 202 (step S1606), and a series of steps according to this flowchart. The process ends.

  On the other hand, if the user is authenticated in step S1605 (step S1605: Yes), the CPU 301 acquires a registered community from the SNS user DB 230 having the user ID shown in FIG. 6 (step S1607). If there are multiple registered communities, all registered communities are acquired. For example, if the user ID is “yamada@xxx.ww”, “education community” is acquired as a registered community, and if the user ID is “kuroda@xxx.ww”, “education community”, Acquire three patent patents and tennis.

  Thereafter, the mail list display screen 900 shown in FIG. 9 is created based on the received mail DB 240 of the user ID shown in FIG. 7 (step S1608). Specifically, e-mail information in which information in at least one of the “sender ID” and “destination” fields matches the information of the user ID is extracted, and the e-mail list display screen is based on the extracted e-mail information. Create screen information. At this time, the CPU 301 may create screen information of a mail list display screen in which mail generation dates and times are sorted in ascending order.

  Then, the CPU 301 transmits screen information of the mail list display screen to the client terminal 202 (step S1609). This client terminal 202 is the client terminal 202 that has requested the display request for the mail list display screen received in step S1601.

  Thereafter, the CPU 301 determines whether a display end request has been received from the client terminal 202 (step S1610). The display end request can be made, for example, when the user presses the “logout” button B3 on the mail list display screen 900 shown in FIG. If no termination request has been received (step S1610: NO), the process proceeds to step S1701 in the flowchart of FIG. On the other hand, when the termination request is received (step S1610: Yes), the series of processes is terminated.

  Next, in the flowchart of FIG. 17, the CPU 301 determines whether a message creation request has been received from the client terminal 202 (step S1701). The message creation request can be made, for example, when the user presses the “message creation” button B1 or the “reply” button B2 on the mail list display screen 900 shown in FIG. Here, it is determined whether it is a reply mail creation request, that is, whether the pressed button is the button B1 or the button B2 (step S1702).

  If it is a reply mail creation request in step S1702, that is, if the button B2 is pressed (step S1702: Yes), the CPU 301 acquires a reply source message from the mail DB 240 of the user ID and sends the message ( A message creation screen using the text as a quote is created (step S1703), and the created message creation screen is transmitted to the client terminal 202 by the CPU 301 (step S1704). Then, the CPU 301 obtains a reply source mail address as a destination from the reply screen (step S1705).

  Furthermore, the creation process of the creation screen with application cooperation is performed (step S1706). The creation processing of the creation screen with application cooperation will be described in detail with reference to the flowchart of FIG.

  Thereafter, the CPU 301 determines whether a mail transmission request is received from the client terminal 202 (step S1707). Here, after waiting for the reception of the mail transmission request (step S1707: No), when the mail transmission request is received (step S1707: Yes), the CPU 301 registers the mail message information in the destination mail DB 240. (Step S1708). The mail transmission request includes at least a transmission user request, a sender user ID corresponding to the sender ID of the mail DB 240, a subject, a body text, and a destination. In the flowchart of FIG. 18, in order to make the explanation of the invention easier to understand, the process waits until a transmission request arrives in step S1707. However, when there is no transmission request, the actual movement proceeds to step S1710. May be.

  If SNS message information is included in the transmission request, the SNS message information is registered in the corresponding community field of the SNS message DB 250 (step S1709).

  Thereafter, the CPU 301 determines whether a display end request has been received from the client terminal 202 (step S1710). The display end request can be made, for example, when the user presses the “logout” button B6 on the message creation screens 1000, 1100, and 1200 shown in FIGS. If no display end request has been received (step S1710: NO), the process proceeds to step S1701. On the other hand, when a display end request is received (step S1710: Yes), a series of processing ends.

  On the other hand, if it is not a reply mail creation request in step S1702, that is, if button B3 is pressed (step S1702: No), CPU 301 creates a message creation screen for new creation (step S1711). The created message creation screen is transmitted to the client terminal 202 (step S1712).

  Thereafter, the CPU 301 determines whether or not another application message display request (destination information) has been received (step S1713). Here, when the other application message display request (destination information) is received (step S1713: Yes), the creation process of the creation screen with application cooperation is performed (step S1714). The creation processing of the creation screen with application cooperation will be described in detail with reference to the flowchart of FIG.

  Thereafter, the CPU 301 determines whether a mail transmission request is received from the client terminal 202 (step S1715). If no mail transmission request is received (step S1715: NO), the process returns to step S1713. On the other hand, when a mail transmission request is received (step S1715: Yes), the process proceeds to step S1708, and the processes after step S1708 are executed. As described above, the transmission request is on standby until the transmission request arrives in step S1707 in the flowchart of FIG. 18, but the actual movement may be shifted to step S1710 when there is no transmission request. .

  Accordingly, the mail list display screen 900 shown in FIG. 9 and the message creation screens 1000, 1100, and 1200 shown in FIGS. 10 to 12 can be provided to the client terminal 202 in response to various display requests from the user. .

(Create screen creation process with linked apps)
Next, the procedure of the creation process of the creation screen with the cooperation application in steps S1706 and S1714 in FIG. 17 will be described. FIG. 18 is a flowchart illustrating an example of a specific processing procedure of the creation process of the creation screen with the cooperation application according to the embodiment. In the flowchart of FIG. 18, first, the CPU 301 determines whether or not the acquired destination is registered for use in the SNS user DB 230 (step S1801).

If the destination is not registered in the SNS user DB 230 (step S1801: No), the CPU 301 creates an SNS cooperation screen as a message creation screen, and transmits a screen without a community name to the client terminal 202 ( Step S1802), the creation processing of the creation screen with application cooperation is terminated.

  If the destination is registered in the SNS user DB 230 in step S1801 (step S1801: Yes), the CPU 301 determines whether there is a community in which the user and the destination participate in common (step S1801). S1803). Here, when there is no community in which the user and the destination are participating in common (step S1803: No), the process proceeds to step S1802, and the CPU 301 creates an SNS cooperation screen on the message creation screen, and sets the community name. A screen with no application is transmitted to the client terminal 202, and the creation processing of the creation screen with application cooperation is terminated.

  On the other hand, when there is a community in which the user and the destination are participating in common (step S1803: Yes), the CPU 301 acquires the community participating in common from the SNS user DB 230 (step S1804). When there are a plurality of destinations, each destination is acquired.

  Next, it is discriminate | determined by CPU301 using the SNS message DB250 whether the community containing the message which a user has not read exists among the acquired communities (step S1805). Then, it is determined whether or not there is a community including an unread message (step S1806). If there is no community including an unread message, the step (S1806: No) proceeds to step S1802. On the other hand, when there is a community including an unread message (step S1806: Yes), the CPU 301 creates an SNS cooperation screen on the message creation screen, and transmits a screen in which a list of acquired community names is added (step S1807). ).

  Thereafter, the CPU 301 determines whether or not the selected community name has been received from the client terminal 202 from among the community names added to the message creation screen (step S1808). Here, when the selected community name is received (step S1808: Yes), the CPU 301 acquires an unread message from the corresponding community in the SNS message DB (step S1809), and adds the acquired unread message to the SNS cooperation screen. The creation screen is transmitted to the client terminal device 202 (step S1810), and the creation processing of the creation screen with application cooperation is terminated.

  If the selected community name is not received from the client terminal 202 in step S1808 (step S1808: No), the creation process of the creation screen with application cooperation is terminated without doing anything.

  As described above, in the creation processing of the creation screen with the cooperation application, when there is an unread message in the community in which the user and the destination participate in common, the SNS cooperation screen of the mail message creation screen is displayed. An unread message is displayed by displaying a list of the community names and selecting the community names displayed in the list.

  Therefore, the user can easily request an unread message of the community related to the destination without being aware of the SNS application only by requesting display of the message creation screen (or simply specifying the destination from the message creation screen). Can be confirmed.

(Information processing procedure of client terminal 202)
Next, an information processing procedure of the client terminal 202 according to the embodiment will be described. 19 and 20 are flowcharts illustrating an example of an information processing procedure of the client terminal 202 according to the embodiment. In the flowchart of FIG. 19, first, the CPU 401 determines whether or not a mail display request has been accepted by a user operation input using the keyboard 410 or the mouse 411 (step S1901).

  Here, the CPU 401 waits to receive a mail display request (step S1901: No). If the mail display request is received by the CPU 401 (step S1901: Yes), the mail display request is transmitted to the information providing apparatus 201 (step S1902).

  Next, the CPU 401 determines whether or not screen information of a user ID / password input screen (not shown) is received from the information providing apparatus 201 (step S1903). Here, it waits for the CPU 401 to receive the screen information of the user ID and password input screen (step S1903: No).

  When the CPU 401 receives the screen information of the user ID / password input screen (step S1903: Yes), the CPU 401 displays the user ID / password input screen on the display 408 based on the received screen information. (Step S1904). Next, the CPU 401 determines whether an input of a user ID and a password has been received by a user operation input (step S1905).

  Here, it waits for the CPU 401 to accept the input of the user ID and password (step S1905: No). When the CPU 401 receives input of the user ID and password (step S1905: Yes), the user ID and password are transmitted to the information providing apparatus 201 (step S1906).

  Next, the CPU 401 determines whether screen information of an authentication error screen (not shown) has been received (step S1907). Here, when the CPU 401 receives the screen information of the authentication error screen (step S1907: Yes), the authentication error screen is displayed on the display 408 based on the received screen information (step S1908). A series of processing ends.

  If the CPU 401 has not received the screen information of the authentication error screen in step S1907 (step S1907: No), it is determined whether the screen information of the mail list display screen has been received (step S1909). If the screen information of the mail list display screen is not received by the CPU 401 (step S1909: No), the process returns to step S1907.

  On the other hand, when the screen information of the mail list display screen is received by the CPU 401 (step S1909: Yes), the mail list display screen is displayed on the display 408 based on the received screen information (step S1910). Thereafter, it is determined whether an end request has been accepted (step S1911). When the CPU 401 accepts an end request, that is, when the “logout” button B3 on the mail list display screen 900 shown in FIG. 9 is pressed (step S1911: Yes), a series of processing according to this flowchart is performed. Exit. On the other hand, when the termination request has not been received (step S1911: No), the process proceeds to step S2001 shown in FIG.

  In the flowchart of FIG. 20, first, the CPU 401 determines whether a message creation request has been received from the information providing apparatus 201 (step S2001). If no message creation request has been received (step S2001: NO), the process proceeds to step S1911. On the other hand, when the message creation request has not been received (step S2001: Yes), the CPU 401 transmits a message creation request to the information providing apparatus 201 (step S2002). The message creation request includes both new creation and reply.

  Then, the CPU 401 determines whether the message creation request is a reply mail (step S2003). If the message creation request is a reply mail, that is, if the button B2 is pressed on the mail list display screen 900 (step S2003: Yes), the CPU 401 displays a message creation screen with a cooperation screen (for reply). It is determined whether the information is received from the information providing apparatus 201 (step S2004).

  Here, the CPU 401 waits for reception of the message creation screen with a cooperation screen (for reply) (step S2004: No), and if received (step S2004: Yes), the CPU 401 uses the received screen information based on the received screen information. Then, a message display screen (for example, the message creation screen 1100 shown in FIG. 11) is displayed on the display 408 (step S2005).

  Next, whether or not another application message display request has been received by the CPU 401, that is, addition or change of the content input in the “destination” box 1101 on the message creation screens 1100 and 1200 shown in FIGS. After the deletion, it is determined whether or not the button B5 is pressed (step S2006). If no other application message display request has been received (step S2006: No), the process proceeds to step S2014. On the other hand, when the other application message display request is received (step S2006: Yes), the CPU 401 transmits the other application message display request to the information providing apparatus 201 (step S2007).

  Then, the CPU 401 determines whether a message creation screen with a cooperation screen has been received from the information providing apparatus 201 (step S2008). Here, it waits for the CPU 401 to receive the message creation screen with a cooperation screen (step S2008: No), and when it is received (step S2008: Yes), the CPU 401 displays the display 408 based on the received screen information. A message creation screen (for example, the message creation screen 1100 shown in FIG. 11) is displayed (step S2009). In the message display screen displayed here, an SNS cooperation screen 1106 updated in a state where the content input in the “destination” box 1101 is added, changed, or deleted is displayed.

  Thereafter, the CPU 401 determines whether or not a community selection has been accepted (step S2010). Here, when the selection of a community is not received (step S2010: No), it transfers to step S2014. On the other hand, when the selection of a community is received (step S2010: Yes), the CPU 401 transmits the selected community name to the information providing apparatus 201 (step S2011).

  Then, the CPU 401 determines whether a message creation screen with a cooperation screen has been received from the information providing apparatus 201 (step S2012). Here, the CPU 401 waits for reception of the message creation screen with a cooperation screen (step S2012: No), and if received (step S2012: Yes), the CPU 401 displays the display 408 based on the received screen information. The message creation screen (for example, the message creation screen 1200 shown in FIG. 12) is displayed (step S2013).

  Next, the CPU 401 accepts a text or the like (step S2014). Specifically, input to the article input screen boxes 1004 and 1104 is accepted. It also accepts input to the subject box 1003, 1103. Also, input to the comment input fields 1207 and 1208 of the SNS cooperation screen 1206 is accepted.

  Thereafter, the CPU 401 determines whether a transmission request has been accepted (step S2015). Specifically, it is determined whether or not the “Send” button B4 on the message creation screens 1000, 1100, and 1200 has been pressed. Here, when the transmission request is not received (step S2015: No), the CPU 401 determines whether or not the display end request is received, that is, whether or not the “logout” button B6 is pressed (step S2016). ), When the display end request is not received (step S2016: No), the process proceeds to step S2014. On the other hand, when a display end request is received (step S2016: Yes), a series of processes according to this flowchart is ended.

  In step S2015, when a transmission request is accepted (step S2015: Yes), the CPU 401 transmits a transmission request, a sender user ID, a subject, a destination, a text, an SNS message, and the like to the information providing apparatus 201 (step S2015). S2017). Thereafter, the CPU 401 determines whether a mail list display screen has been received (step S2018). Then, after waiting for the reception of the mail list display screen (step S2018: No), when the mail list display screen is received (step S2018: Yes), the process proceeds to the flowchart 1910 of FIG.

  If the message creation request is not a reply mail in step S2003, that is, if button B1 is pressed on mail list display screen 900 (step S2003: No), CPU 401 determines whether a message creation screen has been received. (Step S2019). Here, it waits for reception of the message creation screen (step S2019: No), and when it is received (step S2019: Yes), the message creation screen 1000 shown in FIG. 10 is displayed (step S2020).

  Next, whether or not another application message display request has been received by the CPU 401, that is, contents are input to the “Destination” box 1001 and “CC:” box 1002 on the message creation screen 1000 shown in FIG. Above, it is judged whether button B5 was pressed (step S2021). If no other application message display request is received (step S2021: No), the process proceeds to step S2014.

  On the other hand, when the other application message display request is received (step S2021: Yes), the CPU 401 acquires the input destination information from the message creation screen (step S2022), and the other application message display request and the acquired destination information. Is transmitted to the information providing apparatus 201 (step S2023). And it is judged whether the message preparation screen with a cooperation screen was received from the information provision apparatus 201 (step S2024).

  Then, the CPU 401 waits for the message creation screen with the cooperation screen to be received (step S2024: No), and if received (step S2024: Yes), the CPU 401 displays the message information on the display 408 based on the received screen information. A message creation screen (for example, the message creation screen 1000 shown in FIG. 10 and the SNS cooperation screen 1106 shown in FIG. 11 displayed together) is displayed (step S2025). In the message display screen displayed here, the SNS cooperation screen 1106 created in the state input in the “destination” box 1101 is displayed.

  Thereafter, the process proceeds to step S2010. And the process after step S2010 is performed.

  As described above, according to the information providing apparatus 201 according to the embodiment, the SNS message can be confirmed from the mail message creation screen on the mail message creation screen, and the message for the SNS message can be confirmed. Can also be entered and registered together with a reply to the e-mail from the e-mail message creation screen, so that the message transmitted by the SNS can be confirmed without starting the SNS application, and the message corresponding to the confirmed message is SNS Can communicate (reply) to.

  This makes it possible to avoid failing to confirm and fail to reply to messages stored in other message providing systems in a timely manner simply by displaying the message creation screen. The providing system can be efficiently used using electronic mail.

  In addition, according to the information providing apparatus 201 according to the embodiment, since only the message of the group (community) common to the user related to the destination information and the user related to the sender information is displayed, the message related to the reply mail is displayed. Because there is a possibility, information transmission becomes more efficient. Further, only unread messages may be displayed, and even if the number of stored messages increases, the messages can be confirmed efficiently.

  In the present embodiment, the SNS has been described. However, the present invention is not limited to the SNS, and can be applied to other information providing systems such as a chat.

  The information providing method described in the embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. The information providing program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. The information providing program may be distributed via a network such as the Internet.

  The following additional notes are disclosed with respect to the embodiment described above.

(Supplementary note 1)
Accept a request to display the email message creation screen,
Obtaining sender information and destination information on the message creation screen corresponding to the received display request;
Based on the acquired sender information and the destination information, extract a message stored in a message storage unit of another message providing system,
Creating a message creation screen that includes a first input area for inputting the e-mail message and a second input area for inputting a message for the extracted message;
Output the created message creation screen,
Accept the message transmission request entered on the output message creation screen,
In response to the accepted transmission request, the message input in the first input area is stored in an e-mail message storage unit;
In response to the accepted transmission request, the message input to the second input area is stored in the message storage unit of the other message providing system.
An information providing program for executing a process.

(Supplementary Note 2) The process of extracting the message is as follows:
Both the user information related to the sender information and the user information related to the destination information are stored in the message storage unit of the other information providing system as messages of other information providing system groups registered. The information providing program according to appendix 1, wherein a message is extracted.

(Supplementary Note 3) The process of extracting the message is as follows:
Supplementary note 2 characterized in that a user associated with the sender information extracts an unread message among messages stored in a message storage unit of another information providing system stored as the group message. Information providing program.

(Appendix 4) The process of accepting a display request for the e-mail message creation screen is as follows:
Accept a request to display a message creation screen for replying to received emails,
The process of acquiring the sender information and the destination information includes
The information provision according to any one of appendices 1 to 3, wherein the sender information is acquired with the destination of the received e-mail as a sender, and the destination information is acquired with the sender of the received e-mail as a destination. program.

(Supplementary Note 5) The other message providing system is an SNS (Social Networking Service) providing system that stores a message for each community.
The process of extracting the message includes:
Of the messages stored in the message storage unit of the SNS providing system, a community in which both the user related to the sender information and the user related to the destination information are registered based on the sender information and the destination information. The information providing program according to any one of appendices 1 to 4, wherein the message is extracted.

(Appendix 6) a display request receiving unit that receives a display request for an e-mail message creation screen;
An acquisition unit for acquiring sender information and destination information related to the message creation screen corresponding to the display request received by the display request reception unit;
An extraction unit for extracting a message stored in a message storage unit of another message providing system based on the sender information and the destination information acquired by the acquisition unit;
A creation unit for creating a message creation screen including a first input area for inputting the email message and a second input area for inputting a message for the message extracted by the extraction unit;
An output unit for outputting the message creation screen created by the creation unit;
A transmission request reception unit that receives a transmission request for a message input to the message creation screen output by the output unit;
In response to the transmission request received by the transmission request reception unit, the message input in the first input area is stored in an e-mail message storage unit,
A storage unit for storing a message input to the second input area in a message storage unit of the other message providing system in response to the transmission request received by the transmission request reception unit;
An information providing apparatus comprising:

(Appendix 7) The computer
Accept a request to display the email message creation screen,
Obtaining sender information and destination information on the message creation screen corresponding to the received display request;
Based on the acquired sender information and the destination information, extract a message stored in a message storage unit of another message providing system,
Creating a message creation screen that includes a first input area for inputting the e-mail message and a second input area for inputting a message for the extracted message;
Output the created message creation screen,
Accept the message transmission request entered on the output message creation screen,
In response to the accepted transmission request, the message input in the first input area is stored in an e-mail message storage unit;
In response to the accepted transmission request, the message input to the second input area is stored in the message storage unit of the other message providing system.
An information providing method characterized by executing processing.

200 Mail System 201 Information Providing Device 202 Client Terminal 1501 Reception Unit 1502 Acquisition Unit 1503 Extraction Unit 1504 Creation Unit 1505 Output Unit 1506 Storage Unit 1000, 1100, 1200 Message Creation Screen

Claims (6)

On the computer,
Accept a request to display the email message creation screen,
Acquire sender information and recipient information on the accepted message creation screen,
Based on the acquired sender information and destination information, extract the message stored in the message storage unit of another message providing system,
Create a first input region for inputting the e-mail message, and the message extracted, and a second input region for inputting a message to extracted the message, the message creation screen including,
Output the created message creation screen,
Accept the message transmission request entered on the output message creation screen,
In response to the accepted transmission request, the message input in the first input area is stored in an e-mail message storage unit;
In response to the accepted transmission request, the message input to the second input area is stored in the message storage unit of the other message providing system.
An information providing program for executing a process. The process of extracting the message includes:
A message stored in a message storage unit of the other information providing system as a message of a group of another information providing system in which both the user information related to the sender information and the user related to the destination information are registered The information providing program according to claim 1, wherein the information providing program is extracted. The process of extracting the message includes:
3. The message according to claim 2, wherein a user associated with the sender information extracts an unread message from messages stored in a message storage unit of another information providing system stored as the group message. The information provision program described. The process of accepting a display request for the e-mail message creation screen is as follows:
Accept a request to display a message creation screen for replying to received emails,
The process of acquiring the sender information and the destination information includes
The information providing program according to any one of claims 1 to 3, wherein the sender information and the destination information are acquired by using the destination of the received electronic mail as a sender and the sender as a destination. A display request reception unit for receiving a display request for an e-mail message creation screen;
An acquisition unit for acquiring sender information and destination information on the message creation screen received by the display request reception unit;
An extraction unit that extracts a message stored in a message storage unit of another message providing system based on the sender information and the destination information acquired by the acquisition unit;
Creating a first input region for inputting the e-mail message, and the message extracted by the extraction unit, and a second input region for inputting a message to extracted the message, the message creation screen including the A creation department to
An output unit for outputting the message creation screen created by the creation unit;
A transmission request reception unit that receives a transmission request for a message input to the message creation screen output by the output unit;
In response to the transmission request received by the transmission request reception unit, the message input in the first input area is stored in an e-mail message storage unit,
A storage unit for storing a message input to the second input area in a message storage unit of the other message providing system in response to the transmission request received by the transmission request reception unit;
An information providing apparatus comprising: Computer
Accept a request to display the email message creation screen,
Acquire sender information and recipient information on the accepted message creation screen,
Based on the acquired sender information and destination information, extract the message stored in the message storage unit of another message providing system,
Create a first input region for inputting the e-mail message, and the message extracted, and a second input region for inputting a message to extracted the message, the message creation screen including,
Output the created message creation screen,
Accept the message transmission request entered on the output message creation screen,
In response to the accepted transmission request, the message input in the first input area is stored in an e-mail message storage unit;
In response to the accepted transmission request, the message input to the second input area is stored in the message storage unit of the other message providing system.
An information providing method characterized by executing processing.

Images