(7/30/26 Draft version) Property 1.2.9.nnn - Enable Mobile Document Features
The Mobile Document (mDoc) module contains device properties used to configure Mobile Document functionality. The initial release provides a subscription property that defines the licensed operating period for ISO 18013-5 mobile driver's license (mDL) and mobile passport (mPass) transactions. This module is supported on DynaFlex II and is structured to allow additional Mobile Document properties in future releases.
Component 1: Mobile Document Configuration
This component contains configuration properties for Mobile Document operation. The initial property, Mobile Document Subscription (OID 1.2.9.1.1.1), defines the inclusive ValidFrom and ValidTo dates during which Mobile Document transactions are permitted. Additional Mobile Document configuration properties may be added in future releases.
Property 1.2.9.1.1.1 - Mobile Document Subscription
The Mobile Document Subscription property defines the subscription period during which the device is licensed to process Mobile Document (mDL and mPass) transactions. The host provisions the ValidFrom and ValidTo dates as 32-bit Unix epoch timestamps. Mobile Document transactions are permitted only when the current device date falls within the configured subscription date range and the device RTC is valid.
Property 1.2.9.1.1.1 - Mobile Document Subscription
Property OID
1.2.9.1.1.1 / 0x010209010101
Name
Mobile Document Subscription
Description
Set the subscription period using a secured OID that stores ValidFrom (bytes 0–7) and ValidTo (bytes 8–15) as 64-bit Unix epoch timestamps. The OID shall be written using D112 (Set Property – Secured) encapsulated in EEEE (Send Secured Command to Device).
The payload uses 64-bit Unix epoch timestamps for forward compatibility. On current devices, each timestamp shall fit within a 32-bit Unix epoch value; therefore, the most-significant four bytes of each 64-bit field shall be 00 00 00 00.
The payload consists of two 64-bit Unix epoch timestamps:
Bytes 0–7 — ValidFrom
· Unsigned 64-bit Unix epoch timestamp, little-endian
Bytes 8–15 — ValidTo
· Unsigned 64-bit Unix epoch timestamp, little-endian
Disable subscription: All 16 bytes = 0x00.
Enable example (2026-07-14 through 2027-07-14):
· ValidFrom: 0x000000006A557C00 (2026-07-14 00:00:00 UTC) LE
· ValidTo: 0x000000006C36AF80 (2027-07-14 00:00:00 UTC) LE
· Full payload: 00 7C 55 6A 00 00 00 00 80 AF 36 6C 00 00 00 00
Validation rules (SET rejected if violated):
· Length must be exactly 16 bytes.
· Both timestamps equal to 0x0 are accepted (disables subscription).
· One timestamp equal to 0x0 and the other non-zero is rejected.
· ValidFrom shall be less than or equal to ValidTo.
· Each timestamp shall have the most-significant four bytes set to 00 00 00 00 and shall not represent a date later than 2099-12-31 23:59:59 UTC.
Securing Key
Refer to Command 0xD112 – Set Property (Secured). SET shall be delivered using Command 0xEEEE - Send Secured Command to Device.
Min. Len (b)
16
Max. Len (b)
16
Data Type
Binary
Valid Values
Each timestamp shall represent a HEX epoch date from 1970-01-01 00:00:00 UTC through 2099-12-31 23:59:59 UTC
Default
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (Disabled)
Get Request Example
Example (Hex)
AA00 81040155 D101 840F D101 850101 870402090101 8902 C100
Get Response Example
Example (Hex)
AA0081048255D1018204000000008482001FD1018501018704020901018912C11000000000000000000000000000000000
Set Request Example
Example (Hex)
AA008104019CD112846BEEEEA1198105030306000084008500A80A81021111820086008800A9008204BE0011308308F20E121D2DC15FD3842AD11281072B06010401F609850101891AE218E916E114E112C1108058446A0000000000655D6A000000009E1043F302CE2102264069FB7D76A77A36C8
Set Response Example
Example (Hex)
AA0081048255D1018204000000008482001FD1018501018704020901018912C1108058446A0000000000655D6A00000000
Property 1.2.9.1.1.2 - Mobile Document Expiration Notification
The Mobile Document Expiration Notification property controls subscription expiration notifications. It determines how many days before the subscription date the device begins notifying the host. It also specifies the minimum number of hours between notifications. Notifications are generated only when a host MMS command channel is available.
Property 1.2.9.1.1.2 - Mobile Document Expiration Notification
Property OID
1.2.9.1.1.2 / 0x010209010102
Name
Mobile Document Expiration Notification
Description
Specifies when the device begins sending Subscription Expiring Soon notifications before the configured subscription expiration date, and how frequently those notifications are sent.
Byte 0
0x00 = Notifications disabled
0x01–0x5A (1–90) = Start notifying this many days before ValidTo;
Send once per calendar day while
ValidTo − N (Byte0) ≤ today ≤ ValidTo
Example:
ValidTo = 2027-07-01
Byte0 = 0x03
Notifications are sent on these dates:
2027-06-28
2027-06-29
2027-06-30
2027-07-01
Byte 1
0x01–0x18 (1–24) = Send one notification every N hours
Securing Key
None
Min. Len (b)
2
Max. Len (b)
2
Data Type
Binary
Valid Values
0 - 90 (days), 1 – 24 (hours)
Default
0x05 0x03 Start notifications 5 days before ValidTo; repeat every 3 hours
Get Request Example
Example (Hex)
AA00 81040155 D101 840F D101 850101 870402090101 8902 C200
Get Response Example
Example (Hex)
AA0081048255D10182040000000084820011D1018501018704020901018904C2020503
Set Request Example
Example (Hex)
AA008104010CD1118411D1118501018704020901018904C2020501
Set Response Example
Example (Hex)
AA008104820CD11182040000000084820011D1118501018704020901018904C2020501
Last updated