10.5.6 Session management information elements

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

10.5.6.1 Access Point Name

The purpose of the access point name information element is to identify the packet data network to which the GPRS user wishes to connect and to notify the access point of the packet data network that wishes to connect to the MS.

The Access Point Name is a label or a full qualified domain name according to DNS naming conventions (see 3GPP TS 03.03 [10]).

The access point name is a type 4 information element with a minimum length of 3 octets and a maximum length of 102 octets.

The access point name information element is coded as shown in figure 10.5.134/3GPP TS 04.08 and table 10.5.152/3GPP TS 04.08.

8 7 6 5 4 3 2 1

Access point name IEI

octet 1

Length of access point name contents

octet 2

Access point name value

octet 3

octet n*

Figure 10.5.134/3GPP TS 04.08: Access point name information element

The value part is defined in 03.03 [10].

10.5.6.2 Network service access point identifier

The purpose of the network service access point identifier information element is to identify the service access point that is used for the GPRS data transfer at layer 3.

The network service access point identifier is a type 3 information element with a length of 2 octets.

The value part of a network service access point identifier information element is coded as shown in figure 10.5.135/3GPP TS 04.08 and table 10.5.153/3GPP TS 04.08.

8 7 6 5 4 3 2 1

NSAPI IEI

octet 1

0 0 0 0
Spare

NSAPI
value

octet 2

Figure 10.5.135/3GPP TS 04.08: Network service access point identifier information element

Table 10.5.153/3GPP TS 04.08: Network service access point identifier information element

NSAPI value (octet 2)

Bit

4 3 2 1

0 0 0 0 reserved

0 0 0 1 reserved

0 0 1 0 reserved

0 0 1 1 reserved

0 1 0 0 reserved

0 1 0 1 NSAPI 5

0 1 1 0 NSAPI 6

0 1 1 1 NSAPI 7

1 0 0 0 NSAPI 8

1 0 0 1 NSAPI 9

1 0 1 0 NSAPI 10

1 0 1 1 NSAPI 11

1 1 0 0 NSAPI 12

1 1 0 1 NSAPI 13

1 1 1 0 NSAPI 14

1 1 1 1 NSAPI 15

10.5.6.3 Protocol configuration options

The purpose of the protocol configuration options information element is to transfer external network protocol options associated with a PDP context activation.

The protocol configuration options is a type 4 information element with a minimum length of 2 octets and a maximum length of 253 octets.

The protocol configuration options information element is coded as shown in figure 10.5.136/3GPP TS 04.08 and table 10.5.154/3GPP TS 04.08.

8 7 6 5 4 3 2 1

Protocol configuration options IEI

octet 1

Length of protocol config. options contents

octet 2

1
ext

0 0 0 0
Spare

Configuration
protocol

octet 3

Protocol ID 1

octet 4
octet 5

Length of protocol ID 1 contents

octet 6

Protocol ID 1 contents

octet 7

octet m

Protocol ID 2

octet m+1
octet m+2

Protocol ID 2 contents

octet m+4

octet n

. . .

octet n+1

octet x

Protocol ID n-1

octet x+1
octet x+2

Length of protocol ID n-1 contents

octet x+3

Protocol ID n-1 contents

octet x+4

octet y

Protocol ID n

octet y+1
octet y+2

Length of protocol ID n contents

octet y+3

Protocol ID n contents

octet y+4

octet z

Figure 10.5.136/3GPP TS 04.08: Protocol configuration options information element

Table 10.5.154/3GPP TS 04.08: Protocol configuration options information element

Configuration protocol (octet 3)
Bits
3 2 1
0 0 0 PPP for use with IP PDP type

All other values are interpreted as PPP in this version of the protocol.

Configuration protocol options list (octets 4 to z)

The configuration protocol options list contains a variable number of logical units, the may occur in an arbitrary order within the configuration protocol options list.

Each unit is of variable length and consists of a

– protocol identifier (2 octets);
– the length of the protocol identifier contents of the unit (1 octet); and
– the protocol identifier contents itself ( n octets).

The protocol identifier field contains the hexadecimal coding of the configuration protocol identifier. Bit 8 of the first octet of the protocol identifier field contains the most significant bit and bit 1 of the second octet of the protocol identifier field contains the least significant bit.

If the configuration protocol options list contains a protocol identifier that is not supported by the receiving entity the corresponding unit shall be discarded.

The length of the protocol identifier contents field contains the binary coded representation of the length of the protocol identifier contents field of a unit. The first bit in transmission order is the most significant bit.

The protocol identifier contents field of each unit contains information specific to the configuration protocol specified by the protocol identifier.

PPP

At least the following protocol identifiers (as defined in RFC 1700) shall be supported in this version of the protocol:

– C021H (LCP;
– C023H (PAP);
– C223H (CHAP);and
– 8021H (IPCP).

The support of other protocol identifiers is implementation dependent and outside the scope of the present document.

The protocol identifier contents field of each unit corresponds to a ‘Packet’ as defined in RFC 1661 that is stripped off the ‘Protocol’ and the ‘Padding’ octets.

The detailed coding of the protocol identifier contents field is specified in the RFC that is associated with the protocol identifier of that unit.

10.5.6.4 Packet data protocol address

The purpose of the packet data protocol address information element is to identify an address associated with a PDP.

The packet data protocol address is a type 4 information element with minimum length of 4 octets and a maximum length of 20 octets.

The packet data protocol address information element is coded as shown in figure 10.5.137/3GPP TS 04.08 and table 10.5.155/3GPP TS 04.08.

8 7 6 5 4 3 2 1

Packet data protocol address IEI

octet 1

Length of PDP address contents

octet 2

0 0 0 0
spare

PDP type organisation

octet 3

PDP type number

octet 4

Address information

octet 5

octet n

Figure 10.5.137/3GPP TS 04.08: Packet data protocol address information element

Table 10.5.155/3GPP TS 04.08: Packet data protocol address information element

Length of PDP address contents (octet 2)

If the value of octet 2 equals 0000 0010, then :

– No PDP address is included in this information element; and

– If the PDP type is IP, dynamic addressing is applicable.

NOTE : For PPP no address is required in this information element.

PDP type organisation (octet 3)
Bits
4 3 2 1
In MS to network direction :
0 0 0 0 ETSI allocated address (e.g. X.121)
0 0 0 1 IETF allocated address
1 1 1 1 Empty PDP type

All other values are reserved.

In network to MS direction :
0 0 0 0 ETSI allocated address (e.g. X.121)
0 0 0 1 IETF allocated address

All other values are reserved.

If bits 4,3,2,1 of octet 3 are coded 0 0 0 0
PDP type number value (octet 4)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 X.121 address
0 0 0 0 0 0 0 1 PDP-type PPP

All other values shall be interpreted as X.121 address
in this version of the protocol.

If bits 4,3,2,1 of octet 3 are coded 0 0 0 1
PDP type number value (octet 4)
Bits
8 7 6 5 4 3 2 1
0 0 1 0 0 0 0 1 IPv4 address
0 1 0 1 0 1 1 1 IPv6 address

All other values shall be interpreted as IPv4 address
in this version of the protocol.

In MS to network direction:
If bits 4,3,2,1 of octet 3 are coded 1 1 1 1
PDP type number value (octet 4)
bits 8 to 1 are spare and shall be coded all 0.

Octet 3, bits 7, 6, and 5 are spare and shall be coded all 0.

If PDP type number indicates X.121, the Address information is coded as follows:

8 7 6 5 4 3 2 1

digit 2

digit 1

octet 5

digit 4

digit 3

octet 6

digit m+1

digit m

octet n*

Digit 1 contains the first BCD coded digit of the X.121 address. If the X.121 address has an odd number of digits, digit m+1 shall be padded with HEX(F).

If PDP type number indicates IPv4, the Address information in octet 5 to octet 8 contains the IPv4 address. Bit 8 of octet 5 represents the most significant bit of the IP address and bit 1 of octet 8 the least significant bit .

If PDP type number indicates IPv6, the Address information in octet 5 to octet 20 contains the IPv6 address. Bit 8 of octet 5 represents the most significant bit of the IP address and bit 1 of octet 20 the least significant bit.

10.5.6.5 Quality of service

The purpose of the quality of service information element is to specify the QoS parameters for a PDP context.

The quality of service is a type 4 information element with a length of 5 octets.

The quality of service information element is coded as shown in figure 10.5.138/3GPP TS 04.08 and table 10.5.156/3GPP TS 04.08.

8 7 6 5 4 3 2 1

Quality of service IEI

octet 1

Length of quality of service IE

Octet 2

0 0
spare

Delay
class

Reliability
class

octet 3

Peak
throughput

0
spare

Precedence
class

octet 4

0 0 0
spare

Mean
throughput

octet 5

Figure 10.5.138/3GPP TS 04.08: Quality of service information element

Table 10.5.156/3GPP TS 04.08: Quality of service information element

Reliability class, octet 3 (see 3GPP TS 03.60)
Bits
3 2 1
In MS to network direction:
0 0 0 Subscribed reliability class
In network to MS direction:
0 0 0 Reserved
In MS to network direction and in network to MS direction :
0 0 1 Acknowledged GTP, LLC, and RLC; Protected data
0 1 0 Unacknowledged GTP; Acknowledged LLC and RLC, Protected data
0 1 1 Unacknowledged GTP and LLC; Acknowledged RLC, Protected data
1 0 0 Unacknowledged GTP, LLC, and RLC, Protected data
1 0 1 Unacknowledged GTP, LLC, and RLC, Unprotected data
1 1 1 Reserved

All other values are interpreted as Unacknowledged GTP and LLC; Acknowledged RLC, Protected data in this version of the protocol.

Delay class, octet 3 (see 3GPP TS 02.60 and 3GPP TS 03.60)
Bits
6 5 4
In MS to network direction:
0 0 0 Subscribed delay class
In network to MS direction:
0 0 0 Reserved
In MS to network direction and in network to MS direction :
0 0 1 Delay class 1
0 1 0 Delay class 2
0 1 1 Delay class 3
1 0 0 Delay class 4 (best effort)
1 1 1 Reserved

All other values are interpreted as Delay class 4 (best effort) in this version
of the protocol.

Bit 7 and 8 of octet 3 are spare and shall be coded all 0.

Precedence class, octet 4 (see 3GPP TS 03.60)
Bits
3 2 1
In MS to network direction:
0 0 0 Subscribed precedence
In network to MS direction:
0 0 0 Reserved
In MS to network direction and in network to MS direction :
0 0 1 High priority
0 1 0 Normal priority
0 1 1 Low priority
1 1 1 Reserved

All other values are interpreted as Normal priority in this version of the protocol.

Bit 4 of octet 4 is spare and shall be coded as 0.

Peak throughput, octet 4
Bits
8 7 6 5
In MS to network direction:
0 0 0 0 Subscribed peak throughput
In network to MS direction:
0 0 0 0 Reserved
In MS to network direction and in network to MS direction :
0 0 0 1 Up to 1 000 octet/s
0 0 1 0 Up to 2 000 octet/s
0 0 1 1 Up to 4 000 octet/s
0 1 0 0 Up to 8 000 octet/s
0 1 0 1 Up to 16 000 octet/s
0 1 1 0 Up to 32 000 octet/s
0 1 1 1 Up to 64 000 octet/s
1 0 0 0 Up to 128 000 octet/s
1 0 0 1 Up to 256 000 octet/s
1 1 1 1 Reserved

All other values are interpreted as Up to 1 000 octet/s in this
version of the protocol.

Mean throughput, octet 5
Bits
5 4 3 2 1
In MS to network direction:
0 0 0 0 0 Subscribed mean throughput
In network to MS direction:
0 0 0 0 0 Reserved
In MS to network direction and in network to MS direction :
0 0 0 0 1 100 octet/h
0 0 0 1 0 200 octet/h
0 0 0 1 1 500 octet/h
0 0 1 0 0 1 000 octet/h
0 0 1 0 1 2 000 octet/h
0 0 1 1 0 5 000 octet/h
0 0 1 1 1 10 000 octet/h
0 1 0 0 0 20 000 octet/h
0 1 0 0 1 50 000 octet/h
0 1 0 1 0 100 000 octet/h
0 1 0 1 1 200 000 octet/h
0 1 1 0 0 500 000 octet/h
0 1 1 0 1 1 000 000 octet/h
0 1 1 1 0 2 000 000 octet/h
0 1 1 1 1 5 000 000 octet/h
1 0 0 0 0 10 000 000 octet/h
1 0 0 0 1 20 000 000 octet/h
1 0 0 1 0 50 000 000 octet/h
1 1 1 1 0 Reserved
1 1 1 1 1 Best effort

The value Best effort indicates that throughput shall be made available to the MS on a per need and availability basis.

All other values are interpreted as Best effort in this
version of the protocol.
Bits 8 to 6 of octet 5 are spare and shall be coded all 0.

10.5.6.6 SM cause

The purpose of the SM cause information element is to indicate the reason why a session management request is rejected.

The SM cause is a type 3 information element with 2 octets length.

The SM cause information element is coded as shown in figure 10.5.139/3GPP TS 04.08 and table 10.5.157/3GPP TS 04.08.

8 7 6 5 4 3 2 1

SM cause IEI

octet 1

Cause value

octet 2

Figure 10.5.139/3GPP TS 04.08: SM cause information element

Table 10.5.157/3GPP TS 04.08: SM cause information element

Cause value (octet 2)

Bits

8 7 6 5 4 3 2 10 0 0 1 1 0 0 1 LLC or SNDCP failure
0 0 0 1 1 0 1 0 Insufficient resources
0 0 0 1 1 0 1 1 Missing or unknown APN
0 0 0 1 1 1 0 0 Unknown PDP address or PDP type
0 0 0 1 1 1 0 1 User Aauthentication failed 0 0 0 1 1 1 1 0 Activation rejected by GGSN

0 0 0 1 1 1 1 1 Activation rejected, unspecified

0 0 1 0 0 0 0 0 Service option not supported

0 0 1 0 0 0 0 1 Requested service option

not subscribed

0 0 1 0 0 0 1 0 Service option temporarily

out of order

0 0 1 0 0 0 1 1 NSAPI already used

0 0 1 0 0 1 0 0 Regular deactivation

0 0 1 0 0 1 0 1 QoS not accepted

0 0 1 0 0 1 1 0 Network failure

0 0 1 0 0 1 1 1 Reactivation required

0 0 1 0 1 0 0 0 Feature not supported

0 1 0 1 0 0 0 1 Invalid transaction identifier value

0 1 0 1 1 1 1 1 Semantically incorrect message

0 1 1 0 0 0 0 0 Invalid mandatory information

0 1 1 0 0 0 0 1 Message type non-existent

or not implemented

0 1 1 0 0 0 1 0 Message type not compatible with

the protocol state

0 1 1 0 0 0 1 1 Information element non-existent

or not implemented

0 1 1 0 0 1 0 0 Conditional IE error

0 1 1 0 0 1 0 1 Message not compatible with

the protocol state

0 1 1 0 1 1 1 1 Protocol error, unspecified

Any other value received by the mobile station shall
be treated as 0010 0010, ‘Service option temporarily
out of order’. Any other value received by the network
shall be treated as 0110 1111, ‘Protocol error,
unspecified’.

NOTE: The listed cause values are defined in
Annex I

10.5.6.7 Spare

This is intentionally left spare.

10.5.6.8 AA deactivation cause

The purpose of the AA deactivation cause information element is to indicate the reason why a AA PDP context was deactivated by the network.

The AA deactivation cause information element is coded as shown in figure 10.5.140/3GPP TS 04.08 and table 10.5.158/3GPP TS 04.08.

The AA deactivation cause is a type 1 information element.

8 7 6 5 4 3 2 1

AA deactivation cause indicator IEI

0
spare

AA deactivation
cause value

octet 1

Figure 10.5.140/3GPP TS 04.08: AA deactivation cause information element

Table 10.5.158/3GPP TS 04.08: AA deactivation cause information element

AA deactivation cause value (octet 1)

Bits

3 2 1

0 0 0 Normal, unspecified

0 0 1 Server address violation

0 1 0 Network overload

0 1 1 Server not reachable

All other values are interpreted as Normal, unspecified by this version
of the protocol.

10.5.6.9 LLC service access point identifier

The purpose of the LLC service access point identifier information element is to identify the service access point that is used for the GPRS data transfer at LLC layer.

The LLC service access point identifier is a type 3 information element with a length of 2 octets.

The value part of a LLC service access point identifier information element is coded as shown in figure 10.5.141/3GPP TS 04.08 and table 10.5.159/3GPP TS 04.08.

8 7 6 5 4 3 2 1

LLC SAPI IEI

octet 1

0 0 0 0
Spare

LLC SAPI
value

octet 2

Figure 10.5.141/3GPP TS 04.08: LLC service access point identifier information element

Table 10.5.159/3GPP TS 04.08: LLC service access point identifier information element

LLC SAPI value (octet 2)

Bit

4 3 2 1

0 0 1 1 SAPI 3

0 1 0 1 SAPI 5

1 0 0 1 SAPI 9

1 0 1 1 SAPI 11

All other values are reserved.