JP6425472B2 - Notification delivery system - Google Patents

Description

  The present invention manages a plurality of information providers at one place, allows the viewer to select the information provider and set the information distribution period and the display color, and allows the terminal of the viewer connected to the Internet network. The present invention also relates to a notification distribution system that manages and distributes information provided by an information provider into a title distributed in a push type system and content distributed in a pull type system.

  There are various services for bi-directional communication of information transmission via the Internet network. In the information distribution method for providing information by this two-way communication, the viewer on the information acquirer side takes the initiative and the viewer accesses the server on the information provider side when the information is needed. In the pull type method to obtain the target information, and conversely, the information provider side takes the initiative and automatically sends periodically the information requested by the viewer who is the information acquirer to the terminal of the viewer. There is a push type method to provide.

  In the pull type method, for example, information is disclosed on a home page established by a local government, a company, a university, etc. by a www server, a database server, etc., and the target is accessed by the viewer when necessary. Provide information.

  On the other hand, in the push type method, information can be distributed without requiring any operation to the viewer on the information acquirer side. For example, information on event information, advertisement information, stock price information, evacuation information, etc. is provided. It can be delivered at the provider's provision timing.

  There are some which were described in patent documents 1 and 2 as art about a push type method. Patent Document 1 describes a technique for providing information to a receiving contractor by push distribution by determining the timing of providing information and the content of the information to be provided according to the position and time of the receiving contractor. .

  Further, in Patent Document 2, when it is detected that the mobile phone carried by the viewer is in the specific area, the moving image information on the specific area is pushed from the video content server to the mobile phone. The technology to deliver at is described.

JP 2002-278886 A Patent No. 4073819

  In the push type delivery method, the viewer can automatically receive the information without performing operations such as searching for information related to the purpose and accessing the corresponding home page, so convenience is good, but each information in advance You need to register on the distribution site.

  However, such information distribution sites are often opened for each company, and it is troublesome for the viewer to search for the information distribution sites and register them one by one.

  In addition, although local governments etc. disclose important information about a specific area, most are only the delivery method of the pull type system, and information can not be effectively provided to viewers.

  Therefore, if a plurality of information providers are managed in one place, the viewer registers with the management source, and selects an information provider who wants information to be distributed, the information of these information providers can be obtained. There is a need for a service that is automatically delivered in a push-type manner.

  In addition, as described in Patent Documents 1 and 2, information on a specific area is distributed when it is detected that the area is located in the area based on the position information of the portable terminal of the area viewer. Often.

  In other words, information about a specific area will not be distributed unless the viewer goes to the site.

  However, information on a specific area, such as tourist information and event information, is delivered before the viewer arrives at the site, and is therefore effectively used for travel planning and schedule planning. The method of detecting the presence of the viewer and determining the provision timing based on the position information of the terminal is not effective.

  It is better for viewers considering future migration and travel to be able to constantly collect information on multiple candidate sites.

  Therefore, it is desirable to allow the viewer to set the information distribution period, and within the set information distribution period, a service is desired in which information related to a specific area is always delivered by a push type method regardless of the location of the viewer.

  On the other hand, as described in Patent Document 2, in the technology of distributing content such as moving image information in a push type system, the distributed content is stored in the portable terminal of the viewer.

  However, from the memory consumption of the portable terminal and the charge of the data communication fee, it is possible for the viewer to deliver at least large-capacity content such as moving image information in a push type system one after another at the provision timing of the information provider. Not desirable.

  Therefore, the information provided by the information provider is divided into a title indicating the content of the distribution information and the content, and only the title is distributed by the push type method, and only specific content that is determined necessary by the viewer is pulled It is desirable to have services delivered by type system.

  In order to solve the above problems, the present invention manages a plurality of information providers at one place, and allows the viewer to select an information provider and set an information distribution period and a display color to provide information. It is an object of the present invention to obtain a notification distribution system in which information provided by a person is divided into a title distributed in a push type system and content distributed in a pull type system and managed and distributed.

The notification distribution system of the present invention comprises a distribution cloud (10), an administrator terminal (20) connected to the distribution cloud (10) via the Internet network N, a distributor terminal (30a, 30b), and It is a notice delivery system comprised by a viewer terminal (40n), and
The distribution cloud (10) is
A database server (60), a distribution management server (70) connected to the database server (60), and an announcement distribution server (81a, 81b) connected to the distribution management server (70);
The database server (60) is
A distributor information database (201) in which distributor registration information (Hn) to which a distributor ID is assigned and a distributor-specific distribution destination list (LHn) associated with the distributor ID are stored;
A viewer information database (202) in which viewer registration information (Cn) to which a viewer ID is assigned and a distributor selection list (LCn) associated with the viewer ID are stored;
A server memory (204) in which notification basic information (MKn) included in notification information Mn to which a notification ID is assigned is registered;
A distributor selection format in which all the distributor IDs and distributor names registered in the distributor registration information (Hn) are set is transmitted to the viewer terminal (40n).
The distributor selection information (HSn) with distribution selection and distribution period set in the distributor selection format returned from the viewer terminal (40n), the distributor selection list of the viewer information database (202) Save to (LCn),
The viewer ID set in the distributor selection list (LCn) in the distributor-specific distribution destination list (LHn) corresponding to the distributor ID selected as the distribution desired by the distribution selection is the distribution destination viewer A distributor setting unit (110) for adding as an ID and further setting the distribution period;
The distribution destination viewer ID and the distribution period are read out from the distribution destination list by distributor (LHn) corresponding to the distributor ID included in the notification basic information MKn every fixed time, and within the distribution period The distribution data extraction unit (105) creates distribution data (HDn) by adding the notification basic information MKn to the distribution destination viewer ID, and stores the distribution data (HDn) in the distribution list (DT) of the server memory (204). When,
It includes a title distribution unit (106) which reads out the distribution data (HDn) stored in the distribution list (DT) at regular time intervals and transmits the data to the distribution management server (70).
The delivery management server (70) is
Means of transferring the distribution data (HDn) transmitted from the database server (60) to the notification distribution server (81a, 81b) assigned to the distribution destination viewer ID included in the distribution data (HDn) Including
The notice distribution server (81a, 81b)
It includes means for distributing the distribution data (HDn) transmitted from the distribution management server (70) to the viewer terminal (40n) of the distribution destination viewer ID included in the distribution data (HDn),
The viewer terminal (40n) is
Terminal memory (48),
The distributor specific setting information (HSn) in which the distribution selection and the distribution period are set in the distributor selection format received from the database server (60) is stored in the terminal memory (48), and the database A display setting unit (43) that replies to the server (60);
Receiving the distribution data (HDn) distributed from the notification distribution server (81a);
When a folder (Fn) with the distributor name included in the distribution data (HDn) is already created in the terminal memory (48), an unread flag "1" is added to the distribution data (HDn) Save in the folder (Fn),
A distribution information receiving unit (44) for creating and storing a folder (Fn) to which the distributor name is newly added, if not created;
A tab (TGn) with the distributor name corresponding to the folder (Fn) created in the terminal memory (48) is generated, and is stored in the folder (Fn) in the area of the tab (TGn). A summary of the present invention is to include a title display section (45) for displaying a list of the titles of the distribution data (HDn) according to the notification display color included in the distribution data (HDn).

  The notification distribution system of the present invention manages a plurality of information providers at one place, allows the viewer to select the information provider and set the information distribution period and display color, and the information provided by the information provider Can be divided into a title delivered in a push scheme and content delivered in a pull scheme, and can be managed and delivered.

Configuration of information registration and push method delivery of the notice delivery system of the present invention Configuration diagram concerning pull method delivery of the notice delivery system of the present invention Data structure of distributor information database Data structure of audience information database Data relationship diagram of distributor information database and viewer information database Data structure of notification information Data structure of distribution list Data structure of log list Data structure of distribution server list by viewer Data structure of distribution server list by session Viewer Terminal Configuration Diagram Sequence diagram of distributor information registration process Sequence diagram of notification information registration process Sequence diagram of notification information registration process Viewer terminal information setting screen image Notification information display screen image of viewer terminal Sequence diagram of viewer information registration process (viewer information registration) Sequence diagram of viewer information registration process (login) Sequence diagram of viewer information registration process (session establishment) Sequence diagram of distributor selection and display condition setting process Sequence diagram of notification basic information extraction process and push method notification basic information distribution process Sequence diagram of notification basic information extraction process and push method notification basic information distribution process Sequence diagram for low capacity of pull method detailed information distribution process Sequence diagram for low capacity of pull method detailed information distribution process Flow chart of distributor setting unit Flow chart of distribution data extraction unit Flow chart of title distribution unit Flow chart of distribution information receiver Flow chart of title display section Flow chart of the title deletion unit Flow chart of content acquisition unit Flow chart of the log update unit Data configuration diagram of the distributor selection list in the second embodiment Data configuration diagram of distributor-specific distribution destination list in the second embodiment Screen image of the viewer terminal in the second embodiment Flowchart of Distributor Setting Unit in Second Embodiment Flowchart of Delivery Data Extraction Unit in Second Embodiment Title display screen image of the viewer terminal in the second embodiment Title display screen image of the viewer terminal in another embodiment

  The notification distribution system of the present invention, as exemplified in FIG. 1, includes a distribution cloud 10 constructed by a plurality of servers, an administrator terminal 20 connected to the distribution cloud 10 via the Internet network N, and distribution. The terminal 30a, 30b, and the viewer terminal 40n.

  The notification distribution system of the present invention is used by the distributor terminals 30a and 30b to a local government, company, notification service provider, sports event, department store, supermarket, etc. who carries out distribution of information (hereinafter collectively referred to as a distributor). The notification information Mn is registered in the distribution cloud 10, and the notification basic information MKn among the registered notification information Mn is distributed from the distribution cloud 10 to the viewer terminal 40n of the viewer by the push method, and the details of the notification information Mn The information MSn is acquired from the distribution cloud 10 by the viewer terminal 40 n of the viewer in a pull method.

  In the embodiment of the present invention described below, as an example of a distributor, a district (such as Matsue City, Shimane Prefecture, Chiyoda Ward, Tokyo, etc.) is controlled as an example of a distributor, and information mainly related to that district is mainly used. The audience is listed as people who live throughout the country.

  The viewer terminal 40n owned by the viewer may be any terminal capable of data communication via the Internet, such as a smartphone, a tablet, a personal computer, a television with an internet interface, etc. In the following description, , Mobile phones such as smart phones and tablets are taken as an example.

  In the embodiment of the present invention, there are a plurality of servers and data, respectively, and such servers and data are indicated by the symbol "n". When it is described as the code "n" in the description, it may be any of a, b, c, ..., 1, 2, 3, ... and is not specified as "n". .

  Among the plurality of servers and data, in the case where they can be clearly distinguished, the symbols are identified by appending a, b, c to the code.

<First Embodiment of the Present Invention>
In the notification distribution system according to the first embodiment of the present invention, as shown in FIG. 1, a manager terminal 20, a distributor terminal 30a of a distributor of A area, and a distributor terminal 30b of a distributor of B area. The viewer terminal 40 n is connected to the distribution cloud 10 via the Internet network N.

  Actually, a plurality of distributors and a plurality of viewers can be connected to the distribution cloud 10.

(Configuration of Distribution Cloud 10 in the First Embodiment of the Present Invention)
As for the configuration of the distribution cloud 10 in the first embodiment of the present invention, FIG. 1 shows the means related to registration of various data and the means related to push method distribution, and FIG. The relevant means are shown.

  Actually, a plurality of distributors and a plurality of viewers can be connected to the distribution cloud 10.

  As shown in FIGS. 1 and 2, the distribution cloud 10 includes a system management server 50, a database server 60, a storage server 61, low capacity content distribution servers 62a and 62b, and large capacity content distribution servers 63a and 63b. , And the distribution management server 70, the session establishment server 80, and the notification distribution servers 81a and 81b.

  The system administrator accesses the system management server 50 from the administrator terminal 20 via the Internet network N, manipulates the data of the distributor and the data of the viewer stored in the database server 60, and the configuration regarding the system construction Management data (not shown) etc. are set.

  The distributor in the A area and the distributor in the B area access the system management server 50 from the distributor terminal 30a and the distributor terminal 30b via the Internet network N, respectively, and the database server 60 receives the notification basic information MK1 and The notification information M1 including the detailed information MS1, and the notification information M2 including the notification basic information MK2 and the detailed information MS2 are registered.

  The viewer accesses the distribution management server 70 from the viewer terminal 40 n via the Internet network N to establish a session, and from any of the plurality of notification distribution servers 81 a, 81 b,. The notification basic information MKn of the notification information Mn is distributed to the viewer terminal 40 n by the push method.

  In addition, the viewer accesses the distribution management server 70 via the Internet network N by tapping the notification basic information MKn displayed on the viewer terminal 40n, and a plurality of detailed information MSn of the desired notification information Mn is obtained. The low-volume content distribution servers 62a, 62b,... Or the large-capacity content distribution servers 63a, 63b,.

  Specific communication sequences and processing procedures will be described later.

  The system management server 50 is connected to the database server 60, transfers data received from the administrator terminal 20 and the distributor terminals 30a and 30b to the corresponding processing means of the database server 60 according to the type, and from the database server 60 Reply data to the sender.

  The database server 60 is connected to the system management server 50, the storage server 61, the low-capacity content distribution servers 62a and 62b, and the distribution management server 70 as shown in FIG. 1 and FIG. 101, distributor authentication unit 102, input screen provision unit 103, notification information registration unit 104, distribution data extraction unit 105, title distribution unit 106, text transmission unit 111, log update unit 107, viewing and listening A person registration unit 108, a viewer authentication unit 109, and a distributor setting unit 110 are included.

  Furthermore, as shown in FIG. 1, the database server 60 includes a distributor information database 201, a viewer information database 202, a screen configuration information master 203, and a server memory 204 as storage means.

  In the distributor information database 201, distributor registration information Hn and a distributor-specific distribution destination list LHn are stored.

  In the viewer information database 202, viewer registration information Cn and a distributor selection list LCn are stored.

  In the screen configuration information master 203, a notification information format for the distributor to input the notification information Mn is stored so that when the distributor registers the notification information Mn, there is no omission in registration or an error.

  The server memory 204 stores notification basic information MKn, text detailed information MSn, a distribution list DT, and a log list GT.

  As shown in FIGS. 1 and 2, the storage server 61 is connected to the database server 60 and the large-capacity content distribution servers 63a and 63b, and includes a moving picture registration unit 112 and a moving picture transmission unit 113 as processing means. And storage 301 in which detailed information MSn of the moving image is stored.

  The low-capacity content distribution servers 62a and 62b are connected to the database server 60 and the distribution management server 70 as shown in FIG. 2, and distribute the text detailed information MSn to the viewer terminal 40n by a pull method.

  As illustrated in FIG. 2, the large-capacity content distribution servers 63a and 63b are connected to the storage server 61 and the distribution management server 70, and distribute the detailed information MSn of the moving image to the viewer terminal 40n by a pull method.

  The distribution management server 70 is connected to the database server 60, the notification distribution server 81, the low-capacity content distribution servers 62a and 62b, and the large-capacity content distribution servers 63a and 63b, and is a variety of distribution servers for distributing notification information Mn for each viewer. It includes a viewer-specific distribution server list CSn defining an address, and transmits / receives various data between the database server 60 and the viewer terminal 40n, and manages distribution of notification information Mn from various distribution servers.

  The address is used when performing data communication, and may be an IP address or the like that can specify the destination of data.

  The session establishment server 80 is connected to the notification distribution servers 81a and 81b, includes a session-specific distribution server list SSn defining the notification distribution server address corresponding to each session, and via the Internet network N, the notification distribution servers 81a and 81b and It performs data transmission and reception for establishing a session with the viewer terminal 40 n.

  The notification distribution servers 81a and 81b are connected to the distribution management server 70 and the session establishment server 80, and distribute the notification basic information MKn in a push format to the viewer terminal 40n via the Internet network N.

(Configuration of various data used in the distribution cloud 10)
The configuration of various data used in the distribution cloud 10 in the first embodiment of the present invention will be described.

  As shown in FIG. 3A, the distributor registration information Hn stored in the distributor information database 201 of the database server 60 includes the distributor ID, distributor name, distributor password, notification display color of each distributor. , H1, H2,..., And Hn, which are data for each distributor, are made up of an icon image ID and an icon image.

  The distributor ID is identification information assigned to each distributor, the distributor name is the name or district name of the distributor (local government etc.) performing the distribution, and the distributor password is for authentication when the distributor accesses the system It is a password. Further, the notification display color is a color (for example, blue, green, pink, red, etc.) specified by the distributor when displaying the notification on the viewer terminal 40 n.

  Furthermore, the icon image ID is identification information attached to the icon image specified by the distributor as a symbol of the distributor to be displayed on the viewer terminal 40n, and the icon image is data of the icon image. The data of the icon image is preferably a character image of a dog, a tree, a cat, etc. that the distributor (for example, Matsue City, Shimane Prefecture, Chiyoda Ward, Tokyo, etc.) originally considered.

  As shown in (b) of FIG. 3, the distributor-specific distribution destination list LHn stored in the distributor information database 201 of the database server 60 includes a distributor ID to be associated with the distributor registration information Hn, and the distributor. Set the viewer ID of each viewer who wants to distribute the content as the first distribution destination viewer ID, the second distribution destination viewer ID,..., The xth distribution destination viewer ID It is comprised by the record which each set the delivery period designated as a period for which a viewer desires delivery.

  In (b) of FIG. 3, in order to show that a plurality of distributor-specific distribution destination lists LHn are stored, the distributor-specific distribution destination lists LH1 of the first distributor ID,. It is listed as the distribution destination list LHn by distributor of the person ID.

  As shown in FIG. 4A, the viewer registration information Cn stored in the viewer information database 202 of the database server 60 is configured by the viewer ID of each viewer, the viewer password, and the registration date and time, The data C1, C2, ..., Cn, which are data for each viewer, are listed.

  The viewer ID is identification information of the viewer input at the time of login, the viewer password is an authentication password input at the time of login, and the registration date is the date registered by the viewer in the main distribution cloud 10.

  As shown in (b) of FIG. 4, the distributor selection list LCn stored in the viewer information database 202 of the database server 60 includes a viewer ID for associating with the viewer registration information Cn, and the cloud 10 for main distribution. The distributor ID and distributor name of each distributor registered in the first distributor ID and first distributor name, second distributor ID and second distributor name,. The n-th distributor ID and the n-th distributor name are set, and distribution selection (0: unnecessary, 1: desired) for each distributor and a distribution period when distribution is desired (always or desired distribution desired) (Start date and end date) are configured by records.

  In (b) of FIG. 4, in order to show that a plurality of distributor selection lists LCn are stored, distribution of the distributor selection list LC1 of the first viewer ID,..., N-th viewer ID is performed. It is listed as the person selection list LCn.

  In FIG. 5, the distributor registration information Hn stored in the distributor information database 201 and the distribution destination list LHn classified by distributor, and the viewer registration information Cn stored in the viewer information database 202 and the distributor selection list LCn are shown. It shows the relationship.

  As shown in FIG. 5, the records of distributor registration information H1, H2, ..., Hn and distributor-specific distribution destination lists LH1, LH2, ..., LHn are associated one by one by distributor ID. It is done.

  Similarly, the records of the viewer registration information C1, C2, ..., Cn and the distributor selection lists LC1, LC2, ..., LCn are associated one by one by the viewer ID.

  Each record of distribution destination list LH 1, LH 2,..., LHn classified by distributor is the distributor ID selection list LC1 of the corresponding viewer ID according to the viewer ID of the viewer who desires the distribution set in the record. , LC2,..., LCn.

  Conversely, each record of the distributor selection list LC1, LC2,..., LCn is a distribution destination list by distributor of the corresponding distributor ID according to the distributor ID of the distributor selected as the distribution request in the record. It is associated with LH1, LH2, ..., LHn.

  Thus, each data can be assigned by using the distributor ID and the viewer ID as keys.

  As shown in FIG. 6, the notification basic information MKn included in the notification information Mn stored in the server memory 204 of the database server 60 includes a notification ID, a distributor ID, a distributor name, an icon image ID, an icon image, and a notification display. Color, title, content type, delivery time, delivery specified date and the like.

  The notification ID is identification information provided for each notification information Mn, the distributor ID is identification information provided for each distributor, the distributor name is the name or district name of the distributor performing the distribution, and the icon image ID is The identification information added to the icon image specified by the distributor as the distributor's symbol to be displayed on the viewer terminal 40n, the icon image is data of the icon image, and the notice display color is a notice on the viewer terminal 40n The title is the content of the notification title to be displayed on the viewer terminal 40n, and the content type is “0: low capacity (text)” or “1: large capacity (video)” The data to specify whether the delivery date is "0: Normal" or "1: Date / time specified". The specified delivery date / time is the notification basic registered when the delivery time is "1: Date specified". Information MK Is the data that specifies the date and time to deliver.

  Since the icon image ID, the icon image, and the notification display color are already set in the distributor registration information Hn, the database server 60 reads and sets from the distributor registration information Hn on the database server 60 side. You may set it when registering.

  Further, as shown in FIG. 6, the detailed information MSn included in the notification information Mn stored in the server memory 204 of the database server 60 is configured by the notification ID, the distributor ID, and the content.

  The notification ID and the distributor ID are set to the same notification ID and distributor ID as the notification basic information MKn in order to be associated with the notification basic information MKn.

  On the other hand, although the content of the detailed information MSn registered by the distributor is text or moving image data, the content of the detailed information MSn stored in the server memory 204 of the database server 60 is only text.

  In FIG. 6, in order to indicate that a plurality of pieces of notification information Mn are registered, notification basic information MK1 and detailed information MS1, notification basic information MK2 and detailed information MS2, notification basic information MK3 detailed information MS3,. The information MKn and the detailed information MSn are listed.

  FIG. 1 shows an image in which the notification basic information MK1 and the detailed information MS1 are registered from the distributor terminal 30a of the A area, and the notification basic information MK2 and the detailed information MS2 are registered from the distributor terminal 30b of the B area.

  Since a plurality of notification information Mn are registered respectively from distributors of a plurality of districts, notification IDs are assigned in order of registration to identify each, and the notification IDs are sequentially stored in the server memory 204 of the database server 60. .

  In the case of the detailed information MSn stored in the storage 301 of the storage server 61, the content is moving image data.

  As shown in FIG. 7, in the distribution list DT of the server memory 204 of the database server 60, a plurality of distribution data HD1, HD2,.

  Distribution data HD1, HD2, ..., HDn to be stored are notification ID, distributor ID, distribution destination viewer ID, distributor name, icon image, notification display color, title, content type, distribution time, and distribution Configured by specified date and time.

  The distribution destination viewer ID is read from the distribution destination list by distributor LHn and set, and the other data is the notification basic information MKn.

  As shown in FIG. 8, in the log list GT of the server memory 204 of the database server 60, log data G1, G2,..., Gn are stored.

  The log data G1, G2, ..., Gn to be stored are notification ID, distributor ID, distribution destination viewer ID, distribution status, distribution completion date, viewer playback count, latest playback date, and viewer deletion date Composed of

  The notification ID, the distributor ID, and the distribution destination viewer ID are set to data set in the distribution data HD1, HD2,..., HDn corresponding to the log data G1, G2,. .

  Whether the delivery of notification basic information MKn of the delivery data HDn to the viewer has been completed or not is set as the delivery status, and delivery is completed and the date is set as the delivery completion date.

  The number of times the viewer has acquired the detailed information MSn by the pull method is set as the number of times of viewer reproduction, and the latest date and time when the viewer acquires the detailed information MSn by the pull method is set as the latest reproduction date.

  As the viewer deletion date and time, the date and time when the viewer deleted the notification information Mn stored in the viewer terminal 40 n is set.

  The notification information format stored in the screen configuration information master 203 of the database server 60 defines an input screen format for inputting each item of the notification information Mn shown in FIG.

  As shown in FIG. 9, the per-viewer distribution server list CSn of the distribution management server 70 includes a viewer ID, a session ID, an announcement distribution server address, a low capacity content distribution server address, and a large capacity content distribution server address. Ru.

  The viewer ID is identification information of each viewer given when registering viewer information, and the session ID is identification information of a session given when each viewer logs in.

  The notification distribution server address, the low-capacity content distribution server address, and the large-capacity content distribution server address are allocated from among a plurality of distribution servers arranged when registering viewer information or when a viewer logs in. It is an address for communicating with the distribution server.

  The assignment method is optional, and assignment can be performed in consideration of load distribution, or can be assigned from the location of the access point used by the viewer.

  As shown in FIG. 10, the per-session distribution server list SSn of the session establishment server 80 is configured of a session ID and an announcement distribution server address.

  The session ID is identification information of a session given when each viewer logs in, and the notice distribution server address is the address of a notice distribution server with which the viewer establishes a session with the session ID.

The session ID is assigned when the viewer logs in, and is discarded when there is no access or logout for a certain period of time.
Therefore, when the viewer logs in again, these data are updated.

(Function of each processing means included in database server 60)
Subsequently, the function of each processing means included in the database server 60 of the distribution cloud 10 according to the first embodiment will be described.

  The distributor registration unit 101 assigns a distributor ID for identifying a distributor, the distributor information input from the administrator terminal 20 in response to a request from a distributor who wants to distribute information in the main distribution cloud 10. It stores in the distributor information database 201 as the distributor registration information Hn.

  At this time, the distributor registration unit 101 associates the area of the distributor distribution list LHn for the distributor with the distributor registration information Hn and the distributor ID, and sets the area in the distributor information database 201.

  The distributor authentication unit 102 authenticates the distributor by comparing the distributor ID and the password input from the distributor terminals 30 a and 30 b with the distributor registration information Hn stored in the distributor information database 201.

  The input screen providing unit 103 reads the notification information format stored in the screen configuration information master 203, adds a notification ID for identifying the input notification information, and transmits the notification information to the distributor terminals 30a and 30b.

  The notification information registration unit 104 receives the notification information Mn input to the notification information format at the distributor terminals 30a and 30b, and has already registered the notification basic information MKn to which the notification ID included in the notification information Mn is added. Necessary information (icon image, notification display color, etc.) is read out from the person registration information Hn, added, and stored in the server memory 204.

  Furthermore, the notification information registration unit 104 determines the content type of the detailed information MSn included in the notification information Mn, and in the case of low capacity (text), the detailed information MSn of the text to which the notification ID is added is stored in the server memory 204. If the data is stored and has a large capacity (moving image), the moving image registration unit 112 of the storage server 61 transmits the detailed information MSn of the moving image to which the notification ID is assigned.

  The distribution data extraction unit 105 sequentially reads out the notification basic information MKn newly stored in the server memory 204 at predetermined time intervals, to the distributor information database 201 corresponding to the distributor ID included in each notification basic information MKn. The notification basic information MKn is added to each distribution destination viewer ID read out from the stored distribution destination list LHn by distributor, to create distribution data HDn, and the distribution data DTn is stored in the distribution list DT of the server memory 204.

  However, the delivery data extraction unit 105 creates the delivery data HDn only when the current time or the delivery designation date and time set by the deliverer in the notification basic information MKn is within the delivery period desired by the viewer, and the server memory It stores in the distribution list DT of 204.

  The title distribution unit 106 sequentially reads out the distribution data HDn stored in the distribution list DT of the server memory 204 at fixed time intervals, and transmits the distribution data HDn to the distribution management server 70.

  Furthermore, for the distribution data HDn to be transmitted to the distribution management server 70 for the first time, the title distribution unit 106 sets the notification ID of the distribution data HDn, the distributor ID and the distribution destination viewer ID, and “Distributing” in the distribution status column. The set log data Gn is created and stored in the log list GT of the server memory 204.

  However, when the delivery designation date and time is set to the read out delivery data HDn, the title delivery unit 106 transmits the delivery data HDn to the delivery management server 70 only when the current time has reached the delivery designation date and time. .

  When notified of the progress of distribution of each notification information Mn from the distribution management server 70 by the notification ID, the viewer ID, and the distribution status information, the log updating unit 107 uses the notification ID and the viewer ID as the server memory 204. The corresponding log data Gn is detected from the log list GT, and the log data Gn is updated with the data of the distribution state information.

  Furthermore, when the data of the distribution status information is “distribution completed”, the log updating unit 107 detects the corresponding distribution data HDn from the distribution list DT of the server memory 204 by the notification ID and the viewer ID, Delete distribution data HDn.

  The text transmission unit 111 is the notification ID included in the detailed information request received from the viewer terminal 40 n via the distribution management server 70 and the low-capacity content distribution servers 62 a and 62 b, and the detailed information MSn of the text of the server memory 204 , The corresponding detailed information MSn is read out, and transmitted to the low capacity content distribution servers 62a and 62b.

  The viewer registration unit 108 views the viewer information input from the viewer terminal 40 n by the viewer who wishes to distribute the information in the main distribution cloud 10 with the viewer ID for identifying the viewer. It stores in the viewer information database 202 as the person registration information Cn.

  At this time, the viewer registration unit 108 associates the area of the distributor selection list LCn for the viewer with the viewer registration information Cn and the viewer ID, and sets the area in the viewer information database 202.

  The viewer authentication unit 109 verifies the viewer ID and password input from the viewer terminal 40 n with the viewer registration information Cn stored in the viewer information database 202 to authenticate the viewer.

  When the distributor setting unit 110 receives the distributor selection list request from the viewer terminal 40 n, the distributor setting unit 110 sets all distributor IDs and distributor names registered in the distributor registration information Hn of the distributor information database 201. A selection format is created and transmitted to the viewer terminal 40 n.

  In addition, when the distributor setting unit 110 receives, from the viewer terminal 40 n, distributor-specific setting information HSn in which distribution selection and display conditions (distribution period) are set in the distributor selection format, distributor selection of the viewer information database 202 is performed. Set to list LCn.

  Furthermore, the distributor setting unit 110 reads, from the set distributor selection list LCn, the distributor ID and distribution period of each distributor that the viewer has selected as distribution request, and each distribution set in the distributor information database 201 The viewer ID of the viewer is added as a distribution destination viewer ID to the distribution destination list LHn by distributor ID of the person ID, and a distribution period is set.

(Function of each processing means included in storage server 61)
Subsequently, the function of each processing means included in the storage server 61 of the distribution cloud 10 according to the first embodiment will be described.

  When the content type of the detailed information MSn included in the notification information Mn is a large capacity (moving image), the moving image registration unit 112 details the moving image to which the notification ID transmitted from the notification information registration unit 104 of the database server 60 is assigned. The information MSn is stored in the storage 301.

  The moving picture transmission unit 113 uses the notification ID included in the detailed information request received from the viewer terminal 40 n via the distribution management server 70 and the large-capacity content distribution servers 63 a and 63 b to obtain the detailed information MSn of the moving picture in the storage 301. The search is made, the corresponding detailed information MSn is read out, and transmitted to the large-capacity content distribution servers 63a, 63b.

(Configuration of Viewer Terminal 40n in the First Embodiment of the Present Invention)
On the other hand, when the viewer uses the distribution cloud 10, the distribution cloud 10 includes a program (application) for causing the viewer terminal 40n to execute each processing means of the viewer terminal 40n described below. Download and implement from etc.

  Although not shown, the distribution cloud 10 includes means for providing an application to the database server 60, the distribution management server 70, and the like.

  For example, a program providing unit (not shown) is provided in the database server 60, the application is stored in advance in the server memory 204 of the database server 60, and when the download request from the viewer is received By downloading 40 n and mounting it, the CPU of the viewer terminal 40 n is caused to execute the function as each processing means shown in FIG.

  As shown in FIG. 11, the viewer terminal 40 n according to the first embodiment of the present invention has a screen 41, a session establishing unit 42, a display setting unit 43, a distribution information receiving unit 44, and a title display unit 45. , A title deletion unit 46, a content acquisition unit 47, and a terminal memory 48.

  The terminal memory 48 stores distributor-specific setting information HSn and distribution information HTn.

  FIG. 11 illustrates the case where the notification distribution server 81a, the low-capacity content distribution server 62a, and the large-capacity content distribution server 63a are assigned to the viewer terminal 40n.

(Configuration of various data used by viewer terminal 40 n)
Subsequently, the configuration of various data used by the viewer terminal 40 n will be described.

  The distributor-specific setting information HSn has the same configuration as the distributor selection list LCn shown in (b) of FIG. 4 and includes the distributor ID and distributor name of each distributor registered in the main distribution cloud 10. The first distributor ID and the first distributor name, the second distributor ID and the second distributor name,..., The n-th distributor ID and the n-th distributor name are set. It is comprised by the field which each sets delivery selection (0: unnecessary, 1: desired) about each delivery person, and the delivery period in the case of wishing delivery.

  The distributor ID and the distributor name of each distributor are set in the distributor selection format transmitted from the database server 60.

  As shown in FIG. 11, in the distribution information HTn, a folder Fn having a distributor name corresponding to each distributor is created, and to each folder Fn, data for setting the number of unread distribution data in the folder is added. An unread flag is added to the distribution data HDn shown in FIG. 7 from the corresponding distributor and stored.

(Function of each processing means included in the viewer terminal 40 n)
Subsequently, functions of each processing means included in the viewer terminal 40 n will be described.

  The session establishing unit 42 transmits the viewer information input from the screen 41 to the database server 60 via the distribution management server 70 for registration, and registers the viewer ID and password of the registered viewer information, the distribution management server At 70, it transmits to the database server 60 and logs in, and establishes a session with the notification distribution server 81a.

  The display setting unit 43 requests the database server 60 to transmit the distributor selection format via the distribution management server 70 and displays the distributor selection format received on the screen 41 to select distributor and display conditions (distribution period) Are set, and the set information is stored in the terminal memory 48 as the distributor-specific setting information HSn, and at the same time, is transmitted to the database server 60 via the distribution management server 70.

  The distribution information receiving unit 44 receives the distribution data HDn including the notification basic information MKn distributed from the notification distribution server 81a, and adds a folder Fn (for example, A) to the terminal memory 48 with the distributor name included in the distribution data HDn. If the district folder F1) is already created, the unread flag “1” is added to the delivery data HDn and saved in the folder Fn, and if not created, the folder Fn to which a distributor name is newly added (For example, the B area folder F2) is created, the unread flag “1” is added to the delivery data HDn in the created folder Fn, and the folder is stored.

  The delivery information receiving unit 44 adds one to the number of delivery data unread in the folder Fn in order to manage unread and read.

  When receiving the display tap signal from the screen 41, the title display unit 45 generates a tab TGn with a distributor name corresponding to each folder Fn created in the terminal memory 48, and the in-folder delivery data unread in each folder Fn It is displayed on the screen 41 together with the number.

  The title display unit 45 includes, in the distribution data HDn, the title of the distribution data HDn stored in the folder F1 in the area of the tab TGa corresponding to the first folder F1 (displayed in the foreground of the screen 41). Display a list according to the notification color.

  Furthermore, when the title display unit 45 receives a tab selection tap signal specifying another tab TGn on the screen 41, the area of the tab TGn is displayed on the foreground of the screen 41, and the folder corresponding to the selected tab TGn The titles of the distribution data HDn stored in Fn are listed and displayed according to the notification display color included in the distribution data HDn.

  When receiving the deletion tap signal from the screen 41, the title deletion unit 46 detects and deletes the distribution data HDn stored in the corresponding folder Fn from the notification ID of the corresponding title and the distributor ID, and at the same time, the distribution data Notification deletion notification is sent to the distribution management server 70 with the notification ID of HDn and the distribution destination viewer ID, and the log data Gn of the database server 60 is updated.

  When the value of the unread flag added to the distribution data HDn to be deleted is “1 (unread)”, the title deletion unit 46 subtracts one from the number of unread distribution data in the folder.

  When the content acquisition unit 47 receives the title tap signal from the screen 41, it detects the distribution data HDn stored in the corresponding folder Fn from the notification ID of the corresponding title and the distributor ID, and detects the content type of the distribution data HDn. Detailed information request including notification ID, distribution destination viewer ID, and viewer terminal address is transmitted to the distribution management server 70, and detailed information returned from the low capacity content distribution server 62a or the large capacity content distribution server 63a MSn is received and displayed on the screen 41 and reproduced.

  If the value of the unread flag added to the distribution data HDn is “1 (unread)”, the content acquisition unit 47 changes the value of the unread flag to “0: read” and the number of unread in-folder delivery data Subtract one.

(Sequence of each process of notification distribution system in the first embodiment of the present invention)
The process by the notification distribution system according to the first embodiment of the present invention will be described while illustrating the sequence for each process.

(A) Distributor Information Registration Process In the distributor information registration process, in order for the distributor to distribute the notification information Mn provided by the distributor himself using the distribution cloud 10, the distributor information (Distributor This is a step of registering the ID, the distributor name, the distributor password, the notification display color, the icon image ID, and the icon image in the distribution cloud 10.

  As shown in FIG. 12, the system administrator inputs new distributor information from the administrator terminal 20 at the distributor's request, and requests the system management server 50 for registration (d1).

  The system management server 50 transfers the received new distributor information to the distributor registration unit 101 of the database server 60 (d2).

  The distributor registration unit 101 assigns a distributor ID for identifying a distributor to the received new distributor information (d3).

  The distributor registration unit 101 distributes the new distributor information to which the distributor ID is assigned to the distributor information database 201. The distributor registration information Hn (Distributor ID, distributor name, distributor password, notification display color, icon image ID , And save as icon images) (d4).

  The distributor registration unit 101 further associates the distributor registration information Hn with the distributor ID, and sets the area of the distributor-specific distribution destination list LHn of the new distributor (d5).

  When the registration process is completed, the distributor registration unit 101 transmits a setting completion notification to the system management server 50 together with the assigned distributor ID (d6).

  The system management server 50 transfers the setting completion notification to the administrator terminal 20 together with the received distributor ID (d7).

  The system administrator notifies the distributor of the assigned distributor ID, and the distributor inputs the distributor ID and password at the time of use and logs in.

(A) Notification Information Registration Step The notification information registration step is a step in which the distributor registers in the distribution cloud 10 the notification information Mn provided by the distributor, which is distributed using the distribution cloud 10.

  As shown in FIG. 13, in order to access the distribution cloud 10 from the distributor terminal 30n, the distributor inputs the distributor ID and the password into the system management server 50 and logs in (d8).

  The system management server 50 transfers the received distributor ID and password to the distributor authentication unit 102 of the database server 60 (d9).

  From the distributor information database 201 using the distributor ID as a key, the distributor authentication unit 102 receives the corresponding distributor registration information Hn (distributor ID, distributor name, distributor password, notification display color, icon image ID, and icon Image) is read out (d10).

  The distributor authentication unit 102 collates the received password with the password registered in the distributor registration information Hn, authenticates the distributor, and activates the input screen providing unit 103 (d11).

  The input screen providing unit 103 reads the notification information format from the screen configuration information master 203 (d12).

  The input screen providing unit 103 generates a notice ID for identifying the inputted notice information, and sets it in the notice information format (d13).

  The input screen providing unit 103 transmits the notification information format in which the notification ID is set to the system management server 50 (d14).

  The system management server 50 transfers the notification information format in which the received notification ID is set to the distributor terminal 30n (d15).

  The distributor terminal 30n displays the input screen according to the notification information format in which the received notification ID is set (d16).

  Subsequently, as shown in FIG. 14, the distributor sets the notification basic information MKn and the detailed information MSn on the input screen of the distributor terminal 30n (d17).

  The distributor terminal 30n transmits the input notification basic information MKn and the detailed information MSn as the notification information Mn to the system management server 50 (d18).

  The system management server 50 transfers the received notification information Mn (including the notification basic information MKn and the detailed information MSn) to the notification information registration unit 104 of the database server 60 (d19).

  The notification information registration unit 104 reads the corresponding distributor registration information Hn from the distributor information database 201 as the distributor ID key included in the notification basic information MKn (d20).

  The notification information registration unit 104 receives notification basic information MKn (notification ID, distributor ID, etc.) necessary for registration information set in the distributor registration information Hn, such as distributor name, icon image, notification display color, etc. , Including the title) (d21).

  When the distributor is configured to set all elements of the notification basic information MKn on the input screen of the distributor terminal 30n, this process is unnecessary.

  The notification information registration unit 104 stores the notification basic information MKn (including the notification display color, the notification ID, the distributor ID, and the title) for which the setting of all elements is completed in the server memory 204 (d22).

  The notification information registration unit 104 determines whether the content type included in the received notification basic information MKn (including notification display color, notification ID, distributor ID, and title) is low capacity (text) or large capacity (moving image). (D23).

  When the content type is low (text), the notification information registration unit 104 stores the text detailed information MSn in the server memory 204 (d24).

  The notification information registration unit 104 transmits detailed information MSn of the moving image to the moving image registration unit 112 of the storage server 61 when the content type is a large capacity (moving image) (d25).

  The moving picture registration unit 112 stores the received detailed information MSn of the moving picture in the storage 301 (d26).

  The moving picture registration unit 112 sends a save completion notification back to the notification information registration unit 104 of the database server 60 (d27).

  The notification information registration unit 104 transmits the storage completion notification to the system management server 50 when the storage of the text detailed information MSn in the server memory 204 is completed or the storage completion notification is received from the moving image registration unit 112 of the storage server 61. To do (d28).

  The system management server 50 transfers the received storage completion notification to the distributor terminal 30n (d29).

(C) Viewer Information Registration Process In the viewer information registration process, the viewer selects a desired distributor from among a plurality of distributors and receives the distribution of the notification information Mn from the selected distributor. This is a step of registering the viewer information in the distribution cloud 10 in advance.

  Since the display image of the screen 41 of the viewer terminal 40 n is illustrated in FIG. 15 and FIG. 16, the sequence will be described with reference to the display image of the screen 41.

  The viewer taps (or touches) the icon B1 indicating the downloaded application on the screen 41 of the viewer terminal 40n shown in (a) of FIG.

  As shown in FIG. 17, first, the viewer inputs viewer information, and transmits and registers the viewer information from the session establishing unit 42 of the viewer terminal 40n to the distribution management server 70 (d30).

  The distribution management server 70 transfers the received viewer information to the viewer registration unit 108 of the database server 60 (d31).

  The viewer registration unit 108 assigns a viewer ID for identifying a viewer to the received new viewer information (d32).

  The viewer registration unit 108 stores the viewer information given the viewer ID in the viewer information database 202 as viewer registration information Cn (viewer ID, viewer password, registration date and time) (d33).

  The viewer registration unit 108 further associates the viewer registration information Cn with the viewer ID, and sets the area of the distributor selection list LCn of the new viewer (d34).

  When the registration process is completed, the viewer registration unit 108 transmits a setting completion notification to the distribution management server 70 together with the assigned viewer ID (d35).

  The distribution management server 70 includes the viewer ID and addresses of various distribution servers (for example, the notification distribution server 81a, the low-capacity content distribution server 62a, and the large-capacity content distribution server 63a) in charge of distribution to the viewer ID by viewer. It sets and associates with the distribution server list CSn (d36).

  The distribution management server 70 transmits a setting completion notification together with the viewer ID to the session establishing unit 42 of the viewer terminal 40 n (d37).

  As shown in (b) of FIG. 15, the session establishing unit 42 displays a login screen for logging in by inputting the viewer ID and password registered in the viewer (d38).

  Once the registration of the viewer information is completed, tapping the icon B1 in (a) of FIG. 15 displays the login screen of (b) of FIG.

  As shown in FIG. 18, when the viewer inputs the viewer ID and password on the login screen of the viewer terminal 40 n and taps the input button B 2, the session establishing unit 42 receives the input viewer ID and password. Are sent to the delivery management server 70 and logged in (d39).

  The distribution management server 70 transmits the received viewer ID and password to the viewer authentication unit 109 of the database server 60 (d40).

  The viewer authentication unit 109 reads the corresponding viewer registration information Cn (viewer ID, viewer password, registration date and time) from the viewer information database 202 using the received viewer ID as a key (d41).

  The viewer authentication unit 109 verifies the viewer by comparing the received password with the password registered in the viewer registration information Cn (d42).

  When the authentication is completed, the viewer authentication unit 109 sends the viewer ID and the login approval notice back to the distribution management server 70 (d43).

  The distribution management server 70 uses the received viewer ID as a key, and the distribution server list by viewer CSn (viewer ID, session ID, notification distribution server address, low capacity content distribution server address, large capacity content distribution server address) For example, the address of the notification distribution server 81a associated with the viewer ID is retrieved (d44).

  The distribution management server 70 generates a session ID for identifying a session established by the viewer's current login, and the distribution server list by viewer CSn (viewer ID, session ID, notification distribution server address, low capacity) It assigns to the record of the said viewer ID of a content delivery server address and a large capacity content delivery server address (D45).

  The distribution management server 70 transmits the assigned session ID and the login approval notice to the session establishing unit 42 of the viewer terminal 40 n (d46).

  At this time, if necessary, the address of the session establishment server 80 accessed by the viewer terminal 40 n to establish a session is simultaneously notified to the viewer terminal 40 n.

  At the same time, the distribution management server 70 transmits the assigned session ID to the notification distribution server 81a by the address of the notification distribution server 81a associated with the viewer ID read out from the viewer-based distribution server list CSn (d47).

  The notification distribution server 81a stores the received session ID in a temporary memory (not shown) or the like (d48).

  As shown in FIG. 19, the session establishment unit 42 of the viewer terminal 40 n transmits the received session ID to the session establishment server 80 according to the notified address of the session establishment server 80 (d 49).

  The session establishment server 80 inquires of each notification distribution server 81a, 81b whether it is a server to be a partner of the current session, based on the received session ID (d50).

  The session establishment server 80 stores the address of the notification distribution server 81a that has responded to the inquiry in the session-specific distribution server list SSn in association with the session ID (d51).

  The notification distribution server 81a transmits a session establishment signal to the session establishment unit 42 of the viewer terminal 40n of the session partner (d52).

  The session establishing unit 42 sends a session response signal back to the notice distribution server 81a of the session partner (d53).

  The notice distribution server 81a monitors the established session state, periodically transmits a session establishment signal to the session establishment unit 42 of the viewer terminal 40n, and confirms the session response signal from the session establishment unit 42 (d54) .

  When the communication is temporarily interrupted, the session establishing unit 42 of the viewer terminal 40 n transmits the session ID again to the session establishing server 80 according to the address of the session establishing server 80, and repeats the procedure of d49 to d54, Re-establish the session.

  If communication is interrupted for a long time or the viewer logs out, the current session is disconnected and a new session is formed by the viewer's login.

(D) Distributor selection and display condition setting step The distributor selection and display condition setting step is for the viewer to select a desired distributor from among a plurality of distributors, and select notification information Mn of the selected distributor. This is a step of setting the distribution condition from the distribution cloud 10 and the display condition of the notification information Mn on the viewer terminal 40 n.

  As shown in FIG. 20, when the viewer taps the setting menu button B3 displayed on the screen 41 of the viewer terminal 40n shown in (c) of FIG. 15, the display setting unit 43 of the viewer terminal 40n The selection format is requested to the delivery management server 70 (d55).

  The distribution management server 70 transfers the received distributor selection format request to the distributor setting unit 110 of the database server 60 (d56).

  When the distributor setting unit 110 receives the distributor selection format request, the distributor setting unit 110 reads out distributor registration information Hn of the distributor information database 201 (d57).

  The distributor setting unit 110 creates a distributor selection format in which all distributor IDs and distributor names registered in the distributor registration information Hn are set, and transmits the distributor selection format to the distribution management server 70 (d58).

  The distribution management server 70 transfers the received distributor selection format to the display setting unit 43 of the viewer terminal 40n (d59).

  When the display setting unit 43 receives the distributor selection format, as shown in (d) of FIG. 15, the distributor setting information HSn (viewer ID, distributor ID, distributor) is displayed on the screen 41 of the viewer terminal 40n. Displayed as a setting screen for name, delivery selection (unnecessary, desired), delivery period), and for each distributor for each delivery person, if desired / not required for delivery selection, always as delivery period, or with delivery start date and time The distribution end date and time is set and stored in the terminal memory 48 (d60).

  Although the per-distributor setting information HSn includes a viewer ID and a distributor ID, since the viewer ID and the distributor ID are data for internal processing, they are displayed in the screen image of (d) of FIG. Absent.

  When the display setting unit 43 displays the setting screen, when there is the distributor-by-distributor setting information HSn previously set in the terminal memory 48, all the distributors from the distributor setting unit 110 via the distribution management server 70. The distributor selection format transmitted including the ID and the distributor name is overwritten with the stored distributor setting information HSn and displayed on the screen 41.

  Since the viewer is displayed in a state where the newly registered distributor ID and distributor name of the distributor are not set, the viewer can recognize that the distributor is a new distributor.

  In the example of (d) of FIG. 15, the distributor name (district name) always desires to distribute the notification information Mn from the distributor in the A area, and the notification information Mn from the distributor in the B area is 2014 1 Delivery is desired only from January 1st to March 31, 2014, and notification information Mn from a distributor in the Z area is set to be non-deliverable.

  When the update button B5 displayed on the screen 41 of the viewer terminal 40n shown in (d) of FIG. 15 is tapped, the display setting unit 43 transmits the set distributor-specific setting information HSn to the distribution management server 70. (D 61).

  The distribution management server 70 transfers the received distributor-specific setting information HSn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution period) to the distributor setting unit 110 of the database server 60. (D62).

  When the distributor setting unit 110 receives the distributor-specific setting information HSn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution period), the viewer information database 202 transmits the sender information In the area where the viewer ID is set, it is stored as a distributor selection list LCn (d63).

  The distributor setting unit 110 is a distributor of the distributor selected as the distribution request from the stored distributor selection list LCn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution date and time) The ID is read, and the viewer ID of the transmission source is set as the distribution destination viewer ID together with the distribution period in the distribution destination list LHn by distributor corresponding to the distributor ID in the distributor information database 201 (d64) .

  The distributor setting unit 110 transmits a setting completion notification to the distribution management server 70 (d65).

  The distribution management server 70 transfers the setting completion notification to the display setting unit 43 of the viewer terminal 40 n (d 66).

  The detailed processing of the distributor setting unit 110 of the database server 60 will be described later with reference to the flowchart.

(E) Notification Basic Information Extraction Process The notification basic information extraction process includes notification basic information MKn (notice ID, distributor ID, distributor name, icon image ID, icon image, notification display) of the notification information Mn registered by the distributor. Color, title, content type, delivery time, delivery specified date and time, extracted at fixed time intervals, delivery data HDn (announcement ID) in combination with the viewer ID of the delivery destination set in the delivery destination list LHn by distributor In this process, the distributor ID, the distribution destination viewer ID, the distributor name, the icon image, the notification display color, the title, the content type, the distribution time, the specified distribution date and time) are stored in the distribution list DT.

  As shown in FIG. 21, the distribution data extraction unit 105 of the database server 60 uses the notification basic information MKn (notification ID, distributor ID, distributor name, icon image) newly stored in the server memory 204 at fixed time intervals. The ID, icon image, notification display color, title, content type, distribution time, specified delivery date and time) is read, and the distribution destination by distributor is stored in the distributor information database 201 with the distributor ID included in the notification basic information MKn. Each distribution destination viewer ID and notification basic information MKn (notification ID, distributor ID, distributor name, icon image ID, icon image, notification display color) which are searched for the list LHn and set in the distribution destination list LHn for each distributor Distribution data HDn (notification ID, distributor ID, distribution destination viewer ID) from title, content type, distribution time, specified distribution date and time Distributor's name, icon image, notification display color, title, content type, delivery time, to create a distribution specified date and time), to save the distribution list DT of server memory 204 (d67).

(F) Push method notification basic information distribution process The push method notification basic information distribution process includes distribution data HDn (notification ID, distributor ID, distribution destination viewer ID, distributor name, icon image, etc.) stored in the distribution list DT. In this process, the notification display color, the title, the content type, the delivery time, the delivery designation date and time) are read at regular intervals, and the delivery data HDn is delivered by a push method to the viewer ID of the delivery destination.

  As shown in FIG. 21, the title distribution unit 106 of the database server 60 distributes the distribution data HDn (notification ID, distributor ID, distribution destination viewer ID, etc.) stored in the distribution list DT of the server memory 204 at fixed time intervals. The distributor name, the icon image, the notification display color, the title, the content type, the distribution time, the specified distribution date and time) are read out (d68).

  The title distribution unit 106 transmits the read distribution data HDn to the distribution management server 70 (d69).

  The title distribution unit 106 sets the notification ID of the transmitted distribution data HDn, the distributor ID and the distribution destination viewer ID, and log data Gn (log data, notification ID, distributor ID set in the distribution status column as “during distribution”) The distribution destination viewer ID, the distribution status, the distribution completion date and time, the viewer reproduction number, the latest reproduction date and time, the viewer deletion date and time) are created, and the log list GT of the server memory 204 is saved to completion (d70).

  The distribution management server 70 is the distribution destination viewer ID included in the received distribution data HDn, and the distribution server list CSn for each viewer (viewer ID, session ID, notification distribution server address, low-capacity content distribution server address, large capacity) The content distribution server address is searched, and the session ID of the session established by the viewer terminal 40n of the distribution destination viewer ID and the address of the notification distribution server of the session counterpart are read (d71).

  The distribution management server 70 transfers the distribution data HDn and the read session ID to the notification distribution server 81a of the read notification distribution server address (d72).

  The notification distribution server 81a determines whether a session of the received session ID is being established (d73).

  Since the notification distribution server 81a can not distribute the received distribution data HDn to the viewer terminal 40n when the session is not established yet, the “distribution is performed together with the notification ID and the distribution destination viewer ID included in the distribution data HDn. Delivery status information “incomplete” is sent back to the delivery management server 70 (d74).

  The distribution management server 70 transfers the received notification ID, distribution destination viewer ID, and distribution status information of “distribution incomplete” to the log updating unit 107 of the database server 60 (d75).

  The log updating unit 107 detects the corresponding log data Gn from the log list GT of the server memory 204 by the received notification ID and the distribution destination viewer ID, and since the distribution status information is “distribution incomplete”, the distribution status column “Distribution not completed” is set in (d76).

  On the other hand, as shown in FIG. 22, when the session is being established, the notification distribution server 81a distributes the received distribution data HDn to the distribution information receiving unit 44 of the viewer terminal 40n (d77).

  The notification distribution server 81a sends, to the distribution management server 70, distribution status information of “distribution completed” together with the notification ID and the distribution destination viewer ID included in the distribution data HDn (d78).

  The distribution management server 70 transfers the received notification ID, distribution destination viewer ID, and distribution status information of “distribution completed” to the log updating unit 107 of the database server 60 (d79).

  The log updating unit 107 receives the notification ID and the distribution destination viewer ID from the log list GT of the server memory 204, and the corresponding log data Gn (notification ID, distributor ID, distribution destination viewer ID, distribution status, distribution completion) Date and time, viewer playback count, latest playback date and time, viewer deletion date) is detected, and since the delivery status information is "delivery complete", "delivery complete" is set in the delivery status column, and the delivery completion date is set. To do (d80).

  The log updating unit 107 detects the corresponding distribution data HDn from the distribution list DT of the server memory 204 by the received notification ID and distribution destination viewer ID, and deletes the distribution data (d81).

  The distribution information receiving unit 44 of the viewer terminal 40n creates the folder Fn with the distributor name included in the distribution data HDn in the distribution information HT of the terminal memory 48 and stores the received distribution data HDn (d82 ).

  On the other hand, the title display unit 45 of the viewer terminal 40n receives a display tap signal indicating that the viewer taps the display button B4 displayed on the screen 41 of the viewer terminal 40n shown in (c) of FIG. The distribution data HDn stored in each folder Fn of the distribution information HT of the terminal memory 48 is displayed on the screen 41 as shown in (e) and (f) of FIG. 16 (d83).

  The title deletion unit 46 of the viewer terminal 40 n indicates that the viewer taps one of the delete buttons B6 displayed beside the notification titles Ta1 and Ta2 on the screen 41 shown in (e) of FIG. 16, for example. A delete tap signal is received (d84).

  The title deletion unit 46 detects and deletes the distribution data HDn stored in the folder Fn of the corresponding distribution information HT from the notification IDs of the notification titles Ta1 and Ta2 and the distributor ID where the delete button B6 is tapped (d85) ).

  The title deletion unit 46 transmits a notification deletion notification to the distribution management server 70 together with the notification ID of the deleted distribution data HDn and the distribution destination viewer ID (the viewer ID of the viewer) (d86).

  The distribution management server 70 transfers the notification deletion notification to the log updating unit 107 of the database server 60 together with the notification ID and the distribution destination viewer ID received (d87).

The log updating unit 107 detects the corresponding log data Gn from the log list GT of the server memory 204 by the received notification ID and the distribution destination viewer ID, and sets the viewer deletion date and time (d88).
About detailed processing of distribution data extraction unit 105, title distribution unit 106, and log update unit 107 of database server 60, distribution information reception unit 44 of viewer terminal 40n, title display unit 45, and title deletion unit 46 Will be described later with reference to the flowchart.

(K) Pull Method Detailed Information Delivery Process In the pull method detailed information delivery process, the viewer selects the title displayed on the screen 41 of the viewer terminal 40 n and accesses the delivery cloud 10 to deliver the delivery cloud 10 is a process of distributing detailed information MSn from 10 in a pull method.

  The distribution cloud 10 of the present invention is provided with two types of distribution paths in the case where the distribution detailed information MSn has a low capacity like text and the case where it has a large capacity like a moving image.

  FIG. 23 shows a sequence in the case where the delivery detailed information MSn has a low capacity like text.

  As shown in FIG. 23, the content acquisition unit 47 of the viewer terminal 40n receives, for example, a title tap signal indicating that the viewer has tapped the notification title Tb1 on the screen 41 shown in (h) of FIG. d89).

  The content acquisition unit 47 includes the content type, notification ID and distribution destination viewer ID (viewer ID of the viewer's own user) included in the delivery data HDn of the tapped title, and the viewer terminal in use for data communication The detailed information request is transmitted to the delivery management server 70 by the address (d90).

  The distribution management server 70 searches the distribution server list CSn for each viewer based on the received distribution destination viewer ID and content type, and reads out the allocated content distribution server address (d91).

  In FIG. 23, since the content type is low capacity (text), the low capacity content distribution server address is read.

  The distribution management server 70 transmits the received notification ID, distribution destination viewer ID, and viewer terminal address to the low-capacity content distribution server 62a with the read low-capacity content distribution server address (d92).

  The low-capacity content distribution server 62a transmits a detailed information request to the text transmission unit 111 of the database server 60 with the received notification ID and distribution destination viewer ID (d93).

  The text transmission unit 111 searches the detailed information MSn of the text stored in the server memory 204 for the received notification ID, and reads it (d94).

  The text transmission unit 111 sends back the read detailed information MSn of the text to the low-capacity content distribution server 62a together with the notification ID and the distribution destination viewer ID received (d95).

  The low-capacity content distribution server 62a transmits the received detailed information MSn of the text to the content acquisition unit 47 of the viewer terminal 40n by the viewer terminal address received from the distribution management server 70 (d96).

  The content acquisition unit 47 displays the detailed information MSn of the received text on the screen 41 as the notification content Cb1 of the notification title Tb1 as shown in (i) of FIG. 16 (d97).

  When the low-capacity content distribution server 62a completes the transmission of the text detailed information MSn, the low-capacity content distribution server 62a transmits a transmission completion notification to the distribution management server 70 together with the notification ID and the distribution destination viewer ID received (d98).

  When the distribution management server 70 receives the transmission completion notification together with the notification ID and the distribution destination viewer ID, the distribution status information of “reproduction of detailed information” is stored in the log of the database server 60 together with the received notification ID and distribution destination viewer ID. It transmits to the update unit 107 to request log update (d99).

  The log updating unit 107 detects the corresponding log data Gn from the log list GT of the server memory 204 by the received notification ID and the distribution destination viewer ID, and sets the latest playback date and time and the number of viewer playback (d100).

  Next, FIG. 24 shows a sequence in the case where the delivery detailed information MSn has a large capacity like a moving image.

  As shown in FIG. 24, the content acquisition unit 47 of the viewer terminal 40n receives, for example, a title tap signal indicating that the viewer taps the notification title Tb1 on the screen 41 shown in (h) of FIG. d101).

  The content acquisition unit 47 includes the content type, notification ID and distribution destination viewer ID (viewer ID of the viewer's own user) included in the delivery data HDn of the tapped title, and the viewer terminal in use for data communication The detailed information request is transmitted to the delivery management server 70 by the address (d102).

  The distribution management server 70 is a distribution server list CSn (viewer ID, session ID, notification distribution server address, low-capacity content distribution server address, large-capacity content distribution server) according to the distribution destination viewer ID and content type received. Address), and the assigned content delivery server address is read (d103).

  In FIG. 24, since the content type is a large capacity (moving image), a large capacity content distribution server address is read.

  The distribution management server 70 transmits the received notification ID, distribution destination viewer ID, and viewer terminal address to the large-capacity content distribution server 63a with the read-out large-capacity content distribution server address (d104).

  The large-capacity content distribution server 63a transmits a detailed information request to the moving picture transmission unit 113 of the storage server 61 with the received notification ID and distribution destination viewer ID (d105).

  The moving picture transmission unit 113 searches the detailed information MSn of the moving picture stored in the storage 301 with the received notification ID and reads it (d106).

  The moving picture transmission unit 113 sends the read detailed information MSn of the moving picture together with the notification ID and the distribution destination viewer ID received to the large-capacity content distribution server 63a (d107).

  The large-capacity content distribution server 63a transmits the received detailed information MSn of the moving image to the content acquisition unit 47 of the viewer terminal 40n according to the viewer terminal address received from the distribution management server 70 (d108).

  The content acquisition unit 47 reproduces the received detailed information MSn of the moving image on the screen 41 as the notification content Cb1 of the notification title Tb1 as shown in (i) of FIG. 16 (d109).

  When the transmission of the detailed information MSn of the moving image is completed, the large-capacity content distribution server 63a transmits a transmission completion notification to the distribution management server 70 together with the notification ID and the distribution destination viewer ID received (d110).

  When the distribution management server 70 receives the transmission completion notification together with the notification ID and the distribution destination viewer ID, the distribution status information of “reproduction of detailed information” is stored in the log of the database server 60 together with the received notification ID and distribution destination viewer ID. It transmits to the update unit 107 and requests log update (d111).

  The log updating unit 107 detects the corresponding log data Gn from the log list GT of the server memory 204 with the received notification ID and distribution destination viewer ID, and sets the latest playback date and time and the number of viewer playback (d112).

  The detailed processing of the content acquisition unit 47 of the viewer terminal 40 n will be described later with reference to the flowchart.

  Although the flow as the whole of the notification distribution system has been described above with reference to the sequence, the processing means which is the feature of the present invention will be described in more detail with reference to the flowchart.

(Detailed Description of Processing Means in First Embodiment of the Present Invention)
(Distributor setting unit 110 of database server 60)
First, detailed processing will be described with reference to the flowchart of FIG. 25 for the distributor setting unit 110 of the database server 60 that functions in the distributor selection and display condition setting step shown in the sequence of FIG.

  The distributor setting unit 110 receives the distributor selection format request from the display setting unit 43 of the viewer terminal 40 n via the distribution management server 70 (S 11).

  The distributor setting unit 110 reads out distributor registration information Hn (distributor ID, distributor name, distributor password, notification display color, icon image ID, icon image) stored in the distributor information database 201 (S12) .

  As shown in FIG. 3A, in the distributor registration information Hn, distributor IDs and distributor names of all distributors are registered as a list, and the distributor setting unit 110 distributes the distributors. A distributor selection format is created in which all distributor IDs and distributor names registered in registration information Hn (Distributor ID, distributor name, distributor password, notification display color, icon image ID, icon image) are set. To do (S13).

  The distributor selection format has the same format as the distributor selection list LCn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution date and time) shown in FIG. The viewer ID of the viewer who has requested the viewer selection format is set to the nth viewer ID, and all the distributor IDs and distributor names registered in the distributor registration information Hn are, in order, the first The first distributor ID, the second distributor ID, and the second distributor name,..., And the nth distributor ID and the nth distributor name are created. .

  The distributor setting unit 110 transmits the generated distributor selection format to the viewer terminal 40 n via the distribution management server 70 (S 14).

  As described above in d60 and d61 of FIG. 20, when the display setting unit 43 of the viewer terminal 40n receives the distributor selection format, as shown in (d) of FIG. 15, the display setting unit 43 displays the screen 41 of the viewer terminal 40n. It is displayed as a setting screen of setting information HSn for each distributor (viewer ID, distributor ID, name of distributor, selection of distribution (unnecessary, desired), distribution period), and distribution selection unnecessary for each distributor for viewers ・If desired and desired, the distribution period is always set as the distribution period, or the distribution start date and distribution end date are set, and stored in the terminal memory 48, and set distributor-specific setting information HSn (viewer ID, distributor ID, distribution The name of the person, delivery selection (unnecessary, desired), delivery period) is sent to the delivery management server 70.

  The distributor setting unit 110 sets distributor-specific setting information HSn (a viewer ID, a distributor ID, a distributor name, a distribution selection (unnecessary, desired)) in which the viewer sets distributor selection and display conditions in the distributor selection format. , Distribution period) via the distribution management server 70 (S15).

  The distributor setting unit 110 selects the distributor of the viewer information database 202 for the received distributor setting information HSn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution period). It adds to list LCn (S16).

  The distributor setting unit 110 sequentially reads out one record of data related to each distributor of the added distributor selection list LCn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution date and time) (S17).

  That is, the record set for the first distributor ID in the first process, the record set for the second distributor ID in the second process, ..., the nth distributor in the nth process The records set for the ID and one record each time the process is repeated are read.

  The distributor setting unit 110 determines whether the distribution selection of the distributor is unnecessary or desired (S18).

  The distributor setting unit 110 is a distributor shown in (b) of FIG. 3 which is associated with the distributor ID of the distributor in the distributor information database 201 when the distribution selection of the distributor is desired. The viewer ID set in the distributor selection list LCn (a viewer ID, a distributor ID, a distributor name, a distribution selection (unnecessary, desired), a distribution date and time) is searched for a distribution destination viewer by searching the separate distribution destination list LHn. The data is added as an ID, and the data of the distribution period of the read out record is copied and set (S19).

  The distributor setting unit 110 determines whether there is a next record, and if there is, the process returns to the process of S17.

  By the process of the distributor setting unit 110, the distribution destination list LHn (distributor ID, distribution period) shown in FIG. 5 and the distributor selection list LCn (viewer ID, distributor ID, distributor name, distribution selection) are selected. The association of (necessary, desired), delivery date and time is performed.

  For example, in the distributor selection list LC1 shown in FIG. 5, the distributors of the distribution destination distribution list LH1, the distribution destination list LH2, and the distribution destination list LHn are selected as distribution requests. It can be seen that in the distributor selection list LC2, only the distributors of the distribution destination list by distributor LH2 are selected, and in the distributor selection list LCn, only the distributors of the distribution destination list by distributor LHn are selected as the distribution request.

  Conversely, only the viewer ID of the distributor selection list LC1 is in the distributor-specific distribution destination list LH1, and the viewer IDs of the distributor selection list LC1 and the distributor selection list LC2 is the distributor in the distributor-specific distribution destination list LH2. In the separate distribution destination list LHn, the viewer IDs of the distributor selection list LC1 and the distributor selection list LCn are respectively set as distribution destination viewer IDs.

  The notification information Mn of each distributor is distributed only to the viewers of the distribution destination viewer IDs set in the distributor-specific distribution destination lists LH1, LH2, ..., LHn.

(Distributed Data Extraction Unit 105 of Database Server 60)
Next, in the notification basic information extracting step shown in the sequence of FIG. 21, the notification basic information MKn (notification ID, distributor ID, distributor name, icon image ID, icon image, notification display color, title, content type, distribution Detailed processing will be described with reference to the flowchart of FIG. 26 for the delivery data extraction unit 105 of the database server 60 that extracts the time, delivery specified date and time).

  The distribution data extraction unit 105 measures time using a timer (not shown) built in the database server 60, and repeatedly starts the following processing after waiting for a predetermined time set in advance (S21).

  The delivery data extraction unit 105 uses the notification basic information MKn (notification ID, distributor ID, distributor name, icon image ID, icon image, notification display color, title, etc.) newly stored in the server memory 204 for a predetermined time. The content type, delivery time, delivery specified date and time) are read out in order (S22).

  That is, reading the notification basic information MK1, the notification basic information MK2, the notification basic information MK3,... Shown in FIG. 6 one by one, the following process is performed on the read notification basic information MKn.

  The distribution data extraction unit 105 distributes the notification basic information MKn (notice ID, distributor ID, distributor name, icon image ID, icon image, notification display color, title, content type, distribution time, specified distribution time). If the data is “1: date and time designated”, that is, if the delivery designated date and time is set, the delivery designated date and time of the notification basic information MKn is read out (S23).

  The distribution data extraction unit 105 is set to the notification basic information MKn (notification ID, distributor ID, distributor name, icon image ID, icon image, notification display color, title, content type, distribution time, distribution specified date and time) The distributor ID is read (S24).

  The distribution data extraction unit 105 searches the distributor ID distribution destination list LHn (distributor ID, distribution destination viewer ID, distribution period) stored in the distributor information database 201 using the distributor ID (S25).

  The distribution data extraction unit 105 sequentially reads one record (distribution destination viewer ID and distribution period) set in the distribution list by distributor LHn of interest (S26).

  That is, in the first processing, the first distribution destination viewer ID and distribution period, in the second processing, the second distribution destination viewer ID and distribution period,..., In the nth processing, the nth distribution destination One record is read out each time the viewer ID, distribution period, and processing are repeated.

  If there is a distribution period included in the read out record, the current date or time, or the designated distribution date and time read out from the notification basic information MKn, the distribution data extraction unit 105 compares the designated distribution date and time, and within the distribution period. It is determined whether there is any (S27).

  The distribution data extraction unit 105 reads out the notification basic information MKn (notification ID, distributor ID, distributor name, icon image ID, icon image, notification display color, title, content type, distribution) only when the distribution period is under. The distribution destination viewer ID included in the record read out at the time, distribution designated date and time is added to the distribution data HDn (notification ID, distributor ID, distribution destination viewer ID, distributor name, icon image, notification display color, The title, content type, delivery time, delivery specified date and time) are created and stored in the delivery list DT of the server memory 204 (S 28).

  That is, only the notification information Mn for which the viewer of the distribution destination viewer ID included in the read out record has reached the distribution period for which distribution is desired is extracted and becomes distribution data HDn to the corresponding viewer.

  In addition, since the start date and the end date are always set in the delivery period, in the case of the constant, the delivery period is always treated.

  The distribution data extraction unit 105 determines whether or not there is a next record in the corresponding distributor-specific distribution destination list LHn (distributor ID, distribution destination viewer ID, distribution period), and if there is a next record, the processing returns to S26 ( S29).

  When the distribution data extraction unit 105 performs the processing of S27 and S28 for all the records of the distributor-specific distribution destination list LHn (distributor ID, distribution destination viewer ID, distribution period), the next notification basic information is stored in the server memory 204. It is determined whether there is MKn, and if there is, it returns to the processing of S22, and if there is not, the processing is once ended and the processing shifts to the waiting state of S21 (S30).

(Title distribution unit 106 of database server 60)
Next, notification basic information MKn (notification ID, distributor ID, distributor name, icon image ID, icon image, notification display color, title, content type) is shown in the sequence of FIG. The detailed processing will be described with reference to the flowchart of FIG. 27 with respect to the title distribution unit 106 of the database server 60 that distributes distribution timing, distribution specification date and time).

  The title distribution unit 106 measures time using a timer (not shown) built in the database server 60, and repeatedly starts the following process after waiting for a predetermined time period (S31).

  The title distribution unit 106 distributes the distribution data HDn of the distribution list DT (notification ID, distributor ID, distribution destination viewer ID, distributor name, icon image, notification display) stored in the server memory 204 by the distribution data extraction unit 105. Color, title, content type, delivery time, delivery specified date and time) are read out in order (S32).

  That is, in the distribution list DT shown in FIG. 7, the distribution data HD in the first process and the distribution data HD2 in the first process are read out one by one each time the process is repeated.

  The title delivery unit 106 reads the set delivery designated date and time when the delivery date data of the read out delivery data HDn is “1: date and time designation”, that is, when the designated delivery date and time is set (S33).

  The title delivery unit 106 compares the current date and time with the read delivery specified date and determines whether it is after the delivery specified date and time, and if the delivery specified date is not reached, the process returns to S32 and reads the next delivery data HDn (S34).

  In this determination process, when the data of the delivery time is “0: normal”, it is determined that the delivery specified date and time is after.

  The title distribution unit 106 transmits the distribution data HDn to the distribution management server 70 when the data of the distribution time is "0: normal" or when the current date and time is after the distribution specification date and time (S35).

  The title distribution unit 106 searches the log list GT in the server memory 204 for the log data Gn corresponding to the distribution data HDn using the notification ID and the distribution destination viewer ID included in the distribution data HDn as a key (S36) .

  The title distribution unit 106 determines whether there is the corresponding log data Gn (S37).

  When there is no corresponding log data Gn, that is, when the distribution data HDn is transmitted for the first time, the title distribution unit 106 notifies the notification ID of the distribution data HDn, the distributor ID and the distribution destination viewer ID, and The log data Gn corresponding to the distribution data HDn set as "during distribution" is created and stored in the log list GT of the server memory 204 (S38).

  The title distribution unit 106 determines whether there is the next distribution data HDn, and if there is, the process returns to S32, reads the next distribution data HDn, and if there is not, temporarily ends the process and transitions to the wait state of S31. (S39).

  The process of the title distribution unit 106 described above is to distribute the registered notification information Mn when a specific date and time is reached, not immediately after the distributor has registered the notification information Mn. Can be selected by

(Distribution information receiving unit 44 of the viewer terminal 40 n)
Next, in the push method notification basic information distribution process shown in the sequence of FIG. 22, the distribution data HDn including the notification basic information MKn distributed from the title distribution unit 106 of the database server 60 is received from the notification distribution server 81a. The detailed processing of the distribution information receiving unit 44 of the viewer terminal 40 n stored in the terminal memory 48 will be described with reference to the flowchart of FIG. 28.

  The distribution information receiving unit 44 is notified by the session establishing unit 42 of the viewer terminal 40 n to the viewer of the distribution destination viewer ID included in the distribution data HDn, as shown in the sequences of FIGS. 18 and 19. With the session established with the distribution server 81a, the distribution data HDn distributed from the title distribution unit 106 of the database server 60 is received from the notification distribution server 81a (S41).

  The distribution information receiving unit 44 reads the distributor name included in the received distribution data HDn (S42).

  The distribution information receiving unit 44 searches the distribution information HTn of the terminal memory 48 for the folder Fn to which the read distributor name is attached (S43).

  As a result of the search, the distribution information receiving unit 44 determines whether there is a folder Fn to which the read distributor name has been added (S44).

  If there is a corresponding folder Fn (for example, if the read distributor name is A area, A area folder F1), the distribution information receiving unit 44 adds an unread flag “1” to the distribution data HDn, and the corresponding folder Fn (For example, it is stored in the A area folder F1) (S45).

  The delivery information receiving unit 44 adds one to the number of delivery data unread in the folder Fn (for example, the area A folder F1) storing the delivery data HDn (S46).

  On the other hand, when there is no corresponding folder Fn, the distribution information receiving unit 44 adds the folder Fn with the distributor name (for example, the B area folder F2 when the read out distributor name is the B area) in the terminal memory 48. It is generated in delivery information HTn (S47).

  The delivery information receiving unit 44 adds the unread flag “1” to the delivery data HDn, and saves the created data in the generated folder Fn (for example, the B area folder F2) (S48).

  The delivery information receiving unit 44 adds one to the number of delivery data unread in the folder Fn (for example, the B area folder F2) storing the delivery data HDn (S49).

  The distribution information receiving unit 44 adds the reception time to the distribution data HDn when storing the distribution data HDn.

  The delivery information receiving unit 44 generates, in the delivery information HTn of the terminal memory 48, the folder Fn to which the deliverer name is added when the notification basic information MKn is received for the first time from the deliverer selected as the delivery request by the viewer. By doing this, the notification basic information MKn randomly received from a plurality of distributors is classified and stored for each distributor.

(Title display section 45 of the viewer terminal 40n)
Next, in the push method notification basic information distribution process shown in the sequence of FIG. 22, the distribution data HDn including the notification basic information MKn stored in the terminal memory 48 by the distribution information receiving unit 44 of the viewer terminal 40n is The detailed processing of the title display unit 45 of the viewer terminal 40 n displayed on the screen 41 of the viewer terminal 40 n will be described with reference to the flowchart of FIG.

  When the display button B4 is tapped on the screen 41 shown in (c) of FIG. 15, the title display unit 45 receives a display tap signal from the screen 41 (S51).

  The title display unit 45 reads the distribution information HTn from the terminal memory 48 (S52).

  The title display unit 45 generates a tab TGn with a distributor name corresponding to each folder Fn, and displays it on the screen 41 (S53).

  The title display unit 45 displays the number of in-folder delivery data unread in each folder Fn as the unread number on the side of the distributor name displayed on each tab TGn of the screen 41 (S54).

  The title display unit 45 lists the titles included in the distribution data HDn stored in the first folder F1 in the area of the corresponding tab TGn in accordance with the notification display color included in the distribution data HDn (S55).

  The title display unit 45 receives a tab selection tap signal from the screen 41 (S56).

  The title display unit 45 lists the titles included in the distribution data HDn stored in the folder Fn corresponding to the selected tab TGn in the area of the tab TGn according to the notification display color included in the distribution data HDn. (S57).

  The title display unit 45 also displays the reception time of the distribution data HDn when displaying the title.

  The change of the display on the screen 41 will be described with reference to FIG.

  In a state where the delivery information receiving unit 44 of the viewer terminal 40 n receives the delivery data HDn including the notification basic information MKn from only the deliverers whose deliverer name is the A area, the delivery information HTn of the terminal memory 48 includes the A area Only folder F1 is generated.

  For example, it is assumed that two distribution data HDn are stored in the A area folder F1.

  At this time, the screen image shown in (e) of FIG. 16 is displayed by the processes of steps S53 to S55 of the title display unit 45.

  That is, the tab TGa in which the area A of the distributor name is written is displayed, and the unread number is displayed as (2) in the tab TGa.

  The titles included in the two distribution data HDn stored in the A area folder F1 are listed and displayed as an announcement title Ta1 and an announcement title Ta2, respectively, in the area of the tab TGa.

  The area of the notification title Ta1, the notification title Ta2, or the tab TGa is displayed in the notification display color registered by the distributor included in the distribution data HDn.

  A delete button B6 is displayed for each of the notification titles Ta1 and Ta2.

  Further, the icon image included in the delivery data HDn is displayed as an icon Ma in the area of the tab TGa.

  Since the icon image is included in the distribution data HDn, it can be displayed on the respective notification titles Ta1 and Ta2.

  Here, when the distribution information receiving unit 44 of the viewer terminal 40 n receives the distribution data HDn including the notification basic information MKn from the distributor whose distributor name is the B area, the distribution information HTn of the terminal memory 48 is B The district folder F2 is generated, and the received distribution data HDn is stored.

  In the created B-district folder F2, the number of unread in-folder delivery data = 1 is set.

  At this time, the screen image shown in (f) of FIG. 16 is displayed by the processing of steps S53 to S55 of the title display unit 45.

  That is, the tab TGb described as the B area is displayed next to the tab TGa described as the A area of the distributor name, and the unread number is displayed as (1) in the tab TGb.

  Here, when the viewer taps the tab TGb described as the B area, the screen image shown in (f) of FIG. 16 is changed by the processes of steps S56 and S57 of the title display unit 45.

  That is, the area of the tab TGb is displayed in the foreground, and the title included in the distribution data HDn stored in the B area folder F2 is displayed together with the delete button B6 as the notification title Tb1.

  The icon image included in the distribution data HDn stored in the B area folder F2 is displayed as an icon Mb in the area of the tab TGb.

  The notification display color included in the distribution data HDn stored in the B area folder F2 is different from the notification display color included in the distribution data HDn stored in the A area folder F1, as illustrated in (f) of FIG. The area of the notification title Tb1 or tab TGb is different from the display color of the area of the notification title Ta1, the notification title Ta2, or the tab TGa, and the notification display color included in the distribution data HDn stored in the B area folder F2. Is displayed.

  In addition, when displaying the title included in the delivery data HDn in color, it is dark in the case of “1 (unread)” or “0 (read)” depending on the value of the unread flag added to the delivery data HDn. It is preferable to display light color.

(Title deletion unit 46 of the viewer terminal 40 n)
Next, in the push method notification basic information distribution process shown in the sequence of FIG. 22, the viewer terminal deletes the title displayed on the screen 41 of the viewer terminal 40n by the title display unit 45 of the viewer terminal 40n The detailed processing of the 40 n title deletion unit 46 will be described with reference to the flowchart of FIG.

  As in the screen images shown in (f) and (h) of FIG. 16, a delete button B6 is displayed on each of the notification titles Ta1, Ta2, and Tb1.

  When the viewer taps one of the delete buttons B6, the title delete unit 46 receives a delete tap signal from the screen 41 (S61).

  The title deletion unit 46 detects the corresponding folder Fn in the distribution information HTn of the terminal memory 48 from the distributor name or distributor ID of the title having the delete button B6 tapped, and from the notification ID of the corresponding title, The distribution data HDn stored in the folder Fn is detected (S62).

  The title deletion unit 46 determines the value of the unread flag added to the detected distribution data HDn (S63).

  When the value of the unread flag of the detected distribution data HDn is “1 (unread)”, the title deletion unit 46 subtracts one from the number of intra-folder distribution data unread of the corresponding folder Fn (S64).

  If the value of the unread flag of the detected distribution data HDn is “0 (read)”, the content acquisition unit 47 of the viewer terminal 40 n subtracts 1 from the number of in-folder distribution data unread in the folder Fn Because it is done, leave it as it is.

  The title deletion unit 46 deletes the distribution data HDn from the corresponding folder Fn (S65).

  The title deletion unit 46 transmits a notification deletion notification to the distribution management server 70 using the notification ID and the viewer ID of the distribution data HDn (S66).

  The notice deletion notice is transmitted to the log updating unit 107 of the database server 60 via the distribution management server 70, and the log data Gn is updated.

  When the viewer taps the delete button B6 displayed on the notification title Ta1 in the screen image shown in (f) of FIG. 16, the title deletion unit 46 deletes the distribution data HDn of the notification title Ta1 from the terminal memory 48. When the notification title Ta1 disappears and the notification title Ta1 is unread as in the screen image shown in (g) of FIG. 16, the unread number (2) displayed on the tab TGa is (1). Change to

  Here, “unread” means that the detailed information MSn of each title is not acquired by the pull method.

(Content acquisition unit 47 of viewer terminal 40n)
Next, in the pull method detailed information distribution process shown in the sequence of FIG. 23 and FIG. 24, the detailed information MSn regarding the title displayed on the screen 41 of the viewer terminal 40 n by the title display unit 45 of the viewer terminal 40 n Detailed processing will be described with reference to the flowchart in FIG. 31 for the content acquisition unit 47 of the viewer terminal 40 n that acquires the content from the distribution cloud 10.

  By tapping on the notification title Tb1 in the screen image shown in (h) of FIG. 16, the content acquisition section 47 notifies the detailed information MSn of the notification title Tb1 of the notification content as shown in (i) of FIG. It is displayed and reproduced on the screen 41 as Cb1.

  When the viewer taps one of the notification titles Ta1, Ta2, Tb1,... Displayed on the screen 41 by the title display unit 45, the content acquisition unit 47 receives a title tap signal from the screen 41 (see FIG. S71).

  The content acquisition unit 47 detects the corresponding folder Fn in the distribution information HTn of the terminal memory 48 from the distributor name or the distributor ID of the tapped title, and stores the folder Fn from the notification ID of the corresponding title The received delivery data HDn is detected (S72).

  The content acquisition unit 47 determines the value of the unread flag added to the detected distribution data HDn (S73).

  If the value of the unread flag of the detected distribution data HDn is “1 (unread)”, the content acquisition unit 47 subtracts one from the number of unread in-folder distribution data of the corresponding folder Fn (S74).

  If the value of the unread flag of the detected distribution data HDn is “0 (read)”, the detailed information MSn registered simultaneously with the notification basic information MKn included in the distribution data HDn is obtained once before. Since the number of unread in-folder delivery data of the corresponding folder Fn has already been decremented by one, it is left as it is.

  The content acquisition unit 47 distributes and manages the content type, notification ID and distribution destination viewer ID included in the distribution data HDn, and the address of the viewer terminal 40 n currently used by the viewer, for the detailed information request. It transmits to the server 70 (S75).

  The distribution management server 70 having received the detailed information request uses the content type to search the corresponding detailed information MSn for the low-capacity content distribution server 62a or the large-capacity content distribution server 63a assigned to the viewer, as a key. While sending the received notification ID and the distribution destination viewer ID, the address of the viewer terminal 40n received as the distribution destination of the retrieved detailed information MSn is also sent.

  The low-capacity content distribution server 62a transmits the received notification ID and distribution destination viewer ID to the text transmission unit 111 of the database server 60, reads out detailed information MSn including the notification ID from the server memory 204, and returns it. The transmitted detailed information MSn is transmitted to the address of the received viewer terminal 40n.

  Similarly, the large-capacity content distribution server 63a transmits the received notification ID and distribution destination viewer ID to the moving image transmission unit 113 of the storage server 61, and causes the detailed information MSn including the notification ID to be read from the storage 301 and returned. The transmitted detailed information MSn is sent to the address of the received viewer terminal 40n.

  The content acquisition unit 47 receives the detailed information MSn from the low-capacity content distribution server 62a or the large-capacity content distribution server 63a (S76).

  The content acquisition unit 47 displays and reproduces the received detailed information MSn on the screen 41 of the viewer terminal 40n as shown in (f) of FIG. 16 (S77).

  When displaying the detailed information MSn on the screen 41 of the viewer terminal 40n, the content acquisition unit 47 can also display it in the same color as the notification display color set in the distribution data HDn.

  For example, in the case of the notification content Cb1, it can be displayed in the same color as the notification display color set in the distribution data HDn of the notification title Tb1.

(Log update unit 107 of database server 60)
Next, in the push method notification basic information distribution process shown in the sequence of FIGS. 21 and 22 and the pull method detailed information distribution process shown in the sequence of FIGS. 23 and 24, the log list of the server memory 204 of the database server 60 For the log updating unit 107 of the database server 60 that updates the log data Gn created by the title distribution unit 106 of the database server 60 to the GT with the distribution status information notified from the distribution management server 70, the flowchart of FIG. Detailed processing will be described with reference to this.

  The log updating unit 107 transmits the distribution result of the notification basic information MKn and detailed information MSn notified from various distribution servers and the notification deletion notification from the viewer terminal 40 n via the distribution management server 70 to the distribution data HDn. Together with the notification ID and the distribution destination viewer ID included in the distribution information (S81).

  The log updating unit 107 detects corresponding log data Gn in the log list GT of the server memory 204 using the received notification ID and the distribution destination viewer ID as keys (S 82).

  The log updating unit 107 determines the received distribution state information, and branches the process depending on the content (S83).

  When the distribution status information is not distributed yet, the log updating unit 107 sets “distribution incomplete” in the distribution status column of the detected log data Gn (S84).

  When the delivery status information indicates delivery completion, the log updating unit 107 sets “delivery completed” in the delivery status field of the detected log data Gn, and sets the current date and time in the delivery completion date and time field (S85).

  The log updating unit 107 further searches the distribution list DT of the server memory 204 using the received notification ID and distribution destination viewer ID as keys, and deletes the distribution data HDn that has become unnecessary after the distribution is completed (S86) ).

  When the distribution state information indicates the detailed information reproduction, the log updating unit 107 adds 1 to the numerical value in the viewer reproduction number column of the log data Gn, and sets the current date and time in the latest reproduction date and time column (S87).

  When the distribution status information indicates notification deletion, the log updating unit 107 sets the current date and time in the viewer deletion date and time column of the log data Gn (S88).

  As described above, the updated log data Gn is read from the server memory 204 by the administrator terminal 20, and provided as reference history information of the notification information Mn for each distributor, so that any notification information Mn can be viewed by the viewer. It can be used for analysis that is effective for the distributor, such as

  As described above, in the first embodiment of the present invention, titles distributed by the push system from a plurality of distributors to the viewer terminal 40 n are automatically created in the terminal memory 48 and folders Fn of each distributor are created and distributed. It has the function of classifying and storing for each user, and the function of displaying the distributed title for each distributor by displaying and selecting the tab TGn for each folder Fn on the screen 41 of the viewer terminal 40n. .

Second Embodiment of the Present Invention
The configuration of the notification distribution system in the second embodiment of the present invention is the same as the configuration of the notification distribution system in the first embodiment shown in FIG.

  In the second embodiment, the distributed title is displayed by displaying the tab TGn for each folder Fn and selecting it on the screen 41 of the viewer terminal 40n, which is a feature of the first embodiment described above. Instead of or in addition to the function of displaying for each distributor, the distributed title can be displayed for each distributor according to the notification display color desired by the viewer.

  In the following, different from the first embodiment, data and processing means necessary for displaying the distributed title by the distributor according to the notification display color desired by the viewer will be described.

  The other data and processing means are the same as those in the first embodiment, and thus the description thereof is omitted.

  First, differences in data necessary for displaying the distributed title by the distributor according to the notification display color desired by the viewer will be described.

  As shown in FIG. 33, in the distributor selection list LCn in the second embodiment, the viewer is the distributor in the distributor selection list LCn in the first embodiment shown in (b) of FIG. A field for setting notification display color selection (initial value [0] or designated color value) is added for each. The designated color values are, for example, red, pink, blue, green and the like.

  Further, as shown in FIG. 34, the distribution destination list LHn by distributor in the second embodiment is the distribution destination list LHn by distributor in the first embodiment shown in FIG. 3 (b). A field for copying the notification display color selection (initial value [0] or designated color value) set for each distributor is added from the distributor selection list LCn.

  Next, the difference in the processing means necessary for displaying the distributed title by the distributor according to the notification display color desired by the viewer will be described.

  In the distributor selection and display condition setting step shown in the sequence of FIG. 20, in the first embodiment, when the display setting unit 43 of the viewer terminal 40n receives the distributor selection format, (d) of FIG. As shown in the figure, the display screen 41 of the viewer terminal 40n is displayed as a setting screen of the setting information according to distributors HSn, and the distribution period is always set as a distribution period when the distributor needs or does not want distribution selection for each distributor. Alternatively, the distribution start date and time and the distribution end date and time are set and stored in the terminal memory 48 (d60) in the second embodiment as follows.

  That is, when the display setting unit 43 of the viewer terminal 40 n receives the distributor selection format, as shown in FIG. 35, the display setting unit 43 displays it on the screen 41 of the viewer terminal 40 n as a setting screen of the distributor-specific setting information HSn For each distributor, for each distributor, the user is required to set the distribution start date / time and distribution end date / time as the distribution period, if necessary, and the display color specified by the distributor for the distributed title. When it is acceptable to display at the initial value [0] and when the display is desired to be displayed in the display color desired by the viewer, the designated color value is set as notification display color selection and stored in the terminal memory 48 (d60).

  In the screen image of FIG. 35, a column of notification display color selection is displayed in the distributor-specific setting information HSn. For example, for a distributor whose distributor name is A area, an initial value is selected as notification display color selection. For a distributor whose distributor name is B area, "red" is set as a designated color as notification display color selection.

  The distributor-specific setting information HSn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution period, notification display color selection) set by the display setting unit 43 of the viewer terminal 40 n is It is stored in the distributor selection list LCn shown in FIG. 33 by the distributor setting unit 110 of the database server 60.

  Further, the distributor setting unit 110 of the database server 60 sets the distribution destination list LHn by distributor shown in FIG.

(Distributor setting unit 110 of database server 60)
Here, although the distributor setting unit 110 of the database server 60 in the second embodiment is shown in the flowchart of FIG. 36, the distributor setting unit 110 of the database server 60 in the first embodiment shown in FIG. And the difference is that step S119a is added. The other steps from S111 to S120 in FIG. 36 are the same as the steps from S11 to S20 in FIG.

  The distributor setting unit 110 receives the distributor selection format request from the display setting unit 43 of the viewer terminal 40 n via the distribution management server 70 (S 111).

  The distributor setting unit 110 reads out distributor registration information Hn stored in the distributor information database 201 (S112).

  As shown in FIG. 3A, in the distributor registration information Hn, distributor IDs and distributor names of all distributors are registered as a list, and the distributor setting unit 110 distributes the distributors. A distributor selection format is created in which all the distributor IDs and distributor names registered in the registration information Hn are set (S113).

  The distributor selection format has the same format as the distributor selection list LCn shown in FIG. 33, and the viewer ID of the viewer who has requested the distributor selection format is set to the nth viewer ID, and distribution is further performed. The first distributor ID and the first distributor name, the second distributor ID and the second distributor name, all the distributor IDs and the distributor names registered in the distributor registration information Hn, The nth distributor ID and the nth distributor name are set and created.

  The distributor setting unit 110 transmits the generated distributor selection format to the viewer terminal 40 n via the distribution management server 70 (S 114).

  As described above, when the display setting unit 43 of the viewer terminal 40n receives the distributor selection format, as shown in FIG. 35, the display setting unit 43 displays the setting screen for the distributor-specific setting information HSn on the screen 41 of the viewer terminal 40n. If the viewer wants or does not want to select a delivery option for each of the distributors, the delivery period is always set as the delivery period, or the delivery start date and the delivery end date are set, and the distributor specifies the delivered title. When the display color is acceptable, the initial value [0] is desired. When the viewer wishes to display the desired display color, the designated color value is set as notification display color selection, stored in the terminal memory 48, and set. The distribution information per setter HSn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution period, notification display color selection) is transmitted to the distribution management server 70.

  The distributor setting unit 110 receives, via the distribution management server 70, the distributor-specific setting information HSn for which the viewer has set distribution selection and display conditions (distribution period and notification display color selection) in the distributor selection format. (S115).

  The distributor setting unit 110 distributes the received distributor setting information HSn to the distributor selection list LCn (a viewer ID, a distributor ID, a distributor name, a distribution selection (unnecessary, desired), and a distributor selection) of the viewer information database 202 In the period, the notification display color is selected (S116).

  The distributor setting unit 110 sequentially reads one record of data related to each distributor in the set distributor selection list LCn (S117).

  That is, the record set for the first distributor ID in the first process, the record set for the second distributor ID in the second process, ..., the nth distributor in the nth process The records set for the ID and one record each time the process is repeated are read.

  The distributor setting unit 110 determines whether the distribution selection of the distributor is unnecessary or desired (S118).

  If the distribution selection by the distributor is desired, the distributor setting unit 110 associates the distributor ID of the distributor in the distributor information database 201 with the distribution destination list by distributor shown in FIG. 34. The LHn is searched, the viewer ID set in the distributor selection list LCn is added as a distribution destination viewer ID, and the data of the distribution period of the read out record is copied and set (S119).

  Further, the distributor setting unit 110 copies data of notification display color selection of the read out record and sets it in the distributor-specific distribution destination list LHn (S119a).

  The distributor setting unit 110 determines whether there is a next record, and if there is, it returns to the processing of S117, and if there is not, the processing ends (S200).

  In addition, in the push method notification basic information distribution process shown in the sequences of FIGS. 21 and 22, the distribution data extraction unit 105 of the database server 60 that creates the distribution data HDn also includes the distribution data extraction unit in the first embodiment. There is a difference from 105.

(Distributed Data Extraction Unit 105 of Database Server 60)
The delivery data extraction unit 105 of the database server 60 in the second embodiment is shown in the flowchart of FIG. 37, but the difference from the delivery data extraction unit 105 of the database server 60 in the first embodiment shown in FIG. Is that data of the notification display color selection is added to the record read out from the distributor-specific distribution destination list LHn, so steps S128a and S128b related to the notification display color selection are added.

  The other steps from S121 to S130 in FIG. 37 are the same as the steps from S21 to S30 in FIG.

  The distribution data extraction unit 105 measures time using a timer (not shown) built in the database server 60, and repeatedly starts the following processing after waiting for a predetermined time set in advance (S121).

  The distribution data extraction unit 105 sequentially reads out the notification basic information MKn newly stored in the server memory 204 during a predetermined time (S122).

  That is, reading the notification basic information MK1, the notification basic information MK2, the notification basic information MK3,... Shown in FIG. 6 one by one, the following process is performed on the read notification basic information MKn.

  The distribution data extraction unit 105 reads the distribution specification date of the notification basic information MKn when the data of the distribution timing of the notification basic information MKn is “1: date specification”, that is, when the distribution specification date is set (S123) ).

  The delivery data extraction unit 105 reads out the distributor ID set in the notification basic information MKn (S124).

  The distribution data extraction unit 105 searches the distributor ID distribution destination list LHn stored in the distributor information database 201 with the distributor ID (S125).

  The distribution data extraction unit 105 sequentially reads one record (distribution destination viewer ID and distribution period) set in the distribution list by distributor LHn (S126).

  That is, in the first processing, the first distribution destination viewer ID, distribution period, and notification display color selection, and in the second processing, the second distribution destination viewer ID distribution destination viewer ID, distribution period, and notification display In the color selection,..., N-th processing, the nth distribution destination viewer ID, distribution period, and notification display color selection are read out one record at a time each time the processing is repeated.

  If there is a distribution period included in the read out record, the current date or time, or the designated distribution date and time read out from the notification basic information MKn, the distribution data extraction unit 105 compares the designated distribution date and time, and within the distribution period. It is determined whether there is any (S127).

  The delivery data extraction unit 105 creates the delivery data HDn by adding the delivery destination viewer ID included in the read record to the read notification basic information MKn only when it is within the delivery period, and creates the delivery data HDn. Save to DT (S128).

  That is, only the notification information Mn for which the viewer of the distribution destination viewer ID included in the read out record has reached the distribution period for which distribution is desired is extracted and becomes distribution data HDn to the corresponding viewer.

  In addition, since the start date and the end date are always set in the delivery period, in the case of the constant, the delivery period is always treated.

  The distribution data extraction unit 105 determines whether the designated color value is set in the notification display color selection included in the read record (S128a).

When the designated color value is set to the notification display color selection, the distribution data extraction unit 105 specifies the notification display color included in the distribution data HDn created in step S128 and stored in the distribution list DT of the server memory 204. It rewrites to a color value (S128b).
That is, when the viewer specifies the notification display color, the notification display color set by the distributor is set to the distribution data HDn changed to the display color specified by the viewer, and the data of notification display color selection is the initial value In the case of [0], nothing is done because the notification display color set by the distributor may be left as it is.

  The distribution data extraction unit 105 determines whether there is a next record in the distribution list by distributor LHn, and if there is a next record, the process returns to the process of S126 (S129).

  When the processing of steps S127, S128, S128a, and S128b is performed on all the records of the distributor-specific distribution destination list LHn, the distribution data extraction unit 105 determines whether the server memory 204 has the next notification basic information MKn, In the case, the process returns to the process of step S122, and in the case of no, the process is once ended, and the process shifts to the waiting state of S21 (S130).

  After that, the distribution data HDn created by the distribution data extraction unit 105 is transmitted to the viewer terminal 40 n by the title distribution unit 106 of the database server 60 as shown in the sequence of FIG. 21 and FIG. The distribution information receiving unit 44 of the terminal 40 n stores the distribution information HTn of the terminal memory 48.

  Furthermore, the delivery information HTn of the terminal memory 48 is displayed on the screen 41 by the title display unit 45 of the viewer terminal 40n.

  In the first embodiment, as described above with reference to the flowchart in FIG. 29 for the detailed process of the title display unit 45, the title display unit 45 includes the titles included in the distribution data HDn stored in the folder Fn. Are listed and displayed in the area of the corresponding tab TGn in accordance with the notification display color included in the distribution data HDn.

  In the first embodiment, the notification display color included in the distribution data HDn is the notification display color set by the distributor, while in the second embodiment, the viewer selects the notification display color. If the designated color value is set, the notification display color included in the delivery data HDn is changed to the designated color value and transmitted from the delivery cloud 10.

  Therefore, even if the title display unit 45 performs the same processing as in the first embodiment, the notification display color set by the distributor or the designated color designated by the viewer is a color desired by the viewer. It will display the title.

  In the first embodiment, in the screen image shown in (f) of FIG. 16, the area of the A area tab TGa including the notification titles Ta1 and Ta2 and the area B tab TGb are shown in (h) of FIG. In the screen image, the area of the B area tab TGb including the A area tab TGa and the notification title Tb1 is displayed in the display color set by the A area distributor and the area distributor, respectively.

  On the other hand, in the second embodiment, as shown in (a) of FIG. 38, the A area tab TGa is displayed in the display color set by the A area distributor, and the notification title Tb1 is displayed by the viewer. It is displayed in the color specified as the notification display color, for example, in red.

  The area of the B area tab TGb may also be displayed in a color designated by the viewer as the notification display color.

  Further, the title display unit 45 is changed, and a tab TGn having a distributor name corresponding to each folder Fn is not generated, and all distribution data HDn stored in the distribution information HTn are not divided for each distributor. It is also possible to display a list in chronological order from the delivery data HDn having the latest reception time.

  As shown in (b) of FIG. 38, the viewer can view all notification titles Ta1, Ta2, Tb1, Ta3,... From a plurality of distributors on one screen without creating the tab TGn. By designating in advance the notification display color of the distribution data HDn from a specific distributor and displaying it in the specified color, for example, in red, it is possible for the viewer to easily identify from which distributor.

  At this time, icon images symbolizing the distributor included in the distribution data HDn are displayed as icons Ma and Mb in the respective notification titles Ta1, Ta2, Tb1 and Ta3.

  As described above, since the viewer can set the color for displaying the title for each distributor, it is possible for the viewer to realize the viewer's request, such as designating a prominent color for the distributor's title that he wants to read.

  Therefore, for example, the main member moves from Matsue (District A) to Chiyoda Ward (District B) in Tokyo during the traffic period at 10:00 on September 10, 2014 at 15:00 on Sep 10, 2014. If you arrive at, set the delivery date from B area from 15:00 to 19:00 on September 10, 2014, and if you set the color to red, the notification from B area will be red Can be received by

  Therefore, if you want to see only the notice of B area, if the display color of the notice title is red, it is known that it is the notice title distributed from B area, so if you read only the notice title displayed in red Well, it is not necessary to read the contents of all the notice titles and check whether it is from the B area or not.

  In addition, if you want to see only the notification of B area when A area is set to receive on the same delivery date and time, A area is set to be different in color (for example, green) from B area (red). If it is stored, it is easy to recognize that the notice title is from B area when the red notice title is displayed ignoring the green notice title.

<Other Embodiments of the Present Invention>
In the notification distribution system according to another embodiment of the present invention, the distributor adds a display frame type for setting the notification type of the notification information Mn and the title display format for each notification type to the notification basic information MKn, and the viewer notifies Distributor setting information HSn (viewer ID, distributor ID, distributor name, distribution selection (unnecessary, desired), distribution period, notification) with display frame selection type data capable of selecting the title display format for each type as display conditions Add to Display color selection).

  For example, the value of the notification type of the notification information Mn is “0 (general information)”, “1 (event information)”, “2 (weather information)”, or “3 (warning information)”.

  Further, for the display frame type for setting the title display format and the display frame data to be set for the display frame selection type for selecting the title display format, "display frame for notification title Ta1 illustrated in (b) of FIG. The display frame of the notification title Ta2 is "display frame 2", the display frame of the notification title Ta3 is "display frame 3", and the display frame of the notification title Ta4 is "display frame 4".

  When the distributor inputs the notification information Mn from the distributor terminal 30n, the display type of the notification type of the notification information Mn to be registered and the display frame of the decoration frame when displaying the title of the notification information Mn on the viewer terminal 40n The type is set to the notification basic information MKn.

  That is, in addition to the notification display color, the notification ID, the distributor ID, and the title, the notification basic information MKn includes the notification type and the display frame type.

  On the other hand, in the distributor selection format transmitted from the database server 60 by the display setting unit 43 of the viewer terminal 40 n, the viewer wants to display in which display frame for each notification type for each distributor who wants distribution. The display frame selection type is set, and the set per-distributor setting information HSn is returned to the database server 60.

  If the viewer does not agree with the setting of the distributor, the viewer sets "default: 0" as the display frame selection type.

  That is, in addition to the viewer ID, the distributor ID, the distributor name, the distribution selection (unnecessary, desired), the distribution period, and the notification display color selection, the first notification type and its display are included in the distributor-specific setting information HSn. A frame selection type, a second notification type and its display frame selection type, a third notification type and its display frame selection type, and so on are included.

  The distributor setting unit 110 of the database server 60 sets the first notification type and its display frame selection type, the second notification type, and its display frame selection set in the distributor-specific setting information HSn received from the viewer terminal 40 n. The type, the third notification type, and the display frame selection type,... Are set in the distribution destination list LHn by distributor similarly to the data of the distribution period and the notification display color selection described above.

  In the distribution data extraction unit 105 of the database server 60, the display frame selection type included in the distributor-specific distribution destination list LHn for the notification type set in the notification basic information MKn is not “initially 0:” but a display frame When data is set, data of the display frame type included in the distribution data HDn stored in the distribution list DT of the server memory 204 is rewritten to data of the display frame selection type.

  That is, in the distribution data HDn, in addition to the notification ID, the distributor ID, the distribution destination viewer ID, the distributor name, the icon image, the notification display color, the title, the content type, the distribution time, and the distribution specification date and time, The display frame type set by the distributor or the display frame type overwritten by the data of the display frame selection type selected by the viewer is included.

  The distribution data HDn distributed to the viewer terminal 40 n by the title distribution unit 106 of the database server 60 is stored in the corresponding folder Fn of the distribution information HTn of the terminal memory 48.

  The title display unit 45 of the viewer terminal 40n displays the title included in the distribution data HDn stored in the folder Fn corresponding to the selected tab TGn with the decoration frame specified by the display frame type included in the distribution data HDn Then, it displays in the area of the tab TGn.

  A specific display example will be described with reference to the display image of the notification title on the screen 41 by the title display unit 45 of the viewer terminal 40n shown in FIG.

  FIG. 39A shows an example other than the display format of the tab TGn to which the distributor name shown in FIG. 16 is added.

  When the basic information MKn of the notification information Mn is received as distribution data HDn from the distributor who the viewer wishes to distribute, the distributor's name of the distributor and the unread number of the received distribution data HDn are displayed. Instead of displaying the tabs TGn in a single horizontal row as shown in (f) of FIG. 16, the tabs TGn are displayed side by side in a table of a column × horizontal row in the screen of the distributor notification status.

  In (a) of FIG. 39, there are four unannounced notices from the distributor in the A area, the tab TGa shown in green designated by the viewer in the notification display color selection, and the B area next to the tab TGa. There are 5 unread notices from the X city distributor under the tab TGb shown in red that the viewer has specified in the notification display color selection that there is 1 unread notification from the distributors of A tab TGc is displayed in blue, which is set by the distributor of X city as the notification display color.

  In (a) of FIG. 39, the tab TGx indicated by a dotted line is that the viewer further selects a distribution request and a new distributor, and receives the notification basic information MKn of the notification information Mn from the distributor as the distribution data HDn. In the case, it is newly added.

  The display format of (a) in FIG. 39 is also possible in the second embodiment, and in the first embodiment, the display color may be limited to the notification display color set by the distributor. It is preferable to be able to select which of the display format shown in (f) of 16 and the display format shown in (a) of FIG.

  As shown in (b) of FIG. 39, in the display state when the viewer taps and selects the tab TGa in the display state of (a) of FIG. The notification titles Ta1, Ta2, Ta3 and Ta4 are displayed on the screen of the A area notification title.

  Here, for example, in the distribution data HD1 of the notification title Ta1, the notification type "0 (general information)", the display frame type "display frame 1", and the distribution data HD2 of the notification title Ta2 notification type "1 (event information) "And display frame type" display frame 2 ", distribution data HD3 of notification title Ta3 notification type" 2 (weather information) "and display frame type" display frame 3 ", and distribution data HD4 of notification title Ta4 It is assumed that the type “3 (warning information)” and the display frame type “display frame 4” are set.

  Since the title display unit 45 of the viewer terminal 40 n displays each title according to the display frame type, as shown in (b) of FIG. 39, “display frames different from each other in the notification titles Ta1, Ta2, Ta3 and Ta4 1 ”,“ display frame 2 ”,“ display frame 3 ”, and“ display frame 4 ”.

  Further, by adding data for selecting a display color for each notice type, various combinations of display methods of the notice title on the screen 41 by the title display unit 45 of the viewer terminal 40 n become possible.

  Also in the first embodiment and the second embodiment, the display image shown in FIG. 16 is an example, and the decorative frame shown in (b) of FIG. 39 is used instead of the decorative frame shown in FIG. Can be adopted as a notice delivery system.

  The embodiment described above exemplifies the configuration and processing procedure of a system for embodying the technical idea of the present invention, and limits the arrangement and combination of configuration servers, the order of processing, and the like. It is not a thing.

  Various changes can be added to the technical idea of the present invention within the technical scope described in the claims. It should be noted that the drawings are schematic and the configuration of the server is different from the actual one.

DESCRIPTION OF SYMBOLS 10 Cloud for distribution 20 Administrator terminal 30a, 30b Distributor terminal 40n Viewer terminal 41 Screen 42 Session establishment part 43 Display setting part 44 Distribution information receiving part 45 Title display part 46 Title deletion part 47 Content acquisition part 48 Terminal memory 50 System Management server 60 Database server 61 Storage server 62a, 62b Low capacity content distribution server 63a, 63b Large capacity content distribution server 70 Distribution management server 80 Session establishment server 81a, 81b Notification distribution server 101 Distributor registration unit 102 Distributor authentication unit 103 Input Screen providing unit 104 Notification information registration unit 105 Distribution data extraction unit 106 Title distribution unit 107 Log updating unit 108 Viewer registration unit 109 Viewer authentication unit 110 Distributor setting unit 111 Text transmission unit 112 Video registration unit 11 Video transmission unit 201 the distribution information database 202 the viewer information database 203 screen configuration information master 204 server memory 301 storage

Claims (14)

Consisting of a distribution cloud (10), an administrator terminal (20) connected to the distribution cloud (10) via the Internet network N, distributor terminals (30a, 30b), and a viewer terminal (40n) Notification distribution system, and
The distribution cloud (10) is
A database server (60), a distribution management server (70) connected to the database server (60), and an announcement distribution server (81a, 81b) connected to the distribution management server (70);
The database server (60) is
A distributor information database (201) in which distributor registration information (Hn) to which a distributor ID is assigned and a distributor-specific distribution destination list (LHn) associated with the distributor ID are stored;
A viewer information database (202) in which viewer registration information (Cn) to which a viewer ID is assigned and a distributor selection list (LCn) associated with the viewer ID are stored;
A server memory (204) in which notification basic information (MKn) included in notification information Mn to which a notification ID is assigned is registered;
A distributor selection format in which all the distributor IDs and distributor names registered in the distributor registration information (Hn) are set is transmitted to the viewer terminal (40n).
The distributor selection information (HSn) with distribution selection and distribution period set in the distributor selection format returned from the viewer terminal (40n), the distributor selection list of the viewer information database (202) Save to (LCn),
The viewer ID set in the distributor selection list (LCn) in the distributor-specific distribution destination list (LHn) corresponding to the distributor ID selected as the distribution desired by the distribution selection is the distribution destination viewer A distributor setting unit (110) for adding as an ID and further setting the distribution period;
The distribution destination viewer ID and the distribution period are read out from the distribution destination list by distributor (LHn) corresponding to the distributor ID included in the notification basic information MKn every fixed time, and within the distribution period The distribution data extraction unit (105) creates distribution data (HDn) by adding the notification basic information MKn to the distribution destination viewer ID, and stores the distribution data (HDn) in the distribution list (DT) of the server memory (204). When,
It includes a title distribution unit (106) which reads out the distribution data (HDn) stored in the distribution list (DT) at regular time intervals and transmits the data to the distribution management server (70).
The delivery management server (70) is
Means of transferring the distribution data (HDn) transmitted from the database server (60) to the notification distribution server (81a, 81b) assigned to the distribution destination viewer ID included in the distribution data (HDn) Including
The notice distribution server (81a, 81b)
It includes means for distributing the distribution data (HDn) transmitted from the distribution management server (70) to the viewer terminal (40n) of the distribution destination viewer ID included in the distribution data (HDn),
The viewer terminal (40n) is
Terminal memory (48),
The distributor specific setting information (HSn) in which the distribution selection and the distribution period are set in the distributor selection format received from the database server (60) is stored in the terminal memory (48), and the database A display setting unit (43) that replies to the server (60);
Receiving the distribution data (HDn) distributed from the notification distribution server (81a);
When a folder (Fn) with the distributor name included in the distribution data (HDn) is already created in the terminal memory (48), an unread flag "1" is added to the distribution data (HDn) Save in the folder (Fn),
A distribution information receiving unit (44) for creating and storing a folder (Fn) to which the distributor name is newly added, if not created;
A tab (TGn) with the distributor name corresponding to the folder (Fn) created in the terminal memory (48) is generated, and is stored in the folder (Fn) in the area of the tab (TGn). A notification distribution system comprising: a title display section (45) for displaying a list of titles of the distribution data (HDn) according to a notification display color included in the distribution data (HDn). The distribution cloud (10) is
A storage server (61) connected to the database server (60), a low capacity content distribution server (62a, 62b) connected to the database server (60) and the distribution management server (70), and the storage server (61) and a large capacity content distribution server (63a, 63b) connected to the distribution management server (70);
The database server (60) is
The notification basic information (MKn) to which the notification ID is added among the notification basic information (MKn) and the detailed information included in the notification information (Mn) input from the distributor terminal (30a, 30b) The content type of the detailed information (MSn) is stored in the server memory (204), and the content type of the detailed information (MSn) is determined. If the capacity is low, the detailed information (MSn) to which the notification ID is added is stored in the server memory (204). If it is a large capacity, the notification information registration unit (104) for transmitting the detailed information (MSn) to which the notification ID is assigned to the storage server (61) and details from the viewer terminal (40n) An information request is received via the distribution management server (70) and the low-capacity content distribution server (62a, 62b), and the notification ID is included in the detailed information request, And a text transmitting unit (111) for searching and reading the detailed information (MSn) of the server memory (204) and transmitting the detailed information (MSn) to the low capacity content distribution server (62a, 62b);
The storage server (61) is
A storage (301) for storing the detailed information MSn to which the notification ID is assigned;
A moving picture registration unit (112) for storing the detailed information (MSn) received from the database server (60) in the storage (301);
The notification contained in the detailed information request is received by the detailed information request from the viewer terminal (40n) via the distribution management server (70) and the large-capacity content distribution server (63a, 63b) A moving image transmission unit (113) for searching and reading the detailed information (MSn) of the storage (301) by an ID, and transmitting the detailed information (MSn) to the large-capacity content distribution server (63a, 63b);
The low capacity content distribution server (62a, 62b) and the large capacity content distribution server (63a, 63b)
Means for distributing the received detailed information (MSn) to the viewer terminal (40n) according to the address of the viewer terminal (40n) included in the detailed information request,
The viewer terminal (40n) is
The distribution data (HDn) stored in the corresponding folder (Fn) is detected from the notification ID of the title and the distributor ID, and the content type, the notification ID and the content included in the distribution data (HDn) are detected. The detailed information request including the distribution destination viewer ID and the address of the viewer terminal (40n) is transmitted to the distribution management server (70), and the low capacity content distribution server (62a) or the large capacity The notification distribution system according to claim 1, further comprising a content acquisition unit (47) which receives the detailed information (MSn) returned from the content distribution server (63a) and displays / plays back the detailed information (MSn). The database server further includes a log update unit (107),
The title distribution unit (106), for the distribution data (HDn) to be transmitted to the distribution management server (70) for the first time, the notification ID, the distributor ID, and the distribution destination viewing included in the distribution data (HDn) Create a log data (Gn) in which the delivery ID is set to “in delivery” in the delivery ID, and save it in the log list (GT) of the server memory (204);
The log updating unit (107)
When distribution status information is notified from the distribution management server (70) together with the notification ID and the distribution destination viewer ID, the log of the server memory (204) is displayed by the notification ID and the distribution destination viewer ID. The notice distribution system according to claim 1 or 2, wherein the corresponding log data (Gn) is detected from the list (GT), and the log data (Gn) is updated by the data of the distribution state information. . The database server (60) further includes a distributor registration unit (101);
The distributor registration unit (101) uses distributor information input from the administrator terminal (20) as the distributor registration information (Hn) to which the distributor ID for identifying a distributor is added. An area of the distributor-specific distribution destination list (LHn) stored in the distributor information database (201) and associated with the distributor registration information (Hn) and the distributor ID is the distributor information database (201). The notification delivery system according to any one of claims 1 to 3, characterized in that: The database server (60) further includes a viewer registration unit (108);
The viewer registration unit (108) uses the viewer information input from the viewer terminal (40n) as the viewer registration information (Cn) to which the viewer ID for identifying the viewer is added. The area of the distributor selection list (LCn) stored in the viewer information database (202) and associated with the viewer registration information (Cn) and the viewer ID is set in the viewer information database (202) The notification delivery system according to any one of claims 1 to 4, characterized in that: The display setting unit (43) returns, to the database server (60), the distributor-specific setting information (HSn) in which notification display color selection is further set in the distributor selection format.
The distributor setting unit (110) sets the notification display color selection set in the distributor-specific setting information (HSn) in the viewer terminal (40n) in the distributor-specific distribution destination list (LHn) And
When the designated color value is set in the notification display color selection included in the distributor-specific distribution destination list (LHn), the distribution data extraction unit (105) is configured to transmit the distribution list of the server memory (204) The notification distribution system according to any one of claims 1 to 5, wherein the notification display color included in the distribution data (HDn) stored in DT) is rewritten to the specified color value. The notification basic information (MKn) further includes a notification type and a display frame type,
The display setting unit (43) returns, to the database server (60), the distributor-specific setting information (HSn) in which a display frame selection type for each notification type is further set in the distributor selection format.
The distributor setting unit (110) sets the display frame selection type for each notification type set in the distributor-specific setting information (HSn) in the viewer terminal (40n) to the distributor-specific distribution destination list Set to (LHn),
The distribution data extraction unit (105) sets the notification type set in the notification basic information (MKn) included in the distribution data (HDn) stored in the distribution list (DT) of the server memory (204). On the other hand, when display frame data is set in the display frame selection type included in the distributor-specific distribution destination list (LHn), the display frame type included in the distribution data (HDn) is selected as the display frame selection. Rewrite the display frame data set to the type,
The title display unit (45) displays the title included in the distribution data (HDn) with the display frame of the display frame data set to the display frame type included in the distribution data (HDn). The notice distribution system according to any one of claims 1 to 6, which is characterized by the above. A notification distribution system using a distribution cloud (10) connected to an administrator terminal (20), a distributor terminal (30a, 30b), and a viewer terminal (40n) via an Internet network N,
The distribution cloud (10) is
A database server (60), a distribution management server (70) connected to the database server (60), and an announcement distribution server (81a, 81b) connected to the distribution management server (70);
The database server (60) is
A distributor information database (201) in which distributor registration information Hn to which a distributor ID is assigned and a distributor-specific distribution destination list (LHn) associated with the distributor ID are stored;
A viewer information database (202) in which viewer registration information Cn to which a viewer ID is assigned, and a distributor selection list (LCn) associated with the viewer ID are stored;
A server memory (204) in which notification basic information (MKn) included in notification information Mn to which a notification ID is assigned is registered;
A distributor selection format in which all distributor IDs and distributor names registered in the distributor registration information (Hn) are set is transmitted to the viewer terminal (40n).
The distributor selection information (HSn) with distribution selection and distribution period set in the distributor selection format returned from the viewer terminal (40n), the distributor selection list of the viewer information database (202) Save to (LCn),
The viewer ID set in the distributor selection list (LCn) in the distributor-specific distribution destination list (LHn) corresponding to the distributor ID selected as the distribution desired by the distribution selection is the distribution destination viewer A distributor setting unit (110) for adding as an ID and further setting the distribution period;
The distribution destination viewer ID and the distribution period are read out from the distribution destination list by distributor (LHn) corresponding to the distributor ID included in the notification basic information MKn every fixed time, and within the distribution period If there is, distribution data (HDn) is created by adding the notification basic information (MKn) to the distribution destination viewer ID, and the distribution data extraction unit (d) stores the distribution data (HD) in the server memory (204). 105),
A title distribution unit (106) which reads out the distribution data (HDn) stored in the distribution list (DT) at regular time intervals and transmits the data to the distribution management server (70);
A program provision unit (not shown) for providing the program for receiving the notification information (Mn) stored in the server memory (204) to the viewer terminal (40n);
The delivery management server (70) is
Means of transferring the distribution data (HDn) transmitted from the database server (60) to the notification distribution server (81a, 81b) assigned to the distribution destination viewer ID included in the distribution data (HDn) Including
The notice distribution server (81a, 81b)
It includes means for distributing the distribution data (HDn) transmitted from the distribution management server (70) to the viewer terminal (40n) of the distribution destination viewer ID included in the distribution data (HDn),
The program is
In the CPU of the viewer terminal (40n),
A terminal mounted on the viewer terminal (40n) with the distributor-specific setting information (HSn) in which the distribution selection and the distribution period are set in the distributor selection format received from the database server (60) A display setting unit (43) which is stored in a memory (48) and returned to the database server (60);
Receiving the distribution data (HDn) distributed from the notification distribution server (81a);
When a folder (Fn) with the distributor name included in the distribution data (HDn) is already created in the terminal memory (48), an unread flag "1" is added to the distribution data (HDn) Save in the folder (Fn),
A distribution information receiving unit (44) for creating and storing a folder (Fn) to which the distributor name is newly added, if not created;
A tag (TGn) with the distributor name corresponding to the folder (Fn) created in the terminal memory (48) is generated, and is stored in the folder (Fn) in the area of the tag (TGn). A title display section (45) for displaying a list of titles of the distribution data (HDn) according to the notification display color included in the distribution data (HDn)
An announcement distribution system characterized in that the function is executed. The distribution cloud (10) is
A storage server (61) connected to the database server (60), a low capacity content distribution server (62a, 62b) connected to the database server (60) and the distribution management server (70), and the storage server (61) and a large capacity content distribution server (63a, 63b) connected to the distribution management server (70);
The database server (60) is
The notification basic information (MKn) to which the notification ID is added among the notification basic information (MKn) and the detailed information included in the notification information (Mn) input from the distributor terminal (30a, 30b) The content type of the detailed information (MSn) is stored in the server memory (204), and the content type of the detailed information (MSn) is determined. If the capacity is low, the detailed information (MSn) to which the notification ID is added is stored in the server memory (204). If it is a large capacity, the notification information registration unit (104) for transmitting the detailed information (MSn) to which the notification ID is assigned to the storage server (61) and details from the viewer terminal (40n) An information request is received via the distribution management server (70) and the low-capacity content distribution server (62a, 62b), and the notification ID is included in the detailed information request, And a text transmitting unit (111) for searching and reading the detailed information (MSn) of the server memory (204) and transmitting the detailed information (MSn) to the low capacity content distribution server (62a, 62b);
The storage server (61) is
A storage (301) for storing the detailed information MSn to which the notification ID is assigned;
A moving picture registration unit (112) for storing the detailed information (MSn) received from the database server (60) in the storage (301);
The notification contained in the detailed information request is received by the detailed information request from the viewer terminal (40n) via the distribution management server (70) and the large-capacity content distribution server (63a, 63b) A moving image transmission unit (113) for searching and reading the detailed information (MSn) of the storage (301) by an ID, and transmitting the detailed information (MSn) to the large-capacity content distribution server (63a, 63b);
The low capacity content distribution server (62a, 62b) and the large capacity content distribution server (63a, 63b)
Means for distributing the received detailed information (MSn) to the viewer terminal (40n) according to the address of the viewer terminal (40n) included in the detailed information request,
The program is
In the CPU of the viewer terminal (40n),
The distribution data (HDn) stored in the corresponding folder Fn is detected from the notification ID of the title and the distributor ID, and the content type, the notification ID, and the distribution included in the distribution data (HDn) The detailed information request including the destination viewer ID and the address of the viewer terminal (40n) is transmitted to the distribution management server (70), and the low-capacity content server (62a) or the large-capacity content server ( The notice distribution system according to claim 8, characterized in that the detailed information (MSn) returned from 63a) is received to execute a function as a content acquisition unit (47) for displaying and reproducing. The database server further includes a log update unit (107),
The title distribution unit (106), for the distribution data (HDn) to be transmitted to the distribution management server (70) for the first time, the notification ID, the distributor ID, and the distribution destination viewing included in the distribution data (HDn) Create a log data (Gn) in which the delivery ID is set to “in delivery” in the delivery ID, and save it in the log list (GT) of the server memory (204);
The log updating unit (107)
When distribution status information is notified from the distribution management server (70) together with the notification ID and the distribution destination viewer ID, the log of the server memory (204) is displayed by the notification ID and the distribution destination viewer ID. The notice distribution system according to claim 8 or 9, wherein the corresponding log data (Gn) is detected from the list (GT), and the log data (Gn) is updated by the data of the distribution state information. . The database server (60) further includes a distributor registration unit (101);
The distributor registration unit (101) uses distributor information input from the administrator terminal (20) as the distributor registration information (Hn) to which the distributor ID for identifying a distributor is added. An area of the distributor-specific distribution destination list (LHn) stored in the distributor information database (201) and associated with the distributor registration information (Hn) and the distributor ID is the distributor information database (201). The notification delivery system according to any one of claims 8 to 10, wherein The database server (60) further includes a viewer registration unit (108);
The viewer registration unit (108) uses the viewer information input from the viewer terminal (40n) as the viewer registration information (Cn) to which the viewer ID for identifying the viewer is added. The area of the distributor selection list (LCn) stored in the viewer information database (202) and associated with the viewer registration information (Cn) and the viewer ID is set in the viewer information database (202) The notification delivery system according to any one of claims 8 to 11, characterized in that: The program sets the distributor-specific setting information (HSn) in which notification display color selection is further set in the distributor selection format by the display setting unit (43) in the CPU of the viewer terminal (40n). Execute a function to make the database server (60) reply.
The distributor setting unit (110) selects the notification display color selection set in the distributor-specific setting information (HSn) received from the viewer terminal (40n) according to the distributor-specific distribution destination list (LHn). Set to
When the designated color value is set in the notification display color selection included in the distributor-specific distribution destination list (LHn), the distribution data extraction unit (105) is configured to transmit the distribution list of the server memory (204) The notification distribution system according to any one of claims 8 to 12, wherein the notification display color included in the distribution data (HDn) stored in DT) is rewritten to the specified color value. The notification basic information (MKn) further includes a notification type and a display frame type,
The program causes the CPU of the viewer terminal (40n) to
Causing the database server (60) to return the distributor specific setting information (HSn) in which the display frame selection type for each notification type is further set in the distributor selection format by the display setting unit (43);
The title display unit (45) executes a function of displaying a title included in the distribution data (HDn) with a display frame of display frame data set to the display frame type included in the distribution data (HDn) Let
The distributor setting unit (110) sets the display frame selection type for each notification type set in the distributor-specific setting information (HSn) in the viewer terminal (40n) to the distributor-specific distribution destination list Set to LH n
The distribution data extraction unit (105) sets the notification type set in the notification basic information (MKn) included in the distribution data (HDn) stored in the distribution list (DT) of the server memory (204). On the other hand, when display frame data is set in the display frame selection type included in the distributor-specific distribution destination list (LHn), the display frame type included in the distribution data (HDn) is selected as the display frame selection. The notification distribution system according to any one of claims 8 to 13, wherein the display frame data set to the type is rewritten.