Notification 0x1001 - Device Information Update
This notification reports information about general state changes that occur within the device, outside the context of specific operations like transactions (Notification Source 0x01nn - Notifications from Transactions), requests the host receives from the firmware’s integrated display interface (Notification Source 0x18nn - Notifications from User Interface), and so on.
For this notification, Notification Detail described in section 3.2.2.3 Notification Message contains one byte each, shown in the tables below, to indicate:
The Category (Cat) of notification (for example, the subsystem the notification is originating from)
The Reason (Rsn) for the notification (Device Event)
Detail (Det) about the notification that has different meanings depending on the Reason
An Extra field (Ext) that has different meanings depending on the Reason
The other optional message parameters in the Notification Message depend on which combination of four bytes is included in Notification Detail, and are described below.
Table — Notification Detail Codes - Category 0x00 Power / Reset
Category 0x00 Power / Reset contains notification detail codes involving the device’s power and reset functionality. Each possible notification has a unique Reason value:
Reason 0x00 = Device Reset Occurred
Reason 0x01 = Device Reset Will Occur Soon
Reason 0x02 = Low Battery
Reason 0x03 = Key Management
Reason 0x04 = Temperature
00
00
00
00
Power/Reset, Device Reset Occurred, Reserved, Reserved
The device sends and repeats this notification after the device power cycles or resets, depending on the setting in Property 1.2.7.1.1.1 Device Reset Occurred Notification Control. If it is set to repeat, it does so until the host acknowledges it using Property 1.2.7.1.1.2 Device Reset Occurred Notification Acknowledged.
These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table 350.
00
01
0
00
Power/Reset, Device Reset Will Occur Soon, Reserved, Reserved
The device sends this notification before it automatically resets to conform to PCI’s 24 hour Self-Test requirement, and behaves according to the setting in Property 1.2.7.1.1.3 Device Reset Will Occur Soon Notification Control.
See 24 Hour Automatic Reset PCI Requirement for more information.
These notifications always include the Notification Payload parameter in the Notification Message, which directly contains one byte indicating the number of minutes (0x01 to 0xFF) until the device will perform the reset.
00
02
00
00
Power/Reset, Battery, Low Battery Warning, Percent
The device sends this notification when the battery charge reaches 15 percent. If a device is powered on with a charge that is already 15 percent or below, this notification is sent shortly after power up and includes the current battery charge percentage. Percent indicates the percent of battery charge remaining.
00
02
01
00
Power/Reset, Battery, Power Down Imminent, Reserved
The device sends this notification one minute before it automatically powers down the device because the battery charge has reached 0 percent.
00
02
2
00
Power/Reset, Battery, Battery Charge Complete, Reserved
The device sends this notification when the battery charger detects that the battery is fully charged.
00
03
00
00
Power/Reset, Device reset per Command 0x1F01.
The device sends this notification to notify the host when Device executes Reset Command 0x1F01.
Table — Notification Detail Codes - Category 0x01 User Event
Category 0x01 User Event contains notification detail codes involving events triggered by user actions. Each possible notification has a unique Reason value:
Reason 0x00 = Contactless Card Presented (EMV Contactless Only)
Reason 0x01 = Contactless Card Removed (EMV Contactless Only)
Reason 0x02 = Card Seated in Slot (EMV Contact Only)
Reason 0x03 = Card Unseated from Slot (EMV Contact Only)
Reason 0x04 = Card Swiped (MSR Only)
Reason 0x05 = Touch Sensor Press On Display (Touch Only)
Reason 0x06 = Touch Sensor Release On Display (Touch Only)
Reason 0x07 = Barcode Read (BCR Only)
The host can use Property 1.2.7.1.2.1 User Event Notification Controls Enable to enable these notification reasons individually.
The host may choose to use these notifications to determine when to send additional commands. For example, it may send Command 0x1001 - Start Transaction. The host should do this as quickly as possible to minimize the response time between when the cardholder presents a card and when the device provides feedback via a visible or audible state change or attempts to read a chip card. Note there are cases where the device may send a notification with Reason = Contactless Card Presented while the cardholder is inserting or swiping a card, so the host should start transactions with all supported card interfaces enabled to maximize the chances of a successful card read.
01
00
00
00
User Event, Contactless Card Presented, EMV, Reserved (EMV Contactless Only)
01
01
00
00
User Event, Contactless Card Removed, EMV, Reserved (EMV Contactless Only)
01
00
01
00
User Event, Contactless Card Presented, NTag/MIFARE Ultralite, Reserved (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
01
00
User Event, Contactless Card Removed, NTag/MIFARE Ultralite, Reserved (EMV Contactless Only)
01
00
02
00
User Event, Contactless Card Presented, MIFARE Classic, 1K (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
02
00
User Event, Contactless Card Removed, MIFARE Classic, 1K (EMV Contactless Only)
01
00
03
00
User Event, Contactless Card Presented, MIFARE Classic, 4K (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
03
00
User Event, Contactless Card Removed, MIFARE Classic, 4K (EMV Contactless Only)
01
00
04
00
User Event, Contactless Card Presented, MIFARE DESFire Light (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
04
00
User Event, Contactless Card Removed, MIFARE DESFire Light (EMV Contactless Only)
01
00
05
00
User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
05
00
User Event, Contactless Card Removed, MIFARE MINI® (EMV Contactless Only)
01
00
06
00
User Event, Contactless Card Presented, MIFARE Plus EV1 (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
06
00
User Event, Contactless Card Removed, MIFARE Plus EV1 (EMV Contactless Only)
01
00
07
00
User Event, Contactless Card Presented, MIFARE Plus EV2 (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
07
00
User Event, Contactless Card Removed, MIFARE Plus EV2 (EMV Contactless Only)
01
00
08
00
User Event, Contactless Card Presented, MIFARE Plus SE (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
08
00
User Event, Contactless Card Removed, MIFARE Plus SE (EMV Contactless Only)
01
00
09
00
User Event, Contactless Card Presented, MIFARE Plus X (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
09
00
User Event, Contactless Card Removed, MIFARE Plus X (EMV Contactless Only)
01
00
0A
00
User Event, Contactless Card Presented, MIFARE DESFire EV1 (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
0A
00
User Event, Contactless Card Removed, MIFARE DESFire EV1 (EMV Contactless Only)
01
00
0B
00
User Event, Contactless Card Presented, MIFARE DESFire EV2 (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
0B
00
User Event, Contactless Card Removed, MIFARE DESFire EV2 (EMV Contactless Only)
01
00
0C
00
User Event, Contactless Card Presented, MIFARE DESFire EV3 (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table 348 - Notification Payload for UID. A sample notification is shown here: Table 349 – Notification Payload for UID Example
01
01
0C
00
User Event, Contactless Card Removed, MIFARE DESFire EV3 (EMV Contactless Only)
01
02
00
00
User Event, Card Seated in Slot, Reserved, Reserved (EMV Contact Only)
01
03
00
00
User Event, Card Unseated from Slot, Reserved, Reserved (EMV Contact Only)
01
04
00
00
User Event, Card Swiped, Reserved, Reserved (MSR Only). When the host receives this notification, it should call Command 0x1001 - Start Transaction before the timeout configured in Property 1.2.7.1.2.2 User Event Notification MSR Data Timeout (MSR Only) to process the MSR swipe data the device is temporarily storing in memory.
01
05
00
00
User Event, Touch Sensor Press On Display, Reserved, Reserved (Touch Only). These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table 342.
01
06
00
00
User Event, Touch Sensor Release On Display, Reserved, Reserved (Touch Only). These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table 342.
01
07
00
00
Type values:
Type 0x00 = Unknown
Type 0x01 = MagTek
Type 0x02 = EMV
The barcode reader has successfully read a barcode. In this case, the device includes barcode data in the Notification Payload portion of the Notification Message. If the data is encrypted, the data is in the format described in Table 357 - Notification Payload for Personal Info Entry and Table 358 - Notification Payload for Personal Info Entry. Data that is not encrypted is in the format described in Table 360.
Table - Notification Detail Codes - Category 0x02 — Session Management
Category 0x02 Session Management contains notification detail codes involving session management functionality (Session Management Only). Each possible notification has a unique Reason value:
Reason 0x00 = Session Expiring Soon
Session Management, Session Expiring Soon, Reserved, Reserved
0 2
0 0
0 0
0 0
The device sends this notification 5 minutes before a session expires and every minute after that until the session is extended or the connection is closed. The host can optionally extend the session with Command 0x1F03 - Extend Session or by sending any command request. These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table 344.
Table - Notification Detail Codes - Category 0x03 — Key Management (WLAN Only)
Category 0x03 Key Management contains notification detail codes involving key management functionality (WLAN Only). Each possible notification has a unique Reason value:
Reason 0x00 = CSR keys generated
Reason 0x01 = Certificate Expiring Soon
Key management, CSR keys generated, Reserved, Reserved
0 3
0 0
0 0
0 0
This notification does not include a Notification Payload. See Command 0xEF02 – Generate CSR keys (WLAN Only) for more information.
0 3
0 1
0 0
0 0
Key management, Certificate Expiring Soon, Reserved, Reserved. See Property 1.2.2.1.1.B Certificate Expiring Soon Notification Threshold for more information. These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table 346 - Notification Payload for Key management, Certificate Expiring Soon.
Table - Notification Detail Codes - Category 0x04 — Temperature
Category 0x04 Temperature contains notification detail codes involving temperature reporting. Each possible notification has a unique Reason value:
Reason 0x00 = Temperature out of range
Temperature, Out of Range, Low Warning, Temperature
0 4
0 0
0 0
0 0
The device sends this notification when the device’s temperature falls below the temperature set in Low Temperature Notification Level (1.2.7.1.4.1). The temperature reported is in Celsius.
0 4
0 0
0 1
0 0
Temperature, Out of Range, High Warning, Temperature. The device sends this notification when the device’s temperature rises above the temperature set in High Temperature Notification Level (1.2.7.1.4.2). The temperature reported is in Celsius.
The device sends this notification when the battery charge reaches 15 percent. If a device is powered on with a charge that is already 15 percent or below, this notification is sent shortly after power up and includes the current battery charge percentage. Percent indicates the percent of battery charge remaining.
It is recommended that the device is charged using a USB power source soon after receiving this notification. See Table 14 - Notification Message Format and Table 337 Low Battery Notification Example.
Charge the device using a USB power source soon after receiving this notification.
Table - Low Battery Notification Example
The device sends this notification one minute before it automatically powers down the device. This occurs when the battery charge has reached 0 percent. Shutdown can be prevented by connecting the device to a USB power source. See Table 14 - Notification Message Formatand Table 338 Low Battery Shutdown Response Example.
Table - Low Battery Shutdown Response Example
The device sends this notification when the battery charger detects that the battery is fully charged. This only occurs when the device is powered by a USB power source. See Table - Notification Message Formatand Table - Battery Charged Notification Example.
Table - Battery Charged Notification Example
Table - Notification Payload for Device Reset Occurred
Beginning of Notification Message
1001 = Device Information Update
81
var
This parameter has the same length and value described by Property 2.3.1.2.1.1 Device Operational Status.
B
R
82
var
This parameter has the same length and value described by Property 2.3.1.2.1.2 Offline Status Detail.
B
R
xx
var
More data objects may be added in future firmware revisions.
End of Notification Message
Table - Notification Example for Device Reset Occurred
Table - Notification Payload for Touch Sensor Press or Release On Display (Touch Only)
Beginning of Notification Message
1001 = Device Information Update
81
04
Press / Release Coordinates Coordinates of the press / release from origin 0,0 at the top left corner of the display, automatically adjusted to match the device’s orientation as configured by Property 1.2.3.1.1.2 Custom Idle Page Image Device Locked (Display Only). Bytes 1..2 X Coordinate X coordinate of press / release, in big endian order. Bytes 3..4 Y Coordinate Y Coordinate of press / release, in big endian order.
B
R
End of Notification Message
Table - Notification Example for Touch Sensor Press or Release On Display (Touch Only)
Table - Notification Payload for Session Expiring Soon (Session Management Only)
Beginning of Notification Message
1001 = Device Information Update
81
1
Interface 0x00 = WLAN
B
R
82
1
Connection 0x00 = Connection 0, Interfaces that only support one connection will use connection 0. WLAN will always set this to 0 even if the device is configured to support more than one connection with Property 1.2.2.1.1.A Maximum Client Connectionssince there is only a single session for all clients. See **Command 0x1F03 - Extend Session (Session Management Only)**for more information on this scenario.
B
R
83
1
Expiration Time The time in minutes until the session expires.
B
R
xx
var
More data objects may be added in future firmware revisions.
End of Notification Message
Table - Notification Example for Session Expiring Soon (Session Management Only)
Table - Notification Payload for Key management, Certificate Expiring Soon (Session Management Only)
Beginning of Notification Message
1001 = Device Information Update
81
1
This parameter has the same length and value described by Property 1.2.2.1.1.B Certificate Expiring Soon Notification Threshold.
B
R
82
1
This parameter contains the certificate identifier. See the certificate file type section (File Type 0x03) from Table 206 to identify this certificate by locating the certificate that has a File Subtype that matches this certificate identifier.
B
R
83
1
The number of days the certificate is still valid.
B
R
End of Notification Message
Table - Notification Example for Key management, Certificate Expiring Soon (Session Management Only)
Table - Notification Payload for UID
Beginning of Notification Message
1001 = Device Information Update
84
var
NFC Payload
B
R
/DF79
var
NFC UID
B
R
End of Notification Message
Table – Notification Payload for UID Example
Last updated