| Electronic Components Datasheet Search |
|
MF2DL1000DA4/02 Datasheet(PDF) 37 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
MF2DL1000DA4/02 Datasheet(HTML) 37 Page - NXP Semiconductors |
|
37 / 132 page ![]() NXP Semiconductors MF2DL(H)x0 MIFARE DESFire Light contactless application IC MF2DL_H_x0 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2019. All rights reserved. Product data sheet Rev. 3.3 — 5 April 2019 COMPANY PUBLIC 430733 37 / 132 10 Transaction Management MIFARE DESFire Light supports the grouping of data management operations into transactions. This allows for committing or aborting all previous write access to files with integrated backup mechanisms within the selected application via a single atomic operation. How a transaction can be initiated and concluded, is detailed in Section 10.1 and Section 10.2. On top of this, MF2DL(H)x0 supports a Transaction MAC feature which allows proofing transaction execution toward a third party. This feature can be used if, for example, a merchant needs to be reimbursed by a backend for the transaction he executed. This way the backend is protected against the fraudulent merchant scenario. The Transaction MAC feature is specified in Section 10.3. 10.1 Transaction Initiation MF2DL(H)x0 does not provide a separate command for initiating a transaction. Instead, a transaction is started by selecting the application with a ISOSelectFile command. Next to this, a new transaction is also automatically initiated after conclusion of a previous transaction, see Section 10.2. Note that a transaction is not affected by the execution of an authentication. One can have several authentications during the course of a single transaction. 10.2 Transaction Conclusion A transaction can be concluded by successfully committing all write operations on backup files, as detailed in Section 10.2.1, or by abortion which will cancel all changes, as detailed in Section 10.2.2. For both operations, MF2DL(H)x0 supports a specific command, but transaction abortion can also be triggered by other commands. Note that some of the parameters and actions triggered by these commands are related with the Transaction MAC feature, explained in Section 10.3. For a full understanding, the description in that section should be referred to. 10.2.1 CommitTransaction Validating all previous write access to back up files within the currently selected application is possible with the command CommitTransaction as defined in Section 11.9.1. The CommitTransaction takes an optional parameter option, which indicates if the Transaction MAC Counter (TMC) and Transaction MAC Value (TMV) of the calculated Transaction MAC, see Section 10.3, are to be sent with the response. If this is requested while the selected application does not support Transaction MAC calculation, i.e. no TransactionMAC file is present, the command is rejected. The CommitTransaction validates all preceding write access of the ongoing transaction to files with integrated backup mechanisms: • Value file • CyclicRecord file If the Transaction MAC feature is enabled, the TransactionMAC file is updated if the Transaction MAC Input (TMI) is different from the empty string. The updated file holds the |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |