JP4574191B2 - Message distribution system - Google Patents

Description

  The present invention relates to a message distribution system that distributes a character message to, for example, a PHS or a client personal computer (hereinafter simply referred to as a PC).

  Conventionally, as such a message delivery system, a message delivery apparatus that delivers a message to a message receiving side PHS when a message delivery request is detected from the PHS on the message sending side, the PHS on the message receiving side, and the PHS on the message sending side And have.

  Generally, in the PHS on the message receiving side, when a message is received, the message is sequentially stored in the memory, the message stored in the memory is displayed on the display unit, and the stored message includes an unread message. In this case, a technical content is known in which only unread messages are preferentially displayed in a list in the oldest order (for example, see Patent Document 1).

  According to Patent Document 1 described above, when it is determined that there is an unread message in the stored message, only the unread message is preferentially displayed in the oldest order. The situation of forgetting can be surely prevented.

  Further, as a conventional message delivery system, there is a technical content in which a message is delivered to each PC through the Internet, and when the user of each PC accesses the delivery side with respect to the message, it is determined that the message has been read. (For example, refer to Patent Document 2).

According to Patent Document 2 described above, when each user's access to a message is detected, it is determined that the message has already been read. Therefore, the message recipient's message read / Can recognize unread status.
JP 2001-36934 A (see FIG. 1 and abstract) JP 2003-157111 A (see FIG. 1 and abstract)

  However, according to the conventional message distribution system (Patent Document 1), the reception terminal side that has received the message only manages the read / unread status of the received message. For example, the transmission terminal side that has transmitted the message Then, it is impossible to grasp whether the message recipient has read the message, that is, the read / unread status of the message.

  In addition, according to the conventional message delivery system (Patent Document 2), the PC on the sender side can grasp the read / unread status of the message for confirming whether or not the message receiver has received the message. However, since the amount of information related to such a read / unread situation is enormous, there is no problem with a PC or the like having the ability to process a large amount of information. Cannot grasp the same read / unread status.

  The present invention has been made in view of the above points, and an object of the present invention is to easily read / unread a message recipient's message even if the message sender does not go to the PC installation location. It is to provide a message delivery system that can be grasped by the user.

In order to achieve the above object, a message distribution system according to the present invention includes a wireless terminal device having a browsing display function, a wireless base station that accommodates and connects the wireless terminal devices, and a private branch exchange that connects the wireless base stations by wire. And a message distribution system that is wired to the private branch exchange and that allows browsing access from the wireless terminal device through the wireless base station and the private branch exchange, wherein the message distribution device comprises: When a browsing request is detected from the message distribution means for distributing the message to a predetermined wireless terminal device based on the message distribution request and the wireless terminal device that is the message distribution request source, a browsing screen is provided to the wireless terminal device that has made the browsing request A browsing screen providing means, and the message When delivered the, as the transmission success information and receives a response from the wireless terminal device of the message delivery destination stores each message, the message delivery system in the message delivery destinations are browsing access wireless terminal device of a message from When the detail display request is received , storage means for storing each message as message already read information, and the browsing screen providing means, for the wireless terminal device that has made a transmission history display request on the browsing screen, A transmission history screen including transmission success information and read information is provided.

The message delivery system of the invention, the message delivery device, receives the unread instruction request from the wireless terminal device Then, to update the read information messages related to the message of the wireless terminal to the unread information did.

In the message delivery system of the present invention, when the message delivery device delivers a message to the wireless terminal device by the message delivery means, the message has already been read to the wireless terminal device that has received the delivery of the message at a predetermined timing. run the confirmation of telephone call operation, a call response determination means for determining whether to detect the incoming responses to the message read verification call incoming operation, the wireless terminal device in the incoming call response determining means upon detecting an incoming call response to the message read verification call receiving operation from and to be stored as a message read information.

  According to the message delivery system of the present invention configured as described above, when a search request for a read / unread status of a predetermined message is detected on the browsing screen from the PHS, the read of the same message of the PHS related to the message is read. Search the storage means for the unread status, generate a read / unread status screen for PHS based on the read / unread status of the searched message, and display the generated read / unread status screen for PHS Since the PHS that has detected the read / unread status search request is provided on the browsing screen, the PHS user can read the messages of other message recipients, for example, without visiting the PC installation location.・ Unread status can be easily grasped.

  According to the message delivery system of the present invention, when a read instruction request on the browsing screen is detected from the message recipient's PHS, the read / unread status related to the message of the PHS is updated to the storage means as the read state. Therefore, it can be updated to the read state by remote operation on the message receiver side.

  According to the message delivery system of the present invention, when an unread instruction request on the browsing screen is detected from the PHS of the recipient who received the message, the read / unread status related to the message of the PHS is stored in the storage means as an unread state. Since it is updated, it can be updated to an unread state by remote operation on the message receiver side.

  According to the message delivery system of the present invention, the incoming call confirmation operation for the message read confirmation is executed with respect to the PHS of the message recipient at a predetermined timing, and the incoming call response for the incoming call confirmation operation for the message read confirmation is detected from this PHS. If it is determined that the read / unread status of the message of the same PHS is updated to the storage means as the read status, and it is determined not to detect an incoming call response to the call incoming operation of the message read confirmation from the same PHS. Since the read / unread status of the PHS message is updated to the storage means as an unread status, even if the PHS user forgets to update the message read / unread status, the message delivery device side The user is notified of the read confirmation and whether or not to respond to the incoming call operation of the read confirmation. A read-unread status of messages can be updated to the latest situation.

  Hereinafter, a message distribution system showing an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of the entire message distribution system according to the present embodiment.

A message delivery system 1 shown in FIG. 1 includes a PHS 11 as a wireless terminal device having a browsing display function, a PHS base station 12 as a wireless base station that accommodates and connects the PHS 11 and an ISDN connection of the PHS base station 12. A private branch exchange (hereinafter simply referred to as PBX) 13, a terminal adapter (hereinafter simply referred to as TA) 15 that controls the interface between PBX 13 and LAN 14, PC 16 connected to LAN 14, and PHS 11 and / or PC 16. A message distribution device (hereinafter simply referred to as MGW) 17 for distributing messages;

  The PBX 13 includes a base station interface (hereinafter simply referred to as DRIF) 13A that controls an interface with the PHS base station 12, a first IBLCE 13B that controls an interface on the PBX 13 side with the TA 15, and a second IBLCE 13C that controls an interface on the PBX 13 side with the MGW 17 A communication path switch (hereinafter simply referred to as TSW) 13D that forms a communication path between the DRIF 13A, the first IBLCE and 13B and the second IBLCE 13C, and a memory (hereinafter simply referred to as MM) for storing various station data and other information. ) 13E and a central controller (hereinafter simply referred to as CC) 13F for controlling the entire PBX 13.

  Since the PHS 10 has a browsing display function, the number of characters in the message is not limited.

  For example, when transmitting a message from the transmission side PC 16 to the reception side PHS 11, the MGW 17 receives the message from the transmission side PC 16 via the LAN 14 on the browsing, and receives it via the second IBLCE 13 C, TSW 13 D, DRIF 13 A, and the PHS base station 12. The message is delivered to the PHS 11 on the side.

  For example, when delivering a message from the PHS 11 on the transmission side to the PC 16 on the reception side, the MGW 17 receives the message on the browsing from the PHS 11 on the transmission side via the PHS base station 12, the DRIF 13A, the TSW 13D, the first IBLCE 13B, the TA 15, and the LAN 14. The message is delivered to the receiving side PC 16 via the LAN 14.

  For example, when delivering a message from the PHS 11 on the transmission side to the PHS 11 on the reception side, the MGW 17 receives the message on the browsing from the PHS 11 on the transmission side via the PHS base station 12, the DRIF 13A, the TSW 13D, the first IBLCE 13B, the TA 15, and the LAN 14. A message is delivered to the receiving PHS 11 via the second IBLCE 13C, TSW 13D, DRIF 13A, and the PHS base station 12.

  FIG. 2 is a block diagram showing a schematic configuration inside the MGW 17.

  The MGW 17 shown in FIG. 2 is related to an ISND interface 21 that controls the interface with the ISDN wired to the second IBLCE 13C, a LAN interface 22 that connects to the LAN 14 and controls the interface with the LAN 14, and a message from the PHS 11 or the PC 16. For example, a database 23 for managing various information such as reception history information and transmission history information, a RAM 24 for temporarily storing various information related to control of the MGW 17, and a message from the PHS 11 or the PC 16 are distributed to the PHS 11 or the PC 16 in the system. And an MGW control unit 25 for controlling the entire MGW 17.

  The MGW control unit 25 is an ISDN communication control unit 31 that controls communication with the ISDN interface 21, a LAN communication control unit 32 that controls communication with the LAN interface 22, and a message monitor that monitors the message distribution status of the PHS 11 and the PC 16. Unit 33, a database control unit 34 that controls and manages the database 23, a browsing screen generation unit 35 that generates a browsing screen to be provided to the PHS 11 or the PC 16 logged in to the MGW 17, and an internal unit that controls the entire MGW control unit 25 And a control unit 36.

  The LAN communication control unit 32 detects a button operation on the browsing screen of the PC 16 or the PHS 11 and the browsing screen providing unit 32A that provides the browsing screen generated by the browsing screen generation unit 35 to the PHS 11 or the PC 16 via the LAN 14. And a browsing operation detection unit 32B.

  The message monitoring unit 33 detects a browsing read request for requesting reading of a message on the browsing screen through the browsing operation detection unit 32B (button operation of a detail button 143B on the reception history screen 140B described later). A detection unit 33A, a browsing unread request detection unit 33B that detects a browsing unread request (button operation of an unread button 152B on the reception history detail screen 150B described later) that requests unreading of a message on the browsing screen, and an ISDN communication control unit In order to notify the PHS 11 of the message recipient that the message has already been read by voice telephone call through the message 31, the message read through the ISDN communication control unit 31 and the read confirmation transmission unit 33 C that executes a call operation to the PHS 11. PHS1 for incoming phone calls for confirmation A read confirmation response detection unit 33D that detects a response operation of 1 and a message monitoring control unit 33E that controls the message monitoring unit 33.

  When the internal control unit 36 receives a message from the PHS 11 or the PC 16 on the browsing screen through the LAN communication control unit 32, the internal control unit 36 acquires various information of the message.

  When the database control unit 34 acquires various information of the message through the internal control unit 36, the database control unit 34 generates reception history information and transmission history information related to the message, and stores and updates the reception history information and transmission history information in the database 23. When a search request for searching for a read / unread status of a message from the PHS 11 is detected through the database update unit 34A and a browsing operation detection unit 32B described later, the read / unread status of the message corresponding to the search request is stored in the database. 23, and an information search unit 34B that searches from 23.

  When the information retrieval unit 34B retrieves the read / unread status related to the message, the internal control unit 36 generates the read / unread status as a browsing screen for the PHS in the browsing screen generation unit 35. This is provided on the browsing screen to the inquiring PHS 11 through the providing unit 32A.

  Next, the browsing screen provided to the PC 16 or PHS 11 by the browsing screen providing unit 32A of the MGW 17 will be described.

  FIG. 3 is a message creation and transmission screen of the PC 16 and the PHS 11.

  The message creation & transmission screen 110A of the PC 16 shown in FIG. 3A is for delivering a message, for example, a destination input field 111A for inputting a destination number of the PHS 11, a message input field 112A for inputting message contents, and a message delivery failure. A retry number input field 113A for inputting the number of retry times, a retry interval input field 114A for specifying a retry interval time, a send button 115A for transmitting a message input to the message input field 112A, and the like.

  Similarly, the message creation & transmission screen 110B of the PHS 11 shown in FIG. 3B includes a destination input column 111B, a message input column 112B, a retry count input column 113B, a retry interval input column 114B, and a send button 115B. Have.

  For example, the user of the PHS 11 can specify the message transmission destination, for example, the destination number of the PHS 11 in the destination input field 111B of the message creation & transmission screen 110B shown in FIG. 3B, the message content in the message input field 112B, and the number of retries. After inputting the number of retries in the input column 113B and the retry interval time in the retry interval input column 114B, the transmission button 115B is pressed.

  When the LAN communication control unit 32 of the MGW 17 detects the pressing operation of the send button 115B on the message creation & transmission screen 110B through the browsing operation detection unit 32B, the input content of the message creation & transmission screen 110B shown in FIG. Will get.

  FIG. 4 is a transmission history screen of the PC 16 and the PHS 11.

  The transmission history screen 120A of the PC 16 shown in FIG. 4A includes transmission history information 121A for each transmitted message and a detail button 122A for opening the detailed contents of the transmission history information 121A of the message. Is a message transmission date and time 123A, a transmission result 124A indicating whether the message has arrived at the destination, a sender name 125A that has delivered the message, a destination number 126A of the PHS 11 or PC 16 of the message destination, and a message It has a destination name 127A of the transmission destination and a message content 128A.

  The transmission history screen 120B of the PHS 11 shown in FIG. 4B includes transmission history information 121B for each transmitted message and a detail button 122B for opening the detailed contents of the transmission history information 121B of the message. Includes a message transmission date and time 123B, a message transmission result 124B, a destination number 126B of the message transmission destination PHS11 or PC 16, a destination name 127B of the message transmission destination, and a message content 128B.

  Further, when the detail button 122A (122B) on the transmission history screen 120A in FIG. 4A (transmission history screen 120B in FIG. 4B) is operated, the transmission history screen 120A (120B) is shown in FIG. It will move to the transmission history details screen.

  The transmission history detail screen 130A of the PC 16 shown in FIG. 5A is a read / unread status indicating whether the message is read or unread for each recipient in the message in which the detail button 122A on the transmission history screen 120A is pressed. It has transmission history detailed information 132A including 131A. The transmission history detailed information 132A includes, in addition to the read / unread status 131A, a message transmission date / time 133A, a sender name 134A, a transmission result 135A, a message content 136A, a department name 137A, and a recipient name 138A. Yes.

  The transmission history detailed screen 130B of the PHS 11 shown in FIG. 5B has transmission history detailed information 132B including a status mark 131B indicating a message read or unread for each recipient in the message whose detail button 122B is pressed. Yes. The transmission history detailed information 132B includes a message transmission date and time 133B, a transmission result 135B, a department name 137B, a recipient name 138B, and the like in addition to the status mark 131B.

  If the status mark 131B is present, the recipient indicates that the message has not been read. If there is no status mark 131B, the recipient indicates that the message has been read. Therefore, the user of the PHS 11 can recognize the message read / unread status for each recipient related to the message by visually checking the presence / absence of the status mark 131B on the transmission history detail screen 130B shown in FIG. 5B. It can be done.

  FIG. 6 is a reception history screen of the PC 16 or PHS 11.

  The reception history screen 140A of the PC 16 shown in FIG. 6A has a read / unread status check column 141A, reception history information 142A, and an update button 143A for each message. The reception history information 142A includes a message Transmission date / time 144A, message recipient name 145A, message reception result 146A, message content 147A, message sender name 148A, and the like.

  The user of the PC 16 checks the read / unread status check column 141A when the read / unread status of the received message is set to “unread status”, and checks the read / unread status when the read message is set to “read status”. The column 141A is unchecked, and the update button 143A is button-operated.

  Further, the reception history screen 140B of the PHS 11 shown in FIG. 6B has a status mark 141B indicating the read / unread status, reception history information 142B, and a detail button 143B for each message. 142B includes a message transmission date and time 144B, a message reception result 146B, a message content 147B, a message sender name 148B, and the like.

  For example, when the user of the PHS 11 presses the detail button 143B on the reception history screen 140B shown in FIG. 6B, the reception history detail screen 150B shown in FIG. 7 is acquired.

  The reception history detail screen 150B shown in FIG. 7 includes message reception history detail information 151B related to the detail button 143B, and an unread button 152B for setting the read / unread status of the message to “unread state”. .

  When the user of the PHS 11 presses the unread button 152B on the reception history detail screen 150B, the read / unread status of the message is updated to “unread state”. In the reception history screen 140B of FIG. 6B, the read / unread status of the message is normally in an unread state, but when the detail button 143B is operated, the read / unread status of the message is displayed as “ It will be updated to “read state”.

  The message delivery means described in the claims is in the ISDN communication control section 31 and the LAN communication control section 32, the browsing screen providing means is in the browsing screen providing section 32A, the monitoring means is in the message monitoring section 33, and the storage means is in the database 23. The search means corresponds to the information search section 34B, the screen generation means corresponds to the browsing screen generation section 35, and the incoming call response determination means corresponds to the read confirmation transmission section 33C, the read confirmation response detection section 33D, and the message monitoring control section 33E. It is.

  Next, the operation of the message distribution system 1 showing this embodiment will be described. FIG. 8 briefly shows a series of processing operations related to message transmission between the PHS 11 on the message transmission side, message distribution between the PHS 11 on the message reception side and the MGW 17, update of reception history information and transmission history information, and browsing of transmission history. It is the sequence shown.

  The PHS 11 on the transmission side shown in FIG. 8 acquires the message creation & transmission screen 110B shown in FIG. 3B from the browsing screen providing unit 32A of the LAN communication control unit 32 of the MGW 17 by logging in to the MGW 17, and creates the message. & The destination number input field 111B on the transmission screen 110B is input with the destination number of the PHS 11 of the message transmission destination, and the message content is input into the message input field 112B (step S11). At this time, the retry count input field 113B and the retry interval input field 114B are also input.

  When the input to the message creation & transmission screen 110B is completed on the PHS 11 side in step S11 and the button operation of the transmission button 115B is detected through the browsing operation detection unit 32B, the internal control unit 36 of the MGW 17 detects the PHS 11 on the message transmission side. This means that a message transmission request from the side has been detected (step S12).

  When the internal control unit 36 of the MGW 17 detects a message transmission request from the PHS 11 on the message transmission side through the LAN communication control unit 32, the message creation & transmission screen 110B from the transmission side PHS 11 is transmitted through the database update unit 34A of the database control unit 34. The input contents and the like are stored and updated in the database 23 as transmission history information related to the message (step S13).

  When the transmission history information is stored and updated in the database 23, the internal control unit 36 of the MGW 17 transmits a message to the PHS 11 on the message receiving side that is the message transmission destination based on the destination number of the transmission history information (step S14). The MGW 17 transmits a message to the receiving PHS 11 via the second IBLCE 13C, TSW 13D, DRIF 13A, and the PHS base station 12 in order to transmit a message to the receiving PHS 11. When the message destination is the PC 16, the MGW 17 transmits a message to the PC 16 via the LAN.

  When receiving the message delivered from the MGW 17 (Step S15), the receiving-side PHS 11 notifies the MGW 17 of a normal response indicating that the message has been received (Step S16).

  When the internal control unit 36 of the MGW 17 detects a normal response from the receiving side PHS 11, it indicates that the message has successfully arrived in the transmission result column in the transmission history information through the database update unit 34 A of the database control unit 34. The transmission result of "" is stored and updated, and the reception history information of the receiving side PHS11 is also stored and updated (step S17). In step S17, the transmission history information and the reception history information are stored and updated so that the transmission result is “successful” by detecting a normal response from the receiving side PHS11. Even if message transmission is executed based on the retry count and retry interval specified in the above, if a normal response cannot be detected from the PHS 11 on the receiving side, the transmission result is set as “failure” and the transmission history information and the reception history Information is stored and updated.

  According to the series of processing operations from step S11 to step S17, the MGW 17 receives the message on the browsing screen from the PHS 11 on the transmission side, and stores the transmission history information of the transmission side PHS 11 in the database 23. Since the reception history information of the reception side PHS 11 is stored in the database 23 by transmitting the message to the message of the transmission side PHS 11, the reception history information and transmission history information of the message are stored and managed in the database 23 on the MGW 17 side. Can do.

  Next, when the internal control unit 36 of the MGW 17 detects the login from the receiving side PHS 11, the browsing start screen is provided to the receiving side PHS 11 through the browsing screen providing unit 32 A of the LAN communication control unit 32, and the browsing of the LAN communication control unit 32 is performed. A reception history display request is acquired from the receiving side PHS11 on the browsing start screen through the operation detection unit 32B (step S21).

  When acquiring the reception history display request, the internal control unit 36 of the MGW 17 searches the database 23 for reception history information related to the PHS 11 on the receiving side of the reception history display request through the information search unit 34A of the database control unit 34, The search result, that is, reception history information related to the PHS 11 on the receiving side is acquired (step S22).

  Further, when acquiring the reception history information, the internal control unit 36 of the MGW 17 generates a reception history screen 140B for PHS shown in FIG. 6 (b) through the browsing screen generation unit 35 based on the reception history information. The reception history screen 140B is provided to the receiving PHS 11 through the browsing screen providing unit 32A (step S23).

  When the internal control unit 36 of the MGW 17 detects the button operation of the detail button 143B on the reception history screen 140B from the reception side PHS11 through the browsing operation detection unit 32B, the internal control unit 36 acquires a message detail display request related to the detail button 143B. (Step S24).

  When the internal control unit 36 of the MGW 17 obtains the detailed display request for the message related to the detailed button 143B, the database 23 updates the read / unread status of the message to “read state” through the database update unit 34A. The reception history information and transmission history information related to the above message are stored and updated (step S25).

  Furthermore, when the internal control unit 36 of the MGW 17 stores and updates the reception history information and transmission history information related to the message, the detailed information on the message related to the detail button 143B is retrieved from the database 23 through the information search unit 34A of the database control unit 34. Search is performed (step S26).

  The internal control unit 36 of the MGW 17 generates a reception history detail screen 150B for PHS based on the detailed information that is the search result in the browsing screen generation unit 35, and receives the reception history detail screen 150B on the receiving side through the browsing screen provision unit 32A. This is provided to the PHS 11 (step S27). The user of the receiving side PHS 11 can recognize the detailed contents of the received message on the reception history detail screen 150B. When the internal control unit 36 of the MGW 17 detects the button operation of the unread button 152B on the reception history detail screen 150B through the browsing operation detection unit 32B, the reception history information and transmission history information related to the message on the database 23 are detected. The read / unread status of is stored and updated to the “unread status”.

  Therefore, according to the processing operation of step S21 to step S27, the user of the receiving PHS 11 has already read / related to the message by operating the detail button 143B on the reception history screen 140B or the unread button 152B on the reception history detail screen 150B. The unread status can be freely updated on the database 23.

  Next, when detecting the login of the transmission side PHS 11, the internal control unit 36 of the MGW 17 provides a browsing start screen to the transmission side PHS 11 through the browsing screen providing unit 32 A of the LAN communication control unit 32, and browsing operation of the LAN communication control unit 32. A transmission history display request is acquired from the transmission-side PHS 11 on the browsing start screen through the detection unit 32B (step S31).

  When acquiring the transmission history display request, the internal control unit 36 of the MGW 17 searches the transmission history information related to the PHS 11 on the transmission side of the transmission history display request from the database 23 through the information search unit 34A of the database control unit 34. A search result, that is, transmission history information related to the PHS 11 on the transmission side is acquired (step S32).

  When acquiring the transmission history information, the internal control unit 36 of the MGW 17 generates a transmission history screen 120B for PHS shown in FIG. 4B through the browsing screen generation unit 35 based on the transmission history information. The screen 120B is provided to the transmission-side PHS 11 through the browsing screen providing unit 32A (step S33).

  When the internal control unit 36 of the MGW 17 detects the button operation of the detail button 122B on the transmission history screen 120B from the transmission side PHS11 through the browsing operation detection unit 32B, the internal control unit 36 acquires a message detail display request related to the detail button 122B. (Step S34).

  When the internal control unit 36 of the MGW 17 obtains the message detail display request related to the detail button 122B, the internal control unit 36 searches the database 23 for the detailed information of the message related to the detail button 122B through the information search unit 34A of the database control unit 34. (Step S35).

  When the internal control unit 36 of the MGW 17 retrieves the detailed information of the message related to the detail button 122B, the browsing screen generation unit 35 generates the transmission history detail screen 130B for PHS based on the detailed information, and through the browsing screen providing unit 32A. A transmission history detail screen 130B is provided to the PHS 11 on the transmission side (step S36).

  The user on the PHS 11 side can easily recognize whether or not the message transmission destination user (message recipient) has read the message by viewing the status mark 131B on the transmission history detail screen 130B.

  According to the processing operations in steps S31 to S36, the PHS 11 on the message transmission side accesses the MGW 17 on the browsing screen, so that the PHS 11 on the transmission side can recognize the read / unread status of the message recipient.

  In the processing operations of steps S21 to S27, the PHS 11 on the receiving side voluntarily accesses the MGW 17 on the browsing screen, thereby updating the read / unread status of the message to the database 23, and the unread / The update of the read status is left to the user of the receiving side PHS 11, but if the user of the receiving side PHS 11 does not voluntarily update the read / unread status of the message, the latest read / unread status is secured. Can not do it.

  Therefore, in this embodiment, even if the user of the receiving PHS 11 is reading a received message, the latest read / unread status is read even if the registration update of the message read / unread status is forgotten. In order to update, the following processing operation is executed. FIG. 9 is a flowchart showing the processing operation of the internal control unit 36 in the MGW 17 related to the read / unread status update process.

  The read / unread status update processing shown in FIG. 9 is an incoming call response from the MGW 17 to the receiving side PHS 11 even when there is no update operation of the message read / unread status from the message receiver on the browsing. This is a process of updating the message read / unread status to the message recipient.

  If the internal control unit 36 of the MGW 17 shown in FIG. 9 determines that there is no operation for registering the read / unread status related to the message from the stored contents of the database 23 even if a predetermined time has passed since the message transmission, the message The destination number of the receiver's PHS 11, the predetermined number of retries, and the predetermined retry interval are acquired (step S41).

  The internal control unit 36 determines whether the number of incoming calls has reached a predetermined number of retries (step S42).

  The internal control unit 36 performs a transmission operation to the PHS 11 so as to notify the PHS 11 of the message read confirmation through the read confirmation transmission unit 33C of the message monitoring unit 33 (step S43).

  The internal control unit 36 determines whether or not an incoming call response to the incoming call of the PHS 11 is detected through the read confirmation response detection unit 33D when the incoming call for message read confirmation to the PHS 11 is transmitted (step S44). .

  If the incoming call response is detected through the read confirmation response detection unit 33D, the internal control unit 36 determines that the message recipient has confirmed the read of the message, and disconnects communication with the PHS 11 ( In step S45), the reception history information and transmission history information stored in the database 23 are stored and updated with the read / unread status of the message as "read status" (step S46), and this processing operation is terminated.

  The internal control unit 36 disconnects the communication to the PHS 11 unless it detects the PHS 11 incoming call response in step S44 (step S47), and after the next predetermined retry interval time has elapsed, By incrementing the number by +1, the process proceeds to step S42.

  If the number of incoming calls reaches the predetermined number of retries in step S42, the internal control unit 36 determines that the message recipient has not confirmed the read of the message, and uses the database update unit 34A to This processing operation is completed by storing and updating the reception history information and transmission history information stored in the database 23 with the read / unread status of the message as “unread state” (step S48).

  According to the read / unread status update processing shown in FIG. 9, even if the message recipient forgets the registration operation of the message read / unread status, the message recipient on the MGW 17 side after a predetermined time has elapsed after the message transmission. The PHS11 of the message is used to confirm that the message has already been read, and the message recipient simply performs a response operation to the call, and the read / unread status of the message is set to the “read status” database. 23 can automatically update transmission history information and reception history information.

  Further, when the MGW 17 performs a call incoming confirmation for the message read to the message recipient's PHS 11 and the message recipient does not respond to the call incoming, the read / unread status of the message is indicated as “ The transmission history information and the reception history information on the database 23 can be automatically updated as “unread state”.

  According to the present embodiment, when the button operation of the detail button 122B related to a predetermined message is detected on the transmission history screen 120B from the PHS 11, the detailed information of the message is retrieved from the database 23 and read based on the detailed information. Since the transmission history detail screen 130B including the unread status is generated and this transmission history detail screen 130B is provided to the PHS 11, the user of the PHS 11 can visually check the status mark 131B on the transmission history detail screen 130B. For example, it is possible to recognize the read / unread status of the recipient who has received the message without going to the installation location of the PC 16.

  According to the present embodiment, when the MGW 17 is accessed from the PHS 11 of the recipient who has received the message and the button operation of the detail button 143B on the reception history screen 140B being logged in is detected, the read / Since the reception history information and transmission history information on the database 23 are stored and updated with the unread status set to “read status”, the read / unread status of the messages on the database 23 can be changed by browsing operation on the message receiver side. Can be updated to read state.

  According to the present embodiment, when the MGW 17 is accessed from the PHS 11 of the recipient who received the message and the button operation of the unread button 152B on the reception history detail screen 150B being logged in is detected, the already read related to the message of the PHS 11 -Since the reception history information and transmission history information on the database 23 are stored and updated with the unread status set to "unread status", the read / unread status of messages on the database 23 is unread by browsing operations on the message recipient side. Can be updated to state.

  According to the present embodiment, even if a predetermined time after the message transmission has passed, the MGW 17 sends a message to the PHS 11 even if the message recipient has not performed an operation for updating the read / unread status of the message. When the incoming call for read confirmation is executed and the incoming call response of the PHS 11 is detected, the read / unread status of the message is set to “read status” and the reception history information and transmission history information on the database 23 are stored and updated. If no incoming call response is detected, the read / unread status of the message is set to “unread”, and the reception history information and the transmission history information are stored and updated. Even if you forget to update the status, the MGW 17 notifies the PHS 11 user of the read confirmation and responds to the incoming call operation of the read confirmation. Rukashi only or not, it is possible to update the read-unread status of messages on the database 23 to the latest situation.

  In the above embodiment, when the MGW 17 transmits a message to the receiving side PHS 11, if the message transmission retry count exceeds the specified retry count, the transmission result of the transmission history information is stored in the database 23 as “failure”. However, at every predetermined timing, a message whose transmission result of the transmission history information is “failed” is searched, a telephone inquiry for confirming the communication state with the receiving side PHS 11 of the same transmission failure is executed, and the receiving side The user of the PHS 11 may be prompted to browse the received message that has not been transmitted to the MGW 17, and the operation in this case will be described.

  FIG. 10 is a flowchart showing the processing operation of the internal control unit 36 of the MGW 17 related to the communication status confirmation processing.

  The communication status confirmation process shown in FIG. 10 searches the transmission history information for a message indicating that the MGW 17 side cannot send a message to the receiving side PHS11 and the transmission result is “failure”, and makes a call to the receiving side PHS11. When the user of the receiving side PHS 11 responds to an incoming call, the MGW 17 recognizes that the communication state of the receiving side PHS 11 is normal, that is, the receiving side PHS 11 is in a situation of acquiring a received message. .

  In FIG. 10, the internal control unit 36 of the MGW 17 uses the information search unit 34B to transmit detailed information related to a message whose transmission result is “failed” from the transmission history information stored in the database 23, such as a destination, a predetermined number of retries, and a predetermined retry interval. Is acquired (step S51).

  The internal control unit 36 determines whether or not the current number of telephone calls to the destination has reached a predetermined number of retries (step S52).

  The internal control unit 36 makes a call to the destination PHS 11 through the ISDN communication control unit 31 (step S53), and determines whether an incoming call response from the PHS 11 is detected for the incoming call (step S53). S54).

  If the incoming control of the PHS 11 is not detected, the internal control unit 36 disconnects the telephone call to the PHS 11 (step S55), and increments the current number of telephone calls after the predetermined retry interval time by +1. Control goes to step S52.

  If the incoming control of the PHS 11 is detected in step S54, the internal control unit 36 determines that the communication state of the PHS 11 is normal, disconnects the communication with the PHS 11 (step S56), and the PHS 11 Is stored (step S57), and this processing operation is terminated. The user of the PHS 11 can recognize that an unreceived message remains in the MGW 17 by visually checking the caller number on the MGW 17 side in response to an incoming call from the MGW 17. Therefore, the user of the PHS 11 can acquire an unreceived message on the browsing by executing the processing operation in steps S21 to S27 in FIG.

  Next, if the current number of outgoing calls reaches the predetermined number of retries in step S52, the internal control unit 36 stores a communication log that communication with the PHS 11 has failed (step S58). This processing operation ends.

  According to the communication status confirmation process shown in FIG. 10, the MGW 17 side searches the transmission history information for a message that the message cannot be transmitted to the receiving side PHS 11 and the transmission result is “failure”, and makes a call to the receiving side PHS 11. When the user of the receiving side PHS11 performs an incoming call response to the telephone call, the MGW 17 side recognizes that the communication state of the receiving side PHS11 is normal, that is, the receiving side PHS11 is in a situation of acquiring the received message, By leaving the sender number of the MGW 17 in the receiving side PHS 11, it is possible to recognize that an unreceived message remains on the MGW 17 side for the user of the receiving side PHS 11.

  According to the message distribution system of the present invention, a message is transmitted from a transmission side PHS via a message distribution device to a reception side PHS or a PC, and browsing access to the message distribution device is performed from the transmission side PHS. The PHS read / unread status screen including the message read / unread status of the message recipient is provided to the sender PHS so that the message of the message receiver can be read from the user of the sender PHS. Since the unread situation can be easily recognized, it is useful for a system that distributes a text message to a PHS carried by an employee via a LAN in a company, for example.

It is a block diagram which shows schematic structure of the whole message delivery system which shows embodiment of this invention. It is a block diagram which shows the schematic structure inside MGW which is the principal part of this Embodiment. It is explanatory drawing which shows the message preparation & transmission screen of PC and PHS in connection with this Embodiment. a) PC message creation & transmission screen b) PHS message creation & transmission screen It is explanatory drawing which shows the transmission log | history screen of PC and PHS in connection with this Embodiment. a) PC transmission history screen b) PHS transmission history screen It is explanatory drawing which shows the transmission log detail screen of PC and PHS in connection with this Embodiment. a) PC transmission history details screen b) PHS transmission history details screen It is explanatory drawing which shows the reception log | history screen of PC and PHS in connection with this Embodiment. a) PC reception history screen b) PHS reception history screen It is explanatory drawing which shows the reception log detail screen of PHS in connection with this Embodiment. It is a sequence which shows briefly the whole process operation | movement of the transmission side PHS, MGW, and reception side PHS in connection with this Embodiment. It is a flowchart which shows the processing operation | movement of MGW regarding the read / unread condition update process of this Embodiment. It is a flowchart which shows the processing operation | movement of MGW in connection with the transmission history information update process of other embodiment.

Explanation of symbols

1 Message distribution system 11 PHS
12 PHS base station 13 PBX (private branch exchange)
14 LAN
17 MGW (Message Distribution Device)
23 Database (storage means)
31 ISDN communication control unit (message delivery means)
32 LAN communication control unit (message delivery means)
32A Browsing screen providing unit (browsing screen providing means)
33 Message monitoring unit (monitoring means)
33C Read confirmation transmission part (incoming response determination means)
33D Read confirmation response detector (incoming response determination means)
33E Message monitoring controller (incoming response determination means)
34B Information Search Unit (Search means)
35 Browsing screen generator (screen generator)

Claims (3)

A wireless terminal device having a browsing display function, a wireless base station that wirelessly connects and connects the wireless terminal device, a private branch exchange that connects the wireless base station by wire, a wired connection to the private branch exchange, and the wireless base station And a message delivery system comprising a message delivery device that enables browsing access from the wireless terminal device through a private branch exchange,
The message delivery device
Message delivery means for delivering a message to a predetermined wireless terminal device based on the message delivery request;
When a browsing request is detected from the wireless terminal device that is the message delivery request source, a browsing screen providing means for providing a browsing screen to the wireless terminal device that has made the browsing request;
When the message is delivered, when a response is received from the message delivery destination wireless terminal device, the message is stored as transmission success information for each message, and from the message delivery destination wireless terminal device having browsing access to the message delivery device Upon receiving a detailed display request message, comprising storage means for storing each message as a message read information, and
The browsing screen providing means provides a transmission history screen including transmission success information and already-read information to a wireless terminal device that has made a transmission history display request on the browsing screen.   2. The message delivery according to claim 1, wherein when the message delivery device receives an unread instruction request from the wireless terminal device, the message delivery device updates the already-read information of the message related to the message of the wireless terminal device to unread information. system. When the message is delivered to the wireless terminal device by the message delivery means, the message delivery device performs a call incoming operation for confirming that the message has been read to the wireless terminal device that has received the delivery of the message at a predetermined timing. , Having an incoming call response determination means for determining whether an incoming call response for the incoming call operation of the same message read confirmation has been detected,
3. The message delivery system according to claim 1, wherein when an incoming call response to a call incoming operation for confirming a message read from the wireless terminal device is detected by the incoming call response judging means, the message read information is stored. .

Images