IoT system and data collection control method

Abstract

The present application provides an IoT system characterized by comprising: a communication device provided with an identification module that controls a communication element, and that communicates with a cloud server; an asset connected to the communication device; and a control server that manages settings of communication between the communication device and the cloud server, the control server managing a relationship between the identification module and the communication device and a relationship between the communication device and the asset, and setting communication between the communication device and the cloud server in order to forward information from the asset to the cloud server.

Description

[0001] This application claims priority to Japanese application No. 2020-181098, filed on October 29, 2020, the contents of which are incorporated herein by reference. Technical Field

[0002] This invention relates to an IoT system for controlling the collection of data from assets (equipment). Background Technology

[0003] Centered on manufacturers who produce and deploy assets globally, there is a demand for collecting and analyzing data from assets used worldwide, in connection with improving business efficiency and creating business opportunities. Furthermore, the effective utilization of data collected from assets is expected to advance further through the development of high-capacity, high-speed data communication technologies.

[0004] As background technology in this field, there is Japanese Patent Application Publication No. 2015-87852 (Patent Document 1). Japanese Patent Application Publication No. 2015-87852 discloses an industrial equipment management system, which includes a terminal and an industrial equipment management device. The terminal has a transmitting unit that transmits user management information related to the managed industrial equipment and set according to input from a user. The industrial equipment management device has a receiving unit that receives the user management information transmitted by the transmitting unit; and a storage unit that stores the user management information received by the receiving unit in association with individual identification information of the managed industrial equipment. Summary of the Invention

[0005] The problem that the invention aims to solve

[0006] To build a system for collecting IoT data from assets worldwide, the following steps are required: selecting communication lines and devices in various locations; associating communication devices with communication lines; allocating equipment assets; acquiring and accumulating IoT data; and developing corresponding applications. In these processes, multiple factors are involved, including communication line parameters, communication device information, and asset information. In particular, communication line parameters (frequency band, latency, and other communication requirements) are controlled by setting the SIM card installed in the communication device. Therefore, in addition to the communication device, comprehensive SIM card management is also necessary. The goal is to find a unified service platform that controls these factors and provides a one-stop solution for everything from communication line selection to IoT data collection.

[0007] Methods for solving problems

[0008] The following is a representative example of the invention disclosed in this application. Specifically, an IoT system is characterized by comprising: a communication device having an identification module installed to control communication elements and communicating with a cloud server; an asset connected to the communication device; and a control server that manages the settings for communication between the communication device and the cloud server, the control server managing the relationship between the identification module and the communication device and the relationship between the communication device and the asset, and setting up communication between the communication device and the cloud server for forwarding information from the asset to the cloud server.

[0009] Invention Effects

[0010] According to one aspect of the present invention, it is possible to uniformly control the elements required for an IoT system. Other issues, structures, and effects beyond those described above become clear through the following description of embodiments. Attached Figure Description

[0011] Figure 1 This is a conceptual diagram representing a data circulation service platform.

[0012] Figure 2 This is a diagram representing the overall system structure of the data circulation service platform.

[0013] Figure 3 This is a block diagram of the control server for the data circulation service platform.

[0014] Figure 4 It is a diagram representing the structure of the master data management database.

[0015] Figure 5 This is a diagram illustrating a structural example of SIM information.

[0016] Figure 6 This is a diagram illustrating a structural example of SIM / device association information.

[0017] Figure 7 This is a diagram illustrating a structural example of device information.

[0018] Figure 8 This is a diagram illustrating a structural example of asset information.

[0019] Figure 9 This is a diagram illustrating a structural example of asset category information.

[0020] Figure 10 This is a diagram illustrating a structural example of equipment / asset association information.

[0021] Figure 11 This is a sequence diagram showing the process from line contract to line connection.

[0022] Figure 12This is a timing diagram of the process when replacing equipment in a line connection.

[0023] Figure 13 This is a sequence diagram of the toll processing in the line connection.

[0024] Figure 14 This is a sequence diagram of cloud service selection and configuration processing.

[0025] Figure 15 This is a timing diagram for device provisioning.

[0026] Figure 16 It is a timeline diagram of IoT data collection, processing, and management.

[0027] Figure 17 This is a flowchart of public event control and record management processes.

[0028] Figure 18 This is a flowchart of the line management process.

[0029] Figure 19 This is a flowchart of the line management process.

[0030] Figure 20 This is a flowchart of the cloud service selection and configuration process.

[0031] Figure 21 This is a flowchart of the equipment pre-configuration process.

[0032] Figure 22 It is a flowchart of IoT data collection, processing, and management.

[0033] Figure 23 This is a diagram representing multi-tenant access to the server using a communication adapter.

[0034] Figure 24 This is a diagram representing the distribution of asset-related configuration files by the Device Manager server.

[0035] Figure 25 This is an example of a screen showing an overview of the devices.

[0036] Figure 26 This is an example image showing an overview of assets. Detailed Implementation

[0037] Figure 1 This is a conceptual diagram representing a data circulation service platform 100. Figure 2 This is a diagram showing the overall system structure of the data circulation service platform 100.

[0038] The data circulation service platform 100 of this embodiment is a platform that can selectively utilize the communication operator IoT platform 110 provided by the communication operator (Carrier), the cloud service 120 provided by the cloud operator, and the device manager server 130 installed on the communication device 150 for distributing device managers, to provide a one-stop service from the connection from the communication device 150 to the communication operator's line to the collection of data from the asset 160, the accumulation of the collected data, and the visualization.

[0039] The data circulation service platform 100 includes a data circulation service platform control server 101, a master data management RDB server 104, a device firmware / configuration storage server 106, and an IoT data pool server 108. The servers 101, 104, 106, and 108 of the data circulation service platform 100 are interconnected, for example, via a LAN.

[0040] The data circulation service platform control server 101 controls the actions of the other servers 104, 106, and 108 of the data circulation service platform 100. For the structure of the data circulation service platform control server 101, refer to... Figure 3 To be described later.

[0041] The master data management RDB server 104 manages and stores the master management database 105, which is configured to enable the data circulation service platform 100 to function. For the data stored in the master management database 105, refer to... Figure 4 To be described later.

[0042] Device firmware / configuration storage server 106 manages device firmware / configuration database 107 used to store settings for communication device 150 (e.g., communication configuration files, device manager, etc.).

[0043] IoT data pool server 108 collects data from asset 160 and stores it in IoT data pool 109.

[0044] Enterprises access the data circulation service platform 100 through Web GUI (Graphical User Interface) 211 and API (Application Programming Interface) 212.

[0045] The data circulation service platform 100 connects to a communication operator's IoT platform 110 provided by multiple vendors and cloud services 120 provided by multiple vendors. For each cloud service, the cloud service 120 provides multiple services, including a device GW service for receiving data sent by the communication device 150, a data processing service for processing or uncompressing data, and a data stream service for real-time data collection, buffering, and transmission. Since the service methods, connection methods, and data input / output methods of the multiple cloud services 120 differ, the control is configured to enable data transmission and reception suitable for the used cloud service 120 via the communication adapter 227 described later (see reference). Figure 3 The telecommunications operator's IoT platform 110 and cloud service 120 are connected to the communication device 150 via a network (e.g., MNO network, Internet). The communication device 150 is typically connected to the Internet via a public wireless communication network (e.g., 5G line network). The communication device 150 connects to the asset 160 and collects necessary data from the asset 160. The communication device 150 and the asset 160 are typically connected via wired (MODBUS, EtherCAT, etc.), but can also be connected wirelessly (WiFi, Bluetooth, etc.). Alternatively, the communication device 150 and the asset 160 can be connected in a 1:N structure instead of a 1:1 connection. Data sent from the asset 160 is collected and processed in the server of the cloud service 120 via the network and then stored in the IoT data pool 109. The data flow service platform control server 101 analyzes the stored data, estimates the operating status of the asset 160, and determines maintenance information.

[0046] Asset 160 is a device (automobile, IT equipment, construction machinery, etc.) that becomes a source of data collected by the data circulation service platform 100.

[0047] In addition, the data circulation service platform 100 connects to the device manager server 130 in order to provide device managers from multiple vendors to the communication device 150.

[0048] This structure enables easy and efficient collaboration between the steps of line connection, device pre-configuration, and IoT data acquisition of the communication device 150, through the exchange of data with the communication operator's IoT platform 110, cloud service 120, and device manager server 130, and through the collaboration of device data, SIM data (configuration files), and asset data, thereby providing a one-stop service.

[0049] exist Figure 2 In this process, the device firmware and configuration files are maintained by the device firmware / configuration storage server 106 within the data circulation service platform 100, but may also be maintained as described later ( Figure 15 , Figure 21 , Figure 24As shown in the figure, it is maintained by Device Manager Server 130.

[0050] Figure 3 This is a block diagram of the data circulation service platform control server 101. Figure 4 This is a diagram showing the structure of the main management database 105.

[0051] The data circulation service platform control server 101 is composed of a computer having a processor 201, a memory 202, a non-volatile storage device 203, an input / output device 204, and an input / output circuit interface 205.

[0052] The processor 201 executes a program stored in the memory 202. Specifically, by executing the program, the processor 201 implements the following functions: I / F function 210, public event control / history management function 220, tenant / user management function 221, communication operator IoT platform access function 223, cloud service selection and setting function 225, cloud service access function 226, device provisioning function 228, device manager access function 229, IoT data collection / processing / management function 231, and IoT data via cloud service function 232. Alternatively, a portion of the processing performed by the processor 201 may be executed by other forms of computing devices (e.g., hardware-based FPGAs (Field Programmable Gate Arrays) or ASICs (Application Specific Integrated Circuits)).

[0053] The memory 202 includes ROM as a non-volatile storage device and RAM as a volatile storage device. ROM stores immutable programs (such as BIOS). RAM is a high-speed and volatile storage device such as DRAM (Dynamic Random Access Memory), which temporarily stores programs executed by the processor 201 and the data used during program execution.

[0054] The non-volatile storage device 203 is a high-capacity storage device such as a magnetic storage device (HDD) or a flash memory (SSD), which stores the program executed by the processor 201 and the data used when executing the program. That is, the program is read from the non-volatile storage device 203, loaded into the memory 202, and executed by the processor 201.

[0055] Input / output device 204 is an interface device that connects to input devices such as keyboards and mice, output devices such as displays and printers, accepts input from the operator, and outputs the execution results of the program in a form that the operator can visually recognize.

[0056] The input / output circuit interface 205 is a network interface device that controls communication with other devices (such as the master data management RDB server 104, the device firmware / configuration storage server 106, the IoT data pool server 108, etc.) via a communication network according to a predetermined protocol.

[0057] The program executed by the processor 201 is provided to the data circulation service platform control server 101 via a removable medium (CD-ROM, flash memory, etc.) or a network, and stored in a non-volatile storage device 203, which is a non-transitory storage medium. Therefore, the data circulation service platform control server 101 can have an interface for reading data from the removable medium.

[0058] The data circulation service platform control server 101 is a computer system that is physically located on one computer or is logically or physically composed of multiple computers. Each functional block can work on the same computer in different threads, or it can work on a virtual computer constructed on multiple physical computer resources.

[0059] Next, refer to Figure 3 and Figure 4 This section provides a summary of the functional blocks and data installed in the data circulation service platform control server 101.

[0060] The I / F function 210 includes: a GUI 211 provided by a web server; an API 212 capable of inputting and outputting data according to predetermined rules; and a DB access unit 213 that controls the reading and writing of data in the main management database 105, the device firmware / configuration database 107, and the IoT data pool 109. Through the I / F function 210, users as tenants and systems operated by tenants can access the data circulation service platform 100.

[0061] The public event control / record management function 220, referring to the "public event control / record management function" data 300, controls and manages public events in various functional blocks of the data circulation service platform 100. Specifically, the public event control / record management function 220, referring to event management information 301, manages the progress of events or processes generated in the data circulation service platform 100, and records the history (log) of events generated in the data circulation service platform 100 in the history information 302. As needed, the "public event control / record management function" data 300 can be accessed from other functional blocks 221-233.

[0062] The tenant / user management function 221, referring to the "tenant / user management function" and utilizing data 310, manages the tenants and users of the data circulation service platform 100. Specifically, the tenant / user management function 221, referring to the tenant / user group / user information 311, associates tenants, user groups within tenants, and users within tenants, and manages the attributes and permissions of tenants, user groups, and users.

[0063] The line management function 222, referring to the "line management function" data 320, controls access to the communication operator's IoT platform 110 provided by the communication operator. Specifically, the line management function 222 prompts the tenant with available communication operator service plans from the service plan information 322, and registers the SIM information 324 corresponding to the communication requirements (communication operator, service plan, etc.) selected by the tenant (refer to...). Figure 5 ), register SIM / device association information 325 corresponding to SIM information 324 (refer to Figure 6 Additionally, the line management function 222 selects the configuration file information 323 corresponding to the selected service plan and provides it to the communication device 150.

[0064] The telecommunications operator's IoT platform access function 223 operates in conjunction with the line management function 222. Referring to the line management function, it utilizes data 320. The line management function 222 uses a communication adapter 224 to control communication from the communication device 150 to the telecommunications operator's IoT platform 110. Specifically, the telecommunications operator's IoT platform access function 223 controls communication from the communication device 150 to the cloud service 120, referring to SIM information 324 and SIM / device association information 325. Furthermore, the telecommunications operator's IoT platform access function 223 records billing information 321 based on the communication from the communication device 150 to the telecommunications operator's IoT platform 110.

[0065] The communication adapter 224 is a file that defines information for controlling communication from the communication device 150 to the communication operator's IoT platform 110, and is used by the data circulation service platform 100 to control communication to the communication operator's IoT platform 110.

[0066] The cloud service selection and setting function 225, referring to the "cloud service selection and setting function" data 330, assists the cloud operator in selecting the cloud service 120 provided. Specifically, the cloud service selection and setting function 225 prompts the tenant with the available cloud operator service plans from the cloud service selection information 331, registers the cloud service setting information 332 corresponding to the cloud operator and service plan selected by the tenant, and registers the device information 333 corresponding to the cloud service setting information 332 (refer to...). Figure 7 ).

[0067] The cloud service access function 226 works in conjunction with the cloud service selection and setting function 225. Referring to the "cloud service selection and setting function," it uses data 330 and communication adapter 227 to control access from the communication device 150 to the cloud service 120. Specifically, the cloud service access function 226 controls access from the communication device 150 to the cloud service 120 according to cloud service setting information 332 and device information 333.

[0068] The communication adapter 227 is a file that defines information for controlling communication from the communication device 150 to the cloud service 120, and is used by the data circulation service platform 100 to control communication to the cloud service 120.

[0069] The equipment pre-configuration function 228, referring to the "equipment pre-configuration function," utilizes data 340 to control the collection of data from assets 160. Specifically, the equipment pre-configuration function 228 obtains data from asset information 343 (referring to...). Figure 8 ) and asset class information 344 (refer to Figure 9 Obtain the attributes of asset 160 from the data source, and refer to the device / asset association information 345 (refer to...). Figure 10 ), and identify the communication device 150 connected to asset 160.

[0070] Device Manager Access Function 229 operates in conjunction with Device Provisioning Function 228. Referring to the Device Provisioning Function, using data 340 and communication adapter 230, it controls the distribution of the Device Manager to the communication device 150. Specifically, Device Manager Access Function 229, based on Device Manager Selection Information 341, determines the Device Manager Server 130 to distribute the selected Device Manager, and records the distributed Device Manager to the communication device 150 in Device Distribution File Management Information 342.

[0071] The communication adapter 230 is a file that defines information for controlling access from the communication device 150 to the device manager server 130, and is used by the data circulation service platform 100 to control communication to the device manager server 130.

[0072] The IoT data collection / processing / management function 231, referring to the "IoT data collection / processing / management function," utilizes data 350 to manage the data collected from asset 160. Specifically, the IoT data collection / processing / management function 231 processes the information from asset 160 collected by cloud service 120 from communication device 150 and stores it in IoT data pool 109. Furthermore, the IoT data collection / processing / management function 231, referring to processing information 351, processes the information collected from asset 160 (e.g., transforming data used internally into human-understandable values), determines whether to issue an alarm based on alarm threshold setting information 352, and notifies the alarm based on alarm notification destination information 353.

[0073] It operates via a link between the cloud service IoT data function 232 and the IoT data collection / processing / management function 231, and uses the IoT data receiving adapter 233 to control the data flow service platform control server 101 to receive data from the cloud service 120.

[0074] The IoT data receiver adapter 233 is a file that defines information for controlling access from the data circulation service platform control server 101 to the cloud service 120, and is used by the data circulation service platform 100 to control communication to the cloud service 120.

[0075] in addition, Figure 4 The data shown is primarily categorized according to the functions used, but other functional blocks can also be used. Furthermore, each data point corresponds to a tenant, user group, and user, containing these data items, or each data point is associated with tenant / user group / user information 311. Additionally, access permissions are set for each data item, for example, specifying whether access is limited to platform administrators or shared by both platform administrators and tenant users.

[0076] Figure 5 This is a diagram illustrating a structural example of SIM information 324.

[0077] SIM information 324 is a table that records information about the SIM (Subscriber Identity Module) installed in the communication device 150, including SIM ID 3241, communication operator 3242, tenant ID 3243, configuration file 3244, registered user ID 3245, and registration date and time 3246. In addition to the data items shown in the diagram, SIM information 324 may also include user group ID, SIM status, updated user ID, and update date and time.

[0078] SIM ID 3241 is a unique identifier assigned to the SIM, such as using ICCID (Integrated Circuit Card ID). Communication Operator 3242 is the name of the communication operator providing the communication operator IoT platform 110. Identification information based on a combination of MCC (Mobile Country Code) and MNC (Mobile Network Code) can also be recorded in Communication Operator 3242. Tenant ID 3243 is a unique identifier assigned to the tenant using the SIM. Profile 3244 is a communication profile configured on the communication device 150 with the SIM installed (or a pointer specifying the communication profile). Registered User ID 3245 is the identifier of the user who registered the SIM. Registration Date and Time 3246 is the date and time the SIM was registered. As shown, Registration Date and Time 3246 can be an operating system-specific time or a date and time in a human-understandable format.

[0079] Figure 6 This is a diagram illustrating a structural example of SIM / device association information 325.

[0080] SIM / device association information 325 is a table recording the correspondence between the SIM and the communication device 150, including SIMID 3251, device ID 3252, registered user ID 3253, and registration date and time 3254. In addition to the data items shown in the figure, SIM / device association information 325 may also include updated user ID, update date and time, etc.

[0081] SIM ID 3251 is a unique identifier assigned to the SIM card and can use the same value as SIMID 3241 in SIM information 324. Device ID 3252 is a unique identifier assigned to the communication device 150 and can use the same value as Device ID 3331 in device information 333. Registered User ID 3253 is the identifier of the user who registered this relationship. Registration Date and Time 3254 is the date and time of registration for this relationship. As shown in the figure, the registration date and time 3254 can be an operating system-specific time or a date and time in a human-understandable format.

[0082] If the correspondence between the SIM and the communication device 150 remains unchanged, the SIM / device association information 325 can be omitted, and management can be carried out by merging the SIM information 324 and the device information 333 into a single data set.

[0083] Figure 7 This is a diagram representing a structural example of device information 333.

[0084] Device information 333 is a table that records information about communication device 150, including device ID 3331, tenant ID 3332, device group 3333, device name 3334, device authentication information 3335, registered user ID 3336, and registration date and time 3337. In addition to the data items shown in the diagram, device information 333 may also include processing status, etc. Furthermore, it can record a mapping between the internal management identification information of the data flow service platform control server 101 and the inherent identification information of communication device 150, such as the manufacturing number. It can also record information for configuring the gateway within communication device 150.

[0085] Device ID 3331 is a unique identifier assigned to communication device 150 and can use IMEI (International Mobile Equipment Identity). Tenant ID 3332 is a unique identifier assigned to the tenant using communication device 150 and can use the same value as Tenant ID 3243 in SIM information 324. Device group 3333 is the identifier for a group of multiple communication devices 150, assigned according to the management of communication devices 150. Device name 3334 is the name of communication device 150. IMEI (International Mobile Equipment Identity) can also be recorded in device name 3334. Device authentication information 3335 is information used to authenticate communication device 150 (or a pointer specifying the device authentication information). Registered user ID 3336 is the identifier for the user who registered communication device 150. Registration date and time 3337 is the date and time of registration of communication device 150. As shown in the figure, registration date and time 3337 can be either an operating system-specific time or a date and time in a human-understandable form.

[0086] Figure 8 This is a diagram representing a structural example of asset information 343.

[0087] Asset Information 343 is a table that records information about Asset 160, including Asset ID 3431, Asset Group 3432, Asset Serial Number 3433, Asset Name 3434, and Asset Category 3435. In addition to the data items shown in the diagram, Asset Information 343 may also include Registered User ID, Registration Date and Time, Updated User ID, Update Date and Time, etc.

[0088] Asset ID 3431 is the unique identification information assigned to asset 160. Asset group 3432 is the identification information for a group consisting of multiple assets 160, assigned according to the management situation of asset 160. Asset serial number 3433 is the manufacturing number assigned to asset 160. Asset name 3434 is the name of asset 160. Asset category 3435 is the classification of asset 160 as defined in asset category information 344.

[0089] Figure 9 This is a diagram representing a structural example of asset category information 344.

[0090] Asset category information 344 is a table that defines the classification of asset 160, including asset category ID 3441, tenant ID 3442, and asset attribute 3443. In addition to the data items shown in the diagram, asset category information 344 may also include registered user ID, registration date and time, updated user ID, and update date and time.

[0091] Asset category ID 3441 is a unique identifier assigned to the asset category. Tenant ID 3442 is a unique identifier assigned to the tenant using asset 160, and can use the same value as tenant ID 3243 in SIM information 324. Asset attribute 3443 is detailed information about asset 160 (or a pointer to a file that records information about the asset category).

[0092] Figure 10 This is a diagram illustrating a structural example of equipment / asset association information 345.

[0093] Device / asset association information 345 is a table that records the correspondence between communication device 150 and asset 160, including device ID 3451, asset ID 3452, registered user ID 3453, and registration date and time 3454. In addition to the data items shown in the diagram, device / asset association information 345 may also include updated user ID, update date and time, etc.

[0094] Device ID 3451 is a unique identifier assigned to communication device 150 and can use the same value as Device ID 3331 in device information 333. Asset ID 3452 is a unique identifier assigned to asset 160 and can use the same value as Asset ID 3431 in asset information 343. Registered User ID 3453 is the identifier of the user who registered the communication device 150. Registration Date and Time 3454 is the date and time when the communication device 150 was registered. As shown in the figure, the registration date and time 3454 can be either an operating system-specific time or a date and time in a human-understandable format.

[0095] exist Figures 5 to 10The information is presented in tabular form, but this information can also be composed of data structures other than tables (e.g., lists, queues, etc.), independent of the storage area structure. Furthermore, the structure of each piece of information is just one example; the information can also be stored separately or in combination.

[0096] Figure 11 It is a sequence diagram showing the processing from line contract to line connection.

[0097] The platform administrator inputs tenant information, user group information, and user information from the Web GUI 211 or API 212. The input information is sent from the Web GUI 211 or API 212 to the tenant / user management function 221 (401) via the public event control / history management function 220. The tenant / user management function 221 registers the input tenant information, user group information, and user information in the tenant / user group / user information 311 (402) and sends a registration completion response to the Web GUI 211 or API 212 (403).

[0098] Next, the platform administrator registers the tenant information and contract information with the telecommunications operator's IoT platform 110 and generates a service plan (404).

[0099] Next, the platform administrator inputs the service plan from Web GUI 211 or API 212. The input information is sent from Web GUI 211 or API 212 to Line Management Function 222 (405) via Public Event Control / Record Management Function 220. Line Management Function 222 registers the input service plan in Service Plan Information 322 (406) and sends a registration completion response to Web GUI 211 or API 212 (407).

[0100] Next, the platform administrator orders SIMs from the SIM supplier. At the time the SIM and SIM information are manufactured, the SIM is registered with the telecommunications operator's IoT platform 110 (408).

[0101] Next, the platform administrator refers to the service plan information 322 (409) from the Web GUI 211 or API 212 and enters the SIM information. The entered SIM information is sent from the Web GUI 211 or API 212 to the line management function 222 (410) via the public event control / history management function 220. The line management function 222 registers the entered information in the SIM information 324 (411) and sends a registration completion response to the Web GUI 211 or API 212 (412).

[0102] Next, when the platform administrator sends the SIM and SIM information to the equipment supplier, the SIM is installed in the communication device 150 (413).

[0103] Next, the tenant-side user, referring to SIM information 324 and device information 333 (414) from Web GUI 211 or API 212, enters the device ID. The entered device ID is sent from Web GUI 211 or API 212 to line management function 222 (415) via public event control / history management function 220. Line management function 222 registers the entered device ID in SIM / device association information 325 and device information 333 and updates it (416), and sends an update completion response to Web GUI 211 or API 212 (417).

[0104] Afterwards, the communication device 150 leaves the factory, detects roaming in the communication operator's IoT platform 110, and switches the configuration file (418).

[0105] Next, the communication operator's IoT platform 110 notifies the line management function 222 (419) of the configuration file switching result. The line management function 222 updates the configuration file of the SIM information 324 (420) and sends an update completion response to the WebGUI 211 or API 212 (421).

[0106] Next, the platform-side administrator or tenant-side user inputs the SIM status change from the Web GUI 211 or API 212. The input SIM status is sent from the Web GUI 211 or API 212 to the line management function 222 via the public event control / history management function 220 (422). The line management function 222 sends the SIM status change request to the communication operator IoT platform 110 (423). The communication operator IoT platform 110 notifies the line management function 222 of the result of the SIM status change request (424). The line management function 222 updates the SIM status of the SIM information 324 (425) and sends an update completion response to the Web GUI 211 or API 212 (426).

[0107] Figure 12 This is a timing diagram of the process when replacing equipment during the use of a line.

[0108] In the event that communication equipment 150 needs to be replaced due to malfunction or other reasons during line use, the tenant-side administrator communicates the malfunction of communication equipment 150 to the platform-side administrator. The platform-side administrator inputs information about the communication equipment 150 before and after replacement from the Web GUI 211 or API 212. The input information about the communication equipment 150 is then sent from the Web GUI 211 or API 212 to the line management function 222 (431).

[0109] Line management function 222 requests the communication operator's IoT platform 110 to stop using the SIM card of the previous device (432). Additionally, line management function 222 replaces the SIM information of the previous communication device 150 with the SIM information of the new communication device 150 in SIM information 324, SIM / device association information 325, and device information 333 (433). Then, line management function 222 requests the configuration file of the new device from the communication operator's IoT platform 110 (434).

[0110] Subsequently, the telecommunications operator's IoT platform 110 notifies the line management function 222 (419) of the configuration file switching result. The line management function 222 updates the configuration file of the SIM information 324 (420) and sends an update completion response to the WebGUI 211 or API 212 (421).

[0111] exist Figure 12 The sequence of processing during equipment replacement in line use is shown, but when replacing the SIM installed in communication equipment 150, the same processing as steps 431-434 and 419-421 is performed. That is, before SIM replacement, a request to stop SIM use is made (432), and the SIM information 324 before replacement and the SIM / device association information 325 before replacement are updated with the SIM information 324 after replacement (433). At this time, the device / asset association information 345 is not updated. Afterwards, through the sequence from profile switching request (434) to profile switching result notification (419) and profile update (324), SIM replacement can be carried out while maintaining the relationship between communication equipment 150 and asset 160.

[0112] Figure 13 This is a sequence diagram of the toll processing in the line connection.

[0113] The platform administrator requests the registration of charging information from Web GUI 211 or API 212. The charging information registration request is sent from Web GUI 211 or API 212 to the line management function 222 (441).

[0114] Next, the line management function 222 requests the information required for billing calculation from the communication operator's IoT platform 110 (442). The communication operator's IoT platform 110 responds with information such as traffic volume (443).

[0115] Next, the line management function 222 refers to the SIM information 324, SIM / device association information 325 and device information 333 (444), calculates the charging information (445) by device and tenant, and registers the charging information 321 (446).

[0116] Afterwards, the line management function 222 sends the charging information for tenant-side users and the charging information for platform-side administrators to the Web GUI 211 or API 212 (447, 448).

[0117] Afterwards, the data circulation service platform 100 can create reports and send invoices to tenants.

[0118] Figure 14 This is a sequence diagram of cloud service selection and configuration processing.

[0119] Next, the tenant-side user or platform-side administrator refers to the cloud service selection information 331 (451) from the Web GUI 211 or API 212 and inputs the selected cloud service 120. The input cloud service 120 selection is sent from the Web GUI 211 or API 212 to the cloud service selection setting function 225 (452). The cloud service selection setting function 225 registers the information of the selected cloud in the cloud service selection information 331 (453), refers to the cloud service setting information 332, obtains the items that need to be set for the selection (454), and responds with the obtained items to be set to the Web GUI 211 or API 212 (455).

[0120] Then, the tenant-side user or platform-side administrator creates the necessary settings in the selected cloud service 120 (456), and inputs the created cloud service 120 settings. The input cloud service 120 settings are sent from the Web GUI 211 or API 212 to the cloud service selection and setting function 225 (457). The cloud service selection and setting function 225 uses the cloud service settings to update the cloud service setting information 332 (458) and sends the cloud service settings to the cloud service 120 (459). The cloud service 120 performs the necessary processing and responds to the cloud service selection and setting function 225 with a processing completion response (460). The cloud service selection and setting function 225 responds to the Web GUI 211 or API 212 with a message that the cloud service 120 settings are complete (461).

[0121] Figure 15 This is a timing diagram for the equipment pre-configuration process.

[0122] The tenant-side user inputs the asset category of the object to be provisioned by the device. The input asset category is sent from WebGUI 211 or API 212 to the device provisioning function 228 (471). The device provisioning function 228 registers the input asset category in the asset category information 344 (472) and sends a registration completion response to WebGUI 211 or API 212 (473).

[0123] Next, the tenant-side user refers to asset category information 344 (474) from Web GUI 211 or API 212 and enters the asset information that will become the object of device provisioning. The entered asset information is sent from Web GUI 211 or API 212 to device provisioning function 228 (475). Device provisioning function 228 registers the entered asset information into asset information 343 (476) and sends a registration completion response to Web GUI 211 or API 212 (477).

[0124] Next, the tenant-side user or platform-side administrator refers to the device manager selection information 341 (478) from the Web GUI 211 or API 212 and enters the selected device manager. The entered device manager selection is sent from the Web GUI 211 or API 212 to the device provisioning function 228 (479). The device provisioning function 228 registers the information of the selected device manager in the device manager selection information 341 (480) and sends a registration completion response to the Web GUI 211 or API 212 (481).

[0125] Then, through the settings in Device Manager, you can send information to the device (482).

[0126] Next, the tenant-side user, referring to device information 333 and asset information 343 (483) from Web GUI 211 or API 212, inputs the association between communication device 150 and asset 160. The input association between communication device 150 and asset 160 is sent from Web GUI 211 or API 212 to device provisioning function 228 (484). Device provisioning function 228 registers the association between communication device 150 and asset 160 in device / asset association information 345 (485) and sends a registration completion response to Web GUI 211 or API 212 (486).

[0127] Next, the tenant-side user or platform-side administrator refers to device information 333 (487) from Web GUI 211 or API 212, specifies communication device 150, and requests firmware registration. The requested firmware is sent from Web GUI 211 or API 212 to device provisioning function 228 and registered in device distribution file management information 342 (488). Afterwards, device provisioning function 228 registers the firmware in device manager server 130 corresponding to the device ID of the specified communication device 150 (489) and responds to Web GUI 211 or API 212 with registration completion (490).

[0128] Next, the tenant-side user, referring to asset information 343 and asset category information 344 (491) from Web GUI 211 or API 212, specifies asset information and requests registration of the configuration file. The requested configuration file is sent from Web GUI 211 or API 212 to the device provisioning function 228. The device provisioning function 228, referring to device / asset association information 345, searches for the communication device 150 corresponding to the specified asset 160 (492), and for the found communication device 150, registers the configuration file to the device distribution file management information 342 (493). Afterwards, the device provisioning function 228 registers the configuration file in the device manager server 130 corresponding to the device ID of the found communication device 150 (494), and responds to Web GUI 211 or API 212 with a registration completion response (495).

[0129] Thus, if the configuration file is configured in the memory corresponding to the device ID, and the URL for retrieving the configuration file is notified to the communication device 150, then the communication device 150 is in a ready environment to download the firmware and configuration file.

[0130] Figure 16 It is a timeline diagram of IoT data collection, processing, and management.

[0131] The tenant-side user inputs an IoT data threshold for alarm notification. The input IoT data threshold for alarm notification is sent from GUI 211 or API 212 to IoT data collection / processing / management function 231 (501). IoT data collection / processing / management function 231 stores the sent IoT data threshold for alarm notification in alarm threshold setting information 352 (502) and responds to WebGUI 211 or API 212 to register completion (503).

[0132] Next, the tenant-side user enters the alarm notification destination. The entered alarm notification destination is sent from GUI211 or API212 to IoT data collection / processing / management function 231 (504). IoT data collection / processing / management function 231 stores the sent alarm notification destination in alarm notification destination information 353 (505) and completes the registration response to Web GUI211 or API212 (506).

[0133] After receiving IoT data from the communication device 150, the cloud service 120 processes and sends the IoT data (507) based on the settings, and sends the IoT data to the IoT data collection / processing / management function 231 (508).

[0134] Next, the IoT data collection / processing / management function 231 refers to the processing information 351, processes the IoT data received from the communication device 150 (510), and stores it in the IoT data pool 109 (511). The processing in step 510 may be, for example, changing the unit of temperature, or transforming a value used internally by a computer into a value that can be recognized by a human.

[0135] Next, the IoT data collection / processing / management function 231 refers to the IoT data pool 109, asset information 343 and device information 333, and sends the data for GUI display (e.g., a chart representing the working status of asset 160) to the Web GUI 211 or API 212 (513).

[0136] In addition, Figure 16 In the sequence shown, with an alarm threshold and an alarm notification destination set, after storing one batch of processed IoT data, the alarm threshold setting information 352 (521) is used to determine whether the processed IoT data exceeds the threshold (522). If the IoT data exceeds the threshold, a notification is sent to the notification destination user (523).

[0137] Figure 17 This is a flowchart of the public event control processing and history management processing executed by the data circulation service platform control server 101.

[0138] I / F function 210 enters a waiting state to receive a request (S601). Then, I / F function 210 receives the request (S602).

[0139] The public event control / record management function 220 determines whether a processing request has been received through the I / F function 210 (S603). If a processing request has been received through the I / F function 210, the logic flow corresponding to the received processing request is obtained (S604).

[0140] Subsequently, the public event control / history management function 220 determines whether there is a next process to be executed based on a pre-determined logical flow (S605). If there is no next process to be executed, it returns to step S601 and enters a standby state. On the other hand, if there is a next process to be executed, information indicating the progress of the process is registered in the event management information 301 (S606), the corresponding process is invoked (S607), and the history information 302 is registered (S608). At this time, if the process is executed synchronously with the source process, it waits for the response of the destination process to complete before proceeding to the next step. On the other hand, if the process is executed asynchronously, and the destination process is started, it proceeds to the next step.

[0141] On the other hand, if no processing request is received through I / F function 210, it is determined whether the processing request was sent from another function (S609). If the source of the processing request is another function, the process proceeds to step S604, and the logic flow corresponding to the received processing request is obtained. On the other hand, if the source of the processing request is unclear, an unclear processing request reception error is recorded in the history information 302 (S610).

[0142] Figure 18 and Figure 19 This is a flowchart of the line management process executed by the data circulation service platform control server 101.

[0143] The line management function 222 reads the content of the request or notification (S611). Then, it processes the branch according to the read request content.

[0144] When the request read is an information retrieval request ("Yes" in S612), the line management function 222 obtains the "line management function" utilization data 320, generates prompt data (S613), and returns a response to the retrieved data (S629).

[0145] If the read request is a service plan registration request ("Yes" in S614), the line management function 222 registers the requested service plan to the service plan information 322 (S615) and returns a registration completion response (S629).

[0146] If the read request is a SIM information registration request ("Yes" in S616), the line management function 222 registers the requested SIM information in the SIM information 324 and the configuration file information 323 (S617 and S618) and returns a registration completion response (S629).

[0147] If the read request is a device information registration request ("Yes" in S619), the line management function 222 registers the requested device information in the SIM / device association information 325 and device information 333 (S620, S621) and returns a registration completion response (S629).

[0148] If the read notification is a configuration file switching notification ("Yes" in S622), the line management function 222 updates the configuration file 3244 of the configuration file information 323 and SIM information 324 (S623, S624) and returns an update completion response (S629).

[0149] If the read request is a SIM status change request ("Yes" in S625), the line management function 222 sends a status change request to the communication operator's IoT platform 110 (S626). After receiving the status change result (S627), it updates the SIM status of the SIM information 324 (S628) and returns an update completion response (S629).

[0150] If the read request is a device replacement request ("Yes" in S630), the line management function 222 sends a request to stop the use of the SIM of the device before replacement to the communication operator IoT platform 110 (S631), updates the SIM information 324, SIM / device association information 325 and device information 333 to the information after replacement (S632, S633, S634), sends a request to switch the configuration file of the device after replacement to the communication operator IoT platform 110 (S635), and returns a switch completion response (S629).

[0151] If the read request is a billing information registration request ("Yes" in S636), the line management function 222 requests the information required for billing calculation (e.g., traffic volume) from the communication operator's IoT platform 110 (S637), receives the response of the billing calculation information (S638), refers to SIM information 324, SIM / device association information 325 and device information 333 (S639, S640, S641), calculates the billing by device and by tenant (S642), registers the calculated billing amount to the billing information 321 (S643), and returns the registration completion response (S629).

[0152] If the received request is not a fee information registration request, i.e. does not conform to any of steps S612, S614, S616, S619, S622, S625, S630, or S636, an unclear processing request reception error is recorded in the history information 302 (S644).

[0153] Figure 20This is a flowchart of the cloud service selection and setting process executed by the data circulation service platform control server 101.

[0154] The cloud service selects and sets the function 225 to read the requested content (S651). Then, the branch is processed according to the read request content.

[0155] If the read request is a cloud service selection request ("Yes" in S652), the cloud service selection setting function 225 registers the selected cloud service 120 in the cloud service selection information 331 (S653), generates response data for the items to be set by referring to the cloud service setting information 332 (S654), and returns a response (S659).

[0156] If the read request is a cloud service setting request ("Yes" in S655), the cloud service selection setting function 225 uses the cloud service 120 that requested the setting to update the cloud service setting information 332 (S656), updates the setting of the specified cloud service 120 (S657), receives the setting completion response (S658), and returns the setting completion response (S659).

[0157] If the received request is not a cloud service setting request, i.e. does not conform to any of steps S652 and S655, an unclear processing request receiving error is recorded in the history information 302 (S660).

[0158] Figure 21 This is a flowchart of the device pre-configuration process executed by the data circulation service platform control server 101.

[0159] The device pre-configuration function 228 reads the requested content (S661). Then, the branch is processed according to the read requested content.

[0160] If the read request is an information retrieval request ("Yes" in S662), the device configuration function 228 obtains the "device configuration function" utilization data 340, generates prompt data (S663), and returns a response indicating the obtained data (S681).

[0161] If the read request is an asset category information registration request ("Yes" in S664), the device pre-configuration function 228 registers the requested asset category information to asset category information 344 (S665) and returns a registration completion response (S681).

[0162] If the read request is an asset information registration request ("Yes" in S666), the device pre-configuration function 228 registers the requested asset information into asset information 343 (S667) and returns a registration completion response (S681).

[0163] If the read request is a device manager selection request ("Yes" in S668), the device provisioning function 228 registers the selected device manager in the device manager selection information 341 (S669) and returns a registration completion response (S681).

[0164] If the read request is a device / asset association information registration request ("Yes" in S670), the device pre-configuration function 228 registers the requested association to the device / asset association information 345 (S671) and returns a registration completion response (S681).

[0165] If the read request is a device-specified firmware registration request ("Yes" in S672), the device provisioning function 228 registers the requested firmware to the device distribution file management information 342 (S673), refers to the device manager selection information 341 (S674), registers the firmware to the device manager corresponding to the device ID of the specified communication device 150 (S675), and returns a registration completion response (S681).

[0166] If the read request is an asset information specification configuration file registration request ("Yes" in S676), the device pre-configuration function 228 searches for device / asset association information 345, determines the corresponding communication device 150 based on the asset information involved in the registration request (S677), and registers it in the device distribution file management information 342 (S678). Furthermore, the device pre-configuration function 228 refers to the device manager selection information 341 (S679), registers the configuration file in the device manager corresponding to the device ID of the determined communication device 150 (S680), and returns a registration completion response (S681).

[0167] If the read request is not an asset information specified setting file registration request, i.e. does not meet any of steps S662, S664, S666, S668, S670, S672, and S676, an unclear processing request receiving error is recorded in the history information 302 (S682).

[0168] Figure 22 This is a flowchart of the IoT data collection, processing, and management executed by the data circulation service platform control server 101.

[0169] IoT data collection / processing / management function 231 reads in a request or receives IoT data content (S691). Then, the branch is processed according to the content of the read request.

[0170] If the data read is an IoT data threshold setting request for an alarm notification ("Yes" in S692), the IoT data collection / processing / management function 231 registers the requested IoT data threshold to the alarm threshold setting information 352 (S693) and returns a registration completion response (S705).

[0171] If the data read is an alarm notification destination setting request ("Yes" in S694), the IoT data collection / processing / management function 231 registers the requested alarm notification destination to the alarm notification destination information 353 (S695) and returns a registration completion response (S705).

[0172] If the received data is IoT data ("Yes" in S696), the IoT data collection / processing / management function 231 refers to the processing information 351 (S697) and processes the received IoT data once (S698), storing the processed IoT data in the IoT data pool 109 (S699). Then, the IoT data collection / processing / management function 231 refers to the alarm threshold setting information 352 (S700) to determine whether an alarm threshold is set in the data items of the received IoT data and whether the received IoT data exceeds the threshold (S701). If no alarm threshold is set, or the received IoT data does not exceed the threshold, the IoT data collection / processing / management function 231 returns a response indicating reception completion (no alarm required) (S705). On the other hand, if an alarm threshold is set and the received IoT data exceeds the threshold, the IoT data collection / processing / management function 231 refers to the alarm notification destination information 353 (S702) to determine whether the alarm notification destination has been registered (S703). Then, if an alarm notification destination is registered, data is generated to notify the user that the threshold has exceeded the alarm (S704), and a response to the generated alarm is returned (S705).

[0173] If the read request is not an asset information specified setting file registration request, i.e. does not meet any of steps S692, S694, and S696, an unclear processing request receiving error is recorded in the history information 302 (S706).

[0174] Figure 23 This is a diagram representing multi-tenant access to the server using a communication adapter.

[0175] The data circulation service platform control server 101 sets the communication adapter and receiving adapter to be used according to each tenant's selection. By selecting the communication adapter and receiving adapter, the access destinations 110, 120, and 130 can be determined.

[0176] Specifically, based on the SIM information's MNO and configuration file settings, the communication adapter 224 to be used, i.e., the communication operator's IoT platform 110 of the other party, is determined. Additionally, based on cloud service selection settings, the communication adapter 227 and IoT data receiving adapter 233 to be used, i.e., the cloud service 120, are determined. Furthermore, based on device manager selection settings, the communication adapter 230 to be used, i.e., the device manager server 130, is determined. These can be determined by the tenant-side user or the platform-side administrator.

[0177] Figure 24 This is a diagram representing the distribution of the configuration file corresponding to asset 160 by device manager server 130.

[0178] For example, consider the case of updating the asset type-X configuration file (cfg-X-v2) installed on the communication device 150 connected to the type-X asset 160.

[0179] Tenant-side users access the data circulation service platform control server 101 and request updates to the asset type-X configuration file from GUI211 or API212.

[0180] The device pre-configuration function 228, referring to asset information 343 and device / asset association information 345, determines the communication device 150 corresponding to the asset 160 that is the target of the configuration file update. Therefore, it is known that the devices connected to asset type-X are d0000 and d0001. Next, the device pre-configuration function 228 registers the configuration file version, date, etc., as file management information in the device distribution file management information 342. Afterwards, the device pre-configuration function 228 accesses the device manager server 130 and requests that the configuration of communication devices d0000 and d0001 be updated to v2.

[0181] Device manager server 130 has a firmware and configuration file management database. Referring to this database, it obtains the access destination information for the configuration file to be distributed. Then, device manager server 130 notifies the communication device 150 that should update the configuration file of the new version and access destination information. For example, as information sent to communication device d0000, it notifies the configuration file name cfg-X-v2 and the URL (token) used to obtain the configuration file.

[0182] The device manager server 130 can not only distribute download destination URLs, manage and send files as described above, but also periodically obtain information from the communication device 150. Furthermore, the device manager server 130 does not manage the mapping between the communication device 150 and the asset 160, and distributes configuration files to the communication device 150 according to instructions from the data circulation service platform control server 101. Therefore, it can update the configuration files of the communication device 150 without considering the asset 160. On the other hand, the data circulation service platform control server 101 knows the attributes of the asset 160 and the mapping between the communication device 150 and the asset 160. Therefore, it can recognize the asset 160 as the connection destination of the communication device 150 and create update information for the communication device 150.

[0183] According to the notification from the device manager server 130, the communication device 150 obtains the asset type-X configuration file (cfg-X-v2). Alternatively, the configuration file can be obtained from the communication device 150 via access or by push. As a result, the configuration file (cfg-X-v1) of the communication device d0000 connected to the type-X asset a0000 is updated to the new configuration file (cfg-X-v2).

[0184] Figure 25 This is an example diagram showing a device overview screen 800 output by GUI211.

[0185] The device overview screen 800 includes a function selection button 801, a display button 802, an update button 803, a search button 804, a search object selection bar 805, a search condition input bar 806, and a device overview display area 810.

[0186] The function selection button 801 is used to open a menu to select the processing to be performed on this screen. It allows selection of adding, editing, deleting, associating with assets, requesting firmware distribution, requesting configuration distribution, and outputting data for the communication device 150. For example, by selecting "Edit" from the menu, the SIM installed on the communication device 150 can be updated while maintaining the relationship between the communication device 150 and the asset 160. Similarly, by selecting "Associate with Asset" from the menu, the relationship between the communication device 150 and the asset 160 can be updated while maintaining the relationship between the SIM and the communication device 150.

[0187] The Display button 802 is used to open a menu to select the data items to be displayed. The Update button 803 is used to update to the latest display. The Search Item Selection bar 805 is used to select the items to search for, allowing selection of a search within a specified item or a search across all items. The Search Criteria Input bar 806 is used to enter the terms to search for within the search items. The Search button 804 is used when starting a search based on the entered search criteria.

[0188] The device overview display area 810 is an area that displays an overview of the managed communication devices 150. In the illustrated state, it displays the device ID, device group, device name, SIM ID, and asset ID. The displayed information is registered in device information 333 and device / asset association information 345.

[0189] By selecting the data items displayed in the device overview area 810 using the horizontal arrows, the display order can be changed to ascending or descending.

[0190] By selecting items in the device overview display area 810, a summary of the selected items can be displayed. For example, clicking on an asset ID displays the asset overview screen 900 (see reference). Figure 26 When you click on SIM ID, a SIM overview screen will be displayed (illustration omitted). When you click on a device group, a device group overview screen will be displayed (illustration omitted).

[0191] Figure 26 This is an example of an asset overview screen 900 output by GUI211.

[0192] The asset overview screen 900 includes a function selection button 901, a display button 902, an update button 903, a search button 904, a search object selection bar 905, a search criteria input bar 906, and an asset overview display area 910.

[0193] The function selection button 901 is used to open a menu to select the processing to be performed on this screen, and can select to add, edit, delete assets, associate with communication devices, configure distribution requests, and output data. For example, by selecting "Associate with Communication Devices" from the menu, the relationship between communication device 150 and the asset 160 can be updated by associating the communication device 150 and the asset 160 with other communication devices 150.

[0194] The Display button 902 is used to open a menu to select the data items to be displayed. The Update button 903 is used to update to the latest display. The Search Item Selection bar 905 is used to select the items to search for, allowing selection of a search within a specified item or a search across all items. The Search Criteria Input bar 906 is used to enter the terms to search for within the search items. The Search button 904 is used when starting a search based on the entered search criteria.

[0195] The asset overview display area 910 shows a list of managed assets 160. In the illustrated state, it displays the asset ID, asset serial number, asset name, asset category, and equipment ID. The displayed information is registered in asset information 343 and equipment / asset association information 345.

[0196] By using the horizontal arrows to select the data items displayed in the asset overview area 910, the display order can be changed to ascending or descending.

[0197] By selecting items in the asset overview display area 910, a list of the selected items can be displayed. For example, clicking on a device ID will display the device overview screen 800 (see reference). Figure 25 When you click on SIM ID, a SIM overview screen is displayed (illustration omitted). When you click on a device group, a device group overview screen is displayed (illustration omitted).

[0198] As described above, the IoT system (data circulation service platform 100) of this embodiment includes: a communication device 150 equipped with a SIM (identification module) for controlling communication elements, which communicates with a cloud server (cloud service 120); an asset 160 connected to the communication device 150; and a control server (data circulation service platform control server 101) that manages the communication settings between the communication device 150 and the cloud service 120. The data circulation service platform control server 101 manages the relationship between the SIM and the communication device 150 (SIM / device association information 325) and the relationship between the communication device 150 and the asset 160 (device / asset association information 345). In order to forward information from the asset 160 to the cloud service 120, the communication between the communication device 150 and the cloud service 120 is configured, thus enabling unified control of the elements required by the IoT system. Therefore, data collected from multiple assets 160 deployed globally can be analyzed to perform flexible maintenance applications such as proactive maintenance based on fault prediction and destination tracking based on location information.

[0199] In addition, it does not require separate (1) selection of communication operators in various countries and locations for effectively utilizing the data of the globally deployed assets 160, application development for line connections based on understanding the IoT platform, (2) selection of communication equipment 150 for collecting data of assets 160 and wireless transmission, application development of communication equipment, (3) construction of a system to collect, accumulate and visualize IoT data in cooperation with cloud service 120. Instead, it can provide a one-stop service platform for data analysis and visualization of globally deployed products, including "communication line association of communication equipment", "equipment pre-configuration", and "IoT data acquisition, accumulation and visualization".

[0200] In addition, the data circulation service platform control server 101 determines the cloud service 120 to be the communication destination of the communication device 150 based on the settings of the communication adapter 227 used to communicate with the cloud service 120, so that the cloud service 120 can be selected without complicated settings.

[0201] In addition, the configuration data (configuration file) set in the communication device 150 depends on the asset 160 connected to the communication device. The data flow service platform control server 101 searches for the communication device 150 connected to the asset 160. The searched communication device 150 outputs information (URL (token)) for updating the configuration file. Therefore, the configuration file of the communication device 150 can be updated without considering the asset 160.

[0202] In addition, the data circulation service platform control server 101 maintains SIM / device association information 325 for managing the correspondence between SIM and communication device 150 and device / asset association information 345 for managing the correspondence between communication device 150 and asset 160. When the SIM is replaced, the device / asset association information 345 is not updated, but the SIM information is updated in the SIM / device association information 325. Therefore, the SIM installed on the communication device 150 can be updated while maintaining the relationship between communication device 150 and asset 160.

[0203] In addition, the data circulation service platform control server 101 maintains SIM / device association information 325 for managing the correspondence between SIM and communication device 150 and device / asset association information 345 for managing the correspondence between communication device 150 and asset 160. When communication device 150 is replaced, the information of communication device 150 is updated in SIM / device association information 325 and device / asset association information 345. Therefore, communication device 150 can be updated while maintaining the relationship between SIM and asset 160.

[0204] In addition, the data circulation service platform control server 101 outputs display data (device overview screen 800, asset overview screen 900) to display the correspondence between SIM, communication device 150 and asset 160. By specifying any one of SIM, communication device 150 and asset 160, it provides an interface for updating the specified element while maintaining the relationship between other elements, thus enabling flexible changes to the relationship between SIM, communication device 150 and asset 160.

[0205] Furthermore, the present invention is not limited to the embodiments described above, but includes various modifications and equivalent structures within the scope of the appended claims. For example, the embodiments described above are provided in detail for ease of understanding and illustration of the invention, and the invention is not limited to having all the described structures. Additionally, a portion of the structure of one embodiment may be replaced with the structure of another embodiment. Furthermore, structures of other embodiments may be added to the structure of one embodiment. Additionally, parts of the structures of each embodiment may be added to, deleted from, or replaced with other structures.

[0206] In addition, some or all of the aforementioned structures, functions, processing units, and processing modules can be implemented in hardware, such as through integrated circuit design, or in software, by having a processor interpret and execute the program that implements each function.

[0207] Information such as programs, tables, and files that perform various functions can be stored in storage devices such as memory, hard disks, SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs.

[0208] In addition, the control lines and information lines shown are those deemed necessary for the explanation, but are not limited to showing all the control lines and information lines required for installation. In fact, it can be assumed that almost all the structures are interconnected.

Claims

1. An IoT system, characterized in that, have: Communication equipment, which is equipped with an identification module that controls communication elements and communicates with a cloud server; Assets, which are connected to the communication device; and A control server that manages the communication settings between the communication devices and the cloud server. The configuration data set in the communication device depends on the asset connected to the communication device. The control server manages the relationship between the identification module and the communication device and the relationship between the communication device and the asset, and sets up communication between the communication device and the cloud server in order to forward information from the asset to the cloud server. The communication between the communication device and the cloud server is set up by registering cloud service setting information corresponding to the selected cloud operator and the selected service plan with the control server. The cloud server is provided by the selected cloud operator, and the selected service plan is selected from multiple available service plans provided by the selected cloud operator. The control server searches for communication devices connected to the asset by querying the correspondence between the communication devices tracked in the control server, and outputs information for updating the setting data of the searched communication devices. Based on the settings of the communication adapter used to communicate with the cloud server, it determines the cloud server to be the communication destination of the communication device. The communication adapter is a component of the control server. The selected cloud provider and service plan are chosen through the control server.

2. The IoT system according to claim 1, characterized in that, The control server maintains module / device association information for managing the correspondence between the identification module and the communication device, and device / asset association information for managing the correspondence between the communication device and the asset. When the identification module is replaced, the control server does not update the device / asset association information, but updates the information of the identification module in the module / device association information.

3. The IoT system according to claim 1, characterized in that, The control server maintains module / device association information for managing the correspondence between the identification module and the communication device, and device / asset association information for managing the correspondence between the communication device and the asset. When the communication device is replaced, the control server updates the information of the communication device in the module / device association information and the device / asset association information.

4. The IoT system according to claim 1, characterized in that, The control server outputs display data to show the correspondence between the identification module, the communication device, and the asset, and provides an interface for updating the specified element while maintaining the relationship between other elements, by specifying any one of the identification module, the communication device, and the asset.

5. A data collection control method for controlling data collection in an IoT system, characterized in that, The IoT system comprises: a communication device equipped with an identification module for controlling communication elements and communicating with a cloud server; an asset connected to the communication device; and a control server that manages the communication settings between the communication device and the cloud server. The configuration data set in the communication device depends on the asset connected to the communication device. The data collection control method includes: The control server manages the relationship between the identification module and the communication device and the relationship between the communication device and the asset, and sets up communication between the communication device and the cloud server in order to forward information from the asset to the cloud server. The communication between the communication device and the cloud server is set up by registering cloud service setting information corresponding to the selected cloud operator and the selected service plan with the control server. The cloud server is provided by the selected cloud operator, and the selected service plan is selected from multiple available service plans provided by the selected cloud operator. The control server searches for communication devices connected to the asset by querying the correspondence between the communication devices tracked in the control server and the asset. The control server outputs information for updating the setting data of the searched communication devices; and The control server determines the cloud server to be the communication destination of the communication device based on the settings of the communication adapter used for communicating with the cloud server, wherein the communication adapter is a component of the control server. The selected cloud provider and service plan are chosen through the control server.

6. The data collection and control method according to claim 5, characterized in that, The control server maintains module / device association information for managing the correspondence between the identification module and the communication device, and device / asset association information for managing the correspondence between the communication device and the asset. When the identification module is replaced, the control server does not update the device / asset association information, but updates the information of the identification module in the module / device association information.

7. The data collection and control method according to claim 5, characterized in that, The control server maintains module / device association information for managing the correspondence between the identification module and the communication device, and device / asset association information for managing the correspondence between the communication device and the asset. When the communication device is replaced, the control server updates the information of the communication device in the module / device association information and the device / asset association information.

8. The data collection and control method according to claim 5, characterized in that, The control server outputs display data to show the correspondence between the identification module, the communication device, and the asset. The control server provides an interface for updating a specified element while maintaining the relationship between other elements, by specifying any one of the identification module, the communication device, and the asset.

Images