UBM31 Family

UBM31-G21 on SLE77CLFX2400PM

Application Related Characteristics | Primitive Support  | Implementation Specific Characteristics | Codelets Available

 

External Characteristics

Data Item

Value

Comments

External Specification

MULTOS Version

4.2.1

 

Silicon Provider / manufacturer_id

Infineon / 0x05

 

Implementers / implementer_id

UBIVELOX / 0x07

 

Mask / ic_type

UBM31-G21 / 0x01

 

Technical Data for Contact based interface

Power / External Clock

1.62V to 5.5V / 1 to 10 MHz

 

Transport Protocol

T=0, T=1

 

FI/DI

0x01, 0x02, 0x03, 0x08,

0x11, 0x12, 0x13, 0x18,

0x32, 0x33, 0x34, 0x38,

0x92, 0x93, 0x94, 0x95,

0x96

 

Dual ATR

Supported

 

PPS

Supported

 

ATR Character Convention Direct LSB (3B)

Supported

 

ATR Character Convention Indirect MSB (3F)

Supported

 

Technical Data for Contactless based interface

Transport Protocol

Type A, MIFARE

 

Pre-enablement contactless protocol

106kB, Type A, CID

supported,

MIFARE enabled

Pre-enablement ATS:

14 78 80 70 02 80 31 E0 6B 84 21 02 07 00 55 55 55 55 55 55 20 2B

Post-enablement contactless protocol

106kB, Type A, CID

supported,

MIFARE enabled

AMD 0129v001

Post-enablement ATS:

14 78 80 70 02 80 31 E0 6B 84 21 02 07 00 55 55 55 55 55 55 20 2B

Memory Area Sizes

AMD

0129v001

 

Flash

240K

 

RAM Public

529 bytes

 

RAM Dynamic

1024 bytes

 

EEPROM Total

40K

 

EEPROM available for applications

36904 bytes

 

 


Application Related Characteristics

Data Item

Value

Comments

Application EEPROM Loading Requirements

Application Header

62 Bytes

 

Total temporary space per protected ALU

Variable

It is dependent on application provider key size.

Total temporary space per confidential ALU

Variable

It is dependent on KTU size.

MULTOS Application Function

Static Page Size (1 page)

64 Bytes

 

Maximum write size in pages

At least 9 pages

Limited by free EEPROM

Maximum ATR File record size

32 Bytes

 

Maximum ATR Historical Byte record size

15 Bytes

 

Maximum DIR File record size

255 Bytes

 

Maximum FCI record size

255 Bytes

 

Maximum inbound TPDU size

260 Bytes

 

Maximum outbound TPDU size

261 Bytes

 

Maximum delegation nest count

Limited by available

EEPROM

 

Maximum application history list entries

10

 

Retry Counters

Set MSM Controls

30

 

Create MEL Application

15

 

Delete MEL Application

20

 

Key Lengths

KCK Public Key length

128 Bytes

 

Permitted Application Provider Public Key lengths

32 to 128 Bytes

 

MULTOS TKCK length

128 Bytes

 

Primitive Support

The primitives listed here are those that were included in the target specification.

Primitive

Supported

Optional / Mandatory

AddBCDN

Yes

 

BitManipulateByte

Yes

 

BitManipulateWord

Yes

 

CallCardBlock

Yes

 

CallCodelet

Yes

 

CheckCase

Yes

 

Checksum

Yes

 

ControlAutoResetWWT

Yes

 

Delegate

Yes

 

DESECBDecipher

Yes

 

DESECBEncipher

Yes

 

DivideN

Yes

 

EccAdd

No

 

EccConvert

No

 

EccEqual

No

 

EccInv

No

 

EccMult

No

 

EccVerify

No

 

ExchangeData

Yes

 

GenerateAsymmetricHashGeneral

Yes

 

GenerateAsymmetricSignatureGeneral

Yes

 

GenerateDESCBCSignature

Yes

 

GenerateRandomPrime

No

 

GenerateTripleDESCBCSignature

Yes

 

GetData

Yes

 

GetDelegatorAID

Yes

 

GetDIRFileRecord

Yes

 

GetFileControlInfo

Yes

 

GetManufacturerData

Yes

 

GetMemoryReliability

Yes

 

GetMULTOSData

Yes

 

GetPurseType

Yes

 

GetRandomNumber

Yes

 

LoadCCR

Yes

 

Lookup

Yes

 

Memory Compare

Yes

 

Memory Compare Fixed Length

Yes

 

Memory Copy

Yes

 

Memory Copy Fixed Length

Yes

 

MemoryCopy

Yes

 

Modular Exponentiation

Yes

 

Modular Exponentiation CRT

Yes

 

Modular Inverse

No

 

ModularMultiplication

No

 

ModularReduction

No

 

MultiplyN

Yes

 

Query0, Query1, Query2, Query3

Yes

 

QueryChannel

Yes

 

QueryCodelet

Yes

 

QueryInterfaceType

Yes

 

ResetSessionData

Yes

 

ResetWWT

Yes

 

ReturnFromCodelet

Yes

 

SEEDECBDecipher

Yes

 

SEEDECBEncipher

Yes

 

SetAFI

Yes

 

SetATRFileRecord

Yes

 

SetATRHistChars

Yes

 

SetATSHistChars

Yes

 

SetFCIRecord

Yes

 

Set Select SW

Yes

 

Set Transaction Protection

Yes

 

SHA-1

Yes

 

ShiftLeft

Yes

 

ShiftRight

Yes

 

StoreCCR

Yes

 

SubtractBCDN

Yes

 

VerifyAsymmetricAndRetrieveGeneral

Yes

 

 

Implementation Specific Characteristics

Zero Block Size

The following instructions and primitives have the block size specified in the code (as opposed to being run-time data). The following table shows how each will perform if a zero block size is specified.

 

Type

Instruction / Primitive

Operation

Instruction

LOAD, STORE, LOADI, STOREI, CLEAN

No operation

TESTN, INCN, DECN, NOTN

ANDN, ORN, XORN

Z=1

CMPN, ADDN, SUBN

C=0, Z=1

Primitive

MultiplyN

Z=1

DivideN

C=1, Z=Unchanged

ShiftLeft, ShiftRight

C=0, Z=1

GetDIRFileRecord

GetFCIContolInformation

One byte set to zero pushed onto stack,

If the application specified does not exist, C =1, Z = 1

If the application specified exists, C = 0, Z = 0

GetManufacturerData

GetMULTOSData

GetPurseType

One byte set to zero pushed onto stack, C = 0

MemoryCompareFixedLength

DT’ = DT - 4, Z = 1

MemoryCopyFixedLength

DT’ = DT - 4

 

Maximum Number of Pages Permitted in a Single Write

The maximum number of pages is at least sixteen when transaction protection is used. It is possible to write more than twenty pages if there is free EEPROM. Note that if an attempt is made to write more than 16 pages and if there is insufficient free EEPROM, then an abnormal end to processing to will occur.

 

Condition Code Register

This implementation does support signed arithmetic. The N and V flags are present in the CCR, and they may be changed by some instructions. However, signed arithmetic is not guaranteed and should be avoided. They may be used by an application using the Load CCR and Store CCR primitives, but this may affect the portability of the application.

 

 

Important Remarks

This section contains important remarks about the Primitives and IFD commands of this implementation.

 

Functionality

Operation

Delegate

When the application issues the Delegate primitive, Dynamic (Only the part used) and application control information on the issued application save once to area of EEPROM(Delegation stack).

Therefore, the application developer should consider EEPROM writes in every Delegate primitive issuance.

 

Codelet Available

There is one codelet available:

· 0062 MULTOS MICA Codelet 1414 Release 2 Update 1