SEPARATE UPGRADE/MODIFICATION OF REMOTE SOFTWARE IN MACHINE TO MACHINE COMMUNICATION

• US 20140007076A1
• Filed: 03/14/2012
• Published: 01/02/2014
• Est. Priority Date: 03/30/2011
• Status: Abandoned Application

• Current Assignee: KT Corporation
• Original Assignee: KT Corporation
• Inventors: Kim, Sangeon, Jung, Hanwook, Heo, Sungphil, Kang, Sujin, Kim, Yeonsoo
• Application Number:
  US14/004,453
• Publication Number:
  US 20140007076A1
• Time in Patent Office: Days
• US Class Current: 717/173
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

The present disclosure is related to separately upgrading or modifying a remote software in a machine to machine (M2M) communication. Particularly, in the case of upgrading or modifying firmware of an M2M device or an M2M gateway, the present disclosure relates to separating an M2M service provider domain and a manufacturer domain, and independently upgrading or modifying each of the separated domains.

Claims

1. A method of separately upgrading or modifying a remote software installed in (i) a machine to machine (M2M) device which performs a function of an M2M communication enabling communications between two or more machines or (ii) an M2M gateway performing a gateway function in the M2M communication, the method comprising:

transmitting, by a first server, a second software for upgrade or modification of a first software to the M2M device or the M2M gateway, wherein the first software is installed in the M2M device or the M2M gateway; and

performing the upgrade or modification of the first software, separately from a third software installed in the M2M device or the M2M gateway,

wherein the third software is upgraded or modified by a second server, and the first server is an entity different from the second server.

2. The method of claim 1, wherein when the first server is a server of an M2M service provider associated with a communication network applied to the M2M communication,

the second server is a server of at least one of (i) a manufacturer of the M2M device or the M2M gateway and (ii) an application provider having created the first software.

3. The method of claim 2, wherein when the first server is a server of at least one of (i) a manufacturer of the M2M device or the M2M gateway and (ii) an application provider having created the first software,

the second server is a server of an M2M service provider associated with a communication network applied to the M2M communication.

4. The method of claim 3, wherein the M2M device or the M2M gateway requests an authorization check associated with the upgrade or modification of the first software to an authorization control server, in order to modify or upgrade the first software.

5. The method of claim 1, wherein when the second software is a software for improvement of networking performance of the M2M device or the M2M gateway,

the transmitting, by the first server, the second software to the M2M device or the M2M gateway includes:

storing the second software to a remote software control server for an M2M service provider; and

transmitting, by the remote software control server for the M2M service provider, the second software to the M2M device or the M2M gateway.

6. The method of claim 5, further comprising:

after storing the second software to the remote software control server for the M2M service provider,

transmitting the second software to a specific M2M device or M2M gateway which is an upgrade/modification object or at an upgrade/modification time according to control of an M2M server.

7. The method of claim 1, wherein when the second software is a software for improvement of application performance of the M2M device or the M2M gateway,

the transmitting, by the first server, the second software to the M2M device or the M2M gateway includes:

storing the second software to a remote software control server for an application software; and

transmitting, by the remote software control server for the application software, the second software to the M2M device or the M2M gateway according to control of an M2M server.

8. A method of upgrading or modifying a first software installed in (i) a machine to machine (M2M) device which performs a function of an M2M communication enabling communications between two or more machines or (ii) an M2M gateway performing a gateway function in the M2M communication, the method comprising:

receiving a second software for upgrade or modification of the first software from a first server; and

upgrading or modifying the first software using the received second software,

wherein the upgrading or modifying is performed separately from a third software installed in the M2M device or the M2M gateway, and the first server is a different entity from the second server performing upgrade of the third software.

9. The method of claim 8, wherein when the first server is a server of an M2M service provider associated with a communication network applied to the M2M communication,

the second server is a server of at least one of (i) a manufacturer of the M2M device or the M2M gateway and (ii) an application provider having created the first software.

10. The method of claim 9, wherein when the first server is a server of at least one of (i) a manufacturer of the M2M device or the M2M gateway and (ii) an application provider having created the first software,

the second server is a server of an M2M service provider associated with a communication network applied to the M2M communication.

11. The method of claim 10, wherein the M2M device or the M2M gateway requests an authorization check associated with the upgrade or modification of the first software to an authorization control server, in order to modify or upgrade the first software.

12. The method of claim 8, wherein when the second software is a software for improvement of networking performance of the M2M device or the M2M gateway,

the receiving the second software from the first server includes:

receiving the second software from a remote software control server for an M2M service provider.

13. The method of claim 8, wherein when the second software is a software for improvement of application performance of the M2M device or the M2M gateway,

the receiving the second software from the first server includes:

receiving the second software from a remote software control server for an application software according to control of an M2M server.

14. The method of claim 8, further comprising:

determining whether a communication is possible, before the receiving the second software from the first server.

15. The method of claim 8, further comprising:

transmitting an upgrade or modification result of the first software to an authorization control server or a remote software control server.

16. An apparatus for upgrading or modifying software installed in (i) a machine to machine (M2M) device which performs a function of an M2M communication enabling communications between two or more machines or (ii) an M2M gateway performing a gateway function in the M2M communication, the apparatus comprising:

an upgrade/modification storage unit configured to store a second software for upgrade or modification of a first software, wherein the first software is installed in the M2M device or the M2M gateway;

an authentication processor configured to request an authorization check associated with the upgrade or modification of the first software to an authorization control server, in order to modify or upgrade the first software; and

a communication processor configured to transmit the second software to the M2M device or the M2M gateway,

wherein the upgrade or modification of the first software is performed in a different apparatus from an apparatus which modifies or upgrades a third software installed in the M2M device or the M2M gateway.

17-21. -21. (canceled)