JP2018163559A - Distribution control device, distribution control method and distribution control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a distribution control device, distribution control method and distribution control program which permit a service provider who is not a common carrier to push-distribute a message to a terminal in a specific area without needing preparatory work.SOLUTION: A message control unit 33 includes: an event reception unit 334 for receiving event information including an identifier of a terminal 2 as a trigger of message distribution; a destination acquisition unit 335 for acquiring a destination of a message in association with a distribution destination satisfying conditions from network information including an identifier of a connection destination eNB 10 extracted from control data in a mobile network 3 on the basis of the identifier of the terminal 2 in the event information; a message extraction unit 336 for extracting a message corresponding to a service shown by the event information; and a request transmission unit 337 for transmitting a combination of a destination and a message to a distribution server 5.SELECTED DRAWING: Figure 2

Description

  The present invention relates to an apparatus, a method, and a program for controlling message delivery to a terminal.

In recent years, with the development of communication technology and information processing technology, M2M (Machine to Machine) devices such as wearable cameras have become terminals in addition to mobile terminals such as PCs and smartphones, and servers installed on the Internet provide data communication services I can do it now.
The provided data communication service includes a pull-type data communication service that receives distribution of desired information from the server upon request from the terminal side, and a push that distributes information from the server to the terminal using a mail address or telephone number Type data communication service (push delivery).

Some terminals that are the targets of push distribution change the position of a mobile terminal or the like every moment. In view of this, a technique has been proposed in which push distribution is performed in a limited area only to terminals located in specific locations such as in and around facilities such as a stadium, inside and around stores such as department stores, and inside cars such as trains or buses.
For example, Patent Document 1 proposes a technique in which a message distribution server performs push distribution with a limited area by acquiring GPS information from a terminal application and transmitting the terminal position to the message distribution server.
Further, in Patent Document 2, a terminal detection sensor is installed in an area to be subjected to push distribution, and the message distribution server transmits the terminal identification information detected by the terminal detection sensor to the message distribution server. Based on the above, a technique for performing push distribution with limited areas has been proposed.

JP 2009-5366 A JP, 2015-191399, A

  However, in order to perform push delivery limited to an area, for example, in the method of Patent Document 1, preparation work for installing an application for acquiring the terminal position in the terminal is required. In addition, the method of Patent Document 2 requires preparation work for installing hardware (terminal detection sensor) for detecting a nearby terminal in the field.

  The present invention provides a distribution control device, a distribution control method, and a distribution control program that enable a service provider who is not a telecommunications carrier to push messages to terminals in a specific area without requiring these preparation operations. For the purpose.

  The delivery control device according to the present invention includes a message storage unit that stores a message to be delivered for each service, a setting unit that sets a condition for delivering the message for each service, and a trigger for message delivery. A receiving unit that receives event information related to the service including an identifier of one terminal, and an identifier of a connection destination base station extracted from control data in a mobile network based on the identifier of the first terminal in the event information An acquisition unit that acquires a destination of the message associated with a delivery destination that satisfies the condition, an extraction unit that extracts the message corresponding to the service indicated by the event information, and the destination and the message A transmission unit that transmits the combination to the distribution server.

  The distribution control apparatus includes a terminal storage unit that stores an identifier of a candidate terminal that distributes a message for each service, and the reception unit includes the event when the first terminal is included in the candidate terminal. The information may be received, and the acquisition unit may use a terminal included in the candidate terminal as a distribution destination.

  The acquisition unit may use a terminal connected to the same base station as a distribution destination.

  The acquisition unit may use a terminal in which connected base stations are within a predetermined distance as a delivery destination.

  The reception unit may receive the event information including an identifier of the service and the first terminal from an application capable of acquiring the network information.

  The receiving unit may receive the event information in which the terminal newly connected to or disconnected from the specific base station set as the condition by the setting unit is the first terminal.

  The extraction unit may select a message based on the number of terminals connected to the set base station.

  The acquisition unit may select the type of the destination according to a section indicating a transmission means of the message.

  The network information may include a telephone number as the destination.

  The delivery control method according to the present invention stores a message to be delivered for each service, and a computer that sets a condition for delivering the message for each service uses a first terminal identifier as a message delivery trigger. Receiving from the network information including the identifier of the connection destination base station extracted from the control data in the mobile network based on the identifier of the first terminal in the event information An acquisition step of acquiring a destination of the message associated with a delivery destination satisfying the condition, an extraction step of extracting the message corresponding to the service indicated by the event information, and a combination of the destination and the message, And a transmission step of transmitting to.

  The delivery control program according to the present invention stores a message to be delivered for each service, and sets a condition for delivering the message for each service as a trigger for message delivery to a first terminal identifier. Receiving from the network information including the identifier of the connection destination base station extracted from the control data in the mobile network based on the identifier of the first terminal in the event information An acquisition step of acquiring a destination of the message associated with a delivery destination satisfying the condition, an extraction step of extracting the message corresponding to the service indicated by the event information, and a combination of the destination and the message, Sending step to send to It is those of.

  ADVANTAGE OF THE INVENTION According to this invention, the service provider who is not a communication carrier can push-deliver a message with respect to the terminal in a specific area, without requiring preparatory work.

It is a figure showing the whole distribution system composition concerning an embodiment. It is a figure which shows the function structure of the edge host which concerns on embodiment. It is a figure which illustrates the content of the network information which concerns on embodiment. It is a figure which shows an example of the information stored in the delivery terminal DB which concerns on embodiment. It is a figure which shows an example of the information stored in delivery message DB which concerns on embodiment. It is a figure which illustrates the delivery area set by the delivery area setting part which concerns on embodiment. It is a flowchart which shows the process of the message control part which concerns on embodiment. It is a sequence diagram which shows the process by the 1st delivery pattern in the delivery system which concerns on embodiment. It is a 1st figure which shows the flow of the data by the 1st delivery pattern in the edge host which concerns on embodiment. It is a 2nd figure which shows the flow of the data by the 1st delivery pattern in the edge host which concerns on embodiment. It is a 3rd figure which shows the data flow by the 1st delivery pattern in the edge host which concerns on embodiment. It is a 4th figure which shows the data flow by the 1st delivery pattern in the edge host which concerns on embodiment. It is a figure which illustrates the list | wrist of eNB10 which the message control part which concerns on embodiment refers. It is a sequence diagram which shows the process by the 3rd delivery pattern in the delivery system which concerns on embodiment. It is a 1st figure which shows the data flow by the 3rd delivery pattern in the edge host which concerns on embodiment. It is a 2nd figure which shows the flow of the data by the 3rd delivery pattern in the edge host which concerns on embodiment. It is a 3rd figure which shows the data flow by the 3rd delivery pattern in the edge host which concerns on embodiment.

Hereinafter, an example of an embodiment of the present invention will be described.
FIG. 1 is a diagram illustrating an overall configuration of a distribution system 1 according to the present embodiment.
The distribution system 1 includes a terminal 2, a mobile network 3, a cloud server 4, and a distribution server 5.

The terminal 2 is a device that uses a service provided by the cloud server 4. Specifically, the terminal 2 may be a mobile terminal such as a PC, a smartphone, or a sensor, or various M2M devices such as a wearable camera.
The terminal 2 holds terminal information for connection to the mobile network 3 and use of a data communication service, a mail service, or the like in a SIM card or an internal memory. The terminal information includes, for example, an IMSI (International Mobile Subscriber Identity) as a terminal identifier, an MSISDN (Mobile Subscriber Integrated Network Number) indicating a telephone number, an IP address, and an address. Further, the terminal 2 includes a functional unit for receiving a message by using an e-mail service or SMS (short message service).

  The mobile network 3 is a network of a mobile communication system that is prepared by a communication carrier and provides a mobile phone service such as 3G or LTE (Long Term Evolution) defined by 3GPP or 3GPP2. The mobile network 3 includes, for example, an eNB (evolved Node B) 10, an S / PGW (Serving / PDN Gateway) 20, and an edge host 30 when supporting LTE defined by 3GPP.

The cloud server 4 is a server that provides services to the terminal 2 and is centrally deployed in a data center or the like.
The distribution server 5 is an e-mail server or a server that provides an SMS or the like.

The eNB 10 is a base station to which the terminal 2 is wirelessly connected. Each base station is assigned an identifier called ECGI (E-UTRAN Cell Global Identifier).
In S / PGW20, SGW is a communication apparatus which accommodates one or several eNB31, and transmits data between PGW and eNB31. The PGW is a communication device having an interface with an external network.
The edge host 30 is a control device defined by ETSI ISG MEC.

FIG. 2 is a diagram illustrating a functional configuration of the edge host 30 according to the present embodiment.
The edge host 30 includes a network information extraction unit 31, an edge server 32, and a message control unit 33 (distribution control device).

The network information extraction unit 31 relays user data and control signals (GTPv2-C protocol defined in 3GPP TS 29.274) transferred inside the mobile network 3.
The network information extraction unit 31 extracts network information from the user data and control signal and holds it.

FIG. 3 is a diagram illustrating contents of network information according to the present embodiment.
The network information includes the IMSI, MSISDN and IP address of the terminal, and the ECGI of the eNB 10 to which the terminal is connected.

  The network information extraction unit 31 includes an interface that provides the held network information to external components such as the edge server 32 and the message control unit 33 using a protocol such as REST.

The edge server 32 is a server that provides a service to the terminal 2 instead of the cloud server 4, and implements and operates an application (edge application) developed by a service provider or the like.
The edge application refers to the network information held by the network information extraction unit 31 via a predetermined interface, and transmits event information including the acquired terminal identifier to the message control unit 33 as a trigger for push delivery related to the service. To do.

  The message control unit 33 includes a distribution terminal DB 331 (terminal storage unit), a distribution message DB 332 (message storage unit), a distribution area setting unit 333 (setting unit), an event reception unit 334 (reception unit), and a destination acquisition unit. 335 (acquisition unit), a message extraction unit 336 (extraction unit), and a request transmission unit 337 (transmission unit).

FIG. 4 is a diagram illustrating an example of information stored in the distribution terminal DB 331 according to the present embodiment.
The distribution terminal DB 331 stores in advance a service name that implements push distribution and an identifier (IMSI) of a candidate terminal that is to use this service and that distributes a message before system operation. Further, according to the operation of the system, the MSISDN, the mail address, the IP address, and the ECGI of the eNB 10 to which the terminal 2 is connected are stored in association with the service name and IMSI.

In this embodiment, IMSI is used as information for identifying the terminal 2, but the present invention is not limited to this. For example, an identifier that can uniquely identify the terminal 2 or a communication destination, such as a telephone number or IMEI (International Mobile Equipment Identity), may be used.
Also, all terminals 2 communicating with a specific eNB 10 may be registered in the terminal DB 331. Thereby, the delivery system 1 can deliver a message to all the terminals 2 located within a specific range.

FIG. 5 is a diagram illustrating an example of information stored in the delivery message DB 332 according to the present embodiment.
The distribution message DB 332 stores a service name and a message to be transmitted at the time of push distribution for each service before the system operation.
The message to be registered may be appropriately selected from various formats such as text, URL indicating the location of the content to be provided, and text including the URL.

  Also, when using a plurality of messages in the same service, a plurality of message numbers are set together with the service name, and a message is registered for each combination of the service name and the message number.

Distribution area setting section 333 sets a service name and a message distribution area as message distribution conditions in advance before system operation.
FIG. 6 is a diagram illustrating a distribution area set by the distribution area setting unit 333 according to the present embodiment.

The distribution area is set in one of the following formats, for example.
(1) A terminal 2 under the same eNB 10 as the triggering terminal.
(2) The eNB 10 to which the triggering terminal is connected and the terminal 2 under the control of the neighboring eNB 10 (for example, within a radius of OO km).
(3) The terminal 2 that is newly connected to or disconnected from the specific eNB 10 and becomes a trigger.
(4) A terminal 2 that is newly connected to a specific eNB 10 and is under the same eNB 10 as the triggering terminal 2.

  In the same service, a plurality of distribution areas may be set by providing a plurality of message numbers.

  The event receiving unit 334 receives event information related to a service including the IMSI of the terminal 2 (first terminal) as a push delivery trigger. This event information is accepted when the triggering terminal 2 is included in the candidate terminals registered in the distribution terminal DB 331.

Specifically, the event receiving unit 334 receives event information including the service and the IMSI of the terminal 2 (first terminal) from an edge application capable of acquiring network information in the edge server 32.
In addition, the event reception unit 334 receives, as event information, network information of the terminal 2 (first terminal) that is newly connected to or disconnected from the specific eNB 10 set as a condition by the distribution area setting unit 333. In this case, the condition is notified to the network information extraction unit 31 in advance.

  The destination acquisition unit 335 determines the conditions set for each service from the network information held in the network information extraction unit 31 based on the IMSI of the terminal 2 (first terminal) that is a trigger in the received event information. The destination data of the message associated with the distribution destination terminal 2 satisfying the condition is acquired. At this time, the destination acquisition unit 335 sets the terminal 2 included in the candidate terminals registered in the distribution terminal DB 331 as the distribution destination.

  The destination acquisition unit 335 refers to the conditions set by the distribution area setting unit 333. For example, the destination 2 connected to the same eNB 10 is set as the distribution destination, or the connected eNBs 10 are within a predetermined distance. The terminal 2 can be a delivery destination.

The destination data differs depending on the message transmission means, and is, for example, an MSISDN as a mail address in the case of an electronic mail and a telephone number in the case of SMS.
A classification indicating message transmission means may be registered in the distribution terminal DB 331 or the distribution message DB 332, and the destination acquisition unit 335 may select the type of destination data according to this classification.

The message extraction unit 336 extracts a message corresponding to the service indicated by the event information serving as a trigger from the delivery message DB 332.
Further, the message extraction unit 336 may select a message based on the number of terminals 2 currently connected to the set base station.

  The request transmission unit 337 transmits the combination of the destination data and the message to the distribution server 5 as a request for distributing the message to the destination acquired by the destination acquisition unit 335.

FIG. 7 is a flowchart showing processing of the message control unit 33 according to the present embodiment.
Prior to system operation, settings for using the network information extraction unit and registration in the distribution terminal DB 331 and the distribution message DB 332 are performed. Furthermore, a delivery condition is set by the delivery area setting unit 333 (S1).

  When the system operation starts (S2), the message control unit 33 waits for a push delivery delivery trigger (S3).

  When the message control unit 33 receives the push delivery trigger (S4: YES), the information on the target area to the network information extraction unit 31 (for example, ECGI of the eNB to which the terminal 2 where the delivery trigger has occurred is connected). And information on the terminal 2 located in this area (for example, IMSI, MSISDN, IP address, ECGI of the terminal 2 that matches the distribution condition) is inquired (S5). The message control unit 33 receives a response of the inquired content from the network information extraction unit 31 (S6).

  Based on the received answer, the message control unit 33 queries the distribution terminal DB 331 for the distribution destination terminal 2 (S7). When there is a delivery destination (S8: YES), the message control unit 33 refers to the delivery message DB 332 for a message of the corresponding service (S9). When there is a message to be distributed (S10: YES), the message control unit 33 transmits a request to the distribution server 5 including the destination data (MSISDN, mail address, etc.) of the terminal that is the distribution destination and the message. (S11).

  The message control unit 33 confirms whether or not there is an operation end command during the execution of a series of flows (S12). If there is an operation end command (S12: YES), the operation of the message control unit 33 ends. On the other hand, when there is no operation end command (S12: NO), the process returns to the trigger standby state of S3, and the operation of the message control unit 33 continues.

Next, as examples in which the distribution system 1 is applied, first to third distribution patterns having different triggers and distribution conditions will be described.
The first distribution pattern is a case where area-limited push distribution is performed to the terminals 2 under the same eNB 10 triggered by the content of the user data of the specific terminal 2 processed by the edge application.
The second distribution pattern is a case where area-limited push distribution is performed to the terminals 2 under the control of the neighboring eNB 10 including the same eNB 10 with the content of the user data of the specific terminal 2 as a trigger.
The third distribution pattern is a case where push distribution is performed to the terminal 2 when the terminal 2 enters or leaves the specific eNB 10.

[First delivery pattern]
Here, as an example, a use case (service name: edge. ***) is assumed in which a terminal 2 having a wearable camera is used to guard the inside and surroundings of a facility such as a stadium. Specifically, an image is transmitted from the terminal 2 having an IMSI of “440 99 0000000001” to the edge server 32 and triggered by the discovery of a suspicious person registered in advance by the image processing of the edge application. Push distribution is performed to a terminal 2 (IMSI is “440 99 0000000002”) such as a subordinate smartphone.

FIG. 8 is a sequence diagram showing processing by the first distribution pattern in the distribution system 1 according to the present embodiment.
9A to 9D are diagrams illustrating a data flow according to the first distribution pattern in the edge host 30 according to the present embodiment.

Before starting the operation of the system, the service name “edge. ***” shown in FIG. 9A is registered and set in the distribution terminal DB 331, the distribution message DB 332, and the distribution area setting unit 333 of the message control unit 33. (S101).
When the system operation starts after registration and setting are completed, the message control unit 33 is in a state of waiting for a push delivery trigger.

When the power of the terminal 2 is turned on (S102), the terminal 2 attach process sequence defined in 3GPP TS 23.401 is executed (S103).
The network information extraction unit 31 monitors the control signal transferred during the attach process, and extracts the network information (IMSI, MSISDN, IP address, ECGI of the connected eNB 10) shown in FIG. 9A (S104).

When the attach process of the terminal 2 is completed, user data (video data) is transferred from the terminal 2 to the edge server 32 together with the transmission source IP address (S105).
The edge server 32 performs image processing, and detects a case where a suspicious person registered in advance is found as an event (S106).

As shown in FIG. 9B, the edge server 32 requests the IMSI of the terminal 2 from the network information extraction unit 31 using the transmission source IP address “10.0.0.1” as a key (S107). The network information extraction unit 31 refers to the network information and responds with the IMSI “440 99 0000000001” of the terminal 2 (S108).
The edge server 32 stores event information including a service name “edge. ***” and a message number “1” set in advance for each edge application, that is, for each service, and the IMSI of the terminal 2 in which the event is detected. Then, it is transmitted as a delivery trigger to the message control unit 33 (S109).

When the message control unit 33 receives the distribution trigger, as shown in FIG. 9C, the message control unit 33 requests the network information of the terminal 2 in which the distribution trigger has occurred (S110-1), and the terminal 2 is connected from the network information extraction unit 31. The ECGI “440 99 0000001 255” of the eNB 10 that is currently being acquired is acquired (S111-1).
Further, when the condition “same eNB subordinate terminal” is acquired as the target area information from the service name and the message number, the message control unit 33 requests the network information of the terminal 2 that matches the condition (S110-2). ), And acquires the IMSI, MSISDN, IP address, and ECGI of the connected eNB of the target terminal group (S111-2).
The mail address of the terminal 2 can be acquired by referring to IMS (IP Multimedia Subsystem) based on MSISDN.

The message control unit 33 queries the distribution terminal DB 331 for the distribution destination terminal 2 (S112), and if there is a distribution destination, the message control unit 33 queries the distribution message DB 332 for a message of the corresponding service (S113).
When there is a delivery content, the message control unit 33 includes the destination data (for example, MSISDN “81 80 00000002”) and the message of the delivery destination terminal 2 with respect to the delivery server 5 as shown in FIG. 9D. Then, a push delivery request is transmitted (S114).
The distribution server 5 that has received the request performs message push distribution to the terminal 2 based on the content of the request (S115).

[Second delivery pattern]
Here, a use case similar to the first distribution pattern is assumed, but the condition of the distribution destination is the terminal 2 under the same and adjacent eNB 10. The difference between the processing sequence and the information flow in the edge host 30 from the first distribution pattern (FIGS. 8 and 9) will be described.

The edge server 32 designates the message number “2” together with the service name “edge. ***” when transmitting the delivery trigger to the message control unit 33 (S109).
The distribution area is set as “terminals under a neighboring eNB (including the same eNB) (within a radius of 2 km)”. Therefore, when the ECGI of the eNB 10 connected to the terminal 2 where the distribution trigger has occurred is found to be “440 99 0000001 255” (S111-1), the message control unit 33 or the list of eNBs 10 held by the mobile network 3 is message-controlled. Reference is made to part 33.

FIG. 10 is a diagram illustrating a list of eNBs 10 referred to by the message control unit 33 according to the present embodiment.
As the position information, for example, latitude and longitude information is stored in the edge host 30 or an external database for each ECGI of the eNB 10.

The message control unit 33 acquires “440 99 0000002 255” as the ECGI of the eNB 10 within a predetermined distance (2 km) from the eNB 10 whose ECGI is “440 99 0000001 255” from the obtained latitude / longitude information.
Thereafter, when inquiring the network information of the terminal 2 as the delivery destination, the message control unit 33 uses the ECGI “440 99 0000001 255” of the connected eNB 10 as well as the ECGI “440 99 00000002 255” of the neighboring eNB 10 as a query key. Is designated (S110-2), and the network information of the terminals 2 under the two eNBs 10 is acquired (S111-2).

[Third delivery pattern]
Here, as an example, when a terminal 2 enters or exits a store such as a department store or a surrounding eNB 10 using a smartphone as the terminal 2, an advertisement is given to the terminal 2 Suppose a use case for push distribution of campaign information or coupons.

FIG. 11 is a sequence diagram showing processing by the third distribution pattern in the distribution system 1 according to the present embodiment.
12A to 12C are diagrams illustrating a data flow according to the third distribution pattern in the edge host 30 according to the present embodiment.

Before starting the operation of the system, the service name “shop. ***” shown in FIG. 12A is registered and set in the distribution terminal DB 331, the distribution message DB 332, and the distribution area setting unit 333 of the message control unit 33. . In addition, the message control unit 33 moves the terminal 2 of the terminal 2 under the control of the eNB 10 when the terminal 2 moves to the specific eNB 10 having the ECGI “440 99 00000001 255” with respect to the network information extraction unit 31. When the power is turned on, registration is performed so as to notify the network information of the terminal 2 (S301).
When the system operation starts after registration and setting are completed, the message control unit 33 enters a state of waiting for a notification from the network information extraction unit 31 that triggers push delivery.

When the terminal 2 moves under the control of the specific eNB 10 (S302), the sequence of the handover process of the terminal 2 defined in 3GPP TS 23.401 is executed (S303).
The network information extraction unit 31 monitors the control signal transferred during the handover process, and the ECGI of the network information connection eNB 10 is changed as shown in FIG. 12B (S304).

As previously set, the network information extraction unit 31 sends the network information (IMSI, MSISDN, IP address, connection) of the terminal 2 to the message control unit 33 when the terminal 2 moves under a specific eNB 10. (ECGI of eNB) is notified (S311).
The mail address of the terminal 2 can be acquired by referring to IMS based on MSISDN.

The message control unit 33 inquires of the distribution terminal DB 331 about the distribution destination terminal 2 (S312), and the terminal 2 having the IMSI “440 99 0000000003” is the target of the service name “shop. ***”. Judging. When there is a distribution destination in this way, the message of the corresponding service is referred to the distribution message DB 332 (S313).
When there is a delivery content, the message control unit 33 includes the destination data (for example, MSISDN “81 80 0000003”) and the message of the delivery destination terminal 2 with respect to the delivery server 5 as shown in FIG. 12C. Then, a push delivery request is transmitted (S314).
The distribution server 5 that has received the request performs message push distribution to the terminal 2 based on the content of the request (S315).

In addition, although the case where the terminal 2 came under the control of the specific eNB 10 has been described here, the same applies to the case where the terminal 2 comes out.
Further, the message control unit 33 may distribute the message corresponding to the number of terminals 2 by counting the number of terminals 2 under the control of the specific eNB 10 by itself or by acquiring the number from the network information extraction unit 31. . For example, the message control unit 33 can distribute the message to the triggering terminal 2 or the terminals 2 under the same eNB based on a comparison between the number of terminals 2 and one or more threshold values.

Further, the message control unit 33 may measure a time during which the terminal 2 stays under a specific eNB 10 or obtain from the network information extraction unit 31 to distribute a message corresponding to this time. For example, the message control unit 33 can distribute an appropriate message to a terminal 2 of a user who has stayed in a store for a predetermined time or more and is likely to be shopping.
Further, the message control unit 33 may further distribute the message according to the time zone by further acquiring the current time. For example, the message fish section 33 can distribute information such as time sales specialized for time zones, such as a store closing time, to terminals in a specific area.

  According to this embodiment, the distribution system 1 refers to the network information extracted from the control data in the mobile network, thereby identifying the identifier (IMSI) of the terminal 2 and the identifier (ECGI) of the connected base station (eNB 10). Destination data (MSISDN, e-mail address, etc.) for linking and push distribution can be acquired. The distribution system 1 determines a distribution destination that satisfies the distribution condition based on the network information of the terminal 2 that has triggered the push distribution, and provides destination data, so that a service provider that is not a communication carrier does not need to perform preparation work. In addition, a message can be pushed and distributed to the terminal 2 in a specific area.

  The distribution system 1 can provide a service only to the terminals 2 pre-registered as push distribution targets by storing the distribution candidate terminals in the distribution terminal DB 331 in advance.

  The distribution system 1 uses the network information specific to the communication carrier by setting the terminal 2 connected to the same eNB 10 or the terminal 2 connected to a nearby eNB 10 within a predetermined distance as a distribution destination. , Push distribution with limited area can be realized efficiently.

  Since the distribution system 1 can receive event information as a trigger from the application of the edge server 32, the distribution system 1 can perform push distribution by specifying the terminal 2 based on the processing contents of the application created by the service provider who is not the communication carrier.

  The delivery system 1 can refer to the network information and deliver the message by using the terminal 2 newly connected to or disconnected from the specific eNB 10 as a trigger, so that the delivery system 1 can efficiently perform push delivery to the specific terminal 2 on the condition of the area.

  Since the distribution system 1 can acquire the number of terminals 2 connected to a specific eNB 10 based on the network information, the distribution system 1 selects a message to be distributed based on this number, and determines, for example, the degree of communication congestion for each eNB 10. The status of the mobile network 3 can be notified to the terminal 2 such as distribution.

  Since the distribution system 1 can select the type of destination data such as a telephone number or an e-mail address by providing a section indicating the means of push distribution such as SMS or e-mail, the type of service, the type of message, or the terminal 2 Appropriate distribution means can be used depending on the type.

  Since the distribution system 1 can use a telephone number specific to the mobile network as destination data, it is difficult to impersonate the terminal 2 that is the distribution destination, and more reliable push distribution can be realized.

  As mentioned above, although embodiment of this invention was described, this invention is not restricted to embodiment mentioned above. Further, the effects described in the present embodiment are merely a list of the most preferable effects resulting from the present invention, and the effects of the present invention are not limited to those described in the present embodiment.

  The distribution control method by the distribution system 1 is realized by software. When realized by software, a program constituting the software is installed in an information processing apparatus (computer). These programs may be recorded on a removable medium such as a CD-ROM and distributed to the user, or may be distributed by being downloaded to the user's computer via a network. Furthermore, these programs may be provided to the user's computer as a Web service via a network without being downloaded.

DESCRIPTION OF SYMBOLS 1 Distribution system 2 Terminal 3 Mobile network 4 Cloud server 5 Distribution server 30 Edge host 31 Network information extraction part 32 Edge server 33 Message control part (distribution control apparatus)
331 Distribution terminal DB (terminal storage unit)
332 Delivery message DB (message storage unit)
333 Distribution area setting part (setting part)
334 Event receiver (receiver)
335 Address acquisition unit (acquisition unit)
336 Message extraction unit (extraction unit)
337 Request transmitter (transmitter)

Claims (11)

A message storage unit for storing a message to be distributed for each service;
A setting unit for setting a condition for delivering the message for each service;
A reception unit for receiving event information about the service including an identifier of the first terminal as a trigger for message delivery;
Based on the identifier of the first terminal in the event information, the destination of the message associated with the delivery destination satisfying the condition from the network information including the identifier of the connection destination base station extracted from the control data in the mobile network An acquisition unit for acquiring
An extraction unit for extracting the message corresponding to the service indicated by the event information;
And a transmission unit configured to transmit a combination of the destination and the message to a distribution server. A terminal storage unit that stores an identifier of a candidate terminal for delivering a message for each service,
The receiving unit receives the event information when the first terminal is included in the candidate terminals,
The distribution control apparatus according to claim 1, wherein the acquisition unit uses a terminal included in the candidate terminal as a distribution destination.   The distribution control device according to claim 1, wherein the acquisition unit sets a terminal connected to the same base station as a distribution destination.   The distribution control apparatus according to claim 3, wherein the acquisition unit sets a distribution destination to terminals whose connected base stations are within a predetermined distance.   5. The distribution control device according to claim 1, wherein the reception unit receives the event information including an identifier of the service and the first terminal from an application capable of acquiring the network information.   5. The reception unit according to claim 1, wherein the reception unit receives the event information in which the terminal newly connected to or disconnected from the specific base station set as the condition by the setting unit is the first terminal. The delivery control device according to any one of the above.   The distribution control apparatus according to claim 6, wherein the extraction unit selects a message based on the number of terminals connected to the set base station.   The distribution control device according to claim 1, wherein the acquisition unit selects the type of the destination according to a classification indicating a transmission unit of the message.   The distribution control device according to claim 1, wherein the network information includes a telephone number as the destination. For each service, a message to be delivered is stored, and for each service, a computer that sets a condition for delivering the message,
A reception step of receiving event information about the service including an identifier of the first terminal as a message delivery trigger;
Based on the identifier of the first terminal in the event information, the destination of the message associated with the delivery destination satisfying the condition from the network information including the identifier of the connection destination base station extracted from the control data in the mobile network An acquisition step to acquire,
An extraction step of extracting the message corresponding to the service indicated by the event information;
And a transmission step of transmitting the combination of the destination and the message to a distribution server. For each service, a message to be delivered is stored, and for each service, a computer in which conditions for delivering the message are set,
A reception step of receiving event information about the service including an identifier of the first terminal as a message delivery trigger;
Based on the identifier of the first terminal in the event information, the destination of the message associated with the delivery destination satisfying the condition from the network information including the identifier of the connection destination base station extracted from the control data in the mobile network An acquisition step to acquire,
An extraction step of extracting the message corresponding to the service indicated by the event information;
A distribution control program for executing a transmission step of transmitting a combination of the destination and the message to a distribution server;

Images