JP6163094B2 - Message delivery system, message delivery method, and message delivery program - Google Patents

Description

  The present invention relates to a message delivery system, a message delivery method, and a message delivery program for delivering a message to a plurality of devices.

  As a technique for delivering a message, Patent Document 1 describes a push-type message delivery system. In Patent Document 1, when push distribution is performed from a plurality of servers to a plurality of client systems, the distribution information is collected and the collected information is edited in order to solve the problem that the traffic increases and the network becomes congested. In addition, by distributing to the client system, system resources are made more efficient during push message distribution.

  Patent Document 2 describes a technique for performing distribution in a multicast distribution by using a destination list for identifying a distribution device and limiting the devices to those described in the destination list.

JP 2003-303153 A JP 2001-320367 A

  However, the method of Patent Document 1 needs to acquire distribution information in advance, and cannot be applied to push distribution of immediate messages such as timely advertisement, news distribution, and emergency information notification. That is, in the cited document 1, no consideration is given to immediate push-type message delivery.

  In the method of Patent Document 2, in a distribution system that accommodates tens of millions of devices, when there are a large number of distribution destinations, it takes time to create and transfer a destination list, and simultaneous distribution cannot be performed simultaneously.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a message distribution system, a message distribution method, and a message distribution program for immediately and efficiently distributing messages to a large number of devices. There is.

  In order to solve the above problems, the present invention is a message delivery system, which receives a message delivery request, divides a destination specified in the message delivery request, generates a plurality of destination lists, and receives the message delivery request. A delivery receiving means for sequentially outputting together with the messages specified in the above, a delivery means for delivering the message to each destination device set in the destination list, and storing information relating to the delivery of the message in a database; and the delivery And determining means for determining the length of the destination list using the operation information of the means and the database.

  In the message distribution system, the determination unit reduces the length of the destination list when the operation information of the distribution unit is equal to or less than a predetermined threshold, and when the operation information of the database is equal to or greater than the predetermined threshold, The length of the destination list may be increased.

  The message distribution system may include a plurality of the distribution units, and the distribution reception unit may generate the destination list for each distribution unit.

  In the message distribution system, the determination unit may determine the length of the destination list of each distribution unit according to the number of devices to which each distribution unit is connected.

The present invention is a message delivery method performed by a message delivery system, the message delivery system comprising delivery accepting means, delivery means, a database, and determining means, wherein the delivery accepting means sends a message delivery request. Receiving, generating a plurality of destination lists by dividing the destination specified in the message distribution request, and sequentially outputting together with the message specified in the message distribution request , wherein the distribution means includes the destination list each destination device configured to, as well as delivering the message, performs a distribution step of storing information about the delivery of messages in the database, the determination means, by using the operation information of the distribution means and the database The determination step of determining the length of the destination list is performed.

In the determination step of the message distribution method, the determination unit reduces the length of the destination list when the operation information of the distribution unit is equal to or less than a predetermined threshold, and the operation information of the database is equal to or greater than the predetermined threshold. In this case, the length of the destination list may be increased.

  In the message distribution method, the message distribution system includes a plurality of servers that perform the distribution step, the distribution reception step generates the destination list for each server, and the determination step includes a connection between each server. The length of the destination list of each server may be determined according to the number of devices.

  The present invention is a message delivery program for causing the message delivery system to function.

  ADVANTAGE OF THE INVENTION According to this invention, the message delivery system, the message delivery method, and the message delivery program which deliver a message immediately and efficiently to many devices can be provided.

It is a block diagram which shows the whole system of embodiment of this invention. It is a block diagram of the whole other system of embodiment of this invention. It is a system configuration figure of the message distribution system of a 1st embodiment. It is a flowchart which shows operation | movement of 1st Embodiment. It is a figure which shows the processing image of a message delivery reception part and a message delivery part. It is a system block diagram of the message delivery system of 2nd Embodiment. It is a flowchart which shows operation | movement of 2nd Embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a configuration diagram showing the entire system according to the embodiment of the present invention. In the present embodiment, a message delivery request system 1, a message delivery system 2, and a plurality of devices 3 are provided.

  The message delivery request system 1 is a message delivery source and is a system that transmits a delivery request to the message delivery system 2. The message distribution system 2 is a system that receives a request from the message distribution request system 1 and distributes the message to one or more devices 3. The device 3 is various devices used by a user such as a mobile phone, an STB (set top box), a tablet terminal, and a PC.

  As shown in FIG. 2, the device 3 may be used in the message delivery request system 1. In this case, the message delivery system 2 functions as a message delivery system between devices.

<First Embodiment>
FIG. 3 is a system configuration diagram of the message delivery system 2 according to the first embodiment of this invention. The message distribution system 2 shown in the figure is a system for distributing a message to a plurality of devices 3, and includes a message distribution receiving unit 21, a server information management unit 22, a database 23, and a message distribution unit 24. In the present embodiment, it is assumed that the functional units 21 to 24 in the message delivery system 2 are arranged on different servers.

  The message delivery accepting unit 21 accepts a message delivery request from the message delivery request system 1, divides the destination specified by the message delivery request, generates a plurality of destination lists, and sequentially with the messages specified by the message delivery request. And output to the message delivery unit 24.

  The server information management unit 22 determines the length of the destination list according to the resource status of each server in the message distribution system. In particular. Using the operation information of each server of the message delivery accepting unit 21, the database 23, and the message delivery unit 24, the length of the destination list is determined.

  The message delivery unit 24 delivers the message to each destination device 3 set in the destination list. Further, the message delivery unit 24 stores information related to message delivery in the database 23.

  The database 23 stores a unit ID of the device 3 connected to the message distribution system, information related to message distribution, and the like.

  For the servers of the functional units 21 to 24 of the message delivery system 2 of the present embodiment, for example, a general-purpose computer system including a CPU, a memory, an external storage device such as an HDD, and the like can be used. In this computer system, the functional units 21 to 24 are realized by the CPU executing the programs of the functional units 21 to 24 loaded on the memory. These programs can be stored in a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, a DVD-ROM, or can be distributed via a network.

  The operation of this embodiment will be described below.

  FIG. 4 is a flowchart showing the operation of the message delivery system 2 of the present embodiment.

  First, the message delivery request system 1 transmits a message delivery request including a message and a destination to the message delivery system 2. One or more unit IDs are designated as the destination. The unit ID is identification information for identifying each device 3. A wild card character string representing transmission to all devices 3 may be designated as the destination. Here, a case where a wild card character string is designated as the destination will be described below as an example.

  The message delivery accepting unit 21 of the message delivery system 2 accepts a message delivery request from the message delivery request system 1 (S11).

Next, since the wild card character string is designated as the destination of the message delivery request, the message delivery accepting unit 21 accesses the database 23 and unit IDs U _n (n = 1, 2) of all the devices 3 serving as the destination. ,..., N) are acquired (S12).

Then, the message distribution receiving unit 21 divides (groups) the acquired all unit IDs U _n into a predetermined number, and a plurality of destination unit ID lists L _m (m = 1, 2,..., M) Create Then, every time one destination unit ID list L _m is created, the message delivery accepting unit 21 sequentially sends the created destination unit ID list L _m together with the message transmitted from the message delivery request system 1 to the message delivery unit 24. Transmit (S13).

Message delivery unit 24 sequentially receives the destination unit ID list L _m and the message, retrieve the unit ID as the destination from the destination unit ID list L _m (S14). Next, the message delivery unit 24 writes information about delivery such as delivery time and message ID into the database 23 (S15). The message delivery unit 24, the received message is delivered to the device 3 of each unit ID set to the destination unit ID list L _m (S16).

Message delivery section 24, each time it receives the destination unit ID list L _m from a message delivery reception section 21 repeats the process in S16 from S14, completes the message delivery all units ID addressed (addressed all devices 3).

Consider now the length P of the destination unit ID list L _m. Length P is the data length of the "length of one unit ID (bytes)", "destination unit ID number of the unit ID included in the list L _m" ×.

If the length P is smaller (i.e., if a relatively small number of unit ID included in the destination unit ID list L _m), after creating the destination unit ID list L _m, sequentially message delivery portion from the message delivery reception section 21 24 And message delivery processing is performed. Therefore, the creation destination unit ID list L _m of message delivery reception section 21, and message delivery process of message delivery portion 24 comes to be performed substantially simultaneously in parallel. This is because processing is executed almost simultaneously at the server of the message reception unit 21 and the server of the message distribution unit 24, so that processing efficiency is good.

  FIG. 5A is a diagram illustrating an image of processing of the message delivery receiving unit 21 and the message delivery unit 24 when the length P is small. In FIG. 5A, the process of the message delivery accepting unit 21 and most of the process 51 of the message delivery unit 24 overlap and are processed in parallel.

However, when the value of P is small, in the message delivery process of the message delivery unit 24, the write process to the database 23 occurs every time the destination unit ID list _Lm is received. Therefore, when the value of P is small, a high load state of the database 23 due to frequent database access is caused.

On the other hand, when the length P is large (that is, when the number of unit IDs included in the destination unit ID list L _m is relatively large), the message delivery receiving unit 21 creates the destination unit ID list L _m after creating it. transmits the destination unit ID list L _m to the message delivery unit 24, message delivery unit 24 performs the distribution processing. In this case, since one batch creation processing and message delivery process in the destination unit ID list L _m of a relatively long, in the process of processing and message delivery unit 24 of the message receiving unit 21, a short time to be performed simultaneously in parallel The processing efficiency is poor.

  FIG. 5B is a diagram showing an image of processing of the message delivery accepting unit 21 and the message delivery unit 24 when the length P is large. In FIG.5 (b), the part 52 currently overlapped in the process of the message delivery reception part 21 and the process of the message delivery part 24, and processed in parallel is short. That is, in the time from the start of processing of the message delivery accepting unit 21 to the end of processing of the message delivery unit 24, the proportion of the parts 52 processed in parallel is lower than when the length P is small. .

However, when the value of P is large, since the reduced number of times of reception of the destination unit ID list L _m from message delivery reception section 21, access to the database 23 which delivers the message delivery processing of the message delivery portion 24 decreases, the database The load on 23 is also small.

  From the above, the processing efficiency of each server of the message delivery accepting unit 21 and the message delivery unit 24 and the load on the database 23 are in a trade-off relationship.

In the present embodiment, by controlling the length P of the destination unit ID list L _m, and controls the processing efficiency of each server message delivery reception section 21 and the message delivery portion 24, the balance between the load of the database 23.

The server information management unit 22 stores various types of information (hereinafter referred to as “operation information”) regarding the operation status such as the CPU usage rate, the memory usage status, and the number of accesses of each server of the message distribution receiving unit 21, the message distribution unit 24, and the database 23. Collect and monitor at a predetermined timing. Then, the server information managing unit 22 uses the collected operation information to determine the length P of the destination unit ID list L _m.

For example, the initial value of the length P is set to P ₀ , a first threshold value is provided for the CPU usage rate of the server of the message delivery unit 24, and when the value is equal to or less than the first threshold value, P is set to a predetermined value The value P ₁ (P ₁ <P ₀ ) may be set to be smaller than the initial value P ₀ . In addition, a second threshold is set for the CPU usage rate of the server of the database 23. When the threshold is equal to or higher than the second threshold, P is set to a predetermined value P ₂ (P ₂ > P ₀ ) it is considered to be greater than the value P _0.

Here, in order to suppress the high-load state of the server database 23, by preference the conditions CPU utilization of the database 23 is equal to or greater than a second threshold value, the length P of the destination unit ID list L _m It will be decided. That is, if the CPU usage rate of the server of the message delivery unit 24 is equal to or lower than the first threshold value and the CPU usage rate of the server of the database 23 is equal to or higher than the second threshold value, P is set to the initial value. The value P ₂ is greater than P ₀ .

  Note that the length P may be determined using other operation information such as the memory usage status and the number of accesses in addition to the CPU usage rate.

Server information management unit 22, the determined length P of the destination unit ID list L _m, and transmits the message delivery reception section 21. Message delivery accepted unit 21, so that the length P sent from the server information management unit 22 creates a destination unit ID list L _m. As described above, the server information management unit 22 collects the operation information of each server in the message distribution system 2 and dynamically changes the length P of the destination list using the operation information.

<Second Embodiment>
FIG. 6 shows a system configuration diagram of a message delivery system 2A according to the second exemplary embodiment of the present invention. In the present embodiment, it is assumed that the devices 3 are distributed and accommodated in a plurality of message distribution units 241 in order to immediately distribute messages to many devices 3.

  The message distribution system 2 shown in the figure includes a message distribution receiving unit 21, a server information management unit 22, a database 23, and a plurality of message distribution units 241 and 242. In the present embodiment, it is assumed that the functional units 21 to 23, 241, and 242 in the message distribution system 2A are arranged on different servers.

  In the present embodiment, the message distribution accepting unit 21 generates a destination list for each of the message distribution units 241 and 242. Further, the server information management unit 22 determines the length of the destination list of each distribution server according to the number of devices to which the message distribution units 241 and 242 are connected.

The operation of this embodiment will be described below. Here, the description will focus on parts that are different from the first embodiment. Further, the IDs of the message delivery units 241 and 242 are assumed to be M _j (j = 1, 2,..., J).

  The operation of this embodiment will be described below.

  FIG. 7 is a flowchart showing the operation of the message delivery system 2A of the present embodiment.

The message delivery acceptance unit 21 accepts a message delivery request from the message delivery request system 1 (S21). Next, message delivery reception section 21 accesses the database 23, acquires the ID M _j of message delivery unit unit ID as a destination is contained (S22).

Furthermore, the message delivery accepting unit 21 receives the destination unit ID list L _m (Mj) for each message delivery unit ID M _j. (m = 1, 2,..., M _j ) is created, and a destination unit ID list L _m (Mj) and a message are transmitted for each ID M _j of the message delivery unit (S23). That is, the message delivery accepting unit 21 divides the unit ID U _n specified by the destination of the message delivery request into a predetermined number for each ID M _j of the message delivery unit, and divides the unit ID Un into a destination unit ID list L _m (m = 1,2, ..., M). Then, each time the message delivery accepting unit 21 creates one destination unit ID list L _m for each message delivery unit ID M _j , the corresponding message is sequentially sent to the corresponding destination unit ID list L _m together with the message. It transmits to a delivery part (S23).

Each message delivery unit sequentially receives the destination unit ID list L _m and the message, retrieves the unit ID as the destination from the destination unit ID list L _m (S24), distribution time, information about the distribution of ID, such as the message Write to the database 23 (S25). Each message delivery unit delivers the device 3 of each unit ID set the received message to the destination unit ID list L _m (S26). Each message delivery unit, each time it receives the destination unit ID list L _m from a message delivery reception section 21 repeats the processing to S26 S24, completes the message delivery addressed to all units ID specified.

In the present embodiment, the server information management unit 22 determines the length P _j of the destination unit ID list L _m (Mj) using the operation status collected from each message distribution server. The server information management unit 22 sequentially collects the server operating status of each message distribution unit. For example, the delivery status such as how many messages the message delivery unit server delivered to which device 3 and the connection status of each device 3 (currently connected, disconnected, or finally disconnected) Time, frequently connected, etc.).

Here, the server information management unit 22 indicates the number S _{j of} devices 3 to which the ID M _j of each message delivery unit is connected and the total number S _{all of} devices 3 connected to all message delivery units. It will be collected. Then, an initial value P ₀ of the length P _j of the destination unit ID list L _{m (} Mj) is determined in advance, and P _j is determined as follows.

P _j = P ₀ * (S _j / S _all ) (j = 1,2,3,…, J)
That is, the length M _j of the destination unit ID list L _{m (} Mj) is a value corresponding to the number S _j ratio of the devices 3 to which each message delivery unit is connected. As a result, a message is sent to the message delivery unit with a small number of connected devices for each number of unit IDs, so that server resources can be effectively utilized and immediate delivery can be performed. On the other hand, messages are sent to the message delivery unit having a large number of connected devices for each number of unit IDs, and an increase in intra-system traffic is suppressed.

  In the first and second embodiments described above, a message is distributed after a destination list is created and the destinations are limited. Then, a destination list and a message having a length determined by the server information management unit 22 are sequentially transmitted to the message distribution unit in which the device 3 serving as the destination is accommodated, and processing related to distribution is performed simultaneously on each server. In addition, immediate distribution by sequential processing can be realized without increasing traffic in the message distribution system 2.

  In the first and second embodiments, the length of the destination list is dynamically changed based on information such as the operating status of each server of the message distribution system 2, so that the message list in the message distribution system 2 can be changed. Since effective use of server resources can be realized, a delay due to a sudden increase in processing load can be avoided.

  In addition, this invention is not limited to the said embodiment, A various change and application are possible within a claim. For example, in the second embodiment including a plurality of message delivery units, the server information management unit may determine the length P of the destination list of each message delivery unit in the same manner as in the first embodiment. Good.

  In the first and second embodiments, the function units 21 to 24, 241, and 242 in the message distribution system 2 and 2A are arranged on different servers. It is not limited. For example, the server information management unit 22 and the database 23 do not necessarily have to be arranged in separate servers, and may be arranged in either the server of the message distribution receiving unit 21 or the server of the message distribution unit 24.

1: Message distribution request system 2, 2A: Message distribution system 21: Message distribution reception unit 22: Server information management unit 23: Database 24, 241, 242, Message distribution unit 3: Device

Claims (8)

A message delivery system,
A delivery accepting unit that accepts a message delivery request, divides a destination specified in the message delivery request to generate a plurality of destination lists, and sequentially outputs the destination list together with the message designated in the message delivery request;
Distribution means for distributing the message to each destination device set in the destination list, and storing information related to message distribution in a database;
A message distribution system comprising: a determination unit that determines the length of the destination list using operation information of the distribution unit and the database. The message delivery system according to claim 1,
The determination unit reduces the length of the destination list when the operation information of the distribution unit is equal to or smaller than a predetermined threshold, and lengths the destination list when the operation information of the database is equal to or larger than the predetermined threshold. A message delivery system characterized by increasing the size. The message delivery system according to claim 1,
A plurality of delivery means;
The message delivery system, wherein the delivery accepting unit generates the destination list for each delivery unit. The message delivery system according to claim 3, wherein
The message distribution system, wherein the determination unit determines the length of the destination list of each distribution unit according to the number of devices connected to each distribution unit. A message distribution method performed by a message distribution system , wherein the message distribution system includes a distribution reception unit, a distribution unit, a database, and a determination unit.
A delivery acceptance step of accepting a message delivery request, generating a plurality of destination lists by dividing the destination designated by the message delivery request, and sequentially outputting the messages together with the message designated by the message delivery request ; Done
The distribution means, each destination device that is set in the destination list, as well as delivering the message, performs a distribution step of storing information about the delivery of messages in the database,
The message distribution method , wherein the determination unit performs a determination step of determining the length of the destination list using the distribution unit and the operation information of the database . The message delivery method according to claim 5,
In the determining step , the determining means reduces the length of the destination list when the operating information of the distributing means is equal to or smaller than a predetermined threshold, and when the operating information of the database is equal to or larger than the predetermined threshold, A message delivery method characterized by increasing the length of the destination list. The message delivery method according to claim 5,
The message delivery system includes a plurality of servers that perform the delivery step,
The delivery acceptance step generates the destination list for each server,
The determination step determines the length of the destination list of each server according to the number of devices connected to each server.   The message delivery program for functioning as a message delivery system as described in any one of Claim 1 to 4.

Images