Distribution server, distribution server control method, and distribution server control program

Abstract

To provide FOTA efficiently and equally among base stations [Solution] A distribution server that distributes update software to communication devices connected to a base station includes an acquisition unit that acquires, from the communication device to which the update software is to be distributed, identification information that identifies the base station to which the communication device is connected; a setting unit that acquires the number of communication devices connected to each of the multiple base stations based on the identification information acquired from the multiple communication devices, and sets the ratio for each base station of communication devices to which the update software will be distributed in one distribution based on the number; and a distribution unit that distributes the update software to each of the multiple base stations, with the number of devices to distribute to each of the multiple base stations set based on the ratio.

Description

[Technical Field]

[0001] The present invention relates to a distribution server, a control method for a distribution server, and a control program for a distribution server. [Background technology]

[0002] Conventionally, a technology called FOTA (Firmware Over The Air) has been known for wireless communication devices, which updates the firmware (software program) of the device via wireless communication to fix defects or add functions. FOTA is also used for IoT (Internet of Things) devices, and for example, Patent Document 1 discloses a firmware providing device that provides firmware to IoT devices. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6762989 Summary of the Invention [Means for solving the problem]

[0004] In one embodiment of the present invention, a distribution server that distributes update software to communication devices connected to a base station includes an acquisition unit that acquires, from the communication device to which the update software is to be distributed, identification information that identifies the base station to which the communication device is connected; a setting unit that acquires the number of communication devices connected to each of the multiple base stations based on the identification information acquired from the multiple communication devices, and sets, based on the number, a ratio for each base station of the communication devices to which the update software will be distributed in one distribution; and a distribution unit that distributes the update software to each of the multiple base stations, the number of devices to be distributed for each of the multiple base stations set based on the ratio.

[0005] In the distribution server according to one embodiment of the present invention, the acquisition unit may acquire the identification information via a management server that communicates with the communication device using a predetermined protocol.

[0006] In a distribution server according to one embodiment of the present invention, an acquisition unit acquires identification information from a communication device at predetermined intervals, a setting unit updates a ratio at predetermined intervals, and a distribution unit distributes update software to each of a plurality of base stations at a number of distribution units set according to the ratio updated by the setting unit.

[0007] In a distribution server according to one embodiment of the present invention, the distribution unit may distribute update software to each of a plurality of base stations at a distribution number for each of the plurality of base stations, the distribution number being obtained based on the maximum number of units that can be distributed in one distribution and the ratio.

[0008] In a distribution server according to one embodiment of the present invention, the distribution unit may distribute update software using a communication method according to Category M1 among communication methods conforming to LPWA (Low Power Wide Area).

[0009] According to one embodiment of the present invention, a control method for a distribution server that distributes update software to communication devices connected to a base station includes the steps of: a computer acquiring, from the communication device to which the update software is to be distributed, identification information that identifies the base station to which the communication device is connected; acquiring the number of communication devices connected to each of the plurality of base stations based on the identification information acquired from the plurality of communication devices, and setting, based on the number, a ratio for each base station of the communication devices to which the update software will be distributed in one distribution; and distributing the update software to each of the plurality of base stations, the number of devices to be distributed for each of the plurality of base stations set based on the ratio.

[0010] According to one embodiment of the present invention, a control method for a distribution server that distributes update software to communication devices connected to a base station includes a computer that implements the following functions: acquiring, from the communication device to which the update software is to be distributed, identification information that identifies the base station to which the communication device is connected; acquiring the number of communication devices connected to each of the plurality of base stations based on the identification information acquired from the plurality of communication devices, and setting, based on the number, a ratio for each base station of communication devices to which the update software will be distributed in one distribution; and distributing the update software to each of the plurality of base stations, the number of devices to be distributed for each of the plurality of base stations set based on the ratio. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram showing an example of the configuration of a distribution system according to an embodiment of the present invention. [Figure 2] 2(a) to 2(c) are schematic diagrams for explaining one embodiment of the present invention. [Figure 3] FIG. 3 is a schematic diagram of a distribution server and a communication device according to an embodiment of the present invention. [Figure 4] FIG. 4 shows an example of a sequence between a communication device and a distribution server according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the invention according to the present disclosure (also referred to as the present invention) will be described using the drawings. Note that the drawings are merely examples, and the present invention is not limited to those shown in the drawings. For example, the number of distribution servers (information processing devices), management servers, base stations, communication devices (IoT devices), core networks, and database servers, as well as the sequence diagram shown in the drawings, are merely examples, and the present invention is not limited to these.

[0013] LPWA (Low Power Wide Area) is attracting attention as a communication technology for IoT. LPWA is a communication technology that achieves low power consumption and long-distance communication, and is suitable for IoT devices that can be installed in various indoor and outdoor locations and are powered by built-in batteries without external power sources. Examples of communication methods for IoT that fall under LPWA include Category M1, an extension of LTE (Long Term Evolution) (registered trademark), and NB-IoT (Narrow Band IoT).

[0014] Both Category M1 and NB-IoT mentioned above are capable of long-distance communication with lower power consumption than LTE and Wi-Fi (registered trademark), but they are characterized by narrow communication bandwidths and slow communication speeds. Therefore, downloading large amounts of data, such as firmware update software, compared to the data sent and received by IoT devices during normal operation takes time, occupying the communication bandwidth for a long period of time. Therefore, when FOTA is simultaneously performed on a large number of IoT devices within the communication range (cell) provided by a certain base station, it takes time to complete the delivery of the update software, resulting in a low FOTA success rate. For example, when FOTA is performed on IoT devices located in multiple cells provided by different base stations, there is a problem that the delivery of update software is successful for IoT devices in one cell but fails for IoT devices in another cell.

[0015] In contrast, according to an embodiment of the present disclosure, the number of IoT devices that execute FOTA may be varied by base station depending on the number of IoT devices present in the cell. This reduces the time required for FOTA for IoT devices. In other words, according to an embodiment of the present disclosure, FOTA for IoT devices can be made more efficient.

[0016] <System configuration> 1 is a diagram showing an example of the configuration of a distribution system according to an embodiment of the present invention. Distribution system 600 may be a system that distributes update software for updating firmware to communication device 200. Here, "distribution" may refer to making the update software available for communication device 200 to acquire. For example, distribution unit 113 may store the update software in a location from which communication device 200 can download it, and notify communication device 200 of information about the location (URL (Uniform Resource Locator) of the download destination).

[0017] The distribution system 600 may include a distribution server 100, a management server 101, a database server 400, base stations 300 (300A, 300B, 300C), multiple communication devices 200 (200Aa, 200Ab, ..., 200Ba, 200Bb, ..., 200Ca, 200Cb, ...), and a mobile communication network 500. Here, the mobile communication network 500 may include a wireless access network through which the base stations 300 and the communication devices 200 exchange data, and a core network 50. Note that in FIG. 1 , the communication devices 200 connected to the base stations 300A, 300B, 300C, respectively, are designated by the same capital letters A, B, and C, and lowercase letters a, b, ... are used to distinguish between the communication devices. However, when no particular distinction is required, the communication devices will be simply referred to as the base station 300 and the communication device 200.

[0018] The communication device 200 may be any of various IoT devices connected to the base stations 300 and existing (located within) the cell of each base station 300. Hereinafter, the communication device 200 will be described as an IoT device installed in a smart meter for gas (city gas, LP gas), water, electricity, etc., and transmitting meter reading data, etc. However, the present invention is not limited to this, and the communication device 200 may be an IoT sensor used to monitor infrastructure such as bridges and roads, a wearable device, etc.

[0019] The communication device 200 may be a device that complies with a communication method for IoT classified as LPWA, such as NB-IoT, Category M1, etc. Note that hereinafter, the communication method when the communication device 200 connects to a wireless access network will be described as Category M1.

[0020] Distribution server 100 may have a function to manage firmware versions of each communication device 200 connected to base station 300 and, as necessary, transmit update software for updating the firmware of each communication device 200 (a function for executing FOTA). Note that the provider of the update software may be different from the provider that distributes it. For example, the update software may be provided by the manufacturer of each communication device 200 and distributed to each communication device 200 via distribution server 100 by a communications carrier that manages base station 300.

[0021] The management server 101 may function as an IoT-PF (platform) that processes the meter readings of each smart meter transmitted from each communication device 200 and transfers the necessary data to the administrator of the smart meter. The management server 101 may remotely control the communication devices 200 via a mobile communication network 500, and may be connected to a centralized monitoring center (not shown) where an administrator is on standby. The management server 101 and the distribution server 100 may be provided as the same server, or their functions may be distributed among multiple servers. The management server 101 and the distribution server 100 may be any information processing device that can realize the functions described in each embodiment, and may include, for example, a server device, a computer (for example, but not limited to, a desktop, laptop, tablet, etc.), a communication platform, etc.

[0022] The database server 400 may store various data for associating each communication device 200 with the base station 300, and various information required for processing related to FOTA. For example, the database server 400 may store information about the communication device 200 that is to perform FOTA. Note that, although the database server 400 is shown separately from the distribution server 100 in FIG. 1, the present invention is not limited to this, and the data stored in the database server 400 may be stored in, for example, the storage unit 170 of the distribution server 100. Furthermore, a separate database server 400 may exist for each type of data to be stored or for each entity that manages the database.

[0023] The core network 50 may include nodes such as an MME (Mobility Management Entity), an S-GW (Serving Gateway), a P-GW (Packet Data Network Gateway), and an SCEF (Service Capability Exposure Function), which are not shown. The MME has functions such as location management and authentication management of the communication device 200, and session management between each node (i.e., management of communication bearers). The MME also has a function of sending paging to the base station 300 when calling the communication device 200. The S-GW has a function as a gateway that routes and forwards user packets between the base station 300 and the core network 50. The P-GW has a function as a gateway that assigns an IP (Internet Protocol) address to the communication device 200 that can be used in IP communication networks subsequent to the core network 50, and enables communication between the communication device 200 and networks external to the mobile communication network 500 using the IP address. The S-GW and P-GW may be integrated into one node. The core network 50 may further include a Service Capability Server (SCS), not shown.

[0024] <Embodiment> An embodiment of the present invention will be described with reference to FIG.

[0025] First, the distribution server 100 may acquire information about the communication device 200 for which FOTA should be performed, based on information stored in the database server 400. The communication device for which FOTA should be performed may be, for example, a communication device that requires a firmware update to add a function, address a vulnerability, or update for compliance with a communication standard. The information about the communication device for which FOTA should be performed may be listed in, for example, a CSV data file format in the database server 400. Note that, hereinafter, the communication device for which FOTA should be performed is also referred to as the communication device to which the firmware update is to be distributed.

[0026] The distribution server 100 may acquire, from the communication device 200 to which the update software is to be distributed, identification information for identifying the base station 300 to which the communication device 200 is connected. The identification information for identifying the base station may be a cell ID (IDentifier: a type of identification information). The cell ID may be a number uniquely assigned to a base station and uniquely identifying the communication range (cell) of the base station. When connecting to the base station 300, the communication device 200 may store the cell ID of the base station 300 to which the communication device 200 is to be connected in a memory unit of the communication device 200. Note that the distribution server 100 may request the cell ID of the communication device 200 from the management server 101. In response to a request from the distribution server 100, the management server 101 may request the communication device 200 to transmit the cell ID, and transmit the cell ID acquired from the communication device 200 to the management server 101. This makes it possible to reliably acquire the cell ID.

[0027] The communication device 200 may transmit and receive data to and from the distribution server 100 using the LwM2M protocol. LwM2M uses a resource model format for data management. The resource model is a tree structure of objects, object instances, and resources, and each element is assigned a number. In one embodiment of the present invention, a cell ID identifying the base station 300 to which the communication device 200 is connected may be stored in resource "8" of connectivity monitoring object "4." Therefore, the distribution server 100 may generate a command specifying resource " / 4 / 0 / 8" when requesting transmission of the cell ID. When the communication device 200 receives a request specifying resource " / 4 / 0 / 8" from the distribution server 100, the communication device 200 may read the cell ID stored in the resource and transmit it to the distribution server 100. The method of identifying the base station 300 to which each communication device 200 is connected is not limited to the above.

[0028] 2(a) may be an example of a table associating communication devices 200 to which update software is to be distributed with base station identification information (cell ID) of base station 300 to which the communication devices 200 are connected. Table TB10 may store a communication device ID that uniquely identifies a communication device, in association with a cell ID to which the communication device 200 having the communication device ID is connected. For simplicity, in FIG. 2(a), each ID is indicated by the same symbol as in FIG. 1. For example, referring to table TB10, communication device 200Aa is connected to base station 300A. Note that the figure is an example, and the format of the table is not limited to this as long as it is possible to identify the base station to which communication device 200 is connected.

[0029] The distribution server 100 may acquire the number of communication devices 200 connected to each of the plurality of base stations 300 based on the identification information (cell IDs) acquired from the plurality of communication devices 200. FIG. 2(b) may be a table storing the number of communication devices connected to each of the base stations 300A to 300C. For example, table TB11 may be acquired based on table TB10 of FIG. 2(a) and may store the number of communication devices in association with a cell ID that uniquely identifies each base station. In the example of table TB11, 60, 30, and 10 communication devices are connected to base stations 300A, 300B, and 300C, respectively. Note that the numerical values ​​in table TB11 are simplified for ease of explanation, and the present invention is not limited thereto.

[0030] The distribution server 100 may set a ratio for each base station to which the update software is distributed in one distribution, based on the number of communication devices 200 connected to each base station 300. This will be described with reference to FIG. 2(c). From table TB11, the ratio of the communication devices 200 connected to base stations 300A, 300B, and 300C may be "6:3:1." Therefore, the distribution server 100 may set the number of communication devices to which the update software is distributed in one distribution to be "6:3:1" for base stations 300A, 300B, and 300C. The distribution server 100 may then distribute the update software to each of the multiple base stations, with the number of communication devices to be distributed for each base station set based on the ratio. That is, in FIG. 2(c), if band 30 indicates the number of units distributed at one time, update software may be distributed to base station 300A (base station A), base station 300B (base station B), and base station 300C (base station C) at a ratio of 6:3:1.

[0031] The above-mentioned advantages will be explained. For example, assume that the number of devices to which the distribution server 100 can distribute software updates at one time is 10 in the state of table TB11. Furthermore, assume that FOTA is performed for each base station 300 in a predetermined order, regardless of the number of communication devices 200 within the range of the base station 300. If distribution starts from base station 300A, FOTA updates will not be performed for base stations 300B and 300C until FOTA updates for 60 devices are completed, i.e., until six software updates have been distributed. In contrast, according to one embodiment of the present invention, software updates may be distributed according to the number of communication devices 200 within the range of the base station 300. Therefore, in the first distribution, FOTA updates for six, three, and one base stations 300A, 300B, and 300C, respectively, may be performed. This allows FOTA updates to be performed equally for each base station, thereby reducing the time required for FOTA updates for IoT devices.

[0032] The distribution server 100 may acquire a cell ID from the communication device 200 at a predetermined interval and update the above-mentioned ratio. The predetermined interval may be, for example, five minutes, but is not limited to this. When the ratio is updated, the distribution server 100 may distribute update software to each of the multiple base stations 300 with a distribution number set according to the updated ratio. This allows FOTA to be performed efficiently even if the IoT device is mobile, for example.

[0033] Furthermore, the distribution server 100 may set the number of base stations to which the software update can be distributed based on the upper limit of the number of base stations that can be distributed in one distribution and the above-mentioned ratio. This makes it possible to reliably start FOTA for each base station even if there is a limit on the number of base stations to which the software update can be distributed.

[0034] Next, the hardware configuration and functional configuration of the distribution server 100 and the communication device 200 according to one embodiment of the present invention will be described with reference to FIG.

[0035] <Distribution server> (1) Hardware configuration of distribution server 3 shows an example of a block diagram of the distribution server 100 according to an embodiment of the present invention. The distribution server 100 may include a control unit 110, a communication unit 120, an input / output unit 130, and a storage unit 170.

[0036] The storage unit 170 is typically realized by various recording media such as a hard disc drive (HDD), a solid state drive (SSD), or flash memory, and may have the function of storing various programs and data required for the operation of the distribution server 100.

[0037] The control unit 110 is typically a processor and may be realized by a central processing unit (CPU), a microprocessing unit (MPU), a graphics processing unit (GPU), or the like. The control unit 110 may execute the functions and methods described in each embodiment by reading a program stored in the storage unit 170 and executing code or instructions included in the read program. The control unit 110 may implement each process disclosed in each embodiment by a logic circuit (hardware) formed in an integrated circuit (an integrated circuit (IC) chip, a large scale integration (LSI)), or a dedicated circuit. Furthermore, these circuits may be implemented by one or more integrated circuits, and multiple processes described in each embodiment may be implemented by a single integrated circuit.

[0038] The communication unit 120 is implemented as hardware such as a network adapter, communication software, or a combination thereof, and transmits and receives various data to and from external devices. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between them is possible. For example, the distribution server 100 and the communication devices 200 may transmit and receive data using protocols for IoT established by the Open Mobile Alliance (OMA), such as LwM2M (Lightweight M2M), MQTT (Message Queue Telemetry Transport), and CoAP (Constrained Application Protocol). The communication unit 120 may transmit and receive various data using a communication bearer established between the distribution server 100 and each communication device 200.

[0039] The input / output unit 130 may include an input device for inputting various operations to the distribution server 100, and an output device for outputting processing results processed by the distribution server 100. The input device includes, for example, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (for inputting operations via images), and a microphone (for inputting operations via voice). The output device outputs processing results processed by the control unit 110, and includes, for example, a touch panel, a speaker, etc. The input device and the output device may be installed in a centralized monitoring center (not shown) for remotely monitoring the communication device 200, and may receive operations from a monitor (administrator) and output various information to the monitor.

[0040] The distribution server 100 may include an acquisition unit 111, a setting unit 112, and a distribution unit 113 as functions realized by the control unit 110. The acquisition unit 111 may acquire, from a communication device 200 to which update software is to be distributed, identification information (cell ID) that identifies a base station 300 to which the communication device 200 is connected. Note that the acquisition unit 111 may acquire the identification information via a management server 101 that communicates with the communication device 200 using a predetermined protocol.

[0041] The setting unit 112 may obtain the number of communication devices 200 connected to each of the plurality of base stations 300 based on the identification information obtained from the plurality of communication devices 200, and may set the ratio of the communication devices 200 to each base station 300 to which update software will be distributed in one distribution based on the number.

[0042] The distribution unit 113 may distribute update software to each of the plurality of base stations 300, with the number of units to be distributed for each of the plurality of base stations 300 set based on the ratio. Note that the distribution unit 113 may distribute update software to each of the plurality of base stations 300, with the number of units to be distributed for each of the plurality of base stations 300 acquired based on the ratio and the upper limit number of units that can be distributed in one distribution.

[0043] As described above, the acquisition unit 111 may acquire the cell ID from the communication device 200 at predetermined intervals. In this case, the setting unit 112 may update the ratio at predetermined intervals. Furthermore, the distribution unit 113 may distribute update software to each of the plurality of base stations 300, with the number of distributions set according to the ratio updated by the setting unit 112.

[0044] <Communication Device> Next, a communication device 200 according to an embodiment of the present invention will be described. The communication device 200 may include a control unit 210, a communication unit 220, an input / output unit 230, and a storage unit 270. The control unit 210 and the communication unit 220 constituting the communication device 200 may be software or modules that perform processing by a processor executing a program stored in a memory. Alternatively, the control unit 210 and the communication unit 220 constituting the communication device 200 may be hardware such as a circuit or a chip.

[0045] The communication unit 220 communicates with the base station 300 using a predetermined communication method, and may send and receive various data with the distribution server 100 and the management server 101 via the mobile communication network 500.For example, the communication unit 220 may be compatible with NB-IoT, Category M1, LTE, etc. as the predetermined communication method.

[0046] The control unit 210 may be composed of, for example, an MPU (Micro Processing Unit) or the like, and may perform processing to operate the communication device 200 in compliance with NB-IoT, Category M1, etc. by executing a program stored in the memory unit 270.

[0047] Furthermore, the control unit 210 may perform various processes for connecting to the mobile communication network 500 (registering with the core network 50) and for disconnecting from the mobile communication network 500. Furthermore, the control unit 210 may download FOTA update software via the communication unit 220. Furthermore, the control unit 210 may update the firmware of its own device using the downloaded update software.

[0048] The storage unit 270 stores various programs and various data required for the operation of the communication device 200. The storage unit 270 may include, for example, a semiconductor memory (magnetic memory, flash memory, etc.). The storage unit 270 may also include a memory (RAM (Random Access Memory), ROM (Read Only Memory), etc.) that provides a working area for the control unit 210. The storage unit 270 may store base station identification information (cell ID) 271 that uniquely identifies the base station 300 to which the device itself is connected.

[0049] The input / output unit 230 is an interface with an external device such as a sensor, and may include, for example, a U-bus interface, a UART (Universal Asynchronous Receiver / Transmitter) interface, an SPI (Serial Peripheral Interface) interface, an I2C interface, etc. The communication device 200 may transmit data detected by a sensor connected via the input / output unit 230 to the management server 101, etc.

[0050] <Distribution process of software updates> The process of distributing update software according to one embodiment of the present invention will be described with reference to Fig. 4. Fig. 4 is a sequence diagram between distribution server 100 and communication device 200, which corresponds to the execution of the process of distributing update software (FOTA). Note that the description here focuses on communication devices 200Aa and 200Ba connected to base stations 300A and 300B, respectively.

[0051] Upon receiving a request from the management server 101, the communication devices 200Aa and 200Ba may transmit identification information (cell ID) of the base station to which the communication devices 200Aa and 200Ba are connected via the management server 101 (steps S11 and S12). The distribution server 100 may acquire, from the communication devices 200Aa and 200Ba to which the update software is to be distributed, identification information that identifies the base stations 300A and 300B to which the communication devices 200Aa and 200Ba are connected (step S13). As a result, the table TB10 in FIG. 2(a) may be acquired.

[0052] The distribution server 100 may obtain the number of communication devices connected to each of the plurality of base stations 300A and 300B based on the identification information obtained from the plurality of communication devices 200Aa and 200Ba (step S14). As a result, the table TB11 of FIG. 2(b) may be obtained. Furthermore, the distribution server 100 may set the ratio of the communication devices 200 to which update software is distributed in one distribution for each base station 300 based on the obtained numbers (step S15). As a result, the ratio of FIG. 2(c) may be set.

[0053] Then, distribution server 100 may distribute update software to each of the plurality of base stations 300A, 300B, with the number of distributions for each of the plurality of base stations set based on the ratio (steps S16, S17, S18). The distribution of update software may be performed by transmitting a FOTA command (distribution notification) indicating that FOTA will be executed to communication device 200. Note that the FOTA command may include information (URL) regarding the download destination of the update software.

[0054] The communication device 200 may download update software and update its own firmware using the downloaded update software (steps S19 and S20). Furthermore, when the firmware update is complete, the communication device 200 may transmit a notification indicating that FOTA has been completed to the distribution server 100 (steps S21 and S22). Thereafter, a FOTA command may be transmitted to the communication devices 200 to which update software has not yet been distributed in the first distribution, in a number determined by a ratio set in each base station 300 (steps S23 and S24).

[0055] While the present invention has been described based on the drawings and examples, it should be noted that those skilled in the art would readily be able to make various modifications and alterations based on the present disclosure. Therefore, it should be noted that these modifications and alterations are within the scope of the present invention. For example, the functions included in each means, step, etc. may be rearranged so as not to cause logical inconsistencies, and multiple means, steps, etc. may be combined or divided into one. Furthermore, the configurations described in the above embodiments may be appropriately combined. For example, each component described as being included in the distribution server 100 may be realized in a distributed manner by multiple servers. Furthermore, processing described as a function of the distribution server 100 may be performed by the communication device 200. Conversely, processing described as being performed by the communication device 200 may be performed by the distribution server 100 or the management server 101.

[0056] For example, in the above description, a cell ID is used as an example of identification information of a base station. However, an E-UTRAN Cell Global Identifier (ECGI) may be used as identification information of a base station. Furthermore, in addition to the cell ID, information on the communication carrier that provides the base station 300 and information on the installation area of ​​the base station 300 may be used to identify the base station 300.

[0057] Furthermore, the ratio of the number of base stations to which the base stations are to be distributed may be changed according to a predetermined weighting. For example, the control unit 210 of each communication device 200 may acquire communication quality information regarding the communication quality of the device itself and transmit the information to the management server 101 via the communication unit 220. The communication quality information may be, for example, RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality), RSSI (Received Signal Strength Indicator), SINR (Signal to Interference plus Noise Ratio), etc., but is not limited to these. The control unit 210 of the communication device 200 may measure the communication quality information based on the state of wireless communication, such as the reception strength of radio waves received by the communication unit 220. The distribution server 100 may then reduce the ratio of the number of base stations to which the base stations are to be distributed for base stations 300 with poor communication quality. This reduces the probability of FOTA failure.

[0058] Furthermore, the ratio of the number of delivery units may be changed depending on the installation area of ​​the base station 300. For example, a higher ratio may be set for a base station 300 installed in an area where priority delivery is required. This allows for more flexible implementation of FOTA.

[0059] Each functional unit of the distribution server 100 or the communication device 200 may be realized by a logic circuit (hardware) formed on an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or a dedicated circuit, or may be realized by software using a CPU (Central Processing Unit). Furthermore, each functional unit may be realized by one or more integrated circuits, and the functions of multiple functional units may be realized by a single integrated circuit.

[0060] The programs of the embodiments of the present disclosure may be provided in a state stored in a storage medium readable by an information processing device. The storage medium may store the programs in a "non-transitory tangible medium." The programs include, for example, software programs and information processing device programs. When the functional units of the distribution server 100 as an information processing device are realized by software, the distribution server 100 functions as the acquisition unit 111, the setting unit 112, and the distribution unit 113 by the processor executing the programs loaded on the memory.

[0061] The storage medium may, where appropriate, include one or more semiconductor-based or other integrated circuits (ICs) (e.g., field programmable gate arrays (FPGAs), application specific ICs (ASICs), etc.), hard disk drives (HDDs), hybrid hard drives (HHDs), optical disks, optical disk drives (ODDs), magneto-optical disks, magneto-optical drives, floppy diskettes, floppy disk drives (FDDs), magnetic tapes, solid state drives (SSDs), RAM drives, secure digital cards or drives, any other suitable storage media, or any suitable combination of two or more of these. The storage medium may, where appropriate, be volatile, non-volatile, or a combination of volatile and non-volatile.

[0062] Furthermore, each embodiment of the present disclosure may be realized in the form of a data signal embedded in a carrier wave, in which a program is embodied by electronic transmission. Note that the program of the present disclosure may be implemented using, for example, a scripting language such as JavaScript (registered trademark) or Python, or the C language, Go language, Swift (registered trademark), Koltin (registered trademark), or Java (registered trademark).

[0063] According to each aspect of the present disclosure described above, by providing technology related to the monitoring and maintenance of IoT devices for network technologies beyond 5G, it is possible to contribute to the achievement of Goal 9 of the Sustainable Development Goals (SDGs), which is to "build resilient infrastructure, promote inclusive and sustainable industrialization, and foster innovation." [Explanation of symbols]

[0064] 100 Distribution server (information processing device) 110 control section 111 Acquisition Department 112 Setting section 113 Distribution Department 120 Communications Department 130 Input / output section 170 Storage section 101 Management Server 200 Communication devices (IoT devices) 210 Control Unit 220 Communications Department 230 Input / output section 270 Storage section 300 base stations 500 Mobile Communication Network 50 Core Network 600 Distribution System

Claims

1. A distribution server that distributes update software to communication devices connected to a base station, an acquisition unit that acquires, from a communication device to which the update software is to be distributed, identification information that identifies a base station to which the communication device is connected; a setting unit that acquires the number of the communication devices connected to each of a plurality of base stations based on the identification information acquired from the plurality of communication devices, and sets a ratio among the plurality of base stations to which the update software is to be distributed in one distribution based on the acquired number of the communication devices; a distribution unit that distributes the update software to each of the plurality of base stations for each distribution, the number of distributions being set based on the ratio; A distribution server comprising:

2. the acquiring unit acquires the identification information via a management server that communicates with the communication device using a predetermined protocol; The distribution server according to claim 1 .

3. the acquiring unit acquires the identification information from the communication device at predetermined intervals; The setting unit updates the ratio at the predetermined intervals, the distribution unit distributes the update software to each of the plurality of base stations by the number of distributions set in accordance with the ratio updated by the setting unit. The distribution server according to claim 1 .

4. the distribution unit distributes the update software to each of the plurality of base stations by the number of base stations to be distributed to each of the plurality of base stations, the number being acquired based on the upper limit number of base stations to which the distribution server can distribute the update software in one distribution and the ratio. The distribution server according to claim 1 .

5. The distribution unit distributes the update software using a communication method according to Category M1 among communication methods conforming to LPWA (Low Power Wide Area). The distribution server according to claim 1 .

6. A method for controlling a distribution server that distributes update software to a communication device connected to a base station, comprising: The computer acquiring, from a communication device to which the update software is to be distributed, identification information for identifying a base station to which the communication device is connected; acquiring the number of communication devices connected to each of a plurality of base stations based on the identification information acquired from the plurality of communication devices, and setting a ratio among the plurality of base stations to which the update software is distributed in one distribution based on the number of communication devices; and distributing the update software to each of the plurality of base stations for each distribution, the number of distributions being set based on the ratio.

7. A method for controlling a distribution server that distributes update software to a communication device connected to a base station, comprising: On the computer, a function of acquiring, from a communication device to which the update software is to be distributed, identification information for identifying a base station to which the communication device is connected; a function of acquiring the number of communication devices connected to each of a plurality of base stations based on the identification information acquired from the plurality of communication devices, and setting a ratio among the plurality of base stations to which the update software is distributed in one distribution based on the acquired number of communication devices; a control program for a distribution server that realizes a function of distributing the update software to each of the plurality of base stations for each distribution, the number of distributions being set based on the ratio.

Images