METHOD FOR UPDATING AN ENCODED FILE

• US 20130290273A1
• Filed: 12/06/2011
• Published: 10/31/2013
• Est. Priority Date: 12/20/2010
• Status: Abandoned Application

• Current Assignee: Gemalto SA (Thales SA)
• Original Assignee: Gemalto SA (Thales SA)
• Inventors: Gayosso Sanchez, Jose Luis
• Application Number:
  US13/996,112
• Publication Number:
  US 20130290273A1
• Time in Patent Office: Days
• US Class Current: 707/687
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 21/572 Secure firmware programming, e.g. of basic input output system [BIOS]
• CPC Class Codes: G06Q 20/356 Aspects of software for card payments
• CPC Class Codes: G06Q 20/357 Cards having a plurality of specified features

Abstract

The invention relates to method for updating data of an encoded file from a remote server, said encoded file being stored in a secure device, characterized in that it comprises step a): sending a message to said secure device, step b): decoding the encoded file to update, step c): locating a target data and performing an operation upon said target data, said message comprising configuration data and data block.

Claims

1. A method for updating data of an encoded file from a remote server, said encoded file being stored in a secure device, comprising:

step a);

sending a message to said secure device,

step b);

decoding the encoded file to update,

step c);

locating a target data and performing an operation upon said target data,

said message comprising configuration data and data block.

2. The method according to claim 1, comprising repeating step c).

3. The method according to one of the previous claims, comprising updating an OMA DM bootstrap file, said bootstrap file comprising WBXML-encoded message.

4. The method according to claim 3, comprising updating data of an elementary file.

5. The method according to claim 3, comprising updating data of a URL.

6. The method according to one of claims 1 or 2, comprising sending said message over-the-air.

7. The method according to claim 1 or 2, comprising sending said message from a SCWS admin server.

8. The method according to one of claims 1 or 2, comprising processing step b) and c) by an application stored in said secure device.

9. The method according to claim 1 or 2, comprising processing step b) and c) by a servlet running on said secure device.

10. The method according to one of claim 1 or 2, comprising using a smart card as secure device.

11. The method according to one of claim 1 or 2, comprising sending a confirmation to the remote server.

12. (canceled)