4.2.101 EFIPS (IMEI(SV) Pairing Status)
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
The EFIPS file stores the status of USAT Application Pairing checking.
This file shall be present if USAT Application Pairing is supported as defined in this specification.
The status flag of pairing check (with value "OK" or "KO") stored in the file EFIPS can be read by any terminal hosting the UICC. The information stored in the file EFIPS provides a mechanism to detect changes of association between a USIM and a MTC ME. The information stored in the file EFIPS can be read locally by e.g. the maintenance person.
Structure of EFIPS
|
Identifier: ‘6FF1’ |
Structure: Cyclic |
Optional |
||||
|
Record length: 4 bytes |
Update activity: high |
|||||
|
Access Conditions: READ ALWAYS UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1-2 |
Status of the last pairing procedure (detail 1) |
O |
2 bytes |
|||
|
3 |
Link to a record of EFIPD (detail 2) |
O |
1 byte |
|||
|
4 |
Reserved for future use |
– |
1 byte |
|||
Due to the frequency of the pairing procedure, it is recommended that this file contain at least 100 records.
Detail 1:
These 2 bytes contain the status of the last pairing procedure as defined below:
– If the pairing is successful then:
1. Byte 1 is the character "O"
2. Byte 2 is the character "K"
– If the pairing is not successful then:
1. Byte 1 is the character "K"
2. Byte 2 is the character "O"
The characters are coded using the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0.
Detail 2:
This byte contains a link to a record of EFIPD file:
– Unsigned integer coded from ’01’ to ‘FE’