4.2.90 EFNCP-IP (Network Connectivity Parameters for USIM IP connections)

31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS

If service n°80 is "available", this file shall be present.

This EF contains the network activation parameters to be used by the ME for establishing a data channel (e.g. PDP context activation) for UICC remote IP connectivity as described in ETSI TS 102 483 [50].

Each record contains a network connectivity parameters set. A network connectivity parameters set may comprise an Access Point Name, a Login and Password of the Access Point Name, a Data Destination Address Range and the Bearer Description. The priority order of the different Network Connectivity Parameters sets is the same as the order of the record numbers.

Each network connectivity parameters set provides a condition and the network connectivity parameters to be used when this condition is met:

– The network activation parameters present in a record shall be associated with this Data Destination Address Range in the same record (i.e. if a record contains a Data Destination Address Range, all IP packets that are sent by the UICC to any network destination address belonging to this Address Range shall transit through a network connection established using the parameters provided in that record).

Note: A Data Destination Address Range TLV with a zero length prefix matches all addresses of the address type.

In a record, if the Access Point Name has a value part, the associated Login and Password may be provided. If supported by the ME, the Login and Password may be used for Access Point Name authentication. If only the Login is present, the ME shall use its default Password configuration if any. If the Login and Password are not present, the ME shall use its default Login/Password configuration if any. If no authentication is requested, the Login and Password shall be ignored. The Password TLV can only be provided in a record if a Login TLV is provided in the same record.

In any record, if the Access Point Name has no value part, the ME may use its default Access Point Name or the default subscription value together with the other network connectivity parameters of that record.

When present, the Bearer Description TLV provides recommended values for parameters that the ME should use to establish the data link for UICC remote IP connections. However if the ME or network does not support these values, the ME selects the most appropriate values.

Structure of EFNCP-IP

Identifier: ‘6FE2’

Structure: linear fixed

Optional

Record length: Z bytes

Update activity: low

Access Conditions:

READ PIN

UPDATE ADM

DEACTIVATE ADM

ACTIVATE ADM

Bytes

Description

M/O

Length

1 to M

Data Destination Address Range TLV

M

M bytes

M+1 to M+N

Access Point Name TLV

M

N bytes

M+N+1 to M+N+O

Login TLV

C

O bytes

M+N+O+1 to M+N+O+P

Password TLV

C

P bytes

M+N+O+P+1 to M+N+O+P+Q

Bearer description TLV

C

Q bytes

‑ Data Destination Address Range TLV

Contents: the data destination address or the range of data destination addresses.

Coding: the coding of the Data Destination Address Range TLV object is described hereafter.

Length

Description

Value

Status

1 byte

Data Destination Address Range Tag

83

M

1 byte

Length (see note1)

X

M

1 byte

Type of Address

M

1 byte

Prefix length (in bits)

’00’ to ’20’ for IPv4

’00’ to ’80’ for IPv6

M

0 to 16 bytes

Prefix

Note 1: coded according to ISO/IEC 8825-1 [35].

‑ Type of Address

Contents: the type of data destination address range.

Coding:

– ’21’ = IPv4 address range;

– ’57’ = IPv6 address range;

– Other values are RFU.

– Prefix length

Contents: the number N of valid bits of the prefix of the address range. A prefix length of zero denotes the default "all IP addresses" range.

Coding: binary

‑ Prefix

Contents: Prefix, i.e. the leftmost bits of the address range. All addresses where the leftmost N bits match the prefix belong to the address range.

Coding:

– the leftmost N bits encode the prefix of the address range. If N is not an integer multiple of 8, the prefix is right padded with zeroes to the next octet boundary.

‑ Access Point Name TLV

Contents: Access Point Name provides information to the ME necessary to identify the Gateway entity which provides interworking with an external packet data network.

Coding: the coding of the Access Point Name TLV object is described hereafter. The Access Point Name Value is coded as defined in TS 23.003 [25].

Length

Description

Value

Status

1 byte

Access Point Name Tag

80

M

1 byte

Length (see note 1)

W

M

W bytes

Access Point Name Value

M

Note 1: coded according to ISO/IEC 8825-1 [35].

‑ Login TLV

Contents: the login of the Access Point Name.

Coding: the coding of the Login TLV object is described hereafter. The Login Value is coded as for SMS Data coding scheme defined in TS 23.038 [5]. Parts of the data coding scheme other than the character set indication shall be ignored.

Length

Description

Value

Status

1 byte

Login Tag

81

M

1 byte

Length (see note 1)

X

M

X bytes

Login Value

M

Note 1: coded according to ISO/IEC 8825-1 [35].

‑ Password TLV

Contents: the password of the Access Point Name.

Coding: the coding of the Password TLV object is described hereafter. The Password Value is coded as for SMS Data coding scheme defined in TS 23.038 [5]. Parts of the data coding scheme other than the character set indication shall be ignored.

Length

Description

Value

Status

1 byte

Password Tag

82

M

1 byte

Length (see note 1)

Y

M

Y bytes

Password Value

M

Note 1: coded according to ISO/IEC 8825-1 [35].

‑ Bearer Description TLV

Contents: bearer description.

Coding: the coding of the Bearer Description TLV object is described hereafter. The Bearer Description Value is encoded as the value part of the "Bearer description" TLV data object defined in TS 31.111 [12].

Length

Description

Value

Status

1 byte

Bearer Description Tag

84

M

1 byte

Length (see note 1)

Z

M

Z bytes

Bearer Description Value

M

Note 1: coded according to ISO/IEC 8825-1 [35].

Any unused bytes shall be set to ‘FF’.