JP2009088703A - Communication control apparatus, communication control method and communication control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a presence (status) update service in accordance with the complicated condition of a user. <P>SOLUTION: A communication control apparatus installed on a network distributes the status information of a user terminal to the terminal of a member registered for each user terminal. The communication control apparatus is provided with: an event detecting section for detecting a changed event conforming to the changing condition of the status information; a status information changing section for changing the status information to status information corresponding to the changed event when the event detecting section has detected the changed event; and a transmitting section for transmitting the status information changed by the status information changing section to the user terminal and the member terminal. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a communication control device, a communication control method, and a communication control program. In particular, in the communication control device that distributes user status information to the communication terminals of members registered for each user, the present invention can detect an event that changes the user status and automatically change the status of the user. The present invention relates to a communication control device, a communication control method, and a communication control program.

In a mobile terminal such as a mobile phone, a presence service is provided that displays its presence or status on a registered user's communication terminal. For example, Patent Document 1 discloses an automatic presence update system for the purpose of reducing the burden on the user when updating presence. In the presence automatic update system, the low-power transmission / reception unit of the mobile phone performs close-to-proximity communication with the non-contact type communication device installed at each location. And the installation location information is acquired from a non-contact type communication apparatus. The mobile phone compares the presence information registered in the presence management table with the received installation location information, and generates and transmits presence information based on the matched presence information.
JP 2006-140544 A

  However, as described in Patent Document 1, it is difficult to satisfy the needs of various users simply by acquiring position information and automatically updating presence information. In order to provide an update service of presence (hereinafter also referred to as “status” in the present specification) according to a complicated user situation, it is desirable to provide a service system that can flexibly cope with the user situation. It is.

  In order to solve the above-described problem, in the first aspect of the present invention, there is provided a communication control device provided in a network for distributing status information of a user terminal to member terminals of members registered for each user terminal. An event detection unit that detects a change event that matches the status information change condition, and a status information change unit that changes status information to status information corresponding to the change event when the event detection unit detects a change event; There is provided a communication control device including a transmission unit that transmits status information changed by a status information change unit to a user terminal and a member terminal.

  It should be noted that the above summary of the invention does not enumerate all the necessary features of the present invention. In addition, a sub-combination of these feature groups can also be an invention.

  Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. In addition, not all the combinations of features described in the embodiments are essential for the solving means of the invention.

  FIG. 1 shows an example of the entire system 10 including the communication control server 300 of the present embodiment. The overall system 10 includes a communication terminal 100, a communication terminal 200, a communication control server 300, an application server 400, a network 500, a personal computer system 600, and a ticket gate 700. In the figure, two communication terminals, the communication terminal 100 and the communication terminal 200, are illustrated, but a larger number of communication terminals may be connected to the network 500.

  The communication terminal 100 and the communication terminal 200 have the same configuration, and both communication terminals are equivalent in function. Therefore, in the following description, the communication terminal 100 and the communication terminal 200 are not particularly distinguished and described. However, when the communication terminal 100 and the communication terminal 200 are registered with each other, the status information transmitted by the communication terminal 100 is displayed on the communication terminal 200, and the status information transmitted by the communication terminal 200 is displayed on the communication terminal 100. To do. It goes without saying that the communication terminal 100 and the communication terminal 200 can simultaneously distribute status information to other equivalent communication terminals.

  The communication terminal 100 uses the communication control server 300 provided in the network 500 to distribute its own status information to the registered member communication terminal, for example, the communication terminal 200. That is, the communication terminal 100 transmits its own status information to the communication control server 300 in order to distribute its own status information to the communication terminal 200 which is the registered member communication terminal.

  The communication terminal 100 can execute short-range communication such as infrared communication, Bluetooth communication, or IC card reading communication with the personal computer system 600, for example. The communication terminal 100 can achieve data linkage with, for example, schedule software that operates in the personal computer system 600 through communication with the personal computer system 600.

  The communication terminal 200 has the same function as the communication terminal 100. Therefore, as with the communication terminal 100, the status information is distributed to the registered member communication terminal, for example, the communication terminal 100, using the communication control server 300 provided in the network 500.

  The communication terminal 200 can execute short-range communication such as infrared communication, Bluetooth communication, or IC card reading communication with the ticket gate 700, for example. The communication terminal 200 can receive services such as train or aircraft ticket gates, fare payment, etc., through communication with the ticket gate 700. The ticket gate 700 may be an entrance ticket gate for other movie theaters, theaters, sports facilities, and the like, and can be applied to any service based on the premise of ticket inspection.

  The communication control server 300 distributes, for example, status information of the communication terminal 100, which is an example of a user terminal, to, for example, the communication terminal 200, which is an example of a member terminal of a member registered for each user terminal. The communication control server 300 is provided in the network 500. Further, the communication control server 300 detects a change event that changes the status information of the user of the communication terminal 100 or the communication terminal 200, and automatically changes the status information according to the detected change event.

  The application server 400 is a server that provides a service application via the network 500, and may be a schedule server that provides a schedule service, for example. In this case, the personal computer system 600 can function as a client for the schedule service. The application server 400 may be a service server that provides a service with use of an application program or a specific function used in a user terminal such as the communication terminal 100 or the communication terminal 200, for example. For example, a chat server when a chat application is used in the communication terminal 100 can be exemplified.

  The application server 400 may be a service server that detects use of a user terminal such as the communication terminal 100. For example, when a user passes the ticket gate 700 using the communication terminal 200 or the like, a ticket gate server that can detect use of the user's communication terminal 200 or the like (that is, ticket inspection) can be exemplified.

  The network 500 may be a communication path that connects the communication terminal 100, the communication terminal 200, the communication control server 300, the application server 400, the personal computer system 600, and the ticket gate 700. An example of the network 500 is a communication network to which IP (Internet Protocol) is applied.

  The personal computer system 600 can achieve data linkage with the communication terminal 100, for example. Alternatively, the personal computer system 600 functions as a client of a schedule service server that runs on the application server 400.

  The ticket checker 700 performs short-range communication with the communication terminal 200, for example, and acquires ticket information recorded in the communication terminal 200. If the ticket information is valid, passage can be permitted, and if the ticket information is invalid, passage can be prevented. The ticket gate 700 can communicate with the application server 400 via the network 500, and can notify the application server 400 of ticket information acquired from the communication terminal 200, for example.

  FIG. 2 shows an example of functional blocks of the communication control server 300. The communication control server 300 includes an event detection unit 302, a status information change unit 304, a status information transmission unit 306, a data reception unit 308, a schedule storage unit 310, a timer unit 312, a user database 314, a status information reception unit 322, and a control unit 324. Is provided. The user database 314 has user information 316 including a member list 318 and an event list 320.

  The event detection unit 302 detects a change event that matches the change condition of the status information. For example, the event detection unit 302 detects that the current date and time has reached the date and time included in the schedule data stored in the schedule storage unit 310 as a change event. That is, the event detection unit 302 detects that the notification information is received from the timer unit 312 as a change event. Alternatively, the data receiving unit 308 detects that the notification information is received from the data receiving unit 308 as a change event. For example, the event detection unit 302 receives from the timer unit 312 as notification information that the current date and time has reached the date and time scheduled in the schedule data stored in the schedule storage unit 310 based on the notification information notified by the data reception unit 308. The notification information is detected as a change event.

  When the event detection unit 302 detects a change event, the status information change unit 304 changes the status information to status information corresponding to the change event. For example, the status information changing unit 304 changes the status information according to the schedule data stored in the schedule storage unit 310. Alternatively, the status information changing unit 304 changes according to the notification information from the timer unit 312 or the data receiving unit 308. The status information changing unit 304 can change the status information when the interlocking data included in the data received in association with the change event or the interlocking data recorded in association with the change event is true. The status information changing unit 304 can prevent the status information from being changed when the interlocking data is false.

  The status information transmission unit 306 transmits the status information changed by the status information change unit 304 to the communication terminal 100 that is an example of a user terminal and the communication terminal 200 that is an example of a member terminal. The data receiving unit 308 receives schedule data or notification information related to schedule data. Further, the data receiving unit 308 sends notification information indicating that service provision to the communication terminal 100 or the like is started or ended from the application server 400 that provides the service in accordance with the use of the application program or the specific function used in the communication terminal 100 or the like. Receive. Further, the data receiving unit 308 receives notification information indicating that the communication terminal 200 or the like has been used from the application server 400 that detects use of the communication terminal 200 or the like. The communication terminal 100 and the like, the communication terminal 200 and the like are examples of user terminals, and the application server 400 is an example of a service server.

  The schedule storage unit 310 stores schedule data. The schedule data includes schedule item data for each schedule item. The schedule item data includes a label that is a schedule item name, a start date and time, and an end date and time, and includes change status information that is changed when the schedule item is detected as a change event. The change status information includes, for example, a telephone response status, a mail response status, and a PoC response status. The schedule item data further includes comments and linkage data.

  The timer unit 312 counts the current date and time. In addition, the timer unit 312 acquires schedule data from the schedule storage unit 310 and determines whether or not the current date matches the start date and time or end date and time of the schedule recorded in the schedule data. If the start date / time or end date / time of the schedule matches the current date / time, the timer unit 312 notifies the event detection unit 302 that the current date / time has reached the start date / time or end date / time of the schedule.

  User information 316 is stored in the user database 314. The user information 316 includes a member list 318 and an event list 320. The user database 314 can send back user information 316 in accordance with an access request from the status information changing unit 304 or the control unit 324. The member list 318 records identification information for identifying member communication terminals registered for each user.

  The event list 320 includes change status information that is referred to when the status information change unit 304 changes the current status information. The change status information includes, for example, a status (text), a status (pictogram), a telephone response status, a mail response status, a PoC response status, a comment, and interlocking data. The state (text) expresses the current state of the user such as mood by text data, and the mood can be transmitted to the member by text data such as characters and symbols. The state (pictogram) represents the current state of the user, such as the mood, in pictograms, and can convey the mood etc. to the members by pictograms.

  Each of the telephone response status, the mail response status, and the PoC response status indicates whether or not a telephone, mail and PoC response can be made, and informs the member whether or not a telephone response can be made. it can. The comment is an expression method that can be input beyond the limit number of characters of the state (text), and can convey more detailed feelings and situations to the members. The linkage data is data that specifies whether or not the current status information is changed to the changed status information when the change event is detected, and either true or false is recorded. For example, status information is changed when true, and status information is not changed when false. Note that “ON” may be expressed when the interlocking data is true, and “OFF” may be expressed when it is false.

  Further, the event list 320 can hold the usage state of the communication terminal 200 or the like. The usage state can be complementarily changed every time the communication terminal 200 is used through the ticket gate 700 or the like. That is, when the communication terminal 200 or the like is used in the non-use state, the use state is turned on, and when the communication terminal 200 or the like is used next, the use state is turned off (becomes a non-use state).

  The status information receiving unit 322 receives status information from the communication terminal 100, the communication terminal 200, and the like. The received status information is transmitted to the control unit 324, and the control unit 324 controls to distribute the received status information to an appropriate communication terminal. Here, the appropriate communication terminal is a communication terminal of a member registered by the user related to the received status information, and the control unit 324 refers to the member list 318 of the user database 314 and selects an appropriate communication terminal. Determine.

  FIG. 3 shows an example of the overall flow of the communication method in the communication control server 300. In the process of automatically changing the status information for each user, the communication control server 300 executes the event detection process (S800) and executes the status information change process (S900). Then, the changed status information is transmitted (S1002).

  FIG. 4 shows an example of the flow of event detection processing. In the event detection process (S800), first, it is determined whether or not notification information has been received from the timer unit 312 (S802). If it is determined that the notification information has been received, the user's schedule start event or schedule end event is set according to the notification information (S804). If it is determined in step S802 that notification information has not been received, it is further determined whether notification information has been received from the data receiving unit 308 (S806).

  If it is determined that the notification information has been received, a user schedule start event, a schedule end event, a service provision start event, a service provision end event, or a terminal use event is set according to the notification information (S808). After step S804 and step S808, the process returns to the event detection process calling source program (S810). If it is determined in step S806 that notification information has not been received, the process returns to step S802 and the event detection process is repeated. It should be noted that the order of the determination step of step S802 to step S808 and the subsequent change event setting step can be arbitrarily changed.

  FIG. 5 shows a processing flow example in the timer unit 312. In the timer unit process (S812), first, schedule data is acquired from the schedule storage unit 310 (S814). It is determined whether or not the current date and time match the start date and time of the schedule included in the acquired schedule data (S816). If it is determined that they match, notification information including schedule information related to the start is notified to the event detection unit 302 (S818). And it returns to step S814 and continues a timer part process.

  If it is determined in step S816 that they do not match, it is further determined whether or not the current date and time match the end date and time of the schedule included in the schedule data (S820). If it is determined that they match, the event detection unit 302 is notified of notification information including schedule information related to the end (S822). And it returns to step S814 and continues a timer part process. If it is determined in step S820 that they do not match, the process returns to step S814 to continue the timer process.

  FIG. 6 shows an example of a processing flow in the data receiving unit 308. In the data receiving unit process (S824), first, it is determined whether data is received from the network 500 (S826). Step S826 is repeated until data is received, and data is awaited. When the data is received, the user is specified from the user information included in the received data (S828). Next, it is determined whether the received data is schedule data (S830).

  If it is determined in step S830 that the data is schedule data, the received data is stored in the schedule storage unit 310 as the specified user's schedule data (S832). If it is determined in step S830 that it is not schedule data, notification information including the identified user and received data is notified to the event detection unit 302 (S834). After step S832 and step S834, the process returns to step S826 and the processing of the data reception unit 308 is continued.

  FIG. 7 shows a flow example of processing for changing status information in the case of a schedule start event. The status information change process (S910) in the case of a schedule start event first matches the schedule item included in the notification information notified from the timer unit 312 or the data receiving unit 308 with reference to the event list 320 of the user database 314. The record to be extracted is extracted (S912). It is determined whether or not the record extraction is successful (S914). If the extraction is successful, it is further determined whether or not the linked data of the extracted record is true (S916). If the extraction has failed, the process returns to step S800 in FIG. 3 to repeat the event detection process.

  If it is determined in step S916 that the interlocking data is true, the status (text), status (pictogram), response status, and comment of the status information are extracted, and the status (text), status (pictogram), and response of the extracted record are extracted. The status and comment are changed (S918). Then, the process returns to the caller program for the status information change process (S919). If it is determined in step S916 that the interlocking data is false, the process returns to step S800 in FIG. 3 to repeat the event detection process.

  FIG. 8 shows a flow example of processing for changing status information in the case of a schedule end event. In the status information change process (S920) in the case of the schedule end event, it is determined whether or not the corresponding schedule has been started (S922). If the schedule has not been started, the process returns to step S800 in FIG. 3 to repeat the event detection process.

  If the corresponding schedule is started in step S922, the status information status (text), status (pictogram), response status, and comment are changed to the default status (text), status (pictogram), response status, and comment. (S924). Then, the process returns to the calling source program for the status information change process (S926). Note that the default state (text) or the like may be predetermined. Or you may return to the state (text) etc. before the start of the schedule item event which concerns on the said end.

  FIG. 9 shows a flow example of processing for changing status information in the case of a service provision start event. The status information change process (S930) in the case of the service provision start event refers to the event list 320 of the user database 314 and extracts a record that matches the provision service included in the notification information notified from the data reception unit 308. (S932). It is determined whether or not the record has been successfully extracted (S934). If it is determined that the record has been successfully extracted, it is further determined whether or not the linked data of the extracted record is true (S936). If the extraction has failed, the process returns to step S800 in FIG. 3 to repeat the event detection process.

  If it is determined in step S936 that the interlocking data is true, the status (text), status (pictogram), response status, and comment of the status information are extracted, and the status (text), status (pictogram), and response of the extracted record are extracted. The status and comment are changed (S938). Then, the process returns to the caller program for the status information change process (S939). If it is determined in step S936 that the interlocking data is false, the process returns to step S800 in FIG. 3, and the process is repeated from the event detection process.

  FIG. 10 shows a flow example of processing for changing status information in the case of a service provision end event. In the status information change process (S940) in the case of the service provision end event, it is determined whether the provision of the corresponding service is started (S942). If the corresponding service has not been started, the process returns to step S800 in FIG. 3 and is repeated from the event detection process.

  If it is determined in step S942 that the corresponding service has been started, the status information status (text), status (pictogram), response status, and comment, default status (text), status (pictogram), response The status and comment are changed (S944). Then, the process returns to the calling source program for the status information change process (S946). Note that the default state (text) or the like may be predetermined. Or you may return to the state (text) etc. before the start of the schedule item event which concerns on the said end.

  FIG. 11 shows an example of a flow of processing for changing status information in the case of a terminal use event. The status information change process (S950) in the case of the terminal use event refers to the event list 320 of the user database 314 and extracts a record that matches the terminal use device included in the notification information notified from the data receiving unit 308. (S952). It is determined whether or not the record has been successfully extracted (S954). If it is determined that the extraction has been successful, it is further determined whether or not the linked data of the extracted record is true (S956). If the extraction has failed, the process returns to step S800 in FIG. 3 to repeat the event detection process.

  If it is determined in step S956 that the interlocking data is true, it is further determined whether the usage status data of the extracted record is true (S958). If it is determined in step S956 that the interlocking data is false, the process returns to step S800 in FIG. 3 to repeat the event detection process.

  If it is determined in step S958 that the use state data is false, that is, it is not in the use state, it can be determined that service use is newly started. Therefore, the status information status (text), status (pictogram), response status, and comment are changed to the extracted record status (text), status (pictogram), response status, and comment (S960). Then, the usage status data of the corresponding record is set to true (in-use status) (S962).

  If it is determined in step S958 that the use state data is true, that is, the use state is in use, it can be determined that the use of the service is finished. Therefore, the status information status (text), status (pictogram), response status, and comment are changed to the default status (text), status (pictogram), response status, and comment (S964). Then, the usage status data of the corresponding record is set to false (S966). After step S962 and step S966, the process returns to the caller program for the status information change process (S968).

  FIG. 12 shows an example of schedule data stored in the schedule storage unit 310. The schedule data includes schedule item data, and the schedule item data may include a label, a start date / time, an end date / time, a telephone response status, a mail response status, a PoC response status, a comment, and interlocking data. For example, when schedule item data with the label “in-house meeting” is notified as schedule item data related to the schedule start event, the linked data is “ON”, that is, true, and the status information status (text) is “in-house meeting”. Can be changed.

  In addition, each of the status information telephone response status, mail response status, PoC response status, and comment is each data of the corresponding schedule item data, that is, “response NG”, “reply later”, “participation NG”, “project” It can be changed to "It is a meeting." In addition, since the state (pictogram) is not designated in the schedule item data, the status information (pictogram) is not changed. If the schedule item data includes a status (pictogram), the status information status (pictogram) is changed to the status (pictogram) specified by the schedule item data. If the state (pictogram) is not included, the default state (pictogram) is changed.

  FIG. 13 shows an example of an event list related to a service provision start event or a service provision end event. For example, when the provided service started is chat, each item of status information can be changed to each item corresponding to “chat”. That is, the status information state (text) can be changed to “Chat”, and the telephone response status, mail response status, and PoC response status can be changed to “response NG”, “reply later”, and “participation NG”. Since nothing is specified in the comment of the item data, the comment can be left unchanged or displayed as blank.

  FIG. 14 shows an example of an event list related to a terminal usage event. For example, when the terminal use device whose use of the communication terminal is detected is a train ticket gate, if the use state data is OFF, that is, false, the status information state (text) can be changed to “inside the train”. In addition, the telephone response status, mail response status, and PoC response status can be changed to “response NG”, “reply later”, and “participation NG”. Since nothing is specified in the comment of the item data, the comment can be left unchanged or displayed as blank.

  As a terminal use device, as shown in FIG. 14, an airplane ticket gate, a movie theater ticket checker, etc. can be illustrated. If the use state data is ON, that is, true, it is considered that the service provision has been terminated, so that the status information such as the state (text) can be changed to the default state (text) or the like. When the end of service provision is not detected by the communication terminal 100 or the like, the status information is maintained as it is without referring to the usage state data, or the status information is changed by detecting the start of another service. May be adopted.

  FIG. 15 shows an example of a hardware configuration of the communication control server 300 according to the present embodiment. The communication control server 300 according to this embodiment includes a CPU peripheral unit having a CPU 1505, a RAM 1520, a graphic controller 1575, and a display device 1580 that are connected to each other by a host controller 1582. The communication control server 300 also includes an input / output unit having a communication interface 1530, a hard disk drive 1540, and a CD-ROM drive 1560 that are connected to the host controller 1582 by the input / output controller 1584. Further, the communication control server 300 includes a legacy input / output unit having a ROM 1510, a flexible disk drive 1550, and an input / output chip 1570 connected to the input / output controller 1584.

  The host controller 1582 connects the RAM 1520 to the CPU 1505 and the graphic controller 1575 that access the RAM 1520 at a high transfer rate. The CPU 1505 operates based on programs stored in the ROM 1510 and the RAM 1520 to control each unit. The graphic controller 1575 acquires image data generated by the CPU 1505 or the like on a frame buffer provided in the RAM 1520 and displays the image data on the display device 1580. Alternatively, the graphic controller 1575 may include a frame buffer that stores image data generated by the CPU 1505 or the like.

  The input / output controller 1584 connects the host controller 1582 to the communication interface 1530, the hard disk drive 1540, and the CD-ROM drive 1560, which are relatively high-speed input / output devices. The communication interface 1530 communicates with other devices via a network. The hard disk drive 1540 stores programs and data used by the CPU 1505 in the communication control server 300. The CD-ROM drive 1560 reads a program or data from the CD-ROM 1595 and provides it to the hard disk drive 1540 via the RAM 1520.

  The input / output controller 1584 is connected to the ROM 1510, the flexible disk drive 1550, and the relatively low-speed input / output device of the input / output chip 1570. The ROM 1510 stores a boot program that the communication control server 300 executes at startup, a program that depends on the hardware of the communication control server 300, and the like. The flexible disk drive 1550 reads a program or data from the flexible disk 1590 and provides it to the hard disk drive 1540 via the RAM 1520. The input / output chip 1570 connects various input / output devices via a flexible disk drive 1550 such as a parallel port, a serial port, a keyboard port, and a mouse port.

  A communication program provided to the hard disk drive 1540 via the RAM 1520 is stored in a recording medium such as the flexible disk 1590, the CD-ROM 1595, or an IC card and provided by the user. The communication program is read from the recording medium, installed in the hard disk drive 1540 in the communication control server 300 via the RAM 1520, and executed by the CPU 1505. The communication program installed and executed in the communication control server 300 works on the CPU 1505 or the like to cause the communication control server 300 to function as each unit described with reference to FIGS. That is, the communication program uses the communication control server 300, the event detection unit 302, the status information change unit 304, the status information transmission unit 306, the data reception unit 308, the schedule storage unit 310, the timer unit 312, the user database 314, and the status information reception unit 322. And function as the control unit 324.

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiment. It is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

An example of the whole system 10 including the communication control server 300 of this embodiment is shown. An example of functional blocks of the communication control server 300 is shown. The example of the whole flow of the communication method in the communication control server 300 is shown. The example of a flow of an event detection process is shown. An example of a processing flow in the timer unit 312 is shown. The example of a processing flow in the data receiving part 308 is shown. A flow example of processing for changing status information in the case of a schedule start event will be shown. The flow example of the process which changes status information in the case of a schedule end event is shown. The example of a flow of the process which changes status information in the case of a service provision start event is shown. An example of a flow of processing for changing status information in the case of a service provision end event is shown. The example of a flow of the process which changes status information in the case of a terminal use event is shown. An example of the schedule data stored in the schedule storage unit 310 is shown. An example of an event list related to a service provision start event or a service provision end event is shown. The example of an event list which concerns on a terminal use event is shown. An example of the hardware constitutions of the communication control server 300 which concerns on this embodiment is shown.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Overall system 100 Communication terminal 200 Communication terminal 300 Communication control server 302 Event detection part 304 Status information change part 306 Status information transmission part 308 Data reception part 310 Schedule storage part 312 Timer part 314 User database 316 User information 318 Member list 320 Event list 322 Status information receiving unit 324 Control unit 400 Application server 500 Network 600 Personal computer system 700 Ticket gate 1505 CPU
1510 ROM
1520 RAM
1530 Communication interface 1540 Hard disk drive 1550 Flexible disk drive 1560 CD-ROM drive 1570 Input / output chip 1575 Graphic controller 1580 Display device 1582 Host controller 1584 Input / output controller 1590 Flexible disk 1595 CD-ROM

Claims (7)

A communication control device provided in a network for distributing status information of a user terminal to member terminals of members registered for each of the user terminals,
An event detector for detecting a change event that matches the change condition of the status information;
A status information change unit that changes the status information to status information corresponding to the change event when the event detection unit detects the change event;
The status information changed by the status information change unit, a transmission unit for transmitting to the user terminal and the member terminal;
A communication control device comprising: A data receiving unit that receives schedule data or notification information related to the schedule data;
The event detection unit detects that the current date and time has reached the date and time included in the schedule data or that the notification information has been received as the change event,
The status information change unit changes the status information according to the schedule data or the notification information.
The communication control apparatus according to claim 1. A data receiving unit for receiving notification information indicating that service provision to the user terminal starts or ends from an application program used on the user terminal or a service server that provides a service in accordance with the use of a specific function;
The event detection unit detects reception of the notification information as the change event,
The status information change unit changes the status information according to the notification information.
The communication control apparatus according to claim 1. A data receiving unit that receives notification information indicating that the user terminal has been used from a service server that detects use of the user terminal;
The event detection unit detects that the current date and time has reached a scheduled date and time based on the notification information as the change event,
The status information change unit changes the status information according to the notification information.
The communication control apparatus according to claim 1. The status information changing unit changes the status information when the interlocking data included in the data received in association with the change event or the interlocking data recorded in association with the change event is true, and the interlocking data is Do not change the status information if false,
The communication control apparatus according to claim 1. A communication control method used via a network for distributing status information of a user terminal to member terminals of members registered for each of the user terminals,
An event detection stage for detecting a change event that matches the change condition of the status information;
A status change stage for changing the status information to status information corresponding to the change event when the change event is detected in the event detection stage;
Transmitting the status information changed in the status change stage to the user terminal and the member terminal;
A communication control method comprising: A communication control program for use in a communication control device provided in a network, which distributes status information of a user terminal to member terminals of members registered for each user terminal, the communication control device comprising:
An event detection unit for detecting a change event that matches the change condition of the status information;
A status information change unit that changes the status information to status information corresponding to the change event when the event detection unit detects the change event;
A transmission unit that transmits the status information changed by the status information change unit to the user terminal and the member terminal;
Communication control program to function as.

Images