JP2014085810A - Notification bi-directional communication system and viewer terminal - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a notification bi-directional communication system which enables a viewer to access to notification of an operator in a certain area at any time in any place and to obtain a content desired by the viewer efficiently.SOLUTION: A viewer terminal 900, an operator terminal 100, a cloud system 10 and the Internet network 20 are connected to one another so that notification registration data from a municipality, a notification service operator and the like can be received by any one at any time in any place, regardless of the type of the viewer terminal. Notification of a DB server 400 which is displayed after a lapse of a prescribed time is simultaneously distributed by a spray web server 1020 to viewer terminals 900 for which the spray web server is responsible, and a notification title is sequentially displayed on the viewer terminals after a lapse of a prescribed time. Then, when the notification title is selected, detailed information of the notification title which has been registered in advance by the operator is taken out of the DB server 400, and is distributed to the viewer terminals via a low capacity content distribution web server unit 1100.

Description

  The present invention relates to an announcement interactive communication system that distributes efficient announcements to viewer terminals connected to the Internet network.

  There are a variety of services for two-way communication of information transmission via the Internet. A company, a university, or the like has a two-way communication that includes a www server, a database server, and the like to allow a user to access a home page and provide information required by the user.

  The two-way communication includes a method in which the server side takes the initiative and periodically sends information to the user's terminal to provide information requested by the user, a method in which the user accesses the server and obtains information, etc. There is.

  Such two-way communication is also used for safety confirmation, local government disaster prevention information, and the like.

  For example, in Patent Document 1, a dedicated terminal is used as a receiving terminal. Then, the distribution device in the government office etc. divides these dedicated terminals into groups, and when the time comes, it provides information to the dedicated terminals (with browser function) of the corresponding group, and buttons displayed on the screen of the dedicated terminals Is collected, and notification information corresponding to the pressed button type is circulated by voice.

Japanese Patent No. 4808369

  In recent years, more and more children live in the city and parents are in rural areas. For this reason, there is also a demand that urban children always keep the information provided from the government office to the parent dedicated terminal.

  On the other hand, in recent years, more people have multifunctional mobile phones (smart horns), tablets, and personal computers. In the meantime, there is a desire to acquire the information provided in Patent Document 1 with a multi-function mobile phone or the like.

  However, since the method of Patent Document 1 does not employ a method that can respond immediately even if a large number of people access it, those who are far away cannot share information.

  In addition, since Patent Document 1 mainly transmits information to a dedicated terminal led by a distribution device, selects a button displayed on the screen, and knows that the button is pressed. You don't get the content you want.

  For example, even if a plurality of notifications are sent from the government office of XX town in XX prefecture, they are not necessarily all required by the viewer.

  Therefore, it is desirable to provide an interactive notification delivery system that allows viewers to browse notifications of business operators in a certain area at any time and efficiently obtain the content desired by the viewers.

  The interactive bi-directional communication system of the present invention is an interactive bi-directional communication system that is connected to an operator terminal of an operator that registers an announcement of an area, an audience terminal of a viewer, and an announcement service center via a communication network.

The announcement service center
A push route section to the viewer terminal is constructed by a spray web server section having a plurality of spray servers and a batch server section having a batch server, and further a low-capacity content signal having a plurality of content distribution web servers. The web server unit constructs a pull route unit that accepts access from the viewer terminal, transmits various information after login from the pull route unit, and the push route unit transmits detailed information of the notification registered by the operator. Connect the notification service providing server that sends the notification title information,
The notification service providing server is:
Control data for causing the viewer terminal to generate notification title information storage means for sequentially storing the notification title information;
Control data to be divided into an item screen for displaying a service item of an operator on the viewer terminal and a detail screen for displaying details of the service item;
Control data for causing the viewer terminal to generate a memory for an item screen, a memory for the detailed screen, and
Control data for generating a folder for the service item in a memory for the item screen;
With the selection of the service item on the item screen, control data for displaying the service item on the detail screen via the memory for the detail screen;
The notification title information stored in the notification title information storage means is read, and each time the read information is read, whether or not to pass the detailed screen to the notification service center is displayed on the detailed screen. Control data to be added to the service item name folder ID and transmitted to the notification server center;
When the passage response result information for the passage presence / absence inquiry information is received from the notification service center and the passage response result information indicates that the passage does not pass, the notice title of the read notice title information is read for the detailed screen. Control data to be displayed on the detailed screen via a memory and to store the read notification title information in a folder indicated by the passing response result information;
If the passage response result information indicates passing, the notification title information of the destination service item included in the passage response result information is not displayed without displaying the notice title of the read notice title information. And means for transmitting the control data to be stored in the folder having the folder ID via the pull route unit,
further,
The notification service providing server is:
In the detailed screen of the service provider name, the service item name, the service item name, the passage presence / absence flag indicating that the notification title is to be passed or not passed, the folder ID of the moving destination when passing, or the case of not passing A notification title passage presence / absence master in which notification title passage presence / absence information associated with the folder ID is stored;
When the passage presence / absence inquiry information is received from the viewer terminal, the information includes the business ID included in the passage presence / absence inquiry information, the viewer ID, and the ID of the service item name displayed on the detailed screen. Means for reading notification title passage presence / absence information from the notification title passage presence / absence information master;
Means for transmitting the read notification title passage presence / absence information to the viewer terminal in the pull route unit;
It is summarized as having.

  As described above, according to the present invention, the viewer terminal can provide a desired notification by accessing the notification service providing center anytime and anywhere.

1 is a schematic configuration diagram of a notification communication system according to a first embodiment. 2 is a schematic configuration diagram of a viewer terminal 900. FIG. 3 is a schematic program configuration diagram of a DB server 400. FIG. It is a schematic block diagram by the side of a provider terminal. It is explanatory drawing of various master tables. It is explanatory drawing of various master tables. It is explanatory drawing of various master tables. It is explanatory drawing of various master tables. It is explanatory drawing of various master tables. It is explanatory drawing of various master tables. It is explanatory drawing of various master tables. It is explanatory drawing of various master tables. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is a sequence diagram explaining operation | movement of this Embodiment. It is explanatory drawing of a notification basic information input screen. It is explanatory drawing of a delivery destination registration screen. It is explanatory drawing of the registration change screen of a delivery destination folder. It is explanatory drawing of a delivery list | wrist, notification title information, and a viewer log. It is explanatory drawing of a delivery list | wrist, notification title information, and a viewer log. It is explanatory drawing of the item screen displayed on a viewer terminal. It is explanatory drawing of the notification title displayed on a viewer terminal. It is explanatory drawing of an unread list. It is explanatory drawing of the detailed screen displayed on a viewer terminal, and a moving image screen. It is a schematic block diagram of the notification bidirectional | two-way communication system of this Embodiment 2. It is a schematic block diagram of the notification change process part 401 for every viewer of DB server. It is a flowchart explaining operation | movement of the notification change process part 401 for every viewer. It is a flowchart explaining operation | movement of the notification change process part 401 for every viewer. It is explanatory drawing explaining notification update. It is explanatory drawing of the notification title in the detailed screen displayed on the viewer terminal by Embodiment 2. FIG. It is a schematic block diagram of the application example of this Embodiment. It is a schematic block diagram of the application example of this Embodiment.

  The notification interactive communication system according to the present embodiment allows notification registration data from local governments, notification service providers, etc. (hereinafter collectively referred to as business operators) to be anytime, anywhere, and regardless of the type of terminal of the viewer. It is a system that can receive, and the notification registration data registered in the cloud system (also referred to as the notification providing service center) is distributed to the viewer side by push, and the viewer side is configured to acquire this notification registration data by pulling. ing.

  In addition, it is assumed that the operator includes an administrator (icom) of this system, a restaurant, a hospital, a school, a department store, a supermarket, an agricultural cooperative, a fishery association, and the like.

  The viewers are nationwide and are divided into areas (for example, A prefecture A city, B prefecture B city, Tokyo C ward,...). The operators in these areas are responsible for these areas.

  The viewer terminal owned by the viewer is a smart horn, a tablet, a personal computer, a television with an Internet interface, or the like.

<Embodiment 1>
There may be several different business operators in an area with millions of viewers, but in the first embodiment, A city in A prefecture is one area, and other than the management business is one local government. explain.

  FIG. 1 is a schematic configuration diagram of a notification communication system according to the first embodiment. As shown in FIG. 1, the notification communication system of this embodiment includes a plurality of viewer terminals 900 (10000, 1000000,..., 10000 in FIG. 1) and a cloud server system 10 ( (Notification providing service center section), management operator terminal 200, and local government administrator terminal 100 are connected to each other by a communication network 20 (for example, the Internet network).

  As shown in FIG. 1, the cloud server system 10 includes a batch server 600, a spray management web server 700, a spray server unit 1001 (spray session establishment web server 1010, spray servers 1020a to 1020j)), a batch server 600, The push route unit is formed by the DB server 400 or the like.

  In addition, a login route / distribution web server 1000, a low-capacity content distribution web server 1100, a DB server 400, and the like form a pull route unit.

 Further, the pull route unit includes a true web server 1200 (1200a to 1200j) and a storage server 500 for large-capacity content.

  In addition, an administrator web server 300 and a configuration management web server 800 are included.

  The administrator web server 300 is connected to the communication network 20, the spray management web server 700, and the storage server 500.

  The DB server 400 is connected to the batch server 600, the configuration management web server 800, the storage server 500, the low-capacity content distribution web servers 1100a to 1100j, the spray web servers 1020a to 1020j, and the like.

  The management configuration web server 800 is connected to the communication network 20, the DB server 400, and the storage server 500. In other words, the contents of the memory of the DB server 400 and the storage server 500 can be referred to and rewritten by access from the management company terminal 200.

  The batch server 500 is connected to the DB server 400 and the spray management web server 700.

  The spray management web server 700 is connected to the administrator web server 300 and each spray web server 1020.

  The spray server 1020 is connected to the spray management web server 700, the spray session establishment web server 1010, the DB server 400, the communication network 20, and the like.

  Further, the login reception / distribution web server 1000 is connected to the communication network 20, each low-capacity content distribution web server 1100, each large-capacity content distribution web server unit 1200, and the like.

  Each large-capacity content distribution web server unit 1200 is connected to the storage server 500.

  With such a connection configuration, push distribution and pull distribution are possible.

  In addition, the viewer contacts the management company to register as a member.

(Outline of push delivery)
In push distribution, a notification from an operator terminal (local government administrator terminal 100, management operator terminal 200) is registered in the DB server 400 via the administrator web server 300, and this is registered by the batch server 600 for a certain period of time. The later (for example, notification to be displayed on the viewer's screen after 15 minutes) is taken out and transmitted to the spray web server unit 1001 via the spray management web server 700, and the spray web server 1020 of the spray web server unit is for establishing a spray session. The web server 1010 broadcasts the information to the viewer terminal 900 in charge, and the notification titles are sequentially displayed on the viewer terminal after a predetermined time.

(Pull delivery overview)
In the pull distribution, login from the viewer terminal 900 is accepted by the login reception / distribution web server 1000, and this is transmitted to the DB server 400 via the low-capacity content distribution web server unit 1100 for authentication. Establish a session with 900.

  Then, the main item of the operator in charge of the area of the viewer terminal 900 stored in advance is extracted from the DB server 400 and distributed to the viewer terminal via the low-capacity content distribution web server unit 1100.

  Then, when a notification title included in any one of the main items is selected from the viewer terminal, the detailed information of the notification title registered in advance by the operator is taken out, and the low-capacity content distribution web is extracted. Distribution to the viewer terminal via the server unit 1100.

  When the viewer terminal 900 requests a video (including audio), the log-in reception / distribution web server 1000 extracts the video from the storage server 500 via the large-capacity content web server unit 1200 and the viewer terminal 900 Deliver to.

(Server description)
Each of the spray web servers 1020a to 1020j, the low-capacity content distribution web servers 1100a to 1100j, and the large-capacity content distribution web servers 1200a to 1200j of the spray server unit 1001 is in charge of, for example, 1000 viewer terminals 900.

  The DB server 400 stores control data to be described later, a function (means) for transmitting the control data to the viewer terminal 900, a notification title distribution processing unit 410, a display passage determination processing unit 420, and a history registration processing unit. 430 and a detailed distribution processing unit 440 at least.

  The notification title distribution processing unit 410 distributes the information in the pull route unit. The notification title information (notification ID, title name,...) Registered by the business operator for a certain period of time is passed to the batch server 600 in units of groups or viewers to the spray server unit 1001 (spray session establishment web server 1010, spray Broadcast from the servers 1020a to 1020j)) to the viewer terminal 900.

  If there is a display title display inquiry (passed or not passed) from the viewer terminal 900 via the low-capacity content distribution web server 1100 after the session is established, the display passage determination processing unit 420 displays the notification title as a display setting condition. Response information that is displayed on the screen or not displayed on the screen is returned.

  The history registration processing unit 430 receives the screen operation status of the viewer terminal 900 and registers it (including the deletion of the notification title).

  The detailed distribution processing unit 440 sends back the detailed information registered in association with the notification title when the notification title is touched.

  The administrator web server 300 receives access from the local government administrator terminal 100 or the management operator management terminal 200 via the communication network 20, and provides pages requested by these operators from the DB server 400. The input various data is transmitted to the DB server 400 or the spray management server 700.

  The batch server 600 takes out the notification title information (notification ID, notification title name, viewer ID, time until display, icon ID) to be displayed after a predetermined time registered in the DB server 400 every predetermined time. Is transmitted to the spray management web server 700.

  The spray management web server 700 knows which viewer ID the spray web servers 1020a to 1020j deliver to the viewer terminal 900, and transmits the received notification title information to the corresponding spray web server 1020.

(Configuration of the viewer terminal 900)
The viewer terminal 900 (having a browser and an Internet interface) has a program configuration described below based on control data from the DB server 400 of the cloud server system 10.

  FIG. 2 is a schematic configuration diagram of the viewer terminal 900. The viewer terminal 900 includes a RAM, a ROM, a CPU, and the like, and blocks the configuration that functions according to control data.

  In FIG. 2, the viewer terminal 900 displays the screen in two parts, and displays the main item screen GB on the left side (left of the page) and the detail screen GA on the right side.

  The main item screen GB displays the distribution company name GBA (XX government office) of the area and the item name Gba provided by this distribution company (notice of today Gba1, Gba2 from the government office, photo ... PTA ...). It is displayed. Also, the main item screen provided by icom is on the back side. Also, in these items, the number of unread (full numbers) of the notification detailed information is shown. It should be noted that the ○ number of the distribution company name GBA (XX office) is the total number of unread times for each item.

  Further, the notification title Ai (A1, A2,...) Is displayed on the management detail screen GA on the detail screen GA. In addition, a delete icon Bi is displayed for these notification titles Ai.

  As shown in FIG. 2, the main item screen GB is provided with a main item screen memory 920 associated therewith, and information stored in the main item screen memory 920 is displayed by a browser.

  The detailed screen GA is provided with a detailed screen memory 910 for displaying a notification title and the like.

  Furthermore, a memory 930 for storing the announcement title information from the cloud server system 10 is provided.

  Furthermore, a main item acquisition unit 950, a title display unit 980, a timer 970, a detailed acquisition unit 920, a title display presence / absence inquiry unit 982, a storage / delivery destination folder determination unit 983, a title deletion unit 990, a video An acquisition unit 960 and the like.

  The main item acquisition unit 950 receives the login page provided by the URL of this site, inputs the login ID and password, transmits the login information to the login reception / distribution web server 1000 indicated by the URL, and then transmits the login information to the DB server. The main item (operator name, today's notice, from the government office ...) and the unread list from 400 (via the low-capacity content distribution web server 1100) and the unread list are received and stored in the main item screen memory 920.

  When saving to the main item screen memory 920, the main item acquisition unit 950 generates a folder (also referred to as a large distribution destination folder 940) of the business name in the main item screen memory 920, and stores each item in the large distribution destination folder. Folders (also simply referred to as distribution destination folders 941a, 941b...) Are generated in association with each other and displayed on the screen by a browser function.

  Further, when an item (Gbai: distribution destination folder name) on the main item screen GB is selected, the main item acquisition unit 950 stores the item (distribution destination folder name) in the detailed screen memory 910 and stores the detailed screen GA. To display.

  The title display unit 980 sequentially reads the notification title information in the memory 930, and when the display time included in the read notification title information and the current time of the timer 970 substantially match (for example, 0.5 seconds before) ), Notifies the title display presence / absence inquiry unit 982 of the notification ID of the notification title information.

  The title display presence / absence inquiry unit 982 transmits the combination of the notification ID, the viewer ID, and the business ID to the login reception / distribution web server 1000 as display inquiry information (also referred to as passage presence / absence inquiry information).

  Then, it is determined whether the display inquiry response information from the login acceptance / distribution web server 1000 indicates “pass” or “do not pass”. The title information announcement title is stored in the detail screen memory 910 and immediately displayed on the detail screen GB.

  Further, when “pass” is indicated, the notice title of the read notice title information is not displayed on the detailed screen GB.

  The storage / delivery destination folder determination unit 983 indicates that the display inquiry response information (enterprise ID, viewer ID, notification ID, automatic or manual, pass setting information, destination: also referred to as pass response result information) does not pass. Is stored in the distribution destination folder corresponding to the item displayed on the detailed screen GB.

  Further, when the display inquiry response information indicates “pass”, the storage / delivery destination folder determination unit 983 sets the destination distribution destination folder (for example, a government office) included in the display inquiry response information. Store.

  The detail acquisition unit 920 monitors whether or not the notification title Ai displayed on the detail screen GB is touched when the notification title information read by the notification title display unit 980 indicates manual. The notification ID, viewer ID, company ID, detailed request, and the like are transmitted as detailed information request information to the login acceptance / distribution web server 1000, and the detailed information is received and immediately displayed on the detailed screen GB.

  In addition, when the notification title information read by the notification title display unit 980 indicates automatic (what has reached the time to display), the detail acquisition unit 920 displays the notification ID, viewer ID, company ID, and details. The request or the like is immediately transmitted to the login acceptance / distribution web server 1000 as detailed information request information, and the detailed information is received and immediately displayed on the detail screen GB.

  When the video button of the notification title is selected, the video acquisition unit 960 outputs the notification ID, the business ID, and the video request to the login reception / distribution server 1000 as video request information, and transmits the transmitted video. Display on the detail screen GB.

  When the notification title deletion button Bi is touched, the title deletion unit 990 deletes the notification title in the detailed screen memory 910 and deletes the notification title information in the memory 930 and the distribution destination folder. In addition, the notification ID, the operator ID, the viewer ID, and the deletion flag are transmitted as the title deletion information to the login reception / distribution web server 1000, and the deletion flag is set in the corresponding log information.

(Configuration of DB server 400)
FIG. 3 is a schematic program configuration diagram of the DB server 400. The viewer terminal 900 includes a RAM, a ROM, a CPU, and the like, and blocks the configuration that functions according to control data.

  As shown in FIG. 3, the DB server 400 includes various input screen providing units 470, various masters 471, notification ID issuing units 472, a memory 473 that stores notification registration data KBi, and a predetermined time ahead data extracting unit 411. A notification title transmission unit 414, a log creation unit 416, a memory 415 for storing a log, a viewer terminal transmission result writing unit 431, and a title operation result writing unit 432.

  In addition, a viewer authentication unit 460, a main item providing unit 480, a detailed screen providing unit 441, an unread count updating unit 442, a display presence / absence notification unit 430, a post-session log creation unit 490, and the like are provided.

  The notification title distribution providing unit 410 includes a predetermined time ahead data extraction unit 411, a notification title transmission unit 414, and a log creation unit 416, and a registration processing unit 430 includes a viewer terminal transmission result writing unit 431. , Corresponding to the title operation result writing unit 432.

  The display passage determination processing unit 420 corresponds to the display presence / absence notification unit 431, and the detailed distribution processing unit 440 corresponds to the detailed screen providing unit 441 and the unread count updating unit 442.

  The various input screen providing unit 470 provides various pages (for example, a notification registration screen, a distribution destination schedule input screen, a folder passage input screen,...) To be provided to the provider. At this time, the notification ID (unique code), URL, etc. from the notification ID issuing unit 472 are provided in association with each other. Information on various master tables 471 is provided as necessary.

  For example, notification basic input information ka, distribution destination input information kb, and notification distribution folder destination change input information kc are provided, and these pieces of information are stored in the memory 473 as notification registration data KBi.

  Each time the notification request information from the batch server 600 is input, the fixed time ahead data extraction unit 411 sequentially reads the basic notification information KMa into the memory 473 (registration order), and is ahead of the current time of the timer 412 by a fixed time. When there is the basic notification information KMa to be distributed (for example, 15 minutes ahead: including regular, regular, and general cases), the user ID (group ID or viewer ID) of the distribution destination scheduled information KMb having this notification ID ) And a distribution list Li including a distribution destination folder ID, a provider ID, and the like are created in the memory 413.

  The notification title transmission unit 414 allocates a record of the distribution list Li in the memory 413, and distributes the user ID (viewer ID or group ID) and notification ID of this record, and the distribution date and time of the notification basic information KMa having this notification ID ( Time until display; for example, display after arrival 15), icon ID, and notification title (for example, today's summer festival) are read, and these are combined and transmitted to the batch server 600 as notification title information KHi).

  When the user ID is a group, all the viewer IDs associated with the group ID are transmitted as a lump associated with the notification ID, distribution date (time until display), icon ID, and notification title.

  The log creation unit 416 creates first distribution initial log information Fa for each viewer shown in FIG. 27C in the memory 415 in accordance with the creation of the notification title information KHi.

  Then, the second viewer initial log Fb in which the viewer ID and the notification ID are embedded in the corresponding column of the first viewer initial distribution log information Fa is generated, and the viewer ID from the batch server 600 and A per-viewer log Fi (also referred to as a delivery destination result) in which the notification ID is embedded in the second per-viewer initial log Fb is generated.

  The viewer terminal transmission result writing unit 431 receives the distribution result information from the viewer terminal 900 via the low-capacity content distribution web server 110 and stores the log Fi having the viewer ID and notification ID of the distribution result information. Assign and write the transmission result in this transmission result column (error or OK).

  The title operation result writing unit 432 receives the operation result (deletion, touch) of the notification title from the viewer terminal 900 via the low-capacity content distribution web server 110 and receives the viewer ID and notification ID of the operation result. The assigned log Fi is allocated and written in the corresponding column (deletion, reproduction).

  The viewer authentication unit 460 performs authentication by comparing the login information with the viewer master table 471, and returns authentication result information (OK) (d55). At this time, the viewer authentication unit 431 generates a user ID using, for example, time (including date), login information, viewer ID, and the like, and further combines the URL (access destination) of the spray session establishment web server 1010. Sending.

  The main item providing unit 480 reads the business operator ID included in the user ID after the session is established, allocates all the delivery destination folder masters having this business operator ID, and the delivery included in these delivery destination folder masters. The destination folder name is read, main item screen information is created and transmitted to the viewer terminal 900 via the low-capacity content distribution Web server 1100.

  The detailed screen information providing unit 441 reads the notification title touch information from the viewer terminal 900 via the low-capacity content distribution Web server 1100, and displays the detailed content having the notification ID, viewer ID, and business ID as the detailed content database 444. And transmitted to the viewer terminal via the low-capacity content distribution server 1100.

  The display presence / absence notification unit 431 receives the display inquiry information from the viewer terminal 900, assigns the notification basic information master having the notification ID and the operator ID, and the manual reproduction is written in the notification basic information master. In this case, the distribution destination folder master having the distribution destination folder ID and the business ID of the display inquiry information is allocated.

  Then, the status of the folder pass flag of the master (“pass” or “do not pass”) is returned as a display inquiry response result.

  The unread count updating unit 442 reads the notification title deletion information from the viewer terminal 900, assigns a log having the notification ID, the viewer ID, and the business operator ID, and sets a deletion flag (“1”).

  The post-session log creation unit 490 writes the display start time of the announcement title Ai from the viewer terminal 900, the display start time of the detailed information, and the like as log information in the log.

  As shown in FIG. 4, the management terminal of the above-mentioned operator (for example, a local government) connects the input person terminal 100a and the upper person terminal 100b with a LAN cable, and the upper person terminal 100b is the input person. It is preferable to check the notification basic information, the distribution destination, and the distribution destination folder input from the terminal 100a and change the setting to “do not pass” when an unsuitable distribution destination folder is set.

(Various master tables)
As shown in FIG. 5, the various masters (memory) are a viewer master table, a provider master table, a provider detail master table, a group master table, a viewer group master table, and a distribution destination folder master. Table, ID management master table, viewer login management master table, online viewer master table, notification basic information master table, notification detailed information master table, notification distribution destination schedule master table, notification distribution destination results It consists of a master table (also referred to as a distribution log master table), a code management master table, etc.

  6 shows the viewer master table 401a, FIG. 7 shows the provider master table 401b, and FIG. 8 shows the distribution destination folder master table 401c, the ID management master table 401d, and the code management master table 401e. FIG. 9 shows a basic notification information master table 473a, FIG. 10 shows a detailed notification information master table 473b, and FIG. 11 shows a notification distribution destination schedule information master table 473c, and notification distribution results (viewer log). FIG. 12 shows a viewer login management master 471g and an online viewer management table 471h.

  These master tables are provided for each viewer on a business unit basis. However, the notification basic information master table, the notification detailed information master table, the notification distribution destination schedule master table, and the notification distribution destination performance master table (also referred to as distribution log master table) are not shown in the various master tables 471. Shown out.

(Overall operation description)
In the first embodiment, a local government is taken as an example.

  13 to 23 are sequence diagrams for explaining the operation of the first embodiment.

(Register notification data)
The person in charge of the local government administrator terminal 100 operates the keyboard and mouse of the local government administrator terminal 100 to perform connection processing with the administrator web server 300 and the DB server 400 (d1, d2).

  Then, the administrator web server 300 communicates with the DB server 400 to provide (transmit) various screens necessary for the local government administrator terminal 100 (d3, d4). These various screens are acquired by the various input screen providing unit 410 in FIG.

  In providing this screen, the various input screen providing unit 470 of the DB server 400 activates the notification ID issuing unit 472 shown in FIG. 3 to issue and add a notification ID (d5, d6).

  The notification ID is a unique code that combines date, company code, person-in-charge code, content type, random number, and the like. In this embodiment, a notification basic information input screen (in the case of new registration) shown in FIG. 24 is provided.

  This screen is a screen for inputting basic notification information of the A area of the A city.

  On the left side of this screen, an emergency, regular, regular, and general notice delivery type column Ci is provided, which is designated by the person in charge. Further, a column CHa for specifying a distribution time is provided, a column for specifying a distribution date Cha, a column chb for setting a distribution time, a column chc for specifying distribution immediately after registration, and a column chd for specifying a live broadcast. Are displayed.

  Further, on the left side, a distribution pattern column CBa for setting manual, automatic, presence / absence of chime on, level, and the like is displayed. Further, a time limit column Cca for setting a publication time limit and a storage time limit is displayed.

  On the other hand, a message area setting field Ea, a content type field Eb, a title input field Ec, an icon selection field Ed, a text input field Ee, a voice recording designation field Ef and the like are displayed.

  Such input information is referred to as notification basic input information ka.

  The above-mentioned emergency is emergency information to be delivered immediately, and the fixed time means delivery in the morning, for example, at 8:00, noon at 12:00, and evening at 18:00. The term “periodic” means broadcasting at 11:00 every month, for example, Wednesday. General means delivery at a specified time.

  In addition, the person in charge of the municipal administrator terminal 100 operates the keyboard, mouse, etc. of the municipal administrator terminal 100 to communicate with the administrator web server 300 and receives the distribution destination registration screen shown in FIG. As shown in FIG. 25, the delivery destination can be specified in viewer units and group units (collectively referred to as user units). In addition, a distribution destination folder (major item of notification distributed by the operator; item folder name displayed on the viewer terminal) can also be set.

  Such input information is referred to as distribution destination input information kb.

  Further, the person in charge of the local government administrator terminal 100 operates the keyboard, mouse, etc. of the local government administrator terminal 100 to communicate with the administrator web server 300 and is provided with the distribution folder registration change screen shown in FIG. . The screen of FIG. 26 includes a business name, a delivery destination folder name ((2): empty 3 (for example, recipe)), a delivery destination folder number, and designation of passing (1).

  Such input information is referred to as notification distribution folder destination change input information kc.

  In other words, if it is set to pass (1), “means that (1) is passed and registered in the folder (2). The operation on the distribution folder registration change screen has high administrative authority. When the person in charge operates the personal computer (not shown) to check the basic notification information registered and the distribution destination folder on the screen, and when it is determined that it is not enough to register today (1) , (1) is set.

  As a result, the number of notification titles displayed on the detailed screen of the viewer terminal 900 can be limited, so that only effective information can be provided as today's notification.

  The person in charge (simply a person in charge of input, a person in charge with high authority) inputs such information manually and transmits it to the administrator web server 300 (d7).

  On the other hand, the administrator web server 300 includes notification registration information Ki (including notification basic input information ka, distribution destination input information kb, notification distribution folder change input information kc, etc.) from the local government administrator terminal 100. It is received as a moving image / sound (with a notice ID, with a viewer ID), and a distribution determination is made (d12).

  For distribution, the notification registration information Ki is transmitted to the DB server 400 (d11), and the moving image / audio data is transmitted to the storage server 500 for registration (d13).

  The various input image providing units 470 of the DB server 400 store the registration notification input information Ki in the memory 473 (d14).

  In addition, since various data is added to the registered notification input information Ki (including the notification basic input information ka, the distribution destination input information kb, the notification distribution folder destination change input information kc, etc.), it is registered in the memory 473. The registered notification input information Ki is referred to as notification registration data KMi, the notification basic input information ka is the notification basic information KMa (see FIG. 9), the distribution destination input information kb is the notification distribution destination scheduled information KMb (see FIG. 11), and the notification distribution. The folder destination change input information kc is called notification delivery destination folder change information (also simply called the delivery destination folder master 401) and is called KMc (see FIG. 8).

  Note that the detailed notification information (FIG. 10) is also added to the basic notification information KMa.

  In the delivery destination folder master (notification delivery destination folder change information KMc) stored in FIG. 8, a folder passage flag is set (“pass”, “do not pass”).

  In this way, the autonomous manager terminal 100 registers information to be notified in the DB server 400 of the cloud server system 10.

(Notification delivery from the cloud server system to the viewer terminal)
(Distribution from DB server to batch server)
As shown in FIG. 14, every time the timer 610 measures a certain time (for example, 1 minute) (d21), the batch server 600 transmits notification request information to the DB server 400 (d22).

  The predetermined time ahead data extraction unit 411 of the DB server 400 monitors whether notification request information (for example, every minute) has been received from the batch server 600 (d23a).

  When the notification request information is received, every time the notification request information is received from the batch server 600, the notification basic information KMa (see FIGS. 9, 10, and 26) in the memory 473 is read sequentially (registration order) and distributed. When the type ID is other than emergency (regular, regular, general), it is determined whether or not there is the notification basic information KMa to be distributed a predetermined time ahead (for example, 15 minutes ahead) with respect to the current time of the timer 412 (d23b).

  If the notification basic information KMa to be distributed for a predetermined time exists in the memory 473, the fixed time ahead data extraction unit 414 reads the notification ID of the notification basic information KMa, and stores the distribution destination scheduled information KMb having this notification ID in the memory. Search from 473. Then, the set user ID (group ID or viewer ID) is read, and a distribution list (Li) including a notice ID, a user ID, a distribution destination folder ID, a provider ID, and the like is created in the memory 413. (D24).

  The distribution destination folder ID is preferably read from the distribution destination schedule information KMb (see FIG. 11).

  As shown in FIG. 27A, the distribution list Li includes a viewer ID, a notification ID, and a distribution destination folder ID for each company ID.

  Then, the notification title transmission unit 414 of the DB server 400 allocates the record of the distribution list Li in the memory 413, the user ID (viewer ID or group ID) of this record, the notification ID, and the notification base having this notification ID. The distribution date and time of information KMa (see FIG. 9) (time until display; for example, displayed after arrival 15), icon ID, and notification title (for example, about today's summer festival) are read.

  These are combined to generate notification title information KHi (see FIG. 27B) (d25).

  When the user ID is a group ID, a viewer group master (not shown: a group ID and a viewer ID are associated with each other) stored in the memory 471 is read and associated with this group ID. All the viewer IDs that have been read are incorporated and delivered to the batch server 600 as notification title information KHi (JASON). This notification title information KHi is stored in the memory 481 in the actual distribution list GHi (“viewer A ID, notification ID, business ID, distribution date, notification title, icon ID”, “viewer B ID, notification ID, business operator” ID, delivery date, notification title, and icon ID "...) and save.

  Further, the log creating unit 416 creates the first per-viewer distribution initial log information Fa shown in FIG. 27C in the memory 415 along with the creation of the notification title information KHi (d26).

  The generation of the first distribution initial log information Fa for each viewer will be described.

  Along with the creation of the notice title information KHi, the notice ID field, the viewer ID field, the delivery destination folder ID field, the transmission status field, the viewer playback count field, the automatic playback date / time field, the manual playback date / time field, and the viewer are stored in the memory 415. A record (also referred to as a log record for each viewer) of a deletion flag column or the like (see FIGS. 27C and 11B) is generated.

  Then, the generated first viewer initial log Fa is sequentially specified, the read viewer ID is sequentially specified, and the specified viewer ID is embedded in the specified first viewer initial log Fa, The notification ID and distribution folder ID of the generated notification title information KHi are embedded in the corresponding column. This is referred to as a second initial viewer log Fb in this embodiment.

  When the user ID of the announcement title information KHi is a viewer ID, only the viewer log record for the viewer is generated.

  That is, one viewer log record is created and the viewer ID is embedded, and at the same time, the notification ID of the generated notification title information KHi and the distribution destination folder ID are embedded in the corresponding column, and the second viewer-specific notification distribution is performed. An initial log Fb is generated.

  Then, after generating the second viewer-by-viewer notification delivery initial log Fb, the generated notification title information KHi (with group ID or viewer ID) is transmitted to the batch server 600 (d27).

  Whenever the batch server 600 receives the notification title information KHi transmitted from the DB server 400, the user ID (group ID or viewer ID), the notification ID, and the log included in the notification title information KHi are stored in the DB. It transmits to the server 400 (d28).

  The log creation unit 416 of the DB server 400 receives the log from the batch server 600, allocates the second viewer-specific notice delivery initial log Fb having the viewer ID of this log from the memory 415, and sets the viewer ID of the log. The notification ID is embedded in the corresponding column (d29: see FIG. 28 (c)). A field in which data is actually embedded in the column is referred to as a per-viewer distribution log Fi (actual result).

  Next, the notification title transmission unit 414 determines whether there is another notification in the memory 413, and if there is, moves the process to d23b and distributes the next notification (d30).

  In the case of an emergency, notification title information is embedded at the top of the distribution list for automatic distribution to the batch server (automatic reproduction).

(Batch server-> spray management->spray-> distribution to viewer terminal)
On the other hand, as shown in FIG. 15, the batch server 600 receives the received notification title information KHi (group ID or viewer ID, notification ID, time until display, icon ID, notification title) + attached information (viewer terminal Address etc.) is transmitted to the spray management web server 700 (d31).

  The spray management web server DB 700 manages the spray servers 1020a to 1020j, searches for the corresponding spray server based on the user ID, and transmits the notification title information KHi to the spray server (d33).

  Specifically, a table (not shown) that associates group IDs or viewer IDs with spray server numbers is provided.

  For example, it is assumed that the announcement title information KHi is a group ID, and this group ID corresponds to the spray server 1020a. The spray management server 700 receives the notification title information KHi and transmits it to the spray server 1020a together with the attached information.

  Next, the splay distribution web server 1020a inquires of the splay session establishment web server 1010 which viewer terminal 900 the session has established (d34). This session establishment will be described later.

  Next, the spray distribution web server 1020a determines whether or not the distribution destination viewer terminal 900 is establishing a session (d35).

  When the session is not established, the spray web server 1020a transmits the distribution result information (viewer ID, notification ID, not transmitted) to the DB server 400 (d41).

  The viewer terminal transmission result writing unit 431 of the DB server 400 receives the distribution result information, assigns the distribution log Fi having the viewer ID and the notice ID of the distribution result information, and writes a transmission error in this to the transmission result column. (D42).

  On the other hand, when the distribution destination is session establishment, the spray distribution web server 1020a transmits the notification title information KHi to each connected viewer terminal 900 (d38).

  The viewer terminal 900 stores this announcement title information KHi in the memory 930 (d40).

  Then, the distribution result information is received and transmitted to the DB server 400 (d39). The DB server 400 writes the transmission OK in the viewer terminal transmission result writing unit 426 in the viewing log (d43).

(Session establishment)
In the present embodiment, as shown in FIG. 16, the control data (program) and the notice delivery title information KHi are already stored in the viewer terminal 900, and the icon (notice Ken) is displayed on the screen. (D50a, d50b). The viewer of the viewer terminal 900 touches an icon (notifies you).

  This touch is determined to be an access to the login reception / distribution web server 1000, and the access is transmitted to the login reception distribution web server 100. The login reception distribution web server 1000 transmits a login screen to the viewer terminal 900. Then, the viewer of the viewer terminal 900 inputs the login information and transmits the login information to the login acceptance distribution web server 100 (d52).

  The login acceptance distribution web server 1000 manages which low-capacity content distribution web server 1100 accepts the viewer's access, and transmits the login information to the corresponding low-capacity content distribution web server 1100 (d53). ). In the present embodiment, transmission is performed assuming that the low-capacity content distribution web server 1100a is applicable.

  The low-capacity content distribution web server 1100a transmits this login information to the DB server 400 (d54).

  The viewer authentication unit 460 of the DB server 400 shown in FIG. 3 performs authentication in comparison with the viewer master and returns authentication result information (OK) (d55). At this time, the viewer authentication unit 460 generates a user ID using, for example, time (including date), login information, viewer ID, and the like, and further combines the URL (access destination) of the spray session establishment web server 1010. Sending.

  In addition, when the login information from the viewer terminal 900 is OK (use permission), the viewer authentication unit 460 of the DB server 400 sends the user to the splay distribution web server 1020 that connects the session with the viewer terminal 900. The ID is notified (d56).

  On the other hand, when the authentication result information indicates OK (access permission), the session establishment unit (not shown) of the viewer terminal 900 has its user ID (also referred to as user information) based on the URL of the access destination. Is transmitted to the web server 1010 for establishing a spray session (d57).

  The web server 1010 for establishing a spray session receives the user ID, inquires each spray web server about the spray server 1020 in which the user ID is set, and sets the user ID to the spray server in which the user ID is set. Sort and transmit (d59).

  Upon receiving the user ID, the spray server 1020 sends a session establishment signal to the user terminal 900 (d60).

 Further, the spray distribution Web server 1020a transmits ping data to the viewer terminal 900 so that the line is not disconnected after the session is established (d61), and the viewer terminal 900 returns response data (d62).

  Further, the viewer terminal 900 transmits the viewer ID to the spray distribution Web server 1010, for example, every minute so that the line is not disconnected in the tunnel or the like, and the spray distribution Web server 1020a returns the response signal to connect online. Is completed (d63, 63).

  In this state, manual regeneration and automatic regeneration will be described.

(Manual playback)
In this description, a session is established between the spray distribution Web server 1020a and the viewer terminal 900 (d65).

  Further, it is assumed that the notice title information KHi to be displayed after 15 minutes is stored in the memory 930 of the user terminal 900.

  Also, the main item providing unit 480 of the DB server 400 reads the business ID included in the user ID after the session is established, assigns all the delivery destination folder masters having this business ID, and these delivery destination folder masters. The distribution destination folder name included in is read and main item screen information is created (d68).

  Then, the main item providing unit 480 of the DB server 400 sends the main item screen information (a plurality of distribution destination folder names and distribution destination folder IDs, a business name, and a viewer ID) to the corresponding low-capacity content distribution Web server 1100a. Transmit (d69). At this time, information necessary for communication related to the viewer ID of the viewer master is also added and transmitted.

  The low-capacity content distribution Web server 1100a that has received the main item screen information transmits the received main item screen information to the viewer terminal 900 to which the viewer ID is assigned (d70).

  The unread count sending unit 442 of the DB server 400 sequentially reads the distribution destination folder ID (main item) and the viewer ID on the main item screen, and distribution log information (this distribution destination folder ID and the distribution log information for each reading) ( All of the notification ID and the current detailed playback count of the notification title are assigned from the distribution log table 415, and the total of the current detailed playback counts of these log information is sequentially obtained as the detailed total unread count in the distribution destination folder.

  Then, a distribution destination folder ID and a detailed unread total number of times (also referred to as a distribution destination folder unread frequency list) are created (d71). Then, the distribution destination is transmitted to the viewer terminal that has logged in via the low-capacity content distribution web server 1100 (d72, d73).

  In addition, the distribution destination folder unread count list obtains the total number of detailed unread counts of each distribution destination folder ID (the total number of unreads of the operator) and includes this.

  The main item acquisition unit 950 of the viewer terminal 900 receives the unread list and displays it based on the control data and the screen format as shown in FIG. 29 (d75).

  As shown in FIG. 29, on the left main item screen GB, the distributor name GBA (XX office) is displayed, and the main item name Gbi (this day notice, PTA, government office) distributed by the distributor , Culture... Is displayed, the number of unread viewers is displayed in each main item, and the total number of unread times is displayed in the distributor name (XX government office).

  At this time, the time display unit (not shown) stores the current time of the timer 970 in the detailed screen memory 910 and displays it on the detailed screen GA.

  Specifically, the main item screen memory 950 shown in FIG. 2 is stored in the main item screen memory 920 and displayed on the left main item screen GB.

  Next, in any item Gbai (distribution destination folder name) of the viewer terminal 900, for example, when the viewer touches the distribution provider menu of today's notification (d80), the viewer terminal 900 follows the control data. The viewer ID, the distribution destination folder ID of the menu, the URL to be accessed (low-capacity content distribution web server 1100), and the like are transmitted as distribution destination folder touch information to the low-capacity content distribution web server 1100a for each viewer, and the DB server 400 (D81, d82).

  On the other hand, the main item acquisition unit 950 of the viewer terminal 900 reads the folder name (item name) of the touched item (delivery destination folder name), saves it in the detail screen memory 910, and displays it on the detail screen GA. (For example, today's notice) (d84: see FIG. 30).

(Display of announcement title)
In such a state, the title display unit 980 of the viewer terminal 900 monitors whether or not there is announcement title information in the memory 930 (d87).

  When the notice title information is distributed, the title display unit 980 reads the display time of the notice title information KHi (d88), and immediately determines whether the display (start 0) is indicated (d89).

  If it is immediately determined to be displayed, it is determined to be an automatic reproduction mode to be described later (d90).

  When it is determined that it is not immediately displayed, as shown in FIG. 18, the time until the display of the read notification title information KHi (for example, 12:00) and the current time of the timer 971 are compared and displayed. (D110: For example, it is determined that the display time is 11:59:58).

  When it is determined that it is time to display, the title display presence / absence inquiry unit 982 is notified to the title ID KHi of the notification title information, the viewer ID, the business ID, and the item name (distribution destination folder) displayed on the detail screen ID: read from memory 910).

  The display presence / absence inquiry unit 960 transmits display inquiry information (display inquiry, notification ID, viewer ID, business operator ID, distribution destination folder ID) to the DB server 400 via the low-capacity content distribution server 1100. Then, the storage / delivery destination folder determination unit 983 is notified of the display inquiry (d111).

  As shown in FIG. 19, the display presence / absence notifying unit 431 of the DB server 400 receives display inquiry information from the viewer terminal 900, assigns a notification basic information master having the notification ID and the operator ID, and It is determined whether the reproduction flag of the information master is automatic reproduction or manual reproduction (d114).

  The display presence / absence notification unit 431 determines the manual mode in the case of manual reproduction. In the case of the manual mode, the distribution destination folder master having the distribution destination folder ID and the operator ID of the display inquiry information is assigned, and whether or not the folder passage flag of this master indicates “pass” or “do not pass”. Judgment is made (d115).

  Then, the determination result is returned as display inquiry response information (enterprise ID, viewer ID, notification ID, presence / absence of passage, distribution destination) via the low-capacity content distribution web server 1100 (d116).

  When it is determined that “pass”, it is returned as display inquiry response information to which the distribution destination folder ID of the movement destination of the distribution destination folder master is added. When it is determined that “does not pass”, the distribution destination folder ID of the distribution destination folder master is added.

  That is, it is determined on a business unit basis whether or not the notice title read on the detailed screen is to be displayed, and the result is notified to the viewer terminal.

  In other words, depending on the type of business, it may not be preferable to distribute it as today's notice. This is delivered regardless of the business if the content of the announcement title is 15 minutes away. For example, government office relations, neighborhood association relations, department store or soup time sales may be appropriate today, but for example, if it is an announcement from a cooking school manager, it is not appropriate today. For this reason, when the detail screen is today, it is stored in the recipe folder (viewer terminal side) without presenting the cooking class today.

  As a result, a notice appropriate for today's notice can always be displayed on the viewer screen.

  The distribution destination folder master stores the notification ID in association with the distribution destination folder master. The distribution destination folder master having the notification ID of the display inquiry information, the distribution destination folder ID, and the business operator ID is assigned. It may be determined whether or not “Yes” or “No pass” is indicated, and the result may be notified.

  That is, it may be determined whether or not to display each notification title on the detailed screen (today).

  On the other hand, the title display presence / absence inquiry unit 982 of the viewer terminal 900 receives the display inquiry response information and determines whether “does not pass” or “passes” is indicated (whether it is displayed) (d117). ).

  When it is determined that “does not pass” (display) is displayed, the read notification title information is stored in the detailed screen display memory 910 and the notification title A1 is displayed as shown in FIG. 30A (d118). ). Note that the trash can icon B1 of the notification title A in FIG.

  At this time, the storage delivery destination folder determination unit 983 stores the notification title information in the delivery destination folder corresponding to the delivery destination folder ID included in the display inquiry response information (for example, today's folder) when “does not pass”. .

  In addition, the title display unit 980 transmits the business ID, the viewer ID, the notification ID of the notification title displayed on the detailed screen, and the displayed time to the DB server as log information (d121).

  The post-session log creation unit 490 of the DB server 400 writes this log information to log information having a business ID, a viewer ID, and a notification ID (d122).

  Further, when the display inquiry response information indicates that the display inquiry response information is not displayed (passed), the storage distribution destination folder determination unit 983 has a distribution folder ID (for example, PTA) of the movement destination included in the display inquiry response information. Is stored in the distribution destination folder of the main item screen memory 920 corresponding to (d125). That is, it is not displayed on the details screen.

  Next, the storage / delivery destination folder determination unit 983 uses the viewer ID, the notice ID, and the destination delivery destination folder ID of the notice title information stored in the destination delivery destination folder as low-volume content delivery as the notice destination information. The data is transmitted to the DB server 400 via the server 1100 (d126).

  The unread count updating unit 442 of the DB server 400 receives the notification destination information, assigns the unread list 443 having the viewer ID and the distribution destination folder ID, and the unread count associated with the distribution destination folder ID of the unread list. Is updated (increased by 1) (d127).

  In the unread list 443, as shown in FIG. 31, the distribution destination folder ID of the item (distribution destination folder name) provided by the business entity is associated with the combination of the business operator ID and the viewer ID, and the number of unread items is associated. ing.

  Then, the process returns to step d87, the next notice title information is read, and the presence or absence of display is judged by the DB server and displayed (d128). Accordingly, the notification titles are sequentially displayed as shown in FIG.

  Further, as shown in FIG. 20, the detail display unit 980 of the viewer terminal 900 monitors whether or not the notification title on the detail screen is touched (d131).

  When it is determined that the notification title is not touched, the title deletion unit 990 monitors whether or not the deletion icon in the notification title is selected (touched), and if not touched, returns the process to d131 to input the touch. Wait (d132).

  When the deletion icon is selected (touched), the title deletion unit 990 displays the notification ID of the notification title, the deletion command, the viewer ID, the provider ID, the current item name (distribution destination folder ID) of the detailed screen, and the like. Login reception / distribution web server (including URL of login reception / distribution web server, 1100 address, DB server address) as notification title deletion information (shown as URL with notification ID in FIG. 20) 1000 (d134).

  The login acceptance / distribution web server 1000 transmits the notification title deletion information to the low-capacity content distribution server 1100 (d136). That is, the notification title deletion information is distributed so as to be transmitted to the corresponding low-capacity content distribution server 1100 (d135).

  The low-capacity content distribution server 1100 sets the notification title deletion information to the DB server 400 (d137).

  The post-session log creation unit 490 of the DB server 400 reads the notification title deletion information, assigns a log having the notification ID, the viewer ID, and the business operator ID, and sets a deletion flag (“1”) (d138).

  Further, the unread count update unit 442 of the DB server 400 reads the notification title deletion information, assigns an unread list record having a distribution destination folder ID, a viewer ID, and an operator ID, and updates (subtracts 1) the unread count. (D139).

  On the other hand, if the detail acquisition unit 920 of the viewer terminal 900 determines that the notification title on the detail screen has been touched, the notification title is displayed by color.

  The detail display unit 980 of the viewer terminal 900 displays a notification ID of the notification title, a command for touching the notification title, a viewer ID, a provider ID, a touch time (manual playback date and time), etc. (1000 URL, 1100, 400 address) Are sent to the login acceptance / distribution web server 1000 as notification title touch information (indicated as URL with notification ID in FIG. 20) (d140).

  The login reception / distribution web server 1000 distributes and transmits the notification title touch information to the low-capacity content distribution server 1100 (d141, d142).

  The low-capacity content distribution server 1100 transmits the notification title touch information to the DB server 400 (d143).

  The detailed screen information providing unit 441 of the DB server 400 reads the notification title touch information, and acquires the detailed content having the notification ID, the viewer ID, and the business operator ID from the detailed content database 444 (d144).

  Then, the detailed screen information providing unit 441 adds the viewer ID and the notice ID to the acquired detailed content and transmits (HTML) to the low-capacity content distribution server 1100 (d145).

  The low-capacity content distribution server 1100 receives this, and transmits detailed content to this viewer ID (d146).

  The detailed display unit 920 of the viewer terminal 900 receives the detailed content and displays it on the detailed screen (d147; see FIG. 32A).

  Then, the detail acquisition unit 920 sends a log creation request (viewer ID, company ID, notification ID, detailed content ID, playback start time, playback) using the current time of the timer 970 as the playback start time. (D148).

  The low-capacity content distribution server 1100 transmits this log creation request to the DB server 400 (d149).

  The detailed screen providing unit 441 of the DB server 400 allocates a log having a viewer ID, a provider ID, and a notification ID of the log creation request, and writes the reproduction start time included in the log creation request (d150).

  Further, the unread count update unit 442 allocates an unread list having a viewer ID, a company ID, a notice ID, and a detailed content ID, subtracts “1” from the corresponding unread count and subtracts 1 from the total (d150). .

  Further, when the detailed content on the detailed screen is displayed, if a video icon is selected, a video request (viewer ID, business ID, notification ID, detailed content ID, video, 1000 URL, 1200, 500 (Including the address) is transmitted to the login acceptance / distribution server 1000 (d152).

  The login acceptance / distribution server 1000 distributes and transmits the moving image request to the corresponding storage server 500 (d153, d154).

  The storage server 500 receives the moving image request, allocates the moving image content having the viewer ID, the business ID, the notification ID, and the detailed content ID from the moving image database 520 and transmits it to the viewer terminal 900 (d155).

  The viewer terminal displays the moving image content on the detail screen (d156: see FIG. 32B).

(Auto play: Regular, regular, general)
As shown in FIG. 21, the title display unit 980 of the viewer terminal 900 reads the display inquiry response information of the title display presence / absence inquiry unit 982 when it is determined that the reproduction is not immediately performed in step S89, and performs regular, regular, or general And whether or not automatic is indicated (d161).

  When notified as automatic, it is determined whether or not it is time to display by comparing the display start time of the notice title information with the time of the timer 970 (timer time = display start time) (d162).

  If it is determined that the display time has not been reached, the process returns to step S87 (d163).

  When it is determined that it is time to display, the title display unit 980 performs background processing on the detailed screen of the terminal screen (d164).

  The detailed acquisition unit 920 then sends the URL of the login reception / distribution server 1000 and the low-capacity content distribution pasted to the notification ID, viewer ID, company ID, detailed automatic command, and notification title of the notification title. The address of the web server 1100 and the address of the DB server 400 are transmitted to the login acceptance / distribution web server 1000 as detailed automatic information (described as URL with a notice ID in FIG. 21) (d166).

  The login acceptance / distribution web server 1000 transmits the detailed automatic information to the low-capacity content distribution server 1100 (d167).

  The low-capacity content distribution server 1100 sets the detailed automatic information to the DB server 400 (d168).

  The detailed screen information providing unit 441 of the DB server 400 reads the detailed automatic information, acquires the detailed content having the notification ID, the viewer ID, and the business operator ID from the detailed content database 444 and views it via the low-capacity content distribution server 1100. To the user terminal 900 (d169, d170).

  The detail acquisition unit 920 of the viewer terminal 900 receives the detailed content and displays it on the details screen (d171; see FIG. 32 (a)).

  Then, the detail display unit 920 sends a log creation request (viewer ID, business ID, notification ID, detailed content ID, playback start time, playback) to the low-capacity content distribution server 1100 using the current time of the timer as the playback start time. To the DB server 400 (d172).

  The post-session log creation unit 490 of the DB server 400 allocates a log having the viewer ID, the business ID, and the notification ID of the log creation request, and writes the automatic playback start time included in the log creation request (d173). .

  In addition, in the case of reproducing a moving image, the viewer terminal 900 displays a moving image in the same manner as described above (d175).

(Live broadcasting)
As shown in FIG. 22, the person in charge of the municipal terminal 100 operates the terminal 100 to register the audio live notification data in the DB server 400 via the administrator web server 300 (d181, d182).

  Also, the administrator web server 300 transmits a viewing log registration request to the DB server 400 (d183).

  The administrator web server 300 transmits live notification information (live ID, title, icon ID, viewer ID) to prepare for audio live to the spray management server 700 (JASON data) (d185).

  The management server 300 receives this live notification information, and creates and transmits it for the number of spray servers (d186).

  In addition, the local government terminal 100 outputs websocket open request management to the management server 300 (d191), and the management server 300 outputs to the spray server management server (d192) along with the registration of the live notification information. The server is outputting to the spray server 1020 (d193).

  On the other hand, the viewer terminal that has received the live notification request from the spray server immediately transmits a response in response to the reception of the live notification request (d188).

  As a result, the viewer terminal enters the voice standby mode (d201).

  On the other hand, as shown in FIG. 23, the person in charge of the municipality terminal 100 inputs voice from a microphone (not shown), and the municipality terminal 100 encodes this and transmits it to the administrator web server 300 (d202).

The administrator web server transmits this to the spray management server 700 (d203), and the spray management server transmits to the spray server (d204).

  Then, the spray server transmits the audio data to the corresponding viewer terminal (d205).

  Upon receiving the audio data, the viewer terminal immediately reproduces (live reproduction) (d209).

  On the other hand, when the person in charge presses the live end button, the local government terminal 100 immediately transmits a close signal to the spray server via the management server 300 and the spray management server (d210, d211, d212).

  Also, the viewer terminal starts a timer for 4 minutes after the start, and transmits a socket close to the spray server after 4 minutes (d213).

<Embodiment 2>
In the first embodiment, the business operator that registers the notification information has been described as one local government. However, a plurality of business entities may exist in the area. In such a case, the viewer side wants to receive desired notification information from the A company and the B company. However, the number distributed to viewers in a certain period is limited. Even in such a case, the second embodiment distributes the notification information desired by the viewer.

  FIG. 33 is a schematic configuration diagram of the DB server according to the present embodiment. As shown in FIG. 33, the administrator web server 300 is connected to a plurality of operator terminals 100a, 100b,.

  The DB server 400 has a viewer-by-viewer notification change processing unit 401.

  The viewer-by-viewer change processing unit 401 stores an actual distribution list GHi (“viewer A ID, notification ID, company ID, distribution date, notification title, and icon ID”, “ When the viewer B's ID, notification ID, business ID, distribution date, notification title, and icon ID "..." are stored, the number of the actual distribution list GHi is designated, and the actual distribution list Ghi of this number is designated. (Hereinafter, notification distribution actual information Mi (“viewer A ID, notification ID, business ID, distribution date, notification title, and icon ID”) is deleted in the past, It is changed to the notification distribution actual information Mi of the content similar to the notification ID of the business operator and distributed.

  FIG. 34 is a schematic configuration diagram of the viewer notification change processing unit 401 of the DB server. As shown in FIG. 34, it has a notification title deletion unit 405, a past reproduction maximum notification ID determination unit 406, a similar content determination unit 407, a notification update unit 408, and the like. In addition, the viewer master 471 is used. This viewer master 471 further associates the viewer's age, sex, desired genre type (content type), and distribution-permitted carrier ID in addition to the items shown in FIG. These are referred to as attribute information Hsgi.

  In addition, the content master 444 is used. The content master 444 corresponds to the URL of the basic notification information (FIG. 9), and the actual content (details) is linked to the content type.

  In the memory 481 (batch distribution memory), notification distribution actual information Mi to be displayed on the viewer terminal 900 15 minutes ahead is stored in units of businesses.

  The notification deletion unit 405 designates the actual distribution list GHi of the batch distribution memory 481 (in units of one), and the past log information Fi having the viewer ID, notification ID, and business ID of the notification distribution actual information Mi. Is deleted from the memory 415, and if the deletion flag is set, the intelligent distribution actual information Mi is deleted.

  The past reproduction maximum notification ID determination unit 406 reads the viewer ID attribute information Hsgi (gender, desired genre, age, area) of the designated notification delivery actual information Mi from the viewer master, and is most similar to the attribute information Hsgi. The viewer information Sgi to be determined is determined from the viewer master, and the past log information Fi having the distribution folder ID related to the notification distribution actual information Mi and the viewer ID of the viewer information Sgi is determined from the distribution schedule information master for all businesses. The notification ID with the largest number of playbacks is determined (IF).

  The similar content determination unit 407 reads the content type Pi related to the determined notification ID from the content master, and reads all the notification basic information having this URL from the notification basic information master to determine a similar content type Ppi.

  The notification update unit 408 reads the notification ID of the notification basic information of other businesses having the content type Ppi that is regarded as similar, and the notification title, the notification ID of the notification basic information of this notification ID, the icon ID, The display time is stored in the memory 481 as new notification distribution actual information Mi (S45).

  35 and 36 are flowcharts for explaining the operation of the DB server according to the second embodiment.

  The notification deletion unit designates an actual distribution list (enterprise unit, viewer unit) in the batch distribution memory, and reads the notification distribution actual information Mi (S31).

  Next, the past log information Fi having the viewer ID, notification ID, and business ID of this notification distribution actual information Mi is read from the viewer log master (table) 413 (S32).

  Then, it is determined whether or not a deletion flag is set in the past log information Fi (S33).

  If the deletion flag is set in step S33, the notification delivery actual information Mi read in step S31 is deleted (S34).

  In addition, the past playback number maximum notification ID determination unit 406 reads from the viewer master 471h the attribute information Hsgi (gender, desired genre, age, area) of the viewer ID of the notification distribution actual information Mi read in step S32 (S35). ).

  Next, the past playback count maximum notification ID determination unit 406 determines the viewer information Sgi most similar to the attribute information Hsgi from the viewer master (S36).

  Next, the distribution folder ID related to the notification distribution actual information Mi is read from the distribution schedule information master 473 (S37).

  Then, the past log information Fi having the distribution destination folder ID and the viewer ID of the viewer information Sgi is searched over all businesses to determine (IF) the notification ID having the largest number of reproductions (S38).

  Then, as shown in FIG. 36, the similar content determination unit 407 reads the content type Pi related to the determined notification ID from the content master 444 (S39).

  Specifically, the content master 444 is classified by content (genre) type (PTA, government office, cuisine, market, event, etc.).

  The notification basic information master 473 stores the notification ID and the content master URL associated with each other.

  That is, the basic notification information having the determined notification ID is allocated, the URL included in the basic notification information is read, and the content type of the content master is read using this URL as a key.

  Then, the similar content determination unit 407 reads all the notice IDs of the notice delivery actual information Mi (except for deleted information) in the memory 481 (S40), and reads the content types of these notice IDs (S41). Then, it is determined whether there is a content type Ppi similar to the content type Pi read in step S39 (S41).

  Specifically, all basic notification information having these notification IDs is read from the basic notification information master, and all URLs of contents related to these notification IDs are read.

  Then, the content type of the content master is read using these URLs as keys, and a content type Ppi similar to the content type Pi is determined (a weighting function or the like may be used).

  Next, the notification update unit 408 reads the notification basic information of the distribution list of another business having the content type Ppi that is regarded as similar from the notification basic information master (S43), and is associated with this URL. The notification ID is read (S44).

  Then, the notice ID, the notice title of the notice basic information of the notice ID, the icon ID, and the display time are stored as new notice distribution actual information Mi (S45) in the memory 481 (S46).

  Specifically, the basic notification master information of another business operator having a similar content type Ppi URL is searched, and the notification ID of the basic notification information associated with this URL is passed to step S45. (See FIG. 37).

  Next, it is determined whether or not there is actual distribution list information Mi of the actual distribution list other than the actual distribution information Mi read in step S31 in the memory. If there is no other actual distribution list, the process ends (S47).

  If it is determined in step S47 that there are others, the distribution list is updated to the next distribution list, and the process returns to step S31 (S38).

  That is, as shown in FIG. 38A, when A1,... A6 are displayed as notification titles displayed on the detail screen of the viewer A, for example, A5 is deleted.

  Further, as shown in FIG. 38 (b), when the notice title displayed on the viewer A's detail screen is A1,... A6, for example, C1 instead of A2 Stuff) announcement title will be displayed.

  Therefore, in the second embodiment, since what has been deleted in the past is not distributed, only the desired notification can be received for the viewer.

  Moreover, even if it deletes, since the viewer can receive the similar notification which a viewer desires, only the notification which he desires can be received.

<Other embodiments>
As shown in FIG. 39, the management company terminal 200 receives information from the river company terminal 50, the weather company terminal 60, the road management company, the gas company, the water company, etc. You may send it as an announcement.

  In addition, as shown in FIG. 40, this cloud system, prefectural police terminal, police officer terminal (tablet or smart horn) are connected via a communication network, and information (crime occurrence, emergency, patrol instructions, etc.) to be transmitted to the police officer is described above. It may be distributed as a notification.

  Further, for example, the presenter's terminal may be carried by a moderator at a television station so that an announcement relating to today's program may be distributed.

400 DB Server 410 Notification Title Distribution Processing Unit 420 Display Passage Determination Processing Unit 430 History Registration Processing Unit 440 Detailed Distribution Processing Unit Description of Code 600 Batch Server 700 Spray Management Web Server 900 Viewer Terminal 1020 Spray Server 1000 Login Acceptance / Distribution Web Server 1100 Low-capacity content delivery web server

Claims (9)

A notification interactive communication system in which an operator terminal of an operator who registers an announcement of an area, a viewer terminal of a viewer, and a notification service center connected via a communication network,
The announcement service center
A push route section to the viewer terminal is constructed by a spray web server section having a plurality of spray servers and a batch server section having a batch server, and further a low-capacity content signal having a plurality of content distribution web servers. The web server unit constructs a pull route unit that accepts access from the viewer terminal, transmits various information after login from the pull route unit, and the push route unit transmits detailed information of the notification registered by the operator. Connect the notification service providing server that sends the notification title information,
The notification service providing server is:
Control data for causing the viewer terminal to generate notification title information storage means for sequentially storing the notification title information;
Control data to be divided into an item screen for displaying a service item of an operator on the viewer terminal and a detail screen for displaying details of the service item;
Control data for causing the viewer terminal to generate a memory for an item screen, a memory for the detailed screen, and
Control data for generating a folder for the service item in a memory for the item screen;
With the selection of the service item on the item screen, control data for displaying the service item on the detail screen via the memory for the detail screen;
The notification title information stored in the notification title information storage means is read, and each time the read information is read, whether or not to pass the detailed screen to the notification service center is displayed on the detailed screen. Control data to be added to the service item name folder ID and transmitted to the notification server center;
When the passage response result information for the passage presence / absence inquiry information is received from the notification service center and the passage response result information indicates that the passage does not pass, the notice title of the read notice title information is read for the detailed screen. Control data to be displayed on the detailed screen via a memory and to store the read notification title information in a folder indicated by the passing response result information;
If the passage response result information indicates passing, the notification title information of the destination service item included in the passage response result information is not displayed without displaying the notice title of the read notice title information. And means for transmitting the control data to be stored in the folder having the folder ID via the pull route unit,
further,
The notification service providing server is:
In the detailed screen of the service provider name, the service item name, the service item name, the passage presence / absence flag indicating that the notification title is to be passed or not passed, the folder ID of the moving destination when passing, or the case of not passing A notification title passage presence / absence master in which notification title passage presence / absence information associated with the folder ID is stored;
When the passage presence / absence inquiry information is received from the viewer terminal, the information includes the business ID included in the passage presence / absence inquiry information, the viewer ID, and the ID of the service item name displayed on the detailed screen. Means for reading notification title passage presence / absence information from the notification title passage presence / absence information master;
Means for transmitting the read notification title passage presence / absence information to the viewer terminal in the pull route unit;
An announcement bidirectional communication system characterized by comprising: The notification service providing server is:
A notification basic information master storing notification basic information including a notification title from the provider terminal, a notification ID of the notification title, a user ID, a provider ID, and a display start time of the notification title on the viewer terminal; ,
With a timer that measures the current time,
Means for obtaining a time obtained by adding a certain time to the current time of the timer as a certain predecessor delivery time;
The basic notification information having the predetermined post-delivery time is read from the basic notification information master, and the notification ID, notification title, user ID, and display start time on the viewer terminal are generated as the notification title information. Means to
Means for transmitting the announcement title information to the viewer terminal via the batch server of the push route unit and the spray server unit;
The announcement bidirectional communication system according to claim 1, further comprising: The notification service providing server includes:
A viewer master that stores viewer information including a viewer ID and an IP address of the viewer terminal,
When the notification title information is transmitted to the batch server unit, all viewer IDs having user IDs included in the notification title information and their IP addresses are read from the viewer master, and these are read as the notification title. The notification two-way communication system according to claim 1 or 2, further comprising means for transmitting the information added thereto. The notification service providing server is:
A distribution schedule information master, which is transmitted to the viewer terminal and registered in association with distribution schedule information including a folder ID and a user ID of a service item name provided by a provider in the area;
A per-viewer log table stored as log information to the viewer terminal, including the provider ID, notification ID, user ID, and folder ID of the service item of the distribution schedule information,
Accompanying the transmission of the notification title information to the batch server unit, the notification ID of the notification title information, the business ID, and the user ID are returned, and the folder ID of the service item of the distribution schedule information having these is returned. And means for assigning log information having the notification ID, business ID, and user ID returned from the batch server unit from the log table for each viewer,
Means for writing the read folder ID in the allocated log information;
When the delete title is included in the notification title and displayed, and the delete icon is selected, the notification ID of the selected notification title, the operator ID, the user ID, the deletion flag, and the current detail screen are displayed. Means for returning the folder ID of the service item as title deletion information via the pull route unit;
A means for assigning the log information having a business ID, a notice ID, a user ID, and a folder ID of title deletion information, setting a deletion flag to the log information, and obtaining a deletion history. The interactive two-way communication system according to 1, 2, or 3. The notification service providing server is:
A detailed information content server storing detailed information of the notification title information in association with a notification ID, a viewer ID, and an operator ID;
When the touch information of the announcement title is received from the viewer terminal via the pull route unit, the detailed information including the business operator ID, the announcement ID, and the user ID included in the touch information is allocated, 5. The interactive bi-directional communication system according to claim 1, further comprising means for transmitting an instruction to be displayed on the detailed screen of the viewer terminal via the pull route unit. A storage server storing moving image content including sound associated with the notification ID, user ID, and business ID,
The interactive two-way communication system according to any one of claims 1 to 5, further comprising a low-capacity content distribution server unit that connects the viewer terminal and the storage server to transmit the moving image content.   After the session is established between the push route unit spray server unit, the pull route unit low-capacity content distribution web server and the large-capacity content distribution web server and the viewer terminal, it is confirmed that the session is continued by ping / ping. The interactive two-way communication system according to any one of claims 1 to 6.   The viewer terminal transmits reconnection requests to the spray server unit of the push route unit, the low-capacity content distribution web server and the large-capacity content distribution web server of the pull route unit at regular time intervals. The notice bidirectional communication system according to any one of 1 to 7. A viewer terminal that receives notification service information on a communication network from the notification service center and displays it on a screen,
Notification title information storage means for sequentially storing the notification title information from the notification service center;
Means for dividing an item screen for displaying the service items of the business operator and a detail screen for displaying details of the service items;
A memory for the item screen, a memory for the detail screen,
Means for generating a folder for the service item in the item screen memory, and the service item is displayed on the detail screen via the memory for the detail screen in accordance with the selection of the service item on the item screen. Means,
The notification title information stored in the notification title information storage means is read, and each time the read title information is read, whether or not to pass the detailed screen or currency information is displayed on the detailed screen. Means for adding the folder ID of the service item name to be transmitted,
When the passage response result information for the passage presence / absence inquiry information is received from the notification service center and the passage response result information indicates that the passage does not pass, the notice title of the read notice title information is read for the detailed screen. Means for displaying on the details screen via a memory, and storing the read notice title information in a folder ID indicated by the passage response result information;
If the passage response result information indicates passing, the notification title information of the destination service item included in the passage response result information is not displayed without displaying the notice title of the read notice title information. And a means for storing in a folder having a folder ID.

Images