Information delivery system, gateway device, delivery control method, and non-transitory computer readable medium storing program

To provide an information delivery system, a gateway device, a delivery control method and a program that can be used by various business entities to meet diversified needs for information delivery, an information delivery system includes an event detection device (10) that is configured to detect occurrence of a plurality of events and specify delivery area information of event information according to the events, and a delivery device (20) that delivers the event information to a delivery destination node corresponding to the delivery area information specified by the event detection device (10).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a national stage application of International Application No. PCT/JP2013/002725 entitled “Information Delivery System, Gateway Device, Delivery Control Method, and Non-Transitory Computer Readable Medium Storing Program” filed on Apr. 23, 2013, which claims the benefit of the priority of Japanese Patent Application No. 2012-101826, filed on Apr. 26, 2012, the disclosures of each of which are hereby incorporated by reference in their entirety.

TECHNICAL FIELD

The present invention relates to an information delivery system and, particularly, to an information delivery system that changes a delivery area according to an event.

BACKGROUND ART

CBS (Cell Broadcast Service) is used for emergency information delivery in a mobile network today. The CBS sends emergency information through broadcast to mobile phone terminals located in a target area to deliver the emergency information. Further, ETWS (Earthquake and Tsunami Warning System) is specified for more rapid disaster alert and more flexible delivery area.

For example, the rapid disaster alert is achieved by separately delivering two types of signals: a first report that delivers the most urgent minimum information such as “earthquake occurred” in the quickest way and a second report that delivers additional information such as a seismic intensity and an epicenter.

Further, the flexible delivery area is achieved by selectively using a delivery area according to three levels: Cell level, TA (Tracking Area) level and EA (Emergency Area) level.

Regarding the flexible delivery area, Patent Literature 1 discloses a technique that specifies a delivery area of an emergency message in units of wide areas or in units of sectors.

CITATION LIST

Patent Literature

SUMMARY OF INVENTION

Technical Problem

The needs for emergency information delivery are expected to be diversified in the future. For example, at present, emergency information related to earthquakes and Tunami is delivered in emergency information delivery using CBS. In the future, however, it is desired to deliver emergency information other than natural disasters. Further, it is desired to deliver emergency information or the like to an area desired by a business entity or the like that requests delivery of emergency information. However, the present CBS does not have the system architecture to meet such diversified needs, and it is therefore necessary to make further system modifications in order to meet the diversified needs.

An exemplary object of the present invention is to provide an information delivery system, a gateway device, a delivery control method and a program that can be used by various business entities to meet diversified needs for information delivery.

Solution to Problem

An information delivery system according to a first exemplary aspect of the present invention includes an event detection means configured to detect occurrence of a plurality of events and specify delivery area information of event information according to the events, and a delivery means for delivering the event information to a delivery destination node corresponding to the delivery area information specified by the event detection means.

A gateway device according to a second exemplary aspect of the present invention includes a receiving unit that receives a delivery request containing event information and delivery area information from an event detection device configured to detect occurrence of a plurality of events and specify delivery area information of event information according to the events, and a control unit that determines a delivery destination node corresponding to the delivery area information based on the delivery area information.

A delivery control method according to a third exemplary aspect of the present invention includes receiving a delivery request containing event information and delivery area information from an event detection device configured to specify delivery area information of event information according to a plurality of events, and determining a delivery destination node corresponding to the delivery area information based on the delivery area information.

A program according to a fourth exemplary aspect of the present invention causes a computer to execute a step of receiving a delivery request containing event information and delivery area information from an event detection device configured to specify delivery area information of event information according to a plurality of events, and a step of determining a delivery destination node corresponding to the delivery area information based on the delivery area information.

Advantageous Effects of Invention

According to the above-described exemplary aspects of the present invention, it is possible to provide an information delivery system, a gateway device, a delivery control method and a program that can be used by various business entities to meet diversified needs for information delivery.

DESCRIPTION OF EMBODIMENTS

First Exemplary Embodiment

Exemplary embodiments of the present invention are described hereinafter with reference to the drawings. First, a configuration example of an information delivery system according to a first exemplary embodiment of the invention is described with reference toFIG. 1. The information delivery system inFIG. 1includes an event detection device10and a delivery device20.

The event detection device10detects the occurrence of a plurality of events. The event detection device10specifies delivery area information of event information according to the detected events. The occurrence of events is the occurrence of natural disasters such as an earthquake or Tsunami, the occurrence of a fire, the occurrence of a traffic accident, the occurrence of a crime or the like, for example. Further, the events may include an incidental event that occurs with the occurrence of the above-described event, such as the operation of an emergency vehicle with the occurrence of a fire or a traffic accident.

The event detection device10detects the occurrence of such an event. For example, the event detection device10may detect the occurrence of a natural disaster by receiving a notification about the occurrence of a natural disaster through a computer connected to a government agency. Further, the event detection device10may detect the occurrence of a fire, a traffic accident, a crime or the like by receiving a notification about the occurrence of a fire, a traffic accident, a crime or the like through a computer connected to a fire station or a police station. Furthermore, the event detection device10may detect the operation of an emergency vehicle by communicating with a communication device or the like mounted on the emergency vehicle.

The delivery area information may be information that specifies several meters or several kilometers radius of a point where a natural disaster, a fire, an accident, a crime or the like occurs, for example. Alternatively, the delivery area information may be information that specifies an area within several kilometers in up and down paths from a point of an expressway where a traffic accident occurs. Alternatively, the delivery area information may be information related to a traveling route of an emergency vehicle. The event detection device10notifies the specified delivery area information to the delivery device20.

The delivery device20delivers event information to a delivery destination node corresponding to the delivery area information specified by the event detection device10. In the case where the delivery device20is located in a mobile communication network, the delivery destination node may be a base station or the like, for example. In the case where the delivery device20is located in a wireless LAN network, the delivery destination node may be an access point or the like, for example. In the case where the delivery device20is located in a network different from those networks, the delivery device20may be a communication node that delivers information to a communication terminal or the like.

As described above, the event detection device10can receive a plurality of events notified from different organizations. Thus, the event detection device10can detect the occurrence of a plurality of events. Further, the event detection device10notifies the delivery area information to the delivery device20without recognizing the network configuration where the delivery device20is located. Therefore, the event detection device10can specify the delivery area information from map information or the like that is in the public domain without need to specify information that can be known only by a telecommunications carrier, such as a place where a base station, an access point or the like is located. Further, the delivery device20can deliver event information to an area where the information should be delivered according to an event by determining a delivery destination node corresponding to the delivery area information.

In this manner, by using the information delivery system shown inFIG. 1, it is possible to make information delivery according to the occurrence of various events and further to determine a delivery destination of information for each event, which enables accurate delivery of information to an area in need of the information.

Next, a detailed configuration example of the information delivery system according to the first exemplary embodiment of the invention is described with reference toFIG. 2. The information delivery system inFIG. 2includes a M2M (Machine to Machine) service PF30, a gateway device40, a CBC (Cell Broadcast Center)50, a mobility management node60, a radio base station70, and a mobile terminal80. The gateway device40, the CBC50and the mobility management node60are located in a core network90. The devices located in the core network90and the radio base station70are devices that are managed by a mobile telecommunications carrier. Therefore, the M2M service PF30may be a platform provided by an entity different from a mobile telecommunications carrier or a platform managed by a mobile telecommunications carrier.

The M2M service PF30corresponds to the event detection device10inFIG. 1. The M2M service PF30receives information about the occurrence of a natural disaster such as an earthquake or Tsunami, a fire, a traffic accident, a crime or the like through a computer located in an organization such as a government agency, a police station or a fire station. The M2M service PF30also receives information about the place where each event has occurred. The M2M service PF30determines delivery area information related to an area to deliver event information based on the place where the event has occurred. The M2M service PF30transmits a delivery request containing the event information and the delivery area information to the gateway device40.

The gateway device40relays communication between the M2M service PF30and the devices in the core network90. Specifically, the gateway device40has an interface for communication with an external network outside the core network90and further has an interface for communication with the devices in the core network90. The gateway device40thereby functions as a gateway device with the external network. Further, the gateway device40may be configured using two devices: SCS (Service Capability Server) and MTC IWF. The configurations of the SCS and the MTC IWF are described in detail later. The gateway device40receives the delivery request transmitted from the M2M service PF30.

The gateway device40specifies a delivery destination node corresponding to the received delivery area information. The gateway device40transmits a delivery request containing the event information and the specified delivery destination node information to the CBC50.

The gateway device40may perform authentication as to whether the information transmitted from the M2M service PF30is allowed to be transferred into the core network90. For example, when the gateway device40receives a delivery request for event information, it may determine whether the delivery request is related to an organization for which the event information is allowed to be transferred into the core network90. In other words, the gateway device40may manage information about a list of organizations for which transfer of the delivery request is allowed. Alternatively, the gateway device40may manage information about a list of event information that can be transferred to a device in the core network90.

Further, the gateway device40may perform determination as to whether or not to transfer the delivery request transmitted from the M2M service PF30to the CBC50, which is a transfer destination of the delivery request, according to the processing load condition of the CBC50. The gateway device40may receive information about the processing load from the CBC50on a regular basis or upon receiving a delivery request. The information about the processing load may be CPU utilization in the CBC50, for example. Alternatively, the gateway device40may receive information about the processing load of the radio base station70, the mobility management node60or the like, which is the delivery destination node, through the CBC50.

When the processing load of the CBC50, the radio base station70, the mobility management node60or the like is high, the gateway device40may discard the delivery request transmitted from the M2M service PF30without transferring it. Alternatively, when the processing load of the CBC50or the radio base station is high, the gateway device40may specify and notify a retransmission time of the delivery request to the M2M service PF30. Alternatively, the gateway device40may store the delivery request into a buffer and transmit the delivery request stored in the buffer to the CBC50after the lapse of a specified period of time. The gateway device40can thereby prevent an increase in the processing load of the CBC50or the delivery destination node such as the radio base station or the MME. In other words, the gateway device40can transmit the delivery request into the core network90in consideration of the congestion state of the core network90and the radio base station70.

Further, the gateway device40may perform generation of billing information for billing an organization related to the event information when the delivery request is transmitted from the M2M service PF30. For example, the gateway device40may notify identification information that identifies an organization related to the event information and the presence of the delivery request to a billing device or the like that performs billing processing in the core network90so that the billing device generates a billing profile. The billing device may be a CDF (Charging Data Function), CGF (Charging Gateway Function) or the like located in the network defined in the 3GPP, for example.

The CBC50transmits the delivery request to the mobility management node60based on the delivery destination node information notified from the gateway device40. In the delivery destination node information, the mobility management node60as a delivery destination may be specified. Alternatively, in the case where the radio base station70as a delivery destination is specified in the delivery destination node information, the CBC50may extract the mobility management node60connected with the specified radio base station70. In this case, the CBC50may manage the mobility management node60and the specified radio base station70using an information table or the like.

The mobility management node60receives the delivery request transmitted from the CBC50. For example, the mobility management node60may be MME (Mobility Management Entity), which is a node of the core network defined in the 3GPP. The mobility management node60may be located in a network in units of prefectures or in units of regions smaller than the prefectures.

The mobility management node60transmits the event information contained in the received delivery request to a plurality of radio base stations70connected to the mobility management node60. The mobility management node60may transmit the received event information to all of the connected radio base stations70. Alternatively, in the case where the radio base station70as a delivery destination is specified from the CBC50, the mobility management node60may transmit the received event information to the specified radio base station70.

The radio base station70receives the event information transmitted from the mobility management node60. The radio base station70transmits the received event information to the mobile terminal80that belongs to the area managed by the radio base station70.

The mobile terminal80may be a mobile phone terminal, a smartphone terminal, a notebook personal computer or the like, a moving means such as a vehicle or a train with a communication function, or a machine worn by a user such as a watch with a communication function. Alternatively, the mobile terminal80may be a device such as a vending machine with a communication function that does not frequently move and is controlled through radio.

Further, although the gateway device40and the CBC50are different devices in the above description, the function implemented in the gateway device40may be implemented in the CBC50, for example. In other words, the gateway device40and the CBC50may be located as an integrated device in the core network90. Further, in the case where the gateway device40and the CBC50are different devices, the CBC50may determine a delivery destination node based on the delivery area information.

Configuration examples of SCS40A and MTC IWF40B according to the first exemplary embodiment of the invention are described hereinafter with reference toFIGS. 3A and 3B. The SCS40A inFIG. 3Aincludes a service PF interface41, a control unit43, and a NW configuration information DB45. The SCS40A may be referred to as MTC Server.

The service PF interface41is used for communicating with the M2M service PF30and transmits and receives data to and from the M2M service PF30. The service PF interface41receives a delivery request containing event information and delivery area information from the M2M service PF30. The service PF interface41outputs the delivery request to the control unit43. Alternatively, the service PF interface41may output the event information contained in the delivery request to a notification unit44of the MTC IWF40B and output the delivery area information contained in the delivery request to the control unit43.

The control unit43specifies a delivery destination node based on the delivery area information output from the service PF interface41. The control unit43specifies a delivery destination node using the NW configuration information DB45.

A configuration example of the NW configuration information DB45is described hereinafter with reference toFIG. 4. The NW configuration information DB45manages area information and base stations that belong to the area in association with each other. For example, an area A and base stations eNB#1, eNB#2and eNB#3that belong to the area A are associated with each other. Further, an area B and base stations eNB#4, eNB#5and eNB#6that belong to the area B are associated with each other. Further, an area C and base stations eNB#7and eNB#8that belong to the area C are associated with each other. The area C may be specified as “along Route X”, for example. Further, as the area information, a range of several kilometers on an expressway may be specified.

The eNB is the name of a radio base station that is used in LTE defined in the 3GPP. Although eNB is used as an example of a base station in this figure, a radio base station used in a different communication system from LTE, such as a radio base station used in a W-CDMA wireless system, and area information may be associated with each other.

Further, although an example in which area information and base stations are managed in association with each other is described in this figure, area information and a node in the core network such as a mobility management node may be managed in association with each other, for example. Further, area information, a node in the core network and base stations may be managed in association with one another.

Referring back toFIG. 3, the control unit43extracts the base stations associated with the delivery area information output from the service PF interface41. The control unit43outputs delivery destination node information related to the extracted base stations and event information to the notification unit44of the MTC IWF40B.

A configuration example of the MTC IWF40B shown inFIG. 3Bis described hereinafter. The MTC IWF40B includes the notification unit44and a CBC interface42. The notification unit44transmits a delivery request containing the event information and the delivery destination node information output from the control unit43of the SCS40A to the CBC50through the CBC interface42. Alternatively, the notification unit44transmits a delivery request containing the delivery destination node information output from the control unit43of the SCS40A and the event information output from the service PF interface41of the SCS40A to the CBC50through the CBC interface42.

The CBC interface42is used for communicating with the CBC50and transmits and receives data to and from the CBC50.

A sequence showing a flow of signals between the M2M service PF30and the CBC50in the information delivery system according to the first exemplary embodiment of the invention is described hereinafter with reference toFIG. 5. First, the M2M service PF30receives event information such as a natural disaster like an earthquake or Tsunami, a fire, a traffic accident or a crime and information about the place where the event has occurred through a computer located in an organization such as a government agency, a police station or a fire station (S11).

Next, the M2M service PF30transmits a delivery request containing the event information and information about a delivery area to the SCS40A (S12). The SCS40A receives the delivery request transmitted from the M2M service PF30and transmits it to the MTC IWF40B (S13). In this figure, the SCS40A and the MTC IWF40B are illustrated as different devices. This is on the ground that the SCS40A and the MTC IWF40B are different devices in the network configuration defined in the 3GPP. The network configuration defined in the 3GPP is described in detail later.

The MTC IWF40B specifies a delivery destination node based on the delivery area information. The delivery destination node is specified using the NW configuration information DNB45as described above. The MTC IWF40B transmits information about the specified delivery destination node and the event information to the CBC50(S14).

In UE, information for determining whether to receive information delivered in an emergency situation (emergency delivery necessity information) may be notified to the CBC50. For example, in LTE, the emergency delivery necessity information may be set together with a disaster type or the like to Warning Type, Warning Message or the like. Further, in 3G, the emergency delivery necessity information may be set together with a disaster type or the like to Message ID, Serial Number or the like. Further, the emergency delivery necessity information may be set to another parameter or message. The emergency delivery necessity information may be contained in any of the messages transmitted in Steps S12, S13and S14.

For example, the emergency delivery necessity information may be information for determining whether only an MTC device should receive the information or an MTC device should not receive the information (or discard it). The MTC device is a device included in a UE and used for MTC defined as machine communication. The MTC and the MTC device are defined in the 3GPP technical specification. The CBC50may receive a flag indicating whether it is for the MTC device as the emergency delivery necessity information.

Alternatively, the CBC50may determine that all of the information transmitted from the MTC IWF40B are for the MTC device. In this case, the emergency delivery necessity information is not needed.

A sequence showing a flow of signals between the CBC50and the mobile terminal80in the information delivery system is described hereinafter with reference toFIG. 6. The sequence in this figure shows the flow of signals in the network defined in the 3GPP. Information delivery between the CBC50and the mobile terminal80is performed using the emergency information delivery system.

First, when the delivery destination node is notified in Step S14ofFIG. 5, the CBC50transmits WRITE-REPLACE WARNING REQUEST to the MME (S21). WRITE-REPLACE WARNING REQUEST contains TAI, Warning Area List, Extended Repetition Period, Warning Type, Warning Message Contents and the like. TAI is the abbreviated name for Tracking Area Identity indicating a position registration area. When TAI is contained in WRITE-REPLACE WARNING REQUEST, the MME delivers information to cells or base stations that belong to the same TAI. Further, the CBC50sets information (flag) as to whether it is for the MTC device to Warning Type or Warning Message.

Next, when the MME receives WRITE-REPLACE WARNING REQUEST, it transmits WRITE-REPLACE WARNING RESPONSE to the CBC50as a response signal (S22). Then, when the MME receives TAI in Step S21, it transmits WRITE-REPLACE WARNING REQUEST to the eNB that belongs to the received TAI (S23). When the MME does not receive TAI in Step S21, it may transmit WRITE-REPLACE WARNING REQUEST to all of the eNBs under its control.

Then, the eNB delivers the information set to WRITE-REPLACE WARNING REQUEST to a plurality of UEs under its control through broadcast (S24and S25). In LTE ETWS, a first report (paging) called primary notification is sent as emergency delivery (S24), and then a second report called secondary notification is sent for detailed information (S25). For example, by adding the emergency delivery necessity information to the first report, the UE can determine whether the broadcast delivery is addressed to its own device or not. When the emergency delivery necessity information indicating that it is for the MTC device is set to the first report, the UE that is not the MTC device determines that the broadcast delivery is not addressed to its own device. In this case, the UE that is not the MTC device can discard the second report containing the detailed information. On the other hand, when the emergency delivery necessity information indicating that it is not for the MTC device is set to the first report, the MTC device determines that the broadcast delivery is not addressed to its own device. In this case, the MTC device can discard the second report containing the detailed information. Therefore, the MTC device and the UE that is not the MTC device do not need to perform unnecessary data processing and thus not need to unnecessarily use resources for data processing.

Then, the eNB transmits WRITE-REPLACE WARNING RESPONSE as a response signal to the MME (S26).

As described above, by using the M2M service PF30according to the first exemplary embodiment of the invention, it is possible to detect an event related to an organization such as a government agency, a police station or a fire station. Thus, by using the information delivery system according to the first exemplary embodiment of the invention, it is possible to deliver event information in response to a request from a plurality of organizations such as a government agency, a police station and a fire station.

Further, in the gateway device40, by using the NW configuration information DB45, it is possible to determine a delivery destination node for each event information. It is thereby possible to determine a delivery area arbitrarily for each of a plurality of organizations such as a government agency, a police station and a fire station and transmit necessary information to an necessary area.

Further, by using the CBC50, it is possible to deliver the event information to the mobile terminal80using the existing emergency information delivery system. It is thereby possible to eliminate the need for constructing a new network and prevent an increase in cost required for delivery of the event information.

Second Exemplary Embodiment

A configuration example of SCS40A_1according to a second exemplary embodiment of the invention is described hereinafter with reference toFIG. 7. The SCS40A_1includes a service PF interface41, a control unit43, a NW configuration information DB45and a priority information DB46. The elements other than the priority information DB46are the same as those ofFIG. 3Aand detailed description thereof is omitted.

The priority information DB46specifies a priority for each of an organization such as a government agency, a police station or a fire station. Specifically, in the priority information DB46, priorities are set so that, when event information or the like is notified at the same time from a plurality of organizations such as a government agency, a police station and a fire station, the event information or the like from an organization for which a high priority is set is delivered by priority. The case where event information or the like is notified at the same time includes the case where a plurality of event information or the like are notified within a specified period of time. For example, the case where event information or the like is notified at the same time includes the case where a plurality of event information are notified one after another during several seconds.

A configuration example of the priority information DB46is described hereinafter with reference toFIG. 8. The priority information DB46is made up of information related to business entities and information related to priorities. The business entities are organizations such as a government agency, a police station and a fire station, which are shown as business entities A to C in this figure. A priority_1to a priority_3are set as the priorities. The priority_1is the highest priority level, and the priority level is lower as the number increases. As a matter of course, the priority level may be high when the number is large, and the priority level may is lower as the number decreases. In this figure, the priority_1is set for the business entity A, the priority_2is set for the business entity B, and the priority_3is set for the business entity C. Thus, the business entity A has the highest priority and the business entity C has the lowest priority.

A sequence showing a flow of signals between the M2M service PF30and the CBC50in the information delivery system according to the second exemplary embodiment of the invention is described hereinafter with reference toFIG. 9. First, the M2M service PF30receives a notification of event information1from the business entity A (S31). Next, the M2M service PF30notifies a delivery request1to the SCS40A_1(S32). Likewise, the M2M service PF30receives a notification of event information2from the business entity B (S33) and then notifies a delivery request2to the SCS40A_1(S34), and receives a notification of event information3from the business entity (S35) and then notifies a delivery request3to the SCS40A_1(S36). The delivery requests1to3contain the identifier of the corresponding business entity.

Then, in the case where the SCS40A_1receives the delivery requests1to3within a specified period of time, it performs priority determination on each of the delivery requests (S37). The SCS40A_1performs priority determination using the priority information DB46. Referring toFIG. 8, the delivery request1transmitted based on the event information1from the business entity A has the highest priority. Therefore, the SCS40A_1transmits the delivery request1to the MTC IWF40B (S38). The processing of Step S39is the same as Step S14inFIG. 5and thus not redundantly described.

In Step S37, the SCS40A_1may discard the delivery requests2and3other than the delivery request1to be notified to the MTC IWF40B. In this case, the SCS40A_1may notify each business entity that the delivery request has been discarded through the M2M service PF30and make a request for retransmission to notify the event information again after the lapse of a specified period of time. Alternatively, in Step S37, the SCS40A_1may accumulate the delivery requests2and3in a buffer and transmit the delivery request2to the MTC IWF40B after the lapse of a specified period of time and then further transmit the delivery request3to the MTC IWF40B after the lapse of a specified period of time. In other words, the SCS40A_1may transmit the delivery requests at regular time intervals in order of priority.

Although the case where the SCS40A_1receives event information of a plurality of business entities from one M2M service PF30is described inFIG. 9, the present invention may be applied in the same manner also in the case where it receives event information of a plurality of business entities from a plurality of M2M services PF30, for example.

Another example of the case where a plurality of delivery requests are notified from the M2M service PF30is described with reference toFIG. 10. Steps S41to S46are the same as Steps S31to S36inFIG. 9and thus not redundantly described. In Steps S42, S44and S46, when the SCS40A_1receives a plurality of delivery requests within a specified period of time, it generates one delivery request message by putting the plurality of delivery requests together and notifies the generated one delivery request message to the MTC IWF40B (S47). The one delivery request message contains the delivery area information and the event information of the delivery requests1to3.

Then, the MTC IWF40B specifies a delivery destination node for each of the delivery requests and notifies the specified delivery destination node to the CBC50(S48).

As described above, by using the SCS40A_1according to the second exemplary embodiment of the invention, it is possible to deliver event information based on priorities even in the case of receiving a plurality of delivery requests within a specified period of time. It is thereby possible to process an emergency message or the like with a high priority in preference to other event information, for example, to deliver necessary information without fail.

Further, as described inFIG. 10, by putting a plurality of delivery requests1to3together into one delivery request in the SCS40A_1for the MTC IWF40B, it is possible to process a plurality of delivery requests at a time. It is thereby possible to deliver a delivery request received from the M2M service PF30without discarding it.

Third Exemplary Embodiment

A configuration example of SCS40A_2according to a third exemplary embodiment of the invention is described hereinafter with reference toFIG. 11. The SCS40A_2includes a service PF interface41, a control unit43, a NW configuration information DB45, and a data format information DB47. The elements other than the data format information DB47are the same as those ofFIG. 3Aand detailed description thereof is omitted.

The data format information DB47manages delivery contents and the data format of the delivery contents in association with each other. A configuration example of the data format information DB47is described hereinafter with reference toFIG. 12. The data format information DB47manages delivery contents and a data format in association with each other. For example, when delivering text information, a text message is used as a data format. When delivering route information, map data is used as a data format. Further, when controlling the operation of a device such as a mobile communication device at a delivery destination, a device control signal is delivered as a data format. For example, the route information is used to notify a route or the like along which an emergency vehicle travels from an accident site to a hospital or the like to vehicles or the like traveling near the route. Further, for example, the control of the device operation may be turning ON/OFF the power of the device.

Referring back toFIG. 11, when the control unit43receives a delivery request from the service PF interface41, it extracts the delivery contents of the event information set to the delivery request. The control unit43specifies the data format corresponding to the delivery contents using the data format information DB47. The control unit43notifies information about the specified data format to the notification unit44of the MTC IWF40B.

As described above, by using the data format information DB47in the SCS40A_2according to the third exemplary embodiment of the invention, it is possible to deliver various information, not limited to text information. In addition to the contents shown inFIG. 12, a data format may be specified for image information, video information and the like.

Further, although the configuration in which the data format information DB47is added to the configuration of the SCS40ofFIG. 3Ais illustrated inFIG. 11, the data format information DB47may be added to the configuration of the SCS40A_1ofFIG. 7.

Fourth Exemplary Embodiment

A sequence showing a flow of signals between the CBC50and the mobile terminal80in the information delivery system according to a fourth exemplary embodiment of the invention is described hereinafter with reference toFIG. 13. A flow of a process in the case where an information delivery area changes in a short time, such as when delivering information in the range of several kilometers from a moving emergency vehicle, is described usingFIG. 13. The processing in Steps S51to S56is the same as the processing in Steps S21to S26inFIG. 6and thus detailed description thereof is omitted.

It is assumed that UE#1is a terminal that is located within the range of several kilometers from an emergency vehicle and uses a broadcast delivery service, and UE#2is a terminal that is mounted on the emergency vehicle. After Step S55, a position information notification is sent from the UE#2on the emergency vehicle to the M2M service PF30in order to notify a change in position information (S57). When the position information of the UE#2is changed, the M2M service PF30sets new delivery area information and notifies it to the SCS40. The processing ofFIG. 5is repeated after that.

Further, the UE#2may send a position information notification that notifies a change in position information to MME, HSS (subscriber information management device) or the like, which is a device that manages position information in the core network90(S57). When the position information of a mobile communication device such as the UE#2is changed, the MME, HSS or the like in the core network90is updated, and the latest position information is stored. The CBC50may receive the latest position information of the UE#2from the MME, HSS or the like and determine a delivery destination node of event information.

As described above, by using the information delivery system according to the fourth exemplary embodiment of the invention, the following effect is obtained. The M2M service PF30receives position information of a mobile communication device at the center position of information delivery and can thereby change the delivery area according to the received position information. It is thereby possible to change the information delivery area within a short period of time. Further, the CBC50can change the information delivery area within a short period of time also by receiving the latest position information of the mobile communication device at the center position of information delivery from a device such as MME or HSS in the core network.

When the M2M service PF30receives position information from the UE#2, the following effect is also obtained. For example, there is a case where the UE#2enters Idle mode and a connection state of a physical link with eNB or the like is disconnected. In such a case, even in the case where the position information of the UE#2is changed, MME, HSS or the like cannot be informed of the change in the position information of the UE#2. On the other hand, if the UE#2notifies the position information to the M2M service PF30as application information, it is possible to notify a change in position information.

Further, when the CBC50receives the latest position information from MME, HSS or the like, the following effect is also obtained. In this case, a change in position information is notified using a control message or the like in the core network90. Therefore, position information change processing can be done earlier than the case where position information is notified as application information. The CBC50can thereby determine a delivery destination node earlier than the case of receiving updated delivery area information from the M2M service PF30.

Other Exemplary Embodiments

A network system in the case of applying the SCS40A, the MTC IWF40B and the CBC50according to the first to fourth exemplary embodiments described above to the network defined in the 3GPP technical specification is described with reference toFIG. 14.

The MTC-IWF212and the SCS213are placed to relay communication among the MSC202, the MME203, the SGSN204and the AS214. The AS214is placed in an external communication network different from a mobile communication network. The MTC-IWF212is placed in the mobile communication network. The SCS213may be placed in any one of the mobile communication network and the external communication network. Thus, the location of the SCS213depends on a network design policy of a telecommunications carrier, an AS company or the like.

Further, the MTC-IWF212and the CBC111are connected to provide information delivery in response to a plurality of events notified from different organizations using the emergency information delivery system.

Although the present invention is described as a hardware configuration in the above exemplary embodiments, the present invention is not limited thereto. The present invention may be implemented by causing a CPU (Central Processing Unit) to execute a computer program to perform processing of the control unit in the gateway device40.

In the above example, the program can be stored and provided to the computer using any type of non-transitory computer readable medium. The non-transitory computer readable medium includes any type of tangible storage medium. Examples of the non-transitory computer readable medium include magnetic storage media (such as floppy disks, magnetic tapes, hard disk drives, etc.), optical magnetic storage media (e.g. magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R/W, and semiconductor memories (such as mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory), etc.). The program may be provided to a computer using any type of transitory computer readable medium. Examples of the transitory computer readable medium include electric signals, optical signals, and electromagnetic waves. The transitory computer readable medium can provide the program to a computer via a wired communication line such as an electric wire or optical fiber or a wireless communication line.

The present invention is not limited to the above-described exemplary embodiments, and various changes and modifications may be made without departing from the scope of the invention.

This application is based upon and claims the benefit of priority from Japanese patent application No. 2012-101826, filed on Apr. 26, 2012, the disclosure of which is incorporated herein in its entirety by reference.

REFERENCE SIGNS LIST