IP Library Granted Patent US 8,930,707
Granted Patent B2
US 8,930,707 · App. 14/187,965 · Granted Jan 6, 2015

Near field communication (NFC) device and method for selectively securing records in a near field communication data exchange format (NDEF) message

Inventors: Thenmozhi Arunan (Bangalore, IN); Eun-Tae Won (Seoul, KR)
Assignee: Samsung Electronics Co., Ltd
H04L9/3247H04L2209/805H04B5/00G06K7/10297H04W4/008H04L9/3281H04W12/10H04L2209/68
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,930,707
App. No.
14/187,965
Granted
Jan 6, 2015
Kind
B2
Abstract

A method and apparatus for selectively securing records in a Near Field Communication Data Exchange Format (NDEF) message in a Near Field Communication (NFC) device are provided. The method includes generating a place marker signature record by setting a URI_present field to ‘0’ and setting a signature_type field to a predefined value, wherein a combination of the URI_present field set to ‘0’ and the signature_type field set to the predefined value indicates that a signature Record Type Definition (RTD) is a place marker signature record; and placing the place marker signature record in the NDEF message, wherein a set of records following the place marker signature record are secured.

Claims (22)

1. A method for selectively securing records in a Near Field Communication Data Exchange Format (NDEF) message in a Near Field Communication (NFC) device, the method comprising:

generating a place marker signature record indicating that a first set of records preceding the place marker signature record in the NDEF message is unsecured and a second set of records following the place marker signature record is secured, the place marker signature record being generated in a form of a signature Record Type Definition (RID) by setting a URI_present field of the signature RTD to ‘0’ and setting a signature_type field of the signature RTD to a predefined value, wherein a combination of the URI_present field set to ‘0’ and the signature_type field set to the predefined value indicates that the signature RTD is a place marker signature record; and

placing the place marker signature record in the NDEF message.

2. The method of claim 1 , wherein the NDEF message includes an unsecured first set of records spanning from a beginning of the NDEF message to the place marker signature record.

3. The method of claim 1 , wherein the NDEF message includes an unsecured first set of records spanning from a signature RTD preceding the place marker signature record to the place marker signature record.

4. The method of claim 1 , wherein the set of records following the place marker signature record is secured by using a signature RTD that includes a valid signature.

5. The method of claim 4 , further comprising deleting unsecured records in the NDEF message without changing the signature in the signature RTD that includes the valid signature.

6. The method of claim 4 , further comprising modifying unsecured records in the NDEF message, without changing the signature in the signature RTD that includes the valid signature.

7. The method of in claim 4 , further comprising adding unsecured records in the NDEF message, without changing the signature in the signature RTD that includes the valid signature.

8. The method of claim 1 , wherein the predefined value is reserved for indicating a predefined signature type other than a place maker signature record.

9. The method of claim 1 , wherein the predefined value is ‘0’.

10. A Near Field Communication (NFC) device for selectively securing records in a Near Field Communication Data Exchange Format (NDEF) message, the NFC device comprising:

a controller for generating a place marker signature record that a first set of records preceding the place marker signature record in the NDEF message is unsecured and a second set of records following the place marker signature record is secured, the place marker signature record being generated in a form of a signature Record Type Definition (RTD) by setting a URI_present field of the signature RTD to ‘0’ and setting a signature_type field to a predefined value, wherein a combination of the URI_present field set to ‘0’ and the signature_type field set to the predefined value indicates that the signature Record Type Definition (RTD) is a place marker signature record, and placing the place marker signature record in the NDEF message; and

a transmitter for transmitting the NDEF message.

11. The device of claim 10 , wherein the NDEF message includes an unsecured first set of records spanning from a beginning of the NDEF message to the place marker signature record.

12. The device of claim 10 , wherein the NDEF message includes an unsecured first set of records spanning from a signature RTD preceding the place marker signature record to the place marker signature record.

13. The device of claim 10 , wherein the set of records following the place marker signature record is secured by using a signature RTD that includes a valid signature.

14. The device of claim 13 , further comprising deleting unsecured records in the NDEF message without changing the signature in the signature RTD that includes the valid signature.

15. The device of claim 13 , further comprising modifying unsecured records in the NDEF message, without changing the signature in the signature RTD that includes the valid signature.

16. The device of in claim 13 , further comprising adding unsecured records in the NDEF message, without changing the signature in the signature RTD that includes the valid signature.

17. The device of claim 10 , wherein the predefined value is reserved for indicating a predefined signature type other than a place maker signature record.

18. The device of claim 10 , wherein the predefined value is ‘0’.

Priority Claims (2)
IN 1668/CHE/2008 · Jul 9, 2008 · national
KR 10-2009-0043472 · May 19, 2009 · national
Continuity (2)
Continuation 12499919 · Jul 9, 2009
Related Publication 20140201534A1 · Jul 17, 2014