JP2011118931A - Message transmission/reception control method and message transmission/reception control system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method of controlling transmission and reception of message in which both of a message transmitter and message receiver correctly comprehends the state of the message excellent in certainty, reliability, and confidentiality. <P>SOLUTION: The method creates message attribute information H for defining a message M from the message M according to a user for transmitting the message M and a user for receiving the message M. The user receives a message body C defined by the message attribute information H by viewing the message attribute information H, and the message attribute information H of the transmitting user and the message attribute information H of the receiving user are updated by synchronizing with accesses to the body of the message C so that the transmission and reception state of the message body C is confirmed by viewing the message attribute of information H. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a message transmission / reception management method and a message transmission / reception management system for transmitting / receiving a message via a communication network.

  Conventionally, electronic mail has been widely used as a method for communicating via a communication network. This e-mail is sent to an Internet provider (provider) who creates a mail on a terminal (for example, a personal computer) and issues the sender's mail account using a communication means such as a telephone line. The provider temporarily stores the received mail in an e-mail server, and forwards the mail to the provider that issues the recipient's mail account through the Internet. Since the forwarded mail is stored in the mail server of the recipient provider, the provider connects the terminal to the provider using a communication means such as a telephone line and makes a mail reception request. By sending the mail stored in the receiver to the receiver's terminal via a communication means such as a telephone line, the receiver can obtain the mail on the terminal (for example, a personal computer). is there.

  However, it is recognized that there are the following problems in the current electronic mail.

  Since the distribution status of the e-mail depends on the setting of each transmission / route server, the e-mail transmitted from the sender to the provider does not always flow on the Internet and is received by the destination server.

  In addition, because the source server does not guarantee delivery of the email to the destination, the destination server does not always send an operation completion signal and the source server receives it. It is impossible to know the very important elements in communication such as “when did it arrive” and “when the other party read the mail”.

  In addition, if a message is lost due to a problem with each sending / passing server or network, the sender cannot always confirm the fact that the sending has failed. "I can't know for sure that there was a very serious problem in information transmission."

  In addition, SMTP (Simple Mail Transfer Protocol) and POP (Post Office Protocol), which are communication protocols generally used for sending and receiving e-mail, do not use an encryption function. Communicating in a state. For this reason, the confidentiality of electronic mail is not sufficiently ensured, and it is difficult to communicate important communications and documents that require confidentiality by email.

  And in the current standard e-mail browsing software (mail client software), the mail itself is downloaded from the mail server and used, so it is necessary to set the mail software for each mail terminal and each mail account. For users who use a plurality of terminals and a plurality of mail accounts, the setting is troublesome. In addition, the above software is usually set to delete the mail on the server after it has been downloaded, so once you read the mail on one terminal, the mail cannot be read on other terminals, It is distributed for each terminal. As a result, information in electronic mail is dispersed, which hinders smooth communication.

  The present invention solves the above-mentioned problems, allows the sender and recipient to always correctly grasp the state of the transmitted message, and manages the transmission and reception of messages with excellent reliability, reliability, and confidentiality. It is an object of the present invention to provide a method and a message transmission / reception management system.

  In order to solve the above problems, a message transmission / reception management method according to the present invention is characterized by comprising the following requirements for managing message transmission / reception via a communication network.

(B) A message for storing message attribute information related to a message including a user account uniquely set for the user and the message sender, recipient, transmission date and time, whether or not the message has been received, reception date and time, and title (B) When the user sends a message, the message attribute information is created corresponding to the user who sends the message and all the users who receive the message. The created message attribute information is stored in the user-specific message attribute information database. (C) The user can browse the user-specific message attribute information database via the communication network. Unique message attribute information database The message defined in the message attribute information can be received by requesting to receive the message by specifying any message attribute information from the message attribute information stored in the message attribute information database. (E) The user can check the message transmission / reception status defined in the message attribute information by browsing any message attribute information contained in the user-specific message attribute information database. (F) The user is user-specific. By browsing any message attribute information contained in the message attribute information database of, it is possible to check the open status of all recipients of the message for each message received by the user. Whether or not In addition to the message attribute information, including information on whether or not the recipient has received the message, instead of the message attribute information, the sending user has been given to the message body part as management information having an account. When the user receives an unread message, the information about the reception is updated in synchronization with the message attribute information of the sending user and the message attribute information of the receiving user, and the message attribute information of the sending user and the receiving side are updated. Information identity with the user's message attribute information may be ensured.

  In addition, a message body portion including a message transmission content of the message transmitted by the user may be stored in the message body storage area.

  The message body storage area is preferably a message body storage area unique to a user who transmits the message.

  Then, user authority information that permits reading, writing, deletion, transfer, etc. to the message is given to at least one of the message attribute information and the message body part, and access by a user that does not match the user authority information It is preferable to restrict access to the message body portion for requests and access requests other than authorized rights.

  Further, information for managing transmission / reception of a message, such as whether the transmission of the message is completed or whether the receiver has received the message, is attached to the message body portion instead of the message attribute information, and the message attribute information Is limited to information necessary for accessing the message body, and information updated by transmission / reception of the message is preferably given to the message body portion so that the updated information is not distributed.

  Furthermore, at least one of the message body part and the message attribute information may be encrypted and stored.

  The message transmission / reception management system according to the present invention includes the following requirements for managing message transmission / reception via a communication network.

(A) Each user's user account is uniquely registered in the message processing server, and stores message attribute information including the sender, recipient, date / time of transmission, whether received, date / time, and title A message attribute information database unit for storing a message body information storage unit for storing a message body part including a transmission content of the transmitted message. , From the received message, the message body portion including the message transmission content is stored in the message body information storage unit, and the sender defining the message, the receiver, the transmission date and time, whether or not the reception has been received, the reception date and time, The message attribute information of the title is the same as the user sending the message Each message attribute information created is stored in the message attribute information database specific to the user in the message attribute information database section. (C) The message processing server is accessed through the communication network. (D) The user browses the user-specific message attribute information database, designates any message attribute information, and stores the message main body part. By requesting the message processing server to receive, the message body part defined in the message attribute information can be received. (E) Each user accesses the message processing server to access a message attribute unique to the user. By browsing any message attribute information included in the information database, the message transmission / reception status defined in the attribute information can be confirmed. (F) The user can select any message attribute included in the user-specific message attribute information database. By browsing the information, for each message received by the user, the opening status of all the receiving users of the message can be confirmed. (G) Whether the message has been sent or not, the receiver has received the message. Information for managing transmission / reception of messages including whether or not the message attribute information has been added to the message body portion as management information having an account by the sending user. Access the message processing server By receiving the unread message, the information related to the reception is updated in synchronization with the message attribute information database of the sending user and the message attribute information database of the receiving user, and the message attribute information of the sending user related to the message It is preferable to ensure the sameness of information between the message attribute information of the receiving user and the receiving user.

    The message body information storage unit for storing the message body information is preferably a message body information storage unit unique to the user who transmitted the message.

    Then, the message processing server sends at least one of the message attribute information and the message body part user authority information that permits reading, writing, deletion, transfer, etc. to the message body part stored in the message body information storage unit. It is preferable to restrict access to the message main body portion for an access request given to one of the users and an access request by a user who does not match the user authority information or an access request other than the authorized authority.

    Further, the message processing server replaces the message attribute information with information for managing the transmission / reception of the message, such as whether or not the transmission of the message is completed and whether or not the message is received by the recipient, in the message body portion. It is preferable that the message attribute information is limited to information necessary for accessing the message body, and the information updated by sending and receiving the message is given to the message body portion so that the updated information is not distributed. .

    Further, the message processing server encrypts at least one of the message body part and the message attribute information, and stores the decryption key in at least one of the user terminal and the message processing server. It is preferable to ensure confidentiality.

    Then, the message processing server may store the message body information including a file or application software in the message body information storage unit.

    Furthermore, it is preferable that the message processing server is linked with an e-mail server that manages e-mail transmission / reception, and performs e-mail transmission / reception management together with message transmission / reception management so that it can be installed together with the current e-mail system.

    Furthermore, the message processing server converts the message into an e-mail and requests the e-mail server to send an e-mail if the recipient address of the message received from the user is an e-mail address. Also good.

    The message processing server includes a message transmission / reception process for processing message transmission / reception or a processing apparatus thereof, a message body information storage process for storing message body information or a processing apparatus thereof, an e-mail transmission / reception process for processing e-mail transmission / reception, or Preferably, the processing device and the message attribute information database processing for processing the message attribute information data or at least one processing or processing device of the processing device are distributed.

  According to the message transmission / reception management method and the message transmission / reception management system of the present invention, the message main body and the message attribute information for the sender related to the message and the message attribute information for the receiver from the message transmitted from the user to the message processing server, The user can reliably manage the transmission / reception state of the message by browsing the message attribute information through his / her own message attribute information database.

    Then, by checking the message attribute information, the sender side can check whether or not the message sent by the sender is received by the receiver, and if it is received, the date and time can be confirmed. By viewing the message attribute information addressed to you and performing the receiving operation on the receiver side, you can receive the message defined in the message attribute information, so you can receive the message from any terminal any number of times. The message is not distributed to a plurality of terminals.

    In addition, since the message body does not move from the message body information storage unit of the message processing server having the user account of the sender to another message processing server or the like, the message confidentiality is maintained and the message management is ensured. The message is not lost due to a trouble when moving like e-mail.

    Furthermore, if user authority information that allows reading, writing, deleting, forwarding, etc. of messages is added to the message attribute information, in addition to the operation requests permitted by the users who are permitted to operate in the user authority information of the message attribute information Since the message body cannot be operated, it is possible to improve the durability against unauthorized intrusion and attack on the message processing server.

    Note that attribute information for accessing the message body from all message attribute information and whether the message has been received, information for managing the message body, such as the reception date and time, are extracted, and the extracted attribute information is stored in the attribute information database. If the management information is stored together with the message body, only the information for accessing the message body is stored in the attribute information database of the receiver, and the management information for managing the message body and the message body is stored in the message processing server of the sender. Since the information is stored, unlike the case where the management information is included in the attribute information, there is no occurrence of data mismatch in the management information or the like due to an update processing trouble between the distribution source and the distribution destination. Moreover, by transmitting and receiving a minimum amount of information, it is possible to reduce the load of transmission and reception processing of the message processing server.

    Further, for an information management company such as a provider using the message transmission / reception management system of the present invention, the message body is encrypted and stored, and the decryption key is stored in the message attribute information corresponding to the message. In the unlikely event of an unauthorized intrusion or attack on the message processing server, there is no concern that the message body will be decrypted unless the decryption key stored in the message attribute information database is viewed by an intruder.

    And, if the file or application software that the user wants to publish or share is stored in the message storage area instead of the message body or in addition to the message body, the apparent data exchange without moving the file or application software, It is possible to share and prevent multiple copies and multiple transfers, so there is no load on the system, and it is easy to update information such as version upgrades. Because application software is used, it is possible to resolve inconsistencies due to version differences and to update information such as schedule changes at the same time.

    Furthermore, it can coexist with the current mainstream e-mail system, and even e-mails from e-mail users can be managed in the same way as messages from users under the control of the message processing server. Since transmission / reception can be performed, it is possible for an information management company such as a provider to smoothly cope with a transition period.

Network diagram to which message transmission / reception management method according to the present invention is applied Explanatory drawing of the operation screen for messages created by the sender Illustration of the display screen when the recipient receives the message Explanatory drawing of a display screen showing an example of message attribute information Illustration of the display screen for checking the status of the message sent by the sender Illustration of the display screen when the recipient receives the message Illustration of the display screen for checking the status of the message sent by the sender Configuration diagram of message processing server Operation explanatory diagram of the message management system for explaining the flow of messages and message attribute information by the message transmission / reception management method Operation explanatory diagram of the message management system for explaining the conventional e-mail processing in the message processing server The block diagram which shows the other example of the message processing server in the transmission / reception management method of a message (A)-(d) is a table | surface table | surface which shows an example of the information in the transmission / reception management method of the message of said other example

  A mode for carrying out the invention will be described with reference to the drawings.

  FIG. 1 shows an example of a schematic network configuration diagram for explaining a message transmission / reception management method via a communication network according to the present invention and a message transmission / reception management system for managing message transmission / reception by the transmission / reception management method. The figure shows a state in which a large number of host computers 1 and a large number of user terminals 2 are connected via a communication network 3, and the host computer 1 that performs the message transmission / reception management method of the present invention is a message processing server. S is displayed.

  The message processing server S accepts a message transmitted via the communication network 3 by the user terminal 2 that is the sender who created the message, and accepts it in response to a request from the user terminal 2 that is the recipient of the message. In this embodiment, the communication network is limited to the Internet. However, the communication network is limited to the Internet. It may be a LAN or a combination of a LAN and the Internet.

  In FIG. 1, when a user 2 (User01) transmits a message to other users 2 (User02, 03) via the communication network 3, the user 2 who is the sender is displayed on the operation screen as shown in FIG. (User01) in the sender display field a, the recipient user 2 (User02, 03) in the receiver description field b, the title attached to this message in the title description field c, and the message to be communicated After entering the information required for transmission into the user terminal in the form of filling in the description column d, the transmission processing execution key e is selected and the message is transmitted.

  When the created message is sent, the sender of the message, the recipient, the sending time, whether the message has been received, the message attribute information such as the receiving time, the title, etc., the user who sends the message 2 (User01) and all users 2 (User02, 03) receiving the message.

  FIG. 3 shows a reception screen when User02, one of the users (recipients) 2 who receives the message, receives the message. The recipient 2 (User02) receives his message attribute information (FIG. 4). If there is a record that the message addressed to me is sent in the message attribute information, the user 2 (User 02) who is the recipient is one of the titles (for example, unread field) When a message acquisition request is made by selecting a message having an icon displayed thereon, the main part of the requested message is transmitted to the user 2 (User02). At that time, if the requested message is unread before acquisition, the message main part of the message is received by the user 2 (User02) in the message attribute information unique to the message of the user 2 (User02) who received the message. In addition, information related to reception such as date and time of reception is updated.

  Further, in synchronization with the update of the message attribute information of the recipient, the message attribute information unique to the sender's message is updated, and the message sent to a certain recipient is received in the message attribute information unique to the sender's message. Information such as the date and time of reception at the user's terminal is updated.

  Thus, the sender display field e has the name of User01 as the sender, the transmission time display field f has the time when the sender sent the message, and the message reception display field g has the receiver 2 (User02). Displays the date and time when the message was received. When the message is displayed in the message display field h, information indicating that the message attribute information of the receiver and the sender related to this message has been updated is displayed in the message transmission / reception status display field i (see FIG. 3). .

  In synchronization with the update of the message attribute information of the recipient, the message attribute information unique to the sender's message is updated, and the message sent to a certain recipient is added to the message attribute information unique to the sender's message. Since information such as the reception date and time of reception is updated, the sender User01 is updated by selecting an operation screen (see FIG. 5) for checking the status of the transmitted message. The message attribute information unique to User01 can be confirmed.

  At this point, since User 03 has not acquired the message, only the information that User 02 has confirmed the message is written and updated in the message attribute information of the sender and each receiver. Thereby, both the message sender and the message receiver can grasp the delivery state of the message by checking the transmission / reception status display field i of the transmitted message.

  FIG. 6 shows an example of a reception screen when the user User03 who has not received the message has received the message. When the User03 has viewed the message, the message reception display field g displays the recipient 3 (User03). ) Displays the date and time when the message was received. When the message is displayed in the message display field h, information indicating that the message attribute information of the receiver and the sender related to this message has been updated is displayed in the message transmission / reception status display field i.

  FIG. 7 is an example of a transmission confirmation screen shown to the sender. When User03 browses the message, the message attribute information unique to the user of the sender and each recipient is updated with information that all information has been browsed. Thereby, when the message attribute information is requested automatically or selected by the sender, the current status is displayed in the message transmission / reception status display field i. Thus, the sender can confirm that the message transmitted by the sender has been reliably transmitted, and at the same time can obtain information on when each message was viewed.

  In the above-mentioned message transmission / reception status display field i, the reception status of all recipients may be disclosed to the sender and all recipients of this message, or individual recipients may be disclosed. However, it may be possible to limit the status of disclosure to the public or only to the sender.

  FIG. 8 shows an example of a schematic configuration of the message processing server S that performs the above-described message transmission / reception management in the message transmission / reception management system of the present invention. The message processing server S performs conventional electronic mail transmission / reception management. The e-mail processing server E is linked to each other, and the message processing server S and the e-mail processing server E are connected by a dedicated line or the like, and perform information communication with each other. This configuration assumes that an Internet connection provider (hereinafter referred to as a provider) performs an e-mail transmission / reception management service and a message transmission / reception management service according to the present invention by a conventional e-mail processing server E. If the e-mail transmission / reception management is not required, the message processing server unit S may be used alone.

  In FIG. 8, the message processing control unit 10 interfaces with a communication network, and message attribute information such as a sender, a receiver, a transmission date and time, whether or not a message has been received, a reception date and time, a title, etc. The processing is sent to the message attribute information processing unit 11 in the message processing control unit 10, and the message body information part including the message transmission content is sent to the message body information processing unit 12 in the message processing control unit 10.

  The message attribute information portion includes a reference key with the message body in the message attribute information processing unit 11, a decryption key when the message body is encrypted and stored, a transmission date and time, and whether or not the receiving user has received the message body. Management information such as the reception date and time is added and stored in the message attribute information database unit 13 as message attribute information H unique to the message corresponding to the sender of this message and all the receivers who receive this message. The

  The message body information portion 12 is added with link information (for example, a reference key, a user key, etc.) linked to the message attribute information H in the message body information processing section 12 and is stored in the message body information storage section 14 as a message body C. Although stored in the message body information storage unit 14, a message body storage area is preset for each user, and the message body information processing unit 12 refers to the given link information (for example, a user key), 14 stores the message body C in the corresponding message body storage area.

  Note that user information that permits operations such as reading, writing, deleting, and forwarding on the message body C (for example, writing permission, reading permission, and deletion permission are given to the message sender, and reading permission is given to the message receiver. Is given to the message attribute information H, and the operation on the message main body part is restricted for an operation request other than authority by a user who does not match the user information or a user who matches the user information. May be. By the above operation, access from a user who does not have permission to read, write, delete, transfer, etc. to the system administrator or the message body C can be prevented, and access other than the given authority can be prevented, and the confidentiality of the message can be maintained. . Furthermore, the confidentiality of the message body C can be improved even when an unauthorized intrusion or attack is applied to the server.

  Further, the message body C is encrypted when the message body information storage unit 14 stores the message body storage area, and the decryption key used for decrypting the encryption is stored in the message corresponding to the message body C. It may be added to the attribute information H and stored. By the above operation, since the encryption of the message body C cannot be decrypted except by access from the message attribute information H having the decryption key, the confidentiality of the message body C can be improved as described above.

  The decryption key is stored in the user's terminal, and when the user views the message, the message body C in an encrypted state is transmitted from the message processing server S to the terminal and decrypted on the terminal side. You may make it browse.

  Further, the message processing server S includes a predetermined area other than the message attribute information database unit 13 and the message body information storage unit 14 in the message processing server S, and an encryption processing unit (not shown) that mainly performs encryption and decryption processing. Provided, when the decryption of the message body C is requested by the user, the message processing server S accesses the encryption processing unit for message restoration together with the message attribute information H possessed by the user and requests the decryption key. The encryption processing unit refers to the message attribute information H to determine whether or not the delivery of the decryption key is possible. If the decryption key is accepted, the decryption key is given to the message body information storage unit 14 and the message body C is disclosed to the user. Alternatively, the processing may be distributed to reduce the load on the message processing server S.

  Further, different encryption keys may be stored in the message processing server S and the user terminal, and a decryption key for data may be generated by collating or multiplying the two encryption keys.

  When a request is made to disclose the message body C from the user, the encryption processing unit that manages the encryption key of the message processing server S and performs the encryption and decryption processing is such that the terminal or the user uses a password, an external storage device, etc. The terminal-side encryption key is requested, and the data decryption key is generated by using the two encryption keys, the terminal-side encryption key and the server-side encryption key.

  When the user 2 accesses the message processing server S and the message attribute information H addressed to the user 2 exists, when the message processing server S requests the message processing server S to transmit the message body C, the message processing control unit 10 The message attribute information H is referred to via the unit 11, the message body C corresponding to the message attribute information H is read from the message body information storage unit 14 by the message body information processing unit 12, and the read message body C is stored in the user 2 Send to. At the same time, the message processing control unit 10 causes the message attribute information processing unit 11 to receive the message attribute information H of the receiving user and update the reception date and time, and to update the message attribute information H of the transmitting user synchronously. The message attribute information of the sending user and the message attribute information of the receiving user are ensured to be identical.

  Next, an example of a transmission / reception management method of how the message is managed by the message processing server when the user transmits the message will be described with reference to FIG.

  When the user 2a (sender) transmits the message M1 to the user 2b having a user account on the same message processing server S1 as the user 2a, the user 2a creates a message M1 for the user 2b on the terminal, and the user 2a The message processing server S1 is accessed based on the uniquely set user account, and the message M1 is transmitted to the message processing server S1 (a101).

  The message processing control unit 100 of the message processing server S1 receives the message M1 sent from the terminal of the user 2a, and separates the message M1 into message body C1 and message attribute information H1. The message body C1 is stored in the message body storage area 140a unique to the user 2a of the message body information storage unit 140 by the message body information processing unit 120 in the message processing control unit 100 (a102).

  The message attribute information H1 is stored by the message attribute information processing unit 110 in the message processing control unit 100, the message transmission date and time, whether or not the other party has read, the location where the message body C1 is stored, and the message body C1 is encrypted. Is added as the message attribute information H1a in the database area 130a unique to the user 2a of the message attribute information database unit 130 (a103).

  The message attribute information H1a is also stored in synchronization with the database area 130b unique to the user 2b (recipient). Since the user 2b has a user account on the same message processing server S1 as the user 2a, the user 2b is stored as message attribute information H1b having the same contents as the message attribute information H1a in the database area 130b unique to the user 2b (recipient) (a104 ).

  On the other hand, the user 2b who is the recipient of the message M1 accesses the message processing server S1 based on the user account set specifically for the user 2b (a201), and via the message attribute information processing unit 110 of the message processing server S1, The message attribute information H1b related to the message M1 addressed to the user stored in the database area 130b unique to the user 2b in the message attribute information database unit 130 is browsed (a202, a203).

  Since the message attribute information H1b stores a reference to the message body C1, the user 2b specifies the message attribute information H1b and requests the message processing server S1 to transmit the message body C1 (a204). The message processing server S1 transmits the message body C1 stored in the message body storage area 140a unique to the user 2a to the terminal of the user 2b via the message body information processing unit 120 (a205, a206). By this operation, the user 2b can receive the message M1 which is a message from the user 2a.

  As described above, after the message attribute information H1b is first stored in the database area 130b specific to the user 2b, the user 2b browses the database area 130b specific to the user 2b, and thereby receives the message M1 transmitted from the user 2a. Since the message attribute information H1a and the message attribute information H1b are first stored synchronously, the condition that the user 2b as the recipient can receive the message at any time is ready.

  When the message processing server S1 confirms that the user 2b has received the message body C1, the message processing server S1 sends the message attribute information processing unit 110 the database area 130a unique to the user 2a in the message attribute information database unit 130 and the user 2b unique. The message attribute information H1a and message attribute information H1b related to the message M1 in the database area 130b are updated in synchronization with information such as the reception date and time related to the reception of the message M1 by the user 2b (a207).

  The user 2a accesses the message processing server S1 again and browses the message attribute information H1a of the message M1 stored in the database area 130a unique to the user 2a, thereby confirming that the message M1 has been received by the user 2b. It can be confirmed (a208, a209).

  When storing or updating the message attribute information H1a and the message attribute information H1b in the message attribute information database unit 130, it is desirable to store them synchronously. Only one of the attribute information H1a or the message attribute information H1b is not stored, but both are stored, or both are not stored and a processing error occurs. Further, when both are stored synchronously, the temporary storage device that temporarily stores the storage processing and the storage processing unit (not shown) are entrusted with the storage processing. The same effect can be obtained when the unit stores or updates the message attribute information H1a and the message attribute information H1b in synchronization.

  In creating and transmitting / receiving a message by the terminal, an administrator who operates and manages the message processing server may supply a user with an editor for creating a message using a storage medium such as a CD-ROM, or the message processing server. You can download an editor for creating messages to the user's terminal, and users can create and send / receive messages using the editor.

  Next, when the user 2a transmits the message M2 to the user 2c having a user account on the message processing server S2 different from the message processing server S1 of the user 2a, the user 2a creates a message M2 for the user 2c on the terminal. Then, the message processing server S1 is accessed based on the user account set specifically for the user 2a, and the message M2 is transmitted to the message processing server S1 (a301).

  The message processing control unit 100 of the message processing server S1 receives the message M2 sent from the terminal of the user 2a, and separates the message M2 into message body C2 and message attribute information H2. The message body C2 is stored in the message body storage area 140a unique to the user 2a of the message body information storage unit 140 by the message body information processing unit 120 in the message processing control unit 100 (a302).

  The message attribute information H2 is stored by the message attribute information processing unit 110 in the message processing control unit 100, the message transmission date and time, whether or not the other party has read, the location where the message body C2 is stored, and the message body C2 is encrypted. Is added as the message attribute information H2a in the database area 130a unique to the user 2a of the message attribute information database unit 130 (a303).

  At the same time as the above operation, the message processing control unit 100 of the message processing server S1 writes the updated message attribute information H2a of the message M2 to the message processing server S2 having the user account of the user 2c who is the transmission partner of the message M2. (A304).

  Upon receipt of the request from the message processing server S1, the message processing server S2 sends a message to the message attribute information processing unit 111 in the message processing control unit 101 and a message to the message attribute information database 131c unique to the user 2c in the message attribute information database unit 131. The message attribute information H2a of M2 is stored as message attribute information H2c (a305), and the request processing completion response is returned to the message processing control unit 100 of the message processing server S1 (a306).

  On the other hand, the user 2c who is the recipient of the message M2 accesses the message processing server S2 based on the user account set specifically for the user 2c (a401), and via the message attribute information processing unit 111 of the message processing server S2, The message attribute information H2c related to the message M2 addressed to the user stored in the message attribute information database 131c unique to the user 2c provided in the message attribute information database 131 is browsed (a402, a403).

  Since the message attribute information H2c stores a reference to the message body C2, the user 2c designates the message attribute information H2c and requests the message processing server S2 to transmit the message body C2 (a404). The message processing server S2 requests the message processing server S1 to transmit the message body C2 stored in the message body information storage unit 140 of the message processing server S1 to the user 2c (a405).

  Upon receiving the request, the message processing server S1 transmits the message body C2 stored in the message body storage area 140a of the user 2a of the message body information storage unit 140 to the user 2c via the message body information processing unit 120. (A406, a407, a408). By this operation, the user 2c can receive the message M2, which is a message from the user 2a.

  As described above, after the message attribute information H2c is first stored in the message attribute information database 131c, the user 2c browses the message attribute information database 131c unique to the user 2c, and thereby receives the message M2 transmitted from the user 2a. Since the message attribute information H2a and the message attribute information H2c are first stored synchronously, the condition that the user 2c as the receiver can receive the message at any time is ready.

  When the message processing server S2 confirms that the user 2c has received the message body C2, the message attribute information processing unit 111 stores the message attribute information database unit 131 in the message attribute information database 131c unique to the user 2c. The message attribute information H2c stores information such as the reception date and time related to the reception of the message M2 by the user 2c (a409), and also stores that the user 2c has received the message attribute information H2a of the user 2a who is the sender. In order to make this happen, the message processing server S1 is requested to perform processing (a410).

  In response to this, the message processing server S1 confirms that the user 2c has received the message body C2 in the attribute information H2a in the database area 130a of the user 2a provided in the message attribute information database unit 130 in the message attribute information processing unit 110. The process is stored (a411), and a process completion response is returned to the message processing server S2 (a412).

  The user 2a accesses the message processing server S1 again and browses the message attribute information H2a of the message M2 stored in the database area 130a unique to the user 2a, thereby confirming that the message M2 has been received by the user 2c. It can be confirmed (a413, a414).

  When storing or updating the message attribute information H2a and the message attribute information H2c in the message attribute information database unit, it is desirable to store them synchronously. However, if any failure occurs in the storage process, the message attributes Only one of the information H2a and the message attribute information H2c is not stored, but both are stored, or neither is stored and a processing error occurs. Further, as described above, when both are stored synchronously, the temporary storage device that temporarily stores the storage processing and the storage processing unit are entrusted to the temporary storage device and the storage processing. The same effect can also be obtained when the unit stores or updates the message attribute information H2a and the message attribute information H2c in synchronization.

  According to the management method described above, the message body, the message attribute information for the sender related to the message, and the message attribute information for the receiver are created from the message sent from the user, and the message is obtained by browsing the message attribute information. It is possible to reliably manage the transmission / reception state.

  And since the message body does not move from the message body information storage unit of the message processing server having the user account of the sender to another message processing server, etc., the message confidentiality is maintained and trouble during the movement There is no loss of messages. Furthermore, by checking the message attribute information, the sender can check whether or not the receiver has read the message that he / she sent, and if so, when the date / time is received. On the subscriber side, the message can be obtained by obtaining the message attribute information addressed to him and requesting the body part of the message defined in the message attribute information, so the message can be obtained from any terminal any number of times. And messages are no longer spread across multiple terminals.

  Information may be distributed between the user's terminal and the message processing server, and between the message processing server and the message processing server by using encrypted communication such as SSL (Secure Socket Layer).

  Next, a case where the user 2a transmits a message to the e-mail user 2d will be described with reference to FIG.

  The user 2a creates a message M3 for the user 2d on the terminal and transmits it to the message processing server S1 (a501). The message processing control unit 100 of the message processing server S1 receives the message M3 sent from the terminal of the user 2a (a502).

  When the message processing server S1 identifies that the destination address of the message M3 is the email user 2d and transfers the message M3 to the email processing server E (a503), the email processing control unit 15 sends the message M3 to the email. The data is sent to the transmission / reception box 16 (a504). Thereafter, an e-mail M3 is sent from the e-mail sending / receiving box 16 to the user 2d according to the setting of the e-mail processing server E (a505).

  A case where the e-mail user 2d transmits a message to the user 2a will be described.

  When the user 2d sends an email M4 to the email sending / receiving box 16 (a601), the email M4 is sent from the email sending / receiving box 16 to the email processing control unit 15 (a602).

  The email processing control unit 15 sends the email M4 to the message processing control unit 100 (a603). The message processing control unit 100 identifies that the destination address of the email M4 is the user 2a, and sends the email M4 to the message. The main body C4 and the message attribute information H4 are separated.

  The message body C4 is stored in the message body storage area 140a unique to the user 2a of the message body information storage unit 140 by the message body information processing unit 120 in the message processing control unit 100 (a604).

  The message attribute information H4 is information such as a location where the message body C4 is stored by the message attribute information processing unit 110 in the message processing control unit 100, and a decryption key when the message body C4 is encrypted and stored. Is stored as message attribute information H4a in the database area 130a unique to the user 2a (a605).

  The user 2a who is the recipient of the e-mail M4 accesses the message processing server S1 (a701), and the user provided in the message attribute information database unit 130 via the message attribute information processing unit 110 of the message processing server S1. The message attribute information H4a stored in the database area 130a unique to 2a is browsed (a702, a703).

  Since the message attribute information H4a stores a reference to the message body C4, the user 2a designates the message attribute information H4a and requests the message processing server S1 to transmit the message body C4 (a704). The message processing server S1 reads the message body C4 stored in the message body storage area 140a unique to the user 2a via the message body information processing unit 120 (a705) and transmits it to the terminal of the user 2a (a706). ). By this operation, the user 2a can receive the electronic mail M4 which is a message from the user 2d.

  As described above, in the email M transmitted from the email user, the message processing control unit 100 creates a mail body that means the content of the email and attribute information of the email. The message body C is stored in the message body information storage unit 140, and the mail attribute information is stored in the message attribute information database unit 130 as message attribute information H. Therefore, the user 2 under the control of the message processing server S is different from the case of receiving a message from another user 2 under the control of the message processing server S, even if it is an e-mail from the e-mail user. The system of the present invention can coexist with the current mainstream e-mail system, and can be managed by any information processing company such as a provider under the control of any system. It is also possible to provide a message transmission / reception service to users in

  Further, as shown in FIG. 11, the message attribute information H does not store all the message attribute information, but is limited information for accessing the message body C (for example, information as shown in FIG. 12A). Information for managing the transmission / reception of the message, such as whether or not the transmission of the message is completed and whether or not the receiver has received the message is management information T (for example, FIG. 12B) (C) may be stored in the message body information storage unit 14 together with the message body C.

  This message attribute information H describes information for accessing the message body such as the sender of the message, the transmission date and time, and link information linked to the message body part, and basically describes information that is not updated. As a result, data mismatch does not occur due to an update processing trouble between the distribution source and the distribution destination. Moreover, the transmission / reception processing load of the message processing server S can be reduced by transmitting / receiving minimum information.

  Further, since the information to be updated (for example, the reception date and time) is described in the user information of the management information T (see FIG. 12C), the update processing is performed in the management information in the message processing server in which the sender has an account. Since the management information T is not distributed, the identity of the information is surely guaranteed. The management information T can be browsed together with the message body C when accessing the message body C based on the message attribute information H, whether or not the recipient of the message has viewed the message, and when is the viewing date and time. Can know.

  In each of the above embodiments, the message processing control unit, the message main body information storage unit, the message attribute information database unit, and the e-mail server are described one by one in the message processing server. A distributed processing apparatus configured may be used, or an apparatus that partially performs distributed processing may be used. Further, the message body information storage unit and the message attribute information database unit are described so as to have a user-specific information area, but each may be a separate storage device and database, or a single storage device and A user-specific area may be distinguished from the database, or information stored in the storage device and the database may be stored with a user-specific identification symbol attached thereto.

  Furthermore, the message sent from the user terminal to the message processing server is separated into a message body and message attribute information that the message processing server means its transmission contents, and each is divided into a message body information storage unit and a message. Although it is described so that it is stored in the attribute information database part, this may be sent separately to the message processing server after the message body and message attribute information are separated at the user terminal, or once the entire message May be stored in the temporary storage device in the message processing server, and then the message attribute information and the message body may be extracted and stored in the message body information storage unit and the message attribute information database unit, or the entire message may be stored in the message. Store in main unit storage unit After allowed, may be stored in the message attribute information database unit extracts only a message attribute information.

  Further, when the message attribute information is separated into attribute information H for accessing the message body and management information T, management information T for managing the message body is attached to the message body portion, and the message body C and the message body C together with the message body information. Although it is described so as to be stored in the main body information storage unit 14, this is separated into the message processing server after performing separation processing on the message main body C, the attribute information H, and the management information T managing the message main body at the user terminal. Or after storing the entire message in a temporary storage device in the message processing server, the message body C, the message attribute information H, and the management information T are extracted and the message body information storage unit It may be stored in the message attribute information database section, or the entire message may be memorized. After storing in the sage main body storage unit, only the message attribute information excluding the management information T may be extracted and stored in the message attribute information database unit, or the management information T may be extracted after the management information T is extracted. The server may be provided with a dedicated storage unit.

  In addition, although it is stated that encrypted communication such as SSL (Secure Socket Layer) is used for information distribution between the message processing server and the message processing server, this need not be encryption at the communication protocol level. Other methods may be used as long as the content being distributed is encrypted in a way that cannot be easily deciphered by a third party.

  In the embodiments in which messages are transmitted and received between individual users, it is described that the number of recipients is singular in any case, but the operation is the same even if there are a plurality of recipients.

  In each of the above embodiments, it is described that a message is transmitted and received between the user terminal and the message processing server via the communication network. This is done by using an input / output device directly connected to the message processing server. Obviously, the same effect can be obtained by inputting and outputting messages on the message processing server.

  In the above-described management method, the case where the message body is stored in the message storage area and the message attribute information related to the message body is distributed to all users to be transmitted has been described. However, the object stored in the message storage area is the message. The present invention is not limited, and a file or application software that the user wants to publish or share may be stored in the message storage area instead of the message body or in addition to the message body.

  This makes it possible to exchange and share file data, so that it is possible to prevent multiple copies and multiple transfers of files that have been a problem in existing systems, without burdening the system. It is easy to update information such as version upgrades of files and application software, and all users always use the same file and application software. Updates can be realized with synchronization.

DESCRIPTION OF SYMBOLS 1 Host computer 2 Terminal 3 Communication network 10 Message processing control part 11 Message attribute information processing part 12 Message main body information processing part 13 Message attribute information database part 14 Message main body information storage part S Message processing server

Claims (13)

A message transmission / reception management method comprising the following requirements for managing message transmission / reception via a communication network:
(B) A message for storing message attribute information related to a message including a user account uniquely set for the user and the message sender, recipient, transmission date and time, whether or not the message has been received, reception date and time, and title (B) When the user sends a message, the message attribute information is created corresponding to the user who sends the message and all the users who receive the message. The created message attribute information is stored in the user-specific message attribute information database. (C) The user can browse the user-specific message attribute information database via the communication network. Unique message attribute information database The message defined in the message attribute information can be received by requesting to receive the message by specifying any message attribute information from the message attribute information stored in the message attribute information database. (E) The user can check the message transmission / reception status defined in the message attribute information by browsing any message attribute information contained in the user-specific message attribute information database. (F) The user is user-specific. By browsing any message attribute information contained in the message attribute information database of, it is possible to check the open status of all recipients of the message for each message received by the user. Whether or not Recipient message includes whether or not it has received, in place of information for managing the sending and receiving messages to the message attribute information, the sender user as the management information with accounts, was applied to the message body portion   The message transmission / reception management method according to claim 1, wherein a message body portion including a transmission content of the message among messages transmitted by the user is stored in a message body storage area.   3. The message transmission / reception management method according to claim 2, wherein the message body storage area is a message body storage area unique to a user who transmits the message.   User authority information that permits reading, writing, deletion, transfer, etc. for the message is given to at least one of the message attribute information and the message body part, and an access request by a user that does not match the user authority information, 4. The message transmission / reception management method according to claim 1, wherein access to the message body part is restricted for an access request other than authorized authority.   The message transmission / reception management method according to claim 2, 3 or 4, wherein at least one of the message body part and the message attribute information is encrypted and stored. A message management system for managing message transmission / reception via a communication network, the message management system having the following requirements:
(A) Each user's user account is uniquely registered in the message processing server, and stores message attribute information including the sender, recipient, date / time of transmission, whether received, date / time, and title A message attribute information database unit for storing a message body information storage unit for storing a message body part including a transmission content of the transmitted message. , From the received message, the message body portion including the message transmission content is stored in the message body information storage unit, and the sender defining the message, the receiver, the transmission date and time, whether or not the reception has been received, the reception date and time, The message attribute information of the title is the same as the user sending the message Each message attribute information created is stored in the message attribute information database specific to the user in the message attribute information database section. (C) The message processing server is accessed through the communication network. (D) The user browses the user-specific message attribute information database, designates any message attribute information, and stores the message main body part. By requesting the message processing server to receive, the message body part defined in the message attribute information can be received. (E) Each user accesses the message processing server to access a message attribute unique to the user. By browsing any message attribute information included in the information database, the message transmission / reception status defined in the attribute information can be confirmed. (F) The user can select any message attribute included in the user-specific message attribute information database. By browsing the information, for each message received by the user, the opening status of all the receiving users of the message can be confirmed. (G) Whether the message has been sent or not, the receiver has received the message. Information for managing transmission / reception of a message including whether or not the message is assigned to the message body portion as management information having an account by the sending user instead of the message attribute information.   The message transmission / reception management system according to claim 6, wherein the message main body information storage unit for storing the message main body information is a message main body information storage unit specific to the user who transmitted the message.   The message processing server includes user authority information that permits reading, writing, deletion, transfer, and the like for the message body part stored in the message body information storage unit in at least one of the message attribute information and the message body part. 8. The message transmission / reception management system according to claim 6 or 7, wherein access to the message body portion is restricted for an access request by a user that does not match the user authority information or an access request other than authorized authority. .   The message processing server encrypts at least one of a message body part and message attribute information, and stores a decryption key in at least one of a user terminal and the message processing server. 8. A message transmission / reception management system according to item 8.   10. The message transmission / reception management system according to claim 6, 7, 8, or 9, wherein the message processing server stores a file or application software in a message body information storage unit in the message body portion.   The message transmission / reception management according to claim 6, 7, 8, 9 or 10, wherein the message processing server is linked with an e-mail server that manages e-mail transmission / reception, and performs e-mail transmission / reception management together with message transmission / reception management. system.   8. The message processing server, when a recipient address of a message received from the user is an email address, converts the message into an email and requests the email server to send an email. , 8, 9, 10 or 11 message transmission / reception management system.   The message processing server includes a message transmission / reception process for processing message transmission / reception or a processing apparatus thereof, a message body information storage process for storing message body information or a processing apparatus thereof, an e-mail transmission / reception process for processing e-mail transmission / reception, or a process thereof The device and message attribute information database processing for processing message attribute information data or at least one processing or processing device of the processing device is configured to be distributed, 6, 7, 8, 9, 10, 11, or 12. A message transmission / reception management system according to 12.

Images