KR20120111852A - A methods and apparatus of separated software upgrade of device and gateway by over the air in the machine to machine communication - Google Patents

Abstract

PURPOSE: A method and an apparatus for upgrading a remote software function are provided to reduce upgrade load of a communication business by modifying or upgrading necessary software. CONSTITUTION: An upgrade/modification storage unit(5710) stores second software. The second software modifies or upgrades first software installed in more than one M2M device or an M2M gateway. An authentication unit(5720) confirms a right control server about a right to upgrade or modify. A communication processing unit(5700) transmits the second software to a communication gateway. [Reference numerals] (5500) Object communication processing unit; (5510) Upgrade/modification control unit; (5520) Upgrade/modification processing unit; (5530) Software unit; (5700) Communication unit; (5710) Upgrade/modification storing unit; (5720) Authentication unit

Description

A method and apparatus of separated software upgrade of device and gateway by over the air in the machine to machine communication}

MTC ("Machine to machine communication" or M2M, "Machine type communication" or smart device communication "Smart Device communication" or "Machine oriented communication") refers to all aspects of the way in which communication is carried out without human intervention. Refers to a communication method. There is a need for a method and apparatus for remotely upgrading software of a terminal or gateway that performs such a communication function.

)는 모든 소프트웨어의 기능을 하나의 실행파일로 만든 이진(binary) 형식의 파일로서, 사물통신 기능을 수행하는 단말 또는 게이트웨이의 소프트웨이다. 펌웨어의 업그레이드는 하나의 단일 실행파일 중에서 변경된 부분만 원격으로 전송하여 업그레이드 하는 방법을 임베디드 장치의 업그레이드 방법으로 종래에 사용하고 있다. 이는 통상적으로 CPU, 메모리 등의 컴퓨팅 자원이 매우 제한된 센서나 제어 장치 등에서 사용하는 방법이다.In the related art, in order to perform a remote software upgrade of software such as a terminal or a gateway that performs an IoT communication function, a firmware upgrade method is generally used. Firmware (Firmware or

) Is a binary file that combines all the functions of the software into one executable file, and is a software of a terminal or a gateway that performs a communication function. The firmware upgrade is a method of upgrading an embedded device using a method of remotely transferring only a changed part of a single executable file. This is typically used in sensors or control devices with very limited computing resources such as CPU and memory.

However, when dividing the firmware of a terminal or a gateway that performs a thing communication function, it is composed of software that requires verification of a carrier, software provided by a manufacturer, and software provided by a third application service provider. The current firmware upgrade method requires the verification of the carrier when upgrading the firmware composed of one single software, so that the manufacturer's software or the third application service provider's software that does not need the carrier's verification is also used. Will be verified.

The above-mentioned firmware upgrade method has a problem that a communication service provider must verify even when an upgrade of a software that does not require communication service provider verification occurs. It is difficult for a manufacturer or an application service provider to independently upgrade software that does not require verification.

In order to solve the problems of the prior art, a related party such as a communication service provider, a manufacturer, a third application service provider, or the like can modify software such as a terminal or a gateway that performs a thing communication function having limited resources such as a CPU and a memory. The present invention relates to a method and apparatus for remotely upgrading or modifying necessary software by remotely separating necessary parts. The present invention provides a software for verifying a firmware of a terminal or a gateway that performs a communication function by a telecommunication service provider. The software provided by the manufacturer modifies the software remotely from the manufacturer, and the software provided by the third application service provider relates to a method and apparatus for remotely modifying the software by the third application service provider.

According to an aspect of the present invention, there is provided a method for separating and upgrading remote software in the IoT, storing second software for modifying or upgrading the first software installed in at least one IoT communication device or IoT gateway, and the IoT software. And transmitting the second software to a communication device or a thing communication gateway, wherein the modification or upgrade is performed separately from the third software installed in the thing communication device or the thing communication gateway.

According to an embodiment of the present invention, a method for separating and upgrading remote software in the MOT is provided in the method for modifying or upgrading the first software installed in the MTC device performing the IoT communication or the IoT gateway performing the gateway function. Receiving second software for modifying or upgrading the first software from a remote software control server for a telecommunications carrier or a remote software control server for an application service; and receiving the first software using the received second software. And modifying or upgrading, wherein the modifying or upgrading is performed separately from third software installed in the thing communication device or the thing communication gateway.

An apparatus according to another embodiment of the present invention is an upgrade / modification storage unit for storing the second software for the modification or upgrade of the first software installed in one or more things communication device or IoT gateway, the modification of the stored first software Or an authentication unit for confirming the right of the modification or upgrade to an authority control server for upgrading, and a communication processing unit for transmitting the second software to the thing communication device or the thing communication gateway, wherein the modification or upgrade is performed by the thing. The process may be performed separately from the third software installed in the communication device or the thing communication gateway.

An apparatus according to another embodiment of the present invention is a device in which the first software is installed, and performs a thing communication or a gateway function, the remote software control server for an operator or an application software remote software control server. An upgrade / modification control unit for receiving second software for modifying or upgrading the first software, and an upgrade / modification processing unit for modifying or upgrading the first software using the received second software, The upgrade may be performed separately from the third software installed in the thing communication device or the thing communication gateway.

The software of the MTC device and the MTC gateway may be independently of a communication operator, that is, a manufacturer or a third party software provider may upgrade a function of the software or provide a new application regardless of the carrier.

The service provider may upgrade or modify only necessary software, such as software required for communication function software subscription authentication, which requires operator authentication, thereby reducing the use of work and radio resources such as upgrade load of the service provider.

1 illustrates an example of software of a general IoT apparatus and an IoT gateway.
2 is a configuration diagram of a software separation upgrade system of the MTC device and the MWG according to an exemplary embodiment of the present specification.
FIG. 3 is a diagram illustrating a separate upgrade operation of the MTC device and the MWG according to an exemplary embodiment of the present specification.
4 is a diagram illustrating a software configuration of a thing communication apparatus or a thing gateway according to another embodiment of the present specification.
5 is a view showing the configuration of each device according to an embodiment of the present specification.
FIG. 6 is a diagram illustrating a structure of a physical storage medium for separating and upgrading software according to one embodiment of the present specification.
7 is a view showing the structure of a physical storage medium for upgrading by separating the software according to another embodiment of the present disclosure.
8 is a diagram illustrating a structure of a physical storage medium for upgrading and separating software according to another embodiment of the present specification.
9 is a diagram illustrating a process of upgrading or modifying specific software in a remote software control server according to an embodiment of the present invention.
FIG. 10 is a diagram illustrating a process of upgrading or modifying specific software in a thing communication device performing a thing communication or a thing communication gateway performing a gateway function according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In addition, in describing the component of this invention, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; may be "connected," "coupled," or "connected. &Quot;

As described above, in the case of IoT, since software developed by various operators may be installed in a device, upgrading an entire device system may cause various loads.

In this specification, in order to solve such a problem, in performing an upgrade of a plurality of software included in a device, the method is partly a method of remotely software.

1 illustrates an example of software of a general IoT apparatus and an IoT gateway. The firmware here is implemented integrally with the hardware and affects the entire system. That is, conventionally, only firmware could be upgraded.

2 is a configuration diagram of a software separation upgrade system of the MTC device and the MWG according to an exemplary embodiment of the present specification.

In FIG. 2, an executable file is created for each function of the software to partially upgrade an environment called an operating system capable of operating the executable file, and each application software and library.

In more detail, in the service configuration of FIG. 2, software of the M2M device and the M2M gateway may remotely upgrade a partial software. That is, the present invention relates to a method and an implementation of a party having a right to partially separate and upgrade software of an IoT communication device and an IoT communication gateway without influencing other software. 2100, 2110, communication gateways 2200, 2250, things 2210, 2220, 2260, 2270, wireless communication network 2300, Internet 2310, remote software control server 2400, 2410, IoT communication server ( 2510, the authority control server 2500.

The M2M devices 2100 and 2110 are M2M devices having a wireless communication device and communicate information generated or controlled by a sensor, a controller, or the like with the M2M server 2510 without using a wireless communication device. .

The M2M gateway provides a function of relaying a device (a thing, a sensor, or an actuator) such as 2210, 2220, 2260, or 2270 to communicate with the IoT server 2510 without human intervention. do.

Things 2210, 2220, 2260, and 2270 communicate with things gateways 2200 and 2250.

The wireless communication network 2300 provides a wireless communication function necessary for the IoT communication apparatuses 2100 and 2110 and the IoT communication gateways 2200 and 2250 to communicate with the IoT communication server 2510. The wireless communication network 2300 includes various mobile communication networks such as a second generation wireless mobile communication network, a third generation wireless mobile communication network, a WiBro network, a WiFi network, and an LTE / LTE-A network.

The Internet 2310 provides an Internet communication function necessary for the M2O 2100 and 2110 and the MW2200 and 2250 to communicate with the M2 server 2510.

The remote software control server 2400 is a remote software control server for a communication service provider, the remote software control server 2410 is an application software remote software control server, and the communication device (2100, 2110) and the IoT communication gateway (2200, 2250) It is a device that controls remote upgrade of partial software.

The rights control server 2500 is a server that handles related functions for checking legitimate rights for software upgrades or modifications. The thing communication server 2510 is a server which processes a thing communication function other than software upgrade. Physically 2400, 2410 and 2500, 2510 may be performed in one device.

FIG. 3 is a diagram illustrating a separate upgrade operation of the MTC device and the MWG according to an exemplary embodiment of the present specification.

In the configuration of FIG. 2 and the embodiment of FIG. 3, it can be seen that the software of the MTC device and the MWG partially upgrades only relevant software remotely.

The software of the IoT apparatuses 2100 and 2110 and the IoT gateways 2200 and 2250 of FIG. 2 are configured as shown in FIG. 4, which is different from the conventional configuration of FIG. 1.

Briefly described with reference to FIG.

The software of FIG. 4 is divided into device drivers 4510 and 4520, applications 4520 and 4530, and the like. For example, the 4520 upgrades or modifies through the control of the telecommunications provider remote software control server 2400, and the 4530 upgrades through the control of the remote software control server 2410 for application services.

When the software is changed to improve the performance of the 4520, the new software is stored in the remote software control server 2400 for the telecommunications carrier, and the devices of the MOT devices 2100 and 2110 or the IoT gateways 2200 and 2250 are remotely stored. Upgrade to

In this case, the newly changed partial software is stored in a remote software control server 2400 for a communication service provider, and according to the control of the IoT communication server 2510, the upgrade time, the IoT communication apparatuses 2100 and 2110 or the IoT communication gateway that are to be upgraded ( The software is partially upgraded for the devices 2200 and 2250.

In order to partially change the software as shown in FIG. 4, a detailed operation process related to upgrading / modifying the software is shown in FIG. 3. In FIG. 3, as illustrated in FIG. 2, the authorization control server 2500, the remote software control servers 2400 and 2410, and the apparatus 2900 are included. The apparatus 2900 may include the apparatus 2900, the apparatus 2100, 2110, the apparatus 2200, 2250, or the apparatus 2210, 2220, 2260, 2270 coupled to the apparatus 2300. Can be. In addition, the IoT communication server 2510 controls the remote software control servers 2400 and 2410 to perform a software upgrade.

If the software that needs to be upgraded is developed and distributed through testing, it is stored in the server (2400, 2410 of FIG. 2) operated by the institution that upgrades the new software (S3110), and the upgrade is required for the authority control server 2500. The information is notified (S3120). At this time, an embodiment of the information to be notified may be a name of the upgrade software, a distribution reference date, a distributor, or the like.

Since the software upgrade should be performed by distributing the traffic in consideration of the network situation, the authorization control server 2500 checks whether the distributor has the authority to upgrade the corresponding software (S3200). The method of checking the upgrade right may be performed by checking whether there is a right to change firmware or software of 510, 520, and 530 of FIG. 4. The firmware or software can be accessed and controlled using information having a corresponding authority by dividing a physical storage space as shown in FIGS.

Check the upgrade rights of the firmware or software, and if there is a right to change or upgrade the software, check whether the communication is possible to upgrade the device 2900 (step S3210). For example, the firmware related to 4520 of FIG. 4 may be upgraded, and the firmware may use the divided storage space of FIG. 6 to be described later. The 2400 device of FIG. And read and write functions of the divided storage space of FIG. 6.

On the other hand, if there is no upgrade authority, the time of occurrence, the attempted IP address, the relevant connection information, etc. are recorded (S3240) and ends.

When the M2M device or the gateway is in the dormant state in which communication is not possible in step S3210, a control signal for switching to the communication enabled state for the upgrade may be sent to the device 2900 (S3220).

Thereafter, the authorization control server 2400 notifies 2400, 2410, and 2900 that upgrade is possible.

The server 2400 or 2410 having the software or firmware to be upgraded starts the upgrade of new software or firmware to the device 2900 (step S3130). In this case, the servers 2400 and 2410 may check information such as the name, size, and date of last modification of software or firmware of the MTC device or the MWG and record the corresponding information.

When the server 2400 or 2410 transmits software or the like to upgrade new software or firmware (step S3140), the device 2900 receives the new software in 5551 of FIG. 5 to be described later (step S3310). Error control and flow control are performed until all are received (S3150, S3320).

When transmission is completed, the server 2400 or 2410 notifies the authority control server 2500 of the completion time, the software name, and the version information (S3190). In addition, when the device 2900 receives all new software, the device 2900 may replace the software or firmware with a new one and proceed with a process such as rebooting. If the function is normally performed after the reboot, the completion time, the software name and version information is notified to the authority control server 2500 (S3380). However, if the normal operation is not performed after the reboot, it may return to the previous software or firmware, and may notify the authority control server 2500 of the result (S3340).

In the same manner, when the software is changed to improve the performance of the application 45300 of FIG. 4, the new communication apparatus stores the new software in the remote software control server 2410 for an application service, and according to the control of the IoT server 2510. Software is partially upgraded for the devices of the 2100 and 2110 or the IoT gateways 2200 and 2250.

Which control server will perform a partial upgrade of the software of FIG. 4, i.e., whether the remote software control server 2400 for the service provider or the remote software control server 2410 for the application service controls the authorization control server. (2500) can decide.

The method described in the process and configuration of Figures 2 and 3 has the advantage that can be upgraded by separating the software. In particular, as shown in FIG. 2, the MTC device includes software that requires authentication of a service provider and software that does not require authentication of a service provider. It is inefficient to authenticate even application software that is not needed. In addition, other software-related parties such as application developers cannot upgrade the software independently, and must upgrade according to the authentication procedure of the communication service provider, which may cause a problem in that the upgrade cannot be performed in a timely manner. Therefore, when applying the configuration and software of Figures 2 and 3 of the present specification, it is possible to perform a separate upgrade, it is possible to limit the scope of the upgrade to specific software.

4 is a diagram illustrating a software configuration of a thing communication apparatus or a thing gateway according to another embodiment of the present specification. 4520 is a part directly related to communication, and is an area that can be controlled by the remote software control server 2400 for the service provider of FIGS. 2 and 3. Meanwhile, 4530 is general application software and is an area that can be controlled by the remote software control server 2410 for application services. The control of the 4520 and 4530 is not necessarily limited to the service provider / application provider, the remote software control server 2400 for the telecommunications carrier can also control the 530, and the remote software control server 2410 for the telecommunications service provider is also used for the telecommunications carrier. The 4520 may be controlled through collaboration with the remote software control server 2400.

2, 3, and 4, the software upgrade of the IoT apparatus or the IoT gateway may be performed through over-the-air (OTA), in which case the M2M application software and the communication service provider Managed or certified software (Mobile Network Operator Certified software) can be upgraded independently of each other.

As shown in Figures 3 and 4, separate upgrade of software means that it does not affect the software in other areas. That is, a plurality of applications may be installed in 4530 of FIG. 4, and the software upgrades of these applications are separated and upgraded so as not to affect other components of the respective applications. Therefore, the service provider does not need to perform the authentication of the upgrade of the application 4530 in terms of security or system protection.

6, 7, and 8 to be described below are examples of implementing one physical storage medium divided into different areas in order to separate and upgrade software. The software storage space is divided into 4510 of FIG. 4 as shown in FIG. 6, 520 of FIG. 4 is used as shown in FIG. 7, and 4530 of FIG. 4 as shown in FIG. Can be used in areas. 6, 7, and 8 are merely examples, and the capacity and division form of the divided regions may be configured differently. Partition types are distinguished using partition identifiers. The division identification information of Figs. 6, 7, and 8 are 0x07, 0x83, and 0x83, respectively. 6, 7, and 8 can also be divided again using the same segment identification information. For example, the HPFS / NTFS partition of FIG. 6 may be used as one file system or divided into two or three file systems.

The software or firmware No. 4510 of FIG. 4 stores software in the divided storage space of FIG. The software is distinguished using the path information of the software and the software name and version information. The software determines whether the software is upgraded using information such as date, time information and size of the software change.

Similarly, even if the service provider upgrades an area such as the networking 4520 of FIG. 4, the application 4530 may not be affected, thereby preventing the problem of reinstalling the entire application.

In FIG. 4, when an upgrade is performed by separating an area of application software of 530 from an area requiring authentication or having a significant impact on the system, such as 4520 or 4510, the upgrade can be performed without the need for a communication service provider.

2 and 4, if there are software to be upgraded, the IoT communication gateway or the IoT gateway may be a remote software control server or an application software remote software control server for a service provider, depending on whether the software to be upgraded is software for a service provider or application software. You will receive new software from. The software may be partially upgraded using the received software. To this end, the thing communication apparatus or the thing communication gateway may further include an upgrade controller and an upgrade performer in addition to the components for the existing thing communication. Of course, the upgrade control unit and the upgrade execution unit may be implemented in addition to the components for the existing thing communication.

5 is a view showing the configuration of each device according to an embodiment of the present specification.

Looking at the main components, the upgrade correction / control unit 5510 checks whether the software upgrade, and depending on whether the software to be upgraded is a carrier software or an application software, the remote software control server or application software remote software control for the carrier Receive new software from the server. It may be coupled to a transmission / reception component for communication of things.

The upgrade / correction processor 5520 partially upgrades the software by using the received software. This configuration can be found at 5800.

5800 shows the configuration of the MTC device or the MTF. The communication processor 5500 is a transmitter / receiver for object communication, and performs communication using a wireless communication network as shown in FIG. 2.

5900 shows the configuration of a remote software control server. At 5900, the communication processing unit 5700 shows that the remote software control server for the service provider or the application service of FIG. 2 can communicate using the Internet or a wireless communication network.

The upgrade / modification storage unit 5710 may store a software upgrade to be provided to the thing communication device or the thing communication gateway, and may provide the upgrade file by request or at its own discretion.

The authenticator 5720 may optionally exist. For example, in the case of a manufacturer or a third party remote software control server for an application service provider, the authenticator 5720 checks the authority control server 500 of FIG. 2 and the authority to upgrade or modify the corresponding software. However, in the case of the remote software control server of the communication service provider, the authentication process may be omitted, and thus the authentication unit 5720 may not be included.

9 is a diagram illustrating a process of upgrading or modifying specific software in a remote software control server according to an embodiment of the present invention.

In operation S9010, the second software for modifying or upgrading the first software installed in the one or more thing communication devices or the thing communication gateway is stored. The second software may be generated by a communication service provider of a communication network applied to the IoT, or may be generated by a manufacturer that manufactures the IoT apparatus or the IoT gateway, or a third application provider that generates the first software. Can be. The first and second software include firmware.

Thereafter, in order to modify or upgrade the stored first software, the authority of the modification or upgrade is checked to the authority control server (S9020). The embodiment of the authority check process in FIG. 3 may be applied. When the authority is confirmed, that is, when there is a right to modify or upgrade (S9030), the second software is transmitted to the IoT apparatus or the IoT gateway (S9040). The modification or upgrade may be performed separately from the third software installed in the thing communication device or the thing communication gateway.

In addition, the first software of FIG. 9 may be software of some of the software installed in the thing communication device or the thing communication gateway, and the upgrade / modification through the second software affects only the first software.

When the second software is software for improving the performance of networking of the MTC device or the MWG, since approval of a communication provider is required, the second software is stored in a remote software control server for a telecommunication service provider. The remote software control server for an operator may be implemented to transmit the second software to the MTC device or the MTC gateway. In this case, after the second software is stored in the remote software control server for the telecommunication service provider, the second software may be upgraded according to the control of the MTC server for the upgrade time, the specific MTC device or the MTC gateway to be upgraded. This can reduce the load on the remote software control server for the carrier.

In addition, when the second software is software for improving the performance of an application of the IoT apparatus or the IoT gateway, the second software is stored in an application software remote software control server, and the application software remote software control server is Under the control of a communication server, the second software may be implemented to transmit to the MTC device or the MTC gateway.

The above-described modifications / upgrades include not only partial replacement of the first software, but also the manner in which the second software completely replaces the first software.

FIG. 10 is a diagram illustrating a process of upgrading or modifying specific software in a thing communication device performing a thing communication or a thing communication gateway performing a gateway function according to an embodiment of the present invention.

The device (the thing communication device or the thing communication gateway) receives a message for confirming the right of the modification or upgrade to the authority control server in order to correct or upgrade the stored first software (S10010).

As a result of confirming the received message, if the user has authority to modify or upgrade (S10020), the second software for correcting or upgrading the first software is received from a remote software control server for a service provider or a remote software control server for an application service. It is made (S10030). In operation S10040, the first software is modified or upgraded using the received second software.

The modification or upgrade may be performed separately from the third software installed in the thing communication device or the thing communication gateway.

In addition, the first software of FIG. 10 may be software of some of the software installed in the thing communication device or the thing communication gateway, and the upgrade / modification through the second software affects only the first software.

If the second software is software for improving the performance of networking of the MTC device or the MW gateway, since the approval of the telecommunication service provider is required, the second software may be received from the remote software control server for the telecommunication service provider. have. In this case, the reception method of the second software may transmit the second software when the device corresponds to an upgrade time, a specific MTC device or an IoT gateway to be upgraded under the control of the MTC server. Reduce the load on the remote software control server for service providers.

In addition, when the second software is software for improving performance of an application of the IoT apparatus or the IoT gateway, the second software may be received from the application software remote software control server controlled by the IoT server. .

The above-described modifications / upgrades include not only partial replacement of the first software, but also the manner in which the second software completely replaces the first software. The upgrade scheme of the present specification may be performed in Network Remote Entity Management (NREM), Gateway Remote Entity Management (GREM), and Device Remote Entity Management (DREM) in connection with M2M communication.

For example, in the case of NREM, the software upgrade may be independently upgraded software and application software for which the MNO's authentication has been performed.

In addition, the GREM may receive and store an M2M gateway in an M2M area network, a firmware upgrade file of firmware that allows the M2M device to upgrade, or management data (including bootstrap related). The upgrade may be performed by using the software upgrade file and management data of the local firmware based on the received files.

In addition, GREM may function as an M2M Gateway management client, which performs Configuration Management (CM) / Performance Management (CM) / Fault Management (FM) and software module / firmware upgrade.

In the case of DREM, it can function as an M2M device management client, which also performs configuration management (CM) / performance management (PM) / fault management (FM) and software module / firmware upgrade functions. .

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas falling within the scope of the same shall be construed as falling within the scope of the present invention.

2100, 2110: communication device
2200, 2250: Communications Gateway
2210, 2220, 2260, 2270: objects
2300: wireless communication network
2310: Internet
2400, 2410: Remote Software Control Server
2500: authorization control server
2510: Communications Server

Claims (22)

Storing second software for modifying or upgrading the first software installed in the one or more thing communication devices or the thing communication gateway; And
Transmitting the second software to the thing communication device or the thing communication gateway,
The modifying or upgrading is performed separately from the third software installed in the thing communication device or the thing communication gateway, a method of separating and upgrading remote software in the thing communication.
The method of claim 1,
The step of transmitting the second software is
Confirming a right of the modification or upgrade to an authority control server for the modification or upgrade of the stored first software; And
And transmitting the second software according to a result of checking the authority from the authority control server.
The method of claim 1,
The second software may be generated by a communication service provider of a communication network applied to the IoT, generated by a manufacturer who manufactures the IoT apparatus or the IoT gateway, or generated by a third application provider that generates the first software. Characterized in that for separating and upgrading remote software in the IoT.
The method of claim 1,
And the software comprises firmware.
The method of claim 1,
And wherein the first software is software of a part of software installed in the thing communication device or the thing gateway, separate upgrade of remote software in the thing communication.
The method of claim 1,
If the second software is software for improving the performance of networking of the IoT apparatus or the IoT gateway, transmitting the second software to the IoT apparatus or the IoT gateway
Storing the second software in a remote software control server for a service provider;
And transmitting the second software to the IoT apparatus or the IoT gateway at the remote software control server for the telecommunication service provider.
The method according to claim 6,
After the step of storing the second software in the remote software control server for the telecommunications provider to transmit the second software to the upgrade time, the MTC device or the MTC gateway to be upgraded under the control of the MTC server. And separating and upgrading the remote software in the IoT.
The method of claim 1,
If the second software is software for improving the performance of an application of the IoT apparatus or the IoT gateway, transmitting the second software to the IoT apparatus or the IoT gateway
Storing the second software in an application software remote software control server;
And the application software remote software control server transmitting the second software to the IoT apparatus or the IoT gateway under the control of the IoT server.
The method of claim 1,
And wherein said second software replaces said first software.
A method of modifying or upgrading first software installed in a thing communication device performing a thing communication or a thing communication gateway performing a gateway function,
Receiving second software for modifying or upgrading the first software from the remote software control server for the service provider or the remote software control server for application services; And
Modifying or upgrading the first software by using the received second software, wherein the modifying or upgrading is performed separately from the third software installed in the thing communication device or the thing communication gateway. To upgrade remote software from IoT.
The method of claim 10,
Receiving the second software is
Receiving a message confirming a right of the modification or upgrade to an authority control server for the modification or upgrade of the stored first software;
And receiving the second software in accordance with the received message.
The method of claim 10,
The second software may be generated by a communication service provider of a communication network applied to the IoT, generated by a manufacturer who manufactures the IoT apparatus or the IoT gateway, or generated by a third application provider that generates the first software. Characterized in that for separating and upgrading remote software in the IoT.
The method of claim 10,
And the software comprises firmware.
The method of claim 10,
And wherein the first software is software of a part of software installed in the thing communication device or the thing gateway, separate upgrade of remote software in the thing communication.
The method of claim 10,
If the second software is software for improving the performance of networking of the IoT apparatus or the IoT gateway, receiving the second software may include
Receiving the second software at the remote software control server for the telecommunications operator.
The method of claim 10,
If the second software is software for improving performance of an application of the MTC device or the MW gateway, receiving the second software may include
Receiving the second software from the application software remote software control server under the control of the thing communication server.
The method of claim 10,
The method of claim 1 further comprising the step of confirming whether communication is possible prior to receiving the second software.
The method of claim 10,
And wherein said second software replaces said first software.
The method of claim 10,
And transmitting the result of the modification or upgrade of the first software to the remote software control server or the authorization control server.
An upgrade / modification storage unit storing second software for modifying or upgrading the first software installed in at least one thing communication device or the thing communication gateway;
An authentication unit for confirming the right of the modification or upgrade to the rights control server for the modification or upgrade of the stored first software; And
A communication processor for transmitting the second software to the thing communication device or the thing communication gateway;
And wherein the modification or upgrade is performed separately from third software installed in the thing communication device or the thing communication gateway.
In the apparatus, the first software is installed, and performs the thing communication or the gateway function,
An upgrade / modification control unit for receiving a second software for modifying or upgrading the first software from a remote software control server or an application software remote software control server for a telecommunication service provider; And
An upgrade / correction processor configured to correct or upgrade the first software using the received second software,
And wherein the modification or upgrade is performed separately from third software installed in the thing communication device or the thing communication gateway.
22. The method of claim 21,
The upgrade / modification processing unit determines whether to upgrade by using any one or more of partition identifier, path information, software change date or time information, software size, software name or version information of the software storage space. Characterized in that, the device.

Images