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
The EFIPD contains the IMEI(SV) as defined in TS 23.003 that was used in the USAT Application Pairing procedure.
This file shall be present if USAT Application Pairing is supported as defined in this specification.
Identifier: '6FF2'
Structure: linear fixed
Optional
Record length: X+2 bytes (X≥8)
Update activity: high
Access Conditions:
READ
ADM
UPDATE
ADM
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1 to X+2
IMEI or IMEISV TLV object
M
X+2 bytes
IMEI(SV) TLV object
The content and coding is defined below, where IMEI and IMEISV are defined in TS 23.003:
Coding of the IMEI TLV object
If service No. 106 and service No. 107 are "available", this file shall be present.
This EF contains zero or more Home Evolved Packet Data Gateway (ePDG) Identifier data objects as defined in the "Selection of the ePDG" UE procedure of TS 24.302.
Identifier: '6FF3'
Structure: transparent
Optional
File size: >X bytes
Update activity: low
Access Conditions:
READ
PIN
UPDATE
ADM
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1 to X
Home ePDG identifier TLV data object
O
X bytes
X+1 to Y
Home ePDG identifier TLV data object
O
Y-X bytes
…
Home ePDG Identifier TLV data object
Contents:
Address of Evolved Packet Data Gateway, in the format of a FQDN, an IPv4 address, or an IPv6 address.
Coding:
The tag value of this Home ePDG Identifier TLV data object shall be '80'. The format of the data object is as follows:
Field
Length (bytes)
Tag
1
Length
1
Address Type
1
Home ePDG Address
Address Length
Address Type:
Type of the ePDG address.
This field shall be set to the type of the ePDG address according to the following:
Value
Address Type
'00'
FQDN
'01'
IPv4
'02'
IPv6
All other values are reserved
ePDG Address:
Address of the Evolved Packet Data Gateway
Contents:
This field shall be set to the address of the ePDG.
Coding:
When the Address Type is set to '00', the corresponding ePDG FQDN Address shall be encoded to an octet string according to UTF-8 encoding rules as specified in RFC 3629.
When the Address Type is set to '01', the corresponding ePDG IPv4 Address is in octet 5 to octet 8 of the Home ePDG Identifier TLV data object. Bit 8 of octet 5 represents the most significant bit of the IP address and bit 1 of octet 8 the least significant bit.
When the Address Type is set to '02', the corresponding ePDG IPv6 Address is in octet 5 to octet 20 of the Home ePDG Identifier TLV data object. Bit 8 of octet 5 represents the most significant bit of the IP address and bit 1 of octet 20 the least significant bit.
If service No. 106 and service No. 107 are "available", this file shall be present.
This EF contains Evolved Packet Data Gateway (ePDG) selection information for one or more PLMNs as defined in the "Selection of the ePDG" UE procedure of TS 24.302.
Identifier: '6FF4'
Structure: transparent
Optional
File size: Z bytes
Update activity: low
Access Conditions:
READ
PIN
UPDATE
ADM
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1 to Z
ePDG selection information TLV data object
O
Z bytes
The file contains one ePDG selection information TLV data object. The ePDG selection information TLV data object contains a list of PLMNs which are preferred for ePDG selection. The list of PLMNs may include the HPLMN. For each PLMN, it is indicated:
the preference order (priority) given to ePDG of a PLMN and
whether selection of an ePDG in such PLMN should be based on Tracking/Location Area Identity FQDN or on Operator Identifier FQDN,
as specified in the "Selection of the ePDG" UE procedure of TS 24.302.
A BCD value of 'D' in any of the MCC and/or MNC digits shall be used to indicate a "wild" value for that corresponding MCC/MNC digit.
A value of 'DDDDDD' represents "any PLMN" value.
ePDG Priority
Contents:
The PLMN Priority represents the preference order given to ePDGs of a PLMN.
Coding:
ePDG Priority value is coded as a 2-Byte integer.
ePDG FQDN format
Contents:
Indicates whether the selection of an ePDG in this PLMN should be based on Tracking/Location Area Identity FQDN or on Operator Identifier FQDN (see TS 24.302).
Coding:
'00': Indicates that Operator Identifier FQDN format shall be used (see TS 24.302).
'01': Indicates that location based FQDN format shall be used (see TS 24.302).
If service No. 111 and service No. 110 are "available", this file shall be present.
This EF contains zero or more Emergency Evolved Packet Data Gateway (ePDG) Identifier data objects.
If service No. 111 and service No. 110 are "available", this file shall be present.
This EF contains Evolved Packet Data Gateway (ePDG) selection information for Emergency Services.
Identifier: '6FF6'
Structure: transparent
Optional
File size: Z bytes
Update activity: low
Access Conditions:
READ
PIN
UPDATE
ADM
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1 to Z
ePDG selection information for Emergency Services TLV data object
If service No. 114 is "available", this file shall be present.
It shall be possible to define if the UE uses the From header field for the determination of the originating party identity in the OIP service. For more detailed description see clause 4.5.2.12 of TS 24.607.
Identifier: '6FF7'
Structure: transparent
Optional
File size: n bytes
Update activity: low
Access Conditions:
READ
PIN
UPDATE
ADM
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1
Status
M
1 byte
Status
Contents
Status byte indication if From header field is used or not.