WO2018100687A1 - EDGE DEVICE CONTROL METHOD, IoT HUB, AND STORAGE MEDIUM - Google Patents

EDGE DEVICE CONTROL METHOD, IoT HUB, AND STORAGE MEDIUM Download PDF

Info

Publication number
WO2018100687A1
WO2018100687A1 PCT/JP2016/085591 JP2016085591W WO2018100687A1 WO 2018100687 A1 WO2018100687 A1 WO 2018100687A1 JP 2016085591 W JP2016085591 W JP 2016085591W WO 2018100687 A1 WO2018100687 A1 WO 2018100687A1
Authority
WO
WIPO (PCT)
Prior art keywords
distribution
delivery
message
iot
iot hub
Prior art date
Application number
PCT/JP2016/085591
Other languages
French (fr)
Japanese (ja)
Inventor
タン ハイ ヴォ
丹 許
森重　健洋
宏太 川原
大輔 岡部
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2016/085591 priority Critical patent/WO2018100687A1/en
Publication of WO2018100687A1 publication Critical patent/WO2018100687A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/44—Star or tree networks

Definitions

  • the present invention relates to an IoT system that controls a large number of edge devices.
  • the technology for miniaturization and high functionality of computers has progressed, and computers have been placed in various places and devices and connected to the Internet. In recent years, these are called Internet of Things (IoT), and IoT business using accumulated data has attracted social attention.
  • IoT Internet of Things
  • the IoT system includes an edge device, an information transfer network, an IoT hub, and a content server.
  • the edge device is a sensor for each physical quantity that collects data for business use, and a gateway device (IoT-GW) that collectively controls the sensors.
  • the sensor collects data of factories and the like and is collected in a specific IoT-GW.
  • the IoT-GW transfers data from the connected sensor to the cloud-side IoT hub through the information transfer network, and also manages the sensor.
  • the information transfer network provides a data transfer service between the edge device and the cloud via the network device.
  • the IoT hub controls the edge device (for example, IoT-GW), and processes and shapes the data collected from the IoT-GW into a necessary format.
  • the content calculated based on the formatted data is visualized via the content server and provided to the IoT service user.
  • IoT service providers There are IoT service providers, IoT platform providers, and information transfer network providers as business providers in the IoT business.
  • the IoT service provider owns the content server, the IoT-GW, and sensors under the content server, and provides data from the sensor to the IoT service user in the form of content.
  • IoT platform provider owns IoT hub and collects edge device control and factory data to provide processing and shaping services.
  • the information transfer network provider owns an information transfer network between the factory and the cloud and provides a data transfer service.
  • IoT service providers install edge devices in various regions in order to obtain necessary data. For example, there are cases where a plurality of models of IoT-GW are installed in the same area, and a plurality of models of sensors are connected to the same model of IoT-GW.
  • the IoT service provider collects specific data in a specific area (for example, radiation dose data of area A) in response to a user request.
  • the IoT hub does not always collect data from all the sensors via the IoT-GW, but the data transfer service function of the sensor to the IoT-GW for the purpose of reducing useless data communication.
  • the radiation dose data of area A is collected only when necessary by controlling
  • the data transfer service function is a function in which the IoT-GW transfers the sensor data to the IoT hub.
  • the IoT service provider distributes a control command to the IoT-GW by unicast by specifying the ID of the IoT-GW.
  • the same control command is distributed to each IoT-GW individually, a difference in the control time to the IoT-GW is generated, and wasteful data communication occurs in the information transfer network, which increases the cost of the IoT service. there were.
  • the IoT service provider updates the IoT-GW software to the latest state in order to continue the business.
  • the IoT service provider normally performs software update control by distributing a software update control command and an update file to individual IoT-GWs by unicast by specifying an IoT-GW ID.
  • the same control command and update file are distributed to each IoT-GW, useless data communication occurs, and the cost of the IoT service is increased.
  • the distribution request message is registered from the content server to the IoT hub. Based on the delivery start date and time in the delivery message registered by the IoT hub, the control command is delivered to the IoT-GW.
  • the delivery start date and time are the same, the delivery request message registered first is preferentially delivered.
  • the IoT hub cannot control the distribution order according to the urgency level of the distribution request message with respect to the distribution request message having the same distribution start date and time.
  • edge devices In the IoT business, the number of edge devices that collect data at any location is expected to increase further in the future. While edge devices are installed in various regions, there are cases where there are a plurality of types of IoT-GWs in the same region, and a plurality of types of sensors are connected to the same type of IoT-GW. When an IoT service provider controls an edge device, an efficiency control method that suppresses the operation cost of the IoT business is required.
  • a control command for a data transfer service function for a specific sensor is distributed to the IoT-GW.
  • IoT-GW is installed in a plurality of regions, and there are a plurality of models of IoT-GW in the same region. Deliver control commands and update files.
  • the IoT hub can appropriately determine whether broadcast distribution or unicast distribution is performed for each service area to be distributed.
  • Patent Document 1 a service area to be distributed is specified, and a control command or an update file is distributed by broadcast from an IoT hub to reduce a control time difference to the IoT-GW, and to a distribution target IoT-GW.
  • Useless data communication can be reduced.
  • Patent Document 2 when the delivery start date and time is the same for delivery request messages from different content servers, the delivery order according to the priority can be controlled, but the delivery request messages from the same content server all have the same priority. There was a problem that the distribution order could not be controlled.
  • the present invention has been made in view of the above problems, and an object thereof is to appropriately distribute a message for each service area to be distributed.
  • the present invention provides an edge device control method in which an IoT hub having a processor and a memory controls an edge device in one or more service areas connected via a network, wherein the IoT hub transmits a delivery request message.
  • the first step of receiving the second message the second step in which the IoT hub identifies the service area to be distributed based on the transmission condition included in the distribution request message, and the IoT hub has been identified.
  • the IoT hub for each service area to be distributed, the IoT hub appropriately determines a distribution method (broadcast distribution or unicast distribution) based on distribution conditions such as an edge device (for example, IoT-GW model).
  • a distribution method for example, IoT-GW model.
  • IoT-GW edge device
  • the edge device control method of the present invention can be applied not only to control of data transfer service functions and distribution of update files, but also to general control of edge devices.
  • FIG. 9 is a sequence diagram of processing performed in update file distribution according to the embodiment of this invention.
  • the information transfer network is configured with a core network of Long Term Evolution (hereinafter LTE), which is a communication standard for the 3.9th generation mobile phone, and broadcast distribution is performed by LTE broadcast distribution technology evolved Multimedia Broadcast Service ( Hereinafter referred to as eMBMS).
  • LTE Long Term Evolution
  • eMBMS LTE broadcast distribution technology evolved Multimedia Broadcast Service
  • eMBMS is characterized in that a radio resource usage rate in a mobile communication network is high because broadcast distribution can be performed at the same frequency to a plurality of distribution service areas.
  • the IoT system includes a content server 2, an IoT hub (IoT hub) 1, an LTE core network 3, an evolved Node B (eNB 1, eNB 2) that is a base station 6, an IoT-GW 5, a sensor 7.
  • the subordinates of the base station (eNB) 6 are distribution service areas 4-A and 4-B. In order to indicate an entire distribution service area, the symbol “4” in which “ ⁇ ” and the subsequent symbols are omitted is used.
  • the distribution request message 200 is transmitted from the content server 2 to the IoT hub 1.
  • the IoT hub 1 When receiving the distribution request message 200, the IoT hub 1 generates and distributes the broadcast distribution message 300 or the unicast distribution message 350 according to the state of the IoT-GW 5 (edge device) in the distribution service area 4.
  • FIG. 2 is a diagram showing an example of information of the distribution request message 200.
  • the distribution request message 200 includes information on an IoT-GW model name 201, a sensor model name 202, a distribution start date and time 203, a priority 204, and a distribution content 205.
  • the IoT-GW model name 201 is information used as a transmission condition for specifying the distribution service area 4 to be distributed.
  • the sensor model name 202 is information for collecting specific data such as temperature and odor, and may not be specified depending on the content of control.
  • One or more IoT-GW model name 201 and sensor model name 202 can be specified.
  • the distribution start date and time 203 and the priority level 204 are information used for controlling the distribution order.
  • the distribution content 205 indicates a control command executed by the IoT-GW 5, an update file, or the like.
  • FIG. 3 is a block diagram showing functions of the IoT hub 1 of the present embodiment.
  • the IoT hub 1 includes a distribution request message receiving unit 100, a distribution method processing unit 120, a distribution order control unit 110, a distribution start date and time management unit 130, a transmission message editing unit 140, and a distribution message transmission unit 150.
  • the IoT hub 1 includes a distribution request message receiving unit 100, a distribution method processing unit 120, a distribution order control unit 110, a distribution start date and time management unit 130, a transmission message editing unit 140, and a distribution message transmission unit 150.
  • the delivery method processing unit 120 includes a delivery service area analysis unit 121, a delivery method determination unit 122, an edge device and SAI association table 123, a broadcast delivery message table 125, and a unicast delivery message table 127.
  • the distribution order control unit 110 includes a distribution order determination unit 111 and a distribution schedule table 112.
  • the IoT hub 1 collects the data of the sensor 7 from the edge device (IoT-GW 5), and processes or shapes the data into a predetermined format, as described in the conventional example.
  • a function to output to the server 2 is included. Since this function is the same as that of the conventional example, illustration and description are omitted.
  • FIG. 4 is a block diagram showing the configuration of the IoT hub 1.
  • the IoT hub 1 includes a central processing unit (CPU) 11, a memory 12, and a communication port 13, which are connected to each other.
  • CPU central processing unit
  • memory 12 a memory
  • communication port 13 a communication port
  • the memory 12 includes a distribution request message reception unit 100, a distribution service area analysis unit 121, a distribution method determination unit 122, a distribution order determination unit 111, a distribution start date management unit 130, a transmission message editing unit 140, a distribution A program group for realizing the message transmission unit 150, an edge device and SAI association table 103, a broadcast distribution message table 125, a unicast distribution message table 127, and a distribution schedule table 112 are stored.
  • the CPU 11 loads and executes each of the above programs stored in the memory 12, thereby realizing distribution method processing and distribution order control in the IoT hub 1.
  • the communication port 13 communicates with other devices connected to the LTE core network 3.
  • the IoT hub 1 can receive the distribution request message 200 not only from one content server 2 but also from a plurality of content servers 2. If the structure of the distribution request message 200 is the same from different content servers 2, the processing in the IoT hub 1 is the same.
  • the CPU 11 operates as a functional unit that provides a predetermined function by processing according to the program of each functional unit.
  • the CPU 11 functions as the distribution method determination unit 122 by performing processing according to the distribution method determination program.
  • the CPU 11 also operates as a function unit that provides each function of a plurality of processes executed by each program.
  • a computer and a computer system are an apparatus and a system including these functional units.
  • Information such as programs and tables for realizing each function of the IoT hub 1 is a storage subsystem, a nonvolatile semiconductor memory, a hard disk drive, a storage device such as Solid State Drive (hereinafter, SSD), an IC card, an SD card, It can be stored in a computer-readable non-transitory data storage medium such as a DVD.
  • SSD Solid State Drive
  • FIG. 5 is a flowchart illustrating an example of processing performed by the distribution request message receiving unit 100.
  • the distribution request message receiving unit 100 first assigns a message ID that can uniquely identify the message to the received distribution request message 200 (S1).
  • the distribution request message receiving unit 100 transmits the message ID and the information of the IoT-GW model name 201 to the distribution service area analyzing unit 121 (S2).
  • the distribution request message receiving unit 100 transmits the message ID, the priority 204, and the distribution start date / time 203 to the distribution order determining unit 111 (S3).
  • the distribution request message receiving unit 100 stores the message ID, the sensor model name 202, and the distribution content 205 information in the broadcast distribution message table 125 (S4). Further, the distribution request message receiving unit 100 stores the message ID, the sensor model name 202, and the distribution content 205 information in the unicast distribution message table 127 (S5).
  • the processing of steps S2 to S5 can be executed in parallel by the distribution request message receiving unit 100.
  • the distribution request message receiving unit 100 can improve the overall processing efficiency by performing the above parallel processing and transmitting necessary information to the next functional unit.
  • the distribution request message receiving unit 100 sets the message ID assigned to the distribution request message 200 in FIG. 2 to “05” (see FIGS. 9, 10, and 12).
  • FIG. 6 is a flowchart illustrating an example of processing performed by the distribution service area analysis unit 121.
  • the distribution service area analysis unit 121 receives the message ID and the information of the IoT-GW model name 301 from the distribution request message 200 (S11).
  • the distribution service area analysis unit 121 refers to the edge device and SAI association table 123 based on the received IoT-GW model name 301, and identifies the service area ID (Service Area Identifier: below) corresponding to the IoT-GW model name 301 SAI) is acquired (S12). Next, the distribution service area analysis unit 121 transmits the acquired SAI, the IoT-GW model name 301, and the message ID to the distribution method determination unit 122 (S13).
  • the distribution service area analysis unit 121 can acquire the SAI from the preset edge device and SAI association table 123 and notify the distribution method determination unit 122 of the SAI.
  • FIG. 7 shows an example of an edge device and SAI association table 123.
  • the edge device and SAI association table 123 includes number 1231, MBMS-GW1232, MME1233, MCE1234, eNB1235, SAI1236, IoT-GW model name 1237, IoT-GW ID1238, sensor model name 1239, and so on.
  • the total number of IoT-GWs 1240 and the distribution method determination reference value 1241 are included in one entry.
  • eMBMS Multimedia Broadcast Multicast Service Gateway
  • MME Mobility Management Entity
  • MCE Entity
  • eNB 1235 a network device for broadcast distribution.
  • the information of the edge device and SAI association table 123 can be set and changed by the IoT platform provider.
  • the distribution method determination reference value 1241 is set to the total number of IoT-GWs 5 for the purpose of efficiently controlling edge devices by suppressing useless data communication.
  • the present invention is not limited to this, and different information (for example, the total number of sensors 7 and the like) can be set, and the distribution method determination reference value 1241 for the information can be set with a different value for each SAI 1236. It is.
  • the MBMS-GW 1232, MME 1233, MCE 1234, and eNB 1235 columns are network devices necessary for using eMBMS.
  • other broadcast or multicast distribution technologies established by each international standard organization of the mobile communication network are described.
  • the field of the core network device is set instead of the above-mentioned field.
  • FIG. 8 is a flowchart illustrating an example of processing performed by the distribution method determination unit 122.
  • the distribution method determination unit 122 receives the message ID, the information on the IoT-GW model name 1237 and the SAI 1236 from the distribution service area analysis unit 121 (S21).
  • the distribution method determining unit 122 repeats the loop of steps S22 to S29 for each SAI 1236.
  • the delivery method determination unit 122 acquires the IoT-GW total number 1240 and the delivery method determination reference value for each SAI 1236 from the edge device and SAI association table 123 (S23). Next, the distribution method determination unit 122 determines whether or not the total number of IoT-GWs 1240 is larger than the distribution method determination reference value 1241 (S24).
  • step S25 the distribution method determination unit 122 acquires the MBMS-GW 1232, MME 1233, MCE 1234, and eNB 1235 information corresponding to the SAI from the edge device and SAI association table 123.
  • the delivery method determination unit 122 stores the information of the SAI 1236, the MBMS-GW 1232, the MME 1233, the MCE 1234, and the eNB 1235 in the entry with the matching message ID 1251 in the broadcast delivery message table 125.
  • the distribution method determination unit 122 obtains information on the IoT-GW ID 1238 corresponding to the SAI 1236 in step S27 and the edge device and SAI association table 123. Get more. Then, the delivery method determining unit 122 stores the information of the ID 1238 of the IoT-GW in the entry with the matching message ID 1271 in the unicast delivery message table 127 (S28).
  • the delivery method determination unit 122 it is characterized that it is determined for each SAI whether broadcast delivery or unicast delivery. Accordingly, it is possible to efficiently control the edge device by suppressing useless data communication for each SAI.
  • FIG. 9 is a diagram illustrating an example of the broadcast delivery message table 125.
  • the broadcast delivery message table 125 includes message ID 1251, MBMS-GW 1252, MME 1253, MCE 1254, eNB 1255, SAI 1256, sensor model name 1257, and delivery content 1258 in one entry.
  • MBMS-GWs 1252 to SAI 1256 have the same configuration as the edge device and SAI association table 123 shown in FIG.
  • FIG. 10 is a diagram showing an example of the unicast delivery message table 127.
  • the unicast delivery message table 127 includes message ID 1271, IoT-GW ID 1272, sensor model name 1273, and delivery content 1274 in one entry. Since the delivery method determination unit 122 determines a delivery method for each SAI, the broadcast delivery message table 125 has a plurality of SAIs for one message ID 1271, and the unicast delivery message table 127 has a plurality of IoT-GW5 IDs. May have.
  • FIG. 11 shows a flowchart of processing performed in the distribution order determination unit 111.
  • the distribution order determination unit 111 determines the distribution order based on information on the distribution start date and time, priority, and registration order. This process is executed after the distribution request message receiving unit 100 receives the distribution request message 200.
  • the delivery order determination unit 111 receives the message ID, the priority 204, and the delivery start date and time 203 from the delivery request message receiving unit 100 (S31). Next, the delivery order determination unit 111 determines whether there is a message having the same delivery start date / time in the messages stored in the delivery schedule table 112 based on the delivery start date / time 203 received from the delivery request message 200. Determine (S32). If there is a message with the same delivery start date and time, the process proceeds to step S33, and if not, the process proceeds to step S37.
  • the delivery order determination unit 111 determines the delivery order of new messages in the order of delivery start date and time (S37). Thereafter, the process proceeds to step S36.
  • the delivery order determination unit 111 identifies the message and the priority 204 (S33).
  • the delivery order determination unit 111 determines whether there is a message having the same priority in the specified message group based on the priority 204 of the new message (S34). If there is no message with the same priority in the identified message group, the process proceeds to step S38, and the delivery order determination unit 111 determines the delivery order of new messages in the order of priority within the identified message group.
  • the delivery order determination unit 111 puts the new message in the last delivery order among the messages with the same delivery start date and time and the same priority. Determine (S35). Finally, the delivery order determination unit 111 updates the delivery order of messages in the delivery schedule table 112 (S36).
  • the delivery order determination unit 111 updates the delivery schedule table 112 by determining the delivery order of the received messages based on the priority 204.
  • FIG. 12 is a diagram illustrating an example of the distribution schedule table 112.
  • the distribution schedule table 112 includes columns of a distribution order 1121, a message ID 1122, a distribution start date 1123, and a priority 1124 in one entry.
  • One line represents information of one delivery message.
  • the distribution order 1121 of the message “05” is determined in the registration order of the distribution request message 200, and in this example, the message is next to the message having the ID “04”.
  • FIG. 13 is a flowchart illustrating an example of processing performed by the distribution start date / time management unit 130. This process (steps S41 to S46) is repeated at a preset short time period (for example, at intervals of 0.5 seconds).
  • the process ends and waits (S46).
  • the distribution start date and time management unit 130 transmits the message ID 1122 whose distribution order 1121 is “1” to the transmission message editing unit 140 (S44).
  • the period at which the distribution start date and time management unit 130 acquires information in the distribution schedule table 112 needs to be set longer than the time required for the series of steps. However, if the set cycle is too long, the real-time property of the delivery message is lost. Therefore, it is required to set the cycle with a value close to the processing time of one delivery message.
  • FIG. 14 is a flowchart illustrating an example of processing performed by the transmission message editing unit 140. This process is executed after the transmission message editing unit 140 receives the message ID for starting transmission from the distribution start date management unit 130 (S51).
  • the transmission message editing unit 140 acquires information on the message ID SAI 1256, MBMS-GW 1252, MME 1253, MCE 1254, eNB 12555, sensor model name 1257, and distribution content 1258 from the broadcast distribution message table 125 (S52). The transmission message editing unit 140 determines whether or not the SAI 1256 information of the message ID exists in the broadcast delivery message table 125 (S53).
  • the transmission message editing unit 140 When the SAI 1256 information of the message ID exists in the broadcast delivery message table 125, the transmission message editing unit 140 generates a broadcast delivery message (S54) and transmits the broadcast delivery message to the delivery message sending unit 150 (S55). ).
  • the transmission message editing unit 140 acquires the IoT-GW ID 1272 of the message ID, the sensor model name 1273, and the information of the distribution content 1274 from the unicast distribution message table 127.
  • the transmission message editing unit 140 determines whether the information of the IoT-GW ID 1272 of the message ID exists in the unicast delivery message table 127 (S53).
  • the transmission message editing unit 140 When the information of the IoT-GW ID 1272 of the message ID exists in the unicast delivery message table 127, the transmission message editing unit 140 generates a unicast delivery message according to the number of IoT-GW ID 1272 (S58). It transmits to the delivery message transmission part 150 sequentially.
  • the process ends.
  • the transmission message editing unit 140 acquires the information for the message ID from the broadcast distribution message table 125 and the unicast distribution message table 127, at least SAI information or IoT-GW ID information is obtained. Therefore, the process of the delivery method determination unit 122 for the message ID is characterized in that it ends before the process of the transmission message editing unit 140.
  • FIG. 15 is a diagram illustrating an example of information of the broadcast delivery message 300.
  • the broadcast delivery message 300 includes information on the SAI 305, eMBMS delivery information transfer network equipment (MBMS-GW301, MME302, MCE303, eNB304), sensor model name 306, and delivery content 307.
  • MBMS-GW301 eMBMS delivery information transfer network equipment
  • MME302 eMBMS delivery information transfer network equipment
  • MCE303 eMBMS-GW301
  • eNB304 eMBMS delivery information transfer network equipment
  • sensor model name 306 eMBMS-GW301, MME302, MCE303, eNB304
  • FIG. 16 is a diagram showing an example of information of the unicast delivery message 350.
  • the unicast delivery message 350 includes information on the IoT-GW ID 351, the sensor model name 352, and the delivery content 353.
  • FIG. 17 is a flowchart illustrating an example of processing performed by the delivery message transmission unit 150.
  • the delivery message transmission unit 150 receives the delivery message from the transmission message editing unit 140 (S61), the delivery message transmission unit 150 transmits the delivery message to the LTE core network 3 (S62).
  • the delivery message is the broadcast delivery message 300 or the unicast delivery message 350 described above.
  • the distribution message transmission unit 150 may transmit both the broadcast distribution message 300 and the unicast distribution message 350 for one message ID. Further, the distribution message transmission unit 150 transmits only one broadcast distribution message 300 for one message ID, but may transmit a plurality of unicast distribution messages 350 for one message ID.
  • FIG. 18 is a sequence diagram showing an example of update file delivery as processing performed in the IoT system of this embodiment.
  • the IoT hub 1 distributes a control command for software update to a specific model IoT-GW 5 is shown.
  • the IoT-GW 5 performs software update after receiving the update file.
  • the content server 2 transmits a distribution request message 200 including an update file of a specific model IoT-GW 5 to the IoT hub 1 (S71).
  • the IoT hub 1 transmits a response indicating that the distribution request message 200 has been received to the content server 2 (S72).
  • the delivery order control process shown in FIG. 11 is executed (S74), and the delivery schedule table 112 and broadcast delivery are performed.
  • the message table 125 and the unicast delivery message table 127 are updated.
  • the IoT hub 1 transmits a distribution message to the LTE core network 3 (S75).
  • the LTE core network returns a delivery message reception response to the IoT hub 1 (S76), and then broadcasts to each delivery service area 4 to be delivered according to the delivery message information of the IoT hub 1, or an individual IoT-
  • the GW ID is designated and distributed to the IoT-GW 5 by unicast distribution (S77).
  • the IoT-GW 5 transmits the received response to the LTE core network 3 in response to the delivery message received from the base station 6 (eNB) (S78), and updates the software (S79).
  • the IoT-GW 5 transmits the update process end notification to the LTE core network 3 after performing the software update (S80).
  • the LTE core network 3 transmits the received update process end notification to the IoT hub 1 (S81). Thereafter, the IoT hub 1 transmits an update processing end notification from the LTE core network 3 to the content server 2.
  • the update file in FIG. 18 usually has a large capacity. As the total number of IoT-GWs 5 of the model increases, data communication to the IoT-GW 5 becomes enormous. By performing broadcast distribution in the distribution target SAI in which the total number of IoT-GWs 5 of the model is very large, the update file can be distributed only once to the large number of IoT-GWs 5.
  • the IoT hub 1 since the content server 2 can set the priority 204 for the distribution request message 200, the IoT hub 1 responds to the distribution request message with the same distribution start date and time based on the priority 204 of the distribution request message 200. Thus, it is possible to appropriately control the distribution order.
  • the edge device may be a device that controls one or more sensors and transmits data measured by the sensors to the IoT hub 1, and may be configured by a computer or a communication device.
  • the IoT hub 1 may function as a management device that controls the edge device (IoT-GW 5, sensor 7).
  • the IoT-GW model name 201 is used as a transmission condition for specifying the distribution service area 4 is shown.
  • the present invention is not limited to this, and information such as the format and type of the IoT-GW 5 is used. May be used as a transmission condition.
  • broadcast distribution is used as one-to-many communication, but multicast distribution may be used.
  • a table of the distribution destination sensor 7 may be set in the IoT-GW 5, and multicast distribution may be performed based on information in the table.
  • any one of broadcast distribution, unicast distribution, and multicast distribution may be selected by adding multicast distribution conditions to distribution conditions set in advance for each distribution service area 4.
  • this invention is not limited to the above-mentioned Example, Various modifications are included.
  • the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.
  • a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment.
  • any of the additions, deletions, or substitutions of other configurations can be applied to a part of the configuration of each embodiment, either alone or in combination.
  • each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
  • each of the above-described configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function.
  • Information such as programs, tables, and files for realizing each function can be stored in a recording device such as a memory, a hard disk, and an SSD, or a recording medium such as an IC card, an SD card, and a DVD.
  • control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

An edge device control method in which an IoT hub having a processor and memory controls edge devices in one or more service areas connected via a network, comprises: a first step in which the IoT hub receives a delivery request message; a second step in which the IoT hub determines, on the basis of transmission requirements included in the delivery request message, service areas intended for the delivery; and a third step in which the IoT hub selects either a broadcast delivery or a unicast delivery for each of the determined service areas.

Description

エッジデバイスの制御方法、ＩｏＴハブ及び記憶媒体Edge device control method, IoT hub, and storage medium
　本発明は、多数のエッジデバイスを制御するＩｏＴシステムに関する。 The present invention relates to an IoT system that controls a large number of edge devices.
　コンピュータの小型化や、高機能化の技術が進歩し、あらゆる場所や機器にコンピュータが配置され、インターネットへ接続されるようになった。これらは、近年、Ｉｎｔｅｒｎｅｔ　ｏｆ　Ｔｈｉｎｇｓ（ＩｏＴ）と呼ばれ、集積されるデータを活用した、ＩｏＴビジネスが社会的に注目を浴びている。ＩｏＴシステムは、エッジデバイスと、情報転送ネットワークと、ＩｏＴハブと、コンテンツサーバにより構成される。 The technology for miniaturization and high functionality of computers has progressed, and computers have been placed in various places and devices and connected to the Internet. In recent years, these are called Internet of Things (IoT), and IoT business using accumulated data has attracted social attention. The IoT system includes an edge device, an information transfer network, an IoT hub, and a content server.
　エッジデバイスは、ビジネスに活用するためのデータを集める各物理量のセンサおよび、センサを取りまとめて制御するゲートウェイ装置（ＩｏＴ－ＧＷ）である。センサは工場等のデータを収集し、特定のＩｏＴ－ＧＷに集約される。ＩｏＴ－ＧＷは、接続されたセンサからのデータを、情報転送ネットワークを通じてクラウド側のＩｏＴハブに転送し、また、センサの管理も行う。 The edge device is a sensor for each physical quantity that collects data for business use, and a gateway device (IoT-GW) that collectively controls the sensors. The sensor collects data of factories and the like and is collected in a specific IoT-GW. The IoT-GW transfers data from the connected sensor to the cloud-side IoT hub through the information transfer network, and also manages the sensor.
　情報転送ネットワークは、ネットワーク機器を介してエッジデバイスとクラウド間のデータ転送サービスを提供する。 The information transfer network provides a data transfer service between the edge device and the cloud via the network device.
　ＩｏＴハブはエッジデバイス（例えば、ＩｏＴ－ＧＷ）を制御し、ＩｏＴ－ＧＷから収集したデータを必要な形式に加工及び整形する。整形されたデータに基づいて算出されるコンテンツは、コンテンツサーバを介して可視化され、ＩｏＴサービス利用者に提供される。 The IoT hub controls the edge device (for example, IoT-GW), and processes and shapes the data collected from the IoT-GW into a necessary format. The content calculated based on the formatted data is visualized via the content server and provided to the IoT service user.
　ＩｏＴビジネスにおけるビジネス提供者としては、ＩｏＴサービス提供者と、ＩｏＴプラットフォーム提供者と、情報転送ネットワーク提供者が存在する。ＩｏＴサービス提供者は、コンテンツサーバと、ＩｏＴ－ＧＷ及びその配下にあるセンサを所有し、センサからのデータをコンテンツの形でＩｏＴサービス利用者に提供する。 There are IoT service providers, IoT platform providers, and information transfer network providers as business providers in the IoT business. The IoT service provider owns the content server, the IoT-GW, and sensors under the content server, and provides data from the sensor to the IoT service user in the form of content.
　ＩｏＴプラットフォーム提供者はＩｏＴハブを所有し、エッジデバイスの制御や工場のデータを収集して加工および整形のサービスを提供する。情報転送ネットワーク提供者は、工場とクラウド間の情報転送ネットワークを所有し、データ転送サービスを提供する。 IoT platform provider owns IoT hub and collects edge device control and factory data to provide processing and shaping services. The information transfer network provider owns an information transfer network between the factory and the cloud and provides a data transfer service.
特開２００７－１４８８３７号公報JP 2007-148837 A 特開２０１２－１６５１９７号公報JP 2012-165197 A
　ＩｏＴビジネスでは、ＩｏＴサービス提供者が必要なデータを得るためにエッジデバイスを様々な地域に設置する。例えば、同じ地域に複数の機種のＩｏＴ－ＧＷを設置し、同機種のＩｏＴ－ＧＷに複数の機種のセンサを接続する場合がある。 In IoT business, IoT service providers install edge devices in various regions in order to obtain necessary data. For example, there are cases where a plurality of models of IoT-GW are installed in the same area, and a plurality of models of sensors are connected to the same model of IoT-GW.
　ＩｏＴサービス提供者が利用者の要求に応じて、特定地域における特定データ（例えば、地域Ａの放射線量のデータ）を収集するユースケースがある。その際に、ＩｏＴハブはＩｏＴ－ＧＷ経由で全てのセンサからのデータを常時収集するのではなく、無駄なデータ通信を削減する目的で当該ＩｏＴ－ＧＷに対して、当該センサのデータ転送サービス機能を制御することで必要な時のみに地域Ａの放射線量のデータを収集する。 There is a use case where the IoT service provider collects specific data in a specific area (for example, radiation dose data of area A) in response to a user request. At that time, the IoT hub does not always collect data from all the sensors via the IoT-GW, but the data transfer service function of the sensor to the IoT-GW for the purpose of reducing useless data communication. The radiation dose data of area A is collected only when necessary by controlling
　データ転送サービス機能とは、ＩｏＴ－ＧＷが当該センサのデータをＩｏＴハブに転送する機能である。通常は、ＩｏＴサービス提供者がＩｏＴ－ＧＷのＩＤ指定で制御コマンドを当該ＩｏＴ－ＧＷにユニキャストで配信する。但し、各々のＩｏＴ－ＧＷに同じ制御コマンドを個別に配信するとＩｏＴ－ＧＷへの制御時間の差分が多く発生し、情報転送ネットワークにおいて無駄なデータ通信が発生するためＩｏＴサービスのコスト増加が課題であった。 The data transfer service function is a function in which the IoT-GW transfers the sensor data to the IoT hub. Normally, the IoT service provider distributes a control command to the IoT-GW by unicast by specifying the ID of the IoT-GW. However, if the same control command is distributed to each IoT-GW individually, a difference in the control time to the IoT-GW is generated, and wasteful data communication occurs in the information transfer network, which increases the cost of the IoT service. there were.
　また、ＩｏＴサービス提供者が事業を継続する上で、ＩｏＴ－ＧＷのソフトウェアを最新状態に更新するユースケースがある。ＩｏＴサービス提供者は通常ＩｏＴ－ＧＷのＩＤ指定でソフトウェア更新の制御コマンド及び更新ファイルを、個別のＩｏＴ－ＧＷにユニキャストで配信してソフトウェア更新の制御を行う。しかし、同じ制御コマンドや更新ファイルを各々のＩｏＴ－ＧＷに配信すると無駄なデータ通信が発生してＩｏＴサービスのコスト増加が課題であった。 In addition, there is a use case in which the IoT service provider updates the IoT-GW software to the latest state in order to continue the business. The IoT service provider normally performs software update control by distributing a software update control command and an update file to individual IoT-GWs by unicast by specifying an IoT-GW ID. However, if the same control command and update file are distributed to each IoT-GW, useless data communication occurs, and the cost of the IoT service is increased.
　ＩｏＴサービス提供者が特定ＩｏＴ－ＧＷに制御コマンドや更新ファイルを配信する際に、コンテンツサーバからＩｏＴハブに配信要求メッセージを登録する。ＩｏＴハブが登録した配信メッセージにある配信開始日時を元に、制御コマンドを当該ＩｏＴ－ＧＷに配信する。配信開始日時が同じ場合は、通常先に登録された配信要求メッセージが優先的に配信される。ＩｏＴハブが、同じ配信開始日時の配信要求メッセージに対して配信要求メッセージの緊急度に従う配信順序を制御することができないという課題があった。 When the IoT service provider distributes a control command or an update file to a specific IoT-GW, the distribution request message is registered from the content server to the IoT hub. Based on the delivery start date and time in the delivery message registered by the IoT hub, the control command is delivered to the IoT-GW. When the delivery start date and time are the same, the delivery request message registered first is preferentially delivered. There is a problem that the IoT hub cannot control the distribution order according to the urgency level of the distribution request message with respect to the distribution request message having the same distribution start date and time.
　ＩｏＴビジネスにおいてあらゆる場所のデータを収集するエッジデバイスは今後益々増加することが見込まれる。エッジデバイスが様々な地域に設置される中で、同じ地域に複数の機種のＩｏＴ－ＧＷがあり、同機種のＩｏＴ－ＧＷに複数の機種のセンサが接続される場合がある。ＩｏＴサービス提供者がエッジデバイスを制御するにあたってＩｏＴビジネスの運用コストを抑制する効率制御方法が要求される。 In the IoT business, the number of edge devices that collect data at any location is expected to increase further in the future. While edge devices are installed in various regions, there are cases where there are a plurality of types of IoT-GWs in the same region, and a plurality of types of sensors are connected to the same type of IoT-GW. When an IoT service provider controls an edge device, an efficiency control method that suppresses the operation cost of the IoT business is required.
　例えば、上述のように特定地域における特定データ収集のユースケースでは、特定のセンサに対するデータ転送サービス機能の制御コマンドをＩｏＴ－ＧＷに配信する。 For example, in the use case of collecting specific data in a specific area as described above, a control command for a data transfer service function for a specific sensor is distributed to the IoT-GW.
　また、上述のようにＩｏＴ－ＧＷのソフトウェア更新のユースケースでは、ＩｏＴ－ＧＷが複数の地域に設置されて同じ地域に複数の機種のＩｏＴ－ＧＷがある中で、特定機種のＩｏＴ－ＧＷに制御コマンドと更新ファイルを配信する。 In addition, as described above, in the use case of software update of IoT-GW, IoT-GW is installed in a plurality of regions, and there are a plurality of models of IoT-GW in the same region. Deliver control commands and update files.
　個別のＩｏＴ－ＧＷにユニキャスト配信を行う場合は、同じ制御コマンドや更新ファイルが何回も情報転送ネットワーク経由で配信されるため制御時間差分及び無駄なデータ通信が発生する。一方、ブロードキャスト配信を行う場合は、当該機種のＩｏＴ－ＧＷが少なく対象外のＩｏＴ－ＧＷが多い地域では対象外のＩｏＴ－ＧＷにとって無駄な受信処理が発生して性能に影響がある。 When performing unicast delivery to individual IoT-GWs, the same control command and update file are delivered over and over the information transfer network, resulting in control time differences and useless data communication. On the other hand, when broadcast distribution is performed, in a region where the IoT-GW of the model is small and there are many IoT-GWs that are not the target, useless reception processing occurs for the IoT-GW that is not the target, and the performance is affected.
　この場合は配信対象のサービスエリアごとに、当該機種のＩｏＴ－ＧＷには制御コマンドや更新ファイルを効率よく配信しつつ、対象外のＩｏＴ－ＧＷには無駄なデータ配信を避けることが課題となる。そこで、配信対象のサービスエリアごとに、ＩｏＴハブがブロードキャスト配信かユニキャスト配信かを適切に決定できることが要求される。 In this case, for each service area to be distributed, it is an issue to efficiently distribute control commands and update files to the IoT-GW of the model, and to avoid unnecessary data distribution to the IoT-GW that is not the target. . Therefore, it is required that the IoT hub can appropriately determine whether broadcast distribution or unicast distribution is performed for each service area to be distributed.
　上述のように配信開始日時の配信要求メッセージが複数登録された場合は、ＩｏＴハブが緊急度の高い配信メッセージを適切に配信できないという課題があった。そこで、ＩｏＴハブが配信要求メッセージの優先度で配信順序を適切に制御できることが要求される。 As described above, when a plurality of distribution request messages with the distribution start date and time are registered, there is a problem that the IoT hub cannot appropriately distribute a highly urgent distribution message. Therefore, it is required that the IoT hub can appropriately control the distribution order with the priority of the distribution request message.
　特許文献１では、配信対象のサービスエリアを特定し、ＩｏＴハブから制御コマンドや更新ファイルをブロードキャストで配信することによって、ＩｏＴ－ＧＷへの制御時間差分を低減し、配信対象のＩｏＴ－ＧＷへの無駄なデータ通信を削減できる。しかし、全ての配信対象のサービスエリアに制御コマンドや更新ファイル等がブロードキャスト配信されることによって、配信対象外のＩｏＴ－ＧＷには無駄なデータ配信を抑制することができない、という課題があった。 In Patent Document 1, a service area to be distributed is specified, and a control command or an update file is distributed by broadcast from an IoT hub to reduce a control time difference to the IoT-GW, and to a distribution target IoT-GW. Useless data communication can be reduced. However, there is a problem in that useless data distribution cannot be suppressed for IoT-GWs that are not distribution targets by broadcast distribution of control commands, update files, and the like to all distribution target service areas.
　特許文献２では、異なるコンテンツサーバからの配信要求メッセージについては配信開始日時が同じ場合、優先度に従う配信順序を制御できるが、同じコンテンツサーバからの配信要求メッセージについては、全て同じ優先度になるため配信順序の制御ができない、という課題があった。 In Patent Document 2, when the delivery start date and time is the same for delivery request messages from different content servers, the delivery order according to the priority can be controlled, but the delivery request messages from the same content server all have the same priority. There was a problem that the distribution order could not be controlled.
　本発明は、上記問題点に鑑みてなされたもので、配信対象のサービスエリアごとにメッセージを適切に配信することを目的とする。 The present invention has been made in view of the above problems, and an object thereof is to appropriately distribute a message for each service area to be distributed.
　本発明は、プロセッサとメモリを有するＩｏＴハブが、ネットワークを介して接続された１つ以上のサービスエリア内のエッジデバイスを制御するエッジデバイスの制御方法であって、前記ＩｏＴハブが、配信要求メッセージを受信する第１のステップと、前記ＩｏＴハブが、前記配信要求メッセージに含まれる送信条件に基づいて、配信対象のサービスエリアを特定する第２のステップと、前記ＩｏＴハブが、前記特定されたサービスエリア毎にブロードキャスト配信とユニキャスト配信のいずれかを選択する第３のステップと、を含む。 The present invention provides an edge device control method in which an IoT hub having a processor and a memory controls an edge device in one or more service areas connected via a network, wherein the IoT hub transmits a delivery request message. The first step of receiving the second message, the second step in which the IoT hub identifies the service area to be distributed based on the transmission condition included in the distribution request message, and the IoT hub has been identified. And a third step of selecting either broadcast distribution or unicast distribution for each service area.
　本発明では、ＩｏＴハブが配信対象のサービスエリアごとに、エッジデバイス（例えば、ＩｏＴ－ＧＷ機種）等の配信条件に基づいて、配信方法（ブロードキャスト配信かユニキャスト配信か）を適切に決定することによって配信対象のエッジデバイス（ＩｏＴ－ＧＷ）には効率良くメッセージを配信し、配信対象外のエッジデバイス（ＩｏＴ－ＧＷ）には無駄な配信を抑えることが可能となる。本発明におけるエッジデバイスの制御方法はデータ転送サービス機能の制御や更新ファイルの配信だけでなく、エッジデバイスの制御全般にも適用できる。 In the present invention, for each service area to be distributed, the IoT hub appropriately determines a distribution method (broadcast distribution or unicast distribution) based on distribution conditions such as an edge device (for example, IoT-GW model). As a result, it is possible to efficiently distribute messages to the edge device (IoT-GW) that is the distribution target, and to suppress unnecessary distribution to the edge device (IoT-GW) that is not the distribution target. The edge device control method of the present invention can be applied not only to control of data transfer service functions and distribution of update files, but also to general control of edge devices.
本発明の実施例を示し、ネットワークシステムの一例を示すブロック図である。It is a block diagram which shows the Example of this invention and shows an example of a network system. 本発明の実施例を示し、配信要求メッセージの一例を示す図である。It is a figure which shows the Example of this invention and shows an example of a delivery request message. 本発明の実施例を示し、ＩｏＴハブで行われる処理を示す機能ブロック図である。It is a functional block diagram which shows the Example of this invention and shows the process performed by an IoT hub. 本発明の実施例を示し、ＩｏＴハブの構成図の一例を示すブロック図である。It is a block diagram which shows the Example of this invention and shows an example of the block diagram of an IoT hub. 本発明の実施例を示し、配信要求メッセージ受信部で行われる処理の一例を示すフローチャートである。It is a flowchart which shows the Example of this invention and shows an example of the process performed in a delivery request message receiver. 本発明の実施例を示し、配信サービスエリア解析部で行われる処理の一例を示すフローチャートである。It is a flowchart which shows the Example of this invention and shows an example of the process performed in a delivery service area analysis part. 本発明の実施例を示し、エッジデバイス及びＳＡＩの関連テーブルの一例を示す図である。It is a figure which shows the Example of this invention and shows an example of the association table of an edge device and SAI. 本発明の実施例を示し、配信方法決定部で行われる処理の一例を示すフローチャートである。It is a flowchart which shows the Example of this invention and shows an example of the process performed in the delivery method determination part. 本発明の実施例を示し、ブロードキャスト配信メッセージテーブルの一例を示す図である。It is a figure which shows the Example of this invention and shows an example of a broadcast delivery message table. 本発明の実施例を示し、ユニキャスト配信メッセージテーブルの一例を示す図である。It is a figure which shows the Example of this invention and shows an example of a unicast delivery message table. 本発明の実施例を示し、配信順序判定部で行われる処理の一例を示すフローチャートである。It is a flowchart which shows the Example of this invention and shows an example of the process performed in a delivery order determination part. 本発明の実施例を示し、配信スケジュールテーブルの一例を示す図である。It is a figure which shows the Example of this invention and shows an example of a delivery schedule table. 本発明の実施例を示し、配信開始日時管理部で行われる処理の一例を示すフローチャートである。It is a flowchart which shows the Example of this invention and shows an example of the process performed in a delivery start date management part. 本発明の実施例を示し、送信メッセージ編集部で行われる処理の一例を示すフローチャートである。It is a flowchart which shows the Example of this invention and shows an example of the process performed in the transmission message edit part. 本発明の実施例を示し、ブロードキャスト配信メッセージの一例を示す図である。It is a figure which shows the Example of this invention and shows an example of a broadcast delivery message. 本発明の実施例を示し、ユニキャスト配信メッセージの一例を示す図である。It is a figure which shows the Example of this invention and shows an example of a unicast delivery message. 本発明の実施例を示し、配信メッセージ送信部で行われる処理の一例を示すフローチャートある。It is a flowchart which shows the Example of this invention and shows an example of the process performed in a delivery message transmission part. 本発明の実施例を示し、更新ファイル配信で行われる処理のシーケンス図である。FIG. 9 is a sequence diagram of processing performed in update file distribution according to the embodiment of this invention.
　以下、本発明の一実施形態について添付図面を用いて説明する。 Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.
　本実施例におけるＩｏＴシステムの構成の一例を図１のブロック図に示す。本実施例では、情報転送ネットワークを第３．９世代携帯電話の通信規格であるＬｏｎｇ　Ｔｅｒｍ　Ｅｖｏｌｕｔｉｏｎ（以下、ＬＴＥ）のコアネットワークで構成し、ブロードキャスト配信をＬＴＥのブロードキャスト配信技術ｅｖｏｌｖｅｄ　Ｍｕｌｔｉｍｅｄｉａ　Ｂｒｏａｄｃａｓｔ　Ｍｕｌｔｉｃａｓｔ　Ｓｅｒｖｉｃｅ（以下、ｅＭＢＭＳ）とする。ｅＭＢＭＳは、複数の配信サービスエリアに対して、同じ周波数でブロードキャスト配信ができることにより移動体通信ネットワークにおける無線リソースの使用率が高いという特徴がある。 An example of the configuration of the IoT system in this embodiment is shown in the block diagram of FIG. In this embodiment, the information transfer network is configured with a core network of Long Term Evolution (hereinafter LTE), which is a communication standard for the 3.9th generation mobile phone, and broadcast distribution is performed by LTE broadcast distribution technology evolved Multimedia Broadcast Service ( Hereinafter referred to as eMBMS). eMBMS is characterized in that a radio resource usage rate in a mobile communication network is high because broadcast distribution can be performed at the same frequency to a plurality of distribution service areas.
　本実施例に関わるＩｏＴシステムは、コンテンツサーバ２と、ＩｏＴハブ（ＩｏＴハブ）１と、ＬＴＥコアネットワーク３と、基地局６であるｅｖｏｌｖｅｄ　Ｎｏｄｅ　Ｂ（ｅＮＢ１、ｅＮＢ２）と、ＩｏＴ－ＧＷ５と、センサ７により構成されている。本実施例では、基地局（ｅＮＢ）６の配下を配信サービスエリア４－Ａ、４－Ｂとする。なお、とある配信サービスエリア全体を示すときには「－」以降を省略した符号「４」を用いる。 The IoT system according to the present embodiment includes a content server 2, an IoT hub (IoT hub) 1, an LTE core network 3, an evolved Node B (eNB 1, eNB 2) that is a base station 6, an IoT-GW 5, a sensor 7. In this embodiment, the subordinates of the base station (eNB) 6 are distribution service areas 4-A and 4-B. In order to indicate an entire distribution service area, the symbol “4” in which “−” and the subsequent symbols are omitted is used.
　ＩｏＴサービス提供者が特定機種のＩｏＴ－ＧＷ５を制御する必要があると判断した場合、コンテンツサーバ２からＩｏＴハブ１へ配信要求メッセージ２００を送信する。ＩｏＴハブ１は、配信要求メッセージ２００を受信すると、配信サービスエリア４内のＩｏＴ－ＧＷ５（エッジデバイス）の状態に応じて、ブロードキャスト配信メッセージ３００またはユニキャスト配信メッセージ３５０を生成して配信する。 When the IoT service provider determines that it is necessary to control the IoT-GW 5 of the specific model, the distribution request message 200 is transmitted from the content server 2 to the IoT hub 1. When receiving the distribution request message 200, the IoT hub 1 generates and distributes the broadcast distribution message 300 or the unicast distribution message 350 according to the state of the IoT-GW 5 (edge device) in the distribution service area 4.
　図２は、配信要求メッセージ２００の情報の一例を示す図である。配信要求メッセージ２００は、ＩｏＴ－ＧＷ機種名２０１と、センサ機種名２０２と、配信開始日時２０３と、優先度２０４と、配信内容２０５の情報を有する。 FIG. 2 is a diagram showing an example of information of the distribution request message 200. The distribution request message 200 includes information on an IoT-GW model name 201, a sensor model name 202, a distribution start date and time 203, a priority 204, and a distribution content 205.
　ＩｏＴ－ＧＷ機種名２０１は、配信対象の配信サービスエリア４を特定する送信条件として使用される情報である。センサ機種名２０２は、温度や臭い等の特定のデータを収集するための情報であり、制御の内容によって指定しない場合もある。ＩｏＴ－ＧＷ機種名２０１もセンサ機種名２０２も一つ以上指定可能である。 The IoT-GW model name 201 is information used as a transmission condition for specifying the distribution service area 4 to be distributed. The sensor model name 202 is information for collecting specific data such as temperature and odor, and may not be specified depending on the content of control. One or more IoT-GW model name 201 and sensor model name 202 can be specified.
　配信開始日時２０３及び優先度２０４は配信順序の制御に使用される情報である。配信内容２０５は、ＩｏＴ－ＧＷ５で実行される制御コマンドや更新ファイルなどを指す。 The distribution start date and time 203 and the priority level 204 are information used for controlling the distribution order. The distribution content 205 indicates a control command executed by the IoT-GW 5, an update file, or the like.
　図３は、本実施例のＩｏＴハブ１の機能を示すブロック図である。ＩｏＴハブ１は、配信要求メッセージ受信部１００と、配信方法処理部１２０と、配信順序制御部１１０と、配信開始日時管理部１３０と、送信メッセージ編集部１４０と、配信メッセージ送信部１５０から構成される。 FIG. 3 is a block diagram showing functions of the IoT hub 1 of the present embodiment. The IoT hub 1 includes a distribution request message receiving unit 100, a distribution method processing unit 120, a distribution order control unit 110, a distribution start date and time management unit 130, a transmission message editing unit 140, and a distribution message transmission unit 150. The
　配信方法処理部１２０は、配信サービスエリア解析部１２１と、配信方法決定部１２２と、エッジデバイス及びＳＡＩの関連テーブル１２３と、ブロードキャスト配信メッセージテーブル１２５と、ユニキャスト配信メッセージテーブル１２７から構成される。配信順序制御部１１０は、配信順序判定部１１１と、配信スケジュールテーブル１１２から構成される。 The delivery method processing unit 120 includes a delivery service area analysis unit 121, a delivery method determination unit 122, an edge device and SAI association table 123, a broadcast delivery message table 125, and a unicast delivery message table 127. The distribution order control unit 110 includes a distribution order determination unit 111 and a distribution schedule table 112.
　なお、ＩｏＴハブ１は、図示はしないが、前記従来例でも述べたように、エッジデバイス（ＩｏＴ－ＧＷ５）からセンサ７のデータを収集し、当該データを所定の形式に加工または整形してコンテンツサーバ２へ出力する機能を含む。当該機能については前記従来例と同様であるので図示及び説明は省略する。 Although not shown, the IoT hub 1 collects the data of the sensor 7 from the edge device (IoT-GW 5), and processes or shapes the data into a predetermined format, as described in the conventional example. A function to output to the server 2 is included. Since this function is the same as that of the conventional example, illustration and description are omitted.
　図４はＩｏＴハブ１の構成を示すブロック図である。ＩｏＴハブ１はＣｅｎｔｒａｌ　Ｐｒｏｃｅｓｓｉｎｇ　Ｕｎｉｔ（ＣＰＵ）１１とメモリ１２と通信用ポート１３を含み、それらが相互に接続される。 FIG. 4 is a block diagram showing the configuration of the IoT hub 1. The IoT hub 1 includes a central processing unit (CPU) 11, a memory 12, and a communication port 13, which are connected to each other.
　メモリ１２は、配信要求メッセージ受信部１００と、配信サービスエリア解析部１２１と、配信方法決定部１２２と、配信順序判定部１１１と、配信開始日時管理部１３０と、送信メッセージ編集部１４０と、配信メッセージ送信部１５０とを実現するプログラム群と、エッジデバイス及びＳＡＩの関連テーブル１０３と、ブロードキャスト配信メッセージテーブル１２５と、ユニキャスト配信メッセージテーブル１２７と、配信スケジュールテーブル１１２とを格納する。 The memory 12 includes a distribution request message reception unit 100, a distribution service area analysis unit 121, a distribution method determination unit 122, a distribution order determination unit 111, a distribution start date management unit 130, a transmission message editing unit 140, a distribution A program group for realizing the message transmission unit 150, an edge device and SAI association table 103, a broadcast distribution message table 125, a unicast distribution message table 127, and a distribution schedule table 112 are stored.
　ＣＰＵ１１が、メモリ１２に格納された、上記の各プログラムをロードして実行することによってＩｏＴハブ１における配信方法処理と配信順序の制御を実現する。通信用ポート１３は、ＬＴＥコアネットワーク３に接続されている他の装置との通信を行う。 The CPU 11 loads and executes each of the above programs stored in the memory 12, thereby realizing distribution method processing and distribution order control in the IoT hub 1. The communication port 13 communicates with other devices connected to the LTE core network 3.
　ＩｏＴハブ１は、一つのコンテンツサーバ２のみでなく複数のコンテンツサーバ２から配信要求メッセージ２００を受信できる。異なるコンテンツサーバ２からでも配信要求メッセージ２００の構造が同じであればＩｏＴハブ１における処理は同じである。 The IoT hub 1 can receive the distribution request message 200 not only from one content server 2 but also from a plurality of content servers 2. If the structure of the distribution request message 200 is the same from different content servers 2, the processing in the IoT hub 1 is the same.
　なお、ＣＰＵ１１は、各機能部のプログラムに従って処理することによって、所定の機能を提供する機能部として稼働する。例えば、ＣＰＵ１１は、配信方法決定プログラムに従って処理することで配信方法決定部１２２として機能する。他のプログラムについても同様である。さらに、ＣＰＵ１１は、各プログラムが実行する複数の処理のそれぞれの機能を提供する機能部としても稼働する。計算機及び計算機システムは、これらの機能部を含む装置及びシステムである。 Note that the CPU 11 operates as a functional unit that provides a predetermined function by processing according to the program of each functional unit. For example, the CPU 11 functions as the distribution method determination unit 122 by performing processing according to the distribution method determination program. The same applies to other programs. Furthermore, the CPU 11 also operates as a function unit that provides each function of a plurality of processes executed by each program. A computer and a computer system are an apparatus and a system including these functional units.
　ＩｏＴハブ１の各機能を実現するプログラム、テーブル等の情報は、ストレージサブシステムや不揮発性半導体メモリ、ハードディスクドライブ、Ｓｏｌｉｄ　Ｓｔａｔｅ　Ｄｒｉｖｅ（以下、ＳＳＤ）等の記憶デバイス、または、ＩＣカード、ＳＤカード、ＤＶＤ等の計算機読み取り可能な非一時的データ記憶媒体に格納することができる。 Information such as programs and tables for realizing each function of the IoT hub 1 is a storage subsystem, a nonvolatile semiconductor memory, a hard disk drive, a storage device such as Solid State Drive (hereinafter, SSD), an IC card, an SD card, It can be stored in a computer-readable non-transitory data storage medium such as a DVD.
　コンテンツサーバ２から送信された配信要求メッセージ２００は、配信要求メッセージ受信部１００によって受信される。図５は配信要求メッセージ受信部１００で行われる処理の一例を示すフローチャートである。 The distribution request message 200 transmitted from the content server 2 is received by the distribution request message receiving unit 100. FIG. 5 is a flowchart illustrating an example of processing performed by the distribution request message receiving unit 100.
　配信要求メッセージ受信部１００は、まず、受信した配信要求メッセージ２００に対して当該メッセージを一意に特定可能なメッセージＩＤを付与する（Ｓ１）。配信要求メッセージ受信部１００は、メッセージＩＤ及びＩｏＴ－ＧＷ機種名２０１の情報を配信サービスエリア解析部１２１へ送信する（Ｓ２）。 The distribution request message receiving unit 100 first assigns a message ID that can uniquely identify the message to the received distribution request message 200 (S1). The distribution request message receiving unit 100 transmits the message ID and the information of the IoT-GW model name 201 to the distribution service area analyzing unit 121 (S2).
　配信要求メッセージ受信部１００は、メッセージＩＤと、優先度２０４及び配信開始日時２０３を配信順序判定部１１１へ送信する（Ｓ３）。配信要求メッセージ受信部１００は、メッセージＩＤと、センサ機種名２０２及び配信内容２０５の情報をブロードキャスト配信メッセージテーブル１２５へ格納する（Ｓ４）。また、配信要求メッセージ受信部１００は、メッセージＩＤと、センサ機種名２０２及び配信内容２０５の情報をユニキャスト配信メッセージテーブル１２７へ格納する（Ｓ５）。上記ステップＳ２～Ｓ５の処理は、配信要求メッセージ受信部１００が並列的に実行することができる。 The distribution request message receiving unit 100 transmits the message ID, the priority 204, and the distribution start date / time 203 to the distribution order determining unit 111 (S3). The distribution request message receiving unit 100 stores the message ID, the sensor model name 202, and the distribution content 205 information in the broadcast distribution message table 125 (S4). Further, the distribution request message receiving unit 100 stores the message ID, the sensor model name 202, and the distribution content 205 information in the unicast distribution message table 127 (S5). The processing of steps S2 to S5 can be executed in parallel by the distribution request message receiving unit 100.
　配信要求メッセージ受信部１００は、上記並行処理の実施及び、次の機能部に必要な情報を送信することによって全体の処理効率の向上が可能である。本実施例では、配信要求メッセージ受信部１００が、図２の配信要求メッセージ２００に付与したメッセージＩＤを「０５」（図９、図１０、図１２参照）とする。 The distribution request message receiving unit 100 can improve the overall processing efficiency by performing the above parallel processing and transmitting necessary information to the next functional unit. In the present embodiment, the distribution request message receiving unit 100 sets the message ID assigned to the distribution request message 200 in FIG. 2 to “05” (see FIGS. 9, 10, and 12).
　図６は、配信サービスエリア解析部１２１で行われる処理の一例を示すフローチャートである。配信サービスエリア解析部１２１は、配信要求メッセージ２００からメッセージＩＤ及びＩｏＴ－ＧＷ機種名３０１の情報を受信する（Ｓ１１）。 FIG. 6 is a flowchart illustrating an example of processing performed by the distribution service area analysis unit 121. The distribution service area analysis unit 121 receives the message ID and the information of the IoT-GW model name 301 from the distribution request message 200 (S11).
　配信サービスエリア解析部１２１は、受信したＩｏＴ－ＧＷ機種名３０１を元に、エッジデバイス及びＳＡＩの関連テーブル１２３を参照してＩｏＴ－ＧＷ機種名３０１に対応するサービスエリアＩＤ（Ｓｅｒｖｉｃｅ　Ａｒｅａ　Ｉｄｅｎｔｉｆｉｅｒ：以下ＳＡＩ）を取得する（Ｓ１２）。次に、配信サービスエリア解析部１２１は、取得したＳＡＩと、ＩｏＴ－ＧＷ機種名３０１及び当該メッセージＩＤを配信方法決定部１２２に送信する（Ｓ１３）。 The distribution service area analysis unit 121 refers to the edge device and SAI association table 123 based on the received IoT-GW model name 301, and identifies the service area ID (Service Area Identifier: below) corresponding to the IoT-GW model name 301 SAI) is acquired (S12). Next, the distribution service area analysis unit 121 transmits the acquired SAI, the IoT-GW model name 301, and the message ID to the distribution method determination unit 122 (S13).
　上記処理によって、配信サービスエリア解析部１２１は、予め設定されたエッジデバイス及びＳＡＩの関連テーブル１２３からＳＡＩを取得して配信方法決定部１２２へ通知することができる。 Through the above processing, the distribution service area analysis unit 121 can acquire the SAI from the preset edge device and SAI association table 123 and notify the distribution method determination unit 122 of the SAI.
　図７は、エッジデバイス及びＳＡＩの関連テーブル１２３の一例を示す。エッジデバイス及びＳＡＩの関連テーブル１２３は、番号１２３１と、ＭＢＭＳ－ＧＷ１２３２と、ＭＭＥ１２３３と、ＭＣＥ１２３４と、ｅＮＢ１２３５と、ＳＡＩ１２３６と、ＩｏＴ－ＧＷ機種名１２３７と、ＩｏＴ－ＧＷ　ＩＤ１２３８と、センサ機種名１２３９と、ＩｏＴ－ＧＷ合計台数１２４０と、配信方法決定基準値１２４１を一つのエントリに含む。 FIG. 7 shows an example of an edge device and SAI association table 123. The edge device and SAI association table 123 includes number 1231, MBMS-GW1232, MME1233, MCE1234, eNB1235, SAI1236, IoT-GW model name 1237, IoT-GW ID1238, sensor model name 1239, and so on. , The total number of IoT-GWs 1240 and the distribution method determination reference value 1241 are included in one entry.
　ブロードキャスト配信をＬＴＥのブロードキャスト配信技術ｅＭＢＭＳとした場合は、図７に示した通りブロードキャスト配信用ネットワーク機器としてＭｕｌｔｉｍｅｄｉａ　Ｂｒｏａｄｃａｓｔ　Ｍｕｌｔｉｃａｓｔ　Ｓｅｒｖｉｃｅ　Ｇａｔｅｗａｙ　（ＭＢＭＳ－ＧＷ）１２３２と、Ｍｏｂｉｌｉｔｙ　Ｍａｎａｇｅｍｅｎｔ　Ｅｎｔｉｔｙ　（ＭＭＥ）１２３３と、Ｍｕｌｔｉｃｅｌｌ　Ｃｏｏｒｄｉｎａｔｉｏｎ　Ｅｎｔｉｔｙ　（ＭＣＥ）１２３４と、ｅＮＢ１２３５が必要となる。図２に示す配信要求メッセージ２００の場合は、ＩｏＴ－ＧＷ機種名１２３７＝「Ｎ０１」より「Ａ」と「Ｂ」のＳＡＩ１２３６が特定される。 When the broadcast distribution is LTE broadcast distribution technology eMBMS, as shown in FIG. 7, as a network device for broadcast distribution, Multimedia Broadcast Multicast Service Gateway (MBMS-GW) 1232, Mobility Management Entity (MME) 1233 Entity (MCE) 1234 and eNB 1235 are required. In the case of the distribution request message 200 shown in FIG. 2, the SAI 1236 of “A” and “B” is specified from the IoT-GW model name 1237 = “N01”.
　エッジデバイス及びＳＡＩの関連テーブル１２３の情報は、ＩｏＴプラットフォーム提供者によって設定及び変更ができる。本実施例では、無駄なデータ通信を抑制してエッジデバイスを効率的に制御する目的で配信方法決定基準値１２４１をＩｏＴ－ＧＷ５の合計台数に設定する例を示す。しかし、これに限定されるものではなく、異なる情報（例えば、センサ７の合計台数等）を設定すること及び、当該情報の配信方法決定基準値１２４１をＳＡＩ１２３６ごとに異なる値で設定することが可能である。また、ＭＢＭＳ－ＧＷ１２３２、ＭＭＥ１２３３、ＭＣＥ１２３４、ｅＮＢ１２３５の欄は、ｅＭＢＭＳを利用するのに必要なネットワーク機器であるが、移動体通信ネットワークの各国際標準団体で策定された別のブロードキャストまたはマルチキャスト配信技術を利用する場合は、上述の欄の代わりに、当該のコアネットワーク機器の欄が設定される。 The information of the edge device and SAI association table 123 can be set and changed by the IoT platform provider. In this embodiment, an example is shown in which the distribution method determination reference value 1241 is set to the total number of IoT-GWs 5 for the purpose of efficiently controlling edge devices by suppressing useless data communication. However, the present invention is not limited to this, and different information (for example, the total number of sensors 7 and the like) can be set, and the distribution method determination reference value 1241 for the information can be set with a different value for each SAI 1236. It is. The MBMS-GW 1232, MME 1233, MCE 1234, and eNB 1235 columns are network devices necessary for using eMBMS. However, other broadcast or multicast distribution technologies established by each international standard organization of the mobile communication network are described. When using, the field of the core network device is set instead of the above-mentioned field.
　図８は配信方法決定部１２２で行われる処理の一例を示すフローチャートである。配信方法決定部１２２は、配信サービスエリア解析部１２１よりメッセージＩＤと、ＩｏＴ－ＧＷ機種名１２３７及びＳＡＩ１２３６の情報を受信する（Ｓ２１）。配信方法決定部１２２は、ステップＳ２２～Ｓ２９のループをＳＡＩ１２３６毎に繰り返す。 FIG. 8 is a flowchart illustrating an example of processing performed by the distribution method determination unit 122. The distribution method determination unit 122 receives the message ID, the information on the IoT-GW model name 1237 and the SAI 1236 from the distribution service area analysis unit 121 (S21). The distribution method determining unit 122 repeats the loop of steps S22 to S29 for each SAI 1236.
　配信方法決定部１２２は、ＳＡＩ１２３６ごとに当該ＩｏＴ－ＧＷ合計台数１２４０及び配信方法決定基準値をエッジデバイス及びＳＡＩの関連テーブル１２３から取得する（Ｓ２３）。次に、配信方法決定部１２２は、ＩｏＴ－ＧＷ合計台数１２４０が配信方法決定基準値１２４１より大きいか否かを判定する（Ｓ２４）。 The delivery method determination unit 122 acquires the IoT-GW total number 1240 and the delivery method determination reference value for each SAI 1236 from the edge device and SAI association table 123 (S23). Next, the distribution method determination unit 122 determines whether or not the total number of IoT-GWs 1240 is larger than the distribution method determination reference value 1241 (S24).
　ＩｏＴ－ＧＷ合計台数１２４０が配信方法決定基準値１２４１より大きい場合はステップＳ２５へ進み、そうでない場合にはステップＳ２７へ進む。ステップＳ２５では、配信方法決定部１２２が当該ＳＡＩに対応するＭＢＭＳ－ＧＷ１２３２と、ＭＭＥ１２３３と、ＭＣＥ１２３４と、ｅＮＢ１２３５の情報をエッジデバイス及びＳＡＩの関連テーブル１２３より取得する。 If the total number of IoT-GWs 1240 is larger than the distribution method determination reference value 1241, the process proceeds to step S25, and if not, the process proceeds to step S27. In step S25, the distribution method determination unit 122 acquires the MBMS-GW 1232, MME 1233, MCE 1234, and eNB 1235 information corresponding to the SAI from the edge device and SAI association table 123.
　そして、配信方法決定部１２２は、当該ＳＡＩ１２３６と、ＭＢＭＳ－ＧＷ１２３２と、ＭＭＥ１２３３と、ＭＣＥ１２３４と、ｅＮＢ１２３５の情報をブロードキャスト配信メッセージテーブル１２５のうち、メッセージＩＤ１２５１が一致するエントリに格納する。 Then, the delivery method determination unit 122 stores the information of the SAI 1236, the MBMS-GW 1232, the MME 1233, the MCE 1234, and the eNB 1235 in the entry with the matching message ID 1251 in the broadcast delivery message table 125.
　一方、ＩｏＴ－ＧＷ合計台数１２４０が配信方法決定基準値１２４１以下の場合は、ステップＳ２７で、配信方法決定部１２２が当該ＳＡＩ１２３６に対応するＩｏＴ－ＧＷ　ＩＤ１２３８の情報をエッジデバイス及びＳＡＩの関連テーブル１２３より取得する。そして、配信方法決定部１２２はＩｏＴ－ＧＷのＩＤ１２３８の情報をユニキャスト配信メッセージテーブル１２７のうち、メッセージＩＤ１２７１が一致するエントリに格納する（Ｓ２８）。 On the other hand, if the total number of IoT-GWs 1240 is equal to or less than the distribution method determination reference value 1241, the distribution method determination unit 122 obtains information on the IoT-GW ID 1238 corresponding to the SAI 1236 in step S27 and the edge device and SAI association table 123. Get more. Then, the delivery method determining unit 122 stores the information of the ID 1238 of the IoT-GW in the entry with the matching message ID 1271 in the unicast delivery message table 127 (S28).
　配信方法決定部１２２の処理において、ＳＡＩごとに、ブロードキャスト配信かユニキャスト配信かを判定することが特徴である。これによって、ＳＡＩごとに無駄なデータ通信を抑制してエッジデバイスを効率的に制御することが可能となる。 In the process of the delivery method determination unit 122, it is characterized that it is determined for each SAI whether broadcast delivery or unicast delivery. Accordingly, it is possible to efficiently control the edge device by suppressing useless data communication for each SAI.
　図９は、ブロードキャスト配信メッセージテーブル１２５の一例を示す図である。ブロードキャスト配信メッセージテーブル１２５は、メッセージＩＤ１２５１と、ＭＢＭＳ－ＧＷ１２５２と、ＭＭＥ１２５３と、ＭＣＥ１２５４と、ｅＮＢ１２５５と、ＳＡＩ１２５６と、センサ機種名１２５７と、配信内容１２５８を一つのエントリに含む。ＭＢＭＳ－ＧＷ１２５２～ＳＡＩ１２５６は、図７に示したエッジデバイス及びＳＡＩの関連テーブル１２３と同様の構成である。 FIG. 9 is a diagram illustrating an example of the broadcast delivery message table 125. The broadcast delivery message table 125 includes message ID 1251, MBMS-GW 1252, MME 1253, MCE 1254, eNB 1255, SAI 1256, sensor model name 1257, and delivery content 1258 in one entry. MBMS-GWs 1252 to SAI 1256 have the same configuration as the edge device and SAI association table 123 shown in FIG.
　図１０は、ユニキャスト配信メッセージテーブル１２７の一例を示す図である。ユニキャスト配信メッセージテーブル１２７は、メッセージＩＤ１２７１と、ＩｏＴ－ＧＷ　ＩＤ１２７２と、センサ機種名１２７３と、配信内容１２７４を一つのエントリに含む。配信方法決定部１２２は、ＳＡＩごとに配信方法を決定するため、一つのメッセージＩＤ１２７１に対してブロードキャスト配信メッセージテーブル１２５は複数のＳＡＩを、ユニキャスト配信メッセージテーブル１２７は、複数のＩｏＴ－ＧＷ５のＩＤを有する場合がある。 FIG. 10 is a diagram showing an example of the unicast delivery message table 127. The unicast delivery message table 127 includes message ID 1271, IoT-GW ID 1272, sensor model name 1273, and delivery content 1274 in one entry. Since the delivery method determination unit 122 determines a delivery method for each SAI, the broadcast delivery message table 125 has a plurality of SAIs for one message ID 1271, and the unicast delivery message table 127 has a plurality of IoT-GW5 IDs. May have.
　図１１は配信順序判定部１１１で行われる処理のフローチャートを示す。配信順序判定部１１１は、新規の配信メッセージを配信スケジュールテーブル１１２へ登録する際に、配信開始日時と、優先度と、登録順の情報を元に、配信順番を決定する。この処理は、配信要求メッセージ受信部１００が配信要求メッセージ２００を受け付けた後に実行される。 FIG. 11 shows a flowchart of processing performed in the distribution order determination unit 111. When registering a new distribution message in the distribution schedule table 112, the distribution order determination unit 111 determines the distribution order based on information on the distribution start date and time, priority, and registration order. This process is executed after the distribution request message receiving unit 100 receives the distribution request message 200.
　配信順序判定部１１１は、配信要求メッセージ受信部１００からメッセージＩＤと、優先度２０４と、配信開始日時２０３を受信する（Ｓ３１）。次に、配信順序判定部１１１は、配信要求メッセージ２００より受信した配信開始日時２０３を基準に、配信スケジュールテーブル１１２に格納されているメッセージに同一の配信開始日時を有するメッセージがあるか否かを判定する（Ｓ３２）。配信開始日時が同一のメッセージが存在する場合にはステップＳ３３へ進み、そうでない場合にはステップＳ３７へ進む。 The delivery order determination unit 111 receives the message ID, the priority 204, and the delivery start date and time 203 from the delivery request message receiving unit 100 (S31). Next, the delivery order determination unit 111 determines whether there is a message having the same delivery start date / time in the messages stored in the delivery schedule table 112 based on the delivery start date / time 203 received from the delivery request message 200. Determine (S32). If there is a message with the same delivery start date and time, the process proceeds to step S33, and if not, the process proceeds to step S37.
　同一の配信開始日時のメッセージがない場合は、配信順序判定部１１１が配信開始日時の順序で新規のメッセージの配信順番を決定する（Ｓ３７）。その後、ステップＳ３６の処理へ進む。 If there is no message with the same delivery start date and time, the delivery order determination unit 111 determines the delivery order of new messages in the order of delivery start date and time (S37). Thereafter, the process proceeds to step S36.
　一方、配信スケジュールテーブル１１２に同一の配信開始日時のメッセージが格納されている場合は、配信順序判定部１１１が当該メッセージ及び優先度２０４を特定する（Ｓ３３）。 On the other hand, when messages with the same delivery start date and time are stored in the delivery schedule table 112, the delivery order determination unit 111 identifies the message and the priority 204 (S33).
　次に、配信順序判定部１１１は、新規メッセージの優先度２０４を基準にして、特定したメッセージ群のなかで同一の優先度のメッセージがあるか否かを判定する（Ｓ３４）。特定したメッセージ群内で同一の優先度のメッセージがない場合は、ステップＳ３８へ進んで、配信順序判定部１１１は、特定したメッセージ群内で優先度の順序で新規メッセージの配信順番を決定する。 Next, the delivery order determination unit 111 determines whether there is a message having the same priority in the specified message group based on the priority 204 of the new message (S34). If there is no message with the same priority in the identified message group, the process proceeds to step S38, and the delivery order determination unit 111 determines the delivery order of new messages in the order of priority within the identified message group.
　一方、特定したメッセージ群内で同一の優先度のメッセージがある場合は、配信順序判定部１１１が、同一の配信開始日時でかつ同一の優先度のメッセージの中で新規メッセージを最後の配信順番に決定する（Ｓ３５）。最後に、配信順序判定部１１１は、配信スケジュールテーブル１１２におけるメッセージの配信順番を更新する（Ｓ３６）。 On the other hand, if there is a message with the same priority in the specified message group, the delivery order determination unit 111 puts the new message in the last delivery order among the messages with the same delivery start date and time and the same priority. Determine (S35). Finally, the delivery order determination unit 111 updates the delivery order of messages in the delivery schedule table 112 (S36).
　上記処理によって配信順序判定部１１１は、配信開始日時が同一の場合には、優先度２０４に基づいて受け付けたメッセージの配信の順序を決定して、配信スケジュールテーブル１１２を更新する。 If the delivery start date and time are the same, the delivery order determination unit 111 updates the delivery schedule table 112 by determining the delivery order of the received messages based on the priority 204.
　図１２は、配信スケジュールテーブル１１２の一例を示す図である。配信スケジュールテーブル１１２は、配信順番１１２１と、メッセージＩＤ１１２２と、配信開始日時１１２３と、優先度１１２４の欄を一つのエントリに含む。 FIG. 12 is a diagram illustrating an example of the distribution schedule table 112. The distribution schedule table 112 includes columns of a distribution order 1121, a message ID 1122, a distribution start date 1123, and a priority 1124 in one entry.
　一つの行（エントリ）は、一つの配信メッセージの情報を表す。図２の配信要求メッセージ２００は、「０５」のメッセージＩＤを有し、図１２に示すメッセージＩＤが「０４」のメッセージＩＤに比べて同一の配信開始日時１１２３でかつ同一の優先度１１２４＝「中」である。この場合は、配信要求メッセージ２００の登録順で「０５」のメッセージの配信順番１１２１が決定され、この例ではＩＤが「０４」のメッセージの次になる。 One line (entry) represents information of one delivery message. The distribution request message 200 in FIG. 2 has a message ID “05”, and has the same distribution start date 1123 and the same priority 1124 = “comparison” with the message ID “04” shown in FIG. Medium. In this case, the distribution order 1121 of the message “05” is determined in the registration order of the distribution request message 200, and in this example, the message is next to the message having the ID “04”.
　図１３は配信開始日時管理部１３０で行われる処理の一例を示すフローチャートである。この処理（ステップＳ４１～Ｓ４６）は、予め設定した短い時間の周期（例えば、０．５秒間隔等）で繰り返される。 FIG. 13 is a flowchart illustrating an example of processing performed by the distribution start date / time management unit 130. This process (steps S41 to S46) is repeated at a preset short time period (for example, at intervals of 0.5 seconds).
　配信開始日時管理部１３０は、配信順番１１２１が「１」のメッセージＩＤ１１２２及び配信開始日時１１２３を配信スケジュールテーブル１１２から取得する（Ｓ４２）。配信開始日時管理部１３０は、現在時刻が配信順番１１２１＝「１」の配信開始日時１１２３となったか否かを判定する（Ｓ４３）。 The distribution start date and time management unit 130 acquires the message ID 1122 and the distribution start date and time 1123 whose distribution order 1121 is “1” from the distribution schedule table 112 (S42). The distribution start date and time management unit 130 determines whether or not the current time is the distribution start date and time 1123 of the distribution order 1121 = “1” (S43).
　現在時刻が取得した配信開始日時１１２３になっていない場合は、処理を終了して待機する（Ｓ４６）。一方、現在時刻が取得した配信開始日時１１２３になった場合、配信開始日時管理部１３０は、配信順番１１２１が「１」のメッセージＩＤ１１２２を送信メッセージ編集部１４０に送信する（Ｓ４４）。 If the distribution start date and time 1123 obtained is not the current time, the process ends and waits (S46). On the other hand, when the current time is the acquired distribution start date and time 1123, the distribution start date and time management unit 130 transmits the message ID 1122 whose distribution order 1121 is “1” to the transmission message editing unit 140 (S44).
　その後、配信開始日時管理部１３０は、送信したメッセージの情報（配信順番１１２１＝「１」の情報）を配信スケジュールテーブル１１２から削除して、配信スケジュールテーブル１１２を更新する（Ｓ４５）。次に、配信開始日時管理部１３０は、また最初のステップＳ４１に戻り、所定時間が経過してから配信順番１１２１＝「１」のメッセージを取得してから前記の各ステップを実施する。 Thereafter, the distribution start date / time management unit 130 deletes the information of the transmitted message (information of the distribution order 1121 = “1”) from the distribution schedule table 112 and updates the distribution schedule table 112 (S45). Next, the distribution start date / time management unit 130 returns to the first step S41, and after the predetermined time has elapsed, acquires the message of the distribution order 1121 = “1”, and then executes each step described above.
　配信開始日時管理部１３０が配信スケジュールテーブル１１２の情報を取得する周期は、前記の一連のステップが要する時間より長く設定する必要がある。しかし、設定した周期が長すぎると配信メッセージのリアルタイム性を失うため、一つの配信メッセージの処理時間に近い値で前記の周期を設定することが要求される。 The period at which the distribution start date and time management unit 130 acquires information in the distribution schedule table 112 needs to be set longer than the time required for the series of steps. However, if the set cycle is too long, the real-time property of the delivery message is lost. Therefore, it is required to set the cycle with a value close to the processing time of one delivery message.
　図１４は送信メッセージ編集部１４０で行われる処理の一例を示すフローチャートである。この処理は、送信メッセージ編集部１４０が、送信開始のメッセージＩＤを配信開始日時管理部１３０より受信した後に実行される（Ｓ５１）。 FIG. 14 is a flowchart illustrating an example of processing performed by the transmission message editing unit 140. This process is executed after the transmission message editing unit 140 receives the message ID for starting transmission from the distribution start date management unit 130 (S51).
　送信メッセージ編集部１４０は、当該メッセージＩＤのＳＡＩ１２５６、ＭＢＭＳ－ＧＷ１２５２、ＭＭＥ１２５３、ＭＣＥ１２５４、ｅＮＢ１２５５５、センサ機種名１２５７、配信内容１２５８の情報をブロードキャスト配信メッセージテーブル１２５より取得する（Ｓ５２）。送信メッセージ編集部１４０は、当該メッセージＩＤのＳＡＩ１２５６情報がブロードキャスト配信メッセージテーブル１２５に存在するか否かを判定する（Ｓ５３）。 The transmission message editing unit 140 acquires information on the message ID SAI 1256, MBMS-GW 1252, MME 1253, MCE 1254, eNB 12555, sensor model name 1257, and distribution content 1258 from the broadcast distribution message table 125 (S52). The transmission message editing unit 140 determines whether or not the SAI 1256 information of the message ID exists in the broadcast delivery message table 125 (S53).
　ブロードキャスト配信メッセージテーブル１２５に当該メッセージＩＤのＳＡＩ１２５６情報が存在する場合は、送信メッセージ編集部１４０が、ブロードキャスト配信メッセージを生成して（Ｓ５４）、ブロードキャスト配信メッセージを配信メッセージ送信部１５０に送信する（Ｓ５５）。 When the SAI 1256 information of the message ID exists in the broadcast delivery message table 125, the transmission message editing unit 140 generates a broadcast delivery message (S54) and transmits the broadcast delivery message to the delivery message sending unit 150 (S55). ).
　一方、ブロードキャスト配信メッセージテーブル１２５に当該メッセージＩＤのＳＡＩが存在しない場合は、ステップＳ５６へスキップする。次に、送信メッセージ編集部１４０は、当該メッセージＩＤのＩｏＴ－ＧＷ　ＩＤ１２７２と、センサ機種名１２７３と、配信内容１２７４の情報をユニキャスト配信メッセージテーブル１２７より取得する。 On the other hand, when the SAI of the message ID does not exist in the broadcast delivery message table 125, the process skips to step S56. Next, the transmission message editing unit 140 acquires the IoT-GW ID 1272 of the message ID, the sensor model name 1273, and the information of the distribution content 1274 from the unicast distribution message table 127.
　送信メッセージ編集部１４０は、当該メッセージＩＤのＩｏＴ－ＧＷ　ＩＤ１２７２の情報がユニキャスト配信メッセージテーブル１２７に存在するか否かを判定する（Ｓ５３）。 The transmission message editing unit 140 determines whether the information of the IoT-GW ID 1272 of the message ID exists in the unicast delivery message table 127 (S53).
　ユニキャスト配信メッセージテーブル１２７に当該メッセージＩＤのＩｏＴ－ＧＷ　ＩＤ１２７２の情報が存在する場合は、送信メッセージ編集部１４０がユニキャスト配信メッセージをＩｏＴ－ＧＷ　ＩＤ１２７２の数に応じて生成して（Ｓ５８）、配信メッセージ送信部１５０に逐次送信する。 When the information of the IoT-GW ID 1272 of the message ID exists in the unicast delivery message table 127, the transmission message editing unit 140 generates a unicast delivery message according to the number of IoT-GW ID 1272 (S58). It transmits to the delivery message transmission part 150 sequentially.
　一方、ユニキャスト配信メッセージテーブル１２７に当該メッセージＩＤのＩｏＴ－ＧＷ　ＩＤ１２７２の情報が存在しない場合は、処理を終了する。 On the other hand, if the IoT-GW ID 1272 information of the message ID does not exist in the unicast delivery message table 127, the process ends.
　送信メッセージ編集部１４０が、メッセージＩＤに対する当該情報をブロードキャスト配信メッセージテーブル１２５及びユニキャスト配信メッセージテーブル１２７より取得する処理では、少なくともＳＡＩの情報かＩｏＴ－ＧＷ　ＩＤの情報かが得られる。そのため、当該メッセージＩＤに対する前記の配信方法決定部１２２の処理は、送信メッセージ編集部１４０の処理より先に終了することが特徴である。 In the process in which the transmission message editing unit 140 acquires the information for the message ID from the broadcast distribution message table 125 and the unicast distribution message table 127, at least SAI information or IoT-GW ID information is obtained. Therefore, the process of the delivery method determination unit 122 for the message ID is characterized in that it ends before the process of the transmission message editing unit 140.
　図１５は、ブロードキャスト配信メッセージ３００の情報の一例を示す図である。ブロードキャスト配信メッセージ３００は、ＳＡＩ３０５と、ｅＭＢＭＳ配信用情報転送ネットワーク機器（ＭＢＭＳ－ＧＷ３０１、ＭＭＥ３０２、ＭＣＥ３０３、ｅＮＢ３０４）と、センサ機種名３０６と、配信内容３０７の情報を含む。 FIG. 15 is a diagram illustrating an example of information of the broadcast delivery message 300. The broadcast delivery message 300 includes information on the SAI 305, eMBMS delivery information transfer network equipment (MBMS-GW301, MME302, MCE303, eNB304), sensor model name 306, and delivery content 307.
　図１６は、ユニキャスト配信メッセージ３５０の情報の一例を示す図である。ユニキャスト配信メッセージ３５０は、ＩｏＴ－ＧＷ　ＩＤ３５１、センサ機種名３５２、配信内容３５３の情報を含む。 FIG. 16 is a diagram showing an example of information of the unicast delivery message 350. The unicast delivery message 350 includes information on the IoT-GW ID 351, the sensor model name 352, and the delivery content 353.
　図１７は配信メッセージ送信部１５０で行われる処理の一例を示すフローチャートである。配信メッセージ送信部１５０は、配信メッセージを送信メッセージ編集部１４０より受信した場合（Ｓ６１）は、当該配信メッセージをＬＴＥコアネットワーク３に送信する（Ｓ６２）。 FIG. 17 is a flowchart illustrating an example of processing performed by the delivery message transmission unit 150. When the delivery message transmission unit 150 receives the delivery message from the transmission message editing unit 140 (S61), the delivery message transmission unit 150 transmits the delivery message to the LTE core network 3 (S62).
　配信メッセージは、上述のブロードキャスト配信メッセージ３００若しくはユニキャスト配信メッセージ３５０である。配信メッセージ送信部１５０は、一つのメッセージＩＤに対して、ブロードキャスト配信メッセージ３００及びユニキャスト配信メッセージ３５０の両方を送信することがある。また、配信メッセージ送信部１５０は、一つのメッセージＩＤに対して一つのブロードキャスト配信メッセージ３００のみを送信するが、一つのメッセージＩＤに対して複数のユニキャスト配信メッセージ３５０を送信することがある。 The delivery message is the broadcast delivery message 300 or the unicast delivery message 350 described above. The distribution message transmission unit 150 may transmit both the broadcast distribution message 300 and the unicast distribution message 350 for one message ID. Further, the distribution message transmission unit 150 transmits only one broadcast distribution message 300 for one message ID, but may transmit a plurality of unicast distribution messages 350 for one message ID.
　図１８は、本実施例のＩｏＴシステムで行われる処理として、更新ファイル配信の一例を示すシーケンス図である。図示の例では、ＩｏＴハブ１が特定機種のＩｏＴ－ＧＷ５へ、ソフトウェア更新用の制御コマンドを配信した場合を示す。当該ＩｏＴ－ＧＷ５は、更新ファイルを受信した後にソフトウェアの更新を実施する。 FIG. 18 is a sequence diagram showing an example of update file delivery as processing performed in the IoT system of this embodiment. In the illustrated example, a case where the IoT hub 1 distributes a control command for software update to a specific model IoT-GW 5 is shown. The IoT-GW 5 performs software update after receiving the update file.
　コンテンツサーバ２が、特定機種のＩｏＴ－ＧＷ５の更新ファイルを含む配信要求メッセージ２００をＩｏＴハブ１に送信する（Ｓ７１）。ＩｏＴハブ１は、配信要求メッセージ２００を受信したことを示す応答をコンテンツサーバ２に送信する（Ｓ７２）。 The content server 2 transmits a distribution request message 200 including an update file of a specific model IoT-GW 5 to the IoT hub 1 (S71). The IoT hub 1 transmits a response indicating that the distribution request message 200 has been received to the content server 2 (S72).
　次に、ＩｏＴハブ１では上記図８に示した配信方法決定処理が実行され（Ｓ７３）た後に、図１１に示した配信順序制御処理が実行されて（Ｓ７４）配信スケジュールテーブル１１２と、ブロードキャスト配信メッセージテーブル１２５と、ユニキャスト配信メッセージテーブル１２７が更新される。 Next, after the delivery method determination process shown in FIG. 8 is executed in the IoT hub 1 (S73), the delivery order control process shown in FIG. 11 is executed (S74), and the delivery schedule table 112 and broadcast delivery are performed. The message table 125 and the unicast delivery message table 127 are updated.
　そして、配信開始日時になると、ＩｏＴハブ１が配信メッセージをＬＴＥコアネットワーク３に送信する（Ｓ７５）。ＬＴＥコアネットワークは、配信メッセージの受信応答をＩｏＴハブ１に返した後に（Ｓ７６）、ＩｏＴハブ１の配信メッセージの情報によって配信対象の配信サービスエリア４ごとにブロードキャスト配信するか、あるいは個別のＩｏＴ－ＧＷ　ＩＤを指定してユニキャスト配信によってＩｏＴ－ＧＷ５へ配信を行う（Ｓ７７）。 When the distribution start date / time is reached, the IoT hub 1 transmits a distribution message to the LTE core network 3 (S75). The LTE core network returns a delivery message reception response to the IoT hub 1 (S76), and then broadcasts to each delivery service area 4 to be delivered according to the delivery message information of the IoT hub 1, or an individual IoT- The GW ID is designated and distributed to the IoT-GW 5 by unicast distribution (S77).
　次に、当該ＩｏＴ－ＧＷ５は、基地局６（ｅＮＢ）より受信した配信メッセージに対して、受信した応答をＬＴＥコアネットワーク３に送信し（Ｓ７８）、ソフトウェアの更新を実施する（Ｓ７９）。 Next, the IoT-GW 5 transmits the received response to the LTE core network 3 in response to the delivery message received from the base station 6 (eNB) (S78), and updates the software (S79).
　ＩｏＴ－ＧＷ５は、ソフトウェアの更新を実施した後に、更新処理の終了通知をＬＴＥコアネットワーク３に送信する（Ｓ８０）。ＬＴＥコアネットワーク３は、受信した更新処理の終了通知をＩｏＴハブ１に送信する（Ｓ８１）。その後、ＩｏＴハブ１がＬＴＥコアネットワーク３からの更新処理の終了通知をコンテンツサーバ２に送信する。 The IoT-GW 5 transmits the update process end notification to the LTE core network 3 after performing the software update (S80). The LTE core network 3 transmits the received update process end notification to the IoT hub 1 (S81). Thereafter, the IoT hub 1 transmits an update processing end notification from the LTE core network 3 to the content server 2.
　図１８における更新ファイルは、通常大きな容量を有する。当該機種のＩｏＴ－ＧＷ５の合計台数が多いほど当該ＩｏＴ－ＧＷ５へのデータ通信が莫大になる。当該機種のＩｏＴ－ＧＷ５の合計台数が非常に多い配信対象のＳＡＩではブロードキャスト配信を行うことにより、数の多い当該ＩｏＴ－ＧＷ５に更新ファイルを一回のみ配信して済む。 The update file in FIG. 18 usually has a large capacity. As the total number of IoT-GWs 5 of the model increases, data communication to the IoT-GW 5 becomes enormous. By performing broadcast distribution in the distribution target SAI in which the total number of IoT-GWs 5 of the model is very large, the update file can be distributed only once to the large number of IoT-GWs 5.
　一方、当該機種のＩｏＴ－ＧＷ５の合計台数が非常に少ない配信対象のＳＡＩでは、ユニキャスト配信を行うことにより、数が多い対象外のＩｏＴ－ＧＷ５への無駄な配信を抑制できる。全体的には、ＬＴＥコアネットワーク３における無駄なデータ通信を抑制し、エッジデバイス（ＩｏＴ－ＧＷ５やセンサ７）の間の制御時間（更新開始時刻）の差分を抑制してエッジデバイスを効率的に制御できる。 On the other hand, in the distribution target SAI in which the total number of IoT-GWs 5 of the model is very small, useless distribution to the IoT-GW 5 that is not a large number can be suppressed by performing unicast distribution. Overall, useless data communication in the LTE core network 3 is suppressed, and the difference in control time (update start time) between edge devices (IoT-GW 5 and sensor 7) is suppressed, so that the edge devices are efficiently used. Can be controlled.
　また、上記実施例ではコンテンツサーバ２が配信要求メッセージ２００に優先度２０４を設定できるため、ＩｏＴハブ１が配信要求メッセージ２００の優先度２０４に基づいて、同一の配信開始日時の配信要求メッセージに対して配信順序を適切に制御することが可能となる。 In the above embodiment, since the content server 2 can set the priority 204 for the distribution request message 200, the IoT hub 1 responds to the distribution request message with the same distribution start date and time based on the priority 204 of the distribution request message 200. Thus, it is possible to appropriately control the distribution order.
　なお、エッジデバイスは、１つ以上のセンサを制御し、当該センサが測定したデータをＩｏＴハブ１へ送信する装置であればよく、計算機や通信装置で構成しても良い。また、ＩｏＴハブ１は、エッジデバイス（ＩｏＴ－ＧＷ５、センサ７）を制御する管理装置として機能すれば良い。 Note that the edge device may be a device that controls one or more sensors and transmits data measured by the sensors to the IoT hub 1, and may be configured by a computer or a communication device. The IoT hub 1 may function as a management device that controls the edge device (IoT-GW 5, sensor 7).
　また、上記実施例では、配信サービスエリア４を特定する送信条件としてＩｏＴ－ＧＷ機種名２０１を用いる例を示したが、これに限定されるものではなく、ＩｏＴ－ＧＷ５の形式や種類等の情報を送信条件として用いるようにしても良い。 In the above-described embodiment, an example in which the IoT-GW model name 201 is used as a transmission condition for specifying the distribution service area 4 is shown. However, the present invention is not limited to this, and information such as the format and type of the IoT-GW 5 is used. May be used as a transmission condition.
　また、上記実施例では、１対多の通信としてブロードキャスト配信を用いる例を示したが、マルチキャスト配信を用いるようにしても良い。マルチキャスト配信の場合は、ＩｏＴ－ＧＷ５に配信先のセンサ７のテーブルを設定しておき、当該テーブルの情報に基づいてマルチキャスト配信を実施するようにしてもよい。この場合、配信サービスエリア４毎に予め設定された配信条件にマルチキャスト配信の条件を加えることで、ブロードキャスト配信とユニキャスト配信とマルチキャスト配信のいずれか一つを選択するようにしてもよい。 In the above embodiment, an example is shown in which broadcast distribution is used as one-to-many communication, but multicast distribution may be used. In the case of multicast distribution, a table of the distribution destination sensor 7 may be set in the IoT-GW 5, and multicast distribution may be performed based on information in the table. In this case, any one of broadcast distribution, unicast distribution, and multicast distribution may be selected by adding multicast distribution conditions to distribution conditions set in advance for each distribution service area 4.
　なお、本発明は上記した実施例に限定されるものではなく、様々な変形例が含まれる。例えば、上記した実施例は本発明を分かりやすく説明するために詳細に記載したものであり、必ずしも説明した全ての構成を備えるものに限定されるものではない。また、ある実施例の構成の一部を他の実施例の構成に置き換えることが可能であり、また、ある実施例の構成に他の実施例の構成を加えることも可能である。また、各実施例の構成の一部について、他の構成の追加、削除、又は置換のいずれもが、単独で、又は組み合わせても適用可能である。 In addition, this invention is not limited to the above-mentioned Example, Various modifications are included. For example, the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. In addition, any of the additions, deletions, or substitutions of other configurations can be applied to a part of the configuration of each embodiment, either alone or in combination.
　また、上記の各構成、機能、処理部、及び処理手段等は、それらの一部又は全部を、例えば集積回路で設計する等によりハードウェアで実現してもよい。また、上記の各構成、及び機能等は、プロセッサがそれぞれの機能を実現するプログラムを解釈し、実行することによりソフトウェアで実現してもよい。各機能を実現するプログラム、テーブル、ファイル等の情報は、メモリや、ハードディスク、ＳＳＤ等の記録装置、または、ＩＣカード、ＳＤカード、ＤＶＤ等の記録媒体に置くことができる。 In addition, each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. In addition, each of the above-described configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files for realizing each function can be stored in a recording device such as a memory, a hard disk, and an SSD, or a recording medium such as an IC card, an SD card, and a DVD.
　また、制御線や情報線は説明上必要と考えられるものを示しており、製品上必ずしも全ての制御線や情報線を示しているとは限らない。実際には殆ど全ての構成が相互に接続されていると考えてもよい。 Also, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

Claims (15)

  1. 　プロセッサとメモリを有するＩｏＴハブが、ネットワークを介して接続された１つ以上のサービスエリア内のエッジデバイスを制御するエッジデバイスの制御方法であって、
    　前記ＩｏＴハブが、配信要求メッセージを受信する第１のステップと、
    　前記ＩｏＴハブが、前記配信要求メッセージに含まれる送信条件に基づいて、配信対象のサービスエリアを特定する第２のステップと、
    　前記ＩｏＴハブが、前記特定されたサービスエリア毎にブロードキャスト配信とユニキャスト配信のいずれかを選択する第３のステップと、
    を含むことを特徴とするエッジデバイスの制御方法。     An edge device control method in which an IoT hub having a processor and a memory controls an edge device in one or more service areas connected via a network,
    A first step in which the IoT hub receives a delivery request message;
    A second step in which the IoT hub specifies a service area to be distributed based on a transmission condition included in the distribution request message;
    A third step in which the IoT hub selects either broadcast distribution or unicast distribution for each identified service area;
    A method for controlling an edge device, comprising:
  2. 　請求項１に記載のエッジデバイスの制御方法であって、
    　前記第３のステップは、
    　前記特定されたサービスエリア毎にブロードキャスト配信とユニキャスト配信とマルチキャスト配信のいずれかひとつを選択することを特徴とするエッジデバイスの制御方法。     An edge device control method according to claim 1,
    The third step includes
    A method for controlling an edge device, wherein one of broadcast distribution, unicast distribution, and multicast distribution is selected for each specified service area.
  3. 　請求項１に記載のエッジデバイスの制御方法であって、
    　前記第３のステップは、
    　前記サービスエリア毎にブロードキャスト配信とユニキャスト配信のいずれかを選択する基準値を予め設定したエッジデバイスとサービスエリアの関連情報に基づいて選択することを特徴とするエッジデバイスの制御方法。     An edge device control method according to claim 1,
    The third step includes
    A method for controlling an edge device, comprising: selecting a reference value for selecting either broadcast distribution or unicast distribution for each service area based on information related to a preset edge device and service area.
  4. 　請求項１に記載のエッジデバイスの制御方法であって、
    　前記ＩｏＴハブが、前記選択された前記ブロードキャスト配信またはユニキャスト配信と、前記配信要求メッセージの内容に基づいて配信メッセージを生成する第４のステップを、さらに含むことを特徴とするエッジデバイスの制御方法。     An edge device control method according to claim 1,
    The edge device control method further comprising a fourth step in which the IoT hub generates a delivery message based on the selected broadcast delivery or unicast delivery and the content of the delivery request message. .
  5. 　請求項１に記載のエッジデバイスの制御方法であって、
    　前記ＩｏＴハブが、前記配信要求メッセージに含まれる配信開始日時と優先度を取得して配信スケジュール情報に格納し、前記配信スケジュール情報内で前記配信開始日時が同一の配信メッセージが存在する場合には、前記優先度に基づいて配信する順序を変更する第４のステップを、さらに含むことを特徴とするエッジデバイスの制御方法。     An edge device control method according to claim 1,
    When the IoT hub acquires the distribution start date and time and priority included in the distribution request message and stores them in the distribution schedule information, and there is a distribution message having the same distribution start date and time in the distribution schedule information A method for controlling an edge device, further comprising a fourth step of changing a distribution order based on the priority.
  6. 　プロセッサとメモリを含んで、ネットワークを介して接続された１つ以上のサービスエリア内のエッジデバイスを制御するＩｏＴハブであって、
    　配信要求メッセージを受信して、前記配信要求メッセージに含まれる送信条件に基づいて、配信対象のサービスエリアを特定する配信サービスエリア解析部と、
    　前記特定されたサービスエリア毎にブロードキャスト配信とユニキャスト配信のいずれかを選択する配信方法決定部と、
    を有することを特徴とするＩｏＴハブ。     An IoT hub that includes a processor and memory and controls edge devices in one or more service areas connected via a network;
    A distribution service area analyzer that receives a distribution request message and identifies a service area to be distributed based on a transmission condition included in the distribution request message;
    A delivery method determination unit that selects either broadcast delivery or unicast delivery for each identified service area;
    An IoT hub characterized by comprising:
  7. 　請求項６に記載のＩｏＴハブであって、
    　前記配信方法決定部は、
    　前記特定されたサービスエリア毎にブロードキャスト配信とユニキャスト配信とマルチキャスト配信のいずれかひとつを選択することを特徴とするＩｏＴハブ。     The IoT hub according to claim 6, wherein
    The delivery method determination unit
    An IoT hub, wherein one of broadcast distribution, unicast distribution, and multicast distribution is selected for each identified service area.
  8. 　請求項６に記載のＩｏＴハブであって、
    　前記配信方法決定部は、
    　前記サービスエリア毎にブロードキャスト配信とユニキャスト配信のいずれかを選択する基準値を予め設定したエッジデバイスとサービスエリアの関連情報に基づいて選択することを特徴とするＩｏＴハブ。     The IoT hub according to claim 6, wherein
    The delivery method determination unit
    An IoT hub, wherein a reference value for selecting either broadcast distribution or unicast distribution for each service area is selected based on information related to a preset edge device and service area.
  9. 　請求項６に記載のＩｏＴハブであって、
    　前記選択された前記ブロードキャスト配信またはユニキャスト配信と、前記配信要求メッセージの内容に基づいて配信メッセージを生成する送信メッセージ編集部を、さらに有することを特徴とするＩｏＴハブ。     The IoT hub according to claim 6, wherein
    An IoT hub, further comprising: a transmission message editing unit that generates a delivery message based on the selected broadcast delivery or unicast delivery and the content of the delivery request message.
  10. 　請求項６に記載のＩｏＴハブであって、
    　前記配信要求メッセージに含まれる配信開始日時と優先度を取得して配信スケジュール情報に格納し、前記配信スケジュール情報内で前記配信開始日時が同一の配信メッセージが存在する場合には、前記優先度に基づいて配信する順序を変更する配信順序制御部を、さらに有することを特徴とするＩｏＴハブ。     The IoT hub according to claim 6, wherein
    The distribution start date and time and priority included in the distribution request message are acquired and stored in the distribution schedule information, and when there is a distribution message having the same distribution start date and time in the distribution schedule information, the priority is set. An IoT hub, further comprising: a delivery order control unit that changes a delivery order based on the delivery order control unit.
  11. 　プロセッサとメモリを有する計算機で、ネットワークを介して接続された１つ以上のサービスエリア内のエッジデバイスを制御するプログラムを格納した記憶媒体であって、
    　配信要求メッセージを受信する第１のステップと、
    　前記配信要求メッセージに含まれる送信条件に基づいて、配信対象のサービスエリアを特定する第２のステップと、
    　前記特定されたサービスエリア毎にブロードキャスト配信とユニキャスト配信のいずれかを選択する第３のステップと、
    を前記計算機に実行させるプログラムを格納した非一時的な計算機読み取り可能な記憶媒体。     A storage medium storing a program for controlling an edge device in one or more service areas connected via a network by a computer having a processor and a memory,
    A first step of receiving a delivery request message;
    A second step of identifying a service area to be distributed based on a transmission condition included in the distribution request message;
    A third step of selecting either broadcast distribution or unicast distribution for each identified service area;
    A non-transitory computer-readable storage medium storing a program for causing the computer to execute.
  12. 　請求項１１に記載の記憶媒体であって、
    　前記第３のステップは、
    　前記特定されたサービスエリア毎にブロードキャスト配信とユニキャスト配信とマルチキャスト配信のいずれかひとつを選択することを特徴とする記憶媒体。     The storage medium according to claim 11,
    The third step includes
    A storage medium, wherein one of broadcast distribution, unicast distribution, and multicast distribution is selected for each specified service area.
  13. 　請求項１１に記載の記憶媒体であって、
    　前記第３のステップは、
    　前記サービスエリア毎にブロードキャスト配信とユニキャスト配信のいずれかを選択する基準値を予め設定したエッジデバイスとサービスエリアの関連情報に基づいて選択することを特徴とする記憶媒体。     The storage medium according to claim 11,
    The third step includes
    A storage medium, wherein a reference value for selecting either broadcast distribution or unicast distribution for each service area is selected based on information related to a preset edge device and service area.
  14. 　請求項１１に記載の記憶媒体であって、
    　前記選択された前記ブロードキャスト配信またはユニキャスト配信と、前記配信要求メッセージの内容に基づいて配信メッセージを生成する第４のステップを、さらに含むことを特徴とする記憶媒体。     The storage medium according to claim 11,
    The storage medium further comprising a fourth step of generating a delivery message based on the selected broadcast delivery or unicast delivery and the content of the delivery request message.
  15. 　請求項１１に記載の記憶媒体であって、
    　前記配信要求メッセージに含まれる配信開始日時と優先度を取得して配信スケジュール情報に格納し、前記配信スケジュール情報内で前記配信開始日時が同一の配信メッセージが存在する場合には、前記優先度に基づいて配信する順序を変更する第４のステップを、さらに含むことを特徴とする記憶媒体。     The storage medium according to claim 11,
    The distribution start date and time and priority included in the distribution request message are acquired and stored in the distribution schedule information, and when there is a distribution message having the same distribution start date and time in the distribution schedule information, the priority is set. A storage medium further comprising a fourth step of changing a distribution order based on the distribution.
PCT/JP2016/085591 2016-11-30 2016-11-30 EDGE DEVICE CONTROL METHOD, IoT HUB, AND STORAGE MEDIUM WO2018100687A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/085591 WO2018100687A1 (en) 2016-11-30 2016-11-30 EDGE DEVICE CONTROL METHOD, IoT HUB, AND STORAGE MEDIUM

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/085591 WO2018100687A1 (en) 2016-11-30 2016-11-30 EDGE DEVICE CONTROL METHOD, IoT HUB, AND STORAGE MEDIUM

Publications (1)

Publication Number Publication Date
WO2018100687A1 true WO2018100687A1 (en) 2018-06-07

Family

ID=62242033

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/085591 WO2018100687A1 (en) 2016-11-30 2016-11-30 EDGE DEVICE CONTROL METHOD, IoT HUB, AND STORAGE MEDIUM

Country Status (1)

Country Link
WO (1) WO2018100687A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021006983A (en) * 2019-06-27 2021-01-21 ＩｏＴ−ＥＸ株式会社 Iot connection system, information processing method, and computer program

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007336379A (en) * 2006-06-16 2007-12-27 Toshiba Corp Communication apparatus, communication terminal device, communication system, method and program
JP2013026728A (en) * 2011-07-19 2013-02-04 Hitachi Kokusai Electric Inc Data distribution system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007336379A (en) * 2006-06-16 2007-12-27 Toshiba Corp Communication apparatus, communication terminal device, communication system, method and program
JP2013026728A (en) * 2011-07-19 2013-02-04 Hitachi Kokusai Electric Inc Data distribution system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021006983A (en) * 2019-06-27 2021-01-21 ＩｏＴ−ＥＸ株式会社 Iot connection system, information processing method, and computer program
JP7350663B2 (en) 2019-06-27 2023-09-26 ＩｏＴ－ＥＸ株式会社 IoT connection system, information processing method and computer program

Similar Documents

Publication Publication Date Title
US11418413B2 (en) Sharable storage method and system for network data analytics
US10638362B2 (en) Method and system for group communication, group server, and group member device
JP2020509635A (en) Network slice selection method, user equipment, and network device
US9872276B2 (en) Scheduling of software package transmissions on a multimedia broadcast multicast service channel
US10638496B2 (en) Method and apparatus for group management during machine-to-machine communication
EP2211568B1 (en) Method of obtaining service information to receive broadcasting service in a user equipment
CN109783426A (en) Acquire method, apparatus, computer equipment and the storage medium of data
CN115699824A (en) Mobility method and apparatus for supporting collection and analysis of network data in a wireless communication network
CN105578444A (en) Automatic resource subscription method and device
US11929938B2 (en) Evaluating overall network resource congestion before scaling a network slice
WO2018100687A1 (en) EDGE DEVICE CONTROL METHOD, IoT HUB, AND STORAGE MEDIUM
WO2017063677A1 (en) Adaptive precision for reporting consumption of streamed content
KR102488791B1 (en) Association redirection method and device
EP3826229B1 (en) Management method and device for management service
JP2014209676A (en) Communication device, communication method, and radio communication system
JP6555627B2 (en) Information distribution apparatus, push notification transmission method, and computer program
WO2016074455A1 (en) Group resource update processing method, device and system, and cse
JP6360143B2 (en) Information distribution apparatus, push notification transmission method, and computer program
EP4089962B1 (en) Network analytics component and method for providing network analytics information
US20240054109A1 (en) Dynamic file based publish-subscribe method and system
JP6072114B2 (en) Information distribution apparatus, push notification transmission method, and computer program
GB2619582A (en) Monitoring for application AI/ML-based services and operations
CN115038185A (en) Method and device for configuring network slices of base station and readable storage medium
WO2023126479A1 (en) User consent based model provisioning
US8880645B1 (en) Registration of media content with a content distribution network for transfer at a later time

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16923022

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16923022

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP