NOD clients

Pickup of an OrderGroup is always performed in the same way regardless of what order is picked up, or which scenario Pickup follows. A NOD Client declares what properties it possesses when a Pickup is initiated in the form of Capabilities and then follows the slavish client commands it receives until no more. NOD adjusts the Client commands returned to which Capabilities the client possesses. This means that future client-side functionality can be rolled out without existing NOD Clients having to be upgraded. See [HB206.22] for which Capabilities NOD Platform has or is planning support.

Following are the most important Capabilities a NOD Client can support today:

• 9: Client supports Media Independent Mobile 2D Barcode.

• 16: Client supports DESFire APDU commands.

• 27: Client supports display of Messages

• 7: Client supports UltraLight APDU commands.

When placing an Order in an Order Group, a requirement for a minimum of Capabilities is built up for the order to be picked up by Clients. This mechanism means that an Order Group can never be picked up by Clients who cannot execute all Orders in the Order Group. To develop a NOD Client for displaying mobile tickets, the NOD Client must at a minimum support Capability 9. That is, the NOD Client must be able to execute the client command qrTicketCommand.