MoBIB

The MoBIB container facilitates communication with card readers and inserted MoBIB smart cards. The T1C-JLIB client library provides functionality to communicate with the smart card and facilitates integration into a native or Java application. This document describes the functionality provided by the MoBIB container on the T1C-GCL (Generic Connector Library).

Get MoBIB container object

For more information on how to configure the T1C-JLIB client library see Client Configuration. Initialize a gclClient:

LibConfig conf = new LibConfig();
conf.setEnvironment(Environment.DEV);
conf.setDsUri(DS_URI);
conf.setOcvUri(OCV_URI);
conf.setGclClientUri(URI_T1C_GCL);
conf.setApiKey(API_KEY);
conf.setHardwarePinPadForced(false);
conf.setDefaultPollingIntervalInSeconds(5);
conf.setDefaultPollingTimeoutInSeconds(10);
conf.setSessionTimeout(60);
T1cClient t1cClient = new T1cClient(conf);

Obtain the GclReader object

The constructor for the MoBIB containers expects a valid reader-object as parameter. A reader-object can be obtained from the exposed core functionality, for more information see Core Services. Core services responds with available card-readers, available card in a card-reader, etc. For example: In order to get all connected card-readers, with available cards:

List<GclReader> reader = t1cClient.getCore().getReadersWithInsertedCard();

This function call returns a list of the following objects:

com.t1t.t1c.GclReader

com.t1t.t1c.GclCard

We notice that a card object is available in the response in the context of a detected reader. The reader in the example above is Bit4id miniLector, has no pin-pad capabilities, and there is a card detected with given ATR and description "MOBIB Card". An ATR (Answer To Reset) identifies the type of a smart-card. The container must be instantiated with the GclReader object containing the MoBIB card:

MobibContainer container = client.getMobibContainer(reader);

All methods for the mobib container will use the selected reader - identified by the reader-object.

Card data

Status

The MoBIB card can be locked, this means that application(s) on the MoBIB card have been locked by operators. To retrieve this information, the status of the MoBIB card can be requested. Note that this is not related to the expiry date of the card. The service can be called:

Boolean activated = container.getStatus();

Response:

java.lang.Boolean

Card Issuing

The MoBIB card contains a information about the holder of the card.

The service can be called:

GclMobibCardIssuing cardIssuing = container.getCardIssuing();

Response:

com.t1t.t1c.containers.smartcards.mobib.GclMobibCardIssuing

Picture

Contains the card holder's picture stored on the smart card. The service can be called:

String picture = container.getPicture();

Response:

"/9j/4AAQSkZJRgABA...59aVpcklSDzyKUTEDGK//9k="

Contracts

The MoBIB card can contains contracts written by the operators (e.g. SNCB, De Lijn, MIVB, TEC).

The service can be called:

List<GclMobibContract> contracts = container.getContracts();

Response:

com.t1t.t1c.containers.smartcards.mobib.GclMobibContract

com.t1t.t1c.containers.smartcards.mobib.GclMobibSpatial

com.t1t.t1c.containers.smartcards.mobib.GclMobibTariff

com.t1t.t1c.containers.smartcards.mobib.GclMobibCounter

com.t1t.t1c.containers.smartcards.mobib.GclMobibValidityDuration

Data Filter

Filter Card Data

All data on the smart card can be dumped at once, or using a filter. In order to read all data at once:

GclMobibAllData allData = container.getAllData();

Response:

The filter can be used to ask a list of custom data containers. For example, we want to read only the 'rn', 'picture' and 'rrn certificate':

List<String> filter = Arrays.asList("status","card-issuing");
// Or retrieve available data filters as follows:
// filter = container.getAllDataFilters();
GclMobibAllData allData = container.getAllData(filter);